diff --git a/Documentation.html b/Documentation.html index 467a599ed..5e07febcc 100644 --- a/Documentation.html +++ b/Documentation.html @@ -1393,6 +1393,12 @@ CREATE DATABASE,ALTER DATABASE,DROP DATABASE HTTP server is placed. +
Always use the current SVN version of your language file.
- For a new language, start from english-utf-8.inc.php. If you
- don't know how to get the SVN version, please ask one of the developers.
-
+
Always use latest Git versoin of po file to translate. You can optionally
+ translate online at our translation
+ server where you can also get latest po files and merge them
+ with your translations. For creating new translation simply use
+ po/phpmyadmin.pot
and generate
+ po/LANG_CODE.po
for your language (you can use
+ msginit -i po/phpmyadmin.pot -l LANG_CODE --no-translator -o po/LANG_CODE.po
+ to do this) or ask on mailing list to add the translation to the web
+ interface.
+
Please note that we try not to use HTML entities like é in
the translations, since we define the right character set in the file.
With HTML entities, the text on JavaScript messages would not
display correctly.
However there are some entities that need to be there, for quotes
- ,non-breakable spaces, ampersands, less than, greater than.
+ ,non-breakable spaces, ampersands, less than, greater than.
+
You can then put your translations, as a zip file to avoid losing special
- characters, on the sourceforge.net translation tracker.
+ characters, on the sourceforge.net translation tracker.
+
It would be a good idea to subscribe to the phpmyadmin-translators mailing - list, because this is where we ask for translations of new messages.
+ list, because this is where we ask for translations of new messages. +$cfg['Error_Handler']['display']
+ configuration directive.__('Some text')
or _ngettext()
function).
+ To translate them, you need to call scripts/update-po
+ script. To use translated messages, call
+ scripts/generate-mo
, which generates binary files read by
+ Gettext.