It's very much working that way in any serious browsers. Some font formats (e.g. bitmaps for XWindows on Unix) use layouts corresponding to traditional encodings. Truetype fonts used on many systems can be directly accessed by Unicode, but part of the info in a conversion table is still needed to know what characters (actually glyphs!) a font covers.
Regards, Martin. At 10:37 01/11/29 -0500, Suzanne M. Topping wrote: > > -----Original Message----- > > From: [EMAIL PROTECTED] > > > I think maybe that encoding (on the Internet) does not much > > matter. As long as my browser knows that it is looking at > > Unicode, it knows which, say, SJIS, character to look up in > > the font to display. Must have table lookup or something. > >Now THAT's a Browser!!! What the heck are you using? Apologies for my >incredulity, but I'd be surprized if the browser has this level of >sophistication... I question whether it's working the way you describe, >but I could of course be wrong.
