[EMAIL PROTECTED] wrote: >> I would like to see it correct, unlike the current UTF-16 codec. Perhaps >> whoever contributes an UTF-32 codec could also deal with the defects of >> the UTF-16 codec. >> > Now this is interesting, as I hoped to base my code on UTF-16 (and > perhaps UTF-8 for combining surrogates)... Can you elaborate?
The codec doesn't do line-oriented input correctly (i.e. readline); it raises NotImplementedError. Regards, Martin -- http://mail.python.org/mailman/listinfo/python-list
