Replies: 2 comments
-
Most of the work has already been done here: #259 |
Beta Was this translation helpful? Give feedback.
0 replies
-
Yes, I'm back from holidays (for a week) and hope to merge this PR in the following days. We can start accepting community translations afterwards. |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
Currently, SplitPro's interface is primarily in English. This creates a barrier for users who are not fluent in English, making the software less accessible and harder to use for a significant portion of the global community. As a Portuguese (Portugal) speaker, I've personally experienced this limitation.
I propose implementing a system for multi-language support that allows for community contributions to translations. This would enable SplitPro to be easily translated into various languages, making it more user-friendly worldwide.
A practical approach could involve:
languages/
orlocales/
folder in the repository..ini
,.json
, or.yaml
would make it easy for contributors (even those without deep development experience) to add or update translations for their native languages.For example, a pt_PT.ini file could contain:
I haven't considered complex, external translation platforms, as the goal is to keep it straightforward and enable direct community contributions via GitHub. Manually editing core code for translations is not scalable or maintainable.
Implementing this feature would significantly broaden SplitPro's appeal and user base. It empowers the community to help make the software accessible in their native tongues, fostering greater adoption and engagement. This approach leverages the open-source nature of SplitPro, allowing users to directly contribute to its improvement.
Beta Was this translation helpful? Give feedback.
All reactions