Skip to content

Use filesystem encoding for all decode calls #767

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

Merged
merged 1 commit into from
Oct 5, 2018

Conversation

theotherjimmy
Copy link
Contributor

Paths == bytes is a gigantic change set. Let's just try fixing sane
encoding schemes and leave path == bytes for another day.

Fixes #710, maybe

@theotherjimmy
Copy link
Contributor Author

@toyowata I think this should fix your Japanese Windows bug. Could you test this one?

@toyowata
Copy link

toyowata commented Oct 5, 2018

@theotherjimmy Thank you very much! I tested the fix by combination below and all case worked fine (no utf-8 error).

OS Commnad by Charactor code by CHCP
Windows 7 (Japanese) PowerShell 932 (shift_jis)
Windows 7 (Japanese) PowerShell 65001 (utf-8)
Windows 7 (Japanese) Command Prompt 932 (shift_jis)
Windows 7 (Japanese) Command Prompt 65001 (utf-8)
Windows 10 (Japanese) PowerShell 932 (shift_jis)
Windows 10 (Japanese) PowerShell 65001 (utf-8)
Windows 10 (Japanese) Command Prompt 932 (shift_jis)
Windows 10 (Japanese) Command Prompt 65001 (utf-8)

@screamerbg screamerbg self-requested a review October 5, 2018 14:00
Copy link
Contributor

@screamerbg screamerbg left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

That's what I call elegant solution!! LGTM

@theotherjimmy
Copy link
Contributor Author

Brilliant! Merging.

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.

utf8 error by importing mercurial repository
3 participants