Date: Thu, 29 Nov 2012 03:23:32 +0000 From: Alexey Dokuchaev <danfe@FreeBSD.org> To: Emanuel Haupt <ehaupt@FreeBSD.org> Cc: svn-ports-head@FreeBSD.org, svn-ports-all@FreeBSD.org, ports-committers@FreeBSD.org Subject: Re: svn commit: r307951 - head/sysutils/sleuthkit Message-ID: <20121129032332.GA17732@FreeBSD.org> In-Reply-To: <20121129034450.f0d1802f0dd0c5c2396d1ebd@FreeBSD.org> References: <201211290020.qAT0Kecl058401@svn.freebsd.org> <20121129020924.GC11624@FreeBSD.org> <20121129034450.f0d1802f0dd0c5c2396d1ebd@FreeBSD.org>
next in thread | previous in thread | raw e-mail | index | archive | help
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 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? > --- 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 thought into our port descriptions and it's really sad to see my work destroyed. ./danfe
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20121129032332.GA17732>