Dave Mielke <[EMAIL PROTECTED]> writes: > [quoted lines by Mario Lang on 2008/11/24 at 20:27 +0100] > >>What I am looking for is a way for 6-dot contracted braille tables to >>override >>the default for invalid characters. > > Checking for a definition of \uFFFD in the contraction table would solve > this.
Oh, I didn't realize it would work right away. Thanks, problem solved :-). >>To come back to your question, I think it only makes sense to >>represent a unknown character as its escape sequence if we actually know >>what character it was, and, while 6dot mode is active, because only >>in 6dot contracted braille mode will the user assume that character width can >>be unequal to cells used. So yes, maybe it would be useful to >>have contracted braille print unknown characters with an escape sequence, > > So as long as the character isn't \uFFFD. Right. >>> What do you think about eliminating the text table as a fallback and >>> insisting that the contraction table define all of its characters? >>I am not sure this is useful, especially since a user might *want* to mix >>different text/contraction tables. Also, if a contraction table >>really only uses 6dot output it does seem to make sense to be able to >>fall back to the characters defined in a text-table that use dot7 or dot8. >>This way, excessive duplication of character definitions can be avoided. > > Yes, but it could also cause confusion, especially if the text table > representation of the character uses only the upper six dots. Thats true of course. -- CYa, ⡍⠁⠗⠊⠕ | Debian Developer <URL:http://debian.org/> .''`. | Get my public key via finger mlang/[EMAIL PROTECTED] : :' : | 1024D/7FC1A0854909BCCDBE6C102DDFFC022A6B113E44 `. `' `- <URL:http://delysid.org/> <URL:http://www.staff.tugraz.at/mlang/> _______________________________________________ This message was sent via the BRLTTY mailing list. To post a message, send an e-mail to: [email protected] For general information, go to: http://mielke.cc/mailman/listinfo/brltty
