You are viewing a plain text version of this content. The canonical link for it is here.
Posted to zeta-issues@incubator.apache.org by "Rob Allen (JIRA)" <ji...@apache.org> on 2011/01/01 21:47:46 UTC

[jira] Updated: (ZETACOMP-37) RST table to Docbook results in lots of trailing whitespace in XML

     [ https://issues.apache.org/jira/browse/ZETACOMP-37?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Rob Allen updated ZETACOMP-37:
------------------------------

    Description: 
RST:
{code}
================= ============= ====================================
Head One          Head Two      Head Three
================= ============= ====================================
This is body one. This is body2 This is the body to the third column
================= ============= ====================================
{code}

Docbook XML:
{code}
<table>
  <tgroup>
    <thead>
      <row>
        <entry>
          <para>Head One          </para>
        </entry>
        <entry>
          <para>Head Two      </para>
        </entry>
        <entry>
          <para>Head Three</para>
        </entry>
      </row>
    </thead>
    <tbody>
      <row>
        <entry>
          <para>This is body one. </para>
        </entry>
        <entry>
          <para>This is body2</para>
        </entry>
        <entry>
          <para>This is the body to the third column</para>
        </entry>
      </row>
    </tbody>
  </tgroup>
</table>
{code}


I would expect <para>Head One</para> etc.

  was:
RST:
================= ============= ====================================
Head One          Head Two      Head Three
================= ============= ====================================
This is body one. This is body2 This is the body to the third column
================= ============= ====================================

Docbook XML:

<table>
  <tgroup>
    <thead>
      <row>
        <entry>
          <para>Head One          </para>
        </entry>
        <entry>
          <para>Head Two      </para>
        </entry>
        <entry>
          <para>Head Three</para>
        </entry>
      </row>
    </thead>
    <tbody>
      <row>
        <entry>
          <para>This is body one. </para>
        </entry>
        <entry>
          <para>This is body2</para>
        </entry>
        <entry>
          <para>This is the body to the third column</para>
        </entry>
      </row>
    </tbody>
  </tgroup>
</table>



I would expect <para>Head One</para> etc.


> RST table to Docbook results in lots of trailing whitespace in XML
> ------------------------------------------------------------------
>
>                 Key: ZETACOMP-37
>                 URL: https://issues.apache.org/jira/browse/ZETACOMP-37
>             Project: Zeta Components
>          Issue Type: Improvement
>          Components: Document
>         Environment: PHP 5.3
>            Reporter: Rob Allen
>            Priority: Minor
>
> RST:
> {code}
> ================= ============= ====================================
> Head One          Head Two      Head Three
> ================= ============= ====================================
> This is body one. This is body2 This is the body to the third column
> ================= ============= ====================================
> {code}
> Docbook XML:
> {code}
> <table>
>   <tgroup>
>     <thead>
>       <row>
>         <entry>
>           <para>Head One          </para>
>         </entry>
>         <entry>
>           <para>Head Two      </para>
>         </entry>
>         <entry>
>           <para>Head Three</para>
>         </entry>
>       </row>
>     </thead>
>     <tbody>
>       <row>
>         <entry>
>           <para>This is body one. </para>
>         </entry>
>         <entry>
>           <para>This is body2</para>
>         </entry>
>         <entry>
>           <para>This is the body to the third column</para>
>         </entry>
>       </row>
>     </tbody>
>   </tgroup>
> </table>
> {code}
> I would expect <para>Head One</para> etc.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.