And the biggest thing to keep in mind is that text rendering still needs to move the pen even when the current OCG is off.
On 7/4/14, 12:38 PM, "John Hewson (JIRA)" <[email protected]> wrote: > > [ >https://issues.apache.org/jira/browse/PDFBOX-678?page=com.atlassian.jira.p >lugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14052550#com >ment-14052550 ] > >John Hewson commented on PDFBOX-678: >------------------------------------ > >We should do this, but not until after AWT text rendering is removed, >which will be very soon. > >> 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 >> Attachments: Java Printing.pdf, TextRenderingModes.java.patch >> >> >> 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)
