Re: TOC in FAQ

2005-05-27 Thread The Web Maestro


On May 26, 2005, at 11:34 PM, David Crossley wrote:

The Web Maestro wrote:

I don't believe we're using any special project-specific items except
for the compliance2*.xsl files in ViewCVS here:



As for the fop-specific sitemap.xmap file, I believe it's been  
replaced

with the standard version from the Forrest distribution. IIRC, that's
one of the 'tricks' we took to making xml-fop work again.


Are you sure that you don't use a sitemap.xmap file? I remember long
discussions with you late last year on our dev list:
"Subject: "xml-fop Build Failed". It involved using special sitemap
matches to handle your special compliance2html document. IIRC you
had it in your local working copy, but it wasn't in the FOP CVS.
It would probably be at src/documentation/sitemap.xmap


Actually, I was a little off above. I think the way we got forrest to  
generate xml-fop/build/site was to remove the FOP-specific sitemap.xmap  
file (among other changes). Just the same, here're a couple of useful  
commands I just ran from my xml-fop dir:


[EMAIL PROTECTED] xml-fop]$ pwd
/Users/Shared/_WebDLs/_repos/xml-fop
[EMAIL PROTECTED] xml-fop]$ ls src/documentation/
CVS.sandboxinfo  classes  cocoon.diff  content  resources  skinconf.xml
[EMAIL PROTECTED] xml-fop]$

[EMAIL PROTECTED] xml-fop]$ find . -iname sitemap.*
./build/webapp/WEB-INF/logs/sitemap.log
[EMAIL PROTECTED] xml-fop]$ find . -iname *.xmap
[EMAIL PROTECTED] xml-fop]$


If you don't have a project sitemap then great, we can rule that out
as a possible source of your FAQ ToC problem, and close FOR-507.


Sounds good. Go ahead and close the issue (I just tried to close it,  
but I don't appear to have perms.)



FWIW, I just created a new Task/Issue in CocoonDev issues ([#FOR-507]
xml-fop *.xmap files). I've attached my $FORREST_HOME/context/*.xmap
files to the issue.


No that doesn't help. There is no difference between those and
the default forrest 0.6 core sitemaps. It was good to know that they
haven't been changed, but i wasn't actually talking about the
core sitemaps anyway, i was referring to a project-specific sitemap
(discussed above).

--David


As I expected. I thought I'd upload that just to be on the safe side.


I had a colleague try, and the TOC doesn't generate for him either...


FWIW, the 'colleague' was Jeremias.

Regards,

Web Maestro Clay
--
<[EMAIL PROTECTED]> - 
My religion is simple. My religion is kindness.
- HH The 14th Dalai Lama of Tibet



Re: TOC in FAQ

2005-05-26 Thread David Crossley
The Web Maestro wrote:
> David Crossley wrote:
> >David Crossley wrote:
> >
> >At one stage you were using a project-specific sitemap
> >for your FOP website, IIRC. If you are still, i wonder
> >if that has an extraneous match that is interfering with
> >the faq pipeline.
> 
> I don't believe we're using any special project-specific items except  
> for the compliance2*.xsl files in ViewCVS here:
> 
>  stylesheets/>
> 
> As for the fop-specific sitemap.xmap file, I believe it's been replaced  
> with the standard version from the Forrest distribution. IIRC, that's  
> one of the 'tricks' we took to making xml-fop work again.

Are you sure that you don't use a sitemap.xmap file? I remember long
discussions with you late last year on our dev list:
"Subject: "xml-fop Build Failed". It involved using special sitemap
matches to handle your special compliance2html document. IIRC you
had it in your local working copy, but it wasn't in the FOP CVS.
It would probably be at src/documentation/sitemap.xmap

If you don't have a project sitemap then great, we can rule that out
as a possible source of your FAQ ToC problem, and close FOR-507.

> FWIW, I just created a new Task/Issue in CocoonDev issues ([#FOR-507]  
> xml-fop *.xmap files). I've attached my $FORREST_HOME/context/*.xmap  
> files to the issue.

No that doesn't help. There is no difference between those and
the default forrest 0.6 core sitemaps. It was good to know that they
haven't been changed, but i wasn't actually talking about the
core sitemaps anyway, i was referring to a project-specific sitemap
(discussed above).

--David

> I had a colleague try, and the TOC doesn't generate for him either...
> 
> Regards,
> 
> Web Maestro Clay
> -- 
> <[EMAIL PROTECTED]> - 
> My religion is simple. My religion is kindness.
> - HH The 14th Dalai Lama of Tibet


Re: TOC in FAQ

2005-05-26 Thread The Web Maestro

On May 25, 2005, at 5:04 PM, David Crossley wrote:

David Crossley wrote:

I will try to add your FAQ to another site and see what
your problems are. However, i am not sure if i have the
correct file. Is this it? ...


Forget that - you already told us the URL in your
original message, sorry. Also you proved that your
faq.xml is okay by adding it to a fresh 'forrest seed'.


Thanks for the follow-up!


At one stage you were using a project-specific sitemap
for your FOP website, IIRC. If you are still, i wonder
if that has an extraneous match that is interfering with
the faq pipeline.


I don't believe we're using any special project-specific items except  
for the compliance2*.xsl files in ViewCVS here:





As for the fop-specific sitemap.xmap file, I believe it's been replaced  
with the standard version from the Forrest distribution. IIRC, that's  
one of the 'tricks' we took to making xml-fop work again.


FWIW, I just created a new Task/Issue in CocoonDev issues ([#FOR-507]  
xml-fop *.xmap files). I've attached my $FORREST_HOME/context/*.xmap  
files to the issue.


I had a colleague try, and the TOC doesn't generate for him either...

Regards,

Web Maestro Clay
--
<[EMAIL PROTECTED]> - 
My religion is simple. My religion is kindness.
- HH The 14th Dalai Lama of Tibet



Re: TOC in FAQ

2005-05-25 Thread David Crossley
David Crossley wrote:
> I will try to add your FAQ to another site and see what
> your problems are. However, i am not sure if i have the
> correct file. Is this it? ...

Forget that - you already told us the URL in your
original message, sorry. Also you proved that your
faq.xml is okay by adding it to a fresh 'forrest seed'.

At one stage you were using a project-specific sitemap
for your FOP website, IIRC. If you are still, i wonder
if that has an extraneous match that is interfering with
the faq pipeline.

--David


Re: TOC in FAQ

2005-05-25 Thread David Crossley
The Web Maestro wrote:
> I'm having a problem generating the table of Contents for our FAQs...
[snip]
> 
> I thought, perhaps the problem was related to the DOCTYPE for our  
> faq.xml:
> 
>   
> "http://cvs.apache.org/viewcvs.cgi/*checkout*/xml-forrest/src/core/ 
> context/resources/schema/dtd/faq-v12.dtd">
> 
> But again, the Forrest faq.xml file appears to have the same DOCTYPE.  
> faq.xml also appears to have the same structure. I'd rather not move to  
> the v20 DTD if possible.
[snip]

No it doesn't. Our faq.xml for both 0.6 and 0.7 uses FAQ 1.2 DTD.
I don't know if that makes any difference for you.

I will try to add your FAQ to another site and see what
your problems are. However, i am not sure if i have the
correct file. Is this it? ...

http://cvs.apache.org/viewcvs.cgi/xml-fop/src/documentation/content/xdocs/faq.xml

Also, please do not point directly to the specific URLs on the website
for the DTDs. It will actually have no effect, because the entity resolver
will use the PUBLIC Identifer anyway. But we don't want to confuse
other people.

--David


Re: TOC in FAQ

2005-05-24 Thread The Web Maestro

On May 24, 2005, at 8:30 AM, Ross Gardler wrote:
If you faq.xml works in a seeded site then there must be some  
difference between the fresh-site skinconf.xml and your sites  
skinconf.xml that is preventing the TOC being generated.


Perhaps creating a diff between these two files will show the problem  
(post it here if you can't see it, new eyes may help).


Ross


Here you go:

diff ../xml-fop/src/documentation/skinconf.xml  
src/documentation/skinconf.xml > skinconf_diff.txt


('<' = xml-fop & '>' = seed)

<-- = skinconf_diff.txt = -->

32c32
<   provider="google"/>

---
>   
68,71c68,71
<   FOP
<   FOP (Formatting Objects Processor) is the  
world's first output independent formatter. Output formats   
currently supported include PDF, PCL, PS, SVG, XML (area tree  
representation), Print, AWT, MIF and TXT.  The primary output target is  
PDF.

<   http://xml.apache.org/fop/
<   images/logo.jpg
---
>   MyProject
>   MyProject Description
>   http://myproj.mygroup.org/
>   images/project.png
77,80c77,80
<   Apache XML
<   The Apache XML Project provides  
commercial-quality standards-based XML solutions that are developed in  
an open and cooperative fashion, provides feedback to standards bodies  
(such as IETF and W3C) from an implementation perspective, and is a  
focus for XML-related activities within Apache  
projects

<   http://xml.apache.org/
<   images/group-logo.gif
---
>   MyGroup
>   MyGroup Description
>   http://mygroup.org
>   images/group.png
92,94c92,94
<   
<   1999-2005
<   The Apache Software Foundation.
---
>   
>   2004
>   The Acme Software Foundation.
107,110c107,110
<   
< http://www.apache.org/"/>
< http://xml.apache.org/"/>
< href="http://xmlgraphics.apache.org/"/>

---
>   
> http://www.apache.org/"/>
> http://forrest.apache.org/"/>
> 
125c125
<   
---
>   
130,131c130,132
<   
---
> -->
>href="mailto:[EMAIL PROTECTED] " >
134d134
< -->
153,158d152
< .yes { background-color: #99FF99; }
< .no  { background-color: #FF; }
< .partial { background-color: #CC; }
< .category{ /*background-color: #CFDCED;*/
 
194c188
<
---
> -->
270c264
< 
---
> 
318c312
<   1in
---
>   1.25in
349,362c343,346
< 
---
> 
>Built with Apache Forrest
>   http://forrest.apache.org/
369a351
> -->
370a353
>

=

Here's a link to ViewCVS for our skinconf.xml:




The primary differences I see are the use of the Krysalis portion of  
the 'colors' section (lines 164-196), but that may just be a wild goose  
chase...


Regards,

Web Maestro Clay
--
<[EMAIL PROTECTED]> - 
My religion is simple. My religion is kindness.
- HH The 14th Dalai Lama of Tibet



Re: TOC in FAQ

2005-05-24 Thread Ross Gardler

The Web Maestro wrote:

On May 23, 2005, at 4:48 PM, The Web Maestro wrote:


On May 23, 2005, at 4:22 PM, Ross Gardler wrote:


The Web Maestro wrote:

Thanks... Yeah... what we have is what's shown in the skinconf.xml 
for a fresh 'seed' site:


Unfortunately, we remain with an FAQ page which doesn't generate a TOC.
I'd suspect that somehow the faq.xml file is malformed, however I 
suspect that would generate a validate-xdocs error...



For testing purposes try copying your faq.xml over the one in a seed 
site and see if it works, also try copying the seed site faq into 
your project directory. Does that work?


This will at least help us to narrow down the problem.

Ross



Thanks for the suggestion! It looks like it works this way... (of 
course it gives errors for all the references to xml-fop pages ;-))...



Just to be clear, the FAQ generates a TOC when I copy the file faq.xml 
to a fresh seed site's src/documentation/content/xdocs/faq.xml location. 
I could then manually copy the 'content' to an empty page (so I get the 
'skin'), which is not preferred, but doable.




If you faq.xml works in a seeded site then there must be some difference 
between the fresh-site skinconf.xml and your sites skinconf.xml that is 
preventing the TOC being generated.


Perhaps creating a diff between these two files will show the problem 
(post it here if you can't see it, new eyes may help).


Ross


Re: TOC in FAQ

2005-05-24 Thread The Web Maestro

On May 23, 2005, at 4:48 PM, The Web Maestro wrote:

On May 23, 2005, at 4:22 PM, Ross Gardler wrote:

The Web Maestro wrote:
Thanks... Yeah... what we have is what's shown in the skinconf.xml 
for a fresh 'seed' site:


Unfortunately, we remain with an FAQ page which doesn't generate a 
TOC.
I'd suspect that somehow the faq.xml file is malformed, however I 
suspect that would generate a validate-xdocs error...


For testing purposes try copying your faq.xml over the one in a seed 
site and see if it works, also try copying the seed site faq into 
your project directory. Does that work?


This will at least help us to narrow down the problem.

Ross


Thanks for the suggestion! It looks like it works this way... (of 
course it gives errors for all the references to xml-fop pages ;-))...


Just to be clear, the FAQ generates a TOC when I copy the file faq.xml 
to a fresh seed site's src/documentation/content/xdocs/faq.xml 
location. I could then manually copy the 'content' to an empty page (so 
I get the 'skin'), which is not preferred, but doable.


Regards,

Web Maestro Clay
--
<[EMAIL PROTECTED]> - 
My religion is simple. My religion is kindness.
- HH The 14th Dalai Lama of Tibet



Re: TOC in FAQ

2005-05-23 Thread The Web Maestro

On May 23, 2005, at 4:22 PM, Ross Gardler wrote:

The Web Maestro wrote:
Thanks... Yeah... what we have is what's shown in the skinconf.xml 
for a fresh 'seed' site:


Unfortunately, we remain with an FAQ page which doesn't generate a 
TOC.
I'd suspect that somehow the faq.xml file is malformed, however I 
suspect that would generate a validate-xdocs error...


For testing purposes try copying your faq.xml over the one in a seed 
site and see if it works, also try copying the seed site faq into your 
project directory. Does that work?


This will at least help us to narrow down the problem.

Ross


Thanks for the suggestion! It looks like it works this way... (of 
course it gives errors for all the references to xml-fop pages ;-))...


Regards,

Web Maestro Clay
--
<[EMAIL PROTECTED]> - 
My religion is simple. My religion is kindness.
- HH The 14th Dalai Lama of Tibet



Re: TOC in FAQ

2005-05-23 Thread Ross Gardler

The Web Maestro wrote:

On May 4, 2005, at 7:26 PM, David Crossley wrote:


The Web Maestro wrote:


I'm having a problem generating the table of Contents for our FAQs
page[1], although all other pages contain generated TOCs at the top. I
checked the Forrest 0.6 Menus & Linking page[2], and it indicates that
skinconf.xml should include the element:



The value we have in our skinconf.xml file is:



Although what we have is different, this matches what Forrest appears
to have for its skinconf.xml file in SVN[3]. I tried switching to the
, but I get an error that @level must
be declared. I suspect the Docs are incorrect for Forrest 0.6 (I did
make certain I'm running forrest-0.6):



The docs must be old. I suggest that you follow what is
shown in the skinconf.xml for a fresh site, i.e. cd to a
new directory, do 'forrest seed' and look at its skinconf.xml



Thanks... Yeah... what we have is what's shown in the skinconf.xml for a 
fresh 'seed' site:




Unfortunately, we remain with an FAQ page which doesn't generate a TOC.

I'd suspect that somehow the faq.xml file is malformed, however I 
suspect that would generate a validate-xdocs error...


For testing purposes try copying your faq.xml over the one in a seed 
site and see if it works, also try copying the seed site faq into your 
project directory. Does that work?


This will at least help us to narrow down the problem.

Ross


Re: TOC in FAQ

2005-05-23 Thread The Web Maestro

On May 4, 2005, at 7:26 PM, David Crossley wrote:

The Web Maestro wrote:

I'm having a problem generating the table of Contents for our FAQs
page[1], although all other pages contain generated TOCs at the top. I
checked the Forrest 0.6 Menus & Linking page[2], and it indicates that
skinconf.xml should include the element:



The value we have in our skinconf.xml file is:



Although what we have is different, this matches what Forrest appears
to have for its skinconf.xml file in SVN[3]. I tried switching to the
, but I get an error that @level must
be declared. I suspect the Docs are incorrect for Forrest 0.6 (I did
make certain I'm running forrest-0.6):


The docs must be old. I suggest that you follow what is
shown in the skinconf.xml for a fresh site, i.e. cd to a
new directory, do 'forrest seed' and look at its skinconf.xml


Thanks... Yeah... what we have is what's shown in the skinconf.xml for 
a fresh 'seed' site:




Unfortunately, we remain with an FAQ page which doesn't generate a TOC.

I'd suspect that somehow the faq.xml file is malformed, however I 
suspect that would generate a validate-xdocs error...


Regards,

Web Maestro Clay
--
<[EMAIL PROTECTED]> - 
My religion is simple. My religion is kindness.
- HH The 14th Dalai Lama of Tibet



Re: TOC in FAQ

2005-05-04 Thread David Crossley
The Web Maestro wrote:
> I'm having a problem generating the table of Contents for our FAQs  
> page[1], although all other pages contain generated TOCs at the top. I  
> checked the Forrest 0.6 Menus & Linking page[2], and it indicates that  
> skinconf.xml should include the element:
> 
> 
> 
> The value we have in our skinconf.xml file is:
> 
> 
> 
> Although what we have is different, this matches what Forrest appears  
> to have for its skinconf.xml file in SVN[3]. I tried switching to the  
> , but I get an error that @level must  
> be declared. I suspect the Docs are incorrect for Forrest 0.6 (I did  
> make certain I'm running forrest-0.6):

The docs must be old. I suggest that you follow what is
shown in the skinconf.xml for a fresh site, i.e. cd to a
new directory, do 'forrest seed' and look at its skinconf.xml

> p.s. FYI, like FOP's Eyebrowse mailing list archives, Forrest's  
> Eyebrowse links appear to be non-functional. Currently, I see no way to  
> browse the forrest-user archives

This is a problem for many Apache mailing lists.
Some people at ASF Infrastructure are working on fixing it.
In the meantime, try the "mod_mbox" archives ...
http://mail-archives.apache.org/

--David


Re: TOC in FAQ

2005-05-04 Thread Thorsten Scherler
Sorry for not being able to help you, but welcome back web maestro Clay.
Glad to see you around. :)

cu
thorsten

On Wed, 2005-05-04 at 09:40 -0700, The Web Maestro wrote:
> I'm having a problem generating the table of Contents for our FAQs  
> page[1], although all other pages contain generated TOCs at the top. I  
> checked the Forrest 0.6 Menus & Linking page[2], and it indicates that  
> skinconf.xml should include the element:
> 
> 
> 
> The value we have in our skinconf.xml file is:
> 
> 
> 
> Although what we have is different, this matches what Forrest appears  
> to have for its skinconf.xml file in SVN[3]. I tried switching to the  
> , but I get an error that @level must  
> be declared. I suspect the Docs are incorrect for Forrest 0.6 (I did  
> make certain I'm running forrest-0.6):
> 
> [EMAIL PROTECTED] xml-fop]$ which forrest
> /Users/Shared/_WebDLs/_repos/apache-forrest-0.6/src/core/bin/forrest
> 
> FWIW, here's the DOCTYPE from my skinconf.xml file:
> 
>  V0.6-3//EN" "http://forrest.apache.org/dtd/skinconfig-v06-3.dtd";>
> 
> I thought, perhaps the problem was related to the DOCTYPE for our  
> faq.xml:
> 
>
> "http://cvs.apache.org/viewcvs.cgi/*checkout*/xml-forrest/src/core/ 
> context/resources/schema/dtd/faq-v12.dtd">
> 
> But again, the Forrest faq.xml file appears to have the same DOCTYPE.  
> faq.xml also appears to have the same structure. I'd rather not move to  
> the v20 DTD if possible.
> 
> [1] FAQ page w/o TOC
> http://xml.apache.org/fop/faq.html
> [2] Forrest Menus & Linking: TOC Generation
> http://forrest.apache.org/0.6/docs/linking.html#toc-generation
> [3] Forrest skinconf.xml file in SVN
> http://svn.apache.org/viewcvs.cgi/forrest/trunk/site-author/ 
> skinconf.xml?view=markup
> [4] FOP skinconf.xml file in CVS
> http://cvs.apache.org/viewcvs.cgi/xml-fop/src/documentation/ 
> skinconf.xml?view=markup
> [5] FOP faq.xml file in CVS
> http://cvs.apache.org/viewcvs.cgi/xml-fop/src/documentation/content/ 
> xdocs/faq.xml?view=markup
> 
> p.s. FYI, like FOP's Eyebrowse mailing list archives, Forrest's  
> Eyebrowse links appear to be non-functional. Currently, I see no way to  
> browse the forrest-user archives
> 
> Regards,
> 
> Web Maestro Clay
-- 
thorsten

"Together we stand, divided we fall!" 
Hey you (Pink Floyd)



TOC in FAQ

2005-05-04 Thread The Web Maestro
I'm having a problem generating the table of Contents for our FAQs  
page[1], although all other pages contain generated TOCs at the top. I  
checked the Forrest 0.6 Menus & Linking page[2], and it indicates that  
skinconf.xml should include the element:


The value we have in our skinconf.xml file is:

Although what we have is different, this matches what Forrest appears  
to have for its skinconf.xml file in SVN[3]. I tried switching to the  
, but I get an error that @level must  
be declared. I suspect the Docs are incorrect for Forrest 0.6 (I did  
make certain I'm running forrest-0.6):

[EMAIL PROTECTED] xml-fop]$ which forrest
/Users/Shared/_WebDLs/_repos/apache-forrest-0.6/src/core/bin/forrest
FWIW, here's the DOCTYPE from my skinconf.xml file:
http://forrest.apache.org/dtd/skinconfig-v06-3.dtd";>

I thought, perhaps the problem was related to the DOCTYPE for our  
faq.xml:


 
"http://cvs.apache.org/viewcvs.cgi/*checkout*/xml-forrest/src/core/ 
context/resources/schema/dtd/faq-v12.dtd">

But again, the Forrest faq.xml file appears to have the same DOCTYPE.  
faq.xml also appears to have the same structure. I'd rather not move to  
the v20 DTD if possible.

[1] FAQ page w/o TOC
http://xml.apache.org/fop/faq.html
[2] Forrest Menus & Linking: TOC Generation
http://forrest.apache.org/0.6/docs/linking.html#toc-generation
[3] Forrest skinconf.xml file in SVN
http://svn.apache.org/viewcvs.cgi/forrest/trunk/site-author/ 
skinconf.xml?view=markup
[4] FOP skinconf.xml file in CVS
http://cvs.apache.org/viewcvs.cgi/xml-fop/src/documentation/ 
skinconf.xml?view=markup
[5] FOP faq.xml file in CVS
http://cvs.apache.org/viewcvs.cgi/xml-fop/src/documentation/content/ 
xdocs/faq.xml?view=markup

p.s. FYI, like FOP's Eyebrowse mailing list archives, Forrest's  
Eyebrowse links appear to be non-functional. Currently, I see no way to  
browse the forrest-user archives

Regards,
Web Maestro Clay
--
<[EMAIL PROTECTED]> - 
My religion is simple. My religion is kindness.
- HH The 14th Dalai Lama of Tibet