From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <gmazyland@gmail.com>
Received: from mail-lb0-x242.google.com (mail-lb0-x242.google.com
 [IPv6:2a00:1450:4010:c04::242])
 (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits))
 (No client certificate requested)
 by mail.server123.net (Postfix) with ESMTPS
 for <dm-crypt@saout.de>; Mon, 23 May 2016 10:41:42 +0200 (CEST)
Received: by mail-lb0-x242.google.com with SMTP id r5so8542592lbj.3
 for <dm-crypt@saout.de>; Mon, 23 May 2016 01:41:42 -0700 (PDT)
References: <CAFPa+Sk5WET-E+CD3K5WRxj4Sq3+Lkbkj5ka26iKL2qf9kdE7Q@mail.gmail.com>
From: Milan Broz <gmazyland@gmail.com>
Message-ID: <5742C243.90101@gmail.com>
Date: Mon, 23 May 2016 10:41:39 +0200
MIME-Version: 1.0
In-Reply-To: <CAFPa+Sk5WET-E+CD3K5WRxj4Sq3+Lkbkj5ka26iKL2qf9kdE7Q@mail.gmail.com>
Content-Type: text/plain; charset=windows-1252
Content-Transfer-Encoding: 7bit
Subject: Re: [dm-crypt] A couple of strings that could be reviewed
List-Id: <dm-crypt.saout.de>
List-Unsubscribe: <http://www.saout.de/mailman/options/dm-crypt>,
 <mailto:dm-crypt-request@saout.de?subject=unsubscribe>
List-Archive: <http://www.saout.de/pipermail/dm-crypt/>
List-Post: <mailto:dm-crypt@saout.de>
List-Help: <mailto:dm-crypt-request@saout.de?subject=help>
List-Subscribe: <http://www.saout.de/mailman/listinfo/dm-crypt>,
 <mailto:dm-crypt-request@saout.de?subject=subscribe>
To: Rafael Fontenelle <rffontenelle@gmail.com>, dm-crypt@saout.de


On 05/20/2016 10:24 AM, Rafael Fontenelle wrote:
> Hello there!
> 
> I'm currently translating cryptsetup to Brazilian Portuguese and
> notice a small detail in two strings that maybe you want to take a
> look at.
> 
> First is "Cannot open device %s\n", in file
> src/cryptsetup_reencrypt.c, line 154.  I believe a full stop/period
> punctuation would be welcome in there, since other messages nearby
> have it. Please take a look in the catalog messsages file (a.k.a
> translation file).

Hi,

yes, it should be the same as other messages (despite punctuation
could be confusing as already mentioned).
Anyway, messages should not alternate according to random context.

I'll fix it, but it is not worth to submit translation file for 1.7.2 again
(the proper string is already there).

> Second is "Cannot use passed UUID unless decryption in progress.\n",
> in file src/cryptsetup_reencrypt.c, line 1180.  My interpretation of
> it is that decryption must not be in progress to be allowed passing
> UUID.  If I'm correct, then I suggestion adding a "is" in
> "..decryption IS in progress".

Quite terse error message, missed that :) It should be more like
  "Provided UUID can be used only when resuming decryption."

Man page description is

--uuid <uuid>
  Use only while resuming an interrupted decryption process (see --decrypt). 

Will fix this in next version, that message is very rare...

Thanks!
Milan