From: John Snow <jsnow@redhat.com>
To: Peter Maydell <peter.maydell@linaro.org>
Cc: QEMU Developers <qemu-devel@nongnu.org>,
Eduardo Habkost <ehabkost@redhat.com>,
Gabriel Barreto <sbarreto.gabriel@gmail.com>
Subject: Re: [Qemu-devel] GSoC project: API Documentation Generation links and comments
Date: Tue, 27 Aug 2019 17:01:18 -0400 [thread overview]
Message-ID: <ca896264-89fc-bcb6-9e21-b411bd4f9a01@redhat.com> (raw)
In-Reply-To: <CAFEAcA-Faa7j+Dv0L5KPDDwuEvaRMNYNeUNzB8p=ceD3vhyzDw@mail.gmail.com>
On 8/27/19 4:56 PM, Peter Maydell wrote:
> On Tue, 27 Aug 2019 at 21:52, John Snow <jsnow@redhat.com> wrote:
>> - For theming, I'm a fan of the RTD theme, because I think it makes the
>> TOC tree stand out better and makes for nicer browsing than the default
>> alabaster theme. Maybe when there's a better over-arching TOC laid out
>> with better organization we could see which themes the list likes best.
>
> FWIW, for the in-tree doc generation I opted for Alabaster
> (though I prefer RTD's look as well) because Alabaster doesn't
> require shipping any fonts, whereas RTD does, and it seemed
> easier to sidestep any questions about whether a font file in the
> docs was mere aggregation or not. For "putting docs up on the
What do you mean by "mere aggregation"?
> website" this doesn't apply so much, I think. Awkwardly, the
> two themes aren't completely drop-in replacements, though:
> I found that some of the tweaks needed for stuff like the
> sidebar to come out the way I wanted were theme-specific.
>
That's... unfortunate. I've been playing around with RTD and Alabaster
for a hobby project, but hadn't noticed anything too different yet.
Of course, QEMU is gigantic and it is an edge-case magnet.
--js
next prev parent reply other threads:[~2019-08-27 21:02 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-08-26 18:51 [Qemu-devel] GSoC project: API Documentation Generation links and comments Gabriel Barreto
2019-08-27 20:52 ` John Snow
2019-08-27 20:56 ` Peter Maydell
2019-08-27 21:01 ` John Snow [this message]
2019-09-03 8:21 ` Peter Maydell
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=ca896264-89fc-bcb6-9e21-b411bd4f9a01@redhat.com \
--to=jsnow@redhat.com \
--cc=ehabkost@redhat.com \
--cc=peter.maydell@linaro.org \
--cc=qemu-devel@nongnu.org \
--cc=sbarreto.gabriel@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).