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...> - 2003-11-25 16:25:03
|
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/ Is anyone else on this list going to be at XML 2003? 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-11-14 17:49:18
|
Tim Waugh <tw...@re...> wrote at Fri, 14 Nov 2003 15:02:38 +0000: > On Fri, Nov 14, 2003 at 02:36:54PM +0000, Tony Graham wrote: > > > I'm using libgnomeprint 2.2.1.2. What are you using? > > $ rpm -q libgnomeprint22 > libgnomeprint22-2.4.0-1 Problem solved. I had been using a libgnomeprint that I'd tweaked to build using PangoPDF instead of Pango. It's not surprising that it didn't work when I took away the installed PangoPDF files. So I can now build PangoPDF in one go if I use a libgnomeprint that is linked against Pango, or in three steps if I use a libgnomeprint that is linked against PangoPDF. If only Pango had an official GNOME Print backend... 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-11-14 15:02:42
|
On Fri, Nov 14, 2003 at 02:36:54PM +0000, Tony Graham wrote: > I'm using libgnomeprint 2.2.1.2. What are you using? $ rpm -q libgnomeprint22 libgnomeprint22-2.4.0-1 Tim. */ |
From: Tony G. <Ton...@Su...> - 2003-11-14 14:37:04
|
Tim Waugh <tw...@re...> wrote at Fri, 14 Nov 2003 13:03:12 +0000: > On Fri, Nov 14, 2003 at 12:55:53PM +0000, Tony Graham wrote: > > > It appears that I have an extra -L/usr/local/lib that comes from > > $(GNOMEPRINT_LIBS), but removing that from the generated Makefile > > doesn't seem to help either. > > Here's my 'pkg-config --libs libgnomeprint-2.2' output: > > -Wl,--export-dynamic -lgnomeprint-2-2 -lart_lgpl_2 -lxml2 -lpthread -lz -lm -lpango-1.0 -lgobject-2.0 -lgmodule-2.0 -ldl -lglib-2.0 And here's mine: -Wl,--export-dynamic -L/usr/local/lib -lgnomeprint-2-2 -lart_lgpl_2 -lxml2 -lz -lm -lpango-1.0 -lgobject-2.0 -lgmodule-2.0 -ldl -lglib-2.0 I'm using libgnomeprint 2.2.1.2. What are you using? I can build PangoPDF if I do --disable-gp, and if I then install PangoPDF and rebuild with the GP backend enabled, it builds okay. Not exactly the best state of affairs, but better than it was this morning. Now I just need to nail down our libgnomeprint differences. 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-11-14 13:03:16
|
On Fri, Nov 14, 2003 at 12:55:53PM +0000, Tony Graham wrote: > It appears that I have an extra -L/usr/local/lib that comes from > $(GNOMEPRINT_LIBS), but removing that from the generated Makefile > doesn't seem to help either. Here's my 'pkg-config --libs libgnomeprint-2.2' output: -Wl,--export-dynamic -lgnomeprint-2-2 -lart_lgpl_2 -lxml2 -lpthread -lz -lm -lpango-1.0 -lgobject-2.0 -lgmodule-2.0 -ldl -lglib-2.0 Tim. */ |
From: Tony G. <Ton...@Su...> - 2003-11-14 12:55:56
|
Tim Waugh <tw...@re...> wrote at Fri, 14 Nov 2003 11:47:44 +0000: > On Fri, Nov 14, 2003 at 11:07:36AM +0000, Tony Graham wrote: > > > I have got my PangoPDF setup into a state where I can't compile all of > > PangoPDF on a system that doesn't already have PangoPDF installed. > > In current CVS? Works for me with libtool 1.5. Here's the link line > I get: > > /bin/sh ../libtool --mode=link gcc -g -O2 -Wall -o pangogp-to-pdf pangogp-to-pdf.o ../pango/libpango-1.0.la ../pango/libpangogp-1.0.la ../pango/libpangox-1.0.la -Wl,--export-dynamic -lgnomeprint-2-2 -lart_lgpl_2 -lxml2 -lpthread -lz -lm -lpango-1.0 -lgobject-2.0 -lgmodule-2.0 -ldl -lglib-2.0 > gcc -g -O2 -Wall -o .libs/pangogp-to-pdf pangogp-to-pdf.o -Wl,--export-dynamic ../pango/.libs/libpangogp-1.0.so -lfontconfig /usr/lib/libfreetype.so ../pango/.libs/libpangox-1.0.so /root/pangopdf/pango/.libs/libpango-1.0.so -L/usr/X11R6/lib -lX11 -lgnomeprint-2-2 -lart_lgpl_2 /usr/lib/libxml2.so -lpthread -lz -lm ../pango/.libs/libpango-1.0.so -lgobject-2.0 -lgmodule-2.0 -ldl -lglib-2.0 -Wl,--rpath -Wl,/usr/local/lib/pangopdf > > Time to upgrade libtool? I just tried that but it still doesn't work. It appears that I have an extra -L/usr/local/lib that comes from $(GNOMEPRINT_LIBS), but removing that from the generated Makefile doesn't seem to help either. 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-11-14 11:47:55
|
On Fri, Nov 14, 2003 at 11:07:36AM +0000, Tony Graham wrote: > I have got my PangoPDF setup into a state where I can't compile all of > PangoPDF on a system that doesn't already have PangoPDF installed. In current CVS? Works for me with libtool 1.5. Here's the link line I get: /bin/sh ../libtool --mode=link gcc -g -O2 -Wall -o pangogp-to-pdf pangogp-to-pdf.o ../pango/libpango-1.0.la ../pango/libpangogp-1.0.la ../pango/libpangox-1.0.la -Wl,--export-dynamic -lgnomeprint-2-2 -lart_lgpl_2 -lxml2 -lpthread -lz -lm -lpango-1.0 -lgobject-2.0 -lgmodule-2.0 -ldl -lglib-2.0 gcc -g -O2 -Wall -o .libs/pangogp-to-pdf pangogp-to-pdf.o -Wl,--export-dynamic ../pango/.libs/libpangogp-1.0.so -lfontconfig /usr/lib/libfreetype.so ../pango/.libs/libpangox-1.0.so /root/pangopdf/pango/.libs/libpango-1.0.so -L/usr/X11R6/lib -lX11 -lgnomeprint-2-2 -lart_lgpl_2 /usr/lib/libxml2.so -lpthread -lz -lm ../pango/.libs/libpango-1.0.so -lgobject-2.0 -lgmodule-2.0 -ldl -lglib-2.0 -Wl,--rpath -Wl,/usr/local/lib/pangopdf Time to upgrade libtool? Tim. */ |
From: Tony G. <Ton...@Su...> - 2003-11-14 11:07:40
|
I have got my PangoPDF setup into a state where I can't compile all of PangoPDF on a system that doesn't already have PangoPDF installed. Compiling pangogp-to-pdf andd pangopdf-querymodules fails because the linker can't find an installed libpango-1.0.la: ------------------------------------------------------------ make[3]: Entering directory `/usr/local/src/xslfo/pangopdf/examples' /bin/sh ../libtool --mode=link gcc -g -O2 -Wall -o pangogp-to-pdf pangogp-to-pdf.o ../pango/libpango-1.0.la ../pango/libpangogp-1.0.la ../pango/libpangox-1.0.la -Wl,--export-dynamic -L/usr/local/lib -lgnomeprint-2-2 -lart_lgpl_2 -lxml2 -lz -lm -lpango-1.0 -lgobject-2.0 -lgmodule-2.0 -ldl -lglib-2.0 libtool: link: cannot find the library `/usr/local/lib/pangopdf/libpango-1.0.la' make[3]: *** [pangogp-to-pdf] Error 1 ------------------------------------------------------------ FWIW, here's the libpango-1.0.la file: ------------------------------------------------------------ # libpango-1.0.la - a libtool library file # Generated by ltmain.sh - GNU libtool 1.4.3 (1.922.2.111 2002/10/23 02:54:36) # # Please DO NOT delete this file! # It is necessary for linking the library. # The name that we can dlopen(3). dlname='libpango-1.0.so.0' # Names of this library. library_names='libpango-1.0.so.0.230.2 libpango-1.0.so.0 libpango-1.0.so' # The name of the static archive. old_library='' # Libraries that this one depends upon. dependency_libs=' -lgobject-2.0 -lgmodule-2.0 -ldl -lglib-2.0 ' # Version information for libpango-1.0. current=230 age=230 revision=2 # Is this an already installed library? installed=no # Files to dlopen/dlpreopen dlopen='' dlpreopen='' # Directory that this library needs to be installed in: libdir='/usr/local/lib/pangopdf' ------------------------------------------------------------ However, this differs very little from the original Pango libpango-1.0.la file, so the problem probably lies elsewhere. I am going back over previous PangoPDF releases to see where the problem is, but in the meantime does anyone have any ideas? 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-10-29 18:53:10
|
Here is a patch for xmlroff so that rpmbuild -tb xmlroff*.tar.gz works. Note: the other patches I sent in private mail are still needed, both for pangopdf (allow --disable-pdflib) and xmlroff (compilation fixes). Tim. */ Index: Makefile.am =================================================================== RCS file: /cvsroot/xmlroff/xmlroff/Makefile.am,v retrieving revision 1.12 diff -d -u -r1.12 Makefile.am --- Makefile.am 22 Jul 2003 13:15:05 -0000 1.12 +++ Makefile.am 29 Oct 2003 18:51:38 -0000 @@ -83,4 +83,5 @@ -I/opt/gnome-1.4/include EXTRA_DIST = \ - xmlroff.fo + xmlroff.fo \ + xmlroff.spec Index: configure.in =================================================================== RCS file: /cvsroot/xmlroff/xmlroff/configure.in,v retrieving revision 1.11 diff -d -u -r1.11 configure.in --- configure.in 22 Jul 2003 13:15:41 -0000 1.11 +++ configure.in 29 Oct 2003 18:51:39 -0000 @@ -523,6 +523,7 @@ libfo/Makefile examples/Makefile libfo-0.2.pc +xmlroff.spec ]) fo_doc_subtypes="" --- xmlroff.spec.in.orig 2003-10-29 18:50:42.000000000 +0000 +++ xmlroff.spec.in 2003-10-29 18:50:12.000000000 +0000 @@ -0,0 +1,45 @@ +Summary: XSL-FO processor +Name: xmlroff +Version: @VERSION@ +Release: 0.1 +License: Distributable +Group: Applications/Text +URL: http://xmlroff.sourceforge.net +Source0: %{name}-%{version}.tar.gz +BuildRoot: %{_tmppath}/%{name}-%{version}-%{release}-buildroot +BuildRequires: libgnomeprint22-devel +BuildRequires: pangopdf-devel + +%description +This package contains an XSL-FO processing tool. + +%prep +%setup -q + +%build +%configure --disable-pdflib +make %{?_smp_mflags} + +%install +rm -rf $RPM_BUILD_ROOT +%makeinstall +rm -rf $RPM_BUILD_ROOT%{_datadir}/gtk-doc \ + $RPM_BUILD_ROOT%{_libdir}/pkgconfig \ + $RPM_BUILD_ROOT%{_libdir}/*.la \ + $RPM_BUILD_ROOT%{_libdir}/*.a \ + $RPM_BUILD_ROOT%{_includedir} + +%clean +rm -rf $RPM_BUILD_ROOT + +%files +%defattr(-,root,root,-) +%doc COPYING NEWS README TODO +%{_bindir}/* +%{_libdir}/*.so.* + +%changelog +* Mon Oct 27 2003 Tim Waugh <tw...@re...> 0.2.3-0.1 +- Initial build. + + |
From: Tim W. <tw...@re...> - 2003-10-29 18:43:48
|
On Wed, Oct 29, 2003 at 08:41:34AM +0000, Tony Graham wrote: > Can you submit patches so this can be done directly from Make by > anyone? Here is a patch for PangoPDF's own spec file, so that: rpmbuild -tb pangopdf*.tar.gz works. (xmlroff patch to follow) Tim. */ Index: pangopdf-pango.spec.in =================================================================== RCS file: /cvsroot/pangopdf/pangopdf/pangopdf-pango.spec.in,v retrieving revision 1.2 diff -u -r1.2 pangopdf-pango.spec.in --- pangopdf-pango.spec.in 7 Jul 2003 16:00:53 -0000 1.2 +++ pangopdf-pango.spec.in 29 Oct 2003 18:42:32 -0000 @@ -36,7 +36,7 @@ --bindir=%{_bindir} --mandir=%{_mandir} \ --localstatedir=%{_localstatedir} --libdir=%{_libdir} \ --datadir=%{_datadir} --includedir=%{_includedir} \ - --sysconfdir=%{_sysconfdir} --disable-gtk-doc + --sysconfdir=%{_sysconfdir} --disable-gtk-doc --disable-pdflib make %install @@ -49,6 +49,8 @@ includedir=$RPM_BUILD_ROOT%{_includedir} \ sysconfdir=$RPM_BUILD_ROOT%{_sysconfdir} install +rm -f $RPM_BUILD_ROOT%{_sysconfdir}/pangopdf/pango.modules + %clean rm -rf $RPM_BUILD_ROOT @@ -61,20 +63,30 @@ %files %doc README AUTHORS COPYING ChangeLog TODO %doc examples/HELLO.utf8 -%{_libdir}/libpango*-*.so -%{_bindir}/pango-* -%{_libdir}/pango +%dir %{_libdir}/pangopdf +%{_libdir}/pangopdf/*.so.* +%{_bindir}/* +%dir %{_libdir}/pangopdf/pango +%dir %{_libdir}/pangopdf/pango/1.2.0 +%dir %{_libdir}/pangopdf/pango/1.2.0/modules +%{_libdir}/pangopdf/pango/1.2.0/modules/*.so +%{_datadir}/pangopdf %config %{_sysconfdir}/pangopdf/pangox.aliases %files devel %defattr(-, root, root) -%{_libdir}/libpango*.so -%{_libdir}/*a +%{_libdir}/pangopdf/*.so +%{_libdir}/pangopdf/*a +%{_libdir}/pangopdf/pango/1.2.0/modules/*a %{_libdir}/pkgconfig/*.pc -%{_includedir}/pango-1.0 -%{_datadir}/gtk-doc/html/pango +%{_includedir}/pangopdf/pango-1.0 +%{_datadir}/gtk-doc/html/pangopdf %changelog +* Wed Oct 29 2003 Tim Waugh <tw...@re...> +- Adapt file manifest. +- Disable pdflib. + * Mon Aug 27 2001 Jens Finke <je...@gn...> - glib2 package required - updated source url |
From: Tony G. <Ton...@Su...> - 2003-10-29 10:26:57
|
Since the goal of PangoPDF is to become redundant, I submitted an enhancement request to get a GNOME Print backend added to Pango: http://bugzilla.gnome.org/show_bug.cgi?id=125762 We'll see what response this brings. 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-10-29 08:41:41
|
Tim Waugh <tw...@re...> wrote at Mon, 27 Oct 2003 23:06:40 +0000: > I have packaged pangopdf and xmlroff (both with --disable-pdflib), > and put the resulting SRPM packages here: > > ftp://people.redhat.com/twaugh/docbook/xmlroff Cool. Thanks. Can you submit patches so this can be done directly from Make by anyone? 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-10-27 23:12:57
|
I have packaged pangopdf and xmlroff (both with --disable-pdflib), and put the resulting SRPM packages here: ftp://people.redhat.com/twaugh/docbook/xmlroff To create binaries just do this: rpmbuild --rebuild pangopdf*.src.rpm [install resulting packages] rpmbuild --rebuild xmlroff*.src.rpm Sorry, don't have the space to store the binaries too. Tim. */ |
From: Tony G. <Ton...@Su...> - 2003-10-21 00:18:24
|
Dave Malcolm <da...@da...> wrote at Tue, 21 Oct 2003 00:13:23 +0000: > On Mon, 2003-10-20 at 16:52, Tony Graham wrote: > > 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. > > > > It will be interesting to see what this does to the xmlroff page views > > in the next couple of days. > > Ha! :-) Well, a few minutes ago we got the first new subscriber in quite a while. > Are you still working on xmlroff? This list has been very quiet for the > last few months. I haven't had a chance to look at xmlroff/GnomePrint > integration; am too busy with Conglomerate stuff. Yes, I am still working on xmlroff, although I have been busy with other stuff recently. Independently of being mentioned on the XSL-List twice in one week (minor jump in page views at the end of last week, too), I'm giving a talk on xmlroff at my office tomorrow, and I'm getting ready to make a 0.2.4 release that (thanks to patches from Tim Waugh) should put the last nail in the coffin of requiring PDFlib when you're using the GNOME Print backend. Independently of all that, GNOME Print has a new maintainer, and there's already talk of GNOME Print improving its Pango integration. 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-10-20 23:15:04
|
On Mon, 2003-10-20 at 16:52, Tony Graham wrote: > 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. > > It will be interesting to see what this does to the xmlroff page views > in the next couple of days. Ha! :-) Are you still working on xmlroff? This list has been very quiet for the last few months. I haven't had a chance to look at xmlroff/GnomePrint integration; am too busy with Conglomerate stuff. -- David Malcolm www.conglomerate.org |
From: Tony G. <Ton...@Su...> - 2003-10-20 21:04:15
|
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. It will be interesting to see what this does to the xmlroff page views in the next couple of days. 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-10-03 15:22:49
|
FYI, I have signed up xmlroff as one of the XSL formatters at the "XSL-FO Chef's Tools Exhibition" at XML 2003. 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-08-14 16:01:58
|
The xmlroff-list archive shows a message from Dave Malcolm on 5th August titled "GnomePrint with a client-supplied GnomePrintJob" that I, for one, didn't receive. Am I the only one who didn't get it? To answer Dave's question, on the face of it, it looks like the code is correct. What are you getting as output? A zero-length file? Small and invalid PDF file? Blank PDF pages? fo_xsl_formatter_set_result_tree() does fo_xml_doc_ref(result_tree), so you should be able to keep the FoXmlDoc just by omitting the fo_xml_doc_unref() in your code. I would prefer to keep the '#include <libgnomeprint/gnome-print.h>' out of fo-doc-gp.h so apps that use libfo don't need to depend on the libgnomeprint headers. Maybe the new function could go in fo-xsl-formatter-private.h or in a new header for use by apps, such as yours, that aren't troubled by having to know details of libgnomeprint. Yes, I'm still trying to get to the tree-viewer app. 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-08-05 12:20:38
|
I've been experimenting with implementing support for client-supplied GnomePrintJobs to the GnomePrint part of xmlroff. The motivation is that I'd like to be able to provide a print preview of XSL:FO in Conglomerate (www.conglomerate.org). Attached is a unified diff against CVS xmlroff, so you can get an idea of what I've done. Essentially I've added a constructor that takes a GnomePrintJob, and sets an internal flag. If this flag is set, then xmlroff blithely ignores paper sizes in the input XML and uses whatever is set up on the GnomePrintJob. Hence it shouldn't need to create new print jobs if the paper size changes, and hence everything ought to appear in the print preview. It's a bit of a dirty hack, though it compiles and links, and I've got it hooked into some test code in Conglomerate; however I'm currently getting only blank pages. Here is my test code for reference: FoXslFormatter *fo_xsl_formatter; FoDoc *fo_doc; FoXmlDoc *result_tree; FoLibfoContext *libfo_context; GError *error = NULL; fo_xsl_formatter = fo_xsl_formatter_new(); fo_doc = fo_doc_gp_new_from_gnome_print_job (job); result_tree = fo_xml_doc_new (); fo_xsl_formatter_set_fo_doc (fo_xsl_formatter, fo_doc); fo_xsl_formatter_set_result_tree (fo_xsl_formatter, result_tree); /* FIXME: We have to clone the xml_doc: */ fo_xml_doc_set_xml_doc (result_tree, xml_doc); libfo_context = fo_libfo_context_new (); fo_libfo_context_set_debug_mode (libfo_context, FO_DEBUG_MAX); if (fo_xsl_formatter_format (fo_xsl_formatter, libfo_context, &error)) { if (fo_xsl_formatter_draw (fo_xsl_formatter, libfo_context, &error)) { g_message("success"); } } g_object_unref (G_OBJECT(fo_xsl_formatter)); g_object_unref (G_OBJECT(fo_doc)); fo_xml_doc_unref (result_tree); g_object_unref (G_OBJECT(libfo_context)); Some questions (i) is my test code sane? Am I using the API correctly? (ii) does the FoXMLDoc have to "own" its xml_doc, and hence delete it when it closes down? I'd prefer it if it was the client's responsibility (I sometimes use it after doing all of the above code, hence I need to clone it to make the above code correct). (iii) Is the approach I'm following in the patch a good idea? (iv) Is it worth creating a mini Gnome test-app within the xmlroff source tree which acts as a testbed for this kind of functionality? (perhaps it could become the area tree viewer that has been mentioned before on this list?) Dave Malcolm |
From: Tony G. <Ton...@Su...> - 2003-08-05 12:07:00
|
Dave Malcolm wrote at 5 Aug 2003 12:52:04 +0000: > On Sun, 2003-08-03 at 21:20, Tony Graham wrote: ... > > I have now checked in some changes to PangoPDF that stop gnome-hello > > from crashing for me. > > Took a while for anonymous CVS to catch up, but I eventually got the > changes. Works for me too. I had forgotten about the pserver CVS access delay. What a pain. Can't you get at it by non-anonymous, cvs-over-ssh access? > > I have only tried the fix with a statically linked PangoPDF, but since > > the crash occurred at the same place with both a statically and a > > dynamically linked PangoPDF, I expect that the fix will also work with > > a dynamically linked PangoPDF. > > I've built both PangoPDF and xmlroff with just vanilla "./configure" > (dynamic linking, I believe), and gnome-hello with the hacked Yes, dynamic linking. > configure.ac runs successfully for me. Great. Thanks for reporting the problem. The next step will be to tidy up the stuff that I just commented out and to make a new PangoPDF release. 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-08-05 11:50:07
|
On Sun, 2003-08-03 at 21:20, Tony Graham wrote: > (Sorry for not replying to the previous message, but my mail setup is > chaotic right now.) > > When I tried xmlroff-0.2.4 (in CVS) with gnome-hello-2.0.1 using the > pkg-config change in configure.ac, gnome-hello crashed with a > segfault. > > I have now checked in some changes to PangoPDF that stop gnome-hello > from crashing for me. Took a while for anonymous CVS to catch up, but I eventually got the changes. Works for me too. > > I have only tried the fix with a statically linked PangoPDF, but since > the crash occurred at the same place with both a statically and a > dynamically linked PangoPDF, I expect that the fix will also work with > a dynamically linked PangoPDF. I've built both PangoPDF and xmlroff with just vanilla "./configure" (dynamic linking, I believe), and gnome-hello with the hacked configure.ac runs successfully for me. Thanks! |
From: Tony G. <Ton...@Su...> - 2003-08-03 21:18:27
|
(Sorry for not replying to the previous message, but my mail setup is chaotic right now.) When I tried xmlroff-0.2.4 (in CVS) with gnome-hello-2.0.1 using the pkg-config change in configure.ac, gnome-hello crashed with a segfault. I have now checked in some changes to PangoPDF that stop gnome-hello from crashing for me. I have only tried the fix with a statically linked PangoPDF, but since the crash occurred at the same place with both a statically and a dynamically linked PangoPDF, I expect that the fix will also work with a dynamically linked PangoPDF. Incidentally, if you followed my previous advice about using --with-included-modules with --enable-static and --disable-shared, you should have crashed after lots of error messages about not finding pango-basic-xft.so (or similar). If you didn't get those error messages, you weren't cleaning out the shared modules in /usr/local/lib/pangopdf/pango/1.2.0/modules properly. The fix would have been to add basic-xft to the list of included modules. 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-07-29 16:44:57
|
Dave Malcolm wrote at 29 Jul 2003 17:39:48 +0000: > Has anyone else attempted to link libfo with gnome-hello? I won't be able to get to it before Friday. I'll try gnome-hello then. 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-07-29 16:37:58
|
On Tue, 2003-07-29 at 14:55, Dave Malcolm wrote: > > > > > You may also need to add '--enable-static --disable-shared' to the > > xmlroff 'configure' command line, but I suggest trying it without > > first. > > OK - am now doing a full rebuild of xmlroff with those options (having > cleaned out my /usr/local/lib). I'll post the results... > Doh! That failed as well... Doing an "nm" on the installed libfo-0.2.a shows a load of undefined pango symbols. Doing an "nm" on the gnome-hello executable reveals that the pangopdf symbols have been built into it (they are present in the "text" and "data" sections, rather than being "unknown"), so it appears that when GTK+ is loaded it finds the Pango symbols inside the main executable, rather than in the correct shared library - and then blows up. I'm now reading through the libtool and binutils info/man pages... Any ideas? I'm beginning to think that the symbols inside pangopdf need a systematic rename - which would be a pain. Has anyone else attempted to link libfo with gnome-hello? Dave Malcolm |
From: Dave M. <da...@da...> - 2003-07-29 13:53:54
|
On Tue, 2003-07-29 at 10:31, Tony Graham wrote: > Dave Malcolm wrote at 26 Jul 2003 17:19:37 +0000: > > Hope the above makes sense! Is there a simple fix I've missed? Is it > > possible to statically link PangoPDF inside xmlroff without exporting > > its symbols to fix the problem? (I don't know enough about "so" files to > > implement this myself). > > I was about to suggest statically linking PangoPDF to libfo. > > Add '--enable-static --disable-shared' to the PangoPDF 'configure' > command line. You may also need to add > '--with-included-modules=basic-gp'. OK - I just tried that. My "patched to link with libfo" version of gnome-hello still dies deep inside GTK+, in the same way as before. I ran ldd on the executable and grepped for pango, and couldn't see any direct pangopdf references. However, running nm of the libfo library shows up lots of undefined "pango" symbols, so somehow I suppose the libfo linkage is pulling in a load of pango symbols from pangopdf which clash with the pango symbols from the "real" pango. > > You may also need to add '--enable-static --disable-shared' to the > xmlroff 'configure' command line, but I suggest trying it without > first. OK - am now doing a full rebuild of xmlroff with those options (having cleaned out my /usr/local/lib). I'll post the results... Dave Malcolm |