Giter Club home page Giter Club logo

Comments (5)

Arno500 avatar Arno500 commented on May 18, 2024 1

I can now confirm everything is working as expected, filenames are respected, and console output in Powershell is still garbled πŸ˜ƒ (as expected too, since Lucida Console doesn't support Kanji I think).

EDIT : Long live UTF-8 everywhere ! (hoping Microsoft makes something for it)

from freac.

Arno500 avatar Arno500 commented on May 18, 2024

Oh, and I also tried your latest build from the 20190610 (from the issue #39), but it was before your file encoding modifications to your smooth library. And you don't provide a lot of informations to build Fre:ac on windows, so I kind of dropped it.

from freac.

enzo1982 avatar enzo1982 commented on May 18, 2024

Well, it works for me, see this screenshot made with freaccmd 20190423:

2019-07-07 233733

This is using the new Windows Terminal preview app which is the first to really support Unicode. It works with the regular console too, but you will not be able to input Japanese characters there. You can use tab completion, which will print placeholders for the CJK characters but still pass the correct file name to fre:ac.

fre:ac still prints ??? when processing the file, but processes it correctly. I'll see if I can fix the output to print in Unicode mode.

So if this doesn't work for you, something else must be wrong on your end.

from freac.

Arno500 avatar Arno500 commented on May 18, 2024

from freac.

enzo1982 avatar enzo1982 commented on May 18, 2024

I just pushed a commit with a few fixes. Unicode I/O on the Windows console should work as expected now:

screenshot

I also prepared a build for you to test: freac-1.1-alpha-20190708-windows-x64.zip

fre:ac actually was not getting passed Unicode file names on the command line, due to using the non-Unicode command line argument passed to WinMain. Unicode characters were passed as ? causing them to be interpreted as wildcards. That's why it still worked for me when I first tried. fre:ac just coincidentally found the correct file using the wildcard pattern.

The fix is to use the GetCommandLineW() function instead to get a Unicode version of the command line.

The console output issue was due to using the default ANSI codepage and was easily fixed by switching to UTF-8 with SetConsoleOutputCP().

from freac.

Related Issues (20)

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    πŸ–– Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo D3

    Bring data to life with SVG, Canvas and HTML. πŸ“ŠπŸ“ˆπŸŽ‰

Recommend Topics

  • javascript

    JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

  • web

    Some thing interesting about web. New door for the world.

  • server

    A server is a program made to process requests and deliver data to clients.

  • Machine learning

    Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google ❀️ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.