On Apr 5, 2010, at 0:59, Stefan Groth wrote:

> 
> 
>> On Apr 4, 2010, at 3:47, Stefan Groth wrote:
>> 
>>> Hello,
>>> I am currently working on an export template for BibDesk for the AAA style 
>>> (http://www.aaanet.org/publications/style_guide.pdf) and having troubles 
>>> with the author-output for coauthored books. The AAA style suggests the 
>>> format 
>>> 
>>> Lee, Namhee, Lisa Mikesell, and Anna Dina L. Joaquin
>>> 
>>> The string I am using is
>>> 
>>> <$pubauthors.normalizedname.stringbyremovingt...@componentsjoinedbycommaandandwithetalafterthree/>
>>> 
>>> which outputs
>>> 
>>> Lee, Namhee, Mikesell, Lisa, and Joaquin, Anna Dina L.
>>> 
>>> whereas I need
>>> 
>>> Lee, Namhee, Lisa Mikesell, and Anna Dina L. Joaquin
>>> 
>>> How is it possible to achieve a different format for the second author 
>>> name? 
>>> 
>>> Cheers,
>>> Stefan
>> 
>> Style guides really keep amaze me about their weird recommendations. I 
>> wonder in which worlds these guys are living. 
>> 
>> Anyeay, you can get what you want using something like the following (I did 
>> not include the stringByRemovingTeX, and be aware of newlines added by 
>> mailing):
>> 
>> <[email protected]/><$autho...@count<2?><?$autho...@count?>,
>>  and 
>> <[email protected].@componentsJoinedByCommaAndAnd/></$autho...@count?>
>> 
>> Christiaan
> 
> Christiaan,
> thanks a lot. What you suggested results in
> 
>       Lee, Namhee, and Lisa Mikesell, Anna Dina L. Joaquin
> 
> Is there a way to get
> 
>       Lee, Namhee, Lisa Mikesell, and Anna Dina L. Joaquin?
> 

Yes, using more condition tags based on autho...@count, for instance like this:

<$authors.normalizedna...@firstobject/><$autho...@count=0?>
<$autho...@count=1?>
<?$autho...@count=2?>
 and <$authors.na...@secondobject/><?$autho...@count=3?>
, <$authors.na...@secondobject/>, and 
<$authors.na...@thirdobject/><?$autho...@count?>
, <$authors.na...@secondobject/>, <$authors.na...@thirdobject/>, et 
al.</$autho...@count?>

BTW, you should use "authors", not "pubAuthors". 

> And, to avoid such rather boring questions, is there a better documentation 
> for template keys than the list provided in the BibDesk-wiki?
> 
> Stefan

No.

Christiaan

------------------------------------------------------------------------------
Download Intel&#174; Parallel Studio Eval
Try the new software tools for yourself. Speed compiling, find bugs
proactively, and fine-tune applications for parallel performance.
See why Intel Parallel Studio got high marks during beta.
http://p.sf.net/sfu/intel-sw-dev
_______________________________________________
Bibdesk-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/bibdesk-users

Reply via email to