list4xt : Mailing list for the XT users community.

[list4xt] Re: Hacking XT to work with non-unicode.

User: Website

New Message
• Reply
• Next message: Eric van der Vlist: "[list4xt] Changes of direction 4xt"
• Previous message: Mike Brown: "[list4xt] Re: Hacking XT to work with non-unicode."
• Maybe reply: Paul T: "[list4xt] Re: Hacking XT to work with non-unicode."
• Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

 
> If you are not declaring the encoding, UTF-8 will usually be assumed, and
> the document is then subjected to the requirements of UTF-8. You will
> likely get "character not allowed" from XP when it encounters a byte
> sequence that is not allowed in UTF-8. If the bytes happen to form legal
> UTF-8 sequences, then the document will be parsed but the data will be
> 'corrupted'. This is not a flaw in XP.

Many thanks for your perfect explanation, it explains everything.

It is 'flaw' in UTF-8 then, because I'm not getting "character not allowed".

I was not expecting any garbage in this world to be valid UTF-8 ;-)

Rgds.Paul.

---------------------------------
Do You Yahoo!?
Kick off your party with Yahoo! Invites.

--
Mailing list for the XT users community.     (http://ccascollect.com)
(mailto:list4xt-request@4xt.org?Subject=unsubscribe to unsubscribe)

• Next message: Eric van der Vlist: "[list4xt] Changes of direction 4xt"
• Previous message: Mike Brown: "[list4xt] Re: Hacking XT to work with non-unicode."
• Maybe reply: Paul T: "[list4xt] Re: Hacking XT to work with non-unicode."
• Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]