Thank you for quick response. > The egw charset system relies on the "charset" string in phpgwapi, which > currently is set to "EUC-JP" for japanes. This means that the translation > class assumes that all phpgw_ja.lang files use EUC-JP encoding, and sets the > db engine to use that charset for all tables by default. You can tell egw in > setup to use utf-8 or any other useful charset for the encoding (we'll assume > you chose utf-8 for this example), in whose case a EUC-JP->utf-8 conversion > will take place, and since the egw_lang table (where the strings are stored) > is defined at setup time to use that charset, the original strings in EUC-JP > will be correctly encoded, while any string in a different source charset > should be stored wrong. This means that you can't mix different encodings in > the same table, nor use different charsets for the same language.
I was not aware of the charset string at first, I got into trouble. (So, my python code explicitly repalces "EUC-JP" with "UTF-8".) > So, I'd like to follow the discussion about the pros and cons about keep using > EUC-JP or convert it all to utf-8, mostly because issues raising in postgresql > (or other dbs) that need and specific charset defined at installation time. > As I need to handle CJK characters and iso-Latin accented alphabets at the same time, I chose using utf-8 at eGroupware installation (it is also the eGroupWare installer's recommendation). ------------------------------------------------------------------------- Using Tomcat but need to do more? Need to support web services, security? Get stuff done quickly with pre-integrated technology to make your job easier Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642 _______________________________________________ eGroupWare-translation mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/egroupware-translation
