 |
 |
 |
I don't understand. Can't encoding="utf-8" or "utf-16" on the XML
declaration do the job? - i.e. represent every possible "code-point"?
Of course, utf-8 would be better (more efficient space-wise) if the text
is predominantly written in the Latin *alphabet*, with only occasional
excursions into Greek or Cyrillic or whatever.
William J. Kammerer
----- Original Message -----
From: "tedd" <tedd@s...>
To: <xml-dev@l...>
Sent: Saturday, 05 March, 2005 01:17 PM
Subject: Re: [xml-dev] fuzzy end of this lolly-pop OR Why Latin Rocks
William:
>For the most part we're just talking alphabets here.
No, we're talking about code-points -- there are no alphabets in
Internet land. All url's, which is what I'm discussing, are a
collection of code-points.
Now, to draw this thread back to on-topic, I know how code-points are
used in url's, html, and such, but I would like to see how xml
incorporates/uses Unicode code-points. Anyone? Please enlighten me.
Thanks.
tedd
--
--------------------------------------------------------------------------------
http://sperling.com/
|
 | 

|  |
These Archives are provided for informational purposes only and have been generated directly from the Altova mailing list archive system and are comprised of the lists set forth on www.altova.com/list/index.html. Therefore, Altova does not warrant or guarantee the accuracy, reliability, completeness, usefulness, non-infringement of intellectual property rights, or quality of any content on the Altova Mailing List Archive(s), regardless of who originates that content. You expressly understand and agree that you bear all risks associated with using or relying on that content. Altova will not be liable or responsible in any way for any content posted including, but not limited to, any errors or omissions in content, or for any losses or damage of any kind incurred as a result of the use of or reliance on any content. This disclaimer and limitation on liability is in addition to the disclaimers and limitations contained in the Website Terms of Use and elsewhere on the site.
|  |
| |
 |
 |
 |