On Thu 21/06/12,08:01, Christian Egli wrote: > Mesar Hameed <mesar.hameed@xxxxxxxxx> writes: > > > The situation is as follows: > > * a person installs liblouis > > * then installs orca > > > > At this point orca picks up the default tables directory. > > > > Lets say a person wishes to test new tables, and therefore modifies > > LOUIS_TABLEPATH > > At this point orca continues to look at the old (default) tables directory, > > not the one defined in LOUIS_TABLEPATH. > > Issue 9 requests for a function to be exposed so that any program that uses > > liblouis can dynamically and automaticaly pick up any changes to > > the tablePath. > > Why would orca (or any other program) need to know where the tables are? > Isn't that liblouis' business? Orca/NVDA/any other program needs to know what tables are available, so that they can be presented in a nice/user friendly combobox for the user to select from. > In other words if a person installs new tables, they modifies the > LOUIS_TABLEPATH and invokes orca using that env variable then liblouis > should automatically find this new table. Is this not so? Same, liblouis will correctly be able to access the new tables, but the user can not select the his/her choise from the orca interface. Thanks, Mesar For a description of the software, to download it and links to project pages go to http://www.abilitiessoft.com