That's duplicating my results on Gentoo, too. I guess that confirms that this one is upstream.
-FM On 9/4/08, Lenard Lindstrom <[EMAIL PROTECTED]> wrote: > Attached is a C version of font_test.py. It takes a font size as its > only argument. Running the program for both pitch 21 and 210 I get the > same results as I get for font_test.py. > > Lenard > > > Lenard Lindstrom wrote: >> >> I can't account for why the numbers match at a pitch of 210, but not >> 21. I did find the place in SDL_ttf where the dpi is set to the >> FreeType default of 72. And the post to the FreeType mailing list I >> referred to earlier, >> http://lists.nongnu.org/archive/html/freetype-devel/2002-08/msg00020.html, >> >> does imply that font size, in pixels, is affected by some operating >> system provided value. But then this could involve values passed to >> FreeType or FreeType as a display driver. On Windows there are no >> explicit Windows api calls, just C library calls. So I don't know what >> I imply any more. Maybe a C only version of font_test.py will clear >> some things up. >> >> Lenard >> >> >> Brian Fisher wrote: >>> Lenard, are you saying you think it still may be a dpi problem? >>> >>> cause I think if dpi was the problem in this case, the discrepancy >>> would scale with font size. But as there is no discrepancy between >>> the platforms when the font size is 210 (i.e. charlies gentoo matches >>> your windows box), it seems to me that dpi (or any font scaling >>> really) is not different, and therefore not the cause here >>> >>> I really think SDL_ttf is fixing the freetype scaling so it doesn't >>> vary with platform. It would just make sense. >>> >>> did I misunderstand or am I missing something there? >>> >>> >>> On Thu, Sep 4, 2008 at 1:38 PM, Lenard Lindstrom <[EMAIL PROTECTED] >>> <mailto:[EMAIL PROTECTED]>> wrote: >>> >>> As for display point size, that may be the case with Windows, but >>> what about Unix. >>> >>> >> >> > >
