Looks like the best thing will be to use either latex or markdown, and include both the latex/markdown source and an HTML compiled version of the doc in the git repo. The doc will doubtless contain images of patch fragments, taken from the help files, in a way similar to my book (http://msp.ucsd.edu/techniques.htm).
cheers M for the images. (Unless it's feasible to unify that with the help On Tue, Jul 02, 2019 at 07:11:35AM +0000, Lucas Cordiviola wrote: > > On 7/1/2019 5:46 AM, IOhannes m zmoelnig wrote: > > i*strongly* suggest to > > - have **all** the sources (for*anything* generated, including images) > > in the git-repository > > - allow to build all artifacts automatically?? (via the build-system) > > I fail to see anything we can do to auto-generate single image files > from 1 or more LaTex file/s. This should be carefully and manually > handled by the author or the maintainer. There could be one master LaTex > file containing the code for each image if the source is to be stored: > > '' > figure 0.1.0 > $saras \$whatever ... > figure 0.1.1 > $ssgdsdg \$whatever ... > '' > > Since this is not automatic Miller should probably be in favor (and I > understand) of just writing everything on LaTex files instead of html. > Since I don't know how many "math formulas" are needed I don't know what > to say. > > > > :) > > > Mensaje telepatico asistido por maquinas. > > _______________________________________________ > Pd-dev mailing list > [email protected] > https://lists.puredata.info/listinfo/pd-dev _______________________________________________ Pd-dev mailing list [email protected] https://lists.puredata.info/listinfo/pd-dev
