Translations are not displayed correctly

[David Shaw]

On Tue, Feb 18, 2003 at 11:08:14AM +0100, Stéphane Corthésy wrote:
> 
> On Monday, Feb 17, 2003, at 23:45 Europe/Zurich, David Shaw wrote:
> 
> >On Mon, Feb 17, 2003 at 10:14:00PM +0100, Stéphane Corthésy wrote:
> >>As you can see, the e acute is not displayed correctly. Looking at the
> >>raw output using hexdump, the e eacute corresponds to byte 0xe9. It is
> >>not a valid UTF8 sequence. In fact, the output is done using  
> >>ISOLatin1,
> >>despite the options passed on the command-line.
> >>Is it a bug in gpg, the French gnupg.mo, or in my system (MacOS X)?
> >
> >None of the above.  You probably have your local character set in the
> >shell set incorrectly.
> 
> 
> No, I don't. As I wrote, I tested output against hexdump: I redirected  
> gpg stdout/stderr to a file, then displayed content with hexdump, to be  
> sure that my Terminal settings didn't play a role.

GnuPG doesn't output UTF8 help strings.  The --utf8-strings and
--charset utf8 options apply to the command line arguments and input
file.

Look at your LC_CTYPE.  What is it set to?

David

-- 
   David Shaw  |  dshaw at jabberwocky.com  |  WWW http://www.jabberwocky.com/
+---------------------------------------------------------------------------+
   "There are two major products that come out of Berkeley: LSD and UNIX.
      We don't believe this to be a coincidence." - Jeremy S. Anderson