This content has been marked as final. Show 5 replies
I haven't seen RoboHelp alter code within a <SCRIPT> tag, but the WYSIWYG editor is notorious for messing with your HTML. One of the conflicts that can occur with scripts is that RoboHelp adds its own script file to every topic in order to support DHTML. It is possible, but unlikely, that you might define a constant or name a function that is already in use.
What error messages do you get? If you compare the script that worked from one editor, to that which didn't from RH, what are the differences?
2. Be very careful not to introduce line breaks within sections of the script. Usually, I filter any code I've downloaded from sites that offer them through Notepad, by pasting the code and turning off Word Wrap. That tells me exactly where the only allowable line breaks should appear, so that I can verify the format after pasting it into RH.
3. Pay special attention to where in the topic you should place the <SCRIPT call (sometimes in the <HEAD> section, sometimes after the <BODY> tag, sometimes before the </BODY> tag, etc.).
Thanks for the advice. I copied the code into WordPad first and then brought into Robo. This seemed to fix the problem previously where Robo was changing the code slightly. I should mention I'm using RoboHelp 7 HTML and publishing to RoboHelp 7 Server.
It sounds like your bookmark.JPG image is missing. Did you add it to your baggage files? Is this WebHelp? I ask because of the browser checks.
This might be irrelevant but I also noticed the upper case JPG extension. Adobe Photoshop does that to my images when I modify them and then our UNIX server (which is case sensitive) can't find them because all the file references are lower case. And Windows (which is case-insensitive) doesn't allow a direct name change from 'file.JPG' to 'file.jpg.'
John brings up a good point about adding the images to the Baggage Files folder: as far as I know, RH doesn't "recognize" images that are not linked using the <img> HTML tag. Therefore, it will not "carry over" the image into the output folder unless it's told to with other means (the aforementioned Baggage Files folder).