Mailing List Archive

Bugs: gpg and gpgm share options file ungracefully, English usage
I get this message:

gpgm: /home/mskala/.gnupg/options:1: invalid option
gpgm: /home/mskala/.gnupg/options:2: invalid option
gpgm: /home/mskala/.gnupg/options:3: invalid option

when I run gpgm with this:

cipher-algo BLOWFISH
pubkey-algo ELGAMAL
digest-algo SHA1

in my options file. Those are valid options for gpg, but they aren't for
gpgm, and since gpg and gpgm use the same options file by default, gpgm
chokes on those options. It does not silently ignore them as gpg does
with options like -r and -u that don't always make sense.

On another topic, I notice that many of the program's messages are in
slightly broken English; for instance, there are a couple of uses of "his"
where it should really read "its", and a quick check of "strings gpg"
shows occurances of "informations", "Lets" (should be "let's"), "beed"
(should be "been"), etc. I don't have a list of these but could make one;
would that be helpful? Do you want it as a patch or just a list or what?

"Let me lose so beautifully http://www.islandnet.com/~mskala/
Let me lick the dew from the money tree Matthew Skala
Have the moms of the world all care about me Ansuz BBS
At suppertime" - Odds (250) 642-7820
Re: Bugs: gpg and gpgm share options file ungracefully, English usage [ In reply to ]
Matthew Skala <mskala@ansuz.sooke.bc.ca> writes:

> cipher-algo BLOWFISH
> pubkey-algo ELGAMAL
> digest-algo SHA1
>
> in my options file. Those are valid options for gpg, but they aren't for

Fixed (see next release).

> (should be "been"), etc. I don't have a list of these but could make one;
> would that be helpful? Do you want it as a patch or just a list or what?

A diff or a plain file together with the location. I Have to change
the po files too.

I'd be very glad to receive such bug reports - the compiler does
not do a spelling check and English isn't my native language :-)


--
Werner (finger gcrypt@ftp.guug.de for info about GnuPG)