Commit Graph

218 Commits

Author SHA1 Message Date
Carsten Dominik ff38550278 Allow a dash in the name of a latex document class setup.
A line like    #+LATEX_CLASS: auto-report
will now work.

Report by Nicolas Girad.
2010-04-23 20:57:47 +02:00
Carsten Dominik 43bf1bbbd7 Push version number to 6.35trans 2010-04-15 12:24:55 +02:00
Eric Schulte e26deb647f fixes BUG in `org-export-as-latex' -- was only exporting the body
This bug was introduced in commit

    1b40601ebd

  which sets the body-only option to true when called with a simple
  prefix argument, however it does not check that the prefix argument
  is non-null.

  Thanks to Valentin Wüstholz for reporting this bug
2010-04-11 10:14:21 -06:00
Eric Schulte 1b40601ebd `org-export-as-latex' set the body-only option when called with a simple prefix arg
This can be useful for exporting a small active region (often a
  table) to latex for pasting into an existing latex buffer.
2010-04-09 09:11:43 -06:00
Carsten Dominik 6f3026edf1 Release 6.35g 2010-04-08 20:15:15 +02:00
Carsten Dominik a589c7a22e Release 6.35f 2010-04-08 10:36:32 +02:00
Carsten Dominik 50e5924d8a Release 6.35e 2010-04-07 16:33:52 +02:00
Carsten Dominik f722763f8a Release 6.35d 2010-04-07 16:26:42 +02:00
Carsten Dominik d65ed03be6 Update copyright notices and fix wrong version tags 2010-04-07 16:26:10 +02:00
Carsten Dominik f3a25f4d34 Fix caption processing in LaTeX export 2010-04-07 16:10:28 +02:00
Carsten Dominik 007c7bc64b Allow entities to be terminated by {} 2010-04-07 15:32:31 +02:00
Carsten Dominik cafbe1d038 Release 6.35c 2010-04-07 08:58:25 +02:00
Carsten Dominik b213c0f31e Release 6.35b 2010-04-07 07:54:14 +02:00
Carsten Dominik 08d0d2fa20 Release 6.35 2010-04-06 09:16:36 +02:00
Carsten Dominik fea1742762 Fix typo 2010-04-06 09:15:16 +02:00
Carsten Dominik f2b8c25e7a More details about LaTeX setup 2010-04-05 15:10:22 +02:00
Carsten Dominik 00afe22952 Specify the position where the packages are inserted in the LaTeX header. 2010-04-04 08:37:03 +02:00
Carsten Dominik 8fdf80bb5b Fix whitespace and compiler wanings 2010-04-01 13:11:54 +02:00
Carsten Dominik f813b09747 Add the ChangeLog entries 2010-04-01 12:56:23 +02:00
Carsten Dominik a6544ef711 Collect packages to a variable 2010-04-01 12:44:02 +02:00
Carsten Dominik cc2d79d5ac More bug fixes 2010-04-01 12:44:02 +02:00
Carsten Dominik aa220a1e6a More fixes 2010-04-01 12:44:02 +02:00
Carsten Dominik da556cee82 Implement new and better support for entities 2010-04-01 12:44:01 +02:00
Carsten Dominik 313f01d297 Do some formatting of table and figure captions
Table and figure captions are not fully processed.  Now we at least do
basic formatting, but links and footnotes still do not work.
2010-03-29 07:30:00 +02:00
Carsten Dominik 4892c8899e Implement index generation during export
This new code will search #+INDEX lines in the buffer.  For LaTeX, it
will simple convert these into LaTeX \index{} commands.  For other
backends, it will copy thee entries to a new file, with extension
orgx.  These files can then later be post-processed to create the index.
2010-03-28 09:27:33 +02:00
Carsten Dominik 1d4ee49c91 LaTeX export: Do not mistake table.el borders for strike-through emphasis. 2010-03-24 18:44:25 +01:00
Carsten Dominik 15ec1c56ad LaTeX export: Allow parenthesis before exponent of subscript
Keith writes:

> I noticed something strange and I think it's might be a bug converting
> to tex file. I've been trying to put a special symbol inside a
> bracket, e.g.
>
>  air temperature (degree Celsius)
>
> and the symbol should look like ^{\circ}C in org file. It works well
> if it is standalone. However, when I put the brackets out of it, say
> (^{\circ}C), the pdf output looks bizarre. I have checked the tex
> output and the converting results from orgmode file are
>
>  ^{\circ}C   -->   $^{\circ}$C
>  (^{\circ}C) -->   (^\{\circ}C)
2010-03-24 12:26:50 +01:00
Carsten Dominik 749fc76c2d No extra newline after time planning line 2010-03-19 19:51:58 +01:00
Carsten Dominik b68c61e829 Fix problem with a missing function in XEmacs
`latexenc-coding-system-to-inputenc' does not seem to be available in XEmacs.
2010-03-12 17:29:41 +01:00
Carsten Dominik 2b3cb66d54 LaTeX export: Fix another problem with #+AUTHOR export
Jambunathan K. writes:

> I would like to add the following observation as well -
>
> ---> org input <---
> #+AUTHOR: Jambunathan K\cr\href{mailto:{{{EMAIL}}}}{{{{EMAIL}}}}
>
> ---> actual tex output <---
> \author{Jambunathan K\cr\href{mailto:kjambunathan@gmail.com}\{kjambunathan@gmail.com\}}
>
> The above tex snippet has the effect of getting the "Url Box" wrong.
>
> I was hoping to produce the following line -
> \author{Jambunathan K\cr\href{mailto:kjambunathan@gmail.com}{kjambunathan@gmail.com}}
>
> Generally speaking, macro expansion in author string behaves strangely.
2010-03-12 15:21:41 +01:00
Carsten Dominik 1902dfacbe LaTeX export: Macro processing also in author field 2010-03-09 17:24:31 +01:00
Carsten Dominik 48d4ebeb80 LaTeX export: Add \usepackage{latexsym} to the default packages 2010-03-04 07:36:23 +01:00
Carsten Dominik 85df69a5c0 LaTeX export: Protect examples, even if they look like table.el tables
The recent patch to introduce table.el export in LaTeX forgot to check
protectedness.
2010-03-03 13:26:24 +01:00
Carsten Dominik 1c87de51fc LaTeX export: Fix export of &&
Lukasz Stelman writes:

I've create some presentation on programming (some more to do) and to my
surprise I've discovered that if org-mode escapes one "&" properly it
doesn't do its job in case of "&&" (and a single "^" too). I get "\&&"
in latex file which of course is wrong.
2010-03-03 12:59:26 +01:00
Carsten Dominik 6d1e30828b Re-install the support for table.el tables again.
This support was totally broken.  It works now again.  Unfortunately
it is not possible to edit the table directly in the org-mode buffer
anymore - to edit such a table, you have to use C-c '
2010-02-26 22:33:49 +01:00
Carsten Dominik 045676bcaa LaTeX export: Protect footnotes in headings 2010-02-26 21:02:25 +01:00
Carsten Dominik 26b0824f5a LaTeX export: Protect footnotes in headlines 2010-02-23 07:32:06 +01:00
Carsten Dominik d0b0f776d2 Export: Kill product buffer if it has been displayed directly
Request by Livin Stephen Sharma
2010-02-21 09:19:21 +01:00
Carsten Dominik d2f219fd41 LaTeX export: When exporting to a buffer only, do not require a file name 2010-02-12 08:34:00 +01:00
Carsten Dominik 6a15c45544 Use \providecommand to make sure \alert is defined 2010-02-03 16:13:49 +01:00
Carsten Dominik d7c63f6760 LaTeX export: Make inputenc coding system default to utf8 2010-02-02 06:31:21 +01:00
Carsten Dominik b66858acbb LaTeX export: Define the align macro 2010-02-01 17:15:54 +01:00
Carsten Dominik 04057e2195 LaTeX export: Protect <...> arguments for BEAMER export
Bill Jackson writes:

> When exporting to LaTeX, curly brackets in a command will be escaped
> if that command also contains angle brackets.  This can be a problem
> when using beamer.  An example input file:
>
> ------------------------------------------------------------------------
>
> #+LaTeX_CLASS: beamer
>
> * The One and Only Frame
>  When LaTeX \alert<2>{commands} contain angle brackets, the curly
>  brackets are erroneously escaped in the output.  \alert{Commands}
>  that do not contain angle brackets work properly.
>
> ------------------------------------------------------------------------
>
> Typing C-c C-e l will generate the output file:
>
> ------------------------------------------------------------------------
>
> % Created 2010-01-15 Fri 13:57
> \documentclass{beamer}
> \usepackage[latin1]{inputenc}
> \usepackage[T1]{fontenc}
> \usepackage{graphicx}
> \usepackage{longtable}
> \usepackage{float}
> \usepackage{wrapfig}
> \usepackage{soul}
> \usepackage{amssymb}
> \usepackage{hyperref}
>
>
> \title{escCurly}
> \author{}
> \date{15 January 2010}
>
> \begin{document}
>
> \maketitle
>
> \begin{frame}
> \frametitle{Outline}
> \setcounter{tocdepth}{3}
> \tableofcontents
> \end{frame}
>
> \begin{frame}
> \frametitle{The One and Only Frame}
> \label{sec-1}
>
>  When \LaTeX{} \alert<2>\{commands\} contain angle brackets, the curly
>  brackets are erroneously escaped in the output.  \alert{Commands}
>  that do not contain angle brackets work properly.
> \end{frame}
>
> \end{document}
2010-01-28 15:50:20 +01:00
Carsten Dominik 4ba2cb0860 Improve LaTeX export of the words LaTeX and TeX
Bill Jackson writes:

> 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}
2010-01-28 15:29:35 +01:00
Carsten Dominik 0618d821cf LaTeX export: Set coding system only if the class specifies AUTO for it
The coding system of the LaTeX class will now only be set to the value
corresponding to the buffer's file coding system if the class
specifies \usepackage[AUTO]{inputenc}.  Any other value for the coding
system will not be modified.
2010-01-24 18:09:33 +01:00
Carsten Dominik 2e53d9b137 Remove comma after means in many docstrings
Stephen Eglen says these commas should not be there.
2010-01-21 16:15:40 +01:00
Carsten Dominik cae0c63c48 Make hyperref macro customizable
This was a request by Martin G. Skjaeveland
2010-01-20 10:27:45 +01:00
Carsten Dominik 06e74afce3 Version number to 6.34trans 2010-01-20 10:13:21 +01:00
Carsten Dominik a1709ba641 Release 6.34c 2010-01-18 00:10:11 +01:00
Carsten Dominik 8fd14ae648 LaTeX export: Fix another protection bug, this time the char before a "\" 2010-01-15 08:05:22 +01:00