1.3: Other formats links on HTML of book point to index.pdf and index.epub, how to change that?

[fuhrmanator]

Happy 2023!

My book project is now using Quarto 1.3 and I saw that by default the web page has "other formats" links to the PDF and Epub. That's practical:

However, they're broken links because they point to index.pdf and index.epub, which are not the files generated in my _quarto.yml.

The generated PDF is Analyse-et-conception-de-logiciels.pdf and I suspect the filename is automagically derived from the title:

book:
  title: "Analyse et conception de logiciels"

How can I fix this? I couldn't find anything in the documentation.

ETA: my project is at https://github.com/fuhrmanator/log210-ndc-quarto and built to https://fuhrmanator.github.io/log210-ndc-quarto/

[dragonstyle]

I know that you're using a slightly older version of 1.3 due to a regression in later 1.3 builds, but unfortunately, this is a bug that is fixed in later builds... If you update to the latest version of 1.3.86 (available now), it should contain fixes for the regression and also this issue. Sorry for the instability, it was unintentional but we're adding tests as we catch these cases that we've missed to try to prevent this in the future!

[dragonstyle]

There is indeed an issue with cross references inside callouts, opening an issue for that.

[fuhrmanator]

Hmmm, I just rendered log210-ndc-quarto locally and didn't run into the issue with corruption. I did see these three warnings:

[WARNING] Citeproc: citation fig-LucidchartUML not found
[WARNING] Citeproc: citation fig-MDD-ErreurDescription not found
[WARNING] Citeproc: citation fig-dssdetails not found

which I will take a look at.

Are there LaTeX intermediates or anything else that might be causing the issue on your machine but not on a clean enlistment of the repo?

I updated to 1.3.90 this AM and the errors/warnings still show in Windows. However, quarto finally generates a (corrupt) PDF. The problems seem to be with the figures. I'm using MiKTeX on my Windows 10, from Visual Studio Code, in a bash shell (gitbash), not CMD.exe, if that matters.

So far, the rater (bitmap) images are OK. It's the SVG and PlantUML (SVG) figures that don't render properly. I get errors in the viewer saying certain pages can't be rendered. Here are two figures that show trouble (the first is a filter-generated SVG from PlantUML, the second is a SVG done in Inkscape):

[dragonstyle]

Was this working in previous versions of Quarto? The fact that it is affecting SVG images is making me wonder if the issue has to do with the environment (for example not having rsvg-convert available).

[fuhrmanator]

There is indeed an issue with cross references inside callouts, opening an issue for that.

FYI it appears that 1.3.91 (running on the CI of my book) fixes this problem. Thanks for the quick fix (if it's indeed that).

[cscheid]

Yes, that was a bug I introduced with a (large, under-the-hood) change in how quarto processes documents. Glad to hear it fixed the problem! (@dragonstyle: this was an AST bug.)

[fuhrmanator]

Yes it was working in 1.2, prior to the bug with duplicate svgs (discussed in thread about corrupt PDFs). It also worked in the early version of 1.3, but broke when I moved to the 1.3 version that fixed the download links mentioned in this discussion.

…

On Fri, Jan 6, 2023, 13:28 Charles Teague ***@***.***> wrote: Was this working in previous versions of Quarto? The fact that it is affecting SVG images is making me wonder if the issue has to do with the environment (for example not having rsvg-convert available). — Reply to this email directly, view it on GitHub <#3866 (reply in thread)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AB2BCDBBIOVFS4KNTTYLCS3WRBP6NANCNFSM6AAAAAATSLK4TE> . You are receiving this because you authored the thread.Message ID: ***@***.***>

[fuhrmanator]

To be specific (I was away from my PC before): it was 1.2.233 that worked on Windows with latexmk and svg files.

It's 1.3.24 that works (in Windows) for me, and so I've rolled back to it, leaving the more recent version on the CI. Since the web site and PDF download are built by CI (which uses linux) I can live with this compromise for the time being (just need to check PDF changes locally as I make them in branches of the book project).