Re: "One sentence per line"

Jean Jordaan <[email protected]> Wed, 11 Apr 2012 15:09:42 +0700
Newsgroups gmane.comp.web.zope.plone.documentation
Message-ID <CAJqnznCji_WUPtTXkRw6xj5HeM53DcmkiA1kFSCK+pkB0Xap0A@mail.gmail.com>
On Tue, Apr 10, 2012 at 10:03 PM, Mikko Ohtamaa
<mikko+plone-75aZqqp77KCaMPzRcYMCawC/[email protected]> wrote:
>> short, ragged lines, and not reflowing paragraphs, for ease of editing &
>> versioning.
>
> Personally I don't care

Good :-)

While going through the dexterity manual, I formatted the last part
in that way. See the pull request:
  https://github.com/giacomos/collective.dexteritymanual/pull/1

> * Modern editors can wrap lines (take that, pico!)

Yeah, but I think that wrapping paragraphs is often counterproductive for t=
ext
source files.

> * Also some people tend to justify text with somewhat sane line width
> (60-160)

When the text source is meant to be read by many (e.g. README files), that =
make
sense. When it is mainly the source format for publication in other formats,
then not so much.

-- =

jean=A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0=
 =A0 =A0 =A0 =A0 =A0 . .. .... //\\\oo///\\

---------------------------------------------------------------------------=
---
Better than sec? Nothing is better than sec when it comes to
monitoring Big Data applications. Try Boundary one-second =

resolution app monitoring today. Free.
http://p.sf.net/sfu/Boundary-dev2dev