Ruben Vermeersch

@Jesus89 This is angular-gettext-tools, which you normally only call from Node. What do you mean with ES5 projects?

I see, didn't expect them to make that much of a jump either. Either way: I'm pretty sure NW.js supports short function syntax, have you tried upgrading your runtime?

Thanks for the heads up. Sounds like it's time to fork it then!

Great, will bump dependency when there's a new release of `node-po`.

@demetriusnunes Which versions of Node and NPM? And unless you provide some info on what "making npm install fail" means, there's no way for me to be able to help...

You're right: filters don't scale well. I don't like them, but we need them for some cases (e.g. translated attributes). See https://github.com/rubenv/angular-gettext-tools/issues/39: we'll need a second filter to do plurals.

Yup, that could work as well. I'd be cool with that (it means we only need one filter!). We'd need to change the filter implementation as well then.

@gabegorelick I'm considering a release of angular-gettext without context support in filters. This gives us an opportunity to get the fixes out there and gives us more time to figure...

Moving to 2.1.

Would welcome a pull request! How do priorities work in Angular? Does the above get parsed as ``` {{ (app.showingMore ? 'Show less' : 'Show more') | translate }} ```...