Ah-ha! I looked for an option like that but I missed it... Thanks.

It now works correctly with double curly braces in Latex but the OO 
plugin still does not work properly. Appending a comma (which so upset 
bibtex) produced the required "Carbon Trust" citation in the text but 
the reference was still "Trust, C." Removing the comma and introducing 
two lots of curly braces, I'm back to citing as "Trust" and still 
"Trust, C." in the references. Is this an issue with the OO plugin?

P.


On 28/07/14 16:35, Axel Dessecker wrote:
> Peter,
>
> Have you checked Options > Preferences > File > Remove double curly
> braces around BibTeX fields? Sorry, my translation...
>
> Axel
>
>
> Am 28.07.2014 17:15, schrieb Peter Rockett:
>> OK. Tried this but:
>>
>> 1. When running bibtex, I get an error "line xxx of abbrvnat.bst Name1
>>     "Carbon Trust" has a comma at the end for entry CarbonTrust2012
>>     while executing"
>> 2. Although the Open/LibreOffice plugin correctly inserts "Carbon
>>     Trust" in the text, the reference is still shown as "Trust, C.".
>>
>>
>> P.
>>
>>
>>
>> On 28/07/14 14:21, Mario Tavares wrote:
>>> Hi Peter,
>>>
>>> Put a comma "," after the name like this: "The Carbon Trust,"
>>>
>>> Regards,
>>>
>>> Mario Tavares
>>> Canoas, RS, Brazil
>>>
>>>
>>> 2014-07-28 10:17 GMT-03:00 Peter Rockett <[email protected]
>>> <mailto:[email protected]>>:
>>>
>>>      Hi
>>>
>>>      I am trying to cite a technical report where the author is a
>>> corporate
>>>      name, for example "The Carbon Trust".  I can get this to work by
>>>      manually editing the bib file to place two lots of curly braces
>>> around
>>>      the author field, as in:
>>>
>>>      author={{The Carbon Trust}}
>>>
>>>      but when I open the bib file with JabRef, it very helpfully
>>>      removes what
>>>      it seems to regard as one of the redundant pairs of curly braces!
>>>      Hence
>>>      my report is then cited as "... Trust (2012)..." and appears in the
>>>      references as "T. C. Trust, ...".
>>>
>>>      Any ideas on a workaround for this?
>>>
>>>
>>>      P.
>>>
>>>     
>>> ------------------------------------------------------------------------------
>>>
>>>      Infragistics Professional
>>>      Build stunning WinForms apps today!
>>>      Reboot your WinForms applications with our WinForms controls.
>>>      Build a bridge from your legacy apps to the future.
>>>     
>>> http://pubads.g.doubleclick.net/gampad/clk?id=153845071&iu=/4140/ostg.clktrk
>>>
>>>      _______________________________________________
>>>      Jabref-users mailing list
>>>      [email protected]
>>>      <mailto:[email protected]>
>>>      https://lists.sourceforge.net/lists/listinfo/jabref-users
>>>
>>>
>>
>>
>>
>> ------------------------------------------------------------------------------
>> Infragistics Professional
>> Build stunning WinForms apps today!
>> Reboot your WinForms applications with our WinForms controls.
>> Build a bridge from your legacy apps to the future.
>> http://pubads.g.doubleclick.net/gampad/clk?id=153845071&iu=/4140/ostg.clktrk
>>
>>
>>
>> _______________________________________________
>> Jabref-users mailing list
>> [email protected]
>> https://lists.sourceforge.net/lists/listinfo/jabref-users
>>


------------------------------------------------------------------------------
Infragistics Professional
Build stunning WinForms apps today!
Reboot your WinForms applications with our WinForms controls. 
Build a bridge from your legacy apps to the future.
http://pubads.g.doubleclick.net/gampad/clk?id=153845071&iu=/4140/ostg.clktrk
_______________________________________________
Jabref-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/jabref-users

Reply via email to