From: Michael Opdenacker <michael.opdenacker@bootlin.com>
To: Quentin Schulz <quentin.schulz@theobroma-systems.com>
Cc: docs@lists.yoctoproject.org
Subject: Re: [docs] [PATCH 3/4] overview-manual: SVG diagram for the git workflow
Date: Thu, 7 Oct 2021 15:35:30 +0200 [thread overview]
Message-ID: <9de748ab-3704-96a5-e8e6-06fe316067bb@bootlin.com> (raw)
In-Reply-To: <20211007124253.jx6pgewhaiwako7q@fedora>
Hi Quentin,
On 10/7/21 2:42 PM, Quentin Schulz wrote:
>
>>
>> -.. image:: figures/git-workflow.png
>> - :align: center
>> +.. image:: svg/git-workflow.*
> I guess this is due to HTML rendering including SVG but epub using a png
> created by inkscape?
Right.
>
> We could add a comment for this maybe?
Yes, but maybe in a central place that will explain how to add images.
This may be too verbose to repeat a comment every time we include an image.
>
> Does this work well if you do the following:
>
> $ make latexpdf
> $ make html
>
> for the html to use the svg and not the png created by inkscape?
>
> Otherwise not much to add :)
Yes, it works. Actually, the HTML export seems to prefer SVG over PNG by
default (from my experiments, and as claimed by
https://newbedev.com/using-sphinx-docs-how-can-i-specify-png-image-formats-for-html-builds-and-pdf-image-formats-for-latex-pdf-builds).
We may change this by tuning
|StandaloneHTMLBuilder.supported_image_types in conf.py, but since the
default is fine, I'd say that no extra setting is required.|
|Cheers, Michael.|
--
Michael Opdenacker, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
next prev parent reply other threads:[~2021-10-07 13:35 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <16834414503E8A25.21857@lists.yoctoproject.org>
2021-10-06 12:22 ` [PATCH 1/4] Makefile: allow epub and latexpdf outputs to use diagrams from SVG sources Michael Opdenacker
2021-10-06 12:22 ` [PATCH 2/4] conf.py: use PNG first in EPUB output Michael Opdenacker
2021-10-06 12:22 ` [PATCH 3/4] overview-manual: SVG diagram for the git workflow Michael Opdenacker
2021-10-07 12:42 ` [docs] " Quentin Schulz
2021-10-07 13:32 ` Quentin Schulz
2021-10-07 13:41 ` Michael Opdenacker
2021-10-07 13:35 ` Michael Opdenacker [this message]
2021-10-06 12:22 ` [PATCH 4/4] docs: add "make all" to build old types of docs (html, epub, pdf) at once Michael Opdenacker
2021-10-06 14:48 ` [docs] [PATCH 1/4] Makefile: allow epub and latexpdf outputs to use diagrams from SVG sources Nicolas Dechesne
2021-10-06 19:07 ` Michael Opdenacker
2021-10-07 11:05 ` Quentin Schulz
2021-10-07 12:33 ` Michael Opdenacker
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=9de748ab-3704-96a5-e8e6-06fe316067bb@bootlin.com \
--to=michael.opdenacker@bootlin.com \
--cc=docs@lists.yoctoproject.org \
--cc=quentin.schulz@theobroma-systems.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.