Re: [CSS21] Case-insensitivity not defined

Having *some* of the characters be case-insensitive and *some *be
case-sensitive seems the worst of all the choices. I suspect that this will
lead to no end of user confusion; for example,

   - duerst = DUERST
   - but dürst != DÜRST

and claims of favoritism for English.

Mark

On Nov 18, 2007 3:59 PM, fantasai <fantasai.lists@inkedblade.net> wrote:

>
> Martin Duerst wrote:
> > At 04:59 07/11/19, Addison Phillips wrote:
> >> Martin Duerst wrote:
> >>> - Identifiers within CSS. These include cases such as
> >>>   namespace prefixes and counter names inside CSS.
> >>>   Ideally, these should just work case-sensitive; I don't
> >>>   think it's asking too much from stylesheet writers to
> >>>   use the same case for all occurrences of a specific
> >>>   counter name. If that's not possible for legacy reasons
> >>>   (e.g. stylesheets that indeed use counter names and
> >>>   friends with haphazard casing), then something like
> >>>   'case-insensitive for US-ASCII, case sensitive for
> >>>   the rest', even though it sounds terribly ugly, may
> >>>   be the best solution.
>
> Proposed change:
>
> In Section 4.1.3 Characters and case change
>   # All CSS style sheets are case-insensitive, except for
>   # parts that are not under the control of CSS.
> to
>   | All CSS syntax is case-insensitive within the ASCII
>   | range (i.e. [a-z] and [A-Z] are equivalent), except for
>   | parts that are not under the control of CSS.
>
> ~fantasai
>
>


-- 
Mark