TopicAlias markers from FrameMaker

[GregStenhouse]

Flare wants to add its own values (numbers) to TopicAlias markers from Frame, 1000, 1001, 1002 etc. The problem is we are coming from WebWorks where the value has been defined in the marker (e.g. we have six-digit numbers in Frame like 200201, 200202 etc). Flare imports this as (Text) Identifier 200201, (Number) Value 1000. This means all our F1 context sensitive links from the application are bung. Flare also wants to add the marker text after the topic reference in the alias file (e.g. "..topic.htm#200201" Which means a bunch of error messages as the topic does not exist.

Does anyone know if this can be controlled? I am struggling to understand why anyone would want Flare to automagically define their numbers for them, surely this is something that should be constant and defined by authors/developers, and ideally from FrameMaker so you don't have to redo the values each time you import?

Cheers
Greg

[SPearsall]

I've never seen any evidence that Flare supports TopicID markers from FrameMaker. It certainly didn't seem to import them from my Frame files. By contrast, my TopicAlias and Filename markers seem to work fine. Flare creates an alias file based on my TopicAlias markers, but it just seems to ignore my TopicID markers.
I'd be very interested to hear otherwise. Fortunately, it hasn't wrecked my world the way it has wrecked yours because our product is using the alias/filename pairing instead of the ID #.

[GregStenhouse]

It's a shame this isn't supported, but good to know so I can work something else out. Looks like I may be able to create a batch file and use grep or sed to manipulate (search and replace) the TopicAlias files that Flare creates. With a bit of work I should also be able to tie it in with a command-line build to do the whole lot automatically. We'll see how we go

Thanks for your reply!