Comment 1 for bug 908491

Hi and thanks for the bug report. The handling of unicode is generally not easy and it is even more complicated in our case as there is no documentation which encoding vim.eval expects of its strings. After your bug report, I improved upon the situation by converting more explicitily between unicode and utf-8 encoded strings in UltiSnips - this results that german umlauts work for me now in my snippets. This should help you as well.

Unfortunately, the explicit conversion to and from utf-8 might make trouble if the snippet definition files are not encoded in utf-8 or if some vim version expects another encoding for vim.eval - I do not know how to fix this properly for the moment, therefore this 80% must do.

The fix is in r324 in trunk; it would be cool if you could test it and report back.