Unicode Paths not supported

[lyind]

Glogg does not properly handle unicode paths. If any path segment above the log file, or the log file itself, contain complex unicode characters the file cannot be opened and glogg starts empty.

The following message is printed on the terminal when opening fails:

10:54:14.455 ERROR [56900] [MainWindow::loadFile@1287] Can't open file /home/user/Downloads/some-log/����_�\���m�^�b�`_�^�u���b�glog/blabla.log

(The question mark characters are not in the original path and replace unicode characters.)

This is very annoying when analysing log files originating from Japanese, Korean or Chinese systems.