Preparing to dive into the arcane world of #git, #utf8, #utf16le, and #BOM. If you don’t hear from me, send a search party. Why does Windows make working with text so hard?

Released v0.6.1 just fixing one stupid little regression from refactoring: The terminfo writer must never be used when output does *not* go to stdout 🙈

So far so good, I just thought there was yet another bug, testing redirected output on #Windows. I *always* got a file encoded as #UTF16LE, no matter which format I chose (and with #UTF8 chosen, the output was just broken). Meditated on the code for a while. Looks all perfectly good.

Finally, I tested in good old #CMD. And it worked perfectly well.

So, #Powershell is messing with the encoding of my stdout stream on redirects. Really? Really??? WTF, #Microsoft? How should that ever do any good? 🤯

https://github.com/Zirias/dos2ansi/releases/tag/v0.6.1

Release dos2ansi-0.6.1 · Zirias/dos2ansi

Bugfix release, only use terminfo/curses writer on stdout

GitHub

New pre-release of dos2ansi: v0.2

* Works on #Windows, win32 binary (cross-compiled on #FreeBSD) attached
* Selectable input #codepage (so far only #cp437, #cp850 and #cp858)
* Selectable output format, #utf8, #utf16 or #utf16le, with or without #BOM

Still a few things to add, e.g. use #termcap/#terminfo or Windows Console API for "color output" when applicable ... we will see 😎

https://github.com/Zirias/dos2ansi/releases/tag/v0.2

Release dos2ansi-0.2 · Zirias/dos2ansi

Selectable input codepage (so far only 437, 850 or 858) Selectable output format: UTF-8, UTF-16 or UTF-16LE Several smaller fixes, including correct operation on Windows

GitHub