W3C home > Mailing lists > Public > www-html@w3.org > June 2006

Re: Problem in publishing multilingual HTML document on web in UTF-8 encoding

From: आशीष शुक्ला \ <wahjava@gmail.com>
Date: Sat, 3 Jun 2006 22:02:56 +0530
Message-ID: <d9a03f10606030932r156a9075u528157ff7771478e@mail.gmail.com>
To: www-html@w3.org

On 6/3/06, Sebastian Redl <sebastian.redl@getdesigned.at> wrote:
> The practical problem here is, what signals the change of the encoding?
> Is it the end of the meta element, or the end of the content attribute
> of the meta start tag? Since no such thing is specified, we can safely
> assume that the character encoding cannot change during the document.

Yup, it is the end of the <meta> tag, because the parser will accept
<meta> tag only when that tag is properly parsed. This is what I think
should happen

> Sebastian Redl

And what about EBCDIC (or other non-ASCII compatible encoding) based
XML documents which contains following prolog:

<?xml version="1.0" encoding="encoding-name"?>

I've never seen non-ASCII based XML documents. So I think, the
document has to be split in two parts, first which is encoded in ASCII
compatible encoding, should become header and the rest of the document
which contains the text (encoded in encoding specified in the header

Am I correct or not ??

And what about this issue of HTML priority, is that priority order wrong ?

Ashish Shukla
Ashish Shukla "Wah Java !!"
आशीष शुक्ल>

  ,= ,-_-. =.
 ((_/)o o(\_))
  `-'(. .)`-'

My blah, blah, blah at http://wahjava.blogspot.com/
My webpages at http://www.geocities.com/wah_java_dotnet/

My GPG Fingerprint: BBA9 AD7D BA71 61EB BE46 8CF5 E44A C663 A03F 4261

My GPG keys at
Supercomputers are for people too rich and too stupid to design
efficient algorithms -- Steven Skiena, Department of Computer Science,
SUNY Stony Brook.
Received on Saturday, 3 June 2006 16:33:06 UTC

This archive was generated by hypermail 2.3.1 : Wednesday, 7 January 2015 15:06:13 UTC