ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: Hans Hagen <j.hagen@xs4all.nl>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>,
	"Jairo A. del Rio" <jairoadelrio6@gmail.com>
Subject: Re: Concerning \startTEXpage ... \stopTEXpage... again
Date: Mon, 7 Dec 2020 09:58:29 +0100	[thread overview]
Message-ID: <fad30fbc-787e-5465-9165-8fd68ff67785@xs4all.nl> (raw)
In-Reply-To: <CAKyqqaYy8SnnUdiFuomx10bM2dFgr=egUkURwB_EARs4eb-niw@mail.gmail.com>

On 12/7/2020 6:15 AM, Jairo A. del Rio wrote:
> Hi. Thanks to Hans for the quick fixes. However, some examples are still 
> misbehaving.
> See the following:
> 
> \setupbodyfont[70pt]
> \starttext
> \startTEXpage
> \framed{$a >> n = \left\lfloor\frac{a}{2^n}\right\rfloor$}
> \stopTEXpage
> \stoptext
> 
> It works in MkIV, but it has the right margin cut with LMTX. Also, both 
> MkIV and LMTX give cropped formulas when \framed is absent in the 
> example above. Thank you in advance for any feedback.
be careful with terms like 'bug' or 'misbehaving' ... in this case it's 
what one expects

(1) this mechanism creates / operates in a vbox (using a hbox might have 
been nicer in retrospect but then you would have more issues unless 
configured)

(2) so, we need some default hsize to start with and this is the text 
width by defalut unless you set one with the 'width' argument or when
you pass [align=]

(3) cropping takes place after all has been typeset but happens within
the width, again, this could be made more tolerant but then other cases 
will fail

with mechanisms like there is always a catch: handle this well and 
something else will fail (when it works as expected it's seen as a 
feature and otherwise it's considered a bug)

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 / http://www.ntg.nl/mailman/listinfo/ntg-context
webpage  : http://www.pragma-ade.nl / http://context.aanhet.net
archive  : https://bitbucket.org/phg/context-mirror/commits/
wiki     : http://contextgarden.net
___________________________________________________________________________________

  reply	other threads:[~2020-12-07  8:58 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-12-07  5:15 Jairo A. del Rio
2020-12-07  8:58 ` Hans Hagen [this message]
2020-12-07  9:03   ` Jairo A. del Rio
2020-12-07  9:46     ` Hans Hagen

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=fad30fbc-787e-5465-9165-8fd68ff67785@xs4all.nl \
    --to=j.hagen@xs4all.nl \
    --cc=jairoadelrio6@gmail.com \
    --cc=ntg-context@ntg.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).