[ 
https://issues.apache.org/jira/browse/PDFBOX-678?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14088261#comment-14088261
 ] 

ASF subversion and git services commented on PDFBOX-678:
--------------------------------------------------------

Commit 1616350 from [~jahewson] in branch 'pdfbox/trunk'
[ https://svn.apache.org/r1616350 ]

PDFBOX-678: fix build

> Support missing Text Rendering Modes when rendering a PDF
> ---------------------------------------------------------
>
>                 Key: PDFBOX-678
>                 URL: https://issues.apache.org/jira/browse/PDFBOX-678
>             Project: PDFBox
>          Issue Type: Improvement
>          Components: Rendering
>            Reporter: Maruan Sahyoun
>            Assignee: John Hewson
>         Attachments: Java Printing.pdf, TextRenderingModes.java.patch, 
> example_026.pdf
>
>
> Of the 7 different Text Rendering Modes only mode 0 (Fill Text) is correctly 
> implemented. Mode 1 (Stroke Text) falls back to Mode 0 and the others are not 
> implemented. I'm looking to implement the missing modes (at least some of 
> them).
> Before doing so I'm proposing a structural change to when rendering really 
> occurs. Currently it's done within the PDxxxFont classes. I'd rather 
> implement the (AWT) text output in PageDrawer (or helper classes within the 
> same package) and use the font classes to return an AWT font by adding a 
> getAwtFont method. Doing so we get a better separation between the PDF 
> related stuff (PDxxx) and applications like PageDrawer. The current rendering 
> specific code within the PDxxxFont classes can be retained for compatibility 
> and marked deprecated at a later stage.
> WDYT?



--
This message was sent by Atlassian JIRA
(v6.2#6252)

Reply via email to