RE: Trouble with WWP and JavaHelp

["David Knopf" <david@xxxxxxxxx>]

Jeremy H. Griffith wrote:

| That sure looks like a WWP bug.  Have you notified Quadralay?

No need. This works just fine in the current version of WWP.


| Also, the way JavaHelp works, any entry that appears in two different
| markers, like your:
|
| 	secondary entry 12, 15
|
| is going to be problematic because you only get to specify one of
| the targets, not both:
|
|     <indexitem target="secondary target" text="secondary entry"/>
|
| which means one of your refs is just gone.  When we asked Sun about
| this design error, we were told "don't do that", i.e., make sure
| every single index marker is **unique**.  If you avoid this "error",
| you may find that the WWP bug (missing first-level line) goes away.
| Or not.

That's odd, Jeremy, because the JavaHelp helpsets I produce with WWP have
secondary index entries like Gayle's, and they seem to convert just fine. I
haven't had a chance to try this with Mif2Go recently, but I don't see why
this wouldn't work there, too. This doesn't appear to be a fundamental
limitation in JavaHelp.


| >2. Display problems
| >
| >When I run the .hs file and click an entry in the TOC, the main panel
| >displays 2 overlapping versions of the page. This happens even for pages
| >that don't include an anchored frame. I'm using JH 1.1.1 and the Java 2
| >run-time environment, build 1.3, which I thought was supposed to fix this
| >problem.
|
| Well, a Sun person announced on the JavaHelp list that this Sun bug
| was fixed in "JDK 1.3", which presumably is what you have.  It's not
| the first time we've seen misleading statements or outright lies
| from Sun.  As it happens, we discovered the cause of this bug, and
| built a (proprietary) solution into Mif2Go's JavaHelp output, so
| Mif2Go users are spared this particular frustration.

This bug is resolved in JDK 1.3, or at least it appears to be based on the
fact that neither we nor any user of one of our production JavaHelp systems
has been able to duplicate it on 1.3. In any event, I don't think there's
any need for a proprietary solution here. In fact, there are well known
workarounds for this problem even on JDK 1.2.2.

Regards,

David Knopf (mailto:david@knopf.com)
Knopf Online (http://www.knopf.com)
Tel: 415.550.8367

RoboHELP MVP & Certified RoboHELP Instructor
WebWorks Publisher Certified Trainer
Co-moderator, HATT & wwp-users




** To unsubscribe, send a message to majordomo@omsys.com **
** with "unsubscribe framers" (no quotes) in the body.   **