Original en_GB messages POT file

[Javier de Lorenzo-Cáceres]

Some parts of this message have been removed. Learn more about Nabble's security policy.

The original en_GB messages file should be named "messages.pot" instead "messages.po" because it's a .pot, i.e., a GNU Gettext Template. All gettext tools like msgmerge and poedit refer to this kind of files as .pot files.

 

If we open the file with poedit as it was a po, poedit gives an error because CHARSET is not a valid charset,

 

"Content-Type: text/plain; charset=CHARSET\n"

 

What some instructions in the HowToTranslate wiki page tell it's how to convert a .pot to a .po - to change CHARSET with a proper valid charset.

 

After 5 months, I find poedit a better way than text editors for the translation job. Now I only use a text editor to look for the php scripts where the msgids are located and to convert the .po from UTF-8 to ISO.

 

Poedit doesn't make charset conversions as some editors do. If an ISO .po has a header misdeclaring UTF-8, then poedit doesn't open the .po and gives an error message. If vice-versa, the misdecoding may be seen at glance.

 

To begin a translation from scratch, just open poedit, setup the catalog "Catalog -> Options",  and load a .pot file "Catalog -> Update from POT file"

 

"Update from POT file" will do the same than the command "msgmerge file.pot file.po" with some command options.

 

regards,

javier

 

 

 

------------------------------------------------------------------------------
Come build with us! The BlackBerry(R) Developer Conference in SF, CA
is the only developer event you need to attend this year. Jumpstart your
developing skills, take BlackBerry mobile applications to market and stay
ahead of the curve. Join us from November 9 - 12, 2009. Register now!
http://p.sf.net/sfu/devconference
_______________________________________________
Web-erp-developers mailing list
Web-erp-developers@...
https://lists.sourceforge.net/lists/listinfo/web-erp-developers