Or seemingly so, because the newline is being stripped at some lower level before any special formatting is applied.
I suspect the newline is being stripped before the post goes into the database.
As pryrt already explained, no newlines are stripped. Look at the source of the node, they're still there. They are just not rendered by the browser.
| [reply] |
If no transformations are done ...
I'm not talking about what's done by the web protocol.
These fields are POSTed.
What the PM engine receives is what the user typed into the box.
What is stored in the db is what the user typed into the box.
The transformation which the PM engine applies — converting our special markup into real HTML — is done during page rendering.
Is that clear enough?
which would explain why it is not fixable
Why do you believe it's not fixable? Because no one has "fixed" it in the few days since you've started complaining about it?
I suspect the newline is being stripped before the post goes into the database.
100% incorrect. The newline is going all the way to the browser. It's the browser which renders newlines as simple spaces.
I reckon we are the only monastery ever to have a dungeon stuffed with 16 ,000 zombies.
| [reply] |
I see now that this is true, the Newline is passed through unchanged. I just never would have suspected that. I don't know of any other forum software ever used anywhere on the internet, that does not either strip or replace the newline.
"Why do you believe it's not fixable? Because no one has "fixed" it in the few days since you've started complaining about it?"
I didn't start this thread. As I said earlier, I was annoyed slightly, about having to manually insert paragraph breaks, so I searched the forum, and came across this very old thread. (from about 10 YEARS ago).
Numerous other people have brought up the issue. It has been an issue for at least a decade. I could have chosen any of half a dozen or more old threads to post a continuation, or to reopen the discussion.
That is why, I assume, there must be something un-fixable, otherwise, why is it still an issue?
Tom
| [reply] |
| [reply] |