If I run multiple threads that attempt to create a PDF and add some text
with an embedded Type1 font, an EndOfStreamException exception is throw in
RandomAccessFileOrArray. Sample code:
static void Main(string[] args)
{
Font font = FontFactory.GetFont("c:\\windows\\fonts\\KozGoProVI-Medium.otf",
Hi Michael,
thanks for clarify this, much appreciated.
Regards,
Andrea
--
View this message in context:
http://itext-general.2136553.n4.nabble.com/Encrypt-without-owner-password-and-random-password-generation-tp4659839p4659849.html
Sent from the iText - General mailing list archive at Nabble.co
I found what seemed a little discrepancy with the spec and I asked why,
that's it.
I spent time re-reading the spec, comparing it with your implementation and
writing a detailed email because I thought it was useful for me to
understand it but might also be good for iText.. you know, an healthy
di
Andrea wrote
> I don't think your argument is valid, according to it you could, absurdly,
> always replace the owner password with a random string (even when the user
> provided it) and still strictly don't contradict the spec (there is an
> owner password, *a random string*, algorithm 3.3 applies)
Andrea,
Andrea wrote
> I found what seemed a little discrepancy with the spec and I asked why,
> that's it.
> I spent time re-reading the spec, comparing it with your implementation
> and writing a detailed email because I thought it was useful for me to
> understand it but might also be good for
Hi all,
please see my question on Stack Overflow:
http://stackoverflow.com/questions/22321031/how-to-set-full-table-width-on-landscape-document-with-itextsharp-xmlworkerhelpe
I have a problem during PDF rendering on landscape document. Resulting width
seems to be the maximum of a
Andrea schreef op 10/03/2014 18:33:
> I actually disagree.
It's really simple: either you want the owner password to be the same as
the user password, or you want the owner password to be different. In
the former case, pass the same bytes for the owner and user password; in
the latter case, pass
Hi,
I actually disagree.
When I call setEncryption with user pwd, owner pwd and permissions I'm
basically applying to my document a Standard Security Handler which is
responsible for providing additional entries to the encryption dictionary.
Among these entries there's the O key which is a compute
