With the new webERP 3.11 release, translators must take the new en_GB messages.po into account. To merge the existing translation file with the new en_GB we will run the command msgmerge, for example:
msgmerge --no-wrap --update path-to-translated-existing-po-file path-to-enGB-po-file
Before executing the command, 2 very important things must be taken into account:
1) Make a backup of the existing translation .po file or run msgmerge with the option --backup (see msgmerge --help), because the translation file will be overwritten.
2) Change CHARSET in en_GB messages.po header to match the file itself (it is an utf-8 text file); otherwise, you will get the following warning: "The set of characters "CHARSET" is not a portable codification name" "Messages conversion could not work"
Remember that the line 16 at header,
"Content-Type: text/plain; charset=CHARSET\n"
means the code that file uses itself, i.e., what codeset was used to save the file on disk (not the webERP charset to serve content that must remain ISO) and, as you may see, en_GB messages.po is an utf-8 text file itself.
The best practice is to use utf-8 for both en_GB and translation. Indeed, all translation .po files should be saved and edited as UTF-8 files (in the same way that all webERP's PhP scripts are also UTF-8 text files); and this should be properly declared/expressed in their .po header.
javier
------------------------------------------------------------------------------
Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day
trial. Simplify your report design, integration and deployment - and focus on
what you do best, core application coding. Discover what's new with
Crystal Reports now.
http://p.sf.net/sfu/bobj-july_______________________________________________
Web-ERP-translation mailing list
Web-ERP-translation@...
https://lists.sourceforge.net/lists/listinfo/web-erp-translation
