From: Damien Thiriet <damien@thiriet.web4me.fr>
To: ntg-context@ntg.nl
Subject: Bug in lmtx bibliography (numerals in entry?)
Date: Tue, 1 Dec 2020 10:02:08 +0100 [thread overview]
Message-ID: <20201201090208.GA85639@valencay.home> (raw)
Hello,
My bibliography files compiles fine in mkiv, but hangs in lmtx
Here is the error message:
tex error > tex error on line 30 in file ./Nation_rev_empire.mkiv:
Use of \btxshowentryinline doesn't match its definition
<macro> \btxflushlisttext ...tyleandcolor \c!style \c!color
\ignorespaces \publ_fast_setup \plusfour \s!list \currentbtxcategory
\removeunwantedspaces
\endgroup
<argument> \btxflushlisttext
\ifx \currentbtxcombis \empty \else \btxrenderingparameter
\c!separator \btxflushlistcombis \fi
<macro> \btx:list:inject:text ...al \btxinteractivetext \ifx
\currentbtxinternal \empty #1\else \goto {#1} [\s!internal
(\currentbtxinternal )]\fi \else #1
\fi
<macro> \btx_entry_inject ...onal \c_btx_list_texts
\dostarttagged \t!listtext \s!left \currentbtxbefore
\dostoptagged \fi \btx_entry_inject_list_text
\ifconditional \c_btx_list_pages \dostarttagged
\t!listpage \empty \btx_entry_inject_pages \dostoptagged
\fi \ifconditiona...
<macro> \currentlistentrytitle \dostarttagged
\t!listcontent \empty \btx_list_reference_inject
\btx_entry_inject
\dostoptagged
<macro> \22>:139>:paragraph ...\relax \fi \fi \fi
\begingroup \useliststyleandcolor \c!textstyle
\c!textcolor \setstrut \begstrut
\currentlistentrytitle
\endstrut \endgroup \ifconditional
\c_lists_has_page \ifconditional
\c_lists_show_page \nobreak \currentlistfiller
\beging...
[…]
If you say, e.g., '\def\a1{...}', then you must always put '1' after
'\a',
since control sequence names are made up of letters only. The macro here
has not
been followed by the required stuff, so I'm ignoring it.
I am using a custom biblio style, but the command \btxshowentryinline is
not directly called inside.
My ConTeXt version
mtx-context | ConTeXt Process Management 1.04
mtx-context |
mtx-context | main context file:
/usr/local/context/tex/texmf-context/tex/context/base/mkiv/context.mkiv
mtx-context | current version: 2020.11.19 11:28
mtx-context | main context file:
/usr/local/context/tex/texmf-context/tex/context/base/mkiv/context.mkxl
mtx-context | current version: 2020.11.19 11:28
AFAIU, it means my entry shouldn’t have numbers, right? If so, this may
be a bug, since entry biblio files often have a number inside
Best regards,
Damien Thiriet
___________________________________________________________________________________
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:[~2020-12-01 9:02 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-01 9:02 Damien Thiriet [this message]
2020-12-01 10:23 ` Hans Hagen
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=20201201090208.GA85639@valencay.home \
--to=damien@thiriet.web4me.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).