<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META content="text/html; charset=us-ascii" http-equiv=Content-Type>
<META name=GENERATOR content="MSHTML 9.00.8112.16455"></HEAD>
<BODY style="MARGIN: 4px 4px 1px; FONT: 10pt Segoe UI">
<DIV dir=ltr align=left><SPAN class=185165415-28112012>I've not completely
followed this thread, but I do know of a wiki that lets you reuse content.
</SPAN></DIV>
<DIV dir=ltr align=left><SPAN class=185165415-28112012></SPAN> </DIV>
<DIV dir=ltr align=left><SPAN class=185165415-28112012>I've been using MindTouch
for one client, and it definitely lets you reuse content. I've created multiple
"guides" in it and have many sections that I've written once and reused in two
or more places. It's fairly easy to do. I do find the MindTouch editor to have
some significant missing functions (which we've requested), but the sharing of
content does work quite well.</SPAN></DIV>
<DIV> </DIV>
<P align=left><A name=_MailAutoSig><SPAN
style="FONT-FAMILY: Verdana; FONT-SIZE: 10pt; mso-no-proof: yes">~~~~~~~~~~~~~~~~~~~~~~~~~<BR>Linda
G. Gallagher<BR>TechCom Plus, LLC<BR>lindag at techcomplus dot
com<BR></SPAN></A><A title=blocked::http://www.techcomplus.com/
href="http://www.techcomplus.com/"><FONT face=Verdana><FONT color=#0000ff><SPAN
style="mso-bookmark: _MailAutoSig"><SPAN
style="mso-no-proof: yes">www.techcomplus.com</SPAN></SPAN><SPAN
style="mso-bookmark: _MailAutoSig"></SPAN></FONT></FONT></A><SPAN
style="mso-bookmark: _MailAutoSig"><SPAN
style="FONT-FAMILY: Verdana; FONT-SIZE: 10pt; mso-no-proof: yes">
<BR>303-450-9076 or
800-500-3144<BR>~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~<BR></SPAN></SPAN></P>
<DIV> </DIV><BR>
<DIV dir=ltr lang=en-us class=OutlookMessageHeader align=left>
<HR tabIndex=-1>
<FONT face=Tahoma><B>From:</B> framers-bounces@lists.frameusers.com
[mailto:framers-bounces@lists.frameusers.com] <B>On Behalf Of </B>rebecca
officer<BR><B>Sent:</B> Tuesday, November 27, 2012 10:12 PM<BR><B>To:</B> Robert
Lauriston; framers@lists.frameusers.com<BR><B>Subject:</B> Re: Confluence 4
export: the one feature that would justify myupgrading from
FM10<BR></FONT><BR></DIV>
<DIV></DIV>
<DIV>Yes, I guess we're using CT like text insets on a very fine-grained
scale.</DIV>
<DIV> </DIV>
<DIV>Darn about the lack of content reuse in Confluence. Since that thread in
July, I read some of Confluence's marketing material and got hopeful that they
might have enough text-inset-like behaviour for our needs. The AutoDesk hybrid
system looks great but is way out of our budget. Back to XML, I
guess.</DIV>
<DIV> </DIV>
<DIV>The goal of this is to get our software developers helping to write
the user docs. The software developers don't want to use XML because
it's difficult to learn. They want a nice straightforward wiki. I'll have to see
if it's possible to make XML authoring easy enough that software developers can
pick it up with pretty much no training. Ugh. </DIV>
<DIV> </DIV>
<DIV>Cheers</DIV>
<DIV>Rebecca<BR><BR>>>> Robert Lauriston <robert@lauriston.com>
28/11/12 17:49 >>><BR>Ah, so you're using conditional text like text
insets.<BR><BR>Neither Confluence nor any other extant wiki is set up for
reusing<BR>content. We discussed that in detail in July in the "Single
sourcing<BR>from Frame and a wiki ... or something ..." topic you started. As
I<BR>noted there, AutoDesk's hybrid system does what you want but
it's<BR>expensive.<BR><BR>On Tue, Nov 27, 2012 at 8:02 PM, rebecca
officer<BR><rebecca.officer@alliedtelesis.co.nz> wrote:<BR>> Hi
Robert<BR>><BR>> Thanks for discussing this - I really appreciate
it.<BR>><BR>> Our company produces half a dozen different hardware
products with similar<BR>> software feature sets. There's a lot of feature
overlap. And we do new<BR>> software releases at least annually. We've got
one set of source FM files,<BR>> and we use conditional text to build a
document set for each product at each<BR>> new release. Without conditional
text, we'd have to maintain multiple<BR>> similar copies of FM files, which
would be an error-rich nightmare. Many of<BR>> the differences are at the
word or sentence level, but we could rewrite them<BR>> into separate
paragraphs if we have to.<BR>><BR>> I think, if we go to Confluence, we'll
need to create one wiki space per<BR>> product (per release), so we can keep
delivering product-specific info. That<BR>> would mean maintaining multiple
similar copies, unless we can reuse content<BR>> in multiple spaces. So I'm
trying to work out what the Confluence model is<BR>> for reusing content, and
how we could get there from FM.<BR></DIV><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. </BODY></HTML>