I agree Toykeeper. What has happened to the world though is so few of us are âpower usersâ that we get left out. For example, ask any iPhone user if they can download a file. They will say âuh, probablyâ. I even asked at a cell phone store. They said yes. Then I said show me. They could not. With the exception of an image, that core functionality is not in iPhone. And nobody has noticed. But for a âpower userâ downloading a config file or script file off your server and tweaking it, then uploading it is critical.
Apple is a special case. Itâs not a technology company. Itâs a fashion company. And although I donât like Apple, theyâre doing their thing well.
As for the rest of the mobile sector, it seems like a simple story of prioritizing short-term profit over long-term progress.
Back to BLFâs software, I think itâs progressing nicely. The upgrade was surprisingly smooth for a major Drupal update, and the remaining tasks are fairly small in a big picture sense.
Itâs fairly simple to understand what happened if you look at the postâs source in the simple editor and keep in mind that every newline gets converted to a break (newline) tag when it renders. The source declares paragraphs (which do their own formatting and newlines), but it also includes actual newlines (which then adds even more space).
It has no way of knowing which language you started with, or whether to attempt to translate. Plus, it has no built-in translator between the two anyway. So, if content goes back and forth between the two, it will have changes in formatting. BLF has always worked this way, and there isnât a simple automatic solution.
Going the other direction, it has historically been common for all newlines to get eaten when a simple-authored post gets quoted in the advanced editor. Itâs a harder problem than it might seem.
On a related note, this is part of why Wikipedia hasnât had a WYSIWYG-style editor for most of its lifetime. (What You See Is What You Get) That feature is only available as of October 2015, and the organization running the site said it âconsidered it the most challenging technical project to dateâ.
Clicking âmark readâ occasionally will mark every thread with ### NEW posts despite having viewed them before. I.e. I clicked mark read, came back a few hours later and every single thread had tons of new posts marked.
Longer threads showed something like 170 new posts, newer threads just showed all posts as new. It seemed to work correctly after clicking mark read again.
Wasnât a big deal, I just went into each thread I normally read and went to the last page and read backwards until I hit an old post. Just thought Iâd mention it.
Yes, it looks like it went from eating newlines in one direction to adding newlines in the other direction. I think. I havenât tested it though.
Itâs mainly an issue when people donât trim or clean what theyâre quoting, though⌠which is a big factor in a few other issues as well. Deep quote nesting, for example.
I doubt the human element of it is fix-able. Itâs like trying to get people to stop top-posting entire threads in email. Even at the worldâs top tech companies, thatâs still pretty common.
At least for just newline gardening, itâs probably not a hugely complex issue. A small logic table and a small collection of regular expression substitutions could probably do it.
Ok here's a test of the keengeorge bug report using the Advanced Post editor.
Lorem ipsum dolor sit amet, odio sententiae cu usu, detracto persecuti eu est. Quem mutat mea te, fastidii invenire eos et. Eum sanctus hendrerit id. Id erroribus molestiae vel. Id mei vidit dicant vocent, vim ea posse zril. Cetero persecuti definitionem his eu, quo posse dicam ex. Vel platonem evertitur ad, quo rebum ridens diceret an.
Eum no nullam graeco, vis id dolore putent admodum. Officiis argumentum usu te, meis simul lobortis per in, decore utinam efficiantur vix te. Inani partem aperiam sea ut, vel sint labore salutandi in. Mel regione forensibus ad, pri quem decore audiam no, has aliquam euripidis ad. Quo ne civibus electram efficiantur. No vel case iisque, ei quo elit vocent, vis te quodsi regione. Ex nostrud blandit nam, no eos impetus adolescens definitiones, paulo omittantur te sea.
Graece verterem reprimique id pri, ea sumo luptatum nam, et aeterno hendrerit duo. Pri dicant detracto convenire eu, mea ea stet feugiat vivendum. In vim augue noster tibique. Est in elitr vitae labitur. At sit voluptua tractatos, cum ut quod omnium adipiscing.
Not too ugly.
keengeorge: Is your browser having trouble with line wrapping in the Advanced Editor? Because it looks like your previous posts with it have an awful lot of @<p>@ paragraph tags as though you were manually doing a typewriter carriage return when reaching the right border of the input area.
I think what happened here is that you marked âReadâ on your account, but then your significant other came in and logged into their account in the mean time. They hadnât logged-in in a while, so there were a lot of new posts. But they felt you have been spending a lot of time here lately and needed to check up on you.
I just noticed that the viewing format (number of posts per page) is no longer user selectable. I used to select 300 posts per page to speed up text searches, when wading through long discussion threads.
G'Day SB, :)
I have not been aware of any line wrapping issues in the Advanced Editor, but I have just tested line wrapping in the Advanced Editor & it doesn't seem to be working. ;)
Btw, I insert "CR+LF" as & when I consider them desirable for readability.
Best Regards,
George
PS: This has been generated with Simple Post Editor