-
Notifications
You must be signed in to change notification settings - Fork 29
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
Translate database in russian #26
Comments
Is there a way to crowd-source this? |
Maybe we can hold off on translations altogether until the project gets stable and gains some traction? |
Agreed |
We use crowdin for ZAP translations - its free for open source projects, and its been great for us - we have over 120 translators :) The vulnerabilities.xml file we use is in the owasp-zap project, at the top level. |
Any news regarding multi-language support? Has any workflow or tool (like crowdin as suggested by @psiinon) been agreed upon? I'd be happy to help translating to french. |
No news on this front, but I believe that the project is stable enough so we can start thinking about it. The only task that seems to be a good idea to perform before starting a translation is #30 Once that's done, the main effort will be to translate the markdown files. JSON files will still contain some English, but we can translate that really quick, since it would be: title, severity, and maybe tags. In terms of file organization, it seems that inside https://github.com/vulndb/data/tree/master/db we'll have to create an @mattoufoutu Give me a couple of days to review all this, complete #30 , and you'll have everything ready to work on |
Translation documentation at https://github.com/vulndb/data/wiki/Translations |
No description provided.
The text was updated successfully, but these errors were encountered: