[liblouis-liblouisxml] Re: Handling of undefined characters when translating
- From: "John J. Boyer" <john.boyer@xxxxxxxxxxxxxxxxx>
- To: liblouis-liblouisxml@xxxxxxxxxxxxx
- Date: Thu, 29 Jul 2010 14:06:49 -0500
It wouldn't be difficult to introduce a new opcode, something like
"undefined", which would specify the dot pattern to be used if an
undefined character was encountered. If this opcode were not present in
a table the character would be displayed in the present hex form. Is
there a demand for this?
John
On Fri, Jul 30, 2010 at 04:19:20AM +1000, James Teh wrote:
> Hi all,
>
> Following on from the topic of buffer sizes, I'm wondering whether the
> current handling of undefined characters is actually ideal for the user.
> I understand that the hex code is printed so that the user has some idea
> of what the character was, but this seems like something that isn't
> actually that useful or friendly to a user. If something can't be
> displayed on screen, usually a question mark or some other symbol is
> printed, but not a hex code. I think it might perhaps be nicer to do
> this for braille as well. A table developer can investigate a broken
> character, but this isn't useful for a user. This also mitigates the
> buffer size issue somewhat.
>
> If this was done, it might be useful for a table to be able to specify a
> character to output for undefined characters.
>
> Thoughts?
>
> Jamie
>
> --
> James Teh
> Vice President
> NV Access Inc, ABN 61773362390
> Email: jamie@xxxxxxxxxxxx
> Web site: http://www.nvaccess.org/
> For a description of the software and to download it go to
> http://www.jjb-software.com
--
John J. Boyer; President, Chief Software Developer
Abilitiessoft, Inc.
http://www.abilitiessoft.com
Madison, Wisconsin USA
Developing software for people with disabilities
For a description of the software and to download it go to
http://www.jjb-software.com
Other related posts:
