[GH-ISSUE #2267] [Docs] Add a Central Kurdish (Sorani) README edition #749

New issue

Open

opened 2026-10-15 18:27:57 +00:00 by bsakaguchi · 1 comment

bsakaguchi commented

2026-10-15 18:27:57 +00:00

Owner

Originally created by @muhammedburhanx on GitHub (Oct 12, 2026).
Original GitHub issue: https://github.com/morluto/rea/issues/2267

Before submitting

I searched the existing issues for a related documentation report.
I removed credentials, tokens, private paths, and sensitive target data.

Documentation location

README.md language navigation (and website/locales/languages.json)

Problem

REA has README editions in 19 languages but none in Kurdish. Central Kurdish (Sorani) is the most widely written form of Kurdish in the Kurdistan Region of Iraq and in Iran, and Kurdish developers currently need to read the English or Arabic/Persian editions.

Expected content

A README_ku.md edition: a full Sorani translation (Arabic script, right-to-left, laid out like README_fa.md), linked at the end of the language navigation in every README and registered in website/locales/languages.json so the README editions and website inventory stay aligned. Commands, code blocks, product names and link targets stay identical to English.

Supporting evidence

Follows the same pattern as the Italian edition (#1453 / #1455).

Additional context

I'm a native Sorani speaker from Sulaymaniyah and will keep this edition in sync with the English README.
languages.json accepts only two-letter codes, so I propose ku for this edition. The more precise tag for Sorani is ckb; I'm happy to follow your preference.

Originally created by @muhammedburhanx on GitHub (Oct 12, 2026). Original GitHub issue: https://github.com/morluto/rea/issues/2267 ### Before submitting - [x] I searched the existing issues for a related documentation report. - [x] I removed credentials, tokens, private paths, and sensitive target data. ### Documentation location `README.md` language navigation (and `website/locales/languages.json`) ### Problem REA has README editions in 19 languages but none in Kurdish. Central Kurdish (Sorani) is the most widely written form of Kurdish in the Kurdistan Region of Iraq and in Iran, and Kurdish developers currently need to read the English or Arabic/Persian editions. ### Expected content A `README_ku.md` edition: a full Sorani translation (Arabic script, right-to-left, laid out like `README_fa.md`), linked at the end of the language navigation in every README and registered in `website/locales/languages.json` so the README editions and website inventory stay aligned. Commands, code blocks, product names and link targets stay identical to English. ### Supporting evidence Follows the same pattern as the Italian edition (#1453 / #1455). ### Additional context I'm a native Sorani speaker from Sulaymaniyah and will keep this edition in sync with the English README. `languages.json` accepts only two-letter codes, so I propose `ku` for this edition. The more precise tag for Sorani is `ckb`; I'm happy to follow your preference.

bsakaguchi added the

labels

2026-10-15 18:27:57 +00:00

bsakaguchi commented

2026-10-15 18:27:58 +00:00

Author

Owner

@matbrgz commented on GitHub (Oct 12, 2026):

Status & Linkage Update

Thank you for proposing the Central Kurdish (Sorani) documentation edition.
PR #2407 (feat(website): add Central Kurdish (Sorani) locale) is currently open with this implementation. Once documentation checks (npm run docs:check) and sidebar navigation pass, this will be merged.

@matbrgz commented on GitHub (Oct 12, 2026): ### Status & Linkage Update Thank you for proposing the Central Kurdish (Sorani) documentation edition. PR #2407 (`feat(website): add Central Kurdish (Sorani) locale`) is currently open with this implementation. Once documentation checks (`npm run docs:check`) and sidebar navigation pass, this will be merged.

bsakaguchi referenced this issue

2026-10-15 18:28:29 +00:00

[GH-ISSUE #2383] [Tracker] Audit analysis and debugging coverage for the TIOBE top 100 languages (October 2026) #794

bsakaguchi referenced this issue

2026-10-16 21:15:44 +00:00

[PR #749] [MERGED] fix(javascript): expose result schema failures #2211