-
Notifications
You must be signed in to change notification settings - Fork 36
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Official GPL-2.0 license text not recognized #245
Comments
I figured out a problem that could explain this case. I think the tokenization does not work properly.
Returns
When I debug I see that for the first case in Also if I remove all
|
Thanks @sdheh for the analysis! I agree, the tokenization is the issue. I'm still working on the 3.0 update, so I won't have much time over the next week or so to look for a fix, but if you want to create a pull request I can review / merge. |
I ran into this issue as well and believe it affects several templates where the optional text would not be tokenized separately. For the above case I did experiment with the following change but am still learning the code base and am unclear on the total impact:
Modifying the parsed tokens feels wrong but could not sort out an easy way to adjust the tokenization of the license text being matched to the template. |
@douglasclarke this was fixed in PR #249, which is merged but awaiting release. |
@pmonks thanks. I believe I am testing with the latest code on master and still failing to get this case to work:
|
Thanks @douglasclarke for reporting this along with the specific example. This may be a separate issue - let's open a new issue and close this one as resolved since the prior examples seem to be fixed with the latest. |
Just a head's up that this license list XML issue will also cause matching of (recent) GPL-2.0 texts to fail, but not because of anything wrong in |
For the license text https://www.gnu.org/licenses/old-licenses/gpl-2.0.txt I get the following:
outputs
The two outputs should be the same since the GPL-2.0 license spans the whole file.
Tested with version 1.1.11
This problem is similar to 217
The text was updated successfully, but these errors were encountered: