From mboxrd@z Thu Jan 1 00:00:00 1970 From: Nick Dokos Subject: Re: Emphasis etc. in #+CAPTION: Date: Sun, 28 Mar 2010 21:14:37 -0400 Message-ID: <32037.1269825277@gamaville.dokosmarshall.org> References: Reply-To: nicholas.dokos@hp.com Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Return-path: Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1Nw4VP-0001SN-LX for emacs-orgmode@gnu.org; Sun, 28 Mar 2010 22:15:07 -0400 Received: from [140.186.70.92] (port=37183 helo=eggs.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1Nw4VO-0001SF-8z for emacs-orgmode@gnu.org; Sun, 28 Mar 2010 22:15:07 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.69) (envelope-from ) id 1Nw4VM-0001KN-7o for emacs-orgmode@gnu.org; Sun, 28 Mar 2010 22:15:06 -0400 Received: from vms173015pub.verizon.net ([206.46.173.15]:56192) by eggs.gnu.org with esmtp (Exim 4.69) (envelope-from ) id 1Nw4VM-0001KJ-1x for emacs-orgmode@gnu.org; Sun, 28 Mar 2010 22:15:04 -0400 Received: from gamaville.dokosmarshall.org ([unknown] [173.76.32.106]) by vms173015.mailsrvcs.net (Sun Java(tm) System Messaging Server 7u2-7.02 32bit (built Apr 16 2009)) with ESMTPA id <0L0000GHDRGETGB4@vms173015.mailsrvcs.net> for emacs-orgmode@gnu.org; Sun, 28 Mar 2010 20:14:38 -0500 (CDT) In-reply-to: Message from "Thomas S. Dye" of "Sun\, 28 Mar 2010 09\:14\:05 -1000." List-Id: "General discussions about Org-mode." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org Errors-To: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org To: "Thomas S. Dye" Cc: nicholas.dokos@hp.com, emacs-orgmode list Thomas S. Dye wrote: > I see in the Org Manual that: >=20 > You can make words *bold*, /italic/, _underlined_, =3Dcode=3D and > ~verbatim~, and, if you must, =E2=80=98+strike-through+=E2=80=99. Tex= t in the code > and verbatim string is not processed for Org-mode specific syntax, > it is exported verbatim. >=20 > So a caption like this doesn't export italicized a, b, c, and d > (presumably because this is a code string): Hi Tom, IIUC, it's not because it's a code string but simply because the caption is not processed for emphasis (or anything else for that matter - see below). I think the above text in the manual covers the generic case, but captions were probably added afterwards and they didn't get the emphasis treatment. >=20 > #+CAPTION: Pumice collected from p=C4=81hoehoe flows at Manini`=C5=8D= wali: > /a/, pieces that sink in fresh water; /b/, pieces without obvious > crystallization or coating (Category A); /c/, pieces with obvious > crystallization but no coating (Category B); /d/, pieces with > obvious coating (Category C). The scale is 1 cm. >=20 > Is there a common work-around for this that will produce correct LaTeX > and HTML using the org-mode exporters? >=20 Can't think of any workaround within org-mode. Post-processing the output to replace /a/ with \emph{a} for LaTeX and a for HTML, perhaps restricted to captions, seems possible (but ugly). > And, this is just a question and not a feature request or a request > for changes to org-mode, would it be hard to change org-mode's > behavior so that markup like /a/ in the #+CAPTION: string exports > correctly marked-up text to LaTeX and HTML? >=20 I think this is the way it works currently: in org-exp.el:org-export-attach-captions-and-attributes() sets text proper= ties on the following line (the first line of a table or the line containing a l= ink) as follows: ... (add-text-properties (point-at-bol) end (list 'org-caption cap 'org-attributes attr 'org-label label)) The various exporters then retrieve the caption with something like the following code (this is one of the three calls in org-latex.el; the other calls in this exporter, and the other exporters as well, are similar): (let* ... (caption (org-find-text-property-in-string 'org-caption raw-path)) ... This just gets the value of the given text property without further elaboration. So I'd guess it's possible to change these calls so that these values are passed through various filters (emphasis is one of them, but maybe there are others?) before the exporters get them, but it is not done today. But maybe I'm full of it, and somebody will come up with a better idea. Cheers, Nick