From: Jambunathan K <kjambunathan@gmail.com>
To: Nicolas Goaziou <n.goaziou@gmail.com>
Cc: emacs-orgmode@gnu.org
Subject: Re: [bug] org-inlinetask produces invalid xhtml
Date: Wed, 10 Aug 2011 03:21:34 +0530 [thread overview]
Message-ID: <81y5z2p82h.fsf@gmail.com> (raw)
In-Reply-To: <874o1qn756.fsf@gmail.com> (Nicolas Goaziou's message of "Tue, 09 Aug 2011 13:42:13 +0200")
> I see. Contents of inline tasks are meant to be interpreted during
> export. Thus, paragraphs will be marked as <p>, lists as <ul> or
> whatever...
>
> This isn't compatible with the default <pre> 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 <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?
)
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,
--
next prev parent reply other threads:[~2011-08-09 21:52 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 [this message]
2011-08-09 23:47 ` suvayu ali
2011-08-11 10:23 ` Nicolas Goaziou
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=81y5z2p82h.fsf@gmail.com \
--to=kjambunathan@gmail.com \
--cc=emacs-orgmode@gnu.org \
--cc=n.goaziou@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).