Le 01.11.2007 15:39, michał poręba disait :
Hi
I began my translation as recomended in README file
gmake new LANG=pl
It should copy all original files from site/ to pl/, shouldn't it?
I miss these: [...]
shall I just copy those files manually?
cheers
michał
If you have a look at the othe
2007/11/1, Valentin Villenave <[EMAIL PROTECTED]>:
> Is the nested contexts patch applied on your git branch, or do I have
> to apply it on a local master branch ?
Oops, I've just seen the _other_ thread.
Never mind :)
___
lilypond-devel mailing list
2007/10/31, Rune Zedeler <[EMAIL PROTECTED]>:
> On the 29th of october I posted a beta-fix for nested contexts.
> Before we polish it and include it in lily we need to ensure that it works.
Hi Rune,
I'm currently on vacation at my grandparents' (yeah I know, my life is
quite exciting) and I'm ru
Hi
I began my translation as recomended in README file
gmake new LANG=pl
It should copy all orginal files from site/ to pl/, shouldn't it?
I miss these:
announce*.html
contact.ihtml
menu-entries.py
news.ihtml
old-news.html
search-noscript.html
search.html
template.ihtml
shell I just copy those
Mats Bengtsson wrote:
I realize that this might break some existing code and have tried to fix it
in the regression test files I could find (the example line-arrows.ly in
LSR
has to be updated correspondingly).
LSR is still on 2.10.12, so this can't be fixed until it upgrades. (and
that won
On 11/1/07, Mats Bengtsson <[EMAIL PROTECTED]> wrote:
> Hi,
>
> The current mechanism to get solid versus dashed lines in LilyPond has
> been irritating me for several years. We do have the option to set
> both #'style = #'line and #'style = #dashed-line but currently both
> give the same result an
Hi,
The current mechanism to get solid versus dashed lines in LilyPond has
been irritating me for several years. We do have the option to set
both #'style = #'line and #'style = #dashed-line but currently both
give the same result and you instead have to set #'dash-fraction = #'()
to get a solid
On 01.11.2007 (10:11), Mats Bengtsson wrote:
> Cross-staff arpeggios already work in StaffGroups and GrandStaffs, without
> adding any extra engraver:
Ah, great! Thanks. Why didn't I think of that...?
e
--
"To make a bad day worse, spend it wishing for the impossible." -Calvin
Cross-staff arpeggios already work in StaffGroups and GrandStaffs, without
adding any extra engraver:
\score {
\new StaffGroup {
\set StaffGroup.connectArpeggios = ##t
<<
\new Staff \relative c' {
4\arpeggio
}
\new Staff \relative c {
