Describe the feature
Is there an existing issue for this?
What happened?
Lack of Internationalization (i18n) Support
The application currently uses hardcoded English strings throughout the frontend codebase. This prevents the interface from being translated into other languages, limiting accessibility for non-English users and blocking global community contributions.
File: frontend/src (General)
Step Action
| Step |
Action |
| 1 |
Open the PictoPy source code (e.g., LeftSidebar.tsx or Settings.tsx). |
| 2 |
Locate UI elements like buttons or labels. |
| 3 |
Result: Observe that text is hardcoded (e.g., <button>Save</button>) instead of using translation keys (e.g., {t('save')}). |
| 4 |
Open the PictoPy application and go to Settings. |
| 5 |
Result: There is no option to switch the interface language. |
Suggested Solution
Integrate a library like i18next and react-i18next. Extract hardcoded strings into locale files (e.g., en.json) to allow the community to submit translations for other languages.
Record
Add ScreenShots
Record
Describe the feature
Is there an existing issue for this?
What happened?
Lack of Internationalization (i18n) Support
The application currently uses hardcoded English strings throughout the frontend codebase. This prevents the interface from being translated into other languages, limiting accessibility for non-English users and blocking global community contributions.
File:
frontend/src(General)Step Action
LeftSidebar.tsxorSettings.tsx).<button>Save</button>) instead of using translation keys (e.g.,{t('save')}).Suggested Solution
Integrate a library like
i18nextandreact-i18next. Extract hardcoded strings into locale files (e.g.,en.json) to allow the community to submit translations for other languages.Record
Add ScreenShots
Record