我们要不要迁移到Crowdin或者其他翻译平台？| Should we migrate to Crowdin or other platform for l10n?

[liquidhelium]

我注意到现有的翻译过程需要贡献者能够熟练使用github,并且对fluent格式有比较清晰的理解（之前一些翻译文件格式上有轻微错误，曾经使程序无法读取这些文件）,同时对于翻译文本的审核和建议是在github pr里进行的，可能也不如专门的平台方便。

当然，这些都是我个人的看法，难免片面，迁移的过程也肯定不是很容易就能完成的，还可能引起其他问题。所以我在此开一个discussion供大家讨论。

(Gemini translated)

I have noticed that the existing translation process requires contributors to be:

1. Proficient in using GitHub.
2. To have a clear understanding of the Fluent format (some slight formatting errors in previous translation files have occasionally prevented the program from reading them).

Furthermore, the review and suggestion process for translation texts is carried out within GitHub Pull Requests (PRs), which may not be as convenient as using a dedicated platform.

Of course, these are just my personal opinions and are inevitably one-sided. The migration process would certainly not be easy to complete and might also lead to other issues. Therefore, I am opening this discussion for everyone to deliberate on the matter.

[YuevUwU]

2026/03/24 下午三點多
Weblate 已建立，在待Libre計劃審核，不過現在就可用了:
https://hosted.weblate.org/projects/phira/

Mivik 已通知 Discord Translators

PR 做法的指引還在 README 劃掉的那個留言連結待著，
但新的 Weblate 方法指引會在更上面

從 PR (檔案) 轉到 Weblate 的匯入指引也在裡頭
現在的 #393 (新語言 mn-MN)、#528 (新 README 語言+更新ja-JP)、#530 (更新 fr-FR)
就看他們要不要臨時遷移了（如果要更新的話）

轉到 Weblate 後，截圖、審核機制、上下文提示都可以做了，就再說吧
(審核的部分現在看起來沒開，而且因為也沒 Reviewer，所以先說目前還是官方要審PR，但Fluent Syntax的問題就會比較少了)

至於 Crowdin 則在其他分支曇花一現

[YuevUwU]

另外為了提防初期破壞(還沒有審核員)，暫時不會在公開頻道透漏 Weblate 這事
儘管有一部分我推薦翻譯平臺的原因就是公開讓人輕鬆提出翻譯建議

[YuevUwU]

Weblate 已知问题 001：合并冲突

发生时间：2026-03-25T17:01:13+01:00

（注：Weblate Project 有自己的 Repo，这使得他们能用自己的格式去记录 Fluent 不能记录的状态，再转回 Fluent 格式，故会出现重新 compact 或 renormalize/reformat 的问题。同时，变更的翻译字串也自它们的 Repo 记录起通知 Fuzzy。而该 Repo 似乎是仅管理员可查阅内容，非管理员必须透过 Weblate 站点的 History 与释出的 Alert 记录探查，且 Repo 真实内容与 Config 并非完全公开透明）

若途中遭遇了 Weblate Git 存储库 Merge Conflict，整个翻译会被锁定，只能对现有记录的字串 Suggest，无法 Save
并且由于冲突未解决，在 Phira Repo 的翻译键更新并不会同步过去。
这对翻译者可能还好，就晚点等 Unlock 之后收到新字串通知跑去译。
比较大的问题是官方没去解Conflict，如果直到哪天想同步了或快发版了才去解（或者 Alert 埋在 Mail 里面没收到）
那可能得等一段时间给翻译者，这比PR晾在那边没Merge更加不受控制
那翻译者想同步新字串的唯一方法还是开 PR
并且不确定这个 Merge Conflict 是否真的就是因为 Git Repo 编辑了，Weblate 又编辑了一遍导致的冲突
需要管理员(Mivik)亲自复盘

History 截图

Alert 截图

[YuevUwU]

Weblate 於 4/10/26, 2:22:46 PM 再次 rebase conflict

Log

Rebasing (1/35)
dropping 6a48bad4aef9c4975018c15b898089c214c0acd0 Translated using Weblate (Russian) -- patch contents already upstream
Rebasing (2/35)
dropping 675d5b93eff46a1bc320b3623126b8070afb664d Translated using Weblate (Russian) -- patch contents already upstream
Rebasing (3/35)
dropping 4fd10a7b2152ac6286a906e1b0fbbf7ae513c241 Translated using Weblate (Mongolian) -- patch contents already upstream
Rebasing (4/35)
dropping ff74646ce2e6803973d6ca5c7289cb7cacbab193 Translated using Weblate (Russian) -- patch contents already upstream
Rebasing (5/35)
dropping ae13cb5b5f661a6ef170474a91635f0fa5b85d5f Translated using Weblate (Mongolian) -- patch contents already upstream
Rebasing (6/35)
dropping a56702246b9f7fd8b04e018aa3f350159b3fe2db Translated using Weblate (Korean) -- patch contents already upstream
Rebasing (7/35)
dropping 54ea25cbcdb55b0204c2cd30717c64821e69d181 Translated using Weblate (Korean) -- patch contents already upstream
Rebasing (8/35)
dropping 8c250af8b4ccd33e995e9e652d8ba030476ec355 Translated using Weblate (Mongolian) -- patch contents already upstream
Rebasing (9/35)
dropping aba17c11cd2a688ac88bf36bf8156db091f4f9ce Translated using Weblate (Mongolian) -- patch contents already upstream
Rebasing (10/35)
dropping 09f0458c0cae456c0aac4ba8c4ecf502c4807f95 Translated using Weblate (Mongolian) -- patch contents already upstream
Rebasing (11/35)
dropping 593448d32ec38253a0e1d350b09c33f753c0970c Translated using Weblate (Mongolian) -- patch contents already upstream
Rebasing (12/35)
dropping d3e8f69f674787784c88cdb6b99e64a49fa9e6e2 Translated using Weblate (Russian) -- patch contents already upstream
Rebasing (13/35)
dropping 6e75def3d1c10535bcb92ce0d23e079607ca1924 Translated using Weblate (Mongolian) -- patch contents already upstream
Rebasing (14/35)
dropping 84ee19282f97f64145a7fc6902a162e592ce2b2c Translated using Weblate (Russian) -- patch contents already upstream
Rebasing (15/35)
dropping 962a6446fa7c31ffc6836f8a4fe6a0a254143c71 Translated using Weblate (Mongolian) -- patch contents already upstream
Rebasing (16/35)
dropping 21e1687c5b8daf278bcf9077d678d2592ee1799f Translated using Weblate (Mongolian) -- patch contents already upstream
Rebasing (17/35)
dropping bb7d4706685b5f1c9e8b4f580ce91921bedc0ba2 Translated using Weblate (Korean) -- patch contents already upstream
Rebasing (18/35)
dropping 9dc07ea4820e9183c8866e661d05d191f0fc30c2 Translated using Weblate (Korean) -- patch contents already upstream
Rebasing (19/35)
dropping 55aee806d8494e075b4ab5d3f3f424f39b261ce2 Translated using Weblate (Korean) -- patch contents already upstream
Rebasing (20/35)
dropping 2b57179d586d34f1ab4306b4de87f67f053f0217 Translated using Weblate (Mongolian) -- patch contents already upstream
Rebasing (21/35)
Auto-merging phira/locales/mn-MN/favorites.ftl
CONFLICT (content): Merge conflict in phira/locales/mn-MN/favorites.ftl
error: could not apply 9f35c22... Translated using Weblate (Mongolian)
hint: Resolve all conflicts manually, mark them as resolved with
hint: "git add/rm <conflicted_files>", then run "git rebase --continue".
hint: You can instead skip this commit: run "git rebase --skip".
hint: To abort and get back to the state before "git rebase", run "git rebase --abort".
hint: Disable this message with "git config advice.mergeConflict false"
Could not apply 9f35c22... Translated using Weblate (Mongolian)
 (1)

Fixed on 05-08 03:59Z