unicode encoding error fix #1838
Open
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
anadrianmanrique
added
bug
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
I’ve encountered an issue when working with SMB shares that have Turkish characters in their names, such as “TEST YÖNETİM DOKÜMANI”. The current encoding causes a UnicodeEncodeError, specifically:
UnicodeEncodeError: 'latin-1' codec can't encode character '\u0130' in position 29: ordinal not in range(256)The problem arises because the latin-1 codec cannot handle certain Turkish characters like ‘İ’. This fix resolves the encoding issue by ensuring proper handling of Unicode characters in SMB share names.
I hope this helps! Feel free to review and let me know if there’s anything I should adjust.
Thanks!