ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: Floris van Manen <vm@klankschap.nl>
To: Alan Braslau <alan.braslau@cea.fr>
Cc: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: description renders unintended results (LUATEX BUG?)
Date: Wed, 8 Mar 2017 01:40:53 +0100	[thread overview]
Message-ID: <9D2E255C-32A2-4AF1-80FE-896C5BFCCED7@klankschap.nl> (raw)
In-Reply-To: <20170307170437.4551aa14@zoo.hsd1.co.comcast.net>


[-- Attachment #1.1: Type: text/plain, Size: 652 bytes --]


> On 8 Mar 2017, at 01:04, Alan Braslau <alan.braslau@cea.fr> wrote:
> 
>  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.
> 

ok, that makes sense.


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

well i do need the description as the items are not numbered or annotated in a sequential way.

i could use a \sym{tag} but then the available space is constant, and not variable as is when using description.

Or is there a better (simpler) way?

.F

[-- Attachment #1.2: Message signed with OpenPGP using GPGMail --]
[-- Type: application/pgp-signature, Size: 842 bytes --]

[-- Attachment #2: Type: text/plain, Size: 492 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://context.aanhet.net
archive  : https://bitbucket.org/phg/context-mirror/commits/
wiki     : http://contextgarden.net
___________________________________________________________________________________

      reply	other threads:[~2017-03-08  0:40 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
2017-03-08  0:40               ` Floris van Manen [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=9D2E255C-32A2-4AF1-80FE-896C5BFCCED7@klankschap.nl \
    --to=vm@klankschap.nl \
    --cc=alan.braslau@cea.fr \
    --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).