On Nov 10, 2007, at 5:51 AM, Adam M. Goldstein wrote:

> On Nov 10, 2007, at 4:10 AM, Simon Spiegel wrote:
>
>>
>> On 10.11.2007, at 09:55, Hendrik wrote:
>>
>>>>
>>>> Something I noticed which no one seems to have mentioned yet: For
>>>> some reason Google Scholar always gives the title in double curly
>>>> parantheses, so that BibDesk ends importing. For example:
>>>>
>>>>
>>>> @article{delany1970apf,
>>>>    Author = {Delany, ME and Bazley, EN},
>>>>    Date-Added = {2007-11-10 08:57:42 +0100},
>>>>    Date-Modified = {2007-11-10 08:57:42 +0100},
>>>>    Journal = {Applied Acoustics},
>>>>    Number = {2},
>>>>    Pages = {105--116},
>>>>    Title = {{Acoustical properties of fibrous absorbent materials}},
>>>>    Volume = {3},
>>>>    Year = {1970}}
>>>>
>>>> I realize that this an error on Google's side, but maybe such cases
>>>> could be handled by the importer in general. I can't really think  
>>>> of
>>>> a situations where one wants to have double parantheses.
>>>>
>>>
>>> The double braces tell LaTeX to preserve the capitalization. So if
>>> the
>>> title in Google Scholar is capitalized correctly it will be correct
>>> in
>>> your references.
>>
>> Yeah, well, but in this case they're not capitalized correctly (at
>> least according to the rules I know about capitalization of titles in
>> English).
>>
>>> While this can be useful, I personally would also prefer it if the
>>> BibDesk Scholar scraper would strip the extra set of braces.
>>
>> Anyone against this?
>>
>
> I am for it, if it means that this effectively ends the record. But
> does it?
>
> Regarding capitalization, I pretty much ignore whatever comes in, and
> let the .bst file take care of it. My needs for caps change depending
> on what the output is supposed to be.
>
> -Adam G.

Brackets are supposed to be used to force capitalization of things  
that bst files can't know about; i.e., proper nouns and acronyms. So  
I'm in favor of removing this from Google Scholar; I don't know if  
this can be done in a non-hacky way.

-AHM


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

Reply via email to