X-Git-Url: http://shamusworld.gotdns.org/cgi-bin/gitweb.cgi?a=blobdiff_plain;f=_manual%2F07_working-with-sessions%2F04_backup-and-sharing-of-sessions.html;h=ea32fb0968b7e5705b6714edb56af6027f04ca7f;hb=5432a9fe7de29efd25d570bccb662ea3c2b4783c;hp=fba216facdee22a8fd741be4a655df2bffd6c552;hpb=5c3c3ba54db3a08a826c75831bec9c455280f038;p=ardour-manual

diff --git a/_manual/07_working-with-sessions/04_backup-and-sharing-of-sessions.html b/_manual/07_working-with-sessions/04_backup-and-sharing-of-sessions.html
index fba216f..ea32fb0 100644
--- a/_manual/07_working-with-sessions/04_backup-and-sharing-of-sessions.html
+++ b/_manual/07_working-with-sessions/04_backup-and-sharing-of-sessions.html
@@ -3,12 +3,25 @@ layout: default
 title: Backup and Sharing of Sessions
 ---                        
 
-
-  
-  
-<p>An Ardour session is stored in a single folder on your computer's filesystem. This makes backup very easy - any tool capable of backing up a folder (i.e. all of them) can be used to backup a session. You pick the location of a session when it is created - by default it will be in your default session location, which can be altered via <code>Edit &gt; Preferences &gt; Misc &gt; Session Management</code>. </p>
-<blockquote><p>
-There is complication: a session may reference embedded media that are stored outside of the session folder. At this time (December 2012), there is no particularly good solution for this. Backing up a session with embedded files will not create a copy of the session containing those files.
-</p></blockquote>
-<p>The single folder approach also makes sharing a project easy. Simply copy the session folder (onto a storage device, or across a network) and another Ardour user (on any platform) will be able to use it. The limitation regarding embedded files applies to session sharing as well.</p>
+<p>
+  An Ardour session is stored in a single folder on your computer's filesystem. 
+  This makes <dfn>backup</dfn> very easy &mdash; any tool capable of backing up 
+  a folder can be used to backup a session. You pick the location of a session 
+  when it is created &mdash; by default it will be in your default session location, 
+  which can be altered via <kbd class="menu">Edit &gt; Preferences &gt; Misc &gt; Session
+  Management</kbd>. 
+</p>
+<p class="warning">
+  There is one complication: a session may reference media files that are stored 
+  outside of the session folder, if the user has opted not to select <kbd
+  class="optoff">Session &gt; Import &gt; Copy to Session</kbd> during
+  import. Backing up a session with embedded files will not create a 
+  copy of the session containing those files.
+</p>
+<p>
+  The single folder approach also makes sharing a project easy. Simply copy the session 
+  folder (onto a storage device, or across a network) and another Ardour user (on any 
+  platform) will be able to use it. The limitation regarding embedded files applies to 
+  session sharing as well.
+</p>