node-po fails to work with PO files from languages ending with the character `n`

[sanderhouttekier]

Just to give you a heads-up,

I created an issue on node-po's issue tracker requesting info on why he replaces the final n character when parsing headers.

this renders using english po files useless unless you manually replace the language string in the compiled angular translations.js. from eundefined into en

see the issue here: https://github.com/mikejholly/node-po/issues/7 however being the 7th issue in the 1 year of that repositories live, and none of the previous being closed or implemented, I doubt it will ever be picked up.

[rubenv]

Thanks for the heads up.

Sounds like it's time to fork it then!

[sanderhouttekier]

I shouted too early, pull request accepted, no need for a fork.

[rubenv]

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

[demetriusnunes]

Ruben, for some reason, setting the dependency on a specific git revision is making npm install fail on Windows machines.

[rubenv]

@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 out.