On Sun, Sep 20, 2026 at 11:00:45AM +0200, Patrice Dumas wrote: > Hello, > > After cleaning up, there are three HTML customization files that remain > in tta/per/init, that are installed in a location such that they can be > used simply by adding --init=<this_default_installed_file>.pm > > I am wondering if we should document them? My feeling is that we > should, making clear that they should be available as long as the needed > interfaces are there in texi2any and as long as we have time to maintain > them and we will miss bugs if they are not actually used. > > these are > * book.pm: a style that makes the output somewhat more similar to a book > * breadcrumb_navigation.pm: a new file that replaces Up by link to > parents and was discussed/implemented recently > * chm.pm: setup the files needed by chmcmd to create a .chm file
I don't have a strong opinion on it. You know the potential difficulties of maintaining the customisation API. Maybe the files could be listed in texi2any_api.texi as example files? "(texi2any_api)Loading Init Files" seems to be the place where the directories that init files can be found are listed. texinfo.texi doesn't go into that much detail. It could make sense to add a note there that one of those directories contains these files. A feature implemented in an init file, as are the three above, is second-class. We should be careful to avoid going so far as to say, for example, "texi2any supports CHM output".
