WIP Improve handling of challenging file names when 'core.quotePath=true' #80
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.
As described in issue #78 transcrypt could fail to properly handle:
option 'core.quotePath' is set to 'true' (as it is by default)
This change improves handling of non-ASCII or space characters in
filenames and adds a test to exercise and confirm the fix.
Changes in particular:
output paths to ensure 'core.quotePath=false' is always applied
even when 'core.quotePath' is explicitly or implicitly (default)
set to true.