Re: [Fontforge-devel] [Fwd: [ fontforge-Feature Requests-1341892 ] GB 12345-90 support]

[George W. <gw...@si...>]

On Sun, 2005-10-30 at 16:38, Werner LEMBERG wrote:
> > Someone asked for support for GB 12345-90 encoding, and then went on
> > to explain that it was just the same as GB2312 except that it used
> > traditional glyphs.
> > 
> > In my ignorant way I would think that would mean that as far as I am
> > concerned the two are the same and the user should be able to use
> > GB2312 while making his traditional glyphs.
> 
> No, this won't work.  Remember that the Unicode mappings would be
> wrong altogether.
? He says GB 12345-90 is the same as GB2312-80 except that it uses
traditional glyphs rather than simplified ones. Is that incorrect? I
assume that both the traditional and simplified glyph will have been
unified to one unicode code point. Is that incorrect? 
>   In Unicode's Unihan.txt file just extract the
> `kGB1' entries for a proper mapping.
I guess it is incorrect then. They do yield different values.

But you can't have a truetype font with such an encoding. Open/True Type
only supports GB2312 (and Big5) for Chinese. I'm leery of adding a 2byte
encoding which can't be used to generate a font.