Skip to content

Create _language-ar.yml - #14203

Closed
Ciyoku wants to merge 1 commit into
quarto-dev:mainfrom
Ciyoku:Ciyoku-patch-2
Closed

Ciyoku wants to merge 1 commit into
quarto-dev:mainfrom
Ciyoku:Ciyoku-patch-2

Conversation

@Ciyoku

@Ciyoku Ciyoku commented Mar 12, 2026

Copy link
Copy Markdown

This PR adds support for Arabic localization in Quarto by introducing _language-ar.yml. It includes translations for UI elements, navigation labels, buttons, and interface text to enable RTL Arabic display.

@posit-snyk-bot

posit-snyk-bot commented Mar 12, 2026 •

Copy link
Copy Markdown
Collaborator

✅ Snyk checks have passed. No issues have been found so far.

Status Scan Engine Critical High Medium Low Total (0)
✅ Open Source Security 0 0 0 0 0 issues
✅ Licenses 0 0 0 0 0 issues

💻 Catch issues earlier using the plugins for VS Code, JetBrains IDEs, Visual Studio, and Eclipse.

@cscheid

cscheid commented Mar 12, 2026

Copy link
Copy Markdown
Member

Thank you! We're about to release 1.9 but we'll merge this for 1.10.

@cscheid cscheid added this to the v1.10 milestone Mar 12, 2026
@Ciyoku

Ciyoku commented Mar 12, 2026

Copy link
Copy Markdown
Author

Thank you! We're about to release 1.9 but we'll merge this for 1.10.

Thank you for the update! Glad to hear it will be merged for 1.10. Looking forward to the release.

@mcanouil mcanouil modified the milestones: v1.10, v1.11 Jul 30, 2026
@cderv cderv modified the milestones: v1.11, v1.12 Oct 29, 2026
cderv added a commit that referenced this pull request Nov 3, 2026
Keys added to _language.yml did not reach the per-language files, and
nothing checked for it, so localized pages fell back to English for
those strings (#14822). Two files also used keys that no longer match
_language.yml. This adds a test that keeps the language files in step
with _language.yml, and translator comments that say which sense of
each key to use.

- tests/unit/language-parity.test.ts: fails when a language file has a
  key missing from _language.yml, when a base language lacks a key that
  is not in language-known-gaps.yml, when that list goes stale, or when
  a value does not keep the {0} placeholders of the English value.
  Region files are overlays on their base language, so they skip only
  the missing-key check.
- lt and sv: rename the stale keys (search to search-label, and
  callout-danger-title to callout-caution-title), keeping the existing
  values. The Swedish file (#5000) used a key name that was already
  gone when it was added.
- _language.yml: translator comments above each key missing from some
  file: what the string is, where it shows, and which sense to use.
- src/resources/language/README.md and AGENTS.md: the full list of
  language files and contributing guidance for translators, including
  disclosure of AI help.

Related to #14822. Once #14203 lands, its Arabic file needs every key
translated or listed in language-known-gaps.yml.
@cderv

cderv commented Nov 5, 2026

Copy link
Copy Markdown
Member

Thanks a lot for this contribution, and sorry for the long wait. #14389 adds the same file and has been reviewed by an Arabic speaker, so we'll merge that one and I am closing this one. If you think some of your values fit better, like "مقتطف" for code listings, a PR updating _language-ar.yml once #14389 is merged is very welcome.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

5 participants