Issues with charset display.
First of all I am using gmail account to receive form submittions.
Gmail is accessible both via web interface and via Mozilla Thunderbird.
Same page and same form submitted with built in BV form processor and ABVFP are treated differently by Thunderbird while still OK if accessed via gmail`s web interface. I guess gmail is just "smarter" and properly selects UTF-8 encoding automicaly, while Thunderbird doesn`t. Why am I writing it here? Because old fashioned buit-in BV form processor lets me select "accept charset" UTF-8 in form properties and this encoding is recognized by Thunderbird and cyrillic submittions are displayed properly. Same exact form submitted using ABVFP is treated by Thunderbird as something with unidentified charset and text is just a set of messy symbols. However, even this messy message can be read if I force UTF-8 encoding in Thunderbird properties. So here is my question: why does ABVFP looses UTF-8 setting set by form properties while old-fashioned built-in form processor transmits this setting in generated e-mail message.
First of all I am using gmail account to receive form submittions.
Gmail is accessible both via web interface and via Mozilla Thunderbird.
Same page and same form submitted with built in BV form processor and ABVFP are treated differently by Thunderbird while still OK if accessed via gmail`s web interface. I guess gmail is just "smarter" and properly selects UTF-8 encoding automicaly, while Thunderbird doesn`t. Why am I writing it here? Because old fashioned buit-in BV form processor lets me select "accept charset" UTF-8 in form properties and this encoding is recognized by Thunderbird and cyrillic submittions are displayed properly. Same exact form submitted using ABVFP is treated by Thunderbird as something with unidentified charset and text is just a set of messy symbols. However, even this messy message can be read if I force UTF-8 encoding in Thunderbird properties. So here is my question: why does ABVFP looses UTF-8 setting set by form properties while old-fashioned built-in form processor transmits this setting in generated e-mail message.