Re: [gnome-print] PATCH: Make libgnomeprint use fontconfig if it'savailable.

[Chema Celorio <chema ximian com>]

Tambet,

This patch is great. However, this is the "soft" move to fontconfig. For
HEAD we want a definite move and get rid of as much of the old code as
possible. Can you improve the patch in this way? Think about killing the
old fontmap forever (and making our lives better in the process). No
need to detect in configure if it is there to set a flag, if it isn't
there, it should not compile.

great job,
Chema

On Wed, 2002-10-02 at 13:17, Tambet Ingo wrote:
> It's a diff against cvs HEAD of libgnomeprint.
> 
> If fontconfig is detected by configure, it is used, otherwise it falls
> back to old behavior (gnome-print's own fontmap files).
> 
> It isn't tested much, and for some reason, freetype can't get unicode
> charmap for some (few, namely webdings, windings) fonts.
> 
> It's quite hacky, since I didn't want to make big changes. It should be
> possible (and right way to do it) to get all information about fonts
> from fontconfig and we could remove direct freetype/type1 access from
> gnome-print...
> 
> 
> Another thing, I think there is no reason to keep GnomeFontDialog in
> libgnomeprint, it's already in libgnomeui (and Gtk) (correct me if I'm
> wrong).
> 
> As a result, we have unified font backend with pango plus we can (soon)
> remove gnome-font-installer and gnome-font-dialog code to make
> gnome-print's codebase much smaller.
> 
> -- 
> Tambet Ingo <tambet@ximian.com>
-- 
Chema Celorio <chema@ximian.com>