Christian, I'm just learning about svn and texinfo, but I would say go ahead and commit. For my information, what is the advantage of using a patch. I understand that you can just edit files and then commit the changed versions. I will soon have documentation on lou_debug and on a number of new functions added to compileTranslationTable.c for use by the debugger and other tools. I'm thinking of submitting the draft of the documentation to the list in plain text, then putting it in texinfo format. Is this a good approach? Thanks, John On Mon, Dec 22, 2008 at 12:29:14PM +0100, Christian Egli wrote: > Hi all > > I have a patch against liblouis-guide.texi that generates somewhat nicer > links on the html output (the files are now named begnum-opcode.html > instead of begnum_002dopcode.html) and has a bit more explanation around > an example about the syllable opcode where I had a question recently > (//www.freelists.org/post/liblouis-liblouisxml/automake-errors-with-texinfo-patch,1) > > The patch is attached below. Is it ok to commit? > > Thanks > Christian > -- > Christian Egli > Swiss Library for the Blind and Visually Impaired > Grubenstrasse 12, CH-8045 Zürich, Switzerland -- My websites: http://www.godtouches.org http://www.jjb-software.com Location: Madison, WI, USA For a description of the software and to download it go to http://www.jjb-software.com