It is absolutely possible to port it. Huge swaths of it are trivial. It’s just a serious commitment and only senior level webdevs—and it’s time to put a finer point on that point, that Venn does not include anyone who thinks this is a fix for anything: s/\n/<br>/g—and especially ETL pros are qualified to try.
| [reply]
[d/l] |
I would think just allowing the "return" or newline to go into the database unprocessed and unmodified and to spit it back out, unprocessed and unmodified, would be a not good scenario.
What is to prevent me or anyone from just holding down the return key for an hour and posting 7 million lines of whitespace?
Tom
| [reply] |
What is to prevent me or anyone from just holding down the return key for an hour
Nothing; but you're only wasting your own time. And there's nothing special about newlines. What's to prevent someone from pasting <HR/> a million times?
and posting 7 million lines of whitespace?
LOL. Node size is limited to 64 kb.
And if anyone posted a node consisting of 64kb of newlines, that node would be reaped within the hour.
So what was your point again? lol
| [reply]
[d/l] |
"that Venn does not include anyone who thinks this is a fix for anything: s/\n/<br>/g—"
I believe I said: s/\n/<br\/>/g; which is something of a simplification, but what in principle do you think is wrong with it. (<BR /> as a general replacement for "return".)
Tom
| [reply]
[d/l]
[select] |
> what in principle do you think is wrong with it. ( <BR /> as a general replacement for "return".)
Substituting more than 2 "\n" with <p> is OK, I'm doing this for years already.
But <br> for every single "\n" is not a good idea, because HTML must be capable to adapt to different screen-sizes.
That's basically why <pre> is frowned upon.
PS: 2 thirds of all your posts in 11 years are in this thread. Impressive!
| [reply]
[d/l]
[select] |