From: luigi scarso <luigi.scarso@gmail.com>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: underbraces get progressively more misaligned (w/ minimal example)
Date: Fri, 4 Jul 2014 00:47:29 +0200 [thread overview]
Message-ID: <CAG5iGsDdegWfC3pUXz8uX2=fy+ka_QakcyAktdDAcqXaEZL8ng@mail.gmail.com> (raw)
In-Reply-To: <871tu23w7e.fsf@approx.mit.edu>
[-- Attachment #1.1: Type: text/plain, Size: 2968 bytes --]
On Fri, Jul 4, 2014 at 12:37 AM, Sanjoy Mahajan <sanjoy@mit.edu> wrote:
> > context --make does a --generate so you can skip that and the luatools
> > run is not needed either (selfupdate is seldom needed too)
>
> So 'context --make' is all one needs? I'll update the wiki.
>
> > we get a .5pt height difference somewhere (nothing else different in a
> > trace) ... smells like a luatex bug (testing that now)
>
> That is my suspicion as well. But I couldn't reproduce it with plain
> luatex. Though maybe I needed to use equation numbers, however that is
> done in plain tex (the context run doesn't show the problem without the
> \placeformula).
>
> I suspect some internal state is getting slightly corrupted and getting
> progressively worse with the 30,000 repetitions.
>
> I've been finding many unexplained 0.5pt or so differences, which may be
> related to the underbrace problem. The context, so to speak, is that I
> am putting in the last edits to the book, after having gone through and
> checked every page many times. So I want to ensure that none of the
> small changes has a big effect, but I don't want to check every page
> again (or I'll vomit).
>
> Thus, I run my compare-pdfs.sh script on the previous and the latest
> pdf. It renders each page to a B/W png (using mupdf) and then compares
> corresponding pages using 'compare' (one of the ImageMagick tools). Any
> differing pixels are in red, and the shared pixels are in very light
> gray. Then all the pages with enough differences are viewed with 'feh',
> in order of most-to-least differences. And I check that nothing major
> has changed.
>
> What I keep finding is that pages long after where I make a small change
> somehow get changed, with roughly one-pixel shifts to parts of the page.
> I'm attaching an example pixel diff. It shows changes on p.72 of the
> mss. However, the only change to the source code was on p.58 (and was
> designed not to change any page breaks, which it didn't). That same
> page (p.72) often gets similar changes with all kinds of small changes.
>
> [Note to me: In case I need to recreate the source for debugging
> purposes, it's the change from rev 41ff54 to 2467d5]
>
> In case the script is useful to others (earlier versions are in the
> contexttest repository somewhere), I am attaching it. I use it as
> follows with a bash command line. (The awk in the pipeline makes sure
> that only pages with some difference make it to the viewer.)
>
> DPI=72 compare-pdfs.sh old.pdf new.pdf | tee book-print.compare72dpi | awk
> '{if (($3 > 0.02)) print;}' | sort -nr -k3 | awk '{print $1}' | xargs -r feh
>
> Thank you for the script.
Under linux you can also try diffpdf
$> aptitude search diffpdf
i diffpdf
- compare two PDF
files textually or visually
p diffpdf:i386
- compare two PDF
files textually or visually
--
luigi
[-- Attachment #1.2: Type: text/html, Size: 4161 bytes --]
[-- Attachment #2: Type: text/plain, Size: 485 bytes --]
___________________________________________________________________________________
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
___________________________________________________________________________________
next prev parent reply other threads:[~2014-07-03 22:47 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-29 10:13 Sanjoy Mahajan
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 [this message]
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='CAG5iGsDdegWfC3pUXz8uX2=fy+ka_QakcyAktdDAcqXaEZL8ng@mail.gmail.com' \
--to=luigi.scarso@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).