headers
Dan Eble | 1 Oct 2008 01:11
Picon

Re: barcheck failed at: 0/0

The "0/0" message occurs in 2.11.59, but not in 2.11.58.
--  
Dan

On 28 Sep 2008, at 14:26, Dan Eble wrote:

> I'm running the version from http://lilypond.org/web/install/#2.11  
> which is labeled "MacOS X (G3, G4, G5 Macs) 10.3 and newer" on  
> 10.5.5 (the latest).
>
> When I get time, I'll try to narrow it down to a specific version  
> for you.
> -- 
> Dan
>
>
> On 28 Sep 2008, at 14:18, Valentin Villenave wrote:
>
>> 2008/9/28 Dan Eble <dan <at> faithful.be>:
>>> Here's the whole file for now.  It's not that I mind narrowing  
>>> down the
>>> problem for you; I just can't do it today.  Let me know if you  
>>> need a more
>>> restricted example.
>>
>> when compiling the whole file, I get two 3/4 barchecks warnings, but
>> no 0/0. Strange.
>>
>> Cheers,
>> Valentin
(Continue reading)

Permalink | Reply | 1 comment |
headers
Neil Puttock | 1 Oct 2008 01:23
Picon

Re: barcheck failed at: 0/0

Hi Dan,

2008/10/1 Dan Eble <dan <at> faithful.be>:
> The "0/0" message occurs in 2.11.59, but not in 2.11.58.
> -- Dan

This looks like a string conversion failure following the update of
the rational code to 64 bit (implemented in 2.11.59).

Here's the code from flower/string_convert.cc (which was already present):

  84 string
  85 String_convert::i64_string (I64 i64, char const *fmt)
  86 {
  87   char buffer[STRING_BUFFER_LEN];
  88   snprintf (buffer, STRING_BUFFER_LEN,
  89             (fmt ? fmt : "%Ld"), i64); // assume radix 10
  90   return string (buffer);
  91 }

Regards,
Neil
Permalink | Reply | 0 comments |
headers
John Mandereau | 1 Oct 2008 02:11
Picon

Re: Building the docs fails on require_python_version

On 2008/09/30 22:46 +0000, Eyolf Oestrem wrote:
> Since yesterday, I haven't been able to build the docs -- 
> fresh git checkout and a newly compiled lilypond.

Are you sure? (see below)

> Linux (Arch), python version 2.5.2. Make web ends with:
>  
> Traceback (most recent call last):
>   File "../../scripts/lilypond-book.py", line 48, in <module>
>     ly.require_python_version ()
> AttributeError: 'module' object has no attribute 'require_python_version'
> make[1]: *** [out-www/lilypond.texi] Error 1

Do

make -C python

or from toplevel

make

then try building docs again.

HTH,
John
Permalink | Reply | 1 comment |
headers
Eyolf Østrem | 1 Oct 2008 02:27
Favicon

Re: Building the docs fails on require_python_version

On 01.10.2008 (02:11), John Mandereau wrote:
> On 2008/09/30 22:46 +0000, Eyolf Oestrem wrote:
> > Since yesterday, I haven't been able to build the docs -- 
> > fresh git checkout and a newly compiled lilypond.
> 
> Are you sure? (see below)

> Do
> 
> make -C python

Arghh, I had forgotten about that one in the branch I was building from.
Sorry for the noise.

eyolf

--

-- 
Historians exercise great power and some of them know it.  They recreate the
past, changing it to fit their own interpretations.  Thus, they change the
future as well. 

  -- Leto II, His Voice, from Dar-es-Balat
Permalink | Reply | 0 comments |
headers
hanwenn | 1 Oct 2008 02:56
Picon

* Fix arpeggio overshoot for chords which reach centre line.

Reviewers: Neil Puttock,

http://codereview.appspot.com/6453/diff/1/3
File lily/arpeggio.cc (right):

http://codereview.appspot.com/6453/diff/1/3#newcode108
Line 108: y += rint (squiggle.extent (Y_AXIS).length ()))
while the original is obviously wrong for the .ly you show, the fix
looks fishy to me as you would be accumulating roundoff errors. The loop
should be

while (mol.extent(Y_AXIS) <  heads[RIGHT])
  { add_at_edge }

perhaps to prevent the problem, there could be something like

while (mol.extent(Y_AXIS) + 1.0 <  heads[RIGHT])
  { add_at_edge }

(where 1.0 is intelligently chosen.)

Description:
* Fix arpeggio overshoot for chords which reach centre line.
This patch fixes a rounding error in Arpeggio::print () that occurs when
a
chord reaches the centre line, resulting in an extra squiggle being
added.

Please review this at http://codereview.appspot.com/6453
(Continue reading)

Permalink | Reply | 0 comments |
headers
Han-Wen Nienhuys | 1 Oct 2008 06:13
Picon

.61 released

Hi,

I am uploading 2.11.61;  this uses the updated odcctools, so the
binary should work on macos 10.5 as well.

Can someone update the download instructions appropriately?

thanks!

--

-- 
Han-Wen Nienhuys - hanwen <at> xs4all.nl - http://www.xs4all.nl/~hanwen
Permalink | Reply | 0 comments |
headers
Josh Parmenter | 1 Oct 2008 06:13

Re: GUB experiments on linux-64

good... thanks.

Josh

On Sep 30, 2008, at 3:03 PM, Han-Wen Nienhuys wrote:

> On Tue, Sep 30, 2008 at 1:32 PM, Josh Parmenter <josh <at> realizedsound.net 
> > wrote:
>> Hi Han-Wen,
>>
>> otool looks okay:
>>
>> Ringo:bin joshp$ otool -L lilypond
>> lilypond:
>>        <at> executable_path/../lib//libintl.8.dylib (compatibility version
>> 9.0.0, current version 9.0.0)
>>       /usr/lib/libSystem.B.dylib (compatibility version 1.0.0,  
>> current
>> version 88.1.2)
>>        <at> executable_path/../lib//libguile.17.dylib (compatibility  
>> version
>> 19.0.0, current version 19.2.0)
>>        <at> executable_path/../lib//libgmp.3.dylib (compatibility  
>> version 8.0.0,
>> current version 8.1.0)
>>        <at> executable_path/../lib//libpangoft2-1.0.0.dylib (compatibility
>> version 2001.0.0, current version 2001.0.0)
>>        <at> executable_path/../lib//libpango-1.0.0.dylib (compatibility  
>> version
>> 2001.0.0, current version 2001.0.0)
(Continue reading)

Permalink | Reply | 0 comments |
headers
Han-Wen Nienhuys | 1 Oct 2008 06:19
Picon

MacOS python/GUI issues

Given the problems with the current GUI shell and python
incompatibilities on macos, I think it makes sense to rebuild the
shell using python 2.4, and as a fat binary. Then the installer will
include its own python interpreter,  which we could use to run the
scripts.

Any takers for compiling lilypad with py2app ?

--

-- 
Han-Wen Nienhuys - hanwen <at> xs4all.nl - http://www.xs4all.nl/~hanwen
Permalink | Reply | 21 comments |
headers
Francisco Vila | 1 Oct 2008 09:59
Picon

Small issue on title tag, html docs

Hello. There might be a problem on the current build script regarding
to utf8 encoding.

http://kainhofer.com/~lilypond/Documentation/user/lilypond/index.es.html

The <title> HTML tag is composed by concatenating two different
strings, one is the main document title, and the other is the page
currently being viewed. I think two incompatible encoding schemes are
mixing here, because all the document shows utf8 accented characters
fine, but the main title contains accented characters in Spanish and
they appear as viewed as latin-1.

For example

<head>
<title>Referencia de la notación de GNU LilyPond: 1. Notación musical</title>

<meta name="description" content="Referencia de la notación de GNU
LilyPond: 1. Musical notation">
<meta name="keywords" content="Referencia de la notación de GNU
LilyPond: 1. Musical notation">

[Note the correct oacute in the title]

This would be solved by encoding all these strings as iso entities, I think.

Thanks, Good work.
--

-- 
Francisco Vila. Badajoz (Spain)
http://www.paconet.org
(Continue reading)

Permalink | Reply | 2 comments |
headers
Till Rettig | 1 Oct 2008 08:56
Picon
Picon

Re: Link to documentation tarball from documentation index?



Valentin Villenave schrieb:
2008/9/29 John Mandereau <john.mandereau <at> gmail.com>:
Many users overlook the link to the docball in the download page, so they do not know about it; a user suggested on the French list that we could add a link to the docball from the documentation index. How does the attached page look?
+1
I also like it

Till
Cheers, Valentin _______________________________________________ lilypond-devel mailing list lilypond-devel <at> gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-devel 
_______________________________________________
lilypond-devel mailing list
lilypond-devel <at> gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-devel
Permalink | Reply | 0 comments |

Gmane