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

Issues with non-ASCII chars in path or filename #604

Closed
matlo opened this Issue Jan 7, 2019 · 1 comment

Comments

Projects
None yet
1 participant
@matlo
Copy link
Owner

matlo commented Jan 7, 2019

@matlo

This comment has been minimized.

Copy link
Owner

matlo commented Jan 8, 2019

For fast testing in gimx-launcher:

//    const wchar_t* sUserDir = L"C:\\Users\\Администратор\\AppData\\Roaming";
//    userDir = wxString(sUserDir);

@matlo matlo changed the title gimx-launcher fails to download configurations Issues with non-ASCII chars in path or filename Jan 8, 2019

matlo added a commit that referenced this issue Jan 8, 2019

Issues with non-ASCII chars in path or filename #604
Windows fopen and fstream do not support UTF-8 paths.

gimx.exe issues:
* failure to write log file
* failure to read macros

gimx-launcher issues:
* failure to save and restore choices
* failure to read gimx exit status
* failure to download configurations
* failure to download updates (if temp dir was modified)

@matlo matlo closed this Jan 8, 2019

@matlo matlo reopened this Jan 19, 2019

matlo added a commit that referenced this issue Jan 19, 2019

Issues with non-ASCII chars in path or filename #604
* on Windows, use _wopendir, _wclosedir, _wreaddir, and _wstat
* this fixes issues when reading macro files

matlo added a commit that referenced this issue Jan 19, 2019

@matlo matlo closed this Jan 19, 2019

matlo added a commit that referenced this issue Jan 20, 2019

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment