Menu
▾
▴
xmlroff-list — xmlroff XSL formatter discussion list
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: Steinar B. <sb...@do...> - 2007-02-06 11:26:54
|
>>>>> Stefan Seefeld <se...@sy...>: > Yes, please ! :-) > (sf.net's list archive interface is really bad.) Note that this list is also archived on gmane, which is really good, and also gives a lot of alternative ways of accessing it: http://dir.gmane.org/gmane.text.xml.xmlroff.general |
|
From: Stefan S. <se...@sy...> - 2007-02-01 20:49:06
|
Tony Graham wrote: > I now have other webhosting that allows hosting multiple domains for > no extra charge, so I am better placed than ever before to be able to > host xmlroff.org off SourceForge. Sounds good. > One more change would probably be to also move xmlroff-list off > SourceForge and on to xmlroff.org. Yes, please ! :-) (sf.net's list archive interface is really bad.) >>> I have been using Trac for a while now and I quite like it, but what >>> do you people think? >> I haven't really used Trac myself, yet. I'v only looked at it quickly >> when comparing features to other trackers (such as roundup). > > Trac does more than just issue tracking. I would also expect that the > way that you can link between tickets and both the wiki pages and the > Subversion revisions and changesets would mean that bug reports would > receive more attention than they have been receiving. Right. >> If you are comfortable, you should use it. You are the main person who >> will be affected by it. > > That is true, but while it is true, it's not necessarily the best > possible arrangement. > > And if I did all major changes without signalling them or inviting > comment, then I could soon be the only person affected by them. Ah well. Don't be too afraid, though. With sf.net the expectations are pretty low, so almost anything will be a win. ;-) > Talking about it beforehand also gives people a chance to chime in > with alternative, and possibly better, solutions. FWIW, we are in the process to migrate python.org's issue tracker from sf.net to a new site, using roundup. They evaluated a couple of alternative candidates, among them Trac. However, Their requirements are different from yours, and so that doesn't have to mean much in this context. >From all I have heared, Trac is a very good tool. Best regards, Stefan -- ...ich hab' noch einen Koffer in Berlin... |
|
From: Tony G. <Ton...@Me...> - 2007-02-01 20:35:35
|
On Thu, Feb 01 2007 16:57:49 +0000, Stefan Seefeld wrote: > Tony Graham wrote: >> I have it in mind to move xmlroff off CVS on SourceForge to a >> Subversion repository hosted on xmlroff.org (which would also move off >> SourceForge's servers). > > Do you already have a host for xmlroff.org ? I registered the hostname several years ago on some anniversary of Sun's open-sourcing of xmlroff and then doing nothing with it. www.xmlroff.org is currently aliased to SourceForge vhost.sourceforge.net, so http://xmlroff.org is currently served from the SourceForge project's htdocs directory. I now have other webhosting that allows hosting multiple domains for no extra charge, so I am better placed than ever before to be able to host xmlroff.org off SourceForge. One more change would probably be to also move xmlroff-list off SourceForge and on to xmlroff.org. >> I would then choose to use Trac (http://trac.edgewall.com/) for the >> new xmlroff website, ticket tracking system, and repository browser. >> >> I have been using Trac for a while now and I quite like it, but what >> do you people think? > > I haven't really used Trac myself, yet. I'v only looked at it quickly > when comparing features to other trackers (such as roundup). Trac does more than just issue tracking. I would also expect that the way that you can link between tickets and both the wiki pages and the Subversion revisions and changesets would mean that bug reports would receive more attention than they have been receiving. > If you are comfortable, you should use it. You are the main person who > will be affected by it. That is true, but while it is true, it's not necessarily the best possible arrangement. And if I did all major changes without signalling them or inviting comment, then I could soon be the only person affected by them. Talking about it beforehand also gives people a chance to chime in with alternative, and possibly better, solutions. Regards, Tony. |
|
From: Stefan S. <se...@sy...> - 2007-02-01 16:58:28
|
Tony Graham wrote: > I have it in mind to move xmlroff off CVS on SourceForge to a > Subversion repository hosted on xmlroff.org (which would also move off > SourceForge's servers). Do you already have a host for xmlroff.org ? > I would then choose to use Trac (http://trac.edgewall.com/) for the > new xmlroff website, ticket tracking system, and repository browser. > > I have been using Trac for a while now and I quite like it, but what > do you people think? I haven't really used Trac myself, yet. I'v only looked at it quickly when comparing features to other trackers (such as roundup). If you are comfortable, you should use it. You are the main person who will be affected by it. Thanks, Stefan -- ...ich hab' noch einen Koffer in Berlin... |
|
From: Noah S. <ns...@gm...> - 2007-02-01 16:40:25
|
Tony, > I have been using Trac for a while now and I quite like it, but what > do you people think? Trac is an excellent choice. I have been using it for 2 years now both professionally and personally. It makes the perfect compliment to Subversion or SVK. Noah |
|
From: Tony G. <Ton...@Me...> - 2007-02-01 16:34:36
|
I have it in mind to move xmlroff off CVS on SourceForge to a Subversion repository hosted on xmlroff.org (which would also move off SourceForge's servers). I would then choose to use Trac (http://trac.edgewall.com/) for the new xmlroff website, ticket tracking system, and repository browser. I have been using Trac for a while now and I quite like it, but what do you people think? Regards, Tony. |
|
From: SourceForge.net <no...@so...> - 2006-12-15 12:28:28
|
Bugs item #1616349, was opened at 2006-12-15 23:28 Message generated for change (Tracker Item Submitted) made by Item Submitter You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=536897&aid=1616349&group_id=73148 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: configure, make, install, etc. Group: None Status: Open Resolution: None Priority: 5 Private: No Submitted By: Ken Yap (ken_yap) Assigned to: Tony Graham (tonygraham) Summary: 0.3.99 fails to link Initial Comment: After I worked around that last fo-image.c problem by removing the extra argument and the error test after it, I get this output from make. Those errors with multiple definitions look serious. At this point I am stumped. I attach the make output. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=536897&aid=1616349&group_id=73148 |
|
From: SourceForge.net <no...@so...> - 2006-12-15 12:12:31
|
Bugs item #1616335, was opened at 2006-12-15 23:12 Message generated for change (Tracker Item Submitted) made by Item Submitter You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=536897&aid=1616335&group_id=73148 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: configure, make, install, etc. Group: None Status: Open Resolution: None Priority: 5 Private: No Submitted By: Ken Yap (ken_yap) Assigned to: Tony Graham (tonygraham) Summary: 0.39 fails to compile fo-image.c Initial Comment: gcc -DHAVE_CONFIG_H -I. -I. -I.. -DG_LOG_DOMAIN=\"libfo\" -pthread -I/opt/gnome/include/glib-2.0 -I/opt/gnome/lib/glib-2.0/include -I/usr/include/libxml2 -I/opt/gnome/include/gdk-pixbuf-1.0 -I/opt/gnome/include -I/opt/gnome/include/gtk-1.2 -I/opt/gnome/include/glib-1.2 -I/opt/gnome/lib/glib/include -I.. -g -O2 -pthread -I/opt/gnome/include/glib-2.0 -I/opt/gnome/lib/glib-2.0/include -MT fo-image.lo -MD -MP -MF .deps/fo-image.Tpo -c fo-image.c -fPIC -DPIC -o .libs/fo-image.o fo-image.c: In function 'fo_image_set_uri': fo-image.c:278: error: too many arguments to function 'gdk_pixbuf_new_from_file' make[2]: *** [fo-image.lo] Error 1 make[2]: Leaving directory `/usr/local/src/xmlroff-0.3.99/util' According to the API, this function takes only the filename argument, and error is detected by a return of NULL. I appear to have version 2.2 of gdk-pixbuf. The gcc version is 4.1 if it matters. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=536897&aid=1616335&group_id=73148 |
|
From: SourceForge.net <no...@so...> - 2006-12-15 12:07:51
|
Bugs item #1616334, was opened at 2006-12-15 23:07 Message generated for change (Tracker Item Submitted) made by Item Submitter You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=536897&aid=1616334&group_id=73148 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: configure, make, install, etc. Group: v0.3.x Status: Open Resolution: None Priority: 5 Private: No Submitted By: Ken Yap (ken_yap) Assigned to: Tony Graham (tonygraham) Summary: 0.39 cannot find pango-xsl-attributes.h Initial Comment: Include file cannot be found because it is actually in pangoxsl/pangoxsl/pango-xsl-attributes.h. I worked around this by making a symlink from pangoxsl/pangoxsl/pango-xsl-attributes.h to pangoxsl/pango-xsl-attributes.h ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=536897&aid=1616334&group_id=73148 |
|
From: SourceForge.net <no...@so...> - 2006-12-15 12:06:16
|
Bugs item #1616333, was opened at 2006-12-15 23:06 Message generated for change (Tracker Item Submitted) made by Item Submitter You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=536897&aid=1616333&group_id=73148 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: configure, make, install, etc. Group: v0.3.x Status: Open Resolution: None Priority: 5 Private: No Submitted By: Ken Yap (ken_yap) Assigned to: Tony Graham (tonygraham) Summary: 0.39 cannot detect gdk-pixbuf Initial Comment: As supplied by my vendor (OpsnSUSE 10.2), gdk-pixbuf has no metadata file for pkg-config, so the configure test fails, but it has a config info program in /opt/gnome/bin/gdk-pixbuf-config. This has to be run with the arguments --libs and --cflags in turn to extract the desired info. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=536897&aid=1616333&group_id=73148 |
|
From: Tony G. <tk...@me...> - 2006-08-22 23:13:16
|
Ilmari, Welcome to xmlroff and the xmlroff-list. Ilmari Vacklin <ilm...@he...> writes: > on Ubuntu 6.06, building xmlroff 0.3.99 fails with the following error > message (the error is present in multiple files, as you'll see later): ... > I've attached the make logs before and after the path munging, and the > config.log generated by ./configure. > > I'm sorry I couldn't diagnose the problem further, but my C-fu is very > weak. This needs Autotools-fu, which is even more mystical than C-fu. I don't know why configure is not finding the bundled PangoXSL. As I said in IRC on #xmlroff, I have checked in a modified xmlroff 'configure.in' that does away with running 'configure' twice. If you are able to access xmlroff CVS, please check out the current code, copy across the 'pangoxsl' directory from xmlroff-0.3.99, and run './autogen.sh' to create and run a new xmlroff 'configure' script. Regards, Tony. |
|
From: Ilmari V. <ilm...@he...> - 2006-08-17 22:42:55
|
Hello all, on Ubuntu 6.06, building xmlroff 0.3.99 fails with the following error message (the error is present in multiple files, as you'll see later): fo-layout.c:12:43: error: pangoxsl/pango-xsl-attributes.h: No such file or directory The error seems to be caused by the path in the include statement on that line: #include <pangoxsl/pango-xsl-attributes.h> The correct path from the build directory to pango-xsl-attributes.h is <pangoxsl/pangoxsl/pango-xs-attributes.h>. This error is present in many .c and .h files in the project. After running find . -iname '*.[ch]' | xargs perl -pi -e's|#include <pangoxsl/| #include <pangoxsl/pangoxsl/|' to fix the paths, the build proceeds further, but then fails on: ./.libs/libfo-0.4.a(libfo_fodoc_la-fo-doc-gp.o): In function `fo_doc_gp_do_run_callbacks':/home/wolverian/xmlroff-0.3.99/libfo/fo-doc-gp.c:1166: undefined reference to `pango_attr_callback_get_type' and to other similar errors. I've attached the make logs before and after the path munging, and the config.log generated by ./configure. I'm sorry I couldn't diagnose the problem further, but my C-fu is very weak. -- Ilmari Vacklin <ilm...@he...> |
|
From: Tony G. <Ton...@Su...> - 2006-08-10 08:58:45
|
xmlroff 0.3.99 is now available from http://sourceforge.net/projects/xmlroff/ Updated 'testing' and 'testsuite' modules are also available. This is a snapshot of development as of when I heard that I am losing my day job, (though my day job was unrelated to xmlroff). Expect 0.4.0 when I finally finish up, and expect the following release to be 0.5.0 so there's a clear break between what I did at Sun and what I did after Sun. Regards, Tony. Release Name: 0.3.99 Notes: Changes between 0.3.98 and 0.3.99 * xmlroff manpage in DocBook XML (Oliver Kiddle) * Cairo backend is less experimental * Added Cairo backend SVG output that is really experimental * Added handling of base for relative URIs when '--compat' is used * Handles 'auto' for page width and height (1159713) * Reworked checking for popt (1207495) Changes: 2006-08-10 Tony Graham <ton...@us...> * === Released 0.3.99 === * NEWS: Updated for 0.3.99. * Makefile.am: Removed this directory's 'xmlroff.fo' from distribution since 'xmlroff.fo' now produced and packaged in 'docs' directory. * configure.in: Added extra blank lines after messages about whether or not to rerun 'configure'. * xmlroff.spec.in: Added dependency on popt-devel. 2006-08-07 Tony Graham <ton...@us...> * libfo/fo-xslt-transformer.c: More playing with base for relative URIs. * libfo/fo-doc-cairo.c: Line dash and line cap are working except for top borders of blocks. 2006-07-27 Tony Graham <ton...@us...> * libfo/fo-doc-cairo.c: Corrected fo_doc_cairo_move_to(). Fixed several bugs in Cairo backend. 2006-07-26 Tony Graham <ton...@us...> * libfo/libfo-compat.c.tmpl: Added setting base URL of comatible result document to that of original result doc so relative URLs still work. * libfo/fo-xml-doc.c, libfo/fo-xml-doc.h: Added functions to get and set base URL. * Makefile.am: Removed POPT_LIBS from libfo libs. * configure.in: Reworked checking for popt.h and libpopt. 2006-07-25 Tony Graham <ton...@us...> * datatype/fo-length.c, datatype/fo-length.h, property/fo-property-page-height.c, property/fo-property-page-width.c: 'auto' page-height and page-width default to A4 height and width. * property/fo-property.c, property/fo-property.h: Added check for zero-length property values. AFAICT, no property can have a zero-length value. 2006-07-24 Tony Graham <ton...@us...> * configure.in: Added helpful message about rerunning 'configure' when building using bundled PangoXSL. 2006-07-22 Tony Graham <ton...@us...> * libfo/fo-doc-gp.c: Removed second prototype and reference to fo_doc_gp_translate. 2006-07-13 Tony Graham <ton...@us...> * libfo/fo-doc-cairo.c: Added pango_cairo_font_map_set_resolution() call so text output is now the right size. Other reformatting. * libfo-0.4.pc.in: Hardcoded library version 0.4 while xmlroff version is 0.3.99. * configure.in: Upped required Cairo version, if used, to 1.2.0 since that's the minimum for producing useful PDF, PostScript, and SVG. 2006-07-03 Tony Graham <ton...@us...> * libfo/fo-doc-cairo.c: Added SVG output. Moved error message strings to fo-doc.c. * README: Added that xmlroff executable depends on popt. * libfo/fo-doc.c: Added a message string from fo-d0c-cairo.c. * configure.in: Upped version to 0.3.99. |
|
From: Teus B. <te...@te...> - 2006-08-05 09:42:24
|
Hope you find a new job soon. Teus. Tony Graham wrote: > The Java project that was my day job has incurred a disinvestment, > with the result that I am a disinvestmenteee (if there is such a > word). > > In the short term, I may well have more time to spend on xmlroff (in > between job interviews, that is), and in the longer term, I would > anticipate that xmlroff would continue to be developed, but with my > name (or your name, if you also contribute) on the copyright for new > material. > > Regards, > > > Tony. > > ------------------------------------------------------------------------- > Take Surveys. Earn Cash. Influence the Future of IT > Join SourceForge.net's Techsay panel and you'll get the chance to share your > opinions on IT & business topics through brief surveys -- and earn cash > http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV > _______________________________________________ > xmlroff-list mailing list > xml...@li... > https://lists.sourceforge.net/lists/listinfo/xmlroff-list > > > |
|
From: Tony G. <men...@us...> - 2006-08-04 23:58:38
|
The Java project that was my day job has incurred a disinvestment, with the result that I am a disinvestmenteee (if there is such a word). In the short term, I may well have more time to spend on xmlroff (in between job interviews, that is), and in the longer term, I would anticipate that xmlroff would continue to be developed, but with my name (or your name, if you also contribute) on the copyright for new material. Regards, Tony. |
|
From: Stefan S. <se...@sy...> - 2006-07-28 17:56:55
|
Tony Graham wrote:
> What is, or should be, the base URI (for purposes of resolving relative URIs
> in "url('...')") for an FO document that is the result of xmlroff transforming
> an input XML document with an input XSLT stylesheet?
>
> Is it:
>
> - The current directory?
>
> - The directory of the input XML document?
>
> - The directory of the input XSLT stylesheet?
>
> - None?
>
> - Something else?
I believe it should be the directory of the input XML document.
> I'm working on testing the DocBook testdocs, which have relative URI
> references in them, and the relative URIs end up as "url('...')".
>
> To make matters worse, the relative URIs don't resolve from the test docs
> anyway. For example, if 'docbook-testdocs-1.1/tests/stamp.001.xml' refers to
> 'graphics/stamp.png', the actual 'stamp.png' is in the testdocs distribution
> as 'docbook-testdocs-1.1/graphics/stamp.png', not as
> 'docbook-testdocs-1.1/tests/graphics/stamp.png'.
Who is the maintainer of docbook-testdocs-1.1 ? Norman Walsh ? Bob Stayton ?
They should know...
> I can rearrange the testdocs (or add symbolic links) so relative URIs resolve,
> but that still leaves me wondering about what the correct base URI for the FO
> document that is the result of a transformation.
I agree. I remember long discussions related to xml:base when xi:include support
was added to docbook a while ago. I'd suggest you resend the mail to the docbook
lists (do...@li... and / or doc...@li...)
Thanks,
Stefan
--
...ich hab' noch einen Koffer in Berlin...
|
|
From: Tony G. <Ton...@Su...> - 2006-07-28 16:51:02
|
What is, or should be, the base URI (for purposes of resolving relative URIs
in "url('...')") for an FO document that is the result of xmlroff transforming
an input XML document with an input XSLT stylesheet?
Is it:
- The current directory?
- The directory of the input XML document?
- The directory of the input XSLT stylesheet?
- None?
- Something else?
I'm working on testing the DocBook testdocs, which have relative URI
references in them, and the relative URIs end up as "url('...')".
To make matters worse, the relative URIs don't resolve from the test docs
anyway. For example, if 'docbook-testdocs-1.1/tests/stamp.001.xml' refers to
'graphics/stamp.png', the actual 'stamp.png' is in the testdocs distribution
as 'docbook-testdocs-1.1/graphics/stamp.png', not as
'docbook-testdocs-1.1/tests/graphics/stamp.png'.
I can rearrange the testdocs (or add symbolic links) so relative URIs resolve,
but that still leaves me wondering about what the correct base URI for the FO
document that is the result of a transformation.
Regards,
Tony.
|
|
From: Tony G. <Ton...@Su...> - 2006-07-27 23:55:15
|
The 'testing' module has been reworked to get its configuration through 'configure' and do its processing using Make targets. The next step is to generate files of Make targets and dependencies corresponding to the individual tests and the various 'testsuite.xml' files so that if, for example, just a single test is modified, then Make will rerun just that test and remake the report. The logic for walking the 'testsuites.xml' and various 'testsuite.xml' files already exists, since that's how the reports are generated. It just needs to be reapplied to make Make do the right thing and do as little of it as necessary for the situation. Any takers? Regards, Tony. |
|
From: Tony G. <Ton...@Su...> - 2006-07-25 10:04:50
|
Teus Benschop <te...@te...> writes: > Tony Graham wrote: > Teus Benschop <te...@te...> writes: > Thanks for the support. It now formats the xsl-fo document without even one error. > > That's good. Does it also work without '--compat'? > > Without --compat it gives a couple of errors: > > [teus@localhost parallelbible]$ xmlroff document.fo > > (process:8108): libfo-CRITICAL **: fo-fo-error: Cannot rewrite fo:block content.Object path: /FoTree[1]/root[1]/page-sequence[1]/static-content[2]/table[1]/table-body[1]/table-row[1]/table-cell[3]/block[1] > Object path: /FoTree[1]/root[1]/page-sequence[1]/static-content[2]/table[1]/table-body[1]/table-row[1]/table-cell[3]/block[1] > > (process:8108): libfo-CRITICAL **: fo-fo-error: Cannot rewrite fo:block content.Object path: /FoTree[1]/root[1]/page-sequence[1]/static-content[3]/table[1]/table-body[1]/table-row[1]/table-cell[3]/block[1] > Object path: /FoTree[1]/root[1]/page-sequence[1]/static-content[3]/table[1]/table-body[1]/table-row[1]/table-cell[3]/block[1] xmlroff is not coping with the fo:retrieve-marker and fo:leader. I don't know why. ... > You know what: Because of your use of Pango, it formats the Unicode Hebrew better than XEP does. > > Music to my ears. Using Pango has meant a lot of work at various times, so > it's nice to know that it also pays off at times. > > Pls. keep using it, because there is no renderer equal to Pango in the area > of Unicode rendering. And Pango is open, so that people can contribute code > to it that deals with otherwise overlooked minority languages. That was the original motivation: as Pango adds support for new scripts, xmlroff adds support for new scripts with (hopefully) no effort on our part. Regards, Tony. |
|
From: SourceForge.net <no...@so...> - 2006-07-25 08:48:34
|
Feature Requests item #1528250, was opened at 2006-07-25 10:48 Message generated for change (Tracker Item Submitted) made by Item Submitter You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=536900&aid=1528250&group_id=73148 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: xmlroff Improvements Group: Next Release Status: Open Resolution: None Priority: 5 Submitted By: Teus Benschop (teus) Assigned to: Tony Graham (tonygraham) Summary: Support for fo:repeatable-page-master-alternatives Initial Comment: Request: By the way, when do you think that support for fo:repeatable-page-master-alternatives will be in xsmroff? I need it for setting the margins depending on whether it is an even or an odd page. First reply: Since this is open source, the most certain way to get it implemented is for you to do it and contribute it to xmlroff. You could file a feature request on the SourceForge project and/or you could agitate to have it added to the "Big Itches" section of the planning page at http://xmlroff.org/implementation-sequence.html SourceForge doesn't have a voting mechanism for bugs or feature requests AFAIK, so if others see it as a priority, they'll have to chime in on the mailing list to make their opinions known. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=536900&aid=1528250&group_id=73148 |
|
From: Teus B. <te...@te...> - 2006-07-25 01:20:10
|
Hi Tony, Tony Graham wrote: > Teus Benschop <te...@te...> writes: > >> Thanks for the support. It now formats the xsl-fo document without even one error. >> > > That's good. Does it also work without '--compat'? > > Without --compat it gives a couple of errors: [teus@localhost parallelbible]$ xmlroff document.fo (process:8108): libfo-CRITICAL **: fo-fo-error: Cannot rewrite fo:block content.Object path: /FoTree[1]/root[1]/page-sequence[1]/static-content[2]/table[1]/table-body[1]/table-row[1]/table-cell[3]/block[1] Object path: /FoTree[1]/root[1]/page-sequence[1]/static-content[2]/table[1]/table-body[1]/table-row[1]/table-cell[3]/block[1] (process:8108): libfo-CRITICAL **: fo-fo-error: Cannot rewrite fo:block content.Object path: /FoTree[1]/root[1]/page-sequence[1]/static-content[3]/table[1]/table-body[1]/table-row[1]/table-cell[3]/block[1] Object path: /FoTree[1]/root[1]/page-sequence[1]/static-content[3]/table[1]/table-body[1]/table-row[1]/table-cell[3]/block[1] > BTW, I added a warning message to the 'configure.in' in CVS to make it obvious > when you need to re-run 'configure' because of building with the bundled > PangoXSL. > Great! That will prevent some future support requests, most probably. > >> You know what: Because of your use of Pango, it formats the Unicode Hebrew better than XEP does. >> > > Music to my ears. Using Pango has meant a lot of work at various times, so > it's nice to know that it also pays off at times. > > Pls. keep using it, because there is no renderer equal to Pango in the area of Unicode rendering. And Pango is open, so that people can contribute code to it that deals with otherwise overlooked minority languages. >> Thanks for the job you are doing. >> > > My pleasure. I wish I had more time for it. > > >> By the way, when do you think that support for >> fo:repeatable-page-master-alternatives will be in xsmroff? I need it for >> setting the margins depending on whether it is an even or an odd page. >> > > Since this is open source, the most certain way to get it implemented is for > you to do it and contribute it to xmlroff. > > You could file a feature request on the SourceForge project and/or you could > agitate to have it added to the "Big Itches" section of the planning page at > http://xmlroff.org/implementation-sequence.html > > SourceForge doesn't have a voting mechanism for bugs or feature requests > AFAIK, so if others see it as a priority, they'll have to chime in on the > mailing list to make their opinions known. > > The fundamental problem is xmlroff development really only happens in my spare > time, and there's less of that than there are improvements to be made. > > Okay, I will see what to do - probably making some noise about it, as you say, and see if the fix wouldn't be too difficult to do it myself. Thanks, Teus. > Regards, > > > Tony. > > >> Regards, >> >> Teus. >> >> Tony Graham wrote: >> >> Teus Benschop <te...@te...> writes: >> >> Formatting the xsl-fo file given below fails with these messages: >> >> [teus@localhost references]$ xmlroff --compat document.fo >> (process:24370): libfo-CRITICAL **: >> fo_area_table_split_before_height_check: assertion `max_height > 0' failed >> >> (process:24370): libfo-CRITICAL **: fo_area_table_split_before_height: >> assertion `max_height > 0' failed >> >> Is this because of errors in the .fo file? >> >> No. xmlroff does not yet support fo:repeatable-page-master-alternatives >> (which, while useful, is not required for 'basic' conformance). >> >> See http://xmlroff.org/conformance.html >> >> xmlroff also doesn't implement the fallback behaviour. The fallback would be >> to select the 'blank-page' master, which also might not be what you expect. >> >> ... >> >> <fo:page-sequence-master master-name="text"> >> <fo:repeatable-page-master-alternatives> >> <fo:conditional-page-master-reference >> blank-or-not-blank="blank" master-reference="blank-page"/> >> <fo:conditional-page-master-reference odd-or-even="odd" >> master-reference="odd-page"/> >> <fo:conditional-page-master-reference odd-or-even="even" >> master-reference="even-page"/> >> </fo:repeatable-page-master-alternatives> >> </fo:page-sequence-master> >> >> Regards, >> >> Tony. >> >> ------------------------------------------------------------------------- >> Take Surveys. Earn Cash. Influence the Future of IT >> Join SourceForge.net's Techsay panel and you'll get the chance to share your >> opinions on IT & business topics through brief surveys -- and earn cash >> http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV >> _______________________________________________ >> xmlroff-list mailing list >> xml...@li... >> https://lists.sourceforge.net/lists/listinfo/xmlroff-list >> >> ------------------------------------------------------------------------- >> Take Surveys. Earn Cash. Influence the Future of IT >> Join SourceForge.net's Techsay panel and you'll get the chance to share your >> opinions on IT & business topics through brief surveys -- and earn cash >> http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV >> _______________________________________________ >> xmlroff-list mailing list >> xml...@li... >> https://lists.sourceforge.net/lists/listinfo/xmlroff-list >> > > > ------------------------------------------------------------------------- > Take Surveys. Earn Cash. Influence the Future of IT > Join SourceForge.net's Techsay panel and you'll get the chance to share your > opinions on IT & business topics through brief surveys -- and earn cash > http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV > _______________________________________________ > xmlroff-list mailing list > xml...@li... > https://lists.sourceforge.net/lists/listinfo/xmlroff-list > > > |
|
From: Tony G. <Ton...@Su...> - 2006-07-24 16:38:08
|
Teus Benschop <te...@te...> writes: > Thanks for the support. It now formats the xsl-fo document without even one error. That's good. Does it also work without '--compat'? BTW, I added a warning message to the 'configure.in' in CVS to make it obvious when you need to re-run 'configure' because of building with the bundled PangoXSL. > You know what: Because of your use of Pango, it formats the Unicode Hebrew better than XEP does. Music to my ears. Using Pango has meant a lot of work at various times, so it's nice to know that it also pays off at times. > Thanks for the job you are doing. My pleasure. I wish I had more time for it. > By the way, when do you think that support for > fo:repeatable-page-master-alternatives will be in xsmroff? I need it for > setting the margins depending on whether it is an even or an odd page. Since this is open source, the most certain way to get it implemented is for you to do it and contribute it to xmlroff. You could file a feature request on the SourceForge project and/or you could agitate to have it added to the "Big Itches" section of the planning page at http://xmlroff.org/implementation-sequence.html SourceForge doesn't have a voting mechanism for bugs or feature requests AFAIK, so if others see it as a priority, they'll have to chime in on the mailing list to make their opinions known. The fundamental problem is xmlroff development really only happens in my spare time, and there's less of that than there are improvements to be made. Regards, Tony. > Regards, > > Teus. > > Tony Graham wrote: > > Teus Benschop <te...@te...> writes: > > Formatting the xsl-fo file given below fails with these messages: > > [teus@localhost references]$ xmlroff --compat document.fo > (process:24370): libfo-CRITICAL **: > fo_area_table_split_before_height_check: assertion `max_height > 0' failed > > (process:24370): libfo-CRITICAL **: fo_area_table_split_before_height: > assertion `max_height > 0' failed > > Is this because of errors in the .fo file? > > No. xmlroff does not yet support fo:repeatable-page-master-alternatives > (which, while useful, is not required for 'basic' conformance). > > See http://xmlroff.org/conformance.html > > xmlroff also doesn't implement the fallback behaviour. The fallback would be > to select the 'blank-page' master, which also might not be what you expect. > > ... > > <fo:page-sequence-master master-name="text"> > <fo:repeatable-page-master-alternatives> > <fo:conditional-page-master-reference > blank-or-not-blank="blank" master-reference="blank-page"/> > <fo:conditional-page-master-reference odd-or-even="odd" > master-reference="odd-page"/> > <fo:conditional-page-master-reference odd-or-even="even" > master-reference="even-page"/> > </fo:repeatable-page-master-alternatives> > </fo:page-sequence-master> > > Regards, > > Tony. > > ------------------------------------------------------------------------- > Take Surveys. Earn Cash. Influence the Future of IT > Join SourceForge.net's Techsay panel and you'll get the chance to share your > opinions on IT & business topics through brief surveys -- and earn cash > http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV > _______________________________________________ > xmlroff-list mailing list > xml...@li... > https://lists.sourceforge.net/lists/listinfo/xmlroff-list > > ------------------------------------------------------------------------- > Take Surveys. Earn Cash. Influence the Future of IT > Join SourceForge.net's Techsay panel and you'll get the chance to share your > opinions on IT & business topics through brief surveys -- and earn cash > http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV > _______________________________________________ > xmlroff-list mailing list > xml...@li... > https://lists.sourceforge.net/lists/listinfo/xmlroff-list |
|
From: Teus B. <te...@te...> - 2006-07-24 15:38:58
|
Hi Tony, Thanks for the support. It now formats the xsl-fo document without even one error. You know what: Because of your use of Pango, it formats the Unicode Hebrew better than XEP does. Thanks for the job you are doing. By the way, when do you think that support for fo:repeatable-page-master-alternatives will be in xsmroff? I need it for setting the margins depending on whether it is an even or an odd page. Regards, Teus. Tony Graham wrote: > Teus Benschop <te...@te...> writes: > >> Formatting the xsl-fo file given below fails with these messages: >> >> [teus@localhost references]$ xmlroff --compat document.fo >> (process:24370): libfo-CRITICAL **: >> fo_area_table_split_before_height_check: assertion `max_height > 0' failed >> >> (process:24370): libfo-CRITICAL **: fo_area_table_split_before_height: >> assertion `max_height > 0' failed >> >> >> Is this because of errors in the .fo file? >> > > No. xmlroff does not yet support fo:repeatable-page-master-alternatives > (which, while useful, is not required for 'basic' conformance). > > See http://xmlroff.org/conformance.html > > xmlroff also doesn't implement the fallback behaviour. The fallback would be > to select the 'blank-page' master, which also might not be what you expect. > > ... > >> <fo:page-sequence-master master-name="text"> >> <fo:repeatable-page-master-alternatives> >> <fo:conditional-page-master-reference >> blank-or-not-blank="blank" master-reference="blank-page"/> >> <fo:conditional-page-master-reference odd-or-even="odd" >> master-reference="odd-page"/> >> <fo:conditional-page-master-reference odd-or-even="even" >> master-reference="even-page"/> >> </fo:repeatable-page-master-alternatives> >> </fo:page-sequence-master> >> > > Regards, > > > Tony. > > > ------------------------------------------------------------------------- > Take Surveys. Earn Cash. Influence the Future of IT > Join SourceForge.net's Techsay panel and you'll get the chance to share your > opinions on IT & business topics through brief surveys -- and earn cash > http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV > _______________________________________________ > xmlroff-list mailing list > xml...@li... > https://lists.sourceforge.net/lists/listinfo/xmlroff-list > > > |
|
From: Tony G. <Ton...@Su...> - 2006-07-24 14:57:44
|
Teus Benschop <te...@te...> writes: > Formatting the xsl-fo file given below fails with these messages: > > [teus@localhost references]$ xmlroff --compat document.fo > (process:24370): libfo-CRITICAL **: > fo_area_table_split_before_height_check: assertion `max_height > 0' failed > > (process:24370): libfo-CRITICAL **: fo_area_table_split_before_height: > assertion `max_height > 0' failed > > > Is this because of errors in the .fo file? No. xmlroff does not yet support fo:repeatable-page-master-alternatives (which, while useful, is not required for 'basic' conformance). See http://xmlroff.org/conformance.html xmlroff also doesn't implement the fallback behaviour. The fallback would be to select the 'blank-page' master, which also might not be what you expect. ... > <fo:page-sequence-master master-name="text"> > <fo:repeatable-page-master-alternatives> > <fo:conditional-page-master-reference > blank-or-not-blank="blank" master-reference="blank-page"/> > <fo:conditional-page-master-reference odd-or-even="odd" > master-reference="odd-page"/> > <fo:conditional-page-master-reference odd-or-even="even" > master-reference="even-page"/> > </fo:repeatable-page-master-alternatives> > </fo:page-sequence-master> Regards, Tony. |
|
From: Tony G. <Ton...@Su...> - 2006-07-24 10:18:24
|
Teus Benschop <te...@te...> writes: > The very first suggestion made by you, running configure twice, solved the problem. > > I guess I should have read the INSTALL file and not assume that xmlroff behaves like expected of a Linux package. xmlroff is unusual in that it bundles PangoXSL, on which it depends. Bundling PangoXSL with xmlroff is supposed to make it easier to build xmlroff compared to having to separately find and build PangoXSL before building xmlroff, but it appears to be creating more problems than it solves. There's also been a report of build failure after running 'configure' twice, so the bundling method obviously needs more work. As always, suggestions for improvements are welcome. Regards, Tony. |
2 messages has been excluded from this view by a project administrator.
