Rietveld Code Review Tool
Help | Bug tracker | Discussion group | Source code | Sign in
(117)

Unified Diff: Documentation/included/gsoc.itexi

Issue 349100043: web: GSoC: Remove "ScholarLY" project
Patch Set: Created 5 years, 2 months ago
Use n/p to move between diff chunks; N/P to move between comments. Please Sign in to add in-line comments.
Jump to:
View side-by-side diff with in-line comments
Download patch
« no previous file with comments | « no previous file | no next file » | no next file with comments »
Expand Comments ('e') | Collapse Comments ('c') | Show Comments Hide Comments ('s')
Index: Documentation/included/gsoc.itexi
diff --git a/Documentation/included/gsoc.itexi b/Documentation/included/gsoc.itexi
index 33af889edfcf1d7b2ee30f5b24c0189185e1782f..40a4b59354caaafd43141e4e56c7ad321cf4872e 100644
--- a/Documentation/included/gsoc.itexi
+++ b/Documentation/included/gsoc.itexi
@@ -240,33 +240,6 @@ contemporary notation techniques
@emph{Mentors:} @emph{NN,} Urs Liska
-@subsubheading Extending scholarly editing features
-
-The @uref{https://github.com/openlilylib/scholarly, scholarLY}
-extension package provides a powerful infrastructure for scholarly
-editions. With this package it is possible to encode annotations,
-to export them for critical reports, or to produce editorial
-highlighting in the score (e.g. dashing, parenthesizing etc.),
-footnotes etc.
-
-As a GSoC project substantial enhancements can be made to the
-package. Our suggestion is an infrastructure to encode
-@emph{variants} (alternative readings, corrections, regularizations),
-as outlined in
-@uref{https://github.com/openlilylib/scholarly/issues/61, this issue}.
-It could naturally be extended by the ability to produce music examples
-from annotations, to be used in footnotes or reports.
-
-@emph{Difficulty:} medium
-
-@emph{Requirements:} Scheme, ability to assess an extensive existing
-package
-
-@emph{Recommended:} familiarity with scholarly editing
-
-@emph{Mentors:} Jeffery Shivers, Urs Liska
-
-
@subsubheading Implement a System to Handle Scores System by System
One strategy that may improve the issue of LilyPond's compilation time is
« no previous file with comments | « no previous file | no next file » | no next file with comments »

Powered by Google App Engine
RSS Feeds Recent Issues | This issue
This is Rietveld f62528b