@node Point and click
@section Point and click
+
@cindex point and click
Point and click lets you find notes in the input by clicking on them
* Selective point-and-click::
@end menu
+
@node Configuring the system for point and click
@subsection Configuring the system
for @code{LYEDITOR} is equivalent to the standard emacsclient
invocation.
-
@menu
* Using Xpdf for point and click::
* Using GNOME 2 for point and click::
* Extra configuration for Evince::
@end menu
+
@node Using Xpdf for point and click
@unnumberedsubsubsec Using Xpdf
+
@cindex Xpdf
For Xpdf on UNIX, the following should be present in
package and the corresponding @samp{libpoppler} package from
Debian instead. Once you have tested that this works, you might
want to use
+
@example
sudo apt-mark hold xpdf
@end example
+
@noindent
in order to keep Ubuntu from overwriting it with the next
@q{update} of its crashing package.
+
@node Using GNOME 2 for point and click
@unnumberedsubsubsec Using GNOME 2
For using GNOME 2 (and PDF viewers integrated with it), the magic
invocation for telling the system about the @samp{textedit:} URI
-is
-@example
+is;
+
+@smallexample
gconftool-2 -t string -s /desktop/gnome/url-handlers/textedit/command "lilypond-invoke-editor %s"
gconftool-2 -s /desktop/gnome/url-handlers/textedit/needs_terminal false -t bool
gconftool-2 -t bool -s /desktop/gnome/url-handlers/textedit/enabled true
-@end example
+@end smallexample
+
+After that invocation;
-After that invocation,
@example
gnome-open textedit:///etc/issue:1:0:0
@end example
+
@noindent
should call @file{lilypond-invoke-editor} for opening files.
+
@node Using GNOME 3 for point and click
@unnumberedsubsubsec Using GNOME 3
In GNOME 3, URIs are handled by the @q{gvfs} layer rather than by
@q{gconf}. Create a file in a local directory such as @file{/tmp}
-that is called @file{lilypond-invoke-editor.desktop} and has the contents
+that is called @file{lilypond-invoke-editor.desktop} and has the
+contents;
+
@example
[Desktop Entry]
Version=1.0
xdg-mime default lilypond-invoke-editor.desktop x-scheme-handler/textedit
@end example
-After that invocation,
+After that invocation;
+
@example
gnome-open textedit:///etc/issue:1:0:0
@end example
@noindent
should call @file{lilypond-invoke-editor} for opening files.
+
@node Extra configuration for Evince
@unnumberedsubsubsec Extra configuration for Evince
+
@cindex Evince
If @code{gnome-open} works, but Evince still refuses to open point
For Ubuntu, the process is to edit the file
@file{/etc/apparmor.d/local/usr.bin.evince} and append the
following lines:
+
@example
# For Textedit links
/usr/local/bin/lilypond-invoke-editor Cx -> sanitized_helper,
Now Evince should be able to open point and click links. It is
likely that similar configurations will work for other viewers.
+
@node Enabling point and click
@unnumberedsubsec Enabling point and click
@cindex file size, output
files to be distributed to avoid including path information about
your computer in the PDF file, which can pose a security risk.}
+
@node Selective point-and-click
@unnumberedsubsec Selective point-and-click
example.ly
@end smallexample
-
@end itemize
* Other editors::
@end menu
+
@node Emacs mode
@unnumberedsubsec Emacs mode
running some of these scripts, e.g. @code{convert-ly}, see
@rweb{MacOS X}.
-
@knownissues
We unfortunately do not have the resources to maintain these
programs; please consider them @qq{as-is}. Patches are appreciated, but
@end menu
-
@node Invoking midi2ly
@subsection Invoking @command{midi2ly}
@cindex MIDI
-@command{midi2ly} translates a Type@tie{}1 MIDI file to a LilyPond source
-file.
+@command{midi2ly} translates a Type@tie{}1 MIDI file to a LilyPond
+source file.
MIDI (Music Instrument Digital Interface) is a standard for digital
instruments: it specifies cabling, a serial protocol and a file
then convert it to @file{.ly}. However, human players are not
rhythmically exact enough to make a MIDI to LY conversion trivial.
When invoked with quantizing (@option{-s} and @option{-d} options)
-@command{midi2ly} tries to compensate for these timing errors, but is not
-very good at this. It is therefore not recommended to use @command{midi2ly}
-for human-generated midi files.
-
+@command{midi2ly} tries to compensate for these timing errors, but is
+not very good at this. It is therefore not recommended to use
+@command{midi2ly} for human-generated midi files.
It is invoked from the command-line as follows,
+
@example
midi2ly [@var{option}]@dots{} @var{midi-file}
@end example
Treat every text as a lyric.
@end table
-
@knownissues
-
Overlapping notes in an arpeggio will not be correctly rendered. The
first note will be read and the others will be ignored. Set them all
to a single duration and add phrase markings or pedal indicators.
@command{musicxml2ly} extracts the notes, articulations, score structure,
lyrics, etc. from part-wise MusicXML files, and writes them to a @file{.ly}
-file. It is invoked from the command-line.
-
+file and is invoked from the command-line as follows;
-It is invoked from the command-line as follows,
@example
musicxml2ly [@var{option}]@dots{} @var{xml-file}
@end example
use LANG for pitch names, e.g. 'deutsch' for note names in German.
@item --loglevel=@var{loglevel}
-Set the output verbosity to @var{loglevel}. Possible values are @code{NONE},
-@code{ERROR}, @code{WARNING}, @code{PROGRESS} (default) and @code{DEBUG}.
+Set the output verbosity to @var{loglevel}. Possible values are
+@code{NONE}, @code{ERROR}, @code{WARNING}, @code{PROGRESS} (default) and
+@code{DEBUG}.
@item --lxml
-use the lxml.etree Python package for XML-parsing; uses less memory and cpu time.
+use the lxml.etree Python package for XML-parsing; uses less memory and
+cpu time.
@item -m, --midi
activate midi-block.
beaming instead.
@item -o, --output=@var{file}
-set output filename to @var{file}. If @var{file} is @file{-}, the output
-will be printed on stdout. If not given, @var{xml-file}@file{.ly} will
-be used.
+set output filename to @var{file}. If @var{file} is @file{-}, the
+output will be printed on stdout. If not given,
+@var{xml-file}@file{.ly} will be used.
@item -r, --relative
convert pitches in relative mode (default).
@node Invoking abc2ly
@subsection Invoking @code{abc2ly}
-@warning{This program is not supported, and may be remove from
-future versions of LilyPond.}
+@warning{This is not currently supported and may eventually be removed
+from future versions of LilyPond.}
@cindex ABC
-ABC is a fairly simple ASCII based format. It is described at the ABC site:
+ABC is a fairly simple ASCII based format. It is described at the ABC
+site:
@quotation
@uref{http://@/www@/.walshaw@/.plus@/.com/@/abc/@/learn@/.html}.
@end quotation
-@command{abc2ly} translates from ABC to LilyPond. It is invoked as follows:
+@command{abc2ly} translates from ABC to LilyPond. It is invoked as
+follows:
@example
abc2ly [@var{option}]@dots{} @var{abc-file}
@end table
There is a rudimentary facility for adding LilyPond code to the ABC
-source file. If you say:
+source file. For example;
@example
%%LY voices \set autoBeaming = ##f
will cause the text following the @q{slyrics} keyword to be inserted
into the current line of lyrics.
-
@knownissues
-
The ABC standard is not very @q{standard}. For extended features
(e.g., polyphonic music) different conventions exist.
@node Invoking etf2ly
@subsection Invoking @command{etf2ly}
-@warning{This program is not supported, and may be remove from
-future versions of LilyPond.}
+@warning{This is not currently supported and may eventually be removed
+from future versions of LilyPond.}
+@cindex Enigma Transport Format
@cindex ETF
@cindex enigma
@cindex Finale
@cindex Coda Technology
ETF (Enigma Transport Format) is a format used by Coda Music
-Technology's Finale product. @command{etf2ly} will convert part of an ETF
-file to a ready-to-use LilyPond file.
+Technology's Finale product. @command{etf2ly} will convert part of an
+ETF file to a ready-to-use LilyPond file.
-It is invoked from the command-line as follows.
+It is invoked from the command-line as follows;
@example
etf2ly [@var{option}]@dots{} @var{etf-file}
version information
@end table
-
@knownissues
-
The list of articulation scripts is incomplete. Empty measures
-confuse @command{etf2ly}. Sequences of grace notes are ended improperly.
+confuse @command{etf2ly}. Sequences of grace notes are ended
+improperly.
@node Other formats
are listed in @rweb{Easier editing}.
-
@node LilyPond output in other programs
@section LilyPond output in other programs
@node Inserting LilyPond output into OpenOffice and LibreOffice
-@unnumberedsubsec Inserting LilyPond output into OpenOffice and LibreOffice
+@unnumberedsubsec Inserting LilyPond output into OpenOffice and
+LibreOffice
@cindex OpenOffice.org
@cindex LibreOffice.org
that program. Most programs will be able to insert LilyPond output in
@file{PNG}, @file{EPS}, or @file{PDF} formats.
-To reduce the white space around your LilyPond score, use
-the following options
+To reduce the white space around your LilyPond score, use the following
+options;
@example
\paper@{
into LilyPond itself, but until that happens, you must download
and @code{\include} them manually.
-
@menu
* MIDI articulation::
@end menu
@end example
@knownissues
-
Its main limitation is that it can only affect things it knows
about: anything that is merely textual markup (instead of a note
property) is still ignored.
-
-
projects / lilypond.git / commitdiff