CVSROOT: /cvsroot/lilypond
Module name: lilypond
Branch: lilypond_2_6
Changes by: Graham Percival <[EMAIL PROTECTED]> 05/08/05 07:53:01
Modified files:
. : ChangeLog
Documentation/user: lilypond.tely
Log message:
Change documentencoding to utf-8.
CVSWeb URLs:
http://savannah.gnu.org/cgi-bin/viewcvs/lilypond/lilypond/ChangeLog.diff?only_with_tag=lilypond_2_6&tr1=1.3836.2.19&tr2=1.3836.2.20&r1=text&r2=text
http://savannah.gnu.org/cgi-bin/viewcvs/lilypond/lilypond/Documentation/user/lilypond.tely.diff?only_with_tag=lilypond_2_6&tr1=1.132&tr2=1.132.2.1&r1=text&r2=text
Patches:
Index: lilypond/ChangeLog
diff -u lilypond/ChangeLog:1.3836.2.19 lilypond/ChangeLog:1.3836.2.20
--- lilypond/ChangeLog:1.3836.2.19 Thu Aug 4 20:29:41 2005
+++ lilypond/ChangeLog Fri Aug 5 07:53:00 2005
@@ -1,3 +1,7 @@
+2005-08-04 Graham Percival <[EMAIL PROTECTED]>
+
+ * Documentation/user/lilypond.tely: set documentencoding utf-8.
+
2005-07-25 Jan Nieuwenhuizen <[EMAIL PROTECTED]>
* lily/main.cc (sane_setenv)[!ARGV0_RELOCATION]: Also define.
Index: lilypond/Documentation/user/lilypond.tely
diff -u /dev/null lilypond/Documentation/user/lilypond.tely:1.132.2.1
--- /dev/null Fri Aug 5 07:53:02 2005
+++ lilypond/Documentation/user/lilypond.tely Fri Aug 5 07:53:01 2005
@@ -0,0 +1,326 @@
+\input texinfo @c -*- coding: latin-1; mode: texinfo; -*-
[EMAIL PROTECTED] lilypond.info
[EMAIL PROTECTED] GNU LilyPond
[EMAIL PROTECTED]
[EMAIL PROTECTED]
[EMAIL PROTECTED] iftex
+
[EMAIL PROTECTED] GNU music project
[EMAIL PROTECTED]
+
[EMAIL PROTECTED]
+(I think)
+Current version of the manual: 2.5.18
+Please update this whenever you run convert-ly on the docs.
+
+convert-ly --from=... --to=... --no-version *.itely
+
+%%%%%
+
+Distributions will want to install lilypond.info in postinstall, doing:
+
+ install-info --info-dir=/usr/share/info out/lilypond.info
+
+%%%%%
+
+ * Prepend GNU for dir, must be unique.
+
+ * Do not list the `lilypond' node at toplevel, so that `info lilypond'
+ goes to Top.
+
+ * List all commands in direntry.
+
[EMAIL PROTECTED] * lilypond: (lilypond/lilypond)Running LilyPond.
Invoking the
[EMAIL PROTECTED] LilyPond program.
+
[EMAIL PROTECTED] ignore
+
+* LilyPond: (lilypond/lilypond). The GNU music typesetter.
+* abc2ly: (lilypond/lilypond)Invoking abc2ly. Importing ABC.
+* convert-ly: (lilypond/lilypond)Invoking convert-ly. Older LilyPond versions.
+* etf2ly: (lilypond/lilypond)Invoking etf2ly. Importing Finale.
+* lilypond-book: (lilypond/lilypond)LilyPond-book. Itegrating text and
music.
+* midi2ly: (lilypond/lilypond)Invoking midi2ly. Importing MIDI.
+* mup2ly: (lilypond/lilypond)Invoking mup2ly. Importing Mup.
+* musedata2ly: (lilypond/lilypond)Invoking musedata2ly. Importing
MuseData.
[EMAIL PROTECTED] direntry
+
+
[EMAIL PROTECTED]
[EMAIL PROTECTED] Han-Wen Nienhuys and Jan Nieuwenhuizen
[EMAIL PROTECTED] User manual of the LilyPond music engraving system
[EMAIL PROTECTED] user manual
[EMAIL PROTECTED] Applications|Publishing
[EMAIL PROTECTED] English
[EMAIL PROTECTED] ignore
+
[EMAIL PROTECTED] don't remove this comment.
+
[EMAIL PROTECTED]
+
+HINTS FOR STYLE
+
+* Do not forget to create @cindex entries for new sections of text.
+
+* Try not to use punctuation between an introductory sentence and
+ display material (music, example code).
+
+* Do not refer to LilyPond in the text. The reader knows what the
+ manual is about. If you do, capitalization is LilyPond.
+
+* If you explicitly refer to `lilypond', the program (or any other
+ command to be executed), say [EMAIL PROTECTED]'.
+
+* Do not explicitly refer to the reader/user. There is no one else
+ besides the reader and the writer.
+
+* Do not use abbreviations (don't, won't, etc.). If you do, use a
+ comma after it:
+
+ blabla blabla, i.e., blabla blabla
+
+* Avoid fluff (``Notice that,'' ``as you can see,'' ``Currently,'').
+
+* The above three suggestions refer to the formal Notation Manual
+ (chapters 5 and up). In the Tutorial, Example templates, and
+ Putting it all together, you may write more colloquially
+
+* The use of the word `illegal' is inappropriate in most cases. Say
+ `invalid' instead.
+
+* Avoid long stretches of input code. Noone is going to read them in
+ print. Instead refer to an example input file (@inputfileref), these
+ are clickable in HTML.
+
+* Abbrevs in caps, e.g., HTML, DVI, MIDI, etc.
+
+* Colon usage
+
+ 0. Do not use a colon to introduce examples, sentences just continue
+
+ in the display material.
+
+ 1. To introduce lists
+ 2. When beginning a quote: "So, he said,..."
+ This usage is rarer. Americans often just use a comma.
+ 3. When adding a defining example at the end of a sentence.
+
+* To produce good looking texinfo output (for both TTY and DVI) some
+ additional formatting rules should be followed.
+
+ . Do not use tabs. They expand to nothing in DVI output.
+
+ . Do not use spaces at the beginning of a line (except in @example
+ or @verbatim environments), and do not use more than a single space
+ between words. `makeinfo' copies the input lines verbatim without
+ removing those spaces.
+
+ . Variables or numbers which consist of a single character (probably
+ followed by a punctuation mark) should be tied properly, either to
+ the previous or the next word. Example:
+
+ The [EMAIL PROTECTED]@var{a} ...
+
+ . To get consistent indentation in the DVI output it is better to avoid
+ the @verbatim environment. Use the @example environment instead if
+ possible, but without extraneous indentation. For example, this
+
+ @example
+ foo {
+ bar
+ }
+ @end example
+
+ should be replaced with
+
+ @example
+ foo {
+ bar
+ }
+ @end example
+
+ where [EMAIL PROTECTED]' starts the line (without leading spaces).
+
+ . Use the `quote' option in @lilypond commands if possible.
+
+ . Do not compress the input vertically; this is, do not use
+
+ Beginning of logical unit
+ @example
+ ...
+ @end example
+ continuation of logical unit
+
+ but
+
+ Beginning of logical unit
+
+ @example
+ ...
+ @end example
+
+ @noindent
+ continuation of logical unit
+
+ This makes it easier to not forget [EMAIL PROTECTED]'.
+
+ . Non-ASCII characters which are in latin-1 should be directly used;
+ this is, don't say [EMAIL PROTECTED]' but `Baßtuba'. This ensures that
+ all such characters appear in all output formats.
+
[EMAIL PROTECTED] ignore
+
[EMAIL PROTECTED]
+This document is also available in
@uref{source/Documentation/user/out-www/lilypond.pdf,PDF}.
[EMAIL PROTECTED] ifhtml
+
+
[EMAIL PROTECTED] en
[EMAIL PROTECTED] utf-8
+
[EMAIL PROTECTED] fn cp
[EMAIL PROTECTED] ky cp
[EMAIL PROTECTED] pg cp
[EMAIL PROTECTED] tp cp
[EMAIL PROTECTED] vr cp
+
+
[EMAIL PROTECTED]
+
[EMAIL PROTECTED]
[EMAIL PROTECTED] LilyPond
[EMAIL PROTECTED] The music typesetter
[EMAIL PROTECTED] The LilyPond development team
+
+
+
+Copyright @copyright{} 1999--2005 by the authors
+
+ Permission is granted to copy, distribute and/or modify this document
+ under the terms of the GNU Free Documentation License, Version 1.1
+ or any later version published by the Free Software Foundation;
+ with no Invariant Sections.
+ A copy of the license is included in the section entitled ``GNU
+ Free Documentation License''.
+
[EMAIL PROTECTED] 20pt
+
[EMAIL PROTECTED] Not yet debugged or reported. This crashes gs-8.01:
[EMAIL PROTECTED] compiling gs-8.01 right now... -- jcn
[EMAIL PROTECTED]
+\score {
+ \context Lyrics {
+ \override Score.RehearsalMark #'self-alignment-X = #LEFT
+ \override Score.RehearsalMark #'font-size = #-2
+ \mark #(ly:export (string-append
+ "(For LilyPond version " (lilypond-version) ")"))
+ s2
+ }
+ \layout {
+ indent = 0.0\pt
+ raggedright = ##t
+ }
+}
[EMAIL PROTECTED] lilypond
+
[EMAIL PROTECTED] titlepage
+
+
[EMAIL PROTECTED]
+This file documents GNU LilyPond.
+
+Copyright 1999--2005 by the authors
+
+ Permission is granted to copy, distribute and/or modify this document
+ under the terms of the GNU Free Documentation License, Version 1.1
+ or any later version published by the Free Software Foundation;
+ with no Invariant Sections.
+ A copy of the license is included in the section entitled ``GNU
+ Free Documentation License''.
+
[EMAIL PROTECTED] ifnottex
+
+
[EMAIL PROTECTED]
[EMAIL PROTECTED] Top
[EMAIL PROTECTED] GNU LilyPond --- The music typesetter
[EMAIL PROTECTED] HJJ: Info needs [EMAIL PROTECTED]', which is a synonym for
[EMAIL PROTECTED]' in TeX.
+
+This is the user manual for GNU LilyPond 2.6.x series.
[EMAIL PROTECTED]
+(See the bottom of this page for the exact version number).
[EMAIL PROTECTED] ifhtml
+
[EMAIL PROTECTED] web site
[EMAIL PROTECTED] URL
+
+A further source of information is the website, which can be found at
[EMAIL PROTECTED]://@/www@/.lilypond@/.org/}. The website contains on-line
copies
+of this and other documentation.
+
[EMAIL PROTECTED] dedication.itely
+
[EMAIL PROTECTED]
+* Preface:: Preface.
+* Introduction:: What, Why, How.
+* Tutorial:: A tutorial introduction.
+* Example templates:: Larger examples.
+* Putting it all together:: Demonstrates real-life LilyPond usage.
+* Running LilyPond:: Operation.
+* Basic notation:: Standard musical notation.
+* Instrument-specific notation:: Notation that is only used for some
+ instruments.
+* Advanced notation:: Less frequently used notation.
+* Changing defaults:: Tuning output.
+* Output formats:: What LilyPond produces.
+
+* Interfaces for programmers::
+* LilyPond-book:: Integrating text and music.
+* Converting from other formats:: Converting to lilypond source format.
+* Literature list::
+* Scheme tutorial::
+* Notation manual details::
+* Point and click::
+* Cheat sheet::
+* GNU Free Documentation License:: FDL.
+* LilyPond index::
[EMAIL PROTECTED] menu
[EMAIL PROTECTED] ifnottex
+
[EMAIL PROTECTED]
+
+
[EMAIL PROTECTED] macros.itexi
[EMAIL PROTECTED] preface.itely
[EMAIL PROTECTED] introduction.itely
[EMAIL PROTECTED] tutorial.itely
[EMAIL PROTECTED] examples.itely
[EMAIL PROTECTED] putting.itely
[EMAIL PROTECTED] invoking.itely
[EMAIL PROTECTED] basic-notation.itely
[EMAIL PROTECTED] instrument-notation.itely
[EMAIL PROTECTED] advanced-notation.itely
[EMAIL PROTECTED] changing-defaults.itely
[EMAIL PROTECTED] global.itely
+
[EMAIL PROTECTED] programming-interface.itely
[EMAIL PROTECTED] lilypond-book.itely
[EMAIL PROTECTED] converters.itely
+
+
[EMAIL PROTECTED] FIXME: Index has two alphabetically sorted lists @code vs
plain?
+
+
[EMAIL PROTECTED] literature.itely
[EMAIL PROTECTED] scheme-tutorial.itely
[EMAIL PROTECTED] notation-appendices.itely
[EMAIL PROTECTED] point-and-click.itely
[EMAIL PROTECTED] cheatsheet.itely
[EMAIL PROTECTED] fdl.itexi
+
[EMAIL PROTECTED] LilyPond index
[EMAIL PROTECTED] LilyPond index
+
[EMAIL PROTECTED] cp
+
[EMAIL PROTECTED]
_______________________________________________
Lilypond-cvs mailing list
[email protected]
http://lists.gnu.org/mailman/listinfo/lilypond-cvs
