The intention is to base all formats except textDevice and browser on UTDML. This is because in the case of volumes, for example, utd provides a first pass over the material, which is then intended to be used in determining volume size, etc. In all formats except textDevice and browser utd provides the basis for including images and different cell sizes. Do not change this code. It would result in a major rewrite. If utd is working for a given document the problem is in the conversion modules, such as utd2volumes or utd2brf . John On Wed, May 28, 2014 at 06:08:23PM +0100, Michael Whapples wrote: > Hello, > I have been working to correct the back translation from the java > bindings of liblouisutdml. This has revealed a related bug, which > probably will affect C applications using back translation in > liblouisutdml. > > Basically the specific bug is that if one uses a value other than > textDevice, browser or utd for the setting formatFor in the > configuration file (IE. in my testing I used the value brf), then > back translation fails, liblouisutdml seems to use the function > utd_back_translate_braille_string. > > I have tracked the cause of this bug down to the following lines. In > the file readconfig.c in function read_configuration_file at line > 1424 we have: > if (ud->format_for > utd || (ud->mode & louisDots)) > > Inside the block relating to that if statement we get: > ud-format_for = utd; > > Can someone explain why this code is being used and what it is meant > to be achieving? > > Michael Whapples > 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