Skip to content

About translations #1738

@ataseren

Description

@ataseren

Hello there, I have a suggestion about the translations. Currently, I'm translating ASVS to Turkish and the translation mechanism is easier for that project since there are versions of the standard and they are being updated in long periods. For this project, however, most of the cheat sheets are updated frequently and it makes impossible to apply such versioning.

My suggestion is using a versioning system for languages other than English. Each translated cheat sheet may have a date tag on them with a warning says that latest version is the English one. This is not the perfect solution but I think it is better than not having the cheat sheets in any other language.

To not cause any inconvenience, translated versions may only be stored in GitHub repository. In this way, there won't be any need for implementing a solution such as i18n as mentoned in #1410 . Also, PRs can be reviewed periodically to decrease the workload of verifying them.

Asking OWASP Chapters could be very useful because people from the chapters can be assigned to the translations of a language. But, such assignment may not be needed at all if there are (and I think there are) volunteers to translate them.

What do you think?

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions