I did some more small tests (perhaps not very usefull) - webmail used from my Belgian provider: unicode is encoded in base64 (so OK!). Really don't know what software it is. - tried it with squirrelmail. Got a php-error with unicode attachments (not with normal textfiles). I'm not a squirrelmail wizzard, I installed it from debian-packages in a hurry. - when you test it with a standard Linux-command file -i unicode.txt it says: > linux% file -i unicode.txt > unicode.txt: text/plain; charset=utf-16
So the file-utility gets it right (as does the webmail of my provider). Philip Jan Schneider schreef: > Zitat von Otto Stolz <[EMAIL PROTECTED]>: > >>> That >>> attachment-charset field would be preset to the value resulting >>> from the procedure outlined above, but would provide an >>> opportunity to override the preset value. >> On second thought, I am not sure whether this is feasable: >> This would amount to reading the file, via JavaScript, immediately >> after it has been selected, and before it is uploaded. I have not >> delved enough into JavaScript to assess the feasibility of this >> approach. But if JavaScript code is used to guess the encoding >> of the text file to be uploaded, the second step proposed above >> does not apply; rather, the JavaScript code should be able to >> find the system codepage, directly. > > This won't work of course, because you can't read local files with JavaScript. > > Jan. > -- IMP mailing list - Join the hunt: http://horde.org/bounties/#imp Frequently Asked Questions: http://horde.org/faq/ To unsubscribe, mail: [EMAIL PROTECTED]
