Hello,
Nick Dokos ndo...@gmail.com writes:
Please find an org file and the corresponding tex file attached. The
directory structure is as follows:
~/src/org--images--foo.png
|
|--latex--example.{org,tex}
|
|--example.t2d/pdf/build
Hello,
Nick Dokos ndo...@gmail.com writes:
Nicolas Goaziou n.goaz...@gmail.com writes:
With
#+ATTR_LATEX: :options scale=1.5:width :placement [htb!]
it fails here
(attr (org-export-read-attribute :attr_latex parent))
which evalues to something like
Nick Dokos ndo...@gmail.com writes:
Nick Dokos ndo...@gmail.com writes:
Just a heads-up: As part of testing this, I stumbled on an unrelated
current-working-directory problem, where on exporting to pdf, the
pdflatex of the produced tex file fails to find an image file specified
with a
Nicolas Goaziou n.goaz...@gmail.com writes:
Nick Dokos ndo...@gmail.com writes:
Nick Dokos ndo...@gmail.com writes:
Just a heads-up: As part of testing this, I stumbled on an unrelated
current-working-directory problem, where on exporting to pdf, the
pdflatex of the produced tex file fails
Hello,
Rasmus ras...@gmx.us writes:
Nick Dokos ndo...@gmail.com writes:
if I rearrange the line to
#+ATTR_LATEX: :width :placement [htb!] :options scale=1.5
I get the Wrong argument type error in the current version as
well.
I can reproduce this here.
I guess :width has to be
Nicolas Goaziou n.goaz...@gmail.com writes:
With
#+ATTR_LATEX: :options scale=1.5:width :placement [htb!]
it fails here
(attr (org-export-read-attribute :attr_latex parent))
which evalues to something like
Result: (:options scale=1.5 :placement [htb!]
Nick Dokos ndo...@gmail.com writes:
Just a heads-up: As part of testing this, I stumbled on an unrelated
current-working-directory problem, where on exporting to pdf, the
pdflatex of the produced tex file fails to find an image file specified
with a relative pathname (it works fine with an
Hi Marvin,
Marvin Doyley m.doy...@rochester.edu writes:
Hi there,
When I include the following in my org file
#+attr_latex: scale=1.5, placement =[htb!]
[[file:img/figure2.eps]]
The syntax changes. Something like this might give you what you want.
#+ATTR_LATEX: :placement [htb!]
Hi Rasmus,
It is still not behaving properly
#+ATTR_LATEX: :options scale=2
[[file:fig.pdf]]
yields
\begin{figure}[htb]
\centering
\includegraphics[scale=2,width=.9\linewidth]{fig.pdf}
\end{figure}
which is still not quite right, including option, this still doesn't remove the
extra width
Rasmus ras...@gmx.us writes:
Hi Marvin,
Marvin Doyley m.doy...@rochester.edu writes:
Hi there,
When I include the following in my org file
#+attr_latex: scale=1.5, placement =[htb!]
[[file:img/figure2.eps]]
The syntax changes. Something like this might give you what you want.
When I include the following in my org file
#+attr_latex: scale=1.5, placement =[htb!]
[[file:img/figure2.eps]]
The syntax changes. Something like this might give you what you want.
#+ATTR_LATEX: :placement [htb!] :options scale=1.5
#+CAPTION: a float needs a caption
[[file:fig.pdf]]
Rasmus ras...@gmx.us writes:
One thing that I couldn't figure out is how to get rid of the width
specification altogether.
It's a feature. We had a lengthy discussion about it a while ago
(myself, Nicholas and Aaron, I believe)
Count me confused again: what's the feature? I'll go
Nick Dokos ndo...@gmail.com writes:
One thing that I couldn't figure out is how to get rid of the width
specification altogether.
It's a feature. We had a lengthy discussion about it a while ago
(myself, Nicholas and Aaron, I believe)
Count me confused again: what's the feature? I'll
Hello,
Aaron Ecay aarone...@gmail.com writes:
2013ko urtarrilak 23an, Nicolas Goaziou-ek idatzi zuen:
You needn't. org-exp-blocks functionalities are supported by the new
exporter out of the box.
Can you say more about this? I looked for but did not find a
replacement to the
Nicolas,
Thank you for your explanations, which were very helpful.
2013ko urtarrilak 23an, Nicolas Goaziou-ek idatzi zuen:
You needn't. org-exp-blocks functionalities are supported by the new
exporter out of the box.
Can you say more about this? I looked for but did not find a
replacement to
Hello,
Aaron Ecay aarone...@gmail.com writes:
I’m dealing with a puzzling bug in the new exporter. As background,
I’ve written a custom function to process special-blocks, to replicate
in the new exporter the functionality of the org-exp-blocks package
Rick Frankel r...@rickster.com writes:
So, it seems that as long as there is a body (or blank) line after the
parent heading and you position the cursor on that line, it works
(point at X):
#+begin_src org
* Title
X
** heading 1
text
** heading 2
...
#+end_src
But if there
On Wed, Jan 16, 2013 at 07:36:10PM +0100, Nicolas Goaziou wrote:
Rick Frankel r...@rickster.com writes:
In the new exporter, when the option to export only the subtree is
specified, the first heading in the subtree is used as the title of
the document. This seems wrong, as it becomes the
Hello,
Rick Frankel r...@rickster.com writes:
In the new exporter, when the option to export only the subtree is
specified, the first heading in the subtree is used as the title of
the document. This seems wrong, as it becomes the title, the first
element in the table of contents and the
Please ignore this, the problem does not occur using the latest git source.
--
Best,
Hsiu-Khuern.
Thorsten Jolitz writes:
when I try to use the new exporter outside of an Org buffer, e.g. from a
function or with M-:, it seems that there is a problem with the current
buffer that is used for exporting - it is not the buffer of the Org file
given as argument.
You should read the docstring
Achim Gratz strom...@nexgo.de writes:
Thorsten Jolitz writes:
when I try to use the new exporter outside of an Org buffer, e.g. from a
function or with M-:, it seems that there is a problem with the current
buffer that is used for exporting - it is not the buffer of the Org file
given as
22 matches
Mail list logo
