In case anybody needs to configure ASCII Braille support on their Mac for some reason, here's how:
1. Go to Voice Over Utility -> menu -> File -> Export Preferences
2. A save dialog will appear, pick a location on disk somewhere and save the file.
3. Open the file you just saved in any text editor. TextEdit should be good enough.
4. Find the following line:
<key>SCRCUserDefaultsBrailleTableGuideItems</key>
Use your editor's find feature (usually command + f) to do this.
5. Below this line, you should have a line containing <array>, followed by a few lines beginning with <string>, followed by </array>
6. Somewhere inbetween the <array> and </array>, make a new blank line and insert the following text:
<string>com.apple.scrod.braille.table.liblouis.ascii</string>
7. Save the file.
8. In VO Utility, go to Menu -> File -> Import preferences.
9. Pick the file you just edited, agree to replace preferences.
10. Congratulations, ASCII Braille should now be in your Braille table list.
Ærion
in reply to UnifiedPush • • •Even as a non-developer, I found this well written article of great interest. It explained a few things about #UnifiedPush I wasn't aware of, and has given me better insight into how it functions.
It's clear now that there simply isn't any excuse for developers to use #FCM for notifications. I sincerely hope UnifiedPush will gain traction, not only amongst #FOSS developers, but the Android developer community at large.
It's perhaps worth noting that users of #Conversations (and its forks) already have a distributor included in their client, thus further lowering the bar of entry.
@notnotrachit @daniel @snikket_im
reshared this
UnifiedPush and IzzyOnDroid ✅ reshared this.