Hrm... you shouldn't be having issues with UTF8 text within pages. Some time ago I worked with Neal to make UTF8 characters work everywhere - usernames, passwords, page content, comments, etc.. I checked the schema as well, and it is indeed creating tables with "CHARACTER SET `utf8`". How exactly is the text becoming corrupted? Are you using MySQL or PostgreSQL? You're right, it is probably a character encoding issue. If you wish, you may change the encoding of the table with a SQL query like:
ALTER TABLE page_text CHARSET=UTF8 COLLATE=utf8_bin;
(You may need to prepend your table_prefix to "page_text")
There is no translation of Enano into Russian at this time. If you want to translate it, make a copy of the "english" directory and name it "russian" and then edit meta.json with the appropriate information about the language. At that point you should be able to install it. Then, get started on editing everything else in the language directory: five main JSON files (admin, core, install, tools, user), the summary of the license agreement (install/license-deed.html), and the default site content (install/default-blank/*.txt and install/default-tutorial/*.txt). Don't expect to translate the whole thing in one sitting; there are roughly 2,000 strings in the Enano core plus additional strings for any plugins you may want to translate. You can test your translation efforts by re-importing the language in the admin CP, which pulls the language strings from your JSON. Thanks!