lilypond-devel
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [lilypond-book] @format environments


From: Michael Käppler
Subject: Re: [lilypond-book] @format environments
Date: Thu, 9 Jul 2020 13:45:28 +0200
User-agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:68.0) Gecko/20100101 Thunderbird/68.10.0


So I would vote to make

@noindent
[Version string if needed]
@verbatim
...
@end verbatim
This is OK with me.  Thanks for working on this!
Hmm, not so simple as I thought at first.
The version string should be printed in typewriter, like
the code that immediately follows in the @verbatim environment.
If we use

@code{\version @w{"@version{}"}}

it will be put in quotes for Info output, which is not what we want.

With
@verbatim
\version @w ...
@end verbatim

the @version macro won't be expanded.

The following

@format
@t{\version @w...}
@end format

does work well for PDF and for Info output, but not for HTML with
texi2html-1.82, because @format
environments are indented there, the following @verbatim block is not.
Texi2any from texinfo-6.5
behaves differently again, not indenting the @format blocks.

*Ugh*

The only solution that works for PDF, Info and HTML actually seems to be:

@noindent
@t{\version @w....}
@verbatim
foo
@end verbatim

This is hacky, too, because IIUC '@noindent' is designed to be used
*after* environments
like @quotation, @example, etc. to prevent the following paragraph from
being indented.

What strikes me the most is that 'addversion' is used only three times
throughout the
whole documentation, and these three occurrences are all in the LM,
fundamental.itely

What is the reason that the version string is mentioned for these
particular snippets and nowhere else?

Cheers,
Michael




     Werner




reply via email to

[Prev in Thread] Current Thread [Next in Thread]