If someone wanted to port fontconfig to support libxml2, I'm sure the patch would get accepted, were it reasonable. The code actually used to have a configure option to use libxml2 instead, but it was not getting the maintanence it needed, so it was removed.
Beyond that, the only other thing which I care about that uses expat, is the XML::Parser perl module, which we require for intltool. Most everything else in terms of Gnome, use libxml2 anyway. Gnumeric, Abiword, the background capplet, gconf, etc... all use libxml2. -- dobey On Tue, 2005-08-23 at 22:06 +0200, Emmanuele Bassi wrote: > Hi all, > > On Tue, 2005-08-23 at 13:25 +0100, Alberto Manuel Brandão Simões wrote: > > I am entering into the discussion thread without reading any other email > > than this one, but... as for XML we should not create the wheel again. > > > > That leads to libxml2 or expat. In my case, I prefer libxml2. Being part > > of w3c development maybe helps me choosing it. Well, having work with > > expat a long time ago when it was slower than libxml2 might help my > > decision as well. > > Gtk already depends, albeit inderectely, on expat by depending on > fontconfig. > > Anyway, I'd like a dependency on libxml2, since my RecentManager code > uses it for the storage file. > > Just my .02€ > > Ciao, > Emmanuele. > _______________________________________________ desktop-devel-list mailing list desktop-devel-list@gnome.org http://mail.gnome.org/mailman/listinfo/desktop-devel-list