In trying to deal with what looked like bad formatting on Parse::RecDescent grammar and Parenthesis, I noticed that when I previewed the changes, additions I had made to the end of the node looked ok, (that is, closing the CODE tag fixed all the formatting problems on it), but then when updated, all those changes were lost. I'm guess that the same thing bit crazyinsomniac as well, as you can apparently edit arbitrarily long preview nodes, but once it's finalized, the node only seems to consider the first 16k of text, dropping the rest including any possible formatting.

Understandably, limiting the amount of text that can be posted is wise, but this should also apply to preview views, as well as informing the user that they are over the current node size in preview mode. In such cases, the user can easily post follow up code to children nodes, such as in this specific case, the long DD output could go there.

(I'd argue that 16k might be too small, but I would presume that the nodes that are for code specifically (Code/Snippets/CUfP) have a larger limit by default, and most posts here are < 1k to start with. Thus, the number of times this limit will be hit should be minimal and easily fixed with the help of editors and the poster combined).

-----------------------------------------------------
Dr. Michael K. Neylon - mneylon-pm@masemware.com || "You've left the lens cap of your mind on again, Pinky" - The Brain
"I can see my house from here!"
It's not what you know, but knowing how to find it if you don't know that's important