On 2016-12-14 19:46, Knut Petersen wrote:
Am 14.12.2016 um 18:03 schrieb Simon Albrecht:
On 14.12.2016 14:54, Knut Petersen wrote:
With a music function \autoextenders that adds extender events to
every syllable you
- can be sure never to forget extenders,
- can be sure never to generate too sh
On 2016-12-14 23:13, thomasmorle...@gmail.com wrote:
Worth an entry in changes?
Maybe. Doesn't need a lot, I guess; something like
"Accidental rules can now be defined across ChoirStaff contexts. Two new
rules choral and choral-cautionary are available that combine the
characteristics of mode
On 2016-12-14 21:36, Noeck wrote:
Hi Alexander,
in your example, the last line is just a mockup, isn't it? It is not
done by the proposed function? The extender after "We" in the last line
is unexpected for me.
Hi,
not a mockup, but not the real thing either. I sent this from a PC with
the "
Hi Trevor,
yes, I guess I never asked to be on that list. My last commit was
pre-Rietveld and pre-Allura, I think; and it's unlikely that
contributions from my side will come more often in the foreseeable
future (except for one more patch "in the pipeline", waiting for a
cleanup and documenta
> On 14 Dec 2016, at 18:22, Hans Aikema wrote:
>
>
>> On 14 Dec 2016, at 14:56, Hans Aikema wrote:
>>
>>
>>> On 14 Dec 2016, at 14:30, Masamichi Hosoda wrote:
>>>
>>
> <..>
> will do some more digging inside autoconf to see if I can spot any reason why
> CONFIG_SHELL would not be set
Worth an entry in changes?
Some wording-nitpicks, otherwise
LGTM
https://codereview.appspot.com/311430043/diff/1/Documentation/notation/pitches.itely
File Documentation/notation/pitches.itely (right):
https://codereview.appspot.com/311430043/diff/1/Documentation/notation/pitches.itely#newcode2
Hi Alexander,
in your example, the last line is just a mockup, isn't it? It is not
done by the proposed function? The extender after "We" in the last line
is unexpected for me.
Cheers,
Joram
___
lilypond-devel mailing list
lilypond-devel@gnu.org
https:
Am 14. Dezember 2016 18:03:09 MEZ, schrieb Simon Albrecht
:
>On 14.12.2016 14:54, Knut Petersen wrote:
>> With a music function \autoextenders that adds extender events to
>> every syllable you
>> - can be sure never to forget extenders,
>> - can be sure never to generate too short extenders
>>
Am 14.12.2016 um 18:03 schrieb Simon Albrecht:
On 14.12.2016 14:54, Knut Petersen wrote:
With a music function \autoextenders that adds extender events to every
syllable you
- can be sure never to forget extenders,
- can be sure never to generate too short extenders
- can use the same lyrics de
> On 14 Dec 2016, at 14:56, Hans Aikema wrote:
>
>
>> On 14 Dec 2016, at 14:30, Masamichi Hosoda wrote:
>>
> New build from Masamichi’s branch passed the linux ppc harfbuzz, so the
> ICU patch worked. Now looking into a breaking freebsd-x86 lilypond error:
Would you show
On 14.12.2016 14:54, Knut Petersen wrote:
With a music function \autoextenders that adds extender events to
every syllable you
- can be sure never to forget extenders,
- can be sure never to generate too short extenders
- can use the same lyrics definition for voices that require extenders
at d
Hello,
Here is the current patch countdown list. The next countdown will be on
December 17th.
A quick synopsis of all patches currently in the review process can be
found here:
http://philholmes.net/lilypond/allura/
__
Push: No patches to Push at this time.
Countdown:
5004 Doc:
Alexander, you wrote Wednesday, December 14, 2016 12:32 PM
> On 2016-12-14 13:15, James wrote:
>
>> On 13/12/16 20:10, perpeduumimmob...@gmail.com wrote:
>>> Reviewers: ,
>>>
>>> Message:
>>> add choral and choral-cautionary accidental style
>> ...
>>>
>>> Please review this at https://codereview
Hi Knut,
On Wed, Dec 14, 2016 at 3:16 AM, Knut Petersen
wrote:
> Hi everybody!
>
> There is a discussion on lilypond-user with the target to allow automated
> lyric extenders
> to lilypond. One part of that is a patch to clean and extend
> lyric_extender.cc.
>
> To allow automated creation of lyr
> On 14 Dec 2016, at 14:30, Masamichi Hosoda wrote:
>
New build from Masamichi’s branch passed the linux ppc harfbuzz, so the
ICU patch worked. Now looking into a breaking freebsd-x86 lilypond error:
>>>
>>> Would you show me the whole log file?
>> Went into a bit of experimentation
Hi Urs!
My gut feeling says: Yes, this is an improvement and should be there by
default. IIUC the reason why this has to be discussed is because that
could change/break existing scores, right?
If so, could you please think about an example where the patch would
have a negative impact that can't
Hi Urs, hi all.
On 2016-12-14 11:18, Urs Liska wrote:
Am 14.12.2016 um 10:43 schrieb Alexander Kobel:
To allow automated creation of lyric extenders a helper function is
needed
... that does exactly this, adding extenders everywhere.
IMHO, the actual question to decide upon is: Do we want th
>>> New build from Masamichi’s branch passed the linux ppc harfbuzz, so the ICU
>>> patch worked. Now looking into a breaking freebsd-x86 lilypond error:
>>
>> Would you show me the whole log file?
> Went into a bit of experimentation afterwards, still failed attempts only,
> after discovering
Passes make, make check and a full make doc
https://codereview.appspot.com/311430043/
___
lilypond-devel mailing list
lilypond-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-devel
Hi all
Eventually I managed to build the new ISO.
I decided to upgrade to Stretch (still in testing), because otherwise I
had problems with pinning guile-2.0 from testing. Another advantage is
that in Stretch there's also LxQT (successor of LXDE), which seems
lightweight, fast and feature-rich
On 14/12/16 12:32, Alexander Kobel wrote:
Hi James,
thanks for taking care of that one.
On 2016-12-14 13:15, James wrote:
Hello,
On 13/12/16 20:10, perpeduumimmob...@gmail.com wrote:
Reviewers: ,
Message:
add choral and choral-cautionary accidental style
...
Please review this at https
Hi James,
thanks for taking care of that one.
On 2016-12-14 13:15, James wrote:
Hello,
On 13/12/16 20:10, perpeduumimmob...@gmail.com wrote:
Reviewers: ,
Message:
add choral and choral-cautionary accidental style
...
Please review this at https://codereview.appspot.com/311430043/
Affecte
> On 14 Dec 2016, at 12:28, Masamichi Hosoda wrote:
>
>> New build from Masamichi’s branch passed the linux ppc harfbuzz, so the ICU
>> patch worked. Now looking into a breaking freebsd-x86 lilypond error:
>
> Would you show me the whole log file?
Went into a bit of experimentation afterwards
Hello,
On 13/12/16 20:10, perpeduumimmob...@gmail.com wrote:
Reviewers: ,
Message:
add choral and choral-cautionary accidental style
...
Please review this at https://codereview.appspot.com/311430043/
Affected files (+151, -1 lines):
M Documentation/notation/pitches.itely
M ly/engraver
> New build from Masamichi’s branch passed the linux ppc harfbuzz, so the ICU
> patch worked. Now looking into a breaking freebsd-x86 lilypond error:
Would you show me the whole log file?
___
lilypond-devel mailing list
lilypond-devel@gnu.org
https://l
Am 14.12.2016 um 10:43 schrieb Alexander Kobel:
>> To allow automated creation of lyric extenders a helper function is
>> needed
>
> ... that does exactly this, adding extenders everywhere.
>
> IMHO, the actual question to decide upon is: Do we want this to be
> enabled by default? IIUC, the fact
> On 13 Dec 2016, at 01:20, Hans Aikema wrote:
>
> On 12 Dec 2016, at 15:41, Masamichi Hosoda wrote:
>>
>> <…>
>> Maybe the issue is to use ICU of CentOS system.
>>
>> I've created a patch.
>> https://github.com/trueroad/gub/commit/081cc91f698186795dca45e8d6db8af6616826d4
>>
>> If this patch
Am 14.12.2016 um 10:43 schrieb Alexander Kobel:
>> Q2: Obviously the definition of \autoextenders does not match the coding
>> style used in scm/*. It does not even
>> work if it is added to music-functions.scm. Some advice is needed ...
>> the extending-manual is not a real help in
>> this case.
Hi Knut, hi all.
On 2016-12-14 10:16, Knut Petersen wrote:
Hi everybody!
There is a discussion on lilypond-user with the target to allow
automated lyric extenders to lilypond. One part of that is a patch
to clean and extend lyric_extender.cc.
Knut is playing down his work here. The crucial po
Hi everybody!
There is a discussion on lilypond-user with the target to allow automated lyric
extenders
to lilypond. One part of that is a patch to clean and extend lyric_extender.cc.
To allow automated creation of lyric extenders a helper function is needed.
Putting the
following code into a
30 matches
Mail list logo
