Translating
The very nature of the project is multi-lingual and multi-cultural. And although english is (currently) our lingua franca it may not be so in the future—or so we hope—as each community takes over the project and molds it to their needs and objectives.
In the meantime, here are some tips, tricks and things to keep in mind while trying to bridge the language barrier that will hopefully make everybody's life simpler and more productive.
NOTE: most of the things that follow are a personal PoV (by User:Xavi).
fast & furious
So you want to translate a wiki-page? Here's a summary:
- create a /lang-xx sub-page for the translation (copy-pasting the original text as-is)
- eg: original page Core principles => Core principles/lang-es translated page
- preserve section headers
- add before each header a line with <div id="original header"/> (er... obviously, replacing original header by whatever is the original header... )
- this allows linking regardless of target language and/or its wording
- insert the {{Translate Page | ...blah... }} template at the top
- make sure you note the version ID of the original page and diff to the current version—as this will greatly simplify the updating to future editions of the original page!
- add {{Ongoing Translation}} template below it
- if the original page doesn't have it, insert the {{Translations}} template at its top
- This is readily visible (and editable) by following the link present in the template when Show preview is used (a feature highly recommendable not only when translating)
- update the /translations page to link to your translation
- In our example, this would be the Core principles/translations page and will allow multi-lingual navigation of said page
Now you can go back to you the page, translate it at ease, and when you're finished, just remove the {{Ongoing Translation}} template tag.
wiki pages
You are not forced by any means to use what follows—although it may save some time and help develop a standard way of doing things. By no means we are implying this is the best way, and some steps may seem arbitrary, and not really optimal; although their cost may be worthwhile. Any feedback is welcome!
The 'basic' structure of a 'standard' translation is based on the following premises:
- there's a base page you want in another language
- you want to keep it as a 'mirror' translation
- little or no reverse-flow towards the original
One of the main problems when translating is that your personal choice may not be the best one. Text-wise that is not a problem, and here the wiki spirit shows the true power by allowing a more democratic choice of wording. The problem arises from the fact that we are not translating text but also structure (headers, sections, etc.). So if we happen to pick a 'wrong' section header, anything linking to it will be broken when we try to make things better—defeating the wiki kaizen spirit of constant improvements. In order to avoid getting stuck in bad translations, here are some techniques and tips that may help the kaizen spiriti of a wiki-editor.
creating the translated page
Usually you can give a page any name you like, although I recommend using a sub-page technique that uses the language identification: originalPage/lang-xx. This comes in handy as the volume of pages in the xx language grows and won't be able to recall all the exact names of all the translations. So if you find yourself translating a link to say The OLPC Wiki you may wonder what is the exact translation used for your language. Appending /lang-xx to the link takes care of that. If by any chance the page hasn't been translated yet, you may create a redirect page to the original version and do the translation later.
how to set up the translated page
A page worth translating will surely be split up in sections and sub-sections, which are latter used as anchors by the hyper-text system, allowing to refer and link to specific sections. Again, if we translate the section/anchor name, when a better translation is found the links will brake. A simple solution (leveraging on the /lang-xx technique) is to avoid the problem altogether by preserving the original anchors.
For example, if we were to translate the section ==Home==, we could translate it into spanish as either Hogar or Casa—context will probably make one more likely than the other, but you can't always be certain. The problem arises when that header is being used as an anchor for some link: OLPC Human Interface Guidelines/The Laptop Experience/Zoom Metaphor#Home. This 'example' link, is very interesting (although extremely peculiar and rare) because it depends on the original title page OLPC Human Interface Guidelines, the chained subpages The Laptop Experience and Zoom Metaphor, and finally the anchor/section name Home. Each one of them may have multiple possible translations.
The simplest solution is to make the links independent of the translation. The /lang-xx takes care of the page-links and the following trick of the anchor:
# ORIGINAL # TRANSLATION 1 # TRANSLATION REVIEWED
<div id="Home"/> <div id="Home"/>
== Home == == Casa == == Hogar ==
While the links will always remain basically the same:
OLPC Human Interface Guidelines/The Laptop Experience/Zoom Metaphor#Home OLPC Human Interface Guidelines/The Laptop Experience/Zoom Metaphor/lang-es#Home
NOTE: only the /lang-xx has been added—greatly simplifying the linking.
hooking the translation to the wiki
In a wiki, an unlinked page is as good as no page; so we need to somehow make sure that people navigating the site actually can reach those pages in a sensible way. The current technique is based on three elements:
- a template to be included in the translated page,
- a template to be included in the original page, and
- a sub-page indexing the original page's translations (originalPage/translations).
This triad serves two main uses: reader & translator.
- reader
- it allows the multi-lingual navigation by presenting all the translations of a given page in a homogeneous way while avoiding the typical error of forgetting to update all translations with the 'new' translation.
- translator
- by keeping track of the original and diff (to current) anybody can review if the current page is up-to-date in respect to the original.
maintaing the translation
Wikis being what they are, mean that what you translated yesterday is not today's version... so how do you manage the evolution of the original? Fortunately, wiki pages have an essential thing: history; and an extremely useful function: diff. Remember when the {{Translate Page | ...blah... }} template was added, there were two links embeded in it:
- version (ie: http://wiki.laptop.org/index.php?title=The_OLPC_Wiki&oldid=30534)
- diff (ie: http://wiki.laptop.org/index.php?title=The_OLPC_Wiki&diff=current&oldid=30534)
The actual http-link can be extracted initially from the translated page's history page.
The version number 30534 now appears in the original page in the upper right corner. Please note that the diff should compare the current (it's a keyword, not a number) with the translated version ID#.
So at any time, you can verify the changes (if any) of the translated source-version-# with the current-version-#—just by following the link.
IMPORTANT: When updating a translation, you must update the version-# of the links. (Just copy paste the # shown in the original page). This will allow future translators or reviewers to work only in the sections that have changed without actually having to review both documents in order to find differences (some of which may be trivial from the text perspective, but crucial from the exactitude and validity of the content—ie:latest build, etc).
laptop.org
Please refer to the Localization page for further information on the l10n efforts of www.laptop.org.
foreign wiki pages
As the global effort picks up speed, it's our hope and interest that local communities will develop things in their local languages that we may want to share globally. This is already happening, and we are trying to develop the necessary templates to make life simpler (probably a variation on the local translation templates mentioned above). In the meantime, take a look at Hello World!.