| Prio | Original string | Translation | — |
|---|---|---|---|
| When enabled, the system will attempt to renew the domain and charge the customer before expiration. | Când este activată, sistemul va încerca să reînnoiască domeniul și să perceapă clientul înainte de expirare. | Details | |
|
When enabled, the system will attempt to renew the domain and charge the customer before expiration. Când este activată, sistemul va încerca să reînnoiască domeniul și să perceapă clientul înainte de expirare.
You have to log in to edit this translation.
|
|||
| Automatically renew domains before they expire. Customers can toggle this from their account. | Reînnoiește automat domeniile înainte de expirare. Clienții pot comuta această opțiune din contul lor. | Details | |
|
Automatically renew domains before they expire. Customers can toggle this from their account. Reînnoiește automat domeniile înainte de expirare. Clienții pot comuta această opțiune din contul lor.
You have to log in to edit this translation.
|
|||
| Number of years for domain registration. Most customers register for 1 year. | Numărul de ani pentru înregistrarea domeniului. Majoritatea clienților se înregistrează pentru 1 an. | Details | |
|
Number of years for domain registration. Most customers register for 1 year. Numărul de ani pentru înregistrarea domeniului. Majoritatea clienților se înregistrează pentru 1 an.
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>Atenție:</strong> Costurile furnizorilor variază în funcție de TLD. Un .com poate costa 10 USD, în timp ce un .io costă 35 USD. Asigurați-vă că prețul dvs. fix acoperă costul pentru toate TLD-urile atribuite acestui produs sau utilizați TLD-uri acceptate pentru a limita ce TLD-uri gestionează acest produs. | 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>Atenție:</strong> Costurile furnizorilor variază în funcție de TLD. Un .com poate costa 10 USD, în timp ce un .io costă 35 USD. Asigurați-vă că prețul dvs. fix acoperă costul pentru toate TLD-urile atribuite acestui produs sau utilizați TLD-uri acceptate pentru a limita ce TLD-uri gestionează acest produs.
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. | Prețul exact perceput clientului pe an, indiferent de ceea ce vă percepe furnizorul. | Details | |
|
The exact price charged to the customer per year, regardless of what the provider charges you. Prețul exact perceput clientului pe an, indiferent de ceea ce vă percepe furnizorul.
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. | Sumă fixă adăugată pe costul furnizorului. De ex. 5$ pe un domeniu de 10$ = preț client 15$. | Details | |
|
Fixed amount added on top of the provider cost. E.g. $5 on a $10 domain = $15 customer price. Sumă fixă adăugată pe costul furnizorului. De ex. 5$ pe un domeniu de 10$ = preț client 15$.
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. | First, the user said: "Added on top of the provider cost. E.g. 20% on a $10 domain = $12 customer price." I need to translate this from English to Romanian.↵ ↵ The key points are:↵ ↵ - "Added on top of the provider cost." – This means something is added to the cost from the provider.↵ ↵ - "E.g. 20% on a $10 domain = $12 customer price." – This is an example: 20% added to a $10 domain results in a $12 price for the customer.↵ ↵ I must translate this into Romanian. The translation should be natural and preserve any placeholders, formatting, etc., but in this text, I don't see any placeholders like %s. It's plain text with an example.↵ ↵ Now, recall the glossary term: "on" = "pornit" (adjective) [se traduce doar atunci când nu reprezintă o valoare de variabilă]. This means that "on" should be translated as "pornit" only when it's not representing a variable value. In this context, "on" is used in "20% on a $10 domain". Here, "on" might be part of the phrase indicating the percentage applied to the cost. I need to check if "on" here is a variable or not.↵ ↵ In the example, "20% on a $10 domain" – "on" is a preposition meaning "applied to" or "added to". According to the glossary, "on" should be translated as "pornit" only when it's an adjective and not a variable value. But here, "on" is a preposition, not an adjective. The glossary specifies "on" = "pornit" (adjective), so for other uses, I should translate it normally.↵ ↵ Looking at the phrase: "20% on a $10 domain" – in Romanian, this might be translated as "20% pe un domeniu de 10$" or similar. But I need to be careful with the glossary.↵ ↵ The glossary says: "on" = "pornit" (adjective) [se traduce doar atunci când nu reprezintă o valoare de variabilă]. This implies that when "on" is used as an adjective (like in "the light is on"), it should be translated as "pornit". But in this context, "on" is not an adjective; it's a preposition. So, I should not use "pornit" here.↵ ↵ Therefore, for "on" in "20% on", I should translate it as a preposition, probably "pe" or "asupra", depending on the context.↵ ↵ Now, let's translate the entire sentence:↵ ↵ - "Added on top of the provider cost." – This could be: "Adăugat peste costul furnizorului."↵ ↵ - "E.g. 20% on a $10 domain = $12 customer price." – "De exemplu, 20% pe un domeniu de 10$ = prețul pentru client de 12$."↵ ↵ But I need to make it sound natural in Romanian. Also, preserve the example format.↵ ↵ Full translation: "Adăugat peste costul furnizorului. De exemplu, 20% pe un domeniu de 10$ = prețul pentru client de 12$."↵ ↵ I should check if "provider cost" is best as "costul furnizorului". Yes, that seems fine.↵ ↵ For "customer price", I used "prețul pentru client", which is clear.↵ ↵ The example uses "$10" and "$12", which should be kept as is or adapted to Romanian currency format? The instruction says to preserve formatting, so I'll keep the dollar signs. In Romanian, currency is often written after the amount, but since it's an example, it might be fine to leave it as is.↵ ↵ Also, note that the original has "E.g." which is an abbreviation for "exempli gratia", meaning "for example". In Romanian, we often use "De exemplu" or "Ex." but "E.g." might be understood in technical contexts. However, for natural language, I'll use "De exemplu".↵ ↵ Now, to ensure I'm following the instructions: Return ONLY the translated text. Use natural language. Do not explain. Do not add quotes. Preserve punctuation, formatting, HTML, placeholders, and variables exactly.↵ ↵ In this text, there are no HTML or placeholders, so I just need to translate the text.↵ ↵ Final translation: "Adăugat peste costul furnizorului. De exemplu, 20% pe un domeniu de 10$ = prețul pentru client de 12 | Details | |
|
Added on top of the provider cost. E.g. 20% on a $10 domain = $12 customer price.
Warning: Lengths of source and translation differ too much.
Warning: Extra %s placeholder in translation.
First, the user said: "Added on top of the provider cost. E.g. 20% on a $10 domain = $12 customer price." I need to translate this from English to Romanian.↵ ↵ The key points are:↵ ↵ - "Added on top of the provider cost." – This means something is added to the cost from the provider.↵ ↵ - "E.g. 20% on a $10 domain = $12 customer price." – This is an example: 20% added to a $10 domain results in a $12 price for the customer.↵ ↵ I must translate this into Romanian. The translation should be natural and preserve any placeholders, formatting, etc., but in this text, I don't see any placeholders like %s. It's plain text with an example.↵ ↵ Now, recall the glossary term: "on" = "pornit" (adjective) [se traduce doar atunci când nu reprezintă o valoare de variabilă]. This means that "on" should be translated as "pornit" only when it's not representing a variable value. In this context, "on" is used in "20% on a $10 domain". Here, "on" might be part of the phrase indicating the percentage applied to the cost. I need to check if "on" here is a variable or not.↵ ↵ In the example, "20% on a $10 domain" – "on" is a preposition meaning "applied to" or "added to". According to the glossary, "on" should be translated as "pornit" only when it's an adjective and not a variable value. But here, "on" is a preposition, not an adjective. The glossary specifies "on" = "pornit" (adjective), so for other uses, I should translate it normally.↵ ↵ Looking at the phrase: "20% on a $10 domain" – in Romanian, this might be translated as "20% pe un domeniu de 10$" or similar. But I need to be careful with the glossary.↵ ↵ The glossary says: "on" = "pornit" (adjective) [se traduce doar atunci când nu reprezintă o valoare de variabilă]. This implies that when "on" is used as an adjective (like in "the light is on"), it should be translated as "pornit". But in this context, "on" is not an adjective; it's a preposition. So, I should not use "pornit" here.↵ ↵ Therefore, for "on" in "20% on", I should translate it as a preposition, probably "pe" or "asupra", depending on the context.↵ ↵ Now, let's translate the entire sentence:↵ ↵ - "Added on top of the provider cost." – This could be: "Adăugat peste costul furnizorului."↵ ↵ - "E.g. 20% on a $10 domain = $12 customer price." – "De exemplu, 20% pe un domeniu de 10$ = prețul pentru client de 12$."↵ ↵ But I need to make it sound natural in Romanian. Also, preserve the example format.↵ ↵ Full translation: "Adăugat peste costul furnizorului. De exemplu, 20% pe un domeniu de 10$ = prețul pentru client de 12$."↵ ↵ I should check if "provider cost" is best as "costul furnizorului". Yes, that seems fine.↵ ↵ For "customer price", I used "prețul pentru client", which is clear.↵ ↵ The example uses "$10" and "$12", which should be kept as is or adapted to Romanian currency format? The instruction says to preserve formatting, so I'll keep the dollar signs. In Romanian, currency is often written after the amount, but since it's an example, it might be fine to leave it as is.↵ ↵ Also, note that the original has "E.g." which is an abbreviation for "exempli gratia", meaning "for example". In Romanian, we often use "De exemplu" or "Ex." but "E.g." might be understood in technical contexts. However, for natural language, I'll use "De exemplu".↵ ↵ Now, to ensure I'm following the instructions: Return ONLY the translated text. Use natural language. Do not explain. Do not add quotes. Preserve punctuation, formatting, HTML, placeholders, and variables exactly.↵ ↵ In this text, there are no HTML or placeholders, so I just need to translate the text.↵ ↵ Final translation: "Adăugat peste costul furnizorului. De exemplu, 20% pe un domeniu de 10$ = prețul pentru client de 12
You have to log in to edit this translation.
|
|||
| Markup Percentage (%) | First, the user is asking me to translate "Markup Percentage (%)" from English to Romanian. I am a professional translation engine, so I need to provide only the translated text.↵ ↵ Key instructions:↵ - Translate from English to Romanian.↵ - 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 provided glossary terms: "markup" should be translated as "markup" in Romanian, but with the note that it's an adjective. The glossary gives options like "marcap" or "tagat", but it says "markup" = "markup" (adjective) and suggests "limbaj markup" or "schemă (de) markup". However, in this context, "Markup Percentage" is a term, so I need to decide how to translate it.↵ ↵ The phrase is "Markup Percentage (%)". In English, "markup" here likely refers to the increase in price or cost, often in business or finance. But according to the glossary, "markup" should be kept as "markup" in Romanian, but it's noted as an adjective. The glossary says: "markup" = "markup" (adjective) [poate cu vremea... marcap | tagat ... :) limbaj markup, schemă (de) markup...]. This seems a bit confusing. It might be that in the context of WordPress plugins, "markup" is a technical term that should not be translated directly.↵ ↵ Looking at the glossary: it says "markup" = "markup" (adjective), and then gives some Romanian suggestions like "marcap" or "tagat", but with smileys and notes, which might indicate that these are playful or alternative translations. However, the instruction is to "Use these glossary terms", so I should follow the glossary.↵ ↵ The glossary specifies that "markup" should be translated as "markup" in Romanian, but it's in parentheses as an adjective. It also provides options like "limbaj markup" or "schemă (de) markup", which might be for different contexts. In this case, "Markup Percentage" might be a specific term.↵ ↵ I need to translate "Markup Percentage (%)". The word "Percentage" should be translated to Romanian as "Procentaj" or "Procent", but since it's followed by (%), it might be "Procentaj" or simply "Procent".↵ ↵ But to preserve the placeholders and variables, I should keep the (%) as is, since it's part of the text.↵ ↵ Let me break it down:↵ - "Markup" – according to glossary, keep as "markup" but in Romanian context. The glossary says "markup" = "markup" (adjective), so perhaps I should use "markup" as is, or adapt it.↵ - "Percentage" – translate to "Procentaj" or "Procent".↵ - The entire phrase: "Markup Percentage (%)"↵ ↵ In Romanian, a natural translation might be "Procentaj de Markup (%)" or "Procent de Markup (%)". But since the glossary says to use "markup" as "markup", I should probably keep "markup" untranslated.↵ ↵ The glossary says: "markup" = "markup" (adjective) [poate cu vremea... marcap | tagat ... :) limbaj markup, schemă (de) markup...]. This seems to suggest that "markup" can be translated in various ways, but for consistency, I should use "markup" as per the glossary.↵ ↵ Perhaps in this context, "Markup Percentage" is a technical term, so it might be best to keep "Markup" as is and translate "Percentage".↵ ↵ Let me think about common translations in business Romanian. "Markup" is often translated as "marjă de profit" or "adaos comercial", but the glossary specifically says to use "markup" as "markup".↵ ↵ Given the instruction to use the glossary terms, I should translate "markup" as "markup" in Romanian. But the glossary says it's an adjective, so in "Markup Percentage", "Markup" is modifying "Percentage", so it might be "Procentaj Markup" or something similar.↵ ↵ To make it natural in Romanian, I could say "Procentaj de markup (%)". But note that the glossary has "markup" in lowercase in the suggestions, like "limbaj markup".↵ ↵ Also, the original has "Markup" with a capital M, which might be part of a title or label, so I should preserve capitalization if possible.↵ ↵ The instruction says to | Details | |
|
Markup Percentage (%)
Warning: Lengths of source and translation differ too much.
Warning: Extra %s placeholder in translation.
First, the user is asking me to translate "Markup Percentage (%)" from English to Romanian. I am a professional translation engine, so I need to provide only the translated text.↵ ↵ Key instructions:↵ - Translate from English to Romanian.↵ - 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 provided glossary terms: "markup" should be translated as "markup" in Romanian, but with the note that it's an adjective. The glossary gives options like "marcap" or "tagat", but it says "markup" = "markup" (adjective) and suggests "limbaj markup" or "schemă (de) markup". However, in this context, "Markup Percentage" is a term, so I need to decide how to translate it.↵ ↵ The phrase is "Markup Percentage (%)". In English, "markup" here likely refers to the increase in price or cost, often in business or finance. But according to the glossary, "markup" should be kept as "markup" in Romanian, but it's noted as an adjective. The glossary says: "markup" = "markup" (adjective) [poate cu vremea... marcap | tagat ... :) limbaj markup, schemă (de) markup...]. This seems a bit confusing. It might be that in the context of WordPress plugins, "markup" is a technical term that should not be translated directly.↵ ↵ Looking at the glossary: it says "markup" = "markup" (adjective), and then gives some Romanian suggestions like "marcap" or "tagat", but with smileys and notes, which might indicate that these are playful or alternative translations. However, the instruction is to "Use these glossary terms", so I should follow the glossary.↵ ↵ The glossary specifies that "markup" should be translated as "markup" in Romanian, but it's in parentheses as an adjective. It also provides options like "limbaj markup" or "schemă (de) markup", which might be for different contexts. In this case, "Markup Percentage" might be a specific term.↵ ↵ I need to translate "Markup Percentage (%)". The word "Percentage" should be translated to Romanian as "Procentaj" or "Procent", but since it's followed by (%), it might be "Procentaj" or simply "Procent".↵ ↵ But to preserve the placeholders and variables, I should keep the (%) as is, since it's part of the text.↵ ↵ Let me break it down:↵ - "Markup" – according to glossary, keep as "markup" but in Romanian context. The glossary says "markup" = "markup" (adjective), so perhaps I should use "markup" as is, or adapt it.↵ - "Percentage" – translate to "Procentaj" or "Procent".↵ - The entire phrase: "Markup Percentage (%)"↵ ↵ In Romanian, a natural translation might be "Procentaj de Markup (%)" or "Procent de Markup (%)". But since the glossary says to use "markup" as "markup", I should probably keep "markup" untranslated.↵ ↵ The glossary says: "markup" = "markup" (adjective) [poate cu vremea... marcap | tagat ... :) limbaj markup, schemă (de) markup...]. This seems to suggest that "markup" can be translated in various ways, but for consistency, I should use "markup" as per the glossary.↵ ↵ Perhaps in this context, "Markup Percentage" is a technical term, so it might be best to keep "Markup" as is and translate "Percentage".↵ ↵ Let me think about common translations in business Romanian. "Markup" is often translated as "marjă de profit" or "adaos comercial", but the glossary specifically says to use "markup" as "markup".↵ ↵ Given the instruction to use the glossary terms, I should translate "markup" as "markup" in Romanian. But the glossary says it's an adjective, so in "Markup Percentage", "Markup" is modifying "Percentage", so it might be "Procentaj Markup" or something similar.↵ ↵ To make it natural in Romanian, I could say "Procentaj de markup (%)". But note that the glossary has "markup" in lowercase in the suggestions, like "limbaj markup".↵ ↵ Also, the original has "Markup" with a capital M, which might be part of a title or label, so I should preserve capitalization if possible.↵ ↵ The instruction says to
You have to log in to edit this translation.
|
|||
| 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. | Procentajul adaugă un % peste costul furnizorului. Fix adaugă o sumă fixă. Preț Fix ignoră costul furnizorului și percepe o sumă stabilită. | 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. Procentajul adaugă un % peste costul furnizorului. Fix adaugă o sumă fixă. Preț Fix ignoră costul furnizorului și percepe o sumă stabilită.
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. | Cum să calculezi prețul plătit de clienții tăi. Acesta este singurul loc unde se configurează prețurile. | Details | |
|
How to calculate the price your customers pay. This is the only place where pricing is configured. Cum să calculezi prețul plătit de clienții tăi. Acesta este singurul loc unde se configurează prețurile.
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. | First, the user has provided a text to translate from English to Romanian. 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 Romanian.↵ ↵ - 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 provided glossary terms: "create" = "crea" (verb) [creează, persoana a II-a singular, imperativ], "override" = "contramanda" (verb) [(contramandează/anulează o funcție sau funcționalitate implicită/automată); adjectiv: contramandat].↵ ↵ The glossary specifies:↵ ↵ - "create" should be translated as "crea" in the imperative second person singular form, which is "creează". But note: the glossary says "crea" (verb) [creează, persoana a II-a singular, imperativ]. So, in the translation, when "create" is used as a verb in the imperative, I should use "creează".↵ ↵ - "override" should be translated as "contramanda" as a verb. The glossary gives the form "contramandează" for the imperative or present tense. I need to use the appropriate form based on context.↵ ↵ Now, let's break down the original text:↵ ↵ 1. "Products with specific TLDs override catch-all products."↵ ↵ - "Products" = "Produsele" or "Produse" depending on context. Since it's a general statement, I'll use "Produsele" to indicate "the products".↵ ↵ - "with specific TLDs" = "cu TLD-uri specifice" (TLD stands for Top-Level Domain, and in Romanian, it's often kept as TLD or translated as "domenii de nivel superior", but since it's a technical term, I should preserve it as TLD. The text has "TLDs", so I'll use "TLD-uri").↵ ↵ - "override" = from glossary, "contramanda". In this context, it's a verb in present tense. So, "contramandează" or "contramandă". I'll use "contramandează" for natural flow.↵ ↵ - "catch-all products" = "produsele catch-all" or "produsele de tip catch-all". "Catch-all" is a technical term, so I might keep it as is or translate. In Romanian, it's often kept as "catch-all" in technical contexts. I'll use "produsele catch-all" for consistency.↵ ↵ So, part 1: "Produsele cu TLD-uri specifice contramandează produsele catch-all."↵ ↵ 2. "For example, a product with .io will be used for .io domains even if a catch-all product exists."↵ ↵ - "For example" = "De exemplu"↵ ↵ - "a product with .io" = "un produs cu .io" or "un produs pentru .io". Since .io is a TLD, I'll say "un produs pentru domeniile .io" to be clearer.↵ ↵ - "will be used" = "va fi utilizat" or "va fi folosit". I'll use "va fi utilizat" for a more formal tone.↵ ↵ - "for .io domains" = "pentru domeniile .io"↵ ↵ - "even if" = "chiar dacă"↵ ↵ - "a catch-all product exists" = "există un produs catch-all"↵ ↵ So, part 2: "De exemplu, un produs pentru domeniile .io va fi utilizat pentru domeniile .io chiar dacă există un produs catch-all."↵ ↵ 3. "You only need one catch-all product — do not create separate products for each TLD."↵ ↵ - "You only need" = "Aveți nevoie doar de" or "Vă trebuie doar". Since it's addressing the user, I'll use "Aveți nevoie doar de" for politeness.↵ ↵ - "one catch-all product" = "un produs catch-all"↵ ↵ - "— do not create" = from glossary, " | 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 Romanian. 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 Romanian.↵ ↵ - 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 provided glossary terms: "create" = "crea" (verb) [creează, persoana a II-a singular, imperativ], "override" = "contramanda" (verb) [(contramandează/anulează o funcție sau funcționalitate implicită/automată); adjectiv: contramandat].↵ ↵ The glossary specifies:↵ ↵ - "create" should be translated as "crea" in the imperative second person singular form, which is "creează". But note: the glossary says "crea" (verb) [creează, persoana a II-a singular, imperativ]. So, in the translation, when "create" is used as a verb in the imperative, I should use "creează".↵ ↵ - "override" should be translated as "contramanda" as a verb. The glossary gives the form "contramandează" for the imperative or present tense. I need to use the appropriate form based on context.↵ ↵ Now, let's break down the original text:↵ ↵ 1. "Products with specific TLDs override catch-all products."↵ ↵ - "Products" = "Produsele" or "Produse" depending on context. Since it's a general statement, I'll use "Produsele" to indicate "the products".↵ ↵ - "with specific TLDs" = "cu TLD-uri specifice" (TLD stands for Top-Level Domain, and in Romanian, it's often kept as TLD or translated as "domenii de nivel superior", but since it's a technical term, I should preserve it as TLD. The text has "TLDs", so I'll use "TLD-uri").↵ ↵ - "override" = from glossary, "contramanda". In this context, it's a verb in present tense. So, "contramandează" or "contramandă". I'll use "contramandează" for natural flow.↵ ↵ - "catch-all products" = "produsele catch-all" or "produsele de tip catch-all". "Catch-all" is a technical term, so I might keep it as is or translate. In Romanian, it's often kept as "catch-all" in technical contexts. I'll use "produsele catch-all" for consistency.↵ ↵ So, part 1: "Produsele cu TLD-uri specifice contramandează produsele catch-all."↵ ↵ 2. "For example, a product with .io will be used for .io domains even if a catch-all product exists."↵ ↵ - "For example" = "De exemplu"↵ ↵ - "a product with .io" = "un produs cu .io" or "un produs pentru .io". Since .io is a TLD, I'll say "un produs pentru domeniile .io" to be clearer.↵ ↵ - "will be used" = "va fi utilizat" or "va fi folosit". I'll use "va fi utilizat" for a more formal tone.↵ ↵ - "for .io domains" = "pentru domeniile .io"↵ ↵ - "even if" = "chiar dacă"↵ ↵ - "a catch-all product exists" = "există un produs catch-all"↵ ↵ So, part 2: "De exemplu, un produs pentru domeniile .io va fi utilizat pentru domeniile .io chiar dacă există un produs catch-all."↵ ↵ 3. "You only need one catch-all product — do not create separate products for each TLD."↵ ↵ - "You only need" = "Aveți nevoie doar de" or "Vă trebuie doar". Since it's addressing the user, I'll use "Aveți nevoie doar de" for politeness.↵ ↵ - "one catch-all product" = "un produs catch-all"↵ ↵ - "— do not create" = from glossary, "
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. | Limitează acest produs la anumite domenii de nivel superior. Lasă gol pentru a face acest produs universal care prețuiește orice domeniu de nivel superior neacoperit de alt produs. | 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. Limitează acest produs la anumite domenii de nivel superior. Lasă gol pentru a face acest produs universal care prețuiește orice domeniu de nivel superior neacoperit de alt produs.
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. | Fiecare furnizor are propriile sale tarife. Costul de bază este preluat de la furnizor, apoi se aplică marja dvs. de profit. | Details | |
|
Each provider has its own pricing. The base cost is fetched from the provider, then your markup is applied. Fiecare furnizor are propriile sale tarife. Costul de bază este preluat de la furnizor, apoi se aplică marja dvs. de profit.
You have to log in to edit this translation.
|
|||
| The domain registrar used to check availability and register domains sold through this product. | Registratorul de domenii folosit pentru a verifica disponibilitatea și a înregistra domeniile vândute prin acest produs. | Details | |
|
The domain registrar used to check availability and register domains sold through this product. Registratorul de domenii folosit pentru a verifica disponibilitatea și a înregistra domeniile vândute prin acest produs.
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. | Configurează înregistrarea domeniilor și prețurile pentru acest produs. Toate prețurile sunt controlate aici — prețul afișat clienților este calculat pe baza acestor setări. | Details | |
|
Configure domain registration and pricing for this product. All pricing is controlled here — the customer-facing price is calculated based on these settings. Configurează înregistrarea domeniilor și prețurile pentru acest produs. Toate prețurile sunt controlate aici — prețul afișat clienților este calculat pe baza acestor setări.
You have to log in to edit this translation.
|
|||
Export as