W3C home > Mailing lists > Public > public-svg-wg@w3.org > October to December 2008

ISSUE-2102 (ligatures): i18n comment 1: Explanation of ligatures [Last Call: SVG 1.2 Tiny ]

From: SVG Working Group Issue Tracker <sysbot+tracker@w3.org>
Date: Fri, 10 Oct 2008 21:31:55 +0000 (GMT)
To: public-svg-wg@w3.org
Message-Id: <20081010213155.2C3AB5F74D@stu.w3.org>

ISSUE-2102 (ligatures): i18n comment 1: Explanation of ligatures [Last Call: SVG 1.2 Tiny ]


Raised by: Doug Schepers
On product: Last Call: SVG 1.2 Tiny 

Richard Ishida
Comment 1
At http://www.w3.org/International/reviews/0810-svg-tiny/
Editorial/substantive: E
Tracked by: RI

Location in reviewed document:
10.2 [http://www.w3.org/TR/SVGMobile12/text.html#CharactersAndGlyphs]

"(Note that for proper rendering of some languages, ligatures are required for certain character combinations.)"

"Composite characters - In various situations"

"Some typography systems examine "

"In some languages, particular sequences of characters "

I would change 'some' and 'various' to 'many'. Ligatures are required in scripts all across Asia, and composite messages are even more common. Especially since this is SVG Tiny, and will therefore play a role in the mobile Web, I think it's important to make implementers consider support for complex script features. I did some testing of the font features and noted that OpenType features required for the Indic scripts I tested were not supported. This is a common scenario, and has been for a long time. I don't think implementers are actually aware of the fact that ligatures and such are not just frilly features for most languages throughout Asia. I'd generally like to see a little more emphasis on this in the document. (I'd have actually liked to see a graphical example of rendering in a complex script here - i may be able to provide one if you like.)
Received on Friday, 10 October 2008 21:32:33 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 17:29:40 UTC