Hi,
how would you feel about using SVG images and the switch element in
the text-input page?
http://lilypond.org/text-input.html
Pro:
- we could get rid of many .png files for all the translated languages
- maintaining translations would be much easier
Con:
- browser support?
Am 27.02.2012 10:01, schrieb d...@gnu.org:
On 2012/02/27 00:17:05, Carl wrote:
Looks like a good solution.
I think I would prefer the name excludeOpenStrings to
ignoreOpenStrings.
I think exclude is a better word for what is happening than ignore
I am actually not all too happy with
On 2012/02/27 10:51:25, marc wrote:
I hope I corrected everything accordingly, because I screwed up my
local
branch ... :-(
That's quite improbable to do thoroughly with git.
Try git reflog and see whether a useful copy is sitting among the given
references.
Instead of dontTreatOpenStringsSpecially, something like omitOpenStrings
or skipOpenStrings looks less like an active special action for open
strings, and maybe normalOpenStrings or fingerOpenStrings or
fretOpenStrings suggests that the point is to include them in the normal
calculations instead
On Mon, Feb 27, 2012 at 09:47:46AM +0100, Federico Bruni wrote:
- browser support?
http://www.codedread.com/svg-support.php
In 2007 Graham was against using SVG, because of limmited browser support:
http://lists.gnu.org/archive/html/lilypond-devel/2007-04/msg00087.html
5 years later,
On Sat, Feb 25, 2012 at 8:06 PM, Joe Neeman joenee...@gmail.com wrote:
On Sat, Feb 25, 2012 at 8:23 AM, Graham Percival gra...@percival-music.ca
wrote:
On Sat, Feb 25, 2012 at 03:57:55PM +, julien.ri...@gmail.com wrote:
This is good, I now get the error message right away when running
We need to make more space on lilypond.org. I've deleted
binaries, documentation, and regtests from everything other than
the first and last release of a stable series.
I'm going to do the same for the source tarballs, but I'll wait a
few days in case anybody urgently wants to save them. This
http://codereview.appspot.com/5696069/diff/1/Documentation/contributor/lsr-work.itexi
File Documentation/contributor/lsr-work.itexi (right):
http://codereview.appspot.com/5696069/diff/1/Documentation/contributor/lsr-work.itexi#newcode302
Documentation/contributor/lsr-work.itexi:302: @item
On
LGTM
http://codereview.appspot.com/5696073/
___
lilypond-devel mailing list
lilypond-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-devel
At the moment, we can't have text and rehearsal marks at the same
place, i.e.
\relative c' {
c1
\mark \default
\mark play violently
d
}
This can be faked by using a \tempo mark:
\relative c' {
c1
\mark \default
\tempo play violently
d
}
But if you want to display an actual
- Original Message -
From: Graham Percival gra...@percival-music.ca
To: lilypond-devel@gnu.org
Sent: Monday, February 27, 2012 1:48 PM
Subject: simultaneous rehersal marks, tempo indication, and text marks
At the moment, we can't have text and rehearsal marks at the same
place, i.e.
Minor typo
http://codereview.appspot.com/5698074/diff/1/ly/scheme-sandbox.ly
File ly/scheme-sandbox.ly (right):
http://codereview.appspot.com/5698074/diff/1/ly/scheme-sandbox.ly#newcode9
ly/scheme-sandbox.ly:9: % in order to acticate command line editing for
interactive sessions.
acticate -
Graham Percival gra...@percival-music.ca writes:
At the moment, we can't have text and rehearsal marks at the same
place, i.e.
\relative c' {
c1
\mark \default
\mark play violently
d
}
This can be faked by using a \tempo mark:
\relative c' {
c1
\mark \default
\tempo
On 27 February 2012 13:48, Graham Percival gra...@percival-music.ca wrote:
What would be involved in making a clean solution for this? I
imagine that a separate TextMark engraver (just like the
RehearsalMark engraver and MetronomeMark engravers) would do the
trick, but that's a bunch of icky
Neil Puttock n.putt...@gmail.com writes:
On 27 February 2012 13:48, Graham Percival gra...@percival-music.ca wrote:
What would be involved in making a clean solution for this? I
imagine that a separate TextMark engraver (just like the
RehearsalMark engraver and MetronomeMark engravers)
2012/2/27 Federico Bruni fedel...@gmail.com:
Pro:
- we could get rid of many .png files for all the translated languages
- maintaining translations would be much easier
Con:
- browser support?
http://www.codedread.com/svg-support.php
Interesting.
A Con: to view it in another language you
2012/2/27 Francisco Vila paconet@gmail.com:
Interesting.
A Con: to view it in another language you must change the system setting,
right?
Yes, in a browser it's probably the only way.
I've tried using the LANG variable, but it doesn't work.
Another way is using Squiggle.
Install the
Hi list,
a bit insprired by the GSoC 2012 preparations of the Lilypond community,
the Orgmode community is thinking about a participation too.
While the whole application process is pretty transparent and clear, the
question how GNU and the FSF are involved, especially when it comes to
money,
Am 27.02.2012 12:09, schrieb d...@gnu.org:
On 2012/02/27 10:51:25, marc wrote:
I hope I corrected everything accordingly, because I screwed up my
local
branch ... :-(
That's quite improbable to do thoroughly with git.
Well, I did it.
I don't know what happened, but most probably a git
Am 27.02.2012 12:19, schrieb d...@gnu.org:
Instead of dontTreatOpenStringsSpecially, something like omitOpenStrings
Well, omitOpenStrings sounds quite good IMHO. Before I do another patch,
any suggestions/corrections from other string-addicted people ;-) ?
Regards,
Marc
or skipOpenStrings
Marc Hohl m...@hohlart.de writes:
Am 27.02.2012 12:09, schrieb d...@gnu.org:
On 2012/02/27 10:51:25, marc wrote:
I hope I corrected everything accordingly, because I screwed up my
local
branch ... :-(
That's quite improbable to do thoroughly with git.
Well, I did it.
I don't know what
David,
this is 300% awesome!!
However, the following example doesn't work (it doesn't produce any
warning, either):
\score {
\new Staff { b b }
\layout { \override NoteHead #'color = #red }
}
Is this intended? I hoped that it would be possible to do this.
I even hoped that something like
pushed to staging as f154d90b9627c04a195ff3b286fe9737f8c8bc27; this
Rietveld issue can be closed. Thanks!
http://codereview.appspot.com/5672063/
___
lilypond-devel mailing list
lilypond-devel@gnu.org
Hi,
On Mon, Feb 27, 2012 at 6:35 PM, Thorsten quintf...@googlemail.com wrote:
a bit insprired by the GSoC 2012 preparations of the Lilypond community,
the Orgmode community is thinking about a participation too.
While the whole application process is pretty transparent and clear, the
New patch set.
http://codereview.appspot.com/5696069/diff/1/Documentation/contributor/lsr-work.itexi
File Documentation/contributor/lsr-work.itexi (right):
http://codereview.appspot.com/5696069/diff/1/Documentation/contributor/lsr-work.itexi#newcode302
On Tue, Feb 28, 2012 at 12:18 AM, Thorsten quintf...@googlemail.com wrote:
Janek Warchoł janek.lilyp...@gmail.com writes:
Hi,
On Mon, Feb 27, 2012 at 6:35 PM, Thorsten quintf...@googlemail.com wrote:
a bit insprired by the GSoC 2012 preparations of the Lilypond community,
the Orgmode
Maybe add some encouragement for getting involved?
http://codereview.appspot.com/5694092/diff/1/Documentation/changes.tely
File Documentation/changes.tely (right):
http://codereview.appspot.com/5694092/diff/1/Documentation/changes.tely#newcode71
Documentation/changes.tely:71: provide timely
On Mon, Feb 27, 2012 at 1:31 PM, Graham Percival
gra...@percival-music.ca wrote:
We need to make more space on lilypond.org. I've deleted
binaries, documentation, and regtests from everything other than
the first and last release of a stable series.
I understand that there were no binaries
Janek Warchoł janek.lilyp...@gmail.com writes:
Hi,
On Mon, Feb 27, 2012 at 6:35 PM, Thorsten quintf...@googlemail.com wrote:
a bit insprired by the GSoC 2012 preparations of the Lilypond community,
the Orgmode community is thinking about a participation too.
While the whole application
Reviewers: janek,
Message:
On 2012/02/27 22:23:15, janek wrote:
However, the following example doesn't work (it doesn't produce any
warning,
either):
\score {
\new Staff { b b }
\layout { \override NoteHead #'color = #red }
}
Is this intended? I hoped that it would be possible
On Tue, Feb 28, 2012 at 2:36 AM, d...@gnu.org wrote:
\score {
\new Staff { b b }
\layout { \override NoteHead #'color = #red }
}
Totally elusive bug that also afflicted \settingsFrom. Fixed
i confirm that it works for me. Thanks!
I even hoped that something like this will be
31 matches
Mail list logo
