Jan Philipp

Did you already have checked out the latest added strategies since the 2.12 release?

Complete overview here: http://plnkr.co/rJ0R6GzHGbMVxhSa237C - sce: This strategy (just like sanitize) can be used, because you should trust your own translation texts (it's your code). Especially containing HTML, this is...

I'm quite not sure I'm missing some critical case, but that would be one: http://plnkr.co/edit/O56vFM70tVbhh8DrUcfs?p=preview (look for "escape2") (3.1b) ``` js .config(function($translateProvider, $translateSanitizationProvider) { $translateSanitizationProvider.addStrategy('custom', 'escape2'); $translateProvider.useSanitizeValueStrategy('custom'); }) .factory('escape2', function...

Well, If you have a have computed safe string (by the service), you should bind it probably. I guess a trustAsHtml should work?

Hm, get it. This requires some work as directive and service cannot be distinguished at the moment.

Meanwhile, `context` has been added in mostly all calls. The strategy `sce` is using this already.

Hello, as we had already mentioned in the [issue's template](https://github.com/angular-translate/angular-translate/blob/master/.github/ISSUE_TEMPLATE.md), we need a working and as minimal as possible demo covering your specific use case or issue. Follow these steps:...

> Not in plunker but in a normal app it is executed Again, please provide a working demo demonstrating the issue. How should we verify this will work?

Sorry for the delay, I had not complete my inspections on this issue days ago. At the moment I'm wondering what the implication is exactly. The demo is demonstrating nothing...

Okay, now we have a working demo. http://plnkr.co/edit/KJVdvDNI8P2LEOK4uFAi?p=preview