[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: PDF is broken for <at> notation{} encoding
From: |
Keith OHara |
Subject: |
Re: PDF is broken for <at> notation{} encoding |
Date: |
Tue, 26 May 2015 05:14:53 +0000 (UTC) |
User-agent: |
Loom/3.14 (http://gmane.org/) |
Phil Holmes <mail <at> philholmes.net> writes:
> >> > whenever we use <at> 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".
> >> >
I think you found the correct cause, but I cannot see how it causes this
exact problem. Every macro defined in our include-files *macros.texi is
preceded by an extra line-break. The pdfs on the webpage show the problem.
The change to texinfo was requested here
http://lists.gnu.org/archive/html/bug-texinfo/2015-04/msg00037.html
and made here
http://lists.gnu.org/archive/html/texinfo-commits/2015-04/msg00030.html
but that change makes 'active' in the TeX sense a range of characters
that are non-printing in Latin1.
If I could remember how to run texinfo on a 5-line example file, I might
send a bug-report to texinfo
- PDF is broken for @notation{} encoding, Phil Holmes, 2015/05/25
- Re: PDF is broken for @notation{} encoding, David Kastrup, 2015/05/25
- Re: PDF is broken for @notation{} encoding, James Lowe, 2015/05/26
- Re: PDF is broken for @notation{} encoding, David Kastrup, 2015/05/26
- Re: PDF is broken for @notation{} encoding, James Lowe, 2015/05/26
- Re: PDF is broken for @notation{} encoding, David Kastrup, 2015/05/26
- Re: PDF is broken for @notation{} encoding, Phil Holmes, 2015/05/26
- Re: PDF is broken for @notation{} encoding, David Kastrup, 2015/05/26
- Re: PDF is broken for @notation{} encoding, David Kastrup, 2015/05/26
- Re: PDF is broken for @notation{} encoding, Phil Holmes, 2015/05/26
- Re: PDF is broken for @notation{} encoding, David Kastrup, 2015/05/26