Link in post 2 resolves to object not found error
Daniel - I've found this with all the support links inside the plugin files too - you have some serious housekeeping to do.
Why is this plugin not UTF-8 compatible?
Where does Google translate provide the "special HTML characters" you refer to in the languages folder readme.txt file? I cannot find that function anywhere on Google.
The issue here is not just roman characters with umlauts etc, but alphabets that are not even based on the roman characters - e.g. Chinese, Japanese, Korean, Thai, etc. This plugin absolutely should be UTF-8 compliant.