Problem encoding transfer after the update 4.9.2

[vBET]

It seems we found solution for the issue. We want to test it appropriately also on not UTF-8 database, to avoid issues with different encodings. Solution will be included in next release. Until then you can stay with vBET4.9.1 or use vBET4.9.2 with Apertium disabled, or use vBET4.9.2 with disabled Apertium only for Ukrainian (need to change configuration in files).

Please note that already broken translations will not be repaired automatically. Those have to be changed manually, using manual translation support, or removed from database.