Fonts/pixel_or_vibes
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions
Pixel or Vibes? A Rust pixel font library.
1 commit 1 branch 0 tags 31 KiB
Find a file
Exact
diaowinner 9104658bf3 [pov] initial commit
2025-11-16 22:03:42 +08:00
crates [pov] initial commit 2025-11-16 22:03:42 +08:00
.gitignore [pov] initial commit 2025-11-16 22:03:42 +08:00
Cargo.lock [pov] initial commit 2025-11-16 22:03:42 +08:00
Cargo.toml [pov] initial commit 2025-11-16 22:03:42 +08:00
LICENSE [pov] initial commit 2025-11-16 22:03:42 +08:00
README.md [pov] initial commit 2025-11-16 22:03:42 +08:00

README.md

Pixel or Vibes?

A Rust "knock-off" of TakWolf's font library in Python. MIT-licensed. No "vibes". No cryptos.

Crate inspired by is
encoding character-encoding-utils Encoding library for specific CJK encodings
kbit kbitfont Library for reading fonts in Kreative Korp's Bits'n'Picas' native format, kbits and kbitx
knife pixel-font-knife Font utilities
blocks unidata-blocks Unicode blocks and its translation
builder pixel-font-builder Just simply, pixel font builder
bdf bdffont BDF font library
pcf pcffont PCF font library

Why such an odd name? First reason is that I want the name odd. The second reason is here - although AI slops spreads through bunch of softwares from video making to music creating, they are still dumbass to make fixed, pixel stuffs (like sprites, font glyphs etc.) So there's no vibes when doing pixel stuffs, and we don't add any AI slops on our codes.

I have less time to do the thing, so it will take times to finish (it's not a big deal though). Once they're done, I think I will consider Python wrappers, as the fast alternative to TakWolf's library.

I'm a 100% noob when writing Rust codes (before, I always use Python in VS Code, from M$ Visual Studio Code's Pylance to VSCodium's Pyright to basedpyright, and shocked by other languages' performance on VS Code lmao). I'll try my best!