From mboxrd@z Thu Jan 1 00:00:00 1970 From: Matt Price Subject: Re: Citation syntax: a revised proposal Date: Tue, 3 Mar 2015 19:43:07 -0500 Message-ID: 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> <87d24qaj9z.fsf@berkeley.edu> <87vbiia2t7.fsf@nicolasgoaziou.fr> Mime-Version: 1.0 Content-Type: multipart/alternative; boundary=089e01493d9e2771f105106bbc36 Return-path: Received: from eggs.gnu.org ([2001:4830:134:3::10]:40473) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1YSxP5-0000NW-7K for emacs-orgmode@gnu.org; Tue, 03 Mar 2015 19:43:12 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1YSxP3-0008AU-Nr for emacs-orgmode@gnu.org; Tue, 03 Mar 2015 19:43:11 -0500 Received: from mail-la0-x236.google.com ([2a00:1450:4010:c03::236]:44920) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1YSxP3-00089w-Bz for emacs-orgmode@gnu.org; Tue, 03 Mar 2015 19:43:09 -0500 Received: by lams18 with SMTP id s18so41177382lam.11 for ; Tue, 03 Mar 2015 16:43:07 -0800 (PST) In-Reply-To: <87vbiia2t7.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: Richard Lawrence , Org Mode --089e01493d9e2771f105106bbc36 Content-Type: text/plain; charset=UTF-8 On Mar 3, 2015 3:43 AM, "Nicolas Goaziou" wrote: > > Richard Lawrence 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? > > Yes. I find it better than "entries/entry" as discussed with Rasmus. > I'll implement it in a few days. > > > 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? > > AFAIC, I don't think a dedicated symbol is useful. It can be implemented > through subtypes/properties. Besides LaTeX, could other back-end provide > that feature anyway? > I have done this with zotxt for HTML and odt export, so it should be possible. I personally really like this, as I have a personal use case (course syllabi) where I need this all the time. But I may be unusual in this. Matt > I have no opinion about the :suppress-author symbol. > > > Regards, > --089e01493d9e2771f105106bbc36 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable


On Mar 3, 2015 3:43 AM, "Nicolas Goaziou" <mail@nicolasgoaziou.fr> wrote:
>
> Richard Lawrence <= richard.lawrence@berkeley.edu> writes:
>
> >> To support multi cites, we must first decide how the parsed w= ill present
> >> information, i.e., what are the properties in the following c= ase
> >>
> >>=C2=A0 =C2=A0[cite:pre; pre1 @k1 post1; pre2 @k2 post2; post]<= br> > >
> > I was thinking that this should yield a citation object with a st= ructure like:
> >
> > ('citation ...
> >=C2=A0 =C2=A0:common-prefix pre
> >=C2=A0 =C2=A0:common-suffix post
> >=C2=A0 =C2=A0:references ((:prefix pre1
> >=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0:key= "k1"
> >=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0:suf= fix post1 ...)
> >=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 (:prefix p= re2
> >=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0:key= "k2"
> >=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0:suf= fix post2 ...))
> >=C2=A0 =C2=A0...)
> >
> > Would that work?
>
> Yes. I find it better than "entries/entry" as discussed with= Rasmus.
> I'll implement it in a few days.
>
> > Oh, I did not realize there were outstanding issues with this.=C2= =A0 I
> > remember Rasmus not liking `&'.=C2=A0 I'm fine with c= hanging it, though I
> > cannot think of a better symbol.=C2=A0 Does someone think we shou= ld not have
> > a way of indicating that a reference should produce a full biblio= graphy
> > entry?=C2=A0 Or that we should indicate it in some other way?
>
> AFAIC, I don't think a dedicated symbol is useful. It can be imple= mented
> through subtypes/properties. Besides LaTeX, could other back-end provi= de
> that feature anyway?
>

I have done this with zotxt for HTML and odt export, so it s= hould be possible. I personally really like this, as I have a personal use = case (course syllabi) where I need this all the time. But I may be unusual = in this.

Matt
> I have no opinion about the :suppress-author symbol.
>
>
> Regards,
>

--089e01493d9e2771f105106bbc36--