You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hi, and thanks for the translation work on this fork — the multilingual site and TRANSLATION.md conventions are excellent.
I'm a native Persian speaker (UK-based software engineer) and I'd like to add Persian (fa) as a new language. There's very little evidence-based, source-cited material like this available in Persian, so I think it would be genuinely useful.
Proposed approach:
Follow docs/pipeline/add-language.md and TRANSLATION.md as-is: status line, citations/DOIs/numbers byte-identical, cost-tag comments untouched, localisation only via translator's note blocks (e.g. Iranian emergency numbers 115/125/110).
Translate from the Chinese original, with the English version as a reference, using an LLM (Claude), followed by my own manual review of every chapter. I'd prioritise first-aid, medication and "do not" warnings in review.
Start with one pilot chapter (e.g. 06 The Anti-List) as a single PR, so you can check quality before I continue.
Questions before I start:
Would you accept a Persian translation into this fork?
Persian is right-to-left. The site currently has no RTL handling. Are you open to a PR that adds dir="rtl" support for fa (layout, filters, entry cards), without affecting other languages? I'm happy to do this work.
Is LLM translation plus native-speaker review acceptable, or do you require the translate/ pipeline (Hy-MT2 + verify + LanguageTool) to be run? If verify.py can run standalone, I'd be glad to run it before each PR.
Any preference on PR granularity (one chapter per PR, or batches)?
Thanks for writing, and for how carefully you thought this through (this is the first issue in my repository that I'm replying to, so I'm a little nervous ☺️). A Persian translation is very welcome in this fork. I'm all for it: the more languages this knowledge is available in, the better.
A separate pull request that adds dir="rtl" only for fa is fine. It should leave the other languages as they are.
Running the Hy-MT2 pipeline or LanguageTool is not required. What matters is that the text is readable. Running verify.py before the pull request is useful, and if you find problems in it, please send fixes.
Please keep the whole language on one branch and open one pull request, rather than one chapter at a time. The right-to-left layout can stay in its own pull request.
Activity
dlgrv commentedon Sep 30, 2026
Hi Hossein,
Thanks for writing, and for how carefully you thought this through (this is the first issue in my repository that I'm replying to, so I'm a little nervous☺️ ). A Persian translation is very welcome in this fork. I'm all for it: the more languages this knowledge is available in, the better.
A separate pull request that adds
dir="rtl"only forfais fine. It should leave the other languages as they are.Running the Hy-MT2 pipeline or LanguageTool is not required. What matters is that the text is readable. Running
verify.pybefore the pull request is useful, and if you find problems in it, please send fixes.Please keep the whole language on one branch and open one pull request, rather than one chapter at a time. The right-to-left layout can stay in its own pull request.
Looking forward to it.
按 issue #86 补两条:第 2 节第 43 条绝经前后潮热盗汗去妇科评估激素治疗,别自己买、别拿来防心脏病(A 争议:Cochra…
dlgrv commentedon Oct 10, 2026
Hi @margani — just a gentle ping.
Whenever you have time, a Persian (
fa) PR is still very welcome here. No rush; happy to review whenever you open it.margani commentedon Oct 12, 2026
Hi @dlgrv, thank you for the warm reply and the ping, and sorry for the slow response.
Got it: one branch and one PR for the whole fa translation, and a separate PR for the RTL layout. I'll run verify.py before opening it.
I'm starting now and will work through it alongside my day job, so it may take a few weeks. I'll post an update here as it progresses.