unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Juri Linkov <juri@jurta.org>
Cc: emacs-devel@gnu.org
Subject: Re: mention Info image support in NEWS?
Date: Thu, 22 Apr 2004 03:06:17 +0300	[thread overview]
Message-ID: <873c6xaq3b.fsf@mail.jurta.org> (raw)
In-Reply-To: <878ygrrnjx.fsf@peder.flower> (Jan Nieuwenhuizen's message of "Tue, 20 Apr 2004 11:44:34 +0200")

Jan Nieuwenhuizen <janneke@gnu.org> writes:
> Do you think image support for Info mode should be mentioned in NEWS?
>
> If so, I've added a suggestion below, which you may want to
> reword/rephrase.

I installed your additions to NEWS.

> For the curious, the GNU LilyPond 2.2.0 info pages contain loads of
> images.

I'd say GNU LilyPond Info pages with images are very nice looking!

BTW, do you remember I once reported about problems in LilyPond
Info pages?  One problem was with trailing whitespace in some Info
nodes names.  This is easy to fix, but other problem was in the LilyPond
music glossary with the word `*note*' emphasized by asterisks around
it.  This is already fixed in Emacs Info reader to skip the `*note'
text without whitespace after it, but there are still other places in
the LilyPond music glossary which are interpreted as cross references:

*note head*
*note value*

As one solution you can replace a space by some other non-space character,
for example:

*note_head*
*note-value*

-- 
Juri Linkov
http://www.jurta.org/emacs/

  parent reply	other threads:[~2004-04-22  0:06 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-04-20  9:44 mention Info image support in NEWS? Jan Nieuwenhuizen
2004-04-21 18:58 ` Richard Stallman
2004-04-22  0:06 ` Juri Linkov [this message]
2004-04-23  9:30   ` Info *note xxx* problems (WAS: mention Info image support in NEWS?) Jan Nieuwenhuizen
2004-04-25  4:34     ` Info *note xxx* problems Juri Linkov
2004-04-25 17:28       ` Jan Nieuwenhuizen
2004-04-25 21:29         ` Karl Berry
2004-04-25 22:04           ` Jan Nieuwenhuizen
2004-04-26  4:48             ` Juri Linkov

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=873c6xaq3b.fsf@mail.jurta.org \
    --to=juri@jurta.org \
    --cc=emacs-devel@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 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).