Commit Graph

191 Commits

Author SHA1 Message Date
Carsten Dominik a81e918325 New hook `org-export-latex-final-hook'. 2009-09-29 05:01:56 +02:00
Carsten Dominik 7d5408a717 LaTeX export: Fix superscript bug
Thomas S. Dye writes:

> I'm trying to generate $^{14}$C, or an equivalent, from org-mode
> to represent the isotope of carbon important in archaeological
> dating.
>
> Reading the manual, I tried this:
>
> ** A Brief History of Attempts to Interpret the ^{14}C Dates
> *** The ^{14}C Dates
>
> Which, in my #+LaTeX_CLASS: beamer export, yields
>
> \subsection{A Brief History of Attempts to Interpret the \^{}{14}C Dates}
> ...
> \begin{frame}\frametitle{The \^{}{14}C Dates}
>
> The problem seems to be the space before the ^.
>
> This input:
>
> ** A Brief History of Attempts to Interpret the x^{14}C Dates
> *** The x^{14}C Dates
>
> yields the correct LaTeX:
>
> \subsection{A Brief History of Attempts to Interpret the x$^{\mathrm{14}}$C Dates}
> ...
> \begin{frame}\frametitle{The x$^{\mathrm{14}}$C Dates}
>
> Am I missing something?  Or, is the LaTeX export thrown off by
> the space before ^?

Indeed, a space before the caret was not allowed in LaTeX export
2009-09-29 04:40:01 +02:00
Carsten Dominik 201517106c LaTeX export: Fix bug with empty lines in VERSE environment 2009-09-28 20:08:34 +01:00
Carsten Dominik c950e4b3ac Fix backslash and other special characters in verbatim snippets
Jeff Kowalczyk writes:

> Is there a way to escape backslashes (\) in code and verbatim that
> will export to LaTeX correctly?
>
> When writing =\\host\share= or =C:\path\to=, pdftolatex output is
> incorrect.
2009-09-24 10:02:00 +01:00
Carsten Dominik 317ea8bf9d Amend Bastiens fix in 3bc997fe8f
This fix did create a new problem with exporting selected subtrees.
I hope it works now.
2009-09-10 22:37:49 +02:00
Carsten Dominik 97ecc2c180 LaTeX export: Fix bug with accidental multiline protection in comments 2009-09-06 07:54:31 +02:00
Carsten Dominik 291a6db848 Release number back to 6.30trans 2009-09-04 10:39:01 +02:00
Carsten Dominik 12ab55ca43 Release 6.30d 2009-09-03 13:53:46 +02:00
Carsten Dominik adfa87282d Push version number to 6.30trans 2009-09-03 08:10:36 +02:00
Carsten Dominik 63e1714288 Release 6.30c 2009-09-02 14:40:56 +02:00
Carsten Dominik fc332703bf Release 6.30b 2009-09-02 11:33:10 +02:00
Carsten Dominik 1d04b205e6 Release 6.30a 2009-09-02 09:00:23 +02:00
Carsten Dominik db70cdb13b Release 6.30 2009-09-01 06:09:23 +02:00
Carsten Dominik cf67ad2bf7 Cleanup after buggy commit aedef8c804 2009-08-31 21:21:03 +02:00
Carsten Dominik aedef8c804 LaTeX export: Protect ampersands in tables 2009-08-31 14:27:28 +02:00
Carsten Dominik c46cd15045 Keep byte compiler happy 2009-08-31 12:19:56 +02:00
Bastien Guerry 3bc997fe8f org-latex.el: bugfix about exporting first lines with no heading.
org-export-latex-first-lines was confused when there was no
heading after the first headlines.  This patch fixes this.
2009-08-30 19:10:06 +08:00
Carsten Dominik 8a0ae0d3e5 LaTeX export: Fix bug with longtable export.
Karl Stump writes:

> When exporting a table with a horizontal line the column count is wrong.
>
> Output from pdflatex run:
>
> ! Extra alignment tab has been changed to \cr.
> <template> \endtemplate
>
> l.32 ....\multicolumn{4}{r}{Continued on next page}
>                                                   \
> ?
>
> Here's the table in the tex file:
>
> \begin{longtable}{||lll||}
> \caption{This is a long table with lines around and between cells}\\
>  Heading1  &  Heading2  &  Heading3 \\
> \hline
> \endhead
> \hline\multicolumn{4}{r}{Continued on next page}\
> \endfoot
> \endlastfoot
> \hline
>  alpha     &  beta      &  gamma     \\
>            &            &            \\
> \end{longtable}
>
> Here's the org file:
>
> ** table export test
>
> #+CAPTION: This is a long table with lines around and between cells
> #+LATEX_HEADER: \usepackage[landscape]{geometry}
> #+LATEX_HEADER: \geometry{left=0.12in,right=0.12in,top=0.25in,bottom=0.25in}
> #+ATTR_LaTeX: longtable align=||lll||
>
>     | / | <30>     | <10>     | <10>     |
>     |   | Heading1 | Heading2 | Heading3 |
>     |---+----------+----------+----------|
>     |   | alpha    | beta     | gamma    |
>     |   |          |          |          |

Nick Dokos replies:

> I believe it's because of the dummy "calculation-mark" column,
> which is not exported. However, the variable org-table-last-alignment
> (a list, whose length becomes the value of the \multicolumn argument)
> ends up having the value (nil nil nil nil), i.e. it counts the dummy
> column as well. What the proper place to adjust the value is, I don't
> know, but it should be easy for Carsten to fix it. For the time being,
> you can either get rid of the dummy row and column (e.g. if you don't
> need the widths) or fix it by hand in the LaTeX file.

Indeed, and this commit pops `org-table-last-alignment' if the first
column has been removed by `org-table-clean-before-export'.  The same
problem must have caused a one-off error when setting the alignment in
LaTeX tables, bu it seems nobody has noticed this so far.  Anyway,
also this is fixed now.
2009-08-29 07:22:33 +02:00
Carsten Dominik 44bb3134d0 Revert "LaTeX export: Fix problem with emphasis in quotes"
This reverts commit 0ba7d3d2f9.

Conflicts:

	lisp/ChangeLog
2009-08-27 10:29:04 +02:00
Carsten Dominik 0a7e8ab221 LaTeX export: Modify the structure of the listings name option.
The variable `org-export-latex-listings-langs' is now an alist.
2009-08-23 19:11:12 +02:00
Carsten Dominik 0ba7d3d2f9 LaTeX export: Fix problem with emphasis in quotes 2009-08-18 07:45:35 +01:00
Carsten Dominik dec80f2451 LaTeX export: Add support for +strike-through+ emphasis 2009-08-18 07:28:03 +01:00
Carsten Dominik f7e208da37 Make latex preview also use the packages in `org-export-latex-packages-alist'. 2009-08-16 09:38:03 +02:00
Carsten Dominik 5b7ea02286 Fix typos
Thanks to Nick Dokos.
2009-08-12 10:19:57 +02:00
Carsten Dominik 1d18043506 LaTeX export: Add more languages for source code publishing 2009-08-11 15:45:10 +02:00
Carsten Dominik 59370b6a83 LaTeX export: Remove bug in table export.
A `save-excursion' around a call to org-table-align make point end up
*before* the table.  The reason is that a table align replaces the
entire table, including the newline before it.  When the table is
removed in order to be replaced, the marker created by
`save-excursion' slips.  `org-table-align' has it's own, built-in
`save-excursion' by remembering the line and column where the cursor
was before the align.
2009-08-11 07:51:12 +02:00
Carsten Dominik c5783bd8bd LaTeX export: Allow export using the listings package
Patch by Eric Schulte, see

http://thread.gmane.org/gmane.emacs.orgmode/16269
2009-08-09 14:51:09 +02:00
Carsten Dominik bfdd3d3fd3 Push version number to 6.29trans 2009-08-06 12:07:20 +02:00
Carsten Dominik 0864163024 Release 6.29c 2009-08-06 06:26:23 +02:00
Carsten Dominik 8eba33958f LaTeX export: Fix export problems when exporting a region
Dan Griswold writes:

> Hi there,
>
> Well, I think this a bug.
>
> Given this org input file:
>
> ,----
> | * Things
> | ** A Heading
> |    - some
> |    - stuff
> |    - in
> |    - a
> |    - list
> | ** Another heading
> |    - another
> |    - list
> `----
>
> then if I select the level one heading (titled "Things")
> with C-c @, and export to LaTeX using C-c C-e l, I get this
> output:
>
> ,----
> | % Created 2009-07-29 Wed 20:24
> | \documentclass[12pt]{article}
> | \usepackage[utf8]{inputenc}
> | \usepackage[T1]{fontenc}
> | \usepackage{graphicx}
> | \usepackage{longtable}
> | \usepackage{hyperref}
> |
> |
> | \title{Things}
> | \author{Daniel M. Griswold}
> | \date{July 29, 2009}
> |
> | \begin{document}
> |
> | \maketitle
> |
> | ** A Heading
> | \begin{itemize}
> | \item some
> | \item stuff
> | \item in
> | \item a
> | \item list
> | \end{itemize}
> | ** Another heading
> | \begin{itemize}
> | \item another
> | \item list
> | \end{itemize}
> |
> | \end{document}
> `----
>
> Note that the top level headings ("A Heading" and "Another
> Heading") are not exported as \section, but with the
> asterisks they have in the org file:
>
> ,----
> | ** A Heading
> | \begin{itemize}
> |
> |   ... snip ...
> |
> | \end{itemize}
> | ** Another heading
> `----
>
> Exporting the whole file does what it's supposed to do:
> export the headlines as \section and \subsection.

This commit fixes the issue.
2009-08-05 18:18:35 +02:00
Carsten Dominik d6b37ddbea Release 6.29b 2009-08-05 12:34:30 +02:00
Carsten Dominik 1c25048e48 Release 6.29a 2009-08-04 23:54:22 +02:00
Carsten Dominik d67a9be8a2 Release 6.29 2009-08-04 23:06:39 +02:00
Carsten Dominik 2eecb4c43c Fix white-space errors 2009-08-03 17:30:30 +02:00
Carsten Dominik 4249cbf454 Merge branch 'master' of git+ssh://repo.or.cz/srv/git/org-mode
Conflicts:
	lisp/ChangeLog
2009-08-01 11:44:55 +02:00
Carsten Dominik 6677f745cc LaTeX export: Skip title command when there is no title
Using "#+TITLE:" without a value make the LaTeX export ignore the
value of org-export-latex-title-command.
2009-07-27 08:45:02 +02:00
Bastien Guerry fe4967229a Fix problem when publishing the region to LaTeX.
`org-export-latex-first-lines' was rather stupid and would
discard the end of the region with the region was active.
Thanks to Holst Thomas for this bug report.
2009-07-16 21:39:37 +02:00
Carsten Dominik b62e7fc5a0 Fix problems with sub and superscript in LaTeX export 2009-07-09 06:29:51 +02:00
Carsten Dominik c1d00fa463 Export: General mechanism for local settings
Many different people want to set many different variables in a
buffer-local way for export.  This cannot be done with file variables,
because the Org buffer is not current while the exporter is running.

Lots of variables can be set with the #+OPTIONS lines, but finding
abbreviations goes only so far.

Therefore we have now a general mechanism that can be used to bind
variables during export operations.

a line like:   #+BIND: variable value

will bind the variable to value.  For example,
the line

>>      #+OPTIONS: toc:nil

can now equivalently be written as

>>      #+BIND: org-export-with-toc nil
2009-07-06 17:00:03 +02:00
Carsten Dominik 7a73b81208 Fix parenthesis in org-latex.el 2009-07-02 23:09:34 +02:00
Carsten Dominik b85b2e1f19 LaTeX export: Avoid infinite loop when environment is not closed 2009-07-02 13:31:28 +02:00
Carsten Dominik ddf013644a LaTeX export: Fix problem with internal links 2009-07-02 09:54:33 +02:00
Carsten Dominik 483463d18f LaTeX export: Fix problem with quotation marks 2009-07-02 09:53:25 +02:00
Carsten Dominik 3d2b4d98c1 LaTeX export: Allow postscript extensions for images
Some propel process LaTeX filed not directly to pdf, but go
through dvi and then to ps or pdf.  In that case, allowed images
are ps and eps files, not pdf and jpg.

This commit adds the two extensions, so that export using that
alternative path can be supported better.  However, it is up to the
user to make sure that the images are actually compatible with the
backend.
2009-06-28 13:00:37 +02:00
Carsten Dominik 590a339f99 LaTeX export: Allow a user-defined environment for low-level headings
See the variable `org-export-latex-low-levels'.
2009-06-26 17:35:13 +02:00
Carsten Dominik f648323253 Push version number to 6.28trans 2009-06-26 17:26:50 +02:00
Carsten Dominik cd4e52a5ef Release 6.28d 2009-06-26 17:23:27 +02:00
Carsten Dominik 9f91de32e9 Bug fixes:
Make PDF export work on windows.
Use only compatible overlay API.
2009-06-26 13:09:40 +02:00
Carsten Dominik 00ddc4dba7 Release 6.28c 2009-06-26 09:27:50 +02:00
Carsten Dominik e7ffcc1d4d Release 6.28b 2009-06-25 09:01:20 +02:00
Carsten Dominik 7906427aa6 Release 6.28 2009-06-25 08:59:59 +02:00
Carsten Dominik 56cf00c9bc LaTeX export: Fix problem with image names containing underscore
Reported by Arne Freyberger.
2009-06-23 06:15:01 +02:00
Carsten Dominik e23665ee66 LaTeX export: Make the verbatim environment configurable 2009-06-18 09:30:00 +02:00
Carsten Dominik d1f1e63d22 Keep byte compiler happy 2009-06-11 22:18:47 +02:00
Carsten Dominik 7d20a088f5 Minor fixes 2009-06-09 12:10:27 +02:00
Carsten Dominik d27d3e5fa6 LaTeX export: Fix problems with use of \verb in headlines
See http://article.gmane.org/gmane.emacs.orgmode/14257
2009-06-09 06:26:59 +02:00
Carsten Dominik 379b24cc63 Fix whitespace issues 2009-06-08 08:00:46 +02:00
Carsten Dominik 8a9e604a7a New indentation treatment for blocks during export
Now we also deal with center, quote, and verse blocks.
2009-06-07 16:11:14 +02:00
Carsten Dominik 22d5daa11a Respect [TABLE-OF-CONTENTS] also for LaTeX export
Reported by Yuva.
2009-06-04 16:52:02 +02:00
Carsten Dominik 1db461321a Keep compiler happy 2009-06-02 14:49:38 +02:00
Carsten Dominik 3d1ff31b60 LaTeX export: Fix \nbsp, 2nd attempt 2009-05-26 17:04:10 +02:00
Carsten Dominik 7ab9c52c3d Revert "LaTeX export: Fix interpretation of \nbsp"
This reverts commit e85508d5cf.
2009-05-26 16:47:38 +02:00
Carsten Dominik ae7b8f6b12 Push version number to 6.27trans 2009-05-26 15:41:44 +02:00
Carsten Dominik e85508d5cf LaTeX export: Fix interpretation of \nbsp
Reported by Chris Gray.
2009-05-26 15:40:26 +02:00
Carsten Dominik 0421dead4b Release 6.27a 2009-05-25 16:04:45 +02:00
Carsten Dominik b681c7b26e Release 6.27 2009-05-23 08:22:04 +02:00
Carsten Dominik 6d406766df LaTeX export: Fix bug when exporting a region
Exporting a region to LaTeX did not recognize section header
correctly.  Fixed now.
2009-05-23 08:13:05 +02:00
Carsten Dominik db839f4f03 LaTeX export: Fix a variable definition 2009-05-21 18:01:08 +02:00
Carsten Dominik 91f77d7029 Export: Make all export commands push the result to the kill ring
All export commands now push the result to the kill ring by default.
This is subject to the variable `org-export-push-to-kill-ring'.

Also, this commit adds a new variable
`org-export-show-temporary-export-buffer' which can be used to turn
off the display of the temporary buffer containing the exported text.
Since this stuff is now automatically pushed onto the kill ring, some
people might prefer not to see this buffer.
2009-05-21 09:14:33 +02:00
Carsten Dominik d80faba613 Fix docstring of export functions: HIDDEN parameter is obsolete 2009-05-19 08:09:30 +02:00
Carsten Dominik cc440f8529 LaTeX export: Fix bug in removal of TODO keywords
There was a problem that not in all cases the correct regexp was used
to find TODO keywords.
2009-05-14 10:20:04 +02:00
Carsten Dominik 80fb1b566a LaTeX export: Allow uncentered tables 2009-05-14 09:33:07 +02:00
Carsten Dominik 90204fe238 LaTeX export: Make TODO keyword markup configurable 2009-05-12 12:27:56 +02:00
Carsten Dominik d79696d914 Export: org-export-latex-image-default-option can be buffer-local
Jason Riedy writes:

>  I'm trying to change org-export-latex-image-default-option
>  to "width=.7\\linewidth" in a file local variable.  It's set
>  correctly as a buffer local variable, and it's having no
>  effect on the export.  My guess is that the buffer-local
>  property is stopping it as soon as org-export-as-latex runs
>  set-buffer.
>
>  I can smuggle the value in by adding an entry to org-export-plist-vars
>  referring to org-export-latex-image-default-option and pulling the value
>  from the plist, but that feels incorrect.

It is actually the correct way to do this, and I have
implemented this change.
2009-05-05 10:22:37 +02:00
Carsten Dominik 398f5dd2dd Fix typos 2009-05-04 22:26:41 +02:00
Carsten Dominik 52a8783d1d LaTeX export: Fix bugs with exporting the region
Matt Lundin writes:

>  When I select a region and invoke
>  org-replace-region-by-latex, the region is removed, but no
>  latex output is put in its place. In other words, the region
>  is simply deleted.
>
>  Strangely, if I select multiple headlines, they are
>  converted to latex.  But if I select only text underneath a
>  headline, it is not replaced.

This is hopefully fixed now.
2009-05-04 07:46:46 +02:00
Carsten Dominik e726cc46e0 Fix typo 2009-05-03 20:47:04 +02:00
Carsten Dominik abc874cefc Export: New hooks for Chris Gray's LaTeX/HTML blocks
Chris Gray had the idea to have arbitrary blocks turned in LaTeX
environments and HTML divs.  These three new hooks allow
implementation has an add-on rather than a patch.
2009-05-02 09:24:28 +02:00
Carsten Dominik 5f86fd7ae2 LaTeX export: Protect eqnarray* and similar environments.
Environment names ending in a star were not properly protected.  Now
they are.
2009-04-29 21:36:28 +02:00
Carsten Dominik ff07d933ea PDF export: Make processing commands configurable 2009-04-23 06:39:59 +02:00
Carsten Dominik 69e6d249aa Push version number to 6.26trans 2009-04-22 09:08:13 +02:00
Carsten Dominik 73854f435d Release 6.26d 2009-04-22 06:42:17 +02:00
Carsten Dominik 595e9603ac Release 6.26c 2009-04-21 20:26:27 +02:00
Carsten Dominik e0cd12716a Release 6.26b 2009-04-21 10:21:36 +02:00
Carsten Dominik b8a5f1a7fc Release 6.26a 2009-04-19 22:31:36 +02:00
Carsten Dominik ba66d2c8ae Release 6.26 2009-04-19 08:38:49 +02:00
Carsten Dominik 6316b53c46 LaTeX export: Fix bugs with timestamp export.
The formatting of timestamp keywords was wrong.
2009-04-19 07:46:54 +02:00
Carsten Dominik c6fd49726f LaTeX export: Fix some problems with protection of inline latex commands
Scot Becker writes:

>  Prompted by Chris Gray's request for org markup in Latex
>  environment, I thought I'd submit a note (for his sake and
>  others') about a few quirks of org-latex-export's handling
>  of embedded Latex markup in org documents.  I have been
>  puzzling with these for a while but only discovered the
>  problem triggers (and workarounds) this morning just before
>  Chris' mail arrived.  These are both about inline Latex
>  commands:
>
>  I use a few custom commands \mycommand{like this}, and
>  occasionally have to invoke the odd bit of standard LaTeX
>  markup, for example /when \textbf{embedding bold text}
>  inside italics/.  For the most part, these work fine, but
>  I've discovered the following two 'gotchas' that happen when
>  exporting to LaTeX.
>
>  1.  Inline Latex commands get their final curly brace
>  escaped with a slash (and therefore don't work) if they
>  spill over into another line, i.e. if they contain one or
>  more newlines.  This is true also for standard LaTeX
>  commands like \textbf{} and \emph{}.
>
>  ----------------SAMPLE------------------------
>  \mycommand{So, for example this
>  wrapped setence gets a slash added just after the
>  final period and before the curly brace.}  Org is quite
>  helpfully escaping the slash for LaTeX, apparently.
>
>  \mycommand{no trouble if it's all on one line}
>  ------------------END-------------------------
>
>  The workaround of putting all such commands on one line is
>  no hardship for me, since I use visual-line-mode in Emacs 23
>  and keep my paragraphs as single logical lines.  It might be
>  harder for those accustomed to hard-wrapping their
>  paragraphs.
>
>
>  2.  If you have two inline Latex commands on the same
>  logical line, org's latex export doesn't treat the text
>  between them in its usual manner.  Italics get processed,
>  but not the latexification of quotes.  ("this" --> ``this'')
>  For example:
>
>  ----------------SAMPLE------------------------
>  I have a short custom command to tell Latex to invoke a
>  Hebrew-language right-to-left environment when I want to refer to a
>  Hebrew phrase like this: \heb{phrase here}.  But then if I "quote
>  something,"  and follow that by another \heb{phrase}, the inner
>  quotation marks don't get processed.  Oddly enough, this problem is
>  only triggered when there is an inline Latex command both before and
>  after the  quoted material on the same logical line.
>
>  Now if you put a footnote in between those two inline Latex commands,
>  the output is really nutty:
>
>  And \heb{phrase here} with a footnote[fn:: Footnote here.]  I'm not
>  sure what funky org commands get invoked, but again, only when
>  bookended by an inline Latex command like \heb{phrase here}.
>  ------------------END-------------------------
>
>  The nutty output is a number in square brackets like
>  this[1], with the following at the bottom of the document:
>
>  \$\^{}{1}\$ Footnote here.
>
>  This has a the opposite work-around: break the lines so
>  those elements are not all on the same logical line. Put in
>  a few newlines.  Latex, of course doesn't care.  Do take
>  care not to start a newline with the org-footnote, like this
>  [fn:: Org doesn't parse a footnote command which starts on
>  its own line.]
>
>  This is just "for what it's worth" to those who use org-mode
>  as a front-end to writing for LaTeX.

These problems were caused by a regular expression for
matching latex macros with arguments, that did not allow any
newlines.  Now we have a much better regexp, that even
allows for three levels of nested braces.
2009-04-16 14:17:51 +02:00
Carsten Dominik 1bc9b1e302 LaTeX export: Fix regexp bug.
Report and patch by Baoqiu Cui
2009-04-15 08:34:31 +02:00
Carsten Dominik a26f9b5502 LaTeX export: Format time stamps
Time stamps in LaTeX export now also honor custom time stamp formats.
Furthermore, the new option `org-export-latex-timestamp-markup' can
specify special markup for time stamps.
2009-04-13 08:53:58 +02:00
Carsten Dominik 7887f9d5e5 Rename org-export-latex.el to org-latex.el
For consistency, this file gets a new name.
2009-04-09 17:25:44 +02:00