Tomáš Bucki schreef op 15/11/2013 15:24:
> Bookmarks probably will be in our PDF files, but annotations not.
>
> The idea to store the whole file in one place and streams in another is a
> valid solution also. If there are some methods how to separate and again
> recreate them to valid PDF file i
Aritz,
Aritz_85 wrote
> Here it is my code. I can't understand this behaviour:
> [...]
> -Mensaje original-
> [...]
> Aritz_85 wrote
>> Tomorrow I'll try to send you my code.
>
> Please also supply a sample PDF illustrating the issue.
Please definitively also supply a sample PDF illustra
Bookmarks probably will be in our PDF files, but annotations not.
The idea to store the whole file in one place and streams in another is a valid
solution also. If there are some methods how to separate and again recreate
them to valid PDF file in iText. I suppose that streams will be stored onl
Tomáš Bucki schreef op 15/11/2013 14:54:
> Hope now it is little bit clear
Yes, it's important to know that your PDFs "are not such special, only
font's and graphics is used."
This means that we don't have to worry about annotations, bookmarks,
structure trees,... This is important information.
Hallo,
Thanks for the quick answer. Please see my comments:
>Resources are usually reused by different pages. Sometimes content is stored
>as a resource (XObjects).
That's why we want to decompose pages. We will have a large amount of PDF files
which we will need to store somehow. What we want
Tomáš Bucki schreef op 15/11/2013 12:58:
>
> Hi all,
>
> We are in the stage of evaluating/buying iText for use in our company.
> Most of the tasks we want to do with PDF files is iText capable to do.
> However there is one special thing we want to do with PDF and we have
> not found a simple an
Hi all,
We are in the stage of evaluating/buying iText for use in our company. Most of
the tasks we want to do with PDF files is iText capable to do. However there is
one special thing we want to do with PDF and we have not found a simple and
comfortable way how to achieve it with iText :
We