GlotPress

First, the user has provided a text to translate from English to Dutch: "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. I must return ONLY the translated text, use natural language, not explain, not add quotes, and preserve punctuation, formatting, HTML, placeholders (%s, %1$s, %2$d), and variables exactly.↵ ↵ Additionally, there's a glossary term provided: "limit" should be translated as "beperken" (verb) in the context of REST API-specific translation. So, wherever "limit" appears as a verb, I should use "beperken".↵ ↵ Now, let's break down the text:↵ ↵ - "Limit this product to specific TLDs." – Here, "limit" is a verb, so I should use "beperken".↵ ↵ - "Leave empty to make this a catch-all product that prices any TLD not covered by another product." – This is a second sentence.↵ ↵ Key terms:↵ ↵ - TLDs: This stands for Top-Level Domains. In Dutch, it's often kept as TLDs or translated to "top-level domeinen". Since it's a technical term, I might keep it as TLDs, but I need to ensure the translation is natural. For a WordPress plugin, technical terms might be left in English or translated based on context. I'll assume TLDs is kept as is or translated if common.↵ ↵ - Catch-all product: This might be translated as "vangnetproduct" or something similar. I need to find a natural Dutch equivalent.↵ ↵ - Prices: Here, it's a verb meaning "to set a price for" or "to price". In Dutch, it could be "prijzen" or "een prijs bepalen voor".↵ ↵ The glossary specifies "limit" = "beperken" (verb). So, for "Limit this product", I'll use "Beperk dit product".↵ ↵ Now, translating the entire text:↵ ↵ Original: "Limit this product to specific TLDs. Leave empty to make this a catch-all product that prices any TLD not covered by another product."↵ ↵ Step-by-step translation:↵ ↵ 1. "Limit this product to specific TLDs." -> "Beperk dit product tot specifieke TLD's." (Note: I'm using "TLD's" with an apostrophe for plural, which is common in Dutch for abbreviations. But I should check if the original has any formatting. The original says "TLDs", so I'll keep it similar.)↵ ↵ 2. "Leave empty" -> "Laat leeg" (common in Dutch for form fields).↵ ↵ 3. "to make this a catch-all product" -> "om dit een vangnetproduct te maken" or "om dit een allesomvattend product te maken". "Catch-all" in this context means it covers everything else, so "vangnetproduct" might be appropriate, meaning a safety net product.↵ ↵ 4. "that prices any TLD not covered by another product." -> "dat een prijs bepaalt voor elke TLD die niet door een ander product wordt gedekt." or more naturally, "dat prijst elke TLD die niet door een ander product wordt afgedekt."↵ ↵ "Prices" as a verb: In Dutch, "prijzen" can be used, but it might sound a bit formal. Alternatively, "een prijs bepalen voor" is clearer. Since it's for a plugin, I should use concise language.↵ ↵ Let me try to make it natural and concise:↵ ↵ "Beperk dit product tot specifieke TLD's. Laat leeg om dit een vangnetproduct te maken dat elke TLD prijst die niet door een ander product wordt afgedekt."↵ ↵ I need to ensure that placeholders, formatting, etc., are preserved. There are no placeholders in this text, so I don't have to worry about that.↵ ↵ Check for glossary compliance: "limit" is translated as "beperken", which I used.↵ ↵ Final translation: "Beperk dit product tot specifieke TLD's. Laat leeg om dit een vangnetproduct te maken dat elke TLD prijst die niet door een ander product wordt afgedekt."↵ ↵ I think this is good. Let me confirm if "TLD's" should be "TLDs" without apostrophe. In Dutch, abbreviations often use an apostrophe for plural, but in technical contexts, it might vary. Since the original has "TLDs", I might keep it as "TLDs" to be consistent. But the instruction says to preserve formatting, so I should keep it as is if possible. However, the original text is provided