Participating Frequently

Answered

Anyway to fix text Format changes when I use WebHelp to CHM Converter?

Forum|Forum|8 years ago
March 16, 2017
3 replies
873 views

Hello! Any help with this would be appreciated.

Currently I am using the WebHelp to CHM Converter function in RoboHelp so that I can apply a skin to my project. However, when I open the CHM file I noticed that the text format for certain topics have been overridden. For example, my headings appear as basic text, and bullet points and color fonts are gone as well. Images are missing as well in the project. When I generate the chm normally, the format is there, but images are still missing. Is there a fix to this? I really need to use this tool as our company is trying to update our online help by using skins and keeping the chm file. Can anyone think of a cause for the format changing like this?

Thanks

Abigail

This topic has been closed for replies.

Correct answer Captiv8r

While I'm happy to see this has been sorted, there are a couple of things that need mentioning for clarification purposes so if others down the line find this thread it will make better sense.

The reason things looked fine when you generated a CHM file was because that process really doesn't modify the source HTML files. So your topic was referencing the CSS properly with the ampersand in the file name. But when WebHelp is generated, a vastly different process is used. Each source file is modified along the way. And that process was what was causing the actual file name of the CSS to be modified so it no longer had the ampersand. The process substituted the underscore for the ampersand. And actually, this would appear to be a bug to me. If the process causes the CSS file name to be changed, it should have also adjusted the CSS reference in any topic using that CSS. But seeing as how you are using RoboHelp version 10, it's possible that it's no longer a bug we need to be concerned with.

Certainly a skin changes the appearance of things. But it's a bit of a misunderstanding to say that because Skins were being used, Style Sheets became necessary. The thing is, Style Sheets are needed for the ability to format the text as authors hope to see it. Skin or no skin.

When Abigail made the changes to remove the ampersand, she did this using Framemaker, not RoboHelp.

I'm going to move this thread to the Framemaker section as it seems to make logical sense that it should be parked there.

Cheers all... Rick

A

abigailb32739973Author

Participating Frequently

In working with Captiv8r we were able to resolve this issue! This issued was caused by the FrameMaker files having characters such as "&" in it. It generates fine when doing the simple chm, but I supposed when I applied a skin, Style Sheets became necessary. When RoboHelp was creating/updating the style sheets for these files it wasn't registering the "&" character and so the style sheet and the file names weren't matching, thus causing the format to be lost in the chm file. I eliminated all occurrences of the "&" character in my file names, file infos, and even headings. When I updated the book and RoboHelp, the topics that were not displaying correctly now work properly.

As far as the issue with missing images, it seems that shortening the image names are fixing that issue. So in regards to images, it may just be an issue of long files paths.

Thanks!

Abigail

Captiv8rCorrect answer

Legend

While I'm happy to see this has been sorted, there are a couple of things that need mentioning for clarification purposes so if others down the line find this thread it will make better sense.

The reason things looked fine when you generated a CHM file was because that process really doesn't modify the source HTML files. So your topic was referencing the CSS properly with the ampersand in the file name. But when WebHelp is generated, a vastly different process is used. Each source file is modified along the way. And that process was what was causing the actual file name of the CSS to be modified so it no longer had the ampersand. The process substituted the underscore for the ampersand. And actually, this would appear to be a bug to me. If the process causes the CSS file name to be changed, it should have also adjusted the CSS reference in any topic using that CSS. But seeing as how you are using RoboHelp version 10, it's possible that it's no longer a bug we need to be concerned with.

Certainly a skin changes the appearance of things. But it's a bit of a misunderstanding to say that because Skins were being used, Style Sheets became necessary. The thing is, Style Sheets are needed for the ability to format the text as authors hope to see it. Skin or no skin.

When Abigail made the changes to remove the ampersand, she did this using Framemaker, not RoboHelp.

I'm going to move this thread to the Framemaker section as it seems to make logical sense that it should be parked there.

Cheers all... Rick

Captiv8r

Legend

Hmmm, in looking at the image supplied, I'm wondering if the issue isn't simply the naming of the image file. Note that it doesn't end in PNG, but PNGC.

Cheers... Rick

Peter Grainge

Community Expert

Good spot Sherlock.

Use the menu (bottom right) to mark the Best Answer or Highlight particularly useful replies. Found the answer elsewhere? Share it here.

A

abigailb32739973Author

Participating Frequently

Good morning!

I've tried shortening file paths of the topics as suggested, but the problem still persists. Again, the format is completely fine when I generate a normal chm file, but only acts up once the skin is applied. Could there be settings that need to be configured that I'm not aware of? At the moment, I'm just executing trial and error to try and solve the problem. Also, I am willing to send the files if that would be helpful!

Thanks!

Abigail

Peter Grainge

Community Expert

I don't think I have seen this reported so it's going to be trial and error to find the cause. The fact that it is some topics only helps.

Double click one of the affected topics from Windows File Explorer. Does it display correctly or with the same error?

You say images are missing. Have you tried deleting the CPD file and then reopening the project?

Are the project and the folders you are generating to all on the same drive and is that local?

What version of RoboHelp are you using?

See www.grainge.org for RoboHelp and Authoring information

@petergrainge

Use the menu (bottom right) to mark the Best Answer or Highlight particularly useful replies. Found the answer elsewhere? Share it here.

A

abigailb32739973Author

Participating Frequently

Hi Peter Grainge! Thanks for responding! Trial and error is all too familiar for me and Robhelp, but hopefully you can help me further. I'll address your suggestions in order:

When I open the htm files for the affected topics, they display correctly format-wise. All the formats are correct, but in the chm they are not. The topics with images missing, are still missing when I open those topics from Windows File Explorer.

I deleted the cpd file, and opened the project, but the images are still missing when I generate the help.

I do keep my source files on a network drive. I never really had trouble generating online help with the files being on the network, except an occasionally missing image. I moved my files to my desktop and created a new project and linked the same files to a new project and generated the help the same way I did before. And the project wouldn't compile and this message was in the Output View:

I assumed that perhaps the file path was too long and shortened it a bit, and regenerated the project. The project generated this time, but the formats/images were still missing for the same topics so I don't think the network is affecting it as it does the same thing even when the source file is on my hard drive.

I'm using RoboHelp 10.

Thanks!

Abigail Bellman

Peter Grainge

Community Expert

That path does look very long. My next trial would be to move the project locally just to prove it is not a network issue.

If that does not succeed, make a copy of the project for the next trial and drastically shorten the folder name even if they are meaningless. The point here is to disprove that path length is the issue.

Post back and if no success, indicate whether you can share the project with me.

See www.grainge.org for RoboHelp and Authoring information

@petergrainge

Use the menu (bottom right) to mark the Best Answer or Highlight particularly useful replies. Found the answer elsewhere? Share it here.

Sign up

To post, reply, or follow discussions, please sign in with your Adobe ID.

Sign in to Adobe Community

To post, reply, or follow discussions, please sign in with your Adobe ID.

Scanning file for viruses.

This file cannot be downloaded