<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
<style type="text/css" style="display:none;"><!-- P {margin-top:0;margin-bottom:0;} --></style>
</head>
<body dir="ltr">
<div id="divtagdefaultwrapper" style="font-size:12pt;color:#000000;font-family:Calibri,Helvetica,sans-serif;" dir="ltr">
<p style="margin-top:0;margin-bottom:0">Mick:</p>
<p style="margin-top:0;margin-bottom:0"><br>
</p>
<p style="margin-top:0;margin-bottom:0">Ok, this is well underway, though it's going to take some time as there is fairly major delta between Audacity 1.x and 2.2, with a great deal of feature rearranging and many outright new features, which I'm having to
spin up on through a mix of experimentation and appeal to the audacity org documentation. But it's exactly the sort of practice I wanted, and I need it now so the rewrite will move ahead with all deliberate speed. I haven't tackled the tutorials part yet,
and can't swear that I'll keep the original tasks exactly as they were, but all the basic chapter subjects will certainly be preserved. </p>
<p style="margin-top:0;margin-bottom:0"><br>
</p>
<p style="margin-top:0;margin-bottom:0">Btw, I'm not completely sold on the idea of eliminating all references to release/version numbers, which currently appear at the start of each chapter and a few other places. If someone tried to use the current manual
and didn't realize it was years out of date, they'd be lost in some fairly important ways. Clearly the need for this kind of update is burdensome, and I wouldn't advocate it in the Floss context for more than maybe first-order versions (ie 1.x vs 2.x), but
I'm not seeing any good purpose to burying the delta itself. Can you share your thinking on this?</p>
<p style="margin-top:0;margin-bottom:0"><br>
</p>
<p style="margin-top:0;margin-bottom:0">best,</p>
<p style="margin-top:0;margin-bottom:0"><br>
</p>
<p style="margin-top:0;margin-bottom:0">Matt</p>
<p style="margin-top:0;margin-bottom:0"><br>
</p>
<p style="margin-top:0;margin-bottom:0"> </p>
<br>
<br>
<div style="color: rgb(0, 0, 0);">
<hr style="display:inline-block;width:98%" tabindex="-1">
<div id="divRplyFwdMsg" dir="ltr"><font face="Calibri, sans-serif" style="font-size:11pt" color="#000000"><b>From:</b> Discuss <discuss-bounces@lists.flossmanuals.net> on behalf of Mick Chesterman <M.Chesterman@mmu.ac.uk><br>
<b>Sent:</b> Sunday, January 7, 2018 1:35 AM<br>
<b>To:</b> discuss@lists.flossmanuals.net<br>
<b>Subject:</b> Re: [FM Discuss] next steps on Audacity book</font>
<div> </div>
</div>
<div dir="ltr" style="font-size:12pt; color:#000000; background-color:#FFFFFF; font-family:Calibri,Arial,Helvetica,sans-serif">
<p class="x_MsoNormal">Hi Matt, </p>
<p class="x_MsoNormal"><br>
</p>
<p class="x_MsoNormal">That sounds good, </p>
<p class="x_MsoNormal"><br>
</p>
<p class="x_MsoNormal">Unfortunately as I migrated 95% of the books in from the last system, I'm down as the owner for all of those. </p>
<p class="x_MsoNormal"><br>
</p>
<p class="x_MsoNormal">I would say that where possible it would be good to take out references to software version numbers when we come across them.
<br>
</p>
<p class="x_MsoNormal"><br>
</p>
<p class="x_MsoNormal">Thanks</p>
<p class="x_MsoNormal">Mick<br>
</p>
<p class="x_MsoNormal"><br>
<span style="font-size:10.0pt; font-family:"Arial",sans-serif; color:#323E4F"></span></p>
<div id="x_Signature">
<div style="font-family:Tahoma; font-size:13px"></div>
</div>
<div dir="ltr" style="color:rgb(33,33,33)">
<hr tabindex="-1" style="display:inline-block; width:98%">
<div id="x_divRplyFwdMsg" dir="ltr"><font color="#000000" face="Calibri, sans-serif" style="font-size:11pt"><b>From:</b> Discuss <discuss-bounces@lists.flossmanuals.net> on behalf of M R <matrobnew@hotmail.com><br>
<b>Sent:</b> 06 January 2018 01:11<br>
<b>To:</b> discuss@lists.flossmanuals.net<br>
<b>Subject:</b> Re: [FM Discuss] next steps on Audacity book</font>
<div> </div>
</div>
<div>
<div id="x_divtagdefaultwrapper" dir="ltr" style="font-size:12pt; color:#000000; font-family:Calibri,Helvetica,sans-serif">
<p style="margin-top:0; margin-bottom:0">Actually I see it was Ryan who started the substantive updating in June, so I guess my question below is addressed to Ryan (hi Ryan) as much as Mick. </p>
<p style="margin-top:0; margin-bottom:0"><br>
</p>
<p style="margin-top:0; margin-bottom:0">Matt </p>
<br>
<br>
<div style="color:rgb(0,0,0)">
<hr tabindex="-1" style="display:inline-block; width:98%">
<div id="x_divRplyFwdMsg" dir="ltr"><font color="#000000" face="Calibri, sans-serif" style="font-size:11pt"><b>From:</b> Discuss <discuss-bounces@lists.flossmanuals.net> on behalf of M R <matrobnew@hotmail.com><br>
<b>Sent:</b> Friday, January 5, 2018 6:09 PM<br>
<b>To:</b> discuss@lists.flossmanuals.net<br>
<b>Subject:</b> [FM Discuss] next steps on Audacity book</font>
<div> </div>
</div>
<div dir="ltr">
<div id="x_x_divtagdefaultwrapper" dir="ltr" style="font-size:12pt; color:#000000; font-family:Calibri,Helvetica,sans-serif">
<p style="margin-top:0; margin-bottom:0">Hi Mick:</p>
<p style="margin-top:0; margin-bottom:0"><br>
</p>
<p style="margin-top:0; margin-bottom:0">One of your many hats here seems to be owner of the Audacity book. In that capacity, I wonder what you'd like to see done next with that book as it currently stands. It looks like back in June of last year you did
some preliminary work to acknowledge the then-current version 2.1.3 (we're now at 2.2.1), but as far as I can tell most of the extant screenshots and feature discussions throughout the book (other than the installation stuff you worked on) still refer to 1.x.
So would it be useful for me to just start working chapter by chapter to update screenshots and (where necessary) feature discussions to 2.2.x? I wouldn't be doing anything other than updating within the existing framework, and no fancy innovations like screen
vids <span>😊</span> Just addressing the delta from 1.x. What do you think?</p>
<p style="margin-top:0; margin-bottom:0"><br>
</p>
<p style="margin-top:0; margin-bottom:0">Matt</p>
</div>
</div>
</div>
</div>
</div>
</div>
"Before acting on this email or opening any attachments you should read the Manchester Metropolitan University email disclaimer available on its website http://www.mmu.ac.uk/emaildisclaimer "
</div>
</div>
</div>
</body>
</html>