Palia Wiki:Translation portal

From Palia Wiki
Jump to navigation Jump to search
ChapaaChef.png Looks like someone's cooking up some code! Work is actively being done for this page or section, and will be added soon. Please coordinate with the user(s) involved to ensure there are no conflicts.
Comments: Please make sure you're in the Wiki channels of the Palia Server.

This page is the community portal/hub for creating and managing translations of the Palia Wiki articles into languages other than English. The goal is to make it easy for non-English speakers to get into the game, and as a result, improve the gameplay quality and meta-game for all players.

Current Translations

Make sure that your translation category is added to Category:Translation categories.

Outdated Translations

How Palia Wiki Gets Translated

This wiki is using the Translate Extension to implement translations.

Translating the Palia Wiki is a grand collaboration between wiki editors and international translators. Both types of users are required to ensure articles are completed and translated effectively.

  1. Before translating even begins, content must be created in the primary language of the wiki, which in this case is English. For more on content creation, see Help:How to Edit
  2. Once a page has been completed, an editor can tag the page for translation by following the steps outlined below in the #Wiki Editors section.
  3. After an article has been tagged for translation, it gets reviewed by a wiki administrator and approved for translation.
  4. Approved pages ready to be translated get listed in the Language Statistics page where translators can check for updates on missing, outdated, and completed translations.
  5. The final step is to translate! Find out more about how to help in the #Wiki Translators section below.
Any changes that occur after pages have been translated must be reviewed by a Wiki Admin before being re-sent to the language statistics portal.

Please notify a wiki admin if you start a new translation language.

Wiki Editors

An administrator must verify tags have been used properly and mark a page as Translatable before translating may begin.

Translated pages will contain both translation tags (‎<translate>...‎</translate>) and translation comments (<!--T:1-->).

A picture is worth a thousand words! A gallery of examples on how to tag a page can be found here: Translation portal/Gallery

Translation Tags

To mark a section of text as needing to be translated, simply make use of the ‎<translate>...‎</translate> tags. Translate tags are used to designate exactly which text should be translated.

For example: ‎<translate>Some kind of information might go here‎</translate>

Translation Comments

Translation Comments are automatically added by FuzzyBot after a page has been reviewed by an administrator.

They will appear in the editor as HTML comments like so:


The numbers in these comments represent the translation number for the set of tags (usually the order the tag was created in).

  • Do not add these tags manually. Doing so will prevent the section from being translated properly.
  • Do not remove these tags. Deleting the comment will remove the associated translation!
  • Do not modify these tags. The number within the comment links to a page where translations are stored.

The number T:4 is used by FuzzyBot when generating the translated version of pages to know what content to replace.

Translation Variables

To maintain continuity of complex formulas between translations of an article, the ‎<tvar>...‎</tvar> (Translation Variable) tag can be used.

For example: ‎<tvar name=1>{{Template|With|Complex|Parameters}}‎</tvar>

Important: tvar must be placed between a pair of translate tags.

Note 1: Any name can be used for the Translation Variable. The name used by the variable will be the name that the Translator sees and uses in the translation.
Editor ==> Translator
‎<tvar name=example> ==> $example
‎<tvar name=data> ==> $data
‎<tvar name=1> ==> $1
‎<tvar name=2> ==> $2
Note 2: Variable names are per Translate Tag, not per page, so two different pairs of translate tags can each have a Translation Variable $1. It's simplest to name the variables consecutively (Eg. 1, 2, 3, 4...), however additional context can sometimes be useful.

Commonly Used Translations

To minimize the amount of repetitive words that need translating, the {{Heading}} Template provides a number of commonly used translations for page headers. See the template documentation for a list of commonly used headers, and use this template wherever possible instead of a set of Translate Tags.

== <translate>General</translate> ===
== <translate>Notes</translate> ===
== <translate>Gallery</translate> ===
== {{Heading|General}} ==
== {{Heading|Notes}} ==
== {{Heading|Gallery}} ==

Localized Links

By default page links are not automatically translated and may result in ugly links.

For example: [[Villagers]] would become [[Villagers/de]] on a German page.

The {{LocalizedLink}} template (Or {{LL}} for short) may be used instead. This template reads and displays the translated page name.

For example: {{LL|Villagers}} will read the translated title from the localized language translation of the page and output it.
Villagers is displaying in the current language, right?

Using Templates

A lot of Templates are designed to handle any translations within the template themselves. {{NPC}}, {{Skill}}, {{Item}}, {{Quest}} and some other templates will automatically fetch the translated title from the page given in the template. You can just use ‎<tvar name=1>{{Item|Cantankerous Koi}}‎</tvar> and not have to worry about making translators type the translation of Cantankerous Koi on every page that references it.

Magic Words

Please try to avoid using magic words (like {{PAGENAME}}) in content pages, unless you are using them in Templates for things like checking expressions. Magic words make things difficult for translations. While it is annoying to type Eshe or Cantankerous Koi 12 times, magic words either require special treatment from translators or end being something like Eshe/sv on translated pages. That doesn't really roll off the tongue!

If it's necessary to use a {{PAGENAME}} use one of these instead:

  • {{UntranslatedPagename}} (Which would print Cantankerous Koi on the Cantankerous Koi/sv page) or
  • {{TranslatedPagename}} (Which will print the translated page name if it is available, or the /sv instead. ie: Cantankerous Koi/sv)

Reminder: writing out the page's name is still the preferred method.


If you are working on a template that needs to check the pages language, or need to show the language that a page is in you can use the {{PAGELANGUAGE}} magic word. This magic word will output the pages language code (eg; "en", "fr", "de", "it", etc).

It can be used in conjuction with the {{#language:}} module.

Markup Output Description
{{#language:{{PAGELANGUAGE}}}} English Outputs the current pages language in the current pages language.
{{#language:{{PAGELANGUAGE}}|sv}} engelska Outputs English in Swedish.
{{#language:sv|{{PAGELANGUAGE}}}} Swedish Outputs Swedish in English.


In order for Translated pages to be categorized properly, {{#translation:}} should be added to the pages categories, like so:


Adding this tag to the category will ensure that the main page is still tagged as normal (eg; Category:Materials, Category:Furniture, Category:Templates), while translated pages are categorized as follows:


Category Template

It may also be easier (and look nicer) to use the {{Category}} template. Instead of using category link tags, the template will format the category links with {{#translation:}} for you:


Just as the previous example, the page will be added to Category:Materials, Category:Furniture, and Category:Templates.

Wiki Translators

You can check the Missing translations page to see which pages need translating:

More languages can be created by specifying the language code!

How to Translate

Translating an entire page is a simplified process using the translation editor; Pages are broken down into small segments that FuzzyBot will piece together into whole articles.

Each segment is displayed in its own box in the editor, with space underneath it for the translation to be typed and submitted.

When using the Translation editor, you can still use all Mediawiki Markup, such as ''Italics'', '''Bold''', [[Page Links]], etc.

Some segments will use bolding to emphasize certain phrases, similar markup should be made in translations, but it is ultimately up to the translator on what should and should not be formatted.

Direct Translations: Every language has it's own sets of nuanced phrasing, if something can be worded differently in your language, it's perfectly fine to do so! Just make sure that the same point gets across. There may also be situations in English where one single word is used, but it is not a requirement for your translation to do the same. The translation editor gives mostly free reign.

For more on the translation editor interface, proceed below to #Using the Editor

Translation Variables

To prevent translators from having to deal with complex templates, and certain URLs or page links, translations will sometimes make use of variables.

These variables can be seen at the bottom of the translation editor and look like $page, $number, $name, or sometimes be numbers like $1, $2, or $3. To make use of the variables you can type out the variable name, or click on it!

Page Titles

Often the first translation that is presented when translating a page is the Pages title, here are a few important rules to keep in mind.

When the page is in the main namespace, meaning it is not prefixed with anything like Category: or Guide:, the title can be translated normally like any other translation.

When translating a page that is in other namespaces, please translate both sides of the colon (:) separately, leaving the colon in place.

The {{LL}} or {{LocalizedLink}} templates will use the translated page title when displaying links.

Page Links

Often page links will automatically be translated from page titles with a variety of templates such as {{Item}}, {{Quest}}, {{LL}}. In these cases no additional action is required from translators as these templates will be stored as Variables (Usage in previous section).

In some cases where links are embedded only as links (eg; [[Palia Wiki]]) then the link will need to be modified with the language code and then the translation

eg; [[Palia Wiki/sv|Lorem ipsum]]

This may result in links to pages that don't exist yet, but that's okay! We're working our way through the site to make sure that all pages get translated. It's easier to make sure that links go to where they should, than to try updating them all later.

You may also see links using a translation variable (eg; [[$1|Lorem ipsum]]). The variable defines the page link which may be special, and modifying it is not necessary, updating the displayed text is all you need to do!

Linking to Categories

  • Previously a category link may have looked like this: [[:Category:Fish|Fish]]
  • But can now simply be linked like this: {{LL|Category:Fish}}

The {{LL}} template makes linking to Categories far simpler

  • It will localize the Category link, so a link to Category:Fish may link to Category:Fish/sv
  • It will localize the name of the category, removing the Category: namespace. If Category:Fish is translated as Categorie:Vissen, the Categorie: namespace is trimmed away, and Vissen is used to display the link.

Using the Editor


The translation interface provides a section called "Documentation". This documentation is primarily for main-page editors to provide additional context for translations, editing the documentation is shared across all languages. The documentation section should not be used for leaving remarks about a specific translation.

If you want to leave remarks for other translators of your language on why you chose a specific phrasing (Wording isn't always 1-to-1 from English!) there are two ways of doing so:

  1. The less visible way, leave a comment after your edit in the "Explain your changes" input box
  2. Leaving an HTML comments after your translation. The translation editor supports regular wiki markup as well as HTML. So you may leave an HTML comment like so:
Lorem ipsum dolor sit amet, consectetur adipiscing elit.
This translation is made out of Lipsum!

HTML comments will not show up on the final page, as they do not when left in Wiki markup.

Invalidating a Translation

If a translation needs to be seen by a translator, it is possible to mark a translation as outdated. Doing so will cause the page to show up on the Special:LanguageStats page for the language.

To mark a translated as outdated, simply add !!FUZZY!! to the beginning of the existing translation. From there User:FuzzyBot will do the rest!

Reviewing Translations

The translation editor has a Review mode that allows translations to be reviewed. Reviewing translations is not required, once you've published a translation FuzzyBot will generate the translated page when it's job queue runs.

After you've finished translating a page, you may:

  • Go back and review the translations yourself
  • Skip reviewing the translations, allow another user to review the translations to make sure they also make sense to that person

If you don't want to help by translating pages, but want to be a reviewer you can help out other translators by doing so


Palia Wiki appreciates all the time and energy the following Users have dedicated to translating!

Check out the details on Active Languages or see the table below.

If you would like your username added to the list of contributing translators above, tag your User Page with a relating translator category.

eg: [[Category:SV_Translator]]

The page may need to be purged before your name shows up