From mboxrd@z Thu Jan 1 00:00:00 1970 From: Rasmus Subject: Re: [ox, patch] #+SUBTITLE Date: Tue, 31 Mar 2015 12:35:18 +0200 Message-ID: <871tk5jvyx.fsf@gmx.us> 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> <87a8yv0w8v.fsf@nicolasgoaziou.fr> <87twx24vt5.fsf@gmx.us> <87d23pzczl.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]:52959) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1YctW5-0004JZ-Nj for emacs-orgmode@gnu.org; Tue, 31 Mar 2015 06:35:31 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1YctVy-0007tB-Gv for emacs-orgmode@gnu.org; Tue, 31 Mar 2015 06:35:29 -0400 Received: from mout.gmx.net ([212.227.17.20]:54761) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1YctVy-0007sk-7C for emacs-orgmode@gnu.org; Tue, 31 Mar 2015 06:35:22 -0400 Received: from x200s ([46.166.186.213]) by mail.gmx.com (mrgmx102) with ESMTPSA (Nemesis) id 0MHal6-1Ybn3F0g9s-003Mez for ; Tue, 31 Mar 2015 12:35:21 +0200 In-Reply-To: <87d23pzczl.fsf@nicolasgoaziou.fr> (Nicolas Goaziou's message of "Tue, 31 Mar 2015 12:18:38 +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: emacs-orgmode@gnu.org Hi, Nicolas Goaziou writes: > As I explained, both are linked: > > - Anything defined in "ox.el" is documented in "Export settings" ; > - Anything defined in "ox-backend.el" is documented in "Backend > export". > > This is a hard rule. OK. > Even if it means repeating documentation in three > different places, some back-end might use differently the same keyword > than others. > > For the record, if the situation ever rises again, I think that > a keyword can be added to "ox.el" only if > > - it is supported at least in every major back-end (ASCII, HTML, > LaTeX, ODT and Texinfo) > - it comes with a toggle in the OPTIONS line e.g. keyword:nil For subtitle I'm reusing :with-title. If you think it necessary, I can add a :with-subtitle, but I didn't think it was necessary. >> So should I also move the SUBTITLE to ox.el or keep it in files? I think >> it's OK to just define it in the files where it makes sense... > > SUBTITLE, DESCRIPTION and KEYWORDS can be defined in the libraries where > they are used. Only the documentation needs to be adapted, per above. > > Sorry for the confusion. OK. So with the above the in mind the game plan seems to be: - Remove DESCRIPTION/KEYWORD from it's current position in org.texi to backend descriptions and retain them in relevant backends. This imply some repetition, but also allows greater details, e.g. with latex we can point to the hyperref template. - In the subtitle patch documentation should be documented in the relevant backend sections. >>> 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. >> >> Would that not be an abstract? I'm not sure I think description should = be >> handled like that. > > Forget about it. I'm not sure DESCRIPTION should be handled at all in > ASCII back-end. OK. If you want something like the above, I think we should just recognize abstract blocks and reuse the quote formatting. Nicolas Goaziou writes: > Let's erase my suggestion from the internet archives. Pretty please. You can ask Lars to remove the post from gmane, at least . . . :) =E2=80=94Rasmus --=20 Dung makes an excellent fertilizer