> From: "Simons, Don" <[EMAIL PROTECTED]>
> Date: Fri, 4 Feb 2000 15:09:51 -0800
> [...] In addition or perhaps as an alternative you might replace
> all \xbar commands by \zbar (\\let\xbar\zbar\let\alaligne\zalaligne\); I'm
> not sure what that would do to horizontal spacing. [...]
In rare cases replacing \xbar by \zbar may result in additional line breaks.
Concerning horizontal spacing at least \afterruleskip should be set to
0 or revoked. So my solution would be:
2 2 4 4 4 4 0 0
1 2 20 0.1
barlines
without
aa
./
\\let\xbarsav\xbar\
\\let\alalignesav\alaligne\
\\let\endpiecesav\endpiece\
\\def\xbar{\setemptybar\addspace{-\beforeruleskip}\xbarsav\addspace{-\afterruleskip}}\
\\def\alaligne{\addspace{-\beforeruleskip}\setemptybar\alalignesav}\
\\def\endpiece{\addspace{-\beforeruleskip}\setemptybar\endpiecesav}\
\\nostartrule\
\\nobarnumbers\
MR1 e44 e e e e e e e e e e e e e e e e e e e e e e e e e e e M Rb /
MP1 /
It's the usual trick knowing which MusiXTeX macros PMX uses and replacing
them by modified macros. That's the reason why a user should learn a little
bit about MusiXTeX after starting with PMX. Looking at the PMX generated
MusiXTeX-sources may be a good teacher for MusiXTeX :-)
Since I use PMX more and more I stopped using MusiXTeX directly. Instead
I use my MusiXTeX knowledge with the various in-line TeX features of PMX.
-- Werner
PS: If you lateron want to combine many PMX-generated TeX sources you should
define some \Resetall for all those macros you clobbered MusiXTeX.
In the example above it could be something like:
\\def\Resetall{\let\xbar\xbarsav\let\alaligne\alalignesav\let\endpiece\endpiecesav}\
\\def\endpiece{...<as above>...\Resetall}\
The more such definition you collect the more you should store them in
a seperate file outside PMX (without double-\ at beginning an \ at the end)
and call this file within PMX as e.g. "\\input mypmx \"
