toc.xslt bug at match template file and schemas

[GoogleCodeExporter]

What steps will reproduce the problem?
1. On windows installation, run the script

What is the expected output? What do you see instead?
TOS left panel and main panel shows up OK.
When you click on a transform of job at the TOC panel, it fails to display.

Not sure if this is a Windows vs Linux problem.

Original issue reported on code.google.com by herma...@gmail.com on 2 Apr 2011 at 3:24

[GoogleCodeExporter]

Hi herman, 

I just checked out the trunk and tried it on windows, there it seems to work ok 
for jobs and transformations - the connections don't work but I think I didn't 
implement that yet (sorry it's a while since I had a chance to work on 
cookbook).

I'm going to fire up linux and try there too. 

Original comment by roland.bouman on 2 Apr 2011 at 3:36

[GoogleCodeExporter]

Upon investigation,
<xsl:variable name="relative-path" select="substring-after(@full_name, 
$input-dir)"/>
lacks a "/" at the prefix.

the path becomes "htmlcompare-files.ktr.html"
when it should be "html/compare-files.ktr.html"

Can others confirm that on linux this does not happen?

Original comment by herma...@gmail.com on 2 Apr 2011 at 3:41

[GoogleCodeExporter]

herman, I just ran it successfully on windows. I used these parameters:

INPUT_DIR D:\Applications\pentaho\pdi-ce-3.2.0-stable\samples
OUTPUT_DIR D:\tmp\kettle-cookbook-doc

I'd like to find out why it does work for me, but not for you before we change 
it. It's possible that there is a missing slash somewhere, but then I don't 
understand why it does work for me. Can you please post your parameters? Maybe 
we can find out why it behaves differently for you...

Original comment by roland.bouman on 2 Apr 2011 at 3:50

[GoogleCodeExporter]

This is really strange, it works for me on linux too, using 

INPUT_DIR /home/roland/pentaho/kettle-3.2.0/samples
OUTPUT_DIR /home/roland/kettle-cookbook-docs

Original comment by roland.bouman on 2 Apr 2011 at 3:53

[GoogleCodeExporter]

Hi Roland,
I was following the default params where the paths were using '/' format.
when I used the standard windows format 'C:\xxx\yyy', it works.

Thanks.
Herman

Original comment by herma...@gmail.com on 3 Apr 2011 at 1:29

[GoogleCodeExporter]

Ok, thanks.

I did notice some issues at an earlier point when using the "wrong" dir 
separator char. 
I'm wondering whether it's acceptable to say, when on windows please use "\", 
when on *nix please use "/".
Personally I don't think that is a huge problem, but since it's possible to do 
it wrong, it should at least be documented somewhere. 

What do you think? 

Original comment by roland.bouman on 3 Apr 2011 at 7:53

[GoogleCodeExporter]

Original comment by roland.bouman on 14 Jul 2011 at 9:26

• Changed state: Fixed