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

(forw) Bug#189487 acknowledged by developer (Re: Bug#189487: lire: Typo in package description)



(please keep me CC'ed to answers if possible. I never remember which
mail header is supposed to ask for this)

Hello folks,

I need your advice on the following topic :

In #189487, I mention the presence of double spaces after dots ending
sentences in the lire package debconf templates.

Would this be in french sentences, I would have considered it a bug
without any doubt. The french typography is clear on that topic :
after one dot, there should be only one space character.

As I have a small doubt, I prefer asking to this list : is "double
space after dot" correct english typography?

I suspect it isn't, but I prefer having some confirmation before
reopening the bug.

>From the bug log :

On Fri, Apr 18, 2003 at 10:33:26AM +0200, Christian Perrier wrote:
>=20
> While translating the new package description into french, I found the
> following very minor typo. Two spaces instead on one, below :
>=20
>  supported.  Reports can be generated in ASCII format, as well as in
>            ^^

This is done consistently:

 one's system.  Currently, exim, sendmail, qmail, postfix, bind,
 ...
 HTML or PDF and other formats.  Logs can be read from the local system

The hello package uses two spaces after each line too:

 The GNU hello program produces a familiar, friendly greeting.  It

=2E  It is common style to have two spaces after every sentence-ending
dot.  Therefore, I consider this not a bug.

Thanks anyway for your bugreport, Bye,

Joost

PS: I've been searching for a good URL to some standard style guide
backing this up, but failed.  I didn't get any closer than
http://webster.commnet.edu/ , http://www.bartleby.com/141/ and
http://newark.rutgers.edu/~jlynch/Writing/ .

--=20
=2E    .                                        http://logreport.com/
| '.|                        /^LogReport$/
| Lire                                        http://logreport.org/




Reply to: