>|>... I wouldn't think that Windows users would
>|>have any interest in constructing mtxdoc.pdf from scratch.
>|
>|I've been responsible for creating extensive revisions of musixdoc,
>|which is
>|a more complex document than mtxdoc, and I did all the work in
>|Windows. So I
>|have more tha
Bob Tennent wrote
>... I wouldn't think that Windows users would
>have any interest in constructing mtxdoc.pdf from scratch.
I've been responsible for creating extensive revisions of musixdoc, which is
a more complex document than mtxdoc, and I did all the work in Windows. So I
have more than a
DIETER glötzel wrote
What does the "{10}" actually mean?
There are two ways to refer to pitches in MusiXTeX: letters or numbers. When
you use a number, it represents the number of \internote up from the bottom
line of the staff, so for ANY 5-line staff, 0 is the bottom line and 8 is
the top
On Tue, May 03, 2011 at 12:39:44PM +0200, Bob Tennent wrote:
>
> Dirk: Shouldn't you be following your own advice? Re-write the Makefile
> in Lua (and only use tools available on every platform)!
>
It's on my TODO list, but not at this moment very high up.
Dirk
---
>|(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
>|
>|"f
On Tue, May 03, 2011 at 02:15:39AM +0200, Don Simons wrote:
> They start with what happens when I try to compile mtxdoc according to Dirk's
> instructions. I didn't think makefiles had a place in the Windows command
> window, but to my surprise, when I unzipped mtxD060.zip and blindly typed
>
> ma
Don Simons wrote:
> 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.
Quick translation of the Makefile (I haven't tested it)
> make dvitarget
The effect of this statement is to cau
Don Simons wrote:
> I'm glad that the Linux-Unix-Debian-pdftex contingent can now sleep
> soundly. I also see exactly how the new PMX etex-demanding commands got
> into the mix (when the embedded examples were compiled with mtx/pmx).
>
> But there are still a few mysteries I'd like to pursue, for
(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.
9 matches
Mail list logo
