-
Notifications
You must be signed in to change notification settings - Fork 30k
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
Encoding problems with umlauts in logged exception messages #3284
Labels
Comments
Confirming on Windows 7. Setting cmd to unicode with |
silverwind
added
confirmed-bug
Issues with confirmed bugs.
windows
Issues and PRs related to the Windows platform.
labels
Oct 8, 2015
It should be noted it displays as expected in the REPL at least. |
I assume REPL goes through libuv, while errors such as above are printed directly from C++. |
I have a fix coming soon... |
Ack! |
mscdex
added a commit
to mscdex/io.js
that referenced
this issue
Oct 13, 2015
The printf family of functions do not properly display UTF8 strings well on Windows. Use the appropriate wide character API instead if stderr is a tty. Fixes: nodejs#3284
3 tasks
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
I have the following simple script:
which when executed logs the following:
It seems the global exception handler does not use the appropriate output encoding, while
console
does.It doesn't seem to make any difference whether I encode my script as UTF8 or anything else - the first two logs are fine, but the error message is not.
Admittedly, I'm still on node v0.10.30. Would an update help?
The text was updated successfully, but these errors were encountered: