Need a registry for cairo fonts on win32 (instead of the horrible hack that's in there now)

[GoogleCodeExporter]

Currently on win32, enso/graphics/font.py uses a hard-coded path to the
Arial font file as an argument to cairo.

This is bad.  Not only is Arial a horribly ugly font, but this is win32
specific code in the core and it's a hard-coded path which may be incorrect
on some systems.

What we really want is a mini font registry in the win32 implementation of
cairo.  Then the Enso core can simply always pass a font name into cairo
and the win32 implementation of cairo can use the font registry to look up
the path to the font file.

Also, the font that Enso uses should be specified in the config file.

Original issue reported on code.google.com by ebj...@gmail.com on 21 Mar 2008 at 5:25

[GoogleCodeExporter]

Original comment by ebj...@gmail.com on 21 Mar 2008 at 5:36

• Added labels: Milestone-Release0.1

[GoogleCodeExporter]

Guillaume said on IRC that it's in Cairo's plans for their next release to allow
custom font registration, so we may want to look into whether any of this is
implemented yet, or if we can help implement it.

It may also be useful to use the same mechanism on OSX, as it could potentially 
cut
its dependency on fontconfig, making cairo easier to compile and package 
statically
with Enso.

Original comment by var...@gmail.com on 24 Mar 2008 at 4:00

[GoogleCodeExporter]

Because of its potential relevance to OSX, I've added the OSX label to this 
issue.

Original comment by var...@gmail.com on 24 Mar 2008 at 4:00

• Added labels: OpSys-OSX

[GoogleCodeExporter]

The Cairo roadmap (http://cairographics.org/roadmap/) states that this is 
planned for
1.8, planned for at best November 2008, and there doesn't seem to be much 
available
yet for User Fonts, sadly.

Original comment by ixce...@gmail.com on 24 Mar 2008 at 4:19