svn commit: r307951 - head/sysutils/sleuthkit

[Marcus von Appen]

Zitat von Chris Rees <utisoft at gmail.com>:

> On 29 Nov 2012 12:02, "Emanuel Haupt" <ehaupt at freebsd.org> wrote:
>>
>> Alexey Dokuchaev <danfe at 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

And that's your personal opinion. I could introduce you to 5 typographers,
who would give you 8 different opinions on that topic :-).

Cheers
Marcus
(who feels sorry to answer as well and will (or will not) ignore any further
comment on that topic)