Leonard Rosenthol
Leonard Rosenthol
So why does Acrobat fail on the file... Our parser is designed to only expect to find indirect references in certain places (i.e. as entries in an array and as...
Conceptually, sure, we could do this... However, I don't believe that there are "raw" file format requirements here. I think we need to complete (well, start) the work at ETSI...
From looking over the spreadsheet, I agree that most of them are of the form "X is optional and/or ignored unless key Y meets some criteria" (where _some criteria_ is...
@lrosenthol will investigate this
In this case, PDF does not support the parameters. So any change would be to make it clear that parameters are not permitted for this value - it is strictly...
I'd like to get a better understanding of the use cases here, since I don't understand why using a FreeText annotation here, would be a good choice over possible other...
These are designed for very different purposes and allowing for disconnected segments in `Path` would break that.
>Could you please clarify the "very different purposes" which distinguish Path entry from InkList entry? `Path` is present to enable support for handling click testing on non-rectangular annotations/regions, while `InkList`...
This is 100% processor dependent, and there are business reasons that we do what we do - which have changed over time(!). As such, I wouldn't support any work in...
> If I recall correctly, at the time of that forum response by lrosenth a well-known implementation indeed did not accept mixed xref PDFs. So it might be interesting to...