GlotPress

First, the user has provided a glossary for specific terms:↵ ↵ - "all" should be translated as "すべて" in hiragana, not "全て".↵ ↵ - "override" should be translated as "上書き" as a verb, not "オーバーライドする".↵ ↵ The text to translate is: "Products with specific TLDs override catch-all products. For example, a product with .io will be used for .io domains even if a catch-all product exists. You only need one catch-all product — do not create separate products for each TLD."↵ ↵ I need to translate this from English to Japanese, following the instructions:↵ ↵ - Return ONLY the translated text.↵ ↵ - Use natural language.↵ ↵ - Do not explain.↵ ↵ - Do not add quotes.↵ ↵ - Preserve punctuation, formatting, HTML, placeholders (%s, %1$s, %2$d), and variables exactly. In this text, there are no placeholders or variables like %s, but I should be careful with the example ".io" which is a TLD and should be preserved as is.↵ ↵ - Use the glossary terms: "all" as "すべて" and "override" as "上書き".↵ ↵ Now, breaking down the text:↵ ↵ 1. "Products with specific TLDs override catch-all products."↵ ↵ - "Products with specific TLDs" → 特定のTLDを持つ製品↵ ↵ - "override" → 上書きする (but glossary says "上書き" as verb? Actually, "override" is a verb here, so I should use "上書きする" or just "上書き" depending on context. Glossary says "上書き" (verb), so I'll use "上書きする" to make it a verb form.↵ ↵ - "catch-all products" → キャッチオール製品. But note: "catch-all" might be a term that doesn't have a direct translation. In Japanese, it's often kept as "キャッチオール" or translated as "包括的". However, since the glossary specifies "all" as "すべて", I need to see if "catch-all" should be translated. The glossary is for the word "all", but "catch-all" is a compound term. I think it's best to keep "catch-all" as is or use a common translation. In context, "catch-all product" might be translated as "包括製品" or "キャッチオール製品". To be safe, I'll use "キャッチオール製品" since it's a technical term.↵ ↵ - Revised: 特定のTLDを持つ製品はキャッチオール製品を上書きします。↵ ↵ 2. "For example, a product with .io will be used for .io domains even if a catch-all product exists."↵ ↵ - "For example" → 例えば↵ ↵ - "a product with .io" → .ioを持つ製品↵ ↵ - "will be used for .io domains" → .ioドメインに使用されます↵ ↵ - "even if a catch-all product exists" → キャッチオール製品が存在する場合でも↵ ↵ - Combined: 例えば、.ioを持つ製品は、キャッチオール製品が存在する場合でも、.ioドメインに使用されます。↵ ↵ 3. "You only need one catch-all product — do not create separate products for each TLD."↵ ↵ - "You only need one catch-all product" → キャッチオール製品は1つだけ必要です↵ ↵ - "do not create separate products for each TLD" → 各TLDごとに個別の製品を作成しないでください↵ ↵ - The dash "—" should be preserved. In Japanese, it might be replaced with a comma or kept as is. I'll keep it as "—" or use a Japanese equivalent like "―". But to preserve punctuation, I'll use the same dash.↵ ↵ - Combined: キャッチオール製品は1つだけ必要です — 各TLDごとに個別の製品を作成しないでください。↵ ↵ Now, putting it all together:↵ ↵ "特定のTLDを持つ製品はキャッチオール製品を上書きします。例えば、.ioを持つ製品は、キャッチオール製品が存在する場合でも、.ioドメインに使用されます。キャッチオール製品は1つだけ必要です — 各TLDごとに個別の製品を作成しないでください。"↵ ↵ I need to ensure that "all" is translated as "すべて" where applicable. In "catch-all", "all" is part of the term, but since "catch-all" is a fixed term, I might not change it. The glossary says "all" = "すべて" as an adjective, but in "catch-all", it's not used as a standalone adjective. I think it's fine to

First, the user has provided a text to translate from English to Japanese. The text is: "Limit this product to specific TLDs. Leave empty to make this a catch-all product that prices any TLD not covered by another product."↵ ↵ I am a professional translation engine, and I need to translate this text for a WordPress plugin. The instructions are clear: translate from English to Japanese, return ONLY the translated text, use natural language, do not explain, do not add quotes, preserve punctuation, formatting, HTML, placeholders (%s, %1$s, %2$d), and variables exactly.↵ ↵ I also have a glossary term to use: "all" should be translated as "すべて" in hiragana, not "全て". So, wherever "all" appears, I should use "すべて".↵ ↵ Now, let's break down the original text:↵ ↵ - "Limit this product to specific TLDs." – This means restricting the product to certain top-level domains (TLDs).↵ ↵ - "Leave empty to make this a catch-all product that prices any TLD not covered by another product." – This means if the field is left empty, the product will act as a catch-all, pricing any TLD that isn't already covered by another product.↵ ↵ Key terms:↵ ↵ - "TLDs" – This is an acronym for Top-Level Domains. In Japanese, it's often kept as TLDs or translated as トップレベルドメイン. Since it's a technical term, I might keep it as TLDs or use the Japanese equivalent. The instruction says to preserve variables and placeholders, but TLDs isn't a placeholder; it's a term. I should use the common Japanese term, which is often "TLD" or "トップレベルドメイン". For naturalness, I'll use "TLD" as it's widely understood in Japanese context.↵ ↵ - "catch-all product" – This means a product that covers everything else. In the glossary, "all" is translated as "すべて". So, "catch-all" could be translated as "すべてをカバーする" or something similar. But "catch-all" is a specific term; I need to find a natural Japanese equivalent. Perhaps "包括的な製品" or "すべてに対応する製品". Since the glossary specifies "all" as "すべて", I should incorporate that.↵ ↵ - "prices" – Here, it's a verb meaning to set a price for something. In Japanese, it could be "価格を設定する" or simply "価格付けする".↵ ↵ The instruction says to use natural language, so I need to make the translation sound natural in Japanese.↵ ↵ Let me translate sentence by sentence:↵ ↵ 1. "Limit this product to specific TLDs."↵ ↵ - "この製品を特定のTLDに制限する。" or more naturally, "この製品を特定のTLDのみに限定する。"↵ ↵ 2. "Leave empty to make this a catch-all product that prices any TLD not covered by another product."↵ ↵ - "空欄にすると、この製品は他の製品でカバーされていないすべてのTLDに価格を設定する包括的な製品になります。"↵ ↵ - But I need to use "すべて" for "all". In this context, "any TLD" implies "all TLDs not covered", so I can use "すべてのTLD".↵ ↵ - "catch-all product" – I can translate it as "包括的な製品" or "すべてをカバーする製品". Since "catch-all" is often translated as "包括的" in technical contexts.↵ ↵ - To make it more natural for a WordPress plugin setting description, I might phrase it as: "空欄のままにすると、この製品は他の製品でカバーされていないすべてのTLDに対して価格を設定する包括製品となります。"↵ ↵ - Alternatively, simplify: "空欄にすると、他の製品でカバーされていないすべてのTLDに価格を設定する包括製品になります。"↵ ↵ Now, combine both sentences. The original text is two sentences, so I should preserve that structure.↵ ↵ Final translation draft:↵ ↵ "この製品を特定のTLDに制限します。空欄にすると、他の製品でカバーされていないすべてのTLDに価格を設定する包括製品になります。"↵ ↵ I need to ensure that "all" is translated as "すべて". In the second sentence, "any TLD" is effectively "all TLDs not covered", so using "すべてのTLD" is appropriate.↵ ↵ Check for placeholders or variables: There are none like %s in this text, so I don't need to worry about that.↵ ↵ Preserve punctuation: The original has periods at the end of each sentence, so I should include periods in Japanese, which are "。"。↵ ↵ Use natural language: The translation