To be precise, it's a base64 encoded (keyed) archived dictionary containing a relative path and a file alias (an alias stores a full path and a file ID). It is designed to support a large range of storage procedures, as it can find a file by relative path, absolute path, and file ID (in that order). This means that you can - move/rename the .bib file (as it stores full paths) - move/rename a linked file (as it stores file IDs) - move the .bib file and linked files together (as it stores relative paths) - copy the .bib file and linked files togther, even between different machines (as it stores relative paths)
Christiaan On 31 Jul 2008, at 2:12 AM, jbsnyder wrote: > > Hi - > > I'm wondering how the Bdsk-File-1 entries in bib files are encoded, > and if > it should be relatively easy to have a centralized location where > papers can > be stored and shared along with the bib file that references them. > > I'm guessing that Bdsk-File-1 might be something like a base64 > encoding of > the full path to the file, but I'm not sure. I'm also not sure if > the > "file papers relative to each document" might make sharing a bib > file with > associated paper pdfs simple across different machines with different > pathnames. Are perhaps full and relative pathnames stored in the > bib file? > > Thanks in advance, I love Bibdesk :-) > > -jsnyder ------------------------------------------------------------------------- This SF.Net email is sponsored by the Moblin Your Move Developer's challenge Build the coolest Linux based applications with Moblin SDK & win great prizes Grand prize is a trip for two to an Open Source event anywhere in the world http://moblin-contest.org/redirect.php?banner_id=100&url=/ _______________________________________________ Bibdesk-users mailing list Bibdesk-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bibdesk-users
