ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: Sanjoy Mahajan <sanjoy@MIT.EDU>
To: ntg-context@ntg.nl
Subject: example of better linebreak with 2014.05.17 compared to 2014.07.07
Date: Wed, 09 Jul 2014 06:39:30 -0400	[thread overview]
Message-ID: <87simaddel.fsf@approx.mit.edu> (raw)

[-- Attachment #1: Type: text/plain, Size: 2295 bytes --]

Out of curiosity and as a ConTeXt stress test, I installed 2014.07.07
MkIV and recompiled my book with it, and looked at the pixel-by-pixel
comparison between it and the version compiled with 2014.05.17.

There were many changes.  I am going through them one at a time in case
any could be bugs in luatex or context.  (I noticed several good changes
where pages fit more precisely into their height.)

Here is a change that might be a bug.  It uses the following minimal
example:

\setupbodyfont[palatino]
\showframe
\setuplayout[width=5.4286in]

\starttext

Let's see whether this estimate is reasonable.  According to the
plane's technical documentation, the 747-400's four engines together
can provide roughly 1~meganewton of thrust.

\stoptext

With 2014.05.17, the linebreaks are as follows, with no overfull boxes:

  Let's see whether this estimate is reasonable. According to the plane's
  technical documentation, the 747-400's four engines together can provide
  roughly 1 meganewton of thrust.

With 2014.07.07, the linebreaks are as follows, but with an overfull box:

  Let's see whether this estimate is reasonable. According to the plane's tech-
  nical documentation, the 747-400's four engines together can provide roughly
  1 meganewton of thrust.  

The "roughly" on the second line protrudes a good way into the margin.
From the log file:

  Overfull \hbox (8.80678pt too wide) in paragraph at lines 7--10
  \3>palatino-12pt-rm-tf-0--0 ni-cal doc-u-men-ta-tion, the 747-400’s four en-gines to-gether can pro-vide roughly

Both runs use luatex 0.79.1 (svn rev 5033), which I compiled by hand and
then did 'context --make' to regenerate the formats.

Is this change in linebreaking intended, or could it be an unintended
consequence of another change (and therefore maybe problematic)?

Perhaps related, the PDF files behave differently with copying and
pasting.  Copying the paragraph from the 2014.05.17 file, I get spaces
between the words.  Copying from the 2014.07.07 file, I get no spaces
between the words (using mupdf).  (The difference may be due to the
smaller interword spaces, whose size may have fallen below a threshold
that mupdf uses.)

I've attached the uncompressed PDFs (each about 14K).

-Sanjoy


[-- Attachment #2: version with 2014.05.17 --]
[-- Type: application/pdf, Size: 14384 bytes --]

[-- Attachment #3: version with 2014.07.07 --]
[-- Type: application/pdf, Size: 14531 bytes --]

[-- Attachment #4: 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
___________________________________________________________________________________

             reply	other threads:[~2014-07-09 10:39 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-07-09 10:39 Sanjoy Mahajan [this message]
2014-07-09 13:45 ` Hans Hagen
2014-07-10  3:06   ` Sanjoy Mahajan
2014-07-10 11:03     ` 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=87simaddel.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).