DO NOT REPLY [Bug 33126] - [PATCH] updated documentation in /src/documentation/content/xdocs/DnI/areatree.xml
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG· RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT http://issues.apache.org/bugzilla/show_bug.cgi?id=33126. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND· INSERTED IN THE BUG DATABASE. http://issues.apache.org/bugzilla/show_bug.cgi?id=33126 [EMAIL PROTECTED] changed: What|Removed |Added Status|NEW |RESOLVED Resolution||FIXED --- Additional Comments From [EMAIL PROTECTED] 2005-01-30 20:58 --- Applied. Edited the last paragraph to point to LayoutManagerMaker. Thanks for your contribution. Simon Pepping -- Configure bugmail: http://issues.apache.org/bugzilla/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug, or are watching the assignee.
DO NOT REPLY [Bug 33126] New: - [PATCH] updated documentation in /src/documentation/content/xdocs/DnI/areatree.xml
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG· RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT http://issues.apache.org/bugzilla/show_bug.cgi?id=33126. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND· INSERTED IN THE BUG DATABASE. http://issues.apache.org/bugzilla/show_bug.cgi?id=33126 Summary: [PATCH] updated documentation in /src/documentation/content/xdocs/DnI/areatree.xml Product: Fop Version: 1.0dev Platform: PC OS/Version: Linux Status: NEW Severity: normal Priority: P2 Component: documentation AssignedTo: fop-dev@xml.apache.org ReportedBy: [EMAIL PROTECTED] CC: [EMAIL PROTECTED] bonjour fop-dev i did some update of this documentation. i'm not sure about the last paragraph, please correct it. renaud -- Configure bugmail: http://issues.apache.org/bugzilla/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug, or are watching the assignee.
DO NOT REPLY [Bug 33126] - [PATCH] updated documentation in /src/documentation/content/xdocs/DnI/areatree.xml
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG· RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT http://issues.apache.org/bugzilla/show_bug.cgi?id=33126. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND· INSERTED IN THE BUG DATABASE. http://issues.apache.org/bugzilla/show_bug.cgi?id=33126 --- Additional Comments From [EMAIL PROTECTED] 2005-01-16 23:40 --- Created an attachment (id=14028) -- (http://issues.apache.org/bugzilla/attachment.cgi?id=14028action=view) patch for /xdocs/DnI/areatree.xml -- Configure bugmail: http://issues.apache.org/bugzilla/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug, or are watching the assignee.
cvs commit: xml-fop/src/documentation/content/xdocs resources.xml
clay2004/11/29 06:52:11 Modified:src/documentation/content/xdocs resources.xml Log: fixed swapped links for Defoe FOray Revision ChangesPath 1.44 +4 -4 xml-fop/src/documentation/content/xdocs/resources.xml Index: resources.xml === RCS file: /home/cvs/xml-fop/src/documentation/content/xdocs/resources.xml,v retrieving revision 1.43 retrieving revision 1.44 diff -u -r1.43 -r1.44 --- resources.xml 24 Nov 2004 15:35:56 - 1.43 +++ resources.xml 29 Nov 2004 14:52:11 - 1.44 @@ -218,8 +218,8 @@ section id=products-other titleOther products/title ul - li[software] jump href=http://defoe.sourceforge.net/;FOray/jump a renderer for converting XML files to PDF via XSL Formatting Object elements/li - li[software] jump href=http://foray.sourceforge.net/;Defoe/jump a renderer for XML files containing Formatting Object elements (aka FOP Alt.Design)/li + li[software] jump href=http://foray.sourceforge.net/;FOray/jump a renderer for converting XML files to PDF via XSL Formatting Object elements/li + li[software] jump href=http://defoe.sourceforge.net/;Defoe/jump a renderer for XML files containing Formatting Object elements (aka FOP Alt.Design)/li li[commercial software developer] jump href=http://antennahouse.com/product.htm;Antenna House/jump - XSL Formatter, WordMLToFo, XML Editor.../li li[commercial software developer] jump href=http://www.renderx.net/;RenderX/jump XEP, EnMasse, Docbench.../li - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: cvs commit: xml-fop/src/documentation/content/xdocs/dev book.xml
On Mon, Nov 08, 2004 at 01:43:51PM -0800, Clay Leeds wrote: I suspect this could be a problem for the Forrest site-generation process[1]: Specifying menus with book.xml Historically, menus in Forrest have been generated from a book.xml file, one per directory. This mechanism is still available, and if a book.xml is found, it will be used in preference to the menu generated by the site.xml file. The book.xml files can use site: URIs to ease the maintenance burden that led to obsolescence of book.xml files. In general, however, we recommend that users avoid book.xml files. Is it possible for you to rename that file so it doesn't conflict? (I'm hoping it is trivial for you to change that file name. Perhaps fop-=dni-book.xml or something). If not, I'll see if I can come up with some other solution, although my guess is that any workaround will preclude it from having the same look feel as the rest of the FOP web site. A shame; I thought book.xml was the right name for this file. Renamed to DnI.xml. Simon -- Simon Pepping home page: http://www.leverkruid.nl
Re: cvs commit: xml-fop/src/documentation/content/xdocs/dev book.xml
On Nov 9, 2004, at 11:58 AM, Simon Pepping wrote: On Mon, Nov 08, 2004 at 01:43:51PM -0800, Clay Leeds wrote: I suspect this could be a problem for the Forrest site-generation process[1]: Specifying menus with book.xml Historically, menus in Forrest have been generated from a book.xml file, one per directory. This mechanism is still available, and if a book.xml is found, it will be used in preference to the menu generated by the site.xml file. The book.xml files can use site: URIs to ease the maintenance burden that led to obsolescence of book.xml files. In general, however, we recommend that users avoid book.xml files. Is it possible for you to rename that file so it doesn't conflict? (I'm hoping it is trivial for you to change that file name. Perhaps fop-=dni-book.xml or something). If not, I'll see if I can come up with some other solution, although my guess is that any workaround will preclude it from having the same look feel as the rest of the FOP web site. A shame; I thought book.xml was the right name for this file. Renamed to DnI.xml. Simon Perhaps it is the correct name for the file. IMHO, perhaps forrest should pre-pend for_ in front of filenames (e.g., for_book.xml, for_site.xml, for_tabs.xml, etc.) like this to prevent this types of problems. Forrest already was having problems where they were using 'site.xml' and outputting site.html and 'site.pdf' (they changed the latter two to wholesite.html and wholesite.pdf...). Anyway, thanks for making the change. It means that the DnI stuff can be skinned (as I mentioned previously, the book.xml in there made forrest think that it had it's own 'book.xml' file for that directory, so it wouldn't use site.xml file (which defines the site navigation structure). Web Maestro Clay -- Clay Leeds - [EMAIL PROTECTED] Webmaster/Developer - Medata, Inc. - http://www.medata.com/ PGP Public Key: https://mail.medata.com/pgp/cleeds.asc
Re: cvs commit: xml-fop/src/documentation/content/xdocs/dev book.xml
Clay, On Sun, Nov 07, 2004 at 08:48:23PM -0800, Clay Leeds wrote: Simon, Does the book.xml file in your DnI section serve any specific purpose (DnI-related), or is it to follow the common coding/forrest convention? I ask, because the use of book.xml is deprecated in Forrest-0.6 in favor of the site-wide src/documentation/content/xdocs/site.xml file. book.xml is the top-level file that calls in all the chapters. It is indispensible, it is _the_ book, so to speak. I compared it with the book files you have removed. I see that it has a different purpose. The other book files seem to define menus. Regards, Simon On Nov 7, 2004, at 8:26 PM, [EMAIL PROTECTED] wrote: clay2004/11/07 20:26:29 Removed: src/documentation/content/xdocs book.xml src/documentation/content/xdocs/design book.xml src/documentation/content/xdocs/design/alt.design book.xml src/documentation/content/xdocs/design/alt.design/properties book.xml src/documentation/content/xdocs/dev book.xml Log: removed all book.xml files (except DnI) Web Maestro Clay -- Clay Leeds - [EMAIL PROTECTED] Webmaster/Developer - Medata, Inc. - http://www.medata.com/ PGP Public Key: https://mail.medata.com/pgp/cleeds.asc -- Simon Pepping home page: http://www.leverkruid.nl
Re: cvs commit: xml-fop/src/documentation/content/xdocs/dev book.xml
On Nov 8, 2004, at 12:48 PM, Simon Pepping wrote: Clay, On Sun, Nov 07, 2004 at 08:48:23PM -0800, Clay Leeds wrote: Simon, Does the book.xml file in your DnI section serve any specific purpose (DnI-related), or is it to follow the common coding/forrest convention? I ask, because the use of book.xml is deprecated in Forrest-0.6 in favor of the site-wide src/documentation/content/xdocs/site.xml file. book.xml is the top-level file that calls in all the chapters. It is indispensible, it is _the_ book, so to speak. I compared it with the book files you have removed. I see that it has a different purpose. The other book files seem to define menus. Regards, Simon I suspect this could be a problem for the Forrest site-generation process[1]: Specifying menus with book.xml Historically, menus in Forrest have been generated from a book.xml file, one per directory. This mechanism is still available, and if a book.xml is found, it will be used in preference to the menu generated by the site.xml file. The book.xml files can use site: URIs to ease the maintenance burden that led to obsolescence of book.xml files. In general, however, we recommend that users avoid book.xml files. Is it possible for you to rename that file so it doesn't conflict? (I'm hoping it is trivial for you to change that file name. Perhaps fop-=dni-book.xml or something). If not, I'll see if I can come up with some other solution, although my guess is that any workaround will preclude it from having the same look feel as the rest of the FOP web site. [1] http://forrest.apache.org/docs/linking.html#book-menu-selection Web Maestro Clay -- Clay Leeds - [EMAIL PROTECTED] Webmaster/Developer - Medata, Inc. - http://www.medata.com/ PGP Public Key: https://mail.medata.com/pgp/cleeds.asc
Re: cvs commit: xml-fop/src/documentation/content/xdocs/dev book.xml
Simon, Does the book.xml file in your DnI section serve any specific purpose (DnI-related), or is it to follow the common coding/forrest convention? I ask, because the use of book.xml is deprecated in Forrest-0.6 in favor of the site-wide src/documentation/content/xdocs/site.xml file. On Nov 7, 2004, at 8:26 PM, [EMAIL PROTECTED] wrote: clay2004/11/07 20:26:29 Removed: src/documentation/content/xdocs book.xml src/documentation/content/xdocs/design book.xml src/documentation/content/xdocs/design/alt.design book.xml src/documentation/content/xdocs/design/alt.design/properties book.xml src/documentation/content/xdocs/dev book.xml Log: removed all book.xml files (except DnI) Web Maestro Clay -- Clay Leeds - [EMAIL PROTECTED] Webmaster/Developer - Medata, Inc. - http://www.medata.com/ PGP Public Key: https://mail.medata.com/pgp/cleeds.asc
Re: cvs commit: xml-fop/src/documentation/resources/images group-logo.gif logo.jpg
On Nov 6, 2004, at 8:57 AM, [EMAIL PROTECTED] wrote: clay2004/11/06 08:57:40 Modified:.forrest.properties src/documentation sitemap.xmap skinconf.xml src/documentation/content/xdocs compliance.xml graphics.xml resources.xml site.xml src/documentation/resources/images group-logo.gif logo.jpg Log: Updates to achieve a /forrest/ BUILD SUCCESSSFUL for the xml-fop web site. I'm in the process of ironing out the 'final' glitches in the /forrest/ building of xml-fop. In spite of the comment above, we're actually not quite at the BUILD SUCCESSFUL I've been working towards for so many months. Among other issues, I've still got to fix some problems with the transformation of FO SVG files for the Examples Page dev/svg.html... In addition, I'm still working towards getting the Compliance page fixed. I've got it outputting some content, but we're still missing citations and some other stuff. But we're close! Web Maestro Clay -- Clay Leeds - [EMAIL PROTECTED] Webmaster/Developer - Medata, Inc. - http://www.medata.com/ PGP Public Key: https://mail.medata.com/pgp/cleeds.asc
Re: rarr; in DnI documentation
Clay, Sorry for not answering earlier. I have a couple of other things to do these weeks. On Thu, Oct 21, 2004 at 02:25:12PM -0700, Clay Leeds wrote: I'd also like to resolve the error in Forrest if possible, so the rest of this POST deals with that. I suspect the problem is related to the fact that properties.xml references a dtd like this: !-- !DOCTYPE chapter PUBLIC -//OASIS//DTD DocBook XML V4.2//EN docbookx.dtd -- A couple of things I note here: 1. It's commented out It is commented out so it should not have any influence. It is there so that I can uncomment and use it during editing. 2. this is a relative/local link, but the 'docbookx.dtd' is not local (I also tried 'http://www.oasis-open.org/docbook/xml/4.2/docbookx.dtd' and 'http://www.oasis-open.org/docbook/xml/4.2/' and as expected neither works.) Because it is only used during editing I have not bothered to make it absolute. The file book.xml has an absolute path for the DTD, and that is the one that matters. 3. fwiw, iso-num.ent is at http://www.oasis-open.org/docbook/xml/4.2/ent/iso-num.ent The dtd that one uses, should have correct relative links to the entities files. In that way they are loaded without anyone having to bother about them. I'm not very 'up' on DocBook, so this may be how it's 'supposed' to work. Nevertheless, rarr; is the only thing in 'properties.xml' that doesn't validate during the /forrest/ run (unless I replace rarr; with #8594; or #x2192;). Once the document and the stylesheets have been written, nothing is very docbook specific. Only correct absolute paths or good catalogs matter at that stage. Nevertheless, docbook is a very complex DTD that uses the whole DTD machinery. I am glad it works. Regards, Simon -- Simon Pepping home page: http://www.leverkruid.nl
Re: rarr; in DnI documentation
Clay, I am a bit surprised. The docbook dtd clearly defines the entity rarr; in iso-num.ent: !ENTITY rarr #x2192; !-- RIGHTWARDS DOUBLE ARROW -- Why does not the forrest build see this? Does it not read the DTD? I do not like character entities in decimal numbers. I can never figure out what they refer to. IMO character codes should be given in hexadecimal notation; all Unicode documentation uses this. Then it becomes #x2192; as shown above. Regards, Simon On Tue, Oct 19, 2004 at 11:57:00AM -0700, Clay Leeds wrote: Simon, One of the characters in your documentation is causing problems in the Forrest build process. I'd like to swap the rarr; (amp;rarr;) characters with either 'gt;' (amp;gt;) or '--gt;' (--amp;gt;)? Or... after some looking I found the rarr; numeric entity: #8594; [amp;#8594;]. I found the rarr; in a bunch of places but the numeric entity took a while... xml-fop/src/documentation/content/xdocs/DnI/properties.xml Lines 2243-2248: listitem paraliteralpcBase.getDimension/literal; dimension: type of integer, int rarr; 0, length rarr; 1; used by literalPercentBase/literal and literalNumericProperty/literal; literalLengthBase/literal has a dimension of 1/para /listitem Do you have any objections to this change? listitem paraliteralpcBase.getDimension/literal; dimension: type of integer, int #8594; 0, length #8594; 1; used by literalPercentBase/literal and literalNumericProperty/literal; literalLengthBase/literal has a dimension of 1/para /listitem Thanks! Web Maestro Clay -- Clay Leeds - [EMAIL PROTECTED] Webmaster/Developer - Medata, Inc. - http://www.medata.com/ PGP Public Key: https://mail.medata.com/pgp/cleeds.asc -- Simon Pepping home page: http://www.leverkruid.nl
Re: rarr; in DnI documentation
On Oct 20, 2004, at 11:32 AM, Simon Pepping wrote: Clay, I am a bit surprised. The docbook dtd clearly defines the entity rarr; in iso-num.ent: !ENTITY rarr #x2192; !-- RIGHTWARDS DOUBLE ARROW -- Why does not the forrest build see this? Does it not read the DTD? I do not like character entities in decimal numbers. I can never figure out what they refer to. IMO character codes should be given in hexadecimal notation; all Unicode documentation uses this. Then it becomes #x2192; as shown above. Regards, Simon Changing rarr; to #x2192; is an acceptable solution. The xml-fop /forrest/ build does not error out when it tries to validate 'properties.xml'. I made the change and checked it in. I'd also like to resolve the error in Forrest if possible, so the rest of this POST deals with that. I suspect the problem is related to the fact that properties.xml references a dtd like this: !-- !DOCTYPE chapter PUBLIC -//OASIS//DTD DocBook XML V4.2//EN docbookx.dtd -- A couple of things I note here: 1. It's commented out 2. this is a relative/local link, but the 'docbookx.dtd' is not local (I also tried 'http://www.oasis-open.org/docbook/xml/4.2/docbookx.dtd' and 'http://www.oasis-open.org/docbook/xml/4.2/' and as expected neither works.) 3. fwiw, iso-num.ent is at http://www.oasis-open.org/docbook/xml/4.2/ent/iso-num.ent I'm not very 'up' on DocBook, so this may be how it's 'supposed' to work. Nevertheless, rarr; is the only thing in 'properties.xml' that doesn't validate during the /forrest/ run (unless I replace rarr; with #8594; or #x2192;). Web Maestro Clay -- Clay Leeds - [EMAIL PROTECTED] Webmaster/Developer - Medata, Inc. - http://www.medata.com/ PGP Public Key: https://mail.medata.com/pgp/cleeds.asc
rarr; in DnI documentation
Simon, One of the characters in your documentation is causing problems in the Forrest build process. I'd like to swap the rarr; (amp;rarr;) characters with either 'gt;' (amp;gt;) or '--gt;' (--amp;gt;)? Or... after some looking I found the rarr; numeric entity: #8594; [amp;#8594;]. I found the rarr; in a bunch of places but the numeric entity took a while... xml-fop/src/documentation/content/xdocs/DnI/properties.xml Lines 2243-2248: listitem paraliteralpcBase.getDimension/literal; dimension: type of integer, int rarr; 0, length rarr; 1; used by literalPercentBase/literal and literalNumericProperty/literal; literalLengthBase/literal has a dimension of 1/para /listitem Do you have any objections to this change? listitem paraliteralpcBase.getDimension/literal; dimension: type of integer, int #8594; 0, length #8594; 1; used by literalPercentBase/literal and literalNumericProperty/literal; literalLengthBase/literal has a dimension of 1/para /listitem Thanks! Web Maestro Clay -- Clay Leeds - [EMAIL PROTECTED] Webmaster/Developer - Medata, Inc. - http://www.medata.com/ PGP Public Key: https://mail.medata.com/pgp/cleeds.asc
Re: rarr; in DnI documentation
Clay Leeds wrote: I found the rarr; in a bunch of places but the numeric entity took a while... Bookmark this: http://www.w3.org/TR/html4/sgml/entities.html Ctrl-F and type in the entity name, the decimal or the hex numbers. For completeness bookmark http://www.unicode.org/charts/charindex.html J.Pietschmann
Re: rarr; in DnI documentation
On Oct 19, 2004, at 12:50 PM, J.Pietschmann wrote: Bookmark this: http://www.w3.org/TR/html4/sgml/entities.html Ctrl-F and type in the entity name, the decimal or the hex numbers. For completeness bookmark http://www.unicode.org/charts/charindex.html J.Pietschmann Thanks! Might as well get it from the horse's mouth! Of course I've always found specs to be such a pain to read. I guess that's where this comes in handy: AListApart.com's How to Read W3C Specs http://www.alistapart.com/articles/readspec/ After I am able to run forrest and get a BUILD SUCCESSFUL, I'll be adding those links to the FOP Resources page... :-p Web Maestro Clay -- Clay Leeds - [EMAIL PROTECTED] Webmaster/Developer - Medata, Inc. - http://www.medata.com/ PGP Public Key: https://mail.medata.com/pgp/cleeds.asc
FOP Web Site Update (was Re: cvs commit: xml-fop/src/documentation/content/xdocs news.xml team.xml)
Thanks Glen! I was planning to update the site to indicate Luca's 'promotion'. Believe it or not, I'm actually about to update the xml-fop web site. I've been waiting for Forrest 0.6 to be released so that the changes won't get wiped away when we switch over to it. Unfortunately the process will involve replacing all files in the xdocs/ directory. I will need do a DIFF on the files in xdocs/ that changed after August 2 (August 2 is the date I'm using to generate the 0.6 site--it's a long story of why I pick that date, and the thread can be found in the forrest-dev/user logs). My intention is to bring xml-fop up-to-date next week (I'll be out of town this weekend). Speaking of which, does anyone know when xml.apache.org will be updated to forrest-0.6? I guess that's a question for either [EMAIL PROTECTED] or [EMAIL PROTECTED] If anyone has any questions (or the command to diff all files in the xdocs/ path after August 2), that would be great! Web Maestro Clay On Oct 16, 2004, at 11:44 AM, [EMAIL PROTECTED] wrote: gmazza 2004/10/16 11:44:32 Modified:src/documentation/content/xdocs news.xml team.xml Log: Moved Luca to the committer's list, updated news section. Revision ChangesPath 1.21 +6 -2 xml-fop/src/documentation/content/xdocs/news.xml Index: news.xml === RCS file: /home/cvs/xml-fop/src/documentation/content/xdocs/news.xml,v retrieving revision 1.20 retrieving revision 1.21 diff -u -r1.20 -r1.21 --- news.xml 24 Apr 2004 19:37:22 - 1.20 +++ news.xml 16 Oct 2004 18:44:32 - 1.21 @@ -25,6 +25,10 @@ /header body section + title8 October 2004 - New Committer/title + pWelcome Luca Furini!/p +/section +section title24 April 2004 - New Committer/title pWelcome Simon Pepping!/p /section 1.34 +5 -5 xml-fop/src/documentation/content/xdocs/team.xml Index: team.xml === RCS file: /home/cvs/xml-fop/src/documentation/content/xdocs/team.xml,v retrieving revision 1.33 retrieving revision 1.34 diff -u -r1.33 -r1.34 --- team.xml 11 Jun 2004 21:04:06 - 1.33 +++ team.xml 16 Oct 2004 18:44:32 - 1.34 @@ -32,6 +32,9 @@ li id=cblink RENAME_FILE_TO_USE_href=mailto:[EMAIL PROTECTED]Chris Bowditch/link (CB) is a Java/VB Programmer from England./li li id=adlink RENAME_FILE_TO_USE_href=mailto:[EMAIL PROTECTED]Andreas Delmelle/link (AD)/li +!-- Luca prefers the mail address with AT, to stop spam, etc. -- +lilink RENAME_FILE_TO_USE_href=mailto:lfurini AT cs.unibo.itLuca Furini/link + is a student of Computer Studies at the University of Bologna (Italy)/li li id=cglink RENAME_FILE_TO_USE_href=mailto:[EMAIL PROTECTED]Christian Geisert/link (CG)/li li id=phlink RENAME_FILE_TO_USE_href=mailto:[EMAIL PROTECTED]Peter Herweg/link (PH) is helping to integrate the jfor project's RTF support into the upcoming FOP 1.0 version. @@ -66,9 +69,6 @@ Newfoundland. While developing a taste for good seafood, he still isn't ready for seal flipper (even if it's fresh). He is currently assisting the FOP project on memory and performance issues./li -!-- Luca prefers the mail address with AT, to stop spam, etc. -- - lilink RENAME_FILE_TO_USE_href=mailto:lfurini AT cs.unibo.itLuca Furini/link -is a student of Computer Studies at the University of Bologna (Italy)/li /ul /RENAME_FILE_TO_USE_section RENAME_FILE_TO_USE_section id=founder - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] Web Maestro Clay -- Clay Leeds - [EMAIL PROTECTED] Webmaster/Developer - Medata, Inc. - http://www.medata.com/ PGP Public Key: https://mail.medata.com/pgp/cleeds.asc
Re: Committing documentation
On Wed, Jul 28, 2004 at 01:24:22PM -0700, Clay Leeds wrote: On Jul 28, 2004, at 11:51 AM, Simon Pepping wrote: On Sun, Jul 25, 2004 at 12:51:56PM -0700, Clay Leeds wrote: As I understand it, you're primarily doing documentation that is more developer and/or embedded oriented, which is one of the reasons why I would want to have a new 'Documentation' tab. Indeed, it is. Does this mandate a specific directory to commit the files into? Or shall I create a directory in src/documentation/content/xdocs? Or in src/documentation/content/? Regards, Simon Good question. Actually, I was 'putting it out there(tm)' as to whether or not other committers thought that was a good idea. Therefore, I'm not sure where it should go *yet*. As for how it goes in, double-check the FAQ docbook section[1] (IIRC you did the docs in docbook?). If you need more help, let me know. Web Maestro Clay [1] http://forrest.apache.org/faq.html#docbook Thanks for the pointer. I have done what it requires, writing the documentation in Docbook XML 4.2. When the time is there, the map:match element should be added to the site map, and the docbook stylesheets should be reachable. I will commit the work to src/documentation/content/xdocs/DnI. That stands for 'Design and Implementation', into which I have changed the title. Regards, Simon -- Simon Pepping home page: http://www.leverkruid.nl
Re: Committing documentation
On Sun, Jul 25, 2004 at 12:51:56PM -0700, Clay Leeds wrote: As I understand it, you're primarily doing documentation that is more developer and/or embedded oriented, which is one of the reasons why I would want to have a new 'Documentation' tab. Indeed, it is. Does this mandate a specific directory to commit the files into? Or shall I create a directory in src/documentation/content/xdocs? Or in src/documentation/content/? Regards, Simon -- Simon Pepping home page: http://www.leverkruid.nl
Re: Committing documentation
On Jul 28, 2004, at 11:51 AM, Simon Pepping wrote: On Sun, Jul 25, 2004 at 12:51:56PM -0700, Clay Leeds wrote: As I understand it, you're primarily doing documentation that is more developer and/or embedded oriented, which is one of the reasons why I would want to have a new 'Documentation' tab. Indeed, it is. Does this mandate a specific directory to commit the files into? Or shall I create a directory in src/documentation/content/xdocs? Or in src/documentation/content/? Regards, Simon Good question. Actually, I was 'putting it out there(tm)' as to whether or not other committers thought that was a good idea. Therefore, I'm not sure where it should go *yet*. As for how it goes in, double-check the FAQ docbook section[1] (IIRC you did the docs in docbook?). If you need more help, let me know. Web Maestro Clay [1] http://forrest.apache.org/faq.html#docbook
Re: Javasrc, JXR and documentation
Clay, Thanks for keeping this on the boil. The Forrestdoc link you gave me shows the Javasrc at a much greater level of integration than was visible when I last looked. My problem originally was that only line-number links were provided. In the current forrestdoc version, everything is linked in to comprehensive cross-reference web. Nice. The appearance of the the source text is not optimal, but there is scope in Javasrc to correct this, I believe. There are probably two levels of tuning. Firstly, syntax highlighting, and secondly. link presentation. The syntax highlighting variations (if any) would be Javasrc configuration options. The link presentation would be available through the CSS used to present the document. Most things of interest, and, AFAICT, all links are htmlized with a relevant class attribute, so it is feasible to select the link colour or colours for various classes to allow appropriate highlighting. Keywords, although emphasised in the text, are not given a class attribute, which is unfortunate, but may be tunable. The source html I used was generated by htmlize.el, an emacs and XEmacs module by Hrvoje Niksic. In order to use it, you will need to have an emacs or xemacs binary available to the build process. Forrestdoc looks the far better option. Peter Clay Leeds wrote: Peter, On Jun 29, 2004, at 7:04 PM, Peter B. West wrote: Clay, FYI, Java 1.4 javadoc tool supports a -linksource argument, which generates html of source files. However, the process seems to have pretty much the same restrictions as the Maven JXR - the only references are to line numbers, which is just about the most useless form imaginable. It might be of interest to someone at a later stage to look at extending the standard doclet to utilise Javasrc to perform that generation. Peter I've been hoping to get movement on the forrest front, then include the java doc stuff once I have xml-fop up running. As that's not moving along very fast, perhaps I can get a bit more information on what we need to do with the java doc front. Here's something I 'dug' up[1]. Looks like it's along the lines of what we're looking for, although I like what you've got on this page[2] better. Your version seems more accessible. However, you indicate: The problem is that there was no clean way to automatically generate the htmlized source. It's that supplementary facility that I'm looking for. What is the procedure used to generate the htmlized source? Could it be automated using gump or ant or something? BTW, what's the tool called you use to generate this? Web Maestro Clay [1] http://cvs.apache.org/~nicolaken/whiteboard/forrestdoc/ [2] http://xml.apache.org/fop/design/alt.design/properties/classes- overview.html -- Peter B. West http://cv.pbw.id.au/
(Copyright question) Re: Committing documentation
I believe the key word below is transferable, i.e., before checking any work in, it still needs to be copyright The Apache Software Foundation at the time of it being cvs committed. Dirk-Willem, might you know more about this? (Original comments in [1] below.) But I noticed Simon already updated it to The Authors--all it needs to be next (I think) is ASF and we're done: http://www.leverkruid.nl/FOP/documentation-html/index.html We already have a dubious copyright notice in one of our source files [2, lines 36-37], dubious because the file has changed so many times by other people over the years that it is unknown whether the copyright holder actually still owns any of the code. I'm inclined against adding non-ASF copyrighted work to our repository, because once you have it there, it is difficult to get rid of, no matter how out-of-date that copyright gets. If anyone is not ready to transfer the copyright to their work, then it shouldn't be in our repository. Glen [1] http://marc.theaimsgroup.com/?l=fop-devm=109079517313375w=2 [2] http://cvs.apache.org/viewcvs.cgi/xml-fop/src/java/org/apache/fop/render/rtf/ListAttributesConverter.java?annotate=1.7 --- Christian Geisert [EMAIL PROTECTED] wrote: Glen Mazza wrote: Simon, a word of caution*, I believe that anything that goes into the Apache repository will need to be copyright The Apache Software Foundation and only The Apache Software Foundation. (Just look at the bottom No, the contribution is covered by the CLA (which you should have read and signed too ;-) See http://www.apache.org/licenses/#clas, paragraph 2: You hereby grant to the Foundation a non-exclusive, irrevocable, worldwide, no-charge, transferable copyright license to use, execute, prepare derivative works of, and distribute (internally and externally, in object code and, if included in your Contributions, source code form) your Contributions. Except for the rights granted to the Foundation in this paragraph, You reserve all right, title and interest in and to your Contributions. Christian
Re: (Copyright question) Re: Committing documentation
I completely agree with Christian's comment and extract of the CLA. I have signed it and thereby it applies to any work I commit to FOP's repository. That is my intention with the documentation. I wrote 'copyright the Authors', with the idea that every contributor adds his name as an author. But that is indeed probably not right. I will change it to ASF. The files themselves already have the Apache License 2 text. Regards, Simon On Mon, Jul 26, 2004 at 04:16:18AM -0700, Glen Mazza wrote: I believe the key word below is transferable, i.e., before checking any work in, it still needs to be copyright The Apache Software Foundation at the time of it being cvs committed. Dirk-Willem, might you know more about this? (Original comments in [1] below.) But I noticed Simon already updated it to The Authors--all it needs to be next (I think) is ASF and we're done: http://www.leverkruid.nl/FOP/documentation-html/index.html We already have a dubious copyright notice in one of our source files [2, lines 36-37], dubious because the file has changed so many times by other people over the years that it is unknown whether the copyright holder actually still owns any of the code. I'm inclined against adding non-ASF copyrighted work to our repository, because once you have it there, it is difficult to get rid of, no matter how out-of-date that copyright gets. If anyone is not ready to transfer the copyright to their work, then it shouldn't be in our repository. Glen [1] http://marc.theaimsgroup.com/?l=fop-devm=109079517313375w=2 [2] http://cvs.apache.org/viewcvs.cgi/xml-fop/src/java/org/apache/fop/render/rtf/ListAttributesConverter.java?annotate=1.7 --- Christian Geisert [EMAIL PROTECTED] wrote: Glen Mazza wrote: Simon, a word of caution*, I believe that anything that goes into the Apache repository will need to be copyright The Apache Software Foundation and only The Apache Software Foundation. (Just look at the bottom No, the contribution is covered by the CLA (which you should have read and signed too ;-) See http://www.apache.org/licenses/#clas, paragraph 2: You hereby grant to the Foundation a non-exclusive, irrevocable, worldwide, no-charge, transferable copyright license to use, execute, prepare derivative works of, and distribute (internally and externally, in object code and, if included in your Contributions, source code form) your Contributions. Except for the rights granted to the Foundation in this paragraph, You reserve all right, title and interest in and to your Contributions. Christian -- Simon Pepping home page: http://www.leverkruid.nl
Re: (Copyright question) Re: Committing documentation
Simon, My past emails on this topic had a rude tone to it that I regret...I apologize for that. I just didn't know how things should be copyrighted once they're in the repository and just wanted to make sure we are doing things properly. Thanks for your work (especially since it's in Docbook ;) and I look forward to helping out in keeping it up-to-date. Glen --- Simon Pepping [EMAIL PROTECTED] wrote: I completely agree with Christian's comment and extract of the CLA. I have signed it and thereby it applies to any work I commit to FOP's repository. That is my intention with the documentation. I wrote 'copyright the Authors', with the idea that every contributor adds his name as an author. But that is indeed probably not right. I will change it to ASF. The files themselves already have the Apache License 2 text. Regards, Simon On Mon, Jul 26, 2004 at 04:16:18AM -0700, Glen Mazza wrote: I believe the key word below is transferable, i.e., before checking any work in, it still needs to be copyright The Apache Software Foundation at the time of it being cvs committed. Dirk-Willem, might you know more about this? (Original comments in [1] below.) But I noticed Simon already updated it to The Authors--all it needs to be next (I think) is ASF and we're done: http://www.leverkruid.nl/FOP/documentation-html/index.html We already have a dubious copyright notice in one of our source files [2, lines 36-37], dubious because the file has changed so many times by other people over the years that it is unknown whether the copyright holder actually still owns any of the code. I'm inclined against adding non-ASF copyrighted work to our repository, because once you have it there, it is difficult to get rid of, no matter how out-of-date that copyright gets. If anyone is not ready to transfer the copyright to their work, then it shouldn't be in our repository. Glen [1] http://marc.theaimsgroup.com/?l=fop-devm=109079517313375w=2 [2] http://cvs.apache.org/viewcvs.cgi/xml-fop/src/java/org/apache/fop/render/rtf/ListAttributesConverter.java?annotate=1.7 --- Christian Geisert [EMAIL PROTECTED] wrote: Glen Mazza wrote: Simon, a word of caution*, I believe that anything that goes into the Apache repository will need to be copyright The Apache Software Foundation and only The Apache Software Foundation. (Just look at the bottom No, the contribution is covered by the CLA (which you should have read and signed too ;-) See http://www.apache.org/licenses/#clas, paragraph 2: You hereby grant to the Foundation a non-exclusive, irrevocable, worldwide, no-charge, transferable copyright license to use, execute, prepare derivative works of, and distribute (internally and externally, in object code and, if included in your Contributions, source code form) your Contributions. Except for the rights granted to the Foundation in this paragraph, You reserve all right, title and interest in and to your Contributions. Christian -- Simon Pepping home page: http://www.leverkruid.nl
Re: Javasrc, JXR and documentation
Peter, On Jun 29, 2004, at 7:04 PM, Peter B. West wrote: Clay, FYI, Java 1.4 javadoc tool supports a -linksource argument, which generates html of source files. However, the process seems to have pretty much the same restrictions as the Maven JXR - the only references are to line numbers, which is just about the most useless form imaginable. It might be of interest to someone at a later stage to look at extending the standard doclet to utilise Javasrc to perform that generation. Peter I've been hoping to get movement on the forrest front, then include the java doc stuff once I have xml-fop up running. As that's not moving along very fast, perhaps I can get a bit more information on what we need to do with the java doc front. Here's something I 'dug' up[1]. Looks like it's along the lines of what we're looking for, although I like what you've got on this page[2] better. Your version seems more accessible. However, you indicate: The problem is that there was no clean way to automatically generate the htmlized source. It's that supplementary facility that I'm looking for. What is the procedure used to generate the htmlized source? Could it be automated using gump or ant or something? BTW, what's the tool called you use to generate this? Web Maestro Clay [1] http://cvs.apache.org/~nicolaken/whiteboard/forrestdoc/ [2] http://xml.apache.org/fop/design/alt.design/properties/classes- overview.html
Committing documentation
I am preparing my documentation for check-in into the repository. What would be a suitable place. A directory in src/documentation/content/xdocs? Would that be in the way of the forrest build of the web site? Regards, Simon -- Simon Pepping home page: http://www.leverkruid.nl
Re: Committing documentation
On Jul 25, 2004, at 11:43 AM, Simon Pepping wrote: I am preparing my documentation for check-in into the repository. What would be a suitable place. A directory in src/documentation/content/xdocs? Would that be in the way of the forrest build of the web site? Regards, Simon I've been thinking about that, and I think FOP needs to add a new 'Documentation' tab, like the structure for the Forrest[1] documentation[2]. I would probably move much of the content under Using FOP under this other tab (although we could still maintain links from the Home Page if desired, and use a similar navigation structure to what's currently in place). As I understand it, you're primarily doing documentation that is more developer and/or embedded oriented, which is one of the reasons why I would want to have a new 'Documentation' tab. Web Maestro Clay [1] http://forrest.apache.org/ [2] http://forrest.apache.org/docs/your-project.html
Re: Committing documentation
Simon, a word of caution*, I believe that anything that goes into the Apache repository will need to be copyright The Apache Software Foundation and only The Apache Software Foundation. (Just look at the bottom of any of the FOP site's web pages.) Else, best not to commit it--we can always add a link from the Fop site to the documentation on your home page. If you plan on expanding your writing in the future to other areas of XML document publishing, I would recommend the latter right now, as I wouldn't want you to lose your work. Glen *That Jeremias is most welcome to correct, should I be in error here. --- Simon Pepping [EMAIL PROTECTED] wrote: I am preparing my documentation for check-in into the repository. What would be a suitable place. A directory in src/documentation/content/xdocs? Would that be in the way of the forrest build of the web site? Regards, Simon -- Simon Pepping home page: http://www.leverkruid.nl
Re: Committing documentation
Glen Mazza wrote: Simon, a word of caution*, I believe that anything that goes into the Apache repository will need to be copyright The Apache Software Foundation and only The Apache Software Foundation. (Just look at the bottom No, the contribution is covered by the CLA (which you should have read and signed too ;-) See http://www.apache.org/licenses/#clas, paragraph 2: You hereby grant to the Foundation a non-exclusive, irrevocable, worldwide, no-charge, transferable copyright license to use, execute, prepare derivative works of, and distribute (internally and externally, in object code and, if included in your Contributions, source code form) your Contributions. Except for the rights granted to the Foundation in this paragraph, You reserve all right, title and interest in and to your Contributions. Christian
Re: Javasrc, JXR and documentation
On Jul 8, 2004, at 5:02 PM, Peter B. West wrote: Clay Leeds wrote: Peter, Did you get a chance to try the procedure Nicola recommended[1]? I haven't gotten a successful build yet, but I'm still working at it. When I do, I'll try to do as he suggested. No, I've been too busy working on the FAD layout lately. I can relate. Of course, there's also the 'issue' of you being a newlywed! Tell the Mrs. the 'guys' say 'Cheers!' :-) I actually was getting stuck on the BUILD portions, but I was still using forrest 0.5.1. Much of the forrest development is going towards 0.6 which I believe has an imminent release (days? weeks? months? :-D). With all of the stuff going on (XML Graphics, forrest.apache.org, etc.) coupled with the fact that the forrest-site 'skin' is a bit outdated, I thought it best to work toward a 0.6 version of the FOP website. At the same time I'll also change to one of the other skins (css-style, xhtml-css, krysalis-site, tigris-site, etc.). If anyone has a particular preference, please chime in! I'm leaning a bit toward the css-style, as it appears to offer the greatest flexibility, and seems to better leverage css over tables... But we'll see! As we're all anxious to see a Whole Site PDF (not to mention the 'new' logo :-D) I might use one of the others if css-style isn't ready in time. BTW, how does Simon's recent Documentation[2] figure in to this? I don't know. I think the fact that Simon's docs are Docbook based will militate against linking in to the sources, but Simon would be in the best position to answer this. If it could be done, it would be a great boon to the documentation. That actually shouldn't be too hard... It appears that forrest is pretty much built to work with docbook[3]. We can either just 'stick it in the directory' and It Should Just Work(tm)--albeit with limited transformation of the presumably more advanced DocBook elements, or we can use the full DocBook stylesheets themselves (which is probably the preferred method). Each has its own issues. [OT] militate? heh... there's a word I tend to 'try' to stay away from in every day conversation... (it's not that hard, as I don't think I've ever heard it...). [1] http://marc.theaimsgroup.com/?l=fop-devm=108680587917268w=2 [2] http://marc.theaimsgroup.com/?l=fop-devm=108844739724995w=2 [3] http://forrest.apache.org/faq.html#docbook Web Maestro Clay
Re: Javasrc, JXR and documentation
Clay Leeds wrote: Peter, Did you get a chance to try the procedure Nicola recommended[1]? I haven't gotten a successful build yet, but I'm still working at it. When I do, I'll try to do as he suggested. No, I've been too busy working on the FAD layout lately. BTW, how does Simon's recent Documentation[2] figure in to this? I don't know. I think the fact that Simon's docs are Docbook based will militate against linking in to the sources, but Simon would be in the best position to answer this. If it could be done, it would be a great boon to the documentation. [1] http://marc.theaimsgroup.com/?l=fop-devm=108680587917268w=2 [2] http://marc.theaimsgroup.com/?l=fop-devm=108844739724995w=2 Peter -- Peter B. West http://www.powerup.com.au/~pbwest/resume.html
Re: Documentation finished
On Wed, Jun 30, 2004 at 02:04:30PM -0700, Glen Mazza wrote: On second thought, I would hold off on this; I just noticed you copywrited the document under your name; hence it would probably be improper to include the current FOP system documentation from Keiron/Kelly or other former/current committers. That is not a problem. I never publish anything without a copyright holder. If it goes to FOP CVS and other contributions are merged, then the copyright holder is just changed, like with source code. Regards, Simon -- Simon Pepping home page: http://www.leverkruid.nl
Re: Javasrc, JXR and documentation
Peter, On Jun 29, 2004, at 7:04 PM, Peter B. West wrote: Clay, FYI, Java 1.4 javadoc tool supports a -linksource argument, which generates html of source files. However, the process seems to have pretty much the same restrictions as the Maven JXR - the only references are to line numbers, which is just about the most useless form imaginable. It might be of interest to someone at a later stage to look at extending the standard doclet to utilise Javasrc to perform that generation. Peter -- Peter B. West http://www.powerup.com.au/~pbwest/resume.html Did you get a chance to try the procedure Nicola recommended[1]? I haven't gotten a successful build yet, but I'm still working at it. When I do, I'll try to do as he suggested. BTW, how does Simon's recent Documentation[2] figure in to this? [1] http://marc.theaimsgroup.com/?l=fop-devm=108680587917268w=2 [2] http://marc.theaimsgroup.com/?l=fop-devm=108844739724995w=2
Re: Documentation finished
Hi Clay, On Mon, Jun 28, 2004 at 11:54:10AM -0700, Clay Leeds wrote: Looks pretty good. As you indicated, there are a few areas to be improved (e.g., 'TO BE IMPROVED and 'no data' sections), and some I spent quite some time to this documentation. The chapter on properties took quite a bit more work than I expected. Now I want to take a break. I will look at those passages later. issues with formatting (I think they're related to the text-align='justify' setting--perhaps the document would read better with default (i.e., 'left') justification?), but by and large this I suppose you refer to the section titles like 'LineLayoutManager.getNextBreakPoss'. I noticed that these can be mended using hyphenate=false, but it is hard to specify that through DocBook. I think I will change those titles, and set text-align=left for the section titles. Otherwise I am quite pleased with the justification. looks like it will be a valuable addition to the FOP arsenal! One other addition I'd like to see is that the fo:region-before include the Chapter '#' in addition to the Title. I will see if I can customize the DocBook style sheets to do that. There are a few other things that may benefit from customization. Regards, Simon -- Simon Pepping home page: http://www.leverkruid.nl
Re: Documentation finished
On Mon, Jun 28, 2004 at 02:31:27PM -0700, Glen Mazza wrote: Before doing so, it would probably be good if you could look at our System design pages (http://xml.apache.org/fop/design/index.html), if you haven't already, and add to your document anything from them that is still relevant and useful but missing from your document. I have read them but I have not checked whether I have included everything that is relevant. As I replied to Clay, I now want to take a break from this work, and try to do some coding. I will take your suggestion up later. That way, when we add your document to our website, we can rid of the system design pages. (Most of them are obsolete with the changing architecture anyway.) That way, we will just have one official Docbook-based document to maintain. Much of it is still remarkably relevant, esp. regarding FO trees and Layout system. Regards, Simon -- Simon Pepping home page: http://www.leverkruid.nl
Re: Javasrc, JXR and documentation
Clay, FYI, Java 1.4 javadoc tool supports a -linksource argument, which generates html of source files. However, the process seems to have pretty much the same restrictions as the Maven JXR - the only references are to line numbers, which is just about the most useless form imaginable. It might be of interest to someone at a later stage to look at extending the standard doclet to utilise Javasrc to perform that generation. Peter -- Peter B. West http://www.powerup.com.au/~pbwest/resume.html
Documentation finished
Hi, I finished my documentation of the FOP architecture and code. Well, more or less; this is version 0.9. Maybe I'll add a short introduction or some such. See http://www.leverkruid.nl/FOP/index.html. How can this be contributed to the FOP website? The documentation consists of a number of Docbook 4.2 XML files. Could this be part of the wiki? Or could it be in CVS? Regards, Simon -- Simon Pepping home page: http://www.leverkruid.nl
Re: Documentation finished
On Jun 28, 2004, at 11:25 AM, Simon Pepping wrote: Hi, I finished my documentation of the FOP architecture and code. Well, more or less; this is version 0.9. Maybe I'll add a short introduction or some such. See http://www.leverkruid.nl/FOP/index.html. Looks pretty good. As you indicated, there are a few areas to be improved (e.g., 'TO BE IMPROVED and 'no data' sections), and some issues with formatting (I think they're related to the text-align='justify' setting--perhaps the document would read better with default (i.e., 'left') justification?), but by and large this looks like it will be a valuable addition to the FOP arsenal! One other addition I'd like to see is that the fo:region-before include the Chapter '#' in addition to the Title. How can this be contributed to the FOP website? The documentation consists of a number of Docbook 4.2 XML files. Could this be part of the wiki? Or could it be in CVS? I would think this owuld be of interest to some of the more advanced fop-users (particularly those interested in customizing via Java and/or embedding). As such, perhaps there might be a place for its inclusion in a Docs tab or something? Regards, Simon -- Simon Pepping home page: http://www.leverkruid.nl Web Maestro Clay
Re: Documentation finished
Great, this makes for an excellent system design document that we can refine over time. I'm also happy you have it done in Docbook. We're doing it right the first time that way. I'd like to see it incorporated, in Docbook format, on our site. Tapestry has already managed Forrest and Docbook together (http://jakarta.apache.org/tapestry/doc.html). Before doing so, it would probably be good if you could look at our System design pages (http://xml.apache.org/fop/design/index.html), if you haven't already, and add to your document anything from them that is still relevant and useful but missing from your document. That way, when we add your document to our website, we can rid of the system design pages. (Most of them are obsolete with the changing architecture anyway.) That way, we will just have one official Docbook-based document to maintain. Thanks, Glen --- Simon Pepping [EMAIL PROTECTED] wrote: Hi, I finished my documentation of the FOP architecture and code. Well, more or less; this is version 0.9. Maybe I'll add a short introduction or some such. See http://www.leverkruid.nl/FOP/index.html. How can this be contributed to the FOP website? The documentation consists of a number of Docbook 4.2 XML files. Could this be part of the wiki? Or could it be in CVS? Regards, Simon -- Simon Pepping home page: http://www.leverkruid.nl
Re: Javasrc, JXR and documentation
On Jun 8, 2004, at 6:48 PM, Peter B. West wrote: It's not a question of moving away, necessarily. What I'm looking for is a supplementary facility. Look at http://xml.apache.org/fop/design/alt.design/properties/classes- overview.html and click on one of the class name links on the left of the main page, e.g. PropNames. That opens an iframe with the source. On linux, in Mozilla, it also positions the iframe at the top of the page. Clicking the link again - it's a toggle - restores the previous position of the page. When I first set is up, this tidy behaviour was not available on Windows using either Mozilla or IE, but that may have changed by now. FWIW, it works nicely in Mac OS X 10.3.4, Safari 1.2.2 (v125.7) (although it doesn't position the iFrame at the top of the page) as well as Mozilla 1.7b (where it *does* jump to the top of the iFrame). The problem is that there was no clean way to automatically generate the htmlized source. It's that supplementary facility that I'm looking for. OK. I'll see what I can dig up on the subject. If you have any other keywords I can use in my search, by all means, send 'em my way! Web Maestro Clay
Re: Javasrc, JXR and documentation
Clay Leeds wrote: On Jun 8, 2004, at 6:48 PM, Peter B. West wrote: The problem is that there was no clean way to automatically generate the htmlized source. It's that supplementary facility that I'm looking for. OK. I'll see what I can dig up on the subject. If you have any other keywords I can use in my search, by all means, send 'em my way! Clay, I would recommend emailing Nicola on the topic. I'm sure he would be only too pleased to tell you about the situation with Javasrc. Peter -- Peter B. West http://www.powerup.com.au/~pbwest/resume.html
Re: Javasrc, JXR and documentation
Peter, On Jun 9, 2004, at 8:06 AM, Peter B. West wrote: Clay Leeds wrote: On Jun 8, 2004, at 6:48 PM, Peter B. West wrote: The problem is that there was no clean way to automatically generate the htmlized source. It's that supplementary facility that I'm looking for. OK. I'll see what I can dig up on the subject. If you have any other keywords I can use in my search, by all means, send 'em my way! Clay, I would recommend emailing Nicola on the topic. I'm sure he would be only too pleased to tell you about the situation with Javasrc. Peter -- Peter B. West http://www.powerup.com.au/~pbwest/resume.html As you guessed, Nicola was only too happy to help. Now I just need to get the FOP site up and running with Forrest (so we can include Whole Site PDF HTML links on our site!). Web Maestro Clay Nicola's response is below: Begin forwarded message: From: Nicola Ken Barozzi [EMAIL PROTECTED] Date: June 9, 2004 10:13:13 AM PDT To: Clay Leeds [EMAIL PROTECTED] Subject: Re: Possibility of Using Javasrc for FOP Clay Leeds wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hi Nicola, We are exploring the possibility of using Javasrc in generating cross-referenced source in html format, into which we can point from the web-site documentation. Here's the thread[1] to follow for info. Javasrc is now in Forrest scratchpad. Get Forrest from SVN, install graphviz [x1] for a complete build, cd into scratchpad/forrestdoc, then run build project -Dproject.dir=[enter base project dir here] It will generate documentation with javadocs, javasrc, ant docs with dependency graphs, full class diagram, javascript docs. Here is an example: http://cvs.apache.org/~nicolaken/whiteboard/forrestdoc/ Note that the colors of the java src can be made much more different, they are more varied than JXR. Peter West's alt-design has an example[2] of what we want to do: [Peter West] click on one of the class name links on the left of the main page, e.g. PropNames. That opens an iframe with the source. On linux, in Mozilla, it also positions the iframe at the top of the page. Clicking the link again - it's a toggle - restores the previous position of the page. [/Peter West] That's cool! Currently we are focusing on fixing bugs for a 0.6 release, but doing this is on my chart. Actually, what I would like to do is to integrate this forrestdoc in forrest, and have forrest create a complete pdf, htmlhelp and javahelp files for the whole site. Also in this I would like to add something like this, so that users can browse the javadocs and the source dynamically without having to statically generate all the docs (just an index): http://chaperon.sourceforge.net/screenshots.html And then integrate all these docs in our Lucene-based search. Please let me know if there's any other information I can provide. More precisely, what can I do for you? :-) Given the above, I think you have enough to start off helping somewhat. For any other discussion, please refer to [EMAIL PROTECTED] (soon [EMAIL PROTECTED]). TIA, and thanks for contacting me on this! Thanks! Web Maestro Clay [1] http://marc.theaimsgroup.com/?l=fop-devm=108670344811832w=2 [2] http://xml.apache.org/fop/design/alt.design/properties/classes- overview.html [x1] http://www.research.att.com/sw/tools/graphviz/ -- Nicola Ken Barozzi [EMAIL PROTECTED] - verba volant, scripta manent - (discussions get forgotten, just code remains)
Javasrc, JXR and documentation
Clay, Do you have time for some documentation investigations? Some time ago, a project called Javasrc was in the process of migrating from SourceForge to Apache. Nicola Ken Barozzi [EMAIL PROTECTED] was the one who initiated the discussions with the Javasrc developers. The code was originally to go into Alexandria, a project on which development has now ceased. I recall some discussion about the use of Javasrc outside the context of Alexandria. There is an alternative, in the JXR plugin for Maven. Joerg may be of help here, as he seems to be a fan of Maven. My primary interest in this question is in generating cross-referenced source in html format, into which I can point from the web-site documentation. At the moment I have some html source that I generated using Xemacs, but that is extremely tedious. If you have time, could you ask a few questions about the best way of having such cross-referenced html sources generated as part of the process of web site creation? Peter -- Peter B. West http://www.powerup.com.au/~pbwest/resume.html
Re: Javasrc, JXR and documentation
I'm unsure if this is related to your question, but I think it would be nice for us to switch to Docbook. Apparently at least one Apache project, Tapestry, is already using it with Forrest [1][2]. We switched at work from RoboHelp HTML to Docbook and it has been great for us. Glen [1] http://wiki.docbook.org/topic/WhoUsesDocBook [2] http://jakarta.apache.org/tapestry/doc.html --- Peter B. West [EMAIL PROTECTED] wrote: Clay, Do you have time for some documentation investigations? Some time ago, a project called Javasrc was in the process of migrating from SourceForge to Apache. Nicola Ken Barozzi [EMAIL PROTECTED] was the one who initiated the discussions with the Javasrc developers. The code was originally to go into Alexandria, a project on which development has now ceased. I recall some discussion about the use of Javasrc outside the context of Alexandria. There is an alternative, in the JXR plugin for Maven. Joerg may be of help here, as he seems to be a fan of Maven. My primary interest in this question is in generating cross-referenced source in html format, into which I can point from the web-site documentation. At the moment I have some html source that I generated using Xemacs, but that is extremely tedious. If you have time, could you ask a few questions about the best way of having such cross-referenced html sources generated as part of the process of web site creation? Peter -- Peter B. West http://www.powerup.com.au/~pbwest/resume.html
Re: Javasrc, JXR and documentation
Peter, On Jun 8, 2004, at 7:15 AM, Peter B. West wrote: Clay, Do you have time for some documentation investigations? Some time ago, a project called Javasrc was in the process of migrating from SourceForge to Apache. Nicola Ken Barozzi [EMAIL PROTECTED] was the one who initiated the discussions with the Javasrc developers. The code was originally to go into Alexandria, a project on which development has now ceased. I recall some discussion about the use of Javasrc outside the context of Alexandria. There is an alternative, in the JXR plugin for Maven. Joerg may be of help here, as he seems to be a fan of Maven. My primary interest in this question is in generating cross-referenced source in html format, into which I can point from the web-site documentation. At the moment I have some html source that I generated using Xemacs, but that is extremely tedious. If you have time, could you ask a few questions about the best way of having such cross-referenced html sources generated as part of the process of web site creation? Peter -- Peter B. West http://www.powerup.com.au/~pbwest/resume.html I'd be happy to do some research on this subject. I'll look into this and see what i can dig up. Before I spend time on this, it might make more sense to look into Docbook, as Glen mentioned. In addition, it would be good to spend some time checking out what other Apache projects are using for ideas. I would suspect that the most-used documentation system(s) would bear the most fruit for us. If for no other reason, than the sheer numbers of people banging on them. I assume we already have a system (I think it's Javadocs). I think it would also be good to determine if any of our colleagues have made the switch from our system to another. Finally, assuming we've already got a system, what are the reasons we're moving away from our current system? Complexity? Dead-end product? Etc. Web Maestro Clay
cvs commit: xml-fop/src/documentation/content/xdocs embedding.xml
gmazza 2004/04/11 14:53:41 Modified:src/documentation/content/xdocs embedding.xml Log: Returned documentation on how to do Avalon logging; documentation now in two sections. Revision ChangesPath 1.21 +29 -4 xml-fop/src/documentation/content/xdocs/embedding.xml Index: embedding.xml === RCS file: /home/cvs/xml-fop/src/documentation/content/xdocs/embedding.xml,v retrieving revision 1.20 retrieving revision 1.21 diff -u -r1.20 -r1.21 --- embedding.xml 1 Apr 2004 23:38:44 - 1.20 +++ embedding.xml 11 Apr 2004 21:53:41 - 1.21 @@ -65,12 +65,37 @@ In the example above, args[0] contains the path to an XSL-FO file, while args[1] contains a path for the target PDF file. /p - section id=basic-logging + section id=basic-logging titleLogging/title p You also need to set up logging. Global logging for all FOP processes is managed by MessageHandler. Per-instance logging is handled by Driver. You want to set both using an implementation + of org.apache.avalon.framework.logger.Logger. See + jump href=#loggingbelow/jump for more information. +/p +p + Call codesetLogger(Logger)/code always immediately after + instantiating the Driver object. See here: +/p +source![CDATA[ +import org.apache.avalon.framework.logger.Logger; +import org.apache.avalon.framework.logger.ConsoleLogger; + +/*..*/ + +Driver driver = new Driver(); +Logger logger = new ConsoleLogger(ConsoleLogger.LEVEL_INFO); +MessageHandler.setScreenLogger(logger); +driver.setLogger(logger);]]/source + /section + + section id=basic-logging-new-version +titleLogging (Upcoming FOP 1.0 Version only)/title +p + You also need to set up logging. Global logging for all FOP + processes is managed by MessageHandler. Per-instance logging + is handled by Driver. You want to set both using an implementation of org.apache.commons.logging.Log. See jump href=#loggingbelow/jump for more information. /p @@ -160,7 +185,7 @@ section id=logging titleControlling logging/title p - FOP uses the + Current FOP 0.20.x production uses the fork href=http://avalon.apache.org/framework/api/org/apache/avalon/framework/logger/package-summary.html;Logger package/fork from Apache Avalon Framework to do logging. See the fork href=http://avalon.apache.org/framework/;Apache Avalon Framework/fork - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
cvs commit: xml-fop/src/documentation/content/xdocs team.xml
cbowditch2004/04/08 06:17:15 Modified:src/documentation/content/xdocs team.xml Log: added Luca Furini to contributor section Revision ChangesPath 1.30 +5 -2 xml-fop/src/documentation/content/xdocs/team.xml Index: team.xml === RCS file: /home/cvs/xml-fop/src/documentation/content/xdocs/team.xml,v retrieving revision 1.29 retrieving revision 1.30 diff -u -r1.29 -r1.30 --- team.xml 4 Apr 2004 14:27:23 - 1.29 +++ team.xml 8 Apr 2004 13:17:15 - 1.30 @@ -66,6 +66,9 @@ is a TeX/LaTeX and XML expert with Elsevier at its Amsterdam office. See his fork href=http://www.leverkruid.nl;home page/fork for some of his private projects./li +!-- Luca prefers the mail address with AT, to stop spam, etc. -- + lilink href=mailto:lfurini AT cs.unibo.itLuca Furini/link +is a student of Computer Studies at the University of Bologna (Italy)/li /ul /section section id=founder - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
cvs commit: xml-fop/src/documentation/content/xdocs team.xml
adelmelle2004/04/04 07:27:23 Modified:src/documentation/content/xdocs team.xml Log: testing commit access Revision ChangesPath 1.29 +3 -3 xml-fop/src/documentation/content/xdocs/team.xml Index: team.xml === RCS file: /home/cvs/xml-fop/src/documentation/content/xdocs/team.xml,v retrieving revision 1.28 retrieving revision 1.29 diff -u -r1.28 -r1.29 --- team.xml 2 Mar 2004 21:20:51 - 1.28 +++ team.xml 4 Apr 2004 14:27:23 - 1.29 @@ -31,7 +31,7 @@ lilink href=mailto:[EMAIL PROTECTED]Finn Bock/link (FB)/li lilink href=mailto:[EMAIL PROTECTED]Chris Bowditch/link (CB) is a Java/VB Programmer from England./li -lilink href=mailto:[EMAIL PROTECTED]Andreas Delmelle/link (AD)/li +lilink href=mailto:[EMAIL PROTECTED]Andreas Delmelle/link (AD)/li li id=cglink href=mailto:[EMAIL PROTECTED]Christian Geisert/link (CG)/li lilink href=mailto:[EMAIL PROTECTED]Peter Herweg/link (PH) is helping to integrate the jfor project's RTF support into the upcoming FOP 1.0 version. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
cvs commit: xml-fop/src/documentation/content/xdocs embedding.xml
gmazza 2004/04/01 15:38:44 Modified:src/documentation/content/xdocs embedding.xml Log: Update to examples: added text about DOM2PDF and PDF Transcoder examples. Revision ChangesPath 1.20 +26 -13xml-fop/src/documentation/content/xdocs/embedding.xml Index: embedding.xml === RCS file: /home/cvs/xml-fop/src/documentation/content/xdocs/embedding.xml,v retrieving revision 1.19 retrieving revision 1.20 diff -u -r1.19 -r1.20 --- embedding.xml 31 Mar 2004 10:55:05 - 1.19 +++ embedding.xml 1 Apr 2004 23:38:44 - 1.20 @@ -453,8 +453,8 @@ titleExampleObj2PDF.java/title p fork href=http://cvs.apache.org/viewcvs.cgi/xml-fop/examples/embedding/java/embedding/ExampleObj2PDF.java?rev=HEAD; -The last example/fork -here combines the previous and the third to demonstrate +This example/fork +combines the previous and the third to demonstrate how you can transform a Java object to a PDF directly in one smooth run by generating SAX events from the Java object that get fed to an XSL transformation. The result of the transformation is then converted to PDF @@ -462,19 +462,32 @@ /p figure src=images/EmbeddingExampleObj2PDF.png alt=Example Java object to PDF (via XML and XSL-FO)/ /section + section id=ExampleDOM2PDF +titleExampleDOM2PDF.java/title +p +fork href=http://cvs.apache.org/viewcvs.cgi/xml-fop/examples/embedding/java/embedding/ExampleDOM2PDF.java?rev=HEAD; +This example/fork +has FOP use a DOMSource instead of a StreamSource in order to +use a DOM tree as input for an XSL transformation. +/p + /section + section id=ExampleSVG2PDF +titleExampleSVG2PDF.java (PDF Transcoder example)/title +p +fork href=http://cvs.apache.org/viewcvs.cgi/xml-fop/examples/embedding/java/embedding/ExampleSVG2PDF.java?rev=HEAD; +This example/fork +shows use of the PDF Transcoder, a sub-application within FOP. +It is used to generate a PDF document from an SVG file. +/p + /section section id=example-notes titleFinal notes/title p These examples should give you an idea of what's possible. It should be easy -to adjust these examples to your needs. For examples, you can use a DOMSource -instead of a StreamSource to feed a DOM tree as input for an XSL -transformation. -/p -p -If you think you have a decent example that should be here, contact us via -one of the mailing lists and we'll see to it that it gets added. Also, if -you can't find the solution to your particular problem drop us a message on -the fop-user mailing list. +to adjust these examples to your needs. Also, if you have other examples that you +think should be added here, please let us know via either the FOP-USER or FOP-DEV +mailing lists. Finally, for more help please send your questions to the FOP-USER +mailing list. /p /section /section - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
cvs commit: xml-fop/src/documentation/content/xdocs anttask.xml
gmazza 2004/03/20 10:00:57 Modified:src/documentation/content/xdocs anttask.xml Log: updated anttask documentation Revision ChangesPath 1.10 +21 -6 xml-fop/src/documentation/content/xdocs/anttask.xml Index: anttask.xml === RCS file: /home/cvs/xml-fop/src/documentation/content/xdocs/anttask.xml,v retrieving revision 1.9 retrieving revision 1.10 diff -u -r1.9 -r1.10 --- anttask.xml 2 Mar 2004 21:15:35 - 1.9 +++ anttask.xml 20 Mar 2004 18:00:57 - 1.10 @@ -94,11 +94,26 @@ /td tdNo, default is codefalse/code/td /tr - !--tr Commented out; attribute is currently unimplemented according to the code + tr tdbasedir/td - tdDirectory to work from/td - tdYes/td - /tr-- + tdBase directory to resolve relative references (e.g., graphics files) within the +FO document. + /td + tdNo, for single FO File entry, default is to use the location +of that FO file. + /td + /tr + tr + tdrelativebase/td + tdFor fileset usage only. A value of codetrue/code specifies using the location +of each .fo file as the base directory for resolving relative file references located +within that .fo file. A value of codefalse/code specifies using the value of +basedir for all files within the fileset, or just the current working directory +if basedir is not specified. + /td + tdNo, default is codefalse/code. + /td + /tr tr tduserconfig/td tdUser configuration file (same as the FOP -c command line option)/td - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
cvs commit: xml-fop/src/documentation/content/xdocs/design layout.xml
cbowditch2004/03/17 06:24:23 Modified:src/documentation/content/xdocs/design layout.xml Log: updated status of layout development work on HEAD as discussed on fop-user http://nagoya.apache.org/eyebrowse/[EMAIL PROTECTED]msgNo=10498 Revision ChangesPath 1.15 +85 -8 xml-fop/src/documentation/content/xdocs/design/layout.xml Index: layout.xml === RCS file: /home/cvs/xml-fop/src/documentation/content/xdocs/design/layout.xml,v retrieving revision 1.14 retrieving revision 1.15 diff -u -r1.14 -r1.15 --- layout.xml2 Mar 2004 21:32:03 - 1.14 +++ layout.xml17 Mar 2004 14:24:22 - 1.15 @@ -301,15 +301,92 @@ titleStatus/title section id=status-todo titleTo Do/title +table + tr +thTask/th +thPriority/th +thNotes/th + /tr + tr +tdJustified Text/td +tdHigh/td +td/ + /tr + tr +tdMulti-column layout/td +tdHigh/td +td/ + /tr + tr +tdRe-parenting retrieved markers/td +tdHigh/td +td/ + /tr + tr +tdAbsolutely positioned block containers/td +tdHigh/td +td/ + /tr + tr +tdBackground Images/td +tdHigh/td +td/ + /tr + tr +tdConditional space suppression/td +tdHigh/td +td/ + /tr + tr +tdFootnotes/td +tdMedium/td +td/ + /tr + tr +tdRelative positioned block containers/td +tdMedium/td +td/ + /tr + tr +tdFine-tuning line breaking and hypenation/td +tdMedium/td +td/ + /tr + tr +tdLast page layout/td +tdMedium/td +td/ + /tr + tr +tdAligned leaders, especially in justified text/td +tdMedium/td +td/ + /tr + tr +tdFloats of all kind/td +tdLow/td +td/ + /tr + tr +tdBorder collapsing on tables/td +tdLow/td +tdRenderX hasnt implemented this (17/03/04)/td + /tr + tr +tdFine-tuning all other borders/td +tdLow/td +tdNot sure what Joerg means by this, border collapse priorties? +Dashed and dotted borders have been implemented in PDF/td + /tr + tr +tdBIDI support/td +tdLow/td +td/ + /tr +/table /section section id=status-wip titleWork in Progress/title -ul - listrongbetter layout design/strong - that can handle keeps and spacing better/li - listrongbetter area tree handling/strong - means it can run in less memory/li - linew area tree model/li - lichanged area tree xml format to match the area tree hierarchy/li -/ul /section section id=status-complete titleCompleted/title - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
cvs commit: xml-fop/src/documentation/content/xdocs news.xml
gmazza 2004/03/07 15:29:23 Modified:src/documentation/content/xdocs news.xml Log: Add Clay to news page. Revision ChangesPath 1.19 +6 -2 xml-fop/src/documentation/content/xdocs/news.xml Index: news.xml === RCS file: /home/cvs/xml-fop/src/documentation/content/xdocs/news.xml,v retrieving revision 1.18 retrieving revision 1.19 diff -u -r1.18 -r1.19 --- news.xml 2 Mar 2004 21:15:35 - 1.18 +++ news.xml 7 Mar 2004 23:29:23 - 1.19 @@ -25,6 +25,10 @@ /header body section + title7 March 2004 - New Committer/title + pWelcome Web Maestro Clay Leeds!/p +/section +section title10 January 2004 - New Committers/title pWelcome Chris Bowditch and Andreas Delmelle!/p /section - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
cvs commit: xml-fop/src/documentation/content/design/alt.design codedisplay.js FOPropertySets.html FoXMLEvent.html SyncedFoXmlEventsBuffer.html XMLNamespaces.html
jeremias2004/03/02 12:51:33
Modified:src/documentation/content/design/alt.design codedisplay.js
FOPropertySets.html FoXMLEvent.html
SyncedFoXmlEventsBuffer.html XMLNamespaces.html
Log:
Applied Apache License Version 2.0 by following the instructions at
http://www.apache.org/dev/apply-license.html.
Revision ChangesPath
1.2 +15 -1
xml-fop/src/documentation/content/design/alt.design/codedisplay.js
Index: codedisplay.js
===
RCS file:
/home/cvs/xml-fop/src/documentation/content/design/alt.design/codedisplay.js,v
retrieving revision 1.1
retrieving revision 1.2
diff -u -r1.1 -r1.2
--- codedisplay.js20 Mar 2003 05:15:45 - 1.1
+++ codedisplay.js2 Mar 2004 20:51:33 - 1.2
@@ -1,3 +1,17 @@
+// Copyright 1999-2004 The Apache Software Foundation
+//
+// Licensed under the Apache License, Version 2.0 (the License);
+// you may not use this file except in compliance with the License.
+// You may obtain a copy of the License at
+//
+// http://www.apache.org/licenses/LICENSE-2.0
+//
+// Unless required by applicable law or agreed to in writing, software
+// distributed under the License is distributed on an AS IS BASIS,
+// WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+// See the License for the specific language governing permissions and
+// limitations under the License.
+//
// $Id$
var showing = new Array();
var x = new Array(); // scrollX
1.2 +31 -8
xml-fop/src/documentation/content/design/alt.design/FOPropertySets.html
Index: FOPropertySets.html
===
RCS file:
/home/cvs/xml-fop/src/documentation/content/design/alt.design/FOPropertySets.html,v
retrieving revision 1.1
retrieving revision 1.2
diff -u -r1.1 -r1.2
--- FOPropertySets.html 18 Dec 2002 15:53:21 - 1.1
+++ FOPropertySets.html 2 Mar 2004 20:51:33 - 1.2
@@ -1,4 +1,20 @@
!DOCTYPE html PUBLIC -//W3C//DTD HTML 4.01//EN
+!--
+ Copyright 2001-2002,2004 The Apache Software Foundation
+
+ Licensed under the Apache License, Version 2.0 (the License);
+ you may not use this file except in compliance with the License.
+ You may obtain a copy of the License at
+
+ http://www.apache.org/licenses/LICENSE-2.0
+
+ Unless required by applicable law or agreed to in writing, software
+ distributed under the License is distributed on an AS IS BASIS,
+ WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+ See the License for the specific language governing permissions and
+ limitations under the License.
+--
+!-- $Id$ --
!-- Created by htmlize-0.67 in css mode. --
html
head
@@ -68,13 +84,19 @@
body
pre
span class=comment/*
- * $Id$
- * Copyright (C) 2001 The Apache Software Foundation. All rights reserved.
- * For details on use and redistribution please refer to the
- * LICENSE file included with these sources.
- *
- * @author lt;a href=quot;mailto:[EMAIL PROTECTED]quot;gt;Peter B.
Westlt;/agt;
- * @version $Id$
+ * Copyright 2001-2002,2004 The Apache Software Foundation.
+ *
+ * Licensed under the Apache License, Version 2.0 (the License);
+ * you may not use this file except in compliance with the License.
+ * You may obtain a copy of the License at
+ *
+ * http://www.apache.org/licenses/LICENSE-2.0
+ *
+ * Unless required by applicable law or agreed to in writing, software
+ * distributed under the License is distributed on an AS IS BASIS,
+ * WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+ * See the License for the specific language governing permissions and
+ * limitations under the License.
*//span
span class=keywordpackage/span span
class=jde-java-font-lock-packageorg/span.span
class=jde-java-font-lock-packageapache/span.span
class=jde-java-font-lock-packagefop/span.span
class=jde-java-font-lock-packagefo/span;
@@ -100,6 +122,7 @@
span class=comment/**
* Data class relating sets of properties to Flow Objects.
+ * @author lt;a href=quot;mailto:[EMAIL PROTECTED]quot;gt;Peter B.
Westlt;/agt;
*//span
span class=jde-java-font-lock-modifierpublic/span span
class=keywordclass/span span class=function-name
id=FOPropertySetsClassFOPropertySets/span {
1.2 +33 -9
xml-fop/src/documentation/content/design/alt.design/FoXMLEvent.html
Index: FoXMLEvent.html
===
RCS file:
/home/cvs/xml-fop/src/documentation/content/design/alt.design/FoXMLEvent.html,v
retrieving revision 1.1
retrieving revision 1.2
diff -u -r1.1 -r1.2
--- FoXMLEvent.html 12 Mar 2003 14:56:46 -
cvs commit: xml-fop/src/documentation/content/design/alt.design/properties AbstractPropertyValue.html AutoRestore.html BorderCommonStyle.html BorderCommonWidth.html BorderLeftStyle.html BorderLeftWidth.html Character.html Direction.html FOAttributes.html PropNames.html Property.html PropertyConsts.html PropertyParser.html PropertySets.html PropertyTokenizer.html PropertyValue.html PropertyValueList.html RenderingIntent.html ShorthandPropSets.html codedisplay.js
jeremias2004/03/02 13:07:26 Modified:src/documentation/content/design/alt.design/properties AbstractPropertyValue.html AutoRestore.html BorderCommonStyle.html BorderCommonWidth.html BorderLeftStyle.html BorderLeftWidth.html Character.html Direction.html FOAttributes.html PropNames.html Property.html PropertyConsts.html PropertyParser.html PropertySets.html PropertyTokenizer.html PropertyValue.html PropertyValueList.html RenderingIntent.html ShorthandPropSets.html codedisplay.js Log: Applied Apache License Version 2.0 by following the instructions at http://www.apache.org/dev/apply-license.html. Revision ChangesPath 1.2 +33 -10 xml-fop/src/documentation/content/design/alt.design/properties/AbstractPropertyValue.html Index: AbstractPropertyValue.html === RCS file: /home/cvs/xml-fop/src/documentation/content/design/alt.design/properties/AbstractPropertyValue.html,v retrieving revision 1.1 retrieving revision 1.2 diff -u -r1.1 -r1.2 --- AbstractPropertyValue.html20 Jan 2003 14:45:18 - 1.1 +++ AbstractPropertyValue.html2 Mar 2004 21:07:25 - 1.2 @@ -1,4 +1,20 @@ !DOCTYPE html PUBLIC -//W3C//DTD HTML 4.01//EN +!-- + Copyright 1999-2004 The Apache Software Foundation + + Licensed under the Apache License, Version 2.0 (the License); + you may not use this file except in compliance with the License. + You may obtain a copy of the License at + + http://www.apache.org/licenses/LICENSE-2.0 + + Unless required by applicable law or agreed to in writing, software + distributed under the License is distributed on an AS IS BASIS, + WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. + See the License for the specific language governing permissions and + limitations under the License. +-- +!-- $Id$ -- !-- Created by htmlize-0.67 in css mode. -- html head @@ -71,6 +87,22 @@ /head body pre +span class=comment/* + * Copyright 2001-2004 The Apache Software Foundation. + * + * Licensed under the Apache License, Version 2.0 (the License); + * you may not use this file except in compliance with the License. + * You may obtain a copy of the License at + * + * http://www.apache.org/licenses/LICENSE-2.0 + * + * Unless required by applicable law or agreed to in writing, software + * distributed under the License is distributed on an AS IS BASIS, + * WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. + * See the License for the specific language governing permissions and + * limitations under the License. + *//span + span class=keywordpackage/span span class=jde-java-font-lock-packageorg/span.span class=jde-java-font-lock-packageapache/span.span class=jde-java-font-lock-packagefop/span.span class=jde-java-font-lock-packagedatatypes/span; span class=keywordimport/span span class=jde-java-font-lock-packageorg/span.span class=jde-java-font-lock-packageapache/span.span class=jde-java-font-lock-packagefop/span.span class=jde-java-font-lock-packagefo/span.span class=typePropertyConsts/span; @@ -80,18 +112,9 @@ span class=keywordimport/span span class=jde-java-font-lock-packageorg/span.span class=jde-java-font-lock-packageapache/span.span class=jde-java-font-lock-packagefop/span.span class=jde-java-font-lock-packagefo/span.span class=jde-java-font-lock-packageexpr/span.span class=typePropertyException/span; span class=keywordimport/span span class=jde-java-font-lock-packageorg/span.span class=jde-java-font-lock-packageapache/span.span class=jde-java-font-lock-packagefop/span.span class=jde-java-font-lock-packagedatatypes/span.span class=typePropertyValue/span; -span class=comment/* - * AbstractPropertyValue.java - * $Id$ - * - * Copyright (C) 2001 The Apache Software Foundation. All rights reserved. - * For details on use and redistribution please refer to the - * LICENSE file included with these sources. - * @author lt;a href=quot;mailto:[EMAIL PROTECTED]quot;gt;Peter B. Westlt;/agt; - * @version $Revision$ $Name$ - *//span span class=comment/** * Base abstract class for all property value types. + * @author lt;a href=quot;mailto:[EMAIL PROTECTED]quot;gt;Peter B. Westlt;/agt; *//span span class=jde-java-font-lock-modifierpublic/span span class=jde-java-font-lock-modifierabstract/span span class=keywordclass/span span class=function-name id=AbstractPropertyValueClassAbstractPropertyValue/span 1.2 +16 -0 xml-fop/src/documentation/content/design/alt.design/properties/AutoRestore.html Index
cvs commit: xml-fop/src/documentation/content/xdocs anttask.xml book.xml bugs.xml compiling.xml compliance.xml configuration.xml download.xml embedding.xml examples.xml extensions.xml faq.xml fo.xml fonts.xml gethelp.xml graphics.xml hyphenation.xml index.xml license.xml logocontest.xml maillist.xml news.xml output.xml pdfencryption.xml relnotes.xml resources.xml running.xml servlets.xml status.xml tabs.xml team.xml
jeremias2004/03/02 13:15:36 Modified:src/documentation/content/xdocs anttask.xml book.xml bugs.xml compiling.xml compliance.xml configuration.xml download.xml embedding.xml examples.xml extensions.xml faq.xml fo.xml fonts.xml gethelp.xml graphics.xml hyphenation.xml index.xml license.xml logocontest.xml maillist.xml news.xml output.xml pdfencryption.xml relnotes.xml resources.xml running.xml servlets.xml status.xml tabs.xml team.xml Log: Applied Apache License Version 2.0 by following the instructions at http://www.apache.org/dev/apply-license.html. Revision ChangesPath 1.9 +17 -1 xml-fop/src/documentation/content/xdocs/anttask.xml Index: anttask.xml === RCS file: /home/cvs/xml-fop/src/documentation/content/xdocs/anttask.xml,v retrieving revision 1.8 retrieving revision 1.9 diff -u -r1.8 -r1.9 --- anttask.xml 12 Nov 2003 15:11:59 - 1.8 +++ anttask.xml 2 Mar 2004 21:15:35 - 1.9 @@ -1,4 +1,20 @@ ?xml version=1.0 standalone=no? +!-- + Copyright 1999-2004 The Apache Software Foundation + + Licensed under the Apache License, Version 2.0 (the License); + you may not use this file except in compliance with the License. + You may obtain a copy of the License at + + http://www.apache.org/licenses/LICENSE-2.0 + + Unless required by applicable law or agreed to in writing, software + distributed under the License is distributed on an AS IS BASIS, + WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. + See the License for the specific language governing permissions and + limitations under the License. +-- +!-- $Id$ -- !DOCTYPE document PUBLIC -//APACHE//DTD Documentation V1.1//EN http://cvs.apache.org/viewcvs.cgi/*checkout*/xml-forrest/src/core/context/resources/schema/dtd/document-v12.dtd; 1.29 +64 -54xml-fop/src/documentation/content/xdocs/book.xml Index: book.xml === RCS file: /home/cvs/xml-fop/src/documentation/content/xdocs/book.xml,v retrieving revision 1.28 retrieving revision 1.29 diff -u -r1.28 -r1.29 --- book.xml 19 Dec 2003 01:08:42 - 1.28 +++ book.xml 2 Mar 2004 21:15:35 - 1.29 @@ -1,57 +1,67 @@ ?xml version=1.0 encoding=UTF-8? - !DOCTYPE book PUBLIC -//APACHE//DTD Cocoon Documentation Book V1.0//EN - http://cvs.apache.org/viewcvs.cgi/*checkout*/xml-cocoon2/src/documentation/xdocs/dtd/book-cocoon-v10.dtd; - - - book software=FOP -title=FOP -copyright=@year@ The Apache Software Foundation -xmlns:xlink=http://www.w3.org/1999/xlink; - -menu label=Home - menu-item label=Introduction href=index.html/ -/menu +!-- + Copyright 1999-2004 The Apache Software Foundation -menu label=Using FOP - menu-item label=Release Notes href=relnotes.html/ - menu-item label=Download href=download.html/ - menu-item label=Build href=compiling.html/ - menu-item label=Configure href=configuration.html/ - menu-item label=Run href=running.html/ - menu-item label=Embed href=embedding.html/ - menu-item label=Servlets href=servlets.html/ - menu-item label=Ant task href=anttask.html/ -/menu - -menu label=Features - menu-item label=Compliance href=compliance.html/ - menu-item label=Output Targets href=output.html/ - menu-item label=PDF encryption href=pdfencryption.html/ - menu-item label=Graphics href=graphics.html/ - menu-item label=Fonts href=fonts.html/ - menu-item label=Hyphenation href=hyphenation.html/ - menu-item label=Extensions href=extensions.html/ -/menu - -menu label=Resources - menu-item label=Getting Help href=gethelp.html/ - menu-item label=FAQs href=faq.html/ - menu-item label=XSL-FO href=fo.html/ - menu-item label=Examples href=examples.html/ - menu-item label=Mailing Lists href=maillist.html/ - menu-item label=Bugs href=bugs.html/ - menu-item label=Wiki href=http://nagoya.apache.org/wiki/apachewiki.cgi?FOPProjectPages/ - menu-item label=License href=license.html/ - menu-item label=Other href=resources.html/ -/menu - -menu label=Project - menu-item label=News href=news.html/ - menu-item label=Who We Are href=team.html/ - menu-item label=Status href=status.html/ - menu-item label=Logo contest href
cvs commit: xml-fop/src/documentation/content/xdocs team.xml
jeremias2004/03/02 13:20:51 Modified:src/documentation/content/xdocs team.xml Log: Updated my entry. Revision ChangesPath 1.28 +4 -5 xml-fop/src/documentation/content/xdocs/team.xml Index: team.xml === RCS file: /home/cvs/xml-fop/src/documentation/content/xdocs/team.xml,v retrieving revision 1.27 retrieving revision 1.28 diff -u -r1.27 -r1.28 --- team.xml 2 Mar 2004 21:15:35 - 1.27 +++ team.xml 2 Mar 2004 21:20:51 - 1.28 @@ -38,9 +38,8 @@ Born in 1978, he has been serving as an application developer for a small industrial company in Germany since 1999./li li id=jmlink href=mailto:[EMAIL PROTECTED]Jeremias M#x00E4;rki/link (JM) - is a software engineer from Lucerne, Switzerland. He is currently enjoying a longer period of - independence and is having fun working on open source projects like Apache FOP. He's also - the creator of fork href=http://www.krysalis.org/barcode;Krysalis Barcode/fork. + is a software engineer from Lucerne, Switzerland. He's also + the creator of fork href=http://barcode4j.krysalis.org;Barcode4J/fork. /li li id=gmlink href=mailto:[EMAIL PROTECTED]Glen Mazza/link (GM) is an information systems analyst with EDS in Arlington, Virginia, USA./li - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
cvs commit: xml-fop/src/documentation/content/xdocs resources.xml
jeremias2004/03/02 13:24:13 Modified:src/documentation/content/xdocs resources.xml Log: Updated info on Barcode4J Revision ChangesPath 1.35 +3 -3 xml-fop/src/documentation/content/xdocs/resources.xml Index: resources.xml === RCS file: /home/cvs/xml-fop/src/documentation/content/xdocs/resources.xml,v retrieving revision 1.34 retrieving revision 1.35 diff -u -r1.34 -r1.35 --- resources.xml 2 Mar 2004 21:15:35 - 1.34 +++ resources.xml 2 Mar 2004 21:24:13 - 1.35 @@ -142,7 +142,7 @@ li[software] TIFFRenderer is a renderer for outputting multi-page TIFF: jump href=http://www.tkachenko.com/fop/tiffrenderer.html;http://www.tkachenko.com/fop/tiffrenderer.html/jump (MPL)/li li[software] AFP Renderer / Batch Assembler for FOP: jump href=http://mypage.bluewin.ch/huanderegg/;http://mypage.bluewin.ch/huanderegg//jump (open source, license unclear)/li li[software] The jump href=http://mogwai.sourceforge.net;Mogwai Project/jump includes a renderer for FOP that generates output for Okidata dot matrix printers (GPL)./li - li[software] jump href=http://www.krysalis.org/barcode;Krysalis Barcode/jump is a barcode generator which can be used with FOP (Apache-style license)./li + li[software] jump href=http://barcode4j.krysalis.org;Barcode4J/jump (formerly Krysalis Barcode) is a barcode generator which can be used with FOP (Apache-style license)./li /ul /section section id=products-pdf - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
cvs commit: xml-fop/src/documentation/content/xdocs/design/alt.design/properties PropertyConsts-class.ehtml book.xml classes-overview.ehtml enumerated-values.ehtml getInitialValue.ehtml introduction.xml propertyExpressions.ehtml simple-properties.ehtml
jeremias2004/03/02 13:30:25 Modified:src/documentation/content/xdocs/design/alt.design/properties PropertyConsts-class.ehtml book.xml classes-overview.ehtml enumerated-values.ehtml getInitialValue.ehtml introduction.xml propertyExpressions.ehtml simple-properties.ehtml Log: Applied Apache License Version 2.0 by following the instructions at http://www.apache.org/dev/apply-license.html. Revision ChangesPath 1.6 +18 -2 xml-fop/src/documentation/content/xdocs/design/alt.design/properties/PropertyConsts-class.ehtml Index: PropertyConsts-class.ehtml === RCS file: /home/cvs/xml-fop/src/documentation/content/xdocs/design/alt.design/properties/PropertyConsts-class.ehtml,v retrieving revision 1.5 retrieving revision 1.6 diff -u -r1.5 -r1.6 --- PropertyConsts-class.ehtml17 Mar 2003 05:08:59 - 1.5 +++ PropertyConsts-class.ehtml2 Mar 2004 21:30:25 - 1.6 @@ -1,4 +1,20 @@ ?xml version=1.0? +!-- + Copyright 1999-2004 The Apache Software Foundation + + Licensed under the Apache License, Version 2.0 (the License); + you may not use this file except in compliance with the License. + You may obtain a copy of the License at + + http://www.apache.org/licenses/LICENSE-2.0 + + Unless required by applicable law or agreed to in writing, software + distributed under the License is distributed on an AS IS BASIS, + WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. + See the License for the specific language governing permissions and + limitations under the License. +-- +!-- $Id$ -- html body marginheight=0 marginwidth=0 topmargin=0 leftmargin=0 text=#00 bgcolor=#FF @@ -13,11 +29,11 @@ a href=#N10014Introduction/a /li /ul - + a name=N10014/a h3Introduction/h3 p - + span id = span00 /span a href=javascript:toggleCode( 'span00', 'PropertyConsts.html#PropertyConstsClass', '400', '100%' )This class/a, and the singleton object which is 1.6 +16 -0 xml-fop/src/documentation/content/xdocs/design/alt.design/properties/book.xml Index: book.xml === RCS file: /home/cvs/xml-fop/src/documentation/content/xdocs/design/alt.design/properties/book.xml,v retrieving revision 1.5 retrieving revision 1.6 diff -u -r1.5 -r1.6 --- book.xml 8 Mar 2003 13:52:43 - 1.5 +++ book.xml 2 Mar 2004 21:30:25 - 1.6 @@ -1,4 +1,20 @@ ?xml version=1.0 encoding=UTF-8? +!-- + Copyright 1999-2004 The Apache Software Foundation + + Licensed under the Apache License, Version 2.0 (the License); + you may not use this file except in compliance with the License. + You may obtain a copy of the License at + + http://www.apache.org/licenses/LICENSE-2.0 + + Unless required by applicable law or agreed to in writing, software + distributed under the License is distributed on an AS IS BASIS, + WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. + See the License for the specific language governing permissions and + limitations under the License. +-- +!-- $Id$ -- !DOCTYPE book PUBLIC -//APACHE//DTD Cocoon Documentation Book V1.0//EN http://cvs.apache.org/viewcvs.cgi/*checkout*/xml-cocoon2/src/documentation/xdocs/dtd/book-cocoon-v10.dtd; 1.5 +17 -1 xml-fop/src/documentation/content/xdocs/design/alt.design/properties/classes-overview.ehtml Index: classes-overview.ehtml === RCS file: /home/cvs/xml-fop/src/documentation/content/xdocs/design/alt.design/properties/classes-overview.ehtml,v retrieving revision 1.4 retrieving revision 1.5 diff -u -r1.4 -r1.5 --- classes-overview.ehtml12 Mar 2003 14:22:02 - 1.4 +++ classes-overview.ehtml2 Mar 2004 21:30:25 - 1.5 @@ -1,4 +1,20 @@ ?xml version=1.0? +!-- + Copyright 1999-2004 The Apache Software Foundation + + Licensed under the Apache License, Version 2.0 (the License); + you may not use this file except in compliance with the License. + You may obtain a copy of the License at + + http://www.apache.org/licenses/LICENSE-2.0 + + Unless required by applicable law or agreed to in writing, software + distributed under the License is distributed on an AS IS BASIS, + WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. + See the License for the specific language governing permissions and + limitations under the License. +-- +!-- $Id$ -- html body marginheight= 0
cvs commit: xml-fop/src/documentation/content/xdocs/design/alt.design PropNames-png.xml alt-properties.xml book.xml compound-properties.xml coroutines.xml footnotes.xml galleys.xml index.xml keeps.xml properties-classes.xml spaces.xml traits.xml user-agent-refs.xml xml-parsing.ehtml
jeremias2004/03/02 13:30:59 Modified:src/documentation/content/xdocs/design/alt.design PropNames-png.xml alt-properties.xml book.xml compound-properties.xml coroutines.xml footnotes.xml galleys.xml index.xml keeps.xml properties-classes.xml spaces.xml traits.xml user-agent-refs.xml xml-parsing.ehtml Log: Applied Apache License Version 2.0 by following the instructions at http://www.apache.org/dev/apply-license.html. Revision ChangesPath 1.3 +16 -0 xml-fop/src/documentation/content/xdocs/design/alt.design/PropNames-png.xml Index: PropNames-png.xml === RCS file: /home/cvs/xml-fop/src/documentation/content/xdocs/design/alt.design/PropNames-png.xml,v retrieving revision 1.2 retrieving revision 1.3 diff -u -r1.2 -r1.3 --- PropNames-png.xml 12 Nov 2003 15:24:52 - 1.2 +++ PropNames-png.xml 2 Mar 2004 21:30:58 - 1.3 @@ -1,4 +1,20 @@ ?xml version=1.0 standalone=no? +!-- + Copyright 1999-2004 The Apache Software Foundation + + Licensed under the Apache License, Version 2.0 (the License); + you may not use this file except in compliance with the License. + You may obtain a copy of the License at + + http://www.apache.org/licenses/LICENSE-2.0 + + Unless required by applicable law or agreed to in writing, software + distributed under the License is distributed on an AS IS BASIS, + WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. + See the License for the specific language governing permissions and + limitations under the License. +-- +!-- $Id$ -- !DOCTYPE document PUBLIC -//APACHE//DTD Documentation V1.1//EN http://cvs.apache.org/viewcvs.cgi/*checkout*/xml-forrest/src/core/context/resources/schema/dtd/document-v12.dtd; 1.5 +16 -0 xml-fop/src/documentation/content/xdocs/design/alt.design/alt-properties.xml Index: alt-properties.xml === RCS file: /home/cvs/xml-fop/src/documentation/content/xdocs/design/alt.design/alt-properties.xml,v retrieving revision 1.4 retrieving revision 1.5 diff -u -r1.4 -r1.5 --- alt-properties.xml12 Nov 2003 15:24:52 - 1.4 +++ alt-properties.xml2 Mar 2004 21:30:58 - 1.5 @@ -1,4 +1,20 @@ ?xml version=1.0 standalone=no? +!-- + Copyright 1999-2004 The Apache Software Foundation + + Licensed under the Apache License, Version 2.0 (the License); + you may not use this file except in compliance with the License. + You may obtain a copy of the License at + + http://www.apache.org/licenses/LICENSE-2.0 + + Unless required by applicable law or agreed to in writing, software + distributed under the License is distributed on an AS IS BASIS, + WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. + See the License for the specific language governing permissions and + limitations under the License. +-- +!-- $Id$ -- !DOCTYPE document PUBLIC -//APACHE//DTD Documentation V1.1//EN http://cvs.apache.org/viewcvs.cgi/*checkout*/xml-forrest/src/core/context/resources/schema/dtd/document-v12.dtd; 1.9 +16 -0 xml-fop/src/documentation/content/xdocs/design/alt.design/book.xml Index: book.xml === RCS file: /home/cvs/xml-fop/src/documentation/content/xdocs/design/alt.design/book.xml,v retrieving revision 1.8 retrieving revision 1.9 diff -u -r1.8 -r1.9 --- book.xml 8 Mar 2003 13:51:43 - 1.8 +++ book.xml 2 Mar 2004 21:30:58 - 1.9 @@ -1,4 +1,20 @@ ?xml version=1.0 encoding=UTF-8? +!-- + Copyright 1999-2004 The Apache Software Foundation + + Licensed under the Apache License, Version 2.0 (the License); + you may not use this file except in compliance with the License. + You may obtain a copy of the License at + + http://www.apache.org/licenses/LICENSE-2.0 + + Unless required by applicable law or agreed to in writing, software + distributed under the License is distributed on an AS IS BASIS, + WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. + See the License for the specific language governing permissions and + limitations under the License. +-- +!-- $Id$ -- !DOCTYPE book PUBLIC -//APACHE//DTD Cocoon Documentation Book V1.0//EN http://cvs.apache.org/viewcvs.cgi/*checkout*/xml-cocoon2/src/documentation/xdocs/dtd/book-cocoon-v10.dtd; 1.4 +16 -0 xml-fop/src/documentation/content/xdocs/design/alt.design/compound-properties.xml Index: compound-properties.xml
cvs commit: xml-fop/src/documentation/content/xdocs/design areas.xml book.xml breakpos.xml embedding.xml extending.xml fotree.xml images.xml index.xml layout.xml optimise.xml parsing.xml pdf-library.xml properties.xml renderers.xml startup.xml svg.xml useragent.xml
jeremias2004/03/02 13:32:04 Modified:src/documentation/content/xdocs/design areas.xml book.xml breakpos.xml embedding.xml extending.xml fotree.xml images.xml index.xml layout.xml optimise.xml parsing.xml pdf-library.xml properties.xml renderers.xml startup.xml svg.xml useragent.xml Log: Applied Apache License Version 2.0 by following the instructions at http://www.apache.org/dev/apply-license.html. Revision ChangesPath 1.16 +17 -1 xml-fop/src/documentation/content/xdocs/design/areas.xml Index: areas.xml === RCS file: /home/cvs/xml-fop/src/documentation/content/xdocs/design/areas.xml,v retrieving revision 1.15 retrieving revision 1.16 diff -u -r1.15 -r1.16 --- areas.xml 12 Nov 2003 15:24:51 - 1.15 +++ areas.xml 2 Mar 2004 21:32:03 - 1.16 @@ -1,4 +1,20 @@ ?xml version=1.0 standalone=no? +!-- + Copyright 1999-2004 The Apache Software Foundation + + Licensed under the Apache License, Version 2.0 (the License); + you may not use this file except in compliance with the License. + You may obtain a copy of the License at + + http://www.apache.org/licenses/LICENSE-2.0 + + Unless required by applicable law or agreed to in writing, software + distributed under the License is distributed on an AS IS BASIS, + WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. + See the License for the specific language governing permissions and + limitations under the License. +-- +!-- $Id$ -- !DOCTYPE document PUBLIC -//APACHE//DTD Documentation V1.1//EN http://cvs.apache.org/viewcvs.cgi/*checkout*/xml-forrest/src/core/context/resources/schema/dtd/document-v12.dtd; document 1.21 +16 -0 xml-fop/src/documentation/content/xdocs/design/book.xml Index: book.xml === RCS file: /home/cvs/xml-fop/src/documentation/content/xdocs/design/book.xml,v retrieving revision 1.20 retrieving revision 1.21 diff -u -r1.20 -r1.21 --- book.xml 30 Apr 2003 18:54:41 - 1.20 +++ book.xml 2 Mar 2004 21:32:03 - 1.21 @@ -1,4 +1,20 @@ ?xml version=1.0 encoding=UTF-8? +!-- + Copyright 1999-2004 The Apache Software Foundation + + Licensed under the Apache License, Version 2.0 (the License); + you may not use this file except in compliance with the License. + You may obtain a copy of the License at + + http://www.apache.org/licenses/LICENSE-2.0 + + Unless required by applicable law or agreed to in writing, software + distributed under the License is distributed on an AS IS BASIS, + WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. + See the License for the specific language governing permissions and + limitations under the License. +-- +!-- $Id$ -- !DOCTYPE book PUBLIC -//APACHE//DTD Cocoon Documentation Book V1.0//EN http://cvs.apache.org/viewcvs.cgi/*checkout*/xml-cocoon2/src/documentation/xdocs/dtd/book-cocoon-v10.dtd; 1.7 +17 -1 xml-fop/src/documentation/content/xdocs/design/breakpos.xml Index: breakpos.xml === RCS file: /home/cvs/xml-fop/src/documentation/content/xdocs/design/breakpos.xml,v retrieving revision 1.6 retrieving revision 1.7 diff -u -r1.6 -r1.7 --- breakpos.xml 12 Nov 2003 15:24:51 - 1.6 +++ breakpos.xml 2 Mar 2004 21:32:03 - 1.7 @@ -1,4 +1,20 @@ ?xml version=1.0 standalone=no? +!-- + Copyright 1999-2004 The Apache Software Foundation + + Licensed under the Apache License, Version 2.0 (the License); + you may not use this file except in compliance with the License. + You may obtain a copy of the License at + + http://www.apache.org/licenses/LICENSE-2.0 + + Unless required by applicable law or agreed to in writing, software + distributed under the License is distributed on an AS IS BASIS, + WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. + See the License for the specific language governing permissions and + limitations under the License. +-- +!-- $Id$ -- !DOCTYPE document PUBLIC -//APACHE//DTD Documentation V1.1//EN http://cvs.apache.org/viewcvs.cgi/*checkout*/xml-forrest/src/core/context/resources/schema/dtd/document-v12.dtd; 1.8 +17 -1 xml-fop/src/documentation/content/xdocs/design/embedding.xml Index: embedding.xml === RCS file: /home/cvs/xml-fop/src/documentation/content/xdocs/design/embedding.xml,v retrieving revision 1.7 retrieving revision 1.8 diff -u -r1.7 -r1.8 --- embedding.xml 12 Nov 2003
cvs commit: xml-fop/src/documentation/content/xdocs/dev/svg images.svg link.svg paints.svg text.svg transparency.svg
jeremias2004/03/02 13:41:13 Modified:src/documentation/content/xdocs/dev api-doc.xml book.xml conventions.xml doc.xml extensions.xml faq.xml fonts.xml implement.xml index.xml release.xml rtflib.xml svg.xml testing.xml tools.xml src/documentation/content/xdocs/dev/fo embedding.fo src/documentation/content/xdocs/dev/svg images.svg link.svg paints.svg text.svg transparency.svg Log: Applied Apache License Version 2.0 by following the instructions at http://www.apache.org/dev/apply-license.html. Revision ChangesPath 1.6 +17 -1 xml-fop/src/documentation/content/xdocs/dev/api-doc.xml Index: api-doc.xml === RCS file: /home/cvs/xml-fop/src/documentation/content/xdocs/dev/api-doc.xml,v retrieving revision 1.5 retrieving revision 1.6 diff -u -r1.5 -r1.6 --- api-doc.xml 12 Nov 2003 15:24:53 - 1.5 +++ api-doc.xml 2 Mar 2004 21:41:12 - 1.6 @@ -1,4 +1,20 @@ ?xml version=1.0 encoding=UTF-8? +!-- + Copyright 1999-2004 The Apache Software Foundation + + Licensed under the Apache License, Version 2.0 (the License); + you may not use this file except in compliance with the License. + You may obtain a copy of the License at + + http://www.apache.org/licenses/LICENSE-2.0 + + Unless required by applicable law or agreed to in writing, software + distributed under the License is distributed on an AS IS BASIS, + WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. + See the License for the specific language governing permissions and + limitations under the License. +-- +!-- $Id$ -- !DOCTYPE document PUBLIC -//APACHE//DTD Documentation V1.1//EN http://cvs.apache.org/viewcvs.cgi/*checkout*/xml-forrest/src/core/context/resources/schema/dtd/document-v12.dtd; document 1.30 +16 -0 xml-fop/src/documentation/content/xdocs/dev/book.xml Index: book.xml === RCS file: /home/cvs/xml-fop/src/documentation/content/xdocs/dev/book.xml,v retrieving revision 1.29 retrieving revision 1.30 diff -u -r1.29 -r1.30 --- book.xml 7 Jul 2003 04:04:55 - 1.29 +++ book.xml 2 Mar 2004 21:41:12 - 1.30 @@ -1,4 +1,20 @@ ?xml version=1.0 encoding=UTF-8? +!-- + Copyright 1999-2004 The Apache Software Foundation + + Licensed under the Apache License, Version 2.0 (the License); + you may not use this file except in compliance with the License. + You may obtain a copy of the License at + + http://www.apache.org/licenses/LICENSE-2.0 + + Unless required by applicable law or agreed to in writing, software + distributed under the License is distributed on an AS IS BASIS, + WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. + See the License for the specific language governing permissions and + limitations under the License. +-- +!-- $Id$ -- !DOCTYPE book PUBLIC -//APACHE//DTD Cocoon Documentation Book V1.0//EN http://cvs.apache.org/viewcvs.cgi/*checkout*/xml-cocoon2/src/documentation/xdocs/dtd/book-cocoon-v10.dtd; 1.8 +17 -1 xml-fop/src/documentation/content/xdocs/dev/conventions.xml Index: conventions.xml === RCS file: /home/cvs/xml-fop/src/documentation/content/xdocs/dev/conventions.xml,v retrieving revision 1.7 retrieving revision 1.8 diff -u -r1.7 -r1.8 --- conventions.xml 12 Nov 2003 15:24:53 - 1.7 +++ conventions.xml 2 Mar 2004 21:41:12 - 1.8 @@ -1,4 +1,20 @@ ?xml version=1.0 encoding=UTF-8? +!-- + Copyright 1999-2004 The Apache Software Foundation + + Licensed under the Apache License, Version 2.0 (the License); + you may not use this file except in compliance with the License. + You may obtain a copy of the License at + + http://www.apache.org/licenses/LICENSE-2.0 + + Unless required by applicable law or agreed to in writing, software + distributed under the License is distributed on an AS IS BASIS, + WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. + See the License for the specific language governing permissions and + limitations under the License. +-- +!-- $Id$ -- !DOCTYPE document PUBLIC -//APACHE//DTD Documentation V1.1//EN http://cvs.apache.org/viewcvs.cgi/*checkout*/xml-forrest/src/core/context/resources/schema/dtd/document-v12.dtd; document 1.7 +17 -1 xml-fop/src/documentation/content/xdocs/dev/doc.xml Index: doc.xml === RCS file: /home/cvs/xml-fop/src/documentation/content/xdocs/dev
cvs commit: xml-fop/src/documentation/content/xdocs/fo align.fo align2.fo blocks.ent embed.fo fonts.fo size.fo
jeremias2004/03/02 13:42:51 Modified:src/documentation/content/xdocs/fo align.fo align2.fo blocks.ent embed.fo fonts.fo size.fo Log: Applied Apache License Version 2.0 by following the instructions at http://www.apache.org/dev/apply-license.html. Revision ChangesPath 1.3 +15 -0 xml-fop/src/documentation/content/xdocs/fo/align.fo Index: align.fo === RCS file: /home/cvs/xml-fop/src/documentation/content/xdocs/fo/align.fo,v retrieving revision 1.2 retrieving revision 1.3 diff -u -r1.2 -r1.3 --- align.fo 29 Nov 2002 22:00:32 - 1.2 +++ align.fo 2 Mar 2004 21:42:51 - 1.3 @@ -1,5 +1,20 @@ ?xml version=1.0 encoding=utf-8? +!-- + Copyright 1999-2004 The Apache Software Foundation + Licensed under the Apache License, Version 2.0 (the License); + you may not use this file except in compliance with the License. + You may obtain a copy of the License at + + http://www.apache.org/licenses/LICENSE-2.0 + + Unless required by applicable law or agreed to in writing, software + distributed under the License is distributed on an AS IS BASIS, + WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. + See the License for the specific language governing permissions and + limitations under the License. +-- +!-- $Id$ -- fo:root font-family=Times Roman font-size=12pt text-align=center xmlns:fo=http://www.w3.org/1999/XSL/Format; fo:layout-master-set 1.3 +15 -0 xml-fop/src/documentation/content/xdocs/fo/align2.fo Index: align2.fo === RCS file: /home/cvs/xml-fop/src/documentation/content/xdocs/fo/align2.fo,v retrieving revision 1.2 retrieving revision 1.3 diff -u -r1.2 -r1.3 --- align2.fo 29 Nov 2002 22:00:32 - 1.2 +++ align2.fo 2 Mar 2004 21:42:51 - 1.3 @@ -1,5 +1,20 @@ ?xml version=1.0 encoding=utf-8? +!-- + Copyright 1999-2004 The Apache Software Foundation + Licensed under the Apache License, Version 2.0 (the License); + you may not use this file except in compliance with the License. + You may obtain a copy of the License at + + http://www.apache.org/licenses/LICENSE-2.0 + + Unless required by applicable law or agreed to in writing, software + distributed under the License is distributed on an AS IS BASIS, + WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. + See the License for the specific language governing permissions and + limitations under the License. +-- +!-- $Id$ -- fo:root font-family=Times Roman font-size=12pt text-align=center xmlns:fo=http://www.w3.org/1999/XSL/Format; fo:layout-master-set 1.2 +16 -0 xml-fop/src/documentation/content/xdocs/fo/blocks.ent Index: blocks.ent === RCS file: /home/cvs/xml-fop/src/documentation/content/xdocs/fo/blocks.ent,v retrieving revision 1.1 retrieving revision 1.2 diff -u -r1.1 -r1.2 --- blocks.ent12 Nov 2002 09:15:53 - 1.1 +++ blocks.ent2 Mar 2004 21:42:51 - 1.2 @@ -1,3 +1,19 @@ +!-- + Copyright 1999-2004 The Apache Software Foundation + + Licensed under the Apache License, Version 2.0 (the License); + you may not use this file except in compliance with the License. + You may obtain a copy of the License at + + http://www.apache.org/licenses/LICENSE-2.0 + + Unless required by applicable law or agreed to in writing, software + distributed under the License is distributed on an AS IS BASIS, + WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. + See the License for the specific language governing permissions and + limitations under the License. +-- +!-- $Id$ -- svg xmlns=http://www.w3.org/2000/svg; width=100 height=100 rect x=0 y=0 width=25 height=25 style=fill:red/ 1.3 +16 -0 xml-fop/src/documentation/content/xdocs/fo/embed.fo Index: embed.fo === RCS file: /home/cvs/xml-fop/src/documentation/content/xdocs/fo/embed.fo,v retrieving revision 1.2 retrieving revision 1.3 diff -u -r1.2 -r1.3 --- embed.fo 29 Nov 2002 22:00:32 - 1.2 +++ embed.fo 2 Mar 2004 21:42:51 - 1.3 @@ -1,4 +1,20 @@ ?xml version=1.0 encoding=utf-8? +!-- + Copyright 1999-2004 The Apache Software Foundation + + Licensed under the Apache License, Version 2.0 (the License); + you may not use this file except in compliance with the License. + You may obtain a copy of the License at + + http://www.apache.org/licenses/LICENSE-2.0 + + Unless required by applicable law or agreed to in writing, software
cvs commit: xml-fop/src/documentation/content/xdocs compliance.xml
cbowditch2004/03/01 07:38:25 Modified:src/documentation/content/xdocs compliance.xml Log: corrected compliance for baseline-shift and vertical-align properties Revision ChangesPath 1.25 +6 -2 xml-fop/src/documentation/content/xdocs/compliance.xml Index: compliance.xml === RCS file: /home/cvs/xml-fop/src/documentation/content/xdocs/compliance.xml,v retrieving revision 1.24 retrieving revision 1.25 diff -u -r1.24 -r1.25 --- compliance.xml12 Nov 2003 15:11:59 - 1.24 +++ compliance.xml1 Mar 2004 15:38:25 - 1.25 @@ -274,7 +274,9 @@ level-2 name=Area Alignment Properties citation=§7.13 extURL=slice7.html#area-alignment ref-name=areaalign level-3 name=alignment-adjust citation=§7.13.1 extURL=slice7.html#alignment-adjust compliance-level=1 comply=no/ level-3 name=alignment-baseline citation=§7.13.2 extURL=slice7.html#alignment-baseline compliance-level=1 comply=no/ - level-3 name=baseline-shift citation=§7.13.3 extURL=slice7.html#baseline-shift compliance-level=1 comply=no/ + level-3 name=baseline-shift citation=§7.13.3 extURL=slice7.html#baseline-shift compliance-level=1 comply=partial +commentOnly values super and sub have been implemented./comment + /level-3 level-3 name=display-align citation=§7.13.4 extURL=slice7.html#display-align compliance-level=2 comply=partial commentImplemented only for table-cell and block-container./comment commentFor table-cell, the height attribute must be set for the parent table-row; setting the height of the table or the table-cell results in vertical centering having no effect. @@ -502,7 +504,9 @@ commentquot;inheritquot; not handled/comment /level-3 level-3 name=size citation=§7.29.21 extURL=slice7.html#size compliance-level=3 comply=no/ - level-3 name=vertical-align citation=§7.29.22 extURL=slice7.html#vertical-align compliance-level=3 comply=no/ + level-3 name=vertical-align citation=§7.29.22 extURL=slice7.html#vertical-align compliance-level=3 comply=partial +commentOnly works as a shorthand for baseline-shift property./comment + /level-3 level-3 name=white-space citation=§7.29.23 extURL=slice7.html#white-space compliance-level=3 comply=no/ level-3 name=xml:lang citation=§7.29.24 extURL=slice7.html#xml:lang compliance-level=3 comply=no/ /level-2 - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: cvs commit: xml-fop/src/documentation/content/xdocs team.xml
[EMAIL PROTECTED] wrote: removed former contributor section in favor of going back to giving credit within source files. Uh, oh. That's not supposed to be a change anybody can make on a whim. J.Pietschmann
Re: cvs commit: xml-fop/src/documentation/content/xdocs team.xml
I agree. Over at Jakarta (especially Commons) this discussion was renewed lately. Bottomline is that it's better (and safer for the ASF) to remove author tags from the sources and credit contributors in changes files, CVS messages and on websites. All source files should probably have one author tag pointing to the developer mailing list of the respective project. Please see: http://nagoya.apache.org/eyebrowse/[EMAIL PROTECTED]by=threadfrom=572799 That said I'm in favor for: - removing all author tags (and other such markings) in the source files - adding a FOP Dev Team author tag to every source file. - adding each name that is removed somewhere to a list of contributors (hopefully and if possible with a short note about the area of their contribution). - adding contributor names on demand (for those who only have their names in CVS messages) On 20.01.2004 18:37:51 J.Pietschmann wrote: [EMAIL PROTECTED] wrote: removed former contributor section in favor of going back to giving credit within source files. Uh, oh. That's not supposed to be a change anybody can make on a whim. Jeremias Maerki
cvs commit: xml-fop/src/documentation/content/xdocs team.xml
gmazza 2004/01/19 15:56:50 Modified:src/documentation/content/xdocs team.xml Log: Updated team page--moved Finn, Andreas, Chris and Peter to active status; set Victor and Keiron to inactive status, removed former contributor section in favor of going back to giving credit within source files. Revision ChangesPath 1.25 +22 -31xml-fop/src/documentation/content/xdocs/team.xml Index: team.xml === RCS file: /home/cvs/xml-fop/src/documentation/content/xdocs/team.xml,v retrieving revision 1.24 retrieving revision 1.25 diff -u -r1.24 -r1.25 --- team.xml 1 Jan 2004 18:31:03 - 1.24 +++ team.xml 19 Jan 2004 23:56:50 - 1.25 @@ -12,8 +12,14 @@ section id=commit-active titleActive Committers/title ul +lilink href=mailto:[EMAIL PROTECTED]Finn Bock/link (FB)/li +lilink href=mailto:[EMAIL PROTECTED]Chris Bowditch/link (CB)/li +lilink href=mailto:[EMAIL PROTECTED]Andreas Delmelle/link (AD)/li li id=cglink href=mailto:[EMAIL PROTECTED]Christian Geisert/link (CG)/li -li id=klllink href=mailto:[EMAIL PROTECTED]Keiron Liddle/link (KLL)/li +lilink href=mailto:[EMAIL PROTECTED]Peter Herweg/link (PH) is helping to +integrate the jfor project's RTF support into the upcoming FOP 1.0 version. +Born in 1978, he has been serving as an application developer for a small +industrial company in Germany since 1999./li li id=jmlink href=mailto:[EMAIL PROTECTED]Jeremias M#x00E4;rki/link (JM) is a software engineer from Lucerne, Switzerland. He is currently enjoying a longer period of independence and is having fun working on open source projects like Apache FOP. He's also @@ -21,10 +27,6 @@ /li li id=gmlink href=mailto:[EMAIL PROTECTED]Glen Mazza/link (GM) is an information systems analyst with EDS in Arlington, Virginia, USA./li -li id=wvmlink href=mailto:[EMAIL PROTECTED]Victor Mote/link (WVM) is the founder and -manager of fork href=http://www.outfitr.com;Enterprise Outfitters/fork, a business -software company, and of fork href=http://www.portagepub.com;Portage Publications/fork, -a republisher of old documents. Both are located in Colorado Springs, Colorado, USA./li li id=jplink href=mailto:[EMAIL PROTECTED]J#x00F6;rg Pietschmann/link (JP)/li li id=otlink href=mailto:[EMAIL PROTECTED]Oleg Tkachenko/link (OT)/li li id=pbwlink href=mailto:[EMAIL PROTECTED]Peter B. West/link (PBW)/li @@ -38,13 +40,6 @@ Newfoundland. While developing a taste for good seafood, he still isn't ready for seal flipper (even if it's fresh). He is currently assisting the FOP project on memory and performance issues./li -lilink href=mailto:[EMAIL PROTECTED]Finn Bock/link/li -lilink href=mailto:[EMAIL PROTECTED]Chris Bowditch/link/li -lilink href=mailto:[EMAIL PROTECTED]Andreas Delmelle/link/li -lilink href=mailto:[EMAIL PROTECTED]Peter Herweg/link is helping to -integrate the jfor project's RTF support into the upcoming FOP 1.0 version. -Born in 1978, he has been serving as an application developer for a small -industrial company in Germany since 1999./li lilink href=mailto:[EMAIL PROTECTED]Clay Leeds/link is a web/WAP/Palm developer from Laguna Beach, California, USA. A recent XML/XSL-FO convert, he has been nit-picking FAQs amp; assorted web @@ -72,30 +67,26 @@ li id=sglink href=mailto:[EMAIL PROTECTED]Stanislav Gorkhover/link/li li id=fjlink href=mailto:[EMAIL PROTECTED]Fotis Jannidis/link/li li id=kllink href=mailto:[EMAIL PROTECTED]Karen Lease/link/li +li id=klllink href=mailto:[EMAIL PROTECTED]Keiron Liddle/link/li +li id=wvmlink href=mailto:[EMAIL PROTECTED]Victor Mote/link/li li id=jnlink href=mailto:[EMAIL PROTECTED]Jordan Naftolin/link/li li id=aslink href=mailto:[EMAIL PROTECTED]Arved Sandstrom/link/li li id=eslink href=mailto:[EMAIL PROTECTED]Eric Schaeffer/link/li li id=awlink href=mailto:[EMAIL PROTECTED]Art Welch/link/li /ul /section -section id=contribute-former - titleFormer Contributors/title - ul -li id=mllink href=mailto:[EMAIL PROTECTED]Mark Lillywhite/link/li - /ul -/section section id=expertise titleAreas of Expertise/title table tr th/ thCG /th - thKLL/th - thJM /th - thGM /th - thWVM/th - thJP /th - thOT /th + thFB/th
Re: cvs commit: xml-fop/src/documentation/content/xdocs team.xml
[EMAIL PROTECTED] wrote: gmazza 2004/01/19 15:56:50 Modified:src/documentation/content/xdocs team.xml Log: Updated team page--moved Finn, Andreas, Chris and Peter to active status; set Victor and Keiron to inactive status, removed former contributor section in favor of going back to giving credit within source files. I'm sorry that I didn't contribute to the discussion on this, but I think that Mark Lillywhite deserves an honourable mention on the web site. He saved Fop for many users by introducing page-sequence formatting. Peter -- Peter B. West http://www.powerup.com.au/~pbwest/resume.html
cvs commit: xml-fop/src/documentation/content/xdocs news.xml
gmazza 2004/01/11 17:26:59 Modified:src/documentation/content/xdocs news.xml Log: News page updates. Revision ChangesPath 1.17 +13 -1 xml-fop/src/documentation/content/xdocs/news.xml Index: news.xml === RCS file: /home/cvs/xml-fop/src/documentation/content/xdocs/news.xml,v retrieving revision 1.16 retrieving revision 1.17 diff -u -r1.16 -r1.17 --- news.xml 12 Nov 2003 15:11:59 - 1.16 +++ news.xml 12 Jan 2004 01:26:58 - 1.17 @@ -9,6 +9,18 @@ /header body section + title10 January 2004 - New Committers/title + pWelcome Chris Bowditch and Andreas Delmelle!/p +/section +section + title4 January 2004 - New Committer/title + pWelcome Finn Bock!/p +/section +section + title29 November 2003 - New Committer/title + pWelcome Peter Herweg!/p +/section +section title18 July 2003 FOP 0.20.5 released/title pChanges since 0.20.4 include:/p ul - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
cvs commit: xml-fop/src/documentation/content/xdocs team.xml
gmazza 2004/01/01 10:31:03 Modified:src/documentation/content/xdocs team.xml Log: Changed jumps to forks (=open new window on links) on team page. Revision ChangesPath 1.24 +7 -6 xml-fop/src/documentation/content/xdocs/team.xml Index: team.xml === RCS file: /home/cvs/xml-fop/src/documentation/content/xdocs/team.xml,v retrieving revision 1.23 retrieving revision 1.24 diff -u -r1.23 -r1.24 --- team.xml 31 Dec 2003 04:17:34 - 1.23 +++ team.xml 1 Jan 2004 18:31:03 - 1.24 @@ -22,8 +22,8 @@ li id=gmlink href=mailto:[EMAIL PROTECTED]Glen Mazza/link (GM) is an information systems analyst with EDS in Arlington, Virginia, USA./li li id=wvmlink href=mailto:[EMAIL PROTECTED]Victor Mote/link (WVM) is the founder and -manager of jump href=http://www.outfitr.com;Enterprise Outfitters/jump, a business -software company, and of jump href=http://www.portagepub.com;Portage Publications/jump, +manager of fork href=http://www.outfitr.com;Enterprise Outfitters/fork, a business +software company, and of fork href=http://www.portagepub.com;Portage Publications/fork, a republisher of old documents. Both are located in Colorado Springs, Colorado, USA./li li id=jplink href=mailto:[EMAIL PROTECTED]J#x00F6;rg Pietschmann/link (JP)/li li id=otlink href=mailto:[EMAIL PROTECTED]Oleg Tkachenko/link (OT)/li @@ -53,13 +53,14 @@ !-- Simon prefers the mail address with AT, to stop spam, etc. -- lilink href=mailto:spepping AT leverkruid.nlSimon Pepping/link is a TeX/LaTeX and XML expert with Elsevier at its -Amsterdam office. See his jump href=http://www.leverkruid.nl;home -page/jump for some of his private projects./li +Amsterdam office. See his fork href=http://www.leverkruid.nl;home +page/fork for some of his private projects./li /ul /section section id=founder titleFounder/title - pFOP was originally created and donated to the Apache Software Foundation by link href=mailto:[EMAIL PROTECTED]James Tauber/link. Information about him can be found at jump href=http://www.jtauber.com;his website/jump./p + pFOP was originally created and donated to the Apache Software Foundation by link href=mailto:[EMAIL PROTECTED]James Tauber/link. + Information about him can be found at fork href=http://www.jtauber.com;his website/fork./p /section section id=commit-inactive titleInactive Committers/title - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
cvs commit: xml-fop/src/documentation/content/xdocs team.xml
gmazza 2003/12/30 20:17:34 Modified:src/documentation/content/xdocs team.xml Log: XML bug on team page. Revision ChangesPath 1.23 +1 -2 xml-fop/src/documentation/content/xdocs/team.xml Index: team.xml === RCS file: /home/cvs/xml-fop/src/documentation/content/xdocs/team.xml,v retrieving revision 1.22 retrieving revision 1.23 diff -u -r1.22 -r1.23 --- team.xml 28 Dec 2003 19:01:52 - 1.22 +++ team.xml 31 Dec 2003 04:17:34 - 1.23 @@ -55,7 +55,6 @@ is a TeX/LaTeX and XML expert with Elsevier at its Amsterdam office. See his jump href=http://www.leverkruid.nl;home page/jump for some of his private projects./li - /li /ul /section section id=founder - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
cvs commit: xml-fop/src/documentation/content/xdocs team.xml
gmazza 2003/12/28 11:01:52 Modified:src/documentation/content/xdocs team.xml Log: Added Simon Pepping to contributors list. Revision ChangesPath 1.22 +7 -1 xml-fop/src/documentation/content/xdocs/team.xml Index: team.xml === RCS file: /home/cvs/xml-fop/src/documentation/content/xdocs/team.xml,v retrieving revision 1.21 retrieving revision 1.22 diff -u -r1.21 -r1.22 --- team.xml 19 Dec 2003 01:08:42 - 1.21 +++ team.xml 28 Dec 2003 19:01:52 - 1.22 @@ -50,6 +50,12 @@ recent XML/XSL-FO convert, he has been nit-picking FAQs amp; assorted web pages since his first webmaster position @brain.com in 1996. Most important creation? Jeremy Logan Leeds was born June 18, 2002./li +!-- Simon prefers the mail address with AT, to stop spam, etc. -- + lilink href=mailto:spepping AT leverkruid.nlSimon Pepping/link +is a TeX/LaTeX and XML expert with Elsevier at its +Amsterdam office. See his jump href=http://www.leverkruid.nl;home +page/jump for some of his private projects./li + /li /ul /section section id=founder - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
cvs commit: xml-fop/src/documentation/content/xdocs book.xml team.xml
gmazza 2003/12/18 17:08:42 Modified:src/documentation/content/xdocs book.xml team.xml Log: Updates to team page. Revision ChangesPath 1.28 +2 -2 xml-fop/src/documentation/content/xdocs/book.xml Index: book.xml === RCS file: /home/cvs/xml-fop/src/documentation/content/xdocs/book.xml,v retrieving revision 1.27 retrieving revision 1.28 diff -u -r1.27 -r1.28 --- book.xml 26 Nov 2003 01:12:46 - 1.27 +++ book.xml 19 Dec 2003 01:08:42 - 1.28 @@ -47,11 +47,11 @@ menu label=Project menu-item label=News href=news.html/ - menu-item label=Logo contest href=logocontest.html/ + menu-item label=Who We Are href=team.html/ menu-item label=Status href=status.html/ + menu-item label=Logo contest href=logocontest.html/ menu-item label=Changes href=changes.html/ menu-item label=Todo href=todo.html/ - menu-item label=Team href=team.html/ /menu /book 1.21 +13 -6 xml-fop/src/documentation/content/xdocs/team.xml Index: team.xml === RCS file: /home/cvs/xml-fop/src/documentation/content/xdocs/team.xml,v retrieving revision 1.20 retrieving revision 1.21 diff -u -r1.20 -r1.21 --- team.xml 16 Nov 2003 19:02:51 - 1.20 +++ team.xml 19 Dec 2003 01:08:42 - 1.21 @@ -19,9 +19,12 @@ independence and is having fun working on open source projects like Apache FOP. He's also the creator of fork href=http://www.krysalis.org/barcode;Krysalis Barcode/fork. /li -li id=gmlink href=mailto:[EMAIL PROTECTED]Glen Mazza/link (GM) is an information systems analyst - with EDS in Arlington, Virginia, USA./li -li id=wvmlink href=mailto:[EMAIL PROTECTED]Victor Mote/link (WVM) is the founder and manager of jump href=http://www.outfitr.com;Enterprise Outfitters/jump, a business software company, and of jump href=http://www.portagepub.com;Portage Publications/jump, a republisher of old documents. Both are located in Colorado Springs, Colorado, USA./li +li id=gmlink href=mailto:[EMAIL PROTECTED]Glen Mazza/link (GM) is an information +systems analyst with EDS in Arlington, Virginia, USA./li +li id=wvmlink href=mailto:[EMAIL PROTECTED]Victor Mote/link (WVM) is the founder and +manager of jump href=http://www.outfitr.com;Enterprise Outfitters/jump, a business +software company, and of jump href=http://www.portagepub.com;Portage Publications/jump, +a republisher of old documents. Both are located in Colorado Springs, Colorado, USA./li li id=jplink href=mailto:[EMAIL PROTECTED]J#x00F6;rg Pietschmann/link (JP)/li li id=otlink href=mailto:[EMAIL PROTECTED]Oleg Tkachenko/link (OT)/li li id=pbwlink href=mailto:[EMAIL PROTECTED]Peter B. West/link (PBW)/li @@ -30,8 +33,12 @@ section id=contribute-active titleActive Contributors/title ul -lilink href=mailto:[EMAIL PROTECTED]Marcelo Jaccoud Amaral/link/li -lilink href=mailto:[EMAIL PROTECTED]Rhett Aultman/link/li +lilink href=mailto:[EMAIL PROTECTED]John Austin/link is an +is an independent software developer currently based in St John's, +Newfoundland. While developing a taste for good seafood, he still isn't ready +for seal flipper (even if it's fresh). He is currently assisting the FOP +project on memory and performance issues./li +lilink href=mailto:[EMAIL PROTECTED]Finn Bock/link/li lilink href=mailto:[EMAIL PROTECTED]Chris Bowditch/link/li lilink href=mailto:[EMAIL PROTECTED]Andreas Delmelle/link/li lilink href=mailto:[EMAIL PROTECTED]Peter Herweg/link is helping to - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
cvs commit: xml-fop/src/documentation/resources/images logo2.svg
vmote 2003/12/05 11:13:06 Added: src/documentation/resources/images logo2.svg Log: add svg image for new FOP logo Revision ChangesPath 1.1 xml-fop/src/documentation/resources/images/logo2.svg http://cvs.apache.org/viewcvs/xml-fop/src/documentation/resources/images/logo2.svg?rev=1.1 - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Wiki (was Re: cvs commit: xml-fop/src/documentation/content/xdocs book.xml)
Victor Mote wrote: Modified:src/documentation/content/xdocs book.xml Log: Added link to the Wiki Chris: FYI, there is a link to the Wiki on the dev tab, the thinking being that the Wiki would be used primarily for development and design issues that are probably not of general interest to the users. If you think it is needed on the user tab too, that is OK. Yes, I wouldn't limit the Wiki to development issues. IMHO it should also be an easy way for users to contribute to the documentation. The Cocoon Wiki is a nice example. Christian
RE: cvs commit: xml-fop/src/documentation/content/xdocs book.xml
[EMAIL PROTECTED] wrote: Sent: Tuesday, November 25, 2003 6:13 PM To: [EMAIL PROTECTED] Subject: cvs commit: xml-fop/src/documentation/content/xdocs book.xml chrisg 2003/11/25 17:12:46 Modified:src/documentation/content/xdocs book.xml Log: Added link to the Wiki Chris: FYI, there is a link to the Wiki on the dev tab, the thinking being that the Wiki would be used primarily for development and design issues that are probably not of general interest to the users. If you think it is needed on the user tab too, that is OK. Victor Mote
cvs commit: xml-fop/src/documentation/content/xdocs/dev tools.xml
vmote 2003/11/25 07:29:38
Modified:src/documentation/content/xdocs resources.xml
src/documentation/content/xdocs/dev tools.xml
Log:
add some cvs and xsl-fo resources
Revision ChangesPath
1.33 +2 -1 xml-fop/src/documentation/content/xdocs/resources.xml
Index: resources.xml
===
RCS file: /home/cvs/xml-fop/src/documentation/content/xdocs/resources.xml,v
retrieving revision 1.32
retrieving revision 1.33
diff -u -r1.32 -r1.33
--- resources.xml 12 Nov 2003 15:29:59 - 1.32
+++ resources.xml 25 Nov 2003 15:29:38 - 1.33
@@ -68,6 +68,7 @@
li[online article] jump
href=http://www.sun.com/software/xml/developers/slides-dtd/;Using Formatting Objects
with the Slides DTD/jump, by Paul Sandoz./li
li[online article] jump
href=http://www.xml.com/pub/a/2001/01/17/xsl-fo/index.html;Using XSL Formatting
Objects/jump, by J. David Eisenberg./li
li[online reference] jump
href=http://zvon.org/xxl/xslfoReference/Output/index.html;XSL FO reference/jump,
by Miloslav Nic./li
+ li[online reference] jump
href=http://www.dpawson.co.uk/xsl/sect3/index.html;Dave Pawson's XSL-FO
FAQ/jump./li
li[online book] jump
href=http://www.dpawson.co.uk/xsl/sect3/bk/index.html;An introduction to XSL
Formatting Objects/jump, by Dave Pawson. See hardcopy version below./li
li[book] jump
href=http://www.oreilly.com/catalog/xslfo;XSL-FO/jump, by Dave Pawson, O'Reilly
amp; Associates, 2002, ISBN 0-596-00355-2. See online version above./li
li[book] jump
href=http://www.phptr.com/browse/product.asp?product_id={CEA527AF-412D-49DA-8C1F-46E0A519B8D8};Definitive
XSL-FO/jump, by G. Ken Holman, Prentice Hall PTR, 2003, ISBN 0-131-40374-5./li
1.9 +14 -1 xml-fop/src/documentation/content/xdocs/dev/tools.xml
Index: tools.xml
===
RCS file: /home/cvs/xml-fop/src/documentation/content/xdocs/dev/tools.xml,v
retrieving revision 1.8
retrieving revision 1.9
diff -u -r1.8 -r1.9
--- tools.xml 13 Nov 2003 18:01:49 - 1.8
+++ tools.xml 25 Nov 2003 15:29:38 - 1.9
@@ -77,6 +77,19 @@
liOn a Linux/Unix machine, you will want to redirect the output from
the above command into a file. If you are using GNU WinCVS, you can cut the output
from the console window and paste it into a file. The -w ignores whitespace
differences. The -u puts the diff in universal format. You may wish to use the
-N option as well, which is supposed to treat new files as if there were an old 0
byte file -- in other words, it is supposed to include the new file in the patch.
However, it only operates on files that have been added to the CVS repository, which
cannot be done without commit access./li
/ul
/section
+ section id=cvs-doc
+titleDocumentation/title
+ul
+ li[online resource] jump href=http://www.cvshome.org;The CVS Home
Page/jump./li
+ li[electronic manual] jump
href=http://www.cvshome.org/docs/manual;The Cederqvist/jump (official CVS
manual).
+Note that this manual applies to the command-line version of CVS./li
+ li[book] jump href=http://www.oreilly.com/catalog/cvs;Essential
CVS/jump, by Jennifer Vesperman (O'Reilly amp; Associates)./li
+ li[book] jump href=http://www.oreilly.com/catalog/cvspr2;The CVS
Pocket Reference/jump, by Gregor N. Purdy (O'Reilly amp; Associates)./li
+ li[book] Open Source Development with CVS, by Moshe Bar and Karl Franz
Fogel (Paraglyph Press, ISBN 1-932111-81-6)./li
+ li[book] jump href=http://www.oreilly.com/catalog/rcs;Applying RCS
and SCCS/jump, by Dan Bolinger and Tan Bronson (O'Reilly amp; Associates).
+RCS is used by CVS for its file operations (CVS is kind of a wrapper around
RCS)./li
+/ul
+ /section
/section
section id=ide
titleIntegrated Development Environments (IDEs)/title
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
FOP documentation
Hello, I am making an effort to understand FOP's architecture and program code. In this process I have compiled a number of documentation notes. It is a loose collection of notes on various aspects of the program, liberally illustrated with object dumps and stack traces as provided by jdb. The structure of the notes very much reflects my discovery and growing understanding of the various parts of FOP. I will add to this collection as I study more parts of FOP. These documentation notes are very much a work in progress. I do not claim that I understand FOP; I am trying to. Therefore you should not believe what these notes say. If you do, and you act accordingly, you do so at your own risk. The notes can be found at: http://www.leverkruid.nl/FOP/index.html Regards, Simon Pepping -- Simon Pepping email: [EMAIL PROTECTED] home page: http://www.leverkruid.nl
cvs commit: xml-fop/src/documentation/content/xdocs book.xml
chrisg 2003/11/25 17:12:46 Modified:src/documentation/content/xdocs book.xml Log: Added link to the Wiki Revision ChangesPath 1.27 +1 -0 xml-fop/src/documentation/content/xdocs/book.xml Index: book.xml === RCS file: /home/cvs/xml-fop/src/documentation/content/xdocs/book.xml,v retrieving revision 1.26 retrieving revision 1.27 diff -u -r1.26 -r1.27 --- book.xml 10 Jul 2003 17:12:37 - 1.26 +++ book.xml 26 Nov 2003 01:12:46 - 1.27 @@ -40,6 +40,7 @@ menu-item label=Examples href=examples.html/ menu-item label=Mailing Lists href=maillist.html/ menu-item label=Bugs href=bugs.html/ + menu-item label=Wiki href=http://nagoya.apache.org/wiki/apachewiki.cgi?FOPProjectPages/ menu-item label=License href=license.html/ menu-item label=Other href=resources.html/ /menu - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
(Victor) RE: cvs commit: xml-fop/src/documentation/content/xdocs team.xml
Victor wrote: Jeremias wrote: AFAIK Mark Lillywhite was never a committer, only a contributor. He helped improve speed and memory consumption back during his active times. Unfortunately, he didn't stay long enough to get nominated. snip BTW, what triggered this was my transfer of the last batch of resolved style issues to the web page, which included a provision to remove personal attributions within source code. I want to make sure that we don't just erase the memory of the people at the same time. Victor Mote Victor, Rather than burden the team page with the name of each person who has contributed source code to FOP, I think it would be better for us to continue to keep their names in the source file, albeit outside of the @author attribute tag. I had understood the vote as for us not using the @author attribution for source files--in short, that our FOP JavaDoc won't be listing individual committer and contributor names. That's a clean design for our JavaDocs, which I agreed with. But even though the vote was probably to remove *all* author comments, @author or not (which is also fine, after all, the committers themselves rarely put their names on any files), it was not to remove all author credits *and* add them to the team page. Indeed, I don't know of any other Apache group that maintains a former contributors section instead of comments in the source files--and I'm reluctant for us to open that can of worms--especially as this will soon grow to dozens of names (look at the AWT classes, for example). Simple non-JavaDoc comments near the top of a source file that indicate its original contributor are not that bad, actually the right thing to do. (It's also what jfor apparently does--see the Team section at: http://www.jfor.org/) In those cases where we're concerned about the contributor's work getting erased, then this is probably the cleaner route. Glen __ Do you Yahoo!? Protect your identity with Yahoo! Mail AddressGuard http://antispam.yahoo.com/whatsnewfree
cvs commit: xml-fop/src/documentation/content/xdocs team.xml
gmazza 2003/11/16 09:38:59 Modified:src/documentation/content/xdocs team.xml Log: Addition of Peter Herweg to our team page (secured his permission first). Revision ChangesPath 1.19 +6 -2 xml-fop/src/documentation/content/xdocs/team.xml Index: team.xml === RCS file: /home/cvs/xml-fop/src/documentation/content/xdocs/team.xml,v retrieving revision 1.18 retrieving revision 1.19 diff -u -r1.18 -r1.19 --- team.xml 12 Nov 2003 15:11:59 - 1.18 +++ team.xml 16 Nov 2003 17:38:59 - 1.19 @@ -34,7 +34,11 @@ lilink href=mailto:[EMAIL PROTECTED]Rhett Aultman/link/li lilink href=mailto:[EMAIL PROTECTED]Chris Bowditch/link/li lilink href=mailto:[EMAIL PROTECTED]Andreas Delmelle/link/li -lilink href=mailto:[EMAIL PROTECTED]Clay Leeds/link (CL) +lilink href=mailto:[EMAIL PROTECTED]Peter Herweg/link has been busy +integrating the jfor project's RTF support into the upcoming FOP 1.0 version. +Born in 1978, he has been serving as an application developer for a small industrial +company in Germany since 1999./li +lilink href=mailto:[EMAIL PROTECTED]Clay Leeds/link is a web/WAP/Palm developer from Laguna Beach, California, USA. A recent XML/XSL-FO convert, he has been nit-picking FAQs amp; assorted web pages since his first webmaster position @brain.com in 1996. Most - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
cvs commit: xml-fop/src/documentation/content/xdocs team.xml
gmazza 2003/11/16 11:02:51 Modified:src/documentation/content/xdocs team.xml Log: rephrased to look better. Revision ChangesPath 1.20 +5 -5 xml-fop/src/documentation/content/xdocs/team.xml Index: team.xml === RCS file: /home/cvs/xml-fop/src/documentation/content/xdocs/team.xml,v retrieving revision 1.19 retrieving revision 1.20 diff -u -r1.19 -r1.20 --- team.xml 16 Nov 2003 17:38:59 - 1.19 +++ team.xml 16 Nov 2003 19:02:51 - 1.20 @@ -34,10 +34,10 @@ lilink href=mailto:[EMAIL PROTECTED]Rhett Aultman/link/li lilink href=mailto:[EMAIL PROTECTED]Chris Bowditch/link/li lilink href=mailto:[EMAIL PROTECTED]Andreas Delmelle/link/li -lilink href=mailto:[EMAIL PROTECTED]Peter Herweg/link has been busy -integrating the jfor project's RTF support into the upcoming FOP 1.0 version. -Born in 1978, he has been serving as an application developer for a small industrial -company in Germany since 1999./li +lilink href=mailto:[EMAIL PROTECTED]Peter Herweg/link is helping to +integrate the jfor project's RTF support into the upcoming FOP 1.0 version. +Born in 1978, he has been serving as an application developer for a small +industrial company in Germany since 1999./li lilink href=mailto:[EMAIL PROTECTED]Clay Leeds/link is a web/WAP/Palm developer from Laguna Beach, California, USA. A recent XML/XSL-FO convert, he has been nit-picking FAQs amp; assorted web - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
cvs commit: xml-fop/src/documentation/content/xdocs/dev testing.xml
vmote 2003/11/13 09:41:20 Modified:src/documentation/content/xdocs/dev testing.xml Log: 1. add section regarding basic/API tests 2. add warning that the functional testing is inoperative Revision ChangesPath 1.5 +9 -1 xml-fop/src/documentation/content/xdocs/dev/testing.xml Index: testing.xml === RCS file: /home/cvs/xml-fop/src/documentation/content/xdocs/dev/testing.xml,v retrieving revision 1.4 retrieving revision 1.5 diff -u -r1.4 -r1.5 --- testing.xml 12 Nov 2003 15:24:53 - 1.4 +++ testing.xml 13 Nov 2003 17:41:20 - 1.5 @@ -17,8 +17,16 @@ lilink href=http://gump.cocoondev.org/xml-fop-maintenance.html;Gump build for the Maintenance Branch/link/li /ul /section +section id=basic + titleBasic/API Testing/title + pThere is a group of basic API tests that are included in the build process. +For these tests to occur, JUnit must be available to Ant (simply copy junit.jar into Ant's lib directory). +The build will then report error(s) if the high-level APIs for Driver and the Transcoders fail. +The tests do not check the output, but only ensure that something is generated and without exceptions./p +/section section id=functional titleFunctional Testing/title + warningThe functional testing section on this page is currently inoperative./warning section titleRunning and Using Tests/title p - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
cvs commit: xml-fop/src/documentation/content/xdocs/dev tools.xml
vmote 2003/11/13 10:01:49 Modified:src/documentation/content/xdocs/dev tools.xml Log: add developer checklist Revision ChangesPath 1.8 +11 -1 xml-fop/src/documentation/content/xdocs/dev/tools.xml Index: tools.xml === RCS file: /home/cvs/xml-fop/src/documentation/content/xdocs/dev/tools.xml,v retrieving revision 1.7 retrieving revision 1.8 diff -u -r1.7 -r1.8 --- tools.xml 12 Nov 2003 15:24:53 - 1.7 +++ tools.xml 13 Nov 2003 18:01:49 - 1.8 @@ -8,6 +8,16 @@ /header body pThis page documents items that may be helpful to other developers, especially to those who are new to FOP. Exhaustive treatment of these topics is better suited to other fora, but the information presented here is intended to deal with FOP-specific issues related to these tools, especially gotchas, and to help developers get jump-started./p +section id=checklist + titleDeveloper Checklist/title + pHere is a (probably not comprehensive) list of tools you will need to be a successful FOP developer:/p + ul +liA java IDE (see link href=#ideIDE/link)./li +liAnt (see link href=../compiling.htmlBuilding FOP/link)./li +licheckstyle (see link href=conventions.html#java-checkstyleCheckstyle/link on the conventions page)./li +liJUnit (see link href=testing.html#basicBasic Testing/link)./li + /ul +/section section id=general titleGeneral Developer Information/title pSee link href=http://www.apache.org/dev/contributors.html;the Apache Contributors Tech Guide/link for useful information and links for Apache developers, including help with tools and procedures./p - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
cvs commit: xml-fop/src/documentation/content/xdocs anttask.xml bugs.xml compiling.xml compliance.xml configuration.xml download.xml embedding.xml examples.xml extensions.xml faq.xml fo.xml fonts.xml gethelp.xml graphics.xml hyphenation.xml index.xml license.xml logocontest.xml maillist.xml news.xml output.xml pdfencryption.xml relnotes.xml resources.xml running.xml servlets.xml status.xml tabs.xml team.xml
vmote 2003/11/12 07:12:00 Modified:src/documentation/content/xdocs anttask.xml bugs.xml compiling.xml compliance.xml configuration.xml download.xml embedding.xml examples.xml extensions.xml faq.xml fo.xml fonts.xml gethelp.xml graphics.xml hyphenation.xml index.xml license.xml logocontest.xml maillist.xml news.xml output.xml pdfencryption.xml relnotes.xml resources.xml running.xml servlets.xml status.xml tabs.xml team.xml Log: update URLs for DTDs Revision ChangesPath 1.8 +2 -2 xml-fop/src/documentation/content/xdocs/anttask.xml Index: anttask.xml === RCS file: /home/cvs/xml-fop/src/documentation/content/xdocs/anttask.xml,v retrieving revision 1.7 retrieving revision 1.8 diff -u -r1.7 -r1.8 --- anttask.xml 17 Oct 2003 22:21:53 - 1.7 +++ anttask.xml 12 Nov 2003 15:11:59 - 1.8 @@ -1,6 +1,6 @@ ?xml version=1.0 standalone=no? !DOCTYPE document PUBLIC -//APACHE//DTD Documentation V1.1//EN - http://cvs.apache.org/viewcvs.cgi/*checkout*/xml-forrest/src/resources/schema/dtd/document-v11.dtd; + http://cvs.apache.org/viewcvs.cgi/*checkout*/xml-forrest/src/core/context/resources/schema/dtd/document-v12.dtd; document header 1.7 +2 -2 xml-fop/src/documentation/content/xdocs/bugs.xml Index: bugs.xml === RCS file: /home/cvs/xml-fop/src/documentation/content/xdocs/bugs.xml,v retrieving revision 1.6 retrieving revision 1.7 diff -u -r1.6 -r1.7 --- bugs.xml 15 Sep 2003 20:54:01 - 1.6 +++ bugs.xml 12 Nov 2003 15:11:59 - 1.7 @@ -1,6 +1,6 @@ ?xml version=1.0 standalone=no? !DOCTYPE document PUBLIC -//APACHE//DTD Documentation V1.1//EN - http://cvs.apache.org/viewcvs.cgi/*checkout*/xml-forrest/src/resources/schema/dtd/document-v11.dtd; + http://cvs.apache.org/viewcvs.cgi/*checkout*/xml-forrest/src/core/context/resources/schema/dtd/document-v12.dtd; document header 1.11 +2 -2 xml-fop/src/documentation/content/xdocs/compiling.xml Index: compiling.xml === RCS file: /home/cvs/xml-fop/src/documentation/content/xdocs/compiling.xml,v retrieving revision 1.10 retrieving revision 1.11 diff -u -r1.10 -r1.11 --- compiling.xml 16 Oct 2003 15:06:33 - 1.10 +++ compiling.xml 12 Nov 2003 15:11:59 - 1.11 @@ -1,6 +1,6 @@ ?xml version=1.0 standalone=no? !DOCTYPE document PUBLIC -//APACHE//DTD Documentation V1.1//EN - http://cvs.apache.org/viewcvs.cgi/*checkout*/xml-forrest/src/resources/schema/dtd/document-v11.dtd; + http://cvs.apache.org/viewcvs.cgi/*checkout*/xml-forrest/src/core/context/resources/schema/dtd/document-v12.dtd; document header 1.24 +1 -1 xml-fop/src/documentation/content/xdocs/compliance.xml Index: compliance.xml === RCS file: /home/cvs/xml-fop/src/documentation/content/xdocs/compliance.xml,v retrieving revision 1.23 retrieving revision 1.24 diff -u -r1.23 -r1.24 --- compliance.xml15 Sep 2003 20:54:01 - 1.23 +++ compliance.xml12 Nov 2003 15:11:59 - 1.24 @@ -1,6 +1,6 @@ ?xml version=1.0 encoding=UTF-8? !DOCTYPE compliance PUBLIC -//APACHE//DTD Compliance V1.0//EN - http://cvs.apache.org/viewcvs.cgi/*checkout*/xml-fop/src/documentation/resources/schema/dtd/compliance-v10.dtd?rev=1.6; + http://cvs.apache.org/viewcvs.cgi/*checkout*/xml-fop/src/documentation/resources/schema/dtd/compliance-v10.dtd; compliance head 1.16 +2 -2 xml-fop/src/documentation/content/xdocs/configuration.xml Index: configuration.xml === RCS file: /home/cvs/xml-fop/src/documentation/content/xdocs/configuration.xml,v retrieving revision 1.15 retrieving revision 1.16 diff -u -r1.15 -r1.16 --- configuration.xml 15 Sep 2003 20:54:01 - 1.15 +++ configuration.xml 12 Nov 2003 15:11:59 - 1.16 @@ -1,6 +1,6 @@ ?xml version=1.0 standalone=no? !DOCTYPE document PUBLIC -//APACHE//DTD Documentation V1.1//EN - http://cvs.apache.org/viewcvs.cgi/*checkout*/xml-forrest/src/resources/schema/dtd/document-v11.dtd; + http://cvs.apache.org/viewcvs.cgi/*checkout*/xml-forrest/src/core/context/resources/schema/dtd/document-v12.dtd; document header 1.14 +2 -2 xml-fop/src/documentation/content/xdocs/download.xml Index: download.xml
cvs commit: xml-fop/src/documentation/content/xdocs resources.xml
vmote 2003/11/12 07:29:59 Modified:src/documentation/content/xdocs resources.xml Log: add link for UTR-14 Revision ChangesPath 1.32 +7 -1 xml-fop/src/documentation/content/xdocs/resources.xml Index: resources.xml === RCS file: /home/cvs/xml-fop/src/documentation/content/xdocs/resources.xml,v retrieving revision 1.31 retrieving revision 1.32 diff -u -r1.31 -r1.32 --- resources.xml 12 Nov 2003 15:11:59 - 1.31 +++ resources.xml 12 Nov 2003 15:29:59 - 1.32 @@ -46,6 +46,12 @@ /li /ul /section + section id=specs-unicode +titleUnicode/title +ul + lijump href=http://www.unicode.org/reports/tr14;UTR-14 (Unicode Standard Annex #14: Line Breaking Properties)/jump/li +/ul + /section section id=specs-other titleOther/title ul - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
cvs commit: xml-fop/src/documentation/content/xdocs faq.xml fo.xml
vmote 2003/11/12 09:28:07
Modified:src/documentation/content/xdocs faq.xml fo.xml
Log:
add doc for using current date and time, and create an FAQ referencing it
Revision ChangesPath
1.40 +6 -0 xml-fop/src/documentation/content/xdocs/faq.xml
Index: faq.xml
===
RCS file: /home/cvs/xml-fop/src/documentation/content/xdocs/faq.xml,v
retrieving revision 1.39
retrieving revision 1.40
diff -u -r1.39 -r1.40
--- faq.xml 12 Nov 2003 15:11:59 - 1.39
+++ faq.xml 12 Nov 2003 17:28:07 - 1.40
@@ -972,6 +972,12 @@
/p
/answer
/faq
+faq id=xslt-current-date
+ question(XSLT) How can I use the current date and time in my
document?/question
+ answer
+pSee link href=fo.html#xslt-dateCurrent Date and Time/link./p
+ /answer
+/faq
/part
part id=part-help
titleGeneral suggestions. How to solve problems./title
1.9 +22 -1 xml-fop/src/documentation/content/xdocs/fo.xml
Index: fo.xml
===
RCS file: /home/cvs/xml-fop/src/documentation/content/xdocs/fo.xml,v
retrieving revision 1.8
retrieving revision 1.9
diff -u -r1.8 -r1.9
--- fo.xml12 Nov 2003 15:11:59 - 1.8
+++ fo.xml12 Nov 2003 17:28:07 - 1.9
@@ -82,6 +82,27 @@
/p
/section
/section
+section id=xslt
+ titleXSLT Issues/title
+ section id=xslt-date
+titleCurrent Date and Time/title
+pXSL-FO does not currently have a function for retrieving the current
date and time.
+However, in some cases, XSLT can be used to place the current date and time into
the XSL-FO document as it is generated./p
+pOne possibility is to use the link
href=http://exslt.org/date/index.html;exslt date and time extension/link./p
+pAnother possibility is to use java or javascript (or perhaps some other
language).
+Here is an example, using java, that works with Xalan. First, create the
appropriate namespace:/p
+source![CDATA[xsl:stylesheet version=1.0
+ ...
+ xmlns:java=http://xml.apache.org/xslt/java; exclude-result-prefixes=java
+ ...]]/source
+pNext, use the java language to retrieve and format the current date and
time.
+Here is an example template:/p
+source![CDATA[xsl:template match=TodaysDate
+xsl:value-of select=java:format(java:java.text.SimpleDateFormat.new
+(' d, , h:mm:ss a (zz)'), java:java.util.Date.new())/
+ /xsl:template]]/source
+ /section
+/section
section id=xsl-fo
titleXSL-FO Issues/title
section id=fo-center-vertical
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
cvs commit: xml-fop/src/documentation/content/xdocs fo.xml
vmote 2003/11/12 09:41:06 Modified:src/documentation/content/xdocs fo.xml Log: make external site a jump instead of link Revision ChangesPath 1.10 +2 -2 xml-fop/src/documentation/content/xdocs/fo.xml Index: fo.xml === RCS file: /home/cvs/xml-fop/src/documentation/content/xdocs/fo.xml,v retrieving revision 1.9 retrieving revision 1.10 diff -u -r1.9 -r1.10 --- fo.xml12 Nov 2003 17:28:07 - 1.9 +++ fo.xml12 Nov 2003 17:41:06 - 1.10 @@ -88,7 +88,7 @@ titleCurrent Date and Time/title pXSL-FO does not currently have a function for retrieving the current date and time. However, in some cases, XSLT can be used to place the current date and time into the XSL-FO document as it is generated./p -pOne possibility is to use the link href=http://exslt.org/date/index.html;exslt date and time extension/link./p +pOne possibility is to use the jump href=http://exslt.org/date/index.html;exslt date and time extension/jump./p pAnother possibility is to use java or javascript (or perhaps some other language). Here is an example, using java, that works with Xalan. First, create the appropriate namespace:/p source![CDATA[xsl:stylesheet version=1.0 - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
cvs commit: xml-fop/src/documentation/content/xdocs anttask.xml
gmazza 2003/10/17 15:21:53 Modified:src/documentation/content/xdocs anttask.xml Log: Explanation of new force attribute in ant task. Revision ChangesPath 1.7 +8 -4 xml-fop/src/documentation/content/xdocs/anttask.xml Index: anttask.xml === RCS file: /home/cvs/xml-fop/src/documentation/content/xdocs/anttask.xml,v retrieving revision 1.6 retrieving revision 1.7 diff -u -r1.6 -r1.7 --- anttask.xml 15 Sep 2003 20:54:01 - 1.6 +++ anttask.xml 17 Oct 2003 22:21:53 - 1.7 @@ -69,11 +69,15 @@ tdOutput directory/td tdRequired if a fileset is used to specify the files to render; optional for fofile. (Can alternatively specify the full path in the fofile value.)/td /tr - !--tr Commented out; implemented only in 1.0 currently + tr tdforce/td - tdIf codetrue/code, always generate target file, even if source file has not changed./td + tdRecreate target files, even if they are newer than their corresponding +source files. Note: This attribute is available in post-0.20.5 +versions (0.20.x nightly build and 1.0dev) only; target files are +always generated (i.e., force=true) in 0.20.5 release. + /td tdNo, default is codefalse/code/td - /tr-- + /tr !--tr Commented out; attribute is currently unimplemented according to the code tdbasedir/td tdDirectory to work from/td - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
cvs commit: xml-fop/src/documentation/content/xdocs fonts.xml
vmote 2003/10/16 07:35:11 Modified:src/documentation/content/xdocs fonts.xml Log: correct doc re: use of custome fonts from the AWT and Print renderers Revision ChangesPath 1.20 +3 -3 xml-fop/src/documentation/content/xdocs/fonts.xml Index: fonts.xml === RCS file: /home/cvs/xml-fop/src/documentation/content/xdocs/fonts.xml,v retrieving revision 1.19 retrieving revision 1.20 diff -u -r1.19 -r1.20 --- fonts.xml 15 Sep 2003 20:54:01 - 1.19 +++ fonts.xml 16 Oct 2003 14:35:11 - 1.20 @@ -54,14 +54,14 @@ tdAWT/td tdif available from OS/td tdyes/td - tdno/td + tdyes/td tdn/a (display only)/td /tr tr tdPrint/td tdif available from OS/td tdyes/td - tdno/td + tdyes/td tdcontrolled by OS printer driver/td /tr tr - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
cvs commit: xml-fop/src/documentation/content/xdocs compiling.xml
vmote 2003/10/16 08:06:33 Modified:src/documentation/content/xdocs compiling.xml Log: partially implement patch submitted by Clay Leeds (see http://nagoya.apache.org/bugzilla/show_bug.cgi?id=23821) Revision ChangesPath 1.10 +5 -9 xml-fop/src/documentation/content/xdocs/compiling.xml Index: compiling.xml === RCS file: /home/cvs/xml-fop/src/documentation/content/xdocs/compiling.xml,v retrieving revision 1.9 retrieving revision 1.10 diff -u -r1.9 -r1.10 --- compiling.xml 15 Sep 2003 20:54:01 - 1.9 +++ compiling.xml 16 Oct 2003 15:06:33 - 1.10 @@ -20,19 +20,17 @@ titleJDK/title p Building FOP requires a minimum Java Development Kit (JDK/SDK) of 1.3 -(A Java Runtime Environment ist not sufficient) +(A Java Runtime Environment is not sufficient). /p /section section id=env-classpath titleCLASSPATH/title -pThere is no generally no need to setup a classpath. -All libraries needed to compile FOP are included in the source distribution and are referenced by the build script. +pThere is generally no need to setup a classpath. All libraries needed to compile FOP are included in the source distribution and are referenced by the build script. You will only need to adjust the classpath if you build FOP in some other way. See the build scripts (build.bat for Windows, and build.sh for Unix) for details./p /section section id=env-java-home titleJAVA_HOME/title -pAnt, which is used by the build script, requires that the environment variable JAVA_HOME point to your local JDK root directory. -This is true even if you use JDK 1.2 or above, which normally don't need this setting./p +pThe build script uses link href=http://jakarta.apache.org/ant/;Ant/link, a popular java-based build tool, which requires that the environment variable JAVA_HOME point to your local JDK root directory. This is true even if you use JDK 1.2 or above, which normally don't need this setting./p /section /section section id=build-script @@ -40,9 +38,7 @@ pBuild FOP by executing the build script, which is located in the FOP root directory. The Windows batch file is build.bat, and the Unix shell script is build.sh. The examples below are for running the shell script, but except for the build file extension, the syntax is identical./p -pThe build script uses link href=http://jakarta.apache.org/ant/;Ant/link, a popular java-based build tool. -The file build.xml in the FOP root directory is the blueprint that Ant uses for the build. -It contains information for numerous build targets, many of which are building blocks to more useful target, and others which are primarily used by the FOP developers. +pThe file build.xml in the FOP root directory is the blueprint that Ant uses for the build. It contains information for numerous build targets, many of which are building blocks to more useful target, and others which are primarily used by the FOP developers. You may benefit from looking through this file to learn more about the various build targets. To obtain a complete list of useful build targets:/p sourcebuild.sh -projecthelp/source - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
cvs commit: xml-fop/src/documentation/content/xdocs/dev conventions.xml
vmote 2003/10/16 09:50:13 Modified:src/documentation/content/xdocs/dev conventions.xml Log: update code conventions from resolved issues on the FOPDevelopersStyleGuide wiki Revision ChangesPath 1.6 +20 -5 xml-fop/src/documentation/content/xdocs/dev/conventions.xml Index: conventions.xml === RCS file: /home/cvs/xml-fop/src/documentation/content/xdocs/dev/conventions.xml,v retrieving revision 1.5 retrieving revision 1.6 diff -u -r1.5 -r1.6 --- conventions.xml 15 Sep 2003 20:54:03 - 1.5 +++ conventions.xml 16 Oct 2003 16:50:13 - 1.6 @@ -20,7 +20,7 @@ titleJava/title section id=java-style titleJava Style/title -pIn order to facilitate the human reading of FOP source code, the FOP developers have agreed on a set of coding conventions. +pIn order to facilitate the human reading of FOP source code, reduce churning in code, and prevent disputes, the FOP developers have agreed on a set of coding conventions. The basis of these coding conventions is documented in the link href=http://xml.apache.org/source.html;Apache XML Project Guidelines/link, which requires that strongall Java Language source code in the repository must be written in conformance to Sun's/strong link href=http://java.sun.com/docs/codeconv/html/CodeConvTOC.doc.html;Code Conventions for the Java Programming Language/link. In addition, the FOP developers have agreed to other conventions, which are summarized in the following table:/p table @@ -35,21 +35,28 @@ tdcheckstyle/td /tr tr -tdNo tabs in content/td +tdNo tabs in content./td tdProgrammers should not have to adjust the tab settings in their editor to be able to read the source code./td tdcheckstyle/td /tr tr -tdIndentation of 4 spaces per level/td +tdIndentation of 4 spaces per level./td tdMaximize readability./td tdNot enforced/td /tr tr -tdComments must be in English/td +tdComments, identifiers, and project documentation must be in English. +In general, other languages must not be used, except in translated documentation and language-specific i10n files. +/td tdTo avoid the need for everyone to learn all languages, English has become the standard language for many technology projects, and is the only human language that all FOP developers are expected to know./td tdNot enforced/td /tr tr +tdAmerican English spelling should be used. Alternative spelling and idioms are tolerated, but may be changed by anyone to American./td +tdSome standard is useful, and American English is widely used and accepted for technology standards and projects./td +tdNot enforced./td + /tr + tr tdFully qualify all import statements (no import java.util.*)/td tdClarity/td tdcheckstyle/td @@ -68,6 +75,14 @@ tdWrite appropriate javadoc entries for all public and protected classes, methods, and variables./td tdBasic API documentation is needed./td tdcheckstyle/td + /tr + tr +tdPersonal attribution in the source code, such as @author tags and attribution comments should not be used. +Excepted from this general rule are potentially confusing or wide-ranging changes. +If such changes prove useful over time, the related comments should be removed./td +tdPersonal attribution tends to clutter the code. +The relevant historical information that might be useful for problem-solving is tracked in the code repository./td +tdNot enforced. Anyone is free to remove such comments./td /tr /table pFor developers that dislike these conventions, one workaround is to develop using their own style, then use a formatting tool like link href=http://astyle.sourceforge.net/;astyle/link (Artistic Style) before committing./p - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
cvs commit: xml-fop/src/documentation/content/xdocs team.xml
vmote 2003/10/16 10:19:59 Modified:src/documentation/content/xdocs team.xml Log: add Mark Lillywhite to list of former committers Revision ChangesPath 1.16 +2 -1 xml-fop/src/documentation/content/xdocs/team.xml Index: team.xml === RCS file: /home/cvs/xml-fop/src/documentation/content/xdocs/team.xml,v retrieving revision 1.15 retrieving revision 1.16 diff -u -r1.15 -r1.16 --- team.xml 15 Sep 2003 20:54:01 - 1.15 +++ team.xml 16 Oct 2003 17:19:59 - 1.16 @@ -55,6 +55,7 @@ li id=sglink href=mailto:[EMAIL PROTECTED]Stanislav Gorkhover/link/li li id=fjlink href=mailto:[EMAIL PROTECTED]Fotis Jannidis/link/li li id=kllink href=mailto:[EMAIL PROTECTED]Karen Lease/link/li +li id=mllink href=mailto:[EMAIL PROTECTED]Mark Lillywhite/link/li li id=jnlink href=mailto:[EMAIL PROTECTED]Jordan Naftolin/link/li li id=aslink href=mailto:[EMAIL PROTECTED]Arved Sandstrom/link/li li id=eslink href=mailto:[EMAIL PROTECTED]Eric Schaeffer/link/li - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: cvs commit: xml-fop/src/documentation/content/xdocs team.xml
Victor, AFAIK Mark Lillywhite was never a committer, only a contributor. He helped improve speed and memory consumption back during his active times. Unfortunately, he didn't stay long enough to get nominated. add Mark Lillywhite to list of former committers Jeremias Maerki
RE: cvs commit: xml-fop/src/documentation/content/xdocs team.xml
Jeremias Maerki wrote: AFAIK Mark Lillywhite was never a committer, only a contributor. He helped improve speed and memory consumption back during his active times. Unfortunately, he didn't stay long enough to get nominated. Thanks, I wondered about this. I'll change it right away. Do you know if there is an official record somewhere within the Apache infrastructure where stuff like this could be checked? BTW, what triggered this was my transfer of the last batch of resolved style issues to the web page, which included a provision to remove personal attributions within source code. I want to make sure that we don't just erase the memory of the people at the same time. Victor Mote
cvs commit: xml-fop/src/documentation/content/xdocs team.xml
vmote 2003/10/16 12:06:31 Modified:src/documentation/content/xdocs team.xml Log: correct Mark Lillywhite status Revision ChangesPath 1.17 +7 -2 xml-fop/src/documentation/content/xdocs/team.xml Index: team.xml === RCS file: /home/cvs/xml-fop/src/documentation/content/xdocs/team.xml,v retrieving revision 1.16 retrieving revision 1.17 diff -u -r1.16 -r1.17 --- team.xml 16 Oct 2003 17:19:59 - 1.16 +++ team.xml 16 Oct 2003 19:06:31 - 1.17 @@ -55,11 +55,16 @@ li id=sglink href=mailto:[EMAIL PROTECTED]Stanislav Gorkhover/link/li li id=fjlink href=mailto:[EMAIL PROTECTED]Fotis Jannidis/link/li li id=kllink href=mailto:[EMAIL PROTECTED]Karen Lease/link/li -li id=mllink href=mailto:[EMAIL PROTECTED]Mark Lillywhite/link/li li id=jnlink href=mailto:[EMAIL PROTECTED]Jordan Naftolin/link/li li id=aslink href=mailto:[EMAIL PROTECTED]Arved Sandstrom/link/li li id=eslink href=mailto:[EMAIL PROTECTED]Eric Schaeffer/link/li li id=awlink href=mailto:[EMAIL PROTECTED]Art Welch/link/li + /ul +/section +section id=contribute-former + titleFormer Contributors/title + ul +li id=mllink href=mailto:[EMAIL PROTECTED]Mark Lillywhite/link/li /ul /section section id=expertise - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: cvs commit: xml-fop/src/documentation/content/xdocs team.xml
Thanks, I wondered about this. I'll change it right away. Do you know if there is an official record somewhere within the Apache infrastructure where stuff like this could be checked? http://incubator.apache.org/whoweare.html for example BTW, what triggered this was my transfer of the last batch of resolved style issues to the web page, which included a provision to remove personal attributions within source code. I want to make sure that we don't just erase the memory of the people at the same time. Good thinking. Thanks for doing that. Jeremias Maerki
cvs commit: xml-fop/src/documentation/content/xdocs output.xml
chrisg 2003/10/14 17:43:59 Modified:src/documentation/content/xdocs output.xml Log: PCL Output: SVG not supported PR: 22943 Submitted by: Chris Bowditch (bowditch_chris at hotmail.com) Revision ChangesPath 1.14 +2 -3 xml-fop/src/documentation/content/xdocs/output.xml Index: output.xml === RCS file: /home/cvs/xml-fop/src/documentation/content/xdocs/output.xml,v retrieving revision 1.13 retrieving revision 1.14 diff -u -r1.13 -r1.14 --- output.xml15 Sep 2003 20:54:01 - 1.13 +++ output.xml15 Oct 2003 00:43:59 - 1.14 @@ -172,11 +172,10 @@ liOnly the original fonts built into FOP are supported./li liFor the non-symbol fonts, the ISO 8859/1 symbol set is used (PCL set 0N)./li liMultibyte characters are not supported./li -liSVG support is limited. Currently only lines, rectangles (may be rounded), circles, ellipses, text, simple paths, and images are supported. Colors are supported (dithered black and white) but not gradients./li +liSVG is not supported./li liImages print black and white only (not dithered). When the renderer prints a color image it uses a threshold value, colors above the threshold are printed as white and below are black. If you need to print a non-monochrome image you should dither it first./li liImage scaling is accomplished by modifying the effective resolution of the image data. The available resolutions are 75, 100, 150, 300, and 600 DPI./li liColor printing is not supported. Colors are rendered by mapping the color intensity to one of the PCL fill shades (from white to black in 9 steps)./li -liSVG clipping is not supported./li /ul /section - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
cvs commit: xml-fop/src/documentation/content/xdocs extensions.xml
vmote 2003/10/12 12:49:54 Modified:src/documentation/content/xdocs extensions.xml Log: fix typo Revision ChangesPath 1.13 +2 -2 xml-fop/src/documentation/content/xdocs/extensions.xml Index: extensions.xml === RCS file: /home/cvs/xml-fop/src/documentation/content/xdocs/extensions.xml,v retrieving revision 1.12 retrieving revision 1.13 diff -u -r1.12 -r1.13 --- extensions.xml15 Sep 2003 20:54:01 - 1.12 +++ extensions.xml12 Oct 2003 19:49:54 - 1.13 @@ -19,7 +19,7 @@ /p /section section id=fo-extensions - titleFO Extentions/title + titleFO Extensions/title section id=fox-namespace titleNamespace/title pBy convention, FO extensions in FOP use the fox: namespace identifier. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: cvs commit: xml-fop/src/documentation sitemap-0.5.xmap
--- Victor Mote [EMAIL PROTECTED] wrote: Glen Mazza wrote: - map:match pattern=body-compliance.xml + map:match pattern=body-compliance.html Glenn: Thanks for working on this. I also see that the ugly formatting problems have been fixed (presumably by the Forrest team, as I see no commits on our side), and that you have published the web site. It looks good. Thanks for getting all of that going again. Victor Mote That was fun--trying to find out why compliance.html wasn't generating cost me about three hours on Thursday night--even then I wasn't successful until I asked the Forrest team for help on Saturday. But it is finally done. Glen __ Do you Yahoo!? The New Yahoo! Shopping - with improved product search http://shopping.yahoo.com
cvs commit: xml-fop/src/documentation sitemap-0.5.xmap
gmazza 2003/09/27 09:28:23 Modified:src/documentation sitemap-0.5.xmap Log: Patch to sitemap to allow compliance.html to be generated in V5.0 (w/help from Jeff Turner, Forrest Team) Revision ChangesPath 1.3 +2 -2 xml-fop/src/documentation/sitemap-0.5.xmap Index: sitemap-0.5.xmap === RCS file: /home/cvs/xml-fop/src/documentation/sitemap-0.5.xmap,v retrieving revision 1.2 retrieving revision 1.3 diff -u -r1.2 -r1.3 --- sitemap-0.5.xmap 13 Sep 2003 19:57:28 - 1.2 +++ sitemap-0.5.xmap 27 Sep 2003 16:28:23 - 1.3 @@ -239,7 +239,7 @@ /map:match !-- == FOP Additions == -- - map:match pattern=body-compliance.xml + map:match pattern=body-compliance.html map:generate type=file src=content/xdocs/compliance.xml/ map:transform src=resources/stylesheets/compliance2html.xsl/ map:serialize type=xml/ - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
