@subsubsection HELP! I'm stuck!
-Please read this document carefully. If you are still at loss,
-send your subsubsections to the @strong{mailing list}, and not to authors
+Please read this document carefully. If you are still at loss, send
+your questions to the @strong{mailing list}, and not to authors
directly.
Note: relative paths are meant to be relative to the source directory
@node Installing, Documentation, Miscellaneous, FAQ - GNU LilyPond FAQs
@section Installing
+
@subsubsection If I install the .exe file on my DOS/windows 3.11 machine, it doesn't work
-The DOS port is done with the cygnus gnu/windows32 port of the GNU utils.
-It does @emph{not} work with windows 3.x; you need Windows-NT (95/98?). This
-is not a recommendation, however. We recommend you use Unix, in
-particular, use GNU/Linux. For further information see @file{README-W32}.
+The NT port is done with the Cygnus GNU/Windows32 port of the GNU utils.
+It does @emph{not} work with windows 3.x; you need Windows-NT (95/98?).
@subsubsection Where is guile-config
-RedHat RPMS don't include guile-config. You need guile-config as it
+Old RedHat RPMS don't include guile-config. You need guile-config as it
was produced during the RPM build run. Build the RPM from source
(@file{.src.rpm}), and use the guile-config that is in
@file{/usr/src/redhat/BUILD/guile-1.3/guile-config/}.
@end example
-You might need to create some extra "out" directories. Do this with
-@example
-
- make out-wwws
-
-@end example
@subsubsection Some of your neat scripts fail, what directories do you use:
@end example
-)
+
~/usr/src/bin is in the PATH, and contains symbolic links to the
compiled executables.
you have an rpm it is in /usr/doc/lilypond-X/. You have to install it
yourself.
-@subsubsection How do i create the @file{.tfm} files?
+@subsubsection How do I create the @file{.tfm} files?
You don't. The @file{.tfm} files should be generated automatically by
Metafont when you run TeX. Check your TeX installation, or ask
@node Language- mudela, Do you support -, Documentation, FAQ - GNU LilyPond FAQs
@section Language: mudela
-@subsubsection Why can't you type @code{#c} in stead of @code{cis} ?
-
-We think that @code{#c} looks as if you are entering the symbols to
-print (which you are not; remember, you're entering the musical
-content in Mudela)
-
-@subsubsection Why do I have to type the accidentals to the note if I specified them?
+@subsubsection Why do I have to type the accidentals to the note if I
+specified them in the keysignature?
Take this example
@example
@end example
Independently of how it was written and what the current key was, you
-would say that you are playing and reading "two C-sharp" notes. We
-have tried to make the language somewhat context-free. Of course
-sheet music is not context-free. Unfortunately, sheet music is also 2
-dimensional, and ASCII is not.
-
-Technically it would be feasible to have the Interpreting phase do
-tricky things to add (or leave out) the accidentals, but we think that
-it is impractical: it hampers the readability and portability of your
-source, since you need LilyPond to fill in the details and actually
-make sense of it.
+would say that you are playing and reading "two C-sharp" notes, so you
+have to enter C-sharp twice.
@subsubsection What is @code{cis} anyway
@subsubsection Can I join in on LilyPond development? How do I do this?
-LilyPond development is open for anyone who wants to join. We try
-to use a Bazaar style development model for LilyPond, see
-@uref{http://locke.ccil.org/~esr/writings/cathedral.html.} This means:
-frequent releases, everyone can send in a patch or do suggestions and
-all development discussions are public.
+LilyPond development is open for anyone who wants to join. We do
+frequent releases, you are welcome to send in a patch or do suggestions.
+Join the gnu-music-discuss mailing list to participate.
-To be precise, discussions take place on the gnu-music-discuss mailing
-list, which is open for subscription to everyone.
@subsubsection I want to implement XXXX! Should I do this?
-There might be better ways of doing XXXX, so it's a good thing to
+Yes.
+
+But since there might be better ways of doing XXXX, so it's a good thing to
ask about this before you start hacking. If you want to keep in touch
with current developments, you should subscribe to the mailing list
-(see the "links" section of the documentation).
@subsubsection Is there a GUI frontend? Should I start building one?
easier or quicker to use than mudela. But for composing a graphical
environment probably is indispensable.
-In any case @email{Derek Wyatt}(wyatt@@scar.utoronto.edu) is working on
-GTK based editor, but that effort practically died. (see
-@uref{http://harmonia.scar.utoronto.ca}.
-
-Matthew Hiller is working on extending Midiscore and Koobase to handle
-mudela. Check out @uref{http://zoo.cs.yale.edu/~meh25/}.
-
-There is also a GUI package RoseGarden that could be extended to
-output mudela.
+Matthew Hiller has extended Midiscore and Koobase to handle mudela.
+Check out @uref{http://zoo.cs.yale.edu/~meh25/}.
If you want to work on this, please send e-mail to the mailing list
@email{gnu-music-discuss@@gnu.org}.
Your best bet of getting us to include code, is to present it as a
"fait accompli", i.e., to send a patch to the mailing list.
-@subsubsection I made some code, how do I get you to include it?
-
-Send in a patch:
-@example
-
- diff -urN old-file new-file > patch
-
-@end example
-
-or
-@example
-
- diff -urN old-directory/ new-directory/ > patch
-
-@end example
-
-Alternatively, you can use issue the command
-@example
-
- make diff
-
-@end example
+Please use the diff command to generate a patch, and don't send complete
+files, even if the diff is larger than the whole file.
Don't forget to put your name and e-mail address
in the @file{AUTHORS.pod} file, or you won't get credits :-]
-@emph{Please} always send a @strong{-u} diff, even if it is larger than the
-whole file.
-
-@subsubsection How do I learn the C++ code?
-
-The entry point is in @code{main()}. Good luck. :-)
-
-Seriously, read, reread and reread internals and CodingStyle, and
-just start anywhere.
-
-Anywhere? Well, most of the comment doco are in the header files, so
-your best bet would be @code{less lily/include/*.hh}.
-
-You should also have a look using Javadoc like tools. Try
-DOC++, @uref{http://www.imaginator.com/doc++}
-
-@subsubsection Why GPL?
-
-No comment.
-
@subsubsection Your make system does not adhere to GNU coding standards, could you please fix it?
@subsubsection I use dvilj4, and there are lots of warning messages for the printing
-You should use dvips and ghostscript to print the @code{dvi} output:
-the slurs and beams are PS @code{\special} commands.
+You should use dvips and ghostscript to print the @code{dvi} output: the
+slurs and beams are PS @code{\special} commands.
-subsubsection(My symbols are all messed up after I upgraded, I get the wrong symbols and dvi-checksum errors!)
+subsubsection My symbols are all messed up after I upgraded, I get the wrong symbols and dvi-checksum errors!
We obviously mucked with the fonts in the upgrade. Remove @emph{all}
previous fonts, including the @file{.pk} and @file{.tfm} fonts in
Silas S. Brown <ssb22@@hermes.cam.ac.uk>:
+@quotation
+
There are several aspects to sheet music copyright:
1. The music itself - copyright for the composer's life plus 70 years (so
References - best one I know is the UK-based Performing Right Society,
@uref{http://www.prs.co.uk/} (especially "membership") and their links to other
international equivalents.
+@end quotation
+
+Werner Lemberg @email{wl@@gnu.org} writes:
+
+@quotation
+
+Typesetting [at least in Austria or Germany, but not in France] [..]
+isn't copyrighted -- typesetting is a handcraft, not an
+art.
+What's copyrighted in an Urtext edition is the editor's comment or
+the revision remarks, cadenzas added by the editor, etc.
-Juergen Reuter <reuterj@@ira.uka.de>:
+Urtext editions per se are @emph{not} copyrighted -- if you print
+exactly what the composer has written, how can there some copyright be
+added? Copyrighted are usually only the `Critical notes', the foreword,
+and the cadenzas some editors have added.
+
+This means that the `Photocopying forbidden' sign in many scores is not
+always correct for e.g. J.S. Bach -- you are allowed to copy the pages
+which don't contain editorial stuff which is probably copyrighted.
+
+A very unfortunate situation for the publishers.
+
+@end quotation
+
+
+Glen Prideaux, @email{glenprideaux@@MailAndNews.com}:
+
+@quotation
+One has to be careful. In Australia typesetting IS covered by copyright, but
+only for 25 years (as opposed to 50 years from the death of the
+author/composer/artist for virtually any other copyright). If the
+typesetting originates in a country that does not protect typesetting then
+there may indeed be no copyright protection available to control the use of
+mudela files.
+@end quotation
+
+Juergen Reuter @email{reuterj@@ira.uka.de}
[More information can be had at: ]
for a summary of copyright relative to old music, also for the
expert forum for such subsubsections.
-Werner Lemberg <sx0005@@sx2.HRZ.Uni-Dortmund.DE>:
-
-This is not correct. Urtext editions per se are @emph{not} copyrighted
--- if you print exactly what the composer has written, how can there
-some copyright be added? Copyrighted are usually only the `Critical
-notes', the foreword, and the cadenzas some editors have added.
-
-This means that the `Photocopying forbidden' sign in many scores is
-not always correct for e.g. J.S. Bach -- you are allowed to copy the
-pages which don't contain editorial stuff which is probably
-copyrighted.
-
-A very unfortunate situation for the publishers.
-
@node Windows32, Top, Copyright, FAQ - GNU LilyPond FAQs
@section Windows32
projects / lilypond.git / blobdiff