----- Original Message -----
From: "Phil Holmes" <[email protected]>
To: "David Kastrup" <[email protected]>
Cc: <[email protected]>
Sent: Monday, May 25, 2015 4:08 PM
Subject: Re: PDF is broken for @notation{} encoding
----- Original Message -----
From: "David Kastrup" <[email protected]>
To: "Phil Holmes" <[email protected]>
Cc: <[email protected]>
Sent: Monday, May 25, 2015 4:00 PM
Subject: Re: PDF is broken for @notation{} encoding
Phil Holmes <[email protected]> writes:
> Look at page 22 of the most recent PDF of Learning, and you'll see that
> whenever we use @notation{text}, then there is a paragraph break before
> the "text". It took a while to figure out the guilty commit, but it is
> 9f3c7711bb73baf3aea8502227fb5fd2d2851753: "update texinfo.tex from
> upstream".
>
> Anyone know what's happening here?
Are you sure about that? That commit looks pretty harmless as opposed
to some others in the series
I was surprised, too. I repeated the test, with changes made to the
source of the docs between each try, and it consistently showed that this
was the guilty party.
I can try again, but it was consistent. James might want to try?
--
Phil Holmes
99.9% certain that the commit I identified is the problem. I've nuked
build, made lilypond, made docs for the earlier commit
(stem-tremolo-style.ly: Minor doc improvement) and then repeated the
deletion of build for and make for this one. I attach images of the PDF
pages, with the commit title above one of the offending sections, to
illustrate.
--
Phil Holmes
_______________________________________________
lilypond-devel mailing list
[email protected]
https://lists.gnu.org/mailman/listinfo/lilypond-devel
