From: nospam2159@daimi.au.dk (Peter von der Ahé)
Subject: \201 problem (only in news headers) introduced in p0.45 or p0.46
Date: Wed, 18 Nov 1998 17:52:21 GMT [thread overview]
Message-ID: <yc0u2zwzy5o.fsf@ufleku.daimi.au.dk> (raw)
Content-Transfer-Encoding: 8bit
Hi!
When I post to a newsgroup I have problems with latin1 characters in
the headers. Characters like æøåé in headers are still "mule"
encoded, this means that the From: field, as an example, is:
From: Peter von der Ah\201\351 ...
not
From: Peter von der Ah\351 ...
The body is OK.
The strange thing is that, whenever I send a mail, the headers are OK.
As stated in the subject line, the problem was introduced in p0.45 or
p0.46. I have tried p0.50 and the problem is still present.
I'm using Emacs-20.3 (no MBSK, no --unibyte), and I have this Mule
setup:
(set-language-environment "Latin-1")
(modify-coding-system-alist 'file "" 'latin-1)
M-x describe-coding-system gives this output:
Coding system for saving this buffer:
Not set locally, use the default.
Default coding system (for new files):
1 -- iso-latin-1 (alias: iso-8859-1 latin-1)
Coding system for keyboard input:
nil
Coding system for terminal output:
nil
Defaults for subprocess I/O:
decoding: 1 -- iso-latin-1 (alias: iso-8859-1 latin-1)
encoding: 1 -- iso-latin-1 (alias: iso-8859-1 latin-1)
Priority order for recognizing coding systems when reading files:
1. iso-latin-1 (alias: iso-8859-1 latin-1)
2. iso-2022-jp (alias: junet)
3. iso-2022-7bit
4. iso-2022-7bit-lock (alias: iso-2022-int-1)
5. iso-2022-8bit-ss2
6. emacs-mule
7. raw-text
8. japanese-shift-jis (alias: shift_jis sjis)
9. chinese-big5 (alias: big5 cn-big5)
10. no-conversion (alias: binary)
Other coding systems cannot be distinguished automatically
from these, and therefore cannot be recognized automatically
with the present coding system priorities.
The followings are decoded correctly but recognized as iso-2022-7bit-lock:
iso-2022-7bit-ss2 iso-2022-7bit-lock-ss2 iso-2022-cn iso-2022-cn-ext iso-2022-kr
Particular coding systems specified for certain file names:
OPERATION TARGET PATTERN CODING SYSTEM(s)
--------- -------------- ----------------
File I/O "\\.gz\\(~\\|\\.~[0-9]+~\\)?\\'"
(no-conversion . no-conversion)
"\\.tgz\\'" (no-conversion . no-conversion)
"\\.bz2\\'" (no-conversion . no-conversion)
"\\.Z\\(~\\|\\.~[0-9]+~\\)?\\'"
(no-conversion . no-conversion)
"\\.elc$" (emacs-mule . emacs-mule)
"\\(\\`\\|/\\)loaddefs.el$"
(no-conversion . no-conversion)
"\\.tar$" (no-conversion . no-conversion)
"" (latin-1 . latin-1)
Process I/O nothing specified
Network I/O nothing specified
Kind regards
Peter
--
Peter von der Ahé · Systems programmer · <URL:http://www.daimi.aau.dk/~pahe/>
| Phone: office (540.030): +45 89 42 31 41, home: +45 86 13 26 34 ---+
| "Feltet havde bestilt en Hamburger, men fik den ikke spist." |
+--- -- Claus Elgaard (TV2 Sporten) |
.
next reply other threads:[~1998-11-18 17:52 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
1998-11-18 17:52 Peter von der Ahé [this message]
1998-11-19 2:59 ` Lars Magne Ingebrigtsen
1998-11-19 16:48 ` Peter von der Ahé
[not found] ` <6fzp9nbngb.fsf@dna.lth.se>
1998-11-30 0:39 ` Jason L Tibbitts III
1998-11-20 1:01 ` Peter von der Ahé
1998-11-20 4:26 ` Lars Magne Ingebrigtsen
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=yc0u2zwzy5o.fsf@ufleku.daimi.au.dk \
--to=nospam2159@daimi.au.dk \
/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).