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

Re: The myth of the clean slate (was Re: a discussion proposal for addre

  • To: Rick Jelliffe <ricko@a...>
  • Subject: Re: The myth of the clean slate (was Re: a discussion proposal for addressing 'the character entity problem')
  • From: John Cowan <cowan@m...>
  • Date: Sun, 19 Oct 2003 13:27:19 -0400
  • Cc: xml-dev@l...
  • In-reply-to: <3F92569A.10407@a...>
  • References: <3F903A5F.3080704@t...> <OF10F1AB08.8E0B0A3F-ON85256DC0.000D233D@l...> <OF10F1AB08.8E0B0A3F-ON85256DC0.000D233D@l...> <4.2.0.58.J.20031016213904.05baedf0@localhost> <3F903A5F.3080704@t...> <4.2.0.58.J.20031018152242.0272fd60@localhost> <3F91B715.7040104@t...> <3F92569A.10407@a...>
  • User-agent: Mutt/1.3.28i

clean slate hack
Rick Jelliffe scripsit:

>  1) There is no need to tie the naming proposal to a specific encoding 
> (UTF-8), and good reason (i.e. real-life usefulness) to broaded it.

I think that UTF-8 is sufficient, though I wouldn't object to a parallel
proposal for UTF-16+names.  There are people for whom UTF-16 makes much
more sense than UTF-8, and there is no reason why they shouldn't have
access to names as well.

>  2) There is no need to tie the naming proposal to specific mime types
> (*/xml*), and good reason (i.e. other text formats need convenient 
> characters just as much as XML) to broaden it.

It isn't in any way tied to XML, though it does borrow a bit of XML
syntax (and why not?).

>  3) There is no need to insist on particular delimiters, and if
> the need is recognized as being larger than for XML, good reason
> not to.

Why so?  Since the delimiters are filtered out, and there is a very
simple way to write an & character when you need to, what does it
matter what the upper-level syntax is?  This is something about XText
I never understood.

>  4) It is a mistake to introduce a superencoded reference system
> in which simple transcoding a file from UTF-8 to something else would
> render the file non-standard. When I open a UTF-8+Names file, edit
> it (as Unicode or maybe ASCII) in my editor, then save it as
> UTF-16, I have no way of labelling what encoding the file it in.

Okay, so you need UTF-16+names for that.

> The infrastructure is not set up to handle this kind of hack.

Frankly, the infrastructure isn't set up to handle character encodings
at all.

-- 
John Cowan   jcowan@r...   http://www.reutershealth.com
    "Mr. Lane, if you ever wish anything that I can do, all you will have
        to do will be to send me a telegram asking and it will be done."
    "Mr. Hearst, if you ever get a telegram from me asking you to do
        anything, you can put the telegram down as a forgery."

PURCHASE STYLUS STUDIO ONLINE TODAY!

Purchasing Stylus Studio from our online shop is Easy, Secure and Value Priced!

Buy Stylus Studio Now

Download The World's Best XML IDE!

Accelerate XML development with our award-winning XML IDE - Download a free trial today!

Don't miss another message! Subscribe to this list today.
Email
First Name
Last Name
Company
Subscribe in XML format
RSS 2.0
Atom 0.3
 

Stylus Studio has published XML-DEV in RSS and ATOM formats, enabling users to easily subcribe to the list from their preferred news reader application.


Stylus Studio Sponsored Links are added links designed to provide related and additional information to the visitors of this website. they were not included by the author in the initial post. To view the content without the Sponsor Links please click here.

Site Map | Privacy Policy | Terms of Use | Trademarks
Free Stylus Studio XML Training:
W3C Member
Stylus Studio® and DataDirect XQuery ™are products from DataDirect Technologies, is a registered trademark of Progress Software Corporation, in the U.S. and other countries. © 2004-2013 All Rights Reserved.