From: tsd@tsdye.com (Thomas S. Dye)
To: Rasmus <rasmus@gmx.us>
Cc: emacs-orgmode@gnu.org
Subject: Re: org-exp-bibtex missing in git?
Date: Fri, 08 Mar 2013 07:36:44 -1000 [thread overview]
Message-ID: <m1k3phbxoz.fsf@tsdye.com> (raw)
In-Reply-To: <8738w6jl6n.fsf@pank.eu> (rasmus@gmx.us's message of "Fri, 08 Mar 2013 10:27:28 +0100")
Aloha Rasmus,
Rasmus <rasmus@gmx.us> writes:
> tsd@tsdye.com (Thomas S. Dye) writes:
>
>
> Indeed, but perhaps there is a better possible syntax. With Reftex
> the the link-way is OK, but I still think that we should think about
> whether there is a "Better Way"ᵀᴹ if Org was to add it officially.
>
> There are some recent projects adding citation support for higher
> level languages such as:
>
> 1. https://github.com/cboettig/knitcitations
> 2. http://wordpress.org/extend/plugins/kcite/
Thanks for these pointers--very interesting. It is certainly seductive
to think about pointing to a location such as a DOI and coming away with
a useful citation.
In my experience, there is typically a fairly wide gap between the
publisher's citation style and the information available digitally, even
in standard MARC records from a library. I bridge this gap by hand with
lots of changes to a Bib(La)TeX entry taken off the Web. It would
certainly be a feat if this could be done automatically.
Part of the problem is publisher's citation styles. BibLaTeX tries to
canvas that field, and the result is pretty complex. The data needs for
a fully catholic BibLaTeX database are impractically large.
I'm not trying to throw cold water on a prospective project and would be
an avid user of a working "Better Way."
All the best,
Tom
--
T.S. Dye & Colleagues, Archaeologists
735 Bishop St, Suite 315, Honolulu, HI 96813
Tel: 808-529-0866, Fax: 808-529-0884
http://www.tsdye.com
next prev parent reply other threads:[~2013-03-08 17:37 UTC|newest]
Thread overview: 45+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-03 7:06 org-exp-bibtex missing in git? Vikas Rawal
2013-03-03 10:39 ` François Allisson
2013-03-03 17:11 ` Bastien
2013-03-03 17:19 ` Nicolas Goaziou
2013-03-03 20:00 ` Andreas Leha
2013-03-03 20:42 ` Nicolas Goaziou
2013-03-04 9:29 ` Eric S Fraga
2013-03-06 13:38 ` Andreas Leha
2013-03-06 18:25 ` Bastien
2013-03-06 18:39 ` Nicolas Goaziou
2013-03-06 21:16 ` Andreas Leha
2013-03-06 22:55 ` Bastien
2013-03-06 23:37 ` Andreas Leha
2013-03-07 8:32 ` Bastien
2013-03-07 8:44 ` Andreas Leha
2013-03-07 5:38 ` aaronecay
2013-03-07 8:54 ` Eric S Fraga
2013-03-07 10:21 ` Bastien
2013-03-07 11:04 ` Aaron Ecay
2013-03-07 11:16 ` Bastien
2013-03-07 12:03 ` Aaron Ecay
2013-03-07 13:13 ` Nicolas Goaziou
2013-03-07 15:28 ` Bastien
2013-03-07 17:39 ` Achim Gratz
2013-03-07 22:06 ` Bastien
2013-03-07 22:46 ` Achim Gratz
2013-03-07 23:37 ` Rasmus Pank Roulund
2013-03-07 23:43 ` Rasmus
2013-03-08 0:10 ` Thomas S. Dye
2013-03-08 9:27 ` Rasmus
2013-03-08 17:36 ` Thomas S. Dye [this message]
2013-03-08 19:32 ` aaronecay
2013-03-08 19:40 ` Rasmus
2013-03-08 19:29 ` aaronecay
2013-03-09 9:28 ` Bastien
2013-03-19 5:02 ` Aaron Ecay
2013-04-18 10:58 ` Bastien
2013-03-09 15:15 ` Nicolas Goaziou
2013-03-09 16:04 ` Jambunathan K
2013-03-09 16:12 ` Jambunathan K
2013-03-09 17:08 ` Thomas S. Dye
2013-03-07 10:04 ` Jambunathan K
2013-03-11 13:34 ` Andreas Leha
2013-03-04 4:40 ` Vikas Rawal
2013-03-04 13:55 ` Suvayu Ali
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=m1k3phbxoz.fsf@tsdye.com \
--to=tsd@tsdye.com \
--cc=emacs-orgmode@gnu.org \
--cc=rasmus@gmx.us \
/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).