Help:Adding a Language

Introduction

This wiki uses the Translate extension which is described at Help:Translation. You should read that first. This page describes some of the things we did to make translation easier.

Steps

GetLangSuffix

The first thing to do when adding a new language to the wiki is to edit Template:GetLangSuffix. The template is protected though, so you may need to leave a request in the Discussion page. Administrators patrol this wiki daily, so one of us will see the request soon after you leave it.

The GetLangSuffix template returns text like /es or /de depending on where it is invoked from. It basically extracts the last element of the page name, runs it through a #switch statement, and returns a slash plus the language code if it recognizes the last element as a language code. If it is invoked from an English page, or from a page that it doesn't recognize as a translated page, it will return an empty string. Whatever it returns - an empty string, or a language code - can be tacked to the end of any page title to refer to the translated version of that page. This technique is used extensively throughout the wiki.

Localization:All

The next step is to go to the Localization:All page, and create a translation for the new language. This page is a list of words and phrases that we use in templates so that we don't have to translate the templates. Templates can be very complex, and they are difficult to get right. Most templates will display text to the user by having that text in the localization page, and then using the Template:Localize template which will fetch the translated phrase based on the results returned by {{GetLangSuffix}}. For example:

{{Localize|Honor}}

will return this:

Honor

Which is admittedly not that impressive - except that if you call if from a page ending in /es, it will return "Especialidad" which is the Spanish translation of the word "Honor". That makes it quite magical. It's important to note that the argument passed to the Localize template be in English, and that it have the correct unit name. Spelling and case are important. What this means is that you should not expect

{{Localize|Especialidad}}

to work. The name of the phrase is "Honor" and it doesn't matter what language you invoke it from.

The phrases in Localization:All are used to display the names of the tabs, the names of the hierarchical names of the SDA Church organization (i.e., General Conference, North American Division, etc), the honor categories, the names of the Master Awards, and basically, anything we want to display in a template. If a user is going to see it, it should be in Localization:All.

Each entry in Localization:All is tagged as a section so that it can be extracted as a unit. We've already shown how to extract a unit from this file by using Template:Localize. If we want to add new text to a template, we need to add it to this file, and then translate it (or request a translation) in all the supported languages. Each unit is surrounded by section tags which is how they are identified by the Localize template. Because these words and phrases are used so widely, editing it reserved for administrators, so if you need to add a unit, let us know. Inside the section tags are <translate> tags which identify which part of the entry needs to be translated. But because both of these translate tags are actually displayed when they are included, the <translate> and </translate> tags have to be individually wrapped in <nowiki><noinclude> and </noinclude> tags. It's ugly, but it works and it's powerful.

Localization:other pages

The {{Localize}} template can take an optional second argument to specify an alternate localization page containing the localization (the first argument is the term to localize). This allows us to separate localization terms into more than one page so that the localization replacements can run faster and have a little more organization. The template is called thusly:

{{Localize|Lorem ipsum|page=alt_page}} which would search for term in Localization:alt_page (which doesn't exist - it's just an example).

If the second argument is not specified, the template defaults to using Localization:All. Here is a list of alternate Localization pages which also need to be translated:

• Localization:Answer_Variants
• That's all so far. It's a short list, but we expect it to grow.

Language Specific Graphics

When translating Localization:All, you might notice that "No Patch" and "Not Available at AdventSource" contain file names instead of text. These graphics contain text, so a new localized version of the graphic needs to be created too.

Choose a default Bible version

Template:Bible link takes a Bible verse as a parameter and converts that to a link to biblegateway.com. This template cannot use Localization:All to pass in the Bible version because of the additional wiki markup that is added to everything the {{Localize}} template must return. This extra text is ignored by the wiki rendering software, but we need to use it to specify which version of the Bible is to be used, and the text gets added to a URL. URLs don't ignore wiki markup, so this operation fails. So we had to take a different approach.

You will need to first figure out what version string [biblegateway.com] needs to query a language-specific Bible translation. In English, this string is NKJV. Once you know what string you need to use, create a file in [[Localization:Default Bible verse/language code]]. The only thing that should be placed in the file is the string biblegateway.com needs. Do not use the Translation extension to create this file.

Configure Wikipedia links

Most wikis support interwikis - which is an easy way to link to another wiki such as wikipedia. On our wiki, we can link to a wikipedia article by adding [[W:Anax junius]] to an article. It creates a link to the wikipedia article about Anax junius. But it will take you to the English wikipedia. To make that work in another language, we have to translate Template:Localize wikipedia and change the w to something else. In Spanish, the w becomes esw. It's usually just the language code plus a w. We have several templates that automatically localize to the language of the invoking page, and some of those (such as Template:Species id) provide a link to the wikipedia article of the species (using its Latin name, so that should work in most languages).

How to add/change a language specific logo

First of all the image needs to be created. The image we use here, was created by User:DesignerThan. So contact him and he will be glad to create the needed image. The created image then needs to be uploaded to the wiki. Ask any admin for that, or DesignerThan has already done it.

For the next step, you need the link to the file. You can get that by opening the page of the image, and click on "Original File". Now you can copy the link.

Now you are ready to do the magic. Go to the page MediaWiki:Chameleon.css and start edit mode. There you copy the code of an existing language and copy paste it at the bottom of the page. Change the comment so it names your language, also change the short language name to whatever you need and exchange the link with the link of your image (only paste the parts needed, so it looks like the others).

Now the new logo should be visible if the interface is in your language. If not, try to empty your browser cache and reload the page.

If you want to use the same logo for multiple languages, have a look at the code for Portuguese.

Summary

So basically, to add a new language to the wiki, request that it be added to Template:GetLangSuffix, and then translate Localization:All to the new language. Once that's done, you can start translating regular pages.