Simple filenames #966
Open
Simple filenames #966
Conversation
This file contains hidden or 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
…ith their ASCII equivalent
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
Added option to use simple filenames and replace unicode characters with their ASCII equivalent.
WHY: when sharing a disk between a linux machine running SB and a windows machine, for example by using Docker with a shared volume, the difference codepages mess up the visualisation of the file names. Everything keeps working just fine but it will look ugly. Using "simple" file names make sure we have maximum readability and stay as close as possible to the original names.
DRAWBACKS: It introduces another dependency to an external library.