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: Sun, 15 Mar 2015 15:18:12 +0100	[thread overview]
Message-ID: <AB7FC570-33EF-40CA-8C2D-F61258A95ED7@rna.nl> (raw)
In-Reply-To: <E87707F5-AECF-4EEF-9E9F-91BC6CF2EDA7@gmail.com>


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

mkii result



On 14 Mar 2015, at 17:14, 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?
>> - \startitemize[packed,joinedup] inserts whitespace between the list and the paragraph before it where mkii doesn’t
>> 
>> How can I fix this?
> 
> Do you have a example because I can’t reproduce it.
> 
> \showgrid
> 
> \starttext
> 
> \chapter{\contextmark}
> 
> \input knuth
> 
> \startitemize[packed,joinedup]
> \item One
> \item Two
> \item Three
> \stopitemize
> 
> \stoptext 
> 
> 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.1: Type: text/html, Size: 2268 bytes --]

[-- Attachment #1.2.2: Screen Shot 2015-03-15 at 15 March 15.06.18.png --]
[-- Type: image/png, Size: 66352 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
___________________________________________________________________________________

  parent reply	other threads:[~2015-03-15 14:18 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 [this message]
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
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=AB7FC570-33EF-40CA-8C2D-F61258A95ED7@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).