From: Christian Moe <mail@christianmoe.com>
To: Nicolas Goaziou <mail@nicolasgoaziou.fr>
Cc: tumashu <tumashu@163.com>, emacs-orgmode <emacs-orgmode@gnu.org>,
"Simonyi András" <andras.simonyi@gmail.com>,
"John Kitchin" <jkitchin@andrew.cmu.edu>
Subject: Re: Should wip-cite branch be merged to master?
Date: Sat, 21 Apr 2018 10:43:38 +0200 [thread overview]
Message-ID: <87r2n9kkzp.fsf@christianmoe.com> (raw)
In-Reply-To: <871sf9f2ak.fsf@nicolasgoaziou.fr>
I have no opinion on whether it's time for a merge or not, but please
don't wait up for me.
Nicolas Goaziou writes:
> I also remember that Christian Moe suggested an alternate syntax for
> citations. He might want to point out what is missing from @cite syntax
> and if he still prefers his idea.
I did, but my suggestions did not get any traction back when a native
citation syntax was first being discussed on the list. Regrettably, I
have not managed to follow up my proposal properly, then or now -- not
even to the point of updating my own sample code after a Zotero
development broke it last year -- and I probably won't in the
foreseeable near future. So I wouldn't want to hold back a
community-developed solution on account that I had a different idea.
My proposal was for a different approach (parsing a "natural-looking"
citation syntax like (Smith 1990: p.3)), which I thought could be both
more user-friendly and more aesthetically pleasing in plain text. It
was not for improvements to the @cite syntax, so I don't actually know
what is missing from the latter, if anything. I was very excited about
the citeproc contributon, but I have not found the time to test it out.
next prev parent reply other threads:[~2018-04-21 9:31 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-20 23:01 Should wip-cite branch be merged to master? tumashu
2018-04-21 7:26 ` Nicolas Goaziou
2018-04-21 8:43 ` Christian Moe [this message]
2018-04-22 18:17 ` András Simonyi
2018-04-23 19:42 ` John Kitchin
2018-04-25 19:19 ` Richard Lawrence
2018-04-26 23:34 ` Bastien
2018-04-27 21:07 ` András Simonyi
2018-04-27 23:34 ` Nicolas Goaziou
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=87r2n9kkzp.fsf@christianmoe.com \
--to=mail@christianmoe.com \
--cc=andras.simonyi@gmail.com \
--cc=emacs-orgmode@gnu.org \
--cc=jkitchin@andrew.cmu.edu \
--cc=mail@nicolasgoaziou.fr \
--cc=tumashu@163.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).