The appearance of a wiki page will be based on the language preference of the individual user and is found in their basic settings. Another choice is to have the user be directed to a specific page that utilizes the language chosen by the developer and can be locked to prevent language changes. The way to achieve this is to unpack the system at SystemPagesSetup for all of the languages that need to have full support. This will give two choices based on if the page is already translated into multiple languages.
If there is only one inherent language, it can be copied to the FrontPage. Another option is to turn on the rename command and choose another label for the FrontPage, giving that name as variable for the “page_front_page.” On the other hand, using the multiple languages option will require an instruction if a single language is desired. Otherwise, the user will be directed to the home page based on the language set as default in their browser.
Default Language and User Interface
In MoinMoin, the natural process is to convert the interface to the desired language of the user. With most pages, there will be an option to choose the preferred language, but this is unnecessary in cases where the language is detected from the browser. With this method, the appearing language will be reflective of the user’s browser language settings.
This can be confusing when the exact settings criteria are not met. An example would be a user that has the primary language as Australian English, a secondary setting of Romanian, and then a third setting of International English. Pages which do not have a conversion for Australian English will automatically retrieve the Romanian version instead of the International English, which would probably be the right choice.
There is only one real situation where a programmer will need to ignore the browser’s natural settings – a local wiki that only has a limited national audience with the same language. This is when only one language is meant to be displayed. In this case, the language_ignore_browser setting is put to True and the programmer must be sure to specify the desired language as the correct default.
To stay accurate, the archives for the MoinMoin distribution are kept in more than one language, with the FrontPage and site interface selected based on the user’s preference. In the case that the user’s preferred language is not available, the FrontPage will revert to the default setting that is controlled by the page programmer.
A developer that would like to prevent other language FrontPages from being seen will need to edit the files that control this option. Namely, the best way to do this is to simply delete any other language FrontPage that may exist in the archives. In this manner, there will be no alternative language FrontPage to retrieve and the program will automatically go back to the default.
Inherent and Chosen Translations
In most cases of MoinMoin, the default option will be to use translation that is inherent in the system, also called “built-in” translation. This results in the text and page names being displayed in the correct language.
While most developers are unaware of the possibility, there is a way to change the navi_bar settings to display information that is normally resistant to language translation. The way to do this is to build a few pages that correspond to the languages that should be available, such as SpanishDict, EnglishDict, and JapaneseDict. These should have an attached definition list and gives the right translation for each. Therefore, the end result is that the MoinMoin system will retrieve these translations when it comes across text or page names that cannot be automatically translated.