That is true and must be so, since the capturing is handled in the Sikuli frontend which talks utf-8. The problem only exists later, when Sikuli tries to recall the image file whit find operations.
So you might capture with a unicode login account, but you should assure (e.g. preferences image naming), that the final paths to the stored image files do not contain any unicode characters.
@ Edwin
That is true and must be so, since the capturing is handled in the Sikuli frontend which talks utf-8. The problem only exists later, when Sikuli tries to recall the image file whit find operations.
So you might capture with a unicode login account, but you should assure (e.g. preferences image naming), that the final paths to the stored image files do not contain any unicode characters.