From mboxrd@z Thu Jan 1 00:00:00 1970 From: Rasmus Subject: Re: [ox, patch] Add #+SUBTITLE Date: Sun, 22 Mar 2015 16:29:31 +0100 Message-ID: <87sicx6of8.fsf@gmx.us> References: <87a8z7z20k.fsf@gmx.us> <87vbht2kri.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]:54709) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1YZhoo-0003Fv-HS for emacs-orgmode@gnu.org; Sun, 22 Mar 2015 11:29:39 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1YZhok-00064r-Ho for emacs-orgmode@gnu.org; Sun, 22 Mar 2015 11:29:38 -0400 Received: from mout.gmx.net ([212.227.17.22]:57453) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1YZhok-00064k-8D for emacs-orgmode@gnu.org; Sun, 22 Mar 2015 11:29:34 -0400 Received: from W530 ([109.201.154.154]) by mail.gmx.com (mrgmx101) with ESMTPSA (Nemesis) id 0Li0dC-1ZLQhq3cHK-00nDNq for ; Sun, 22 Mar 2015 16:29:33 +0100 In-Reply-To: <87vbht2kri.fsf@nicolasgoaziou.fr> (Nicolas Goaziou's message of "Sun, 22 Mar 2015 15:02:09 +0100") 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, I'm a bit confused by your message. Nicolas Goaziou writes: > However, I think porting this feature to back-ends that do not support > it out of the box is pushing too hard.=20 In the patch there's ox-latex where e.g. KOMA-Script has as subtitle-macro. ox-html, ox-ascii, ox-odt all are pretty liberate formats in terms of what elements are supported. > Back-ends developers should try hard to support features defined in > "ox.el" (in particular in `org-export-options-alist'). However, all > back-ends are free to implement their specific keywords without adding > burden on other libraries. "ox-texinfo" supports #+SUBAUTHOR, should we > add it everywhere? I don't think so. OK. ox and org-element shouldn't be touched by the patch. > This is why I suggested to move KEYWORD and DESCRIPTION outside of > "ox.el", as they cannot be ported to all back-ends without relying on > dubious markup. Yeah, I still have a patch for that... I still have to do the documentation changes. > Now, if SUBTITLE is a feature desperately needed everywhere, which can > be discussed, it should be moved to "ox.el" and probably > `org-element-document-keywords'. IMO, this is not necessary. SUBTITLE > should be kept for back-ends that can handle it. IMO it is. The only place where there's a "hack" is in ox-latex and that's cause article is the default class. If you prefer, it can just output to the \subtitle{=C2=B7} by default and say it's KOMA-script only. = That seems harsh, though. > As a side note, "ox-texinfo" doesn't parse SUBTITLE. You might want to > change it and update manual accordingly. The patch doesn't touch ox-texinfo. I don't mind fixing that bug, though. =E2=80=94Rasmus --=20 Hvor meget poesi tror De kommer ud af et glas isvand?