ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: "Meer, H. van der" <H.vanderMeer@uva.nl>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: bibmodule acquired problem
Date: Tue, 27 Sep 2011 08:07:36 +0000	[thread overview]
Message-ID: <77B9ED10-CC61-4342-A953-18F8D991A197@uva.nl> (raw)
In-Reply-To: <182B9444-49D1-4CC9-84A5-377F4DDE40E1@xs4all.nl>

An addtionial remark here: in the .bib file this is caused by a missing "book title".

On 27 sep. 2011, at 10:03, Hans van der Meer wrote:

> Recently I reported the following problem:
> 
> On 25 sep. 2011, at 19:58, H. van der Meer wrote:
> 
>> I used the following macro for typsetting literature references in footnotes. It worked without problems until now, but then I didn't use the bib module for some time.
>> It looks like a problem has crept in with the <inproceedings> type.
>> 
>> The error message:
>> <to be read again> 
>>                  \pbd: 
>> \bibgetvart #1->\csname pbd:#1\endcsname 
>>                                        \plussix 
> 
> Digging into the code I finally was able to nail the problem: the offending citation being of type "t=inproceedings" was missing the "title" item. Then I observe a call with #1 in bibgetvart empty, somehow leading to a missing \endcsname error message.
> 
> Obviously earlier this wasn't a problem but now is. I guess because the code changed since my previous work on the project.
> 
> Hans van der Meer
> 
> 
> ___________________________________________________________________________________
> 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
> ___________________________________________________________________________________

___________________________________________________________________________________
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
___________________________________________________________________________________


  reply	other threads:[~2011-09-27  8: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 [this message]
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
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=77B9ED10-CC61-4342-A953-18F8D991A197@uva.nl \
    --to=h.vandermeer@uva.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).