From: Jonathan Corbet <corbet@lwn.net>
To: Mauro Carvalho Chehab <mchehab+samsung@kernel.org>
Cc: Heiko Carstens <heiko.carstens@de.ibm.com>,
Hannes Reinecke <hare@suse.com>,
linux-kbuild@vger.kernel.org, Jens Axboe <axboe@kernel.dk>,
Andy Shevchenko <andy.shevchenko@gmail.com>,
Christian Borntraeger <borntraeger@de.ibm.com>,
Dan Williams <dan.j.williams@intel.com>,
Michal Marek <michal.lkml@markovi.net>,
Masahiro Yamada <yamada.masahiro@socionext.com>,
Vasily Gorbik <gor@linux.ibm.com>,
linux-s390@vger.kernel.org, linux-doc@vger.kernel.org,
Omar Sandoval <osandov@fb.com>
Subject: Re: [PATCH 0/5] PDF output fixes
Date: Fri, 12 Jul 2019 14:19:21 -0600 [thread overview]
Message-ID: <20190712141921.7f8a1d02@lwn.net> (raw)
In-Reply-To: <cover.1562696797.git.mchehab+samsung@kernel.org>
On Tue, 9 Jul 2019 15:33:18 -0300
Mauro Carvalho Chehab <mchehab+samsung@kernel.org> wrote:
> In order to be able to build all PDF books, besides the two patches I
> already sent:
>
> docs: pdf: add all Documentation/*/index.rst to PDF output
> docs: automarkup.py: ignore exceptions when seeking for xrefs
>
> A few others are needed:
>
> - patch 1 removes nested tables for a few files I converted, as
> Sphinx LaTeX builder doesn't support it;
> - Patches 2 to 4 addresses some minor issues on some books,
> usually requiring some blank lines, extra whitespaces or some
> tag replacement;
> - Patch 5 is required in order to be able to build the translations
> PDF book, as it adds Asian fonts support to XeLaTeX.
So, modulo my one comment on the last patch the series seems OK, though I
don't like having to work around limitations in PDF generation this way.
Can't you just make rst2pdf work instead? :)
I guess it makes sense for these to go with the big band-aid-removal patch
set.
Thanks,
jon
P.S. it seems that rst2pdf is actually being developed again:
https://akrabat.com/rst2pdf-back-from-the-dead/ . I wonder how far
they'll get with it.
next prev parent reply other threads:[~2019-07-12 20:19 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-09 18:33 [PATCH 0/5] PDF output fixes Mauro Carvalho Chehab
2019-07-09 18:33 ` [PATCH 1/5] docs: don't use nested tables Mauro Carvalho Chehab
2019-07-09 18:33 ` [PATCH 2/5] docs: arm: fix a breakage with pdf output Mauro Carvalho Chehab
2019-07-09 18:33 ` [PATCH 3/5] docs: block: fix " Mauro Carvalho Chehab
2019-07-09 18:33 ` [PATCH 4/5] docs: kbuild: fix build with pdf and fix some minor issues Mauro Carvalho Chehab
2019-07-09 18:33 ` [PATCH 5/5] docs: conf.py: add CJK package needed by translations Mauro Carvalho Chehab
2019-07-12 20:12 ` Jonathan Corbet
2019-07-12 21:16 ` Mauro Carvalho Chehab
2019-07-12 20:19 ` Jonathan Corbet [this message]
2019-07-12 22:27 ` [PATCH 0/5] PDF output fixes Mauro Carvalho Chehab
2019-07-13 3:41 ` Mauro Carvalho Chehab
2019-07-18 17:46 ` Using rst2pdf for PDF output - Was: " Mauro Carvalho Chehab
2019-07-18 17:56 ` Markus Heiser
2019-07-19 2:44 ` Mauro Carvalho Chehab
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=20190712141921.7f8a1d02@lwn.net \
--to=corbet@lwn.net \
--cc=andy.shevchenko@gmail.com \
--cc=axboe@kernel.dk \
--cc=borntraeger@de.ibm.com \
--cc=dan.j.williams@intel.com \
--cc=gor@linux.ibm.com \
--cc=hare@suse.com \
--cc=heiko.carstens@de.ibm.com \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kbuild@vger.kernel.org \
--cc=linux-s390@vger.kernel.org \
--cc=mchehab+samsung@kernel.org \
--cc=michal.lkml@markovi.net \
--cc=osandov@fb.com \
--cc=yamada.masahiro@socionext.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.
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 NNTP newsgroup(s).