get the best and fastest answer
|
|
|
|
Clear questions and runnable code get the best and fastest answer |
|
| PerlMonks |
comment on |
| ( [id://3333]=superdoc: print w/replies, xml ) | Need Help?? |
|
"What?". What?
That was A joke. They say a joke isn't funny if it needs explaining? The issue regarding having to insert html code for paragraph breaks. I have difficulty understanding why, in a forum run by Perl programmers, I assume, or guess, probably coded in Perl, (I can't do view source on this Android device, but I assume) built by Perl programmers with Perl. such a nuisance issue, or issue about a nuisance exists. It looks like I'm not the first to bring this up. People have been complaining, and implementing work arounds for what looks like maybe decades. Making templates, and yours. Which I haven't gotten working. Posting in a forum involves CGI. (I assume I don't have to explain this, but anyway..) "Common Gateway Interface" (not computer generated imagery) Most often, at least in the old days, and, I'm guessing this forum was established long ago... Posts made to any kind of Perl forum were processed with the CGI.pm Perl module which handles the translation of the URL encoding in which the post is sent over the internet back into readable text. Splits on =, Replaces + with spaces and all that. A post to this forum, or any forum, is sent across the internet URL encoded. When it is received by the program it is posted to, by the forum, by PerlMonks.org's backend: (alert! URL coded text ahead)
text=The+program+receives+the+text+URL+encoded+which+ CGI.pm puts it (the URL encoded text) back to normal. So it can be read. In most forums, newline character, (the return for paragraph breaks) which don't render in html are converted to html paragraph breaks or BR or something so that they do. I would assume the reason this hasn't been fixed long ago, is because the "gods" are just having some fun. Certainly it's not because nobody knows how to do a substitution. It must be some kind of joke right? So I got to thinking, if we are going to NOT do the substitution to change the text input newline to html paragraph or line breaks. If someone thinks that's such a gas, well it would be loads more fun if we didn't bother with reversing the URL encoding either. (Try reading the following)
text=Then+all+the+posts+in+here%2C+besides+not+having In other words, the text is going through a lot of processing anyway, on the server, to strip out the URL encoding, perform split and do replacements. Text processing is what Perl excells at. Why not be processing paragraph breaks to be what they are or should be? It's not dangerous. Tom In reply to Re^6: Making Perl Monks a better place for newbies (and others)
by PerlGuy(Tom)
|
|