On 5 May 2009, at 6:22 PM, Robert Sloan wrote: > I have the same issue with sharing with collaborators, and I can > answer the question about why they want a minimal .bib file that they > can read in an editor. > > Some of my collaborators are in the 45-60 age range and have been > writing papers in LaTeX with Bibtex for way over 20 years, and are > really comfortable with the tools that they have been using for eons, > and just not interested in changing to more modern tools. > > In fact, my question is: How do I save out a minimal .bib file for > them, and then get it back with a couple of added cites, and put those > added cites into my large bibtex file that has all my links to the > articles themselves on my hard drives? >
Probably easiest is to add an external file group for the minimal .bib file, and using the merge feature. Christiaan > > On May 5, 2009, at 4:20 AM, bibdesk-users- > [email protected] wrote: > >> Message: 3 >> Date: Mon, 04 May 2009 19:43:15 -0700 >> From: "Adam R. Maxwell" <[email protected]> >> Subject: Re: [Bibdesk-users] Sharing bib managed with Bibdesk with >> non-bibdesk users >> To: For general discussion about using BibDesk >> <[email protected]> >> Message-ID: <[email protected]> >> Content-Type: text/plain; charset="us-ascii" >> >> 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 editor screen space (not to >>> mention bandwith), to no avail for them. >> >> A simple option would be to use File->Export to save a .bib file as >> "minimal" BibTeX for your collaborators. >> >> I think Christiaan added a bunch of the old Local-Url stuff back in, >> so you might be able to use that. I wouldn't recommend it, since it >> makes your links fragile once again and possibly reduces >> functionality. >> >> With cite completion in modern editors, reading the .bib file seems >> unusual to me. Why do they do this (serious question...I'm not >> trying >> to be snotty)? Are your collaborators able to use JabRef or >> something >> similar? Finally, complaining about bandwidth seems like a stretch >> unless they're on a 2400 baud modem... >> >>> 2) Bibdesk writes trailing white spaces which make my version >>> control system complain every single time: >>> >>> trunk/dox/cctbx_references.bib:5: trailing whitespace. >>> +%% Created for Luc Bourhis at 2009-05-04 16:29:15 +0200 >>> ||||||||||||||||||||||||||||||||| >>> trunk/dox/cctbx_references.bib:8: trailing whitespace. >>> +%% Saved with string encoding Western (ISO Latin 1) >>> ||||||||||||||||||||||||||||||||||||| >>> >>> (The ||||||||||||||| aren't in the file of course: I have added them >>> to show where the trailing blank is!) >> >> Offhand, I'm not sure why this would occur, since the only code >> appends a single space and double newline when writing that info. If >> you disable the preference to write a template file when saving, it >> won't be written at all. My own .bib files are still in CVS, and I >> don't recall having this problem. >> >>> I would think that (2) is trivial to fix. >> >> Time for you to fire up gdb :). The code you're looking for is in >> BibDocument.m, line 1556. >> >>> As for (1), I would really love the info stored in the Bdsk-File-1 >>> to live in another file than the bib file. >> >> At that point, you should consider a different program to manage that >> info; storing the file info in a separate file would be a nightmare. >> >> -- >> Adam > > > > Robert H. Sloan http://www.cs.uic.edu/~sloan/ > Professor and Interim Head > Dept. of Computer Science > University of Illinois at Chicago > > 312-996-2369 (office) > 312-413-0024 (fax) > 312-413-2911 (my assistant Ms. Imelda Baker) > > > > > > > ------------------------------------------------------------------------------ > The NEW KODAK i700 Series Scanners deliver under ANY circumstances! > Your > production scanning environment may not be a perfect world - but > thanks to > Kodak, there's a perfect scanner to get the job done! With the NEW > KODAK i700 > Series Scanner you'll get full speed at 300 dpi even with all image > processing features enabled. http://p.sf.net/sfu/kodak-com > _______________________________________________ > Bibdesk-users mailing list > [email protected] > https://lists.sourceforge.net/lists/listinfo/bibdesk-users ------------------------------------------------------------------------------ The NEW KODAK i700 Series Scanners deliver under ANY circumstances! Your production scanning environment may not be a perfect world - but thanks to Kodak, there's a perfect scanner to get the job done! With the NEW KODAK i700 Series Scanner you'll get full speed at 300 dpi even with all image processing features enabled. http://p.sf.net/sfu/kodak-com _______________________________________________ Bibdesk-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/bibdesk-users
