aboutcode-org / aboutcode-org/scancode-toolkit

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

Ouverte
#4,843 1 commentaire 0 réactions 1 personne assignée Réclamée par @AyanSinhaMahapatra Voir sur GitHub
documentation
Langage dominant
Python
Étoiles
2.6k
Forks
791
Merge moyen
1 j 12 h
PR mergées (30 j)
5

Description

### 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

Guide de contribution

Ouvrir le guide de contribution

Évaluation

Cette issue n'a pas encore été évaluée.

Recevez les nouvelles issues par e-mail

Un résumé court des issues GitHub adaptées aux débutants.