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 11:49:21 +0100 Message-ID: <878ufzo3f2.fsf@nicolasgoaziou.fr> References: <87bnl0ynd2.fsf@gmx.us> <87bnkyvfz2.fsf@nicolasgoaziou.fr> <87lhk0aqjd.fsf@pank.eu> Mime-Version: 1.0 Content-Type: text/plain Return-path: Received: from eggs.gnu.org ([2001:4830:134:3::10]:33850) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1YMwkM-0000Ml-LW for emacs-orgmode@gnu.org; Sun, 15 Feb 2015 05:48:23 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1YMwkH-0008Fj-Su for emacs-orgmode@gnu.org; Sun, 15 Feb 2015 05:48:18 -0500 Received: from relay3-d.mail.gandi.net ([2001:4b98:c:538::195]:42602) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1YMwkH-0008FD-N7 for emacs-orgmode@gnu.org; Sun, 15 Feb 2015 05:48:13 -0500 In-Reply-To: <87lhk0aqjd.fsf@pank.eu> (rasmus@gmx.us's message of "Sun, 15 Feb 2015 02:53:42 +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 Hello, Rasmus writes: > Nicolas Goaziou writes: > >>> + (?k . ,(or (plist-get info :keywords) "")) >>> + (?d . ,(or (plist-get info :description) "")) > > So it occurred to me that these should also be exported to proper syntax > so we don't end up with e.g. a raw $ or & in our latex document. Hyperref > will actually handle it, but usually by discarding offending characters. > > However, since they are plain strings something like \alpha will be > exported as $\backslash$lpha. I can kind of get it interpreting using > org-element-parse-secondary-string, but this is not the right > approach. Why isn't it the right approach? > Is there a reason why DESCRIPTION and KEYWORDS can't have formatting? 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. 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". Regards, -- Nicolas Goaziou