Travis E. Oliphant schrieb:
How to handle unicode data-formats could definitely be improved.
As before, I'm doubtful what the actual needs are. For example, is it desired to support generation of ID3v2 tags with such a data format? The tag is specified here:
In ID3v1, text fields have a specified width, and are supposed to be encoded in Latin-1, and padded with zero bytes.
In ID3v2, text fields start with an encoding declaration (say, \x03 for UTF-8), then followed with a null-terminated sequence of UTF-8 bytes.
Is it the intent of this PEP to support such data structures, and allow the user to fill in a Unicode object, and then the processing is automatic? (i.e. in ID3v1, the string gets automatically Latin-1-encoded and zero-padded, in ID3v2, it gets automatically UTF-8 encoded, and null-terminated)
If that is not to be supported, what are the use cases?