TechWhirl (TECHWR-L) is a resource for technical writing and technical communications professionals of all experience levels and in all industries to share their experiences and acquire information.
For two decades, technical communicators have turned to TechWhirl to ask and answer questions about the always-changing world of technical communications, such as tools, skills, career paths, methodologies, and emerging industries. The TechWhirl Archives and magazine, created for, by and about technical writers, offer a wealth of knowledge to everyone with an interest in any aspect of technical communications.
What's a good versioning system for Office documents?
Subject:What's a good versioning system for Office documents? From:"Edgar D' Souza" <edgar -dot- b -dot- dsouza -at- gmail -dot- com> To:"List,Techwriter" <techwr-l -at- lists -dot- techwr-l -dot- com> Date:Sat, 8 Jul 2006 13:27:37 +0530
Hi all,
I've googled a lot and searched TECHWR-L archives, but haven't come up
with a definitive answer to my question, therefore this post. I have
been tasked with researching a decent, Office-doc-friendly
versioning/Source Control System for a small (5-member) documentation
team at our clients' site.
A few facts:
0. The versioning/SCS system will be used with MS Office (primarily
Word) documents, American English only, to the best of my knowledge.
1. If possible, the SCS should store deltas/diffs of documents instead
of the entire new copy of an edited document.
2. If possible, the SCS should allow users to view the differences
between various versions of a document.
3. The SCS will also need to store images, and possibly other files,
which are linked into the Word documents.
4. Storage requirements are low to medium - at present, the doc team
is 5 members, and the combined storage requirement (documents +
images) for five manuals is around 60MB. That includes redundant
content which should be shared between manuals - once this is done,
the size will actually drop - but even after that, content will not
grow at a high rate.
5. While our client is willing to purchase licenses as needed, they
don't want to break the bank in doing so :-)
6. The client is essentially a Microsoft shop, and would prefer a
Windows-based software, though if the price difference is compelling,
they would also consider products that run on other OSs.
Given the above, could you recommend one or more products that might
fit the bill? I welcome plenty of feedback (and thanks in advance for
your help!), especially if you already use such a product, and could
give me your valuable feedback on how well it works for you.
Thank you,
Ed.
--
Technical Documentation Specialist, teclarity.com
____________________
To be or not to be. -- Shakespeare
To do is to be. -- Nietzsche
To be is to do. -- Sartre
Do be do be do. -- Sinatra
Yabba dabba do -- Flintstones
Just do it! -- Nike
____________________
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
WebWorks ePublisher Pro for Word features support for every major Help
format plus PDF, HTML and more. Flexible, precise, and efficient content
delivery. Try it today!. http://www.webworks.com/techwr-l
Doc-To-Help includes a one-click RoboHelp project converter. It's that easy. Watch the demo at http://www.DocToHelp.com/TechwrlList