[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20160603144732.18db8869@lwn.net>
Date: Fri, 3 Jun 2016 14:47:32 -0600
From: Jonathan Corbet <corbet@....net>
To: Jani Nikula <jani.nikula@...el.com>
Cc: Markus Heiser <markus.heiser@...marit.de>,
Daniel Vetter <daniel.vetter@...ll.ch>,
Grant Likely <grant.likely@...retlab.ca>,
Mauro Carvalho Chehab <mchehab@....samsung.com>,
Dan Allen <dan@...ndevise.io>,
Russel Winder <russel@...der.org.uk>,
Keith Packard <keithp@...thp.com>,
LKML <linux-kernel@...r.kernel.org>, linux-doc@...r.kernel.org,
Hans Verkuil <hverkuil@...all.nl>
Subject: Re: rst2pdf (was [PATCH 00/10] Documentation/Sphinx)
On Mon, 30 May 2016 23:05:34 +0300
Jani Nikula <jani.nikula@...el.com> wrote:
> > I can't recommend to use rst2pdf (it is less maintained), use default
> > sphinx LaTeX toolchain.
>
> I think we'll use whatever works, rst2pdf seemed to work for now, but we
> can change if needed.
I really like the idea of using rst2pdf and keeping the huge latex
dependency out of the mix. I am a bit concerned, though; I've been able
to crash it in my experiments here. We may want to have the ability to
support either chain eventually; otherwise, we might just end up picking
up maintenance of rst2pdf at some point so that it works properly for us.
jon
Powered by blists - more mailing lists