W3C home > Mailing lists > Public > www-style@w3.org > July 2010

Re: [css3-fonts] unicode-range and unicode normalization

From: fantasai <fantasai.lists@inkedblade.net>
Date: Tue, 13 Jul 2010 00:45:20 -0700
Message-ID: <4C3C1990.2070602@inkedblade.net>
To: John Daggett <jdaggett@mozilla.com>
CC: Yuzo Fujishima <yuzo@google.com>, www-style@w3.org, www-font <www-font@w3.org>
On 07/12/2010 08:06 PM, John Daggett wrote:
> fantasai wrote:
>>   * The UA must choose a single font for each grapheme cluster. [UAX10]
> Did you mean to refer to UAX10?  UAX10 is the Unicode Collation
> Algorithm and deals with how to compare two Unicode strings. Matching
> character streams to font character maps is a different problem, since
> the goal is not to determine equivalence but rather to render a
> character sequence correctly.

No, I meant [UAX29]. :) Sorry.

>> A related topic would be what happens when the base character is in
>> one element, the combining character in another, and the two are
>> assigned different fonts. Do we want different behavior for that
>> than for assigning different fonts through unicode-range?
> This starts to push into the realm of saving users from themselves. In
> general, I don't think we should burden implementations with complex
> error handling requirements like this unless it's really a common
> occurrence that's hard for the author to work around.  Codepoints
> defined in unicode-range descriptors act as a filter on the codepoints
> in the cmap of a font, I don't think we should blur that based on
> complex conditions.

I don't mind much what we do here, and am happy to leave it undefined
if that's easier. (I can see use cases for wanting part of a grapheme
cluster in a different color, which, depending on the font, may or may
not be possible--but not for having part of it in a different font.)

Received on Tuesday, 13 July 2010 07:46:10 UTC

This archive was generated by hypermail 2.4.0 : Friday, 25 March 2022 10:07:48 UTC