On 12 Jan 2009, at 7:58 PM, Christian Plessl wrote:
> Hi Christiaan
>
>>> Is this intended behavior? A possible workaround might be to re-
>>> define
>>> each month with a macro @{jan = January}, but this seems too hackish
>>> for me.
>>>
>>> Best regards,
>>> Christian
>>
>> Yes, BibDesk uses the month names from the user localization for the
>> default month name macros. If you want to change this, you can
>> override the macros for the month name. Either in your document or in
>> BD's Fields prefs.
>
>
> My tests showed that this doesn't work as I would like. I think most
> BibTeX styles expect that the months are written with three letter
> abbreviations, jan, feb, ... If I define a @String{jan = {January}} or
> @String{jan = {jan}} macro, January or jan will be included in curly
> braces and thus treated literally.
Well, that's what you were asking for: you asked it to be expanded as
"January", and that's what this does. If not, then please tell me what
you want to achieve.
>
> Is there a way how I can iterate over all fields but the month field
> and use the bibTeXString key instead of value for month in my template
> (see below)?
Why would you want to treat the month differently from the other
fields? Do you want to expand macros in the exported bibtex or not?
> Is there an array modifier for excluding a key, I
> couldn't find any.
No array modifiers, wouldn't even be possible. You can use condition
tags to treat some fields differently. But is that really what you want?
>
> <$publications>
> @<$pubType/>{<$citeKey/><$allfiel...@nonempty>,
> <$name/> = {<$value/>}</$allfiel...@nonempty>}
> </$publications>
>
> Best regards,
> Christian
------------------------------------------------------------------------------
This SF.net email is sponsored by:
SourcForge Community
SourceForge wants to tell your story.
http://p.sf.net/sfu/sf-spreadtheword
_______________________________________________
Bibdesk-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/bibdesk-users
