On Monday, August 13, 2007, at 11:57AM, "Simon Spiegel" <[EMAIL PROTECTED]> wrote: > >On 13.08.2007, at 20:34, Adam R. Maxwell wrote: > >> >> On Monday, August 13, 2007, at 11:31AM, "Simon Spiegel" >> <[EMAIL PROTECTED]> wrote: >>> >>> And yet another question. Do I understand this correctly that only >>> 'editor' and 'author' are treated as names? Styles like jurabib and >>> biblatex offer a bunch of other name fields like 'bookauthor', >>> 'translator' etc. Any chance that these are added? >> >> Add them as "Person" fields in the Defaults pref pane, and they >> should be parsed using BibTeX name rules (and treated as person >> objects, as author and editor are). > >I really learn something new about BibDesk everyday. Ok, I added >'translator' and some other fields, and they're now tread correctly >by BibDesk (for autocomplete et al.), but if I understand you >correctly, I should now be able to use 'persons.translator' and >configure the name like for 'author' in my template file, and this >doesn't work.
After adding Translator as a person field and creating a dummy reference with a couple of translators, this works for me in the default RTF template. What doesn't work? <$publications> <$citeKey/> <$fields.Title/> (<$type/>) <[EMAIL PROTECTED]> <$name/> <$value/> </[EMAIL PROTECTED]> <[EMAIL PROTECTED]/> </$publications> ------------------------------------------------------------------------- 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
