sect(Installing)
-question(Wow, the webpages look really neat, but if I install the .exe
-file on my DOS/windows 3.11 machine, it doesn't work.)
+question(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 em(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).
+question(Where is guile-config)
+
+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/).
+
+
question(I get all kinds of errors while compiling file(parser.cc))
LilyPond uses features of bison version 1.25. Please confirm that
question(Do you support multiple staff-sizes?)
-Yes and no. At this time you can choose between 11, 13, 16, 19,
-20, 23 and 20 pt staff-size. The sizes can't be changed per staff
-(yet). Look at file(standchen.ly) for an example.
+Yes. At this time you can choose between 11, 13, 16, 19, 20, 23 and
+20 pt staff-size. Use the staffLineLeading property for setting the
+size of the staff, and fontSize for setting the size of the glyphs.
+
+question(Do you support Gregorian chant notation?)
+
+No. There is no reason why LilyPond can't be extended to do so, but
+we haven't done it yet (and there are currently no plans to do it).
+
+question(Do you support grace notes?)
+
+No. But they can kludged. See file(input/test/grace.ly)
sect(How do I ....)
question(How do I get bar numbers?)
-See file(init/engraver.ly). You have to uncomment some entries. To
-do this `portably' you should redefine some engravers in your own
-source files. Check out file(init/rhythm.ly).
+See file(input/test/bar-scripts.ly).
sect(Development)
RoseGarden that could be extended to output mudela.
If you want to work on this, please send e-mail to the mailing list
-email(gnu-misc-discuss@gnu.org).
+email(gnu-music-discuss@gnu.org).
question(I want to implement XXXX! How should I do this?)
directory is called out/, there is one in every source directory).
make distclean essentially reduces to file(rm -f out/*) in every directory
-
question(gdb crashes when I debug!)
Upgrade to 4.17.
-question(Why do I need g++ >= 2.7?)
+question(Why do I need g++ >= 2.8 / EGCS-1.1 ?)
-By using g++, GNU LilyPond is portable to all platforms which support
-g++ (there are quite a few). Not having to support other compilers
-saves us a em(lot) of trouble.
+Supporting more compilers than EGCS/G++ 2.8 is unlikely to make
+LilyPond run on more platforms. It would give us an enormous headache
+in detecting and catering for every variant of every compiler: not
+having to support other compilers saves us a em(lot) of trouble.
sect(Running)
file(/var/lib/texmf). A script automating this has been included, see
file(buildscripts/clean-fonts.sh).
+question(all the pk and tfm
+fonts are created in the directory where the mudela file is, not in
+"/var/spool/texmf" where I think they should be.)
+
+Mats Bengtsson <mats.bengtsson@s3.kth.se> writes:
+
+The simple solution used by Anthony Fok in the Debian distribution of
+Lilypond is to link the mf/ directory to
+/usr/lib/texmf/fonts/source/public/lilypond Depending on what
+distribution of teTeX and Linux you have installed, there might also
+be other places like /usr/local/lib/texmf/fonts/source/public/lilypond
+or /var/spool/texmf//fonts/source/public/lilypond
+
+Wherever you put it, don't forget to run mktexlsr (or texhash for
+older installations) afterwards, so that TeX will find the files.
+Also, don't forget to remove all old .tfm and .*pk files when the font
+is updated (as it will be in version 1.1.40, for example).
+
+question(How does PS output work?)
+
+itemize(
+ it()
+Generate the PostScript Type-3 fonts. In the file(mf/)
+subdirectory, issue:
+verb(
+ make pfa
+) in the mf/ subdirectory. This will also make file(mfplain) for metapost.
+it()
+Run lilypond with option tt(-f ps):
+verb(
+ lilypond -fps foo.ly
+)
+it() To view the file(.ps) output with GhostView, set GS_FONTPATH to the
+directory containing the file(pfa)s, and set GS_LIB to the directory containing the file(.ps) library files of LilyPond. In the source tree, these are file(mf/out/) and file(ps/).
+
+
+i.e. do something like:
+verb(
+ export GS_FONTPATH=$HOME/usr/src/lilypond/mf/out
+ export GS_LIB=$HOME/usr/src/lilypond/ps
+ gv foo.ps &
+)
+)
+
+Direct PS output is still experimental. For creating nice looking ps
+output, use TeX() and code(dvips).
+
question(The beams and slurs are gone if use the XDvi magnifying glass!?)
The beams and slurs are done in PostScript. XDvi doesn't show
\melodic { c4 c g g }
\paper {}
\midi {
- \output "myfile.mid";
+ output = "myfile.midi";
\tempo 4=70;
}
}
done, and as a method of proof"reading" the input. The MIDI support
is by no means finished. Patches appreciated.
+
+sect(Copyright)
+
+question(How does copyright for sheet music work? Can I enter and
+spread my newly bought Bach urtext?)
+
+Silas S. Brown <ssb22@hermes.cam.ac.uk>:
+
+There are several aspects to sheet music copyright:
+
+1. The music itself - copyright for the composer's life plus 70 years (so
+not applicable to Bach).
+
+2. If the music is an arrangement, then the arranger holds copyright on
+that arrangement. However, you can produce your own arrangement using
+that arrangement as a reference point. Obviously your arrangement must be
+sufficently different to be called your own arrangement - you need to do
+more than change one note!
+
+3. In some countries, the same applies for editions. This could be
+relevant to the Bach example. If a modern person has edited the music,
+then they hold the copyright on the edition. This does not stop you from
+removing the editorial features - remove all editorial slurs, phrasemarks,
+ornaments etc and only leave those that you know to be original. You can
+then add some of your own if you want to be your own editor.
+
+4. If there are lyrics, then the lyricist also holds copyright. This
+does not stop you from using the music without the lyrics if it is
+otherwise out of copyright.
+
+5. The copyright of the printed page is held by the publisher for 30
+years after printing (25 in some countries). This stops you from
+photocopying (unless it's "fair use" eg. you're partially sighted and need
+to enlarge the music) or otherwise reproducing the typesetting that is
+used on it. But the copyright is only held over the typesetting work, not
+the music itself. Since Mudela specifies the notes, independently of any
+typesetting work that went into your reference copy, you are not
+duplicating any of the publisher's work.
+
+6. If you want to violate copyright, there are two main cases where you
+may do so: fair use, and with permission. The former is rather fuzzily
+defined, but it includes such things as including small extracts of a
+score in a critique, and making a large print or Braille copy for a blind
+or partially-sighted performer (many people argue that in this case it
+should always be kept with the original copy and/or destroyed after it is
+no longer needed). The latter is obvious: You can always write to the
+composer, arranger, editor, lyricist or publisher in question and ask if
+you can do whatever it is you're trying to do. Some will respond more
+readily than others, but anything that they say will override any copying
+restrictions imposed on you.
+
+
+References - best one I know is the UK-based Performing Right Society,
+lurl(http://www.prs.co.uk/) (especially "membership") and their links to other
+international equivalents.
+
+
+
+Juergen Reuter <reuterj@ira.uka.de>:
+
+[More information can be had at: ]
+
+lurl(http://lcweb.loc.gov/copyright/)
+(USA copyright law)
+
+lurl(http://fairuse.stanford.edu/)
+(meta site about copyright with many links to other resources)
+
+lurl(http://host.mpa.org/crc.html)
+(copyright from the viewpoint of the USA music publishers' association)
+
+lurl(http://www.wipo.int)
+(World Intellectual Property Organization (a UNO agency); with
+information about international copyright)
+
+
sect(Windows32)
question(I downloaded the windows32 port, and it doesn't match the website!)
projects / lilypond.git / blobdiff