From: Tony G. <Ton...@Su...> - 2004-08-22 10:56:10
|
I answered this yesterday, but my reply seems to have been redirected to /dev/null. I didn't even get a copy of it. da...@da... wrote at Sat, 21 Aug 2004 19:58:37 +0100: > I'm trying to set up a build environment for xmlroff using jhbuild. I > want to eliminate PangoPDF (and eventually do everything use Cairo and > gnome-print). > > So I've hacked the xmlroff configure.in so that it doesn't look for > PangoPDF, and I plan to apply the various minimal necessary changes > directly into the environment's version of Pango (basically just add the > xsl attribute stuff, as far as I can make out). An idea whose time has come. > I've tried downloading Pango and PangoPDF tarballs and diffing between > them, but there's too much "noise" caused by minor differences between > the original Pango source the PangoPDF source was created from, and the > Pango tarball I'm diffing against. > > So is there a patch somewhere containing a minimal set of changes that I > can apply to a checkout of Pango from CVS that will let me build xmlroff > against it directly? > > I've tried copying the pango/pango-xsl-attribute* files directly into > the Pango source tree, but there seems to have been a reorganisation in > which a bunch of static attribute manipulation functions have been > semi-exposed in a "private" header. That was mostly me. This time around, I'm prepared to copy the structures and functions for the 'int' and 'float' PangoAttribute types rather than mess with the internals of the Pango files. [1] Also, the variants of render_layout that take ranges of lines could be dispensed with by rendering the full layout but cropping it to the area of interest. > So before going any further down this path I was wondering if what I'm > proposing is sane, and I'm hoping Tony Graham has a ready-made patch > like this on his hard-drive somewhere :-) Not yet. We should collaborate. Regards, Tony. [1] http://bugzilla.gnome.org/show_bug.cgi?id=116115 |