From: Christian Moe <mail@christianmoe.com>
To: "Martin Gürtler" <martin.guertler@gmx.de>
Cc: emacs-orgmode@gnu.org
Subject: Re: ox-odt doesn't honor :anchor "page"
Date: Tue, 30 Sep 2014 09:58:01 +0200 [thread overview]
Message-ID: <m2bnpxtu9i.fsf@christianmoe.com> (raw)
In-Reply-To: <loom.20140930T092118-520@post.gmane.org>
Confirmed, but it seems to be a documentation error, not a bug.
It works if you leave out the quotation marks:
#+ATTR_ODT: :anchor page
The docs do indeed unequivocally require quotation marks, but I don't
think there is any need for them.
Yours,
Christian
Martin Gürtler writes:
> Hi,
>
> I'm using Org-mode version 8.2.7c (8.2.7c-74-gd2ecbe-elpa, org-plus-contrib
> package).
>
> I am writing a documentation in org mode with the intent of exporting it to
> libreoffice (using libreoffice 4.2.6.3 on ubuntu 12.04).
>
> This works in general very well.
>
> I have a minor problem with image anchors.
>
> I think I followed the docs when writing
>
> #+ATTR_ODT: :width 17 :anchor "page"
> #+CAPTION: Some text.
> #+LABEL: fig:figureLabel
> [[file:someFig.png]]
>
> The :anchor statement seems to be ignored in the export process, I always
> get images anchored to the paragraph.
>
> When using Jambunathan's version of ox-odt I get images anchored to the
> page, but there seem to be problems if there are two images on one page,
> images covering each other when both are anchored to the page..
>
> One of the few cases where doc is ahead of implementation?
>
>
> Regards
>
> Martin
next prev parent reply other threads:[~2014-09-30 7:57 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-30 7:35 ox-odt doesn't honor :anchor "page" Martin Gürtler
2014-09-30 7:58 ` Christian Moe [this message]
2014-09-30 8:21 ` Image collisions (was Re: ox-odt doesn't honor :anchor "page") Martin Gürtler
2014-09-30 9:30 ` Christian Moe
2014-09-30 10:23 ` Martin Gürtler
2014-09-30 16:50 ` ox-odt doesn't honor :anchor "page" Achim Gratz
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://www.orgmode.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=m2bnpxtu9i.fsf@christianmoe.com \
--to=mail@christianmoe.com \
--cc=emacs-orgmode@gnu.org \
--cc=martin.guertler@gmx.de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).