-
Notifications
You must be signed in to change notification settings - Fork 1
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
Support non-English languages (Unicode) #24
Comments
Can you give me a sample string in Cyrillic to test with? |
Yes of course
"Привіт світ " Ukrainian
"Привет мир" Russian
It don't work when pass it to standardImport and by Console.Readline.
Thanks.
Пн, 20 серп. 2018, 16:26 користувач Bob <notifications@github.com> пише:
… Can you give me a sample string in Cyrillic to test with?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
<#24 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AhD9fSs3tEJP4z0Dnj9_a8cbhPkTkNHPks5uSscRgaJpZM4WEF1d>
.
|
Cool, thanks. I'll take a look tomorrow, should be fairly simple. Alternatively it might give me an excuse to move to named pipes... |
Ok, not quite as simple as I'd hoped. There's a lot of iffiness around Windows codepages that make encoding changes for stdin/stdout difficult (e.g. I can easily use a custom encoding when writing to a redirected Instead, let's stop using unreliable stdin/stdout altogether and switch to anonymous pipes, which can be passed directly to a child process. Effectively, this should be solved by #9. |
Please try https://github.com/BobVul/GrowlToToast/releases/tag/v2.0.3. Don't forget to run GrowlerInstaller after the main install so the Growl plugin is updated. |
Great job, thank you very much! |
now it also shows emojis 💃 great job! |
process.standardInput encoding problem - don't show cyrylic
Solution:
StreamWriter utf8Writer = new StreamWriter(proc.StandardInput.BaseStream, new UTF8Encoding(false));--disable bom characters
utf8Writer.Write(...);
utf8Writer.Close();
The text was updated successfully, but these errors were encountered: