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:29:44 -0400	[thread overview]
Message-ID: <8d8b01598d277ad77f2d4081ded6e199@mail.rickster.com> (raw)
In-Reply-To: <20140528132220.GA2600@pfdstudio-air.home>

On 2014-05-28 09:22, Peter Davis wrote:
> On Wed, May 28, 2014 at 08:50:20AM -0400, Rick Frankel wrote:
> On 2014-05-28 07:47, Peter Davis wrote:
> >Is there any markup which will let me get superscripts and subscripts
> >in HTML export?
> >
> >It would be great if the HTML exporter recognized ^{...} and _{...} so
> >the same markup would work for both LaTeX/PDF and for HTML.
> 
> It does for me. I believe it always has. Are you sure your options are
> set correctly? Also, are you sure that the html source doesn't contain
> <sup/> and <sub/> tags that aren't being styled?
> 
> Here's a example and the output
> 
> #+BEGIN_SRC org
> ,#+OPTIONS: toc:nil
> ,* Super and subscript
> this is a super^{1} script. and a sub_{2} script.
> 
> another super^3 and another sub_4
> #+END_SRC
> 
> and the results (C-c C-e C-b h H)
> 
> #+BEGIN_EXAMPLE
> <div id="outline-container-sec-1" class="outline-2">
> <h2 id="sec-1">Super and subscript</h2>
> <div class="outline-text-2" id="text-1">
> <p>
> this is a super<sup>1</sup> script. and a sub<sub>2</sub> script.
> </p>
> 
> <p>
> another super<sup>3</sup> and another sub<sub>4</sub></p>
> </div>
> </div>
> 
> #+END_EXAMPLE
> 
> 
> Here's what I get for the body, using your example:
> 
> +==========
> <div class="org-src-container">
> 
> <pre class="src src-org"><span style="color: #b22222;">#+OPTIONS: 
> toc:nil</span>
> <span style="color: #0000ff;">* Super and subscript</span>
> this is a super^{1} script. and a sub_{2} script.
> 
> another super^3 and another sub_4
> </pre>
> </div>
> +==========
> 
> Leaving out the #+BEGIN_SRC/#+END_SRC doesn't work either. This is
> with emacs 24.3.3, org-mode 8.2.5g

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.

1. Create a new org mode buffer.
2. Copy the contents WITHIN the begin/end src block to the buffer.
3. Remove the leading commas (,).
4. With your cursor on the #+OPTION line type [C-c C-c].
5. Generate the html output.

If it still doesn't work edit the file with:

emacs -Q -L<path to org 8.2.5g> mytest.org

and try again.

rick

  reply	other threads:[~2014-05-28 13:29 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 [this message]
2014-05-28 13:36       ` Peter Davis
2014-05-28 13:42         ` Rick Frankel
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=8d8b01598d277ad77f2d4081ded6e199@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).