Actually, I didn't give all the information. Logging messages are set to print in liblouisutdmjl.log by the initialize method in the Java bindings. It is unnecessary to set any other log file name. In fact, doing so will interfere with CheckLiblouisutdmlLog I'll look at Subcommands.java In DocumentManager.java The statement String logFile... should be removed. When translateFile is called logFile should be changed to null. Then a call to displayLog should immediately follow. Progress on tika looks really good. John On Fri, Jul 20, 2012 at 08:31:29AM -0400, Fran�ois Ouellette wrote: > OK. Thanks. > > François > > On Fri, Jul 20, 2012 at 5:34 AM, John J. Boyer > <john.boyer@xxxxxxxxxxxxxxxxx> wrote: > > liblouisutdml operations may or may not create a log file, depending on > > if there is anything to log. I have modified the CheckLiblouisLog class > > to simply return if the file is not found. The subcommands already call > > the showLog method in this class. The GUI should call displayLog after > > translateFile and other calls to methods in the Java bindings. I could > > make this change, but since Francois is working on DocumentManager.java > > I don'[t want to deal with two people changing the same file > > simultaneously, although mercurial can deal with this. > > > > As a reminder, it is better to make small commits and pushes rather than > > wait until a large number of changes have accumulated. > > > > John > > > > -- > > John J. Boyer; President, Chief Software Developer > > Abilitiessoft, Inc. > > http://www.abilitiessoft.com > > Madison, Wisconsin USA > > Developing software for people with disabilities > > > > -- John J. Boyer; President, Chief Software Developer Abilitiessoft, Inc. http://www.abilitiessoft.com Madison, Wisconsin USA Developing software for people with disabilities