[prev in list] [next in list] [prev in thread] [next in thread] 

List:       gnupg-i18n
Subject:    Re: Standard or Default?
From:       Werner Koch <wk () gnupg ! org>
Date:       2023-11-30 16:08:52
Message-ID: 8734wnxlyj.fsf () jacob ! g10code ! de
[Download RAW message or body]

[Attachment #2 (multipart/signed)]


Hi!

> Should this lines, instead of being written as "standard keys" or as
> "standard options", have been written as "default keys" and "default
> options" ?

Good question.  We recently talked about this for the German translation
and came to no conclusion what to use.

In this case we are talking about the commonly used PIN for a certain
smartcard.  Given that we use the same prompt for all types of
smaretcards and tokens, it is not easy to find a name.  Some card
vendors and their sales documentaion name this "User PIN", others just
"PIN", "Encryption PIN" (which of course is for decryption), or "PIN-1".

Thus we weasel out by using "standard" to mean whatever PIN is used for
common operations with the card.

The other use case is:

  #: tools/gpg-connect-agent.c:2259
  #, c-format
  msgid "error sending standard options: %s\n"
  msgstr "Fehler beim Senden der Standardoptionen: %s\n"

which really means the standard options which are always sent to the
agent after setting up a connection.  Not actually spmething which needs
a translation because it is a rare error diagnostic.


Shalom-Salam,

   Werner

-- 
The pioneers of a warless world are the youth that
refuse military service.             - A. Einstein

["openpgp-digital-signature.asc" (application/pgp-signature)]

_______________________________________________
Gnupg-i18n mailing list
Gnupg-i18n@gnupg.org
http://lists.gnupg.org/mailman/listinfo/gnupg-i18n


[prev in list] [next in list] [prev in thread] [next in thread]