documentation/mobile-manual: create a merged v3 manual

Unintentionally two versions of the mobile manual were created. This brings all of Willem's changes into the version for Subsurface-mobile v3, and restores the last version of the v2 mobile manual. This commit was manually created from a pull request that was signed off by Willem, given that he wrote most of the text I am copying that SOB into this commit and will assign authorship to him. To avoid further confusion, we now have a v2 and a v3 manual, explicitly named. The corresponding .html.git files were also updated (reflecting our switch to asciidoctor). Signed-off-by: willemferguson <willemferguson@zoology.up.ac.za> Signed-off-by: Dirk Hohndel <dirk@hohndel.org>
author: Willem Ferguson <willemferguson@zoology.up.ac.za> 2020-05-05 17:46:48 -0700
committer: Dirk Hohndel <dirk@hohndel.org> 2020-05-05 17:55:02 -0700
commit: 70ebc2bee7bc01e0758b7608cfbbe2e8a945c062 (patch)
tree: 97262be1334832c8b8cdc6d494f43ad36e783196 /Documentation
parent: 33b4ecf0555371e0c325ff05707d70ac9e69c8db (diff)
download: subsurface-70ebc2bee7bc01e0758b7608cfbbe2e8a945c062.tar.gz
6 files changed, 2825 insertions, 2162 deletions
diff --git a/Documentation/Makefile b/Documentation/Makefile
index 55671b09a..1df632af6 100644
--- a/Documentation/Makefile
+++ b/Documentation/Makefile
@@ -13,7 +13,7 @@ HTMLDOCS = $(patsubst %,$(OUT)%.html,$(DOCNAMES))
 TEXTDOCS = $(patsubst %,$(OUT)%.text,$(DOCNAMES))
 PDFDOCS = $(patsubst %,$(OUT)%.pdf,$(DOCNAMES))
 
-ASCIIDOC = asciidoc
+ASCIIDOC = asciidoctor
 A2X = a2x
 BROWSER = firefox
 THEME = compact_subsurface
diff --git a/Documentation/mobile-manual-v2.html.git b/Documentation/mobile-manual-v2.html.git
new file mode 100644
index 000000000..12e12d942
--- /dev/null
+++ b/Documentation/mobile-manual-v2.html.git
@@ -0,0 +1,1302 @@
+<!DOCTYPE html>
+<html lang="en">
+<head>
+<meta charset="UTF-8">
+<meta http-equiv="X-UA-Compatible" content="IE=edge">
+<meta name="viewport" content="width=device-width, initial-scale=1.0">
+<meta name="generator" content="Asciidoctor 2.0.10">
+<title>Introducing Subsurface-mobile</title>
+<link rel="stylesheet" href="https://fonts.googleapis.com/css?family=Open+Sans:300,300italic,400,400italic,600,600italic%7CNoto+Serif:400,400italic,700,700italic%7CDroid+Sans+Mono:400,700">
+<style>
+/* Asciidoctor default stylesheet | MIT License | https://asciidoctor.org */
+/* Uncomment @import statement to use as custom stylesheet */
+/*@import "https://fonts.googleapis.com/css?family=Open+Sans:300,300italic,400,400italic,600,600italic%7CNoto+Serif:400,400italic,700,700italic%7CDroid+Sans+Mono:400,700";*/
+article,aside,details,figcaption,figure,footer,header,hgroup,main,nav,section{display:block}
+audio,video{display:inline-block}
+audio:not([controls]){display:none;height:0}
+html{font-family:sans-serif;-ms-text-size-adjust:100%;-webkit-text-size-adjust:100%}
+a{background:none}
+a:focus{outline:thin dotted}
+a:active,a:hover{outline:0}
+h1{font-size:2em;margin:.67em 0}
+abbr[title]{border-bottom:1px dotted}
+b,strong{font-weight:bold}
+dfn{font-style:italic}
+hr{-moz-box-sizing:content-box;box-sizing:content-box;height:0}
+mark{background:#ff0;color:#000}
+code,kbd,pre,samp{font-family:monospace;font-size:1em}
+pre{white-space:pre-wrap}
+q{quotes:"\201C" "\201D" "\2018" "\2019"}
+small{font-size:80%}
+sub,sup{font-size:75%;line-height:0;position:relative;vertical-align:baseline}
+sup{top:-.5em}
+sub{bottom:-.25em}
+img{border:0}
+svg:not(:root){overflow:hidden}
+figure{margin:0}
+fieldset{border:1px solid silver;margin:0 2px;padding:.35em .625em .75em}
+legend{border:0;padding:0}
+button,input,select,textarea{font-family:inherit;font-size:100%;margin:0}
+button,input{line-height:normal}
+button,select{text-transform:none}
+button,html input[type="button"],input[type="reset"],input[type="submit"]{-webkit-appearance:button;cursor:pointer}
+button[disabled],html input[disabled]{cursor:default}
+input[type="checkbox"],input[type="radio"]{box-sizing:border-box;padding:0}
+button::-moz-focus-inner,input::-moz-focus-inner{border:0;padding:0}
+textarea{overflow:auto;vertical-align:top}
+table{border-collapse:collapse;border-spacing:0}
+*,*::before,*::after{-moz-box-sizing:border-box;-webkit-box-sizing:border-box;box-sizing:border-box}
+html,body{font-size:100%}
+body{background:#fff;color:rgba(0,0,0,.8);padding:0;margin:0;font-family:"Noto Serif","DejaVu Serif",serif;font-weight:400;font-style:normal;line-height:1;position:relative;cursor:auto;tab-size:4;-moz-osx-font-smoothing:grayscale;-webkit-font-smoothing:antialiased}
+a:hover{cursor:pointer}
+img,object,embed{max-width:100%;height:auto}
+object,embed{height:100%}
+img{-ms-interpolation-mode:bicubic}
+.left{float:left!important}
+.right{float:right!important}
+.text-left{text-align:left!important}
+.text-right{text-align:right!important}
+.text-center{text-align:center!important}
+.text-justify{text-align:justify!important}
+.hide{display:none}
+img,object,svg{display:inline-block;vertical-align:middle}
+textarea{height:auto;min-height:50px}
+select{width:100%}
+.center{margin-left:auto;margin-right:auto}
+.stretch{width:100%}
+.subheader,.admonitionblock td.content>.title,.audioblock>.title,.exampleblock>.title,.imageblock>.title,.listingblock>.title,.literalblock>.title,.stemblock>.title,.openblock>.title,.paragraph>.title,.quoteblock>.title,table.tableblock>.title,.verseblock>.title,.videoblock>.title,.dlist>.title,.olist>.title,.ulist>.title,.qlist>.title,.hdlist>.title{line-height:1.45;color:#7a2518;font-weight:400;margin-top:0;margin-bottom:.25em}
+div,dl,dt,dd,ul,ol,li,h1,h2,h3,#toctitle,.sidebarblock>.content>.title,h4,h5,h6,pre,form,p,blockquote,th,td{margin:0;padding:0;direction:ltr}
+a{color:#2156a5;text-decoration:underline;line-height:inherit}
+a:hover,a:focus{color:#1d4b8f}
+a img{border:0}
+p{font-family:inherit;font-weight:400;font-size:1em;line-height:1.6;margin-bottom:1.25em;text-rendering:optimizeLegibility}
+p aside{font-size:.875em;line-height:1.35;font-style:italic}
+h1,h2,h3,#toctitle,.sidebarblock>.content>.title,h4,h5,h6{font-family:"Open Sans","DejaVu Sans",sans-serif;font-weight:300;font-style:normal;color:#ba3925;text-rendering:optimizeLegibility;margin-top:1em;margin-bottom:.5em;line-height:1.0125em}
+h1 small,h2 small,h3 small,#toctitle small,.sidebarblock>.content>.title small,h4 small,h5 small,h6 small{font-size:60%;color:#e99b8f;line-height:0}
+h1{font-size:2.125em}
+h2{font-size:1.6875em}
+h3,#toctitle,.sidebarblock>.content>.title{font-size:1.375em}
+h4,h5{font-size:1.125em}
+h6{font-size:1em}
+hr{border:solid #dddddf;border-width:1px 0 0;clear:both;margin:1.25em 0 1.1875em;height:0}
+em,i{font-style:italic;line-height:inherit}
+strong,b{font-weight:bold;line-height:inherit}
+small{font-size:60%;line-height:inherit}
+code{font-family:"Droid Sans Mono","DejaVu Sans Mono",monospace;font-weight:400;color:rgba(0,0,0,.9)}
+ul,ol,dl{font-size:1em;line-height:1.6;margin-bottom:1.25em;list-style-position:outside;font-family:inherit}
+ul,ol{margin-left:1.5em}
+ul li ul,ul li ol{margin-left:1.25em;margin-bottom:0;font-size:1em}
+ul.square li ul,ul.circle li ul,ul.disc li ul{list-style:inherit}
+ul.square{list-style-type:square}
+ul.circle{list-style-type:circle}
+ul.disc{list-style-type:disc}
+ol li ul,ol li ol{margin-left:1.25em;margin-bottom:0}
+dl dt{margin-bottom:.3125em;font-weight:bold}
+dl dd{margin-bottom:1.25em}
+abbr,acronym{text-transform:uppercase;font-size:90%;color:rgba(0,0,0,.8);border-bottom:1px dotted #ddd;cursor:help}
+abbr{text-transform:none}
+blockquote{margin:0 0 1.25em;padding:.5625em 1.25em 0 1.1875em;border-left:1px solid #ddd}
+blockquote cite{display:block;font-size:.9375em;color:rgba(0,0,0,.6)}
+blockquote cite::before{content:"\2014 \0020"}
+blockquote cite a,blockquote cite a:visited{color:rgba(0,0,0,.6)}
+blockquote,blockquote p{line-height:1.6;color:rgba(0,0,0,.85)}
+@media screen and (min-width:768px){h1,h2,h3,#toctitle,.sidebarblock>.content>.title,h4,h5,h6{line-height:1.2}
+h1{font-size:2.75em}
+h2{font-size:2.3125em}
+h3,#toctitle,.sidebarblock>.content>.title{font-size:1.6875em}
+h4{font-size:1.4375em}}
+table{background:#fff;margin-bottom:1.25em;border:solid 1px #dedede}
+table thead,table tfoot{background:#f7f8f7}
+table thead tr th,table thead tr td,table tfoot tr th,table tfoot tr td{padding:.5em .625em .625em;font-size:inherit;color:rgba(0,0,0,.8);text-align:left}
+table tr th,table tr td{padding:.5625em .625em;font-size:inherit;color:rgba(0,0,0,.8)}
+table tr.even,table tr.alt{background:#f8f8f7}
+table thead tr th,table tfoot tr th,table tbody tr td,table tr td,table tfoot tr td{display:table-cell;line-height:1.6}
+h1,h2,h3,#toctitle,.sidebarblock>.content>.title,h4,h5,h6{line-height:1.2;word-spacing:-.05em}
+h1 strong,h2 strong,h3 strong,#toctitle strong,.sidebarblock>.content>.title strong,h4 strong,h5 strong,h6 strong{font-weight:400}
+.clearfix::before,.clearfix::after,.float-group::before,.float-group::after{content:" ";display:table}
+.clearfix::after,.float-group::after{clear:both}
+:not(pre):not([class^=L])>code{font-size:.9375em;font-style:normal!important;letter-spacing:0;padding:.1em .5ex;word-spacing:-.15em;background:#f7f7f8;-webkit-border-radius:4px;border-radius:4px;line-height:1.45;text-rendering:optimizeSpeed;word-wrap:break-word}
+:not(pre)>code.nobreak{word-wrap:normal}
+:not(pre)>code.nowrap{white-space:nowrap}
+pre{color:rgba(0,0,0,.9);font-family:"Droid Sans Mono","DejaVu Sans Mono",monospace;line-height:1.45;text-rendering:optimizeSpeed}
+pre code,pre pre{color:inherit;font-size:inherit;line-height:inherit}
+pre>code{display:block}
+pre.nowrap,pre.nowrap pre{white-space:pre;word-wrap:normal}
+em em{font-style:normal}
+strong strong{font-weight:400}
+.keyseq{color:rgba(51,51,51,.8)}
+kbd{font-family:"Droid Sans Mono","DejaVu Sans Mono",monospace;display:inline-block;color:rgba(0,0,0,.8);font-size:.65em;line-height:1.45;background:#f7f7f7;border:1px solid #ccc;-webkit-border-radius:3px;border-radius:3px;-webkit-box-shadow:0 1px 0 rgba(0,0,0,.2),0 0 0 .1em white inset;box-shadow:0 1px 0 rgba(0,0,0,.2),0 0 0 .1em #fff inset;margin:0 .15em;padding:.2em .5em;vertical-align:middle;position:relative;top:-.1em;white-space:nowrap}
+.keyseq kbd:first-child{margin-left:0}
+.keyseq kbd:last-child{margin-right:0}
+.menuseq,.menuref{color:#000}
+.menuseq b:not(.caret),.menuref{font-weight:inherit}
+.menuseq{word-spacing:-.02em}
+.menuseq b.caret{font-size:1.25em;line-height:.8}
+.menuseq i.caret{font-weight:bold;text-align:center;width:.45em}
+b.button::before,b.button::after{position:relative;top:-1px;font-weight:400}
+b.button::before{content:"[";padding:0 3px 0 2px}
+b.button::after{content:"]";padding:0 2px 0 3px}
+p a>code:hover{color:rgba(0,0,0,.9)}
+#header,#content,#footnotes,#footer{width:100%;margin-left:auto;margin-right:auto;margin-top:0;margin-bottom:0;max-width:62.5em;*zoom:1;position:relative;padding-left:.9375em;padding-right:.9375em}
+#header::before,#header::after,#content::before,#content::after,#footnotes::before,#footnotes::after,#footer::before,#footer::after{content:" ";display:table}
+#header::after,#content::after,#footnotes::after,#footer::after{clear:both}
+#content{margin-top:1.25em}
+#content::before{content:none}
+#header>h1:first-child{color:rgba(0,0,0,.85);margin-top:2.25rem;margin-bottom:0}
+#header>h1:first-child+#toc{margin-top:8px;border-top:1px solid #dddddf}
+#header>h1:only-child,body.toc2 #header>h1:nth-last-child(2){border-bottom:1px solid #dddddf;padding-bottom:8px}
+#header .details{border-bottom:1px solid #dddddf;line-height:1.45;padding-top:.25em;padding-bottom:.25em;padding-left:.25em;color:rgba(0,0,0,.6);display:-ms-flexbox;display:-webkit-flex;display:flex;-ms-flex-flow:row wrap;-webkit-flex-flow:row wrap;flex-flow:row wrap}
+#header .details span:first-child{margin-left:-.125em}
+#header .details span.email a{color:rgba(0,0,0,.85)}
+#header .details br{display:none}
+#header .details br+span::before{content:"\00a0\2013\00a0"}
+#header .details br+span.author::before{content:"\00a0\22c5\00a0";color:rgba(0,0,0,.85)}
+#header .details br+span#revremark::before{content:"\00a0|\00a0"}
+#header #revnumber{text-transform:capitalize}
+#header #revnumber::after{content:"\00a0"}
+#content>h1:first-child:not([class]){color:rgba(0,0,0,.85);border-bottom:1px solid #dddddf;padding-bottom:8px;margin-top:0;padding-top:1rem;margin-bottom:1.25rem}
+#toc{border-bottom:1px solid #e7e7e9;padding-bottom:.5em}
+#toc>ul{margin-left:.125em}
+#toc ul.sectlevel0>li>a{font-style:italic}
+#toc ul.sectlevel0 ul.sectlevel1{margin:.5em 0}
+#toc ul{font-family:"Open Sans","DejaVu Sans",sans-serif;list-style-type:none}
+#toc li{line-height:1.3334;margin-top:.3334em}
+#toc a{text-decoration:none}
+#toc a:active{text-decoration:underline}
+#toctitle{color:#7a2518;font-size:1.2em}
+@media screen and (min-width:768px){#toctitle{font-size:1.375em}
+body.toc2{padding-left:15em;padding-right:0}
+#toc.toc2{margin-top:0!important;background:#f8f8f7;position:fixed;width:15em;left:0;top:0;border-right:1px solid #e7e7e9;border-top-width:0!important;border-bottom-width:0!important;z-index:1000;padding:1.25em 1em;height:100%;overflow:auto}
+#toc.toc2 #toctitle{margin-top:0;margin-bottom:.8rem;font-size:1.2em}
+#toc.toc2>ul{font-size:.9em;margin-bottom:0}
+#toc.toc2 ul ul{margin-left:0;padding-left:1em}
+#toc.toc2 ul.sectlevel0 ul.sectlevel1{padding-left:0;margin-top:.5em;margin-bottom:.5em}
+body.toc2.toc-right{padding-left:0;padding-right:15em}
+body.toc2.toc-right #toc.toc2{border-right-width:0;border-left:1px solid #e7e7e9;left:auto;right:0}}
+@media screen and (min-width:1280px){body.toc2{padding-left:20em;padding-right:0}
+#toc.toc2{width:20em}
+#toc.toc2 #toctitle{font-size:1.375em}
+#toc.toc2>ul{font-size:.95em}
+#toc.toc2 ul ul{padding-left:1.25em}
+body.toc2.toc-right{padding-left:0;padding-right:20em}}
+#content #toc{border-style:solid;border-width:1px;border-color:#e0e0dc;margin-bottom:1.25em;padding:1.25em;background:#f8f8f7;-webkit-border-radius:4px;border-radius:4px}
+#content #toc>:first-child{margin-top:0}
+#content #toc>:last-child{margin-bottom:0}
+#footer{max-width:100%;background:rgba(0,0,0,.8);padding:1.25em}
+#footer-text{color:rgba(255,255,255,.8);line-height:1.44}
+#content{margin-bottom:.625em}
+.sect1{padding-bottom:.625em}
+@media screen and (min-width:768px){#content{margin-bottom:1.25em}
+.sect1{padding-bottom:1.25em}}
+.sect1:last-child{padding-bottom:0}
+.sect1+.sect1{border-top:1px solid #e7e7e9}
+#content h1>a.anchor,h2>a.anchor,h3>a.anchor,#toctitle>a.anchor,.sidebarblock>.content>.title>a.anchor,h4>a.anchor,h5>a.anchor,h6>a.anchor{position:absolute;z-index:1001;width:1.5ex;margin-left:-1.5ex;display:block;text-decoration:none!important;visibility:hidden;text-align:center;font-weight:400}
+#content h1>a.anchor::before,h2>a.anchor::before,h3>a.anchor::before,#toctitle>a.anchor::before,.sidebarblock>.content>.title>a.anchor::before,h4>a.anchor::before,h5>a.anchor::before,h6>a.anchor::before{content:"\00A7";font-size:.85em;display:block;padding-top:.1em}
+#content h1:hover>a.anchor,#content h1>a.anchor:hover,h2:hover>a.anchor,h2>a.anchor:hover,h3:hover>a.anchor,#toctitle:hover>a.anchor,.sidebarblock>.content>.title:hover>a.anchor,h3>a.anchor:hover,#toctitle>a.anchor:hover,.sidebarblock>.content>.title>a.anchor:hover,h4:hover>a.anchor,h4>a.anchor:hover,h5:hover>a.anchor,h5>a.anchor:hover,h6:hover>a.anchor,h6>a.anchor:hover{visibility:visible}
+#content h1>a.link,h2>a.link,h3>a.link,#toctitle>a.link,.sidebarblock>.content>.title>a.link,h4>a.link,h5>a.link,h6>a.link{color:#ba3925;text-decoration:none}
+#content h1>a.link:hover,h2>a.link:hover,h3>a.link:hover,#toctitle>a.link:hover,.sidebarblock>.content>.title>a.link:hover,h4>a.link:hover,h5>a.link:hover,h6>a.link:hover{color:#a53221}
+details,.audioblock,.imageblock,.literalblock,.listingblock,.stemblock,.videoblock{margin-bottom:1.25em}
+details>summary:first-of-type{cursor:pointer;display:list-item;outline:none;margin-bottom:.75em}
+.admonitionblock td.content>.title,.audioblock>.title,.exampleblock>.title,.imageblock>.title,.listingblock>.title,.literalblock>.title,.stemblock>.title,.openblock>.title,.paragraph>.title,.quoteblock>.title,table.tableblock>.title,.verseblock>.title,.videoblock>.title,.dlist>.title,.olist>.title,.ulist>.title,.qlist>.title,.hdlist>.title{text-rendering:optimizeLegibility;text-align:left;font-family:"Noto Serif","DejaVu Serif",serif;font-size:1rem;font-style:italic}
+table.tableblock.fit-content>caption.title{white-space:nowrap;width:0}
+.paragraph.lead>p,#preamble>.sectionbody>[class="paragraph"]:first-of-type p{font-size:1.21875em;line-height:1.6;color:rgba(0,0,0,.85)}
+table.tableblock #preamble>.sectionbody>[class="paragraph"]:first-of-type p{font-size:inherit}
+.admonitionblock>table{border-collapse:separate;border:0;background:none;width:100%}
+.admonitionblock>table td.icon{text-align:center;width:80px}
+.admonitionblock>table td.icon img{max-width:none}
+.admonitionblock>table td.icon .title{font-weight:bold;font-family:"Open Sans","DejaVu Sans",sans-serif;text-transform:uppercase}
+.admonitionblock>table td.content{padding-left:1.125em;padding-right:1.25em;border-left:1px solid #dddddf;color:rgba(0,0,0,.6)}
+.admonitionblock>table td.content>:last-child>:last-child{margin-bottom:0}
+.exampleblock>.content{border-style:solid;border-width:1px;border-color:#e6e6e6;margin-bottom:1.25em;padding:1.25em;background:#fff;-webkit-border-radius:4px;border-radius:4px}
+.exampleblock>.content>:first-child{margin-top:0}
+.exampleblock>.content>:last-child{margin-bottom:0}
+.sidebarblock{border-style:solid;border-width:1px;border-color:#dbdbd6;margin-bottom:1.25em;padding:1.25em;background:#f3f3f2;-webkit-border-radius:4px;border-radius:4px}
+.sidebarblock>:first-child{margin-top:0}
+.sidebarblock>:last-child{margin-bottom:0}
+.sidebarblock>.content>.title{color:#7a2518;margin-top:0;text-align:center}
+.exampleblock>.content>:last-child>:last-child,.exampleblock>.content .olist>ol>li:last-child>:last-child,.exampleblock>.content .ulist>ul>li:last-child>:last-child,.exampleblock>.content .qlist>ol>li:last-child>:last-child,.sidebarblock>.content>:last-child>:last-child,.sidebarblock>.content .olist>ol>li:last-child>:last-child,.sidebarblock>.content .ulist>ul>li:last-child>:last-child,.sidebarblock>.content .qlist>ol>li:last-child>:last-child{margin-bottom:0}
+.literalblock pre,.listingblock>.content>pre{-webkit-border-radius:4px;border-radius:4px;word-wrap:break-word;overflow-x:auto;padding:1em;font-size:.8125em}
+@media screen and (min-width:768px){.literalblock pre,.listingblock>.content>pre{font-size:.90625em}}
+@media screen and (min-width:1280px){.literalblock pre,.listingblock>.content>pre{font-size:1em}}
+.literalblock pre,.listingblock>.content>pre:not(.highlight),.listingblock>.content>pre[class="highlight"],.listingblock>.content>pre[class^="highlight "]{background:#f7f7f8}
+.literalblock.output pre{color:#f7f7f8;background:rgba(0,0,0,.9)}
+.listingblock>.content{position:relative}
+.listingblock code[data-lang]::before{display:none;content:attr(data-lang);position:absolute;font-size:.75em;top:.425rem;right:.5rem;line-height:1;text-transform:uppercase;color:inherit;opacity:.5}
+.listingblock:hover code[data-lang]::before{display:block}
+.listingblock.terminal pre .command::before{content:attr(data-prompt);padding-right:.5em;color:inherit;opacity:.5}
+.listingblock.terminal pre .command:not([data-prompt])::before{content:"$"}
+.listingblock pre.highlightjs{padding:0}
+.listingblock pre.highlightjs>code{padding:1em;-webkit-border-radius:4px;border-radius:4px}
+.listingblock pre.prettyprint{border-width:0}
+.prettyprint{background:#f7f7f8}
+pre.prettyprint .linenums{line-height:1.45;margin-left:2em}
+pre.prettyprint li{background:none;list-style-type:inherit;padding-left:0}
+pre.prettyprint li code[data-lang]::before{opacity:1}
+pre.prettyprint li:not(:first-child) code[data-lang]::before{display:none}
+table.linenotable{border-collapse:separate;border:0;margin-bottom:0;background:none}
+table.linenotable td[class]{color:inherit;vertical-align:top;padding:0;line-height:inherit;white-space:normal}
+table.linenotable td.code{padding-left:.75em}
+table.linenotable td.linenos{border-right:1px solid currentColor;opacity:.35;padding-right:.5em}
+pre.pygments .lineno{border-right:1px solid currentColor;opacity:.35;display:inline-block;margin-right:.75em}
+pre.pygments .lineno::before{content:"";margin-right:-.125em}
+.quoteblock{margin:0 1em 1.25em 1.5em;display:table}
+.quoteblock:not(.excerpt)>.title{margin-left:-1.5em;margin-bottom:.75em}
+.quoteblock blockquote,.quoteblock p{color:rgba(0,0,0,.85);font-size:1.15rem;line-height:1.75;word-spacing:.1em;letter-spacing:0;font-style:italic;text-align:justify}
+.quoteblock blockquote{margin:0;padding:0;border:0}
+.quoteblock blockquote::before{content:"\201c";float:left;font-size:2.75em;font-weight:bold;line-height:.6em;margin-left:-.6em;color:#7a2518;text-shadow:0 1px 2px rgba(0,0,0,.1)}
+.quoteblock blockquote>.paragraph:last-child p{margin-bottom:0}
+.quoteblock .attribution{margin-top:.75em;margin-right:.5ex;text-align:right}
+.verseblock{margin:0 1em 1.25em}
+.verseblock pre{font-family:"Open Sans","DejaVu Sans",sans;font-size:1.15rem;color:rgba(0,0,0,.85);font-weight:300;text-rendering:optimizeLegibility}
+.verseblock pre strong{font-weight:400}
+.verseblock .attribution{margin-top:1.25rem;margin-left:.5ex}
+.quoteblock .attribution,.verseblock .attribution{font-size:.9375em;line-height:1.45;font-style:italic}
+.quoteblock .attribution br,.verseblock .attribution br{display:none}
+.quoteblock .attribution cite,.verseblock .attribution cite{display:block;letter-spacing:-.025em;color:rgba(0,0,0,.6)}
+.quoteblock.abstract blockquote::before,.quoteblock.excerpt blockquote::before,.quoteblock .quoteblock blockquote::before{display:none}
+.quoteblock.abstract blockquote,.quoteblock.abstract p,.quoteblock.excerpt blockquote,.quoteblock.excerpt p,.quoteblock .quoteblock blockquote,.quoteblock .quoteblock p{line-height:1.6;word-spacing:0}
+.quoteblock.abstract{margin:0 1em 1.25em;display:block}
+.quoteblock.abstract>.title{margin:0 0 .375em;font-size:1.15em;text-align:center}
+.quoteblock.excerpt>blockquote,.quoteblock .quoteblock{padding:0 0 .25em 1em;border-left:.25em solid #dddddf}
+.quoteblock.excerpt,.quoteblock .quoteblock{margin-left:0}
+.quoteblock.excerpt blockquote,.quoteblock.excerpt p,.quoteblock .quoteblock blockquote,.quoteblock .quoteblock p{color:inherit;font-size:1.0625rem}
+.quoteblock.excerpt .attribution,.quoteblock .quoteblock .attribution{color:inherit;text-align:left;margin-right:0}
+table.tableblock{max-width:100%;border-collapse:separate}
+p.tableblock:last-child{margin-bottom:0}
+td.tableblock>.content>:last-child{margin-bottom:-1.25em}
+td.tableblock>.content>:last-child.sidebarblock{margin-bottom:0}
+table.tableblock,th.tableblock,td.tableblock{border:0 solid #dedede}
+table.grid-all>thead>tr>.tableblock,table.grid-all>tbody>tr>.tableblock{border-width:0 1px 1px 0}
+table.grid-all>tfoot>tr>.tableblock{border-width:1px 1px 0 0}
+table.grid-cols>*>tr>.tableblock{border-width:0 1px 0 0}
+table.grid-rows>thead>tr>.tableblock,table.grid-rows>tbody>tr>.tableblock{border-width:0 0 1px}
+table.grid-rows>tfoot>tr>.tableblock{border-width:1px 0 0}
+table.grid-all>*>tr>.tableblock:last-child,table.grid-cols>*>tr>.tableblock:last-child{border-right-width:0}
+table.grid-all>tbody>tr:last-child>.tableblock,table.grid-all>thead:last-child>tr>.tableblock,table.grid-rows>tbody>tr:last-child>.tableblock,table.grid-rows>thead:last-child>tr>.tableblock{border-bottom-width:0}
+table.frame-all{border-width:1px}
+table.frame-sides{border-width:0 1px}
+table.frame-topbot,table.frame-ends{border-width:1px 0}
+table.stripes-all tr,table.stripes-odd tr:nth-of-type(odd),table.stripes-even tr:nth-of-type(even),table.stripes-hover tr:hover{background:#f8f8f7}
+th.halign-left,td.halign-left{text-align:left}
+th.halign-right,td.halign-right{text-align:right}
+th.halign-center,td.halign-center{text-align:center}
+th.valign-top,td.valign-top{vertical-align:top}
+th.valign-bottom,td.valign-bottom{vertical-align:bottom}
+th.valign-middle,td.valign-middle{vertical-align:middle}
+table thead th,table tfoot th{font-weight:bold}
+tbody tr th{display:table-cell;line-height:1.6;background:#f7f8f7}
+tbody tr th,tbody tr th p,tfoot tr th,tfoot tr th p{color:rgba(0,0,0,.8);font-weight:bold}
+p.tableblock>code:only-child{background:none;padding:0}
+p.tableblock{font-size:1em}
+ol{margin-left:1.75em}
+ul li ol{margin-left:1.5em}
+dl dd{margin-left:1.125em}
+dl dd:last-child,dl dd:last-child>:last-child{margin-bottom:0}
+ol>li p,ul>li p,ul dd,ol dd,.olist .olist,.ulist .ulist,.ulist .olist,.olist .ulist{margin-bottom:.625em}
+ul.checklist,ul.none,ol.none,ul.no-bullet,ol.no-bullet,ol.unnumbered,ul.unstyled,ol.unstyled{list-style-type:none}
+ul.no-bullet,ol.no-bullet,ol.unnumbered{margin-left:.625em}
+ul.unstyled,ol.unstyled{margin-left:0}
+ul.checklist{margin-left:.625em}
+ul.checklist li>p:first-child>.fa-square-o:first-child,ul.checklist li>p:first-child>.fa-check-square-o:first-child{width:1.25em;font-size:.8em;position:relative;bottom:.125em}
+ul.checklist li>p:first-child>input[type="checkbox"]:first-child{margin-right:.25em}
+ul.inline{display:-ms-flexbox;display:-webkit-box;display:flex;-ms-flex-flow:row wrap;-webkit-flex-flow:row wrap;flex-flow:row wrap;list-style:none;margin:0 0 .625em -1.25em}
+ul.inline>li{margin-left:1.25em}
+.unstyled dl dt{font-weight:400;font-style:normal}
+ol.arabic{list-style-type:decimal}
+ol.decimal{list-style-type:decimal-leading-zero}
+ol.loweralpha{list-style-type:lower-alpha}
+ol.upperalpha{list-style-type:upper-alpha}
+ol.lowerroman{list-style-type:lower-roman}
+ol.upperroman{list-style-type:upper-roman}
+ol.lowergreek{list-style-type:lower-greek}
+.hdlist>table,.colist>table{border:0;background:none}
+.hdlist>table>tbody>tr,.colist>table>tbody>tr{background:none}
+td.hdlist1,td.hdlist2{vertical-align:top;padding:0 .625em}
+td.hdlist1{font-weight:bold;padding-bottom:1.25em}
+.literalblock+.colist,.listingblock+.colist{margin-top:-.5em}
+.colist td:not([class]):first-child{padding:.4em .75em 0;line-height:1;vertical-align:top}
+.colist td:not([class]):first-child img{max-width:none}
+.colist td:not([class]):last-child{padding:.25em 0}
+.thumb,.th{line-height:0;display:inline-block;border:solid 4px #fff;-webkit-box-shadow:0 0 0 1px #ddd;box-shadow:0 0 0 1px #ddd}
+.imageblock.left{margin:.25em .625em 1.25em 0}
+.imageblock.right{margin:.25em 0 1.25em .625em}
+.imageblock>.title{margin-bottom:0}
+.imageblock.thumb,.imageblock.th{border-width:6px}
+.imageblock.thumb>.title,.imageblock.th>.title{padding:0 .125em}
+.image.left,.image.right{margin-top:.25em;margin-bottom:.25em;display:inline-block;line-height:0}
+.image.left{margin-right:.625em}
+.image.right{margin-left:.625em}
+a.image{text-decoration:none;display:inline-block}
+a.image object{pointer-events:none}
+sup.footnote,sup.footnoteref{font-size:.875em;position:static;vertical-align:super}
+sup.footnote a,sup.footnoteref a{text-decoration:none}
+sup.footnote a:active,sup.footnoteref a:active{text-decoration:underline}
+#footnotes{padding-top:.75em;padding-bottom:.75em;margin-bottom:.625em}
+#footnotes hr{width:20%;min-width:6.25em;margin:-.25em 0 .75em;border-width:1px 0 0}
+#footnotes .footnote{padding:0 .375em 0 .225em;line-height:1.3334;font-size:.875em;margin-left:1.2em;margin-bottom:.2em}
+#footnotes .footnote a:first-of-type{font-weight:bold;text-decoration:none;margin-left:-1.05em}
+#footnotes .footnote:last-of-type{margin-bottom:0}
+#content #footnotes{margin-top:-.625em;margin-bottom:0;padding:.75em 0}
+.gist .file-data>table{border:0;background:#fff;width:100%;margin-bottom:0}
+.gist .file-data>table td.line-data{width:99%}
+div.unbreakable{page-break-inside:avoid}
+.big{font-size:larger}
+.small{font-size:smaller}
+.underline{text-decoration:underline}
+.overline{text-decoration:overline}
+.line-through{text-decoration:line-through}
+.aqua{color:#00bfbf}
+.aqua-background{background:#00fafa}
+.black{color:#000}
+.black-background{background:#000}
+.blue{color:#0000bf}
+.blue-background{background:#0000fa}
+.fuchsia{color:#bf00bf}
+.fuchsia-background{background:#fa00fa}
+.gray{color:#606060}
+.gray-background{background:#7d7d7d}
+.green{color:#006000}
+.green-background{background:#007d00}
+.lime{color:#00bf00}
+.lime-background{background:#00fa00}
+.maroon{color:#600000}
+.maroon-background{background:#7d0000}
+.navy{color:#000060}
+.navy-background{background:#00007d}
+.olive{color:#606000}
+.olive-background{background:#7d7d00}
+.purple{color:#600060}
+.purple-background{background:#7d007d}
+.red{color:#bf0000}
+.red-background{background:#fa0000}
+.silver{color:#909090}
+.silver-background{background:#bcbcbc}
+.teal{color:#006060}
+.teal-background{background:#007d7d}
+.white{color:#bfbfbf}
+.white-background{background:#fafafa}
+.yellow{color:#bfbf00}
+.yellow-background{background:#fafa00}
+span.icon>.fa{cursor:default}
+a span.icon>.fa{cursor:inherit}
+.admonitionblock td.icon [class^="fa icon-"]{font-size:2.5em;text-shadow:1px 1px 2px rgba(0,0,0,.5);cursor:default}
+.admonitionblock td.icon .icon-note::before{content:"\f05a";color:#19407c}
+.admonitionblock td.icon .icon-tip::before{content:"\f0eb";text-shadow:1px 1px 2px rgba(155,155,0,.8);color:#111}
+.admonitionblock td.icon .icon-warning::before{content:"\f071";color:#bf6900}
+.admonitionblock td.icon .icon-caution::before{content:"\f06d";color:#bf3400}
+.admonitionblock td.icon .icon-important::before{content:"\f06a";color:#bf0000}
+.conum[data-value]{display:inline-block;color:#fff!important;background:rgba(0,0,0,.8);-webkit-border-radius:100px;border-radius:100px;text-align:center;font-size:.75em;width:1.67em;height:1.67em;line-height:1.67em;font-family:"Open Sans","DejaVu Sans",sans-serif;font-style:normal;font-weight:bold}
+.conum[data-value] *{color:#fff!important}
+.conum[data-value]+b{display:none}
+.conum[data-value]::after{content:attr(data-value)}
+pre .conum[data-value]{position:relative;top:-.125em}
+b.conum *{color:inherit!important}
+.conum:not([data-value]):empty{display:none}
+dt,th.tableblock,td.content,div.footnote{text-rendering:optimizeLegibility}
+h1,h2,p,td.content,span.alt{letter-spacing:-.01em}
+p strong,td.content strong,div.footnote strong{letter-spacing:-.005em}
+p,blockquote,dt,td.content,span.alt{font-size:1.0625rem}
+p{margin-bottom:1.25rem}
+.sidebarblock p,.sidebarblock dt,.sidebarblock td.content,p.tableblock{font-size:1em}
+.exampleblock>.content{background:#fffef7;border-color:#e0e0dc;-webkit-box-shadow:0 1px 4px #e0e0dc;box-shadow:0 1px 4px #e0e0dc}
+.print-only{display:none!important}
+@page{margin:1.25cm .75cm}
+@media print{*{-webkit-box-shadow:none!important;box-shadow:none!important;text-shadow:none!important}
+html{font-size:80%}
+a{color:inherit!important;text-decoration:underline!important}
+a.bare,a[href^="#"],a[href^="mailto:"]{text-decoration:none!important}
+a[href^="http:"]:not(.bare)::after,a[href^="https:"]:not(.bare)::after{content:"(" attr(href) ")";display:inline-block;font-size:.875em;padding-left:.25em}
+abbr[title]::after{content:" (" attr(title) ")"}
+pre,blockquote,tr,img,object,svg{page-break-inside:avoid}
+thead{display:table-header-group}
+svg{max-width:100%}
+p,blockquote,dt,td.content{font-size:1em;orphans:3;widows:3}
+h2,h3,#toctitle,.sidebarblock>.content>.title{page-break-after:avoid}
+#toc,.sidebarblock,.exampleblock>.content{background:none!important}
+#toc{border-bottom:1px solid #dddddf!important;padding-bottom:0!important}
+body.book #header{text-align:center}
+body.book #header>h1:first-child{border:0!important;margin:2.5em 0 1em}
+body.book #header .details{border:0!important;display:block;padding:0!important}
+body.book #header .details span:first-child{margin-left:0!important}
+body.book #header .details br{display:block}
+body.book #header .details br+span::before{content:none!important}
+body.book #toc{border:0!important;text-align:left!important;padding:0!important;margin:0!important}
+body.book #toc,body.book #preamble,body.book h1.sect0,body.book .sect1>h2{page-break-before:always}
+.listingblock code[data-lang]::before{display:block}
+#footer{padding:0 .9375em}
+.hide-on-print{display:none!important}
+.print-only{display:block!important}
+.hide-for-print{display:none!important}
+.show-for-print{display:inherit!important}}
+@media print,amzn-kf8{#header>h1:first-child{margin-top:1.25rem}
+.sect1{padding:0!important}
+.sect1+.sect1{border:0}
+#footer{background:none}
+#footer-text{color:rgba(0,0,0,.6);font-size:.9em}}
+@media amzn-kf8{#header,#content,#footnotes,#footer{padding:0}}
+</style>
+</head>
+<body class="article">
+<div id="header">
+<div id="toc" class="toc">
+<div id="toctitle">Table of Contents</div>
+<ul class="sectlevel1">
+<li><a href="#_introducing_subsurface_mobile">1. Introducing Subsurface-mobile</a></li>
+<li><a href="#_installing_subsurface_mobile_on_your_mobile_device">2. Installing <em>Subsurface-mobile</em> on your mobile device</a></li>
+<li><a href="#_using_subsurface_mobile_for_the_first_time">3. Using <em>Subsurface-mobile</em> for the first time</a>
+<ul class="sectlevel2">
+<li><a href="#_when_not_using_cloud_storage">3.1. When NOT Using Cloud Storage</a></li>
+<li><a href="#_using_cloud_storage">3.2. Using Cloud Storage</a></li>
+<li><a href="#_changing_the_existing_login_credentials_on_the_subsurface_cloud">3.3. Changing the existing login credentials on the <em>Subsurface</em> cloud</a></li>
+</ul>
+</li>
+<li><a href="#_getting_support">4. Getting Support</a></li>
+<li><a href="#_menu_structure_and_user_interface">5. Menu Structure and User Interface</a></li>
+<li><a href="#_the_dive_list">6. The Dive List</a></li>
+<li><a href="#_filter_the_dive_list">7. Filter the dive list</a></li>
+<li><a href="#_viewing_the_locations_of_all_dives_in_the_dive_list">8. Viewing the locations of all dives in the dive list</a></li>
+<li><a href="#_viewing_the_location_of_a_dive_on_google_maps">9. Viewing the location of a dive on <em>Google Maps</em></a></li>
+<li><a href="#S_View_Dive">10. View a dive</a></li>
+<li><a href="#S_Edit_Dive">11. Edit a particular dive</a></li>
+<li><a href="#S_Add_Dive">12. Manually adding a new dive to the dive list</a></li>
+<li><a href="#_copy_dive_information_from_one_dive_to_another">13. Copy dive information from one dive to another</a></li>
+<li><a href="#_deleting_a_dive">14. Deleting a dive</a></li>
+<li><a href="#S_Download">15. Download dives from a dive computer</a></li>
+<li><a href="#_dive_log_management">16. Dive log management</a>
+<ul class="sectlevel2">
+<li><a href="#_add_new_dive_manually">16.1. Add new dive manually</a></li>
+<li><a href="#_download_from_dc">16.2. Download from DC</a></li>
+<li><a href="#_apply_gps_fixes">16.3. Apply GPS fixes</a></li>
+<li><a href="#_manually_sync_the_dive_log_with_the_subsurface_cloud_storage">16.4. Manually sync the dive log with the <em>Subsurface</em> cloud storage</a></li>
+<li><a href="#_enable_cloud_auto_sync">16.5. Enable cloud auto sync</a></li>
+</ul>
+</li>
+<li><a href="#_recording_dive_locations_using_gps">17. Recording dive locations using GPS</a>
+<ul class="sectlevel2">
+<li><a href="#S_ConfigureGPS">17.1. Configuring the GPS service</a></li>
+<li><a href="#_collecting_gps_positions">17.2. Collecting GPS positions</a></li>
+<li><a href="#_viewing_gps_data">17.3. Viewing GPS data</a></li>
+<li><a href="#_applying_gps_data_to_dives_in_the_dive_log">17.4. Applying GPS data to dives in the dive log</a></li>
+</ul>
+</li>
+<li><a href="#S_Settings">18. Specifying the settings for <em>Subsurface-mobile</em>.</a>
+<ul class="sectlevel2">
+<li><a href="#S_ChangeCloudAccount">18.1. Changing to a different <em>Subsurface</em> cloud account</a></li>
+<li><a href="#_changing_the_color_theme_of_subsurface_mobile">18.2. Changing the color theme of <em>Subsurface-mobile</em></a></li>
+<li><a href="#_configuring_the_gps_webservice">18.3. Configuring the GPS webservice</a></li>
+<li><a href="#_activating_the_developer_sub_menu">18.4. Activating the Developer sub-menu</a></li>
+<li><a href="#_app_log">18.5. App log</a></li>
+<li><a href="#_theme_information">18.6. Theme information</a></li>
+</ul>
+</li>
+</ul>
+</div>
+</div>
+<div id="content">
+<div class="imageblock text-center">
+<div class="content">
+<img src="mobile-images/Banner.jpg" alt="Banner">
+</div>
+</div>
+<div class="paragraph">
+<p><span class="big">Subsurface-mobile USER MANUAL</span></p>
+</div>
+<div class="paragraph">
+<p><strong>Manual authors</strong>: Willem Ferguson, Dirk Hohndel</p>
+</div>
+<div class="paragraph">
+<p><span class="blue"><em>Version 2.1.5, December 2018</em></span></p>
+</div>
+<div class="paragraph">
+<p>Welcome as a user of <em>Subsurface</em> and <em>Subsurface-mobile</em>, advanced dive logging
+software with extensive infrastructure to describe, organize, and interpret scuba
+and free dives. <em>Subsurface</em> offers many advantages over other similar
+software solutions, including compatibility with Windows, macOS, Linux (many
+distributions), Android and iOS. In addition, <em>Subsurface</em> is
+open-source software that allows downloading dive
+information from many dive computers.</p>
+</div>
+<div class="sect1">
+<h2 id="_introducing_subsurface_mobile">1. Introducing Subsurface-mobile</h2>
+<div class="sectionbody">
+<div class="paragraph">
+<p><em>Subsurface-mobile</em> is a limited mobile version of <em>Subsurface</em>
+aimed at Android and iOS smartphone and tablet devices, allowing viewing, entering, sharing, and storage of dive information at dive sites where a desktop
+computer is not useful. While the desktop version of <em>Subsurface</em> shows much more detailed information
+for each dive, the mobile version allows a more accessible dive log
+on a dive trip, useful for proving dive experience to dive shops or to review
+previous dives. <em>Subsurface-mobile</em> also allows
+the gathering of GPS locations where dives are performed.</p>
+</div>
+<div class="paragraph">
+<p>Users of <em>Subsurface-mobile</em> typically use the
+mobile app as a companion to the laptop/desktop version of <em>Subsurface</em>,  sharing dive information
+between the mobile and the desktop versions. However <em>Subsurface-mobile</em> can
+also be used independently of the desktop version and does not require the use of
+cloud storage.</p>
+</div>
+<div class="paragraph">
+<p><em>Subsurface-mobile</em> allows:</p>
+</div>
+<div class="ulist">
+<ul>
+<li>
+<p>Download and storage of dive log information using the <em>Subsurface</em> cloud.</p>
+</li>
+<li>
+<p>Viewing this information on a mobile device.</p>
+</li>
+<li>
+<p>Manually creating and adding new dive records to your dive log.</p>
+</li>
+<li>
+<p>Download dive data directly from many dive computers.</p>
+</li>
+<li>
+<p>Editing many of the dive log data fields, e.g. dive-master, buddy,
+equipment or notes relating to a dive.</p>
+</li>
+<li>
+<p>Recording, storing and applying GPS positions of dives.</p>
+</li>
+<li>
+<p>Viewing the localities of recorded GPS positions and of dives
+on a map.</p>
+</li>
+</ul>
+</div>
+<div class="paragraph">
+<p>These items are discussed in greater detail in the following text.
+<em>Subsurface-mobile</em> does not support download of dive data from all the
+dive computers that the desktop/laptop version can. This limitation is
+mainly caused by the inability of accessing some types of devices on the
+two mobile platforms. On Android, a subset of
+dive computers that use a FTDI USB interface or a Bluetooth / Bluetooth LE interface
+are accessible by <em>Subsurface-mobile</em>. On iOS, only Bluetooth LE based
+dive computers are supported.</p>
+</div>
+</div>
+</div>
+<div class="sect1">
+<h2 id="_installing_subsurface_mobile_on_your_mobile_device">2. Installing <em>Subsurface-mobile</em> on your mobile device</h2>
+<div class="sectionbody">
+<div class="paragraph">
+<p>Find <em>Subsurface-mobile</em> in the <em>Google Play Store</em> or the <em>iTunes Store</em>
+and install it. Please note that both stores also contain the older <em>Subsurface</em> companion app (used only for tracking GPS positions) - make sure you actually install <em>Subsurface-mobile</em>.</p>
+</div>
+</div>
+</div>
+<div class="sect1">
+<h2 id="_using_subsurface_mobile_for_the_first_time">3. Using <em>Subsurface-mobile</em> for the first time</h2>
+<div class="sectionbody">
+<div class="paragraph">
+<p>When you start <em>Subsurface-mobile</em> for the first time, a Subsurface
+splash screen is shown while the program loads. On some devices this
+may take several seconds. After loading, the <em>Cloud Credentials screen</em> appears
+(see image below on left).</p>
+</div>
+<div class="imageblock text-center">
+<div class="content">
+<img src="mobile-images/Credentials.jpg" alt="FIGURE: Mobile credentials screen">
+</div>
+</div>
+<div class="sect2">
+<h3 id="_when_not_using_cloud_storage">3.1. When NOT Using Cloud Storage</h3>
+<div class="paragraph">
+<p>Tap the "No cloud mode" button. The app will not access the <em>Subsurface</em>
+cloud storage server
+to obtain dive log information. This means that dive log information is
+stored on the mobile device only. If no dives have been entered into the dive log
+yet (the usual case), an empty dive log is created.</p>
+</div>
+</div>
+<div class="sect2">
+<h3 id="_using_cloud_storage">3.2. Using Cloud Storage</h3>
+<div class="paragraph">
+<p>The <em>Subsurface</em> developers provide a dedicated and
+free Internet cloud storage account that can be used for
+storing dive log information. This account can be created either from <em>Subsurface</em> on the desktop or from <em>Subsurface-mobile</em>
+using a mobile device; you can
+do full maintenance of a dive log from <em>Subsurface-mobile</em> alone. By using the same
+credentials with <em>Subsurface-mobile</em> and <em>Subsurface</em> for desktop, the <em>Subsurface</em> cloud storage allows sharing of a dive
+log between both (or even more than two) devices.</p>
+</div>
+<div class="paragraph">
+<p>The dive data on the cloud are cached locally both on the mobile device as well as on the desktop - it is easy to create backups of the data (for example in XML format) on the desktop: both mobile device and desktop keep a local copy of the data so that the dive log is always accessible, even without Internet connection. The Subsurface team never accesses a user&#8217;s dive data without explicit permission to do so, the data are not used for any purpose other than providing them to the user who created them. There are no ads and no harvesting / analysis of the data stored in the Subsurface cloud storage.</p>
+</div>
+<div class="paragraph">
+<p>1) Enter an e-mail address and a password in the fields indicated on the screen (see image above).
+The e-mail address should be in lower case and the password should contain a combination of
+letters from the alphabet (upper and lower case) and/or numbers.
+Tap the "Sign-in or Register" button. If you have already set
+up an account from the <em>Subsurface</em> desktop application, enter the same credentials here.
+Once the dive
+list has been downloaded from the cloud, <em>Subsurface-mobile</em> usually works only with the the local
+copy on the mobile device. This avoids long delays or even failure of operations if there is a bad (or no) internet connection, a situation fairly common at many dive sites. Once registered, <em>Subsurface-mobile</em> remembers the cloud credentials and it is not necessary to provide these again when launching the program.</p>
+</div>
+<div class="paragraph">
+<p>2) If this is a new cloud account, a PIN screen will open (see image on right, above). A PIN is e-mailed
+to the email address entered in the previous step. Enter this PIN into the field indicated
+and tap the <em>Register</em> button. The user
+information is stored on the cloud server and access to the cloud is enabled. In this case
+the dive list is initially empty. Start entering dives in the dive
+log or download dive information from a supported dive computer.</p>
+</div>
+<div class="sidebarblock">
+<div class="content">
+<div class="admonitionblock important">
+<table>
+<tr>
+<td class="icon">
+<img src="./images/icons/images/icons/important.png" alt="Important">
+</td>
+<td class="content">
+<strong>Cloud problems: FAQ</strong>
+</td>
+</tr>
+</table>
+</div>
+<div class="paragraph">
+<p><span class="blue">After filling in the correct information and submitting it, I did not receive a PIN by email</span></p>
+</div>
+<div class="olist arabic">
+<ol class="arabic">
+<li>
+<p>Check <strong>carefully</strong> that there is not a spelling mistake in the email address you provided.</p>
+</li>
+<li>
+<p>Check that the return email containing the PIN is not in the SPAM folder of your email client.</p>
+</li>
+<li>
+<p>Wait for 24 hours and check again for an email with a PIN.</p>
+</li>
+<li>
+<p>If there is still no email containing a PIN, send mail to <a href="mailto:in-app-support@subsurface-divelog.org">in-app-support@subsurface-divelog.org</a></p>
+</li>
+</ol>
+</div>
+<div class="paragraph">
+<p><span class="blue">I want to access the Subsurface cloud facility but I have forgotten my password. How can I reset my password?</span></p>
+</div>
+<div class="paragraph">
+<p>Open the following web address: <a href="https://cloud.subsurface-divelog.org/passwordreset" class="bare">https://cloud.subsurface-divelog.org/passwordreset</a></p>
+</div>
+<div class="paragraph">
+<p>This will require that you enter the same email address that you used during cloud registration.</p>
+</div>
+</div>
+</div>
+<div class="paragraph">
+<p>The dive log can be updated automatically. If there is Internet connectivity, <em>Subsurface-mobile</em> accesses
+the cloud-based dive log to verify that the local copy of the dive log is still the
+same as the log in the cloud server. If not, the local copy and the copy on
+the server are synchronized.</p>
+</div>
+</div>
+<div class="sect2">
+<h3 id="_changing_the_existing_login_credentials_on_the_subsurface_cloud">3.3. Changing the existing login credentials on the <em>Subsurface</em> cloud</h3>
+<div class="paragraph">
+<p>The login credentials can be changed, for example to work with
+multiple accounts. See the section on <a href="#S_ChangeCloudAccount">Changing to a different <em>Subsurface</em> cloud account</a>.</p>
+</div>
+</div>
+</div>
+</div>
+<div class="sect1">
+<h2 id="_getting_support">4. Getting Support</h2>
+<div class="sectionbody">
+<div class="paragraph">
+<p>The best place to get support is the Subsurface User Forum. Additionally, Subsurface-mobile allows you to send a support email by tapping on <em>Ask for support</em> in the main menu. This will open an email to our in app support address in the native email client, including the relevant logs.</p>
+</div>
+</div>
+</div>
+<div class="sect1">
+<h2 id="_menu_structure_and_user_interface">5. Menu Structure and User Interface</h2>
+<div class="sectionbody">
+<div class="paragraph">
+<p>At the bottom of many <em>Subsurface-mobile</em> screens is a round button that provides for
+several actions (see image below). The most common choice is indicated in a round colored <em>action button</em> (in the case below, edit a dive). Alternative actions are indicated in a white <em>action bar</em>.
+On Android devices, use the Android Back
+button for "cancel", "discard" or "back" actions. For example, when
+editing dive information, tapping the action button saves the changes while the
+Android back button can be used to cancel the edit without saving changes.</p>
+</div>
+<div class="imageblock text-center">
+<div class="content">
+<img src="mobile-images/Actionbutton.jpg" alt="FIGURE: Action Button">
+</div>
+</div>
+<div class="paragraph">
+<p>On iOS devices, on screens where a "back" action is enabled, a back arrow
+is shown in the top left corner of the screen.</p>
+</div>
+<div class="paragraph">
+<p>For a consistent experience between iOS and Android,
+<em>Subsurface-mobile</em> on Android does not use the traditional "hamburger"
+menu button in the top left or right corner of the screen to open menus.
+Instead, <em>Subsurface-mobile</em> uses a
+different user interaction philosophy based on the Kirigami framework
+developed by the Plasma developers. There are three ways to open the main menu:</p>
+</div>
+<div class="ulist">
+<ul>
+<li>
+<p>Tap the "hamburger" symbol in the lower left corner of the screen
+(easy to reach for hand held devices)</p>
+</li>
+<li>
+<p>Swipe towards the right across the left edge of the screen</p>
+</li>
+</ul>
+</div>
+<div class="imageblock text-center">
+<div class="content">
+<img src="mobile-images/Menusystem.jpg" alt="FIGURE: Dive management sub-panel">
+</div>
+</div>
+<div class="paragraph">
+<p>The image above indicates some of the important features of the menu system.
+On the left is the main menu, activated as described above. On the right of the image
+are the items of all the sub-menus accessible.</p>
+</div>
+<div class="paragraph">
+<p>All screenshots in this user manual are currently from the Android
+version. The iOS screens look similar.</p>
+</div>
+</div>
+</div>
+<div class="sect1">
+<h2 id="_the_dive_list">6. The Dive List</h2>
+<div class="sectionbody">
+<div class="paragraph">
+<p>Most of the actions of <em>Subsurface-mobile</em> center around the dives on the
+dive list. While the dive list is loading from the cloud,
+a message appears at the bottom of the screen, indicating that the cloud is
+being accessed, after which the dive list is shown. Once the list is loaded you can scroll up and down through your dive history.
+To upload dives from a dive computer, tap the blue action button. If you wish
+to add a dive manually, tap the + button in the action bar (described below).
+Tapping an existing dive on the list brings up a display of the <em>Details View</em> for that dive
+including the dive profile, notes and additional information.</p>
+</div>
+<div class="imageblock text-center">
+<div class="content">
+<img src="mobile-images/Divelist2.jpg" alt="FIGURE: Dive list screen">
+</div>
+</div>
+<div class="paragraph">
+<p>You can view other dives by swiping the <em>Details view</em> to the right (for the
+previous dive) or to the left (following dive).
+Using the Action Bar, it is also possible to delete the dive (tap the dustbin
+on the Action Bar) or to view the dive
+location on a map viewer (Google Maps on Android, the Google Maps web site
+on iOS; tap the GPS icon on the Action Bar.).</p>
+</div>
+</div>
+</div>
+<div class="sect1">
+<h2 id="_filter_the_dive_list">7. Filter the dive list</h2>
+<div class="sectionbody">
+<div class="paragraph">
+<p>Use this action button:</p>
+</div>
+<div class="imageblock text-center">
+<div class="content">
+<img src="mobile-images/FilterButton.jpg" alt="FIGURE: Filter button">
+</div>
+</div>
+<div class="paragraph">
+<p>at the bottom of the dive list to perform filtering of the dive list (see image on left above).</p>
+</div>
+<div class="imageblock text-center">
+<div class="content">
+<img src="mobile-images/Filter.jpg" alt="FIGURE: Filter tool">
+</div>
+</div>
+<div class="paragraph">
+<p>By default, all the dives in the dive log are shown in the dive list. After several years your dive log can become quite long and, sometimes, you might like to list only the dives of a particular type, e.g. those at a particular dive site or those with a specific buddy or dive master. Use the Filter to achieve this. The filter mechanism searches through all the information for each dive, looking for one or more key words. Only the dives containing these key words are listed in the dive list. In the <a href="#S_Settings"><em>Settings</em></a> screen there two options that affect the way the filter searches for appropriate information. Firstly, you can select <em>Match filter case sensitive</em> which causes the search of key words to be case sensitive. Secondly, you can select <em>Include notes in full text filtering</em>. If this option is not selected, the filter does not search through the dive notes for key words. Selecting the <em>Filter</em> action button brings up a text box at the top of the dive list. Type the key words to be searched for. In the image on the left, the dive list has been filtered for the word "Nitrox" and 265 dives were found containing this word as a tag. For each trip in the dive list the number of dives containing "Nitrox" as a tag is shown. To clear the filter, remove the key words from the text box and select the Filter action button to switch off filtering.</p>
+</div>
+</div>
+</div>
+<div class="sect1">
+<h2 id="_viewing_the_locations_of_all_dives_in_the_dive_list">8. Viewing the locations of all dives in the dive list</h2>
+<div class="sectionbody">
+<div class="imageblock text-center">
+<div class="content">
+<img src="mobile-images/DivesMap.jpg" alt="FIGURE: Map of all dive sites">
+</div>
+</div>
+<div class="paragraph">
+<p>The locations of all dives in the dive list can be viewed from the <em>Main Menu</em> by selecting the <em>Map</em> option.
+A satellite image of the world is shown. At that scale no dive sites are shown. If you zoom into a particular region
+of the world the dive sites appear, indicated by red flags. Zooming in even closer indicates the names of each
+of the different dive sites.</p>
+</div>
+</div>
+</div>
+<div class="sect1">
+<h2 id="_viewing_the_location_of_a_dive_on_google_maps">9. Viewing the location of a dive on <em>Google Maps</em></h2>
+<div class="sectionbody">
+<div class="imageblock text-center">
+<div class="content">
+<img src="mobile-images/Map.jpg" alt="FIGURE: Map of dive site">
+</div>
+</div>
+<div class="paragraph">
+<p>In the <em>Details View</em>, the Action Bar at the bottom has a GPS pin on the
+left hand side. Tap that pin and the dive site is shown in Google Maps. Close Google Maps by using the Android <em>Back</em> button
+or tapping on the <em>Subsurface-mobile</em> link in the top left corner on iOS.</p>
+</div>
+<div class="paragraph">
+<p>Alternatively, the <em>Details View</em> has a button at the top right hand marked
+<em>Map it</em>. Tap this button to open Google Maps showing the dive site (image on left).</p>
+</div>
+</div>
+</div>
+<div class="sect1">
+<h2 id="S_View_Dive">10. View a dive</h2>
+<div class="sectionbody">
+<div class="paragraph">
+<p>When you tap on a dive in the <em>Dive List</em>, a new screen with the dive profile
+and many important details about the dive is opened. You can use a pich gesture
+to zoom into the profile, and tapping with one finger, waiting briefly until
+the profile becomes translucent, and then dragging the finger around allows you
+to pan the profile so the interesting parts are shown.</p>
+</div>
+</div>
+</div>
+<div class="sect1">
+<h2 id="S_Edit_Dive">11. Edit a particular dive</h2>
+<div class="sectionbody">
+<div class="imageblock text-center">
+<div class="content">
+<img src="mobile-images/Editdive.jpg" alt="FIGURE: Dive edit screen">
+</div>
+</div>
+<div class="paragraph">
+<p>At the bottom of the <em>Dive Details</em> screen the action button is a pencil.
+Tapping the pencil button changes the page and enables edit boxes that allow
+modifying the existing dive information, e.g. adding text to the dive notes
+or changing the names or values of some of the information (see image on left).
+It may be necessary to scroll the window to access all the information.
+At the bottom of the edit screen is a <em>Save</em> action button. Tap this to save
+the new information, after which the dive list screen is
+updated and shown. To cancel any edits, tap the Android <em>Back</em> Button or
+the application back button at the top left of the screen on iOS.</p>
+</div>
+</div>
+</div>
+<div class="sect1">
+<h2 id="S_Add_Dive">12. Manually adding a new dive to the dive list</h2>
+<div class="sectionbody">
+<div class="paragraph">
+<p>You can manually add a dive to the existing dive list. On the dive list
+tap the "plus" sign in the action bar, or use the
+main menu and tap <em>Dive management  &#8594;  Add dive manually</em>. This opens  a screen that is
+identical to the editing screen discussed above. When a dive is added manually, you
+cannot directly add a dive profile from a dive computer. However, if you do not use a
+dive computer, the duration, depth and several other bits of information about
+the new dive can be entered. The <em>Action button</em> at the bottom of the screen
+contains a disk symbol. Tap this to save the new dive. To cancel any edits, tap the <em>Back</em> button.
+The left-hand image below shows a screenshot of a dive being created and the right-hand image shows
+the same dive in <em>Details View</em>.</p>
+</div>
+<div class="imageblock text-center">
+<div class="content">
+<img src="mobile-images/Manualdive.jpg" alt="FIGURE: Manual dive entry screen">
+</div>
+</div>
+</div>
+</div>
+<div class="sect1">
+<h2 id="_copy_dive_information_from_one_dive_to_another">13. Copy dive information from one dive to another</h2>
+<div class="sectionbody">
+<div class="paragraph">
+<p>When editing dives it is possible to transfer information from one dive to another. For instance,
+when diving with the same buddy and the same equipment configuration during a particular dive trip
+it can be efficient to simply copy all this information from the previous dive into the dive that
+is being edited. Currently a standard list of dive information is copied to the clipboard:</p>
+</div>
+<div class="paragraph">
+<p>Divemaster, Buddy, Suit, Tags, Cylinders, Weights.</p>
+</div>
+<div class="paragraph">
+<p>Copy and paste dive information is performed on the Dive List. Long-press on a dive. A panel
+with three icons appears on top the selected dive :</p>
+</div>
+<div class="imageblock text-center">
+<div class="content">
+<img src="mobile-images/CopyDeleteDive.jpg" alt="FIGURE: Copy/Delete dive information">
+</div>
+</div>
+<div class="paragraph">
+<p>To copy the above information to the clipboard, select the leftmost of the three icons. A "Copy"
+notification briefly appears on the screen. Now long-press the dive into which the copied information
+needs to be pasted. The same three icons appear on the target dive. Select the middle icon. A "Paste"
+notification briefly appears on the screen. This completes the copy-and-paste action. Continue by
+reviewing this new (pasted) information by manually editing the target dive.</p>
+</div>
+<div class="paragraph">
+<p>To choose what dive details to copy, long-press the copy button. This will open
+up a configuration page where you can toggle the details you want to copy over
+to the destination.</p>
+</div>
+</div>
+</div>
+<div class="sect1">
+<h2 id="_deleting_a_dive">14. Deleting a dive</h2>
+<div class="sectionbody">
+<div class="paragraph">
+<p>Delete a dive from the dive list by long-pressing a dive
+until a red dustbin appears on the right-hand side (see image above). Tap the dustbin.
+The dive is deleted without asking any confirmation because <em>Subsurface-mobile</em> assumes that the
+combination of a long tap on the dive with another tap on the red dustbin is an unambiguous
+instruction to delete the dive.</p>
+</div>
+<div class="paragraph">
+<p>To choose what dive details to copy, long-press the copy button. This will open
+up a configuration page where you can toggle the details you want to copy over
+to the destination. By default, the following fields are copied:</p>
+</div>
+<div class="imageblock text-center">
+<div class="content">
+<img src="mobile-images/Delete_undo.jpg" alt="FIGURE: Undo delete dive">
+</div>
+</div>
+</div>
+</div>
+<div class="sect1">
+<h2 id="S_Download">15. Download dives from a dive computer</h2>
+<div class="sectionbody">
+<div class="paragraph">
+<p>From the main menu,
+tap <em>Manage dives &#8594;  Download from DC</em>. A screen is shown requiring that the user specify
+the names of the vendor and model of the dive computer. For instance, when using a Shearwater Petrel dive
+computer, the vendor is <em>Shearwater</em> and the Dive computer name is <em>Petrel</em>(see image on the left, below).
+<strong>Caveats:</strong> The download feature in smartphones supports only a limited number of dive computers. On
+Android devices these are typically dive computers using an FTDI interface
+using a USB OTG cable (but this is blocked on some Android devices by OS
+settings). Android devices also support Bluetooth dive computers that
+are supported in <em>Subsurface</em> on the desktop. Both Android and iOS devices allow direct
+download of dive data from a handful of Bluetooth LE enabled dive
+computers. Use the <em>Vendor name</em> and <em>Dive Computer</em> drop-downs to pick the correct
+dive computer. When downloading from multiple different dive computers, shortcut
+buttons appear below the drop-downs to easily switch between them. In the <a href="#S_Settings"><em>Settings</em></a> menu
+you can remove these buttons, a useful feature for removing buttons of dive
+computers that are not used any more. Achieve this by selecting the option
+<em>Forget remembered dive computers</em> in the <a href="#S_Settings"><em>Settings</em></a> menu.
+After all these caveats, let us proceed with download.</p>
+</div>
+<div class="paragraph">
+<p><strong>For USB FTDI dive computers:</strong>
+This feature is not supported on iOS and on most newer Android devices. It still works on some older
+Android devices (typically Android 7 and older) and is kept enabled for this
+reason. Note: USB cables "normally" used for uploading dives to a
+desktop/laptop computer do NOT work; these
+cables usually have a full-sized ("Type A") male USB plug
+on one end which plugs into the USB port of a desktop/laptop computer. For downloads to a mobile device
+one needs a USB OTG (USB On-The-Go) cable.</p>
+</div>
+<table class="tableblock frame-None grid-all stretch">
+<colgroup>
+<col style="width: 50%;">
+<col style="width: 50%;">
+</colgroup>
+<tbody>
+<tr>
+<td class="tableblock halign-left valign-top"><div class="content"><div class="imageblock text-center">
+<div class="content">
+<img src="mobile-images/USB-OTG.jpg" alt="FIGURE: USB-OTG cable">
+</div>
+</div></div></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">In most cases it is required to plug the USB
+cable "normally" used with the dive computer into a USB OTG cable which,
+in turn, plugs into the mini-USB (or sometimes a USB "Type C")
+receptacle of the mobile device. The
+OTG cable usually has a full-size ("Type A") female receptacle at one end which
+accommodates the full-sized male plug
+of the USB cable "normally" used (see image below). This means that two cables are used to connect
+the dive computer to the mobile device. <strong>Not all Android devices support OTG cables</strong>
+and even on some devices that do support those cables in general, as mentioned above <em>Subsurface-mobile</em>
+does usually not support cable based downloads, except on some older Android devices.</p></td>
+</tr>
+</tbody>
+</table>
+<div class="paragraph">
+<p><em>Subsurface</em> remembers the settings for dive computers that
+have been successfully used (image on right, below). These appear
+as buttons under a heading "<em>Previously used dive computers</em>".
+Select the appropriate button. Having connected the USB dive computer to the
+<em>Subsurface</em> computer and having selected the appropriate vendor and dive computer,
+ensure that the Connection text box shows "FTDI".</p>
+</div>
+<div class="paragraph">
+<p><strong>For BLUETOOTH/BTLE dive computers:</strong> The process for Bluetooth download is slightly different between Android and iOS.
+In our testing we got the best results on iOS when the dive computer was
+in Bluetooth mode before <em>Subsurface-mobile</em> is started. On most dive
+computers this is done through a menu entry, others (like the Suunto
+models) always respond to BTLE requests. However, on Android devices,
+you should first establish a link between the
+Bluetooth or Bluetooth LE dive computer and the mobile device using
+Android utilities. See below for more details.</p>
+</div>
+<div class="paragraph">
+<p>For Bluetooth-equipped dive computers and Android devices, establish a Bluetooth connection between the dive computer and the
+mobile device. Use the tools on the mobile device to achieve pairing between the Bluetooth dice computer
+and the mobile device. For many Android devices,
+the Settings &#8594; Bluetooth tool of Android is probably appropriate.
+<em>Subsurface-mobile</em> performs communication using both Bluetooth and Bluetooth-low-energy (BTLE).
+The appropriate choice of Bluetooth communication is often made by the software and the user need not be concerned with this.
+For dive computers with both Bluetooth and Bluetooth-low-energy (BTLE), a separate button is presented on the download
+screen for each mode of communication, allowing a choice. Use the <em>Connection</em> value to distinguish between the
+two options. In the image on the right, below, there are three buttons labeled "Shearwater Petrel 2". These represent two Shearwater Petrel dive computers, one of which can communicate in both Bluetooth as well as BTLE. The <em>Connection</em>
+information indicates that the Petrel with no BTLE is selected.</p>
+</div>
+<div class="paragraph">
+<p><strong>DOWNLOAD:</strong> With communication between dive computer and <em>Subsurface-mobile</em>
+having been set up, tap the <em>Download</em> button. Be patient because the download can take a few minutes.
+As a matter of fact, a complete first download from some dive computers can take 45 minutes or longer.
+The downloaded dives appear in the bottom part of the screen,
+the most recent dive at the top (see image on right, below).</p>
+</div>
+<div class="paragraph">
+<p>Each dive has a check-box on the left hand side, used for selecting which dives you want to be added to the
+<em>Subsurface-mobile</em> dive list: dives that are not checked are ignored. With the appropriate downloaded dives
+having been checked, tap the button at the bottom left labeled <em>Accept</em>. All the selected dives appear on
+the <em>Subsurface-mobile</em> dive list. The downloaded dive information can now be edited as described in the section
+above <a href="#S_Edit_Dive">Edit a dive</a>.</p>
+</div>
+<div class="imageblock text-center">
+<div class="content">
+<img src="mobile-images/DC-Download.jpg" alt="FIGURE: DC download screen">
+</div>
+</div>
+</div>
+</div>
+<div class="sect1">
+<h2 id="_dive_log_management">16. Dive log management</h2>
+<div class="sectionbody">
+<div class="paragraph">
+<p>A central  part of <em>Subsurface-mobile</em> is the ability to store the dive
+log using the <em>Subsurface</em> cloud storage.
+This provides security against loss or damage of the dive information in a local copy
+and allows the desktop version of <em>Subsurface</em> to
+access changes made using the mobile device. This ability is accessed
+through the main menu
+(by tapping the "Hamburger" icon at the bottom left of the screen).
+Tap the option <em>Dive management</em>, enabling a number of options:</p>
+</div>
+<div class="sect2">
+<h3 id="_add_new_dive_manually">16.1. Add new dive manually</h3>
+<div class="paragraph">
+<p>This is described above under the section dealing with <a href="#S_Add_Dive">Manually adding a new dive to the dive list</a>.</p>
+</div>
+</div>
+<div class="sect2">
+<h3 id="_download_from_dc">16.2. Download from DC</h3>
+<div class="paragraph">
+<p>This is described above under the section dealing with <a href="#S_Download">Download dives from a dive computer</a>.</p>
+</div>
+</div>
+<div class="sect2">
+<h3 id="_apply_gps_fixes">16.3. Apply GPS fixes</h3>
+<div class="paragraph">
+<p>This is described in the following main section, below.</p>
+</div>
+</div>
+<div class="sect2">
+<h3 id="_manually_sync_the_dive_log_with_the_subsurface_cloud_storage">16.4. Manually sync the dive log with the <em>Subsurface</em> cloud storage</h3>
+<div class="paragraph">
+<p>Upload the dives contained on the mobile device
+to the <em>Subsurface</em> cloud storage by tapping the option <em>Manual sync with cloud</em>.
+This synchronizes the local changes to
+the dive log with the cloud storage. It also downloads changes made to
+the dive log using another device or computer and stored in shared cloud storage.</p>
+</div>
+</div>
+<div class="sect2">
+<h3 id="_enable_cloud_auto_sync">16.5. Enable cloud auto sync</h3>
+<div class="paragraph">
+<p>By default <em>Subsurface-mobile</em> runs offline and only syncs the dive list
+with cloud storage when explicitly told to do so (see above).
+You can choose to always sync with the cloud servers. This is not
+recommended unless you are in
+an area with a fast and reliable internet connection, as otherwise
+<em>Subsurface-mobile</em> might appear to hang between operations as it tries to
+connect to the cloud server. Selecting <em>Enable cloud auto sync</em> causes
+the local dive log to be synchronized with the copy in the cloud every time that
+<em>Subsurface-mobile</em> is closed.</p>
+</div>
+</div>
+</div>
+</div>
+<div class="sect1">
+<h2 id="_recording_dive_locations_using_gps">17. Recording dive locations using GPS</h2>
+<div class="sectionbody">
+<div class="paragraph">
+<p>The fact that most smartphones have GPS facilities allows
+<em>Subsurface-mobile</em> to record
+the locations of dives. <strong>IMPORTANT: GPS-derived coordinates on a smartphone
+are not always accurate and can have an error greater than 1 km. GPS accuracy
+is determined by the hardware and software of the
+smartphone as well as by the GPS settings selected within Android/iOS.
+As of Android V6 select Android <em>Settings &#8594; Communication &#8594; Location &#8594; High accuracy.</em></strong>
+If the smartphone is taken on the boat
+during a dive, locations will be automatically recorded at regular intervals.
+These locations can then be applied to dives in the dive list. Here is how it&#8217;s done:</p>
+</div>
+<div class="sect2">
+<h3 id="S_ConfigureGPS">17.1. Configuring the GPS service</h3>
+<div class="paragraph">
+<p>From the <em>Main Menu</em>, select <a href="#S_Settings"><em>Settings</em></a> screen which has a section for
+configuring the GPS service (image below). GPS location data
+are collected at regular intervals, e.g. every 5 minutes, or at regular
+distances, e.g. after the boat has moved more than 200m, or a combination of
+both of these approaches. Provide the appropriate information and
+tap the <em>Back</em> button. The program is now ready to collect GPS positions.</p>
+</div>
+<div class="imageblock text-center">
+<div class="content">
+<img src="mobile-images/GPS-config.jpg" alt="FIGURE: GPS configure">
+</div>
+</div>
+</div>
+<div class="sect2">
+<h3 id="_collecting_gps_positions">17.2. Collecting GPS positions</h3>
+<table class="tableblock frame-None grid-all stretch">
+<colgroup>
+<col style="width: 50%;">
+<col style="width: 50%;">
+</colgroup>
+<tbody>
+<tr>
+<td class="tableblock halign-left valign-top"><div class="content"><div class="imageblock text-center">
+<div class="content">
+<img src="mobile-images/GPSstart.jpg" alt="FIGURE: GPS start">
+</div>
+</div></div></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">On the <em>Main Menu</em> select <em>GPS &#8594; Run location service</em>.
+<em>Subsurface-mobile</em> starts to collect GPS locations automatically,
+following the preferences specified as described above. While the GPS
+location service is running, all menus have a GPS symbol at the bottom
+of the menu, indicating that the service is active. After return from
+the dive trip, deactivate the collection of GPS data by tapping
+the option <em>GPS &#8594; Disable location service</em>. The GPS symbol at the bottom
+of all menus disappears.</p></td>
+</tr>
+</tbody>
+</table>
+</div>
+<div class="sect2">
+<h3 id="_viewing_gps_data">17.3. Viewing GPS data</h3>
+<div class="paragraph">
+<p>From the <em>GPS</em> submenu select <em>Show GPS fixes</em>. This brings
+up a list of GPS positions obtained by the location service (image
+below). Two actions are possible for each of the locations, enabled by
+dragging the right part of a location to the left. This exposes two
+options. Tapping the dustbin deletes this particular GPS location. Tapping the
+teardrop-shaped icon (actually a Google Maps pin) opens up Google Maps with a pin
+indicating the exact map position of the GPS record being viewed. The two above
+options can be hidden by drawing the GPS record to the right.</p>
+</div>
+<div class="imageblock text-center">
+<div class="content">
+<img src="mobile-images/gpsmanagement.jpg" alt="FIGURE: GPS management">
+</div>
+</div>
+</div>
+<div class="sect2">
+<h3 id="_applying_gps_data_to_dives_in_the_dive_log">17.4. Applying GPS data to dives in the dive log</h3>
+<div class="paragraph">
+<p>Assuming that all the dives have been entered into the dive log or have
+been downloaded from the <em>Subsurface</em> cloud, apply the GPS positions to
+these dives. GPS positions can only be applied to dives in the dive list.
+From the <em>Dive management</em> sub-panel, tap <em>Apply GPS fixes</em>. The dive list contains the start
+and end times of each dive. Now, <em>Subsurface-mobile</em> applies the first
+GPS position that falls within the dive period of each dive. This results
+in a GPS position for each dive that is saved as part of the dive log.</p>
+</div>
+</div>
+</div>
+</div>
+<div class="sect1">
+<h2 id="S_Settings">18. Specifying the settings for <em>Subsurface-mobile</em>.</h2>
+<div class="sectionbody">
+<div class="paragraph">
+<p>The <em>Settings</em> screen allows the customization of <em>Subsurface-mobile</em>. Many of the settings involve dragging a slider switch to activate or deactivate a particular setting.</p>
+</div>
+<div class="sect2">
+<h3 id="S_ChangeCloudAccount">18.1. Changing to a different <em>Subsurface</em> cloud account</h3>
+<div class="paragraph">
+<p>Some users have more than one <em>Subsurface</em> cloud account and have a need to switch between accounts. Tap <em>Settings</em> on the Main menu and scroll to the section titled <em>Cloud status</em> (see image below).
+Tap the <em>Change</em> button. This opens the <em>Cloud credentials</em> screen.
+change the credential information, then tap the button <em>Sign-in or register</em>. The appropriate dive list is shown.</p>
+</div>
+<div class="imageblock text-center">
+<div class="content">
+<img src="mobile-images/SettingsCloudTheme.jpg" alt="FIGURE: Settings: Cloud &amp; Theme">
+</div>
+</div>
+</div>
+<div class="sect2">
+<h3 id="_changing_the_color_theme_of_subsurface_mobile">18.2. Changing the color theme of <em>Subsurface-mobile</em></h3>
+<table class="tableblock frame-None grid-all stretch">
+<colgroup>
+<col style="width: 50%;">
+<col style="width: 50%;">
+</colgroup>
+<tbody>
+<tr>
+<td class="tableblock halign-left valign-top"><div class="content"><div class="imageblock text-center">
+<div class="content">
+<img src="mobile-images/PinkTheme.jpg" alt="FIGURE: GPS start">
+</div>
+</div></div></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock"><em>Subsurface-mobile</em> has three color schemes to please users with different
+tastes (see image above). This user manual shows the default color scheme, comprising blue
+colors. Change to a pink or a dark color scheme by opening the main menu,
+tap <em>Settings</em>, and scroll to the section with heading <em>Theme</em> (see image above).
+Select the appropriate color theme by dragging the appropriate slider on the right-hand.
+On the left is the dive list after selecting the Pink theme.</p></td>
+</tr>
+</tbody>
+</table>
+</div>
+<div class="sect2">
+<h3 id="_configuring_the_gps_webservice">18.3. Configuring the GPS webservice</h3>
+<div class="paragraph">
+<p>The Settings screen allows one to set up the way in which GPS positions are collected during dives. See the section on <a href="#S_ConfigureGPS">Configuring the GPS service</a>.</p>
+</div>
+</div>
+<div class="sect2">
+<h3 id="_activating_the_developer_sub_menu">18.4. Activating the Developer sub-menu</h3>
+<div class="paragraph">
+<p>The information in the subsurface.log generated while running <em>Subsurface-mobile</em>, plus some additional information for understanding the screen rendering of dive information as well as the way in which <em>Subsurface-mobile</em> processed information during a specific occasion while running the app (see section below) is available through a <em>Developer</em> menu at run time. Activate (or deactivate) this menu item on the Main Menu by dragging the slider switch in the Settings screen.
+If <em>Display developer menu</em> has been activated in the <em>Settings screen</em>, the Main menu has a <em>Developer</em> item. By tapping this one has two options that are relevant within
+the context of program development and debugging.</p>
+</div>
+</div>
+<div class="sect2">
+<h3 id="_app_log">18.5. App log</h3>
+<div class="paragraph">
+<p>This option shows the messages that <em>Subsurface-mobile</em> generates while running. While
+most users are not aware of these messages, they are often crucial in detecting any
+abnormal behavior of the app. The App log can be found in the root directory of the local storage of the mobile device.</p>
+</div>
+</div>
+<div class="sect2">
+<h3 id="_theme_information">18.6. Theme information</h3>
+<div class="paragraph">
+<p>This option provides a wealth of information about the screen characteristics of the mobile
+device and the font characteristics used by <em>Subsurface-mobile</em>.</p>
+</div>
+</div>
+</div>
+</div>
+</div>
+<div id="footer">
+<div id="footer-text">
+Last updated 2020-05-05 17:43:53 -0700
+</div>
+</div>
+</body>
+</html>
+\ No newline at end of file
diff --git a/Documentation/mobile-manual.txt b/Documentation/mobile-manual-v2.txt
index 58558b6b5..d003c9850 100644
--- a/Documentation/mobile-manual.txt
+++ b/Documentation/mobile-manual-v2.txt
@@ -2,8 +2,8 @@
 // Subsurface-mobile User Manual
 // =============================
 // :author: Manual authors: Willem Ferguson, Dirk Hohndel
-// :revnumber: 3.0.0
-// :revdate: March 2020
+// :revnumber: 2.1.5
+// :revdate: December 2018
 :icons:
 :toc:
 :toc-placement: manual
@@ -16,8 +16,9 @@ image::mobile-images/Banner.jpg["Banner",align="center"]
 
 *Manual authors*: Willem Ferguson, Dirk Hohndel
 
+// toc::[]
 
-[blue]#_Version 3.0.5, May 2020_#
+[blue]#_Version 2.1.5, December 2018_#
 
 Welcome as a user of _Subsurface_ and _Subsurface-mobile_, advanced dive logging
 software with extensive infrastructure to describe, organize, and interpret scuba
@@ -27,9 +28,6 @@ distributions), Android and iOS. In addition, _Subsurface_ is
 open-source software that allows downloading dive
 information from many dive computers.
 
-toc::[]
-
-
 Introducing Subsurface-mobile
 -----------------------------
 
@@ -52,7 +50,7 @@ _Subsurface-mobile_ allows:
 - Download and storage of dive log information using the _Subsurface_ cloud.
 - Viewing this information on a mobile device.
 - Manually creating and adding new dive records to your dive log.
-- Download dive data directly from some dive computers.
+- Download dive data directly from many dive computers.
 - Editing many of the dive log data fields, e.g. dive-master, buddy,
   equipment or notes relating to a dive.
 - Recording, storing and applying GPS positions of dives.
@@ -64,15 +62,14 @@ _Subsurface-mobile_ does not support download of dive data from all the
 dive computers that the desktop/laptop version can. This limitation is
 mainly caused by the inability of accessing some types of devices on the
 two mobile platforms. On Android, a subset of
-dive computers that use USB serial cables or a Bluetooth / Bluetooth LE interface
+dive computers that use a FTDI USB interface or a Bluetooth / Bluetooth LE interface
 are accessible by _Subsurface-mobile_. On iOS, only Bluetooth LE based
 dive computers are supported.
 
 == Installing _Subsurface-mobile_ on your mobile device
 
 Find _Subsurface-mobile_ in the _Google Play Store_ or the _iTunes Store_
-and install it. For Android devices without access to the _Google Play Store_
-APKs can be found in the downloads folder on the Subsurface website.
+and install it. Please note that both stores also contain the older _Subsurface_ companion app (used only for tracking GPS positions) - make sure you actually install _Subsurface-mobile_.
 
 == Using _Subsurface-mobile_ for the first time
 
@@ -99,13 +96,7 @@ do full maintenance of a dive log from _Subsurface-mobile_ alone. By using the s
 credentials with _Subsurface-mobile_ and _Subsurface_ for desktop, the _Subsurface_ cloud storage allows sharing of a dive
 log between both (or even more than two) devices.
 
-The dive data in the cloud are cached locally both on the mobile device as well as on the desktop -
-it is easy to create backups of the data (for example in XML format) on the desktop: both mobile
-device and desktop keep a local copy of the data so that the dive log is always accessible, even
-without Internet connection. The Subsurface team never accesses a user's dive data without explicit
-permission to do so, the data are not used for any purpose other than providing them to the user who
-created them. There are no ads and no harvesting / analysis of the data stored in the Subsurface
-cloud storage.
+The dive data on the cloud are cached locally both on the mobile device as well as on the desktop - it is easy to create backups of the data (for example in XML format) on the desktop: both mobile device and desktop keep a local copy of the data so that the dive log is always accessible, even without Internet connection. The Subsurface team never accesses a user's dive data without explicit permission to do so, the data are not used for any purpose other than providing them to the user who created them. There are no ads and no harvesting / analysis of the data stored in the Subsurface cloud storage.
 
 1) Enter an e-mail address and a password in the fields indicated on the screen (see image above).
 The e-mail address should be in lower case and the password should contain a combination of
@@ -114,21 +105,14 @@ Tap the "Sign-in or Register" button. If you have already set
 up an account from the _Subsurface_ desktop application, enter the same credentials here.
 Once the dive
 list has been downloaded from the cloud, _Subsurface-mobile_ usually works only with the the local
-copy on the mobile device. This avoids long delays or even failure of operations if there is a bad
-(or no) internet connection, a situation fairly common at many dive sites. Once registered,
-_Subsurface-mobile_ remembers the cloud credentials and it is not necessary to provide these again
-when launching the program.
+copy on the mobile device. This avoids long delays or even failure of operations if there is a bad (or no) internet connection, a situation fairly common at many dive sites. Once registered, _Subsurface-mobile_ remembers the cloud credentials and it is not necessary to provide these again when launching the program.
 
 2) If this is a new cloud account, a PIN screen will open (see image on right, above). A PIN is e-mailed
 to the email address entered in the previous step. Enter this PIN into the field indicated
 and tap the _Register_ button. The user
 information is stored on the cloud server and access to the cloud is enabled. In this case
 the dive list is initially empty. Start entering dives in the dive
-log or download dive information from a supported dive computer. After the PIN has been entered it
-is no longer needed - it just proves that this is indeed your email account.
-
-A https://www.youtube.com/watch?v=Vp_bEm5ZDRA[*video-tutorial*] is available that demonstrates
-how to connect to the cloud.
+log or download dive information from a supported dive computer.
 
 ****
 [icon="images/icons/important.png"]
@@ -140,11 +124,11 @@ how to connect to the cloud.
 1. Check *carefully* that there is not a spelling mistake in the email address you provided.
 2. Check that the return email containing the PIN is not in the SPAM folder of your email client.
 3. Wait for 24 hours and check again for an email with a PIN. 
-4. If there is still no email containing a PIN, send mail to mailto:in-app-support@subsurface-divelog.org[our in-app-support address]
+4. If there is still no email containing a PIN, send mail to in-app-support@subsurface-divelog.org
 
 [blue]#I want to access the Subsurface cloud facility but I have forgotten my password. How can I reset my password?#
 
-Use our https://cloud.subsurface-divelog.org/passwordreset[Internet-based password reset facility]. 
+Open the following web address: https://cloud.subsurface-divelog.org/passwordreset
 
 This will require that you enter the same email address that you used during cloud registration.
 ****
@@ -161,18 +145,12 @@ multiple accounts. See the section on xref:S_ChangeCloudAccount[Changing to a di
 
 == Getting Support
 
-The best place to get support is the Subsurface User Forum. Additionally, Subsurface-mobile allows
-you to send a support email by tapping on _Ask for support_ in the main menu. This will open an
-email to our in app support address in the native email client, including the relevant logs.
+The best place to get support is the Subsurface User Forum. Additionally, Subsurface-mobile allows you to send a support email by tapping on _Ask for support_ in the main menu. This will open an email to our in app support address in the native email client, including the relevant logs.
 
 == Menu Structure and User Interface
 
 At the bottom of many _Subsurface-mobile_ screens is a round button that provides for
 several actions (see image below). The most common choice is indicated in a round colored _action button_ (in the case below, edit a dive). Alternative actions are indicated in a white _action bar_.
-On some screen a context menu is available by tapping on the three dots in the lower right corner
-of the screen. In the dive list this can also be opened by tapping and holding a dive ot trip
-header.
-
 On Android devices, use the Android Back
 button for "cancel", "discard" or "back" actions. For example, when
 editing dive information, tapping the action button saves the changes while the
@@ -188,7 +166,7 @@ _Subsurface-mobile_ on Android does not use the traditional "hamburger"
 menu button in the top left or right corner of the screen to open menus.
 Instead, _Subsurface-mobile_ uses a
 different user interaction philosophy based on the Kirigami framework
-developed by the Plasma developers. There are two ways to open the main menu:
+developed by the Plasma developers. There are three ways to open the main menu:
 
 - Tap the "hamburger" symbol in the lower left corner of the screen
   (easy to reach for hand held devices)
@@ -205,44 +183,23 @@ version. The iOS screens look similar.
 
 == The Dive List
 
-The _Dive List_ is the heart of _Subsurface-mobile_ because most of the actions
-center around the dives on the dive list. While the dive list is loading from the cloud,
+Most of the actions of _Subsurface-mobile_ center around the dives on the
+dive list. While the dive list is loading from the cloud,
 a message appears at the bottom of the screen, indicating that the cloud is
-being accessed, after which the dive list is shown. Once the list is loaded you can scroll up and down
-through your dive history.
-
-The Dive List consists of two types of entries:
-
-1. *Trip headers*. A trip header is a line describing the year and month during which a dive trip 
-took place, as wel as the geographical area of the trip. The second line in the lefthand image below indicates that a 10-dive trip
-was made to Guinjata, Moçambique during December 2016.
-
-2. *Individual dive records*. Tapping a trip header expands the dive list to show (or hide) the individual dives performed during the trip. Each dive is represented by a dive record. By default the dives during the last trip are listed with older dives at the bottom and recent dives at the top of the list. In the lefthand image below the last dive during
-the Guinjata trip was in the Inhambane Estuary.
+being accessed, after which the dive list is shown. Once the list is loaded you can scroll up and down through your dive history.
+To upload dives from a dive computer, tap the blue action button. If you wish
+to add a dive manually, tap the + button in the action bar (described below).
+Tapping an existing dive on the list brings up a display of the _Details View_ for that dive
+including the dive profile, notes and additional information.
 
 image::mobile-images/Divelist2.jpg["FIGURE: Dive list screen",align="center"]
 
-[[S_View_Dive]]
-== View a dive: the _Details View_
-
-Tapping on a dive in the _Dive List_ brings up a screen with the dive profile
-and many important details about the dive is opened (image on right, above). The dive details usually
-do not fit in a single screen and one needs to scroll the screen to see all the information.
-View other dives by swiping the _Details view_ to the right (for the
-previous dive) or to the left (following dive). Alternatively use a pinch gesture
-to zoom into the profile and tapping with one finger, waiting briefly until
-the profile becomes translucent, and then dragging the finger around
-to pan the profile so the interesting parts are shown. 
-To view the dive
-location on a map viewer (Google Maps on Android, the Google Maps web site
-on iOS) tap the GPS icon on the Action Bar (to the left of the pencil action button in image on the right, above).
-
-To upload dives from a dive computer, tap the blue action button. If you wish
-to add a dive manually, tap the + button in the action bar (described below).
+You can view other dives by swiping the _Details view_ to the right (for the
+previous dive) or to the left (following dive).
 Using the Action Bar, it is also possible to delete the dive (tap the dustbin
-on the Action Bar).
-The context menu (accessible by tapping on the vertical three dots in the lower right corner of the
-screen) offers additional options to move dives between trips and to undo and redo previous actions.
+on the Action Bar) or to view the dive
+location on a map viewer (Google Maps on Android, the Google Maps web site
+on iOS; tap the GPS icon on the Action Bar.).
 
 == Filter the dive list
 
@@ -254,15 +211,7 @@ at the bottom of the dive list to perform filtering of the dive list (see image
 
 image::mobile-images/Filter.jpg["FIGURE: Filter tool",align="center"]
 
-By default, all the dives in the dive log are shown in the dive list. After several years your dive
-log can become quite long and, sometimes, you might like to list only the dives of a particular
-type, e.g. those at a particular dive site or those with a specific buddy or dive master. Use the
-Filter to achieve this. The filter mechanism searches through all the information for each dive,
-looking for one or more key words. Only the dives containing these key words are listed in the dive
-list. Three filter modes exist. "Fulltext" searches all text strings. Selecting "People" lists buddies and
-dive masters, while "Tags" only filters for tags containing the given text. Filters are not case-sensitive.
-To clear the filter, remove the key words from the text box and select the Filter action button to
-switch off filtering. The image above represents a full-text search for dives with the word "nitrox".
+By default, all the dives in the dive log are shown in the dive list. After several years your dive log can become quite long and, sometimes, you might like to list only the dives of a particular type, e.g. those at a particular dive site or those with a specific buddy or dive master. Use the Filter to achieve this. The filter mechanism searches through all the information for each dive, looking for one or more key words. Only the dives containing these key words are listed in the dive list. In the xref:S_Settings[_Settings_] screen there two options that affect the way the filter searches for appropriate information. Firstly, you can select _Match filter case sensitive_ which causes the search of key words to be case sensitive. Secondly, you can select _Include notes in full text filtering_. If this option is not selected, the filter does not search through the dive notes for key words. Selecting the _Filter_ action button brings up a text box at the top of the dive list. Type the key words to be searched for. In the image on the left, the dive list has been filtered for the word "Nitrox" and 265 dives were found containing this word as a tag. For each trip in the dive list the number of dives containing "Nitrox" as a tag is shown. To clear the filter, remove the key words from the text box and select the Filter action button to switch off filtering.
 
 == Viewing the locations of all dives in the dive list
 
@@ -276,10 +225,36 @@ of the different dive sites.
 == Viewing the location of a dive on _Google Maps_
 
 image::mobile-images/Map.jpg["FIGURE: Map of dive site",align="center"]
-In the _Details View_, the Action Bar at the bottom of the screen has a GPS pin on the
+In the _Details View_, the Action Bar at the bottom has a GPS pin on the
 left hand side. Tap that pin and the dive site is shown in Google Maps. Close Google Maps by using the Android _Back_ button
 or tapping on the _Subsurface-mobile_ link in the top left corner on iOS.
 
+Alternatively, the _Details View_ has a button at the top right hand marked
+_Map it_. Tap this button to open Google Maps showing the dive site (image on left).
+
+[[S_View_Dive]]
+== View a dive
+
+When you tap on a dive in the _Dive List_, a new screen with the dive profile
+and many important details about the dive is opened. You can use a pich gesture
+to zoom into the profile, and tapping with one finger, waiting briefly until
+the profile becomes translucent, and then dragging the finger around allows you
+to pan the profile so the interesting parts are shown.
+
+[[S_Edit_Dive]]
+== Edit a particular dive
+
+image::mobile-images/Editdive.jpg["FIGURE: Dive edit screen",align="center"]
+At the bottom of the _Dive Details_ screen the action button is a pencil.
+Tapping the pencil button changes the page and enables edit boxes that allow
+modifying the existing dive information, e.g. adding text to the dive notes
+or changing the names or values of some of the information (see image on left).
+It may be necessary to scroll the window to access all the information.
+At the bottom of the edit screen is a _Save_ action button. Tap this to save
+the new information, after which the dive list screen is
+updated and shown. To cancel any edits, tap the Android _Back_ Button or
+the application back button at the top left of the screen on iOS.
+
 [[S_Add_Dive]]
 == Manually adding a new dive to the dive list
 
@@ -292,14 +267,48 @@ dive computer, the duration, depth and several other bits of information about
 the new dive can be entered. The _Action button_ at the bottom of the screen
 contains a disk symbol. Tap this to save the new dive. To cancel any edits, tap the _Back_ button.
 The left-hand image below shows a screenshot of a dive being created and the right-hand image shows
-the same dive in _Details View_. After editing the dive information, the dive trip information
-needs to be edited as described in the section above on xref:S_Divetrip[Dive trip editing].
-
-This https://www.youtube.com/watch?v=sF8KB_r0rFw[*video-tutorial*] explains how to add information to a
-manually-entered dive.
+the same dive in _Details View_.
 
 image::mobile-images/Manualdive.jpg["FIGURE: Manual dive entry screen",align="center"]
 
+== Copy dive information from one dive to another
+
+When editing dives it is possible to transfer information from one dive to another. For instance,
+when diving with the same buddy and the same equipment configuration during a particular dive trip
+it can be efficient to simply copy all this information from the previous dive into the dive that
+is being edited. Currently a standard list of dive information is copied to the clipboard:
+
+Divemaster, Buddy, Suit, Tags, Cylinders, Weights.
+
+Copy and paste dive information is performed on the Dive List. Long-press on a dive. A panel
+with three icons appears on top the selected dive :
+
+image::mobile-images/CopyDeleteDive.jpg["FIGURE: Copy/Delete dive information",align="center"]
+
+To copy the above information to the clipboard, select the leftmost of the three icons. A "Copy"
+notification briefly appears on the screen. Now long-press the dive into which the copied information
+needs to be pasted. The same three icons appear on the target dive. Select the middle icon. A "Paste"
+notification briefly appears on the screen. This completes the copy-and-paste action. Continue by
+reviewing this new (pasted) information by manually editing the target dive.
+
+To choose what dive details to copy, long-press the copy button. This will open
+up a configuration page where you can toggle the details you want to copy over
+to the destination.
+
+== Deleting a dive
+
+Delete a dive from the dive list by long-pressing a dive
+until a red dustbin appears on the right-hand side (see image above). Tap the dustbin.
+The dive is deleted without asking any confirmation because _Subsurface-mobile_ assumes that the
+combination of a long tap on the dive with another tap on the red dustbin is an unambiguous
+instruction to delete the dive.
+
+To choose what dive details to copy, long-press the copy button. This will open
+up a configuration page where you can toggle the details you want to copy over
+to the destination. By default, the following fields are copied:
+
+image::mobile-images/Delete_undo.jpg["FIGURE: Undo delete dive",align="center"]
+
 [[S_Download]]
 == Download dives from a dive computer
 
@@ -308,9 +317,9 @@ tap _Manage dives ->  Download from DC_. A screen is shown requiring that the us
 the names of the vendor and model of the dive computer. For instance, when using a Shearwater Petrel dive
 computer, the vendor is _Shearwater_ and the Dive computer name is _Petrel_(see image on the left, below).
 *Caveats:* The download feature in smartphones supports only a limited number of dive computers. On
-Android devices these are typically dive computers using a serial USB interface
-using a USB OTG cable or a simple USB C-A adapter on newer devices.
-Android devices also support Bluetooth dive computers that
+Android devices these are typically dive computers using an FTDI interface
+using a USB OTG cable (but this is blocked on some Android devices by OS
+settings). Android devices also support Bluetooth dive computers that
 are supported in _Subsurface_ on the desktop. Both Android and iOS devices allow direct
 download of dive data from a handful of Bluetooth LE enabled dive
 computers. Use the _Vendor name_ and _Dive Computer_ drop-downs to pick the correct
@@ -321,8 +330,14 @@ computers that are not used any more. Achieve this by selecting the option
 _Forget remembered dive computers_ in the xref:S_Settings[_Settings_] menu.
 After all these caveats, let us proceed with download. 
 
-*For USB serial dive computers:*
-This feature is not supported on iOS.
+*For USB FTDI dive computers:*
+This feature is not supported on iOS and on most newer Android devices. It still works on some older
+Android devices (typically Android 7 and older) and is kept enabled for this
+reason. Note: USB cables "normally" used for uploading dives to a
+desktop/laptop computer do NOT work; these
+cables usually have a full-sized ("Type A") male USB plug
+on one end which plugs into the USB port of a desktop/laptop computer. For downloads to a mobile device
+one needs a USB OTG (USB On-The-Go) cable.
 
 [width="100%", frame="None"]
 |=======
@@ -335,7 +350,8 @@ OTG cable usually has a full-size ("Type A") female receptacle at one end which
 accommodates the full-sized male plug
 of the USB cable "normally" used (see image below). This means that two cables are used to connect
 the dive computer to the mobile device. *Not all Android devices support OTG cables*
-but usually all modern Android devices with a USB C plug can be used with a USB A-C adapter.
+and even on some devices that do support those cables in general, as mentioned above _Subsurface-mobile_
+does usually not support cable based downloads, except on some older Android devices.
 |=======
 
 _Subsurface_ remembers the settings for dive computers that
@@ -343,13 +359,7 @@ have been successfully used (image on right, below). These appear
 as buttons under a heading "_Previously used dive computers_".
 Select the appropriate button. Having connected the USB dive computer to the
 _Subsurface_ computer and having selected the appropriate vendor and dive computer,
-ensure that the Connection text box shows the corresponding connection. For a small number of dive
-computers the connection name shows the dive computer vendor, for most only the cable chipset vendor
-(and USB connection number) is shown. Most users of course only connect one USB dive computer to
-their Android device and then things are fairly straight forward. A dialog will pop up and ask if
-you want to use Subsurface-mobile to connect to the device. If you confirm, then Subsurface will
-open to the dive computer download screen with the correct connection selected (and if it can deduce
-the correct dive computer based on the cable used, even that information is already pre-filled).
+ensure that the Connection text box shows "FTDI". 
 
 *For BLUETOOTH/BTLE dive computers:* The process for Bluetooth download is slightly different between Android and iOS.
 In our testing we got the best results on iOS when the dive computer was
@@ -371,8 +381,6 @@ screen for each mode of communication, allowing a choice. Use the _Connection_ v
 two options. In the image on the right, below, there are three buttons labeled "Shearwater Petrel 2". These represent two Shearwater Petrel dive computers, one of which can communicate in both Bluetooth as well as BTLE. The _Connection_
 information indicates that the Petrel with no BTLE is selected.
 
-This https://www.youtube.com/watch?v=4MtQqm4o7bw[*video-tutorial*] demonstrates setting up a Bluetooth connection with an Android device.
-
 *DOWNLOAD:* With communication between dive computer and _Subsurface-mobile_
 having been set up, tap the _Download_ button. Be patient because the download can take a few minutes.
 As a matter of fact, a complete first download from some dive computers can take 45 minutes or longer.
@@ -383,72 +391,9 @@ Each dive has a check-box on the left hand side, used for selecting which dives
 _Subsurface-mobile_ dive list: dives that are not checked are ignored. With the appropriate downloaded dives
 having been checked, tap the button at the bottom left labeled _Accept_. All the selected dives appear on
 the _Subsurface-mobile_ dive list. The downloaded dive information can now be edited as described in the section
-above xref:S_Edit_Dive[Edit the dive information]. After editing the dive information, the dive trip information
-needs to be edited as described in the section above on xref:S_Divetrip[Edit the dive trip information].
-
-This https://www.youtube.com/watch?v=DCi70WZMTws[*video-tutorial*] demonstrates downloading dives from a Bluetooth-equipped dive computer.
-
-[[S_Edit_Dive]]
-== Edit the dive information
-
-image::mobile-images/Editdive.jpg["FIGURE: Dive edit screen",align="center"]
-At the bottom of the _Dive Details_ screen the action button is a pencil.
-Tapping the pencil button changes the page and enables edit boxes that allow
-modifying the existing dive information, e.g. adding text to the dive notes
-or changing the names or values of some of the information (see image on left).
-It may be necessary to scroll the window to access all the information.
-At the bottom of the edit screen is a _Save_ action button. Tap this to save
-the new information, after which the dive list screen is
-updated and shown. To cancel any edits, tap the Android _Back_ Button or
-the application back button at the top left of the screen on iOS.
-
-This https://www.youtube.com/watch?v=pE3ujzGw_7o[*video-tutorial*] explains how to add information about a dive.
-
-[[S_Divetrip]]
-== Edit the dive trip information
-
-When a new dive(s) is entered manually or downloaded from dive computer, a trip header is created at the
-top of the dive list only showing the month and the year of the dive trip as well as the number of dives
-during the trip (image on left below, showing a trip header with "May 2018", the trip comprising two dives).
-You would probably like to include information about the place
-where the trip took place, e.g. "Channel Islands" or the dive charter company used. In this case long-press
-the dive trip header to activate the context menu. Select the option "Edit trip details" to open a panel
-for typing information about the trip (image on right, below). Having provided the required information,
-tap the _Save_ action button at the bottom of the screen. This returns you to the dive list, showing some of
-the dive trip information that has just been provided.
-
-image::mobile-images/TripDetails.jpg["FIGURE: Edit trip details",align="center"]
-
-// == Copy dive information from one dive to another
-// 
-// When editing dives it is possible to transfer information from one dive to another. For instance,
-// when diving with the same buddy and the same equipment configuration during a particular dive trip
-// it can be efficient to simply copy all this information from the previous dive into the dive that
-// is being edited. Currently a standard list of dive information is copied to the clipboard:
-// 
-// Divemaster, Buddy, Suit, Tags, Cylinders, Weights.
-// 
-// Copy and paste dive information is performed on the Dive List. Long-press on a dive. A panel
-// with three icons appears on top the selected dive :
-// 
-// image::mobile-images/CopyDeleteDive.jpg["FIGURE: Copy/Delete dive information",align="center"]
-// 
-// To copy the above information to the clipboard, select the leftmost of the three icons. A "Copy"
-// notification briefly appears on the screen. Now long-press the dive into which the copied information
-// needs to be pasted. The same three icons appear on the target dive. Select the middle icon. A "Paste"
-// notification briefly appears on the screen. This completes the copy-and-paste action. Continue by
-// reviewing this new (pasted) information by manually editing the target dive.
-// 
-// To choose what dive details to copy, long-press the copy button. This will open
-// up a configuration page where you can toggle the details you want to copy over
-// to the destination.
-
-== Deleting a dive
+above xref:S_Edit_Dive[Edit a dive].
 
-Delete a dive from the dive list by long-pressing a dive and selecting delete in the context menu.
-If the wrong dive was deleted by mistake you can easily undo the operation by using the context menu.
-
-image::mobile-images/Delete_undo.jpg["FIGURE: Undo delete dive",align="center"]
+image::mobile-images/DC-Download.jpg["FIGURE: DC download screen",align="center"]
 
 == Dive log management
 
@@ -583,6 +528,10 @@ Select the appropriate color theme by dragging the appropriate slider on the rig
 On the left is the dive list after selecting the Pink theme.
 |=======
 
+=== Configuring the GPS webservice
+
+The Settings screen allows one to set up the way in which GPS positions are collected during dives. See the section on xref:S_ConfigureGPS[Configuring the GPS service].
+
 === Activating the Developer sub-menu
 
 The information in the subsurface.log generated while running _Subsurface-mobile_, plus some additional information for understanding the screen rendering of dive information as well as the way in which _Subsurface-mobile_ processed information during a specific occasion while running the app (see section below) is available through a _Developer_ menu at run time. Activate (or deactivate) this menu item on the Main Menu by dragging the slider switch in the Settings screen.
diff --git a/Documentation/mobile-manual-v3.html.git b/Documentation/mobile-manual-v3.html.git
index 28eb03154..0962fd61c 100644
--- a/Documentation/mobile-manual-v3.html.git
+++ b/Documentation/mobile-manual-v3.html.git
@@ -1,427 +1,564 @@
-<?xml version="1.0" encoding="UTF-8"?>
-<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.1//EN"
-    "http://www.w3.org/TR/xhtml11/DTD/xhtml11.dtd">
-<html xmlns="http://www.w3.org/1999/xhtml" xml:lang="en">
+<!DOCTYPE html>
+<html lang="en">
 <head>
-<meta http-equiv="Content-Type" content="application/xhtml+xml; charset=UTF-8" />
-<meta name="generator" content="AsciiDoc 8.6.10" />
-<title></title>
-<style type="text/css">
-/*
- * compact_subsurface.css, a special style sheet for Subsurface,
- *  modified by Willem Ferguson and derived from:
- *		compact.css, version 1.3 by Alex Efros <powerman@powerman.name>
- * Licence: Public Domain
- *
- * Usage: asciidoc -a theme=compact_subsurface ...
- */
-
-*   { padding: 0;  margin: 0; }
-img { border: 0; margin: 15px; }
-
-/*** Layout ***/
-
-body                        { margin: 10px 20px; }
-#header br                  { display: none; }
-#revnumber                  { display: block; }
-#toc                        { margin: 1em 0; }
-.toclevel2                  { margin-left: 1em; }
-.toclevel3		    { margin-left: 2em; }
-#footer                     { margin-top: 2em; }
-
-#preamble .sectionbody,
-h2,
-h3,
-h4,
-h5                          { margin: 1em 0 0 0; }
-
-.admonitionblock,
-.listingblock,
-.sidebarblock,
-.exampleblock,
-.tableblock,
-.literalblock               { margin: 1em 0; }
-.admonitionblock td.icon    { padding-right: 0.5em; }
-.admonitionblock td.content { padding-left:  0.5em; }
-.listingblock .content      { padding: 0.5em; }
-.sidebarblock > .content    { padding: 0.5em; }
-.exampleblock > .content    { padding: 0 0.5em; }
-.tableblock caption         { padding: 0 0 0.5em 0; }
-.tableblock thead th,
-.tableblock tbody td,
-.tableblock tfoot td        { padding: 0 0.5em; }
-.quoteblock                 { padding: 0 2.0em; }
-
-.paragraph                  { margin: 1em 0 0 0; }
-.sidebarblock .paragraph:first-child,
-.exampleblock .paragraph:first-child,
-.admonitionblock .paragraph:first-child  { margin: 0; }
-
-   .ulist,    .olist,    .dlist,    .hdlist,    .qlist   { margin: 1em 0; }
-li .ulist, li .olist, li .dlist, li .hdlist, li .qlist,
-dd .ulist, dd .olist, dd .dlist, dd .hdlist, dd .qlist   { margin: 0; }
-ul                          { margin-left: 1.5em; }
-ol                          { margin-left: 2em; }
-dd                          { margin-left: 3em; }
-td.hdlist1                  { padding-right: 1em; }
-
-/*** Fonts ***/
-
-body                        { font-family: Verdana, sans-serif; }
-#header                     { font-family: Arial,   sans-serif; }
-#header h1                  { font-family: Arial,   sans-serif; }
-#footer                     { font-family: Georgia, serif;      }
-#email                      { font-size: 0.85em; }
-#revnumber                  { font-size: 0.75em; }
-#toc                        { font-size: 0.9em;  }
-#toctitle                   { font-weight: bold; }
-#footer                     { font-size: 0.8em; }
-
-h2, h3, h4, h5, .title      { font-family: Arial,   sans-serif; }
-h2                          { font-size: 1.5em; }
-.sectionbody                { font-size: 0.85em; }
-.sectionbody .sectionbody   { font-size: inherit; }
-h3                          { font-size: 159%; } /* 1.35em */
-h4                          { font-size: 141%; } /* 1.2em */
-h5                          { font-size: 118%; } /* 1em */
-.title                      { font-size: 106%;   /* 0.9em */
-			      font-weight: bold;
-			    }
-
-tt, .monospaced             { font-family: monospace; font-size: 106%; } /* 0.9em */
-dt, td.hdlist1, .qlist em   { font-family: Times New Roman, serif;
-			      font-size: 118%;   /* 1em */
-			      font-style: italic;
-			    }
-.tableblock tfoot td        { font-weight: bold; }
-
-/*** Colors and Backgrounds ***/
-
-h1                          { color: #527bbd; border-bottom: 2px solid silver; }
-#footer                     {                 border-top:    2px solid silver; }
-
-h2                          { color: #527bbd; border-bottom: 2px solid silver; }
-h3                          { color: #5D7EAE; border-bottom: 2px solid silver; }
-h3                          { display: inline-block; }
-h4,h5                       { color: #5D7EAE; }
-
-.admonitionblock td.content { border-left: 2px solid silver; }
-.listingblock .content      { background: #f4f4f4;   border: 1px solid silver; border-left: 5px solid #e0e0e0; }
-.sidebarblock > .content    { background: #ffffee;   border: 1px solid silver; border-left: 5px solid #e0e0e0; }
-.exampleblock > .content    {                   border-left: 2px solid silver; }
-.quoteblock                 {                   border-left: 5px solid #e0e0e0; }
-.tableblock table {
-    border-collapse: collapse;
-    border-width: 3px;
-    border-color: #527bbd;
-}
-.tableblock table[frame=hsides] { border-style: solid none; }
-.tableblock table[frame=border] { border-style: solid;      }
-.tableblock table[frame=void]   { border-style: none;       }
-.tableblock table[frame=vsides] { border-style: none solid; }
-.tableblock table[rules=all] tbody tr *,
-.tableblock table[rules=rows] tbody tr * {
-    border-top: 1px solid #527bbd;
-}
-.tableblock table[rules=all] tr *,
-.tableblock table[rules=cols] tr * {
-    border-left: 1px solid #527bbd;
-}
-.tableblock table tbody tr:first-child * {
-    border-top: 1px solid white; /* none don't work here... %-[] */
-}
-.tableblock table tr *:first-child {
-    border-left: none;
-}
-.tableblock table[frame] thead tr *,
-.tableblock table[frame] thead tr * {
-    border-top: 1px solid white;
-    border-bottom: 2px solid #527bbd;
-}
-.tableblock table tr td p.table,
-.tableblock table tr td p.table * {
-    border: 0px;
-}
-
-tt, .monospaced             { color: navy; }
-
-li                          { color: #a0a0a0; }
-li > *                      { color: black; }
-
-span.aqua { color: aqua; }
-span.black { color: black; }
-span.blue { color: blue; }
-span.fuchsia { color: fuchsia; }
-span.gray { color: gray; }
-span.green { color: green; }
-span.lime { color: lime; }
-span.maroon { color: maroon; }
-span.navy { color: navy; }
-span.olive { color: olive; }
-span.purple { color: purple; }
-span.red { color: red; }
-span.silver { color: silver; }
-span.teal { color: teal; }
-span.white { color: white; }
-span.yellow { color: yellow; }
-
-span.aqua-background { background: aqua; }
-span.black-background { background: black; }
-span.blue-background { background: blue; }
-span.fuchsia-background { background: fuchsia; }
-span.gray-background { background: gray; }
-span.green-background { background: green; }
-span.lime-background { background: lime; }
-span.maroon-background { background: maroon; }
-span.navy-background { background: navy; }
-span.olive-background { background: olive; }
-span.purple-background { background: purple; }
-span.red-background { background: red; }
-span.silver-background { background: silver; }
-span.teal-background { background: teal; }
-span.white-background { background: white; }
-span.yellow-background { background: yellow; }
-
-span.big { font-size: 2em; }
-span.small { font-size: 0.6em; }
-
-span.underline { text-decoration: underline; }
-span.overline { text-decoration: overline; }
-span.line-through { text-decoration: line-through; }
-
-/*** Misc ***/
-
-.admonitionblock td.icon    { vertical-align: top; }
-.attribution                { text-align: right; }
-
-ul                          { list-style-type: disc; }
-ol.arabic                   { list-style-type: decimal; }
-ol.loweralpha               { list-style-type: lower-alpha; }
-ol.upperalpha               { list-style-type: upper-alpha; }
-ol.lowerroman               { list-style-type: lower-roman; }
-ol.upperroman               { list-style-type: upper-roman; }
-.hdlist td                  { vertical-align: top; }
-
-
+<meta charset="UTF-8">
+<meta http-equiv="X-UA-Compatible" content="IE=edge">
+<meta name="viewport" content="width=device-width, initial-scale=1.0">
+<meta name="generator" content="Asciidoctor 2.0.10">
+<title>Installing Subsurface-mobile on your mobile device</title>
+<link rel="stylesheet" href="https://fonts.googleapis.com/css?family=Open+Sans:300,300italic,400,400italic,600,600italic%7CNoto+Serif:400,400italic,700,700italic%7CDroid+Sans+Mono:400,700">
+<style>
+/* Asciidoctor default stylesheet | MIT License | https://asciidoctor.org */
+/* Uncomment @import statement to use as custom stylesheet */
+/*@import "https://fonts.googleapis.com/css?family=Open+Sans:300,300italic,400,400italic,600,600italic%7CNoto+Serif:400,400italic,700,700italic%7CDroid+Sans+Mono:400,700";*/
+article,aside,details,figcaption,figure,footer,header,hgroup,main,nav,section{display:block}
+audio,video{display:inline-block}
+audio:not([controls]){display:none;height:0}
+html{font-family:sans-serif;-ms-text-size-adjust:100%;-webkit-text-size-adjust:100%}
+a{background:none}
+a:focus{outline:thin dotted}
+a:active,a:hover{outline:0}
+h1{font-size:2em;margin:.67em 0}
+abbr[title]{border-bottom:1px dotted}
+b,strong{font-weight:bold}
+dfn{font-style:italic}
+hr{-moz-box-sizing:content-box;box-sizing:content-box;height:0}
+mark{background:#ff0;color:#000}
+code,kbd,pre,samp{font-family:monospace;font-size:1em}
+pre{white-space:pre-wrap}
+q{quotes:"\201C" "\201D" "\2018" "\2019"}
+small{font-size:80%}
+sub,sup{font-size:75%;line-height:0;position:relative;vertical-align:baseline}
+sup{top:-.5em}
+sub{bottom:-.25em}
+img{border:0}
+svg:not(:root){overflow:hidden}
+figure{margin:0}
+fieldset{border:1px solid silver;margin:0 2px;padding:.35em .625em .75em}
+legend{border:0;padding:0}
+button,input,select,textarea{font-family:inherit;font-size:100%;margin:0}
+button,input{line-height:normal}
+button,select{text-transform:none}
+button,html input[type="button"],input[type="reset"],input[type="submit"]{-webkit-appearance:button;cursor:pointer}
+button[disabled],html input[disabled]{cursor:default}
+input[type="checkbox"],input[type="radio"]{box-sizing:border-box;padding:0}
+button::-moz-focus-inner,input::-moz-focus-inner{border:0;padding:0}
+textarea{overflow:auto;vertical-align:top}
+table{border-collapse:collapse;border-spacing:0}
+*,*::before,*::after{-moz-box-sizing:border-box;-webkit-box-sizing:border-box;box-sizing:border-box}
+html,body{font-size:100%}
+body{background:#fff;color:rgba(0,0,0,.8);padding:0;margin:0;font-family:"Noto Serif","DejaVu Serif",serif;font-weight:400;font-style:normal;line-height:1;position:relative;cursor:auto;tab-size:4;-moz-osx-font-smoothing:grayscale;-webkit-font-smoothing:antialiased}
+a:hover{cursor:pointer}
+img,object,embed{max-width:100%;height:auto}
+object,embed{height:100%}
+img{-ms-interpolation-mode:bicubic}
+.left{float:left!important}
+.right{float:right!important}
+.text-left{text-align:left!important}
+.text-right{text-align:right!important}
+.text-center{text-align:center!important}
+.text-justify{text-align:justify!important}
+.hide{display:none}
+img,object,svg{display:inline-block;vertical-align:middle}
+textarea{height:auto;min-height:50px}
+select{width:100%}
+.center{margin-left:auto;margin-right:auto}
+.stretch{width:100%}
+.subheader,.admonitionblock td.content>.title,.audioblock>.title,.exampleblock>.title,.imageblock>.title,.listingblock>.title,.literalblock>.title,.stemblock>.title,.openblock>.title,.paragraph>.title,.quoteblock>.title,table.tableblock>.title,.verseblock>.title,.videoblock>.title,.dlist>.title,.olist>.title,.ulist>.title,.qlist>.title,.hdlist>.title{line-height:1.45;color:#7a2518;font-weight:400;margin-top:0;margin-bottom:.25em}
+div,dl,dt,dd,ul,ol,li,h1,h2,h3,#toctitle,.sidebarblock>.content>.title,h4,h5,h6,pre,form,p,blockquote,th,td{margin:0;padding:0;direction:ltr}
+a{color:#2156a5;text-decoration:underline;line-height:inherit}
+a:hover,a:focus{color:#1d4b8f}
+a img{border:0}
+p{font-family:inherit;font-weight:400;font-size:1em;line-height:1.6;margin-bottom:1.25em;text-rendering:optimizeLegibility}
+p aside{font-size:.875em;line-height:1.35;font-style:italic}
+h1,h2,h3,#toctitle,.sidebarblock>.content>.title,h4,h5,h6{font-family:"Open Sans","DejaVu Sans",sans-serif;font-weight:300;font-style:normal;color:#ba3925;text-rendering:optimizeLegibility;margin-top:1em;margin-bottom:.5em;line-height:1.0125em}
+h1 small,h2 small,h3 small,#toctitle small,.sidebarblock>.content>.title small,h4 small,h5 small,h6 small{font-size:60%;color:#e99b8f;line-height:0}
+h1{font-size:2.125em}
+h2{font-size:1.6875em}
+h3,#toctitle,.sidebarblock>.content>.title{font-size:1.375em}
+h4,h5{font-size:1.125em}
+h6{font-size:1em}
+hr{border:solid #dddddf;border-width:1px 0 0;clear:both;margin:1.25em 0 1.1875em;height:0}
+em,i{font-style:italic;line-height:inherit}
+strong,b{font-weight:bold;line-height:inherit}
+small{font-size:60%;line-height:inherit}
+code{font-family:"Droid Sans Mono","DejaVu Sans Mono",monospace;font-weight:400;color:rgba(0,0,0,.9)}
+ul,ol,dl{font-size:1em;line-height:1.6;margin-bottom:1.25em;list-style-position:outside;font-family:inherit}
+ul,ol{margin-left:1.5em}
+ul li ul,ul li ol{margin-left:1.25em;margin-bottom:0;font-size:1em}
+ul.square li ul,ul.circle li ul,ul.disc li ul{list-style:inherit}
+ul.square{list-style-type:square}
+ul.circle{list-style-type:circle}
+ul.disc{list-style-type:disc}
+ol li ul,ol li ol{margin-left:1.25em;margin-bottom:0}
+dl dt{margin-bottom:.3125em;font-weight:bold}
+dl dd{margin-bottom:1.25em}
+abbr,acronym{text-transform:uppercase;font-size:90%;color:rgba(0,0,0,.8);border-bottom:1px dotted #ddd;cursor:help}
+abbr{text-transform:none}
+blockquote{margin:0 0 1.25em;padding:.5625em 1.25em 0 1.1875em;border-left:1px solid #ddd}
+blockquote cite{display:block;font-size:.9375em;color:rgba(0,0,0,.6)}
+blockquote cite::before{content:"\2014 \0020"}
+blockquote cite a,blockquote cite a:visited{color:rgba(0,0,0,.6)}
+blockquote,blockquote p{line-height:1.6;color:rgba(0,0,0,.85)}
+@media screen and (min-width:768px){h1,h2,h3,#toctitle,.sidebarblock>.content>.title,h4,h5,h6{line-height:1.2}
+h1{font-size:2.75em}
+h2{font-size:2.3125em}
+h3,#toctitle,.sidebarblock>.content>.title{font-size:1.6875em}
+h4{font-size:1.4375em}}
+table{background:#fff;margin-bottom:1.25em;border:solid 1px #dedede}
+table thead,table tfoot{background:#f7f8f7}
+table thead tr th,table thead tr td,table tfoot tr th,table tfoot tr td{padding:.5em .625em .625em;font-size:inherit;color:rgba(0,0,0,.8);text-align:left}
+table tr th,table tr td{padding:.5625em .625em;font-size:inherit;color:rgba(0,0,0,.8)}
+table tr.even,table tr.alt{background:#f8f8f7}
+table thead tr th,table tfoot tr th,table tbody tr td,table tr td,table tfoot tr td{display:table-cell;line-height:1.6}
+h1,h2,h3,#toctitle,.sidebarblock>.content>.title,h4,h5,h6{line-height:1.2;word-spacing:-.05em}
+h1 strong,h2 strong,h3 strong,#toctitle strong,.sidebarblock>.content>.title strong,h4 strong,h5 strong,h6 strong{font-weight:400}
+.clearfix::before,.clearfix::after,.float-group::before,.float-group::after{content:" ";display:table}
+.clearfix::after,.float-group::after{clear:both}
+:not(pre):not([class^=L])>code{font-size:.9375em;font-style:normal!important;letter-spacing:0;padding:.1em .5ex;word-spacing:-.15em;background:#f7f7f8;-webkit-border-radius:4px;border-radius:4px;line-height:1.45;text-rendering:optimizeSpeed;word-wrap:break-word}
+:not(pre)>code.nobreak{word-wrap:normal}
+:not(pre)>code.nowrap{white-space:nowrap}
+pre{color:rgba(0,0,0,.9);font-family:"Droid Sans Mono","DejaVu Sans Mono",monospace;line-height:1.45;text-rendering:optimizeSpeed}
+pre code,pre pre{color:inherit;font-size:inherit;line-height:inherit}
+pre>code{display:block}
+pre.nowrap,pre.nowrap pre{white-space:pre;word-wrap:normal}
+em em{font-style:normal}
+strong strong{font-weight:400}
+.keyseq{color:rgba(51,51,51,.8)}
+kbd{font-family:"Droid Sans Mono","DejaVu Sans Mono",monospace;display:inline-block;color:rgba(0,0,0,.8);font-size:.65em;line-height:1.45;background:#f7f7f7;border:1px solid #ccc;-webkit-border-radius:3px;border-radius:3px;-webkit-box-shadow:0 1px 0 rgba(0,0,0,.2),0 0 0 .1em white inset;box-shadow:0 1px 0 rgba(0,0,0,.2),0 0 0 .1em #fff inset;margin:0 .15em;padding:.2em .5em;vertical-align:middle;position:relative;top:-.1em;white-space:nowrap}
+.keyseq kbd:first-child{margin-left:0}
+.keyseq kbd:last-child{margin-right:0}
+.menuseq,.menuref{color:#000}
+.menuseq b:not(.caret),.menuref{font-weight:inherit}
+.menuseq{word-spacing:-.02em}
+.menuseq b.caret{font-size:1.25em;line-height:.8}
+.menuseq i.caret{font-weight:bold;text-align:center;width:.45em}
+b.button::before,b.button::after{position:relative;top:-1px;font-weight:400}
+b.button::before{content:"[";padding:0 3px 0 2px}
+b.button::after{content:"]";padding:0 2px 0 3px}
+p a>code:hover{color:rgba(0,0,0,.9)}
+#header,#content,#footnotes,#footer{width:100%;margin-left:auto;margin-right:auto;margin-top:0;margin-bottom:0;max-width:62.5em;*zoom:1;position:relative;padding-left:.9375em;padding-right:.9375em}
+#header::before,#header::after,#content::before,#content::after,#footnotes::before,#footnotes::after,#footer::before,#footer::after{content:" ";display:table}
+#header::after,#content::after,#footnotes::after,#footer::after{clear:both}
+#content{margin-top:1.25em}
+#content::before{content:none}
+#header>h1:first-child{color:rgba(0,0,0,.85);margin-top:2.25rem;margin-bottom:0}
+#header>h1:first-child+#toc{margin-top:8px;border-top:1px solid #dddddf}
+#header>h1:only-child,body.toc2 #header>h1:nth-last-child(2){border-bottom:1px solid #dddddf;padding-bottom:8px}
+#header .details{border-bottom:1px solid #dddddf;line-height:1.45;padding-top:.25em;padding-bottom:.25em;padding-left:.25em;color:rgba(0,0,0,.6);display:-ms-flexbox;display:-webkit-flex;display:flex;-ms-flex-flow:row wrap;-webkit-flex-flow:row wrap;flex-flow:row wrap}
+#header .details span:first-child{margin-left:-.125em}
+#header .details span.email a{color:rgba(0,0,0,.85)}
+#header .details br{display:none}
+#header .details br+span::before{content:"\00a0\2013\00a0"}
+#header .details br+span.author::before{content:"\00a0\22c5\00a0";color:rgba(0,0,0,.85)}
+#header .details br+span#revremark::before{content:"\00a0|\00a0"}
+#header #revnumber{text-transform:capitalize}
+#header #revnumber::after{content:"\00a0"}
+#content>h1:first-child:not([class]){color:rgba(0,0,0,.85);border-bottom:1px solid #dddddf;padding-bottom:8px;margin-top:0;padding-top:1rem;margin-bottom:1.25rem}
+#toc{border-bottom:1px solid #e7e7e9;padding-bottom:.5em}
+#toc>ul{margin-left:.125em}
+#toc ul.sectlevel0>li>a{font-style:italic}
+#toc ul.sectlevel0 ul.sectlevel1{margin:.5em 0}
+#toc ul{font-family:"Open Sans","DejaVu Sans",sans-serif;list-style-type:none}
+#toc li{line-height:1.3334;margin-top:.3334em}
+#toc a{text-decoration:none}
+#toc a:active{text-decoration:underline}
+#toctitle{color:#7a2518;font-size:1.2em}
+@media screen and (min-width:768px){#toctitle{font-size:1.375em}
+body.toc2{padding-left:15em;padding-right:0}
+#toc.toc2{margin-top:0!important;background:#f8f8f7;position:fixed;width:15em;left:0;top:0;border-right:1px solid #e7e7e9;border-top-width:0!important;border-bottom-width:0!important;z-index:1000;padding:1.25em 1em;height:100%;overflow:auto}
+#toc.toc2 #toctitle{margin-top:0;margin-bottom:.8rem;font-size:1.2em}
+#toc.toc2>ul{font-size:.9em;margin-bottom:0}
+#toc.toc2 ul ul{margin-left:0;padding-left:1em}
+#toc.toc2 ul.sectlevel0 ul.sectlevel1{padding-left:0;margin-top:.5em;margin-bottom:.5em}
+body.toc2.toc-right{padding-left:0;padding-right:15em}
+body.toc2.toc-right #toc.toc2{border-right-width:0;border-left:1px solid #e7e7e9;left:auto;right:0}}
+@media screen and (min-width:1280px){body.toc2{padding-left:20em;padding-right:0}
+#toc.toc2{width:20em}
+#toc.toc2 #toctitle{font-size:1.375em}
+#toc.toc2>ul{font-size:.95em}
+#toc.toc2 ul ul{padding-left:1.25em}
+body.toc2.toc-right{padding-left:0;padding-right:20em}}
+#content #toc{border-style:solid;border-width:1px;border-color:#e0e0dc;margin-bottom:1.25em;padding:1.25em;background:#f8f8f7;-webkit-border-radius:4px;border-radius:4px}
+#content #toc>:first-child{margin-top:0}
+#content #toc>:last-child{margin-bottom:0}
+#footer{max-width:100%;background:rgba(0,0,0,.8);padding:1.25em}
+#footer-text{color:rgba(255,255,255,.8);line-height:1.44}
+#content{margin-bottom:.625em}
+.sect1{padding-bottom:.625em}
+@media screen and (min-width:768px){#content{margin-bottom:1.25em}
+.sect1{padding-bottom:1.25em}}
+.sect1:last-child{padding-bottom:0}
+.sect1+.sect1{border-top:1px solid #e7e7e9}
+#content h1>a.anchor,h2>a.anchor,h3>a.anchor,#toctitle>a.anchor,.sidebarblock>.content>.title>a.anchor,h4>a.anchor,h5>a.anchor,h6>a.anchor{position:absolute;z-index:1001;width:1.5ex;margin-left:-1.5ex;display:block;text-decoration:none!important;visibility:hidden;text-align:center;font-weight:400}
+#content h1>a.anchor::before,h2>a.anchor::before,h3>a.anchor::before,#toctitle>a.anchor::before,.sidebarblock>.content>.title>a.anchor::before,h4>a.anchor::before,h5>a.anchor::before,h6>a.anchor::before{content:"\00A7";font-size:.85em;display:block;padding-top:.1em}
+#content h1:hover>a.anchor,#content h1>a.anchor:hover,h2:hover>a.anchor,h2>a.anchor:hover,h3:hover>a.anchor,#toctitle:hover>a.anchor,.sidebarblock>.content>.title:hover>a.anchor,h3>a.anchor:hover,#toctitle>a.anchor:hover,.sidebarblock>.content>.title>a.anchor:hover,h4:hover>a.anchor,h4>a.anchor:hover,h5:hover>a.anchor,h5>a.anchor:hover,h6:hover>a.anchor,h6>a.anchor:hover{visibility:visible}
+#content h1>a.link,h2>a.link,h3>a.link,#toctitle>a.link,.sidebarblock>.content>.title>a.link,h4>a.link,h5>a.link,h6>a.link{color:#ba3925;text-decoration:none}
+#content h1>a.link:hover,h2>a.link:hover,h3>a.link:hover,#toctitle>a.link:hover,.sidebarblock>.content>.title>a.link:hover,h4>a.link:hover,h5>a.link:hover,h6>a.link:hover{color:#a53221}
+details,.audioblock,.imageblock,.literalblock,.listingblock,.stemblock,.videoblock{margin-bottom:1.25em}
+details>summary:first-of-type{cursor:pointer;display:list-item;outline:none;margin-bottom:.75em}
+.admonitionblock td.content>.title,.audioblock>.title,.exampleblock>.title,.imageblock>.title,.listingblock>.title,.literalblock>.title,.stemblock>.title,.openblock>.title,.paragraph>.title,.quoteblock>.title,table.tableblock>.title,.verseblock>.title,.videoblock>.title,.dlist>.title,.olist>.title,.ulist>.title,.qlist>.title,.hdlist>.title{text-rendering:optimizeLegibility;text-align:left;font-family:"Noto Serif","DejaVu Serif",serif;font-size:1rem;font-style:italic}
+table.tableblock.fit-content>caption.title{white-space:nowrap;width:0}
+.paragraph.lead>p,#preamble>.sectionbody>[class="paragraph"]:first-of-type p{font-size:1.21875em;line-height:1.6;color:rgba(0,0,0,.85)}
+table.tableblock #preamble>.sectionbody>[class="paragraph"]:first-of-type p{font-size:inherit}
+.admonitionblock>table{border-collapse:separate;border:0;background:none;width:100%}
+.admonitionblock>table td.icon{text-align:center;width:80px}
+.admonitionblock>table td.icon img{max-width:none}
+.admonitionblock>table td.icon .title{font-weight:bold;font-family:"Open Sans","DejaVu Sans",sans-serif;text-transform:uppercase}
+.admonitionblock>table td.content{padding-left:1.125em;padding-right:1.25em;border-left:1px solid #dddddf;color:rgba(0,0,0,.6)}
+.admonitionblock>table td.content>:last-child>:last-child{margin-bottom:0}
+.exampleblock>.content{border-style:solid;border-width:1px;border-color:#e6e6e6;margin-bottom:1.25em;padding:1.25em;background:#fff;-webkit-border-radius:4px;border-radius:4px}
+.exampleblock>.content>:first-child{margin-top:0}
+.exampleblock>.content>:last-child{margin-bottom:0}
+.sidebarblock{border-style:solid;border-width:1px;border-color:#dbdbd6;margin-bottom:1.25em;padding:1.25em;background:#f3f3f2;-webkit-border-radius:4px;border-radius:4px}
+.sidebarblock>:first-child{margin-top:0}
+.sidebarblock>:last-child{margin-bottom:0}
+.sidebarblock>.content>.title{color:#7a2518;margin-top:0;text-align:center}
+.exampleblock>.content>:last-child>:last-child,.exampleblock>.content .olist>ol>li:last-child>:last-child,.exampleblock>.content .ulist>ul>li:last-child>:last-child,.exampleblock>.content .qlist>ol>li:last-child>:last-child,.sidebarblock>.content>:last-child>:last-child,.sidebarblock>.content .olist>ol>li:last-child>:last-child,.sidebarblock>.content .ulist>ul>li:last-child>:last-child,.sidebarblock>.content .qlist>ol>li:last-child>:last-child{margin-bottom:0}
+.literalblock pre,.listingblock>.content>pre{-webkit-border-radius:4px;border-radius:4px;word-wrap:break-word;overflow-x:auto;padding:1em;font-size:.8125em}
+@media screen and (min-width:768px){.literalblock pre,.listingblock>.content>pre{font-size:.90625em}}
+@media screen and (min-width:1280px){.literalblock pre,.listingblock>.content>pre{font-size:1em}}
+.literalblock pre,.listingblock>.content>pre:not(.highlight),.listingblock>.content>pre[class="highlight"],.listingblock>.content>pre[class^="highlight "]{background:#f7f7f8}
+.literalblock.output pre{color:#f7f7f8;background:rgba(0,0,0,.9)}
+.listingblock>.content{position:relative}
+.listingblock code[data-lang]::before{display:none;content:attr(data-lang);position:absolute;font-size:.75em;top:.425rem;right:.5rem;line-height:1;text-transform:uppercase;color:inherit;opacity:.5}
+.listingblock:hover code[data-lang]::before{display:block}
+.listingblock.terminal pre .command::before{content:attr(data-prompt);padding-right:.5em;color:inherit;opacity:.5}
+.listingblock.terminal pre .command:not([data-prompt])::before{content:"$"}
+.listingblock pre.highlightjs{padding:0}
+.listingblock pre.highlightjs>code{padding:1em;-webkit-border-radius:4px;border-radius:4px}
+.listingblock pre.prettyprint{border-width:0}
+.prettyprint{background:#f7f7f8}
+pre.prettyprint .linenums{line-height:1.45;margin-left:2em}
+pre.prettyprint li{background:none;list-style-type:inherit;padding-left:0}
+pre.prettyprint li code[data-lang]::before{opacity:1}
+pre.prettyprint li:not(:first-child) code[data-lang]::before{display:none}
+table.linenotable{border-collapse:separate;border:0;margin-bottom:0;background:none}
+table.linenotable td[class]{color:inherit;vertical-align:top;padding:0;line-height:inherit;white-space:normal}
+table.linenotable td.code{padding-left:.75em}
+table.linenotable td.linenos{border-right:1px solid currentColor;opacity:.35;padding-right:.5em}
+pre.pygments .lineno{border-right:1px solid currentColor;opacity:.35;display:inline-block;margin-right:.75em}
+pre.pygments .lineno::before{content:"";margin-right:-.125em}
+.quoteblock{margin:0 1em 1.25em 1.5em;display:table}
+.quoteblock:not(.excerpt)>.title{margin-left:-1.5em;margin-bottom:.75em}
+.quoteblock blockquote,.quoteblock p{color:rgba(0,0,0,.85);font-size:1.15rem;line-height:1.75;word-spacing:.1em;letter-spacing:0;font-style:italic;text-align:justify}
+.quoteblock blockquote{margin:0;padding:0;border:0}
+.quoteblock blockquote::before{content:"\201c";float:left;font-size:2.75em;font-weight:bold;line-height:.6em;margin-left:-.6em;color:#7a2518;text-shadow:0 1px 2px rgba(0,0,0,.1)}
+.quoteblock blockquote>.paragraph:last-child p{margin-bottom:0}
+.quoteblock .attribution{margin-top:.75em;margin-right:.5ex;text-align:right}
+.verseblock{margin:0 1em 1.25em}
+.verseblock pre{font-family:"Open Sans","DejaVu Sans",sans;font-size:1.15rem;color:rgba(0,0,0,.85);font-weight:300;text-rendering:optimizeLegibility}
+.verseblock pre strong{font-weight:400}
+.verseblock .attribution{margin-top:1.25rem;margin-left:.5ex}
+.quoteblock .attribution,.verseblock .attribution{font-size:.9375em;line-height:1.45;font-style:italic}
+.quoteblock .attribution br,.verseblock .attribution br{display:none}
+.quoteblock .attribution cite,.verseblock .attribution cite{display:block;letter-spacing:-.025em;color:rgba(0,0,0,.6)}
+.quoteblock.abstract blockquote::before,.quoteblock.excerpt blockquote::before,.quoteblock .quoteblock blockquote::before{display:none}
+.quoteblock.abstract blockquote,.quoteblock.abstract p,.quoteblock.excerpt blockquote,.quoteblock.excerpt p,.quoteblock .quoteblock blockquote,.quoteblock .quoteblock p{line-height:1.6;word-spacing:0}
+.quoteblock.abstract{margin:0 1em 1.25em;display:block}
+.quoteblock.abstract>.title{margin:0 0 .375em;font-size:1.15em;text-align:center}
+.quoteblock.excerpt>blockquote,.quoteblock .quoteblock{padding:0 0 .25em 1em;border-left:.25em solid #dddddf}
+.quoteblock.excerpt,.quoteblock .quoteblock{margin-left:0}
+.quoteblock.excerpt blockquote,.quoteblock.excerpt p,.quoteblock .quoteblock blockquote,.quoteblock .quoteblock p{color:inherit;font-size:1.0625rem}
+.quoteblock.excerpt .attribution,.quoteblock .quoteblock .attribution{color:inherit;text-align:left;margin-right:0}
+table.tableblock{max-width:100%;border-collapse:separate}
+p.tableblock:last-child{margin-bottom:0}
+td.tableblock>.content>:last-child{margin-bottom:-1.25em}
+td.tableblock>.content>:last-child.sidebarblock{margin-bottom:0}
+table.tableblock,th.tableblock,td.tableblock{border:0 solid #dedede}
+table.grid-all>thead>tr>.tableblock,table.grid-all>tbody>tr>.tableblock{border-width:0 1px 1px 0}
+table.grid-all>tfoot>tr>.tableblock{border-width:1px 1px 0 0}
+table.grid-cols>*>tr>.tableblock{border-width:0 1px 0 0}
+table.grid-rows>thead>tr>.tableblock,table.grid-rows>tbody>tr>.tableblock{border-width:0 0 1px}
+table.grid-rows>tfoot>tr>.tableblock{border-width:1px 0 0}
+table.grid-all>*>tr>.tableblock:last-child,table.grid-cols>*>tr>.tableblock:last-child{border-right-width:0}
+table.grid-all>tbody>tr:last-child>.tableblock,table.grid-all>thead:last-child>tr>.tableblock,table.grid-rows>tbody>tr:last-child>.tableblock,table.grid-rows>thead:last-child>tr>.tableblock{border-bottom-width:0}
+table.frame-all{border-width:1px}
+table.frame-sides{border-width:0 1px}
+table.frame-topbot,table.frame-ends{border-width:1px 0}
+table.stripes-all tr,table.stripes-odd tr:nth-of-type(odd),table.stripes-even tr:nth-of-type(even),table.stripes-hover tr:hover{background:#f8f8f7}
+th.halign-left,td.halign-left{text-align:left}
+th.halign-right,td.halign-right{text-align:right}
+th.halign-center,td.halign-center{text-align:center}
+th.valign-top,td.valign-top{vertical-align:top}
+th.valign-bottom,td.valign-bottom{vertical-align:bottom}
+th.valign-middle,td.valign-middle{vertical-align:middle}
+table thead th,table tfoot th{font-weight:bold}
+tbody tr th{display:table-cell;line-height:1.6;background:#f7f8f7}
+tbody tr th,tbody tr th p,tfoot tr th,tfoot tr th p{color:rgba(0,0,0,.8);font-weight:bold}
+p.tableblock>code:only-child{background:none;padding:0}
+p.tableblock{font-size:1em}
+ol{margin-left:1.75em}
+ul li ol{margin-left:1.5em}
+dl dd{margin-left:1.125em}
+dl dd:last-child,dl dd:last-child>:last-child{margin-bottom:0}
+ol>li p,ul>li p,ul dd,ol dd,.olist .olist,.ulist .ulist,.ulist .olist,.olist .ulist{margin-bottom:.625em}
+ul.checklist,ul.none,ol.none,ul.no-bullet,ol.no-bullet,ol.unnumbered,ul.unstyled,ol.unstyled{list-style-type:none}
+ul.no-bullet,ol.no-bullet,ol.unnumbered{margin-left:.625em}
+ul.unstyled,ol.unstyled{margin-left:0}
+ul.checklist{margin-left:.625em}
+ul.checklist li>p:first-child>.fa-square-o:first-child,ul.checklist li>p:first-child>.fa-check-square-o:first-child{width:1.25em;font-size:.8em;position:relative;bottom:.125em}
+ul.checklist li>p:first-child>input[type="checkbox"]:first-child{margin-right:.25em}
+ul.inline{display:-ms-flexbox;display:-webkit-box;display:flex;-ms-flex-flow:row wrap;-webkit-flex-flow:row wrap;flex-flow:row wrap;list-style:none;margin:0 0 .625em -1.25em}
+ul.inline>li{margin-left:1.25em}
+.unstyled dl dt{font-weight:400;font-style:normal}
+ol.arabic{list-style-type:decimal}
+ol.decimal{list-style-type:decimal-leading-zero}
+ol.loweralpha{list-style-type:lower-alpha}
+ol.upperalpha{list-style-type:upper-alpha}
+ol.lowerroman{list-style-type:lower-roman}
+ol.upperroman{list-style-type:upper-roman}
+ol.lowergreek{list-style-type:lower-greek}
+.hdlist>table,.colist>table{border:0;background:none}
+.hdlist>table>tbody>tr,.colist>table>tbody>tr{background:none}
+td.hdlist1,td.hdlist2{vertical-align:top;padding:0 .625em}
+td.hdlist1{font-weight:bold;padding-bottom:1.25em}
+.literalblock+.colist,.listingblock+.colist{margin-top:-.5em}
+.colist td:not([class]):first-child{padding:.4em .75em 0;line-height:1;vertical-align:top}
+.colist td:not([class]):first-child img{max-width:none}
+.colist td:not([class]):last-child{padding:.25em 0}
+.thumb,.th{line-height:0;display:inline-block;border:solid 4px #fff;-webkit-box-shadow:0 0 0 1px #ddd;box-shadow:0 0 0 1px #ddd}
+.imageblock.left{margin:.25em .625em 1.25em 0}
+.imageblock.right{margin:.25em 0 1.25em .625em}
+.imageblock>.title{margin-bottom:0}
+.imageblock.thumb,.imageblock.th{border-width:6px}
+.imageblock.thumb>.title,.imageblock.th>.title{padding:0 .125em}
+.image.left,.image.right{margin-top:.25em;margin-bottom:.25em;display:inline-block;line-height:0}
+.image.left{margin-right:.625em}
+.image.right{margin-left:.625em}
+a.image{text-decoration:none;display:inline-block}
+a.image object{pointer-events:none}
+sup.footnote,sup.footnoteref{font-size:.875em;position:static;vertical-align:super}
+sup.footnote a,sup.footnoteref a{text-decoration:none}
+sup.footnote a:active,sup.footnoteref a:active{text-decoration:underline}
+#footnotes{padding-top:.75em;padding-bottom:.75em;margin-bottom:.625em}
+#footnotes hr{width:20%;min-width:6.25em;margin:-.25em 0 .75em;border-width:1px 0 0}
+#footnotes .footnote{padding:0 .375em 0 .225em;line-height:1.3334;font-size:.875em;margin-left:1.2em;margin-bottom:.2em}
+#footnotes .footnote a:first-of-type{font-weight:bold;text-decoration:none;margin-left:-1.05em}
+#footnotes .footnote:last-of-type{margin-bottom:0}
+#content #footnotes{margin-top:-.625em;margin-bottom:0;padding:.75em 0}
+.gist .file-data>table{border:0;background:#fff;width:100%;margin-bottom:0}
+.gist .file-data>table td.line-data{width:99%}
+div.unbreakable{page-break-inside:avoid}
+.big{font-size:larger}
+.small{font-size:smaller}
+.underline{text-decoration:underline}
+.overline{text-decoration:overline}
+.line-through{text-decoration:line-through}
+.aqua{color:#00bfbf}
+.aqua-background{background:#00fafa}
+.black{color:#000}
+.black-background{background:#000}
+.blue{color:#0000bf}
+.blue-background{background:#0000fa}
+.fuchsia{color:#bf00bf}
+.fuchsia-background{background:#fa00fa}
+.gray{color:#606060}
+.gray-background{background:#7d7d7d}
+.green{color:#006000}
+.green-background{background:#007d00}
+.lime{color:#00bf00}
+.lime-background{background:#00fa00}
+.maroon{color:#600000}
+.maroon-background{background:#7d0000}
+.navy{color:#000060}
+.navy-background{background:#00007d}
+.olive{color:#606000}
+.olive-background{background:#7d7d00}
+.purple{color:#600060}
+.purple-background{background:#7d007d}
+.red{color:#bf0000}
+.red-background{background:#fa0000}
+.silver{color:#909090}
+.silver-background{background:#bcbcbc}
+.teal{color:#006060}
+.teal-background{background:#007d7d}
+.white{color:#bfbfbf}
+.white-background{background:#fafafa}
+.yellow{color:#bfbf00}
+.yellow-background{background:#fafa00}
+span.icon>.fa{cursor:default}
+a span.icon>.fa{cursor:inherit}
+.admonitionblock td.icon [class^="fa icon-"]{font-size:2.5em;text-shadow:1px 1px 2px rgba(0,0,0,.5);cursor:default}
+.admonitionblock td.icon .icon-note::before{content:"\f05a";color:#19407c}
+.admonitionblock td.icon .icon-tip::before{content:"\f0eb";text-shadow:1px 1px 2px rgba(155,155,0,.8);color:#111}
+.admonitionblock td.icon .icon-warning::before{content:"\f071";color:#bf6900}
+.admonitionblock td.icon .icon-caution::before{content:"\f06d";color:#bf3400}
+.admonitionblock td.icon .icon-important::before{content:"\f06a";color:#bf0000}
+.conum[data-value]{display:inline-block;color:#fff!important;background:rgba(0,0,0,.8);-webkit-border-radius:100px;border-radius:100px;text-align:center;font-size:.75em;width:1.67em;height:1.67em;line-height:1.67em;font-family:"Open Sans","DejaVu Sans",sans-serif;font-style:normal;font-weight:bold}
+.conum[data-value] *{color:#fff!important}
+.conum[data-value]+b{display:none}
+.conum[data-value]::after{content:attr(data-value)}
+pre .conum[data-value]{position:relative;top:-.125em}
+b.conum *{color:inherit!important}
+.conum:not([data-value]):empty{display:none}
+dt,th.tableblock,td.content,div.footnote{text-rendering:optimizeLegibility}
+h1,h2,p,td.content,span.alt{letter-spacing:-.01em}
+p strong,td.content strong,div.footnote strong{letter-spacing:-.005em}
+p,blockquote,dt,td.content,span.alt{font-size:1.0625rem}
+p{margin-bottom:1.25rem}
+.sidebarblock p,.sidebarblock dt,.sidebarblock td.content,p.tableblock{font-size:1em}
+.exampleblock>.content{background:#fffef7;border-color:#e0e0dc;-webkit-box-shadow:0 1px 4px #e0e0dc;box-shadow:0 1px 4px #e0e0dc}
+.print-only{display:none!important}
+@page{margin:1.25cm .75cm}
+@media print{*{-webkit-box-shadow:none!important;box-shadow:none!important;text-shadow:none!important}
+html{font-size:80%}
+a{color:inherit!important;text-decoration:underline!important}
+a.bare,a[href^="#"],a[href^="mailto:"]{text-decoration:none!important}
+a[href^="http:"]:not(.bare)::after,a[href^="https:"]:not(.bare)::after{content:"(" attr(href) ")";display:inline-block;font-size:.875em;padding-left:.25em}
+abbr[title]::after{content:" (" attr(title) ")"}
+pre,blockquote,tr,img,object,svg{page-break-inside:avoid}
+thead{display:table-header-group}
+svg{max-width:100%}
+p,blockquote,dt,td.content{font-size:1em;orphans:3;widows:3}
+h2,h3,#toctitle,.sidebarblock>.content>.title{page-break-after:avoid}
+#toc,.sidebarblock,.exampleblock>.content{background:none!important}
+#toc{border-bottom:1px solid #dddddf!important;padding-bottom:0!important}
+body.book #header{text-align:center}
+body.book #header>h1:first-child{border:0!important;margin:2.5em 0 1em}
+body.book #header .details{border:0!important;display:block;padding:0!important}
+body.book #header .details span:first-child{margin-left:0!important}
+body.book #header .details br{display:block}
+body.book #header .details br+span::before{content:none!important}
+body.book #toc{border:0!important;text-align:left!important;padding:0!important;margin:0!important}
+body.book #toc,body.book #preamble,body.book h1.sect0,body.book .sect1>h2{page-break-before:always}
+.listingblock code[data-lang]::before{display:block}
+#footer{padding:0 .9375em}
+.hide-on-print{display:none!important}
+.print-only{display:block!important}
+.hide-for-print{display:none!important}
+.show-for-print{display:inherit!important}}
+@media print,amzn-kf8{#header>h1:first-child{margin-top:1.25rem}
+.sect1{padding:0!important}
+.sect1+.sect1{border:0}
+#footer{background:none}
+#footer-text{color:rgba(0,0,0,.6);font-size:.9em}}
+@media amzn-kf8{#header,#content,#footnotes,#footer{padding:0}}
 </style>
-<script type="text/javascript">
-/*<![CDATA[*/
-var asciidoc = {  // Namespace.
-
-/////////////////////////////////////////////////////////////////////
-// Table Of Contents generator
-/////////////////////////////////////////////////////////////////////
-
-/* Author: Mihai Bazon, September 2002
- * http://students.infoiasi.ro/~mishoo
- *
- * Table Of Content generator
- * Version: 0.4
- *
- * Feel free to use this script under the terms of the GNU General Public
- * License, as long as you do not remove or alter this notice.
- */
-
- /* modified by Troy D. Hanson, September 2006. License: GPL */
- /* modified by Stuart Rackham, 2006, 2009. License: GPL */
-
-// toclevels = 1..4.
-toc: function (toclevels) {
-
-  function getText(el) {
-    var text = "";
-    for (var i = el.firstChild; i != null; i = i.nextSibling) {
-      if (i.nodeType == 3 /* Node.TEXT_NODE */) // IE doesn't speak constants.
-        text += i.data;
-      else if (i.firstChild != null)
-        text += getText(i);
-    }
-    return text;
-  }
-
-  function TocEntry(el, text, toclevel) {
-    this.element = el;
-    this.text = text;
-    this.toclevel = toclevel;
-  }
-
-  function tocEntries(el, toclevels) {
-    var result = new Array;
-    var re = new RegExp('[hH]([1-'+(toclevels+1)+'])');
-    // Function that scans the DOM tree for header elements (the DOM2
-    // nodeIterator API would be a better technique but not supported by all
-    // browsers).
-    var iterate = function (el) {
-      for (var i = el.firstChild; i != null; i = i.nextSibling) {
-        if (i.nodeType == 1 /* Node.ELEMENT_NODE */) {
-          var mo = re.exec(i.tagName);
-          if (mo && (i.getAttribute("class") || i.getAttribute("className")) != "float") {
-            result[result.length] = new TocEntry(i, getText(i), mo[1]-1);
-          }
-          iterate(i);
-        }
-      }
-    }
-    iterate(el);
-    return result;
-  }
-
-  var toc = document.getElementById("toc");
-  if (!toc) {
-    return;
-  }
-
-  // Delete existing TOC entries in case we're reloading the TOC.
-  var tocEntriesToRemove = [];
-  var i;
-  for (i = 0; i < toc.childNodes.length; i++) {
-    var entry = toc.childNodes[i];
-    if (entry.nodeName.toLowerCase() == 'div'
-     && entry.getAttribute("class")
-     && entry.getAttribute("class").match(/^toclevel/))
-      tocEntriesToRemove.push(entry);
-  }
-  for (i = 0; i < tocEntriesToRemove.length; i++) {
-    toc.removeChild(tocEntriesToRemove[i]);
-  }
-
-  // Rebuild TOC entries.
-  var entries = tocEntries(document.getElementById("content"), toclevels);
-  for (var i = 0; i < entries.length; ++i) {
-    var entry = entries[i];
-    if (entry.element.id == "")
-      entry.element.id = "_toc_" + i;
-    var a = document.createElement("a");
-    a.href = "#" + entry.element.id;
-    a.appendChild(document.createTextNode(entry.text));
-    var div = document.createElement("div");
-    div.appendChild(a);
-    div.className = "toclevel" + entry.toclevel;
-    toc.appendChild(div);
-  }
-  if (entries.length == 0)
-    toc.parentNode.removeChild(toc);
-},
-
-
-/////////////////////////////////////////////////////////////////////
-// Footnotes generator
-/////////////////////////////////////////////////////////////////////
-
-/* Based on footnote generation code from:
- * http://www.brandspankingnew.net/archive/2005/07/format_footnote.html
- */
-
-footnotes: function () {
-  // Delete existing footnote entries in case we're reloading the footnodes.
-  var i;
-  var noteholder = document.getElementById("footnotes");
-  if (!noteholder) {
-    return;
-  }
-  var entriesToRemove = [];
-  for (i = 0; i < noteholder.childNodes.length; i++) {
-    var entry = noteholder.childNodes[i];
-    if (entry.nodeName.toLowerCase() == 'div' && entry.getAttribute("class") == "footnote")
-      entriesToRemove.push(entry);
-  }
-  for (i = 0; i < entriesToRemove.length; i++) {
-    noteholder.removeChild(entriesToRemove[i]);
-  }
-
-  // Rebuild footnote entries.
-  var cont = document.getElementById("content");
-  var spans = cont.getElementsByTagName("span");
-  var refs = {};
-  var n = 0;
-  for (i=0; i<spans.length; i++) {
-    if (spans[i].className == "footnote") {
-      n++;
-      var note = spans[i].getAttribute("data-note");
-      if (!note) {
-        // Use [\s\S] in place of . so multi-line matches work.
-        // Because JavaScript has no s (dotall) regex flag.
-        note = spans[i].innerHTML.match(/\s*\[([\s\S]*)]\s*/)[1];
-        spans[i].innerHTML =
-          "[<a id='_footnoteref_" + n + "' href='#_footnote_" + n +
-          "' title='View footnote' class='footnote'>" + n + "</a>]";
-        spans[i].setAttribute("data-note", note);
-      }
-      noteholder.innerHTML +=
-        "<div class='footnote' id='_footnote_" + n + "'>" +
-        "<a href='#_footnoteref_" + n + "' title='Return to text'>" +
-        n + "</a>. " + note + "</div>";
-      var id =spans[i].getAttribute("id");
-      if (id != null) refs["#"+id] = n;
-    }
-  }
-  if (n == 0)
-    noteholder.parentNode.removeChild(noteholder);
-  else {
-    // Process footnoterefs.
-    for (i=0; i<spans.length; i++) {
-      if (spans[i].className == "footnoteref") {
-        var href = spans[i].getElementsByTagName("a")[0].getAttribute("href");
-        href = href.match(/#.*/)[0];  // Because IE return full URL.
-        n = refs[href];
-        spans[i].innerHTML =
-          "[<a href='#_footnote_" + n +
-          "' title='View footnote' class='footnote'>" + n + "</a>]";
-      }
-    }
-  }
-},
-
-install: function(toclevels) {
-  var timerId;
-
-  function reinstall() {
-    asciidoc.footnotes();
-    if (toclevels) {
-      asciidoc.toc(toclevels);
-    }
-  }
-
-  function reinstallAndRemoveTimer() {
-    clearInterval(timerId);
-    reinstall();
-  }
-
-  timerId = setInterval(reinstall, 500);
-  if (document.addEventListener)
-    document.addEventListener("DOMContentLoaded", reinstallAndRemoveTimer, false);
-  else
-    window.onload = reinstallAndRemoveTimer;
-}
-
-}
-asciidoc.install(3);
-/*]]>*/
-</script>
 </head>
 <body class="article">
 <div id="header">
+<div id="toc" class="toc">
+<div id="toctitle">Table of Contents</div>
+<ul class="sectlevel1">
+<li><a href="#_installing_subsurface_mobile_on_your_mobile_device">1. Installing <em>Subsurface-mobile</em> on your mobile device</a></li>
+<li><a href="#_getting_support">2. Getting Support</a></li>
+<li><a href="#_user_interface">3. User Interface</a></li>
+<li><a href="#_using_subsurface_mobile_for_the_first_time">4. Using <em>Subsurface-mobile</em> for the first time</a>
+<ul class="sectlevel2">
+<li><a href="#_using_subsurface_mobile_without_cloud_storage">4.1. Using <em>Subsurface-mobile</em> without Cloud Storage</a></li>
+<li><a href="#_using_cloud_storage">4.2. Using Cloud Storage</a></li>
+</ul>
+</li>
+<li><a href="#_the_dive_list">5. The Dive List</a>
+<ul class="sectlevel2">
+<li><a href="#S_View_Dive">5.1. View a dive: the Details view</a></li>
+<li><a href="#_viewing_the_location_of_a_dive_on_a_map">5.2. Viewing the location of a dive on a map</a></li>
+<li><a href="#_filter_the_dive_list">5.3. Filter the dive list</a></li>
+</ul>
+</li>
+<li><a href="#S_Dive_Management">6. Dive List Management and adding dive information</a>
+<ul class="sectlevel2">
+<li><a href="#S_Add_Dive">6.1. Manually adding a new dive to the dive list</a></li>
+<li><a href="#S_Download">6.2. Download dives from a dive computer</a>
+<ul class="sectlevel3">
+<li><a href="#_download_from_usb_serial_dive_computers">6.2.1. Download from USB serial dive computers</a></li>
+<li><a href="#_download_from_bluetooth_and_bluetooth_le_dive_computers">6.2.2. Download from Bluetooth and Bluetooth LE dive computers</a></li>
+<li><a href="#_start_the_download">6.2.3. Start the download</a></li>
+</ul>
+</li>
+<li><a href="#S_Edit_Dive">6.3. Edit the dive information</a></li>
+</ul>
+</li>
+<li><a href="#S_Divetrip">7. Edit the dive trip information</a>
+<ul class="sectlevel2">
+<li><a href="#_deleting_a_dive">7.1. Deleting a dive</a></li>
+</ul>
+</li>
+<li><a href="#_interacting_with_the_cloud_storage">8. Interacting with the cloud storage</a>
+<ul class="sectlevel2">
+<li><a href="#_manually_sync_the_dive_log_with_the_subsurface_cloud">8.1. Manually sync the dive log with the <em>Subsurface Cloud</em></a></li>
+<li><a href="#_enable_cloud_auto_sync">8.2. Enable cloud auto sync</a></li>
+</ul>
+</li>
+<li><a href="#_dive_summary">9. Dive Summary</a>
+<ul class="sectlevel2">
+<li><a href="#_export">9.1. Export</a></li>
+</ul>
+</li>
+<li><a href="#_obtaining_dive_site_locations_using_the_gps">10. Obtaining dive site locations using the GPS</a>
+<ul class="sectlevel2">
+<li><a href="#S_ConfigureGPS">10.1. Configuring the GPS service</a></li>
+<li><a href="#_collecting_gps_positions">10.2. Collecting GPS positions</a></li>
+<li><a href="#_viewing_gps_data_collected_during_a_dive">10.3. Viewing GPS data collected during a dive</a></li>
+<li><a href="#_applying_gps_data_to_dives_in_the_dive_log">10.4. Applying GPS data to dives in the dive log</a></li>
+</ul>
+</li>
+<li><a href="#_viewing_the_locations_of_all_dives_in_the_dive_list">11. Viewing the locations of all dives in the dive list</a></li>
+<li><a href="#S_Settings">12. Specifying the settings for <em>Subsurface-mobile</em></a>
+<ul class="sectlevel2">
+<li><a href="#_general_settings_section">12.1. <em>General settings</em> section</a>
+<ul class="sectlevel3">
+<li><a href="#S_ChangeCloudAccount">12.1.1. Cloud status: Changing to a different <em>Subsurface</em> cloud account</a></li>
+<li><a href="#_default_cylinder">12.1.2. Default cylinder</a></li>
+<li><a href="#_forget_the_remembered_dive_computers_used_during_dive_download">12.1.3. Forget the remembered dive computers used during dive download</a></li>
+</ul>
+</li>
+<li><a href="#_theme_section">12.2. <em>Theme</em> section</a>
+<ul class="sectlevel3">
+<li><a href="#_color_theme">12.2.1. Color theme</a></li>
+<li><a href="#_font_size">12.2.2. Font size</a></li>
+</ul>
+</li>
+<li><a href="#_units_section">12.3. <em>Units</em> section</a></li>
+<li><a href="#_advanced_section">12.4. <em>Advanced</em> section</a>
+<ul class="sectlevel3">
+<li><a href="#_gps_location_service_thresholds">12.4.1. GPS location service thresholds</a></li>
+<li><a href="#_bluetooth">12.4.2. Bluetooth</a></li>
+<li><a href="#_display">12.4.3. Display</a></li>
+<li><a href="#_activating_the_developer_sub_menu">12.4.4. Activating the Developer sub-menu</a></li>
+</ul>
+</li>
+</ul>
+</li>
+<li><a href="#_help">13. Help</a>
+<ul class="sectlevel2">
+<li><a href="#_about">13.1. About</a></li>
+<li><a href="#_show_user_manual">13.2. Show user manual</a></li>
+<li><a href="#_ask_for_support">13.3. Ask for support</a></li>
+<li><a href="#_reset_forgotten_subsurface_cloud_password">13.4. Reset forgotten <em>Subsurface Cloud</em> password</a></li>
+</ul>
+</li>
+</ul>
+</div>
 </div>
 <div id="content">
-<div class="imageblock" style="text-align:center;">
+<div class="imageblock text-center">
 <div class="content">
-<img src="mobile-images/Banner.jpg" alt="Banner" />
+<img src="mobile-images/Banner.jpg" alt="Banner">
 </div>
 </div>
-<div class="paragraph"><p><span class="big"><em>Subsurface-mobile</em> User Manual</span></p></div>
-<div class="paragraph"><p><strong>Manual authors</strong>: Willem Ferguson, Dirk Hohndel</p></div>
-<div class="paragraph"><p><span class="blue"><em>Version 3.0.0, March 2020</em></span></p></div>
-<div class="sect1">
-<h2 id="_introducing_em_subsurface_mobile_em">1. Introducing <em>Subsurface-mobile</em></h2>
-<div class="sectionbody">
-<div class="paragraph"><p>Welcome to <em>Subsurface-mobile</em>, the mobile version of <em>Subsurface</em>, advanced dive logging
+<div class="paragraph">
+<p><span class="big"><em>Subsurface-mobile</em> User Manual</span></p>
+</div>
+<div class="paragraph">
+<p><strong>Manual authors</strong>: Willem Ferguson, Dirk Hohndel</p>
+</div>
+<div class="paragraph">
+<p><span class="blue"><em>Version 3.0.5, May 2020</em></span></p>
+</div>
+<!-- toc disabled -->
+<div class="paragraph">
+<p>Welcome to <em>Subsurface-mobile</em>, the mobile version of <em>Subsurface</em>, advanced dive logging
 software with extensive infrastructure to display, organize, and interpret scuba
 and free dives. <em>Subsurface</em> runs on Windows, macOS, most common distributions of Linux.
 <em>Subsurface-mobile</em> is available for Android and iOS. Both are
 open-source software (in simple terms that means that there is no commercial interest behind
 them, all the source code needed to build them is available, there are no ads, no one is
-monetizing your data, etc).</p></div>
-<div class="paragraph"><p><em>Subsurface-mobile</em> is a limited mobile version of <em>Subsurface</em>,
+monetizing your data, etc).</p>
+</div>
+<div class="paragraph">
+<p><em>Subsurface-mobile</em> is a limited mobile version of the desktop software <em>Subsurface</em>,
 aimed at Android and iOS smartphone and tablet devices.
 While the desktop version of <em>Subsurface</em> shows much more detailed information
 for each dive, the mobile version allows a more accessible dive log on the go. For example,
@@ -429,418 +566,467 @@ you can prove dive experience on a dive trip to dive shops or review
 previous dives while on a dive boat. <em>Subsurface-mobile</em> also allows
 the gathering of GPS locations where dives are performed.
 Assuming you have a dive computer that is supported by the mobile OS of
-your choice, <em>Subsurface-mobile</em> even supports the downloading of dives from your dive computer.</p></div>
-<div class="paragraph"><p>Users of <em>Subsurface-mobile</em> typically use the
+your choice, <em>Subsurface-mobile</em> supports the downloading of dives from your dive computer.</p>
+</div>
+<div class="paragraph">
+<p>Users of <em>Subsurface-mobile</em> often use the
 mobile app together with the desktop version of <em>Subsurface</em>,  sharing dive information
 between the mobile and the desktop versions using a free <em>Subsurface Cloud</em> account.
-However <em>Subsurface-mobile</em> can
-also be used independently of the desktop version and does not require the use of cloud storage.</p></div>
-<div class="paragraph"><p><em>Subsurface-mobile</em> allows:</p></div>
-<div class="ulist"><ul>
+However <em>Subsurface-mobile</em> is a fully fledged application in its own right that can
+also be used independently of the desktop version with or without the use of cloud storage.
+<em>Subsurface-mobile</em> allows:</p>
+</div>
+<div class="ulist">
+<ul>
 <li>
-<p>
-Download and storage of dive log information using the <em>Subsurface</em> cloud.
-</p>
+<p>Download and storage of dive log information using the <em>Subsurface</em> cloud.</p>
 </li>
 <li>
-<p>
-Viewing this information on a mobile device.
-</p>
+<p>Viewing this information on a mobile device.</p>
 </li>
 <li>
-<p>
-Manually creating and adding new dive records to your dive log.
-</p>
+<p>Manually creating and adding new dive records to your dive log.</p>
 </li>
 <li>
-<p>
-Download dive data directly from some dive computers.
-</p>
+<p>Download dive data directly from some dive computers.</p>
 </li>
 <li>
-<p>
-Editing most of the dive log data, e.g. dive-master, buddy,
-  equipment or notes relating to a dive.
-</p>
+<p>Editing most of the dive log data, e.g. dive-master, buddy,
+equipment or notes relating to a dive.</p>
 </li>
 <li>
-<p>
-Recording, storing and applying GPS positions to dives.
-</p>
+<p>Recording, storing and applying GPS positions to dive information.</p>
 </li>
 <li>
-<p>
-Viewing the locations of recorded GPS positions and of dives
-  on a map.
-</p>
+<p>Viewing the localities of recorded GPS positions and of dives
+on a map.</p>
 </li>
-</ul></div>
-<div class="paragraph"><p>These items are discussed in greater detail in the following chapters.</p></div>
-<div class="paragraph"><p><em>Subsurface-mobile</em> has some limitations compared to <em>Subsurface</em>:</p></div>
-<div class="ulist"><ul>
+</ul>
+</div>
+<div class="paragraph">
+<p>These items are discussed in greater detail below.</p>
+</div>
+<div class="paragraph">
+<p><em>Subsurface-mobile</em> has some limitations compared to <em>Subsurface</em>:</p>
+</div>
+<div class="ulist">
+<ul>
 <li>
-<p>
-Only a subset of the dive computers supported for download by the desktop
-version work with <em>Subsurface-mobile</em>. This limitation is
-mainly caused by hardware and OS limitations in the
+<p>Only a subset of the dive computers supported for download by the desktop
+version work with <em>Subsurface-mobile</em>, this being determined
+by hardware and OS limitations in the
 two mobile platforms. On Android, a subset of
 dive computers that use USB serial cables or a Bluetooth / Bluetooth LE interface
-are accessible by <em>Subsurface-mobile</em>. On iOS, only Bluetooth LE based
-dive computers are supported.
-</p>
+are accessible. On iOS, only Bluetooth LE based
+dive computers are supported.</p>
 </li>
 <li>
-<p>
-No dive planner.
-</p>
+<p>No dive planner.</p>
 </li>
 <li>
-<p>
-No printing.
-</p>
+<p>No printing.</p>
 </li>
 <li>
-<p>
-No support for media embedded in dive profiles (<em>Subsurface</em> allows to reference images and video clips directly in the dive profile).
-</p>
+<p>No support for media embedded in dive profiles (<em>Subsurface</em> allows access to
+images and video clips directly from the dive profile).</p>
 </li>
-</ul></div>
-</div>
+</ul>
 </div>
 <div class="sect1">
-<h2 id="_installing_em_subsurface_mobile_em_on_your_mobile_device">2. Installing <em>Subsurface-mobile</em> on your mobile device</h2>
+<h2 id="_installing_subsurface_mobile_on_your_mobile_device">1. Installing <em>Subsurface-mobile</em> on your mobile device</h2>
 <div class="sectionbody">
-<div class="paragraph"><p>Find <em>Subsurface-mobile</em> in the <em>Google Play Store</em> or the <em>Apple App Store</em>
-and install it. For Android devices without access to the <em>Google Play Store</em>
-APKs can be found in the downloads folder on the <em>Subsurface</em> website.</p></div>
+<div class="paragraph">
+<p>Find <em>Subsurface-mobile</em> in the <em>Google Play Store</em> or the <em>Apple App Store</em>
+and install it. For Android devices without access to the <em>Google Play Store</em>,
+APKs can be found in the downloads folder on the <em>Subsurface</em> website.</p>
+</div>
 </div>
 </div>
 <div class="sect1">
-<h2 id="_getting_support">3. Getting Support</h2>
+<h2 id="_getting_support">2. Getting Support</h2>
 <div class="sectionbody">
-<div class="paragraph"><p>The best place to get support is the <a href="https://subsurface-divelog.org/user-forum"><em>Subsurface</em> User Forum</a>. Additionally, <em>Subsurface-mobile</em> allows
-you to send a support email by tapping on <em>Ask for support</em> in the <em>Help</em> menu. This will open an
-email to our in-app-support address in the native email client, including the relevant logs.</p></div>
+<div class="paragraph">
+<p>The best place to get support is the <a href="https://subsurface-divelog.org/user-forum"><em>Subsurface</em> User Forum</a>. Additionally, <em>Subsurface-mobile</em> allows
+you to send a support request by tapping on <em>Ask for support</em> in the <em>Help</em> menu. This will open an
+email to our in-app-support address in the native email client, including the relevant logs.</p>
+</div>
 </div>
 </div>
 <div class="sect1">
-<h2 id="_user_interface">4. User Interface</h2>
+<h2 id="_user_interface">3. User Interface</h2>
 <div class="sectionbody">
-<div class="paragraph"><p><em>Subsurface-mobile</em> uses the same user interface philosophy on both Android and iOS, based on an
-open source project called <em>Kirigami</em> that is maintained by the <em>KDE/Plasma</em> development community.
-This user interface has a slightly different look and feel than many native Android and iOS apps,
-but we (the developers) feel that it is very easy and intuitive to work with.</p></div>
-<div class="paragraph"><p>On every screen you have access to the <em>Main menu</em> through a <em>Hamburger</em> button (three short
-horizontal lines) in the lower left corner. Additionally, the <em>Main menu</em> can be opened by swiping
-towards the right from the very left edge of the screen. The entries in the main menu are all explained
-starting in section <a href="#S_Dive_Management"><em>Dive Management</em></a>.</p></div>
-<div class="paragraph"><p>On many pages there is also a <em>Context menu</em> available through a button with three vertical dots in
-the lower right corner.
-In the dive list this <em>Context menu</em> can also be opened by tapping and holding a dive or trip header.</p></div>
-<div class="imageblock" style="float:left;">
+<div class="paragraph">
+<p><em>Subsurface-mobile</em> uses the same user interface philosophy on both Android and iOS, based on an
+open source project called <em>Kirigami</em>, maintained by the <em>KDE/Plasma</em> development community.
+It has a slightly different look and feel than many native Android and iOS apps,
+but we find it easy and intuitive to work with.</p>
+</div>
+<div class="paragraph">
+<p>You have access to the <em>Main menu</em> through a <em>Hamburger</em> button (three short
+horizontal lines) in the lower left corner of the screen. Additionally, the <em>Main menu</em> can be opened by swiping
+towards the right from the very left edge of the screen.
+In addition, many screens have a <em>Context menu</em> available through a button with three vertical dots in
+the lower right corner and that can be opened by tapping and holding a dive or trip header in the dive list.</p>
+</div>
+<div class="imageblock left">
 <div class="content">
-<img src="mobile-images/ActionButton2.jpg" alt="FIGURE: Action Button" />
+<img src="mobile-images/ActionButton2.jpg" alt="FIGURE: Action Button">
 </div>
 </div>
-<div class="paragraph"><p>Additionally, at the bottom of many <em>Subsurface-mobile</em> screens is a round
+<div class="paragraph">
+<p>At the bottom of many <em>Subsurface-mobile</em> screens is a round
 <em>Action button</em> that provides quick access to the most commonly needed
-actions on that screen (see image on the left). On some screens there is only
-the round center button enabled, on others there are one or two additional
-actions available on either side of that center button.</p></div>
-<div style="clear:both;"></div>
-<div class="paragraph"><p>On Android devices, use the Android Back
+actions on that screen (see image on the left). Some screens have only
+the round central button, others have one or two additional
+actions on either side of the central button.</p>
+</div>
+<div class="paragraph">
+<p>unfloat::[]</p>
+</div>
+<div class="paragraph">
+<p>On Android devices, use the Android Back
 button for "cancel", "discard" or "back" actions. For example, when
 editing dive information, tapping the action button saves the changes while the
-Android back button can be used to cancel the edit without saving changes.</p></div>
-<div class="paragraph"><p>The image below indicates some of the important features of the menu system.
+Android back button can be used to cancel the edit without saving changes.</p>
+</div>
+<div class="paragraph">
+<p>The image below indicates some of the important features of the menu system.
 On the left is the main menu, activated as described above. On the right of the image
-are the items of all the sub-menus available.</p></div>
-<div class="imageblock" style="text-align:center;">
+are the sub-menus.</p>
+</div>
+<div class="imageblock text-center">
 <div class="content">
-<img src="mobile-images/Subsurface-mobile-menu-system.jpg" alt="FIGURE: Subsurface-mobile menu system" />
+<img src="mobile-images/Subsurface-mobile-menu-system.jpg" alt="FIGURE: Subsurface-mobile menu system">
 </div>
 </div>
-<div class="paragraph"><p>All screenshots in this user manual are currently from the Android
-version. The iOS screens look similar.</p></div>
+<div class="paragraph">
+<p>All screenshots in this user manual are currently from the Android
+version. The iOS screens look similar.</p>
+</div>
 </div>
 </div>
 <div class="sect1">
-<h2 id="_using_em_subsurface_mobile_em_for_the_first_time">5. Using <em>Subsurface-mobile</em> for the first time</h2>
+<h2 id="_using_subsurface_mobile_for_the_first_time">4. Using <em>Subsurface-mobile</em> for the first time</h2>
 <div class="sectionbody">
-<div class="paragraph"><p>When you start <em>Subsurface-mobile</em> for the first time, a <em>Subsurface</em>
+<div class="paragraph">
+<p>When you start <em>Subsurface-mobile</em> for the first time, a <em>Subsurface</em>
 splash screen is shown while the program loads. On some devices this
 may take several seconds. Afterwards the <em>Cloud Credentials screen</em> appears
-(see left image below).</p></div>
-<div class="imageblock" style="text-align:center;">
+(see left image below).</p>
+</div>
+<div class="imageblock text-center">
 <div class="content">
-<img src="mobile-images/Credentials.jpg" alt="FIGURE: Mobile credentials screen" />
+<img src="mobile-images/Credentials.jpg" alt="FIGURE: Mobile credentials screen">
 </div>
 </div>
 <div class="sect2">
-<h3 id="_using_em_subsurface_mobile_em_without_cloud_storage">5.1. Using <em>Subsurface-mobile</em> without Cloud Storage</h3>
-<div class="paragraph"><p>Tap the "No cloud mode" button. The app will only store dive log information locally
-on your device. After the first start the dive log will therefore be empty.</p></div>
+<h3 id="_using_subsurface_mobile_without_cloud_storage">4.1. Using <em>Subsurface-mobile</em> without Cloud Storage</h3>
+<div class="paragraph">
+<p>Tap the "No cloud mode" button. The app will only store dive log information locally
+on your device. Following installation an empty dive log is created.</p>
+</div>
 </div>
 <div class="sect2">
-<h3 id="_using_cloud_storage">5.2. Using Cloud Storage</h3>
-<div class="paragraph"><p>The <em>Subsurface</em> maintainer provides a dedicated and
+<h3 id="_using_cloud_storage">4.2. Using Cloud Storage</h3>
+<div class="paragraph">
+<p>The <em>Subsurface</em> maintainer provides a dedicated and
 free Internet cloud storage account for users of <em>Subsurface</em> and <em>Subsurface-mobile</em>.
-You can use this to store your dive log and to share your data between various computers
+You can use this to store your dive log and to share your data between several computers
 and devices. The <em>Subsurface</em> team never accesses your dive data without explicit
 permission to do so, the data are not used for any other purpose than providing them to the user who
-created them. There are no ads and no harvesting / analysis of the data
-stored in the <em>Subsurface Cloud</em> storage. There is no monetization whatsoever.</p></div>
-<div class="paragraph"><p><em>Subsurface-mobile</em> is sufficient to fully maintain a dive log. In addition you can use the
+created them. There are no ads and no harvesting / analysis of the data / monetization of data
+on the <em>Subsurface Cloud</em> storage.</p>
+</div>
+<div class="paragraph">
+<p><em>Subsurface-mobile</em> is sufficient to fully maintain a dive log. In addition you can use the
 more advanced features in <em>Subsurface</em> when you have access to a computer while still
-being able to work with your dive data when only a mobile device is available.</p></div>
-<div class="paragraph"><p>The dive data in the cloud are cached locally on any device or computer that is connected to
+being able to work with your dive data when only a mobile device is available.</p>
+</div>
+<div class="paragraph">
+<p>The dive data in the cloud are cached locally on any device or computer that is connected to
 the <em>Subsurface Cloud</em> account.
 It is easy to create backups of the data (for example in XML format) on the desktop: both the mobile
 device and the desktop keep a local copy of the data so that the dive log is always accessible, even
-without Internet connection.</p></div>
-<div class="paragraph"><p>To create a <em>Subsurface Cloud</em> account follow these steps:</p></div>
-<div class="paragraph"><p>1) Enter an e-mail address and a password in the fields indicated on the screen (see image above).
+without an Internet connection.</p>
+</div>
+<div class="paragraph">
+<p>To create a <em>Subsurface Cloud</em> account follow these steps:</p>
+</div>
+<div class="paragraph">
+<p>1) Enter an e-mail address and a password in the fields indicated on the screen (see image above).
 The e-mail address should be in lower case and the password should contain a combination of
-upper and lower case letters and/or numbers.</p></div>
-<div class="paragraph"><p>2) Tap the "Sign-in or Register" button.</p></div>
-<div class="paragraph"><p>If you have already set
+upper and lower case letters and/or numbers.</p>
+</div>
+<div class="paragraph">
+<p>2) Tap the "Sign-in or Register" button.</p>
+</div>
+<div class="paragraph">
+<p>If you have already set
 up an account on a different computer or device, simply enter the same credentials here.
 <em>Subsurface-mobile</em> will now download your existing dive log data. Once the dive
 list has been downloaded from the cloud, <em>Subsurface-mobile</em> usually works only with the the local
-copy on the mobile device. This avoids long delays or even failure of operations if there is a bad
-(or no) internet connection, a situation fairly common at many dive sites. Remember to manually sync
+copy on the mobile device. This avoids long delays or even failure of operations if there is poor
+internet connectivity. Remember to manually sync
 with the server after making local changes (either by pulling down on the dive list, or by using the
-manual sync entry in the Dive management menu entry).</p></div>
-<div class="paragraph"><p>3) If this is a new cloud account, a PIN screen will open (see right image above). A PIN is e-mailed
+manual sync entry in the Dive management menu entry).</p>
+</div>
+<div class="paragraph">
+<p>3) If this is a new cloud account, a PIN screen will open (see right image above). A PIN is e-mailed
 to the email address entered in the previous step. Enter this PIN into the field indicated
 and tap the <em>Register</em> button. After the PIN has been entered it
-is no longer needed - it just proves that this is indeed your email account.</p></div>
-<div class="paragraph"><p>At this point a new account has been created for you on the cloud server and access to the cloud is
+is no longer needed - it just proves that this is indeed your email account.</p>
+</div>
+<div class="paragraph">
+<p>A <a href="https://www.youtube.com/watch?v=Vp_bEm5ZDRA"><strong>video-tutorial</strong></a> is available that demonstrates
+how to connect to the cloud.</p>
+</div>
+<div class="paragraph">
+<p>At this point a new account has been created for you on the cloud server and access to the cloud is
 enabled. In this case the dive list is initially empty. Start entering dives in the dive
-log or download dive information from a supported dive computer.</p></div>
-<div class="paragraph"><p>Once registered, <em>Subsurface-mobile</em> remembers the cloud credentials and it is not necessary to
-provide these again when launching the program.</p></div>
+log or download dive information from a supported dive computer.</p>
+</div>
+<div class="paragraph">
+<p>Once registered, <em>Subsurface-mobile</em> remembers the cloud credentials and it is not necessary to
+provide these again when launching the program.</p>
+</div>
 <div class="sidebarblock">
 <div class="content">
-<div class="admonitionblock">
-<table><tr>
+<div class="admonitionblock important">
+<table>
+<tr>
 <td class="icon">
-<img src="images/icons/important.png" alt="Important" />
+<img src="./images/icons/images/icons/important.png" alt="Important">
+</td>
+<td class="content">
+<strong>Cloud problems: FAQ</strong>
 </td>
-<td class="content"><strong>Cloud problems: FAQ</strong></td>
-</tr></table>
+</tr>
+</table>
+</div>
+<div class="paragraph">
+<p><span class="blue">After filling in the correct information and submitting it, I did not receive a PIN by email</span></p>
 </div>
-<div class="paragraph"><p><span class="blue">After filling in the correct information and submitting it, I did not receive a PIN by email</span></p></div>
-<div class="olist arabic"><ol class="arabic">
+<div class="olist arabic">
+<ol class="arabic">
 <li>
-<p>
-Check <strong>carefully</strong> that you didn&#8217;t make a spelling mistake in the email address you provided. You would be surprised how often this is the problem that people encounter, as autocorrect often mangles email addresses.
-</p>
+<p>Check <strong>carefully</strong> for spelling mistakes in the email address you provided. This is a common problem since autocorrect often mangles email addresses.</p>
 </li>
 <li>
-<p>
-Check that the return email containing the PIN is not in the SPAM/Junk folder of your email client.
-</p>
+<p>Check that the return email containing the PIN is not in the SPAM/Junk folder of your email client.</p>
 </li>
 <li>
-<p>
-Wait for a few hours and check again for an email with a PIN.
-</p>
+<p>Wait for a few hours and check again for an email with a PIN.</p>
 </li>
 <li>
-<p>
-If there is still no email containing a PIN, send mail to <a href="mailto:in-app-support@subsurface-divelog.org">in-app-support@subsurface-divelog.org</a>
-</p>
+<p>If there is still no email containing a PIN, send mail to <a href="mailto:in-app-support@subsurface-divelog.org">in-app-support@subsurface-divelog.org</a></p>
 </li>
-</ol></div>
-<div class="paragraph"><p><span class="blue">I want to access the <em>Subsurface Cloud</em> storage but I have forgotten my password. How can I reset my password?</span></p></div>
-<div class="paragraph"><p>There is a <em>Reset forgotten Subsurface Cloud password</em> entry in the <em>Help</em> menu in
-<em>Subsurface-mobile</em>, or you can go to the <a href="https://cloud.subsurface-divelog.org/passwordreset">password reset website</a></p></div>
-<div class="paragraph"><p>Simply enter the same email address that you used during cloud registration and follow the indicated steps. A confirmation email will be sent to your account to prevent abuse of this system.</p></div>
-</div></div>
+</ol>
+</div>
+<div class="paragraph">
+<p><span class="blue">I want to access the <em>Subsurface Cloud</em> storage but I have forgotten my password. How can I reset my password?</span></p>
+</div>
+<div class="paragraph">
+<p>The <em>Help menu</em> has an option <em>Reset forgotten Subsurface Cloud password</em>. Use that or go to the <a href="https://cloud.subsurface-divelog.org/passwordreset">password reset website</a></p>
+</div>
+<div class="paragraph">
+<p>Simply enter the same email address that you used during cloud registration and follow the indicated steps.
+To prevent abuse of this system a confirmation email will be sent to your account.</p>
+</div>
+</div>
+</div>
+<div class="paragraph">
+<p>The dive log can be updated automatically. If there is Internet connectivity, <em>Subsurface-mobile</em> accesses
+the cloud-based dive log to verify that the local copy of the dive log is still the
+same as the log in the cloud server. If not, the local copy and the copy on
+the server are synchronized.</p>
+</div>
 </div>
 </div>
 </div>
 <div class="sect1">
-<h2 id="_the_dive_list">6. The Dive List</h2>
+<h2 id="_the_dive_list">5. The Dive List</h2>
 <div class="sectionbody">
-<div class="paragraph"><p>Most of the actions of <em>Subsurface-mobile</em> center around the dives in the
-dive list. While the dive list is loading from the cloud,
+<div class="paragraph">
+<p>The <em>Dive List</em> is the heart of <em>Subsurface-mobile</em> because most of the actions
+center around the dives on the dive list. While the dive list is loading from the cloud,
 a message appears at the bottom of the screen, indicating that the cloud is
 being accessed, after which the dive list is shown. Once the list is loaded you can scroll up
-and down through your dive history.
-<em>Subsurface</em> typically structures your dive list by dive trips, but using those is optional
-(and for divers who are lucky enough to be able to dive all the time at local dive sites,
-trips might only make sense for dive vacations).</p></div>
-<div class="paragraph"><p>Two <a href="#S_Dive_Management"><em>Dive Management</em></a> actions are available by tapping on the
-action buttons at the bottom of the <em>Dive List</em> page:
-To <a href="#S_Download"><em>Download dives from a dive computer</em></a>, tap the main action button. If you wish
-to <a href="#S_Add_Dive"><em>Manually add a dive</em></a>, tap the + button in the action bar. Both of these
-actions are described in detail below.</p></div>
-<div class="paragraph"><p>Tapping an existing dive on the list brings up a display of the <a href="#S_ViewDive"><em>Details View</em></a>
-for that dive including the dive profile, notes, and additional information.</p></div>
-<div class="imageblock" style="text-align:center;">
-<div class="content">
-<img src="mobile-images/DiveListAndDetails.jpg" alt="FIGURE: Dive list screen" />
+and down through your dive history.</p>
 </div>
+<div class="paragraph">
+<p>The Dive List consists of two types of entries:</p>
 </div>
-<div class="paragraph"><p>A tap and hold on a dive or a trip header opens the context menu for that entry.</p></div>
-<div class="paragraph"><p>For a dive this allows moving the dive into or out of trips or between trips, deleting
-the dive or showing the dive on an integrated map viewer (assuming the dive has the
-necessary GPS information). The context menu also allows access to the undo and redo
-system that allows you to step backwards and forwards through recent changes.</p></div>
-<div class="paragraph"><p>For a trip header the context menu gives you an option to edit the trip title (typically
-the trip location) and some quick notes for the trip.</p></div>
-<div class="sect2">
-<h3 id="_filter_the_dive_list">6.1. Filter the dive list</h3>
-<div style="clear:both;"></div>
-<div class="imageblock" style="float:right;">
-<div class="content">
-<img src="mobile-images/FilterButton.jpg" alt="FIGURE: Filter button" />
-</div>
+<div class="olist arabic">
+<ol class="arabic">
+<li>
+<p><strong>Trip headers</strong>. A trip header is a line describing the year and month during which a dive trip
+took place, as wel as the geographical area of the trip. The second line in the lefthand image below indicates that a 10-dive trip
+was made to Guinjata, Moçambique during December 2016.</p>
+</li>
+<li>
+<p><strong>Individual dive records</strong>. Tapping a trip header expands the dive list to show (or hide) the individual dives performed during the trip. Each dive is represented by a dive record. By default the dives during the last trip are listed with older dives at the bottom and recent dives at the top of the list. In the lefthand image below the last dive during
+the Guinjata trip was in the Inhambane Estuary.</p>
+</li>
+</ol>
 </div>
-<div class="paragraph"><p>The left action button shows three horizontal lines of declining length, symbolizing a filter.
-When you tap this button, a text entry line appears at the top of screen which will allow you to
-enter a filter search term that is either used in a full text search, a search just of the people
-involved in a dive (in the Divemaster and Buddy fields), or a search of the tags you have used
-to classify your dives. Tapping the filter button again clears the filter and shows the full
-dive list.</p></div>
-<div class="imageblock" style="text-align:center;">
+<div class="imageblock text-center">
 <div class="content">
-<img src="mobile-images/FilteredDivelist.jpg" alt="FIGURE: Filter tool" />
-</div>
+<img src="mobile-images/Divelist2.jpg" alt="FIGURE: Dive list screen">
 </div>
 </div>
 <div class="sect2">
-<h3 id="S_View_Dive">6.2. View a dive</h3>
-<div class="paragraph"><p>When you tap on a dive in the <em>Dive List</em>, a <em>Dive Details</em> page with the dive profile
-and many important details about the dive is opened. You can use a pinch gesture
+<h3 id="S_View_Dive">5.1. View a dive: the Details view</h3>
+<div class="paragraph">
+<p>When you tap on a dive in the <em>Dive List</em>, a <em>Dive Details</em> page with the dive profile
+and many important details about the dive is opened (image on right above). You can use a pinch gesture
 to zoom into the profile. Tapping and holding with one finger (until
 the profile becomes translucent) allows you
-to pan the profile and see more details in specific parts of the profile.</p></div>
-<div class="paragraph"><p>You can view other dives by swiping the <em>Details view</em> to the right (for the
+to pan the profile and see more details in specific parts of the profile.</p>
+</div>
+<div class="paragraph">
+<p>You can view other dives by swiping the <em>Details view</em> to the right (for the
 previous dive) or to the left (next dive).
 Using the Action Bar, it is also possible to delete the dive (tap the Trash Icon
-on the Action Bar) or to view the dive location on an integrated map viewer.</p></div>
-<div class="paragraph"><p>The context menu (accessible by tapping on the vertical three dots in the lower right corner of the
+on the Action Bar) or to view the dive location on an integrated map viewer.</p>
+</div>
+<div class="paragraph">
+<p>The context menu (accessible by tapping on the vertical three dots in the lower right corner of the
 screen) offers additional options to move dives between trips, the same delete and map options
 already mentioned, and access to the undo and redo facility that allows you to step backwards and
-forwards through recent changes.</p></div>
+forwards through recent changes.</p>
+</div>
 </div>
 <div class="sect2">
-<h3 id="_viewing_the_location_of_a_dive_on_a_map">6.3. Viewing the location of a dive on a map</h3>
-<div class="imageblock" style="text-align:center;">
+<h3 id="_viewing_the_location_of_a_dive_on_a_map">5.2. Viewing the location of a dive on a map</h3>
+<div class="imageblock text-center">
 <div class="content">
-<img src="mobile-images/DiveSiteMap.jpg" alt="FIGURE: Map of dive site" />
+<img src="mobile-images/DiveSiteMap.jpg" alt="FIGURE: Map of dive site">
 </div>
 </div>
-<div class="paragraph"><p>In the <em>Details View</em>, you can either tap the name of a dive site
+<div class="paragraph">
+<p>In the <em>Details View</em>, you can either tap the name of a dive site
 or the GPS pin on the
 left hand side of the <em>Action Button</em> at the bottom of the screen in order
 to open a map with the dive site in an integrated map viewer.
 This of course is only possible if the dive site is associated with GPS
-information.</p></div>
+information.</p>
+</div>
 </div>
 <div class="sect2">
-<h3 id="S_Edit_Dive">6.4. Edit a dive</h3>
-<div class="imageblock" style="text-align:center;">
+<h3 id="_filter_the_dive_list">5.3. Filter the dive list</h3>
+<div class="paragraph">
+<p>By default, all the dives in the dive log are shown in the dive list. After several years your dive
+log can become quite long and, sometimes, you might like to list only the dives of a particular
+type, e.g. those at a particular dive site or those with a specific buddy or dive master. Use the
+Filter to achieve this. The filter mechanism searches through all the information for each dive,
+looking for one or more key words. Only the dives containing these key words are listed in the dive
+list. To Filter the dive list, tap the Filter action button:</p>
+</div>
+<div class="paragraph">
+<p>unfloat::[]</p>
+</div>
+<div class="imageblock text-center">
 <div class="content">
-<img src="mobile-images/DiveDetailsEdit.jpg" alt="FIGURE: Dive edit screen" />
+<img src="mobile-images/FilterButton.jpg" alt="FIGURE: Filter button">
 </div>
 </div>
-<div class="paragraph"><p>At the bottom of the <em>Dive Details</em> screen, the action button is a pencil.
-Tapping the pencil button changes the page and enables editing
-the dive details, e.g. adding text to the dive notes
-or changing the names or values of some of the information (see image on left).
-It may be necessary to scroll the window to access all the available fields.
-At the bottom of the edit screen is a <em>Save</em> action button. Tap this to save
-the new information, after which the dive list screen is
-updated and displayed. To cancel any edits, tap the Android <em>Back</em> Button or
-the application back button at the top left of the screen on iOS.</p></div>
+<div class="paragraph">
+<p>at the bottom of the dive list. A text box appears at the top of the screen (image below). Type the
+word(s) that you would like to use as a filter.</p>
 </div>
-<div class="sect2">
-<h3 id="_deleting_a_dive">6.5. Deleting a dive</h3>
-<div class="paragraph"><p>You can delete a dive from the dive list by long-pressing a dive and selecting delete in the context menu.
-You can also delete a dive from the <em>Details View</em> by tapping on the trash can icon on the right
-side of the <em>Action Button</em></p></div>
-<div class="paragraph"><p>If you deleted the wrong dive by mistake you can easily undo the operation in the context menu.</p></div>
-<div class="imageblock" style="text-align:center;">
+<div class="imageblock text-center">
 <div class="content">
-<img src="mobile-images/UndoDelete.jpg" alt="FIGURE: Undo delete dive" />
+<img src="mobile-images/Filter.jpg" alt="FIGURE: Filter tool">
+</div>
 </div>
+<div class="paragraph">
+<p>Three filter modes exist. "Fulltext" searches all text strings. Selecting "People" lists buddies and
+dive masters, while "Tags" only filters for tags containing the given text. Filters are not case-sensitive.
+To clear the filter, remove the key words from the text box and select the Filter action button to
+switch off filtering. The image above represents a full-text search for dives with the word "nitrox".</p>
 </div>
 </div>
 </div>
 </div>
 <div class="sect1">
-<h2 id="S_Dive_Management">7. Dive Management</h2>
+<h2 id="S_Dive_Management">6. Dive List Management and adding dive information</h2>
 <div class="sectionbody">
-<div class="paragraph"><p>A central  part of <em>Subsurface-mobile</em> is the ability to store the dive
-log using the <em>Subsurface</em> cloud storage.
-This provides security against loss or damage of the dive information in a local copy
-and allows the desktop version of <em>Subsurface</em> to
-access changes made using the mobile device. This feature is accessed
-through the <em>Dive management</em> option in the main menu.</p></div>
 <div class="sect2">
-<h3 id="S_Add_Dive">7.1. Manually adding a new dive to the dive list</h3>
-<div class="paragraph"><p>You can manually add a dive to the existing dive list. On the dive list
-tap the "plus"-icon in the action bar, or use the
-main menu and tap <em>Dive management  &#8594;  Add dive manually</em>. This opens a screen that is
-identical to the editing screen described above. When a dive is added manually, you
+<h3 id="S_Add_Dive">6.1. Manually adding a new dive to the dive list</h3>
+<div class="paragraph">
+<p>This <a href="https://www.youtube.com/watch?v=sF8KB_r0rFw"><strong>video-tutorial</strong></a> explains how to add information to a
+manually-entered dive.</p>
+</div>
+<div class="paragraph">
+<p>You can manually add a dive to the existing dive list. On the dive list
+tap the "plus" sign in the action bar, or use the
+main menu and tap <em>Dive management  &#8594;  Add dive manually</em>. This opens  a screen that is
+identical to the editing screen discussed above. When a dive is added manually, you
 cannot directly add a dive profile from a dive computer. However, if you do not use a
 dive computer, the duration, depth and several other bits of information about
 the new dive can be entered. The <em>Action button</em> at the bottom of the screen
 contains a disk symbol. Tap this to save the new dive. To cancel any edits, tap the <em>Back</em> button.
 The left-hand image below shows a screenshot of a dive being created and the right-hand image shows
-the same dive in <em>Details View</em>.</p></div>
-<div class="imageblock" style="text-align:center;">
+the same dive in <em>Details View</em>. After editing the dive information, the dive trip information
+needs to be edited as described in the section above on <a href="#S_Divetrip">Dive trip editing</a>.</p>
+</div>
+<div class="imageblock text-center">
 <div class="content">
-<img src="mobile-images/ManualAddDive.jpg" alt="FIGURE: Manual dive entry screen" />
+<img src="mobile-images/Manualdive.jpg" alt="FIGURE: Manual dive entry screen">
 </div>
 </div>
 </div>
 <div class="sect2">
-<h3 id="S_Download">7.2. Download dives from a dive computer</h3>
-<div class="paragraph"><p>There are several ways to get to the <em>Download Page</em>. You can either tap on the main <em>Action Button</em> on
+<h3 id="S_Download">6.2. Download dives from a dive computer</h3>
+<div class="paragraph">
+<p>There are several ways to get to the <em>Download Page</em>. You can either tap on the main <em>Action Button</em> on
 the bottom of the <em>Dive List</em>, or you can select <em>Dive management &#8594;  Download from DC</em> in the main menu.
 On Android devices, when you plug in a USB serial cable for a dive computer, the <em>Download Page</em> will be
-opened automatically.</p></div>
-<div class="paragraph"><p>The download feature on smartphones supports only a limited number of dive computers. On
+opened automatically. A screen is shown requiring that the user specify
+the names of the vendor and model of the dive computer. For instance, when using a Shearwater Petrel dive
+computer, the vendor is <em>Shearwater</em> and the Dive computer name is <em>Petrel</em> (see image on the left, below).
+<strong>Caveats:</strong> The download feature in smartphones supports only a limited number of dive computers. On
 Android devices these are typically dive computers using a serial USB interface
 using a USB OTG cable or a simple USB C-A adapter on newer devices.
 Android devices also support Bluetooth dive computers that
 are supported in <em>Subsurface</em> on the desktop. Both Android and iOS devices allow direct
 download of dive data from a handful of Bluetooth LE enabled dive
-computers.</p></div>
-<div class="paragraph"><p>Use the <em>Vendor name</em> and <em>Dive Computer</em> drop-downs to pick the correct
-dive computer.
-For instance, when using a Shearwater Petrel dive
-computer, the vendor is <em>Shearwater</em> and the product is <em>Petrel</em>(see left image below -
-section Start the download).</p></div>
-<div class="paragraph"><p>TODO: image of DL missing - or link to the 7.2.3 Start the download</p></div>
-<div class="paragraph"><p>When downloading from multiple different dive computers, shortcut
+computers. Use the <em>Vendor name</em> and <em>Dive Computer</em> drop-downs to pick the correct
+dive computer. When downloading from multiple different dive computers, shortcut
+buttons appear below the drop-downs to easily switch between them. In the <a href="#S_Settings"><em>Settings</em></a> menu
+you can remove these buttons, a useful feature for removing buttons of dive
+computers that are not used any more. Achieve this by selecting the option
+<em>Forget remembered dive computers</em> in the <a href="#S_Settings"><em>Settings</em></a> menu.
+After all these caveats, let us proceed with download.</p>
+</div>
+<div class="paragraph">
+<p><strong>TODO: image of DL missing - or link to the 7.2.3 Start the download</strong></p>
+</div>
+<div class="paragraph">
+<p>When downloading from multiple different dive computers, shortcut
 buttons appear below the drop-downs to easily switch between them. In the <a href="#S_Settings"><em>Settings</em></a> menu
 you can remove these buttons, a useful feature for removing buttons of dive
 computers that you do not use any more. Achieve this by selecting the option
-<em>Forget remembered dive computers</em> in the <a href="#S_Settings"><em>Settings</em></a> menu.</p></div>
+<em>Forget remembered dive computers</em> in the <a href="#S_Settings"><em>Settings</em></a> menu.</p>
+</div>
 <div class="sect3">
-<h4 id="_download_from_usb_serial_dive_computers">7.2.1. Download from USB serial dive computers</h4>
-<div class="paragraph"><p>This feature is not supported on iOS.</p></div>
-<div class="tableblock">
-<table rules="all"
-width="100%"
-frame=""
-cellspacing="0" cellpadding="4">
-<col width="50%" />
-<col width="50%" />
+<h4 id="_download_from_usb_serial_dive_computers">6.2.1. Download from USB serial dive computers</h4>
+<div class="paragraph">
+<p>This feature is not supported on iOS.</p>
+</div>
+<table class="tableblock frame-None grid-all stretch">
+<colgroup>
+<col style="width: 50%;">
+<col style="width: 50%;">
+</colgroup>
 <tbody>
 <tr>
-<td align="left" valign="top"><div><div class="imageblock" style="text-align:center;">
+<td class="tableblock halign-left valign-top"><div class="content"><div class="imageblock text-center">
 <div class="content">
-<img src="mobile-images/USB-OTG.jpg" alt="FIGURE: USB-OTG cable" />
+<img src="mobile-images/USB-OTG.jpg" alt="FIGURE: USB-OTG cable">
 </div>
 </div></div></td>
-<td align="left" valign="top"><p class="table">Most current Android devices now have a USB
+<td class="tableblock halign-left valign-top"><p class="tableblock">Most current Android devices now have a USB
 Type C port and come with a simple A-to-C adapter plug, which lets you plug in
 the dive computer cable into the phone or tablet.
 For older Android devices with micro USB connector you will need to plug the USB
@@ -854,333 +1040,501 @@ but usually all modern Android devices with a USB C plug can be used with a USB
 </tr>
 </tbody>
 </table>
-</div>
-<div class="paragraph"><p><em>Subsurface-mobile</em> remembers the settings for dive computers that
+<div class="paragraph">
+<p><em>Subsurface-mobile</em> remembers the settings for dive computers that
 have been successfully used (image on right, below). These appear
 as buttons under a heading "<em>Previously used dive computers</em>".
 Select the appropriate button. Having connected the USB dive computer to the
 <em>Subsurface</em> computer and having selected the appropriate vendor and dive computer,
-ensure that the Connection text box shows the corresponding connection. For a small number of dive
+ensure that the <em>Connection</em> text box shows the corresponding connection. For a small number of dive
 computers the connection name shows the dive computer vendor, for most only the cable chipset vendor
-(and USB connection number) is shown. Most users of course only connect one USB dive computer to
-their Android device and then things are fairly straightforward. A dialog will pop up and ask if
-you want to use <em>Subsurface-mobile</em> to connect to the device. If you confirm, then <em>Subsurface-mobile</em> will
-open to the dive computer download screen with the correct connection selected (and if it can deduce
-the correct dive computer based on the cable used, even that information is already pre-filled).</p></div>
+(and USB connection number) is shown. Most users only connect one USB dive computer to
+their Android device and then things are fairly straightforward. A dialog appears asking if
+you want to use <em>Subsurface-mobile</em> to connect to the device. If you confirm, then <em>Subsurface-mobile</em>
+opens the dive computer download screen with the correct connection selected (and if it can deduce
+the correct dive computer based on the cable used, even that information is already pre-filled).</p>
+</div>
 </div>
 <div class="sect3">
-<h4 id="_download_from_bt_blw_dive_computers">7.2.2. Download from BT/BLW dive computers</h4>
-<div class="paragraph"><p>The process for Bluetooth download is slightly different between Android and iOS.</p></div>
-<div class="paragraph"><p>In our testing we got the best results on iOS when the dive computer was
-in Bluetooth mode before <em>Subsurface-mobile</em> is started. On most dive
-computers this is done through a menu entry, others (like the Suunto
-models) always respond to Bluetooth LE requests. However, on Android devices,
-you should first establish a link between the
-Bluetooth or Bluetooth LE dive computer and the mobile device using
-Android utilities. See below for more details.</p></div>
-<div class="paragraph"><p>For Bluetooth-equipped dive computers and Android devices, establish a Bluetooth connection between the dive computer and the
+<h4 id="_download_from_bluetooth_and_bluetooth_le_dive_computers">6.2.2. Download from Bluetooth and Bluetooth LE dive computers</h4>
+<div class="paragraph">
+<p>This <a href="https://www.youtube.com/watch?v=DCi70WZMTws"><strong>video-tutorial</strong></a> demonstrates downloading dives from a
+Bluetooth-equipped dive computer.</p>
+</div>
+<div class="paragraph">
+<p>The process for Bluetooth download differs between Android and iOS. In <strong>iOS</strong> the best
+results are obtained when the dive computer was
+in Bluetooth LE mode before <em>Subsurface-mobile</em> is started. On most dive
+computers this is done through a menu entry, others (e.g. Suunto) always respond to Bluetooth LE requests.</p>
+</div>
+<div class="paragraph">
+<p>In contrast, for Bluetooth-equipped dive computers and <strong>Android</strong> devices, first establish a Bluetooth connection
+between the dive computer and the
 mobile device using Android system tools to achieve pairing.
 For many Android devices,
 the Settings &#8594; Bluetooth tool of Android is probably appropriate.
-<em>Subsurface-mobile</em> performs communication using both Bluetooth and Bluetooth-low-energy (BLE).
-The best choice of Bluetooth communication is often made by the software and the user need not be concerned with this.
-For dive computers with both Bluetooth and BLE, a separate button is presented on the download
+<em>Subsurface-mobile</em> performs communication using both Bluetooth and Bluetooth LE (BLE).
+The best choice of Bluetooth communication is often made by the software and the user need not be concerned
+with this.
+For dive computers with both Bluetooth and BLE, a separate dive computer button is presented on the download
 screen for each mode of communication, allowing a choice. Use the <em>Connection</em> value to distinguish between the
-two options. In the image on the below right, there are three buttons labeled "Shearwater Petrel 2". These represent two Shearwater Petrel dive computers, one of which can communicate in both Bluetooth as well as BLE. The <em>Connection</em>
-information indicates that the Petrel with no BLE is selected.</p></div>
+two options. In the image on the right, below, there are three buttons labeled "Shearwater Petrel 2".
+These represent two Shearwater Petrel dive computers, one of which can communicate in both Bluetooth as well as BLE.
+The <em>Connection</em> information in the image below indicates that the Petrel with no BLE is selected. For
+Bluetooth LE dive computers, the <em>Connection</em> value has an "LE" prefix.</p>
+</div>
+<div class="paragraph">
+<p>This <a href="https://www.youtube.com/watch?v=4MtQqm4o7bw"><strong>video-tutorial</strong></a> demonstrates setting up a
+Bluetooth connection with an Android device.</p>
+</div>
 </div>
 <div class="sect3">
-<h4 id="_start_the_download">7.2.3. Start the download</h4>
-<div class="paragraph"><p>With communication between dive computer and <em>Subsurface-mobile</em>
+<h4 id="_start_the_download">6.2.3. Start the download</h4>
+<div class="paragraph">
+<p>With communication between dive computer and <em>Subsurface-mobile</em>
 having been set up, tap the <em>Download</em> button. Be patient because the download can take a while - with many
-long dives and a slow BLE connection we have seen download times of 45 minutes or longer. But usually downloading
+long dives and a slow Bluetooth LE connection we have seen download times of 45 minutes or longer. But usually
+downloading
 a day&#8217;s worth of diving happens reasonably quickly.
 The downloaded dives appear in the bottom part of the screen,
-the most recent dive at the top (see right image below).</p></div>
-<div class="paragraph"><p>Each dive has a check-box on the left hand side, used for selecting which dives you want to add to the
-<em>Subsurface-mobile</em> dive list: dives that are not checked are ignored. Once you picked the dives
+the most recent dive at the top (see right image below).</p>
+</div>
+<div class="paragraph">
+<p>Each dive has a check-box on the left hand side, used for selecting which dives you want to add to the
+<em>Subsurface-mobile</em> dive list: dives that are not checked are ignored. Once you have picked the dives
 you want to add to the dive list, tap the button at the bottom left labeled <em>Accept</em>. The selected dives will
 now appear as part of
-the <em>Subsurface-mobile</em> dive list. The downloaded dive information can be edited as described in the section
-above <a href="#S_Edit_Dive">Edit a dive</a>.</p></div>
-<div class="imageblock" style="text-align:center;">
+the <em>Subsurface-mobile</em> dive list.</p>
+</div>
+<div class="imageblock text-center">
 <div class="content">
-<img src="mobile-images/DC-Download.jpg" alt="FIGURE: DC download screen" />
+<img src="mobile-images/DC-Download.jpg" alt="FIGURE: DC download screen">
 </div>
 </div>
 </div>
 </div>
 <div class="sect2">
-<h3 id="_manually_sync_the_dive_log_with_the_em_subsurface_cloud_em">7.3. Manually sync the dive log with the <em>Subsurface Cloud</em></h3>
-<div class="paragraph"><p>As the name indicates, this ensures that the local changes on the mobile device and changes
+<h3 id="S_Edit_Dive">6.3. Edit the dive information</h3>
+<div class="paragraph">
+<p>This <a href="https://www.youtube.com/watch?v=pE3ujzGw_7o"><strong>video-tutorial</strong></a> explains how to add information about a dive.</p>
+</div>
+<div class="imageblock text-center">
+<div class="content">
+<img src="mobile-images/Editdive.jpg" alt="FIGURE: Dive edit screen">
+</div>
+</div>
+<div class="paragraph">
+<p>At the bottom of the <em>Dive Details</em> screen the action button is a pencil.
+Tapping the pencil button changes the page and enables edit boxes that allow
+modifying the existing dive information, e.g. adding text to the dive notes
+or changing the names or values of some of the information (see image above).
+It may be necessary to scroll the window to access all the information.
+At the bottom of the edit screen is a <em>Save</em> action button. Tap this to save
+the new information, after which the dive list screen is
+updated and shown. To cancel any edits, tap the Android <em>Back</em> Button or
+the application back button at the top left of the screen on iOS.</p>
+</div>
+</div>
+</div>
+</div>
+<div class="sect1">
+<h2 id="S_Divetrip">7. Edit the dive trip information</h2>
+<div class="sectionbody">
+<div class="paragraph">
+<p>When a new dive(s) is entered manually or downloaded from dive computer, a trip header is created at the
+top of the dive list only showing the month and the year of the dive trip as well as the number of dives
+during the trip (image on left below, showing a trip header with "May 2018", the trip comprising two dives).
+You would probably like to include information about the place
+where the trip took place, e.g. "Channel Islands" or the dive charter company used. In this case long-press
+the dive trip header to activate the context menu. Select the option "Edit trip details" to open a panel
+for typing information about the trip (image on right, below). Having provided the required information,
+tap the <em>Save</em> action button at the bottom of the screen. This returns you to the dive list, showing some of
+the dive trip information that has just been provided.</p>
+</div>
+<div class="imageblock text-center">
+<div class="content">
+<img src="mobile-images/TripDetails.jpg" alt="FIGURE: Edit trip details">
+</div>
+</div>
+<div class="sect2">
+<h3 id="_deleting_a_dive">7.1. Deleting a dive</h3>
+<div class="paragraph">
+<p>Delete a dive from the dive list by long-pressing a dive and selecting delete in the context menu.
+If the wrong dive was deleted by mistake you can easily undo the operation by using the context menu.</p>
+</div>
+<div class="imageblock text-center">
+<div class="content">
+<img src="mobile-images/Delete_undo.jpg" alt="FIGURE: Undo delete dive">
+</div>
+</div>
+</div>
+</div>
+</div>
+<div class="sect1">
+<h2 id="_interacting_with_the_cloud_storage">8. Interacting with the cloud storage</h2>
+<div class="sectionbody">
+<div class="sect2">
+<h3 id="_manually_sync_the_dive_log_with_the_subsurface_cloud">8.1. Manually sync the dive log with the <em>Subsurface Cloud</em></h3>
+<div class="paragraph">
+<p>As the name indicates, this ensures that the local changes on the mobile device and changes
 made by other devices and computers to the data stored in the <em>Subsurface Cloud</em> are synchronized.
 It is highly recommended to sync with cloud storage after downloading new dives from a dive computer
-or manually adding or editing dive information on the mobile device.</p></div>
-<div class="paragraph"><p>This can also be triggered by pulling down (and briefly holding) the <em>Dive List</em>.</p></div>
+or after manually adding or editing dive information on the mobile device.
+This can also be triggered by pulling down (and briefly holding) the topmost entry of the <em>Dive List</em>.</p>
+</div>
 </div>
 <div class="sect2">
-<h3 id="_enable_cloud_auto_sync">7.4. Enable cloud auto sync</h3>
-<div class="paragraph"><p>By default <em>Subsurface-mobile</em> runs offline and only syncs the dive list
+<h3 id="_enable_cloud_auto_sync">8.2. Enable cloud auto sync</h3>
+<div class="paragraph">
+<p>By default <em>Subsurface-mobile</em> runs offline and only syncs the dive list
 with cloud storage when explicitly told to do so (see the previous entry above).
-You can choose to always sync with the cloud servers. This is not
+You can choose to always sync with the cloud server. This is not
 recommended unless you are in
-an area with a fast and reliable internet connection, as otherwise
+an area with a fast and reliable Internet connection, as otherwise
 <em>Subsurface-mobile</em> might appear to hang between operations as it tries to
 connect to the cloud server. Selecting <em>Enable cloud auto sync</em> causes
 the local dive log to be synchronized with the copy in the cloud after most changes as well
 as (on Android) every time that <em>Subsurface-mobile</em> is closed. iOS doesn&#8217;t support the concept
 of closing an app (you can just kill it, which doesn&#8217;t allow for a final sync with the cloud).
 In general it is safer to manually sync with the cloud once you are done making changes in
-<em>Subsurface-mobile</em>.</p></div>
+<em>Subsurface-mobile</em>.</p>
 </div>
-<div class="sect2">
-<h3 id="_dive_summary">7.5. Dive Summary</h3>
-<div class="paragraph"><p>The <em>Dive Summary</em> page provides a very simple overview of your diving activities - which can for example
+</div>
+</div>
+</div>
+<div class="sect1">
+<h2 id="_dive_summary">9. Dive Summary</h2>
+<div class="sectionbody">
+<div class="paragraph">
+<p>The <em>Dive Summary</em> page provides a very simple overview of your diving activities - which can for example
 be useful when documenting total dive experience and recent dive activity for a dive center at
-the beginning of a dive trip.</p></div>
-<div class="paragraph"><p>The summary page lists the date of your first dive in the dive list as well as your most recent dive.
+the beginning of a dive trip.</p>
+</div>
+<div class="paragraph">
+<p>The summary page lists the date of your first dive in the dive list as well as your most recent dive.
 It also provides two columns of data for selectable time ranges (by default all dives in the dive list
-and the dives during the last six months.</p></div>
+and the dives during the last six months.</p>
 </div>
 <div class="sect2">
-<h3 id="_export">7.6. Export</h3>
-<div class="paragraph"><p>The <em>Export</em> feature is somewhat experimental. On Android it only allows the upload of your dive list
-to two websites (divelogs.de and diveshare). On iOS it also allows local file based exports as <em>Subsurface</em>
-specific XML files (both for dives and dive sites) as well as <em>UDDF</em>.</p></div>
-<div class="paragraph"><p>Tapping on <em>Next</em> opens an additional page for login information (or a file selection dialog).</p></div>
+<h3 id="_export">9.1. Export</h3>
+<div class="paragraph">
+<p>The <em>Export</em> feature is somewhat experimental. On Android it only allows the upload of your dive list
+to two websites (<em>divelogs.de</em> and <em>diveshare</em>). On iOS it also allows local file based exports as <em>Subsurface</em>
+specific XML files (both for dives and dive sites) as well as <em>UDDF</em>.</p>
+</div>
+<div class="paragraph">
+<p>Tapping on <em>Next</em> opens an additional page for login information for the destination website (or a file selection dialog).</p>
+</div>
 </div>
 </div>
 </div>
 <div class="sect1">
-<h2 id="_location">8. Location</h2>
+<h2 id="_obtaining_dive_site_locations_using_the_gps">10. Obtaining dive site locations using the GPS</h2>
 <div class="sectionbody">
-<div class="paragraph"><p>The fact that almost all smartphones have GPS facilities allows
+<div class="paragraph">
+<p>The fact that almost all smartphones have GPS facilities allows
 <em>Subsurface-mobile</em> to record
-the locations of dives. <strong>IMPORTANT: GPS-derived coordinates on a smartphone
+the locations of dives.</p>
+</div>
+<div class="sidebarblock">
+<div class="content">
+<div class="admonitionblock important">
+<table>
+<tr>
+<td class="icon">
+<img src="./images/icons/images/icons/important.png" alt="Important">
+</td>
+<td class="content">
+<strong>Accuracy of GPS coordinates</strong>
+</td>
+</tr>
+</table>
+</div>
+<div class="paragraph">
+<p>GPS-derived coordinates on a smartphone
 are not always accurate and can have an error greater than 1 km. GPS accuracy
 is determined by the hardware and software of the
 smartphone as well as by the GPS settings selected within Android/iOS.
-As of Android V6 select Android <em>Settings &#8594; Communication &#8594; Location &#8594; High accuracy.</em></strong>
+As of Android V6 (Marshmallow) select Android <em>Settings &#8594; Communication &#8594; Location &#8594; High accuracy</em>*.
 If the smartphone is taken on the boat
-during a dive, locations will be automatically recorded at regular intervals.
-These locations can then be applied to dives in the dive list as described in following chapters.</p></div>
+during a dive, locations can be automatically recorded at regular intervals.
+These locations can then be applied to dives in the dive list as described below</p>
+</div>
+</div>
+</div>
+<div class="paragraph">
+<p>To collect dive site coordinates four step are required:</p>
+</div>
 <div class="sect2">
-<h3 id="S_ConfigureGPS">8.1. Configuring the GPS service</h3>
-<div class="paragraph"><p>For most users, the defaults for tracking GPS locations will be
+<h3 id="S_ConfigureGPS">10.1. Configuring the GPS service</h3>
+<div class="paragraph">
+<p>For most users, the defaults for tracking GPS locations are
 appropriate. If you would like to change them, go to
 the <em>Main Menu</em>, select the <a href="#S_Settings"><em>Settings</em></a> screen, and open
-the <em>Advanced</em> area on that page. Here you will find the section for
+the <em>Advanced</em> area on that page where there is a section for
 configuring the GPS service (see image below). GPS location data
 are collected at regular intervals, e.g. every 5 minutes, or at regular
 distances, e.g. after the boat has moved more than 200m, or a combination of
 both of these approaches. Provide the appropriate information and
-tap the <em>Back</em> button. The program is now ready to collect GPS positions.</p></div>
-<div class="imageblock" style="text-align:center;">
+tap the <em>Back</em> button. The program is now ready to collect GPS positions.</p>
+</div>
+<div class="imageblock text-center">
 <div class="content">
-<img src="mobile-images/GPSConfig.jpg" alt="FIGURE: GPS configure" />
+<img src="mobile-images/GPSConfig.jpg" alt="FIGURE: GPS configure">
 </div>
 </div>
 </div>
 <div class="sect2">
-<h3 id="_collecting_gps_positions">8.2. Collecting GPS positions</h3>
-<div class="tableblock">
-<table rules="all"
-width="100%"
-frame=""
-cellspacing="0" cellpadding="4">
-<col width="50%" />
-<col width="50%" />
+<h3 id="_collecting_gps_positions">10.2. Collecting GPS positions</h3>
+<table class="tableblock frame-None grid-all stretch">
+<colgroup>
+<col style="width: 50%;">
+<col style="width: 50%;">
+</colgroup>
 <tbody>
 <tr>
-<td align="left" valign="top"><div><div class="imageblock" style="text-align:center;">
+<td class="tableblock halign-left valign-top"><div class="content"><div class="imageblock text-center">
 <div class="content">
-<img src="mobile-images/LocationMenu.jpg" alt="FIGURE: GPS start" />
+<img src="mobile-images/LocationMenu.jpg" alt="FIGURE: GPS start">
 </div>
 </div></div></td>
-<td align="left" valign="top"><p class="table">In the <em>Location</em> menu select <em>Run location service</em>.
+<td class="tableblock halign-left valign-top"><p class="tableblock">In the <em>Location</em> menu select <em>Run location service</em>.
 <em>Subsurface-mobile</em> starts to collect GPS locations automatically,
 following the preferences specified as described above. While the GPS
-location service is running, all menus have a GPS symbol at the bottom
-of the menu, indicating that the service is active. After returning from
+location service is running, all menus have a GPS symbol at the bottom,
+indicating that the service is active. After returning from
 the dive, deactivate the collection of GPS data by tapping
-the option <em>GPS &#8594; Disable location service</em>. The GPS symbol at the bottom
-of all menus disappears.</p>
-<p class="table">Collecting GPS fixes like this is relatively battery intensive and unfortunately
+the option <em>Location &#8594; Disable location service</em>. The GPS symbol at the bottom
+of menus disappears.</p>
+<p class="tableblock">Collecting GPS fixes like this is relatively battery intensive and unfortunately
 both Android and especially iOS have become increasingly aggressive in killing
 applications that are running while the screen is turned off. It may make sense
-to check between dives that the location service is still running.</p></td>
+to check between dives that the location service is still running. On the other hand
+the battery consumption of a smartphone with GPS enabled is often significantly less than
+the battery consumption of a dedicated GPS that is logging a track.</p></td>
 </tr>
 </tbody>
 </table>
 </div>
+<div class="sect2">
+<h3 id="_viewing_gps_data_collected_during_a_dive">10.3. Viewing GPS data collected during a dive</h3>
+<div class="paragraph">
+<p>From the <em>Location</em> submenu select <em>Show GPS fixes</em>. This brings
+up a list of GPS positions obtained by the location service (image
+below). Two actions are possible for each of the locations, enabled by
+dragging the right part of a location to the left. This exposes two
+options. Tapping the dustbin deletes this particular GPS location. Tapping the
+teardrop-shaped icon (actually a Google Maps pin) opens up Google Maps with a pin
+indicating the exact map position of the GPS record being viewed. The two above
+options can be hidden by drawing the GPS record to the right.</p>
+</div>
+<div class="imageblock text-center">
+<div class="content">
+<img src="mobile-images/gpsmanagement.jpg" alt="FIGURE: GPS management">
+</div>
+</div>
 </div>
 <div class="sect2">
-<h3 id="_applying_gps_data_to_dives_in_the_dive_log">8.3. Applying GPS data to dives in the dive log</h3>
-<div class="paragraph"><p>After running the location service during a dive trip, first either download
+<h3 id="_applying_gps_data_to_dives_in_the_dive_log">10.4. Applying GPS data to dives in the dive log</h3>
+<div class="paragraph">
+<p>After running the location service during a dive trip, first either download
 the dives from your dive computer or manually enter the dives into the dive list.
 Now you can apply the GPS positions to these dives.
 From the <em>Dive management</em> menu, tap <em>Apply GPS fixes</em>. The dive list contains the start
 and end times of each dive. Now, <em>Subsurface-mobile</em> applies the first
 GPS position that falls within the dive period of each dive. This results
-in a GPS position for each dive that is saved as part of the dive log.</p></div>
+in a GPS position for each dive that is saved as part of the dive log.</p>
 </div>
-<div class="sect2">
-<h3 id="_viewing_the_locations_of_all_dives_in_the_dive_list">8.4. Viewing the locations of all dives in the dive list</h3>
-<div class="imageblock" style="text-align:center;">
+</div>
+</div>
+</div>
+<div class="sect1">
+<h2 id="_viewing_the_locations_of_all_dives_in_the_dive_list">11. Viewing the locations of all dives in the dive list</h2>
+<div class="sectionbody">
+<div class="imageblock text-center">
 <div class="content">
-<img src="mobile-images/DivesMap.jpg" alt="FIGURE: Map of all dive sites" />
+<img src="mobile-images/DivesMap.jpg" alt="FIGURE: Map of all dive sites">
 </div>
 </div>
-<div class="paragraph"><p>The locations of all dives in the dive list can be viewed from the <em>Location</em> menu by selecting the <em>Map</em> option.
+<div class="paragraph">
+<p>The locations of all dives in the dive list can be viewed from the <em>Location</em> menu by selecting the <em>Map</em> option.
 A satellite image of the world is shown. At that scale no dive sites are shown. If you zoom into a particular region
 of the world the dive sites appear, indicated by red flags. Zooming in even closer indicates the names of each
-of the different dive sites.</p></div>
+of the different dive sites.</p>
 </div>
 </div>
 </div>
 <div class="sect1">
-<h2 id="S_Settings">9. Settings</h2>
+<h2 id="S_Settings">12. Specifying the settings for <em>Subsurface-mobile</em></h2>
 <div class="sectionbody">
-<div class="paragraph"><p>The <em>Settings</em> page allows the customization of <em>Subsurface-mobile</em>.
-It is grouped into four sections.</p></div>
+<div class="paragraph">
+<p>The <em>Settings</em> page allows the customization of <em>Subsurface-mobile</em>.
+It is grouped into four sections. Many of the settings involve dragging a slider switch to activate or deactivate a particular setting.</p>
+</div>
 <div class="sect2">
-<h3 id="_em_general_settings_em_section">9.1. <em>General settings</em> section</h3>
-<div class="imageblock" style="text-align:center;">
+<h3 id="_general_settings_section">12.1. <em>General settings</em> section</h3>
+<div class="imageblock text-center">
 <div class="content">
-<img src="mobile-images/GeneralSettings.jpg" alt="FIGURE: General Settings" />
+<img src="mobile-images/GeneralSettings.jpg" alt="FIGURE: General Settings">
 </div>
 </div>
 <div class="sect3">
-<h4 id="S_ChangeCloudAccount">9.1.1. Changing to a different <em>Subsurface</em> cloud account</h4>
-<div class="paragraph"><p>Some users have more than one <em>Subsurface</em> cloud account and have a need to switch between accounts.
-Tap on the <em>Change</em> button next to the <em>Email address</em> in the <em>General settings</em> on the <em>Settings</em> page.
+<h4 id="S_ChangeCloudAccount">12.1.1. Cloud status: Changing to a different <em>Subsurface</em> cloud account</h4>
+<div class="paragraph">
+<p>Some users have more than one <em>Subsurface</em> cloud account and need to switch between accounts.
+Tap on the <em>Change</em> button next to the <em>Email address</em> in the <em>General settings</em> on the <em>Settings</em> page (see image above).
 This opens the <em>Cloud credentials</em> page.
 Here you can change the email address and password used and then tap the button <em>Sign-in or register</em>.
-The appropriate dive list is shown.</p></div>
+The dive list of the newly-opened account is shown.</p>
+</div>
 </div>
 <div class="sect3">
-<h4 id="_default_cylinder">9.1.2. Default cylinder</h4>
-<div class="paragraph"><p>When manually entering a dive or when downloading from a dive computer that doesn&#8217;t explicitly
+<h4 id="_default_cylinder">12.1.2. Default cylinder</h4>
+<div class="paragraph">
+<p>When manually entering a dive or when downloading from a dive computer that doesn&#8217;t explicitly
 include cylinder size information (very few dive computers support that feature), <em>Subsurface-mobile</em>
-uses the cylinder that you select here as the default. If you don&#8217;t set this entry, no default
-cylinder is used.</p></div>
+uses the cylinder that you select here as the default, useful for divers that mostly use a particular
+type of cylinder. If you don&#8217;t set this entry, no default
+cylinder is used.</p>
+</div>
 </div>
 <div class="sect3">
-<h4 id="_forget_the_remembered_dive_computers">9.1.3. Forget the remembered dive computers</h4>
-<div class="paragraph"><p>Tap the <em>Forget</em> button to reset the dive computers that are stored in the up to four shortcut
-buttons on the <em>Download from dive computer</em> page.</p></div>
+<h4 id="_forget_the_remembered_dive_computers_used_during_dive_download">12.1.3. Forget the remembered dive computers used during dive download</h4>
+<div class="paragraph">
+<p>Tap the <em>Forget</em> button to reset the dive computers that are stored in the shortcut
+buttons on the <em>Download from dive computer</em> page.</p>
+</div>
 </div>
 </div>
 <div class="sect2">
-<h3 id="_em_theme_em_section">9.2. <em>Theme</em> section</h3>
+<h3 id="_theme_section">12.2. <em>Theme</em> section</h3>
 <div class="sect3">
-<h4 id="_color_theme">9.2.1. Color theme</h4>
-<div class="tableblock">
-<table rules="all"
-width="100%"
-frame=""
-cellspacing="0" cellpadding="4">
-<col width="50%" />
-<col width="50%" />
+<h4 id="_color_theme">12.2.1. Color theme</h4>
+<table class="tableblock frame-None grid-all stretch">
+<colgroup>
+<col style="width: 50%;">
+<col style="width: 50%;">
+</colgroup>
 <tbody>
 <tr>
-<td align="left" valign="top"><div><div class="imageblock" style="text-align:center;">
+<td class="tableblock halign-left valign-top"><div class="content"><div class="imageblock text-center">
 <div class="content">
-<img src="mobile-images/ThemeSettings.jpg" alt="FIGURE: Theme Settings" />
+<img src="mobile-images/ThemeSettings.jpg" alt="FIGURE: Theme Settings">
 </div>
 </div></div></td>
-<td align="left" valign="top"><p class="table">Besides the default blue color scheme, <em>Subsurface-mobile</em> supports two additional color schemes
+<td class="tableblock halign-left valign-top"><p class="tableblock">Besides the default blue color scheme, <em>Subsurface-mobile</em> supports two additional color schemes
 for users with different tastes (see image on left). All screenshots shown in this user manual are
-based on the blue default color scheme. You can pick the <em>pink</em> or <em>dark</em> color scheme from
+based on the blue default color scheme. You can pick the <em>pink</em> or <em>dark</em> color theme from
 the drop down menu.</p>
-<p class="table">The boxes below show the various color choices in the theme of your choice.</p></td>
+<p class="tableblock">The boxes in the image on the left show the various color choices in the theme of your choice.</p></td>
 </tr>
 </tbody>
 </table>
 </div>
-</div>
 <div class="sect3">
-<h4 id="_font_size">9.2.2. Font size</h4>
-<div class="paragraph"><p>Depending on the size and the screen resolution of your mobile device, you may prefer slightly
-smaller or slightly larger fonts. You can make this selection with the three buttons here.</p></div>
+<h4 id="_font_size">12.2.2. Font size</h4>
+<div class="paragraph">
+<p>Depending on the size and the screen resolution of your mobile device, you may prefer slightly
+smaller or slightly larger fonts. You can make this selection with the three buttons here.</p>
+</div>
 </div>
 </div>
 <div class="sect2">
-<h3 id="_em_units_em_section">9.3. <em>Units</em> section</h3>
-<div class="paragraph"><p>Here you can pick <em>metric</em>, <em>imperial</em>, or <em>personalized</em> units for the user interface.
+<h3 id="_units_section">12.3. <em>Units</em> section</h3>
+<div class="paragraph">
+<p>Here you can pick <em>metric</em>, <em>imperial</em>, or <em>personalized</em> units for the user interface.
 In most cases <em>Subsurface-mobile</em> should pick the regionally typical unit system for
-your location.</p></div>
+your location.</p>
+</div>
 </div>
 <div class="sect2">
-<h3 id="_em_advanced_em_section">9.4. <em>Advanced</em> section</h3>
-<div class="paragraph"><p>As the name indicates, most users will not need to make changes here.</p></div>
+<h3 id="_advanced_section">12.4. <em>Advanced</em> section</h3>
+<div class="paragraph">
+<p>As the name indicates, most users do not need to make changes here.</p>
+</div>
 <div class="sect3">
-<h4 id="_gps_location_service_thresholds">9.4.1. GPS location service thresholds</h4>
-<div class="paragraph"><p>As indicated above in the <em>Location</em> section of this manual, here you can set the distance and time
-thresholds for the <em>location service</em></p></div>
+<h4 id="_gps_location_service_thresholds">12.4.1. GPS location service thresholds</h4>
+<div class="paragraph">
+<p>As indicated above in the <em>Location</em> section of this manual, here you can set the distance and time
+thresholds for the <em>location service</em></p>
+</div>
 </div>
 <div class="sect3">
-<h4 id="_bluetooth">9.4.2. Bluetooth</h4>
-<div class="paragraph"><p>Since most devices tend to find a <em>LOT</em> of BT/BLE devices that aren&#8217;t dive computers, by
+<h4 id="_bluetooth">12.4.2. Bluetooth</h4>
+<div class="paragraph">
+<p>Since most mobile devices tend to find a <em>LOT</em> of BT/BLE devices that aren&#8217;t dive computers, by
 default <em>Subsurface-mobile</em> only shows known dive computers to make the connection list
-easier to use.</p></div>
-<div class="paragraph"><p>This setting tells <em>Subsurface-mobile</em> to temporarily show <em>ALL</em> Bluetooth and BLE devices as
+easier to use.</p>
+</div>
+<div class="paragraph">
+<p>This setting tells <em>Subsurface-mobile</em> to temporarily show <em>ALL</em> Bluetooth and BLE devices as
 possible connections on the <em>Download Page</em>, not just the ones recognized as dive computers.
 If you end up needing this option in order to select a dive computer that is not recognized
 by <em>Subsurface-mobile</em>, please send an email to the developers (using the <em>Help &#8594; Ask for support</em>
-menu entry) so we can add the missing code to recognize your dive computer as well.</p></div>
+menu entry) so we can add the missing code to recognize your dive computer as well.</p>
+</div>
 </div>
 <div class="sect3">
-<h4 id="_display">9.4.3. Display</h4>
-<div class="paragraph"><p><em>Subsurface-mobile</em> tries to make efficient use of the available screen real estate of your
+<h4 id="_display">12.4.3. Display</h4>
+<div class="paragraph">
+<p><em>Subsurface-mobile</em> tries to make efficient use of the available screen real estate of your
 mobile device. In most cases this leads to reasonable choices regarding the number of parallel
 columns that are being displayed. Some users have expressed the desire to force <em>Subsurface-mobile</em>
 to show only one column in portrait mode, even on large devices like tablets, as this results
 in a larger profile on the <em>Dive Details</em> page. Select this option if you want to enable that
-feature.</p></div>
+feature.</p>
+</div>
 </div>
 <div class="sect3">
-<h4 id="_activating_the_developer_sub_menu">9.4.4. Activating the Developer sub-menu</h4>
-<div class="paragraph"><p>This enables an additional menu item in the <em>Main</em> menu which contains options which are almost
-never useful for a regular users. Here you can find the detailed app log file as well as several
-test screens that help the developers track down issues you might encounter.</p></div>
+<h4 id="_activating_the_developer_sub_menu">12.4.4. Activating the Developer sub-menu</h4>
+<div class="paragraph">
+<p>This enables an additional menu item in the <em>Main</em> menu which contains options which are almost
+never useful for a regular user. Here you can find the detailed app log file as well as several
+test screens that help the developers track down issues you might encounter.</p>
+</div>
 </div>
 </div>
 </div>
 </div>
 <div class="sect1">
-<h2 id="_help">10. Help</h2>
+<h2 id="_help">13. Help</h2>
 <div class="sectionbody">
 <div class="sect2">
-<h3 id="_about">10.1. About</h3>
-<div class="paragraph"><p>This page shows you the exact version of <em>Subsurface-mobile</em> that you are running and provides
-a convenient way to copy the application logs to the clipboard.</p></div>
+<h3 id="_about">13.1. About</h3>
+<div class="paragraph">
+<p>This page shows you the exact version of <em>Subsurface-mobile</em> that you are running and provides
+a convenient way to copy the application logs to the clipboard.</p>
+</div>
 </div>
 <div class="sect2">
-<h3 id="_show_user_manual">10.2. Show user manual</h3>
-<div class="paragraph"><p>This menu entry opens the online version of this user manual in the native browser of your
-device. Unfortunately this option isn&#8217;t available if your device is offline.</p></div>
+<h3 id="_show_user_manual">13.2. Show user manual</h3>
+<div class="paragraph">
+<p>This menu entry opens the online version of this user manual in the native browser of your
+device. Unfortunately this option is not available without Internet access.</p>
+</div>
 </div>
 <div class="sect2">
-<h3 id="_ask_for_support">10.3. Ask for support</h3>
-<div class="paragraph"><p>This item opens your default email client with a pre-populated email to the <em>Subsurface</em>
+<h3 id="_ask_for_support">13.3. Ask for support</h3>
+<div class="paragraph">
+<p>This item opens your default email client with a pre-populated email to the <em>Subsurface</em>
 support alias and copies the app logs into that email. Simply add your question or the
-but that you are reporting and send us your message.</p></div>
+but that you are reporting and send us your message.</p>
+</div>
 </div>
 <div class="sect2">
-<h3 id="_reset_forgotten_em_subsurface_cloud_em_password">10.4. Reset forgotten <em>Subsurface Cloud</em> password</h3>
-<div class="paragraph"><p>As mentioned earlier in this manual, this is a convenient link to a web page that allows
-you to reset the password for your <em>Subsurface Cloud</em> account.</p></div>
+<h3 id="_reset_forgotten_subsurface_cloud_password">13.4. Reset forgotten <em>Subsurface Cloud</em> password</h3>
+<div class="paragraph">
+<p>As mentioned earlier in this manual, this is a convenient link to a web page that allows
+you to reset the password for your <em>Subsurface Cloud</em> account.</p>
+</div>
 </div>
 </div>
 </div>
 </div>
-<div id="footnotes"><hr /></div>
 <div id="footer">
 <div id="footer-text">
-Last updated
- 2020-03-30 14:00:22 PDT
+Last updated 2020-05-05 17:41:48 -0700
 </div>
 </div>
 </body>
-</html>
+</html>
+\ No newline at end of file
diff --git a/Documentation/mobile-manual-v3.txt b/Documentation/mobile-manual-v3.txt
index e7843dde1..77e877eeb 100644
--- a/Documentation/mobile-manual-v3.txt
+++ b/Documentation/mobile-manual-v3.txt
@@ -18,10 +18,9 @@ image::mobile-images/Banner.jpg["Banner",align="center"]
 
 // toc::[]
 
-[blue]#_Version 3.0.0, March 2020_#
+[blue]#_Version 3.0.5, May 2020_#
 
-Introducing _Subsurface-mobile_
------------------------------
+toc::[]
 
 Welcome to _Subsurface-mobile_, the mobile version of _Subsurface_, advanced dive logging
 software with extensive infrastructure to display, organize, and interpret scuba
@@ -31,7 +30,7 @@ open-source software (in simple terms that means that there is no commercial int
 them, all the source code needed to build them is available, there are no ads, no one is
 monetizing your data, etc).
 
-_Subsurface-mobile_ is a limited mobile version of _Subsurface_,
+_Subsurface-mobile_ is a limited mobile version of the desktop software _Subsurface_,
 aimed at Android and iOS smartphone and tablet devices.
 While the desktop version of _Subsurface_ shows much more detailed information
 for each dive, the mobile version allows a more accessible dive log on the go. For example,
@@ -39,14 +38,13 @@ you can prove dive experience on a dive trip to dive shops or review
 previous dives while on a dive boat. _Subsurface-mobile_ also allows
 the gathering of GPS locations where dives are performed.
 Assuming you have a dive computer that is supported by the mobile OS of
-your choice, _Subsurface-mobile_ even supports the downloading of dives from your dive computer.
+your choice, _Subsurface-mobile_ supports the downloading of dives from your dive computer.
 
-Users of _Subsurface-mobile_ typically use the
+Users of _Subsurface-mobile_ often use the
 mobile app together with the desktop version of _Subsurface_,  sharing dive information
 between the mobile and the desktop versions using a free _Subsurface Cloud_ account.
-However _Subsurface-mobile_ can
-also be used independently of the desktop version and does not require the use of cloud storage.
-
+However _Subsurface-mobile_ is a fully fledged application in its own right that can
+also be used independently of the desktop version with or without the use of cloud storage.
 _Subsurface-mobile_ allows:
 
 - Download and storage of dive log information using the _Subsurface_ cloud.
@@ -55,59 +53,57 @@ _Subsurface-mobile_ allows:
 - Download dive data directly from some dive computers.
 - Editing most of the dive log data, e.g. dive-master, buddy,
   equipment or notes relating to a dive.
-- Recording, storing and applying GPS positions to dives.
-- Viewing the locations of recorded GPS positions and of dives
+- Recording, storing and applying GPS positions to dive information.
+- Viewing the localities of recorded GPS positions and of dives
   on a map.
 
-These items are discussed in greater detail in the following chapters.
+These items are discussed in greater detail below.
 
 _Subsurface-mobile_ has some limitations compared to _Subsurface_:
 
 - Only a subset of the dive computers supported for download by the desktop
-version work with _Subsurface-mobile_. This limitation is
-mainly caused by hardware and OS limitations in the
+version work with _Subsurface-mobile_, this being determined
+by hardware and OS limitations in the
 two mobile platforms. On Android, a subset of
 dive computers that use USB serial cables or a Bluetooth / Bluetooth LE interface
-are accessible by _Subsurface-mobile_. On iOS, only Bluetooth LE based
+are accessible. On iOS, only Bluetooth LE based
 dive computers are supported.
 - No dive planner.
 - No printing.
-- No support for media embedded in dive profiles (_Subsurface_ allows to reference images and video clips directly in the dive profile).
+- No support for media embedded in dive profiles (_Subsurface_ allows access to
+  images and video clips directly from the dive profile).
 
 == Installing _Subsurface-mobile_ on your mobile device
 
 Find _Subsurface-mobile_ in the _Google Play Store_ or the _Apple App Store_
-and install it. For Android devices without access to the _Google Play Store_
+and install it. For Android devices without access to the _Google Play Store_,
 APKs can be found in the downloads folder on the _Subsurface_ website.
 
 == Getting Support
 
 The best place to get support is the https://subsurface-divelog.org/user-forum[_Subsurface_ User Forum]. Additionally, _Subsurface-mobile_ allows
-you to send a support email by tapping on _Ask for support_ in the _Help_ menu. This will open an
+you to send a support request by tapping on _Ask for support_ in the _Help_ menu. This will open an
 email to our in-app-support address in the native email client, including the relevant logs.
 
 == User Interface
 
 _Subsurface-mobile_ uses the same user interface philosophy on both Android and iOS, based on an
-open source project called _Kirigami_ that is maintained by the _KDE/Plasma_ development community.
-This user interface has a slightly different look and feel than many native Android and iOS apps,
-but we (the developers) feel that it is very easy and intuitive to work with.
-
-On every screen you have access to the _Main menu_ through a _Hamburger_ button (three short
-horizontal lines) in the lower left corner. Additionally, the _Main menu_ can be opened by swiping
-towards the right from the very left edge of the screen. The entries in the main menu are all explained
-starting in section xref:S_Dive_Management[_Dive Management_].
+open source project called _Kirigami_, maintained by the _KDE/Plasma_ development community.
+It has a slightly different look and feel than many native Android and iOS apps,
+but we find it easy and intuitive to work with.
 
-On many pages there is also a _Context menu_ available through a button with three vertical dots in
-the lower right corner.
-In the dive list this _Context menu_ can also be opened by tapping and holding a dive or trip header.
+You have access to the _Main menu_ through a _Hamburger_ button (three short
+horizontal lines) in the lower left corner of the screen. Additionally, the _Main menu_ can be opened by swiping
+towards the right from the very left edge of the screen.
+In addition, many screens have a _Context menu_ available through a button with three vertical dots in
+the lower right corner and that can be opened by tapping and holding a dive or trip header in the dive list.
 
 image::mobile-images/ActionButton2.jpg["FIGURE: Action Button",float="left"]
-Additionally, at the bottom of many _Subsurface-mobile_ screens is a round
+At the bottom of many _Subsurface-mobile_ screens is a round
 _Action button_ that provides quick access to the most commonly needed
-actions on that screen (see image on the left). On some screens there is only
-the round center button enabled, on others there are one or two additional
-actions available on either side of that center button.
+actions on that screen (see image on the left). Some screens have only
+the round central button, others have one or two additional
+actions on either side of the central button.
 
 unfloat::[]
 
@@ -118,7 +114,7 @@ Android back button can be used to cancel the edit without saving changes.
 
 The image below indicates some of the important features of the menu system.
 On the left is the main menu, activated as described above. On the right of the image
-are the items of all the sub-menus available.
+are the sub-menus.
 
 image::mobile-images/Subsurface-mobile-menu-system.jpg["FIGURE: Subsurface-mobile menu system",align="center"]
 
@@ -137,16 +133,16 @@ image::mobile-images/Credentials.jpg["FIGURE: Mobile credentials screen",align="
 
 === Using _Subsurface-mobile_ without Cloud Storage
 Tap the "No cloud mode" button. The app will only store dive log information locally
-on your device. After the first start the dive log will therefore be empty.
+on your device. Following installation an empty dive log is created.
 
 === Using Cloud Storage
 The _Subsurface_ maintainer provides a dedicated and
 free Internet cloud storage account for users of _Subsurface_ and _Subsurface-mobile_.
-You can use this to store your dive log and to share your data between various computers
+You can use this to store your dive log and to share your data between several computers
 and devices. The _Subsurface_ team never accesses your dive data without explicit
 permission to do so, the data are not used for any other purpose than providing them to the user who
-created them. There are no ads and no harvesting / analysis of the data
-stored in the _Subsurface Cloud_ storage. There is no monetization whatsoever.
+created them. There are no ads and no harvesting / analysis of the data / monetization of data
+on the _Subsurface Cloud_ storage.
 
 _Subsurface-mobile_ is sufficient to fully maintain a dive log. In addition you can use the
 more advanced features in _Subsurface_ when you have access to a computer while still
@@ -156,7 +152,7 @@ The dive data in the cloud are cached locally on any device or computer that is
 the _Subsurface Cloud_ account.
 It is easy to create backups of the data (for example in XML format) on the desktop: both the mobile
 device and the desktop keep a local copy of the data so that the dive log is always accessible, even
-without Internet connection.
+without an Internet connection.
 
 To create a _Subsurface Cloud_ account follow these steps:
 
@@ -170,8 +166,8 @@ If you have already set
 up an account on a different computer or device, simply enter the same credentials here.
 _Subsurface-mobile_ will now download your existing dive log data. Once the dive
 list has been downloaded from the cloud, _Subsurface-mobile_ usually works only with the the local
-copy on the mobile device. This avoids long delays or even failure of operations if there is a bad
-(or no) internet connection, a situation fairly common at many dive sites. Remember to manually sync
+copy on the mobile device. This avoids long delays or even failure of operations if there is poor
+internet connectivity. Remember to manually sync
 with the server after making local changes (either by pulling down on the dive list, or by using the
 manual sync entry in the Dive management menu entry).
 
@@ -180,6 +176,9 @@ to the email address entered in the previous step. Enter this PIN into the field
 and tap the _Register_ button. After the PIN has been entered it
 is no longer needed - it just proves that this is indeed your email account.
 
+A https://www.youtube.com/watch?v=Vp_bEm5ZDRA[*video-tutorial*] is available that demonstrates
+how to connect to the cloud.
+
 At this point a new account has been created for you on the cloud server and access to the cloud is
 enabled. In this case the dive list is initially empty. Start entering dives in the dive
 log or download dive information from a supported dive computer.
@@ -194,72 +193,50 @@ provide these again when launching the program.
 
 [blue]#After filling in the correct information and submitting it, I did not receive a PIN by email#
 
-1. Check *carefully* that you didn't make a spelling mistake in the email address you provided. You would be surprised how often this is the problem that people encounter, as autocorrect often mangles email addresses.
+1. Check *carefully* for spelling mistakes in the email address you provided. This is a common problem since autocorrect often mangles email addresses.
 2. Check that the return email containing the PIN is not in the SPAM/Junk folder of your email client.
 3. Wait for a few hours and check again for an email with a PIN.
 4. If there is still no email containing a PIN, send mail to in-app-support@subsurface-divelog.org
 
 [blue]#I want to access the _Subsurface Cloud_ storage but I have forgotten my password. How can I reset my password?#
 
-There is a _Reset forgotten Subsurface Cloud password_ entry in the _Help_ menu in
-_Subsurface-mobile_, or you can go to the https://cloud.subsurface-divelog.org/passwordreset[password reset website]
+The _Help menu_ has an option _Reset forgotten Subsurface Cloud password_. Use that or go to the https://cloud.subsurface-divelog.org/passwordreset[password reset website]
 
-Simply enter the same email address that you used during cloud registration and follow the indicated steps. A confirmation email will be sent to your account to prevent abuse of this system.
+Simply enter the same email address that you used during cloud registration and follow the indicated steps.
+To prevent abuse of this system a confirmation email will be sent to your account.
 
 ****
 
+The dive log can be updated automatically. If there is Internet connectivity, _Subsurface-mobile_ accesses
+the cloud-based dive log to verify that the local copy of the dive log is still the
+same as the log in the cloud server. If not, the local copy and the copy on
+the server are synchronized.
 
 == The Dive List
 
-Most of the actions of _Subsurface-mobile_ center around the dives in the
-dive list. While the dive list is loading from the cloud,
+The _Dive List_ is the heart of _Subsurface-mobile_ because most of the actions
+center around the dives on the dive list. While the dive list is loading from the cloud,
 a message appears at the bottom of the screen, indicating that the cloud is
 being accessed, after which the dive list is shown. Once the list is loaded you can scroll up
 and down through your dive history.
-_Subsurface_ typically structures your dive list by dive trips, but using those is optional
-(and for divers who are lucky enough to be able to dive all the time at local dive sites,
-trips might only make sense for dive vacations).
-
-Two xref:S_Dive_Management[_Dive Management_] actions are available by tapping on the
-action buttons at the bottom of the _Dive List_ page:
-To xref:S_Download[_Download dives from a dive computer_], tap the main action button. If you wish
-to xref:S_Add_Dive[_Manually add a dive_], tap the + button in the action bar. Both of these
-actions are described in detail below.
 
-Tapping an existing dive on the list brings up a display of the xref:S_ViewDive[_Details View_]
-for that dive including the dive profile, notes, and additional information.
+The Dive List consists of two types of entries:
 
-image::mobile-images/DiveListAndDetails.jpg["FIGURE: Dive list screen",align="center"]
+1. *Trip headers*. A trip header is a line describing the year and month during which a dive trip 
+took place, as wel as the geographical area of the trip. The second line in the lefthand image below indicates that a 10-dive trip
+was made to Guinjata, Moçambique during December 2016. 
 
-A tap and hold on a dive or a trip header opens the context menu for that entry.
+2. *Individual dive records*. Tapping a trip header expands the dive list to show (or hide) the individual dives performed during the trip. Each dive is represented by a dive record. By default the dives during the last trip are listed with older dives at the bottom and recent dives at the top of the list. In the lefthand image below the last dive during
+the Guinjata trip was in the Inhambane Estuary.
 
-For a dive this allows moving the dive into or out of trips or between trips, deleting
-the dive or showing the dive on an integrated map viewer (assuming the dive has the
-necessary GPS information). The context menu also allows access to the undo and redo
-system that allows you to step backwards and forwards through recent changes.
+image::mobile-images/Divelist2.jpg["FIGURE: Dive list screen",align="center"]
 
-For a trip header the context menu gives you an option to edit the trip title (typically
-the trip location) and some quick notes for the trip.
-
-=== Filter the dive list
-
-unfloat::[]
-
-image::mobile-images/FilterButton.jpg["FIGURE: Filter button",float="right"]
-The left action button shows three horizontal lines of declining length, symbolizing a filter.
-When you tap this button, a text entry line appears at the top of screen which will allow you to
-enter a filter search term that is either used in a full text search, a search just of the people
-involved in a dive (in the Divemaster and Buddy fields), or a search of the tags you have used
-to classify your dives. Tapping the filter button again clears the filter and shows the full
-dive list.
-
-image::mobile-images/FilteredDivelist.jpg["FIGURE: Filter tool",align="center"]
 
 [[S_View_Dive]]
-=== View a dive
+=== View a dive: the Details view
 
 When you tap on a dive in the _Dive List_, a _Dive Details_ page with the dive profile
-and many important details about the dive is opened. You can use a pinch gesture
+and many important details about the dive is opened (image on right above). You can use a pinch gesture
 to zoom into the profile. Tapping and holding with one finger (until
 the profile becomes translucent) allows you
 to pan the profile and see more details in specific parts of the profile.
@@ -284,81 +261,52 @@ to open a map with the dive site in an integrated map viewer.
 This of course is only possible if the dive site is associated with GPS
 information.
 
-[[S_Edit_Dive]]
-=== Edit a dive
-
-image::mobile-images/DiveDetailsEdit.jpg["FIGURE: Dive edit screen",align="center"]
-At the bottom of the _Dive Details_ screen, the action button is a pencil.
-Tapping the pencil button changes the page and enables editing
-the dive details, e.g. adding text to the dive notes
-or changing the names or values of some of the information (see image on left).
-It may be necessary to scroll the window to access all the available fields.
-At the bottom of the edit screen is a _Save_ action button. Tap this to save
-the new information, after which the dive list screen is
-updated and displayed. To cancel any edits, tap the Android _Back_ Button or
-the application back button at the top left of the screen on iOS.
+=== Filter the dive list
 
+By default, all the dives in the dive log are shown in the dive list. After several years your dive
+log can become quite long and, sometimes, you might like to list only the dives of a particular
+type, e.g. those at a particular dive site or those with a specific buddy or dive master. Use the
+Filter to achieve this. The filter mechanism searches through all the information for each dive,
+looking for one or more key words. Only the dives containing these key words are listed in the dive
+list. To Filter the dive list, tap the Filter action button:
 
-// == Copy dive information from one dive to another
-//
-// When editing dives it is possible to transfer information from one dive to another. For instance,
-// when diving with the same buddy and the same equipment configuration during a particular dive trip
-// it can be efficient to simply copy all this information from the previous dive into the dive that
-// is being edited. Currently a standard list of dive information is copied to the clipboard:
-//
-// Divemaster, Buddy, Suit, Tags, Cylinders, Weights.
-//
-// Copy and paste dive information is performed on the Dive List. Long-press on a dive. A panel
-// with three icons appears on top the selected dive :
-//
-// image::mobile-images/CopyDeleteDive.jpg["FIGURE: Copy/Delete dive information",align="center"]
-//
-// To copy the above information to the clipboard, select the leftmost of the three icons. A "Copy"
-// notification briefly appears on the screen. Now long-press the dive into which the copied information
-// needs to be pasted. The same three icons appear on the target dive. Select the middle icon. A "Paste"
-// notification briefly appears on the screen. This completes the copy-and-paste action. Continue by
-// reviewing this new (pasted) information by manually editing the target dive.
-//
-// To choose what dive details to copy, long-press the copy button. This will open
-// up a configuration page where you can toggle the details you want to copy over
-// to the destination.
+unfloat::[]
 
-=== Deleting a dive
+image::mobile-images/FilterButton.jpg["FIGURE: Filter button",align="center"]
 
-You can delete a dive from the dive list by long-pressing a dive and selecting delete in the context menu.
-You can also delete a dive from the _Details View_ by tapping on the trash can icon on the right
-side of the _Action Button_
+at the bottom of the dive list. A text box appears at the top of the screen (image below). Type the
+word(s) that you would like to use as a filter.
 
-If you deleted the wrong dive by mistake you can easily undo the operation in the context menu.
+image::mobile-images/Filter.jpg["FIGURE: Filter tool",align="center"]
 
-image::mobile-images/UndoDelete.jpg["FIGURE: Undo delete dive",align="center"]
+Three filter modes exist. "Fulltext" searches all text strings. Selecting "People" lists buddies and
+dive masters, while "Tags" only filters for tags containing the given text. Filters are not case-sensitive.
+To clear the filter, remove the key words from the text box and select the Filter action button to
+switch off filtering. The image above represents a full-text search for dives with the word "nitrox".
 
 
 [[S_Dive_Management]]
-== Dive Management
-
-A central  part of _Subsurface-mobile_ is the ability to store the dive
-log using the _Subsurface_ cloud storage.
-This provides security against loss or damage of the dive information in a local copy
-and allows the desktop version of _Subsurface_ to
-access changes made using the mobile device. This feature is accessed
-through the _Dive management_ option in the main menu.
+== Dive List Management and adding dive information
 
 [[S_Add_Dive]]
 === Manually adding a new dive to the dive list
 
+This https://www.youtube.com/watch?v=sF8KB_r0rFw[*video-tutorial*] explains how to add information to a
+manually-entered dive.
+
 You can manually add a dive to the existing dive list. On the dive list
-tap the "plus"-icon in the action bar, or use the
-main menu and tap _Dive management  ->  Add dive manually_. This opens a screen that is
-identical to the editing screen described above. When a dive is added manually, you
+tap the "plus" sign in the action bar, or use the
+main menu and tap _Dive management  ->  Add dive manually_. This opens  a screen that is
+identical to the editing screen discussed above. When a dive is added manually, you
 cannot directly add a dive profile from a dive computer. However, if you do not use a
 dive computer, the duration, depth and several other bits of information about
 the new dive can be entered. The _Action button_ at the bottom of the screen
 contains a disk symbol. Tap this to save the new dive. To cancel any edits, tap the _Back_ button.
 The left-hand image below shows a screenshot of a dive being created and the right-hand image shows
-the same dive in _Details View_.
+the same dive in _Details View_. After editing the dive information, the dive trip information
+needs to be edited as described in the section above on xref:S_Divetrip[Dive trip editing].
 
-image::mobile-images/ManualAddDive.jpg["FIGURE: Manual dive entry screen",align="center"]
+image::mobile-images/Manualdive.jpg["FIGURE: Manual dive entry screen",align="center"]
 
 [[S_Download]]
 === Download dives from a dive computer
@@ -366,23 +314,24 @@ image::mobile-images/ManualAddDive.jpg["FIGURE: Manual dive entry screen",align=
 There are several ways to get to the _Download Page_. You can either tap on the main _Action Button_ on
 the bottom of the _Dive List_, or you can select _Dive management ->  Download from DC_ in the main menu.
 On Android devices, when you plug in a USB serial cable for a dive computer, the _Download Page_ will be
-opened automatically.
-
-The download feature on smartphones supports only a limited number of dive computers. On
+opened automatically. A screen is shown requiring that the user specify
+the names of the vendor and model of the dive computer. For instance, when using a Shearwater Petrel dive
+computer, the vendor is _Shearwater_ and the Dive computer name is _Petrel_ (see image on the left, below).
+*Caveats:* The download feature in smartphones supports only a limited number of dive computers. On
 Android devices these are typically dive computers using a serial USB interface
 using a USB OTG cable or a simple USB C-A adapter on newer devices.
 Android devices also support Bluetooth dive computers that
 are supported in _Subsurface_ on the desktop. Both Android and iOS devices allow direct
 download of dive data from a handful of Bluetooth LE enabled dive
-computers.
-
-Use the _Vendor name_ and _Dive Computer_ drop-downs to pick the correct
-dive computer.
-For instance, when using a Shearwater Petrel dive
-computer, the vendor is _Shearwater_ and the product is _Petrel_(see left image below -
-section Start the download).
+computers. Use the _Vendor name_ and _Dive Computer_ drop-downs to pick the correct
+dive computer. When downloading from multiple different dive computers, shortcut
+buttons appear below the drop-downs to easily switch between them. In the xref:S_Settings[_Settings_] menu
+you can remove these buttons, a useful feature for removing buttons of dive
+computers that are not used any more. Achieve this by selecting the option 
+_Forget remembered dive computers_ in the xref:S_Settings[_Settings_] menu.
+After all these caveats, let us proceed with download. 
 
-TODO: image of DL missing - or link to the 7.2.3 Start the download
+*TODO: image of DL missing - or link to the 7.2.3 Start the download*
 
 When downloading from multiple different dive computers, shortcut
 buttons appear below the drop-downs to easily switch between them. In the xref:S_Settings[_Settings_] menu
@@ -414,71 +363,116 @@ have been successfully used (image on right, below). These appear
 as buttons under a heading "_Previously used dive computers_".
 Select the appropriate button. Having connected the USB dive computer to the
 _Subsurface_ computer and having selected the appropriate vendor and dive computer,
-ensure that the Connection text box shows the corresponding connection. For a small number of dive
+ensure that the _Connection_ text box shows the corresponding connection. For a small number of dive
 computers the connection name shows the dive computer vendor, for most only the cable chipset vendor
-(and USB connection number) is shown. Most users of course only connect one USB dive computer to
-their Android device and then things are fairly straightforward. A dialog will pop up and ask if
-you want to use _Subsurface-mobile_ to connect to the device. If you confirm, then _Subsurface-mobile_ will
-open to the dive computer download screen with the correct connection selected (and if it can deduce
+(and USB connection number) is shown. Most users only connect one USB dive computer to
+their Android device and then things are fairly straightforward. A dialog appears asking if
+you want to use _Subsurface-mobile_ to connect to the device. If you confirm, then _Subsurface-mobile_
+opens the dive computer download screen with the correct connection selected (and if it can deduce
 the correct dive computer based on the cable used, even that information is already pre-filled).
 
-==== Download from BT/BLW dive computers
+==== Download from Bluetooth and Bluetooth LE dive computers
 
-The process for Bluetooth download is slightly different between Android and iOS.
+This https://www.youtube.com/watch?v=DCi70WZMTws[*video-tutorial*] demonstrates downloading dives from a
+Bluetooth-equipped dive computer.
 
-In our testing we got the best results on iOS when the dive computer was
-in Bluetooth mode before _Subsurface-mobile_ is started. On most dive
-computers this is done through a menu entry, others (like the Suunto
-models) always respond to Bluetooth LE requests. However, on Android devices,
-you should first establish a link between the
-Bluetooth or Bluetooth LE dive computer and the mobile device using
-Android utilities. See below for more details.
+The process for Bluetooth download differs between Android and iOS. In *iOS* the best
+results are obtained when the dive computer was
+in Bluetooth LE mode before _Subsurface-mobile_ is started. On most dive
+computers this is done through a menu entry, others (e.g. Suunto) always respond to Bluetooth LE requests.
 
-For Bluetooth-equipped dive computers and Android devices, establish a Bluetooth connection between the dive computer and the
+In contrast, for Bluetooth-equipped dive computers and *Android* devices, first establish a Bluetooth connection
+between the dive computer and the
 mobile device using Android system tools to achieve pairing.
 For many Android devices,
 the Settings -> Bluetooth tool of Android is probably appropriate.
-_Subsurface-mobile_ performs communication using both Bluetooth and Bluetooth-low-energy (BLE).
-The best choice of Bluetooth communication is often made by the software and the user need not be concerned with this.
-For dive computers with both Bluetooth and BLE, a separate button is presented on the download
+_Subsurface-mobile_ performs communication using both Bluetooth and Bluetooth LE (BLE).
+The best choice of Bluetooth communication is often made by the software and the user need not be concerned 
+with this.
+For dive computers with both Bluetooth and BLE, a separate dive computer button is presented on the download
 screen for each mode of communication, allowing a choice. Use the _Connection_ value to distinguish between the
-two options. In the image on the below right, there are three buttons labeled "Shearwater Petrel 2". These represent two Shearwater Petrel dive computers, one of which can communicate in both Bluetooth as well as BLE. The _Connection_
-information indicates that the Petrel with no BLE is selected.
+two options. In the image on the right, below, there are three buttons labeled "Shearwater Petrel 2".
+These represent two Shearwater Petrel dive computers, one of which can communicate in both Bluetooth as well as BLE.
+The _Connection_ information in the image below indicates that the Petrel with no BLE is selected. For 
+Bluetooth LE dive computers, the _Connection_ value has an "LE" prefix.
+
+This https://www.youtube.com/watch?v=4MtQqm4o7bw[*video-tutorial*] demonstrates setting up a
+Bluetooth connection with an Android device.
 
 ==== Start the download
 
 With communication between dive computer and _Subsurface-mobile_
 having been set up, tap the _Download_ button. Be patient because the download can take a while - with many
-long dives and a slow BLE connection we have seen download times of 45 minutes or longer. But usually downloading
+long dives and a slow Bluetooth LE connection we have seen download times of 45 minutes or longer. But usually
+downloading
 a day's worth of diving happens reasonably quickly.
 The downloaded dives appear in the bottom part of the screen,
 the most recent dive at the top (see right image below).
 
 Each dive has a check-box on the left hand side, used for selecting which dives you want to add to the
-_Subsurface-mobile_ dive list: dives that are not checked are ignored. Once you picked the dives
+_Subsurface-mobile_ dive list: dives that are not checked are ignored. Once you have picked the dives
 you want to add to the dive list, tap the button at the bottom left labeled _Accept_. The selected dives will
 now appear as part of
-the _Subsurface-mobile_ dive list. The downloaded dive information can be edited as described in the section
-above xref:S_Edit_Dive[Edit a dive].
+the _Subsurface-mobile_ dive list. 
 
 image::mobile-images/DC-Download.jpg["FIGURE: DC download screen",align="center"]
 
+[[S_Edit_Dive]]
+=== Edit the dive information
+
+This https://www.youtube.com/watch?v=pE3ujzGw_7o[*video-tutorial*] explains how to add information about a dive.
+
+image::mobile-images/Editdive.jpg["FIGURE: Dive edit screen",align="center"]
+
+At the bottom of the _Dive Details_ screen the action button is a pencil.
+Tapping the pencil button changes the page and enables edit boxes that allow
+modifying the existing dive information, e.g. adding text to the dive notes
+or changing the names or values of some of the information (see image above).
+It may be necessary to scroll the window to access all the information.
+At the bottom of the edit screen is a _Save_ action button. Tap this to save
+the new information, after which the dive list screen is
+updated and shown. To cancel any edits, tap the Android _Back_ Button or
+the application back button at the top left of the screen on iOS.
+
+[[S_Divetrip]]
+== Edit the dive trip information
+
+When a new dive(s) is entered manually or downloaded from dive computer, a trip header is created at the
+top of the dive list only showing the month and the year of the dive trip as well as the number of dives
+during the trip (image on left below, showing a trip header with "May 2018", the trip comprising two dives).
+You would probably like to include information about the place
+where the trip took place, e.g. "Channel Islands" or the dive charter company used. In this case long-press
+the dive trip header to activate the context menu. Select the option "Edit trip details" to open a panel
+for typing information about the trip (image on right, below). Having provided the required information,
+tap the _Save_ action button at the bottom of the screen. This returns you to the dive list, showing some of
+the dive trip information that has just been provided.
+
+image::mobile-images/TripDetails.jpg["FIGURE: Edit trip details",align="center"]
+
+=== Deleting a dive
+
+Delete a dive from the dive list by long-pressing a dive and selecting delete in the context menu.
+If the wrong dive was deleted by mistake you can easily undo the operation by using the context menu.
+
+image::mobile-images/Delete_undo.jpg["FIGURE: Undo delete dive",align="center"]
+
+== Interacting with the cloud storage
+
 === Manually sync the dive log with the _Subsurface Cloud_
 
 As the name indicates, this ensures that the local changes on the mobile device and changes
 made by other devices and computers to the data stored in the _Subsurface Cloud_ are synchronized.
 It is highly recommended to sync with cloud storage after downloading new dives from a dive computer
-or manually adding or editing dive information on the mobile device.
-
-This can also be triggered by pulling down (and briefly holding) the _Dive List_.
+or after manually adding or editing dive information on the mobile device.
+This can also be triggered by pulling down (and briefly holding) the topmost entry of the _Dive List_.
 
 === Enable cloud auto sync
 
 By default _Subsurface-mobile_ runs offline and only syncs the dive list
 with cloud storage when explicitly told to do so (see the previous entry above).
-You can choose to always sync with the cloud servers. This is not
+You can choose to always sync with the cloud server. This is not
 recommended unless you are in
-an area with a fast and reliable internet connection, as otherwise
+an area with a fast and reliable Internet connection, as otherwise
 _Subsurface-mobile_ might appear to hang between operations as it tries to
 connect to the cloud server. Selecting _Enable cloud auto sync_ causes
 the local dive log to be synchronized with the copy in the cloud after most changes as well
@@ -487,7 +481,7 @@ of closing an app (you can just kill it, which doesn't allow for a final sync wi
 In general it is safer to manually sync with the cloud once you are done making changes in
 _Subsurface-mobile_.
 
-=== Dive Summary
+== Dive Summary
 
 The _Dive Summary_ page provides a very simple overview of your diving activities - which can for example
 be useful when documenting total dive experience and recent dive activity for a dive center at
@@ -500,31 +494,40 @@ and the dives during the last six months.
 === Export
 
 The _Export_ feature is somewhat experimental. On Android it only allows the upload of your dive list
-to two websites (divelogs.de and diveshare). On iOS it also allows local file based exports as _Subsurface_
+to two websites (_divelogs.de_ and _diveshare_). On iOS it also allows local file based exports as _Subsurface_
 specific XML files (both for dives and dive sites) as well as _UDDF_.
 
-Tapping on _Next_ opens an additional page for login information (or a file selection dialog).
+Tapping on _Next_ opens an additional page for login information for the destination website (or a file selection dialog).
 
-== Location
+== Obtaining dive site locations using the GPS
 
 The fact that almost all smartphones have GPS facilities allows
 _Subsurface-mobile_ to record
-the locations of dives. *IMPORTANT: GPS-derived coordinates on a smartphone
+the locations of dives. 
+
+****
+[icon="images/icons/important.png"]
+[IMPORTANT]
+*Accuracy of GPS coordinates*
+
+GPS-derived coordinates on a smartphone
 are not always accurate and can have an error greater than 1 km. GPS accuracy
 is determined by the hardware and software of the
 smartphone as well as by the GPS settings selected within Android/iOS.
-As of Android V6 select Android _Settings -> Communication -> Location -> High accuracy._*
+As of Android V6 (Marshmallow) select Android _Settings -> Communication -> Location -> High accuracy_*.
 If the smartphone is taken on the boat
-during a dive, locations will be automatically recorded at regular intervals.
-These locations can then be applied to dives in the dive list as described in following chapters.
+during a dive, locations can be automatically recorded at regular intervals.
+These locations can then be applied to dives in the dive list as described below
+****
+To collect dive site coordinates four step are required:
 
 [[S_ConfigureGPS]]
 === Configuring the GPS service
 
-For most users, the defaults for tracking GPS locations will be
+For most users, the defaults for tracking GPS locations are
 appropriate. If you would like to change them, go to
 the _Main Menu_, select the xref:S_Settings[_Settings_] screen, and open
-the _Advanced_ area on that page. Here you will find the section for
+the _Advanced_ area on that page where there is a section for
 configuring the GPS service (see image below). GPS location data
 are collected at regular intervals, e.g. every 5 minutes, or at regular
 distances, e.g. after the boat has moved more than 200m, or a combination of
@@ -541,18 +544,34 @@ a|image::mobile-images/LocationMenu.jpg["FIGURE: GPS start",align="center"] |
 In the _Location_ menu select _Run location service_.
 _Subsurface-mobile_ starts to collect GPS locations automatically,
 following the preferences specified as described above. While the GPS
-location service is running, all menus have a GPS symbol at the bottom
-of the menu, indicating that the service is active. After returning from
+location service is running, all menus have a GPS symbol at the bottom,
+indicating that the service is active. After returning from
 the dive, deactivate the collection of GPS data by tapping
-the option _GPS -> Disable location service_. The GPS symbol at the bottom
-of all menus disappears.
+the option _Location -> Disable location service_. The GPS symbol at the bottom
+of menus disappears.
 
 Collecting GPS fixes like this is relatively battery intensive and unfortunately
 both Android and especially iOS have become increasingly aggressive in killing
 applications that are running while the screen is turned off. It may make sense
-to check between dives that the location service is still running.
+to check between dives that the location service is still running. On the other hand
+the battery consumption of a smartphone with GPS enabled is often significantly less than
+the battery consumption of a dedicated GPS that is logging a track.
 |=======
 
+=== Viewing GPS data collected during a dive
+
+From the _Location_ submenu select _Show GPS fixes_. This brings
+up a list of GPS positions obtained by the location service (image
+below). Two actions are possible for each of the locations, enabled by
+dragging the right part of a location to the left. This exposes two
+options. Tapping the dustbin deletes this particular GPS location. Tapping the
+teardrop-shaped icon (actually a Google Maps pin) opens up Google Maps with a pin
+indicating the exact map position of the GPS record being viewed. The two above
+options can be hidden by drawing the GPS record to the right.
+
+image::mobile-images/gpsmanagement.jpg["FIGURE: GPS management",align="center"]
+
+
 === Applying GPS data to dives in the dive log
 
 After running the location service during a dive trip, first either download
@@ -563,7 +582,7 @@ and end times of each dive. Now, _Subsurface-mobile_ applies the first
 GPS position that falls within the dive period of each dive. This results
 in a GPS position for each dive that is saved as part of the dive log.
 
-=== Viewing the locations of all dives in the dive list
+== Viewing the locations of all dives in the dive list
 
 image::mobile-images/DivesMap.jpg["FIGURE: Map of all dive sites",align="center"]
 
@@ -573,34 +592,35 @@ of the world the dive sites appear, indicated by red flags. Zooming in even clos
 of the different dive sites.
 
 [[S_Settings]]
-== Settings
+== Specifying the settings for _Subsurface-mobile_
 
 The _Settings_ page allows the customization of _Subsurface-mobile_.
-It is grouped into four sections.
+It is grouped into four sections. Many of the settings involve dragging a slider switch to activate or deactivate a particular setting.
 
 === _General settings_ section
 
 image::mobile-images/GeneralSettings.jpg["FIGURE: General Settings",align="center"]
 
 [[S_ChangeCloudAccount]]
-==== Changing to a different _Subsurface_ cloud account
+==== Cloud status: Changing to a different _Subsurface_ cloud account
 
-Some users have more than one _Subsurface_ cloud account and have a need to switch between accounts.
-Tap on the _Change_ button next to the _Email address_ in the _General settings_ on the _Settings_ page.
+Some users have more than one _Subsurface_ cloud account and need to switch between accounts.
+Tap on the _Change_ button next to the _Email address_ in the _General settings_ on the _Settings_ page (see image above).
 This opens the _Cloud credentials_ page.
 Here you can change the email address and password used and then tap the button _Sign-in or register_.
-The appropriate dive list is shown.
+The dive list of the newly-opened account is shown.
 
 ==== Default cylinder
 
 When manually entering a dive or when downloading from a dive computer that doesn't explicitly
 include cylinder size information (very few dive computers support that feature), _Subsurface-mobile_
-uses the cylinder that you select here as the default. If you don't set this entry, no default
+uses the cylinder that you select here as the default, useful for divers that mostly use a particular
+type of cylinder. If you don't set this entry, no default
 cylinder is used.
 
-==== Forget the remembered dive computers
+==== Forget the remembered dive computers used during dive download
 
-Tap the _Forget_ button to reset the dive computers that are stored in the up to four shortcut
+Tap the _Forget_ button to reset the dive computers that are stored in the shortcut
 buttons on the _Download from dive computer_ page.
 
 === _Theme_ section
@@ -612,10 +632,10 @@ buttons on the _Download from dive computer_ page.
 a|image::mobile-images/ThemeSettings.jpg["FIGURE: Theme Settings",align="center"] |
 Besides the default blue color scheme, _Subsurface-mobile_ supports two additional color schemes
 for users with different tastes (see image on left). All screenshots shown in this user manual are
-based on the blue default color scheme. You can pick the _pink_ or _dark_ color scheme from
+based on the blue default color scheme. You can pick the _pink_ or _dark_ color theme from
 the drop down menu.
 
-The boxes below show the various color choices in the theme of your choice.
+The boxes in the image on the left show the various color choices in the theme of your choice.
 |=======
 
 ==== Font size
@@ -631,7 +651,7 @@ your location.
 
 === _Advanced_ section
 
-As the name indicates, most users will not need to make changes here.
+As the name indicates, most users do not need to make changes here.
 
 ==== GPS location service thresholds
 
@@ -640,7 +660,7 @@ thresholds for the _location service_
 
 ==== Bluetooth
 
-Since most devices tend to find a _LOT_ of BT/BLE devices that aren't dive computers, by
+Since most mobile devices tend to find a _LOT_ of BT/BLE devices that aren't dive computers, by
 default _Subsurface-mobile_ only shows known dive computers to make the connection list
 easier to use.
 
@@ -663,7 +683,7 @@ feature.
 ==== Activating the Developer sub-menu
 
 This enables an additional menu item in the _Main_ menu which contains options which are almost
-never useful for a regular users. Here you can find the detailed app log file as well as several
+never useful for a regular user. Here you can find the detailed app log file as well as several
 test screens that help the developers track down issues you might encounter.
 
 == Help
@@ -676,7 +696,7 @@ a convenient way to copy the application logs to the clipboard.
 === Show user manual
 
 This menu entry opens the online version of this user manual in the native browser of your
-device. Unfortunately this option isn't available if your device is offline.
+device. Unfortunately this option is not available without Internet access.
 
 === Ask for support
 
diff --git a/Documentation/mobile-manual.html.git b/Documentation/mobile-manual.html.git
deleted file mode 100644
index 58cf88cff..000000000
--- a/Documentation/mobile-manual.html.git
+++ /dev/null
@@ -1,962 +0,0 @@
-<?xml version="1.0" encoding="UTF-8"?>
-<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.1//EN"
-    "http://www.w3.org/TR/xhtml11/DTD/xhtml11.dtd">
-<html xmlns="http://www.w3.org/1999/xhtml" xml:lang="en">
-<head>
-<meta http-equiv="Content-Type" content="application/xhtml+xml; charset=UTF-8" />
-<meta name="generator" content="AsciiDoc 8.6.10" />
-<title></title>
-<style type="text/css">
-/*
- * compact_subsurface.css, a special style sheet for Subsurface,
- *  modified by Willem Ferguson and derived from:
- *		compact.css, version 1.3 by Alex Efros <powerman@powerman.name>
- * Licence: Public Domain
- *
- * Usage: asciidoc -a theme=compact_subsurface ...
- */
-
-*   { padding: 0;  margin: 0; }
-img { border: 0; }
-
-/*** Layout ***/
-
-body                        { margin: 10px 20px; }
-#header br                  { display: none; }
-#revnumber                  { display: block; }
-#toc                        { margin: 1em 0; }
-.toclevel2                  { margin-left: 1em; }
-.toclevel3		    { margin-left: 2em; }
-#footer                     { margin-top: 2em; }
-
-#preamble .sectionbody,
-h2,
-h3,
-h4,
-h5                          { margin: 1em 0 0 0; }
-
-.admonitionblock,
-.listingblock,
-.sidebarblock,
-.exampleblock,
-.tableblock,
-.literalblock               { margin: 1em 0; }
-.admonitionblock td.icon    { padding-right: 0.5em; }
-.admonitionblock td.content { padding-left:  0.5em; }
-.listingblock .content      { padding: 0.5em; }
-.sidebarblock > .content    { padding: 0.5em; }
-.exampleblock > .content    { padding: 0 0.5em; }
-.tableblock caption         { padding: 0 0 0.5em 0; }
-.tableblock thead th,
-.tableblock tbody td,
-.tableblock tfoot td        { padding: 0 0.5em; }
-.quoteblock                 { padding: 0 2.0em; }
-
-.paragraph                  { margin: 1em 0 0 0; }
-.sidebarblock .paragraph:first-child,
-.exampleblock .paragraph:first-child,
-.admonitionblock .paragraph:first-child  { margin: 0; }
-
-   .ulist,    .olist,    .dlist,    .hdlist,    .qlist   { margin: 1em 0; }
-li .ulist, li .olist, li .dlist, li .hdlist, li .qlist,
-dd .ulist, dd .olist, dd .dlist, dd .hdlist, dd .qlist   { margin: 0; }
-ul                          { margin-left: 1.5em; }
-ol                          { margin-left: 2em; }
-dd                          { margin-left: 3em; }
-td.hdlist1                  { padding-right: 1em; }
-
-/*** Fonts ***/
-
-body                        { font-family: Verdana, sans-serif; }
-#header                     { font-family: Arial,   sans-serif; }
-#header h1                  { font-family: Arial,   sans-serif; }
-#footer                     { font-family: Georgia, serif;      }
-#email                      { font-size: 0.85em; }
-#revnumber                  { font-size: 0.75em; }
-#toc                        { font-size: 0.9em;  }
-#toctitle                   { font-weight: bold; }
-#footer                     { font-size: 0.8em; }
-
-h2, h3, h4, h5, .title      { font-family: Arial,   sans-serif; }
-h2                          { font-size: 1.5em; }
-.sectionbody                { font-size: 0.85em; }
-.sectionbody .sectionbody   { font-size: inherit; }
-h3                          { font-size: 159%; } /* 1.35em */
-h4                          { font-size: 141%; } /* 1.2em */
-h5                          { font-size: 118%; } /* 1em */
-.title                      { font-size: 106%;   /* 0.9em */
-			      font-weight: bold;
-			    }
-
-tt, .monospaced             { font-family: monospace; font-size: 106%; } /* 0.9em */
-dt, td.hdlist1, .qlist em   { font-family: Times New Roman, serif;
-			      font-size: 118%;   /* 1em */
-			      font-style: italic;
-			    }
-.tableblock tfoot td        { font-weight: bold; }
-
-/*** Colors and Backgrounds ***/
-
-h1                          { color: #527bbd; border-bottom: 2px solid silver; }
-#footer                     {                 border-top:    2px solid silver; }
-
-h2                          { color: #527bbd; border-bottom: 2px solid silver; }
-h3                          { color: #5D7EAE; border-bottom: 2px solid silver; }
-h3                          { display: inline-block; }
-h4,h5                       { color: #5D7EAE; }
-
-.admonitionblock td.content { border-left: 2px solid silver; }
-.listingblock .content      { background: #f4f4f4;   border: 1px solid silver; border-left: 5px solid #e0e0e0; }
-.sidebarblock > .content    { background: #ffffee;   border: 1px solid silver; border-left: 5px solid #e0e0e0; }
-.exampleblock > .content    {                   border-left: 2px solid silver; }
-.quoteblock                 {                   border-left: 5px solid #e0e0e0; }
-.tableblock table {
-    border-collapse: collapse;
-    border-width: 3px;
-    border-color: #527bbd;
-}
-.tableblock table[frame=hsides] { border-style: solid none; }
-.tableblock table[frame=border] { border-style: solid;      }
-.tableblock table[frame=void]   { border-style: none;       }
-.tableblock table[frame=vsides] { border-style: none solid; }
-.tableblock table[rules=all] tbody tr *,
-.tableblock table[rules=rows] tbody tr * {
-    border-top: 1px solid #527bbd;
-}
-.tableblock table[rules=all] tr *,
-.tableblock table[rules=cols] tr * {
-    border-left: 1px solid #527bbd;
-}
-.tableblock table tbody tr:first-child * {
-    border-top: 1px solid white; /* none don't work here... %-[] */
-}
-.tableblock table tr *:first-child {
-    border-left: none;
-}
-.tableblock table[frame] thead tr *,
-.tableblock table[frame] thead tr * {
-    border-top: 1px solid white;
-    border-bottom: 2px solid #527bbd;
-}
-.tableblock table tr td p.table,
-.tableblock table tr td p.table * {
-    border: 0px;
-}
-
-tt, .monospaced             { color: navy; }
-
-li                          { color: #a0a0a0; }
-li > *                      { color: black; }
-
-span.aqua { color: aqua; }
-span.black { color: black; }
-span.blue { color: blue; }
-span.fuchsia { color: fuchsia; }
-span.gray { color: gray; }
-span.green { color: green; }
-span.lime { color: lime; }
-span.maroon { color: maroon; }
-span.navy { color: navy; }
-span.olive { color: olive; }
-span.purple { color: purple; }
-span.red { color: red; }
-span.silver { color: silver; }
-span.teal { color: teal; }
-span.white { color: white; }
-span.yellow { color: yellow; }
-
-span.aqua-background { background: aqua; }
-span.black-background { background: black; }
-span.blue-background { background: blue; }
-span.fuchsia-background { background: fuchsia; }
-span.gray-background { background: gray; }
-span.green-background { background: green; }
-span.lime-background { background: lime; }
-span.maroon-background { background: maroon; }
-span.navy-background { background: navy; }
-span.olive-background { background: olive; }
-span.purple-background { background: purple; }
-span.red-background { background: red; }
-span.silver-background { background: silver; }
-span.teal-background { background: teal; }
-span.white-background { background: white; }
-span.yellow-background { background: yellow; }
-
-span.big { font-size: 2em; }
-span.small { font-size: 0.6em; }
-
-span.underline { text-decoration: underline; }
-span.overline { text-decoration: overline; }
-span.line-through { text-decoration: line-through; }
-
-/*** Misc ***/
-
-.admonitionblock td.icon    { vertical-align: top; }
-.attribution                { text-align: right; }
-
-ul                          { list-style-type: disc; }
-ol.arabic                   { list-style-type: decimal; }
-ol.loweralpha               { list-style-type: lower-alpha; }
-ol.upperalpha               { list-style-type: upper-alpha; }
-ol.lowerroman               { list-style-type: lower-roman; }
-ol.upperroman               { list-style-type: upper-roman; }
-.hdlist td                  { vertical-align: top; }
-
-
-</style>
-<script type="text/javascript">
-/*<![CDATA[*/
-var asciidoc = {  // Namespace.
-
-/////////////////////////////////////////////////////////////////////
-// Table Of Contents generator
-/////////////////////////////////////////////////////////////////////
-
-/* Author: Mihai Bazon, September 2002
- * http://students.infoiasi.ro/~mishoo
- *
- * Table Of Content generator
- * Version: 0.4
- *
- * Feel free to use this script under the terms of the GNU General Public
- * License, as long as you do not remove or alter this notice.
- */
-
- /* modified by Troy D. Hanson, September 2006. License: GPL */
- /* modified by Stuart Rackham, 2006, 2009. License: GPL */
-
-// toclevels = 1..4.
-toc: function (toclevels) {
-
-  function getText(el) {
-    var text = "";
-    for (var i = el.firstChild; i != null; i = i.nextSibling) {
-      if (i.nodeType == 3 /* Node.TEXT_NODE */) // IE doesn't speak constants.
-        text += i.data;
-      else if (i.firstChild != null)
-        text += getText(i);
-    }
-    return text;
-  }
-
-  function TocEntry(el, text, toclevel) {
-    this.element = el;
-    this.text = text;
-    this.toclevel = toclevel;
-  }
-
-  function tocEntries(el, toclevels) {
-    var result = new Array;
-    var re = new RegExp('[hH]([1-'+(toclevels+1)+'])');
-    // Function that scans the DOM tree for header elements (the DOM2
-    // nodeIterator API would be a better technique but not supported by all
-    // browsers).
-    var iterate = function (el) {
-      for (var i = el.firstChild; i != null; i = i.nextSibling) {
-        if (i.nodeType == 1 /* Node.ELEMENT_NODE */) {
-          var mo = re.exec(i.tagName);
-          if (mo && (i.getAttribute("class") || i.getAttribute("className")) != "float") {
-            result[result.length] = new TocEntry(i, getText(i), mo[1]-1);
-          }
-          iterate(i);
-        }
-      }
-    }
-    iterate(el);
-    return result;
-  }
-
-  var toc = document.getElementById("toc");
-  if (!toc) {
-    return;
-  }
-
-  // Delete existing TOC entries in case we're reloading the TOC.
-  var tocEntriesToRemove = [];
-  var i;
-  for (i = 0; i < toc.childNodes.length; i++) {
-    var entry = toc.childNodes[i];
-    if (entry.nodeName.toLowerCase() == 'div'
-     && entry.getAttribute("class")
-     && entry.getAttribute("class").match(/^toclevel/))
-      tocEntriesToRemove.push(entry);
-  }
-  for (i = 0; i < tocEntriesToRemove.length; i++) {
-    toc.removeChild(tocEntriesToRemove[i]);
-  }
-
-  // Rebuild TOC entries.
-  var entries = tocEntries(document.getElementById("content"), toclevels);
-  for (var i = 0; i < entries.length; ++i) {
-    var entry = entries[i];
-    if (entry.element.id == "")
-      entry.element.id = "_toc_" + i;
-    var a = document.createElement("a");
-    a.href = "#" + entry.element.id;
-    a.appendChild(document.createTextNode(entry.text));
-    var div = document.createElement("div");
-    div.appendChild(a);
-    div.className = "toclevel" + entry.toclevel;
-    toc.appendChild(div);
-  }
-  if (entries.length == 0)
-    toc.parentNode.removeChild(toc);
-},
-
-
-/////////////////////////////////////////////////////////////////////
-// Footnotes generator
-/////////////////////////////////////////////////////////////////////
-
-/* Based on footnote generation code from:
- * http://www.brandspankingnew.net/archive/2005/07/format_footnote.html
- */
-
-footnotes: function () {
-  // Delete existing footnote entries in case we're reloading the footnodes.
-  var i;
-  var noteholder = document.getElementById("footnotes");
-  if (!noteholder) {
-    return;
-  }
-  var entriesToRemove = [];
-  for (i = 0; i < noteholder.childNodes.length; i++) {
-    var entry = noteholder.childNodes[i];
-    if (entry.nodeName.toLowerCase() == 'div' && entry.getAttribute("class") == "footnote")
-      entriesToRemove.push(entry);
-  }
-  for (i = 0; i < entriesToRemove.length; i++) {
-    noteholder.removeChild(entriesToRemove[i]);
-  }
-
-  // Rebuild footnote entries.
-  var cont = document.getElementById("content");
-  var spans = cont.getElementsByTagName("span");
-  var refs = {};
-  var n = 0;
-  for (i=0; i<spans.length; i++) {
-    if (spans[i].className == "footnote") {
-      n++;
-      var note = spans[i].getAttribute("data-note");
-      if (!note) {
-        // Use [\s\S] in place of . so multi-line matches work.
-        // Because JavaScript has no s (dotall) regex flag.
-        note = spans[i].innerHTML.match(/\s*\[([\s\S]*)]\s*/)[1];
-        spans[i].innerHTML =
-          "[<a id='_footnoteref_" + n + "' href='#_footnote_" + n +
-          "' title='View footnote' class='footnote'>" + n + "</a>]";
-        spans[i].setAttribute("data-note", note);
-      }
-      noteholder.innerHTML +=
-        "<div class='footnote' id='_footnote_" + n + "'>" +
-        "<a href='#_footnoteref_" + n + "' title='Return to text'>" +
-        n + "</a>. " + note + "</div>";
-      var id =spans[i].getAttribute("id");
-      if (id != null) refs["#"+id] = n;
-    }
-  }
-  if (n == 0)
-    noteholder.parentNode.removeChild(noteholder);
-  else {
-    // Process footnoterefs.
-    for (i=0; i<spans.length; i++) {
-      if (spans[i].className == "footnoteref") {
-        var href = spans[i].getElementsByTagName("a")[0].getAttribute("href");
-        href = href.match(/#.*/)[0];  // Because IE return full URL.
-        n = refs[href];
-        spans[i].innerHTML =
-          "[<a href='#_footnote_" + n +
-          "' title='View footnote' class='footnote'>" + n + "</a>]";
-      }
-    }
-  }
-},
-
-install: function(toclevels) {
-  var timerId;
-
-  function reinstall() {
-    asciidoc.footnotes();
-    if (toclevels) {
-      asciidoc.toc(toclevels);
-    }
-  }
-
-  function reinstallAndRemoveTimer() {
-    clearInterval(timerId);
-    reinstall();
-  }
-
-  timerId = setInterval(reinstall, 500);
-  if (document.addEventListener)
-    document.addEventListener("DOMContentLoaded", reinstallAndRemoveTimer, false);
-  else
-    window.onload = reinstallAndRemoveTimer;
-}
-
-}
-asciidoc.install(3);
-/*]]>*/
-</script>
-</head>
-<body class="article">
-<div id="header">
-</div>
-<div id="content">
-<div class="imageblock" style="text-align:center;">
-<div class="content">
-<img src="mobile-images/Banner.jpg" alt="Banner" />
-</div>
-</div>
-<div class="paragraph"><p><span class="big">Subsurface-mobile USER MANUAL</span></p></div>
-<div class="paragraph"><p><strong>Manual authors</strong>: Willem Ferguson, Dirk Hohndel</p></div>
-<div class="paragraph"><p><span class="blue"><em>Version 2, December 2017</em></span></p></div>
-<div class="paragraph"><p>Welcome as a user of <em>Subsurface</em> and <em>Subsurface-mobile</em>, advanced dive logging
-software with extensive infrastructure to describe, organize, and interpret scuba
-and free dives. <em>Subsurface</em> offers many advantages over other similar
-software solutions, including compatibility with Windows, macOS, Linux (many
-distributions), Android and iOS. In addition, <em>Subsurface</em> is
-open-source software that allows downloading dive
-information from many dive computers.</p></div>
-<div class="sect1">
-<h2 id="_introducing_subsurface_mobile">1. Introducing Subsurface-mobile</h2>
-<div class="sectionbody">
-<div class="paragraph"><p><em>Subsurface-mobile</em> is a more limited mobile version of <em>Subsurface</em>
-aimed at Android and iOS smartphone and tablet devices, allowing viewing, entering, sharing, and storage of dive information at dive sites where a larger
-computer is not useful. While the desktop version of <em>Subsurface</em> shows much more detailed information
-for each dive, the mobile version allows a more accessible dive log
-on a dive trip, useful for proving dive experience to dive shops or to review
-previous dives. <em>Subsurface-mobile</em> also allows
-the gathering of GPS locations where dives are performed.</p></div>
-<div class="paragraph"><p>Users of <em>Subsurface-mobile</em> typically use the
-mobile app as a companion to the laptop/desktop version of <em>Subsurface</em>,  sharing dive information
-between the mobile and the desktop versions. However <em>Subsurface-mobile</em> can
-also be used independently of the desktop version and does not require the use of
-cloud storage.</p></div>
-<div class="paragraph"><p><em>Subsurface-mobile</em> allows:</p></div>
-<div class="ulist"><ul>
-<li>
-<p>
-Download and storage of dive log information using the <em>Subsurface</em> cloud.
-</p>
-</li>
-<li>
-<p>
-Viewing this information on a mobile device.
-</p>
-</li>
-<li>
-<p>
-Manually creating and adding new dive records to your dive log.
-</p>
-</li>
-<li>
-<p>
-Download dive data directly from many dive computers.
-</p>
-</li>
-<li>
-<p>
-Editing many of the dive log data fields, e.g. divemaster, buddy,
-  equipment or notes relating to a dive.
-</p>
-</li>
-<li>
-<p>
-Recording, storing and applying GPS positions of dives.
-</p>
-</li>
-<li>
-<p>
-Viewing the localities of recorded GPS positions and of dives
-  on a map.
-</p>
-</li>
-</ul></div>
-<div class="paragraph"><p>These items are discussed in greater detail in the following text.
-<em>Subsurface-mobile</em> does not support download of dive data from all the
-dive computers that the desktop/laptop version can. This limitation is
-mainly caused by the ability to access different type of devices on the
-two mobile platforms. On Android, a subset of
-dive computers that use a FTDI USB interface or a Bluetooth / Bluetooth LE interface
-are accessible by <em>Subsurface-mobile</em>. On iOS, only Bluetooth LE based
-dive computers are supported.</p></div>
-</div>
-</div>
-<div class="sect1">
-<h2 id="_installing_em_subsurface_mobile_em_on_your_mobile_device">2. Installing <em>Subsurface-mobile</em> on your mobile device</h2>
-<div class="sectionbody">
-<div class="paragraph"><p>Find <em>Subsurface-mobile</em> in the <em>Google Play Store</em> or the <em>iTunes Store</em>
-and install it. Please note that both stores also contain the older <em>Subsurface</em> companion app (used only for tracking GPS positions) - make sure you actually install <em>Subsurface-mobile</em>.</p></div>
-</div>
-</div>
-<div class="sect1">
-<h2 id="_using_em_subsurface_mobile_em_for_the_first_time">3. Using <em>Subsurface-mobile</em> for the first time</h2>
-<div class="sectionbody">
-<div class="paragraph"><p>When you start <em>Subsurface-mobile</em> for the first time, a Subsurface
-splash screen is shown while the program loads. On some devices this
-may take several seconds. After loading, the <em>Cloud Credentials screen</em> appears
-(see image below on left).</p></div>
-<div class="imageblock" style="text-align:center;">
-<div class="content">
-<img src="mobile-images/Credentials.jpg" alt="FIGURE: Mobile credentials screen" />
-</div>
-</div>
-<div class="sect2">
-<h3 id="_when_not_using_cloud_storage">3.1. When NOT Using Cloud Storage</h3>
-<div class="paragraph"><p>Tap the "No cloud mode" button. The app will not access the <em>Subsurface</em>
-cloud storage server
-to obtain dive log information. This means that dive log information is
-stored on the mobile device only. If no dives have been entered into the dive log
-yet (the usual case), an empty dive log is created.</p></div>
-</div>
-<div class="sect2">
-<h3 id="_using_cloud_storage">3.2. Using Cloud Storage</h3>
-<div class="paragraph"><p>The <em>Subsurface</em> developers provide a custom
-free Internet cloud storage account that can be used for
-storing dive log information. This cloud storage account can be created either from <em>Subsurface</em> on the desktop or <em>Subsurface-mobile</em>
-using a mobile device; you can
-do full maintenance of a dive log from <em>Subsurface-mobile</em> alone. By using the same
-credentials wirh <em>Subsurface-mobile</em> and <em>Subsurface</em> for desktop, the <em>Subsurface</em> cloud storage allows you to share your dive
-log between both (or even more than two) devices.</p></div>
-<div class="paragraph"><p>The dive data are cached both on the mobile device as well as on the desktop - it is easy to create backups of the data (for example in XML format) on the desktop, and both mobile device and desktop keep a local copy of the data so that the dive log is always accessible, even without Internet connection. The Subsurface team never accesses a user&#8217;s dive data without explicit permission to do so, the data are not used for any purpose other than providing them to the user who created them. There are no ads and no harvesting / analysis of the data stored in the Subsurface cloud storage.</p></div>
-<div class="paragraph"><p>1) Enter an e-mail address and a password in the fields indicated on the screen.
-The e-mail address should be in lower case and the password should contain a combination of
-letters from the alphabet (upper and lower case) and/or numbers.
-Tap the "Sign-in or Register" button. If you have already set
-up an account from the <em>Subsurface</em> desktop application, enter the same credentials here.
-Once the dive
-list has been downloaded from the cloud, <em>Subsurface-mobile</em> usually works only with the the local
-copy on the mobile device. This avoids long delays or even failure of operations if there is a bad (or no) internet connection, a situation fairly common at many dive sites.</p></div>
-<div class="paragraph"><p>3) If this is a new account, a PIN screen will open (see image on right, above). A PIN is e-mailed
-to the email address entered in the previous step. Enter this PIN into the field indicated
-and tap the <em>Register</em> button. The user
-information is stored on the cloud server and access to the cloud is enabled. In this case
-the dive list is initially empty. Start entering dives in the dive
-log or download dive information from a supported dive computer.</p></div>
-<div class="paragraph"><p>The dive log can be updated automatically. If there is Internet connectivity, <em>Subsurface-mobile</em> accesses
-the cloud-based dive log to verify that the local copy of the dive log is still the
-same as the log in the cloud server. If not, the local copy and the copy on
-the server are synchronized.</p></div>
-</div>
-<div class="sect2">
-<h3 id="_changing_the_existing_login_credentials_on_the_em_subsurface_em_cloud">3.3. Changing the existing login credentials on the <em>Subsurface</em> cloud</h3>
-<div class="paragraph"><p>The login credentials can be changed, for an example in order to work with
-multiple accounts. See the section on <a href="#S_ChangeCloudAccount">Changing to a different <em>Subsurface</em> cloud account</a>.</p></div>
-</div>
-</div>
-</div>
-<div class="sect1">
-<h2 id="_menu_structure_and_user_interface">4. Menu Structure and User Interface</h2>
-<div class="sectionbody">
-<div class="paragraph"><p>At the bottom of many Subsurface-mobile screens is a round button that provides for
-several actions (see image below). The most common choice is indicated in a round colored <em>action button</em> (in the case below, edit a dive). Alternative actions are indicated in a white <em>action bar</em>.
-On Android devices, use the Android Back
-button for "cancel", "discard" or "back" actions. For example, when
-editing dive information, tapping the action button saves the changes while the
-Android back button can be used to cancel the edit without saving changes.</p></div>
-<div class="paragraph"><p>On iOS devices, on screens where a "back" action is enabled, a back arrow
-is shown in the top left corner of the screen.</p></div>
-<div class="imageblock" style="text-align:center;">
-<div class="content">
-<img src="mobile-images/Actionbutton.jpg" alt="FIGURE: Action Button" />
-</div>
-</div>
-<div class="paragraph"><p>In order to have a consistent experience between iOS and Android,
-<em>Subsurface-mobile</em> on Android does not use the traditional "hamburger"
-menu button in the top left or right corner of the screen to open menus.
-Instead, <em>Subsurface-mobile</em> uses a
-different user interaction philosophy based on the Kirigami framework
-developed by the Plasma developers. There are three ways to open the main menu:</p></div>
-<div class="ulist"><ul>
-<li>
-<p>
-Tap the "hamburger" symbol in the lower left corner of the screen
-  (easy to reach for hand held devices)
-</p>
-</li>
-<li>
-<p>
-Swipe towards the right across the left edge of the screen
-</p>
-</li>
-<li>
-<p>
-Drag the action button visible on most screens to
-  the right
-</p>
-</li>
-</ul></div>
-<div class="imageblock" style="text-align:center;">
-<div class="content">
-<img src="mobile-images/Menusystem.jpg" alt="FIGURE: Dive management sub-panel" />
-</div>
-</div>
-<div class="paragraph"><p>The image above indicates some of the important features of the menu system.
-On the left is the main menu, activated as described above. On the right of the image
-are the items of all the submenus accessible.</p></div>
-<div class="paragraph"><p>All screenshots in this user manual are currently from the Android
-version. The iOS screens look fairly similar.</p></div>
-</div>
-</div>
-<div class="sect1">
-<h2 id="_the_dive_list">5. The Dive List</h2>
-<div class="sectionbody">
-<div class="paragraph"><p>Most of the actions of <em>Subsurface-mobile</em> center around the dives on the
-dive list. While the dive list is loading from the cloud,
-a message appears at the bottom of the screen, indicating that the cloud is
-being accessed, after which the dive list is shown. Once the list is loaded you can scroll up and down
-through your dive history.
-To upload dives from a dive computer, tap the blue action button. If you wish
-to add a dive manually, tap the + button in the action bar (described below).
-Tapping an existing dive on the list brings up a display of <em>Details View</em> for that dive
-(see image on right below). This includes the dive profile as well as
-additional information and notes.</p></div>
-<div class="imageblock" style="text-align:center;">
-<div class="content">
-<img src="mobile-images/Divelist2.jpg" alt="FIGURE: Dive list screen" />
-</div>
-</div>
-<div class="paragraph"><p>You can view other dives by swiping the <em>Details view</em> to the right (for the
-previous dive) or to the left (following dive).
-Using the Action Bar, it is also possible to delete the dive (tap the dustbin
-on the Action Bar) or to view the dive
-location on a map viewer (Google Maps on Android, the Google Maps web site
-on iOS; tap the GPS icon on the Action Bar.).</p></div>
-</div>
-</div>
-<div class="sect1">
-<h2 id="S_Edit_Dive">6. Editing dive details</h2>
-<div class="sectionbody">
-<div class="paragraph"><p>At the bottom of the dive details screen the action button is a pencil (image on right, above).
-Tapping the pencil button changes the page and enables edit boxes that allow
-modifying the existing dive information, e.g. adding text to the dive notes
-or changing the names or values of some of the information (see image below).
-It may be necessary to scroll the window to access all the information.
-At the bottom of the edit screen is a <em>Save</em> action button. Tap this to save
-the new information, after which the dive list screen is
-updated and shown. To cancel any edits, tap the Android <em>Back</em> Button or
-the application back button at the top left of the screen on iOS.</p></div>
-<div class="paragraph"><p>When the virtual keyboard is shown, to avoid screen clutter, the action button is hidden.
-Once you close the keyboard it is drawn again.</p></div>
-<div class="imageblock" style="text-align:center;">
-<div class="content">
-<img src="mobile-images/Editdive.jpg" alt="FIGURE: Dive edit screen" />
-</div>
-</div>
-</div>
-</div>
-<div class="sect1">
-<h2 id="S_Add_Dive">7. Manually adding a new dive to the dive list</h2>
-<div class="sectionbody">
-<div class="paragraph"><p>One can manually add a dive to the existing dive list. On the dive list
-tap the "plus" sign in the action bar, or use the
-main menu and tap <em>Manage dives  &#8594;  Add dive manually</em>. This opens  a screen that is
-identical to the editing screen discussed above. When a dive is added manually, you
-cannot directly add a dive profile from a dive computer. However, if you do not use a
-dive computer, the duration, depth and several other bits of information about
-the new dive can be entered. The <em>Action button</em> at the bottom of the screen
-contains a disk symbol. Tap this to save the new dive. To cancel any edits, tap the Android Back Button.
-The left-hand image below shows a screenshot of a dive being created and the right-hand image shows
-the same dive in <em>Details View</em>.</p></div>
-<div class="imageblock" style="text-align:center;">
-<div class="content">
-<img src="mobile-images/Manualdive.jpg" alt="FIGURE: Manual dive entry screen" />
-</div>
-</div>
-</div>
-</div>
-<div class="sect1">
-<h2 id="_deleting_a_dive">8. Deleting a dive</h2>
-<div class="sectionbody">
-<div class="paragraph"><p>The <em>Details View</em> of a dive has an Action Bar, including a dustbin. If this is tapped,
-the dive shown in the <em>Details View</em> is deleted. You have a brief opportunity to undo
-the delete by tapping the grey <em>Undo</em> button in the message that appears at the bottom of
-the screen (see image below).</p></div>
-<div class="imageblock" style="text-align:center;">
-<div class="content">
-<img src="mobile-images/Delete_undo.jpg" alt="FIGURE: Undo delete dive" />
-</div>
-</div>
-<div class="paragraph"><p>You can also delete a dive from the dive list by long-pressing a dive
-until a red dustbin appears on the right-hand side (see image below). Tap the dustbin. The dive is
-deleted without asking any confirmation because <em>Subsurface-mobile</em> assumes that the
-combination of a long tap on the dive with another tap on the red dustbin is an unambiguous
-instruction to delete the dive.</p></div>
-<div class="imageblock" style="text-align:center;">
-<div class="content">
-<img src="mobile-images/RedDustbin.jpg" alt="FIGURE: delete dive from list" />
-</div>
-</div>
-</div>
-</div>
-<div class="sect1">
-<h2 id="S_Download">9. Download dives from a dive computer</h2>
-<div class="sectionbody">
-<div class="paragraph"><p>The download deature supports only a limited number of dive computers. On
-Android devices these are typically dive computers using an FTDI interface
-using a USB OTG cable (but this is blocked on some Android devices by OS
-settings). Android devices also support all Bluetooth dive computers that
-are supported in Subsurface. And both Android and iOS devices allow direct
-download of dive data from a hand full of Bluetooth LE enabled dive
-computers.</p></div>
-<div class="paragraph"><p>Use the <em>Vendor name</em> and <em>Dive Computer</em> drop-downs to pick the correct
-dive computer. When downloading from multiple different dive computers, shortcut
-buttons to easily switch between them will appear below the drop-downs.</p></div>
-<div class="paragraph"><p>The process for download is slightly different between the two OSs.
-In our testing we got the best results on iOS when the dive computer was
-in Bluetooth mode before <em>Subsurface-mobile</em> is started. On most dive
-computers this is done through a menu entry, others (like the Suunto
-models) always respond to BLE requests.</p></div>
-<div class="paragraph"><p>On Android devices, you should first establish a link between the
-Bluetooth or Bluetooth LE dive computer and the mobile device using
-Android utilities. See below for more details.</p></div>
-<div class="paragraph"><p>For USB dive computers, USB cables "normally" used
-for uploading dives to a desktop/laptop computer do NOT work: these cables usually have a full-sized ("Type A") male USB plug
-on one end which plugs into the USB port of a desktop/laptop computer. For downloads to a mobile device
-one needs a USB OTG (USB On-The-Go) cable. In most cases it is required to plug the USB
-cable "normally" used with the dive computer into a USB OTG cable which, in turn, plugs into the mini-USB (or sometimes a USB "Type C")
-receptacle of the mobile device. The
-OTG cable usually has a full-size ("Type A") female receptacle at one end which accommodates the full-sized male plug
-of the USB cable "normally" used (see image below). This means that two cables are used to connect the dive computer to the mobile device.</p></div>
-<div class="paragraph"><p>Please note that not all Android devices support OTG cables. And even on some devices that do support those cables in general, <em>Subsurface-mobile</em> still in some cases cannot access a dive computer through a serial port.</p></div>
-<div class="imageblock" style="text-align:center;">
-<div class="content">
-<img src="mobile-images/USB-OTG.jpg" alt="FIGURE: USB-OTG cable" />
-</div>
-</div>
-<div class="paragraph"><p>For Bluetooth-equipped dive computers and Android devices, establish a Bluetooth connection between the dive computer and the
-mobile device. Use the tools on the mobile device to achieve pairing between the Bluetooth dice computer
-and the mobile device. For of Android devices,
-the Settings &#8594; Bluetooth tool is probably appropriate. Ensure pairing of the dive computer and mobile device.
-<em>Subsurface-mobile</em> performs communication using both Bluetooth and Bluetooth-low-energy (BTLE).
-The appropriate choice of Bluetooth communication is made by the software and the user need not be concerned with this.</p></div>
-<div class="paragraph"><p>With pairing between dive computer and <em>Subsurface-mobile</em> having been set up, dive download is simple.
-From the main menu, tap <em>Manage dives &#8594;  Download from DC</em>. A screen is shown requiring that the user specify
-the names of the vendor and model of the dive computer. For instance, when using a Shearwater Petrel 2 dive
-computer, the vendor is <em>Shearwater</em> and the Dive computer name is <em>Petrel 2</em>. From the two dropdown lists
-at the top of the screen, select the correct vendor and dive computer names (see image on the left, below).</p></div>
-<div class="paragraph"><p>Now tap the button labeled <em>Download</em>. The downloaded dives appear in the bottom part of the screen, the
-most recent dive at the top (see image on right, below). Be patient because the download can take a few minutes.
-As a matter of fact, a complete first download from some dive computers has been shown to take 45 minutes and longer.</p></div>
-<div class="paragraph"><p>After the download, each dive has a check-box on the left hand side, used for selecting which dives you want to be added to the
-<em>Subsurface-mobile</em> dive list: dives that are not checked are ignored. With the appropriate downloaded dives
-having been checked, tap the button at the bottom left labeled <em>Accept</em>. All the selected dives appear on
-the <em>Subsurface-mobile</em> dive list. The downloaded dive information can now be edited as described in the section
-above <a href="#S_Edit_Dive">Edit a dive</a>.</p></div>
-<div class="imageblock" style="text-align:center;">
-<div class="content">
-<img src="mobile-images/DC-Download.jpg" alt="FIGURE: DC download screen" />
-</div>
-</div>
-</div>
-</div>
-<div class="sect1">
-<h2 id="_viewing_the_dive_location_on_google_maps">10. Viewing the dive location on Google Maps</h2>
-<div class="sectionbody">
-<div class="paragraph"><p>In the <em>Details View</em>, the Action Bar at the bottom has a GPS pin on the
-left hand side. Tap that pin and the dive site is shown in Google Maps. Close Google Maps by using the Android <em>Back</em> button
-or tapping on the <em>Subsurface-mobile</em> link in the top left corner on iOS.</p></div>
-<div class="paragraph"><p>Alternatively, the <em>Details View</em> has a button at the top right hand marked
-<em>Map it</em>. Tap this button to open Google Maps showing the dive site (image below).</p></div>
-<div class="imageblock" style="text-align:center;">
-<div class="content">
-<img src="mobile-images/Map.jpg" alt="FIGURE: Map of dive site" />
-</div>
-</div>
-</div>
-</div>
-<div class="sect1">
-<h2 id="_dive_log_management">11. Dive log management</h2>
-<div class="sectionbody">
-<div class="paragraph"><p>A central  part of <em>Subsurface-mobile</em> is the ability to store the dive
-log using the <em>Subsurface</em> cloud storage.
-This provides security against loss or damage to the dive information in a local copy
-and allows the desktop version of <em>Subsurface</em> to
-access changes made using the mobile device. This ability is accessed
-through the main menu (by dragging the Action Button to the right, or
-by tapping the "Hamburger" icon at the bottom left of the screen).
-Tap the option <em>Dive management</em>, enabling a number of options:</p></div>
-<div class="sect2">
-<h3 id="_add_new_dive_manually">11.1. Add new dive manually</h3>
-<div class="paragraph"><p>This is described above under the section dealing with <a href="#S_Add_Dive">Manually adding a new dive to the dive list</a>.</p></div>
-</div>
-<div class="sect2">
-<h3 id="_download_from_dc">11.2. Download from DC</h3>
-<div class="paragraph"><p>This is described above under the section dealing with <a href="#S_Download">Download dives from a dive computer</a>.</p></div>
-</div>
-<div class="sect2">
-<h3 id="_apply_gps_fixes">11.3. Apply GPS fixes</h3>
-<div class="paragraph"><p>This is described in the following main section, below.</p></div>
-</div>
-<div class="sect2">
-<h3 id="_manually_sync_the_dive_log_with_the_em_subsurface_em_cloud_storage">11.4. Manually sync the dive log with the <em>Subsurface</em> cloud storage</h3>
-<div class="paragraph"><p>Upload the dives contained on the mobile device
-to the <em>Subsurface</em> cloud storage by tapping the option <em>Manual sync with cloud</em>.
-This synchronizes the local changes to
-the dive log with the cloud storage. It also downloads changes made to
-the dive log using another device or computer and stored in shared cloud storage.</p></div>
-</div>
-<div class="sect2">
-<h3 id="_enable_cloud_auto_sync">11.5. Enable cloud auto sync</h3>
-<div class="paragraph"><p>By default <em>Subsurface-mobile</em> runs offline and only syncs the dive list
-with cloud storage when explicitly told to do so (see above).
-You can choose to always sync with the cloud servers after every
-modification of the dive list. This is not recommended unless you are in
-an area with fast and reliable internet connection, as otherwise
-<em>Subsurface-mobile</em> might appear to hang between operations as it tries to
-connect to the cloud server. Selecting <em>Enable cloud auto sync</em> causes
-the local dive log to be synchronized with the copy in the cloud every time that
-<em>Subsurface-mobile</em> is closed. This option is a switch that allows auto
-sync to be either activated or to be switched off.</p></div>
-</div>
-</div>
-</div>
-<div class="sect1">
-<h2 id="_recording_dive_locations_using_gps">12. Recording dive locations using GPS</h2>
-<div class="sectionbody">
-<div class="paragraph"><p>The fact that most smartphones have GPS facilities allows
-<em>Subsurface-mobile</em> to record
-the locations of dives. If the smartphone is taken on the dive boat
-during a dive, locations will be automatically recorded at regular intervals.
-These locations can then be applied to dives in the dive list. Here is how it&#8217;s done:</p></div>
-<div class="sect2">
-<h3 id="S_ConfigureGPS">12.1. Configuring the GPS service</h3>
-<div class="paragraph"><p>From the Main menu, select <em>Settings</em>. The Settings screen has a section for
-configuring the GPS service (image below). GPS location data
-are collected at regular intervals, e.g. every 5 minutes, or at regular
-distances, e.g. after the boat has moved more than 200m, or a combination of
-both of these approaches. Provide the appropriate information and
-tap the <em>Back</em> button. The program is now ready to collect GPS positions.</p></div>
-<div class="imageblock" style="text-align:center;">
-<div class="content">
-<img src="mobile-images/GPS-config.jpg" alt="FIGURE: GPS configure" />
-</div>
-</div>
-</div>
-<div class="sect2">
-<h3 id="_collecting_gps_positions">12.2. Collecting GPS positions</h3>
-<div class="paragraph"><p>Ensure that the GPS on the mobile device has been activated and that you
-have given the app permission to access your location data.
-Open the Main Menu and select <em>GPS &#8594; Run location service</em>. This activates the
-recording of GPS locations.</p></div>
-<div class="imageblock" style="text-align:center;">
-<div class="content">
-<img src="mobile-images/GPSstart.jpg" alt="FIGURE: GPS start" />
-</div>
-</div>
-<div class="paragraph"><p><em>Subsurface-mobile</em> starts to collect GPS locations automatically,
-following the preferences specified as described above. While the GPS
-location service is running, all menus have a GPS symbol at the bottom
-of the menu, indicating that the service is active. After return from
-the dive trip, deactivate the collection of GPS data by tapping
-the option <em>Disable location service</em>. The GPS symbol at the bottom
-of all manus disappears.</p></div>
-</div>
-<div class="sect2">
-<h3 id="_storing_the_gps_data_on_the_em_subsurface_em_cloud">12.3. Storing the GPS data on the <em>Subsurface</em> cloud</h3>
-<div class="paragraph"><p>Activate the main menu and select the <em>GPS</em> option that brings up the submenu
-of GPS-related actions. Tap <em>Upload GPS data</em> that saves the GPS data
-on the <em>Subsurface</em> cloud server. These GPS data are saved <strong>separately</strong>
-from the other dive log data. All collected GPS data are kept on the
-Android device, independent of whether they have been uploaded or not.</p></div>
-</div>
-<div class="sect2">
-<h3 id="_downloading_gps_data_from_the_em_subsurface_em_cloud">12.4. Downloading GPS data from the <em>Subsurface</em> cloud</h3>
-<div class="paragraph"><p>Download the GPS data that have been saved on the cloud (possibly by a
-different device) by
-selecting <em>Download GPS Data</em> from the GPS sub-panel.</p></div>
-</div>
-<div class="sect2">
-<h3 id="_viewing_gps_data">12.5. Viewing GPS data</h3>
-<div class="paragraph"><p>From the GPS submenu select <em>Show GPS fixes</em>. This brings
-up a list of GPS positions obtained by the location service (image
-below). Two actions are possible for each of the locations, enabled by
-dragging the handle (the dotted matrix on the right below) to the left. This exposes two
-options. Tapping the dustbin deletes this particular GPS location. Tapping the
-teardrop-shaped icon (actually a Google Maps pin) opens up Google Maps with a pin
-indicating the exact map position of the GPS record being viewed. The two above
-options can be hidden by drawing the GPS record to the right, again using the handle.</p></div>
-<div class="imageblock" style="text-align:center;">
-<div class="content">
-<img src="mobile-images/gpsmanagement.jpg" alt="FIGURE: GPS management" />
-</div>
-</div>
-</div>
-<div class="sect2">
-<h3 id="_applying_gps_data_to_dives_in_the_dive_log">12.6. Applying GPS data to dives in the dive log</h3>
-<div class="paragraph"><p>Assuming that all the dives have been entered into the dive log or have
-been downloaded from the <em>Subsurface</em> cloud, apply the GPS positions to
-these dives. GPS positions can therefore only be applied to dives in the dive list.
-From the <em>Dive management</em> sub-panel, tap <em>Apply GPS fixes</em>. The dive list contains the start
-and end times of each dive. Now, <em>Subsurface-mobile</em> applies the first
-GPS position that falls within the dive period of each dive. This results
-in a GPS position for each dive that is saved as part of the dive log.</p></div>
-</div>
-</div>
-</div>
-<div class="sect1">
-<h2 id="_using_the_settings_for_em_subsurface_mobile_em">13. Using the settings for <em>Subsurface-mobile</em>.</h2>
-<div class="sectionbody">
-<div class="paragraph"><p>The Settings screen allows the customization of <em>Subsurface-mobile</em>. Many of the settings involve dragging a slider switch to activate or deactivate a particular setting.</p></div>
-<div class="sect2">
-<h3 id="S_ChangeCloudAccount">13.1. Changing to a different <em>Subsurface</em> cloud account</h3>
-<div class="paragraph"><p>Some users have more than one <em>Subsurface</em> cloud account and with a need to switch between accounts. Tap <em>Settings</em> on the Main menu and scroll to the section titled <em>Cloud status</em> (see image below).
-Tap the <em>Change</em> button. This opens the <em>Cloud credentials</em> screen.
-change the credential information, then tap the button <em>Sign-in or register</em>. The appropriate dive list is shown.</p></div>
-<div class="imageblock" style="text-align:center;">
-<div class="content">
-<img src="mobile-images/SettingsCloudTheme.jpg" alt="FIGURE: Settings: Cloud &amp; Theme" />
-</div>
-</div>
-</div>
-<div class="sect2">
-<h3 id="_changing_the_color_theme_of_em_subsurface_mobile_em">13.2. Changing the color theme of <em>Subsurface-mobile</em></h3>
-<div class="paragraph"><p><em>Subsurface-mobile</em> has three color schemes to please users with different
-tastes. This user manual shows the default color scheme, comprising blue
-colors. Change to a pink or a dark color scheme by opening the main menu,
-tap <em>Settings</em>, and scroll to the section with heading <em>Theme</em> (see image above).
-Select the appropriate color theme by dragging the appropriate slider on the righthand.</p></div>
-</div>
-<div class="sect2">
-<h3 id="_configuring_the_gps_webservice">13.3. Configuring the GPS webservice</h3>
-<div class="paragraph"><p>The Settings screen allows one to set up the way in which GPS positions are collected during dives. See the section on <a href="#S_ConfigureGPS">Configuring the GPS service</a>.</p></div>
-</div>
-<div class="sect2">
-<h3 id="_saving_a_detailed_dive_computer_dive_log">13.4. Saving a detailed dive computer dive log</h3>
-<div class="paragraph"><p>Under the heading <em>Dive computer</em>, you will find a switch to save a detailed log each time dives are downloaded from a dive computer. This is important for solving problems in downloading dives from the dive computer. When contacting the developers with download problems, you will usually be asked to provide the information in this log, which can be found in the root folder of your local storage device as <code>libdivecomputer.log</code>. In the same location you can also find a <code>subsurfacel.log</code> which is always created and which include more information which can be helpful when debugging problems with Subsurface-mobile.</p></div>
-</div>
-<div class="sect2">
-<h3 id="_activating_the_developer_submenu">13.5. Activating the Developer submenu</h3>
-<div class="paragraph"><p>The information in subsurface.log plus some additional information for understanding the screen rendering of dive information as well as the way in which <em>Subsurface-mobile</em> processed information during a specific occasion while running the app (see section below) is available through a <em>Developer</em> menu at run time. Activate (or deactivate) this menu item on the Main Menu by dragging the slider switch in the Settings screen.</p></div>
-</div>
-</div>
-</div>
-<div class="sect1">
-<h2 id="_developer_submenu">14. Developer submenu</h2>
-<div class="sectionbody">
-<div class="paragraph"><p>If the Developer submenu has been activated in the Settings screen, the Main menu has a <em>Developer</em> item. By tapping this one has two options that are relevant within
-the context of program development and debugging.</p></div>
-<div class="sect2">
-<h3 id="_app_log">14.1. App log</h3>
-<div class="paragraph"><p>This option shows the messages that <em>Subsurface-mobile</em> generates while running. While
-most users are not aware of these messages, they are often crucial in detecting any
-abnormal behavior of the app. The App log can be found in the root directory of the local storage of the mobile device.</p></div>
-</div>
-<div class="sect2">
-<h3 id="_theme_information">14.2. Theme information</h3>
-<div class="paragraph"><p>This option provides a wealth of information about the screen characteristics of the mobile
-device and the font characteristics used by <em>Subsurface-mobile</em>.</p></div>
-</div>
-</div>
-</div>
-</div>
-<div id="footnotes"><hr /></div>
-<div id="footer">
-<div id="footer-text">
-Last updated
- 2018-09-21 19:29:32 PDT
-</div>
-</div>
-</body>
-</html>
author	Willem Ferguson <willemferguson@zoology.up.ac.za>	2020-05-05 17:46:48 -0700
committer	Dirk Hohndel <dirk@hohndel.org>	2020-05-05 17:55:02 -0700
commit	70ebc2bee7bc01e0758b7608cfbbe2e8a945c062 (patch)
tree	97262be1334832c8b8cdc6d494f43ad36e783196 /Documentation
parent	33b4ecf0555371e0c325ff05707d70ac9e69c8db (diff)
download	subsurface-70ebc2bee7bc01e0758b7608cfbbe2e8a945c062.tar.gz