On 12/4/05, Ramkumar R <[EMAIL PROTECTED]> wrote:
e17's built in modules don't do any bindtextdomain calls, and afaik the only 3rd party module that has been set up with i18n support is the one that I did recently as an experiment (http://edevelop.org/node/1860).
It uses a var in config.h to specify the locale path.
David
> modules can use gettext DOMAINS to load a different domain for their use, but
> they still suffer fromt he problem of possibly haveing some languages already
> supported by teh system packages, but the user wanting to edxtend language
> support by adding more translations but not having root access.
So, do they currently use E's locale search path? Should we be
exposing a e_intl_get_locale_path(), so that modules can do a
bindtextdomain(MODULENAME, e_intl_get_locale_path()).
e17's built in modules don't do any bindtextdomain calls, and afaik the only 3rd party module that has been set up with i18n support is the one that I did recently as an experiment (http://edevelop.org/node/1860).
It uses a var in config.h to specify the locale path.
David
