emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Rick Frankel <rick@rickster.com>
To: Peter Davis <pfd@pfdstudio.com>
Cc: emacs-orgmode@gnu.org
Subject: Re: Superscript and subscript in HTML?
Date: Wed, 28 May 2014 09:42:13 -0400	[thread overview]
Message-ID: <e6b7d52d86b6aa3651529c3f66518550@mail.rickster.com> (raw)
In-Reply-To: <20140528133612.GB2600@pfdstudio-air.home>

On 2014-05-28 09:36, Peter Davis wrote:
> On Wed, May 28, 2014 at 09:29:44AM -0400, Rick Frankel wrote:
> 
> The begin/end src lines are just that, markers to show where the org
> source starts and end. What you have formatted is a source code
> listing, not the source code.
> 
> If you're giving an example of org buffer contents, #+BEGIN_SRC and
> #+END_SRC are probably not the best delimiters to use to set off your
> example, since they're valid org markup.

#+BEGIN_SRC org
^^^

Is the common method on this list for specifying org (or any other)
source code in an email. Org can embed org source in org.
> 
> Anyway, it turns out some options I had enabled were preventing the
> superscript/subscript markup from being recognized. I had this
> 
> #+OPTIONS:   H:5 \n:nil @:t ::t |:t ^:nil -:t f:t *:t <:t

^^^^^
> at the top of the buffer. Removing that line seems to get me proper
> HTML markup.

You are explicitly disabling super/subscripts. It would be the same
for latex output.

  reply	other threads:[~2014-05-28 13:42 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-05-28 11:47 Superscript and subscript in HTML? Peter Davis
2014-05-28 12:50 ` Rick Frankel
2014-05-28 13:22   ` Peter Davis
2014-05-28 13:29     ` Rick Frankel
2014-05-28 13:36       ` Peter Davis
2014-05-28 13:42         ` Rick Frankel [this message]
2014-05-28 13:37 ` Nick Dokos

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

  List information: https://www.orgmode.org/

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

  git send-email \
    --in-reply-to=e6b7d52d86b6aa3651529c3f66518550@mail.rickster.com \
    --to=rick@rickster.com \
    --cc=emacs-orgmode@gnu.org \
    --cc=pfd@pfdstudio.com \
    /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 public inbox

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

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).