Thanks for your reply, Louis. :) On 25/08/2007, at 5:21 AM, Louis Suarez-Potts wrote:
On 2007-08-18, at 07:38 , Clytie Siddall wrote:Sorry if I'm catching up with these a bit late. :( On 14/03/2007, at 11:03 PM, G. Roderick Singleton wrote:The dropdown at http://documentation.openoffice.org/ displays nativelanguages in the correct language. e.g. German is correctly listed as Deutsch, French as Français. We have tried to do this for each language listed where the NLCs have provided the correct spelling. I agree thathaving the website automatically recognize native languages would benice but the following thread seems to indicate that doing this would beproblematic:http://native-lang.openoffice.org/servlets/BrowseList? list=dev&by=thread&from=1610035The drop-down list on the docs homepage only lists _some_ languages as they are written in their own language. For example, Vietnamese is only shown as "Vietnamese", not "Việt".How do I correct this, please?"Correct' is not the term I would use ;-)
Well, I would, because the list is not consistent. Either we use the English names, or the native-language names, but not a mixture of both, please. And a mixture of both is what we currently have.
The problem is this: if we do it for one, we really have to do it for all. I'd love to be able to do that, and could ask every one of the members to send in exactly what is required. If you want to help get the NLC projects to contribute the appropriate graphics or text (we could use the wiki for this, then cut and paste), be my guest.Note: The last time I did this, btw, I abandoned it after a while for two reasons: inconsistency was confusing (Finnish vs. Suomi, for example: different location on alphabet string) and it took a lot longer to do; also, where does one stop? With the NLC or do we go on to include the download pages? I'd love to have *all* the pages sensitive to a user's linguistic configuration--but it's not so trivial.
It's not a trivial fix, but I remember discussing content-sensitive [1] pages on at least one of the OpenOffice.org lists some time ago. It's a very worthwhile goal. Even if we have to do it one page at a time, each page is a marked improvement in our accessibility.
The OpenOffice.org User Survey (when I translated it recently by banging my head against it enough times) also included a mixed (and very long) list of English and native-language language names. I spent some time in Wikipedia [2] and converted a lot of the language names to native-language. I can supply that list if it will be useful. I'll put it up on a wiki page, and we can add to it.
[Later]I decided to compile a more comprehensive list, combining the languages supported by OpenOffice.org with those actively published in Wikipedia, to represent our international users (a list of _all_ world languages is extremely long). It took all afternoon, but I've managed to track down most of them. I hope people will add to and/or correct the table. I've linked the page from the main NLC page for now.
http://wiki.services.openoffice.org/wiki/NLC:LanguageListOnce the list has been revised, I will also publish it in the Translate Wiki, which collects central resources for translators. It would also be useful, later on, to have cut-and-paste HTML/PHP code containing the language bars or language drop-down menus, to help people construct content-sensitive webpages.
____Revised alphabetical order to display the native-language names is a secondary priority. Being able to recognize your own language at all in a list is a huge help: having it in correct alphabetical order is just icing on the cake. Ordering this type of list by language code would work better, in any case, IMHO.
Imagine looking for the Chinese characters for "English" in a long list of Chinese expressions, even if you had tried to memorize those characters. People won't jump through hoops like this to access our information.
Picking the word "English" out of that list would be so much easier.I hope the list and the wiki page will be useful. I didn't intend to spend so much time on it, but I think it will be worth it in the end. :)
from Clytie (vi-VN, Vietnamese free-software translation team / nhóm Việt hóa phần mềm tự do)
http://groups-beta.google.com/group/vi-VN [1] http://www.w3.org/QA/2006/02/content_negotiation.html[2] e.g. http://en.wikipedia.org/wiki/ Wikipedia:Multilingual_coordination
PGP.sig
Description: This is a digitally signed message part
