RE: [css3-fonts] humane 'unicode-range'

> > I don't think adding this to "unicode-range" makes sense. The 'unicode-range'
> selector is one specific, effective mechanism for one specific use--selecting font
> based on a range of Unicode code points.
> 
> I don't think I agree with you on this. The point of the unicode-range descriptor
> in @font-face is to control which characters a particular font is used to render;
> but selecting on the basis of the actual numeric values of Unicode codepoints is
> not necessarily the most useful way to express this.

 [AP>] I agree with you. I just think it makes implementing "unicode-range" complicated (think of writing the value parser). We want features that will be both useful and fully/interoperably implemented. Unicode code point ranges are implemented in some font selection systems, etc., already. Instead of making this feature (which I recognize has limited utility) more complicated, what I'm suggesting is providing appropriate property-based selectors with clear implementation descriptions.


> 
> Personally, I'd like to see ways to express the "ranges" of interest for unicode-
> range in terms of various properties defined in the Unicode character database,
> in a similar way to the use of properties to express character classes in Unicode
> regexps, as an alternative to cumbersome [....] expressions.
> 
[AP>] I agree that this is desirable, since I've had to deal with this myself. The question is what features to provide and how to provide them. Koji is suggesting adding more states/classes/values to unicode-range. I guess I'm suggesting that 'unicode-range' is good for code point ranges and that some other selector can be created for property selection, noting that both potentially have utility outside font selection too.

Addison

Addison Phillips
Globalization Architect (Lab126)
Chair (W3C I18N WG)

Internationalization is not a feature.
It is an architecture.

Received on Monday, 2 May 2011 00:01:37 UTC