Hi currently Names are UTF-8, IMHO we should limit them to [a-zA-Z0-9] at least or maybe just [a-z] furthermore its a little tempting to either use the unused bytes for common syllables or store things in 5-6bit per char or does that syllable table need to be extendible but not storeable too? in which case iam obviously not agreeing comments? -- Michael
On Sun, Feb 19, 2006 at 10:47:03AM +0100, Michael Niedermayer wrote:
Hi
currently Names are UTF-8, IMHO we should limit them to [a-zA-Z0-9] at least or maybe just [a-z] furthermore its a little tempting to either use the unused bytes for common syllables or store things in 5-6bit per char or does that syllable table need to be extendible but not storeable too? in which case iam obviously not agreeing
You mean, names of fields in info packets?.. 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... _maybe_ limiting types of fields, but i'm not sure that's a good idea either. - ods15
Hi On Sun, Feb 19, 2006 at 02:13:45PM +0200, Oded Shimon wrote:
On Sun, Feb 19, 2006 at 10:47:03AM +0100, Michael Niedermayer wrote:
Hi
currently Names are UTF-8, IMHO we should limit them to [a-zA-Z0-9] at least or maybe just [a-z] furthermore its a little tempting to either use the unused bytes for common syllables or store things in 5-6bit per char or does that syllable table need to be extendible but not storeable too? in which case iam obviously not agreeing
You mean, names of fields in info packets?..
yes
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 values should be UTF-8 where appropriate and ASCII where not (Author,Title, ... should be UTF-8 while Language and Disposition just need ASCII) but i dont have a strong oppionion on these, making all UTF-8 is fine for me too [...] -- Michael
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
Hi On Sun, Feb 19, 2006 at 01:21:01PM -0500, Rich Felker wrote:
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
well, the problem is "X-cartoonist" vs "X-mangaka in kanji" for example, even if i cant read the value (name of the artist) i would like to know what the field does contain, not to mention the issue of what name english cartoons would then use [...] -- Michael
On Sun, Feb 19, 2006 at 07:31:03PM +0100, Michael Niedermayer wrote:
Hi
On Sun, Feb 19, 2006 at 01:21:01PM -0500, Rich Felker wrote:
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
well, the problem is "X-cartoonist" vs "X-mangaka in kanji" for example, even if i cant read the value (name of the artist) i would like to know what the field does contain, not to mention the issue of what name english cartoons would then use
Why require everyone to use english? I'm very against this. It's imperialist and unnecessary. If you really care you can copy the string into babelfish or whatever.. Rich
Hi On Sun, Feb 19, 2006 at 02:11:08PM -0500, Rich Felker wrote:
On Sun, Feb 19, 2006 at 07:31:03PM +0100, Michael Niedermayer wrote:
Hi
On Sun, Feb 19, 2006 at 01:21:01PM -0500, Rich Felker wrote:
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
well, the problem is "X-cartoonist" vs "X-mangaka in kanji" for example, even if i cant read the value (name of the artist) i would like to know what the field does contain, not to mention the issue of what name english cartoons would then use
Why require everyone to use english? I'm very against this. It's imperialist and unnecessary. If you really care you can copy the string into babelfish or whatever..
iam tempted to awnser in german ;) what about: names of info packet fields SHOULD be english words instead of some other language if a word with th same meaning exists in english [...] -- Michael
On Sun, Feb 19, 2006 at 09:55:38PM +0100, Michael Niedermayer wrote:
Hi
On Sun, Feb 19, 2006 at 02:11:08PM -0500, Rich Felker wrote:
On Sun, Feb 19, 2006 at 07:31:03PM +0100, Michael Niedermayer wrote:
Hi
On Sun, Feb 19, 2006 at 01:21:01PM -0500, Rich Felker wrote:
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
well, the problem is "X-cartoonist" vs "X-mangaka in kanji" for example, even if i cant read the value (name of the artist) i would like to know what the field does contain, not to mention the issue of what name english cartoons would then use
Why require everyone to use english? I'm very against this. It's imperialist and unnecessary. If you really care you can copy the string into babelfish or whatever..
iam tempted to awnser in german ;)
:)))
what about: names of info packet fields SHOULD be english words instead of some other language if a word with th same meaning exists in english
This is reasonable. Rich
On Sun, Feb 19, 2006 at 04:28:37PM -0500, Rich Felker wrote:
On Sun, Feb 19, 2006 at 09:55:38PM +0100, Michael Niedermayer wrote:
what about: names of info packet fields SHOULD be english words instead of some other language if a word with th same meaning exists in english
This is reasonable.
Committed - ods15
participants (3)
-
Michael Niedermayer -
Oded Shimon -
Rich Felker