Re: [NTG-context] Crossref in bibtex

2018-07-21 Thread context
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  
Sent: 12 July 2018 18:37
To: cont...@joshuamoerman.nl
Cc: mailing list for ConTeXt users 
Subject: Re: [NTG-context] Crossref in bibtex

On Thu, 12 Jul 2018 12:21:28 +0200
 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
___

Re: [NTG-context] Crossref in bibtex

2018-07-12 Thread Alan Braslau
On Thu, 12 Jul 2018 12:21:28 +0200
 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
___

Re: [NTG-context] crossref in bibtex

2006-03-23 Thread Taco Hoekwater


Hi Ulf,
Ulf Martin wrote:
 Crossrefs don't seem to work properly.

There isn't one, only a partial workaround: manually add a line of

   \nocite[crossref-ed entry]

in your source somewhere, and at least the module will typeset the 
cross-referenced item itself.

I will reconsider fixing this, but it is one of the more annoying
things to get right.

 
 A hint to the solution for an expert could be the bbl file. Note that 
 the order of the entries is turned around:

No, that is absolutely unrelated. The .bbl file in context is nothing
else than a representation in TeX macros of the original .bib file(s).

 (If ordered by author first, then year. Note also that in \language[de] 
 vol. should be Bd. and p. be S..)

Someone could create a bibl-aps-de.tex file, but I can not. It would
just be a copy of bibl-aps.tex, but with german strings instead of
english ones. You would still need to use an explicit language like

   \setuppublications[alternative=aps-de]

though (because switching based on the current document language is not
necessarily correct and is therefore unsupported).

 Any ideas of what to do or hints where to find more info?

Rgiht here, on this list.

* * *
 
 Additional question: what is the best way to generate the bbl file in 
 the project directory? (I use Central.bib for all my documents).
 
 Using
 
 % texexec mainsetup
 
 in the projects directory produces many unnecessary files (e.g. a dvi 
 file) as it is only meant as a setup file.

You only have to generate the bbl file once, so that should not be
a big burden. You could feasibly create a dummy file that is 4 or 5 
lines long and has nothing but the \usemodule  \setupbibtex lines,
run that, and rename the resulting bbl file.

 However, proper bibliography processing is a killer feature for me -- 
 I have virtually no document whithout references. (I wonder, what the 
 direction of the ConText development here is; arguably, odd old BibTeX 
 has reached an end of its history and support for more modern and 
 complete, e.g. XML-based formats would be preferable (say, MODS) -- 
 considering the seeminly nice XML support that is already there.)

Bibtex is a rather idiosyncratic and LaTeX-centric program, and it
already takes some effort to make bibtex believe that ConTeXt is
enough like LaTeX to make it work. I do not wish to spend much
more time catering for the bizarreness that is bibtex than I
already have.

The next major release of the module (but don't expect a release
anywhere this year) will indeed support MODS through citeproc:

http://xbiblio.sourceforge.net/citeproc/

Cheers, Taco


___
ntg-context mailing list
ntg-context@ntg.nl
http://www.ntg.nl/mailman/listinfo/ntg-context


Re: [NTG-context] crossref in bibtex

2006-03-23 Thread Bruce D'Arcus
Taco Hoekwater taco at elvenkind.com writes:

[.. snip ...]

 The next major release of the module (but don't expect a release
 anywhere this year) will indeed support MODS through citeproc:
 
   http://xbiblio.sourceforge.net/citeproc/

As the author of citeproc (hi Taco!), let me just update people on recent
developments there, which are currently in the project subversion repository*,
but not yet officially released.

First, I have switched to using a particular RDF/XML as the internal
representation, and also therefore the primary input format. I will likely be
adding back a MODS input driver when I get a chance, but it's no longer the
focus. I will also be releasing a schema for this RDF representation for people
that need it.

The primary reason for this change is that in comparison to MODS, RDF has a
consistent model that makes it easier to model reference metadata. It's also
fundamentally a relational model, and so easier to integrate with relational
databases where needed.

Also, I am working with the OpenDocument Technical Committee on a plan to add
extensible metadata support using this RDF-based approach, so we hope to adopt
this in OpenOffice as well (I am co-project lead for the OOo bib project).

Second, I have started porting CiteProc to Ruby (and put a citeproc-py directory
in the repo for those python coders that might want to contribute), which might
integrate better with ConTeXt. (I suppose Lua might also be an option given the
integration with pdftex?) In any case, this will take me a bit of time as a) I
don't have much of it, and b) my coding skills aren't that great.

But the actual formatting code (Ruby, XSLT, etc.) is to my mind less important
than the logic as embedded in the XML citation style language I wrote to
configure the formatting.

http://xbiblio.sourceforge.net/csl/

Bruce

* http://svn.sourceforge.net/viewcvs.cgi/xbiblio/

___
ntg-context mailing list
ntg-context@ntg.nl
http://www.ntg.nl/mailman/listinfo/ntg-context