Traditionally, multiple wiki instances are needed to support multiple languages. This approach is problematic since wiki management needs to be handled separately for each language; users need to maintain an account and user page per language, the same services need to be registered for each instance, common templates cannot be leveraged, and there is no easy mechanism for performing cross-language searches. With the upcoming changes described in this document, MindTouch Deki will provides seamless support for multiple languages within one wiki!
Each site is associated with a default language: this is usually en-us, but can be overwritten in "Site Settings" by using the "Site site language" option:

This value is used to localize the user interface, if that language's resource file exists.
A wiki may be converted to a "multi-language" mode by adding the config key languages with a comma-separated list of language codes (example: en,ko,zh-cn,it,ja,pt,ru,nl,pl,hu,ca,cs,fr,de,es,fi,zh-tw) through the "Configuration" screen in the control panel. When this occurs, 3 UI changes occur:
Note: Do not confuse the languages config key with the ui/language config key. They are separate and different config keys. The ui/language config key is the general language to use for the site and changing the key will not enable multi-language support.
When a page is loaded, Deki Wiki will first examine the language assigned to the page through "Page properties." If this value has not been set, Deki Wiki will examine the language set by the user in their "User Preferences." If this does not exist, Deki Wiki will use the general site language set by the administrator.
Every page is now associated with a language (or language neutral), which can be set through a page properties user interface. New pages automatically inherit language settings from their parent. As a result, it is easy to setup the following sort of hierarchy under the home page, where all pages created under Main_Page are automatically English, under Portada are Spanish, and under メインページ are Japanese:

The page language determines the language of the user interface; changing the page language will cause the language of all the menus and buttons shown on that page to change. Thus, once a users navigate within a language sub-tree, it appears as if the wiki is decidicated to the seleted language.
In order to promote a common set of templates across multiple languages, Deki Wiki now supports localized templates. To insert localized text, use the lang attribute; lang="<language>" includes the content only if the page using the template has the specified language, whereas lang="*" includes the content if no other language match is found. For example, to create a template of a red box warning that something is obsolete:
<span style="border: 1px solid #FF9999; background-color: #FFDBDB; font-size: 9px; vertical-align: text-top;"><div lang="*">Obsolete</div>
<div lang="es">Obsoleto</div>
<div lang="ja">廃止</div></span>
Output when included on an English page:
Output when included on a Spanish page:
Output when included on a Japanese page:
Deki Wiki provides several mechanisms to help users locate content in other languages:
Often, the same page appears in multiple languages. The following Deki Wiki extension makes it possible to associate these pages:
{{wiki.languages({ '<language1>': '<path1>', '<language2': '<path2>', ... })}}
For example, adding the DekiScript below to an English page on XML associates it with the corresponding Spanish and Japanese XML pages:
{{ wiki.languages( { 'es': 'Portada/XML', 'ja': 'メインページ/XML' } ) }}
Output(as seen on the bottom of the page:

The location of the "In other languages" can vary depending on the skin implementation
There is no mechanism to enforce translations to maintain 1:1 relationships. Using the "Page Language" method Deki Wiki will end up with the same problem.
What would be really great is storing all translations in the same topic text, with client-side tools assisting translators:
* Per-paragraph translations
* Warning symbols for translated content that wasn't updated after a change was made to another language
* Assume embedded content is language-neutral but allow per-language overriding (for example graphics which contain text)
With this in place, translations would have a better chance of being in sync and partial translations would be possible. For example a user could select a "give me spanish except when the english version is more recent" setup and they would see pages with certain paragraphs in English.
I hope that the site I'm creating will be in atleast ten different languages. And while I hope the data will stay 1:1 if you guys made it easier for translators and people fluent or good in several languages that would be such a plus.
As it's hard to say in which language the best information on a topic might be written in first, and then translated from. It's not an easy problem but wow imagine the possibilities.