From mboxrd@z Thu Jan 1 00:00:00 1970 From: Nicolas Goaziou Subject: Re: [patch, ox-latex] better hyperref and title options Date: Sun, 15 Feb 2015 13:57:26 +0100 Message-ID: <87h9unl4cp.fsf@nicolasgoaziou.fr> References: <87bnl0ynd2.fsf@gmx.us> <87bnkyvfz2.fsf@nicolasgoaziou.fr> <87lhk0aqjd.fsf@pank.eu> <878ufzo3f2.fsf@nicolasgoaziou.fr> <874mqn765j.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]:53696) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1YMykI-0006gD-Dz for emacs-orgmode@gnu.org; Sun, 15 Feb 2015 07:56:27 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1YMykD-000487-9v for emacs-orgmode@gnu.org; Sun, 15 Feb 2015 07:56:22 -0500 Received: from relay3-d.mail.gandi.net ([2001:4b98:c:538::195]:55638) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1YMykD-000482-4Y for emacs-orgmode@gnu.org; Sun, 15 Feb 2015 07:56:17 -0500 In-Reply-To: <874mqn765j.fsf@gmx.us> (rasmus@gmx.us's message of "Sun, 15 Feb 2015 12:42:16 +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: Rasmus Cc: emacs-orgmode@gnu.org Rasmus writes: > 'Cause usually org-export-data gives you the right value automatically. > Anyway, I don't mind using org-element-parse-secondary-string. `org-element-parse-secondary-string' is meant for cases like this one. >> DESCRIPTION could be moved to `org-element-document-properties'. But >> then, we need to introduce `org-export-with-description', which implies >> export back-ends have to deal with it somehow (ATM "ox-ascii" ignores >> it). > >> Another option is to simply remove DESCRIPTION from "ox.el" and let >> export back-ends in need of it to add it to their definition. > > I don't oppose that. > >> However, I don't see why KEYWORDS should accept markup. I also think it >> should be moved to back-end definitions instead of "ox.el". > > Keywords should also be printed in the document as well IMO, e.g. after > the abstract. An example of where you need markup: =CF=83-algebra. Good point. Since KEYWORDS and DESCRIPTION are really back-end dependant, I vote for moving them from `org-export-options-alist' to back-end definitions. Using `org-element-parse-secondary-string' will be required in this case. WDYT? Also, supposing you agree, do you want to do a patch (caveat: there's "org.texi" messing involved)? Regards,