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:05:46 +0000 Message-ID: <87zj8fc7w5.fsf@gmail.com> References: <87k2zjnc0e.fsf@berkeley.edu> <87zj8fjdnv.fsf@nicolasgoaziou.fr> <873867m4kg.fsf@berkeley.edu> <87fva7jaly.fsf@nicolasgoaziou.fr> Mime-Version: 1.0 Content-Type: text/plain Return-path: Received: from eggs.gnu.org ([2001:4830:134:3::10]:40201) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1YN4Vv-0002Re-A1 for emacs-orgmode@gnu.org; Sun, 15 Feb 2015 14:06:00 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1YN4Vq-0004E6-Mn for emacs-orgmode@gnu.org; Sun, 15 Feb 2015 14:05:55 -0500 Received: from mail-wg0-x22f.google.com ([2a00:1450:400c:c00::22f]:63444) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1YN4Vq-0004Dz-Gb for emacs-orgmode@gnu.org; Sun, 15 Feb 2015 14:05:50 -0500 Received: by mail-wg0-f47.google.com with SMTP id x12so12090120wgg.6 for ; Sun, 15 Feb 2015 11:05:49 -0800 (PST) In-Reply-To: <87fva7jaly.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: >> 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). Thanks, -- Aaron Ecay