Skip to main content
Z
Z__Bulova
Known Participant
May 21, 2008
Question

xref marker syntax question

  • May 21, 2008
  • 3 replies
  • 502 views
Hello, I am running the Technical Communication Suite and trying to figure out why some of my Framemaker cross references import into RoboHelp and some do not. I have saved one offending file as MIF and took a look at the cross reference markers. What I observed is that the markers of those that import differ from the markers of those that do not import. More specifically, the markers of those that do not import carry an \xod appendage. <br /><br />Here is an example of one that does import:<br /><br /> <XRefSrcText `85269: Heading 2: System Architecture'><br /><br />Here is an example of one that does not:<br /><br /> <XRefSrcText `14446: Heading 2: Management Console\x0d '><br /><br />So I have narrowed this down a bit but what I do not understand is the significance of the \xod appendage. I was thinking that perhaps someone here might know. If so, that would be a godsend. Thank you in advance for any insight you may be able to offer.<br /><br />Best Regards,<br /><br />Z.
    This topic has been closed for replies.

    3 replies

    Z
    Z__BulovaAuthor
    Known Participant
    May 22, 2008
    Awesome! That was it. Thanks Sheila!
    A
    Anonymous
    May 22, 2008
    oops, amend that -- could the paragraph with the misbehaving cross-ref actually have a soft carriage return at the end of the line? If so, make it a hard return (end of paragraph) and see if the cross-ref then behaves itself when converting to RoboHelp.
    A
    Anonymous
    May 22, 2008
    \x0D is the hexadecimal form of a carriage return character -- could you have inadvertently hit enter at some point while editing or entering the cross-ref?
    Terms & ConditionsAccessibility statement
    Using the community Terms of use Privacy Cookie preferences Do not sell or share my personal information ad choicesAdChoices