logobossnation

1. El Arte De Decir No Pdf On Machine

GNU Free Documentation License 1.1 Version 1.3, 3 November 2008 Copyright © 2000, 2001, 2002, 2007, 2008 Free Software Foundation, Inc. Everyone is permitted to copy and distribute verbatim copies of this license document, but changing it is not allowed. PREAMBLE The purpose of this License is to make a manual, textbook, or other functional and useful document free in the sense of freedom: to assure everyone the effective freedom to copy and redistribute it, with or without modifying it, either commercially or noncommercially. Secondarily, this License preserves for the author and publisher a way to get credit for their work, while not being considered responsible for modifications made by others. This License is a kind of “copyleft”, which means that derivative works of the document must themselves be free in the same sense. It complements the GNU General Public License, which is a copyleft license designed for free software.

We have designed this License in order to use it for manuals for free software, because free software needs free documentation: a free program should come with manuals providing the same freedoms that the software does. But this License is not limited to software manuals; it can be used for any textual work, regardless of subject matter or whether it is published as a printed book. We recommend this License principally for works whose purpose is instruction or reference. APPLICABILITY AND DEFINITIONS This License applies to any manual or other work, in any medium, that contains a notice placed by the copyright holder saying it can be distributed under the terms of this License.

Such a notice grants a world-wide, royalty-free license, unlimited in duration, to use that work under the conditions stated herein. The “Document”, below, refers to any such manual or work. Any member of the public is a licensee, and is addressed as “you”. You accept the license if you copy, modify or distribute the work in a way requiring permission under copyright law. A “Modified Version” of the Document means any work containing the Document or a portion of it, either copied verbatim, or with modifications and/or translated into another language. A “Secondary Section” is a named appendix or a front-matter section of the Document that deals exclusively with the relationship of the publishers or authors of the Document to the Document’s overall subject (or to related matters) and contains nothing that could fall directly within that overall subject.

(Thus, if the Document is in part a textbook of mathematics, a Secondary Section may not explain any mathematics.) The relationship could be a matter of historical connection with the subject or with related matters, or of legal, commercial, philosophical, ethical or political position regarding them. The “Invariant Sections” are certain Secondary Sections whose titles are designated, as being those of Invariant Sections, in the notice that says that the Document is released under this License. If a section does not fit the above definition of Secondary then it is not allowed to be designated as Invariant. The Document may contain zero Invariant Sections. If the Document does not identify any Invariant Sections then there are none. The “Cover Texts” are certain short passages of text that are listed, as Front-Cover Texts or Back-Cover Texts, in the notice that says that the Document is released under this License.

A Front-Cover Text may be at most 5 words, and a Back-Cover Text may be at most 25 words. A “Transparent” copy of the Document means a machine-readable copy, represented in a format whose specification is available to the general public, that is suitable for revising the document straightforwardly with generic text editors or (for images composed of pixels) generic paint programs or (for drawings) some widely available drawing editor, and that is suitable for input to text formatters or for automatic translation to a variety of formats suitable for input to text formatters. A copy made in an otherwise Transparent file format whose markup, or absence of markup, has been arranged to thwart or discourage subsequent modification by readers is not Transparent. An image format is not Transparent if used for any substantial amount of text. A copy that is not “Transparent” is called “Opaque”. Examples of suitable formats for Transparent copies include plain ASCII without markup, Texinfo input format, LaTeX input format, SGML or XML using a publicly available DTD, and standard-conforming simple HTML, PostScript or PDF designed for human modification. Examples of transparent image formats include PNG, XCF and JPG.

Opaque formats include proprietary formats that can be read and edited only by proprietary word processors, SGML or XML for which the DTD and/or processing tools are not generally available, and the machine-generated HTML, PostScript or PDF produced by some word processors for output purposes only. The “Title Page” means, for a printed book, the title page itself, plus such following pages as are needed to hold, legibly, the material this License requires to appear in the title page. For works in formats which do not have any title page as such, “Title Page” means the text near the most prominent appearance of the work’s title, preceding the beginning of the body of the text.

The “publisher” means any person or entity that distributes copies of the Document to the public. A section “Entitled XYZ” means a named subunit of the Document whose title either is precisely XYZ or contains XYZ in parentheses following text that translates XYZ in another language.

(Here XYZ stands for a specific section name mentioned below, such as “Acknowledgements”, “Dedications”, “Endorsements”, or “History”.) To “Preserve the Title” of such a section when you modify the Document means that it remains a section “Entitled XYZ” according to this definition. The Document may include Warranty Disclaimers next to the notice which states that this License applies to the Document. These Warranty Disclaimers are considered to be included by reference in this License, but only as regards disclaiming warranties: any other implication that these Warranty Disclaimers may have is void and has no effect on the meaning of this License. VERBATIM COPYING You may copy and distribute the Document in any medium, either commercially or noncommercially, provided that this License, the copyright notices, and the license notice saying this License applies to the Document are reproduced in all copies, and that you add no other conditions whatsoever to those of this License. You may not use technical measures to obstruct or control the reading or further copying of the copies you make or distribute. However, you may accept compensation in exchange for copies. If you distribute a large enough number of copies you must also follow the conditions in section 3.

You may also lend copies, under the same conditions stated above, and you may publicly display copies. COPYING IN QUANTITY If you publish printed copies (or copies in media that commonly have printed covers) of the Document, numbering more than 100, and the Document’s license notice requires Cover Texts, you must enclose the copies in covers that carry, clearly and legibly, all these Cover Texts: Front-Cover Texts on the front cover, and Back-Cover Texts on the back cover. Both covers must also clearly and legibly identify you as the publisher of these copies. The front cover must present the full title with all words of the title equally prominent and visible. You may add other material on the covers in addition. Copying with changes limited to the covers, as long as they preserve the title of the Document and satisfy these conditions, can be treated as verbatim copying in other respects.

El Arte De Decir No Pdf On Machine

If the required texts for either cover are too voluminous to fit legibly, you should put the first ones listed (as many as fit reasonably) on the actual cover, and continue the rest onto adjacent pages. If you publish or distribute Opaque copies of the Document numbering more than 100, you must either include a machine-readable Transparent copy along with each Opaque copy, or state in or with each Opaque copy a computer-network location from which the general network-using public has access to download using public-standard network protocols a complete Transparent copy of the Document, free of added material. If you use the latter option, you must take reasonably prudent steps, when you begin distribution of Opaque copies in quantity, to ensure that this Transparent copy will remain thus accessible at the stated location until at least one year after the last time you distribute an Opaque copy (directly or through your agents or retailers) of that edition to the public. It is requested, but not required, that you contact the authors of the Document well before redistributing any large number of copies, to give them a chance to provide you with an updated version of the Document. MODIFICATIONS You may copy and distribute a Modified Version of the Document under the conditions of sections 2 and 3 above, provided that you release the Modified Version under precisely this License, with the Modified Version filling the role of the Document, thus licensing distribution and modification of the Modified Version to whoever possesses a copy of it.

In addition, you must do these things in the Modified Version:. Use in the Title Page (and on the covers, if any) a title distinct from that of the Document, and from those of previous versions (which should, if there were any, be listed in the History section of the Document). You may use the same title as a previous version if the original publisher of that version gives permission.

List on the Title Page, as authors, one or more persons or entities responsible for authorship of the modifications in the Modified Version, together with at least five of the principal authors of the Document (all of its principal authors, if it has fewer than five), unless they release you from this requirement. State on the Title page the name of the publisher of the Modified Version, as the publisher. Preserve all the copyright notices of the Document. Add an appropriate copyright notice for your modifications adjacent to the other copyright notices. Include, immediately after the copyright notices, a license notice giving the public permission to use the Modified Version under the terms of this License, in the form shown in the Addendum below.

Preserve in that license notice the full lists of Invariant Sections and required Cover Texts given in the Document’s license notice. Include an unaltered copy of this License. Preserve the section Entitled “History”, Preserve its Title, and add to it an item stating at least the title, year, new authors, and publisher of the Modified Version as given on the Title Page. If there is no section Entitled “History” in the Document, create one stating the title, year, authors, and publisher of the Document as given on its Title Page, then add an item describing the Modified Version as stated in the previous sentence.

Preserve the network location, if any, given in the Document for public access to a Transparent copy of the Document, and likewise the network locations given in the Document for previous versions it was based on. These may be placed in the “History” section. You may omit a network location for a work that was published at least four years before the Document itself, or if the original publisher of the version it refers to gives permission. For any section Entitled “Acknowledgements” or “Dedications”, Preserve the Title of the section, and preserve in the section all the substance and tone of each of the contributor acknowledgements and/or dedications given therein.

Preserve all the Invariant Sections of the Document, unaltered in their text and in their titles. Section numbers or the equivalent are not considered part of the section titles.

Delete any section Entitled “Endorsements”. Such a section may not be included in the Modified Version. Do not retitle any existing section to be Entitled “Endorsements” or to conflict in title with any Invariant Section. Preserve any Warranty Disclaimers.

If the Modified Version includes new front-matter sections or appendices that qualify as Secondary Sections and contain no material copied from the Document, you may at your option designate some or all of these sections as invariant. To do this, add their titles to the list of Invariant Sections in the Modified Version’s license notice. These titles must be distinct from any other section titles. You may add a section Entitled “Endorsements”, provided it contains nothing but endorsements of your Modified Version by various parties—for example, statements of peer review or that the text has been approved by an organization as the authoritative definition of a standard. You may add a passage of up to five words as a Front-Cover Text, and a passage of up to 25 words as a Back-Cover Text, to the end of the list of Cover Texts in the Modified Version.

Only one passage of Front-Cover Text and one of Back-Cover Text may be added by (or through arrangements made by) any one entity. If the Document already includes a cover text for the same cover, previously added by you or by arrangement made by the same entity you are acting on behalf of, you may not add another; but you may replace the old one, on explicit permission from the previous publisher that added the old one. The author(s) and publisher(s) of the Document do not by this License give permission to use their names for publicity for or to assert or imply endorsement of any Modified Version. COMBINING DOCUMENTS You may combine the Document with other documents released under this License, under the terms defined in section 4 above for modified versions, provided that you include in the combination all of the Invariant Sections of all of the original documents, unmodified, and list them all as Invariant Sections of your combined work in its license notice, and that you preserve all their Warranty Disclaimers.

The combined work need only contain one copy of this License, and multiple identical Invariant Sections may be replaced with a single copy. If there are multiple Invariant Sections with the same name but different contents, make the title of each such section unique by adding at the end of it, in parentheses, the name of the original author or publisher of that section if known, or else a unique number. Make the same adjustment to the section titles in the list of Invariant Sections in the license notice of the combined work.

In the combination, you must combine any sections Entitled “History” in the various original documents, forming one section Entitled “History”; likewise combine any sections Entitled “Acknowledgements”, and any sections Entitled “Dedications”. You must delete all sections Entitled “Endorsements.”. COLLECTIONS OF DOCUMENTS You may make a collection consisting of the Document and other documents released under this License, and replace the individual copies of this License in the various documents with a single copy that is included in the collection, provided that you follow the rules of this License for verbatim copying of each of the documents in all other respects. You may extract a single document from such a collection, and distribute it individually under this License, provided you insert a copy of this License into the extracted document, and follow this License in all other respects regarding verbatim copying of that document. AGGREGATION WITH INDEPENDENT WORKS A compilation of the Document or its derivatives with other separate and independent documents or works, in or on a volume of a storage or distribution medium, is called an “aggregate” if the copyright resulting from the compilation is not used to limit the legal rights of the compilation’s users beyond what the individual works permit. When the Document is included in an aggregate, this License does not apply to the other works in the aggregate which are not themselves derivative works of the Document. If the Cover Text requirement of section 3 is applicable to these copies of the Document, then if the Document is less than one half of the entire aggregate, the Document’s Cover Texts may be placed on covers that bracket the Document within the aggregate, or the electronic equivalent of covers if the Document is in electronic form.

Otherwise they must appear on printed covers that bracket the whole aggregate. TRANSLATION Translation is considered a kind of modification, so you may distribute translations of the Document under the terms of section 4. Replacing Invariant Sections with translations requires special permission from their copyright holders, but you may include translations of some or all Invariant Sections in addition to the original versions of these Invariant Sections.

You may include a translation of this License, and all the license notices in the Document, and any Warranty Disclaimers, provided that you also include the original English version of this License and the original versions of those notices and disclaimers. In case of a disagreement between the translation and the original version of this License or a notice or disclaimer, the original version will prevail. If a section in the Document is Entitled “Acknowledgements”, “Dedications”, or “History”, the requirement (section 4) to Preserve its Title (section 1) will typically require changing the actual title. TERMINATION You may not copy, modify, sublicense, or distribute the Document except as expressly provided under this License.

Any attempt otherwise to copy, modify, sublicense, or distribute it is void, and will automatically terminate your rights under this License. However, if you cease all violation of this License, then your license from a particular copyright holder is reinstated (a) provisionally, unless and until the copyright holder explicitly and finally terminates your license, and (b) permanently, if the copyright holder fails to notify you of the violation by some reasonable means prior to 60 days after the cessation. Moreover, your license from a particular copyright holder is reinstated permanently if the copyright holder notifies you of the violation by some reasonable means, this is the first time you have received notice of violation of this License (for any work) from that copyright holder, and you cure the violation prior to 30 days after your receipt of the notice. Termination of your rights under this section does not terminate the licenses of parties who have received copies or rights from you under this License.

If your rights have been terminated and not permanently reinstated, receipt of a copy of some or all of the same material does not give you any rights to use it. FUTURE REVISIONS OF THIS LICENSE The Free Software Foundation may publish new, revised versions of the GNU Free Documentation License from time to time. Such new versions will be similar in spirit to the present version, but may differ in detail to address new problems or concerns. Each version of the License is given a distinguishing version number. If the Document specifies that a particular numbered version of this License “or any later version” applies to it, you have the option of following the terms and conditions either of that specified version or of any later version that has been published (not as a draft) by the Free Software Foundation.

If the Document does not specify a version number of this License, you may choose any version ever published (not as a draft) by the Free Software Foundation. If the Document specifies that a proxy can decide which future versions of this License can be used, that proxy’s public statement of acceptance of a version permanently authorizes you to choose that version for the Document. RELICENSING “Massive Multiauthor Collaboration Site” (or “MMC Site”) means any World Wide Web server that publishes copyrightable works and also provides prominent facilities for anybody to edit those works. A public wiki that anybody can edit is an example of such a server.

A “Massive Multiauthor Collaboration” (or “MMC”) contained in the site means any set of copyrightable works thus published on the MMC site. “CC-BY-SA” means the Creative Commons Attribution-Share Alike 3.0 license published by Creative Commons Corporation, a not-for-profit corporation with a principal place of business in San Francisco, California, as well as future copyleft versions of that license published by that same organization. “Incorporate” means to publish or republish a Document, in whole or in part, as part of another Document. An MMC is “eligible for relicensing” if it is licensed under this License, and if all works that were first published under this License somewhere other than this MMC, and subsequently incorporated in whole or in part into the MMC, (1) had no cover texts or invariant sections, and (2) were thus incorporated prior to November 1, 2008.

The operator of an MMC Site may republish an MMC contained in the site under CC-BY-SA on the same site at any time before August 1, 2009, provided the MMC is eligible for relicensing. ADDENDUM: How to use this License for your documents To use this License in a document you have written, include a copy of the License in the document and put the following copyright and license notices just after the title page: Copyright (C) year your name. Permission is granted to copy, distribute and/or modify this document under the terms of the GNU Free Documentation License, Version 1.3 or any later version published by the Free Software Foundation; with no Invariant Sections, no Front-Cover Texts, and no Back-Cover Texts. A copy of the license is included in the section entitled ``GNU Free Documentation License'. If you have Invariant Sections, Front-Cover Texts and Back-Cover Texts, replace the “withTexts.” line with this: with the Invariant Sections being list their titles, with the Front-Cover Texts being list, and with the Back-Cover Texts being list.

If you have Invariant Sections without Cover Texts, or some other combination of the three, merge those two alternatives to suit the situation. If your document contains nontrivial examples of program code, we recommend releasing these examples in parallel under your choice of free software license, such as the GNU General Public License, to permit their use in free software. What is Google Summer of Code? Is a global program that offers students stipends to write code for free software and open source projects during the summer. For three months students work to complete a given task as part of the project’s community and under the guidance of experienced mentors. The program is an excellent opportunity for students to gain experience with real-world software development and make a contribution that benefits everyone.

It brings new contributors to LilyPond and enables students who are already involved to become more involved. LilyPond participates in GSoC as part of the.

We have had GSoC participants in 2012, 2015, 2016 and 2017. This site will be updated in time before the 2018 season will start.

Project Ideas List Below is a list of GSoC project ideas (last update: May 2017), but if you have other ideas for a project you may complete within the three months of the program you’re welcome to make a suggestion on our developer mailing list (see ). There are a number of areas where LilyPond could be improved, and our development team is always willing to help those who would like to tackle a project similar to those listed below. As mentor availability varies from project to project and from year to year it is wise to get in touch with us as early as possible. A full list of all the current open issues can be found. Adopt the SMuFL music font encoding standard For several years now a new standard for music fonts has been around:, which is also discussed as becoming part of a future W3C standard for music encoding. As a FLOSS tool LilyPond should adhere to such an open standard instead of using an isolated solution like it does today. Adopting SMuFL will help integrating LilyPond with the world of music notation software and eventually give LilyPond users access to a wider selection of notation fonts.

Making LilyPond compliant to SMuFL includes remapping of the glyphs that are built from METAFONT sources, adjusting the glyphs’ metrics to SMuFL’s specifications, and finally updating the way LilyPond looks up and positions the glyphs. As an optional part of this project LilyPond’s font loading mechanism could be modified to use notation fonts installed as system fonts instead of inside the LilyPond installation. Difficulty: Easy/medium Requirements: C and willingness to get familiar with LilyPond internals. Recommended: Interest and experience in working with font files. A little bit of METAFONT.

Mentors: Werner Lemberg, Abraham Lee Adding variants of font glyphs. Adding ‘on’ and ‘between’ staff-line variants.

Shorter and narrower variants of some glyphs for example, accidentals. Another, more specific example could be an ancient notation breve notehead coming in two variants one with a small or big ‘hole’ within it. Difficulty: easy Requirements: MetaFont, C, good eye for details Recommended knowledge: basic LilyPond knowledge Mentor: Werner Lemberg Contemporary Notation LilyPond is very good at creating non-standard notation. Having to code every graphical element instead of simply drawing it may seem cumbersome but is in fact a strong asset.

New notational functionality can be provided with consistent appearance, automatic layout and a natural syntactic interface. Within the library system the student will create a fundamental infrastructure and building blocks to make creating contemporary notation easier. Additionally (at least) one concrete package is developed to cover specific contemporary notation, such as for example the style of a given composer, extended playing techniques for a specific instrument or a certain category of effects. Difficulty: medium Requirements: Scheme (interaction with LilyPond internals), contemporary notation techniques Recommended: sense of building hierarchical frameworks Mentors: NN, Urs Liska Rewrite LibreOffice LilyPond Extension with Python The extension made it possible to conveniently include LilyPond score snippets in OpenOffice.org/LibreOffice Writer, Draw and Impress documents while keeping source and image together.

After many years without development an initial effort has started to make the extension compatible again with current versions of LibreOffice and LilyPond. However, as the LibreOffice ecosystem has changed substantially it is now possible to rewrite the extension with Python and PyQt. This will not only be more powerful in general but will allow the integration of functionality from, such as for example syntax highlighting, entry helpers, score wizards or musical transformations.

Difficulty: easy/medium Requirements: Python, PyQt, LilyPond basics, LibreOffice extension basics Recommended knowledge: Familiarity with Frescobaldi code based or willingness to learn during bonding period Mentor(s): Joram Berger, Urs Liska, (Thorsten Behrens/LibreOffice) Automated testing and documentation for openLilyLib is an extension framework for LilyPond code providing a “snippets” repository and a suite of integrated packages such as for example page layout tools or scholarly annotations. It is very powerful and promising, but to really get off the ground two features are missing: automated testing and documentation generation. Automated testing is necessary to ensure modifications to functionality don’t break other functions within the library.

There is already some Automated Testing of the “snippets” repository with Github’s Travis server, but this has to be reconsidered and extended to cover the standalone packages too. In order to be usable for a wider range of LilyPond users on a “consumer level” openLilyLib needs proper documentation. This documentation has to be generated from the sources, so a system is needed that requires package authors to document the input files and provide additional usage examples, from which documentation is generated. Ideally but not necessarily this is implemented as a Git hook, i.e. Automatically upon each update to the repository. We don’t prescribe the tools and approaches to be used, but the most widely used language in the LilyPond domain is Python, so there would be some bias towards that. Alternatively a Scheme solution could be fine so generating the documentation would actually be triggered by “compiling” a certain LilyPond input file.

In general it is advisable to make use of proven concepts and tools from other languages. The eventual output of the documentation should be a static HTML site that can be viewed locally and/or uploaded to a website. But it would be beneficial if the tool would first generate an intermediate representation (e.g. A JSON file with additional media files) from which a Single Page Application could retrieve content for display on openLilyLib’s. Development of such a SPA can be part of the GSoC project, but is optional.

Difficulty: medium Requirements: Python or Scheme, static website generator(s) or (Node.js based) dynamic web application technology. Continuous Integration (can be learned during the bonding period) Mentors: Urs Liska, Matteo Ceccarello MusicXML Improving MusicXML import and export functions: File interchange between LilyPond and other applications using MusicXML is still a difficult matter.

To import MusicXML it has to be converted manually by the musicxml2ly script. Export to MusicXML is only available as a rudimentary feature inside Frescobaldi. In order to provide natural interchange between LilyPond and MusicXML based applications there’s the need of actual import functionality and a dedicated export backend. Importing XML shall provide file, line and column to add origin attributes to generated objects. That way point and click can be made available in Frescobaldi or other supported IDEs.

Exporting XML shall be realized with an exporter class like the MIDI export. This may be based on the work already done in by David Garfinkle. It should be checked if it is possible to use another XML library than the one provided by guile-2 in order to have this feature available in current LilyPond (which is based on guile-1.8).

Difficulty: medium Requirements: MusicXML, Python, Scheme, basic LilyPond knowledge Recommended: Familiarity with other scorewriters (for cross-testing) Mentor: Jan-Peter Voigt. Information for Applicants/Participants In order to have a satisfying experience with GSoC applicants are strongly advised to thoroughly read the following recommendations. Some of these are relevant for the application process, others for the time within the project. Read all applicable information on the program’s website, particularly the.

Make sure you fulfil all of Google’s prerequisites and are willing to join the program as a full-time commitment over the coding period of three months. Please get in touch with us as soon as possible if you are interested in applying with a project. Mentor availability may change without notice, project proposals may need fine-tuning, and many other reasons might require us to reject or ignore an application that hasn’t been discussed before. We do not know in advance how many “slots” we will have available for projects, so please be aware that you may find yourself in competition with other applicants or not. Interested or even enthusiastic response from our mentors is no guarantee of eventually being accepted, and not being accepted does not necessarily indicate a negative evaluation of your application. If we have to decide between different applicants there may be various aspects to consider. Integration in the LilyPond community is a fundamental part of GSoC, and we expect our students to make substantial efforts to become community members.

Within the bonding period we expect you to write a blog post about your project (either on or on any other blog) and to be active on our mailing lists, introducing yourself but also communicating about unrelated tasks. This goes beyond the mere setting up of a working environment and familiarizing yourself with the relevant code, but we think it is crucial for the GSoC project to be mutually satisfying. If you are accepted to the program you will have one mentor explicitly assigned to your project. With this mentor you will have to agree upon a communication strategy, be it emails, chatrooms, issue trackers or voice/video chats. Regular communication is absolutely crucial for the success of a GSoC project so you are stricly required to keep talking to your mentor. But keep in mind that your mentor has explicitly taken over the responsibility for your project, and while unlike you he isn’t paid for this activity you are still entitled to get regular attention from him.

In order to get support from your mentor you have to give him a chance to follow your progress and efforts. Therefore it is important to regularly commit your changes to the versioning repository you are working on. Don’t hesitate making unfinished code available because you are afraid of criticism, and don’t suppress questions because you think they might be considered stupid.

But ideally your code should at any time be accompanied by compatible testing code. Your mentor may not be able to properly assess your code by only reading it without the opportunity to apply it in a real example.

There is a list of inactive projects in the. We list projects there that are still considered valuable but for which there are currently no mentors available. Two LilyPond projects in Google Summer of Code 2016 April 23, 2016 We are happy to see two students, Nathan Chou and Jeffery Shivers, working on LilyPond as participants in the Google Summer of Code this year. We hope they produce great results and stay in the developer community afterwards. Nathan will tackle an annoying limitation, namely the unability of spanners to cross voices. His work will make a class of ugly workarounds obsolete. Jeffery will bring the ScholarLY package1 to production quality and add a LaTeX package to it, making it possible to create beautiful critical reports from data encoded directly in the LilyPond score.

Inactive Google Summer of Code project suggestions The following list describes GSoC projects that had been proposed in recent years and which are still considered valuable but for which we currently don’t have mentors available. Improve slurs and ties The engraving quality of slurs and ties is often unsatisfactory.

Ties ‘broken’ by clef or staff changes are not handled well. The project could include collecting and sorting examples of bad output, deciding on the intended output and writing code to improve them. Difficulty: hard Requirements: C, experience with writing heuristics Recommended knowledge: LilyPond knowledge, aesthetic sense Grace notes Fix problems with synchronization of grace notes. Grace notes can interfere with LilyPond’s timing and cause odd effects, especially when multiple staffs are used where some have grace notes and others don’t. This is one of the longest-standing and one of the more embarrassing in LilyPond.

Difficulty: medium Requirements: C, MIDI Recommended: familiarity with LilyPond internals Improve default beam positioning For regular, cross-staff, broken and kneed beams. Beaming should depend on context and neighbor notes (see section 2.2 of ). If possible also reduce beaming-computation time. Difficulty: medium Requirements: C, experience with writing heuristics Recommended knowledge: aesthetic sense Help improve compilation behavior Automatic code analysis tools, like valgrind memory leak detection or callgrind code profilers, provide valuable information about possible flaws in our C code. Cleaning up warnings would allow us to automate the rejection of any patch which introduced extra warnings. Difficulty: medium Requirements: C. LilyPond 2.19.16 released February 28, 2015 At long last, we are very happy to announce the release of LilyPond 2.19.16.

This release includes a number of enhancements, and contains some work in progress. You will have access to the very latest features, but some may be incomplete, and you may encounter bugs and crashes. If you require a stable version of LilyPond, we recommend using the 2.18 version. We would like to acknowledge and thank Masamichi Hosoda for making this release possible with his work on updating GUB, the build tool.

LilyPond 2.18.1 February 16, 2014 We have released updated manuals for LilyPond’s stable version, 2.18. The manuals are now for 2.18.1 and have a number of updates and improvements over 2.18.0. There will be a further release of 2.18 in the future (2.18.2), and this will include the updates to the manuals as well as some minor enhancements to the LilyPond core functionality. To summarise the current situation: stable LilyPond application: 2.18.0; stable LilyPond manuals: 2.18.1; development for both: 2.19.2. LilyPond 2.17.22 released! July 14, 2013 We are happy to announce the release of LilyPond 2.17.22.

This release contains the usual number of bugfixes and enhancements, and contains some work in progress. You will have access to the very latest features, but some may be incomplete, and you may encounter bugs and crashes.

If you require a stable version of LilyPond, we recommend using the 2.16 version. This update cures the issue with the Windows version crashing with a problem with positioning text. The LilyPond Report #28.

November 12, 2012 The focuses on the in Waltrop, Germany last August. Of course, there are also some musings on LilyPond triggered by the release of 2.16.0 and 2.17.0 occuring from that venue. There are also two monthly financial reports from David Kastrup whose work on LilyPond is by financial contributions from other developer and users (thank you!), and a report about experiences from using LilyPond internally. Come now; comments and contributions are warmly encouraged!

Release candidate 8 of 2.16 - LilyPond 2.15.41 released! July 4, 2012 LilyPond 2.15.41 is out; this is the eighth release candidate of the upcoming 2.16 stable release.

All users are invited to experiment with this version. New features since 2.14.2 are listed in the “Changes” manual on the website section about. There are no known Critical issues with this release.

If no Critical bugs are found, then the official 2.16.0 release will be on 18 July 2012. If you discover any problems, please send us. Release candidate 7 of 2.16 - LilyPond 2.15.39 released! May 22, 2012 LilyPond 2.15.39 is out; this is the seventh release candidate of the upcoming 2.16 stable release.

All users are invited to experiment with this version. New features since 2.14.2 are listed in the “Changes” manual on the website section about. There are no known Critical issues with this release. If no Critical bugs are found, then the official 2.16.0 release will be on 05 June 2012. If you discover any problems, please send us.

Release candidate 5 of 2.16 - LilyPond 2.15.37 released! April 19, 2012 LilyPond 2.15.37 is out; this is the fifth release candidate of the upcoming 2.16 stable release. All users are invited to experiment with this version. New features since 2.14.2 are listed in the “Changes” manual on the website section about. There are no known Critical issues with this release.

If no Critical bugs are found, then the official 2.16.0 release will be on 03 May 2012. If you discover any problems, please send us. Release candidate 4 of 2.16 - LilyPond 2.15.36 released! April 6, 2012 LilyPond 2.15.36 is out; this is the fourth release candidate of the upcoming 2.16 stable release.

All users are invited to experiment with this version. New features since 2.14.2 are listed in the “Changes” manual on the website section about. There are no known Critical issues with this release. If no Critical bugs are found, then the official 2.16.0 release will be on 20 April 2012. If you discover any problems, please send us. Release candidate 3 of 2.16 - LilyPond 2.15.30 released!

Feb 17, 2012 LilyPond 2.15.30 is out; this is the third release candidate of the upcoming 2.16 stable release. All users are invited to experiment with this version. New features since 2.14.2 are listed in the “Changes” manual on the website section about. There are no known Critical issues with this release. If no Critical bugs are found, then the official 2.16.0 release will be on 02 March 2012. If you discover any problems, please send us.

Release candidate 2 of 2.16 - LilyPond 2.15.12 released! Sep 20, 2011 LilyPond 2.15.12 is out; this is the second release candidate of the upcoming 2.16 stable release. All users are invited to experiment with this version. New features since 2.14.2 are listed in the “Changes” manual on the website section about. There are no known Critical issues with this release.

If no Critical bugs are found, then the official 2.16.0 release will be on 27 Sep 2011. If you discover any problems, please send us. Release candidate 1 of 2.16 - LilyPond 2.15.8 released! Aug 01, 2011 LilyPond 2.15.8 is out; this is the first release candidate of the upcoming 2.16 stable release. All users are invited to experiment with this version. New features since 2.14.2 are listed in the “Changes” manual on the website section about.

There are no known Critical issues with this release. If no Critical bugs are found, then the official 2.16.0 release will be on 08 Aug 2011. If you discover any problems, please send us. Release candidate 7 of 2.14 - LilyPond 2.13.63 released! May 30, 2011 LilyPond 2.13.63 is out; this is the seventh release candidate of the upcoming 2.14 stable release.

All users are invited to experiment with this version. New features since 2.12.3 are listed in the “Changes” manual on the website section about. There are no known Critical issues with this release. If no Critical bugs are found, then the official 2.14.0 release will be on June 6, 2011. If you discover any problems, please send us. Release candidate 6 of 2.14 - LilyPond 2.13.58 released! April 7, 2011 LilyPond 2.13.58 is out; this is the sixth release candidate of the upcoming 2.14 stable release.

All users are invited to experiment with this version. New features since 2.12.3 are listed in the “Changes” manual on the website section about. There are no known Critical issues with this release. If no Critical bugs are found, then the official 2.14.0 release will be on April 14, 2011. If you discover any problems, please send us. Release candidate 5 of 2.14 - LilyPond 2.13.57 released! April 3, 2011 LilyPond 2.13.57 is out; this is the fifth release candidate of the upcoming 2.14 stable release.

All users are invited to experiment with this version. New features since 2.12.3 are listed in the “Changes” manual on the website section about. There are no known Critical issues with this release. If no Critical bugs are found, then the official 2.14.0 release will be on April 10, 2011. If you discover any problems, please send us. Release candidate 4 of 2.14 - LilyPond 2.13.56 released! Mar 29, 2011 LilyPond 2.13.56 is out; this is the fourth release candidate of the upcoming 2.14 stable release.

All users are invited to experiment with this version. New features since 2.12.3 are listed in the “Changes” manual on the website section about.

There are no known Critical issues with this release. If no Critical bugs are found, then the official 2.14.0 release will be on April 5, 2011. If you discover any problems, please send us. Release candidate 3 of 2.14 - LilyPond 2.13.54 released! Mar 13, 2011 LilyPond 2.13.54 is out; this is the third release candidate of the upcoming 2.14 stable release. All users are invited to experiment with this version.

New features since 2.12.3 are listed in the “Changes” manual on the website section about. There are no known Critical issues with this release. If no Critical bugs are found, then the official 2.14.0 release will be on March 27, 2011. If you discover any problems, please send us. Release candidate 2 of 2.14 - LilyPond 2.13.49 released! Feb 9, 2011 LilyPond 2.13.49 is out; this is the second release candidate of the upcoming 2.14 stable release. All users are invited to experiment with this version.

New features since 2.12.3 are listed in the “Changes” manual on the website section about. There are no known Critical issues with this release. If no Critical bugs are found, then the official 2.14.0 release will be on Feb 23, 2011.

If you discover any problems, please send us. Release candidate 1 of 2.14 - LilyPond 2.13.46 released! Jan 12, 2011 LilyPond 2.13.46 is out; this is the first release candidate of the upcoming 2.14 stable release. All users are invited to experiment with this version.

New features since 2.12.3 are listed in the “Changes” manual on the website section about. There are no known Critical issues with this release.

If no Critical bugs are found, then the official 2.14.0 release will be on 26 Jan 2011. If you discover any problems, please send us. Beta test three of 2.14 – LilyPond 2.13.44 released! Dec 25, 2010 LilyPond 2.13.44 is out; this is the third beta test of the upcoming 2.14 stable release. Users are invited to experiment with this version. New features since 2.12.3 are listed in the “Changes” manual on the website section about. There is still one Critical problem with this release: in one case, the vertical spacing is much too compressed.

If you decide to test this version, do not be surprised to discover problems; just send us polite. Beta test two of 2.14 – LilyPond 2.13.43 released! Dec 14, 2010 LilyPond 2.13.43 is out; this is the second beta test of the upcoming 2.14 stable release. Users are invited to experiment with this version.

New features since 2.12.3 are listed in the “Changes” manual on the website section about. There is still one Critical problem with this release: in one case, the vertical spacing is much too compressed. If you decide to test this version, do not be surprised to discover problems; just send us polite. Beta test one of 2.14 – LilyPond 2.13.39 released! Nov 15, 2010 LilyPond 2.13.39 is out; this is the first beta test of the upcoming 2.14 stable release. Users are invited to experiment with this version.

New features since 2.12.3 are listed in the “Changes” manual on the website section about. There are still some Critical problems with this release: the vertical spacing is suspicious in two cases, and lilypond can crash with some odd input. If you decide to test 2.13.39, do not be surprised to discover problems; just send us polite.

Alpha test four of 2.14 – LilyPond 2.13.38 released! Oct 31, 2010 LilyPond 2.13.38 is out; this is the fourth alpha test of the upcoming 2.14 stable release. Users are invited to experiment with this version.

New features since 2.12.3 are listed in the “Changes” manual on the website section about. There are still some Critical problems with this release: the vertical spacing is suspicious in two cases, and lilypond can crash with some odd input. If you decide to test 2.13.38, do not be surprised to discover problems; just send us polite. Alpha test three of 2.14 – LilyPond 2.13.37 released! Oct 25, 2010 LilyPond 2.13.37 is out; this is the third alpha test of the upcoming 2.14 stable release.

Users are invited to experiment with this version. New features since 2.12.3 are listed in the “Changes” manual on the website section about. There are still some Critical problems with this release: the vertical spacing is suspicious in two cases, and lilypond can crash with some odd input. If you decide to test 2.13.37, do not be surprised to discover problems; just send us polite. LilyPond 2.13.21 released!

May 12, 2010 We are happy to announce the release of LilyPond 2.13.21. This release contains the usual number of bugfixes. However, a number of critical issues still remain, so this release is intended for developers only. This release should be of particular interest to package maintainers: we have made a few changes to the configure script and the required libraries. Barring any urgent bug reports, this is the build system and libraries that will be used for the next stable release.

LilyPond 2.11.65 — Release Candidate. December 2, 2008 This release has improvements to MusicXML import, contributed by Reinhold Kainhofer, and adds support for splitting a book in several book parts, contributed by Nicolas Sceaux.

Nested contexts of the same type are now allowed with any depth, and overriding nested properties can be done with list syntax, thanks to Neil Puttock. This is hopefully the last Release Candidate before stable release 2.12, so you are welcome to test this release if you can to report new issues.,. LilyPond 2.11.58 available. September 13, 2008 LilyPond 2.11.58 is a beta release, which means the next stable release is expected in a few weeks.

This release is also special, as it includes code which supports more flexible automatic accidentals rules, written several months ago by Rune Zedeler, deceased since then. All the development team express their condolences to his family and his friends. Besides this, automatic beaming has been improved by Carl Sorensen, support for creating stem flags in a new style has been contributed by Reinhold Kainhofer, and a few bugs have been fixed.,.