From: Matt Price <moptop99@gmail.com>
To: Matt Price <moptop99@gmail.com>, Org Mode <emacs-orgmode@gnu.org>
Subject: Re: contributing to work on citations
Date: Thu, 5 Nov 2015 20:41:02 -0500 [thread overview]
Message-ID: <CAN_Dec-P6RzHkZgjMuBcVehtBgauJRfyd2iQq7mxj=6ZGQg2dg@mail.gmail.com> (raw)
In-Reply-To: <87si4lvlm8.fsf@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1901 bytes --]
On Wed, Nov 4, 2015 at 10:18 AM, Aaron Ecay <aaronecay@gmail.com> wrote:
> >
> > 3. Handling of citation links in the various export engines
> > Functions must be written to handle citations in, at minimum, latex,
> html,
> > and org
> >
> > 4. Interface with backends
> > Org should be able to talk to bibtex and zotero databases, at least (and
> > maybe more).
>
> The code I wrote should have enough hooks to enable this. But I haven’t
> looked at zotero at all. If zotero support is important to you, you
> could investigate the “lookup types” in the citation code I wrote, see
> if they are adequate, and try to use them to implement zotero lookup.
> From the docstring:
>
> "Types of citation lookup backends.
>
> Alist from type to list of:
>
> - Function called at the beginning of export, with the rest of
> the keyword line after #+BIBDB: type, and the info plist.
> Should cache whatever it needs in the info plist.
>
> - Function to lookup a citation. Called with the key and the
> info plist. Will be memoized by
> `org-export-cite--lookup' (TODO). Should return an alist of
> keys and values about the citation (author, year, title, etc.)
>
> - A boolean; non-nil = this lookup type is remote. All local
> lookups will be tried before any remote one is.
> TODO: not yet implemented"
>
Hey, Aaron,
Am I right that I need to check out your wip-cite-awe branch from ~8 months
ago? Would it make sense to try to merge recent changes on master into that
branch first?
Anyway, I figure I will try to modify zotxt-emacs so it provides these
functions and generates conformant cite: links. That seems the easiest
solution, and maybe Erik will give me some help once I've made some initial
progress. Meanwhile I will try to learn enough about javascript to get
started on the citeproc-js ocmmand-line tool. thx,
matt
[-- Attachment #2: Type: text/html, Size: 2424 bytes --]
next prev parent reply other threads:[~2015-11-06 1:41 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-30 20:17 contributing to work on citations Matt Price
2015-11-04 15:18 ` Aaron Ecay
2015-11-04 19:37 ` Will Monroe
2015-11-04 19:49 ` William Denton
2015-11-04 20:20 ` John Wiegley
2015-11-04 22:25 ` Matt Price
2015-11-06 1:41 ` Matt Price [this message]
2015-11-06 13:10 ` Aaron Ecay
2015-11-06 17:14 ` Matt Price
2015-11-22 20:32 ` Richard Lawrence
2015-11-08 11:17 ` Rasmus
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='CAN_Dec-P6RzHkZgjMuBcVehtBgauJRfyd2iQq7mxj=6ZGQg2dg@mail.gmail.com' \
--to=moptop99@gmail.com \
--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).