![]() RoboHelp requires at least 15 macros to clean up printed documentation output (e.g., numbering). If they bury it, they will anger an immense group of RoboHelp users who recently spent $500 for the upgrade.ĥ. RoboHelp isn't compatible with Word 2007 ( nor with Vista), so when Vista and Office 2007 become mainstream, Adobe will either have to fix or bury RoboHelp. ![]() RoboHelp isn't compatible with Word 2007. So basically you would have to manually do all your cross references, or use a touchy macro workaround.Ĥ. If you link to another topic in the online help, when you output to printed documentation, the link doesn't translate into a cross reference. RoboHelp doesn't support cross references. So if your topic spans 3 pages, and the keywords relate to the last page, the index will point the reader to the first page, where the header is.ģ. But if you do output to print, your index will never be accurate because all the keywords are crammed into the topic headings rather than where they appear in the document. If all you create is online documentation, the printed documentation indexing glitch isn't an issue. This is probably the biggest strike against using RoboHelp as a single sourcing tool. RoboHelp doesn't support character level indexing. Sorry Adobe, but you really get a D when it comes to communication.Ģ. But even the senior project evangelist, R.J. ![]() Vivek Jain, Adobe's RoboHelp blogger, either is totally clueless about responding to comments, or he doesn't understand that a blog is not a PR marketing vehicle. Today I just checked again and saw that someone else's comment had been approved. I followed up to ask if the comment got lost in the moderation queue. I assumed my comment was in moderation, but apparently it was filtered. Have you ever posted a comment on their blog? After I finished the RoboHelp podcast on Tech Writer Voices, I posted a comment on the Adobe RoboHelp blog letting them know about the podcast. Author in DITA and Publish with WordPressĪlthough I currently use RoboHelp 5, I can think of at least 10 good reasons not to upgrade to RoboHelp 6.Reflecting seven years later about why we were laid off.A hypothesis about influence on the web and the workplace.
0 Comments
Leave a Reply. |