Layout things on a page is so much different that laying it out on HTML, you want things to wrap differently around graphics and you want page breaks to be natural and not broken. That way I’m not going back and forth on the initial pass. Like I said, I have to transfer by hand everything from the HTML, but I make sure initially I do the PDF LAST, when I’m very confident in the HTML. I’ve used Pagemaker since the 1980’s so it’s real easy for me to use. So far so good, everything is platform-specific and industry-standard so no one should be surprised.įor the PDF I use Adobe’s inDesign, the best IMHO layout program around. Also, in my apps, I link to my company’s web site which has this same HTML code-base but it may be more updated than what their current HelpFile/HelpViewer is. For Mac I simply move it into the app bundle and HelpViewer displays it and it looks great. ![]() ![]() On Windows I use the standard old HTML Workshop from Microsoft to make the CHM Help File (standard). I am not convinced any of these automated solutions, even the expensive ones, have the intelligence (if it’s even possible) to make a decent-looking PDF document based on what has to be HTML for the other Help methods. Documentation should look good to impress your customers/clients. ![]() This is something all the automated solutions downplay. Although it is NOT single-code-based, I find it very effective and best of all makes everything look like I want it to.
0 Comments
Leave a Reply. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |