From mboxrd@z Thu Jan 1 00:00:00 1970 From: "Thomas S. Dye" Subject: Re: Emphasis etc. in #+CAPTION: Date: Sun, 28 Mar 2010 18:52:27 -1000 Message-ID: References: <32037.1269825277@gamaville.dokosmarshall.org> Mime-Version: 1.0 (Apple Message framework v936) Content-Type: text/plain; charset=UTF-8; format=flowed; delsp=yes Content-Transfer-Encoding: quoted-printable Return-path: Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1Nw6xo-0003Oh-MX for emacs-orgmode@gnu.org; Mon, 29 Mar 2010 00:52:36 -0400 Received: from [140.186.70.92] (port=45190 helo=eggs.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1Nw6xm-0003Mr-S6 for emacs-orgmode@gnu.org; Mon, 29 Mar 2010 00:52:36 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.69) (envelope-from ) id 1Nw6xl-0006ws-88 for emacs-orgmode@gnu.org; Mon, 29 Mar 2010 00:52:34 -0400 Received: from outbound-mail-360.bluehost.com ([66.147.249.254]:51223) by eggs.gnu.org with smtp (Exim 4.69) (envelope-from ) id 1Nw6xl-0006wl-15 for emacs-orgmode@gnu.org; Mon, 29 Mar 2010 00:52:33 -0400 In-Reply-To: <32037.1269825277@gamaville.dokosmarshall.org> 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: nicholas.dokos@hp.com Cc: emacs-orgmode list On Mar 28, 2010, at 3:14 PM, Nick Dokos wrote: > Thomas S. Dye wrote: > >> I see in the Org Manual that: >> >> You can make words *bold*, /italic/, _underlined_, =3Dcode=3D and >> ~verbatim~, and, if you must, =E2=80=98+strike-through+=E2=80=99. = Text in the =20 >> code >> and verbatim string is not processed for Org-mode specific syntax, >> it is exported verbatim. >> >> 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 =20 > 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. > >> >> #+CAPTION: Pumice collected from p=C4=81hoehoe flows at = Manini`=C5=8Dwali: >> /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. >> >> Is there a common work-around for this that will produce correct =20 >> LaTeX >> and HTML using the org-mode exporters? >> > > 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? >> > > I think this is the way it works currently: > > in org-exp.el:org-export-attach-captions-and-attributes() sets text =20= > properties > on the following line (the first line of a table or the line =20 > containing a link) > 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 =20= > 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-=20 > 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, =20 > but it > is not done today. > > But maybe I'm full of it, and somebody will come up with a better =20 > idea. > > Cheers, > Nick > Thanks Nick, That seems to work. I'll test it a bit to make certain, but right now =20= the italics in the legend look very good in place of /a/, etc., so =20 there is some progress. All the best, Tom