From: Rasmus <rasmus@gmx.us>
To: emacs-orgmode@gnu.org
Subject: Re: Some projects
Date: Tue, 27 Oct 2015 14:51:25 +0100 [thread overview]
Message-ID: <87bnbkmnc2.fsf@gmx.us> (raw)
In-Reply-To: <871tcgzcoc.fsf@gmail.com> (Aaron Ecay's message of "Tue, 27 Oct 2015 13:03:15 +0000")
Aaron Ecay <aaronecay@gmail.com> writes:
> You have to write java to use it, which is a big negative (at least for
> me). Last time I think we concluded that the CLI interface it exposes
> is not adequate (though I actually started off trying to use it).
I see. That's probably the reason.
> There’s also the issue that it is just a bundling of citeproc-js with
> some java libraries (js interpreter, bibtex processor, ...), so someone
> who tries to extend it actually has to know both java and js.
Another drawback.
Pure JS (or perhaps Haskell?) is probably more accessible then. FWIW,
there's a couple of libraries that promise to read bibtex on npm, though I
haven’t tried any of those.
https://www.npmjs.com/search?q=bibtex
>> Do we WANT to depend on Pandoc? I would say "no". In my OS, where we
>> finally got a binary distribution of pandoc, the size of pandoc is still
>> 1600Mb! I don’t know if this is representative of other systems, though.
>> E.g. what is the size of pandoc+deps in Debian?
>
> 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.
Indeed. I guess this is what they use:
https://github.com/zotero/citeproc-node
It also looks rather complex...
Rasmus
--
9000!
next prev parent reply other threads:[~2015-10-27 13:51 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 [this message]
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
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=87bnbkmnc2.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).