From: Peter Dyballa <Peter_Dyballa@Web.DE>
Cc: help-gnu-emacs@gnu.org
Subject: Re: emacs and UTF-8
Date: Fri, 29 Apr 2005 00:22:39 +0200 [thread overview]
Message-ID: <76e0cf806e5d393e9bdbc9bbee2e825c@Web.DE> (raw)
In-Reply-To: <1114723995.031386.273860@g14g2000cwa.googlegroups.com>
Am 28.04.2005 um 23:33 schrieb knubee:
>> In case debian uses UTF-8 too for file names: keep that entry!
>
> Which one? (In fact, I think I appropriated many of those settings from
> one of your earlier postings on this topic :-))
>
(setq file-name-coding-system 'utf-8)
On your Scheme experience: could be the Swedish text was the whole time
correctly saved as UTF-8 since you made Emacs act like that. Only Guile
was in the incorrect environment not able to detect and interpret the
UTF-8 text. In the corrected environment Guile now could do it right.
These eMail subjects "=?iso-8859-1?Q?Bj=" come from some RFC that
describes how such a non-7 bit text is saved when transferred over the
internet. Since mail is still a 7 bit application, because nobody can
guarantee that there is absolutely no node that only understands 7 bit,
such encoding has to be done. Our eMail, when it leaves the MUA, is
encoded as base64 (Emacs can do that too, C-h a base64 RET). And
decoded when it enters.
Although I have saved eMails that contain lines like these
From: =?iso-8859-15?Q?S=E9bastien?= Kirche
Content-Type: text/plain; charset=iso-8859-15
To: Diskussionsliste
=?iso-8859-1?Q?f=FCr_Mitglieder_von_DANTE_e=2EV=2E?=
Mail-Followup-To: Diskussionsliste
=?iso-8859-1?Q?f=FCr_Mitglieder_von_DAN?=
=?iso-8859-1?Q?TE_e=2EV=2E?= <dante-ev@dante.de>
Content-Type: text/plain; charset=iso-8859-1
Reply-To:
=?iso-8859-1?q?Diskussionsliste_f=FCr_Mitglieder_von_DANTE_e=2EV=2E?=
List-Id:
=?iso-8859-1?q?Diskussionsliste_f=FCr_Mitglieder_von_DANTE_e=2EV=2E?=
my Mac OS X eMail programme, just Mail(.app), hides that "header" and
decodes the =XY codes according to the charset given to the correct
glyphs (XY is just the hex value of the "ASCII" code of that glyph in
that encoding). I think you only have to adjust some settings of your
Mail User Agent. Or switch to another one!
--
Greetings
Pete
Got Mole problems?
Call Avogadro 6.02 x 10^23
next prev parent reply other threads:[~2005-04-28 22:22 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-04-28 17:44 emacs and UTF-8 knubee
2005-04-28 20:05 ` Peter Dyballa
2005-04-28 20:09 ` Peter Dyballa
[not found] ` <mailman.3358.1114718800.2895.help-gnu-emacs@gnu.org>
2005-04-28 21:33 ` knubee
2005-04-28 22:22 ` Peter Dyballa [this message]
2005-04-28 22:54 ` Pascal Bourguignon
2005-04-30 17:05 ` knubee
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=76e0cf806e5d393e9bdbc9bbee2e825c@Web.DE \
--to=peter_dyballa@web.de \
--cc=help-gnu-emacs@gnu.org \
/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 read-only IMAP folder(s) and NNTP newsgroup(s).