ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: Alan Braslau <alan.braslau@cea.fr>
To: Floris van Manen <vm@klankschap.nl>
Cc: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: description renders unintended results (LUATEX BUG?)
Date: Tue, 7 Mar 2017 17:04:37 -0700	[thread overview]
Message-ID: <20170307170437.4551aa14@zoo.hsd1.co.comcast.net> (raw)
In-Reply-To: <BD6B027E-67AF-48BE-94A1-E0D859988B70@klankschap.nl>

You can see from your log that
	context --pdftext
is running the MKII macros and
	context
is running MKIV macros. The two systems are very different, MKII being
"frozen" and MKIV having evolved in some ways significantly. It is not
a question of TeX engines, but rather of entire systems.

But it sounds like you want to be using an itemize or enumeration
rather than a description.

\startitemize [n]
  \startitem one
     \startitemize [a]
         \startitem two \stopitem
         \startitem three \stopitem
     \stopitemize
  \stopitem
  \startitem four
     \startitemize [a,continue]
         \startitem five \stopitem
         \startitem six
             \startitemize
                 \startitem seven \stopitem
                 \startitem eight \stopitem
                 \startitem nine \stopitem
             \stopitemize
         \stopitem
     \stopitemize
  \stopitem
  \startitem ten \stopitem
\stopitemize

Alan
___________________________________________________________________________________
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:[~2017-03-08  0:04 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-03-03  8:59 description renders unintended results Floris van Manen
2017-03-04 10:25 ` Otared Kavian
2017-03-04 10:46   ` Henning Hraban Ramm
2017-03-04 10:58   ` Floris van Manen
2017-03-05 23:34     ` Floris van Manen
2017-03-07 17:04       ` description renders unintended results (LUATEX BUG?) Floris van Manen
2017-03-07 19:13         ` Alan Braslau
     [not found]           ` <BD6B027E-67AF-48BE-94A1-E0D859988B70@klankschap.nl>
2017-03-08  0:04             ` Alan Braslau [this message]
2017-03-08  0:40               ` Floris van Manen

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=20170307170437.4551aa14@zoo.hsd1.co.comcast.net \
    --to=alan.braslau@cea.fr \
    --cc=ntg-context@ntg.nl \
    --cc=vm@klankschap.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).