Hello, I would love an answer to this: why even provide translations such as russian, ukraininan and any other language that is not available in ANSI codeset? I read that a year ago one of the main developers stated that he has no plants AT ALL to allow unicode or else for language packs so you should just remove the non-working languages... It's like giving false hope, disappointed me

ZZberry wrote:Hello, I would love an answer to this: why even provide translations such as russian, ukraininan and any other language that is not available in ANSI codeset?

You are wrong. Windows use windows-1251 codepage for Cyryllic alphabet, so there is no problem with Russian or Ukrainian translations. See http://en.wikipedia.org/wiki/Windows-1251
There are problems with scripts for other languages that have no Windows codepage defined, f.e. Sinhala or Georgian alphabet. See http://www.microsoft.com/resources/msdn ... fault.mspx (0 is missing ANSI codepage, 1 is missing OEM codepage).
Some time ago I heard some people succesfully used Georgian in Russian Windows, but not found detailed how-to. If you want to be helpful, share your knowledge with developers, please, complaining is futile.

ZZberry wrote:I read that a year ago one of the main developers stated that he has no plants AT ALL to allow unicode or else for language packs so you should just remove the non-working languages... It's like giving false hope, disappointed me

It's misunderstanding, I think. You should read: "There will be no move from ANSI to Unicode in current 3.x FDM versions". It doesn't mean there will be no move to Unicode at all, but it requires a lot of work. There is at least one critical decision to make: what encoding should be used internally in the program - UTF-8 or UTF-16? Windows are UTF-16 based, while UTF-8 is an Internet standard.