[Announce] GnuPG 1.3.3 released (development)
udjinrg at forenet.by
Tue Oct 14 11:13:25 CEST 2003
-----BEGIN PGP SIGNED MESSAGE-----
> On Mon, Oct 13, 2003 at 03:59:18PM +0300, Maxim Britov wrote:
> > I have a problems with russian interface :(
> > gpg from cvs; RH Linux 9; gettext 0.12.2 from cvs; utf-8
> > 1. I get messages like underlined [revoked], trust: marginal validity:expired, etc.
> > ^^^^^^^ ^^^^^^^^ ^^^^^^^
> > in russian (in utf-8) with broken lenght.
> > They looks like: [revo], trust:marginalvalidity:expired, etc. :(
> > (In russian equivalent.)
> > 2. I always get "?" instead russian symbols in gpgv :(
> The development 1.3.x branch does not have updated translations. The
> code changes often enough that re-translating for each release would
> be a huge burden on the translators. When 1.3.x becomes 1.4, new
> translations will have to be made.
I know, but I'm currently Russian translation's maintainer :)
I have made 1.3.x translation and I having these problems.
In 1.2.x I didn't have ones. Only in 1.3.x with utf-8.
In: $ LANG=ru_RU.KOI8-R gpg --edit <MyKey>
I get fine text, but when I use utf-8 I gets problems.
> > 3. I still have problem with: make install and po/Makefile.
> > I always gets error message and I have to change po/Makefile :(
> This is a problem that is being fixed. In the meantime, use
> --disable-nls when configuring.
> > 4. I gets empty "Comment:" when my sylpheed-claws sign my messages.
> > I think that it is my sylpheed-claws or gpgme bag.
> > In gpg.conf: no-comments and no-sk-comments.
> > gpg --clearsign gives sign without empty "Comment:"
> Hmm. I suspect something is doing --comment "". An earlier version
> of GnuPG needed that to un-set the default comment. Try the attached
This works fine.
GnuPG KeyID 0x4580A6D66F3DB1FB Keyserver hkp://keyserver.kjsl.com
Fingerprint: 4059 B5C5 8985 5A47 8F5A 8623 4580 A6D6 6F3D B1FB
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.3.4-cvs (GNU/Linux)
-----END PGP SIGNATURE-----
More information about the Gnupg-devel