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).
<a
href="javascript:BSSCPopup('<file_name>.htm',400,300);"
id=a4;">link text</a>
<robohelp><script type="text/javascript"
language=JavaScript1.2><!--
kadovFilePopupInit('a4');//--></script>
</robohelp>
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:
<a href="JavaScript:showHelp('ms-its:
with: <a href="javascript:BSSCPopup('
<project_name>.chm::/<folder_name>/
with: ../ (as many instances as there are projects)
.htm>$global_glosspop'
with: htm');" id=ax>Allocation Type</a><script
type="text/javascript"
language=JavaScript1.2><!--kadovFilePopupInit('ax');//--></script>
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?
Good luck,
Leon