Answered
Space in URL is converted to %2520
I use RoboHelp 7 (7.02.001) to create WebHelp.
In the Table Of Contents I have created a page with a link to a folder on one of our file servers.
The folder however, has spaces in its path.
No problem so far, as I can open the link in the Preview in RoboHelp.
When I generate the WebHelp output and open the site in IE7, a warning is shown stating a script or ActiveX control wants to be executed. If I ignore this message and press on the page in my TOC (navigation), the folder is opened as expected.
If I accept the script to be run subsequently, and then try to follow the link to the folder, an error is shown stating the folder cannot be found. What I see is that the space isn't replaced any longer by %20, but it now reads %2520.
Further investigation learned that when I replace any %20 occurences in whxdata\whtdata0.xml to a space, I can follow the link successfully in both cases (with or without the script activated).
So, this is a workaround, but I am looking for a resolution.
Has anyone a good idea?
(Note that the link does not open the target in any case when opening the site in Firefox 2.)
TIA,
Andre
In the Table Of Contents I have created a page with a link to a folder on one of our file servers.
The folder however, has spaces in its path.
No problem so far, as I can open the link in the Preview in RoboHelp.
When I generate the WebHelp output and open the site in IE7, a warning is shown stating a script or ActiveX control wants to be executed. If I ignore this message and press on the page in my TOC (navigation), the folder is opened as expected.
If I accept the script to be run subsequently, and then try to follow the link to the folder, an error is shown stating the folder cannot be found. What I see is that the space isn't replaced any longer by %20, but it now reads %2520.
Further investigation learned that when I replace any %20 occurences in whxdata\whtdata0.xml to a space, I can follow the link successfully in both cases (with or without the script activated).
So, this is a workaround, but I am looking for a resolution.
Has anyone a good idea?
(Note that the link does not open the target in any case when opening the site in Firefox 2.)
TIA,
Andre
