You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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: mikejholly/node-po#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.
The text was updated successfully, but these errors were encountered:
@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.
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
intoen
see the issue here: mikejholly/node-po#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.
The text was updated successfully, but these errors were encountered: