From: Jani Nikula <jani.nikula@intel.com>
To: Mauro Carvalho Chehab <mchehab@osg.samsung.com>,
Jonathan Corbet <corbet@lwn.net>
Cc: "Luis R. Rodriguez" <mcgrof@kernel.org>,
linux-doc@vger.kernel.org,
"linux-kernel\@vger.kernel.org" <linux-kernel@vger.kernel.org>,
Daniel Vetter <daniel.vetter@ffwll.ch>,
Markus Heiser <markus.heiser@darmarit.de>
Subject: Re: [RFC PATCH 0/3] Documentation: switch to pdflatex and fix pdf build
Date: Fri, 19 Aug 2016 15:54:37 +0300 [thread overview]
Message-ID: <87zio8syuq.fsf@intel.com> (raw)
In-Reply-To: <20160815192632.56727ab9@vento.lan>
On Tue, 16 Aug 2016, Mauro Carvalho Chehab <mchehab@osg.samsung.com> wrote:
> 5) At media docs, some tables will only print ok in landscape.
>
> After making the media books build, I think that the best way is to
> use xelatex instead of pdfdocs. Visually, xelatex output is, IMHO,
> nice - and it has colors :-)
>
> It seems that there's yet another option: lualatex. I didn't try to
> build with it. So, not sure if its output is better or not, nor if
> some extra config for it is needed at conf.py.
>
> I sent a patch series addressing most of the issues above.
I didn't see the series, but I'm surprised we now have HAVE_PDFLATEX
that actually checks for 'xelatex'. The commit subject doing the change
doesn't even mention xelatex, it's just about UTF-8:
commit a682ec4ba10c88231cdbb8bb9823b2cc749d6364
Author: Mauro Carvalho Chehab <mchehab@s-opensource.com>
Date: Tue Aug 16 13:25:39 2016 -0300
docs-rst: Don't mangle with UTF-8 chars on LaTeX/PDF output
</bikeshedding after the fact>
BR,
Jani.
--
Jani Nikula, Intel Open Source Technology Center
next prev parent reply other threads:[~2016-08-19 12:54 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-08-10 1:19 Making pdfdocs with sphinx - only select rst targets Luis R. Rodriguez
2016-08-10 8:41 ` Mauro Carvalho Chehab
[not found] ` <CAB=NE6UUiKSn66=F+WUrqk3E1tj+fnzqFnD=dX55md6RnaiOgQ@mail.gmail.com>
2016-08-10 15:05 ` Mauro Carvalho Chehab
2016-08-10 15:54 ` [RFC PATCH 0/3] Documentation: switch to pdflatex and fix pdf build Jani Nikula
2016-08-10 15:54 ` [RFC PATCH 1/3] Documentation/sphinx: build the media intermediate rst files for all outputs Jani Nikula
2016-08-10 16:14 ` Mauro Carvalho Chehab
2016-08-10 15:54 ` [RFC PATCH 2/3] Documentation: switch to pdflatex for pdf generation Jani Nikula
2016-08-10 17:15 ` Markus Heiser
2016-08-10 20:07 ` Luis R. Rodriguez
2016-08-10 15:54 ` [RFC PATCH 3/3] Documentation: exclude media documentation from " Jani Nikula
2016-08-10 16:16 ` Mauro Carvalho Chehab
2016-08-10 16:31 ` Markus Heiser
2016-08-10 20:05 ` Luis R. Rodriguez
2016-08-10 16:27 ` [RFC PATCH 0/3] Documentation: switch to pdflatex and fix pdf build Markus Heiser
2016-08-10 20:09 ` Luis R. Rodriguez
2016-08-12 22:40 ` Jonathan Corbet
2016-08-13 16:00 ` Markus Heiser
2016-08-15 9:40 ` Jani Nikula
2016-08-15 12:17 ` Mauro Carvalho Chehab
2016-08-15 22:26 ` Mauro Carvalho Chehab
2016-08-19 12:54 ` Jani Nikula [this message]
2016-08-19 13:21 ` 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=87zio8syuq.fsf@intel.com \
--to=jani.nikula@intel.com \
--cc=corbet@lwn.net \
--cc=daniel.vetter@ffwll.ch \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=markus.heiser@darmarit.de \
--cc=mcgrof@kernel.org \
--cc=mchehab@osg.samsung.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