From: I. <air...@us...> - 2005-04-13 18:07:09
|
Ok, so finally I added native names to the langlist file (all I found), and= =20 sorted languages by ENGLISH name, as I find it impossible to sort some nati= ve=20 names :) Please translators, check them. Greets. El S=E1bado, 2 de Abril de 2005 20:37, Harry Vennik escribi=F3: > While thinking it over once again I realize that I was mainly thinking of > the language list as it appears on the translations page on the amsn > website, forgetting the language chooser in amsn itself. Of course, both > are based on the same file, but preferred order does not necessarily be t= he > same. > > From a user point of view, yes, I think you may be right. Let's be as > friendly as possible and let him choose for Espa=F1ol, Italiano or > Nederlands, rather than Dutch, Italian or Spanish. The native name will be > easier to recognize. > > From the developer point of view, English names make more sense. > Communication is mainly in English, so let's stick to that. Besides, some > time ago (don't know when exactly) there also was a langlist discussion > like this one. We chose to use English names that time. We do have all > English names now, but we are missing lots of native names. Getting all > native names in the list would certainly be a requirement if we want to > sort languages by native names. Having mixed 'native (english)' and > 'english' would really be too ugly. > > And finally: do we really want to have double naming everywhere? Do we ne= ed > to? I'd say 'no' to both. Having a separate <nativename> element is not > difficult, and I don't think it will break a thing, since the currently > used xml elements keep their meaning. It's not really changing the file > format, it's just extending. It would be the most clean way to do it, and > at the same time it enables for using english names on the website and > native names in the language chooser in aMSN, for example. (And such a > thing requires only a very little change of code, I guess). > > Okay, I gave some arguments, it's up to you... > > If you are going to complete the list with all native names, one way or t= he > other, the following might help you a lot: > http://www.omniglot.com/language/names.htm > > Greetings, > > Harry > > Op zaterdag 2 april 2005 18:22, schreef =C1lvaro J. Iradier: > > Ok, I agree. I thought Dutch was native name and Nederlands the english > > name, sorry. I just intended to have: > > > > Native name (english name) > > > > where possible > > > > instead of changing the langlist format, why not just: > > > > Native name (english name) > > or > > English name (native name) > > > > for languages in language list? That should be very easy. As langlist is > > utf-8 encoded you can even have the native chinese name in there, for > > example. > > > > The question is: > > > > native(english) > > or > > english(native) > > > > I think first option is better, because the user might now the native > > name but not the english name. Why do you think english(native) is > > better? > > > > Greets. > > ------------------------------------------------------- > SF email is sponsored by - The IT Product Guide > Read honest & candid reviews on hundreds of IT Products from real users. > Discover which products truly live up to the hype. Start reading now. > http://ads.osdn.com/?ad_ide95&alloc_id=14396&op=3DClick > _______________________________________________ > Amsn-lang mailing list > Ams...@li... > https://lists.sourceforge.net/lists/listinfo/amsn-lang =2D-=20 (=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D) Alvaro J. Iradier Muro air...@us... |