Re: font error in 2.11.36/5 - workaround (not quite)

2007-12-31 Thread Han-Wen Nienhuys
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)

2007-12-31 Thread Risto Vääräniemi

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-24 Thread Risto Vääräniemi

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