Fredrick Brennan

Thanks Simon! Yeah, this will break poorly implemented software, like FontForge. (Cf. fontforge/fontforge#4751.) I imagine other similarly badly-thought-out C code is just doing `char[63]` somewhere.

Hmm. No idea why this works, but I was able to pull the repo, build, and copy `target/debug/cargo-edit-locally` to `/home/fred/.cargo/bin/`.

I have the same issue in i3. It is probably not easily fixable by the developer, though, as it works fine on real hardware. VirtualBox's 3D acceleration is really only...

See https://github.com/hodefoting/kernagic/issues/27#issuecomment-478231796 Not being a professional type designer, I don't understand the point of this project. Sorry.

(By the way, humorously I emailed Øyvind for another reason yesterday. Sorry for the noise Øyvind)

Here's my offer to you Dave. If you teach me what this tool is actually for and help me improve Chomsky's letter spacing I'll fix these bugs. I doubt you...

Unfortunately I couldn't get it to work at all...it creates empty kerning.plist and doesn't write any kerning information to features.fea. Providing the undocumented `-x` does write out a bunch to...

Right, I was replying to > This tool has rusted quite a bit due to disuse and my own current lack of interest in creating type While it is shocking...

I've fixed one CVE (libsixel#8) and followed up on the other (https://github.com/saitoha/libsixel/issues/134#issuecomment-857726044). Hopefully we can put that one to bed soon as well, pending reply by reporter or expiration (let's...

Both CVE security bugs are now remedied. (libsixel#8; libsixel#9) I have made the first new libsixel release in a long time as well, [1.9.0](https://github.com/libsixel/libsixel/releases/tag/v1.9.0). CVEセキュリティバグをすべて修正しました。(libsixel#8; libsixel#9) また、久しぶりにlibsixelの新規リリース[1.9.0](https://github.com/libsixel/libsixel/releases/tag/v1.9.0)を作成しました。