Thanks for the offer, Noum, but they aren't really a big problem. I have a spreadsheet that finds them, and I just edit. There are usually only about thirty or so a thread (I'm looking at you, BHP...).

Cindy, the problem with PRE for me is that between the way the Phoenix and Mozilla handle the tag, every blank line in PRE formatted text becomes three or four blank lines, which really looks awful on the screen. It looks fine in IE.

I just thought maybe we would need the pre tag less, if a single line break (you know, like "return" on a typewriter - I don't know right techie words) showed up without us having to put in the t br tag. And if we could get rid of the t pre , your life would be easier when you archive. I'm all for an easier life for nice people who are doing helpful things. There should be more of that.

But, since quick edit requires a new line for its codes, I don't know if this would affect quick edit posts, and gum up the whole shebang.

Am I making any sense? I think not. I'll stop. :)

It requires no Special Stompy Powers, Nou. DX threadsucks the Natter thread and then manually goes though the downloaded file to fix the messy parts.

Actually, it does, because I edit the original posts. It's much easier to do the editing on them than on the entire threadsuck.

because I edit the original posts.

So THAT's why all those archived threads keep having posts like "DX is the coolest!" and "You know you want him..."

No, wait, we say that anyway...

Am I making any sense?

I get what you're saying. It's the way LJ works. I don't know that it would work here.

The problem is that the Phoenix code puts a Paragraph tag after each blank line, even inside the PRE tag. IE ignores the extra tags. Mozilla doesn't.

So THAT's why all those archived threads keep having posts like "DX is the coolest!" and "You know you want him..."

I knew I shoulda kept my mouth shut...

Actually, it does, because I edit the original posts.

I stand corrected!

since quick edit requires a new line for its codes

Yeah, you wouldn't want a line break to appear after a quickedit, so you'd have to code to ignore those breaks.

The problem with having carriage returns always display as line breaks, aside from any coding issues, is that sometimes you want the line breaks to disappear, for instance when copying and pasting from somewhere else. I think forcing people to use the t br tag is the simplest solusion.

I don't know if it matters or if there is anything that could/should be done, but the computers at Breuggers block Buffistas.org as having unsafe content.

What's Breuggers?

Oh-- sorry-- it is a chain of bagel places-- I thought it was national. But they have public computers