Linux: Braille View shows ASCII because APH_Braille_Font .otf files aren't installed
Maintainers usually reply within 1 day
@mnstewart232 is already working on this.
Since Oct 22, 2026.
Assessment
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Newbie friendliness
- 78/100
Research direction
Inspect the Linux font installation step and the font files in lib/app/programData/fonts/. Start by finding where the installer copies the uniBraille .ttf files and check how that step handles .otf files. Done means the APH_Braille_Font files are installed and the Braille View displays simulated braille on Linux.
Written by the indexing model from the issue text.
Description
Environment
- BrailleBlaster 3.2.5, installed at ~/.local/opt/brailleblaster-3.2.5
- Linux under WSL2 ([distro and version])
Problem
With View > View Braille checked (simBraille=true in user_settings.properties), the Braille View shows ASCII braille instead of simulated braille. Braille Preview with the Unicode toggle displays correctly. Restarting, resetting settings, and forcing X11 (GDK_BACKEND=x11) did not help.
Cause
Running with FC_DEBUG=1 shows the Braille View requests the font family APH_Braille_Font-6s. Only the uniBraille fonts were installed to the user font directory:
~/.local/share/fonts/brailleblaster/unibraille29.ttf
~/.local/share/fonts/brailleblaster/unibraille36.ttf
~/.local/share/fonts/brailleblaster/unibraille43.ttf
The APH_Braille_Font-*.otf files in lib/app/programData/fonts/ were not installed, so fontconfig falls back to DejaVu Sans and the Braille View shows plain ASCII.
Workaround
cp ~/.local/opt/brailleblaster-3.2.5/lib/app/programData/fonts/APH_Braille_Font-*.otf ~/.local/share/fonts/brailleblaster/
fc-cache -f
After restarting BrailleBlaster, the Braille View displays simulated braille correctly.
Suggested fix
The Linux font installation step appears to copy only .ttf files. Including the .otf files from programData/fonts/ should fix this.
- Dominant language
- Kotlin
- Stars
- 15
- Forks
- 11
- Avg merge
- 14h 34m
- Merged PRs (30d)
- 29
Getting set up
This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from aphtech/brailleblaster
-
Difficulty 1/5 Under an hour Newbie friendliness 88/100
aphtech/brailleblaster#163 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
aphtech/brailleblaster#152 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
aphtech/brailleblaster#151 · 1 comment ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
aphtech/brailleblaster#149 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
aphtech/brailleblaster#145 ·
Maintainers usually reply within 1 day
All issues in aphtech/brailleblaster
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
SimonHalvdansson/Harmonic-HN#399 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
-
[Request] 李跳跳Openrequest-adaption
Difficulty 2/5 Under an hour Newbie friendliness 78/100
BetterAndroid/android-notification-icon-project#799 ·
Maintainers usually reply within 1 day
-
6.4.0快进问题Open
Difficulty 2/5 1-3 hours Newbie friendliness 62/100
open-ani/animeko#3664 · 4 comments ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 75/100