all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: "Thomas S. Dye" <tsd@tsdye.com>
To: emacs-orgmode list <emacs-orgmode@gnu.org>
Subject: Emphasis etc. in #+CAPTION:
Date: Sun, 28 Mar 2010 09:14:05 -1000	[thread overview]
Message-ID: <A349A9C9-FBEB-40C6-813B-5C0C9E408E9D@tsdye.com> (raw)


[-- Attachment #1.1: Type: text/plain, Size: 1134 bytes --]

Aloha all,

I see in the Org Manual that:

> You can make words *bold*, /italic/, _underlined_, =code= and  
> ~verbatim~, and, if you must, ‘+strike-through+’.  Text in the  
> 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):

> #+CAPTION: Pumice collected from pāhoehoe flows at Manini`ō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.

Is there a common work-around for this that will produce correct LaTeX  
and HTML using the org-mode exporters?

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?

All the best,
Tom


[-- Attachment #1.2: Type: text/html, Size: 1663 bytes --]

[-- Attachment #2: Type: text/plain, Size: 201 bytes --]

_______________________________________________
Emacs-orgmode mailing list
Please use `Reply All' to send replies to the list.
Emacs-orgmode@gnu.org
http://lists.gnu.org/mailman/listinfo/emacs-orgmode

             reply	other threads:[~2010-03-28 19:14 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-03-28 19:14 Thomas S. Dye [this message]
2010-03-29  1:14 ` Emphasis etc. in #+CAPTION: Nick Dokos
2010-03-29  4:52   ` Thomas S. Dye
2010-03-29 12:20   ` Carsten Dominik

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=A349A9C9-FBEB-40C6-813B-5C0C9E408E9D@tsdye.com \
    --to=tsd@tsdye.com \
    --cc=emacs-orgmode@gnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this external index

	https://git.savannah.gnu.org/cgit/emacs.git
	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.