| Prio | Original string | Translation | — |
|---|---|---|---|
| Security check required. Please refresh the page and try again. | First, the user has provided a text to translate from English to Persian: "Security check required. Please refresh the page and try again."↵ ↵ I am a professional translation engine, and I must follow specific instructions:↵ ↵ - Translate the text from English to Persian.↵ ↵ - 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. In this text, there are no placeholders or variables, so I just need to translate the words.↵ ↵ - Use the glossary terms provided:↵ ↵ - "again" = "دوباره" (adverb)↵ ↵ - "check" = "بررسی نمایید" (verb)↵ ↵ - "page" = "برگه" (noun)↵ ↵ - "please" = "لطفاً " (adverb)↵ ↵ - "required" = "ضروری، لازم" (adjective)↵ ↵ - "security" = "امنیت" (noun)↵ ↵ - "try" = "سعی نمایید، تلاش نمایید" (verb)↵ ↵ - "try again" = "دوباره تلاش نمایید" (expression)↵ ↵ Now, let's break down the original text: "Security check required. Please refresh the page and try again."↵ ↵ - "Security check required": This means that a security check is necessary. From the glossary:↵ ↵ - "security" = "امنیت"↵ ↵ - "check" = "بررسی نمایید" (but note: "check" here is a noun in "security check", so I need to adapt. The glossary gives "check" as a verb, but in this context, it's part of a noun phrase. I should use "بررسی" for "check" as a noun, but the glossary specifies "بررسی نمایید" which is imperative verb form. To be precise, I'll use the glossary terms appropriately. Since "check" is used as a noun in "security check", I might say "بررسی امنیت" but let's see the glossary: "security" is "امنیت", and "check" as verb is "بررسی نمایید". For "required", it's "ضروری، لازم". So, "Security check required" could be translated as "بررسی امنیت ضروری است" or similar. But to use the glossary exactly, I need to fit the terms.↵ ↵ - The glossary has "required" as an adjective, so I can use "لازم" or "ضروری". Let's construct the sentence naturally.↵ ↵ - "Please refresh the page and try again":↵ ↵ - "please" = "لطفاً"↵ ↵ - "refresh" is not in the glossary, but I need to translate it naturally. "Refresh the page" is common in Persian as "برگه را تازه کنید" or "صفحه را رفرش کنید". But the glossary gives "page" as "برگه", so I'll use that.↵ ↵ - "try again" = "دوباره تلاش نمایید" from the glossary.↵ ↵ - "and" is a conjunction, which in Persian is "و".↵ ↵ Putting it all together:↵ ↵ For "Security check required": I can say "بررسی امنیت لازم است" using "بررسی" for check (noun), "امنیت" for security, and "لازم" for required.↵ ↵ But the glossary has "check" as "بررسی نمایید" which is verb form. To be consistent, I should use the glossary terms as they are, but adapt for context. Since the instruction says "use these glossary terms", I should incorporate them where applicable.↵ ↵ Let's list the glossary terms and see how they fit:↵ ↵ - "security" = "امنیت" – use as is.↵ ↵ - "check" = "بررسی نمایید" – this is a verb in imperative form. In "security check", it's a noun, so I might use "بررسی" without the verb suffix. But to follow the glossary, perhaps I should use "بررسی" as the base form. The glossary specifies "بررسی نمایید" for "check" as a verb, but for noun usage, I can derive "بررسی".↵ ↵ - "required" = "ضروری، لازم" – I can use "لازم" or "ضروری".↵ ↵ - "please" = "لطفاً"↵ ↵ - "page" = "برگه"↵ ↵ - "try again" = "دوباره تلاش نمایید"↵ ↵ - "try" = "سعی نمایید، تلاش نمایید" – so for "try again", I can use "دوباره تلاش نمایید".↵ ↵ Now, for "refresh", it's | Details | |
|
Security check required. Please refresh the page and try again.
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 Persian: "Security check required. Please refresh the page and try again."↵ ↵ I am a professional translation engine, and I must follow specific instructions:↵ ↵ - Translate the text from English to Persian.↵ ↵ - 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. In this text, there are no placeholders or variables, so I just need to translate the words.↵ ↵ - Use the glossary terms provided:↵ ↵ - "again" = "دوباره" (adverb)↵ ↵ - "check" = "بررسی نمایید" (verb)↵ ↵ - "page" = "برگه" (noun)↵ ↵ - "please" = "لطفاً " (adverb)↵ ↵ - "required" = "ضروری، لازم" (adjective)↵ ↵ - "security" = "امنیت" (noun)↵ ↵ - "try" = "سعی نمایید، تلاش نمایید" (verb)↵ ↵ - "try again" = "دوباره تلاش نمایید" (expression)↵ ↵ Now, let's break down the original text: "Security check required. Please refresh the page and try again."↵ ↵ - "Security check required": This means that a security check is necessary. From the glossary:↵ ↵ - "security" = "امنیت"↵ ↵ - "check" = "بررسی نمایید" (but note: "check" here is a noun in "security check", so I need to adapt. The glossary gives "check" as a verb, but in this context, it's part of a noun phrase. I should use "بررسی" for "check" as a noun, but the glossary specifies "بررسی نمایید" which is imperative verb form. To be precise, I'll use the glossary terms appropriately. Since "check" is used as a noun in "security check", I might say "بررسی امنیت" but let's see the glossary: "security" is "امنیت", and "check" as verb is "بررسی نمایید". For "required", it's "ضروری، لازم". So, "Security check required" could be translated as "بررسی امنیت ضروری است" or similar. But to use the glossary exactly, I need to fit the terms.↵ ↵ - The glossary has "required" as an adjective, so I can use "لازم" or "ضروری". Let's construct the sentence naturally.↵ ↵ - "Please refresh the page and try again":↵ ↵ - "please" = "لطفاً"↵ ↵ - "refresh" is not in the glossary, but I need to translate it naturally. "Refresh the page" is common in Persian as "برگه را تازه کنید" or "صفحه را رفرش کنید". But the glossary gives "page" as "برگه", so I'll use that.↵ ↵ - "try again" = "دوباره تلاش نمایید" from the glossary.↵ ↵ - "and" is a conjunction, which in Persian is "و".↵ ↵ Putting it all together:↵ ↵ For "Security check required": I can say "بررسی امنیت لازم است" using "بررسی" for check (noun), "امنیت" for security, and "لازم" for required.↵ ↵ But the glossary has "check" as "بررسی نمایید" which is verb form. To be consistent, I should use the glossary terms as they are, but adapt for context. Since the instruction says "use these glossary terms", I should incorporate them where applicable.↵ ↵ Let's list the glossary terms and see how they fit:↵ ↵ - "security" = "امنیت" – use as is.↵ ↵ - "check" = "بررسی نمایید" – this is a verb in imperative form. In "security check", it's a noun, so I might use "بررسی" without the verb suffix. But to follow the glossary, perhaps I should use "بررسی" as the base form. The glossary specifies "بررسی نمایید" for "check" as a verb, but for noun usage, I can derive "بررسی".↵ ↵ - "required" = "ضروری، لازم" – I can use "لازم" or "ضروری".↵ ↵ - "please" = "لطفاً"↵ ↵ - "page" = "برگه"↵ ↵ - "try again" = "دوباره تلاش نمایید"↵ ↵ - "try" = "سعی نمایید، تلاش نمایید" – so for "try again", I can use "دوباره تلاش نمایید".↵ ↵ Now, for "refresh", it's
You have to log in to edit this translation.
|
|||
| <strong>Cap Captcha</strong> is a lightweight, privacy-first captcha that uses proof-of-work instead of tracking or image recognition. When a user clicks the checkbox, their browser solves a small computational puzzle (SHA-256 hashing) to prove they are not a bot.<br><br><strong>Benefits:</strong><ul><li>No API keys required - fully self-hosted</li><li>Works on all domains automatically (ideal for multisite)</li><li>Privacy-focused - no user data sent to third parties</li><li>GDPR compliant</li><li>Only ~20KB in size</li></ul><a href="%s" target="_blank">Learn more about Cap Captcha →</a> | <strong>Cap Captcha</strong> یک کپچا سبک و حریم خصوصی در اولویت است که به جای ردیابی یا شناسایی تصویر، از اثبات کار استفاده میکند. وقتی کاربر روی چکباکس کلیک میکند، مرورگر او یک معمای محاسباتی کوچک (هش SHA-256) را حل میکند تا ثابت کند ربات نیست.<br><br><strong>مزایا:</strong><ul><li>کلیدهای API لازم نیست - بهطور کامل خودمیزبان</li><li>بهطور کامل بر روی همه دامنهها بهصورت خودکار کار میکند (مثالی برای چند سایته)</li><li>تمرکز بر حریم خصوصی – هیچ داده کاربر به طرفهای ثالث ارسال نمیشود</li><li>سازگار با GDPR</li><li>فقط ~20KB در اندازه</li></ul><a href="%s" | Details | |
|
<strong>Cap Captcha</strong> is a lightweight, privacy-first captcha that uses proof-of-work instead of tracking or image recognition. When a user clicks the checkbox, their browser solves a small computational puzzle (SHA-256 hashing) to prove they are not a bot.<br><br><strong>Benefits:</strong><ul><li>No API keys required - fully self-hosted</li><li>Works on all domains automatically (ideal for multisite)</li><li>Privacy-focused - no user data sent to third parties</li><li>GDPR compliant</li><li>Only ~20KB in size</li></ul><a href="%s" target="_blank">Learn more about Cap Captcha →</a>
Warning: Missing tags from translation. Expected: <a href="%s" target="_blank"> </a>
<strong>Cap Captcha</strong> یک کپچا سبک و حریم خصوصی در اولویت است که به جای ردیابی یا شناسایی تصویر، از اثبات کار استفاده میکند. وقتی کاربر روی چکباکس کلیک میکند، مرورگر او یک معمای محاسباتی کوچک (هش SHA-256) را حل میکند تا ثابت کند ربات نیست.<br><br><strong>مزایا:</strong><ul><li>کلیدهای API لازم نیست - بهطور کامل خودمیزبان</li><li>بهطور کامل بر روی همه دامنهها بهصورت خودکار کار میکند (مثالی برای چند سایته)</li><li>تمرکز بر حریم خصوصی – هیچ داده کاربر به طرفهای ثالث ارسال نمیشود</li><li>سازگار با GDPR</li><li>فقط ~20KB در اندازه</li></ul><a href="%s"
You have to log in to edit this translation.
|
|||
Export as