Creating Translations: Difference between revisions
From IHRIS Wiki
No edit summary |
No edit summary |
||
Line 7: | Line 7: | ||
Usage: translate_create_templates.php | Usage: translate_create_templates.php | ||
[--template_dir=$template_dir]: The directory to store .pot template files in | [--template_dir=$template_dir]: The directory to store .pot template files in | ||
If not set, we use ./translations/templates | |||
[--remove-strings=T/F] set to true to always remove the string from a module's .pot | [--remove-strings=T/F] set to true to always remove the string from a module's .pot | ||
which are no longer present in the module | |||
[--modules=$module1,$module2..$moduleN]: The module(s) for which we wish to operate on | [--modules=$module1,$module2..$moduleN]: The module(s) for which we wish to operate on | ||
If not specified, it uses every valid module | If not specified, it uses every valid module |
Revision as of 09:34, 14 July 2009
There is a utility to create .POT translation template files to upload to launchpad. The utility creates a .POT file for each module in a package (such as I2CE, ihris-common, ihris-manage, etc) and is found in the I2CE package under:
i2ce/tools/translate_create_templates.php
It should be the run in the top-level directory <DIR> of a package. The usage as of version 4.0.0:
cd <DIR> php <I2CE_DIRECTORY>/tools/translate_create_templates.php --help Usage: translate_create_templates.php [--template_dir=$template_dir]: The directory to store .pot template files in If not set, we use ./translations/templates [--remove-strings=T/F] set to true to always remove the string from a module's .pot which are no longer present in the module [--modules=$module1,$module2..$moduleN]: The module(s) for which we wish to operate on If not specified, it uses every valid module [--search_dirs=$dir1,$dir2]: Set the search directories for modules If not specified, we search <DIR>,<DIR>/sites/* [--limit_search=T/F]: Limit the module search results of found sub-modules of a top-level Defaults to T.