ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: "Mikael P. Sundqvist" <mickep@gmail.com>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: Vertical alignment in nested itemizations
Date: Thu, 10 May 2012 09:30:55 +0200	[thread overview]
Message-ID: <CAHy-LL9MeUYABzVuew45ng2ppPq5rurehuCcxMX_YcPj00OYOQ@mail.gmail.com> (raw)
In-Reply-To: <CAHy-LL_XGyraAR7TGLBMU75sPs4FT9t1fvfQjCDMjyY6Z1XJoA@mail.gmail.com>

On Thu, May 10, 2012 at 9:10 AM, Mikael P. Sundqvist <mickep@gmail.com> wrote:
> Dear list,
>
> My question is: Can I somehow force an "inner" itemization to begin on
> the same line as the outer one?
>
> Background:
>
> I am writing solutions to an exam and use nested itemizations, as in
> the test file
>
> \starttext
> \startitemize[n][style=sans]
> \item Bla bla
> \item
> \startitemize[a,packed][left={},right={)},stopper=,style=sans]
> \item Det sökta
> \stopitemize
> \stopitemize
> \stoptext
>
> Now the problem is that the a) does not stay on the same line as the
> 2., but is moved down half a line (this differs depending on the
> amount of text in the file).
>
> In the example code below this problem does not happen, but it happens
> in my file (which contains solutions to an exam not yet given, so I
> cannot show it to you).
>
> However, please see the attached png file to see what it looks like in
> my original file.
>
> Best regards, Mikael

Dear list,

here is a complete example that shows the problem:

\setuppapersize[A4][A4]

\setuplayout[
topspace=0.7cm,
backspace=0.7cm,
leftmargin=0cm,
rightmargindistance=0cm,
rightmargin=0cm,
footer=0cm,
header=0cm,
width=fit,
height=fit,
]

\mainlanguage[sv]
\enableregime[utf]

\starttext
\startitemize[n][style=sans]
\item \input tufte
\item
\startitemize[a,packed][left={},right={)},stopper=,style=sans]
\item Det sökta
\item Bingospjäll
\stopitemize
\item \input tufte
\item \input tufte
\item \input tufte
\item \input tufte
\item \input tufte
\item \input tufte
Brynja
\stopitemize

\stoptext

In this example the a) is pushed a bit up instead of down, but I guess
the reason is the same.

Best regards, Mikael
___________________________________________________________________________________
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:[~2012-05-10  7:30 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-05-10  7:10 Mikael P. Sundqvist
2012-05-10  7:30 ` Mikael P. Sundqvist [this message]
2012-05-10  8:08   ` Hans Hagen
2012-05-10  8:26     ` luigi scarso
2012-05-10  8:32     ` Procházka Lukáš Ing. - Pontex s. r. o.
2012-05-10  8:57       ` Marco
2012-05-10 11:14         ` Hans Hagen
2012-05-22 19:27           ` Mikael P. Sundqvist

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=CAHy-LL9MeUYABzVuew45ng2ppPq5rurehuCcxMX_YcPj00OYOQ@mail.gmail.com \
    --to=mickep@gmail.com \
    --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).