Re: internationalization

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Dumas Patrice wrote:

|Hi,
|
|I implemented your ideas about a parser for strings in code and things like
|%{var} in text strings, and I put the relevant code in a new command
|manage_i18n.pl.


:)

|Currently the translations.pl file is included, but if I don't have
negative
|feedback about putting T2H_LANGUAGES in the Texi2HTML::Config namespace I
|will also implement the search in the i18n directory based on the language
|and change Makefile.am such that i18n files are installed at the right
|place.


I don't think that I have any objection to moving i18n strings to the
config namespace, though perhaps the user and site config could be moved
into ~/.texi2html/conf and /etc/texi2html/conf and handling added for
~/.texi2html/i18n and /etc/texi2html/i18n directories for the
translation overrides?  That should answer the efficiency and clutter
issues.  Most of the code that sources the installed i18n/* files should
be reusable in config then as well.

~/.texi2htmlrc and /etc/texi2htmlrc could be continued to be sourced for
a few releases with deprecation warnings.

|I still have a question. I currently call the file holding the english
strings
|'template'. I am wondering if it shouldn't simply be called 'en'.
Thoughts ?


I'm not sure about this, as long as the file isn't installed.  The
script does not need to source the `en' file to determine english
strings and thus I think no `en' file should be installed by default.
The `i18n/template' in the source distribution would hopefully jump out
at contributors as a starting point for translations.  If we were to
install a file for english "translations", i.e. one that allowed an
installer to change the english text, then that should definately be
called `en', however.

Derek

- --
~                *8^)

Email: [email protected]

Get CVS support at <http://ximbiot.com>!
- --
I will not waste chalk.
I will not waste chalk.
I will not waste chalk...

~          - Bart Simpson on chalkboard, _The Simpsons_
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.0.7 (GNU/Linux)
Comment: Using GnuPG with Netscape - http://enigmail.mozdev.org

iD8DBQE/YfdWLD1OTBfyMaQRAoEYAJ9hXiUp+BII1So7fqMEihbt0EPIuwCfbGP4
EF07zUAA7eoixxFBCikcl1s=
=AqYK
-----END PGP SIGNATURE-----