Have translation priorities to help translators do most important strings first · zulip/zulip#1628

(6 留言) (0 反應) (0 負責人)Python (19,672 star) (7,339 fork)batch import

area: internationalizationhelp wanted

描述

I'm not 100% sure what the design for this should be, but I think it'd be awesome for making life easier for translators if we split our translations into a few files (or otherwise had a way to tag priority of strings for transifex). Basically I think there's tiers of priority:

(1) Main UI (2) Error messages (only needed if things go wrong) (3) Administration pages (only need for admin) (4) Maybe some other category?

And it'd be nice to be able to have translators easily focus on translating strings in order of importance.

We should research options for how to do this, but one fairly doable approach would be to just output a separate file for the error messages and also separate files for certain groups of templates (e.g. templates/corporate could be its own file, since it isn't used in the open source project).

@umairwaheed you may have ideas for how to do this technically.

貢獻者指南

技術棧: pythondjango
領域: internationalizationlocalization
議題類型: feature
難度: 3
預計時間: half day
活動狀態: stale
清晰度: mostly clear
前置要求: Django i18n knowledgeTranslation file handling
新手友善度: 40
研究方向: Investigate how to split translation strings into prioritized files, e.g., using separate .po files for different categories like main UI, error messages, and admin pages. Look into existing i18n practices in Django, such as using different domain names for translation files. Check if the Zulip codebase currently has a single translation file and explore how to organize templates into groups without breaking existing functionality. Consider using Transifex tagging features if applicable.