|
From: Peter B. <ps...@vi...> - 2012-02-16 11:26:06
|
Ah, that explains it. Choose Unicode-BMP encoding for your font and put your non-standard glyphs in the Private Use Area (encodings E000 and higher if I recall rightly). No need for "add encoding slots." Peter S. Baker University of Virginia On Feb 15, 2012, at 10:40 PM, Marco Ricci <mar...@ya...> wrote: > --- On Wed, 2/15/12, Peter Baker <ps...@vi...> wrote: > >> I'm not sure what you mean by "slot number." In FontForge you don't >> have to worry about anything but glyph names and Unicode encodings. >> If you add encoding slots, these are normally for unencoded glyphs. >> You can have as many as you want, pretty much. > > I just used fontforge's terminology that it uses when I click on "Add Encoding slots." I guess this corresponds to the unicode value, but since my glyphs are non-standard, I thought I will use some non-standard slot numbers for my program without encroaching on unicode ranges. > > ~~marco |