At 16:06 25.05.03 +0200, Sven Neumann wrote: >Hi, > >Hans Breuer <Hans@xxxxxxxxxx> writes: > >> - GIMP's direct usage of fontconfig >> IMO fontconfig is a X-only library which shouldn't be ported >> to win32. Why should one want to inherit the mess which X fonts >> are on a platform with better font support built-in ? > >fontconfig has nothing to do with X11. It is not dependant on any X11 >libraries. > I know. As noted in my previous mail. Yet I'm still not able to compile it with msvc. And I'm still not convinced it is useful on win32 in it's current shape. One of the goals of Pango's fontconfig usage was to use the *same* font configuration with different backends. This goal is certainly not reached on win32. >> - GIMP's dependency on pangoft2 (1.2) >> The dependency on Ft2 isn't such severe as the fontconfig one, >> but pangoft2-1.2 does depend on fontconfig. >> http://mail.gnome.org/archives/gtk-devel-list/2002-June/msg00008.html >> >> I'm still convinced that the native pangowin32 backend should be >> the first class citizen on win32, but I appear to be the only one: >> http://bugzilla.gnome.org/show_bug.cgi?id=94791 >> has the rotten bits :) > >IMO we should render text with the same backend on all platforms. Same >holds true for selecting fonts. We use PangoFT2 and fontconfig since >they provide a platform-independent architecture for this. > http://bugzilla.gnome.org/show_bug.cgi?id=113681 should have had some additional notes of mine, but cause it already is in the state of WONTFIX without them, here they are: Feel free to have IMHO impossible goals: - having the *exactly* same results with fonts on different platforms would require to use the same font file (may be possible with M$ webfonts) - ... and let the application find it. Even PangoFT2 offers the ability to add aliases to address fonts. AFAIK there is no way (but including the font vectors) to assure that the same name resolves to the same vectors, i.e. font file - Delivering font vectors would be possible as a PangoWin32 extensions as well. But I'm still not sure how much looking into the future is acceptable. Almost two years ago Sven had the same reasoning against the 'Pango Backend Abstraction' http://mail.gnome.org/archives/gtk-devel-list/2001-August/msg00627.html The only thing GIMP currently does is rendering to bitmap ... - affine transformation on fonts (or better text) would probably be done with the bitmap (not with the vector ?). With more backends supporting rendering to bitmap it would be simple to keep the GIMP code the same for all platforms. To me the first 'is a must' is being able to render text at all. Which I am with the pangowin32 backend but _not_ with pangoft2. Also having two font backends with independent configuration is not only a waste of disk/memory space and performance but also the source of inconvinients for users: - different lists of fonts depending on the configuration dialog used (either Gtk built-in or GIMP's) - Fontlist of pangoft2/fontconfig probably does not match the rest of the platform fontlists in native programs - Additional configuation (file) required Anyway: the PangoFt2/fontconfig thing is probably a WONTFIX for me. As a result my GIMP version will diverge from the CVS version ... Thanks for your fast (not so educated?) decision. >> - Some brokeness of glib::g_spawn_async on win32 >> Without patching it The Gimp can't talk to it's plug-ins anymore. >> Although I have a patch it is probably too dirty to be included >> in GLib ... > >Is it in Bugzilla? If not, please do file a bug-report for it asap. > Info appended to http://bugzilla.gnome.org/show_bug.cgi?id=98737 Hans -------- Hans "at" Breuer "dot" Org ----------- Tell me what you need, and I'll tell you how to get along without it. -- Dilbert
