Announcements and discussions for Gnus, the GNU Emacs Usenet newsreader
 help / color / mirror / Atom feed
From: usenet@shadowprint.de
Subject: Re: PGP / GPG and non-US ascii
Date: 23 Jul 2002 10:54:16 +0200	[thread overview]
Message-ID: <87d6telt8n.fsf@shadowprint.de> (raw)
In-Reply-To: <87k7nnvcf1.fsf@unix.home>

>>>>> "V.K." == Vasily Korytov <moderator@faqteam.org> writes:


    V.K.> Let me try again. Are you sure, you have GNU Emacs version
    V.K.> 21? Your User-Agent header reports v20.7. I don't have Emacs
    V.K.> 20 here, but this problem seems not to present in v21.

I am using an older emacs 20.7 on another machine, but ironically the
problem doesn't exist there, but only at home, where I am using a GNU
Emacs 21.1.1 (Debian Package from Woody) and a 5.9.0 GNUS. So a simple
workaround for me is to "downgrade" to 20.7.


    V.K.> If you don't want upgrade Emacs, maybe you should upgrade
    V.K.> Gnus and use gpg.el -- as it was already suggested.

I am not sure to use Alpha - Software for email and especially
encryption / signing. what do yout think?

    >> Perhaps I should use pure ascii until that is fixed. Is there
    >> some code for message assuring that Encoding is ascii and
    >> Umlauts (öäü...)  are automatically converted into their
    >> counterparts (ae, ue ...)  also with citations ... . That could
    >> work for me.

I ment to do the conversion when writing the mail, not after
signing. But that's quite uncomfortable either.


Thanks for your help,
Daniel Hofmann.


      parent reply	other threads:[~2002-07-23  8:54 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-07-17 18:22 Daniel Hofmann
2002-07-17 18:26 ` Vasily Korytov
2002-07-22 12:51   ` Daniel Hofmann
     [not found]     ` <8765z7gbfe.fsf@unix.home>
2002-07-22 14:11       ` Daniel Hofmann
     [not found]         ` <87k7nnvcf1.fsf@unix.home>
2002-07-23  8:54           ` usenet [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87d6telt8n.fsf@shadowprint.de \
    --to=usenet@shadowprint.de \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).