How to create a restricted symbols context property

2016-01-18 Thread Urs Liska
I have created a new boolean context property by - adding an entry in define-context-properties.scm - setting the default in engraver-init.ly - retrieving it in a class's (Beaming_option) from_context method However, I would like to add another context property (and modify the added one) from bool

Re: Add ly:one-line-auto-height-breaking (issue 284240043 by paulwmor...@gmail.com)

2016-01-18 Thread git
This is a great enhancement. I commented on one typo, but I saw two issues (I'll add images to the lilypond-devel copy of this message as soon as it pops up): 1) In one file the instrument name was severely truncated 2) In another file with three staves (staff + piano staff) the vertical spacin

Re: Add ly:one-line-auto-height-breaking (issue 284240043 by paulwmor...@gmail.com)

2016-01-18 Thread Urs Liska
Am 18.01.2016 um 13:43 schrieb g...@ursliska.de: > This is a great enhancement. > > I commented on one typo, but I saw two issues (I'll add images to the > lilypond-devel copy of this message as soon as it pops up): > > 1) > In one file the instrument name was severely truncated (BeiMannern ...

Re: How to create a restricted symbols context property

2016-01-18 Thread Urs Liska
Am 18.01.2016 um 11:31 schrieb Urs Liska: > And how do I retrieve the value of the property in a C++ class? > I see this in bar-number-engraver.cc: > > SCM alternative_style = get_property > ("alternativeNumberingStyle"); > string text_tag = ""; > if (scm_is_eq (alte

Re: Add ly:one-line-auto-height-breaking (issue 284240043 by paulwmor...@gmail.com)

2016-01-18 Thread Paul Morris
> On Jan 18, 2016, at 7:43 AM, g...@ursliska.de wrote: > > This is a great enhancement. Thanks Urs. > I commented on one typo, but I saw two issues (I'll add images to the > lilypond-devel copy of this message as soon as it pops up): > > 1) > In one file the instrument name was severely truncat

Re: Add ly:one-line-auto-height-breaking (issue 284240043 by paulwmor...@gmail.com)

2016-01-18 Thread Urs Liska
Am 18.01.2016 um 16:17 schrieb Paul Morris: >> On Jan 18, 2016, at 7:43 AM, g...@ursliska.de wrote: >> >> This is a great enhancement. > Thanks Urs. > >> I commented on one typo, but I saw two issues (I'll add images to the >> lilypond-devel copy of this message as soon as it pops up): >> >> 1) >

PATCHES: Countdown for January 21st

2016-01-18 Thread James
Hello, Here is the current patch countdown list. The next countdown will be on January the 21st. A quick synopsis of all patches currently in the review process can be found here: http://philholmes.net/lilypond/allura/ __ Push: 4742 Only \propertyTweak rather than \tweak can be appl

Re: Add ly:one-line-auto-height-breaking (issue 284240043 by paulwmor...@gmail.com)

2016-01-18 Thread Urs Liska
Am 18.01.2016 um 16:35 schrieb Urs Liska: >>> 2) >>> >> In another file with three staves (staff + piano staff) the vertical >>> >> spacing of the systems is unusably large. >> > How do these compare with ly:one-line-breaking ? (I might try this myself >> > but I don’t have the .ly files you’re

OpenType Features

2016-01-18 Thread Jay Anderson
I'm interested in seeing what it would take to add OpenType features -- specifically old style number figures (onum) and small caps (smcp). First issue: It appears that lilypond is dependent on pango 1.6 (pangoft2 - required 1.6.0, INSTALL.txt says pango 1.12 or newer so I'm not totally sure what

Re: OpenType Features

2016-01-18 Thread James
Hello Jay, On 18/01/16 16:59, Jay Anderson wrote: > I'm interested in seeing what it would take to add OpenType features > -- specifically old style number figures (onum) and small caps (smcp). > > First issue: It appears that lilypond is dependent on pango 1.6 > (pangoft2 - required 1.6.0, INSTAL

Re: How to create a restricted symbols context property

2016-01-18 Thread Urs Liska
Am 18.01.2016 um 11:31 schrieb Urs Liska: > I have created a new boolean context property by > - adding an entry in define-context-properties.scm > - setting the default in engraver-init.ly > - retrieving it in a class's (Beaming_option) from_context method > > However, I would like to add anothe

Re: OpenType Features

2016-01-18 Thread Simon Albrecht
On 18.01.2016 17:59, Jay Anderson wrote: This is the lilypond issue: https://code.google.com/p/lilypond/issues/detail?id=1388 (What's the new issue location? I couldn't find it in my quick searching and lilypond still points to google code (

Re: OpenType Features

2016-01-18 Thread Jay Anderson
On Mon, Jan 18, 2016 at 9:59 AM, Jay Anderson wrote: > First issue: It appears that lilypond is dependent on pango 1.6 > (pangoft2 - required 1.6.0, INSTALL.txt says pango 1.12 or newer so > I'm not totally sure what to believe.). OpenType features were added > in pango 1.18 (assuming I'm reading

Re: OpenType Features

2016-01-18 Thread James
Hello On 18/01/16 17:18, Simon Albrecht wrote: > On 18.01.2016 17:59, Jay Anderson wrote: >> This is the lilypond issue: >> https://code.google.com/p/lilypond/issues/detail?id=1388 (What's the >> new issue location? > > > >> I couldn't find it in

Trivial change to Website URL pushed without Issue

2016-01-18 Thread James
Hello, I made a change to the URL listed in the Website's itexi file from the old Google Code URL to the current one we use at Sourceforge.net as it was still being referenced in the 'bug reports' part of the website. I have pushed this trivial change without an issue and so I am hoping that is O

Re: OpenType Features

2016-01-18 Thread Simon Albrecht
On 18.01.2016 18:40, James wrote: I'll make a patch Good! TIA, Simon ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel

Re: How to create a restricted symbols context property

2016-01-18 Thread David Kastrup
Urs Liska writes: > Am 18.01.2016 um 11:31 schrieb Urs Liska: >> I have created a new boolean context property by >> - adding an entry in define-context-properties.scm >> - setting the default in engraver-init.ly >> - retrieving it in a class's (Beaming_option) from_context method >> >> However,

ly:one-page-breaking (was: ly:one-line-breaking)

2016-01-18 Thread Paul Morris
> On Jan 9, 2016, at 1:30 PM, Richard Shann wrote: > > I was wondering if it would be possible to develop a variant of "all on > one line", namely "all on one page", where the page height would be > automatically adjusted to fit the music, leaving the width as set. I’m glad to report that I’ve m

Re: Add ly:one-line-auto-height-breaking (issue 284240043 by paulwmor...@gmail.com)

2016-01-18 Thread paulwmorris
A few doc edits. -Paul https://codereview.appspot.com/284240043/diff/1/Documentation/notation/spacing.itely File Documentation/notation/spacing.itely (right): https://codereview.appspot.com/284240043/diff/1/Documentation/notation/spacing.itely#newcode895 Documentation/notation/spacing.itely:895

ly:one-page-breaking (was: ly:one-line-breaking)

2016-01-18 Thread Paul Morris
> On Jan 9, 2016, at 1:30 PM, Richard Shann wrote: > > I was wondering if it would be possible to develop a variant of "all on > one line", namely "all on one page", where the page height would be > automatically adjusted to fit the music, leaving the width as set. I’m glad to report that I’ve m

Re: ly:one-page-breaking (was: ly:one-line-breaking)

2016-01-18 Thread Paul Morris
> On Jan 18, 2016, at 7:09 PM, Paul Morris wrote: > > (Also, I now see how to improve the ly:one-line-auto-height code to avoid > some of the unintuitive results related to bottom-margin and > top-system-spacing. So a new patch set for that is on the way, when I can > get to it...) Actually