Re: Several .tex files from https://ctan.org/pkg/olsak-misc are incorrectly in DOC instead of RUN
Petr Olsak <[email protected]> Thu, 9 Jul 2026 11:25:57 +0200
| Newsgroups | gmane.comp.tex.live |
|---|---|
| Message-ID | <[email protected]> |
Hello Karl, the problem is that the files from olsak-misc have very various uses. Some of them can be used directly in a plain TeX document by \input (or in OpTeX document) and they work in LaTeX too if somebody writes \input file in a LaTeX document. They are booklet.tex, cropmarks.tex, qrcode.tex, circu.tex, scanbase.tex, scancsv.tex (1). It should be more comfortable if they were installed in the TeX input area by default. The other files from olsak-misc: cnv*.tex, eparam.tex, fun-cofee.tex, openclose.tex, seplist.tex and xmlparser.tex include an experimental macro code or a code for fun. I assume that a macro programmer can be inspired by them. They are not intended to direct use. So it is okay that they are in doc/ subdirectory. IMHO there is no name conflict with the six files mentioned above (1) . They have .tex extension but LaTeX uses .sty extension for its style files: booklet.sty, qrcode.sty exist. The only reason why these six files shouldn't be in the TeX area is the fact that somebody will write better qrcode.tex, cropmarks.tex etc. Best Regards Petr Olsak On 7/8/26 23:30, Karl Berry wrote: > Hi quark67 (and Petr), > > I can't find file `circu'. > > Yes, thanks for the report. I know. I can't install additional files > with such "generic" names. Some of the files in olsak-misc are > grandfathered in (booklet.tex, qrcode.tex, scancsv.tex, etc.) since they > have been in the runtime for many years. But newer files (circu.tex, > cnv.tex, openclose.tex, etc.), whose names have no relationship to the > package name, and which have never been in the TL runtime, just can't be > moved to the runtime now. I can't set that precedent. > > I seem to recall Petr and I discussing this some years ago and he didn't > want to rename the files, which is certainly understandable. In which > case, the only recourse is for users to copy them out of the doc > directory into their own directory/ies. --best, karl.