Tip of the Day
The base chance to find FINE materials is 1/100, which you can increase with better gear and tools.

Wiki Translation

From Walkscape Walkthrough
Revision as of 13:41, 22 December 2025 by Bonez565 (talk | contribs) (Translation on Weblate)
(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)

This is a work in progress and coming soon. The Walkscape Wiki uses the Translate Extension to handle the translation of wiki pages. To get started with helping with wiki page translation you'll need to have a wiki account with a verified email address.

A list of all pages prepared for translation can be found here: Special:PageTranslation

Or to jump right in all needed translations can be found here: Special:Translate

Interface

This is the main part that is added to pages that are able to be translated. The blue box is the language bar and shows both which languages have a page already made and the amount of the filled bubble next to the language shows the percentage of the page translated. Clicking on a language will take you to the current page in that language. The red box in the middle will take you to the translation page allowing you to add, update, or fix translations.

Once you click "Translate this page" then you'll be taken to the language selection and from there you can select the language to work on. If you have set your language on the wiki then it will appear in the suggested languages section. Once you select a language you can begin adding or updating translation units (See the Style Guide below.)

Style Guide

Title

The first translation unit on most pages is the page title. For most pages this should match exactly with what is used in game including capitalization and symbols.

Templates

Because the wiki is heavily data driven and built from the game files all that is needed for most translation units is just to update the language code within the template call. Other parts of the template should be left alone. One of the few exception is on some keyword pages which have a "SplitNumber = #" entry, that number may be adjusted to help the table fit. Language codes use a 2 digit for the language code and an extra two digits for optional region codes. Language codes should be entered in all caps (ie. "EN" for English, or "PT-BR" for Brazilian Portuguese)

Language Code   Language Code   Language Code
Czech CS Croatian HR Slovak SK
Danish DA Italian IT Slovene SL
German DE Japanese JA Serbian SR
English (US) EN-US Lithuanian LT Swedish SV
English EN Latvian LV Thai TH
Spanish ES Norwegian NO Turkish TR
Spanish (Mexico) ES-MX Norwegian Bokmål NB-NO Ukrainian UK
Estonian ET Polish PL Vietnamese VI
Finnish FI Portuguese PT Chinese (Simplified) ZH-HANS
French FR Portuguese (Brazil) PT-BR
French (Canada) FR-CA Russian RU

Text

Text can be adjusted and formatted as appropriate for your language with a few caveats as follows.

  • Links: Links take the form of text wrapped in double brackets when translating text with links only the part to the right of the pipe character "|" should be changed the text to the left controls where the link goes.
    [[Special:MyLanguage/Page to Link To | Text to display]]
    
  • Images: Images are similar to links and should mostly be left as is. You can optionally add an extra modifier that will serve as mouse over text which can be translated.
    [[[[File:Image Name.svg|20px|Text to display]]
    
  • HTML Tags HTML tags assist in deep linking or specific formatting and should be left as is.
    <span id="deep_link_name"></span>
    

Adding Translation Tags

Extra Reading: https://www.mediawiki.org/wiki/Help:Extension:Translate

Basic components of a translated page are the languages and translate tags.

Language tags shold be the first thing on a page it wil add the language bar that allows viewers to select a language.

<languages />

Translate tags are wrapped around text to be translated. For simple pages there can be just one wrapping the entire contents. For pages with multiple sections a new pair of tags should wrap each section.

<translate>Text to be translated.</translate>

Page Example:

Translation on Weblate

On Weblate the wiki strings are added as a single file.

Translation Formatting Notes:

  • Variables are represented by camelCase words in single brackets like this {itemName}. These will be replaced with translated content from the game string with wiki formatting. They should not be changed but may be moved within the string (or even duplicated) as needed.
  • Links are represented by double square brackets [[Special:MyLanguage/Wiki_Page_Name | Text that will be displayed]] Everything left of the the pipe character "|" should be left as is everything between the pipe and the closing brackets can be translated. The entire link structure can be moved within the sentence as needed
  • Line Breaks are represented by a <br> symbol they will force a line break. They are especially useful for table headers to keep the name compact. They can be added or removed as necessary to help format the text.

Description of String Families

  • Common - These are strings used in multiple places as short table headers or to fill in places that act as titles. They should be short and concise as well as use "Title Case" or the equivalent for your language.
  • pageHeaders - These are used for the headers in various pages. They can be as short or as descriptive as necessary.
  • Helpers - These are strings that are used directly in template calls as common strings.

Everything else is a component of various modules and templates and generally have no particular space or style limitations other than the cases described in the "notes" above.