home.social

#utf16le — Public Fediverse posts

Live and recent posts from across the Fediverse tagged #utf16le, aggregated by home.social.

  1. Ken Brucker @[email protected] ·

    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?

    #git #utf8 #utf16le #bom
  2. Felix Palmen 📯 @[email protected] ·

    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? 🤯

    github.com/Zirias/dos2ansi/rel

    #windows #utf16le #utf8 #cmd #powershell #microsoft
  3. Felix Palmen 📯 @[email protected] ·

    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 😎

    github.com/Zirias/dos2ansi/rel

    #windows #freebsd #codepage #cp437 #cp850 #cp858
  4. Felix Palmen 📯 @[email protected] ·

    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 😎

    github.com/Zirias/dos2ansi/rel

    #windows #freebsd #codepage #cp437 #cp850 #cp858
  5. Felix Palmen 📯 @[email protected] ·

    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 😎

    github.com/Zirias/dos2ansi/rel

    #windows #freebsd #codepage #cp437 #cp850 #cp858
  6. Felix Palmen 📯 @[email protected] ·

    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 😎

    github.com/Zirias/dos2ansi/rel

    #termcap #bom #utf16le #utf16 #utf8 #cp858
  7. Felix Palmen 📯 @zirias ·

    New pre-release of dos2ansi: v0.2

    * Works on , win32 binary (cross-compiled on ) attached
    * Selectable input (so far only , and )
    * Selectable output format, , or , with or without

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

    github.com/Zirias/dos2ansi/rel

    #windows #freebsd #codepage #cp437 #cp850 #cp858