zai-org / zai-org/feedback

[Feature Request]: Official Farsi (Persian / فارسی) Localization for ZCode Docs & UI (Community Lead Volunteer Ready)

Open
#666 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

priority: P2
Dominant language
No language data
Stars
22
Forks
1
PR merge metrics
No merged PRs in 30d

Description

Proposal Overview

Add official Farsi (Persian / فارسی) localization support for the ZCode documentation and desktop application, backed by community volunteer leadership.


Motivation & Community Impact
  • Target Audience: Over 100M+ native speakers with an active, fast-growing developer community in Iran and globally, currently underserved with modern AI coding documentation in their native language.
  • Current Docs Limitation: The official documentation currently supports English (EN) and Chinese (ZH) only.

Suggested Phased Implementation
  1. Phase 1 (Documentation):
    • Introduce Farsi language switcher (fa-IR) on the docs platform.
    • Establish community localization pipeline (e.g. Crowdin, Weblate, or GitHub pull-request based Markdown translation).
  2. Phase 2 (Desktop UI Localization):
    • Support RTL (Right-to-Left) rendering and Farsi string catalogs (i18n) in the ZCode desktop client.

Community Volunteer Contribution

Community member Danial [PPLX] (experienced in open-source localization, currently leading Penpot frontend Farsi translation on Weblate) has volunteered to:

  • Act as lead Farsi translator and proofreader.
  • Help configure community translation tooling (Weblate/Crowdin).
  • Coordinate and review community translation PRs.

Origin & Discord Reference

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

No files, tests, or code entry points are identified. Start by locating the documentation language switcher and the desktop client's i18n and rendering configuration, then determine the scope of the phased work. Done would include an agreed Farsi documentation workflow and a defined plan for RTL desktop UI support.

Written by the indexing model from the issue text.

Assessment

Domain
desktop, documentation, internationalization, localization
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Active
Clarity
Needs clarification
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.