At 18:48 12.05.2002, Stas Bekman wrote:
I thought of:
guide/index.html: ----------------- Part II: OS-specific information
Win32 OSX ...
each pointing to the docset of its own. So all you need to do is
1. mv docs/1.0/win32 docs/1.0/guide/win32
2. remove it from docs/1.0/config.cfg and put it into docs/1.0/guide/config.cfg
3. find . -type f -exec perl pi -e 's|win32::|guide::win32::|' {} \;
After thinking some more I've realized that this doesn't solve anything. Since the os specific docsets are nested (and aren't a core part of the "guide" docset) they aren't becoming a part of the top level PDF. So they are going to be separate in any case. I guess in that case docs/1.0/os is better than, as suggested by Per Einar in first place.
Unless you have better ideas.
Another related question: Should each platform specific docs go into separate docsets, so each can be downloaded as a separate PDF. Or putting them all into one docset, with the overhead of having all the OSs in one doc.
I think they should be separate docsets.
__________________________________________________________________ Stas Bekman JAm_pH ------> Just Another mod_perl Hacker http://stason.org/ mod_perl Guide ---> http://perl.apache.org mailto:[EMAIL PROTECTED] http://use.perl.org http://apacheweek.com http://modperlbook.org http://apache.org http://ticketmaster.com
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
