From: Mans Rullgard <mans@mansr.com>
To: sox-devel@lists.sourceforge.net
Cc: Kevin Conder <kwconder@yahoo.com>
Subject: [PATCH 2/2] Fix Bug #261: absurd docs bug - PDF is doubled
Date: Fri, 27 Apr 2018 14:16:45 +0100 [thread overview]
Message-ID: <20180427131645.26367-2-mans@mansr.com> (raw)
In-Reply-To: <20180427131645.26367-1-mans@mansr.com>
From: Kevin Conder <kwconder@yahoo.com>
The problem is when any PDF is created, the result is two duplicate
documents concatenated together.
Solution: Add the "--no-toc-relocation" parameter to pdfroff as a
work-around.
[ew: format + edit commit message, add references:
https://bugs.debian.org/538326
http://lists.gnu.org/archive/html/groff/2009-08/msg00028.html
]
Reviewed-by: Eric Wong <normalperson@yhbt.net>
---
Makefile.am | 6 +++---
1 file changed, 3 insertions(+), 3 deletions(-)
diff --git a/Makefile.am b/Makefile.am
index fefa1869a632..35d06abdc6e7 100644
--- a/Makefile.am
+++ b/Makefile.am
@@ -39,11 +39,11 @@ txt: $(DOCTXT)
# Rule for making PDF man pages
.1.pdf:
- pdfroff -t -man -Tps $< > $@
+ pdfroff -t -man --no-toc-relocation -Tps $< > $@
.3.pdf:
- pdfroff -t -man -Tps $< > $@
+ pdfroff -t -man --no-toc-relocation -Tps $< > $@
.7.pdf:
- pdfroff -t -man -Tps $< > $@
+ pdfroff -t -man --no-toc-relocation -Tps $< > $@
DOCPDF = sox.pdf soxi.pdf soxformat.pdf libsox.pdf
pdf: $(DOCPDF)
--
2.17.0
------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
_______________________________________________
SoX-devel mailing list
SoX-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/sox-devel
prev parent reply other threads:[~2018-04-27 13:17 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-27 13:16 [PATCH 1/2] fix out of tree text/pdf/html generation Mans Rullgard
2018-04-27 13:16 ` Mans Rullgard [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-list from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://lists.sourceforge.net/lists/listinfo/sox-devel
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20180427131645.26367-2-mans@mansr.com \
--to=sox-devel@lists.sourceforge.net \
--cc=kwconder@yahoo.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://80x24.org/mirrors/sox.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).