2,569
edits
Changes
From SME Server
Jump to navigationJump to search
mLine 40:
Line 40: − + − + − + − + − :this shows missing translations very nicely and is ready for user testing − − *all .po files have been converted to UTF-8, they will be converted back to ISO-8859-1 when patching SME − + − + − + + + − + − + − : we need to script the conversion of existing translations into .po files − + − : the following is speculative ...+ − : these are imported into the .pot templates, other languages are updated from templates − : new <base> strings only have to be added to the cvs xml file for english − + − then diff against cvs, make patch, check and apply+
→Translation Workflow
===.po files===
===.po files===
*gettext strings are in various files in cvs, currently we think we have them all in pootle as .pot template files
*gettext strings are in various files in cvs
: we need to use xgettext to search a maintained list of files to extract current gettext strings
: we use xgettext to creates .po files from the original files to by extracting gettext strings [1]
: this may find missing, or modified strings or remove old strings saving on pointless translations
: we load these into pootle as .pot template files and update other languages from these
*existing translations have been placed in pootle and merged with the templates
* .po files have been converted to UTF-8, they will be converted back to ISO-8859-1 when patching SME
*changes to original files, ie changed gettext strings, have to be tracked as usual in the bug tracker
*changes to original files, ie changed gettext strings, have to be tracked as usual in the bug tracker
:these are imported into the templates, other languages are updated from templates
: these are imported into the templates and other languages by above method
*at some point we diff against cvs po files, the patch is checked and applied.
*at some point we diff updated po files against cvs po files, the patch is checked and applied.
===FormMagick files===
===FormMagick files===
*these are XML files with a <base> and <trans> pair of strings, these can be converted to .po files with some work
*these are XML files with a <base> and <trans> pair of strings
: we create .po files from the english versions [2]
: we load these into pootle as .pot template files and update other languages from these
*some rough scripts are being worked on above, there may be others on the net waiting to be found...
* changes to original files, have to be tracked as usual in the bug tracker
: we need to clean up some inconsistencies in the english lexicons and they will be our .pot templates
: new <base> strings only have to be added (or removed) to the cvs xml file for english
*changes to original files, have to be tracked as usual in the bug tracker
*at some point we apply the new translation back to the xml file [2]
then diff against cvs, make patch, check and apply
*at some point we script xml2po to apply the new translation back to the xml file,
[1] smeserver-locale smefetchpo (added)
[2] smeserver-locale smefetchxml, smexml* smereload (to be added)
== Pootle Usage ==
== Pootle Usage ==
