Re: [bug] org-inlinetask produces invalid xhtml

[Jambunathan K <kjambunathan@gmail.com>]

[-- Attachment #1: Type: text/plain, Size: 487 bytes --]

Nicolas Goaziou <n.goaziou@gmail.com> writes:

> Hello,
>
> Jambunathan K <kjambunathan@gmail.com> writes:
>
>>> Summary: org-inlinetask produces invalid xhtml
>
> I've pushed a fix. Is it correct now?

The problem persists. You can put the exported html file in nxml-mode
and do a C-c C-n to find the validation errors.

I am attaching the two examples and the problematic html segment (marked
with VALIDATION ERROR) here. Note that one of the examples has a list in
the inline task.



[-- Attachment #2: odt-export-bug.org --]
[-- Type: text/plain, Size: 404 bytes --]

* B oscillations
This is Suvayu's example but simplified. Also see the annotation
within the inline task itself.

_Questions_:
*************** Detector effects					 :Qn:
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: Type: text/plain, Size: 405 bytes --]



#+begin_src nxml
<pre class="inlinetask"><b>Detector effects</b><br />
<ol> <!-- VALIDATION ERROR HERE: Element not allowed in this context -->
  <li>How is the Gaussian used for smearing of proper time resolution
  derived? <a href="http://www.google.com">Google</a> this.
  </li>
  <li>Why is the proper time error PDF needed? Why is
  smearing of time resolution not enough?
  </li>
</ol>
#+end_src


[-- Attachment #4: odt-export-bug1.org --]
[-- Type: text/plain, Size: 470 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.
*************** END


[-- Attachment #5: Type: text/plain, Size: 968 bytes --]


#+begin_src nxml
<div id="outline-container-1" class="outline-2">
  <h2 id="sec-1"><span class="section-number-2">1</span> B oscillations </h2>
  <div class="outline-text-2" id="text-1">

    <p>This is Suvayu's example but simplified. Also see the annotation
    within the inline task itself.
    </p>
    <p>
      <span style="text-decoration:underline;">Questions</span>:
    </p>


    <pre class="inlinetask"><b>Detector effects</b><br />
    <p> <!-- VALIDATION ERROR: Element not allowed in this context -->
      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.
    </pre> <!-- VALIDATION ERROR: Missing end-tag "p" -->

  </p></div> <!-- VALIDATION ERROR: Mismatched end-tag -->
</div>
#+end_src


--