Re: I18N / UTF-8 versus US-ASCII

We are using US-ASCII everywhere for several years now without any
problem (and because we had many problems with UTF-8).

We use OmniMark (WinNT/2000 and AIX), MSXML, Xalan/Xerces (C/AIX and
Java/WinNT), Adept (WinNT), Epic(Win2000/XP) in our document processing
chain.

We publish our documents in French, Spanish, German, Japanese, Chinese
and Russian languages (sometimes mixing any of these languages).

>>> andrew.j.welch@xxxxxxxxx 4/04/06 12:47:03 PM >>>
On 4/4/06, Sangal, Amit (STSD) <amit.sangal@xxxxxx> wrote:
> I have less knowledge in this area.
>
> In my case also, XML (containing Korean character) need to travel
from one machine(running in Korean/ko_KR locale) to another
machine(running in english/en_US local) inside SOAP envelope.
>
> Is there any known disadvantage/limitation of using US-ASCII output
encoding?

The only disadvantage I'm aware of is that anyone reading the file is
presented with the numeric character references instead of the
characters themselves - this is not normally a problem as the only
people who ever examine the XML itself are developers, users only see
the parsed content (at which point all the references have been
resolved).

It would be interesting to know if anyone who was using US-ASCII
output had to switch to a broader encoding because of some issue....



------
World Intellectual Property Organization Disclaimer:

This electronic message may contain privileged, confidential and
copyright protected information. If you have received this e-mail
by mistake, please immediately notify the sender and delete this
e-mail and all its attachments. Please ensure all e-mail attachments
are scanned for viruses prior to opening or using.