From mboxrd@z Thu Jan 1 00:00:00 1970 From: Jambunathan K Subject: Re: [bug] org-inlinetask produces invalid xhtml Date: Wed, 10 Aug 2011 03:21:34 +0530 Message-ID: <81y5z2p82h.fsf@gmail.com> References: <81ipq7j1xp.fsf@gmail.com> <81aabjj17d.fsf@gmail.com> <87wrenn4ic.fsf@gmail.com> <81vcu7i1g6.fsf@gmail.com> <874o1qn756.fsf@gmail.com> Mime-Version: 1.0 Content-Type: text/plain Return-path: Received: from eggs.gnu.org ([140.186.70.92]:59971) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1QquDW-0006Ol-Iv for emacs-orgmode@gnu.org; Tue, 09 Aug 2011 17:52:07 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1QquDU-0003A9-LP for emacs-orgmode@gnu.org; Tue, 09 Aug 2011 17:52:06 -0400 Received: from mail-pz0-f44.google.com ([209.85.210.44]:65285) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1QquDU-00039Q-CY for emacs-orgmode@gnu.org; Tue, 09 Aug 2011 17:52:04 -0400 Received: by pzk36 with SMTP id 36so741389pzk.17 for ; Tue, 09 Aug 2011 14:52:02 -0700 (PDT) In-Reply-To: <874o1qn756.fsf@gmail.com> (Nicolas Goaziou's message of "Tue, 09 Aug 2011 13:42:13 +0200") 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: Nicolas Goaziou Cc: emacs-orgmode@gnu.org > I see. Contents of inline tasks are meant to be interpreted during > export. Thus, paragraphs will be marked as

, lists as

    or > whatever... > > This isn't compatible with the default 
     tag provided. I can see two
> possibilities. Come up with a better default value, or provide a way to
> tell to template that contents will be verbatim (or both).
>
> I prefer the first solution, but I can't think of something simple, yet
> elegant enough, for that value. Do you have any suggestion?

(I am speaking here from purely html/odt perspective)

1. When org-inlinetask is NOT LOADED, inline tasks are treated as
   regular headlines and are listified. (The "END" of inlinetask appears
   as listified headline though)

2. If inlinetask is LOADED, the exporter could check the headline level
   against org-inlinetask-min-level and take the following actions:

   - Continue to generate listified entries for inline tasks but
     surround them with 
     ... 
     entries.

   - Strip the "END" list item from being generated

I think org-inlinetask-export-handler could be reduced to 
1. removing the inlinetask when org-inlinetask-export is nil
2. stripping the inlinetask of drawers etc etc.

(Queestions: Does the org-inlinetask-export-handler treat nested inline
tasks well? Btw, Is nesting of inline tasks "legitimate" to begin with?
) 

I am sure html and odt exporters can take care of inlinetask purely
during post-processing and do away with templates altogether. I am not
sure about LaTeX exporter though.

What do you & others think? Let me work on a patch from odt/html side of
things.


Misc:

1. May be someone with css/html expertise can devise a nice css for
   formatting of inlinetasks as part of addressig this bug. 

2. I am undecided about how odt export be formatted - comments, text
   boxes, what else. In case of odt export, there is an option of always
   exporting the inline task but turn on/off their display conditionally
   based on user setting.

> Regards,

--