From: Rik Kabel <context@rik.users.panix.com>
To: ntg-context@ntg.nl
Subject: URLs break bib export
Date: Thu, 26 Jul 2018 23:17:56 -0400 [thread overview]
Message-ID: <b0d86e93-ec77-d73a-e415-9ec3d0b649c2@rik.users.panix.com> (raw)
The new tagged biblography export is very nice, but there is a routine
(marked UGLY in the source) that causes processing to fail with
otherwise-valid input. The failure message is
...eXt/tex/texmf-context/tex/context/base/mkiv/back-exp.lua:3889: invalid capture index
stack traceback:
[C]: in function 'gsub'
...eXt/tex/texmf-context/tex/context/base/mkiv/back-exp.lua:3889: in function <...eXt/tex/texmf-context/tex/context/base/mkiv/back-exp.lua:3747>
(...tail calls...)
and two URLs which cause this problem are:
url = {http://www.jerwood-no.org.uk/pdf/Dunning%20Kruger.pdf},
url = {http://oll.libertyfund.org/?option=com_staticxt&staticfile=show.php\%3Fcollection=46&Itemid=27},
These URLs caused no problem with PDF output or in the previous
exports, although they were not printed and exist only in the bibliography.
Do I need to protect the special characters in the bib file, or is this
a problem with the UGLY code?
--
Rik
___________________________________________________________________________________
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:[~2018-07-27 3:17 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-07-27 3:17 Rik Kabel [this message]
2018-07-27 16:18 ` 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=b0d86e93-ec77-d73a-e415-9ec3d0b649c2@rik.users.panix.com \
--to=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).