ngPluralize: support for HTML tags in translations?

[ysbaddaden]

I found myself in a situation where some of the translation, and not all, must be within a strong tag. Since the ngPluralize directive uses element.text() (source) then the string is HTML escaped, and it doesn't work.

<ng:pluralize count="users.length" when="{other:'<strong>{}</strong> users'}" />

Since it may lead to XSS issues, I was wondering how to allow ngPluralize to use element.html() in some cases. If $interpolate already escapes the interpolated values, then maybe the directive could use element.html()? Or may be add an attribute like as="html" to give the user control over the HTML safeness of the translation? All it would need then is:

function ngPluralizeWatchAction(newVal) {
  if (attr.as === 'html') {
    element.html(newVal);
  } else {
    element.text(newVal);
  }
}

[samward1985]

+1

[Casperd88]

+1

[guillaumesmo]

+1

[wagnerdevel]

+1

[hamsterready]

+1

[josh256]

+1

[xaralis]

+1

[PatrickWolleb]

+1

[jbielick]

+1

[amitport]

:+1:

[squarecapadmin]

+1

[blair55]

+1

[scanferla]

+1

[shanecp]

+1

[imjoshholloway]

+1. In the mean time I've created a gist that I'm using in place of ngPluralize where I need HTML

[krazi3]

+1

[AshCoolman]

:+1:

[thicolares]

+1

[jhalley]

+1

[lgalfaso]

Using html with pluralize should be strait-forward with a small ad-hoc directive as it is the case here http://plnkr.co/edit/mkKt5rqYorGu4a1t93J8?p=preview

[manikanta896]

+1

[nicolasmoise]

+1

[danpe]

+1

[christianesperar]

Hi, this seems a little bit late, but in case anyone still has some problem with this one, I created directives that can solve this problem. It can be found here https://github.com/christianesperar/ng-pluralize-html

You can see it in action here https://rawgit.com/christianesperar/ng-pluralize-html/master/example/github.html