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

Translate database in russian #26

Open
m0sth8 opened this issue Apr 4, 2015 · 7 comments
Open

Translate database in russian #26

m0sth8 opened this issue Apr 4, 2015 · 7 comments
Assignees

Comments

@m0sth8
Copy link
Contributor

m0sth8 commented Apr 4, 2015

No description provided.

@m0sth8 m0sth8 self-assigned this Apr 4, 2015
@andresriancho
Copy link
Contributor

Is there a way to crowd-source this?

@Zapotek
Copy link

Zapotek commented Apr 5, 2015

Maybe we can hold off on translations altogether until the project gets stable and gains some traction?
I don't want us to get into a situation where we have partial or outdated translations.

@andresriancho
Copy link
Contributor

Agreed

@psiinon
Copy link

psiinon commented Apr 7, 2015

We use crowdin for ZAP translations - its free for open source projects, and its been great for us - we have over 120 translators :)
https://crowdin.com/project/owasp-zap/
https://crowdin.com/project/owasp-zap-help/

The vulnerabilities.xml file we use is in the owasp-zap project, at the top level.
Again, feel free to grab anything of use from this and just should if you have any questions etc

@mdeous
Copy link
Contributor

mdeous commented Oct 8, 2017

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.

@andresriancho
Copy link
Contributor

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 en directory for storing the existing content, and then create different directories for each translation: fr, ru, etc.

@mattoufoutu Give me a couple of days to review all this, complete #30 , and you'll have everything ready to work on fr

andresriancho pushed a commit that referenced this issue May 3, 2018
@andresriancho
Copy link
Contributor

Translation documentation at https://github.com/vulndb/data/wiki/Translations

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

5 participants