The interesting thing is that if I launch that binary on barsant.pmx with end-of-lines converted to mac format (Ctr-R) then I get the reported error message. But if I replace with a unix end-of-line format (Ctr-N) file then pmxab completes successfully with a MusiXTeX processable file barsant.tex.

At the end of the first pmx pass I get a warning

 WARNING:
 Last non-blank character is "¿", not "/,%"
 ASCII code: 191

But that doesn't (apparently) influence the resulting tex file. I don't get that warning if I add an extra trailing newline to barsant.pmx.

I see exactly the same

Now, when I open barsant.pmx with macintosh Ctr-R newlines in a simple text editor (like 'pico' coming with the mail reader 'pine') then that editor doesn't recognize any newlines! GNU emacs does know about Ctr-R newlines, though. My conlusion (for now) is that Mac OSX pmx source files _must_ have unix style end-of-lines. OSX, as operated from a shell prompt, behaves like unix, and to my best knowledge _is_ basically unix.

That's it. I've many unix stuff on my mac (OSX) and I never cared about line ends. I'm pretty sure that most of the text/source-code files I've been using/compiling have got unix line ends. Moving stuff forth and back between Linux/OSX/SunOS never lead to any probllems. However, I don't use much good-old-mac programs, especially no editors. There, things might be different.

bernhard

_______________________________________________
TeX-music mailing list
[email protected]
http://icking-music-archive.org/mailman/listinfo/tex-music

Reply via email to