search

OWASP / Go-SCP

Golang Secure Coding Practices guide
https://owasp.org/www-project-go-secure-coding-practices-guide/
Creative Commons Attribution Share Alike 4.0 International
4.84k stars 369 forks source link

Traditional Chinese Version #16

Open kevingo opened 7 years ago

kevingo commented 7 years ago

Hi, this book is useful for gopher to follow the best practice of secure programming. Would you mind I translate this book to Traditional Chinese? I will link to origin repository and follows the license.

thanks

ErezYalon commented 7 years ago

Hi @kevingo, We will happy to accommodate your translation. Hopefully, this will be the beginning of a multi-language project where everyone can contribute translations to any language.

We will prepare the book structure to allow multiple languages. After that, you will be able to fork and create a branch for the translation.

kevingo commented 7 years ago

@ErezYalon That will be great! Looking forward to the new book structure 👍

PauloASilva commented 7 years ago

Hi @kevingo, I will test Gitbook Multi-Languages feature so that we can try to accommodate all Go SCP translations together in a single repository. This way, when accessing the book from Gitbook, users will have the possibility to choose not only the file format, but also the language.

I will keep you posted.

Best, Paulo

kevingo commented 7 years ago

@PauloASilva That's great. Currently I am starting my translation job. After finishing, I will create an issue with corresponding link here. Thanks :)

PauloASilva commented 7 years ago

Hi @kevingo, Can you please checkout our feature/i18n branch and test it? You will find instructions about how to switch languages to server and locally build the book in the How To Contribute section.

I will add another section in the How To Contribute section, explaining how it works, but basically:

  1. You should create a new folder inside the src one, naming it according the ISO 3166-2 (e.g. zh_tw);
  2. Place your files inside the new language specific folder (e.g. src/zh_tw).

We will also add some guidelines about a default disclaimer to be included right on top of the README.md file on every language: as you may understand we won't be able to validate every language.

Thanks for your interest and effort.

Regards, Paulo

kevingo commented 7 years ago

Hi @PauloASilva,

Sure! I will checkout the branch and test it locally.