Translate a Page/es

Herramientas disponibles

• El flujo de los trabajos de la traducción describe el flujo de trabajo para migrar al nuevo sistema de traducción

Flujo de trabajo

• Request addition to the Translator group:
  • Click on Get a Translator Account in the sidebar
  • Click on the Edit icon and enter your username, the language you want to translate for and whether you intend to translate off-line
  • Use Save page to save the information

• When your user has been added to the group (you should get an notification), click on Start Translating in the sidebar

• Escriba el idioma que desea traducir en Código de idioma y haga clic en Ir

Note

Entering en (English) as the language code won't display any untranslated messages since all original content is written in English

• Has clic en una página que desea traducir en la lista

• In the Translate page set View all untranslated message in the first drop-down list

• Comprueba que se muestra el código de idioma correcto

• In the Navigation section, click on the link to the left of the message you want to translate

• Enter the translation - a Google translation is provided for reference, but your own translation is usually preferred.

• Click on Save and open next to continue with the next message or Save page to save the translation if you wish to stop working.

Warning

Do not create a localized page variant manually (by entering pagename/langcode and trying to translate the original). This will mess up the translation system and no translation will be shown at all.

Consejos y trucos

Image display instructions

A typical example is [[Image:Plasma-kickoff.jpg|right|160px]]. The whole of this is a system instruction on how to display the image. None of it is translated.

Category statements

In this context, think of the word "Category" as a system word which therefore should not be translated. For example, [[Category:Administration]] would become [[Category:Administrasi/id]]

For consistency, UserBase has lists of approved translations of categories. Translation teams may find a similar list useful. Such tables can be seen at Translation Help Needed. Please request help if you need it.

Vinculos a otras paginas en TechBase

These take the form [[Special:myLanguage/Other page|link text]] The link should remain untranslated, whereas the link text should always be translated. If no link text is present, please add suitable (translated) link text.

Nota: "myLanguage" intentará cargar la versión traducida del vinculo en el idioma establecido en las preferencias del usuario. Si falla se cargara el original en Inglés, por lo que es seguro para el uso de cualquier enlace interno.

Links to external sites

These take the form [http://example.com link text]. Like the internal links, retain the actual link and translate the link text.

Links in the Sidebar

Instructions for translating those sidebar links can be found at Modifying_the_Sidebar#Translating_Sidebar_Items

Info-boxes

These generally consist of a header word "Information" and an editable information text. If the word "Information" is not recognizable in your language you may need a localized version of the template. Please ask if you need help with this.

Translated units are marked as fuzzy

Sometimes it may happen that you have translated a page, but the translation is marked as incomplete. Certain errors in the markup of the original page can cause this. The most common type of error is the appearance of unbalanced brackets or parentheses. The translation system requires that all opening brackets ('[', '{' or '(' ) have a matching closing bracket (']', '}' or ')' ) in the same translation unit, otherwise the translation is considered incomplete.

The same rule is not enforced by the wiki software, so it is easy for writers to miss those mistakes. If a bracket character is simply missing, just add it. However, sometimes the bracketed content extends over more than one translation unit, so that the matching closing bracket is in later unit. In this case you need to balance brackets in both units, but you can't simply add bracket characters without changing the meaning or formatting, so you must must comment out the added bracket character, like this

<!--}}-->{{Info|1=Beginning of long info box... 

and in a later unit

 ...end of long info box}}<!--{{-->

If the offending bracket is part of a smiley, please replace it with an emoticon icon. For the standard smiley, :-), you can use the template {{Smiley}}

Please also correct the original page so other translators won't have the same problem, or leave a message on the discussion page.

Language Statistics discrepancies

You may notice some slight discrepancy between the percentages stated on your LanguageStats page and the percentage on the language bar. This is normal. LanguageStats compares only the number of messages that are untranslated or outdated. The language bar statistic tries to be more intelligent. For instance, in one page (100 messages) 8 messages had a small (re-branding-releated) change, in each case, a single word was involved. There was 8% difference between the two statistics, since it was a substantial proportion of the messages, but a small proportion of the whole translation.

Si utiliza Chromium o el navegador Chrome ....

Be aware that there seems to be some sort of caching problem on the Chromium browser. I have noticed that even with forced refreshes, sometimes statistics do not show up as they should (I have seen other things affected, too), yet if I open the same page in Firefox I see the correct stats.

Véase también

• [1]