On Tue, Apr 13, 2010 at 2:22 AM, Christiaan Hofman <[email protected]> wrote:
>
> On Apr 13, 2010, at 11:06, Christiaan Hofman wrote:
>
>>
>> On Apr 13, 2010, at 2:45, Peter Cowan wrote:
>>
>>> All,
>>>
>>> Two of my favorite issues in BibDesk are the autofile feature and the
>>> "Send via Email" features.  Recently I ran into an issue where when
>>> certain citations were selected the "Send via Email" silently failed.
>>> This turned out to be because the associated pdf filename was
>>>
>>> "Sax D & Gaines S 2003 Trends In Ecology \& Evolution.pdf"
>>>
>>> Getting rid of the slash before "&" fixed the issue.
>>>
>>> My autofile format string is: %A[ & ][ ]3 %Y%u0 %f{Journal}30%e
>>>
>>> and I have selected "Clean by removing Tex".  This produces the above
>>> file for the citation:
>>>
>>> Sax DF, Gaines SD (2003) Species diversity: from global decreases to
>>> local increases. Trends In Ecology & Evolution 18, 561–566.
>>>
>>> To summarize, some of my journal names have "&" in them which is
>>> escaped as "\&", which is subsequently in the filename when using
>>> autofile.  These files then cause "Send via Email" to fail.
>>>
>>> What am I doing wrong? Is there a work around?
>>>
>>> Thanks
>>>
>>> Peter
>>>
>>
>> Unfortunately, I think you're doing nothing wrong and there's no workaround.
>>
>> Christiaan
>
> I've fixed this for tomorrow's nightly, please test it out.

Christiaan,

Thanks for such a quick response.  I tried the nightly marked
"BibDesk-20100413.dmg" (is there a way to tell which SVN revision that
is?).  And, I also checked out the source and attempted to build it
myself (which seemed successful with the debug type selected).

Unfortunately, both versions also fail silently, with the file: "Sax D
& Gaines S 2003 Trends In Ecology \& Evolution.pdf".   I get the
following message in the console:

4/14/10 2:34:25 PM      BibDesk[11223]  Error compiling mail to script: {
    NSAppleScriptErrorBriefMessage = "Expected \U201c\"\U201d but
found unknown token.";
    NSAppleScriptErrorMessage = "Expected \U201c\"\U201d but found
unknown token.";
    NSAppleScriptErrorNumber = "-2741";
    NSAppleScriptErrorRange = "NSRange: {463, 1}";
}

Did the nightly I grabbed not have the relevant update?   I appreciate
you attention, to this minor issue!

Peter


>
> 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
>

------------------------------------------------------------------------------
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