Re: [python-win32] GDI+ text rendering screwed up

2009-03-19 Thread Greg Ewing
Turns out I *sort* of have a font called Times... I've got "Times Bold", "Times Italic" and "Times Bold Italic", but no plain "Times"! "Times New Roman" works fine, though, and it seems that the same is true of all the other fonts for which there is a full set of variations. So it looks like I'l

Re: [python-win32] GDI+ text rendering screwed up

2009-03-19 Thread Greg Ewing
Tim Roberts wrote: Sadly, I see "Times Italic 48" in black-on-yellow. Do you really have a font called "Times"? I'm not sure, but I can use the name "Times" with plain GDI and it works fine, so it seems to be able to find something equivalent. But I'll try using the exact name and see if it

Re: [python-win32] GDI+ text rendering screwed up

2009-03-19 Thread Tim Roberts
Greg Ewing wrote: > I'm trying to use GDI+ (via ctypes) to draw text. > It works for some fonts but messes up with others. > Using Times, for example, it seems to be using the > glyphs for one character earlier in the code sequence, > so that "Times" comes out as "Shldr" -- except that it > uses th

[python-win32] GDI+ text rendering screwed up

2009-03-19 Thread Greg Ewing
I'm trying to use GDI+ (via ctypes) to draw text. It works for some fonts but messes up with others. Using Times, for example, it seems to be using the glyphs for one character earlier in the code sequence, so that "Times" comes out as "Shldr" -- except that it uses the widths of the original char