News for hackers. Stuff that matters.
Re:This is a regular text file. People will read it. Maybe. by pyre on Sunday June 23, 2013 @07:33AM (#5927110)
Of course not. You could write it in RTF.
Re:This is a regular text file. People will read it. Maybe. by DanBC on Sunday June 23, 2013 @08:32AM (#5927321)
You could write it in plain text and only have line breaks when fitting a new paragraph, leaving it up to the user's software to wrap the lines.
Re:This is a regular text file. People will read it. Maybe. by agargarg on Sunday June 23, 2013 @09:07AM (#5927425)
But it wouldn't handle indentation properly, unless you define a standard formatting convention similar to Markdown. For example, you need to handle bullet points. But what if a plain, non-indented text just happens to contain a star at the start of a line? This means headaches for text writers to avoid these edge cases, and wrong indentation when viewing legacy texts.

Also, all viewers would have to support it, which somewhat defeats the purpose of using plain text.

Re:This is a regular text file. People will read it. Maybe. by DanBC on Sunday June 23, 2013 @09:42AM (#5927519)
> But it wouldn't handle indentation properly

8 spaces is fine.

> For example, you need to handle bullet points.

Asterisks are fine.

> Also, all viewers would have to support it, which somewhat defeats the purpose of using plain text.

I think that you're over thinking what plain text is. I don't mean "plain text with some additions". I really do just mean plain text.

Re:This is a regular text file. People will read it. Maybe. by agargarg on Sunday June 23, 2013 @11:17AM (#5927830)
> 8 spaces is fine.

I'm not talking tab characters, I'm talking indentation of whole paragraphs with plain spaces, as seen in the article. Most existing viewers just wrap long lines so that the wrapped content is unindented: this makes any indentation hard to notice and mostly useless. For your proposition to be viable, viewing software has to detect indentation and keep that indentation in wrapped lines.

> Asterisks are fine.

Ok, but usually you want to indent the wrapped contents by 2 columns otherwise asterisks become hard to notice. This is only possible with special magic in the viewer.

Re:This is a regular text file. People will read it. Maybe. by agargarg on Sunday June 23, 2013 @11:43AM (#5927945)

  --- BEGIN MESSAGE ---
  --- BEGIN BLOCK QUOTE ---
  --- BEGIN BLOCK QUOTE ---
  I'm not talking tab characters, I'm talking indentation of whole paragraphs
  with plain spaces, as seen in the article.
  --- END BLOCK QUOTE ---
  Ah, okay. You're right, indenting an entire paragraph is hard.
  --- BEGIN BLOCK QUOTE ---
  This is the kind of thing they'd do on Usenet.
  --- END BLOCK QUOTE ---
  --- END BLOCK QUOTE ---
  All you get is a very verbose markup language :-)
  --- END MESSAGE ---
Re:This is a regular text file. People will read it. Maybe. by DanBC on Sunday June 23, 2013 @11:23AM (#5927848)
> I'm not talking tab characters, I'm talking indentation of whole paragraphs with plain spaces, as seen in the article.

Ah, okay. You're right, indenting an entire paragraph is hard.

--- BEGIN BLOCK QUOTE ---

This is the kind of thing they'd do on Usenet.

---END BLOCK QUOTE ---

Re:This is a regular text file. People will read it. Maybe. by angersock on Sunday June 23, 2013 @10:24AM (#5927648)
Sometimes there is no replacement for just a big honking array of ASCII.
Re:This is a regular text file. People will read it. Maybe. by kylec on Sunday June 23, 2013 @01:08PM (#5928327)
This is the best solution, because you never know how large the text will be when rendered by the user's software. For example, this is how it rendered on my iPad:

http://cl.ly/Pp7I

It looks terrible, and I didn't read it, effectively falsifying the article.