Re: internationalization

> However I agree that it makes sense to source files conditionnaly on a 
> language. In that case, if a user wants to do different formatting based
> on the languages he will be able to do so. I think that Karl Heinz Marbraise 
> proposed something along that in his IDEAS file. In fact I think that the user
> should put in this file everything that is not translated strings because
> translated strings are allready taken into account. Of course your point about
> efficiency still holds, that is the user could put relevant translations in 
> the i18n files only to avoid having a too big  /etc/texi2htmlrc or 
> ~/.texi2htmlrc with all the translations.

There is an error here: the configuration and the internationalization are
not in the same namespace. To overcome that issue, I propose putting
the languages hash in the config namespace. I think that is will simplify the
whole and solve other issues (like $T2H_LANGUAGES being global).

Pat