From: <hu...@ya...> - 2007-10-26 16:03:05
|
Le Friday 26 October 2007 11:22:06, vous avez =E9crit=A0: > Thanks for this information. It looks like the font outline data is > somehow getting corrupted before freetype renders it. Again, however, I > can't reproduce it on my machine (I've attached a copy of what it looks > like for me), so I'm still pretty stumped. My suspicion is that it's a > 64-bit vs. 32-bit problem since both people known to have trouble are on > 64-bit platforms, and I am not. I have tried recompiling with gcc-4.2.2 > and I still wasn't able to reproduce. I can imagine that it's difficult for you to debug something you cannot=20 reproduce. Just a remark I don't have 64-bits but a 32 so the problem is no= t=20 comming because of the plateforme. > One thing you could *try*, to rule out any recent changes to the glyph > rendering, is to comment out this line near the top of src/ft2font.cpp: > > #define VERTICAL_HINTING > > as follows > > //#define VERTICAL_HINTING Yes it's doing the trick., I don't have anymore the problem. Thank you very= =20 much. I have now the same result than you with the test I produce before. > Additional information: Are there any warnings produced when compiling > ft2font.cpp? Can you send me your matplotlibrc file? just the classic one: cc1plus: warning: command line option "-Wstrict-prototypes" is valid for=20 Ada/C/ObjC but not for C++ Thank you very much. N. > Cheers, > Mike > > hu...@ya... wrote: > > Yep that can be a good idea. I don't know anything on how mathtext is > > working but I'm not completely sure that the problem is with freetype > > because sometime that can work. In reality every character I tested > > worked but you have to put in a certain order. To understand a little b= it > > more what I try to say (very badly) see the script join and the figure. > > > > I hope that can help a little bit to try to find the reason of this > > behaviour. > > > > N > > > > Le Thursday 25 October 2007 15:41:40 Michael Droettboom, vous avez =E9c= rit : > >> Darren Dale wrote: > >>> Hi Mike, > >>> > >>> On Tuesday 23 October 2007 09:05:56 am Michael Droettboom wrote: > >>>> Unfortunately, I can't reproduce this on my machine even with the > >>>> latest stable version of freetype-2.5.3 (which is the same version in > >>>> Ubuntu Gutsy). > >>> > >>> I think you mean freetype-2.3.5. I also have that version installed, > >>> although the mpl setup script is reporting 9.16.3. > >> > >> Yes. freetype-2.3.5. There are arcane historical reasons I don't ful= ly > >> comprehend why the pkgconfig version doesn't match the release version > >> (and why freetype2 is called freetype6 on Debian and derivatives)... > >> but my numbers do match yours. > >> > >>>> The Ubuntu/Debian package of freetype has a lot of patches > >>>> applied, and I don't know if they are causing this (but from the loo= ks > >>>> of them, I doubt it). > >>>> > >>>> Can you set debug.verbose to "annoying" and send me the output of yo= ur > >>>> matplotlib run? I want to rule out any font-loading problems. > >>> > >>> It's attached. I'm running 64bit gentoo, everything compiled with > >>> gcc-4.2.2, in case its relevent. > >> > >> Always good to have more details, but I'm sort of at a loss on this on= e, > >> especially since I can't reproduce it. > >> > >> Maybe we need to take a poll on this list of who is working and who > >> isn't to see what the source of the breakage may be... > >> > >> Cheers, > >> Mike > >> > >> ----------------------------------------------------------------------= =2D- |