ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: Peter Rolf <indiego@gmx.net>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: Difference between MKIV and MKII
Date: Fri, 10 Aug 2007 12:07:02 +0200	[thread overview]
Message-ID: <46BC38C6.2070908@gmx.net> (raw)
In-Reply-To: <20070809181942.fkqwr40cu8k8kssw@web.mail.umich.edu>

Hi Aditya,

Aditya Mahajan schrieb:
> Quoting Hans Hagen <pragma@wxs.nl>:
> 
>> Aditya Mahajan wrote:
>>> Hi,
>>>
>>> I get significantly different white spaces (and hence page breaks)
>>> while using mkiv and mkii. Is this expected, or should I try to create
>>> minimal example exhibiting such "problems"?
>> indeed
> 
> Here is a minimal example. The spaces around formulas are more.
>
in the meantime I have also updated my \texmf subtree (LM should be up
to date). Using your example, I now get a

12pt text font with pdftex and
10pt text font with luatex (but 12pt in math mode).

So maybe you have the same problem?

If I remember it right, luatex normally used the OTF variant of LM in my
prior test. Now it's also T1, but with an additional font (this one is
used for the 10pt text) in comparison to pdftex:

lmrroman12-regular (Embedded Subset)
Type: Type1 (CID)
Encoding: Identity-H

Strange. Maybe only some messy font setup on my system.

Peter

> \starttext
> 
> \dorecurse{10}
> {
> \input tufte
> \startformula
>   E = mc^2
> \stopformula
> \par
> }
> 
> \stoptext
> 
> 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
> ___________________________________________________________________________________
> 

___________________________________________________________________________________
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:[~2007-08-10 10:07 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-08-08 19:29 Aditya Mahajan
2007-08-08 22:59 ` luigi scarso
2007-08-09  8:21 ` Hans Hagen
2007-08-09 22:19   ` Aditya Mahajan
2007-08-10  9:57     ` Hans Hagen
2007-08-10 10:07     ` Peter Rolf [this message]
2007-08-10 10:52       ` Peter Rolf
2007-08-10 11:26         ` Hans Hagen
2007-08-10 11:40           ` Arthur Reutenauer
2007-08-10 12:27             ` Hans Hagen
2007-08-10 11:54           ` Peter Rolf
2007-08-10 16:51             ` Hans Hagen
2007-08-10 18:20               ` Peter Rolf
2007-08-10 17: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=46BC38C6.2070908@gmx.net \
    --to=indiego@gmx.net \
    --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).