I've not had an issue with messy HTML nor with controlling output file nesting. As for tools, I based my recommendation on familiarity and not on size of the Help. Since it's all FM source it really doesn't matter if tools change or not (you're only recrafting content mapping and template design), unless impacted by familiarity, time to learn, and cost.
On Tue, Dec 18, 2012 at 4:04 PM, Robert Lauriston <[email protected]>wrote: > RoboHelp's exported HTML is messy and I don't like the way it insists > on putting topics from each document in a FrameMaker book in a > separate directory in the generated help. > > It works OK for generating help from FrameMaker, but given that Laura > has only one small project in RH, I would suggest using MIF2Go or > Webworks ePublisher, since they're more flexible. > > On Tue, Dec 18, 2012 at 11:40 AM, Bill Swallow <[email protected]> > wrote: > > I'm a big advocate for WWeP but since they indicated they already use RH, > > the TCS option was a best fit. > _______________________________________________ > > > You are currently subscribed to framers as [email protected]. > > Send list messages to [email protected]. > > To unsubscribe send a blank email to > [email protected] > or visit > http://lists.frameusers.com/mailman/options/framers/techcommdood%40gmail.com > > Send administrative questions to [email protected]. Visit > http://www.frameusers.com/ for more resources and info. > -- Bill Swallow Writing and Content Strategy Consultant http://www.linkedin.com/in/techcommdood
_______________________________________________ You are currently subscribed to framers as [email protected]. Send list messages to [email protected]. To unsubscribe send a blank email to [email protected] or visit http://lists.frameusers.com/mailman/options/framers/archive%40mail-archive.com Send administrative questions to [email protected]. Visit http://www.frameusers.com/ for more resources and info.
