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
