RE: CSS1 becomes W3C Proposed Recommendation

It's not actually lost; any character can be escaped in a CSS selector
name.  According to section 7.2 of the CSS PR, 

'in CSS1, selectors...can also contain escaped characters and any
Unicode character as a numeric code...the backslash followed by at most
four hexadecimal digits (0..9A..F) stands for the Unicode character with
that number...any character except a digit can be escaped to remove its
special meaning, by putting a backslash in front, Example: "\"" is a
string consisting of one double quote.'

Does this suffice to address your concerns?

Chris Wilson
( And no, Internet Explorer 3.0 did not support this.  :^) )

>-----Original Message-----
>From:	Paul Prescod [SMTP:papresco@calum.csclub.uwaterloo.ca]
>Sent:	Friday, November 15, 1996 9:52 AM
>To:	Chris Wilson (PSD); 'Paul Prescod'; 'w3c-sgml-wg@w3.org'
>Subject:	RE: CSS1 becomes W3C Proposed Recommendation
>At 09:26 AM 11/15/96 -0800, Chris Wilson (PSD) wrote:
>>Sorry, I haven't been paying as close attention to this list as perhaps
>>I should have.  What's the problem with CSS using '.' as a class
>>selector indicator?
>It is a useful SGML NAME character: 
><THIS.THAT ID="Introduction.Opening.Paragraph"> 
>Since the SGML Reference Concrete Syntax ("regular SGML") doesn't allow
>underscore as a word-joiner, the loss of "." is a problem.
> Paul Prescod
>Boycott Shell Oil worldwide!  http://www.web.apc.org/embargo/shell.htm    
>"Shell is here on trial and it is as well that it is represented by counsel
>said to be holding a watching brief."..."The ecological war that the Company
>has waged in the Delta will be called to question sooner than later." -Ken
>Saro-Wiwa to the tribunal that later executed him.