W3C home > Mailing lists > Public > www-style@w3.org > February 2004

Re: [CSS21] response to issue 115 (and 44)

From: Jungshik Shin <jshin@i18nl10n.com>
Date: Tue, 24 Feb 2004 05:27:26 +0900 (KST)
To: www-style@w3.org
Message-ID: <Pine.LNX.4.58.0402240520280.9245@jshin.net>

On Mon, 23 Feb 2004, Jukka K. Korpela wrote:

> On Mon, 23 Feb 2004, Henri Sivonen wrote:
>
> > On Feb 21, 2004, at 00:26, Bert Bos wrote:
> >
> > >  4) If all else fails, assume UTF-8.
> >
> > Why not windows-1252 (with the few undefined bytes mapped to
> > *something* so that all byte streams can be converted some
> > "characters")?

  Why not? Because there are a lot of stylesheets in encodings other
than Windows-1252. If you don't like UTF-8, you'd better ask for
ISO-646:IRV.

> > Anyway, it's just
> > plain stupid to use non-ASCII outside comments in a style sheet that
> > doesn't have a character encoding label and doesn't have a BOM, so in
> > the relatively rare cases where this heuristic fails, the author would
> > have only him/herself to blame.
>
> Indeed. And currently most style sheets contain Ascii only.

  True in Western Europe and most other parts of the world. Not true in
Japan, China and Korea. I'm not talking about comments here. A number
of stylesheets list font-family names in Chinese, Japanese and Korean in legacy
encodings (GB2312, Big5, Shift_JIS, EUC-JP, EUC-KR, etc).

  Jungshik
Received on Monday, 23 February 2004 15:27:30 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Monday, 27 April 2009 13:54:26 GMT