Re: logo contest
Peter B. West wrote: Let's choose from the submissions, and if there is a consensus that some tweaking is required, we can go back to the designer with a request for a change. Here is my favourite three: #2 (I like the parrot idea, but sure it should be tweaked) #21/22 (a little bit minimalistic, but looks good) #9 So I propose to all committers (who didn't make it yet) to declare their 3 favorites and then we can repeat the same with the filtered list, as you suggested earlier. -- Oleg Tkachenko Multiconn Technologies, Israel - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
cvs commit: xml-fop/src/documentation/resources/scripts/design/alt.design/properties codedisplay.js
pbwest 2003/03/24 02:20:38 Removed: src/documentation/resources/scripts/design/alt.design/properties codedisplay.js Log: Moved to content/design/alt.design/properties - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
DO NOT REPLY [Bug 18275] New: - Fop enter in an infinite loop if image size is biger than page size
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT http://nagoya.apache.org/bugzilla/show_bug.cgi?id=18275. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE. http://nagoya.apache.org/bugzilla/show_bug.cgi?id=18275 Fop enter in an infinite loop if image size is biger than page size Summary: Fop enter in an infinite loop if image size is biger than page size Product: Fop Version: 0.20.4 Platform: PC OS/Version: All Status: NEW Severity: Normal Priority: Other Component: images AssignedTo: [EMAIL PROTECTED] ReportedBy: [EMAIL PROTECTED] Hello, I test on fop 0.20.4 and 0.20.5rc2 on PC windows 2000 and Linux Red Hat with Java 1.3.1. If the inclued gif image is declared with width and height bigger than page size (280x470mm for exemple), fop enter in an infinit loop and I have to kill the java process (fop 0.20.4) or fop detect an infinit loop and stop (fop 0.20.5rc2). I can provide the files, just tell me how if necessary. Cedric. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
DO NOT REPLY [Bug 18275] - Fop enter in an infinite loop if image size is biger than page size
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT http://nagoya.apache.org/bugzilla/show_bug.cgi?id=18275. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE. http://nagoya.apache.org/bugzilla/show_bug.cgi?id=18275 Fop enter in an infinite loop if image size is biger than page size [EMAIL PROTECTED] changed: What|Removed |Added Status|NEW |RESOLVED Resolution||INVALID --- Additional Comments From [EMAIL PROTECTED] 2003-03-24 13:26 --- Well, you ask the processor to do something not quite possible, and which causes conflicting user expectations. The spec is not really helpful in resolving this issues. For now you just have to accept the way FOP implements it, if you want to make sure your file renders you'll have to clip the images yourself so that they fit into the allocated areas. BTW it would have helped if you described you expectations a bit more, ahem, detailed. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
DO NOT REPLY [Bug 18275] - Fop enter in an infinite loop if image size is biger than page size
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT http://nagoya.apache.org/bugzilla/show_bug.cgi?id=18275. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE. http://nagoya.apache.org/bugzilla/show_bug.cgi?id=18275 Fop enter in an infinite loop if image size is biger than page size [EMAIL PROTECTED] changed: What|Removed |Added Status|RESOLVED|REOPENED Resolution|INVALID | --- Additional Comments From [EMAIL PROTECTED] 2003-03-24 13:45 --- I coded an infinite loop detector for FOP that should be able to catch these classes of bug. Please submit a FO file and the necessary graphics file as attachments to this bug and I will happily test this. FOP 0.20.4 should loop, but FOP 0.20.5 should not, unless someone's squashed my infinite loop detecting code. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
DO NOT REPLY [Bug 5654] - PS rendering doesn't seem to support landscape pages
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
http://nagoya.apache.org/bugzilla/show_bug.cgi?id=5654.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND
INSERTED IN THE BUG DATABASE.
http://nagoya.apache.org/bugzilla/show_bug.cgi?id=5654
PS rendering doesn't seem to support landscape pages
[EMAIL PROTECTED] changed:
What|Removed |Added
CC||[EMAIL PROTECTED]
||om
--- Additional Comments From [EMAIL PROTECTED] 2003-03-24 14:53 ---
Jeremias Maerki [EMAIL PROTECTED] (email seemingly no longer valid)
mentioned on June 17, 2002:
write(%%Page: + page.getNumber() + + page.getNumber());
if (page.getHeight() page.getWidth()) {
write(%%PageBoundingBox: 0 0 + pw + + ph);
write(%%PageOrientation: Portrait);
} else {
write(%%PageBoundingBox: 0 0 + ph + + pw);
write(%%PageOrientation: Landscape);
}
write(%%BeginPageSetup);
Could fix this problem.
Is there any reason why a patch such as this shouldn't be applied?
We really need Landscape rendering here (of course, we'll just patch it
ourselves for the time being, but it would be nice if there were an official fix).
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, email: [EMAIL PROTECTED]
Re: logo contest SVG question
J.Pietschmann wrote: Clay Leeds wrote: As a side note, does anyone know how to get SVG to display in Mozilla (1.3b). I tried installing the SVG plugin, but I can't get it to work. Works with 1.2.1: copy NPSVGvw.dll, SVGView.dll and SVGViewer.zip into the Mozilla plugins folder and restart. There's still the license screen I have to get rid of. J.Pietschmann I am unable to find those files on my hard drive. I've downloaded Adobe SVG Viewer 3.0 and when I run it, it indicates it has completed installation, but Mozilla is still unable to display SVG (IE works fine after running). Unfortunately, there is no interactivity when running SVGView.exe. After some searching, I've been able to find these files this directory: C:\WINDOWS\system32\Adobe\SVG Viewer 3.0 NPSVG3.dll ReadMe.html SVG3ACE.dll SVG3AGM.dll SVG3BIB.dll SVG3CT.dll SVG Viewer License.txt SVGAbout.svg SVGCore.dll SVGHelp.html SVGRSRC.dll SVGViewer.dict After reading the ReadMe SVGHelp.html files I'm still stuck. You indicated three files which aren't listed. In addition, there is no *.zip file (you and the ReadMe file indicate needing a zip file). I've tried copying these files to the plugins directory, but Mozilla crashes as soon as an SVG page is loaded (the FOP logo contest page or the Adobe SVG Demo page). I've also tried it with just NPSVG3.dll, SVGCore.dll and SVGViewer.dict. -- Clay Leeds - [EMAIL PROTECTED] Web Developer - Medata, Inc. - http://www.medata.com PGP Public Key: https://mail.medata.com/pgp/cleeds.asc - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
DO NOT REPLY [Bug 5654] - PS rendering doesn't seem to support landscape pages
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
http://nagoya.apache.org/bugzilla/show_bug.cgi?id=5654.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND
INSERTED IN THE BUG DATABASE.
http://nagoya.apache.org/bugzilla/show_bug.cgi?id=5654
PS rendering doesn't seem to support landscape pages
[EMAIL PROTECTED] changed:
What|Removed |Added
OS/Version|Windows NT/2K |All
--- Additional Comments From [EMAIL PROTECTED] 2003-03-24 17:02 ---
Ok, now that I've been hit with a cluestick (and noted that the fix I mentioned
below won't work for some cases, included the one that I am using), I've done
some hacking. :-)
I used fop.sh test.fo -awt to display the text, then I printed it to a file in
landscape mode. I noticed that this did some very generic things to make
landscape work, so I tried to incorporate them into FOP.
That didn't totally work, I got a mirror image of what I wanted. So I did some
more PostScript Googling/Hacking and came up with some slight changes to fix the
mirror effect.
The following works for me, but I would appreciate it if someone who is a bit
more clueful about Postscript could point out any potential pitfalls:
write(%%Page: + page.getNumber() + + page.getNumber());
if (page.getHeight() page.getWidth()) {
// Assume Portrait mode and do nothing (relying on the defaults)
write(%%PageBoundingBox: 0 0 +
Math.round(page.getWidth() / 1000f) + +
Math.round(page.getHeight() / 1000f));
} else {
write(/pgSave save def);
write(0 0.0 translate 1 -1 scale[72 300 div 0 0 72 300 div 0
0]concat);
write(1 -1 scale);
write(gsave);
write([0.0 -4.167 4.167 0.0 0.0
3300.5] concat);
write(newpath);
write(%%PageBoundingBox: 0 0 +
Math.round(page.getHeight() / 1000f) + +
Math.round(page.getWidth() / 1000f));
}
write(%%BeginPageSetup);
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, email: [EMAIL PROTECTED]
RE: logo contest
Scott Hofmann wrote: Victor, since one of my choices was also #7 with a dislike of the font i decided to post a revised version. Oooh. I like that a lot. Definitely my favorite. Thanks for submitting that. Victor Mote - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
RE: Encryption
Peter B. West wrote: This step seems to have some problems. I have just gone through the cycle of building locally, checking the changes into HEAD, getting forrestbot to refresh, checking the just-constucted site, and then getting forrestbot to publish. I had problems on the live site that I did not see locally or on the forrestbot driver pages at forrestbot.cocoondev.org. Specifically, an old copy of my javascript file was in service. Well, the forrestbot stuff is a black box to me right now. It may not know to look for your javascript code. Probably you'll have to check that into the sites repository manually to get it updated, but Jeff may have a better idea, or perhaps can provide a fix. I have noticed that redundant files do not seem to be cleaned up in the process either - they just hang around. I think old stuff probably needs to be retired in the sites repository manually, using CVS. I think this is what Jeff was referring to in an earlier posting about not being able to find a safe way to delete content. Victor Mote - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
Re: logo contest SVG question
Clay Leeds wrote: I am unable to find those files on my hard drive. I've downloaded Adobe SVG Viewer 3.0 My SVGViewer identifies itself as Version 2.0 (Build 55, 03/14/01) You'd better ask on a Mozilla related forum for further help. J.Pietschmann - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
Re: logo contest
Victor Mote wrote: Victor, since one of my choices was also #7 with a dislike of the font i decided to post a revised version. Oooh. I like that a lot. Definitely my favorite. Thanks for submitting that. Me too! J.Pietschmann - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
Re: logo contest
J.Pietschmann wrote: Victor, since one of my choices was also #7 with a dislike of the font i decided to post a revised version. Oooh. I like that a lot. Definitely my favorite. Thanks for submitting that. Me too! Well, I like the idea of inkstand and feather also. What about combining it with another logo? -- Oleg Tkachenko Multiconn Technologies, Israel - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
Re: logo contest SVG question (How to view SVG w Mozilla)
I was unable to load Adobe SVG Viewer 3.0. But Adobe SVG v2.0 is another story! I downloaded the archived SVG Viewer 2.0 found here: http://www.adobe.com/svg/viewer/install/old.html After downloading and running the installer, I copied NPSVGvw.dll, SVGView.dll and SVGViewer.zip to my Mozilla Plugins directory from: C:\WINDOWS\system32\Adobe\SVG Viewer\ The first time I loaded the FOP logo poll page, Mozilla hung. Then I relaunched Mozilla, and it works! Thanks! Web Maestro Clay -- Clay Leeds - [EMAIL PROTECTED] Web Developer - Medata, Inc. - http://www.medata.com PGP Public Key: https://mail.medata.com/pgp/cleeds.asc - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
RE: logo contest
Oleg Tkachenko wrote: Well, I like the idea of inkstand and feather also. What about combining it with another logo? Sure. What did you have in mind? Victor Mote - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
Re: logo contest
I too like the re-tooled #7 by Scott Hofman. However, I am leaning toward a lowercase fop for the logo (as in #10). I like the feeling I get from the serif of the f and the p. I also like the circular o in #13 (although the red dot reminds me I need to use visine...) My non-vote in order of preference: #10 (with or without the background fo) #7 (as modified by Scott Hofman) #9 (the modified version--I don't recall who modified it) -- Clay Leeds - [EMAIL PROTECTED] Web Developer - Medata, Inc. - http://www.medata.com PGP Public Key: https://mail.medata.com/pgp/cleeds.asc - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
Re: logo contest
Hi, I can't recall if the first winnowing round was for 3 or 4 picks, and I never noticed whether non-committers were even eligible to vote. So anyway, here's my $0.02 For round I nominate: 7, 10, 21 and/or 22 13 (maybe w/out the dot - I also think of visine) Many congratulations to all the submitters. Who would have expected so many worthy entries! -ralph committed, but not a committer ;-) ' Best, -Ralph LaChance In theory, there is no difference between theory and practice, but in practice there is. (Jan L.A. van de Snepsheut (1953-1994), late of CalTech) - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
DO NOT REPLY [Bug 18292] New: - 24 bit PNG not displayed correctly
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT http://nagoya.apache.org/bugzilla/show_bug.cgi?id=18292. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE. http://nagoya.apache.org/bugzilla/show_bug.cgi?id=18292 24 bit PNG not displayed correctly Summary: 24 bit PNG not displayed correctly Product: Fop Version: 0.20.4 Platform: PC OS/Version: Windows NT/2K Status: NEW Severity: Normal Priority: Other Component: pdf renderer AssignedTo: [EMAIL PROTECTED] ReportedBy: [EMAIL PROTECTED] When inserting a 24-bit .PNG file into a pdf, the transpancy is displayed a black. 8-bit .png files display correctly. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
cvs commit: xml-fop/src/documentation/content/xdocs/design book.xml architecture.xml
vmote 2003/03/24 13:37:20 Modified:src/documentation/content/xdocs/design book.xml architecture.xml Log: Change title of architecture.xml to reflect its orientation toward implementation details. Flesh out the comments in the startup and FO Tree sections. Revision ChangesPath 1.6 +1 -1 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.5 retrieving revision 1.6 diff -u -r1.5 -r1.6 --- book.xml 2 Jan 2003 12:59:30 - 1.5 +++ book.xml 24 Mar 2003 21:37:20 - 1.6 @@ -15,7 +15,7 @@ menu-item label=Understanding href=understanding/index.html/ /menu menu label=Overview - menu-item label=Architecture href=architecture.html/ + menu-item label=Architecture Implementation href=architecture.html/ /menu menu label=Sections menu-item label=FO Tree href=fotree.html/ 1.4 +50 -73xml-fop/src/documentation/content/xdocs/design/architecture.xml Index: architecture.xml === RCS file: /home/cvs/xml-fop/src/documentation/content/xdocs/design/architecture.xml,v retrieving revision 1.3 retrieving revision 1.4 diff -u -r1.3 -r1.4 --- architecture.xml 2 Jan 2003 12:59:30 - 1.3 +++ architecture.xml 24 Mar 2003 21:37:20 - 1.4 @@ -1,80 +1,60 @@ ?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; - document -header -titleArchitecture/title -subtitleArchitecture information for FOP/subtitle -authors -person name=Arved Sandstrom email=/ -/authors -/header - -body - -section - titleFOP Mechanics/title - -section - titleIntroduction/title -p -The overall process is controlled by emorg.apache.fop.apps.Driver/em. -This class handles the FO Tree building, structure handler, renderers, output and logging. -/p -p -The process in general is that the FO document is sent to the tree -builder via SAX events. This creates an FO Tree. The FO Tree is then -handled by the layout processor which converts the FO Tree into an area -tree. This area tree is then given to the renderer and the renderer converts -the area tree into a stream of data containing the output document. -/p -/section - -section - titleFormatting Object Tree/title -p -The class emorg.apache.fop.fo.FOTreeBuilder/em is responsible for -actually constructing the FO tree. The key SAX events used are /p -pcodestartElement()/code,/p -pcodeendElement()/code and codecharacters()/code./p - -/section - -section - titleLayout/title -p -The layout managers handle the layout. They take an FO tree and construct -the area tree. -The layout process involves finding out where line breaks and page -breaks should be made. The areas are then added to the page. The -static areas can the be done for all the static regions. -Completed pages are then added to the area tree, the area tree can -then deal with the page. -/p -/section - -section - titleArea Tree/title -p -The area tree is a data structure designed to hold the page areas. + header +titleImplementation Overview/title +subtitleFollowing a Document Through FOP/subtitle +authors + person name=Arved Sandstrom email=/ +/authors + /header + body +pThe purpose of this document is to tie together the FOP design (interface) with some of the key points where control is passed within FOP (implementation), so that developers can quickly find the section of code that is relevant to their needs. The process described is for a typical command-line document. All class names are in org.apache.fop unless otherwise designated./p +section + titleOverview/title + pThe input FO document is sent to the FO tree builder via SAX events. Fragments of an FO Tree are built from this process. As each page-sequence element is completed, it is passed to a layout processor, which in turn converts it into an Area Tree. The Area Tree is then given to the Renderer, which converts it into a stream of data containing the output document. The sections below will provide additional details./p +/section +section + titleStartup/title + ul +liThe job starts in apps.Fop.main()./li +liControl is passed to apps.CommandLineStarter.run()./li +liControl is passed to emapps.Driver.render()/em. This class fires up a SAX parser, the events from which indirectly control
block rendering problem with 0.20.5rc2
The following fo apparently causes the last line of text from the text area of the parent fo:block to be rendered twice, once before the child fo:block and once after it. That is, supposing that deducted as an itemized deduction is the last line of the parent block, this same text will be repeated after the child block element. fo:block fo:leader leader-length=6.0mm leader-pattern=space/ fo:inline font-weight=boldDISCUSSION:/fo:inline his/her employer for the expenses and the expenses equal the reimbursement. All other business expenses incurred by employees (except those incurred by a qualified performing artist) are deducted from adjusted gross income [Sec. 62(a)]. Justins gross income was $31,500 ($30,000 salary + $1,500 expense allowance). When the employee receives an allowance and does not account to the employer for the expenses, the expense allowance is included in gross income, and the expenses are deducted as an itemized deduction. fo:block line-height=1em + 1pt space-after=0mm space-before=0mmfo:leader rule-style=none leader-length=5mm/Therefore, Justins adjusted gross income is $31,500, and his travel, lodging, and entertainment expenses are deductible from adjusted gross income./fo:block /fo:block The same behavior occurs if the child element is an fo:table as well. This did not occur with version 0.20.4. Any help with this will be appreciated, matthew l. avizinis Gleim Publications, Inc. http://www.gleim.com - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
admin tab
I am tempted to add an Admin tab to our web site for pages dealing with administrative matters. For example, our readme that tells how to rebuild the web site could go there. Christian may have notes on creating builds that could go there as well. I would like to document the link to the cocoondev.org (I think) site where our web site is generated and built. Since at least some of the information on such page(s) would not be suitable for public consumption (ie. triggering web site updates), does anyone know whether the infrastructure is in place to restrict access to certain pages, presumably based on an apache login password? Alternative to having restricted pages on the public site would be to have a virtual intranet on another server (?). Victor Mote (mailto:[EMAIL PROTECTED]) 2025 Eddington Way Colorado Springs, Colorado 80916 Voice +1 (719) 622-0650 Fax +1 (720) 293-0044 - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
cvs commit: xml-fop/src/documentation/content/xdocs/design architecture.xml
vmote 2003/03/24 14:22:40 Modified:src/documentation/content/xdocs/design architecture.xml Log: Add some em tags for consistency. Revision ChangesPath 1.5 +4 -4 xml-fop/src/documentation/content/xdocs/design/architecture.xml Index: architecture.xml === RCS file: /home/cvs/xml-fop/src/documentation/content/xdocs/design/architecture.xml,v retrieving revision 1.4 retrieving revision 1.5 diff -u -r1.4 -r1.5 --- architecture.xml 24 Mar 2003 21:37:20 - 1.4 +++ architecture.xml 24 Mar 2003 22:22:40 - 1.5 @@ -18,8 +18,8 @@ section titleStartup/title ul -liThe job starts in apps.Fop.main()./li -liControl is passed to apps.CommandLineStarter.run()./li +liThe job starts in emapps.Fop.main()/em./li +liControl is passed to emapps.CommandLineStarter.run()/em./li liControl is passed to emapps.Driver.render()/em. This class fires up a SAX parser, the events from which indirectly control the remaining processing, including building the FO Tree, building the Area Tree, rendering, output and logging./li /ul /section @@ -27,8 +27,8 @@ titleFormatting Object Tree/title ul liThe SAX events that the parser creates are handled by emfo.FOTreeBuilder/em, which uses codestartElement()/code, codeendElement()/code, and codecharacters()/code methods to build the FO Tree./li -lifo.FOTreeBuilder.endElement() runs the end() method for each node as it is created. The fo.pagination.PageSequence class overrides this end() method to run apps.LayoutHandler.endPageSequence()./li -liapps.LayoutHandler.endPageSequence() in turn runs fo.pagination.PageSequence.format, which drives the layout process./li +liemfo.FOTreeBuilder.endElement()/em runs the end() method for each node as it is created. The emfo.pagination.PageSequence/em class overrides this end() method to run emapps.LayoutHandler.endPageSequence()/em./li +liemapps.LayoutHandler.endPageSequence()/em in turn runs emfo.pagination.PageSequence.format()/em, which drives the layout process./li /ul /section section - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
cvs commit: xml-fop/src/documentation/content/xdocs/dev faq.xml
vmote 2003/03/24 15:04:25 Modified:src/documentation/content/xdocs/dev faq.xml Log: Move developer FAQs to the Developer FAQ document. Revision ChangesPath 1.7 +11 -1405 xml-fop/src/documentation/content/xdocs/dev/faq.xml Index: faq.xml === RCS file: /home/cvs/xml-fop/src/documentation/content/xdocs/dev/faq.xml,v retrieving revision 1.6 retrieving revision 1.7 diff -u -r1.6 -r1.7 --- faq.xml 18 Mar 2003 16:48:15 - 1.6 +++ faq.xml 24 Mar 2003 23:04:25 - 1.7 @@ -2,1418 +2,24 @@ !DOCTYPE faqs PUBLIC -//APACHE//DTD FAQ V1.1//EN http://cvs.apache.org/viewcvs.cgi/*checkout*/xml-forrest/src/resources/schema/dtd/faq-v11.dtd; -faqs title=FOP FAQ - part -titleGeneral questions/title -faq - questionWhat is FOP?/question - answer - p -FOP is a print formatter for jump href=#XSLFOXSL formatting -objects/jump. - /p - p -It can be used to render an XML file containing XSL formatting objects -into a page layout. The main target is PDF but other rendering targets -are supported, such as AWT, PCL, text and direct printing. - /p - /answer -/faq -faq - questionWhat can I do with FOP?/question - answer -p - FOP provides both an application and a library that converts an XSL FO - document into paginated output. -/p -p - The FOP command line application can be directly used to transform XML - into PDF, PostScript, PCL and other formats, there is also an AWT - based viewer integrated. -/p -p - The library can be used in servlets and other Java applications. -/p - /answer -/faq -faq - questionWhat does FOP stand for?/question - answer -p - It's an acronym for strongF/strongormatting - strongO/strongbject strongP/strongrocessor -/p - /answer -/faq -faq - questionHow does FOP interact with other Apache Projects?/question - answer -p - FOP is distributed with link - href=http://xml.apache.org/cocoon;Cocoon/link as a PDF serializer - for XSL (FO) documents. -/p -p - link href=http://xml.apache.org/batik;Batik/link can be used with - FOP to link - href=http://xml.apache.org/batik/svgrasterizer.html;transcode an SVG - image/link into a PDF document. -/p - /answer -/faq -faq - questionWhat is XSL?/question - answer -p - XSL is a W3C standard concerned with publishing XML documents. It - consists of two parts: jump href=#XSLTXSLT/jump and jump - href=#XSLFOXSLFO/jump. The acronym expands to - estrongX/strongtensible strongS/strongtylesheet - strongL/stronganguage. -/p - /answer -/faq -faq id=XSLFO - questionWhat is XSLFO?/question - answer -p - XSLFO is an XML vocabulary that is used to specify a pagination and - other styling for page layout output. The acronym ldquo;FOrdquo; stands for - strongF/strongormatting strongO/strongbjects. XSLFO can be - used in conjunction with jump href=#XSLTXSLT/jump to convert - from any XML format into a paginated layout ready for printing or - displaying. -/p -p - XSLFO defines a set of elements in XML that describes the way pages - are set up. The contents of the pages are filled from flows. There can - be static flows that appear on every page (for headers and footers) - and the main flow which fills the body of the page. -/p -p - Synonyms: XSL FO, XSL (FO), XSL:FO, XSL-FO, Formatting Objects -/p - /answer -/faq -faq id=XSLT - questionWhat is XSLT?/question - answer -p - XSLT describes the transformation of arbitrary XML input into other - XML (like XSLFO), HTML or plain text. The ldquo;Trdquo; comes from - strongT/strongransformation. For historical reasons, a - transformation is often also called a ldquo;style sheetrdquo;. -/p -p - Synonyms: XSL transformation, XSL:T, XSL style sheet. -/p - /answer -/faq -faq - questionHow can I contribute?/question - answer -p - There is always plenty of things to do. See link href=../limitations.htmllimitations/link - and link href=../resources.htmlbugzilla/link. -/p - /answer -/faq - /part
cvs commit: xml-fop/src/documentation/content/xdocs/dev faq.xml
vmote 2003/03/24 15:20:11 Modified:src/documentation/content/xdocs/dev faq.xml Log: Fix URLs and add missing ids. Revision ChangesPath 1.8 +5 -5 xml-fop/src/documentation/content/xdocs/dev/faq.xml Index: faq.xml === RCS file: /home/cvs/xml-fop/src/documentation/content/xdocs/dev/faq.xml,v retrieving revision 1.7 retrieving revision 1.8 diff -u -r1.7 -r1.8 --- faq.xml 24 Mar 2003 23:04:25 - 1.7 +++ faq.xml 24 Mar 2003 23:20:10 - 1.8 @@ -3,20 +3,20 @@ http://cvs.apache.org/viewcvs.cgi/*checkout*/xml-forrest/src/resources/schema/dtd/faq-v11.dtd; faqs title=FOP Developer FAQ - part id=documentation + part id=part_documentation titleDocumentation/title faq id=javadoc_location questionHow do I get the javadocs for FOP?/question answer -pCurrently, the only way to get FOP javadocs is to link href=download.html -Download the source code/link and then link href=compiling.htmlBuild +pCurrently, the only way to get FOP javadocs is to link href=../download.html +Download the source code/link and then link href=../compiling.htmlBuild FOP/link using the ant build task javadocs./p /answer /faq /part - part + part id=part_further_help titleFurther Help/title -faq +faq id=other_faqs questionI don't see my question addressed here. Are there other FAQs?/question answer pYes. See also the link href=../faq.htmlFOP General FAQs/link./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 book.xml
vmote 2003/03/24 16:30:18 Modified:src/documentation/content/xdocs/dev book.xml Added: src/documentation/content/xdocs/dev tools.xml Log: Add a tools page for FOP-related comments about development tools. Revision ChangesPath 1.9 +1 -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.8 retrieving revision 1.9 diff -u -r1.8 -r1.9 --- book.xml 23 Dec 2002 10:35:13 - 1.8 +++ book.xml 25 Mar 2003 00:30:18 - 1.9 @@ -26,5 +26,6 @@ menu label=Developers external label=FOP Wiki href=http://nagoya.apache.org/wiki/apachewiki.cgi?FOPProjectPages/ menu-item label=Design href=../design/index.html/ + menu-item label=Tools href=tools.html/ /menu /book 1.1 xml-fop/src/documentation/content/xdocs/dev/tools.xml Index: tools.xml === ?xml version=1.0 encoding=UTF-8? !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; document header titleDeveloper Tools/title /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 titleCVS/title pYou will need a CVS client to be able to gain access to the FOP repository./p pTo create a patch to be submitted for consideration to be committed, do the following:/p ul licodecd/code to the directory above the xml-fop directory that was created when you checked out the code. You can actually codecd/code farther down the directory tree if your changes do not comprehend the entire FOP directory structure. However, don't go any deeper than will allow all of your changes to be included in one diff. Also, adjust/li liRun: codecvs -q diff -wu xml-fop/code/li liIf you are running WinCVS, select Admin/Command Line for a console in which to key the above command./li 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 titleIntegrated Development Environments (IDEs)/title pAn IDE is not required, but will generally be found to be helpful, especially for serious debugging and refactoring./p pBorland's JBuilder 7/8 does not support Ant builds unless you have the Enterprise Edition (which is quite expensive). This causes problems with any code that is generated by the Ant build. First, you must run the Ant build before you can use the IDE. Second, when you are editing in the IDE, you must be editing the generated files, which means that you must make any changes to the source files in another editor. This is less serious for development on the trunk, but in the maintenance branch, all source files were generated./p pSun ONE Studio Four does support Ant, but seems to use a built-in version, and as of this writing chokes on the FOP build file, saying that it is not valid. There is awkward because there is no official DTD for Ant, and it may be merely an Ant version issue./p /section /body /document - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
cvs commit: xml-fop build.xml
chrisg 2003/03/24 17:31:00
Modified:.Tag: fop-0_20_2-maintain build.xml
Log:
fixed manifest classpath
PR: 17311
Revision ChangesPath
No revision
No revision
1.44.2.40 +1 -1 xml-fop/build.xml
Index: build.xml
===
RCS file: /home/cvs/xml-fop/build.xml,v
retrieving revision 1.44.2.39
retrieving revision 1.44.2.40
diff -u -r1.44.2.39 -r1.44.2.40
--- build.xml 13 Mar 2003 21:55:09 - 1.44.2.39
+++ build.xml 25 Mar 2003 01:31:00 - 1.44.2.40
@@ -285,7 +285,7 @@
--
property name=main.class value=org.apache.fop.apps.Fop/
-property name=runtime.classpath value=xercesImpl-2.0.1.jar
xml-apis.jar xalan-2.3.1.jar batik.jar jimi-1.0.jar
avalon-framework-cvs-20020806.jar/
+property name=runtime.classpath value=xercesImpl-2.2.1.jar xml-apis.jar
xalan-2.4.1.jar batik.jar jimi-1.0.jar avalon-framework-cvs-20020806.jar/
filter filtersfile=${build.codegen}/filter/
/target
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
DO NOT REPLY [Bug 17311] - Manifest file class path contains outdated entries
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT http://nagoya.apache.org/bugzilla/show_bug.cgi?id=17311. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE. http://nagoya.apache.org/bugzilla/show_bug.cgi?id=17311 Manifest file class path contains outdated entries [EMAIL PROTECTED] changed: What|Removed |Added Status|NEW |RESOLVED Resolution||FIXED --- Additional Comments From [EMAIL PROTECTED] 2003-03-25 01:47 --- Fixed in CVS. Thanks for reporting - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
DO NOT REPLY [Bug 16957] - Broken link - please change
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT http://nagoya.apache.org/bugzilla/show_bug.cgi?id=16957. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE. http://nagoya.apache.org/bugzilla/show_bug.cgi?id=16957 Broken link - please change [EMAIL PROTECTED] changed: What|Removed |Added Status|NEW |RESOLVED Resolution||FIXED --- Additional Comments From [EMAIL PROTECTED] 2003-03-25 01:51 --- Thanks for reporting (someone else already fixed it) - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
cvs commit: xml-fop/src/documentation/content/xdocs implemented.xml
chrisg 2003/03/24 17:57:56 Modified:src/documentation/content/xdocs implemented.xml Log: fixed typos on implemented.xml PR: 18023 Submitted by: [EMAIL PROTECTED] (Glen Mazza) Revision ChangesPath 1.4 +10 -10xml-fop/src/documentation/content/xdocs/implemented.xml Index: implemented.xml === RCS file: /home/cvs/xml-fop/src/documentation/content/xdocs/implemented.xml,v retrieving revision 1.3 retrieving revision 1.4 diff -u -r1.3 -r1.4 --- implemented.xml 29 Nov 2002 22:00:31 - 1.3 +++ implemented.xml 25 Mar 2003 01:57:56 - 1.4 @@ -12,15 +12,15 @@ section titleWhat's Implemented?/title pThe following formatting objects and properties of the XSL-FO 1.0 - W3C Recommandation are implemented. Please have also a look at the + W3C Recommendation are implemented. Please also have a look at the section on jump href=limitations.htmllimitations/jump. /p /section section title1) Formatting Objects/title -pThis section follows the table B Formatting Object Summary in the xsl:fo specification. At the - end of each sub-section you find listed what is not implemented./p - +pThis section follows the tables in + jump href=http://www.w3.org/TR/2001/REC-xsl-20011015/sliceB.html#FO-summary;Appendix B, Formatting Object Summary/jump of the XSL-FO specification. + Items that are not currently implemented are listed at the end of each sub-section./p section titleB.1 Declaration and Pagination and Layout Formatting Objects/title ul @@ -119,7 +119,7 @@ section title2) Properties/title - pProperty values can be computed. Compound properties are also understood by Fop./p + pProperty values can be computed. Compound properties are also understood by FOP./p ul libackground-color /li libackground-image /li @@ -239,15 +239,15 @@ /section section -title3)SVG Support/title +title3) SVG Support/title p FOP uses jump href=http://xml.apache.org/batik/;Batik/jump directly for its SVG support. Therefore FOP supports the same -elements and properties as are supported by Batik. As FOP is designed for -rendering to a static medium then only static SVG is rendered. +elements and properties as are supported by Batik. Because FOP is designed for +rendering to a static medium, only static SVG is supported. /p p -Due to some limitations in PDF some SVG images, particularly ones with effects -or transparency, may not come out correctly. The images should still be renderedcorrectly for the AWT and Print renderers. +Due to certain PDF limitations, some SVG images, particularly those with filter effects +or transparency, may not come out correctly. However, these images should still be rendered correctly by the AWT and Print renderers. /p /section /section - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
DO NOT REPLY [Bug 18292] - 24 bit PNG not displayed correctly
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT http://nagoya.apache.org/bugzilla/show_bug.cgi?id=18292. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE. http://nagoya.apache.org/bugzilla/show_bug.cgi?id=18292 24 bit PNG not displayed correctly --- Additional Comments From [EMAIL PROTECTED] 2003-03-25 02:01 --- I'm guessing that you're using Jimi for the PNG images (as FOP 0.20.4 isn't compiled with JAI support) Please try FOP 0.20.5rc2 with JAI - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
cvs commit: xml-fop/src/documentation/content/xdocs/dev tools.xml
vmote 2003/03/24 18:17:55 Modified:src/documentation/content/xdocs/dev tools.xml Log: Fix typo Revision ChangesPath 1.4 +1 -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.3 retrieving revision 1.4 diff -u -r1.3 -r1.4 --- tools.xml 25 Mar 2003 02:04:43 - 1.3 +++ tools.xml 25 Mar 2003 02:17:55 - 1.4 @@ -16,7 +16,7 @@ pRegardless of what platform you develop on, please be sure to submit patches that use Unix line endings. If you are using WinCVS, check code out this way by going to the Admin / Preferences menu item, clicking on the Globals tab, then select the Checkout text files with the Unix LF (0xa) option. You will also need to use an editor that supports opening and saving files using Unix line endings./p /section section id=wincvs_download -titleStep-by-step instructions for downloading FOP using WinCVS:/title +titleStep-by-step instructions for downloading FOP using WinCVS/title ul liSelect Create / Checkout Module menu item./li li“Checkout Settings” Tab: - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Encryption
On Tue, Mar 25, 2003 at 01:56:04AM +1000, Peter B. West wrote: Victor Mote wrote: My understanding is as follows: 1. The refresh button on the http://forrestbot.cocoondev.org site will take the contents at cvs.apache.org/cvs/xml-fop as input, and generate the web site. That is what is displayed at http://forrestbot.cocoondev.org/site/xml-fop. 2. The publish button at http://forrestbot.cocoondev.org seems to actually update the cvs.apache.org/cvs/xml-site/targets/fop directory, checking the output from refresh into that repository. This is somewhat contrary to the text that appears on http://forrestbot.cocoondev.org. This step seems to have some problems. I have just gone through the cycle of building locally, checking the changes into HEAD, getting forrestbot to refresh, checking the just-constucted site, and then getting forrestbot to publish. I had problems on the live site that I did not see locally or on the forrestbot driver pages at forrestbot.cocoondev.org. Specifically, an old copy of my javascript file was in service. The script which pulls files from CVS and publishes them is only run every X hours, so the live site probably just hasn't caught up. I've verified that the codedisplay.js files displayed by forrestbot.cocoondev.org and those in xml-site/targets/fop CVS are identical. I have noticed that redundant files do not seem to be cleaned up in the process either - they just hang around. Yes, detecting when a file *isn't* generated is harder than detecting when one is, and the price of making a mistake is much greater, so I didn't attempt it. --Jeff - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
Re: Development/Redesign tabs
On Mon, Mar 24, 2003 at 03:36:30PM -0700, Victor Mote wrote: I made some decent progress today on getting my head into the trunk code, and to document some of what I have learned. I am still confused by the Development and Redesign tabs. At first, I thought that maybe Development was for those who might be developing on the maintenance branch, and Redesign for those on the trunk, but the title to the index document under Development seems to belie that. I see that we have some problems with the left nav bar that result from our directory structure. For example, first click http://xml.apache.org/fop/design/index.html, then click on the tab entitled Understanding, and watch the left nav bar change, which you would think it should not. Perhaps we made the two tabs to ease that problem? Is 'understanding' a subsection of 'design', as the directory structure suggests? The menu changes because there are two different book.xml files (which generate the menus): src/documentation/content/xdocs/design/book.xml src/documentation/content/xdocs/design/understanding/book.xml As for tabs, they are completely reactive things. The tab with the longest matching @dir is on. So FOP's tabs.xml has: tab label=Home dir=/ tab label=Development dir=dev// tab label=Redesign dir=design// tab label=alt design dir=design/alt.design// When viewing design/* or design/understanding/*, the longest matching tab is Redesign. HTH, --Jeff Assuming that I can find the Forrest solution to that problem, is there any objection to merging these two tabs into one entitled Development? Victor Mote (mailto:[EMAIL PROTECTED]) 2025 Eddington Way Colorado Springs, Colorado 80916 Voice +1 (719) 622-0650 Fax +1 (720) 293-0044 - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
Re: logo contest
As the modified logo is so popular, we should probably include it in the list for voting, and let those who like it change their vote. Let's make it #30. Peter Oleg Tkachenko wrote: J.Pietschmann wrote: Victor, since one of my choices was also #7 with a dislike of the font i decided to post a revised version. Oooh. I like that a lot. Definitely my favorite. Thanks for submitting that. Me too! Well, I like the idea of inkstand and feather also. What about combining it with another logo? -- Peter B. West [EMAIL PROTECTED] http://www.powerup.com.au/~pbwest/ Lord, to whom shall we go? - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
cvs commit: xml-fop/src/documentation/content/xdocs/dev tools.xml
vmote 2003/03/24 18:48:06 Modified:src/documentation/content/xdocs/dev tools.xml Log: Add links to some other Apache sites, per Christian's suggestion. Revision ChangesPath 1.5 +5 -0 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.4 retrieving revision 1.5 diff -u -r1.4 -r1.5 --- tools.xml 25 Mar 2003 02:17:55 - 1.4 +++ tools.xml 25 Mar 2003 02:48:06 - 1.5 @@ -7,6 +7,10 @@ /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=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 +/section section id=cvs titleConcurrent Versions System (CVS)/title section id=cvs_general @@ -66,6 +70,7 @@ section id=ide titleIntegrated Development Environments (IDEs)/title pAn IDE is not required, but will generally be found to be helpful, especially for serious debugging and refactoring./p + pSee link href=http://jakarta.apache.org/site/idedevelopers.html;the Apache Jakarta IDE Developer's Guide/link for useful information on Java IDEs./p pBorland's JBuilder 7/8 does not support Ant builds unless you have the Enterprise Edition (which is quite expensive). This causes problems with any code that is generated by the Ant build. First, you must run the Ant build before you can use the IDE. Second, when you are editing in the IDE, you must be editing the generated files, which means that you must make any changes to the source files in another editor. This is less serious for development on the trunk, but in the maintenance branch, all source files were generated./p pSun ONE Studio Four does support Ant, but seems to use a built-in version, and as of this writing chokes on the FOP build file, saying that it is not valid. There is awkward because there is no official DTD for Ant, and it may be merely an Ant version issue./p /section - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: Development/Redesign tabs
Jeff Turner wrote: On Mon, Mar 24, 2003 at 03:36:30PM -0700, Victor Mote wrote: I made some decent progress today on getting my head into the trunk code, and to document some of what I have learned. I am still confused by the Development and Redesign tabs. At first, I thought that maybe Development was for those who might be developing on the maintenance branch, and Redesign for those on the trunk, but the title to the index document under Development seems to belie that. I see that we have some problems with the left nav bar that result from our directory structure. For example, first click http://xml.apache.org/fop/design/index.html, then click on the tab entitled Understanding, and watch the left nav bar change, which you would think it should not. Perhaps we made the two tabs to ease that problem? Is 'understanding' a subsection of 'design', as the directory structure suggests? Yes, but they are probably logically part of the same tab/left nav bar on the web site. The menu changes because there are two different book.xml files (which generate the menus): src/documentation/content/xdocs/design/book.xml src/documentation/content/xdocs/design/understanding/book.xml I understood that, and I assume that the book.xml that is in the same directory as document.xml is the menu that attaches to document.html when it is generated. The question then is, can that be overridden? As for tabs, they are completely reactive things. The tab with the longest matching @dir is on. So FOP's tabs.xml has: tab label=Home dir=/ tab label=Development dir=dev// tab label=Redesign dir=design// tab label=alt design dir=design/alt.design// When viewing design/* or design/understanding/*, the longest matching tab is Redesign. Interesting unexpected. Now I see why I got the counter-intuitive effect that I saw. I don't know how well it fits with the Cocoon processing model (I have a book on order that I hope will connect a few dots about Cocoon for me), but a more clear parent-child hierarchical relationship in the site setup would seem to be more flexible. In my mind, the left nav bar is a subset of the tab that it is under. I might be able to be talked out of that. I guess I would like to see: site tab desc=Tab 1 menu desc=Tab 1, Menu 1 doc desc=Doc 1 path=abc.html/ doc desc=Doc 2 path=xyz/abc.html/ /menu menu desc=Tab 1, Menu 2 doc desc=Doc 3 path=xyz/pdq/abc.html/ /menu /tab tabTab 2/tab /site Each document would get tab nav information from the structure that it is in. The above separates the directory structure from the web site hierarchy. Although this seems good to me, it may rob Cocoon or Forrest of some of their power (I'm not sure yet), and there may be other good reasons not to do it. Anyway, thanks for the info. That does save me a bunch of work. Victor Mote - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
