Forum .LRN Q&A: Re: The .LRN UI is ready for translation

Collapse
Posted by Peter Marklund on
Thanks for all the interest in translation - I'm overwhelmed! 😊 I've setup translate.dotlrn.collaboraid.net now and everybody that was registered can now start translating. Here is your kick-start guide:

1) Visit /acs-lang and choose the locale that you are translating to. If the locale is not present you need to visit /acs-lang/admin and create the locale (see below).
2) Visit /acs-lang/admin and activate translator mode
3) Visit dotlrn and start translating
4) Alternative approach to translation is to visit /acs-lang/admin and translate messages in bulk.

I've configured the server to return UTF8. Currently, only the following locales are in the system

Danish
French
German
Japanes
Spanish

New locales can be created at /acs-lang/admin. Let me know if you have problems with this. Most importantly - make sure you get the right ISO 639 two letter language code and the right ISO 3166 country code for the locale. Here are codes that I found via Google:

http://ftp.ics.uci.edu/pub/ietf/http/related/iso639.txt
http://userpage.chemie.fu-berlin.de/diverse/doc/ISO_3166.html

Currently myself, Carl Robert Blesius and Caroline are site-wide admins on the server. Note for site-wide admins: translators should be added as professors so that they have admin privilege on the acs-lang package.

I hacked togehter a feature that makes it possible to see previous translations (a very light-weight version history if you will). This is useful if you want to recover an old translation.

Thanks Lars for helping me get UTF8 to work on the server. In case someone is interested - here is what I have in the config file:

ns_param  OutputCharset utf-8
ns_param  HackContentType true
ns_param  DefaultCharset utf-8