public inbox for linux-media@vger.kernel.org
 help / color / mirror / Atom feed
From: Mauro Carvalho Chehab <mchehab@s-opensource.com>
To: Markus Heiser <markus.heiser@darmarit.de>
Cc: Linux Media Mailing List <linux-media@vger.kernel.org>,
	Mauro Carvalho Chehab <mchehab@infradead.org>,
	Jonathan Corbet <corbet@lwn.net>,
	linux-doc@vger.kernel.org
Subject: Re: [PATCH RFC v2 3/9] docs-rst: Don't mangle with UTF-8 chars on LaTeX/PDF output
Date: Tue, 16 Aug 2016 13:51:12 -0300	[thread overview]
Message-ID: <20160816135112.4207b489@vento.lan> (raw)
In-Reply-To: <1C2F668D-41DD-4682-89D9-639430AAF3A6@darmarit.de>

Em Tue, 16 Aug 2016 13:48:13 +0200
Markus Heiser <markus.heiser@darmarit.de> escreveu:

> Am 16.08.2016 um 13:03 schrieb Mauro Carvalho Chehab <mchehab@s-opensource.com>:
> 
> > Em Tue, 16 Aug 2016 06:36:05 -0300
> > Mauro Carvalho Chehab <mchehab@s-opensource.com> escreveu:
> > 
> > 2) the Latex auto-generated Makefile is hardcoded to use pdflatex. So,
> > I had to manually replace it to xelatex. One easy solution would be to
> > not use Make -C $BUILDDIR/latex, but to just call xelatex $BUILDDIR/$tex_name.  
> 
> I recommend to ship your own tex-Makefile, see:
> 
>   https://lkml.org/lkml/2016/8/10/114

That makes sense for me, but let the others review what we have so far.
We can later improve and use a makefile for tex. I would prefer to call
the version that will be copied to the output dir with a different name
(like Makefile.tex or Makefile.in), as I found really weird to have a
file called Makefile inside the Kernel tree that contains just a makefile
prototype.

Regards,
Mauro

  reply	other threads:[~2016-08-16 16:51 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-08-15 21:21 [PATCH RFC v2 0/9] Make PDF output for media book to work Mauro Carvalho Chehab
2016-08-15 21:21 ` [PATCH 1/9] docs-rst: allow generating some LaTeX pages in landscape Mauro Carvalho Chehab
2016-08-15 21:21 ` [PATCH RFC v2 2/9] docs-rst: improve output for .. notes:: on LaTeX Mauro Carvalho Chehab
2016-08-15 21:21 ` [PATCH RFC v2 3/9] docs-rst: Don't mangle with UTF-8 chars on LaTeX/PDF output Mauro Carvalho Chehab
2016-08-16  8:27   ` Markus Heiser
2016-08-16  9:36     ` Mauro Carvalho Chehab
2016-08-16 11:03       ` Mauro Carvalho Chehab
2016-08-16 11:48         ` Markus Heiser
2016-08-16 16:51           ` Mauro Carvalho Chehab [this message]
2016-08-16 12:16         ` Mauro Carvalho Chehab
2016-08-16 12:35           ` Markus Heiser
2016-08-16 16:52             ` Mauro Carvalho Chehab
2016-08-15 21:21 ` [PATCH RFC v2 4/9] [media] pixfmt-007.rst: use Sphinx math:: expressions Mauro Carvalho Chehab
2016-08-15 21:21 ` [PATCH RFC v2 5/9] [media] pixfmt-nv12mt.rst: use PNG instead of GIF Mauro Carvalho Chehab
2016-08-15 21:21 ` [PATCH RFC v2 6/9] [media] vidioc-enumstd.rst: fix a broken reference Mauro Carvalho Chehab
2016-08-15 21:21 ` [PATCH RFC v2 7/9] [media] vidioc-enumstd.rst: remove bullets from sound carrier Mauro Carvalho Chehab
2016-08-15 21:21 ` [PATCH RFC v2 8/9] [media] docs-rst: better use the .. note:: tag Mauro Carvalho Chehab
2016-08-15 21:22 ` [PATCH RFC v2 9/9] HACK: make pdfdocs build with media books 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=20160816135112.4207b489@vento.lan \
    --to=mchehab@s-opensource.com \
    --cc=corbet@lwn.net \
    --cc=linux-doc@vger.kernel.org \
    --cc=linux-media@vger.kernel.org \
    --cc=markus.heiser@darmarit.de \
    --cc=mchehab@infradead.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