Skip to content

Enable (partially) to work under non-ASCII path on Windows.#483

Closed
Suzumizaki wants to merge 1 commit into
marcelotduarte:mainfrom
Suzumizaki:enable_under_non_ascii_path
Closed

Enable (partially) to work under non-ASCII path on Windows.#483
Suzumizaki wants to merge 1 commit into
marcelotduarte:mainfrom
Suzumizaki:enable_under_non_ascii_path

Conversation

@Suzumizaki

Copy link
Copy Markdown
Contributor

Consider building under virtual environments made by venv which contains non-ASCII characters.

Especially, the default user name often contains that characters under non-English mode Windows. That means the full path of "Documents" or "Desktop" etc. possibly be contain such characters.

In fact, due to using imagehlp.h functions, this is partial solution. For example, under en-US environment, this patch affects nothing. Another example, when using Japanese mode Windows and using characters that is not included cp932, this patch would help none.

But this patch would much better user experience, because at least they can use their native characters.

@Suzumizaki

Copy link
Copy Markdown
Contributor Author

... Sorry, I made something wrong. I'll re-fix later.

@Suzumizaki Suzumizaki force-pushed the enable_under_non_ascii_path branch 3 times, most recently from 2ac07ae to c8f39bb Compare August 13, 2019 06:00
Consider building under virtual environments made by venv which contains non-ASCII characters.

Especially, the default user name often contains that characters under non-English mode Windows. That means the full path of "Documents" or "Desktop" etc. possibly  be contain such characters.

In fact, due to using imagehlp.h functions, this is partial solution. For example, under en-US environment, this patch affects nothing. Another example, when using Japanese mode Windows and using characters that is *not* included cp932, this patch would help none.

But this patch would much better user experience, because at least they can use their native characters.
@Suzumizaki Suzumizaki force-pushed the enable_under_non_ascii_path branch from c8f39bb to 37d746a Compare August 13, 2019 06:18
@Suzumizaki

Copy link
Copy Markdown
Contributor Author

... I finished fix to catch up master branch. Thank you.

Base automatically changed from master to main January 24, 2021 20:19
@marcelotduarte

Copy link
Copy Markdown
Owner

In some PR I solved problems with names in UTF-8 on Windows and Linux. And as this PR is very old, and the code is different, I will close it.
But, if you still have a problem with non-ASCII characters, please feel free to contact me.
Thanks!

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

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants