Skip site navigation (1)Skip section navigation (2)
Date:      Thu, 29 Nov 2012 13:30:34 +0000
From:      Chris Rees <utisoft@gmail.com>
To:        Emanuel Haupt <ehaupt@freebsd.org>
Cc:        svn-ports-head@freebsd.org, svn-ports-all@freebsd.org, Alexey Dokuchaev <danfe@freebsd.org>, ports-committers@freebsd.org
Subject:   Re: svn commit: r307951 - head/sysutils/sleuthkit
Message-ID:  <CADLo83_czXHfckjp1%2BG0TKmY49bySYFUhpgf1M%2BH___T%2BPT8_A@mail.gmail.com>
In-Reply-To: <20121129130147.c5fcd6296c6bd967ca0745e4@FreeBSD.org>
References:  <201211290020.qAT0Kecl058401@svn.freebsd.org> <20121129020924.GC11624@FreeBSD.org> <20121129034450.f0d1802f0dd0c5c2396d1ebd@FreeBSD.org> <20121129032332.GA17732@FreeBSD.org> <20121129130147.c5fcd6296c6bd967ca0745e4@FreeBSD.org>

next in thread | previous in thread | raw e-mail | index | archive | help
On 29 Nov 2012 12:02, "Emanuel Haupt" <ehaupt@freebsd.org> wrote:
>
> Alexey Dokuchaev <danfe@FreeBSD.org> wrote:
> > On Thu, Nov 29, 2012 at 03:44:50AM +0100, Emanuel Haupt wrote:
> > > I would say this is opinionated. I think it looks better that way.
> > > I've always removed double spaces (which most of the time were
> > > introduced trough copy pasting from webpages/manpages) in the past.
> >
> > And others were adding them back.  This is totally bogus situation, we
> > should not adhere to different standards.
> >
> > Also 80-char limit is normally should be lowered down to 78 or even
>
> As 'the dude' would say:
>         "yeah well, that's just like your opinion man"
>
> > 76 in some case if formatting looks better (more even at the right
> > edge), previous version complied to this as well.  Now 'Mac' in the
> > line 7 touches the screen edge; the whole right edge is uneven.  You
> > still thing it looks better, seriously?
>
> To me yes. The terminals xterm, rxvt, aterm, eterm all have a 80
> character width:
>
>
http://critical.ch/people/fbsd/standard-term-width-settings-xterm-rxvt-aterm-eterm.png
>
> > > --- begin quote ---
> > > Please be careful if you are copying from the README or manpage; too
> > > often they are not a concise description of the port or are in an
> > > awkward format (e.g., manpages have justified spacing).
> > > --- end quote ---
> >
> > Correct, because justified spacing normally does look ugly with
> > monospaced fonts.  Double spacing (at the sentense breaks), on the
> > contrary, makes it look better.  Please reconsider.  I put a lot of
>
> Again: "your opinion"
>
> > thought into our port descriptions and it's really sad to see my work
> > destroyed.
>
> FreeBSD is a large project with > 400 committers and many more highly
> motivated active contributors. I would suggest you get familiar with
> the concept of people having different opinions. Accusing others of not
> caring or destroying "your work" (really? please...) is just rediculous.

English text is rendered by LaTeX with double spaces between sentences (not
always after periods).  Other languages (French for example) are not.

Whatever your opinion on the matter, standard technical English should have
double spaces after periods in monospaced fonts.  Of course, word processed
text may be different, but that is not normally monospaced.

Chris



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CADLo83_czXHfckjp1%2BG0TKmY49bySYFUhpgf1M%2BH___T%2BPT8_A>