Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

bugfix for UTF16 vs UTF8 problems #471

Closed
wants to merge 11 commits into from
Closed

bugfix for UTF16 vs UTF8 problems #471

wants to merge 11 commits into from

Conversation

DBHeise
Copy link

@DBHeise DBHeise commented Jan 14, 2019

On systems running UTF16 prompt (i.e. CMD and/or PowerShell on Windows), ECHO will output in UTF16 which will not work in nodeJS (must have UTF8)

This change just moves the actions that were in a grunt file shell command, to a javascript file.

@CLAassistant
Copy link

CLAassistant commented Jan 14, 2019

CLA assistant check
All committers have signed the CLA.

@DBHeise DBHeise closed this Jan 14, 2019
@DBHeise
Copy link
Author

DBHeise commented Jan 14, 2019

will resubmit with passing lint tests

@mattnotmitt
Copy link
Collaborator

mattnotmitt commented Jan 14, 2019 via email

@DBHeise DBHeise reopened this Jan 14, 2019
@DBHeise DBHeise closed this Jan 14, 2019
@DBHeise DBHeise reopened this Jan 15, 2019
@n1474335 n1474335 added the bug label Jan 18, 2019
@n1474335
Copy link
Member

@d98762625 Could this be incorporated into the eventual solution in #291?

@DBHeise
Copy link
Author

DBHeise commented Jan 18, 2019

@d98762625 Could this be incorporated into the eventual solution in #291?

Unfortunately, no (or at least for the current implementation of #291), because it's the "echo" part of the grunt "exec:generateConfig" command, that is causing things to fail. As on Windows, it can output UTF16 instead of UTF8.

Closing this temporarily until I can figure out why the Travis CI build is failing with these changes.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants