Not sure what bug was meant. I still have this problem. Namely, when exporting a reference list "inproceedings" items do not inherit values from crossref'd "proceedings" items, instead 2 references are created one for "inproc." the other for "proc."
e.g. [1] P. Dolog, N. Henze, W. Nejdl, and M. Sintek. Personalization in distributed e-learning environments. In Feldman et al. [2], pages 170–179. [2] S. I. Feldman, M. Uretsky, M. Najork, and C. E. Wills, editors. Proceedings of the 13th international conference on World Wide Web - Alternate Track Papers & Posters, WWW 2004, New York, NY, USA, May 17-20, 2004, New York, NY, USA, 2004. ACM. On 10/2/07, Adam R. Maxwell <[EMAIL PROTECTED]> wrote: > > On Oct 2, 2007, at 02:10, Christiaan Hofman wrote: > > > I think you've misunderstood the meaning of a crossref. It is used to > > pre-fill related items, not to link items. > > Michael's problem was the crossref bug you just fixed :). > > adam > > > > > On 2 Oct 2007, at 3:07 AM, Michael Yudelson wrote: > > > >> Hello Everybody, > >> > >> I'm new to TeX, so please don't judge me for a potentially trivial > >> question. > >> > >> I'm using BibDesk and have a problem with exporting references. I > >> have > >> a number of "proceedings" items in my library that are > >> cross-referenced by "inproceedings" papers. > >> > >> Whenever I try to "Preview" or "Copy Drag" improceeddings items it > >> results in 2(two) references instead of one. Since my BibDesk version > >> is up to date and the BibTeX version as well, I'd expect it to handle > >> crossref field correctly. > >> > >> I've set the appropriate sorting of the items (proceedings after > >> inproceedings). I've tried exporting properly formatted references > >> both to RTF and PDF Nothing seems to work. > >> > >> Any help is appreciated. > >> Best, > >> Michael > >> > >> -- > >> Michael V. Yudelson, > >> PhD candidate > >> School of Information Science, University of Pittsburgh. > >> Email: [EMAIL PROTECTED] Tel: +1 (412) 624-9437 > >> > >> ---------------------------------------------------------------------- > >> --- > >> This SF.net email is sponsored by: Microsoft > >> Defy all challenges. Microsoft(R) Visual Studio 2005. > >> http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ > >> _______________________________________________ > >> Bibdesk-users mailing list > >> [email protected] > >> https://lists.sourceforge.net/lists/listinfo/bibdesk-users > > > > > > ------------------------------------------------------------------------- > > This SF.net email is sponsored by: Microsoft > > Defy all challenges. Microsoft(R) Visual Studio 2005. > > http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ > > _______________________________________________ > > Bibdesk-users mailing list > > [email protected] > > https://lists.sourceforge.net/lists/listinfo/bibdesk-users > > > ------------------------------------------------------------------------- > This SF.net email is sponsored by: Microsoft > Defy all challenges. Microsoft(R) Visual Studio 2005. > http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ > _______________________________________________ > Bibdesk-users mailing list > [email protected] > https://lists.sourceforge.net/lists/listinfo/bibdesk-users > -- Michael V. Yudelson, PhD candidate School of Information Science, University of Pittsburgh. Email: [EMAIL PROTECTED] Tel: +1 (412) 624-9437 ------------------------------------------------------------------------- This SF.net email is sponsored by: Splunk Inc. Still grepping through log files to find problems? Stop. Now Search log events and configuration files using AJAX and a browser. Download your FREE copy of Splunk now >> http://get.splunk.com/ _______________________________________________ Bibdesk-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/bibdesk-users
