aboutcode-org / aboutcode-org/scancode-toolkit

Explain when and where comma, whitespace, etc. are ignored

未關閉
#4,843 1 則留言 0 個 reaction 已指派 1 人 已被 @AyanSinhaMahapatra 認領 在 GitHub 檢視
documentation
主要語言
Python
星號
2.6k
分支
791
平均合併
1 天 12 小時
30 天內合併 PR
5

描述

### Description

> A brief description of the Documentation Improvement or New Section request.

I am currently scanning a file with the following license reference:

```
Licensed under GPLv2, see file LICENSE in this source tree.
```

scancode reports a match for rule `gpl-2.0_147.RULE` which has the following:

```
Licensed under GPLv2.
```

The file I am scanning has a comma, while the rule has a dot, yet it matches. This makes me wonder if scancode first preprocesses data and ignores commas, whitespace, and others, and if so: when (at the end of a sentence? mid-sentence?). This could possibly be relevant when writing license rules.

### Link to Documentation Page

> Where the confusion/inconsistency/incomplete documentation is.

### Select Category

- [ ] Inconsistency
- [ ] New Section Request
- [ ] General Improvement
- [ ] Typo/Mistakes
- [X] Other

貢獻指南

開啟貢獻指南

評估

這個 Issue 還沒有評估資料。

把新 issue 寄到你的電子郵件信箱

精選適合新手參與的 GitHub issue 摘要。