Do not completely lowercase the first word in a heading #29
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
1-1sam
changed the title
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.
Currently, Pod::Usage will completely lowercase all words in a heading if they contain three or less characters when using
-verbose 99. This behavior can provide undesirable results for some headings. For example, a heading namedSEE ALSOwill be formatted assee Also.This PR adds some additional formatting logic that ensures the first word of a heading has its first character uppercased regardless of length. This means that the above
SEE ALSOexample will now be formatted asSee Also. I believe this behavior will provide more desirable output for most users.