From mboxrd@z Thu Jan  1 00:00:00 1970
From: Jambunathan K <kjambunathan@gmail.com>
Subject: Re: [bug] org-inlinetask produces invalid xhtml
Date: Mon, 08 Aug 2011 22:21:50 +0530
Message-ID: <81aabjj17d.fsf@gmail.com>
References: <81ipq7j1xp.fsf@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 ([140.186.70.92]:56756)
	by lists.gnu.org with esmtp (Exim 4.71)
	(envelope-from <kjambunathan@gmail.com>) id 1QqT3v-0007qV-94
	for emacs-orgmode@gnu.org; Mon, 08 Aug 2011 12:52:23 -0400
Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71)
	(envelope-from <kjambunathan@gmail.com>) id 1QqT3u-0007ca-7W
	for emacs-orgmode@gnu.org; Mon, 08 Aug 2011 12:52:23 -0400
Received: from mail-yw0-f41.google.com ([209.85.213.41]:60495)
	by eggs.gnu.org with esmtp (Exim 4.71)
	(envelope-from <kjambunathan@gmail.com>) id 1QqT3u-0007cF-4y
	for emacs-orgmode@gnu.org; Mon, 08 Aug 2011 12:52:22 -0400
Received: by ywa6 with SMTP id 6so3163083ywa.0
	for <emacs-orgmode@gnu.org>; Mon, 08 Aug 2011 09:52:21 -0700 (PDT)
In-Reply-To: <81ipq7j1xp.fsf@gmail.com> (Jambunathan K.'s message of "Mon, 08
	Aug 2011 22:06:02 +0530")
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: </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: Nicolas Goaziou <n.goaziou@gmail.com>
Cc: emacs-orgmode@gnu.org


Nicolas,

> Summary: org-inlinetask produces invalid xhtml
>
> The org file and exported html files are included. Org file also
> contains some annotation on the bug.
>
> Food for thought: If inline task entry is seen as a regular "body text"
> even though it is wrapped in to "<pre> </pre>" element does that suggest
> a possible way in which this bug could be fixed.

Do you want to take a stab at this bug?

Having a valid html is in some sense necessary for producing for valid
odt output ...

Additional Note: I think instead of having templates one could have
org-<backend>-format-inlinetask(heading task todo priority whatever)

Jambunathan K.
--