Hmmm...
I am surprised that you aren't getting flagged for the need to have
an OutputIntent present.
Leonard
On Mar 13, 2007, at 5:25 PM, Seung Hyun Park wrote:
> Leonard Rosenthol pdfsages.com> writes:
>
>>
>> On Mar 12, 2007, at 9:43 AM, SeungHyun Park wrote:
>>> I have started my project
On Mar 12, 2007, at 9:43 AM, SeungHyun Park wrote:
> I have started my project right now.
>
> I have no idea about color problem. I do not also know whether
> color problem can be fixed by iText.
>
Color can NOT be corrected by iText, that's why I am asking the
question.
Where
How foolish I am !
I added below lines and therefore file ID Entry error disappeared.
else {
fileID = PdfEncryption.createInfoId(PdfEncryption.createDocumentId());
}
-
*Could you appy this to next release?*
Leonard Rosenthol,
I have started
How does your solution deal with PDF's with color concerns? Or
other types of inconsistent data that PDF/A does not allow?
Leonard
On Mar 12, 2007, at 3:51 AM, SeungHyun Park wrote:
> Hello.
>
>
> I have developed some application related PDF using iTextSharp.
>
>
> Currenly, I am making an
SeungHyun Park wrote:
> I added below lines into PDFStamperImp class and tried again.
> else {
>PdfEncryption.createInfoId(PdfEncryption.createDocumentId());
> }
The createInfoId method returns an object of type PdfLiteral.
You have to do something with that object, otherwise it won't work.
I
SeungHyun Park wrote:
> If you could take a few minutes to answer my questions, I would really
> appreciate it.
In the trailer of the PDF file, you can have a fileID.
Such a file ID is created automatically when you generate
a PDF file with iText. When you alter an existing PDF,
it is removed (no
