Learn Six Ways to Increase Productivity with Braille and JAWS blog.freedomscientific.com/lea…

Ahahaha y'all wanna know why some people hear whispering and others don't? With the latest NV Speech? I know who might. @@radiorobbe who reported it first.
The Root Cause: "Dot" vs. "Comma"
NVDA Sets the Locale: When you set NVDA's interface language to Spanish, Hungarian, German, Polish, etc., NVDA configures the Python process's global locale (via setlocale) to match that region. In the US/English locale, the decimal separator is a dot (e.g., 0.5, 60.0). In many European/South American locales (the "supported languages" you noticed), the decimal separator is a comma (e.g., 0,5, 60,0). The DLL Inherits the Locale: The nvspFrontend.dll is loaded into the same process space. The standard C++ string parsing functions (like atof, strtod, or std::stringstream) often respect this global locale setting. So, all the YAML files become invalidly parsed because they use a period. Ha. Wow. What a bug.

The weirdest part of self-hosting isn't the control, it's the silence.
I logged into my dashboard tonight via the tunnel. No banner ads. No
"suggested content" algorithms designed to doomscroll me. No tracking pixels firing off to a data broker in Utah, lol.
Just my tools, sitting there, waiting.
We really forgot what the internet feels like when it isn't trying to extract value from us every single second. It’s quiet here. I like it.
#digital #minimalism #selfhosted #SmallWeb #AdFree

:PleaseReblog:
Question for people relying on alt text: When one posts contains multiple images, should each alt text be written independently, or does it make more sense for one text to refer back to previous ones?
Like, when the first describes shape and colour of a flower, should the second copy that description and add to it (independent alt texts), or refer back, like "the same flower [from a different angle, showing xyz]"?

#altText #imageDescriptions #Blind #questions

  • independently (16%, 13 votes)
  • refer back (45%, 36 votes)
  • just show results (38%, 31 votes)
80 voters. Poll end: in 6 days

This entry was edited (22 hours ago)

Jak se z nás stali geokačeři
Přemýšlel jsem, jak v pochmurném prosincovém počasí dostat děti ven, až mě napadl geocaching, který se ukázal jako trefa do černého. Pár řádků o tom, jak se z nás stali geokačeři.
#děti #geocachingblog.eischmann.cz/2026/01/17/j…(reakce na tento příspěvek se může zobrazit jako komentář pod článkem)

reshared this

yes, yes. The output for "level" seems incomplete, possibly missing leading "l" and "və." This might be happening because the pointer iteration isn't handled properly in the script. espeak_TextToPhonemes might modify the text pointer internally, and I may need to adjust this to correctly handle wide char pointers (wchar_t*) instead of using c_void_p. Let's fix that. Why not, let's fix it all. All the bugs. Fix fix fix. No breaks.
in reply to Cleverson

@clv1 nah, I updated them just recently :) the instructions should be recent. It now talks about the formats for the various pack files, so definitely do a control+shift+R just to make sure you get the latest version.
Espeak is able to speak many of them, but you have to like, read them as individual letters sometimes. Yeah. I think JAWS is the only one I know where there's a way to get Eloquence to speak IPA, and supported posts about this (ruf.rice.edu/~reng/jaws-ipa.ht…) but it's tricky for sure. I will switch to Espeak sometimes in this workflow (or Speechplayer) and see how it speaks the symbol and compare as it's the only one I've seen in NVDA doing some interpretation.
in reply to Cleverson

@clv1 kind of. For language-specific tweaks: don’t edit a shared IPA key in phonemes.yaml unless you want every language to change.
Instead:
1.
“copy the closest phoneme to a new key (e.g. y_hu / ᴇ) in phonemes.yaml”
2.
“in your packs/lang/<lang>.yaml, add a normalization rule that maps the IPA symbol to your new key”
That keeps the phoneme table centralized, and language packs only decide which key to use.
in reply to Cleverson

for sure strange! Looks like it has to do with Espeak launching and maybe not finding espeak-data in the same path. We try to now find it more explicitly, and also if the error comes up again it should pass any Espeak errors through too. So if it appears again, it'll be more descriptive, LOL. eurpod.com/synths/NVSPPhonemeE… is the link, else the original one is the latest now too anyway.
This entry was edited (4 hours ago)

I listen to someone recommend portfoliocharts.com and portfoliovisualizer.com and wonder if they're going to be accessible to me. I hope so, at least in terms of doing the things that I'd want to do, but they have "charts" and "visualizer" in their names, respectively... So we'll see. A lot of things out there weren't really designed with someone like me in mind. That's just my life. If I'm going to be using a new thing for some reason, then I'll wonder, am I going to run into any accessibility-related trouble with it?

I just discovered (and tried) this wonderful piece of software

github.com/houmain/keymapper

It allows remapping your keyboard in many ways, and it's controlled from a simple configuration file (so, you can prepare one for your disabled friend).

You can, for example, remap the keyboard to only use its right half, if the left hand is dysfunctional (similar to the mirrored keyboard I made, github.com/clackups/qmk_firmwa… ).

Also, it should be useful for #disabledgamers , to map, for example, AWSD to different keys.

#disability #keyboard #accessibility

@Tutanota@mastodon.social Hey, I love what you do and I appreciate it, but please take the flatpak package more seriously. I hope you do this year.

Using an AppImage is not really a universal solution. For example, for those of us on musl distros (Alpine, Chimera Linux, etc.) that package is useless.

I really hope you consider treating flatpak as a first-class package because in musl it is our best and probably only option ​:neofox_laptop_owo:

@Tuta

Aha, how fitting for NV Speech Player. eurpod.com/synths/nvSpeechPlay… is the first version to hit the 10th file milestone for my synthesizers. It's also the first time I'm using the new directory link. This copy fixes memory corruption problems in the frontend, Post-stop aspiration block was made non-brittle now, and the applyRules allocation performance fix. No new versions for awhile until we have tweaked more languages, so I'm done with new files at least until way later in my evening or tomorrow.
This entry was edited (14 hours ago)

People asked for it, and I do think it's a great idea! All of my Speech synthesizers live at eurpod.com/synths - easy to remember URL, and if you want to check it for updates, easy to look at for a version difference. At most, we are only keeping the last 2 versions of a synthesizer, so they will not pile up here. Still uploading some of the larger files, but in the next hour this will all be updated.
The old URLs will work for now, a little bit. As time goes on I will remove them from their old locations and update the blog page to point to this folder too.
This entry was edited (15 hours ago)

Zach Bennoui reshared this.

Jak zní tepelné čerpadlo v -15 ℃


Hlučnost tepelných čerpadel vzduch-voda je předmětem mnoha debat a panuje o něm mnoho mýtů. Když u nás bylo po ránu -15 ℃, využil jsem toho a nahrál jsem si naše tepelné čerpadlo Nibe F2120-8 při teplotě, při které už si opravdu mákne. I při takto nízké teplotě se jedná jen o šum, který už pár metrů od čerpadla nijak výrazně neruší. Tento model podle výrobce dokáže pracovat přes kompresor až do teplot -25 ℃, ale technik říkal, že ho mají vyzkoušené i při -28 ℃. To je na českou zimu dostatečná rezerva.
in reply to Jiří Eischmann

Hehe, ty seš nadšenec, u nás bylo -17℃ a já byl tedy taky koukat, jak to běží, že to nepotřebuje použít ani elektrickou patronu, ale telefon jsem nechal doma a honem pospíchal za ním :-) A upřímně, všímám si, že nejhlučnější je TČ v teplotách okolo nuly, asi jak je "hustší" vzduk plný vody a ten to protlačuje lamelami a i ventilátor běhá na vyšší otáčky. Jakmile je mráz a klesne vlhkost, tak je to paradoxně daleko tišší, protože ventilátor sníží otáčky. Sice se více namáhá kompresor, ale ten je u dnešních TČ tak kvalitně hlukově zaizolován, že není skoro vůbec slyšet a to ani při 17 pod nulou.

We will be doing some performance tweaks in the C++ wrapper next update. I can already see people complaining that there's a slight hit. You want to know why? I made a mistake. Or maybe GPT. Well one of us did anyway. I wrote the base C++ outline for it and then it helped me. But uh, at the moment we are allocating memory for out and copying the entire text string for every single rule, even if the rule doesn't match. If we have 50 replacement rules (common in phonology), we are re-allocating and copying the full text string 50 times per function call. Ouch ouch. I'm fixing this.
in reply to TheFriedChip

@flyingpenguinMwauthzyx @jscholes Unpopular opinion these days, because not everything has to be open source. I don't know anyone who'd contribute to it and I don't see the requirement. Tweesecake also wasn't OSS and people loved it. I like OSS software yes, absolutely, but it's also work to respect kinda. I know that wasn't your intention just saying my thoughts. Of course Quin can and probably has a different reason.

The great thing is, people should not notice changes to existing sounds and tonality. What did change were expansions of rules we can define per language, but to everyone else, this update should not introduce changes in UK and US English, or how the voice sounds. That was not the goal. The goal was to decouple the IPA rule tokenizer into a nice, beautiful frontend.
This entry was edited (15 hours ago)