RE: [FARHTML] h3 toc steps
Once the source is kicked into shape using mshcMigrate (no XML errors; no empty TOC nodes; no duplicate TOC nodes etc)
then I would take that as my new VS 2005/2008 source (after mshcMigrate (and your fixes) everything in _HelpSource is now valid
vs 2005\vs2008\vs2011 help source).
Then when you want to publish to 2011 you just zip it up without the Nav files (and for VS2005\2008 you just compile to HxS).
In the event that you add a new topic … you would either:
- carefully copy in the Meta data with a unique Topic ID and correct TocParent ID. Then use FAR TOC Editor to export your HxT and HxK out to the Topic files.
- You just ram the whole thing through mshcMigrate.exe (an overnight build) and there is your .mshc file ready for the installer.
Yes an XML editor would be fine. It’s mostly about correct XML syntax. This is because they load and parse into .NET XML classes.
Hope your wrist comes good soon.
My goal at the moment is only to convert a 2005 toc to a 2010 toc, fix any problems, and deliver the toc with the zip package.
(I'm also working with my left hand only for six weeks due to a broken wrist, and having some challenging days. so will work on maintaining the whole source toc xml errors later.) Our 2005/8 integration help and toc are good, and have been delivered.
Are my steps the correct procedure to fix the 2010 toc? It sounds like you are saying that an xml editor would do, not necessarily an xhtml editor - are they the same thing? Expression web takes hours to download, not run on my laptop.
I'm so grateful that you answer.
- Thanks, Rob. I was hoping for a magic bullet around XML errors, as I haven't got into XML yet, and just want to turn this one in. However, the best way to do something is to go straight at it, so I'll dig in. Appreciate your guidance.