From: Hans Hagen <pragma@wxs.nl>
To: ntg-context@ntg.nl
Subject: Re: Strange behaviour with spacing in itemization using "columns" vs "horizontal".
Date: Wed, 29 Mar 2017 19:12:46 +0200 [thread overview]
Message-ID: <4914e267-fc47-dd77-4c8a-17b4e90fc2ce@wxs.nl> (raw)
In-Reply-To: <CAAiy42dhi0rOpkfimn4OAq3wnSifmkRaLcN0yD2BpMfZo-d7-Q@mail.gmail.com>
On 3/29/2017 1:34 AM, cryo shock wrote:
> Hi folks,
>
> I noticed a difference in how spacing is set after an itemization.
> I have the following example:
>
> -----------------------------
> \starttext
>
> \startitemize[packed, joinedup, columns, two]
> \startitem
> top left item
> \stopitem
> \startitem
> bottom left item
> \stopitem
> \startitem
> top right item
> \stopitem
> \startitem
> bottom right item
> \stopitem
> \stopitemize
> Notice the size of the blank space?
>
> \startitemize[packed, joinedup, horizontal, two]
> \startitem
> top left item
> \stopitem
> \startitem
> top right item
> \stopitem
> \startitem
> bottom left item
> \stopitem
> \startitem
> bottom right item
> \stopitem
> \stopitemize
> Notice the size of the blank space?
>
> \stoptext
> ---------------------------------
>
> Both itemizations are the same except item order and using "columns" in
> the first one and "horizontal" in the second. Yet the spacing after the
> first itemization seems not right. Or do I oversee something?
they use different mechanisms
- columns switches to columns mode so there we have two columns with a
distance and items can span multiple lines
- horizontal divides the width in (in this case) two equal sized boxes
so there is no distance involved and no breaking across lines (a mixed
variant is probably not too hard to implement)
-----------------------------------------------------------------
Hans Hagen | PRAGMA ADE
Ridderstraat 27 | 8061 GH Hasselt | The Netherlands
tel: 038 477 53 69 | www.pragma-ade.nl | www.pragma-pod.nl
-----------------------------------------------------------------
___________________________________________________________________________________
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://context.aanhet.net
archive : https://bitbucket.org/phg/context-mirror/commits/
wiki : http://contextgarden.net
___________________________________________________________________________________
next prev parent reply other threads:[~2017-03-29 17:12 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-28 23:34 cryo shock
2017-03-29 17:12 ` Hans Hagen [this message]
2017-03-29 17:31 ` Hans Hagen
2017-03-29 19:37 ` cryo shock
2017-04-05 22:19 ` cryo shock
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=4914e267-fc47-dd77-4c8a-17b4e90fc2ce@wxs.nl \
--to=pragma@wxs.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).