Feature Area
Web UI / Dashboard
Feature Description
Hi!
First of all, thank you for Pulsarr. I use it in my own setup, and I wanted to make it fully comfortable for Russian-speaking users. So I went ahead and completed the Russian localization for Pulsarr v0.17.3.
This is not only a translation file or a rough prototype. It is a complete working implementation that is already running in my Docker setup.
What is ready:
- a proper i18n layer with English as the fallback language;
- full
ru-RU localization of the interface, including navigation, Dashboard, Approvals, Plex, Radarr, Sonarr, Notifications, Utilities, dialogs, labels, placeholders and toasts;
- automatic browser-language detection;
- a language switcher with the selected language saved between sessions;
- Russian TMDb titles and descriptions using
language=ru-RU, with field-level fallback to en-US when Russian data is missing;
- no database migration and no change to the existing
/app/data contract;
- tests, typecheck, lint and production build passing;
- an automated coverage check showing 1,154 of 1,154 unique UI strings covered.
I also built and tested a separate Docker image based on the official v0.17.3 runtime. It is running successfully in my setup without changing the existing Pulsarr database.
I would like to give this entire implementation to the project completely free of charge and under the existing project license. There is no need to build the localization from scratch. I can provide it as a patch, branch or pull request in whatever format is easiest for you. I am also happy to make any cleanup or structural adjustments you request, so your part can be limited to reviewing and merging the approach you prefer.
Use Case
Russian is my primary language, and a fully localized interface makes Pulsarr much easier and more comfortable to use. I believe this would also make the project accessible to many more Russian-speaking Plex, Radarr and Sonarr users.
Because the implementation is already complete and tested, the feature can be added without developing the localization from scratch. After it is merged, the normal ongoing maintenance would only be adding new UI strings to the English and Russian catalogs when new features are introduced. I can continue helping with the Russian translations as well.
I have not published a fork yet because I wanted to ask first which contribution format and i18n structure you would prefer.
Would you be interested in accepting this into Pulsarr?
Proposed Solution
No response
Alternatives Considered
No response
Additional Context
No response
Feature Area
Web UI / Dashboard
Feature Description
Hi!
First of all, thank you for Pulsarr. I use it in my own setup, and I wanted to make it fully comfortable for Russian-speaking users. So I went ahead and completed the Russian localization for Pulsarr v0.17.3.
This is not only a translation file or a rough prototype. It is a complete working implementation that is already running in my Docker setup.
What is ready:
ru-RUlocalization of the interface, including navigation, Dashboard, Approvals, Plex, Radarr, Sonarr, Notifications, Utilities, dialogs, labels, placeholders and toasts;language=ru-RU, with field-level fallback toen-USwhen Russian data is missing;/app/datacontract;I also built and tested a separate Docker image based on the official v0.17.3 runtime. It is running successfully in my setup without changing the existing Pulsarr database.
I would like to give this entire implementation to the project completely free of charge and under the existing project license. There is no need to build the localization from scratch. I can provide it as a patch, branch or pull request in whatever format is easiest for you. I am also happy to make any cleanup or structural adjustments you request, so your part can be limited to reviewing and merging the approach you prefer.
Use Case
Russian is my primary language, and a fully localized interface makes Pulsarr much easier and more comfortable to use. I believe this would also make the project accessible to many more Russian-speaking Plex, Radarr and Sonarr users.
Because the implementation is already complete and tested, the feature can be added without developing the localization from scratch. After it is merged, the normal ongoing maintenance would only be adding new UI strings to the English and Russian catalogs when new features are introduced. I can continue helping with the Russian translations as well.
I have not published a fork yet because I wanted to ask first which contribution format and i18n structure you would prefer.
Would you be interested in accepting this into Pulsarr?
Proposed Solution
No response
Alternatives Considered
No response
Additional Context
No response