[Top][All Lists]

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

Re: [patch] info: error messages in echo area want a period

From: Gavin Smith
Subject: Re: [patch] info: error messages in echo area want a period
Date: Sat, 20 May 2017 18:18:14 +0100
User-agent: Mutt/1.5.23 (2014-03-12)

On Mon, May 15, 2017 at 10:09:26PM +0200, Benno Schulenberg wrote:
> On Mon, May 15, 2017, at 18:22, Gavin Smith wrote:
> > I couldn't find any discussion online of why the recommendation was
> > made.  You can make arguments either way but ultimately it is a question
> > of taste.
> Okay.  If you will leave the periods in translations alone.

Translations are organised separately through the Translation Project, 
as you know, and what happens in translations is a matter for the 
language communities and translators involved.  Developers of projects 
using the TP for translations don't tell translators what to do.  That's 
my understanding of how it is supposed to work, anyway.  So if 
translators did put full stops at the ends of messages, I wouldn't 
complain about it.

> Hm.  Are you suggesting that also info's very first message should
> be stripped from its periods?
>   Welcome to Info version 6.3.90.  Type H for help, h for tutorial.

That's not possible because it is two sentences.

> Or the docstring from --help?
>   Read documentation in Info format.

Maybe, but it appears to be usual to have a full stop there or
to have several sentences.

I'm more concerned about lines like

  -a, --all                    use all matching manuals.

from the --help text, which possibly shouldn't end in a full stop.
It appears to be usual for such lines not to.

reply via email to

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