All of lore.kernel.org
 help / color / mirror / Atom feed
From: Milan Broz <gmazyland@gmail.com>
To: Rafael Fontenelle <rffontenelle@gmail.com>, dm-crypt@saout.de
Subject: Re: [dm-crypt] A couple of strings that could be reviewed
Date: Mon, 23 May 2016 10:41:39 +0200	[thread overview]
Message-ID: <5742C243.90101@gmail.com> (raw)
In-Reply-To: <CAFPa+Sk5WET-E+CD3K5WRxj4Sq3+Lkbkj5ka26iKL2qf9kdE7Q@mail.gmail.com>


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

  parent reply	other threads:[~2016-05-23  8:41 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-05-20  8:24 [dm-crypt] A couple of strings that could be reviewed Rafael Fontenelle
2016-05-21 12:36 ` Michael Kjörling
2016-05-23  8:41 ` Milan Broz [this message]
2016-05-23 15:28   ` Rafael Fontenelle

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=5742C243.90101@gmail.com \
    --to=gmazyland@gmail.com \
    --cc=dm-crypt@saout.de \
    --cc=rffontenelle@gmail.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.