From 76f4bead34eb1beead7e51d0be2a5c0f021754e8 Mon Sep 17 00:00:00 2001 From: Francisco Vila Date: Fri, 7 Sep 2007 11:09:16 +0200 Subject: [PATCH] Spanish Program usage skeleton --- Documentation/es/user/advanced-notation.itely | 2 +- Documentation/es/user/converters.itely | 52 +++ Documentation/es/user/install.itely | 410 ++++++++++++++++++ Documentation/es/user/lilypond-book.itely | 111 +++++ Documentation/es/user/lilypond-program.tely | 162 +++++++ Documentation/es/user/literature.itely | 2 +- Documentation/es/user/non-music.itely | 2 +- .../es/user/notation-appendices.itely | 2 +- .../es/user/programming-interface.itely | 2 +- Documentation/es/user/running.itely | 64 +++ Documentation/es/user/scheme-tutorial.itely | 2 +- Documentation/es/user/setup.itely | 279 ++++++++++++ Documentation/es/user/spacing.itely | 2 +- Documentation/es/user/templates.itely | 2 +- 14 files changed, 1086 insertions(+), 8 deletions(-) create mode 100644 Documentation/es/user/converters.itely create mode 100644 Documentation/es/user/install.itely create mode 100644 Documentation/es/user/lilypond-book.itely create mode 100644 Documentation/es/user/lilypond-program.tely create mode 100644 Documentation/es/user/running.itely create mode 100644 Documentation/es/user/setup.itely diff --git a/Documentation/es/user/advanced-notation.itely b/Documentation/es/user/advanced-notation.itely index 418c5b3ddc..0d0602c43b 100644 --- a/Documentation/es/user/advanced-notation.itely +++ b/Documentation/es/user/advanced-notation.itely @@ -1,7 +1,7 @@ @c -*- coding: utf-8; mode: texinfo; documentlanguage: es -*- @c This file is part of lilypond.tely @ignore - Translation of GIT committish: 21149cf2a4a3f620c5ed11989998bb0d4a4fc254 + Translation of GIT committish: aea9d21f9173e688c4b18b64ef4bf955cd8d2d82 When revising a translation, copy the HEAD committish of the diff --git a/Documentation/es/user/converters.itely b/Documentation/es/user/converters.itely new file mode 100644 index 0000000000..7036c7f949 --- /dev/null +++ b/Documentation/es/user/converters.itely @@ -0,0 +1,52 @@ +@c -*- coding: utf-8; mode: texinfo; documentlanguage: es -*- +@c This file is part of lilypond-program.tely +@ignore + Translation of GIT committish: aea9d21f9173e688c4b18b64ef4bf955cd8d2d82 + + + When revising a translation, copy the HEAD committish of the + version that you are working on. See TRANSLATION for details. +@end ignore + + +@node Converting from other formats +@chapter Converting from other formats + +UNTRANSLATED NODE: IGNORE ME + +@menu +* Invoking midi2ly:: +* Invoking musicxml2ly:: +* Invoking abc2ly:: +* Invoking etf2ly:: +* Generating LilyPond files:: +@end menu +@node Invoking midi2ly +@section Invoking @command{midi2ly} + +UNTRANSLATED NODE: IGNORE ME + +@node Invoking musicxml2ly +@section Invoking @code{musicxml2ly} + +UNTRANSLATED NODE: IGNORE ME + +@node Invoking abc2ly +@section Invoking @code{abc2ly} + +UNTRANSLATED NODE: IGNORE ME + +@node Invoking etf2ly +@section Invoking @command{etf2ly} + +UNTRANSLATED NODE: IGNORE ME + +@node Generating LilyPond files +@section Generating LilyPond files + +UNTRANSLATED NODE: IGNORE ME + + +-- SKELETON FILE -- +When you actually translate this file, please remove these lines as +well as all `UNTRANSLATED NODE: IGNORE ME' lines. diff --git a/Documentation/es/user/install.itely b/Documentation/es/user/install.itely new file mode 100644 index 0000000000..37d4cdd031 --- /dev/null +++ b/Documentation/es/user/install.itely @@ -0,0 +1,410 @@ +@c -*- coding: utf-8; mode: texinfo; -*- +@c This file is part of lilypond-program.tely +@ignore + Translation of GIT committish: FILL-IN-HEAD-COMMITTISH + + When revising a translation, copy the HEAD committish of the + version that you are working on. See TRANSLATION for details. +@end ignore + +@ifclear INSTALL +@node Install +@chapter Install +@end ifclear + +@c I don't know what this comment does. Remove? -gp +@ignore +@h tml + +@e nd html +@end ignore + +There are two sets of releases for LilyPond: stable releases, and +unstable development releases. Stable versions have an even-numbered +@q{minor} version number (i.e. 2.8, 2.10, 2.12, etc). Development +versions have an odd-numbered @q{minor} version number (i.e. 2.7, 2.9, +2.11, etc). + +Building LilyPond is a very involved process, so we @strong{highly} +recommend using the precompiled binaries. + +@menu +* Precompiled binaries:: +* Compiling from source:: +@end menu + + +@node Precompiled binaries +@section Precompiled binaries + +@subsection Downloading + +Check out @uref{http://lilypond.org/web/install/} for up to date +information on binary packages for your platform. If your operating +system is not covered on that general page, please see the complete list +at @uref{http://download.linuxaudio.org/lilypond/binaries/} + +We currently create binaries for + +@example +MacOSX-ppc +MacOSX-x86 +freebsd-64 +freebsd-x86 +linux-64 +linux-arm +linux-ppc +linux-x86 +win32-x86 +@end example + + +@c TRANSLATORS: +@c Please **do not** translate anything below this line. Users +@c should not be compiling LilyPond themselves; if they really +@c want to do so, they should be able to read the English docs, +@c because they'll probably need to ask questions in English +@c on the -devel list. -gp + +@node Compiling from source +@section Compiling from source + +@menu +* Downloading source code:: +* Requirements:: +* Building LilyPond:: +* Building documentation without compiling LilyPond:: +* Testing LilyPond:: +* Problems:: +@end menu + +@node Downloading source code +@subsection Downloading source code + +Download source + +@itemize @bullet +@item tarballs from +@uref{http://lilypond.org/download/} by HTTP. +@item tarballs from +@uref{http://download.linuxaudio.org/lilypond/} by HTTP. +@item +GIT from @uref{http://git.sv.gnu.org/gitweb/?p=lilypond.git;a=summary,git.sv.gnu.org} + +@example +git clone git://git.sv.gnu.org/lilypond.git +@end example + +The repository does not contain generated files. To create +@file{configure}, run +@example +./autogen.sh +@end example +@end itemize + +For information on packaging, see @uref{http://lilypond.org/devel}. + + +@node Requirements +@subsection Requirements + +@unnumberedsubsubsec Compilation + +In addition to the packages needed for running Lilypond (see below), you +need the following extra packages for building. + +When installing a binary package FOO, you may need to install the +FOO-devel, libFOO-dev or FOO-dev package too. + +@itemize + +@item @uref{http://fontforge.sf.net/,FontForge} 20060125 or newer. + +@item New Century Schoolbook fonts, as PFB files. These are shipped with +X11 and Ghostscript, and are named @file{c059033l.pfb} +@file{c059036l.pfb}, @file{c059013l.pfb} and @file{c059016l.pfb} + +@item @uref{http://www.xs4all.nl/~hanwen/mftrace/,mftrace} (1.1.19 or +newer); you may need to install some additional packages to get mftrace +to work. + +@item @uref{http://www.gnu.org/software/guile/guile.html,GUILE} (version +1.8.2 or newer). If you are installing binary packages, you may need to +install guile-devel or guile-dev or libguile-dev too. + +@item @uref{ftp://ftp.gnu.org/gnu/texinfo/,Texinfo} (version 4.8 or newer). + +@item @uref{http://gcc.gnu.org/, The GNU c++ compiler} (version 4.x or +newer). + +@item @uref{http://www.python.org,Python} (version 2.4 or newer) + +@item @uref{ftp://ftp.gnu.org/gnu/make/,GNU Make} (version 3.78 or newer). + +@item @uref{http://www.gnu.org/software/gettext/gettext.html,gettext}. + +@item @uref{http://www.gnu.org/software/flex/,Flex} + +@item @uref{http://www.perl.org/,Perl} + +@item @uref{http://www.gnu.org/software/flex/,GNU Bison} + +@item All packages required for running, including development packages with +header files and libraries. + +@end itemize + + +@unnumberedsubsubsec Running requirements + +Running LilyPond requires proper installation of the following software + +@itemize @bullet + +@item @uref{http://www.freetype.org/,Freetype} (version 2.1.10 or newer). +@item @uref{http://www.freetype.org/,FontConfig} (version 2.2). +@item @uref{http://www.pango.org/,Pango} (version 1.12 or newer). +@item @uref{http://www.gnu.org/software/guile/guile.html,GUILE} +(version 1.8.2 or newer), or patch 1.8.1 with +@uref{http://lilypond.org/vc/gub.darcs/patches/guile-1.8-rational.patch}. +@item @uref{http://www.python.org,Python} (version 2.4 or newer). +@item @uref{http://www.ghostscript.com,Ghostscript} (version 8.15 or +newer. 8.50 recommended) +@item Dejaview. (This is normally installed by default) +@end itemize + +International fonts are required to create music with international text +or lyrics. + + +@unnumberedsubsubsec Building documentation + +You can view the documentation online at +@uref{http://lilypond.org/doc/}, but you can also build it locally. +This process requires a successful compile of lilypond. The +documentation is built by issuing + +@example +make web +@end example + +Building the website requires some additional tools and packages + +@itemize @bullet +@item The @uref{http://netpbm.sourceforge.net/,netpbm utilities} +@item ImageMagick +@item International fonts (see input/regression/utf-8.ly for hints +about which font packages are necessary for your platform) +@item Ghostscript, 8.50 with the patch from +@uref{http://bugs.ghostscript.com/show_bug.cgi?id=688154} +and the patch from +@uref{http://bugs.ghostscript.com/show_bug.cgi?id=688017}. +@end itemize + +The HTML files can be installed into the standard documentation path +by issuing + +@example +make out=www web-install +@end example + + +@node Building LilyPond +@subsection Building LilyPond + +@unnumberedsubsubsec Compiling + +To install GNU LilyPond, type + +@example +gunzip -c lilypond-x.y.z | tar xf - +cd lilypond-x.y.z +./configure # run with --help for applicable options +make +make install +@end example + +If you are not root, you should choose a @code{--prefix} argument that +points into your home directory, e.g. + +@example +./configure --prefix=$HOME/usr +@end example + + +@unnumberedsubsubsec Compiling for multiple platforms + +If you want to build multiple versions of LilyPond with different +configuration settings, you can use the @code{--enable-config=CONF} +option of configure. You should use @samp{make conf=CONF} to generate +the output in @file{out-CONF}. Example: Suppose you want to build +with and without profiling, then use the following for the normal +build + +@example +./configure --prefix=$HOME/usr/ --enable-checking +make +make install +@end example + +and for the profiling version, specify a different configuration + +@example +./configure --prefix=$HOME/usr/ --enable-profiling --enable-config=prof --disable-checking +make conf=prof +make conf=prof install +@end example + + +@node Building documentation without compiling LilyPond +@subsection Building documentation without compiling LilyPond + +The documentation can be built locally without compiling lilypond from +scratch. + +From a fresh git checkout, do + +@example +./autogen.sh % ignore any warning messages +cp GNUmakefile.in GNUmakefile +make -C python +nice make LILYPOND_EXTERNAL_BINARY=/path/to/bin/lilypond web +% change the lilypond directory as appropriate +@end example + +Please note that this may break sometimes -- for example, if a new +feature is added with a test file in input/regression, even the latest +unstable Lily will fail to build the docs. + +You may build the manual ( Documentation/user/ ) without building all +the input/* stuff. + + +@node Testing LilyPond +@subsection Testing LilyPond + +@html + +@end html + +LilyPond comes with an extensive suite that exercises the entire +program. This suite can be used to automatically check the impact of a +change. This is done as follows + +@example +make test-baseline +@emph{## apply your changes, compile} +make check +@end example + +This will leave an HTML page @file{out/test-results/index.html}. This +page shows all the important differences that your change introduced, +whether in the layout, MIDI, performance or error reporting. + +To rerun tests, use + +@example +make test-redo @emph{## redo files differing from baseline} +make test-clean @emph{## remove all test results} +@end example + +@noindent +and then run @code{make check} again. + +For tracking memory usage as part of this test, you will need GUILE +CVS; especially the following patch: +@uref{http://lilypond.org/vc/gub.darcs/patches/guile-1.9-gcstats.patch}. + +For checking the coverage of the test suite, do the following + +@example +./buildscripts/build-coverage.sh +@emph{# uncovered files, least covered first} +python ./buildscripts/coverage.py --summary out-cov/*.cc +@emph{# consecutive uncovered lines, longest first} +python ./buildscripts/coverage.py --uncovered out-cov/*.cc +@end example + + +@node Problems +@subsection Problems + +For help and questions use @email{lilypond-user@@gnu.org}. Send bug +reports to @email{bug-lilypond@@gnu.org}. + +Bugs that are not fault of LilyPond are documented here. + +@unnumberedsubsubsec Bison 1.875 + +There is a bug in bison-1.875: compilation fails with "parse error +before `goto'" in line 4922 due to a bug in bison. To fix, please +recompile bison 1.875 with the following fix + +@example +$ cd lily; make out/parser.cc +$ vi +4919 out/parser.cc +# append a semicolon to the line containing "__attribute__ ((__unused__)) +# save +$ make +@end example + + +@unnumberedsubsubsec Solaris + +Solaris7, ./configure + +@file{./configure} needs a POSIX compliant shell. On Solaris7, +@file{/bin/sh} is not yet POSIX compliant, but @file{/bin/ksh} or bash +is. Run configure like + +@example +CONFIG_SHELL=/bin/ksh ksh -c ./configure +@end example + +@noindent +or + +@example +CONFIG_SHELL=/bin/bash bash -c ./configure +@end example + +@unnumberedsubsubsec FreeBSD + +To use system fonts, dejaview must be installed. With the default +port, the fonts are installed in @file{usr/X11R6/lib/X11/fonts/dejavu}. + +Open the file @file{$LILYPONDBASE/usr/etc/fonts/local.conf} and add the +following line just after the @code{} line. (Adjust as necessary +for your hierarchy.) + +@example +/usr/X11R6/lib/X11/fonts +@end example + + +@unnumberedsubsubsec International fonts + +On MacOs X, all fonts are installed by default. However, finding all +system fonts requires a bit of configuration; see +@uref{http://lists.gnu.org/archive/html/lilypond-user/2007-03/msg00472.html, +this post} on the @code{lilypond-user} mailing list. + +On Linux, international fonts are installed by different means on +every distribution. We cannot list the exact commands or packages +that are necessary, as each distribution is different, and the exact +package names within each distribution changes. Here are some +hints, though: + +@verbatim +Red Hat Fedora + + taipeifonts fonts-xorg-truetype ttfonts-ja fonts-arabic \ + ttfonts-zh_CN fonts-ja fonts-hebrew + +Debian GNU/Linux + + apt-get install emacs-intl-fonts xfonts-intl-.* \ + ttf-kochi-gothic ttf-kochi-mincho \ + xfonts-bolkhov-75dpi xfonts-cronyx-100dpi xfonts-cronyx-75dpi +@end verbatim + diff --git a/Documentation/es/user/lilypond-book.itely b/Documentation/es/user/lilypond-book.itely new file mode 100644 index 0000000000..2227ba7bd6 --- /dev/null +++ b/Documentation/es/user/lilypond-book.itely @@ -0,0 +1,111 @@ +@c -*- coding: utf-8; mode: texinfo; documentlanguage: es -*- +@c This file is part of lilypond-program.tely +@ignore + Translation of GIT committish: aea9d21f9173e688c4b18b64ef4bf955cd8d2d82 + + + When revising a translation, copy the HEAD committish of the + version that you are working on. See TRANSLATION for details. +@end ignore + + +@node LilyPond-book +@chapter @command{lilypond-book}: Integrating text and music + +UNTRANSLATED NODE: IGNORE ME + +@menu +* An example of a musicological document:: +* Integrating music and text:: +* Music fragment options:: +* Invoking lilypond-book:: +* Filename extensions:: +* Alternate methods of mixing text and music:: +@end menu +@node An example of a musicological document +@section An example of a musicological document + +UNTRANSLATED NODE: IGNORE ME + +@subheading Input +@subheading Processing +@subheading Output +@node Integrating music and text +@section Integrating music and text + +UNTRANSLATED NODE: IGNORE ME + +@menu +* LaTeX:: +* Texinfo:: +* HTML:: +* DocBook:: +@end menu +@node LaTeX +@subsection @LaTeX{} + +UNTRANSLATED NODE: IGNORE ME + +@node Texinfo +@subsection Texinfo + +UNTRANSLATED NODE: IGNORE ME + +@node HTML +@subsection HTML + +UNTRANSLATED NODE: IGNORE ME + +@node DocBook +@subsection DocBook + +UNTRANSLATED NODE: IGNORE ME + +@subheading Common conventions +@subheading Including a LilyPond file +@subheading Including LilyPond code +@subheading Processing the DocBook document +@node Music fragment options +@section Music fragment options + +UNTRANSLATED NODE: IGNORE ME + +@node Invoking lilypond-book +@section Invoking @command{lilypond-book} + +UNTRANSLATED NODE: IGNORE ME + +@node Filename extensions +@section Filename extensions + +UNTRANSLATED NODE: IGNORE ME + +@node Alternate methods of mixing text and music +@section Alternative methods of mixing text and music + +UNTRANSLATED NODE: IGNORE ME + +@menu +* Many quotes from a large score:: +* Inserting LilyPond output into OpenOffice.org:: +* Inserting LilyPond output into other programs:: +@end menu +@node Many quotes from a large score +@subsection Many quotes from a large score + +UNTRANSLATED NODE: IGNORE ME + +@node Inserting LilyPond output into OpenOffice.org +@subsection Inserting LilyPond output into OpenOffice.org + +UNTRANSLATED NODE: IGNORE ME + +@node Inserting LilyPond output into other programs +@subsection Inserting LilyPond output into other programs + +UNTRANSLATED NODE: IGNORE ME + + +-- SKELETON FILE -- +When you actually translate this file, please remove these lines as +well as all `UNTRANSLATED NODE: IGNORE ME' lines. diff --git a/Documentation/es/user/lilypond-program.tely b/Documentation/es/user/lilypond-program.tely new file mode 100644 index 0000000000..54b2e804a9 --- /dev/null +++ b/Documentation/es/user/lilypond-program.tely @@ -0,0 +1,162 @@ +\input texinfo @c -*- coding: utf-8; mode: texinfo; -*- +@ignore + Translation of GIT committish: aea9d21f9173e688c4b18b64ef4bf955cd8d2d82 + + When revising a translation, copy the HEAD committish of the + version that you are working on. See TRANSLATION for details. +@end ignore +@setfilename lilypond-program.info +@settitle GNU LilyPond program usage +@documentencoding UTF-8 +@documentlanguage en + +@iftex +@afourpaper +@c don't replace quotes with directed quotes +@tex +\gdef\SETtxicodequoteundirected{Foo} +\gdef\SETtxicodequotebacktick{Bla} +@end tex +@end iftex + + +@c don't remove this comment. +@ignore +@omfcreator Han-Wen Nienhuys, Jan Nieuwenhuizen and Graham Percival +@omfdescription User manual of the LilyPond music engraving system +@omftype program usage +@omfcategory Applications|Publishing +@omflanguage English +@end ignore + + +@ifhtml +Este documento está disponible también en formato +@uref{source/Documentation/user/lilypond-program.pdf,PDF} y como +@uref{source/Documentation/user/lilypond-program-big-page.html,una sola página}. +@end ifhtml + + +@c This produces the unified index +@syncodeindex fn cp +@syncodeindex vr cp + + +@finalout + +@titlepage +@title LilyPond +@subtitle El tipografiador de música +@titlefont{Utilización del programa} +@author El equipo de desarrollo de LilyPond + + +Copyright @copyright{} 1999--2007 por los autores + +@quotation +Se otorga permiso para copiar, distribuir y/o modificar este documento +bajo los términos de la licencia GNU Free Documentation License, versión 1.1 +cualquier otra posterior publicada por la Free Software Foundation; +sin ninguna de las secciones invariantes. +Se incluye una copia de la licencia en la sección ``GNU +Free Documentation License''. +@end quotation + +@vskip 20pt + +@lilypond[ragged-right] +\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 + } +} +@end lilypond + +@end titlepage + +@copying +Copyright @copyright{} 1999--2007 por los autores + +@quotation +Se otorga permiso para copiar, distribuir y/o modificar este documento +bajo los términos de la licencia GNU Free Documentation License, versión 1.1 +cualquier otra posterior publicada por la Free Software Foundation; +sin ninguna de las secciones invariantes. +Se incluye una copia de la licencia en la sección ``GNU +Free Documentation License''. +@end quotation +@end copying + +@ifnottex +Este archivo es la documentación de la utilización del programa GNU LilyPond. + +Copyright 1999--2007 por los autores + +@quotation +Se otorga permiso para copiar, distribuir y/o modificar este documento +bajo los términos de la licencia GNU Free Documentation License, versión 1.1 +cualquier otra posterior publicada por la Free Software Foundation; +sin ninguna de las secciones invariantes. +Se incluye una copia de la licencia en la sección ``GNU +Free Documentation License''. +@end quotation +@end ifnottex + +@ifnottex +@node Top +@top GNU LilyPond --- program usage +@c HJJ: Info needs `@top', which is a synonym for `@unnumbered' in TeX. + +El presente documento es el manual de utilización del programa GNU LilyPond, serie 2.11.x. +@ifhtml +(Consulte el final de la presente página para ver el número exacto de la versión). +@end ifhtml + +@cindex web site +@cindex URL + +Se puede ampliar información en +@uref{http://@/www@/.lilypond@/.org/}. La página web incluye copias en línea +de esta documentación y otras. + +@menu +* Install:: Cómo instalarlo o compilarlo. +* Setup:: Utilizar LilyPond con notros programas. +* Running LilyPond:: Funcionamiento. +* LilyPond-book:: Integrar texto y música. +* Converting from other formats:: Convertir al formato del código de entrada de lilypond. + +Apéndices + +* GNU Free Documentation License:: Licencia de este documento. +* LilyPond index:: +@end menu +@end ifnottex + +@contents + + +@include macros.itexi + +@include install.itely +@include setup.itely +@include running.itely +@include lilypond-book.itely +@include converters.itely + +@include fdl.itexi + +@node LilyPond index +@appendix LilyPond index + +@printindex cp + +@bye + diff --git a/Documentation/es/user/literature.itely b/Documentation/es/user/literature.itely index 8966c8e08a..971112d5a1 100644 --- a/Documentation/es/user/literature.itely +++ b/Documentation/es/user/literature.itely @@ -1,7 +1,7 @@ @c -*- coding: utf-8; mode: texinfo; documentlanguage: es -*- @c This file is part of lilypond.tely @ignore - Translation of GIT committish: 21149cf2a4a3f620c5ed11989998bb0d4a4fc254 + Translation of GIT committish: aea9d21f9173e688c4b18b64ef4bf955cd8d2d82 When revising a translation, copy the HEAD committish of the diff --git a/Documentation/es/user/non-music.itely b/Documentation/es/user/non-music.itely index df1bfaddd7..b5e500c235 100644 --- a/Documentation/es/user/non-music.itely +++ b/Documentation/es/user/non-music.itely @@ -1,7 +1,7 @@ @c -*- coding: utf-8; mode: texinfo; documentlanguage: es -*- @c This file is part of lilypond.tely @ignore - Translation of GIT committish: 21149cf2a4a3f620c5ed11989998bb0d4a4fc254 + Translation of GIT committish: aea9d21f9173e688c4b18b64ef4bf955cd8d2d82 When revising a translation, copy the HEAD committish of the diff --git a/Documentation/es/user/notation-appendices.itely b/Documentation/es/user/notation-appendices.itely index a85975e310..6d500c7e9e 100644 --- a/Documentation/es/user/notation-appendices.itely +++ b/Documentation/es/user/notation-appendices.itely @@ -1,7 +1,7 @@ @c -*- coding: utf-8; mode: texinfo; documentlanguage: es -*- @c This file is part of lilypond.tely @ignore - Translation of GIT committish: 21149cf2a4a3f620c5ed11989998bb0d4a4fc254 + Translation of GIT committish: aea9d21f9173e688c4b18b64ef4bf955cd8d2d82 When revising a translation, copy the HEAD committish of the diff --git a/Documentation/es/user/programming-interface.itely b/Documentation/es/user/programming-interface.itely index ee5ae6ed9d..87c1cf52af 100644 --- a/Documentation/es/user/programming-interface.itely +++ b/Documentation/es/user/programming-interface.itely @@ -1,7 +1,7 @@ @c -*- coding: utf-8; mode: texinfo; documentlanguage: es -*- @c This file is part of lilypond.tely @ignore - Translation of GIT committish: 21149cf2a4a3f620c5ed11989998bb0d4a4fc254 + Translation of GIT committish: aea9d21f9173e688c4b18b64ef4bf955cd8d2d82 When revising a translation, copy the HEAD committish of the diff --git a/Documentation/es/user/running.itely b/Documentation/es/user/running.itely new file mode 100644 index 0000000000..b287c3f9cc --- /dev/null +++ b/Documentation/es/user/running.itely @@ -0,0 +1,64 @@ +@c -*- coding: utf-8; mode: texinfo; documentlanguage: es -*- +@c This file is part of lilypond-program.tely +@ignore + Translation of GIT committish: aea9d21f9173e688c4b18b64ef4bf955cd8d2d82 + + + When revising a translation, copy the HEAD committish of the + version that you are working on. See TRANSLATION for details. +@end ignore + + +@node Running LilyPond +@chapter Running LilyPond + +UNTRANSLATED NODE: IGNORE ME + +@menu +* Normal usage:: +* Command-line usage:: +* Error messages:: +* Updating files with convert-ly:: +* Reporting bugs:: +@end menu +@node Normal usage +@section Normal usage + +UNTRANSLATED NODE: IGNORE ME + +@node Command-line usage +@section Command-line usage + +UNTRANSLATED NODE: IGNORE ME + +@subsection Invoking lilypond +@subsection Command line options +@subsection Environment variables +@node Error messages +@section Error messages + +UNTRANSLATED NODE: IGNORE ME + +@node Updating files with convert-ly +@section Updating with @command{convert-ly} + +UNTRANSLATED NODE: IGNORE ME + +@subsection Command line options +@menu +* Problems with convert-ly:: +@end menu +@node Problems with convert-ly +@subsection Problems with @code{convert-ly} + +UNTRANSLATED NODE: IGNORE ME + +@node Reporting bugs +@section Reporting bugs + +UNTRANSLATED NODE: IGNORE ME + + +-- SKELETON FILE -- +When you actually translate this file, please remove these lines as +well as all `UNTRANSLATED NODE: IGNORE ME' lines. diff --git a/Documentation/es/user/scheme-tutorial.itely b/Documentation/es/user/scheme-tutorial.itely index 798b0cf4ae..f12683dcf1 100644 --- a/Documentation/es/user/scheme-tutorial.itely +++ b/Documentation/es/user/scheme-tutorial.itely @@ -1,7 +1,7 @@ @c -*- coding: utf-8; mode: texinfo; documentlanguage: es -*- @c This file is part of lilypond.tely @ignore - Translation of GIT committish: 21149cf2a4a3f620c5ed11989998bb0d4a4fc254 + Translation of GIT committish: aea9d21f9173e688c4b18b64ef4bf955cd8d2d82 When revising a translation, copy the HEAD committish of the diff --git a/Documentation/es/user/setup.itely b/Documentation/es/user/setup.itely new file mode 100644 index 0000000000..dbbcb33da4 --- /dev/null +++ b/Documentation/es/user/setup.itely @@ -0,0 +1,279 @@ +@c -*- coding: utf-8; mode: texinfo; -*- +@c This file is part of lilypond-program.tely +@ignore + Translation of GIT committish: aea9d21f9173e688c4b18b64ef4bf955cd8d2d82 + + When revising a translation, copy the HEAD committish of the + version that you are working on. See TRANSLATION for details. +@end ignore + +@node Setup +@chapter Setup + +Este capítulo trata sobre varias opciones de configuración, posteriores a la instalación, para +LilyPond y otros programas. Este capítulo se puede tratar tranquilamente como una referencia: +lea solamente las secciones que le interesen. + +@menu +* Setup for specific Operating Systems:: +* Text editor support:: +* Point and click:: +@end menu + + +@node Setup for specific Operating Systems +@section Setup for specific Operating Systems + +Esta sección explica cómo realizar pùestas a punto adicionales para sistemas operativos +específicos. + +@menu +* MacOS X on the command-line:: +@end menu + + +@node MacOS X on the command-line +@subsection MacOS X on the command-line + +Los scripts (guiones como lilypond-book, convert-ly, abc2ly e incluso +el propio lilypond) van incluidos dentro del archivo de aplicación .app de MacOS X. Se pueden ejecutar a partir de +la línea de órdenes invocándolos directamente, p.ej. + +@example +@var{ruta/hacia}/LilyPond.app/Contents/Resources/bin/lilypond +@end example + +@noindent +Lo mismo vale para otros scripts de ese directorio, incluidos los guiones +lilypond-book, convert-ly, abc2ly, etc. + +Como alternativa, puede crear scripts que añadan la ruta +automáticamente. Cree un directorio para guardar estos guiones, + +@example +mkdir -p ~/bin +cd ~/bin +@end example + +Cree un archivo de nombre @code{lilypond} que contenga + +@example +exec @var{ruta/hacia}/LilyPond.app/Contents/Resources/bin/lilypond "$@@" +@end example + +Cree archivos similares @code{lilypond-book}, @code{convert-ly} y cualesquiera +otros programas de apoyo que vaya a utilizar (@code{abc2ly}, @code{midi2ly}, +etc). Sencillamente, sustituya el fragmento @code{bin/lilypond} por +@code{bin/convert-ly} (u otro nombre de programa) en el archivo anterior. + +Haga ejecutable al archivo, + +@example +chmod u+x lilypond +@end example + +Y ahora añada este directorio a su ruta de ejecución. Modifique (o cree) +un archivo llamado @code{.profile} en su directorio personal que contenga + +@example +export PATH=$PATH:~/bin +@end example + +@noindent +Este archivo debe acabar con una línea en blanco. + +Fíjese en que @var{ruta/hacia} será por lo general @code{/Applications/}. + + +@node Text editor support +@section Text editor support + +@cindex editors +@cindex vim +@cindex emacs +@cindex modes, editor +@cindex syntax coloring +@cindex coloring, syntax + +Existe apoyo por parte de varios editores de texto para LilyPond. + +@menu +* Emacs mode:: +* Vim mode:: +* jEdit:: +* TexShop:: +* TextMate:: +@end menu + +@node Emacs mode +@subsection Emacs mode + +Emacs tiene un @file{lilypond-mode}, que proporciona autocompleción de +teclado, sangrado, compensación de paréntesis específica de LilyPond +y resaltado de sintaxis con colores, útiles combinaciones de teclas para compilar y leer los manuales de LilyPond +utilizando Info. Si el @file{lilypond-mode} no está instalado en su sistema, +siga leyendo. + +Está incluido un modo de Emacs para escribir música y ejecutar LilyPond, en +el archivo del código fuente dentro del directorio @file{elisp}. Haga @command{make +install} para instalarlo dentro de @var{elispdir}. El archivo @file{lilypond-init.el} +se debe situar en @var{load-path}@file{/site-start.d/} o añadirse a su +@file{~/.emacs} o @file{~/.emacs.el}. + +Como usuario, puede querer añadir su ruta a las fuentes (p.ej. @file{~/site-lisp/}) a su +@var{load-path} añadiendo la siguiente línea (modificada) a su +@file{~/.emacs} + +@c any reason we do not advise: (push "~/site-lisp" load-path) +@example +(setq load-path (append (list (expand-file-name "~/site-lisp")) load-path)) +@end example + + +@node Vim mode +@subsection Vim mode + +Para @uref{http://@/www@/.vim@/.org,VIM} se proporciona un @file{vimrc}, +junto con herramientas de resaltado de sintaxis con colores. Se encuentra incluido un modo de Vim para escribir música y +ejecutar LilyPond, dentro del archivo de código fuente, en el directorio +@code{$VIM}. + +El tipo de archivo de LilyPond se detecta si el archivo +@file{~/.vim/filetype.vim} tiene el siguiente contenido + +@example +if exists("did_load_filetypes") + finish +endif +augroup filetypedetect + au! BufNewFile,BufRead *.ly setf lilypond +augroup END +@end example + +Incluya esta ruta añadiendo la siguiente línea a su +@file{~/.vimrc} + +@example +set runtimepath+=/usr/local/share/lilypond/$@{LILYPOND_VERSION@}/vim/ +@end example + +@noindent +donde $@{LILYPOND_VERSION@} es su versión de lilypond. Si Lilypond no se instaló +en su momento en @file{/usr/local/}, cambie esta ruta de la forma correspondiente. + + +@node jEdit +@subsection jEdit + +Creado como un plugin o añadido para el editor de texto @uref{http://@/www@/.jedit@/.org@/,jEdit}, +LilyPondTool es la herramienta basada en texto más rica en posibilidades para +editar partituras de LilyPond. Sus posibilidades incluyen un Asistente de Documentos con apoyo para las +letras de las canciones para preparar documentos más fácilmente, y un visor de PDF empotrado con apoyo +avanzado para el uso del cursor del ratón. Para ver capturas de pantalla, demostraciones e +instrucciones de instalación, visite +@uref{http://lilypondtool@/.organum@/.hu} + + +@node TexShop +@subsection TexShop + +El editor @uref{http://@/www@/.uoregon@/.edu/~koch/texshop/index@/.html,TexShop} +para Mac OS X se puede extender para la ejecución de LilyPond, lilypond-book y +convert-ly desde dentro del editor, usando las extensiones disponibles en +@uref{http://@/www@/.dimi@/.uniud@/.it/vitacolo/freesoftware@/.html}. + + +@node TextMate +@subsection TextMate + +Hay un tinglado de LilyPond para TextMate. Se puede instalar ejecutando + +@example +mkdir -p /Library/Application\ Support/TextMate/Bundles +cd /Library/Application\ Support/TextMate/Bundles +svn co http://macromates.com/svn/Bundles/trunk/Bundles/Lilypond.tmbundle/ +@end example + + + +@node Point and click +@section Point and click +@cindex point and click + + +Point and click (apuntar y pulsar con el ratón) le da la posibilidad de localizar notas del código de entrada pulsando sobre ellas +dentro del visor de PDF. Ello facilita encontrar los fragmentos de la entrada que producen +algún tipo de eeror en la partitura. + +Cuando esta funcionalidad está activada, LilyPond añade hiper-enlaces al archivo +PDF. Estos hiper-enlaces se envían al navegador de web, que a su vez abre un +editor de texto con el cursor situado en el lugar correcto. + +Para conseguir que esta cadena funciones, tendrá que configurar el visor de PDF de forma que +siga los hiper-enlaces usando el guión @file{lilypond-invoke-editor} proporcionado +con LilyPond. + +Para Xpdf sobre Unix, lo siguiente debe estar presente en +@file{xpdfrc}@footnote{En Unix, este archivo se encuentra o bien en +@file{/etc/xpdfrc} o como @file{.xpdfrc} en su directorio personal.} + +@example +urlCommand "lilypond-invoke-editor %s" +@end example + +El programa @file{lilypond-invoke-editor} es un pequeño programa de +apoyo. Invoca un editor para las URIs especiales de @code{textedit}, +y lanza un navegador de web para otros. Comprueba la variable de entorno +@code{EDITOR} en busca de los siguientes patrones, + +@table @code +@item emacs + esto invoca a +@example +emacsclient --no-wait +@var{line}:@var{column} @var{file} +@end example +@item vim + esto invoca a +@example +gvim --remote +:@var{line}:norm@var{char} @var{file} +@end example + +@item nedit +esto invoca a +@example + nc -noask +@var{line} @var{file}' +@end example +@end table + +La variable de entorno @code{LYEDITOR} se utiliza para sobreescibir esto. Contiene +la instrucción de línea de órdenes para abrir el editor, donde @code{%(file)s}, +@code{%(column)s}, @code{%(line)s} se sustituye por el archivo, columna y +línea respectivamente. El ajuste + +@example +emacsclient --no-wait +%(line)s:%(column)s %(file)s +@end example + +@noindent +para @code{LYEDITOR} equivale a la invocación estándar de +emacsclient. + + +@cindex archivo de salida, tamaño del + +Los enlaces de apuntar y pulsar aumentan significativamente el tamaño de los archivos de salida. Para +reducir el tamaño de los archivos PDF y PS, la posibilidad de apuntar y pulsar se puede desactivar +escribiendo + +@example +#(ly:set-option 'point-and-click #f) +@end example + +@noindent +dentro de un archivo @file{.ly}. De forma alternativa, puede pasarlo como una opción de +la linea de órdenes + +@example +lilypond -dno-point-and-click file.ly +@end example + diff --git a/Documentation/es/user/spacing.itely b/Documentation/es/user/spacing.itely index cf22d7224b..d31a673763 100644 --- a/Documentation/es/user/spacing.itely +++ b/Documentation/es/user/spacing.itely @@ -1,7 +1,7 @@ @c -*- coding: utf-8; mode: texinfo; documentlanguage: es -*- @c This file is part of lilypond.tely @ignore - Translation of GIT committish: 21149cf2a4a3f620c5ed11989998bb0d4a4fc254 + Translation of GIT committish: aea9d21f9173e688c4b18b64ef4bf955cd8d2d82 When revising a translation, copy the HEAD committish of the diff --git a/Documentation/es/user/templates.itely b/Documentation/es/user/templates.itely index eed9db776d..f2655dfa36 100644 --- a/Documentation/es/user/templates.itely +++ b/Documentation/es/user/templates.itely @@ -1,7 +1,7 @@ @c -*- coding: utf-8; mode: texinfo; documentlanguage: es -*- @c This file is part of lilypond.tely @ignore - Translation of GIT committish: 21149cf2a4a3f620c5ed11989998bb0d4a4fc254 + Translation of GIT committish: aea9d21f9173e688c4b18b64ef4bf955cd8d2d82 When revising a translation, copy the HEAD committish of the -- 2.39.5