Not sure why, but, on this particular document, on Sphinx 1.4 and 1.5,
the usage of \small here causes it to write the table at the same
column where the text before it ended, with makes the table to
go out of the page.
A possible solution would be to add a \newline on latex raw,
with was the approach took.
Unfortunately, that causes a breakage on Sphinx 1.6.
So, we're adding a small dot here, in order to avoid polluting
too much the document, while making it compatible with all versions.
Signed-off-by: Mauro Carvalho Chehab <mche...@s-opensource.com>
---
Documentation/media/uapi/v4l/pixfmt-srggb10p.rst | 16 ++++++++++++++--
1 file changed, 14 insertions(+), 2 deletions(-)
diff --git a/Documentation/media/uapi/v4l/pixfmt-srggb10p.rst
b/Documentation/media/uapi/v4l/pixfmt-srggb10p.rst
index 9e52610aa954..aa3dbf163b97 100644
--- a/Documentation/media/uapi/v4l/pixfmt-srggb10p.rst
+++ b/Documentation/media/uapi/v4l/pixfmt-srggb10p.rst
@@ -33,10 +33,22 @@ of a small V4L2_PIX_FMT_SBGGR10P image:
**Byte Order.**
Each cell is one byte.
-
.. raw:: latex
- \newline\small
+ \small
+
+.. HACK:
+
+ On Sphinx 1.4 and 1.5, the usage of \small just before the table
+ causes it to continue at the same column where the above text ended.
+
+ A possible solution would be to add a \newline on latex raw.
+ Unfortunately, that causes a breakage on Sphinx 1.6.
+
+ So, we're placing the \small before this note, with should be producing
+ the same result on all versions
+
+.
.. tabularcolumns:: |p{2.0cm}|p{1.0cm}|p{1.0cm}|p{1.0cm}|p{1.0cm}|p{10.0cm}|
--
2.13.5
