Re: Error in glyphs: glyphs with filled loops at different feta font sizes
Compiling the glitch.ly at 17.82 on 2.13.46 on Windows produces perfect output, so it's either specific to an OS, a machine, or a Lilypond build. -- Phil Holmes - Original Message - From: Frank Steinmetzger war...@gmx.de To: lilypond-user@gnu.org Sent: Tuesday, January 18, 2011 4:35 AM Subject: Error in glyphs: glyphs with filled loops at different feta font sizes Hello List, I am having a problem here with Lilypond 2.12.3 on Gentoo Linux. I use a size of 14.14 for my own things, so I haven’t noticed it yet. But now I’ve come across someone else’s documents, which are set at 17.82. There the loop at the tip of the G clef is filled out. And at size 15.87 it’s the 4/4 time signatury glyph that displays incorrectly. Can you tell me how to avoid this? I attached a screenie of the sizes in question and the ly they were made with. I have tried all sizes that are stated in the comment of the attached file. The filled loop also occurs at 11.22, 20 and 22.45. At 25.2 I noticed that the clef’s centre diagonal line has an error at its lower end (the inside of the curve is thicker). Thus I discovered this error in the others as well. Only 12.6 and 14.14 seem to really look normal. I tested it with Okular, Gnome’s PDF viewer and KPDF, they all showed the error. But still I’m attaching the PDF for size 17.82 to test it. -- Gruß | Greetings | Qapla' Emacs is a great operating system, which only lacks a good editor. ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Error in glyphs: glyphs with filled loops at different feta font sizes
I'm using Adobe Reader on Windows XP SP3 machine. Your pdf glitches17.82 displays wrong indeed (however the errors in the display are different with different zoom). Compiling the ly gives perfect output (in attachment). cheers, Janek 2011/1/18 Phil Holmes m...@philholmes.net Compiling the glitch.ly at 17.82 on 2.13.46 on Windows produces perfect output, so it's either specific to an OS, a machine, or a Lilypond build. -- Phil Holmes - Original Message - From: Frank Steinmetzger war...@gmx.de To: lilypond-user@gnu.org Sent: Tuesday, January 18, 2011 4:35 AM Subject: Error in glyphs: glyphs with filled loops at different feta font sizes Hello List, I am having a problem here with Lilypond 2.12.3 on Gentoo Linux. I use a size of 14.14 for my own things, so I haven’t noticed it yet. But now I’ve come across someone else’s documents, which are set at 17.82. There the loop at the tip of the G clef is filled out. And at size 15.87 it’s the 4/4 time signatury glyph that displays incorrectly. Can you tell me how to avoid this? I attached a screenie of the sizes in question and the ly they were made with. I have tried all sizes that are stated in the comment of the attached file. The filled loop also occurs at 11.22, 20 and 22.45. At 25.2 I noticed that the clef’s centre diagonal line has an error at its lower end (the inside of the curve is thicker). Thus I discovered this error in the others as well. Only 12.6 and 14.14 seem to really look normal. I tested it with Okular, Gnome’s PDF viewer and KPDF, they all showed the error. But still I’m attaching the PDF for size 17.82 to test it. -- Gruß | Greetings | Qapla' Emacs is a great operating system, which only lacks a good editor. ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user glitches.pdf Description: Adobe PDF document ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
Error in glyphs: glyphs with filled loops at different feta font sizes
Hello List, I am having a problem here with Lilypond 2.12.3 on Gentoo Linux. I use a size of 14.14 for my own things, so I haven’t noticed it yet. But now I’ve come across someone else’s documents, which are set at 17.82. There the loop at the tip of the G clef is filled out. And at size 15.87 it’s the 4/4 time signatury glyph that displays incorrectly. Can you tell me how to avoid this? I attached a screenie of the sizes in question and the ly they were made with. I have tried all sizes that are stated in the comment of the attached file. The filled loop also occurs at 11.22, 20 and 22.45. At 25.2 I noticed that the clef’s centre diagonal line has an error at its lower end (the inside of the curve is thicker). Thus I discovered this error in the others as well. Only 12.6 and 14.14 seem to really look normal. I tested it with Okular, Gnome’s PDF viewer and KPDF, they all showed the error. But still I’m attaching the PDF for size 17.82 to test it. -- Gruß | Greetings | Qapla' Emacs is a great operating system, which only lacks a good editor.\version 2.12.3 \include deutsch.ly #(set-global-staff-size 14.14) %11.22, 12.6, 14.14, 15.87, 17.82, 20, 22.45, 25.2 upper=\relative c' { c d e f } \score { \new Staff \upper \layout {} }attachment: glitches.png glitches17.82.pdf Description: Adobe PDF document ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Error in glyphs: glyphs with filled loops at different feta font sizes
Hi Frank, I can not reproduce these errors on Ubuntu 10.04 . I have a suspicion that it is your rasterizing engine in your Gentoo that is being fussy and that the errors might be caused by the fact that some of the fonts used by lilypond do not validate properly. Much of the time this will not affect things adversely, but it is a commercial standard that is pretty rigorously adhered to. This means that certain rasterizing engines might get a little mixed up by tracing the wrong direction or things that self overlap or simply missing extremum (points marking outer boundaries and changes of direction) can also cause unreliable results. This of course is a shot in the dark but it makes a fair amount of sense. In any event If I had any idea how lilypond called up which set of fonts for what size it would be simple to make an experiment to see if it is resolvable by correcting those things. Attaching the pdf only will show us what errors your machine has generated as pdf viwers on other machines will display the same errors as the pdf is in its own way an image sort of file. Shane On Mon, Jan 17, 2011 at 11:35 PM, Frank Steinmetzger war...@gmx.de wrote: Hello List, I am having a problem here with Lilypond 2.12.3 on Gentoo Linux. I use a size of 14.14 for my own things, so I haven’t noticed it yet. But now I’ve come across someone else’s documents, which are set at 17.82. There the loop at the tip of the G clef is filled out. And at size 15.87 it’s the 4/4 time signatury glyph that displays incorrectly. Can you tell me how to avoid this? I attached a screenie of the sizes in question and the ly they were made with. I have tried all sizes that are stated in the comment of the attached file. The filled loop also occurs at 11.22, 20 and 22.45. At 25.2 I noticed that the clef’s centre diagonal line has an error at its lower end (the inside of the curve is thicker). Thus I discovered this error in the others as well. Only 12.6 and 14.14 seem to really look normal. I tested it with Okular, Gnome’s PDF viewer and KPDF, they all showed the error. But still I’m attaching the PDF for size 17.82 to test it. -- Gruß | Greetings | Qapla' Emacs is a great operating system, which only lacks a good editor. ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Error in glyphs: glyphs with filled loops at different feta font sizes
I can not reproduce these errors on Ubuntu 10.04. I have a suspicion that it is your rasterizing engine in your Gentoo that is being fussy and that the errors might be caused by the fact that some of the fonts used by lilypond do not validate properly. Another possibility is that the glyphs from the version he uses have been created with a buggy version of FontForge. From time to time the intersection resolution algorithm is broken (for example right now in FontForge's CVS repository), causing exactly such results. Werner ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user