Timur Sağlam
Timur Sağlam
Sounds good to me so far! I think it is important that we think about where we persist the design rationale behind the dataset. E.g. if we have a plagiarised...
Closed by #548 and #551.
I fixed a few encoding issues by enforcing UTF-8 (#177 and #185), but these PRs concern the core and the Java 9+ frontend. Other language frontends might still use the...
Also, some language frontends use a grammar-based parser that explicitly limits identifiers to e.g. [a-z, A-Z, 0-9].
I think we might need to have a discussion internally on if and what licensing we want to enforce, as this also affects code/PRs of external contributors.
Great idea!
For Python it's something like 3.4 or 3.5, maybe I can find it again. EDIT: It is 3.6, the hint is hidden in #34, and its date matches as well.
A was also thinking of adding a state _label_ for each frontend: - `established` or `mature` (e.g. Java) - `beta` (e.g. EMF or C#) - `legacy` or `outdated` (e.g. C++...
Current state: | Language | Version | CLI Argument Name | [state](https://github.com/jplag/JPlag/wiki/3.-Language-Modules) | parser | --- | ---: | --- | :---: | :---: | | [Java](https://www.java.com) | 17 |...
@nestabentum, some conflicts need to be solved here before we can proceed.