I'd like to thank all those who participated in fixing this bug. It's much
appreciated.
David
2007/10/29, John Hunter <[EMAIL PROTECTED]>:
>
> On 10/29/07, Michael Droettboom <[EMAIL PROTECTED]> wrote:
>
> > I submitted a fix for this in matplotlib SVN r4047. Freetype takes a
> > FT_LOAD_FORCE_A
On 10/29/07, Michael Droettboom <[EMAIL PROTECTED]> wrote:
> I submitted a fix for this in matplotlib SVN r4047. Freetype takes a
> FT_LOAD_FORCE_AUTOHINT flag to force it to bypass the patented bytecode
> hinter at runtime (even if it was compiled in). This appears to fix the
> problem, and doe
Le Monday 29 October 2007 10:57:52 Darren Dale, vous avez écrit :
> On Monday 29 October 2007 10:45:22 am Michael Droettboom wrote:
> > Darren Dale wrote:
> > > On Monday 29 October 2007 10:09:21 am Michael Droettboom wrote:
> > >> Michael Droettboom wrote:
> > >>> Darren Dale wrote:
> > I thi
On Monday 29 October 2007 10:45:22 am Michael Droettboom wrote:
> Darren Dale wrote:
> > On Monday 29 October 2007 10:09:21 am Michael Droettboom wrote:
> >> Michael Droettboom wrote:
> >>> Darren Dale wrote:
> I think the problem is related to autohinting. When I compile
> freetype, the
Darren Dale wrote:
> On Monday 29 October 2007 10:09:21 am Michael Droettboom wrote:
>> Michael Droettboom wrote:
>>> Darren Dale wrote:
I think the problem is related to autohinting. When I compile freetype,
the patented bytecode and subpixel hinting support is disabled, I am
using
[My original response to the list got bounced because it included zip files. I
am posting again without the attachments.]
I attached the results (_b is with BROKEN = 0). I didn't notice any problems
in the Vera test, but in cmmi, Delta has problems when BROKEN is 1, it looks
better when BROKEN
On Monday 29 October 2007 10:09:21 am Michael Droettboom wrote:
> Michael Droettboom wrote:
> > Darren Dale wrote:
> >> I think the problem is related to autohinting. When I compile freetype,
> >> the patented bytecode and subpixel hinting support is disabled, I am
> >> using freetype's autohinting
Michael Droettboom wrote:
> Darren Dale wrote:
>> I think the problem is related to autohinting. When I compile freetype, the
>> patented bytecode and subpixel hinting support is disabled, I am using
>> freetype's autohinting instead. I recompiled freetype with the support for
>> the patented hi
Thanks for that. You really downplayed the problems when BROKEN is 1.
It seems to me that most of the glyphs are very bad -- the 'e', for
instance, is filled in the middle.
Darren Dale wrote:
> I think the problem is related to autohinting. When I compile freetype, the
> patented bytecode and
I should also mention -- please let me know if setting BROKEN to 0 fixes
any rendering problems.
Cheers,
Mike
Michael Droettboom wrote:
> Forgot to attach the program.
>
> Michael Droettboom wrote:
>> Nicolas, Darren,
>>
>> I have created a minimal program that hopefully will exercise the
>> p
Forgot to attach the program.
Michael Droettboom wrote:
Nicolas, Darren,
I have created a minimal program that hopefully will exercise the
problem. If it breaks for either of you, I'll take this to the freetype
mailing list for further clarification... If it doesn't break for you,
my theor
Nicolas, Darren,
I have created a minimal program that hopefully will exercise the
problem. If it breaks for either of you, I'll take this to the freetype
mailing list for further clarification... If it doesn't break for you,
my theory about the cause is still incorrect.
I have attached a sm
More information -- I just compiled matplotlib on a communal RHEL4
64-bit installation, and I still can not reproduce this bug there.
The plot thickens...
Cheers,
Mike
Michael Droettboom wrote:
> Thanks for this information. It looks like the font outline data is
> somehow getting corrupted b
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
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 bit more what I tr
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
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 installe
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). 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 looks
of them, I do
I can't reproduce this bug on my own machine with SVN head. I suspect
this is freetype2 related -- that's the library that actually performs
the rendering of the characters for the Agg backend. The fact the
humufr saw this after upgrading to Gutsy suggests there might have been
change to fr
Sorry I didn't know the difference...
N.
Le Friday 19 October 2007 10:52:25 Darren Dale, vous avez écrit :
> On Friday 19 October 2007 10:38:36 am [EMAIL PROTECTED] wrote:
> > Le Friday 19 October 2007 08:37:00 Darren Dale, vous avez écrit :
> > > On Thursday 18 October 2007 11:49:50 am [EMAIL PR
On Friday 19 October 2007 10:38:36 am [EMAIL PROTECTED] wrote:
> Le Friday 19 October 2007 08:37:00 Darren Dale, vous avez écrit :
> > On Thursday 18 October 2007 11:49:50 am [EMAIL PROTECTED] wrote:
> > > Hi,
> > >
> > > I have a small problem with label.
> > >
> > >
> > > plot([0,1],[0,1])
> >
Oups I found the problem, I don't know why because it was working fine before
the upgrade to gutsy but I have to change matplotlib configuration and
everything is working fine if I put in the file:
rc('text', usetex=True)
sorry to have bother you with this,
N.
Le Friday 19 October 2007 08:37:
I don't think the problem is in dvipng because I have exactly the same when
I'm using GtkAgg and before your message I didn't have dvipng installed. I'm
using ubuntu gutsy so perhaps there are a change in the lib.
N.
Le Friday 19 October 2007 08:37:00 Darren Dale, vous avez écrit :
> On Thursd
On Thursday 18 October 2007 11:49:50 am [EMAIL PROTECTED] wrote:
> Hi,
>
> I have a small problem with label.
>
>
> plot([0,1],[0,1])
> xlabel(r'$ABCDEF$',fontsize=35)
>
> (but the size doesn't change anything) I obtain the result visible on the
> figure join. I think there are a problem when
Hi,
I have a small problem with label.
plot([0,1],[0,1])
xlabel(r'$ABCDEF$',fontsize=35)
(but the size doesn't change anything) I obtain the result visible on the
figure join. I think there are a problem when using latex and how the first
character is handle.
Thanks for matplotlib.
25 matches
Mail list logo
