Re: Problems with human language translations

    Even worse, my "solution" only works for the latest release 4.8 but
    not for the CVS version.  :-(

Perhaps it is a matter of where the respective programs are looking for
the translated messages (e.g., configure options).  Maybe strace or
something would help debug it?

    LANG because @documentlanguage is not interpreted correctly.
    
I'm confused.  @documentlanguage has nothing to do how program messages
are translated, which is all we're talking about here, right?  Just like
cat or cp or any other program.  As far as I know, makeinfo uses just
the same code as all those others.

The problem with @documentlanguage is that makeinfo should be smart
enough to distinguish text used in the document (like the "see" from
@pxref) from the program messages (like --help output).  But supporting
two different languages like that is, as you say, not trivial.

    By the way, in po/POTRANCE.in two files are missing.  This makes it

Oops, thanks.
_______________________________________________
Texinfo home page: http://www.gnu.org/software/texinfo/
[email protected]
http://ff0.org/mailman/listinfo/texinfo-pretest