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
When importing keys for a secondary locale, I would like Tolk to be able to read from multiple YAML files. Currently it's limited to one plain #{locale}.yml, and leaves out keys from files such as lists.sv.yml, products.sv.yml and so on.
For the primary locale, we are already calling I18n.backend.send(:translations) to get all keys, even when split over multiple files. I would assume that we could do the same for secondary locales?
Likewise, it would ease my translation management a lot if Tolk was able to output translations to multiple paths, following the naming used in the primary locale. I see two alternative ways to achieve this:
Store the original file path for each Tolk::Phrase in the db.
Traverse the keys of each primary locale file when dumping to see which translation goes where.
I looked through the import / export / sync files, and got the feeling that there's quite a bit of work ahead if I want to get this working. Therefore I thought I'd reach out first to see if others consider this a feature worth pursuing.
The text was updated successfully, but these errors were encountered:
In version 1.8 (if i remember correctly) we did something close. We use a regex to filter wich yml files are loaded. Improving this feature could help with your concern I think.
Thanks for the reply, I'm happy to hear this feature would be considered useful.
At the moment I am using a commercial SaaS for translation management, meaning it is not too likely I will start working on this feature for Tolk in the near future. It's up for grabs if anyone wants to give it a shot. :)
When importing keys for a secondary locale, I would like Tolk to be able to read from multiple YAML files. Currently it's limited to one plain
#{locale}.yml
, and leaves out keys from files such aslists.sv.yml
,products.sv.yml
and so on.For the primary locale, we are already calling
I18n.backend.send(:translations)
to get all keys, even when split over multiple files. I would assume that we could do the same for secondary locales?Likewise, it would ease my translation management a lot if Tolk was able to output translations to multiple paths, following the naming used in the primary locale. I see two alternative ways to achieve this:
Tolk::Phrase
in the db.I looked through the import / export / sync files, and got the feeling that there's quite a bit of work ahead if I want to get this working. Therefore I thought I'd reach out first to see if others consider this a feature worth pursuing.
The text was updated successfully, but these errors were encountered: