As described at:
https://stackoverflow.com/questions/23211695/modifying-content-width-of-the-sphinx-theme-read-the-docs
since Sphinx 1.8, the standard way to setup a custom theme is
to use html_css_files. While using html_context is OK with RTD
0.5.2, it doesn't work with 1.0.0, causing the theme to not load,
producing a very weird html.
Tested with:
- Sphinx 2.4.4 + sphinx-rtd-theme 0.5.2
- Sphinx 2.4.4 + sphinx-rtd-theme 1.0.0
- Sphinx 4.3.0 + sphinx-rtd-theme 1.0.0
Reported-by: Hans Verkuil <[email protected]>
Signed-off-by: Mauro Carvalho Chehab <[email protected]>
---
Documentation/conf.py | 13 +++++++++----
1 file changed, 9 insertions(+), 4 deletions(-)
diff --git a/Documentation/conf.py b/Documentation/conf.py
index 17f7cee56987..7bc72be63fd2 100644
--- a/Documentation/conf.py
+++ b/Documentation/conf.py
@@ -249,11 +249,16 @@ except ImportError:
html_static_path = ['sphinx-static']
-html_context = {
- 'css_files': [
+if major <= 1 and (minor < 8):
+ html_context = {
+ 'css_files': [
+ '_static/theme_overrides.css',
+ ],
+ }
+else:
+ html_css_files = [
'_static/theme_overrides.css',
- ],
-}
+ ]
# Add any extra paths that contain custom files (such as robots.txt or
# .htaccess) here, relative to this directory. These files are copied
--
2.33.1
On 26/11/2021 11:50, Mauro Carvalho Chehab wrote:
> As described at:
> https://stackoverflow.com/questions/23211695/modifying-content-width-of-the-sphinx-theme-read-the-docs
>
> since Sphinx 1.8, the standard way to setup a custom theme is
> to use html_css_files. While using html_context is OK with RTD
> 0.5.2, it doesn't work with 1.0.0, causing the theme to not load,
> producing a very weird html.
>
> Tested with:
> - Sphinx 2.4.4 + sphinx-rtd-theme 0.5.2
> - Sphinx 2.4.4 + sphinx-rtd-theme 1.0.0
> - Sphinx 4.3.0 + sphinx-rtd-theme 1.0.0
>
> Reported-by: Hans Verkuil <[email protected]>
Tested-by: Hans Verkuil <[email protected]>
Much appreciated! Looks a lot better now :-)
Regards,
Hans
> Signed-off-by: Mauro Carvalho Chehab <[email protected]>
> ---
> Documentation/conf.py | 13 +++++++++----
> 1 file changed, 9 insertions(+), 4 deletions(-)
>
> diff --git a/Documentation/conf.py b/Documentation/conf.py
> index 17f7cee56987..7bc72be63fd2 100644
> --- a/Documentation/conf.py
> +++ b/Documentation/conf.py
> @@ -249,11 +249,16 @@ except ImportError:
>
> html_static_path = ['sphinx-static']
>
> -html_context = {
> - 'css_files': [
> +if major <= 1 and (minor < 8):
> + html_context = {
> + 'css_files': [
> + '_static/theme_overrides.css',
> + ],
> + }
> +else:
> + html_css_files = [
> '_static/theme_overrides.css',
> - ],
> -}
> + ]
>
> # Add any extra paths that contain custom files (such as robots.txt or
> # .htaccess) here, relative to this directory. These files are copied
>
Hi Mauro,
Thank you for the patch.
On Fri, Nov 26, 2021 at 11:50:53AM +0100, Mauro Carvalho Chehab wrote:
> As described at:
> https://stackoverflow.com/questions/23211695/modifying-content-width-of-the-sphinx-theme-read-the-docs
>
> since Sphinx 1.8, the standard way to setup a custom theme is
> to use html_css_files. While using html_context is OK with RTD
> 0.5.2, it doesn't work with 1.0.0, causing the theme to not load,
> producing a very weird html.
>
> Tested with:
> - Sphinx 2.4.4 + sphinx-rtd-theme 0.5.2
> - Sphinx 2.4.4 + sphinx-rtd-theme 1.0.0
> - Sphinx 4.3.0 + sphinx-rtd-theme 1.0.0
>
> Reported-by: Hans Verkuil <[email protected]>
> Signed-off-by: Mauro Carvalho Chehab <[email protected]>
> ---
> Documentation/conf.py | 13 +++++++++----
> 1 file changed, 9 insertions(+), 4 deletions(-)
>
> diff --git a/Documentation/conf.py b/Documentation/conf.py
> index 17f7cee56987..7bc72be63fd2 100644
> --- a/Documentation/conf.py
> +++ b/Documentation/conf.py
> @@ -249,11 +249,16 @@ except ImportError:
>
> html_static_path = ['sphinx-static']
>
> -html_context = {
> - 'css_files': [
> +if major <= 1 and (minor < 8):
No need for parentheses.
> + html_context = {
> + 'css_files': [
> + '_static/theme_overrides.css',
> + ],
> + }
> +else:
> + html_css_files = [
> '_static/theme_overrides.css',
> - ],
> -}
> + ]
You could also write
html_css_files = [
'_static/theme_overrides.css',
]
if major <= 1 and minor < 8:
html_context = {
'css_files': html_css_files,
}
which would be slightly easier to drop when support for sphinx 1.7
(which is the minimum required version) is removed.
Reviewed-by: Laurent Pinchart <[email protected]>
> # Add any extra paths that contain custom files (such as robots.txt or
> # .htaccess) here, relative to this directory. These files are copied
--
Regards,
Laurent Pinchart
Hi Mauro,
On Fri, Nov 26, 2021 at 11:50:53AM +0100, Mauro Carvalho Chehab wrote:
> As described at:
> https://stackoverflow.com/questions/23211695/modifying-content-width-of-the-sphinx-theme-read-the-docs
>
> since Sphinx 1.8, the standard way to setup a custom theme is
> to use html_css_files. While using html_context is OK with RTD
> 0.5.2, it doesn't work with 1.0.0, causing the theme to not load,
> producing a very weird html.
>
> Tested with:
> - Sphinx 2.4.4 + sphinx-rtd-theme 0.5.2
> - Sphinx 2.4.4 + sphinx-rtd-theme 1.0.0
> - Sphinx 4.3.0 + sphinx-rtd-theme 1.0.0
>
> Reported-by: Hans Verkuil <[email protected]>
> Signed-off-by: Mauro Carvalho Chehab <[email protected]>
> ---
> Documentation/conf.py | 13 +++++++++----
> 1 file changed, 9 insertions(+), 4 deletions(-)
So I have an issue with this simple change.
As I said to Jon in another thread [1], in which Jon didn't show any
interest, this update changes the look of generated HTML pages
(I should say) rather drastically, and it looks quite distracting
for my eyes. The style might be acceptable for API documentations,
but kernel-doc has abundant natural language contents.
[1]: https://lkml.kernel.org/r/[email protected]
I think there should be some knobs for customizing the styles.
But I don't know much about css.
Can anybody restore the current look of kernel-doc HTML pages
in a sphinx-rtd-theme-1.0.0-compatible way?
Sidenote:
The change (html_css_files) actually works with
- Sphinx 1.7.9 + sphinx-rtd-theme 1.0.0
This contradicts the Sphinx documentation saying that html_css_files
was new to Sphinx 1.8. This might be related to the changes in
sphinx-rtd-theme side, but I have no evidence.
Any suggestion is welcome!
Regards, Akira
On 11/26/21 6:33 AM, Akira Yokosawa wrote:
> Hi Mauro,
>
> On Fri, Nov 26, 2021 at 11:50:53AM +0100, Mauro Carvalho Chehab wrote:
>> As described at:
>> https://stackoverflow.com/questions/23211695/modifying-content-width-of-the-sphinx-theme-read-the-docs
>>
>> since Sphinx 1.8, the standard way to setup a custom theme is
>> to use html_css_files. While using html_context is OK with RTD
>> 0.5.2, it doesn't work with 1.0.0, causing the theme to not load,
>> producing a very weird html.
>>
>> Tested with:
>> - Sphinx 2.4.4 + sphinx-rtd-theme 0.5.2
>> - Sphinx 2.4.4 + sphinx-rtd-theme 1.0.0
>> - Sphinx 4.3.0 + sphinx-rtd-theme 1.0.0
>>
>> Reported-by: Hans Verkuil <[email protected]>
>> Signed-off-by: Mauro Carvalho Chehab <[email protected]>
>> ---
>> Documentation/conf.py | 13 +++++++++----
>> 1 file changed, 9 insertions(+), 4 deletions(-)
>
> So I have an issue with this simple change.
> As I said to Jon in another thread [1], in which Jon didn't show any
> interest, this update changes the look of generated HTML pages
> (I should say) rather drastically, and it looks quite distracting
> for my eyes. The style might be acceptable for API documentations,
> but kernel-doc has abundant natural language contents.
I agree 100% that the sans serif font is not desirable and not as
easy on the eyes as the serif font is.
Hopefully there is a way to change that.
> [1]: https://lkml.kernel.org/r/[email protected]
>
> I think there should be some knobs for customizing the styles.
> But I don't know much about css.
>
> Can anybody restore the current look of kernel-doc HTML pages
> in a sphinx-rtd-theme-1.0.0-compatible way?
>
> Sidenote:
>
> The change (html_css_files) actually works with
> - Sphinx 1.7.9 + sphinx-rtd-theme 1.0.0
>
> This contradicts the Sphinx documentation saying that html_css_files
> was new to Sphinx 1.8. This might be related to the changes in
> sphinx-rtd-theme side, but I have no evidence.
>
> Any suggestion is welcome!
thanks.
--
~Randy
On Fri, 26 Nov 2021, Randy Dunlap <[email protected]> wrote:
> On 11/26/21 6:33 AM, Akira Yokosawa wrote:
>> Hi Mauro,
>>
>> On Fri, Nov 26, 2021 at 11:50:53AM +0100, Mauro Carvalho Chehab wrote:
>>> As described at:
>>> https://stackoverflow.com/questions/23211695/modifying-content-width-of-the-sphinx-theme-read-the-docs
>>>
>>> since Sphinx 1.8, the standard way to setup a custom theme is
>>> to use html_css_files. While using html_context is OK with RTD
>>> 0.5.2, it doesn't work with 1.0.0, causing the theme to not load,
>>> producing a very weird html.
>>>
>>> Tested with:
>>> - Sphinx 2.4.4 + sphinx-rtd-theme 0.5.2
>>> - Sphinx 2.4.4 + sphinx-rtd-theme 1.0.0
>>> - Sphinx 4.3.0 + sphinx-rtd-theme 1.0.0
>>>
>>> Reported-by: Hans Verkuil <[email protected]>
>>> Signed-off-by: Mauro Carvalho Chehab <[email protected]>
>>> ---
>>> Documentation/conf.py | 13 +++++++++----
>>> 1 file changed, 9 insertions(+), 4 deletions(-)
>>
>> So I have an issue with this simple change.
>> As I said to Jon in another thread [1], in which Jon didn't show any
>> interest, this update changes the look of generated HTML pages
>> (I should say) rather drastically, and it looks quite distracting
>> for my eyes. The style might be acceptable for API documentations,
>> but kernel-doc has abundant natural language contents.
>
> I agree 100% that the sans serif font is not desirable and not as
> easy on the eyes as the serif font is.
> Hopefully there is a way to change that.
Taking a step back, choosing the sphinx-rtd-theme to begin with was
purely arbitrary, I didn't put much effort into checking the
alternatives, and as far as I recall, neither did Jon. There were more
pressing issues at the time to get the documentation generation ball
rolling at all.
Obviously anyone can change the theme for themselves, and I guess the
question is rather what the default is, and, subsequently, what gets
used at [1].
I haven't followed the development on this closely, but I am somewhat
surprised at the amount of theme overrides having been added, and it
begs the question whether there'd perhaps be a readily available stock
theme that would be better suited than sphinx-rtd-theme?
BR,
Jani.
[1] https://www.kernel.org/doc/html/latest/
>
>> [1]: https://lkml.kernel.org/r/[email protected]
>>
>> I think there should be some knobs for customizing the styles.
>> But I don't know much about css.
>>
>> Can anybody restore the current look of kernel-doc HTML pages
>> in a sphinx-rtd-theme-1.0.0-compatible way?
>>
>> Sidenote:
>>
>> The change (html_css_files) actually works with
>> - Sphinx 1.7.9 + sphinx-rtd-theme 1.0.0
>>
>> This contradicts the Sphinx documentation saying that html_css_files
>> was new to Sphinx 1.8. This might be related to the changes in
>> sphinx-rtd-theme side, but I have no evidence.
>>
>> Any suggestion is welcome!
>
> thanks.
--
Jani Nikula, Intel Open Source Graphics Center
Em Sat, 27 Nov 2021 00:03:04 +0200
Jani Nikula <[email protected]> escreveu:
> On Fri, 26 Nov 2021, Randy Dunlap <[email protected]> wrote:
> > On 11/26/21 6:33 AM, Akira Yokosawa wrote:
> >> Hi Mauro,
> >>
> >> On Fri, Nov 26, 2021 at 11:50:53AM +0100, Mauro Carvalho Chehab wrote:
> >>> As described at:
> >>> https://stackoverflow.com/questions/23211695/modifying-content-width-of-the-sphinx-theme-read-the-docs
> >>>
> >>> since Sphinx 1.8, the standard way to setup a custom theme is
> >>> to use html_css_files. While using html_context is OK with RTD
> >>> 0.5.2, it doesn't work with 1.0.0, causing the theme to not load,
> >>> producing a very weird html.
> >>>
> >>> Tested with:
> >>> - Sphinx 2.4.4 + sphinx-rtd-theme 0.5.2
> >>> - Sphinx 2.4.4 + sphinx-rtd-theme 1.0.0
> >>> - Sphinx 4.3.0 + sphinx-rtd-theme 1.0.0
> >>>
> >>> Reported-by: Hans Verkuil <[email protected]>
> >>> Signed-off-by: Mauro Carvalho Chehab <[email protected]>
> >>> ---
> >>> Documentation/conf.py | 13 +++++++++----
> >>> 1 file changed, 9 insertions(+), 4 deletions(-)
> >>
> >> So I have an issue with this simple change.
> >> As I said to Jon in another thread [1], in which Jon didn't show any
> >> interest, this update changes the look of generated HTML pages
> >> (I should say) rather drastically, and it looks quite distracting
> >> for my eyes. The style might be acceptable for API documentations,
> >> but kernel-doc has abundant natural language contents.
> >
> > I agree 100% that the sans serif font is not desirable and not as
> > easy on the eyes as the serif font is.
> > Hopefully there is a way to change that.
That's actually a bug on my past patch. When html_css_files is used,
it should *not* contain "_static/" at the path. So, it should simply
be:
html_css_files = [
'theme_overrides.css',
]
Just sent a v2 fixing such issue.
>
> Taking a step back, choosing the sphinx-rtd-theme to begin with was
> purely arbitrary, I didn't put much effort into checking the
> alternatives, and as far as I recall, neither did Jon. There were more
> pressing issues at the time to get the documentation generation ball
> rolling at all.
>
> Obviously anyone can change the theme for themselves, and I guess the
> question is rather what the default is, and, subsequently, what gets
> used at [1].
>
> I haven't followed the development on this closely, but I am somewhat
> surprised at the amount of theme overrides having been added, and it
> begs the question whether there'd perhaps be a readily available stock
> theme that would be better suited than sphinx-rtd-theme?
I doubt we'll find one that everybody agrees on, but it sounds worth
discussing it.
One of the things with themes (and with supporting different Sphinx
versions) is that the look-and-feel changes over time, depending on the
specific versions that are used. I mean, newer versions of Sphinx come
with newer css classes, which sometimes replace the output of existing
tags.
So, except if either:
1. We stick with just a single Sphinx and theme version; or
2. someone has enough time to keep tracking on mapping each tag's output
to their css classes and ensure that the look-and-feel will remain
the same with all valid version combinations (I don't)
the output will differ depending on the changes at the theme and due
to Sphinx version-dependent output.
Btw, if we look at RTD change log:
https://sphinx-rtd-theme.readthedocs.io/en/stable/changelog.html
version 1.0.0 basically upgraded the theme to support:
- Sphinx 4.x
- Docutils 0.17
It also dropped support for Sphinx version < 1.6.
On other words, by sticking with a non-builtin theme, we may end
needing to apply version-dependent fixes from time to time - mostly
via css override stuff.
-
Perhaps one alternative to help with themes maintenance would be to
select one of the builtin themes from:
https://sphinx-themes.org/
if they're good enough and are present at the minimal Sphinx version
supported by Kernel documentation. The ones available on 1.7.9 are:
$ ls sphinx_1.7.9/lib/python3.10/site-packages/sphinx/themes
agogo bizstyle default haiku nonav scrolls traditional
basic classic epub nature pyramid sphinxdoc
They all are also the same themes available at the latest version.
If we're willing to do so, I did a quick test here. Those seems to
produce a reasonable output:
- bizstyle
- nature
- classic
If something would still be needed to change, the css override file could
still be used, but keeping it minimal helps to avoid the need of too
drastic changes.
Thanks,
Mauro
On 11/27/21 1:25 AM, Mauro Carvalho Chehab wrote:
> Em Sat, 27 Nov 2021 00:03:04 +0200
> Jani Nikula <[email protected]> escreveu:
>
>> On Fri, 26 Nov 2021, Randy Dunlap <[email protected]> wrote:
>>> On 11/26/21 6:33 AM, Akira Yokosawa wrote:
>>>> Hi Mauro,
>>>>
>>>> On Fri, Nov 26, 2021 at 11:50:53AM +0100, Mauro Carvalho Chehab wrote:
>>>>> As described at:
>>>>> https://stackoverflow.com/questions/23211695/modifying-content-width-of-the-sphinx-theme-read-the-docs
>>>>>
>>>>> since Sphinx 1.8, the standard way to setup a custom theme is
>>>>> to use html_css_files. While using html_context is OK with RTD
>>>>> 0.5.2, it doesn't work with 1.0.0, causing the theme to not load,
>>>>> producing a very weird html.
>>>>>
>>>>> Tested with:
>>>>> - Sphinx 2.4.4 + sphinx-rtd-theme 0.5.2
>>>>> - Sphinx 2.4.4 + sphinx-rtd-theme 1.0.0
>>>>> - Sphinx 4.3.0 + sphinx-rtd-theme 1.0.0
>>>>>
>>>>> Reported-by: Hans Verkuil <[email protected]>
>>>>> Signed-off-by: Mauro Carvalho Chehab <[email protected]>
>>>>> ---
>>>>> Documentation/conf.py | 13 +++++++++----
>>>>> 1 file changed, 9 insertions(+), 4 deletions(-)
>>>>
>>>> So I have an issue with this simple change.
>>>> As I said to Jon in another thread [1], in which Jon didn't show any
>>>> interest, this update changes the look of generated HTML pages
>>>> (I should say) rather drastically, and it looks quite distracting
>>>> for my eyes. The style might be acceptable for API documentations,
>>>> but kernel-doc has abundant natural language contents.
>>>
>>> I agree 100% that the sans serif font is not desirable and not as
>>> easy on the eyes as the serif font is.
>>> Hopefully there is a way to change that.
>
> That's actually a bug on my past patch. When html_css_files is used,
> it should *not* contain "_static/" at the path. So, it should simply
> be:
>
> html_css_files = [
> 'theme_overrides.css',
> ]
>
> Just sent a v2 fixing such issue.
>
Oh, thanks.
>>
>> Taking a step back, choosing the sphinx-rtd-theme to begin with was
>> purely arbitrary, I didn't put much effort into checking the
>> alternatives, and as far as I recall, neither did Jon. There were more
>> pressing issues at the time to get the documentation generation ball
>> rolling at all.
>>
>> Obviously anyone can change the theme for themselves, and I guess the
>> question is rather what the default is, and, subsequently, what gets
>> used at [1].
>>
>> I haven't followed the development on this closely, but I am somewhat
>> surprised at the amount of theme overrides having been added, and it
>> begs the question whether there'd perhaps be a readily available stock
>> theme that would be better suited than sphinx-rtd-theme?
>
> I doubt we'll find one that everybody agrees on, but it sounds worth
> discussing it.
>
> One of the things with themes (and with supporting different Sphinx
> versions) is that the look-and-feel changes over time, depending on the
> specific versions that are used. I mean, newer versions of Sphinx come
> with newer css classes, which sometimes replace the output of existing
> tags.
>
> So, except if either:
>
> 1. We stick with just a single Sphinx and theme version; or
>
> 2. someone has enough time to keep tracking on mapping each tag's output
> to their css classes and ensure that the look-and-feel will remain
> the same with all valid version combinations (I don't)
>
> the output will differ depending on the changes at the theme and due
> to Sphinx version-dependent output.
>
> Btw, if we look at RTD change log:
>
> https://sphinx-rtd-theme.readthedocs.io/en/stable/changelog.html
>
> version 1.0.0 basically upgraded the theme to support:
> - Sphinx 4.x
> - Docutils 0.17
>
> It also dropped support for Sphinx version < 1.6.
>
> On other words, by sticking with a non-builtin theme, we may end
> needing to apply version-dependent fixes from time to time - mostly
> via css override stuff.
>
> -
>
> Perhaps one alternative to help with themes maintenance would be to
> select one of the builtin themes from:
>
> https://sphinx-themes.org/
Looks to me like those are external to sphinx-doc.org. It says that
they are maintained by @pradyunsg and @shirou. (don't know who they are)
There are over 40 themes shown there.
OTOH, there is https://www.sphinx-doc.org/en/master/usage/theming.html#builtin-themes,
which shows about 12 builtin themes to choose from. Pretty much like the
list the you show just below here...
>
> if they're good enough and are present at the minimal Sphinx version
> supported by Kernel documentation. The ones available on 1.7.9 are:
>
> $ ls sphinx_1.7.9/lib/python3.10/site-packages/sphinx/themes
> agogo bizstyle default haiku nonav scrolls traditional
> basic classic epub nature pyramid sphinxdoc
>
> They all are also the same themes available at the latest version.
>
> If we're willing to do so, I did a quick test here. Those seems to
> produce a reasonable output:
>
> - bizstyle
> - nature
> - classic
Thanks for checking.
> If something would still be needed to change, the css override file could
> still be used, but keeping it minimal helps to avoid the need of too
> drastic changes.
I'll take a look...
--
~Randy
Jani Nikula <[email protected]> writes:
> Taking a step back, choosing the sphinx-rtd-theme to begin with was
> purely arbitrary, I didn't put much effort into checking the
> alternatives, and as far as I recall, neither did Jon. There were more
> pressing issues at the time to get the documentation generation ball
> rolling at all.
Yeah, I was just happy to see something that worked ... :)
> Obviously anyone can change the theme for themselves, and I guess the
> question is rather what the default is, and, subsequently, what gets
> used at [1].
>
> I haven't followed the development on this closely, but I am somewhat
> surprised at the amount of theme overrides having been added, and it
> begs the question whether there'd perhaps be a readily available stock
> theme that would be better suited than sphinx-rtd-theme?
I've never been hugely pleased with the appearance of the processed
docs, but haven't had a chance to tear into it. I'll try to look at the
themes Mauro pointed out in the near future.
Meanwhile, I'll go ahead and apply v2 of this patch, thanks.
jon
Em Sat, 27 Nov 2021 07:59:13 -0800
Randy Dunlap <[email protected]> escreveu:
> > Perhaps one alternative to help with themes maintenance would be to
> > select one of the builtin themes from:
> >
> > https://sphinx-themes.org/
>
> Looks to me like those are external to sphinx-doc.org. It says that
> they are maintained by @pradyunsg and @shirou. (don't know who they are)
> There are over 40 themes shown there.
>
> OTOH, there is https://www.sphinx-doc.org/en/master/usage/theming.html#builtin-themes,
> which shows about 12 builtin themes to choose from. Pretty much like the
> list the you show just below here...
>
> >
> > if they're good enough and are present at the minimal Sphinx version
> > supported by Kernel documentation. The ones available on 1.7.9 are:
> >
> > $ ls sphinx_1.7.9/lib/python3.10/site-packages/sphinx/themes
> > agogo bizstyle default haiku nonav scrolls traditional
> > basic classic epub nature pyramid sphinxdoc
> >
> > They all are also the same themes available at the latest version.
> >
> > If we're willing to do so, I did a quick test here. Those seems to
> > produce a reasonable output:
> >
> > - bizstyle
> > - nature
> > - classic
>
> Thanks for checking.
>
> > If something would still be needed to change, the css override file could
> > still be used, but keeping it minimal helps to avoid the need of too
> > drastic changes.
>
> I'll take a look...
Just sent a patch to help testing/using a different theme:
https://lore.kernel.org/lkml/8a33f4516c937556b9a38157e236b2f55ef67540.1638353179.git.mchehab+huawei@kernel.org/T/#u
After such patch, you could easily select a different theme during
documentation build, like:
$ make cleandocs
$ make SPHINXDIRS=input THEME=classic htmldocs
$ make SPHINXDIRS=i2c THEME=nature htmldocs
The patch disables the CSS overrides when a theme different than RTD
is used, as the CSS changes there may not be the best with other
themes. It probably make sense to split the contents of the
CSS override to a generic theme, which contains only things that
would apply to all themes (like font selection) from other things
that are theme-dependent, like colors.
Thanks,
Mauro