Kadav tags carry over from RH 6 to RH 7

Question

kadov is gone, but not forgotten.
If you don't care about kadov, skip to the end.
RH 7 doesn't use the old kadov tags in source html, so they
don't appear in WebHelp output topics either.
However, RH 7 does not automatically clean up kadov coding
when you import a topic created in RH 6 into a new RH 7 project..
Nor does it clean up when you use RH 7 to open a project originally
built in RH 6 or earlier.
This bit is generated when you put two or more spaces
together:
<!--kadov_tag{{<spaces>}}--> <!--kadov_tag{{</spaces>}}-->
In RH 7 it becomes
<spaces> </spaces>
but not automatically.
Note the regular space at the beginning. You can repair this
with the RH find and replace utility, changing the string to a
single space (unless you wanted the extra space. In that case just
leave them there and RH will insert
<spaces> </spaces>).
I traced most of the kadov carryover to a .css stylesheet
originally created in RH 5 (maybe earlier) and reused in RH 6 and
7. I had built custom bullet styles. Some used a standard disc or
square, while some used custom images. RH coded the style and
duplicated it in a slightly different form, with kadov tags. (This
presumably ensured the display would be same in RH WYSIWYG as in
WebHelp output. Hmmm .....)
Steps I took:
1. In each topic, deleted the meta string
<meta name=filetype content=kadov>
2. Outside RH, cleaned up the .css stylesheet. You can build
a new one in RH7, which may be less trouble than revising the old
.css file with a text editor. I removed everything kadov.
3. Launched the project in RH 7.
4. Selected all topics and in the properties dialog, applied
default .css to all, reapplied the custom stylesheet to all, and
closed the dialog with the X icon at upper right. If you click OK,
you need to check a few topics to see which .css file stuck.
5. Generate WebHelp to a test location and see whether any
kadov tags got through. Do this even if you don't see kadov tags in
the project source files' html code.
6. I hope the next won't be necessary.
If kadovs still show up in the output,
a. Delete the problem styles in RH and rebuild them.
b. Reapply the style sheet to each topic.
c. Repeat Step 5.
d. If kadov isn't dead yet, open each topic and reapply the
corrected style everywhere the original was used. Regenerate
WebHelp.
Alternatively, you could spend that time making some lemonade
and sitting back to reflect on whether it's worth the trouble.
Depends on how obsessive you are about kadov.
Harvey

Answer 1

Thanks to Peter, whose messages late Friday and yesterday I
didn't see until this morning, I now retract nearly all of my
previous post.
It happened that kadov cleanup was coded late in the RH 7
development cycle. I was looking at topics in a project that I had
started in RH 6, then opened in a test version of RH 7 that was not
the final release. Even though I started fresh, with a new project
in the final RH 7 release, and imported those topics from the old
RH 7 project, they had been tainted, apparently. I apologize for
this false alarm.
I think my old .css stylesheet was an unnecessary
complication. I plan to create a new one in RH 7 to match those
styles.
Another oddity that still clouds the picture:
When you import topics from an RH 6 project, the RH 7 view of
html source shows no evidence of kadov tags.
However, even after you save and close the new RH 7 project,
Notepad and FAR find kadov tags lurking about until you make a
change and save the topic in RH 7.
I understand you can edit and restore text in RH 7 before
saving, and kadovs will be gone in Notepad and FAR, as well as from
RH html view.
RH 7 does better if you open the old project directly, rather
than importing individual topics. Yet, the old .css style sheets
(default, etc.) retain kadovs. Maybe they get cleaned up later if
you apply them, I haven't tried.
Harvey