On 2/28/2023 6:23 PM, Pablo Rodriguez via ntg-context wrote:
Dear list,
I have the following source:
\nopdfcompression \setupinteractionscreen [width=max] \setuplayout [standard] [backspace=.7\textwidth, cutspace=\cutspace, width=middle] \starttext \startmakeup[page] \null \stopmakeup \startmakeup[standard] \null \stopmakeup \stoptext
Boxes are defined in the following objects:
3 0 obj [ 0 0 595.275590072 841.88975789 ] endobj
5 0 obj [ 0 0 595.27559 841.889758 ] endobj
8 0 obj [ 0 0 968.199847 841.889758 ] endobj
Page 1 has /MediaBox redirected to object 3 and /CropBox redirected to object 5.
Page 2 has /MediaBox redirected to object 3 and /CropBox redirected to object 8.
I’m not sure whether the oversized /CropBox in the sample above is a bug triggered by the use of "\setupinteractionscreen[width=fit]".
From the PDF–1.7 specification (https://opensource.adobe.com/dc-acrobat-sdk-docs/standards/pdfstandards/pdf/...):
The crop, bleed, trim, and art boxes shall not ordinarily extend beyond the boundaries of the media box. If they do, they are effectively reduced to their intersection with the media box.
https://wiki.contextgarden.net/PDF_Boxes displays an image of (what I guess) the ordinary case: /CropBox fits inside /MediaBox.
Could anyone be so kind to confirm the issue or to explain the rationale behind the oversized /CropBox? different code path (dates from mkiv but i can adapt it for lmtx)
anyway, overflow is in the 7th decimal so quite harmless i guess Hans ----------------------------------------------------------------- Hans Hagen | PRAGMA ADE Ridderstraat 27 | 8061 GH Hasselt | The Netherlands tel: 038 477 53 69 | www.pragma-ade.nl | www.pragma-pod.nl -----------------------------------------------------------------