From: Hans Hagen <j.hagen@xs4all.nl>
To: Rik Kabel <context@rik.users.panix.com>,
"ntg-context@ntg.nl >> mailing list for ConTeXt users"
<ntg-context@ntg.nl>
Subject: Re: Endnote list difference, MKIV and LMTX
Date: Fri, 12 Apr 2019 14:51:20 +0200 [thread overview]
Message-ID: <916c9d73-c581-3444-766e-9547477579ae@xs4all.nl> (raw)
In-Reply-To: <fa613813-0fe4-2bc4-b296-f93b05574039@rik.users.panix.com>
On 4/12/2019 3:27 AM, Rik Kabel wrote:
> List,
>
> With the following example, endnotes are set differently with MKIV and
> LMTX – incorrectly under LMTX. (MKIV 20190404, LMTX 20190411)
>
> The problem disappears if /either//or both/ of the first two lines are
> removed, but of course those usually serve an important purpose.
>
> \setupbodyfont [12pt]
> \setupindenting[yes,small]
> \starttext
> \chapter{Testing}
> \dorecurse{5}{\samplefile{ward}\endnote{\samplefile{lorem}}\par}
> \chapter{Notes}
> \placenotes[endnote]
> \stoptext
>
> A workaround is to place \placenotes in a group with indenting turned off.
I found the reason .. later this day an update.
Hans
-----------------------------------------------------------------
Hans Hagen | PRAGMA ADE
Ridderstraat 27 | 8061 GH Hasselt | The Netherlands
tel: 038 477 53 69 | www.pragma-ade.nl | www.pragma-pod.nl
-----------------------------------------------------------------
___________________________________________________________________________________
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
___________________________________________________________________________________
prev parent reply other threads:[~2019-04-12 12:51 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-12 1:27 Rik Kabel
2019-04-12 12:51 ` Hans Hagen [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=916c9d73-c581-3444-766e-9547477579ae@xs4all.nl \
--to=j.hagen@xs4all.nl \
--cc=context@rik.users.panix.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).