The team released a new version of texdoc-online, version 0.4.0. It features improved handling of overwriting defaults and allows for bundling fonts and scripts to help protecting your privacy. See the CHANGELOG for a full list of release notes.
I like that you a) choose debian and b) texlive-full. With that, you're image is not far away from mine at https://github.com/dante-ev/docker-texlive/blob/188b8be4aad340b79fdf43ef3819b62f332d60fb/Dockerfile#L37. I wonder whether I should create pull requests based on my image? - Should we discuss each addition one-by-one? E.g., pkcheck could be a good addition, but support for pax (which requries Java) is not good b/c of size of the image
6 replies
We could discuss some points in here. :)
In short, I am maintaining https://github.com/latextemplates/. Main template: https://github.com/latextemplates/scientific-thesis-template, with issue latextemplates/scientific-thesis-template#25 still unresolved :)
5 replies
I am also working on a template-generator https://github.com/latextemplates/generator-latex-template. The difference to https://gitlab.com/islandoftex/texplate seems to be that I a) provide a choice for each "minor" thing to include/exclude and b) try to offer a form
.preamble, .example for each package (hyperref, csquotes, ...). See https://github.com/latextemplates/generator-latex-template/tree/lncs/generators/app/templates for the current lists of contents
Still have to finish the first "real" template generation. I am close in the context of LNCS.
Let's see, what our discussion reveals.
I am still struggling with lualatex vs. pdflatex. On the one hand, I want to provide the users to give the freedom of choice at each compilation, on the other hand, I want to have clean
.tex files. - For the choice, I need much \ifluatex in the .tex files, which clutters them very much.
On a more serious note, we want to have a series of abstract layers that can talk to each other.