I've released version 1.36 of MusiXTeX. This supports accidentals for
Turkish classical music (Makam), new thin accidentals, and thicker ledger
lines and Postscript hairpins. It is also necessary to update to release
2023-01-11 of the MusiXTeX fonts package.
http://icking-music-archive.org/softwar
Unfortunately, the author of musixtex is no longer with us. If someone
wants to try implementing this suggestion, I'll incorporate it, but note
that new attributes can be activated by no less than 14 different commands
and some of them can be used when there are *no* attribute changes.
The source
On Sun, May 22, 2022 at 12:12 AM wrote:
>
> Rodolfo--
>
> I now understand exactly what you're looking for, and it poses a very
> interesting logical problem. I don't have a solution. But I will just say
> that in a way PMX has already solved the problem if you leave the line break
> locations up
start of a new system
it repeats it at the end of the old one; otherwise it doesn't do anything
special.
--Don
> -Original Message-
> From: TeX-Music
> On Behalf Of Rodolfo Medina
> Sent: Saturday, May 21, 2022 10:32 AM
> To: Werner Icking Music Archive
> Subject:
Thanks indeed Don and Jean-Pierre: in both your examples though it
seems to me that you force break whereas what I'm looking for is a way
- if any - to tell TeX to add the meter change also on previous staff
*only* if break ever occur but leave everything as normal *if* instead
that break does not
Try the attached workaround
--
Jean-Pierre Coulon\input musixtex
\nostartrule
\generalmeter{\meterfrac34}
\startpiece
\NOtes\qa{cdf}\en
\bar
\NOtes\qa{cdf}\en
\bar
\NOtes\qa{cdf}\en
\bar
\NOtes\qa{cdf}\en
\bar
\NOtes\qa{cdf}\en
\generalmeter{\meterfrac24}\Changecontext\zstoppiece
\startbarno=7
Simons
> -Original Message-
> From: TeX-Music
> On Behalf Of Rodolfo Medina
> Sent: Saturday, May 21, 2022 6:30 AM
> To: Werner Icking Music Archive
> Subject: [Tex-music] MusiXTeX: changes at the end of a system
>
> Hi all...
>
> In MusiXTeX code: I
Hi all...
In MusiXTeX code: I usually change meter with, e.g.,
\generalmeter{\meterfrac{3}{4}}%
\changecontext%
just after the \enotes command; but I wish, in case of a system break,
that the change occurred not only at the start of the new system but
also at the end of the previous one, like a
The problem here has nothing to do with drums or x; the \ibbu beams have to
be terminated by \tbu, not \tbbu.
On Fri, Jan 14, 2022 at 5:39 PM Qiang Chen 陈强 wrote:
> Dear community,
>
> The problem is simple, when I use MusiXTeX to write something for the
> cajon drum, once I add 'x' to the 16th
Dear community,
The problem is simple, when I use MusiXTeX to write something for the
cajon drum, once I add 'x' to the 16th beam, it doesn't show the upper beam
The source file and the pdf are attached.
The same problem is also submitted here
https://tex.stackexchange.com/q/628867/106187
God
Oops. That subject should have been musixtex-135.
Bob T.
On Sat, Aug 28, 2021 at 10:40 PM Bob Tennent wrote:
> I've released a new version of musixtex that includes a "handwriting" font
> from MuseScore and an extension library musixjt.tex to use this font for
> all textual elements of a sco
I've released a new version of musixtex that includes a "handwriting" font
from MuseScore and an extension library musixjt.tex to use this font for
all textual elements of a score, as is traditional in jazz scores.
http://icking-music-archive.org/software/musixtex/musixtex135.zip
http://icking-mus
I've released version 1.34 of MusiXTeX. This release
includes a new extension library musixftab.tex which
supports traditional French tablature using script
letters rather than numerals to specify notes. The
\tabfnt definitions in musixtex.tex have been revised to
allow re-definition in musixftab.t
>|Den 04.07.2021 kl. 18.23 skrev Bob Tennent:
>|> I've released a new version of the musixtex package.
>|> This version improves on the tablature support:
>|> tablature notes are now in (Helvetica) bold, tablature
>|> notes below the staff now use slashes (/) rather than
>|> ledger lines, as
Den 04.07.2021 kl. 18.23 skrev Bob Tennent:
I've released a new version of the musixtex package. This
version improves on the tablature support: tablature notes
are now in (Helvetica) bold, tablature notes below the
staff now use slashes (/) rather than ledger lines, as is
conventional in French
I've released a new version of the musixtex package. This
version improves on the tablature support: tablature notes
are now in (Helvetica) bold, tablature notes below the
staff now use slashes (/) rather than ledger lines, as is
conventional in French tablature, and new commands are
provided to ge
>|Takanori Uchiyama, the developer of the type1 musixtex
>|fonts, has been following the discussion in the various
>|mail lists and, remarkably, has regenerated all the type1
>|fonts, correcting *all* the inconsistent glyph widths
>|(and also the internal FontNames). I've been testing
>|these
Takanori Uchiyama, the developer of the type1 musixtex
fonts, has been following the discussion in the various mail
lists and, remarkably, has regenerated all the type1 fonts,
correcting *all* the inconsistent glyph widths (and also the
internal FontNames). I've been testing these fonts with
severa
I've released version 1.31 of musixtex, which defines
macros \zzdoublebar, \zzbar and \zendpiece, and version
2021-01-07 of the autosp preprocessor which allows \Cp as an
abbreviation for \Cpause.
http://icking-music-archive.org/software/musixtex/musixtex131.zip
http://icking-music-archive.org/so
>|> >|I get an overfull box at the end of the staff
>|> >|system. Why does it occur, and how to avoid it...?
>|>
>|> You're trying to squeeze too much into one system.
>|>Replace
>|>
>|> \parindent2cm%
>|>
>|> by
>|>
>|> \parindent1.5cm%
>|>
>|> and there's no problem.
>|Thanks, th
Bob Tennent writes:
> >|I get an overfull box at the end of the staff system. Why
> >|does it occur, and how to avoid it...?
>
> You're trying to squeeze too much into one system. Replace
>
> \parindent2cm%
>
> by
>
> \parindent1.5cm%
>
> and there's no problem.
>
> Bob
Thanks, this solved
>|I get an overfull box at the end of the staff system. Why
>|does it occur, and how to avoid it...?
You're trying to squeeze too much into one system. Replace
\parindent2cm%
by
\parindent1.5cm%
and there's no problem.
Bob
---
TeX-music@tug.org mailing list
I
Hi all...
In the attached MusiXTeX example, to be processed with simply:
$ tex file
$ musixflx file
$ tex file,
I get an overfull box at the end of the staff system. Why does it occur, and
how to avoid it...?
Please help whoever can.
Thanks in advance,
Rodolfo
\input musixtex
\input pmx
Rodolfo Medina writes:
> Hi all.
>
> I'm attaching a MusiXTeX example with overfull hbox at system break. I wonder
> why TeX doesn't break at the previous bar...
mmmhhh... maybe I understand... breaking at any of the previous bars would
maybe make too short the last system of the piece...
R
Hi all.
I'm attaching a MusiXTeX example with overfull hbox at system break. I wonder
why TeX doesn't break at the previous bar... It is allowed to... Please help
whoever can. Process with simply: `tex test; musixflx test; tex test'; or
also: `musixtex test'.
Thanks,
Rodolfo
\input musixtex
>|> >|Yes, the flageolett-circle becomes bigger, but also the whole note
>|> >|become bigger.
>|> >|How can I avoid this effect?
>|>
>|> Try
>|>
>|> {\largenotesize\flageolett{17}}\ a
>|>
>|> which is what I had suggested, or
>|>
>|> \largenotesize\flageolett{17}\normalnotesize\ a
>|\flageolett{17}\ a06 /
>|\largenotesize\flageolett{17}\ a /
>|\Largenotesize\flageolett{17}\ a /
>|
>|Yes, the flageolett-circle becomes bigger, but also the whole note
>|become bigger.
>|How can I avoid this effect?
Try
{\largenotesize\flageolett{17}}\ a
which is what I had suggested
Am 16.05.2019 um 17:24 schrieb Bob Tennent:
>|Am 16.05.2019 um 13:14 schrieb Bob Tennent:
>|> >|In musixtex.tex I find this definition
>|> >|
>|> >|\def\flageolett{...}
>|> >|
>|> >|and would like to know, how to increase the size of the
>|> >|little circle by 50 %.
>|
Rodolfo Medina writes:
> Rodolfo Medina writes:
>
>> Is there anyone who has typeset J. S. Bach's two-voices Invention...? On
>> IMSLP repository I coudn't find the engraving sources...
>
>
> ...it's a bit depressing to see how little is in percentage the presence of
> MusiXTeX/pmx sources in I
>|In musixtex.tex I find this definition
>|
>|\def\flageolett{...}
>|
>|and would like to know, how to increase the size of the
>|little circle by 50 %.
{\largenotesize\flageolett ...}
Bob
---
TeX-music@tug.org mailing list
If you want to unsubscribe or look at t
In musixtex.tex I find this definition
\def\flageolett{\n@iv120\uacc@Char}
and would like to know, how to increase the size of the little circle by
50 %.
Thanks,
Dieter
--
Dr. Dieter Glötzel
Im Rosengarten 27
64367 Mühltal
Tel.: 06151 / 360 82 72
---
After Christian Mondrup's kindly added pmx sources to IMSLP for Bach's
Inventions, another couple of requests from me...: anyone has typeset Bach's
Partita BWV 826 in C minor - and the Paradisi's Toccata in A major...?
Thanks...
Rodolfo
---
TeX-music@tug.org mailing li
Christian Mondrup writes:
> Den 29/04/2019 kl. 20.37 skrev Rodolfo Medina:
>> Christian Mondrup writes:
>>
>>> Luigi has sent me alternative PMX sources to his edition of the
>>> two-part inventions by J.S.Bach. I've added these to IMSLP. They'll
>>> be available on the above quoted URL upon app
Den 29/04/2019 kl. 20.37 skrev Rodolfo Medina:
Christian Mondrup writes:
Luigi has sent me alternative PMX sources to his edition of the
two-part inventions by J.S.Bach. I've added these to IMSLP. They'll
be available on the above quoted URL upon approval from the IMSLP
staff (I'm not a staff
Christian Mondrup writes:
>> Years ago Luigi Cataldi prepared a complete edition for my former site WIMA,
>> now merged with IMSLP. Luigi, like many other WIMA contributors published his
>> engraving sources (in this case MUP)
>> along with the pdf scores. Luigi's engraving sources are still
>> a
Years ago Luigi Cataldi prepared a complete edition for my former
site WIMA, now merged with IMSLP. Luigi, like many other WIMA
contributors published his engraving sources (in this case MUP)
along with the pdf scores. Luigi's engraving sources are still
available on IMSLP:
https://imslp.org/wi
"Don Simons" writes:
> maurizio .mau. codogno wrote
>
>>I agree that a section of sources would be very useful: as many have said,
>> it is easier not to start from scratch if you want to edit a piece of sheet
>> music.
>>(I would even accept abc sources!) But I also >think that it would be be
Dieter writes:
> Hi Rodolfo,
>
> "fi invalid" means that the input xml-file does not exist.
> Could you send me the whole input command?
>
> I am just unable to test, because my linux-ubuntu machine is not working
> properly (mousepointer shivering),
> I must get a new mouse and keyboard early n
maurizio .mau. codogno wrote
>I agree that a section of sources would be very useful: as many have said,
> it is easier not to start from scratch if you want to edit a piece of sheet
> music.
>(I would even accept abc sources!) But I also >think that it would be better
>to
>have it as a side
Hi Rodolfo,
"fi invalid" means that the input xml-file does not exist.
Could you send me the whole input command?
I am just unable to test, because my linux-ubuntu machine is not working
properly (mousepointer shivering),
I must get a new mouse and keyboard early next week.
Regards, Dieter
A
Rodolfo Medina writes:
> "Don Simons" writes:
>
>> Bob Tennent wrote
>> ...
>>> Instead of duplicating IMSLP, for no evident benefit, I suggest that
>> authors
>>> can send sources for M-Tx, PMX, autosp or MusiXTeX processing to me for
>>> inclusion in "contrib"
>>> sub-directories of subsequent
On Sat, Apr 20, 2019 at 6:39 PM Rodolfo Medina
wrote:
>
> I personally believe in, and wish here to remark, the importance of a
> specific
> common time-growing patrimony of MusiXTeX sources, along with IMSLP or
> aside...
> But maybe aside...
I agree that a section of sources would be very use
"Don Simons" writes:
> Bob Tennent wrote
> ...
>> Instead of duplicating IMSLP, for no evident benefit, I suggest that
> authors
>> can send sources for M-Tx, PMX, autosp or MusiXTeX processing to me for
>> inclusion in "contrib"
>> sub-directories of subsequent CTAN releases of those packages. T
Bob Tennent wrote
...
> Instead of duplicating IMSLP, for no evident benefit, I suggest that
authors
> can send sources for M-Tx, PMX, autosp or MusiXTeX processing to me for
> inclusion in "contrib"
> sub-directories of subsequent CTAN releases of those packages. They will
> then be incorporated i
Dieter writes:
> Hi Rodolfo,
>
> I believe you are working with Linux, right? Did you have a look at the
> README file?
>
> There should be 5 entries in the command line. Like this one:
>
> ./XML2PMX ./XML/Telemann.xml ./PMX/Telemann.pmx n 10
>
> The option "n" means no option chosen. And "10" is
>| >|Rodolfo Medina writes:
>| >|
>| >|I'd propose that a specific repository be created,
>| >|including all and only music score sources...
Instead of duplicating IMSLP, for no evident benefit, I
suggest that authors can send sources for M-Tx, PMX, autosp
or MusiXTeX processing to me for inc
Hi Christian,
could you please send me your XML file or even better pdf file of Anna
Magdalena's Musette?
Then I will run it through my machinery and we can count the errors.
Regards, Dieter
Am 20.04.2019 um 11:35 schrieb Christian Mondrup:
On 4/20/19 12:05 AM, Rodolfo Medina wrote:
Dieter
Hi Rodolfo,
I believe you are working with Linux, right? Did you have a look at the
README file?
There should be 5 entries in the command line. Like this one:
./XML2PMX ./XML/Telemann.xml ./PMX/Telemann.pmx n 10
The option "n" means no option chosen. And "10" is the number of bars you want
to
Dieter writes:
> For all people in need of a PMX-version of existing note sheets (of e.g.
> the Bach two voice inventions) I have a tool since 2015: "XML2PMX".
> Please find attached the 1st invention (BWV 772) in terms of MusicXML,
> PMX and PDF.
> There are three steps:
> (1) Scan the original
>|Bob Tennent writes:
>|
>|> >|Rodolfo Medina writes:
>|> >|
>|> >|I'd propose that a specific repository be created,
>|> >|including all and only music score sources...
>|>
>|> Why would that make a difference?
>|
>|The difference is that a source file can be easily
>|converted in
On 20.04.2019 13:38 Rodolfo Medina wrote:
> The difference is that a source file can be easily converted into MusiXTeX
> format and so edited at pleasure; a PDF final output can't, or it can but with
> much more difficulty.
As Christian Mondrup already wrote it would be
Bob Tennent writes:
> >|Rodolfo Medina writes:
> >|
> >|I'd propose that a specific repository be created, including all and
> >|only music
> >|score sources...
>
> Why would that make a difference?
The difference is that a source file can be easily converted into MusiXTeX
format and so e
>|Rodolfo Medina writes:
>|
>|I'd propose that a specific repository be created, including all and
>|only music
>|score sources...
Why would that make a difference?
Who would set up and manage this repository? Are you
volunteering?
---
TeX-music@tug.org mailing
On 4/20/19 12:05 AM, Rodolfo Medina wrote:
Dieter writes:
Thank you... It'd be great. I'll try to install Audiveris in my Linux
machine. If successful, I'll then start the happy `xml -> tex' walk. I'll let
you know.
I managed to build and run audiveris on my Mint 18.3 linux station. I
fo
Rodolfo Medina writes:
> Bob Tennent writes:
>
>> >| it's a bit depressing to see how little is in percentage
>> >| the presence of MusiXTeX/pmx sources in IMSLP
>>
>> Lots of scores at IMSLP were produced using MusiXTeX, but
>> the contributors haven't bothered to submit their "engraving
>> f
Bob Tennent writes:
> >| it's a bit depressing to see how little is in percentage
> >| the presence of MusiXTeX/pmx sources in IMSLP
>
> Lots of scores at IMSLP were produced using MusiXTeX, but
> the contributors haven't bothered to submit their "engraving
> files".
I think it's a pity...
Dieter writes:
> For all people in need of a PMX-version of existing note sheets (of e.g.
> the Bach two voice inventions) I have a tool since 2015: "XML2PMX".
> Please find attached the 1st invention (BWV 772) in terms of MusicXML,
> PMX and PDF.
> There are three steps:
> (1) Scan the original
>| it's a bit depressing to see how little is in percentage
>| the presence of MusiXTeX/pmx sources in IMSLP
Lots of scores at IMSLP were produced using MusiXTeX, but
the contributors haven't bothered to submit their "engraving
files". If anyone is interested in getting sources for any
of my sco
On 4/19/19 9:12 AM, Rodolfo Medina wrote:
Rodolfo Medina writes:
Hi all MusiXTeX users...
Is there anyone who has typeset J. S. Bach's two-voices Invention...? On
IMSLP repository I coudn't find the engraving sources...
Years ago Luigi Cataldi prepared a complete edition for my former site
Rodolfo Medina writes:
> Hi all MusiXTeX users...
>
> Is there anyone who has typeset J. S. Bach's two-voices Invention...? On
> IMSLP repository I coudn't find the engraving sources...
...it's a bit depressing to see how little is in percentage the presence of
MusiXTeX/pmx sources in IMSLP...
Hi all MusiXTeX users...
Is there anyone who has typeset J. S. Bach's two-voices Invention...? On IMSLP
repository I coudn't find the engraving sources...
Thanks a lot,
Cheers
Rodolfo
---
TeX-music@tug.org mailing list
If you want to unsubscribe or look at the archi
Rafael N.
Sent: Thursday, March 21, 2019 11:36 AM
To: tex-music@tug.org
Subject: [Tex-music] Musixtex
Hey, i'm not sure if i should speak english or german, and because of that i
will continue in english.
I have a question about the musictex and musixtex. How do I get audio files
with
Hey, i'm not sure if i should speak english or german, and because of that i
will continue in english.
I have a question about the musictex and musixtex. How do I get audio files
with those packages and i would very appreciate it if you may send me an
example code with a step by step guide beca
This release incorporates support for tablature notation
for fretted string instruments such as lute, guitar, banjo,
mandolin, and so on, adapted from R.J. Gelten's tabdefs.tex.
An example and documentation are in Section 18.10 of
musixdoc.pdf. Thanks to Christian for testing beta versions
of the
>|> Please do not send html mail to the list.
>|
>|Hum, but you're doing so! ;-)
Sorry. I had to redirect the message to gmail to read it
and gmail decided to use html.
---
TeX-music@tug.org mailing list
If you want to unsubscribe or look at the archives, go to
ht
On Tue, 12 Jun 2018, Bob Tennent wrote:
Please do not send html mail to the list.
Hum, but you're doing so! ;-)
--
Jean-Pierre
---
TeX-music@tug.org mailing list
If you want to unsubscribe or look at the archives, go to
http://tug.org/mailman/listinfo/tex-music
tiple times in a row. But in the end the file compiles.
>
> Jörg Hudelmaier
>
> *Gesendet:* Samstag, 09. Juni 2018 um 21:15 Uhr
> *Von:* "Jean-Pierre Coulon"
> *An:* "Werner Icking Music Archive"
> *Betreff:* [Tex-music] MusiXTeX or Tex bug or feature?
>
quot;
Betreff: [Tex-music] MusiXTeX or Tex bug or feature?
When I musixtex a file I obtain the message \inline= and I am unable to enter any character. X gives nothing. All I can do is to kill the command prompt window I was working with. Any other solution? Bye, Jean-Pierre Coulon ---
Bob Tennent wrote:
> >|I've more commonly seen this using OpusTeX - it's usually >|a sign that
> either the .mx2 file is out-of-sync with the
> >|.mx1 file, as Bob noted.
>
> either ... or what?
Oops - the "either" was from an earlier edit which I clearly forgot to delete!
> >|Deleting the .
CTRL-X is rarely the command exit anything - CTRL+C should terminate
TeX, unless something's really broken.
Yes. I typed this mail too fast!
I've more commonly seen this using OpusTeX - it's usually a sign that
either the .mx2 file is out-of-sync with the .mx1 file, as Bob noted.
Deleting the
>|I've more commonly seen this using OpusTeX - it's usually
>|a sign that either the .mx2 file is out-of-sync with the
>|.mx1 file, as Bob noted.
either ... or what?
>|Deleting the .mx1 *and* .mx2
>|file should clear it, otherwise there's a bug.
>|
>|If memory serves, from writing TeX-bas
Jean-Pierre Coulon wrote:
> When I musixtex a file I obtain the message \inline= and I am unable to enter
> any character. X gives nothing. All I can do is to kill the command
> prompt window I was working with.
CTRL-X is rarely the command exit anything - CTRL+C should terminate TeX,
unless som
>|When I musixtex a file I obtain the message \inline= and I am unable to
>|enter any character. X gives nothing. All I can do is to kill the
>|command prompt window I was working with.
>|
>|Any other solution?
Jean-Pierre: In musixtex.tex, the section that defines
macros to set up the secon
>|When I musixtex a file I obtain the message \inline= and I am unable to
>|enter any character. X gives nothing. All I can do is to kill the
>|command prompt window I was working with.
Jean-Pierre: What file is "a file"?
Does your musixtex work on the small examples available at
http://icki
When I musixtex a file I obtain the message \inline= and I am unable to
enter any character. X gives nothing. All I can do is to kill the
command prompt window I was working with.
Any other solution?
Bye,
Jean-Pierre Coulon
---
TeX-music@tug.org mailing list
If yo
I've released version 1.28 of MusiXTeX. It's unchanged
from version 128beta previously announced which provides new
commands for repeats *within* a bar, possibly forced to be
at the end of a system, and fixes a bug for \nblines < 4.
http://icking-music-archive.org/software/musixtex/musixtex128.zip
I've released version 1.27 of MusiXTeX:
http://icking-music-archive.org/software/musixtex/musixtex127.zip
http://icking-music-archive.org/software/musixtex/musixtex127.tds.zip
It introduces several new features:
+ \meterN
+ \xxtuplet
+ pointed half-notes \hap \happ analogous to \qap \qapp
I've released MusiXTeX version 1.26. The only changes
are corrections for minor bugs in the implementation of
\setinterstaff that were causing Overfull hboxes. Thanks to
Staffan Lundberg for reporting the problem.
http://icking-music-archive.org/software/musixtex/musixtex126.zip
Bob T.
--
I've released MusiXTeX version 1.25. The changes are minor:
* included dummy file tuplet.tex
* defined \qap, \qapp, \tqsk
* added \ignorespaces in musixltx.tex
http://icking-music-archive.org/software/musixtex/musixtex125.zip
Bob T.
---
TeX-music@tug.org mailing list
http://icking-music-archive.org/software/musixtex/musixtex123.zip
Changes:
+ added \xtr and \ptr ornaments
+ adjusted spacing of \tr
+ corrected definition of \C@Inter for \nblines > 6
+ version 0.16e of the musixtex.lua script
+ revised material on page layout in the manual
Bob T.
--
From: TeX-Music [mailto:tex-music-boun...@tug.org] On Behalf Of Bob
>>> Tennent
>>> Sent: Saturday, May 07, 2016 4:13 PM
>>> To: Florin Panc
>>> Cc: tex-music@tug.org
>>> Subject: Re: [Tex-music] musixtex possible bug
>>>
>>&g
do.
>
> --Don Simons
>
>> -Original Message-
>> From: TeX-Music [mailto:tex-music-boun...@tug.org] On Behalf Of Bob
>> Tennent
>> Sent: Saturday, May 07, 2016 4:13 PM
>> To: Florin Panc
>> Cc: tex-music@tug.org
>> Subject: Re: [Tex-music] musixtex poss
c@tug.org
> Subject: Re: [Tex-music] musixtex possible bug
>
> >|Look at line 932 in sonatalunii.tex (moonlight sonata).
> >|
> >|At line 926 I put a cautionary \na K command and at my >|computer
> shows sharp instead of natural.
>|Look at line 932 in sonatalunii.tex (moonlight sonata).
>|
>|At line 926 I put a cautionary \na K command and at my
>|computer shows sharp instead of natural.
Difficult to do when the file has only 745 lines.
---
TeX-music@tug.org mailing list
If you want to unsub
>|I'm using a pdflatex compiler for musixtex package and
>|print natural instead of sharp
Your tex file can't possibly work with pdflatex because it
uses fontspec.
Please post a MWE (minimal working example) that compiles
and demonstrates what you think is a bug. And please don't
use fonts that
I've uploaded this to WIMA and CTAN. The revisions include
+ a more robust version 0.16c of the musixtex.lua script
+ adjustments to the dimensions involved in the \pdlud command
+ numerous minor improvements to the font definitions and
extension libraries
Bob T.
>|Perhaps now the warning should be:
>|
>|> If you've elected to write your text documents with
>|MS-Word and not with TeX > or LaTeX I would recommend
>|to find another software package to do musical >
>|typesetting. Mastering it will disorganize you etc.
>|
>|or some brief explanation tha
On Mon, 30 Nov 2015, Bob Tennent wrote:
>|On the other hand I wonder, whether the "Leitmotiv" on
>|the title page of musixdoc.pdf 1.19:
>|
>|If you are not familiar with TEX at all, I would
>|recommend to find another software package t
>|On the other hand I wonder, whether the "Leitmotiv" on
>|the title page of musixdoc.pdf 1.19:
>|
>|If you are not familiar with TEX at all, I would
>|recommend to find another software package to do musical
>|typesetting. Setting u
Hi Bob,
the new tremolo commands are exactly what I was looking for. Thank you
so much!
On the other hand I wonder, whether the "Leitmotiv" on the title page of
musixdoc.pdf 1.19:
If you are not familiar with TEX at all, I would re
The main change is that typos causing problems with
\Largemusicsize have been corrected. Also there are new
commands for tremolos and an updated musixtex.lua script.
http://icking-music-archive.org/software/musixtex/musixtex119.zip
Bob T.
---
TeX-music@tug.org mailing
I've submitted MusiXTeX version 1.18 to WIMA and CTAN.
Changes include
+ musixtmr.tex, musixplt.tex and musixhv.tex now support traditional
accented characters in etex processing
+ length of beam stems increased
+ definitions of \raggedstoppiece and \slide moved into musixtex.tex
* \xppff no
> I've put proposed musixtex.tex and musixdoc.pdf for version 1.17 at
>
> http://icking-music-archive.org/software/musixtex/musixtex-T117beta/
>
> The main changes are as follows:
>
> re-defined \centerpause, \centerPAuse etc. (but not \centerbar, \pause,
> etc.) re-defined \ppff and \txtfont to
I've put proposed musixtex.tex and musixdoc.pdf for
version 1.17 at
http://icking-music-archive.org/software/musixtex/musixtex-T117beta/
The main changes are as follows:
re-defined \centerpause, \centerPAuse etc. (but not \centerbar, \pause, etc.)
re-defined \ppff and \txtfont to be staffsize-d
>|I've uploaded betas to WIMA:
>|
>|http://icking-music-archive.org/software/musixtex/musixtex116.tds.zip
>|http://icking-music-archive.org/software/musixtex/musixtex-fonts116.tds.zip
>|
>|Unzip these archives at the root of a local or personal
>|texmf tree and update the file-name database
>|I've uploaded betas to WIMA:
>|
>|http://icking-music-archive.org/software/musixtex/musixtex116.tds.zip
>|http://icking-music-archive.org/software/musixtex/musixtex116.tds.zip
That second link should be
http://icking-music-archive.org/software/musixtex/musixtex-fonts116.tds.zip
Bob T.
I've uploaded betas to WIMA:
http://icking-music-archive.org/software/musixtex/musixtex116.tds.zip
http://icking-music-archive.org/software/musixtex/musixtex116.tds.zip
Unzip these archives at the root of a local or personal
texmf tree and update the file-name database on your TeX
system.
Change
"Dr. Gerhard Eber" writes:
> "Dr. Gerhard Eber" writes:
>
>> Don Simons writes:
>>
>>> Yes, and come to think of it, we built the MusiXTeX manual with LaTeX and
>>> with many many more than 20 \startextract...\endextract
>>>
>>> To get help, you really should post an example of a LaTeX source t
>|Sorry, 20 was not correct, I tried again with the latest musixflx and
>|found that it stopped working in the 2nd run after 184 pieces.
musixflx has "array" sizes:
MAX_SIGNS = 128; MAX_SECTIONS = 128; MAX_BARS = 2048
but you should be getting error messages if these are exceeded.
You coul
Don Simons writes:
> Yes, and come to think of it, we built the MusiXTeX manual with LaTeX and
> with many many more than 20 \startextract...\endextract
>
> To get help, you really should post an example of a LaTeX source that fails.
> And be sure to also post any custom TeX files you included.
>
1 - 100 of 211 matches
Mail list logo