diff options
author | Karl Berry <karl@freefriends.org> | 2011-11-05 23:40:54 +0000 |
---|---|---|
committer | Karl Berry <karl@freefriends.org> | 2011-11-05 23:40:54 +0000 |
commit | f9b4593f28389832c5573550b53b9e5569163cf8 (patch) | |
tree | 8486c13e5eeb51bccdd926bedd693096a9e0e17f /Master/texmf-dist/doc/generic | |
parent | 2632cfd91ace0a6428f33d057fb0c51e23fbab76 (diff) |
musixtex 10-26-2011 (27oct11)
git-svn-id: svn://tug.org/texlive/trunk@24518 c570f23f-e606-0410-a88d-b1316a301751
Diffstat (limited to 'Master/texmf-dist/doc/generic')
-rw-r--r-- | Master/texmf-dist/doc/generic/musixtex/ChangeLog | 25 | ||||
-rw-r--r-- | Master/texmf-dist/doc/generic/musixtex/README | 84 | ||||
-rw-r--r-- | Master/texmf-dist/doc/generic/musixtex/gpl.txt | 251 | ||||
-rw-r--r-- | Master/texmf-dist/doc/generic/musixtex/musixtex-install.pdf | bin | 0 -> 94387 bytes | |||
-rw-r--r-- | Master/texmf-dist/doc/generic/musixtex/musixtex-install.tex | 170 | ||||
-rw-r--r-- | Master/texmf-dist/doc/generic/musixtex/psfonts/CHANGES.psfonts | 34 | ||||
-rw-r--r-- | Master/texmf-dist/doc/generic/musixtex/psfonts/README.psfonts | 114 |
7 files changed, 530 insertions, 148 deletions
diff --git a/Master/texmf-dist/doc/generic/musixtex/ChangeLog b/Master/texmf-dist/doc/generic/musixtex/ChangeLog new file mode 100644 index 00000000000..7d588009ee2 --- /dev/null +++ b/Master/texmf-dist/doc/generic/musixtex/ChangeLog @@ -0,0 +1,25 @@ +2011-10-23 All font-related files moved to a new package musixtex-fonts, + which obsoletes musixtex-t1fonts. +2011-06-27 Small revisions to the README. Moved the scripts documentation + to doc/generic/musixtex/scripts +2011-05-21 Augmented the musixtex.lua script to allow multiple filenames, + and added -l (latex) and -f (default) options. +2011-04-25 Rainer Dunker patch to curly.tex; Mthimkhulu Molekwa e-mail updated; + added options to musixtex.lua +2011-04-19 replaced musixflx.c by musixflx.lua and musixtex.sh by musixtex.lua +2011-04-04 added musixtex scripts to run etex && musixflx && etex && dvips && ps2pdf +2011-04-03 updated musixtex.tex to version 1.15 (T-115) +2010-12-18 "universal" OS-X binary for musixflx +2010-11-28 added Joel Hunsberger as an author of musixflx.c +2010-11-10 added font-map configuration to musixtex-install; + updated mail-list info +2010-11-07 moved musixcrd.tex from doc to tex +2010-11-05 psslurs re-licensed to GPL +2010-11-02 musixcrd source files added +2010-11-01 underbracket.sty etc. moved to doc +2010-10-26 added tests and improved the error message for + version-incompatibility in musixflx +2010-10-18 first version of musixflx-0.83.2 +2010-09-28 type 1 font for mxsk added to psfonts and musix.map +2010-09-27 musixflx.c GPLed + diff --git a/Master/texmf-dist/doc/generic/musixtex/README b/Master/texmf-dist/doc/generic/musixtex/README new file mode 100644 index 00000000000..b319fd5f376 --- /dev/null +++ b/Master/texmf-dist/doc/generic/musixtex/README @@ -0,0 +1,84 @@ +This is MusiXTeX, version 1.15 (packaged 2011-10-23). MusiXTeX is a +TeX-based system for typesetting music. + +The main author was Daniel Taupin, who died in a climbing accident in +2003; other authors credited in the MusiXTeX manual are Andreas Egler +and Ross Mitchell. MusiXTeX is now being maintained by + +Don Simons dsimons(at)roadrunner(dot)com +Hiroaki Morimoto CQX05646(at)nifty(dot)com + +The package consists of + +musixtex-texmf.zip, which contains macros, documentation and +support files, including + + + Postscript slur support, due to Stanislav Kneifl + + + musixlyr support for lyrics, due to Rainer Dunker + + + musixcrd support for chord symbols, due to Robert Hennig + + + a few small extension packages (curly, tuplet, underbracket) + + + a script musixflx.lua for the 2nd-pass processing + + + a script musixtex.lua that automates the 3-pass + etex -> musixflx -> [pdf]etex process, + possibly followed by calls to dvips and ps2pdf (or dvipdfm) + to convert the output to Portable Document Format (PDF) + + + wrapper scripts musixflx.bat and musixtex.bat for use on Windows + +MusiXTeX fonts, including both the original metafont sources and Type 1 +versions by Takanori Uchiyama are in a separate musixtex-fonts package, +which must be installed before using the MusiXTeX macros. + +musixtex-install.{pdf,tex} is a more-detailed version of the following +instructions: + +To install (on TDS-compliant TeX systems): + + + unzip musixtex-texmf.zip at the root of a texmf tree and, if + necessary, update the filename database; e.g., texhash texmf. + + + on Windows: move the scripts in scripts\musixtex\Windows to a folder + on the executable PATH (or add that folder to the PATH) + + + on any Unix-like system: install symbolic links musixflx + and musixtex in a directory on the executable PATH to + scripts/musixtex/musixflx.lua and scripts/musixtex/musixtex.lua, + respectively. + +Documentation for MusiXTeX and friends is installed under + +doc/generic/musixtex + +Documentation for the musixflx and musixtex scripts are in + +doc/generic/musixtex/scripts + +Check out musixtex-install.pdf for information on the extension +packages, which are installed under + +doc/generic/musixtex/addons + +Many users, especially beginners, will find it easier to use the PMX and +M-Tx pre-processors, which accept a simpler input language than MusiXTeX +itself. These pre-processor packages may be found at CTAN under support. +Additional documentation, additional add-on packages, and many examples +of MusiXTeX typesetting may be found at the Werner Icking Music Archive +at + +http://icking-music-archive.org/ + +Support for users of MusiXTeX and related software may be obtained via +the MusiXTeX mail list at + +http://tug.org/mailman/listinfo/tex-music + +MusiXTeX may be freely copied, duplicated and used in conformance to the +GNU General Public License (Version 2, 1991, see included file gpl.txt). + +This CTAN distribution is maintained by Bob Tennent +rdt(at)cs(dot)queensu(dot)ca. diff --git a/Master/texmf-dist/doc/generic/musixtex/gpl.txt b/Master/texmf-dist/doc/generic/musixtex/gpl.txt new file mode 100644 index 00000000000..8de98afaaf9 --- /dev/null +++ b/Master/texmf-dist/doc/generic/musixtex/gpl.txt @@ -0,0 +1,251 @@ + + GNU GENERAL PUBLIC LICENSE + Version 1, February 1989 + + Copyright (C) 1989 Free Software Foundation, Inc. + 51 Franklin St, Fifth Floor, Boston, MA 02110-1301 USA + + Everyone is permitted to copy and distribute verbatim copies + of this license document, but changing it is not allowed. + + Preamble + + The license agreements of most software companies try to keep users +at the mercy of those companies. By contrast, our General Public +License is intended to guarantee your freedom to share and change free +software--to make sure the software is free for all its users. The +General Public License applies to the Free Software Foundation's +software and to any other program whose authors commit to using it. +You can use it for your programs, too. + + When we speak of free software, we are referring to freedom, not +price. Specifically, the General Public License is designed to make +sure that you have the freedom to give away or sell copies of free +software, that you receive source code or can get it if you want it, +that you can change the software or use pieces of it in new free +programs; and that you know you can do these things. + + To protect your rights, we need to make restrictions that forbid +anyone to deny you these rights or to ask you to surrender the rights. +These restrictions translate to certain responsibilities for you if you +distribute copies of the software, or if you modify it. + + For example, if you distribute copies of a such a program, whether +gratis or for a fee, you must give the recipients all the rights that +you have. You must make sure that they, too, receive or can get the +source code. And you must tell them their rights. + + We protect your rights with two steps: (1) copyright the software, and +(2) offer you this license which gives you legal permission to copy, +distribute and/or modify the software. + + Also, for each author's protection and ours, we want to make certain +that everyone understands that there is no warranty for this free +software. If the software is modified by someone else and passed on, we +want its recipients to know that what they have is not the original, so +that any problems introduced by others will not reflect on the original +authors' reputations. + + The precise terms and conditions for copying, distribution and +modification follow. + + GNU GENERAL PUBLIC LICENSE + TERMS AND CONDITIONS FOR COPYING, DISTRIBUTION AND MODIFICATION + + 0. This License Agreement applies to any program or other work which +contains a notice placed by the copyright holder saying it may be +distributed under the terms of this General Public License. The +"Program", below, refers to any such program or work, and a "work based +on the Program" means either the Program or any work containing the +Program or a portion of it, either verbatim or with modifications. Each +licensee is addressed as "you". + + 1. You may copy and distribute verbatim copies of the Program's source +code as you receive it, in any medium, provided that you conspicuously and +appropriately publish on each copy an appropriate copyright notice and +disclaimer of warranty; keep intact all the notices that refer to this +General Public License and to the absence of any warranty; and give any +other recipients of the Program a copy of this General Public License +along with the Program. You may charge a fee for the physical act of +transferring a copy. + + 2. You may modify your copy or copies of the Program or any portion of +it, and copy and distribute such modifications under the terms of Paragraph +1 above, provided that you also do the following: + + a) cause the modified files to carry prominent notices stating that + you changed the files and the date of any change; and + + b) cause the whole of any work that you distribute or publish, that + in whole or in part contains the Program or any part thereof, either + with or without modifications, to be licensed at no charge to all + third parties under the terms of this General Public License (except + that you may choose to grant warranty protection to some or all + third parties, at your option). + + c) If the modified program normally reads commands interactively when + run, you must cause it, when started running for such interactive use + in the simplest and most usual way, to print or display an + announcement including an appropriate copyright notice and a notice + that there is no warranty (or else, saying that you provide a + warranty) and that users may redistribute the program under these + conditions, and telling the user how to view a copy of this General + Public License. + + d) You may charge a fee for the physical act of transferring a + copy, and you may at your option offer warranty protection in + exchange for a fee. + +Mere aggregation of another independent work with the Program (or its +derivative) on a volume of a storage or distribution medium does not bring +the other work under the scope of these terms. + + 3. You may copy and distribute the Program (or a portion or derivative of +it, under Paragraph 2) in object code or executable form under the terms of +Paragraphs 1 and 2 above provided that you also do one of the following: + + a) accompany it with the complete corresponding machine-readable + source code, which must be distributed under the terms of + Paragraphs 1 and 2 above; or, + + b) accompany it with a written offer, valid for at least three + years, to give any third party free (except for a nominal charge + for the cost of distribution) a complete machine-readable copy of the + corresponding source code, to be distributed under the terms of + Paragraphs 1 and 2 above; or, + + c) accompany it with the information you received as to where the + corresponding source code may be obtained. (This alternative is + allowed only for noncommercial distribution and only if you + received the program in object code or executable form alone.) + +Source code for a work means the preferred form of the work for making +modifications to it. For an executable file, complete source code means +all the source code for all modules it contains; but, as a special +exception, it need not include source code for modules which are standard +libraries that accompany the operating system on which the executable +file runs, or for standard header files or definitions files that +accompany that operating system. + + 4. You may not copy, modify, sublicense, distribute or transfer the +Program except as expressly provided under this General Public License. +Any attempt otherwise to copy, modify, sublicense, distribute or transfer +the Program is void, and will automatically terminate your rights to use +the Program under this License. However, parties who have received +copies, or rights to use copies, from you under this General Public +License will not have their licenses terminated so long as such parties +remain in full compliance. + + 5. By copying, distributing or modifying the Program (or any work based +on the Program) you indicate your acceptance of this license to do so, +and all its terms and conditions. + + 6. Each time you redistribute the Program (or any work based on the +Program), the recipient automatically receives a license from the original +licensor to copy, distribute or modify the Program subject to these +terms and conditions. You may not impose any further restrictions on the +recipients' exercise of the rights granted herein. + + 7. The Free Software Foundation may publish revised and/or new versions +of the General Public License from time to time. Such new versions will +be similar in spirit to the present version, but may differ in detail to +address new problems or concerns. + +Each version is given a distinguishing version number. If the Program +specifies a version number of the license which applies to it and "any +later version", you have the option of following the terms and conditions +either of that version or of any later version published by the Free +Software Foundation. If the Program does not specify a version number of +the license, you may choose any version ever published by the Free Software +Foundation. + + 8. If you wish to incorporate parts of the Program into other free +programs whose distribution conditions are different, write to the author +to ask for permission. For software which is copyrighted by the Free +Software Foundation, write to the Free Software Foundation; we sometimes +make exceptions for this. Our decision will be guided by the two goals +of preserving the free status of all derivatives of our free software and +of promoting the sharing and reuse of software generally. + + NO WARRANTY + + 9. BECAUSE THE PROGRAM IS LICENSED FREE OF CHARGE, THERE IS NO WARRANTY +FOR THE PROGRAM, TO THE EXTENT PERMITTED BY APPLICABLE LAW. EXCEPT WHEN +OTHERWISE STATED IN WRITING THE COPYRIGHT HOLDERS AND/OR OTHER PARTIES +PROVIDE THE PROGRAM "AS IS" WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESSED +OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF +MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. THE ENTIRE RISK AS +TO THE QUALITY AND PERFORMANCE OF THE PROGRAM IS WITH YOU. SHOULD THE +PROGRAM PROVE DEFECTIVE, YOU ASSUME THE COST OF ALL NECESSARY SERVICING, +REPAIR OR CORRECTION. + + 10. IN NO EVENT UNLESS REQUIRED BY APPLICABLE LAW OR AGREED TO IN WRITING +WILL ANY COPYRIGHT HOLDER, OR ANY OTHER PARTY WHO MAY MODIFY AND/OR +REDISTRIBUTE THE PROGRAM AS PERMITTED ABOVE, BE LIABLE TO YOU FOR DAMAGES, +INCLUDING ANY GENERAL, SPECIAL, INCIDENTAL OR CONSEQUENTIAL DAMAGES ARISING +OUT OF THE USE OR INABILITY TO USE THE PROGRAM (INCLUDING BUT NOT LIMITED +TO LOSS OF DATA OR DATA BEING RENDERED INACCURATE OR LOSSES SUSTAINED BY +YOU OR THIRD PARTIES OR A FAILURE OF THE PROGRAM TO OPERATE WITH ANY OTHER +PROGRAMS), EVEN IF SUCH HOLDER OR OTHER PARTY HAS BEEN ADVISED OF THE +POSSIBILITY OF SUCH DAMAGES. + + END OF TERMS AND CONDITIONS + + Appendix: How to Apply These Terms to Your New Programs + + If you develop a new program, and you want it to be of the greatest +possible use to humanity, the best way to achieve this is to make it +free software which everyone can redistribute and change under these +terms. + + To do so, attach the following notices to the program. It is safest to +attach them to the start of each source file to most effectively convey +the exclusion of warranty; and each file should have at least the +"copyright" line and a pointer to where the full notice is found. + + <one line to give the program's name and a brief idea of what it does.> + Copyright (C) 19yy <name of author> + + This program is free software; you can redistribute it and/or modify + it under the terms of the GNU General Public License as published by + the Free Software Foundation; either version 1, or (at your option) + any later version. + + This program is distributed in the hope that it will be useful, + but WITHOUT ANY WARRANTY; without even the implied warranty of + MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the + GNU General Public License for more details. + + You should have received a copy of the GNU General Public License + along with this program; if not, write to the Free Software + Foundation, Inc., 51 Franklin Street, Fifth Floor, Boston MA 02110-1301 USA + + +Also add information on how to contact you by electronic and paper mail. + +If the program is interactive, make it output a short notice like this +when it starts in an interactive mode: + + Gnomovision version 69, Copyright (C) 19xx name of author + Gnomovision comes with ABSOLUTELY NO WARRANTY; for details type `show w'. + This is free software, and you are welcome to redistribute it + under certain conditions; type `show c' for details. + +The hypothetical commands `show w' and `show c' should show the +appropriate parts of the General Public License. Of course, the +commands you use may be called something other than `show w' and `show +c'; they could even be mouse-clicks or menu items--whatever suits your +program. + +You should also get your employer (if you work as a programmer) or your +school, if any, to sign a "copyright disclaimer" for the program, if +necessary. Here a sample; alter the names: + + Yoyodyne, Inc., hereby disclaims all copyright interest in the + program `Gnomovision' (a program to direct compilers to make passes + at assemblers) written by James Hacker. + + <signature of Ty Coon>, 1 April 1989 + Ty Coon, President of Vice + +That's all there is to it! diff --git a/Master/texmf-dist/doc/generic/musixtex/musixtex-install.pdf b/Master/texmf-dist/doc/generic/musixtex/musixtex-install.pdf Binary files differnew file mode 100644 index 00000000000..08fc01aae49 --- /dev/null +++ b/Master/texmf-dist/doc/generic/musixtex/musixtex-install.pdf diff --git a/Master/texmf-dist/doc/generic/musixtex/musixtex-install.tex b/Master/texmf-dist/doc/generic/musixtex/musixtex-install.tex new file mode 100644 index 00000000000..2375565aa5c --- /dev/null +++ b/Master/texmf-dist/doc/generic/musixtex/musixtex-install.tex @@ -0,0 +1,170 @@ +\documentclass[11pt]{article} +\usepackage[textwidth=6.5in,textheight=8.5in]{geometry} +\usepackage[osf]{mathpazo} +\usepackage{textcomp} +\PassOptionsToPackage{urlcolor=black,colorlinks}{hyperref} +\RequirePackage{hyperref} +\usepackage{xcolor} +\newcommand{\myurl}[1]{\textcolor{blue}{\underline{\textcolor{black}{\url{#1}}}}} +\newcommand{\musixflxVersion}{0.83.3} +\begin{document} +\title{Installation of the CTAN MusiXTeX Distribution} +\author{Bob Tennent\\ +\small\url{rdt@cs.queensu.ca}} +\date{\today} +\maketitle +\thispagestyle{empty} + +\section{Introduction} +Before trying to install from CTAN, check whether your TeX distribution +provides packages for MusiXTeX; this will be easier than doing it yourself. +But if your TeX distribution +doesn't have MusiXTeX (or doesn't have the most recent version), this distribution +of MusiXTeX is very easy to install, though +you may need to read the material on +installation of (La)TeX files in the +TeX FAQ\footnote{% +\myurl{http://www.tex.ac.uk/cgi-bin/texfaq2html}}, +particularly +the pages on +which tree to use\footnote{% +\myurl{http://www.tex.ac.uk/cgi-bin/texfaq2html?label=what-TDS}} +and installing files\footnote{% +\myurl{http://www.tex.ac.uk/cgi-bin/texfaq2html?label=inst-wlcf}}. + +\section{Installing \texttt{musixtex-texmf.zip}} + +In this distribution of MusiXTeX, most of the files to be installed +(including macros, scripts, and documentation) are in +\texttt{musixtex-texmf.zip}, a zipped TEXMF +hierarchy. Simply unzip this archive in the root folder/directory of whichever TEXMF tree +you decide is most appropriate, likely a ``local'' or ``personal'' one. +This should work with any TDS\footnote{% +\myurl{http://www.tex.ac.uk/cgi-bin/texfaq2html?label=tds}} +compliant TeX distribution, including MikTeX, TeXlive and teTeX. + +After unzipping the archive, update the filename database as necessary, +for example, by executing \verb\texhash ~/texmf\ or +clicking the button labelled ``Refresh FNDB" in the MikTeX settings program. + +MusiXTeX requires a large set of specialized fonts. If necessary, install the +\texttt{musixtex-fonts} package. + +You should now be able to process files that use the MusiXTeX macros using +\verb\etex\ or \verb\pdfetex\; +documentation for MusiXTeX is installed under \verb\.../doc/generic/musixtex...\ +in the TEXMF tree. But the music will be ``squeezed'' to the left; to produce +proper spacing, go on. + +\section{Installing \texttt{musixflx}} + +The next step in the installation is to install +the one crucial file that can't be installed in a TEXMF tree: a \texttt{musixflx} executable, which calls +the script that implements +the second pass of the three-pass MusiXTeX typesetting system described in Section~1.3 of the +MusiXTeX manual (\verb\musixdoc.pdf\). In this MusiXTeX package, the +calculations are done by a Lua script +\begin{list}{}{} +\item \verb|.../scripts/musixtex/musixflx.lua| +\end{list} +On a Unix-like system (with \texttt{luatex} installed), you can put a +symbolic link to \texttt{musixflx.lua} in any directory on the executable PATH as follows: +\begin{list}{}{} +\item \verb\ln -s <path to musixflx.lua> musixflx\ +\end{list} +On Windows, you can \emph{either} +copy the batch file +\begin{list}{}{} +\item \verb|...\scripts\musixtex\Windows\musixflx.bat| +\end{list} +to a folder +on the executable PATH \emph{or} add the folder +\verb|...\scripts\musixtex\Windows| to the executable PATH +as follows: +in ``My Computer'' +click on +\begin{center} +View System Information\quad$\rightarrow$\quad Advanced\quad$\rightarrow$\quad Environment Variables +\end{center} +scroll +down to ``path'', select it, click edit, and add the path to \verb|...\scripts\musixtex\Windows| after a semi-colon. +Documentation for \verb\musixflx\ is in the \verb\doc/generic/musixtex/scripts\ directory. + +\section{Installing \texttt{musixtex}} + +The Lua script \verb\.../scripts/musixtex/musixtex.lua\ +is simply a convenient wrapper that, by default, +runs the following processes in order (and then deletes intermediate files): +\begin{itemize}\topsep=0pt\itemsep=0pt +\item \verb\etex\ (1st pass) +\item \verb\musixflx\ (2nd pass) +\item \verb\etex\ (3rd pass) +\item \verb\dvips\ (to convert \verb\dvi\ output to Postscript) +\item \verb\ps2pdf\ (to convert \verb\ps\ output to Portable Document Format) +\end{itemize}% +To install, follow the instructions given in the preceding section; i.e., +on Unix-like systems, +install a symbolic link \verb\musixtex\; on Windows, +ensure that the corresponding batch file +is in a folder on the executable PATH. Documentation is in the +\verb\doc/generic/musixtex/scripts\ directory. + +If the \verb\musixps.tex\ package is not used to produce slurs, it is possible to use \verb\pdfetex\ +rather than \verb\etex\, in which case a PDF file will be produced directly, +without the use of \verb\dvips\ and \verb\ps2pdf\; use the \verb\-p\ option in the call to \verb\musixtex\. +The \verb\-d\ option will replace \verb\dvips\ and \verb\ps2pdf\ by \verb\dvipdfm\; again, +this option is usable only if Postscript slurs are \emph{not} used. Use the \verb\-s\ option +to stop processing after the third pass; i.e., at the \verb\dvi\ file. +Use the \verb\-l\ option for \verb\LaTeX\ processing and the \verb\-f\ option to restore the defaults for subsequent files. + +The cross-platform TeXWorks editing environment can +be configured +to use the relevant \verb\musixtex\ script as a typesetting process as follows: +\begin{center} +Edit\quad$\rightarrow$\quad Preferences\quad$\rightarrow$\quad Typesetting +\end{center} +then click on + to add a new processing tool as follows: +\begin{description}\itemsep=0pt +\item[Name:] \verb\musixtex\ +\item[Program:] \verb\musixtex\ +\item[Arguments:] \verb\$basename\ +\end{description} +If necessary, add the path to the directory/folder containing the \verb\musixtex\ +script to the list of Paths for TeX and related programs. + +\section{Addons} + +Unzipping \verb\musixtex-texmf.zip\ will install into +\verb\doc/generic/musixtex/addons/\ +several small packages which extend the capabilities of +MusiXTeX: +\begin{center} +\begin{tabular}{lll} +\verb\curly.tex\ & multiple left curly brackets & by Mthimkhulu Molekwa \\ +\verb\tuplet.tex\ & conventional tuplet brackets & by Col. G. L. Sicherman\\ +\verb\underbracket.sty\ & brackets to underline text& by Bernd Jantzen\\ +\end{tabular} +\end{center} +Check out the +documentation in \verb\musixdoc.pdf\ and in the comments of +the files. +If you want to use any of these packages, you'll have to copy them +to a place where TeX can find them, such as your working directory +or the \verb\tex/generic/musixtex\ sub-directory of the TEXMF tree +where \verb\musixtex-texmf.zip\ was installed. + + +\section{Discussion} +Many users, especially beginners, will find it easier to use the PMX and +M-Tx pre-processors, which accept a simpler input language than MusiXTeX +itself. These pre-processor packages may be found at CTAN under \verb\support\. Additional documentation, additional +add-on packages, and many examples of MusiXTeX typesetting may be found +at the Werner Icking Music Archive\footnote{% +\myurl{http://icking-music-archive.org}}. +Support for users of MusiXTeX and related software may be obtained via +the MusiXTeX mail list\footnote{% +\myurl{http://tug.org/mailman/listinfo/tex-music}}. +MusiXTeX may be freely copied, duplicated and used in conformance to the +GNU General Public License (Version~2, 1991, see included file \verb\gpl.txt\). + +\end{document} diff --git a/Master/texmf-dist/doc/generic/musixtex/psfonts/CHANGES.psfonts b/Master/texmf-dist/doc/generic/musixtex/psfonts/CHANGES.psfonts deleted file mode 100644 index 47ef978a546..00000000000 --- a/Master/texmf-dist/doc/generic/musixtex/psfonts/CHANGES.psfonts +++ /dev/null @@ -1,34 +0,0 @@ - PostScript (Type 1) Fonts for MusiXTeX - Ver 1.14 - - 28-September-2010 - - Takanori Uchiyama, uchiyama@appi.keio.ac.jp - -28-September-2010 - + Augment mxsk from slur-ps package. - -19-February-2003 - + Fix a problem that xslz20 disappears with Acrobat 5. - -15-July-2002 - + Fix broken fonts, xslhd11, xslhd11d, xslhd13, xslhd13d, xslhd16d, - xslhd24, xslhd29d. - -28-August-2001 - + Fix wrong width of musix13.pfb. - + Fix wrong width of xslhu11-29 and xslhu11d-29d. - -30-July-2001 - + Reducing control points. - + Hinted automatically with Fontographer. - + Upgrade from T101 to T102 (musix11 - 29, xslhz20, xslhz20d) - + PostScript names were changed. - Ex. TeX-musix20 --> TeXMUSIX20-Regular - + typo correction. - musix.tex --> musix.map - -13-July-2001 - + First release. - -[End of CHANGES] diff --git a/Master/texmf-dist/doc/generic/musixtex/psfonts/README.psfonts b/Master/texmf-dist/doc/generic/musixtex/psfonts/README.psfonts deleted file mode 100644 index 24c14c70735..00000000000 --- a/Master/texmf-dist/doc/generic/musixtex/psfonts/README.psfonts +++ /dev/null @@ -1,114 +0,0 @@ - PostScript (Type 1) Fonts for MusiXTeX - Ver 1.14 - - 28-September-2010 - - Takanori Uchiyama, uchiyama@appi.keio.ac.jp - -1. DESCRIPTION - -This package provides PostScript (type 1) fonts (PFB format), and dvips and -dvipdfm map files for MusiXTeX. The fonts are based on the original METAFONT -sources, such as musix20.mf, which are distributed with MusiXTeX. The fonts -provided here may be used to produce printer-independent Postscript files. PDF -files generated using type 1 fonts are well displayed by the Adobe Reader and -xpdf. - -The most of fonts were generated from the METAFONT sources in the TeX Live -CD 2000 July using TeXtrace 0.45 or mftrace 1.0.12 but musix11-20, xslhz20 -and xslhz20d were upgraded to those in musixtex-T102.tar.gz. -mxsk was generated from the METAFONT source in slur-ps package using mftrace -1.2.16. - -Here is a list of the 72 generated fonts. - -musix11.pfb xgreg24.pfb xsld29.pfb xslhd24.pfb xslhu24.pfb xslu20.pfb -musix13.pfb xgreg29.pfb xsld29d.pfb xslhd24d.pfb xslhu24d.pfb xslu20d.pfb -musix16.pfb xsld11.pfb xsldd20.pfb xslhd29.pfb xslhu29.pfb xslu24.pfb -musix20.pfb xsld11d.pfb xsldu20.pfb xslhd29d.pfb xslhu29d.pfb xslu24d.pfb -musix24.pfb xsld13.pfb xslhd11.pfb xslhu11.pfb xslhz20.pfb xslu29.pfb -musix29.pfb xsld13d.pfb xslhd11d.pfb xslhu11d.pfb xslhz20d.pfb xslu29d.pfb -musixsps.pfb xsld16.pfb xslhd13.pfb xslhu13.pfb xslu11.pfb xslud20.pfb -musixspx.pfb xsld16d.pfb xslhd13d.pfb xslhu13d.pfb xslu11d.pfb xslup20.pfb -xgreg11.pfb xsld20.pfb xslhd16.pfb xslhu16.pfb xslu13.pfb xslz20.pfb -xgreg13.pfb xsld20d.pfb xslhd16d.pfb xslhu16d.pfb xslu13d.pfb xslz20d.pfb -xgreg16.pfb xsld24.pfb xslhd20.pfb xslhu20.pfb xslu16.pfb xtie20.pfb -xgreg20.pfb xsld24d.pfb xslhd20d.pfb xslhu20d.pfb xslu16d.pfb -mxsk.pfb - -Note: musix25 and xgreg25 were not generated because they are not used in - musixgre.tex or musixtex.tex. - - -The control points were reduced with Fontographer. -The fonts were hinted automatically with Fontographer. musix11 - 29 were -hand tuned by Takanori Uchiyama. - -2. METHOD - -Most of fonts were generated using TeXtrace 0.45 running on Mac OS X 10.0.4. -xslz20 was generated using mftrace 1.0.12 running on Mac OS X 10.2.3. -mxsk was generated using mftrace 1.2.16 running on Mac OS X 10.6.4. -Thirty-two fonts were generated with the original traceall.sh script. Others -were generated with traceall.sh modified by Takanori Uchiyama. The modification -involved reducing resolution, corresponding to enlargement of "1 thou" in -traceall.sh. The following are lists of fonts that were generated with N-fold -thou scripts. - -twofold - musix11, musix13, xsld11, xsld11d, xsld13, xsld13d, xsld16, xsld16d, - xslhd13, xslhd13d, xslhd16, xslhd16d, xslhd20, xslhd20d, xslhd24d, - xslhu13, xslhu13d, xslhu16, xslhu16d, xslhu20, xslhu20d, xslhu24d, - xslu13, xslu13d, xslu16, xslu16d, xslud20 - -threefold - musixsps, musixspx, xslhd11, xslhd11d, xslhu11, xslhu11d, xslz20, xslz20d - -fivefold - xslhz20, xslhz20d, xtie20 - -The reason for reducing resolution is that METAFONT supports only limited -values of real numbers and so cannot generate very high resolution MusiXTeX -fonts. - -3. INSTALLATION - - 1) Make a directory such as $TEXMF/fonts/type1/musixtex, for PFBs. - 2) Copy all PFBs to the above directory; they should be readable by all users. - 3) Copy the map file ./dvips/musix.map to the appropriate directory, such as - $TEXMF/dvips/config - 4) Add a line - - p +musix.map - - to a suitable config.xxx file or, in a tetex-based distribution, add - musix.map to the list of map files for Type1 fonts with Metafont - equivalents in the updmap script, which should then be executed - by doing "./updmap". - 5) Do mktexlsr or texhash or whatever is necessary on your system to - re-generate the TeX database. - -Note: dvipdfm does not need a map file for these fonts because the PFBs' -names are identical to TFMs' names. - -When these fonts are used, type 1 fonts should also be used for non-music text; -for example, type 1 versions of the Computer Modern fonts are available. - -4. TODO - - + Hinting - + Modifying METAFONT sources to get high resolution outputs - -5. LICENSE - - The license of this package is LPPL. - -6. ACKNOWLEDGEMENTS - - Thanks to Dr. Daniel Taupin, Ross Mitchell and Andreas Egler for their -MusiXTeX package, to Dr. Peter Szabo for his excellent TeXtrace tool, -and to Dr. Han-Wen Nienhuys for his smart mftrace tool. -And thanks to Dr. Bob Tennent for his helpful comments, and to Mr. David -Fritzsche for his suggestions. - -[End of README] |