Hi Nicolas,
I'm a bit confused by your message.
Nicolas Goaziou <m...@nicolasgoaziou.fr> writes:
> However, I think porting this feature to back-ends that do not support
> it out of the box is pushing too hard.
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{·} 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.
—Rasmus
--
Hvor meget poesi tror De kommer ud af et glas isvand?
