<html>
<head>
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
<div class="moz-cite-prefix">Mif2Go might be a good solution. I
suggest using a Mif2Go expert such as Steve Wiseman to set it up.
After that you just click a button and it creates help that
requires very little or no clean-up afterwards. <br>
<br>
You can contact him at: <a class="moz-txt-link-abbreviated" href="mailto:swiseman@context.co.il">swiseman@context.co.il</a> or +972-2-999-7816.
<br>
<br>
<pre class="moz-signature" cols="72">Shmuel Wolfson
Technical Writer
052-763-7133
</pre>
On 15-Jul-14 9:07 PM, Joe Malin wrote:<br>
</div>
<blockquote cite="mid:CFEABC08.674%25Joe.Malin@magnet.com"
type="cite">
<meta http-equiv="Content-Type" content="text/html;
charset=ISO-8859-1">
<div>Hi!</div>
<div><br>
</div>
<div>I work for a small startup that delivers documentation to
software developers. I’m investigating how to continue our
strategy of publishing to HTML so that we can “merge” our
reference documentation (such as Javadoc) with our developer
guides, samples, and so forth. </div>
<div><br>
</div>
<div>Our legacy is unstructured FrameMaker 12, which I’d prefer to
continue for the moment. We use FrameMaker’s multi-publishing
feature to output to Responsive HTML5, using the RoboHelp
features that come with FM. However, this approach isn’t
customizable, as far as I can tell. I’m sure to get pressure to
make our docs conform to the rest of the company’s design
philosophy.</div>
<div><br>
</div>
<div>How should I proceed? Full RoboHelp would probably give us
the customization we need without a lot of work, but RoboHelp is
very expensive. We could go to structured FM and convert XML to
HTML5 using XSLT (I was a software engineer in a past life, so I
don’t find this troubling), but it’s a lot of work. Going to a
different content/publishing solution would take some
‘splaining, since we’ve already invested in FM 12. But, if it
were cheap enough, we could consider it.</div>
<div><br>
</div>
<div>I should add that we use Git for CMS. This approach actually
works pretty well, since our goal is to track versions and
branches rather than save space or do line-by-line reviews. For
reviews, we’re currently using Acrobat XI features based on
tagged PDF from FM 12.</div>
<div><br>
</div>
<div>Thoughts? I would be grateful for any advice!</div>
<div><br>
</div>
<div>Joe</div>
This e-mail and any attached files are intended solely for the use
of the individual or entity to which this mail is addressed and
may contain information that is privileged, confidential and
exempt from disclosure under applicable law. Any use, disclosure,
copying or distribution of this e-mail or the attached files by
anyone other than the intended recipient is strictly prohibited.
If you have received this e-mail in error, please notify the
sender by reply e-mail or collect call to (650) 388-4111 and
delete this e-mail and attached files from your system. Thank you.
<br>
<fieldset class="mimeAttachmentHeader"></fieldset>
<br>
<pre wrap="">_______________________________________________
You are currently subscribed to framers as <a class="moz-txt-link-abbreviated" href="mailto:shmuelw1@gmail.com">shmuelw1@gmail.com</a>.
Send list messages to <a class="moz-txt-link-abbreviated" href="mailto:framers@lists.frameusers.com">framers@lists.frameusers.com</a>.
To unsubscribe send a blank email to
<a class="moz-txt-link-abbreviated" href="mailto:framers-unsubscribe@lists.frameusers.com">framers-unsubscribe@lists.frameusers.com</a>
or visit <a class="moz-txt-link-freetext" href="http://lists.frameusers.com/mailman/options/framers/shmuelw1%40gmail.com">http://lists.frameusers.com/mailman/options/framers/shmuelw1%40gmail.com</a>
Send administrative questions to <a class="moz-txt-link-abbreviated" href="mailto:listadmin@frameusers.com">listadmin@frameusers.com</a>. Visit
<a class="moz-txt-link-freetext" href="http://www.frameusers.com/">http://www.frameusers.com/</a> for more resources and info.
</pre>
</blockquote>
<br>
</body>
</html>