In Windows ME, works in IE5.5 but not in Netscape 4.7 or Mozilla 2001021204.
So I doubt it would work in say Linux (I haven't tested it, but might be
able to later on).
In IE5.5/ME, it works for me not only with different fontName values, but
even with a list (e.g.,
var fontName="Arial Unicode MS,Lucida Sans Unicode"
). Of course, the list simply uses the first font that's available,
regardless of whether the font contains any number of the characters being
mapped (so if one has both fonts, and puts Lucida Sans Unicode first, code
points that LSU doesn't provide glyphs for are displayed as artifact
characters (mostly boxes)).
Good job. Next time, though, I'd suggest using CSS rather than the
deprecated <font> element.
> I wrote a small HTML document that implements a quick-and-dirty chart for
> Unicode, and I thought that someone on the Unicode list could find it
> The whole 17 planes may be reached, and you can see the three standard
> encoding forms (not the schemes!) of each character.
> The document is formed by two HTML files and can be used off-line. Of
> course, whether your browser shows the correct glyphs or just boxes
> on the availability of fonts and Unicode support in your browser.
> I only tested it with Internet Explorer 4.0 on Windows NT (sp6), and I
> font Arial Unicode MS installed.
> I don't absolutely know (nor give warranties about) whether and how it
> on a different environment.
> If anyone is adventurous enough to wish to try it, find the two files
> attached. You should put both in the same directory, and open
> in your browser.
> Hint: red text is clickable and has some effect; black text is static.
> If you wish to read the sources, both files start with an explanatory
> comment, but the rest is totally uncommented (yet).
> Have fun (I hope).
This archive was generated by hypermail 2.1.2 : Tue Jul 10 2001 - 17:21:20 EDT