search

pandoc / dockerfiles

Dockerfiles for various pandoc images
GNU General Public License v2.0
372 stars 100 forks source link

SVG URLs not rendering in PDF #250

Open casperdcl opened 4 days ago

casperdcl commented 4 days ago

Source: https://github.com/casperdcl/test/tree/refs/heads/pandoc-test

![](https://img.shields.io/badge/test-pandoc-green.svg)

Expected: pandoc -s -t pdf should work fine

Got: PDF art[ie]fact downloadable from https://github.com/casperdcl/test/actions/runs/11659385994

image

jgm commented 3 days ago

This works fine for me when I try it locally. What version of pandoc are you using? If you're running it in an action, is rsvg-convert available?

tarleb commented 3 days ago

I can confirm this behavior for pandoc/latex:latest-alpine, but it works fine for pandoc/latex:latest-ubuntu. Graphic libraries seem to have problems when compiled against musl. See, e.g., reports of very elongated images produced by graphviz on Alpine.

Please use a Ubuntu-base image, there's nothing we can do about this on our end.

tarleb commented 3 days ago

On second thought, maybe we should consider to make Ubuntu-based images the default, so pandoc/core:latest would become an alias for pandoc/core:latest-ubuntu instead of pandoc/core:latest-alpine.

daamien commented 1 day ago

On second thought, maybe we should consider to make Ubuntu-based images the default, so pandoc/core:latest would become an alias for pandoc/core:latest-ubuntu instead of pandoc/core:latest-alpine.

Seems like a huge change to me because we would also have to point the latest tag to ubuntu on the other images too, otherwise it would be kind of a mess.... Overall that could break thousands of CI pipelines and other workflows....

tarleb commented 1 day ago

Indeed, it would induce a lot of breakage, so this step would have to be well-planned, well-documented, and widely announced.

There's another reason why I'm tempted to do that in the future: we don't have LaTeX images for Alpine on arm64. I see that as a serious problem, as the default template should be the most general, and it should not come with a list of platform limitations and asterisks.

I've also been toying the idea to move from Ubuntu to Debian at some point, simply because Debian seems a bit more stable and closer to the traditional free software spirit. If we do that, then that might be a good opportunity to change the default as well.