Translating/HowTo/lang-es
Traducción de Translating/HowTo | original |
english | español | 日本語 | 中文 | català | Indonesia +/- | cambios |
- This is an on-going translation
Sugar framework |
Python framework |
Localizing an XO |
Keyboards |
Changing language |
Getting started |
Website translation |
modify |
Participar en proyectos de traducción puede ser divertido y gratificante. Sin embargo, la naturaleza volátil de wiki puede hacer las cosas difíciles para el traductor. Estas complicaciones pueden superarse siguiendo unas reglas simples y usando prácticas de trabajo estandarizadas. Se espera que esto permita a cualquier persona colaborar en el esfuerzo de traducción y, al mismo tiempo divertirse en el proceso.
Taking part in translation projects can be fun and rewarding. However the volatile nature of wiki can make things difficult for the translator. These complications can be overcome by following a few simple rules and using standardised work practices. It is hoped that this will allow anybody to collaborate in the translating effort and at the same time have fun in the process.
Las plantillas de traducir ahora tratan de dar un texto de ayuda para guiarlo a través del proceso. Este texto de ayuda es la mejor guía para la traducción. Pruebe a empezar poniendo la plantilla {{translations}} en su página de inicio y siga las instrucciones recursivamente, grabando la página correspondiente, y leyendo las nuevas instrucciones. El material que aparece a continuación se conserva en caso de que los textos breves de ayuda lo lleven a confundirse, sin embargo, en algunos casos es obsoleta.
The translate templates now attempt to give help text to guide you through the process. This help-text is the best guide for translating. Try starting out by putting the {{translations}} template on your home page and recursively following the instructions, saving the relevant page, and reading the new instructions. The material below is preserved in case the brief help texts leave you confused, yet in some cases it is out-of-date.
Step-by-step summary
Desde el punto de vista del wiki, hay básicamente tres formas de enlazar una página traducida:
- [[Configurar la página fuente: asegurarse de que haya una plantilla {{Translations}}| modificar la fuente de la página]]&mdash si nunca se ha traducido;
- agragar una referencia — apuntar/vincular la traducción de manera estándar, y
- acondicionar la página traducida — añadiendo alguna estructura de ayuda.
La mayoría de las veces, los traductores sólo se enfrentarán con los dos últimos pasos (la creación y la vinculación de la traducción)
From the point-of-view of the wiki, there are basically three tasks to hook up a translated page:
- [[Setting up the source page: ensure it has a {{Translations}} template|modify the source page]] — if it has never been translated;
- adding a reference — point/link to the translation in a standard way; and
- conditioning the translated page — adding some helper structure.
Most of the time, translators will only deal with the last two steps (setting up and linking the translation).
Puede ver una vista general de la estructura relevante de una página, y un ejemplo de acabado completo hacia el final de esta página.
You can see an overview of the relevant structure of a page, and a full finished example towards the end of this page.
Setting up the source page: ensure it has a {{Translations}} template
Vamos a suponer que usted desea traducir una página que es supervisada por el equipo de OLPC; lo que significa que tendrá una referencia al {{OLPC}} template— que agrupa las páginas Category:Paginas monitoreadas por OLPC— y con frecuencia son los puntos de entrada o que contengan información que pueda ser más útil, evidentemente, para las comunidades locales.
We'll assume that you want to translate a page that is monitored by the OLPC team; meaning that it will have a reference to the {{OLPC}} template—that groups pages in the Category:Pages monitored by OLPC—and they frequently are the entry points or that contain information that may be more obviously helpful for the local communities.
Si la página a traducir ya tiene una barra de idiomas, puede pasar a #Modifying the language bar
If the page to translate already has a language bar, you can skip down to #Modifying the language bar.
[[Página Original]] | (Página traducida que no existe—aun) |
---|---|
{{OLPC}} == Algún encabezado == Algún texto blah... |
Adding the language bar
Aunque es raro, puede que sea necesario traducir una página que nadie más ha traducido antes. En ese caso, debe ser añadida una barra de navegación de las traducciones en la página original.
Although it is rare, it may be necessary to translate a page that nobody else has translated yet. In that case, a translations navigation bar must be added in the original page.
[[Página Original]] | (página traducida que no existe —aun) |
---|---|
{{OLPC}} {{Translations}} == Algún encabezado == Algún texto blah... |
Setting up the /translations
You should follow the [[Original page/translations]] link in order to edit the page that groups the translations of a particular page, and should look something like this:
To edit the page that groups the translations of a particular page, follow the [[Original page/translations]] link. It should look something like the following:
{{translationlist | xx | origlang=en}}
The resulting page will have a red colored link, denoting a missing/broken link to your future translation. Don't worry, you'll fix that in the next step.
NOTE: The Translationlist template uses the form "The OLPC Wiki/lang-es" for translated pages. If you want to change it later so that the page title is in the target language (e.g. "El Wiki de la OLPC"), use the "move" function of the wiki; this automatically creates a redirect link so that the interlanguage links still work. (As a matter of fact, there are many pages that do not follow this structure, but most of them are left over from when there wasn't a clear structure and way for adding translations. As mentioned in the translating pages, there are advantages to sticking with the /lang-xx structure.)
Modifying the language bar
When inserting the link to your page, please keep things in alphabetical order denoted by the /lang-xx sequence (if you're adding say /lang-de it should go before the link to 'english'). Also, note the spaces around the '
Setting up the translated page
Although the translator is given as much freedom to edit and to translate as possible when translating the wiki, there is one rule that must be adhered to at all times. The translated page must be declared as a {{Translation}}. (Please note the use of "singular". Plural is for the original page and it will have many translations.)
There are couple of other bits of advice that may improve the quality of the translation process. First, please keep navigation and linking within the translated pages simple and easy to follow. Secondly, preserving the original text in the translation may simplify peer review and help with maintenance.
The quickest way to set up a page is by going back to the original page, then copying the wiki-text. This can be done either by following the edit link or through view source if the page is protected. Then copy the whole page and paste it onto the new page.
Adding the Translation template
For a full explanation of the parameters, see the Notes below, in short: lang — is the IANA language code (usually 2 letters, without any further segmentation—ie: instead of lang-pt-BR (brazilian portuguese), just lang-pt (portuguese)—just to keep things simple and neutral.
Adding the Ongoing Translation template
The main purpose of the {{Ongoing Translation}} template is to inform the readers that a particular page is still not finished, therefore they can expect the presence of untranslated text or that it hasn't been reviewed enough and thus may not be quite done yet. Parallel to that notice to the reader, it does a grouping of them in the Ongoing Translation category thus allowing other translators to find them and collaborate, review, make comments, etc. on them.
Translating section headers
When translating section headers, the best practice is to preserve them as anchors. Then add the translated header under it.
For example if the section header is called "Some Section Header" and it is translated into German in the form of "Einige Paragraph Kopfzeile". Original text "Some Section Header" is preserved by wrapping it between curly braces like the following:
{{anchor|Some Section Header}}
Translating links
As a result, following "einige-link" will connect to "some-link". The reader will only see the translated link "einige-link".
Linking to a page in particular language
When linking to a translated page in a particular language use the /lang-xx to point to that particular translation.
[[some-link/lang-de|einige-link]]
Translating texts
Handling translated links that point to a non-existent page
At the beginning, any link you 'translate' will most likely point to a non-existing page; don't worry. There are two alternatives:
- let the wiki handle them through Special:Wantedpages
- make one last translating effort: dedicated redirects
The first alternative is the simplest but also the hardest on the reader (lands them on the 'create page option' which is hardly the best alternative). Another downside, is that it'll be hard to detect those 'wanted pages' for a specific language, as they will be in the same list as all other 'missing translated pages' in other languages plus all the naturally missing pages in the wiki (a long list due to historical reasons).
Note: the last option is only available for those languages whose "inline translation instructions" are not red in this table. Use the links there to create instructions for your language, based on English or Spanish, in a template named "translation/no translation/lang-xx".
- WARNING
- Make sure that the original page is not linking to a REDIRECT. If that is the case, you should change the target to the real page and create there the /lang-xx subpage. For example, if the [[Foo]] actually is a redirect to [[Bar]], then you should create the [[Bar/lang-xx]] instead of [[Foo/lang-xx]] and change the referencing link accordingly.
This will serve three purposes, first the page will at least take the reader to the right page (albeit not in the correct language). Secondly, the Category will allow a simple way to check 'what is missing'. Finally, and using the What links here from the toolbox you can find out how many references to the missing page exist, giving some sense of need for it and thus guiding the translating efforts.
Please do NOT add these fake translation redirects to the /translations page, as it doesn't make sense to advertise a translation that doesn't yet exist. Only when the REDIRECT is made into a real translation (ongoing or otherwise) add the link to the language navigation page.
Full example of a wiki-page
Anatomy of a wiki-page
Full finished example
Notes
- shortNativeName
- should be in the native language; español instead of spanish.
Translation template notes
For the full documentation, please see Template:Translation.
- lang
- This parameter identifies the target language of the translation. See ISO 639 for a select list of codes being used in the wiki. (Another source is IANA's lang codes).
- It serves several purposes, and is used in several contexts although it should be done in a homogeneous way.
- We are currently using ISO 639-1 codes (two-letter codes).
- source
- is the name of the page (not the link—in other words, without the enclosing square brackets).
- version
- Each original page has a unique version number. These version numbers appear on the far right of the 'blue language navigation bar', and appear in the form: [ID# yyyyy]
- When a page edit is submitted, the version number for that particular page is incremented.
- A translated page on the other hand does not have a visible version number on its own. It must be manually assigned by the translator when an edit is submitted. The version number of a translated page is the same as the version number of the original page which it is based on.
- For example if the original page has a version number ID# 54321, and the translatation is based on this particular version, the translated page is given the version number ID# 54321.
- The version number for the translated page is entered at the top of the page as a parameter for the {{Translation}} function.
- {{ Translation
- There is one use which results directly from the above manual assignment of a version number to the translated page. It allows the translator to easily lookup what new translations are needed by following the 'changes' link located to the far right of the 'blue language navigation bar'.
- Suppose translator 'A' is making a translation of page Bitfrost with version number ID# 65535 into español. As per this guide, translator 'A' assigns version number ID# 65535 to the Bitfrost/lang-es español translated page. Meanwhile editor 'B' arrives and edits the original Bitfrost page and its version number is incremented to ID# 65536. Translator 'A' then can see what new translations are necessary by following the 'changes' link located on the blue nav bar. The 'changes' link compares the differences of two versions of the original page ID# 65535 and ID# 65536. By observing the resulting output, translator 'A' could easily see what new text needs to be translated.
Translated text template notes
- display
- is used to show or hide the enclosed translated text.
- While doing the translation, it comes in handy for comparing the original with the translation. When finished, you can replace the block with none and the source text is not displayed. Although it adds quite a bit of text and 'noise' to the source of the translated page, it comes in handy when trying to update or synchronize it with any changes in the original page—after all, this IS a wiki and pages are supposed to mutate!