test: add regression coverage for ordinal indicators (º, ª) - #189
Open
mmaxjr wants to merge 1 commit into
Open
Conversation
Issue un33k#172 reported that slugify() doesn't transliterate the masculine/ feminine ordinal indicators (º, ª) common on Portuguese keyboards. Verified against both supported transliteration backends (text-unidecode>=1.3 and Unidecode>=1.1.1): both already map these correctly (º->o, ª->a) via their Latin-1 Supplement tables, so the bug no longer reproduces on the current codebase. Adding a regression test to lock in the correct behavior and close out the issue. Closes un33k#172 Co-Authored-By: Claude Sonnet 4.6 <[email protected]>
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.
Closes #172
Investigation
Issue #172 reports that
slugify()doesn't transliterate the masculine/feminine ordinal indicators "º" and "ª", common on Portuguese keyboards.
I tried to reproduce it and couldn't: on the current codebase, both
supported transliteration backends already handle these correctly: