| 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. | Производи са специфичним TLD-овима имају предност над универзалним производима. На пример, производ са .io ће се користити за .io домене чак и ако постоји универзални производ. Потребан вам је само један универзални производ — не креирајте одвојене производе за сваки 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. Производи са специфичним TLD-овима имају предност над универзалним производима. На пример, производ са .io ће се користити за .io домене чак и ако постоји универзални производ. Потребан вам је само један универзални производ — не креирајте одвојене производе за сваки 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 said: "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 need to translate this from English to Serbian. The user specified that I am a professional translation engine 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.↵ ↵ Also, there's a glossary term: "product" should be translated as "производ" (noun).↵ ↵ Now, let's break down the original text:↵ ↵ - "Limit this product to specific TLDs." – TLDs likely stands for Top-Level Domains, like .com, .net, etc. In the context of a WordPress plugin, it might be related to domain pricing or something similar. I need to translate this naturally.↵ ↵ - "Leave empty to make this a catch-all product that prices any TLD not covered by another product." – This explains what happens if the field is left empty.↵ ↵ Key terms to translate:↵ ↵ - "product" – from the glossary, it should be "производ".↵ ↵ - "TLDs" – I should keep it as TLDs or translate it? Since it's a technical term, it might be best to keep it as TLDs or use the Serbian equivalent. In Serbian, TLD is often referred to as "TLD" or "врхунски домен", but for simplicity and consistency with technical contexts, I'll use "TLD-ova" or similar. Let's see: "specific TLDs" – perhaps "одређеним TLD-овима" or "специфичним TLD-овима". I'll aim for natural language.↵ ↵ - "catch-all product" – this means a product that covers everything else. In Serbian, I might say "универзални производ" or "производ за све остале". But "catch-all" is often translated as "ухвати све" or "општи". I need to find a natural equivalent.↵ ↵ - "prices any TLD" – here "prices" is a verb meaning to set the price for. In Serbian, "одређује цену за" or "цени".↵ ↵ Now, constructing the translation:↵ ↵ First part: "Limit this product to specific TLDs."↵ ↵ - "Limit" – ограничи↵ ↵ - "this product" – овај производ (using glossary term)↵ ↵ - "to specific TLDs" – на одређене TLD-ове↵ ↵ So, "Ограничи овај производ на одређене TLD-ове."↵ ↵ But to make it more natural: "Ограничите овај производ на специфичне TLD-ове." Since it's likely an instruction in a form, using the imperative might be appropriate.↵ ↵ Second part: "Leave empty to make this a catch-all product that prices any TLD not covered by another product."↵ ↵ - "Leave empty" – Оставите празно↵ ↵ - "to make this a catch-all product" – да би овај производ био универзалан (or catch-all). Let's think: "catch-all product" could be "производ који обухвата све" or "универзални производ".↵ ↵ - "that prices any TLD" – који одређује цену за било који TLD↵ ↵ - "not covered by another product" – који није покривен другим производом↵ ↵ Putting it together: "Оставите празно да би овај производ био универзалан и одређивао цену за било који TLD који није покривен другим производом."↵ ↵ But to make it concise and natural: "Оставите празно да би овај производ био универзалан и одређивао цену за све TLD-ове који нису покривени другим производима."↵ ↵ I need to ensure that "product" is consistently translated as "производ".↵ ↵ Also, preserve any placeholders. In the original text, there are no placeholders like %s, so I don't need to worry about that.↵ ↵ Now, combining both parts with the original punctuation: The original has a period at the end of the first sentence, and the second sentence continues. In Serbian, we use similar punctuation.↵ ↵ Final translation attempt:↵ ↵ "Ограничите овај производ на специфичне TLD-ове. Оставите празно да би овај производ био универзалан и одређивао цену за било који TLD који није покривен другим производом."↵ ↵ To make it flow better | 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 said: "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 need to translate this from English to Serbian. The user specified that I am a professional translation engine 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.↵ ↵ Also, there's a glossary term: "product" should be translated as "производ" (noun).↵ ↵ Now, let's break down the original text:↵ ↵ - "Limit this product to specific TLDs." – TLDs likely stands for Top-Level Domains, like .com, .net, etc. In the context of a WordPress plugin, it might be related to domain pricing or something similar. I need to translate this naturally.↵ ↵ - "Leave empty to make this a catch-all product that prices any TLD not covered by another product." – This explains what happens if the field is left empty.↵ ↵ Key terms to translate:↵ ↵ - "product" – from the glossary, it should be "производ".↵ ↵ - "TLDs" – I should keep it as TLDs or translate it? Since it's a technical term, it might be best to keep it as TLDs or use the Serbian equivalent. In Serbian, TLD is often referred to as "TLD" or "врхунски домен", but for simplicity and consistency with technical contexts, I'll use "TLD-ova" or similar. Let's see: "specific TLDs" – perhaps "одређеним TLD-овима" or "специфичним TLD-овима". I'll aim for natural language.↵ ↵ - "catch-all product" – this means a product that covers everything else. In Serbian, I might say "универзални производ" or "производ за све остале". But "catch-all" is often translated as "ухвати све" or "општи". I need to find a natural equivalent.↵ ↵ - "prices any TLD" – here "prices" is a verb meaning to set the price for. In Serbian, "одређује цену за" or "цени".↵ ↵ Now, constructing the translation:↵ ↵ First part: "Limit this product to specific TLDs."↵ ↵ - "Limit" – ограничи↵ ↵ - "this product" – овај производ (using glossary term)↵ ↵ - "to specific TLDs" – на одређене TLD-ове↵ ↵ So, "Ограничи овај производ на одређене TLD-ове."↵ ↵ But to make it more natural: "Ограничите овај производ на специфичне TLD-ове." Since it's likely an instruction in a form, using the imperative might be appropriate.↵ ↵ Second part: "Leave empty to make this a catch-all product that prices any TLD not covered by another product."↵ ↵ - "Leave empty" – Оставите празно↵ ↵ - "to make this a catch-all product" – да би овај производ био универзалан (or catch-all). Let's think: "catch-all product" could be "производ који обухвата све" or "универзални производ".↵ ↵ - "that prices any TLD" – који одређује цену за било који TLD↵ ↵ - "not covered by another product" – који није покривен другим производом↵ ↵ Putting it together: "Оставите празно да би овај производ био универзалан и одређивао цену за било који TLD који није покривен другим производом."↵ ↵ But to make it concise and natural: "Оставите празно да би овај производ био универзалан и одређивао цену за све TLD-ове који нису покривени другим производима."↵ ↵ I need to ensure that "product" is consistently translated as "производ".↵ ↵ Also, preserve any placeholders. In the original text, there are no placeholders like %s, so I don't need to worry about that.↵ ↵ Now, combining both parts with the original punctuation: The original has a period at the end of the first sentence, and the second sentence continues. In Serbian, we use similar punctuation.↵ ↵ Final translation attempt:↵ ↵ "Ограничите овај производ на специфичне TLD-ове. Оставите празно да би овај производ био универзалан и одређивао цену за било који TLD који није покривен другим производом."↵ ↵ To make it flow better
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. | Сваки провајдер има свој ценовник. Основна цена се добија од провајдера, а затим се примењује ваша надокнада. | Details | |
|
Each provider has its own pricing. The base cost is fetched from the provider, then your markup is applied. Сваки провајдер има свој ценовник. Основна цена се добија од провајдера, а затим се примењује ваша надокнада.
You have to log in to edit this translation.
|
|||
| The domain registrar used to check availability and register domains sold through this product. | Регистратор домена који се користи за проверу доступности и регистрацију домена продатих кроз овај производ. | Details | |
|
The domain registrar used to check availability and register domains sold through this product. Регистратор домена који се користи за проверу доступности и регистрацију домена продатих кроз овај производ.
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. | Конфигуришите регистрацију домена и ценовник за овај производ. Сви ценовници се контролишу овде — цена која се приказује клијенту се израчунава на основу ових подешавања. | Details | |
|
Configure domain registration and pricing for this product. All pricing is controlled here — the customer-facing price is calculated based on these settings. Конфигуришите регистрацију домена и ценовник за овај производ. Сви ценовници се контролишу овде — цена која се приказује клијенту се израчунава на основу ових подешавања.
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 zahteva Ultimate Multisite %1$s ili višu verziju. Pokrećete %2$s. Molimo vas da ažurirate 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 zahteva Ultimate Multisite %1$s ili višu verziju. Pokrećete %2$s. Molimo vas da ažurirate 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>Напомена:</strong> Namecheap укључује WHOIS приватност (WhoisGuard) бесплатно. OpenSRS наплаћује за WHOIS приватност — трошак се одузима од вашег рачуна реселера. | 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>Напомена:</strong> Namecheap укључује WHOIS приватност (WhoisGuard) бесплатно. OpenSRS наплаћује за WHOIS приватност — трошак се одузима од вашег рачуна реселера.
You have to log in to edit this translation.
|
|||
| WHOIS Privacy Price | Cena WHOIS privatnosti | Details | |
| Customer Choice | Izbor kupca | Details | |
| Always Included | Uvek uključeno | Details | |
| Disabled | Onemogućeno | Details | |
| Controls whether WHOIS privacy is available for domains registered with this product. | Kontroliše da li je WHOIS privatnost dostupna za domene registrovane sa ovim производом. | Details | |
|
Controls whether WHOIS privacy is available for domains registered with this product. Kontroliše da li je WHOIS privatnost dostupna za domene registrovane sa ovim производом.
You have to log in to edit this translation.
|
|||
| Hide your personal contact information from the public WHOIS database. | Сакрити ваше личне контакт информације од јавне WHOIS базе података. | Details | |
|
Hide your personal contact information from the public WHOIS database. Сакрити ваше личне контакт информације од јавне WHOIS базе података.
You have to log in to edit this translation.
|
|||
| Phone number with country code (e.g. +15551234567). | Broj telefona sa zemljopisnim kodom (npr. +15551234567). | Details | |
|
Phone number with country code (e.g. +15551234567). Broj telefona sa zemljopisnim kodom (npr. +15551234567).
You have to log in to edit this translation.
|
|||
| Include country code (e.g. +15551234567). | Uključite zemaljski kod (npr. +15551234567). | Details | |
|
Include country code (e.g. +15551234567). Uključite zemaljski kod (npr. +15551234567).
You have to log in to edit this translation.
|
|||
Export as