- Appended to comment:
drh added on 2008-07-24 12:35:28:
I content that the <verbatim> rendering is correct and that it is your expectation of wha <verbatim> is suppose to do that is wrong. To this end, I have attempted to clarify the documentation on <verbatim>:The <verbatim> tag works like <pre> with the addition that it also disables all wiki and HTML markup through the matching </verbatim>.
- Change priority to "Immediate"
- Change private_contact to "6b3f5a8f6def0ef153f7a89fb5a1b0fa01d7509e"
- Change resolution to "Fixed"
- Change status to "Fixed"
- Change subsystem to "one"
- Change comment to "If you try to add following text in the sandbox, the resulting rendering is IMO not correct (please insert two spaces in front of every non-blank line in the sample below -- the sample should consists of 7 lines including the "pre" tags) <hr> <samp> <pre><br> This section encapsulated with <verbatim><pre></verbatim> will not be handled correctly <br> <br> ... if it does go over more ... <br> <br> ... than one line ...<br> </pre> </samp> <hr> The inner "pre" is encapsulated within "verbatim" it still influence the rendering. And although the whole text is encapsulated within "pre", the first line will be rendered differently from the second and third one."
- Change foundin to "f46fe42d6d"
- Change private_contact to "63f4cb9d6971f7dbdee05412b8546975182b32e4"
- Change severity to "Minor"
- Change status to "Open"
- Change title to "Rendering of tags <pre> and <verbatim> not correct"
- Change type to "Code_Defect"