Hello,
is it a solution to map certain extensions to the correct mime types
(not perfect but enough for me).
e.g.:
.rdp --> Content-Type: text/plain;
--> Content-Transfer-Encoding: base64
.sav --> Content-Type: text/plain;
--> Content-Transfer-Encoding: base64
best solution: via a configuration-file
other possibility: can I hardcode it anywhere in the source?
Philip
Andrew Morgan schreef:
> On Fri, 28 Mar 2008, Philip Steeman wrote:
>
>>>> When you want to mail a .rdp file (remote desktop program), it becomes
>>>> corrupt.
>>>> Other problem files: .sav (from SPSS program). I think there must be
>>>> more examples.
>>>
>>> NO. This is an entirely different issue dealing with a broken
>>> browser. This has nothing to do with charsets.
>>>
>>
>> You mean all the browser I tested (IE6 IE7 Firefox konqueror) are
>> broken? I don't see a difference between a unicode textfile (utf-16) and
>> a configuration-file '.rdp' or a output-file '.sav' all in unicode.
>> To test you can download a .rdp file from
>> http://users.khbo.be/steeman/unicode.html
>
> Since test.rdp is simply a text file that happens to be encoded in
> UTF-16, I agree that it will suffer from the same problem.
>
> Andy
--
IMP mailing list - Join the hunt: http://horde.org/bounties/#imp
Frequently Asked Questions: http://horde.org/faq/
To unsubscribe, mail: [EMAIL PROTECTED]
