Apparently there's a thing called #FollowFriday. Here are some open source projects that I think you should follow. #liblouis #riscv #haikuOS #CrossPlatformActions #rust https://liblouis.io/ https://riscv.org/ https://www.haiku-os.org/ https://github.com/cross-platform-actions https://www.rust-lang.org/

#TIL https://liblouis.io/translate/

Ich bin begeistert!

Quellcode: https://github.com/liblouis/liblous

:boost_ok: :replyOk:

#GameOverFuerBarrieren #GameOverFürBarrieren #Inklusion #Integration #FediLZ #EduDE #Blindenschrift #Liblouis #TeilhabeFürAlle #TeilhabeFuerAlle #followerpower #Fediversepower #boostokay #replyokay

The older version uses #liblouis's data files, but assumes liblouis is already installed. It also assumes that liblouis is installed in one particular place, so isn't very portable - it will fail at the whim of a platform's package manager. The new version bundles the data files with the code and can always find it, so it works no matter whether you're on #Linux, a Mac, #IllumOS, or anything in between.

It's this <https://github.com/larsbjorndal/App-Brl2Brl/pull/1>. The purpose is to bundle #liblouis's data with the code instead of assuming that the user has installed it separately, and also installing it at a known location instead of wherever the platform-specific package management tool decides to put it. I'm planning on creating Alien::liblouis and some XS jibber-jabber later to do the job properly, but this is a decent improvement for now that will make it more portable.

Spent the evening improving some #Braille software. #liblouis is a thing of wonder.

I have a question for all those hwo know stuff about licenses. I have created the #dotnet wrapper for the #liblouis braille translation and back-translation library. The whole engine is not just a simple wrapper, but it interacts with LL in a truely Dot-netty way. I have written the thing for my internal use but I wish to share it with the community, but I *DO NOT* want to share my source code with the external world. I am very much against Open SOurce as it currently stands hence i want to protect my work. If Liblouis is LGPL 2.1, can I release my wrapper as a close source component? Its highly probable I won’t ever release it outside the circles I wrote it for, but just in case.

On another note, I’m on the verge of writing my own #braille translator. I hate #liblouis with a pasison, and interfacing with that library is a pain in the neck. #programming

Why they have to complicate everything! I need to write a program that will trap letters on the keyboard, like globally hook them to do another action. Guess what, it took me freaking four hours to get it working cause… Windows 10 oddities, I don’t even wanna know if it does work on #windows 11 cause it probably doesn’t. Even #liblouis gave me less trouble and I thought its the worst library I have ever worked with. Nah I am tired.