ZTree.com  | ZEN  | About...  

 Index   Back

lI|1o0O   [OT]

By: Martijn Coppoolse   Homepage   Voorburg, NL  
Date: Feb 21,2019 at 04:23
In Response to: lI|1o0O (Greg Akers)

> > > [RANT]
> > > And I am no fan of hard carriage returns in text strings that may
> > > actually wrap differently than the author intends on different
> > devices.
> > > [/RANT]
> >
> > I see your point, but you have reduced your browser width to about
> > 46 columns, and zoomed in the font until the effect started to
> appear.
> >
> > How realistic is that? All my browsers are always maximized, and the
> > font set to the default. I use Ctrl+NumPlus copiously, when not
> > wearing glasses, for example, and I rarely see this effect.

This looks like a fairly normal screenshot taken on a high-resolution smartphone screen; and so, very realistic — albeit not typical for this specific forum, perhaps. :-)


> > On what device/OS did you capture this? I went to my OP and had a
> > hard time reproducing it on Windows -- until I reduced my browser's
> > width
> > to ridiculously low. I'll try with my Android and iOS browsers to
> see
> > when/if the effect appears.
> >
> >
> 123456789*123456789*123456789*123456789*123456789*123456789*123456[70]
> > I think I insert hard CRs at about 65-70 (didn't count), and review
> > before posting. This width allows me to see what I'm thinking and
> > typing, as I tend to write long sentences. Habits from being
> > very aware of the 80 column limit in the days of terminals.
> >
> > If this habit is screwing up threads and hurting information
> > exchange, I'm willing to adapt.

To be fair, this problem is not really caused by Slobodan, but by the forum software, which has a fairly simplistic way of editing replies in a post (modeled on the convention from back in the days of plain text e-mails, usenet, etc.)
Replies really ought to be quoted in <blockquote>-tags, which could then be styled to clearly mark the different quoting levels (example). But that would probably require extensive rewriting of the forum software. :-)


> No real need to adapt, Slo. Not as big a deal as I've let on. But
> you actually did much better this time. Smaller font? That screenshot
> was taken on my 10" Android tablet, just as the one below was.
>
> Personally, I think CRs inserted into text are a lost cause. With the
> 'net on everything from phones to widescreen PCs, there is no reasonably
> standard width any more. From the first word processor I found in the
> early '80s that autowrapped I've rarely tried to manually wrap text.
> Let the receiving software/device/aspect ratio wrap it as it will. It
> will more often do a better job than my feeble efforts.

Agreed. All the more so because most techniques that are being used today to display text (plain text, RTF, HTML, markdown et al.; and the appropriate multiline editing controls in all OSes) have been in use since at least two decades, and have supported ‘soft’ line breaks and ways to avoid the need to insert line breaks for all of those two decades.


--
Martijn

188 views      
Thread locked
 

Messages in this Thread

 
94,593 Postings in 11,933 Threads, 348 registered users, 24 users online (1 registered, 23 guests)
Index | Admin contact |   Forum Time: Nov 22, 2019 - 7:08 am EST  |  Hits:29,233,998  (8,676 Today )
RSS Feed