From: Steffen Wolfrum <context@st.estfiles.de>
To: Hans Hagen <pragma@wxs.nl>
Cc: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: hack needed (MkIV)
Date: Fri, 6 Aug 2010 19:01:52 +0200 [thread overview]
Message-ID: <837281D0-4E3D-48F5-BFDD-49DEE34A6470@st.estfiles.de> (raw)
In-Reply-To: <4C5BF9DE.5010400@wxs.nl>
Am 06.08.2010 um 14:02 schrieb Hans Hagen:
> On 6-8-2010 1:56, Steffen Wolfrum wrote:
>
>> sorry, but this is not what is needed (see attached pdf, please)
>> this tight interlinespace is not possible in MkIV when grid mode is on?
>
> well, you want things on a grid ... if you don't want that don't use grid mode or snap a box on the grid and disable gridmode inside the box
>
> alternatively you can define a grid instance where spacing is handled differently,
>
> \setuplayout[grid=none]
>
> you can define variants with different thresholds (for ht and dp), extra lines, etc
Could you give an example on this (thresholds for ht and dp), please?
Indeed, the new options with grid mode are enormous. I just tried "local" and the result looks as desired. I only can't estimate what side-effects it might have in a real-life-project.
What does "local" do here, as there are only global settings?!
\usetypescript[postscript]
\definetypeface[postscript][rm][serif][times][default]
\setupbodyfont[postscript,30pt]\setupinterlinespace[line=10pt]
\setuplayout[grid=local]
\starttext
\input tufte \par
\stoptext
Best, Steffen
___________________________________________________________________________________
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
___________________________________________________________________________________
next prev parent reply other threads:[~2010-08-06 17:01 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <B7C3A1D3-BE06-475B-AF3E-441517DE1874@post.werksatz.com>
2010-08-06 11:18 ` Hans Hagen
2010-08-06 11:56 ` Steffen Wolfrum
2010-08-06 12:02 ` Hans Hagen
2010-08-06 12:22 ` Steffen Wolfrum
2010-08-06 13:48 ` life insurance (was hack needed) MkIV Steffen Wolfrum
2010-08-06 15:28 ` hack needed (MkIV) Hans Hagen
2010-08-06 17:01 ` Steffen Wolfrum [this message]
2010-08-06 17:40 ` Hans Hagen
2010-08-06 18:22 ` Steffen Wolfrum
2010-08-08 16:27 ` 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=837281D0-4E3D-48F5-BFDD-49DEE34A6470@st.estfiles.de \
--to=context@st.estfiles.de \
--cc=ntg-context@ntg.nl \
--cc=pragma@wxs.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).