From: Pavel.Janik@inet.cz (Pavel Janík ml.)
Subject: Re: drafts and infamous \202 :-(
Date: Fri, 5 May 2000 08:12:03 +0200 [thread overview]
Message-ID: <m3wvl9wnbz.fsf@totally-fudged-out-message-id> (raw)
In-Reply-To: Pavel.Janik@inet.cz's message of "(unknown date)"
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain; charset=us-ascii, Size: 1182 bytes --]
From: Pavel.Janik@inet.cz (Pavel Janík ml.)
Date:
Hi,
I'm replying to my message, because this problem is probably connected with
that one:
> stored as two byte-sequence. But when it is displayed for editing in drafts
> group, the \202\xxx appears instead í.
The only thing I did now is saved the draft and edit it again and got this
Backtrace:
Debugger entered--Lisp error: (wrong-type-argument arrayp nil)
get-charset-property(unknown prefered-coding-system)
mm-preferred-coding-system(unknown)
mm-mime-charset(unknown)
mapcar(mm-mime-charset (unknown indian-is13194 chinese-cns11643-5))
mm-find-mime-charset-region(381 431)
mml-parse-1()
mml-parse()
mml-generate-mime()
message-encode-message-body()
mml-to-mime()
(let ((mail-parse-charset ...) (mail-parse-ignored-charsets ...)) (mml-to-mime) (gnus-summary-edit-article-done "" nil #<buffer *Summary nndraft:drafts*> no-highlight))
(lambda (no-highlight) (let (... ...) (mml-to-mime) (gnus-summary-edit-article-done "" nil #<buffer *Summary nndraft:drafts*> no-highlight)))(nil)
gnus-article-edit-done(nil)
--
Pavel Janík ml.
Pavel.Janik@inet.cz
next prev parent reply other threads:[~2000-05-05 6:12 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-05-05 6:12 Pavel Janík ml.
2000-05-05 6:12 ` Pavel Janík ml. [this message]
2000-05-05 6:30 ` Shenghuo ZHU
2000-05-05 7:50 ` Pavel Janík ml.
2000-05-05 9:37 ` Kai Großjohann
2000-05-05 10:20 ` Pavel Janík ml.
2000-05-05 10:57 ` Kai Großjohann
2000-05-05 8:22 ` Hrvoje Niksic
2000-05-05 16:40 ` Shenghuo ZHU
2000-05-05 16:54 ` Hrvoje Niksic
2000-05-14 16:04 ` Mike Fabian
2000-05-14 18:07 ` Shenghuo ZHU
2000-05-14 21:05 ` Mike Fabian
2000-05-05 9:34 ` Kai Großjohann
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=m3wvl9wnbz.fsf@totally-fudged-out-message-id \
--to=pavel.janik@inet.cz \
/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).