Hyphenate Filenames #405
Closed
Hyphenate Filenames #405
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
* Create filename template * Enable ZERO WIDTH SPACE (U+200B) in ulink.hyphenate * Minor comment and linebreak fixes
|
This is already integrated in the suse2022 stylesheets. Closing this PR. |
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.
Originally #348, by @tomschr:
Related to issue #339.
This PR contains the following changes:
ulink.hyphenateThe result will look like this:
I'm not sure if we should enable it. Please DO NOT merge it for the time being, as we should investigate it a bit further. It's just a "proof of concept" which we can play around, but I wouldn't want to see it in production code yet.
At the moment, we should keep in mind the following: