Feature #3023
open
Rails models i18n support for plugins
Updated by Lukas Zapletal over 11 years ago
- Related to Feature #2942: Plugin i18n support added
Updated by Lukas Zapletal over 11 years ago
- Target version set to 1.15.0
- Difficulty set to medium
Also as part of this task, catch up with Gregs changes in discovery and update i18n string extraction. Implement models and javascript on discovery first, then update our plugin template.
Updated by Lukas Zapletal over 11 years ago
- Status changed from New to Assigned
Taking, first of all I want to fix discovery i18n and then I will carry on with this task.
Updated by Lukas Zapletal over 11 years ago
- Target version changed from 1.15.0 to 1.10.0
Updated by Lukas Zapletal over 11 years ago
- % Done changed from 0 to 50
Discovery i18n plugin is done, now taking foreman_setup to do some model fun.
Updated by Dominic Cleal over 11 years ago
- Target version changed from 1.10.0 to 1.9.3
Updated by Lukas Zapletal about 11 years ago
Note to myself - first do an investigation and estimation. This can be painful.
Updated by Anonymous about 11 years ago
- Target version changed from 1.9.0 to 1.8.4
Updated by Lukas Zapletal about 11 years ago
- Target version changed from 1.8.4 to 1.8.3
Updated by Lukas Zapletal over 10 years ago
- Subject changed from Add models and javascript i18n support for plugins to Rails models i18n support for plugins
Some discussion is here, for the record. Given the complexity of this it would be best to list all the translation in a separate file manually I guess.
https://github.com/grosser/gettext_i18n_rails/issues/100
Removing JavaScript part, Katello implemented that and can be taken as a good template for other plugins.
Updated by Lukas Zapletal over 10 years ago
- Status changed from Assigned to New
I dont really work on this, sorry to keep it so long.
Updated by Dominic Cleal over 10 years ago
Katello uses Angular rather than the same JS framework (inc gettext_i18n_rails_js) that Foreman does, right? I don't think it's comparable...