<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">btw, I should add that there's a specific reason why the tables in the Menu chapter look less readable now than they did in the first version of the manual. In that version, the author was able in most cases to offer
a relatively short, non-wrapping description of the each menu option (ie, each row in the table describing that menu could contain a single, non-wrapping description of what that option did). So this mapped across very well with the option name, and made
the whole table simple and clean-looking. But that was because Audacity itself, in its first release, had adopted a relatively 'flat' single-level Menu structure with relatively little use of submenus. It's quite a different design now, with either submenus
or specialized dialog boxes evoked by nearly every option in the main menus. The way Audacity's own online manual deals with this is to simply say something like
<b>Edit > Tracks</b>: "The <u>Tracks Submenu</u> allows for various manipulations of selected tracks"; and then
<u>Tracks Submenu</u> is itself a hyperlink to a whole different page dealing exclusively with that submenu, with its own screenshot and detailed walk-throughs of each option there, so the reader got all the information they could need. This wiki-style approach
wasn't possible within the Floss framework, which still presumes a PDF, eBook or printed book as its ideal end work product, and doesn't 'chunk' information by page at any finer granularity than the chapter themselves. So I had to basically attempt to
say enough about each submenu or dialog to be of use to the reader (so they'd know which main menu item to choose); but this required in some cases much longer option descriptions which at least itemized the most important of the sub-options. So when if you
do that for 10 rows out of 12-row table, your table begins to look a little crowded; and if we retain the convention of clear/transparent cell borders and no cell padding, the result is in some case...hard to read. </p>
<p style="margin-top:0;margin-bottom:0"><br>
</p>
<p style="margin-top:0;margin-bottom:0">So what do to: As I said, one option would be to add some cell padding throughout, to force all that description text apart into discrete units which are still easily visually mapped to the options they are decribing
in the left column. Of course the more common way of solving this problem in document tables of all kinds is to simply put a thin colored or black border around each cell; we could do that, but to preserve consistently we'd need to border ALL of our tables
in that way, across the manual, and that seems like a radical step. Anyway, suggestions on this are welcome. You could just try experimentally applying some of those format changes to the first few tables of the FILE MENU chapter, and see what you thought
of the results. </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>
<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 M R <matrobnew@hotmail.com><br>
<b>Sent:</b> Friday, January 12, 2018 4:16 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">
<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">Aha, so you can (get to indiv chapter URLS) --I was always hitting 'edit this book' first from the main page, which brings up a different way to access the indiv chapters. </p>
<p style="margin-top:0; margin-bottom:0"><br>
</p>
<p style="margin-top:0; margin-bottom:0">One thing that strikes me now, especially looking at the revised "Menu Bar" chapter when it's not in edit mode, since that chapter makes especially extensive use of tables: I kept with the existing formatting convention
of having no cell padding set within any of the tables, but I'm not actually sure how readable the result is. It would be easy enough to apply some cell padding to each of the tables in that chapter, at least--maybe 3 - 5 of whatever the unit of measure is
there (pts, pixels?) for padding. In general I tried to keep with the formatting conventions I found, but these are now long, complex tables with many rows and no real spacing between them.</p>
<p style="margin-top:0; margin-bottom:0"><br>
</p>
<p style="margin-top:0; margin-bottom:0">Ahh, double-clicking, yes: when in doubt, always double-click...</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 face="Calibri, sans-serif" color="#000000" style="font-size:11pt"><b>From:</b> Discuss <discuss-bounces@lists.flossmanuals.net> on behalf of Mick Chesterman <M.Chesterman@mmu.ac.uk><br>
<b>Sent:</b> Friday, January 12, 2018 3:59 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>Ok will do , </p>
<p><br>
</p>
<p><br>
</p>
<p>You can see the direct links from here </p>
<p><br>
</p>
<p><a href="http://write.flossmanuals.net/audacity" id="LPlnk392770" previewremoved="true">http://write.flossmanuals.net/audacity</a></p>
<div id="LPBorder_GT_15157550248580.35228071512213854" style="margin-bottom:20px; overflow:auto; width:100%; text-indent:0px">
<table id="LPContainer_15157550248500.9165917331242748" cellspacing="0" style="width:90%; background-color:rgb(255,255,255); overflow:auto; padding-top:20px; padding-bottom:20px; margin-top:20px; border-top:1px dotted rgb(200,200,200); border-bottom:1px dotted rgb(200,200,200)">
<tbody>
<tr valign="top" style="border-spacing:0px">
<td id="x_ImageCell_15157550248530.8874806870615319" colspan="1" style="width:250px; display:table-cell; padding-right:20px">
<div id="LPImageContainer_15157550248530.6873425583959469" style="background-color:rgb(255,255,255); height:160px; margin:auto; display:table; width:250px">
<a id="LPImageAnchor_15157550248540.5665600123411627" href="http://write.flossmanuals.net/audacity" target="_blank" style="display:table-cell; text-align:center"><img id="LPThumbnailImageID_15157550248540.4821520114215003" width="250" height="160" style="display:inline-block; max-width:250px; max-height:250px; height:160px; width:250px; border-width:0px; vertical-align:bottom" src="http://write.flossmanuals.net/audacity/introduction/static/Audacity-audacity_cover2c-en.gif"></a></div>
</td>
<td id="x_TextCell_15157550248550.44729452881936527" colspan="2" style="vertical-align: top; padding: 0px; display: table-cell; position: relative;">
<div id="LPRemovePreviewContainer_15157550248550.4528371704090104"></div>
<div id="LPTitle_15157550248550.6930421825273592" style="top:0px; color:rgb(0,120,215); font-weight:400; font-size:21px; font-family:wf_segoe-ui_light,"Segoe UI Light","Segoe WP Light","Segoe UI","Segoe WP",Tahoma,Arial,sans-serif; line-height:21px">
<a id="LPUrlAnchor_15157550248560.35311173342725644" href="http://write.flossmanuals.net/audacity" target="_blank" style="text-decoration:none">/chapter: Introduction / Audacity - FLOSS Manuals - Booktype</a></div>
<div id="LPMetadata_15157550248560.9946512538827044" style="margin:10px 0px 16px; color:rgb(102,102,102); font-weight:400; font-family:wf_segoe-ui_normal,"Segoe UI","Segoe WP",Tahoma,Arial,sans-serif; font-size:14px; line-height:14px">
write.flossmanuals.net</div>
<div id="LPDescription_15157550248570.9045304953878952" style="display:block; color:rgb(102,102,102); font-weight:400; font-family:wf_segoe-ui_normal,"Segoe UI","Segoe WP",Tahoma,Arial,sans-serif; font-size:14px; line-height:20px; max-height:100px; overflow:hidden">
The Audacity program is an example of an 'audio editor'. Which means Audacity can record and edit audio. Typically, one uses Audacity for recording sounds, like ...</div>
</td>
</tr>
</tbody>
</table>
</div>
<br>
<p><br>
</p>
<p>for example. </p>
<p><br>
</p>
<p><a href="http://write.flossmanuals.net/audacity/ubuntu/" id="LPlnk205845" previewremoved="true">http://write.flossmanuals.net/audacity/ubuntu/</a></p>
<div id="LPBorder_GT_15157550248420.13509541427509575" style="margin-bottom:20px; overflow:auto; width:100%; text-indent:0px">
<table id="LPContainer_15157550248360.01003258596817913" cellspacing="0" style="width:90%; background-color:rgb(255,255,255); overflow:auto; padding-top:20px; padding-bottom:20px; margin-top:20px; border-top:1px dotted rgb(200,200,200); border-bottom:1px dotted rgb(200,200,200)">
<tbody>
<tr valign="top" style="border-spacing:0px">
<td id="x_TextCell_15157550248370.6632286485725805" colspan="2" style="vertical-align: top; padding: 0px; display: table-cell; position: relative;">
<div id="LPRemovePreviewContainer_15157550248380.8327782498203096"></div>
<div id="LPTitle_15157550248380.8893504329746384" style="top:0px; color:rgb(0,120,215); font-weight:400; font-size:21px; font-family:wf_segoe-ui_light,"Segoe UI Light","Segoe WP Light","Segoe UI","Segoe WP",Tahoma,Arial,sans-serif; line-height:21px">
<a id="LPUrlAnchor_15157550248390.009727244996388551" href="http://write.flossmanuals.net/audacity/ubuntu/" target="_blank" style="text-decoration:none">Installing Audacity on Ubuntu - FLOSS Manuals</a></div>
<div id="LPMetadata_15157550248390.32209596604927015" style="margin:10px 0px 16px; color:rgb(102,102,102); font-weight:400; font-family:wf_segoe-ui_normal,"Segoe UI","Segoe WP",Tahoma,Arial,sans-serif; font-size:14px; line-height:14px">
write.flossmanuals.net</div>
<div id="LPDescription_15157550248400.9655936469713211" style="display:block; color:rgb(102,102,102); font-weight:400; font-family:wf_segoe-ui_normal,"Segoe UI","Segoe WP",Tahoma,Arial,sans-serif; font-size:14px; line-height:20px; max-height:100px; overflow:hidden">
Installing Audacity on Ubuntu Software name : Audacity Homepage : http://audacity.sourceforge.net Software version used for this installation : 1.2.6</div>
</td>
</tr>
</tbody>
</table>
</div>
<br>
<p><br>
</p>
<p><br>
</p>
<p><span id="x_x_ms-rterangepaste-end">Thanks</span><br>
</p>
<div dir="ltr" style="color:rgb(33,33,33)">
<hr tabindex="-1" style="display:inline-block; width:98%">
<div id="x_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> 12 January 2018 10:55<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_x_divtagdefaultwrapper" dir="ltr" style="font-size:12pt; color:#000000; font-family:Calibri,Helvetica,sans-serif">
<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">It doesn't actually appear like the specific chapters have their own urls -- when I go to <a href="http://write.flossmanuals.net/audacity/_edit/" class="x_x_OWAAutoLink" id="LPlnk649236" previewremoved="true">http://write.flossmanuals.net/audacity/_edit/</a> and
select a chapter to edit, the url doesn't change that I can see. The Linux installation chapter is simply entitled "UBUNTU" and its in the "Installing" part of the manual. Looking over that chapter just now, I'd be very surprised if the Linux install process
hadn't been somewhat streamlined, but again we need a Linux/Ubuntu user to tell us that.</p>
<p style="margin-top:0; margin-bottom:0"><br>
</p>
<p style="margin-top:0; margin-bottom:0">I actually wanted to edit some of the other chapter TITLES a bit, but couldn't figure out a way to do that. No big deal though, as the current titles will serve. I did drag one entire chapter out of the to-be-published
structure and down to the bottom: that was "MP3 INSTALLATION ON WINDOWS" bc it's no longer necessary to install the LAME MP3 codec separately. Just one of many ways that Audacity has gotten more user-friendly over the years.</p>
<p style="margin-top:0; margin-bottom:0"><br>
</p>
<p style="margin-top:0; margin-bottom:0">So, yeah, take a look when you've got time.</p>
<p style="margin-top:0; margin-bottom:0"><br>
</p>
<p style="margin-top:0; margin-bottom:0">Thanks,</p>
<p style="margin-top:0; margin-bottom:0"><br>
</p>
<p style="margin-top:0; margin-bottom:0">Matt</p>
<br>
<br>
<br>
<div style="color:rgb(0,0,0)">
<hr tabindex="-1" style="display:inline-block; width:98%">
<div id="x_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 Mick Chesterman <M.Chesterman@mmu.ac.uk><br>
<b>Sent:</b> Friday, January 12, 2018 3:14 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>Hi Matt this is fantastic, </p>
<p><br>
</p>
<p>In terms of best practice, there isn't any official guidance to follow, It is more of an emerging sharing of practice and negociation. So as the person taking the lead on this you are free to use your best judgement. </p>
<p>I'd be happy to have a look at it though as soon as I can and share thoughts. </p>
<p><br>
</p>
<p>One thought I had is that as the official audacity manual is "<strong>Copyright:</strong> Unless otherwise noted, all pages in this Manual are available under the terms of the
<a rel="nofollow" class="x_x_x_external x_x_x_text" href="https://creativecommons.org/licenses/by/3.0/">
Creative Commons Attribution 3.0</a> license. " then you would be free to include chunks if you wanted to, just link back to the sources as you noted.
<br>
</p>
<p><br>
</p>
<p>I wonder if anyone else out there can step in to help you with the Linux based chapter?
</p>
<p>Have you got a direct link? <br>
</p>
<p><br>
</p>
<p>Thanks</p>
<p>Mick<br>
</p>
<p><br>
</p>
<p><br>
</p>
<p> <br>
</p>
<p class="x_x_x_MsoNormal"><span style="font-size:10.0pt; font-family:"Arial",sans-serif; color:#323E4F"></span><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></font><br>
</p>
<div dir="ltr" style="color:rgb(33,33,33)">
<div id="x_x_x_divRplyFwdMsg" dir="ltr"><font color="#000000" face="Calibri, sans-serif" style="font-size:11pt"><b>Sent:</b> 11 January 2018 20:17<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_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">Mick:</p>
<p style="margin-top:0; margin-bottom:0"><br>
</p>
<p style="margin-top:0; margin-bottom:0">I've completed my revisions to the Audacity manual--at least everything I could do from a Windows machine. Rosalind Lord has agreed to address the Mac-specific install chapter and Recording config instructions. There's
also a Linux/Ubuntu install chapter, which someone in that world will need to update (at least with screenshots, if all the info itself is still current). But the other 90% or so has been redone, with new screenshots throughout (Windows-based; in the old
manual they were Linux-based, but it's my rewrite so I'm the Decider in this case <span>😊). As for the writing, s</span>ince there was so much feature change and addition from 1.x to 2.2, a good deal of the text has been rewritten as well. So someone with
veteran FM eyes will want to take a look, to make sure I haven't strayed too much either stylistically or in terms of depth of coverage. </p>
<p style="margin-top:0; margin-bottom:0"><br>
</p>
<p style="margin-top:0; margin-bottom:0">I have relied heavily both on my own experimentation with Audacity 2.2, and where necessary on official Audacity documentation. In the latter case, where I've borrowed specific information I've paraphrased language wherever
possible (being an English/composition professor, I know the rules), though in some specific places clarity and precision has dictated that I follow their wording. In some cases, where a topic is dealt with much more exhaustively in their documentation than
it was in the earlier version of the Floss manual, I've linked to the relevant pages in their site (in the old manual, this was only done once in the appendix, and I don't know if you have best-practice guidance on this, but it seemed like the most useful
thing to do). </p>
<p style="margin-top:0; margin-bottom:0"><br>
</p>
<p style="margin-top:0; margin-bottom:0">Anyway, there it is. I'm happy to revise based on any feedback.</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>
<br>
<br>
<div style="color:rgb(0,0,0)">
<hr tabindex="-1" style="display:inline-block; width:98%">
<div id="x_x_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 mick@flossmanuals.net <mick@flossmanuals.net><br>
<b>Sent:</b> Wednesday, January 10, 2018 2:35 PM<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 style="background-color:#FFFFFF">
<p>This sounds great!<br>
</p>
<br>
<div class="x_x_x_x_moz-cite-prefix">On 10/01/18 12:52, M R wrote:<br>
</div>
<blockquote type="cite">
<div id="x_x_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">I agree that what's important to the end user is feature and function, not version/release number as such. Certainly incremental releases (like the difference between 2.2.1 and 2.2.2) don't typically merit an update
to the documentation. But here we're talking essentially about the delta between an initial stable release (1.1) and a release some years later (2.x); and having nearly completed the revision I can say that about 40% of the functionality is new altogether,
and much of the rest has new GUI look/feel and arrangement, and/or is found in a new place in the main menu system than in the first release. When and if the time comes, we'll see what the delta is between 2.x and 3.x; but I'm guessing a new revision of the
FM would be appropriate then too. Meanwhile users of the newly-revised book will at least know they are dealing with the Audacity feature-set as of late 2017.</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_x_x_x_divRplyFwdMsg" dir="ltr"><font color="#000000" face="Calibri, sans-serif" style="font-size:11pt"><b>From:</b> Discuss
<a class="x_x_x_x_moz-txt-link-rfc2396E" href="mailto:discuss-bounces@lists.flossmanuals.net">
<discuss-bounces@lists.flossmanuals.net></a> on behalf of Mick Chesterman <a class="x_x_x_x_moz-txt-link-rfc2396E" href="mailto:M.Chesterman@mmu.ac.uk">
<M.Chesterman@mmu.ac.uk></a><br>
<b>Sent:</b> Wednesday, January 10, 2018 2:26 AM<br>
<b>To:</b> <a class="x_x_x_x_moz-txt-link-abbreviated" href="mailto:discuss@lists.flossmanuals.net">
discuss@lists.flossmanuals.net</a><br>
<b>Subject:</b> Re: [FM Discuss] next steps on Audacity book</font>
<div> </div>
</div>
<div lang="EN-GB">
<div class="x_x_x_x_x_WordSection1">
<p class="x_x_x_x_x_MsoNormal"><span style="font-size:11.0pt; font-family:"Calibri",sans-serif; color:#1F497D">Hi there,
</span></p>
<p class="x_x_x_x_x_MsoNormal"><span style="font-size:11.0pt; font-family:"Calibri",sans-serif; color:#1F497D"> </span></p>
<p class="x_x_x_x_x_MsoNormal"><span style="font-size:11.0pt; font-family:"Calibri",sans-serif; color:#1F497D">Regarding not including version numbers.
</span></p>
<p class="x_x_x_x_x_MsoNormal"><span style="font-size:11.0pt; font-family:"Calibri",sans-serif; color:#1F497D">It’s not a strong opinion but it’s based on some software which changes version a lot but not necessarily function.
</span></p>
<p class="x_x_x_x_x_MsoNormal"><span style="font-size:11.0pt; font-family:"Calibri",sans-serif; color:#1F497D">In that case it can mean the process of patching up docs and just making small changes where there is new functionality is harder, or may appear harder
as an editor may think they need to update the whole manual which might be too big a job for them to take on, or at least to finish.
</span></p>
<p class="x_x_x_x_x_MsoNormal"><span style="font-size:11.0pt; font-family:"Calibri",sans-serif; color:#1F497D">In any case I would trust your judgement on this for the Audacity manuals.
</span><i><span style="font-size:10.0pt; font-family:"Calibri",sans-serif; color:#44546A"></span></i></p>
<p class="x_x_x_x_x_MsoNormal"><span style="font-size:11.0pt; font-family:"Calibri",sans-serif; color:#1F497D"> </span></p>
<p class="x_x_x_x_x_MsoNormal"><span style="font-size:11.0pt; font-family:"Calibri",sans-serif; color:#1F497D">Thx
</span></p>
<p class="x_x_x_x_x_MsoNormal"><span style="font-size:11.0pt; font-family:"Calibri",sans-serif; color:#1F497D">Mick</span></p>
<div style="border:none; border-left:solid blue 1.5pt; padding:0cm 0cm 0cm 4.0pt">
<div>
<div style="border:none; border-top:solid #E1E1E1
1.0pt; padding:3.0pt 0cm 0cm 0cm">
<p class="x_x_x_x_x_MsoNormal"><b><span lang="EN-US" style="font-size:11.0pt; font-family:"Calibri",sans-serif">From:</span></b><span lang="EN-US" style="font-size:11.0pt; font-family:"Calibri",sans-serif"> Discuss [<a class="x_x_x_x_moz-txt-link-freetext" href="mailto:discuss-bounces@lists.flossmanuals.net">mailto:discuss-bounces@lists.flossmanuals.net</a>]
<b>On Behalf Of </b>M R<br>
<b>Sent:</b> 08 January 2018 06:19<br>
<b>To:</b> <a class="x_x_x_x_moz-txt-link-abbreviated" href="mailto:discuss@lists.flossmanuals.net">
discuss@lists.flossmanuals.net</a><br>
<b>Subject:</b> Re: [FM Discuss] next steps on Audacity book</span></p>
</div>
</div>
<p class="x_x_x_x_x_MsoNormal"> </p>
<div id="x_x_x_x_x_divtagdefaultwrapper">
<p><span style="font-family:"Calibri",sans-serif; color:black">Mick:</span></p>
<p><span style="font-family:"Calibri",sans-serif; color:black"> </span></p>
<p><span style="font-family:"Calibri",sans-serif; color:black">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. </span></p>
<p><span style="font-family:"Calibri",sans-serif; color:black"> </span></p>
<p><span style="font-family:"Calibri",sans-serif; color:black">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?</span></p>
<p><span style="font-family:"Calibri",sans-serif; color:black"> </span></p>
<p><span style="font-family:"Calibri",sans-serif; color:black">best,</span></p>
<p><span style="font-family:"Calibri",sans-serif; color:black"> </span></p>
<p><span style="font-family:"Calibri",sans-serif; color:black">Matt</span></p>
<p><span style="font-family:"Calibri",sans-serif; color:black"> </span></p>
<p><span style="font-family:"Calibri",sans-serif; color:black"> </span></p>
<p class="x_x_x_x_x_MsoNormal" style="margin-bottom:12.0pt"><span style="font-family:"Calibri",sans-serif; color:black"> </span></p>
<div>
<div class="x_x_x_x_x_MsoNormal" align="center" style="text-align:center"><span style="font-family:"Calibri",sans-serif; color:black">
<hr align="center" width="98%" size="2">
</span></div>
<div id="x_x_x_x_x_divRplyFwdMsg">
<p class="x_x_x_x_x_MsoNormal"><b><span style="font-size:11.0pt; font-family:"Calibri",sans-serif; color:black">From:</span></b><span style="font-size:11.0pt; font-family:"Calibri",sans-serif; color:black"> Discuss <<a href="mailto:discuss-bounces@lists.flossmanuals.net">discuss-bounces@lists.flossmanuals.net</a>>
on behalf of Mick Chesterman <<a href="mailto:M.Chesterman@mmu.ac.uk">M.Chesterman@mmu.ac.uk</a>><br>
<b>Sent:</b> Sunday, January 7, 2018 1:35 AM<br>
<b>To:</b> <a href="mailto:discuss@lists.flossmanuals.net">discuss@lists.flossmanuals.net</a><br>
<b>Subject:</b> Re: [FM Discuss] next steps on Audacity book</span><span style="font-family:"Calibri",sans-serif; color:black">
</span></p>
<div>
<p class="x_x_x_x_x_MsoNormal"><span style="font-family:"Calibri",sans-serif; color:black"> </span></p>
</div>
</div>
<div>
<p class="x_x_x_x_x_xmsonormal" style="background:white"><span style="font-family:"Calibri",sans-serif; color:black">Hi Matt,
</span></p>
<p class="x_x_x_x_x_xmsonormal" style="background:white"><span style="font-family:"Calibri",sans-serif; color:black"> </span></p>
<p class="x_x_x_x_x_xmsonormal" style="background:white"><span style="font-family:"Calibri",sans-serif; color:black">That sounds good,
</span></p>
<p class="x_x_x_x_x_xmsonormal" style="background:white"><span style="font-family:"Calibri",sans-serif; color:black"> </span></p>
<p class="x_x_x_x_x_xmsonormal" style="background:white"><span style="font-family:"Calibri",sans-serif; color:black">Unfortunately as I migrated 95% of the books in from the last system, I'm down as the owner for all of those. </span></p>
<p class="x_x_x_x_x_xmsonormal" style="background:white"><span style="font-family:"Calibri",sans-serif; color:black"> </span></p>
<p class="x_x_x_x_x_xmsonormal" style="background:white"><span style="font-family:"Calibri",sans-serif; color:black">I would say that where possible it would be good to take out references to software version numbers when we come across them.
</span></p>
<p class="x_x_x_x_x_xmsonormal" style="background:white"><span style="font-family:"Calibri",sans-serif; color:black"> </span></p>
<p class="x_x_x_x_x_xmsonormal" style="background:white"><span style="font-family:"Calibri",sans-serif; color:black">Thanks</span></p>
<p class="x_x_x_x_x_xmsonormal" style="background:white"><span style="font-family:"Calibri",sans-serif; color:black">Mick</span></p>
<p class="x_x_x_x_x_xmsonormal" style="background:white"><span style="font-family:"Calibri",sans-serif; color:black"> </span></p>
<div>
<div class="x_x_x_x_x_MsoNormal" align="center" style="text-align:center; background:white">
<span style="font-family:"Calibri",sans-serif; color:#212121">
<hr align="center" width="98%" size="2">
</span></div>
<div id="x_x_x_x_x_x_divRplyFwdMsg">
<p class="x_x_x_x_x_MsoNormal" style="background:white"><b><span style="font-size:11.0pt; font-family:"Calibri",sans-serif; color:black">From:</span></b><span style="font-size:11.0pt; font-family:"Calibri",sans-serif; color:black"> Discuss <<a href="mailto:discuss-bounces@lists.flossmanuals.net">discuss-bounces@lists.flossmanuals.net</a>>
on behalf of M R <<a href="mailto:matrobnew@hotmail.com">matrobnew@hotmail.com</a>><br>
<b>Sent:</b> 06 January 2018 01:11<br>
<b>To:</b> <a href="mailto:discuss@lists.flossmanuals.net">discuss@lists.flossmanuals.net</a><br>
<b>Subject:</b> Re: [FM Discuss] next steps on Audacity book</span><span style="font-family:"Calibri",sans-serif; color:#212121">
</span></p>
<div>
<p class="x_x_x_x_x_MsoNormal" style="background:white"><span style="font-family:"Calibri",sans-serif; color:#212121"> </span></p>
</div>
</div>
<div>
<div id="x_x_x_x_x_x_divtagdefaultwrapper">
<p style="background:white"><span style="font-family:"Calibri",sans-serif; color:black">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. </span></p>
<p style="background:white"><span style="font-family:"Calibri",sans-serif; color:black"> </span></p>
<p style="background:white"><span style="font-family:"Calibri",sans-serif; color:black">Matt </span></p>
<p class="x_x_x_x_x_MsoNormal" style="margin-bottom:12.0pt; background:white"><span style="font-family:"Calibri",sans-serif; color:black"> </span></p>
<div>
<div class="x_x_x_x_x_MsoNormal" align="center" style="text-align:center; background:white">
<span style="font-family:"Calibri",sans-serif; color:black">
<hr align="center" width="98%" size="2">
</span></div>
<div id="x_x_x_x_x_x_divRplyFwdMsg">
<p class="x_x_x_x_x_MsoNormal" style="background:white"><b><span style="font-size:11.0pt; font-family:"Calibri",sans-serif; color:black">From:</span></b><span style="font-size:11.0pt; font-family:"Calibri",sans-serif; color:black"> Discuss <<a href="mailto:discuss-bounces@lists.flossmanuals.net">discuss-bounces@lists.flossmanuals.net</a>>
on behalf of M R <<a href="mailto:matrobnew@hotmail.com">matrobnew@hotmail.com</a>><br>
<b>Sent:</b> Friday, January 5, 2018 6:09 PM<br>
<b>To:</b> <a href="mailto:discuss@lists.flossmanuals.net">discuss@lists.flossmanuals.net</a><br>
<b>Subject:</b> [FM Discuss] next steps on Audacity book</span><span style="font-family:"Calibri",sans-serif; color:black">
</span></p>
<div>
<p class="x_x_x_x_x_MsoNormal" style="background:white"><span style="font-family:"Calibri",sans-serif; color:black"> </span></p>
</div>
</div>
<div>
<div id="x_x_x_x_x_x_x_divtagdefaultwrapper">
<p style="background:white"><span style="font-family:"Calibri",sans-serif; color:black">Hi Mick:</span></p>
<p style="background:white"><span style="font-family:"Calibri",sans-serif; color:black"> </span></p>
<p style="background:white"><span style="font-family:"Calibri",sans-serif; color:black">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 style="">😊</span><span style="font-family:"Calibri",sans-serif; color:black"> Just addressing the delta from 1.x. What do you think?</span></p>
<p style="background:white"><span style="font-family:"Calibri",sans-serif; color:black"> </span></p>
<p style="background:white"><span style="font-family:"Calibri",sans-serif; color:black">Matt</span></p>
</div>
</div>
</div>
</div>
</div>
</div>
<p class="x_x_x_x_x_MsoNormal" style="background:white"><span style="font-family:"Calibri",sans-serif; color:black">"Before acting on this email or opening any attachments you should read the Manchester Metropolitan University email disclaimer available on
its website <a href="http://www.mmu.ac.uk/emaildisclaimer">http://www.mmu.ac.uk/emaildisclaimer</a> "
</span></p>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
<br>
<fieldset class="x_x_x_x_mimeAttachmentHeader"></fieldset> <br>
<pre>_______________________________________________
Discuss mailing list
<a class="x_x_x_x_moz-txt-link-abbreviated" href="mailto:Discuss@lists.flossmanuals.net">Discuss@lists.flossmanuals.net</a>
<a class="x_x_x_x_moz-txt-link-freetext" href="http://lists.flossmanuals.net/listinfo.cgi/discuss-flossmanuals.net">http://lists.flossmanuals.net/listinfo.cgi/discuss-flossmanuals.net</a> - you can unsubscribe here
</pre>
</blockquote>
<br>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
</body>
</html>