Voytek Eymont wrote: > > > On Thu, July 12, 2012 3:21 am, Tomas Kuliavas wrote: > >> Switch to Polish translation or set default charset to iso-8859-2 or like >> Juergen suggested use utf-8. > > so the inbound email must have something like > Content-Type: text/plain; charset="utf-8" > or, 8859-2 > > as a pre-requsite, yes ? > If your SquirrelMail is in utf-8, inbound email can have any charset supported by your SquirrelMail setup (ls functions/decode/) as long as it follows MIME formating rules and specifies charset in headers. SquirrelMail will convert that character set to utf-8 on forward or reply. If your SquirrelMail is in iso-8859-2, inbound email should use iso-8859-2 or you will need to enable lossy encoding option in SquirrelMail config to convert utf-8 and other charsets to iso-8859-2 on forward/reply. IMHO Polish variant of Windows-125x should be relatively safe too as it is close to iso-8859-2. I don't remember with windows codepage is subtype of iso-8859-2. -- Tomas -- View this message in context: http://old.nabble.com/Squirrel-Android-sync-import--tp34137468p34151548.html Sent from the squirrelmail-users mailing list archive at Nabble.com. ------------------------------------------------------------------------------ Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ ----- squirrelmail-users mailing list Posting guidelines: http://squirrelmail.org/postingguidelines List address: squirrelmail-users@xxxxxxxxxxxxxxxxxxxxx List archives: http://news.gmane.org/gmane.mail.squirrelmail.user List info (subscribe/unsubscribe/change options): https://lists.sourceforge.net/lists/listinfo/squirrelmail-users
