-
-
Notifications
You must be signed in to change notification settings - Fork 300
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
Non-latin characters in results #520
Comments
Hi! Any news here? |
@mvarakin ... i have refactored wmic that it should now support UTF8 characters. As I want to have confirmation that this works before publishing it to npm, can you test all functions on your side? Easiest way would be to close from GitHub and run tests like so:
then go through all tests and see if results are fine on your side. Thank you in advance! |
Nope |
@Phamier @mvarakin thank you for testing ... I also got other feedback that this still is a problem. So I made more research and after hours I guess that at least for some (not all) of the commands I can solve the it ... let me work on it again a little bit and then we might see what I can come up with ... Hope that I have time to work on it the next weekend. |
@mvarakin Can you test this one more time? I made a transition to powerShell also for |
It returns wrong |
@Phamier thank you for reporting! |
Thanks a lot! |
Windows 10 with Russian locale
Sometimes strings come in Russian (this is more less ok, we can deal with it)
But sometimes strings come in unreadable format
On the example above there is no way to find default iface among all the list as there is no ID but only description which is unreadable.
The text was updated successfully, but these errors were encountered: