Hi, The Thai OOo translator team has done OOo translation since 2.0, integrated in 2.0.1 (but not in time for 2.0.2).
We have a serious problem. We use po for translation to leverage already available tools. We convert SDF to po, then translate them, then convert them back. I guess this is the normal process for many locale. (?) However, when finish 2.0, and try to merge po (from SDF) update from 2.0.1, we have a problem. When we finish 2.0.1 po and try to merge from m150, we have the same problem. I'm not the one who did the process so I may not describe the problem correctly. The problem is something like some entres in the SDF are moved to other source files (result in bad po merge), some entries have the same msg id in po. We're trying to hack the tool to make it workable. I guess many of you should have found the same problem if you use po. How do you solve them? Thanks. -- _/|\_ Samphan Raruenrom. Open Source Development Co., Ltd. Tel: +66 38 311816, Fax: +66 38 773128, http://www.osdev.co.th/
smime.p7s
Description: S/MIME Cryptographic Signature
