ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: Wolfgang Schuster <wolfgang.schuster.lists@gmail.com>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>,
	Taco Hoekwater <taco@elvenkind.com>
Subject: Re: Itemization formatting
Date: Wed, 29 May 2019 17:31:39 +0200	[thread overview]
Message-ID: <674e29d6-68c0-7ec7-be99-76452ea41f40@gmail.com> (raw)
In-Reply-To: <E6D26AB8-FFF1-4128-8A63-6D32A967B8BE@elvenkind.com>

Taco Hoekwater schrieb am 29.05.2019 um 16:15:
> Hi all,
>
> I must be getting old :(
>
> It used to be that I could get ConTeXt to do what I wanted, but that is increasingly getting harder.
>
> Current problem: I would like to have itemizations that behave like in this dummy
> ascii formatting:
>
>    *   Lorem ipsum dolor sit amet, consectetur adipiscing elit. Donec dapibus turpis et
>    nulla venenatis tincidunt. Curabitur sit amet vehicula nisi, sit amet
>
> and so far it has been impossible for me to set up \setupitemize to do what I want.
>
> In descriptive text, what I want is:
>
> 1. some global indentation to the left and/or right. That is what the margin= key does
> 2. the symbol (or number) typeset in a specific width. That is the width= key
> 3. some distance between the number box and the following text. That is the distance= key
> 4. on line 2 and forward to the end of the item, I want a *different* indentation from the first item line.
>
> In this particular case, I want no extra indentation except for ‘margin’, but in other
> cases I may like either more or less indentation than on line 1 of the first para of the item.
>
> The desired effect is simple achieve with primitive operations, but I would like the input
> to look nice (not to mention that I do not want to loose options for cross-referencing etc).
>
>    \setupitemize[option=intext]
>
> is nearly right for this case (with indentation equal to the left margin), so I assumed I would
> be able to tweak that. But the problem there is that while it does 2-4, it ignores the extra
> indentation required for nested itemizations (it even ignores explicit margin= settings for the
> nested level). After fighting with this for hours, I am nearly ready to give up.
>
> Anybody have any idea how to get itemizations to do what I want?
>
> MWE attached.
>
> Best wishes,
> Taco
> PS It seems that “indentnext=no” does not work for nested itemizations?

You can use the "text" option and add \par at the end of each item but 
your requirements (hanging text, different margin and before/after 
ssettings) are easier to solve with a description or enumeration.

\definesymbol
   [taco]
   [{\inframed[frame=off,width=2em,align=flushleft]{\textbullet}}]

\starttext

\samplefile{zapf}

\startitemize[text][symbol=taco]
   \item \samplefile{weisman}\par
   \startitemize
     \item \samplefile{ward}\par
   \stopitemize
\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://context.aanhet.net
archive  : https://bitbucket.org/phg/context-mirror/commits/
wiki     : http://contextgarden.net
___________________________________________________________________________________

      parent reply	other threads:[~2019-05-29 15:31 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-05-29 14:15 Taco Hoekwater
2019-05-29 14:20 ` Itemization formatting (different question) Taco Hoekwater
2019-05-29 15:14   ` Wolfgang Schuster
2019-05-29 15:20     ` Taco Hoekwater
2019-05-29 15:26       ` Hans Hagen
2019-05-29 14:27 ` Itemization formatting Tomas Hala
2019-05-29 14:40   ` Taco Hoekwater
2019-05-29 14:53     ` Tomas Hala
2019-05-29 15:01       ` Taco Hoekwater
2019-05-29 14:59 ` Hans Hagen
2019-05-29 15:04   ` Taco Hoekwater
2019-05-29 15:24 ` Hans Hagen
2019-05-29 15:31 ` Wolfgang Schuster [this message]

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=674e29d6-68c0-7ec7-be99-76452ea41f40@gmail.com \
    --to=wolfgang.schuster.lists@gmail.com \
    --cc=ntg-context@ntg.nl \
    --cc=taco@elvenkind.com \
    /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).