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

Re: RE: There is a serious amount of character encodingconvers

• From: Chris Maloney <voldrani@gmail.com>
• To: Michael Kay <mike@saxonica.com>
• Date: Sat, 29 Dec 2012 00:22:06 -0500

On Fri, Dec 28, 2012 at 3:38 PM, Michael Kay <mike@saxonica.com> wrote:
>
> On 28/12/2012 19:45, Chris Maloney wrote:
>>
>> Roger,
>>
>> Here is a classic post from XML.com that is right in line with the
>> topic of character encodings that you have been posting about
>> recently, titled "XML on the web has failed":
>> http://www.xml.com/pub/a/2004/07/21/dive.html
>>
>>
> Well, it's a very sensible article spoilt by a very silly title.

I agree with this.  When I first read it, several years ago, it seemed
to me that the problems he was describing were disastrous and
implacable.  Now, not so much.

I guess the main problems he points out are solved just by making sure
your server always uses the "charset" parameter with the HTTP
content-type header.  The other problems, such as static caching of
news feeds, would/should be solved by using proper transcoders within
those caching systems.

It makes interesting reading, though, insofar as it serves to
illustrate that the things Roger was marveling about, how all these
encodings are handled seemlessly and invisibly, doesn't just happen by
magic; there's a lot of engineering behind the scenes.


>  What the
> title should be is "XML has failed to solve the problem of character
> miscoding", and that of course is true, and is inevitably true, because so
> long as we have programs exchanging "strings" with each other (whether by
> procedure calls, on the wire, or via file storage) without also exchanging
> reliable and secure metadata about the character encoding of those strings,
> character miscoding will continue to be a problem. XML has done its bit to
> solve that problem, and has made a useful contribution (as has HTTP), but
> there's no way XML can solve the problem on its own.
>
> Just consider: can we ban people from using text editors that allow you to
> put encoding="utf-8" in an XML declaration when the file is actually iso
> 8859-1? Until we can, how can we solve the miscoding problem?
>
> Michael Kay
> Saxonica
>
>
> _______________________________________________________________________
>
> XML-DEV is a publicly archived, unmoderated list hosted by OASIS
> to support XML implementation and development. To minimize
> spam in the archives, you must subscribe before posting.
>
> [Un]Subscribe/change address: http://www.oasis-open.org/mlmanage/
> Or unsubscribe: xml-dev-unsubscribe@lists.xml.org
> subscribe: xml-dev-subscribe@lists.xml.org
> List archive: http://lists.xml.org/archives/xml-dev/
> List Guidelines: http://www.oasis-open.org/maillists/guidelines.php
>

• References:
  • There is a serious amount of character encoding conversionsoccurring inside our computers and on the Web
    • From: "Costello, Roger L." <costello@mitre.org>
  • RE: There is a serious amount of character encoding conversionsoccurring inside our computers and on the Web
    • From: David Lee <dlee@calldei.com>
  • RE: There is a serious amount of character encoding conversionsoccurring inside our computers and on the Web
    • From: "Costello, Roger L." <costello@mitre.org>
  • RE: There is a serious amount of character encoding conversionsoccurring inside our computers and on the Web
    • From: David Lee <dlee@calldei.com>
  • Re: RE: There is a serious amount of character encodingconversions occurring inside our computers and on the Web
    • From: Chris Maloney <voldrani@gmail.com>
  • Re: RE: There is a serious amount of character encodingconversions occurring inside our computers and on the Web
    • From: Michael Kay <mike@saxonica.com>