- From: Håkon Wium Lie <howcome@opera.com>
- Date: Tue, 1 Feb 2011 09:34:35 +0100
- To: John Daggett <jdaggett@mozilla.com>
- Cc: www-style list <www-style@w3.org>
Also sprach John Daggett:
> The current CSS3 Text spec defines a 'hyphenation-resource' @-rule:
>
> http://dev.w3.org/csswg/css3-text/#hyphenation-resource
>
> This was based on a similar property defined in CSS3 GCPM:
>
> http://dev.w3.org/csswg/css3-gcpm/#the-hyphenate-resource-property
>
> However, neither of these reference or define a syntax for the
> hyphenation resource.
As such, the 'hyphenate-resource property is similar to the
'cursor' property:
http://www.w3.org/TR/css3-ui/#cursor
> Effectively, these are UA-specific resources when defined this way.
Not quite. Both Prince and Antenna House supports the TeX format, it
seems. Having a standardized way of referencing the hyphenation
resources therefore make sense. I believe the TeX format is also used
in many other products.
Even when differnet UAs support different formats, the comma-separated
list will handle the situation:
body { hyphenate-resource: url(hyph.dic), url(hyph.dac) }
The result would be interoperable between a formatter that supports
"dic" and the (more hypothetical) "dac" format.
Cheers,
-h&kon
Håkon Wium Lie CTO °þe®ª
howcome@opera.com http://people.opera.com/howcome
Received on Tuesday, 1 February 2011 08:35:19 UTC