Re: Issue 3945: fix (De)crescendo with unspecified starting volume in MIDI (issue 294700043 by nine.fierce.ball...@gmail.com)

2016-06-05 Thread nine . fierce . ballads
HT, thanks for your review and your detailed response. (or in some cases move the Dynamic_performer from the Voice context to the Staff context) I understand what you are saying. I often use the part combiner, which lays waste to the organization of musical parts within Lilypond Voice context

Re: Issue 3945: fix (De)crescendo with unspecified starting volume in MIDI (issue 294700043 by nine.fierce.ball...@gmail.com)

2016-06-05 Thread ht . lilypond . development
I understand from this patch that you are in favor of removing the warning altogether, which - I agree - works very inconsistently in current versions (as demonstrated by the examples in the issues about the warning). As you yourself have noted on a discussion attached to issue 4104, however, the

Re: Issue 4789: Note_performer: articulate events (issue 298330043 by d...@gnu.org)

2016-06-05 Thread ht . lilypond . development
This looks great! Even though this question has little relevance to these code changes, I can't resist asking whether you might have ideas about the best way to fix the "reverse" problem of ties attached to *individual notes of a chord* ending up ignored when processing articulations using the ar

Re: make calc-blot from bar-line.scm public (issue 299250044 by thomasmorle...@gmail.com)

2016-06-05 Thread dak
On 2016/06/05 17:27:15, thomasmorley651 wrote: I expected this one to be a real nobrainer... Well, sorry for that. Anyway, On 2016/06/05 15:51:25, dak wrote: > https://codereview.appspot.com/299250044/diff/1/scm/bar-line.scm > File scm/bar-line.scm (right): > > https://codereview.appspot.

Re: make calc-blot from bar-line.scm public (issue 299250044 by thomasmorle...@gmail.com)

2016-06-05 Thread thomasmorley65
I expected this one to be a real nobrainer... Anyway, On 2016/06/05 15:51:25, dak wrote: https://codereview.appspot.com/299250044/diff/1/scm/bar-line.scm File scm/bar-line.scm (right): https://codereview.appspot.com/299250044/diff/1/scm/bar-line.scm#newcode30 scm/bar-line.scm:30: (define-pu

Re: make doc still fails - problem with lilypond-book - was: Still cannot make doc

2016-06-05 Thread Werner LEMBERG
> I've tried some Japanese fonts with `-dgs-load-fonts' option. [...] > > So most Japanese fonts can not be used with `-dgs-load-fonts' > option. Any idea why this is so? Could you contact the gs people by filing a bug report so that we get an explanation? Werner ___

Re: make calc-blot from bar-line.scm public (issue 299250044 by thomasmorle...@gmail.com)

2016-06-05 Thread dak
https://codereview.appspot.com/299250044/diff/1/scm/bar-line.scm File scm/bar-line.scm (right): https://codereview.appspot.com/299250044/diff/1/scm/bar-line.scm#newcode30 scm/bar-line.scm:30: (define-public (calc-blot thickness extent grob) For a public function, the name is awful. When made pu

make calc-blot from bar-line.scm public (issue 299250044 by thomasmorle...@gmail.com)

2016-06-05 Thread thomasmorley65
Reviewers: , Description: make calc-blot from bar-line.scm public To facilitate defining custom-bar-lines using ly:round-filled-box Please review this at https://codereview.appspot.com/299250044/ Affected files (+1, -1 lines): M scm/bar-line.scm Index: scm/bar-line.scm diff --git a/scm/bar

Re: make doc still fails - problem with lilypond-book - was: Still cannot make doc

2016-06-05 Thread Masamichi Hosoda
>>> In addition, all fonts of the above without `-dgs-load-fonts' option are >>> fine. >>> I suggest removing `-dgs-load-fonts' option from lilypond-book. >>> I think that `--bigpdfs' option is more suitable than >>> `-dgs-load-fonts'. >> >> Either make for particularly large PDF files, don't the

Re: Issue 3945: fix (De)crescendo with unspecified starting volume in MIDI (issue 294700043 by nine.fierce.ball...@gmail.com)

2016-06-05 Thread Graham King
On Sat, 2016-06-04 at 14:16 -0700, nine.fierce.ball...@gmail.com wrote: > https://codereview.appspot.com/294700043/ > >From the bug tracker: In order to avoid the midi-warning a workaround would be to specify the starting volume explicitly and hide or omit the Dy

Re: make doc still fails - problem with lilypond-book - was: Still cannot make doc

2016-06-05 Thread Masamichi Hosoda
>> In addition, all fonts of the above without `-dgs-load-fonts' option are >> fine. >> I suggest removing `-dgs-load-fonts' option from lilypond-book. >> I think that `--bigpdfs' option is more suitable than >> `-dgs-load-fonts'. > > Either make for particularly large PDF files, don't they? If

Re: make doc still fails - problem with lilypond-book - was: Still cannot make doc

2016-06-05 Thread David Kastrup
Masamichi Hosoda writes: > In addition, all fonts of the above without `-dgs-load-fonts' option are fine. > I suggest removing `-dgs-load-fonts' option from lilypond-book. > I think that `--bigpdfs' option is more suitable than > `-dgs-load-fonts'. Either make for particularly large PDF files, d

Re: make doc still fails - problem with lilypond-book - was: Still cannot make doc

2016-06-05 Thread Masamichi Hosoda
> As of > http://www.mail-archive.com/bug-lilypond@gnu.org/msg40846.html > I had uninstalled Noto and instead installed IPA fonts _and_ IPAex fonts. > After uninstalling IPAex fonts - first the test-case worked and now I > have success on a full `make doc'. It seems that fonts-ipaexfont-{mincho|go

Re: broken doc build (orchestra.ly)

2016-06-05 Thread David Kastrup
Knut Petersen writes: > "make doc" succeeds again, at least here. > > [newer versions]: make doc succeeds > dbaf1e56e37be0e204231c5bf1adcb14bd8ac3b8: fixes "make doc" failure here Ugh, I forgot to make this a merge commit. The preceding commit does not compile on its own. Let's hope that this