RH 9 Mangles single XREF from FM 10 page

[Mark Southee]

I have a linked project from FM10 to RH9

One one single page, a single Heading 3 is being mangled by the RH import, and for the life of me, I don't know why. There are other Heading 3's on this page which come across fine. For example:

<p class="FM_Heading3"><a name="XREF_33020_System_Preferences"></a>System  Preferences</p>

But one (it is only this one!) comes in like this:

<p x-orig-class="FM_Heading3" class="FM_Heading3"><a name="XREF_38522_Database_Management"></a><xref_marker  mtext="38522:_Heading3:_Database_Management" filepath="C:\Documentation\User Guide\Frame_reference.fm">Database Management</p>

I've even removed the whole section from the document and input again from scratch, but it keeps doing it. Why would it try and link to the related FM file? In Design view it flags it as an unknown tag

Anyone else seen this?

Mark

[Sreekanth_S]

Even I am facing this issue. Anybody has a solution yet?

[Matt-Tech Comm Tools]

For starters, map your FM Heading3 style to something in your RH css. You could map it to Heading1 with Pagination (Split Topic) or you could map it to a Heading 2 or Heading 3 if it is  a subsection of your RH topic.

Once you've done that, (removed the horrid class="FM_Heading3" code) then let us know if the problem persists.

BTW, IIRC, RH9 has issues with cross-references that I believe are fixed in RH 9.02 and definitely fixed in RH10

[Sreekanth_S]

I am using RH10, that came as a part of TCS 4.0.

I am having this problem with bulleted lists. Unfortunately, the issue is random. The same FM tag is imported correctly in some other place in the project.

Here is the issue in detail:

Incorrect Output (Design view):

Incorrect Output (HTML View): (The image int he post is fuzzy. Please click to open it. )

FM content and tag of this content:

Note the difference in tag names between what is shown in RH and FM. As per RH, the original class "x-orig-class" is LB1ListBullet1, whereas in FM, it is "LB1-ListBullet1". I guess that is the cause of this issue. However, I am not able to figure out how this can be prevented. (On a side note, the issue of different tag names in RH and FM for the same content has occurred in other places as well. So, if we get a solution here, I will apply it for those instances.)

Correct Output (Design View):

Correct Output (HTML View): (The image int he post is fuzzy. Please click to open it. )

Here MLB1 is the multi-level list tag (where I have defined the type of bullet required) based on BodyLevel1 paragraph tag. In the Settings ISF file, I have mapped the FM bulleted list tag to BodyLevel1 tag, due to which the output appears correctly.

[Matt-Tech Comm Tools]

The 2 things I see:

1. You appear to be mapping a character tag to a custom <paranum> html element. Track it down and fix this.
2. You're using an RH Multilevel list, but this is a first-level list. Change it to HTML List.

[Sreekanth_S]

1.  I didn't find any tag mapped to <paranum> element.

2.  I opted for RH Multilevel list because this is the first part of three bullet levels I have in my course.

Anyway, on further investigation, I noticed couple of things:

1. The FrameMaker topic which contained this bulleted list is configured to appear as a new topic within RoboHelp. However, on import, this topic is appearing as a continuation of previous topic.
2. Now, this led me to check the previous topic where I found the real culprit. This topic has a hyperlinked text which was configured to launch the target in a new window. Its syntax in FM was:

           message URL <filepath>” target=_blank

          Due to this " target=_blank , the content following this was not tagged and mapped properly while importing to RoboHelp.

My Solution: I removed " target=_blank from FM hyperlink and imported the book to RH. Everything worked fine. I modified the hyperlink to open in the new window from within RH.

I don't know if this is the best solution or only possible solution. But this worked for me.