Mailing List Archive: Problem with english translation

Problem with english translation

Apr 30, 2013, 4:03 PM

Post #1 of 3 (2618 views)

Hi,

I'm not sure I have the right list. If not, please forgive me and let
me know the correct list. This is about translations.

My win32 program, QuickSilver Lite Remailer Client, uses GPG (1.4.12
currently).

Some of my users have their main GPG installation set to languages
other than english. My program has it own copy of GPG. In this
circumstances my GPG gets it's language from the registry entry of
the main GPG. I need errors in english. I've used the environment
variable LANGUAGE to set the language to en@quot.mo. Verifications
work fine, but it's apparently some form of english other than plain
english (or american english). Same problem with en@boldquot.mo.

When verifying messages, I always get this error message:
"conversion from `utf-8' to `CP437' failed: Illegal byte sequence"
"Good signature from \xe2\x80\x9cSteven Crook\xe2\x80\x9d"

If I add "display-charset utf-8" to the config file, I get this
instead:
"Good signature from â€œRichard Christmanâ€"

I need to solve the error problem. I can't find an en.mo for regular
english. I'm getting the impression that is built in to GPG as it is
english when no .mo files are present at all.

Can I force GPG to use plain english in this situation, with the main
GPG installation set to some other language? I've researched this a
great deal and found no answers other than the LANGUAGE environment
variable.

Thanks so much for any help you can provide,

Richard
--
Richard Christman
https://quicksilvermail.net

Re: Problem with english translation [ In reply to ]

petr.pisar at atlas

Apr 30, 2013, 11:34 PM

Post #2 of 3 (2437 views)

Permalink

On Tue, Apr 30, 2013 at 05:03:39PM -0600, richard@quicksilvermail.net wrote:
> I need errors in english. I've used the environment
> variable LANGUAGE to set the language to en@quot.mo. Verifications
> work fine, but it's apparently some form of english other than plain
> english (or american english). Same problem with en@boldquot.mo.
>
It's English. It's English with correct quoting characters. You can verify it
in a printed newspaper.

The @quot and @boldquot modifiers turn these Unicode quotations on explicitly.
Have you tried simple "en"?

> When verifying messages, I always get this error message:
> "conversion from `utf-8' to `CP437' failed: Illegal byte sequence"
> "Good signature from \xe2\x80\x9cSteven Crook\xe2\x80\x9d"
>
The \xe2\x80\x9 is American opening double quotes (â€œ). But such a character
does not exist in CP437 character set used by your operating system.

> If I add "display-charset utf-8" to the config file, I get this
> instead:
> "Good signature from ???Richard Christman??"
>
Because you forced UTF-8 character set for the output, no recoding has been
performed and wrong characters have been printed to the output.

> I need to solve the error problem. I can't find an en.mo for regular
> english. I'm getting the impression that is built in to GPG as it is
> english when no .mo files are present at all.
>

I guess you look for English output in ASCII.

I have two pieces of news for you. The bad one is "en_US.CP437" or similar
locale does not know how to transliterate Unicode quoting characters to CP437
probably. The good one is GnuPG is written in English, so setting locale to
"C" or "POSIX" should give you untranslated output in ASCII which is, by
concidence, in English. And you should get plain ASCII quotes like (`').

So try to set LANGUAGE=C.

-- Petr

Re: Problem with english translation [ In reply to ]

moses.mason at gmail

May 1, 2013, 10:48 PM

Post #3 of 3 (2432 views)

Permalink

I think he is using Windows...In fact, I have these kind of problem
before. I have to change the Codepage in cmd. And yes it is
frustrating.

On Wed, May 1, 2013 at 2:34 PM, Petr Pisar <petr.pisar@atlas.cz> wrote:
> On Tue, Apr 30, 2013 at 05:03:39PM -0600, richard@quicksilvermail.net wrote:
>> I need errors in english. I've used the environment
>> variable LANGUAGE to set the language to en@quot.mo. Verifications
>> work fine, but it's apparently some form of english other than plain
>> english (or american english). Same problem with en@boldquot.mo.
>>
> It's English. It's English with correct quoting characters. You can verify it
> in a printed newspaper.
>
> The @quot and @boldquot modifiers turn these Unicode quotations on explicitly.
> Have you tried simple "en"?
>
>> When verifying messages, I always get this error message:
>> "conversion from `utf-8' to `CP437' failed: Illegal byte sequence"
>> "Good signature from \xe2\x80\x9cSteven Crook\xe2\x80\x9d"
>>
> The \xe2\x80\x9 is American opening double quotes (“). But such a character
> does not exist in CP437 character set used by your operating system.
>
>> If I add "display-charset utf-8" to the config file, I get this
>> instead:
>> "Good signature from ???Richard Christman??"
>>
> Because you forced UTF-8 character set for the output, no recoding has been
> performed and wrong characters have been printed to the output.
>
>> I need to solve the error problem. I can't find an en.mo for regular
>> english. I'm getting the impression that is built in to GPG as it is
>> english when no .mo files are present at all.
>>
>
> I guess you look for English output in ASCII.
>
> I have two pieces of news for you. The bad one is "en_US.CP437" or similar
> locale does not know how to transliterate Unicode quoting characters to CP437
> probably. The good one is GnuPG is written in English, so setting locale to
> "C" or "POSIX" should give you untranslated output in ASCII which is, by
> concidence, in English. And you should get plain ASCII quotes like (`').
>
> So try to set LANGUAGE=C.
>
> -- Petr
>
> _______________________________________________
> Gnupg-i18n mailing list
> Gnupg-i18n@gnupg.org
> http://lists.gnupg.org/mailman/listinfo/gnupg-i18n
>

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