Skip to content
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

Multilingual findings #130

Closed
noraj opened this issue Dec 1, 2020 · 7 comments
Closed

Multilingual findings #130

noraj opened this issue Dec 1, 2020 · 7 comments
Labels

Comments

@noraj
Copy link

noraj commented Dec 1, 2020

Another critical feature is having a Multilingual vulnerability database (findings library).

Pentesters from english-speaking countries are maybe the only ones that doesn't need this feature.
But in countries you will need to have a findings library in both English and your native language and some countries also have 2, 3 or more official languages.

@chrismaddalena
Copy link
Collaborator

That's a good point. This is supported in a roundabout way. Findings just need unique titles, so the same finding written in a second or third language can be added because the title strings wouldn't match. That makes it messy to maintain the finding, but it can be done.

It shouldn't be too difficult to engineer a way to create and link two or more versions for language options. It's not a feature I can work on immediately, but I definitely see its value and would like to add it.

@noraj
Copy link
Author

noraj commented Jan 6, 2021

It already exists in PwnDoc if you want to check how it's done there.

@reversebrain
Copy link

+1 on this. Normally I write reports in italian but sometimes happened that I had to write them in english, so having a multilingual support for findings would be great.

Copy link

github-actions bot commented Jul 6, 2024

This issue has been labeled as stale because it has been open for 30 days with no activity.

@github-actions github-actions bot added the stale label Jul 6, 2024
@noraj
Copy link
Author

noraj commented Jul 7, 2024

I don't see the benefits of stale bots…

@github-actions github-actions bot removed the stale label Jul 7, 2024
Copy link

github-actions bot commented Aug 7, 2024

This issue has been labeled as stale because it has been open for 30 days with no activity.

@github-actions github-actions bot added the stale label Aug 7, 2024
@noraj
Copy link
Author

noraj commented Aug 7, 2024

I'll close it as it's not planned, and I don't want to fight against the useless stale bot by bumping every 30 days.

@noraj noraj closed this as completed Aug 7, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

3 participants