search

andry81 / contools

A wide range of scripts for Windows interpreter (cmd.exe) and other interpreters such as bash shell (.sh), visual basic (.vbs), jscript (.js), python (.py), perl (.pl) and so on. Plus some set of standalone console utilities and tools aside other utilities and tools from cygwin, msys and mingw. • :page_with_curl: https://github.com/andry81-stats/contools--gh-stats :page_with_curl:
https://sf.net/p/contools
MIT License
11 stars 0 forks source link

wxFileDialog.exe does not support UTF-8 #1

Open westyles opened 1 year ago

westyles commented 1 year ago

When run from cmd or ps with output (encoding) set to UTF-8, the utility still outputs in ANSI. And therefore the characters are not displayed. Same thing if output to a file, it gets ansi encoding.

For cmd it works like this: chcp 65001 wxFileDialog.exe "" . "Open Me"

Result with Cyrillic file name: Z:\ .txt

Same in PS:

& .\wxFileDialog.exe "" "." "Open Me"

Result with Cyrillic file name: Z:\ .txt

If you set cmd chcp 866 or PS [Console]::OutputEncoding = [System.Text.Encoding]::GetEncoding('cp866') then instead of Cyrillic characters are hieroglyphs. That is, the output does not match. It's not just about Cyrillic, but in general this problem of one encoding output.

andry81 commented 1 year ago

I will check that back as soon as I could resolve the issue with complete svn-to-git conversion of all mine repos.

https://github.com/chronoxor/gil/issues/6 https://github.com/dirk-thomas/vcstool/issues/243 https://github.com/dirk-thomas/vcstool/issues/249