- From: Ian Hickson <ian@hixie.ch>
- Date: Sat, 25 May 2002 15:00:10 +0100
- To: Etan Wexler <ewexler@stickdog.com>
- CC: David Baron <dbaron@fas.harvard.edu>, www-style@w3.org
Etan Wexler wrote: > > The exact case equivalences need listing. Since the Unicode Standard has already > listed them, a normative reference to the latest UnicodeData file will suffice. This > assumes that CSS will not permit special case equivalents. There is already a normative reference to UNICODE, and recent drafts have a further reference to CHARMOD. That should suffice. > Then we need to note in all syntax definitions that the identifiers (and names, as in > HASH tokens) allow escape sequences that correspond to the given characters or to the > case equivalents of the given characters. That's already in the grammar. -- Ian Hickson ``The inability of a user agent to implement part of this specification due to the limitations of a particular device (e.g., non interactive user agents will probably not implement dynamic pseudo-classes because they make no sense without interactivity) does not imply non-conformance.'' -- Selectors, Sec13
Received on Saturday, 25 May 2002 10:10:00 UTC