|
From: | Phil Holmes |
Subject: | Re: PDF is broken for @notation{} encoding |
Date: | Mon, 25 May 2015 16:08:26 +0100 |
To: "Phil Holmes" <address@hidden> Cc: <address@hidden> Sent: Monday, May 25, 2015 4:00 PM Subject: Re: PDF is broken for @notation{} encoding Phil Holmes <address@hidden> 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
[Prev in Thread] | Current Thread | [Next in Thread] |