From: Richard Lawrence <richard.lawrence@berkeley.edu>
To: vaidheeswaran.chinnaraju@gmail.com
Cc: emacs-orgmode@gnu.org
Subject: Re: Citation syntax and ODT
Date: Mon, 23 Feb 2015 15:25:39 -0800 [thread overview]
Message-ID: <87fv9wrz0s.fsf@berkeley.edu> (raw)
In-Reply-To: <54EB6D6F.7060005@gmail.com>
Vaidheeswaran C <vaidheeswaran.chinnaraju@gmail.com> writes:
>> But whatever style is chosen, I would still think that the fact that the
>> citation is in-text rather than parenthetical, and that it has a prefix
>> and suffix, should be represented in the output.
>
> 1. When you choose 'style' (Chicago etc.) wouldn't be one of in-text
> or parenthetical already chosen for you? Stated other way, is the
> choice between parenthetical or in-text document-wide or is it that
> one could intermix the two styles in the same document.
These could be intermixed in the same document. The document-level
style determines how each type ultimately looks, but the choice of style
is (mostly) independent of using parenthetical vs. in-text citations.
> 2. Citation processor like JabRef just takes a cite-key. It doesn't
> take a pre or post-note. So, the pre and post notes should be
> spliced in to the exported document by the elisp module that
> interfaces with the citation processor.
Right. That's what I'm thinking, anyway.
> If we are going to interface with a citation-processor, the best
> course of action would be to have someone first 'gauge' the
> capabilities provided by the citation processor and let that
> experience inform what Org should aspire to do.
Yes. Other people have more experience with this than me. But based on
what Pandoc is able to do, I am pretty confident that everything that
has been proposed could be handled by a CSL processor like citeproc-js
(or Pandoc's own). The possible exceptions are the common prefix and
common suffix in a multi-work citation, which I imagine would be easy
enough to add to the output of the citation processor.
Best,
Richard
next prev parent reply other threads:[~2015-02-23 23:26 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-02-22 7:22 Citation syntax and ODT Vaidheeswaran
2015-02-23 4:11 ` Richard Lawrence
2015-02-23 6:22 ` Vaidheeswaran
2015-02-23 7:10 ` Vaidheeswaran
2015-02-23 17:15 ` Richard Lawrence
2015-02-23 18:11 ` Vaidheeswaran C
2015-02-23 23:25 ` Richard Lawrence [this message]
2015-02-24 3:26 ` Alexis
2015-02-24 3:52 ` Vaidheeswaran C
2015-02-24 4:34 ` Vaidheeswaran C
2015-02-24 5:01 ` Thomas S. Dye
2015-02-24 5:31 ` Vaidheeswaran C
2015-02-24 6:07 ` Thomas S. Dye
2015-02-24 6:37 ` Vaidheeswaran C
2015-02-24 7:48 ` Thomas S. Dye
2015-02-24 17:19 ` Jorge A. Alfaro-Murillo
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=87fv9wrz0s.fsf@berkeley.edu \
--to=richard.lawrence@berkeley.edu \
--cc=emacs-orgmode@gnu.org \
--cc=vaidheeswaran.chinnaraju@gmail.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).