The rules for escaping special characters in this forum are
For example, the DELIMITED BY slash-x09 must be coded with two slashes in the PRE section in this question: http://sqlanywhere-forum.sap.com/questions/12518/how-do-i-refer-to-the-same-openstring-file-twice-in-one-query
but with only one slash in the PRE section of this answer: http://sqlanywhere-forum.sap.com/questions/12518/how-do-i-refer-to-the-same-openstring-file-twice-in-one-query/12540
This is only one example of many... sometimes stuff doesn't need to be escaped (underscores, asterisks), sometimes it doesn't.
For example the asterisk in SELECT v_property.* needed escaping in the question linked above, but not in the answer... and right now I cannot seem to create an example of PRE where it DOES need escaping.
IMO pre-formatted text is sacrosanct... special highlighting features are acceptable ONLY IF THEY ARE PERFECTLY IMPLEMENTED... if special features have any flaws whatsoever, they should be REMOVED ALTOGETHER... code is code, not a Christmas tree.
I can't tell you exactly why but it's an issue with HTML parsing. The difference between the formatted text in the question and the formatted text in the answer is that there's a blank line before the
Text <pre> Code </pre>
I suspect that in the first case, the markdown parser doesn't realize it's in a
answered 06 Jul '12, 11:19
I'll agree with you that the Markdown syntax can take a bit of effort to learn, but all mark-up syntaxes take effort to learn, and I have (personally) find that Markdown is easier than other ones that I have used (especially some Wiki syntaxes which IMHO are less than wonderful).
I've tried to understand why you have seen the differences in the escape requirements in the two pre sections but my offline testing has not repro'ed the issue. :-( '\\x09' vs '\x09' - in fact my testing (on our development system) has shown that the question did not need to use two backslashes when you escaped the sequence. It would appear that it was just a preview vs final-rendered difference (as I mentioned above).
Edit: Note that in typing my response I had to go back and edit my response to escape the second \x09 so that the backslash would show up. A confirmation that the rendering of escape sequences is not the same in the preview and the final answer !