Howtos not in community folder

["Vladimir R. Bossicard" <vl...@bossicard.com>]

Hi all,

I have just figured out that the how-tos are not rendered properly if 
they are not placed into a subfolder "community/howto".  Just change 
community into community2, fix book.xml and see what happens :-)

Although I upgrated to the new forrest cvs and I don't know how I did it 
but I got all the files in my src/documentation overwritten by the 
standard forrest website.  God I love CVS :-)

-Vladimir

-- 
Vladimir R. Bossicard
www.bossicard.com

Re: Howtos not in community folder

["Vladimir R. Bossicard" <vl...@bossicard.com>]

> So if you rename community to community2, the first rules will no longer
> apply, and the second rule doesn't match because the actual howtos are in
> howto/*/*, not howto/*

That's effectively obvious.  How could I have missed it? :-)

But Forrest is still a great product.  The finesses are sometimes 
difficult to find out.

-Vladimir

-- 
Vladimir R. Bossicard
www.bossicard.com

Re: Howtos not in community folder

[Jeff Turner <je...@apache.org>]

On Sun, Nov 17, 2002 at 12:47:02AM -0800, Vladimir R. Bossicard wrote:
> >However is another sitemap rule matching **howto/*:
> >
> > <!-- Any other howto directories get transformed, without revisions -->
> >  <map:match pattern="body-**howto/*.xml">
> >
> >So if you don't need revisions, any directory ending with 'howto' will
> >have its contents interpreted as howto docs.
> 
> Sorry it's not the experience I made.  Could you try to move community 
> into community2 and see if your howtos are still interpreted.

It's fairly complicated.. there are two sitemap rules:

1) community/*/*/**

The pipeline does two things:
 - applies stylesheet {1}2document.xsl to source XML.  Eg for
   community/howto/*/**, {1} is 'howto' and the pipeline applies
   howto2document.xsl
 - merges 'revisions' into the XML.

2) **howto/*
 - has a hardcoded rule to apply howto2document.xsl to the XML to
   generate HTML and PDF.

So if you rename community to community2, the first rules will no longer
apply, and the second rule doesn't match because the actual howtos are in
howto/*/*, not howto/*


--Jeff

Re: Howtos not in community folder

["Vladimir R. Bossicard" <vl...@bossicard.com>]

> However is another sitemap rule matching **howto/*:
> 
>  <!-- Any other howto directories get transformed, without revisions -->
>   <map:match pattern="body-**howto/*.xml">
> 
> So if you don't need revisions, any directory ending with 'howto' will
> have its contents interpreted as howto docs.

Sorry it's not the experience I made.  Could you try to move community 
into community2 and see if your howtos are still interpreted. I just 
tried it with the xml-xindice site and they are not interpreted, 
although I still have the howto directory.

> Check CVS/Repository.. it should not say 'xml-forrest' :P

I checked it and it's still my brave xml-xindice site.  Next time I 
upgrade Forrest, I'll try to reproduce it.

-Vladimir

-- 
Vladimir R. Bossicard
www.bossicard.com

Re: Howtos not in community folder

[Jeff Turner <je...@apache.org>]

On Sat, Nov 16, 2002 at 08:53:13PM -0800, Vladimir R. Bossicard wrote:
> Hi all,
> 
> I have just figured out that the how-tos are not rendered properly if 
> they are not placed into a subfolder "community/howto".  Just change 
> community into community2, fix book.xml and see what happens :-)

Yes, there's a sitemap rule matching 'community/howto/*'.

However is another sitemap rule matching **howto/*:

 <!-- Any other howto directories get transformed, without revisions -->
  <map:match pattern="body-**howto/*.xml">

So if you don't need revisions, any directory ending with 'howto' will
have its contents interpreted as howto docs.

> Although I upgrated to the new forrest cvs and I don't know how I did it 
> but I got all the files in my src/documentation overwritten by the 
> standard forrest website.  God I love CVS :-)

Check CVS/Repository.. it should not say 'xml-forrest' :P

--Jeff

> 
> -Vladimir
> 
> -- 
> Vladimir R. Bossicard
> www.bossicard.com
>