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: Tony G. <Ton...@Su...> - 2005-01-28 11:43:36
|
In advance of the xmlroff 0.3.1 release (which should be this weekend), I have added the xmlroff 0.3.1 reference manual and test results report to the xmlroff website. Comments and suggestions for improvements are welcome. I have also added a 'Ports' page, which currently only lists the FreeBSD port. Regards, Tony. |
|
From: James E. <ja...@ic...> - 2005-01-24 19:51:01
|
On 01/24/05 10:21:33, Tony Graham wrote: > James Earl <ja...@ic...> writes: > > xmlroff is now part of the FreeBSD ports collection: > > > > http://www.freshports.org/textproc/xmlroff/ >=20 > That sounds good. Thank you for doing this. >=20 > What does this mean to the average FreeBSD user? >=20 > Also, what changes were necessary between 0.3.0 and 0.3.0_2? > This basically means that FreeBSD users will be able to easily install/=20 uninstall/upgrade xmlroff (and it's dependencies) from pre-compiled =20 packages or source code. More information is available here: http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/ports.html The changes which may be of interest are these: http://www.freebsd.org/cgi/cvsweb.cgi/ports/textproc/xmlroff/files/ These patches were submitted by a FreeBSD developer (hrs at =20 FreeBSD.org) to fix the xmlroff build on FreeBSD 4.x systems. You may =20 want to contact him for further information. Unfortunately I'm not a C =20 developer. James |
|
From: Tony G. <Ton...@Su...> - 2005-01-24 17:20:49
|
James Earl <ja...@ic...> writes: > xmlroff is now part of the FreeBSD ports collection: > > http://www.freshports.org/textproc/xmlroff/ That sounds good. Thank you for doing this. What does this mean to the average FreeBSD user? Also, what changes were necessary between 0.3.0 and 0.3.0_2? Regards, Tony. |
|
From: James E. <ja...@ic...> - 2005-01-24 16:23:12
|
Hi, xmlroff is now part of the FreeBSD ports collection: http://www.freshports.org/textproc/xmlroff/ James |
|
From: Tony G. <Ton...@Su...> - 2005-01-04 13:31:26
|
Steinar Bang <sb...@do...> writes: ... > I'm still using gmane primarily because it gives me NNTP access to > mailing lists. Regardless of how you read the xmlroff-list, you should post from a subscribed address (which you didn't do). Since the Mailman software lets you configure your subscription so you don't get any mail, you can be subscribed, post messages, and still read the xmlroff-list messages using gmane. Regards, Tony. |
|
From: Steinar B. <sb...@do...> - 2004-12-18 09:32:16
|
FWIW it still is on gmane, which was nice for me, when I decided to give xmlroff a look, after a long pause. gmane has aquired a bit more polish since march of 2003. It now has two separate web interfaces, as well as an RSS feed from the lists: http://dir.gmane.org/gmane.text.xml.xmlroff.general I'm still using gmane primarily because it gives me NNTP access to mailing lists. |
|
From: Tony G. <Ton...@Su...> - 2004-11-04 10:25:44
|
Stefan Seefeld <se...@sy...> writes: > what's going on with the website right now ? > The 'news' page seems broken (it looks like > when you reported that it only contained > '<div class="rss"></div>'. Is the used > 'custom-website.xsl' file really the current > one from the repository ?) > Also, the front-page contains a redundant > 'soureforge' logo. > > Just in case you didn't notice... I hadn't. Thanks. The news is back, although you could have regenerated and installed it yourself. I didn't have the proxy-related environment variables set right when I regenerated all the HTML files last. I'll look into the logo problem tonight. Regards, Tony. |
|
From: Stefan S. <se...@sy...> - 2004-11-04 05:12:11
|
hi Tony, what's going on with the website right now ? The 'news' page seems broken (it looks like when you reported that it only contained '<div class="rss"></div>'. Is the used 'custom-website.xsl' file really the current one from the repository ?) Also, the front-page contains a redundant 'soureforge' logo. Just in case you didn't notice... Regards, Stefan |
|
From: Tony G. <Ton...@Su...> - 2004-10-29 10:54:52
|
Is there anybody else on this list who will be at XML 2004 in Washington, D.C. next month? Regards, Tony. |
|
From: Tony G. <Ton...@Su...> - 2004-10-27 21:36:58
|
There's been two changes in the CVS repository structure: - xmlroff/examples/io was moved to become the top-level libfo-examples module since it is released as the libfo-examples package. - pangoxsl was mistakenly imported into the xmlroff CVS repository. It has now been moved to the PangoPDF CVS repository. Regards, Tony. |
|
From: Tony G. <Ton...@Su...> - 2004-10-27 21:28:22
|
Andy Sanders <an...@se...> writes: > Hi, Hello, and welcome to the xmlroff-list. > I'm just wondering if there is an XSL-FO compliance list for xmlroff > like there is for FOP (http://xml.apache.org/fop/compliance.html#fo). http://xmlroff.org/conformance.html I do plan to include that conformance information in the xmlroff distributions, but I haven't done the groundwork to be able to produce the web page and the xmlroff documentation page from a single source. Ideally it would be done with an XSLT stylesheet and some additions to dump-info.xml in the spec-dump module. > Knowing in advance what does and does not work would be very handy. True. Note that there's now also a libfo-compat.xsl stylesheet in xmlroff 0.3.0 that you can use that tries to rewrite or remove various FOs and properties so xmlroff has a better chance of working with your document. It's a bit rough-and-ready, but I'd rather spend my time improving xmlroff than improving the stylesheet. However, patches are welcome. Regards, Tony. |
|
From: Andy S. <an...@se...> - 2004-10-26 08:27:27
|
Hi, I'm just wondering if there is an XSL-FO compliance list for xmlroff like there is for FOP (http://xml.apache.org/fop/compliance.html#fo). Knowing in advance what does and does not work would be very handy. Thanks Andy |
|
From: Tony G. <Ton...@Su...> - 2004-10-21 23:11:40
|
From the SourceForge news item: xmlroff 0.3.0 -- Free and PDFlib-free xmlroff (http://xmlroff.org) is an XSL Formatter written in C. xmlroff 0.3.0 builds solely on open source software since it no longer supports a PDFlib backend. It also plays well with GNOME desktops since it uses Pango and the new PangoXSL library (from the PangoPDF project) instead of the previous PangoPDF library. ------------------------------------------------------------ From the NEWS file: Changes between 0.2.8 and 0.3.0 * No more PDFlib backend * Uses PangoXSL, not PangoPDF * 'libfo-compat.xsl' stylesheet for ensuring compatibility of FO files ------------------------------------------------------------ From the ChangeLog file: 2004-10-21 Tony Graham <ton...@us...> * === Released 0.3.0 === * Makefile.am: Added back xmlroff.spec in EXTRA_DIST. * xmlroff.spec.in: Minor changes to match xmlroff 0.3.0. * Makefile.am: Added libfo-compat.xsl and xmlroff.fo to EXTRA_DIST. * libfo-compat.xsl: Stylesheet for reducing FO files to subset supported by libfo. * catalog.xml.in: Catalog file for libfo library. * INSTALL: Added section about 'libfo-compat.xsl'. * Makefile.am: Removed xmlroff_INCLUDES and xmlroff_CFLAGS. Added xmlroff.fo to xml_DATA. * NEWS: Updated for xmlroff 0.3.0. * README: Updated name and URL. * configure.in: Changed definition of 'ENABLE_GP'. Added 'catalog.xml' to AC_OUTPUT. * libfo-0.3.pc.in: Added 'compat_stylesheet' variable. Added pangoxsl to dependencies. * xmlroff.c: Changed definition of '-backend'. Removed '-compress'. * xmlroff.fo: Changed definition of '-backend'. 2004-10-12 Tony Graham <ton...@us...> * libfo-0.2.pc.in: Removed since library version is now 0.3. * area/fo-area-layout.c: fo_area_layout_resolve_text_align(): Added call to pango_layout_set_auto_dir() to turn off auto-dir since it caused more problems than it solved. Having it now causes problems for 'writing-direction' test, however. * libfo/fo-doc-gp.c: fo_doc_gp_render_layout_lines(): Added crop area around lines to be rendered since neither Pango nor GNOME Print supports rendering line ranges. fo_doc_gp_init(): Commented out call to gnome_print_pango_update_context() that doesn't do anything except cause a warning. * docs/xmlroff-docs.sgml, examples/io/gmodule-area-tree.c, examples/io/xmlroff-gmodule.c, examples/io/xmlroff-libfo.c, examples/io/xmlroff-text-tree.c, examples/io/xmlroff-text-tree2.c, libfo/fo-doc.c, libfo/fo-xsl-formatter.c, xmlroff.c: Expunged mentions of PDFlib. * examples/io/configure.ac, libfo/Makefile.am, libfo/fo-layout-gp.c, libfo/fo-layout.c, property/Makefile.am, property/fo-property-alignment-adjust.c, property/fo-property-alignment-baseline.c, property/fo-property-background-color.c, property/fo-property-baseline-shift.c, property/fo-property-color.c, property/fo-property-dominant-baseline.c, property/fo-property-font-family.c, property/fo-property-font-size.c, property/fo-property-keep-together-within-line.c, property/fo-property-keep-with-next-within-line.c, property/fo-property-keep-with-previous-within-line.c, property/fo-property-line-height.c, datatype/Makefile.am, docs/Makefile.am, fo/Makefile.am, fo/fo-block-area.c, fo/fo-external-graphic.c, Makefile.am, area/Makefile.am, configure.in, xmlroff.spec.in: Updated for changes from libfo-0.2 to libfo-0.3 and pangopdf to pangoxsl. * INSTALL: Updated for xmlroff 0.3.0 and PangoXSL 1.6.0.0. * ChangeLog.pre-0.3, ChangeLog: Moved old changes out of ChangeLog to ChangeLog.pre-0.3. 2004-10-10 Tony Graham <ton...@us...> * xmlroff.fo.in: Removed since unused. * libfo/fo-layout-pdflib-private.h, libfo/fo-layout-pdflib.c, libfo/fo-layout-pdflib.h, libfo/fo-doc-pdflib-private.h, libfo/fo-doc-pdflib.c, libfo/fo-doc-pdflib.h: Removed since PDFlib backend is no longer used. 2004-08-26 Tony Graham <ton...@us...> * xmlroff.fo: Re-adding since don't have PDFlib backend anymore. * libfo-0.3.pc.in: pkg-config file for libfo-0.3. * Makefile.am: Updated to use GNOME Print libs and new PangoPDF lib. * configure.in: Updated to use Pango 1.5, libgnomeprint 2.7, and new PangoPDF. Dropped PDFlib. * fo/fo-block-area.c, fo/fo-external-graphic.c: Changed #include to match changed location of pango-xsl-attributes.h. * libfo/Makefile.am: Removed PDFlib stuff from libfo/Makefile.am. * libfo/fo-layout-gp.c: Commented out functions for attributes not supported by PangoLayout. * libfo/fo-doc-gp.c: Changed to use GNOME Print functions for working with Pango. * libfo/fo-layout.c, property/fo-property-alignment-adjust.c, property/fo-property-alignment-baseline.c, property/fo-property-background-color.c, property/fo-property-baseline-shift.c, property/fo-property-color.c, property/fo-property-dominant-baseline.c, property/fo-property-font-family.c, property/fo-property-font-size.c, property/fo-property-keep-together-within-line.c, property/fo-property-keep-with-next-within-line.c, property/fo-property-keep-with-previous-within-line.c, property/fo-property-line-height.c: Changed #include to match changed location of pango-xsl-attributes.h. * libfo/fo-doc.c: Added cases for three new Pango directions. Regards, Tony. -- Tony Graham Sun Microsystems Ireland Phone: +353 1 8199708 East Point Business Park, Dublin 3 Internal: (70)19708 |
|
From: Tony G. <Ton...@Su...> - 2004-10-20 13:35:26
|
Tony Graham <Ton...@Su...> writes: > Please subscribe to the xmlroff-list rather than sending me mail > directly. ... >>> Jaromir Talir <ja...@ip...> writes: >>> > I would like to test xmlroff on Fedora Core 2 installation but: >>> > >>> > rpmbuild -tb pangoxsl-1.2.3.7.tar.gz >>> > - missing /usr/lib/libart_lgpl_2.la. I cannot find any package on my >>> > system that contains it. FWIW, I don't get that problem. No file on my system contains the text 'libart_lgpl_2.la'. Is it possible that you're using a version of libgnomeprint older than 2.8.0? ... >> I will try to play with spec file a bit and send you my result. Since you haven't commented on failures related to PangoPDF, it seems that you also have PangoPDF installed. Is that correct? Please try the attached spec file and reply to the list (after subscribing) about whether or not it works. Regards, Tony. |
|
From: Tony G. <Ton...@Su...> - 2004-10-18 22:12:55
|
Jaromir, Please subscribe to the xmlroff-list rather than sending me mail directly. Jaromir Talir <ja...@ip...> writes: > V P=C3=A1, 15. 10. 2004 v 15:55, Tony Graham p=C3=AD=C5=A1e: =2E.. > Now we are using fop but because of it's java nature resource > consumption are very high. Beside passiveTex I don't see any other = open > source solution other than xmlroff. From webpages of xmlroff I made > opinion that xmlroff is still in early stage of development. How wo= uld > you compared it's stability and level compared to fop, which seems > doesnt evolve for past year? I read the fop-dev mailing list, but I don't use FOP and I don't trac= k FOP's capabilities. To put a positive spin on xmlroff's progress over the last two years, most of the recent changes in xmlroff have been under the covers. xmlroff has gone from only using PDFlib to produce output, to using either PDFlib or GNOME Print, and now to only using GNOME Print; the property and enumeration token handling is much more consistent; the code generated by the spec-dump module more accurately reflects the current conventions for coding a property; and it's now possible to write parser routines for shorthand properties that don't follow the usual expression syntax. The downside of that has been that there hasn't been much increase in supported FOs and properties in that time. However, I believe that the project is on an upswing: the project has two new developers; the website is being actively updated; and the recent change to using Pango 1.6.0 and libgnomeprint 2.8.0 means both that we can stop futzing with backends for a while and that xmlroff now plays better with a GNOME installation. You can see the current state of xmlroff from the conformance page on the web site, but even I wouldn't say that it's ready for business documents. >> Jaromir Talir <ja...@ip...> writes: >> > I would like to test xmlroff on Fedora Core 2 installation but: >> > >> > rpmbuild -tb pangoxsl-1.2.3.7.tar.gz >> > - missing /usr/lib/libart_lgpl_2.la. I cannot find any package o= n my >> > system that contains it. >>=20 >> What about libart_lgpl_2.so? > > .so is OK but .la is missing. I have only basic knowledge abut this= and > I thing that this file is somewhat genereated by libtool but > libart_lgpl-devel-2.3.16-2.1 package which conains libart_lgpl_2.so > doesn't contain libart_lgpl_2.la and I've been searching a while an= d > none of packages can solve this dependency. I'm still working on this. I'll get back to you (unless someone else can solve it first). =2E.. >> I don't doubt that there's problems with the spec file. I can't s= ay >> that I understand them, and the PangoPDF spec file only worked tha= nks >> to the efforts of Tim Waugh. >>=20 >> Assuming that libpangoxsl-1.0 should be installed into the libdir >> (i.e., /usr/lib or /usr/local/lib), what changes would you make? >>=20 >> Regards, >>=20 >>=20 >> Tony. > > I will try to play with spec file a bit and send you my result. Thanks. Regards, Tony. |
|
From: Tony G. <Ton...@Su...> - 2004-10-15 13:55:54
|
Jaromir, Welcome to xmlroff and PangoPDF/PangoXSL. Please note that you should subscribe if you are to continue to post to this list and receive replies. Jaromir Talir <ja...@ip...> writes: > I would like to test xmlroff on Fedora Core 2 installation but: > > rpmbuild -tb pangoxsl-1.2.3.7.tar.gz > - missing /usr/lib/libart_lgpl_2.la. I cannot find any package on my > system that contains it. What about libart_lgpl_2.so? On my system, the .so file is from libart_lgpl-devel-2.3.13-230. AFAIK, libart_lgpl_2 is used by GNOME Print. > rpmbuild -tb pangoxsl-1.6.0.0.tar.gz > - spec file %files section doesn't conform to installed files. I would > repair it but don't know wich version is correct (spec or make > install) > - .pc file points to libdir /usr/lib/pangoxsl but Makefile installs > libraries into /usr/lib/ I don't doubt that there's problems with the spec file. I can't say that I understand them, and the PangoPDF spec file only worked thanks to the efforts of Tim Waugh. Assuming that libpangoxsl-1.0 should be installed into the libdir (i.e., /usr/lib or /usr/local/lib), what changes would you make? Regards, Tony. |
|
From: Jaromir T. <ja...@ip...> - 2004-10-15 08:59:53
|
I would like to test xmlroff on Fedora Core 2 installation but: rpmbuild -tb pangoxsl-1.2.3.7.tar.gz - missing /usr/lib/libart_lgpl_2.la. I cannot find any package on my system that contains it. rpmbuild -tb pangoxsl-1.6.0.0.tar.gz - spec file %files section doesn't conform to installed files. I would repair it but don't know wich version is correct (spec or make install) - .pc file points to libdir /usr/lib/pangoxsl but Makefile installs libraries into /usr/lib/ Jaromir Talir |
|
From: Tony G. <Ton...@Su...> - 2004-10-12 15:37:16
|
Hopefully I've checked in all of the code changes necessary to make an xmlroff 0.3.0, but I still need to update and regenerate the documentation and test the packaging, etc. I also intend to make the examples/xml2003/fixup.xsl stylesheet into something that can be installed as /usr/local/share/xml/libfo-0.3/libfo-compat.xsl to make it easier for users to munge their .fo files so they don't break xmlroff (which is all too easy to do). Regards, Tony. |
|
From: Tony G. <Ton...@Su...> - 2004-10-12 15:31:43
|
Stefan Seefeld <se...@sy...> writes: > Tony Graham wrote: > > > Shouldn't it be possible to be able to extract the project description > > from the xmlroff project's RSS and insert that in the generated > > index.html file for the xmlroff website? > > yes, it should... > > > Most of the description that's there now could easily be moved to the > > overview page instead. > > ...but is that such a good idea ? Note that I'v had my own projects on > sf.net, which I deliberately moved elsewhere because I found the service > offered by sf.net to be suboptimal. In this perspective I'm wondering > why one should add more dependencies to the sf.net infrastructure, > instead of rolling your own solution. > The more you are independent from sf.net the easier it will be for > you to migrate the project elsewhere when you decide to. > Please take this with a grain of salt. It's just my observation. YMMV. The problem I was trying to solve is that the change to the SourceForge project description isn't reflected in the xmlroff web site. The answer might be to not automate it, either because it's more trouble than it's worth or because it ties xmlroff too closely to SF. Of course, there's still the xmlroff README file and documentation files that also need to be updated, so it probably is a minor saving to be able to automatically update the xmlroff web site. If I was in the habit of updating the description once a week (which I'm not), then I would look to ways to update all descriptions of xmlroff from a single source. Right now, that looks like too much effort, so I guess I'll update the xmlroff web site the old-fashioned way. Regards, Tony. |
|
From: Tony G. <Ton...@Su...> - 2004-10-11 08:29:54
|
Tony Graham <Ton...@Su...> writes: > The first release of the reformulated PangoPDF is now available on > SourceForge as PangoXSL 1.6.0.0. I.e., as the 'pangoxsl' module of the 'pangopdf' project. See https://sourceforge.net/projects/pangopdf/. Regards, Tony. |
|
From: Tony G. <Ton...@Su...> - 2004-10-11 01:40:43
|
The first release of the reformulated PangoPDF is now available on SourceForge as PangoXSL 1.6.0.0. Regards, Tony. |
|
From: Stefan S. <se...@sy...> - 2004-10-09 02:46:24
|
Tony Graham wrote: > Shouldn't it be possible to be able to extract the project description > from the xmlroff project's RSS and insert that in the generated > index.html file for the xmlroff website? yes, it should... > Most of the description that's there now could easily be moved to the > overview page instead. ...but is that such a good idea ? Note that I'v had my own projects on sf.net, which I deliberately moved elsewhere because I found the service offered by sf.net to be suboptimal. In this perspective I'm wondering why one should add more dependencies to the sf.net infrastructure, instead of rolling your own solution. The more you are independent from sf.net the easier it will be for you to migrate the project elsewhere when you decide to. Please take this with a grain of salt. It's just my observation. YMMV. Kind regards, Stefan |
|
From: Tony G. <Ton...@Su...> - 2004-10-08 14:08:19
|
This question is mainly for Stefan... Shouldn't it be possible to be able to extract the project description from the xmlroff project's RSS and insert that in the generated index.html file for the xmlroff website? Most of the description that's there now could easily be moved to the overview page instead. If we do start to reuse the URL for the RSS, that would make a case for putting the RSS as a parameter in layout.xml. Regards, Tony. |
|
From: Tony G. <Ton...@Su...> - 2004-10-08 14:04:24
|
If you're like me, you probably don't pay much attention to a SourceForge project's description after the first couple of times that you see it. However, the xmlroff and PangoPDF project descriptions do change from time to time. FYI, both descriptions changed recently because xmlroff now uses both PangoPDF and Pango rather than having to use PangoPDF *instead* of Pango. xmlroff ======= xmlroff is an XSL Formatter written in C. It produces PDF or PostScript output using GNOME Print. xmlroff uses Pango (and, currently, PangoPDF) to lay out the text. xmlroff was initiated as an Open Source project by Sun Microsystems. PangoPDF ======== PangoPDF implements several of the inline properties defined by XSL that are not currently implemented by Pango. PangoPDF used to attempt to do more (hence its name), but no longer needs to thanks to recent changes in both Pango and GNOME Print. Regards, Tony. |
|
From: Tony G. <Ton...@Su...> - 2004-10-08 13:49:02
|
From http://xmlroff.org/news.html (which we all know is from RSS): xmlroff-testing is a framework for running the xmlroff XSL formatter (http://xmlroff.org/) on test stylesheets, comparing the results against reference output, and producing a summary report as well as individual reports for each test. Using the provided CGI script, you can also update each test's record from the test's report page. xmlroff-testing 0.3.0 is over 90% faster than the previous version when the test output hasn't changed since it only rasterizes pages and compares results when the PDF output has actually changed. From the NEWS file: Changes between 0.2.7 and 0.3.0: * Runs tests in less than 10% of previous time if no changes in PDF output. * Minor improvements to format of individual reports. * Now checks log files for diffs. From the ChangeLog: 2004-10-08 Tony Graham <ton...@us...> * === Released 0.3.0 === * test2sh.xsl: Stopped deleting PNG files before test runs. * makefile: Removed png-to-ref.pl, added png+ref2stereo.pl. * README: Minor change. * png+ref2stereo.pl: Don't die if diff fails. * update-results.pl: Applied recent png-to-ref.pl changes to this script. * png-to-ref.pl: Removed since unused since long-since replaced by update-results.pl. * test2sh.xsl: Added diff of PDFs and logs, removed running 'convert' on PDFs. * png-to-ref.pl: Added handling of PDF files. * png+ref2stereo.pl: Removed debugging messages. * png+ref2stereo.pl: Added running 'convert' and 'composite' only for PDFs with diffs. * dotests.pl: Commented out diffing of files. Added skipping of 'CVS' directories. * README: Updated for more happening in png+ref2stereo.pl and less in dotests.pl. 2004-10-07 Tony Graham <ton...@us...> * update-results.pl: Corrected $cTestResultsBase. * update-result.xsl: Stopped outputting DOCTYPE. * testsuccess.xsl: Minor improvements to HTML for individual reports. * testsuccess.pl: Added output of file sizes for .log files as well. * png-to-ref.pl: Added moving .log files as well. * makefile: Upped version to 0.3.0. Changed to remove .log, not .err file. * make-success-report.sh: Added png+ref2stereo.pl, removed path to 'make', changed HTML file name. * dotests.pl: Made 'composite' in .log diffs ignorable. * README, png+ref2stereo.pl, test2sh.xsl: Moved creating 'stereo' files to png+ref2stereo.pl. * configure.ac, autogen.sh: Moving to using autotools. 2004-10-06 Tony Graham <ton...@us...> * README: Added lists of steps for how to do things. Regards, Tony. |
2 messages has been excluded from this view by a project administrator.
