[vorbis] TAG Standard - ENSEMBLE/PERFORMER tags

[Victoria E. Lease]

[Dan Hollis]
> In fact what I expect will happen is that everyone is simply going to 
> ignore the requirement for UTF-8 and they are just going to use their 
> local encodings instead. It *will* end up being a real mess. This has 
> happened numerous times with other standards where westerners tried to 
> force UTF-8. This has already happened with ID3. Don't make the same 
> mistake.

Oggenc uses iconv to convert local encodings to UTF-8. If other
encoders follow suit, then this mess will probably not happen.

Admittedly, I was a little dismayed to see that iso-8859-1 and
iso-8859-2 were the only two local encodings supported. It wasn't
too difficult for me to get euc-jp in there, though... but that
is certainly not a task which all users are capable of doing. I
should probably offer up some patches that squeeze more non-euro
encodings in...

> You can avoid this by explicitly allowing UTF-8 *OR* RFC2047.

MIME-encoded 8-bit text is not human readable, which is one of
the requirements for tag data. I don't expect this requirement to
change, but I am hardly authoritative. Even the mess of using
arbitrary unspecified encoding methods is more human-readable
than MIME-encoded versions of those encodings, on most systems.
(None of my terminals interpret MIME text, but rxvt is pretty
good with JIS0208, SJIS, and EUC. It would be nice if it
supported UTF8, but that is not our concern, and xterm handles UTF8
pretty well over here...)

Why not funnel this energy into a bit of work on metadata stream
stuff?

-- 
   Victoria E. Lease <vlease at floofy-skirts.org>
C66F 5745 AE21 B21F 5326  FA12 DBC2 9245 9475 3F70

--- >8 ----
List archives:  http://www.xiph.org/archives/
Ogg project homepage: http://www.xiph.org/ogg/
To unsubscribe from this list, send a message to 'vorbis-request at xiph.org'
containing only the word 'unsubscribe' in the body.  No subject is needed.
Unsubscribe messages sent to the list will be ignored/filtered.