From: Gerben Wierda <gerben.wierda@rna.nl>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: itemize: how to get the first level items indented?
Date: Wed, 20 Aug 2014 17:53:44 +0200 [thread overview]
Message-ID: <1A3EEE98-AE32-44DA-9F2C-7AF642BEDC0E@rna.nl> (raw)
In-Reply-To: <E759A724-DF9F-49EC-B6A8-45378287AD20@gmail.com>
[-- Attachment #1.1: Type: text/plain, Size: 1741 bytes --]
On 20 Aug 2014, at 17:34, Wolfgang Schuster <schuster.wolfgang@gmail.com> wrote:
>
> Am 20.08.2014 um 17:32 schrieb Gerben Wierda <gerben.wierda@rna.nl>:
>
>>
>> On 20 Aug 2014, at 17:23, Wolfgang Schuster <schuster.wolfgang@gmail.com> wrote:
>>
>>>
>>> Am 20.08.2014 um 16:07 schrieb Gerben Wierda <gerben.wierda@rna.nl>:
>>>
>>>> Thanks. I used
>>>>
>>>> \setupitemize[each][margin=standard]
>>>>
>>>> and this works. However, I've noticed that the normal pararaph indent is just a little bit more than the itemize margin. The bullets of the list are not aligned perfectly with the indented line. They are indented slightly less. Anything I can do about that?
>>>
>>> Are you sure?
>>
>> Yes:
>>
>> https://dl.dropboxusercontent.com/u/59305058/Screen%20Shot%202014-08-20%20at%2020%20August%2017.30.37.png
>
> Make a *working* minimal example.
Having that part in a smaller bodyfont is what triggers it:
\starttext
\setupbodyfont[12pt]
\setupindenting[small]
\indenting[yes]
\setupitemize[each][margin=standard]
\start
\switchtobodyfont[8pt]
Bar foo foo bar. Bar foo foo bar. Bar foo foo bar. Bar foo foo bar. Bar foo
foo bar.
(PSA) becomes the Project Architecture (PA). As of that moment:
\startitemize[joinedup,packed]
\item Foo
\item Foo
\item Foo
\item Foo
\stopitemize
Bar foo foo bar. Bar foo foo bar. Bar foo foo bar. Bar foo foo bar. Bar foo
foo bar. Bar foo foo bar. Bar foo foo bar. Bar foo foo bar. Bar foo foo bar.
Bar foo foo bar. Bar foo foo bar. Bar foo foo bar. Bar foo foo bar. Bar foo
foo bar. Bar foo foo bar. Bar foo foo bar. Bar foo foo bar. Bar foo foo bar.
Bar foo foo bar. Bar foo foo bar. Bar foo foo bar. Bar foo foo bar.
\stop
\stoptext
[-- Attachment #1.2: Type: text/html, Size: 6090 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
___________________________________________________________________________________
next prev parent reply other threads:[~2014-08-20 15:53 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-08-19 14:27 Gerben Wierda
2014-08-19 14:33 ` Wolfgang Schuster
2014-08-19 22:21 ` Gerben Wierda
2014-08-19 23:22 ` Aditya Mahajan
2014-08-20 14:07 ` Gerben Wierda
2014-08-20 15:23 ` Wolfgang Schuster
2014-08-20 15:32 ` Gerben Wierda
2014-08-20 15:34 ` Wolfgang Schuster
2014-08-20 15:53 ` Gerben Wierda [this message]
2014-08-20 16:01 ` Wolfgang Schuster
2014-08-20 17:01 ` Gerben Wierda
2014-08-20 17:56 ` 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=1A3EEE98-AE32-44DA-9F2C-7AF642BEDC0E@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).