RE: Unicode string handling

"Simon C" <[email protected]>
Newsgroups gmane.comp.mobile.bitpim.devel
Message-ID <002501c65ece$5b8fc320$0201a8c0@HOME>
> The stated problem was that we allow multiple types for 
> terminators including integers and strings.  We should only 
> allow one type with very well defined semantics.  I don't 
> care if it is strings, integers or sequence of integers.  It 
> should just be consistent.  The secondary point is that the 
> terminator is not passed to the codecs so it doesn't matter 
> if Python's codecs leave particular codepoints in or out.

Meanings were garbled in e-mail. We are in violent agreement :-)
As it stands in SVN the new code uses integers only for terminators, and
does not pass the terminator to python's codecs.

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.