Help:Translating Pages

From eRepublik Official Wiki
Jump to: navigation, search
Languages: 
EnglishIcon-English.png
中文(简体)Icon-China.png
فارسیIcon-Iran2.png
DeutschIcon-Germany.png
עבריתIcon-Israel.png
PortuguêsIcon-Portugal.png
Portugues BrasileiroIcon-Brazil.png
РусскийIcon-Russia.png
EspañolIcon-Spain.png
УкраїнськаIcon-Ukraine.png


Green check.jpg

This page represents an official eRepublik Wiki help page.
This is an administrative page. Please notify Admin when editing this page.


Erepublik-logo.jpg

See Also


Contents

The official language of the eRepublik Wiki is English. However, the wiki allows for page translation to make information exchange a bit easier and to better support the truly international community of the New World. This page provides basic instruction on translating pages and templates.

Users should only translate pages into languages in which they are fluent. Automatic translating tools are inefficient and usually wrong.

How to translate pages

  • In the wiki, find the page that needs to be translated and click "Edit"
  • If it isn't already there, add the Language Menu to the page, type: {{LangMenu}} and click "Save"
  • In the Search field, type the name of the page (in English)/Language Name that you want to create and click search. For example, "Train/Polski", "Grain/Српски", or "Info/Bahasa Indonesia"
  • When the search appears, click the red link to create the page.
  • Begin the new page by adding the Language Menu, type {{LangMenu}}
  • Add the language category so that the page will be categorized properly: type [[Category:Language]], for example [[Category:Italiano]], [[Category:Polski]] . No other categories should be on the page (unless they have been added automatically by a template.
  • Begin your translation! Don't forget to copy graphics from the original page!
  • Remember to create links in the proper way (see below)

Creating Links

Translated pages should link to other translated pages. For this, we have created the "L template". This will make linking to translated pages much easier for all involved.

  • This is the format of the template({{L|Link|name of the link}})

For an example on how to use the template, we will look at one from Food/Hrvatski. The first link is for energy, looking at the edit page, we see the code is written like this: {{L|Energy|energiju}}. "Energy" is the link and "energija" (Croatian for energy) is what the link will appear as in the text of the article. The template recognizes that since this is a page that ends in /Hrvatski, the link will go to the energy page that also ends in /Hrvatski. If Croatian version of Energy doesn't exist, the link will take you to the English version of the page.

DO NOT CREATE A REDIRECT IN YOUR LANGUAGE! For example creating the page "Comida" with the redirect to Food/Español. Instead you should create a link like this [[Food/Español|Comida]] or {{L|Food|Comida}} or {{DL|Food|Comida}}

Notes

  • For articles that aren't about gameplay (citizen, party, company pages etc.) the limit of maximum allowed translations is two (English version + 2 translations). If you wish to have more than two translations, leave a message to the bar and wait for community approval.
  • Do not add other categories to your translated page, even if the English version of the page has another category.
  • The only category should be the language category, except in cases where one of the common templates are used.
  • Users should not attempt to create a category structure in their own language.
  • If a page only exists in a language other that English, such as a citizen page or another article. Please do the following: create a basic page in English with a note to click on the language menu to see the page in the other language. Then have the bulk of the text on the page with the language after it. For an example of this see Operação ALPHA or this citizen page MalaBestia.
  • And last, always remember: PLEASE, DO NOT USE SAVE EVERY FEW MINUTES, USE PREVIEW TO SEE YOUR WORK.

A Note to All Translators

First written in the Wiki Chronicle[1]
Our wiki is quickly filling up with translated pages. This is good and helpful to the eRepublik Community. However, monitoring these pages cause an additional administrative workload. Here are a few reminders:

Tip for all Users
The "OFFICIAL" information will always be on the English version of pages. When we receive updates from eRepublik on new features, clarifications, or rule changes the English version is updated first. We have no control over when or if the translated page gets translated. You can always check when the page was last updated by looking at the history tab.

Tips for Editors

  1. EVERY person that creates a page that is NOT IN ENGLISH in this wiki needs to read and understand Help:Translating Pages. If you do not understand, please ask. This page tells you:
    1. How to name pages
    2. How to create links (different than other wiki links)
    3. How to categorize your pages
    4. How to deal with a page that is not a translation, but is only in a language other than English
  2. Editors translating the game information pages MUST REMOVE THE ENGLISH CATEGORIES! The only category on these pages should be the category of the language.
    1. Editors translating pages that have one of the common templates on them will have the English categories because the template puts them there.
  3. If you are translating a page and don't think you will finish it in the time you have, you might want to create it in your sandbox. You can go back to it later and then move it to the main space when finished. There are many "translated pages" that are not completely translated because people started and never continued the translation.
  4. When creating a translated page, make sure your links are taking you to the right page, don't link to a redirect. For example, the page is Experience points, the phrases EP and Experience Points are redirects. This means we now have tons of redirects of the various languages for these in between steps. Make your links to the most DIRECT location.
  5. Remember to keep the graphics and formatting of the original page (unless you are improving it). Just because the pages isn't in English, doesn't mean the people don't get pretty graphics.
  6. Work with other editors who are translating in your language to make a combined and constructive effort. The best translations are those where several people have gotten together to share the work and check for quality.

How to translate templates

This is very complex and takes a lot of courage and use of a sandbox. Please do not attempt ANYTHING in this section unless you have some wiki coding abilities!!

Translating a template isn't difficult but preparing a template to be translated is really difficult, and is an error-prone process because the code is so complex.

  • Check if the template you want to translate is ready for translation
    • Edit the template page and check on the list below if the template includes another template named as the template itself, but ending with /Core
      • If it does then your work is easy: just edit the page Template:NAME/LANGUAGE, use a language already done to help you (tip:most of the translated templates are already translated into Italian, so check the /Italiano pages)
      • If it doesn't then you need to prepare it yourself. This is not an easy thing to do. Better ask a Uber Editor.

How to prepare a template

This is the basic scheme:

  • Template:NAME (e.g. {{IParty}})
    • Calls {{Template:NAME/{{TemplateLang|Template:NAME}}}} passing all the parameters
    • Quite easy to do
  • Template:NAME/CORE (e.g. {{IParty/Core}})
    • Contains the code (this is the Real Bad Beast)
  • Template:NAME/LANGUAGE (e.g. {{IParty/Italiano}})
    • Calls Template:NAME/Core, passing all the parameters and the translated strings

If the template is complicate/very used it's better to create a new template, test it and then move it (e.g. {{MenuRising}}, {{IParty}}, ...)

Now the difficult part: how to prepare the core.

The basic idea is that for every string to be translated you create a iSTRING parameter

  • let's say string is "Social"
  • you create an iSocial parameter
  • you substitute "Social" with {{{iSocial|Social}}}, that way if a translation template edits it, it gets translated, otherwise it defaults to English

Then, the translation work:

  • Create the English page
    • Just create Template:NAME/English and make it call /Core, with "normal" parameters
  • Create an example translation (may be important for other translators)
    • Create Template:NAME/LANGUAGE, and make it call /Core with "normal" parameters coming from the "main" template, and "i" parameters translated

Translators Bureau

If you are looking for a good place to start translating/share your ideas, or you simply do not know what to translate next, visit Translators Bureau.