Download
@oleg Ah I discovered, it's because I had set a custom font in Notepad++ style config (Inconsolata).
I'm not particularly happy with the patch solution, as that would require Russian, eastern European, Arab, Chinese, etc. to have a crappy workaround for renaming tabs.
UPDATE:
See http://stackoverflow.com/questions/29722...3#29728633. GS Custom Settings 0.4 will include support for non-Latin characters in the following way:
To keep it ASCII-compatible a word will display correctly in the plugin UI/ output, but will be changed to unicode in the JSON data, eg: Экспорт will become: \u042D\u043A\u0441\u043F\u043E\u0440\u0442. The only downside (if any) is that, eg. Russian users have to pass the raw data file through a unicode converter if they want to be able to read it properly.
I'm not particularly happy with the patch solution, as that would require Russian, eastern European, Arab, Chinese, etc. to have a crappy workaround for renaming tabs.
UPDATE:
See http://stackoverflow.com/questions/29722...3#29728633. GS Custom Settings 0.4 will include support for non-Latin characters in the following way:
To keep it ASCII-compatible a word will display correctly in the plugin UI/ output, but will be changed to unicode in the JSON data, eg: Экспорт will become: \u042D\u043A\u0441\u043F\u043E\u0440\u0442. The only downside (if any) is that, eg. Russian users have to pass the raw data file through a unicode converter if they want to be able to read it properly.
