I'm open to posting my code differently. The only thing I have a problem with is appearance changes to posts that were created before this new functionality went into effect. It would be neat if there could be some kind of filter where posts made before the new functionality aren't modified. Existing posts were made with the originator verifying the appearance. If changes to the appearance are done later, the intent of the original post may change.

>>I have a quite a few messages where I used < b > tag inside < pre > tag to highlite suggested changes to the code. Now they are shows as a tags not as a bold. How are you going to fix those?
>>For example, Message #604932, Message #565149.
>
>To me, this is why HTML on a web forum shoudl never be opened up. You effectlivy lock the application to one specific interface. FWIW, I woudl avoid posting HTML in your messages. West Wind's messageboard gets around this by posting test "as is" and require two angle brackets around the text you want to treat as HTML.
>
>I'd suggest working on moving towards a standard like that. UT Macros could be developed (something like the Wikis #b#) or you can use West Wind's solution and do < < b > >.
>
>Or, simply don't use fomrating in code, and use code comments. After all, that IS what they are designed for.