From mboxrd@z Thu Jan 1 00:00:00 1970 From: Matt Price Subject: Re: current status of citation syntax discussion Date: Tue, 16 Jun 2015 16:18:16 -0400 Message-ID: References: <87bngfa0un.fsf@gmx.us> Mime-Version: 1.0 Content-Type: multipart/alternative; boundary=001a11347b184b30570518a84601 Return-path: Received: from eggs.gnu.org ([2001:4830:134:3::10]:58899) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1Z4xJK-0002aA-Tu for emacs-orgmode@gnu.org; Tue, 16 Jun 2015 16:18:22 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1Z4xJJ-0003ZK-IZ for emacs-orgmode@gnu.org; Tue, 16 Jun 2015 16:18:18 -0400 Received: from mail-la0-x234.google.com ([2a00:1450:4010:c03::234]:35493) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1Z4xJJ-0003YL-Ad for emacs-orgmode@gnu.org; Tue, 16 Jun 2015 16:18:17 -0400 Received: by labko7 with SMTP id ko7so19134824lab.2 for ; Tue, 16 Jun 2015 13:18:16 -0700 (PDT) In-Reply-To: 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: Rasmus Cc: Org Mode --001a11347b184b30570518a84601 Content-Type: text/plain; charset=UTF-8 On Jun 16, 2015 3:51 PM, "Rasmus" wrote: > > Matt Price writes: > > > Am just wondering what the current status is of the work that was being > > done earlier this year on improved citation support in org. Has an > > official syntax been settled on? > > AFAIK: No. Some people wanted something like [cite/type: pre @key post]. > Some people wanted additional key-value support, something like > [cite: pre @key post]{:key val}. Some people wanted @key > to be able to contain arbitrary characters such as punctuation. Is the discussion stalled out then? What would have to happen to move it along? > > > Are there blessed citation managers and export solutions? > > ox-bibtex supports \cite{key} and I think [[cite:key]]. > > > I would like to figure out a personal system over the summer, and would > > prefer to adhere to whatever stand(s) others have settled on. > > There's about as many systems as there are org users. I use > [[citetype: pre @key post]]. (hmm, are spaces allowed in pre and post? If so how is the expression parsed? ) > If it's not too much trouble, could you provide some examples of code you use to - generate cite links - export those links to (preferably non-latex) formats ? Thanks as always, Matt > Rasmus > > -- > May the Force be with you And with you. > > --001a11347b184b30570518a84601 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable


On Jun 16, 2015 3:51 PM, "Rasmus" <rasmus@gmx.us> wrote:
>
> Matt Price <moptop99@gmail.co= m> writes:
>
> > Am just wondering what the current status is of the work that was= being
> > done earlier this year on improved citation support in org.=C2=A0= Has an
> > official syntax been settled on?
>
> AFAIK: No.=C2=A0 Some people wanted something like [cite/type: pre @ke= y post].
> Some people wanted additional key-value support, something like
> [cite: pre @key post]{:key val}.=C2=A0 Some people wanted @key
> to be able to contain arbitrary characters such as punctuation.

Is the discussion stalled out then?=C2=A0 What would have to= happen to move it along?
>
> > Are there blessed citation managers and export solutions?
>
> ox-bibtex supports \cite{key} and I think [[cite:key]].
>
> > I would like to figure out a personal system over the summer, and= would
> > prefer to adhere to whatever stand(s) others have settled on.
>
> There's about as many systems as there are org users.=C2=A0 I use<= br> > [[citetype: pre @key post]].

(hmm,=C2=A0 are spaces allowed in pre and post? If so how is= the expression parsed? )
>

If it's not too much trouble,=C2=A0 could you provide so= me examples of code you use to

- generate cite links
- export those links to (preferably non-latex)=C2=A0 formats
?

Thanks as always,
Matt
> Rasmus
>
> --
> May the Force be with you
And with you.
>
>

--001a11347b184b30570518a84601--