From: Matt Price <moptop99@gmail.com>
To: Christian Moe <mail@christianmoe.com>, Org Mode <emacs-orgmode@gnu.org>
Subject: Re: exporting zotxt or orgref links to HTML and ODF
Date: Tue, 27 Jan 2015 21:10:43 -0500 [thread overview]
Message-ID: <CAN_Dec_Vmwdh0oedBn39xFLS5Gkg3ba3g1iuOaD583iupoomvA@mail.gmail.com> (raw)
In-Reply-To: <m2iofsq9gp.fsf@christianmoe.com>
[-- Attachment #1: Type: text/plain, Size: 3977 bytes --]
I am very eager to see this work of yours, Christian. I also would very
much like to find a way to have a single, well-supported citation framework
in org -- I certainly think John's work looks incredible, and zotxt is very
powerful, but it would be fantastic if one could just choose a
bibliographic backend and export seamlessly to any supported format. It
would be a big step forward. I guess I don't quite see, yet, what has to
happen for the work of various contributors to be consolidated; clearly
Erik, You, and John have worked in overlapping and distinct directions, but
I would be veyr enthusiastic about helping a unified approach emerge,
espeically one that supported Zotero.
Thanks everyone,
Matt
On Tue, Jan 27, 2015 at 3:01 PM, Christian Moe <mail@christianmoe.com>
wrote:
>
> Richard Lawrence writes:
>
> > It looks to me like Pandoc has a quite general solution, and it also
> > looks like Org could use Pandoc's citation syntax as-is. I would
> > suggest borrowing this syntax as a starting point for building citation
> > support into Org.
>
> It's been years since I looked at Pandoc, and I think they've added some
> functionality since then. Prefix, locator, suffix, and multiple
> references in one human-readable citation: Great! And /much/ nicer to
> look at than latex \cite commands with their frankly bizarre placement
> of locators etc.
>
> > Blah blah [see @doe99, pp. 33-35; also @smith04, ch. 1].
>
> In my current homebrewn solution for Zotero, I have tried to do
> something similarly readable using Org link syntax (sorry, Rasmus!) with
> the database entry ID as link target, and parsing the description part
> for prefix/author-date/locator/suffix, but with a slightly different
> syntax than Pandoc uses. In my solution the above would be:
>
> Blah blah [[zotero:0_A43F89;0_E25CB3][(see: Doe 1999: p.33-35; also:
> Smith 2004: ch. 1)]].
>
> > A minus sign (-) before the @ will suppress mention of the author in the
> > citation. This can be useful when the author is already mentioned in the
> > text:
> >
> > Smith says blah [-@smith04].
>
> In my current Zotero solution:
>
> Smith says blah [[zotero:0_E25CB3][(2004)]].
>
> > Does anyone have citation needs that this syntax doesn't cover?
>
> It's great, as long as your database uses mnemonic citekeys like
> doe99. Zotero doesn't, but uses keys that are meaningless to humans,
> like 0_A43F89. Unfortunately [see @0_A43F89, p. 5] wouldn't look nearly
> as nice as [see @doe99, p.5], and it wouldn't help you remember what you
> referenced.
>
> I think the typical workflow combining Zotero with Pandoc is to export a
> BibTex file from Zotero and reference the BibTex citekeys from
> there. I could live with that much of the time.
>
> But that workflow doesn't help with something I often want to do, which
> is to export to ODT and have 'live' Zotero citations that I can continue
> to work with in LibreOffice.
>
> > Using this syntax would also have the advantage that Pandoc can already
> > parse it, which would reduce friction for Org users who convert their
> > documents with Pandoc (and Pandoc users who need to deal with Org
> > inputs). Since this seems like a significant contingent of Org users,
> > that's something to consider.
>
> That's a good point. OTOH, don't Org users convert their documents with
> Pandoc mostly because cross-backend citation support is lacking?
>
> > The bigger question is whether, in addition to a citation *syntax*, it
> > would be a lot of work to add support for the various citation database
> > formats, as well as the various output styles, and which ones to
> > support.
>
> Possibly more work if it's worth if we adopt Pandoc syntax,
> since Pandoc-citeproc seems to handle nearly everything that is based on
> plain text.
>
> To truly support citations natively, we'd essentially have to implement
> something like citeproc in elisp. Not that I haven't been thinking about
> that...
>
> Yours,
> Christian
>
>
>
>
>
>
>
[-- Attachment #2: Type: text/html, Size: 4837 bytes --]
next prev parent reply other threads:[~2015-01-28 2:10 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
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 [this message]
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=CAN_Dec_Vmwdh0oedBn39xFLS5Gkg3ba3g1iuOaD583iupoomvA@mail.gmail.com \
--to=moptop99@gmail.com \
--cc=emacs-orgmode@gnu.org \
--cc=mail@christianmoe.com \
/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).