Justin,

Could you please fix your parsing of our posted comments?

It's very frustrating for us programmers to post properly formatted/indented code that your form parser goofs up because it fails to properly handle the html encoding of the leading spaces.

Oh, his text parser has greater problems than just indenting. Like how the preview breaks whenever two links are manually created in a post.

Hey,

What do you mean HTML encoding of leading spaces? Is it a specific tag you need enabled? I can do that.

Razor,

What do you mean? What is the problem that happens? I'm sure I can fix that as well.

Thanks,
Justin

Hey,

Razor... Thanks for letting me know about that problem. I figured it out and fixed it.

Thanks. Still waiting to hear on the other problem.

Justin

Justin, I beleive he just means that he wants lines that begin a line NOT be stripped off. When posting code it is difficult to interpret without the leading spaces used to show logical segmentation of the code.

Many forums support [CODE] tags to use around the code. If you were to allow PRE tags, that may solve the problem.

Michael J

Justin,

Unfortunately, due to how you parse the submission, I haven't figured out how to post an example (in plain text) on how to to substitute the spaces in our post with the equivalent html code. So, let me ask you, how do YOU represent/display multiple spaces (or tabs) in html code?

I'd post a simple regex example, if I could, but I'm unable to, due to your parsing.

If you need help in the coding, I'm sure there are enough of us to help.

Michael,

If you look at the html source, you'll see that the spaces in our posts are preserved, but they are not html encoded. So, in the browser rendering, multiple spaces get squashed down to 0 leading spaces and/or a single space in between the "words".

BTW, while we're on the subject of html coding, have you ever validated any of the pages in your site? The main page for the programming section has over 1200 errors.

Justin Weber: I figured it out and fixed it.
So you did. Thanks.

Still waiting to hear on the other problem.
The responses are kinda vague, but what we want is a tag that preserves whitespace; <pre> probably.

Hey,

I thought I had allowed pre tags. I must have taken them out.

Anyway, pre should work now...

  This is test code {
       print "hello world";
  }
}

Thanks for letting me know about this. If you have any more issues, let me know about those too and I'll do my best to fix them.

Justin

BTW,

Fishmonger, I am using an HTML validator. Those show up as "warnings" not errors for me.

Justin

Justin,

Thanks for enabling the use of the pre tag. I haven't tested it, but it should help. Did you implement it in the backend or frontend; meaning is it added by your parser, or do we need to add it in the confirmation page.

BTW,
You may want to use a different validator. According to the W3C validator, there are 1210 errors, none of which are listed as warnings.
http://validator.w3.org/check?uri=h...

However, most of those will go away if you change the doctype.

Well, the W3C validator is a bit overzealous. Besides, the count shoots down to 61 if you force HTML 3.2.

FishMonger
It appears to be added at the parser.

Looks like we need to put in the tags.

http://computing.net/programming/ww...

Next mystery: why do the tags change the font?

BTW, the only W3C errors on my page are in the PayPal code. I wrote to support and got some totally berserk response. LOL

Justin,

Thanks for the tag fix.

=====================================
If at first you don't succeed, you're about average.

M2

Mechanix2Go: Next mystery: why do the tags change the font?
<`pre> renders with a mono-spaced font. Thus the font change.