Explain text normalization in license matching documentation#4854
Open
kushal-p16 wants to merge 1 commit intoaboutcode-org:developfrom
Open
Explain text normalization in license matching documentation#4854kushal-p16 wants to merge 1 commit intoaboutcode-org:developfrom
kushal-p16 wants to merge 1 commit intoaboutcode-org:developfrom
Conversation
Add documentation explaining how ScanCode handles text normalization during license matching. This includes handling of whitespace, punctuation, and case differences to ensure robust license detection even when text formatting varies. Signed-off-by: KUSHAL P <kushalmys55@gmail.com>
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.
This PR adds documentation explaining how ScanCode handles text normalization during license matching, including handling of whitespace, punctuation, and case differences.
This helps clarify why similar license texts with minor formatting differences can still result in a match.
Fixes #4843