From: Mark Wielaard <mark@klomp.org>
To: bzip2-devel@sourceware.org
Cc: "Anibal Monsalve Salazar" <anibal@debian.org>,
"Santiago Ruano Rincón" <santiago@debian.org>,
"Anthony Fok" <foka@debian.org>
Subject: Some bzip2 manual page patches from Debian
Date: Tue, 01 Jan 2019 00:00:00 -0000 [thread overview]
Message-ID: <20190721205419.2904-1-mark@klomp.org> (raw)
Hi,
Here are two patches from Debian for the man page and manual.
The first simply removes some odd blanks/formatting from bzip2.1.
The second adds the --help option to the manual and man page.
The last one adds generation of bzip2.txt and bzip2.1.preformatted
to the Makefile, so they are freshly generated when doing a dist.
[PATCH 1/3] bzip2.1: remove blank spaces in man page and drop the
.PU macro
[PATCH 2/3] Mention the --help command line option in the manual
[PATCH 3/3] Add generation of bzip2.txt and bzip2.1.preformatted
to Makefile
Ideally the bzip2.1 man page itself would be generated from the
manual.xml file. But I saw that on Debian even the pdf and html
generation of the manual seem to fail. Debian does have a
xml-manual-escape.diff patch, which escape special characters in
XML source of the manual' but that seems wrong to me. The special
characters don't seem special in xml, only in the html. So when
applied the characters get escaped twice. Does Debian regenerate
the manual, and if so, does it do it differently than how it
is done through the upstream xmlproc.sh script?
Thanks,
Mark
next reply other threads:[~2019-07-21 20:55 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-01 0:00 Mark Wielaard [this message]
2019-01-01 0:00 ` [PATCH 2/3] Mention the --help command line option in the documentation Mark Wielaard
2019-01-01 0:00 ` Some bzip2 manual page patches from Debian Santiago Ruano Rincón
2019-01-01 0:00 ` Mark Wielaard
2019-01-01 0:00 ` [PATCH 1/3] bzip2.1: remove blank spaces in man page and drop the .PU macro Mark Wielaard
2019-01-01 0:00 ` [PATCH 3/3] Add generation of bzip2.txt and bzip2.1.preformatted to Makefile Mark Wielaard
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-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20190721205419.2904-1-mark@klomp.org \
--to=mark@klomp.org \
--cc=anibal@debian.org \
--cc=bzip2-devel@sourceware.org \
--cc=foka@debian.org \
--cc=santiago@debian.org \
/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.
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).