You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
There is a (very low volume?) mailing list linked to from that site: https://www.livingbraille.eu. That might be a way to get answers to questions if the contacts in the first link don't pan out.
If someone is knowledgeable in a braille code that they would like to see added to MathCAT and is willing to help out, please open an issue with whatever links to specs you know about. We can then discuss plans to make the translation happen in that issue. One particularly important link would be to a site that makes it easy to convert a Unicode character such as "⊆" to the corresponding braille characters. These are often part of a PDF document, but often the dots listed for a character aren't Unicode braille dots, so some translation needs to happen, where the translation has been by trial and error for other codes. Also very useful are sites that have more examples. In order to make sure a translation is working correctly, I need to have LOTS of examples taken from the spec and other trusted sources. About half my time in the previous translations has been writing these tests (MathML and expected braille), so help on that front would definitely be appreciated. The MathML can from from whatever math editing tool someone uses. There probably should be a minimum of 100 tests, but better would be 200 or more tests, especially if the braille code has special cases.
Note: currently MathCAT is targeting one line refreshable braille displays, so expert help on deciding how to translate 2D braille used for matrices and other notations (depends on the braille code) into a linear format will eventually be needed. At some point in the future, refreshable grid displays will get cheap enough that they will start to become common. At that point, I plan to tackle adding on 2D braille support (as a user option). That's probably several years away though.
The text was updated successfully, but these errors were encountered:
A list of braille code links per country is given here. Although some sites have dead links, in general, they seem to be useful links that include links to math braille specs.
There is a (very low volume?) mailing list linked to from that site: https://www.livingbraille.eu. That might be a way to get answers to questions if the contacts in the first link don't pan out.
If someone is knowledgeable in a braille code that they would like to see added to MathCAT and is willing to help out, please open an issue with whatever links to specs you know about. We can then discuss plans to make the translation happen in that issue. One particularly important link would be to a site that makes it easy to convert a Unicode character such as "⊆" to the corresponding braille characters. These are often part of a PDF document, but often the dots listed for a character aren't Unicode braille dots, so some translation needs to happen, where the translation has been by trial and error for other codes. Also very useful are sites that have more examples. In order to make sure a translation is working correctly, I need to have LOTS of examples taken from the spec and other trusted sources. About half my time in the previous translations has been writing these tests (MathML and expected braille), so help on that front would definitely be appreciated. The MathML can from from whatever math editing tool someone uses. There probably should be a minimum of 100 tests, but better would be 200 or more tests, especially if the braille code has special cases.
Note: currently MathCAT is targeting one line refreshable braille displays, so expert help on deciding how to translate 2D braille used for matrices and other notations (depends on the braille code) into a linear format will eventually be needed. At some point in the future, refreshable grid displays will get cheap enough that they will start to become common. At that point, I plan to tackle adding on 2D braille support (as a user option). That's probably several years away though.
The text was updated successfully, but these errors were encountered: