ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: Sanjoy Mahajan <sanjoy@MIT.EDU>
To: ntg-context@ntg.nl
Subject: underbraces get progressively more misaligned (w/ minimal example)
Date: Sun, 29 Jun 2014 06:13:57 -0400	[thread overview]
Message-ID: <87d2dsnhui.fsf@approx.mit.edu> (raw)

Dear list,

As I copyedited my book, I noticed examples where the underbraces in
math formulas were not aligned vertically, especially toward the end of
the book.  Eventually I realized it was not due to my growing
copyediting skill, and I have made the following minimal example showing
the problem (I am using 2014.05.17 MkIV):

\setupformulas[indentnext=auto, spacebefore=none, spaceafter=none]

\starttext

\dorecurse{3000}{
\placeformula\startformula
\underbrace{\hbox{yyyy}}_{\rho} =
\underbrace{\hbox{yyyy yyyy yyyy}}_{\rho}
\stopformula
}

\stoptext

It'll produce a 162-page file.  On the formulas on page 1, the two
underbraces in each equation are aligned.  But there seems to be some
kind of slow leak, because the underbraces become ever more misaligned.
By page 162, they are visibly misaligned by maybe 3pt.  If I increase
the recursion count to 30000, on page 2129 the misalignment is about 30pt.

Taking out the \placeformula makes the misalignment go away.

I tried to reproduce the problem with plain LuaTeX, using the tex file
below, but the underbraces came out aligned.

\newcount\foo
\foo=3000
\loop
$$
\underbrace{\hbox{yyyy}}_{\rho} =
\underbrace{\hbox{yyyy yyyy yyyy}}_{\rho}
$$
\advance \foo -1
\ifnum \foo>0
\repeat

\end

Any thoughts on this very strange issue?

-Sanjoy
___________________________________________________________________________________
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://tex.aanhet.net
archive  : http://foundry.supelec.fr/projects/contextrev/
wiki     : http://contextgarden.net
___________________________________________________________________________________


             reply	other threads:[~2014-06-29 10:13 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-06-29 10:13 Sanjoy Mahajan [this message]
2014-06-29 10:24 ` Sanjoy Mahajan
2014-07-03 10:49   ` Sanjoy Mahajan
2014-07-03 19:21     ` Wolfgang Schuster
2014-07-03 21:03       ` Sanjoy Mahajan
2014-07-03 22:09         ` Hans Hagen
2014-07-03 22:37           ` Sanjoy Mahajan
2014-07-03 22:47             ` luigi scarso
2014-07-07 13:59               ` Sanjoy Mahajan
2014-07-03 22:51             ` Hans Hagen
2014-07-04  4:58               ` Wolfgang Schuster
2014-07-04  8:22                 ` Hans Hagen
2014-07-04  9:34                 ` Sanjoy Mahajan
2014-07-05  0:30                   ` Hans Hagen
2014-07-07  2:16                     ` Sanjoy Mahajan
2014-07-07  3:48                       ` Sanjoy Mahajan
2014-07-07 13:56             ` Sanjoy Mahajan
2014-07-07 13:53       ` Sanjoy Mahajan
2014-07-04  7:12 Akira Kakuto
2014-07-04  8:17 ` 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=87d2dsnhui.fsf@approx.mit.edu \
    --to=sanjoy@mit.edu \
    --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).