Just Launched: You can now import projects and releases from Google Code onto SourceForge

We are excited to release new functionality to enable a 1-click import from Google Code onto the Allura platform on SourceForge. You can import tickets, wikis, source, releases, and more with a few simple steps.

bibdesk-users — For discussion about using BibDesk.

You can subscribe to this list here.

2002 2003 2004 2005 2006 2007 2008 2009 2010 2011 2012 2013 Jan Feb Mar Apr May Jun Jul Aug Sep (3) Oct (2) Nov Dec (1) Jan Feb (4) Mar (5) Apr (4) May (14) Jun (12) Jul (3) Aug (1) Sep (3) Oct (5) Nov (21) Dec (7) Jan (13) Feb (5) Mar (37) Apr (17) May (5) Jun (18) Jul (19) Aug (16) Sep (63) Oct (108) Nov (65) Dec (132) Jan (73) Feb (176) Mar (131) Apr (106) May (153) Jun (99) Jul (94) Aug (110) Sep (218) Oct (194) Nov (257) Dec (200) Jan (178) Feb (182) Mar (152) Apr (58) May (135) Jun (113) Jul (103) Aug (197) Sep (101) Oct (101) Nov (68) Dec (208) Jan (520) Feb (203) Mar (197) Apr (200) May (110) Jun (167) Jul (162) Aug (206) Sep (199) Oct (312) Nov (283) Dec (246) Jan (350) Feb (163) Mar (233) Apr (168) May (183) Jun (152) Jul (130) Aug (81) Sep (79) Oct (158) Nov (98) Dec (153) Jan (230) Feb (171) Mar (108) Apr (68) May (140) Jun (53) Jul (52) Aug (110) Sep (68) Oct (17) Nov (28) Dec (82) Jan (141) Feb (80) Mar (39) Apr (102) May (86) Jun (37) Jul (56) Aug (62) Sep (108) Oct (24) Nov (7) Dec (27) Jan (19) Feb (18) Mar (33) Apr (45) May (38) Jun (53) Jul (26) Aug (142) Sep (78) Oct (75) Nov (79) Dec (19) Jan (49) Feb (39) Mar (28) Apr (14) May (56) Jun (16) Jul (41) Aug (17) Sep (15) Oct (38) Nov (35) Dec (22) Jan (44) Feb (30) Mar (30) Apr (53) May (1) Jun (4) Jul (9) Aug (21) Sep (22) Oct (2) Nov (26) Dec (58) Jan (27) Feb (2) Mar Apr May Jun Jul Aug Sep Oct Nov Dec
S M T W T F S

1
(1)
2

3
(2)
4

5

6
(1)
7

8
(5)
9
(2)
10
(10)
11
(1)
12
(11)
13
(2)
14

15
(4)
16
(3)
17
(4)
18
(3)
19
(13)
20

21

22

23
(4)
24
(1)
25

26

27
(2)
28

29
(8)
30
(2)

Showing results of 79

1 2 3 4 > >> (Page 1 of 4)
 Re: [Bibdesk-users] Add field based on another field's contents From: Maxwell, Adam R - 2011-11-30 21:24:37 On Nov 30, 2011, at 11:39, Alan Munn wrote: > Hi, I've added a field to each of my @article entries, and no I want to add values in bulk to that field based on the value of some other field in the entry. Can I do this with database search and replace (or some other method?) > > E.g. set the value of the MyField field to "True" if the Journal field is "Journal of Linguistics". Sounds like a job for AppleScript. As far as I know, the advanced find & replace doesn't do anything this exotic. 
 [Bibdesk-users] Add field based on another field's contents From: Alan Munn - 2011-11-30 19:40:27 Hi, I've added a field to each of my @article entries, and no I want to add values in bulk to that field based on the value of some other field in the entry. Can I do this with database search and replace (or some other method?) E.g. set the value of the MyField field to "True" if the Journal field is "Journal of Linguistics". Alan -- Alan Munn amunn@... 
 Re: [Bibdesk-users] Local-Url field From: FZiegler - 2011-11-29 22:39:52 Christiaan Hofman wrote: > if (count of linked files) > 0 then > >> set thePath to quoted form of (get POSIX path of linked file 1) >> set thePath to do shell script "echo " & thePath & "|sed -e >> \"s|$HOME|~|\"" >> set value of field "Local-Url" to thePath > > delete linked file 1 > end if Yay -- that works perfectly. Thank you so much! Francois   Re: [Bibdesk-users] Local-Url field From: Christiaan Hofman - 2011-11-29 22:31:54 On Nov 29, 2011, at 23:14, FZiegler wrote: > Christiaan Hofman wrote: >> On Nov 29, 2011, at 22:57, FZiegler wrote: >> >>>> Well, you could. But it could lead to some inconsistencies in how things work, because BibDesk assumes that they are data. If you don't want to save them, then simply don't have linked files in your database, it's as simple as that. >>> Aha. Now I see that control-clicking a linked file gives me a "remove" >>> option. So I'll link files to have my script generate Local-Url, then >>> remember to always immediately "remove" the file and choose not to have >>> it moved to the trash -- I guess that's the idea? That works for me. >>> >>> Thanks, >>> Francois >> >> Doen't the script remove the linked file? > > Hmmmm, no, but you're makink me realize that there probably is a way to > make it do all the operations I spelled out above? This is what it does > currently: > > using terms from application "BibDesk" > on perform BibDesk action with publications thePubs for script hook > theScriptHook > repeat with thePub in thePubs > set thePub to contents of thePub > tell thePub if (count of linked files) > 0 then > set thePath to quoted form of (get POSIX path of linked file 1) > set thePath to do shell script "echo " & thePath & "|sed -e > \"s|$HOME|~|\"" > set value of field "Local-Url" to thePath delete linked file 1 end if > end tell > end repeat > end perform BibDesk action with publications > end using terms from > >> And how do you get the linked file in the first place? > > By dropping it from the Finder onto the "Drop Files Here" well. (So far > as I can tell, dropping a file onto the "Local-Url" field creates a link > to where it is, but no longer autofiles it as it used to in 1.3.12.) > > Thanks again, > Francois An alternative is to auto-file through a script hook. Christiaan 
 Re: [Bibdesk-users] Local-Url field From: FZiegler - 2011-11-29 22:14:36 Christiaan Hofman wrote: > On Nov 29, 2011, at 22:57, FZiegler wrote: > >>> Well, you could. But it could lead to some inconsistencies in how things work, because BibDesk assumes that they are data. If you don't want to save them, then simply don't have linked files in your database, it's as simple as that. >> Aha. Now I see that control-clicking a linked file gives me a "remove" >> option. So I'll link files to have my script generate Local-Url, then >> remember to always immediately "remove" the file and choose not to have >> it moved to the trash -- I guess that's the idea? That works for me. >> >> Thanks, >> Francois > > Doen't the script remove the linked file? Hmmmm, no, but you're makink me realize that there probably is a way to make it do all the operations I spelled out above? This is what it does currently: using terms from application "BibDesk" on perform BibDesk action with publications thePubs for script hook theScriptHook repeat with thePub in thePubs set thePub to contents of thePub tell thePub set thePath to quoted form of (get POSIX path of linked file 1) set thePath to do shell script "echo " & thePath & "|sed -e \"s|\$HOME|~|\"" set value of field "Local-Url" to thePath end tell end repeat end perform BibDesk action with publications end using terms from > And how do you get the linked file in the first place? By dropping it from the Finder onto the "Drop Files Here" well. (So far as I can tell, dropping a file onto the "Local-Url" field creates a link to where it is, but no longer autofiles it as it used to in 1.3.12.) Thanks again, Francois 
 Re: [Bibdesk-users] Local-Url field From: Christiaan Hofman - 2011-11-29 22:03:01 On Nov 29, 2011, at 22:57, FZiegler wrote: > Christiaan Hofman wrote: >> On Nov 29, 2011, at 21:30, FZiegler wrote: >> >>> Christiaan Hofman wrote: >>>> On Nov 18, 2011, at 6:58, FZiegler wrote: >>>> >>>>> 1) The line set value of field "Bdsk-File-1" to ""' has no effect. It is meant to erase that field, but it seems it either doesn't or the field gets regenerated on every save. Is there a better way that would actually remove it? >>>>> >>>> You should never access those fields. Those fields only exists in the saved file, they don't exist in the program. You only have the linked files, so if you want to remove them you should delete those. >>> I understood tyhe above and removed this line from my script, but no I >>> do in fact have to ask: is there a simple change I could make in >>> BibDesk's source so that on saving a file it *doesn't* write these >>> "Bdsk-File-*" fields? (or at least writes empty fields?) >>> >> >> Well, you could. But it could lead to some inconsistencies in how things work, because BibDesk assumes that they are data. If you don't want to save them, then simply don't have linked files in your database, it's as simple as that. > > Aha. Now I see that control-clicking a linked file gives me a "remove" > option. So I'll link files to have my script generate Local-Url, then > remember to always immediately "remove" the file and choose not to have > it moved to the trash -- I guess that's the idea? That works for me. > > Thanks, > Francois Doen't the script remove the linked file? And how do you get the linked file in the first place? Christiaan 
 Re: [Bibdesk-users] Local-Url field From: FZiegler - 2011-11-29 21:57:16 Christiaan Hofman wrote: > On Nov 29, 2011, at 21:30, FZiegler wrote: > >> Christiaan Hofman wrote: >>> On Nov 18, 2011, at 6:58, FZiegler wrote: >>> >>>> 1) The line set value of field "Bdsk-File-1" to ""' has no effect. It is meant to erase that field, but it seems it either doesn't or the field gets regenerated on every save. Is there a better way that would actually remove it? >>>> >>> You should never access those fields. Those fields only exists in the saved file, they don't exist in the program. You only have the linked files, so if you want to remove them you should delete those. >> I understood tyhe above and removed this line from my script, but no I >> do in fact have to ask: is there a simple change I could make in >> BibDesk's source so that on saving a file it *doesn't* write these >> "Bdsk-File-*" fields? (or at least writes empty fields?) >> > > Well, you could. But it could lead to some inconsistencies in how things work, because BibDesk assumes that they are data. If you don't want to save them, then simply don't have linked files in your database, it's as simple as that. Aha. Now I see that control-clicking a linked file gives me a "remove" option. So I'll link files to have my script generate Local-Url, then remember to always immediately "remove" the file and choose not to have it moved to the trash -- I guess that's the idea? That works for me. Thanks, Francois 
 Re: [Bibdesk-users] Local-Url field From: Christiaan Hofman - 2011-11-29 21:41:29 On Nov 29, 2011, at 21:30, FZiegler wrote: > Christiaan Hofman wrote: >> On Nov 18, 2011, at 6:58, FZiegler wrote: >> >>> 1) The line set value of field "Bdsk-File-1" to ""' has no effect. It is meant to erase that field, but it seems it either doesn't or the field gets regenerated on every save. Is there a better way that would actually remove it? >>> >> >> You should never access those fields. Those fields only exists in the saved file, they don't exist in the program. You only have the linked files, so if you want to remove them you should delete those. > > I understood tyhe above and removed this line from my script, but no I > do in fact have to ask: is there a simple change I could make in > BibDesk's source so that on saving a file it *doesn't* write these > "Bdsk-File-*" fields? (or at least writes empty fields?) > Well, you could. But it could lead to some inconsistencies in how things work, because BibDesk assumes that they are data. If you don't want to save them, then simply don't have linked files in your database, it's as simple as that. > Reason: I've always had my .bib file mirrored between my desktop and > laptop, using Unison. That worked fine under 1.3.12. But now say Unison > copies the file, desktop-->laptop. The next time I open it on the laptop > and save even once, all Bdsk-File-* fields change so the next Unison run > reports the file as no longer in sync, even if *I* made no changes to > it. Actual user-made changes get drowned in the noise of these alias > changes. > > As I don't actually need these fields in the file (thanks to the > applescript you helped me write), I'd rather just get rid of them, than > return to 1.3.12. Unless you suggest yet another way of solving this > problem? I have a hard time believing I'm the first person to hit it. > > Francois I already explained how you can live without having linked files. Christiaan 
 Re: [Bibdesk-users] Local-Url field From: FZiegler - 2011-11-29 20:31:36 Christiaan Hofman wrote: > On Nov 18, 2011, at 6:58, FZiegler wrote: > >> 1) The line set value of field "Bdsk-File-1" to ""' has no effect. It is meant to erase that field, but it seems it either doesn't or the field gets regenerated on every save. Is there a better way that would actually remove it? >> > > You should never access those fields. Those fields only exists in the saved file, they don't exist in the program. You only have the linked files, so if you want to remove them you should delete those. I understood the above and removed this line from my script, but now I do in fact have to ask: is there a simple change I could make in BibDesk's source so that on saving a file it *doesn't* write these "Bdsk-File-*" fields? (or at least writes empty fields?) Reason: I've always had my .bib file mirrored between my desktop and laptop, using Unison. That worked fine under 1.3.12. But now say Unison copies the file, desktop-->laptop. The next time I open it on the laptop and save even once, all Bdsk-File-* fields change so the next Unison run reports the file as no longer in sync, even if *I* made no changes to it. Actual user-made changes get drowned in the noise of these alias changes. As I don't actually need these fields in the file (thanks to the applescript you helped me write), I'd rather just get rid of them, than return to 1.3.12. Unless you suggest yet another way of solving this problem? I have a hard time believing I'm the first person to hit it. Francois 
 Re: [Bibdesk-users] Local-Url field From: FZiegler - 2011-11-29 20:30:45 Christiaan Hofman wrote: > On Nov 18, 2011, at 6:58, FZiegler wrote: > >> 1) The line set value of field "Bdsk-File-1" to ""' has no effect. It is meant to erase that field, but it seems it either doesn't or the field gets regenerated on every save. Is there a better way that would actually remove it? >> > > You should never access those fields. Those fields only exists in the saved file, they don't exist in the program. You only have the linked files, so if you want to remove them you should delete those. I understood tyhe above and removed this line from my script, but no I do in fact have to ask: is there a simple change I could make in BibDesk's source so that on saving a file it *doesn't* write these "Bdsk-File-*" fields? (or at least writes empty fields?) Reason: I've always had my .bib file mirrored between my desktop and laptop, using Unison. That worked fine under 1.3.12. But now say Unison copies the file, desktop-->laptop. The next time I open it on the laptop and save even once, all Bdsk-File-* fields change so the next Unison run reports the file as no longer in sync, even if *I* made no changes to it. Actual user-made changes get drowned in the noise of these alias changes. As I don't actually need these fields in the file (thanks to the applescript you helped me write), I'd rather just get rid of them, than return to 1.3.12. Unless you suggest yet another way of solving this problem? I have a hard time believing I'm the first person to hit it. Francois 
 Re: [Bibdesk-users] BibDesk manual as single PDF? From: Michael Singer - 2011-11-27 05:15:48  Re: [Bibdesk-users] BibDesk manual as single PDF?
It probably makes sense to include this link to that EF forum post. (The forum settings have been changed to allow downloading of attachments w/o signing in.)

I didn't fix the Texinfo source, but I did post a workflow on the EagleFiler forum for making a single pdf from paginated html manuals. It makes a usable 6.5 MB pdf version of the Bibdesk manual.

(The workflow uses SiteSucker, EagleFiler, Applescript, and Automator.)

Michael

I'm sure no one would object to you fixing the problems in the Texinfo
source that keep it from being converted to PDF.

 Re: [Bibdesk-users] BibDesk manual as single PDF? From: Michael Singer - 2011-11-27 02:55:19 I didn't fix the Texinfo source, but I did post a workflow on the EagleFiler forum for making a single pdf from paginated html manuals. It makes a usable 6.5 MB pdf version of the Bibdesk manual. (The workflow uses SiteSucker, EagleFiler, Applescript, and Automator.) Michael >I'm sure no one would object to you fixing the problems in the Texinfo >source that keep it from being converted to PDF. 
 Re: [Bibdesk-users] Applescript Question From: Fischlin Andreas - 2011-11-24 09:13:40 Don't do any hacks with BibDesk. BibDesk allows to do everything with AppleScripts quite nicely. To remove a field, make it empty, i.e. assign an empty string value and the filed will be gone. For actual code examples see my script collection at http://www.sysecol.ethz.ch/people/afischli/software Regards, Andreas NOTE: I have a new mobile number! ETH Zurich Prof. Dr. Andreas Fischlin Systems Ecology - Institute of Integrative Biology CHN E 21.1 Universitaetstrasse 16 8092 Zurich SWITZERLAND andreas.fischlin@... http://www.sysecol.ethz.ch; +41 44 633-6090 phone +41 44 633-1136 fax +41 79 595-4050 mobile Make it as simple as possible, but distrust it! ________________________________________________________________________ On 23/11/2011, at 16:41 , Di Xiao wrote: On Wed, Nov 23, 2011 at 5:25 AM, Christiaan Hofman > wrote: On Nov 23, 2011, at 3:10, Di Xiao wrote: I'm writing an applescript to do the following 1) import bibtex from a webpage in safari 2) generate a cite key according to the auto generation rule set in preferences Below is the part of applescript tell document 1 of application "BibDesk" activate set myPub to first item of (import from theBibTeXString) set selection to {myPub} tell application "System Events" to keystroke "k" using {command down} end tell However, I ran into the following problem. I use keyword groups. If BibDesk is already running and one of the keyword groups is selected, then the the last line won't run because, unless the imported entry has the same keyword, it won't be selected. I checked the BibDesk dictionary in Applescript Editor. It seems that I can first select the "library group" right after "activate". But I cannot figure out the proper way to do it. Any help is appreciated. D. Using system events to simulate key strokes is something of a hack, you should not use that if it's not necessary. In this case you can simply generate and set the cite key in applescript. tell application "BibDesk" activate set theFormat to cite key format tell document 1 set thePubs to (import from theBibTeXString) if count of thePubs > 0 then set myPub to (get first item of thePubs) set theCiteKey to parse format theFormat for "Cite Key" from myPub set cite key of myPub to theCiteKey end if end tell end tell Christiaan Hi Christiaan, Thanks a lot! I was wondering if there is a more elegant way to do the cite key generation. I have another question. I have a script saved in BibDesk's script folder to do some format cleaning after a record is imported, i.e., remove some unnecessary field added by the publisher. Right now what I'm doing is again to assign a menu shortcut to that script, then call it using the system events. Is there a way to call that script from the current applescript? Di ------------------------------------------------------------------------------ All the data continuously generated in your IT infrastructure contains a definitive record of customers, application performance, security threats, fraudulent activity, and more. Splunk takes this data and makes sense of it. IT sense. And common sense. http://p.sf.net/sfu/splunk-novd2d _______________________________________________ Bibdesk-users mailing list Bibdesk-users@... https://lists.sourceforge.net/lists/listinfo/bibdesk-users 
 Re: [Bibdesk-users] Applescript Question From: Di Xiao - 2011-11-23 15:41:30 On Wed, Nov 23, 2011 at 5:25 AM, Christiaan Hofman wrote: > > On Nov 23, 2011, at 3:10, Di Xiao wrote: > >> I'm writing an applescript to do the following >> >> 1) import bibtex from a webpage in safari >> 2) generate a cite key according to the auto generation rule set in preferences >> >> Below is the part of applescript >> >> tell document 1 of application "BibDesk" >>       activate >>       set myPub to first item of (import from theBibTeXString) >>       set selection to {myPub} >>       tell application "System Events" to keystroke "k" using {command down} >> end tell >> >> However, I ran into the following problem.  I use keyword groups.  If >> BibDesk is already running and one of the keyword groups is selected, >> then the the last line won't run because, unless the imported entry >> has the same keyword, it won't be selected.  I checked the BibDesk >> dictionary in Applescript Editor.  It seems that I can first select >> the "library group" right after "activate".  But I cannot figure out >> the proper way to do it.  Any help is appreciated. >> >> D. > > Using system events to simulate key strokes is something of a hack, you should not use that if it's not necessary. In this case you can simply generate and set the cite key in applescript. > > tell application "BibDesk" >        activate >        set theFormat to cite key format >        tell document 1 >                set thePubs to (import from theBibTeXString) >                if count of thePubs > 0 then >                        set myPub to (get first item of thePubs) >                        set theCiteKey to parse format theFormat for "Cite Key" from myPub >                        set cite key of myPub to theCiteKey >                end if >        end tell > end tell > > Christiaan > Hi Christiaan, Thanks a lot! I was wondering if there is a more elegant way to do the cite key generation. I have another question. I have a script saved in BibDesk's script folder to do some format cleaning after a record is imported, i.e., remove some unnecessary field added by the publisher. Right now what I'm doing is again to assign a menu shortcut to that script, then call it using the system events. Is there a way to call that script from the current applescript? Di 
 Re: [Bibdesk-users] Applescript Question From: Christiaan Hofman - 2011-11-23 10:26:07 On Nov 23, 2011, at 3:10, Di Xiao wrote: > I'm writing an applescript to do the following > > 1) import bibtex from a webpage in safari > 2) generate a cite key according to the auto generation rule set in preferences > > Below is the part of applescript > > tell document 1 of application "BibDesk" > activate > set myPub to first item of (import from theBibTeXString) > set selection to {myPub} > tell application "System Events" to keystroke "k" using {command down} > end tell > > However, I ran into the following problem. I use keyword groups. If > BibDesk is already running and one of the keyword groups is selected, > then the the last line won't run because, unless the imported entry > has the same keyword, it won't be selected. I checked the BibDesk > dictionary in Applescript Editor. It seems that I can first select > the "library group" right after "activate". But I cannot figure out > the proper way to do it. Any help is appreciated. > > D. Using system events to simulate key strokes is something of a hack, you should not use that if it's not necessary. In this case you can simply generate and set the cite key in applescript. tell application "BibDesk" activate set theFormat to cite key format tell document 1 set thePubs to (import from theBibTeXString) if count of thePubs > 0 then set myPub to (get first item of thePubs) set theCiteKey to parse format theFormat for "Cite Key" from myPub set cite key of myPub to theCiteKey end if end tell end tell Christiaan 
 Re: [Bibdesk-users] Applescript Question From: Fischlin Andreas - 2011-11-23 07:06:51 I see no need for a hack such as tell application "System Events" to keystroke "k" using {command down} if you check your BibDesk preference "Cite Key -> Cite Key Autogeneration -> Autogenerate the cite key wehn enough fields are supplied" Regards, Andreas On 23/11/2011, at 03:10 , Di Xiao wrote: I'm writing an applescript to do the following 1) import bibtex from a webpage in safari 2) generate a cite key according to the auto generation rule set in preferences Below is the part of applescript tell document 1 of application "BibDesk" activate set myPub to first item of (import from theBibTeXString) set selection to {myPub} tell application "System Events" to keystroke "k" using {command down} end tell However, I ran into the following problem. I use keyword groups. If BibDesk is already running and one of the keyword groups is selected, then the the last line won't run because, unless the imported entry has the same keyword, it won't be selected. I checked the BibDesk dictionary in Applescript Editor. It seems that I can first select the "library group" right after "activate". But I cannot figure out the proper way to do it. Any help is appreciated. D. ------------------------------------------------------------------------------ All the data continuously generated in your IT infrastructure contains a definitive record of customers, application performance, security threats, fraudulent activity, and more. Splunk takes this data and makes sense of it. IT sense. And common sense. http://p.sf.net/sfu/splunk-novd2d _______________________________________________ Bibdesk-users mailing list Bibdesk-users@... https://lists.sourceforge.net/lists/listinfo/bibdesk-users 
 [Bibdesk-users] Applescript Question From: Di Xiao - 2011-11-23 02:10:27 I'm writing an applescript to do the following 1) import bibtex from a webpage in safari 2) generate a cite key according to the auto generation rule set in preferences Below is the part of applescript tell document 1 of application "BibDesk" activate set myPub to first item of (import from theBibTeXString) set selection to {myPub} tell application "System Events" to keystroke "k" using {command down} end tell However, I ran into the following problem. I use keyword groups. If BibDesk is already running and one of the keyword groups is selected, then the the last line won't run because, unless the imported entry has the same keyword, it won't be selected. I checked the BibDesk dictionary in Applescript Editor. It seems that I can first select the "library group" right after "activate". But I cannot figure out the proper way to do it. Any help is appreciated. D. 
 Re: [Bibdesk-users] Crossref with biblatex From: Christiaan Hofman - 2011-11-19 13:23:52 On Nov 19, 2011, at 13:40, Niklas Hartmann - listserv address wrote: > Dear all, > > I am managing my references with bibdesk, but I am also using biblatex's features quite extensively. Thus, I am looking for a way to adjust the feature controlled by the checkbox 'Duplicate "Title" field to "Booktitle"' in the 'Crossref' panel of bibdesk's preferences. I would like the same checkbox to also trigger "Subtitle" and "Titleaddon" being copied to "Booksubtitle" and "Booktitleaddon", respectively. I am not sure whether this needs source code adjustments or whether this option is realised though an apple script or the like, in which case I'd probably find out how to do it myself if I know where to look for the script... > > Any help greatly appreciated! > > Cheers > Niklas You should do this through AppleScript. In hindsight that's also what should have been done with Booktitle. Christiaan 
 [Bibdesk-users] Crossref with biblatex From: Niklas Hartmann - listserv address - 2011-11-19 13:21:23 Dear all, I am managing my references with bibdesk, but I am also using biblatex's features quite extensively. Thus, I am looking for a way to adjust the feature controlled by the checkbox 'Duplicate "Title" field to "Booktitle"' in the 'Crossref' panel of bibdesk's preferences. I would like the same checkbox to also trigger "Subtitle" and "Titleaddon" being copied to "Booksubtitle" and "Booktitleaddon", respectively. I am not sure whether this needs source code adjustments or whether this option is realised though an apple script or the like, in which case I'd probably find out how to do it myself if I know where to look for the script... Any help greatly appreciated! Cheers Niklas 
 Re: [Bibdesk-users] Window menu (a request) From: Christiaan Hofman - 2011-11-19 10:26:10 On Nov 19, 2011, at 3:03, Adam R. Maxwell wrote: > > On Nov 18, 2011, at 17:49 , FZiegler wrote: > >> That said, unless you advise against compiling my own, you can still >> help me by pointing out the line(s) of code where the title gets set... > > In BDSKEditor.m, change > > - (NSString *)windowTitleForDocumentDisplayName:(NSString *)displayName{ > return [publication displayTitle]; > } > > to > > - (NSString *)windowTitleForDocumentDisplayName:(NSString *)displayName{ > return [publication citeKey]; > } > As well as the various places where -synchronizeWindowTitleWithDocumentName is called. Christiaan 
 Re: [Bibdesk-users] Local-Url field From: FZiegler - 2011-11-19 10:17:00 Christiaan Hofman wrote: >> >> I don't intend to ever have an entry with more than one linked file, >> btw. To me this contradicts the whole spirit of bibliography: if we have >> two different documents, then they should each have its own entry. >> > > It doesn't matter what you do. I am talking about what "linked files" returns: a list. Whether that's a list of one or more does not matter. So you should treat it as a list in your script. Yes, yes, I do understand this. The reason I wrote the above was further down, "I mention this because..." Francois 
 Re: [Bibdesk-users] Local-Url field From: Christiaan Hofman - 2011-11-19 10:11:04 On Nov 19, 2011, at 0:32, FZiegler wrote: > Thank you so much for taking the times to educate me; I've happily > adopted all your suggestions. > >> When you use a path in a shell script, you should always quote the path. In AppleScript you can conveniently do that by using "quoted form of thePath". >> >> Also, there can be multiple linked files. So getting "POSIX path of linked files" gives you a *list* of strings. So you should get something like "POSIX path of linked file 1". And you should first check whether there are linked files, and also whether the Local-Url isn't overwritten or unnecessarily set. > > Ah. At first I had tried the quoted form (inspired by the script of > Andreas who is careful to do that), but it hadn't worked, and I believe > your second remark above explains exactly why. With both changes in > place it works fine. > > I don't intend to ever have an entry with more than one linked file. > btw. To me this contradicts the whole spirit of bibliography: if we have > two different documents, then they should each have its own entry. > It doesn't matter what you do. I am talking about what "linked files" returns: a list. Whether that's a list of one or more does not matter. So you should treat it as a list in your script. Christiaan 
 Re: [Bibdesk-users] Local-Url field From: FZiegler - 2011-11-19 05:21:22 Adam R. Maxwell wrote: >> On the other hand, I *do* often have several entries linking to the same >> file, for practical reasons. (E.g., I've got volumes of collected works, >> or Encyklopädie, from archive.org. Each has its own entry under the >> editor's or collectee's name; but I often have entries for individual >> articles. These link again to the whole volume -- since it's there.) I >> mention this because it's easy to do by manually in the Local-Url field, >> whereas... how would I do it under the new filing system? > > Drag that file to the file pane for each entry it should be associated > with. If it's a collection, consider using crossrefs. But then, under which author/year (say) does the file end up *in the filesystem*? The last one to have spoken? I need this to be predictable by plain (cross-platform) bibtex reading any of the .bib entries. > Do you mean that you're sharing the .bib file with Linux/Windows users? > What software do they use to read the .bib file, and how does it deal with > file names? Storing it on a server shouldn't matter. The software used is just plain latex (and bibtex), running on the server. There, our book's source and my biblio.bib are sync'd using Mercurial, and the literature Archive is sync'd using Unison. It's also served (to us) by Apache. While working on a paper (or the book) we use a special .bst which includes hyperlinks to that Archived literature. The book's mercurial repo also contains a http://hatta-wiki.org for discussion. This also supports latex (mathjax) and I'd like to also be able to \cite references and get the hyperlinked, but that part is not implemented. > I guess I thought you needed 20 editor windows open because you were > referring back to others as you were writing notes. Why do you have > so many open at once? (just curious) In what I think is the common > case, you have 1--3 editors open at once, and the window title isn't > prone to confusion. The 20 was a somewhat extreme example to show how useless a title list could become, but I might typically have 10 -- why? because I'm copying and pasting and moving material and \cite-ing from one another. Since you express curiosity, I'm emailing you 3 random pages in hope they'll illustrate this better than long explanations could. The bottom line is that this is history-of-math related work, where having all sources at your fingertips is starting to allow for a new style of work. (You don't need to quote nearly as much, when you can just link the original pages from gallica.fr, archive.org, etc.) Francois 
 Re: [Bibdesk-users] Window menu (a request) From: Adam R. Maxwell - 2011-11-19 04:32:45 On Nov 18, 2011, at 20:17 , FZiegler wrote: > Where I need to switch Get Info windows is when I *write* them, which > (for me) is most of the time spent using BibDesk. I guess I thought you needed 20 editor windows open because you were referring back to others as you were writing notes. Why do you have so many open at once? (just curious) In what I think is the common case, you have 1--3 editors open at once, and the window title isn't prone to confusion. -- Adam 
 Re: [Bibdesk-users] Window menu (a request) From: FZiegler - 2011-11-19 04:17:41 Adam R. Maxwell wrote: > > In BDSKEditor.m, change > > - (NSString *)windowTitleForDocumentDisplayName:(NSString *)displayName{ > return [publication displayTitle]; > } > > to > > - (NSString *)windowTitleForDocumentDisplayName:(NSString *)displayName{ > return [publication citeKey]; > } Thank you!! This worked like a charm. (If I may: I knew what to expect, from having lurked on this and Skim's list before, yet I keep being amazed by the unparalleled level of support you and Christiaan provide.) > Having said that, I seldom use the window menu to find editor windows. > In your situation, I'd use Exposé or select the items in the main list > and read their annotations in the main window's lower pane. I readily admit that my workflow is nonstandard... For me Exposé would not make a difference, as all Get Info windows look alike and are only distinguished by their (now useful) title. My annotations are full of latex code, so I read them in typesets I make with an appropriate bst. Where I need to switch Get Info windows is when I *write* them, which (for me) is most of the time spent using BibDesk. Your case does not contradict my hunch that, *of the people who actually read Window Menu items*, a majority might prefer the citeKey there. But of course I won't press the issue, now that I've been satisfied anyway. Francois `

Showing results of 79

1 2 3 4 > >> (Page 1 of 4)