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

Tilman Hausherr commented on PDFBOX-4556:
-----------------------------------------

No, BC is not used for the visual representation, BC is for the crypto stuff 
both when visual and not visual.

C# is not supported by the PDFBox team. See also your previous issue why 
signing doesn't work on C# with IKVM. And why you shouldn't use IKVM in a 
project at all.

The CreateVisibleSignature and CreateVisibleSignature2 examples are what you 
should follow. The second one is easier to understand. Have a look at the 
method {{createVisualSignatureTemplate}}. This creates a template that is then 
passed to {{signatureOptions.setVisualSignature()}}. That is what you did, but 
at least one of your modifications was wrong, see my comment. You should start 
with the unmodified example and get that one to run.

However the CreateVisibleSignature2 example doesn't exist in 1.8. There are no 
plans to port it to 1.8. (It might still work, but one doesn't know for sure) 
The 1.8 version is only maintained, not improved. If you insist on using 1.8 
then you should use the CreateVisibleSignature example that exists, i.e. see if 
it runs or not. It is somewhat inflexible (doesn't support text in signature) 
and hard to understand / debug, due to the usage of design patterns.

> how the visual representation of the signature is achieved  
> ------------------------------------------------------------
>
>                 Key: PDFBOX-4556
>                 URL: https://issues.apache.org/jira/browse/PDFBOX-4556
>             Project: PDFBox
>          Issue Type: Wish
>          Components: .NET
>    Affects Versions: 1.8.16
>            Reporter: bal
>            Priority: Major
>




--
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