linux-media.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Mauro Carvalho Chehab <mchehab@s-opensource.com>
To: Jonathan Corbet <corbet@lwn.net>
Cc: Linux Doc Mailing List <linux-doc@vger.kernel.org>,
	Linux Media Mailing List <linux-media@vger.kernel.org>,
	Mauro Carvalho Chehab <mchehab@infradead.org>,
	linux-kernel@vger.kernel.org,
	Daniel Vetter <daniel.vetter@ffwll.ch>,
	SeongJae Park <sj38.park@gmail.com>,
	Markus Heiser <markus.heiser@darmarit.de>
Subject: Re: [PATCH v2 4/4] docs-rst: Allow Sphinx version 1.6
Date: Sat, 26 Aug 2017 06:36:41 -0300	[thread overview]
Message-ID: <20170826063641.6f2467f2@vento.lan> (raw)
In-Reply-To: <20170824132914.062d7a4c@lwn.net>

Em Thu, 24 Aug 2017 13:29:14 -0600
Jonathan Corbet <corbet@lwn.net> escreveu:

> On Thu, 24 Aug 2017 13:26:28 -0600
> Jonathan Corbet <corbet@lwn.net> wrote:
> 
> > > -	% To allow adjusting table sizes
> > > -	\\usepackage{adjustbox}
> > > -
> > >       '''
> > >  }    
> > 
> > So this change doesn't quite match the changelog...what's the story there?  
> 
> Indeed, with that patch applied, I get this:
> 
> ! LaTeX Error: Environment adjustbox undefined.
> 
> See the LaTeX manual or LaTeX Companion for explanation.
> Type  H <return>  for immediate help.
>  ...                                              
>                                                   
> l.4108 \begin{adjustbox}
>                         {width=\columnwidth}
> 
> ...so methinks something isn't quite right...

Sorry, yeah, I messed with this one. Just sent a new series of patches,
splitting it from the documentation changes.

This change (and the equivalent one at sphinx-pre-build script) is
actually a cleanup change. It can *only* be applied after the
patch that goes through the media tree.

What happens is that this patch:
	media: fix pdf build with Spinx 1.6

Stops using adjustbox, with is what causes build problem on Sphinx 1.6.

I suspect that now the PDF build will be a bit more reliable, as the
"..raw: latex" blocs now only adjust font sizes and table spacing,
when needed to output large tables, but Sphinx maintainers have been
creative on finding new ways to break backward compatibility on every
new version ;-) Still, hope is the last thing to die.

Thanks,
Mauro

      reply	other threads:[~2017-08-26  9:36 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-08-23  8:56 [PATCH v2 0/4] Fix problems with PDF output with Sphinx 1.6 Mauro Carvalho Chehab
2017-08-23  8:56 ` [PATCH v2 1/4] media: fix pdf build with Spinx 1.6 Mauro Carvalho Chehab
2017-08-23  8:56 ` [PATCH v2 2/4] media: dev-sliced-vbi.rst: fix verbatim font size on a table Mauro Carvalho Chehab
2017-08-23  8:56 ` [PATCH v2 3/4] docs-rst: pdf: use same vertical margin on all Sphinx versions Mauro Carvalho Chehab
2017-08-23  8:56 ` [PATCH v2 4/4] docs-rst: Allow Sphinx version 1.6 Mauro Carvalho Chehab
2017-08-24 19:26   ` Jonathan Corbet
2017-08-24 19:29     ` Jonathan Corbet
2017-08-26  9:36       ` 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=20170826063641.6f2467f2@vento.lan \
    --to=mchehab@s-opensource.com \
    --cc=corbet@lwn.net \
    --cc=daniel.vetter@ffwll.ch \
    --cc=linux-doc@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-media@vger.kernel.org \
    --cc=markus.heiser@darmarit.de \
    --cc=mchehab@infradead.org \
    --cc=sj38.park@gmail.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).