All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Nicolas Dechesne" <nicolas.dechesne@linaro.org>
To: Michael Opdenacker <michael.opdenacker@bootlin.com>
Cc: YP docs mailing list <docs@lists.yoctoproject.org>
Subject: Re: [docs] Vector sources for the manual figures ?
Date: Thu, 22 Apr 2021 09:58:55 +0200	[thread overview]
Message-ID: <CAP71WjxRhwcrzjKh8gKTiuby1HBtMn0C-ikkHXM2WrRt=Qm75A@mail.gmail.com> (raw)
In-Reply-To: <7f2f05a5-7492-ff74-e756-09937f59643f@bootlin.com>

[-- Attachment #1: Type: text/plain, Size: 1446 bytes --]

hey Michael,

On Tue, Apr 20, 2021 at 6:10 PM Michael Opdenacker <
michael.opdenacker@bootlin.com> wrote:

> Greetings,
>
> In the YP manual sources, all the figures are in PNG format. Except for
> screenshots, that's far from ideal for high resolution printing and
> viewing!
>
> Don't we have vector sources of such diagrams anywhere, so that I can
> export them to SVG? Don't tell me they were lost during the migration to
> Egypt. I mean the migration to Sphinx ;-P
>

Nothing was lost/destroyed as part of the migration for sure. And we use
git, so nothing can be lost anyways.
I've used the .png files since they were used in the docbook docs, and
available in yocto-docs, but I am not aware if the 'sources' for these PNG
were some actual SVG.


>
> In particular, I'm asking because I managed to find a way to see the
> figures in full-width in the epub output (using my KOBO reader to read
> the manuals when I'm not in front of my computer, but the figures are
> always too small and therefore unreadable). You just need to add
> ":width: 100%" to each image insertion, and this doesn't seem to disturb
> the HTML output which already looks correct.
>
> I'll propose a patch soon, but the results would be even better with
> vector figures :)
>
> Thanks in advance,
>
> Michael.
>
> --
> Michael Opdenacker, Bootlin
> Embedded Linux and Kernel engineering
> https://bootlin.com
>
>
> 
>
>

[-- Attachment #2: Type: text/html, Size: 2109 bytes --]

  reply	other threads:[~2021-04-22  7:59 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-04-20 16:10 Vector sources for the manual figures ? Michael Opdenacker
2021-04-22  7:58 ` Nicolas Dechesne [this message]
2021-04-22  9:13 ` [docs] " Richard Purdie
2021-04-22 12:50   ` 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='CAP71WjxRhwcrzjKh8gKTiuby1HBtMn0C-ikkHXM2WrRt=Qm75A@mail.gmail.com' \
    --to=nicolas.dechesne@linaro.org \
    --cc=docs@lists.yoctoproject.org \
    --cc=michael.opdenacker@bootlin.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.