You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
If the feature solves a problem you have, specify it here.
The project is currently available in a single language, limiting its accessibility to users who speak different languages.
Describe the proposed feature.
I propose implementing internationalization (i18n) support to make the project available in multiple languages. Key aspects include:
Identifying and extracting translatable strings.
Providing translations for common languages.
Allowing users to switch between languages within the project.
Describe alternatives you've considered
One possible solution is to group all the strings used inside different files, e.g. JSON, and read the values from the desired file depending on the user's language selection. That would be an approach very similar to what Android apps do to support multiple languages.
Another important tool to use for easier integration is Crowdin. It streamlines the localization process, allowing us to support multiple languages without the need for extensive manual translation management. It encourages collaboration among translators and ensures that our project is accessible to users worldwide.
Additional context
Internationalization support enhances the inclusivity of the project, making it accessible and user-friendly for a global audience.
No related issues are currently open.
Related Issues
N/A
The text was updated successfully, but these errors were encountered:
If the feature solves a problem you have, specify it here.
The project is currently available in a single language, limiting its accessibility to users who speak different languages.
Describe the proposed feature.
I propose implementing internationalization (i18n) support to make the project available in multiple languages. Key aspects include:
Describe alternatives you've considered
One possible solution is to group all the strings used inside different files, e.g. JSON, and read the values from the desired file depending on the user's language selection. That would be an approach very similar to what Android apps do to support multiple languages.
Another important tool to use for easier integration is Crowdin. It streamlines the localization process, allowing us to support multiple languages without the need for extensive manual translation management. It encourages collaboration among translators and ensures that our project is accessible to users worldwide.
Additional context
Internationalization support enhances the inclusivity of the project, making it accessible and user-friendly for a global audience.
No related issues are currently open.
Related Issues
N/A
The text was updated successfully, but these errors were encountered: