| 2010-11-30 21:10:03 |
Emilien Klein |
description |
As suggested in bug #423529, it should be possible to create the template file (.pot) and update the translation files (.po) without having to do a release. I would also approve the creation of the command "quickly translate [language]". This would update the .pot file, update the existing .po files, and if the optional "language" variable is set, create a new <language>.po file to get started with translating a new language. ("language" would be the usual 2-letter language code, like nl, fr, es, etc.)
The reason for creating this separate command is that the workflow of updating translations is different than that of releasing a new version. At the time of releasing the new version you want it to ship with the newest translations, but if the template only gets updated when releasing, it means that the translators always have one version delay in translating.
And for a brand new project, it means that you can only start translating after your first version has been released. The first version then always has to be English-only.
Having to manually execute the gettext commands (as explained in http://faq.pygtk.org/index.py?req=show&file=faq22.002.htp) is not a nice way to go.
Main point: Translating != Releasing ;)
$quickly --version
Quickly 0.4.3
Ubunt 10.04 |
As suggested in bug #423529, it should be possible to create the template file (.pot) and update the translation files (.po) without having to do a release. I would also approve the creation of the command "quickly translate [language]". This would update the .pot file, update the existing .po files, and if the optional "language" variable is set, create a new <language>.po file to get started with translating a new language. ("language" would be the usual 2-letter language code, like nl, fr, es, etc.)
The reason for creating this separate command is that the workflow of updating translations is different than that of releasing a new version. At the time of releasing the new version you want it to ship with the newest translations, but if the template only gets updated when releasing, it means that the translators always have one version delay in translating.
And for a brand new project, it means that you can only start translating after your first version has been released. The first version then always has to be English-only.
Having to manually execute the gettext commands (as explained in http://faq.pygtk.org/index.py?req=show&file=faq22.002.htp) is not a nice way to go.
Main point: Translating != Releasing ;)
$quickly --version
Quickly 0.4.3
Ubuntu 10.04
|
|
