[XML-DEV Mailing List Archive Home] [By Thread] [By Date] [Recent Entries] [Reply To This Message]

Re: more fixed lists (was UTF-8+names)

• To: xml-dev@l...
• Subject: Re: more fixed lists (was UTF-8+names)
• From: ari@c... (K. Ari Krupnikov)
• Date: 19 Oct 2003 17:24:02 -0700
• In-reply-to: <000901c3965a$7b9c4dd0$42a7c044@aldebaran>
• References: <000901c3965a$7b9c4dd0$42a7c044@aldebaran>
• Sender: ari@f...
• User-agent: Gnus/5.09 (Gnus v5.9.0) Emacs/21.3

"Alessandro Triglia" <sandro@m...> writes:

> I don't see how the lists can be changed in the future, since we are talking
> about an encoding.  Changing the lists would mean that the encoding becomes
> a different encoding, and must have a different name (UTF-8+names-1,
> UTF-8+names-2, etc.).  The last thing we want is interoperability problems
> between different versions of the *same* encoding that decode the same byte
> sequence in different ways.  So any list that is initially specified must be
> carved in stone.

Haven't we been there? Latin-1? Latin-2? 8859-15? The lists were
carved in stone, and the stones kept piling up until Unicode came and
made one level gravel field out of all these stones.

But this is a proposal about writing Unicode in some other (less
capable but more easily typed) character set, so we might as well
explicitly state which encoding it is.

So we can have UTF-8+names-15+MacCyrillic. Can we have
UTF-8+names+UTF-8?

Ari.

-- 
Elections only count as free and trials as fair if you can lose money
betting on the outcome.

• References:
  • RE: more fixed lists (was UTF-8+names)
    • From: "Alessandro Triglia" <sandro@m...>

• Prev by Date: RE: UTF-8+names
• Next by Date: Re: Entity support in XML parsers (was: UTF-8+names)
• Previous by thread: Re: more fixed lists (was UTF-8+names)
• Next by thread: Re: UTF-8+names
• Index(es):
  • Date
  • Thread