From: "Ken Manheimer" <ken.manheimer@gmail.com>
Subject: Fwd: allout encryption and non-ascii characters
Date: Wed, 1 Nov 2006 13:07:49 -0500 [thread overview]
Message-ID: <2cd46e7f0611011007g772df6dcn84b0e36c2a2dfe71@mail.gmail.com> (raw)
In-Reply-To: <877iyfjpbx.fsf@acm.org>
allout's use of pgg for encryption doesn't provide for non-ascii text,
and encoding is a realm where i seem to have less than zero
cluefulness. can anyone help me solve the problem posed below?
ken
On 11/1/06, an allout user wrote:
> Hi Ken,
>
> I've been an allout user for a very long time. It's wonderful
> software. Thank you.
>
> Today I thought I'd try out the encryption support as I finally
> have a need for it but it doesn't properly handle non-ascii
> characters. pgg-output-buffer is created inside of pgg-gpg with
> mode of raw-text or binary and that is never converted back
> into the charset of the original cleartext. I do a lot of work
> in Japanese and so this is critical.
>
> I look at how gnus uses pgg and its charset handling but even
> in edebug I couldn't quite see how it was doing it correctly
> compared to how allout's method.
>
> If you have any insight I would really appreciate it. I will
> try to debug this in my own time but as you are the
> maintainer/author of the software involved, I hope you can at
> least nudge in me the right direction towards a fix.
--
ken
ken.manheimer@gmail.com
http://myriadicity.net
next parent reply other threads:[~2006-11-01 18:07 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <877iyfjpbx.fsf@acm.org>
2006-11-01 18:07 ` Ken Manheimer [this message]
2006-11-01 18:33 ` allout encryption and non-ascii characters Ken Manheimer
2006-11-04 19:28 ` Ken Manheimer
2006-11-06 15:56 ` Ken Manheimer
[not found] ` <87wt68yrcu.fsf@acm.org>
2006-11-07 23:22 ` Ken Manheimer
2006-11-08 0:13 ` Ken Manheimer
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
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=2cd46e7f0611011007g772df6dcn84b0e36c2a2dfe71@mail.gmail.com \
--to=ken.manheimer@gmail.com \
/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.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs.git
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 read-only IMAP folder(s) and NNTP newsgroup(s).