Mark,
Someone may know of a workaround.
One solution is to push for a standard that doesn't allow
spaces in network drives, directory names and file names
but_permits_underscores.
The best solution is to store WebHelp on a network drive that
has a domain name and to point the link to its Intranet URL. No
spaces are permitted.
I saw a truly awesome improvement in response time when the
IT folks set this up for my material.
I don't know how much trouble it is to assign a domain name
to a drive/server on an Intranet.
In my case, I publish to a network drive using the file
system path X://rootdirectory/subdirectory/ ..... etc.
That drive also is a server on the company Intranet, so the
browser address is
ht[xxxx]tp://division.company.net/subdirectory(ies).../myhelppackage.htm.
[xxx inserted to block an automatic hyperlink]
There's a significant bonus: Navigating network file paths is
increasing subject to security measures like identity/authorization
checking by transmission chunk, which significantly slows response
to the browser. Using a Web/Intranet path usually requires an
identity check only once for a given file, when you first access
it.
(I think that's the right explanation. Any experts on htt
protocol are welcome to chime in.)
Harvey