From mboxrd@z Thu Jan 1 00:00:00 1970 From: Nicolas Goaziou Subject: Re: Citation syntax: a revised proposal Date: Sun, 15 Feb 2015 20:18:03 +0100 Message-ID: <87bnkvj85w.fsf@nicolasgoaziou.fr> References: <87k2zjnc0e.fsf@berkeley.edu> <87zj8fjdnv.fsf@nicolasgoaziou.fr> <873867m4kg.fsf@berkeley.edu> <87fva7jaly.fsf@nicolasgoaziou.fr> <87zj8fc7w5.fsf@gmail.com> Mime-Version: 1.0 Content-Type: text/plain Return-path: Received: from eggs.gnu.org ([2001:4830:134:3::10]:41459) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1YN4gg-0001l1-3v for emacs-orgmode@gnu.org; Sun, 15 Feb 2015 14:17:06 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1YN4gb-0007Ib-0S for emacs-orgmode@gnu.org; Sun, 15 Feb 2015 14:17:01 -0500 Received: from relay5-d.mail.gandi.net ([2001:4b98:c:538::197]:52464) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1YN4ga-0007IX-Qy for emacs-orgmode@gnu.org; Sun, 15 Feb 2015 14:16:56 -0500 In-Reply-To: <87zj8fc7w5.fsf@gmail.com> (Aaron Ecay's message of "Sun, 15 Feb 2015 19:05:46 +0000") 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 Cc: emacs-orgmode@gnu.org Hello, Aaron Ecay writes: > Hi Nicolas, > > 2015ko otsailak 15an, Nicolas Goaziou-ek idatzi zuen: >>> 1) It looks like it only supports properties directed at specific >>> backends. How should users specify custom properties that they want to >>> be handled in multiple backends (by their own filter)? >> >> They cannot (unless they want to use something like "|custom: ..."). >> >> Note they cannot either for regular elements using attributes. The >> reason is that multiple back-end properties are very rare. For >> example, :width hasn't the same unit in "ox-latex" and "ox-html". > > It seems like these might occur for citations. The :capitalize property > discussed in the predecessor to this thread is one example. So perhaps > there could be a |all: list which would be merged with the > backend-specific one(s). Perhaps. But [cite: ... |latex: :cap t |html: :cap t] isn't impossible to write either. Anyway, time for another proposal. In fact, it seems that it would be better to externalize these properties, e.g., [cite: ...]{latex :prop val}{html :prop val} or [cite: ...]{latex :prop val | html :prop val} 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. It would solve one long standing limitation: Text [[file:img1.png]]{html :width 50px} and [[file:img2.png]]{html :width 60 px} Regards,