To my knowledge, there's no practical way to do that kind of parallel
updating of doc versions using unstructured FrameMaker.
If updating multiple versions of the doc is a requirement, you should
evaluate other tools with better support for reuse, versioning,
variable sets, and profiling. Paligo
So is Paligo instead of FrameMaker?
בתאריך יום ד׳, 2 במאי 2018, 23:41, מאת Robert Lauriston <
> The way I have things set up on Paligo, when we ship, say, release
> 1.2, I branch the 1.2 doc to create the 1.3 doc, and update the
> version number variable
The way I have things set up on Paligo, when we ship, say, release
1.2, I branch the 1.2 doc to create the 1.3 doc, and update the
version number variable in the 1.3 doc to reflect the new number.
At that point, all the topics are the same. If I generate the 1.3 doc,
it's identical to the 1.2
Well, you could think of it like what is done with version control. When
Release 3 of Application A comes out, they create a branch for Release 3
and the trunk continues forward to Release 3.1 or 4 or whatever.
Sometimes fixes for Release 3 are that release only. Sometimes they also
The nature of software releases means that the number of conditions
would grow indefinitely. I don't see how this would not eventually
DITA (which is just a text markup standard) doesn't make sense if you
don't have a lot more reuse than simply maintaining multiple versions
I think it would depend on how many simultaneous versions you have to
manage. I've done something similar in Frame where I had to keep three
different versions of a document from one set of source files - there were
different features for different roles, not versions per se, but the
I switched to Paligo in part because it's very good at maintaining
multiple versions and handling reuse across versions. It has an
integrated CMS that handles that stuff.
I presume that structured FrameMaker with a compatible CMS that
supports reuse can do what I do with Paligo, but switching
At 11:52 PM 5/1/2018, Caroline Tabach wrote:
I have been asked what SW writing tool can manage versions. At first
I thought "version control" like you have in Software, but I found
they meant maintaining multiple versions of the User guides at the
same time. For instance, even when SW version
You can use conditional text to do this, but you have to be very careful
with tagging the conditional text. I've done this with a very, very
complicated documentation set: 3 main platforms with between 2-4 versions
each, with internal and external conditions on top of that.
There are two ways to
-- Forwarded message -
From: Caroline Tabach
Date: יום ג׳, 1 במאי 2018, 16:23
Subject: Managing Versions of documentation simultaneously
I have been asked what SW
Mail list logo