TrueKeys v1.0 - v2.1 Copyright: Xiaolin Zhao, 1996-1997.
TrueKeys v3.0 - v3.5 Copyright: UniDoc System LLC, 1998-1999.
All rights reserved.

• RichWin Chinese PC font 1/2 width problem
• Use custom Unicode mapping table for TrueKeys

Some PC programmers do not know too much about the required MacOS roman cmap format. They just tried their best as long as the font works on Windows. These font bugs cause troubles when converted to MacOS.

Take GTHT.TTF from RichWin as an example, this GB encoded font will have only half width when converted to MacOS format with Microsoft GBK->GB.

But the good news is that the GBK->GB also adds a Apple Unicode 2.1 encoding during font conversion. To fix the font width problem, use TrueKeys to convert the converted MacOS formated font one more time, but using Apple Unicode 2.1 -> GB conversion. This conversion will fixed the redundent encoding mapping introduced by those guilty PC programmers.

In summary, for all RichWin GB fonts:

• Do Microsoft Simp. Chinese (GB2312)->Simp. Chinese (GB2312) conversion
• Do Unicode 2.1 -> Simp. Chinese(GB2312) conversion

2) I need to convert MS Gothic Japanese font to Mac format. But the converted Mac font does not contain some characters which is available on PC. Is there a solution?

MS Gothic font is a Unicode font with some extension. When it is converted into Mac format, the Unicode 2.1 -> Shift-JIS encoding conversion must be made. UniDoc uses the Unicode 2.1->Shift-JIS supplied by Microsoft (if you selected the Microsoft encoding option) in the standard release.

If the standard Unicode 2.1 mapping table does not support certain code in the original font, these code/glyph will be lost in the conversion. Notably, all Japanese code with high byte larger than 0xed will not be able to appear in Mac format after the standard conversion.

If you are registered TrueKeys user, you may send in your custom mapping table in text format. We will compile the mapping table for you to assemble into TrueKeys for your use.