From: tsd@tsdye.com (Thomas S. Dye)
To: Vaidheeswaran C <vaidheeswaran.chinnaraju@gmail.com>
Cc: Richard Lawrence <richard.lawrence@berkeley.edu>, emacs-orgmode@gnu.org
Subject: Re: Zotero csl file that uses parenthetical style for citations
Date: Sat, 07 Mar 2015 07:25:23 -1000 [thread overview]
Message-ID: <m2k2ys1zzw.fsf@tsdye.com> (raw)
In-Reply-To: <54FA9D93.6010101@gmail.com> (Vaidheeswaran C.'s message of "Sat, 07 Mar 2015 12:11:23 +0530")
Aloha Vaidheeswaran C,
Vaidheeswaran C <vaidheeswaran.chinnaraju@gmail.com> writes:
>> So there is not really any such thing as an "in-text CSL style".
>> Rather, there are CSL styles that support both in-text and parenthetical
>> citations (which is most of them, I'd guess).
>
> Your guess is just a guess. You haven't looked at chicago-author-date
> style, have you?
>
> You can prove yourself right by
>
> (a) producing an "off-the-shelf" CSL file that uses BOTH "in-text" AND
> "parenthetical" citations.
>
> (b) producing a csl-based tool that ORG CAN INTERFACE WITH that
> produces "in-text" AND "parenthetical" styles.
Could you explain how CSL returns citation information through the
various interfaces that have been developed? Several have been
mentioned previously, e.g., citeproc-js, zotxt, etc.
Do you know of something in their design that would make it difficult
(or impossible) for the Org mode developers to produce, e.g., "Foo (2015)"
instead of "(Foo 2015)"?
I'm asking because the developers who contribute their effort to Org
mode are, IMHO, extremely talented and experienced programmers. IIUC,
they are also busy with other projects (some of which hopefully make
them some money!), so I think it would help them if you could document
the problem you've identified.
All the best,
Tom
--
Thomas S. Dye
http://www.tsdye.com
next prev parent reply other threads:[~2015-03-07 17:26 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-06 13:03 Zotero csl file that uses parenthetical style for citations Vaidheeswaran C
2015-03-06 13:18 ` Vaidheeswaran C
2015-03-06 13:29 ` Rasmus
2015-03-06 13:51 ` Vaidheeswaran C
2015-03-06 13:51 ` Vaidheeswaran C
2015-03-06 14:55 ` Rasmus
2015-03-06 15:27 ` Vaidheeswaran C
2015-03-06 13:27 ` Rasmus
2015-03-06 13:48 ` Vaidheeswaran C
2015-03-06 13:57 ` Rasmus
2015-03-06 15:21 ` Vaidheeswaran C
2015-03-06 18:21 ` Richard Lawrence
2015-03-07 6:41 ` Vaidheeswaran C
2015-03-07 16:48 ` Richard Lawrence
2015-03-07 18:22 ` Vaidheeswaran C
2015-03-07 17:25 ` Thomas S. Dye [this message]
2015-03-07 18:49 ` Vaidheeswaran C
2015-03-07 19:31 ` Thomas S. Dye
[not found] ` <54FB5E02.9080003@gmail.com>
2015-03-07 21:31 ` Thomas S. Dye
2015-03-08 2:59 ` Vaidheeswaran C
2015-03-08 3:59 ` Thomas S. Dye
2015-03-08 5:49 ` Vaidheeswaran C
2015-03-08 17:34 ` Thomas S. Dye
2015-03-09 5:21 ` Vaidheeswaran C
2015-03-09 6:34 ` Thomas S. Dye
2015-03-09 7:13 ` Vaidheeswaran C
2015-03-06 15:32 ` Vaidheeswaran C
2015-03-07 7:37 ` Vaidheeswaran C
2015-03-07 17:32 ` Thomas S. Dye
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=m2k2ys1zzw.fsf@tsdye.com \
--to=tsd@tsdye.com \
--cc=emacs-orgmode@gnu.org \
--cc=richard.lawrence@berkeley.edu \
--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).