From mboxrd@z Thu Jan 1 00:00:00 1970 From: Richard Lawrence Subject: Re: Citation syntax: a revised proposal Date: Mon, 02 Mar 2015 18:48:08 -0800 Message-ID: <87d24qaj9z.fsf@berkeley.edu> References: <87k2zjnc0e.fsf@berkeley.edu> <87bnkvm8la.fsf@berkeley.edu> <87zj8co3se.fsf@berkeley.edu> <87ioezooi2.fsf@berkeley.edu> <87mw4bpaiu.fsf@nicolasgoaziou.fr> <8761aznpiq.fsf@berkeley.edu> <87twyjnh0r.fsf@nicolasgoaziou.fr> <87oaopx24e.fsf@berkeley.edu> <87k2zd4f3w.fsf@nicolasgoaziou.fr> <87egpkv8g9.fsf@berkeley.edu> <877fv6xfaq.fsf@gmail.com> <87twya2ak0.fsf@berkeley.edu> <87zj81aa97.fsf@nicolasgoaziou.fr> <87ioep2r6p.fsf@berkeley.edu> <87y4ngbgm7.fsf@nicolasgoaziou.fr> <87twy39qt2.fsf@berkeley.edu> <87pp8rb1i3.fsf@nicolasgoaziou.fr> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Return-path: Received: from eggs.gnu.org ([2001:4830:134:3::10]:33760) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1YSctB-0004Yn-SH for emacs-orgmode@gnu.org; Mon, 02 Mar 2015 21:48:59 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1YSct5-0003o5-Q5 for emacs-orgmode@gnu.org; Mon, 02 Mar 2015 21:48:53 -0500 Received: from mail-pa0-f50.google.com ([209.85.220.50]:33571) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1YSct5-0003nq-Kg for emacs-orgmode@gnu.org; Mon, 02 Mar 2015 21:48:47 -0500 Received: by padet14 with SMTP id et14so23206403pad.0 for ; Mon, 02 Mar 2015 18:48:46 -0800 (PST) In-Reply-To: <87pp8rb1i3.fsf@nicolasgoaziou.fr> List-Id: "General discussions about Org-mode." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org Sender: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org To: Nicolas Goaziou Cc: emacs-orgmode@gnu.org Hi Nicolas, Nicolas Goaziou writes: > To support multi cites, we must first decide how the parsed will present > information, i.e., what are the properties in the following case > > [cite:pre; pre1 @k1 post1; pre2 @k2 post2; post] I was thinking that this should yield a citation object with a structure like: ('citation ... :common-prefix pre :common-suffix post :references ((:prefix pre1 :key "k1" :suffix post1 ...) (:prefix pre2 :key "k2" :suffix post2 ...)) ...) Would that work? > There is also the following degenerate case > > [cite:pre; pre ;post] > > What should be done about it? Hmm, I don't quite understand what you mean. This is not allowed by the grammar (as far as I can tell), so that should not parse as a citation object, IMO. > I didn't implement &-keys as there is no consensus on them. Oh, I did not realize there were outstanding issues with this. I remember Rasmus not liking `&'. I'm fine with changing it, though I cannot think of a better symbol. Does someone think we should not have a way of indicating that a reference should produce a full bibliography entry? Or that we should indicate it in some other way? Best, Richard