<html xmlns:v="urn:schemas-microsoft-com:vml" xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns:m="http://schemas.microsoft.com/office/2004/12/omml" xmlns="http://www.w3.org/TR/REC-html40"><head><meta http-equiv=Content-Type content="text/html; charset=utf-8"><meta name=Generator content="Microsoft Word 15 (filtered medium)"><style><!--
/* Font Definitions */
@font-face
{font-family:"Cambria Math";
panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
{font-family:Tahoma;
panose-1:2 11 6 4 3 5 4 4 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
margin-bottom:.0001pt;
font-size:11.0pt;
font-family:"Calibri",sans-serif;}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:blue;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:purple;
text-decoration:underline;}
p
{mso-style-priority:99;
margin:0in;
margin-bottom:.0001pt;
font-size:12.0pt;
font-family:"Times New Roman",serif;}
p.MsoAcetate, li.MsoAcetate, div.MsoAcetate
{mso-style-priority:99;
mso-style-link:"Balloon Text Char";
margin:0in;
margin-bottom:.0001pt;
font-size:8.0pt;
font-family:"Tahoma",sans-serif;}
span.BalloonTextChar
{mso-style-name:"Balloon Text Char";
mso-style-priority:99;
mso-style-link:"Balloon Text";
font-family:"Tahoma",sans-serif;}
p.msochpdefault, li.msochpdefault, div.msochpdefault
{mso-style-name:msochpdefault;
mso-style-priority:99;
margin:0in;
margin-bottom:.0001pt;
font-size:12.0pt;
font-family:"Calibri",sans-serif;}
span.emailstyle17
{mso-style-name:emailstyle17;
font-family:"Arial",sans-serif;
color:windowtext;
font-weight:normal;
font-style:normal;}
span.balloontextchar0
{mso-style-name:balloontextchar;
font-family:"Tahoma",sans-serif;}
span.EmailStyle23
{mso-style-type:personal;
font-family:"Calibri",sans-serif;
color:#1F497D;}
span.EmailStyle24
{mso-style-type:personal;
font-family:"Calibri",sans-serif;
color:#1F497D;}
span.EmailStyle25
{mso-style-type:personal;
font-family:"Calibri",sans-serif;
color:#1F497D;}
span.EmailStyle26
{mso-style-type:personal-reply;
font-family:"Calibri",sans-serif;
color:#1F497D;}
.MsoChpDefault
{mso-style-type:export-only;
font-size:10.0pt;}
@page WordSection1
{size:8.5in 11.0in;
margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext="edit" spidmax="1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext="edit">
<o:idmap v:ext="edit" data="1" />
</o:shapelayout></xml><![endif]--></head><body lang=EN-US link=blue vlink=purple><div class=WordSection1><p class=MsoNormal><span style='color:#1F497D'>Unfortunately, not an option for us … older documents have to be available for our customers just in case there is a question of “which version” did I develop to. :)<o:p></o:p></span></p><p class=MsoNormal><span style='color:#1F497D'><o:p> </o:p></span></p><p class=MsoNormal><span style='color:#1F497D'>Rarely (but it does happen), there are “branches” for older version document fixes … that are then brought into the main path later.<o:p></o:p></span></p><p class=MsoNormal><span style='color:#1F497D'><o:p> </o:p></span></p><p class=MsoNormal><span style='color:#1F497D'>Hench my thinking that I would switch to Git.<o:p></o:p></span></p><p class=MsoNormal><span style='color:#1F497D'><o:p> </o:p></span></p><p class=MsoNormal><span style='color:#1F497D'>Z<o:p></o:p></span></p><p class=MsoNormal><span style='color:#1F497D'><o:p> </o:p></span></p><p class=MsoNormal>Jeff Coatsworth wrote:<br><span lang=EN-CA style='color:#1F497D'>> Or you could really simplify things & not care about old versions after you’ve moved on to the new version. ;>)<o:p></o:p></span></p><p class=MsoNormal><span lang=EN-CA style='color:#1F497D'><o:p> </o:p></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">framers-bounces@lists.frameusers.com</a> [<a href="mailto:framers-bounces@lists.frameusers.com">mailto:framers-bounces@lists.frameusers.com</a>] <b>On Behalf Of </b>Scott Turner<br><b>Sent:</b> February-05-15 1:10 PM<br><b>To:</b> Syed Zaeem Hosain (<a href="mailto:Syed.Hosain@aeris.net">Syed.Hosain@aeris.net</a>)<br><b>Cc:</b> <a href="mailto:framers@lists.frameusers.com">framers@lists.frameusers.com</a><br><b>Subject:</b> Re: Basic question: Book revision best practices<o:p></o:p></span></p></div></div><p class=MsoNormal><span lang=EN-CA><o:p> </o:p></span></p><div><p class=MsoNormal><span lang=EN-CA>Rick and Syed have the meat of it. Keep it simple.<o:p></o:p></span></p></div><div><p class=MsoNormal><span lang=EN-CA><o:p> </o:p></span></p></div><div><p class=MsoNormal style='margin-bottom:12.0pt'><span lang=EN-CA>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.<o:p></o:p></span></p></div><div><p class=MsoNormal style='margin-bottom:12.0pt'><span lang=EN-CA>On Feb 5, 2015, at 11:41, Syed Zaeem Hosain (<a href="mailto:Syed.Hosain@aeris.net">Syed.Hosain@aeris.net</a>) <<a href="mailto:Syed.Hosain@aeris.net">Syed.Hosain@aeris.net</a>> wrote:<o:p></o:p></span></p></div><blockquote style='margin-top:5.0pt;margin-bottom:5.0pt'><div><p class=MsoNormal><span lang=EN-CA style='color:#1F497D'>Tim, I agree entirely with Rick.</span><span lang=EN-CA><o:p></o:p></span></p><p class=MsoNormal><span lang=EN-CA style='color:#1F497D'> </span><span lang=EN-CA><o:p></o:p></span></p><p class=MsoNormal><span lang=EN-CA 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><span lang=EN-CA><o:p></o:p></span></p><p class=MsoNormal><span lang=EN-CA style='color:#1F497D'> </span><span lang=EN-CA><o:p></o:p></span></p><p class=MsoNormal><span lang=EN-CA style='color:#1F497D'>Being able to compare files (to see what changed from version B to version F) is often useful too.</span><span lang=EN-CA><o:p></o:p></span></p><p class=MsoNormal><span lang=EN-CA style='color:#1F497D'> </span><span lang=EN-CA><o:p></o:p></span></p><p class=MsoNormal><span lang=EN-CA style='color:#1F497D'>The names of the books and the files stay unchanged as a result of this approach.</span><span lang=EN-CA><o:p></o:p></span></p><p class=MsoNormal><span lang=EN-CA style='color:#1F497D'> </span><span lang=EN-CA><o:p></o:p></span></p><p class=MsoNormal><span lang=EN-CA 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><span lang=EN-CA><o:p></o:p></span></p><p class=MsoNormal><span lang=EN-CA style='color:#1F497D'> </span><span lang=EN-CA><o:p></o:p></span></p><p class=MsoNormal><span lang=EN-CA style='color:#1F497D'>Z</span><span lang=EN-CA><o:p></o:p></span></p><p class=MsoNormal><span lang=EN-CA style='color:#1F497D'> </span><span lang=EN-CA><o:p></o:p></span></p><div><div style='border:none;border-top:solid #E1E1E1 1.0pt;padding:3.0pt 0in 0in 0in'><p class=MsoNormal><b><span lang=EN-CA>From:</span></b><span lang=EN-CA> <a href="mailto:framers-bounces@lists.frameusers.com">framers-bounces@lists.frameusers.com</a> [<a href="mailto:framers-bounces@lists.frameusers.com">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">framers@lists.frameusers.com</a><br><b>Subject:</b> RE: Basic question: Book revision best practices<o:p></o:p></span></p></div></div><p class=MsoNormal><span lang=EN-CA> <o:p></o:p></span></p><p class=MsoNormal><span lang=EN-CA style='color:#1F497D'>Hi Tim,</span><span lang=EN-CA><o:p></o:p></span></p><p class=MsoNormal><span lang=EN-CA style='color:#1F497D'> </span><span lang=EN-CA><o:p></o:p></span></p><p class=MsoNormal><span lang=EN-CA 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><span lang=EN-CA><o:p></o:p></span></p><p class=MsoNormal><span lang=EN-CA style='color:#1F497D'> </span><span lang=EN-CA><o:p></o:p></span></p><p class=MsoNormal><span lang=EN-CA style='color:#1F497D'>Rick</span><span lang=EN-CA><o:p></o:p></span></p><p class=MsoNormal><span lang=EN-CA style='color:#1F497D'> </span><span lang=EN-CA><o:p></o:p></span></p><p class=MsoNormal><span lang=EN-CA style='color:#1F497D'>Rick Quatro</span><span lang=EN-CA><o:p></o:p></span></p><p class=MsoNormal><span lang=EN-CA style='color:#1F497D'>Carmen Publishing Inc.</span><span lang=EN-CA><o:p></o:p></span></p><p class=MsoNormal><span lang=EN-CA style='color:#1F497D'>585-366-4017</span><span lang=EN-CA><o:p></o:p></span></p><p class=MsoNormal><span lang=EN-CA style='color:#1F497D'><a href="mailto:rick@frameexpert.com">rick@frameexpert.com</a></span><span lang=EN-CA><o:p></o:p></span></p><p class=MsoNormal><span lang=EN-CA style='color:#1F497D'> </span><span lang=EN-CA><o:p></o:p></span></p><p class=MsoNormal><span lang=EN-CA style='color:#1F497D'> </span><span lang=EN-CA><o:p></o:p></span></p><p class=MsoNormal><span lang=EN-CA style='color:#1F497D'> </span><span lang=EN-CA><o:p></o:p></span></p><div><div style='border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0in 0in 0in'><p class=MsoNormal><b><span lang=EN-CA style='font-size:10.0pt;font-family:"Tahoma",sans-serif'>From:</span></b><span lang=EN-CA style='font-size:10.0pt;font-family:"Tahoma",sans-serif'> <a href="mailto:framers-bounces@lists.frameusers.com">framers-bounces@lists.frameusers.com</a> [<a href="mailto:framers-bounces@lists.frameusers.com">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">framers@lists.frameusers.com</a><br><b>Subject:</b> Basic question: Book revision best practices</span><span lang=EN-CA><o:p></o:p></span></p></div></div><p class=MsoNormal><span lang=EN-CA> <o:p></o:p></span></p><div><p class=MsoNormal><span lang=EN-CA 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><span lang=EN-CA><o:p></o:p></span></p></div></div></blockquote></div></body></html>