public inbox for docs@lists.yoctoproject.org
 help / color / mirror / Atom feed
From: Quentin Schulz <quentin.schulz@cherry.de>
To: antonin.godard@bootlin.com, docs@lists.yoctoproject.org
Cc: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
Subject: Re: [docs] [PATCH 2/5] Makefile: fix rsvg-convert --format capitalization
Date: Fri, 5 Dec 2025 16:03:55 +0100	[thread overview]
Message-ID: <e81c4d94-7666-4cf1-bba6-9a4a2ea4d4db@cherry.de> (raw)
In-Reply-To: <20251205-build-docs-container-tlmgr-v1-2-de30623e664d@bootlin.com>

Hi Antonin,

On 12/5/25 3:51 PM, Antonin Godard via lists.yoctoproject.org wrote:
> On some versions of rsvg-convert, capitalized formats are unknown.
> 
> For example on CentOS Stream 9:
> 
>    $ rsvg-convert --format=Png --output=ref-manual/svg/releases.png ref-manual/svg/releases.svg
>    Unknown output format.
> 
> While the same command with "png" runs fine.
> 
> On Ubuntu 22.04, both are accepted.
> 
> Switch to the un-capitalized options, compatible with all versions.
> 

rsvg-convert doc only mentions all lowercase format options, so looks 
fine to me

Reviewed-by: Quentin Schulz <quentin.schulz@cherry.de>

FYI, --format=pdf is a "moving" target, that is it isn't always the same 
PDF version depending on rsvg-convert's own version. They mention it can 
be an issue with some latexpdf versions only supporting older PDF 
versions. See 
https://github.com/GNOME/librsvg/blob/main/rsvg-convert.rst#pdf-versions

At least you're aware of it now, no idea if we should be doing something 
about it. I guess we could try to be smart and detect the max PDF 
version supported by latexmk at runtime and select the pdf version for 
rsvg-convert based on that.

Thanks!
Quentin


  reply	other threads:[~2025-12-05 15:04 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-12-05 14:51 [PATCH 0/5] Add missing CentOS Stream / RockyLinux distros to the system-requirements.rst doc Antonin Godard
2025-12-05 14:51 ` [PATCH 1/5] tools/build-docs-container: move container files in their own directory Antonin Godard
2025-12-05 14:51 ` [PATCH 2/5] Makefile: fix rsvg-convert --format capitalization Antonin Godard
2025-12-05 15:03   ` Quentin Schulz [this message]
2025-12-05 14:51 ` [PATCH 3/5] tools/build-docs-container: add CentOS Stream 9 support Antonin Godard
2025-12-05 15:29   ` [docs] " Quentin Schulz
2025-12-11  8:13     ` Antonin Godard
2025-12-05 14:51 ` [PATCH 4/5] ref-manual/system-requirements.rst: fix AlmaLinux PDF build Antonin Godard
2025-12-05 14:51 ` [PATCH 5/5] ref-manual/system-requirements.rst: add RockyLinux install instructions Antonin Godard

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=e81c4d94-7666-4cf1-bba6-9a4a2ea4d4db@cherry.de \
    --to=quentin.schulz@cherry.de \
    --cc=antonin.godard@bootlin.com \
    --cc=docs@lists.yoctoproject.org \
    --cc=thomas.petazzoni@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox