Re: [Bibdesk-users] Sharing bib managed with Bibdesk with non-bibdesk users

2009-05-04 Thread Adam R. Maxwell
On May 4, 2009, at 4:42 PM, Luc Bourhis wrote: although bibdesk is invaluable to me, I have a few gripes when it comes to share a bib file managed by Bibdesk with non-bibdesk users. 1) My collaborators keep complaining about the Bdsk-File-1 entries which takes a very large amount of text ed

Re: [Bibdesk-users] Sharing bib managed with Bibdesk with non-bibdesk users

2009-05-04 Thread Mark Moll
On May 4, 2009, at 6:42 PM, Luc Bourhis wrote: > 1) My collaborators keep complaining about the Bdsk-File-1 entries > which takes a very large amount of text editor screen space (not to > mention bandwith), to no avail for them. Install bibtool [*] and execute the following command in the te

Re: [Bibdesk-users] Adding biblio entries by adding PDFs "lose"diacritics

2009-05-04 Thread Maxwell, Adam R
On 05/04/09 15:49, "Gregory Jefferis" wrote: > On 2009-05-02 23:30, "Adam R. Maxwell" wrote: > >> >> I wrote a parser for the XML format. Can anyone suggest some PMIDs or > Great! Have you committed or do you have a patch? No. I developed it on my own tree, since that's what I'm set up to

[Bibdesk-users] Sharing bib managed with Bibdesk with non-bibdesk users

2009-05-04 Thread Luc Bourhis
Hi, although bibdesk is invaluable to me, I have a few gripes when it comes to share a bib file managed by Bibdesk with non-bibdesk users. 1) My collaborators keep complaining about the Bdsk-File-1 entries which takes a very large amount of text editor screen space (not to mention bandwit

Re: [Bibdesk-users] Adding biblio entries by adding PDFs "lose"diacritics

2009-05-04 Thread Gregory Jefferis
On 2009-05-02 23:30, "Adam R. Maxwell" wrote: > > I wrote a parser for the XML format. Can anyone suggest some PMIDs or Great! Have you committed or do you have a patch? > search terms that result in data loss presently? I also never use Try PMID: 12767029 > PubMed, so I only tested with ra

Re: [Bibdesk-users] Abbreviated @STRING

2009-05-04 Thread M. Tamer Özsu
Thank you. I think revising the tex template file is easier and I'll try that. ==Tamer On Mon 4-May-09, at 3:14 PM, Christiaan Hofman wrote: > If you want to include macros from an external file for the TeX > preview the simplest way to achieve that is to edit the tex template > file (see the

Re: [Bibdesk-users] EBSCO changes file structure

2009-05-04 Thread Christiaan Hofman
The RIS specs explicitly say that references must start with "TY - " and end with "ER - ", see . Perhaps you can point them to that, it's their bug. Christiaan On 4 May 2009, at 9:09 PM, Cloy Tobola wrote: > I'm currently using BibDe

Re: [Bibdesk-users] Abbreviated @STRING

2009-05-04 Thread Christiaan Hofman
If you want to include macros from an external file for the TeX preview the simplest way to achieve that is to edit the tex template file (see the preview preferences). Or you can add the macros to the .bst file that you use. Christiaan On 4 May 2009, at 9:06 PM, M. Tamer Özsu wrote: > Con

[Bibdesk-users] EBSCO changes file structure

2009-05-04 Thread Cloy Tobola
I'm currently using BibDesk 1.3.20 (1412) The file structure for citations being downloaded from EBSCO seems to have changed. Below is an example of a citation that will not open correctly. If I remove the first two lines (DP and DB), the file opens in BibDesk correctly. Earlier citations

Re: [Bibdesk-users] Abbreviated @STRING

2009-05-04 Thread M. Tamer Özsu
Continuing a question that was asked earlier... I now know how to enter the raw data for macros, but is there a way that I can specify that the macro definitions are in an external file? I wanted to do this so that Tex Preview would expand things properly and show the correct typesetting. T

Re: [Bibdesk-users] Adding biblio entries by adding PDFs "lose"diacritics

2009-05-04 Thread Maxwell, Adam R
On 05/02/09 02:31, "Christiaan Hofman" wrote: > > On 2 May 2009, at 9:10 AM, Grant Jacobs wrote: > >>> It >>> seems that they also provide an XML format that retains the >>> diacritics, but we don't know yet what syntax they use. Documentation >>> about that is extremely sparse and unreadable.