Hello,
t...@tsdye.com (Thomas S. Dye) writes:
With a recent Org from git and this source:
#+attr_latex: :width 0.8\textwidth :placement [htb]
#+name: fig:harris-errors
#+caption[Structural effects of false transitives]: Structural effects of
false transitives with the stratigraphic
Aloha Nicolas,
Nicolas Goaziou m...@nicolasgoaziou.fr writes:
Hello,
t...@tsdye.com (Thomas S. Dye) writes:
With a recent Org from git and this source:
#+attr_latex: :width 0.8\textwidth :placement [htb]
#+name: fig:harris-errors
#+caption[Structural effects of false transitives]:
Aloha all,
With a recent Org from git and this source:
#+attr_latex: :width 0.8\textwidth :placement [htb]
#+name: fig:harris-errors
#+caption[Structural effects of false transitives]: Structural effects of
false transitives with the stratigraphic section in Figure [[fig:fig12-open]]:
Hello,
t...@tsdye.com (Thomas S. Dye) writes:
I'm having a problem with exporting quotes. I have the #+OPTIONS ':t.
This input in the Org mode file:
[l]ater walls ...
produces this in the tex file (open quote wrong, close quote OK):
[l]ater walls ...''
I'm expecting this in the tex
Aloha Nicolas,
Nicolas Goaziou n.goaz...@gmail.com writes:
Hello,
t...@tsdye.com (Thomas S. Dye) writes:
I'm having a problem with exporting quotes. I have the #+OPTIONS ':t.
This input in the Org mode file:
[l]ater walls ...
produces this in the tex file (open quote wrong, close
t...@tsdye.com (Thomas S. Dye) writes:
I'm getting the same incorrect result as before with:
Org-mode version 8.2.4 (release_8.2.4-391-g954168 @
/Users/dk/.emacs.d/src/org-mode/lisp/)
Did you reload Org? I cannot reproduce the problem anymore.
Nevertheless, there will always be failing
Nicolas Goaziou n.goaz...@gmail.com writes:
t...@tsdye.com (Thomas S. Dye) writes:
I'm getting the same incorrect result as before with:
Org-mode version 8.2.4 (release_8.2.4-391-g954168 @
/Users/dk/.emacs.d/src/org-mode/lisp/)
Did you reload Org? I cannot reproduce the problem anymore.
Aloha Nicolas,
Ah, I see what's happening now. I've set up asynchronous export to use
the Org mode that ships with Emacs, rather than the one from the git
repo. Of course, that doesn't track your changes.
In this case, where many potential users of my reproducible research
document aren't using
Aloha all,
I'm having a problem with exporting quotes. I have the #+OPTIONS ':t.
This input in the Org mode file:
[l]ater walls ...
produces this in the tex file (open quote wrong, close quote OK):
[l]ater walls ...''
I'm expecting this in the tex file:
''[l]ater walls ...''
I'm using
Hello,
Alexander Vorobiev alexander.vorob...@gmail.com writes:
The next problem I have is babel-related. I create results of
execution of my source blocks in org format so they are enclosed in
#+BEGIN_ORG ... #END_ORG which gets translated by the new exporter
into \begin{org} \end{org} -
Nicolas,
Here is my configuration section (it goes at the end of the org file).
Nothing in the LaTeX_HEADER lines gets inserted into output tex
document. The old exporter just inserted them all verbatim.
#+STARTUP:align fold nodlcheck hidestars oddeven lognotestate
#+PROPERTY: exports
Hello,
Alexander Vorobiev alexander.vorob...@gmail.com writes:
Here is my configuration section (it goes at the end of the org file).
Nothing in the LaTeX_HEADER lines gets inserted into output tex
document. The old exporter just inserted them all verbatim.
#+STARTUP:align fold
Hi Nicolas,
Thanks a lot for the help, I configured the org-e-latex-classes and
now am getting somewhere - at least my LaTeX settings appear in the
output. The next problem I have is babel-related. I create results of
execution of my source blocks in org format so they are enclosed in
#+BEGIN_ORG
Hello,
t...@tsdye.com (Thomas S. Dye) writes:
(require 'org-special-blocks)
You can remove this line. `org-special-blocks' is obsolete with the new
exporter.
Regards,
--
Nicolas Goaziou
Hello,
Alexander Vorobiev alexander.vorob...@gmail.com writes:
I tried the new exporter (using today's snapshot of the sources) and
it produced invalid LaTeX (it calls hypersetup without loading
hyperref package).
The export back-end doesn't load any package on its own. You have to
make sure
Hi Alexander,
Alexander Vorobiev alexander.vorob...@gmail.com writes:
Could you point us to any documentation on how to switch to the new
exporter?
Add contrib/lisp to your load-path.
(require 'org-e-latex)
then M-x org-export-dispatch RET to get a menu and be able to
export to LaTeX from
I tried the new exporter (using today's snapshot of the sources) and
it produced invalid LaTeX (it calls hypersetup without loading
hyperref package). It also ignored the #+LaTeX_CLASS: and all the
#+LaTeX_HEADER:lines in my file. Are there any examples of org files
which show how to customize the
Alexander Vorobiev alexander.vorob...@gmail.com writes:
I tried the new exporter (using today's snapshot of the sources) and
it produced invalid LaTeX (it calls hypersetup without loading
hyperref package). It also ignored the #+LaTeX_CLASS: and all the
#+LaTeX_HEADER:lines in my file. Are
Hi,
I am having similar problems with LaTeX export. I am exporting source
code snippets (XML) which has many variables with underscores in their
names. At some point in the process of switching to more recent Org
the export started producing incorrect LaTeX so the generation of PDF
fails,
Hi Gary,
Gary Oberbrunner ga...@oberbrunner.com writes:
Using a recent git checkout of org-mode (f51c405), the following small
org-mode file produces invalid LaTeX. I'm pretty sure it used to
work. The \alpha and \beta seem to be what confuses it.
---snip
* Scorecards
**
Using a recent git checkout of org-mode (f51c405), the following small
org-mode file produces invalid LaTeX. I'm pretty sure it used to
work. The \alpha and \beta seem to be what confuses it.
---snip
* Scorecards
** Product Releases
| *Product* | *\alpha* | *\beta* | *Release* |
Wiadomość napisana przez Nick Dokos w dniu 10 sty 2012, o godz. 01:13:
Have you tried exporting a simple file to latex? Perhaps something as simple
as:
---
* Foo
Bar
Piotr Kaźmierczak p.h.kazmierc...@gmail.com wrote:
Wiadomość napisana przez Nick Dokos w dniu 10 sty 2012, o godz. 01:13:
Have you tried exporting a simple file to latex? Perhaps something as simple
as:
---
*
Wiadomość napisana przez Nick Dokos w dniu 17 sty 2012, o godz. 18:00:
In that case, it seems like your orgmode install is hosed - have you tried
reinstalling from scratch?
I did, but no luck. There must be something else I'm missing here, but I don't
have time to investigate now.
Thanks
Piotr Kaźmierczak p.h.kazmierc...@gmail.com writes:
Wiadomość napisana przez Nick Dokos w dniu 10 sty 2012, o godz. 01:13:
Have you tried exporting a simple file to latex? Perhaps something as simple
as:
---
* Foo
Hi,
I have a very strange problem: I can no longer process an org file with all my
notes to LaTeX. I've been using org-mode this way for some time now, and I was
always able to get a nice tex file I could later process to PDF. Now all I get
is a TeX file with absolutely no new-line symbols
Piotr Kaźmierczak p.h.kazmierc...@gmail.com wrote:
I have a very strange problem: I can no longer process an org file
with all my notes to LaTeX. I've been using org-mode this way for some
time now, and I was always able to get a nice tex file I could later
process to PDF. Now all I get is
Hi there!
I experience some problems when exporting clipped tables to LaTeX:
The text in the fields doesn't get properly expanded, the `=' is not
removed.
Imagine the following table in org-mode:
| on the one hand | on the other = |
|-+-|
| 15| 15
Hi Frederik,
Frederik freak.f...@gmail.com writes:
I experience some problems when exporting clipped tables to LaTeX:
The text in the fields doesn't get properly expanded, the `=' is not
removed.
thanks for reporting this -- should be fixed now.
Best,
--
Bastien
29 matches
Mail list logo
