Too much PreFigure?

[Rob Beezer]

Likely just for David A. I had to build a PDF for a single PreFigure diagram,
so the LateX version would build. When I used the "-f pdf" switch, I also got
changes to the diagcess SVG.

Now, maybe those changes should happen. I did not merge them, you know which
example I mean. I think it also means the current state of the repository is
such that you can reproduce my work and see the existing SVG change.

But the question is - if I request PDF, shouldn't that be all I get? Is there
some logic in our Python or in the PF library that needs a tweak?

Rob

[David Austin]

I saw the subject line and couldn't imagine too much PreFigure, but I have to agree.  When we allowed SVGs to proliferate to address sizing issues with annotated diagrams rendered by diagcess, I neglected to clean up the *-diagcess SVG in the PDF and PNG builds.  That is fixed in the latest release of prefig.  Nothing needs to change in the prefigure_conversion function in pretext.py and no need to merge the extra *-diagcess.svg.  The PDF you generated looks good.

Sincerely,

"Another contributor"

--
You received this message because you are subscribed to the Google Groups "PreTeXt development" group.
To unsubscribe from this group and stop receiving emails from it, send an email to pretext-dev...@googlegroups.com.
To view this discussion visit https://groups.google.com/d/msgid/pretext-dev/MTAwMDAyMC5iZWV6ZXI.1776020706%40pnsh.