Unable to rename topic files in Robohelp

[Guest]

We're translating Framemaker > Robohelp integrated project into Chinese, and as part of the process, we rename the Chinese topic file names to English so that the Webhelp output works on our chinese web site. This process has worked well, except we are now having a peculiar problem:

The topic File Name in the Topic Properties dialog cannot be changed in any project. The topic file name is grayed out. I have tested and confirmed this behavior in both projects in Robosource Control and local projects that are NOT in Robosource control. In the past, I have always been able to change both the topic title and topic file name, but in Version 8 (TCS 2), both fields are grayed out in EVERY project.

Our IT guys tried changing all kinds of file permissions on our Windows XP boxes, and Robohelp STILL won't let us change the topic file names or the topic titles in Robohelp's Topic Properties dialog.

We have not installed any patch since installing TCS 2.

Anybody have a clue?

Thanks,

Michael Cohen

[ProvGS]

Hi Michael,

If you're linking your Frame documents into RoboHelp, I believe that behaviour is expected. Since the files can change anytime because they are generated, it's my belief that RoboHelp won't let you change them on purpose. If you Import the Frame into Robohelp then you should be able to change the filename.

Try using a Topic Name marker to define what the filenames should be when they are generated. Also make sure that you add a title to the marker in addition to the filename (for the HTML title tag). This works most of the time, but I'm certain there is some bug that prevents all of mine from being converted properly. My workflow, until I come up with something better, is to use Linking up until a certain milestone, then Import the Frame into RoboHelp/ Importing appears to be more reliable with less bugs than Linking.

Gerry

[Guest]

I am very interested in your technique of importing FM docs after mapping. Could you explain? Thanks!

Missy

[ProvGS]

Hi Missy

I am actually doing several things: I use the linking method a few times during the project, but near the end I just use the import feature. It is far more reliable than linking. There are just too many things wrong with the output when I link Frame and RoboHelp. Here is my process in a nutshell:

Set up the project as follows:

Export settings file from Linked project so you don't need to do all the mapping again. A note here to use the conditional settings of your FrameMaker files instead of RoboHelp. Also avoid using Frame revisions as they confuse RoboHelp .

Add CSS as baggage file

Project Settings: Add css to Import tab as CSS for style mapping

Project Settings: Add FrameMaker template (used during import)

Ensure the Project Settings is using your exported settings file.

Set up output format as follows:

MS HTML Help Properties:

• Conditional text settings: ensure you don’t hide revision text that is added to Frame (if using revisions)

• Add breadcrumbs

• Add TOC

• Add Index

• Default first topic

• Check Apply css to all topics

Create a window and give it the same name as the help file name.

Import Frame files

Map styles to css styles

When making a change, you need to re-import the Frame files. To do this, delete all Frame output files (from the Topics list or the Project view). Ensure your project is set up as described above, then re-import.

Gerry

[Guest]

Thank you so much for taking the time to answer my query.

I've never used a FM template file. Why would I need that? Would this be a different file than a FM file from the original FM project?

[ProvGS]

Hi

I got the idea from this post and it worked: FM Cross-Reference Styles to RH Styles. Although when importing instead of linking it may not be required. Yes it's the same as a regular FM file. I think it's just what RoboHelp does with it that makes it different.

[Matt-Tech Comm Tools]

Recently I had a client come across a solution to a few formatting issues when working with linked FrameMaker 9 documents in RoboHelp 8. I solved it with the FM Template option & wrote it up here: http://blogs.roundpeg.com/2010/03/controlling-robohelp-output-with-a-framemaker-template/

[grammatophile]

I do not believe that Michel's original questions was ever answered. Why did Adobe decide to negate the possibility for changing the file name in TCS2 when it was available in TCS1? I consider this a bug and wonder whether Adobe has been notified.

[Arnis Gubins]

You can file a bug report for this at:

https://www.adobe.com/cfusion/mmform/index.cfm?name=wishform

[3rd_name_change_april_5th]

I have the same problem. In the Topic Properties>General tab, the Topic Title and File name fields are grayed out. How to enable those fields?