Mapping Japanese characters not working as expected

Question

Hello,

For our project, we are using both Japanese and Chinese languages, so the overlapped characters need to be remapped for Japanese. We recently remapped the characters to different unicode values (compared to previous character mapping) in the Charset file for the Japanese language. It seems like the new mapping is put into the strings, but when the character is grabbed, it uses the old mapping to get and display it, resulting in characters in incorrect places and new characters appearing as empty boxes. Is there some reason the old mapping is still used to display the characters? Do we need to reload the Charset into EW somehow?

Thanks,

John

Answer 1

Hello John,

the problem you described is not fully clear for me. May be it could help me to understand it better when you provide an example project demonstrating the issue? What do you mean with reloading charsets?

Please note, that within one font resource there is always 1:1 relation between a Unicode code point and the associated glyph. Consequently, when Chinese and Japanese use the same Unicode points for different glyphs, they can't coexist within one and the same font resource. You will need:

Option 1: manage two different font resources. One with Chinese and the other with Japanese glyphs. Select the right resource depending on the text content you plan to display.

Option 2: map the overlapping characters (e.g. from Japanese) to other (unused) Unicode code points. Doing this ensure that strings containing Japanese text are correctly converted in advance to use the mapped Unicode code points. How you map the code points is explained in the section Ranges.

Best regards

Paul Banach

Comments

Hi Paul,

We are using option 2, mapping overlapping characters. For example, 0x4E2D:0xF003 is one mapping, but, on the screen, it displays as 0x4E0E (which is mapped to 0xF002). In a previous version, 0x4E2D was mapped to 0xF002.
 

John

---

Hello John,

the described problem is not clear for me. Can you provide an example project demonstrating the issue?

Best regards

Paul Banach

---

Hi Paul,

I figured out the issue. In our excel sheet, within the macro to generate the strings that are imported into Embedded Wizard, we have a function to insert the mapped unicode value for the Japanese characters. This function had not been updated when the mappings were changed so incorrect unicode values were being imported into Embedded Wizard.

Thanks,

John