- UTF-8 handling when LANG=C
- In some situations, with LANG=C, some people expect UTF-8 (or no-translation) on POSIX, these days
- With LANG=C, nl_langinfo (CODESET) returns ASCII (ANSI_X3.4-1968) (on GNU/Linux)
- So, currently, it is handled as iso-8859-1 by GnuPG
- In future, possibly, it would make sense to change behavior of this corner case, adding special handling of LANG=C
- When LANG=C or LC_CTYPE=C is detected, it is handled as UTF-8, instead of iso-8859-1
- Or, emit a warning that it defaults to iso-8859-1 and to suggest an option of --utf8-strings
- UTF-8 things: T1514: charset weirdness with non-ascii User IDs under non-UTF-8 locales & T5038: UTF-8 handling in the command line
- For future development: T5034: dev: Deprecate libassuan-config, libgcrypt-config, ksba-config, ntbtls-config, npth-config, ang gpg-error-config
- Minor fixes & update
- Gnuk fixes for passphrase check
- Examine the error path(s) of UI of gpg --card-edit and gpg-card, so that it won't confuse users much.
--utf8-strings is usuallay the default, so your suggestion to assume utf-8 is a good one. Let's do that for 2.3.
- Released ntbtls
- Released gnupg 2.2.22
- Work on 2.3
- Fix fallout from 2.2.22.