From: Jambunathan K <kjambunathan@gmail.com>
To: emacs-orgmode@gnu.org
Subject: [bug] org-inlinetask produces invalid xhtml
Date: Mon, 08 Aug 2011 22:06:02 +0530 [thread overview]
Message-ID: <81ipq7j1xp.fsf@gmail.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 347 bytes --]
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.
[-- Attachment #2: odt-export-bug.org --]
[-- Type: text/plain, Size: 693 bytes --]
* B oscillations
This is Suvayu's example but simplified. Also see the annotation
within the inline task itself.
_Questions_:
*************** Detector effects :Qn:
Suvayu's example uses lists within inline task. Can the html export
engine produce valid html when the inline task has lists. But honestly
why does a preformatted text looks like a well-formatted html
list. Isn't that strange. Just uncomment the below list and see for
yourself.
# 1. How is the Gaussian used for smearing of proper time resolution
# derived? [[http://www.google.com][Google]] this.
# 2. Why is the proper time error PDF needed? Why is
# smearing of time resolution not enough?
*************** END
[-- Attachment #3: odt-export-bug.html --]
[-- Type: text/html, Size: 3678 bytes --]
[-- Attachment #4: Type: text/plain, Size: 5 bytes --]
--
next reply other threads:[~2011-08-08 16:36 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-08-08 16:36 Jambunathan K [this message]
2011-08-08 16:51 ` [bug] org-inlinetask produces invalid xhtml 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
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=81ipq7j1xp.fsf@gmail.com \
--to=kjambunathan@gmail.com \
--cc=emacs-orgmode@gnu.org \
/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).