GlotPress

<strong>Cap Captcha</strong> is een lichtgewicht, privacy‑eerste captcha die proof‑of‑work gebruikt in plaats van volgen of afbeelding herkenning. Wanneer een gebruiker het selectievakje aanklikt, lost hun browser een klein rekenpuzzel (SHA‑256 hashing) op om te bewijzen dat ze geen bot zijn. <strong>Voordelen:</strong> <ul> <li>Geen API sleutels vereist - volledig zelf gehost</li> <li>Werkt automatisch op alle domeinen (ideaal voor multisite)</li> <li>Privacy‑gericht - geen gebruikersgegevens verzonden naar derden</li> <li>GDPR conform</li> <li>Alleen ~20KB groot</li> </ul> <a href="%s" target="_blank">Leer meer over Cap Captcha &rarr;</a>

We are translating from English to Dutch.↵ The given text is: "Protect the WordPress password reset form."↵ We are to translate this text, using the provided glossary terms.↵ Glossary:↵ "password" = "wachtwoord" (noun)↵ "reset" = "reset" (verb)↵ "WordPress" = "WordPress" (noun) [Grote W en P]↵ ↵ The sentence structure in Dutch might be: "Bescherm het WordPress-wachtwoord resetformulier."↵ However, note that "reset" is given as a verb in the glossary, but here it is used as part of a compound noun.↵ In Dutch, we might use "resetformulier" or "formulier voor het resetten van wachtwoorden".↵ But the instruction says to use the glossary terms exactly as given, and "reset" is given as a verb.↵ ↵ Alternatively, we can use the verb form in a phrase: "Bescherm het WordPress-formulier voor het resetten van wachtwoorden."↵ ↵ However, the original is a concise phrase, and we want to keep it as natural as possible.↵ ↵ Let's consider common Dutch usage:↵ "password reset form" is often translated as "wachtwoord reset formulier" or "formulier om het wachtwoord te resetten".↵ ↵ But note: the glossary says "reset" is a verb, so we might use the infinitive in a compound.↵ ↵ However, in Dutch, it is common to use English terms in IT contexts, so "resetformulier" might be acceptable.↵ ↵ Since the instruction says to use natural language and preserve the meaning, and we have the glossary, we can try:↵ ↵ "Bescherm het WordPress wachtwoord resetformulier."↵ ↵ But wait, the glossary says "WordPress" should be written with capital W and P, so that's preserved.↵ ↵ Alternatively, we can write: "Bescherm het WordPress-formulier voor het resetten van wachtwoorden."↵ ↵ However, the original is a short imperative sentence. Let's see which one is more natural.↵ ↵ Since the instruction says to use the glossary terms exactly, we must use "wachtwoord" and "reset" and "WordPress".↵ ↵ But note: "reset" in the glossary is a verb, so if we use it as a noun in a compound, it might be acceptable to use the English term.↵ ↵ In Dutch, it is common to use the English word "reset" in such contexts.↵ ↵ Let me check: the original phrase is "password reset form", which in Dutch is often "wachtwoord reset formulier" or "wachtwoordresetformulier".↵ ↵ Since the instruction says to use natural language, I think we can go with:↵ ↵ "Bescherm het WordPress wachtwoord resetformulier."↵ ↵ But to be more precise and use the verb form, we can say:↵ ↵ "Bescherm het WordPress-formulier voor het resetten van wachtwoorden."↵ ↵ However, the original does not have "voor het" and "van", so it's a bit longer.↵ ↵ Considering the instruction to be concise and to preserve the structure, I think the first option is acceptable.↵ ↵ But note: the original says "WordPress password reset form", which is a compound noun. In Dutch, we might write it as one word or with hyphens.↵ ↵ Since "WordPress" is a trademark and we are to preserve it, we can write:↵ ↵ "Bescherm het WordPress-wachtwoordresetformulier."↵ ↵ However, that might be a bit long and not commonly written as one word.↵ ↵ Alternatively, we can use:↵ ↵ "Bescherm het WordPress wachtwoordresetformulier."↵ ↵ But in Dutch, we often hyphenate compound nouns when they are made of multiple words, especially with English terms.↵ ↵ Let me think about the most natural way:↵ ↵ "Bescherm het WordPress-wachtwoord-resetformulier."↵ ↵ That might be over-hyphenated.↵ ↵ Since the instruction says to use natural language, I think the most common way in Dutch would be to use the English term for "reset" in this context.↵ ↵ I will go with:↵ ↵ "Bescherm het WordPress wachtwoord resetformulier."↵ ↵ But wait, the glossary says "reset" is a verb, so maybe we should use the Dutch verb form in the compound? However, the glossary does not specify a noun form.↵ ↵ Alternatively, we can avoid the compound and say:↵ ↵ "Bescherm het formulier voor het resetten van het WordPress-wachtwoord."↵ ↵ But that changes the structure a bit.↵ ↵ Since the instruction is to translate the text and use the glossary terms, and the original is a short imperative, I think we can keep it short.↵ ↵ Let's look at the glossary again: ↵ "password" = "wachtwoord"↵ "reset" = "reset" (verb)↵ "WordPress" = "WordPress"↵ ↵ So, if we

We are translating from English to Dutch.↵ The given text is: "Protect WooCommerce forms."↵ We are to translate this into Dutch, preserving any terms like "WooCommerce" as per the glossary.↵ According to the glossary, "WooCommerce" should remain "WooCommerce" (with capital W and C).↵ So, we translate "Protect" to Dutch and keep "WooCommerce forms" as is, but note that "forms" will be translated.↵ However, note that the instruction says to preserve variables and placeholders, but there are none in this string.↵ We are to return ONLY the translated text.↵ ↵ Translation: "Protect" can be translated as "Bescherm" (imperative) or "Beschermen" (infinitive). Since the original is in the imperative (command) form, we use the imperative in Dutch: "Bescherm".↵ "WooCommerce forms" -> "WooCommerce-formulieren" (since "forms" is plural, we use the plural "formulieren").↵ ↵ However, note that the original might be a title or a short instruction. We'll use the imperative.↵ ↵ So, the translation: "Bescherm WooCommerce-formulieren."↵ ↵ But note: the glossary says to use "WooCommerce" as is, so we don't translate that part. We only translate "forms" to "formulieren".↵ ↵ However, the original does not have a hyphen, but in Dutch, we often use a hyphen in compound nouns when the first part is a brand name. It is acceptable to write "WooCommerce formulieren" without a hyphen, but using a hyphen is more common in Dutch for clarity.↵ ↵ Since the instruction says to use natural language, we can choose the form that is most natural. In Dutch, it is common to use a hyphen in such cases.↵ ↵ Alternatively, we could write it as "WooCommerce formulieren" without a hyphen, but that might be less clear.↵ ↵ Let's check: The glossary only specifies the term "WooCommerce" itself, not how to combine it with other words. So we are free to use the natural Dutch way.↵ ↵ However, note that the original English does not use a hyphen, so we might want to keep the same structure. But in Dutch, compound nouns are often written as one word or with a hyphen.↵ ↵ Since "WooCommerce" is a brand name and we are combining it with a common noun, it is recommended to use a hyphen.↵ ↵ Therefore, I will go with: "Bescherm WooCommerce-formulieren."↵ ↵ But wait, the original is a short phrase, likely used as a button or label. In Dutch, we might also use the infinitive form for such labels, like "WooCommerce-formulieren beschermen". However, the original is in the imperative, so we stick to the imperative.↵ ↵ Let's confirm: The original says "Protect WooCommerce forms." which is an instruction. In Dutch, we can use the imperative for instructions.↵ ↵ So, I think "Bescherm WooCommerce-formulieren." is correct.↵ ↵ However, note that the instruction says to preserve punctuation. The original has a period at the end? Actually, the original does not have a period. It is just a phrase. So we should not add a period if the original doesn't have one.↵ ↵ The original text: "Protect WooCommerce forms." does not have a period? Actually, in the prompt it is written without a period. So we should not add one.↵ ↵ Correction: The original is "Protect WooCommerce forms." (without a period). So we output without a period.↵ ↵ Therefore: "Bescherm WooCommerce-formulieren"↵ ↵ But note: the original might be a title or a button, so no period is common.↵ ↵ Let's write it without the period.↵ ↵ However, in Dutch, we might also use the infinitive form for such labels, but the instruction says to translate the text. Since the original is in the imperative, we use the imperative.↵ ↵ Final translation: "Bescherm WooCommerce-formulieren"↵ ↵ But wait, the glossary says to preserve the term "WooCommerce" exactly, which we are doing. And we are translating the rest.↵ ↵ Alternatively, if the context is a button or a menu item, sometimes Dutch uses the infinitive. But the instruction does not specify context, so we stick to the given text.↵ ↵ Since the instruction says to translate the text, we do so.↵ ↵ However, note that the original is a short phrase. In Dutch, short instructions are often in the imperative.↵ ↵ So, I think this is correct.↵ ↵ Let's consider: "Protect" -> "Bescherm", "WooCommerce" -> "WooCommerce", "forms" -> "formulieren".↵ ↵ We combine them: "Bescherm WooCommerce-formulieren"↵ ↵ We are using a hyphen because in Dutch,