On Sat, May 20, 2017, at 19:18, Gavin Smith wrote: > On Mon, May 15, 2017 at 10:09:26PM +0200, Benno Schulenberg wrote: > > 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.
Correct. That is how it is supposed to work. But sometimes there is a maintainer who thinks he can edit PO files to his liking. > So if > translators did put full stops at the ends of messages, I wouldn't > complain about it. Good. By the way, you didn't change the feedback messages about being on the first or last node. Why? > > 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. Even if it were just one sentence, it's far better /with/ a period. Or really: it is only /correct/ with a period. > 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. Yes, those option descriptions shouldn't end in a period -- it is the usual style, /and/ a period is incorrect when a phrase doesn't start with a capital. Benno -- http://www.fastmail.com - Accessible with your email software or over the web
