Difference between revisions of "Talk:Translations"

From SME Server
Jump to navigationJump to search
Line 25: Line 25:
 
: we create .po files from the english versions  
 
: we create .po files from the english versions  
 
: using subversion we load these into pootle as .pot template files
 
: using subversion we load these into pootle as .pot template files
: see http://wiki.contribs.org/Xml2po
 
  
 
* changes to original files, have to be tracked as usual in the bug tracker
 
* changes to original files, have to be tracked as usual in the bug tracker

Revision as of 19:36, 8 March 2008

bugs

Bugs related to Pootle based translations are linked here

Translation Workflow

Draft suggestions ...

.po files

  • gettext strings are in various files in cvs
we use xgettext to creates .pot files from the original files to by extracting gettext strings [1]
developers load these into pootle as .pot template files using subversion
  • .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
these are imported into the template .pot files using subversion
  • at some point we diff updated po files against cvs po files, the patch is checked and applied.

FormMagick files

  • these are XML files with a <base> and <trans> pair of strings
we create .po files from the english versions
using subversion we load these into pootle as .pot template files
  • changes to original files, have to be tracked as usual in the bug tracker
<base> strings only have to be added (or removed) to the cvs xml file for english
  • at some point we apply the new translation back to the xml file

then diff against cvs, make patch, check and apply

[1] smeserver-locale.src.rpm smefetchpo