| Prio | Original string | 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. | First, the user has provided a text to translate from English to Danish. The text 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 am a professional translation engine, and I must follow specific instructions:↵ ↵ - Translate the text from English to Danish.↵ ↵ - 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.↵ ↵ - Use the glossary term: "create" = "opret" (verb).↵ ↵ Now, analyzing the text:↵ ↵ - "Products with specific TLDs override catch-all products." – This means that products that have specific top-level domains (like .com, .io) will take precedence over general catch-all products.↵ ↵ - "For example, a product with .io will be used for .io domains even if a catch-all product exists." – This gives an example to clarify.↵ ↵ - "You only need one catch-all product — do not create separate products for each TLD." – This is advice to avoid redundancy.↵ ↵ I need to translate this into Danish while preserving the meaning and following the glossary. The glossary specifies that "create" should be translated as "opret" (verb).↵ ↵ Key terms to translate:↵ ↵ - "products" – in Danish, "produkter" (plural).↵ ↵ - "TLDs" – this is an acronym for Top-Level Domains. In Danish, it might be kept as "TLD'er" or "topdomæner". Since it's a technical term, I should use "TLD'er" to keep it consistent.↵ ↵ - "override" – in this context, it means "tilsidesætter" or "overstyrer". I'll use "overstyrer" as it's common in technical contexts.↵ ↵ - "catch-all products" – "catch-all" might be translated as "fang-alt" or kept as "catch-all". In Danish, it's often "fang-alt" or "alt-omfattende". I'll use "fang-alt-produkter" for clarity.↵ ↵ - "domains" – "domæner".↵ ↵ - "create" – must be "opret" as per glossary.↵ ↵ Now, constructing the translation sentence by sentence:↵ ↵ 1. "Products with specific TLDs override catch-all products."↵ ↵ - Danish: "Produkter med specifikke TLD'er overstyrer fang-alt-produkter."↵ ↵ 2. "For example, a product with .io will be used for .io domains even if a catch-all product exists."↵ ↵ - Danish: "For eksempel vil et produkt med .io blive brugt for .io-domæner, selvom der findes et fang-alt-produkt."↵ ↵ - Note: ".io" is a TLD, so I should keep it as is. "domains" is "domæner", so ".io-domæner" might be better.↵ ↵ 3. "You only need one catch-all product — do not create separate products for each TLD."↵ ↵ - Danish: "Du har kun brug for et fang-alt-produkt — opret ikke separate produkter for hver TLD."↵ ↵ - Here, "create" is translated to "opret" as per glossary.↵ ↵ The text has an em dash (—), which I should preserve. Also, the punctuation and structure should be similar.↵ ↵ Full translation:↵ ↵ "Produkter med specifikke TLD'er overstyrer fang-alt-produkter. For eksempel vil et produkt med .io blive brugt for .io-domæner, selvom der findes et fang-alt-produkt. Du har kun brug for et fang-alt-produkt — opret ikke separate produkter for hver TLD."↵ ↵ I should ensure it sounds natural in Danish. Let me review:↵ ↵ - "overstyrer" is appropriate for "override".↵ ↵ - "fang-alt-produkter" might be a bit literal, but it's understandable in a technical context. Alternatively, "catch-all-produkter" could be used, but since the instruction is to use natural language, I'll stick with "fang-alt-produkter" as it's a direct translation.↵ ↵ - "Du har kun brug for" is natural for "You only need".↵ ↵ - "opret ikke" is imperative for "do not create", using "opret" as required.↵ ↵ The text doesn't have any placeholders or variables, so I don't need to worry about that.↵ ↵ Finally, return ONLY the translated text, so I'll output | 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.
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 Danish. The text 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 am a professional translation engine, and I must follow specific instructions:↵ ↵ - Translate the text from English to Danish.↵ ↵ - 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.↵ ↵ - Use the glossary term: "create" = "opret" (verb).↵ ↵ Now, analyzing the text:↵ ↵ - "Products with specific TLDs override catch-all products." – This means that products that have specific top-level domains (like .com, .io) will take precedence over general catch-all products.↵ ↵ - "For example, a product with .io will be used for .io domains even if a catch-all product exists." – This gives an example to clarify.↵ ↵ - "You only need one catch-all product — do not create separate products for each TLD." – This is advice to avoid redundancy.↵ ↵ I need to translate this into Danish while preserving the meaning and following the glossary. The glossary specifies that "create" should be translated as "opret" (verb).↵ ↵ Key terms to translate:↵ ↵ - "products" – in Danish, "produkter" (plural).↵ ↵ - "TLDs" – this is an acronym for Top-Level Domains. In Danish, it might be kept as "TLD'er" or "topdomæner". Since it's a technical term, I should use "TLD'er" to keep it consistent.↵ ↵ - "override" – in this context, it means "tilsidesætter" or "overstyrer". I'll use "overstyrer" as it's common in technical contexts.↵ ↵ - "catch-all products" – "catch-all" might be translated as "fang-alt" or kept as "catch-all". In Danish, it's often "fang-alt" or "alt-omfattende". I'll use "fang-alt-produkter" for clarity.↵ ↵ - "domains" – "domæner".↵ ↵ - "create" – must be "opret" as per glossary.↵ ↵ Now, constructing the translation sentence by sentence:↵ ↵ 1. "Products with specific TLDs override catch-all products."↵ ↵ - Danish: "Produkter med specifikke TLD'er overstyrer fang-alt-produkter."↵ ↵ 2. "For example, a product with .io will be used for .io domains even if a catch-all product exists."↵ ↵ - Danish: "For eksempel vil et produkt med .io blive brugt for .io-domæner, selvom der findes et fang-alt-produkt."↵ ↵ - Note: ".io" is a TLD, so I should keep it as is. "domains" is "domæner", so ".io-domæner" might be better.↵ ↵ 3. "You only need one catch-all product — do not create separate products for each TLD."↵ ↵ - Danish: "Du har kun brug for et fang-alt-produkt — opret ikke separate produkter for hver TLD."↵ ↵ - Here, "create" is translated to "opret" as per glossary.↵ ↵ The text has an em dash (—), which I should preserve. Also, the punctuation and structure should be similar.↵ ↵ Full translation:↵ ↵ "Produkter med specifikke TLD'er overstyrer fang-alt-produkter. For eksempel vil et produkt med .io blive brugt for .io-domæner, selvom der findes et fang-alt-produkt. Du har kun brug for et fang-alt-produkt — opret ikke separate produkter for hver TLD."↵ ↵ I should ensure it sounds natural in Danish. Let me review:↵ ↵ - "overstyrer" is appropriate for "override".↵ ↵ - "fang-alt-produkter" might be a bit literal, but it's understandable in a technical context. Alternatively, "catch-all-produkter" could be used, but since the instruction is to use natural language, I'll stick with "fang-alt-produkter" as it's a direct translation.↵ ↵ - "Du har kun brug for" is natural for "You only need".↵ ↵ - "opret ikke" is imperative for "do not create", using "opret" as required.↵ ↵ The text doesn't have any placeholders or variables, so I don't need to worry about that.↵ ↵ Finally, return ONLY the translated text, so I'll output
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. | Begræns dette produkt til specifikke TLD'er. Lad feltet være tomt for at gøre dette til et opsamlingsprodukt, der prissætter enhver TLD, der ikke er dækket af et andet produkt. | 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. Begræns dette produkt til specifikke TLD'er. Lad feltet være tomt for at gøre dette til et opsamlingsprodukt, der prissætter enhver TLD, der ikke er dækket af et andet produkt.
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. | Hver udbyder har sin egen prissætning. Grundprisen hentes fra udbyderen, og derefter påføres dit påslag. | Details | |
|
Each provider has its own pricing. The base cost is fetched from the provider, then your markup is applied. Hver udbyder har sin egen prissætning. Grundprisen hentes fra udbyderen, og derefter påføres dit påslag.
You have to log in to edit this translation.
|
|||
| The domain registrar used to check availability and register domains sold through this product. | Den domæneregistrator, der bruges til at kontrollere tilgængelighed og registrere domæner solgt gennem dette produkt. | Details | |
|
The domain registrar used to check availability and register domains sold through this product. Den domæneregistrator, der bruges til at kontrollere tilgængelighed og registrere domæner solgt gennem dette produkt.
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. | Konfigurer domæneregistrering og prissætning for dette produkt. Al prissætning styres her – den kunde-synlige pris beregnes ud fra disse indstillinger. | Details | |
|
Configure domain registration and pricing for this product. All pricing is controlled here — the customer-facing price is calculated based on these settings. Konfigurer domæneregistrering og prissætning for dette produkt. Al prissætning styres her – den kunde-synlige pris beregnes ud fra disse indstillinger.
You have to log in to edit this translation.
|
|||
| Ultimate Multisite: Domain Seller requires Ultimate Multisite %1$s or higher. You are running %2$s. Please update Ultimate Multisite. | Ultimate Multisite: Domain Seller kræver Ultimate Multisite %1$s eller højere. Du kører %2$s. Opdater venligst Ultimate Multisite. | Details | |
|
Ultimate Multisite: Domain Seller requires Ultimate Multisite %1$s or higher. You are running %2$s. Please update Ultimate Multisite. Ultimate Multisite: Domain Seller kræver Ultimate Multisite %1$s eller højere. Du kører %2$s. Opdater venligst Ultimate Multisite.
You have to log in to edit this translation.
|
|||
| <strong>Note:</strong> Namecheap includes WHOIS privacy (WhoisGuard) for free. OpenSRS charges for WHOIS privacy — the cost is deducted from your reseller balance. | <strong>Bemærk:</strong> Namecheap inkluderer WHOIS-privatliv (WhoisGuard) gratis. OpenSRS opkræver for WHOIS-privatliv — omkostningen trækkes fra din forhandlerbalance. | Details | |
|
<strong>Note:</strong> Namecheap includes WHOIS privacy (WhoisGuard) for free. OpenSRS charges for WHOIS privacy — the cost is deducted from your reseller balance. <strong>Bemærk:</strong> Namecheap inkluderer WHOIS-privatliv (WhoisGuard) gratis. OpenSRS opkræver for WHOIS-privatliv — omkostningen trækkes fra din forhandlerbalance.
You have to log in to edit this translation.
|
|||
| WHOIS Privacy Price | WHOIS Privatlivspris | Details | |
| Customer Choice | Kundens valg | Details | |
| Always Included | Altid inkluderet | Details | |
| Disabled | Deaktiveret | Details | |
| Controls whether WHOIS privacy is available for domains registered with this product. | Kontrollerer, om WHOIS-privatliv er tilgængeligt for domæner registreret med dette produkt. | Details | |
|
Controls whether WHOIS privacy is available for domains registered with this product. Kontrollerer, om WHOIS-privatliv er tilgængeligt for domæner registreret med dette produkt.
You have to log in to edit this translation.
|
|||
| Hide your personal contact information from the public WHOIS database. | Skjul dine personlige kontaktoplysninger fra den offentlige WHOIS-database. | Details | |
|
Hide your personal contact information from the public WHOIS database. Skjul dine personlige kontaktoplysninger fra den offentlige WHOIS-database.
You have to log in to edit this translation.
|
|||
| Phone number with country code (e.g. +15551234567). | Telefonnummer med landskode (f.eks. +15551234567). | Details | |
|
Phone number with country code (e.g. +15551234567). Telefonnummer med landskode (f.eks. +15551234567).
You have to log in to edit this translation.
|
|||
| Include country code (e.g. +15551234567). | Inkludér landekode (f.eks. +15551234567). | Details | |
|
Include country code (e.g. +15551234567). Inkludér landekode (f.eks. +15551234567).
You have to log in to edit this translation.
|
|||
Export as