in reply to Tk unicode paths chooseDirectory vs getOpenFile and getSaveFile
I don't have a solution, nor can comment on your latest update, but can only confirm: for me, getOpenFile returns correct utf8 path in all tests.
chooseDirectory, for "ã" dir, returns plain Latin "a" as trailing path component, with utf8::is_utf8 being false. While, for "у" -- Cyrillic, qq(\x{443}) -- it returns utf8, but "ó". Weird and broken.
|
|---|
| Replies are listed 'Best First'. | |
|---|---|
|
Re^2: Tk unicode paths chooseDirectory vs getOpenFile and getSaveFile
by vr (Curate) on Mar 05, 2019 at 14:48 UTC | |
by Takamoto (Monk) on Mar 12, 2019 at 15:18 UTC |