Translate directive does not always work correctly

Steps to reproduce

We have encountered problems considering the language directive provided by angular-translate.

In places that were using this directive correctly according to https://angular-translate.github.io/docs/#/api/pascalprecht.translate.directive:translate, the translation does no work correctly.

Encountered problems:

Case 1: <[...] tranlsate="STRING">Edit<[...]/> does not work, but <[...] translate="STRING"><!--Edit--><[...]/> does.
Reference: https://bitbucket.org/opencast-community/matterhorn/pull-requests/962/mh-11555-localisation-of-recordings-events/diff

Case 2: When reloading the page in the browser, the translation does not work anymore
Reference: https://bitbucket.org/opencast-community/matterhorn/pull-requests/957/mh-11548-the-edit-button-at-the-top-right/diff

Activity

Show:
Sven Stauber
May 10, 2016, 2:40 PM

It turned out that it indeed does work correctly:

In case 1, some translation keys were not present in the translations. In that case, the describe phenomena occurs, but that's actually only the case when the translation files are incomplete which is also an error.

In case 2, it seems that element value simply should not be used.

Cannot Reproduce
Your pinned fields
Click on the next to a field label to start pinning.

Assignee

Sven Stauber

Reporter

Sven Stauber

Severity

Usability Issue