Thomas Leitner

@theasteve Have a look at the http://prawnpdf.org/manual.pdf, pages 57 and 58.

@pmverma In the link you referenced is the mention of font shaping. Prawn doesn't do font shaping since that is quite a complex topic. So if the combination is done...

@pointlessone Really? But how does it do ligatures like 'll' then?

Ah, you are right, I thought about kerning which Prawn supports. The standard 14 PDF fonts partially support ligatures, e.g. Times-Roman supports `f i -> fi`, and I thought that...

@petergoldstein @pointlessone Wouldn't it be more "correct" to use the master branch of each repo in the CI pipeline instead of the released versions?

@petergoldstein I understand what you are saying but I think the exception you mentioned comes into play here since pdf-core and prawn are interdependent, as can be seen by this...

I'm closing this since it doesn't seem to be worked on and it seems that the opinions on whether this is actually a problem differs. For myself, I wouldn't factor...

@cristianpaul0 Just a heads up: The [devel branch](github.com/gettalong/hexapdf/tree/devel) contains changes to more easily support external signing. To this end I have added a PKCS#7/CMS signed data object builder that allows...

@jotolo You are correct that PKCS#1 signatures are deprecated. However, you should be able to create a PAdES/CMS signature using one of the rsa-sign-pkcs1-{2048,3072,4096}-{sha256,sha512} RSA signing keys . The resulting...

@jotolo Thanks for confirming that this works! :smile: I will add some documentation to https://hexapdf.gettalong.org/documentation/digital-signatures/signing-pdfs-howto.html