Hi Christian, Thanks for the explanation. I was not told this at the beginning, so I assumed that the environment variable just added additional places to look. This can be changed. However, since it seems to be agreed that the lou_getTablePaths functgion is not what is wanted, this should be eliminated first. Since some commits have been made since it was added, I don't think that a simple revert should be done. What do you suggest? John On Thu, Jun 21, 2012 at 03:11:18PM +0200, Christian Egli wrote: > "John J. Boyer" <john.boyer@xxxxxxxxxxxxxxxxx> writes: > > > I always thought that if the user defines some special paths using > > LOUIS_TABLEPATH he might still want to access other tables in the > > current directory or in the tables subdirectory. What is the reason for > > stopping the search with LOUIS_TABLEPATH ? > > If I override a table locally and I have an error in it I will never > know, because liblouis silently keeps looking for a correct table, i.e. > a table that it can load. So in the end it will take the global one > without me noticing. If I explicitly put the global one on the path then > I consent to looking further. Otherwise I just want the local one and no > other. > > Thanks > Christian > > -- > Christian Egli > Swiss Library for the Blind, Visually Impaired and Print Disabled > Grubenstrasse 12, CH-8045 Zürich, Switzerland > > ----- > Tag der offenen Tuer > Die SBS laedt Sie herzlich ein: 30. Juni 2012 von 9 bis 16 Uhr. > Mehr Informationen erhalten Sie unter www.sbs.ch/offenetuer -- 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