From mboxrd@z Thu Jan  1 00:00:00 1970
From: Christian Moe <mail@christianmoe.com>
Subject: Re: [BUG] [ODT] Annotations break paragraphs
Date: Mon, 25 Mar 2013 11:29:35 +0100
Message-ID: <m2d2un3h80.fsf@christianmoe.com>
References: <m2vc8kjvud.fsf@christianmoe.com>
	<CAJcAo8v=gSw+6=yCrh7QuDCTidL_3gKJeMkiYGQ9m2qL_fJKjg@mail.gmail.com>
Mime-Version: 1.0
Content-Type: text/plain
Return-path: <emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org>
Received: from eggs.gnu.org ([208.118.235.92]:34249)
	by lists.gnu.org with esmtp (Exim 4.71)
	(envelope-from <mail@christianmoe.com>) id 1UK4da-00080d-8t
	for Emacs-orgmode@gnu.org; Mon, 25 Mar 2013 06:28:23 -0400
Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71)
	(envelope-from <mail@christianmoe.com>) id 1UK4dZ-0002fN-5r
	for Emacs-orgmode@gnu.org; Mon, 25 Mar 2013 06:28:22 -0400
Received: from mail2.b1.hitrost.net ([91.185.211.205]:50335)
	by eggs.gnu.org with esmtp (Exim 4.71)
	(envelope-from <mail@christianmoe.com>) id 1UK4dY-0002el-WC
	for Emacs-orgmode@gnu.org; Mon, 25 Mar 2013 06:28:21 -0400
In-reply-to: <CAJcAo8v=gSw+6=yCrh7QuDCTidL_3gKJeMkiYGQ9m2qL_fJKjg@mail.gmail.com>
List-Id: "General discussions about Org-mode." <emacs-orgmode.gnu.org>
List-Unsubscribe: <https://lists.gnu.org/mailman/options/emacs-orgmode>,
	<mailto:emacs-orgmode-request@gnu.org?subject=unsubscribe>
List-Archive: <http://lists.gnu.org/archive/html/emacs-orgmode>
List-Post: <mailto:emacs-orgmode@gnu.org>
List-Help: <mailto:emacs-orgmode-request@gnu.org?subject=help>
List-Subscribe: <https://lists.gnu.org/mailman/listinfo/emacs-orgmode>,
	<mailto:emacs-orgmode-request@gnu.org?subject=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: Samuel Wales <samologist@gmail.com>
Cc: Emacs-orgmode@gnu.org


Samuel Wales writes:
>
> A similar issue arises with inline footnotes.
[...]
> In my case I was able with Nicolas's supplied code to create a hook
> that normalized footnotes before export.  Maybe extracting in a hook
> will work for you.  However, I fear that incorporating the parser into
> the font lock engine will break these paragraphs.

Thanks for the tip. I don't think user-side hacks are the way to go
here, though. Org-odt provides an annotation feature for ODT export,
based on using the special-block syntax, that no longer works as
intended. I'm hoping it can simply be fixed, but if putting the
annotation in a block must lead to paragraph breaks under the new
exporter, a different solution is needed.

Yours,
Christian