>|(Lack of) progress report:
>|
>|1. In a Windows command window, I've succeeded in creating *.tex for
>|all of
>|the *.mtx, using only commands starting with
>|
>|"for %a in (*."
>|
>|In the process I figured out how to pass only the basenames of all
>|*.pmx to
>|musixflx with
>|
>|"for %a in (*.pmx) do musixflx %~na"
>|
>|2. I've succeeded in creating *.ps for all those tex files, again using
>|"for" commands. But evidently my TeX system lacks the control sequence
>|\textit.
>|
>|3. I got the latex compilation started. During that I had to let MiKTeX
>|install a bunch of packages it was missing. Then it even seemed to process
>|some of the inserted tex files after I included \usepackage{etex} as
>|suggested. But it choked on "\input netsoos1.tex". Looking in the makefile
>|it appears that this and various other *.tex are created on the fly by
>|merging various *.mta and *.mtb files.
>|
>|At that point it transitioned from adventure to slog, and I threw in the
>|towel, leaving the keys to this forbidden kingdom to the Unix gurus
>|for the
>|time being.
Don: Why are you doing this? I wouldn't think that Windows users would
have any interest in constructing mtxdoc.pdf from scratch. And if this
is considered important for some reason, a batch file isn't the right
way to do it.
Dirk: Shouldn't you be following your own advice? Re-write the Makefile
in Lua (and only use tools available on every platform)!
Bob T.
-------------------------------
[email protected] mailing list
If you want to unsubscribe or look at the archives, go to
http://tug.org/mailman/listinfo/tex-music
