Hello,
I'm using send email action. I want to send message body with national (Polish) characters. I prepared the text in notepad and copied it into the action. When I receive the email, national characters are replaced with ansi nearest characters. I tried to used different values for Encoding lookup control in the action. But it didn't help. I tried to use ISO-8859-2, Windows-1250 (though it is not listed, I entered the encoding name).
OS: Windows 2003 R2 Std 32b PL.
FB.7.0.0.880
This looks like something I fixed a few days ago, the email library we use changed how things worked internally and we had to re-organize our code to get the correct behavior.
This build has that fix included :
https://www.finalbuilder.com/downloads/finalbuilder/aex6/FB700_894.exe
Hi,
You are really fast. What do you think about adding "check for update" feature in FB. Currently only official releases are checked, but maybe it would be good to add a user an ability to update to the latest build?
There is a “Check for Updates” feature on the help menu already, however it only checks for official updates. We were discussing in the office this week the possibility of making our daily builds available from the downloads page. The risk there is that daily builds include anything that is checked in, and might not be quite ready for general use.
While we post bugfix builds often, the general idea is if you are not experiencing any issues then it’s best to wait for official updates. With official updates we usually have confirmation and verification that bugfixes actually worked for the person who reported it. We are intending to post official update builds more often, including one next week.
Posted By Vincent Parrett on 04 Dec 2010 05:33 AM
There is a "Check for Updates" feature on the help menu already, however it only checks for official updates. We were discussing in the office this week the possibility of making our daily builds available from the downloads page. The risk there is that daily builds include anything that is checked in, and might not be quite ready for general use.
Yes, I am aware of that. I think that if "check for update" would say:
"No official release is available, but snapshot build is available, however not fully tested", it would be enough.
I agree with you that it's better not to touch running system, but in case of problems, it would be good to get latest version, this way we would avoid creating duplicate problem tickets. Another option is to search the forum searching for links to newer versions, but it is complicate.
While we post bugfix builds often, the general idea is if you are not experiencing any issues then it's best to wait for official updates. With official updates we usually have confirmation and verification that bugfixes actually worked for the person who reported it. We are intending to post official update builds more often, including one next week.