emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Carsten Dominik <carsten.dominik@gmail.com>
To: Dan Davison <davison@stats.ox.ac.uk>
Cc: emacs org-mode mailing list <emacs-orgmode@gnu.org>
Subject: Re: [BUG] latex superscript and documentation bugs
Date: Wed, 28 Apr 2010 17:22:03 +0200	[thread overview]
Message-ID: <86924F51-29C4-4E07-9E0F-A0190BF84347@gmail.com> (raw)
In-Reply-To: <8739yge6ml.fsf@stats.ox.ac.uk>


On Apr 28, 2010, at 2:57 AM, Dan Davison wrote:

> Org:
> x^{(0)}
>
> becomes [note missing parenthesis]
>
> LaTeX:
> x$^{\mathrm{(0}}$

This is now fixed.

>
> (Emacs 24 with Org 6.35i and also with current Org-mode HEAD)
>
> Also, two possible documentation bugs:
>
> 1
> =============================
>
> http://orgmode.org/manual/Images-and-tables.html#Images-and-tables
>
> says
>
>    You can use the following lines somewhere before the table to  
> assign
>    a caption and a label for cross references, and in the text you can
>    refer to the object with \ref{tab:basic-data}:
>
> I think that is a LaTeX-specific comment in a non-LaTeX specific  
> manual
> section? Should it say "and if exporting to LaTeX, in the text you can
> refer to the object..."?

No, this works also in HTML.  It should, anyway.

>
>
>
> 2
> ==============================
>
> In the docstring for org-export-latex-classes it says
>
>    So a header like
>
>      \documentclass{article}
>      [NO-DEFAULT-PACKAGES]
>      [EXTRA]
>      \providecommand{\alert}[1]{\textbf{#1}}
>      [PACKAGES]
>
>    will omit the default packages,
>
> I wonder whether it would be better to show the double backslashes (\ 
> \)
> explicitly, seeing as the user will need to escape them in this way,  
> or
> at least to warn the reader.

You can add a warning - but this depends on whether you use customize  
or not to edit the variable.

- Carsten

  reply	other threads:[~2010-04-28 15:22 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-04-28  0:57 [BUG] latex superscript and documentation bugs Dan Davison
2010-04-28 15:22 ` Carsten Dominik [this message]
2010-04-28 19:00   ` Dan Davison

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=86924F51-29C4-4E07-9E0F-A0190BF84347@gmail.com \
    --to=carsten.dominik@gmail.com \
    --cc=davison@stats.ox.ac.uk \
    --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 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).