On Jan 7, 2010, at 8:47 PM, david craig wrote: > Ok, here's another reason groups don't work all that smoothly as a means > of implementing a master bibtex database file. I realize now that > global macros are NEVER written into an exported bib file, only a > document's macros.
This is by design. The global macros feature was intended to allow expansion of macros defined in .bst files or global .bib files that you'd normally include in a .tex document via the \bibliography command. > A workaround is to write all of one's macros into the master file > directly and forget about global macros, I suppose. That's not a workaround; you just need to stop abusing the global macro feature :). The entire point of it is to display macros that you do not want included in your database. > Right now, there's no way (as far as I can see) to properly export a > group as a self-contained bib file. Selecting the members of the group > and exporting is really only using the group as a shortcut to the > selection, and doesn't take care of the macros. As you already noticed, it exports all of the macros in your file, which creates a standalone file that will work perfectly with BibTeX. It would be quite complicated to determine which macros and their dependencies are required, and I have a hard time believing it would be worth the effort. Christiaan might have a different opinion, though, or accept a patch to do this…although the macro code is non-trivial, to say the least. ------------------------------------------------------------------------------ This SF.Net email is sponsored by the Verizon Developer Community Take advantage of Verizon's best-in-class app development support A streamlined, 14 day to market process makes app distribution fast and easy Join now and get one step closer to millions of Verizon customers http://p.sf.net/sfu/verizon-dev2dev _______________________________________________ Bibdesk-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/bibdesk-users
