Re: [TeX-Music] TeX, Latex and iMac

2009-07-13 Thread David Allsopp
  Graham Norton wrote
 
  A. The good news is that TexMozartp3.tex (see attached) did compile
  and generate the same output as in the manual  (except for the bar
  numbers).
  For this to work, the input file and the directory musixtex MUST be
  at the same level in the parent directory. This is crucial.
 
  Not on my PC. TeXMozartp3.tex goes through just fine, straight out of
  the box, without any musixtex directory at the same level as the
  source. I believe all that is required is to have a properly set up
  installation of TeX and MusiXTeX, with a path variable set to allow
  execution of all the necessary binaries, and with musixtex.tex and all
  the musixtex fonts in folders that TeX can find. In MiKTeX, the latter
  is accomplished by placing the files in the designated user input
  folder or a subfolders of that, and then refreshing the filename
  database.
 
 
 
 I tried putting TexMozartp3.tex  in Downloads, a complely different
 directory which does not contain any musixtex software. (I moved all my
 WIMA downloads  elsewhere in a directory Documents/music).
 
 Then I double-clicked on it to bring up Texshop (downloaded from CTAN)
 and it  compiled correctly in Tex . Perhaps it was just the initial run
 that needed them in the same position. No need to modify any  path
 names or a database.

TeXshop should have something called a Local Guide (because LaTeX
recommends that all distributions have a document called that) which should
explain where to put custom packages like musixtex and how to refresh the
FNDB (texhash is probably the command you're looking for).

  C. I note that doc/musixdoc.tex (which I cannot latex)
 
  When I first tried to latex it (not tex; it's a LaTeX file), latex
  complained that it couldn't find backgrnd.sty. So I grabbed that file
  from the musixtex.zip and put it in my user tex input folder,
  refreshed the filename database, and the file compiles just fine.
 
 No complaints about not being able to find backgrnd.sty ; it stops
 with
 
 !no room for a new count

(this message means TeX has run out of a particular kind of memory)

It sounds like your TeX distro is possibly not using e-TeX - very near the
top of the file, is there the line entering extended mode. The first three
lines of the log should be roughly:

This is [pdf]TeX, Version 3.1415926[-1.40.9] (the name of your
distribution)
**musixdoc
entering extended mode

Either that or it's possible that you're using a newer version of LaTeX
which has used slightly more memory and so pushed the documentation over the
limit.

 l 400 \newcount\nofMPsegements
 
 Unfortunately the log file is different and I cannot past the console
 errors.
 

snip

 
  D. Including
 
  \documentclass{article}
  \usepackage{musixtex}
 
  
 
  \end{document}
 
  around the example was a good suggestion. For this to work, my input
  Mozartp3.tex and the directory musixtex have to be in the same parent
  directory (i.e. at the same level).
 
  Unfortunately it still won't complete, complaining:
 
  !I can't find 'Mozartp3.aux,'
  \enddocument

Your sample is missing \begin{document} after \usepackage{musixtex}. All
LaTeX files get a .aux file on pass one, even though it may be empty.


David

___
tex-mu...@icking-music-archive.org mailing list
If you want to unsubscribe or look at the archives, go to 
http://mailman.nfit.au.dk/mailman/listinfo/icking-music-archive.org-tex-music


Re: [TeX-Music] TeX, Latex and iMac

2009-07-13 Thread Graham Norton

Dear David,

Thanks for your reply. I am really impressed that Mac OS learned the  
path names of the .sty etc. files after running them initially at the  
same level without any intervention on my part .i.e. without any  
changing path names or databases. It is now running fine with the  
input source files no longer having to be in the same position, which  
was my fix for the problem of not finding the .sty files.


I will get to texhash etc. later once I have learnt how to compile and  
run musixflx in C (or maybe run a unix version via X11)  on an iMac,  
which I have never done. I will need to look at some development  
literature.


But thanks for your comment on Texhash. It seems spot on.

musixflx is a more pressing concern.

I plan to write up some iMac installation notes and forward them to  
WIMA once I have worked out how to combine the output of pass 1 with  
musixflx and send its output to latex, hopefully seamlessly.



On 13/07/2009, at 4:39 PM, David Allsopp wrote:


Graham Norton wrote


A. The good news is that TexMozartp3.tex (see attached) did compile
and generate the same output as in the manual  (except for the bar
numbers).
For this to work, the input file and the directory musixtex MUST be
at the same level in the parent directory. This is crucial.


Not on my PC. TeXMozartp3.tex goes through just fine, straight out  
of

the box, without any musixtex directory at the same level as the
source. I believe all that is required is to have a properly set up
installation of TeX and MusiXTeX, with a path variable set to allow
execution of all the necessary binaries, and with musixtex.tex and  
all
the musixtex fonts in folders that TeX can find. In MiKTeX, the  
latter

is accomplished by placing the files in the designated user input
folder or a subfolders of that, and then refreshing the filename
database.




I tried putting TexMozartp3.tex  in Downloads, a complely different
directory which does not contain any musixtex software. (I moved  
all my

WIMA downloads  elsewhere in a directory Documents/music).

Then I double-clicked on it to bring up Texshop (downloaded from  
CTAN)
and it  compiled correctly in Tex . Perhaps it was just the initial  
run

that needed them in the same position. No need to modify any  path
names or a database.


TeXshop should have something called a Local Guide (because LaTeX
recommends that all distributions have a document called that) which  
should
explain where to put custom packages like musixtex and how to  
refresh the

FNDB (texhash is probably the command you're looking for).


C. I note that doc/musixdoc.tex (which I cannot latex)


When I first tried to latex it (not tex; it's a LaTeX file), latex
complained that it couldn't find backgrnd.sty. So I grabbed that  
file

from the musixtex.zip and put it in my user tex input folder,
refreshed the filename database, and the file compiles just fine.


No complaints about not being able to find backgrnd.sty ; it stops
with

!no room for a new count


(this message means TeX has run out of a particular kind of memory)

It sounds like your TeX distro is possibly not using e-TeX - very  
near the
top of the file, is there the line entering extended mode. The  
first three

lines of the log should be roughly:

This is [pdf]TeX, Version 3.1415926[-1.40.9] (the name of your
distribution)
**musixdoc
entering extended mode

Either that or it's possible that you're using a newer version of  
LaTeX
which has used slightly more memory and so pushed the documentation  
over the

limit.



On the console window, I get

This is pdfTeXk, Version 3.1415926.40.9 (Web2C 7.5.7)
\write18 enabled %-line parsing enabled.
entering extended mode

.
See the attached log file (curiously different from the console log  
file) it goes to line 3272.

musixdoc.log
Description: Binary data



l 400 \newcount\nofMPsegements

Unfortunately the log file is different and I cannot past the console
errors.




snip




D. Including

\documentclass{article}
\usepackage{musixtex}



\end{document}

around the example was a good suggestion. For this to work, my  
input
Mozartp3.tex and the directory musixtex have to be in the same  
parent

directory (i.e. at the same level).

Unfortunately it still won't complete, complaining:

!I can't find 'Mozartp3.aux,'
\enddocument


Your sample is missing \begin{document} after \usepackage{musixtex}.  
All

LaTeX files get a .aux file on pass one, even though it may be empty.


David

___
tex-mu...@icking-music-archive.org mailing list
If you want to unsubscribe or look at the archives, go to 
http://mailman.nfit.au.dk/mailman/listinfo/icking-music-archive.org-tex-music


SIlly of me to forget \begin{document}  I have been using Latex  
for nearly 20 years!!


Thanks for your helpful comments,

Graham___
tex-mu...@icking-music-archive.org mailing list
If you want to unsubscribe or look at the 

[TeX-Music] TeX, Latex and iMac

2009-07-12 Thread Graham Norton

Dear All,

Thanks for your replies and hints. Sincere apologies for the length of  
this reply.


A. The good news is that TexMozartp3.tex (see attached) did compile  
and generate the same output as in the manual  (except for the bar  
numbers). For this to work, the input file and the directory musixtex  
MUST be at the same level in the parent directory. This is crucial.



B. I did mean page 3 of the printed manual, not page iii. The example  
is as follows:



\begin{music}
\parindent10mm
\setname1{Piano}
\setstaffs12
\generalmeter{\meterfrac44}
\startextract
\Notes\ibu0f0\qb0{cge}\tbu0\qb0g|\hl j\en
\Notes\ibu0f0\qb0{cge}\tbu0\qb0g|\ql l\sk\ql n\en
\bar
\Notes\ibu0f0\qb0{dgf}|\qlp i\en
\notes\tbu0\qb0g|\ibbl1j3\qb1j\tbl1\qb1k\en
\Notes\ibu0f0\qb0{cge}\tbu0\qb0g|\hl j\en
\endextract
\end{music}

which I can now cut  from doc/musixdoc.tex. Thanks for this hint.

C. I note that doc/musixdoc.tex (which I cannot latex) differs from  
the pdf file of the manual currently available from WIMA. I'd like to  
suggest that  the pdf version of musixdoc.tex be put on WIMA,  
replacing the current one.


On line 8048 of musixdoc.tex, we read:


 When producing this examples, care should be taken about the fact
that several given files are supposed to be included (by means of
\keyindex{input}) in other files. Thus the only good files to be  
directly

\TeX-ed are those which begin with \verb|\input musixtex| or
 \verb|% \input musixtex|. This latter command is often commented out  
so that

the examples can be run either using a \musixtex\ format including {\tt
musixcpt.tex} and {\tt musixsty.tex} --- namely the format generated  
by {\tt
musixtex.ins} --- or using a \musictex\ format including {\tt  
musictrp.tex},
{\tt musicvbm.tex} and {\tt musicsty.tex} --- namely the format  
generated by

{\tt musixtex.ins}.


It would be very useful if this statement (or a shortened version of  
it) were included as a footnote before the first examples in the  
manual . And 'begin{music}'  \'end \{music} ' should be removed from  
the example! ... it is a bit confusing here for the reader, as Tex is  
mentioned repeatedly as the preferred engine, and in Chapter 2,  
opening paragraph,  we are reminded that \input musixtex must be  
included, again suggesting Tex.


D. Including

\documentclass{article}
\usepackage{musixtex}



\end{document}

around the example was a good suggestion. For this to work, my input  
Mozartp3.tex and the directory musixtex have to be in the same parent  
directory (i.e. at the same level).


Unfortunately it still won't complete, complaining:

!I can't find 'Mozartp3.aux,'
\enddocument

and hangs on
l. 17 \end{document}

with no pdf file generated. Definite progress, but this is strange as  
there are no e.g section references to generate such a file(??)


Seems to be a Latex problem.  Oddly enough, Tex does not complain  
about a missing .aux file, and does not generate one from e.g.  
adagio.tex.



Thanks again for your assistance.

Graham Norton

 

TexMozartp3.tex
Description: Binary data


TexMozartp3.pdf
Description: Adobe PDF document
___
tex-mu...@icking-music-archive.org mailing list
If you want to unsubscribe or look at the archives, go to 
http://mailman.nfit.au.dk/mailman/listinfo/icking-music-archive.org-tex-music


Re: [TeX-Music] TeX, Latex and iMac

2009-07-12 Thread Graham Norton

Dear Don,

Thanks for your reply.



On 13/07/2009, at 1:47 PM, Don Simons wrote:


Graham Norton wrote

A. The good news is that TexMozartp3.tex (see attached) did compile  
and
generate the same output as in the manual  (except for the bar  
numbers).
For this to work, the input file and the directory musixtex MUST be  
at

the same level in the parent directory. This is crucial.


Not on my PC. TeXMozartp3.tex goes through just fine, straight out  
of the

box, without any musixtex directory at the same level as the source. I
believe all that is required is to have a properly set up  
installation of
TeX and MusiXTeX, with a path variable set to allow execution of all  
the
necessary binaries, and with musixtex.tex and all the musixtex fonts  
in
folders that TeX can find. In MiKTeX, the latter is accomplished by  
placing
the files in the designated user input folder or a subfolders of  
that, and

then refreshing the filename database.




I tried putting TexMozartp3.tex  in Downloads, a complely different  
directory which does not contain any musixtex software. (I moved all  
my WIMA downloads  elsewhere in a directory Documents/music).


Then I double-clicked on it to bring up Texshop (downloaded from CTAN)  
and it  compiled correctly in Tex . Perhaps it was just the initial  
run that needed them in the same position. No need to modify any  path  
names or a database.



C. I note that doc/musixdoc.tex (which I cannot latex)


When I first tried to latex it (not tex; it's a LaTeX file), latex
complained that it couldn't find backgrnd.sty. So I grabbed that  
file from

the musixtex.zip and put it in my user tex input folder, refreshed the
filename database, and the file compiles just fine.


No complaints about not being able to find backgrnd.sty ; it stops  with

!no room for a new count

l 400 \newcount\nofMPsegements

Unfortunately the log file is different and I cannot past the console  
errors.



differs from the
pdf file of the manual currently available from WIMA. I'd like to
suggest that  the pdf version of musixdoc.tex be put on WIMA,  
replacing

the current one.


There are two versions of the manual on WIMA. I believe that the  
directly

linked copy of version T.113, at
http://www.icking-music-archive.org/software/musixtex/musixdoc.pdf
is the same as the one from musixdoc.tex in the musixtex.zip. If  
there are

any differences, please let me know exactly where they are.


I have not compared them in detail, but Chapter {Examples} in  
musixdoc.tex  is quite different from  \Chapter{MusixTex examples} of  
the pdf of T114 that I  downloaded.



The other one
that is directly linked is version T.114, at
http://www.icking-music-archive.org/software/musixtex/mxdoc110d.pdf
This is an extensively edited version. I am not going to remove it,  
because

I spent a long time creating it, and I believe it's a substantial
improvement over to older version. Some day I or some other  
volunteer may
create a new musixtex.zip; and when and if that happens, the most  
recent

version of the manual will be included.



On line 8048 of musixdoc.tex, we read:

 When producing this examples, care should be taken about the fact  
that

several given files are supposed to be included (by means of
\keyindex{input}) in other files. Thus the only good files to be
directly \TeX-ed are those which begin with \verb|\input musixtex| or
\verb|% \input musixtex|. This latter command is often commented out
so that the examples can be run either using a \musixtex\ format
including {\tt musixcpt.tex} and {\tt musixsty.tex} --- namely the
format generated by {\tt musixtex.ins} --- or using a \musictex\  
format
including {\tt musictrp.tex}, {\tt musicvbm.tex} and {\tt  
musicsty.tex}

--- namely the format generated by {\tt musixtex.ins}.


It would be very useful if this statement (or a shortened version of
it) were included as a footnote before the first examples in the  
manual

. And 'begin{music}'  \'end \{music} ' should be removed from the
example! ... it is a bit confusing here for the reader, as Tex is
mentioned repeatedly as the preferred engine, and in Chapter 2,  
opening
paragraph,  we are reminded that \input musixtex must be included,  
again

suggesting Tex.



Where to begin? I removed this comment from version T.114 of the  
manual. It
contains lots of references to obsolete components of the MusiXTeX  
system.
The corresponding text in T.114 is The file musixdoc.tex, the  
source for

this manual, contains many useful examples. In the
PDF, many examples are accompanied by a display of the code that  
produced

them, while for a
few only an image of the extract is included in the PDF and you'll  
have to

look in musixdoc.tex
to see the coding. I admit that I didn't go into the complex  
distinctions
between TeX and LaTeX at this point. But the idea is that in most  
cases, one
can copy the source from the PDF, surround it with the necessary  
boilerplate

including setting up the page size,