Logo file path is converted to "TRUE" in typst extensions

[produnis]

Description

Hi there,
I have a new problem with my typst extensions.

My extension provides a logo at _extensions/hsnr-aushang/HSNRfb10s.png.
This worked just fine....
Now, after the summer break, I come back to see that it throws an error

[typst]: Compiling Beispiel.typ to Beispiel.pdf...error: file not found (searched at /home/produnis/minimal_examples/true)

The "logo" file path (see _extension.yml) is now overwritten to "true" instead.

If I set a "new" logo file in the qmd-document, it throws the same error, and "logo" is TRUE.

If I set the "new" logo to some fantasy-filename, it throws:

[typst]: Compiling Beispiel.typ to Beispiel.pdf...error: file not found (searched at /home/produnis/Dokumente/Programmierung/minimal_examples/HSNRfb10s.pngr)

So, the file name is "correct" (but as the file does not exist, it does not work).
But if I state a "real" existing file name, it goes back to "TRUE".

I set up a minimal (non) working example here:
https://github.com/produnis/minimal_examples/tree/typstlogo

I am on arch and tried it with quarto 1.8.24 and quarto-prerelease 1.9.2.

[mcanouil]

Did you check the Typst template/partials update from 1.8?
Unless you redefined everything (i.e., the whole template, not few partials) which is not the case in your extension, you need to ensure you account for changes at each update: https://quarto.org/docs/journals/templates.html#typst-partials

[mcanouil]

I am willing to redefine everything, but I have no clue what exactly changed since 1.8 or where to look.

Reading the changelog is not as optional for developers as it could be for users: https://quarto.org/docs/download/

[produnis]

hmmm. I am sorry....
I dont get a clue from that.
I can see from the change log that there is a discussion about logos in typst here #12180
But as an autodidact and just-hobby-coder, I need a "working example" to adapt it to my code...
I dont know where to change what....

[mcanouil]

Don't apologise, there is no reason for.

The changelog is actually missing an entry on top of the autocomplete for logo.

See the partials documentation: https://quarto.org/docs/journals/templates.html#typst-partials

page.typ
Sets properties of the page such as size, margin, numbering, and background logo.

You can also look at the code of the partials, in addition to reading the changelog: https://github.com/quarto-dev/quarto-cli/tree/main/src/resources/formats/typst/pandoc/quarto

Then you need to either overwrite Quarto's changes, or change your code to use that, for instance see how the logo is used in page.typ partial and in typst-show.typ declaration partial.

[mcanouil]

for instance see how the logo is used in page.typ partial and in typst-show.typ declaration partial.

It's not in typst-show.typ because the logo uses the schema at Quarto level and in your extension you defined a new logo parameter which conflicts with Quarto's logo.

logo is no longer a scalar.

• quarto-cli/src/resources/formats/typst/pandoc/quarto/page.typ

  Lines 6 to 8 in 0eda022

  	$if(logo)$
  	#set page(background: align($logo.location$, box(inset: $logo.inset$, image("$logo.path$", width: $logo.width$$if(logo.alt)$, alt: "$logo.alt$"$endif$))))
  	$endif$

[produnis]

thanks!!! as a dirty workaround, I change "logo" to "mylogo" and avereything works again (yeeeha, I have to give lectures in about 2 hours and somehow paniked that I cannot have handouts for the students).
Later this day I will have time to dive deeper into it and convert my extensions according to the quarto way.
:)
Thx, dude, that really helped me out!

[mcanouil]

Hopefully, in the future there will be a way to test extensions on development version of Quarto to help prevent breakage earlier.

[cscheid]

Hopefully, in the future there will be a way to test extensions on development version of Quarto to help prevent breakage earlier.

In principle, we do this right now through the release candidate versions; it's possible that as a project, we need to communicate these versions more explicitly and loudly, and have explicit waiting periods between that and a full release.

[mcanouil]

I meant a more automatic way, such as a GitHub action, etc.

I will resume my work on something related in the coming weeks hopefully:

• ci: add test workflow for Quarto extensions mcanouil/quarto-extensions#188 (not fully up to date)