From: Christian Moe <mail@christianmoe.com>
To: Enrico Scholz <enrico.scholz@sigma-chemnitz.de>
Cc: emacs-orgmode@gnu.org
Subject: Re: Bug: Bad ODT files when including multiple images [7.9.3f (release_7.9.3f-17-g7524ef @ /usr/share/emacs/24.3/lisp/org/)]
Date: Tue, 03 Dec 2013 15:41:35 +0100 [thread overview]
Message-ID: <m238ma0zfk.fsf@uio.no> (raw)
In-Reply-To: <lyob4y3tbx.fsf@ensc-virt.intern.sigma-chemnitz.de>
Enrico Scholz writes:
>> It seems LibreOffice 4.1 now requires that draw:frame elements wrapping
>> images be uniquely named with the draw:name attribute if there's more
>> than one of them.
>> ...
>> So we may need a fix for the corner case of identical captions as
>> well.
>
> Why do we need meaningful 'draw:name' values at all? And why use the
> caption for it? Just adding 'draw:name="Image%u"' and incrementing the
> index after each use seems to be enough.
Indeed, that sounds like a simple all-round fix, and better than one
solution for uncaptioned images and a fragile one for captioned
ones. Did a quick test replacing the draw:name attributes for captioned
images with such generic names, and it didn't seem to cause any
problems.
> Alternatively, '#+NAME:' seems to be a much better choice than
> #+CAPTION.
But not a good one, since users do not necessarily name images.
Yours,
Christian
next prev parent reply other threads:[~2013-12-03 14:42 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-12-02 17:22 Bug: Bad ODT files when including multiple images [7.9.3f (release_7.9.3f-17-g7524ef @ /usr/share/emacs/24.3/lisp/org/)] Enrico Scholz
2013-12-02 20:10 ` Jambunathan K
2013-12-02 23:54 ` Enrico Scholz
2013-12-03 11:06 ` Enrico Scholz
2013-12-03 13:53 ` Christian Moe
2013-12-03 14:25 ` Enrico Scholz
2013-12-03 14:41 ` Christian Moe [this message]
2013-12-03 15:47 ` Jambunathan K
2013-12-17 14:04 ` Tim
2013-12-17 18:46 ` Jambunathan K
2013-12-17 19:28 ` Tim
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=m238ma0zfk.fsf@uio.no \
--to=mail@christianmoe.com \
--cc=emacs-orgmode@gnu.org \
--cc=enrico.scholz@sigma-chemnitz.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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.