On Tue, Sep 25, 2007 at 10:03:30AM +0200, Eyolf Østrem wrote:
There was a thread a short while ago about non-ascii characters in the
From name during which I changed my name from Oestrem to Østrem, and
it works.
Today, I happened to find one of my own messages in a search of the
list at
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Thursday, September 27 at 12:56 PM, quoth Eyolf Østrem:
This puzzled me at first, because I didn't know where that latin1
coding came from, but I assume it is because of send_charset or
assumed_charset, right?
Yup. It's send_charset that matters
On 27.09.2007 (09:11), Kyle Wheeler wrote:
set assumed_charset =us-ascii:windows-1252:latin-1:utf-8
For what it's worth, this setting is pretty pointless for most
Westerners. The best setting for Westerners is:
set assumed_charset=windows-1252
The reason this is better than what
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Thursday, September 27 at 05:50 PM, quoth Eyolf Østrem:
3. Along similar lines, windows-1252 contains the entire set of
possible values, 0 to 255, and has a character assigned to each.
Thus, no email will *ever* not match windows-1252. The way
On 27.09.2007 (12:22), Kyle Wheeler wrote:
If someone took a utf-8-encoded email (read: sequence of bytes) and
handed it to a file reader that only understood windows-1252, it would
get rendered, it would just look wrong. For example, this character: ☺
That character is not in windows-1252.
On 25-09-2007, at 21h 35'01, Kyle Wheeler wrote about Re: More on non-ascii
chars in headers
On Tuesday, September 25 at 11:16 PM, quoth Ionel Mugurel Ciobica:
Eyolf =?iso-8859-1?Q?=D8strem?=
That is not Unicode. Unicode would be this:
| Eyolf =?UTF-8?Q?=C3=98strem?=
This is the (safe
On Tue, Sep 25, 2007 at 10:03:30AM +0200, Eyolf Østrem wrote:
There was a thread a short while ago about non-ascii characters in the
From name during which I changed my name from Oestrem to Østrem, and
it works.
Today, I happened to find one of my own messages in a search of the
list at
On Tue, Sep 25, 2007 at 10:03:30AM +0200, Eyolf Østrem wrote:
Eyolf =?iso-8859-1?Q?=D8strem?= eyolf () oestrem ! com
RFC 2822 (is that the right number?) does not allow non-ascii characters
in headers, and there is another RFC that describes how to encode
non-ascii characters in headers.
On 25.09.2007 (04:13), Jiang Qian wrote:
Not so nice to look at... Is there still some setting I should
make/change, or is this down to marc.info's inability to handle
unicode characters?
Your name appears(including Ø) fine on my mutt display. My default
encoding is
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Tuesday, September 25 at 10:03 AM, quoth Eyolf Østrem:
Eyolf =?iso-8859-1?Q?=D8strem?= eyolf () oestrem ! com
Not so nice to look at... Is there still some setting I should
make/change, or is this down to marc.info's inability to handle
On 25.09.2007 (09:02), Kyle Wheeler wrote:
The answer is, unfortunately, no. There's no way to specify
alternatives in your From header. Plus, even if there was, it's
doubtful that marc.info would support them, given that it doesn't seem
interested or capable of decoding the existing RFC.
On 25-09-2007, at 10h 03'30, Eyolf Østrem wrote about More on non-ascii chars
in headers
Not so nice to look at... Is there still some setting I should
make/change, or is this down to marc.info's inability to handle
unicode characters?
Eyolf Østrem/Oestrem/=?iso-8859-1?Q?=D8strem
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Tuesday, September 25 at 11:16 PM, quoth Ionel Mugurel Ciobica:
Eyolf =?iso-8859-1?Q?=D8strem?=
That is not Unicode. Unicode would be this:
| Eyolf =?UTF-8?Q?=C3=98strem?=
This is the (safe) way to transfer non-ASCII information over the net.
13 matches
Mail list logo
