>>>>> "Martin" == Martin v Löwis <[EMAIL PROTECTED]> writes:
Martin> Please do take a look. It is the only way: If you were to
Martin> embed base64 *bytes* into character data content of an XML
Martin> element, the resulting XML file might not be well-formed
Martin> anymore (if the encoding of the XML file is not an ASCII
Martin> superencoding).
Excuse me, I've been doing category theory recently. By "embedding" I
mean a map from an intermediate object which is a stream of bytes to
the corresponding stream of characters. In the case of UTF-16-coded
characters, this would necessarily imply a representation change, as
you say.
What I advocate for Python is to require that the standard base64
codec be defined only on bytes, and always produce bytes. Any
representation change should be done explicitly. This is surely
conformant with RFC 2045's definition and with RFC 3548.
--
School of Systems and Information Engineering http://turnbull.sk.tsukuba.ac.jp
University of Tsukuba Tennodai 1-1-1 Tsukuba 305-8573 JAPAN
Ask not how you can "do" free software business;
ask what your business can "do for" free software.
_______________________________________________
Python-Dev mailing list
Python-Dev@python.org
http://mail.python.org/mailman/listinfo/python-dev
Unsubscribe:
http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
