>|How could I put the duration of a multirest below the staff?
what are you using to generate the multirest? musixtex.tex, pmx,
autosp, ...
---
TeX-music@tug.org mailing list
If you want to unsubscribe or look at the archives, go to
>|Would you be willing to provide me with a trial
>|executable with the changes you're suggesting? I'm
>|wondering if it will still fail my test if I use \xbar.
>|If it does, I would consider revising PMX to take
>|advantage of the enhancement. If we could find someone
>|who knows lua and is
>|On p.77 of MusiXTeX manual (v. 1.27, Dec 22 2017) there's
>|the subsection titled `Changes at the end of a system'
>|but then it closes soon without explaining how to do
>|that... Am I missing some other place of the manual?
The whole chapter tells you "how to". That subsection only
points
>|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
>|For me, this file works OK:
>|
>|===
>|
>|\input musixtex
>|\hsize=524pt
>|\vsize740pt
>|\def\nbinstruments{1}
>|\setstaffs11
>|\setclef10
>|\generalmeter{\meterfrac{4}{4}}%
>|\nostartrule
>|\startmuflex
>|\parindent 253pt
>|
>| >|And is there any way to allow \parindent > 253pt?
More than one bar?
---
TeX-music@tug.org mailing list
If you want to unsubscribe or look at the archives, go to
https://tug.org/mailman/listinfo/tex-music
>| 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
>| musixguide.pdf,
>| but is there any doc in English?
There's enough English in the example, crucially
\input colordvi.tex
:
\OliveGreen\startpiece
See Section 7 of the dvips documentation for more. Colour
support for MusiXTeX is just colour support for plain TeX.
Bob T.
>| >|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
>|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
>|> Here's how to do this in musixtex, based on Olivier's
>|> coda.pmx. Notice there are *three* groups of special
>|> commands, before and after the "short" system, and then
>|> after the 2nd short system (or text after the short
>|> system).
My example was sent privately to Don, but here
>|This is educational...over the years I've noticed some
>|horizontal alignment issues related to whole notes, but
>|never realized there was a built in macro to fix them.
>|So naturally PMX doesn't make the whole note correction.
>|I suppose I could make PMX automatically use \wholeshift
>|Enlarging the \flageolett symbol works fine, but it is
>|not exactly aligned with the whole note "a06".
>From musixdoc.pdf:
These marks are horizontally centered relative to
solid note heads. To compensate for the fact that
whole notes are wider, you should use \wholeshift{Any
>| Where do I put the \wholeshift{} ?
\wholeshift{} will work for the "normalsize" \flageolett.
But for \Largenotesize you need a *left* offset. Try:
\def\flg#1{\Largenotesize\loffset{.13}{\flageolett{#1}}\normalnotesize}
Bob
---
TeX-music@tug.org mailing list
If
>|> I'm not sure what you mean by "horizontal shift" or exactly
>|
>|Don't you notice the vertical misalignment between notes at measure 2 ?
No I didn't; I was just looking at the ornament.
The horizontal shift seems to be caused by the ~
character *after* the \lcn{}{}. Maybe you want
>|> what you want but the following would seem to be easier and
>|> more flexible:
>|>
>|> \loff{\islurd1h}\tslur1e\qa{cdfe}
>|
>|Well, true with font-based slurs, but musixps manages very steep slurs in
>|its manner. :-)
Try this with musixps:
>|In a passage where the other instrument has the fastest
>|notes the horizontal spacing is governed by this
>|instrument (measure 3).
The (relative) horizontal spacing is determined by your use
of \NOtes.
>|Why do I have to say \multnoteskip\tinyvalue at this
>|passage for the spacing to
>|> Try this with musixps:
>|>
>|> \loffset{1.8}{\islurd1g}\loffset{0.8}{\tslur1e}
>|
>|Yes but I prefer mine !
De gustibus non est disputandum.
Bob
---
TeX-music@tug.org mailing list
If you want to unsubscribe or look at the archives, go to
>|I want to use a short, steep font-based slur a an ornament with
>|\lcharnote.
>|
>|Why does this \lcharnote cause a horizontal shift in bar 2 of my example ?
I'm not sure what you mean by "horizontal shift" or exactly
what you want but the following would seem to be easier and
more
I've released a new version of the autosp preprocessor.
The new feature is that note spacing is now scaled for
instrument musicsize, as suggested by Jean-Pierre Coulon.
http://icking-music-archive.org/software/autosp/
Bob T.
---
TeX-music@tug.org mailing list
If you
>|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 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,
>| the wording in the MusiXTeX manual as quoted above
>|is misleading...it implies you need to explicitly use
>|\wholeshift to center \Fermataup over a whole note, while
>|in fact that's one case where musixtex.tex does it for
>|you.
I agree. It'll be fixed in the next release.
Bob
>|I have a question about if I can put accompaniment chords on each bars.
Look at the musixcrd and pmxchords packages under Add-ons at
http://icking-music-archive.org/software/htdocs/
Bob T.
---
TeX-music@tug.org mailing list
If you want to unsubscribe or look at
>|Notes far above the staff have their stems automatically lengthened so the
>|stem goes to about the staff middle.
>|
>|But this prevents \stemlength to shorten it if I want. Is there a
>|workaround?
Use \stdstemfalse for each such note. (There is no command
to globally suppress the default
. If you are
determined for some reason to use f2c, please look at the
Makefile.am file in the tarball to see what options to f2c
and revisions to the f2c library are needed.
Bob Tennent
---
TeX-music@tug.org mailing list
If you want to unsubscribe or look
>|I don't know if this is useful. In order to compile
>|pmx294 I see that gfortran version that comes with
>|the Debian 9 distribution (Debian 6.3.0-18+deb9u1)
>|works well, while the second that comes with Fedora 30
>|distribution (Red Hat 9.2.1-1) doesn't work.
Thank you Luigi. It might be
>|I'm looking for a way to input guitar choking like this.
>|https://www.instagram.com/p/B7tNcMTgqsd/
It would have been helpful if the orientation wasn't 90 deg
off.
>|"cho." and small note with slur on the score is the
>|guitar choking. With PMX and M-Tx, as much as I learned,
>|there's
pmx-2.94 is now available in MiKTeX. Use the Updates action
in the MiKTeX Console, either for Admin or a personal user,
to update your installation. Let Don or I know if you have
any issues, particularly with the new features since 2.84.
Bob
---
TeX-music@tug.org
>|Why can't obtain dotted barlines on staves with a \changecontext or
>|\Changcontext? See my last bar.
Does anyknow if Rainer Dunker is still active? He was
the author of musixdbr.tex (and several other extension
packages) around 2002. He should be addressing this problem.
Bob
TeXLive 2020 has been officially released. It is not
possible to upgrade an earlier version but TeXLive 2020 can
be installed in parallel with an older version.
The 2020 release provides
musixtex (1.30)
pmx (2.94 2020-03-20)
M-Tx (0.63c)
autosp (2019-12-22)
for 16 platforms, including MacOSX
>|Maybe my question is too technical. I ask on the list
>|anyway.
Christian: I regret that I'm not able to help you on this.
For TeXLive, I stick to the suggested defaults. I suggest
you ask at tex-l...@tug.org.
Bob
---
TeX-music@tug.org mailing list
If you want to
>|Chopin's mazurka Op.67 n.2 .pmx file at IMSLP is
>|uncomplete: it only includes the first measure. Why...?
Presumably the source file was corrupted at some point.
Andre: Please send me privately the full pmx file and I'll
try and upload it to IMSLP.
>|With the occasion, I renew my
>|Adolf Jensen's Etuden Op.32 are beautiful... On IMSLP of
>|course they are only present in scanned PDFs. I tried
>|to run Sharpeye and Audiveris on them in order to get a
>|MusicXML format to be in turn converted to PMX via Dieter
>|Gloetzel's tool: but with very very poor result... Well,
>| How does one find out how many time a particular file on
>| IMSLP has been downloaded?
Go to the relevant work page, find the relevant sheet-music
heading, find the relevant file and look for a line like this:
#117989 - 0.10MB, 6 pp. - 8/10 2 4 6 8 10 (2) - 1680×
The first item is the
Dieter Glötzel has released an updated version of his
MusicXML-to-PMX converter (currently for Windows and Linux
only). The main improvement is a cleaner input organization.
http://icking-music-archive.org/software/xml2pmx/XML2PMX_Windows.zip
>|Thanks for updating XML2PMX on WIMA. I have tried it on Linux, but cannot
>|find any input XML file.
>|This is what I get in the terminal:
>|
>|===
>|./RunTelemann
>|
>|NoOfArgs : 5
>|./XML/Telemann.xml
>|./PMX/Telemann.pmx
>|sout :
>|So how do you set smaller subtitles in M-Tx?
Try
Title: Psalm 42\\{\normtype\it Ainsi que la biche r\'ee}
The \textit and \normalsize commands are for use in a LaTeX
document.
Bob T.
---
TeX-music@tug.org mailing list
If you want to unsubscribe or look at the
Danai was referring to the following:
http://icking-music-archive.org/software/xml2pmx/xml2pmx-2020-05-24.tar.gz
(now gzipped). Dieter and I have received assistance from
Mike Spivey who is responsible for obc, the Oxford Oberon
Compiler. The package contains Dieter's Oberon source files,
>|The file comes from a previous XML -> PMX convertion with
>|Dieter's fantastic XML2PMX.
Dieter's XML2PMX is promising but still "beta". He is
currently working through a test suite of MusicXML files to
try and squash bugs. If you were to open the xml file in
musescore, you could export a
>|I just installed the Miktex distribution. When I type PATH from the
>|command prompt I see C:\Program Files\MiKTeX\miktex\bin\x64\. This
>|directory contains dvips.exe. But when I type dvips something.dvi the
>|system says: The system cannot find the path specified.
Are you sure the dvips
Jean-Pierre:
>|In the 2017 version of psslurs.pro the string AR has been
>|changed into psxAR.
>From the HISTORY section of musixps.tex:
0.93 (17.2.2015)
changed definitions of AR, GDAR and GD to avoid collisions
in certain PS files
Bob T.
---
files and is included in the
package.
http://icking-music-archive.org/software/xml2pmx/xml2pmx.zip
Please report problems with the executables or the Linux
build system to me. Problems with the XML to PMX conversion
should be reported to Dieter Glötzel (d.gloetzel(at)web.de).
Bob Tennent
>|> >|On IMSLP there are 5 different typset editions of Scott
>|> >|Joplin's The Entertainer... One of those is declared to
>|> >|be MuseScore and MusicXML source, the other 4 are not
>|> >|declared at all... Does anyone know if among them is a
>|> >|pmx/MusiXTeX source...?
>|>
>|> The
>|could you send me the entertainer.xml?
Accessible at IMSLP:
https://imslp.org/wiki/The_Entertainer_(Joplin%2C_Scott)
under Scores.
Bob T.
---
TeX-music@tug.org mailing list
If you want to unsubscribe or look at the archives, go to
>|On IMSLP there are 5 different typset editions of Scott
>|Joplin's The Entertainer... One of those is declared to
>|be MuseScore and MusicXML source, the other 4 are not
>|declared at all... Does anyone know if among them is a
>|pmx/MusiXTeX source...?
The MusicXML score can be translated
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
Don and Dieter:
>The only PMX problem here occurs with a 2-note, unbeamed
>grace. It's true that PMX chokes on this, and its also
>true that with some effort I could modify the code to
>make it work. But really?? Is there any composer in the
>history of the world who has ever called
>|Are slurs between the grace note and the next one absolutely necessary ?
>|According to CPE Bach a grace note is always slurred to the next one.
I must confess that in my arrangements, I usually omit
slurs on appoggiaturas but there is the danger that
literal-minded musicians who are used to
>|it is evident that the \crescendo is not at all
>|vertically at the middle of the staff although it is
>|within the \zmidstaff macro: in faith, it is a little
>|below. Why?
Rodolfo: \zmidstaff is designed for *text* (like p), not
arbitrary symbols with unpredictable vertical extents.
Bob
>|> Rodolfo: \zmidstaff is designed for *text* (like p),
>|> not arbitrary symbols with unpredictable vertical
>|> extents.
>|
>|Thank you, Bob, I'm learning now what you say, but
>|on p.53 of my copy of MusiXTeX manual it says that
>|\crescendo should be used as argument of \zcharnote,
>|Did something inadvertent happen to \doublebar in the
>|most recent update? Some files that use that command were
>|working prior to the upgrade, but now that command is
>|throwing an error: Undefined control sequence.
Hi. I can't replicate that issue. PLease send me a minimal
example (and
ctan.org and we hope it will be adopted by
TeXLive-2021. Thanks to Mike Spivey for his assistance
in preparing this release.
http://icking-music-archive.org/software/xml2pmx/xml2pmx.zip
http://icking-music-archive.org/software/musixtex/musixtex.lua
Bob Tennent
---
TeX
>|> I'm very puzzled why " cd22xT20 g" didn't work for you because it
>|did work
>|> for me (using PMX 2.94).
>|
>|Hi, Don, thank you. I'm using PMX 2.94 too. Maybe it is musixtex
>|version?
>|Mine are:
>|
>| This is musixtex.lua version 0.21.
>| This is PMX, Version 2.94 , 17 Mar 20
-2.94a.zip
Bob T.
On Thu, Jan 28, 2021 at 1:56 PM Bob Tennent wrote:
> Hi Kalvin. That changes the diagnosis. I had assumed from a message Don
> sent me that the problem
> was in the Windows executables in the archive. But after further testing
> I see that scor2prt in TeXLive
> is s
>|When I need to compile a new PMX release I've been using gfortran for a
>|while since f2c caused trouble.
Hi Christian. I use the following Makefile:
all: pmxab.c scor2prt.c
pmxab.c: pmx294.for
f2c -g -\!bs < pmx294.for > pmxab.c
scor2prt.c: scor2prt.for
f2c -g -\!bs <
> I recall some interactions a while back where I needed
> to make some changes in the PMX FORTRAN to make it more
> compatible with something, but I'd have to do some real
> digging to find the details. I also don't recall whether
> I made those same kinds of changes in scor2prt. I'm
> pretty
>|I suppose you could try replacing that statement with the more
>|conventional
>|form:
>|
>| write(*,'(a33,i3,a26)')'33H Any whole-bar rests of duration',lenbar,
>| * '/64 will not be recognized'
This works if I use a sinle line:
write(*,'(a33,i3,a26)')'33H Any whole-bar
> $
>
> Now that I re-read your reply, I get the sense that you're talking about
> TeX on Windows; I'm running Fedora 33, so I don't interact with those.
>
> Thank you for looking into the issue!
>
> Kalvin
>
> On 1/28/21 7:00 AM, Bob Tennent wrote:
> > Kalvin: Th
>|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
t;|> we're now discussing with beams. Wouldn't it be great
>|> if someone (with a lot more MusiXTeX and postscript
>|> knowledge that I have) were to create such a package
>|> for beams?
>|>
>|> --Don
>|>
>|> > -Original Message- From: TeX-Music
re sources.
Thanks Hiroaki.
Best,
Bob T.
>|- Original Message -
>|> From: Bob Tennent
>|> Date: Thu, 13 May 2021 08:42:25 -0400
>|> To: Hiroaki MORIMOTO
>|> Cc: Werner Icking Music Archive
>|> Subject: Re: Re: [Tex-music] strange beam discontinui
I've released version 1.32 of MusiXTeX. It provides
a new add-on package musixvbm by Hiroaki Morimoto to
support vectorized beams and corrects two minor issues in
musixtex.tex.
http://icking-music-archive.org/software/musixtex/musixtex132.zip
>|I've noticed that the scores I now make using
>|PMX/MusiXTeX are not centered by default the same way
>|they've been in the past. The problem is both vertical
>|and horizontal. I'm pretty sure the change was not in
>|PMX, since when I reprocess old .tex files that used to
>|come out
>|I found empirically that \hoffset=-28pt centers the
>|example, and that number agrees with Bob's formula. I
>|suppose I can use that as a bandaid going forward.
The advantage of using the "formula" in your set-up is that
you can vary the \hsize and \vsize values without having to
recalculate
>|> Perhaps your TeX configuration has changed from letter
>|> paper to A4?
>|>
>|Bob, first of all, thanks so much for your prompt replies. What you
>|suggested could be the problem, but I'm still not sure. Here's what
>|I know.
>|By default, PMX sets \vsize and \hsize for letter, and no
I've had reports that musixvbm generates beams with
misaligned note stems. See the attached. However, I can't
reproduce this on my system. If you can on the attached
source file, please let me know what versions of musixtex
and dvips you are using.
Bob Tennent
strangebeam.tex
Description: TeX
>|Jean-Pierre: If I increase the zoom to 500%, I can see a
>|discontinuity using the most recent dvips but it's less
>|pronounced.
And if I zoom into the dvi, I see the same discontinuity. So
the problem *is* in musixtex but can be exacerbated by an
old dvips. Sigh.
Bob
>|Does everybody see a gap between J and F and an overlap between M and L in
>|the 16th notes?
>|
>|The problem in the same in the PostScript file but it is not present
>|in the
>|dvi file.
Jean-Pierre: There is a discontinuity between L and M in
your PDF (generated using dvips from 2013)
Jean-Pierre: If I increase the zoom to 500%, I can see a
discontinuity using the most recent dvips but it's less
pronounced.
Bob
---
TeX-music@tug.org mailing list
If you want to unsubscribe or look at the archives, go to
https://tug.org/mailman/listinfo/tex-music
>|Processed in my environment
>|
>|Linux Mint 20.1
>|TeXLive 2021
>|PMX 2.94
>|MusiXTeX 1.32
>|Musixflx-0.83.3.lua7
>|
>|the score is clearly misaligned, see the attached .ps file
Christian: When you installed TeXLive 2021, did you set the
paper option to A4? Do you get different
>|It turns out there's already an option in PMX that causes
>|the proper offsets for letter size paper to be inserted
>|into the TeX file: Acl. Could you or Bob or both try
>|inserting that into centtest.pmx near the beginning and
>|checking? The numbers differ by 2 pt from what I had just
I believe that the majority of musixtex users convert
TeX output using dvips and that is the default in the
musixtex.lua script. But there are also users of dvipdfmx,
including many in Japan, presumably because it handles the
relevant fonts better than dvips. The musixtex script will
use dvipdfmx
>|dvips -e 0 foobar[.dvi]
>|
>|seems to be a solution.
>|(not be perfect but becomes rather better with this option)
Thanks Hiroaki. As it happens, -e0 has been added to the
"default" dvips call in the musixtex.lua script since 2015!
I not sure I ever knew why :+)
Bob T.
And it seems that the -e0 option has been recommended for
dvips on musixtex output for a very long time. See
Section 26.3 of musixdoc.pdf
Bottom-line:
If you don't use the musixtex.lua script, add -e0 as an
option to dvips to preclude the dvips "feature" (i.e.,
bug) of adjusting pixels
>|I can reproduce the misalignment on my system by using
>|
>| dvips -D 300
>|
>|(following a suggestion by Hiroaki). Using -D 600 (the
>|default resolution) does not produce misalignments.
On some systems the situation is reversed: -D 300 is good,
-D 600 is not. It seems -D 1200
he misalignment on my system by using
dvips -D 300
(following a suggestion by Hiroaki). Using -D 600 (the
default resolution) does not produce misalignments.
Bob Tennent
---
TeX-music@tug.org mailing list
If you want to unsubscribe or look at the archive
>|That will insert the necessary \hoffset and \voffset
>|commands into your TeX file, assuming you haven't altered
>|the printed width and height \hsize and \vsize from their
>|defaults.
TeX commands that will *calculate* the correct offsets for
*any* \hsize or \vsize can be found in Section
As a stopgap measure, I've released a new version of the
musixtex-fonts package. The only significant change is
that the widths of three glyphs in musixspx.pfb have been
adjusted to work around recent changes to dvipdfmx that
resulted in overly long horizontal dashed lines such as
octaviation
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
>|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 (/) ra
to generate notehead-less stems above a tablature
staff to specify note duration. Full details in
Section 18.10 of musixdoc.pdf.
http://icking-music-archive.org/software/musixtex/musixtex133.zip
http://icking-music-archive.org/software/musixtex/musixdoc.pdf
Bob Tennent
Thanks Christian. gfortran is indeed an alternative but
perhaps you need to be reminded why translation to C
is important: TeXLive won't accept Fortran (or Pascal
or Oberon) sources. So the reason PMX and M-Tx are
distributed in TeXLive and available without compilation
for all their supported
ly broken for now.
Sorry about this.
Bob Tennent
---
TeX-music@tug.org mailing list
If you want to unsubscribe or look at the archives, go to
https://tug.org/mailman/listinfo/tex-music
>|> In the case of scor2prt, an unusual and apparently
>|> obsolete format is being accepted by gfortran but has
>|> confused the most recent version of f2c. This has now
>|> been fixed and a corrected version of the pmx package
>|> has been uploaded to WIMA and CTAN. It will no doubt be
>|>
This will not remove "local" or "personal" additions,
provided you have not put them into the texmf-dist tree.
Bob Tennent
---
TeX-music@tug.org mailing list
If you want to unsubscribe or look at the archives, go to
https://tug.org/mailman/listinfo/tex-music
>|tug.org provides a search box atop the private view of the archives that
>|farms out queries to DuckDuckGo, e.g. searching "gliss" searches
>|DuckDuckGo for "gliss site:tug.org/pipermail/TeX-Music."
>|
>|The problem is that this never turns up results ??? seems that
>| The WIMA home page is up-and-running again
Thanks Christian.
Bob T.
---
TeX-music@tug.org mailing list
If you want to unsubscribe or look at the archives, go to
https://tug.org/mailman/listinfo/tex-music
This web site appears to be inoperative. But
http://icking-music-archive.org/software/
and
http://icking-music-archive.org/software/htdocs
are OK.
Bob T.
---
TeX-music@tug.org mailing list
If you want to unsubscribe or look at the archives, go to
>|Perfect, there's my backdoor in; thanks. I'm a bit surprised that this
>|dances neatly around the privacy settings of the whole list.
I think they don't reveal the e-mail addresses, which is likely the
intent of the "privacy" settings.
Bob T.
>|> Try
>|>
>|>
Early Music Sources provide a font that emulates 16th and 17th century music
publications. It is supposed to work in conventional word-processing
programs with ligatures enabled, but it should be possible to adapt it for
use with MusiXTeX. Let me know if this might be of interest to you.
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
> a
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
Christian Mondrup <
c...@icking-music-archive.org> wrote:
> Den 28.08.2021 kl. 15.01 skrev Bob Tennent:
> > Early Music Sources provide a font that emulates 16th and 17th century
> music
> > publications. It is supposed to work in conventional word-processing
> > p
See Section 5.7 of musixdoc.pdf.
Bob T.
On Mon, Oct 4, 2021 at 7:56 AM Rodolfo Medina
wrote:
> Hi all!
>
> In the following example, to be processed with simply:
>
> tex test
> musixlfx test
> tex test
>
> the double bar of the staff-crossing beam should be different from it is:
> the
>
> I can’t find any “add new file” links on that page
Near the top on the right-hand side directly across from 6 Concerts et 6
Suites (Telemann, Georg Philipp).
Bob
On Mon, Dec 27, 2021 at 8:04 PM wrote:
> I have typeset parts and scores for the flute+harpsichord versions of 3
> “concerts”
orm one
> of the 4 possible combinations that Telemann himself certified to play
> these trio sonatas, and he didn’t just slap together the bass line and the 2
> nd treble part but took the trouble to produce a complete, separate
> harpsichord part.
>
>
>
> --Don
>
>
>
>
gt; > -Original Message-
> > From: TeX-Music
> > On Behalf Of Christian Mondrup
> > Sent: Tuesday, December 28, 2021 7:20 AM
> > To: tex-music@tug.org
> > Subject: Re: [Tex-music] Uploading to IMSLP?
> >
> > Den 28.12.2021 kl. 13.37 skrev Bob
Hi Christian. Seems to be okay now. Thanks.
Bob
On Tue, Dec 7, 2021 at 5:58 AM Christian Mondrup <
c...@icking-music-archive.org> wrote:
> Den 07.12.2021 kl. 00.34 skrev dsim...@roadrunner.com:
> > Bob--
> >
> > When I try to access the Icking "archive" at
> >
> >
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
401 - 500 of 557 matches
Mail list logo
