[ < ] [ > ]   [ << ] [ Up ] [ >> ]         [Top] [Contents] [Index] [ ? ]

7.5.8 Internationalizing Options

Normally, AutoOpts produces usage text that is difficult to translate. It is pieced together on the fly using words and phrases scattered around here and there, piecing together toe document. This does not translate well.

Incorporated into this package are some ways around the problem. First, you should specify the full-usage and short-usage program attributes (see section Program Description Attributes). This will enable your translators to translate the usage text as a whole.

Your translators will also be able to translate long option names. The option name translations will then become the names searched for both on the command line and in configuration files. However, it will not affect the names of environment variable names used to configure your program.

If it is considered desireable to keep configuration files in the C locale, then several macros are available to suppress or delay the translations of option names at run time. These are all disabled if ENABLE_NLS is not defined at compile time or if no-xlate has been set to the value anything. These macros must be invoked before the first invocation of optionProcess.

OPT_NO_XLAT_CFG_NAMES;
OPT_XLAT_CFG_NAMES;

Disable (or enable) the translations of option names for configuration files. If you enable translation for config files, then they will be translated for command line options.

OPT_NO_XLAT_OPT_NAMES;
OPT_XLAT_OPT_NAMES;

Disable (or enable) the translations of option names for command line processing. If you disable the translation for command line processing, you will also disable it for configuration file processing. Once translated, the option names will remain translated.


[ < ] [ > ]   [ << ] [ Up ] [ >> ]         [Top] [Contents] [Index] [ ? ]

This document was generated by Bruce Korb on October 16, 2013 using texi2html 1.82.