From: Ken Whistler (firstname.lastname@example.org)
Date: Fri May 20 2011 - 14:37:36 CDT
On 5/19/2011 8:45 AM, FrÃ©dÃ©ric Grosshans wrote:
> The section 12.2 of the unicode standard 6.0 contains the following
> sentence (p412, paragraph "rendering") :
> An implementation may render a valid Ideographic Description
> Sequence either by rendering the individual characters
> separately or by parsing the Ideographic Description Sequence
> and drawing the ideograph so described.
> So "to parse an IDS and substitute an appropriately constructed CJK
> ideograph glyph on the fly for display" would not be totally unexpected.
It isn't disallowed, but the emphasis there should be on the *may*.
As long as you are quoting, note also, earlier in Section 12.2:
In particular, support for the characters in the Ideographic Description
block does *not* require the rendering engine to recreate the graphic
appearance of the described character.
The primary purpose of Ideographic Description Characters is to allow
systematic description of unencoded CJK characters. The mechanism
is not a replacement for an actual sophisticated glyph description
language, nor is it intended as a means of representing unencoded
CJK characters regularly in text with an expectation that rendering engines
would simply render fully-formed glyphs correctly.
This archive was generated by hypermail 2.1.5 : Fri May 20 2011 - 14:43:42 CDT