<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=us-ascii">
<style>
<!--
@font-face
{font-family:Calibri}
@font-face
{font-family:Tahoma}
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin-right:0in;
margin-left:0in;
font-size:12.0pt;
font-family:"Times New Roman","serif"}
a:link, span.MsoHyperlink
{color:blue;
text-decoration:underline}
a:visited, span.MsoHyperlinkFollowed
{color:purple;
text-decoration:underline}
span.EmailStyle17
{font-family:"Calibri","sans-serif";
color:#1F497D}
.MsoChpDefault
{font-size:10.0pt}
@page WordSection1
{margin:1.0in 1.0in 1.0in 1.0in}
div.WordSection1
{}
-->
</style><style>
<!--
p.MsoNormal
{margin-left:3.0pt}
-->
</style>
</head>
<body lang="EN-US" link="blue" vlink="purple" style="margin-left:3.0pt; margin-top:3.0pt; margin-right:3.0pt; margin-bottom:.75pt">
<div class="WordSection1">
<p class="MsoNormal"><span style="font-size:11.0pt; font-family:"Calibri","sans-serif"; color:#1F497D">You may want to look at the Confluence wiki. I know that there is a DITA > Confluence tool (Dita2Wiki?) and WebWorks ePublisher will also convert FM to Confluence.
However, I don’t know if it’s possible to go the other way, or to round-trip content between FM DITA and Confluence. According to Sarah Maddox’s book on wikis, Confluence will import and export DocBook XML so that might be another option.
</span></p>
<p class="MsoNormal"><span style="font-size:11.0pt; font-family:"Calibri","sans-serif"; color:#1F497D">I’m sure others will comment on this.</span></p>
<p class="MsoNormal"><span style="font-size:11.0pt; font-family:"Calibri","sans-serif"; color:#1F497D">Regards,</span></p>
<p class="MsoNormal"><span style="font-size:11.0pt; font-family:"Calibri","sans-serif"; color:#1F497D">Keith<br>
<br>
</span></p>
<div style="border:none; border-left:solid blue 1.5pt; padding:0in 0in 0in 4.0pt">
<div>
<div style="border:none; border-top:solid #B5C4DF 1.0pt; padding:3.0pt 0in 0in 0in">
<p class="MsoNormal" style="margin:0in; margin-bottom:.0001pt"><b><span style="font-size:10.0pt; font-family:"Tahoma","sans-serif"">From:</span></b><span style="font-size:10.0pt; font-family:"Tahoma","sans-serif""> framers-bounces@lists.frameusers.com [mailto:framers-bounces@lists.frameusers.com]
<b>On Behalf Of </b>rebecca officer<br>
<b>Sent:</b> Monday, June 25, 2012 2:03 AM<br>
<b>To:</b> framers@lists.frameusers.com<br>
<b>Subject:</b> Single sourcing from Frame and a wiki ... or something ...</span></p>
</div>
</div>
<p class="MsoNormal"> </p>
<div>
<p class="MsoNormal" style="margin:0in; margin-bottom:.0001pt"><span style="font-size:10.0pt; font-family:"Tahoma","sans-serif"">Hi everyone</span></p>
</div>
<div>
<p class="MsoNormal" style="margin:0in; margin-bottom:.0001pt"><span style="font-size:10.0pt; font-family:"Tahoma","sans-serif""> </span></p>
</div>
<div>
<p class="MsoNormal" style="margin:0in; margin-bottom:.0001pt"><span style="font-size:10.0pt; font-family:"Tahoma","sans-serif"">Our docs team (4 of us) creates a many-thousand-page multi-chapter user manual in unstructured Frame. Lots of tables and cross-refs.
Conditional text used to publish several variants. Published as PDFs a couple of times a year, delivered online.
</span></p>
</div>
<div>
<p class="MsoNormal" style="margin:0in; margin-bottom:.0001pt"><span style="font-size:10.0pt; font-family:"Tahoma","sans-serif""> </span></p>
</div>
<div>
<p class="MsoNormal" style="margin:0in; margin-bottom:.0001pt"><span style="font-size:10.0pt; font-family:"Tahoma","sans-serif"">And the engineers (about 80) have a wiki that's a mish-mash of internal feature development info, some of which ends up in the user
manual.</span></p>
</div>
<div>
<p class="MsoNormal" style="margin:0in; margin-bottom:.0001pt"><span style="font-size:10.0pt; font-family:"Tahoma","sans-serif""> </span></p>
</div>
<div>
<p class="MsoNormal" style="margin:0in; margin-bottom:.0001pt"><span style="font-size:10.0pt; font-family:"Tahoma","sans-serif"">I've been asked to make the user manual and the internal docs use the same source, which both writers and engineers would write.
We want to work collaboratively, stop duplicating effort and come much closer to real-time updates.</span></p>
</div>
<div>
<p class="MsoNormal" style="margin:0in; margin-bottom:.0001pt"><span style="font-size:10.0pt; font-family:"Tahoma","sans-serif""> </span></p>
</div>
<div>
<p class="MsoNormal" style="margin:0in; margin-bottom:.0001pt"><span style="font-size:10.0pt; font-family:"Tahoma","sans-serif"">I'll need to include version control, content re-use, status tagging (e.g. draft/final), read-only access, and delivery as PDF and
HTML. While I'm at it, I'd like to do automated builds and publish ebooks.</span></p>
</div>
<div>
<p class="MsoNormal" style="margin:0in; margin-bottom:.0001pt"><span style="font-size:10.0pt; font-family:"Tahoma","sans-serif""> </span></p>
</div>
<div>
<p class="MsoNormal" style="margin:0in; margin-bottom:.0001pt"><span style="font-size:10.0pt; font-family:"Tahoma","sans-serif"">The engineers would like the wiki to be the source. The writers want to stay with FM. I'm prepared to make everyone change tools
(*grin*) but only if we have to.</span></p>
</div>
<div>
<p class="MsoNormal" style="margin:0in; margin-bottom:.0001pt"><span style="font-size:10.0pt; font-family:"Tahoma","sans-serif""> </span></p>
</div>
<div>
<p class="MsoNormal" style="margin:0in; margin-bottom:.0001pt"><span style="font-size:10.0pt; font-family:"Tahoma","sans-serif"">As a complicating factor, the engineers are all on Linux. Getting an FM licence per engineer would blow my budget (Adobe, how about
selling a site licence???), and they'd have to run it in Virtual Box. I'm not seeing a happy ending there.</span></p>
</div>
<div>
<p class="MsoNormal" style="margin:0in; margin-bottom:.0001pt"><span style="font-size:10.0pt; font-family:"Tahoma","sans-serif""> </span></p>
</div>
<div>
<p class="MsoNormal" style="margin:0in; margin-bottom:.0001pt"><span style="font-size:10.0pt; font-family:"Tahoma","sans-serif"">I've got plenty of implementation time and can lay my mitts on a programmer or two. Budget's not yet set but prob around $20K.</span></p>
</div>
<div>
<p class="MsoNormal" style="margin:0in; margin-bottom:.0001pt"><span style="font-size:10.0pt; font-family:"Tahoma","sans-serif""> </span></p>
</div>
<div>
<p class="MsoNormal" style="margin:0in; margin-bottom:.0001pt"><span style="font-size:10.0pt; font-family:"Tahoma","sans-serif"">So ...</span></p>
</div>
<div>
<p class="MsoNormal" style="margin:0in; margin-bottom:.0001pt"><span style="font-size:10.0pt; font-family:"Tahoma","sans-serif""> </span></p>
</div>
<div>
<p class="MsoNormal" style="margin:0in; margin-bottom:.0001pt"><span style="font-size:10.0pt; font-family:"Tahoma","sans-serif"">Does anyone know of a good tool for round-tripping Framemaker <--> Wiki?
</span></p>
</div>
<div>
<p class="MsoNormal" style="margin:0in; margin-bottom:.0001pt"><span style="font-size:10.0pt; font-family:"Tahoma","sans-serif""> </span></p>
</div>
<div>
<p class="MsoNormal" style="margin:0in; margin-bottom:.0001pt"><span style="font-size:10.0pt; font-family:"Tahoma","sans-serif"">Should I be looking at XML?</span></p>
</div>
<div>
<p class="MsoNormal" style="margin:0in; margin-bottom:.0001pt"><span style="font-size:10.0pt; font-family:"Tahoma","sans-serif""> </span></p>
</div>
<div>
<p class="MsoNormal" style="margin:0in; margin-bottom:.0001pt"><span style="font-size:10.0pt; font-family:"Tahoma","sans-serif"">Any other thoughts on how I should tackle this?</span></p>
</div>
<div>
<p class="MsoNormal" style="margin:0in; margin-bottom:.0001pt"><span style="font-size:10.0pt; font-family:"Tahoma","sans-serif""> </span></p>
</div>
<div>
<p class="MsoNormal" style="margin:0in; margin-bottom:.0001pt"><span style="font-size:10.0pt; font-family:"Tahoma","sans-serif"">Many thanks<br>
Rebecca</span></p>
</div>
<div>
<p class="MsoNormal" style="margin:0in; margin-bottom:.0001pt"><span style="font-size:10.0pt; font-family:"Tahoma","sans-serif""> </span></p>
</div>
<div>
<p class="MsoNormal" style="margin:0in; margin-bottom:.0001pt"><span style="font-size:10.0pt; font-family:"Tahoma","sans-serif""> </span></p>
</div>
<div>
<p class="MsoNormal" style="margin:0in; margin-bottom:.0001pt"><span style="font-size:10.0pt; font-family:"Tahoma","sans-serif""> </span></p>
</div>
<div>
<p class="MsoNormal" style="margin:0in; margin-bottom:.0001pt"><span style="font-size:10.0pt; font-family:"Tahoma","sans-serif""> </span></p>
</div>
<p class="MsoNormal" style="margin:0in; margin-bottom:.0001pt"><span style="font-size:10.0pt; font-family:"Tahoma","sans-serif""><br>
NOTICE: This message contains privileged and confidential<br>
information intended only for the use of the addressee<br>
named above. If you are not the intended recipient of<br>
this message you are hereby notified that you must not<br>
disseminate, copy or take any action in reliance on it.<br>
If you have received this message in error please<br>
notify Allied Telesis Labs Ltd immediately.<br>
Any views expressed in this message are those of the<br>
individual sender, except where the sender has the<br>
authority to issue and specifically states them to<br>
be the views of Allied Telesis Labs. </span></p>
</div>
</div>
<font size="2" face="arial"><br>
NOTICE OF CONFIDENTIALITY This e-mail, including all materials contained in or attached to this e-mail, contains proprietary and confidential information solely for the internal use of the intended recipient. If you have received this email in error, please
notify us immediately by return e-mail or otherwise and ensure that it is permanently deleted from your systems, and do not print, copy, distribute or read its contents.
<br>
<br>
AVIS DE CONFIDENTIALITÉ Le présent courriel, y compris tous les documents qu'il contient ou qui y sont joints, renferme des renseignements exclusifs et confidentiels destinés uniquement à l'usage interne du destinataire prévu. Si vous avez reçu le présent courriel
par erreur, veuillez nous aviser immédiatement, notamment par retour de courriel, et vous assurer qu'il est supprimé de façon permanente de vos systèmes; veuillez également vous abstenir d'imprimer, de copier, de distribuer ou de lire son contenu.
</font>
</body>
</html>