From: Jambunathan K <kjambunathan@gmail.com>
To: Rasmus <rasmus@gmx.us>
Cc: emacs-orgmode@gnu.org
Subject: Re: Standardize #+BIBLIOGRAPHY line
Date: Mon, 22 Jul 2013 22:31:31 +0530 [thread overview]
Message-ID: <87d2qaplzo.fsf@gmail.com> (raw)
In-Reply-To: <87hafmwuhs.fsf@gmx.us> (rasmus@gmx.us's message of "Mon, 22 Jul 2013 16:15:59 +0200")
> As expressed elsewhere I think
>
> [cite:key :pre xxx :post yyy :mycrazykey zzz]
>
> is the most desirable syntax.
Where would the pre, post text would go.
Will it go as part of "in text" or will it go in to References list or
both. For command line based processing, I see foresee issues with:
1. Multiple keys.
2. Stuff like "Ibid."
3. Sort order of keys.
4. Numbering of entries.
> The system should exhibit some flexibility supporting e.g. notes,
> parencite (prenote, key, year, postnote) and textcite key (prenote,
> year, postnote). But there could be others. E.g. someone mentioned
> using DOIs etc.
> I'd be willing to put in work on ox-bibliography, although I don't
> know if my 'skillz' suffice.
This is just escaping :-). You already have some ideas on "what"s and
"how"s. You put "what" in "what" and "how" in "how".
IME, Confusion, lethargy or escapism starts when "what" gets mixed with
"how". "Collection" can happen now. "Processing" can happen later.
next prev parent reply other threads:[~2013-07-22 17:00 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-07-22 7:25 Standardize #+BIBLIOGRAPHY line Jambunathan K
2013-07-22 9:03 ` Nicolas Goaziou
2013-07-22 13:16 ` Jambunathan K
2013-07-22 13:19 ` Jambunathan K
2013-07-22 13:31 ` Nicolas Goaziou
2013-07-22 13:47 ` Jambunathan K
2013-07-22 13:58 ` Nicolas Goaziou
2013-07-22 16:09 ` Jambunathan K
2013-07-22 19:33 ` Jambunathan K
2013-07-22 14:15 ` Rasmus
2013-07-22 16:29 ` Jambunathan K
2013-07-22 21:51 ` Rasmus
2013-07-25 8:47 ` Jambunathan K
2013-07-22 17:01 ` Jambunathan K [this message]
2013-07-22 19:34 ` Jambunathan K
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=87d2qaplzo.fsf@gmail.com \
--to=kjambunathan@gmail.com \
--cc=emacs-orgmode@gnu.org \
--cc=rasmus@gmx.us \
/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).