From: Rasmus <rasmus@gmx.us>
To: emacs-orgmode@gnu.org
Subject: Re: Citation processing via Zotero + zotxt
Date: Fri, 04 Dec 2015 01:03:27 +0100 [thread overview]
Message-ID: <87mvtrqdv4.fsf@gmx.us> (raw)
In-Reply-To: m2y4dbgldp.fsf@andrew.cmu.edu
John Kitchin <jkitchin@andrew.cmu.edu> writes:
> I clearly had some super important academic work to do today, so instead
> I played around with citations ;)
>
> I am not yet convinced a citation processor will get us where we want
> because of the complexity of the external dependencies, and the
> potential/probable need for us to define new CSL files for different
> backends, or at a minimum for org-formatted citations and
> bibliographies. Hacking bst files is no fun, and it doesn't look like
> CSL files are much better! Plus you have to find them and install them
> somehow.
>
> I wanted to get a sense for how well I could manipulate citation and
> bibliography format from org-ref with a bibtex database. The answer is
> it is pretty easy, not perfect, but pretty good, and could certainly be
> made better with dedicated effort. You can see how here, and some
> discussion about its limitations:
>
> http://kitchingroup.cheme.cmu.edu/blog/2015/12/03/Exporting-numbered-citations-in-html-with-unsorted-numbered-bibliography/
>
> I am pointing this out because I think the approach I used could allow
> for plugins for different database backends, different ways to get the
> replacements, etc... you could substitute org-ref links for the citation
> syntax at some point with no real loss of generality. org-ref could
> insert the new syntax as soon as it is available in a main org branch.
> Some code will have to be rewritten to get the key under point, but that
> probably won't be too hard.
>
> We could provide a solution like this for some backends, using bibtex as
> the database, for pretty immediate use. Then other more advanced
> solutions could come along that would likely be superior in output
> quality if they use real citation processors, but only if there are CSLs
> for different backends (if I understand how they work). These would be
> optional, and only needed if higher quality and flexibility in output
> was required.
>
> What do you think?
My guess is that it is orders of magnitudes harder with author (year) and
footnotes and whatnot. But bibtex.el helps in some regards (indeed in an
ancestor to this thread we discussed whether bibtex.el + reftex.el could
be used). Then comes the formatting and sorting of the bibliography, also
when using different languages (Marcin talks about this) or types of
publications (bibtex.el lists 27 when you switch the dialect to
biblatex)...
As a small example comes out of your example which has mistakes such as
"17()".
The fact that the documentation of biblatex-chicago (a biblatex *style*)
is 149 pages might also serve as a warning.
Note, I use a similar system myself when exporting citations outside of
latex (lookup stuff from bibtex and cross-fingers), but fitted to
author-year. It’s certainly doable when you know your fixed needs, but it
is harder to convince yourself it’s a good general solution.
It would be nice if you could prove me wrong.
Rasmus
--
What will be next?
next prev parent reply other threads:[~2015-12-04 0:03 UTC|newest]
Thread overview: 37+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-28 20:16 Citation processing via Zotero + zotxt Richard Lawrence
2015-11-30 8:12 ` Martin Yrjölä
2015-12-01 0:32 ` John Kitchin
2015-12-01 2:59 ` Richard Lawrence
2015-12-03 0:27 ` Matt Lundin
2015-12-03 1:41 ` Christian Wittern
2015-12-03 14:25 ` Matt Lundin
2015-12-03 4:32 ` Richard Lawrence
2015-12-03 15:27 ` Matt Lundin
2015-12-03 17:56 ` Richard Lawrence
2015-12-03 19:14 ` Thomas S. Dye
2015-12-03 22:05 ` Rasmus
2015-12-03 20:45 ` Matt Lundin
2015-12-03 21:04 ` Matt Lundin
2015-12-03 23:31 ` John Kitchin
2015-12-04 0:03 ` Rasmus [this message]
2015-12-04 1:49 ` John Kitchin
2015-12-05 21:18 ` Matt Lundin
2015-12-05 22:23 ` John Kitchin
2015-12-04 2:06 ` Matt Lundin
2015-12-04 11:22 ` John Kitchin
2015-12-04 14:13 ` Matt Lundin
2015-12-05 1:23 ` John Kitchin
2015-12-04 9:20 ` Eric S Fraga
2015-12-01 9:34 ` Ramon Diaz-Uriarte
2015-11-30 11:35 ` Eric S Fraga
2015-11-30 12:02 ` Ramon Diaz-Uriarte
[not found] ` <CAN_Dec-JCmwQ2bc=U93rRaPMYyXOiN_PRbtyya9x396r3qqMrg@mail.gmail.com>
2015-12-01 12:12 ` Fwd: " Matt Price
2015-12-01 15:28 ` Eric S Fraga
2015-12-01 15:51 ` Richard Lawrence
2015-12-01 19:20 ` Matt Price
2015-12-01 21:34 ` Eric S Fraga
2015-12-01 21:51 ` Matt Lundin
2015-12-02 15:21 ` Richard Lawrence
2015-12-01 14:36 ` Rasmus
2015-12-01 19:37 ` Matt Price
2015-12-02 15:58 ` Richard Lawrence
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=87mvtrqdv4.fsf@gmx.us \
--to=rasmus@gmx.us \
--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
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
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).