On Tue, Mar 26, 2002 at 05:30:29PM -0000, Tomas Frydrych wrote: > > > Cheesy hack: When we read the width for unicode 32, also copy it to be > > the width for unicode 160. > > The "real" solution is to have two separate look up tables, one for > translating Unicode -> Adobe and the other Adobe->Unicode. I > have been very reluctant to go this way since the number of glyphs > impacted is small (I do not know of other than NBS), and the > lookup tables are sizeable. A hard coded workaround is, therefore, > I think best.
The problem is that Adobe -> Unicode is not a function. The URL I referenced mention that there are 8 double mappings (one adobe glyph to two unicode chars), most of which are uncommon in most documents. Let's stick with the hard coded workaround. pat
