Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

API functions do not accept certain characters in file paths #6

Open
paul-krug opened this issue May 28, 2021 · 5 comments
Open

API functions do not accept certain characters in file paths #6

paul-krug opened this issue May 28, 2021 · 5 comments
Labels
bug Something isn't working

Comments

@paul-krug
Copy link
Collaborator

API function (tested with vtlSegmentSequenceToGesturalScore) can not load the input file if the respective paths contains chars such as 'ä,ö,ü,ß'. The same files work fine when renamed.

@Simon-Stone
Copy link
Contributor

Using the CMake or the Visual Studio build?

@paul-krug
Copy link
Collaborator Author

CMake, I did not test the VS build yet

@Simon-Stone
Copy link
Contributor

Simon-Stone commented May 31, 2021

The reason is that all strings are handled with (narrow) characters of type char. To properly handle special characters like ä or è we need to switch to unicode, which means wide characters of type wchar_t.

This is a larger change which will be handled soon™.

@paul-krug
Copy link
Collaborator Author

Was this fixed?

@Simon-Stone
Copy link
Contributor

Nope. Like I said above, it's a bigger change than one might think, with a few implications regarding cross-platform compatibility on top. For the foreseeable future, please use paths without "special" characters.

@paul-krug paul-krug added the bug Something isn't working label Aug 9, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

2 participants