- From: Chris Lilley <chris@w3.org>
- Date: Mon, 1 Jun 2009 08:27:37 +0200
- To: Cameron McCormack <cam@mcc.id.au>
- CC: public-svg-wg@w3.org
On Monday, June 1, 2009, 6:46:55 AM, Cameron wrote: CM> If we have time, I’d like also to discuss: CM> * Multiple <missing-glyph> CM> http://www.w3.org/Bugs/Public/show_bug.cgi?id=4930 CM> With some preliminary testing, it seems that Batik and WebKit use the CM> first <missing-glyph>, while Opera uses the last. Why is that an issue? Quoting CSS 2.1 "The UA should map each character for which it has no suitable font to a visible symbol chosen by the UA, preferably a "missing character" glyph from one of the font faces available to the UA. " http://www.w3.org/TR/CSS21/fonts.html#algorithm The UA can pick any "missing glyph" (the wording "missing character" in CSS2.1 is loose and not in conformance with the character model). It might be from the svg font, from another font in the list, or from a fallback font. I have also seen a more informative missing glyph style which gives the hex code of the unicode block. All of these are fine. -- Chris Lilley mailto:chris@w3.org Technical Director, Interaction Domain W3C Graphics Activity Lead Co-Chair, W3C Hypertext CG
Received on Monday, 1 June 2009 06:28:06 UTC