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
Which version of Django are you using?:
Django 1.11.17
Which version of django-rosetta are you using?:
django-rosetta 0.9.3
Have you looked trough recent issues and checked this isn't a duplicate?
Yes.
I have for instance overwritten some templates from Django-allauth in my own app's template directory. The translations in those templates are translated in Allauth's own translations and are correctly translated in my app's front-end. This all works. The problem is that they are shown as untranslated in Rosetta so I never reach 100% translated strings there and it's also difficult to find out which strings are actually not translated.
Is there any way to make Rosetta aware that those strings are already translated? I have tried to add Allauth to LOCALE_PATHS and also to symlink its directory into my own app but without any luck.
Thanks for a great project btw ☺️ !
The text was updated successfully, but these errors were encountered:
Which version of Django are you using?:
Django 1.11.17
Which version of django-rosetta are you using?:
django-rosetta 0.9.3
Have you looked trough recent issues and checked this isn't a duplicate?
Yes.
I have for instance overwritten some templates from Django-allauth in my own app's template directory. The translations in those templates are translated in Allauth's own translations and are correctly translated in my app's front-end. This all works. The problem is that they are shown as untranslated in Rosetta so I never reach 100% translated strings there and it's also difficult to find out which strings are actually not translated.
Is there any way to make Rosetta aware that those strings are already translated? I have tried to add Allauth to
LOCALE_PATHS
and also to symlink its directory into my own app but without any luck.Thanks for a great project btw☺️ !
The text was updated successfully, but these errors were encountered: