From: Nicolas Goaziou <n.goaziou@gmail.com>
To: Jambunathan K <kjambunathan@gmail.com>
Cc: emacs-orgmode@gnu.org
Subject: Re: [bug] org-inlinetask produces invalid xhtml
Date: Thu, 11 Aug 2011 12:23:06 +0200 [thread overview]
Message-ID: <871uwsl01h.fsf@gmail.com> (raw)
In-Reply-To: <81y5z2p82h.fsf@gmail.com> (Jambunathan K.'s message of "Wed, 10 Aug 2011 03:21:34 +0530")
Hello,
Jambunathan K <kjambunathan@gmail.com> writes:
> 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)
Loading org-inlinetask is the user's job. He has to assume weird things
which will happen when the buffer holds inline tasks without them being
loaded (but I give him an excuse as inline tasks are completely
undocumented).
> 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 <div class="inlinetask"> ... </div> 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? )
As far as I can tell, inline tasks are not designed to be nested.
> I am sure html and odt exporters can take care of inlinetask purely
> during post-processing and do away with templates altogether.
Templates are fine as long as inline tasks are not loaded by default. If
this changes, I agree there are better ways to handle them (one being
what you explain above).
But, a few weeks ago, Bastien suggested to think again inline tasks. So,
that might not happen soon.
> 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.
What I think is that, for now, we just should keep the existing facility
and implement a working default template for HTML (and a new one for
ODT).
Regards,
--
Nicolas Goaziou
next prev parent reply other threads:[~2011-08-11 10:23 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-08-08 16:36 [bug] org-inlinetask produces invalid xhtml Jambunathan K
2011-08-08 16:51 ` Jambunathan K
2011-08-08 18:26 ` Nicolas Goaziou
2011-08-09 5:44 ` Jambunathan K
2011-08-09 11:42 ` Nicolas Goaziou
2011-08-09 21:51 ` Jambunathan K
2011-08-09 23:47 ` suvayu ali
2011-08-11 10:23 ` Nicolas Goaziou [this message]
2011-08-11 11:21 ` Jambunathan K
2011-08-11 11:21 ` Jambunathan K
2011-08-11 12:17 ` Nicolas Goaziou
2011-08-11 20:38 ` Jambunathan K
2011-08-16 19:30 ` Bastien
2011-08-16 19:21 ` Bastien
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
List information: https://www.orgmode.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=871uwsl01h.fsf@gmail.com \
--to=n.goaziou@gmail.com \
--cc=emacs-orgmode@gnu.org \
--cc=kjambunathan@gmail.com \
/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 public inbox
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).