<html dir="ltr">
<head>
<meta http-equiv="Content-Type" content="text/html; charset=Windows-1252">
<style id="owaParaStyle" type="text/css"></style>
</head>
<body ocsi="0" fpstyle="1" dir="auto">
<div style="direction: ltr;font-family: Tahoma;color: #000000;font-size: 10pt;">Thank you for all of your responses! You have answered my question quite sufficiently (except one that I'm addressing personally about a clever trick someone does). Folders it is!<br>
<br>
I'm also encouraged that my email hit the distribution in about an hour rather than taking more than a day, which is one of the primary reasons for my lurker status. :)<br>
<br>
Tim<br>
<br>
<div style="font-family: Times New Roman; color: #000000; font-size: 16px">
<hr tabindex="-1">
<div style="direction: ltr;" id="divRpF726393"><font color="#000000" face="Tahoma" size="2"><b>From:</b> Scott Turner [quills@airmail.net]<br>
<b>Sent:</b> Thursday, February 05, 2015 10:10 AM<br>
<b>To:</b> Syed Zaeem Hosain (Syed.Hosain@aeris.net)<br>
<b>Cc:</b> Rick Quatro; Tim Pann; framers@lists.frameusers.com<br>
<b>Subject:</b> Re: Basic question: Book revision best practices<br>
</font><br>
</div>
<div></div>
<div>
<div>Rick and Syed have the meat of it. Keep it simple.</div>
<div><br>
</div>
<div>We do not use small increments, the x.1 and so forth, because we consider all changes to the doc as major. We don't have to worry over what constitutes a minor or major version.<br>
<br>
</div>
<div><br>
On Feb 5, 2015, at 11:41, Syed Zaeem Hosain (<a href="mailto:Syed.Hosain@aeris.net" target="_blank">Syed.Hosain@aeris.net</a>) <<a href="mailto:Syed.Hosain@aeris.net" target="_blank">Syed.Hosain@aeris.net</a>> wrote:<br>
<br>
</div>
<blockquote type="cite">
<div><style>
<!--
@font-face
{font-family:"Cambria Math"}
@font-face
{font-family:Calibri}
@font-face
{font-family:Tahoma}
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
margin-bottom:.0001pt;
font-size:11.0pt;
font-family:"Calibri",sans-serif}
a:link, span.MsoHyperlink
{color:blue;
text-decoration:underline}
a:visited, span.MsoHyperlinkFollowed
{color:purple;
text-decoration:underline}
p
{margin:0in;
margin-bottom:.0001pt;
font-size:12.0pt;
font-family:"Times New Roman",serif}
p.MsoAcetate, li.MsoAcetate, div.MsoAcetate
{margin:0in;
margin-bottom:.0001pt;
font-size:8.0pt;
font-family:"Tahoma",sans-serif}
span.BalloonTextChar
{font-family:"Tahoma",sans-serif}
p.msochpdefault, li.msochpdefault, div.msochpdefault
{margin:0in;
margin-bottom:.0001pt;
font-size:12.0pt;
font-family:"Calibri",sans-serif}
span.emailstyle17
{font-family:"Arial",sans-serif;
color:windowtext;
font-weight:normal;
font-style:normal}
span.balloontextchar0
{font-family:"Tahoma",sans-serif}
span.EmailStyle23
{font-family:"Calibri",sans-serif;
color:#1F497D}
span.EmailStyle24
{font-family:"Calibri",sans-serif;
color:#1F497D}
.MsoChpDefault
{font-size:10.0pt}
@page WordSection1
{margin:1.0in 1.0in 1.0in 1.0in}
-->
BODY {direction: ltr;font-family: Tahoma;color: #000000;font-size: 10pt;}P {margin-top:0;margin-bottom:0;}</style>
<div class="WordSection1">
<p class="MsoNormal"><span style="color:#1F497D">Tim, I agree entirely with Rick.</span></p>
<p class="MsoNormal"><span style="color:#1F497D"> </span></p>
<p class="MsoNormal"><span style="color:#1F497D">I like to leave a directory/folder with all the files (including the output PDF) of older versions, so that I can refer to/recreate them later as needed – questions about prior versions of documents do arise.</span></p>
<p class="MsoNormal"><span style="color:#1F497D"> </span></p>
<p class="MsoNormal"><span style="color:#1F497D">Being able to compare files (to see what changed from version B to version F) is often useful too.</span></p>
<p class="MsoNormal"><span style="color:#1F497D"> </span></p>
<p class="MsoNormal"><span style="color:#1F497D">The names of the books and the files stay unchanged as a result of this approach.</span></p>
<p class="MsoNormal"><span style="color:#1F497D"> </span></p>
<p class="MsoNormal"><span style="color:#1F497D">(FWIW though, I am thinking of switching to GIT for this purpose in the future. Then, I can recreate any released version as needed, rather than having a separated directory/folder for each.)</span></p>
<p class="MsoNormal"><span style="color:#1F497D"> </span></p>
<p class="MsoNormal"><span style="color:#1F497D">Z</span></p>
<p class="MsoNormal"><span style="color:#1F497D"> </span></p>
<div>
<div style="border:none; border-top:solid #E1E1E1 1.0pt; padding:3.0pt 0in 0in 0in">
<p class="MsoNormal"><b>From:</b> <a href="mailto:framers-bounces@lists.frameusers.com" target="_blank">
framers-bounces@lists.frameusers.com</a> [<a href="mailto:framers-bounces@lists.frameusers.com" target="_blank">mailto:framers-bounces@lists.frameusers.com</a>]
<b>On Behalf Of </b>Rick Quatro<br>
<b>Sent:</b> Thursday, February 05, 2015 9:15 AM<br>
<b>To:</b> 'Tim Pann'; <a href="mailto:framers@lists.frameusers.com" target="_blank">
framers@lists.frameusers.com</a><br>
<b>Subject:</b> RE: Basic question: Book revision best practices</p>
</div>
</div>
<p class="MsoNormal"> </p>
<p class="MsoNormal"><span style="color:#1F497D">Hi Tim,</span></p>
<p class="MsoNormal"><span style="color:#1F497D"> </span></p>
<p class="MsoNormal"><span style="color:#1F497D">I prefer to do my versioning at the folder level. That way, I never have to rename .book or .fm files. When I am ready for 1.1, I create a folder and copy all of the 1.0 files to it. You can rename book components
and FrameMaker will resolve cross-references, etc. but I prefer filenames that I can leave unchanged.</span></p>
<p class="MsoNormal"><span style="color:#1F497D"> </span></p>
<p class="MsoNormal"><span style="color:#1F497D">Rick</span></p>
<p class="MsoNormal"><span style="color:#1F497D"> </span></p>
<p class="MsoNormal"><span style="color:#1F497D">Rick Quatro</span></p>
<p class="MsoNormal"><span style="color:#1F497D">Carmen Publishing Inc.</span></p>
<p class="MsoNormal"><span style="color:#1F497D">585-366-4017</span></p>
<p class="MsoNormal"><span style="color:#1F497D"><a href="mailto:rick@frameexpert.com" target="_blank">rick@frameexpert.com</a></span></p>
<p class="MsoNormal"><span style="color:#1F497D"> </span></p>
<p class="MsoNormal"><span style="color:#1F497D"> </span></p>
<p class="MsoNormal"><span style="color:#1F497D"> </span></p>
<div>
<div style="border:none; border-top:solid #B5C4DF 1.0pt; padding:3.0pt 0in 0in 0in">
<p class="MsoNormal"><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">
<a href="mailto:framers-bounces@lists.frameusers.com" target="_blank">framers-bounces@lists.frameusers.com</a> [<a href="mailto:framers-bounces@lists.frameusers.com" target="_blank">mailto:framers-bounces@lists.frameusers.com</a>]
<b>On Behalf Of </b>Tim Pann<br>
<b>Sent:</b> Thursday, February 05, 2015 11:55 AM<br>
<b>To:</b> <a href="mailto:framers@lists.frameusers.com" target="_blank">framers@lists.frameusers.com</a><br>
<b>Subject:</b> Basic question: Book revision best practices</span></p>
</div>
</div>
<p class="MsoNormal"> </p>
<div>
<p class="MsoNormal"><span style="font-size:10.0pt; font-family:"Tahoma",sans-serif; color:black">Hello,<br>
<br>
I'm a long-time lurker sometime poster. Not particularly active on the list because my use of Frame is pretty limited. (I am a technical trainer and I do not follow strict version control practices, so some of this will probably make some folks on this list
bristle.) But I would love some input on this particular issue. I'm using Frame 9 on Windows 7 but I doubt that is relevant here.<br>
<br>
I have a book file that contains several chapters, a TOC, and a title page. Very simple. The book is version 1.0. The book file and all other files contain "v1-0" in the filename. All files have "Version 1.0" in the footer, and the date of release.<br>
<br>
Now I want to make changes, so it will become version 1.1. What do best practices say to do? I assume save all content, TOC, and title files as new "v1-1" files. Should I create a new "v1-1" book file into which the v1-1 content goes? Or should the book file
itself be version agnostic?<br>
<br>
Depending on answers to these questions I may have other questions so feel free to be exhaustive. Or, if you can provide a link to such information all the better.<br>
<br>
Thank you,<br>
Tim</span></p>
</div>
</div>
</div>
</blockquote>
<blockquote type="cite">
<div><span>_______________________________________________</span><br>
<span></span><br>
<span></span><br>
<span>You are currently subscribed to framers as <a href="mailto:quills@airmail.net" target="_blank">
quills@airmail.net</a>.</span><br>
<span></span><br>
<span>Send list messages to <a href="mailto:framers@lists.frameusers.com" target="_blank">
framers@lists.frameusers.com</a>.</span><br>
<span></span><br>
<span>To unsubscribe send a blank email to</span><br>
<span><a href="mailto:framers-unsubscribe@lists.frameusers.com" target="_blank">framers-unsubscribe@lists.frameusers.com</a></span><br>
<span>or visit <a href="http://lists.frameusers.com/mailman/options/framers/quills%40airmail.net" target="_blank">
http://lists.frameusers.com/mailman/options/framers/quills%40airmail.net</a></span><br>
<span></span><br>
<span>Send administrative questions to <a href="mailto:listadmin@frameusers.com" target="_blank">
listadmin@frameusers.com</a>. Visit</span><br>
<span><a href="http://www.frameusers.com/" target="_blank">http://www.frameusers.com/</a> for more resources and info.</span><br>
</div>
</blockquote>
</div>
</div>
</div>
</body>
</html>