Re: [PATCH 14/14] docs: staging: use small font for literal includes

From: Mauro Carvalho Chehab <mchehab+huawei@kernel.org>
To: Joe Perches <joe@perches.com>
Cc: Linux Doc Mailing List <linux-doc@vger.kernel.org>,
	linux-kernel@vger.kernel.org, Jonathan Corbet <corbet@lwn.net>
Subject: Re: [PATCH 14/14] docs: staging: use small font for literal includes
Date: Sat, 2 May 2020 12:27:28 +0200	[thread overview]
Message-ID: <20200502122728.36eb231b@coco.lan> (raw)
In-Reply-To: <3aac8d7e3f11d7df5b8155c93beee447cf8f064b.camel@perches.com>

Em Fri, 01 May 2020 17:10:00 -0700
Joe Perches <joe@perches.com> escreveu:

> On Fri, 2020-05-01 at 17:37 +0200, Mauro Carvalho Chehab wrote:
> > The normal font is too big to display 80 columns, causing extra
> > breaks to be added at weird places.
> > 
> > change to the footnotesize, as this would fit a little bit
> > better.  
> []
> > diff --git a/Documentation/staging/index.rst b/Documentation/staging/index.rst  
> []
> > @@ -19,17 +19,41 @@ Unsorted Documentation
> >  Atomic Types
> >  ============
> >  
> > +.. raw:: latex
> > +
> > +    \footnotesize  
> 
> Please don't make the markup too invasive.

With the current status, this is unavoidable.

The only way to avoid those would be to convert the document itself
to ReST, but the document writer was not convinced yet to even minimal
ReST markups on 3 files.

The problem with a text file is that the lines produced at the PDF output 
with a mono-spaced font, on LaTeX have lot less than 80 colums. So, 
some markups should tell Sphinx to use a reduced font for those includes.

However, there's no "fontsize" directive (nor any other directive that 
would allow adjusting font parameters on an included file) on Sphinx. 
So, we need to use the above.

Thanks,
Mauro