HTML tag, but additionally, if -long_titles is used, seems to become the name of the HTML file containing the titlepage - that file which is then linked to index.html. If the value of this option differs from the name of the master .tex file, and -long_titles is used, then you get that error message "Link failed..." you report. This is a latex2html bug. Don't bother, set -t to the master .tex file name for now. This bug in latex2htrml will be fixed later, but it will take some time. )

Build html manual for Context Help In parallel with compiling your own \CGG{}, we can also translate the manual into an html version for Context Help. The main version of the manual is in latex, so you need a full latex environment, git, and the Latex2html program. Texlive is about 1 GB; Latex2html itself has many requirements: Netpbm, GhostScript, dvips, etc. If some of its requirements are not fulfilled, not only \CGG{} manual cannot be translated, any other latex document will be untranslatable also. Translating \CGG{} manual does not impose any special requirements to latex2html except that it must be at least version 2021.2. The steps are as follows: 1- Download the manual in LaTeX from: git clone "git://git.cinelerra-gg.org/goodguy/cin-manual-latex.git" master 2- Go to the master directory where the latex manual was downloaded and create the pdf manual. Since the glossary and index are also present, we will have to do the pdf build several times. For example you can use the commands: pdflatex CinelerraGG_Manual.tex makeindex CinelerraGG_Manual.idx pdflatex CinelerraGG_Manual.tex makeindex CinelerraGG_Manual.nlo -s nomencl.ist -o CinelerraGG_Manual.nls pdflatex CinelerraGG_Manual.tex You get the manual in pdf complete with index and glossary. 3- To produce HTML output, one has to move (rename) latex2html-init to .latex2html-init (starting with dot). 4- Invoke translate_manual script (needs execution permissions): ./translate_manual The script uses latex2html. It creates the directory CinelerraGG_Manual containing all the files of the manual in html: images, tables, references, index, glossary, etc.. 5- After installation of \CGG{} itself, place the complete unchanged directory CinelerraGG_Manual, as it was produced by latex2html from the manual package, into the 'doc' directory of the installed Cinelerra package. This will be the directory bin/doc/CinelerraGG_Manual if \CGG{} was built --with-single-user. The script ContextManual.pl should appear after installation also here, in bin/doc. It is this perl script that, when compiling \CGG{}, allows the program to access CinelerraGG_Manual to offer Context Help. 6- Optional: we can make some adjustment to the latex2html command line. Some variants are given in the comments inside translate_manual script, some are listed here: -html_version 4.0,math 4.0 is perhaps mandatory. To my feeling, HTML5 is not (yet) implemented in the latex2html translator as complete as HTML4 is. If you remove 'math', then HTML math extension will not be used, and much more small images will have to be generated by the translator for various subscripts, superscripts, simple arithmetics etc. The things should still work but the document will contain many unnecessary images when translated without 'math'. -use_pdftex is a must. However, as this option actually is the default, you can just safely remove it, nothing will change. -use_dvipng / -nouse_dvipng These are equivalent alternatives. The output will look only slightly differently, you can choose best looking one, both will work. -use_dvipng is the default. But for debugging (if generation of images while translation goes wrong for unknown reason), -nouse_dvipng can give more diagnostics. -image_type (gif/png/svg) You can try any option, all should work. But different browsers may support these image formats differently. For example, some do not understand svg, some could have troubles with transparency in PNG, etc. -long_titles 5 With this option, HTML file names will consist of words taken from section names. Without it, all HTML files fill be named 'node.html' where are sequential numbers. Both will work, but in ContextManual.pl you will have to actualize the filenames which contain the actual Contents and Index. -split +3 -link 3 These control segmenting of the whole HTML hierarchy and the depth of generated links to subsections. You can try different, but here, the depth 3 seems optimal. >3 will fractionize the document on too small pieces, <3 on too large ones, so the manual will be inconvenient to read. -split 0 will not segment the document at all and produce one huge HTML file. -nofootnode With this options, footnotes are placed at the bottom of that HTML page in which they appear. Without it, one special HTML file fill be created and all the footnotes collected in this extra file. For CGG manual this would be definitely undesired result. -numbered_footnotes Footnotes can be displayed either with a superscripted number, or as a general link icon without number. The second may be desired in the cases where different HTML pages are intended to be used independently, so that the footnote numbers become out of order. The default depends on the documentclass (for the used in CGG class memoir: numbered). Both should work in Context help equally well. -show_section_numbers The section numbers (same as in PDF) will be prepended to the section names, figure captions, etc. The look of the result will be different, Your preferences may vary. This format of section names will also appear in Contents.html, and for Context Help it was not foreseen. Although Context Help may still work with this form of manual, it can be not as efficient and reliable as without numbers. If we decide later to use the numbers, perhaps ContextManual.pl will have to be adjusted to this format. -bottom_navigation is just a styling for the created HTML pages, to place the Next/Up/Previous links not only on top, but additionally at the bottom of HTML pages. For Context Help it does not matter. -local_icons The icons for the Next/Up/Previous, and some additional links will be copied into the document hierarchy. For a standalone document (as used for Context Help) this is a requirement. For a document on a webserver such icons might be taken from some central place on the server. -t 'CinelerraGG_Manual' This is set into the HTML tag, but additionally, if -long_titles is used, seems to become the name of the HTML file containing the titlepage - that file which is then linked to index.html. If the value of this option differs from the name of the master .tex file, and -long_titles is used, then you get that error message "Link failed..." you report. This is a latex2html bug. Don't bother, set -t to the master .tex file name for now. This bug in latex2htrml will be fixed later, but it will take some time. )