Nice, I like text files.
Paragraph width is a little too wide for me, however.
I assume you made the line breaks manually,
but it IMHO looks better if you let a decent
algorithm do it.
Most Unix systems should have fmt, but par is
better. If you are a vim user, just hit gqip
inside of every paragraph.
The manual of par [1] has an example that shows the superiority of a dynamic programming algorithm (par, TeX) over a greedy algorithm (fmt, aprox. format manually).
Nice, I like text files. Paragraph width is a little too wide for me, however.
This is why we need markup languages like HTML. Inevitably people will want different widths paragraphs due to different devices, preferences, etc. Just because some people use HTML badly doesn't mean we need to go back to text.
Ideal paragraph width is not a function of device display size. A line of text should contain about 12 words, give or take. Long enough to not feel choppy but short enough to not feel like a "wall of text."
Deviate too much from this and readability suffers.
Edit: adequate whitespace in the margins is important too.
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.
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.
--- 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 ---
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:
You Europeans have things too easy with your metric paper sizes and sales tax included in displayed prices and standardized road signage and drinkable beer and functional healthcare systems. We'll stick with PDFs, and fluid ounces, and trying to calculate 18% of pretax dinner tabs thanks. Excuse me while I go fight with my health insurance company over my last doctor bill.
I'd say it's more than fine. I just spent three weeks in Europe and I was underwhelmed by the beer everywhere except Munich, Berlin, and Copenhagen (Mikeller was great). Foreigners seem to think of American beer as PBR, Bud Light, Miller, etc... and they have a good reason to--it's what most Americans drink.
But the strong microbrew renaissance going on right now is producing some of my favorite beers. Beers with the same depth and complexity as the finest of wines--he said, opinionatedly.
Now, I've learned that this experimental attitude towards beer is highly American. I don't think I've seen anywhere else in the world, except maybe Belgium, that is quite as crazy and experimental with what they put in their beers. After all, who in their right minds would like sour beers?
If you think the beer situation in the US is poor try out some Russian River, Boulevard, or Elysian brews and come back to me.
gqG also does violence to some plain-text formatting, such as numbered lists or other short sections in which a specified line length or presentation is preferred.
Long lines and wrapping within the text viewer is probably your best bet.
Comments
Nice, I like text files. Paragraph width is a little too wide for me, however.
I assume you made the line breaks manually, but it IMHO looks better if you let a decent algorithm do it.
Most Unix systems should have fmt, but par is better. If you are a vim user, just hit gqip inside of every paragraph.
The manual of par [1] has an example that shows the superiority of a dynamic programming algorithm (par, TeX) over a greedy algorithm (fmt, aprox. format manually).
[1] http://www.nicemice.net/par/par-doc.var
This is why we need markup languages like HTML. Inevitably people will want different widths paragraphs due to different devices, preferences, etc. Just because some people use HTML badly doesn't mean we need to go back to text.
Ideal paragraph width is not a function of device display size. A line of text should contain about 12 words, give or take. Long enough to not feel choppy but short enough to not feel like a "wall of text."
Deviate too much from this and readability suffers.
Edit: adequate whitespace in the margins is important too.
Because HTML is the only way you can have variable paragraph width?
Of course not. You could write it in RTF.
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.
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.
8 spaces is fine.
Asterisks are fine.
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.
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.
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.
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 ---
Sometimes there is no replacement for just a big honking array of ASCII.
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.
People who want to modify paragraph widths and mess with the designer's vision are why we need PDF.
As a European designer who hates the fact that so many PDFs are in US letter format: fuck designers.
You Europeans have things too easy with your metric paper sizes and sales tax included in displayed prices and standardized road signage and drinkable beer and functional healthcare systems. We'll stick with PDFs, and fluid ounces, and trying to calculate 18% of pretax dinner tabs thanks. Excuse me while I go fight with my health insurance company over my last doctor bill.
If you're implying that the US doesn't produce drinkable beer, I'd humbly suggest you're going to the wrong bars :).
It's true that the beer situation in the US is just fine these days.
I'd say it's more than fine. I just spent three weeks in Europe and I was underwhelmed by the beer everywhere except Munich, Berlin, and Copenhagen (Mikeller was great). Foreigners seem to think of American beer as PBR, Bud Light, Miller, etc... and they have a good reason to--it's what most Americans drink.
But the strong microbrew renaissance going on right now is producing some of my favorite beers. Beers with the same depth and complexity as the finest of wines--he said, opinionatedly.
Now, I've learned that this experimental attitude towards beer is highly American. I don't think I've seen anywhere else in the world, except maybe Belgium, that is quite as crazy and experimental with what they put in their beers. After all, who in their right minds would like sour beers?
If you think the beer situation in the US is poor try out some Russian River, Boulevard, or Elysian brews and come back to me.
As a Dutch man, I think our beer is highly overrated. Belgian and German beers are great though.
Do i really need to explicitly flag my remark as sarcastic? Apparently so.
Or just use
to start with.I like the playfulness of these pages (the original and this parody) and I hope both authors achieve their aims.
The worst thing isn't that it's too wide but that the line length is inconsistent.
Call me rough, but I still wrap my papers with fold.
M-x autofill-mode
gggqG - wraps the entire document
Good call, but it does violence to the ASCII creature:-(
That's why I suggested gqip on every paragraph, but I'm sure there are more efficient ways.
Could you place the cursor just above the ASCII art and then wrap from there to the top of the document?
For that, you could place the cursor above the ASCII art; press (ma) to set marker 'a'; (gg) to go to the top; (gq`a) to wrap until marker a. ;)
gqG also does violence to some plain-text formatting, such as numbered lists or other short sections in which a specified line length or presentation is preferred.
Long lines and wrapping within the text viewer is probably your best bet.
Ah, I do see your point!
Why three g's at the beginning?
(g) invokes extra commands. here two are used: (gg) places the cursor at the top. (gq) wraps the text until (G) the end of the document.