ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: Khaled Hosny <khaledhosny@eglug.org>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Cc: Mojca Miklavec <mojca.miklavec.lists@gmail.com>
Subject: Re: 10+ reasons why I still use MKII
Date: Thu, 13 May 2010 17:32:43 +0300	[thread overview]
Message-ID: <20100513143243.GB3884@khaled-laptop> (raw)
In-Reply-To: <4BEC09AC.8000403@wxs.nl>

On Thu, May 13, 2010 at 04:16:12PM +0200, Hans Hagen wrote:
> On 13-5-2010 3:42, Mojca Miklavec wrote:
> 
> >\startyoumayignorethis
> >The only thing that really bothers me are so much different vertical
> >differences which show up in almost every document I ever write. MKIV
> >consistently takes more vertical space, so no matter what document I
> >try to recompile, it always ends up with more pages (and some weird
> >page breaks) when processing it with MKIV.
> 
> \startcantresistmode
> 
> the lineheight relates to the ex height and as in mkiv we don't have
> the tfm limitations (those 16 values of ht dp) we have slightly
> different spacing

Something I find very annoying is variable interline spacing, if I've,
for example, a line with some Arabic words vocalized I get some times
too much white space above it that it almost looks like an empty line.
It makes the page look like crap. Is there a way to force fixed
interline spacing?

-- 
 Khaled Hosny
 Arabic localiser and member of Arabeyes.org team
 Free font developer
___________________________________________________________________________________
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:[~2010-05-13 14:32 UTC|newest]

Thread overview: 29+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-05-12 13:48 Mojca Miklavec
2010-05-12 14:44 ` Taco Hoekwater
2010-05-12 15:15 ` Hans Hagen
2010-05-13 13:42   ` Mojca Miklavec
2010-05-13 13:55     ` luigi scarso
2010-05-13 14:16     ` Hans Hagen
2010-05-13 14:32       ` Khaled Hosny [this message]
2010-05-13 15:00         ` Hans Hagen
2010-05-13 17:08           ` Khaled Hosny
2010-05-13 21:09             ` Hans Hagen
2010-05-14 13:52               ` Henning Hraban Ramm
2010-05-13 18:46           ` Idris Samawi Hamid ادريس  سماوي حامد
2010-05-13 20:06             ` Khaled Hosny
2010-05-13 19:31               ` Idris Samawi Hamid ادريس  سماوي حامد
2010-05-13 21:05                 ` Hans Hagen
2010-05-13 20:25               ` Hans Hagen
2010-05-13 21:26                 ` Khaled Hosny
2010-05-13 21:35                   ` Hans Hagen
2010-05-14 12:37                     ` Khaled Hosny
2010-05-14 12:54                       ` Hans Hagen
2010-05-14 13:10                         ` Khaled Hosny
2010-05-14 14:52                       ` Idris Samawi Hamid ادريس   سماوي حامد
2010-05-13 18:34       ` Mojca Miklavec
2010-05-13 21:49         ` Hans Hagen
2010-05-14  5:23     ` Taco Hoekwater
2010-05-12 15:20 ` Aditya Mahajan
2010-05-12 15:23   ` Taco Hoekwater
2010-05-12 15:41     ` Aditya Mahajan
2010-05-12 15:45       ` Taco Hoekwater

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=20100513143243.GB3884@khaled-laptop \
    --to=khaledhosny@eglug.org \
    --cc=mojca.miklavec.lists@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).