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

OpenSSF Best Practices Badges - Internationalization #160

Open
FredFousPro opened this issue Jul 8, 2022 · 2 comments
Open

OpenSSF Best Practices Badges - Internationalization #160

FredFousPro opened this issue Jul 8, 2022 · 2 comments

Comments

@FredFousPro
Copy link
Member

FredFousPro commented Jul 8, 2022

In order to fully validate the silver level of OpenSSF Best Practices Badges for our project, we have to fully implement internationalization.

Currently messages error are not translated and should be.

Here is the requirement to meet:
The software produced by the project SHOULD be internationalized to enable easy localization for the target audience's culture, region, or language. If internationalization (i18n) does not apply (e.g., the software doesn't generate text intended for end-users and doesn't sort human-readable text), select "not applicable" (N/A).

Here is the questionnaire :
https://bestpractices.coreinfrastructure.org/en/projects/5925?criteria_level=1

@Sander3003
Copy link
Member

The OpenSCD core initiative will help with more easy translations; This initiative excludes the error messages translations.

@dlabordus
Copy link

For the Backend Services we need to figure out how to do this and how it can be easily passed from the Frontend (OpenSCD) to the backend, maybe using some standardized HTTP Headers.

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

3 participants