On Monday 06 February 2006 19:33, Mathieu Roy wrote: > > What do you think should <verbatim> be? Inline or a new block? > > inline.
Yes, that's my opinion, too.
> Using html < and > is shooting a bullet in our foot. As one may well be
> writing in a comment
>
> #verbatim#
> althis html <b>bla bla</a> with <code>inside</code> bla bla
> blo bli <br>
> #verbatim#
>
> And we definitely do not want <code> in this text to have any effect.
True. But it won't have any effect, because it's converted with
htmlspecialchars() before being inserted in the DB. So the actual output to
the browser is <code>, not <code>.
The verbatim tag does nothing else than temporarily disabling the wiki
markup. The rest of the markup is completely left alone.
> The point with #verbatim# is the fact that this is not used in any
> language (or if it does, I wonder which)
>
> Also, it highlight the idea of the string being some kind of comment
> which wont show up in the end.
To me, it's not a comment, but a special tag used for the markup, like three
'=' signs are the tag for a level 3 heading. Moreover, if the parsing fails
for some reason, <verbatim> will not show up in the browser, because it's
recognized as an unknown HTML tag. #verbatim# on the other hand will be
displayed.
[HTML chars in the DB]
> Granted this is not great. But I guess changing that means reviewing all
> the code, everytime a SQL INSERT or UPDATE is made. Tough job!
Indeed.
Cheers,
--
Tobias
Warning: Trespassers will be shot.
Survivors will be shot again.
pgpvN2NN3cxHq.pgp
Description: PGP signature
