[Lilypond-auto] [LilyIssues-auto] [testlilyissues:issues] #1388 Support OpenType font features
Yes, I think so. Alternatively there is a way to install Guile 1.8 to LilyDev 5.2. Another solution is to use Ubuntu 16.04 which has Pango 1.38.1 and Guile 1.8. --- ** [issues:#1388] Support OpenType font features** **Status:** Started **Created:** Mon Nov 08, 2010 10:34 PM UTC by Anonymous **Last Updated:** Mon Jun 05, 2017 03:21 PM UTC **Owner:** horndude77 *Originally created by:* *anonymous *Originally created by:* [lemzw...@googlemail.com](http://code.google.com/u/102649819178652971408/) Currently, LilyPond doesn't support OpenType font features. For example, many fonts already contain glyphs for small caps letters, but lilypond can't access such glyphs directly since OpenType fonts don't need to have named glyphs, and you need to activate an OpenType feature \(\`smcp' in this particular case\) so that input character codes get properly mapped to caps glyphs. I suggest that we implement an interface similar to the \`fontspec' package for XeTeX and luatex: [http://www.ctan.org/get/macros/xetex/latex/fontspec/fontspec.pdf](http://www.ctan.org/get/macros/xetex/latex/fontspec/fontspec.pdf) --- Sent from sourceforge.net because testlilyissues-a...@lists.sourceforge.net is subscribed to https://sourceforge.net/p/testlilyissues/issues/ To unsubscribe from further messages, a project admin can change settings at https://sourceforge.net/p/testlilyissues/admin/issues/options. Or, if this is a mailing list, you can unsubscribe from the mailing list.-- Check out the vibrant tech community on one of the world's most engaging tech sites, Slashdot.org! http://sdm.link/slashdot___ Testlilyissues-auto mailing list testlilyissues-a...@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/testlilyissues-auto
[Lilypond-auto] [LilyIssues-auto] [testlilyissues:issues] #5140 Fix granados example
- **labels**: --> Fixed_2_19_62 - **status**: Started --> Fixed - **Patch**: push --> - **Comment**: Pushed to staging as faa73e45e2049ea74fc8e0405b64cc5854e747e7. Also updated in lilypond-extra with the result that the webpage is now already showing a corrected example. --- ** [issues:#5140] Fix granados example** **Status:** Fixed **Labels:** Fixed_2_19_62 **Created:** Mon May 29, 2017 04:39 PM UTC by Phil Holmes **Last Updated:** Mon Jun 05, 2017 12:29 PM UTC **Owner:** Phil Holmes Fix granados example http://codereview.appspot.com/297540043 --- Sent from sourceforge.net because testlilyissues-a...@lists.sourceforge.net is subscribed to https://sourceforge.net/p/testlilyissues/issues/ To unsubscribe from further messages, a project admin can change settings at https://sourceforge.net/p/testlilyissues/admin/issues/options. Or, if this is a mailing list, you can unsubscribe from the mailing list.-- Check out the vibrant tech community on one of the world's most engaging tech sites, Slashdot.org! http://sdm.link/slashdot___ Testlilyissues-auto mailing list testlilyissues-a...@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/testlilyissues-auto
[Lilypond-auto] [LilyIssues-auto] [testlilyissues:issues] #5141 Fix typos in \offset documentation
--- ** [issues:#5141] Fix typos in \offset documentation** **Status:** Started **Created:** Wed Jun 07, 2017 02:46 PM UTC by David Nalesnik **Last Updated:** Wed Jun 07, 2017 02:46 PM UTC **Owner:** nobody Fix typos in \offset documentation - Fix errors in description of OttavaBracket example - Minor improvements in wording http://codereview.appspot.com/322040043 --- Sent from sourceforge.net because testlilyissues-a...@lists.sourceforge.net is subscribed to https://sourceforge.net/p/testlilyissues/issues/ To unsubscribe from further messages, a project admin can change settings at https://sourceforge.net/p/testlilyissues/admin/issues/options. Or, if this is a mailing list, you can unsubscribe from the mailing list.-- Check out the vibrant tech community on one of the world's most engaging tech sites, Slashdot.org! http://sdm.link/slashdot___ Testlilyissues-auto mailing list testlilyissues-a...@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/testlilyissues-auto
[Lilypond-auto] [LilyIssues-auto] [testlilyissues:issues] #1388 Support OpenType font features
- **Patch**: review --> countdown - **Comment**: So as far as I can tell there is nothing wrong with this going on countdown for June 11th (we will have to update LilyDev, but I don't see that as a blocking 'thing' for this patch). Patch on countdown for June 11th --- ** [issues:#1388] Support OpenType font features** **Status:** Started **Created:** Mon Nov 08, 2010 10:34 PM UTC by Anonymous **Last Updated:** Tue Jun 06, 2017 12:55 PM UTC **Owner:** horndude77 *Originally created by:* *anonymous *Originally created by:* [lemzw...@googlemail.com](http://code.google.com/u/102649819178652971408/) Currently, LilyPond doesn't support OpenType font features. For example, many fonts already contain glyphs for small caps letters, but lilypond can't access such glyphs directly since OpenType fonts don't need to have named glyphs, and you need to activate an OpenType feature \(\`smcp' in this particular case\) so that input character codes get properly mapped to caps glyphs. I suggest that we implement an interface similar to the \`fontspec' package for XeTeX and luatex: [http://www.ctan.org/get/macros/xetex/latex/fontspec/fontspec.pdf](http://www.ctan.org/get/macros/xetex/latex/fontspec/fontspec.pdf) --- Sent from sourceforge.net because testlilyissues-a...@lists.sourceforge.net is subscribed to https://sourceforge.net/p/testlilyissues/issues/ To unsubscribe from further messages, a project admin can change settings at https://sourceforge.net/p/testlilyissues/admin/issues/options. Or, if this is a mailing list, you can unsubscribe from the mailing list.-- Check out the vibrant tech community on one of the world's most engaging tech sites, Slashdot.org! http://sdm.link/slashdot___ Testlilyissues-auto mailing list testlilyissues-a...@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/testlilyissues-auto
[Lilypond-auto] [LilyIssues-auto] [testlilyissues:issues] #1388 Support OpenType font features
How about the following method? * configure script checks whether Pango's version is 1.38 or above. * If Pango's version is 1.38+, configure makes that `config.hh` defines something like `HAVE_PANGO_1_38`. * In `lily/pango-font.cc`, enclose around `pango_attr_font_features_new ()` with `#ifdef HAVE_PANGO_1_38` and `#endif`. * In the else clause it may be better to show a warning message that this binary cannnot use OpenType font features. In this method, the binary that is builded by GUB can use OpenType font features since GUB has Pango 1.40.1. So you can use OpenType font features in the binary distributed by lilypond.org. LilyDev 4.1 also can compile it. However, the binary cannot use OpenType font features. If you compile .ly file that uses OpenType font features by the binary, you would see the warning message that this binary cannot use OpenType font features. --- ** [issues:#1388] Support OpenType font features** **Status:** Started **Created:** Mon Nov 08, 2010 10:34 PM UTC by Anonymous **Last Updated:** Thu Jun 08, 2017 06:54 AM UTC **Owner:** horndude77 *Originally created by:* *anonymous *Originally created by:* [lemzw...@googlemail.com](http://code.google.com/u/102649819178652971408/) Currently, LilyPond doesn't support OpenType font features. For example, many fonts already contain glyphs for small caps letters, but lilypond can't access such glyphs directly since OpenType fonts don't need to have named glyphs, and you need to activate an OpenType feature \(\`smcp' in this particular case\) so that input character codes get properly mapped to caps glyphs. I suggest that we implement an interface similar to the \`fontspec' package for XeTeX and luatex: [http://www.ctan.org/get/macros/xetex/latex/fontspec/fontspec.pdf](http://www.ctan.org/get/macros/xetex/latex/fontspec/fontspec.pdf) --- Sent from sourceforge.net because testlilyissues-a...@lists.sourceforge.net is subscribed to https://sourceforge.net/p/testlilyissues/issues/ To unsubscribe from further messages, a project admin can change settings at https://sourceforge.net/p/testlilyissues/admin/issues/options. Or, if this is a mailing list, you can unsubscribe from the mailing list.-- Check out the vibrant tech community on one of the world's most engaging tech sites, Slashdot.org! http://sdm.link/slashdot___ Testlilyissues-auto mailing list testlilyissues-a...@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/testlilyissues-auto
[Lilypond-auto] [LilyIssues-auto] [testlilyissues:issues] #5141 Fix typos in \offset documentation
- Description has changed: Diff: - **Needs**: --> - **Patch**: new --> review - **Type**: Enhancement --> Documentation - **Comment**: Passes make, make check and a full make doc --- ** [issues:#5141] Fix typos in \offset documentation** **Status:** Started **Created:** Wed Jun 07, 2017 02:46 PM UTC by David Nalesnik **Last Updated:** Wed Jun 07, 2017 02:46 PM UTC **Owner:** David Nalesnik Fix typos in \offset documentation - Fix errors in description of OttavaBracket example - Minor improvements in wording http://codereview.appspot.com/322040043 --- Sent from sourceforge.net because testlilyissues-a...@lists.sourceforge.net is subscribed to https://sourceforge.net/p/testlilyissues/issues/ To unsubscribe from further messages, a project admin can change settings at https://sourceforge.net/p/testlilyissues/admin/issues/options. Or, if this is a mailing list, you can unsubscribe from the mailing list.-- Check out the vibrant tech community on one of the world's most engaging tech sites, Slashdot.org! http://sdm.link/slashdot___ Testlilyissues-auto mailing list testlilyissues-a...@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/testlilyissues-auto
[Lilypond-auto] [LilyIssues-auto] [testlilyissues:issues] #5142 partcombine can't handle simultaneous hairpins
--- ** [issues:#5142] partcombine can't handle simultaneous hairpins** **Status:** New **Created:** Fri Jun 09, 2017 12:34 PM UTC by Palmer Ralph **Last Updated:** Fri Jun 09, 2017 12:34 PM UTC **Owner:** nobody **Attachments:** - [falla-amor-brujo-trp-1-2.ly](https://sourceforge.net/p/testlilyissues/issues/5142/attachment/falla-amor-brujo-trp-1-2.ly) (971 Bytes; text/lilypond-source) - [falla-amor-brujo-trp-1-2.preview.png](https://sourceforge.net/p/testlilyissues/issues/5142/attachment/falla-amor-brujo-trp-1-2.preview.png) (23.5 kB; image/png) Rutger Hofman wrote : I stumble into a partcombine bug. At times, \partcombine extends hairpins over (possibly long) stretches to the wrong terminating dynamic. In the top staff of the attached MWE, the erroneous behaviour is shown. The bottom staff group shows the intended behaviour. If I specify any of \partcombineApart or \partcombineChords, the bug disappears, second and third staves. --- Sent from sourceforge.net because testlilyissues-a...@lists.sourceforge.net is subscribed to https://sourceforge.net/p/testlilyissues/issues/ To unsubscribe from further messages, a project admin can change settings at https://sourceforge.net/p/testlilyissues/admin/issues/options. Or, if this is a mailing list, you can unsubscribe from the mailing list.-- Check out the vibrant tech community on one of the world's most engaging tech sites, Slashdot.org! http://sdm.link/slashdot___ Testlilyissues-auto mailing list testlilyissues-a...@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/testlilyissues-auto
[Lilypond-auto] [LilyIssues-auto] [testlilyissues:issues] #5143 [partcombine] partcombine can't handle simultaneous hairpins
---
** [issues:#5143] [partcombine] partcombine can't handle simultaneous hairpins**
**Status:** New
**Created:** Fri Jun 09, 2017 12:40 PM UTC by Palmer Ralph
**Last Updated:** Fri Jun 09, 2017 12:40 PM UTC
**Owner:** nobody
Kieren MacMillan wrote :
I see this is still a problem, so I thought I'd post it to -bug.
%%% SNIPPET BEGINS
\version "2.19.61"
musicA = {
g'1\> R1\!
}
musicB = {
b'1\> R1\!
}
\new Staff \partcombine \musicA \musicB
%%% SNIPPET ENDS
---
Sent from sourceforge.net because testlilyissues-a...@lists.sourceforge.net is
subscribed to https://sourceforge.net/p/testlilyissues/issues/
To unsubscribe from further messages, a project admin can change settings at
https://sourceforge.net/p/testlilyissues/admin/issues/options. Or, if this is
a mailing list, you can unsubscribe from the mailing list.--
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot___
Testlilyissues-auto mailing list
testlilyissues-a...@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/testlilyissues-auto
[Lilypond-auto] [LilyIssues-auto] [testlilyissues:issues] #5144 lilypond-manuals.css: edit color scheme and some spacing
--- ** [issues:#5144] lilypond-manuals.css: edit color scheme and some spacing** **Status:** Started **Created:** Sat Jun 10, 2017 05:23 PM UTC by Paul Morris **Last Updated:** Sat Jun 10, 2017 05:23 PM UTC **Owner:** nobody lilypond-manuals.css: edit color scheme and some spacing This patch simplifies and (IMHO) improves the color scheme and spacing of the manuals on the web. I will include a link to screenshots and a demo site, with more details on what's different. http://codereview.appspot.com/322070043 --- Sent from sourceforge.net because testlilyissues-a...@lists.sourceforge.net is subscribed to https://sourceforge.net/p/testlilyissues/issues/ To unsubscribe from further messages, a project admin can change settings at https://sourceforge.net/p/testlilyissues/admin/issues/options. Or, if this is a mailing list, you can unsubscribe from the mailing list.-- Check out the vibrant tech community on one of the world's most engaging tech sites, Slashdot.org! http://sdm.link/slashdot___ Testlilyissues-auto mailing list testlilyissues-a...@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/testlilyissues-auto
[Lilypond-auto] [LilyIssues-auto] [testlilyissues:issues] #5144 lilypond-manuals.css: edit color scheme and some spacing
Here is a screenshot showing the language section in the footer. See reitveld issue for more details and link to demo site. Attachments: - [screenshot-lilypond-languages-footer.png](https://sourceforge.net/p/testlilyissues/issues/_discuss/thread/d22bf24b/6cbd/attachment/screenshot-lilypond-languages-footer.png) (120.9 kB; image/png) --- ** [issues:#5144] lilypond-manuals.css: edit color scheme and some spacing** **Status:** Started **Created:** Sat Jun 10, 2017 05:23 PM UTC by Paul Morris **Last Updated:** Sat Jun 10, 2017 05:23 PM UTC **Owner:** Paul Morris lilypond-manuals.css: edit color scheme and some spacing This patch simplifies and (IMHO) improves the color scheme and spacing of the manuals on the web. I will include a link to screenshots and a demo site, with more details on what's different. http://codereview.appspot.com/322070043 --- Sent from sourceforge.net because testlilyissues-a...@lists.sourceforge.net is subscribed to https://sourceforge.net/p/testlilyissues/issues/ To unsubscribe from further messages, a project admin can change settings at https://sourceforge.net/p/testlilyissues/admin/issues/options. Or, if this is a mailing list, you can unsubscribe from the mailing list.-- Check out the vibrant tech community on one of the world's most engaging tech sites, Slashdot.org! http://sdm.link/slashdot___ Testlilyissues-auto mailing list testlilyissues-a...@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/testlilyissues-auto
[Lilypond-auto] [LilyIssues-auto] [testlilyissues:issues] #1388 Support OpenType font features
- **Patch**: countdown --> push - **Comment**: This can now be pushed - I am waiting on some approval from the other Devs (as far as I could see it was only LilyDev that was going to have problems with this change), and as Paul does not have commit access, if this gets approved one of the other Devs can push this - if they would be so kind - else set this back to 'Review' while we figure out what else (if anything) needs to be done. --- ** [issues:#1388] Support OpenType font features** **Status:** Started **Created:** Mon Nov 08, 2010 10:34 PM UTC by Anonymous **Last Updated:** Thu Jun 08, 2017 12:16 PM UTC **Owner:** horndude77 *Originally created by:* *anonymous *Originally created by:* [lemzw...@googlemail.com](http://code.google.com/u/102649819178652971408/) Currently, LilyPond doesn't support OpenType font features. For example, many fonts already contain glyphs for small caps letters, but lilypond can't access such glyphs directly since OpenType fonts don't need to have named glyphs, and you need to activate an OpenType feature \(\`smcp' in this particular case\) so that input character codes get properly mapped to caps glyphs. I suggest that we implement an interface similar to the \`fontspec' package for XeTeX and luatex: [http://www.ctan.org/get/macros/xetex/latex/fontspec/fontspec.pdf](http://www.ctan.org/get/macros/xetex/latex/fontspec/fontspec.pdf) --- Sent from sourceforge.net because testlilyissues-a...@lists.sourceforge.net is subscribed to https://sourceforge.net/p/testlilyissues/issues/ To unsubscribe from further messages, a project admin can change settings at https://sourceforge.net/p/testlilyissues/admin/issues/options. Or, if this is a mailing list, you can unsubscribe from the mailing list.-- Check out the vibrant tech community on one of the world's most engaging tech sites, Slashdot.org! http://sdm.link/slashdot___ Testlilyissues-auto mailing list testlilyissues-a...@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/testlilyissues-auto
[Lilypond-auto] [LilyIssues-auto] [testlilyissues:issues] #5141 Fix typos in \offset documentation
- **Patch**: review --> countdown - **Comment**: Patch on countdown for June 14th. --- ** [issues:#5141] Fix typos in \offset documentation** **Status:** Started **Created:** Wed Jun 07, 2017 02:46 PM UTC by David Nalesnik **Last Updated:** Fri Jun 09, 2017 06:54 AM UTC **Owner:** David Nalesnik Fix typos in \offset documentation - Fix errors in description of OttavaBracket example - Minor improvements in wording http://codereview.appspot.com/322040043 --- Sent from sourceforge.net because testlilyissues-a...@lists.sourceforge.net is subscribed to https://sourceforge.net/p/testlilyissues/issues/ To unsubscribe from further messages, a project admin can change settings at https://sourceforge.net/p/testlilyissues/admin/issues/options. Or, if this is a mailing list, you can unsubscribe from the mailing list.-- Check out the vibrant tech community on one of the world's most engaging tech sites, Slashdot.org! http://sdm.link/slashdot___ Testlilyissues-auto mailing list testlilyissues-a...@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/testlilyissues-auto
[Lilypond-auto] [LilyIssues-auto] [testlilyissues:issues] #5144 lilypond-manuals.css: edit color scheme and some spacing
- Description has changed: Diff: - **Needs**: --> - **Patch**: new --> review - **Comment**: passes make, make check and a full make doc. --- ** [issues:#5144] lilypond-manuals.css: edit color scheme and some spacing** **Status:** Started **Created:** Sat Jun 10, 2017 05:23 PM UTC by Paul Morris **Last Updated:** Sat Jun 10, 2017 06:05 PM UTC **Owner:** Paul Morris lilypond-manuals.css: edit color scheme and some spacing This patch simplifies and (IMHO) improves the color scheme and spacing of the manuals on the web. I will include a link to screenshots and a demo site, with more details on what's different. http://codereview.appspot.com/322070043 --- Sent from sourceforge.net because testlilyissues-a...@lists.sourceforge.net is subscribed to https://sourceforge.net/p/testlilyissues/issues/ To unsubscribe from further messages, a project admin can change settings at https://sourceforge.net/p/testlilyissues/admin/issues/options. Or, if this is a mailing list, you can unsubscribe from the mailing list.-- Check out the vibrant tech community on one of the world's most engaging tech sites, Slashdot.org! http://sdm.link/slashdot___ Testlilyissues-auto mailing list testlilyissues-a...@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/testlilyissues-auto
[Lilypond-auto] [LilyIssues-auto] [testlilyissues:issues] #1228 merge simultaneous rests of the same duration
Rebase, simplify scheme with every as suggested http://codereview.appspot.com/321930043 --- ** [issues:#1228] merge simultaneous rests of the same duration** **Status:** Started **Created:** Wed Aug 18, 2010 11:15 AM UTC by Anonymous **Last Updated:** Mon Jun 12, 2017 05:18 AM UTC **Owner:** horndude77 *Originally created by:* *anonymous *Originally created by:* [ralphbug...@gmail.com](http://code.google.com/u/106131861630194758622/) On 11 June 2010 16:27, Xavier Scheuer wrote: Could you implement the possibility: \override RestCollision \#'positioning-done = \#merge-rests-on-positioning described in [http://lsr.dsi.unimi.it/LSR/Item?id=336](http://lsr.dsi.unimi.it/LSR/Item?id=336) \_directly\_ into LilyPond? So we would not have to define merge-rests-on-positioning ourselves, each time we want to use this function. This function \_is useful\_, as shown by the several messages asking for this on lilypond-user: [http://lists.gnu.org/archive/cgi-bin/namazu.cgi?query=Merging+rests+&submit=Search!&idxname=lilypond-user](http://lists.gnu.org/archive/cgi-bin/namazu.cgi?query=Merging+rests+&submit=Search!&idxname=lilypond-user) That would also be great if you could overpass the limitations, i.e. – ability to handle more than two voices ; >– handle multi-measure/whole-measure rests. Maybe the following discussion could be helpful in a certain way: [http://lists.gnu.org/archive/html/lilypond-user/2010-02/msg00452.html](http://lists.gnu.org/archive/html/lilypond-user/2010-02/msg00452.html) --- Sent from sourceforge.net because testlilyissues-a...@lists.sourceforge.net is subscribed to https://sourceforge.net/p/testlilyissues/issues/ To unsubscribe from further messages, a project admin can change settings at https://sourceforge.net/p/testlilyissues/admin/issues/options. Or, if this is a mailing list, you can unsubscribe from the mailing list.-- Check out the vibrant tech community on one of the world's most engaging tech sites, Slashdot.org! http://sdm.link/slashdot___ Testlilyissues-auto mailing list testlilyissues-a...@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/testlilyissues-auto
[Lilypond-auto] [LilyIssues-auto] [testlilyissues:issues] #1228 merge simultaneous rests of the same duration
- **Needs**: --> - **Patch**: new --> review - **Type**: --> Enhancement - **Comment**: Passes make, make check and a full make doc. --- ** [issues:#1228] merge simultaneous rests of the same duration** **Status:** Started **Created:** Wed Aug 18, 2010 11:15 AM UTC by Anonymous **Last Updated:** Mon Jun 12, 2017 05:18 AM UTC **Owner:** horndude77 *Originally created by:* *anonymous *Originally created by:* [ralphbug...@gmail.com](http://code.google.com/u/106131861630194758622/) On 11 June 2010 16:27, Xavier Scheuer wrote: Could you implement the possibility: \override RestCollision \#'positioning-done = \#merge-rests-on-positioning described in [http://lsr.dsi.unimi.it/LSR/Item?id=336](http://lsr.dsi.unimi.it/LSR/Item?id=336) \_directly\_ into LilyPond? So we would not have to define merge-rests-on-positioning ourselves, each time we want to use this function. This function \_is useful\_, as shown by the several messages asking for this on lilypond-user: [http://lists.gnu.org/archive/cgi-bin/namazu.cgi?query=Merging+rests+&submit=Search!&idxname=lilypond-user](http://lists.gnu.org/archive/cgi-bin/namazu.cgi?query=Merging+rests+&submit=Search!&idxname=lilypond-user) That would also be great if you could overpass the limitations, i.e. – ability to handle more than two voices ; >– handle multi-measure/whole-measure rests. Maybe the following discussion could be helpful in a certain way: [http://lists.gnu.org/archive/html/lilypond-user/2010-02/msg00452.html](http://lists.gnu.org/archive/html/lilypond-user/2010-02/msg00452.html) --- Sent from sourceforge.net because testlilyissues-a...@lists.sourceforge.net is subscribed to https://sourceforge.net/p/testlilyissues/issues/ To unsubscribe from further messages, a project admin can change settings at https://sourceforge.net/p/testlilyissues/admin/issues/options. Or, if this is a mailing list, you can unsubscribe from the mailing list.-- Check out the vibrant tech community on one of the world's most engaging tech sites, Slashdot.org! http://sdm.link/slashdot___ Testlilyissues-auto mailing list testlilyissues-a...@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/testlilyissues-auto
[Lilypond-auto] [LilyIssues-auto] [testlilyissues:issues] #5144 lilypond-manuals.css: edit color scheme and some spacing
Paul, I've been thinking for some time that language selection should be moved to the top, for the following reasons: 1. It's the place where most people expect the language selection to be. There are obvious reasons for this. 2. Add to previous argument the fact that links in online manuals are nice links without extension and the browser always serves the file matching the browser language setting (issue [#2273]). So if you happen to use a browser in a language different from the language you'd like to read, you'll need to scroll down each new page to select the right language in the footer. Obviously, this belongs to a new issue. But I'm curious to know your opinion. --- ** [issues:#5144] lilypond-manuals.css: edit color scheme and some spacing** **Status:** Started **Created:** Sat Jun 10, 2017 05:23 PM UTC by Paul Morris **Last Updated:** Sun Jun 11, 2017 08:58 AM UTC **Owner:** Paul Morris lilypond-manuals.css: edit color scheme and some spacing This patch simplifies and (IMHO) improves the color scheme and spacing of the manuals on the web. I will include a link to screenshots and a demo site, with more details on what's different. http://codereview.appspot.com/322070043 --- Sent from sourceforge.net because testlilyissues-a...@lists.sourceforge.net is subscribed to https://sourceforge.net/p/testlilyissues/issues/ To unsubscribe from further messages, a project admin can change settings at https://sourceforge.net/p/testlilyissues/admin/issues/options. Or, if this is a mailing list, you can unsubscribe from the mailing list.-- Check out the vibrant tech community on one of the world's most engaging tech sites, Slashdot.org! http://sdm.link/slashdot___ Testlilyissues-auto mailing list testlilyissues-a...@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/testlilyissues-auto
[Lilypond-auto] [LilyIssues-auto] [testlilyissues:issues] #5145 Allow $... to specify a markup command
--- ** [issues:#5145] Allow $... to specify a markup command** **Status:** Started **Created:** Mon Jun 12, 2017 03:16 PM UTC by David Kastrup **Last Updated:** Mon Jun 12, 2017 03:16 PM UTC **Owner:** nobody Allow $... to specify a markup command This is a partial (though more flexible) substitute for \on-the-fly since it allows to replace \on-the-fly #(lambda (layout props args) ...) with $(let ((fun (lambda (layout props args) ...))) (set! (markup-command-signature fun) (list markup?)) fun) Namely: ad-hoc written functions (probably most useful when written using macros) can be employed as markup commands when preceded with $ as long as they have a suitable markup command signature attached. This feature is mainly added for consistency with music functions. Lexer: factor out push_markup_predicates http://codereview.appspot.com/322090043 --- Sent from sourceforge.net because testlilyissues-a...@lists.sourceforge.net is subscribed to https://sourceforge.net/p/testlilyissues/issues/ To unsubscribe from further messages, a project admin can change settings at https://sourceforge.net/p/testlilyissues/admin/issues/options. Or, if this is a mailing list, you can unsubscribe from the mailing list.-- Check out the vibrant tech community on one of the world's most engaging tech sites, Slashdot.org! http://sdm.link/slashdot___ Testlilyissues-auto mailing list testlilyissues-a...@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/testlilyissues-auto
[Lilypond-auto] [LilyIssues-auto] [testlilyissues:issues] #5122 Fix not scaling stem in note-by-number-markup
This patch may have broken the rendering of metronomic marks in case the staff
size was set with set-global-staff-size.
For the following simple source code, the stem of the metronomic mark is ok
with version 2.19.55, but it is not with version 2.19.61 after the patch was
applied:
\version "2.19.55"
#(set-global-staff-size 11 )
\score {
\new Staff {
\tempo 8 = 140
c'4
}
}
---
** [issues:#5122] Fix not scaling stem in note-by-number-markup**
**Status:** Verified
**Labels:** Fixed_2_19_60
**Created:** Sun Apr 16, 2017 05:15 PM UTC by Thomas Morley
**Last Updated:** Mon Jun 12, 2017 04:35 PM UTC
**Owner:** Thomas Morley
**Attachments:**
-
[note-by-number-after-patch.png](https://sourceforge.net/p/testlilyissues/issues/5122/attachment/note-by-number-after-patch.png)
(25.3 kB; image/png)
-
[note-by-number-before-patch.png](https://sourceforge.net/p/testlilyissues/issues/5122/attachment/note-by-number-before-patch.png)
(24.9 kB; image/png)
Fix not scaling stem in note-by-number-markup
Done by calling text-font-size from layout, which defaults to 11.
Then scaling stem-thickness and stem-length by division of
text-font-size through 11.
This ensures a stem-appearance according to the text-properties of
MetronomeMark.
http://codereview.appspot.com/324780043
---
Sent from sourceforge.net because testlilyissues-a...@lists.sourceforge.net is
subscribed to https://sourceforge.net/p/testlilyissues/issues/
To unsubscribe from further messages, a project admin can change settings at
https://sourceforge.net/p/testlilyissues/admin/issues/options. Or, if this is
a mailing list, you can unsubscribe from the mailing list.--
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot___
Testlilyissues-auto mailing list
testlilyissues-a...@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/testlilyissues-auto
[Lilypond-auto] [LilyIssues-auto] [testlilyissues:issues] #5146 Don't use \line in the implementation of \concat
--- ** [issues:#5146] Don't use \line in the implementation of \concat** **Status:** Started **Created:** Mon Jun 12, 2017 06:34 PM UTC by David Kastrup **Last Updated:** Mon Jun 12, 2017 06:34 PM UTC **Owner:** nobody Don't use \line in the implementation of \concat It doesn't really make any sense to override word-space temporarily and it does not make sense to heed text-direction when putting together stuff without actual word boundaries. http://codereview.appspot.com/325860043 --- Sent from sourceforge.net because testlilyissues-a...@lists.sourceforge.net is subscribed to https://sourceforge.net/p/testlilyissues/issues/ To unsubscribe from further messages, a project admin can change settings at https://sourceforge.net/p/testlilyissues/admin/issues/options. Or, if this is a mailing list, you can unsubscribe from the mailing list.-- Check out the vibrant tech community on one of the world's most engaging tech sites, Slashdot.org! http://sdm.link/slashdot___ Testlilyissues-auto mailing list testlilyissues-a...@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/testlilyissues-auto
[Lilypond-auto] [LilyIssues-auto] [testlilyissues:issues] Re: #5144 lilypond-manuals.css: edit color scheme and some spacing
Hi Federico, I'm not opposed to that, in principle. I think the devil is in the details of how it's done, but it's only one line or two of text so that's promising... (I think it would require changes to the code that generates the html, which I think is in Perl, which I don't know.) --- ** [issues:#5144] lilypond-manuals.css: edit color scheme and some spacing** **Status:** Started **Created:** Sat Jun 10, 2017 05:23 PM UTC by Paul Morris **Last Updated:** Mon Jun 12, 2017 10:37 AM UTC **Owner:** Paul Morris lilypond-manuals.css: edit color scheme and some spacing This patch simplifies and (IMHO) improves the color scheme and spacing of the manuals on the web. I will include a link to screenshots and a demo site, with more details on what's different. http://codereview.appspot.com/322070043 --- Sent from sourceforge.net because testlilyissues-a...@lists.sourceforge.net is subscribed to https://sourceforge.net/p/testlilyissues/issues/ To unsubscribe from further messages, a project admin can change settings at https://sourceforge.net/p/testlilyissues/admin/issues/options. Or, if this is a mailing list, you can unsubscribe from the mailing list.-- Check out the vibrant tech community on one of the world's most engaging tech sites, Slashdot.org! http://sdm.link/slashdot___ Testlilyissues-auto mailing list testlilyissues-a...@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/testlilyissues-auto
[Lilypond-auto] [LilyIssues-auto] [testlilyissues:issues] Re: #5122 Fix not scaling stem in note-by-number-markup
Confirmed. On devel I suggested to revert this patch. --- ** [issues:#5122] Fix not scaling stem in note-by-number-markup** **Status:** Verified **Labels:** Fixed_2_19_60 **Created:** Sun Apr 16, 2017 05:15 PM UTC by Thomas Morley **Last Updated:** Mon Jun 12, 2017 04:35 PM UTC **Owner:** Thomas Morley **Attachments:** - [note-by-number-after-patch.png](https://sourceforge.net/p/testlilyissues/issues/5122/attachment/note-by-number-after-patch.png) (25.3 kB; image/png) - [note-by-number-before-patch.png](https://sourceforge.net/p/testlilyissues/issues/5122/attachment/note-by-number-before-patch.png) (24.9 kB; image/png) Fix not scaling stem in note-by-number-markup Done by calling text-font-size from layout, which defaults to 11. Then scaling stem-thickness and stem-length by division of text-font-size through 11. This ensures a stem-appearance according to the text-properties of MetronomeMark. http://codereview.appspot.com/324780043 --- Sent from sourceforge.net because testlilyissues-a...@lists.sourceforge.net is subscribed to https://sourceforge.net/p/testlilyissues/issues/ To unsubscribe from further messages, a project admin can change settings at https://sourceforge.net/p/testlilyissues/admin/issues/options. Or, if this is a mailing list, you can unsubscribe from the mailing list.-- Check out the vibrant tech community on one of the world's most engaging tech sites, Slashdot.org! http://sdm.link/slashdot___ Testlilyissues-auto mailing list testlilyissues-a...@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/testlilyissues-auto
[Lilypond-auto] [LilyIssues-auto] [testlilyissues:issues] #5145 Allow $... to specify a markup command
- Description has changed: Diff: - **Needs**: --> - **Patch**: new --> review - **Comment**: Passes make, make check and a full make doc --- ** [issues:#5145] Allow $... to specify a markup command** **Status:** Started **Created:** Mon Jun 12, 2017 03:16 PM UTC by David Kastrup **Last Updated:** Mon Jun 12, 2017 03:17 PM UTC **Owner:** David Kastrup Allow $... to specify a markup command This is a partial (though more flexible) substitute for \on-the-fly since it allows to replace \on-the-fly #(lambda (layout props args) ...) with $(let ((fun (lambda (layout props args) ...))) (set! (markup-command-signature fun) (list markup?)) fun) Namely: ad-hoc written functions (probably most useful when written using macros) can be employed as markup commands when preceded with $ as long as they have a suitable markup command signature attached. This feature is mainly added for consistency with music functions. Lexer: factor out push_markup_predicates http://codereview.appspot.com/322090043 --- Sent from sourceforge.net because testlilyissues-a...@lists.sourceforge.net is subscribed to https://sourceforge.net/p/testlilyissues/issues/ To unsubscribe from further messages, a project admin can change settings at https://sourceforge.net/p/testlilyissues/admin/issues/options. Or, if this is a mailing list, you can unsubscribe from the mailing list.-- Check out the vibrant tech community on one of the world's most engaging tech sites, Slashdot.org! http://sdm.link/slashdot___ Testlilyissues-auto mailing list testlilyissues-a...@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/testlilyissues-auto
[Lilypond-auto] [LilyIssues-auto] [testlilyissues:issues] #5146 Don't use \line in the implementation of \concat
- Description has changed: Diff: - **Needs**: --> - **Patch**: new --> review - **Comment**: Passes make, make check and a full make doc. --- ** [issues:#5146] Don't use \line in the implementation of \concat** **Status:** Started **Created:** Mon Jun 12, 2017 06:34 PM UTC by David Kastrup **Last Updated:** Mon Jun 12, 2017 06:34 PM UTC **Owner:** David Kastrup Don't use \line in the implementation of \concat It doesn't really make any sense to override word-space temporarily and it does not make sense to heed text-direction when putting together stuff without actual word boundaries. http://codereview.appspot.com/325860043 --- Sent from sourceforge.net because testlilyissues-a...@lists.sourceforge.net is subscribed to https://sourceforge.net/p/testlilyissues/issues/ To unsubscribe from further messages, a project admin can change settings at https://sourceforge.net/p/testlilyissues/admin/issues/options. Or, if this is a mailing list, you can unsubscribe from the mailing list.-- Check out the vibrant tech community on one of the world's most engaging tech sites, Slashdot.org! http://sdm.link/slashdot___ Testlilyissues-auto mailing list testlilyissues-a...@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/testlilyissues-auto
[Lilypond-auto] [LilyIssues-auto] [testlilyissues:issues] #5147 Add whether to use OTF feature depending on Pango version
--- ** [issues:#5147] Add whether to use OTF feature depending on Pango version** **Status:** Started **Created:** Tue Jun 13, 2017 12:19 PM UTC by Masamichi Hosoda **Last Updated:** Tue Jun 13, 2017 12:19 PM UTC **Owner:** nobody Add whether to use OTF feature depending on Pango version Issue 1338 requires Pango 1.38+ for using OpenType font feature. However, LilyDev 4.1 has Pango 1.36.8. So it cannot compile Issue 1338. This commit makes LilyPond can be configured without OpenType font feature if Pango is old. Therefore, LilyPond become to be able to compile even by LilyDev 4.1 that has old Pango. However, the binary that compiled by LilyDev 4.1 cannot use OpenType feature. It is required Pango 1.38+ if you'd like to use the feature. This patch requires Issue 1388 https://sourceforge.net/p/testlilyissues/issues/1388/ https://codereview.appspot.com/323850043 http://codereview.appspot.com/322100043 --- Sent from sourceforge.net because testlilyissues-a...@lists.sourceforge.net is subscribed to https://sourceforge.net/p/testlilyissues/issues/ To unsubscribe from further messages, a project admin can change settings at https://sourceforge.net/p/testlilyissues/admin/issues/options. Or, if this is a mailing list, you can unsubscribe from the mailing list.-- Check out the vibrant tech community on one of the world's most engaging tech sites, Slashdot.org! http://sdm.link/slashdot___ Testlilyissues-auto mailing list testlilyissues-a...@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/testlilyissues-auto
[Lilypond-auto] [LilyIssues-auto] [testlilyissues:issues] #5147 Add whether to use OTF feature depending on Pango version
- Description has changed: Diff: --- old +++ new @@ -2,7 +2,7 @@ Issue 1338 requires Pango 1.38+ for using OpenType font feature. However, LilyDev 4.1 has Pango 1.36.8. -So it cannot compile Issue 1338. +So it cannot compile Issue 1388. This commit makes LilyPond can be configured without OpenType font feature if Pango is old. - **Needs**: --> --- ** [issues:#5147] Add whether to use OTF feature depending on Pango version** **Status:** Started **Created:** Tue Jun 13, 2017 12:19 PM UTC by Masamichi Hosoda **Last Updated:** Tue Jun 13, 2017 12:19 PM UTC **Owner:** Masamichi Hosoda Add whether to use OTF feature depending on Pango version Issue 1338 requires Pango 1.38+ for using OpenType font feature. However, LilyDev 4.1 has Pango 1.36.8. So it cannot compile Issue 1388. This commit makes LilyPond can be configured without OpenType font feature if Pango is old. Therefore, LilyPond become to be able to compile even by LilyDev 4.1 that has old Pango. However, the binary that compiled by LilyDev 4.1 cannot use OpenType feature. It is required Pango 1.38+ if you'd like to use the feature. This patch requires Issue 1388 https://sourceforge.net/p/testlilyissues/issues/1388/ https://codereview.appspot.com/323850043 http://codereview.appspot.com/322100043 --- Sent from sourceforge.net because testlilyissues-a...@lists.sourceforge.net is subscribed to https://sourceforge.net/p/testlilyissues/issues/ To unsubscribe from further messages, a project admin can change settings at https://sourceforge.net/p/testlilyissues/admin/issues/options. Or, if this is a mailing list, you can unsubscribe from the mailing list.-- Check out the vibrant tech community on one of the world's most engaging tech sites, Slashdot.org! http://sdm.link/slashdot___ Testlilyissues-auto mailing list testlilyissues-a...@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/testlilyissues-auto
[Lilypond-auto] [LilyIssues-auto] [testlilyissues:issues] #5147 Add whether to use OTF feature depending on Pango version
- Description has changed: Diff: --- old +++ new @@ -1,6 +1,6 @@ Add whether to use OTF feature depending on Pango version -Issue 1338 requires Pango 1.38+ for using OpenType font feature. +Issue 1388 requires Pango 1.38+ for using OpenType font feature. However, LilyDev 4.1 has Pango 1.36.8. So it cannot compile Issue 1388. --- ** [issues:#5147] Add whether to use OTF feature depending on Pango version** **Status:** Started **Created:** Tue Jun 13, 2017 12:19 PM UTC by Masamichi Hosoda **Last Updated:** Tue Jun 13, 2017 12:22 PM UTC **Owner:** Masamichi Hosoda Add whether to use OTF feature depending on Pango version Issue 1388 requires Pango 1.38+ for using OpenType font feature. However, LilyDev 4.1 has Pango 1.36.8. So it cannot compile Issue 1388. This commit makes LilyPond can be configured without OpenType font feature if Pango is old. Therefore, LilyPond become to be able to compile even by LilyDev 4.1 that has old Pango. However, the binary that compiled by LilyDev 4.1 cannot use OpenType feature. It is required Pango 1.38+ if you'd like to use the feature. This patch requires Issue 1388 https://sourceforge.net/p/testlilyissues/issues/1388/ https://codereview.appspot.com/323850043 http://codereview.appspot.com/322100043 --- Sent from sourceforge.net because testlilyissues-a...@lists.sourceforge.net is subscribed to https://sourceforge.net/p/testlilyissues/issues/ To unsubscribe from further messages, a project admin can change settings at https://sourceforge.net/p/testlilyissues/admin/issues/options. Or, if this is a mailing list, you can unsubscribe from the mailing list.-- Check out the vibrant tech community on one of the world's most engaging tech sites, Slashdot.org! http://sdm.link/slashdot___ Testlilyissues-auto mailing list testlilyissues-a...@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/testlilyissues-auto
[Lilypond-auto] [LilyIssues-auto] [testlilyissues:issues] #1388 Support OpenType font features
If I understand correctly, LilyDev 4.1 cannot compile this patch. In my humble opinion, it is necessary that LilyDev 4.1 can compile it. I've uploaded an additional patch that can be compiled by LilyDev 4.1. https://sourceforge.net/p/testlilyissues/issues/5147/ Jay, would you send us the git format-patch file? Then, I can commit your patch and my additional patch together. --- ** [issues:#1388] Support OpenType font features** **Status:** Started **Created:** Mon Nov 08, 2010 10:34 PM UTC by Anonymous **Last Updated:** Sun Jun 11, 2017 08:20 AM UTC **Owner:** horndude77 *Originally created by:* *anonymous *Originally created by:* [lemzw...@googlemail.com](http://code.google.com/u/102649819178652971408/) Currently, LilyPond doesn't support OpenType font features. For example, many fonts already contain glyphs for small caps letters, but lilypond can't access such glyphs directly since OpenType fonts don't need to have named glyphs, and you need to activate an OpenType feature \(\`smcp' in this particular case\) so that input character codes get properly mapped to caps glyphs. I suggest that we implement an interface similar to the \`fontspec' package for XeTeX and luatex: [http://www.ctan.org/get/macros/xetex/latex/fontspec/fontspec.pdf](http://www.ctan.org/get/macros/xetex/latex/fontspec/fontspec.pdf) --- Sent from sourceforge.net because testlilyissues-a...@lists.sourceforge.net is subscribed to https://sourceforge.net/p/testlilyissues/issues/ To unsubscribe from further messages, a project admin can change settings at https://sourceforge.net/p/testlilyissues/admin/issues/options. Or, if this is a mailing list, you can unsubscribe from the mailing list.-- Check out the vibrant tech community on one of the world's most engaging tech sites, Slashdot.org! http://sdm.link/slashdot___ Testlilyissues-auto mailing list testlilyissues-a...@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/testlilyissues-auto
[Lilypond-auto] [LilyIssues-auto] [testlilyissues:issues] #1388 Support OpenType font features
Patch can be downloaded as part of the review (https://codereview.appspot.com/download/issue323850043_20001.diff) or are you looking for something else? --- ** [issues:#1388] Support OpenType font features** **Status:** Started **Created:** Mon Nov 08, 2010 10:34 PM UTC by Anonymous **Last Updated:** Tue Jun 13, 2017 12:32 PM UTC **Owner:** horndude77 *Originally created by:* *anonymous *Originally created by:* [lemzw...@googlemail.com](http://code.google.com/u/102649819178652971408/) Currently, LilyPond doesn't support OpenType font features. For example, many fonts already contain glyphs for small caps letters, but lilypond can't access such glyphs directly since OpenType fonts don't need to have named glyphs, and you need to activate an OpenType feature \(\`smcp' in this particular case\) so that input character codes get properly mapped to caps glyphs. I suggest that we implement an interface similar to the \`fontspec' package for XeTeX and luatex: [http://www.ctan.org/get/macros/xetex/latex/fontspec/fontspec.pdf](http://www.ctan.org/get/macros/xetex/latex/fontspec/fontspec.pdf) --- Sent from sourceforge.net because testlilyissues-a...@lists.sourceforge.net is subscribed to https://sourceforge.net/p/testlilyissues/issues/ To unsubscribe from further messages, a project admin can change settings at https://sourceforge.net/p/testlilyissues/admin/issues/options. Or, if this is a mailing list, you can unsubscribe from the mailing list.-- Check out the vibrant tech community on one of the world's most engaging tech sites, Slashdot.org! http://sdm.link/slashdot___ Testlilyissues-auto mailing list testlilyissues-a...@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/testlilyissues-auto
[Lilypond-auto] [LilyIssues-auto] [testlilyissues:issues] #1228 merge simultaneous rests of the same duration
Minor edit to docs http://codereview.appspot.com/321930043 --- ** [issues:#1228] merge simultaneous rests of the same duration** **Status:** Started **Created:** Wed Aug 18, 2010 11:15 AM UTC by Anonymous **Last Updated:** Wed Jun 14, 2017 05:03 AM UTC **Owner:** horndude77 *Originally created by:* *anonymous *Originally created by:* [ralphbug...@gmail.com](http://code.google.com/u/106131861630194758622/) On 11 June 2010 16:27, Xavier Scheuer wrote: Could you implement the possibility: \override RestCollision \#'positioning-done = \#merge-rests-on-positioning described in [http://lsr.dsi.unimi.it/LSR/Item?id=336](http://lsr.dsi.unimi.it/LSR/Item?id=336) \_directly\_ into LilyPond? So we would not have to define merge-rests-on-positioning ourselves, each time we want to use this function. This function \_is useful\_, as shown by the several messages asking for this on lilypond-user: [http://lists.gnu.org/archive/cgi-bin/namazu.cgi?query=Merging+rests+&submit=Search!&idxname=lilypond-user](http://lists.gnu.org/archive/cgi-bin/namazu.cgi?query=Merging+rests+&submit=Search!&idxname=lilypond-user) That would also be great if you could overpass the limitations, i.e. – ability to handle more than two voices ; >– handle multi-measure/whole-measure rests. Maybe the following discussion could be helpful in a certain way: [http://lists.gnu.org/archive/html/lilypond-user/2010-02/msg00452.html](http://lists.gnu.org/archive/html/lilypond-user/2010-02/msg00452.html) --- Sent from sourceforge.net because testlilyissues-a...@lists.sourceforge.net is subscribed to https://sourceforge.net/p/testlilyissues/issues/ To unsubscribe from further messages, a project admin can change settings at https://sourceforge.net/p/testlilyissues/admin/issues/options. Or, if this is a mailing list, you can unsubscribe from the mailing list.-- Check out the vibrant tech community on one of the world's most engaging tech sites, Slashdot.org! http://sdm.link/slashdot___ Testlilyissues-auto mailing list testlilyissues-a...@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/testlilyissues-auto
[Lilypond-auto] [LilyIssues-auto] [testlilyissues:issues] #5141 Fix typos in \offset documentation
- **Patch**: countdown --> push - **Comment**: Patch counted down - please push. --- ** [issues:#5141] Fix typos in \offset documentation** **Status:** Started **Created:** Wed Jun 07, 2017 02:46 PM UTC by David Nalesnik **Last Updated:** Sun Jun 11, 2017 08:20 AM UTC **Owner:** David Nalesnik Fix typos in \offset documentation - Fix errors in description of OttavaBracket example - Minor improvements in wording http://codereview.appspot.com/322040043 --- Sent from sourceforge.net because testlilyissues-a...@lists.sourceforge.net is subscribed to https://sourceforge.net/p/testlilyissues/issues/ To unsubscribe from further messages, a project admin can change settings at https://sourceforge.net/p/testlilyissues/admin/issues/options. Or, if this is a mailing list, you can unsubscribe from the mailing list.-- Check out the vibrant tech community on one of the world's most engaging tech sites, Slashdot.org! http://sdm.link/slashdot___ Testlilyissues-auto mailing list testlilyissues-a...@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/testlilyissues-auto
[Lilypond-auto] [LilyIssues-auto] [testlilyissues:issues] #5144 lilypond-manuals.css: edit color scheme and some spacing
- **Patch**: review --> countdown - **Comment**: Patch on countdown for June 17th. --- ** [issues:#5144] lilypond-manuals.css: edit color scheme and some spacing** **Status:** Started **Created:** Sat Jun 10, 2017 05:23 PM UTC by Paul Morris **Last Updated:** Mon Jun 12, 2017 10:37 AM UTC **Owner:** Paul Morris lilypond-manuals.css: edit color scheme and some spacing This patch simplifies and (IMHO) improves the color scheme and spacing of the manuals on the web. I will include a link to screenshots and a demo site, with more details on what's different. http://codereview.appspot.com/322070043 --- Sent from sourceforge.net because testlilyissues-a...@lists.sourceforge.net is subscribed to https://sourceforge.net/p/testlilyissues/issues/ To unsubscribe from further messages, a project admin can change settings at https://sourceforge.net/p/testlilyissues/admin/issues/options. Or, if this is a mailing list, you can unsubscribe from the mailing list.-- Check out the vibrant tech community on one of the world's most engaging tech sites, Slashdot.org! http://sdm.link/slashdot___ Testlilyissues-auto mailing list testlilyissues-a...@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/testlilyissues-auto
[Lilypond-auto] [LilyIssues-auto] [testlilyissues:issues] #5146 Don't use \line in the implementation of \concat
- **Patch**: review --> countdown - **Comment**: Patch on countdown for June 17th. --- ** [issues:#5146] Don't use \line in the implementation of \concat** **Status:** Started **Created:** Mon Jun 12, 2017 06:34 PM UTC by David Kastrup **Last Updated:** Tue Jun 13, 2017 08:30 AM UTC **Owner:** David Kastrup Don't use \line in the implementation of \concat It doesn't really make any sense to override word-space temporarily and it does not make sense to heed text-direction when putting together stuff without actual word boundaries. http://codereview.appspot.com/325860043 --- Sent from sourceforge.net because testlilyissues-a...@lists.sourceforge.net is subscribed to https://sourceforge.net/p/testlilyissues/issues/ To unsubscribe from further messages, a project admin can change settings at https://sourceforge.net/p/testlilyissues/admin/issues/options. Or, if this is a mailing list, you can unsubscribe from the mailing list.-- Check out the vibrant tech community on one of the world's most engaging tech sites, Slashdot.org! http://sdm.link/slashdot___ Testlilyissues-auto mailing list testlilyissues-a...@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/testlilyissues-auto
[Lilypond-auto] [LilyIssues-auto] [testlilyissues:issues] #5145 Allow $... to specify a markup command
- **Patch**: review --> countdown - **Comment**: Patch on countdown for June 17th. --- ** [issues:#5145] Allow $... to specify a markup command** **Status:** Started **Created:** Mon Jun 12, 2017 03:16 PM UTC by David Kastrup **Last Updated:** Tue Jun 13, 2017 07:54 AM UTC **Owner:** David Kastrup Allow $... to specify a markup command This is a partial (though more flexible) substitute for \on-the-fly since it allows to replace \on-the-fly #(lambda (layout props args) ...) with $(let ((fun (lambda (layout props args) ...))) (set! (markup-command-signature fun) (list markup?)) fun) Namely: ad-hoc written functions (probably most useful when written using macros) can be employed as markup commands when preceded with $ as long as they have a suitable markup command signature attached. This feature is mainly added for consistency with music functions. Lexer: factor out push_markup_predicates http://codereview.appspot.com/322090043 --- Sent from sourceforge.net because testlilyissues-a...@lists.sourceforge.net is subscribed to https://sourceforge.net/p/testlilyissues/issues/ To unsubscribe from further messages, a project admin can change settings at https://sourceforge.net/p/testlilyissues/admin/issues/options. Or, if this is a mailing list, you can unsubscribe from the mailing list.-- Check out the vibrant tech community on one of the world's most engaging tech sites, Slashdot.org! http://sdm.link/slashdot___ Testlilyissues-auto mailing list testlilyissues-a...@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/testlilyissues-auto
[Lilypond-auto] [LilyIssues-auto] [testlilyissues:issues] #1228 merge simultaneous rests of the same duration
- **Needs**: --> - **Patch**: new --> review - **Type**: --> Enhancement - **Comment**: Passes make, make check and a full make doc. --- ** [issues:#1228] merge simultaneous rests of the same duration** **Status:** Started **Created:** Wed Aug 18, 2010 11:15 AM UTC by Anonymous **Last Updated:** Wed Jun 14, 2017 05:03 AM UTC **Owner:** horndude77 *Originally created by:* *anonymous *Originally created by:* [ralphbug...@gmail.com](http://code.google.com/u/106131861630194758622/) On 11 June 2010 16:27, Xavier Scheuer wrote: Could you implement the possibility: \override RestCollision \#'positioning-done = \#merge-rests-on-positioning described in [http://lsr.dsi.unimi.it/LSR/Item?id=336](http://lsr.dsi.unimi.it/LSR/Item?id=336) \_directly\_ into LilyPond? So we would not have to define merge-rests-on-positioning ourselves, each time we want to use this function. This function \_is useful\_, as shown by the several messages asking for this on lilypond-user: [http://lists.gnu.org/archive/cgi-bin/namazu.cgi?query=Merging+rests+&submit=Search!&idxname=lilypond-user](http://lists.gnu.org/archive/cgi-bin/namazu.cgi?query=Merging+rests+&submit=Search!&idxname=lilypond-user) That would also be great if you could overpass the limitations, i.e. – ability to handle more than two voices ; >– handle multi-measure/whole-measure rests. Maybe the following discussion could be helpful in a certain way: [http://lists.gnu.org/archive/html/lilypond-user/2010-02/msg00452.html](http://lists.gnu.org/archive/html/lilypond-user/2010-02/msg00452.html) --- Sent from sourceforge.net because testlilyissues-a...@lists.sourceforge.net is subscribed to https://sourceforge.net/p/testlilyissues/issues/ To unsubscribe from further messages, a project admin can change settings at https://sourceforge.net/p/testlilyissues/admin/issues/options. Or, if this is a mailing list, you can unsubscribe from the mailing list.-- Check out the vibrant tech community on one of the world's most engaging tech sites, Slashdot.org! http://sdm.link/slashdot___ Testlilyissues-auto mailing list testlilyissues-a...@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/testlilyissues-auto
[Lilypond-auto] [LilyIssues-auto] [testlilyissues:issues] #1388 Support OpenType font features
I'd like the following information for commiting your patch. * author's name * author's email * date of written * commit message Rietveld's patch file (https://codereview.appspot.com/download/issue323850043_20001.diff) does not contain them. `git format-patch` command genarates a patch file that contains them. http://lilypond.org/doc/v2.19/Documentation/contributor/patches#how-to-make-a-patch --- ** [issues:#1388] Support OpenType font features** **Status:** Started **Created:** Mon Nov 08, 2010 10:34 PM UTC by Anonymous **Last Updated:** Wed Jun 14, 2017 12:20 AM UTC **Owner:** horndude77 *Originally created by:* *anonymous *Originally created by:* [lemzw...@googlemail.com](http://code.google.com/u/102649819178652971408/) Currently, LilyPond doesn't support OpenType font features. For example, many fonts already contain glyphs for small caps letters, but lilypond can't access such glyphs directly since OpenType fonts don't need to have named glyphs, and you need to activate an OpenType feature \(\`smcp' in this particular case\) so that input character codes get properly mapped to caps glyphs. I suggest that we implement an interface similar to the \`fontspec' package for XeTeX and luatex: [http://www.ctan.org/get/macros/xetex/latex/fontspec/fontspec.pdf](http://www.ctan.org/get/macros/xetex/latex/fontspec/fontspec.pdf) --- Sent from sourceforge.net because testlilyissues-a...@lists.sourceforge.net is subscribed to https://sourceforge.net/p/testlilyissues/issues/ To unsubscribe from further messages, a project admin can change settings at https://sourceforge.net/p/testlilyissues/admin/issues/options. Or, if this is a mailing list, you can unsubscribe from the mailing list.-- Check out the vibrant tech community on one of the world's most engaging tech sites, Slashdot.org! http://sdm.link/slashdot___ Testlilyissues-auto mailing list testlilyissues-a...@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/testlilyissues-auto
[Lilypond-auto] [LilyIssues-auto] [testlilyissues:issues] #5147 Add whether to use OTF feature depending on Pango version
- **Patch**: new --> review - **Comment**: Passes make, make check and a full make doc. --- ** [issues:#5147] Add whether to use OTF feature depending on Pango version** **Status:** Started **Created:** Tue Jun 13, 2017 12:19 PM UTC by Masamichi Hosoda **Last Updated:** Tue Jun 13, 2017 12:23 PM UTC **Owner:** Masamichi Hosoda Add whether to use OTF feature depending on Pango version Issue 1388 requires Pango 1.38+ for using OpenType font feature. However, LilyDev 4.1 has Pango 1.36.8. So it cannot compile Issue 1388. This commit makes LilyPond can be configured without OpenType font feature if Pango is old. Therefore, LilyPond become to be able to compile even by LilyDev 4.1 that has old Pango. However, the binary that compiled by LilyDev 4.1 cannot use OpenType feature. It is required Pango 1.38+ if you'd like to use the feature. This patch requires Issue 1388 https://sourceforge.net/p/testlilyissues/issues/1388/ https://codereview.appspot.com/323850043 http://codereview.appspot.com/322100043 --- Sent from sourceforge.net because testlilyissues-a...@lists.sourceforge.net is subscribed to https://sourceforge.net/p/testlilyissues/issues/ To unsubscribe from further messages, a project admin can change settings at https://sourceforge.net/p/testlilyissues/admin/issues/options. Or, if this is a mailing list, you can unsubscribe from the mailing list.-- Check out the vibrant tech community on one of the world's most engaging tech sites, Slashdot.org! http://sdm.link/slashdot___ Testlilyissues-auto mailing list testlilyissues-a...@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/testlilyissues-auto
[Lilypond-auto] [LilyIssues-auto] [testlilyissues:issues] #1388 Support OpenType font features
Understood. Patch attached. Thanks. Attachments: - [0001-Initial-work-to-support-opentype-font-features.patch](https://sourceforge.net/p/testlilyissues/issues/_discuss/thread/ec7b7711/ff0d/attachment/0001-Initial-work-to-support-opentype-font-features.patch) (7.2 kB; text/x-patch) --- ** [issues:#1388] Support OpenType font features** **Status:** Started **Created:** Mon Nov 08, 2010 10:34 PM UTC by Anonymous **Last Updated:** Wed Jun 14, 2017 11:32 AM UTC **Owner:** horndude77 *Originally created by:* *anonymous *Originally created by:* [lemzw...@googlemail.com](http://code.google.com/u/102649819178652971408/) Currently, LilyPond doesn't support OpenType font features. For example, many fonts already contain glyphs for small caps letters, but lilypond can't access such glyphs directly since OpenType fonts don't need to have named glyphs, and you need to activate an OpenType feature \(\`smcp' in this particular case\) so that input character codes get properly mapped to caps glyphs. I suggest that we implement an interface similar to the \`fontspec' package for XeTeX and luatex: [http://www.ctan.org/get/macros/xetex/latex/fontspec/fontspec.pdf](http://www.ctan.org/get/macros/xetex/latex/fontspec/fontspec.pdf) --- Sent from sourceforge.net because testlilyissues-a...@lists.sourceforge.net is subscribed to https://sourceforge.net/p/testlilyissues/issues/ To unsubscribe from further messages, a project admin can change settings at https://sourceforge.net/p/testlilyissues/admin/issues/options. Or, if this is a mailing list, you can unsubscribe from the mailing list.-- Check out the vibrant tech community on one of the world's most engaging tech sites, Slashdot.org! http://sdm.link/slashdot___ Testlilyissues-auto mailing list testlilyissues-a...@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/testlilyissues-auto
[Lilypond-auto] [LilyIssues-auto] [testlilyissues:issues] #5140 Fix granados example
- **status**: Fixed --> Verified --- ** [issues:#5140] Fix granados example** **Status:** Verified **Labels:** Fixed_2_19_62 **Created:** Mon May 29, 2017 04:39 PM UTC by Phil Holmes **Last Updated:** Tue Jun 06, 2017 12:52 PM UTC **Owner:** Phil Holmes Fix granados example http://codereview.appspot.com/297540043 --- Sent from sourceforge.net because testlilyissues-a...@lists.sourceforge.net is subscribed to https://sourceforge.net/p/testlilyissues/issues/ To unsubscribe from further messages, a project admin can change settings at https://sourceforge.net/p/testlilyissues/admin/issues/options. Or, if this is a mailing list, you can unsubscribe from the mailing list.-- Check out the vibrant tech community on one of the world's most engaging tech sites, Slashdot.org! http://sdm.link/slashdot___ Testlilyissues-auto mailing list testlilyissues-a...@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/testlilyissues-auto
[Lilypond-auto] [LilyIssues-auto] [testlilyissues:issues] #5139 abc2ly: Support R (rhythm / meter) and Z (transcription) fields
- **status**: Fixed --> Verified --- ** [issues:#5139] abc2ly: Support R (rhythm / meter) and Z (transcription) fields** **Status:** Verified **Labels:** Fixed_2_19_62 **Created:** Mon May 22, 2017 07:41 PM UTC by Paul Morris **Last Updated:** Thu Jun 01, 2017 02:52 PM UTC **Owner:** Paul Morris abc2ly: Support R (rhythm / meter) and Z (transcription) fields http://codereview.appspot.com/324890043 --- Sent from sourceforge.net because testlilyissues-a...@lists.sourceforge.net is subscribed to https://sourceforge.net/p/testlilyissues/issues/ To unsubscribe from further messages, a project admin can change settings at https://sourceforge.net/p/testlilyissues/admin/issues/options. Or, if this is a mailing list, you can unsubscribe from the mailing list.-- Check out the vibrant tech community on one of the world's most engaging tech sites, Slashdot.org! http://sdm.link/slashdot___ Testlilyissues-auto mailing list testlilyissues-a...@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/testlilyissues-auto
[Lilypond-auto] [LilyIssues-auto] [testlilyissues:issues] #5148 Various chain-assoc-get -> #:properties
--- ** [issues:#5148] Various chain-assoc-get -> #:properties** **Status:** Started **Created:** Fri Jun 16, 2017 08:55 AM UTC by David Kastrup **Last Updated:** Fri Jun 16, 2017 08:55 AM UTC **Owner:** nobody Various chain-assoc-get -> #:properties Also contains commits: three-sided-box snippet: use #:properties keyword Run scripts/auxiliar/makelsr.py http://codereview.appspot.com/323940043 --- Sent from sourceforge.net because testlilyissues-a...@lists.sourceforge.net is subscribed to https://sourceforge.net/p/testlilyissues/issues/ To unsubscribe from further messages, a project admin can change settings at https://sourceforge.net/p/testlilyissues/admin/issues/options. Or, if this is a mailing list, you can unsubscribe from the mailing list.-- Check out the vibrant tech community on one of the world's most engaging tech sites, Slashdot.org! http://sdm.link/slashdot___ Testlilyissues-auto mailing list testlilyissues-a...@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/testlilyissues-auto
[Lilypond-auto] [LilyIssues-auto] [testlilyissues:issues] #5148 Various chain-assoc-get -> #:properties
Remove tab http://codereview.appspot.com/323940043 --- ** [issues:#5148] Various chain-assoc-get -> #:properties** **Status:** Started **Created:** Fri Jun 16, 2017 08:55 AM UTC by David Kastrup **Last Updated:** Fri Jun 16, 2017 10:44 AM UTC **Owner:** David Kastrup Various chain-assoc-get -> #:properties Also contains commits: three-sided-box snippet: use #:properties keyword Run scripts/auxiliar/makelsr.py http://codereview.appspot.com/323940043 --- Sent from sourceforge.net because testlilyissues-a...@lists.sourceforge.net is subscribed to https://sourceforge.net/p/testlilyissues/issues/ To unsubscribe from further messages, a project admin can change settings at https://sourceforge.net/p/testlilyissues/admin/issues/options. Or, if this is a mailing list, you can unsubscribe from the mailing list.-- Check out the vibrant tech community on one of the world's most engaging tech sites, Slashdot.org! http://sdm.link/slashdot___ Testlilyissues-auto mailing list testlilyissues-a...@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/testlilyissues-auto
[Lilypond-auto] [LilyIssues-auto] [testlilyissues:issues] #5148 Various chain-assoc-get -> #:properties
- Description has changed: Diff: - **Needs**: --> - **Patch**: new --> review - **Type**: --> Enhancement - **Comment**: Passes make, make check and a full make doc. --- ** [issues:#5148] Various chain-assoc-get -> #:properties** **Status:** Started **Created:** Fri Jun 16, 2017 08:55 AM UTC by David Kastrup **Last Updated:** Fri Jun 16, 2017 10:44 AM UTC **Owner:** David Kastrup Various chain-assoc-get -> #:properties Also contains commits: three-sided-box snippet: use #:properties keyword Run scripts/auxiliar/makelsr.py http://codereview.appspot.com/323940043 --- Sent from sourceforge.net because testlilyissues-a...@lists.sourceforge.net is subscribed to https://sourceforge.net/p/testlilyissues/issues/ To unsubscribe from further messages, a project admin can change settings at https://sourceforge.net/p/testlilyissues/admin/issues/options. Or, if this is a mailing list, you can unsubscribe from the mailing list.-- Check out the vibrant tech community on one of the world's most engaging tech sites, Slashdot.org! http://sdm.link/slashdot___ Testlilyissues-auto mailing list testlilyissues-a...@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/testlilyissues-auto
[Lilypond-auto] [LilyIssues-auto] [testlilyissues:issues] #5144 lilypond-manuals.css: edit color scheme and some spacing
- **Patch**: countdown --> push - **Comment**: Patch counted down - please push. --- ** [issues:#5144] lilypond-manuals.css: edit color scheme and some spacing** **Status:** Started **Created:** Sat Jun 10, 2017 05:23 PM UTC by Paul Morris **Last Updated:** Wed Jun 14, 2017 07:41 AM UTC **Owner:** Paul Morris lilypond-manuals.css: edit color scheme and some spacing This patch simplifies and (IMHO) improves the color scheme and spacing of the manuals on the web. I will include a link to screenshots and a demo site, with more details on what's different. http://codereview.appspot.com/322070043 --- Sent from sourceforge.net because testlilyissues-a...@lists.sourceforge.net is subscribed to https://sourceforge.net/p/testlilyissues/issues/ To unsubscribe from further messages, a project admin can change settings at https://sourceforge.net/p/testlilyissues/admin/issues/options. Or, if this is a mailing list, you can unsubscribe from the mailing list.-- Check out the vibrant tech community on one of the world's most engaging tech sites, Slashdot.org! http://sdm.link/slashdot___ Testlilyissues-auto mailing list testlilyissues-a...@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/testlilyissues-auto
[Lilypond-auto] [LilyIssues-auto] [testlilyissues:issues] #5145 Allow $... to specify a markup command
- **Patch**: countdown --> push - **Comment**: Patch counted down - please push. --- ** [issues:#5145] Allow $... to specify a markup command** **Status:** Started **Created:** Mon Jun 12, 2017 03:16 PM UTC by David Kastrup **Last Updated:** Wed Jun 14, 2017 07:41 AM UTC **Owner:** David Kastrup Allow $... to specify a markup command This is a partial (though more flexible) substitute for \on-the-fly since it allows to replace \on-the-fly #(lambda (layout props args) ...) with $(let ((fun (lambda (layout props args) ...))) (set! (markup-command-signature fun) (list markup?)) fun) Namely: ad-hoc written functions (probably most useful when written using macros) can be employed as markup commands when preceded with $ as long as they have a suitable markup command signature attached. This feature is mainly added for consistency with music functions. Lexer: factor out push_markup_predicates http://codereview.appspot.com/322090043 --- Sent from sourceforge.net because testlilyissues-a...@lists.sourceforge.net is subscribed to https://sourceforge.net/p/testlilyissues/issues/ To unsubscribe from further messages, a project admin can change settings at https://sourceforge.net/p/testlilyissues/admin/issues/options. Or, if this is a mailing list, you can unsubscribe from the mailing list.-- Check out the vibrant tech community on one of the world's most engaging tech sites, Slashdot.org! http://sdm.link/slashdot___ Testlilyissues-auto mailing list testlilyissues-a...@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/testlilyissues-auto
[Lilypond-auto] [LilyIssues-auto] [testlilyissues:issues] #5146 Don't use \line in the implementation of \concat
- **Patch**: countdown --> push - **Comment**: Patch counted down - please push. --- ** [issues:#5146] Don't use \line in the implementation of \concat** **Status:** Started **Created:** Mon Jun 12, 2017 06:34 PM UTC by David Kastrup **Last Updated:** Wed Jun 14, 2017 07:41 AM UTC **Owner:** David Kastrup Don't use \line in the implementation of \concat It doesn't really make any sense to override word-space temporarily and it does not make sense to heed text-direction when putting together stuff without actual word boundaries. http://codereview.appspot.com/325860043 --- Sent from sourceforge.net because testlilyissues-a...@lists.sourceforge.net is subscribed to https://sourceforge.net/p/testlilyissues/issues/ To unsubscribe from further messages, a project admin can change settings at https://sourceforge.net/p/testlilyissues/admin/issues/options. Or, if this is a mailing list, you can unsubscribe from the mailing list.-- Check out the vibrant tech community on one of the world's most engaging tech sites, Slashdot.org! http://sdm.link/slashdot___ Testlilyissues-auto mailing list testlilyissues-a...@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/testlilyissues-auto
[Lilypond-auto] [LilyIssues-auto] [testlilyissues:issues] #1228 merge simultaneous rests of the same duration
patch on countdown for June 20th --- ** [issues:#1228] merge simultaneous rests of the same duration** **Status:** Started **Created:** Wed Aug 18, 2010 11:15 AM UTC by Anonymous **Last Updated:** Wed Jun 14, 2017 10:04 AM UTC **Owner:** horndude77 *Originally created by:* *anonymous *Originally created by:* [ralphbug...@gmail.com](http://code.google.com/u/106131861630194758622/) On 11 June 2010 16:27, Xavier Scheuer wrote: Could you implement the possibility: \override RestCollision \#'positioning-done = \#merge-rests-on-positioning described in [http://lsr.dsi.unimi.it/LSR/Item?id=336](http://lsr.dsi.unimi.it/LSR/Item?id=336) \_directly\_ into LilyPond? So we would not have to define merge-rests-on-positioning ourselves, each time we want to use this function. This function \_is useful\_, as shown by the several messages asking for this on lilypond-user: [http://lists.gnu.org/archive/cgi-bin/namazu.cgi?query=Merging+rests+&submit=Search!&idxname=lilypond-user](http://lists.gnu.org/archive/cgi-bin/namazu.cgi?query=Merging+rests+&submit=Search!&idxname=lilypond-user) That would also be great if you could overpass the limitations, i.e. – ability to handle more than two voices ; >– handle multi-measure/whole-measure rests. Maybe the following discussion could be helpful in a certain way: [http://lists.gnu.org/archive/html/lilypond-user/2010-02/msg00452.html](http://lists.gnu.org/archive/html/lilypond-user/2010-02/msg00452.html) --- Sent from sourceforge.net because testlilyissues-a...@lists.sourceforge.net is subscribed to https://sourceforge.net/p/testlilyissues/issues/ To unsubscribe from further messages, a project admin can change settings at https://sourceforge.net/p/testlilyissues/admin/issues/options. Or, if this is a mailing list, you can unsubscribe from the mailing list.-- Check out the vibrant tech community on one of the world's most engaging tech sites, Slashdot.org! http://sdm.link/slashdot___ Testlilyissues-auto mailing list testlilyissues-a...@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/testlilyissues-auto
[Lilypond-auto] [LilyIssues-auto] [testlilyissues:issues] #1228 merge simultaneous rests of the same duration
- **Patch**: review --> countdown --- ** [issues:#1228] merge simultaneous rests of the same duration** **Status:** Started **Created:** Wed Aug 18, 2010 11:15 AM UTC by Anonymous **Last Updated:** Fri Jun 16, 2017 11:13 PM UTC **Owner:** horndude77 *Originally created by:* *anonymous *Originally created by:* [ralphbug...@gmail.com](http://code.google.com/u/106131861630194758622/) On 11 June 2010 16:27, Xavier Scheuer wrote: Could you implement the possibility: \override RestCollision \#'positioning-done = \#merge-rests-on-positioning described in [http://lsr.dsi.unimi.it/LSR/Item?id=336](http://lsr.dsi.unimi.it/LSR/Item?id=336) \_directly\_ into LilyPond? So we would not have to define merge-rests-on-positioning ourselves, each time we want to use this function. This function \_is useful\_, as shown by the several messages asking for this on lilypond-user: [http://lists.gnu.org/archive/cgi-bin/namazu.cgi?query=Merging+rests+&submit=Search!&idxname=lilypond-user](http://lists.gnu.org/archive/cgi-bin/namazu.cgi?query=Merging+rests+&submit=Search!&idxname=lilypond-user) That would also be great if you could overpass the limitations, i.e. – ability to handle more than two voices ; >– handle multi-measure/whole-measure rests. Maybe the following discussion could be helpful in a certain way: [http://lists.gnu.org/archive/html/lilypond-user/2010-02/msg00452.html](http://lists.gnu.org/archive/html/lilypond-user/2010-02/msg00452.html) --- Sent from sourceforge.net because testlilyissues-a...@lists.sourceforge.net is subscribed to https://sourceforge.net/p/testlilyissues/issues/ To unsubscribe from further messages, a project admin can change settings at https://sourceforge.net/p/testlilyissues/admin/issues/options. Or, if this is a mailing list, you can unsubscribe from the mailing list.-- Check out the vibrant tech community on one of the world's most engaging tech sites, Slashdot.org! http://sdm.link/slashdot___ Testlilyissues-auto mailing list testlilyissues-a...@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/testlilyissues-auto
[Lilypond-auto] [LilyIssues-auto] [testlilyissues:issues] #5147 Add whether to use OTF feature depending on Pango version
- **Patch**: review --> countdown - **Comment**: patch on countdown for June 20th --- ** [issues:#5147] Add whether to use OTF feature depending on Pango version** **Status:** Started **Created:** Tue Jun 13, 2017 12:19 PM UTC by Masamichi Hosoda **Last Updated:** Wed Jun 14, 2017 06:05 PM UTC **Owner:** Masamichi Hosoda Add whether to use OTF feature depending on Pango version Issue 1388 requires Pango 1.38+ for using OpenType font feature. However, LilyDev 4.1 has Pango 1.36.8. So it cannot compile Issue 1388. This commit makes LilyPond can be configured without OpenType font feature if Pango is old. Therefore, LilyPond become to be able to compile even by LilyDev 4.1 that has old Pango. However, the binary that compiled by LilyDev 4.1 cannot use OpenType feature. It is required Pango 1.38+ if you'd like to use the feature. This patch requires Issue 1388 https://sourceforge.net/p/testlilyissues/issues/1388/ https://codereview.appspot.com/323850043 http://codereview.appspot.com/322100043 --- Sent from sourceforge.net because testlilyissues-a...@lists.sourceforge.net is subscribed to https://sourceforge.net/p/testlilyissues/issues/ To unsubscribe from further messages, a project admin can change settings at https://sourceforge.net/p/testlilyissues/admin/issues/options. Or, if this is a mailing list, you can unsubscribe from the mailing list.-- Check out the vibrant tech community on one of the world's most engaging tech sites, Slashdot.org! http://sdm.link/slashdot___ Testlilyissues-auto mailing list testlilyissues-a...@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/testlilyissues-auto
[Lilypond-auto] [LilyIssues-auto] [testlilyissues:issues] #5145 Allow $... to specify a markup command
- **labels**: --> Fixed_2_19_63 - **status**: Started --> Fixed - **Patch**: push --> - **Comment**: Pushed to staging as commit c3b51542671a9af5647d4cbc63f7c8ae98c1c2bd Author: David Kastrup Date: Mon Jun 12 13:44:51 2017 +0200 Issue 5145/2: Allow $... to specify a markup command This is a partial (though more flexible) substitute for \on-the-fly since it allows to replace \on-the-fly #(lambda (layout props args) ...) with $(let ((fun (lambda (layout props args) ...))) (set! (markup-command-signature fun) (list markup?)) fun) Namely: ad-hoc written functions (probably most useful when written using macros) can be employed as markup commands when preceded with $ as long as they have a suitable markup command signature attached. This feature is mainly added for consistency with music functions. --- ** [issues:#5145] Allow $... to specify a markup command** **Status:** Fixed **Labels:** Fixed_2_19_63 **Created:** Mon Jun 12, 2017 03:16 PM UTC by David Kastrup **Last Updated:** Fri Jun 16, 2017 11:12 PM UTC **Owner:** David Kastrup Allow $... to specify a markup command This is a partial (though more flexible) substitute for \on-the-fly since it allows to replace \on-the-fly #(lambda (layout props args) ...) with $(let ((fun (lambda (layout props args) ...))) (set! (markup-command-signature fun) (list markup?)) fun) Namely: ad-hoc written functions (probably most useful when written using macros) can be employed as markup commands when preceded with $ as long as they have a suitable markup command signature attached. This feature is mainly added for consistency with music functions. Lexer: factor out push_markup_predicates http://codereview.appspot.com/322090043 --- Sent from sourceforge.net because testlilyissues-a...@lists.sourceforge.net is subscribed to https://sourceforge.net/p/testlilyissues/issues/ To unsubscribe from further messages, a project admin can change settings at https://sourceforge.net/p/testlilyissues/admin/issues/options. Or, if this is a mailing list, you can unsubscribe from the mailing list.-- Check out the vibrant tech community on one of the world's most engaging tech sites, Slashdot.org! http://sdm.link/slashdot___ Testlilyissues-auto mailing list testlilyissues-a...@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/testlilyissues-auto
[Lilypond-auto] [LilyIssues-auto] [testlilyissues:issues] #5146 Don't use \line in the implementation of \concat
- **labels**: --> Fixed_2_19_63 - **status**: Started --> Fixed - **Patch**: push --> - **Type**: Enhancement --> Maintainability - **Comment**: Pushed to staging as commit 0c201efa0df6baa2f3d0f452646de07216f97608 Author: David Kastrup Date: Mon Jun 12 20:33:40 2017 +0200 Issue 5146: Don't use \line in the implementation of \concat It doesn't really make any sense to override word-space temporarily and it does not make sense to heed text-direction when putting together stuff without actual word boundaries. --- ** [issues:#5146] Don't use \line in the implementation of \concat** **Status:** Fixed **Labels:** Fixed_2_19_63 **Created:** Mon Jun 12, 2017 06:34 PM UTC by David Kastrup **Last Updated:** Fri Jun 16, 2017 11:12 PM UTC **Owner:** David Kastrup Don't use \line in the implementation of \concat It doesn't really make any sense to override word-space temporarily and it does not make sense to heed text-direction when putting together stuff without actual word boundaries. http://codereview.appspot.com/325860043 --- Sent from sourceforge.net because testlilyissues-a...@lists.sourceforge.net is subscribed to https://sourceforge.net/p/testlilyissues/issues/ To unsubscribe from further messages, a project admin can change settings at https://sourceforge.net/p/testlilyissues/admin/issues/options. Or, if this is a mailing list, you can unsubscribe from the mailing list.-- Check out the vibrant tech community on one of the world's most engaging tech sites, Slashdot.org! http://sdm.link/slashdot___ Testlilyissues-auto mailing list testlilyissues-a...@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/testlilyissues-auto
[Lilypond-auto] [LilyIssues-auto] [testlilyissues:issues] #5141 Fix typos in \offset documentation
- **labels**: --> Fixed_2_19_63 - **status**: Started --> Fixed - **Patch**: push --> - **Comment**: Pushed to staging as commit c377d85f06e524599d20e9edf102ae186ede5e77. --- ** [issues:#5141] Fix typos in \offset documentation** **Status:** Fixed **Labels:** Fixed_2_19_63 **Created:** Wed Jun 07, 2017 02:46 PM UTC by David Nalesnik **Last Updated:** Wed Jun 14, 2017 07:39 AM UTC **Owner:** David Nalesnik Fix typos in \offset documentation - Fix errors in description of OttavaBracket example - Minor improvements in wording http://codereview.appspot.com/322040043 --- Sent from sourceforge.net because testlilyissues-a...@lists.sourceforge.net is subscribed to https://sourceforge.net/p/testlilyissues/issues/ To unsubscribe from further messages, a project admin can change settings at https://sourceforge.net/p/testlilyissues/admin/issues/options. Or, if this is a mailing list, you can unsubscribe from the mailing list.-- Check out the vibrant tech community on one of the world's most engaging tech sites, Slashdot.org! http://sdm.link/slashdot___ Testlilyissues-auto mailing list testlilyissues-a...@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/testlilyissues-auto
[Lilypond-auto] [LilyIssues-auto] [testlilyissues:issues] #5144 lilypond-manuals.css: edit color scheme and some spacing
Pushed to staging: commit 90e4d7057f3857da049dfda3d130017d4719bd6b Author: Paul Morris Date: Mon May 22 15:02:52 2017 -0400 --- ** [issues:#5144] lilypond-manuals.css: edit color scheme and some spacing** **Status:** Started **Created:** Sat Jun 10, 2017 05:23 PM UTC by Paul Morris **Last Updated:** Fri Jun 16, 2017 11:11 PM UTC **Owner:** Paul Morris lilypond-manuals.css: edit color scheme and some spacing This patch simplifies and (IMHO) improves the color scheme and spacing of the manuals on the web. I will include a link to screenshots and a demo site, with more details on what's different. http://codereview.appspot.com/322070043 --- Sent from sourceforge.net because testlilyissues-a...@lists.sourceforge.net is subscribed to https://sourceforge.net/p/testlilyissues/issues/ To unsubscribe from further messages, a project admin can change settings at https://sourceforge.net/p/testlilyissues/admin/issues/options. Or, if this is a mailing list, you can unsubscribe from the mailing list.-- Check out the vibrant tech community on one of the world's most engaging tech sites, Slashdot.org! http://sdm.link/slashdot___ Testlilyissues-auto mailing list testlilyissues-a...@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/testlilyissues-auto
[Lilypond-auto] [LilyIssues-auto] [testlilyissues:issues] #5149 lilypond-manuals.css: Add a maximum width for manuals sidebar
--- ** [issues:#5149] lilypond-manuals.css: Add a maximum width for manuals sidebar** **Status:** Started **Created:** Sat Jun 17, 2017 09:57 PM UTC by Paul Morris **Last Updated:** Sat Jun 17, 2017 09:57 PM UTC **Owner:** nobody lilypond-manuals.css: Add a maximum width for manuals sidebar When the browser window is 1280px wide or more, the sidebar will be 346px wide, rather than a percentage of the window width. Also contains these two commits: lilypond-manuals.css: A better brown for the usage manual I think this shade goes better with the other colors, giving us a more coherent color scheme across manuals. lilypond-manuals.css: Add space between top-levels in sidebar (This one was originally in my last patch for the manuals css, but I found a better way to do it, so removed it from the previous patch and including it here.) http://codereview.appspot.com/328740043 --- Sent from sourceforge.net because testlilyissues-a...@lists.sourceforge.net is subscribed to https://sourceforge.net/p/testlilyissues/issues/ To unsubscribe from further messages, a project admin can change settings at https://sourceforge.net/p/testlilyissues/admin/issues/options. Or, if this is a mailing list, you can unsubscribe from the mailing list.-- Check out the vibrant tech community on one of the world's most engaging tech sites, Slashdot.org! http://sdm.link/slashdot___ Testlilyissues-auto mailing list testlilyissues-a...@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/testlilyissues-auto
[Lilypond-auto] [LilyIssues-auto] [testlilyissues:issues] #5149 lilypond-manuals.css: Add a maximum width for manuals sidebar
Screenshot showing previous brown color. Attachments: - [Screen-Shot-2017-06-17-previous-brown.png](https://sourceforge.net/p/testlilyissues/issues/_discuss/thread/d0ff0bf5/7e89/attachment/Screen-Shot-2017-06-17-previous-brown.png) (140.3 kB; image/png) --- ** [issues:#5149] lilypond-manuals.css: Add a maximum width for manuals sidebar** **Status:** Started **Created:** Sat Jun 17, 2017 09:57 PM UTC by Paul Morris **Last Updated:** Sat Jun 17, 2017 09:57 PM UTC **Owner:** Paul Morris lilypond-manuals.css: Add a maximum width for manuals sidebar When the browser window is 1280px wide or more, the sidebar will be 346px wide, rather than a percentage of the window width. Also contains these two commits: lilypond-manuals.css: A better brown for the usage manual I think this shade goes better with the other colors, giving us a more coherent color scheme across manuals. lilypond-manuals.css: Add space between top-levels in sidebar (This one was originally in my last patch for the manuals css, but I found a better way to do it, so removed it from the previous patch and including it here.) http://codereview.appspot.com/328740043 --- Sent from sourceforge.net because testlilyissues-a...@lists.sourceforge.net is subscribed to https://sourceforge.net/p/testlilyissues/issues/ To unsubscribe from further messages, a project admin can change settings at https://sourceforge.net/p/testlilyissues/admin/issues/options. Or, if this is a mailing list, you can unsubscribe from the mailing list.-- Check out the vibrant tech community on one of the world's most engaging tech sites, Slashdot.org! http://sdm.link/slashdot___ Testlilyissues-auto mailing list testlilyissues-a...@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/testlilyissues-auto
[Lilypond-auto] [LilyIssues-auto] [testlilyissues:issues] #5147 Add whether to use OTF feature depending on Pango version
- **Patch**: countdown --> push - **Comment**: Patch counted down - please push. Hosoda-san can push this at the same time he pushes the fix for https://sourceforge.net/p/testlilyissues/issues/1388 --- ** [issues:#5147] Add whether to use OTF feature depending on Pango version** **Status:** Started **Created:** Tue Jun 13, 2017 12:19 PM UTC by Masamichi Hosoda **Last Updated:** Fri Jun 16, 2017 11:15 PM UTC **Owner:** Masamichi Hosoda Add whether to use OTF feature depending on Pango version Issue 1388 requires Pango 1.38+ for using OpenType font feature. However, LilyDev 4.1 has Pango 1.36.8. So it cannot compile Issue 1388. This commit makes LilyPond can be configured without OpenType font feature if Pango is old. Therefore, LilyPond become to be able to compile even by LilyDev 4.1 that has old Pango. However, the binary that compiled by LilyDev 4.1 cannot use OpenType feature. It is required Pango 1.38+ if you'd like to use the feature. This patch requires Issue 1388 https://sourceforge.net/p/testlilyissues/issues/1388/ https://codereview.appspot.com/323850043 http://codereview.appspot.com/322100043 --- Sent from sourceforge.net because testlilyissues-a...@lists.sourceforge.net is subscribed to https://sourceforge.net/p/testlilyissues/issues/ To unsubscribe from further messages, a project admin can change settings at https://sourceforge.net/p/testlilyissues/admin/issues/options. Or, if this is a mailing list, you can unsubscribe from the mailing list.-- Check out the vibrant tech community on one of the world's most engaging tech sites, Slashdot.org! http://sdm.link/slashdot___ Testlilyissues-auto mailing list testlilyissues-a...@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/testlilyissues-auto
[Lilypond-auto] [LilyIssues-auto] [testlilyissues:issues] #1388 Support OpenType font features
Patch counted down - please push. Hosoda-san can push this at the same time he pushes his fix for https://sourceforge.net/p/testlilyissues/issues/5147/ --- ** [issues:#1388] Support OpenType font features** **Status:** Started **Created:** Mon Nov 08, 2010 10:34 PM UTC by Anonymous **Last Updated:** Fri Jun 16, 2017 05:44 AM UTC **Owner:** horndude77 *Originally created by:* *anonymous *Originally created by:* [lemzw...@googlemail.com](http://code.google.com/u/102649819178652971408/) Currently, LilyPond doesn't support OpenType font features. For example, many fonts already contain glyphs for small caps letters, but lilypond can't access such glyphs directly since OpenType fonts don't need to have named glyphs, and you need to activate an OpenType feature \(\`smcp' in this particular case\) so that input character codes get properly mapped to caps glyphs. I suggest that we implement an interface similar to the \`fontspec' package for XeTeX and luatex: [http://www.ctan.org/get/macros/xetex/latex/fontspec/fontspec.pdf](http://www.ctan.org/get/macros/xetex/latex/fontspec/fontspec.pdf) --- Sent from sourceforge.net because testlilyissues-a...@lists.sourceforge.net is subscribed to https://sourceforge.net/p/testlilyissues/issues/ To unsubscribe from further messages, a project admin can change settings at https://sourceforge.net/p/testlilyissues/admin/issues/options. Or, if this is a mailing list, you can unsubscribe from the mailing list.-- Check out the vibrant tech community on one of the world's most engaging tech sites, Slashdot.org! http://sdm.link/slashdot___ Testlilyissues-auto mailing list testlilyissues-a...@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/testlilyissues-auto
[Lilypond-auto] [LilyIssues-auto] [testlilyissues:issues] #1228 merge simultaneous rests of the same duration
- **Patch**: countdown --> push - **Comment**: Patch counted down - I will push this for you. --- ** [issues:#1228] merge simultaneous rests of the same duration** **Status:** Started **Created:** Wed Aug 18, 2010 11:15 AM UTC by Anonymous **Last Updated:** Fri Jun 16, 2017 11:14 PM UTC **Owner:** horndude77 *Originally created by:* *anonymous *Originally created by:* [ralphbug...@gmail.com](http://code.google.com/u/106131861630194758622/) On 11 June 2010 16:27, Xavier Scheuer wrote: Could you implement the possibility: \override RestCollision \#'positioning-done = \#merge-rests-on-positioning described in [http://lsr.dsi.unimi.it/LSR/Item?id=336](http://lsr.dsi.unimi.it/LSR/Item?id=336) \_directly\_ into LilyPond? So we would not have to define merge-rests-on-positioning ourselves, each time we want to use this function. This function \_is useful\_, as shown by the several messages asking for this on lilypond-user: [http://lists.gnu.org/archive/cgi-bin/namazu.cgi?query=Merging+rests+&submit=Search!&idxname=lilypond-user](http://lists.gnu.org/archive/cgi-bin/namazu.cgi?query=Merging+rests+&submit=Search!&idxname=lilypond-user) That would also be great if you could overpass the limitations, i.e. – ability to handle more than two voices ; >– handle multi-measure/whole-measure rests. Maybe the following discussion could be helpful in a certain way: [http://lists.gnu.org/archive/html/lilypond-user/2010-02/msg00452.html](http://lists.gnu.org/archive/html/lilypond-user/2010-02/msg00452.html) --- Sent from sourceforge.net because testlilyissues-a...@lists.sourceforge.net is subscribed to https://sourceforge.net/p/testlilyissues/issues/ To unsubscribe from further messages, a project admin can change settings at https://sourceforge.net/p/testlilyissues/admin/issues/options. Or, if this is a mailing list, you can unsubscribe from the mailing list.-- Check out the vibrant tech community on one of the world's most engaging tech sites, Slashdot.org! http://sdm.link/slashdot___ Testlilyissues-auto mailing list testlilyissues-a...@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/testlilyissues-auto
[Lilypond-auto] [LilyIssues-auto] [testlilyissues:issues] #5148 Various chain-assoc-get -> #:properties
- **Patch**: review --> countdown - **Comment**: Patch on countdown for June 20th --- ** [issues:#5148] Various chain-assoc-get -> #:properties** **Status:** Started **Created:** Fri Jun 16, 2017 08:55 AM UTC by David Kastrup **Last Updated:** Fri Jun 16, 2017 11:03 AM UTC **Owner:** David Kastrup Various chain-assoc-get -> #:properties Also contains commits: three-sided-box snippet: use #:properties keyword Run scripts/auxiliar/makelsr.py http://codereview.appspot.com/323940043 --- Sent from sourceforge.net because testlilyissues-a...@lists.sourceforge.net is subscribed to https://sourceforge.net/p/testlilyissues/issues/ To unsubscribe from further messages, a project admin can change settings at https://sourceforge.net/p/testlilyissues/admin/issues/options. Or, if this is a mailing list, you can unsubscribe from the mailing list.-- Check out the vibrant tech community on one of the world's most engaging tech sites, Slashdot.org! http://sdm.link/slashdot___ Testlilyissues-auto mailing list testlilyissues-a...@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/testlilyissues-auto
[Lilypond-auto] [LilyIssues-auto] [testlilyissues:issues] #5144 lilypond-manuals.css: edit color scheme and some spacing
- **labels**: --> Fixed_2_19_63 - **status**: Started --> Fixed - **Patch**: push --> --- ** [issues:#5144] lilypond-manuals.css: edit color scheme and some spacing** **Status:** Fixed **Labels:** Fixed_2_19_63 **Created:** Sat Jun 10, 2017 05:23 PM UTC by Paul Morris **Last Updated:** Sat Jun 17, 2017 04:30 PM UTC **Owner:** Paul Morris lilypond-manuals.css: edit color scheme and some spacing This patch simplifies and (IMHO) improves the color scheme and spacing of the manuals on the web. I will include a link to screenshots and a demo site, with more details on what's different. http://codereview.appspot.com/322070043 --- Sent from sourceforge.net because testlilyissues-a...@lists.sourceforge.net is subscribed to https://sourceforge.net/p/testlilyissues/issues/ To unsubscribe from further messages, a project admin can change settings at https://sourceforge.net/p/testlilyissues/admin/issues/options. Or, if this is a mailing list, you can unsubscribe from the mailing list.-- Check out the vibrant tech community on one of the world's most engaging tech sites, Slashdot.org! http://sdm.link/slashdot___ Testlilyissues-auto mailing list testlilyissues-a...@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/testlilyissues-auto
[Lilypond-auto] [LilyIssues-auto] [testlilyissues:issues] #1228 merge simultaneous rests of the same duration
- **labels**: --> Fixed_2_19_63 - **status**: Started --> Fixed - **Patch**: push --> - **Comment**: author Jay Anderson Mon, 19 Jun 2017 12:58:17 +0100 (12:58 +0100) committer James Lowe Mon, 19 Jun 2017 12:58:17 +0100 (12:58 +0100) commit 212ca268e813cd72eca8c07e714e1b6669cba747 --- ** [issues:#1228] merge simultaneous rests of the same duration** **Status:** Fixed **Labels:** Fixed_2_19_63 **Created:** Wed Aug 18, 2010 11:15 AM UTC by Anonymous **Last Updated:** Mon Jun 19, 2017 11:15 AM UTC **Owner:** horndude77 *Originally created by:* *anonymous *Originally created by:* [ralphbug...@gmail.com](http://code.google.com/u/106131861630194758622/) On 11 June 2010 16:27, Xavier Scheuer wrote: Could you implement the possibility: \override RestCollision \#'positioning-done = \#merge-rests-on-positioning described in [http://lsr.dsi.unimi.it/LSR/Item?id=336](http://lsr.dsi.unimi.it/LSR/Item?id=336) \_directly\_ into LilyPond? So we would not have to define merge-rests-on-positioning ourselves, each time we want to use this function. This function \_is useful\_, as shown by the several messages asking for this on lilypond-user: [http://lists.gnu.org/archive/cgi-bin/namazu.cgi?query=Merging+rests+&submit=Search!&idxname=lilypond-user](http://lists.gnu.org/archive/cgi-bin/namazu.cgi?query=Merging+rests+&submit=Search!&idxname=lilypond-user) That would also be great if you could overpass the limitations, i.e. – ability to handle more than two voices ; >– handle multi-measure/whole-measure rests. Maybe the following discussion could be helpful in a certain way: [http://lists.gnu.org/archive/html/lilypond-user/2010-02/msg00452.html](http://lists.gnu.org/archive/html/lilypond-user/2010-02/msg00452.html) --- Sent from sourceforge.net because testlilyissues-a...@lists.sourceforge.net is subscribed to https://sourceforge.net/p/testlilyissues/issues/ To unsubscribe from further messages, a project admin can change settings at https://sourceforge.net/p/testlilyissues/admin/issues/options. Or, if this is a mailing list, you can unsubscribe from the mailing list.-- Check out the vibrant tech community on one of the world's most engaging tech sites, Slashdot.org! http://sdm.link/slashdot___ Testlilyissues-auto mailing list testlilyissues-a...@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/testlilyissues-auto
[Lilypond-auto] [LilyIssues-auto] [testlilyissues:issues] #1388 Support OpenType font features
- **labels**: --> Fixed_2_19_63 - **status**: Started --> Fixed - **Patch**: push --> - **Comment**: I've pushed to staging. commit 8cf69a467ad7650f5ca9da6fe2dfd4c7c088b239 Issue 1388: Initial work to support opentype font features. Thank you. --- ** [issues:#1388] Support OpenType font features** **Status:** Fixed **Labels:** Fixed_2_19_63 **Created:** Mon Nov 08, 2010 10:34 PM UTC by Anonymous **Last Updated:** Mon Jun 19, 2017 11:13 AM UTC **Owner:** horndude77 *Originally created by:* *anonymous *Originally created by:* [lemzw...@googlemail.com](http://code.google.com/u/102649819178652971408/) Currently, LilyPond doesn't support OpenType font features. For example, many fonts already contain glyphs for small caps letters, but lilypond can't access such glyphs directly since OpenType fonts don't need to have named glyphs, and you need to activate an OpenType feature \(\`smcp' in this particular case\) so that input character codes get properly mapped to caps glyphs. I suggest that we implement an interface similar to the \`fontspec' package for XeTeX and luatex: [http://www.ctan.org/get/macros/xetex/latex/fontspec/fontspec.pdf](http://www.ctan.org/get/macros/xetex/latex/fontspec/fontspec.pdf) --- Sent from sourceforge.net because testlilyissues-a...@lists.sourceforge.net is subscribed to https://sourceforge.net/p/testlilyissues/issues/ To unsubscribe from further messages, a project admin can change settings at https://sourceforge.net/p/testlilyissues/admin/issues/options. Or, if this is a mailing list, you can unsubscribe from the mailing list.-- Check out the vibrant tech community on one of the world's most engaging tech sites, Slashdot.org! http://sdm.link/slashdot___ Testlilyissues-auto mailing list testlilyissues-a...@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/testlilyissues-auto
[Lilypond-auto] [LilyIssues-auto] [testlilyissues:issues] #5147 Add whether to use OTF feature depending on Pango version
- **labels**: --> Fixed_2_19_63 - **status**: Started --> Fixed - **Patch**: push --> - **Comment**: I've pushed to staging. commit f75eceb27a4b630d4e898b1d93e3b051f969ff5e Issue 5147: Add whether to use OTF feature depending on Pango version --- ** [issues:#5147] Add whether to use OTF feature depending on Pango version** **Status:** Fixed **Labels:** Fixed_2_19_63 **Created:** Tue Jun 13, 2017 12:19 PM UTC by Masamichi Hosoda **Last Updated:** Mon Jun 19, 2017 11:13 AM UTC **Owner:** Masamichi Hosoda Add whether to use OTF feature depending on Pango version Issue 1388 requires Pango 1.38+ for using OpenType font feature. However, LilyDev 4.1 has Pango 1.36.8. So it cannot compile Issue 1388. This commit makes LilyPond can be configured without OpenType font feature if Pango is old. Therefore, LilyPond become to be able to compile even by LilyDev 4.1 that has old Pango. However, the binary that compiled by LilyDev 4.1 cannot use OpenType feature. It is required Pango 1.38+ if you'd like to use the feature. This patch requires Issue 1388 https://sourceforge.net/p/testlilyissues/issues/1388/ https://codereview.appspot.com/323850043 http://codereview.appspot.com/322100043 --- Sent from sourceforge.net because testlilyissues-a...@lists.sourceforge.net is subscribed to https://sourceforge.net/p/testlilyissues/issues/ To unsubscribe from further messages, a project admin can change settings at https://sourceforge.net/p/testlilyissues/admin/issues/options. Or, if this is a mailing list, you can unsubscribe from the mailing list.-- Check out the vibrant tech community on one of the world's most engaging tech sites, Slashdot.org! http://sdm.link/slashdot___ Testlilyissues-auto mailing list testlilyissues-a...@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/testlilyissues-auto
[Lilypond-auto] [LilyIssues-auto] [testlilyissues:issues] #5150 Update Finnendahl testimony info
This is uncontroversial, and I'll push as soon as it passes the tests --- ** [issues:#5150] Update Finnendahl testimony info** **Status:** Started **Created:** Thu Jun 22, 2017 04:24 PM UTC by Urs Liska **Last Updated:** Thu Jun 22, 2017 04:24 PM UTC **Owner:** Urs Liska Update Finnendahl testimony info http://codereview.appspot.com/320690043 --- Sent from sourceforge.net because testlilyissues-a...@lists.sourceforge.net is subscribed to https://sourceforge.net/p/testlilyissues/issues/ To unsubscribe from further messages, a project admin can change settings at https://sourceforge.net/p/testlilyissues/admin/issues/options. Or, if this is a mailing list, you can unsubscribe from the mailing list.-- Check out the vibrant tech community on one of the world's most engaging tech sites, Slashdot.org! http://sdm.link/slashdot___ Testlilyissues-auto mailing list testlilyissues-a...@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/testlilyissues-auto
[Lilypond-auto] [LilyIssues-auto] [testlilyissues:issues] #5150 Update Finnendahl testimony info
--- ** [issues:#5150] Update Finnendahl testimony info** **Status:** Started **Created:** Thu Jun 22, 2017 04:24 PM UTC by Urs Liska **Last Updated:** Thu Jun 22, 2017 04:24 PM UTC **Owner:** nobody Update Finnendahl testimony info http://codereview.appspot.com/320690043 --- Sent from sourceforge.net because testlilyissues-a...@lists.sourceforge.net is subscribed to https://sourceforge.net/p/testlilyissues/issues/ To unsubscribe from further messages, a project admin can change settings at https://sourceforge.net/p/testlilyissues/admin/issues/options. Or, if this is a mailing list, you can unsubscribe from the mailing list.-- Check out the vibrant tech community on one of the world's most engaging tech sites, Slashdot.org! http://sdm.link/slashdot___ Testlilyissues-auto mailing list testlilyissues-a...@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/testlilyissues-auto
[Lilypond-auto] [LilyIssues-auto] [testlilyissues:issues] #5149 lilypond-manuals.css: Add a maximum width for manuals sidebar
- Description has changed: Diff: - **Needs**: --> - **Patch**: new --> review - **Comment**: Passes make, make check and a full make doc. --- ** [issues:#5149] lilypond-manuals.css: Add a maximum width for manuals sidebar** **Status:** Started **Created:** Sat Jun 17, 2017 09:57 PM UTC by Paul Morris **Last Updated:** Sat Jun 17, 2017 10:06 PM UTC **Owner:** Paul Morris lilypond-manuals.css: Add a maximum width for manuals sidebar When the browser window is 1280px wide or more, the sidebar will be 346px wide, rather than a percentage of the window width. Also contains these two commits: lilypond-manuals.css: A better brown for the usage manual I think this shade goes better with the other colors, giving us a more coherent color scheme across manuals. lilypond-manuals.css: Add space between top-levels in sidebar (This one was originally in my last patch for the manuals css, but I found a better way to do it, so removed it from the previous patch and including it here.) http://codereview.appspot.com/328740043 --- Sent from sourceforge.net because testlilyissues-a...@lists.sourceforge.net is subscribed to https://sourceforge.net/p/testlilyissues/issues/ To unsubscribe from further messages, a project admin can change settings at https://sourceforge.net/p/testlilyissues/admin/issues/options. Or, if this is a mailing list, you can unsubscribe from the mailing list.-- Check out the vibrant tech community on one of the world's most engaging tech sites, Slashdot.org! http://sdm.link/slashdot___ Testlilyissues-auto mailing list testlilyissues-a...@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/testlilyissues-auto
[Lilypond-auto] [LilyIssues-auto] [testlilyissues:issues] #5150 Update Finnendahl testimony info
- Description has changed: Diff: - **Needs**: --> - **Patch**: new --> review - **Comment**: Passes make, make check and a full make doc --- ** [issues:#5150] Update Finnendahl testimony info** **Status:** Started **Created:** Thu Jun 22, 2017 04:24 PM UTC by Urs Liska **Last Updated:** Thu Jun 22, 2017 04:24 PM UTC **Owner:** Urs Liska Update Finnendahl testimony info http://codereview.appspot.com/320690043 --- Sent from sourceforge.net because testlilyissues-a...@lists.sourceforge.net is subscribed to https://sourceforge.net/p/testlilyissues/issues/ To unsubscribe from further messages, a project admin can change settings at https://sourceforge.net/p/testlilyissues/admin/issues/options. Or, if this is a mailing list, you can unsubscribe from the mailing list.-- Check out the vibrant tech community on one of the world's most engaging tech sites, Slashdot.org! http://sdm.link/slashdot___ Testlilyissues-auto mailing list testlilyissues-a...@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/testlilyissues-auto
[Lilypond-auto] [LilyIssues-auto] [testlilyissues:issues] #5148 Various chain-assoc-get -> #:properties
- **Patch**: countdown --> push - **Comment**: Patch counted down - please push --- ** [issues:#5148] Various chain-assoc-get -> #:properties** **Status:** Started **Created:** Fri Jun 16, 2017 08:55 AM UTC by David Kastrup **Last Updated:** Mon Jun 19, 2017 11:16 AM UTC **Owner:** David Kastrup Various chain-assoc-get -> #:properties Also contains commits: three-sided-box snippet: use #:properties keyword Run scripts/auxiliar/makelsr.py http://codereview.appspot.com/323940043 --- Sent from sourceforge.net because testlilyissues-a...@lists.sourceforge.net is subscribed to https://sourceforge.net/p/testlilyissues/issues/ To unsubscribe from further messages, a project admin can change settings at https://sourceforge.net/p/testlilyissues/admin/issues/options. Or, if this is a mailing list, you can unsubscribe from the mailing list.-- Check out the vibrant tech community on one of the world's most engaging tech sites, Slashdot.org! http://sdm.link/slashdot___ Testlilyissues-auto mailing list testlilyissues-a...@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/testlilyissues-auto
[Lilypond-auto] [LilyIssues-auto] [testlilyissues:issues] #5148 Various chain-assoc-get -> #:properties
- **labels**: --> FIxed_2_19_63 - **status**: Started --> Fixed - **Patch**: push --> - **Comment**: ~~~ Issue 5148/1: Various chain-assoc-get -> #:properties author David Kastrup Fri, 16 Jun 2017 09:50:58 +0100 (10:50 +0200) committer David Kastrup Sun, 25 Jun 2017 11:34:08 +0100 (12:34 +0200) commit 2c894ac3f60274f9fdd0bf2593cfb856c5c7b13f ~~~ and ~~~ Issue 5148/2: three-sided-box snippet: use #:properties keyword author David Kastrup Sat, 10 Jun 2017 20:14:08 +0100 (21:14 +0200) committer David Kastrup Sun, 25 Jun 2017 11:34:08 +0100 (12:34 +0200) commit 926115ff42def8bc1ce767029e4f03c8072994ba ~~~ --- ** [issues:#5148] Various chain-assoc-get -> #:properties** **Status:** Fixed **Labels:** FIxed_2_19_63 **Created:** Fri Jun 16, 2017 08:55 AM UTC by David Kastrup **Last Updated:** Sun Jun 25, 2017 10:09 AM UTC **Owner:** David Kastrup Various chain-assoc-get -> #:properties Also contains commits: three-sided-box snippet: use #:properties keyword Run scripts/auxiliar/makelsr.py http://codereview.appspot.com/323940043 --- Sent from sourceforge.net because testlilyissues-a...@lists.sourceforge.net is subscribed to https://sourceforge.net/p/testlilyissues/issues/ To unsubscribe from further messages, a project admin can change settings at https://sourceforge.net/p/testlilyissues/admin/issues/options. Or, if this is a mailing list, you can unsubscribe from the mailing list.-- Check out the vibrant tech community on one of the world's most engaging tech sites, Slashdot.org! http://sdm.link/slashdot___ Testlilyissues-auto mailing list testlilyissues-a...@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/testlilyissues-auto
[Lilypond-auto] [LilyIssues-auto] [testlilyissues:issues] #5149 lilypond-manuals.css: Add a maximum width for manuals sidebar
- **Patch**: review --> countdown - **Comment**: Patch on countdown for July 1st --- ** [issues:#5149] lilypond-manuals.css: Add a maximum width for manuals sidebar** **Status:** Started **Created:** Sat Jun 17, 2017 09:57 PM UTC by Paul Morris **Last Updated:** Sun Jun 25, 2017 09:31 AM UTC **Owner:** Paul Morris lilypond-manuals.css: Add a maximum width for manuals sidebar When the browser window is 1280px wide or more, the sidebar will be 346px wide, rather than a percentage of the window width. Also contains these two commits: lilypond-manuals.css: A better brown for the usage manual I think this shade goes better with the other colors, giving us a more coherent color scheme across manuals. lilypond-manuals.css: Add space between top-levels in sidebar (This one was originally in my last patch for the manuals css, but I found a better way to do it, so removed it from the previous patch and including it here.) http://codereview.appspot.com/328740043 --- Sent from sourceforge.net because testlilyissues-a...@lists.sourceforge.net is subscribed to https://sourceforge.net/p/testlilyissues/issues/ To unsubscribe from further messages, a project admin can change settings at https://sourceforge.net/p/testlilyissues/admin/issues/options. Or, if this is a mailing list, you can unsubscribe from the mailing list.-- Check out the vibrant tech community on one of the world's most engaging tech sites, Slashdot.org! http://sdm.link/slashdot___ Testlilyissues-auto mailing list testlilyissues-a...@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/testlilyissues-auto
[Lilypond-auto] [LilyIssues-auto] [testlilyissues:issues] #5150 Update Finnendahl testimony info
- **Patch**: review --> countdown - **Comment**: Patch on countdown for July 1st --- ** [issues:#5150] Update Finnendahl testimony info** **Status:** Started **Created:** Thu Jun 22, 2017 04:24 PM UTC by Urs Liska **Last Updated:** Sun Jun 25, 2017 10:09 AM UTC **Owner:** Urs Liska Update Finnendahl testimony info http://codereview.appspot.com/320690043 --- Sent from sourceforge.net because testlilyissues-a...@lists.sourceforge.net is subscribed to https://sourceforge.net/p/testlilyissues/issues/ To unsubscribe from further messages, a project admin can change settings at https://sourceforge.net/p/testlilyissues/admin/issues/options. Or, if this is a mailing list, you can unsubscribe from the mailing list.-- Check out the vibrant tech community on one of the world's most engaging tech sites, Slashdot.org! http://sdm.link/slashdot___ Testlilyissues-auto mailing list testlilyissues-a...@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/testlilyissues-auto
[Lilypond-auto] [LilyIssues-auto] [testlilyissues:issues] #5150 Update Finnendahl testimony info
- **labels**: --> Fixed_2_19_63 - **status**: Started --> Fixed - **Comment**: Pushed to staging as ``` commit f0887364f183175facfde169447845a2390a6ed2 Author: Urs Liska Date: Thu Jun 22 18:23:13 2017 +0200 #5150: Update Finnendahl testimony info ``` --- ** [issues:#5150] Update Finnendahl testimony info** **Status:** Fixed **Labels:** Fixed_2_19_63 **Created:** Thu Jun 22, 2017 04:24 PM UTC by Urs Liska **Last Updated:** Wed Jun 28, 2017 07:15 AM UTC **Owner:** Urs Liska Update Finnendahl testimony info http://codereview.appspot.com/320690043 --- Sent from sourceforge.net because testlilyissues-a...@lists.sourceforge.net is subscribed to https://sourceforge.net/p/testlilyissues/issues/ To unsubscribe from further messages, a project admin can change settings at https://sourceforge.net/p/testlilyissues/admin/issues/options. Or, if this is a mailing list, you can unsubscribe from the mailing list.-- Check out the vibrant tech community on one of the world's most engaging tech sites, Slashdot.org! http://sdm.link/slashdot___ Testlilyissues-auto mailing list testlilyissues-a...@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/testlilyissues-auto
[Lilypond-auto] [LilyIssues-auto] [testlilyissues:issues] #5151 midi2ly on mac: midi.so wrong architecture
--- ** [issues:#5151] midi2ly on mac: midi.so wrong architecture** **Status:** New **Created:** Fri Jun 30, 2017 04:27 AM UTC by David Elaine Alt **Last Updated:** Fri Jun 30, 2017 04:27 AM UTC **Owner:** nobody When a try a midi2ly, I get this: File "/Applications/LilyPond.app/Contents/Resources/bin/midi2ly", line 54, in import midi ImportError: dlopen(/Applications/LilyPond.app/Contents/Resources/lib/lilypond/current/python/midi.so, 2): no suitable image found. Did find: /Applications/LilyPond.app/Contents/Resources/lib/lilypond/current/python/midi.so: mach-o, but wrong architecture /Applications/LilyPond.app/Contents/Resources/lib/lilypond/current/python/midi.so: mach-o, but wrong architecture Confirmed problem on OSX 10.11.6, OSX 10.9.5 and OSX 10.11.5. --- Sent from sourceforge.net because testlilyissues-a...@lists.sourceforge.net is subscribed to https://sourceforge.net/p/testlilyissues/issues/ To unsubscribe from further messages, a project admin can change settings at https://sourceforge.net/p/testlilyissues/admin/issues/options. Or, if this is a mailing list, you can unsubscribe from the mailing list.-- Check out the vibrant tech community on one of the world's most engaging tech sites, Slashdot.org! http://sdm.link/slashdot___ Testlilyissues-auto mailing list testlilyissues-a...@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/testlilyissues-auto
[Lilypond-auto] [LilyIssues-auto] [testlilyissues:issues] #5151 midi2ly on mac: midi.so wrong architecture
- **status**: New --> Duplicate - **assigned_to**: David Kastrup - **Comment**: Duplicate of issue #2208. I was vaguely aware that Graham had worked on it and submitted a patch replacing the midi.so module with Python code? What happened with that? --- ** [issues:#5151] midi2ly on mac: midi.so wrong architecture** **Status:** Duplicate **Created:** Fri Jun 30, 2017 04:27 AM UTC by David Elaine Alt **Last Updated:** Fri Jun 30, 2017 04:27 AM UTC **Owner:** David Kastrup When a try a midi2ly, I get this: File "/Applications/LilyPond.app/Contents/Resources/bin/midi2ly", line 54, in import midi ImportError: dlopen(/Applications/LilyPond.app/Contents/Resources/lib/lilypond/current/python/midi.so, 2): no suitable image found. Did find: /Applications/LilyPond.app/Contents/Resources/lib/lilypond/current/python/midi.so: mach-o, but wrong architecture /Applications/LilyPond.app/Contents/Resources/lib/lilypond/current/python/midi.so: mach-o, but wrong architecture Confirmed problem on OSX 10.11.6, OSX 10.9.5 and OSX 10.11.5. --- Sent from sourceforge.net because testlilyissues-a...@lists.sourceforge.net is subscribed to https://sourceforge.net/p/testlilyissues/issues/ To unsubscribe from further messages, a project admin can change settings at https://sourceforge.net/p/testlilyissues/admin/issues/options. Or, if this is a mailing list, you can unsubscribe from the mailing list.-- Check out the vibrant tech community on one of the world's most engaging tech sites, Slashdot.org! http://sdm.link/slashdot___ Testlilyissues-auto mailing list testlilyissues-a...@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/testlilyissues-auto
[Lilypond-auto] [LilyIssues-auto] [testlilyissues:issues] #5149 lilypond-manuals.css: Add a maximum width for manuals sidebar
- **Patch**: countdown --> push - **Comment**: Patch counted down - please push. --- ** [issues:#5149] lilypond-manuals.css: Add a maximum width for manuals sidebar** **Status:** Started **Created:** Sat Jun 17, 2017 09:57 PM UTC by Paul Morris **Last Updated:** Wed Jun 28, 2017 07:15 AM UTC **Owner:** Paul Morris lilypond-manuals.css: Add a maximum width for manuals sidebar When the browser window is 1280px wide or more, the sidebar will be 346px wide, rather than a percentage of the window width. Also contains these two commits: lilypond-manuals.css: A better brown for the usage manual I think this shade goes better with the other colors, giving us a more coherent color scheme across manuals. lilypond-manuals.css: Add space between top-levels in sidebar (This one was originally in my last patch for the manuals css, but I found a better way to do it, so removed it from the previous patch and including it here.) http://codereview.appspot.com/328740043 --- Sent from sourceforge.net because testlilyissues-a...@lists.sourceforge.net is subscribed to https://sourceforge.net/p/testlilyissues/issues/ To unsubscribe from further messages, a project admin can change settings at https://sourceforge.net/p/testlilyissues/admin/issues/options. Or, if this is a mailing list, you can unsubscribe from the mailing list.-- Check out the vibrant tech community on one of the world's most engaging tech sites, Slashdot.org! http://sdm.link/slashdot___ Testlilyissues-auto mailing list testlilyissues-a...@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/testlilyissues-auto
[Lilypond-auto] [LilyIssues-auto] [testlilyissues:issues] #5149 lilypond-manuals.css: Add a maximum width for manuals sidebar
- **labels**: --> Fixed_2_19_64 - **status**: Started --> Fixed - **Patch**: push --> --- ** [issues:#5149] lilypond-manuals.css: Add a maximum width for manuals sidebar** **Status:** Fixed **Labels:** Fixed_2_19_64 **Created:** Sat Jun 17, 2017 09:57 PM UTC by Paul Morris **Last Updated:** Sat Jul 01, 2017 09:16 AM UTC **Owner:** Paul Morris lilypond-manuals.css: Add a maximum width for manuals sidebar When the browser window is 1280px wide or more, the sidebar will be 346px wide, rather than a percentage of the window width. Also contains these two commits: lilypond-manuals.css: A better brown for the usage manual I think this shade goes better with the other colors, giving us a more coherent color scheme across manuals. lilypond-manuals.css: Add space between top-levels in sidebar (This one was originally in my last patch for the manuals css, but I found a better way to do it, so removed it from the previous patch and including it here.) http://codereview.appspot.com/328740043 --- Sent from sourceforge.net because testlilyissues-a...@lists.sourceforge.net is subscribed to https://sourceforge.net/p/testlilyissues/issues/ To unsubscribe from further messages, a project admin can change settings at https://sourceforge.net/p/testlilyissues/admin/issues/options. Or, if this is a mailing list, you can unsubscribe from the mailing list.-- Check out the vibrant tech community on one of the world's most engaging tech sites, Slashdot.org! http://sdm.link/slashdot___ Testlilyissues-auto mailing list testlilyissues-a...@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/testlilyissues-auto
[Lilypond-auto] [LilyIssues-auto] [testlilyissues:issues] #5149 lilypond-manuals.css: Add a maximum width for manuals sidebar
Pushed to staging as: commit 77267b700c377fd170abcbf4863728937038eb5e Author: Paul Morris Date: Sat Jun 17 17:44:16 2017 -0400 Doc: CSS: Add a maximum width for the sidebar in the manuals commit 750b714488c5af6eae22d07163bba8b554734ac6 Author: Paul Morris Date: Sat Jun 17 17:43:11 2017 -0400 Doc: CSS: A better brown for the usage manual commit 149f0cddc0bad45dd8c1822195b0352fdc6912b5 Author: Paul Morris Date: Sat Jun 17 15:40:57 2017 -0400 Doc: CSS: Add space between top-levels in sidebar --- ** [issues:#5149] lilypond-manuals.css: Add a maximum width for manuals sidebar** **Status:** Fixed **Labels:** Fixed_2_19_64 **Created:** Sat Jun 17, 2017 09:57 PM UTC by Paul Morris **Last Updated:** Sat Jul 01, 2017 02:50 PM UTC **Owner:** Paul Morris lilypond-manuals.css: Add a maximum width for manuals sidebar When the browser window is 1280px wide or more, the sidebar will be 346px wide, rather than a percentage of the window width. Also contains these two commits: lilypond-manuals.css: A better brown for the usage manual I think this shade goes better with the other colors, giving us a more coherent color scheme across manuals. lilypond-manuals.css: Add space between top-levels in sidebar (This one was originally in my last patch for the manuals css, but I found a better way to do it, so removed it from the previous patch and including it here.) http://codereview.appspot.com/328740043 --- Sent from sourceforge.net because testlilyissues-a...@lists.sourceforge.net is subscribed to https://sourceforge.net/p/testlilyissues/issues/ To unsubscribe from further messages, a project admin can change settings at https://sourceforge.net/p/testlilyissues/admin/issues/options. Or, if this is a mailing list, you can unsubscribe from the mailing list.-- Check out the vibrant tech community on one of the world's most engaging tech sites, Slashdot.org! http://sdm.link/slashdot___ Testlilyissues-auto mailing list testlilyissues-a...@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/testlilyissues-auto
[Lilypond-auto] [LilyIssues-auto] [testlilyissues:issues] #5152 Doc: CG: Add guideline for use of 'CSS' prefix in commit messages
--- ** [issues:#5152] Doc: CG: Add guideline for use of 'CSS' prefix in commit messages** **Status:** Started **Created:** Tue Jul 04, 2017 07:22 PM UTC by Paul Morris **Last Updated:** Tue Jul 04, 2017 07:22 PM UTC **Owner:** nobody Doc: CG: Add guideline for use of 'CSS' prefix in commit messages http://codereview.appspot.com/325970043 --- Sent from sourceforge.net because testlilyissues-a...@lists.sourceforge.net is subscribed to https://sourceforge.net/p/testlilyissues/issues/ To unsubscribe from further messages, a project admin can change settings at https://sourceforge.net/p/testlilyissues/admin/issues/options. Or, if this is a mailing list, you can unsubscribe from the mailing list.-- Check out the vibrant tech community on one of the world's most engaging tech sites, Slashdot.org! http://sdm.link/slashdot___ Testlilyissues-auto mailing list testlilyissues-a...@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/testlilyissues-auto
[Lilypond-auto] [LilyIssues-auto] [testlilyissues:issues] #5152 Doc: CG: Add guideline for use of 'CSS' prefix in commit messages
- Description has changed: Diff: - **Needs**: --> - **Patch**: new --> review --- ** [issues:#5152] Doc: CG: Add guideline for use of 'CSS' prefix in commit messages** **Status:** Started **Created:** Tue Jul 04, 2017 07:22 PM UTC by Paul Morris **Last Updated:** Wed Jul 05, 2017 09:56 AM UTC **Owner:** Paul Morris Doc: CG: Add guideline for use of 'CSS' prefix in commit messages http://codereview.appspot.com/325970043 --- Sent from sourceforge.net because testlilyissues-a...@lists.sourceforge.net is subscribed to https://sourceforge.net/p/testlilyissues/issues/ To unsubscribe from further messages, a project admin can change settings at https://sourceforge.net/p/testlilyissues/admin/issues/options. Or, if this is a mailing list, you can unsubscribe from the mailing list.-- Check out the vibrant tech community on one of the world's most engaging tech sites, Slashdot.org! http://sdm.link/slashdot___ Testlilyissues-auto mailing list testlilyissues-a...@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/testlilyissues-auto
[Lilypond-auto] [LilyIssues-auto] [testlilyissues:issues] #5152 Doc: CG: Add guideline for use of 'CSS' prefix in commit messages
Passes make, make check and a full make doc. I'd have no problem with you pushing this immediately. --- ** [issues:#5152] Doc: CG: Add guideline for use of 'CSS' prefix in commit messages** **Status:** Started **Created:** Tue Jul 04, 2017 07:22 PM UTC by Paul Morris **Last Updated:** Tue Jul 04, 2017 07:22 PM UTC **Owner:** Paul Morris Doc: CG: Add guideline for use of 'CSS' prefix in commit messages http://codereview.appspot.com/325970043 --- Sent from sourceforge.net because testlilyissues-a...@lists.sourceforge.net is subscribed to https://sourceforge.net/p/testlilyissues/issues/ To unsubscribe from further messages, a project admin can change settings at https://sourceforge.net/p/testlilyissues/admin/issues/options. Or, if this is a mailing list, you can unsubscribe from the mailing list.-- Check out the vibrant tech community on one of the world's most engaging tech sites, Slashdot.org! http://sdm.link/slashdot___ Testlilyissues-auto mailing list testlilyissues-a...@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/testlilyissues-auto
[Lilypond-auto] [LilyIssues-auto] [testlilyissues:issues] #5152 Doc: CG: Add guideline for use of 'CSS' prefix in commit messages
This looks like it should still be on review. --- ** [issues:#5152] Doc: CG: Add guideline for use of 'CSS' prefix in commit messages** **Status:** Started **Created:** Tue Jul 04, 2017 07:22 PM UTC by Paul Morris **Last Updated:** Wed Jul 05, 2017 09:56 AM UTC **Owner:** Paul Morris Doc: CG: Add guideline for use of 'CSS' prefix in commit messages http://codereview.appspot.com/325970043 --- Sent from sourceforge.net because testlilyissues-a...@lists.sourceforge.net is subscribed to https://sourceforge.net/p/testlilyissues/issues/ To unsubscribe from further messages, a project admin can change settings at https://sourceforge.net/p/testlilyissues/admin/issues/options. Or, if this is a mailing list, you can unsubscribe from the mailing list.-- Check out the vibrant tech community on one of the world's most engaging tech sites, Slashdot.org! http://sdm.link/slashdot___ Testlilyissues-auto mailing list testlilyissues-a...@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/testlilyissues-auto
[Lilypond-auto] [LilyIssues-auto] [testlilyissues:issues] #5153 Implementing Chord Semantics as a part of the EventChord structure
--- ** [issues:#5153] Implementing Chord Semantics as a part of the EventChord structure** **Status:** Started **Created:** Sat Jul 08, 2017 11:32 AM UTC by pkx166h **Last Updated:** Sat Jul 08, 2017 11:32 AM UTC **Owner:** Charles Winston Implementing Chord Semantics as a part of the EventChord structure, and using semantics to create a chord name with the Chord Name Engraver https://codereview.appspot.com/321250043 --- Sent from sourceforge.net because testlilyissues-a...@lists.sourceforge.net is subscribed to https://sourceforge.net/p/testlilyissues/issues/ To unsubscribe from further messages, a project admin can change settings at https://sourceforge.net/p/testlilyissues/admin/issues/options. Or, if this is a mailing list, you can unsubscribe from the mailing list.-- Check out the vibrant tech community on one of the world's most engaging tech sites, Slashdot.org! http://sdm.link/slashdot___ Testlilyissues-auto mailing list testlilyissues-a...@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/testlilyissues-auto
[Lilypond-auto] [LilyIssues-auto] [testlilyissues:issues] #5153 Implementing Chord Semantics as a part of the EventChord structure
- **Patch**: new --> needs_work - **Comment**: Passes make but fails the regression tests. Specifically (as far as I can tell): chord-name-minor.ly ~~~ warning: cannot find property type-check for `chord-step' (music-type?). perhap s a typing error? Writing timing to 56/lily-44b4b5eb.profile... programming error: Parsed object should be dead: #) > continuing, cross fingers ~~~ fret-diagrams-capo.ly (same error as above) partial-in-mid-piece.ly (same error as above) etc. There are nother 6 or 7 reg tests that fail but I am guessing they are failing with the same error. Charles, just in case you are not familiar with the patch test process, see: http://lilypond.org/doc/v2.19/Documentation/contributor-big-page.html#regression-tests This means that I haven't tested a make doc either, but until it passes the reg tests, that is moot (in the American sense of the word). Thanks. Setting this tracker to needs_work. --- ** [issues:#5153] Implementing Chord Semantics as a part of the EventChord structure** **Status:** Started **Created:** Sat Jul 08, 2017 11:32 AM UTC by pkx166h **Last Updated:** Sat Jul 08, 2017 11:32 AM UTC **Owner:** Charles Winston Implementing Chord Semantics as a part of the EventChord structure, and using semantics to create a chord name with the Chord Name Engraver https://codereview.appspot.com/321250043 --- Sent from sourceforge.net because testlilyissues-a...@lists.sourceforge.net is subscribed to https://sourceforge.net/p/testlilyissues/issues/ To unsubscribe from further messages, a project admin can change settings at https://sourceforge.net/p/testlilyissues/admin/issues/options. Or, if this is a mailing list, you can unsubscribe from the mailing list.-- Check out the vibrant tech community on one of the world's most engaging tech sites, Slashdot.org! http://sdm.link/slashdot___ Testlilyissues-auto mailing list testlilyissues-a...@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/testlilyissues-auto
[Lilypond-auto] [LilyIssues-auto] [testlilyissues:issues] #5152 Doc: CG: Add guideline for use of 'CSS' prefix in commit messages
Don't mention a 'both' case http://codereview.appspot.com/325970043 --- ** [issues:#5152] Doc: CG: Add guideline for use of 'CSS' prefix in commit messages** **Status:** Started **Created:** Tue Jul 04, 2017 07:22 PM UTC by Paul Morris **Last Updated:** Sat Jul 08, 2017 09:26 PM UTC **Owner:** Paul Morris Doc: CG: Add guideline for use of 'CSS' prefix in commit messages http://codereview.appspot.com/325970043 --- Sent from sourceforge.net because testlilyissues-a...@lists.sourceforge.net is subscribed to https://sourceforge.net/p/testlilyissues/issues/ To unsubscribe from further messages, a project admin can change settings at https://sourceforge.net/p/testlilyissues/admin/issues/options. Or, if this is a mailing list, you can unsubscribe from the mailing list.-- Check out the vibrant tech community on one of the world's most engaging tech sites, Slashdot.org! http://sdm.link/slashdot___ Testlilyissues-auto mailing list testlilyissues-a...@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/testlilyissues-auto
[Lilypond-auto] [LilyIssues-auto] [testlilyissues:issues] #4603 change all occurences of ‘partcombine’ to ‘partCombine’.
- Description has changed: Diff: --- old +++ new @@ -19,3 +19,7 @@ > > Cheers, > Malte + +Response to Issue #4603: Syntax change from all instances "partcombine" to "partCombine" and convert-ly rule added to go along with. + +http://codereview.appspot.com/323040043 - part 1 of 3 - **Patch**: needs_work --> new - **Comment**: I have made the relevant Doc and Reg test edits to make this initial patch pass the tests. I'll upload the two other patches (split into a Doc & snippet patch and a Reg test patch) --- ** [issues:#4603] change all occurences of ‘partcombine’ to ‘partCombine’.** **Status:** Started **Created:** Sun Sep 13, 2015 03:17 PM UTC by pkx166h **Last Updated:** Fri Jun 02, 2017 06:47 AM UTC **Owner:** Charles Winston On 13/08/15 21:42, Malte Meyn wrote: > Hi list, > > the case of the ‘c’ in partcombine is inconsistent, confusing me every > time I use \partcombine(Apart|Chords|…): > > \partcombine, \partcombineApart, … but > \partCombineTextsOnNote, \partCombineListener > > I would suggest to change all occurences of ‘partcombine’ to ‘partCombine’. > > Why not change ‘partCombine’ to ‘partcombine’? Because I looked at the > engravers which use the more ‘natural’ underscore instead of camelCase > for spaces. And in the same way as ‘Cue_clef_engraver’ suggests that > ‘cue clef’ are two words (resulting in ‘cueClefGlyph’, not > ‘cueclefGlyph’), ‘Part_combine_engraver’ does. > > I think that this would be rather easy to change. > > Cheers, > Malte Response to Issue #4603: Syntax change from all instances "partcombine" to "partCombine" and convert-ly rule added to go along with. http://codereview.appspot.com/323040043 - part 1 of 3 --- Sent from sourceforge.net because testlilyissues-a...@lists.sourceforge.net is subscribed to https://sourceforge.net/p/testlilyissues/issues/ To unsubscribe from further messages, a project admin can change settings at https://sourceforge.net/p/testlilyissues/admin/issues/options. Or, if this is a mailing list, you can unsubscribe from the mailing list.-- Check out the vibrant tech community on one of the world's most engaging tech sites, Slashdot.org! http://sdm.link/slashdot___ Testlilyissues-auto mailing list testlilyissues-a...@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/testlilyissues-auto
[Lilypond-auto] [LilyIssues-auto] [testlilyissues:issues] #4603 change all occurences of ‘partcombine’ to ‘partCombine’.
Change all instances of \partcombine to \partCombine in the documentation Issue 4603 (2 of 3) All instances of \partcombine in ../Documentation (including translated and snippets) have been changed to \partCombine. http://codereview.appspot.com/326870043 --- ** [issues:#4603] change all occurences of ‘partcombine’ to ‘partCombine’.** **Status:** Started **Created:** Sun Sep 13, 2015 03:17 PM UTC by pkx166h **Last Updated:** Mon Jul 10, 2017 10:19 AM UTC **Owner:** Charles Winston On 13/08/15 21:42, Malte Meyn wrote: > Hi list, > > the case of the ‘c’ in partcombine is inconsistent, confusing me every > time I use \partcombine(Apart|Chords|…): > > \partcombine, \partcombineApart, … but > \partCombineTextsOnNote, \partCombineListener > > I would suggest to change all occurences of ‘partcombine’ to ‘partCombine’. > > Why not change ‘partCombine’ to ‘partcombine’? Because I looked at the > engravers which use the more ‘natural’ underscore instead of camelCase > for spaces. And in the same way as ‘Cue_clef_engraver’ suggests that > ‘cue clef’ are two words (resulting in ‘cueClefGlyph’, not > ‘cueclefGlyph’), ‘Part_combine_engraver’ does. > > I think that this would be rather easy to change. > > Cheers, > Malte Response to Issue #4603: Syntax change from all instances "partcombine" to "partCombine" and convert-ly rule added to go along with. http://codereview.appspot.com/323040043 - part 1 of 3 --- Sent from sourceforge.net because testlilyissues-a...@lists.sourceforge.net is subscribed to https://sourceforge.net/p/testlilyissues/issues/ To unsubscribe from further messages, a project admin can change settings at https://sourceforge.net/p/testlilyissues/admin/issues/options. Or, if this is a mailing list, you can unsubscribe from the mailing list.-- Check out the vibrant tech community on one of the world's most engaging tech sites, Slashdot.org! http://sdm.link/slashdot___ Testlilyissues-auto mailing list testlilyissues-a...@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/testlilyissues-auto
[Lilypond-auto] [LilyIssues-auto] [testlilyissues:issues] #4603 change all occurences of ‘partcombine’ to ‘partCombine’.
Change all instances of \partcombine to \partCombine in the reg tests Issue 4603 (3 of 3) All instances of \partcombine in ../input/regression/ have been changed to \partCombine. http://codereview.appspot.com/327970043 --- ** [issues:#4603] change all occurences of ‘partcombine’ to ‘partCombine’.** **Status:** Started **Created:** Sun Sep 13, 2015 03:17 PM UTC by pkx166h **Last Updated:** Mon Jul 10, 2017 10:24 AM UTC **Owner:** Charles Winston On 13/08/15 21:42, Malte Meyn wrote: > Hi list, > > the case of the ‘c’ in partcombine is inconsistent, confusing me every > time I use \partcombine(Apart|Chords|…): > > \partcombine, \partcombineApart, … but > \partCombineTextsOnNote, \partCombineListener > > I would suggest to change all occurences of ‘partcombine’ to ‘partCombine’. > > Why not change ‘partCombine’ to ‘partcombine’? Because I looked at the > engravers which use the more ‘natural’ underscore instead of camelCase > for spaces. And in the same way as ‘Cue_clef_engraver’ suggests that > ‘cue clef’ are two words (resulting in ‘cueClefGlyph’, not > ‘cueclefGlyph’), ‘Part_combine_engraver’ does. > > I think that this would be rather easy to change. > > Cheers, > Malte Response to Issue #4603: Syntax change from all instances "partcombine" to "partCombine" and convert-ly rule added to go along with. http://codereview.appspot.com/323040043 - part 1 of 3 --- Sent from sourceforge.net because testlilyissues-a...@lists.sourceforge.net is subscribed to https://sourceforge.net/p/testlilyissues/issues/ To unsubscribe from further messages, a project admin can change settings at https://sourceforge.net/p/testlilyissues/admin/issues/options. Or, if this is a mailing list, you can unsubscribe from the mailing list.-- Check out the vibrant tech community on one of the world's most engaging tech sites, Slashdot.org! http://sdm.link/slashdot___ Testlilyissues-auto mailing list testlilyissues-a...@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/testlilyissues-auto
[Lilypond-auto] [LilyIssues-auto] [testlilyissues:issues] #4603 change all occurences of ‘partcombine’ to ‘partCombine’.
- Description has changed: Diff: --- old +++ new @@ -23,3 +23,6 @@ Response to Issue #4603: Syntax change from all instances "partcombine" to "partCombine" and convert-ly rule added to go along with. http://codereview.appspot.com/323040043 - part 1 of 3 + +http://codereview.appspot.com/326870043 - part 2 of 3 + - **Needs**: --> - **Type**: --> --- ** [issues:#4603] change all occurences of ‘partcombine’ to ‘partCombine’.** **Status:** Started **Created:** Sun Sep 13, 2015 03:17 PM UTC by pkx166h **Last Updated:** Mon Jul 10, 2017 10:24 AM UTC **Owner:** Charles Winston On 13/08/15 21:42, Malte Meyn wrote: > Hi list, > > the case of the ‘c’ in partcombine is inconsistent, confusing me every > time I use \partcombine(Apart|Chords|…): > > \partcombine, \partcombineApart, … but > \partCombineTextsOnNote, \partCombineListener > > I would suggest to change all occurences of ‘partcombine’ to ‘partCombine’. > > Why not change ‘partCombine’ to ‘partcombine’? Because I looked at the > engravers which use the more ‘natural’ underscore instead of camelCase > for spaces. And in the same way as ‘Cue_clef_engraver’ suggests that > ‘cue clef’ are two words (resulting in ‘cueClefGlyph’, not > ‘cueclefGlyph’), ‘Part_combine_engraver’ does. > > I think that this would be rather easy to change. > > Cheers, > Malte Response to Issue #4603: Syntax change from all instances "partcombine" to "partCombine" and convert-ly rule added to go along with. http://codereview.appspot.com/323040043 - part 1 of 3 http://codereview.appspot.com/326870043 - part 2 of 3 --- Sent from sourceforge.net because testlilyissues-a...@lists.sourceforge.net is subscribed to https://sourceforge.net/p/testlilyissues/issues/ To unsubscribe from further messages, a project admin can change settings at https://sourceforge.net/p/testlilyissues/admin/issues/options. Or, if this is a mailing list, you can unsubscribe from the mailing list.-- Check out the vibrant tech community on one of the world's most engaging tech sites, Slashdot.org! http://sdm.link/slashdot___ Testlilyissues-auto mailing list testlilyissues-a...@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/testlilyissues-auto
[Lilypond-auto] [LilyIssues-auto] [testlilyissues:issues] #4603 change all occurences of ‘partcombine’ to ‘partCombine’.
- Description has changed: Diff: --- old +++ new @@ -26,3 +26,7 @@ http://codereview.appspot.com/326870043 - part 2 of 3 +http://codereview.appspot.com/327970043 - part 3 of 3 + +Note this will require both a convert.ly and a makelsr.py run to make sure that the patch passes all the tests. + --- ** [issues:#4603] change all occurences of ‘partcombine’ to ‘partCombine’.** **Status:** Started **Created:** Sun Sep 13, 2015 03:17 PM UTC by pkx166h **Last Updated:** Mon Jul 10, 2017 10:25 AM UTC **Owner:** Charles Winston On 13/08/15 21:42, Malte Meyn wrote: > Hi list, > > the case of the ‘c’ in partcombine is inconsistent, confusing me every > time I use \partcombine(Apart|Chords|…): > > \partcombine, \partcombineApart, … but > \partCombineTextsOnNote, \partCombineListener > > I would suggest to change all occurences of ‘partcombine’ to ‘partCombine’. > > Why not change ‘partCombine’ to ‘partcombine’? Because I looked at the > engravers which use the more ‘natural’ underscore instead of camelCase > for spaces. And in the same way as ‘Cue_clef_engraver’ suggests that > ‘cue clef’ are two words (resulting in ‘cueClefGlyph’, not > ‘cueclefGlyph’), ‘Part_combine_engraver’ does. > > I think that this would be rather easy to change. > > Cheers, > Malte Response to Issue #4603: Syntax change from all instances "partcombine" to "partCombine" and convert-ly rule added to go along with. http://codereview.appspot.com/323040043 - part 1 of 3 http://codereview.appspot.com/326870043 - part 2 of 3 http://codereview.appspot.com/327970043 - part 3 of 3 Note this will require both a convert.ly and a makelsr.py run to make sure that the patch passes all the tests. --- Sent from sourceforge.net because testlilyissues-a...@lists.sourceforge.net is subscribed to https://sourceforge.net/p/testlilyissues/issues/ To unsubscribe from further messages, a project admin can change settings at https://sourceforge.net/p/testlilyissues/admin/issues/options. Or, if this is a mailing list, you can unsubscribe from the mailing list.-- Check out the vibrant tech community on one of the world's most engaging tech sites, Slashdot.org! http://sdm.link/slashdot___ Testlilyissues-auto mailing list testlilyissues-a...@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/testlilyissues-auto
[Lilypond-auto] [LilyIssues-auto] [testlilyissues:issues] #4603 change all occurences of ‘partcombine’ to ‘partCombine’.
Ok, this is really really late but I've taken a look at the output of git grep '[pP]artCombine' in the current code base and changing those occurences to `partcombine` would be way less effort than the other way round: basically most of them are new. I might be predisposed by lots of exposure to previous code though. The oldest ones to be changed would be `partcombineListener` (output definitions are not capitalized?), `PartcombineMusic`, `PartcombinePartMusic`, `printPartcombineTexts`. I am slightly leaning to that change but it would also have to result in `Partcombine_engraver`, `Partcombine_iterator`, `Partcombine_part_iterator` to be consistent. Basically making partcombining one word (wouldn't separate words be rather "combine parts"? The correct spelling of partcombiner would likely be "the part-combiner". Huh). However that may be: having a large discrepancy without backward compatibility between 2.18 and 2.20 seems like a bad idea since LSR and online help will bomb a lot. We have seen this effect with various backward-compatible but compelling changes in the past: having this in a non-backward-compatible way seems like a bad idea that will cause a whole lot of medium-term pain for little long-term gain. So I think it would be reasonable to a) postpone any such changes to 2.21. Since we currently are at a good time to fork off the 2.20 release branch anyway, that does not need to imply a large delay. b) develop a mechanism for backward compatibility. Reasonably easy for commands, trickier for properties and engravers. Point b) should be tackled rather fast though, preferably within a reasonable time frame of a), perhaps even before if possible. Depends on how fast we can come up with ideas for making this work. --- ** [issues:#4603] change all occurences of ‘partcombine’ to ‘partCombine’.** **Status:** Started **Created:** Sun Sep 13, 2015 03:17 PM UTC by pkx166h **Last Updated:** Mon Jul 10, 2017 10:26 AM UTC **Owner:** Charles Winston On 13/08/15 21:42, Malte Meyn wrote: > Hi list, > > the case of the ‘c’ in partcombine is inconsistent, confusing me every > time I use \partcombine(Apart|Chords|…): > > \partcombine, \partcombineApart, … but > \partCombineTextsOnNote, \partCombineListener > > I would suggest to change all occurences of ‘partcombine’ to ‘partCombine’. > > Why not change ‘partCombine’ to ‘partcombine’? Because I looked at the > engravers which use the more ‘natural’ underscore instead of camelCase > for spaces. And in the same way as ‘Cue_clef_engraver’ suggests that > ‘cue clef’ are two words (resulting in ‘cueClefGlyph’, not > ‘cueclefGlyph’), ‘Part_combine_engraver’ does. > > I think that this would be rather easy to change. > > Cheers, > Malte Response to Issue #4603: Syntax change from all instances "partcombine" to "partCombine" and convert-ly rule added to go along with. http://codereview.appspot.com/323040043 - part 1 of 3 http://codereview.appspot.com/326870043 - part 2 of 3 http://codereview.appspot.com/327970043 - part 3 of 3 Note this will require both a convert.ly and a makelsr.py run to make sure that the patch passes all the tests. --- Sent from sourceforge.net because testlilyissues-a...@lists.sourceforge.net is subscribed to https://sourceforge.net/p/testlilyissues/issues/ To unsubscribe from further messages, a project admin can change settings at https://sourceforge.net/p/testlilyissues/admin/issues/options. Or, if this is a mailing list, you can unsubscribe from the mailing list.-- Check out the vibrant tech community on one of the world's most engaging tech sites, Slashdot.org! http://sdm.link/slashdot___ Testlilyissues-auto mailing list testlilyissues-a...@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/testlilyissues-auto
[Lilypond-auto] [LilyIssues-auto] [testlilyissues:issues] #5152 Doc: CG: Add guideline for use of 'CSS' prefix in commit messages
- **Needs**: --> - **Patch**: new --> review - **Type**: --> Documentation - **Comment**: Passes make, make check and a full make doc. --- ** [issues:#5152] Doc: CG: Add guideline for use of 'CSS' prefix in commit messages** **Status:** Started **Created:** Tue Jul 04, 2017 07:22 PM UTC by Paul Morris **Last Updated:** Sat Jul 08, 2017 09:26 PM UTC **Owner:** Paul Morris Doc: CG: Add guideline for use of 'CSS' prefix in commit messages http://codereview.appspot.com/325970043 --- Sent from sourceforge.net because testlilyissues-a...@lists.sourceforge.net is subscribed to https://sourceforge.net/p/testlilyissues/issues/ To unsubscribe from further messages, a project admin can change settings at https://sourceforge.net/p/testlilyissues/admin/issues/options. Or, if this is a mailing list, you can unsubscribe from the mailing list.-- Check out the vibrant tech community on one of the world's most engaging tech sites, Slashdot.org! http://sdm.link/slashdot___ Testlilyissues-auto mailing list testlilyissues-a...@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/testlilyissues-auto
[Lilypond-auto] [LilyIssues-auto] [testlilyissues:issues] #5152 Doc: CG: Add guideline for use of 'CSS' prefix in commit messages
- **Patch**: review --> countdown - **Comment**: Patch on countdown for July 16th --- ** [issues:#5152] Doc: CG: Add guideline for use of 'CSS' prefix in commit messages** **Status:** Started **Created:** Tue Jul 04, 2017 07:22 PM UTC by Paul Morris **Last Updated:** Mon Jul 10, 2017 03:07 PM UTC **Owner:** Paul Morris Doc: CG: Add guideline for use of 'CSS' prefix in commit messages http://codereview.appspot.com/325970043 --- Sent from sourceforge.net because testlilyissues-a...@lists.sourceforge.net is subscribed to https://sourceforge.net/p/testlilyissues/issues/ To unsubscribe from further messages, a project admin can change settings at https://sourceforge.net/p/testlilyissues/admin/issues/options. Or, if this is a mailing list, you can unsubscribe from the mailing list.-- Check out the vibrant tech community on one of the world's most engaging tech sites, Slashdot.org! http://sdm.link/slashdot___ Testlilyissues-auto mailing list testlilyissues-a...@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/testlilyissues-auto
[Lilypond-auto] [LilyIssues-auto] [testlilyissues:issues] #4603 change all occurences of ‘partcombine’ to ‘partCombine’.
- **assigned_to**: Charles Winston --> pkx166h - **Patch**: new --> waiting - **Type**: --> Enhancement - **Comment**: I'll set this to 'Waiting' for now as I have no problems with waiting until 2.20 is released and there is no pressing requirement for what has been done so far. --- ** [issues:#4603] change all occurences of ‘partcombine’ to ‘partCombine’.** **Status:** Started **Created:** Sun Sep 13, 2015 03:17 PM UTC by pkx166h **Last Updated:** Mon Jul 10, 2017 02:48 PM UTC **Owner:** pkx166h On 13/08/15 21:42, Malte Meyn wrote: > Hi list, > > the case of the ‘c’ in partcombine is inconsistent, confusing me every > time I use \partcombine(Apart|Chords|…): > > \partcombine, \partcombineApart, … but > \partCombineTextsOnNote, \partCombineListener > > I would suggest to change all occurences of ‘partcombine’ to ‘partCombine’. > > Why not change ‘partCombine’ to ‘partcombine’? Because I looked at the > engravers which use the more ‘natural’ underscore instead of camelCase > for spaces. And in the same way as ‘Cue_clef_engraver’ suggests that > ‘cue clef’ are two words (resulting in ‘cueClefGlyph’, not > ‘cueclefGlyph’), ‘Part_combine_engraver’ does. > > I think that this would be rather easy to change. > > Cheers, > Malte Response to Issue #4603: Syntax change from all instances "partcombine" to "partCombine" and convert-ly rule added to go along with. http://codereview.appspot.com/323040043 - part 1 of 3 http://codereview.appspot.com/326870043 - part 2 of 3 http://codereview.appspot.com/327970043 - part 3 of 3 Note this will require both a convert.ly and a makelsr.py run to make sure that the patch passes all the tests. --- Sent from sourceforge.net because testlilyissues-a...@lists.sourceforge.net is subscribed to https://sourceforge.net/p/testlilyissues/issues/ To unsubscribe from further messages, a project admin can change settings at https://sourceforge.net/p/testlilyissues/admin/issues/options. Or, if this is a mailing list, you can unsubscribe from the mailing list.-- Check out the vibrant tech community on one of the world's most engaging tech sites, Slashdot.org! http://sdm.link/slashdot___ Testlilyissues-auto mailing list testlilyissues-a...@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/testlilyissues-auto
[Lilypond-auto] [LilyIssues-auto] [testlilyissues:issues] #5154 Centering bass figures on whole notes and longer
--- ** [issues:#5154] Centering bass figures on whole notes and longer** **Status:** Started **Created:** Fri Jul 14, 2017 03:41 PM UTC by pkx166h **Last Updated:** Fri Jul 14, 2017 03:41 PM UTC **Owner:** nobody Centering bass figures on whole notes and longer This is a patch that fixes the centering of single bass figures over notes of duration whole note and more. The duration is tested and a translate applied horizontally if needed. http://codereview.appspot.com/325070043 --- Sent from sourceforge.net because testlilyissues-a...@lists.sourceforge.net is subscribed to https://sourceforge.net/p/testlilyissues/issues/ To unsubscribe from further messages, a project admin can change settings at https://sourceforge.net/p/testlilyissues/admin/issues/options. Or, if this is a mailing list, you can unsubscribe from the mailing list.-- Check out the vibrant tech community on one of the world's most engaging tech sites, Slashdot.org! http://sdm.link/slashdot___ Testlilyissues-auto mailing list testlilyissues-a...@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/testlilyissues-auto
[Lilypond-auto] [LilyIssues-auto] [testlilyissues:issues] #5154 Centering bass figures on whole notes and longer
- Description has changed:
Diff:
--- old
+++ new
@@ -1,3 +1,47 @@
+From: Richard Shann
+Subject: Patch to fix centering of some bass figures on whole notes and
longer.
+Date: Sun, 09 Jul 2017 15:05:18 +0100
+
+Simon Albrecht suggested I start a new thread for this (apologies for
+any confusion)
+
+Attached is a patch that fixes the centering of single bass figures over
+notes of duration whole note and more. The duration is tested and a
+translate applied horizontally if needed.
+
+A test snippet is this:
+
+8><8><8><8><8><8><8><8><8><8><8><8><8><8><8><8><
+<<
+
+{
+
+\time 4/2 c''\breve c'' c''1 c''
+
+c''4 c'' c'' c''
+
+
+}
+
+\new FiguredBass {
+
+\figuremode {
+
+<_+>\breve <_-> <3>1 <3+>
+
+<_+>4 <_-> <3> <3+>
+
+}
+
+}
+
+>>
+8><8><8><8><8><8><8><8><8><8><8><8><8><8><8><8><
+
+In version until now the single character figures are placed to the left
+of the true center.
+
+
Centering bass figures on whole notes and longer
This is a patch that fixes
- **Needs**: -->
- **Patch**: new --> review
---
** [issues:#5154] Centering bass figures on whole notes and longer**
**Status:** Started
**Created:** Fri Jul 14, 2017 03:41 PM UTC by pkx166h
**Last Updated:** Fri Jul 14, 2017 03:41 PM UTC
**Owner:** pkx166h
From: Richard Shann
Subject:Patch to fix centering of some bass figures on whole notes and
longer.
Date: Sun, 09 Jul 2017 15:05:18 +0100
Simon Albrecht suggested I start a new thread for this (apologies for
any confusion)
Attached is a patch that fixes the centering of single bass figures over
notes of duration whole note and more. The duration is tested and a
translate applied horizontally if needed.
A test snippet is this:
8><8><8><8><8><8><8><8><8><8><8><8><8><8><8><8><
<<
{
\time 4/2 c''\breve c'' c''1 c''
c''4 c'' c'' c''
}
\new FiguredBass {
\figuremode {
<_+>\breve <_-> <3>1 <3+>
<_+>4 <_-> <3> <3+>
}
}
>>
8><8><8><8><8><8><8><8><8><8><8><8><8><8><8><8><
In version until now the single character figures are placed to the left
of the true center.
Centering bass figures on whole notes and longer
This is a patch that fixes
the centering of single bass
figures over notes of duration
whole note and more.
The duration is tested and a
translate applied horizontally
if needed.
http://codereview.appspot.com/325070043
---
Sent from sourceforge.net because testlilyissues-a...@lists.sourceforge.net is
subscribed to https://sourceforge.net/p/testlilyissues/issues/
To unsubscribe from further messages, a project admin can change settings at
https://sourceforge.net/p/testlilyissues/admin/issues/options. Or, if this is
a mailing list, you can unsubscribe from the mailing list.--
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot___
Testlilyissues-auto mailing list
testlilyissues-a...@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/testlilyissues-auto
[Lilypond-auto] [LilyIssues-auto] [testlilyissues:issues] Re: #5154 Centering bass figures on whole notes and longer
From: Richard Shann
Subject:Re: Patch to fix centering of some bass figures on whole notes
and longer.
Date: Sun, 09 Jul 2017 17:51:32 +0100
On Sun, 2017-07-09 at 18:46 +0200, David Kastrup wrote:
> Richard Shann writes:
>
> > Simon Albrecht suggested I start a new thread for this (apologies for
> > any confusion)
> >
> > Attached is a patch that fixes the centering of single bass figures over
> > notes of duration whole note and more. The duration is tested and a
> > translate applied horizontally if needed.
>
> Except that the "centering" or not decision then rests on the duration
> of the bass figure rather than any properties of the note column in
> question.
>
> I think it isn't uncommon to have bass lines where there isn't one
> figure per bass note but there are also intermediate notes without
> figure.
Indeed, there are frequently notes without figures (more often than not
in fact) and there are also multiple figures per note, and figures on
rests. Not sure what any of that has to do with this.
In the current LilyPond the figures are centered (visually speaking - I
don't know how they relate to internals such as note column) for
durations greater than 0 but too far to the left for the others (always
referring here to the case of a single figures on a note).
Richard
---
** [issues:#5154] Centering bass figures on whole notes and longer**
**Status:** Started
**Created:** Fri Jul 14, 2017 03:41 PM UTC by pkx166h
**Last Updated:** Fri Jul 14, 2017 03:43 PM UTC
**Owner:** pkx166h
From: Richard Shann
Subject:Patch to fix centering of some bass figures on whole notes and
longer.
Date: Sun, 09 Jul 2017 15:05:18 +0100
Simon Albrecht suggested I start a new thread for this (apologies for
any confusion)
Attached is a patch that fixes the centering of single bass figures over
notes of duration whole note and more. The duration is tested and a
translate applied horizontally if needed.
A test snippet is this:
8><8><8><8><8><8><8><8><8><8><8><8><8><8><8><8><
<<
{
\time 4/2 c''\breve c'' c''1 c''
c''4 c'' c'' c''
}
\new FiguredBass {
\figuremode {
<_+>\breve <_-> <3>1 <3+>
<_+>4 <_-> <3> <3+>
}
}
>>
8><8><8><8><8><8><8><8><8><8><8><8><8><8><8><8><
In version until now the single character figures are placed to the left
of the true center.
Centering bass figures on whole notes and longer
This is a patch that fixes
the centering of single bass
figures over notes of duration
whole note and more.
The duration is tested and a
translate applied horizontally
if needed.
http://codereview.appspot.com/325070043
---
Sent from sourceforge.net because testlilyissues-a...@lists.sourceforge.net is
subscribed to https://sourceforge.net/p/testlilyissues/issues/
To unsubscribe from further messages, a project admin can change settings at
https://sourceforge.net/p/testlilyissues/admin/issues/options. Or, if this is
a mailing list, you can unsubscribe from the mailing list.--
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot___
Testlilyissues-auto mailing list
testlilyissues-a...@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/testlilyissues-auto
[Lilypond-auto] [LilyIssues-auto] [testlilyissues:issues] #5154 Centering bass figures on whole notes and longer
From: David Kastrup
Subject:Re: Patch to fix centering of some bass figures on whole notes
and longer.
Date: Sun, 09 Jul 2017 18:46:25 +0200
User-agent: Gnus/5.13 (Gnus v5.13) Emacs/26.0.50 (gnu/linux)
Richard Shann writes:
> Simon Albrecht suggested I start a new thread for this (apologies for
> any confusion)
>
> Attached is a patch that fixes the centering of single bass figures over
> notes of duration whole note and more. The duration is tested and a
> translate applied horizontally if needed.
Except that the "centering" or not decision then rests on the duration
of the bass figure rather than any properties of the note column in
question.
I think it isn't uncommon to have bass lines where there isn't one
figure per bass note but there are also intermediate notes without
figure.
--
David Kastrup
---
** [issues:#5154] Centering bass figures on whole notes and longer**
**Status:** Started
**Created:** Fri Jul 14, 2017 03:41 PM UTC by pkx166h
**Last Updated:** Fri Jul 14, 2017 03:43 PM UTC
**Owner:** pkx166h
From: Richard Shann
Subject:Patch to fix centering of some bass figures on whole notes and
longer.
Date: Sun, 09 Jul 2017 15:05:18 +0100
Simon Albrecht suggested I start a new thread for this (apologies for
any confusion)
Attached is a patch that fixes the centering of single bass figures over
notes of duration whole note and more. The duration is tested and a
translate applied horizontally if needed.
A test snippet is this:
8><8><8><8><8><8><8><8><8><8><8><8><8><8><8><8><
<<
{
\time 4/2 c''\breve c'' c''1 c''
c''4 c'' c'' c''
}
\new FiguredBass {
\figuremode {
<_+>\breve <_-> <3>1 <3+>
<_+>4 <_-> <3> <3+>
}
}
>>
8><8><8><8><8><8><8><8><8><8><8><8><8><8><8><8><
In version until now the single character figures are placed to the left
of the true center.
Centering bass figures on whole notes and longer
This is a patch that fixes
the centering of single bass
figures over notes of duration
whole note and more.
The duration is tested and a
translate applied horizontally
if needed.
http://codereview.appspot.com/325070043
---
Sent from sourceforge.net because testlilyissues-a...@lists.sourceforge.net is
subscribed to https://sourceforge.net/p/testlilyissues/issues/
To unsubscribe from further messages, a project admin can change settings at
https://sourceforge.net/p/testlilyissues/admin/issues/options. Or, if this is
a mailing list, you can unsubscribe from the mailing list.--
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot___
Testlilyissues-auto mailing list
testlilyissues-a...@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/testlilyissues-auto
[Lilypond-auto] [LilyIssues-auto] [testlilyissues:issues] #5154 Centering bass figures on whole notes and longer
- **Comment**:
Passes make, make check and a full make doc.
---
** [issues:#5154] Centering bass figures on whole notes and longer**
**Status:** Started
**Created:** Fri Jul 14, 2017 03:41 PM UTC by pkx166h
**Last Updated:** Fri Jul 14, 2017 03:43 PM UTC
**Owner:** pkx166h
From: Richard Shann
Subject:Patch to fix centering of some bass figures on whole notes and
longer.
Date: Sun, 09 Jul 2017 15:05:18 +0100
Simon Albrecht suggested I start a new thread for this (apologies for
any confusion)
Attached is a patch that fixes the centering of single bass figures over
notes of duration whole note and more. The duration is tested and a
translate applied horizontally if needed.
A test snippet is this:
8><8><8><8><8><8><8><8><8><8><8><8><8><8><8><8><
<<
{
\time 4/2 c''\breve c'' c''1 c''
c''4 c'' c'' c''
}
\new FiguredBass {
\figuremode {
<_+>\breve <_-> <3>1 <3+>
<_+>4 <_-> <3> <3+>
}
}
>>
8><8><8><8><8><8><8><8><8><8><8><8><8><8><8><8><
In version until now the single character figures are placed to the left
of the true center.
Centering bass figures on whole notes and longer
This is a patch that fixes
the centering of single bass
figures over notes of duration
whole note and more.
The duration is tested and a
translate applied horizontally
if needed.
http://codereview.appspot.com/325070043
---
Sent from sourceforge.net because testlilyissues-a...@lists.sourceforge.net is
subscribed to https://sourceforge.net/p/testlilyissues/issues/
To unsubscribe from further messages, a project admin can change settings at
https://sourceforge.net/p/testlilyissues/admin/issues/options. Or, if this is
a mailing list, you can unsubscribe from the mailing list.--
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot___
Testlilyissues-auto mailing list
testlilyissues-a...@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/testlilyissues-auto
[Lilypond-auto] [LilyIssues-auto] [testlilyissues:issues] #5154 Centering bass figures on whole notes and longer
As David already pointed out this patch looks only at the duration of the
BassFigure whether to apply some translation or not. This will only work, if
the durations of BassFigure and related note match.
To illustrate:
~~~
<<
\relative c' { c1 c'8 d e f g f e d }
\figures { <6+>2 <6+>2 <6+>1 }
~~~
Only the third BassFigure is moved, but shouldn't!
See attached.
I'd rather go for a procedure looking at NoteColumn, applying it to
BassFigure.X-offset or the like to get convincing aligning.
Attachments:
-
[atest-63.png](https://sourceforge.net/p/testlilyissues/issues/_discuss/thread/2e2f0279/1933/attachment/atest-63.png)
(4.9 kB; image/png)
---
** [issues:#5154] Centering bass figures on whole notes and longer**
**Status:** Started
**Created:** Fri Jul 14, 2017 03:41 PM UTC by pkx166h
**Last Updated:** Fri Jul 14, 2017 03:45 PM UTC
**Owner:** pkx166h
From: Richard Shann
Subject:Patch to fix centering of some bass figures on whole notes and
longer.
Date: Sun, 09 Jul 2017 15:05:18 +0100
Simon Albrecht suggested I start a new thread for this (apologies for
any confusion)
Attached is a patch that fixes the centering of single bass figures over
notes of duration whole note and more. The duration is tested and a
translate applied horizontally if needed.
A test snippet is this:
8><8><8><8><8><8><8><8><8><8><8><8><8><8><8><8><
<<
{
\time 4/2 c''\breve c'' c''1 c''
c''4 c'' c'' c''
}
\new FiguredBass {
\figuremode {
<_+>\breve <_-> <3>1 <3+>
<_+>4 <_-> <3> <3+>
}
}
>>
8><8><8><8><8><8><8><8><8><8><8><8><8><8><8><8><
In version until now the single character figures are placed to the left
of the true center.
Centering bass figures on whole notes and longer
This is a patch that fixes
the centering of single bass
figures over notes of duration
whole note and more.
The duration is tested and a
translate applied horizontally
if needed.
http://codereview.appspot.com/325070043
---
Sent from sourceforge.net because testlilyissues-a...@lists.sourceforge.net is
subscribed to https://sourceforge.net/p/testlilyissues/issues/
To unsubscribe from further messages, a project admin can change settings at
https://sourceforge.net/p/testlilyissues/admin/issues/options. Or, if this is
a mailing list, you can unsubscribe from the mailing list.--
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot___
Testlilyissues-auto mailing list
testlilyissues-a...@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/testlilyissues-auto
[Lilypond-auto] [LilyIssues-auto] [testlilyissues:issues] #5154 Centering bass figures on whole notes and longer
I now coded such a callback.
See attached.
The file includes the relevant regtest.
Triggered by figured-bass-extenders-markup.ly a design-decision is be needed,
how to deal with text-markups.
Needs design-decision as well: how to deal with suspended NoteHeads.
Attachments:
-
[atest-63.ly](https://sourceforge.net/p/testlilyissues/issues/_discuss/thread/2e2f0279/ce35/attachment/atest-63.ly)
(9.9 kB; text/x-lilypond)
---
** [issues:#5154] Centering bass figures on whole notes and longer**
**Status:** Started
**Created:** Fri Jul 14, 2017 03:41 PM UTC by pkx166h
**Last Updated:** Sat Jul 15, 2017 07:06 AM UTC
**Owner:** pkx166h
From: Richard Shann
Subject:Patch to fix centering of some bass figures on whole notes and
longer.
Date: Sun, 09 Jul 2017 15:05:18 +0100
Simon Albrecht suggested I start a new thread for this (apologies for
any confusion)
Attached is a patch that fixes the centering of single bass figures over
notes of duration whole note and more. The duration is tested and a
translate applied horizontally if needed.
A test snippet is this:
8><8><8><8><8><8><8><8><8><8><8><8><8><8><8><8><
<<
{
\time 4/2 c''\breve c'' c''1 c''
c''4 c'' c'' c''
}
\new FiguredBass {
\figuremode {
<_+>\breve <_-> <3>1 <3+>
<_+>4 <_-> <3> <3+>
}
}
>>
8><8><8><8><8><8><8><8><8><8><8><8><8><8><8><8><
In version until now the single character figures are placed to the left
of the true center.
Centering bass figures on whole notes and longer
This is a patch that fixes
the centering of single bass
figures over notes of duration
whole note and more.
The duration is tested and a
translate applied horizontally
if needed.
http://codereview.appspot.com/325070043
---
Sent from sourceforge.net because testlilyissues-a...@lists.sourceforge.net is
subscribed to https://sourceforge.net/p/testlilyissues/issues/
To unsubscribe from further messages, a project admin can change settings at
https://sourceforge.net/p/testlilyissues/admin/issues/options. Or, if this is
a mailing list, you can unsubscribe from the mailing list.--
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot___
Testlilyissues-auto mailing list
testlilyissues-a...@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/testlilyissues-auto
[Lilypond-auto] [LilyIssues-auto] [testlilyissues:issues] #5155 Allow { expression } in markup command arguments
---
** [issues:#5155] Allow { expression } in markup command arguments**
**Status:** Started
**Created:** Sun Jul 16, 2017 03:36 PM UTC by David Kastrup
**Last Updated:** Sun Jul 16, 2017 03:36 PM UTC
**Owner:** nobody
Allow { expression } in markup command arguments
This allows utilizing basically what ##{ expression #} would.
Additionally, music introduced with \chordmode, \notemode, \lyricmode,
\figuremode is permitted (with the necessary argument) as well as
music identifiers.
A delimited argument is needed in order to switch back into markup
mode in an orderly manner. '{' and '}' are already special in markup
modes and thus suitable for delimination and the explicit mode
commands offer delimination as well.
This is 2.21 material. Time to fork.
http://codereview.appspot.com/329850043
---
Sent from sourceforge.net because testlilyissues-a...@lists.sourceforge.net is
subscribed to https://sourceforge.net/p/testlilyissues/issues/
To unsubscribe from further messages, a project admin can change settings at
https://sourceforge.net/p/testlilyissues/admin/issues/options. Or, if this is
a mailing list, you can unsubscribe from the mailing list.--
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot___
Testlilyissues-auto mailing list
testlilyissues-a...@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/testlilyissues-auto
