[liblouis-liblouisxml] Re: Grouping tables according to language and Braille code
- From: "John J. Boyer" <john.boyer@xxxxxxxxxxxxxxxxx>
- To: liblouis-liblouisxml@xxxxxxxxxxxxx
- Date: Tue, 24 Jul 2012 15:42:32 -0500
Hi Mesar,
This is a good start. For BrailleBlaster it would be nice to have an
explicit statement of the language and the braille code. For example,
table en-us-g2.ctb, English-us, Grade 2
This list could be quite lengthy. The lou_listTables function would need
two parameters, a pointer to an area where the list should be stored and
the length of the area.
What is the license for gettext? LGPL is fine, but not GPL. Can gettext
be included in the liblouis build, like gnulib? It would be best to
avoid having to download a dependency. It would be compiled into
liblouis. After all, the library is cross-platform.
John
On Tue, Jul 24, 2012 at 06:25:20AM +0100, Mesar Hameed wrote:
> Hi John,
>
> What do you think about the following alteration:
>
> 1. we add new opcodes, tableName and tableInfo
> tableName en-gb-g2 # probably the same as the actual filename of the table.
> tableInfo English UK grade 2
> These should be defined as the first non-comment lines of any table, so that
> they dont get overridden.
>
> 2. A new function is added to liblouis: listTables(localizationLang)
> The function iterates over the defined table paths, extracting the
> information and builds up a list of pares.
> tableName, localizedTableInfo
>
> The localizedTableInfo is obtained using a call to gettext, which if no
> localization was found for the given string simply returns the english
> default.
>
> If I am not too mistaken, this should address the requirements for Blaster,
> NVDA and Orca.
> The particular package can restrict the data as it wishes depending on
> comboboxes etc.
>
> This solution also has the advantage that minimal maintenence is required.
>
> Thoughts?
>
> -- Mesar
> On Mon 23/07/12,13:53, John J. Boyer wrote:
> > For BrailleBlaster we are planing to give users a choice first of
> > supported languages and then of the Braille codes for each language.
> > Something like this has already been discussed on this list. Perhaps
> > there could be a file in the tables directory with two columns, the
> > first for a human-readable table name and the second for the actual name
> > of the table file. This file could be divided into sectgions acording to
> > language. Of course this would also be useful for NVDA and Orca. The big
> > question is who is going to maintain it.
> >
> > John
> >
> > --
> > 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, to download it and links to
> > project pages go to http://www.abilitiessoft.com
> For a description of the software, to download it and links to
> project pages go to http://www.abilitiessoft.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, to download it and links to
project pages go to http://www.abilitiessoft.com
Other related posts:
