[Pkg-shadow-devel] Bug#812127: login: wrong German error message

[Bálint Réczey]

Hi Holger,

2017-02-06 20:12 GMT+01:00 Holger Wansing <linux at wansing-online.de>:
> Hi,
>
> Bálint Réczey <balint at balintreczey.hu> wrote:
>> Hi Helge,
>>
>> 2017-01-21 17:15 GMT+01:00 Helge Kreutzmann <debian at helgefjell.de>:
>> > Hello Holger,
>> > On Sat, Jan 21, 2017 at 11:41:43AM +0100, Holger Wansing wrote:
>> >> Helge Kreutzmann <debian at helgefjell.de> wrote:
>> >> > On Fri, Jan 20, 2017 at 09:19:34PM +0100, Balint Reczey wrote:
>> >> > > My wife says the proposed solution does not sound good and I don't speak
>> >> > > German thus I can't make a decision here. :-)
>> >> >
>> >> > The incorrect translation is probably caused by a misunderstanding of
>> >> > the translator (I put him explicitly in CC).
>> >> >
>> >> > I believe you mean:
>> >> > Under no cirumstance work is possible without effective root.
>> >>
>> >> This means, the english version is incorrect too, right?
>> >> Since in english it says "Cannot possibly work ...", and that means
>> >> something like "möglicherweise" or "eventuell" or "unter Umständen".
>> >
>> > No. In this place »possibly« does not mean »perhaps«. It rather means
>> > »at all«.
>> >
>> > This is, if the text was produced by a good or native speaker. Thus my
>> > uncertainty.
>> >
>> >> What do you think, is the correct english meaning, which is intended here?
>> >
>> > As stated, I (rather firmly) believe
>> >> Under no cirumstance work is possible without effective root.
>>
>> IMO this is the correct interpretation.
>>
>> The place where the message is emitted is here:
>> http://sources.debian.net/src/shadow/1:4.4-3/src/login.c/?hl=567#L567
>
> So you should probably change the phrase in English too, to ensure it
> is understood correctly? (Maybe other translators have misinterpreted it
> too?)

The freeze is not a great time for making changes to the original strings. :-)
Let's defer the resolution of this bug after Stretch is released.

Login may be provided by util-linux per #833256 and in that case I don't wan't
to ask l10n teams to update a string in every language before that string goes
away.

Cheers,
Balint