Log file Viewer

[15:51:54] <amaurea> Does PIL have a scalable built-in font I can use instead of having to hard-code a font path? Or does it have som other way to specify a font without needing to refer to a file?

[15:52:42] <wiredfool> I think there's a built in font, but it's a minimalistic bitmap

[15:53:09] <amaurea> Yes, I saw something about a size 10 built-in font

[15:53:26] <amaurea> I guess I could use that, but I would prefer something that I can at least rescale

[15:53:33] <amaurea> A built-in ttf font, for example

[15:53:48] <wiredfool> I think you'd have to go with a ttf file

[15:53:52] <wiredfool> there's nothing built ine

[15:55:00] <amaurea> ok, fair enough. It's not too much of a hassle (just whether my module will be a single file, or a directory with an __init__.py)

[15:55:36] <wiredfool> if you're on windows, it looks like ImageFont.truetype will look in the windows font directory

[15:56:18] <wiredfool> http://effbot.org/imagingbook/imagefont.htm

[15:56:44] <amaurea> I'm not on windows, but I'll try specifying a font without a full path name, and see what happens

[15:58:14] <amaurea> nope, that didn't work

[15:59:43] <wiredfool> yep, looking at the code, it's a win32 thing

[15:59:53] <wiredfool> I should fix that.

[16:00:04] <amaurea> That would be very much appreciated

[16:00:11] <wiredfool> you on osx?

[16:00:16] <amaurea> no, linux

[16:00:26] <wiredfool> ah. the land of the wtf font handling

[16:00:44] <amaurea> On my system, the ttf fonts are in /usr/share/fonts/TTF/, but I don't know if that is standard

[16:01:19] <wiredfool> there are several standards

[16:01:29] <wiredfool> and there's at least one registry

[16:01:40] <wiredfool> no, two.

[16:02:12] <amaurea> this seems like a problem somebody might have already solved

[16:03:36] <amaurea> the sysfont module looks interesting

[16:09:36] <wiredfool> ok, added issue for Pillow. no promises if/when it actually gets done

[16:09:58] <amaurea> thanks

[16:10:06] <amaurea> I will distribute the font fot now