diff options
author | Karl Berry <karl@freefriends.org> | 2011-11-02 22:51:17 +0000 |
---|---|---|
committer | Karl Berry <karl@freefriends.org> | 2011-11-02 22:51:17 +0000 |
commit | 6f714441a5f4ecd5bc220e2f50cc98472bc079d0 (patch) | |
tree | c82791cc9234223333f0ad5ba4712aa7f0d4286f /Master/texmf-dist/doc/generic/FAQ-en/faq-adj-types.tex | |
parent | e5cd5f13085b6988a96d8e68ac5b703be949ad24 (diff) |
uk-tex-faq 3.24 (1nov11)
git-svn-id: svn://tug.org/texlive/trunk@24465 c570f23f-e606-0410-a88d-b1316a301751
Diffstat (limited to 'Master/texmf-dist/doc/generic/FAQ-en/faq-adj-types.tex')
-rw-r--r-- | Master/texmf-dist/doc/generic/FAQ-en/faq-adj-types.tex | 159 |
1 files changed, 91 insertions, 68 deletions
diff --git a/Master/texmf-dist/doc/generic/FAQ-en/faq-adj-types.tex b/Master/texmf-dist/doc/generic/FAQ-en/faq-adj-types.tex index 473d6d4b4dc..b03de85315d 100644 --- a/Master/texmf-dist/doc/generic/FAQ-en/faq-adj-types.tex +++ b/Master/texmf-dist/doc/generic/FAQ-en/faq-adj-types.tex @@ -1,4 +1,4 @@ -% $Id: faq-adj-types.tex,v 1.33 2011/06/01 19:57:21 rf10 Exp rf10 $ +% $Id: faq-adj-types.tex,v 1.35 2011/10/12 21:58:46 rf10 Exp rf10 $ \section{Adjusting the typesetting} @@ -2627,7 +2627,9 @@ bundle, \Package{algpascal}, uses Pascal-like keywords, indents differently from \Package{algpseudocode}, and puts command arguments in maths mode instead of text mode. There is no floating environment but \Package{algorithmicx}, like \Package{algorithmic}, is compatible -with the \Package{algorithm} package. +with the \Package{algorithm} package. (There have been reports of +difficulty defining new commands to fit with the package; +unfortunately, the author is not available to comment.) The \Package{alg} package, like \Package{algorithms}, offers a floating algorithm environment with all of the ensuing niceties. @@ -2697,6 +2699,7 @@ algorithms to float like figures and tables. \item[program.sty]\CTANref{program} \item[pseudocode.sty]\CTANref{pseudocode} \end{ctanrefs} +\LastEdit{2011-10-12} \Question[Q-makeindex]{Generating an index in \AllTeX{}} @@ -2845,68 +2848,64 @@ is in the package files. \item[url.sty]\CTANref{url} \end{ctanrefs} -\Question[Q-music]{Typesetting music in \TeX{}} - -In the early days, a simple music package called Mu\TeX{} was -written by Angelika Schofer and Andrea Steinbach, which demonstrated -that music typesetting was possible; the package was very limited, and is -hardly ever used nowadays. Daniel Taupin took up the baton, and -developed Music\TeX{}, which allows the typesetting of polyphonic and -other multiple-stave music; Music\TeX{} remains available, but is most -definitely no longer recommended. - -Music\TeX{} has been superseded by a further development called -MusiX\TeX{}, which is a three-pass system (with a processor program -that computes values for the element spacing in the music, and sorts -out spaces and ties (which Music\tex{} does ``woodenly''~--- playing -from a Music\tex{}-typeset page is entirely possible, but the look of -the slurs is very unsatisfying). Thus Musix\tex{} achieves finer -control than is possible with the unmodified \TeX{}-based mechanism -that Music\TeX{} uses. - -The original author of Musix\tex{}, Andreas Egler, withdrew from -development of the package; he has a further package Opus\tex{} (not -on \acro{CTAN}) which is focused on typesetting Gregorian chant and -the like. - -Daniel Taupin forked his development of MusiX\TeX{}, and his is the -only version currently maintained (by Daniel's successors, since -Daniel died). - -Input to MusiX\TeX{} is tricky stuff, and Don Simons' preprocessor -\ProgName{pmx} is the preferred method of creating input for Taupin's -version. \ProgName{Pmx} greatly eases use of MusiX\TeX{}, but it -doesn't support the full range of MusiX\TeX{}'s facilities directly; -however, it does allow in-line MusiX\TeX{} code in \ProgName{pmx} -sources. - -Dirk Laurie's \ProgName{M-Tx} allows preparation of music with lyrics; -it operates ``on top of'' \ProgName{pmx} - -Another simple notation is supported by \ProgName{abc2mtex}; this is a -package designed to notate tunes stored in an \acro{ASCII} format -(\texttt{abc} notation). It was designed primarily for folk and traditional -tunes of Western European origin (such as Irish, English and Scottish) -which can be written on one stave in standard classical notation, and -creates input intended for Music\TeX{}. However, it should be -extendable to many other types of music. - -Digital music fans can typeset notation for their efforts by using -\ProgName{midi2tex}, which translates \acro{MIDI} data files into -Music\TeX{} source code. - -There is a mailing list (\Email{TeX-music@icking-music-archive.org}) -for discussion of typesetting music in \TeX{}; it mostly covers -MusiX\TeX{} and related systems. To subscribe, use -\URL{http://icking-music-archive.org/mailman/listinfo/tex-music/} - -An alternative (free) means of embedding music examples into \AllTeX{} -documents is \href{http://www.lilypond.org}{Lilypond}. Lilypond is -(at heart) a batch music typesetting system with plain text input that -does most of its work without TeX. Lilypond's input syntax is far -less cryptic than is MusiX\TeX{}'s, and it handles much more stuff -automatically, yielding the same or better quality with less effort. -Lilypond can also produce basic \acro{MIDI} output. +\Question[Q-music]{Typesetting music in \tex{}} + +The current best bet for music typesetting is to use +\Package{musixtex}. \Package{Musixtex} is a three-pass system that +has a \tex{}-based pass, a processing pass and then a further \tex{} +pass. The middle pass, a program called \ProgName{musixflx}, +optimises the spacing and sorts out slurs and ties. +\Package{Musixtex} is demanding of \tex{} resources, and any +significant score requires that typesetting is done using \etex{}, +whose expanded variable- and box-register ranges allow for more of the +``parallel'' activities that abound in a music score. +Of course, \Package{musixtex} also requires music fonts; those are +available in a separate package on the archive. + +\Package{Musixtex} requires pretty arcane input; most people using it +actually prepare (less obscure) input for \ProgName{pmx}, whose output +is \tex{} input suitable for \Package{musixtex}. + +A further preprocessor, \ProgName{M-Tx}, allows preparation of music +with lyrics; \ProgName{M-Tx}'s output is fed into \ProgName{pmx}, and +thence to \Package{musixtex}. + +An alternative path to music examples within a \alltex{} document is +\href{http://www.lilypond.org}{\ProgName{Lilypond}}. +\ProgName{Lilypond} is (at heart) a batch music typesetting system +with plain text input that does most of its work without \tex{}. +\ProgName{Lilypond}'s input syntax is less cryptic than is +MusiX\TeX{}'s, though similar quality is achieved. The +\ProgName{lilypond} +\href{http://lilypond.org/web/about/faq}{\acro{FAQ}} mentions +development of graphical user interfaces. + +Another alternative in the production of music is the \acro{ABC} +notation, which was developed to notate the traditional music of +Western Europe (which can be written on a single stave), though it can +be used much more widely. A front end to \Package{musictex} (see +below), \ProgName{abc2mtex}, makes \acro{ABC} typesetting possible. + +The program \ProgName{midi2tex} can also generate \Package{musictex} +output, from \acro{MIDI} files. + +The history of music in \tex{} goes back some time; the earliest +``working'' macros were Mu\tex{}, by Angelika Schofer and Andrea +Steinbach. Mu\tex{} was very limited, but it was some time before +Daniel Taupin took up the baton, and developed Music\TeX{}, which +allows the typesetting of polyphonic and other multiple-stave music; +Music\TeX{} remains available, but is no longer recommended. + +The first version of Musix\tex{} was developed by Andreas Egler, but +he withdrew from the project to work on another package, Opus\tex{}. +That never reached the mainstream, and is no longer maintained. The +current recommended way of doing Opus\tex{}'s job is +\href{http://home.gna.org/gregorio/}{\ProgName{gregorio}}, which can +in principle feed into a \tex{}-based document. + +Once Andreas Egler had withdrawn (his last version of +\Package{musixtex} is preserved on the archive), Daniel Taupin took up +the development, leading to the \Package{musixtex} used today. \begin{ctanrefs} \item[abc2mtex]\CTANref{abc2mtex} \item[M-Tx]\CTANref{mtx} @@ -2915,9 +2914,11 @@ Lilypond can also produce basic \acro{MIDI} output. % ! line breaks \item[musixtex \nothtml{\rmfamily}(Taupin's version)]\CTANref{musixtex} \item[musixtex \nothtml{\rmfamily}(Egler's version)]\CTANref{musixtex-egler} +\item[musixtex \nothtml{\rmfamily}fonts]\CTANref{musixtex-fonts} \item[mutex]\CTANref{mutex} \item[pmx]\CTANref{pmx} \end{ctanrefs} +\LastEdit{2011-11-01} \Question[Q-parskip]{Zero paragraph indent} @@ -3393,9 +3394,9 @@ multiple indexing. You tag each \csx{makeindex}, \csx{index} and \csx{printindex} command with a file name, and indexing commands are written to (or read from) the name with the appropriate (\extension{idx} or \extension{ind}) extension appended. The \csx{printindex} command is modified -from the \LaTeX{} standard so that it doesn't create its own chapter -or section heading; you therefore decide what names (or sectioning -level, even) to use for the indexes, and +from an old version of the \LaTeXo{} standard so that it doesn't +create its own chapter or section heading; you therefore decide what +names (or sectioning level, even) to use for the indexes, and \Qref*{\csx{indexname}}{Q-fixnam} is completely ignored. To create a ``general'' and an ``authors'' index, one might write: @@ -3405,7 +3406,7 @@ To create a ``general'' and an ``authors'' index, one might write: \makeindex{general} \makeindex{authors} ... -\index{authors}{Another Idiot} +\index{authors}{Eccentric Professor} ... \index{general}{FAQs} ... @@ -3427,6 +3428,13 @@ file you're processing, at all. (There's no documentation that comes with the package: what you see above is as good as you will get\dots{}) +The \Package{multind} package doesn't work with the % ! line break +\Qref*{\amslatex{} classes}{Q-AMSpkg}, but the \acro{AMS} provide a +substitute, the \Package{amsmidx} package. You use the +\Package{amsmidx} package pretty much the same as you would +\Package{multind}, but if things aren't clear, there \emph{is} +documentation (unlike \Package{multind}). + The \Package{index} package provides a comprehensive set of indexing facilities, including a \csx{newindex} command that allows the definition of new styles of index. \csx{newindex} takes a `tag' (for @@ -3497,10 +3505,25 @@ from this trick, \Package{splitidx} supports the same sorts of things as does \Package{index}. An example of use appears in the documentation. +The \Package{imakeidx} can do a wide range of things (in particular, +it can run an index-builder~--- via % ! line break +\Qref*{\csx{write18} commands}{Q-spawnprog}~--- so as to simplify +business of making the final copy of a document). The package can +also make multiple indexes; it can do the job in the conventional +(\Package{multind}) way, or by using the external +\ProgName{splitindex} script provided with the \Package{splitindex} +package. (This arrangement allows efficient operation with small +numbers of indexes, while retaining the flexibility of permitting +large numbers of indexes without hitting the restriction of numbers of +active output streams.) + The \Class{memoir} class has its own multiple-index functionality (as well as its own index layout options, which other packages delegate to the index style used by \ProgName{makeindex}). \begin{ctanrefs} +\item[amsmidx.sty]Part of the \acro{AMS} class distribution + \CTANref{amscls}[amsmidx] +\item[imakeidx.sty]\CTANref{imakeidx} \item[index.sty]\CTANref{index} \item[makeidx.sty]Part of the \LaTeX{} distribution \item[memoir.cls]\CTANref{memoir} |