Hi Gerald,
Ulf Stegemann and myself have been working on improving this
problem. The result of this work is in a special branch on the
git repo, called "new-entity-support".
If you have time, maybe you can check out this branch and test it,
to see if the problem you reported is indeed fixed.
-
Hi Gerald,
I confirm this bug, but I don't have a fix currently. There is a
revamp of the entiies code in the making, but not done yet.
- Carsten
On Feb 26, 2010, at 11:24 AM, Geralt wrote:
Hello,
I think there's at least one bug in the
org-export-latex-treat-backslash-char function, bec
I think I forgot to state the actual problem, cosider the following org-file:
* An example \Rightarrow foobar
some text
The produced LaTeX code is:
% Created 2010-03-02 Tue 12:53
\documentclass[11pt]{article}
\usepackage[utf8]{inputenc}
\usepackage[T1]{fontenc}
\usepackage{graphicx}
\usepackage{
Hi,
it's been a few days and still no response, am I the only one who
thinks there's something wrong with the export of the special entities
preceded by a backslash, like \Rightarrow?
Geralt.
___
Emacs-orgmode mailing list
Please use `Reply All' to
Hello,
I think there's at least one bug in the
org-export-latex-treat-backslash-char function, because it does not
correctly export entries of the org-html-entities variable that have
the form ("Rightarrow" . "⇒"). To render such entities the
function uses (member (list string-after) org-html-enti
Hi, this is not a bug. Org-mode treats laTeX environments as
implicitly literal.
As we have discussed a few days ago here, you can work around it using
#+LaTeX: {}\begin{multicol}[2]
- Carsten
P.S. this is becoming another subject for a FAQ which should cover both
org-special-blocks.el
Remember to cover the basics, that is, what you expected to happen and
what in fact did happen. You don't know how to make a good report? See
http://orgmode.org/manual/Feedback.html#Feedback
Your bug report will be posted to the Org-mode mailing list.
--
Fixed, thanks.
- Carsten
On Nov 20, 2009, at 2:36 PM, Francesco Pizzolante wrote:
Hi,
Exporting multiple references to the same footnote to LaTeX lead to
a wrong
generated code.
The following example:
--8<---cut here---start->8---
* Title
This is my t
Hi,
Exporting multiple references to the same footnote to LaTeX lead to a wrong
generated code.
The following example:
--8<---cut here---start->8---
* Title
This is my text[fn:1:This is my footnote.]. And another one[fn:1].
--8<---cut here---
"Holst Thomas (DS-ET/ECF1)" writes:
> I think I discoverd a bug in LaTeX export. I mark a subtree with C-c @
> and then export it to LaTeX with C-c C-e L.
>
> If the subtree has no further subtrees the LaTeX-file not only contains
> the region, but also the rest of the document to the end.
Fixed
Hello,
I think I discoverd a bug in LaTeX export. I mark a subtree with C-c @
and then export it to LaTeX with C-c C-e L.
If the subtree has no further subtrees the LaTeX-file not only contains
the region, but also the rest of the document to the end.
Here is an example:
,[ test.org ]
| * K
This has already been addressed and should work in the 6.18 release.
- Carsten
On Jan 20, 2009, at 9:32 AM, Thomas Holst wrote:
Hello,
when I call `org-export-region-as-latex' emacs enters a ininite
loop. When I call a HTML export command prior to
`org-export-region-as-latex' everything works
Hello,
when I call `org-export-region-as-latex' emacs enters a ininite
loop. When I call a HTML export command prior to
`org-export-region-as-latex' everything works fine with LaTeX export
commands.
As I found out `org-maybe-keyword-time-regexp' is not set when calling a
LaTeX export command. It
13 matches
Mail list logo
