From: Eli Zaretskii <eliz@gnu.org>
To: "Vincent Belaïche" <Vincent.b.1@hotmail.fr>
Cc: pertusus@free.fr, bug-texinfo@gnu.org, gavinsmith0123@gmail.com,
18308@debbugs.gnu.org, karl@freefriends.org
Subject: bug#18308: 24.4.50; Info viewer cannot follow menu entry for '(texinfo) @- @hyphenation'
Date: Fri, 22 Aug 2014 16:36:26 +0300 [thread overview]
Message-ID: <83ppfsmysl.fsf__40324.9970208437$1408715064$gmane$org@gnu.org> (raw)
In-Reply-To: <80r4083cg8.fsf@gmail.com>
> From: Vincent Belaïche <Vincent.b.1@hotmail.fr>
> Cc: 18308@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
> accross a line in the case of a note.
>
> - info viewer must handle node name split accross lines, but it does not
> need to make multiblank reduction in other-cases
>
> Now, if the above is agreable, then in the case of our problem this
> would imply that when texi2any meets that kind of menu entry
>
> * NODE NAME:: SOME TITLE
>
> It must convert it to within the info file:
>
> * NODE NAME: NODE NAME. SOME TITLE
Or it should remove the extra blanks, i.e. produce this:
* NODE NAME:: SOME TITLE
Or it could emit a warning, or even error out.
IOW, I see no reason to silently tolerate such cases. They are surely
unintended.
> Eli:
> 1) do you agree on my re-caping and suggestion ?
Almost, see above.
> 2) do you think that all the same, robustifying the info viewer in the
> case of menu entry has some benefit --- after all this allows:
> 2.1) to cope with job done by earlier versions of makeinfo in this
> corner case
> 2.2) to have very slightly smaller info file still in this corner case
I'm on the fence about this.
next prev parent reply other threads:[~2014-08-22 13:36 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-08-21 8:45 bug#18308: 24.4.50; Info viewer cannot follow menu entry for '(texinfo) @- @hyphenation' Vincent Belaïche
2014-08-21 14:12 ` Eli Zaretskii
2014-08-21 16:30 ` Vincent Belaïche
2014-08-21 22:23 ` Vincent Belaïche
2014-08-22 6:36 ` Eli Zaretskii
2014-08-22 17:17 ` Richard Stallman
2014-08-22 20:12 ` Gavin Smith
2014-08-22 20:57 ` Eli Zaretskii
2014-08-23 19:44 ` Richard Stallman
2014-08-24 14:05 ` Stefan Monnier
2014-08-24 23:41 ` Richard Stallman
2014-08-25 15:05 ` Stefan Monnier
2014-08-25 19:11 ` Richard Stallman
2014-08-25 2:07 ` Tom Tromey
2014-08-25 19:10 ` Richard Stallman
2014-08-22 17:56 ` Gavin Smith
2014-08-26 15:58 ` Glenn Morris
2014-08-22 13:01 ` Vincent Belaïche
2014-08-22 13:36 ` Eli Zaretskii [this message]
2014-08-22 22:04 ` Vincent Belaïche
2014-08-22 22:09 ` Glenn Morris
2014-08-31 22:37 ` Gavin Smith
[not found] ` <CAKPWYQ2r6y7spGnwU+34BQDMYRikEGoROP0BAJ5mLR0g4d7jTg@mail.gmail.com>
2014-09-01 19:40 ` Vincent Belaïche
2014-09-01 21:37 ` Gavin Smith
2014-09-01 21:53 ` Karl Berry
[not found] ` <201409012153.s81LrtTi021549@freefriends.org>
2014-09-02 21:44 ` Vincent Belaïche
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='83ppfsmysl.fsf__40324.9970208437$1408715064$gmane$org@gnu.org' \
--to=eliz@gnu.org \
--cc=18308@debbugs.gnu.org \
--cc=Vincent.b.1@hotmail.fr \
--cc=bug-texinfo@gnu.org \
--cc=gavinsmith0123@gmail.com \
--cc=karl@freefriends.org \
--cc=pertusus@free.fr \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).