PTE Request for Prevent Browser…


PTE Request for Prevent Browser Caching (es_AR, es_CL, es_CO, es_EC, es_MX, es_VE, ca)

Hi Polyglots,

I’m the author of Prevent Browser Caching:

  • https://wordpress.org/plugins/prevent-browser-caching/

I’ve just submitted translations of the plugin’s UI (all 86 strings) and the current readme as suggestions for seven locales, and I’d be grateful if each team could review them. The existing Ukrainian and Spanish (es_ES) translations of this plugin are already approved and live, and I maintain them after every release.

I’m not a native speaker of these locales, so I did not machine-translate. For the Spanish variants I started from the approved es_ES translation and then checked every difference against that locale’s own conventions as they actually appear in your WordPress core translation and in this plugin’s already-approved strings. Catalan is a fresh translation, not adapted from Spanish. What that meant per locale:

Spanish (Argentina) — es_AR: voseo throughout (agregá, verificá, hacé clic, podés, tenés), agregar rather than añadir, Predeterminado, ” ” quotation marks.
Spanish (Chile) — es_CL: agregar, Predeterminado, ” ” quotation marks.
Spanish (Colombia) — es_CO: Predeterminado, « » quotation marks, existing approved strings reused verbatim.
Spanish (Ecuador) — es_EC: your glossary is currently empty, so I followed the es_ES glossary plus your core translation; « » quotation marks.
Spanish (Mexico) — es_MX: Predeterminado, straight quotation marks (matching your core translation and this plugin’s existing strings).
Spanish (Venezuela) — es_VE: « » quotation marks, existing approved strings reused verbatim.
Catalan — ca: formal plural register (Afegiu, Comproveu, Espereu), memòria cau, extensió, imperative singular on buttons, « » quotation marks.
Across all the LatAm variants I also used celular rather than móvil, and replaced pulsar with hacer clic. Existing approved strings were reused as-is everywhere.

Corrections are very welcome — please treat my suggestions as a starting point. If they’re up to standard, I’d be grateful for PTE access for this project so I can keep these translations current after each release (every release adds a few strings, and a locale that falls below 90% stops getting language-pack updates). If a team would rather simply review and approve the waiting suggestions instead of granting PTE, that’s completely fine.

Project: https://translate.wordpress.org/projects/wp-plugins/prevent-browser-caching/
Locales:
— es_AR
— es_CL

— es_VE

My WordPress.org username: kostyatereshchuk

One thing to flag: an older community import left a corrupted character in an approved string — Visita Plugins > Añadir nuevo» contains a CJK ideograph (U+2A85E) where the opening « should be. It renders that way on the localized plugin page today. My suggestion for that string fixes it, but since suggestions don’t overwrite approved strings, it needs an editor to accept it. (Affects es_CO, es_CL, es_EC and es_VE.)

Thank you for your time and for maintaining these locales.

#editor-requests