I've set the PDF Service Manager back to version 1...
# cfml-general
a
I've set the PDF Service Manager back to version 1 as a "fix" for now. This changes the value of the engine node from “pdfReactor“ to “WebKit” in /cfusion/lib/neo-document.xml
m
CF23 introduced a new PDF engine which supports modern HTML/CSS + JS/SVG etc. It is a more pixel-perfect solution. However, older code which was "tweaked" to align things in the old engine may break visually in the new one, as those tweaks will now be accurately represented on screen (instead of band-aiding items into place in the old engine).
a
Thanks @Mark Takata (Adobe) - I don't need anything like a complete list, but do you have maybe one or two anecdotal examples of what would constitute a "tweak"? I seem to recall that we couldn't have as much inline declaration, and moved everything to a grouping in a style tag above all the content. But I'm not sure what kind of tweak to look for. I was suspecting that we were seeing CF-4198045 or CF-4211032 in our case...
@Mark Takata (Adobe) Here's an example of our "legacy" or desired output, showing a complete week
@Mark Takata (Adobe) And here's the PDFRefactor version, in which some double quotes have appeared, and the week is chopped off
Anywhoo, changing the version to 1 will buy us the time we need to dig in and see what parts of this we can solve under the status quo, and what parts might fix themselves with a future update.
m
pretty sure i had to specify the margins to reduce them down to match the previous version. also, pdf reactor does support pseudo elements like ::before and ::after, blockquote with pseudo element putting in quotes around a p would look like what yours looks like.