2014-07-20 21:13 GMT+02:00 James :
> On 20/07/14 19:56, Federico Bruni wrote:
> > Thanks Markus, I'm putting the translation list in Cc. There are two
> > persons who expressed their interest in contributing to the update of
> > german manuals and hopefully they are reading this email and will tak
On 20/07/14 19:56, Federico Bruni wrote:
> Thanks Markus, I'm putting the translation list in Cc. There are two
> persons who expressed their interest in contributing to the update of
> german manuals and hopefully they are reading this email and will take care
> of this report also.
>
> Bug squad:
Thanks Markus, I'm putting the translation list in Cc. There are two
persons who expressed their interest in contributing to the update of
german manuals and hopefully they are reading this email and will take care
of this report also.
Bug squad: given the frequency of reports about translated man
Markus Olbrich writes:
> Hi!
>
> On the German version of the website there is a mistake in the first
> sentence of the first page (http://www.lilypond.org/index.de.html):
>
> Incorrect is:
> "LilyPond ist ein Notensatzprogramm, dass es sich zum Ziel gemacht hat,
> Notendruck von der bestmögliche
Hi!
On the German version of the website there is a mistake in the first
sentence of the first page (http://www.lilypond.org/index.de.html):
Incorrect is:
"LilyPond ist ein Notensatzprogramm, dass es sich zum Ziel gemacht hat,
Notendruck von der bestmöglichen Qualität zu erstellen."
Correct is:
2014-07-19 17:59 GMT+02:00 Francisco Vila :
> Yesterday I was messing with a MIDI imported in Rosegarden and edited
> a bass segment with the event editor, and one of the first events was
> a clef event. Let me look at it again tonight.
>
> Maybe the clef event was generated by Rosegarden on import
On 20/07/14 12:13, Karol Majewski wrote:
>> It seems to me (from my limited playing about with 2.19.8) that if you
>> comment out either/or 'two-sided' or 'binding-offset' then the problem
>> 'goes away'. So is this a 'binding-offset' issue or a 'two-sided' issue?
> James, note that binding-offset
> It seems to me (from my limited playing about with 2.19.8) that if you
> comment out either/or 'two-sided' or 'binding-offset' then the problem
> 'goes away'. So is this a 'binding-offset' issue or a 'two-sided' issue?
James, note that binding-offset doesn't work at all when two-sided is disable
On 19/07/14 23:25, Karol Majewski wrote:
> Hi,
>
> it seems that binding-offset size scales accordingly to global-staff-size,
> which of course is a bug:
>
> %%%
>
> \version "2.19.10"
>
> #(set-global-staff-size 20)
>
> \paper {
> top-markup-spacing = #'((basic-distance
On 19/07/14 23:25, Karol Majewski wrote:
> Hi,
>
> it seems that binding-offset size scales accordingly to global-staff-size,
> which of course is a bug:
>
> %%%
>
> \version "2.19.10"
>
> #(set-global-staff-size 20)
>
> \paper {
> top-markup-spacing = #'((basic-distance
10 matches
Mail list logo
