From: Rasmus <rasmus@gmx.us>
To: emacs-orgmode@gnu.org
Subject: Re: exporting zotxt or orgref links to HTML and ODF
Date: Tue, 27 Jan 2015 15:14:37 +0100 [thread overview]
Message-ID: <87bnlkqpiq.fsf@gmx.us> (raw)
In-Reply-To: CAN_Dec-Ayz6_QY9+oG-hGNnsEt9KQX6NOhw7bt210qPixA4geA@mail.gmail.com
Matt Price <moptop99@gmail.com> writes:
> On Tue, Jan 27, 2015 at 8:30 AM, Rasmus <rasmus@gmx.us> wrote:
>> #+begin_rant
>>
>> The current state is a mess and not portable. E.g. there's at least two
>> Zotero projects, there's John Kitchin's code, there's ox-bibtex.el (which
>> IMO is not suitable for complicated citation requirements), plus everyone
>> and their mother's have got custom citation links in their config via
>> custom org link types...
>>
>> /Proper/ citation support (not links) is, IMO, the last thing that is
>> missing for good academic publishing support.
>>
>> #+end_rant
>
> (I know about zotxt -- is there another zotero project?)
This is the other one I had in mind:
https://github.com/vspinu/zotelo
> (b) I could start to recommend it to colleagues, as I'm itching to do.
But the argument "it's easier/cleaner" seems to shatter when you get to
[[textcite:KEY]] compared to \textcite{KEY}... Even worse when you have
to have notes, e.g. \textcite[pre][post]{KEY}.
—Rasmus
--
The right to be left alone is a human right
next prev parent reply other threads:[~2015-01-27 14:15 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-01-26 16:29 exporting zotxt or orgref links to HTML and ODF Matt Price
[not found] ` <54C67E1A.8080706@law.lsu.edu>
2015-01-26 20:40 ` Matt Price
2015-01-26 21:53 ` Monroe, Will
2015-01-27 8:25 ` Eric S Fraga
2015-01-27 9:23 ` Christian Moe
2015-01-27 13:30 ` Rasmus
2015-01-27 13:51 ` Matt Price
2015-01-27 14:14 ` Rasmus [this message]
2015-01-27 18:17 ` John Kitchin
2015-01-27 15:24 ` Christian Moe
2015-01-27 17:24 ` Richard Lawrence
2015-01-27 17:50 ` Rasmus
2015-01-28 4:09 ` Richard Lawrence
2015-01-27 20:01 ` Christian Moe
2015-01-27 22:08 ` Rasmus
2015-01-27 22:15 ` John Kitchin
2015-01-28 2:10 ` Matt Price
2015-01-28 6:37 ` Erik Hetzner
2015-02-01 4:20 ` Erik Hetzner
2015-01-27 12:01 ` Vikas Rawal
2015-01-27 13:12 ` Matt Price
2015-01-27 14:28 ` Eric S Fraga
2015-01-27 13:31 ` Albert Krewinkel
[not found] ` <m2vbjsvay0.fsf@christianmoe.com>
[not found] ` <CAN_Dec9qBWWWgdX+wQhdgbthMg_ZOgbOMFoXFixSc4=74avMjw@mail.gmail.com>
2015-01-27 14:41 ` Christian Moe
[not found] <CAMfbzvA83eSWe79Ot=yX+_s_g33gpLnP-z+zQ52QFJm+iJTR+Q@mail.gmail.com>
2015-01-28 21:53 ` Matt Price
2015-01-28 23:01 ` John Kitchin
2015-01-29 1:34 ` Matt Price
2015-01-29 1:48 ` John Kitchin
[not found] ` <CAN_Dec80Su+5Nh5mqNxBXsLu_gm93aY77B=2Zrce-TJ1RPKCig@mail.gmail.com>
2015-01-29 13:06 ` John Kitchin
2015-01-29 13:11 ` Vikas Rawal
2015-01-29 13:24 ` John Kitchin
2015-01-29 13:39 ` Vikas Rawal
2015-01-29 13:09 ` John Kitchin
2015-01-29 2:26 ` Vikas Rawal
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=87bnlkqpiq.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).