[
https://issues.apache.org/jira/browse/PDFBOX-678?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12864712#action_12864712
]
Maruan Sahyoun commented on PDFBOX-678:
---------------------------------------
To answer your question. I'm planning to use TextLayout objects only for the
added functionality mainly to get an outline of the text.
For Type3 there will be a fall back to the old behaviour as will for all Fonts
where getawtFont ist not available.
The issue with c) is that adding the outline of the text object via
PageDrawer.setClippingPath will cut off the outline stroke (i.e. the user
visible outline) as this is drawn 'outside' of the outline itself which brings
me back to b). But maybe you have another idea to get around that.
Other than that the basic implementation of the rendering modes is done and the
samples I have (generated by iText)
fox_dog_render.pdf
text_operators.pdf
are rendered the same as with Adobe Reader 9.
> 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: PDFReader
> Reporter: Maruan Sahyoun
>
> 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 is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
