mirror of
git://git.gnupg.org/gnupg.git
synced 2025-07-03 22:56:33 +02:00
w32: Always use Unicode for console input and output.
* common/init.c (_init_common_subsystems) [W32]: Set the codepage to
UTF-8 for input and putput. Switch gettext to UTF-8.
* g10/gpg.c (utf8_strings) [W32]: Make sure this is always set.
--
With this patch the former patch to use ReadConsoleW and WriteConsoleW
in ttyio.c are kind of superfluous because the ANSI version of these
functions are also able to read/write UTF-8 directly given the console
code page has been set correctly. However, this seems to work only
with recent versions of Windows-10.
GnuPG-bug-id: 4365
(cherry picked from commit 8c41b8aac3
)
Removed changes for "gpgconf --show-codepages" of the original patch.
This commit is contained in:
parent
ebdb62a98a
commit
b912f07cdf
3 changed files with 36 additions and 8 deletions
19
doc/gpg.texi
19
doc/gpg.texi
|
@ -1532,13 +1532,14 @@ not used).
|
|||
|
||||
@item --display-charset @var{name}
|
||||
@opindex display-charset
|
||||
Set the name of the native character set. This is used to convert
|
||||
some informational strings like user IDs to the proper UTF-8 encoding.
|
||||
Set the name of the native character set. This is used to convert some
|
||||
informational strings like user IDs to the proper UTF-8 encoding.
|
||||
Note that this has nothing to do with the character set of data to be
|
||||
encrypted or signed; GnuPG does not recode user-supplied data. If
|
||||
this option is not used, the default character set is determined from
|
||||
the current locale. A verbosity level of 3 shows the chosen set.
|
||||
Valid values for @var{name} are:
|
||||
encrypted or signed; GnuPG does not recode user-supplied data. If this
|
||||
option is not used, the default character set is determined from the
|
||||
current locale. A verbosity level of 3 shows the chosen set. This
|
||||
option should not be used on Windows. Valid values for @var{name}
|
||||
are:
|
||||
|
||||
@table @asis
|
||||
|
||||
|
@ -1575,6 +1576,12 @@ encoded in the character set as specified by
|
|||
arguments. Both options may be used multiple times.
|
||||
This option should not be used in an option file.
|
||||
|
||||
This option has no effect on Windows. There the internal used UTF-8
|
||||
encoding is translated for console input and output. The command line
|
||||
arguments are expected as Unicode and translated to UTF-8. Thus when
|
||||
calling this program from another, make sure to use the Unicode
|
||||
version of CreateProcess.
|
||||
|
||||
@anchor{gpg-option --options}
|
||||
@item --options @var{file}
|
||||
@opindex options
|
||||
|
|
Loading…
Add table
Add a link
Reference in a new issue