Content deleted Content added
→"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 |
|||
Line 67:
''—[[User:Mzajac |Michael]] [[User talk:Mzajac |Z.]] <small>2005-01-31 07:22 Z</small>''
:Hi. Yes, I see that IE is having trouble with unformatted text in your example.
:I based my assertion on the mention of "font linking" in this paper, presented at the 16th International Unicode Conference back in 2000: ''[http://www.unicode.org/iuc/iuc16/c6/paper.pdf New International features of Internet Explorer]''. I did not research the issue beyond this, but it does appear that IE has at least some support in this regard, and has it it in a less capable form since IE 4.0 days.
:Researching a bit just now, I found another description of the technology: ''"Font linking is basically the technology that Internet Explorer uses to be able to display characters from multiple languages within a single page at once. So for example, you can have Japanese and Chinese and Korean and Arabic and Devanagari and whatever character set you want, all on the same page. And there are some neat pages of that on the Internet that actually demonstrate this capability. What Internet Explorer does is it looks up certain fonts within the operating system that support this ability called font linking. What that means is that these fonts have the ability, if a character is not within that current font, to be able to look up a character and an associated font. So, for example, you could set your page to display to Japanese and set the font to Mincho, a popular Japanese font. Now let's say you have Korean within the same page. Because of the way Internet Explorer handles this, and the way it keys off this font linking capability, it can identify that the Korean characters aren't within the Mincho font, but it can get references to a Korean font that will handle those characters. And so if you look up a page with both Japanese and Korean, you'll see the Japanese page using the Mincho font and the Korean part of the page will be using GulimChe, or another Korean font."'' [http://support.microsoft.com/?scid=http://support.microsoft.com%2Fservicedesks%2Fwebcasts%2Fen%2Fwc050400%2Fwct050400.asp]
:This makes it sound perfect, and rather automatic, doesn't it? And in fact, on my system, with IE6 on Windows XP SP2, I have no problem rendering [http://ourworld.compuserve.com/homepages/paulgor/utf8-jap.htm this test page]. So I would conclude from this that IE is doing the same thing as other browsers; the others apparently just do it better or 'more thoroughly'. Someone will have to do further research in order to determine what the quirks are in IE's built-in font linking. Anyway, I don't think it was correct to assert that IE doesn't do it at all, while these others do.
: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)
| |||