David,
For whatever it is worth, here is how I use macros. I have a separate file (let
us call publications.bib) in which I have all expansions of abbreviations to
full journal names. I keep this in my personal texmf directory
(~/Library/texmf/bibtex). I have modified the template that Bibdesk uses to
display previews (click on TeX Template Edit) in the Style and Template section
of the Preview tab of Bibdesk preferences to include
\bibliography{publications,<<File>>}
Then the Preview within Bibdesk works well and in my latex document I put the
same \bibliography command with the right master bib file name and things work
as they should. This also allows me to develop different expansions for
different purposes (although I never change the Preview preferences to see them
differently within Bibdesk).
I have never used group feature in Bibdesk (I'll check it out) so I am not sure
if this is what you want to do, but I thought it might be helpful.
==Tamer
On Fri 8-Jan-10, at 12:43 AM, david craig wrote:
>
>> 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.
>
> More to the point, from the point of view of maintaining a single master
> bibliographic databse that makes it easy to generate bibliographies for
> individual papers, the whole point of THAT is not having to maintain
> multiple copies of the same set macros.
>
> It's not such a big deal to include that list in the same file as the
> bibliography database, but surely it's not so hard to see why the global
> macros feature might also make sense for this purpose, even if it is not
> how you have learned to conceptualize it?
>
> There is a practical reason for maintaining a separation between the
> master bib entries and the macros. As an example, say one journal wants
> full journal titles, another abbreviated ones. If you maintain two
> parallel sets of journal title expansions, you can have BibDesk load the
> set of macros you need from the appropriate external file before
> exporting the group to an independent bib file. If you keep the macros
> locally in the master file, I do not see an easy way to toggle your
> macro sets like this. Document-specific macros can't be loaded from an
> external file in BibDesk, nor is there an obvious way to integrate this
> freedom with exported groups.
>
> Any of that make sense? I'm open to other approaches, but the simple
> option I suggested in the previous email of including the option to
> include global macros when exporting a group would be one way to take
> care of it quite simply.
>
> Thanks for listening,
> David Craig
>
>
> <http://www.panix.com/~dac/>
>
> ------------------------------------------------------------------------------
> 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
>
------------------------------------------------------------------------------
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
