David Starner <[EMAIL PROTECTED]> wrote: > There's no confusion. If the content tag is going to be read without > outside knowledge of the encoding form, then it's got to be in ASCII, > and since it's got to be in SCSU, too, it has to be in that common > subset - i.e. CR/LF/HT and printable ASCII. Well, that's certainly true -- the Content-Type tag does have to be in straight ASCII. I thought you meant that SCSU itself was straight ASCII, which is only true in the trivial case. -Doug Ewell Fullerton, California
- Re: Unicode on a website Lars Marius Garshol
- Re: Unicode on a website Lars Marius Garshol
- Re: Unicode on a website Michael \(michka\) Kaplan
- Re: Unicode on a website Lars Marius Garshol
- RE: Unicode on a website Carl W. Brown
- Re: Unicode on a website James Kass
- Re: Unicode on a website David Starner
- Re: Unicode on a website Roozbeh Pournader
- Re: Unicode on a website David Starner
- Re: Unicode on a website Doug Ewell
- RE: Unicode on a website Doug Ewell
- RE: Unicode on a website Carl W. Brown
- Re: Unicode on a website Andrew Cunningham
- Re: Unicode on a website David Starner
- RE: Unicode on a website Doug Ewell
- Re: Unicode on a website Elaine Keown
- Re: Unicode on a website Michael \(michka\) Kaplan
- Re: Unicode on a website Doug Ewell
- Re: Unicode on a website Erik van der Poel

