ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: Gerben Wierda <gerben.wierda@rna.nl>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: mkiv versus mkii: whitespace issues
Date: Mon, 16 Mar 2015 15:03:12 +0100	[thread overview]
Message-ID: <EAEC6998-CEE8-42DC-8235-48071CFE21B0@rna.nl> (raw)
In-Reply-To: <8D576EF7-9F18-4F11-9A60-AEDA071377B2@gmail.com>


[-- Attachment #1.1: Type: text/plain, Size: 3698 bytes --]


On 15 Mar 2015, at 23:24, Wolfgang Schuster <schuster.wolfgang@gmail.com> wrote:

> 
>> Am 14.03.2015 um 15:54 schrieb Gerben Wierda <gerben.wierda@rna.nl>:
>> 
>> I am running into two issues with my mkii-to-mkiv conversion project
>> 
>> - The \chapter command in mkiv uses more whitespace between the header and the first paragraph. How can I influence this?
> 
> The different space before the \chapter is caused by the “fixed” keyword for \blank
> which produce different result with MkII and MkIV and the MkIV behaviour need
> to be corrected.
> 
> The space after \chapter comes from your \writetolist entry and you can correct
> this with the \GotoPar command at the end of the entry as shown below.
> 
> %%%% begin example
> \showgrid
> 
> \setuphead[chapter][before={\blank[force,2*line]}]
> 
> \starttext
> 
> \chapter{Knuth}
> 
> \writetolist[chapter]{}{}\GotoPar
> 
> \input knuth
> 
> \stoptext
> %%%% end example

Thanks. I tried this

% Every chapter starts with a quote on the LHS page:
\setuphead
  [chapter]
  [page=,
   before={\setups[chapter:before]},
   after={\setups[chapter:after]}]

\startsetups chapter:before
    \page[left]
    \noheaderandfooterlines
    \startalignment[left,nothyphenated]
	\startnarrower[4*left]
            \em \getbuffer[chapter:quote]
	\stopnarrower
    \stopalignment
    \resetsetups[quote:text]
    \page[right]
    \noheaderandfooterlines
    \blank[force,2*big]
\stopsetups

\startsetups chapter:after
    \blank[3*big]
\stopsetups

\definelist[chaptertext]
\setuplist[chaptertext][margin=1.3em,pagecommand=\gobbleoneargument]
\define[1]\ChapterAbstract{\writetolist[chaptertext]{}{\start\itx#1\stop}\GotoPar}


(Adding the \GotoPar at the end) but it did not had any effect. At one place (no chapter but an unnumbered title, it doesn’t work as well. Here I now have:

\title[h:grief1]{Intermezzo:\\
A short story about grief}
\writetolist[chapter]{}{Intermezzo: A Short Story about Grief}\GotoPar
\ChapterAbstract{A small fragment of a movie script that beautifully
illustrates the gap between the rational and the real.}

I changed it to 
\title[h:grief1]{Intermezzo:\\
A short story about grief}
\writetolist[chapter]{}{Intermezzo: A Short Story about Grief}\GotoPar
\ChapterAbstract{A small fragment of a movie script that beautifully
illustrates the gap between the rational and the real.}\GotoPar

And that works. So I changed it in another chapter to

\chapter[h:loosely]{Prologue:\\Loosely Coupled Spaghetti}
\ChapterAbstract{Starting with an example of how things can go wrong in a
current Business-IT landscape, we notice that these kinds of problems have
existed almost for as long as IT has existed, and that no proposed `silver
bullet' has ever solved them. The goal of the book is introduced.}\GotoPar

\placeinitial S{\kap{\bf uppose we}} have a system for the approval of loans. The
business logic has been put into a Business Rule Engine (BRE)
system\footnote{If you are not technical and terms like `application server',

But there it doesn’t. Apparently, I am still missing something. 

G


> 
> 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  : http://foundry.supelec.fr/projects/contextrev/
> wiki     : http://contextgarden.net
> ___________________________________________________________________________________


[-- Attachment #1.2: Type: text/html, Size: 8200 bytes --]

[-- Attachment #2: Type: text/plain, Size: 485 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
___________________________________________________________________________________

  reply	other threads:[~2015-03-16 14:03 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-03-14 14:54 Gerben Wierda
2015-03-14 16:14 ` Wolfgang Schuster
2015-03-15 14:17   ` Gerben Wierda
2015-03-15 14:18   ` Gerben Wierda
2015-03-15 14:18   ` Gerben Wierda
2015-03-15 14:57   ` Gerben Wierda
2015-03-15 22:20     ` Wolfgang Schuster
2015-03-15 22:24 ` Wolfgang Schuster
2015-03-16 14:03   ` Gerben Wierda [this message]
2015-03-20 13:43     ` Gerben Wierda
2015-03-20 17:33       ` Wolfgang Schuster
2015-03-21 18:49         ` Gerben Wierda
2015-03-22 22:03           ` Wolfgang Schuster

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=EAEC6998-CEE8-42DC-8235-48071CFE21B0@rna.nl \
    --to=gerben.wierda@rna.nl \
    --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).