Sitting here in the US on a Windows 10 box with LANG set to en_US.UTF-8, I tried to load an image from a Swiss patient with an ß in the file name. VTK couldn’t open the file - “file not found”, so after playing around with some candidate solutions, I searched around and found this old thread (@dgobbi, sorry to suck you back into the vortex ):
tldr: Windows sucks at Unicode, so if you don’t have the proper codepage set (generally the same one used when creating the file name), then things will not work well (write a Chinese character into a file name, try to read it with Spanish codepage, and file not found, etc). Not an issue on macOS or Linux.
I had already tried the Win ShortName call, which “fixed” it, but was hoping there was something a little more elegant that had been implemented in the intervening five years. Does anyone know of improvements in Windows or VTK handling of this issue?