This content has been marked as final. Show 5 replies
As you're probably aware, the "id=a" sequence is determined by the order in which the popups were/are created, and not top-to-bottom.
That said, you're not clear in your post exactly what you would be changing. As to the local popups, a comparison with my WebHelp popups indicate that you would need to delete the bold strings and add the italic string (all easily done in FAR).
As to the external links, I assume that these projects will now all be child projects within your merged WebHelp (as per Peter's excellent tutorial)? Therefore, you'd be replacing:
<project_name>.chm::/<folder_name>/ with: ../ (as many instances as there are projects)
You'll have to manually assign numbers to replace the "ax" string that I'm suggesting, but you can use FAR to at least identify the files that need attention. For example:
1. Search on id=a (amount of matches will identify the maximum amount of popups in any topic).
2. Search on id=a4 (or whatever the maximum amount was in step 1).
3. Click the Matches column head twice to bring all related topics to the top of your list.
4. Select all other topics, right click and select Remove Selected.
5. Search again on the remaining topics to find any "id=ax" matches. Enter only those topics that need to have "id=ax" changed to 5, 6, etc.
6. If none, start over at step 1 using "id=a3" for matches.
Pretty simple, huh?
The only other thing beyond Leon's advice that comes to mind is Regular Expressions. They are described on my site but you would almost certainly need developer support and not all developers are familiar with them.
We're using RoboHelp 7 so I'm confused as to why I'd want to reintroduce kadov tags? The rest of it looks good, thanks!
Leon's example is from X5. You will need to adapt it using the format you see in your code.
Another approach might be to use MacroExpress. Record a macro as you change one popup manually, then manually locate each popup and run the macro. Still a bit manual but much quicker. Not entirely sure it will work without testing.
I suggest you create a mock merge set up and experiment with that, rather than working on your real project.
Originally posted by: Peter Grainge
...I suggest you create a mock merge set up and experiment with that, rather than working on your real project.
I did that first thing. Thanks, that clears things up. I'll let you know how things work out.