On Sun, Feb 19, 2006 at 03:05:09PM +0100, Michael Niedermayer wrote:
i think not limit them, allow the user to have whatever extra weird fields he wants, there's no big disadvantage in allowing full utf-8...
id say require names and types to be ASCII and in english or at least suggest it if possible, otherwise we might end up with X-?????? stuff written in your favorite asian or whatever language
What's wrong with this? A player can just ignore names it can't display, since they obviously won't represent anything meaningful to the user. For types I would generally agree that ascii is sufficient, but I see no harm in allowing any character.
values should be UTF-8 where appropriate and ASCII where not (Author,Title, ... should be UTF-8 while Language and Disposition just need ASCII)
Yes.
but i dont have a strong oppionion on these, making all UTF-8 is fine for me too
IMO it's fine for them to be UTF-8 since UTF-8 is a superset of ASCII. It just happens that no non-ASCII language or disposition values represent meaningful info. In other words, we don't need to make any special rule to make non-ASCII values of language invalid. They're just invalid because language is required to be an ISO 639-2 code, and all ISO 639-2 codes are ASCII. Rich