Revision as of 02:34, 1 February 2005 edit Mjb (talk \| contribs) Extended confirmed users 10,716 edits →"IE5 was the first to use glyphs from 'best available' fonts": cited documentation and examples; IE does it for some, but apparently not all, cases ← Previous edit		Revision as of 04:27, 1 February 2005 edit undo Mzajac (talk \| contribs) Autopatrolled, Extended confirmed users 66,545 edits →"IE5 was the first to use glyphs from 'best available' fonts" Next edit →
Line 77: :Various other links I found via Google make it sound like "font linking" is something that one can also do when coding one's own apps (browser-based or standalone) by scripting an IE-specific COM object (MLang) in order to render multilingual text [http://msdn.microsoft.com/workshop/misc/mlang/tutorials/fontlinking.asp]. - [[User:Mjb\|mjb]] 02:34, 1 Feb 2005 (UTC) :: I have a stock XP system for testing web sites, and I loaded that test page in my browsers. None displayed the Kanji or Hankaku, presumably because I haven't added any fonts to the system. Firefox displayed the three lines labelled Romanj, but MSIE 6 and Opera 7.5 only showed squares there. ::MSIE 6 is ahead of Netscape 4, in that it can display Unicode from multiple encodings on one page. But I have yet to see any instance where it chooses a font other than what is specified in a web page (in very little testing, I admit). I'm curious to know how the font linking works. But in the mean time, in terms of multi-Unicode block display, it's the one browser that I have to do extra work for (as it also is in terms of CSS rendering). ''—[[User:Mzajac \|Michael]] [[User talk:Mzajac \|Z.]] <small>2005-02-1 04:27 Z</small>''

Talk:Unicode and HTML: Difference between revisions