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: Steve C. <g3c...@cd...> - 2004-08-20 15:13:42
|
On Fri, 20 Aug 2004, Steve Cheng wrote: > I don't use RPM, but does that work? I mean, > doesn't the xmlroff building page say that you need to patch GNOME Print > to use PangoPDF? Some observations: 1. The building xmlroff page says there are directions to patch GNOME print in the xmlroff distribution, but I didn't find any. Maybe I'm dumb. 2. I sincerely hope that I can tell the patched GNOME print to build libraries with a separate name so as to not clobber the system GNOME print. 3. The PangoPDF home page have the wrong versions listed as current. 4. Just what is really different/new in PangoPDF from regular Pango? I'm using Pango myself right now for a project I'm working on, despite the lack of tutorial documentation it was a breeze to use, so I can't imagine it would be that hard to have the new functionality go in the main Pango :) -- Steve Cheng 鄭君博 docbook2X: <URL:http://docbook2x.sourceforge.net/> |
|
From: Tony G. <Ton...@Su...> - 2004-08-20 15:09:53
|
For a limited time only, you can take advantage of this fantastic offer: contribute to xmlroff or pangopdf and receive 'developer' status on the xmlroff project! Just indicate your willingness to be a xmlroff developer when you submit your patch for improved code or documentation, and as an xmlroff developer you will receive CVS access to the xmlroff code and a subscription to the exclusive xmlroff-commit mailing list. Seriously, folks, while open-source development is frequently described as a meritocracy, it's both hard to establish what the level of merit should be before you get developer status for a particular project and hard for a project that needs more developers as much as xmlroff does to be snooty about any level of merit. So forget snootiness, let's have a sale! (Okay, that wasn't serious.) Underneath the sales gimmick is recognition that xmlroff needs more developers. You may think that xmlroff is my day job and that I'm beavering away at it full-time. It isn't, and I'm not. If xmlroff is going to progress, it needs more than the limited time that I can spend on it. It needs more developers. It needs you. I just hope this message makes it through people's spam filters. Regards, Tony. |
|
From: Steve C. <g3c...@cd...> - 2004-08-20 14:50:42
|
On Mon, 16 Aug 2004, Tony Graham wrote: > I've updated http://xmlroff.org/building.html to include the names of > the RPMs you'd need to install for the libraries that have RPMs. I don't use RPM, but does that work? I mean, doesn't the xmlroff building page say that you need to patch GNOME Print to use PangoPDF? (I think that comment about patching should be emphasized in bold print, it was not obvious when one is in a hurry to build xmlroff! Happened in my case, was wondering why I couldn't build the GNOME print backend.) By the way, are there missing files in docs/ directory in the release tarball? I can't build the code documentation (on gtk-doc version 1.2). -- Steve Cheng 鄭君博 docbook2X: <URL:http://docbook2x.sourceforge.net/> |
|
From: Tony G. <Ton...@Su...> - 2004-08-20 14:26:16
|
Since Sun has recently developed a fascination for blogging, I blogged two paragraphs on xmlroff [1]. The xmlroff project's page views increased after that [2], but since they were already rising, I don't know how much to attribute to the influence of the blog entry. Either way, there hasn't been an increase in downloads, which is what we'd really want. Regards, Tony. [1] http://blog.sun.com/roller/page/menteith/20040818#xmlroff_xsl_formatter [2] http://sourceforge.net/project/stats/?group_id=73148 |
|
From: Tony G. <Ton...@Su...> - 2004-08-16 17:12:00
|
Steve Cheng <g3c...@cd...> wrote at Mon, 16 Aug 2004 11:41:45 -0400: > On Sun, 15 Aug 2004, Tony Graham wrote: ... > > What OS are you using? If you are using a recent version of Linux or > > Solaris you should have most of the libraries that you need. > > Turns out not much downloading was needed. (I am using Debian testing > distribution, just had to apt-get install libgnomeprint2.2-dev.) > I'll try building with gnome-print later. I've updated http://xmlroff.org/building.html to include the names of the RPMs you'd need to install for the libraries that have RPMs. > > The lack of support stems from working on 'Basic' conformance before > > 'Complete'. The individual properties are part of 'Basic' > > conformance, and the shorthands are part of 'Complete'. > > Oh, I see, please don't expect me to have digested all of the XSL-FO spec > just yet :) Considering that's in Appendix B, it would take you a while to find it if you're reading from front to back. I have updated http://xmlroff.org/conformance.html and http://xmlroff.org/implementation-sequence.html to add back the colours that they used to have a while ago. That should make it easier to sort out what is and isn't supported. Regards, Tony. |
|
From: Steve C. <g3c...@cd...> - 2004-08-16 15:41:47
|
On Sun, 15 Aug 2004, Tony Graham wrote: > Hello and welcome. Please subscribe to the xmlroff mailing list if > you want to continue to discuss xmlroff. I was going to, but my current email is broken, but what the heck, I'll just use this alternate account instead... > What OS are you using? If you are using a recent version of Linux or > Solaris you should have most of the libraries that you need. Turns out not much downloading was needed. (I am using Debian testing distribution, just had to apt-get install libgnomeprint2.2-dev.) I'll try building with gnome-print later. > The lack of support stems from working on 'Basic' conformance before > 'Complete'. The individual properties are part of 'Basic' > conformance, and the shorthands are part of 'Complete'. Oh, I see, please don't expect me to have digested all of the XSL-FO spec just yet :) > > docbook2X: <URL:http://docbook2x.sourceforge.net/> > > It's a small world. I'm still trying to find the time to use your TeX > markup so I can convert the XSL spec into info files so I can > distribute it with my XSL mode for Emacs. Soon I will just write that thing myself --- don't worry, I consider that for a package for making documentation to have incomplete documentation itself a serious deficiency :) -- Steve Cheng 鄭君博 docbook2X: <URL:http://docbook2x.sourceforge.net/> |
|
From: Tony G. <Ton...@Su...> - 2004-08-16 15:32:27
|
Stefan Seefeld <sse...@ar...> wrote at Mon, 16 Aug 2004 11:12:34 -0400: > hi there, Hello and welcome. Please subscribe to xml...@li... if you want to continue discussing xmlroff. > I'm trying to access the cvs repo via > > http://cvs.sourceforge.net/viewcvs.py/xmlroff > > but that generates the error: > > Bad Gateway > > The proxy server received an invalid response from an upstream server. > > I'v been getting this error for several days now. Is this a known > issue with sf.net ? Do others see the same ? I thought you may want to > know... It's a known problem affecting projects starting with any of five letters. See https://sourceforge.net/docman/display_doc.php?docid=2352&group_id=1 for the current status. Regards, Tony. |
|
From: Stefan S. <sse...@ar...> - 2004-08-16 15:16:21
|
hi there, I'm trying to access the cvs repo via http://cvs.sourceforge.net/viewcvs.py/xmlroff but that generates the error: Bad Gateway The proxy server received an invalid response from an upstream server. I'v been getting this error for several days now. Is this a known issue with sf.net ? Do others see the same ? I thought you may want to know... Regards, Stefan |
|
From: Tony G. <Ton...@Su...> - 2004-08-15 21:49:35
|
Steve Cheng <g3c...@cd...> wrote at Fri, 13 Aug 2004 20:20:31 -0400: > Hello *! Hello and welcome. Please subscribe to the xmlroff mailing list if you want to continue to discuss xmlroff. > I have downloaded the latest versions of xmlroff and > pangopdf and tried it out. No problems with the building > of the packages. That's good to hear. > This is with PDFlib; nothing wrong with gnome-print, > I just didn't have time to download all the dependencies. What OS are you using? If you are using a recent version of Linux or Solaris you should have most of the libraries that you need. > Unfortunately I have to find out the user-unfriendly way > that xmlroff doesn't seem to support CSS-style shorthand > properties, at least for "margin". If I attempt to use it, > I get a barrage of libfo critical errors and xmlroff then > either aborts or segfaults. When I separate it to the various > "margin-*" properties xmlroff works fine[*]. (This may be > the answer to a previous post by Giuseppe Greco.) The lack of support stems from working on 'Basic' conformance before 'Complete'. The individual properties are part of 'Basic' conformance, and the shorthands are part of 'Complete'. Shorthand support is yet another of those things that are in progress. The 'padding' shorthand has been done. I can give you advice about what to work on if you want to implement the rest. The user unfriendliness is unplanned. Please submit a bug report. > Whoever is in charge (I guess Tony Graham?) may want to Tony Graham in his spare time. > document this. Anyway thanks for writing xmlroff. Conformance is documented at http://xmlroff.org/conformance.html The stylesheet at examples/xml2003/fixup.xsl will munge your FO to expand shorthands and remove unsupported FOs so your FO file has a better chance of working with xmlroff. > [*] This is of course with a very simple FO document I created, > nothing from big stylesheets :) I'm still learning FO right now. > > -- > Steve Cheng > 鄭君博 > > docbook2X: <URL:http://docbook2x.sourceforge.net/> It's a small world. I'm still trying to find the time to use your TeX markup so I can convert the XSL spec into info files so I can distribute it with my XSL mode for Emacs. Regards, Tony. |
|
From: Steve C. <g3c...@cd...> - 2004-08-14 00:20:42
|
Hello *! I have downloaded the latest versions of xmlroff and pangopdf and tried it out. No problems with the building of the packages. This is with PDFlib; nothing wrong with gnome-print, I just didn't have time to download all the dependencies. Unfortunately I have to find out the user-unfriendly way that xmlroff doesn't seem to support CSS-style shorthand properties, at least for "margin". If I attempt to use it, I get a barrage of libfo critical errors and xmlroff then either aborts or segfaults. When I separate it to the various "margin-*" properties xmlroff works fine[*]. (This may be the answer to a previous post by Giuseppe Greco.) Whoever is in charge (I guess Tony Graham?) may want to document this. Anyway thanks for writing xmlroff. [*] This is of course with a very simple FO document I created, nothing from big stylesheets :) I'm still learning FO right now. -- Steve Cheng 鄭君博 docbook2X: <URL:http://docbook2x.sourceforge.net/> |
|
From: Tony G. <Ton...@Su...> - 2004-08-10 22:04:54
|
Changes between 0.2.7 and 0.2.8 * xmlroff-specific INSTALL file (Fabio Arciniegas) * Defaults to not building PDFlib backend Coupled with the change in PangoPDF 1.2.3.7 to default to not building the PDFlib backend, you can see that PDFlib on the way out. xmlroff needs graphics to work with the GNOME Print backend for it to match the current capability of the PDFlib backend. I also need to verify how well the GNOME Print backend does CJK, which used to be an advantage of the PDFlib backend (and one part of the reason why there was a PDFlib backend to begin with). I hesitate to say what my next steps will be since I missed a release last month, but I will try to work on updating PangoPDF to use Pango 1.5.1 (rather than attempt to replace it) and on that graphics capability. Thanks go to Fabio Arciniegas for providing the new installation instructions. Regards, Tony. |
|
From: Giuseppe G. <giu...@ag...> - 2004-06-05 21:19:52
|
Hi all, try to process the attached .fo file: xmlroff csharp-coding-guidelines-0.9.fo http://www.agamura.com/quxo/stylesheets/current/fo/quxo.xsl -o csharp-coding-guidelines-0.9.pdf ... you'll get lots of error messages like this: (process:5409): libfo-CRITICAL **: file fo-area.c: line 1879 (fo_area_size_request_default): assertion `FO_IS_AREA_AREA (fo_area_parent (child))' failed Any idea? j3d. -- ---------------------------------------- Giuseppe Greco ::agamura:: phone: +41 91 604 67 65 mobile: +41 76 390 60 32 email: giu...@ag... web: www.agamura.com ---------------------------------------- |
|
From: Tony G. <Ton...@Su...> - 2004-06-04 01:15:26
|
Tony Graham <Ton...@Su...> wrote at Fri, 04 Jun 2004 02:10:34 +0100 (BST): ... > The next step (other than making modules for code that's repeated in That's 'modules' as in 'separate source code files', not 'modules' as in 'separate .so files'. > every example program) is to hide the GModule interface inside a > GTypeModule so the loadable modules can be treated as objects. Regards, Tony Graham ------------------------------------------------------------------------ Web Products, Technologies and Standards Phone: +353 1 8199708 Sun Microsystems x(70)19708 East Point Business Park, Dublin 3, Ireland |
|
From: Tony G. <Ton...@Su...> - 2004-06-04 01:10:41
|
Continuing the monthly releases for a record third month in a row, the following are now available for your downloading pleasure: - xmlroff-0.2.7 - libfo-examples-0.2.7 - xmlroff-testsuite-0.2.7 - xmlroff-testing-0.2.7 (There will also be spec-dump-0.3.1 once I manage to upload it.) xmlroff-0.2.7 fixes a bug where an fo:block that was broken across a page had the entire fo:block repeated on both pages. It also adds support for resolving .length and .conditionality components of padding-* properties, although padding-before is the only one that's implemented in the area tree so far. It also installs more headers than previously, plus it incorporates the fix for segfaulting on unsupported properties that was provided by Charles Bozeman. The extra headers are installed because I had a day off this month and found the time to write some examples (now in libfo-examples-0.2.7) of programs that work with the FO and area trees: - xmlroff-text-tree demonstrates accessing the FO tree as FoNode objects. - xmlroff-text-tree2 demonstrates accessing the area tree as GObjects. - xmlroff-gmodule and gmodule-area-tree demonstrate using a loadable module that accesses the area tree as GObjects. You need to run 'make install' to install gmodule-area-tree for it to work. The programs all just show a GTK+ GtkText widget that shows the nodes in their respective trees. It's a small step towards the tree browser that I was talking about last year, and an even smaller step towards the "area-tree adjust" phase in xmlroff processing, but it is a start. And all of you are welcome to continue from this start. The next step (other than making modules for code that's repeated in every example program) is to hide the GModule interface inside a GTypeModule so the loadable modules can be treated as objects. A further extension of that idea is to make the FoDoc subtypes into loadable modules so you don't have to load a backend if you're not going to use it, but that is a low priority for me. There were only minor changes to the testsuite and test setup. However, my tests are sometimes getting different (and bad) results for the simple.fo test: I got the different result for a while, then I didn't, and now it's back again. Can someone check if they also get different results for simple.fo with xmlroff-0.2.7? My priority for June is to get past my fixation on padding properties. I expect that my priority for July will be plugging memory leaks. Regards, Tony Graham ------------------------------------------------------------------------ Web Products, Technologies and Standards Phone: +353 1 8199708 Sun Microsystems x(70)19708 East Point Business Park, Dublin 3, Ireland |
|
From: Fabio A. <fa...@po...> - 2004-06-03 13:33:25
|
Hello all, I am new to the list so I would like to introduce myself.
My name is Fabio Arciniegas, I work with UBL and am ready to
contribute to the xmlroff in any capacity (C, xslt) that advances it
as a free platform for the transformation to PDF of UBL documents.
All the best,
F.
|
|
From: Tony G. <Ton...@Su...> - 2004-05-19 09:33:11
|
"Robert J=E4ger" <Rob...@gm...> wrote at Tue, 18 May 2004 18:07:0= 4 +0200 (MEST): > I am thinking about using (integrating) XMLroff in commercial softw= are (as > far as I know there are no legal problems). AFAIK, there are no legal problems, but IANAL. PDFlib does have terms covering commercial use, but you don't have to use PDFlib. =2E.. > Before I start compiling the sources (there=B4s a lot of work to do= before > using XMLroff and it would take me a while to compile/configure all= the > libraries - my knowledges are not the best) I wanted to know if the= re are > compiled versions available on the internet. Not to my knowledge. Most of the libraries that xmlroff uses are present on computers running recent versions of GNOME. To compile xmlroff itself, the only package from the xmlroff project that you need is the 'xmlroff' package. The other packages are mostl= y useful when working with the source, although you may find the 'libfo-examples' package helpful if you want to integrate the 'libfo' library into an application. > If XMLroff is an interesting alternative I also would contact the > development team of the software, maybe they are not only intereste= d in > integrating XMLroff (and giving valuable feedback), but also in > participating in the developement. Both feedback and help would be appreciated. > I hope I didn=B4t bother the open-source community since I want to = use XMLroff > for commercial purposes.=20 Provided you comply with the terms of the license, I don't have a problem. If you contribute improvements to the xmlroff code, then I could become quite enthusiastic. Regards, Tony Graham ---------------------------------------------------------------------= --- Web Products, Technologies and Standards Phone: +353 1 8199= 708 Sun Microsystems x(70)19= 708 East Point Business Park, Dublin 3, Ireland |
|
From: <Rob...@gm...> - 2004-05-18 16:07:12
|
Hi! I am thinking about using (integrating) XMLroff in commercial software (as far as I know there are no legal problems). Since the software (business process modelling toolkit based on C++) that I am customizing exports its information to XML I could use XMLroff to transfer the data via XSL to PDF. Honestly I am not an expert concering C, but I am used to work with JAVA, FOP, XSL, ... Before I start compiling the sources (there´s a lot of work to do before using XMLroff and it would take me a while to compile/configure all the libraries - my knowledges are not the best) I wanted to know if there are compiled versions available on the internet. If XMLroff is an interesting alternative I also would contact the development team of the software, maybe they are not only interested in integrating XMLroff (and giving valuable feedback), but also in participating in the developement. I hope I didn´t bother the open-source community since I want to use XMLroff for commercial purposes. Greetings from Vienna, Robert. -- NEU : GMX Internet.FreeDSL Ab sofort DSL-Tarif ohne Grundgebühr: http://www.gmx.net/dsl |
|
From: Tony G. <Ton...@Su...> - 2004-05-17 11:16:27
|
Charles Bozeman <cbo...@hi...> wrote at Sun, 16 May 2004 20:23:04 -0500: > This patch is to keep from segfaulting when it encounters properties > that aren't handled. Thanks. Committed. I added a warning message about unsupported properties. Time will tell whether that becomes too annoying. Regards, Tony Graham ------------------------------------------------------------------------ Web Products, Technologies and Standards Phone: +353 1 8199708 Sun Microsystems x(70)19708 East Point Business Park, Dublin 3, Ireland |
|
From: Charles B. <cbo...@hi...> - 2004-05-17 01:22:46
|
This patch is to keep from segfaulting when it encounters properties that aren't handled. Charlie Bozeman |
|
From: Tony G. <Ton...@Su...> - 2004-05-04 11:18:44
|
Someone yesterday posted on the libxslt list that xmlroff was dead because the xmlroff website at http://www.xmlroff.org/ hadn't been updated since last year. I updated the website. Is there anyone who is even vaguely familiar with the DocBook website XML who has the spare time to keep the xmlroff website up to date when a new release comes out, etc.? Regards, Tony Graham ------------------------------------------------------------------------ Web Products, Technologies and Standards Phone: +353 1 8199708 Sun Microsystems x(70)19708 East Point Business Park, Dublin 3, Ireland |
|
From: Tony G. <Ton...@Su...> - 2004-05-04 11:06:45
|
New versions are now available from the Sourceforge download site accessible from http://sourceforge.net/projects/xmlroff/. Even the website at http://www.xmlroff.org/ has been updated. It's all part of a new "On or about the first of the month" release schedule. Since it's hard to find the spare time to make significant progress on xmlroff within a month, I've decided to make new releases on or about the first of the month no matter how insignificant the changes. And, of course, any contributed changes would also make it into the next monthly release. Regards, Tony Graham ------------------------------------------------------------------------ Web Products, Technologies and Standards Phone: +353 1 8199708 Sun Microsystems x(70)19708 East Point Business Park, Dublin 3, Ireland |
|
From: Tony G. <Ton...@Su...> - 2004-04-02 22:11:37
|
This is another code drop just before I get on a plane. I won't be able to work on xmlroff again until April 16. This release adds support for the 'padding' shorthand property. More importantly from the point of view of working with the code, all properties are now created (or creatable) using fo_property_new_from_expr(). Changes between 0.2.4 and 0.2.5: * Added 'padding' shorthand property * Fixed bug in 'gp' backend colour calculations * All properties now created using fo_property_new_from_expression() * Most property-specific enumerations moved to fo-enum.[ch] * 84% documentation comment coverage Regards, Tony Graham ------------------------------------------------------------------------ Web Products, Technologies and Standards Phone: +353 1 8199708 Sun Microsystems x(70)19708 East Point Business Park, Dublin 3, Ireland |
|
From: Tony G. <Ton...@Su...> - 2004-03-24 13:35:02
|
Tony Graham <Ton...@Su...> wrote at Tue, 23 Mar 2004 14:13:38 +0000 (GMT): > There is a problem with the border-*-width properties, but you should > be able to compile xmlroff successfully. Fixed. Please do a 'cvs update'. Regards, Tony Graham ------------------------------------------------------------------------ Web Products, Technologies and Standards Phone: +353 1 8199708 Sun Microsystems x(70)19708 East Point Business Park, Dublin 3, Ireland |
|
From: Tony G. <Ton...@Su...> - 2004-03-24 12:56:40
|
Matthew Mackey <mm...@ma...> wrote at Tue, 23 Mar 2004 11:18:42 -0800: > I'm new to the list, so I'm doing a little introduction. My name is > Matthew Mackey - everyone calls me Matt - and I'm here to lend what > help I can to the project. My skill set is mildly eclectic, having a > good C/C++ and Java foundation with a variety of database and > multimedia stuff thrown in. Welcome (again). > Tony already sent me some ideas about things that could use attention. > I figure since I like to really get my head around something before I > dive in, time I spend getting to know the project would be good for > enhancing the documentation, something that Tony mentioned needs doing. > > So one of my first questions would be about what format(s) should the > documentation be in. I believe (correct me if I'm wrong) I saw javadoc > style comments/markup in some of the files in my initial glance. So > that would be one area to continue expanding. But I'm assuming that Get to know gtk-doc. Assuming you have gtk-doc on your system, adding --enable-gtk-doc to the configure command line will enable building the documentation when you run 'make'. In addition to the Javadoc-like comments that you can put in the source code, there's a .sgml file for each source code module in docs/tmpl to which you can add additional stuff (using DocBook markup) that will end up in the generated HTML documentation. > there's a desire for external documentation as well. Perhaps a primer > of some sort that would cover internal structure for xmlroff developers > and/or proper usage for those trying to use it in a solution? Should it > be html? Raw text? (Or even XML and XSL sheets so we can make PDFs of > it with xmlroff! Okay, I'm getting ahead of myself...) > > I'm open to ideas... xmlroff.fo in the source distribution is a simple man page for the xmlroff executable in FO markup that serves the dual purposes of man page and being something that you can use to check that xmlroff works. The short-term place for documentation until it's cooked enough to bake into the gtk-doc documentation is meant to be the xmlroff Wiki at http://www.xmlroff.org/phpwiki/. If what you want to write doesn't slot in to the structure of the current Wiki pages, then just add another top-level Wiki page. Regards, Tony Graham ------------------------------------------------------------------------ Web Products, Technologies and Standards Phone: +353 1 8199708 Sun Microsystems x(70)19708 East Point Business Park, Dublin 3, Ireland |
|
From: Matthew M. <mm...@ma...> - 2004-03-23 19:17:22
|
I'm new to the list, so I'm doing a little introduction. My name is Matthew Mackey - everyone calls me Matt - and I'm here to lend what help I can to the project. My skill set is mildly eclectic, having a good C/C++ and Java foundation with a variety of database and multimedia stuff thrown in. Tony already sent me some ideas about things that could use attention. I figure since I like to really get my head around something before I dive in, time I spend getting to know the project would be good for enhancing the documentation, something that Tony mentioned needs doing. So one of my first questions would be about what format(s) should the documentation be in. I believe (correct me if I'm wrong) I saw javadoc style comments/markup in some of the files in my initial glance. So that would be one area to continue expanding. But I'm assuming that there's a desire for external documentation as well. Perhaps a primer of some sort that would cover internal structure for xmlroff developers and/or proper usage for those trying to use it in a solution? Should it be html? Raw text? (Or even XML and XSL sheets so we can make PDFs of it with xmlroff! Okay, I'm getting ahead of myself...) I'm open to ideas... Matt |
2 messages has been excluded from this view by a project administrator.
