From: Mauro Carvalho Chehab <mchehab@s-opensource.com>
To: Sakari Ailus <sakari.ailus@linux.intel.com>
Cc: linux-doc@vger.kernel.org, linux-media@vger.kernel.org,
mchehab@infradead.org, linux-kernel@vger.kernel.org,
Jonathan Corbet <corbet@lwn.net>,
Hans Verkuil <hans.verkuil@cisco.com>,
Laurent Pinchart <laurent.pinchart@ideasonboard.com>,
Aviv Greenberg <aviv.d.greenberg@intel.com>
Subject: Re: [PATCH 1/1] docs-rst: media: Don't use \small for V4L2_PIX_FMT_SRGGB10 documentation
Date: Mon, 4 Sep 2017 17:43:28 -0300 [thread overview]
Message-ID: <20170904174328.7415ea1f@vento.lan> (raw)
In-Reply-To: <20170903224002.071c1587@vento.lan>
Em Sun, 3 Sep 2017 22:40:02 -0300
Mauro Carvalho Chehab <mchehab@s-opensource.com> escreveu:
> Em Sun, 3 Sep 2017 23:12:33 +0300
> Sakari Ailus <sakari.ailus@linux.intel.com> escreveu:
>
> > There appears to be an issue in using \small in certain cases on Sphinx
> > 1.4 and 1.5. Other format documents don't use \small either, remove it
> > from here as well.
> >
> > Signed-off-by: Sakari Ailus <sakari.ailus@linux.intel.com>
> > ---
> > Hi Mauro,
> >
> > What would you think of this as an alternative approach? No hacks needed.
> > Just a recognition \small could have issues. For what it's worth, I
> > couldn't reproduce the issue on Sphinx 1.4.9.
>
> Btw, there are other places where \small runs smoothly. It is *just*
> on this table that it has issues.
>
>
> >
> > Regards,
> > Sakari
> >
> > Documentation/media/uapi/v4l/pixfmt-srggb10p.rst | 11 -----------
> > 1 file changed, 11 deletions(-)
> >
> > diff --git a/Documentation/media/uapi/v4l/pixfmt-srggb10p.rst b/Documentation/media/uapi/v4l/pixfmt-srggb10p.rst
> > index 86cd07e5bfa3..368ee61ab209 100644
> > --- a/Documentation/media/uapi/v4l/pixfmt-srggb10p.rst
> > +++ b/Documentation/media/uapi/v4l/pixfmt-srggb10p.rst
> > @@ -33,13 +33,6 @@ of a small V4L2_PIX_FMT_SBGGR10P image:
> > **Byte Order.**
> > Each cell is one byte.
> >
> > -
> > -.. raw:: latex
> > -
> > - \small
>
> Interesting... yeah, that could be possible.
>
> > -
> > -.. tabularcolumns:: |p{2.0cm}|p{1.0cm}|p{1.0cm}|p{1.0cm}|p{1.0cm}|p{10.0cm}|
>
> Nah... Without tabularcolumns, LaTeX usually got sizes wrong and don't
> always place things at the right positions I'm actually considering
> adding it to all media tables, in order to be less dependent on
> LaTex automatic cells resizing - with doesn't seem to work too well.
>
> So, better to keep it, even if it works without
> \small. Btw, tried your patch here (without tabularcolumns) on
> Sphinx 1.6 (tomorrow, I'll do tests with other version). There, the
> last "(bits x-y)" ends by being wrapped to the next line.
>
> Yet, I guess the enclosed diff (or something like that) would be
> good enough (applied after my own patch, just to quickly test it).
>
> I'll play more with it tomorrow.
OK, that works. Thanks!
I rebased your patch, keeping tabularcolumns and adding blank lines
to reduce the column size.
That works really better.
I also added a second patch doing the same for srggb12p.
Thanks,
Mauro
next prev parent reply other threads:[~2017-09-04 20:43 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-09-03 19:03 [PATCH 0/7] Another set of fixes for PDF output Mauro Carvalho Chehab
2017-09-03 19:03 ` [PATCH 1/7] media: format.rst: use the right markup for important notes Mauro Carvalho Chehab
2017-09-03 19:03 ` [PATCH 2/7] media: v4l2 uapi book: get rid of driver programming's chapter Mauro Carvalho Chehab
2017-09-03 19:03 ` [PATCH 3/7] media: vivid.rst: add a blank line to correct ReST format Mauro Carvalho Chehab
2017-09-03 19:03 ` [PATCH 4/7] media: vidioc-g-fmt.rst: adjust table format Mauro Carvalho Chehab
2017-09-03 19:03 ` [PATCH 5/7] media: fix build breakage with Sphinx 1.6 Mauro Carvalho Chehab
2017-09-03 20:12 ` [PATCH 1/1] docs-rst: media: Don't use \small for V4L2_PIX_FMT_SRGGB10 documentation Sakari Ailus
2017-09-04 1:40 ` Mauro Carvalho Chehab
2017-09-04 20:43 ` Mauro Carvalho Chehab [this message]
2017-09-03 19:03 ` [PATCH 6/7] media: pixfmt*.rst: replace a two dots by a comma Mauro Carvalho Chehab
2017-09-03 19:03 ` [PATCH 7/7] media: index.rst: don't write "Contents:" on PDF output 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=20170904174328.7415ea1f@vento.lan \
--to=mchehab@s-opensource.com \
--cc=aviv.d.greenberg@intel.com \
--cc=corbet@lwn.net \
--cc=hans.verkuil@cisco.com \
--cc=laurent.pinchart@ideasonboard.com \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=mchehab@infradead.org \
--cc=sakari.ailus@linux.intel.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