Re: font error in 2.11.36/5 - workaround (not quite)
I'll continue my monologue. :-) Risto Vääräniemi wrote: I think there are two font bugs after all (they could be interrelated, though). One is related to missing accents and the other to substituting all fonts with Verdana. programming error: FT_Get_Glyph_Name () error: invalid argument continuing, cross fingers programming error: Glyph has no name, but font supports glyph naming. Skipping glyph U+, file C:/WINDOWS/fonts/CenturySchL-Ital.otf continuing, cross fingers The missing accented characters issue is probably not caused by any bug. I was able to reproduce the behaviour when I created a LP source file with accents but did not save it as UTF-8. When I converted it to UTF-8 the accented chars were OK. -Risto -- View this message in context: http://www.nabble.com/font-error--in-2.11.36-tp14313181p14556442.html Sent from the Gnu - Lilypond - Bugs mailing list archive at Nabble.com. ___ bug-lilypond mailing list bug-lilypond@gnu.org http://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: font error in 2.11.36/5 - workaround (not quite)
2007/12/31, Risto Vääräniemi [EMAIL PROTECTED]: I'll continue my monologue. :-) Hi, the quick fix is to patch out /type1/ and /otf/ which appear somewhere in the binary lilypond.exe: replace the trailing slash with a \0 character. I hope to release a new versions shortly, which will fix this. -- Han-Wen Nienhuys - [EMAIL PROTECTED] - http://www.xs4all.nl/~hanwen ___ bug-lilypond mailing list bug-lilypond@gnu.org http://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: font error in 2.11.36/5 - workaround (not quite)
Hi again, Risto Vääräniemi wrote: I made some more tests. On my XP box the effect was similar to Martial-3's observations, i.e., dynamic texts and time signature were converted to sans-serif font but lyrics and markups were fine. I was wondering why I got different results on this computer but I finally remembered that I had copied the Lilypond OTF fonts to the Windoze Fonts directory. When did the same trick on my W2k box I got similar results. After that I copied the Type1 Feta fonts to windoze\fonts directory (normal copy paste doesn't work, but command line copy does). After that LP was able to find the Feta font and the output seemed quite OK. I think there are two font bugs after all (they could be interrelated, though). One is related to missing accents and the other to substituting all fonts with Verdana. The trick described above only helps if you're suffering the Verdana font error that was introduced in .36 (cannot find fonts under LP installation dir). If the accents were missing (in .35) it won't bring them back. :-( I made a new installation on my mother's computer (XP Personal in Finnish) and I cannot get accents on the prints even if I copy the OTF and TYPE1 fonts to Windows\Fonts dir. The fonts are restored to normal, though. On my two other computers (XP Pro and W2k both in English) there were no accent problems either with .35 or .36. I wonder if there could be a connection with Windoze language and font (Pango?) errors. When LP is run with -V option it blurts out errors like this: (lilypond.exe:712): Pango-CRITICAL **: pango_coverage_get: assertion `index = 0' failed programming error: FT_Get_Glyph_Name () error: invalid argument continuing, cross fingers programming error: Glyph has no name, but font supports glyph naming. Skipping glyph U+, file C:/WINDOWS/fonts/CenturySchL-Ital.otf continuing, cross fingers If someone is interested in a full print, let me know. -Risto -- View this message in context: http://www.nabble.com/font-error--in-2.11.36-tp14313181p14491636.html Sent from the Gnu - Lilypond - Bugs mailing list archive at Nabble.com. ___ bug-lilypond mailing list bug-lilypond@gnu.org http://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: font error in 2.11.36
I'm not certain if this will be enough info to fix the problem, but I've added it here: http://code.google.com/p/lilypond/issues/detail?id=536 Cheers, - Graham On Thu, 13 Dec 2007 04:01:50 -0800 (PST) Risto Vr__niemi [EMAIL PROTECTED] wrote: Dear All, Martial-3 wrote: Thank for the version 2.11.36 but there are dysfunction with the fonts for dynamics and TimeSignature. It also seems to affect other text features such as lyrics and markup (in Win2k). Example: http://www.nabble.com/file/p14314241/fonttivirhe_36.png Font error -Risto -- View this message in context: http://www.nabble.com/font-error--in-2.11.36-tp14313181p14314241.html Sent from the Gnu - Lilypond - Bugs mailing list archive at Nabble.com. ___ bug-lilypond mailing list bug-lilypond@gnu.org http://lists.gnu.org/mailman/listinfo/bug-lilypond ___ bug-lilypond mailing list bug-lilypond@gnu.org http://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: font error in 2.11.36 - workaround
Dear All, Risto Vääräniemi wrote: It also seems to affect other text features such as lyrics and markup (in Win2k). I made some more tests. On my XP box the effect was similar to Martial-3's observations, i.e., dynamic texts and time signature is converted to sans-serif font but lyrics and markups are fine. I was wondering why I got different results on this computer and I finally remembered that I had copied the LP fonts to the Windoze Fonts directory. When I copied them also on my W2k box I got similar results. Somehow it seems that LP does not find the fonts in its own directory structure and cannot use the Emmentaler font from Windows\Fonts directory. When I ran LP using -V option on .35 and .36 one line caught my eye. LP .36 tries to set: GS_FONTPATH=C:/Program Files/LilyPond/usr/bin/../share/gs/fonts The above-mentioned directory does not exist. I tried to copy the fonts there but nothing really changed. :-( When printing to PS file starts, .35 prints a list of fonts that reside in LP installation path. .36, however, prints a list of fonts from C:\Windows\Fonts directory. When they are compared, the feta-alphabet20.pfa font is replaced by Verdana.ttf, which causes the font weirdness. Then I copied also the Type1 Feta fonts to windoze\fonts directory (normal copy paste doesn't work, but command line copy does). After that LP can find the Feta font and the output seems quite OK. This is probably not the ultimate solution but now I can use the .36. -Risto -- View this message in context: http://www.nabble.com/font-error--in-2.11.36-tp14313181p14372559.html Sent from the Gnu - Lilypond - Bugs mailing list archive at Nabble.com. ___ bug-lilypond mailing list bug-lilypond@gnu.org http://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: font error in 2.11.36 - workaround
Dear All, Risto Vääräniemi wrote: It also seems to affect other text features such as lyrics and markup (in Win2k). I made some more tests. On my XP box the effect was similar to Martial-3's observations, i.e., dynamic texts and time signature were converted to sans-serif font but lyrics and markups were fine. I was wondering why I got different results on this computer but I finally remembered that I had copied the Lilypond OTF fonts to the Windoze Fonts directory. When did the same trick on my W2k box I got similar results. Somehow it seems that .36 does not find the fonts in its own directory structure and cannot use the Feta font from Windows\Fonts directory. When I ran LP using -V option on .35 and .36 one line caught my eye. LP .36 tries to set: GS_FONTPATH=C:/Program Files/LilyPond/usr/bin/../share/gs/fonts The above-mentioned directory does not exist. I tried to copy the fonts there but nothing really changed. :-( When printing to PS file started, .35 output a list of fonts that reside in LP installation path. .36, however, gave a list of fonts in C:\Windows\Fonts directory. The feta-alphabet20.pfa font was not found and was replaced by Verdana.ttf, which caused the font weirdness. After that I copied the Type1 Feta fonts to windoze\fonts directory (normal copy paste doesn't work, but command line copy does). After that LP was able to find the Feta font and the output seemed quite OK. This is probably not the ultimate solution but now I can use the .36. Hopefully it is of some help. -Risto -- View this message in context: http://www.nabble.com/font-error--in-2.11.36-tp14313181p14373910.html Sent from the Gnu - Lilypond - Bugs mailing list archive at Nabble.com. ___ bug-lilypond mailing list bug-lilypond@gnu.org http://lists.gnu.org/mailman/listinfo/bug-lilypond
font error in 2.11.36
Hello Thank for the version 2.11.36 but there are dysfunction with the fonts for dynamics and TimeSignature. Best Regards -- Martial http://cathemline.org inline: 2.11.36.font-bug.jpg___ bug-lilypond mailing list bug-lilypond@gnu.org http://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: font error in 2.11.36
Which operating system? /Mats Martial wrote: Hello Thank for the version 2.11.36 but there are dysfunction with the fonts for dynamics and TimeSignature. Best Regards -- Martial http://cathemline.org ___ bug-lilypond mailing list bug-lilypond@gnu.org http://lists.gnu.org/mailman/listinfo/bug-lilypond -- = Mats Bengtsson Signal Processing Signals, Sensors and Systems Royal Institute of Technology SE-100 44 STOCKHOLM Sweden Phone: (+46) 8 790 8463 Fax: (+46) 8 790 7260 Email: [EMAIL PROTECTED] WWW: http://www.s3.kth.se/~mabe = ___ bug-lilypond mailing list bug-lilypond@gnu.org http://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: font error in 2.11.36
Which operating system? Oops ! winXP ___ bug-lilypond mailing list bug-lilypond@gnu.org http://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: font error in 2.11.36
Dear All, Martial-3 wrote: Thank for the version 2.11.36 but there are dysfunction with the fonts for dynamics and TimeSignature. It also seems to affect other text features such as lyrics and markup (in Win2k). Example: http://www.nabble.com/file/p14314241/fonttivirhe_36.png Font error -Risto -- View this message in context: http://www.nabble.com/font-error--in-2.11.36-tp14313181p14314241.html Sent from the Gnu - Lilypond - Bugs mailing list archive at Nabble.com. ___ bug-lilypond mailing list bug-lilypond@gnu.org http://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: font error in 2.11.36
Martial-3 wrote:
Hello
Thank for the version 2.11.36
but there are dysfunction with the fonts
for dynamics and TimeSignature.
With 2.11.36 on WinXP: the abcdef text below is not in italic in the pdf,
but the ghij is in italic. Is there something wrong in my code? Bug or
feature?
%%
\include italiano.ly
\version 2.11.36
{ do'^\markup { \column { \override #'(font-name . Times New Roman)
\italic abcdef \italic \bold \smaller ghij} } re' mi' fa' sol' }
%%
--
View this message in context:
http://www.nabble.com/font-error--in-2.11.36-tp14313181p14314234.html
Sent from the Gnu - Lilypond - Bugs mailing list archive at Nabble.com.
___
bug-lilypond mailing list
bug-lilypond@gnu.org
http://lists.gnu.org/mailman/listinfo/bug-lilypond
Italic Times New Roman. Was: font error in 2.11.36
sdfgsdhdshd wrote:
With 2.11.36 on WinXP: the abcdef text below is not in italic in the pdf,
but the ghij is in italic. Is there something wrong in my code? Bug or
feature?
%%
\include italiano.ly
\version 2.11.36
{ do'^\markup { \column { \override #'(font-name . Times New Roman)
\italic abcdef \italic \bold \smaller ghij} } re' mi' fa' sol' }
%%
First of all, this has nothing to do with the font error in 2.11.36.
Also, I hope you realize that your code only changes the font name
of the abcdef but not on ghij. You could also simplify it somewhat
as
markup { \italic \column { \override #'(font-name . Times New Roman)
abcdef \bold \smaller ghij} }
However, this doesn't answer your question. If you read the
documentation of the
font related properties at
http://lilypond.org/doc/v2.11/Documentation/user/lilypond-internals/font_002dinterface#font_002dinterface
it says that if you specify the font-name, then you override any
settings of
font-family, font-series and font-shape. In other words, setting the
font-name
is a more low-level operation than setting the other font-related
parameters.
So, if you want to use the font-name property, you have to specify the
name of the
Italic version of the font, i.e.
\override #'(font-name . Times New Roman Italic)
/Mats
___
bug-lilypond mailing list
bug-lilypond@gnu.org
http://lists.gnu.org/mailman/listinfo/bug-lilypond
