aleksandr.andreev wrote Wednesday, February 27, 2013 2:49 PM
> I think it makes sense to push this patch first and then I will upload
> another patch that changes the syntax across the manual. That way it is
> cleaner in the commit history.
Fine by me.
> There is also Issue 1287. I could try t
Le 28/02/2013 07:45, Federico Bruni disait :
I've received the texinfo_document.po file from the Translation Project.
While looking at other languages po files to understand what to
translate and what to leave untraslated, I've noticed some strange
characters. Probably because these files are sav
On 28 févr. 2013, at 06:48, d...@gnu.org wrote:
> On 2013/02/27 23:00:48, mike7 wrote:
>> On 27 févr. 2013, at 19:06, mailto:d...@gnu.org wrote:
>
>> >
>> >
>
> https://codereview.appspot.com/7377046/diff/17001/input/regression/scheme-text-spanner.ly
>> > File input/regression/scheme-text-spanne
> I think that at the current point of time, we should try getting
> along with a flat namespace approach. That might imply renaming
> properties like "padding" to "side-padding" if we can't achieve
> reasonable results otherwise. Not sure about that.
I support that. Renaming properties which
On 28 févr. 2013, at 12:16, Werner LEMBERG wrote:
>
>> I think that at the current point of time, we should try getting
>> along with a flat namespace approach. That might imply renaming
>> properties like "padding" to "side-padding" if we can't achieve
>> reasonable results otherwise. Not su
>> Renaming properties which do something differently is the way to go
>> IMHO.
>
> Then the first step is finding all properties that are defined in
> multiple interfaces and changing their names.
Maybe a naïve question: Are there many?
Werner
On 28 févr. 2013, at 12:40, Werner LEMBERG wrote:
>
>>> Renaming properties which do something differently is the way to go
>>> IMHO.
>>
>> Then the first step is finding all properties that are defined in
>> multiple interfaces and changing their names.
>
> Maybe a naïve question: Are there m
"m...@mikesolomon.org" writes:
> On 28 févr. 2013, at 12:40, Werner LEMBERG wrote:
>
>>
Renaming properties which do something differently is the way to go
IMHO.
>>>
>>> Then the first step is finding all properties that are defined in
>>> multiple interfaces and changing their names
On 28 févr. 2013, at 12:47, David Kastrup wrote:
> "m...@mikesolomon.org" writes:
>
>> On 28 févr. 2013, at 12:40, Werner LEMBERG wrote:
>>
>>>
> Renaming properties which do something differently is the way to go
> IMHO.
Then the first step is finding all properties that
2013/2/28 Jean-Charles Malahieude
> It is because the files are in US-ASCII and not in UTF-8.
> I have to admit it has been a pain for me having to type "@'a" instead of
> just "à" or "@ " for a non breakable space like in the old times of LaTeX
> (or even lyrics in LilyPond 1.3.84).
>
Do you me
Le 28/02/2013 13:11, Federico Bruni disait :
2013/2/28 Jean-Charles Malahieude
It is because the files are in US-ASCII and not in UTF-8.
I have to admit it has been a pain for me having to type "@'a" instead of
just "à" or "@ " for a non breakable space like in the old times of LaTeX
(or even
https://codereview.appspot.com/7424049/diff/1/input/regression/repeat-slur.ly
File input/regression/repeat-slur.ly (right):
https://codereview.appspot.com/7424049/diff/1/input/regression/repeat-slur.ly#newcode14
input/regression/repeat-slur.ly:14: \alternative { { a' ) b' \set
breakSlurAtBarLine
On 28 févr. 2013, at 21:30, n.putt...@gmail.com wrote:
>
> https://codereview.appspot.com/7424049/diff/1/input/regression/repeat-slur.ly
> File input/regression/repeat-slur.ly (right):
>
> https://codereview.appspot.com/7424049/diff/1/input/regression/repeat-slur.ly#newcode14
> input/regression/
On Feb 28, 2013 8:37 PM, "m...@mikesolomon.org"
wrote:
> You're right, but I've opted for the breaking behavior in the most recent
patch-set (\breakSlurHere). Otherwise, slurs wouldn't be able to span only
one musical moment.
Ok, so how about using an event of class break-span-event (like
\brea
On 28 févr. 2013, at 22:29, Neil Puttock wrote:
>
> On Feb 28, 2013 8:37 PM, "m...@mikesolomon.org" wrote:
>
> > You're right, but I've opted for the breaking behavior in the most recent
> > patch-set (\breakSlurHere). Otherwise, slurs wouldn't be able to span only
> > one musical moment.
Please see the report from Hanspeter, below, about a problem building
Lilypond.
Cheers,
Colin.
Hanspeter Niederstrasser writes:
> When texinfo 5.0 is installed, the build fails with this error:
>
>
> /sw/build.build/lilypond-devel-2.17.13-1/lilypond-2.17.13/scripts/build/out/
> run-and-che
Hello,
On 28 February 2013 22:13, Colin Hall wrote:
>
> Please see the report from Hanspeter, below, about a problem building
> Lilypond.
>
> Cheers,
> Colin.
>
> Hanspeter Niederstrasser writes:
>
> > When texinfo 5.0 is installed, the build fails with this error:
> >
> >
> #
>
See this t
Very nice, and thanks a lot! From visual inspection only, LGTM.
Just curious: You apparently like the word `junk', however, I find it
not optimal. Can you replace this with `discard' or `cut' within the
command names?
https://codereview.appspot.com/7424049/diff/3002/scm/define-music-types.sc
LGTM
https://codereview.appspot.com/7404046/
___
lilypond-devel mailing list
lilypond-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-devel
LGTM
https://codereview.appspot.com/7382060/
___
lilypond-devel mailing list
lilypond-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-devel
Hi list,
Attached is a minimal score containing a scheme engraver that adds a
grob in the `stop-translation-timestep` function. This results in a
segfault when the score is to be rendered.
I'm using Lilypond 2.16.1.
segfault.ly
Description: Binary data
__
Much better, thanks!
https://codereview.appspot.com/7424049/
___
lilypond-devel mailing list
lilypond-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-devel
22 matches
Mail list logo
