...@debbugs.gnu.org; bug-texinfo@gnu.org
Subject: RE: bug#18308: 24.4.50; Info viewer cannot follow menu entry for
'(texinfo) @- @hyphenation'
use exactly the same node names whatever the language, so that the
same link can be used, and when the manual is compiled to multifile
HTML, you have the same
Answers inserted below...
Date: Sun, 31 Aug 2014 23:37:06 +0100
Subject: Re: bug#18308: 24.4.50; Info viewer cannot follow menu entry for
'(texinfo) @- @hyphenation'
From: gavinsmith0...@gmail.com
To: vincent@hotmail.fr
CC: 18...@debbugs.gnu.org
On Mon, Sep 1, 2014 at 8:40 PM, Vincent Belaïche vincent@hotmail.fr 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
use exactly the same node names whatever the language, so that the
same link can be used, and when the manual is compiled to multifile
HTML, you have the same file tree whatever the language. Seems
Currently the usual practice is that a translated document is just
(adding bug-texinfo)
On Fri, Aug 22, 2014 at 11:04 PM, Vincent Belaïche
vincent@hotmail.fr wrote:
Finally, as an EMACS user, it would be more important to me
* if docstring could be written in a sort of texinfo-light format (when
you create a package or anything you first do docstring,
From: Vincent Belaïche vincent@hotmail.fr
Cc: 18...@debbugs.gnu.org, Texinfo bug-texinfo@gnu.org
Date: Fri, 22 Aug 2014 15:01:43 +0200
- texi2any must collapse multiple blanks in node names *everywhere*, but
it is still allowed to break and indent a node name containing a blank
2014 09:36:14 +0300
From: e...@gnu.org
Subject: Re: bug#18308: 24.4.50; Info viewer cannot follow menu entry for
'(texinfo) @- @hyphenation'
To: vincent@hotmail.fr
CC: gavinsmith0...@gmail.com; 18...@debbugs.gnu.org
[...]
I a nutshell, there are cases of node references where the info
