ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: Aditya Mahajan <adityam@umich.edu>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: MkII vs. MkIV
Date: Tue, 4 Nov 2008 22:00:03 -0500 (EST)	[thread overview]
Message-ID: <alpine.DEB.1.00.0811042152160.8346@nqv-yncgbc> (raw)
In-Reply-To: <420A16D6-319B-49F6-8B52-F7E7FDF5618B@gmail.com>

On Tue, 4 Nov 2008, Wolfgang Schuster wrote:

>
> Am 04.11.2008 um 21:20 schrieb Aditya Mahajan:
>
>> On Tue, 4 Nov 2008, Marcin Borkowski wrote:
>>
>>> Hi,
>>>
>>> Is it normal that output from MkII and MkIV are different in terms of
>>> page breaks?
>>
>> Yes. In MKII the interline space is hard coded. MKIV gets the
>> interline
>> space from the font. So, you will get different page breaks. I
>> experienced
>> around 2-5 pages difference in a 100 page document.
>
> The interlinespace in MkII and MkIV is the same and both use a distance
> of 2.8ex between the lines.

Yes, but ex means different dimensions in pdftex and luatex. For example

\starttext

1ex = \the\dimexpr1ex\relax \crlf
2.8ex = \the\dimexpr2.8ex\relax

\stoptext

gives in MKII

1ex = 5.16667pt
2.8ex = 14.46669pt

and in MKIV gives

1ex = 5.172pt
2.8ex = 14.4816pt

The reason is that what ex means is hardcoded in MKII but MKIV gets this 
info from the font. For example, if I use palatino at 12pt, the result in 
MKII does not change, but MKIV gives

1ex = 5.388pt
2.8ex = 15.08641pt

So, depending on the font, MKII and MKIV can have considerably different 
lines per page.

Aditya
___________________________________________________________________________________
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  : https://foundry.supelec.fr/projects/contextrev/
wiki     : http://contextgarden.net
___________________________________________________________________________________


  parent reply	other threads:[~2008-11-05  3:00 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-11-04 20:06 Marcin Borkowski
2008-11-04 20:20 ` Aditya Mahajan
2008-11-04 20:41   ` Wolfgang Schuster
2008-11-04 20:59     ` Marcin Borkowski
2008-11-04 21:06       ` Arthur Reutenauer
2008-11-04 21:51         ` Marcin Borkowski
2008-11-04 22:02           ` Wolfgang Schuster
2008-11-04 22:18             ` Marcin Borkowski
2008-11-05  3:00     ` Aditya Mahajan [this message]
2008-11-05  9:48       ` Wolfgang Schuster
2008-11-05 14:29       ` 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=alpine.DEB.1.00.0811042152160.8346@nqv-yncgbc \
    --to=adityam@umich.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).