feat(i18n): Comprehensive platform localization (Flows, Templates, Enrichers) - #195
feat(i18n): Comprehensive platform localization (Flows, Templates, Enrichers)#195sevasdron wants to merge 19 commits into
Conversation
Added Russian localization for all standard entity types and built-in enricher modules. Updated frontend UI components to dynamically resolve translations for labels, descriptions, and categories.
|
This is an absolute banger. Amazing. I'll review your PR very soon ! |
|
I'm glad I could be of assistance. I really liked your product. I was a bit hasty and missed a couple of tabs. I'll correct and add them now. |
… system info - Added Russian translations for 470+ entity fields and descriptions (`ru.json`). - Synced `en.json`, `fr.json`, `it.json` structures to maintain 100% key parity across locales. - Localized `ImportSheet` texts with i18n hooks and error fallbacks. - Refactored `InfoDialog` (About Flowsint) to use `dangerouslySetInnerHTML` instead of `<Trans>`. This fixes an i18next parsing bug where nested <strong> tags and blank spaces caused text duplication and broken HTML rendering in long text blocks.
|
Sorry, I was in a hurry, it needs some work. I'll come back later. |
…ings - Cleaned up duplicate translation keys across localization files - Translated hardcoded strings in FlowSheet and AddItemDialog components to use i18next hooks - Extracted and added missing Enricher descriptions directly from backend Python sources - Synchronized `ru.json` structure to strictly match `en.json` (master file) layout and ordering - Removed temporary parsing scripts and unused fr/it locales
…stigation and nodes components
|
Hey @sevasdron thanks for your work. You can leave it open and mark it as draft or work in progress :) |
Description
This PR introduces a comprehensive internationalization (i18n) layer for the Flowsint platform, transitioning the dashboard from hardcoded English strings to a fully dynamic localization system.
Key implementations include:
react-i18nexthooks.en.json,ru.json,fr.json, andit.jsonto share identical key structures. Original English text was preserved inen.json, ensuring stable behavior for English users while enabling full support for Russian and serving as a foundation for other languages.Motivation and Context
To support a global user base and make the platform accessible to analysts in multiple languages. By decoupling display text from component logic and backend docstrings, we enable easier maintenance and community-driven translations.
Type of change