Better title casing #24
Open
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
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.
Fixes #18 and #25.
Previously, when
titlecasewas not installed, decoding fell back on Python's builtintitle()string operation for uppercasing the card name and subtypes. This resulted in awkwardness like "Brain In A Jar" and "Urza'S Mine".Now, in MSE and Gatherer modes, if the
titlecasemodule is not present, we at least swap out the most common faulty capitalizations for their lowercase versions.Previously, default text and forum decoding modes did no postprocessing on lowercase text.
Now, these modes put card names and type lines into title case, and rules text into sentence case. Additionally, card names are made bold in forum mode.