Well this passes make, make check and a full make doc.
But there are a LOT of warnings now (as you say) but a LOT of them in the regi
test
e.g
--snip--
input/regression/mozart-hrn-3.log
@@ -1,21 +1,556 @@
Processing `./mozart-hrn-3.ly'
Parsing...
Renaming input to: `/home/james/lilypond-git/input/regression/mozart-hrn-3.ly'
-Interpreting
music...[8][16][24][32][40][48][56][64][72][80][88][96][104][112][120]
+Interpreting music...
+warning: cannot get font Emmentaler-20 CFF name
+[8][16][24][32][40][48][56][64][72][80][88][96][104][112][120]
Preprocessing graphical objects...
+warning: cannot get font TeXGyreSchola-Bold CFF name
+warning: cannot get font TeXGyreSchola-Bold CFF name
+warning: cannot get font TeXGyreSchola-Bold CFF name
+warning: cannot get font TeXGyreSchola-Bold CFF name
+warning: cannot get font TeXGyreSchola-Bold CFF name
+warning: cannot get font TeXGyreSchola-Bold CFF name
+warning: cannot get font TeXGyreSchola-Bold CFF name
+warning: cannot get font Emmentaler-20 CFF name
+warning: cannot get font Emmentaler-20 CFF name
+warning: cannot get font Emmentaler-20 CFF name
+warning: cannot get font Emmentaler-20 CFF name
+warning: cannot get font Emmentaler-20 CFF name
+warning: cannot get font Emmentaler-20 CFF name
+warning: cannot get font Emmentaler-20 CFF name
+warning: cannot get font Emmentaler-20 CFF name
+warning: cannot get font Emmentaler-20 CFF name
+warning: cannot get font Emmentaler-20 CFF name
+warning: cannot get font Emmentaler-20 CFF name
+warning: cannot get font Emmentaler-20 CFF name
+warning: cannot get font Emmentaler-20 CFF name
+warning: cannot get font Emmentaler-20 CFF name
+warning: cannot get font Emmentaler-20 CFF name
+warning: cannot get font Emmentaler-20 CFF name
+warning: cannot get font Emmentaler-20 CFF name
+warning: cannot get font Emmentaler-20 CFF name
+warning: cannot get font Emmentaler-20 CFF name
+warning: cannot get font Emmentaler-20 CFF name
+warning: cannot get font Emmentaler-20 CFF name
+warning: cannot get font TeXGyreSchola-BoldItalic CFF name
+warning: cannot get font TeXGyreSchola-Regular CFF name
+warning: cannot get font TeXGyreSchola-BoldItalic CFF name
+warning: cannot get font TeXGyreSchola-Regular CFF name
for about 200 lines.
I am using Fedora 23 and this has Freetype 2.6.0
So, I would ask; unless it is simple to update to Freetype 2.6.x where these
warnings go away, are we going to get emails from users asking about all these
'warnings' that they never had before?
A smaller example in the reg test is this:
--snip--
input/regression/music-function-direct-call.log
@@ -2,9 +2,24 @@
Parsing...
Renaming input to:
`/home/james/lilypond-git/input/regression/music-function-direct-call.ly'
Interpreting music...
+warning: cannot get font Emmentaler-20 CFF name
Preprocessing graphical objects...
+warning: cannot get font Emmentaler-20 CFF name
+warning: cannot get font Emmentaler-20 CFF name
+warning: cannot get font Emmentaler-20 CFF name
+warning: cannot get font Emmentaler-20 CFF name
+warning: cannot get font Emmentaler-20 CFF name
+warning: cannot get font Emmentaler-20 CFF name
+warning: cannot get font Emmentaler-20 CFF name
+warning: cannot get font Emmentaler-20 CFF name
+warning: cannot get font Emmentaler-20 CFF name
+warning: cannot get font Emmentaler-20 CFF name
+warning: cannot get font TeXGyreSchola-Regular CFF name
+warning: cannot get font TeXGyreSchola-Regular CFF name
Calculating line breaks...
Drawing systems...
+warning: cannot get font TeXGyreSchola-Italic CFF name
+warning: cannot get font TeXGyreSchola-Italic CFF name
Writing header field `texidoc' to `./music-function-direct-call.texidoc'...
Writing ./music-function-direct-call-1.signature
Layout output to `./music-function-direct-call.eps'...
--snip--
We can make recommendations to install FreeType version X but it has to be
simple to do this for users for whatever distribution they might use - we
cannot really just use Ubuntu as a baseline I don't think.
Also, as I test patches are the reg tests going to be full of these messages
all the time if this were to get pushed and I didn't have Freetype 2.6.1 or 2?
James
---
** [issues:#4876] The wrong font name is embedded by using some OTF / OTC
fonts**
**Status:** Started
**Created:** Thu Jun 02, 2016 03:00 PM UTC by Masamichi Hosoda
**Last Updated:** Sat Jun 25, 2016 05:03 PM UTC
**Owner:** Masamichi Hosoda
If I understand correctly, this caused by FreeType 2.5.5 or earlier.
For example, if you use a non-Japanese (e.g. Chinese or Korean) font in
NotoSansCJK.ttc ver. 1.004, FreeType 2.5.5 gets a Japanese postscript name.
Therefore, LilyPond might embed the fonts with wrong postscript name if you use
FreeType 2.5.5 or earlier.
Even if the name is wrong, the glyphs are correct.
FreeType 2.6+ is fixed it.
For LilyPond official site's binaries:
Current GUB uses FreeType 2.4.12.
So I'm making the GUB's patch which update FreeType.
For others:
Bump up required or recommended version of FreeType?
---
Sent from sourceforge.net because [email protected] is
subscribed to https://sourceforge.net/p/testlilyissues/issues/
To unsubscribe from further messages, a project admin can change settings at
https://sourceforge.net/p/testlilyissues/admin/issues/options. Or, if this is
a mailing list, you can unsubscribe from the mailing list.
------------------------------------------------------------------------------
Attend Shape: An AT&T Tech Expo July 15-16. Meet us at AT&T Park in San
Francisco, CA to explore cutting-edge tech and listen to tech luminaries
present their vision of the future. This family event has something for
everyone, including kids. Get more information and register today.
http://sdm.link/attshape
_______________________________________________
Testlilyissues-auto mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/testlilyissues-auto
