Comment 11 for bug 120907

The problem seems to occur only when a non-English locale is being used (might not be triggered by all locales). I can trigger the abort by running "LC_ALL=pt_BR.utf8 LANGUAGE=pt info" (with the Portuguese language packs installed).

The problem seems to be in command documentation strings like:

msgid "Internally used by \\[universal-argument]"
msgstr "Intern gebruikt door \\[universal-argument]"

Info absolutely expects that the text between the \\[...] refers to an actual function name, which it expects to be able to find and replace according to its needs. If it sees a "function name", but can't look that name up, then it aborts.

For instance, when I'm using pt_BR, I see that it gets translated to ""Ir para o próximo item correspondente do último `\\[pesquisa-índice]' comando". Notice that they translated the function name itself, too (bad idea). This is what's causing problems.

I'm not seeing function-name translation like this upstream, nor does upstream even appear to provide translations for Portuguese; so it looks like a ticket should be opened in the Translations section for this.