mention Info image support in NEWS?

mention Info image support in NEWS?

[Jan Nieuwenhuizen]

Hi,

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.

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

Jan.


--- NEWS	20 apr 2004 11:26:43 +0200	1.937
+++ NEWS	20 apr 2004 11:40:37 +0200	
@@ -374,6 +374,12 @@ If you prefer the old behavior, you can 
 Info files on your system for a string, and builds a menu of the
 possible matches.
 
+*** Images in info pages are supported.
+Info pages show embedded images, in Emacs frames with image support.
+
+Info documentation that includes images, processed with makeinfo
+version 4.7 or newer, compiles to Info pages with embedded images.
+
 +++
 *** The default value for `Info-scroll-prefer-subnodes' is now nil.
 

-- 
Jan Nieuwenhuizen <janneke@gnu.org> | GNU LilyPond - The music typesetter
http://www.xs4all.nl/~jantien       | http://www.lilypond.org

Re: mention Info image support in NEWS?

[Richard Stallman]

    Do you think image support for Info mode should be mentioned in NEWS?

Yes, that is worth mentioning.
Thanks.

Would someone please install that text in NEWS?

Re: mention Info image support in NEWS?

[Juri Linkov]

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/

Info *note xxx* problems (WAS: mention Info image support in NEWS?)

[Jan Nieuwenhuizen]

Juri Linkov writes:

> I installed your additions to NEWS.

Thanks.

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

Yes, I think so too.  I'm glad you like them.

> 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*

I would much prefer fixing the info readers, rather than mangling node
names, if possible.

Jan.

-- 
Jan Nieuwenhuizen <janneke@gnu.org> | GNU LilyPond - The music typesetter
http://www.xs4all.nl/~jantien       | http://www.lilypond.org

Re: Info *note xxx* problems

[Juri Linkov]

Jan Nieuwenhuizen <janneke@gnu.org> writes:
> Juri Linkov writes:
>> 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*
>
> I would much prefer fixing the info readers, rather than mangling node
> names, if possible.

I don't see how Info readers could be fixed: the `*note ' text
is used for cross-references.

Fortunately, you can use emphasis other than asterisks by replacing
the @string argument of the @table by any argument which doesn't put
asterisks around the text: @emph, @asis, @code, @samp, @var, @option...

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

Re: Info *note xxx* problems

[Jan Nieuwenhuizen]

Juri Linkov writes:

> I don't see how Info readers could be fixed: the `*note ' text
> is used for cross-references.
>
> Fortunately, you can use emphasis other than asterisks by replacing
> the @string argument of the @table by any argument which doesn't put
> asterisks around the text: @emph, @asis, @code, @samp, @var, @option...

Hmm, then I think we could/should do that, but, I also think that if
there is consensus that this cannot be fixed by info readers, makeinfo
should not output it that way.

It should maybe check the string it puts asterisks around, and replace
spaces by underscores, or use other emphasis marks than asterisks if
there' a loose word called `note' in it.

Jan.

-- 
Jan Nieuwenhuizen <janneke@gnu.org> | GNU LilyPond - The music typesetter
http://www.xs4all.nl/~jantien       | http://www.lilypond.org

Re: Info *note xxx* problems

[Karl Berry]

    there is consensus that this cannot be fixed by info readers, 

Well, I want to develop an alternative xref scheme that can support any
characters in node/xref names.  But even when/if we implement such a
thing, it would not help here, since I really doubt you or anyone wants
to generate Info files which can only be read by the very latest
readers.

So, as you say ... :

    makeinfo should not output it that way.

Agreed.

Re: Info *note xxx* problems

[Jan Nieuwenhuizen]

Karl Berry writes:

>     makeinfo should not output it that way.
>
> Agreed.

The question is what to do with: @strong{note head}.  There are
several solutions

    *note_head*, *note*head*, _note head_, * note head *

Does this need further discussion (ie, should we take this thread to
texinfo-*?), or this such an easy thing that `cvs up' tomorrow will
fix it for me :-)

Jan.

-- 
Jan Nieuwenhuizen <janneke@gnu.org> | GNU LilyPond - The music typesetter
http://www.xs4all.nl/~jantien       | http://www.lilypond.org

Re: Info *note xxx* problems

[Juri Linkov]

Jan Nieuwenhuizen <janneke@gnu.org> writes:
> The question is what to do with: @strong{note head}.  There are
> several solutions
>
>     *note_head*, *note*head*, _note head_, * note head *
>
> Does this need further discussion (ie, should we take this thread to
> texinfo-*?), or this such an easy thing that `cvs up' tomorrow will
> fix it for me :-)

Not `cvs up emacs', but `cvs up texinfo' ;-)

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