PDF created by integration not same as PDF from "MS Print to PDF"
Purpose of creating a PDF is to pass it to Vericut so a Cutter/Plotter can cut out a Stencil. The label template uses TTF "Stencil Gothic JL" in Bold at size 22.
PDF file created by our Bartender Integration looks correct in MS Edge but when importing the that PDF file into Vericut the font changes.
Oddly, if we view the PDF in Edge and then “Print to PDF” using “MS Print to PDF”, the new file created imports into Vericut with the correct Font intact.
What is the difference between the integration PDF generation and MS Print to PDF? How can I make our integration PDF more like the MS Print version so that Vericut will maintain the desired font?
Thanks,
Darron
-
Set the driver in the Integration to the MS Print to PDF driver rather than Seagulls inbuilt PDF driver and see what that does
0 -
I don't see how I can set the integration to use MS Print to PDF.
0 -
I don't see an option to get the integration to automatically use MS Print to PDF.
Also, is there a parameter I can pass to the integration to make it overwrite existing file and not append numbers to make it unique? I pass it the PRNFILE parameter to tell it where to create the file and how to name it, but I need to also tell it to overwrite without having to modify 200 different printer templates. I'm currently passing /D /PRN /PRNFILE /P /C /R /Close /DD
0
Please sign in to leave a comment.
Comments
3 comments