On Mon, 3 Mar 2008, Simon Dreher wrote:
> >
> Because Thomas Esser (the former tetex maintainer) stopped his support
> in favour of texlive?
I had not heard that. As far I read his email, he stopped support of
TeX packages which are on ctan anyhow, but promised to continue to support
the tetex
On Mon, 28 Jan 2008, Don Simons wrote:
>
> I have published one vocal piece, and I used M-Tx for it. I spent a great
> deal of time resolving issues exactly like the ones you mention. And it got
> even worse when I went to make parts. I think changing the number of voices
> in the score is doable
On Mon, 28 Jan 2008, Carlo Centemeri wrote:
>
> %%K+0-2
> m d4 Dp d cs d |
>
> To which I should add the LxMy command for the new "paragraph". But if
> I add it together withe the previous ones, the mtx file is compiled
> correctly, while the pmx one gives an error (I have and Rd appearing
>
On Fri, 3 Aug 2007, Don Simons wrote:
>
> t
> .\
> Abepl
> g04 t | g t t+.5+.5 | g t+.5-.5 t | g t t /
> g04 t t | g t t+1+1 | g t+1-1 t | g t t /
> g04 t t | g t t | g t t+2+2 | g t+2-2 t /
> g04 t t | g t t | g t t | g t t /
> g04 t t | g t t | g t t | g t /
> ==
On Thu, 2 Aug 2007, Christian Mondrup wrote:
>
> Well, pmxab doesn't accept that with ties:
>
> ERROR in line 295, bar 16 "+|-" for slur height only allowed in "s"-slurs
> v
> But it works excellently with slurs
>
> d45 c8 b a2 g4 b a a s s+
On Mon, 9 Jul 2007, Jean-Pierre Coulon wrote:
> Daniel Taupin's last versions of the MusiXTeX documentation discouraged
> making
> large scores under LaTeX, because of the lack of 'registers' - Don's version
> is in a milder tone. Yet I managed to make a large score under LaTeX with
> the
>
On Mon, 12 Mar 2007, Cornelius C. Noack wrote:
> >
> > Thing are OK I send the PostScript to a PostScript printer, but when I
> > view the score with Acrobat Reader, the printing stops at the first blank
> > page, and Acrobat Reader reports a printing error.
> >
I had also problems with the Acroba
On Mon, 26 Feb 2007, Mats Bengtsson wrote:
>
> Sorry to answer about LilyPond on this mailing list. As long as you use
> LaTeX to write your documents, you can certainly insert both large and small
> music examples using lilypond-book, which is included in the LilyPond
> distribution. Lilypond-bo
On Fri, 19 Jan 2007, Jean-Pierre Coulon wrote:
>
> \begin{document}
> \pagecolor{colorfond}
> \Huge Blablabla
> \end{document}
>
> but how can I "translate" this in plain TeX, for use with MusiXTeX?
>
This problem has been discussed already quite extensively,
as a google search "color plain tex
On Mon, 10 Jul 2006, Jean-Pierre Coulon wrote:
>
> When a person familiar with Word, Powerpoint, or Finale, or other WYSIthingy
> stuff sees me making corrections in a MusiXTeX file after he pointed out
> errors in my score, his face becomes green :-)
>
> Has anybody a similar experience? I doub
On Mon, 10 Jul 2006, Jean-Pierre Coulon wrote:
> Does anybody know when Hans Kuykens's warning at the beginning of the MusiXTeX
> manual was written? (... awesome job which gobbles ...)
>
> Of course the "disk space" part is now obsolete, but I'm just curious. Has
> anybody an old, old MusiXTeX m
Dear all:
in my opinion, musixtex and the preprocessors are
mature and stable software. While there will be maintenance
releases in the future, it is unlikely that major changes
will take place. On the other hand, installation and documentation
are outdated and an obstacle to the propagation of th
On Tue, 4 Apr 2006, Don Simons wrote:
> Sonja--
>
> If you are using PMX, then at all costs, you should avoid doing anything
> that requires you to edit the TeX file directly. The reason is that every
> time you want to change or edit ANYTHING in the PMX, you'll then have to
> re-edit the TeX fil
On Fri, 24 Feb 2006, Andre Van Ryckeghem wrote:
>
> - use the pmx commands for the page hight en width:
> 'w280m h205m'
> \voffset=-08mm\hoffset=-5mm\
>
> - change interstaff
> \\\interstaff{14}\
>
> - change the margins
> \\\def\atnextline{\stafftopmarg4\Interligne}\
>
It may be further neces
On Tue, 24 Jan 2006, Robin Fairbairns wrote:
>
> no: we don't make recommendations like that. the change came from the
> tds group, who're as near to a standards body as tex systems get.
>
TeX is indeed quite standardized. At home, my computer has windows
and linux partitions. Nevertheless, I h
Dear Christian:
The HOWTO is correct, thank you. The installation of
type1 fonts has changed somewhat, but I do not know
whether we need a correction: in the README of the
type1 fonts is recommended to put the map files to the
directory $TEXMFMAIN/dvips/config/. In my present distribution,
SuSE 10.
On Wed, 21 Dec 2005, Don Simons wrote:
>
> On a harpsichord, which is definitely a keyboard instrument, it would also
> be possible to play two different but equal-pitched notes, one with each
> hand on a different keyboard. However, in the rare cases where this is
> intended, it is practically al
On Wed, 23 Nov 2005, Anna Choma wrote:
>
> I've tried to switch off the numbers and remove pageno from theese
> definitions (I've put them to the score of course). Without success.
> Sorry for disturbing you with such problems, but I write usually the
> title, composer with the musixsty.tex. Shoul
On Sun, 9 Oct 2005, A.H.Gilbert wrote:
>
>
> I took the file into a hex editor and removed all "0d"s. It then processed
> OK.
>
> The reqired "kfsqpmx.tex" file is in the zip pack "kfur.zip" which is a
> compendium of Bach fugues, transcribed by Werner, in the archive. There
> are many "0d"s are i
On Tue, 13 Sep 2005, Trent Johnston wrote:
>
> Oh by the way I'm using MTX which I assume the same thing would occur in
> PMX.
>
Not necessarily. M-Tx makes a separate PMX input block for each bar.
Therefore you cannot use commands that may not span different input blocks.
I wish there would be a
On Wed, 25 May 2005, Dirk Laurie wrote:
> Neil Killeen skryf:
> >
> > On compiling this source (MTx 0.53F, PMX 2.4) I get a warning
> > about a hanging slur. It's to do with the tie across the second and third
> > bars in the upper voice.
> >
> > Despite this, the notes seem to typeset ok. Howe
On Thu, 19 May 2005, Don Simons wrote:
>
> thought you were taking into account the way TeX was going to change the
> octave. As you can see, PMX is still confused about the default directions
> of the stems; that's because it still thinks it's putting the notes much
> lower. The moral of this sto
On Thu, 12 May 2005, Quinten wrote:
>
> When I use WinEdt to 'run'
> \input musixtex
> \parindent10mm
> \setname1{Piano} \setstaffs12 \generalmeter{\meterfrac44}
> \nobarnumbers \startextract \Notes\ibu0f0\qb0{cge}\tbu0\qb0g|\hl
> j\en \Notes\ibu0f0\qb0{cge}\tbu0\qb0g|\ql l\sk\ql n\en \bar
> \Note
> tenor clef. Likewise, one needs a change sign also within the peace
^
Sorry, I meant of course piece!
___
TeX-music mailing list
TeX-music@icking-music-archive.org
http://icking-music-
awkward, isn't it. Sorry for not including the practical example.
Regards,
Christof
--
Prof. Dr. Christof Biebricher
Max-Planck-Institute for Biophysical Chemistry
D-37070 Göttingen
Tel: +49 (551) 201 1442
FAX: +49 (551) 201 1435
email: [EMAIL PROTECTED]
right away with
the intended, but unexpected clef.
However, in PMX, a clef change by Ct at the very beginning
is ignored and only possible after the first note.
The clef can be changed probably simply by in-line text, but
it would interest me why this is so.
Christof
--
Prof. Dr. Christof
On Wed, 17 Nov 2004, Jean-Pierre Coulon wrote:
>
> > I agree that it is a nuisance to find our open source scores thus made
> > subject to bargaining. However, what can we do about it? I'm unsure
> > whether http://www.pianofiles.com/ breaks any 'laws' at all.
>
> OK, if I am the only one here com
On Mon, 15 Nov 2004, Don Simons wrote:
>
> 1. Say the tie starts in voice 1. If a rest or a note at a different pitch
> starts in voice 1 at the time you want the tie terminated in voice 2, you
> can still do it in voice 1. The tie will remain horizontal, and appear to
> terminate on the voice 2 n
On Sat, 13 Nov 2004, Don Simons wrote:
> I've just uploaded a new beta to
>
> http://icking-music-archive.org/software/pmx/pmx2505.zip
>
Thank you, Don.
There is still a big wish on my list, which I mentioned already
some years ago. Polyphonic organ music very frequently demands that a
key is not
On Sat, 30 Oct 2004, Don Simons wrote:
> I put in the F option at Werner's request, because Bach used it somewhere
> and Werner wanted to reproduce Bach's rhythmic notation. I've never come
> across it in any other context. I respect Bach a great deal, but in fact the
> F notation is ambiguous and
On Tue, 26 Oct 2004, Christian Mondrup wrote:
> main note not only the main note is offset but also the preceding grace
> note. Can I do what I want with 'plain PMX' ?
Part of the problem comes from the opposite direction of the stems.
Gsxle looks acceptable to me.
Christof
__
On Tue, 27 Jul 2004, Stefan Svensson wrote:
> Not being an organ player, what does "+ Ped. k" and "- Ped. k" mean?
It is not standard, but often means in German `Pedalkoppel an/ ab'. If nothing
else is written, `Tirasse' is meant, i.e. coupling of great and pedal.
Christof
___
On Thu, 22 Jul 2004, Jean-Pierre Coulon wrote:
> > ... i have already ordered the printed score. If the adaption for organ
> > (made by Patrik Vretblad) is old enough (that is, 70 years) I might
> > create a PMX version myself.
>
> Hum! In Europe this may not be enough, unless Good Patrick Vretbla
Dear all:
First of all, I want to thank Dirk Laurie for
the new version of M-Tx, expecially the improvement
with the slurs and ties which solve many problems I
had previously. I have a new coding problem, though.
In the attached file (extension txt should be reconverted to
mtx), in the Tenor line b
On Thu, 29 Apr 2004, Bodo Meissner wrote:
>
> in the attached example the lyrics lines are not vertically aligned.
> It's the first time this problem occurs to me. It seems to be specific
> to this score, because I cannot reproduce it with other scores I made
> before.
I had plenty of errors in pr
On Wed, 14 Apr 2004, Maurizio Codogno wrote:
> discarded from the list, as a measure against worms. Yes, we need it.
May I politely correct: The M$ users among us need it...
It is dangerous to have dialects of musixtex around.
Nevertheless, the patch as such (the one that came through) might be so
On Thu, 26 Feb 2004, Roland Stigge wrote:
>
>
> f77 -O2 -g -Wall -o pmxab pmxab.for
I also used g77 earlier and sometimes got similar results. As
recommended by Christian, I changed to the two-step compilation
via f2c an
On Wed, 18 Feb 2004, Dirk Laurie wrote:
>
> This change invalidates a sentence in the present M-Tx manual suggesting
> that it is a good idea to code { ( ... ) ... } rather than
> ( { ... } ... )
>
> If I receive no violent objections to this suggestion, I shall make it
> "official" (since no one
On Tue, 17 Feb 2004, Francois Planiol-Auger wrote:
>
> Here it is now
>
The only mistake I found was the invocation of a macro that did
not exist. If you write
Title: {\names FPA}
all works fine.
Christof
___
Tex-music mailing list
[EMAIL PROTECTED]
htt
On Mon, 12 Jan 2004, Christian Mondrup wrote:
> >
> >
> > I notice exactly the same strange behavior under mandrake linux 9.1 for PPC.
>
> I don't recognize that behaviour with my current typesetting project
> whether I use an f2c- or a g77 compiled pmx (2.415) binary. My OS
> environment is good
Lieber François,
Glückwunsch zu Suse-Linux. Damit brauchst Du keine extra Shell
mehr, weil Linux sie schon mitbringt. Wenn Du TeX schon auf einer
Windowspartition installiert hast, brauchst Du nur die executables
zu installieren. Sonst kannst Du die Windows-partition(en) einhängen,
z.B. als /dosc u
On Sat, 13 Dec 2003, Don Simons wrote:
>
> If a whole note is shifted to the left, then I agree. But if to the right,
> the proper distance depends on the width of whatever is in the way, and
> that's not necessarily another whole note. I can do it the way Olivier
> suggests, and it will cover cho
On Thu, 11 Dec 2003, Cornelius C. Noack wrote:
> This is strange: I use Acrobat reader 5.0, and I CAN'T reproduce the
> problem. But this is under Win 98 ... And Francois is using Acrobat
> Reader 6.0 ---
Fortunately, I could reproduce the error under Acroread 6.0 on a Windows
computer and track t
Dear Fraçois,
On Thu, 11 Dec 2003, Francois Planiol-Auger wrote:
>
> Question 1: when scrolling in the german pmx manual, I got the warning
> (translated from german with my own words):
>
> parts will eventually not be correct displayed or printed.>
>
A repaired font of slz20 has been provided so
On Fri, 5 Dec 2003, Christian Mondrup wrote:
> 2.
> One of my purposes with typesetting the Laub Ritornelles is to test
> M-Tx/PMX features not relevant to early music which is my main typesetting
> interest. Among the problems I've encountered is that vertical and
> horizontal fine tuning of PMX
On Fri, 5 Dec 2003, Bernhard Lang wrote:
>
> Nevertheless this gives often rise to confusion, since less informed
> people often tend to interpret text slurs in vocal music as something
> halfway between phrasing (or even worse "legato") and pure text (melisma)
> syntax. At least in ancient music
parsingOn Fri, 5 Dec 2003, Dirk Laurie wrote:
> >
> M-Tx passes along everything that starts with a letter that it does not
> understand. Unfortunately, some PMX enhancements occur in things that
> M-Tx understands the way it was. M-Tx tries to extract the things it
> needs and keep the rest int
On Thu, 4 Dec 2003, Olivier Vogel wrote:
>
> Here the long slur is coded directly in PMX. But I can't
> code it with M-Tx! I don't understand why.
>
It is relatively easy to understand. The development of M-Tx
stopped at a time where PMX was in strong development. The trouble
is that M-Tx is even
On Tue, 4 Nov 2003, Simon Dreher wrote:
> how can I get multiple ties in a chord with m-tx? Coding a chord with
> three ties [with (t and )t] I get an error message that only two pairs
> of nested slurs are allowed.
In PMX you should use slurs with an ID, e.g. (1 )1 (2 )2. I have not
tested whe
49 matches
Mail list logo
