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 found that having to edit every "original" resource to be translated is tedious and in my opinion a superfluous step. I think it would be handy to have translation commands in the resource context menu. Thanks to that I could speed up repetitive translations (ie. translating the whole context or branch one after another).
The text was updated successfully, but these errors were encountered:
Translating a whole context in one go would be nice, indeed. However, in case of site I've just finished with there were gaps in translation as some res were missing in some contexts.
What I think about is to be able to translate a resource without having to edit it first. Thus the context menu idea.
I completely get your point.
I'm not sure how i could handle that without Custom Resource Class, but i take note of your idea and will see what i can do :)
I found that having to edit every "original" resource to be translated is tedious and in my opinion a superfluous step. I think it would be handy to have translation commands in the resource context menu. Thanks to that I could speed up repetitive translations (ie. translating the whole context or branch one after another).
The text was updated successfully, but these errors were encountered: