Commit Graph

388 Commits

Author SHA1 Message Date
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