Skip to content

multi language open tasks #2315

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

Open
wants to merge 3 commits into
base: develop
Choose a base branch
from

Conversation

TwoOfTwelve
Copy link
Contributor

Fixes the open tasks from #2304

Copy link

@Kr0nox Kr0nox added this to the 6.1.0 milestone Apr 20, 2025
@tsaglam tsaglam requested a review from a team April 22, 2025 11:25
}

public List<Token> parseFiles(Set<File> files, boolean normalize) throws ParsingException {
this.printWarning();
List<Token> results = new ArrayList<>();
for (File file : files) {
Optional<Language> language = findLanguageForFile(file);
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

We discussed that we can find out at compile time whether the mapping of file extensions to language modules is well-defined. I would argue then that we should set up an actual look up table instead of repeating the same steps for each individual file.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This is not a specific warning, but a general one that is printed the first time the language module is used. See #2304

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

if someone wants to use the content and not only the file extensions: https://github.com/ArDoCo/magika we ported magika to java :)

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

We could do that, but I'd recommend doing it in a separate PR and everywhere in JPlag

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Yes, I meant it as general information . I would not implement it in this PR :)

@robinmaisch robinmaisch removed this from the 6.1.0 milestone Apr 24, 2025
@tsaglam tsaglam added enhancement Issue/PR that involves features, improvements and other changes minor Minor issue/feature/contribution/change labels Apr 29, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement Issue/PR that involves features, improvements and other changes minor Minor issue/feature/contribution/change
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants