Re: I18N / UTF-8 versus US-ASCII
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....
PURCHASE STYLUS STUDIO ONLINE TODAY!
Purchasing Stylus Studio from our online shop is Easy, Secure and Value Priced!
Download The World's Best XML IDE!
Accelerate XML development with our award-winning XML IDE - Download a free trial today!
Subscribe in XML format