On Tue, Jun 27, 2006 at 07:10:07PM +0200, Platonides wrote:
"Rob Church" wrote:
The main argument boils down to semantics. The
output is wrapped in
<div class="poem">, meaning that people can opt to see poems formatted
in a specific manner. This formatting might not need to be applied to
non-poem texts, or it might be otherwise undesirable. In short, it
comes down to "don't mark up non poems as poems".
It would be somewhat trivial to expand the extension to allow
customising the class output according to the tag used; if another use
case pops up, we can add another tag and class combination.
This seems the most logical of all the discussion. Make the <poem> produce
<div class="poem"> and <poem class="Foo"> <div
class="Foo">. It may seem
strange a poem of recipe class but could be the solution for all this
problematic.
Well, perhaps, but remember that it was just pointed out that the poem
tag does special things specific to poems, which may or may note be
appropriate to other specialty insertions -- which may be why it's
called called 'poem', come to think of it.
Cheers,
-- jra
--
Jay R. Ashworth jra(a)baylink.com
Designer Baylink RFC 2100
Ashworth & Associates The Things I Think '87 e24
St Petersburg FL USA
http://baylink.pitas.com +1 727 647 1274
A: Because it messes up the order in which people normally read text.
Q: Why is top-posting such a bad thing?
A: Top-posting.
Q: What is the most annoying thing on Usenet and in e-mail?