[Zope] RFC: Flaws in Structured text

[Olivier Deckmyn]

Oups...

I would like to correct my RFC with :

<table>
  <tr>
     <th>FirstName</th><th>LastName</th><th>Age</th>
  </tr>
  <tr>
    <td>Olivier </td><td>Deckmyn</td><td>25</td>
  </tr>
  <tr>
    <td>Guido</td><td>Van Rossum</td><td>32</td>
  </tr>
  <tr>
    <td>Linus </td><td>Torvald </td><td>29</td>
  </tr>
</table>

I changed the
    <td>FirstName</td><td>LastName</td><td>Age</td>
to :
     <th>FirstName</th><th>LastName</th><th>Age</th>


----- Message d'origine -----
De : Olivier Deckmyn <odeckmyn.list@teaser.fr>
À : Zope Mailing List <zope@zope.org>
Envoyé : lundi 13 mars 2000 11:38
Objet : Re: [Zope] RFC: Flaws in Structured text


> I agree with theese purposes on Structured Text...
>
> I would like to be able to write simple tables with Structured Text.
> Something like :
>
> | FirstName | LastName | Age |
> | Olivier | Deckmyn | 25 |
> | Guido | Van Rossum | 32 |
> | Linus | Torvald | 29 |
>
> That will build a simple table :
> <table>
>   <tr>
>     <td>FirstName</td><td>LastName</td><td>Age</td>
>   </tr>
>   <tr>
>     <td>Olivier </td><td>Deckmyn</td><td>25</td>
>   </tr>
>   <tr>
>     <td>Guido</td><td>Van Rossum</td><td>32</td>
>   </tr>
>   <tr>
>     <td>Linus </td><td>Torvald </td><td>29</td>
>   </tr>
> </table>
>
> Customization could be done with CSS...
>
> Thanx !
>
> ----- Message d'origine -----
> De : Geir B Hansen <geirh@funcom.com>
> À : Alexander Staubo <alex@mop.no>
> Cc : Zope Mailing List (E-mail) <zope@zope.org>
> Envoyé : lundi 13 mars 2000 10:38
> Objet : Re: [Zope] RFC: Flaws in Structured text
>
>
> > on Monday, March 13, 2000 Alexander Staubo wrote :
> > AS> I would like to outline a few problems, based on
> > AS> observations of real-world usage, with Structured text.
> > AS> Comments are appreciated.
> >
> > AS> As much as I like the format, the current syntax is either
> > AS> too loose, or the transformation logic too dumb, resulting
> > AS> in text that does not come out quite as expected. There are
> > AS> workarounds for all such problems, but authors and editors
> > AS> aren't aware of them, and continually make the same mistakes
> > AS> over and over again.
> >
> > ...[snip]
> >
> > I agree with your points, but what is more important for me,
> > is that the rendered HTML is syntatically correct
> >
> > * this is an item
> >
> > * another item
> >
> > * a third item
> >
> > currently renders as :
> >
> > <ul>
> > <li><p>this is an item</p>
> > <li><p>another item</p>
> > <li><p>a third item</p>
> > </ul>
> >
> > which is not very slick.. I'd prefer a forward-compatible
> > list-rendering format, complying with HTML4.0 and XHTML,
> > looking like this :
> >
> > <ul>
> > <li>this is an item</li>
> > <li>another item</li>
> > <li>a third item</li>
> > </ul>
> >
> > Anybody who has tried to make Netscape4.x understand CSS
> > without properly closing tags will understand my point..
> >
> > --
> > Geir Bækholt Hansen
> > web-developer/designer
> > geirh@funcom.com
> > http://www.funcom.com
> >
> >
> >
> > _______________________________________________
> > Zope maillist  -  Zope@zope.org
> > http://lists.zope.org/mailman/listinfo/zope
> > **   No cross posts or HTML encoding!  **
> > (Related lists -
> >  http://lists.zope.org/mailman/listinfo/zope-announce
> >  http://lists.zope.org/mailman/listinfo/zope-dev )
> >
> >
>
>
> _______________________________________________
> Zope maillist  -  Zope@zope.org
> http://lists.zope.org/mailman/listinfo/zope
> **   No cross posts or HTML encoding!  **
> (Related lists -
>  http://lists.zope.org/mailman/listinfo/zope-announce
>  http://lists.zope.org/mailman/listinfo/zope-dev )
>
>