ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: Hans Hagen via ntg-context <ntg-context@ntg.nl>
To: Pablo Rodriguez via ntg-context <ntg-context@ntg.nl>
Cc: Hans Hagen <j.hagen@xs4all.nl>
Subject: Re: /CropBox overflows /MediaBox
Date: Tue, 28 Feb 2023 21:18:56 +0100	[thread overview]
Message-ID: <53a436ab-9250-4637-505d-6ff3cff15a0c@xs4all.nl> (raw)
In-Reply-To: <4f3e3013-be6d-89b9-45df-778b937d2aa0@gmx.es>

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/PDF32000_2008.pdf#page=636):
> 
>    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
-----------------------------------------------------------------

___________________________________________________________________________________
If your question is of interest to others as well, please add an entry to the Wiki!

maillist : ntg-context@ntg.nl / https://www.ntg.nl/mailman/listinfo/ntg-context
webpage  : https://www.pragma-ade.nl / http://context.aanhet.net
archive  : https://bitbucket.org/phg/context-mirror/commits/
wiki     : https://contextgarden.net
___________________________________________________________________________________

  reply	other threads:[~2023-02-28 20:18 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-02-28 17:23 Pablo Rodriguez via ntg-context
2023-02-28 20:18 ` Hans Hagen via ntg-context [this message]
2023-03-01 15:44   ` Pablo Rodriguez via ntg-context
     [not found] ` <a64d5f5b-5bfa-920d-eebf-195287f2eda7@xs4all.nl>
2023-03-06 18:02   ` Pablo Rodriguez via ntg-context
2023-03-06 22:06     ` Hans Hagen via ntg-context
2023-03-07 14:38       ` Pablo Rodriguez via ntg-context

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=53a436ab-9250-4637-505d-6ff3cff15a0c@xs4all.nl \
    --to=ntg-context@ntg.nl \
    --cc=j.hagen@xs4all.nl \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).