![]() ![]() ![]() To keep an overview of missing phrases in languages, we use a Github project which gets updated whenever a phrase file changes. This brings the translation phrases one step closer to where most of the activity happens. Since we're using Github for most of the file related tasks already, just including all phrases in the repository and updating them through pull requests seems like the obvious choice. With a rolling release model, the 1.11-dev and master branches are always kept in a runnable state, so there is no time to stop and gather all translations before each commit. After they voted on the best translation for all phrases, they were exported and shipped with the next release. With scheduled releases, it used to work like this: before publishing a release, the phrases were frozen and all translators asked to update the phrases. This led to rethinking how community translations are collected and resulted in putting the old translator tool down in favor of a Github Project tracking the progress. We couldn't add new phrases (looking at you, #597), since there was no process to gather translations and the existing solution saw little activity over the years. While the tool worked well and served its purpose, it doesn't quite work with the current rolling release model. The translation phrases used to be maintained by dedicated community volunteers through an online tool. Phrases for all languages have been moved into the repository and can be updated through pull requests. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |