| Prio | Original string | 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 Tagalog. The text is: "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 must follow specific instructions:↵ ↵ - Translate the text from English to Tagalog.↵ ↵ - 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: "all" = "lahat" (adjective).↵ ↵ Now, let's break down the original text:↵ ↵ 1. "Limit this product to specific TLDs." – This means to restrict the product to certain top-level domains (like .com, .net, etc.).↵ ↵ 2. "Leave empty to make this a catch-all product that prices any TLD not covered by another product." – This means if you leave the field empty, this product will apply to all TLDs that aren't already priced by other products. "Catch-all" here means it covers everything else.↵ ↵ Key terms to note:↵ ↵ - "TLDs" – This is an acronym for Top-Level Domains. In translation, I should keep it as is or translate if appropriate, but since it's a technical term, it might be best to leave it as TLDs or explain in context. However, the instruction says to preserve variables and placeholders, so I should keep "TLDs" as is unless it's a placeholder.↵ ↵ - "catch-all" – This needs to be translated. The glossary says "all" = "lahat", so "catch-all" might be translated as "saklaw-lahat" or something similar, but I need to use natural Tagalog.↵ ↵ - The glossary term: "all" = "lahat" (adjective). So wherever "all" appears, I should use "lahat".↵ ↵ Now, translating sentence by sentence:↵ ↵ First sentence: "Limit this product to specific TLDs."↵ ↵ - "Limit" can be translated as "Limitahan" or "I-limit", but since it's a command in context, I'll use "Limitahan".↵ ↵ - "this product" – "ang produktong ito" or "ang produkto na ito".↵ ↵ - "to specific TLDs" – "sa mga tiyak na TLD" or "sa partikular na mga TLD".↵ ↵ So, a natural translation: "Limitahan ang produktong ito sa mga tiyak na TLD."↵ ↵ Second sentence: "Leave empty to make this a catch-all product that prices any TLD not covered by another product."↵ ↵ - "Leave empty" – In context, it means leave the field empty. Translate as "Iwanang blangko" or "Iwanang walang laman".↵ ↵ - "to make this a catch-all product" – "upang gawin itong isang catch-all na produkto". But since "catch-all" needs to be translated, and "all" is "lahat", I can say "saklaw-lahat" or "pang-lahat". "Catch-all" in this context means covering all others, so "pang-sakop ng lahat" or something similar.↵ ↵ - "that prices any TLD" – "na nagpe-presyo ng anumang TLD" or "na nagtatalaga ng presyo sa anumang TLD".↵ ↵ - "not covered by another product" – "na hindi sakop ng ibang produkto".↵ ↵ Putting it together: "Iwanang blangko upang gawin itong isang produktong saklaw-lahat na nagpe-presyo ng anumang TLD na hindi sakop ng ibang produkto."↵ ↵ But to make it more natural, I can adjust: "Iwanang blangko upang maging isang produktong pang-lahat na nagtatalaga ng presyo sa anumang TLD na hindi sakop ng iba pang produkto."↵ ↵ Using the glossary: "all" = "lahat", so for "catch-all", I can use "pang-lahat" which means "for all".↵ ↵ Now, combine both sentences with proper punctuation. The original has a period at the end of the first sentence, so I should preserve that.↵ ↵ Final translation: "Limitahan ang produktong ito sa mga tiyak na TLD. Iwanang blangko upang gawin itong isang produktong pang-lahat na nagpe-presyo ng anumang TLD na hindi sakop ng ibang produkto."↵ ↵ I need to ensure that "TLDs" is preserved as is, since it's a technical term and not a placeholder. | 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 Tagalog. The text is: "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 must follow specific instructions:↵ ↵ - Translate the text from English to Tagalog.↵ ↵ - 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: "all" = "lahat" (adjective).↵ ↵ Now, let's break down the original text:↵ ↵ 1. "Limit this product to specific TLDs." – This means to restrict the product to certain top-level domains (like .com, .net, etc.).↵ ↵ 2. "Leave empty to make this a catch-all product that prices any TLD not covered by another product." – This means if you leave the field empty, this product will apply to all TLDs that aren't already priced by other products. "Catch-all" here means it covers everything else.↵ ↵ Key terms to note:↵ ↵ - "TLDs" – This is an acronym for Top-Level Domains. In translation, I should keep it as is or translate if appropriate, but since it's a technical term, it might be best to leave it as TLDs or explain in context. However, the instruction says to preserve variables and placeholders, so I should keep "TLDs" as is unless it's a placeholder.↵ ↵ - "catch-all" – This needs to be translated. The glossary says "all" = "lahat", so "catch-all" might be translated as "saklaw-lahat" or something similar, but I need to use natural Tagalog.↵ ↵ - The glossary term: "all" = "lahat" (adjective). So wherever "all" appears, I should use "lahat".↵ ↵ Now, translating sentence by sentence:↵ ↵ First sentence: "Limit this product to specific TLDs."↵ ↵ - "Limit" can be translated as "Limitahan" or "I-limit", but since it's a command in context, I'll use "Limitahan".↵ ↵ - "this product" – "ang produktong ito" or "ang produkto na ito".↵ ↵ - "to specific TLDs" – "sa mga tiyak na TLD" or "sa partikular na mga TLD".↵ ↵ So, a natural translation: "Limitahan ang produktong ito sa mga tiyak na TLD."↵ ↵ Second sentence: "Leave empty to make this a catch-all product that prices any TLD not covered by another product."↵ ↵ - "Leave empty" – In context, it means leave the field empty. Translate as "Iwanang blangko" or "Iwanang walang laman".↵ ↵ - "to make this a catch-all product" – "upang gawin itong isang catch-all na produkto". But since "catch-all" needs to be translated, and "all" is "lahat", I can say "saklaw-lahat" or "pang-lahat". "Catch-all" in this context means covering all others, so "pang-sakop ng lahat" or something similar.↵ ↵ - "that prices any TLD" – "na nagpe-presyo ng anumang TLD" or "na nagtatalaga ng presyo sa anumang TLD".↵ ↵ - "not covered by another product" – "na hindi sakop ng ibang produkto".↵ ↵ Putting it together: "Iwanang blangko upang gawin itong isang produktong saklaw-lahat na nagpe-presyo ng anumang TLD na hindi sakop ng ibang produkto."↵ ↵ But to make it more natural, I can adjust: "Iwanang blangko upang maging isang produktong pang-lahat na nagtatalaga ng presyo sa anumang TLD na hindi sakop ng iba pang produkto."↵ ↵ Using the glossary: "all" = "lahat", so for "catch-all", I can use "pang-lahat" which means "for all".↵ ↵ Now, combine both sentences with proper punctuation. The original has a period at the end of the first sentence, so I should preserve that.↵ ↵ Final translation: "Limitahan ang produktong ito sa mga tiyak na TLD. Iwanang blangko upang gawin itong isang produktong pang-lahat na nagpe-presyo ng anumang TLD na hindi sakop ng ibang produkto."↵ ↵ I need to ensure that "TLDs" is preserved as is, since it's a technical term and not a placeholder.
You have to log in to edit this translation.
|
|||
| All Options (subdomain, register, existing) | lahat ng mga pagpipilian (subdomain, register, existing) | Details | |
|
All Options (subdomain, register, existing)
Warning: The translation appears to be missing the initial uppercase.
lahat ng mga pagpipilian (subdomain, register, existing)
You have to log in to edit this translation.
|
|||
| Nameservers | mga server ng pangalan | Details | |
|
Nameservers
Warning: The translation appears to be missing the initial uppercase.
mga server ng pangalan
You have to log in to edit this translation.
|
|||
| All TLDs | lahat ng TLDs | Details | |
|
All TLDs
Warning: The translation appears to be missing the initial uppercase.
lahat ng TLDs
You have to log in to edit this translation.
|
|||
|
|
Details | |
|
Singular: %d taon
You have to log in to edit this translation.
Plural: %d taon
You have to log in to edit this translation.
|
|||
| first year | unang taon | Details | |
|
first year
Warning: The translation appears to be missing 1 space at the beginning.
unang taon
You have to log in to edit this translation.
|
|||
| Renews at | Nag-renew sa | Details | |
|
Renews at
Warning: The translation appears to be missing 1 space at the end.
Nag-renew sa
You have to log in to edit this translation.
|
|||
| Status | estado | Details | |
|
Status
Warning: The translation appears to be missing the initial uppercase.
estado
You have to log in to edit this translation.
|
|||
| Invalid customer session | walang bisa na sesyon ng customer | Details | |
|
Invalid customer session
Warning: The translation appears to be missing the initial uppercase.
walang bisa na sesyon ng customer
You have to log in to edit this translation.
|
|||
| Invalid request parameters | walang bisa na mga parameter ng kahilingan | Details | |
|
Invalid request parameters
Warning: The translation appears to be missing the initial uppercase.
walang bisa na mga parameter ng kahilingan
You have to log in to edit this translation.
|
|||
| Invalid IPv4 address | walang bisa na IPv4 address | Details | |
|
Invalid IPv4 address
Warning: The translation appears to be missing the initial uppercase.
walang bisa na IPv4 address
You have to log in to edit this translation.
|
|||
| Invalid IPv6 address | walang bisa na IPv6 address | Details | |
|
Invalid IPv6 address
Warning: The translation appears to be missing the initial uppercase.
walang bisa na IPv6 address
You have to log in to edit this translation.
|
|||
| Invalid provider selected | walang bisa na provider ang napili | Details | |
|
Invalid provider selected
Warning: The translation appears to be missing the initial uppercase.
walang bisa na provider ang napili
You have to log in to edit this translation.
|
|||
| Invalid customer | walang bisa na customer | Details | |
|
Invalid customer
Warning: The translation appears to be missing the initial uppercase.
walang bisa na customer
You have to log in to edit this translation.
|
|||
|
|
Details | |
|
Singular: %d na paglipat ng domain ay nabigo kamakailan.
You have to log in to edit this translation.
Plural: %d na mga paglipat ng domain ay nabigo kamakailan.
You have to log in to edit this translation.
|
|||
Export as