gnupg-1.0.2 patch: LC_CTYPE needs to be imported

[Edmund GRIMLEY EVANS]

Werner Koch <wk@gnupg.org>:

> > The usual advice is to use the wchar_t API, let the system libraries
> > handle it and avoid putting anything UTF-8-specific into the
> 
> The problem we have is that OpenPGP specifies the use of UTF-8 and
> therefore I don't see any reason to assume an unknown encoding. Okay.
> there are some output functions for it just becuase not all system
> support UTF-8 and frankly, I don't know how to determine whether a
> system supports UTF-8 or how to switch the TTY to UTF-8.

What I wrote about using the wchar_t API concerns any data that is in
the local charset, e.g. terminal input and output.

Where UTF-8 is specified for data that is transmitted between
machines, on a modern system you should be able to convert between
UTF-8 and the locale charset using iconv, and find out what the locale
charset is using nl_langinfo(CODESET).

In case you don't have nl_langinfo(CODESET), or to override it if it's
wrong or uses names that are incompatible with iconv for some stupid
reason, there should be a way for the user to optionally specify the
local charset.

If case you don't have iconv you can include your own simple version
of it. You might do nothing, or replace non-ascii chars by '?', or
include full support for a few popular charsets, as you wish.

Is there a separate development branch of GnuPG, or is development
happening on the same branch as gnupg-1.0.2?

Edmund