RE: Unicode string handling

"Simon C" <[email protected]>
Newsgroups gmane.comp.mobile.bitpim.devel
Message-ID <002001c65ec8$d1a43e70$0201a8c0@HOME>
> The terminator is not part of the string returned and hence 
> isn't supplied to the codec for conversion.  Technically 0x0a 
> is part of Unicode and ISO-8859-1.

What I mean is that if we =define terminators as characters/strings, as I
thought you suggested, instead of integers (like we do now) we will not be
able to support terminators that are not representable as characters.

Simon



-------------------------------------------------------
This SF.Net email is sponsored by xPML, a groundbreaking scripting language
that extends applications into web and mobile media. Attend the live webcast
and join the prime developer group breaking into this new coding territory!
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=110944&bid=241720&dat=121642
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.