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
I used this rake tasks to synchronize and update my translations to newest spree defaults:
rake spree_i18n:update_default
rake spree_i18n:sync
After doing so all model and attributes translation were lost and resetted to the default value.
Thats because you namespaced the models and therefore the translation keys were changed from i.e product: to spree/product
Please fix the sync task to understand the namespace, otherwise all the translation effort from past years are obsolet!
The text was updated successfully, but these errors were encountered:
Looking at the history of the german translation file (and many other as well, I guess) is not very motivating. There are bulk commits that override perfectly translated phrases into their original values. I think that's related to this namespacing problem.
I am wondering if it is a better idea to just grab a copy of the YML file and use it for my spree application locally instead of referencing this github repository in my Gemfile. I don't want lots of hard work to be lost again after some wrong commits and the next bundle update (especially not in production!).
We will be looking into a better way of managing translations by using http://localeapp.com before Spree 2 comes out. You will not be managing the translations using rake commands any more.
I used this rake tasks to synchronize and update my translations to newest spree defaults:
rake spree_i18n:update_default
rake spree_i18n:sync
After doing so all model and attributes translation were lost and resetted to the default value.
Thats because you namespaced the models and therefore the translation keys were changed from i.e
product:
tospree/product
Please fix the sync task to understand the namespace, otherwise all the translation effort from past years are obsolet!
The text was updated successfully, but these errors were encountered: