Hello Werner,
On Thursday, February 28, 2008 at 9:17:59 +0100, Werner Koch wrote:
> Yes there is the Charset armor header but that one is not supported by
> GnuPG because it is a kludge not required since 15 years or so (since
> MIME).
A charsethacked Mutt can make use of this Charset armor
Hello Martin,
On Wednesday, February 27, 2008 at 20:06:57 +0100, Martin Toft wrote:
> I use GnuPG together with mutt on Debian Etch. I prefer to use
> ISO-8859-1 and have these lines in my .muttrc to accomplish that:
First of all, your Mutt charset setup is quite suboptimal.
Discussing it w
Hello Mike,
On Friday, September 8, 2006 at 15:32:10 +0100, Mike Keighley wrote:
> GnuPG 1.4.5 on HP-UX 11.0 [...]
> gpg: conversion from `utf-8' to `iso88591' not available
The HP iconv has non-standard names for charsets. It knows the UTF-8
charset only by the name "utf8". While GnuPG har
Hello,
On Saturday, April 15, 2006 at 2:33:21 -0400, feitao wrote:
> [embedded filenames] gpg has some problem with some Chinese
> characters. For example, it interprets '‚S' as '\x8S'
Confirmed with GnuPG 1.4.3 on Linux. It seems that in characters
encoding, all bytes that are between 0x80
pired
sigs done on 2005-09-04 stays uncleanable?
| $ gpg --check-sigs C1C46015
| pub 1024D/C1C46015 2003-11-29
| uid Alain Bench <[EMAIL PROTECTED]>
| sig!3C1C46015 2006-01-26 Alain Bench <[EMAIL PROTECTED]>
| uid Alain Bench <[
Hello David, Satya,
On Wednesday, November 2, 2005 at 0:11:47 -0500, David M. Shaw wrote:
> On Fri, Oct 28, 2005 at 10:50:56AM +, bingumalla satyanarayana wrote:
>> using HP Unix 11.0 [...] I am getting the following message:
>>| gpg: conversion from `utf-8' to `roman8' not available
> Chang
Hello Johan,
On Friday, August 5, 2005 at 2:55:37 PM +0200, Johan Wevers wrote:
> I read my own email usually in text mode screens, with the IBM 850
> charset. MIME headers can't change that anyway, since you need root
> acces to change the active charset and I don't plan to make [...] mutt
> su
Hello Michael,
On Wednesday, August 3, 2005 at 8:57:07 PM +, Michael Kjörling wrote:
> My MUA, muttng, correctly identifies the input data prior to signing
> as iso-8859-15 and after signing as utf-8
Mutt half-recently began to force outgoing traditional inline PGP
messages to UTF-8, di
On Tuesday, July 5, 2005 at 7:50:54 PM +0200, Bruno Haible wrote:
> Alain Bench wrote:
>> how is a Win32 console app supposed to use libcharset?
> The application needs to know where it intends to send a certain
> string of text.
And this app needs to know which Windows speci
Hello Bruno,
On Monday, July 4, 2005 at 1:28:35 PM +0200, Bruno Haible wrote:
> Please use the appended patch, which I'll also use in libiconv-1.10.
>| localcharset.c (get_charset_aliases) [WIN32]: Add CP65001 and others.
>| Reported by <[EMAIL PROTECTED]> via Alain Ben
[copy to libiconv author]
Hello,
On Saturday, May 21, 2005 at 9:21:01 AM +0200, [EMAIL PROTECTED] wrote:
> when setting utf-8 for cmd.exe, gpg switches back to its default
> character set. In cmd.exe I do the follwoing to change the codepage:
> [chcp 65001] Active Codepage: 65001.
> gpg: co
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi Sascha,
On Sunday, June 19, 2005 at 4:39:40 AM +0200, Sascha Kiefer wrote:
>> Mutt generates since version 1.5.1:
>>| Content-Type: text/plain; x-action=pgp-{encrypted,signed,keys}
> May u send me a signed, encrypted and your public key so i can
Hello Patrick,
On Friday, June 17, 2005 at 7:44:49 PM +0200, Patrick Brunschwig wrote:
> what I do in Enigmail. For attachments, I'm looking at the
> content-type (application/pgp-*)
What about the types Mutt generates since version 1.5.1:
| Content-Type: text/plain; x-action=pgp-{encrypte
Hello Gbenga,
On Wednesday, March 23, 2005 at 4:41 PM, Gbenga Abimbola wrote:
>| $ gpg -v
>| gpg: conversion from `utf-8' to `roman8' not available
On HP-UX? Then: In fact the said conversion *is* available, but a
bug makes GnuPG request it under a wrong name, unknown by the HP iconv
librar
14 matches
Mail list logo
