[Lilypond-auto] [LilyIssues-auto] [testlilyissues:issues] #5164 Add usage of OpenType font feature to the documents

2017-07-26 Thread Auto mailings of changes to Lily Issues via Testlilyissues-auto 
- Description has changed:

Diff:







- **Needs**:  -->  
- **Patch**: new --> review



---

** [issues:#5164] Add usage of OpenType font feature to the documents**

**Status:** Started
**Created:** Wed Jul 26, 2017 01:24 PM UTC by Masamichi Hosoda
**Last Updated:** Wed Jul 26, 2017 03:33 PM UTC
**Owner:** Masamichi Hosoda


Add usage of OpenType font feature to the documents

This commit adds the usage of OpenType font feature
added in Issue 1388 to the document.

http://codereview.appspot.com/328140043


---

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

2017-07-26 Thread Auto mailings of changes to Lily Issues via Testlilyissues-auto 
Patch counted down - please push


---

** [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 23, 2017 07:21 AM UTC
**Owner:** David Kastrup


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

[Lilypond-auto] [LilyIssues-auto] [testlilyissues:issues] Re: #5162 Some hooks useful for video production

2017-07-26 Thread Auto mailings of changes to Lily Issues via Testlilyissues-auto 
> Passing postscript code to other backends indeed is a good idea ;-)

So you agree that a hook mechanism discriminating between backends is a good 
idea.  That's why I proposed it.


---

** [issues:#5162] Some hooks useful for video production**

**Status:** Started
**Created:** Tue Jul 25, 2017 05:48 PM UTC by Knut Petersen
**Last Updated:** Wed Jul 26, 2017 11:51 AM UTC
**Owner:** Knut Petersen
**Attachments:**

- 
[0001-Implement-some-hooks-useful-for-producing-score-vide.patch](https://sourceforge.net/p/testlilyissues/issues/5162/attachment/0001-Implement-some-hooks-useful-for-producing-score-vide.patch)
 (7.7 kB; text/x-patch)


Producing ps or pdf documents intended to be used as
a source for video production requires some changes to
the output at a very late stage.

Often a page needs to repeated more than once with only
changes to some kind of progress bar / line or changes
to the color of a few grobs.

Parts of this postprocessing might be passed to postscript,
parts of this postprocessing might be done in the dump-page
procedure.

Therefore this patch provides a hook to write arbitrary
code to the prolog section of postscript output and a
hook to take over the dump-page process.

Using rgb values  < 0 and > 1 for grobs is an efficient
way to pass the information that, when and for how long
an object should change its color to a late state of
processing. Therefore a way to disable the range
check implemented in color? and to disable the precision
restriction in setrgbcolor is provided.



---

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] #5165 [Feature Request]: More flexible SVG snippet cropping

2017-07-26 Thread Auto mailings of changes to Lily Issues via Testlilyissues-auto 
Hello! I use lilypond quite often to illustrate and show snippets of music
on the web, both using lilypond-book and other tools (such as MediaWiki
's Score extension
). Looking at the process
for lilypond-book, I see that the snippets are in a .png format and are cropped
using "gs", not natively.

As a feature, my final objective would be the ability to typeset the
snippets into a vector format, as the resolution's better and it takes up
less space.

In order for the goal to be eventually reached, cropping would have to be
native to lilypond. Right now, there is no cropping for SVGs. Each
generated SVG is the size of the page, through the height, width, and
viewBox="0
0 119.5016 169.0094" attributes.

With individual snippets I've typeset into SVG, I've been taking the
bounding box and using that as the viewBox; modifying the snippets with
this js:

var svg = document.getElementsByTagName("svg")[0];
var box = svg.getBBox();
var viewBox = [box.x, box.y, box.width, box.height].join(" ");

console.log(svg.getAttribute(viewBox));
svg.setAttribute("viewBox", viewBox);
svg.removeAttribute("height");
svg.removeAttribute("width");
console.log(viewBox);

However, I don't think it's a very good solution; finding that such
functionality should be built-in to lilypond, and not require the use of
user javascript (of which would be unusable anyway with img tags used with
PNGs.

In the MediaWiki extension, I've been trying to find a way, and the feature
request is being tracked: https://phabricator.wikimedia.org/T49578. Making
the extension output SVG is no problem (just change the backend on the
lilypond command), but cropping is. I believe that the Lilypond project
would be more suited to handle and incorporate this proposed feature, and
could potentially be useful when outputting PNG too. A flag could be added
to the command if cropping is desired.

Thank you for considering my feature request. This would not only help me,
but make Lilypond more flexible for typesetting music.

Cordially,

Étienne Beaulé


---

** [issues:#5165] [Feature Request]: More flexible SVG snippet cropping**

**Status:** New
**Created:** Wed Jul 26, 2017 02:56 PM UTC by pkx166h
**Last Updated:** Wed Jul 26, 2017 02:56 PM UTC
**Owner:** nobody


I might have posted my request to the wrong mailing list. The original
message is below, but is not quite relevant with some new developments.

I have found the -dpreview option, but has a big limitation as it only
outputs the first line.

Looking through the code, my feature seems like in between the two existing
methods dump-page and dump-preview, found in scm/framework-svg.scm. The
little stumbling block is how both methods are invoked
separately: output-framework or output-preview-framework, both supplying
different arguments, the main difference being "stensil" that is required
for calculating the viewbox, but is not in dump-page.

Would it be possible for the two methods to be merged, so that there's an
option for cropping on pages that are not just previews (and on multi-page
scores)? (Or if a third method could be made...)

If someone could add this feature, it would be very useful for my work, and
for Lilypond's prominence on Wikipedia.

Cordially,

Étienne Beaulé


---

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] #5164 Add usage of OpenType font feature to the documents

2017-07-26 Thread Auto mailings of changes to Lily Issues via Testlilyissues-auto 
Out of interest is there a standard list of all the possible OT 
'features/functions' even if not all of them use them all?


---

** [issues:#5164] Add usage of OpenType font feature to the documents**

**Status:** Started
**Created:** Wed Jul 26, 2017 01:24 PM UTC by Masamichi Hosoda
**Last Updated:** Wed Jul 26, 2017 01:24 PM UTC
**Owner:** Masamichi Hosoda


Add usage of OpenType font feature to the documents

This commit adds the usage of OpenType font feature
added in Issue 1388 to the document.

http://codereview.appspot.com/328140043


---

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] #5157 Doc: add comment about automatically generated documentation

2017-07-26 Thread Auto mailings of changes to Lily Issues via Testlilyissues-auto 
- **Patch**: countdown --> push
- **Comment**:

Patch counted down - please push.



---

** [issues:#5157] Doc: add comment about automatically generated documentation**

**Status:** Started
**Created:** Mon Jul 17, 2017 04:39 PM UTC by Federico Bruni
**Last Updated:** Sun Jul 23, 2017 07:23 AM UTC
**Owner:** Federico Bruni


http://codereview.appspot.com/321270043Doc: add comment about automatically 
generated documentation

This is mainly for translators. See this discussion:
http://lilypond-translations.3384276.n2.nabble.com/Doubt-about-ref-Align-in-text-itely-of-the-notationn-manual-td7572987.html


http://codereview.appspot.com/321270043


---

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] #5156 Change \note markup command to get a duration

2017-07-26 Thread Auto mailings of changes to Lily Issues via Testlilyissues-auto 
Patch counted down - please push


---

** [issues:#5156] Change \note markup command to get a duration**

**Status:** Started
**Created:** Sun Jul 16, 2017 03:48 PM UTC by David Kastrup
**Last Updated:** Sun Jul 23, 2017 07:22 AM UTC
**Owner:** David Kastrup


Change \note markup command to get a duration

Previously, it used a string.


First patch only establishes baseline of issue 5155, second patch is
the actual change.  Third patch is the result of running
scripts/auxiliar/update-with-convert-ly.

http://codereview.appspot.com/328050043


---

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] #5164 Add usage of OpenType font feature to the documents

2017-07-26 Thread Auto mailings of changes to Lily Issues via Testlilyissues-auto 
Passes make, make check and a full make doc.


---

** [issues:#5164] Add usage of OpenType font feature to the documents**

**Status:** Started
**Created:** Wed Jul 26, 2017 01:24 PM UTC by Masamichi Hosoda
**Last Updated:** Wed Jul 26, 2017 03:25 PM UTC
**Owner:** Masamichi Hosoda


Add usage of OpenType font feature to the documents

This commit adds the usage of OpenType font feature
added in Issue 1388 to the document.

http://codereview.appspot.com/328140043


---

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] #5163 Update URW++ OTF files

2017-07-26 Thread Auto mailings of changes to Lily Issues via Testlilyissues-auto 
- Description has changed:

Diff:







- **Needs**:  -->  
- **Patch**: new --> review
- **Comment**:

Passes make, make check and a full make doc - I applied all the URW++ fonts 
from the git repo and then did all the standard tests.



---

** [issues:#5163] Update URW++ OTF files**

**Status:** Started
**Created:** Wed Jul 26, 2017 11:56 AM UTC by Masamichi Hosoda
**Last Updated:** Wed Jul 26, 2017 11:56 AM UTC
**Owner:** Masamichi Hosoda


Update URW++ OTF files

URW++ has been released URW++ core 35 fonts 2017-07-20.
It has some bugfixes.

This commit makes configure script can find latest URW++ OTF files (2017-07-20).
http://git.ghostscript.com/?p=urw-core35-fonts.git;a=tree;hb=1f28a6fcd2176256a995db907d9ffe6e1b9b83e9

It also can find previously released files (2017-05 and 2016).
http://git.ghostscript.com/?p=urw-core35-fonts.git;a=tree;hb=e3c665a8a3df36a54b22ad0b6176283db5310f97
http://git.ghostscript.com/?p=urw-core35-fonts.git;a=tree;hb=79bcdfb34fbce12b592cce389fa7a19da6b5b018

http://codereview.appspot.com/321350043


---

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] #5157 Doc: add comment about automatically generated documentation

2017-07-26 Thread Auto mailings of changes to Lily Issues via Testlilyissues-auto 
- **labels**:  --> Fixed_2_19_65
- **status**: Started --> Fixed
- **Comment**:

pushed to staging as commit 2dcca6dacd9f419922a7d056389b152f195d6e4c



---

** [issues:#5157] Doc: add comment about automatically generated documentation**

**Status:** Fixed
**Labels:** Fixed_2_19_65 
**Created:** Mon Jul 17, 2017 04:39 PM UTC by Federico Bruni
**Last Updated:** Wed Jul 26, 2017 02:44 PM UTC
**Owner:** Federico Bruni


http://codereview.appspot.com/321270043Doc: add comment about automatically 
generated documentation

This is mainly for translators. See this discussion:
http://lilypond-translations.3384276.n2.nabble.com/Doubt-about-ref-Align-in-text-itely-of-the-notationn-manual-td7572987.html


http://codereview.appspot.com/321270043


---

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] #5159 Web: Authors.itexi update

2017-07-26 Thread Auto mailings of changes to Lily Issues via Testlilyissues-auto 
author  James Lowe   
Thu, 20 Jul 2017 13:16:41 +0100 (13:16 +0100)
committer   James Lowe   
Wed, 26 Jul 2017 18:47:04 +0100 (18:47 +0100)
commit  54a35cdc574e4088ea8a0aa81b7df0789de758bc


---

** [issues:#5159] Web: Authors.itexi update**

**Status:** Fixed
**Labels:** FIxed_2_19_65 
**Created:** Thu Jul 20, 2017 12:17 PM UTC by pkx166h
**Last Updated:** Wed Jul 26, 2017 05:49 PM UTC
**Owner:** pkx166h


Web: Authors.itexi update

>From October 2016 until
July 2017 Based on all
those contributors for
2.18.x and current 2.19.x.

http://codereview.appspot.com/323320043


---

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] #5159 Web: Authors.itexi update

2017-07-26 Thread Auto mailings of changes to Lily Issues via Testlilyissues-auto 
- **labels**:  --> FIxed_2_19_65
- **status**: Started --> Fixed
- **Patch**: push -->  



---

** [issues:#5159] Web: Authors.itexi update**

**Status:** Fixed
**Labels:** FIxed_2_19_65 
**Created:** Thu Jul 20, 2017 12:17 PM UTC by pkx166h
**Last Updated:** Wed Jul 26, 2017 02:44 PM UTC
**Owner:** pkx166h


Web: Authors.itexi update

>From October 2016 until
July 2017 Based on all
those contributors for
2.18.x and current 2.19.x.

http://codereview.appspot.com/323320043


---

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] #5160 Doc: CG, explain other git prompt variables

2017-07-26 Thread Auto mailings of changes to Lily Issues via Testlilyissues-auto 
- **labels**:  --> FIxed_2_19_65
- **status**: Started --> Fixed
- **Comment**:

pushed to staging as commit 68dbc841e3401f14b900f6750ebb49b406caf357



---

** [issues:#5160] Doc: CG, explain other git prompt variables**

**Status:** Fixed
**Labels:** FIxed_2_19_65 
**Created:** Thu Jul 20, 2017 09:14 PM UTC by Federico Bruni
**Last Updated:** Wed Jul 26, 2017 02:44 PM UTC
**Owner:** Federico Bruni


Doc: CG, explain other git prompt variables

The use of these environment variables is documented within the
git source code: git/contrib/completion/git-prompt.sh

Background: in January a translator using LilyDev made a
simple mistake because he did not know the meaning of the
symbols in the git prompt:
http://lilypond-translations.3384276.n2.nabble.com/More-Catalan-translations-td7572931.html

http://codereview.appspot.com/328890043


---

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] Ticket 3609 discussion

2017-07-24 Thread Auto mailings of changes to Lily Issues via Testlilyissues-auto 
Things are even worse if \start/stopStaff is happen at line-break, repeat-signs 
and different StaffSymbol.line-positions are used.

~~~
\paper {
  indent = 0
  line-width = 40
}

musII = { 
  \repeat volta 2 { c'1 }
  %\workAround
  \break 
  \stopStaff 
  \override Staff.StaffSymbol.line-positions = #'(-6) 
  \override Staff.Clef #'stencil = ##f
  \startStaff 
  \repeat volta 2 { c'1 }
}

\new StaffGroup 
  <<
\new Staff \musII
\new Staff \musII

~~~
See attached png.

A workaround for the Barline could be:
~~~
workAround =
\once \override Staff.BarLine #'before-line-breaking =
  #(lambda (grob)
(if (eqv? LEFT (ly:item-break-dir grob))
(begin
  (ly:grob-set-property! grob 'bar-extent '(-5 . -1))
  (ly:grob-set-property! grob 'Y-extent '(-5 . -1))
  (ly:grob-set-property! grob 'Y-offset 3
~~~
Still no SpanBar, that's issue 2876, though.



Attachments:

- 
[atest-63-1.png](https://sourceforge.net/p/testlilyissues/issues/_discuss/thread/42f48c44/d912/attachment/atest-63-1.png)
 (8.8 kB; image/png)


---

** [issues:#3609] \stopStaff at the end of a measure should produce a bar line 
spanning the previous staff lines**

**Status:** Accepted
**Created:** Sun Oct 13, 2013 03:09 PM UTC by Anonymous
**Last Updated:** Sun Oct 13, 2013 03:09 PM UTC
**Owner:** nobody


*Originally created by:* *anonymous

*Originally created by:* 
[elu...@gmail.com](http://code.google.com/u/114137843947982417046/)

several uglies have been discussed in this thread 
[http://lilypond.1069038.n5.nabble.com/ugly-bar-line-when-changing-line-count-td152072.html](http://lilypond.1069038.n5.nabble.com/ugly-bar-line-when-changing-line-count-td152072.html)

1\. the main outline is that a \stopStaff \startStaff doesn't terminate 
"correctly" a measure with a staff-bar covering the full line-count of the 
preceding measure but just spans the line-count of the following code.

2\. when a time signature change \(or key or clef\) occurs the staff lines of 
the preceding and following measure overlap.

3\. if there are accidentals involved they are not clearly separated from the 
preceding part

workarounds are presented in the link above but the majority of the 
participants to the discussion \(66:33%\) vote for a clean LilyPond integrated 
solution - and honestly I'd also appreciate if this would happen automatically.


---

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] #5160 Doc: CG, explain other git prompt variables

2017-07-20 Thread Auto mailings of changes to Lily Issues via Testlilyissues-auto 



---

** [issues:#5160] Doc: CG, explain other git prompt variables**

**Status:** Started
**Created:** Thu Jul 20, 2017 09:14 PM UTC by Federico Bruni
**Last Updated:** Thu Jul 20, 2017 09:14 PM UTC
**Owner:** nobody


Doc: CG, explain other git prompt variables

The use of these environment variables is documented within the
git source code: git/contrib/completion/git-prompt.sh

Background: in January a translator using LilyDev made a
simple mistake because he did not know the meaning of the
symbols in the git prompt:
http://lilypond-translations.3384276.n2.nabble.com/More-Catalan-translations-td7572931.html

http://codereview.appspot.com/328890043


---

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] #5161 Announce slur ends when they are known

2017-07-24 Thread Auto mailings of changes to Lily Issues via Testlilyissues-auto 



---

** [issues:#5161] Announce slur ends when they are known**

**Status:** Started
**Created:** Mon Jul 24, 2017 11:12 AM UTC by David Kastrup
**Last Updated:** Mon Jul 24, 2017 11:12 AM UTC
**Owner:** nobody


Announce slur ends when they are known

Previously they were announced at the end of the time step, too late to
actually run the process_acknowledged hook any more.  This change makes
it possible to end ongoing slurs in the end of a repeat alternative
with <>) when they have been started with -\tweak to-barline ##t (

http://codereview.appspot.com/329880043


---

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] #5161 Announce slur ends when they are known

2017-07-24 Thread Auto mailings of changes to Lily Issues via Testlilyissues-auto 
- Description has changed:

Diff:







- **Needs**:  -->  
- **Type**: Enhancement --> Defect
- **Comment**:

Whenever I try actually using LilyPond for typesetting something of my own, I 
swear I have no idea how people can actually get anything done with it.



---

** [issues:#5161] Announce slur ends when they are known**

**Status:** Started
**Created:** Mon Jul 24, 2017 11:12 AM UTC by David Kastrup
**Last Updated:** Mon Jul 24, 2017 11:12 AM UTC
**Owner:** David Kastrup


Announce slur ends when they are known

Previously they were announced at the end of the time step, too late to
actually run the process_acknowledged hook any more.  This change makes
it possible to end ongoing slurs in the end of a repeat alternative
with <>) when they have been started with -\tweak to-barline ##t (

http://codereview.appspot.com/329880043


---

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

2017-06-30 Thread Auto mailings of changes to Lily Issues via Testlilyissues-auto 



---

** [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

2017-06-30 Thread Auto mailings of changes to Lily Issues via Testlilyissues-auto 
- **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

2017-07-01 Thread Auto mailings of changes to Lily Issues via Testlilyissues-auto 
- **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

2017-07-01 Thread Auto mailings of changes to Lily Issues via Testlilyissues-auto 
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] #5149 lilypond-manuals.css: Add a maximum width for manuals sidebar

2017-07-01 Thread Auto mailings of changes to Lily Issues via Testlilyissues-auto 
- **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] #5152 Doc: CG: Add guideline for use of 'CSS' prefix in commit messages

2017-07-04 Thread Auto mailings of changes to Lily Issues via Testlilyissues-auto 



---

** [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

2017-07-05 Thread Auto mailings of changes to Lily Issues via Testlilyissues-auto 
- 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

2017-07-05 Thread Auto mailings of changes to Lily Issues via Testlilyissues-auto 
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] #5168 Let arpeggio-bracket/slur depend on grob-property thickness

2017-07-28 Thread Auto mailings of changes to Lily Issues via Testlilyissues-auto 
Test-code:

~~~
{
  \override Arpeggio.thickness = 0.2
  \arpeggio
  \override Arpeggio.stencil = #ly:arpeggio::brew-chord-bracket
  \arpeggio
  \override Arpeggio.stencil = #ly:arpeggio::brew-chord-slur
  \arpeggio
}
~~~


---

** [issues:#5168] Let arpeggio-bracket/slur depend on grob-property thickness**

**Status:** Started
**Created:** Fri Jul 28, 2017 09:12 PM UTC by Thomas Morley
**Last Updated:** Fri Jul 28, 2017 09:12 PM UTC
**Owner:** Thomas Morley


Let arpeggio-bracket/slur depend on grob-property thickness

Before thickness based on line-thickness from layout

http://codereview.appspot.com/326970043


---

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] #5168 Let arpeggio-bracket/slur depend on grob-property thickness

2017-07-28 Thread Auto mailings of changes to Lily Issues via Testlilyissues-auto 



---

** [issues:#5168] Let arpeggio-bracket/slur depend on grob-property thickness**

**Status:** Started
**Created:** Fri Jul 28, 2017 09:12 PM UTC by Thomas Morley
**Last Updated:** Fri Jul 28, 2017 09:12 PM UTC
**Owner:** nobody


Let arpeggio-bracket/slur depend on grob-property thickness

Before thickness based on line-thickness from layout

http://codereview.appspot.com/326970043


---

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: #5169 Segfault after "cannot find line breaking that satisfies constraints"

2017-07-29 Thread Auto mailings of changes to Lily Issues via Testlilyissues-auto 
Why this hostility?

James is simply right.

Furthermore, you didn't report a problem, but opened a tracker issue. 
If you or someone else has problems tracking a file down to a minimal, even if 
the reason is running short of time, it woud have been appropriate to ask for 
help on the user- or probably the bug-list.



---

** [issues:#5169] Segfault after "cannot find line breaking that satisfies 
constraints"**

**Status:** New
**Created:** Sat Jul 29, 2017 07:40 AM UTC by Knut Petersen
**Last Updated:** Sat Jul 29, 2017 07:16 PM UTC
**Owner:** Knut Petersen
**Attachments:**

- 
[segfault.ly](https://sourceforge.net/p/testlilyissues/issues/5169/attachment/segfault.ly)
 (14.5 kB; text/x-lilypond)


Current master segfaults on an openSuSE Tumbleweed system if a global staff 
size equal or greater 14.5 is used. It also segfaulted with git master about 
half a year ago, but I had/have no time to investigate the problem. Maybe 
someone is interested.


---

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

2017-07-30 Thread Auto mailings of changes to Lily Issues via Testlilyissues-auto 
- **status**: Fixed --> Verified



---

** [issues:#5149] lilypond-manuals.css: Add a maximum width for manuals 
sidebar**

**Status:** Verified
**Labels:** Fixed_2_19_64 
**Created:** Sat Jun 17, 2017 09:57 PM UTC by Paul Morris
**Last Updated:** Sat Jul 01, 2017 02:53 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] #5166 Doc: Delete note for svg backend which become unnecessary

2017-07-28 Thread Auto mailings of changes to Lily Issues via Testlilyissues-auto 
- Description has changed:

Diff:







- **Needs**:  -->  
- **Patch**: new --> review
- **Type**: Enhancement --> Documentation
- **Comment**:

Passes make, make check and a full make doc.



---

** [issues:#5166] Doc: Delete note for svg backend which become unnecessary**

**Status:** Started
**Created:** Fri Jul 28, 2017 04:15 PM UTC by Masamichi Hosoda
**Last Updated:** Fri Jul 28, 2017 04:15 PM UTC
**Owner:** Masamichi Hosoda


Doc: Delete note for svg backend which become unnecessary

  Issue 4776 changed default fonts of svg backend.
  This commit deletes note which become unnecessary.

Doc: Update default font description

  Issue 4332, 4441, 4544, 4552, 4776, 4987 etc. changed default fonts.
  This commit updates the document.

http://codereview.appspot.com/323350043


---

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] #5167 Allow defining markup commands in LilyPond syntax

2017-07-28 Thread Auto mailings of changes to Lily Issues via Testlilyissues-auto 



---

** [issues:#5167] Allow defining markup commands in LilyPond syntax**

**Status:** Started
**Created:** Fri Jul 28, 2017 06:55 PM UTC by David Kastrup
**Last Updated:** Fri Jul 28, 2017 06:55 PM UTC
**Owner:** nobody


Allow defining markup commands in LilyPond syntax

This works with assignments of the form

\markup with-red = \markup \with-color #red \etc

or similar.  The resulting definition (in addition to being available
as \with-red command inside of markups) can be used with the `markup'
macro and also gets a `make-with-red-markup' convenience function.


Also contains commits:

markup-partial regtest: use \markup function assignment



Changes: show \markup xxx = ... \etc assignments



Parser: let `assignment_id' return a symbol

That's actually what's needed rather than a string.



Split off `markup-lambda' from `define-markup-command'

Also markup-list-lambda from define-markup-list-command.



Let `make-markup' fetch the signature itself

Also don't export it from markup-macros.scm: it is an internal function.



Reorganize markup commands to use object properties

This loosens the ties between the actual markup function and its
calling methods.

http://codereview.appspot.com/324140043


---

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] #5169 Segfault after "cannot find line breaking that satisfies constraints"

2017-07-29 Thread Auto mailings of changes to Lily Issues via Testlilyissues-auto 
Well, in this particular case I have to say that the situation at a segfault 
makes a minimal example often less necessary for analysis than in other cases 
since the debugger will provide a lot of information.  However, once one needs 
to work with reverse execution, it's important that the segfault occurs as fast 
as possible since "reverse execution" is actually tracing with full recording 
in order to be able to "step backward".  So even in the segfault case, an 
example with minimal running time (rather than minimal source size though both 
are usually correlated) is helpful.


---

** [issues:#5169] Segfault after "cannot find line breaking that satisfies 
constraints"**

**Status:** New
**Created:** Sat Jul 29, 2017 07:40 AM UTC by Knut Petersen
**Last Updated:** Sat Jul 29, 2017 07:16 PM UTC
**Owner:** Knut Petersen
**Attachments:**

- 
[segfault.ly](https://sourceforge.net/p/testlilyissues/issues/5169/attachment/segfault.ly)
 (14.5 kB; text/x-lilypond)


Current master segfaults on an openSuSE Tumbleweed system if a global staff 
size equal or greater 14.5 is used. It also segfaulted with git master about 
half a year ago, but I had/have no time to investigate the problem. Maybe 
someone is interested.


---

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] #5166 Doc: Delete note for svg backend which become unnecessary

2017-07-28 Thread Auto mailings of changes to Lily Issues via Testlilyissues-auto 



---

** [issues:#5166] Doc: Delete note for svg backend which become unnecessary**

**Status:** Started
**Created:** Fri Jul 28, 2017 04:15 PM UTC by Masamichi Hosoda
**Last Updated:** Fri Jul 28, 2017 04:15 PM UTC
**Owner:** nobody


Doc: Delete note for svg backend which become unnecessary

  Issue 4776 changed default fonts of svg backend.
  This commit deletes note which become unnecessary.

Doc: Update default font description

  Issue 4332, 4441, 4544, 4552, 4776, 4987 etc. changed default fonts.
  This commit updates the document.

http://codereview.appspot.com/323350043


---

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] #5164 Doc: Add usage of OpenType font feature

2017-08-01 Thread Auto mailings of changes to Lily Issues via Testlilyissues-auto 
- **summary**: Add usage of OpenType font feature to the documents --> Doc: Add 
usage of OpenType font feature
- **Needs**:  -->  
- **Type**:  -->  



---

** [issues:#5164] Doc: Add usage of OpenType font feature**

**Status:** Started
**Created:** Wed Jul 26, 2017 01:24 PM UTC by Masamichi Hosoda
**Last Updated:** Tue Aug 01, 2017 03:05 PM UTC
**Owner:** Masamichi Hosoda


Add usage of OpenType font feature to the documents

This commit adds the usage of OpenType font feature
added in Issue 1388 to the document.

http://codereview.appspot.com/328140043


---

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] #5164 Add usage of OpenType font feature to the documents

2017-08-01 Thread Auto mailings of changes to Lily Issues via Testlilyissues-auto 
Add notes and identification way

http://codereview.appspot.com/328140043


---

** [issues:#5164] Add usage of OpenType font feature to the documents**

**Status:** Started
**Created:** Wed Jul 26, 2017 01:24 PM UTC by Masamichi Hosoda
**Last Updated:** Tue Aug 01, 2017 03:05 PM UTC
**Owner:** Masamichi Hosoda


Add usage of OpenType font feature to the documents

This commit adds the usage of OpenType font feature
added in Issue 1388 to the document.

http://codereview.appspot.com/328140043


---

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] #5166 Doc: Delete note for svg backend which become unnecessary

2017-08-01 Thread Auto mailings of changes to Lily Issues via Testlilyissues-auto 
- **status**: Started --> Fixed
- **Patch**: push -->  
- **Comment**:

I've pushed to staging.

commit 97956152eba4292886a47c74b45bc6be5a0349e8
Date:   Sat Jul 29 01:11:05 2017 +0900
Issue 5166/2: Doc: Delete note for svg backend which become unnecessary

commit f40aa7dc7410285fc904612941b1909144c01c2f
Date:   Sat Jul 29 01:03:17 2017 +0900
Issue 5166/1: Doc: Update default font description



---

** [issues:#5166] Doc: Delete note for svg backend which become unnecessary**

**Status:** Fixed
**Created:** Fri Jul 28, 2017 04:15 PM UTC by Masamichi Hosoda
**Last Updated:** Tue Aug 01, 2017 08:09 AM UTC
**Owner:** Masamichi Hosoda


Doc: Delete note for svg backend which become unnecessary

  Issue 4776 changed default fonts of svg backend.
  This commit deletes note which become unnecessary.

Doc: Update default font description

  Issue 4332, 4441, 4544, 4552, 4776, 4987 etc. changed default fonts.
  This commit updates the document.

http://codereview.appspot.com/323350043


---

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] #5163 Update URW++ OTF files

2017-08-01 Thread Auto mailings of changes to Lily Issues via Testlilyissues-auto 
May I push this to staging?
Should I wait for 2.21?


---

** [issues:#5163] Update URW++ OTF files**

**Status:** Started
**Created:** Wed Jul 26, 2017 11:56 AM UTC by Masamichi Hosoda
**Last Updated:** Tue Aug 01, 2017 08:09 AM UTC
**Owner:** Masamichi Hosoda


Update URW++ OTF files

URW++ has been released URW++ core 35 fonts 2017-07-20.
It has some bugfixes.

This commit makes configure script can find latest URW++ OTF files (2017-07-20).
http://git.ghostscript.com/?p=urw-core35-fonts.git;a=tree;hb=1f28a6fcd2176256a995db907d9ffe6e1b9b83e9

It also can find previously released files (2017-05 and 2016).
http://git.ghostscript.com/?p=urw-core35-fonts.git;a=tree;hb=e3c665a8a3df36a54b22ad0b6176283db5310f97
http://git.ghostscript.com/?p=urw-core35-fonts.git;a=tree;hb=79bcdfb34fbce12b592cce389fa7a19da6b5b018

http://codereview.appspot.com/321350043


---

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: #5163 Update URW++ OTF files

2017-08-01 Thread Auto mailings of changes to Lily Issues via Testlilyissues-auto 
For better or worse, there is little point in the stable release not being able 
to find fonts.  There will also have to be some prereleases anyway.  So I think 
this should be pushed.


---

** [issues:#5163] Update URW++ OTF files**

**Status:** Started
**Created:** Wed Jul 26, 2017 11:56 AM UTC by Masamichi Hosoda
**Last Updated:** Tue Aug 01, 2017 12:28 PM UTC
**Owner:** Masamichi Hosoda


Update URW++ OTF files

URW++ has been released URW++ core 35 fonts 2017-07-20.
It has some bugfixes.

This commit makes configure script can find latest URW++ OTF files (2017-07-20).
http://git.ghostscript.com/?p=urw-core35-fonts.git;a=tree;hb=1f28a6fcd2176256a995db907d9ffe6e1b9b83e9

It also can find previously released files (2017-05 and 2016).
http://git.ghostscript.com/?p=urw-core35-fonts.git;a=tree;hb=e3c665a8a3df36a54b22ad0b6176283db5310f97
http://git.ghostscript.com/?p=urw-core35-fonts.git;a=tree;hb=79bcdfb34fbce12b592cce389fa7a19da6b5b018

http://codereview.appspot.com/321350043


---

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] #5163 Update URW++ OTF files

2017-08-01 Thread Auto mailings of changes to Lily Issues via Testlilyissues-auto 
- **status**: Started --> Fixed
- **Patch**: push -->  
- **Comment**:

I've pushed to staging.

commit 0e23f12caa09cd3848076be24a9ed8920d2d678d
Date:   Wed Jul 26 20:53:58 2017 +0900
Issue 5163: Update URW++ OTF files

Thank you.



---

** [issues:#5163] Update URW++ OTF files**

**Status:** Fixed
**Created:** Wed Jul 26, 2017 11:56 AM UTC by Masamichi Hosoda
**Last Updated:** Tue Aug 01, 2017 12:28 PM UTC
**Owner:** Masamichi Hosoda


Update URW++ OTF files

URW++ has been released URW++ core 35 fonts 2017-07-20.
It has some bugfixes.

This commit makes configure script can find latest URW++ OTF files (2017-07-20).
http://git.ghostscript.com/?p=urw-core35-fonts.git;a=tree;hb=1f28a6fcd2176256a995db907d9ffe6e1b9b83e9

It also can find previously released files (2017-05 and 2016).
http://git.ghostscript.com/?p=urw-core35-fonts.git;a=tree;hb=e3c665a8a3df36a54b22ad0b6176283db5310f97
http://git.ghostscript.com/?p=urw-core35-fonts.git;a=tree;hb=79bcdfb34fbce12b592cce389fa7a19da6b5b018

http://codereview.appspot.com/321350043


---

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] #5168 Let arpeggio-bracket/slur depend on grob-property thickness

2017-08-01 Thread Auto mailings of changes to Lily Issues via Testlilyissues-auto 
let arpeggio-slur rely on grob-line-thickness as well

http://codereview.appspot.com/326970043


---

** [issues:#5168] Let arpeggio-bracket/slur depend on grob-property thickness**

**Status:** Started
**Created:** Fri Jul 28, 2017 09:12 PM UTC by Thomas Morley
**Last Updated:** Tue Aug 01, 2017 10:54 AM UTC
**Owner:** Thomas Morley


Let arpeggio-bracket/slur depend on grob-property thickness

Before thickness based on line-thickness from layout

http://codereview.appspot.com/326970043


---

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] #5170 Output better message for wrong argument of dash-definiton

2017-08-01 Thread Auto mailings of changes to Lily Issues via Testlilyissues-auto 



---

** [issues:#5170] Output better message for wrong argument of dash-definiton**

**Status:** Started
**Created:** Tue Aug 01, 2017 05:15 PM UTC by Thomas Morley
**Last Updated:** Tue Aug 01, 2017 05:15 PM UTC
**Owner:** nobody


Output better message for wrong argument of dash-definiton

Previously an argument like '(0 1.0 0.5 0.5) passed the
pair?-typecheck, segfaulting later.
Thus a new predicate, list-of-lists? is introduced.

http://codereview.appspot.com/321400043


---

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] #5168 Let arpeggio-bracket/slur depend on grob-property thickness

2017-08-02 Thread Auto mailings of changes to Lily Issues via Testlilyissues-auto 
- **Needs**:  -->  
- **Patch**: new --> review
- **Type**:  --> Enhancement
- **Comment**:

Passes make, make check and a full make doc.



---

** [issues:#5168] Let arpeggio-bracket/slur depend on grob-property thickness**

**Status:** Started
**Created:** Fri Jul 28, 2017 09:12 PM UTC by Thomas Morley
**Last Updated:** Tue Aug 01, 2017 10:54 AM UTC
**Owner:** Thomas Morley


Let arpeggio-bracket/slur depend on grob-property thickness

Before thickness based on line-thickness from layout

http://codereview.appspot.com/326970043


---

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] #5170 Output better message for wrong argument of dash-definiton

2017-08-02 Thread Auto mailings of changes to Lily Issues via Testlilyissues-auto 
- Description has changed:

Diff:







- **Needs**:  -->  
- **Patch**: new --> review
- **Comment**:

Passes make, make check and a full make doc.



---

** [issues:#5170] Output better message for wrong argument of dash-definiton**

**Status:** Started
**Created:** Tue Aug 01, 2017 05:15 PM UTC by Thomas Morley
**Last Updated:** Tue Aug 01, 2017 05:15 PM UTC
**Owner:** Thomas Morley


Output better message for wrong argument of dash-definiton

Previously an argument like '(0 1.0 0.5 0.5) passed the
pair?-typecheck, segfaulting later.
Thus a new predicate, list-of-lists? is introduced.

http://codereview.appspot.com/321400043


---

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] #5169 Segfault after "cannot find line breaking that satisfies constraints"

2017-07-29 Thread Auto mailings of changes to Lily Issues via Testlilyissues-auto 



---

** [issues:#5169] Segfault after "cannot find line breaking that satisfies 
constraints"**

**Status:** New
**Created:** Sat Jul 29, 2017 07:40 AM UTC by Knut Petersen
**Last Updated:** Sat Jul 29, 2017 07:40 AM UTC
**Owner:** Knut Petersen
**Attachments:**

- 
[segfault.ly](https://sourceforge.net/p/testlilyissues/issues/5169/attachment/segfault.ly)
 (14.5 kB; text/x-lilypond)


Current master segfaults on an openSuSE Tumbleweed system if a global staff 
size equal or greater 14.5 is used. It also segfaulted with git master about 
half a year ago, but I had/have no time to investigate the problem. Maybe 
someone is interested.


---

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] #5168 Let arpeggio-bracket/slur depend on grob-property thickness

2017-07-29 Thread Auto mailings of changes to Lily Issues via Testlilyissues-auto 
- Description has changed:

Diff:







- **Needs**:  -->  
- **Patch**: new --> needs_work
- **Comment**:

Due to review I set this on needs-work for now



---

** [issues:#5168] Let arpeggio-bracket/slur depend on grob-property thickness**

**Status:** Started
**Created:** Fri Jul 28, 2017 09:12 PM UTC by Thomas Morley
**Last Updated:** Fri Jul 28, 2017 09:14 PM UTC
**Owner:** Thomas Morley


Let arpeggio-bracket/slur depend on grob-property thickness

Before thickness based on line-thickness from layout

http://codereview.appspot.com/326970043


---

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

2017-06-08 Thread Auto mailings of changes to Lily Issues via Testlilyissues-auto 
- **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] #5145 Allow $... to specify a markup command

2017-06-12 Thread Auto mailings of changes to Lily Issues via Testlilyissues-auto 



---

** [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] #5141 Fix typos in \offset documentation

2017-06-09 Thread Auto mailings of changes to Lily Issues via Testlilyissues-auto 
- 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] #5146 Don't use \line in the implementation of \concat

2017-06-12 Thread Auto mailings of changes to Lily Issues via Testlilyissues-auto 



---

** [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

2017-06-12 Thread Auto mailings of changes to Lily Issues via Testlilyissues-auto 
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

2017-06-12 Thread Auto mailings of changes to Lily Issues via Testlilyissues-auto 
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] #1388 Support OpenType font features

2017-06-19 Thread Auto mailings of changes to Lily Issues via Testlilyissues-auto 
- **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

2017-06-19 Thread Auto mailings of changes to Lily Issues via Testlilyissues-auto 
- **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

2017-06-22 Thread Auto mailings of changes to Lily Issues via Testlilyissues-auto 



---

** [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] #5150 Update Finnendahl testimony info

2017-06-22 Thread Auto mailings of changes to Lily Issues via Testlilyissues-auto 
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] #5149 lilypond-manuals.css: Add a maximum width for manuals sidebar

2017-06-25 Thread Auto mailings of changes to Lily Issues via Testlilyissues-auto 
- 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

2017-06-25 Thread Auto mailings of changes to Lily Issues via Testlilyissues-auto 
- 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

2017-06-25 Thread Auto mailings of changes to Lily Issues via Testlilyissues-auto 
- **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] #1388 Support OpenType font features

2017-06-08 Thread Auto mailings of changes to Lily Issues via Testlilyissues-auto 
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] #5140 Fix granados example

2017-06-06 Thread Auto mailings of changes to Lily Issues via Testlilyissues-auto 
- **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

2017-06-07 Thread Auto mailings of changes to Lily Issues via Testlilyissues-auto 



---

** [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] #5146 Don't use \line in the implementation of \concat

2017-06-13 Thread Auto mailings of changes to Lily Issues via Testlilyissues-auto 
- 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] #5145 Allow $... to specify a markup command

2017-06-13 Thread Auto mailings of changes to Lily Issues via Testlilyissues-auto 
- 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] #5147 Add whether to use OTF feature depending on Pango version

2017-06-13 Thread Auto mailings of changes to Lily Issues via Testlilyissues-auto 
- 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] #1388 Support OpenType font features

2017-06-13 Thread Auto mailings of changes to Lily Issues via Testlilyissues-auto 
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] #5147 Add whether to use OTF feature depending on Pango version

2017-06-13 Thread Auto mailings of changes to Lily Issues via Testlilyissues-auto 
- 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] #5147 Add whether to use OTF feature depending on Pango version

2017-06-13 Thread Auto mailings of changes to Lily Issues via Testlilyissues-auto 



---

** [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] #1228 merge simultaneous rests of the same duration

2017-06-16 Thread Auto mailings of changes to Lily Issues via Testlilyissues-auto 
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+=Search!=lilypond-user](http://lists.gnu.org/archive/cgi-bin/namazu.cgi?query=Merging+rests+=Search!=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

2017-06-16 Thread Auto mailings of changes to Lily Issues via Testlilyissues-auto 
- **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+=Search!=lilypond-user](http://lists.gnu.org/archive/cgi-bin/namazu.cgi?query=Merging+rests+=Search!=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] #5146 Don't use \line in the implementation of \concat

2017-06-16 Thread Auto mailings of changes to Lily Issues via Testlilyissues-auto 
- **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] #5147 Add whether to use OTF feature depending on Pango version

2017-06-16 Thread Auto mailings of changes to Lily Issues via Testlilyissues-auto 
- **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

2017-06-16 Thread Auto mailings of changes to Lily Issues via Testlilyissues-auto 
- **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] #5144 lilypond-manuals.css: edit color scheme and some spacing

2017-06-16 Thread Auto mailings of changes to Lily Issues via Testlilyissues-auto 
- **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] #5141 Fix typos in \offset documentation

2017-06-17 Thread Auto mailings of changes to Lily Issues via Testlilyissues-auto 
- **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] #5145 Allow $... to specify a markup command

2017-06-17 Thread Auto mailings of changes to Lily Issues via Testlilyissues-auto 
- **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

2017-06-17 Thread Auto mailings of changes to Lily Issues via Testlilyissues-auto 
- **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] #5149 lilypond-manuals.css: Add a maximum width for manuals sidebar

2017-06-17 Thread Auto mailings of changes to Lily Issues via Testlilyissues-auto 
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] #5149 lilypond-manuals.css: Add a maximum width for manuals sidebar

2017-06-17 Thread Auto mailings of changes to Lily Issues via Testlilyissues-auto 



---

** [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] #5144 lilypond-manuals.css: edit color scheme and some spacing

2017-06-17 Thread Auto mailings of changes to Lily Issues via Testlilyissues-auto 
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] #5144 lilypond-manuals.css: edit color scheme and some spacing

2017-06-10 Thread Auto mailings of changes to Lily Issues via Testlilyissues-auto 



---

** [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] #5143 [partcombine] partcombine can't handle simultaneous hairpins

2017-06-09 Thread Auto mailings of changes to Lily Issues via Testlilyissues-auto 



---

** [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] #5142 partcombine can't handle simultaneous hairpins

2017-06-09 Thread Auto mailings of changes to Lily Issues via Testlilyissues-auto 



---

** [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] #5144 lilypond-manuals.css: edit color scheme and some spacing

2017-06-10 Thread Auto mailings of changes to Lily Issues via Testlilyissues-auto 
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] #1228 merge simultaneous rests of the same duration

2017-06-11 Thread Auto mailings of changes to Lily Issues via Testlilyissues-auto 
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+=Search!=lilypond-user](http://lists.gnu.org/archive/cgi-bin/namazu.cgi?query=Merging+rests+=Search!=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

2017-06-12 Thread Auto mailings of changes to Lily Issues via Testlilyissues-auto 
- **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+=Search!=lilypond-user](http://lists.gnu.org/archive/cgi-bin/namazu.cgi?query=Merging+rests+=Search!=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

2017-06-13 Thread Auto mailings of changes to Lily Issues via Testlilyissues-auto 
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+=Search!=lilypond-user](http://lists.gnu.org/archive/cgi-bin/namazu.cgi?query=Merging+rests+=Search!=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

2017-06-13 Thread Auto mailings of changes to Lily Issues via Testlilyissues-auto 
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] #5147 Add whether to use OTF feature depending on Pango version

2017-06-14 Thread Auto mailings of changes to Lily Issues via Testlilyissues-auto 
- **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] #5141 Fix typos in \offset documentation

2017-06-14 Thread Auto mailings of changes to Lily Issues via Testlilyissues-auto 
- **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] #5145 Allow $... to specify a markup command

2017-06-14 Thread Auto mailings of changes to Lily Issues via Testlilyissues-auto 
- **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] #5144 lilypond-manuals.css: edit color scheme and some spacing

2017-06-14 Thread Auto mailings of changes to Lily Issues via Testlilyissues-auto 
- **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

2017-06-14 Thread Auto mailings of changes to Lily Issues via Testlilyissues-auto 
- **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] #5148 Various chain-assoc-get -> #:properties

2017-06-16 Thread Auto mailings of changes to Lily Issues via Testlilyissues-auto 



---

** [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] #1388 Support OpenType font features

2017-06-15 Thread Auto mailings of changes to Lily Issues via Testlilyissues-auto 
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

2017-06-16 Thread Auto mailings of changes to Lily Issues via Testlilyissues-auto 
- **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

2017-06-16 Thread Auto mailings of changes to Lily Issues via Testlilyissues-auto 
- **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

2017-06-16 Thread Auto mailings of changes to Lily Issues via Testlilyissues-auto 
- 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] #5148 Various chain-assoc-get -> #:properties

2017-06-16 Thread Auto mailings of changes to Lily Issues via Testlilyissues-auto 
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] #5147 Add whether to use OTF feature depending on Pango version

2017-06-19 Thread Auto mailings of changes to Lily Issues via Testlilyissues-auto 
- **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

2017-06-19 Thread Auto mailings of changes to Lily Issues via Testlilyissues-auto 
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

<    1   2   3   4   5   6   7   8   9   10   >