Re: 2.19.26 regtests

2015-08-31 Thread Masamichi HOSODA 
I've post a message to the tracker.
https://sourceforge.net/p/testlilyissues/issues/4585/

I've made a GUB's patch and send pull request.
https://github.com/gperciva/gub/pull/20

Would you merge it and try following command before make lilypond?

$ git fetch orign
$ git checkout master
$ git merge origin/master
$ rm -fr downloads/fonts-urw-core35/

> I've forwarded this to the bug list so someone should create a
> tracker.
> 
> Please note the bug list is now at
> http://sourceforge.net/p/testlilyissues/issues/
> 
> --
> Phil Holmes
> 
> 
> - Original Message - 
> From: "Masamichi HOSODA" <truer...@sea.plala.or.jp>
> To: <d...@gnu.org>
> Cc: <lilypond-devel@gnu.org>
> Sent: Monday, August 31, 2015 3:17 PM
> Subject: Re: 2.19.26 regtests
> 
> 
>>>>>There's lots of differences, presumably down to font changes,
>>>>
>>>> Also sans \bold and \italic do not seem to work in
>>>> font-family-override.ly
>>>
>>> Well, I call uh-oh.  It will probably take a few more unstable
>>> releases
>>> to shake out the problems from the font setup changes.
>>
>> Probably, it caused by URW fonts problem and/or Pango version.
>>
>> In my experiment, with newest URW fonts release (commit date is
>> 2015-08-28)
>> and newest Pango (version 1.36.8, 2014-09), there is no problem.
>> Attached file is the result.
>>
>>
>> First, the previous URW fonts release (commit date is 2015-08-25)
>> seems broken.
>> It has "Nimbus Sans Regular", "Nimbus Sans L Bold",
>> "Nimbus Sans L Regular Italic", "Nimbus Sans L Bold Italic".
>> Only "Regular" font's family name is "Nimbus Sans"
>> but others are "Nimbus Sans L".
>>
>> http://bugs.ghostscript.com/show_bug.cgi?id=696089
>> http://git.ghostscript.com/?p=urw-core35-fonts.git;a=commitdiff;h=ee2beed6
>>
>> The newest URW fonts release has no "Nimbus Sans" but "Nimbus Sans L".
>>
>> http://git.ghostscript.com/?p=urw-core35-fonts.git;a=commit;h=c983ed400dc278dcf20bdff68252fad6d9db7af9
>>
>>
>> Next, we use old Pango (version 1.28.3, 2010-09) in GUB.
>> In four years, many bugs would have been fixed.
>>
>>
>> So I'll make a GUB's patch that updates URW fonts and Pango.
>>
>>
>> Would I create an Issue on tracker?
>> How can I do so?
>> Or, would someone create it?
>>
> 
> 
> 
> 
> 
>> ___
>> lilypond-devel mailing list
>> lilypond-devel@gnu.org
>> https://lists.gnu.org/mailman/listinfo/lilypond-devel

___
lilypond-devel mailing list
lilypond-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-devel

Re: 2.19.26 regtests

2015-08-31 Thread Masamichi HOSODA 
There's lots of differences, presumably down to font changes,
>>>
>>> Also sans \bold and \italic do not seem to work in font-family-override.ly
>> 
>> And in kievan-notation.ly the spacing of the lyrics in-syllable is
>> awful.  Whatever font we chose there has metrics that appear hardly
>> suitable to me for running text.
> 
> kievan-notation.ly seems to use DejaVu Serif.
> It should be Linux Libertine like utf-8.ly using.
> I'll make a patch.

I've created Issue 4587.
http://sourceforge.net/p/testlilyissues/issues/4587/

And, I've uploaded a patch.
https://codereview.appspot.com/264080043

___
lilypond-devel mailing list
lilypond-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-devel

Re: 2.19.26 regtests

2015-08-31 Thread David Kastrup 
Masamichi HOSODA  writes:

>There's lots of differences, presumably down to font changes,

 Also sans \bold and \italic do not seem to work in font-family-override.ly
>>> 
>>> And in kievan-notation.ly the spacing of the lyrics in-syllable is
>>> awful.  Whatever font we chose there has metrics that appear hardly
>>> suitable to me for running text.
>> 
>> kievan-notation.ly seems to use DejaVu Serif.
>> It should be Linux Libertine like utf-8.ly using.
>> I'll make a patch.
>
> I've created Issue 4587.
> http://sourceforge.net/p/testlilyissues/issues/4587/
>
> And, I've uploaded a patch.
> https://codereview.appspot.com/264080043

Thanks.

-- 
David Kastrup

___
lilypond-devel mailing list
lilypond-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-devel

Re: 2.19.26 regtests

2015-08-31 Thread Masamichi HOSODA 
>>>There's lots of differences, presumably down to font changes,
>>
>> Also sans \bold and \italic do not seem to work in
>> font-family-override.ly
> 
> Well, I call uh-oh.  It will probably take a few more unstable releases
> to shake out the problems from the font setup changes.

Probably, it caused by URW fonts problem and/or Pango version.

In my experiment, with newest URW fonts release (commit date is 2015-08-28)
and newest Pango (version 1.36.8, 2014-09), there is no problem.
Attached file is the result.


First, the previous URW fonts release (commit date is 2015-08-25) seems broken.
It has "Nimbus Sans Regular", "Nimbus Sans L Bold",
"Nimbus Sans L Regular Italic", "Nimbus Sans L Bold Italic".
Only "Regular" font's family name is "Nimbus Sans"
but others are "Nimbus Sans L".

http://bugs.ghostscript.com/show_bug.cgi?id=696089
http://git.ghostscript.com/?p=urw-core35-fonts.git;a=commitdiff;h=ee2beed6

The newest URW fonts release has no "Nimbus Sans" but "Nimbus Sans L".

http://git.ghostscript.com/?p=urw-core35-fonts.git;a=commit;h=c983ed400dc278dcf20bdff68252fad6d9db7af9


Next, we use old Pango (version 1.28.3, 2010-09) in GUB.
In four years, many bugs would have been fixed.


So I'll make a GUB's patch that updates URW fonts and Pango.


Would I create an Issue on tracker?
How can I do so?
Or, would someone create it?
___
lilypond-devel mailing list
lilypond-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-devel

Re: 2.19.26 regtests

2015-08-31 Thread Phil Holmes 

I've forwarded this to the bug list so someone should create a tracker.

Please note the bug list is now at 
http://sourceforge.net/p/testlilyissues/issues/


--
Phil Holmes


- Original Message - 
From: "Masamichi HOSODA" <truer...@sea.plala.or.jp>

To: <d...@gnu.org>
Cc: <lilypond-devel@gnu.org>
Sent: Monday, August 31, 2015 3:17 PM
Subject: Re: 2.19.26 regtests



There's lots of differences, presumably down to font changes,


Also sans \bold and \italic do not seem to work in
font-family-override.ly


Well, I call uh-oh.  It will probably take a few more unstable releases
to shake out the problems from the font setup changes.


Probably, it caused by URW fonts problem and/or Pango version.

In my experiment, with newest URW fonts release (commit date is 
2015-08-28)

and newest Pango (version 1.36.8, 2014-09), there is no problem.
Attached file is the result.


First, the previous URW fonts release (commit date is 2015-08-25) seems 
broken.

It has "Nimbus Sans Regular", "Nimbus Sans L Bold",
"Nimbus Sans L Regular Italic", "Nimbus Sans L Bold Italic".
Only "Regular" font's family name is "Nimbus Sans"
but others are "Nimbus Sans L".

http://bugs.ghostscript.com/show_bug.cgi?id=696089
http://git.ghostscript.com/?p=urw-core35-fonts.git;a=commitdiff;h=ee2beed6

The newest URW fonts release has no "Nimbus Sans" but "Nimbus Sans L".

http://git.ghostscript.com/?p=urw-core35-fonts.git;a=commit;h=c983ed400dc278dcf20bdff68252fad6d9db7af9


Next, we use old Pango (version 1.28.3, 2010-09) in GUB.
In four years, many bugs would have been fixed.


So I'll make a GUB's patch that updates URW fonts and Pango.


Would I create an Issue on tracker?
How can I do so?
Or, would someone create it?








___
lilypond-devel mailing list
lilypond-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-devel




___
lilypond-devel mailing list
lilypond-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-devel

Re: 2.19.26 regtests

2015-08-31 Thread Masamichi HOSODA 
>>>There's lots of differences, presumably down to font changes,
>>
>> Also sans \bold and \italic do not seem to work in font-family-override.ly
> 
> And in kievan-notation.ly the spacing of the lyrics in-syllable is
> awful.  Whatever font we chose there has metrics that appear hardly
> suitable to me for running text.

kievan-notation.ly seems to use DejaVu Serif.
It should be Linux Libertine like utf-8.ly using.
I'll make a patch.
___
lilypond-devel mailing list
lilypond-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-devel

Re: 2.19.26 regtests

2015-08-30 Thread David Kastrup 
Phil Holmes m...@philholmes.net writes:

 There's lots of differences, presumably down to font changes, but I'd like 
 someone who understands autochange to look at

 autochange-inside-grace.ly

 http://lilypond.org/test/v2.19.26-1/compare-v2.19.25-1/index.html

 Is this change expected?

Yes, this change is expected and a bug fix.

See URL:https://code.google.com/p/lilypond/issues/detail?id=4569#c2.

Since \autochange no longer moves from an existing Voice into the first
Voice of the up Staff at startup, the final c' is typeset where
\autochange left the Voice started in the down Staff after the grace
notes.

-- 
David Kastrup

___
lilypond-devel mailing list
lilypond-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-devel

Re: 2.19.26 regtests

2015-08-30 Thread David Kastrup 
Mark Knoop m...@opus11.net writes:

 At 14:41 on 30 Aug 2015, Phil Holmes wrote:
There's lots of differences, presumably down to font changes,

 Also sans \bold and \italic do not seem to work in
 font-family-override.ly

Well, I call uh-oh.  It will probably take a few more unstable releases
to shake out the problems from the font setup changes.

-- 
David Kastrup

___
lilypond-devel mailing list
lilypond-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-devel

Re: 2.19.26 regtests

2015-08-30 Thread David Kastrup 
Mark Knoop m...@opus11.net writes:

 At 14:41 on 30 Aug 2015, Phil Holmes wrote:
There's lots of differences, presumably down to font changes,

 Also sans \bold and \italic do not seem to work in font-family-override.ly

And in kievan-notation.ly the spacing of the lyrics in-syllable is
awful.  Whatever font we chose there has metrics that appear hardly
suitable to me for running text.

-- 
David Kastrup

___
lilypond-devel mailing list
lilypond-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-devel

Re: 2.19.26 regtests

2015-08-30 Thread Mark Knoop 
At 14:41 on 30 Aug 2015, Phil Holmes wrote:
There's lots of differences, presumably down to font changes,

Also sans \bold and \italic do not seem to work in font-family-override.ly

-- 
Mark Knoop

___
lilypond-devel mailing list
lilypond-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-devel