- From: Jose <jose_stephen@cdactvm.in>
- Date: Tue, 7 Nov 2006 12:14:14 +0530
- To: "Chris Lilley" <chris@w3.org>, "Paul Nelson \(ATC\)" <paulnel@winse.microsoft.com>
- Cc: <www-style@w3.org>
The following font rendering rules for Malayalam (Indic language) are handled by operating system itself in the case of normal fonts. eg:- 1.. Malayalam letter KA (0D15) + Malayalam Vowel sign E (0D46) has to be rendered as Malayalam Vowel sign E (0D46) + Malayalam letter KA (0D15) 2.. Malayalam letter KA (0D15) + Malayalam Vowel sign O (0D4A) has to be rendered as Malayalam Vowel sign E (0D46) + Malayalam letter KA (0D15)+ Malayalam Vowel sign AA (0D46) etc.. But in the case of SVG document even if the glyph set are provided it is not rendering properly (i.e displayed in the order in which the text is provided).Is it because of lack of support of browser/OS/plugin? We can make the text render by changing the order in the text.But it is not the correct method as Chris Lilley point out.Can any one tell any method for mentioning it in SVG Font file itself? With regards Jose Stephen ----- Original Message ----- From: "Chris Lilley" <chris@w3.org> To: "Paul Nelson (ATC)" <paulnel@winse.microsoft.com> Cc: "Jose" <jose_stephen@cdactvm.in>; <www-style@w3.org> Sent: Tuesday, November 07, 2006 5:22 AM Subject: Re: Rendering of Svg Font > > On Monday, November 6, 2006, 11:02:01 PM, Paul wrote: > > PNA> There needs to be a higher level protocol to shape and position > glyphs > > Yes > > PNA> before things are sent to SVG. > > No. You don't "send glyphs" to SVG. You send characters to SVG. As you > correctly note, shaping and positioning takes place at the glyph level. > > PNA> Complex script languages cannot be > PNA> handled by simply sending Unicode strings of characters. > > Now, if you had said "simply sending lists of glyphs" that would be > correct. > > > -- > Chris Lilley mailto:chris@w3.org > Interaction Domain Leader > Co-Chair, W3C SVG Working Group > W3C Graphics Activity Lead > Co-Chair, W3C Hypertext CG > ______________________________________ Scanned and protected by Email scanner
Received on Tuesday, 7 November 2006 06:49:16 UTC