[ad_1]
|picture = Palia Brand.png
|picture = Palia Brand.png
}}{Please be sure you’re within the [https://discord.gg/playPalia Wiki channels of the Palia Server.]}
}}{Please be sure you’re within the [https://discord.gg/playPalia Wiki channels of the Palia Server.]}
{{#vardefine:examplelanguage|{{RandomLanguage}}}}{type=asc}
{{#vardefine:examplelanguage|{{RandomLanguage}}}}{type=asc}
This web page is the group portal/hub for creating and managing translations of the Palia Wiki articles into languages apart from English. The purpose is to make it straightforward for non-English audio system to get into the sport, and consequently, enhance the gameplay high quality and meta-game for all gamers.
This web page is the group portal/hub for creating and managing translations of the Palia Wiki articles into languages apart from English. The purpose is to make it straightforward for non-English audio system to get into the sport, and consequently, enhance the gameplay high quality and meta-game for all gamers.
Appears like somebody’s cooking up some code! Work is actively being accomplished for this web page or part, and might be added quickly. Please coordinate with the person(s) concerned to make sure there aren’t any conflicts.Feedback: Please be sure you’re within the Wiki channels of the Palia Server.
This web page is the group portal/hub for creating and managing translations of the Palia Wiki articles into languages apart from English. The purpose is to make it straightforward for non-English audio system to get into the sport, and consequently, enhance the gameplay high quality and meta-game for all gamers.
Guarantee that your translation class is added to Class:Translation classes.
Outdated Translations
This wiki is utilizing the Translate Extension to implement translations.
Translating the Palia Wiki is a grand collaboration between wiki editors and worldwide translators. Each varieties of customers are required to make sure articles are accomplished and translated successfully.
- Earlier than translating even begins, content material should be created within the main language of the wiki, which on this case is
English. For extra on content material creation, see Assist:Methods to Edit - As soon as a web page has been accomplished, an editor can tag the web page for translation by following the steps outlined under within the #Wiki Editors part.
- After an article has been tagged for translation, it will get reviewed by a wiki administrator and permitted for translation.
- Accepted pages able to be translated get listed within the Language Statistics web page the place translators can verify for updates on lacking, outdated, and accomplished translations.
- The ultimate step is to translate! Discover out extra about methods to assist in the #Wiki Translators part under.
-
-
-
- Any adjustments that happen after pages have been translated should be reviewed by a Wiki Admin earlier than being re-sent to the language statistics portal.
-
-
Please notify a wiki admin for those who begin a brand new translation language.
Translated pages will include each translation tags (<translate>...</translate>) and translation feedback (<!--T:1-->).
Translation Tags
To mark a bit of textual content as needing to be translated, merely make use of the <translate>...</translate> tags. Translate tags are used to designate precisely which textual content needs to be translated.
- For instance:
<translate>Some type of data would possibly go right here</translate>
Translation Feedback are robotically added by FuzzyBot after a web page has been reviewed by an administrator.
They may seem within the editor as HTML feedback like so:
<!--T:1-->
<!--T:2-->
<!--T:3-->
<!--T:4-->
The numbers in these feedback characterize the interpretation quantity for the set of tags (normally the order the tag was created in).
- Don't add these tags manually. Doing so will stop the part from being translated correctly.
- Don't take away these tags. Deleting the remark will take away the related translation!
- Don't modify these tags. The quantity inside the remark hyperlinks to a web page the place translations are saved.
The quantity T:4 is utilized by FuzzyBot when producing the translated model of pages to know what content material to exchange.
- Web page titles are saved in:
- Numbered translation tags (eg;
T:4) might be saved right here:
Translation Variables
To take care of continuity of advanced formulation between translations of an article, the <tvar>...</tvar> (Translation Variable) tag can be utilized.
- For instance:
<tvar title=1>{With}</tvar>
Essential: tvar should be positioned between a pair of translate tags.
- Notice 1: Any title can be utilized for the Translation Variable. The title utilized by the variable would be the title that the Translator sees and makes use of within the translation.
- Notice 2: Variable names are per Translate Tag, not per web page, so two totally different pairs of translate tags can every have a Translation Variable
$1. It is easiest to call the variables consecutively (Eg. 1, 2, 3, 4...), nevertheless extra context can typically be helpful.
Generally Used Translations
To attenuate the quantity of repetitive phrases that want translating, the {{Heading}} Template gives plenty of generally used translations for web page headers. See the template documentation for an inventory of generally used headers, and use this template wherever doable as an alternative of a set of Translate Tags.
== <translate>Basic</translate> ===
== <translate>Notes</translate> ===
== <translate>Gallery</translate> ===
== {Basic} ==
== {Notes} ==
== {Gallery} ==
Localized Hyperlinks
By default web page hyperlinks usually are not robotically translated and should lead to ugly hyperlinks.
- For instance:
[[Villagers]]would turn out to be[[Villagers/de]]on a German web page.
The {{LocalizedLink}} template (Or {{LL}} for brief) could also be used as an alternative. This template reads and shows the translated web page title.
- For instance:
{Villagers}will learn the translated title from the localized language translation of the web page and output it.- Villagers is displaying within the present language, proper?
Utilizing Templates
Loads of Templates are designed to deal with any translations inside the template themselves. {{NPC}}, {{Ability}}, {{Merchandise}}, {{Quest}} and another templates will robotically fetch the translated title from the web page given within the template. You possibly can simply use <tvar title=1>{Cantankerous Koi}</tvar> and never have to fret about making translators sort the interpretation of Cantankerous Koi on each web page that references it.
Magic Phrases
Please attempt to keep away from utilizing magic phrases (like {{PAGENAME}}) in content material pages, until you might be utilizing them in Templates for issues like checking expressions. Magic phrases make issues troublesome for translations. Whereas it's annoying to sort Eshe or Cantankerous Koi 12 occasions, magic phrases both require particular therapy from translators or finish being one thing like Eshe/fr on translated pages. That does not actually roll off the tongue!
If it's a necessity to make use of a {{PAGENAME}} use considered one of these as an alternative:
- {{UntranslatedPagename}} (Which might print
Cantankerous Koion theCantankerous Koi/frweb page) or - {{TranslatedPagename}} (Which is able to print the translated web page title whether it is obtainable, or the /fr as an alternative. ie: Cantankerous Koi/fr)
Reminder: writing out the web page's title continues to be the popular technique.
Languages
If you're engaged on a template that should verify the pages language, or want to indicate the language {that a} web page is in you should use the {{PAGELANGUAGE}} magic phrase. This magic phrase will output the pages language code (eg; "en", "fr", "de", "it", and many others).
It may be utilized in conjuction with the {{#language:}} module.
Classes
To ensure that Translated pages to be categorized correctly, {{#translation:}} needs to be added to the pages classes, like so:
[[Category:Materials{{#translation:}}]]
[[Category:Furniture{{#translation:}}]]
[[Category:Templates{{#translation:}}]]
Including this tag to the class will be certain that the principle web page continues to be tagged as regular (eg; Class:Supplies, Class:Furnishings, Class:Templates), whereas translated pages are categorized as follows:
Class:Supplies/fr Class:Supplies/de Class:Furnishings/fr Class:Furnishings/de Class:Templates/fr Class:Templates/de
Class Template
It might even be simpler (and look nicer) to make use of the {{Class}} template. As a substitute of utilizing class hyperlink tags, the template will format the class hyperlinks with {{#translation:}} for you:
{Furnishings
}
Simply because the earlier instance, the web page might be added to Class:Supplies, Class:Furnishings, and Class:Templates.
You possibly can verify the Lacking translations web page to see which pages want translating:
Extra languages could be created by specifying the language code!
Methods to Translate
Translating a complete web page is a simplified course of utilizing the interpretation editor; Pages are damaged down into small segments that FuzzyBot will piece collectively into complete articles.
Every phase is displayed in its personal field within the editor, with house beneath it for the interpretation to be typed and submitted.
When utilizing the Translation editor, you possibly can nonetheless use all Mediawiki Markup, resembling ''Italics'', '''Daring''', [[Page Links]], and many others.
Some segments will use bolding to emphasise sure phrases, related markup needs to be made in translations, however it's in the end as much as the translator on what ought to and shouldn't be formatted.
Direct Translations: Each language has it is personal units of nuanced phrasing, if one thing could be worded otherwise in your language, it is completely nice to take action! Simply be sure that the identical level will get throughout. There can also be conditions in English the place one single phrase is used, however it's not a requirement to your translation to do the identical. The interpretation editor offers largely free reign.
Translation Variables
To stop translators from having to take care of advanced templates, and sure URLs or web page hyperlinks, translations will typically make use of variables.
These variables could be seen on the backside of the interpretation editor and appear like $web page, $quantity, $title, or typically be numbers like $1, $2, or $3. To utilize the variables you possibly can sort out the variable title, or click on on it!
Web page Titles
Typically the primary translation that's offered when translating a web page is the Pages title, listed here are a number of vital guidelines to bear in mind.
When the web page is in the principle namespace, which means it's not prefixed with something like Class: or Information:, the title could be translated usually like another translation.
When translating a web page that's in different namespaces, please translate each side of the colon (:) individually, leaving the colon in place.
- Web page titles are saved in:
The {{LL}} or {{LocalizedLink}} templates will use the translated web page title when displaying hyperlinks.
Web page Hyperlinks
Typically web page hyperlinks will robotically be translated from web page titles with quite a lot of templates resembling {{Merchandise}}, {{Quest}}, {{LL}}. In these circumstances no extra motion is required from translators as these templates might be saved as Variables (Utilization in earlier part).
In some circumstances the place hyperlinks are embedded solely as hyperlinks (eg; [[Palia Wiki]]) then the hyperlink will have to be modified with the language code and then the interpretation
- eg;
[[Palia Wiki/fr|Lorem ipsum]]
This will likely lead to hyperlinks to pages that do not exist but, however that is okay! We're working our manner by the positioning to be sure that all pages get translated. It is simpler to be sure that hyperlinks go to the place they need to, than to strive updating all of them later.
You may additionally see hyperlinks utilizing a translation variable (eg; [[$1|Lorem ipsum]]). The variable defines the web page hyperlink which can be particular, and modifying it's not essential, updating the displayed textual content is all it's worthwhile to do!
Linking to Classes
- Beforehand a class hyperlink might have seemed like this:
[[:Category:Fish|Fish]] - However can now merely be linked like this:
{Class:Fish}
The {{LL}} template makes linking to Classes far less complicated
- It can localize the Class hyperlink, so a hyperlink to
Class:Fishmight hyperlink toClass:Fish/fr - It can localize the title of the class, eradicating the
Class:namespace. IfClass:Fishis translated asCategorie:Vissen, theCategorie:namespace is trimmed away, andVissenis used to show the hyperlink.
Utilizing the Editor
Documentation
The interpretation interface gives a bit known as "Documentation". This documentation is primarily for main-page editors to offer extra context for translations, modifying the documentation is shared throughout all languages. The documentation part shouldn't be used for leaving remarks a few particular translation.
If you wish to depart remarks for different translators of your language on why you selected a selected phrasing (Wording is not all the time 1-to-1 from English!) there are two methods of doing so:
- The much less seen manner, depart a remark after your edit within the "Clarify your adjustments" enter field
- Leaving an HTML feedback after your translation. The interpretation editor helps common wiki markup in addition to HTML. So chances are you'll depart an HTML remark like so:
Lorem ipsum dolor sit amet, consectetur adipiscing elit.
<!--
This translation is made out of Lipsum!
-->
HTML feedback won't present up on the ultimate web page, as they don't when left in Wiki markup.
Invalidating a Translation
If a translation must be seen by a translator, it's doable to mark a translation as outdated. Doing so will trigger the web page to indicate up on the Particular:LanguageStats web page for the language.
To mark a translated as outdated, merely add !!FUZZY!! to the start of the prevailing translation. From there Consumer:FuzzyBot will do the remaining!
Reviewing Translations
The interpretation editor has a Evaluation mode that enables translations to be reviewed. Reviewing translations is not required, as soon as you have printed a translation FuzzyBot will generate the translated web page when it is job queue runs.
After you have completed translating a web page, chances are you'll:
- Return and evaluate the translations your self
- Skip reviewing the translations, permit one other person to evaluate the translations to ensure in addition they make sense to that particular person
In the event you do not wish to assist by translating pages, however wish to be a reviewer you possibly can assist out different translators by doing so
Palia Wiki appreciates on a regular basis and power the next Customers have devoted to translating!
Take a look at the main points on Lively Languages or see the desk under.
If you want your username added to the listing of contributing translators above, tag your Consumer Web page with a relating translator class.
- eg:
[[Category:FR_Translator]][[Category:LANGUAGECODE_Translator]]
The web page might have to be purged earlier than your title exhibits up
[ad_2]