From: "Stefan Müller" <warrence.stm@gmx.de>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: bibmodule acquired problem
Date: Tue, 27 Sep 2011 15:07:06 +0200 [thread overview]
Message-ID: <4E81CA7A.4070209@gmx.de> (raw)
In-Reply-To: <4E81C816.7080701@elvenkind.com>
On 27.09.2011 14:56, Taco Hoekwater wrote:
> On 09/27/2011 02:51 PM, Meer, H. van der wrote:
>> My best guess now is the description of the
>> FUNCTION {format.crossref}
>> { "" "\crossref" crossref do.out
>> }
>> entry on the .bst file. Probably this generates the bad code leading
>> to a missing \endcsname.
>
> I do not have time to pay close attention right now, but the .bst has
> not changed in years, as far as I know.
>
> Best wishes,
> Taco
Maybe the problem is already present for so long. It occurs only if
"title" of an "inproceedings" that has "crossref" set is accessed. The
bibl-*.tex files don't do that.
Stefan
___________________________________________________________________________________
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://tex.aanhet.net
archive : http://foundry.supelec.fr/projects/contextrev/
wiki : http://contextgarden.net
___________________________________________________________________________________
next prev parent reply other threads:[~2011-09-27 13:07 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-09-25 17:58 Meer, H. van der
2011-09-27 8:03 ` Hans van der Meer
2011-09-27 8:07 ` Meer, H. van der
2011-09-27 8:41 ` Meer, H. van der
2011-09-27 10:09 ` Stefan Müller
2011-09-27 10:35 ` Meer, H. van der
2011-09-27 10:50 ` Stefan Müller
2011-09-27 11:33 ` Meer, H. van der
2011-09-27 12:12 ` Stefan Müller
2011-09-27 12:51 ` Meer, H. van der
2011-09-27 12:56 ` Taco Hoekwater
2011-09-27 13:07 ` Stefan Müller [this message]
2011-09-27 14:23 ` Meer, H. van der
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=4E81CA7A.4070209@gmx.de \
--to=warrence.stm@gmx.de \
--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).