Creating Translations: Difference between revisions
From IHRIS Wiki
No edit summary |
No edit summary |
||
Line 11: | Line 11: | ||
If not specified, we search '''<DIR>''','''<DIR>'''/sites/* | 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 | [--limit_search=T/F]: Limit the module search results of found sub-modules of a top-level | ||
module to those that are | module to those that are real subdirectories of top-level's given directory | ||
If not specified, we search '''<DIR>''','''<DIR>'''/sites/* | If not specified, we search '''<DIR>''','''<DIR>'''/sites/* |
Revision as of 09:19, 14 July 2009
There is a utility to create [1] 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 Usage: translate_create_templates.php [--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 module to those that are real subdirectories of top-level's given directory If not specified, we search <DIR>,<DIR>/sites/*