From mboxrd@z Thu Jan 1 00:00:00 1970 From: Christian Moe 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 Message-ID: References: <87ob4zko8o.fsf@gmail.com> Mime-Version: 1.0 Content-Type: text/plain Return-path: Received: from eggs.gnu.org ([2001:4830:134:3::10]:44235) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1VnrAs-0001gp-OE for emacs-orgmode@gnu.org; Tue, 03 Dec 2013 09:42:16 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1VnrAj-0005xi-A7 for emacs-orgmode@gnu.org; Tue, 03 Dec 2013 09:42:06 -0500 Received: from mail-forward4.uio.no ([2001:700:100:10::33]:45600) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1VnrAi-0005xY-VJ for emacs-orgmode@gnu.org; Tue, 03 Dec 2013 09:41:57 -0500 Received: from exim by mail-out4.uio.no with local-bsmtp (Exim 4.80.1) (envelope-from ) id 1VnrAg-0004Lq-V5 for emacs-orgmode@gnu.org; Tue, 03 Dec 2013 15:41:54 +0100 In-reply-to: List-Id: "General discussions about Org-mode." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org Sender: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org To: Enrico Scholz Cc: emacs-orgmode@gnu.org 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