-
Notifications
You must be signed in to change notification settings - Fork 0
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Invent a translator property or feature for handling undefined characters #57
Comments
Does the dash prefix in I'm a bit hesitant to use a temporary table file to compile the Another question is if we need this generality. NLB already implemented this in their module (pipeline-mod-nlb#6) and Celia/Dedicon could do the same. I think it boils down to the question if there will be a future use for compiling programmatically (or through a temporary table file). If not, let's do it in the agency modules for now. If there is a need, let's fix liblouis. :) |
OK, fine by me. I'm not against keeping things simple. I thought this could be a good way to enable/disable the alert feature (#54). Let's keep it in mind for later then. The dash prefix is just an arbitrary thing, nothing special happens with it. It's not automatically filtered out for non-Liblouis translators or something like that, if that's your question. But it is supported by the CSS parser. |
I meant to ask if the parser supports it. Are you suggesting that alerting the user of unknown characters should be enabled automatically if the CSS property |
No I meant if |
As a start, the liblouis based translator could support a property called
-louis-undefined
which would map to a liblouis "undefined" rule. A table file with a single "undefined" rule would be generated on the fly. The value of-louis-undefined
should be a<braille-character>
. Possibly we can allow additional values such asabort
.Related issues:
The text was updated successfully, but these errors were encountered: