I'll jump in, as I've also been experiencing this in 0.06 on Windows
using ActivePerl.
I've only been using the default CSS and JS files, so I haven't tried
changing the input. The error I've been receiving, which I suspect is
related to this is:
Warning: couldn't read
C:%5CPerl%5Csite%5Clib%5CTAP%5CFormatter%5CHTML%5Cdefault_page.css: file
does not exist!
Warning: couldn't read
C:%5CPerl%5Csite%5Clib%5CTAP%5CFormatter%5CHTML%5Cdefault_report.css:
file does not exist!
This occurs in slurp_css, as it doesn't seem to think uri->path points
to a valid file. If uri->file is used instead, it works properly for me.
From some quick testing of URIs through Explorer:
C:%5CPerl%5Csite%5Clib%5CTAP%5CFormatter%5CHTML%5C is interpreted as
file:///C:%255CPerl%255Csite%2555Clib%255CTAP%255CFormatter%255CHTML%255
C for some reason, and is not found.
file://C:%5CPerl%5Csite%5Clib%5CTAP%5CFormatter%5CHTML%5C is not found
file:///C:%5CPerl%5Csite%5Clib%5CTAP%5CFormatter%5CHTML%5C, as indicated
by the linked article, does work.
Let me know if you need me to try anything else out.
On Mon Feb 02 17:08:56 2009, SPURKIS wrote:
Show quoted text> On Mon Jul 28 06:13:08 2008, DAVAZ wrote:
> > File-schemed CSS and JS paths get mangled on Win32. If we have
> >
> > file://C:\some\path
>
> I think this may be a case of invalid file URI's being passed into TFH
> - see
>
http://blogs.msdn.com/ie/archive/2006/12/06/file-uris-in-windows.aspx
>
> According to this, you should be using the following:
>
> file:///C:/some/path
>
> Can you try that & see if that works?
>