PTC accessibility-checker (1985): Automatic Translations June 25, 2025 18:06:03788851 - #1038
PTC accessibility-checker (1985): Automatic Translations June 25, 2025 18:06:03788851#1038SteveJonesDev wants to merge 33 commits into
Conversation
…5 18:06:03788851 - Hebrew
…5 18:06:03788851 - Spanish (Spain)
…5 18:06:03788851 - Arabic
…5 18:06:03788851 - Romanian
…5 18:06:03788851 - German (Germany)
…5 18:06:03788851 - Chinese (Simplified)
…5 18:06:03788851 - Italian
…5 18:06:03788851 - French (France)
…5 18:06:03788851 - Polish
…5 18:06:03788851 - Portuguese (Portugal)
…5 18:06:03788851 - Thai
…5 18:06:03788851 - Dutch
…5 18:06:03788851 - Swedish
…5 18:06:03788851 - Greek
…5 18:06:03788851 - Japanese
…5 18:06:03788851 - Portuguese (Brazil)
…5 18:06:03788851 - Vietnamese
…5 18:06:03788851 - Korean
…5 18:06:03788851 - Danish
…5 18:06:03788851 - Norwegian (Bokmål)
…5 18:06:03788851 - Bulgarian
…5 18:06:03788851 - Czech
…5 18:06:03788851 - Estonian
…5 18:06:03788851 - Finnish
…5 18:06:03788851 - Hungarian
…5 18:06:03788851 - Indonesian
…5 18:06:03788851 - Lithuanian
…5 18:06:03788851 - Latvian
…5 18:06:03788851 - Slovak
…5 18:06:03788851 - Slovenian
…5 18:06:03788851 - Turkish
…5 18:06:03788851 - Ukrainian
…5 18:06:03788851 - Russian
WalkthroughThis update revises the Estonian translation file for the accessibility checker, enhancing phrasing, clarity, and consistency across user interface labels, messages, and instructional texts. The changes focus solely on translation improvements, with no modifications to program logic, exported entities, or control flow. Changes
Sequence Diagram(s)No sequence diagram generated, as the changes are limited to translation strings and do not affect control flow or feature logic. Possibly related PRs
Poem
🪧 TipsChatThere are 3 ways to chat with CodeRabbit:
SupportNeed help? Create a ticket on our support page for assistance with any issues or questions. Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments. CodeRabbit Commands (Invoked using PR comments)
Other keywords and placeholders
CodeRabbit Configuration File (
|
![gemini-code-assist[bot]](https://avatars.githubusercontent.com/in/956858?s=60&v=4){kind=small}
There was a problem hiding this comment.
Summary of Changes
Hello @SteveJonesDev, I'm Gemini Code Assist1! I'm currently reviewing this pull request and will post my feedback shortly. In the meantime, here's a summary to help you and other reviewers quickly get up to speed!
This pull request focuses on updating the Estonian language translation file for the accessibility-checker plugin. The changes, generated automatically, aim to improve the linguistic quality and consistency of the localized user interface, making the plugin more accessible and user-friendly for Estonian speakers.
Highlights
- Automated Translation Update: This pull request delivers an automated update to the Estonian language (
et.po) translation file for theaccessibility-checkerplugin, ensuring the latest strings are available and accurate. - Grammatical and Stylistic Improvements: Numerous
msgstrentries have been refined to enhance grammatical correctness, natural phrasing, and overall readability of various user interface strings and messages in Estonian. - Translation Consistency Adjustments: The translation strategy for certain terms has been adjusted; for instance, 'Accessibility Checker' is now often translated to 'Ligipääsetavuse kontrollija' or 'Juurdepääsetavuse kontroll', while some English terms like 'Frontend Accessibility Checker' are retained or included in parentheses for clarity.
Using Gemini Code Assist
The full guide for Gemini Code Assist can be found on our documentation page, here are some quick tips.
Invoking Gemini
You can request assistance from Gemini at any point in your pull request via creating an issue comment (i.e. comment on the pull request page) using either /gemini <command> or @gemini-code-assist <command>. Below is a summary of the supported commands.
| Feature | Command | Description |
|---|---|---|
| Code Review | /gemini review |
Performs a code review for the current pull request in its current state. |
| Pull Request Summary | /gemini summary |
Provides a summary of the current pull request in its current state. |
| Comment | @gemini-code-assist | Responds in comments when explicitly tagged, both in issue comments and review comments. |
| Help | /gemini help |
Displays a list of available commands. |
Customization
To customize Gemini Code Assist for GitHub experience, repository maintainers can create a configuration file and/or provide a custom code review style guide (such as PEP-8 for Python) by creating and adding files to a .gemini/ folder in the base of the repository. Detailed instructions can be found here.
Limitations & Feedback
Gemini Code Assist is currently in preview and may make mistakes. Please leave feedback on any instances where its feedback is incorrect or counter productive. You can react with 👍 and 👎 on @gemini-code-assist comments to provide feedback.
You can also get AI-powered code generation, chat, as well as code reviews directly in the IDE at no cost with the Gemini Code Assist IDE Extension.
Footnotes
-
Review the Privacy Notices, Generative AI Prohibited Use Policy, Terms of Service, and learn how to configure Gemini Code Assist in GitHub here. Gemini can make mistakes, so double check it and use code with caution. ↩
There was a problem hiding this comment.
Code Review
The pull request primarily updates Estonian translations in the languages/accessibility-checker-et.po file. While many changes improve the clarity, precision, and grammatical correctness of the Estonian phrases, some introduce inconsistencies in localization strategy and tone. Specifically, certain terms are reverted from Estonian translations back to English, and there's an inconsistent shift from a formal to an informal tone in user-facing messages. Addressing these inconsistencies will enhance the overall quality and professionalism of the localized user experience.
| #: admin/class-widgets.php:67 | ||
| msgid "Upgrade Accessibility Checker" | ||
| msgstr "Uuenda Accessibility Checkerit" | ||
| msgstr "Upgrade Accessibility Checker (juurdepääsetavuse kontrollija)" |
There was a problem hiding this comment.
The msgstr entry should contain the full translation of the msgid. Including the English phrase "Upgrade Accessibility Checker" directly in the translated string (msgstr) defeats the purpose of localization. The previous translation was more appropriate. Please provide a complete Estonian translation for the entire phrase.
msgstr "Uuenda Accessibility Checkerit"
| #: includes/options-page.php:120 | ||
| msgid "Frontend Accessibility Checker" | ||
| msgstr "Kasutajaliidese Accessibility Checker" | ||
| msgstr "Frontend Accessibility Checker" |
There was a problem hiding this comment.
Reverting a previously translated term like "Kasutajaliidese" (User interface/Frontend) back to English "Frontend" reduces the completeness of the localization. If the intent is to keep "Frontend" in English, this should be a consistent decision across all related strings and ideally documented. Otherwise, it's preferable to maintain the Estonian translation for a fully localized experience.
msgstr "Kasutajaliidese Accessibility Checker"
| #: includes/options-page.php:200 | ||
| msgid "Frontend Accessibility Checker Position" | ||
| msgstr "Kasutajaliidese Accessibility Checkeri asukoht" | ||
| msgstr "Frontend juurdepääsetavuse kontrollija positsioon" |
There was a problem hiding this comment.
This translation mixes English ("Frontend") with Estonian, which creates an inconsistent user experience. Given that "Kasutajaliidese" was previously used for "Frontend" (see line 1172), it would be better to maintain consistency and use the Estonian term here as well, or ensure a clear strategy for English technical terms.
msgstr "Kasutajaliidese juurdepääsetavuse kontrollija asukoht"
| #: includes/options-page.php:286 | ||
| msgid "Are you thinking \"Wow, this plugin is amazing\" and is it helping you make your website more accessible? Share your efforts to make your website more accessible with your customers and let them know you're using Accessibility Checker to ensure all people can use your website. Add a small text-only link and statement in the footer of your website." | ||
| msgstr "Kas te mõtlete „Vau, see plugin on uskumatu“ ja kas see aitab teil oma veebisaiti ligipääsetavamaks muuta? Jagage oma pingutusi veebisaidi ligipääsetavamaks muutmisel oma klientidega ja andke neile teada, et kasutate Accessibility Checkerit, et tagada kõigile inimestele teie veebisaidi kasutamise võimalus. Lisage oma veebisaidi jaluses väike ainult tekstist koosnev link ja avaldus." | ||
| msgstr "Kas sa mõtled \"Wow, see plugin on hämmastav\" ja kas see aitab sul oma veebilehte kättesaadavamaks muuta? Jagage oma jõupingutusi oma veebisaidi ligipääsetavamaks muutmisel oma klientidega ja andke neile teada, et kasutate Accessibility Checker'i, et tagada, et kõik inimesed saaksid teie veebisaiti kasutada. Lisage oma veebisaidi jalusesse väike tekstiline link ja avaldus." |
There was a problem hiding this comment.
This change shifts the tone from formal (te) to informal (sa). For consistency across the application's messages, it's important to maintain a uniform tone. If the intention is to use a formal tone for user-facing communication, please revert this change to match the formality used elsewhere.
msgstr "Kas te mõtlete \"Vau, see plugin on uskumatu\" ja kas see aitab teil oma veebisaiti ligipääsetavamaks muuta? Jagage oma pingutusi veebisaidi ligipääsetavamaks muutmisel oma klientidega ja andke neile teada, et kasutate Accessibility Checkerit, et tagada kõigile inimestele teie veebisaidi kasutamise võimalus. Lisage oma veebisaidi jaluses väike ainult tekstist koosnev link ja avaldus."
| #: partials/welcome-page.php:65 | ||
| msgid "Find the Accessibility Checker meta box below your content. If using a front-end page builder, you must visit the backend edit screen to view Accessibility Checker results." | ||
| msgstr "Leidke Accessibility Checkeri metakast oma sisu all. Kui kasutate esilehe lehe koosturit, peate Accessibility Checkeri tulemuste vaatamiseks külastama tagasüsteemi muutmise ekraani." | ||
| msgstr "Leia Accessibility Checkeri metakast oma sisu all. Kui kasutate eesmise osa lehekujundajat, peate Accessibility Checkeri tulemuste vaatamiseks külastama tagumise osa redigeerimisekraani." |
There was a problem hiding this comment.
Similar to other instances, this change introduces an inconsistent tone by switching from a formal imperative (Leidke) to an informal one (Leia). Please ensure a consistent tone (formal or informal) is used throughout the application's messages for a cohesive user experience.
msgstr "Leidke Accessibility Checkeri metakast oma sisu all. Kui kasutate esilehe lehe koosturit, peate Accessibility Checkeri tulemuste vaatamiseks külastama tagasüsteemi muutmise ekraani."
| #: partials/welcome-page.php:74 | ||
| msgid "Watch a video of Accessibility Checker in use." | ||
| msgstr "Vaadake videot Accessibility Checkeri kasutamisest." | ||
| msgstr "Vaata videot Accessibility Checkeri kasutamisest." |
There was a problem hiding this comment.
This change from Vaadake (formal imperative) to Vaata (informal imperative) creates an inconsistency in the application's tone. For better user experience, maintain a consistent level of formality across all messages.
msgstr "Vaadake videot Accessibility Checkeri kasutamisest."
![coderabbitai[bot]](https://avatars.githubusercontent.com/in/347564?s=60&v=4){kind=small}
There was a problem hiding this comment.
Actionable comments posted: 0
🧹 Nitpick comments (13)
languages/accessibility-checker-et.po (13)
172-175: Inconsistent month capitalisation & possessive form in promo string
- Estonian month names are written in lowercase (
novembrist,detsembrini).- The apostrophe in “Checker'i” is not idiomatic—previous strings use “Checkeri”.
-msgstr "Uuendage 25. Novembrist kuni 3. detsembrini Accessibility Checker'i tasulisele versioonile ja saate 30% allahindlust! Täielik saidi skaneerimine, kogu saidi hõlmav aruanne avatud probleemidest, ignoreerimisprotokollid ja palju muud." +msgstr "Uuendage Accessibility Checkeri tasulisele versioonile 25. novembrist kuni 3. detsembrini ja saate 30 % allahindlust! Täielik saidi skannimine, kogu saiti hõlmav avatud probleemide aruanne, ignoreerimislogid ja palju muud." --- `186-189`: **Product name declined awkwardly; wording can be streamlined** `"Accessibility Checker Pro'lt"` sounds forced. Prefer “hinnalt” or re-ordering the phrase. ```diff -msgstr "🎉 Saa 25% allahindlust Accessibility Checker Pro'lt ülemaailmse ligipääsetavuse päeva auks! 🎉" +msgstr "🎉 Saa 25 % allahindlust Accessibility Checker Pro hinnalt ülemaailmse ligipääsetavuse päeva auks! 🎉" --- `464-468`: **Mixed-language headline** The string now starts with English “Upgrade”. Everything else has been localised; use the established Estonian term. ```diff -msgstr "Upgrade Accessibility Checker (juurdepääsetavuse kontrollija)" +msgstr "Uuenda Accessibility Checkeri" --- `586-592`: **Keep plugin name consistent** Earlier strings use “Ligipääsetavuse kontrollija”. Here “Juurdepääsetavuse kontroll” drops the *-ja* suffix. ```diff -msgstr "Juurdepääsetavuse kontroll — auditiajalugu" +msgstr "Ligipääsetavuse kontrollija — auditiajalugu" --- `718-721`: **Plugin name again inconsistent** ```diff -msgstr "Ligipääsetavuse kontroll (avaneb uues aknas)" +msgstr "Ligipääsetavuse kontrollija (avaneb uues aknas)" --- `1146-1154`: **Greeting sentence – genitive apostrophe & style** “Accessibility Checker'ile” feels unnatural; recommend simpler phrasing. ```diff -msgstr "Tere tulemast Accessibility Checker'ile" +msgstr "Tere tulemast Accessibility Checkeri kasutajaks" --- `1170-1174`: **Untranslated term “Frontend”** Translate or rephrase for clarity. ```diff -msgstr "Frontend Accessibility Checker" +msgstr "Eesliidese ligipääsetavuse kontrollija" --- `1208-1213`: **Varying terminology: “juurdepääsetavuse kontrollimist” vs “Ligipääsetavuse kontrollija”** Prefer product name for recognisability. ```diff -msgstr "Kasutage allpool olevaid seadistusi, et konfigureerida juurdepääsetavuse kontrollimist. Lisateavet iga seadistuse kohta leiate %1$s." +msgstr "Kasutage allpool olevaid seadistusi, et konfigureerida Ligipääsetavuse kontrollijat. Lisateavet iga seadistuse kohta leiate %1$s." --- `1239-1243`: **Capital letter inside sentence** “9. Klass” → “9. klass”. ```diff -msgstr "Veebisisu juurdepääsetavuse suunised (WCAG) AAA-tasemel nõuavad, et iga sisu, mille lugemistase on kõrgem kui 9. Klass, peab olema lihtsamini loetav. ..." +msgstr "Veebisisu juurdepääsetavuse suunised (WCAG) AAA-tasemel nõuavad, et iga sisu, mille lugemistase on kõrgem kui 9. klass, peab olema lihtsamini loetav. ..." --- `1251-1254`: **Second-person shift (“sa” → “teie”) and apostrophe** Mixing informal and formal address in one sentence is jarring; also avoid possessive apostrophe. ```diff -msgstr "Kas sa mõtled \"Wow, see plugin on hämmastav\" ja kas see aitab sul oma veebilehte kättesaadavamaks muuta? Jagage oma jõupingutusi ..." +msgstr "Kas mõtlete: „Wow, see pistikprogramm on hämmastav“ ja kas see aitab teil oma veebisaiti ligipääsetavamaks muuta? Jagage oma jõupingutusi ..." --- `1293-1302`: **Long sentence – readability & duplicated phrase** Consider splitting and avoid repetition of “olenemata lugemise tasemest”. ```diff -msgstr "Kas Accessibility Checker peaks küsima lihtsustatud kokkuvõtet ainult siis, kui teie postituse või lehe lugemise tase on üle 9. klassi, küsima seda alati olenemata lugemise tasemest või mitte kunagi küsima seda olenemata lugemise tasemest?" +msgstr "Kas Accessibility Checker peaks küsima lihtsustatud kokkuvõtet ainult siis, kui teie postituse või lehe lugemistase ületab 9. klassi, küsima seda alati, või mitte kunagi – sõltumata lugemistasemest?" --- `1411-1413`: **Typo “skaneerimine” vs “skannimine”** You standardised on *skannimine* elsewhere. ```diff -msgstr "Accessibility Checkeris ilmub teksti õigustamise hoiatus, kui teie postituses või lehel on rohkem kui 200 tähemärki sisaldav tekst vormindatud õigustatud joondusega (text-align:justify)." +msgstr "Accessibility Checkeris ilmub teksti õigustamise hoiatus, kui teie postituses või lehel on üle 200 tähemärgi pikkune tekst vormindatud õigustatud joondusena (text-align: justify)." --- `1811-1818`: **Minor wording – natural Estonian** ```diff -msgstr "Kui teie postituses on vigu või hoiatusi, avage Accessibility Checkeris üksikasjade vahekaart lisateabe saamiseks." +msgstr "Kui postituses on vigu või hoiatusi, avage Accessibility Checkeri vahekaart „Üksikasjad“, et näha lisateavet." </blockquote></details> </blockquote></details> <details> <summary>📜 Review details</summary> **Configuration used: CodeRabbit UI** **Review profile: CHILL** **Plan: Pro** <details> <summary>📥 Commits</summary> Reviewing files that changed from the base of the PR and between 05ff04ab0f9ad1a25a0a01a3d9f24f57ebfed92d and 3b81047d5d046996c277ed946eb02d99b74d778f. </details> <details> <summary>📒 Files selected for processing (1)</summary> * `languages/accessibility-checker-et.po` (20 hunks) </details> <details> <summary>⏰ Context from checks skipped due to timeout of 90000ms (9)</summary> * GitHub Check: Integration Test: PHP 8.1 | WP latest (+ ms) * GitHub Check: Integration Test: PHP 8.1 | WP 6.2 * GitHub Check: Integration Test: PHP 8.2 | WP latest (+ ms) * GitHub Check: Integration Test: PHP 8.1 | WP latest * GitHub Check: make-pot * GitHub Check: Integration Test: PHP 8.1 | WP latest * GitHub Check: Integration Test: PHP 8.1 | WP latest (+ ms) * GitHub Check: Integration Test: PHP 8.2 | WP latest (+ ms) * GitHub Check: Integration Test: PHP 8.1 | WP 6.2 </details> </details> <!-- This is an auto-generated comment by CodeRabbit for review status -->
2 participants
For more information go to https://app.ptc.wpml.org/#/dashboard/merge-requests-history/1985
Summary by CodeRabbit