Re: [css3-text] @text-transform from Christoph Päper on 2012-01-07 (www-style@w3.org from January 2012)

From: Christoph Päper <christoph.paeper@crissov.de>
Date: Sat, 7 Jan 2012 19:48:38 +0100
To: www-style list <www-style@w3.org>
Message-Id: <FDDD4A22-FFD4-4BD5-B645-C1F275962E67@crissov.de>

When the scope descriptor is used in combination with a reference to a previously defined transform you currently suggest that the resulting scope is their intersection. That means on the one hand, ‘all’ is then always ignored, on the other hand, if two different single values out of ‘initial’, ‘medial’ and ‘final’ are combined the transform matches nothing. I don‘t think that is ideal, but I don’t have a better solution either.

The German ‘ß’ example states that there traditionally is no uppercase variant, i.e. the character is not a letter proper, but a ligature equivalent to ‘ss’ – accordingly, current implementations transform it to ‘SS’ for ‘uppercase’ (like they turn ‘ﬁ’ into ‘FI’). That means

  transformation: uppercase, "ß" to U+1E9E;

can only work, if later partial transformations can overrule earlier ones, even if they are predefined in CSS2 (and possibly employ mappings that the at-rule cannot express yet). Otherwise the above rule would be equivalent to

  transformation: uppercase;

Received on Saturday, 7 January 2012 18:51:44 UTC