This is not documentation about using Tiki but documentation for tiki site admins about customizing the interface. Perhaps the part about using custom translations should be on doc and the part about contributing translations should be on a i18n workspace on tiki.org.
This page is a kind of tutorial, that needs needs review. Moreover, some more screenshots would be nice... See related page: i18n Admin.
Table of contents
- 1.1. Status of the translations
- 1.2. Translate through i18n.tiki.org
- 1.3. Translate editing the language.* files on disk and use svn
- 1.4. More Information
See also * Interactive Translation of Tiki Interface
That ususally means commiting changes to the next development version of Tiki (since these changes will be merged into the trunk branch of development).
For example, to improve the translation into Catalan, it is necessary to modify the content of the file:
And since tiki6.1, you can edit the strings at:
These .php (and .js) file contains a bunch of lines with pieces of sentences or words (“strings of text”) like:
(...) "Internationalization" => "Internacionalització (I18n)", "I18n setup" => "Configuració de I18n ", "Best Language" => "Millor idioma", "Restrict available languages" => "Restringeix idiomes disponibles", "Available languages:" => "Idiomes disponibles:", // "Intertiki exchange feature" => "Intertiki exchange feature", // "Intertiki client" => "Intertiki client", (...)
Lines that start with “// ”, such as:
// "Intertiki exchange feature" => "Intertiki exchange feature",
have not been translated yet. It is necessary to translate the right side of the line (to the right of “=>”, the full text between the right set of double quotation marks (e.g. “Intertiki exchange feature” in the example above). Then delete the two initial slashes and the blank which follows (“// ”). This way, the previous example would be (once translated):
"Intertiki exchange feature" => "Funcionalitat d'intercanvi Intertiki",
Once you have translated a few strings, save the file language.php (and return a saved copy back into the original place you got it, if you had moved it somewhere else to edit it. Then execute the command:
in order to ensure that Tiki understands your changes, and re-sort the text strings grouping the ones that still need to be translated, etc.
You can then continue translating, etc., and repeating the process as frequently as desired.
In the end, the file will need to be uploded to the Tiki SVN (the central repository of code; keep reading, further down).
This general process has some variants, depending on how to edit the file that contains the text strings. Shortly, you can modify:
- Each time directly against the central repository svn. How to commit
- Previously through Wiki pages
- Previously through Tiki itself (database)
Be careful that the language.php is a php parseable file. So you must not change some lines at the top
<?php // -*- coding:utf-8 -*- $lang=Array(
And some lines at the bottom
Be also careful to respect the syntax on each line
"..." => "...",
Each string is surrounded with double quotes “. If you need to add a double quote in your string, precede it with a \ like this : ". Do not forget the comma at the end of each line. Separate the 2 strings by =>.
If you’re using Emacs (external link) then it’s easy to change the encoding of a file. Simply open the file, and then type ‘-+C-x RET f+-’ which runs the commandset-buffer-file-coding-system. Now choose utf-8 from the list.
For more information about branches and how to commit, check:
For more information on how to merge strings translated from trunk into previous branches, see:
- OpenTrad Apertium: On-line free software translator, including Catalan-French, French-Catalan, Catalan-English, English-Catalan, among others.
- Dictionary English-Catalan (open source code):
This system is not explained here. You can find more information at:
i18n (Internationalization) > Use database for translation”, and afterwards, clean caches (“Admin > System Administration” > ./templates_c/ Empty).
Then, the link is enabled in the main application menu: Admin > Edit languages, that will bring to an url like:
Then it is necessary to create the translation into the database, for the Catalan language in this example, and tell Tiki to import the text strings already translated at the file language.php. This is performed in some short steps:
- Tell Tiki to create a record for the new language (Catalan) into the database
- Create Language
Shortname: ca (like en)
Longname: Catalan (like English)
- Click in the Create button
- Create Language
- Select the language you want to edit (Catalan) in the drop down menu.
- Select the language to edit: ca
- Click on the button Set
- Then go to the link above called: Im- Export Languages,
that will lead you to to an url like:
- Import the text strings of the language.php in Catalan
- Go to “Import > Select the language to”, and choose Catalan (Catalan,ca) in the drop down menu. ## Click on the button Import.
- Clean cache (“Admin > System Admin” > empty the three sections).
You will see already the interface in your new language (Catalan, in this example).
To edit the text strings, then you need to:
Go to “Admin > Edit languages”. In “Edit or export/import Languages”, select the language you want to edit (do as explained above), and afterwards go to “edit Translations”.
Then you will be able to edit the text strings you want, search any of them, etc. The process is quite intuitive.
Once finished, export the translation to the file language.php (through the link “Import/Export Languages”), and select the language you want to export. It Is necessary that the file and unix folder are writable for the apache user, if in a GNU/Linux or similar environment.
At the end, it is necessary to take this generated file language.php (in ./lang/ca/language.php) and upload it (commit changes) the central repository of code of Tiki at sourceforge.net, through SVN, in case you want that other people can benefit from your improvements (desirable! ).
An example of adding a language
Your strings must be put in a file lang/your_language/custom.php. This file must be readable by the server. The file must have UTF-8 encoding. The format is very close to the format of language.php
<?php $lang_custom = array( "Hello"=>"My Hello", "This is the place to customize your translation"=>":-)", ); $lang = array_merge($lang, $lang_custom); //###trebly: this changed will not be probably necessary for 7.x after 01/18/2011
In Tiki 9.x there is this on the last line:
$lang = $lang_custom + $lang;
A file example is located at lang/fr/custom.php_example.
You can customize any translation with this file by putting exactly the same string on the left as in language.php. The strings that are not in custom.php are still translated as specified in language.php.
You can even change the English strings by using this file. For instance, if you do not like ‘Contact Us’ but prefer ‘Contact Form’ you can have a lang/en/custom.php like this
<?php $lang_custom = array( "Contact Us'=>'Contact Form'", ); $lang = $lang_custom + $lang;
Note : Be aware that any file like “language_*.php” will be also included in the translation.
When you are on a multitiki, you can have a lang/your_language/custom.php and a lang/your_language/your_tikidomain/custom.php
Be sure the file is saved with UTF-8 encoding. If the file is not saved with UTF-8 encoding, a fatal error may result and no Tiki pages will display. Terms/phrases in the custom file will be used in place of the same terms/phrases in the regular language file. (Not just anything can be added to these files, of course. They must be strings specified for translation in the templates, etc.)
- Internationalization Admin
- Interactive Translation of Tiki Interface
- Multilingual Wiki
Alias names for this pageTranslating Tiki interface | Translating interface