font-patcher: Sanitize output filenames #1029
Merged
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
[why] The filename is determined by the font (family) name. The font name might include characters that are forbidden to use in filenames. [how] Filter output filesnames and prevent any character that is likely forbidden under Windows. Also prevent control characters. Translate Windows path separators to posix. Fixes: #632 Signed-off-by: Fini Jastrow <ulf.fini.jastrow@desy.de>
# for free
to join this conversation on GitHub.
Already have an account?
# 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.
[why]
The filename is determined by the font (family) name. The font name might include characters that are forbidden to use in filenames.
[how]
Filter output filesnames and prevent any character that is likely forbidden under Windows.
Also prevent control characters.
Translate Windows path separators to posix.
Fixes: #632
Requirements / Checklist
What does this Pull Request (PR) do?
Replace problematic chars from the output filename with an underscore
_How should this be manually tested?
Any background context you can provide?
What are the relevant tickets (if any)?
Screenshots (if appropriate or helpful)