You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
About time someone actually is working on this. Indeed I18n is in need of an update in its format to allow foreign elements without always marking the subsequent string as html_safe.
Nevertheless, I see something missing: basically using it on top of I18ninstead of trying to replace it. So, instead of using the helper #it, i'd be using the old I18n.t, but I would be able to use the other It helpers inside it to handle the new markup.
Advantages: This lowers the overhead of introducing It in a new project by enhancing its features; otherwise I'll have to replace all I18n.t calls, and for some projects that's prohibitive. Also, the future merge of your idea into the actual i18n gem would be easened and the gems would be more of collaborators instead of competitors.
The text was updated successfully, but these errors were encountered:
Thank you for your proposal. I agree with your reasons, it should be possible to replace or extend one of the existing backends. Unfortunately, I don't have time for this at the moment, but the next time I do a major contribution here, I'll consider it.
Hi
About time someone actually is working on this. Indeed I18n is in need of an update in its format to allow foreign elements without always marking the subsequent string as html_safe.
Nevertheless, I see something missing: basically using it on top of I18ninstead of trying to replace it. So, instead of using the helper #it, i'd be using the old I18n.t, but I would be able to use the other It helpers inside it to handle the new markup.
Advantages: This lowers the overhead of introducing It in a new project by enhancing its features; otherwise I'll have to replace all I18n.t calls, and for some projects that's prohibitive. Also, the future merge of your idea into the actual i18n gem would be easened and the gems would be more of collaborators instead of competitors.
The text was updated successfully, but these errors were encountered: