Re: [Bibdesk-users] Safari recent downloads does not include Safari-saved PDFs in Leopard
Am 07.11.2007 um 11:05 schrieb Christiaan Hofman: Doesn't it appear in the Recent Downloads submenu? That should contain all items recently added to the default download location for Safari. No, it doesn't. Despite the fact the Downloads is the default download location set in my Safari preferences. Christiaan On 7 Nov 2007, at 10:18 AM, Bertolt Meyer wrote: Hi all, When I link to a downloaded PDF, I find the option Safari recent downloads... very useful. Unfortunately, PDF-Files that were opened in Safari and then saved to the Download-Folder with this greyish Save to Download-Folder icon that appears when one hovers with the mose over the opened PDF are not listed there. Any ideas how to change this? Wouldn't it be nice to add an option like Choose from Downloads folder... in that menu for Leopard? Cheers, Bertolt. PS. and thanks forpointing me to the web groups.. I hid the groups- sidebar, that why I didn't see it. DUH. -- Bertolt Meyer Oberassistent Psychologisches Institut Universität Zürich Sozialpsychologie Binzmühlestr. 14 / 1, Box 15 CH-8050 Zürich [EMAIL PROTECTED] tel: +41446357282 fax: +41446357279 mob: +41788966111 -- --- This SF.net email is sponsored by: Splunk Inc. Still grepping through log files to find problems? Stop. Now Search log events and configuration files using AJAX and a browser. Download your FREE copy of Splunk now http://get.splunk.com/ ___ Bibdesk-users mailing list Bibdesk-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bibdesk-users - This SF.net email is sponsored by: Splunk Inc. Still grepping through log files to find problems? Stop. Now Search log events and configuration files using AJAX and a browser. Download your FREE copy of Splunk now http://get.splunk.com/ ___ Bibdesk-users mailing list Bibdesk-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bibdesk-users -- Bertolt Meyer Oberassistent Psychologisches Institut Universität Zürich Sozialpsychologie Binzmühlestr. 14 / 1, Box 15 CH-8050 Zürich [EMAIL PROTECTED] tel: +41446357282 fax: +41446357279 mob: +41788966111 - This SF.net email is sponsored by: Splunk Inc. Still grepping through log files to find problems? Stop. Now Search log events and configuration files using AJAX and a browser. Download your FREE copy of Splunk now http://get.splunk.com/ ___ Bibdesk-users mailing list Bibdesk-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bibdesk-users
[Bibdesk-users] View bibtex record from the file content search view
Hello everyone, I was wondering wether is it possible to open the bibtex edition window of a particular reference from the File Content search view. This view already shows the records titles and double clicking one opens the associated PDF file, so the relation between those two is already known. It would be nice to have a bibtex record icon next to the pdf one and click this one to edit the bibtex record. A typical use case (well mine actually ;)) is that I often search for all files broadly related to a subject with the (great but necessarily slow) file content search, skim through the highest results and add keywords to the articles that are really well related to the subject in their bibtex records. Then the rest of my organization or searches relies on these keywords (so it is both fast and more accurate). I find this very efficient and the only black spot is that I have to note the names of all interesting records while I skim trough them and then get out of the file content view to add keyword to them. I guess other people could also find many use cases when directly opening the bibtex record would be useful also. Thanks in advance for your help. JiHO --- http://jo.irisson.free.fr/ - This SF.net email is sponsored by: Splunk Inc. Still grepping through log files to find problems? Stop. Now Search log events and configuration files using AJAX and a browser. Download your FREE copy of Splunk now http://get.splunk.com/ ___ Bibdesk-users mailing list Bibdesk-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bibdesk-users
Re: [Bibdesk-users] z39.50 Support
On Wednesday, November 07, 2007, at 04:01PM, Christiaan Hofman [EMAIL PROTECTED] wrote: It's not returning any format BibDesk can parse. Either it returns SUTRS, which is a another word for junk, or it returns a sort of hybrid Dublin Core XML, but not in a form we can recognize. I can't even get it to work with the test app; have you? I've tried various encoding, syntax, and database combinations without success. If the thing actually returns XML there's chance we can parse it, or use the yaz XML conversion. adam - This SF.net email is sponsored by: Splunk Inc. Still grepping through log files to find problems? Stop. Now Search log events and configuration files using AJAX and a browser. Download your FREE copy of Splunk now http://get.splunk.com/ ___ Bibdesk-users mailing list Bibdesk-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bibdesk-users
Re: [Bibdesk-users] z39.50 Support
Hi Andy, On Nov 7, 2007, at 5:55 PM, Andy Green wrote: So is this something that ADS should/could fix? Admittedly, I know very little about how this works, but it seems from the ADS record syntax, that they support several different return formats including SUTRS and some form of XML. Now if the XML they're returning is nonsensical, then maybe it's something ADS could fix. Or maybe they could add a syntax which more closely matches something the parser in BibDesk is used too. I'll be happy to contact them to see if they could help out from their end. Either of those options would be fine with me. We support MARC21, which is a standard format for z39.50, and MODS is semi-supported. Supporting Dublin Core XML isn't a problem, but it would really help to have valid XML to start with. I am /not/ an XML expert, so I just accept what my tools tell me. Running xmllint on an ADS entry (appended) in TextMate gives a list of errors: validity error: Validation failed: no DTD found ! recorddc:identifier2007arXiv0710.5836G/ dc:identifierdc:titleTidal synch ^ error: Namespace prefix dc on identifier is not defined recorddc:identifier2007arXiv0710.5836G/ dc:identifierdc:titleTidal synch recorddc:identifier2007arXiv0710.5836G/ dc:identifierdc:titleTidal synchronization of the subdwarf B binary PG 0101+039/dc:titledc:creatorGeier, S./ dc:creatordc:creatorNesslinger, S./dc:creatordc:creatorHeber, U./dc:creatordc:creatorRandall, S. K./ dc:creatordc:creatorEdelmann, H./dc:creatordc:creatorGreen, E. M./dc:creatordc:sourceeprint arXiv:0710.5836/ dc:sourcedc:date2007-10-01/dc:datedc:subjectAstrophysics/ dc:subjectdc:relationhttp://adsseeks.cfa.harvard.edu/abs/2007arXiv0710.5836G /dc:relationdc:descriptionTidally locked rotation is a frequently applied assumption that helps tomeasure masses of invisible compact companions in close binaries. Thecalculations of synchronization times are affected by largeuncertainties in particular for stars with radiative envelopes callingfor observational constraints. We aim at verifying tidally lockedrotation for the binary PG 0101+039, a subdwarf B star + white dwarfbinary from its tiny (0.025 %) light variations measured with the MOSTsatellite (Randall et al. 2005). Binary parameters were derived from themass function, apparent rotation and surface gravity of PG 0101+039assuming a canonical mass of 0.47 Mo and tidally locked rotation. Thelight curve was then synthesised and was found to match the observedamplitude well. We verified that the light variations are due toellipsoidal deformation and that tidal synchronization is establishedfor PG 0101+039. We conclude that this assumption should hold for allsdB binaries with orbital periods of less than half a day. Hence themasses can be derived from systems too faint to measure tiny lightvariations./ dc:description/record - This SF.net email is sponsored by: Splunk Inc. Still grepping through log files to find problems? Stop. Now Search log events and configuration files using AJAX and a browser. Download your FREE copy of Splunk now http://get.splunk.com/ ___ Bibdesk-users mailing list Bibdesk-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bibdesk-users
Re: [Bibdesk-users] z39.50 Support
On Wednesday, November 07, 2007, at 04:44PM, Adam R. Maxwell [EMAIL PROTECTED] wrote: On Wednesday, November 07, 2007, at 04:01PM, Christiaan Hofman [EMAIL PROTECTED] wrote: It's not returning any format BibDesk can parse. Either it returns SUTRS, which is a another word for junk, or it returns a sort of hybrid Dublin Core XML, but not in a form we can recognize. I can't even get it to work with the test app; have you? I've tried various encoding, syntax, and database combinations without success. If the thing actually returns XML there's chance we can parse it, or use the yaz XML conversion. Never mind...our list archives reveal that you can use au=someone to get results back. Anyway, it's returning is DC XML as Christiaan said, but it's only returning XML fragments, so our current DC XML parser would choke on it. If we strip the dc: namespace and tidy the XML, it's parseable, but we'd have no way to recognize the format. I wrote the current DC XML parser as a special case to deal with COPAC, but as far as I know it's no longer used since COPAC switched to MODS. Hence we could conceivably turn it into a special-case parser for ADS instead, and not really lose anything. It's annoying that the journal, volume, issue, and page range are all part of the source. -- adam - This SF.net email is sponsored by: Splunk Inc. Still grepping through log files to find problems? Stop. Now Search log events and configuration files using AJAX and a browser. Download your FREE copy of Splunk now http://get.splunk.com/ ___ Bibdesk-users mailing list Bibdesk-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bibdesk-users
Re: [Bibdesk-users] z39.50 Support
So is this something that ADS should/could fix? Admittedly, I know very little about how this works, but it seems from the ADS record syntax, that they support several different return formats including SUTRS and some form of XML. Now if the XML they're returning is nonsensical, then maybe it's something ADS could fix. Or maybe they could add a syntax which more closely matches something the parser in BibDesk is used too. I'll be happy to contact them to see if they could help out from their end. Cheers, Andy from the Server Config Outline: Record Syntax Supported ValueDescription Databases -- --- - 1.2.840.10003.5.101 SUTRS Records All 1.2.840.10003.5.109.3HTML RecordsAll 1.2.840.10003.5.109.10 XML Records All 1.2.840.10003.5.1000.147.1 ADS Tagged Records All On 8/11/2007, at 12:11 PM, Adam R. Maxwell wrote: On Wednesday, November 07, 2007, at 04:44PM, Adam R. Maxwell [EMAIL PROTECTED] wrote: On Wednesday, November 07, 2007, at 04:01PM, Christiaan Hofman [EMAIL PROTECTED] wrote: It's not returning any format BibDesk can parse. Either it returns SUTRS, which is a another word for junk, or it returns a sort of hybrid Dublin Core XML, but not in a form we can recognize. I can't even get it to work with the test app; have you? I've tried various encoding, syntax, and database combinations without success. If the thing actually returns XML there's chance we can parse it, or use the yaz XML conversion. Never mind...our list archives reveal that you can use au=someone to get results back. Anyway, it's returning is DC XML as Christiaan said, but it's only returning XML fragments, so our current DC XML parser would choke on it. If we strip the dc: namespace and tidy the XML, it's parseable, but we'd have no way to recognize the format. I wrote the current DC XML parser as a special case to deal with COPAC, but as far as I know it's no longer used since COPAC switched to MODS. Hence we could conceivably turn it into a special-case parser for ADS instead, and not really lose anything. It's annoying that the journal, volume, issue, and page range are all part of the source. -- adam -- --- This SF.net email is sponsored by: Splunk Inc. Still grepping through log files to find problems? Stop. Now Search log events and configuration files using AJAX and a browser. Download your FREE copy of Splunk now http://get.splunk.com/ ___ Bibdesk-users mailing list Bibdesk-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bibdesk-users - This SF.net email is sponsored by: Splunk Inc. Still grepping through log files to find problems? Stop. Now Search log events and configuration files using AJAX and a browser. Download your FREE copy of Splunk now http://get.splunk.com/ ___ Bibdesk-users mailing list Bibdesk-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bibdesk-users
Re: [Bibdesk-users] votes on 1.3.11?
Back to the root of this thread, I uploaded a replacement nightly build for 7 November that was compiled on Leopard and includes the QuickLook plugin. Let me know if there are any problems running it, particularly on Tiger. thanks, Adam - This SF.net email is sponsored by: Splunk Inc. Still grepping through log files to find problems? Stop. Now Search log events and configuration files using AJAX and a browser. Download your FREE copy of Splunk now http://get.splunk.com/ ___ Bibdesk-users mailing list Bibdesk-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bibdesk-users
Re: [Bibdesk-users] votes on 1.3.11?
On 08.11.2007, at 07:27, Adam R. Maxwell wrote: Back to the root of this thread, I uploaded a replacement nightly build for 7 November that was compiled on Leopard and includes the QuickLook plugin. Let me know if there are any problems running it, particularly on Tiger. After a first superficial test, I don't see any problems on Tiger. simon thanks, Adam -- --- This SF.net email is sponsored by: Splunk Inc. Still grepping through log files to find problems? Stop. Now Search log events and configuration files using AJAX and a browser. Download your FREE copy of Splunk now http://get.splunk.com/ ___ Bibdesk-users mailing list Bibdesk-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bibdesk-users -- Simon Spiegel Steinhaldenstr. 50 8002 Zürich Telephon: ++41 44 451 5334 Mobophon: ++41 76 459 60 39 http://www.simifilm.ch In a world getting more and more democratic, film directing is the last resort for dictators. Francis Ford Coppola - This SF.net email is sponsored by: Splunk Inc. Still grepping through log files to find problems? Stop. Now Search log events and configuration files using AJAX and a browser. Download your FREE copy of Splunk now http://get.splunk.com/ ___ Bibdesk-users mailing list Bibdesk-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bibdesk-users
