Re: [Framers] VSdocman Outputs to FM

Most developers expect API documentation in HTML format these days. If you haven't done it before it may seem like a lot of overhead, but in the long run putting API documentation in the code and generating it automatically saves time and helps ensure accuracy. Seriously, take a look at

Re: [Framers] VSdocman Outputs to FM

: Thu, 2 Mar 2017 09:01:06 -0800 From: "Monique Semp" <monique.s...@earthlink.net> To: <framers@lists.frameusers.com> Subject: Re: [Framers] VSdocman Outputs to FM Message-ID: <5495A9F706E84A819133D344542E13AA@WQI1509Dell> Content-Type: text/plain; format=flowed; charset=&quo

Re: [Framers] VSdocman Outputs to FM

I agree, if there's an API doc generator, using it would certainly be my first choice. You might also take a look at Document!X. That said, recent releases of FrameMaker reportedly do a much better job of importing Word. On Thu, Mar 2, 2017 at 9:01 AM, Monique Semp

Re: [Framers] VSdocman Outputs to FM

Just wondering why the need to convert to FrameMaker at all? Why not just use VSdocman and create the appropriate output (http://www.helixoft.com/vsdocman/examples.html)? It purports to create HTML, CHM, PDF, XML, and more. That would mean, of course, that the result would likely be strictly

[Framers] VSdocman Outputs to FM

Hi All, A software team manager came to me asking for help creating an API manual. They had a specialized developer create about 200 API's and they need a manual in about a week. The developer has no time for documentation. My programming skills are very limited, but I have some light