Date: prev next · Thread: first prev next last
2010 Archives by date, by thread · List index


Hi,
I've reordered the table at http://wiki.documentfoundation.org/Language_Teams, it's now sorted alphabetically by language name by default. While doing that, I've also fixed a few language codes that didn't match the actual ones or used an unusual (for us) form, e.g. oc_FR -> oc-FR, bg-BG -> bg, ca-xv -> ca-XV.

I also fixed a few (non-working) links to wiki pages to use language codes systematically (except Laotian, which already had a page at http://wiki.documentfoundation.org/Lo-LA/Main_Page).

After doing that, I've also noticed that there's an updated instruction about using different languages in wiki at http://wiki.documentfoundation.org/Multilingual_Wiki. Among other things, it suggests that the top-level locale pages should be called http://wiki.documentfoundation.org/LOCALE instead of http://wiki.documentfoundation.org/LOCALE/Main_Page. I suggest all teams to actually follow this advice and update their content/links appropriately.

Also, I'd like to suggest that Lao localizers change the langauge code they use for their wiki page, to be consistent with the language code used elsewhere (http://wiki.documentfoundation.org/LO).

Any comments?

Regards,
Rimas


--
Unsubscribe instructions: E-mail to l10n+help@libreoffice.org
List archive: http://www.libreoffice.org/lists/l10n/
*** All posts to this list are publicly archived for eternity ***

Context


Privacy Policy | Impressum (Legal Info) | Copyright information: Unless otherwise specified, all text and images on this website are licensed under the Creative Commons Attribution-Share Alike 3.0 License. This does not include the source code of LibreOffice, which is licensed under the Mozilla Public License (MPLv2). "LibreOffice" and "The Document Foundation" are registered trademarks of their corresponding registered owners or are in actual use as trademarks in one or more countries. Their respective logos and icons are also subject to international copyright laws. Use thereof is explained in our trademark policy.