emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed

From: Stephen Eglen <S.J.Eglen@damtp.cam.ac.uk>
To: emacs-orgmode@gnu.org
Subject: Re: zotero (or mendeley) integration with org
Date: Thu, 31 Mar 2011 12:39:26 +0100	[thread overview]
Message-ID: <t5xaagbiknl.fsf@rgc.damtp.cam.ac.uk> (raw)
In-Reply-To: 8739m6oyqf.fsf@fastmail.fm


> Agreed. Google Scholar citations need very close proofreading, as they
> can be erroneous or poorly formatted. 

Thanks Matt - I'd agree with this, having seen oddities from google
scholar.  I emailed them ages ago about one problem (formatting of
initials in author names), but never heard back... it is a pity that
there is no mechanism for tidying up their references, as it seems to be
the best thing out there that covers all the fields.

Having said that, if google scholar can save me some typing, I'll
happilyuse it as a starting point for a bibtex entry.  I've just started
using pdfmeat -- this is nice, as given a pdf, it outputs the
corresponding bibtex entry from google scholar.  Probably works similar
to the way zotero does it, but can be used straight from the command
line:

  http://code.google.com/p/pdfmeat/

(Warning: I couldn't get one of the python dependencies, unidecode, to
work on mac, but it does work on ubuntu for me.)

> accessed by bibsnarf are limited to math and sciences. Since I use
> biblatex together with the Chicago Manual of Style, any bibtex entry I
> clip has to be edited and tweaked substantially. (Indeed, manual editing
> is unavoidable when using biblatex.)

If its not too tangential, why do you use biblatex -- is it the future
for bibtex?

Thanks for summarising your workflow, very helpful.

Stephen

next prev parent reply	other threads:[~2011-03-31 11:39 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-03-26 15:47 zotero (or mendeley) integration with org Stephen Eglen
2011-03-26 21:04 ` Cian
2011-03-26 21:06 ` Ramon Diaz-Uriarte
2011-03-28  9:14   ` Stephen Eglen
2011-03-28 14:07     ` brian powell
2011-03-28 17:06 ` Erik Hetzner
2011-03-29  3:32 ` Matt Lundin
2011-03-29  7:21   ` William Gardella
2011-03-29 10:55     ` Rasmus
2011-03-29 11:42       ` William Gardella
2011-03-29 13:14       ` Matt Lundin
2011-03-31 11:39         ` Stephen Eglen [this message]
2011-03-31 20:13           ` Matt Lundin
2011-04-02  1:40             ` Alan E. Davis
2011-04-02 13:19               ` Matt Lundin
2011-04-02 13:37               ` Eric S Fraga
2011-04-02 14:13                 ` Alan E. Davis
2011-03-30  0:54   ` Alan E. Davis
2011-03-30  8:26     ` Cian
2011-03-30 14:34     ` Joost Kremers
  -- strict thread matches above, loose matches on Subject: below --
2011-03-27  3:12 Rustom Mody

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: https://www.orgmode.org/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=t5xaagbiknl.fsf@rgc.damtp.cam.ac.uk \
    --to=s.j.eglen@damtp.cam.ac.uk \
    --cc=emacs-orgmode@gnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link

Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).