PDF diagram get a weird header

[PierreSolomon]

Hello,

I'm using the extension with a pdf output, the diagram once writen to a pdf file get a header with the word "root". Is there a way to remove it?

I'm using the latest version of quarto (pre-release) and the latest version of the extension on windows 11.

diagram-1.pdf

Thank you in advance for the help!

[rcannood]

Hi @PierreSolomon !

Could you provide the full source qmd you used to generate the PDF?

Kind regards,
Robrecht

[PierreSolomon]

Hello,
I can't provide the full source as it concern the thesis I'm redacting actually. But I have the same problem with a qmd document containing:

---
title: "Untitled"
format: pdf
filters:
  - d2
---

```{.d2}
x -> y
```

It give the document next: test.pdf

Also, I am not sure why but the pdf refused to render at first because the d2 svg/pdf was not created. I needed to first compile to the docx format and then to pdf:

==> quarto preview test.qmd --to pdf --no-watch-inputs --no-browse

pandoc 
  to: latex
  output-file: test.tex
  standalone: true
  pdf-engine: xelatex
  variables:
    graphics: true
    tables: true
  default-image-extension: pdf
  
metadata
  documentclass: scrartcl
  classoption:
    - DIV=11
    - numbers=noendperiod
  papersize: letter
  header-includes:
    - '\KOMAoption{captions}{tableheading}'
  block-headings: true
  title: Untitled
  
La syntaxe de la commande n'est pas correcte.
err: failed to compile ..\..\AppData\Local\Temp\svg-convert-97090f7710e56e36\temp_1.txt: open C:\Users\E142543N\Downloads\Nouveau dossier\images\diagram-1.pdf: The system cannot find the path specified.

Rendering PDF
running xelatex - 1
  This is XeTeX, Version 3.141592653-2.6-0.999994 (TeX Live 2022) (preloaded format=xelatex)
   restricted \write18 enabled.
  entering extended mode
  
updating tlmgr

updating existing packages
ERROR: 
compilation failed- error
Unable to load picture or PDF file './images/diagram-1.pdf'.
<to be read again> 
                   }
l.146 \includegraphics{./images/diagram-1.pdf}
                                               

see test.log for more information.