Aistriúchán Gaeilge GNU/Linux:
How to Help
The goal of this project is to create a free computing system entirely in the Irish language. So far we've translated Mozilla Firefox (web browser), Mozilla Thunderbird (email handler), KDE (complete desktop system), OpenOffice.org (office suite), and much much more.
In practice, "free" means that you're able to download and use our software for free (i.e. no cost). More importantly, it means that the software is free as in "free speech" or as in "freedom". In other words, you can do whatever you want with the software: view and change the source code, modify our translations to your liking, or even put it on a CD, give it away, or sell it. The only rule is that the existing license be preserved, which guarantees that others share these same freedoms.
This is a powerful approach to developing software for languages with limited resources, like Irish. This is evidenced by the fact that there are free translation projects underway for almost 100 languages, 5 times the number of languages that are available for Microsoft Windows. Even in the rare instances that Microsoft has released products in minority languages, they do so in order to lock computer users into their proprietary solutions. In contrast, free software is "owned" by those who produce it, in this case, by the Irish speaking community.
Séamus Ó Ciardhuáin and I have written an article about the advantages of free software for minority language localization, and which discusses some of the software tools we use for maintaining and verifying the Irish translations. Read it here.
The volunteers who work on this project come from all over the world; some are native Irish speakers and work primarily on translation, while others speak very little Irish at all, and provide other kinds of support instead.
Here are some ways you can help:
- Translate (more information below)
- Proofread existing translations
- Use the software and provide feedback
- Provide technical help (builds, debugging)
- Help maintain the project web pages
- Create graphics, icons, or screenshots for publicity
- Other kinds of publicity (press releases, etc.)
- Spread the word; tell friends about the project!
Getting started with translation
Translating open source software is very easy. Here's how to get started.
- Decide which product(s) you'd like to work on. Mozilla Firefox is complete, and Thunderbird is close also. But substantial work is needed on just about everything else. If you've never used any free software packages and you're not sure, that's OK too; I can direct you to where help is most needed.
- Send me an email (kscanne at gmail dot com). I'm managing the technical aspects of all of the ongoing projects (and do a lot of the translating too).
- Download and install the latest version of poedit. Translations of all free software packages can be stored in a special file format called a PO file. POEdit is a specialized editor that is used to translate PO files.
- Once you have POEdit installed and running, I'll send you a PO file to translate. If you're using a Windows computer, simply save the PO file to your desktop and then double click it; POEdit should start. Each string is shown on a single line, English on the left and the translation on the right. Untranslated strings are highlighted in blue. Click a string you'd like to translate, and then type the translation into the box at the very bottom of the window. When you're done, click the next string and proceed.
- When the file is completed, email it back to me and I'll incorporate it into the finished product. Then I'll send more strings to work on.
Translation: nuts and bolts
Every package has it's own conventions for handling things like variables ("Do you want to delete %s"), keyboard shortcuts, and plural forms ("1 file" vs. "%n files"). Here are some tips:
- Keyboard shortcuts. In OpenOffice.org these are marked by a tilde "~". Most other programs use an ampersand "&". So if the string to be translated is "&File", this is probably a menu item for which Alt+F will display the drop down file menu. In cases like this you should include a corresponding ampersand in your translation ("&Comhad"). If the same shortcut key is available in the Irish word ("&Edit" = "&Eagar", or "&Help" = "Cab&hair"), that is the best choice. Otherwise I usually use the first letter. It is also a good idea not to make an accented character into a shortcut, since this defeats the purpose on keyboards that require multiple keystrokes to enter síntí fada.
- Terminology. The first remark is not to spend too
much time worrying about this. I've written various
tools for checking consistency of terminology in the
different translations so if you call an icon a "dealbh"
vs. "deilbhín" a few times it's not big deal.
Most of the terminology we use is pretty
well nailed down, based on the recommendations of
An Coiste Téarmaíochta,
and also many discussions among the Mozilla translators.
Occasionally we depart from the CT recommendations, but not
very often. Here are a few examples:
- boot -> tosaigh (vs. "bútáil")
- collapse -> laghdaigh (vs. "leacaigh")
- document -> cáipéis (vs. "doiciméad")
- front-end -> comhéadan (vs. "tosach")
- global -> comhchoiteann (vs. "domhanda", unless it's literally global, like GPS)
- keyword -> lorgfhocal (vs. eochairfhocal)
- launch -> tosaigh (vs. lainseáil)
- load -> luchtaigh (vs. lódáil, similarly "upload", "download")
- path -> conair (vs. "cosán")
- popup window -> preabfhuinneog (vs. fuinneog aníos)
- setup -> socrú (vs. "cumraíocht", which we reserve for "configuration")
- wizard -> treoraí (vs. draoi)
- Spelling and grammar. Again, don't worry too much about it, I have tools like my grammar checker for correcting spelling mistakes, lenition errors, etc. automatically.
- Indecipherable strings. Even the most technically savvy translator will run into strings he or she simply doesn't understand. The best rule here is that if you're not sure, ask me or on one of the mailing lists and we can poke around the source code to try and figure out what is intended.
- Ambiguous English. Some English computing terms translate
to different Irish words depending on context; e.g.
- accelerator -> "aicearra" (keyboard) or "luasaire" (graphics)
- base -> "bonn" (base 10) or "bun-" (address, directory)
- directory -> "comhadlann" (file directory) or "eolaire" (with contact info)
- erase -> "léirscrios" (disk) or "glan" (screen)
- event -> "teagmhas" (computing) or "imeacht" (calendar)
- extension -> "eisínteacht" (of an application) or "iarmhír" (of a filename)
- manual -> "lámhleabhar" (handbook) or "de láimh" (by hand)
- pager -> "glaoire" (beeper) or "brabhsálaí leathanach" (Unix utility)
- player -> "imreoir" (game) or "seinnteoir" (media player)
- port -> "port" (networking) or "leagan" (version for another system)
- tab -> "táb" (on a keyboard) or "cluaisín" (in web browsers or dialog boxes)
- token -> "ceadchomhartha" (token ring) or "teaghrán comhartha" (parsing)
- track -> "amhrán" (song) or "rian" (storage media)
This work is licensed under a Creative Commons Attribution-ShareAlike 3.0 Unported License.