Skip to content

TODO: Bug fixes and planned features #2

Description

@Polda18

Claude has identified an oversight in builder config, which needs to be corrected (as seen here):

Charset quirk: Debug|Win32 passes /execution-charset:cp852 to cl. The other three configurations don't. Source files contain Czech characters in author-attribution comments (Marek Polášek) — if you save them in a different encoding the Win32 Debug build can break in surprising ways. Prefer not to re-save source files unless you know what encoding they're in.

That is an oversight. The same argument should be passed into all of the 4 builder configs. That needs to be fixed before the next build.

Additionally, every source file should be in UTF-8 encoding, and conversions should be in place to convert everything into the correct format. The reason is to display the text properly in source code on GitHub. For resources.rc file, the strings format after conversion should be UTF-16 LE (Little Endian) for modern Win32 Windows NT. For runtime strings (output into the console), the charset should be MS-DOS Code Page 852.

Other bug fixes

  1. Replace the do-while loop with a while loop (the do-while cycle makes duplicate address prints on empty files).
  2. Fix the issue with the canonical hex+ASCII display that shifts the pipe character to the left if the file doesn't align exactly with multiples of 16 bytes)

TODO: Planned features

  1. Make Hexdump for Windows feature-complete parity with the original Linux tool. That means introduce stdin capability, making it possible to pipe a file contents output into the program input, introduce custom formatting capabilities, etc.
  2. Make a parity cmdlet for Powershell with similar functionality, but built-in .NET API
  3. Make a distribution package for winget to allow people to install this tool to their system easily

Metadata

Metadata

Assignees

No one assigned

    Labels

    bugSomething isn't workingenhancementNew feature or request

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions