<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<!-- header_tag -->
<html lang="en">
<head>
<title>Suggestions for writing LilyPond input files - GNU LilyPond Learning Manual</title>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
<meta name="description" content="GNU LilyPond Learning Manual">
<meta name="generator" content="makeinfo 4.11">
<link title="Top" rel="start" href="index.es.html#Top">
<link rel="up" href="Working-on-LilyPond-projects.es.html#Working-on-LilyPond-projects" title="Working on LilyPond projects">
<link rel="next" href="When-things-don_0027t-work.es.html#When-things-don_0027t-work" title="When things don't work">
<link href="http://www.gnu.org/software/texinfo/" rel="generator-home" title="Texinfo Homepage">
<!--
Copyright (C) 1999--2007 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''.
-->
<meta http-equiv="Content-Style-Type" content="text/css">
<style type="text/css"><!--
pre.display { font-family:inherit }
pre.format { font-family:inherit }
pre.smalldisplay { font-family:inherit; font-size:smaller }
pre.smallformat { font-family:inherit; font-size:smaller }
pre.smallexample { font-size:smaller }
pre.smalllisp { font-size:smaller }
span.sc { font-variant:small-caps }
span.roman { font-family:serif; font-weight:normal; }
span.sansserif { font-family:sans-serif; font-weight:normal; }
hr { border:0; height:1; color: #000000; background-color: #000000; }
/* hr {
border: none;
height: 1px;
color: #666666;
background-color: #666666;
}
body {
border-left: 1px solid #666666;
border-right: 1px solid #666666;
color: #332d28;
margin-right: auto;
margin-left: auto;
width: 60em;
list-style-type: square;
font-family: Arial,Helvetica,sans-serif;
padding-right: 1em;
padding-left: 1em;
}
a {
border-bottom: 1px dashed #344242;
text-decoration: none;
color: #344242;
}
a:link {
text-decoration: none;
}
a:visited {
border-bottom: 1px dashed #666666;
color: #666666;
}
a:active {
border-bottom: 1px solid #00cccc;
color: #00cccc;
}
a:hover {
border-bottom: 1px solid #1d7b85;
color: #1d7b85;
}
blockquote {
border: 1px solid #cccccc;
padding: 3px;
width: 40em;
}
.node {
border-left: 1px solid #666666;
margin: -0.5em 0px 1em;
padding: 2px 1px 0px;
font-style: italic;
}
.node a {
border: none;
text-decoration: underline;
font-style: normal;
font-weight: bold;
}
.verbatim {
font-family: "Courier New",Courier,monospace;
}
.unnumberedsubsubsec {
font-size: large;
color: #1d7b85;
}
.subsubheading {
font-size: large;
color: #3b220d;
}
.contents {
border: 1px dashed #339999;
margin: 3px 2em;
list-style-type: square;
padding-right: 1em;
width: 40em;
background-color: #fcfff9;
}
.contents a {
border-bottom: 1px dashed #423d34;
text-decoration: none;
color: #423d34;
}
.contents a:visited {
border-bottom: 1px dashed #666666;
color: #666666;
}
.contents a:active {
border-bottom: 1px solid #f0d86d;
color: #f0d86d;
}
.contents a:hover {
border-bottom: 1px solid #3b220d;
color: #3b220d;
}
.menu {
border-left: 1px dashed #339999;
margin: 3px 2em 1em;
list-style-type: square;
padding-left: 1.4em;
width: 40em;
}
.unnumbered {
}
h2 {
font-size: x-large;
color: #1d7b85;
}
*/
--></style>
</head>
<BODY BGCOLOR=WHITE TEXT=BLACK>
<div class="node">
<p>
<a name="Suggestions-for-writing-LilyPond-input-files"></a>
Next: <a rel="next" accesskey="n" href="When-things-don_0027t-work.es.html#When-things-don_0027t-work">When things don't work</a>,
Up: <a rel="up" accesskey="u" href="Working-on-LilyPond-projects.es.html#Working-on-LilyPond-projects">Working on LilyPond projects</a>
<hr>
</div>
<h3 class="section">5.1 Suggestions for writing LilyPond input files</h3>
<p>Now you're ready to begin writing larger LilyPond input files –
not just the little examples in the tutorial, but whole pieces.
But how should you go about doing it?
<p>As long as LilyPond can understand your input files and produce
the output that you want, it doesn't matter what your input files
look like. However, there are a few other things to consider when
writing LilyPond input files.
<ul>
<li>What if you make a mistake? The structure of a LilyPond
file can make certain errors easier (or harder) to find.
<li>What if you want to share your input files with somebody
else? In fact, what if you want to alter your own input files in
a few years? Some LilyPond input files are understandable at
first glance; others may leave you scratching your head
for an hour.
<li>What if you want to upgrade your LilyPond file for use
with a later version of LilyPond? The input syntax changes
occasionally as LilyPond improves. Most changes can be
done automatically with <code>convert-ly</code>, but some changes
might require manual assistance. LilyPond input files can be
structured in order to be easier (or harder) to update.
</ul>
<ul class="menu">
<li><a accesskey="1" href="General-suggestions.es.html#General-suggestions">General suggestions</a>
<li><a accesskey="2" href="Typesetting-existing-music.es.html#Typesetting-existing-music">Typesetting existing music</a>
<li><a accesskey="3" href="Large-projects.es.html#Large-projects">Large projects</a>
<li><a accesskey="4" href="Saving-typing-with-variables-and-functions.es.html#Saving-typing-with-variables-and-functions">Saving typing with variables and functions</a>
<li><a accesskey="5" href="Style-sheets.es.html#Style-sheets">Style sheets</a>
</ul>
<!-- footer_tag --><br><hr>
<div class="node">
<p>
Next: <a rel="next" accesskey="n" href="When-things-don_0027t-work.es.html#When-things-don_0027t-work">When things don't work</a>,
Up: <a rel="up" accesskey="u" href="Working-on-LilyPond-projects.es.html#Working-on-LilyPond-projects">Working on LilyPond projects</a>
</div>
<div style="background-color: #e8ffe8; padding: 2; border: #c0ffc0 1px solid;">
<p>
<font size="-1">
Esta página corresponde a LilyPond-2.11.57 (rama de desarrollo).
<br>
<address>
Informe de los fallos a través de la lista en español <a href="http://es.groups.yahoo.com/group/lilypond-es/">lilypond-es</a>, o en inglés a través de <a href="http://post.gmane.org/post.php?group=gmane.comp.gnu.lilypond.bugs">http://post.gmane.org/post.php?group=gmane.comp.gnu.lilypond.bugs</a>. </address>
<br>
Se agradecen las <a href="http://lilypond.org/web/devel/participating/documentation-adding">sugerencias para la documentación</a>.
</font>
</p>
</div>
<P>
Otros idiomas: <a href="Suggestions-for-writing-LilyPond-input-files.fr.html">français</a>.
<BR>
</P>
</BODY></html>
