emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Carsten Dominik <carsten.dominik@gmail.com>
To: Bill Jackson <wj2@jacksonhost.com>
Cc: emacs-orgmode@gnu.org
Subject: Re: Bug: Inconsistency exporting \LaTeX and \TeX [6.34a]
Date: Thu, 28 Jan 2010 15:30:09 +0100	[thread overview]
Message-ID: <ACD6F1D4-1D83-43D4-A7F3-E21875764C5F@gmail.com> (raw)
In-Reply-To: <4B50E909.8000801@jacksonhost.com>

Hi Bill,

thanks for noticing this inconsistency - it is now fixed.

- Carsten

On Jan 15, 2010, at 11:15 PM, Bill Jackson wrote:

> When exporting to LaTeX, the commands \LaTeX and \TeX are not
> processed consistently.  In particular, the backslash for \LaTeX is
> escaped.  This might not be a bug, but it is a bit confusing.  An
> example input file:
>
> ------------------------------------------------------------------------
>
> * The One and Only Header
>  The command \LaTeX generates an escaped backslash, while \TeX and
>  \alpha do not.  Note that LaTeX is converted to a command, while TeX
>  is not.
>
> ------------------------------------------------------------------------
>
> Typing C-c C-e l will generate the output file:
>
> ------------------------------------------------------------------------
>
> % Created 2010-01-15 Fri 13:47
> \documentclass[11pt]{article}
> \usepackage[latin1]{inputenc}
> \usepackage[T1]{fontenc}
> \usepackage{graphicx}
> \usepackage{longtable}
> \usepackage{float}
> \usepackage{wrapfig}
> \usepackage{soul}
> \usepackage{amssymb}
> \usepackage{hyperref}
>
>
> \title{escLaTeX}
> \author{}
> \date{15 January 2010}
>
> \begin{document}
>
> \maketitle
>
> \setcounter{tocdepth}{3}
> \tableofcontents
> \vspace*{1cm}
> \section{The One and Only Header}
> \label{sec-1}
>
>  The command \\LaTeX{} generates an escaped backslash, while \TeX and
>  $\alpha$ do not.  Note that \LaTeX{} is converted to a command,  
> while TeX
>  is not.
>
> \end{document}
>
> ------------------------------------------------------------------------
>
>
> Emacs  : GNU Emacs 23.1.1 (i386-mingw-nt5.1.2600)
> of 2009-07-29 on SOFT-MJASON
> Package: Org-mode version 6.34a
>
> current state:
> ==============
> (setq
> org-export-latex-after-initial-vars-hook '(org-beamer-after-initial- 
> vars)
> org-after-todo-state-change-hook '(org-clock-out-if-current)
> org-export-latex-format-toc-function 'org-export-latex-format-toc- 
> default
> org-export-preprocess-hook '(org-export-blocks-preprocess)
> org-tab-first-hook '(org-hide-block-toggle-maybe)
> org-src-mode-hook '(org-src-mode-configure-edit-buffer)
> org-confirm-shell-link-function 'yes-or-no-p
> org-export-first-hook '(org-beamer-initialize-open-trackers)
> org-agenda-before-write-hook '(org-agenda-add-entry-text)
> org-directory "O:/org"
> org-cycle-hook '(org-cycle-hide-archived-subtrees org-cycle-hide- 
> drawers
>          org-cycle-show-empty-lines
>          org-optimize-window-after-visibility-change)
> org-export-preprocess-before-normalizing-links-hook '(org-remove- 
> file-link-modifiers)
> org-mode-hook '(#[nil "\300\301\302\303\304$\207"
>           [org-add-hook change-major-mode-hook org-show-block-all
>            append local]
>           5]
>         )
> org-confirm-elisp-link-function 'yes-or-no-p
> org-occur-hook '(org-first-headline-recenter)
> org-export-preprocess-before-selecting-backend-code-hook '(org- 
> beamer-select-beamer-code)
> org-export-latex-final-hook '(org-beamer-amend-header org-beamer-fix- 
> toc
>                   org-beamer-auto-fragile-frames
>                   org-beamer-place-default-actions-for-lists)
> )
>
>
> _______________________________________________
> 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

- Carsten

      reply	other threads:[~2010-01-28 14:30 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-01-15 22:15 Bug: Inconsistency exporting \LaTeX and \TeX [6.34a] Bill Jackson
2010-01-28 14:30 ` Carsten Dominik [this message]

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=ACD6F1D4-1D83-43D4-A7F3-E21875764C5F@gmail.com \
    --to=carsten.dominik@gmail.com \
    --cc=emacs-orgmode@gnu.org \
    --cc=wj2@jacksonhost.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).