ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: Marcin Borkowski <mbork@atos.wmid.amu.edu.pl>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: MkII vs. MkIV
Date: Tue, 4 Nov 2008 21:59:22 +0100	[thread overview]
Message-ID: <20081104205922.GC2264@atos.labs.wmid.amu.edu.pl> (raw)
In-Reply-To: <420A16D6-319B-49F6-8B52-F7E7FDF5618B@gmail.com>

Dnia Tue, Nov 04, 2008 at 09:41:43PM +0100, Wolfgang Schuster napisa&#322;(a):
> 
> 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. One difference between the two engines are
> the used fonts, pdfTeX use type 1 fonts and luaTeX MkIV opentype fonts.

Thank you for your prompt answers.  I am a bit surprised, though, that
the otf and Type1 Latin Modern fonts are not compatible.  Strange thing.
Seems it will be a good idea to stick to MkIV...

> 
> Wolfgang
> 
> ___________________________________________________________________________________
> 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
> ___________________________________________________________________________________

-- 
Marcin Borkowski (http://mbork.pl)

Stłumiony głos w końcu wypowie słowo prawdy - otworzą się usta!
Prawda - choćby zdeptana - zawsze pozostanie prawdą!
Żadna przemoc, chamstwo, kłamstwo nie uczynią z niej ofiary!
                        (Izaiash)
___________________________________________________________________________________
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
___________________________________________________________________________________


  reply	other threads:[~2008-11-04 20:59 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 [this message]
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
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=20081104205922.GC2264@atos.labs.wmid.amu.edu.pl \
    --to=mbork@atos.wmid.amu.edu.pl \
    --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).