Wtfiles Alternatives

Similar projects and alternatives to wtfiles

zig

816 30,773 10.0 Zig wtfiles VS zig

General-purpose programming language and toolchain for maintaining robust, optimal, and reusable software.
dmd

146 2,888 9.9 D wtfiles VS dmd

dmd D Programming Language compiler
InfluxDB

www.influxdata.com featured

Power Real-Time Data Analytics at Scale. Get real-time insights from all types of time series data with InfluxDB. Ingest, query, and analyze billions of data points in real-time with unbounded cardinality.
nomicon

87 1,693 5.6 CSS wtfiles VS nomicon

The Dark Arts of Advanced and Unsafe Rust Programming
mach

36 2,787 9.7 Zig wtfiles VS mach

zig game engine & graphics toolkit
RIIR

17 614 3.5 wtfiles VS RIIR

why not Rewrite It In Rust
arocc

10 765 9.7 Zig wtfiles VS arocc

A C compiler written in Zig.
zigstr

3 108 6.7 Zig wtfiles VS zigstr

Zigstr is a UTF-8 string type for Zig programs.
SaaSHub

www.saashub.com featured

SaaSHub - Software Alternatives and Reviews. SaaSHub helps you find the best software and product alternatives
ziglyph

5 207 6.7 Zig wtfiles VS ziglyph

Unicode text processing for the Zig programming language.
dstep

4 202 6.5 C wtfiles VS dstep

A tool for converting C and Objective-C headers to D modules
cc-rs

8 1,731 9.0 Rust wtfiles VS cc-rs

Rust library for build scripts to compile C/C++ code into a Rust library
ohmygentool

1 38 3.9 C++ wtfiles VS ohmygentool

LLVM/Clang based bindings generator for D language
utfcpp

3 1,419 7.3 C++ wtfiles VS utfcpp

UTF-8 with C++ in a Portable Way

NOTE: The number of mentions on this list indicates mentions on common posts plus user suggested alternatives. Hence, a higher number means a better wtfiles alternative or higher similarity.

Suggest an alternative to wtfiles

wtfiles reviews and mentions

Posts with mentions or reviews of wtfiles. We have used some of these posts to build our list of alternatives and similar projects. The last one was on 2021-09-08.

Maintain It with Zig
16 projects | news.ycombinator.com | 8 Sep 2021

Keep in mind that filesystem paths aren't strings. On Linux, they are raw bytes without any fixed encoding (but usually UTF-8 on UTF-8-based locales), and on Windows, they are sequences of 16-bit codepoints which are expected to be UTF-16 but not validated.
Rust's OsStr is my favorite approach so far. It stores Linux's raw bytes as-is, and stores Windows's possibly-valid UTF-16 as WTF-8. This makes path management "just work", with the ability to operate normally on invalid UTF-8 or UTF-16 paths, and zero-copy conversion from UTF-8/ASCII strings to OsStr (though converting OsStr into UTF-16 requires parsing). (Qt's QString-based file dialogs on Linux fail to convert invalid UTF-8 paths like those in https://github.com/petrosagg/wtfiles into QString, causing Qt-based apps to open/save the wrong paths.)
However there are difficulties in printing an OsStr. For example, a file dialog that shows filenames as raw bytes can't show non-Latin/Unicode characters in a human-readable form, and a file dialog that shows filenames as Unicode strings can't handle invalid Unicode filenames. GTK3 file dialogs show filenames as Unicode strings, and when encountering files with invalid Unicode names, instead displays "file�name.txt (invalid encoding)".
Worse yet, how should a file dialog allow users to rename files? If it's based around byte arrays, the user can't enter Unicode characters directly, and if it's based around Unicode (or a locale-specific text encoding), it can't display existing files with invalid Unicode/etc. in the name (probably not an issue if it allows the user to rename to a valid name), nor allow users to enter invalid Unicode (which is not an issue IMO).

Stats

Basic wtfiles repo stats

Mentions

Stars

Activity

3.3

Last Commit

3 months ago

Popular Comparisons