Wiki
EGroupware Wiki
Translation manager and Team

Overview

EGroupWare has a target of being available in the most possible number of languages, so if you find that you want to help on this task, you'll find in this document the necessary info and steps to do it.

What is the code for my language?

Egroupware lang codes try to fit to the ISO standard language codes. The lang code format in egw is the two letter code from the ISO 639 code list, and for languages with different "flavours" depending on a specific country, append a hypen followed by the two letter ISO code for the specific country from the ISO country codes list. The resulting code is all lowercase. If you find an outdate or something not fitting, please let us know.

Knowing the status of a translation

For getting a quick idea of the status of the translation of EGroupWare, you can take a look at the Languages page. At the time of this writing, that page covers the progress of the stable branch (1.2.x), not including some new app and maybe the evolution of some app is different in the stable (main) branch that in the upcoming new versions in the development (trunk) branch, so if you don't even see your language listed in the main branch, there might be extra work in the trunk branch.

What happens with RTL (right to left) languages?

At the time of this writing, the right to left support is not yet integrated into eGroupWare. We think it needs to be done in the following steps:

- Translation of the language can be done as usual with the translation tools (we think to have already seen some starts with arabic language)
- The charset, can be set as usual via the charset phrase in the phpgwapi lang-file
- rtl versus ltr header should be triggered by a similar "translation" in the phpgwapi langfile, eg. "rtl_ltr_direction" as "rtl", if needed
- The other stuff needs to be an own template set for rtl languages. In a template set, you can change the location of the menus. That template set would be usable for all rtl languages, not only arabic. It's recommended to base it on the standard idots template.

If you think you have the knowledge and experience to do that changes in the code, let us know. We dont think it makes sense one of us "ltr people" do it.

We can support you with the necesary information and that the project will welcome a patch to implement rtl support.

Tools

The preferred way is to use the Translation Tools, that you'll find in your own installation, so you should get used to it. Make sure you have it installed, enabled for your user and that the webserver can write in the directory where the lang files reside. About the lang files, egroupware 1.4 is the last version where the naming for the lang files was in the form phpgw_ab[-cd].lang, and the charset encoding for the lang files was specified in the phrase "charset" in phpgwapi app. But this is currently deprecated, because from egroupware 1.5 on, the naming for the language files is egw_ab[-cd].lang and the encoding is utf-8, regardless what the "charset" phrase says. Then, you can provide every egw_ab[-cd].lang file you'll find under the setup directory in every app (or in the "lang" directory in the case of the setup app) so it is added to the existing ones.

eGroupWare Manual

The translation of the eGroupWare manual is a different process. More details here.

How can I contribute translating?

Since June 2006, there's a mailing list for egroupware translators. You have to suscribe to this list (non-members mail is not allowed!!) as a prerequisite if you want to help and contribute on egroupware translation (it's a low-traffic list). This way, it's easier to have and coordinate translation teams, along with any common or specific issues about the translation process. Unfortunately, having a team is not always possible and you might be alone, or just don't know what the situation is, so in any case, please mail after joining, introduce yourself and just expose your situation. You'll get contacted and be told how to manage best in your case. Please DO NOT mail attachments with your work to any of the lists.

For starting working with the translation tools (if you aren't very used to it), you can, at your local installation, try updating (better completing) the translation of phpgwapi and setup for your language with the updated trunk file, and make sure your changes work.

Additionally, these modifications should mean an improvement of the existing translations, so in this case you should send one or both files as a patch to the patch manager at egroupware.org and assign it to the Translations category. You should reference this patch when you introduce yourself in the translation list, as starting point for your work, and so you prove you have successfully dealt with translation tools.

It can happen that you have some extra translations of some other apps. In general, the best way to get your translation uploaded is:

- Make a zip from your egroupware root directory (where header.inc.php file resides). This can be done with a GUI utility or using the zip utility in Linux system like this:
zip -r egw_AB_lang.zip $(find . -name egw_AB.lang)
replacing "AB" with your lang code.
- Create a new patch at the patch manager at egroupware.org, describing the language and the files included in the file(s) you're about the attach. Only in the case you have just one single app file to be attached, you don't need a zip with the directory structure, attaching the file instead. If the attached file is a zip file and the contents are not properly organized (custom filenames, unorganized directory structure), there are many chances that the patch will be rejected.

NOTE: Calendar holidays for specific countries are NOT translations. Use the calendar category at the bug tracker instead.

Current known translators list

There's a list below of the known contributors along with languages for a better understanding. Since the pool is in the way translator-> coordinator, some names could be outdated or not accurate. You can contact directly the current team (if any), and please, CC me (omgs at escomposlinux.org) in any case.

  • Basque (eu)
    • Elema Project - ilarranaga at elema.org
    • Ibon Castilla - estri at euskalnet.net

  • Bulgarian (br)
    • Yasen Pramatarov - turin at fsa-bg.org

  • Catalan (ca)
    • Jordi Esteve - jesteve at zikzakmedia.com
    • Laura Lázaro - lauradevilafranca at gmail.com
    • Carmen Cerdá Torres - carmect at tv3mail.com (old)
    • Xavier Navarro - xavin at users.sourceforge.net (old)

  • Czech (cs)
    • Martin Sustik - martin.sustik at quick.cz
    • Michal Sladek - msladek at brotel.cz
    • Willi Gruber - w.gruber at connectel-cz.com (old)

  • Danish (da)
    • Esben Laursen - hyber at hyber.dk
    • Henrik Bork Steffensen - hbs at rosetechnology.dk
    • Poul Hansen - hector.hansen at gmail.com

  • Dutch (nl)
    • Arjan van Waay - arjan at vanwaay.net

  • English reviewer (en)
    • Miles Lott - milos at groupwhere.org

  • French (fr)
    • Antoine Theytaz - theytaz at users.sourceforge.net
    • Zorg - zorg at probesys.com
    • Dablah - dablah at users.sourceforge.net (old)

  • Galician (gl)
    • Manuel Varela - mvarela at cesga.es

  • German (de)
    • Ralf Becker - RalfBecker at outdoor-training.de (as core developer)
    • Lars Knechke - l.kneschke at metaways.de (as core developer)
    • Cornellius Weiss - egw at von-und-zu-weiss.de (as core developer)
    • Sebastian Ebling - s.ebling at umwelt-campus.de (as reviewer)

  • Greek (el)
    • Alexandros Sigalas - asig at sigalas-wp.gr

  • Hebrew (iw)
    • Dov Zamir - dov at zamirfamily.com

  • Hungarian (hu)
    • Fehér János - feher.janos at mindworks.hu
    • István Pongrácz - istvan.pongracz at osbusiness.hu

  • Italian (it)
    • Leo Amadori - leolovers at users.sourceforge.net

  • Japanese (ja)
    • Moritoshi Osiro - m-ooshiro at 10art-ni.co.jp

  • Korean (ko)
    • Futurizer - futurizer at blueweb.co.kr

  • Latvian (lv)
    • Atis Rudzitis - latvietis at users.sourceforge.net

  • Lithuanian(lt)
    • Aurimas Fišeras - aurimas at gmail.com

  • Norwegian (no)
    • Harald Finnas - finnas at lantrix.no
    • Knut Carlsen - knut.carlsen at indusoft.no

  • Persian (fa)
    • Alireza Eliaderani - eliaderani at dpilinux.com
    • Daade Pardazi Iran / open source department - dpilinux.com
    • Davood Firouzian

  • Polish (pl)
    • Michael Bielicki - Michael.Bielicki at taansoftworks.com

  • Portuguese of Brazil (pt-br)
    • Frank Alcantara - Frank at thyamad.com
    • Orlando Gentil - gentil at nod.com.br
    • Renato Cintra - renato at aats.com.br
    • Guilherme M Furlan - guilherme at mehospeda.com

  • Portuguese of Portugal (pt-pt)
    • Rita Farinha - rita.farinha at intraneia.com

  • Russian (ru)
    • Alexander Krasnov - ank at reklamalab.ru

  • Slovak (sk)
    • Peter Tuharsky - tuharsky at misbb.sk

  • Slovenian (sl)
    • Tomaz Savodnik - tomaz at 386tele.com
    • Robert Ludvik - r at aufbix.org

  • Spanish of Spain (es-es)
    • Oscar Manuel Gómez Senovilla - omgs at escomposlinux.org

  • Swedish (sv)
    • Johan Kragsterman - johan.kragsterman at capvert.se
    • Marko Vourinen - egw at aarnet.se
    • Martin Kurtsson - martin at kurtsson.com
    • Mats Fredriksson - mfredriksson at gmail.com

  • Traditional Chinese (zh-tw)
    • Finjon Kiang - kiange at gmail.com

  • Simplified Chinese (zh)
    • Zhang Weiwu - zhangweiwu at realss.com

  • Turkish (tr)
    • Naval Map - bilgi at navalmap.com
    • Alaattin Kahramanlar - alaattin at gmail.com
    • Mahmut Cuneyt Gursan - cgursan at kablonet.com.tr (old)

  • Vietnamese (vi)
    • Nguyen Van Nhat Nam - nhatnamnv at gmail.com

Stylite GmbH


Stylite GmbH - The main developer of EGroupware

EGroupware 2010



Login

Login Name

Password

remember me

Don't have an account?
Register for one now.

Sourceforge.net


SourceForge.net Logo