From mboxrd@z Thu Jan 1 00:00:00 1970 From: Aaron Ecay Subject: Re: Citation syntax: a revised proposal Date: Sun, 15 Feb 2015 19:38:39 +0000 Message-ID: <87wq3jc6dc.fsf@gmail.com> References: <87k2zjnc0e.fsf@berkeley.edu> <87zj8fjdnv.fsf@nicolasgoaziou.fr> <873867m4kg.fsf@berkeley.edu> <87fva7jaly.fsf@nicolasgoaziou.fr> <87zj8fc7w5.fsf@gmail.com> <87bnkvj85w.fsf@nicolasgoaziou.fr> Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Return-path: Received: from eggs.gnu.org ([2001:4830:134:3::10]:44973) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1YN51j-00008u-Ap for emacs-orgmode@gnu.org; Sun, 15 Feb 2015 14:38:51 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1YN51e-0006rb-Km for emacs-orgmode@gnu.org; Sun, 15 Feb 2015 14:38:47 -0500 Received: from mail-wi0-x232.google.com ([2a00:1450:400c:c05::232]:53645) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1YN51e-0006rS-EQ for emacs-orgmode@gnu.org; Sun, 15 Feb 2015 14:38:42 -0500 Received: by mail-wi0-f178.google.com with SMTP id em10so22163402wid.5 for ; Sun, 15 Feb 2015 11:38:41 -0800 (PST) In-Reply-To: <87bnkvj85w.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 , Richard Lawrence Cc: emacs-orgmode@gnu.org Hi Nicolas, 2015ko otsailak 15an, Nicolas Goaziou-ek idatzi zuen: > Perhaps. But [cite: ... |latex: :cap t |html: :cap t] isn't impossible > to write either. It violates DRY. It (thus) makes it annoying to export a document to a new backend: you have to search through all the citations and copy any :cap keys to the new backend. Crazy idea: what if there was a =E2=80=9Croot=E2=80=9D backend from which a= ll other backends were derived? This would maintain consistency with existing attribute syntax (and possibly new, as proposed below), but also allow certain attributes to be passed to all backends. >=20 > Anyway, time for another proposal. In fact, it seems that it would be > better to externalize these properties, e.g., >=20 > [cite: ...]{latex :prop val}{html :prop val} >=20 > or >=20 > [cite: ...]{latex :prop val | html :prop val} >=20 > No space allowed between the citation and the attributes. The big > advantage with this is that it can be extended to other objects while > still being backward-compatible. >=20 > It would solve one long standing limitation: >=20 > Text [[file:img1.png]]{html :width 50px} and > [[file:img2.png]]{html :width 60 px} Nice, I like it. Thanks, --=20 Aaron Ecay