PTC accessibility-checker (1985): Automatic Translations July 29, 2025 12:12:40953900 - #1127
PTC accessibility-checker (1985): Automatic Translations July 29, 2025 12:12:40953900#1127SteveJonesDev wants to merge 16 commits into
Conversation
…5 12:12:40953900 - Vietnamese
…5 12:12:40953900 - Korean
…5 12:12:40953900 - Danish
…5 12:12:40953900 - Norwegian (Bokmål)
…5 12:12:40953900 - Bulgarian
…5 12:12:40953900 - Czech
…5 12:12:40953900 - Estonian
…5 12:12:40953900 - Finnish
…5 12:12:40953900 - Hungarian
…5 12:12:40953900 - Indonesian
…5 12:12:40953900 - Lithuanian
…5 12:12:40953900 - Latvian
…5 12:12:40953900 - Slovak
…5 12:12:40953900 - Slovenian
…5 12:12:40953900 - Turkish
…5 12:12:40953900 - Ukrainian
WalkthroughThis change reformats numerous JSON translation files for various languages from a multi-line, pretty-printed format to a single-line, minified format. The translation keys, values, and metadata remain unchanged except for the addition of a new "Rescan This Page" translation in a few files. No code or logic is altered. Changes
Estimated code review effort🎯 2 (Simple) | ⏱️ ~8 minutes Possibly related PRs
Suggested reviewers
Poem
Note ⚡️ Unit Test Generation is now available in beta!Learn more here, or try it out under "Finishing Touches" below. ✨ Finishing Touches🧪 Generate unit tests
🪧 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 (
|
|
The POT or JSON translation files have changed. Please update the translation files in your PR to keep translations up to date. |
![coderabbitai[bot]](https://avatars.githubusercontent.com/in/347564?s=60&v=4){kind=small}
There was a problem hiding this comment.
Actionable comments posted: 15
♻️ Duplicate comments (7)
languages/accessibility-checker-cs_CZ-4aeb45733c7671c6641789798428b69d.json (1)
1-1: Samelang":"en"vs Czech locale mismatch as noted in previous file.See previous comment – the header should be
"cs"(or"cs_CZ") with
the correct plural-forms rule.languages/accessibility-checker-cs_CZ-2babf73ad0b848216944ffff693aa351.json (1)
1-1: Header locale mismatch ("lang":"en").Identical issue as described earlier.
languages/accessibility-checker-cs_CZ-c6b6e50c6acd7c42c9d09e857f9ed6b0.json (1)
1-1: Header locale mismatch ("lang":"en").Identical issue as described earlier.
languages/accessibility-checker-cs_CZ-b93b9e514c44a41f97246123aa57f5c4.json (1)
1-1: Header locale mismatch ("lang":"en").Identical issue as described earlier.
languages/accessibility-checker-id_ID-2babf73ad0b848216944ffff693aa351.json (1)
1-1: Duplicate of earlier comment: storing minified single-line JSON in VCS harms diff readability; prefer pretty-printed sources and build-time minification.languages/accessibility-checker-id_ID-4aeb45733c7671c6641789798428b69d.json (1)
1-1: Duplicate of earlier comment: store formatted JSON, let the build process minify.languages/accessibility-checker-lt_LT-c6b6e50c6acd7c42c9d09e857f9ed6b0.json (1)
1-1: Duplicate of earlier comment: avoid committing minified translation files to keep diffs manageable.
🧹 Nitpick comments (61)
languages/accessibility-checker-hu_HU-4aeb45733c7671c6641789798428b69d.json (1)
1-1: Minifying source locale files hurts diff-ability—consider pretty source + minified build artifactThe switch to a single-line JSON dramatically reduces human readability and makes future PR reviews of translation changes nearly impossible (tiny string edits are buried). A common pattern is:
- Keep locale files pretty-printed in the repository for easy review/merge-conflict resolution.
- Generate minified versions during the build/release pipeline for distribution.
That gives you the best of both worlds—small artifacts for production, readable sources for developers.
languages/accessibility-checker-sk_SK-4aeb45733c7671c6641789798428b69d.json (1)
1-1: Minified JSON hurts diff-ability and maintainabilityChecking in single-line, minified translation files makes future reviews nearly impossible and increases merge-conflict risk. Prefer committing a human-readable, pretty-printed format and, if size matters, minify as part of the build/release pipeline.
languages/accessibility-checker-nb_NO-95b093794875bec5eeac2e02bfe32541.json (1)
1-1: Prefer committed, human-readable formatting over minified JSONCommitting minified JSON saves a few bytes but makes future diffs nearly unreadable, obscuring any real translation changes. A common pattern is to keep the file pretty-printed in the repo and let the build pipeline handle minification for distribution assets.
languages/accessibility-checker-ko_KR-4aeb45733c7671c6641789798428b69d.json (1)
1-1: Minified translation file hinders diff-based reviewsCommitting the translations as a single minified line makes future changes virtually impossible to review with meaningful diffs. Consider keeping the prettified, multi-line version in source control and generating the minified artifact during the build/release step (e.g., into
/build/or app bundle).
This keeps the repo human-friendly while still shipping the compact asset.languages/accessibility-checker-da_DK-c6b6e50c6acd7c42c9d09e857f9ed6b0.json (1)
1-1: Minifying translation file trades readability for size—consider keeping the source pretty-printedMoving to a single-line JSON reduces file size and diff noise but makes manual reviews and conflict resolution harder. A common pattern is to store the human-edited source in a pretty-printed format and add a build step (or commit hook) that minifies files for distribution.
If manual edits in the repo are still expected, keeping the file formatted will likely save future headache.languages/accessibility-checker-et-b93b9e514c44a41f97246123aa57f5c4.json (1)
1-1: Prefer storing translations pretty-printed and minifying only for distributionKeeping the source JSON minified reduces repo readability and causes noisy, non-semantic diffs. A common pattern is to commit human-readable, pretty-printed files and run a build-step (e.g.,
npm run i18n:compress) that minifies assets for production bundles or ZIP releases. This preserves auditability while still shipping compact assets.languages/accessibility-checker-tr_TR-2babf73ad0b848216944ffff693aa351.json (1)
1-1: Consider keeping human-readable JSON in the repository and minifying only at build timeThe switch to a single-line file improves payload size but makes future diffs nearly impossible to review, especially for translators who need context.
Typical i18n workflows store pretty-printed sources and run a minification step (e.g., viawp i18n make-json,jq -c, or a custom Gulp/Webpack task) in CI/CD before packaging.If repo size isn’t a pressing concern, retaining the pretty-printed JSON and generating a
.min.jsonartifact at release strikes a better balance between readability and performance.languages/accessibility-checker-ko_KR-c6b6e50c6acd7c42c9d09e857f9ed6b0.json (1)
1-1: Consider keeping human-readable formatting in VCS and minifying at build timeCommitting a fully minified one-liner makes diff reviews of future translation changes nearly impossible and inflates PR noise (every character becomes part of the hunk).
Common workflow: store prettified JSON in the repository, then minify during packaging (e.g., viawp i18n make-json,jq -c, or a Webpack loader) so runtime bundles stay small while git history remains legible.If build-time minification isn’t feasible, at least add an
.editorconfig/.gitattributesrule or npm script that can prettify the file for reviewers.languages/accessibility-checker-uk-4aeb45733c7671c6641789798428b69d.json (1)
1-1: Minified JSON hurts diff-ability & manual maintenanceStoring the translation file as a single 11 k-char line saves only a few KB but makes future diffs, code-search, and spot fixes painful. Consider committing pretty-printed JSON and delegating minification to the build/packaging step instead.
languages/accessibility-checker-sk_SK-ffd08c762bdabd23386ea03007811e0f.json (1)
1-1: Consider keeping human-readable JSON in VCS and minifying at build time
A single-line minified translation file is great for runtime size but makes diffs and manual edits painful. An alternative workflow is to commit pretty-printed JSON (or PO) files, then run a build step (npm script,make, etc.) that outputs minified assets tobuild/or similar. This preserves developer ergonomics while still delivering compact assets.languages/accessibility-checker-ko_KR-95b093794875bec5eeac2e02bfe32541.json (1)
1-1: Single-line minification hurts diff-ability and human editing
While compact JSON reduces file size, it makes reviews and manual fixes painful. A common pattern is:
- Keep a pretty-printed source file in VCS for readability.
- Generate the minified artefact during the build/publish step (e.g., via
npm run build-i18n).Consider adopting that workflow to balance size and maintainability.
languages/accessibility-checker-uk-2babf73ad0b848216944ffff693aa351.json (1)
1-1: Consider keeping human-readable JSON in source and minifying at build time
Committing minified translation files makes future diffs hard to scan and complicates manual edits. A common workflow is:
• store pretty-printed JSON insrc/…(easier reviews / merges)
• run a build step that minifies intobuild/…or similar and exclude the minified artifacts from code review.
If feasible, adopting that pattern will improve maintainability while retaining the runtime size benefits.languages/accessibility-checker-sk_SK-c6b6e50c6acd7c42c9d09e857f9ed6b0.json (1)
1-1: Minifying locale files hurts diff readability—keep sources formatted, minify at build timeWhile the minified one-liner reduces repository size marginally, it makes future PRs hard to review and virtually impossible to spot real content changes. Store the human-friendly, pretty-printed JSON in source control and add a build-step (e.g.,
npm run build:translations) to emit minified artifacts for distribution.languages/accessibility-checker-uk-ffd08c762bdabd23386ea03007811e0f.json (1)
1-1: Minified JSON hurts diff-ability — consider keeping a pretty-printed sourceA single-line 7 kB JSON string makes future reviews and translator updates painful. Typical pattern:
• Store a human-readable, pretty-printed file in the repo.
• Generate a.min.jsonvariant (or bundle into JS) during the build/deploy step.This keeps git history readable while still delivering compact assets in production.
languages/accessibility-checker-nb_NO-b93b9e514c44a41f97246123aa57f5c4.json (1)
1-1: Minified JSON hurts diff-readability; consider retaining pretty-printed format.The single-line form is perfectly valid JSON, but it makes future reviews of translation changes difficult because even a one-word edit shows up as a full-line replacement. Unless the build or delivery pipeline explicitly requires minification at source-control time, keep the human-friendly multi-line format and delegate minification to the build step.
languages/accessibility-checker-vi-c6b6e50c6acd7c42c9d09e857f9ed6b0.json (1)
1-1: Minification is fine, but keep a prettified source for translators & merge clarityStoring only the minified form makes diffs noisy and hard for translators to review. Consider committing prettified JSON in
src/and generating the minified artifact during the build/publish step (e.g., vianpm run i18n:compile).
This preserves readability while still shipping compact assets.languages/accessibility-checker-et-95b093794875bec5eeac2e02bfe32541.json (1)
1-1: Minified JSON aids size, but hampers human diff-ability—consider keeping the source pretty-printed and minifying at build timeShipping minified strings is fine for production, yet storing minified blobs in VCS makes future reviews almost impossible (every change becomes “the whole file changed”). A common pattern is to:
- Keep a formatted
.json(or.po/.pot) in source for translators & reviewers.- Add a CI step that runs
jq -c(or equivalent) to create the minified artefact for the plugin bundle.This keeps Git history readable while still delivering compact assets.
languages/accessibility-checker-da_DK-ffd08c762bdabd23386ea03007811e0f.json (1)
1-1: Minified translation file hampers version-control readabilityCommitting the locale file as a single-line minified blob makes future diffs almost unreadable; even the smallest text tweak will appear as a full-line change.
Consider committing the pretty-printed JSON (or PO/MO source) and letting a build step generate the minified artefact that ships with the plugin.If keeping the minified file is required, adding an accompanying
.pretty.json(ignored by the build) or amake formatscript can mitigate review pain.Also note the placeholder
"translation-revision-date":"YEAR-MO-DA HO:MI+ZONE"—ensure this is populated by the build step to avoid shipping placeholder metadata.languages/accessibility-checker-ko_KR-b93b9e514c44a41f97246123aa57f5c4.json (1)
1-1: Minifying in-repo translation JSON hurts diff-abilityStoring the file as a single-line JSON improves transfer size but makes code-reviewing and resolving merge conflicts painful. A common pattern is:
- Keep pretty-printed, human-friendly JSON in the repository.
- Generate minified assets in the build artefacts (ignored by Git) for runtime delivery.
Consider adopting that approach; it provides both maintainability and runtime efficiency.
languages/accessibility-checker-et-c6b6e50c6acd7c42c9d09e857f9ed6b0.json (2)
1-1: Replace placeholder revision date with an actual timestamp
"translation-revision-date"still contains the placeholder valueYEAR-MO-DA HO:MI+ZONE. Populate this during build/publish so tooling can detect when the catalog was last updated.
1-1: Commit pretty-printed JSON; leave minification to the build stepA single-line JSON hinders code-review diffing and often causes noisy merge conflicts. Consider keeping a readable, indented format in VCS and running minification only in distribution artifacts.
languages/accessibility-checker-hu_HU-c6b6e50c6acd7c42c9d09e857f9ed6b0.json (1)
1-1: Consider retaining pretty-printed JSON in repo and generating minified artifacts automaticallyCommitting the minified single-line JSON makes diffs and manual corrections hard to read. A typical workflow is to keep the formatted JSON in version control and minify during the build/publish step instead, preserving human readability without bloating the shipped asset.
languages/accessibility-checker-uk-95b093794875bec5eeac2e02bfe32541.json (1)
1-1: Minified JSON hurts diffability & maintainability – keep sources pretty-printedCommitting a 1-line blob obscures future diffs, complicates code-reviews, and increases merge-conflict surface. Commit the file formatted (e.g.,
json.dumps(obj, indent=2, ensure_ascii=False)) and let build tooling handle minification for distribution assets.languages/accessibility-checker-vi-4aeb45733c7671c6641789798428b69d.json (1)
1-1: Consider preserving a readable source for translators.
While minification reduces repo size, having a pretty-printed version (e.g., insrc/or generated artifacts) eases manual reviews and future updates.languages/accessibility-checker-lv-b93b9e514c44a41f97246123aa57f5c4.json (2)
1-1: Minified file in VCS – consider keeping a human-readable source.Committing the translation catalogue as a single-line JSON sacrifices diff readability and makes manual edits painful. A common pattern is:
- Store the prettified file in the repo for humans.
- Minify only in the build/release pipeline.
That keeps reviews meaningful while still delivering compact assets to production.
1-1:"translation-revision-date"still holds the placeholder value.The field is
"YEAR-MO-DA HO:MI+ZONE". Up-to-date revision metadata is useful for translators and troubleshooting. Please populate it automatically during the extraction/minification step.languages/accessibility-checker-sk_SK-2babf73ad0b848216944ffff693aa351.json (1)
1-1: Minified JSON hampers readability & diff quality – keep human-friendly formatting in the repoStoring locale files as a single-line string makes it almost impossible to review, merge-resolve, or cherry-pick individual key changes. Consider committing prettified JSON (e.g.
jq --indent 2output) and running minification only in the build/packaging step. This preserves readable history while still shipping compact assets.languages/accessibility-checker-tr_TR-ffd08c762bdabd23386ea03007811e0f.json (1)
1-1: Minified JSON hinders readability & future diffs – keep sources pretty-printedStoring translation catalogs in a single-line form makes review, merge conflict resolution, and manual edits cumbersome. Prefer committing them pretty-printed (e.g.,
json.dumps(obj, indent=2, ensure_ascii=False)) and, if desired, minify during build or packaging.This keeps Git history useful without sacrificing runtime size.
languages/accessibility-checker-vi-95b093794875bec5eeac2e02bfe32541.json (1)
1-1: Consider retaining human-readable source and generating the minified artifact in the build stepThe fully-minified single line keeps the runtime asset small but removes diff granularity—any future key change rewrites the whole line, making PRs hard to review. A common compromise is to keep a pretty-printed JSON in the repo and emit the compact
.min.jsonduring build/publish (e.g., via an i18n compile script). This preserves readability without sacrificing bundle size.languages/accessibility-checker-nb_NO-2babf73ad0b848216944ffff693aa351.json (2)
1-1: Potential typo – missing space in “Fikseinnstillinger” translation
"Fix Settings"is translated as“Fikseinnstillinger”(no space). Norwegian Bokmål normally requires a space:“Fikse innstillinger”or“Fiks innstillinger”. Please have a native speaker confirm.- "Fix Settings":["Fikseinnstillinger"] + "Fix Settings":["Fikse innstillinger"]
1-1: One-line minification hurts diff readabilityConverting the entire file to a single line reduces repository size but makes future reviews almost impossible (any change rewrites the whole line).
Consider keeping a human-readable, pretty-printed JSON in source control and generating the minified variant during the build/release process.languages/accessibility-checker-hu_HU-ffd08c762bdabd23386ea03007811e0f.json (1)
1-1: Replace the placeholder timestamp intranslation-revision-date.
"translation-revision-date":"YEAR-MO-DA HO:MI+ZONE"is still the scaffold value generated by WP-CLI.
Down-stream tooling (e.g., cache-busting, update detection) often expects an ISO-8601 timestamp here; leaving the placeholder can cause the file to be skipped or flagged as stale.Example quick fix:
-"translation-revision-date":"YEAR-MO-DA HO:MI+ZONE" +"translation-revision-date":"2025-07-29 12:12+0000"Please ensure your build process writes an actual revision date before merging.
languages/accessibility-checker-nb_NO-ffd08c762bdabd23386ea03007811e0f.json (2)
1-1: Minifying locale files hampers diff-ability; consider pretty-print in source & minify only for build artifacts.Moving the entire JSON into a single line makes future reviews much harder—tiny content changes become invisible in PR diffs. A common workflow is:
- Keep the human-readable, multi-line JSON in the repository.
- Add a build step (e.g.,
npm run i18n:compress) that writes minified copies todist/or equivalent.This preserves developer ergonomics while still shipping the smallest possible assets.
1-1:translation-revision-datestill contains the placeholder value.The header field is left as
YEAR-MO-DA HO:MI+ZONE; many tooling pipelines rely on this timestamp for cache-busting or translation freshness checks. Update it to the actual generation time or remove the field if unused to avoid misleading metadata.languages/accessibility-checker-cs_CZ-95b093794875bec5eeac2e02bfe32541.json (1)
1-1: One-line minification hurts diff-ability; consider keeping source pretty-printed and minifying at build.Committing a 20 kB JSON blob on a single line makes future reviews
and merges painful; you lose meaningful diffs.
A common pattern is:
- Keep
*.jsonpretty-printed inlanguages/(human-editable, diff-friendly).- Add a build step (
npm run build-translationsorwp i18n make-json --no-purge) that outputs minified assets intobuild/ordist/, which are ignored in PRs.This keeps the repo readable while still shipping minified files to production.
languages/accessibility-checker-cs_CZ-ffd08c762bdabd23386ea03007811e0f.json (1)
1-1: Minification accepted, but keep a pretty-printed variant in source control for maintainabilityThe single-line JSON reduces bundle size but makes future diffs and manual reviews painful.
Consider committing the human-readable file (e.g.*.jsonpretty-printed) and generating the minified version (*.min.json) during the build/publish step so translators and reviewers can work with a readable format while releases still ship the compact asset.languages/accessibility-checker-lv-2babf73ad0b848216944ffff693aa351.json (1)
1-1: Minified JSON hurts maintainability & diffabilityMoving from a pretty-printed to a single-line JSON makes the file ~unreadable for humans and future diffs will flag the whole file even for tiny key changes.
If size matters, keep the human-friendly.jsonin the repo and generate the minified artifact at build-time (e.g.,make i18n:build).languages/accessibility-checker-lt_LT-95b093794875bec5eeac2e02bfe32541.json (1)
1-1: Minified JSON hampers human readability & future diffsThe switch from pretty-printed to one-line JSON saves a few bytes but makes manual review and merge-conflict resolution painful. Consider keeping the source files formatted (checked-in prettified or wrapped at ≤ 80 cols) and letting your build pipeline handle minification for production assets instead.
languages/accessibility-checker-nb_NO-4aeb45733c7671c6641789798428b69d.json (1)
1-1: Minifying translation JSON hurts diff readability—consider keeping a pretty-printed source and generating a.min.jsonartifact at build timeStoring the only author-editable copy in a single line makes future reviews painful (every small change rewrites the whole file) and practically prevents manual edits.
Typical practice is:
- Keep a formatted
…nb_NO.jsonunder version control.- Generate
…nb_NO.min.json(or bundle) during the build/release step.This yields both human-friendly diffs and compact assets.
languages/accessibility-checker-da_DK-4aeb45733c7671c6641789798428b69d.json (1)
1-1: Minifying to a single line hampers diffabilityKeeping the JSON on one ultra-long line makes future diffs unreadable and inflates PRs when any key changes. Consider storing pretty-printed JSON in Git and letting build tooling handle minification for distribution artifacts.
languages/accessibility-checker-da_DK-95b093794875bec5eeac2e02bfe32541.json (1)
1-1: One-liner minification hurts diff readability & merge resolutionStoring translation catalogs as a single line makes future diffs opaque and complicates manual conflict resolution. Consider committing the pretty-printed variant (e.g. with
wp i18n make-json --no-compact) and letting the build pipeline minify for distribution instead.languages/accessibility-checker-vi-b93b9e514c44a41f97246123aa57f5c4.json (1)
1-1: Minified JSON impairs VCS diff-ability – keep prettified source, minify in build?Storing a one-line 5 kB JSON string makes manual reviews and merge conflict resolution difficult. A common pattern is:
- Commit a formatted
.json(or.po/.mo) that’s human-readable.- Minify during packaging (npm/gulp/webpack/CI) so deployed assets stay small.
Not blocking, but worth weighing readability vs. repo size.
languages/accessibility-checker-sk_SK-95b093794875bec5eeac2e02bfe32541.json (1)
1-1: Revision-date placeholder & hard-minified JSON hurt traceability
"translation-revision-date":"YEAR-MO-DA HO:MI+ZONE"is still the skeleton value produced bywp i18n make-json. Commit an actual timestamp to ease cache-busting and provenance tracking.
Additionally, fully minifying large JSON makes diffs opaque. Keeping a newline-indented format (or leveraging.gitattributes diff=json) greatly improves PR reviews while hardly affecting payload size after compression.languages/accessibility-checker-lt_LT-ffd08c762bdabd23386ea03007811e0f.json (2)
1-1:translation-revision-datestill has placeholder valueThe field keeps the scaffolding string
YEAR-MO-DA HO:MI+ZONE, which breaks some i18n tooling that expects a real timestamp. Replace it with the actual generation date or remove the field if not used.
1-1: Consider committing pretty-printed JSON; minify at build timeChecking a one-line 10 kB JSON file makes diffs opaque. Keeping the source formatted and letting the build process minify (e.g., via
wp i18n make-json --no-purge --pretty) improves code-review and blame while retaining runtime size benefits.languages/accessibility-checker-tr_TR-c6b6e50c6acd7c42c9d09e857f9ed6b0.json (1)
1-1: Minified JSON hampers diff readabilityA single-line file makes future reviews painful and inflates diffs for minor key changes.
Consider keeping UTF-8 JSON pretty-printed in the repo and performing minification only in the build artifact.languages/accessibility-checker-sl_SI-ffd08c762bdabd23386ea03007811e0f.json (1)
1-1: Minified JSON reduces VCS diff readability – commit pretty-printed, minify in buildCommitting single-line JSON makes each tiny textual change appear as a full-file rewrite, which hampers code-review and blame. Keep the human-readable, multi-line version in the repo and run minification during the packaging/build step instead.
languages/accessibility-checker-id_ID-95b093794875bec5eeac2e02bfe32541.json (1)
1-1: Minified JSON hurts diff-readability—keep pretty-printed source and generate minified in build.Committing the minified blob makes future translation updates hard to review (all keys appear on one line). A common pattern is to:
- Keep a human-friendly, pretty-printed
*.json(or*.json5) insrc/ortranslations/.- Add a build step (
npm run build:translationsor WP-CLI) that outputs minified assets tobuild/ordist/, which are then enqueued by PHP.This preserves reviewability without increasing runtime payload.
languages/accessibility-checker-vi-2babf73ad0b848216944ffff693aa351.json (1)
1-1: Same readability concern—consider storing formatted source, emit minified artifact.Minified commit impedes git blame & translator contributions. Prefer formatted source + build-time minification to keep both developer ergonomics and runtime efficiency.
languages/accessibility-checker-hu_HU-b93b9e514c44a41f97246123aa57f5c4.json (1)
1-1: Readable source vs. minified asset—apply build pipeline pattern.For consistency with other localization workflows (GlotPress, WP-CLI), store pretty JSON in VCS and produce minified output during release. This keeps diffs meaningful and simplifies manual edits.
languages/accessibility-checker-sl_SI-4aeb45733c7671c6641789798428b69d.json (1)
1-1: Maintainability tip: avoid committing single-line JSON.Same rationale as above—pretty print in repo, minify in CI/CD to retain developer friendliness without shipping extra bytes.
languages/accessibility-checker-lt_LT-b93b9e514c44a41f97246123aa57f5c4.json (1)
1-1: Readable translations first, minified later.Recommend storing formatted translations and generating minified versions automatically to improve diff clarity and translator collaboration.
languages/accessibility-checker-ko_KR-2babf73ad0b848216944ffff693aa351.json (1)
1-1: Repository-side minification hurts diffs & manual edits.Storing translation assets fully minified makes future reviews and merge conflict resolution painful. Consider committing them pretty-printed and minifying only in the build pipeline.
languages/accessibility-checker-et-2babf73ad0b848216944ffff693aa351.json (1)
1-1:translation-revision-dateleft as placeholderThe header still shows
YEAR-MO-DA HO:MI+ZONE.
While not critical at runtime, it undermines traceability. Consider stamping the actual build time:-"translation-revision-date":"YEAR-MO-DA HO:MI+ZONE" +"translation-revision-date":"2025-07-29 12:12+0000"languages/accessibility-checker-tr_TR-4aeb45733c7671c6641789798428b69d.json (1)
1-1: Minified JSON reduces human-readability & diff qualityStoring translations in a single-line format makes future reviews almost impossible—every string change shows as a whole-file diff.
Recommend keeping files pretty-printed in the repo and running a minify step only in the build/release pipeline.languages/accessibility-checker-tr_TR-b93b9e514c44a41f97246123aa57f5c4.json (1)
1-1: Minified JSON hurts diff-ability & manual reviews.While minification reduces file size, the repo previously stored translations pretty-printed, making string updates easy to review. Consider keeping human-readable formatting and letting build tooling handle minification for distribution artifacts.
languages/accessibility-checker-bg_BG-2babf73ad0b848216944ffff693aa351.json (1)
1-1: Minified JSON reduces diff readability; consider keeping a formatted source in VCSStoring only the minified one-liner makes future reviews painful—small textual edits will appear as wholesale file changes. A common pattern is to keep the pretty-printed JSON in the repo and generate the minified artifact in a build step (e.g. via WP-CLI) or store both (-src vs. ‑dist).
languages/accessibility-checker-uk-b93b9e514c44a41f97246123aa57f5c4.json (1)
1-1: Minified JSON reduces human diff-ability; consider keeping pretty-printed source
One-line minification saves a few bytes but makes reviews impossible. A common pattern is: commit pretty-printed files, then minify during the build/release step. Evaluate if that workflow suits this repo.languages/accessibility-checker-sk_SK-b93b9e514c44a41f97246123aa57f5c4.json (1)
1-1: Minifying translation JSON hinders diff-based reviewsMoving from pretty-printed to one-line JSON makes future localisation changes hard to review and increases merge-conflict risk.
Consider keeping files formatted (e.g. via Prettier) while enabling gzip/HTTP compression at runtime instead of source-level minification.languages/accessibility-checker-lv-4aeb45733c7671c6641789798428b69d.json (2)
1-1:translation-revision-dateplaceholder never replacedThe header still reads
"YEAR-MO-DA HO:MI+ZONE".
While largely cosmetic, an actual timestamp is useful for cache-busting and tracking when translations were last updated. Ensure the build step populates this field.
1-1: One-line minification hinders diff readabilityMoving from pretty-printed JSON to a single line makes future reviews painful and increases merge-conflict risk with crowd-sourced translations.
Consider storing files prettified in source control and letting the build pipeline minify them for distribution instead.
📜 Review details
Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro
📒 Files selected for processing (91)
languages/accessibility-checker-bg_BG-2babf73ad0b848216944ffff693aa351.json(1 hunks)languages/accessibility-checker-bg_BG-4aeb45733c7671c6641789798428b69d.json(1 hunks)languages/accessibility-checker-bg_BG-95b093794875bec5eeac2e02bfe32541.json(1 hunks)languages/accessibility-checker-bg_BG-b93b9e514c44a41f97246123aa57f5c4.json(1 hunks)languages/accessibility-checker-bg_BG-c6b6e50c6acd7c42c9d09e857f9ed6b0.json(1 hunks)languages/accessibility-checker-bg_BG-ffd08c762bdabd23386ea03007811e0f.json(1 hunks)languages/accessibility-checker-cs_CZ-2babf73ad0b848216944ffff693aa351.json(1 hunks)languages/accessibility-checker-cs_CZ-4aeb45733c7671c6641789798428b69d.json(1 hunks)languages/accessibility-checker-cs_CZ-95b093794875bec5eeac2e02bfe32541.json(1 hunks)languages/accessibility-checker-cs_CZ-b93b9e514c44a41f97246123aa57f5c4.json(1 hunks)languages/accessibility-checker-cs_CZ-c6b6e50c6acd7c42c9d09e857f9ed6b0.json(1 hunks)languages/accessibility-checker-cs_CZ-ffd08c762bdabd23386ea03007811e0f.json(1 hunks)languages/accessibility-checker-da_DK-2babf73ad0b848216944ffff693aa351.json(1 hunks)languages/accessibility-checker-da_DK-4aeb45733c7671c6641789798428b69d.json(1 hunks)languages/accessibility-checker-da_DK-95b093794875bec5eeac2e02bfe32541.json(1 hunks)languages/accessibility-checker-da_DK-b93b9e514c44a41f97246123aa57f5c4.json(1 hunks)languages/accessibility-checker-da_DK-c6b6e50c6acd7c42c9d09e857f9ed6b0.json(1 hunks)languages/accessibility-checker-da_DK-ffd08c762bdabd23386ea03007811e0f.json(1 hunks)languages/accessibility-checker-et-2babf73ad0b848216944ffff693aa351.json(1 hunks)languages/accessibility-checker-et-4aeb45733c7671c6641789798428b69d.json(1 hunks)languages/accessibility-checker-et-95b093794875bec5eeac2e02bfe32541.json(1 hunks)languages/accessibility-checker-et-b93b9e514c44a41f97246123aa57f5c4.json(1 hunks)languages/accessibility-checker-et-c6b6e50c6acd7c42c9d09e857f9ed6b0.json(1 hunks)languages/accessibility-checker-et-ffd08c762bdabd23386ea03007811e0f.json(1 hunks)languages/accessibility-checker-fi_FI-b93b9e514c44a41f97246123aa57f5c4.json(1 hunks)languages/accessibility-checker-hu_HU-2babf73ad0b848216944ffff693aa351.json(1 hunks)languages/accessibility-checker-hu_HU-4aeb45733c7671c6641789798428b69d.json(1 hunks)languages/accessibility-checker-hu_HU-95b093794875bec5eeac2e02bfe32541.json(1 hunks)languages/accessibility-checker-hu_HU-b93b9e514c44a41f97246123aa57f5c4.json(1 hunks)languages/accessibility-checker-hu_HU-c6b6e50c6acd7c42c9d09e857f9ed6b0.json(1 hunks)languages/accessibility-checker-hu_HU-ffd08c762bdabd23386ea03007811e0f.json(1 hunks)languages/accessibility-checker-id_ID-2babf73ad0b848216944ffff693aa351.json(1 hunks)languages/accessibility-checker-id_ID-4aeb45733c7671c6641789798428b69d.json(1 hunks)languages/accessibility-checker-id_ID-95b093794875bec5eeac2e02bfe32541.json(1 hunks)languages/accessibility-checker-id_ID-b93b9e514c44a41f97246123aa57f5c4.json(1 hunks)languages/accessibility-checker-id_ID-c6b6e50c6acd7c42c9d09e857f9ed6b0.json(1 hunks)languages/accessibility-checker-id_ID-ffd08c762bdabd23386ea03007811e0f.json(1 hunks)languages/accessibility-checker-ko_KR-2babf73ad0b848216944ffff693aa351.json(1 hunks)languages/accessibility-checker-ko_KR-4aeb45733c7671c6641789798428b69d.json(1 hunks)languages/accessibility-checker-ko_KR-95b093794875bec5eeac2e02bfe32541.json(1 hunks)languages/accessibility-checker-ko_KR-b93b9e514c44a41f97246123aa57f5c4.json(1 hunks)languages/accessibility-checker-ko_KR-c6b6e50c6acd7c42c9d09e857f9ed6b0.json(1 hunks)languages/accessibility-checker-ko_KR-ffd08c762bdabd23386ea03007811e0f.json(1 hunks)languages/accessibility-checker-lt_LT-2babf73ad0b848216944ffff693aa351.json(1 hunks)languages/accessibility-checker-lt_LT-4aeb45733c7671c6641789798428b69d.json(1 hunks)languages/accessibility-checker-lt_LT-95b093794875bec5eeac2e02bfe32541.json(1 hunks)languages/accessibility-checker-lt_LT-b93b9e514c44a41f97246123aa57f5c4.json(1 hunks)languages/accessibility-checker-lt_LT-c6b6e50c6acd7c42c9d09e857f9ed6b0.json(1 hunks)languages/accessibility-checker-lt_LT-ffd08c762bdabd23386ea03007811e0f.json(1 hunks)languages/accessibility-checker-lv-2babf73ad0b848216944ffff693aa351.json(1 hunks)languages/accessibility-checker-lv-4aeb45733c7671c6641789798428b69d.json(1 hunks)languages/accessibility-checker-lv-95b093794875bec5eeac2e02bfe32541.json(1 hunks)languages/accessibility-checker-lv-b93b9e514c44a41f97246123aa57f5c4.json(1 hunks)languages/accessibility-checker-lv-c6b6e50c6acd7c42c9d09e857f9ed6b0.json(1 hunks)languages/accessibility-checker-lv-ffd08c762bdabd23386ea03007811e0f.json(1 hunks)languages/accessibility-checker-nb_NO-2babf73ad0b848216944ffff693aa351.json(1 hunks)languages/accessibility-checker-nb_NO-4aeb45733c7671c6641789798428b69d.json(1 hunks)languages/accessibility-checker-nb_NO-95b093794875bec5eeac2e02bfe32541.json(1 hunks)languages/accessibility-checker-nb_NO-b93b9e514c44a41f97246123aa57f5c4.json(1 hunks)languages/accessibility-checker-nb_NO-c6b6e50c6acd7c42c9d09e857f9ed6b0.json(1 hunks)languages/accessibility-checker-nb_NO-ffd08c762bdabd23386ea03007811e0f.json(1 hunks)languages/accessibility-checker-sk_SK-2babf73ad0b848216944ffff693aa351.json(1 hunks)languages/accessibility-checker-sk_SK-4aeb45733c7671c6641789798428b69d.json(1 hunks)languages/accessibility-checker-sk_SK-95b093794875bec5eeac2e02bfe32541.json(1 hunks)languages/accessibility-checker-sk_SK-b93b9e514c44a41f97246123aa57f5c4.json(1 hunks)languages/accessibility-checker-sk_SK-c6b6e50c6acd7c42c9d09e857f9ed6b0.json(1 hunks)languages/accessibility-checker-sk_SK-ffd08c762bdabd23386ea03007811e0f.json(1 hunks)languages/accessibility-checker-sl_SI-2babf73ad0b848216944ffff693aa351.json(1 hunks)languages/accessibility-checker-sl_SI-4aeb45733c7671c6641789798428b69d.json(1 hunks)languages/accessibility-checker-sl_SI-95b093794875bec5eeac2e02bfe32541.json(1 hunks)languages/accessibility-checker-sl_SI-b93b9e514c44a41f97246123aa57f5c4.json(1 hunks)languages/accessibility-checker-sl_SI-c6b6e50c6acd7c42c9d09e857f9ed6b0.json(1 hunks)languages/accessibility-checker-sl_SI-ffd08c762bdabd23386ea03007811e0f.json(1 hunks)languages/accessibility-checker-tr_TR-2babf73ad0b848216944ffff693aa351.json(1 hunks)languages/accessibility-checker-tr_TR-4aeb45733c7671c6641789798428b69d.json(1 hunks)languages/accessibility-checker-tr_TR-95b093794875bec5eeac2e02bfe32541.json(1 hunks)languages/accessibility-checker-tr_TR-b93b9e514c44a41f97246123aa57f5c4.json(1 hunks)languages/accessibility-checker-tr_TR-c6b6e50c6acd7c42c9d09e857f9ed6b0.json(1 hunks)languages/accessibility-checker-tr_TR-ffd08c762bdabd23386ea03007811e0f.json(1 hunks)languages/accessibility-checker-uk-2babf73ad0b848216944ffff693aa351.json(1 hunks)languages/accessibility-checker-uk-4aeb45733c7671c6641789798428b69d.json(1 hunks)languages/accessibility-checker-uk-95b093794875bec5eeac2e02bfe32541.json(1 hunks)languages/accessibility-checker-uk-b93b9e514c44a41f97246123aa57f5c4.json(1 hunks)languages/accessibility-checker-uk-c6b6e50c6acd7c42c9d09e857f9ed6b0.json(1 hunks)languages/accessibility-checker-uk-ffd08c762bdabd23386ea03007811e0f.json(1 hunks)languages/accessibility-checker-vi-2babf73ad0b848216944ffff693aa351.json(1 hunks)languages/accessibility-checker-vi-4aeb45733c7671c6641789798428b69d.json(1 hunks)languages/accessibility-checker-vi-95b093794875bec5eeac2e02bfe32541.json(1 hunks)languages/accessibility-checker-vi-b93b9e514c44a41f97246123aa57f5c4.json(1 hunks)languages/accessibility-checker-vi-c6b6e50c6acd7c42c9d09e857f9ed6b0.json(1 hunks)languages/accessibility-checker-vi-ffd08c762bdabd23386ea03007811e0f.json(1 hunks)
⏰ Context from checks skipped due to timeout of 90000ms. You can increase the timeout in your CodeRabbit configuration to a maximum of 15 minutes (900000ms). (1)
- GitHub Check: make-pot
🔇 Additional comments (49)
languages/accessibility-checker-et-ffd08c762bdabd23386ea03007811e0f.json (1)
1-1: LGTM – purely formatting changeNo semantic or structural modifications; translation data remains untouched.
languages/accessibility-checker-hu_HU-2babf73ad0b848216944ffff693aa351.json (1)
1-1: Minified translation JSON looks fineNo semantic changes detected; the single-line format is valid JSON and consistent with the other locale files minified in this PR.
languages/accessibility-checker-lv-c6b6e50c6acd7c42c9d09e857f9ed6b0.json (1)
1-1: Minified-JSON change looks fine.No semantic changes detected; data remains intact. 👍
languages/accessibility-checker-tr_TR-95b093794875bec5eeac2e02bfe32541.json (1)
1-1: Minification looks good – no semantic changes detected.Only formatting changed to a single-line JSON; keys/values remain intact, so this is safe to merge.
languages/accessibility-checker-ko_KR-95b093794875bec5eeac2e02bfe32541.json (1)
1-1:translation-revision-dateplaceholder is still the default value
The value"YEAR-MO-DA HO:MI+ZONE"was not replaced with an actual timestamp. WordPress uses this field to decide whether a translation file is stale; leaving the placeholder could cause the file to be ignored or repeatedly re-generated.languages/accessibility-checker-uk-2babf73ad0b848216944ffff693aa351.json (1)
1-1: Translation data unchanged – formatting looks fine
The switch to a compact, single-line JSON doesn’t affect runtime behavior.languages/accessibility-checker-uk-ffd08c762bdabd23386ea03007811e0f.json (1)
1-1: Formatting-only change looks fineNo keys, values, or metadata were altered—only whitespace was removed. From a functional standpoint this is safe.
languages/accessibility-checker-ko_KR-b93b9e514c44a41f97246123aa57f5c4.json (1)
1-1: Placeholdertranslation-revision-datestill present – verify build step replaces it
"translation-revision-date":"YEAR-MO-DA HO:MI+ZONE"is a literal placeholder.
WordPress expects an actual timestamp (e.g.2025-07-29 12:12+0000).
If the placeholder isn’t replaced during the build/publish pipeline, the JSON will be treated as stale and can be rejected bywp i18n make-json.Please confirm that a post-build task substitutes the correct date or update the file here before merging.
languages/accessibility-checker-hu_HU-c6b6e50c6acd7c42c9d09e857f9ed6b0.json (1)
1-1:translation-revision-dateplaceholder is stillYEAR-MO-DA HO:MI+ZONEIf this placeholder is not replaced later, translation tooling may treat the file as stale. Please verify the export pipeline or post-processing step that should inject the actual timestamp.
languages/accessibility-checker-uk-95b093794875bec5eeac2e02bfe32541.json (1)
1-1: Locale is missing the new “Rescan This Page” string present in other languagesOther updated catalogs include a translation for
"Rescan This Page"; this Ukrainian file does not. Without the key, the UI will fall back to English. Please add the entry (even if untranslated) to keep string parity across locales.languages/accessibility-checker-vi-4aeb45733c7671c6641789798428b69d.json (1)
1-1: LGTM – formatting-only change keeps translations intact.
No functional impact observed; the minified JSON is syntactically valid and preserves all keys/values.languages/accessibility-checker-lv-b93b9e514c44a41f97246123aa57f5c4.json (1)
1-1:"lang":"en"looks wrong for a Latvian (lv) catalogue.
locale_data.messages[""].langis set to"en", but the file name and strings indicate Latvian. Some i18n loaders rely on this header to pick plural rules; a mismatch could cause runtime issues.Confirm whether this should be
"lv", and regenerate the.jsonif necessary.languages/accessibility-checker-ko_KR-ffd08c762bdabd23386ea03007811e0f.json (1)
1-1: Minification looks good – no functional impact detectedValidated that the one-line JSON still parses correctly and carries the same keys/values. No further action needed.
languages/accessibility-checker-tr_TR-ffd08c762bdabd23386ea03007811e0f.json (1)
1-1:translation-revision-datestill contains placeholder textThe value
"YEAR-MO-DA HO:MI+ZONE"looks like a template token that never got replaced. Confirm whether the tooling expects an actual timestamp; leaving the placeholder may break downstream checks or mislead translators.languages/accessibility-checker-hu_HU-ffd08c762bdabd23386ea03007811e0f.json (1)
1-1: Confirm the"lang":"en"flag is intentional for a Hungarian catalog.Inside the header block we still declare
"lang":"en", while the file name and entries targethu_HU.
Some i18n consumers rely on this field to determine the catalogue language; a mismatch can cause fall-backs to English or prevent loading altogether.If this value should reflect the target language, amend it:
-"lang":"en" +"lang":"hu"Otherwise, document why English is correct (e.g., “lang denotes source string language”) to avoid future confusion.
languages/accessibility-checker-nb_NO-ffd08c762bdabd23386ea03007811e0f.json (1)
1-1: Check if the new “Rescan This Page” key should exist for nb_NO.Other locale files in this PR added the
"Rescan This Page"string, but it’s missing here. Confirm whether Norwegian really doesn’t need this translation or if it was accidentally omitted.languages/accessibility-checker-lv-ffd08c762bdabd23386ea03007811e0f.json (1)
1-1: LGTM – semantic content unchanged, just minifiedThe file remains valid JSON and all translation keys/values are preserved. No further action needed.
languages/accessibility-checker-cs_CZ-95b093794875bec5eeac2e02bfe32541.json (1)
1-1:langheader is still set to"en"instead of the Czech locale – please verify.Inside
locale_data.messages[""]we still declare
"lang":"en"even though the file is clearly Czech (cs_CZ).
Several i18n loaders use this header to decide whether a catalog
is suitable for the active locale; leaving it as"en"risks the file
being ignored or falling back to English.Diff illustrating the required fix:
-{"domain":"messages","lang":"en","plural-forms":"nplurals=2; plural=(n != 1);"} +{"domain":"messages","lang":"cs","plural-forms":"nplurals=3; plural=(n==1) ? 0 : (n>=2 && n<=4) ? 1 : 2;"}(Plural-form expression taken from the official WordPress Czech catalog.)
Would you double-check, or should I script-scan the repo for other locale files with the same mismatch?
languages/accessibility-checker-lv-2babf73ad0b848216944ffff693aa351.json (2)
1-1:translation-revision-dateis still the template placeholder
"translation-revision-date":"YEAR-MO-DA HO:MI+ZONE"was not updated. WP-CLI expects an actual timestamp; leaving the placeholder may break tooling that relies on date comparisons.
Please regenerate translations withwp i18n make-json --pretty-print(or similar) so the field is populated.
1-1: Potential language code mismatchInside
locale_data.messages[""].langthe value is"en", but this file represents Latvian (lv). Double-check whether WP-CLI intentionally keeps"en"(source language) here or if it should be"lv". Mismatched codes can cause the translation to be skipped.languages/accessibility-checker-nb_NO-4aeb45733c7671c6641789798428b69d.json (1)
1-1: Verify locale metadata & completenessThe
"lang":"en"value embedded in annb_NOfile looks suspect—WordPress JSON files usually match the locale (e.g.,"lang":"nb_NO").
Additionally, other locales in this PR gained the new key"Rescan This Page"; that entry is missing here. Please confirm this file shouldn't include it.languages/accessibility-checker-da_DK-4aeb45733c7671c6641789798428b69d.json (1)
1-1: "lang" field still set to English & revision date placeholder looks staleThe header still shows
"lang":"en"and the dummy"translation-revision-date":"YEAR-MO-DA HO:MI+ZONE", which is inconsistent with a Danish (da_DK) translation and may cause WordPress to regard the file as untranslated or outdated.-{"translation-revision-date":"YEAR-MO-DA HO:MI+ZONE", ... "lang":"en", ...} +{"translation-revision-date":"2025-07-29 12:12+0000", ... "lang":"da_DK", ...}Please verify the generator or post-processing step so both fields are filled correctly on rebuild.
languages/accessibility-checker-da_DK-95b093794875bec5eeac2e02bfe32541.json (1)
1-1:translation-revision-dateis still a placeholderThe value is
"YEAR-MO-DA HO:MI+ZONE", which indicates the build step that stamps the actual revision timestamp never ran (or ran incorrectly). WordPress uses this field to decide whether a JSON catalog is up-to-date; leaving the placeholder can cause the catalog to be ignored and fall back to the POT or an older MO file.- "translation-revision-date":"YEAR-MO-DA HO:MI+ZONE" + "translation-revision-date":"2025-07-29 12:12+0000" // example – should be generated automaticallyPlease re-run the i18n build so the timestamp is populated, or patch it manually if that pipeline step is unavailable.
languages/accessibility-checker-vi-b93b9e514c44a41f97246123aa57f5c4.json (1)
1-1:translation-revision-dateplaceholder still present – please verify build stepThe field
"translation-revision-date":"YEAR-MO-DA HO:MI+ZONE"has not been interpolated with a real timestamp. Some i18n tooling treats an unreplaced placeholder as “stale” and may skip the file or mark it as needing update.Consider ensuring your build/export step writes an ISO-8601 timestamp, e.g.:
-{"translation-revision-date":"YEAR-MO-DA HO:MI+ZONE", +{"translation-revision-date":"2025-07-29 12:12+0000",If this placeholder is intentionally left for downstream automation, please confirm it won’t break WP i18n loading.
languages/accessibility-checker-vi-ffd08c762bdabd23386ea03007811e0f.json (1)
1-1: Translation key “Rescan This Page” is missing for VietnameseOther locale files in this PR added the new key, but it’s absent here, so the UI will fall back to English for Vietnamese users. Please confirm whether the omission is intentional; if not, add a Vietnamese translation, e.g.:
…"learn more":["tìm hiểu thêm"], +"Rescan This Page":["Quét lại trang này"] }}languages/accessibility-checker-lt_LT-ffd08c762bdabd23386ea03007811e0f.json (1)
1-1: Missing “Rescan This Page” translation keyOther locale files in this PR include the new UI string, but the Lithuanian set does not. Without it, the interface will silently fall back to English for LT users.
Add the entry inside
locale_data.messagesto keep parity:…"learn more":["sužinoti daugiau"] +,"Rescan This Page":["Iš naujo nuskaityti šį puslapį"]languages/accessibility-checker-lt_LT-4aeb45733c7671c6641789798428b69d.json (1)
1-1: Alltranslation-revision-dateplaceholders have been replaced
A search for “YEAR-MO-DA” across all JSON files returned no matches, indicating the placeholder has been removed and real timestamps are present. No further action needed.languages/accessibility-checker-lv-95b093794875bec5eeac2e02bfe32541.json (1)
1-1: JSON minification looks goodWhitespace-only change reduces file size and is fine for production.
languages/accessibility-checker-hu_HU-95b093794875bec5eeac2e02bfe32541.json (1)
1-1: Placeholdertranslation-revision-dateleft unreplacedThe
"translation-revision-date"field still contains the template stringYEAR-MO-DA HO:MI+ZONE.
Many build and deploy pipelines rely on this timestamp to detect updated translation packs; shipping the placeholder may prevent those updates from being picked up.Make sure the build step that generates/minifies the JSON sets a real timestamp, or post-process the artefact before committing.
languages/accessibility-checker-tr_TR-c6b6e50c6acd7c42c9d09e857f9ed6b0.json (1)
1-1:translation-revision-dateplaceholder not replaced
"translation-revision-date":"YEAR-MO-DA HO:MI+ZONE"is a stub left bywp i18n make-json.
If not updated, GlotPress/WordPress treats the file as stale and can prefer another catalog.Confirm whether your build pipeline populates this field after minification; if not, set an actual timestamp, e.g.:
-"translation-revision-date":"YEAR-MO-DA HO:MI+ZONE" +"translation-revision-date":"2025-07-29 12:12+0000"languages/accessibility-checker-fi_FI-b93b9e514c44a41f97246123aa57f5c4.json (1)
1-1: New “Rescan This Page” key looks correct; placeholders still intactThe added string and existing
%splaceholders appear consistent with the English source. No further action needed.Please confirm translators validated the placeholder ordering (%s…%s) in runtime.
languages/accessibility-checker-id_ID-ffd08c762bdabd23386ea03007811e0f.json (1)
1-1: Consider storing translations in a readable (pretty-printed) form and performing minification only in the build pipelineCommitting single-line JSON makes human diff review nearly impossible and inflates PR noise. Keeping the source pretty-printed while letting a build step generate the minified assets preserves readability without affecting runtime size.
If minification in-repo is required, at least retain an
.unmin.json(or similar) alongside to aid translators.[ suggest_optional_refactor ]
[ request_verification ]languages/accessibility-checker-lt_LT-2babf73ad0b848216944ffff693aa351.json (1)
1-1: Same observation as in the Indonesian file: the wholesale switch to single-line JSON hampers diffability and translator edits.[ duplicate_comment ]
languages/accessibility-checker-sl_SI-2babf73ad0b848216944ffff693aa351.json (1)
1-1: See prior comment regarding minification reducing review readability.[ duplicate_comment ]
languages/accessibility-checker-sl_SI-c6b6e50c6acd7c42c9d09e857f9ed6b0.json (1)
1-1: See prior comment regarding minification reducing review readability.[ duplicate_comment ]
languages/accessibility-checker-id_ID-c6b6e50c6acd7c42c9d09e857f9ed6b0.json (1)
1-1: See prior comment regarding minification reducing review readability.[ duplicate_comment ]
languages/accessibility-checker-da_DK-2babf73ad0b848216944ffff693aa351.json (1)
1-1: Minification-only change – no issues foundThe file is now compact JSON with identical content; translations remain intact.
languages/accessibility-checker-sl_SI-95b093794875bec5eeac2e02bfe32541.json (1)
1-1: Minification-only change – no issues foundFormatting update only; semantic content unchanged.
languages/accessibility-checker-id_ID-b93b9e514c44a41f97246123aa57f5c4.json (1)
1-1: New “Rescan This Page” translation added – looks correctThe Indonesian string “Pindai ulang halaman ini” is in place and the JSON is valid.
languages/accessibility-checker-da_DK-b93b9e514c44a41f97246123aa57f5c4.json (1)
1-1: New translation entry verifiedAdds Danish “Genindlæs denne side”; no other content changes.
languages/accessibility-checker-sl_SI-b93b9e514c44a41f97246123aa57f5c4.json (1)
1-1: New translation entry verifiedAdds Slovenian “Ponovno preglej to stran”; JSON structure remains valid.
languages/accessibility-checker-et-4aeb45733c7671c6641789798428b69d.json (2)
1-1:translation-revision-dateplaceholder never replacedThe header still contains the template string
YEAR-MO-DA HO:MI+ZONE.
Without a real timestamp WordPress treats the file as stale and may ignore it when fresher translations exist.Please populate this field during the build step (e.g.,
2025-07-29 12:12+0000) or remove it if not used.
1-1: Potentially missing new key"Rescan This Page"Other locale files in this PR gained a translation for the new UI copy
"Rescan This Page", but the Estonian bundle did not.
Confirm whether this key is intentionally omitted or should be included to keep feature-parity across locales.languages/accessibility-checker-tr_TR-4aeb45733c7671c6641789798428b69d.json (1)
1-1: Ignore thelangheader mismatch—it’s systematic
All of the JSON translation files generated here (includingtr_TR) use"lang":"en"in their headers. This isn’t an outlier, but how WP-CLI emits these JS translation files. WordPress’s i18n-JS loader relies on the file name for locale, not that header, so no change is required.Likely an incorrect or invalid review comment.
languages/accessibility-checker-bg_BG-4aeb45733c7671c6641789798428b69d.json (1)
1-1: No functional or content changes—only whitespace eliminated.languages/accessibility-checker-bg_BG-95b093794875bec5eeac2e02bfe32541.json (1)
1-1: No functional or content changes—only whitespace eliminated.languages/accessibility-checker-bg_BG-b93b9e514c44a41f97246123aa57f5c4.json (1)
1-1: New key “Rescan This Page” translated correctlyThe added string appears accurate Bulgarian (“Сканирай отново тази страница”). Nothing else changed.
languages/accessibility-checker-bg_BG-c6b6e50c6acd7c42c9d09e857f9ed6b0.json (1)
1-1: No functional or content changes—only whitespace eliminated.languages/accessibility-checker-uk-b93b9e514c44a41f97246123aa57f5c4.json (1)
1-1: Placeholdertranslation-revision-dateleft unreplaced
"translation-revision-date":"YEAR-MO-DA HO:MI+ZONE"is still the template value. Some tooling interprets this literally and may emit warnings or skip the file. Confirm whether your build pipeline rewrites it later; if not, fill it with the actual ISO-8601 timestamp.
| } | ||
| } | ||
| } No newline at end of file | ||
| {"translation-revision-date":"YEAR-MO-DA HO:MI+ZONE","generator":"WP-CLI\/2.12.0","source":"build\/pageScanner.bundle.js","domain":"messages","locale_data":{"messages":{"":{"domain":"messages","lang":"en","plural-forms":"nplurals=2; plural=(n != 1);"},"opens a new window":["\u043e\u0442\u0432\u0430\u0440\u044f \u0441\u0435 \u0432 \u043d\u043e\u0432 \u043f\u0440\u043e\u0437\u043e\u0440\u0435\u0446"],"new window":["\u043d\u043e\u0432 \u043f\u0440\u043e\u0437\u043e\u0440\u0435\u0446"],"new tab":["\u043d\u043e\u0432 \u0440\u0430\u0437\u0434\u0435\u043b"],"click":["\u0449\u0440\u0430\u043a\u043d\u0435\u0442\u0435"],"click here":["\u0449\u0440\u0430\u043a\u043d\u0435\u0442\u0435 \u0442\u0443\u043a"],"here":["\u0442\u0443\u043a"],"go here":["\u043e\u0442\u0438\u0434\u0435\u0442\u0435 \u0442\u0443\u043a"],"more":["\u043e\u0449\u0435"],"more...":["\u043e\u0449\u0435..."],"more\u2026":["\u043e\u0449\u0435\u2026"],"details":["\u043f\u043e\u0434\u0440\u043e\u0431\u043d\u043e\u0441\u0442\u0438"],"more details":["\u043f\u043e\u0432\u0435\u0447\u0435 \u043f\u043e\u0434\u0440\u043e\u0431\u043d\u043e\u0441\u0442\u0438"],"link":["\u0432\u0440\u044a\u0437\u043a\u0430"],"this page":["\u0442\u0430\u0437\u0438 \u0441\u0442\u0440\u0430\u043d\u0438\u0446\u0430"],"continue":["\u043f\u0440\u043e\u0434\u044a\u043b\u0436\u0435\u0442\u0435"],"continue reading":["\u043f\u0440\u043e\u0434\u044a\u043b\u0436\u0435\u0442\u0435 \u0434\u0430 \u0447\u0435\u0442\u0435\u0442\u0435"],"read more":["\u043f\u0440\u043e\u0447\u0435\u0442\u0435\u0442\u0435 \u043e\u0449\u0435"],"open":["\u043e\u0442\u0432\u043e\u0440\u0438"],"download":["\u0438\u0437\u0442\u0435\u0433\u043b\u0438"],"button":["\u0431\u0443\u0442\u043e\u043d"],"keep reading":["\u043f\u0440\u043e\u0434\u044a\u043b\u0436\u0435\u0442\u0435 \u0434\u0430 \u0447\u0435\u0442\u0435\u0442\u0435"],"learn more":["\u043d\u0430\u0443\u0447\u0435\u0442\u0435 \u043f\u043e\u0432\u0435\u0447\u0435"]}}} No newline at end of file |
There was a problem hiding this comment.
💡 Verification agent
🧩 Analysis chain
Minified JSON hurts diff-ability; verify missing new key “Rescan This Page”.
- Storing minified translation files in the repo makes future reviews painful—every real string change will appear as one giant line diff. Consider keeping files pretty-printed in VCS and minifying only in the build/release pipeline (e.g. via
npm run build:translations). - Other locale files in this PR gained the key
"Rescan This Page". This BG file did not; double-check you’re not introducing an untranslated UI string.
🏁 Script executed:
#!/bin/bash
# Confirm whether the Bulgarian locale contains the new key
jq '..|objects|select(has("Rescan This Page"))' languages/accessibility-checker-bg_BG-ffd08c762bdabd23386ea03007811e0f.json
# Exit code 0 means found, 1 means missing.Length of output: 125
🏁 Script executed:
#!/bin/bash
# Search for the new key across all accessibility-checker locale JSON files
rg -n '"Rescan This Page"' -C2 languages/accessibility-checker-*.jsonLength of output: 65347
Pretty-print translation files for clearer diffs; no missing key in this bundle
- The file
languages/accessibility-checker-bg_BG-ffd08c762bdabd23386ea03007811e0f.jsonis a minified one-liner, making any change a massive diff. Please keep translation JSON pretty-printed in the repo and only minify as part of your build/release process (for example, vianpm run build:translations). - The string key
"Rescan This Page"does not belong in the Page Scanner bundle (pageScanner.bundle.js)—it’s only added to the Highlighter App bundle’s translations. No untranslated UI string needs to be added to this particular BG file.
🤖 Prompt for AI Agents
In languages/accessibility-checker-bg_BG-ffd08c762bdabd23386ea03007811e0f.json
at line 1, the translation JSON is minified into a single line, making diffs
hard to review. Reformat this JSON file to be pretty-printed with proper
indentation and line breaks for clearer diffs. Also, ensure that the translation
key "Rescan This Page" is not included in this Page Scanner bundle file, as it
belongs only to the Highlighter App bundle; remove it if present.
| } | ||
| } | ||
| } No newline at end of file | ||
| {"translation-revision-date":"YEAR-MO-DA HO:MI+ZONE","generator":"WP-CLI\/2.12.0","source":"build\/admin.bundle.js","domain":"messages","locale_data":{"messages":{"":{"domain":"messages","lang":"en","plural-forms":"nplurals=2; plural=(n != 1);"},"Get Pro to unlock this feature, opens in a new window.":["Selle funktsiooni avamiseks hangi Pro versioon, avaneb uues aknas."],"Saving...":["Salvestamine..."],"Settings saved successfully. You must %svisit the editor%s and save the post to rescan and remove fixed issues from Accessibility Checker reports.":["S\u00e4tted salvestati edukalt. Peate %sk\u00fclastama redaktorit%s ja salvestama postituse, et uuesti skaneerida ja eemaldada parandatud probleemid Accessibility Checkeri aruannetest."],"Settings saved successfully.":["Seaded edukalt salvestatud."],"Saving failed.":["Salvestamine eba\u00f5nnestus."],"Fix Settings":["Paranduste seaded"]}}} No newline at end of file |
There was a problem hiding this comment.
💡 Verification agent
🧩 Analysis chain
Estonian file still advertises lang:"en" – likely breaks lookup
locale_data.messages[""].lang is set to "en" even though the file path ( …/et-…json) implies Estonian.
When WP loads translations it matches the JSON’s lang header against the current locale; a mismatch can cause this file to be ignored entirely.
-"lang":"en"
+"lang":"et"Please update (and check other newly-minified files) so that each locale file reports its own language code.
🏁 Script executed:
#!/bin/bash
# Find all Accessibility Checker locale JSONs still reporting "lang":"en"
rg '"lang":"en"' -n languages/accessibility-checker-*.jsonLength of output: 148442
Update locale JSON headers for all languages
All files under languages/accessibility-checker-*.json still report "lang":"en", which will prevent WordPress from loading any translations. You need to replace the "lang":"en" entry in each JSON with its corresponding locale code. For example:
- languages/accessibility-checker-et-*.json →
"lang":"et" - languages/accessibility-checker-vi-*.json →
"lang":"vi" - languages/accessibility-checker-bg_BG-*.json →
"lang":"bg_BG"
… and so on for every<locale>in your filenames.
You can script it, for instance:
for file in languages/accessibility-checker-*-*.json; do
locale=$(basename "$file" | cut -d '-' -f 3 | sed 's/\..*//')
sed -i "s/\"lang\":\"en\"/\"lang\":\"${locale}\"/" "$file"
done• After updating, rerun your build/minification to ensure newly generated files carry the correct lang header.
• Double-check any other JSON localization artifacts for the same issue.
🤖 Prompt for AI Agents
In languages/accessibility-checker-et-2babf73ad0b848216944ffff693aa351.json at
line 1, the "lang" field is incorrectly set to "en" instead of the correct
locale code "et". Update the "lang" value to match the locale code derived from
the filename, replacing "en" with "et". After making this change, rerun the
build and minification process to ensure the updated locale header is reflected
in the generated files.
| } | ||
| } | ||
| } No newline at end of file | ||
| {"translation-revision-date":"YEAR-MO-DA HO:MI+ZONE","generator":"WP-CLI\/2.12.0","source":"build\/emailOptIn.bundle.js","domain":"messages","locale_data":{"messages":{"":{"domain":"messages","lang":"en","plural-forms":"nplurals=2; plural=(n != 1);"},"There was a problem. Please try again.":["Tekkis probleem. Palun proovige uuesti."],"Sorry, your submission failed. Please shorten your responses and try again.":["Vabandust, teie esitamine eba\u00f5nnestus. Palun l\u00fchendage oma vastuseid ja proovige uuesti."],"Sorry, your submission failed. Please try again.":["Vabandust, teie esitamine eba\u00f5nnestus. Palun proovige uuesti."]}}} No newline at end of file |
There was a problem hiding this comment.
Incorrect lang header value – should be et, not en
WordPress loads a locale JSON file only when the "lang" header matches the locale slug of the file name.
Keeping "lang":"en" in an …-et-….json file prevents this translation bundle from ever being selected at runtime.
-...,"lang":"en","plural-forms":"nplurals=2; plural=(n != 1);"}...
+...,"lang":"et","plural-forms":"nplurals=2; plural=(n != 1);"}...📝 Committable suggestion
‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.
| {"translation-revision-date":"YEAR-MO-DA HO:MI+ZONE","generator":"WP-CLI\/2.12.0","source":"build\/emailOptIn.bundle.js","domain":"messages","locale_data":{"messages":{"":{"domain":"messages","lang":"en","plural-forms":"nplurals=2; plural=(n != 1);"},"There was a problem. Please try again.":["Tekkis probleem. Palun proovige uuesti."],"Sorry, your submission failed. Please shorten your responses and try again.":["Vabandust, teie esitamine eba\u00f5nnestus. Palun l\u00fchendage oma vastuseid ja proovige uuesti."],"Sorry, your submission failed. Please try again.":["Vabandust, teie esitamine eba\u00f5nnestus. Palun proovige uuesti."]}}} | |
| {"translation-revision-date":"YEAR-MO-DA HO:MI+ZONE","generator":"WP-CLI\/2.12.0","source":"build\/emailOptIn.bundle.js","domain":"messages","locale_data":{"messages":{"":{"domain":"messages","lang":"et","plural-forms":"nplurals=2; plural=(n != 1);"},"There was a problem. Please try again.":["Tekkis probleem. Palun proovige uuesti."],"Sorry, your submission failed. Please shorten your responses and try again.":["Vabandust, teie esitamine ebaõnnestus. Palun lühendage oma vastuseid ja proovige uuesti."],"Sorry, your submission failed. Please try again.":["Vabandust, teie esitamine ebaõnnestus. Palun proovige uuesti."]}}} |
🤖 Prompt for AI Agents
In languages/accessibility-checker-et-4aeb45733c7671c6641789798428b69d.json at
line 1, the "lang" header is incorrectly set to "en" instead of "et". Update the
"lang" value in the JSON from "en" to "et" to match the locale slug in the file
name, ensuring WordPress correctly loads this translation bundle at runtime.
| } | ||
| } | ||
| } No newline at end of file | ||
| {"translation-revision-date":"YEAR-MO-DA HO:MI+ZONE","generator":"WP-CLI\/2.12.0","source":"build\/frontendFixes.bundle.js","domain":"messages","locale_data":{"messages":{"":{"domain":"messages","lang":"en","plural-forms":"nplurals=2; plural=(n != 1);"},"opens a new window":["\u00faj ablakot nyit"],"EDAC: Did not find a matching target ID on the page for the skip link.":["EDAC: Nem tal\u00e1lhat\u00f3 megfelel\u0151 c\u00e9l azonos\u00edt\u00f3 az oldalon az ugr\u00f3linkhez."],"EDAC: Error updating history for skip link.":["EDAC: Hiba t\u00f6rt\u00e9nt az ugr\u00f3linkhez tartoz\u00f3 el\u0151zm\u00e9nyek friss\u00edt\u00e9sekor."]}}} No newline at end of file |
There was a problem hiding this comment.
🛠️ Refactor suggestion
"lang":"en" metadata looks incorrect for a Hungarian translation file
The metadata block still declares the language as English ("lang":"en").
For locale hu_HU this should normally be "hu" (or "hu_HU"-style, depending on your tooling).
Leaving it as "en" can break locale loading and fallback logic in WP i18n.
- "lang":"en",
+ "lang":"hu",Please verify against other translation files and regenerate if necessary.
📝 Committable suggestion
‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.
| {"translation-revision-date":"YEAR-MO-DA HO:MI+ZONE","generator":"WP-CLI\/2.12.0","source":"build\/frontendFixes.bundle.js","domain":"messages","locale_data":{"messages":{"":{"domain":"messages","lang":"en","plural-forms":"nplurals=2; plural=(n != 1);"},"opens a new window":["\u00faj ablakot nyit"],"EDAC: Did not find a matching target ID on the page for the skip link.":["EDAC: Nem tal\u00e1lhat\u00f3 megfelel\u0151 c\u00e9l azonos\u00edt\u00f3 az oldalon az ugr\u00f3linkhez."],"EDAC: Error updating history for skip link.":["EDAC: Hiba t\u00f6rt\u00e9nt az ugr\u00f3linkhez tartoz\u00f3 el\u0151zm\u00e9nyek friss\u00edt\u00e9sekor."]}}} | |
| {"translation-revision-date":"YEAR-MO-DA HO:MI+ZONE","generator":"WP-CLI\/2.12.0","source":"build\/frontendFixes.bundle.js","domain":"messages","locale_data":{"messages":{"":{"domain":"messages","lang":"hu","plural-forms":"nplurals=2; plural=(n != 1);"},"opens a new window":["\u00faj ablakot nyit"],"EDAC: Did not find a matching target ID on the page for the skip link.":["EDAC: Nem tal\u00e1lhat\u00f3 megfelel\u0151 c\u00e9l azonos\u00edt\u00f3 az oldalon az ugr\u00f3linkhez."],"EDAC: Error updating history for skip link.":["EDAC: Hiba t\u00f6rt\u00e9nt az ugr\u00f3linkhez tartoz\u00f3 el\u0151zm\u00e9nyek friss\u00edt\u00e9sekor."]}}} |
🤖 Prompt for AI Agents
In languages/accessibility-checker-hu_HU-95b093794875bec5eeac2e02bfe32541.json
at line 1, the "lang" metadata is incorrectly set to "en" for a Hungarian
translation file. Update the "lang" value to "hu" or "hu_HU" to correctly
reflect the Hungarian locale. Verify this change against other translation files
and regenerate the file if needed to ensure proper locale loading and fallback
in WP i18n.
| } | ||
| } | ||
| } No newline at end of file | ||
| {"translation-revision-date":"YEAR-MO-DA HO:MI+ZONE","generator":"WP-CLI\/2.12.0","source":"build\/admin.bundle.js","domain":"messages","locale_data":{"messages":{"":{"domain":"messages","lang":"en","plural-forms":"nplurals=2; plural=(n != 1);"},"Get Pro to unlock this feature, opens in a new window.":["\uc774 \uae30\ub2a5\uc744 \uc0ac\uc6a9\ud558\ub824\uba74 Pro \ubc84\uc804\uc73c\ub85c \uc5c5\uadf8\ub808\uc774\ub4dc\ud558\uc138\uc694. \uc0c8 \ucc3d\uc5d0\uc11c \uc5f4\ub9bd\ub2c8\ub2e4."],"Saving...":["\uc800\uc7a5 \uc911..."],"Settings saved successfully. You must %svisit the editor%s and save the post to rescan and remove fixed issues from Accessibility Checker reports.":["\uc124\uc815\uc774 \uc131\uacf5\uc801\uc73c\ub85c \uc800\uc7a5\ub418\uc5c8\uc2b5\ub2c8\ub2e4. %s\ud3b8\uc9d1\uae30\ub97c \ubc29\ubb38%s\ud558\uc5ec \uac8c\uc2dc\ubb3c\uc744 \uc800\uc7a5\ud574\uc57c Accessibility Checker \ubcf4\uace0\uc11c\uc5d0\uc11c \uc218\uc815\ub41c \ubb38\uc81c\ub97c \ub2e4\uc2dc \uac80\uc0ac\ud558\uace0 \uc81c\uac70\ud560 \uc218 \uc788\uc2b5\ub2c8\ub2e4."],"Settings saved successfully.":["\uc124\uc815\uc774 \uc131\uacf5\uc801\uc73c\ub85c \uc800\uc7a5\ub418\uc5c8\uc2b5\ub2c8\ub2e4."],"Saving failed.":["\uc800\uc7a5\uc5d0 \uc2e4\ud328\ud588\uc2b5\ub2c8\ub2e4."],"Fix Settings":["\uc124\uc815 \uc218\uc815"]}}} No newline at end of file |
There was a problem hiding this comment.
Missing new translation key “Rescan This Page”.
Other locale files in this PR introduce a translation for “Rescan This Page”, but the Korean file does not. At runtime this will fall back to the default (English) string, breaking language consistency.
Suggested patch (minified style kept for consistency):
-..."Fix Settings":["\uc124\uc815 \uc218\uc815"]}}}
+..."Fix Settings":["\uc124\uc815 \uc218\uc815"],"Rescan This Page":["\uc774 \ud398\uc774\uc9c0 \ub2e4\uc2dc \uac80\uc0ac"]}}}🤖 Prompt for AI Agents
In languages/accessibility-checker-ko_KR-2babf73ad0b848216944ffff693aa351.json
at line 1, add the missing translation key "Rescan This Page" with its Korean
translation to maintain language consistency and prevent fallback to English at
runtime. Insert this key-value pair in the "messages" object alongside the
existing translations.
| } | ||
| } | ||
| } No newline at end of file | ||
| {"translation-revision-date":"YEAR-MO-DA HO:MI+ZONE","generator":"WP-CLI\/2.12.0","source":"build\/frontendHighlighterApp.bundle.js","domain":"messages","locale_data":{"messages":{"":{"domain":"messages","lang":"en","plural-forms":"nplurals=2; plural=(n != 1);"},"Save":["Ulo\u017ei\u0165"],"Saving...":["Uklad\u00e1 sa..."],"Settings saved successfully. You must %svisit the editor%s and save the post to rescan and remove fixed issues from Accessibility Checker reports.":["Nastavenia boli \u00faspe\u0161ne ulo\u017een\u00e9. Mus\u00edte %snav\u0161t\u00edvi\u0165 editor%s a ulo\u017ei\u0165 pr\u00edspevok, aby sa op\u00e4tovne skontrolovali a odstr\u00e1nili opraven\u00e9 probl\u00e9my zo spr\u00e1v Accessibility Checker."],"Settings saved successfully.":["Nastavenia boli \u00faspe\u0161ne ulo\u017een\u00e9."],"Saving failed.":["Ulo\u017eenie zlyhalo."],"Fix Settings":["Nastavenia opravy"],"Close fixes modal":["Zatvori\u0165 mod\u00e1lne okno s opravami"],"Rescan This Page":["Preskenova\u0165 t\u00fato str\u00e1nku"],"Disable Page Styles":["Vypn\u00fa\u0165 \u0161t\u00fdly str\u00e1nky"],"Disable Styles":["Vypn\u00fa\u0165 \u0161t\u00fdly"],"An error occurred when loading the issues.":["Pri na\u010d\u00edtavan\u00ed probl\u00e9mov sa vyskytla chyba."],"Show Code":["Zobrazi\u0165 k\u00f3d"],"Issue type:":["Typ probl\u00e9mu:"],"Enable Styles":["Zapn\u00fa\u0165 \u0161t\u00fdly"],"There are no settings to display.":["Nie s\u00fa k dispoz\u00edcii \u017eiadne nastavenia na zobrazenie."],"These settings enable global fixes across your entire site. Pages may need to be resaved or a full site scan run to see fixes reflected in reports.":["Tieto nastavenia umo\u017e\u0148uj\u00fa glob\u00e1lne opravy na celom va\u0161om webe. M\u00f4\u017ee by\u0165 potrebn\u00e9 znovu ulo\u017ei\u0165 str\u00e1nky alebo spusti\u0165 \u00fapln\u00e9 skenovanie webu, aby sa opravy prejavili v spr\u00e1vach."],"No issues detected.":["Neboli zisten\u00e9 \u017eiadne probl\u00e9my."],"error":["chyba","chyby"],"warning":["upozornenie","upozornenia"],"and":["a"],"ignored issue":["ignorovan\u00fd probl\u00e9m","ignorovan\u00e9 probl\u00e9my"],"detected.":["zisten\u00fdch."],"Scanner function not found.":["Skenovacia funkcia nebola n\u00e1jden\u00e1."],"Scanning...":["Prebieha skenovanie..."],"No violations found, skipping save.":["Neboli n\u00e1jden\u00e9 \u017eiadne poru\u0161enia, preskakujem ulo\u017eenie."],"Missing postId or nonce.":["Ch\u00fdba postId alebo nonce."],"Accessibility scan error.":["Chyba pri skenovan\u00ed pr\u00edstupnosti."],"Error saving scan results.":["Chyba pri ukladan\u00ed v\u00fdsledkov skenovania."]}}} No newline at end of file |
There was a problem hiding this comment.
💡 Verification agent
❓ Verification inconclusive
Locale metadata appears to be set for English, not Slovak
The "lang":"en" value and the English plural-forms (nplurals=2; plural=(n != 1);) do not match the sk_SK locale.
Correct Slovak metadata should be roughly:
"lang":"sk" and nplurals=3; plural=(n == 1) ? 0 : (n >= 2 && n <= 4) ? 1 : 2.
Incorrect metadata can break WordPress translation loading or cause pluralisation bugs.
-{"domain":"messages","lang":"en","plural-forms":"nplurals=2; plural=(n != 1);"}
+{"domain":"messages","lang":"sk","plural-forms":"nplurals=3; plural=(n==1)?0:(n>=2 && n<=4)?1:2;"}Please confirm whether this was an intentional override or a long-standing error in the source POT file. If unintentional, updating the metadata will prevent runtime localisation issues.
Fix metadata to match Slovak locale in JSON translation
The metadata header currently uses English locale settings, which will break translation loading and pluralization for Slovak.
Locations to update:
- File:
languages/accessibility-checker-sk_SK-b93b9e514c44a41f97246123aa57f5c4.json - Inside the
locale_data.messages[""]header object
Apply this change:
- {"domain":"messages","lang":"en","plural-forms":"nplurals=2; plural=(n != 1);"}
+ {"domain":"messages","lang":"sk","plural-forms":"nplurals=3; plural=(n == 1) ? 0 : (n >= 2 && n <= 4) ? 1 : 2;"}📝 Committable suggestion
‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.
| {"translation-revision-date":"YEAR-MO-DA HO:MI+ZONE","generator":"WP-CLI\/2.12.0","source":"build\/frontendHighlighterApp.bundle.js","domain":"messages","locale_data":{"messages":{"":{"domain":"messages","lang":"en","plural-forms":"nplurals=2; plural=(n != 1);"},"Save":["Ulo\u017ei\u0165"],"Saving...":["Uklad\u00e1 sa..."],"Settings saved successfully. You must %svisit the editor%s and save the post to rescan and remove fixed issues from Accessibility Checker reports.":["Nastavenia boli \u00faspe\u0161ne ulo\u017een\u00e9. Mus\u00edte %snav\u0161t\u00edvi\u0165 editor%s a ulo\u017ei\u0165 pr\u00edspevok, aby sa op\u00e4tovne skontrolovali a odstr\u00e1nili opraven\u00e9 probl\u00e9my zo spr\u00e1v Accessibility Checker."],"Settings saved successfully.":["Nastavenia boli \u00faspe\u0161ne ulo\u017een\u00e9."],"Saving failed.":["Ulo\u017eenie zlyhalo."],"Fix Settings":["Nastavenia opravy"],"Close fixes modal":["Zatvori\u0165 mod\u00e1lne okno s opravami"],"Rescan This Page":["Preskenova\u0165 t\u00fato str\u00e1nku"],"Disable Page Styles":["Vypn\u00fa\u0165 \u0161t\u00fdly str\u00e1nky"],"Disable Styles":["Vypn\u00fa\u0165 \u0161t\u00fdly"],"An error occurred when loading the issues.":["Pri na\u010d\u00edtavan\u00ed probl\u00e9mov sa vyskytla chyba."],"Show Code":["Zobrazi\u0165 k\u00f3d"],"Issue type:":["Typ probl\u00e9mu:"],"Enable Styles":["Zapn\u00fa\u0165 \u0161t\u00fdly"],"There are no settings to display.":["Nie s\u00fa k dispoz\u00edcii \u017eiadne nastavenia na zobrazenie."],"These settings enable global fixes across your entire site. Pages may need to be resaved or a full site scan run to see fixes reflected in reports.":["Tieto nastavenia umo\u017e\u0148uj\u00fa glob\u00e1lne opravy na celom va\u0161om webe. M\u00f4\u017ee by\u0165 potrebn\u00e9 znovu ulo\u017ei\u0165 str\u00e1nky alebo spusti\u0165 \u00fapln\u00e9 skenovanie webu, aby sa opravy prejavili v spr\u00e1vach."],"No issues detected.":["Neboli zisten\u00e9 \u017eiadne probl\u00e9my."],"error":["chyba","chyby"],"warning":["upozornenie","upozornenia"],"and":["a"],"ignored issue":["ignorovan\u00fd probl\u00e9m","ignorovan\u00e9 probl\u00e9my"],"detected.":["zisten\u00fdch."],"Scanner function not found.":["Skenovacia funkcia nebola n\u00e1jden\u00e1."],"Scanning...":["Prebieha skenovanie..."],"No violations found, skipping save.":["Neboli n\u00e1jden\u00e9 \u017eiadne poru\u0161enia, preskakujem ulo\u017eenie."],"Missing postId or nonce.":["Ch\u00fdba postId alebo nonce."],"Accessibility scan error.":["Chyba pri skenovan\u00ed pr\u00edstupnosti."],"Error saving scan results.":["Chyba pri ukladan\u00ed v\u00fdsledkov skenovania."]}}} | |
| { | |
| "translation-revision-date": "YEAR-MO-DA HO:MI+ZONE", | |
| "generator": "WP-CLI/2.12.0", | |
| "source": "build/frontendHighlighterApp.bundle.js", | |
| "domain": "messages", | |
| "locale_data": { | |
| "messages": { | |
| "": { | |
| "domain": "messages", | |
| "lang": "sk", | |
| "plural-forms": "nplurals=3; plural=(n == 1) ? 0 : (n >= 2 && n <= 4) ? 1 : 2;" | |
| }, | |
| "Save": ["Uložiť"], | |
| "Saving...": ["Ukladá sa..."], | |
| "Settings saved successfully. You must %svisit the editor%s and save the post to rescan and remove fixed issues from Accessibility Checker reports.": [ | |
| "Nastavenia boli úspešne uložené. Musíte %snavštíviť editor%s a uložiť príspevok, aby sa opätovne skontrolovali a odstránili opravené problémy zo správ Accessibility Checker." | |
| ], | |
| "Settings saved successfully.": ["Nastavenia boli úspešne uložené."], | |
| "Saving failed.": ["Uloženie zlyhalo."], | |
| "Fix Settings": ["Nastavenia opravy"], | |
| "Close fixes modal": ["Zatvoriť modálne okno s opravami"], | |
| "Rescan This Page": ["Preskenovať túto stránku"], | |
| "Disable Page Styles": ["Vypnúť štýly stránky"], | |
| "Disable Styles": ["Vypnúť štýly"], | |
| "An error occurred when loading the issues.": ["Pri načítavaní problémov sa vyskytla chyba."], | |
| "Show Code": ["Zobraziť kód"], | |
| "Issue type:": ["Typ problému:"], | |
| "Enable Styles": ["Zapnúť štýly"], | |
| "There are no settings to display.": ["Nie sú k dispozícii žiadne nastavenia na zobrazenie."], | |
| "These settings enable global fixes across your entire site. Pages may need to be resaved or a full site scan run to see fixes reflected in reports.": [ | |
| "Tieto nastavenia umožňujú globálne opravy na celom webe. Môže byť potrebné znova uložiť stránky alebo spustiť úplné skenovanie webu, aby sa opravy prejavili vo správach." | |
| ], | |
| "No issues detected.": ["Neboli zistené žiadne problémy."], | |
| "error": ["chyba", "chyby"], | |
| "warning": ["upozornenie", "upozornenia"], | |
| "and": ["a"], | |
| "ignored issue": ["ignorovaný problém", "ignorované problémy"], | |
| "detected.": ["zistených."], | |
| "Scanner function not found.": ["Skenovacia funkcia nebola nájdená."], | |
| "Scanning...": ["Prebieha skenovanie..."], | |
| "No violations found, skipping save.": ["Neboli nájdené žiadne porušenia, preskakujem uloženie."], | |
| "Missing postId or nonce.": ["Chýba postId alebo nonce."], | |
| "Accessibility scan error.": ["Chyba pri skenovaní prístupnosti."], | |
| "Error saving scan results.": ["Chyba pri ukladaní výsledkov skenovania."] | |
| } | |
| } | |
| } |
🤖 Prompt for AI Agents
In languages/accessibility-checker-sk_SK-b93b9e514c44a41f97246123aa57f5c4.json
at line 1, the metadata header under locale_data.messages[""] incorrectly uses
English locale settings, which will cause translation loading and pluralization
issues for Slovak. Update the "lang" field to "sk_SK" and adjust the
"plural-forms" to match Slovak pluralization rules. Ensure the
"translation-revision-date" is set correctly if needed.
| } | ||
| } | ||
| } No newline at end of file | ||
| {"translation-revision-date":"YEAR-MO-DA HO:MI+ZONE","generator":"WP-CLI\/2.12.0","source":"build\/frontendHighlighterApp.bundle.js","domain":"messages","locale_data":{"messages":{"":{"domain":"messages","lang":"en","plural-forms":"nplurals=2; plural=(n != 1);"},"Save":["Kaydet"],"Saving...":["Kaydediliyor..."],"Settings saved successfully. You must %svisit the editor%s and save the post to rescan and remove fixed issues from Accessibility Checker reports.":["Ayarlar ba\u015far\u0131yla kaydedildi. Accessibility Checker raporlar\u0131ndan d\u00fczeltilmi\u015f sorunlar\u0131 yeniden taramak ve kald\u0131rmak i\u00e7in %sedit\u00f6r\u00fc ziyaret etmeli%s ve yaz\u0131y\u0131 kaydetmelisin."],"Settings saved successfully.":["Ayarlar ba\u015far\u0131yla kaydedildi."],"Saving failed.":["Kaydetme ba\u015far\u0131s\u0131z oldu."],"Fix Settings":["Ayarlar\u0131 d\u00fczelt"],"Close fixes modal":["D\u00fczeltmeler modal\u0131n\u0131 kapat"],"Rescan This Page":["Bu sayfay\u0131 yeniden tara"],"Disable Page Styles":["Sayfa stillerini devre d\u0131\u015f\u0131 b\u0131rak"],"Disable Styles":["Stilleri devre d\u0131\u015f\u0131 b\u0131rak"],"An error occurred when loading the issues.":["Sorunlar y\u00fcklenirken bir hata olu\u015ftu."],"Show Code":["Kodu g\u00f6ster"],"Issue type:":["Sorun t\u00fcr\u00fc:"],"Enable Styles":["Stilleri etkinle\u015ftir"],"There are no settings to display.":["G\u00f6r\u00fcnt\u00fclenecek ayar yok."],"These settings enable global fixes across your entire site. Pages may need to be resaved or a full site scan run to see fixes reflected in reports.":["Bu ayarlar, t\u00fcm siteniz genelinde global d\u00fczeltmeleri etkinle\u015ftirir. D\u00fczeltmelerin raporlarda g\u00f6r\u00fcnmesi i\u00e7in sayfalar\u0131n yeniden kaydedilmesi veya tam site taramas\u0131 yap\u0131lmas\u0131 gerekebilir."],"No issues detected.":["Hi\u00e7bir sorun tespit edilmedi."],"error":["hata","hata"],"warning":["uyar\u0131","uyar\u0131"],"and":["ve"],"ignored issue":["g\u00f6z ard\u0131 edilen sorun","g\u00f6z ard\u0131 edilen sorun"],"detected.":["tespit edildi."],"Scanner function not found.":["Taray\u0131c\u0131 i\u015flevi bulunamad\u0131."],"Scanning...":["Taran\u0131yor..."],"No violations found, skipping save.":["Hi\u00e7bir ihlal bulunamad\u0131, kaydetme atlan\u0131yor."],"Missing postId or nonce.":["PostId veya nonce eksik."],"Accessibility scan error.":["Eri\u015filebilirlik tarama hatas\u0131."],"Error saving scan results.":["Tarama sonu\u00e7lar\u0131 kaydedilirken hata olu\u015ftu."]}}} No newline at end of file |
There was a problem hiding this comment.
Incorrect lang header – should be "tr" not "en".
The locale header inside locale_data.messages[""] still declares "lang":"en", which mismatches the file’s Turkish locale (tr_TR). WP-i18n tooling relies on this value; the mismatch can prevent the translations from being loaded.
- "lang":"en"
+ "lang":"tr"📝 Committable suggestion
‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.
| {"translation-revision-date":"YEAR-MO-DA HO:MI+ZONE","generator":"WP-CLI\/2.12.0","source":"build\/frontendHighlighterApp.bundle.js","domain":"messages","locale_data":{"messages":{"":{"domain":"messages","lang":"en","plural-forms":"nplurals=2; plural=(n != 1);"},"Save":["Kaydet"],"Saving...":["Kaydediliyor..."],"Settings saved successfully. You must %svisit the editor%s and save the post to rescan and remove fixed issues from Accessibility Checker reports.":["Ayarlar ba\u015far\u0131yla kaydedildi. Accessibility Checker raporlar\u0131ndan d\u00fczeltilmi\u015f sorunlar\u0131 yeniden taramak ve kald\u0131rmak i\u00e7in %sedit\u00f6r\u00fc ziyaret etmeli%s ve yaz\u0131y\u0131 kaydetmelisin."],"Settings saved successfully.":["Ayarlar ba\u015far\u0131yla kaydedildi."],"Saving failed.":["Kaydetme ba\u015far\u0131s\u0131z oldu."],"Fix Settings":["Ayarlar\u0131 d\u00fczelt"],"Close fixes modal":["D\u00fczeltmeler modal\u0131n\u0131 kapat"],"Rescan This Page":["Bu sayfay\u0131 yeniden tara"],"Disable Page Styles":["Sayfa stillerini devre d\u0131\u015f\u0131 b\u0131rak"],"Disable Styles":["Stilleri devre d\u0131\u015f\u0131 b\u0131rak"],"An error occurred when loading the issues.":["Sorunlar y\u00fcklenirken bir hata olu\u015ftu."],"Show Code":["Kodu g\u00f6ster"],"Issue type:":["Sorun t\u00fcr\u00fc:"],"Enable Styles":["Stilleri etkinle\u015ftir"],"There are no settings to display.":["G\u00f6r\u00fcnt\u00fclenecek ayar yok."],"These settings enable global fixes across your entire site. Pages may need to be resaved or a full site scan run to see fixes reflected in reports.":["Bu ayarlar, t\u00fcm siteniz genelinde global d\u00fczeltmeleri etkinle\u015ftirir. D\u00fczeltmelerin raporlarda g\u00f6r\u00fcnmesi i\u00e7in sayfalar\u0131n yeniden kaydedilmesi veya tam site taramas\u0131 yap\u0131lmas\u0131 gerekebilir."],"No issues detected.":["Hi\u00e7bir sorun tespit edilmedi."],"error":["hata","hata"],"warning":["uyar\u0131","uyar\u0131"],"and":["ve"],"ignored issue":["g\u00f6z ard\u0131 edilen sorun","g\u00f6z ard\u0131 edilen sorun"],"detected.":["tespit edildi."],"Scanner function not found.":["Taray\u0131c\u0131 i\u015flevi bulunamad\u0131."],"Scanning...":["Taran\u0131yor..."],"No violations found, skipping save.":["Hi\u00e7bir ihlal bulunamad\u0131, kaydetme atlan\u0131yor."],"Missing postId or nonce.":["PostId veya nonce eksik."],"Accessibility scan error.":["Eri\u015filebilirlik tarama hatas\u0131."],"Error saving scan results.":["Tarama sonu\u00e7lar\u0131 kaydedilirken hata olu\u015ftu."]}}} | |
| { | |
| "translation-revision-date":"YEAR-MO-DA HO:MI+ZONE", | |
| "generator":"WP-CLI\/2.12.0", | |
| "source":"build\/frontendHighlighterApp.bundle.js", | |
| "domain":"messages", | |
| "locale_data":{ | |
| "messages":{ | |
| "":{ | |
| "domain":"messages", | |
| "lang":"tr", | |
| "plural-forms":"nplurals=2; plural=(n != 1);" | |
| }, | |
| "Save":["Kaydet"], | |
| "Saving...":["Kaydediliyor..."], | |
| "Settings saved successfully. You must %svisit the editor%s and save the post to rescan and remove fixed issues from Accessibility Checker reports.":["Ayarlar başarıyla kaydedildi. Accessibility Checker raporlarındaki düzeltilmiş sorunları yeniden taramak ve kaldırmak için %seditörü ziyaret etmeli%s ve yazıyı kaydetmelisin."], | |
| "Settings saved successfully.":["Ayarlar başarıyla kaydedildi."], | |
| "Saving failed.":["Kaydetme başarısız oldu."], | |
| "Fix Settings":["Ayarları düzelt"], | |
| "Close fixes modal":["Düzeltmeler modalını kapat"], | |
| "Rescan This Page":["Bu sayfayı yeniden tara"], | |
| "Disable Page Styles":["Sayfa stillerini devre dışı bırak"], | |
| "Disable Styles":["Stilleri devre dışı bırak"], | |
| "An error occurred when loading the issues.":["Sorunlar yüklenirken bir hata oluştu."], | |
| "Show Code":["Kodu göster"], | |
| "Issue type:":["Sorun türü:"], | |
| "Enable Styles":["Stilleri etkinleştir"], | |
| "There are no settings to display.":["Görüntülenecek ayar yok."], | |
| "These settings enable global fixes across your entire site. Pages may need to be resaved or a full site scan run to see fixes reflected in reports.":["Bu ayarlar, tüm siteniz genelinde global düzeltmeleri etkinleştirir. Düzeltmelerin raporlarda görünmesi için sayfaların yeniden kaydedilmesi veya tam site taraması yapılması gerekebilir."], | |
| "No issues detected.":["Hiçbir sorun tespit edilmedi."], | |
| "error":["hata","hata"], | |
| "warning":["uyarı","uyarı"], | |
| "and":["ve"], | |
| "ignored issue":["göz ardı edilen sorun","göz ardı edilen sorun"], | |
| "detected.":["tespit edildi."], | |
| "Scanner function not found.":["Tarayıcı işlevi bulunamadı."], | |
| "Scanning...":["Taranıyor..."], | |
| "No violations found, skipping save.":["Hiçbir ihlal bulunamadı, kaydetme atlanıyor."], | |
| "Missing postId or nonce.":["PostId veya nonce eksik."], | |
| "Accessibility scan error.":["Erişilebilirlik tarama hatası."], | |
| "Error saving scan results.":["Tarama sonuçları kaydedilirken hata oluştu."] | |
| } | |
| } | |
| } |
🤖 Prompt for AI Agents
In languages/accessibility-checker-tr_TR-b93b9e514c44a41f97246123aa57f5c4.json
at line 1, the lang header inside locale_data.messages[""] is incorrectly set to
"en" instead of "tr". Update the "lang" value from "en" to "tr" to correctly
reflect the Turkish locale and ensure WP-i18n tooling loads the translations
properly.
| } | ||
| } | ||
| } No newline at end of file | ||
| {"translation-revision-date":"YEAR-MO-DA HO:MI+ZONE","generator":"WP-CLI\/2.12.0","source":"build\/editorApp.bundle.js","domain":"messages","locale_data":{"messages":{"":{"domain":"messages","lang":"en","plural-forms":"nplurals=2; plural=(n != 1);"},"Clear Issues":["Sorunlar\u0131 temizle"],"This will clear all issues for this post. A save will be required to trigger a fresh scan of the post content. Do you want to continue?":["Bu, bu g\u00f6nderi i\u00e7in t\u00fcm sorunlar\u0131 temizleyecektir. G\u00f6nderi i\u00e7eri\u011finin yeniden taranmas\u0131n\u0131 tetiklemek i\u00e7in bir kaydetme i\u015flemi gerekecektir. Devam etmek istiyor musunuz?"],"Clearing...":["Temizleniyor..."],"Issues cleared successfully.":["Sorunlar ba\u015far\u0131yla temizlendi."],"Failed to clear issues.":["Sorunlar temizlenemedi."],"An error occurred while clearing issues.":["Sorunlar\u0131 temizlerken bir hata olu\u015ftu."]}}} No newline at end of file |
There was a problem hiding this comment.
🛠️ Refactor suggestion
Plural-form rule is wrong for Turkish
Turkish has a single plural form (nplurals=1; plural=0;).
Keeping the English rule (nplurals=2; plural=(n != 1);) will make the __n() calls return the wrong string or trigger warnings.
Same diff as above applies.
🤖 Prompt for AI Agents
In languages/accessibility-checker-tr_TR-c6b6e50c6acd7c42c9d09e857f9ed6b0.json
at line 1, the plural-forms rule for Turkish is incorrect; it currently uses the
English rule with two plurals. Update the plural-forms to "nplurals=1;
plural=0;" to correctly reflect Turkish grammar and prevent wrong string returns
or warnings in __n() calls.
lang is set to "en" instead of "tr"
The locale header still reports English ("lang":"en") even though this is the Turkish (tr_TR) catalog. WordPress uses this field to decide whether to load the file; a mismatch can cause the entire translation set to be ignored at runtime.
Proposed fix (extract only the changed fragment for clarity):
-{"":{"domain":"messages","lang":"en","plural-forms":"nplurals=2; plural=(n != 1);"} ...
+{"":{"domain":"messages","lang":"tr","plural-forms":"nplurals=1; plural=0;"} ...📝 Committable suggestion
‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.
| {"translation-revision-date":"YEAR-MO-DA HO:MI+ZONE","generator":"WP-CLI\/2.12.0","source":"build\/editorApp.bundle.js","domain":"messages","locale_data":{"messages":{"":{"domain":"messages","lang":"en","plural-forms":"nplurals=2; plural=(n != 1);"},"Clear Issues":["Sorunlar\u0131 temizle"],"This will clear all issues for this post. A save will be required to trigger a fresh scan of the post content. Do you want to continue?":["Bu, bu g\u00f6nderi i\u00e7in t\u00fcm sorunlar\u0131 temizleyecektir. G\u00f6nderi i\u00e7eri\u011finin yeniden taranmas\u0131n\u0131 tetiklemek i\u00e7in bir kaydetme i\u015flemi gerekecektir. Devam etmek istiyor musunuz?"],"Clearing...":["Temizleniyor..."],"Issues cleared successfully.":["Sorunlar ba\u015far\u0131yla temizlendi."],"Failed to clear issues.":["Sorunlar temizlenemedi."],"An error occurred while clearing issues.":["Sorunlar\u0131 temizlerken bir hata olu\u015ftu."]}}} | |
| { | |
| "translation-revision-date":"YEAR-MO-DA HO:MI+ZONE", | |
| "generator":"WP-CLI/2.12.0", | |
| "source":"build/editorApp.bundle.js", | |
| "domain":"messages", | |
| "locale_data":{ | |
| "messages":{ | |
| "":{ | |
| "domain":"messages", | |
| "lang":"tr", | |
| "plural-forms":"nplurals=1; plural=0;" | |
| }, | |
| "Clear Issues":["Sorunları temizle"], | |
| "This will clear all issues for this post. A save will be required to trigger a fresh scan of the post content. Do you want to continue?":["Bu, bu gönderi için tüm sorunları temizleyecektir. Gönderi içeriğinin yeniden taranmasını tetiklemek için bir kaydetme işlemi gerekecektir. Devam etmek istiyor musunuz?"], | |
| "Clearing...":["Temizleniyor..."], | |
| "Issues cleared successfully.":["Sorunlar başarıyla temizlendi."], | |
| "Failed to clear issues.":["Sorunlar temizlenemedi."], | |
| "An error occurred while clearing issues.":["Sorunları temizlerken bir hata oluştu."] | |
| } | |
| } | |
| } |
🤖 Prompt for AI Agents
In languages/accessibility-checker-tr_TR-c6b6e50c6acd7c42c9d09e857f9ed6b0.json
at line 1, the "lang" attribute is incorrectly set to "en" instead of "tr".
Update the "lang" value from "en" to "tr" in the locale_data messages header to
correctly reflect the Turkish locale and ensure WordPress loads the translation
file properly.
| } | ||
| } | ||
| } No newline at end of file | ||
| {"translation-revision-date":"YEAR-MO-DA HO:MI+ZONE","generator":"WP-CLI\/2.12.0","source":"build\/frontendHighlighterApp.bundle.js","domain":"messages","locale_data":{"messages":{"":{"domain":"messages","lang":"en","plural-forms":"nplurals=2; plural=(n != 1);"},"Save":["\u0417\u0431\u0435\u0440\u0435\u0433\u0442\u0438"],"Saving...":["\u0417\u0431\u0435\u0440\u0435\u0436\u0435\u043d\u043d\u044f..."],"Settings saved successfully. You must %svisit the editor%s and save the post to rescan and remove fixed issues from Accessibility Checker reports.":["\u041d\u0430\u043b\u0430\u0448\u0442\u0443\u0432\u0430\u043d\u043d\u044f \u0443\u0441\u043f\u0456\u0448\u043d\u043e \u0437\u0431\u0435\u0440\u0435\u0436\u0435\u043d\u043e. \u0412\u0438 \u043c\u0430\u0454\u0442\u0435 %s\u0432\u0456\u0434\u0432\u0456\u0434\u0430\u0442\u0438 \u0440\u0435\u0434\u0430\u043a\u0442\u043e\u0440%s \u0456 \u0437\u0431\u0435\u0440\u0435\u0433\u0442\u0438 \u0434\u043e\u043f\u0438\u0441, \u0449\u043e\u0431 \u043f\u043e\u0432\u0442\u043e\u0440\u043d\u043e \u043f\u0440\u043e\u0441\u043a\u0430\u043d\u0443\u0432\u0430\u0442\u0438 \u0442\u0430 \u0432\u0438\u0434\u0430\u043b\u0438\u0442\u0438 \u0432\u0438\u043f\u0440\u0430\u0432\u043b\u0435\u043d\u0456 \u043f\u0440\u043e\u0431\u043b\u0435\u043c\u0438 \u0437\u0456 \u0437\u0432\u0456\u0442\u0456\u0432 Accessibility Checker."],"Settings saved successfully.":["\u041d\u0430\u043b\u0430\u0448\u0442\u0443\u0432\u0430\u043d\u043d\u044f \u0443\u0441\u043f\u0456\u0448\u043d\u043e \u0437\u0431\u0435\u0440\u0435\u0436\u0435\u043d\u043e."],"Saving failed.":["\u041d\u0435 \u0432\u0434\u0430\u043b\u043e\u0441\u044f \u0437\u0431\u0435\u0440\u0435\u0433\u0442\u0438."],"Fix Settings":["\u041d\u0430\u043b\u0430\u0448\u0442\u0443\u0432\u0430\u043d\u043d\u044f \u0432\u0438\u043f\u0440\u0430\u0432\u043b\u0435\u043d\u044c"],"Close fixes modal":["\u0417\u0430\u043a\u0440\u0438\u0442\u0438 \u043c\u043e\u0434\u0430\u043b\u044c\u043d\u0435 \u0432\u0456\u043a\u043d\u043e \u0432\u0438\u043f\u0440\u0430\u0432\u043b\u0435\u043d\u044c"],"Rescan This Page":["\u041f\u0435\u0440\u0435\u0441\u043a\u0430\u043d\u0443\u0432\u0430\u0442\u0438 \u0446\u044e \u0441\u0442\u043e\u0440\u0456\u043d\u043a\u0443"],"Disable Page Styles":["\u0412\u0438\u043c\u043a\u043d\u0443\u0442\u0438 \u0441\u0442\u0438\u043b\u0456 \u0441\u0442\u043e\u0440\u0456\u043d\u043a\u0438"],"Disable Styles":["\u0412\u0438\u043c\u043a\u043d\u0443\u0442\u0438 \u0441\u0442\u0438\u043b\u0456"],"An error occurred when loading the issues.":["\u0412\u0438\u043d\u0438\u043a\u043b\u0430 \u043f\u043e\u043c\u0438\u043b\u043a\u0430 \u043f\u0456\u0434 \u0447\u0430\u0441 \u0437\u0430\u0432\u0430\u043d\u0442\u0430\u0436\u0435\u043d\u043d\u044f \u043f\u0440\u043e\u0431\u043b\u0435\u043c."],"Show Code":["\u041f\u043e\u043a\u0430\u0437\u0430\u0442\u0438 \u043a\u043e\u0434"],"Issue type:":["\u0422\u0438\u043f \u043f\u0440\u043e\u0431\u043b\u0435\u043c\u0438:"],"Enable Styles":["\u0423\u0432\u0456\u043c\u043a\u043d\u0443\u0442\u0438 \u0441\u0442\u0438\u043b\u0456"],"There are no settings to display.":["\u041d\u0435\u043c\u0430\u0454 \u043d\u0430\u043b\u0430\u0448\u0442\u0443\u0432\u0430\u043d\u044c \u0434\u043b\u044f \u0432\u0456\u0434\u043e\u0431\u0440\u0430\u0436\u0435\u043d\u043d\u044f."],"These settings enable global fixes across your entire site. Pages may need to be resaved or a full site scan run to see fixes reflected in reports.":["\u0426\u0456 \u043d\u0430\u043b\u0430\u0448\u0442\u0443\u0432\u0430\u043d\u043d\u044f \u0432\u043c\u0438\u043a\u0430\u044e\u0442\u044c \u0433\u043b\u043e\u0431\u0430\u043b\u044c\u043d\u0456 \u0432\u0438\u043f\u0440\u0430\u0432\u043b\u0435\u043d\u043d\u044f \u043d\u0430 \u0432\u0441\u044c\u043e\u043c\u0443 \u0432\u0430\u0448\u043e\u043c\u0443 \u0441\u0430\u0439\u0442\u0456. \u041c\u043e\u0436\u043b\u0438\u0432\u043e, \u0441\u0442\u043e\u0440\u0456\u043d\u043a\u0438 \u043f\u043e\u0442\u0440\u0456\u0431\u043d\u043e \u0431\u0443\u0434\u0435 \u043f\u043e\u0432\u0442\u043e\u0440\u043d\u043e \u0437\u0431\u0435\u0440\u0435\u0433\u0442\u0438 \u0430\u0431\u043e \u043f\u0440\u043e\u0432\u0435\u0441\u0442\u0438 \u043f\u043e\u0432\u043d\u0435 \u0441\u043a\u0430\u043d\u0443\u0432\u0430\u043d\u043d\u044f \u0441\u0430\u0439\u0442\u0443, \u0449\u043e\u0431 \u043f\u043e\u0431\u0430\u0447\u0438\u0442\u0438 \u0432\u0438\u043f\u0440\u0430\u0432\u043b\u0435\u043d\u043d\u044f \u0443 \u0437\u0432\u0456\u0442\u0430\u0445."],"No issues detected.":["\u041f\u0440\u043e\u0431\u043b\u0435\u043c \u043d\u0435 \u0432\u0438\u044f\u0432\u043b\u0435\u043d\u043e."],"error":["\u043f\u043e\u043c\u0438\u043b\u043a\u0430","\u043f\u043e\u043c\u0438\u043b\u043e\u043a"],"warning":["\u043f\u043e\u043f\u0435\u0440\u0435\u0434\u0436\u0435\u043d\u043d\u044f","\u043f\u043e\u043f\u0435\u0440\u0435\u0434\u0436\u0435\u043d\u044c"],"and":["\u0442\u0430"],"ignored issue":["\u043f\u0440\u043e\u0456\u0433\u043d\u043e\u0440\u043e\u0432\u0430\u043d\u0430 \u043f\u0440\u043e\u0431\u043b\u0435\u043c\u0430","\u043f\u0440\u043e\u0456\u0433\u043d\u043e\u0440\u043e\u0432\u0430\u043d\u0438\u0445 \u043f\u0440\u043e\u0431\u043b\u0435\u043c"],"detected.":["\u0432\u0438\u044f\u0432\u043b\u0435\u043d\u043e."],"Scanner function not found.":["\u0424\u0443\u043d\u043a\u0446\u0456\u044e \u0441\u043a\u0430\u043d\u0435\u0440\u0430 \u043d\u0435 \u0437\u043d\u0430\u0439\u0434\u0435\u043d\u043e."],"Scanning...":["\u0421\u043a\u0430\u043d\u0443\u0432\u0430\u043d\u043d\u044f..."],"No violations found, skipping save.":["\u041f\u043e\u0440\u0443\u0448\u0435\u043d\u044c \u043d\u0435 \u0432\u0438\u044f\u0432\u043b\u0435\u043d\u043e, \u043f\u0440\u043e\u043f\u0443\u0441\u043a\u0430\u0454\u043c\u043e \u0437\u0431\u0435\u0440\u0435\u0436\u0435\u043d\u043d\u044f."],"Missing postId or nonce.":["\u0412\u0456\u0434\u0441\u0443\u0442\u043d\u0456\u0439 postId \u0430\u0431\u043e nonce."],"Accessibility scan error.":["\u041f\u043e\u043c\u0438\u043b\u043a\u0430 \u0441\u043a\u0430\u043d\u0443\u0432\u0430\u043d\u043d\u044f \u0434\u043e\u0441\u0442\u0443\u043f\u043d\u043e\u0441\u0442\u0456."],"Error saving scan results.":["\u041f\u043e\u043c\u0438\u043b\u043a\u0430 \u0437\u0431\u0435\u0440\u0435\u0436\u0435\u043d\u043d\u044f \u0440\u0435\u0437\u0443\u043b\u044c\u0442\u0430\u0442\u0456\u0432 \u0441\u043a\u0430\u043d\u0443\u0432\u0430\u043d\u043d\u044f."]}}} No newline at end of file |
There was a problem hiding this comment.
"lang" header incorrectly set to "en" instead of "uk" – translations will not load
The locale header still declares English ("lang":"en"). For a Ukrainian PO/MO JSON this should be "uk". WordPress will treat the file as English and ignore the provided strings.
-...{"domain":"messages","lang":"en","plural-forms":"nplurals=2; plural=(n != 1);"}...
+...{"domain":"messages","lang":"uk","plural-forms":"nplurals=2; plural=(n != 1);"}...📝 Committable suggestion
‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.
| {"translation-revision-date":"YEAR-MO-DA HO:MI+ZONE","generator":"WP-CLI\/2.12.0","source":"build\/frontendHighlighterApp.bundle.js","domain":"messages","locale_data":{"messages":{"":{"domain":"messages","lang":"en","plural-forms":"nplurals=2; plural=(n != 1);"},"Save":["\u0417\u0431\u0435\u0440\u0435\u0433\u0442\u0438"],"Saving...":["\u0417\u0431\u0435\u0440\u0435\u0436\u0435\u043d\u043d\u044f..."],"Settings saved successfully. You must %svisit the editor%s and save the post to rescan and remove fixed issues from Accessibility Checker reports.":["\u041d\u0430\u043b\u0430\u0448\u0442\u0443\u0432\u0430\u043d\u043d\u044f \u0443\u0441\u043f\u0456\u0448\u043d\u043e \u0437\u0431\u0435\u0440\u0435\u0436\u0435\u043d\u043e. \u0412\u0438 \u043c\u0430\u0454\u0442\u0435 %s\u0432\u0456\u0434\u0432\u0456\u0434\u0430\u0442\u0438 \u0440\u0435\u0434\u0430\u043a\u0442\u043e\u0440%s \u0456 \u0437\u0431\u0435\u0440\u0435\u0433\u0442\u0438 \u0434\u043e\u043f\u0438\u0441, \u0449\u043e\u0431 \u043f\u043e\u0432\u0442\u043e\u0440\u043d\u043e \u043f\u0440\u043e\u0441\u043a\u0430\u043d\u0443\u0432\u0430\u0442\u0438 \u0442\u0430 \u0432\u0438\u0434\u0430\u043b\u0438\u0442\u0438 \u0432\u0438\u043f\u0440\u0430\u0432\u043b\u0435\u043d\u0456 \u043f\u0440\u043e\u0431\u043b\u0435\u043c\u0438 \u0437\u0456 \u0437\u0432\u0456\u0442\u0456\u0432 Accessibility Checker."],"Settings saved successfully.":["\u041d\u0430\u043b\u0430\u0448\u0442\u0443\u0432\u0430\u043d\u043d\u044f \u0443\u0441\u043f\u0456\u0448\u043d\u043e \u0437\u0431\u0435\u0440\u0435\u0436\u0435\u043d\u043e."],"Saving failed.":["\u041d\u0435 \u0432\u0434\u0430\u043b\u043e\u0441\u044f \u0437\u0431\u0435\u0440\u0435\u0433\u0442\u0438."],"Fix Settings":["\u041d\u0430\u043b\u0430\u0448\u0442\u0443\u0432\u0430\u043d\u043d\u044f \u0432\u0438\u043f\u0440\u0430\u0432\u043b\u0435\u043d\u044c"],"Close fixes modal":["\u0417\u0430\u043a\u0440\u0438\u0442\u0438 \u043c\u043e\u0434\u0430\u043b\u044c\u043d\u0435 \u0432\u0456\u043a\u043d\u043e \u0432\u0438\u043f\u0440\u0430\u0432\u043b\u0435\u043d\u044c"],"Rescan This Page":["\u041f\u0435\u0440\u0435\u0441\u043a\u0430\u043d\u0443\u0432\u0430\u0442\u0438 \u0446\u044e \u0441\u0442\u043e\u0440\u0456\u043d\u043a\u0443"],"Disable Page Styles":["\u0412\u0438\u043c\u043a\u043d\u0443\u0442\u0438 \u0441\u0442\u0438\u043b\u0456 \u0441\u0442\u043e\u0440\u0456\u043d\u043a\u0438"],"Disable Styles":["\u0412\u0438\u043c\u043a\u043d\u0443\u0442\u0438 \u0441\u0442\u0438\u043b\u0456"],"An error occurred when loading the issues.":["\u0412\u0438\u043d\u0438\u043a\u043b\u0430 \u043f\u043e\u043c\u0438\u043b\u043a\u0430 \u043f\u0456\u0434 \u0447\u0430\u0441 \u0437\u0430\u0432\u0430\u043d\u0442\u0430\u0436\u0435\u043d\u043d\u044f \u043f\u0440\u043e\u0431\u043b\u0435\u043c."],"Show Code":["\u041f\u043e\u043a\u0430\u0437\u0430\u0442\u0438 \u043a\u043e\u0434"],"Issue type:":["\u0422\u0438\u043f \u043f\u0440\u043e\u0431\u043b\u0435\u043c\u0438:"],"Enable Styles":["\u0423\u0432\u0456\u043c\u043a\u043d\u0443\u0442\u0438 \u0441\u0442\u0438\u043b\u0456"],"There are no settings to display.":["\u041d\u0435\u043c\u0430\u0454 \u043d\u0430\u043b\u0430\u0448\u0442\u0443\u0432\u0430\u043d\u044c \u0434\u043b\u044f \u0432\u0456\u0434\u043e\u0431\u0440\u0430\u0436\u0435\u043d\u043d\u044f."],"These settings enable global fixes across your entire site. Pages may need to be resaved or a full site scan run to see fixes reflected in reports.":["\u0426\u0456 \u043d\u0430\u043b\u0430\u0448\u0442\u0443\u0432\u0430\u043d\u043d\u044f \u0432\u043c\u0438\u043a\u0430\u044e\u0442\u044c \u0433\u043b\u043e\u0431\u0430\u043b\u044c\u043d\u0456 \u0432\u0438\u043f\u0440\u0430\u0432\u043b\u0435\u043d\u043d\u044f \u043d\u0430 \u0432\u0441\u044c\u043e\u043c\u0443 \u0432\u0430\u0448\u043e\u043c\u0443 \u0441\u0430\u0439\u0442\u0456. \u041c\u043e\u0436\u043b\u0438\u0432\u043e, \u0441\u0442\u043e\u0440\u0456\u043d\u043a\u0438 \u043f\u043e\u0442\u0440\u0456\u0431\u043d\u043e \u0431\u0443\u0434\u0435 \u043f\u043e\u0432\u0442\u043e\u0440\u043d\u043e \u0437\u0431\u0435\u0440\u0435\u0433\u0442\u0438 \u0430\u0431\u043e \u043f\u0440\u043e\u0432\u0435\u0441\u0442\u0438 \u043f\u043e\u0432\u043d\u0435 \u0441\u043a\u0430\u043d\u0443\u0432\u0430\u043d\u043d\u044f \u0441\u0430\u0439\u0442\u0443, \u0449\u043e\u0431 \u043f\u043e\u0431\u0430\u0447\u0438\u0442\u0438 \u0432\u0438\u043f\u0440\u0430\u0432\u043b\u0435\u043d\u043d\u044f \u0443 \u0437\u0432\u0456\u0442\u0430\u0445."],"No issues detected.":["\u041f\u0440\u043e\u0431\u043b\u0435\u043c \u043d\u0435 \u0432\u0438\u044f\u0432\u043b\u0435\u043d\u043e."],"error":["\u043f\u043e\u043c\u0438\u043b\u043a\u0430","\u043f\u043e\u043c\u0438\u043b\u043e\u043a"],"warning":["\u043f\u043e\u043f\u0435\u0440\u0435\u0434\u0436\u0435\u043d\u043d\u044f","\u043f\u043e\u043f\u0435\u0440\u0435\u0434\u0436\u0435\u043d\u044c"],"and":["\u0442\u0430"],"ignored issue":["\u043f\u0440\u043e\u0456\u0433\u043d\u043e\u0440\u043e\u0432\u0430\u043d\u0430 \u043f\u0440\u043e\u0431\u043b\u0435\u043c\u0430","\u043f\u0440\u043e\u0456\u0433\u043d\u043e\u0440\u043e\u0432\u0430\u043d\u0438\u0445 \u043f\u0440\u043e\u0431\u043b\u0435\u043c"],"detected.":["\u0432\u0438\u044f\u0432\u043b\u0435\u043d\u043e."],"Scanner function not found.":["\u0424\u0443\u043d\u043a\u0446\u0456\u044e \u0441\u043a\u0430\u043d\u0435\u0440\u0430 \u043d\u0435 \u0437\u043d\u0430\u0439\u0434\u0435\u043d\u043e."],"Scanning...":["\u0421\u043a\u0430\u043d\u0443\u0432\u0430\u043d\u043d\u044f..."],"No violations found, skipping save.":["\u041f\u043e\u0440\u0443\u0448\u0435\u043d\u044c \u043d\u0435 \u0432\u0438\u044f\u0432\u043b\u0435\u043d\u043e, \u043f\u0440\u043e\u043f\u0443\u0441\u043a\u0430\u0454\u043c\u043e \u0437\u0431\u0435\u0440\u0435\u0436\u0435\u043d\u043d\u044f."],"Missing postId or nonce.":["\u0412\u0456\u0434\u0441\u0443\u0442\u043d\u0456\u0439 postId \u0430\u0431\u043e nonce."],"Accessibility scan error.":["\u041f\u043e\u043c\u0438\u043b\u043a\u0430 \u0441\u043a\u0430\u043d\u0443\u0432\u0430\u043d\u043d\u044f \u0434\u043e\u0441\u0442\u0443\u043f\u043d\u043e\u0441\u0442\u0456."],"Error saving scan results.":["\u041f\u043e\u043c\u0438\u043b\u043a\u0430 \u0437\u0431\u0435\u0440\u0435\u0436\u0435\u043d\u043d\u044f \u0440\u0435\u0437\u0443\u043b\u044c\u0442\u0430\u0442\u0456\u0432 \u0441\u043a\u0430\u043d\u0443\u0432\u0430\u043d\u043d\u044f."]}}} | |
| {"translation-revision-date":"YEAR-MO-DA HO:MI+ZONE","generator":"WP-CLI\/2.12.0","source":"build\/frontendHighlighterApp.bundle.js","domain":"messages","locale_data":{ | |
| "messages":{ | |
| "":{ | |
| "domain":"messages", | |
| "lang":"uk", | |
| "plural-forms":"nplurals=2; plural=(n != 1);" | |
| }, | |
| "Save":["\u0417\u0431\u0435\u0440\u0435\u0433\u0442\u0438"], | |
| "Saving...":["\u0417\u0431\u0435\u0440\u0435\u0436\u0435\u043d\u043d\u044f..."], | |
| /* …rest of your translations… */ | |
| } | |
| }} |
🤖 Prompt for AI Agents
In languages/accessibility-checker-uk-b93b9e514c44a41f97246123aa57f5c4.json at
line 1, the "lang" header is incorrectly set to "en" instead of "uk". To fix
this, change the "lang" value from "en" to "uk" in the locale_data section so
WordPress correctly recognizes the file as Ukrainian and loads the translations.
| } | ||
| } | ||
| } No newline at end of file | ||
| {"translation-revision-date":"YEAR-MO-DA HO:MI+ZONE","generator":"WP-CLI\/2.12.0","source":"build\/editorApp.bundle.js","domain":"messages","locale_data":{"messages":{"":{"domain":"messages","lang":"en","plural-forms":"nplurals=2; plural=(n != 1);"},"Clear Issues":["\u041e\u0447\u0438\u0441\u0442\u0438\u0442\u0438 \u043f\u0440\u043e\u0431\u043b\u0435\u043c\u0438"],"This will clear all issues for this post. A save will be required to trigger a fresh scan of the post content. Do you want to continue?":["\u0426\u0435 \u043e\u0447\u0438\u0441\u0442\u0438\u0442\u044c \u0443\u0441\u0456 \u043f\u0440\u043e\u0431\u043b\u0435\u043c\u0438 \u0434\u043b\u044f \u0446\u044c\u043e\u0433\u043e \u0437\u0430\u043f\u0438\u0441\u0443. \u041f\u043e\u0442\u0440\u0456\u0431\u043d\u043e \u0431\u0443\u0434\u0435 \u0437\u0431\u0435\u0440\u0435\u0433\u0442\u0438, \u0449\u043e\u0431 \u0437\u0430\u043f\u0443\u0441\u0442\u0438\u0442\u0438 \u043d\u043e\u0432\u0435 \u0441\u043a\u0430\u043d\u0443\u0432\u0430\u043d\u043d\u044f \u0432\u043c\u0456\u0441\u0442\u0443 \u0437\u0430\u043f\u0438\u0441\u0443. \u0412\u0438 \u0445\u043e\u0447\u0435\u0442\u0435 \u043f\u0440\u043e\u0434\u043e\u0432\u0436\u0438\u0442\u0438?"],"Clearing...":["\u041e\u0447\u0438\u0449\u0435\u043d\u043d\u044f..."],"Issues cleared successfully.":["\u041f\u0440\u043e\u0431\u043b\u0435\u043c\u0438 \u0443\u0441\u043f\u0456\u0448\u043d\u043e \u043e\u0447\u0438\u0449\u0435\u043d\u043e."],"Failed to clear issues.":["\u041d\u0435 \u0432\u0434\u0430\u043b\u043e\u0441\u044f \u043e\u0447\u0438\u0441\u0442\u0438\u0442\u0438 \u043f\u0440\u043e\u0431\u043b\u0435\u043c\u0438."],"An error occurred while clearing issues.":["\u041f\u0456\u0434 \u0447\u0430\u0441 \u043e\u0447\u0438\u0449\u0435\u043d\u043d\u044f \u043f\u0440\u043e\u0431\u043b\u0435\u043c \u0441\u0442\u0430\u043b\u0430\u0441\u044f \u043f\u043e\u043c\u0438\u043b\u043a\u0430."]}}} No newline at end of file |
There was a problem hiding this comment.
💡 Verification agent
🧩 Analysis chain
lang metadata is incorrectly set to en in a Ukrainian locale file
The root metadata object still declares "lang":"en" although the file represents Ukrainian (uk). Many i18n loaders rely on this flag to choose the correct catalogue; keeping it as en can silently prevent the UA strings from ever being served.
-... "lang":"en", ...
+... "lang":"uk", ...Run the following check to catch the same issue in other locale files:
🏁 Script executed:
#!/bin/bash
# Find JSON translation files that incorrectly declare English language codes
rg -n '"lang":"en"' languages/*.jsonLength of output: 148442
Ensure correct lang metadata for all locale JSONs
Our scan shows dozens of languages/accessibility-checker-<locale>-*.json files still declare "lang":"en". Each file’s "lang" value must match its locale code (e.g. uk, cs_CZ, da_DK, etc.), or those translations will never be served.
Quick bulk-fix script:
#!/usr/bin/env bash
# For each translation JSON, extract its locale from the filename
# and use jq to update the nested "lang" field accordingly.
for file in languages/accessibility-checker-*.json; do
locale=${file#languages/accessibility-checker-}
locale=${locale%%-*}
# update the "" message’s lang metadata
jq --arg locale "$locale" \
'.locale_data.messages[""].lang = $locale' \
"$file" > tmp && mv tmp "$file"
doneAlternatively, manually update in each file:
- "lang":"en",
+ "lang":"uk", # or "cs_CZ", "da_DK", etc. per filenameFiles requiring this change:
• languages/accessibility-checker-*.json (all locale variants)
🤖 Prompt for AI Agents
In languages/accessibility-checker-uk-c6b6e50c6acd7c42c9d09e857f9ed6b0.json at
line 1, the "lang" metadata is incorrectly set to "en" instead of the correct
locale code "uk". To fix this, update the "lang" field inside the nested
"messages" object to match the locale code extracted from the filename, which is
"uk" in this case. You can do this manually or use a bulk script with jq to
automate updating all such files consistently.
![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 is an automated update focused on reformatting existing translation files across multiple languages. The primary change involves converting JSON files from a human-readable, pretty-printed format to a minified, single-line format. This optimization aims to reduce file size without altering the actual translated content.
Highlights
- Automated Translation Reformatting: This pull request updates numerous language translation files (JSON) by reformatting them from a pretty-printed, multi-line structure to a minified, single-line format. The content of the translations remains unchanged; only the file structure has been optimized for compactness.
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 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 or fill out our survey 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
This pull request adds new translations and reformats many of the JSON translation files into a single-line format. While the new translations are a welcome addition, I've pointed out a potential mistranslation for Danish. Additionally, I've raised a concern about the maintainability of single-line JSON files, as it makes reviewing changes more difficult. Please see the detailed comments.
| } | ||
| } | ||
| } No newline at end of file | ||
| {"translation-revision-date":"YEAR-MO-DA HO:MI+ZONE","generator":"WP-CLI\/2.12.0","source":"build\/admin.bundle.js","domain":"messages","locale_data":{"messages":{"":{"domain":"messages","lang":"en","plural-forms":"nplurals=2; plural=(n != 1);"},"Get Pro to unlock this feature, opens in a new window.":["\u041f\u0440\u0435\u043c\u0438\u043d\u0435\u0442\u0435 \u043a\u044a\u043c Pro \u0432\u0435\u0440\u0441\u0438\u044f, \u0437\u0430 \u0434\u0430 \u043e\u0442\u043a\u043b\u044e\u0447\u0438\u0442\u0435 \u0442\u0430\u0437\u0438 \u0444\u0443\u043d\u043a\u0446\u0438\u044f, \u043e\u0442\u0432\u0430\u0440\u044f \u0441\u0435 \u0432 \u043d\u043e\u0432 \u043f\u0440\u043e\u0437\u043e\u0440\u0435\u0446."],"Saving...":["\u0417\u0430\u043f\u0430\u0437\u0432\u0430\u043d\u0435..."],"Settings saved successfully. You must %svisit the editor%s and save the post to rescan and remove fixed issues from Accessibility Checker reports.":["\u041d\u0430\u0441\u0442\u0440\u043e\u0439\u043a\u0438\u0442\u0435 \u0441\u0430 \u0437\u0430\u043f\u0430\u0437\u0435\u043d\u0438 \u0443\u0441\u043f\u0435\u0448\u043d\u043e. \u0422\u0440\u044f\u0431\u0432\u0430 \u0434\u0430 %s\u043f\u043e\u0441\u0435\u0442\u0438\u0442\u0435 \u0440\u0435\u0434\u0430\u043a\u0442\u043e\u0440\u0430%s \u0438 \u0434\u0430 \u0437\u0430\u043f\u0430\u0437\u0438\u0442\u0435 \u043f\u0443\u0431\u043b\u0438\u043a\u0430\u0446\u0438\u044f\u0442\u0430, \u0437\u0430 \u0434\u0430 \u0441\u043a\u0430\u043d\u0438\u0440\u0430\u0442\u0435 \u043e\u0442\u043d\u043e\u0432\u043e \u0438 \u043f\u0440\u0435\u043c\u0430\u0445\u043d\u0435\u0442\u0435 \u043a\u043e\u0440\u0438\u0433\u0438\u0440\u0430\u043d\u0438\u0442\u0435 \u043f\u0440\u043e\u0431\u043b\u0435\u043c\u0438 \u043e\u0442 \u043e\u0442\u0447\u0435\u0442\u0438\u0442\u0435 \u043d\u0430 Accessibility Checker."],"Settings saved successfully.":["\u041d\u0430\u0441\u0442\u0440\u043e\u0439\u043a\u0438\u0442\u0435 \u0441\u0430 \u0437\u0430\u043f\u0430\u0437\u0435\u043d\u0438 \u0443\u0441\u043f\u0435\u0448\u043d\u043e."],"Saving failed.":["\u0417\u0430\u043f\u0430\u0437\u0432\u0430\u043d\u0435\u0442\u043e \u043d\u0435 \u0443\u0441\u043f\u044f."],"Fix Settings":["\u041d\u0430\u0441\u0442\u0440\u043e\u0439\u043a\u0438 \u0437\u0430 \u043a\u043e\u0440\u0435\u043a\u0446\u0438\u0438"]}}} No newline at end of file |
There was a problem hiding this comment.
Reformatting the JSON files to a single line reduces readability and makes tracking changes in version control difficult. For better maintainability, it's recommended to keep the pretty-printed, multi-line format. This would make it much easier to see what translations are being added or changed in each pull request.
| } | ||
| } | ||
| } No newline at end of file | ||
| {"translation-revision-date":"YEAR-MO-DA HO:MI+ZONE","generator":"WP-CLI\/2.12.0","source":"build\/frontendHighlighterApp.bundle.js","domain":"messages","locale_data":{"messages":{"":{"domain":"messages","lang":"en","plural-forms":"nplurals=2; plural=(n != 1);"},"Save":["Gem"],"Saving...":["Gemmer..."],"Settings saved successfully. You must %svisit the editor%s and save the post to rescan and remove fixed issues from Accessibility Checker reports.":["Indstillinger gemt. Du skal %sbes\u00f8ge editoren%s og gemme indl\u00e6gget for at genscanne og fjerne l\u00f8ste problemer fra Accessibility Checker-rapporter."],"Settings saved successfully.":["Indstillinger gemt med succes."],"Saving failed.":["Gemning mislykkedes."],"Fix Settings":["Ret indstillinger"],"Close fixes modal":["Luk rettelsesvindue"],"Rescan This Page":["Genindl\u00e6s denne side"],"Disable Page Styles":["Deaktiver sidestilarter"],"Disable Styles":["Deaktiv\u00e9r stilarter"],"An error occurred when loading the issues.":["Der opstod en fejl under indl\u00e6sning af problemerne."],"Show Code":["Vis kode"],"Issue type:":["Problemtype:"],"Enable Styles":["Aktiv\u00e9r stilarter"],"There are no settings to display.":["Der er ingen indstillinger at vise."],"These settings enable global fixes across your entire site. Pages may need to be resaved or a full site scan run to see fixes reflected in reports.":["Disse indstillinger aktiverer globale rettelser p\u00e5 hele dit websted. Sider skal muligvis gemmes igen, eller der skal k\u00f8res en fuld webstedsskanning for at se rettelser afspejlet i rapporterne."],"No issues detected.":["Ingen problemer registreret."],"error":["fejl","fejl"],"warning":["advarsel","advarsler"],"and":["og"],"ignored issue":["ignoreret problem","ignorerede problemer"],"detected.":["registreret."],"Scanner function not found.":["Scannerfunktion ikke fundet."],"Scanning...":["Scanner..."],"No violations found, skipping save.":["Ingen overtr\u00e6delser fundet, springer over gemning."],"Missing postId or nonce.":["Manglende postId eller nonce."],"Accessibility scan error.":["Fejl i tilg\u00e6ngelighedsscanning."],"Error saving scan results.":["Fejl ved gemning af scanningsresultater."]}}} No newline at end of file |
There was a problem hiding this comment.
The Danish translation for "Rescan This Page" seems incorrect. Genindlæs denne side translates to "Reload this page". A more accurate translation for "Rescan this page" would be Skan denne side igen.
2 participants
For more information go to https://app.ptc.wpml.org/#/dashboard/merge-requests-history/1985
Summary by CodeRabbit
New Features
Style