From: Floris van Manen <vm@klankschap.nl>
To: ntg-context@ntg.nl
Subject: description renders unintended results
Date: Fri, 3 Mar 2017 09:59:31 +0100 [thread overview]
Message-ID: <3734E0A9-279D-4659-8EB2-903910ADFD4B@klankschap.nl> (raw)
[-- Attachment #1.1.1: Type: text/plain, Size: 1523 bytes --]
The documentation on page
http://wiki.contextgarden.net/Description
provides sample code to stack multiple levels of description such as:
\setuppapersize[A5]
\definedescription[descr][
headstyle=bold, style=normal, align=left, location=hanging,
width=broad, margin=1cm
]
\starttext
\startdescr{Para}
This is a shorter item label, and some text that talks about it.
The text is wrapped into a paragraph, with successive lines indented.
This is another paragraph under the "Para" item.
\startdescr{Sub Item}
This is a description of an item which is within the "Para" item.
\stopdescr
\startdescr{Sub Item}
Another Sub Item
\stopdescr
\stopdescr
\startdescr{Short}
A short item that's not part of that really long "Para" item.
\stopdescr
\stoptext
which should generate the included rendering.
But reality is somewhat more diverse …
My current context / luatex, as well as the online context engine come up with a different rendering
Even when you correct for the right/left alignment, the itemising does not properly stack up:
It there a work around ?
$ context --version
mtx-context | ConTeXt Process Management 0.63
mtx-context |
mtx-context | main context file: /Applications/ConTeXt/tex/texmf-context/tex/context/base/mkiv/context.mkiv
mtx-context | current version: 2016.09.24 12:40
$ luatex --version
This is LuaTeX, Version 1.0.0 (TeX Live 2017/dev)
Thanks
.Floris van Manen
[-- Attachment #1.1.2.1: Type: text/html, Size: 5667 bytes --]
[-- Attachment #1.1.2.2: d24ff9f3afdcc6cb5d0c8e09c24d5338.png --]
[-- Type: image/png, Size: 18294 bytes --]
[-- Attachment #1.1.2.3: Screen Shot 2017-03-03 at 09.51.57.PNG --]
[-- Type: image/png, Size: 220667 bytes --]
[-- Attachment #1.1.2.4: Screen Shot 2017-03-03 at 09.53.43.PNG --]
[-- Type: image/png, Size: 216750 bytes --]
[-- 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
___________________________________________________________________________________
next reply other threads:[~2017-03-03 8:59 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-03 8:59 Floris van Manen [this message]
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
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=3734E0A9-279D-4659-8EB2-903910ADFD4B@klankschap.nl \
--to=vm@klankschap.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).