- From: Mike Bremford <mike-css@bfo.co.uk>
- Date: Tue, 7 Nov 2006 09:05:00 +0000
- To: www-style@w3.org
I know zip about SVG, but we've just been implementing Indic support and there's a lot more to it than just defining ligatures. Full support requires some fairly considerable pre-processing even before you start applying the rules in the GSUB and GPOS tables (I'm assuming Opentype fonts here). > That would violate one of the accessibility principles of SVG, namely > that simple text should be simple text. Being in an Indic language > doesn't make it non-simple in this context. The shaping rules are well defined [2] and shouldn't require any additional info in the SVG to implement, just as they don't for HTML. However the text (in logical order) must be reordered and converted to glyphs by the SVG viewer using a shaping engine that handles Indic - Uniscribe on Windows, Pango on Linux. It sounds like that's not happening in this case. Jose, I'm afraid either way you're on the wrong list, as this has nothing to do with CSS. It sounds like a bug in your SVG viewer/ plugin to me - I'd suggest contacting them. [1] http://www.w3.org/TR/SVG/text.html#AlternateGlyphs [2] http://www.microsoft.com/typography/OpenType%20Dev/indic/intro.mspx Cheers... Mike
Received on Tuesday, 7 November 2006 09:05:24 UTC