From mboxrd@z Thu Jan 1 00:00:00 1970 From: Nicolas Goaziou Subject: Re: [ox, patch] #+SUBTITLE Date: Mon, 30 Mar 2015 09:39:44 +0200 Message-ID: <87a8yv0w8v.fsf@nicolasgoaziou.fr> References: <87y4miv7y6.fsf@gmx.us> <87a8yxi0zf.fsf@nicolasgoaziou.fr> <87k2y1qfpi.fsf@gmx.us> <87d23sdtod.fsf@nicolasgoaziou.fr> <87oanct43z.fsf@gmx.us> <874mp4dkeb.fsf@nicolasgoaziou.fr> <87bnjct08z.fsf@gmx.us> 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]:45032) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1YcUHL-0005uV-3z for emacs-orgmode@gnu.org; Mon, 30 Mar 2015 03:38:36 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1YcUHG-0001Kc-FE for emacs-orgmode@gnu.org; Mon, 30 Mar 2015 03:38:35 -0400 Received: from relay4-d.mail.gandi.net ([2001:4b98:c:538::196]:56468) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1YcUHG-0001KP-8u for emacs-orgmode@gnu.org; Mon, 30 Mar 2015 03:38:30 -0400 In-Reply-To: <87bnjct08z.fsf@gmx.us> (rasmus@gmx.us's message of "Sun, 29 Mar 2015 15:13:32 +0200") 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: emacs-orgmode@gnu.org Rasmus writes: > Nicolas Goaziou writes: >> Do you mean KEYWORD and DESCRIPTION should also belong to category 1? >> I'm not against it, but then, back-ends are required to support them >> whenever possible. > > At the moment they are. They lack ascii support, but at least keywords > should be supported in ascii eventually IMO (but that's another thread). > > So I would keep them. The documentation explicitly states which backend > these keywords are supported by. OK. Then DESCRIPTION and KEYWORD stay in "ox.el", and documented in "Export settings". You need to revert your patch about it. We will have to take care about support for missing back-ends. E.g., ASCII could treat DESCRIPTION as a quote box just below title. >>> We could add a subsection with "text document properties" which are >>> keywords that are supported by the set: {ox-html, ox-ascii, ox-odt, >>> ox-latex}. These would be sort of 1=C2=BD class citizens. >> >> I don't want to create a third category (=C3=A0 la >> `org-element-document-properties', which I'm trying to remove). > > This category would not exists in the code. It would simply be a > classification that exists in the manual. I would be a hack to not > maintain "no. of backend that support SOME_KEYWORD" different places to > maintain documentation for SOME_KEYWORD. I don't think it is needed. Such "text document properties" are de facto members of category 1 anyway. Regards,