libtool-patches
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: How many spaces after a period? [WAS: Re: [PATCH 7/7] Prefer $NM @fi


From: Ralf Wildenhues
Subject: Re: How many spaces after a period? [WAS: Re: [PATCH 7/7] Prefer $NM @file over calculating the cmd line length.]
Date: Sun, 12 Sep 2010 11:37:31 +0200
User-agent: Mutt/1.5.20 (2010-04-22)

Hi Gary,

* Gary V. Vaughan wrote on Sun, Sep 12, 2010 at 11:23:52AM CEST:
> On 12 Sep 2010, at 15:01, Ralf Wildenhues wrote:
> > * Peter Rosin wrote on Sat, Sep 11, 2010 at 02:24:18PM CEST:
> >> * libltdl/config/ltmain.m4sh (func_mode_link): Avoid calculating
> >> the command line length and take the @file branch *if* the file
> >> names needs to be converted for the toolchain and the @file
> >> branch works. Fixes stresstest.at when doing a cross from Cygwin
> > 
> > Two spaces after period.
> 
> Only for texinfo markup I believe, since two spaces after a period are
> widely regarded as typographically bad (see the following and the
> reports it cites at the end):
> 
>     http://webword.com/reports/period.html

Maybe.  I thought the two spaces were so that emacs would correctly jump
a sentence ahead; guess that's not needed any more now.

FWIW I consider two spaces to really improve readability in fixed-width
font.[1]  All proportional renderers are better off because they can
just increase the space by a little.  The above URL admits that two
spaces are better for fixed-with.

Thanks,
Ralf

[1] I also regard lines in email wrapped at 72 chars highly improving
readability, by the way.  ;->



reply via email to

[Prev in Thread] Current Thread [Next in Thread]