From: <context@joshuamoerman.nl>
To: "'Alan Braslau'" <braslau.list@comcast.net>
Cc: 'mailing list for ConTeXt users' <ntg-context@ntg.nl>
Subject: Re: Crossref in bibtex
Date: Fri, 20 Jul 2018 16:10:01 +0200 [thread overview]
Message-ID: <00b701d42033$59de2a60$0d9a7f20$@joshuamoerman.nl> (raw)
In-Reply-To: <20180712103722.01060068@poo.hsd1.co.comcast.net>
Dear Alan,
Thank you very much fox fixing the issue so quickly! The patch you have sent
me works on my machine as well :-).
I was playing around with bibliography a bit more, and I noticed that when
you make a crossref-loop (two entries pointing to eachother, or a single
entry pointing to itself), the lua interpreter will crash with
"publ-dat.lua:540: loop in gettable stack". Now, this is a bit of a silly
case of course ;-).
Kind regards,
Joshua
-----Original Message-----
From: Alan Braslau <braslau.list@comcast.net>
Sent: 12 July 2018 18:37
To: context@joshuamoerman.nl
Cc: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: [NTG-context] Crossref in bibtex
On Thu, 12 Jul 2018 12:21:28 +0200
<context@joshuamoerman.nl> wrote:
> Hi all,
>
> I am now playing around with ConTeXt to see if it fits my needs for
> writing my thesis :-).
>
> One thing which did not work for me was the use of crossref in bibtex
> entries. This feature is used when generating bibtex entries via DBLP
> (which is quite standard in computer science). It is used to have one
> single entry for the journal/conference which the lists the editors.
> Consequently you can have several paper entries referring to that,
> without duplicating the editors. This has worked fine for me in LaTeX.
> But in ConTeXt it seems the crossref is not used at all.
> Example:
>
> \usebtxdefinitions[apa]
> \usebtxdataset[biblio.bib]
>
> \starttext
> See \cite{PAPER}.
> Version: \contextversion.
> \placelistofpublications
> \stoptext
>
> @inproceedings{PAPER,
> author = {First Last},
> title = {PaperTitle},
> booktitle = {Conference of BlaBla},
> year = {2017},
> crossref = {CONF},
> }
>
> @proceedings{CONF,
> title = {Conference on BlaBla},
> year = {2017},
> editor = {Edith Tor},
> publisher = {Springer},
> }
>
> Result (copied from pdf):
> See (Last, 2017). Version: 2018.07.02 14:39.
> Last, F. (2017). PaperTitle. In PaperTitle. Conference of BlaBla.
> Author.
>
> Expected (made by manually copying editor/publisher):
> See (Last, 2017). Version: 2018.07.02 14:39.
> Last, F. (2017). PaperTitle. In E. Tor (Ed.) Conference of BlaBla.
> Springer.
>
>
> Should I setup the style differently? Or is the crossref feature not
> supported?
>
> Thanks in advance,
> All the best,
> Joshua
crossref is implemented and works, but failed as shown above, when the
crossref points to a "future" entry, that is one not already processed
(inverting the order of the two entries above will show the desired
behavior).
This is not good: the order should not matter, and Hans has fixed this, to
appear in the "next beta". Thank you Joshua for uncovering this.
Alan
___________________________________________________________________________________
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 prev parent reply other threads:[~2018-07-20 14:10 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-07-12 10:21 context
2018-07-12 16:37 ` Alan Braslau
2018-07-20 14:10 ` context [this message]
-- strict thread matches above, loose matches on Subject: below --
2006-03-23 13:50 crossref " Ulf Martin
2006-03-23 14:48 ` Taco Hoekwater
2006-03-23 18:57 ` Bruce D'Arcus
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='00b701d42033$59de2a60$0d9a7f20$@joshuamoerman.nl' \
--to=context@joshuamoerman.nl \
--cc=braslau.list@comcast.net \
--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).