Also sprach Brad Kemper: > Yes. How about this for hiding spaces by transforming them to an empty string: > > @text-transform no-spaces { convert: "\ " to ""; } Looks right. > I think it would be good to have examples like that in the spec > when we have one. It would show that the only way to convert > characters to an empty string is if the entire "to" part is "". Or > it could be " " or " ", etc. I suppose, since the spaces are just > seperators. . Yes. There are many ways to make text disappear, I'm afraid :) > > Should we allow "negative" ranges? As in: > > > > convert: z-a to "•"; > > > > Probably not. The presence of a "negative range" should probably lead > > to discarding the whole statement: > > > > convert: "0-9 z-a A-Z" to "•"; } /* no effect */ > > convert: lowercase, "æ" to "Æ", "0-9 z-a A-Z" to "•"; } /* no effect */ > > I don't feel strongly about that. To me, z-a and a-z seem to > unambiguously mean the same thing. But I wouldn't fight for the > right to write z-a. They probably don't do any harm. And allowing them will give us fewer rules for error handling. So, let's. -h&kon Håkon Wium Lie CTO °þe®ª howcome@opera.com http://people.opera.com/howcomeReceived on Friday, 16 December 2011 19:45:48 UTC
This archive was generated by hypermail 2.4.0 : Friday, 25 March 2022 10:08:08 UTC