You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@pdfbox.apache.org by "Tres Finocchiaro (Jira)" <ji...@apache.org> on 2020/10/27 18:03:00 UTC
[jira] [Comment Edited] (PDFBOX-4709) PDFBox prints text poorly in
comparison to Adobe, Chrome, other apps
[ https://issues.apache.org/jira/browse/PDFBOX-4709?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17221622#comment-17221622 ]
Tres Finocchiaro edited comment on PDFBOX-4709 at 10/27/20, 6:02 PM:
---------------------------------------------------------------------
[~tilman] we're still actively working with the JDK support provider. We're able to get results that are improved, but still can't match the quality of Adobe.
Quoting:
{quote}The workaround solution would be to use {{graphics.drawString(),}} but this would work only on fonts based on type1 or truetype fonts.
{quote}
Since *drawString(...)* is a viable workaround which is a tradeoff between font accuracy and font compatibility (per ttf/type1 quote), is there a viable way (possibility via enhancement) to support *drawString()* as some type of advanced option? This way the user has the ability to choose one technique over the other. The solutions we're working on are better, but still none of them compare to the quality of drawString(), even when forcing a GDI precision value 10,000x. It's improved, but not as accurate as simply using drawString().
was (Author: tresf):
[~tilman] we're still actively working with the JDK support provider. We're able to get results that are improved, but still can't match the quality of Adobe.
Quoting:
{quote}The workaround solution would be to use {{graphics.drawString(),}} but this would work only on fonts based on type1 or truetype fonts.
{quote}
Since *drawString(...)* is a viable workaround which is a tradeoff between font accuracy and font compatibility (per ttf/type1 quote), is there a viable way to support *drawString()* as some type of advanced option? This way the user has the ability to choose one technique over the other. The solutions we're working on are better, but still none of them compare to the quality of drawString(), even when forcing a GDI precision value 10,000x. It's improved, but not as accurate as simply using drawString().
> PDFBox prints text poorly in comparison to Adobe, Chrome, other apps
> --------------------------------------------------------------------
>
> Key: PDFBOX-4709
> URL: https://issues.apache.org/jira/browse/PDFBOX-4709
> Project: PDFBox
> Issue Type: Bug
> Components: Rendering
> Affects Versions: 2.0.14
> Environment: Windows 10
> AdoptOpenJDK 11
> PDFBox 2.0.14
> Reporter: Lite M Finocchiaro
> Priority: Major
> Labels: Zebra
> Attachments: Adoberesult.jpg, Drug-print.pdf, Drug-print.pdf, IMG_20191219_130048_2.jpg, PDFBoxVSgraphicsobj.jpg, PDFBoxresult.jpg, PrintedWithPDFBox.pdf, Screen Shot 2019-12-22 at 2.20.54 PM.png, Screen Shot 2019-12-22 at 2.21.00 PM.png, linux-thermal-test-graphics-frc-4pt.pdf, linux-thermal-test-graphics-frc.pdf, linux-thermal-test-pdfbox-4pt.pdf
>
>
> When printing a PDF from PDFBox to a Zebra GK420d thermal label printer, the text from the PDF is blurry and appears to have the top and bottom cut off compared to printing the same file through Adobe Acrobat.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@pdfbox.apache.org
For additional commands, e-mail: dev-help@pdfbox.apache.org