From: Jesper Harder <harder@myrealbox.com>
Subject: Re: How does one cope with missing charsets?
Date: Fri, 24 Oct 2003 16:24:19 +0200 [thread overview]
Message-ID: <m3u15yn27g.fsf@defun.localdomain> (raw)
In-Reply-To: <87smll97au.fsf@era.iki.fi>
era@iki.fi writes:
> I have Gnus 5.8.8 so forgive me if this is improved in newer
> versions.
I can't reproduce it with the current version, so I guess it has been
fixed.
> I get an MMF spec which looks like this ("disarmed").
>
> [#part charset="utf-8" type="text/plain" filename="/tmp/8bit.txt"
> disposition=attachment
> description="Test file for unknown character set"]
> [#/part]
As a work-around it'll probably work to specify the encoding in the
MML tag, e.g. "encoding=base64", or to specify the MIME type as
application/octet-stream.
prev parent reply other threads:[~2003-10-24 14:24 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-10-22 5:53 era
2003-10-24 14:24 ` Jesper Harder
2003-10-24 14:24 ` Jesper Harder [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=m3u15yn27g.fsf@defun.localdomain \
--to=harder@myrealbox.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.
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).