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 13:56:06 +0200 [thread overview]
Message-ID: <E0609894-004A-4B33-A3ED-35177F7B3B88@st.estfiles.de> (raw)
In-Reply-To: <4C5BEF7D.3030800@wxs.nl>
[-- Attachment #1: Type: text/plain, Size: 1614 bytes --]
Am 06.08.2010 um 13:18 schrieb Hans Hagen:
> On 6-8-2010 10:44, Steffen Wolfrum wrote:
>
>> before coming to Brejlov I am just about to clean all my open threads regarding transition MkII->MkIV.
>> One thing is still unanswered - related to grid mode:
>>
>> In MkII the example below rendered the same with or without grid mode.
>> Now in MkIV the lineskiplimit is overruled by grid mode.
>
> forget about comparing to mkii .. a completely different mechanism and behaviour will not be mkii compatible (different kind of control)
>
>> But as I still have to use grid, and yet have to make sure that character clashes don't disturb the consistent interlinespace, I have a problem.
>
> in grid mode interlinespace is ignores
>
>> Looking through spac-ver.mkiv gave me the impression that lineskip related code is quite ... precarious.
>> But maybe an unofficial hack is doable?
>
> no hack needed
>
> \enabletrackers[nodes.vsnapping]
>
> \starttext % see spac-ver.mkiv: \definegridsnapping
>
> \switchtobodyfont[42pt] \setupinterlinespace[line=30pt]
>
> Big text\par written in\par three row
>
> \setuplayout[grid=strict] \setupinterlinespace[line=30pt]
>
> Big text\par written in\par three row
>
> \stoptext
>
> with 'yes' the line gets snapped to fit an extra line when too high (ht/dp ratio) and your first line is larger than the second and third
> (try {yes,line} so see a variant).
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?
Steffen
[-- Attachment #2: grid_on.pdf --]
[-- Type: application/pdf, Size: 40979 bytes --]
[-- Attachment #3: Type: text/plain, Size: 486 bytes --]
___________________________________________________________________________________
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 11:56 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 [this message]
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
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=E0609894-004A-4B33-A3ED-35177F7B3B88@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).