Mesar, It sounds like a fantastic idea if it can be made to work without a lot of headaches. The more we can develop self-sustaining features like this, the less manual work has to go into keeping the tables up to date. Best regards from Ohio, U.S.A., Vic E-mail: vic.beckley3@xxxxxxxxx -----Original Message----- From: liblouis-liblouisxml-bounce@xxxxxxxxxxxxx [mailto:liblouis-liblouisxml-bounce@xxxxxxxxxxxxx] On Behalf Of Mesar Hameed Sent: Tuesday, July 24, 2012 1:25 AM To: liblouis-liblouisxml@xxxxxxxxxxxxx Subject: [liblouis-liblouisxml] Re: Grouping tables according to language and Braille code 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 For a description of the software, to download it and links to project pages go to http://www.abilitiessoft.com