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

Andrew Hung commented on PDFBOX-4437:
-------------------------------------

1) Any ideas how I should be handling the key attribute of the STREAM, as I'm 
not sure how to add this using
{code:java}
setItem(COSName key, COSBase value)
{code}
since unable to create new COSName with the actual key attribute, which I know 
is wrong but not clear what proper way to handle it right now.

2) Should be calling close() after I've completed adding items to the COSStream 
and COSDictionary, or does not need to be handled?

> Import XFDF stamp annotation loses appearance
> ---------------------------------------------
>
>                 Key: PDFBOX-4437
>                 URL: https://issues.apache.org/jira/browse/PDFBOX-4437
>             Project: PDFBox
>          Issue Type: Bug
>          Components: PDModel
>    Affects Versions: 2.0.9, 2.0.10, 2.0.11, 2.0.12, 2.0.13
>            Reporter: Andrew Hung
>            Priority: Major
>         Attachments: A1.01 - MYLES - 2ND-4TH  FLOOR PLAN.pdf, 
> FDFAnnotationStamp.java, FDFAnnotationStamp2.java, 
> Stamp_appearance_decoded.txt, ap.xml, stamp_annotation.xfdf, xfdf stamp 
> annotation to PDF.zip
>
>
> When loading an XFDF which has a stamp annotation which contains an 
> appearance element after added to the PDF in place of the annotation is an 
> box with an X.
> Reviewing the FDFAnnotationStamp class, it skips all internal elements.  Is 
> there any development being done to enhance this?
> I've attached "xfdf stamp annotation to PDF.zip" which has an example, if you 
> open the stamp_annot.xfdf it will show on the PDF.  While using PDFBox API 
> the only piece missing is the appearance of the stamp.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to