I believe I need to add a little context to my last blog about Adobe RoboHelp 9 – A real XML XHTML Editor.
Old perceptions die hard. Before Adobe acquired RoboHelp, earlier versions of its source code used a lot of proprietary tags such as the notorious kadov tags. Because of this, even today, people who don’t know better will mistakenly assume that RoboHelp has not changed.
That was then. This is now! The good news is that Adobe has leveraged its leadership and engineering knowhow in XML and DITA tools with Adobe FrameMaker to reshape RoboHelp’s source code editor so that is squeaky clean in terms of following the XML and XHTML standards.
OK, fine. So what does that do for you as an author? Well, authors often have multiple tools that we work with. Because XML must be “well formed,” only a strict implementation will allow you to open the same file in any XML Editor.
So to prove the point, I’ve set up a scenario:
Let’s say that one author is using RoboHelp and a colleague wants to use FrameMaker to edit the file. An author in another office uses Altova XML Spy and yet another uses Notepad in their workflows. The accompanying YouTube video shows how to “roundtrip” RoboHelp’s XHTML source file into FrameMaker and back to RoboHelp and then from RoboHelp to XML Spy and even Notepad. In each case, the integrity of the XML “under the hood” is retained because RoboHelp created correctly in the first place.
Here is the YouTube video. I have added Intro Slides – http://www.youtube.com/watch?v=cOkRZfAzYvg
Here is the FrameMaker files I mentioned in the video http://www.aldousxml.com/Adobe/ROBOHELPXML/FrameMakerXHTML.zip