If I'd hit this thread earlier I'd have told you about the <pre>...</pre> tags. Everything between those tags is displayed in a monospaced font and line breaks are preserved. Tabs aren't handled reliably, so you should indent with spaces. Angle brackets, of course, need to be escaped using < for < and > for >. Inline code can be made monospaced like here using <tt>...</tt> tags.
As for the second problem you had, yeah, my filter really made a mess of your code. I've thought about special processing for code examples, but I was afraid it would weaken the filter's protection against script insertion (JavaScript is almost indistinguishable from C from the viewpoint of a filter trying to parse them); and because with the <pre> tag I've generally been able to post code acceptably.
I'm not clear, in the second example, about whether UUencoding is a necessary part of the example. If you want to send me the unencoded code, I can post it for you with the proper formatting. Or maybe all the encoded block needed was to escape any angle brackets. In either case, I can get your code posted--least I can do after my software ate a half hour's work.
Space/Science » in reply to Darn it!! The Zone's HTML logic ruined that last post
I'm sorry
The whole thread (45 posts)
- a comment on the go for shuttle launch
- re: a comment on the go for shuttle launch
- re: a comment on the go for shuttle launch
- my view as posted on msnbc.com
- Could you imagine what the doctors would say if you had a backup heart?
- Intermittent problems are tough to fix
- re: Intermittent problems are tough to fix
- It's like the "array out of bounds" bug in C programming
- which is itself the best argument against C.
- re: It's like the "array out of bounds" bug in C programming
