You can subscribe to this list here.
2003 |
Jan
|
Feb
(8) |
Mar
(38) |
Apr
(13) |
May
(17) |
Jun
(9) |
Jul
(31) |
Aug
(5) |
Sep
|
Oct
(9) |
Nov
(8) |
Dec
(8) |
---|---|---|---|---|---|---|---|---|---|---|---|---|
2004 |
Jan
(8) |
Feb
(2) |
Mar
(10) |
Apr
(1) |
May
(6) |
Jun
(4) |
Jul
|
Aug
(32) |
Sep
(20) |
Oct
(26) |
Nov
(2) |
Dec
(1) |
2005 |
Jan
(6) |
Feb
(9) |
Mar
(69) |
Apr
(13) |
May
(7) |
Jun
(21) |
Jul
(9) |
Aug
(21) |
Sep
(28) |
Oct
|
Nov
(15) |
Dec
(1) |
2006 |
Jan
(32) |
Feb
(47) |
Mar
(44) |
Apr
(10) |
May
(5) |
Jun
(7) |
Jul
(21) |
Aug
(5) |
Sep
(1) |
Oct
|
Nov
|
Dec
(4) |
2007 |
Jan
|
Feb
(12) |
Mar
(7) |
Apr
(10) |
May
(1) |
Jun
|
Jul
|
Aug
(1) |
Sep
|
Oct
|
Nov
|
Dec
|
2008 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
(1) |
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
From: Tony G. <Ton...@Su...> - 2004-03-23 14:23:11
|
Luke, Please subscribe to the xmlroff-list mailing list if you are interested in further discussing xmlroff. Luke Deller <ld...@xp...> wrote at Tue, 23 Mar 2004 14:21:46 +1100: > It looks like something has been incompletely checked into CVS? When I > try to build xmlroff from cvs, I get this error: Please try again after a CVS update. I have checked in all my updated files. There is a problem with the border-*-width properties, but you should be able to compile xmlroff successfully. Regards, Tony Graham ------------------------------------------------------------------------ Web Products, Technologies and Standards Phone: +353 1 8199708 Sun Microsystems x(70)19708 East Point Business Park, Dublin 3, Ireland |
From: Luke D. <ld...@xp...> - 2004-03-23 03:22:12
|
Hi, It looks like something has been incompletely checked into CVS? When I try to build xmlroff from cvs, I get this error: /bin/sh ../libtool --mode=compile gcc -DHAVE_CONFIG_H -I. -I. -I.. -DG_LOG_DOMAIN=\"libfo\" -I/usr/include/libxml2 -I/usr/include/glib-2.0 -I/usr/lib/glib-2.0/include -I.. -I../datatype -I../expr -I../fo -g -O2 -I/usr/local/stow/pango-1.2.3.5/include/pangopdf/pango-1.0 -I/usr/include/freetype2 -I/usr/include/glib-2.0 -I/usr/lib/glib-2.0/include -I/usr/include -I/usr/include/freetype2 -Wall -c -o fo-property-eval.lo `test -f 'fo-property-eval.c' || echo './'`fo-property-eval.c gcc -DHAVE_CONFIG_H -I. -I. -I.. -DG_LOG_DOMAIN=\"libfo\" -I/usr/include/libxml2 -I/usr/include/glib-2.0 -I/usr/lib/glib-2.0/include -I.. -I../datatype -I../expr -I../fo -g -O2 -I/usr/local/stow/pango-1.2.3.5/include/pangopdf/pango-1.0 -I/usr/include/freetype2 -I/usr/include/glib-2.0 -I/usr/lib/glib-2.0/include -I/usr/include -I/usr/include/freetype2 -Wall -c fo-property-eval.c -MT fo-property-eval.lo -MD -MP -MF .deps/fo-property-eval.TPlo -fPIC -DPIC -o .libs/fo-property-eval.lo fo-property-eval.c: In function `fo_property_eval_init_hash': fo-property-eval.c:116: error: `fo_property_margin_bottom_new_from_expression' undeclared (first use in this function) fo-property-eval.c:116: error: (Each undeclared identifier is reported only once fo-property-eval.c:116: error: for each function it appears in.) fo-property-eval.c:118: error: `fo_property_margin_right_new_from_expression' undeclared (first use in this function) fo-property-eval.c:119: error: `fo_property_margin_top_new_from_expression' undeclared (first use in this function) make[2]: *** [fo-property-eval.lo] Error 1 make[2]: Leaving directory `/home/luked/xmlroff/property' make[1]: *** [all-recursive] Error 1 make[1]: Leaving directory `/home/luked/xmlroff' make: *** [all] Error 2 I configured xmlroff with: PKG_CONFIG_PATH=/usr/local/stow/pango-1.2.3.5/lib/pkgconfig ./configure --prefix=/home/luked/stow/xmlroff --disable-gp Regards, Luke. |
From: Tony G. <Ton...@Su...> - 2004-03-16 16:45:55
|
Dave Malcolm <da...@da...> wrote at Fri, 12 Mar 2004 00:45:45 +0000: > I noticed from this recent "commit" that libgnomeprint appears to now > support printing a PangoLayout to a GnomePrintContext. > > I thought I'd mention it in case this is relevant/of use. I'm glad that you saw that since the new files don't even show up in the libgnomeprint ChangeLog. It is useful as long as xmlroff doesn't need or use any additional Pango attributes. For example, the PDFlib backend uses a 'callback' attribute type for handling fo:external-graphic. (There used to be more non-standard Pango attributes in use before Pango moved to using fontconfig and blew away the code on which the extra attributes were based.) Lines 134-138 in gnome-print-pango.c don't appear to do anything. It would be nice to be able to get away from building GnomeGlyphLists for the GNOME Print backend. This would be most useful if it is coupled with an upgrade to basing PangoPDF on Pango 1.3.* where the Pango modules are common across Pango backends. Anybody for a bit of PangoPDF hacking? Regards, Tony Graham ------------------------------------------------------------------------ Web Products, Technologies and Standards Phone: +353 1 8199708 Sun Microsystems x(70)19708 East Point Business Park, Dublin 3, Ireland |
From: Tony G. <Ton...@Su...> - 2004-03-16 16:17:55
|
Dave Malcolm <da...@da...> wrote at Fri, 12 Mar 2004 15:14:05 +0000: > On Fri, 2004-03-12 at 01:41, Dave Malcolm wrote: > > I've been having a look at xmlroff and libfo after a long break. It > > struck me that there's a lot in common between the FoDoc subclasses and > > a Cairo context. > > > > See http://cairographics.org/ > > > > There's currently a fair amount of momentum behind the Cairo project (it > > has the author of Pango and of the X Render extension on board) - so it That explains the reference to Cairo in my Pango feature request for Pango to have a GNOME Print context. > > might be worth supporting a FoDocCairo backend. Is it worth me > > attempting a patch? > > Alas, looking deeper, I'm not sure I'd be able to achieve much more than > sending the pages as a series of fully composited pixbufs to the > printer/PDF - not necessarily very useful. Yeah, it was an eye-opener to see the generated PostScript being just one bitmap per page. That will be even less useful once they get to generating PDF. > Probably worth keeping an eye on, though. True, especially if they make it possible to get a vector view, not just a raster. Regards, Tony Graham ------------------------------------------------------------------------ Web Products, Technologies and Standards Phone: +353 1 8199708 Sun Microsystems x(70)19708 East Point Business Park, Dublin 3, Ireland |
From: Dave M. <da...@da...> - 2004-03-12 15:19:39
|
On Fri, 2004-03-12 at 01:41, Dave Malcolm wrote: > I've been having a look at xmlroff and libfo after a long break. It > struck me that there's a lot in common between the FoDoc subclasses and > a Cairo context. > > See http://cairographics.org/ > > There's currently a fair amount of momentum behind the Cairo project (it > has the author of Pango and of the X Render extension on board) - so it > might be worth supporting a FoDocCairo backend. Is it worth me > attempting a patch? Alas, looking deeper, I'm not sure I'd be able to achieve much more than sending the pages as a series of fully composited pixbufs to the printer/PDF - not necessarily very useful. Probably worth keeping an eye on, though. > > > (I'm hoping Cairo will emerge as the "one true 2D imaging API", which > would allow the scrapping of lots of intermediate wrapper layers. In > particular, a Cairo backend for printing to a GnomePrintContext might > emerge at some point, or GnomePrint might go over to using Cairo > directly. Hopefully some way of plugging it all together, at any > rate...) |
From: Dave M. <da...@da...> - 2004-03-12 01:46:18
|
I've been having a look at xmlroff and libfo after a long break. It struck me that there's a lot in common between the FoDoc subclasses and a Cairo context. See http://cairographics.org/ There's currently a fair amount of momentum behind the Cairo project (it has the author of Pango and of the X Render extension on board) - so it might be worth supporting a FoDocCairo backend. Is it worth me attempting a patch? (I'm hoping Cairo will emerge as the "one true 2D imaging API", which would allow the scrapping of lots of intermediate wrapper layers. In particular, a Cairo backend for printing to a GnomePrintContext might emerge at some point, or GnomePrint might go over to using Cairo directly. Hopefully some way of plugging it all together, at any rate...) -- David Malcolm www.conglomerate.org |
From: Dave M. <da...@da...> - 2004-03-12 00:50:58
|
I noticed from this recent "commit" that libgnomeprint appears to now support printing a PangoLayout to a GnomePrintContext. I thought I'd mention it in case this is relevant/of use. -- David Malcolm www.conglomerate.org |
From: Tony G. <Ton...@Su...> - 2004-02-20 14:27:02
|
PangoPDF 1.2.3.4 (an easy-to-type version number if ever there was one) is now available in source and Source RPM forms. This release fixes a bug in setting the foreground colour of text in the GNOME Print backend. I obviously haven't got the hang of the do-a-release-a-month idea since the goal is to do an xmlroff release at least once a month (and have the bandwidth left over to announce the release in all the places that it should be announced), but this does fix a visible bug in the GNOME Print backend. Regards, Tony Graham ------------------------------------------------------------------------ Web Products, Technologies and Standards Phone: +353 1 8199708 Sun Microsystems x(70)19708 East Point Business Park, Dublin 3, Ireland |
From: Tony G. <Ton...@Su...> - 2004-02-02 16:47:37
|
Dave Malcolm <da...@da...> wrote at Fri, 30 Jan 2004 16:45:06 +0000: > There's a discussion going on on the Gnome documentation mailing list > (gno...@gn...) about printing DocBook from Yelp (the Gnome > help viewer), which mentioned xmlroff. > > In case you hadn't seen this, I've attached a copy of the posting. Thanks. Someone else had alerted me to it, and I had a reply waiting to be sent. It's sent now. We'll see what response that brings. > Tony: I was hoping you could reply to this (on that list) and give some > indication of what could be done on the part of Gnome people to make > xmlroff easier to build/integrate into Gnome; perhaps Pango or > libgnomeprint fixes? I would have answered myself, but I haven't had a > chance to look at xmlroff in the last few months and I've forgotten how > it all fits together :-( > > (in particular, is PDFlib still a real dependency? I had a feeling it's > now optional) Totally optional. Regards, Tony Graham ------------------------------------------------------------------------ XML Technology Center - Dublin Sun Microsystems Ireland Ltd Phone: +353 1 8199708 Hamilton House, East Point Business Park, Dublin 3 x(70)19708 |
From: Dave M. <da...@da...> - 2004-01-30 16:39:49
|
There's a discussion going on on the Gnome documentation mailing list (gno...@gn...) about printing DocBook from Yelp (the Gnome help viewer), which mentioned xmlroff. In case you hadn't seen this, I've attached a copy of the posting. Tony: I was hoping you could reply to this (on that list) and give some indication of what could be done on the part of Gnome people to make xmlroff easier to build/integrate into Gnome; perhaps Pango or libgnomeprint fixes? I would have answered myself, but I haven't had a chance to look at xmlroff in the last few months and I've forgotten how it all fits together :-( (in particular, is PDFlib still a real dependency? I had a feeling it's now optional) Thanks Dave Malcolm |
From: Tony G. <Ton...@Su...> - 2004-01-30 14:29:20
|
There's nothing quite like moving scripts from one machine to another to really show the scripts' dependencies on an idiosyncratic directory structure. I did that: I copied the previous xmlroff-testing package to a different machine, and nothing worked. So I fixed it. If there'd been a bug reported about it, I expect I would have fixed it sooner. Can someone try it out to see if it works for them so I can close bug 886125? The testing setup still needs work so it's easier to test the different xmlroff backends and output types: for example, right now the scripts, etc. are hardwired for PDF files, with no option of generating or manipulating PostScript files. I will be filing some RFEs just to get the necessary changes on the record. If anyone else wants to help, working on the testing setup would be a good way to help xmlroff without having to delve into the xmlroff source code: all that's needed is a bit of XSLT and Perl knowledge. I said before that I wanted to to monthly releases. This month's release is the xmlroff testing setup. I did mean xmlroff itself, so I don't know if releasing the testing setup obeys the letter but not the spirit or the spirit but not the letter of what I said before, but that's what's released this month. From the news item about it: ------------- The xmlroff test setup automatically runs xmlroff on the XML and FO files in one or more testsuites. It also compares a test's output against its reference and produces a summary report indicating which tests produce differing output. Lastly, the record of the test results can be updated from the HTML page showing the test results. This release removes a lot of the idiosyncratic file system dependencies of the 0.2.0 release, makes it easier to create an initial testresults.xml file, and groups the common parameters into a testing-param.xsl file. --------------- Regards, Tony Graham. |
From: Tony G. <Ton...@Su...> - 2004-01-13 16:35:36
|
I want to get into the habit of making more frequent, ideally monthly, xmlroff releases so the project has some momentum. The holiday break and the current failure of my New Year's resolution to get up early and work on xmlroff before starting my day job hasn't helped progress. I propose to work on the bugs and unimplemented features shown up by the samples for the XML 2003 "XSL FO Chef's Tools Exhibition" since that will shortly be the most visible indicator of xmlroff's abilities. I doubt that IdeaAlliance will be interested in updating results, but Mulberry Technologies may well repeat the exercise at future conferences, plus it will always be possible to show progress on the "Examples" pages on the xmlroff web site. I don't know how many of you have run the Chef's Tools samples, but the samples need to be modified by a "fixup.xsl" stylesheet before xmlroff can do much with them. Since "fixup.xsl" writes a message every time it modifies the samples, the most direct way to show progress is to reduce the number of messages by reducing the number of times "fixup.xsl" has to modify the samples. The prime candidates for changes are: - Implementing border and padding shorthands I have picked away at this in the past. This needs a new expression evaluator (or more than one) to handle the different syntax of the shorthand expressions, a new four-part and/or three-part datatype to represent the result of evaluating a shorthand, and code in fo-context-util to resolve shorthands. - Implementing system-color() This can be based on the Pango color attribute code, which borrows from Tcl/Tk code. - "height" properties on tables This doesn't work with table cells that span rows. This needs yet another table-related area object type and/or implementing spanning-cell-specific versions of fo_area_n_children() and others. Regards, Tony Graham |
From: Tony G. <Ton...@Su...> - 2004-01-12 16:23:47
|
Tim Waugh <tw...@re...> wrote at Mon, 12 Jan 2004 16:03:09 +0000: > On Mon, Jan 12, 2004 at 03:51:29PM +0000, Tony Graham wrote: > > Tim Waugh <tw...@re...> wrote at Fri, 09 Jan 2004 17:31:42 +0000: > > > rpmbuild -ts doesn't work for you? > > > > # rpmbuild -ts xmlroff-0.2.4.tar.gz > > error: Failed build dependencies: > > libgnomeprint22-devel is needed by xmlroff-0.2.4-0.1 > > pangopdf-devel is needed by xmlroff-0.2.4-0.1 > > Ah. I think you can short-circuit that check with --nodeps (with no > ill effects). Thanks, yet again. Done and uploaded. Regards, Tony Graham ------------------------------------------------------------------------ XML Technology Center - Dublin Sun Microsystems Ireland Ltd Phone: +353 1 8199708 Hamilton House, East Point Business Park, Dublin 3 x(70)19708 |
From: Tim W. <tw...@re...> - 2004-01-12 16:03:18
|
On Mon, Jan 12, 2004 at 03:51:29PM +0000, Tony Graham wrote: > Tim Waugh <tw...@re...> wrote at Fri, 09 Jan 2004 17:31:42 +0000: > > On Fri, Jan 09, 2004 at 04:44:24PM +0000, Tony Graham wrote: > >=20 > > > The xmlroff source RPM will take a bit longer since it appears I have > > > to go back and reinstall/rebuild pangopdf and libgnomeprint from their > > > RPMs before I can make a source RPM for xmlroff. > >=20 > > rpmbuild -ts doesn't work for you? >=20 > # rpmbuild -ts xmlroff-0.2.4.tar.gz > error: Failed build dependencies: > libgnomeprint22-devel is needed by xmlroff-0.2.4-0.1 > pangopdf-devel is needed by xmlroff-0.2.4-0.1 Ah. I think you can short-circuit that check with --nodeps (with no ill effects). Tim. */ |
From: Tony G. <Ton...@Su...> - 2004-01-12 15:51:32
|
Tim Waugh <tw...@re...> wrote at Fri, 09 Jan 2004 17:31:42 +0000: > On Fri, Jan 09, 2004 at 04:44:24PM +0000, Tony Graham wrote: > > > The xmlroff source RPM will take a bit longer since it appears I have > > to go back and reinstall/rebuild pangopdf and libgnomeprint from their > > RPMs before I can make a source RPM for xmlroff. > > rpmbuild -ts doesn't work for you? # rpmbuild -ts xmlroff-0.2.4.tar.gz error: Failed build dependencies: libgnomeprint22-devel is needed by xmlroff-0.2.4-0.1 pangopdf-devel is needed by xmlroff-0.2.4-0.1 Presumably this is because I install PangoPDF from the development directory and built libgnomeprint from its tar file, not from any RPM. I will change to a different Linux partition and build the packages from their RPMs. BTW, the PangoPDF SRPM is now available on SourceForge. Thanks, Tim, for helping me get this far, and for making the SRPMs available on your site up until now. Regards, Tony Graham ------------------------------------------------------------------------ XML Technology Center - Dublin Sun Microsystems Ireland Ltd Phone: +353 1 8199708 Hamilton House, East Point Business Park, Dublin 3 x(70)19708 |
From: Tim W. <tw...@re...> - 2004-01-09 17:31:52
|
On Fri, Jan 09, 2004 at 04:44:24PM +0000, Tony Graham wrote: > The xmlroff source RPM will take a bit longer since it appears I have > to go back and reinstall/rebuild pangopdf and libgnomeprint from their > RPMs before I can make a source RPM for xmlroff. rpmbuild -ts doesn't work for you? Tim. */ |
From: Tony G. <Ton...@Su...> - 2004-01-09 16:44:31
|
Tim Waugh <tw...@re...> wrote at Sat, 20 Dec 2003 13:57:44 +0000: > On Sat, Dec 20, 2003 at 09:43:07AM +0000, Tony Graham wrote: ... > > I tried making source RPMs, a la Tim Waugh, but it failed, and since > > I'm supposed to be catching a plane a few hours from now, I don't have > > time to investigate. > > Pangopdf needs this patch (sorry I didn't catch it before): Thanks. Committed. I plan to add my PangoPDF source RPM to the Sourceforge downloads, but I'm having trouble uploading at present. The xmlroff source RPM will take a bit longer since it appears I have to go back and reinstall/rebuild pangopdf and libgnomeprint from their RPMs before I can make a source RPM for xmlroff. Regards, Tony Graham ------------------------------------------------------------------------ XML Technology Center - Dublin Sun Microsystems Ireland Ltd Phone: +353 1 8199708 Hamilton House, East Point Business Park, Dublin 3 x(70)19708 |
From: Tim W. <tw...@re...> - 2003-12-20 13:57:59
|
On Sat, Dec 20, 2003 at 09:43:07AM +0000, Tony Graham wrote: > xmlroff 0.2.4 incorporates multiple fixes resulting from getting > xmlroff to run the samples from the XML 2003 "XSL FO Chef's Tools > Exhibition". Excellent! > I tried making source RPMs, a la Tim Waugh, but it failed, and since > I'm supposed to be catching a plane a few hours from now, I don't have > time to investigate. Pangopdf needs this patch (sorry I didn't catch it before): --- pangopdf-1.2.3.3/pangopdf-pango.spec.in.fix 2003-12-20 13:44:57.0000000= 00 +0000 +++ pangopdf-1.2.3.3/pangopdf-pango.spec.in 2003-12-20 13:45:59.000000000 += 0000 @@ -4,8 +4,9 @@ Release: 1 License: LGPL Group: System Environment/Libraries -Source: http://pangopdf.sourceforge.net/ -BuildRoot: /var/tmp/%{name}-%{version}-root +Url: http://pangopdf.sourceforge.net/ +Source0: %{name}-%{version}.tar.gz +BuildRoot: %{_tmppath}/%{name}-%{version}-root Requires: glib2 BuildRequires: glib2-devel =20 I've put updated source RPMs at: ftp://people.redhat.com/twaugh/docbook/xmlroff Tim. */ |
From: Tony G. <Ton...@Su...> - 2003-12-20 09:43:14
|
I don't know that anybody actually asked Santa Claus for a new version of xmlroff for Christmas, but it's here just in time for the holidays. xmlroff 0.2.4 incorporates multiple fixes resulting from getting xmlroff to run the samples from the XML 2003 "XSL FO Chef's Tools Exhibition". PangoPDF 1.2.3.3 differs from 1.2.3.2 only in that two irrelevant error messages are commented out. libfo-jni 0.2.0 is an extremely simple Java Native Interface wrapper on libfo. I tried making source RPMs, a la Tim Waugh, but it failed, and since I'm supposed to be catching a plane a few hours from now, I don't have time to investigate. Happy holidays, Tony Graham ------------------------------------------------------------------------ XML Technology Center - Dublin Sun Microsystems Ireland Ltd Phone: +353 1 8199708 Hamilton House, East Point Business Park, Dublin 3 x(70)19708 |
From: Tony G. <Ton...@Su...> - 2003-12-17 12:13:15
|
Tony Graham <Ton...@Su...> wrote at Mon, 20 Oct 2003 17:52:37 +0100 (BST): > http://www.biglist.com/lists/xsl-list/archives/200310/msg00752.html > > However, it was only cited by a RenderX developer to silence > self-advertising by AntennaHouse about their formatter being the > fastest. David Tolpin has corrected my assumption that he was still a RenderX developer: | I am the author and implementor of RenderX XEP core and had been | RenderX CTO but I am not with RenderX since July 30th, 2003. I | thought I would let you know. I would not participate in that | dispute with Kobayashi if I was. I like the idea of a free XSL FO | formatter with a better quality then FOP. Meanwhile, I have serious | concerns with regard to the design of XMLroff, but when I express my | concerns, it is an engineer's point of view, not a competitive rant. I apologise to David for my misunderstanding and for any further misunderstandings that that caused. Regards, Tony Graham ------------------------------------------------------------------------ XML Technology Center - Dublin Sun Microsystems Ireland Ltd Phone: +353 1 8199708 Hamilton House, East Point Business Park, Dublin 3 x(70)19708 |
From: Tim W. <tw...@re...> - 2003-12-05 18:12:50
|
I've updated the SRPM in ftp://people.redhat.com/twaugh/docbook/xmlroff. Tim. */ |
From: Tony G. <Ton...@Su...> - 2003-12-05 17:40:50
|
Overview of Changes in Pango 1.2.3.2 ==================================== * Improved reliability of PangoPDF working with GNOME apps. * No dependency on PDFlib when using --disable-pdflib. 2003-12-05 Tony Graham <ton...@us...> * === Released 1.2.3.2 === * NEWS.pangopdf: Updated for 1.2.3.2. * autogen.sh: Added support for libtool 1.5 (Dave Malcolm). 2003-12-01 Tony Graham <ton...@us...> * examples/pangogp-to-pdf.c: Removed unused y_start, x_start, and init_paper variables. * pangopdf-pango.pc.in: Added 'pango_module_version=@PANGO_MODULE_VERSION@' to match Pango. * pangopdf-pangoft2.pc.in: Removed a blank line. 2003-11-26 Tony Graham <ton...@us...> * pangopdf-pango.spec.in: Applied patch from Tim Waugh so that works with rpmbuild. Changed 'Source' to point to SourceForge site. 2003-10-29 Tony Graham <ton...@us...> * configure.in: Reworked checking for PDFlib so doesn't error on --disable-pdflib. 2003-08-03 Tony Graham <ton...@us...> * configure.in: Upped pango_pico_version and interface_age to '2'. * pango/pango-layout-private.h, pango/pango-layout.c, pango/pangogp-layout.c, pango/pangopdflib-layout.c: Commented out get_extents member of PangoLayoutRunPrivate and commented out all uses of it. Renamed pango_layout_run_get_extents_real back to pango_layout_run_get_extents. This appears to solve problem of GNOME apps linked with libfo crashing with segfaults. Regards, Tony Graham ------------------------------------------------------------------------ XML Technology Center - Dublin Sun Microsystems Ireland Ltd Phone: +353 1 8199708 Hamilton House, East Point Business Park, Dublin 3 x(70)19708 |
From: Tony G. <Ton...@Su...> - 2003-12-03 11:23:59
|
Dave Malcolm <da...@da...> wrote at Mon, 01 Dec 2003 22:13:27 +0000: > I just built PangoPDF and xmlroff with libtool 1.5; I had to patch the > autogen.sh files, which currently require libtool 1.4 exactly. > > Attached you should find the patches I applied. Thanks. Regards, Tony Graham ------------------------------------------------------------------------ XML Technology Center - Dublin Sun Microsystems Ireland Ltd Phone: +353 1 8199708 Hamilton House, East Point Business Park, Dublin 3 x(70)19708 |
From: Dave M. <da...@da...> - 2003-12-02 10:00:31
|
I just built PangoPDF and xmlroff with libtool 1.5; I had to patch the autogen.sh files, which currently require libtool 1.4 exactly. Attached you should find the patches I applied. -- David Malcolm www.conglomerate.org |
From: Dave M. <da...@da...> - 2003-12-01 20:27:50
|
On Tue, 2003-11-25 at 16:24, Tony Graham wrote: > If anyone else has the time and inclination to try them with xmlroff, > the test files for the XSL FO Chef's Tools Exhibition at XML 2003 are > temporarily available at: > > ftp://www.mulberrytech.com/FO-Chef-Tool/SampleFiles/ Thanks for the link (back from holiday now). Unfortunately I'm too busy working through Conglomerate issues to have a good look at xmlroff's handling of these right now - I hope to at some point this week though. > > Is anyone else on this list going to be at XML 2003? Can't really afford to, unfortunately. Unless some nice company would like to sponsor me, or hire me :-) > > Regards, > > > Tony Graham -- David Malcolm www.conglomerate.org |