From: <da...@da...> - 2004-08-21 18:58:41
|
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). 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. 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 :-) Dave Malcolm |
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 |
From: Steve C. <g3c...@cd...> - 2004-08-23 17:13:11
|
On Sun, 22 Aug 2004, Tony Graham wrote: > > 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. Well, count me in at least as a tester :) (I'm currently blocked on the gnome-print backend unless I downgrade my libraries, but even if I downgrade I have to fix the FreeType header include problems. I do happen to have time, but I'm devoting myself to some other projects now (yes, it's XSL-related).) -- Steve Cheng 鄭君博 docbook2X: <URL:http://docbook2x.sourceforge.net/> |
From: Tony G. <xm...@me...> - 2004-08-22 23:02:06
|
At 21 Aug 2004 19:58 +0100, da...@da... wrote: > 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). There will also be functions for rendering layouts, lines, and runs since the core Pango rendering functions won't do anything with any extra attributes. One question that needs answering is whether the differences are small enough that the XSL attributes and the rendering functions can be tacked on to the xmlroff tree such that there's really no need to modify Pango at all. The first thing to do is to stub out all the xmlroff functions for the extra XSL attributes and just make an xmlroff that works with the stock Pango attributes. If that can be done, then we need to decide how to go about adding support for the extra XSL attributes. Regards, Tony. |
From: Tony G. <xm...@me...> - 2004-08-23 11:32:53
|
At 23 Aug 2004 00:18 -0400, Tony Graham wrote: ... > One question that needs answering is whether the differences are small > enough that the XSL attributes and the rendering functions can be > tacked on to the xmlroff tree such that there's really no need to > modify Pango at all. The answer to that question is that the different licenses of Pango and xmlroff mean that something based on Pango code shouldn't go under the xmlroff license, but IANAL. Regards, Tony. |