Le 16 nov. 2010 à 07:48, Dirk Laurie a écrit :
I think the choice is obvious. Don't you?
Wanna be part of it! Lately I've been fighting with the question: “Should I try
Lilypond?” but your idea is much more interesting.
Don't know anything about Lua though.
PS If you would like to try
Thanks Dirk to draw our attention to this new development. Such a major
change--and it would be a major change--would perhaps also give opportunity to
think about how to overcome some limitations to MusixTeX and friends which are
due to its design. Quite some inline TeX coding could probably
|I have on two occasions asked on this list whether anybody wants to
|help me convert M-Tx to Python. Christian Mondrup convinced me that
|we shouldn't, as outside the Unix world people don't already have Python
|anyway.
That may have been the case when you asked but it isn't now: Python is
Hello friends.
Could anyone tell me what is going on? I use MusixTex but, I guess, in a
very simple way, actually, I use MusixTex inside Latex. I don't know nothing
about PMX or LuaTex etc; never heard about it. Could anyone tell me if
something good or bad is coming?
Regards,
Filipe
2010/11/16
Bernhard Lang wrote
...
Sometimes the limitation to 12 voices gets in the way
Not for long! Even now there are prototypes available on Hiroaki's site of
MusiXTeX 1.15 and PMX 2.60 which together allow up to 24 voices (and 1.15
will allow many more). Very soon these will be activated in WIMA.
I’ve failed as an advertiser. PMX is a preprocessor for musixtex which you
should definitely avoid if you prefer
1. typing input files that are 3 times longer than they have to be
2. calculating and adjusting all the horizontal spacings of all notes based on
their durations and relationships
6 matches
Mail list logo
