| Prio | Original string | Translation | — |
|---|---|---|---|
| When enabled, the system will attempt to renew the domain and charge the customer before expiration. | Wanneer ingeschakeld, zal het systeem proberen het domein te vernieuwen en de klant voor de vervaldatum in rekening brengen. | Details | |
|
When enabled, the system will attempt to renew the domain and charge the customer before expiration. Wanneer ingeschakeld, zal het systeem proberen het domein te vernieuwen en de klant voor de vervaldatum in rekening brengen.
You have to log in to edit this translation.
|
|||
| Automatically renew domains before they expire. Customers can toggle this from their account. | Domeinen automatisch vernieuwen voordat ze verlopen. Klanten kunnen dit vanuit hun account toggle. | Details | |
|
Automatically renew domains before they expire. Customers can toggle this from their account. Domeinen automatisch vernieuwen voordat ze verlopen. Klanten kunnen dit vanuit hun account toggle.
You have to log in to edit this translation.
|
|||
| Number of years for domain registration. Most customers register for 1 year. | Aantal jaren voor domeinregistratie. De meeste klanten registreren voor 1 jaar. | Details | |
|
Number of years for domain registration. Most customers register for 1 year. Aantal jaren voor domeinregistratie. De meeste klanten registreren voor 1 jaar.
You have to log in to edit this translation.
|
|||
| <strong>Warning:</strong> Provider costs vary by TLD. A .com might cost $10 while a .io costs $35. Make sure your fixed price covers your cost for all TLDs assigned to this product, or use Supported TLDs to limit which TLDs this product handles. | <strong>Waarschuwing:</strong> Providerkosten variëren per TLD. Een .com kan $10 kosten, terwijl een .io $35 kost. Zorg ervoor dat je vaste prijs je kosten dekt voor alle TLD's die aan dit product zijn toegewezen, of gebruik Ondersteunde TLD's om te beperken welke TLD's dit product verwerkt. | Details | |
|
<strong>Warning:</strong> Provider costs vary by TLD. A .com might cost $10 while a .io costs $35. Make sure your fixed price covers your cost for all TLDs assigned to this product, or use Supported TLDs to limit which TLDs this product handles. <strong>Waarschuwing:</strong> Providerkosten variëren per TLD. Een .com kan $10 kosten, terwijl een .io $35 kost. Zorg ervoor dat je vaste prijs je kosten dekt voor alle TLD's die aan dit product zijn toegewezen, of gebruik Ondersteunde TLD's om te beperken welke TLD's dit product verwerkt.
You have to log in to edit this translation.
|
|||
| The exact price charged to the customer per year, regardless of what the provider charges you. | De exacte prijs die aan de klant per jaar wordt doorberekend, ongeacht wat de provider jou in rekening brengt. | Details | |
|
The exact price charged to the customer per year, regardless of what the provider charges you. De exacte prijs die aan de klant per jaar wordt doorberekend, ongeacht wat de provider jou in rekening brengt.
You have to log in to edit this translation.
|
|||
| Fixed amount added on top of the provider cost. E.g. $5 on a $10 domain = $15 customer price. | Vast bedrag toegevoegd bovenop de leverancierskosten. Bijv. $5 op een domein van $10 = $15 klantenprijs. | Details | |
|
Fixed amount added on top of the provider cost. E.g. $5 on a $10 domain = $15 customer price. Vast bedrag toegevoegd bovenop de leverancierskosten. Bijv. $5 op een domein van $10 = $15 klantenprijs.
You have to log in to edit this translation.
|
|||
| Added on top of the provider cost. E.g. 20% on a $10 domain = $12 customer price. | Toegevoegd bovenop de leverancierskosten. Bijv. 20% op een $10 domein = $12 klantenprijs. | Details | |
|
Added on top of the provider cost. E.g. 20% on a $10 domain = $12 customer price. Toegevoegd bovenop de leverancierskosten. Bijv. 20% op een $10 domein = $12 klantenprijs.
You have to log in to edit this translation.
|
|||
| Markup Percentage (%) | Opslagpercentage (%) | Details | |
| Percentage adds a % on top of the provider cost. Fixed adds a flat amount. Fixed Price ignores the provider cost and charges a set amount. | Percentage voegt een % toe bovenop de leverancierskosten. Vast bedrag voegt een vast bedrag toe. Vaste prijs negeert de leverancierskosten en rekent een vast bedrag aan. | Details | |
|
Percentage adds a % on top of the provider cost. Fixed adds a flat amount. Fixed Price ignores the provider cost and charges a set amount. Percentage voegt een % toe bovenop de leverancierskosten. Vast bedrag voegt een vast bedrag toe. Vaste prijs negeert de leverancierskosten en rekent een vast bedrag aan.
You have to log in to edit this translation.
|
|||
| How to calculate the price your customers pay. This is the only place where pricing is configured. | Hoe de prijs te berekenen die je klanten betalen. Dit is de enige plek waar prijzen worden geconfigureerd. | Details | |
|
How to calculate the price your customers pay. This is the only place where pricing is configured. Hoe de prijs te berekenen die je klanten betalen. Dit is de enige plek waar prijzen worden geconfigureerd.
You have to log in to edit this translation.
|
|||
| 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. | Producten met specifieke TLD's hebben voorrang op algemene producten. Bijvoorbeeld, een product met .io wordt gebruikt voor .io-domeinen, zelfs als er een algemeen product bestaat. Je hebt maar één algemeen product nodig — maak geen aparte producten voor elke TLD. | Details | |
|
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. Producten met specifieke TLD's hebben voorrang op algemene producten. Bijvoorbeeld, een product met .io wordt gebruikt voor .io-domeinen, zelfs als er een algemeen product bestaat. Je hebt maar één algemeen product nodig — maak geen aparte producten voor elke TLD.
You have to log in to edit this translation.
|
|||
| Limit this product to specific TLDs. Leave empty to make this a catch-all product that prices any TLD not covered by another product. | 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 | Details | |
|
Limit this product to specific TLDs. Leave empty to make this a catch-all product that prices any TLD not covered by another product.
Warning: Lengths of source and translation differ too much.
Warning: Extra %s placeholder in translation.
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
You have to log in to edit this translation.
|
|||
| Each provider has its own pricing. The base cost is fetched from the provider, then your markup is applied. | Elke provider heeft zijn eigen prijzen. De basiskosten worden van de provider opgehaald, waarna je markup wordt toegepast. | Details | |
|
Each provider has its own pricing. The base cost is fetched from the provider, then your markup is applied. Elke provider heeft zijn eigen prijzen. De basiskosten worden van de provider opgehaald, waarna je markup wordt toegepast.
You have to log in to edit this translation.
|
|||
| The domain registrar used to check availability and register domains sold through this product. | De domeinregistrar die wordt gebruikt om beschikbaarheid te controleren en domeinen te registreren die via dit product worden verkocht. | Details | |
|
The domain registrar used to check availability and register domains sold through this product. De domeinregistrar die wordt gebruikt om beschikbaarheid te controleren en domeinen te registreren die via dit product worden verkocht.
You have to log in to edit this translation.
|
|||
| Configure domain registration and pricing for this product. All pricing is controlled here — the customer-facing price is calculated based on these settings. | Configureer domeinregistratie en prijzen voor dit product. Alle prijzen worden hier beheerd — de klantgerichte prijs wordt berekend op basis van deze instellingen. | Details | |
|
Configure domain registration and pricing for this product. All pricing is controlled here — the customer-facing price is calculated based on these settings. Configureer domeinregistratie en prijzen voor dit product. Alle prijzen worden hier beheerd — de klantgerichte prijs wordt berekend op basis van deze instellingen.
You have to log in to edit this translation.
|
|||
Export as