Could LaTeX and ASCII Math be speech navigation options?
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 5/5
- Estimated time
- Over a week
- Newbie friendliness
- 45/100
- Issue type
- Feature
- Clarity
- Mostly clear
- Activity status
- Quiet
- Tech stack
- rust
- Domain
- accessibility
Research direction
The issue names no files, tests, or specific entry points. Start by tracing MathCAT's MathML navigation handling and comparing it with the existing LaTeX and ASCII Math paths used for braille and copying; done means those representations can be used as speech navigation options while Orca continues delegating expression navigation to MathCAT.
Written by the indexing model from the issue text.
Description
An Orca user wants to navigate in MathML content rendered in LaTeX and/or ASCII Math.
I realize that I can obtain the LaTeX/ASCII Math from MathCAT. Orca already supports those options for braille and for copying. The reasons why I'm requesting this as a MathCAT navigation option are:
- Orca's MathCAT implementation turns navigation in MathML expressions completely over to MathCAT, treating those expressions as black boxes. Being able to do so fills me with joy. 😄 I don't want to move away from that. But even if I were ok with it:
- Unlike other screen readers, Orca does not have a virtual buffer or any notion of virtual objects. The user is always in the actual document. The user's location is always a valid/real AT-SPI accessible object with a valid character offset. If I need to do this on my end, I'll need to create some sort of virtual object and take navigation over from MathCAT.
So... Any possibility of this happening on your end? (Please and thank you in advance.)
- Dominant language
- Rust
- Stars
- 118
- Forks
- 88
- Avg merge
- 1d 12h
- Merged PRs (30d)
- 49
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 daisy/MathCAT
-
documentation
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
daisy/MathCAT#839 · 1 reaction ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
Maintainers usually reply within 1 day
-
Speak !! as double factorial in MathMLPossibly taken @AdamMagued claimed this 8 days ago. Openbug rules
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
Maintainers usually reply within 1 day
-
discussion
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
Maintainers usually reply within 1 day
-
discussion translation
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
daisy/MathCAT#675 · 1 comment ·
Maintainers usually reply within 1 day
Similar issues
-
feature request good first issue
Difficulty 2/5 1-3 hours Newbie friendliness 85/100
TabularisDB/tabularis#853 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
andrewdavidmackenzie/jonesy#267 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
Maintainers usually reply within 4 days
-
`future_into_py` loses the original panic messagePossibly taken @Danipulok claimed this today. Open
Difficulty 1/5 Under an hour Newbie friendliness 90/100
PyO3/pyo3-async-runtimes#91 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
Maintainers usually reply within 1 day