Re: Bytes, character encodings and characters

Shadi wrote:
>>the reader/processor may need to know that the 
>>textContent was originally UTF-16 in order to decode the 
>>"UTF-16 in ASCII" and reassemble the original content (for 
>>example to display it to the end-user). Or am I overseeing 
>>how you want to translate UTF-16 characters into ASCII ones 
>>without going into the byte-level?

Carlos Iglesias wrote:
> Now I see your point Shadi, and I think you're right.

I don't. When you have transformed the resource bytes into characters 
using UTF-16, you can create an EARL report and store it using US-ASCII 
by writing character references for characters above U007F. A reader can 
then again transform the bytes into characters using US-ASCII. No 
problem. However US-ASCII is not the first choice when it comes to 
internationalization :-)
-- 
Johannes Koch - Competence Center BIKA
Fraunhofer Institute for Applied Information Technology (FIT.LIFE)
Schloss Birlinghoven, D-53757 Sankt Augustin, Germany
Phone: +49-2241-142628

Received on Tuesday, 9 May 2006 21:43:28 UTC