Alternatives
Products that do what xxUTF – SIMD Unicode Normalization does
- 1CF
2024 · github.com
- 2OC
I’m building a Unicode reference where each symbol has its own dev-friendly page with all relevant encodings. Example: [https://fontgenerator.design/symbol/almost-equal-to](https://fontgenerator.design/symbol/almost-equal-to) Includes Unicode, HTML, CSS, JS, UTF-8/16 bytes, URL encoding, and usage examples. The same structure is used across thousands of symbols (math, arrows, currency, tech/UI, punctuation). Built because existing references are fragmented. Feedback welcome.
Dec 2025 · fontgenerator.design
- 3USunicode.style▲125
2018 · unicode.style
- 4
- 5SL
I made a free tool that stuns LLMs with invisible Unicode characters. *Use cases:* Anti-plagiarism, text obfuscation against LLM scrapers, or just for fun! Even just one word's worth of “gibberified” text is enough to block most LLMs from responding coherently.
Nov 2025 · gibberifier.com
- 6WT
After working with LLMs for long enough, I found myself wanting a lightweight utility for doing various small tasks to prepare inputs, locate information and create evaluators. This library is two things: a very simple model and utilities that inference it (eg. fuzzy deduplication). The target platform is CPU, and it’s intended to be light, fast and pip installable — a library that lowers the barrier to working with strings semantically. You don’t need to install pytorch to use it, or any deep learning runtimes. How can this be accomplished? The model is simply token embeddings that are…
2024 · github.com
- 7JK
Justif is a drop-in JavaScript library that progressively enhances web pages to TeX-level text justification. Installation is a single line, standard text and accessibility affordances are unchanged, and users with JS disabled get native browser rendering. I made justif because I've long been a fan of justified text. I think it looks clean and elegant, and makes reading more enjoyable. But bad justification is the opposite, with gaping spaces that distract me to the point of making the text near unreadable. Browsers have got better recently at handling justified text [0][1], but still use…
Jul 2026 · justif.lyall.co
- 8MA
I've written Mojibake because I don't like the other Unicode libraries for Unicode support. It consists of only two amalgamation files: mojibake.h and mojibake.c. I've added all the most important Unicode algorithms, such as normalization, case conversion, segmentation, bidirectional text, collation, confusable, and others. I regularly test it in these OSes: Linux, macOS, FreeBSD, OpenBSD, NetBSD, and Windows 11. You can find a WASM demo on that site of all the public API functions and the documentation. If you want to participate, feel free to do it. Any kind of help is welcome. Check the…
Jul 2026 · mojibake.zaerl.com
- 9ZJ
2020 · bennettfeely.com
- 10HS
2021 · github.com
- 11FU
2019 · github.com
- 12US
I built a demo of two Unicode steganography techniques, zero-width characters and homoglyph substitution, in the context of AI misalignment. The first is about the use of two invisible zero-width characters (ZWS and ZWNJ) to binary encode text. The second is much cooler. Most characters in the Latin and Cyrillic alphabets look nearly identical, but have different unicode. If you have text to encode and convert it into binary representation (1s and 0s), you could take plain english "carrier" text and for each 1 in the binary representation you could substitute the Cyrillic letter equivalent.…
Apr 2026 · steganography.patrickvuscan.com
- 13FS
I want to share a really dumb, but very practical project I have packaged this summer, to perform operations on strings much faster. I was using Python to work with a multi-terabyte newline-delimited file. Reading, splitting, and shuffling it was a nightmare. So, I wrapped a trivial hardware-friendly heuristic I've been using for the last few years into a CPython library. The part I enjoyed the most is implementing SIMD behavior without SIMD instructions... Using 64-bit words to work at 8-bit granularity. Unlike conventional SIMD, the code would remain the same for ~~almost~~ any hardware.…
2023 · ashvardanian.com
- 14UO
2012 · unicodefor.us
- 15AW
2025 · fontgenerator.cool
- 16UU
2022 · github.com
- 17WO
I ported Markus Kuhn’s wcwidth to TypeScript and optimized it with bitset lookups for O(1) performance. It now covers the full Unicode 15.1 combining ranges. GitHub: https://github.com/dawsonhuang0/Wcwidth-O1 NPM: https://www.npmjs.com/package/wcwidth-o1 Feedback welcome!
Sep 2025 · github.com
- 18LN
2016 · github.com
- 19UL
2021 · unicode.emnudge.dev
- 20RL
We've been building data pipelines that scrape websites and extract structured data for a while now. If you've done this, you know the drill: you write CSS selectors, the site changes its layout, everything breaks at 2am, and you spend your morning rewriting parsers. LLMs seemed like the obvious fix — just throw the HTML at GPT and ask for JSON. Except in practice, it's more painful than that: - Raw HTML is full of nav bars, footers, and tracking junk that eats your token budget. A typical product page is 80% noise. - LLMs return malformed JSON more often than you'd expect, especially with…
Mar 2026 · github.com
- 21TP
2022 · github.com
- 22MC
multilspy is a cross-platform library that we have built to set up and interact with various language servers in a unified and easy way. Language servers are tools that perform a variety of static analyses on source code and provide useful information such as type-directed code completion suggestions, symbol definition locations, symbol references, etc., over the Language Server Protocol (LSP). multilspy intends to ease the process of using language servers, by abstracting the setting up of the language servers, performing language-specific configuration and handling communication with the…
2024 · github.com
- 23OT
2019 · gitlab.com
- 24JN
Hi HN! I'm Alex, a tech enthusiast. I'm excited to show you Jesth, a next-level human-readable data serialization format. This project started out as a markup language for writing the docstrings of functions that would ultimately be consumed by a documentation generator. Basically the idea was to split a docstring into sections like Description and Parameters. Each section would consist of a header in square brackets and a body (lines of text between two headers). Here's what a docstring for a sum function would look like: This function takes in two integers a and b and returns their sum.…
2023 · github.com
Ranked by how close each launch is in meaning, then by votes. Refine with a description →