I went back and found the MCIDs in the content stream. They correspond
to the top and side headers (WACC, g) of the two tables at the bottom
right. So looks like an Excel problem.
Marc
On 9/12/2025 5:51 PM, Marc Kaufman wrote:
Looking at Image1:
The Artifact parent is S:Worksheet, but the K entry for Worksheet does
not contain the Artifact. From this, I infer that the Artifact does
not appear in the page content stream.
Note that each Artifact (which is RoleMap Sect) is followed by an
entry of type P, which is in a TextBox. The TextBox entries do appear
in the Worksheet list. Without digging through all the content
streams, I would hazard a guess that these are placeholder entries for
Alternate Text, which were not used. At this point I'd put it down to
an error in Excel export.
Marc
On 9/12/2025 1:30 PM, Mark Gibson wrote:
Huge thanks Tilman
I’m still learning this stuff. But I did debug the loading of the
image PDF, paying close attention to the structure tree. The more I
dug in, the more I started to think this was a PDF output issue from
Excel. But the spec is large, complex, and obscure in places. So I
was still uncertain.
The Cross Reference table view in the PDFDebugger fairly plainly
shows StructTreeRoot, ParentTree (in StructTreeRoot) and page
content. And it’s plain there’s discrepancies. Allowable by the
spec? No idea.
Mark
