On Nov 10, 2007, at 11:59 AM, Justin C. Walker wrote:
>
> On Nov 10, 2007, at 10:16 , Adam R. Maxwell wrote:
>
>>
>> On Nov 10, 2007, at 9:48 AM, Alexander H. Montgomery wrote:
>>
>>>>>> 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.
>>
>> Try the next nightly build. If the title has surrounding { and }
>> braces, they're removed if it doesn't cause a brace error.
>
> I'm puzzled: since the braces are legit (perhaps Google puts the
> extra set there to keep the title the way they got it?), why remove
> them? I assume I'm missing something, but...
They're not always correct, though, unfortunately. It's generally
better to let the .bst handle capitalization issues, as Alex said,
rather than force it in the database. The records I've seen from
Google Scholar are a mix of title case, sentence case, and all caps.
--
adam
-------------------------------------------------------------------------
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
