Should ASF/ID3 implicitly convert UTF-16 to UTF-8

[GoogleCodeExporter]

I ask for comments on whether the ASF class should automatically convert
any UTF-16LE string to UTF-8 strings. The ASF standard specifies all
strings to be in UTF-16LE but this is rather complex to use in practice.

Original issue reported on code.google.com by svollbehr on 9 Apr 2008 at 3:33

[GoogleCodeExporter]

This is a problem also with ID3 tags if encoded with UTF-16. Would be much more
usable if one wouldn't have to check the encoding before printing the tag info.

Original comment by svollbehr on 15 Apr 2008 at 12:16

• Changed title: Should ASF/ID3 implicitly convert UTF-16 to UTF-8
• Changed state: Accepted

[GoogleCodeExporter]

I don't think it matters what you choose to implicitly convert to, but I agree 
that
it should always be the same thing (ie: either convert UTF-8 to UTF-16 or 
UTF-16 to
UTF-8) that way we can always know which is being used. I do agree though that 
UTF-8
would be the better choice.

Original comment by wphil...@gmail.com on 15 Apr 2008 at 5:19

[GoogleCodeExporter]

[deleted comment]

[GoogleCodeExporter]

I will add an encoding option (defaults to utf-8) to both ID3 and ASF classes

Original comment by svollbehr on 15 May 2008 at 6:43

• Changed state: Started

[GoogleCodeExporter]

Original comment by svollbehr on 28 Dec 2008 at 6:49

• Changed state: Verified