Re: bug#18308: 24.4.50; Info viewer cannot follow menu entry for '(texinfo) @- @hyphenation'

[Gavin Smith]

On Mon, Sep 1, 2014 at 8:40 PM, Vincent Belaïche <address@hidden> wrote:
>> Having translated node names isn't as important because there would be
>> translated headers in the contents of files/nodes saying what section
>> we're in. The main use would be the status bar in a browser giving the
>> current node, and pointers or references to other nodes. I understand
>> it is not ideal to read a cross-reference in another language. Maybe
>> anchors with translated node names could be used instead? That would
>> work for everything (cross-references, pointers) apart from the node
>> name that is displayed in a status bar. Maybe makeinfo would have to
>> be modified to recognize that a menu in a node using anchor names is
>> referring to the child nodes properly.
>
> Menus are precisely the only place where you don't need any change in 
> Texinfo, as you can do:
>
> * Translated node name: true node name. Some description
>
> @node true node name
>
> and the viewer is supposed to show only "Translated node name".
>

I can imagine cases where a menu label is something other than the
node name, for example if the document author wants to give a more
extended description of what the node is about. Anyway, names of
targets are not usually hidden (in the standalone Info browser, at
least).

> What I was meaning is that the viewer should be configurable to show either 
> the "node path" with translated names or true names.
>
> In the case of nodes that are not referred by any menu, like the top node, or 
> node accessed only by cross reference, there aren't currently any provision 
> in Texinfo to povide a node name translation. That could be some command 
> @localenodename to give that translation inside the node.

Something like this could be done by treating an anchor as a synonym
for a node if it refers to byte 0 of the node. If someone selected or
followed a reference to such an anchor, its name could be displayed
instead of the node. There would still be the problem of how makeinfo
would do "implicit pointer creation" with the right node names.