From: Juri Linkov <juri@jurta.org>
Cc: emacs-devel@gnu.org, janneke@gnu.org
Subject: Re: [PATCH] ignoring Info extensions
Date: Thu, 01 Apr 2004 19:33:15 +0300 [thread overview]
Message-ID: <87ad1v8xox.fsf@mail.jurta.org> (raw)
In-Reply-To: <200404010201.i3121XM31201@f7.net> (Karl Berry's message of "Wed, 31 Mar 2004 21:01:33 -0500")
karl@freefriends.org (Karl Berry) writes:
> I will change makeinfo to make this an error, or at least a warning,
> and remove such trailing whitespace so it doesn't get into the output.
I think a warning is ok. But moreover, I noticed other places
in Info manuals that cause problems for Info readers:
By funny coincidence, the LilyPond music glossary contains words
`*note*' emphasized by asterisks around them, where the word `note'
means a symbol for a musical tone. But it is interpreted by the Info
reader as an Info reference, and if Info-hide-note-references=t it is
displayed as `See *'. Even though the Texinfo manual warns about
using asterisks with the word `note', it suggests to replace it
by a phrase such as *Please notice* which is inappropriate here.
Perhaps makeinfo should produce a warning about it, but still
I don't see how the author would fix this problem.
There are many other Info manuals that have a string `*Note:'
which is treated incorrectly by Info readers. What do you think
about interpreting a `*Note' as an Info reference only if it
has whitespace around it, i.e. if it matches the following regexp?
[ \t\n]+\*[Nn]ote[ \t\n]+
It would also solve the problem of incorrect interpreting of
the quoted ``*Note:'' string such as in the following Info nodes:
(info "(info)Cross-refs")
(info "(info-stnd)Parts of an Xref")
(info "(texinfo)Cross Reference Commands")
--
Juri Linkov
http://www.jurta.org/emacs/
next prev parent reply other threads:[~2004-04-01 16:33 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-03-11 19:47 resend: [PATCH] ignoring Info extensions Jan Nieuwenhuizen
2004-03-14 7:39 ` Eli Zaretskii
2004-03-14 12:53 ` Jan Nieuwenhuizen
2004-03-29 7:57 ` Jan Nieuwenhuizen
2004-03-31 20:56 ` Juri Linkov
2004-04-01 2:01 ` Karl Berry
2004-04-01 5:53 ` Eli Zaretskii
2004-04-01 16:33 ` Juri Linkov [this message]
2004-04-01 19:53 ` Eli Zaretskii
2004-04-02 3:27 ` Juri Linkov
2004-04-02 7:47 ` Eli Zaretskii
2004-04-03 1:30 ` Richard Stallman
2004-04-02 1:50 ` Karl Berry
2004-04-02 3:32 ` Juri Linkov
2004-04-02 14:16 ` Karl Berry
2004-04-02 18:19 ` Juri Linkov
2004-04-02 19:28 ` Eli Zaretskii
2004-04-02 21:38 ` Juri Linkov
2004-04-03 0:19 ` Karl Berry
2004-04-02 19:29 ` Eli Zaretskii
2004-04-02 7:43 ` Eli Zaretskii
2004-04-02 21:47 ` Juri Linkov
2004-04-03 1:25 ` Karl Berry
2004-04-03 4:56 ` Juri Linkov
2004-04-03 9:05 ` Eli Zaretskii
2004-04-03 23:39 ` Richard Stallman
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87ad1v8xox.fsf@mail.jurta.org \
--to=juri@jurta.org \
--cc=emacs-devel@gnu.org \
--cc=janneke@gnu.org \
/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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.