Creating Translations: Difference between revisions

From IHRIS Wiki
No edit summary
No edit summary
Line 1: Line 1:
==translate_create_templates.php==
==translate_create_templates.php==
There is a utility to create [http://en.wikipedia.org/wiki/GNU_gettext .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:
There is a utility to create [http://en.wikipedia.org/wiki/GNU_gettext .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:
Line 24: Line 23:
   [--overwrite-configs=T/F] set to true to always overwrite the translated
   [--overwrite-configs=T/F] set to true to always overwrite the translated
     config.xml
     config.xml
==create_launchpad_upload.php==
Create the tarball needed to upload into launchpad.
It should be the run in the top-level directory '''<DIR>''' of a package. 
Looks for .pot files in translations/templates/
Creates the file translations/templates/lauchpad/templates-'''<PACKAGE>'''.tgz

Revision as of 11:47, 14 July 2009

translate_create_templates.php

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>

<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.
  [--categories=$cat1,$cat2]: The categories to search
    If not specificed we search TEMPLATES
  [--create-configs=T/F]  set to true to always create ./configs
    directory and add to to config.xml if there are translatable strings.
  [--overwrite-configs=T/F] set to true to always overwrite the translated
    config.xml


create_launchpad_upload.php

Create the tarball needed to upload into launchpad.

It should be the run in the top-level directory <DIR> of a package.

Looks for .pot files in translations/templates/

Creates the file translations/templates/lauchpad/templates-<PACKAGE>.tgz