14. NsCDE Localization
Prev |  | Next

## 14. NsCDE Localization

NsCDE implements localization capabilities provided by FVWM and system C library. Directive `LocalePath` in `$NSCDE_DATADIR/fvwm/Main.fvwmconf` is set to look at `$[NSCDE_ROOT]/share/locale;NsCDE:$[NSCDE_ROOT]/share/locale;NsCDE-Subpanels:+`. In other words, whole NsCDE reads it's localization from ".mo" files from `$[NSCDE_ROOT]/share/locale/$LANG/LC_MESSAGES/NsCDE.mo` except subpanels which have their localization in separate mo files in the same directory.

All FvwmScript based applications are reading their own "mo" file from `$[NSCDE_ROOT]/share/locale/$LANG/LC_MESSAGES/NsCDE.mo` which is defined in every program's header with `UseGettext` directive.

All parts of visible text provided by NsCDE have localization ability.

LANGUAGE and LC_MESSAGES environment variables must be set for localization to work correctly. Best way to do this are user's login and profile files, but it can also work with parameters choosen with display manager's popdown menu or similar pre-login mechanism, or as a fallback, `$FVWM_USERDIR/NsCDE.conf` can be used to assign value of the LC_MESSAGES (or LC_ALL) and LANGUAGE commands.

First translated language from original English is Croatian. Other translations are welcome and expected. There are some pitfalls and things which must be observed when translating to the new languages. Existing .po files in "hr" can serve as a template for new translations since just msgstr lines must be replaced and msgid's are already there.

For more information about localization see $PREFIX/share/doc/nscde/README.localization README file which is also provided with software in the root of the unpacked tarball.

Prev |  | Next
13. NsCDE Startup | Home | 15. Initial Configuration