Lmst

Hallelujah! #LibLouis rewritten in #Rust achieved its first testable version, Christian Egli announces in the official mailing list. Not every test passes, so Christian does request help from the community: test your #Braille tables and report any inconsistencies.
#GitHub: https://github.com/liblouis/louis-rs/
Rust crate: https://crates.io/crates/louis-rs
#Blind #Accessibility

What a news" #liblouis our awesome #braille translator is being rewritten in @rustlang
The internal testing is now taking place but since this is an open-source project developed in public meaningfull testing is probably welcome by anyone who is happy to take their favorite braille tables for a spin with this new version.
github.com/liblouis/louis-rs/

@menelion @fubsepude There definately are things that can be improved and are slowly improving for example a few years ago there was an issue browsing huge lists of items that's no longer such an issue any more. The webbrowser browse navigation is improving all the time. The accessibility labels and keyboard navigation in the settings app of @gnome is much improved. Gnome calendar is keyboard accessible. The default files app has incremental search that not only searches at the begining of file names but everywhere, we have configurable keyboard shortcuts for launching our apps and scripts, Access to reading PDF files has improved, I'm not using this but I know there are sound schemes for notifying desktop events. And so on and so on. Windows software is improving too.
As for the braille I don't have a braille display but our screen reader #orca is powered by the same translation engine your screen readers #nvda and #jaws are powered on windows, that's #liblouis.
Orca has flat review, sticky focus / sticky browse mode, application specific settings, settings profiles, progress bar beeps, auto restart when it freezes or crashes, ability to display flat review content in a window, object navigation, reconfigurable keyboard shortcuts, ability to present clipboard content, reporting system information such as ram / / cpu usage, It's now getting speech screen and braille screen output usefull for #a11y testing, browse mode features outside web content to combat bad authoring to an extend, Automatic language switching for web and document content, And perhaps other usefull features I'm not thinking of right now.
It's rich ecosystem, our screen reader is very powerfull too.
The best advice I can give you for all environments is know your tools, screen reader in particular and you should be fine.

On the front page of #Wikipedia today:

Did you know ... that John Boyer was forced to train his own guide dog because the training program could not support people who were both blind and deaf?

https://en.wikipedia.org/wiki/John_Boyer_(software_engineer)

(He's better known for creating #liblouis and other FOSS for the blind.)

Did you know ...

[picture of a consistometer measuring barbecue sauce]

... that ketchup in the US must be measured with a consistometer (example pictured) to be graded?
... that the Mitsubishi G6M was intended to be a escort gunship, but is best known as one of the transport aircraft that carried the Japanese surrender delegation to Iejima?
... that John Boyer was forced to train his own guide dog because the training program could not support people who were both blind and deaf?
... that Computer Mah-jong Yakuman was Nintendo's first handheld device providing multiplayer gaming via a link cable, an innovation that would later be integral to the success of the Game Boy?
... that there could have been as many as five individual leaders of the Big Three in World War II?
... that, nearly 50 years after the formation of Carlos y José, their grandsons, also named Carlos and José, formed Carlos y José Jr.?
... that Seattle mayor Thomas J. Humes went missing for more than 30 hours in 1902?
... that the African thin mouse shrew may have diverged from its nearest relative due to glacial cycles?
... that the theme song to SpongeBob SquarePants was written by Stephen Hillenburg with the idea "to try to make the most annoying song you can"?

We're so excited to welcome #liblouis, an essential copyleft tool for blind and visually impaired users, as SFC's newest member project!!

https://sfconservancy.org/news/2025/mar/17/liblouis-joins-software-freedom-conservancy/

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/liblouis

: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 or depending on whether you installed liblouis via the package manager or from source. The new version bundles the data files with the code and can always find them, so it works no matter whether you're on #Linux, a Mac, #IllumOS, or anything in between. 2/3

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.

@menelion @deafblind So with #liblouis installed and available on the path, I can call it like this:
echo "Merry Christmas" | lou_translate unicode.dis,en-us-g2.ctb
And it will output
⠠⠍⠻⠗⠽⠀⠠⠡⠗⠊⠌⠍⠁⠎

For most braille codes liblouis is a great source so we can be sure it's going to be right. Just change your table when calling.

@deafblind @menelion I like to use #liblouis lou_translate on the commandline for this.

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.

#liblouis

Client Info