From mboxrd@z Thu Jan 1 00:00:00 1970 From: Rasmus Subject: Re: [patch, ox-latex] better hyperref and title options Date: Sun, 15 Feb 2015 12:42:16 +0100 Message-ID: <874mqn765j.fsf@gmx.us> References: <87bnl0ynd2.fsf@gmx.us> <87bnkyvfz2.fsf@nicolasgoaziou.fr> <87lhk0aqjd.fsf@pank.eu> <878ufzo3f2.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]:41660) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1YMxak-0002Ei-Fv for emacs-orgmode@gnu.org; Sun, 15 Feb 2015 06:42:32 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1YMxae-0001KP-Dj for emacs-orgmode@gnu.org; Sun, 15 Feb 2015 06:42:26 -0500 Received: from mout.gmx.net ([212.227.17.22]:52769) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1YMxae-0001K3-2m for emacs-orgmode@gnu.org; Sun, 15 Feb 2015 06:42:20 -0500 Received: from W530 ([46.166.186.232]) by mail.gmx.com (mrgmx103) with ESMTPSA (Nemesis) id 0LevUh-1XnPBl0VTz-00qhFT for ; Sun, 15 Feb 2015 12:42:18 +0100 In-Reply-To: <878ufzo3f2.fsf@nicolasgoaziou.fr> (Nicolas Goaziou's message of "Sun, 15 Feb 2015 11:49:21 +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 Nicolas Goaziou writes: >> 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? 'Cause usually org-export-data gives you the right value automatically. Anyway, I don't mind using org-element-parse-secondary-string. >> 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. 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. =E2=80=94Rasmus --=20 Slowly unravels in a ball of yarn and the devil collects it