emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Matt Price <moptop99@gmail.com>
To: Rasmus <rasmus@gmx.us>, Org Mode <emacs-orgmode@gnu.org>
Subject: Re: Some projects
Date: Tue, 27 Oct 2015 21:05:57 -0400	[thread overview]
Message-ID: <CAN_Dec_Zj8adeYUBpqp-EFhk1m6nrpaGRh-S_mMuOY8JUHqPJA@mail.gmail.com> (raw)
In-Reply-To: <871tcgzcoc.fsf@gmail.com>

[-- Attachment #1: Type: text/plain, Size: 866 bytes --]

On Tue, Oct 27, 2015 at 9:03 AM, Aaron Ecay <aaronecay@gmail.com> wrote:

> Hi Rasmus,
>
> 2015ko urriak 27an, Rasmus-ek idatzi zuen:
>
> [...]
>
> >
>
> It’s unfortunate, but pandoc has the most easily adaptable CSL
> implementation for our use case, as far as I can see.  The other
> contender is Zotero (in JS, possibly with XUL-specific bits).  It would
> be good if somebody looked at what it would take for us to use Zotero’s
> implementation, just as Richard did for Pandoc.
>

You know about zotxt, right? https://github.com/egh/zotxt-emacs  It is
probably the best starting point, but is currently a little cumbersome to
set up, with several moving parts (zoterto, zotero zotxt extension,
zotxt-emacs library).  And in the end it also sort of makes use of pandoc,
too (https://github.com/egh/zotxt-emacs#for-pandoc-markdown-files)

[-- Attachment #2: Type: text/html, Size: 1427 bytes --]

  parent reply	other threads:[~2015-10-28  1:06 UTC|newest]

Thread overview: 62+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-10-25 13:08 Some projects Nicolas Goaziou
2015-10-25 14:43 ` Marcin Borkowski
2015-10-25 16:11   ` Nicolas Goaziou
2015-10-25 15:45 ` Eric S Fraga
2015-10-25 16:16   ` Nicolas Goaziou
2015-10-25 16:18   ` Marcin Borkowski
2015-10-25 16:37     ` Nicolas Goaziou
2015-10-25 18:13       ` Marcin Borkowski
2015-10-25 18:24         ` Nicolas Goaziou
2015-10-25 17:57 ` Thomas S. Dye
2015-10-25 18:00   ` Fabrice Popineau
2015-10-25 18:12     ` Nicolas Goaziou
2015-10-25 18:22       ` Eric S Fraga
2015-10-25 19:12         ` Marcin Borkowski
2015-10-25 19:11       ` Marcin Borkowski
2015-10-25 21:18         ` Anders Johansson
2015-10-25 21:29           ` Anders Johansson
2015-10-25 19:33       ` Thomas S. Dye
2015-10-25 20:00         ` Nicolas Goaziou
2015-10-25 20:17           ` Thomas S. Dye
2015-10-25 20:03         ` Nicolas Goaziou
2015-10-25 19:02 ` Rasmus
2015-10-25 19:20   ` Marcin Borkowski
2015-10-26  2:23   ` Matt Price
2015-10-25 20:24 ` Samuel Wales
2015-10-25 20:25   ` Samuel Wales
2015-10-25 23:03 ` Aaron Ecay
2015-10-26  8:13   ` Marcin Borkowski
2015-10-26  9:20     ` Rasmus
2015-10-26 16:39   ` Richard Lawrence
2015-10-26 18:17     ` Nicolas Goaziou
2015-10-26 22:23       ` Richard Lawrence
2015-10-27  0:03         ` Matt Price
2015-10-27 12:01     ` Aaron Ecay
2015-10-27 12:34       ` Rasmus
2015-10-27 13:03         ` Aaron Ecay
2015-10-27 13:51           ` Rasmus
2015-10-28  1:05             ` Matt Price
2015-10-28  3:28               ` Aldric Giacomoni
2015-10-28  3:31               ` Matt Lundin
2015-10-28 14:36                 ` Matt Price
2015-10-28 15:31                   ` Matt Price
2015-10-28  1:05           ` Matt Price [this message]
2015-10-27 13:19         ` Rainer M Krug
2015-10-27 13:42           ` Rasmus
2015-10-27 14:49             ` Ista Zahn
2015-10-27 15:09               ` Rasmus Pank Roulund
2015-10-27 15:25                 ` Ista Zahn
2015-10-27 15:36                 ` Rainer M Krug
2015-10-28  2:52                 ` Matt Lundin
2015-10-27 13:22         ` Richard Lawrence
2015-10-28  1:57   ` Matt Lundin
2015-10-28  8:56     ` Rasmus
2015-10-28  9:07       ` Rasmus
2015-10-26 17:20 ` Eric Abrahamsen
2015-10-27  8:30   ` Nicolas Goaziou
2015-10-27 18:53     ` Eric Abrahamsen
2015-10-27 19:23       ` Rasmus
2015-10-27 20:28         ` Eric Abrahamsen
2015-10-27 20:01       ` Marcin Borkowski
2015-10-27 21:53       ` Nicolas Goaziou
2015-10-26 18:20 ` Kaushal Modi

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_Zj8adeYUBpqp-EFhk1m6nrpaGRh-S_mMuOY8JUHqPJA@mail.gmail.com \
    --to=moptop99@gmail.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).