[2192] Latest edit on
2010-12-26 20:32:24 by
BrianKoontz [Added note about multibyte errors]
Additions:
If you are receiving multibyte errors when running this command, you will most likely have to manually edit the .po file, specifically the following line:
"Content-Type: text/plain; charset=UTF-8\n"
Additions:
Some gettext notes from Pablo Hoch's blog
Deletions:
Some gettext notes from Pablo Hoch's Blog
Additions:
This document describes a proposal to implement gettext for all translation strings in
WikkaWiki, starting with Wikka 1.3. Note that this is only a proposal, so this document can and probably will be modified several times. Should the dev team decide to adopt gettext as the localization standard for Wikka, this page will be renamed to indicate this.
SVN checkout: svn co
https://wush.net/svn/wikka/branches/1.3_gettext
Deletions:
This document describes a proposal to implement gettext for all translation strings in
WikkaWiki, starting with Wikka 1.3. Note that this is only a proposal, so this document can and probably will be modified several times. Should the dev team decide to adopt gettext as the localization standard for Wikka, this page will be renamed to indicate this.
Additions:
Any time new translation macros (of the form T_(...)) are added to the source code, a new gettext template file must be generated. There are several different gettext utilities that can be used to generate this file. GNU gettext command-line utility examples are used in this document, so we will be using the gettext command from the Wikka top-level directory:
find ./ -name '*.php' | xargs xgettext -L PHP --force-po -kT_ -o locale/po/messages.pot
Creating language-specific template (.po) files
If one does not already exist, create a new directory structure under locale/ using BCP-47 language tags (validator). For instance:
mkdir -p locale/fr_CH/LC_MESSAGES
The GNU gettext command msginit can then be invoked to copy the messages.pot template file for use with the language to be translated:
msginit --locale fr_CH --input locale/po/messages.pot --output-file locale/fr_CH/LC_MESSAGES/fr_CH.po
Creating translations
Several utilities exist that can be used to modify .po files. Some of the available utilities are listed here. The file can also be modified manually in a text editor.
[More info needed? I really don't want this to become a translation how-to!]
Compiling translations (.po->.mo files)
Once translations in the .po file are complete, these must be compiled into a binary format for use by the PHP-gettext libraries. The GNU gettext msgfmt can be used here:
msgfmt -o locale/fr_CH/LC_MESSAGES/fr_CH.mo locale/fr_CH/LC_MESSAGES/fr_CH.po
Merging translations
[TBD]
Deletions:
Any time new translation macros (of the form T_(...)) are added to the source code, a new gettext template file must be generated. There are several different gettext utilities that can be used to generate this file.
Additions:
Defines that were used as translation strings in lang/en/en.inc.php and related language files were replaced in source files with their English equivalents using a Perl script. The gettext macro used for all Wikka translation strings is T_ (the reason for this is that _ is already used by the installer). For instance, the following define:
if(!defined('FOOTER_PAGE_EDIT_LINK_DESC')) define('FOOTER_PAGE_EDIT_LINK_DESC', 'Edit page');
was replaced in the header.php source code file with the following:
T_('Edit page')
A file called localization.php is used in the Wikka top-level directory to configure PHP-gettext. This file should normally not require modification by the end-user. The file itself is invoked from within wikka.php via the include_once directive.
Locale directory structure
The locale directory is structured as follows:
locale/
locale/po <--contains the generic template file; must be copied to lang-specific directories for translation
locale/po/messages.pot <--generic template file
locale/en_US <--locale-specific
locale/en_US/LC_MESSAGES <--holds lang-specific translations
locale/en_US/LC_MESSAGES/en_US.po <--lang-specific template file, usually created by msginit
locale/en_US/LC_MESSAGES/en_US.mo <--compiled translation file, usually created by msgfmt
locale/de_DE
locale/de_DE/LC_MESSAGES
etc...
Generating the gettext template (.pot) file
Any time new translation macros (of the form T_(...)) are added to the source code, a new gettext template file must be generated. There are several different gettext utilities that can be used to generate this file.
Additions:
Implementation Notes
The PHP-gettext standalone library is used to implement gettext in Wikka. This eliminates the need for a Wikka administrator to ensure their version of PHP has gettext support compiled in. PHP-gettext requires no external libraries and only a minimal amount of configuration. It is licensed under GPLv2.
In Wikka 1.3, the PHP-gettext version 1.09 libraries are located in 3rdparty/core/php-gettext. No modifications are necessary when installing from the PHP-gettext version 1.09 release package.
Testing was conducted on a Windows 7 laptop running the excellent WampServer 2.0 package (Apache 2.2.11, PHP 5.2.11, and MySQL 5.1.36) using GNU gettext 0.17 tools under Cygwin.
[2186] The oldest known version of this page was created on
2010-11-07 21:33:31 by
BrianKoontz [Initial draft]
Localization proposal using gettext
This document describes a proposal to implement gettext for all translation strings in
WikkaWiki, starting with Wikka 1.3. Note that this is only a proposal, so this document can and probably will be modified several times. Should the dev team decide to adopt gettext as the localization standard for Wikka, this page will be renamed to indicate this.
References
The following references were used to develop the initial gettext implementation using the Wikka 1.3 development branch:
"Translating WordPress"
PHP-gettext dev blog (Danilo Segan)
PHP-gettext repository
GNU gettext manual
Some gettext notes from Pablo Hoch's Blog
