Leonard Rosenthol

> The understanding at the National Archives and Records Administration is that there are three ways to scan a document into the PDF format. Actually, there are MANY ways to...

>If Differences arrays were ok to use, it would be possible to select different sets of glyphs from one larger font program in different font dictionaries. It was never envisioned...

PDF supports ICC Profiles in Gray, RGB, CMYK and Lab spaces. Period. (the main reason for this, as noted above, is that the current transparency algorithms aren't designed to work...

I am OK with the first proposed changed and the last, but not the middle one, as (was discussed in the Securing PDF TWG) operators are also PDF objects.

Yes, that is correct - operators are PDF objects. It states this clearly in 7.8.2 (paragraph 3) >A content stream, after decoding with any specified filters, shall be interpreted according...

>I think reading that sentence as a definition of objects is very backwards. It is **NOT** a definition of objects, but is a **USE** of objects - just as the...

Definition of what @pesco ? Operators and Operands in a content stream are PDF objects. PDF objects are those things defined in section 7.3, Objects. 7.8.2 goes even further in...

Oh - I think you are saying that you believe that they should all be defined in a single section of the specification. Yes? I don't see any reason that...

Depends on what you mean by "would be allowed". Is that fragment `BX 1 2 \o EX` allowed to be present in a content stream? Yes, it is. Why? Because...

>A more direct definition might be helpful It might be - but you are almost 30 years too late for doing so. > even if it were more restrictive Why...