|Posted: Tue, 2009-03-10 21:26|
I'm in the process of migrating from G1 (v1.5-RC2) to G2. But it's driving me nuts because they seem to treat foreign characters (Traditional Chinese) differently.
In G1, for unknown reasons over the course of 4+ years I've been using it, those Traditional Chinese characters typed longer time ago are scrambled and look like "¾÷³õ,Ä_¤s·s®a,²y³õ" but the more recent ones looks fine. This is not a big deal as most Chinese characters were entered more recently.
However, this has become a big issue for my G1-G2 migration. During or after migration of selected test albums from G1 to G2, those characters that were scrambled in G1 become visible but all the recent ones become something like "野 柳". I checked around and found these are HTML decimal character rendering codes. Each code corresponds to the character position in Unicode character set.
I've tried most "Character Encoding of Source Text" choices with G2's G1 import module and the problem persists.
It appears to me that G1 accepts or preserves html decimal characters but G2 doesn't understand it and stores and renders them as ASCII characters.
Anyone knows how to fix it? I'd really really appreciate any comments!