[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [Nmh-workers] RFC 2047 vs RFC 2231 encoding for MIME parameters
From: |
Ken Hornstein |
Subject: |
Re: [Nmh-workers] RFC 2047 vs RFC 2231 encoding for MIME parameters |
Date: |
Mon, 03 Oct 2016 09:26:00 -0400 |
>I see plenty of sources of heartburn if somebody sends a filename with
>Hebrew characters in whatever 8859-foo (-8?), to somebody in a UTF-8
>environment. Unlike textual data intended to be read, where "decode
>to recipient's locale" makes sense, when it's a filename things get
>stickier, because there can be external references (indexes, etc) that
>point at a filename in a particular encoding - or even the 2047-encoded
>string as the filename. :)
I am not sure this is within the scope of nmh; I mean, it's a general
problem that exists even if you use RFC 2231 encoding. Also ... I'm
unclear from your response if you are a +1 or -1 on the idea of nmh
automatically decoding RFC-2047 encoded filenames, which was my original
query :-)
Regarding filenames lacking locale (really, I think you mean character
set), that is no longer true. I see a number of network filesystems
start to enforce UTF-8 (really, the only sane choice) and more Unix-like
operating systems are doing the same for local filesystems (MacOS and
Solaris are the ones that I'm aware of). Really, I think that's where
things will ultimately end up.
--Ken
- Re: [Nmh-workers] RFC 2047 vs RFC 2231 encoding for MIME parameters, (continued)
- Re: [Nmh-workers] RFC 2047 vs RFC 2231 encoding for MIME parameters, Ralph Corderoy, 2016/10/07
- Re: [Nmh-workers] RFC 2047 vs RFC 2231 encoding for MIME parameters, Earl Hood, 2016/10/05
- Re: [Nmh-workers] RFC 2047 vs RFC 2231 encoding for MIME parameters, David Levine, 2016/10/06
- Re: [Nmh-workers] RFC 2047 vs RFC 2231 encoding for MIME parameters, Lyndon Nerenberg, 2016/10/06
- Re: [Nmh-workers] RFC 2047 vs RFC 2231 encoding for MIME parameters, Lyndon Nerenberg, 2016/10/06
- Re: [Nmh-workers] RFC 2047 vs RFC 2231 encoding for MIME parameters, David Levine, 2016/10/06
- Re: [Nmh-workers] RFC 2047 vs RFC 2231 encoding for MIME parameters, Lyndon Nerenberg, 2016/10/06
- Re: [Nmh-workers] RFC 2047 vs RFC 2231 encoding for MIME parameters, David Levine, 2016/10/07
- Re: [Nmh-workers] RFC 2047 vs RFC 2231 encoding for MIME parameters, Ralph Corderoy, 2016/10/10
- Re: [Nmh-workers] RFC 2047 vs RFC 2231 encoding for MIME parameters, Ken Hornstein, 2016/10/10
- Re: [Nmh-workers] RFC 2047 vs RFC 2231 encoding for MIME parameters,
Ken Hornstein <=
- Re: [Nmh-workers] RFC 2047 vs RFC 2231 encoding for MIME parameters, Paul Vixie, 2016/10/03
- Re: [Nmh-workers] RFC 2047 vs RFC 2231 encoding for MIME parameters, Paul Vixie, 2016/10/03