Skip to main content
ColdForest
Inspiring
September 24, 2018
Question

RH2017 Topic Filenames Include Ending Hyphen

  • September 24, 2018
  • 1 reply
  • 1930 views

Hi, I've been using RH for a couple years now and I'm trapped in a situation I've previously randomly seen (but always seem to get out of, somehow). The situation is that after importing a Word (2017) document the topic filenames include an ending "-" (hypen) as the last character of the file's basename (e.g., 1_Introduction-.htm - I need this to be 1_Introduction.htm). I've seen this occur randomly in the past and I know there must be some way to control this, but I can't seem to find it. My conversion is very straightforward (pagination on Heading 1/2) and the topic pattern is using $paratext (in angle brackets)).

Any ideas how I can control/fix this?

Thanks,

-David

    This topic has been closed for replies.

    1 reply

    Peter Grainge
    Community Expert
    Community Expert
    September 25, 2018

    Have you tried paratext no num? I am wondering if it is trying to apply a number and then truncating. It's a wild guess.


    See www.grainge.org for free 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.
    ColdForest
    Inspiring
    September 25, 2018

    Hi Peter,

    Yes, I've tried each of the available options and they all end up with topic filenames including the trailing (in the file's basename) hyphen.

    1_Introduction-.htm <$paratext>

    1_Introduction-.htm <$paratext_no_num>

    <filename>-1-.htm <$filename_no_ext>-<n>

    <filename>-1-Introduction-.htm <$filename_no_ext>-<$paratext>

    BTW, I'm not sure why the second option isn't removing the "1_"(?). Each of the above were generated from defaults during import (except for the topic pattern option/setting obviously).

    I have isolated the issue related to what I thought was the "randomness" element. I happen to have two, saved ".isf" (import settings) files. I had thought these were *identical* but after comparing them I see they are very slightly different (these are binary files so their differences are a couple dozen bytes, which I can see in my hex editor/differ - however, there isn't anything obvious here, e.g., the hex values don't equate to any ASCII representation that might provide a hint about the phantom hyphen). The two .isf files are identical otherwise and certainly don't indicate any differences that I can make out in the settings dialog in the import dialog (both topic pattern values are <$paratext>). When I use one of these settings files the hyphens are present but not when I use the other one.

    Now I'm really nervous about preserving the apparently "special" .isf file; I can't seem to get an import that works properly without it.

    Peter Grainge
    Community Expert
    Community Expert
    September 25, 2018

    When you import you select an ISF. Next time you import it shows Custom. Don't assume it is still using the ISF you think it is.

    Select one ISF and start the import. Go to the Edit button and screenshot everything.

    Now select the other ISF and do the same.

    Does that reveal any difference?


    See www.grainge.org for free 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.