This content has been marked as final. Show 6 replies
To those who rail against RH for adding code to assist the help author: SO WHAT?
Seriously, the output works just fine in Web browsers.
thanks for the reply.
What you say is all well and good but when that code is rolled into an app it isn't (WAI) web accessible - a MAJOR consideration for U.S. Gov work.
I was just trying to validate the RH7 online help and it failed on simple things like lacking a DOCTYPE and a lang attribute.
Can the code be altered without breaking RH? For example - what if I used Dreamweaver to add to this RH code, or Notepad? If I used an external app to make the code standards compliant, how would that effect how RH works?
Can I jump in and out of the RH editor and Dreamweaver without breaking RH?
I appreciate some input.
You can set Dreamweaver as you external editor. Topics will then open in dreamweaver instead of the RH editor. Not really sure about the WAI issue, but it sounds like dreamweaver may be more suituable as an editor in your situation.
When you select "W3 compliant topics" in the WebHelp setup, the RH 7 topic output files have this as the first line:
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
Does this meet the standard? If not, why not?
RH project files, including the topic source files, don't have this line. The project source files are not intended for display on the WWW.
Also, the other .htm output files (i.e., not the topics, but those for WebHelp processes) do not have this line.
Do you see a problem here?
(I shot from the hip earlier; the above is correct.)
P.S. I see some other differences in syntax for js and tags, but I don't know enough to make a generalization, beyond this:
The differences apparently remove some RH html code that might not "meet W3 standards." I'm guessing, and maybe Adobe can confirm this, the code doesn't violate any explicit W3 rules, but isn't specifically part of their library.
But I wholeheartily agree with Leon that browsers don't get upset about it.
In RoboHelp 6 and earlier versions, this is largely true. While beta testing RoboHelp 7, I saw many improvements in code. I don't have a production copy of RoboHelp 7, so I don't know how well the finished product does in regards to accessibility.
This is a false propaganda. I am sure this came from a RoboHelp competitor. RoboHelp generates clean HTML code and has got rid of Kadov tags in RH7.