Le 14 déc. 08 à 21:12, Joe Neeman a écrit :
This gives good results, however,
the page-turn page breaking algorithm adds blank pages at some
places,
for instance, just before the last page of a bookpart, which gives an
awkward result:
_4_ _5__6_ _7__8_
|===||===| |===|| | |===|
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Please review the following two patches:
1) About the single thick barlines and the current \bar "." style (which
produces a single centered dot). Unless someone has a good reason, I propose
to use \bar "." for a thick bar line instead and drop the
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Am Dienstag, 23. Dezember 2008 05:01:39 schrieb Patrick McCarty:
> Is this better for you, Till? Does anyone else have any more
> comments?
The only thing that is bothering me is the color of visited links in the TOC
on the left. The different color
> Please review the following two patches:
>
> 1) About the single thick barlines and the current \bar "." style
> (which produces a single centered dot). Unless someone has a good
> reason, I propose to use \bar "." for a thick bar line instead and
> drop the single centered dot altogether (or sh
Reviewers: Reinhold,
Message:
Shouldn't there be changes in other files to correspond? (do we have a
regtest?)
Description:
* use correct left to right ordering in keySignature list
The keySignature property list of the KeySignature so far was using
reversed order (e.g. the rightmost accidental
Reviewers: Reinhold,
Message:
LGTM
missing documentation, and regtest though
Description:
Implement thick bar lines (use \bar "." for this)
Until now, \bar"." produced a single dot instead of the bar line, which
was however not used anywhere and also not documented...
Using "." for the bar line
On Tue, Dec 23, 2008 at 4:26 AM, Reinhold Kainhofer
wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> Am Dienstag, 23. Dezember 2008 05:01:39 schrieb Patrick McCarty:
>> Is this better for you, Till? Does anyone else have any more
>> comments?
>
> The only thing that is bothering me is
GCC 4.4 tends to be extra-picky about explicitly including header
files in C++. Attached is a patch to resolve the issue.
0001-Add-header-includes-for-GCC-4.4.patch
Description: application/download
___
lilypond-devel mailing list
lilypond-devel@gnu.or
> GCC 4.4 tends to be extra-picky about explicitly including header
> files in C++. Attached is a patch to resolve the issue.
Applied, thanks.
Werner
___
lilypond-devel mailing list
lilypond-devel@gnu.org
http://lists.gnu.org/mailman/listinfo/l
Hello,
I have just cut a 2.12.0 release, uploaded it to lilypond.org, and
switched over the redirects to v2.12.
I leave it to anyone interested to pose as the official representative
of the lilypond community and post a release announcement.
--
Han-Wen Nienhuys - han...@xs4all.nl - http://www.x
On Wed, Dec 24, 2008 at 12:27:33AM -0200, Han-Wen Nienhuys wrote:
> I have just cut a 2.12.0 release, uploaded it to lilypond.org, and
> switched over the redirects to v2.12.
Yay! Christmas present for everybody.
> I leave it to anyone interested to pose as the official representative
> of the l
Whoever is up-to-date on convert-ly (I'm not), please review and
apply.
Cheers,
- Graham
diff --git a/python/convertrules.py b/python/convertrules.py
index f86165c..d431bf6 100644
--- a/python/convertrules.py
+++ b/python/convertrules.py
@@ -2860,6 +2860,12 @@ chord-shape call.\n"))
raise
Note that I also did not update the website accordingly, so you'll
need to update the download page too.
On Wed, Dec 24, 2008 at 1:10 AM, Graham Percival
wrote:
> On Wed, Dec 24, 2008 at 12:27:33AM -0200, Han-Wen Nienhuys wrote:
>> I have just cut a 2.12.0 release, uploaded it to lilypond.org, an
Han-Wen Nienhuys wrote:
Hello,
I have just cut a 2.12.0 release, uploaded it to lilypond.org, and
switched over the redirects to v2.12.
I leave it to anyone interested to pose as the official representative
of the lilypond community and post a release announcement.
Congratulations! I just dow
14 matches
Mail list logo
