pl_PL, de_DE, ja_jP and ru_RU translations are now merged
into ZF-Commons/ZfcUser master branch :-), (*1)
Translation continues there., (*2)
WebsafeZfModZfcUserI18n
, (*3)
Multi language pack module for the ZF-Commons/ZfcUser module., (*4)
Currently contains following languages/locales/translations:, (*5)
Each translation is located in a separate repository (linked above).
This module (WebsafeZfModZfcUserI18n) simply collects all .po
files from
coresponding single-language repositories during the build process., (*6)
For details about the build process see this repositories
composer.json
-> require-dev
and scripts/build/build.sh
., (*7)
Installation
Chdir into Your projects root directory (where composer.json
resides)
and run the following command:, (*8)
~~~~ bash
composer require websafe/zf-mod-zfc-user-i18n:dev-master --prefer-dist, (*9)
Configuration
--------------------------------------------------------------------------------
### Enabling the multi language pack module in Your ZF2 application
In `config/application.conf.php` add `WebsafeZfModZfcUserI18n` after
`ZfcUser`:
~~~~ php
<?php
return array(
'modules' => array(
// ...
'ZfcUser',
'WebsafeZfModZfcUserI18n',
// ...
),
// ...
);
Set the locale
This step is not really required - it depends on how the locale is initialized
in Your application., (*10)
In config/global.conf
or module/Application/config/module.config.php
add:, (*11)
~~~~ php
// ...
'translator' => array(
'locale' => 'AVAILABLE_LOCALE',
// ...
),
// ..., (*12)
Replace `AVAILABLE_LOCALE` with `de_DE`, `ja_JP` or `pl_PL`. See list of
available translations at the [top of this README].
Updating
--------------------------------------------------------------------------------
Chdir into projects root directory (where `composer.json` resides)
and run the following commands:
~~~~ bash
rm -rf ~/.composer/cache/files/websafe/zf-mod-zfc-user-i18n*
composer update websafe/zf-mod-zfc-user-i18n
The rm -rf ...
part is needed when the module was installed with
--prefer-dist
. Without cleaning up the cache before installing - Composer
will probably stick to a cached version., (*13)
Contributing
If You want to help with translation, just:, (*14)
and after all send a pull request., (*15)
When You're not familiar with editing .po
files - simply:, (*16)
If You want to add a new language:, (*17)
-
report an issue and I will create a repo for Your language, compatible
with existing single-language module repos.
Compiling .po files to .mo files
There's no need to compile .po
files after the installation or before sending
pull requests, but if you modify the .po
file locally, recompile it by
executing the following command in this modules root directory:, (*18)
~~~~ bash
msgfmt -cv -o language/de_DE.mo language/de_DE.po
~~~~, (*19)