esd-translators
[Top][All Lists]
Advanced

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

Re: [ESD-translators] Proposed changes in sections 1 and 2


From: Zoë Kooyman
Subject: Re: [ESD-translators] Proposed changes in sections 1 and 2
Date: Wed, 11 Aug 2021 21:03:23 +0200
User-agent: Mozilla/5.0 (X11; Linux x86_64; rv:78.0) Gecko/20100101 Icedove/78.11.0

Hi!

Apologies for the slow response. See my comments below on the changes.
thanks!

On 03.08.21 18:02, Thérèse Godefroy wrote:
Hello Zoë, hello everybody,

I found a few inconsistencies:

* In Step 1.A

   If you already have an email program, you can skip to
   <a href="#section2">Step 2</a>.

Not really. What you need is an email program with your account set up.
And if you are using macOS or Windows, you still need to go through Step
1B. So, the correct wording would be:

  If you already have an email program with your account set up, and are
  running GNU/Linux, you can skip to <a href="#section2">Section 2</a>.

Why not simply delete this complicated sentence? People who already have
their account set up are not going to set it up once more. They will
scroll down a few lines to step 1B, and then skip to Section 2 if they
are using GNU/Linux.
I am ok with this change.

* In Step 1.B

- s/Step 2/Section 2/  (Step 2 doesn't exist.)

- We probably don't need to mention PowerShell here. This will just
scare Windows users away.
   --> Remove the note?
I am ok with this change.
* In Step 2.A [**]

It's kind of awkward to intercalate a note between a phrase which ends
with a colon, and the list that is supposed to follow.

Proposed rewording:

   <p>We will use the command line in a terminal to create a keypair
   using the GnuPG program.</p>

   <p class="notes">A terminal is installed by default on most
   GNU/Linux systems; if you are on macOS, use "Terminal", as in
   Step 1.B; if you are on Windows, use a program named "PowerShell".
   You can launch your terminal from the Applications menu, or (on
   some GNU/Linux systems) with the <kbd>Ctrl + Alt + T</kbd>
   shortcut.</p>

   <p># Enter <code>gpg --full-generate-key</code> to start the
   process.</p>
   ...
   <p># Choose the expiration date;  we suggest...

(Semi-colon instead of comma between 2 complete sentences.)
I am good with all this as well, but it should say "PowerShell" (2 caps)

* Minor typos:

In Step 2.B - Advanced:
   Refer to <a href="#step-2b">*troubleshoot* in step 2.B</a>...
   --> Refer to <a href="#step-2b">Troubleshooting in Step 2.B</a>

In Step 3.A:  s/step 2.b/Step 2.B/
OK

I pushed a new version to enc.

All the best,
Thérèse
Thanks Therese


[**] *NOTE about Step 2.A*

This part may scare away quite a few "normal" users, for no good
reason: it is very easy to generate a strong key from the OpenPGP Key
Manager of Thunderbird. No typing is needed if you already have an
email account.

Tools > OpenPGP Key Manager > Generate > New key pair
Identity: autocompleted.
Expiration date: 3y by default (choose from a dropdown list).
Type: RSA (default) or ECC
Size: 3072 (default) or 4096.

The whole process took me less than 30 seconds.

Importing and exporting public and private keys can also be done from
Thunderbird. The only thing that seems to require a terminal is the
revocation certificate.
We are working on expanding the guide further, and this could be part of it. We looked at it a bit, but as I understand it the Thunderbird key creation allows you to use the key only in Thunderbird, at this time there are some functionalities that are not ideal yet - Thunderbird uses its own copy of keys, and doesn't support synchronizing keys with GnuPG.

Thanks!







reply via email to

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