From: mikadoZero <mikadozero@yandex.com>
To: Raghav Gururajan <rvgn@disroot.org>
Cc: guix-devel@gnu.org
Subject: Re: Zotero Packaging Request
Date: Sat, 30 Mar 2019 21:02:27 -0400 [thread overview]
Message-ID: <cuc1s2n6el8.fsf@yandex.com> (raw)
In-Reply-To: <87k1ggia56.fsf@ambrevar.xyz>
Raghav given Pierre's assessment I just wanted to suggest some potential
Zotero alternatives.
They would require using a document compiler like latex, groff or
pandoc. I do not know if the following have the feature set that you
are looking for. I have not used these myself but they would be what I
would look at using if I needed to create citations or bibliographies.
For use with latex:
* biber
* texlive-bibtex
For use with pandoc:
* ghc-pandoc-citeproc
For use with emacs/org:
* emacs-biblio
* emacs-org-ref
I do not know if `refer` is included in the `groff` packaged.
As an aside it is interesting to see that `emacs-zotxt` is packaged.
Pierre Neidhardt writes:
> Hi Raghav,
>
> I'm very sorry, I looked a little too fast (did I look at the wrong
> program? :p), and Zotero is actually the very opposite of what it
> thought, it's a hard one.
>
> It turns out that Zotero needs... NodeJS (!) and XULrunner (!!!).
>
> As long as Guix won't have a recursive importer for NodeJS, it will be
> a big hassle to package Zotero.
>
> Besides, isn't XULrunner deprecated?
>
> More details there:
> https://www.zotero.org/support/dev/client_coding/building_the_standalone_client
>
> Sorry, I'm out :(
next prev parent reply other threads:[~2019-03-31 1:03 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-25 18:55 Zotero Packaging Request Raghav Gururajan
2019-03-25 19:21 ` Pierre Neidhardt
2019-03-25 19:23 ` Raghav Gururajan
2019-03-27 14:31 ` Ludovic Courtès
2019-03-28 19:18 ` Raghav Gururajan
2019-03-30 16:45 ` Pierre Neidhardt
2019-03-31 1:02 ` mikadoZero [this message]
2019-03-31 6:09 ` Raghav Gururajan
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=cuc1s2n6el8.fsf@yandex.com \
--to=mikadozero@yandex.com \
--cc=guix-devel@gnu.org \
--cc=rvgn@disroot.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 external index
https://git.savannah.gnu.org/cgit/guix.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.