From: Mauro Carvalho Chehab <mchehab+samsung@kernel.org>
To: Markus Heiser <markus.heiser@darmarit.de>
Cc: Jonathan Corbet <corbet@lwn.net>, linux-doc@vger.kernel.org
Subject: Re: Using rst2pdf for PDF output - Was: Re: [PATCH 0/5] PDF output fixes
Date: Thu, 18 Jul 2019 23:44:16 -0300 [thread overview]
Message-ID: <20190718234416.59c9cf7a@coco.lan> (raw)
In-Reply-To: <04a1a65f-c96c-1f4a-d987-d8b9e605d7c1@darmarit.de>
Em Thu, 18 Jul 2019 19:56:57 +0200
Markus Heiser <markus.heiser@darmarit.de> escreveu:
> Am 18.07.19 um 19:46 schrieb Mauro Carvalho Chehab:
> > Em Sat, 13 Jul 2019 00:41:25 -0300
> > Mauro Carvalho Chehab <mchehab+samsung@kernel.org> escreveu:
> >
> >> Em Fri, 12 Jul 2019 19:27:05 -0300
> >> Mauro Carvalho Chehab <mchehab+samsung@kernel.org> escreveu:
> >>
> >>> Em Fri, 12 Jul 2019 14:19:21 -0600
> >>> Jonathan Corbet <corbet@lwn.net> escreveu:
> >>>
> >>>> Can't you just make rst2pdf work instead? :)
> >>>
> >>> Well, we can try.
>
> Thanks a lot for your investigation on this. I also checked the rst2pdf sources
> a while ago, for me it was crap with crap requirements [1] .. my tip: don't
> waste to much time on it.
>
> [1] https://github.com/mchehab/rst2pdf/blob/master/requirements.txt#L31
>
Yeah, a simple test shows that this upstream rst2pdf + latest reportlab has
some issues.
Running this:
$ rst2pdf Documentation/process/license-rules.rst
causes an error with reportlab-3.5.23. It has to be downgraded to version
3.4 in order to avoid this error:
File "/devel/v4l/docs_temp/sphinx_2.0.1/lib/python3.7/site-packages/reportlab/platypus/doctemplate.py", line 651, in handle_pageEnd
raise LayoutError(ident)
reportlab.platypus.doctemplate.LayoutError: More than 10 pages generated without content - halting layout. Likely that a flowable is too large for any frame.
Another solution would be to do this:
diff --git a/Documentation/process/license-rules.rst b/Documentation/process/license-rules.rst
index 2ef44ada3f11..19a480ebd69a 100644
--- a/Documentation/process/license-rules.rst
+++ b/Documentation/process/license-rules.rst
@@ -452,7 +452,10 @@ _`MODULE_LICENSE`
module source is dual licensed under a
GPL v2 variant and MIT license. Please do
not use in new code.
+ ============================= =============================================
+
+ ============================= =============================================
"Dual MIT/GPL" The correct way of expressing that the
module is dual licensed under a GPL v2
variant or MIT license choice.
But it sucks needing to break long tables because reportlab's handling
for big tables is broken.
Thanks,
Mauro
prev parent reply other threads:[~2019-07-19 2:44 UTC|newest]
Thread overview: 17+ 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 ` 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 ` 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 ` 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 ` [PATCH 0/5] PDF output fixes Jonathan Corbet
2019-07-12 22:27 ` 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 [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-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=20190718234416.59c9cf7a@coco.lan \
--to=mchehab+samsung@kernel.org \
--cc=corbet@lwn.net \
--cc=linux-doc@vger.kernel.org \
--cc=markus.heiser@darmarit.de \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.