Francisco Vila schrieb:
Just to add a bit to the brainstorming:
The uppermost lace of our G-clef already was slightly oversized.
I cannot explain why, but latest proposals I've seen are getting it
even greater.
Anyone appreciates the same?
Well spotted. I was not sure whether this is kind
Trevor Daniels Monday, December 21, 2009 1:07 AM
n.putt...@gmail.com, Sunday, December 20, 2009 9:48 PM
On 2009/12/14 12:13:07, t.daniels_treda.co.uk wrote:
So is http://codereview.appspot.com/164063 now ready to go?
The indentation in translation-functions.scm is still a bit
wrong, but
On Thu, Dec 24, 2009 at 03:22:51AM +0100, Francisco Vila wrote:
In my translated downloads page, I can not make
@downloadStableLinuxNormal and others to appear properly expanded.
I can only find the macro downloadStableLinuxNormal defined in
generated files (and therefore not able to find it
Marc Hohl wrote:
By the way, it would be easier for you developers when the
patches go directly to rietveld. How can I archieve this?
Does somebody need to create an account for me?
See CG Adding or modifying features; scroll down to
8.7.9 Post patch for comments.
- Mark
2009/12/23 John Mandereau john.mander...@gmail.com:
Hi guys,
In my way of fixing lilypond-book hashing, I'm afraid I'll have to
revert 4c5a581ca25398669b9ecbc7a606febb09e60214 lilypond-book: Change
md5 hashing strategy, because ignoring fragment options for the hash
which have an impact on
On Thu, Dec 24, 2009 at 01:06:19AM +0100, John Mandereau wrote:
Le mercredi 23 décembre 2009 à 23:17 +, Graham Percival a écrit :
Yes; that's why we changed the hash calculation from self.ly() to
self.full_ly()
You meant the opposite.
err, yeah.
-- produced lily-abcd1234 filename
2009/12/24 John Mandereau john.mander...@gmail.com:
Please review
http://codereview.appspot.com/183048
Looks fine to me, and nothing broken while doing an out-of-tree build
from scratch.
Cheers,
- Graham
___
lilypond-devel mailing list
On Thu, Dec 24, 2009 at 7:30 PM, Graham Percival
gra...@percival-music.ca wrote:
and will achieve what you explained
above (regtest comparison is based on input/regression/out-www or its
mirror in out-www/offline-root, right?).
I think it's actually via make test, following by tarring the
commit 6c1cdaa331972442a8fd62d98da5adebfaa9a17b
I thought that texinfo macros were supposed to have a {} after them --
I mean, it's not /required/ for arguments without any macros, but...?
Cheers,
- Graham
___
lilypond-devel mailing list
Am Donnerstag, 24. Dezember 2009 21:52:10 schrieb Graham Percival:
If the files in those directories had names corresponding to their
actual regtest file names, then the regtest comparisons would be more
robust against changing lilypond-book options. I'm not certain
whether this would be best
On Sun, 2009-12-20 at 18:42 +0100, James Bailey wrote:
In checking the regressions, I've come across some issues. And, sorry
for posting these all in one go, but I've just been saving them up
until one day I could post a massive email and have the bug tracker
explode with new regression
On Thu, Dec 24, 2009 at 02:57:07PM -0800, Joe Neeman wrote:
On Sun, 2009-12-20 at 18:42 +0100, James Bailey wrote:
profile-property-access.ly errors and fails when I try to compile it.
Additionally, the properties shown in the output are all 0
You need to configure with
On Thu, 2009-12-24 at 23:24 +, Graham Percival wrote:
On Thu, Dec 24, 2009 at 02:57:07PM -0800, Joe Neeman wrote:
On Sun, 2009-12-20 at 18:42 +0100, James Bailey wrote:
profile-property-access.ly errors and fails when I try to compile it.
Additionally, the properties shown in the
Op woensdag 23-12-2009 om 17:38 uur [tijdzone +0100], schreef John
Mandereau:
Le lundi 21 décembre 2009 à 22:28 +0100, Translation Project Robot a
écrit :
A new POT file for textual domain 'lilypond' has been made available
to the language teams for translation. It is archived as:
14 matches
Mail list logo
