On Wed, 2011-06-22 at 15:30 +0200, Cornelius C. Noack wrote:
> (cut)
>
> This is even more so, as the solution of the problm is to make use
> of the appropriate PMX method for that: tweaking the position/length
> of D< (and, in fact, all other cases of the D command!) accordingly;
> in your case, the following will do the job; instead of
> D< g83 d+ g- g+ D< g4 r /
> write
> g84 D<+0-5 d+ g- g+ D<+0+1 g4 r /
>
> ( Adjust the shift parameters to suit your own taste).
Yes.
My error on Monday was a simple accident. But Grieg obviously put a
lot of care into the manuscript, and I shall try to duplicate the
appearance, even if there is no great difference in meaning between a
hairpin starting at the bar line compared to a hairpin starting at the
first beat of the measure.
>
> Thanks for your citing the remark on this in my tutorial!
> In light of your 'problem', I guess it would make sense to point
> out the remedy in the Note I wrote on this -- I will add that in
> my next update (coming soon for another, more serious reason ...) .
Before starting to work in musixtex on this work, I did look at pmx; I
even made some notes about why I was choosing musixtex. For what it's
worth, here are the thoughts of a newbie to pmx.
(*) The first time I looked at your tutorial, I had a broken printer.
I have since replaced my printer and printed a hard copy of the
tutorial. Being able to mark pages makes a lot of difference.
(*) The long list of positional numeric parameters at the start of the
input reminded me of primitive programming languages in which I
did some of my early programming. The memories are not pleasant,
and I noted "this is too terse for me!" In actual use, those
numbers just sit in the source file and rarely need attention.
The coding of the central part of the score, while terse, is
sufficiently mnemonic that I can remember the codes for the
duration of a working session, and even between sessions. There
are some codes that I find (so far) less memorable than musixtex,
but I greatly appreciate relief from trying to remember where the
opposite of u-for-up is l-for-lower and where it is d-for-down.
(*) My favourite mistake so far is to type a backslash where a forward
slash is required. Why, oh why, can I not see what is right in
front of me? I hereby state my resolution to add a step to my
makefile to check the source for backslashes. The first time I
have to write inline TeX, more intelligence will be required. (I
am deliberately not specifying whether I am talking about more
intelligence in the makefile or more intelligence in me. <grin />)
(*) A couple of features of the syntax of the language bother me by
limiting my freedom to indent the code. I would like to be able
to let comments, even the leading "%", recede to the right
according to their (lack of) importance. I would like to let the
slashes marking change of stave or change of voice hang out at the
left without using up a whole line on the screen. Of course, as I
use pmx more, the way it is will come to seem more and more right.
Thank you for letting me ramble on.
Terry.
-------------------------------
[email protected] mailing list
If you want to unsubscribe or look at the archives, go to
http://tug.org/mailman/listinfo/tex-music
