Documentation: Add initial support for French translation

Add initial support to French (fr) translation of user-manual.

Note that it is not perfect, since the po4a tool loose some list item
indexes during PO to ASCIIDOC conversion (see asciidoc warning messages
during user manual generation).

Signed-off-by: Guillaume GARDET <guillaume.gardet@free.fr>
Signed-off-by: Dirk Hohndel <dirk@hohndel.org>

4 files changed, 14997 insertions, 1 deletions

diff --git a/Documentation/Makefile b/Documentation/Makefile
index 52b1d9cd6..3df677723 100644
--- a/Documentation/Makefile
+++ b/Documentation/Makefile
@@ -7,7 +7,7 @@
 # submitting patches to the user manual, only submit the changes to the .txt
 # file - the maintainer will recreate the .html.git file
 
-DOCNAMES = user-manual user-manual_es user-manual_ru
+DOCNAMES = user-manual user-manual_es user-manual_fr user-manual_ru
 
 HTMLDOCS = $(patsubst %,$(OUT)%.html,$(DOCNAMES))
 TEXTDOCS = $(patsubst %,$(OUT)%.text,$(DOCNAMES))
diff --git a/Documentation/fr/po/subsurface-manual.fr.po b/Documentation/fr/po/subsurface-manual.fr.po
new file mode 100644
index 000000000..a4582ba13
--- /dev/null
+++ b/Documentation/fr/po/subsurface-manual.fr.po
@@ -0,0 +1,6850 @@
+# French translations for PACKAGE package
+# Copyright (C) 2015 Free Software Foundation, Inc.
+# This file is distributed under the same license as the PACKAGE package.
+#
+# Guillaume GARDET <guillaume.gardet@free.fr>, 2015.
+msgid ""
+msgstr ""
+"Project-Id-Version: \n"
+"Report-Msgid-Bugs-To: subsurface@subsurface-divelog.org\n"
+"POT-Creation-Date: 2015-01-14 15:37+0100\n"
+"PO-Revision-Date: 2015-01-14 16:18+0100\n"
+"Last-Translator: Guillaume GARDET <guillaume.gardet@opensuse.org>\n"
+"Language-Team: French <opensuse-fr@opensuse.org>\n"
+"Language: fr\n"
+"MIME-Version: 1.0\n"
+"Content-Type: text/plain; charset=UTF-8\n"
+"Content-Transfer-Encoding: 8bit\n"
+"Plural-Forms: nplurals=2; plural=(n > 1);\n"
+"X-Generator: Lokalize 1.5\n"
+
+#.  :website: http://subsurface-divelog.org
+#. type: Target for macro image
+#: user-manual.txt:14
+#, no-wrap
+msgid "images/Subsurface4Banner.jpg"
+msgstr "images/Subsurface4Banner.jpg"
+
+#. type: Plain text
+#: user-manual.txt:17
+msgid "[big]#USER MANUAL#"
+msgstr "[big]#MANUEL UTILISATEUR#"
+
+#. type: Plain text
+#: user-manual.txt:20
+#, no-wrap
+msgid ""
+"*Manual authors*: Willem Ferguson, Jacco van Koll, Dirk Hohndel, Reinout Hoornweg,\n"
+"Linus Torvalds, Miika Turkia, Amit Chaudhuri, Jan Schubert, Salvador Cuñat, Pedro Neves\n"
+msgstr ""
+"*Auteurs du manuel* : Willem Ferguson, Jacco van Koll, Dirk Hohndel, Reinout Hoornweg,\n"
+"Linus Torvalds, Miika Turkia, Amit Chaudhuri, Jan Schubert, Salvador Cuñat, Pedro Neves\n"
+
+#. type: Plain text
+#: user-manual.txt:22
+msgid "[blue]#_Version 4.3, December 2014_#"
+msgstr "[blue]#_Version 4.3, Décembre 2014_#"
+
+#. type: Plain text
+#: user-manual.txt:28
+msgid ""
+"Welcome as a user of _Subsurface_, an advanced dive logging program with "
+"extensive infrastructure to describe, organise, interpret and print scuba "
+"and free dives. _Subsurface_ offers many advantages over other similar "
+"software solutions:"
+msgstr ""
+"Bienvenue en tant qu'utilisateur de _Subsurface_, un programme avancé "
+"d'enregistrement de plongées (carnet de plongées) avec une bonne "
+"infrastructure pour décrire, organiser, interpréter et imprimer des plongées "
+"en scaphandre et en apnée. _Subsurface_ offre de nombreux avantages par "
+"rapport à d'autres solutions logicielles similaires :"
+
+#. type: Plain text
+#: user-manual.txt:31
+msgid ""
+"Do you need a flexible way of logging dives using recreational equipment, "
+"even not using a dive computer?"
+msgstr ""
+
+#. type: Plain text
+#: user-manual.txt:37
+msgid ""
+"Do you use two different dive computer brands, each with its own proprietary "
+"software for downloading dive logs? Do you dive with rebreathers as well as "
+"open circuit or recreational equipment? Do you use a Reefnet Sensus time-"
+"depth recorder in conjunction with a dive computer? _Subsurface_ offers a "
+"standard interface for downloading dive logs from all these different pieces "
+"of equipment and to store and analyse the dive logs within a unified system."
+msgstr ""
+
+#. type: Plain text
+#: user-manual.txt:40
+msgid ""
+"Do you use more than one operating system? _Subsurface_ is fully compatible "
+"with Mac, Linux and Windows, allowing you to access your dive log on each of "
+"your operating systems using a single application."
+msgstr ""
+
+#. type: Plain text
+#: user-manual.txt:43
+msgid ""
+"Do you use Linux or Mac and your dive computer has only Windows-based "
+"software for downloading dive information (e.g. Mares)? _Subsurface_ "
+"provides a way of downloading and analysing your dive logs on other "
+"operating systems."
+msgstr ""
+
+#. type: Plain text
+#: user-manual.txt:45
+msgid ""
+"Do you need an intuitive graphical dive planner that integrates with and "
+"takes into account the dives that have already been logged?"
+msgstr ""
+
+#. type: Plain text
+#: user-manual.txt:50
+msgid ""
+"_Subsurface_ binaries are available for Windows PCs (Win XP or later), Intel "
+"based Macs (OS/X) and many Linux distributions. _Subsurface_ can be built "
+"for many more hardware platforms and software environments where Qt and "
+"libdivecomputer are available."
+msgstr ""
+
+#. type: Plain text
+#: user-manual.txt:59
+msgid ""
+"The scope of this document is the use of the _Subsurface_ program. To "
+"install the software, consult the _Downloads_ page on the http://subsurface-"
+"divelog.org/[_Subsurface_ web site].  Please discuss issues with this "
+"program by sending an email to mailto:subsurface@subsurface-divelog.org[our "
+"mailing list] and report bugs at http://trac.hohndel.org[our bugtracker].  "
+"For instructions on how to build the software and (if needed) its "
+"dependencies please consult the INSTALL file included with the source code."
+msgstr ""
+
+#. type: Plain text
+#: user-manual.txt:62
+#, no-wrap
+msgid ""
+"*Audience*: Recreational Scuba Divers, Free Divers, Tec Divers, Professional\n"
+"Divers\n"
+msgstr ""
+
+#. type: Plain text
+#: user-manual.txt:64
+msgid "toc::[]"
+msgstr "toc::[]"
+
+#. type: Title -
+#: user-manual.txt:68
+#, no-wrap
+msgid "The user survey"
+msgstr "Le sondage utilisateur"
+
+#. type: Plain text
+#: user-manual.txt:80
+msgid ""
+"In order to develop _Subsurface_ in a way that serves its users in the best "
+"possible way, it is important to have some user information. Upon launching "
+"_Subsurface_ after using this software for a week or so, a one-box user "
+"survey pops up. It is entirely optional and the user controls what, if any, "
+"data are sent to the _Subsurface_ development team. Any data that the user "
+"chooses to send is extremely useful, and will only be used to steer future "
+"development and to customise the software to fit the needs of the "
+"_Subsurface_ users. If one completes the survey, or clicks the option not to "
+"be asked again, that should be the last communication of this nature one "
+"receives.  However, if one's diving and/or subsurface habits change and one "
+"wishes to provide another survey, this can be done by launching _Subsurface_ "
+"with the _--survey_ option on the command line."
+msgstr ""
+
+#. type: Title -
+#: user-manual.txt:83
+#, no-wrap
+msgid "Start Using the Program"
+msgstr ""
+
+#. type: Plain text
+#: user-manual.txt:88
+msgid ""
+"The _Subsurface_ window is usually divided into four panels with a *Main "
+"Menu* (File Import Log View Filter Help) at the top of the window (for "
+"Windows and Linux) or the top of the screen (for Mac and Ubuntu Unity). The "
+"four panels are:"
+msgstr ""
+
+#. type: Plain text
+#: user-manual.txt:94
+msgid ""
+"The *Dive List* to the bottom left containing a list of all the dives in the "
+"user's dive log. A dive can be selected and highlighted on the dive list by "
+"clicking on it. In most situations the up/down keys can be used to switch "
+"between dives. The *Dive List* is an important tool for manipulating a dive "
+"log."
+msgstr ""
+
+#. type: Plain text
+#: user-manual.txt:98
+msgid ""
+"The *Dive Map* to the bottom right, showing the user's dive sites on a world "
+"map and centred on the site of the last dive selected in the *Dive List*."
+msgstr ""
+
+#. type: Plain text
+#: user-manual.txt:102
+msgid ""
+"The *Dive Info* to the top left, giving more detailed information on the "
+"dive selected in the *Dive List*, including some statistics for the selected "
+"dive or for all highlighted dive(s)."
+msgstr ""
+
+#. type: Plain text
+#: user-manual.txt:105
+msgid ""
+"The *Dive Profile* to the top right, showing a graphical dive profile of the "
+"selected dive in the *Dive List*."
+msgstr ""
+
+#. type: Plain text
+#: user-manual.txt:110
+msgid ""
+"The dividers between panels can be dragged in order to change the size of "
+"any of the panels. _Subsurface_ remembers the position of the dividers, so "
+"the next time _Subsurface_ starts it uses the positions of the dividers from "
+"when the program was last used."
+msgstr ""
+
+#. type: Plain text
+#: user-manual.txt:118
+msgid ""
+"If a dive is selected in the *Dive List*, the dive location, detailed "
+"information and profile of the _selected dive_ are shown in the respective "
+"panels. On the other hand, if one highlights more than one dive the last "
+"highlighted dive is the _selected dive_, but summary data of all "
+"_highlighted dives_ are shown in the *Stats* tab of the *Dive Info* panel "
+"(maximum, minimum and average depths, durations, water temperatures and SAC; "
+"total time and number of dives selected)."
+msgstr ""
+
+#. type: Target for macro image
+#: user-manual.txt:121
+#, no-wrap
+msgid "images/main_window_f20.jpg"
+msgstr ""
+
+#. type: Plain text
+#: user-manual.txt:126
+msgid ""
+"The user can determine which of the four panels are displayed by selecting "
+"the *View* option on the main menu. This feature gives the user several "
+"choices of display:"
+msgstr ""
+
+#. type: Plain text
+#: user-manual.txt:128
+#, no-wrap
+msgid "*All*: show all four of the panels as in the screenshot above.\n"
+msgstr ""
+
+#. type: Plain text
+#: user-manual.txt:130
+#, no-wrap
+msgid "*Divelist*: Show only the Dive List.\n"
+msgstr ""
+
+#. type: Plain text
+#: user-manual.txt:132
+#, no-wrap
+msgid "*Profile*: Show only the Dive Profile of the selected dive.\n"
+msgstr ""
+
+#. type: Plain text
+#: user-manual.txt:135
+#, no-wrap
+msgid ""
+"*Info*: Show only the Dive Notes about the last selected dive and statistics for\n"
+"all highlighted dives.\n"
+msgstr ""
+
+#. type: Plain text
+#: user-manual.txt:137
+#, no-wrap
+msgid "*Globe*: Show only the world map, centred on the last selected dive.\n"
+msgstr ""
+
+#. type: Plain text
+#: user-manual.txt:143
+msgid ""
+"Like many other functions that can be accessed via the Main Menu, these "
+"options can be triggered using keyboard shortcuts. The shortcuts for a "
+"particular system are shown with an underline in the main menu entries. "
+"Since different Operating Systems and the user chosen language may cause "
+"_Subsurface_ to use different shortcut keys they are not listed here in the "
+"user manual."
+msgstr ""
+
+#. type: Plain text
+#: user-manual.txt:147
+msgid ""
+"When the program is started for the first time, it shows no information at "
+"all.  This is because the program doesn't have any dive information "
+"available. In the following sections, the procedures to create a new logbook "
+"will be described."
+msgstr ""
+
+#. type: Title -
+#: user-manual.txt:150
+#, no-wrap
+msgid "Creating a new logbook"
+msgstr ""
+
+#. type: Plain text
+#: user-manual.txt:155
+msgid ""
+"Select _File -> New Logbook_ from the main menu. All existing dive data are "
+"cleared so that new information can be added. If there are unsaved data in "
+"an open logbook, the user is asked whether the open logbook should be saved "
+"before a new logbook is created."
+msgstr ""
+
+#. type: Title ==
+#: user-manual.txt:157
+#, no-wrap
+msgid "Storing dive information in the logbook"
+msgstr ""
+
+#. type: Plain text
+#: user-manual.txt:162
+msgid ""
+"Now that a new logbook was created, it is simple to add dive data to it.  "
+"_Subsurface_ allows several ways of adding dive data to a logbook, detailed "
+"in the following sections."
+msgstr ""
+
+#. type: Plain text
+#: user-manual.txt:166
+msgid ""
+"If the user has a handwritten divelog, a spreadsheet or another form of "
+"manually maintained divelog, dive data can be added to the logbook using one "
+"of these approaches:"
+msgstr ""
+
+#. type: Plain text
+#: user-manual.txt:170
+msgid ""
+"Enter dive information by hand. This is useful if the diver did not use a "
+"dive computer and dives were recorded in a written logbook. See: xref:"
+"S_EnterData[Entering dive information by hand]"
+msgstr ""
+
+#. type: Plain text
+#: user-manual.txt:174
+msgid ""
+"Import dive log information that has been maintained either as a spreadsheet "
+"or as a CSV file. Refer to: xref:S_Appendix_D[APPENDIX D: Exporting a "
+"spreadsheet to CSV format] and the text about xref:"
+"S_ImportingManualCSV[Importing dives from manually created CSV files] and"
+msgstr ""
+
+#. type: Plain text
+#: user-manual.txt:178
+msgid ""
+"If one has dives recorded using a dive computer, the depth profile of the "
+"dive and a large amount of additional information can be accessed. These "
+"dives can be imported from:"
+msgstr ""
+
+#. type: Plain text
+#: user-manual.txt:180
+msgid ""
+"The divecomputer itself. See: xref:S_ImportDiveComputer[Importing new dive "
+"information from a Dive Computer] or"
+msgstr ""
+
+#. type: Plain text
+#: user-manual.txt:183
+msgid ""
+"Proprietary software distributed by manufacturers of dive computers. Refer "
+"to: xref:S_ImportingAlienDiveLogs[Importing dive information from other "
+"digital data sources or other data formats]."
+msgstr ""
+
+#. type: Plain text
+#: user-manual.txt:186
+msgid ""
+"Import from spreadsheet or CSV files containing dive profiles.  See: xref:"
+"S_ImportingCSVDives[Importing dives in CSV format from dive computers or "
+"other dive log software]"
+msgstr ""
+
+#. type: Title ===
+#: user-manual.txt:189
+#, no-wrap
+msgid "Entering dive information by hand"
+msgstr ""
+
+#. type: Plain text
+#: user-manual.txt:203
+msgid ""
+"This is usually the approach for dives without a dive computer. The basic "
+"record of information within _Subsurface_ is a dive. The most important "
+"information in a simple dive logbook usually includes dive type, date, time, "
+"duration, depth, the names of your dive buddy and of the dive master or dive "
+"guide, and some remarks about the dive. _Subsurface_ can store much more "
+"information than this for each dive. In order to add a dive to a dive log, "
+"select _Log -> Add Dive_ from the Main Menu. The program then shows three "
+"panels to enter information for a dive: two tabs in the *Dive Info* panel "
+"(*Dive Notes* and *Equipment*), as well as the *Dive Profile* panel that "
+"displays a graphical profile of each dive. These panels are respectively "
+"marked [red]#A#, [red]#B# and [red]#C# in the figure below. Each of these "
+"tabs will now be explained for data entry."
+msgstr ""
+
+#. type: Target for macro image
+#: user-manual.txt:204
+#, no-wrap
+msgid "images/AddDive1_f20.jpg"
+msgstr ""
+
+#. type: Plain text
+#: user-manual.txt:209
+msgid ""
+"When one edits a field in Dive notes or Equipment panels, _Subsurface_ "
+"enters *Editing Mode*, indicated by the message in the blue box at the top "
+"of the _Dive Notes_ panel (see the image below). This message is displayed "
+"in all the panels under Dive notes and Equipment when in *Editing Mode*."
+msgstr ""
+
+#. type: Target for macro image
+#: user-manual.txt:210 user-manual.txt:787
+#, no-wrap
+msgid "images/BlueEditBar_f20.jpg"
+msgstr ""
+
+#. type: Plain text
+#: user-manual.txt:217
+msgid ""
+"The _Save_ button should only be selected after all the parts of a dive have "
+"been entered.  When entering dives by hand, the _Info_, _Equipment_ and "
+"_Profile_ tabs should be completed before saving the information. By "
+"selecting the _Save_ button, a local copy of the information for this "
+"specific dive is saved in memory. When one closes Subsurface, the program "
+"will ask again, this time whether the complete dive log should be saved on "
+"disk or not."
+msgstr ""
+
+#. type: Title ====
+#: user-manual.txt:218 user-manual.txt:673
+#, no-wrap
+msgid "Dive Notes"
+msgstr ""
+
+#. type: Plain text
+#: user-manual.txt:224
+msgid ""
+"This panel contains the date, time and place information for a particular "
+"dive, environmental conditions, co-divers and buddies, as well as some "
+"descriptive information. If one clicks on the *Dive Notes* tab, the "
+"following fields are visible:"
+msgstr ""
+
+#. type: Target for macro image
+#: user-manual.txt:225
+#, no-wrap
+msgid "images/AddDive2_f20.jpg"
+msgstr ""
+
+#. type: Plain text
+#: user-manual.txt:234
+msgid ""
+"The *Time* field reflects the date and the time of the dive. By clicking the "
+"date, a calendar is displayed from which one can choose the correct date. "
+"Press ESC to escape from the calendar.  The time values (hour and minutes) "
+"can also be edited directly by clicking on each of them in the text box and "
+"by overtyping the information displayed. The default date is the present "
+"date and the default time is an hour in advance of the present time."
+msgstr ""
+
+#. type: Plain text
+#: user-manual.txt:241
+#, no-wrap
+msgid ""
+"*Air and water temperatures*: the air and water temperatures during the\n"
+"dive can be typed directly on the fields to the right of the Start time.\n"
+"Temperature units are not needed, as they will be automatically supplied by\n"
+"_Subsurface_. Only the numerical value must be\n"
+"typed by the user (the units selected in the 'Preferences'\n"
+"will determine whether metric or imperial units are used).\n"
+msgstr ""
+
+#. type: Plain text
+#: user-manual.txt:246
+#, no-wrap
+msgid ""
+"*Location*: Here the name of the dive site can be entered, e.g. \"Tihany, Lake\n"
+"Balaton,\n"
+"Hungary\". Auto completion of location names will make this easier if one\n"
+"frequently dives at the same sites.\n"
+msgstr ""
+
+#. type: Plain text
+#: user-manual.txt:249 user-manual.txt:710
+#, no-wrap
+msgid ""
+"*Coordinates*: The geographic coordinates of the dive site should be entered\n"
+"here. These can come from three sources:\n"
+msgstr ""
+
+#. type: Plain text
+#: user-manual.txt:256
+msgid ""
+"One can find the coordinates on the world map in the bottom right hand part "
+"of the Subsurface window. The map displays a green bar indicating \"No "
+"location data - Move the map and double-click to set the dive location\". "
+"Upon a double-click at the appropriate place, the green bar disappears and "
+"the coordinates are stored."
+msgstr ""
+
+#. type: Plain text
+#: user-manual.txt:261
+msgid ""
+"The coordinates can be obtained from the _Subsurface_ Companion app if the "
+"user has an Android device with GPS and if the coordinates of the dive site "
+"were stored using that device.  xref:S_Companion[Click here for more "
+"information]"
+msgstr ""
+
+#. type: Plain text
+#: user-manual.txt:264 user-manual.txt:725
+msgid ""
+"The coordinates can be entered by hand if they are known, using one of four "
+"formats with latitude followed by longitude:"
+msgstr ""
+
+#. type: Plain text
+#: user-manual.txt:269 user-manual.txt:730
+#, no-wrap
+msgid ""
+"\tISO 6709 Annex D format e.g. 30°13'28.9\"N 30°49'1.5\"E\n"
+"\tDegrees and decimal minutes, e.g. N30° 13.49760' , E30° 49.30788'\n"
+"\tDegrees minutes seconds, e.g. N30° 13' 29.8\" , E30° 49' 1.5\"\n"
+"\tDecimal degrees, e.g. 30.22496 , 30.821798\n"
+msgstr ""
+
+#. type: Plain text
+#: user-manual.txt:273
+msgid ""
+"Southern hemisphere latitudes are given with a *S*, e.g. S30°, or with a "
+"negative value, e.g. -30.22496. Similarly western longitudes are given with "
+"a *W*, e.g. W07°, or with a negative value, e.g. -7.34323."
+msgstr ""
+
+#. type: Plain text
+#: user-manual.txt:279 user-manual.txt:740
+msgid ""
+"Please note that GPS coordinates of a dive site are linked to the Location "
+"name - so adding coordinates to dives that do not have a location "
+"description will cause unexpected behaviour (Subsurface will think that all "
+"of these dives have the same location and try to keep their GPS coordinates "
+"the same)."
+msgstr ""
+
+#. type: Plain text
+#: user-manual.txt:284
+#, no-wrap
+msgid ""
+"*Divemaster*: The name of the dive master or dive guide for this dive can be\n"
+"entered here.\n"
+"Again, this field offers auto completion based on the list of dive masters in\n"
+"the current logbook.\n"
+msgstr ""
+
+#. type: Plain text
+#: user-manual.txt:288
+#, no-wrap
+msgid ""
+"*Buddy*: In this field one can enter the name(s) of the buddy / buddies\n"
+"(separated by commas) who accompanied the user on the dive. Auto completion\n"
+"is offered based on the list of buddies in the current logbook.\n"
+msgstr ""
+
+#. type: Plain text
+#: user-manual.txt:293
+#, no-wrap
+msgid ""
+"*Suit*: The type of diving suit used for the dive can be entered here.\n"
+"As with the other items, auto completion of the suit description is available.\n"
+"Some dry-suit users may choose to use this field to record what combination of\n"
+"suit and thermal protection undersuit was used.\n"
+msgstr ""
+
+#. type: Plain text
+#: user-manual.txt:296 user-manual.txt:758
+#, no-wrap
+msgid ""
+"*Rating*: One can provide a subjective overall rating of the dive on a\n"
+"5-point scale by clicking the appropriate star on the rating scale.\n"
+msgstr ""
+
+#. type: Plain text
+#: user-manual.txt:300 user-manual.txt:762
+#, no-wrap
+msgid ""
+"*Visibility*: Similarly, one can provide a rating of visibility during the\n"
+"dive on a\n"
+"5-point scale by clicking the appropriate star.\n"
+msgstr ""
+
+#. type: Plain text
+#: user-manual.txt:306
+#, no-wrap
+msgid ""
+"*Tags*: Tags that describe the type of dive performed may\n"
+"be entered here (separated by commas). Examples of common tags are boat, drift,\n"
+"training, cave etc. _Subsurface_ has many built-in tags. Auto completion is once again offered.\n"
+"For instance, if +cav+ was typed, then the tags *cave* and *cavern* are\n"
+"shown for the user to choose from.\n"
+msgstr ""
+
+#. type: Plain text
+#: user-manual.txt:308
+#, no-wrap
+msgid "*Notes*: Any additional information can be typed here.\n"
+msgstr ""
+
+#. type: Plain text
+#: user-manual.txt:313 user-manual.txt:778
+msgid ""
+"The *Save* and *Cancel* buttons are used to save all the information for "
+"tabs in the info panel and in the dive profile panel, so there's no need to "
+"use them until ALL other information has been added. Here is an example of a "
+"completed Dive Notes panel:"
+msgstr ""
+
+#. type: Target for macro image
+#: user-manual.txt:314 user-manual.txt:779
+#, no-wrap
+msgid "images/CompletedDiveInfo_f20.jpg"
+msgstr ""
+
+#. type: Title ====
+#: user-manual.txt:316 user-manual.txt:781
+#, no-wrap
+msgid "Equipment"
+msgstr ""
+
+#. type: Plain text
+#: user-manual.txt:323
+msgid ""
+"The Equipment tab allows the user to enter information about the type of "
+"cylinder and gas used, as well as the weights used for a dive. This is a "
+"highly interactive part of _Subsurface_ and the information on cylinders and "
+"gases (entered here) affects the behaviour of the dive profile (top right-"
+"hand panel)."
+msgstr ""
+
+#. type: Plain text
+#: user-manual.txt:327 user-manual.txt:796
+#, no-wrap
+msgid ""
+"*Cylinders*: The cylinder information is entered through a dialogue that looks\n"
+"like this:\n"
+msgstr ""
+
+#. type: Target for macro image
+#: user-manual.txt:328
+#, no-wrap
+msgid "images/Gas_dialogue1_f20.jpg"
+msgstr ""
+
+#. type: Plain text
+#: user-manual.txt:336
+msgid ""
+"The + button at the top right allows the user to add more cylinders for this "
+"dive.  The dark dustbin icon on the left allows one to delete information "
+"for a particular cylinder. Note that it is not possible to delete a cylinder "
+"if it is used during the dive. One cylinder is implicitly used in the dive, "
+"even without a gas change event. Thus the first cylinder cannot be deleted "
+"until another cylinder is created."
+msgstr ""
+
+#. type: Plain text
+#: user-manual.txt:341
+msgid ""
+"Start by selecting a cylinder type on the left-hand side of the table.  To "
+"select a cylinder, click in the *Type* box.  This brings up a button that "
+"can be used to display a dropdown list of cylinders:"
+msgstr ""
+
+#. type: Target for macro image
+#: user-manual.txt:342
+#, no-wrap
+msgid "images/Gas_dialogue2_f20.jpg"
+msgstr ""
+
+#. type: Plain text
+#: user-manual.txt:350
+msgid ""
+"The drop-down list can be used to select the cylinder type used for the dive "
+"or the user may start typing in the box which shows the available options "
+"for the entered characters. The *Size* of the cylinder as well as its "
+"working pressure (*WorkPress*) will automatically be shown in the dialogue. "
+"If a cylinder is not shown in the dropdown list, type the name and "
+"description of that cylinder into the *Type* field."
+msgstr ""
+
+#. type: Plain text
+#: user-manual.txt:355
+msgid ""
+"Next, indicate the starting pressure and the ending pressure of the gas used "
+"during the dive. The unit of pressure (metric/imperial) corresponds to the "
+"setting in the _Preferences_."
+msgstr ""
+
+#. type: Plain text
+#: user-manual.txt:366
+msgid ""
+"Finally, type in the gas mixture used in the *O2%* field. If air was used, a "
+"value of 21% can be entered on this field, or it might be left blank. If "
+"nitrox or trimix were used, their percentages of oxygen and/or helium must "
+"be specified.  Any inappropriate fields should be left empty. After typing "
+"the information for the cylinder, press _ENTER_ on the keyboard or click "
+"outside the cell that contains the cursor. Information for any additional "
+"cylinders can be added by using the + button at the top right hand. "
+"Following is an example of a complete description for a dive made using two "
+"cylinders (air and EAN50):"
+msgstr ""
+
+#. type: Target for macro image
+#: user-manual.txt:367 user-manual.txt:834
+#, no-wrap
+msgid "images/CylinderDataEntry3_f20.jpg"
+msgstr ""
+
+#. type: Plain text
+#: user-manual.txt:373
+#, no-wrap
+msgid ""
+"*Weights*: Information about the weight system used during a dive can be entered\n"
+"using a dialogue very similar to that for the cylinder information. If the user\n"
+"clicks the + button on the top right of the weights dialogue, the table looks\n"
+"like this:\n"
+msgstr ""
+
+#. type: Target for macro image
+#: user-manual.txt:374 user-manual.txt:842
+#, no-wrap
+msgid "images/WeightsDataEntry1_f20.jpg"
+msgstr ""
+
+#. type: Plain text
+#: user-manual.txt:378
+msgid ""
+"If one then clicks on the *Type* field, a drop-down list becomes accessible "
+"through a down-arrow:"
+msgstr ""
+
+#. type: Target for macro image
+#: user-manual.txt:379 user-manual.txt:847
+#, no-wrap
+msgid "images/WeightsDataEntry2_f20.jpg"
+msgstr ""
+
+#. type: Plain text
+#: user-manual.txt:393
+msgid ""
+"The drop-down list can then be used to select the type of weight system or "
+"the user may start typing in the box which shows the available options for "
+"the entered characters. In the *Weight* field, the weight used during the "
+"dive must be typed. After typing the information for the weight system the "
+"user must either press _ENTER_ on the keyboard or click outside the cell "
+"that contains the cursor. It is possible to enter information for more than "
+"one weight system by adding an additional system using the + button on the "
+"top right hand. Weight systems can be deleted using the dustbin icon on the "
+"left hand. Here is an example of information for a dive with two types of "
+"weights: integrated and a weight belt:"
+msgstr ""
+
+#. type: Target for macro image
+#: user-manual.txt:394 user-manual.txt:863
+#, no-wrap
+msgid "images/WeightsDataEntry3_f20.jpg"
+msgstr ""
+
+#. type: Plain text
+#: user-manual.txt:398
+msgid ""
+"There's NO need to click the _Save_ button before the dive profile has been "
+"completed."
+msgstr ""
+
+#. type: Title ====
+#: user-manual.txt:400
+#, no-wrap
+msgid "Creating a Dive Profile"
+msgstr ""
+
+#. type: Plain text
+#: user-manual.txt:407
+msgid ""
+"The *Dive Profile* (a graphical representation of the depth of the dive as a "
+"function of time) is indicated in the panel on the top right hand of the "
+"_Subsurface_ window. When a dive is manually added to a logbook, "
+"_Subsurface_ presents a default dive profile that needs to be modified to "
+"best represent the dive being described:"
+msgstr ""
+
+#. type: Target for macro image
+#: user-manual.txt:408
+#, no-wrap
+msgid "images/DiveProfile1_f20.jpg"
+msgstr ""
+
+#. type: Plain text
+#: user-manual.txt:426
+msgid ""
+"_Modifying the dive profile_: When the cursor is moved around the dive "
+"profile, its position is indicated by two coloured lines (red and green) as "
+"shown below.  The depth and time that the cursor represents are indicated at "
+"the top of the black information box (@ and D). The units (metric/imperial) "
+"on the axes are determined by the *Preference* settings. The dive profile "
+"itself comprises several line segments demarcated by waypoints (white dots "
+"on the profile, as shown above). The default dive depth is 15 m.  If the "
+"dive depth was 20 m then the user needs to drag the appropriate waypoints "
+"downwards to represent 20 m. To add a waypoint, double-click on any line "
+"segment. To move an additional waypoint, drag it.  To remove this waypoint, "
+"right-click on it and choose \"Remove this point\" from the context menu. "
+"The user needs to drag the waypoints to represent an accurate time duration "
+"for the dive. Below is a dive profile that represents a dive to 20 m for 30 "
+"min, followed by a 5 minute safety stop at 5 m."
+msgstr ""
+
+#. type: Target for macro image
+#: user-manual.txt:427
+#, no-wrap
+msgid "images/DiveProfile2_f20.jpg"
+msgstr ""
+
+#. type: Plain text
+#: user-manual.txt:439
+msgid ""
+"_Specifying the gas composition:_ The gas composition used is clearly "
+"indicated along the line segments of the dive profile. This defaults to the "
+"first gas mixture specified in the *Equipment* tab, which was air in the "
+"case of the profile illustrated above. The gas mixtures of segments of the "
+"dive profile can be edited. This is done by right-clicking on the particular "
+"waypoint and selecting the appropriate gas from the context menu. Changing "
+"the gas for a waypoint affects the gas shown in the segment _to the left_ of "
+"that waypoint. Note that only the gases defined in the *Equipment* tab "
+"appear in the context menu."
+msgstr ""
+
+#. type: Target for macro image
+#: user-manual.txt:440
+#, no-wrap
+msgid "images/DiveProfile3_f20.jpg"
+msgstr ""
+
+#. type: Plain text
+#: user-manual.txt:445
+msgid ""
+"Below is the profile of a dive to 25 m for 30 min and with a switch from air "
+"to EAN50 at the end of the duration at 20m. In this case the first cylinder "
+"in the *Equipment* tab contained air and the second cylinder contained EAN50."
+msgstr ""
+
+#. type: Target for macro image
+#: user-manual.txt:446
+#, no-wrap
+msgid "images/DiveProfile4_f20.jpg"
+msgstr ""
+
+#. type: Title ====
+#: user-manual.txt:448
+#, no-wrap
+msgid "Saving the hand-entered dive information"
+msgstr ""
+
+#. type: Plain text
+#: user-manual.txt:459
+msgid ""
+"The information entered in the *Dive Notes* tab, the *Equipment* tab as well "
+"as the *Dive Profile* can now be saved in the user's logbook by using the "
+"two buttons on the top right hand of the Dive Notes tab. If the _Save_ "
+"button is clicked, the dive data are saved in the current logbook. If the "
+"_Cancel_ button is clicked, the newly entered dive data are discarded. When "
+"exiting _Subsurface_, the user will be prompted once more to save the "
+"logbook with the new dive(s)."
+msgstr ""
+
+#. type: Title ===
+#: user-manual.txt:461
+#, no-wrap
+msgid "Importing new dive information from a Dive Computer"
+msgstr ""
+
+#. type: Title ====
+#: user-manual.txt:463
+#, no-wrap
+msgid "Connecting and importing data from a dive computer."
+msgstr ""
+
+#. type: Plain text
+#: user-manual.txt:474
+msgid ""
+"The use of dive computers allows the collection of a large amount of "
+"information about each dive, e.g. a detailed record of depth, duration, "
+"rates of ascent/descent and of gas partial pressures. _Subsurface_ can "
+"capture this information and present it as part of the dive information, "
+"using dive information from a wide range of dive computers. The latest list "
+"of supported dive computers can be found at: link:http://subsurface-divelog."
+"org/documentation/supported-dive-computers/[ Supported dive computers]."
+msgstr ""
+
+#. type: Named 'icon' AttributeList argument for style 'icon'
+#: user-manual.txt:475 user-manual.txt:2574
+#, no-wrap
+msgid "images/icons/warning2.png"
+msgstr ""
+
+#. type: Plain text
+#: user-manual.txt:486
+msgid ""
+"Several dive computers consume more power when they are in their PC-"
+"Communication mode. **This could drain the dive computer's battery**. We "
+"therefore recommend that the user checks if the dive computer is charged "
+"when connected to the USB port of a PC. For example, several Suunto and "
+"Mares dive computers do not recharge through the USB connection. Users "
+"should refer to the dive computer's manual if they are unsure whether the "
+"dive computer recharges its batteries while connected to the USB port."
+msgstr ""
+
+#. type: Plain text
+#: user-manual.txt:502
+msgid ""
+"To import dive information from a dive computer to a computer with "
+"_Subsurface_, it is necessary that the two pieces of equipment communicate "
+"with one another.  This involves setting up the communications port (or "
+"mount point) of the computer with _Subsurface_ that communicates with the "
+"dive computer. In order to set up this communication, one needs to find the "
+"appropriate information to instruct _Subsurface_ where and how to import the "
+"dive information.  xref:"
+"_appendix_a_operating_system_specific_information_for_importing_dive_information_from_a_dive_computer[Appendix "
+"A] provides the technical information to help the user achieving this for "
+"different operating systems and xref:"
+"_appendix_b_dive_computer_specific_information_for_importing_dive_information[Appendix "
+"B] has dive computer specific information."
+msgstr ""
+
+#. type: Plain text
+#: user-manual.txt:505
+msgid ""
+"After this, the dive computer can be hooked up to the user's PC, which can "
+"be achieved by following these steps:"
+msgstr ""
+
+#. type: Plain text
+#: user-manual.txt:507
+msgid ""
+"The interface cable should be connected to a free USB port (or the Infra-red"
+msgstr ""
+
+#. type: Plain text
+#: user-manual.txt:508
+msgid "or Bluetooth connection set up as described later in this manual)"
+msgstr ""
+
+#. type: Plain text
+#: user-manual.txt:510
+msgid "The dive computer should be placed into PC Communication mode."
+msgstr ""
+
+#. type: Plain text
+#: user-manual.txt:511
+msgid "(Users should refer to the manual of their specific dive computer)"
+msgstr ""
+
+#. type: Plain text
+#: user-manual.txt:515
+msgid ""
+"In _Subsurface_, from the Main Menu, the user must select _Import -> Import "
+"From Dive Computer_.  Dialogue *A* in the figure below appears:"
+msgstr ""
+
+#. type: Target for macro image
+#: user-manual.txt:517
+#, no-wrap
+msgid "images/ImportFromDC1_f20.jpg"
+msgstr ""
+
+#. type: Plain text
+#: user-manual.txt:527
+msgid ""
+"Dive computers tend to keep a certain number of dives in their memory, even "
+"though these dives have already been imported to _Subsurface_. For that "
+"reason _Subsurface_ only imports dives that have not been uploaded before. "
+"This makes the download process faster on most dive computers and also saves "
+"battery power of the dive computer (at least for those not charging while "
+"connected via USB).  If, for some reason, the user wishes to import ALL "
+"dives from the dive computer, even though some may already be in the "
+"logbook, then check the check box labelled _Force download of all dives_."
+msgstr ""
+
+#. type: Plain text
+#: user-manual.txt:534
+msgid ""
+"The dialogue has two drop-down lists, *Vendor* and *Dive Computer*. On the "
+"*vendor* drop-down list select the make of the computer, e.g.  Suunto, "
+"Oceanic, Uwatec, Mares. On the *Dive Computer* drop-down list, the model "
+"name of the dive computer must be selected, e.g. D4 (Suunto), Veo200 "
+"(Oceanic), or Puck (Mares)."
+msgstr ""
+
+#. type: Plain text
+#: user-manual.txt:545
+msgid ""
+"The *Device or Mount Point* drop-down list contains the USB or Bluetooth "
+"port name that _Subsurface_ needs in order to communicate with the dive "
+"computer.  The appropriate port name must be selected. Consult xref:"
+"_appendix_a_operating_system_specific_information_for_importing_dive_information_from_a_dive_computer[Appendix "
+"A] and xref:"
+"_appendix_b_dive_computer_specific_information_for_importing_dive_information[Appendix "
+"B] for technical details on how to find the appropriate port information for "
+"a particular dive computer and, in some cases, how to do the correct "
+"settings to the operating system of the computer on which _Subsurface_ is "
+"running."
+msgstr ""
+
+#. type: Plain text
+#: user-manual.txt:555
+msgid ""
+"If all the dives on the dive computer need to be downloaded, check the "
+"checkbox _Force download of all dives_. Normally, _Subsurface_ only "
+"downloads dives after the date-time of the last dive in the *Dive List* "
+"panel. If one or more of your dives in _Subsurface_ have been accidentally "
+"deleted or if there are older dives that still need to be downloaded from "
+"the dive computer, this checkbox needs to be activated. Some dive computers "
+"(e.g. Mares Puck) do not provide a contents list to _Subsurface_ before the "
+"download in order to select only new dives.  Consequently, for these dive "
+"computers, all dives are downloaded irrespective of the status of this check "
+"box."
+msgstr ""
+
+#. type: Plain text
+#: user-manual.txt:561
+msgid ""
+"If the checkbox _Always prefer downloaded dives_ has been checked and, "
+"during download, dives with identical date-times exist on the dive computer "
+"and on the _Subsurface_ *Dive List* panel, the record in the _Subsurface_ "
+"divelog will be overwritten by the record from the dive computer"
+msgstr ""
+
+#. type: Plain text
+#: user-manual.txt:565
+msgid ""
+"Do *not* check the checkboxes labelled _Save libdivecomputer logfile_ and "
+"_Save libdivecomputer dumpfile_. These are only used as diagnostic tools "
+"when problems with downloads are experienced (see below)."
+msgstr ""
+
+#. type: Plain text
+#: user-manual.txt:568
+msgid ""
+"The _OK_ button must then be clicked. Dialogue *B* in the figure above "
+"appears."
+msgstr ""
+
+#. type: Plain text
+#: user-manual.txt:583
+msgid ""
+"With communication established, one can see how the data are retrieved from "
+"the dive computer.  Depending on the make of the dive computer and/or number "
+"of recorded dives, this could take some time. The user should be patient. "
+"The _Download_ dialogue shows a progress bar at the bottom of the dialogue "
+"(for some dive computers the progress information could be inaccurate as we "
+"cannot determine how much downloadable data there is until all data have "
+"been downloaded). When the download of the dive information is complete, all "
+"the imported dives appear in the *Dive List*, sorted by date and time. "
+"Disconnect and switch off the dive computer to conserve its battery power.  "
+"If a particular dive is selected, the *Dive Profile* panel shows an "
+"informative graph of dive depth against time for that particular dive."
+msgstr ""
+
+#. type: Plain text
+#: user-manual.txt:588
+msgid ""
+"If there is a problem in communicating with the dive computer, an error "
+"message will be shown, similar to this text: \"Unable to open /dev/ttyUSB0 "
+"Mares (Puck Pro)\". Refer to the text in the box below."
+msgstr ""
+
+#. type: delimited block *
+#: user-manual.txt:592
+#, no-wrap
+msgid "*PROBLEMS WITH DATA DOWNLOAD FROM A DIVE COMPUTER?*\n"
+msgstr ""
+
+#. type: Named 'icon' AttributeList argument for style 'icon'
+#: user-manual.txt:592 user-manual.txt:1094 user-manual.txt:1161
+#: user-manual.txt:1330 user-manual.txt:1406
+#, no-wrap
+msgid "images/icons/important.png"
+msgstr ""
+
+#. type: delimited block *
+#: user-manual.txt:595
+msgid "Check the following:"
+msgstr ""
+
+#. type: delimited block *
+#: user-manual.txt:598
+msgid "Is the dive computer still in PC-communication or Upload mode?"
+msgstr ""
+
+#. type: delimited block *
+#: user-manual.txt:601
+msgid ""
+"Is the battery of the dive computer fully charged? If not then the battery "
+"must be charged or replaced."
+msgstr ""
+
+#. type: delimited block *
+#: user-manual.txt:605
+msgid ""
+"Is the connecting cable faulty? Does the cable work perfectly using other "
+"software? Has it worked before, or is this the first time the cable is being "
+"used? Are the contacts on the dive computer and the cable clean?"
+msgstr ""
+
+#. type: delimited block *
+#: user-manual.txt:610
+msgid ""
+"Consult xref:"
+"_appendix_a_operating_system_specific_information_for_importing_dive_information_from_a_dive_computer[Appendix "
+"A] and make sure that the correct Mount Point was specified (see above)."
+msgstr ""
+
+#. type: delimited block *
+#: user-manual.txt:614
+msgid ""
+"On Unix-like operating systems, does the user have write permission to the "
+"USB port? If not, consult xref:"
+"_appendix_a_operating_system_specific_information_for_importing_dive_information_from_a_dive_computer[Appendix "
+"A]"
+msgstr ""
+
+#. type: delimited block *
+#: user-manual.txt:622
+msgid ""
+"If the _Subsurface_ computer does not recognise the USB adaptor by showing "
+"an appropriate device name next to the Mount Point, then there is a "
+"possibility that the cable or USB adaptor is faulty. A faulty cable is the "
+"most common cause of communication failure between dive computer and "
+"_Subsurface_ computer. It is also possible that the _Subsurface_ computer "
+"cannot interpret the data. Perform a download for diagnostic purposes with "
+"the following two check boxes checked in the download dialogue discussed "
+"above:"
+msgstr ""
+
+#. type: delimited block *
+#: user-manual.txt:625
+#, no-wrap
+msgid ""
+"\tSave libdivecomputer logfile\n"
+"\tSave libdivecomputer dumpfile\n"
+msgstr ""
+
+#. type: delimited block *
+#: user-manual.txt:631
+#, no-wrap
+msgid ""
+"*Important*: These check boxes are only used when problems are encountered\n"
+"during the download process: under normal circumstances they should not be checked.\n"
+"When checking these boxes, the user is prompted to select a folder to\n"
+"save the information to. The default folder is the one in which the _Subsurface_\n"
+"dive log is kept.\n"
+msgstr ""
+
+#. type: delimited block *
+#: user-manual.txt:635
+#, no-wrap
+msgid ""
+"*Important:* _After downloading with the above checkboxes\n"
+"checked, no dives are added to the\n"
+"*Dive List* but two files are created in the folder selected above_:\n"
+msgstr ""
+
+#. type: delimited block *
+#: user-manual.txt:638
+#, no-wrap
+msgid ""
+"\tsubsurface.log\n"
+"\tsubsurface.bin\n"
+msgstr ""
+
+#. type: delimited block *
+#: user-manual.txt:644
+msgid ""
+"These files should be send to the _Subsurface_ mail list: "
+"_subsurface@subsurface-divelog.org_ with a request for the files to be "
+"analysed. Provide the dive computer make and model as well as contextual "
+"information about the dives recorded on the dive computer."
+msgstr ""
+
+#. type: Title ====
+#: user-manual.txt:647
+#, no-wrap
+msgid "Changing the name of a dive computer"
+msgstr ""
+
+#. type: Plain text
+#: user-manual.txt:663
+msgid ""
+"It may be necessary to distinguish between different dive computers used to "
+"upload dive logs to _Subsurface_. For instance if one's partner's dive "
+"computer is the same make and model as one's own and dive logs are uploaded "
+"from both dive computers to the same _Subsurface_ computer, then one would "
+"perhaps like to call one dc \"Alice's Suunto D4\" and the other one \"Bob's "
+"Suunto D4\". Alternatively, perhaps a technical diver dives with two or more "
+"dive computers of the same model, the logs of both (or all) being uploaded.  "
+"In this case it might be prudent to call one of them \"Suunto D4 (1)\" and "
+"another one \"Suunto D4 (2)\". This is easily done in _Subsurface_.  On the "
+"*Main Menu*, select _Log -> Edit device names_. A dialog opens, indicating "
+"the current Model, ID and Nickname of the dive computers used for upload. "
+"Edit the Nickname field for the appropriate dive computer. After saving the "
+"Nickname, the dive logs show the nickname for that particular device instead "
+"of the model name, allowing easy identification of devices."
+msgstr ""
+
+#. type: Title ====
+#: user-manual.txt:665
+#, no-wrap
+msgid "Updating the dive information imported from the dive computer."
+msgstr ""
+
+#. type: Plain text
+#: user-manual.txt:672
+msgid ""
+"The information from the dive computer is not complete and more details must "
+"be added in order to have a fuller record of the dives. To do this, the "
+"*Dive Notes* and the *Equipment* tabs on the top left hand of the "
+"_Subsurface_ window should be used."
+msgstr ""
+
+#. type: Plain text
+#: user-manual.txt:682
+msgid ""
+"The date and time of the dive, gas mixture and (often) water temperature is "
+"shown as obtained from the dive computer, but the user needs to add "
+"additional information by hand in order to have a more complete dive "
+"record.  If the contents of this tab is changed or edited in any way, the "
+"message in a blue box at the top of the panel indicates that the dive is "
+"being edited. If one clicks on the *Dive Notes* tab, the following fields "
+"are visible:"
+msgstr ""
+
+#. type: Target for macro image
+#: user-manual.txt:683
+#, no-wrap
+msgid "images/AddDive3_f20.jpg"
+msgstr ""
+
+#. type: Plain text
+#: user-manual.txt:691
+msgid ""
+"The *Time* field reflects the date and time of the dive. By clicking the "
+"date, a calendar is displayed from which one can choose the correct date. "
+"Press ESC to close the calendar.  The time values (hour and minutes) can "
+"also be edited directly by clicking on each of them in the text box and by "
+"overtyping the information displayed."
+msgstr ""
+
+#. type: Plain text
+#: user-manual.txt:702
+#, no-wrap
+msgid ""
+"*Air/water temperatures*: Air and water temperatures during the dive are shown\n"
+"in these fields to the right of the Start time. Many dive computers supply water\n"
+"temperature information and this field may therefore contain information obtained from the dive computer.\n"
+"If air temperature is not provided by the dive computer, the first temperature reading\n"
+"might be used for the air temperature. Generally this is close enough to the real air temperature as\n"
+"the change in the temperature sensor reading is quite slow to follow the changes in the environment.\n"
+"If editing is required, only a value is required, the units of temperature will be\n"
+"automatically supplied by\n"
+"_Subsurface_ (according to the _Preferences_, metric or imperial units will\n"
+"be used).\n"
+msgstr ""
+
+#. type: Plain text
+#: user-manual.txt:707
+#, no-wrap
+msgid ""
+"*Location*: In this field one should type in text that describes the site\n"
+"where the dive was performed, e.g. \"Tihany, Lake Balaton, Hungary\".\n"
+"Auto completion of location names will\n"
+"make this easier if one frequently dives at the same sites.\n"
+msgstr ""
+
+#. type: Plain text
+#: user-manual.txt:717
+msgid ""
+"The user can find the coordinates on the world map in the bottom right hand "
+"part of the Subsurface window. The map displays a green bar indicating "
+"\"Move the map and double-click to set the dive location\". Double-click at "
+"the appropriate place, the green bar disappears and the coordinates are "
+"stored."
+msgstr ""
+
+#. type: Plain text
+#: user-manual.txt:722
+msgid ""
+"The user can obtain the coordinates from the _Subsurface_ Companion app if "
+"an Android device with GPS was used and if the coordinates of the dive site "
+"were stored using that device.  xref:S_Companion[Click here for more "
+"information]"
+msgstr ""
+
+#. type: Plain text
+#: user-manual.txt:734
+msgid ""
+"Southern hemisphere latitudes are given with a *S*, e.g. S30°, or with a "
+"negative value, e.g. -30.22496. Similarly, western longitudes are given with "
+"a *W*, e.g. W07°, or with a negative value, e.g. -7.34323."
+msgstr ""
+
+#. type: Plain text
+#: user-manual.txt:745
+#, no-wrap
+msgid ""
+"*Divemaster*: The name of the dive master or dive guide for this dive should be\n"
+"entered in this field\n"
+"which offers auto completion based on the list of dive masters in\n"
+"the current logbook.\n"
+msgstr ""
+
+#. type: Plain text
+#: user-manual.txt:750
+#, no-wrap
+msgid ""
+"*Buddy*: In this field, one enters the name(s) of the buddy / buddies\n"
+"(separated with commas) who accompanied him/her on the\n"
+"dive. Auto completion based on the list of buddies in the current logbook is\n"
+"offered.\n"
+msgstr ""
+
+#. type: Plain text
+#: user-manual.txt:755
+#, no-wrap
+msgid ""
+"*Suit*: Here the type of diving suit used for the dive can be entered.\n"
+"Auto completion of the suit description is available.\n"
+"Some dry-suit users may choose to use this field to record what combination of\n"
+"suit and thermal protection undersuit was used.\n"
+msgstr ""
+
+#. type: Plain text
+#: user-manual.txt:771
+#, no-wrap
+msgid ""
+"*Tags*: Tags that describe the type of dive performed can be entered\n"
+"here (separated by commas). Examples of common tags are boat, drift, training,\n"
+"cave, etc.\n"
+"_Subsurface_ has many built-in tags. If the user starts typing a tag, the\n"
+"program\n"
+"will list the tags that correspond to the typing. For instance, if the user\n"
+"typed\n"
+"+cav+, then the tags *cave* and *cavern* are shown for the user to choose from.\n"
+msgstr ""
+
+#. type: Plain text
+#: user-manual.txt:773
+#, no-wrap
+msgid "*Notes*: Any additional information for the dive can be entered here.\n"
+msgstr ""
+
+#. type: Plain text
+#: user-manual.txt:786
+msgid ""
+"The Equipment tab allows one to enter information about the type of cylinder "
+"and gas used as well as the weights used for the dive. The message in a blue "
+"box at the top of the panel:"
+msgstr ""
+
+#. type: Plain text
+#: user-manual.txt:793
+msgid ""
+"indicates that the dive is being edited. This is a highly interactive part "
+"of _Subsurface_ and the information on cylinders and gases (entered here) "
+"determines the behaviour of the dive profile (top right-hand panel)."
+msgstr ""
+
+#. type: Target for macro image
+#: user-manual.txt:797
+#, no-wrap
+msgid "images/DC_gas-dialogue1_f20.jpg"
+msgstr ""
+
+#. type: Plain text
+#: user-manual.txt:805
+msgid ""
+"In most cases _Subsurface_ obtains the gas used from the dive computer and "
+"automatically inserts the gas composition(% oxygen) in the table. The + "
+"button at the top right allows the user to add more cylinders for this dive. "
+"The dark dustbin icon on the left allows the deletion of information for a "
+"cylinder.  Note that it is not possible to delete a cylinder if it is used "
+"during the dive. A cylinder might be implicitly used in the dive, even "
+"without a gas change event."
+msgstr ""
+
+#. type: Plain text
+#: user-manual.txt:810
+msgid ""
+"The user should start by selecting a cylinder type on the left-hand side of "
+"the table.  To select a cylinder, the *cylinder type* box should be clicked. "
+"This brings up a list button that can be used to display a dropdown list of "
+"cylinders:"
+msgstr ""
+
+#. type: Target for macro image
+#: user-manual.txt:811
+#, no-wrap
+msgid "images/DC_gas-dialogue2_f20.jpg"
+msgstr ""
+
+#. type: Plain text
+#: user-manual.txt:818
+msgid ""
+"The drop-down list can then be used to select the cylinder type that was "
+"used for this dive or the user may start typing in the box which shows the "
+"available options for the entered characters. The *Size* of the cylinder as "
+"well as its working pressure (*WorkPress*) will automatically be shown in "
+"the dialogue."
+msgstr ""
+
+#. type: Plain text
+#: user-manual.txt:822
+msgid ""
+"Next one must indicate the starting pressure and the ending pressure of the "
+"specified gas during the dive. The unit of pressure (metric/imperial)  "
+"corresponds to the settings chosen in the _Preferences_."
+msgstr ""
+
+#. type: Plain text
+#: user-manual.txt:833
+msgid ""
+"Finally, provide the gas mixture used. If air was used, the value of 21% can "
+"be entered or this field can be left blank. If nitrox or trimix were used, "
+"their percentages of oxygen and/or helium should be entered.  Any "
+"inappropriate fields should be left empty. After typing the information for "
+"the cylinder, either press _ENTER_ on the keyboard or click outside the cell "
+"that contains the cursor. Information for any additional cylinders can be "
+"added by using the + button at the top right hand. Following is an example "
+"of a complete description for a dive using two cylinders (air and EAN50):"
+msgstr ""
+
+#. type: Plain text
+#: user-manual.txt:841
+#, no-wrap
+msgid ""
+"*Weights*: Information about the weight system used can be entered\n"
+"using a dialogue very similar to that of the cylinder information. If one\n"
+"clicks\n"
+"the + button on the top right of the weights dialogue, the table looks like\n"
+"this:\n"
+msgstr ""
+
+#. type: Plain text
+#: user-manual.txt:846
+msgid ""
+"By clicking on the *Type* field, a drop-down list becomes accessible through "
+"a down-arrow:"
+msgstr ""
+
+#. type: Plain text
+#: user-manual.txt:862
+msgid ""
+"The drop-down list can then be used to select the type of weight system used "
+"during the dive or the user may start typing in the box which shows the "
+"available options for the entered characters.  In the *Weight* field, type "
+"in the amount of weight used during the dive. After specifying the weight "
+"system, the user can either press _ENTER_ on the keyboard or click outside "
+"the cell with the cursor.  It is possible to enter information for more than "
+"one weight system by adding an additional system using the + button on the "
+"top right hand. Weight systems can be deleted using the dustbin icon on the "
+"left hand. Here is an example of information for a dive with two types of "
+"weights: integrated as well as a weight belt:"
+msgstr ""
+
+#. type: Title ====
+#: user-manual.txt:865
+#, no-wrap
+msgid "Editing several selected dives simultaneously"
+msgstr ""
+
+#. type: Plain text
+#: user-manual.txt:880
+msgid ""
+"_METHOD 1_: After uploading dives from a dive computer, the dive profiles of "
+"the uploaded dives are shown in the *Dive profile* tab, as well as a few "
+"items of information in the *Dive Notes* tab (e.g. water temperature) and in "
+"the *Equipment* tab (e.g. gas pressures and gas composition). However the "
+"other fields remain empty.  It may be useful to simultaneously edit some of "
+"the fields in the *Dive Notes* and *Equipment* tabs.  For instance, it is "
+"possible that a diver performed several dives during a single day, using "
+"identical equipment while diving at the same dive site or with the same dive "
+"master and/or buddy or tags. Instead of completing the information for each "
+"of these dives separately, one can select all the dives for that day in the "
+"*Dive List* and insert the same information in the *Dive Notes* and "
+"*Equipment* fields that need identical information. This is achieved by "
+"editing the dive notes or the equipment for any one of the selected dives."
+msgstr ""
+
+#. type: Plain text
+#: user-manual.txt:890
+msgid ""
+"The simultaneous editing only works with fields that do not already contain "
+"information.  This means that, if some fields have been edited for a "
+"particular dive among the selected dives, these are not changed while "
+"editing the dives simultaneously. Technically, the rule for editing several "
+"dives simultaneously is: if the data field being edited contains _exactly "
+"the same information_ for all the dives that have been selected, the new, "
+"edited information is substituted for all the selected dives, otherwise only "
+"the edited dive is changed, even though several dives have been selected in "
+"the *Dive List*. This greatly speeds up the completion of the dive log after "
+"several similar dives."
+msgstr ""
+
+#. type: Plain text
+#: user-manual.txt:899
+msgid ""
+"_METHOD 2_:There is a different way of achieving the same goal. Select a "
+"dive with all the appropriate information typed into the *Dive Notes* and "
+"*Equipment* tabs. Then, from the main menu, select _Log -> Copy dive "
+"components_.  A box is presented with a selection of check boxes for most of "
+"the fields in the *Dive Notes* and *Equipment* tabs.  Select the fields to "
+"be copied from the currently selected dive, then select _OK_. Now, in the "
+"*Dive List*, select the dives into which this information is to be pasted. "
+"Then, from the main menu, select _Log -> Paste dive components_.  All the "
+"selected dives now contain the data initially selected in the original "
+"source dive log."
+msgstr ""
+
+#. type: Title ====
+#: user-manual.txt:900
+#, no-wrap
+msgid "Adding Bookmarks to a dive"
+msgstr ""
+
+#. type: Plain text
+#: user-manual.txt:905
+msgid ""
+"Many divers wish to annotate their dives with text that indicate particular "
+"events during the dive, e.g. \"Saw dolphins\", or \"Released surface buoy\". "
+"This is easily done:"
+msgstr ""
+
+#. type: Plain text
+#: user-manual.txt:909
+msgid ""
+"Right-click at the appropriate point on the dive profile.  This brings up "
+"the dive profile context menu. Select _Add bookmark_. A red flag is placed "
+"on the dive profile at the point that was initially selected (see *A* below)."
+msgstr ""
+
+#. type: Plain text
+#: user-manual.txt:911
+msgid ""
+"Right-click on the red flag. This brings up the context menu (see *B* "
+"below). Select _Edit name_."
+msgstr ""
+
+#. type: Plain text
+#: user-manual.txt:914
+msgid ""
+"A text box is shown. Type the explanatory text for the bookmark (see *C* "
+"below). Select _OK_.  This saves the text associated with the bookmark."
+msgstr ""
+
+#. type: Plain text
+#: user-manual.txt:917
+msgid ""
+"If one hovers using the mouse over the red bookmark, the appropriate text is "
+"shown at the bottom of the information box (see *D* below)."
+msgstr ""
+
+#. type: Target for macro image
+#: user-manual.txt:918
+#, no-wrap
+msgid "images/Bookmarks.jpg"
+msgstr ""
+
+#. type: Title ====
+#: user-manual.txt:921
+#, no-wrap
+msgid "Saving the updated dive information"
+msgstr ""
+
+#. type: Plain text
+#: user-manual.txt:933
+msgid ""
+"The information entered in the *Dive Notes* tab and the *Equipment* tab can "
+"be saved by using the two buttons on the top right hand of the *Dive Notes* "
+"tab. If the _Save_ button is clicked, the dive data are saved. If the "
+"_Cancel_ button is clicked, then the newly entered dive data are deleted, "
+"although the dive profile obtained from the dive computer will be retained. "
+"When the user exits _Subsurface_ there is a final prompt to confirm that the "
+"new data should be saved."
+msgstr ""
+
+#. type: Title ===
+#: user-manual.txt:934
+#, no-wrap
+msgid "Importing dive information from other digital data sources or other data formats"
+msgstr ""
+
+#. type: Plain text
+#: user-manual.txt:960
+msgid ""
+"If a user has been diving for some time, it is possible that several dives "
+"were logged using other dive log software. This information does not need "
+"retyping because these dive logs can probably be imported into _Subsurface_. "
+"_Subsurface_ will import dive logs from a range of other dive log software. "
+"While some software is supported natively, for others the user has to export "
+"the logbook(s) to an intermediate format so that they can then be imported "
+"by _Subsurface_.  Currently, _Subsurface_ supports importing CSV log files "
+"from several sources.  APD LogViewer, XP5, Sensus and Seabear files are "
+"preconfigured, but because the import is flexible, users can configure their "
+"own imports.  Manually kept log files (e.g. in spreadsheet) can also be "
+"imported by configuring the CSV import.  _Subsurface_ can also import UDDF "
+"and UDCF files used by some divelog software and some dive computers, like "
+"the Heinrichs & Weikamp DR5. Finally, for some divelog software like Mares "
+"Dive Organiser it is currently suggested to import the logbooks first into a "
+"webservice like _divelogs.de_ and then import them from there with "
+"_Subsurface_, as divelogs.de supports a few additional logbook formats that "
+"_Subsurface_ currently cannot parse."
+msgstr ""
+
+#. type: Plain text
+#: user-manual.txt:969
+msgid ""
+"If the format of other software is supported natively on Subsurface, it "
+"should be sufficient to select either _Import->Import log files_ or _File-"
+">Open log file_. _Subsurface_ supports the data formats of many dive "
+"computers, including Suunto and Shearwater. When importing dives, "
+"_Subsurface_ tries to detect multiple records for the same dive and merges "
+"the information as best as it can. If there are no time zone issues (or "
+"other reasons that would cause the beginning time of the dives to be "
+"significantly different) _Subsurface_ will not create duplicate entries."
+msgstr ""
+
+#. type: Title ====
+#: user-manual.txt:970
+#, no-wrap
+msgid "Using the universal import dialogue"
+msgstr ""
+
+#. type: Plain text
+#: user-manual.txt:976
+msgid ""
+"Importing dives from other software is performed through a universal "
+"interface that is activated by selecting _Import_ from the Main Menu, then "
+"clicking on _Import Log Files_. This brings up the dialogue *A* below."
+msgstr ""
+
+#. type: Target for macro image
+#: user-manual.txt:977
+#, no-wrap
+msgid "images/Import1_f20.jpg"
+msgstr ""
+
+#. type: Plain text
+#: user-manual.txt:982
+msgid ""
+"Towards the bottom right is a dropdown selector with a default label of "
+"_Dive Log Files_ which gives access to the different types of direct imports "
+"available, as in dialogue *B*, above. Currently these are:"
+msgstr ""
+
+#. type: Plain text
+#: user-manual.txt:984
+msgid ""
+"XML-formatted dive logs (DivingLog 5.0, MacDive and several other dive log "
+"systems)"
+msgstr ""
+
+#. type: Plain text
+#: user-manual.txt:985
+msgid "UDDF-formatted dive logs (e.g. Kenozoooid)"
+msgstr ""
+
+#. type: Plain text
+#: user-manual.txt:986
+msgid "UDCF-formatted dive logs"
+msgstr ""
+
+#. type: Plain text
+#: user-manual.txt:987
+msgid "Poseidon MkVI CCR logs"
+msgstr ""
+
+#. type: Plain text
+#: user-manual.txt:988
+msgid "JDiveLog"
+msgstr ""
+
+#. type: Plain text
+#: user-manual.txt:989
+msgid "Suunto Dive Manager (DM3 and DM4)"
+msgstr ""
+
+#. type: Plain text
+#: user-manual.txt:990
+msgid ""
+"CSV (text-based and spreadsheet-based) dive logs, including APD CCR logs"
+msgstr ""
+
+#. type: Plain text
+#: user-manual.txt:994
+msgid ""
+"Selecting the appropriate file in the file list of the dialogue opens the "
+"imported dive log in the _Subsurface_ *Dive List*. Some other formats, not "
+"accessible through the Import dialogue are also supported, as explained "
+"below."
+msgstr ""
+
+#. type: Title ====
+#: user-manual.txt:995
+#, no-wrap
+msgid "Importing dive logs from closed circuit rebreather (CCR) systems"
+msgstr ""
+
+#. type: Named 'icon' AttributeList argument for style 'icon'
+#: user-manual.txt:997
+#, no-wrap
+msgid "images/APD.jpg"
+msgstr ""
+
+#. type: Plain text
+#: user-manual.txt:1002
+msgid ""
+"Closed system rebreathers use advanced technology to recirculate gas that "
+"has been breathed while doing two things to maintain a breathable oxygen "
+"concentration:"
+msgstr ""
+
+#. type: Plain text
+#: user-manual.txt:1003
+msgid "remove carbon dioxide from the gas that has been exhaled"
+msgstr ""
+
+#. type: Plain text
+#: user-manual.txt:1012
+msgid ""
+"regulate the oxygen concentration to remain within safe diving limits.  "
+"Currently, within _Subsurface_, the Poseidon MkVI Discovery is the best "
+"supported CCR dive computer. The CCR interface of _Subsurface_ is currently "
+"experimental and under active development. In contrast to a conventional "
+"open circuit dive computer, a CCR system computer does not allow the "
+"download of a log containing multiple dives. Rather, each dive is stored "
+"independently. This means that _Subsurface_ cannot download a dive log "
+"directly from a CCR dive computer, but that it imports CCR dive logs in the "
+"same way that it imports dive log data from other databases."
+msgstr ""
+
+#. type: Title =====
+#: user-manual.txt:1013
+#, no-wrap
+msgid "Import a CCR dive"
+msgstr ""
+
+#. type: Plain text
+#: user-manual.txt:1025
+msgid ""
+"See the section dealing with xref:S_ImportingAlienDiveLogs[Importing dive "
+"information from other digital sources]. From the main menu of _Subsurface_, "
+"select _Import->Import log files_ to bring up the xref:"
+"Unified_import[universal import dialogue]. As explained in the previous "
+"section, the bottom right hand of the import dialogue contains a dropdown "
+"list of appropriate devices that currently includes an option for MkVI "
+"files. Having selected the appropriate CCR format and the directory where "
+"the original dive logs have been stored from the CCR dive computer, one can "
+"select a particular dive log file (in the case of the MkVI it is a file with "
+"a .txt extension). After selecting the appropriate dive log, activate the "
+"_Open_ button at the bottom right hand of the universal import dialogue."
+msgstr ""
+
+#. type: Title =====
+#: user-manual.txt:1026
+#, no-wrap
+msgid "Displayed information for a  dive"
+msgstr ""
+
+#. type: Plain text
+#: user-manual.txt:1037
+msgid ""
+"_Partial pressures of gases_: The graph of oxygen partial pressure shows the "
+"information from the oxygen sensors of the CCR equipment. In the case of the "
+"Poseidon MKVI, the mean value of the two oxygen sensors are shown. In the "
+"case of the APD equipment, the mean of the three oxygen sensors are shown. "
+"If one sensor shows a very different oxygen PO2 reading compared to the "
+"others, the divergent sensor is ignored. For CCR dives the graph for oxygen "
+"partial pressure should be fairly flat, reflecting the setpoint settings "
+"during the dive.  Partial pressures for nitrogen (and helium, if applicable) "
+"are shown in the usual way as for other dives."
+msgstr ""
+
+#. type: Plain text
+#: user-manual.txt:1042
+msgid ""
+"_Cylinder pressures_: CCR dive computers like the Poseidon MkVI record the "
+"pressures of the oxygen and diluent cylinders. The pressure of the oxygen "
+"cylinder is shown on the dive profile. In addition, start and end pressures "
+"for both oxygen and diluent cylinders are shown in the _Equipment Tab_."
+msgstr ""
+
+#. type: Plain text
+#: user-manual.txt:1046
+msgid ""
+"_Equipment-specific information_: Equipment-specific information gathered by "
+"_Subsurface_ is shown in the _Extra data_ tab. This may include setup "
+"information or metadata about the dive."
+msgstr ""
+
+#. type: Plain text
+#: user-manual.txt:1048
+msgid ""
+"More equipment-specific information for downloading CCR dive logs can be "
+"found in xref:S_PoseidonMkVI[Appendix B]."
+msgstr ""
+
+#. type: Title ====
+#: user-manual.txt:1049
+#, no-wrap
+msgid "Importing from Mares Dive Organiser V2.1"
+msgstr ""
+
+#. type: Plain text
+#: user-manual.txt:1056
+msgid ""
+"Since Mares utilise proprietary Windows software not compatible with multi-"
+"platform applications, these dive logs cannot be directly imported into "
+"_Subsurface_. Mares dive logs need to be imported using a three-step "
+"process, using _www.divelogs.de_ as a mechanism to extract the dive log "
+"information."
+msgstr ""
+
+#. type: Plain text
+#: user-manual.txt:1061
+#, no-wrap
+msgid ""
+"The dive log data from Mares Dive Organiser need to be exported to the user's\n"
+"desktop, using\n"
+" a _.sdf_ file name extension. Refer to xref:Mares_Export[Appendix C] for more\n"
+"information.\n"
+msgstr ""
+
+#. type: Plain text
+#: user-manual.txt:1067
+#, no-wrap
+msgid ""
+"Data should then be imported into _www.divelogs.de_. One needs to create a user\n"
+"account in\n"
+"_www.divelogs.de_, log into that web site, then\n"
+"select _Import Logbook -> Dive Organiser_ from the menu on the left hand side.\n"
+"The instructions must be carefully followed to transfer the dive information\n"
+"(in _.sdf_ format) from the Dive Organiser database to _www.divelogs.de_.\n"
+msgstr ""
+
+#. type: Plain text
+#: user-manual.txt:1069
+#, no-wrap
+msgid ""
+"Finally,  import the dives\n"
+"from _divelogs.de_ to _Subsurface_, using the instructions below.\n"
+msgstr ""
+
+#. type: Title ====
+#: user-manual.txt:1072
+#, no-wrap
+msgid "Importing dives from *divelogs.de*"
+msgstr ""
+
+#. type: Plain text
+#: user-manual.txt:1085
+msgid ""
+"The import of dive information from _divelogs.de_ is simple, using a single "
+"dialogue box. The _Import->Import form Divelogs.de_ option should be "
+"selected from the Main Menu. This brings up a dialogue box (see figure on "
+"left [*A*] below). Enter a user-ID and password for _divelogs.de_ into the "
+"appropriate fields and then select the _Download_ button. Download from "
+"_divelogs.de_ starts immediately, displaying a progress bar in the dialogue "
+"box. At the end of the download, the success status is indicated (see figure "
+"on the right [*B*], below). The _Apply_ button should then be selected, "
+"after which the imported dives appear in the _Subsurface_ *Dive List* panel."
+msgstr ""
+
+#. type: Target for macro image
+#: user-manual.txt:1086
+#, no-wrap
+msgid "images/Divelogs1.jpg"
+msgstr ""
+
+#. type: Title ====
+#: user-manual.txt:1089
+#, no-wrap
+msgid "Importing data in CSV format"
+msgstr ""
+
+#. type: Plain text
+#: user-manual.txt:1093
+msgid ""
+"A comma-separated file (.csv) can be used to import dive information either "
+"as dive profiles (as in the case of the APD Inspiration and Evolution closed "
+"circuit rebreathers) or as dive metadata (in case the user keeps dive data "
+"in a spreadsheet). For an introduction to CSV-formatted files see xref:"
+"S_CSV_Intro[A Diver's Introduction To CSV Files]."
+msgstr ""
+
+#. type: Plain text
+#: user-manual.txt:1103
+msgid ""
+"The CSV import has a couple of caveats. You should avoid some special "
+"characters like ampersand (&), less than (<), greater than (>) and double "
+"quotes (\"), the latter if quoting text cells. The file should use UTF-8 "
+"character set, if having non-ASCII characters. Also the size of the CSV file "
+"might cause problems. Importing 100 dives at a time (without dive profile) "
+"has worked previously, but larger files might exceed limits of the parser "
+"used. When having problems with CSV imports, try first with a smaller sample "
+"to make sure everything works."
+msgstr ""
+
+#. type: Title =====
+#: user-manual.txt:1105
+#, no-wrap
+msgid "Importing dives in CSV format from dive computers or other dive log software"
+msgstr ""
+
+#. type: Plain text
+#: user-manual.txt:1112
+msgid ""
+"CSV files are normally organised into a single line that provides the "
+"headers (or _field names_) of the data columns, followed by the data, one "
+"record per line. CSV files can be opened with a normal text editor.  For "
+"information of how to export a spreadsheet in CSV format see xref:"
+"S_Appendix_D[APPENDIX D: Exporting a spreadsheet to CSV format]."
+msgstr ""
+
+#. type: Plain text
+#: user-manual.txt:1114
+msgid "Before being able to import the data to _Subsurface_ one needs to know:"
+msgstr ""
+
+#. type: Plain text
+#: user-manual.txt:1123
+msgid ""
+"Which character separates the different columns within a single line of "
+"data? This field separator should be either a comma (,) or a TAB character.  "
+"This can be determined by opening the file with a text editor. If it is "
+"comma-delimited, then the comma characters between the values are clearly "
+"visible. If no commas are evident and the numbers are aligned in columns, "
+"the file is probably TAB-delimited (i.e. it uses a TAB as a field separator, "
+"as in the above example)."
+msgstr ""
+
+#. type: Plain text
+#: user-manual.txt:1127
+msgid ""
+"Which data columns need to be imported into _Subsurface_? The Dive Time and "
+"Depth columns are always required. Open the file using a text editor and "
+"note the titles of the columns to be imported and their column positions."
+msgstr ""
+
+#. type: Plain text
+#: user-manual.txt:1129
+msgid ""
+"Is the numeric information (e.g. dive depth) in metric or in imperial unis?"
+msgstr ""
+
+#. type: Plain text
+#: user-manual.txt:1136
+msgid ""
+"Armed with this information, importing the data into _Subsurface_ is "
+"straightforward. Select _Import->Import Log Files_ from the main menu. In "
+"the resulting file selection menu, select _CSV files_, after which a common "
+"configuration dialog appears for all the files with a CSV extension:"
+msgstr ""
+
+#. type: Target for macro image
+#: user-manual.txt:1137
+#, no-wrap
+msgid "images/Import_CSV1.jpg"
+msgstr ""
+
+#. type: Plain text
+#: user-manual.txt:1143
+msgid ""
+"There are pre-configured definitions for some dive computers, e.g. the APD "
+"rebreathers. If the user's dive computer is on this list, it should be "
+"selected using the dropdown box labeled _Pre-configured imports_."
+msgstr ""
+
+#. type: Plain text
+#: user-manual.txt:1150
+msgid ""
+"If the dive computer is not on the pre-configured list, the user must select "
+"the _Field Separator_ (TAB or comma) for the particular CSV file, using the "
+"appropriate dropdown list. For each data column used for import, the user "
+"must check the appropriate check box and indicate in which column these data "
+"are found."
+msgstr ""
+
+#. type: Plain text
+#: user-manual.txt:1153
+msgid ""
+"Finally _OK_ should be clicked and the dive(s) are imported and listed in "
+"the *Dive List* tab of _Subsurface_."
+msgstr ""
+
+#. type: Title ====
+#: user-manual.txt:1156
+#, no-wrap
+msgid "Importing dives from a manually kept CSV file or a spreadsheet"
+msgstr ""
+
+#. type: delimited block *
+#: user-manual.txt:1161
+#, no-wrap
+msgid "*A Diver's Introduction To CSV Files*\n"
+msgstr ""
+
+#. type: delimited block *
+#: user-manual.txt:1175
+msgid ""
+"CSV is an abbreviation for a data file format: _Comma-Separated Variables_. "
+"It is a file format allowing someone to view or edit the information using a "
+"text editor such as Notebook (Windows), gedit (Linux) or TextWrangler (OS/"
+"X). The two main advantages of the CSV format is that the data are easily "
+"editable as text without any proprietary software and ensuring all "
+"information is human-readable, not being obscured by the any custom or "
+"proprietary attributes that proprietary software insert into files.  Because "
+"of its simplicity the CSV format is used as an interchange format between "
+"many software packages, e.g. between spreadsheet, statistical, graphics, "
+"database and diving software. Within _Subsurface_, CSV files can also be "
+"used to import information from other sources such as spreadsheet-based dive "
+"logs and even from some dive computers."
+msgstr ""
+
+#. type: delimited block *
+#: user-manual.txt:1184
+msgid ""
+"CSV files can be created or edited with a normal text editor. The most "
+"important attribute of a CSV file is the _field separator_, the character "
+"used to separate fields within a single line. The field separator is "
+"frequently a comma, a colon, a SPACE character or a TAB character. When "
+"exporting data from spreadsheet software, the field separator needs to be "
+"specified in order to create the CSV file. CSV files are normally organised "
+"into a single line that provides the headers (or _field names_) of the data "
+"columns, followed by the data, one record per line. Note that each field "
+"name may comprise more than one word separated by spaces; for instance _Dive "
+"site_, below. Here is an example of dive information for four dives using a "
+"comma as a field separator:"
+msgstr ""
+
+#. type: delimited block *
+#: user-manual.txt:1190
+#, no-wrap
+msgid ""
+"\tDive site,Dive date,Time,Dive_duration, Dive_depth,Dive buddy\n"
+"\tIllovo Beach,2012-11-23,10:45,46:15,18.4,John Smith\n"
+"\tKey Largo,2012-11-24,09:12,34:15,20.4,Jason McDonald\n"
+"\tWismar Baltic,2012-12-01,10:13,35:27,15.4,Dieter Albrecht\n"
+"\tPulau Weh,2012-12-20,09:46,55:56,38.6,Karaeng Bontonompo\n"
+msgstr ""
+
+#. type: delimited block *
+#: user-manual.txt:1192
+msgid ""
+"In this format the data are not easily read by a human. Here is the same "
+"information in TAB-delimited format:"
+msgstr ""
+
+#. type: delimited block *
+#: user-manual.txt:1198
+#, no-wrap
+msgid ""
+"\tDive site\tDive date\tTime\tDive_duration\tDive_depth\tDive buddy\n"
+"\tIllovo Beach\t2012-11-23\t10:45\t46:15\t18.4\tJohn Smith\n"
+"\tKey Largo\t2012-11-24\t09:12\t34:15\t20.4\tJason McDonald\n"
+"\tWismar Baltic\t2012-12-01\t10:13\t35:27\t15.4\tDieter Albrecht\n"
+"\tPulau Weh\t2012-12-20\t09:46\t55:56\t38.6\tKaraeng Bontonompo\n"
+msgstr ""
+
+#. type: delimited block *
+#: user-manual.txt:1206
+msgid ""
+"It is clear why many people prefer the TAB-delimited format to the comma-"
+"delimited format. The disadvantage is that one cannot see the TAB "
+"characters. For instance, the space between _Dive_ and _date_ in the top "
+"line may be a SPACE character or a TAB character (in this case it is a SPACE "
+"character: the tabs are before and after _Dive date_). If the field names in "
+"the first line are long, the alignment with data in the other lines cannot "
+"be maintained. Here is a highly simplified and shortened TAB-delimited "
+"example of a CSV dive log from an APD closed-circuit rebreather (CCR) dive "
+"computer:"
+msgstr ""
+
+#. type: delimited block *
+#: user-manual.txt:1217
+#, no-wrap
+msgid ""
+"\tDive Time (s)\tDepth (m)\tpO₂ - Setpoint (Bar) \tpO₂ - C1 Cell 1 (Bar)\tAmbient temp. (Celsius)\n"
+"\t0       0.0     0.70    0.81    13.1\n"
+"\t0       1.2     0.70    0.71    13.1\n"
+"\t0       0.0     0.70    0.71    13.1\n"
+"\t0       1.2     0.70    0.71    13.2\n"
+"\t0       1.2     0.70    0.71    13.1\n"
+"\t10      1.6     0.70    0.72    12.7\n"
+"\t20      1.6     0.70    0.71    12.6\n"
+"\t30      1.7     0.70    0.71    12.6\n"
+"\t40      1.8     0.70    0.68    12.5\n"
+msgstr ""
+
+#. type: delimited block *
+#: user-manual.txt:1219
+msgid ""
+"CSV files can therefore be used in many contexts for importing data into a "
+"_Subsurface_ dive log."
+msgstr ""
+
+#. type: delimited block *
+#: user-manual.txt:1222
+msgid ""
+"An important aspect of the CSV format required by _Subsurface_ is the "
+"_Column Mapping_. In the example from different dive sites above, each line "
+"of data is organised as follows:"
+msgstr ""
+
+#. type: delimited block *
+#: user-manual.txt:1229
+#, no-wrap
+msgid ""
+"\tColumn 1:\tDive site (location)\n"
+"\tColumn 2:\tDive date\n"
+"\tColumn 3:\tDive time\n"
+"\tColumn 4:\tDive duration\n"
+"\tColumn 5:\tMaximum dive depth (m)\n"
+"\tColumn 6:\tName of dive buddy\n"
+msgstr ""
+
+#. type: delimited block *
+#: user-manual.txt:1232
+msgid ""
+"_Subsurface_ requires the column number of each of these data items. For "
+"these data the column specification may look like this:"
+msgstr ""
+
+#. type: Target for macro image
+#: user-manual.txt:1233
+#, no-wrap
+msgid "images/CSV_column_definition.jpg"
+msgstr ""
+
+#. type: delimited block *
+#: user-manual.txt:1237
+msgid ""
+"Knowledge of a few basic things about he content of the CSV file allows a "
+"smooth import of the dives into _Subsurface_."
+msgstr ""
+
+#. type: Plain text
+#: user-manual.txt:1247
+msgid ""
+"If one keeps dive logs in a spreadsheet, there is an option to import those "
+"dives, exported as a CSV file. See xref:S_Appendix_D[APPENDIX D: Exporting a "
+"spreadsheet to CSV format] for information of how to export a spreadsheet in "
+"CSV format.  When importing manually kept log files into _Subsurface_, the "
+"information needed is quite different from that accessible using a dive "
+"computer, as we are importing only summary data, not depth profile samples."
+msgstr ""
+
+#. type: Plain text
+#: user-manual.txt:1250
+msgid ""
+"When importing dives in CSV format (see above), one needs to know the "
+"internal format of the CSV data to import."
+msgstr ""
+
+#. type: Plain text
+#: user-manual.txt:1257
+msgid ""
+"Which character separates the different columns within a single line of "
+"data? A recommended field separator for the export is TAB, as commas might "
+"be part of the decimal data values themselves. Therefore the use of an "
+"appropriate field separator is very important. When exporting data from a "
+"spreadsheet it is likely to request the user to supply an appropriate field "
+"separator character."
+msgstr ""
+
+#. type: Plain text
+#: user-manual.txt:1263
+msgid ""
+"Which columns need to be imported into _Subsurface_? Currently there are not "
+"any mandatory input fields, but some, e.g. dive duration are crucial for the "
+"log file to make any sense. Possible options can be seen in the image below "
+"and one should include as many as possible of the fields available in the "
+"original log file."
+msgstr ""
+
+#. type: Plain text
+#: user-manual.txt:1269
+msgid ""
+"Units used for depth, weight and temperature. We consider depth to be either "
+"feet or meters, weight kilograms or pounds and temperature either Celsius or "
+"Fahrenheit. However, the users can select _Metric_ or _Imperial_ in the "
+"*Preferences* tab of _Subsurface_. No mixture of unit systems is allowed for "
+"the different fields."
+msgstr ""
+
+#. type: Plain text
+#: user-manual.txt:1273
+msgid ""
+"Importing manually kept CSV log files is quite straight forward, but there "
+"might be many fields and counting the field numbers is error prone. "
+"Therefore validation of the data to be imported is critical."
+msgstr ""
+
+#. type: Plain text
+#: user-manual.txt:1278
+msgid ""
+"To import the dives, select _Import->Import Log Files_ from the menu bar. If "
+"the CSV option in the dropdown list is selected and the file list includes "
+"file names ending with .CSV, one can select the _Manual dives_ tab that will "
+"bring up the following configuration dialog:"
+msgstr ""
+
+#. type: Target for macro image
+#: user-manual.txt:1279
+#, no-wrap
+msgid "images/Import_CSV2.jpg"
+msgstr ""
+
+#. type: Plain text
+#: user-manual.txt:1288
+msgid ""
+"Check the check boxes corresponding to the data in the original import "
+"file.  For each of the checked data items, a corresponding column number "
+"needs to be entered. For instance in the image above, the name of the dive "
+"site (i.e. location)  is located as the 11th item (or column) on each line "
+"of the CSV import file.  The input fields can be configured as appropriate, "
+"and when everything is done the _OK_ button should be selected to perform "
+"the import. New dives should appear in the *Dive List* area of _Subsurface_."
+msgstr ""
+
+#. type: Title ===
+#: user-manual.txt:1291
+#, no-wrap
+msgid "Importing GPS coordinates with the _Subsurface Companion App_ for mobile phones"
+msgstr ""
+
+#. type: Plain text
+#: user-manual.txt:1299
+msgid ""
+"Using the *Subsurface Companion App* on an Android device with a GPS, the "
+"coordinates for the diving location can be automatically passed to the "
+"_Subsurface_ dive log. The Companion App stores the dive locations on a "
+"dedicated Internet-based file server. _Subsurface_, in turn, can collect the "
+"localities from the file server."
+msgstr ""
+
+#. type: Plain text
+#: user-manual.txt:1301
+msgid "To do this:"
+msgstr ""
+
+#. type: Title ====
+#: user-manual.txt:1302
+#, no-wrap
+msgid "Create a Companion App account"
+msgstr ""
+
+#. type: Plain text
+#: user-manual.txt:1307
+msgid ""
+"Register on the http://api.hohndel.org/login/[_Subsurface companion web "
+"page_].  A confirmation email with instructions and a personal *DIVERID* "
+"will be sent, a long number that gives access to the file server and "
+"Companion App capabilities."
+msgstr ""
+
+#. type: Plain text
+#: user-manual.txt:1312
+msgid ""
+"Download the app from https://play.google.com/store/apps/details?id=org."
+"subsurface[Google Play Store] or from http://f-droid.org/repository/browse/?"
+"fdfilter=subsurface&fdid=org.subsurface[F-Droid]."
+msgstr ""
+
+#. type: Title ====
+#: user-manual.txt:1313
+#, no-wrap
+msgid "Using the Subsurface companion app on a smartphone"
+msgstr ""
+
+#. type: Plain text
+#: user-manual.txt:1316
+msgid "On first use the app has three options:"
+msgstr ""
+
+#. type: Plain text
+#: user-manual.txt:1322
+msgid ""
+"_Create a new account._ Equivalent to registering in _Subsurface_ companion "
+"page using an Internet browser. One can request a *DIVERID* using this "
+"option, but this is supplied via email and followed up by interaction with "
+"the http://api.hohndel.org/login/[_Subsurface companion web page_] in order "
+"to activate the account."
+msgstr ""
+
+#. type: Plain text
+#: user-manual.txt:1325
+msgid ""
+"_Retrieve an account._ If users forgot their *DIVERID* they will receive an "
+"email to recover the number."
+msgstr ""
+
+#. type: Plain text
+#: user-manual.txt:1329
+msgid ""
+"_Use an existing account._ Users are prompted for their *DIVERID*. The app "
+"saves this *DIVERID* and does not ask for it again unless one uses the "
+"_Disconnect_ menu option (see below)."
+msgstr ""
+
+#. type: Plain text
+#: user-manual.txt:1337
+msgid ""
+"In the _Subsurface_ main program, the *DIVERID* should also be entered on "
+"the Default Preferences panel, obtained by selecting _File->Preferences-"
+">Defaults_ from the main menu in _Subsurface_ itself.  This facilitates "
+"synchronisation between _Subsurface_ and the Companion App."
+msgstr ""
+
+#. type: Title =====
+#: user-manual.txt:1338
+#, no-wrap
+msgid "Creating new dive locations"
+msgstr ""
+
+#. type: Plain text
+#: user-manual.txt:1343
+msgid ""
+"Now one is ready to get a dive position and send it to the server. The "
+"Android display will look like the left hand image (*A*) below, but without "
+"any dives."
+msgstr ""
+
+#. type: Plain text
+#: user-manual.txt:1346
+msgid ""
+"Touch the \"+\" icon on the top right to add a new dive site, a menu will be "
+"showed with 3 options:"
+msgstr ""
+
+#. type: Plain text
+#: user-manual.txt:1349
+msgid ""
+"Current: A prompt for a place name (or a request to activate the GPS if it "
+"is turned off) will be displayed, after which the current location is saved."
+msgstr ""
+
+#. type: Plain text
+#: user-manual.txt:1358
+msgid ""
+"Use Map: This option allows the user to fix a position by searching a world "
+"map. A world map is shown (see *B* below) on which one should indicate the "
+"desired position with a _long press_ on the touch sensitive screen (if the "
+"marked location is erroneous, simply indicate a new location)  and select "
+"the check symbol in the upper right. A dialog is shown allowing to enter the "
+"name of the dive location and the date-time of the dive (see *C* below). In "
+"order to import this dive location in _Subsurface_ it's advisable to set the "
+"time to agree with the time of that dive on the dive computer."
+msgstr ""
+
+#. type: Target for macro image
+#: user-manual.txt:1359
+#, no-wrap
+msgid "images/Companion_5.jpg"
+msgstr ""
+
+#. type: Plain text
+#: user-manual.txt:1367
+msgid ""
+"Import local GPX file: The android device searches for .gpx files and "
+"located archives will be shown. The selected .gpx file is opened and the "
+"stored locations shown. Now one needs to select the appropriate locations, "
+"then select the tab in the upper right, after which the locations will be "
+"sent to the web service and added to the list on the Android device."
+msgstr ""
+
+#. type: Title =====
+#: user-manual.txt:1368
+#, no-wrap
+msgid "Dive lists of dive locations"
+msgstr ""
+
+#. type: Plain text
+#: user-manual.txt:1376
+msgid ""
+"The main screen shows a list of dive locations, each with a name, date and "
+"time (see *A* below). Some locations may have an arrow-up icon over the "
+"selection box to the left indicating that they require upload to the server. "
+"One can select individual dive locations from the list. A selected location "
+"has a check mark in the selection box on the left. Group operations (such as "
+"_Delete_ or _Send_)  are performed on several locations that are selected."
+msgstr ""
+
+#. type: Plain text
+#: user-manual.txt:1384
+msgid ""
+"Dive locations in this list can be viewed in two ways: a list of locations "
+"or a map indicating the dive locations. The display mode (List or Map) is "
+"changed by selecting _Dives_ at the top left of the screen (see *A* below) "
+"and then selecting the display mode. The display mode can be changed either "
+"from the list of locations or from the map (see *B* below). If one selects a "
+"location (on the list or on the map), an editing panel opens (see *C* below) "
+"where the dive description or other details may be changed."
+msgstr ""
+
+#. type: Target for macro image
+#: user-manual.txt:1385
+#, no-wrap
+msgid "images/Companion_4.jpg"
+msgstr ""
+
+#. type: Plain text
+#: user-manual.txt:1391
+msgid ""
+"When one clicks on a dive (*not* selecting the check box), the name given to "
+"it, date/time and GPS coordinates will be shown, with two options at the top "
+"of the screen:"
+msgstr ""
+
+#. type: Plain text
+#: user-manual.txt:1393
+msgid ""
+"Edit (pencil): Change the text name or other characteristics of the dive "
+"location."
+msgstr ""
+
+#. type: Plain text
+#: user-manual.txt:1395
+msgid "Maps: Display a map showing the dive location."
+msgstr ""
+
+#. type: Plain text
+#: user-manual.txt:1398
+msgid ""
+"After editing and saving a dive location (see *C* above), one needs to "
+"upload it to the web service, as explained below."
+msgstr ""
+
+#. type: Title =====
+#: user-manual.txt:1399
+#, no-wrap
+msgid "Uploading dive locations"
+msgstr ""
+
+#. type: Plain text
+#: user-manual.txt:1405
+msgid ""
+"There are several ways to send locations to the server.  The easiest is by "
+"simply selecting the locations (See *A* below) and then touching the right "
+"arrow at the top right of the screen."
+msgstr ""
+
+#. type: Plain text
+#: user-manual.txt:1410
+msgid ""
+"Users must be careful, as the trash icon on the right means exactly what it "
+"should; it deletes the selected dive location(s)."
+msgstr ""
+
+#. type: Target for macro image
+#: user-manual.txt:1411
+#, no-wrap
+msgid "images/Companion_1.jpg"
+msgstr ""
+
+#. type: Plain text
+#: user-manual.txt:1416
+msgid ""
+"After a dive trip using the Companion App, all dive locations are ready to "
+"be downloaded to a _Subsurface_ dive log (see below)."
+msgstr ""
+
+#. type: Title =====
+#: user-manual.txt:1418
+#, no-wrap
+msgid "Settings on the Companion app"
+msgstr ""
+
+#. type: Plain text
+#: user-manual.txt:1421
+msgid ""
+"Selecting the _Settings_ menu option results in the right hand image above "
+"(*B*)."
+msgstr ""
+
+#. type: Title =====
+#: user-manual.txt:1422
+#, no-wrap
+msgid "Server and account"
+msgstr ""
+
+#. type: Plain text
+#: user-manual.txt:1425
+msgid "_Web-service URL._ This is predefined (http://api.hohndel.org/)"
+msgstr ""
+
+#. type: Plain text
+#: user-manual.txt:1429
+msgid ""
+"_User ID._ The DIVERID obtained by registering as described above. The "
+"easiest way to obtain it is simply to copy and paste from the confirmation "
+"email but, of course, users can also type this information."
+msgstr ""
+
+#. type: Title =====
+#: user-manual.txt:1430
+#, no-wrap
+msgid "Synchronisation"
+msgstr ""
+
+#. type: Plain text
+#: user-manual.txt:1434
+msgid ""
+"_Synchronize on startup._ If selected, dive locations in the Android device "
+"and those on the web service synchronise each time the app is started."
+msgstr ""
+
+#. type: Plain text
+#: user-manual.txt:1437
+msgid ""
+"_Upload new dives._ If selected, each time the user adds a dive location it "
+"is automatically sent to the server."
+msgstr ""
+
+#. type: Title =====
+#: user-manual.txt:1438
+#, no-wrap
+msgid "Background service"
+msgstr ""
+
+#. type: Plain text
+#: user-manual.txt:1441
+msgid ""
+"Instead of entering a unique dive location, users can leave the service "
+"running in the background of their Android device, allowing the continuous "
+"collection of GPS locations."
+msgstr ""
+
+#. type: Plain text
+#: user-manual.txt:1444
+msgid "The settings below define the behaviour of the service:"
+msgstr ""
+
+#. type: Plain text
+#: user-manual.txt:1447
+msgid ""
+"_Min duration._ In minutes. The app will try to get a location every X "
+"minutes until stopped by the user."
+msgstr ""
+
+#. type: Plain text
+#: user-manual.txt:1449
+msgid "_Min distance._ In meters. Minimum distance between two locations."
+msgstr ""
+
+#. type: Plain text
+#: user-manual.txt:1451
+msgid "_Name template._ The name the app will use when saving the locations."
+msgstr ""
+
+#. type: Named 'icon' AttributeList argument for style 'icon'
+#: user-manual.txt:1452 user-manual.txt:1528 user-manual.txt:1703
+#, no-wrap
+msgid "images/icons/info.jpg"
+msgstr ""
+
+#. type: Plain text
+#: user-manual.txt:1462
+msgid ""
+"_How does the background service work?_ Assuming the user sets 5 minutes and "
+"50 meters in the settings above, the app will start by recording a location "
+"at the current location, followed by another one at every 5 minutes *or* "
+"every time one moves 50m from previous location.  If subsequent locations "
+"are within a radius of 50 meters from the previous one, a new location is "
+"not saved. If the user is not moving, only one location is saved, but if the "
+"user is moving, a trace of the route is obtained by saving a location every "
+"50 meters."
+msgstr ""
+
+#. type: Title =====
+#: user-manual.txt:1463
+#, no-wrap
+msgid "Other"
+msgstr ""
+
+#. type: Plain text
+#: user-manual.txt:1467
+msgid ""
+"_Mailing List._ The mail box for _Subsurface_. Users can send an email to "
+"the Subsurface mailing list."
+msgstr ""
+
+#. type: Plain text
+#: user-manual.txt:1469
+msgid "_Subsurface website._ A link to the URL of Subsurface web"
+msgstr ""
+
+#. type: Plain text
+#: user-manual.txt:1471
+msgid "_Version._ Displays the current version of the Companion App."
+msgstr ""
+
+#. type: Title =====
+#: user-manual.txt:1472
+#, no-wrap
+msgid "Search"
+msgstr ""
+
+#. type: Plain text
+#: user-manual.txt:1475
+msgid "Search the saved dive locations by name or by date and time."
+msgstr ""
+
+#. type: Title =====
+#: user-manual.txt:1476
+#, no-wrap
+msgid "Start service"
+msgstr ""
+
+#. type: Plain text
+#: user-manual.txt:1479
+msgid ""
+"Initiates the _background service_ following the previously defined settings."
+msgstr ""
+
+#. type: Title =====
+#: user-manual.txt:1480
+#, no-wrap
+msgid "Disconnect"
+msgstr ""
+
+#. type: Plain text
+#: user-manual.txt:1488
+msgid ""
+"This is a badly named option that disconnects the app from the server by "
+"resetting the user ID in the app, showing the first screen where an account "
+"can be created, retrieve the ID for an existing account or use the users own "
+"ID. The disconnect option is useful if a user's Android device was used to "
+"download the dive locations of another registered diver."
+msgstr ""
+
+#. type: Title =====
+#: user-manual.txt:1489
+#, no-wrap
+msgid "Send all locations"
+msgstr ""
+
+#. type: Plain text
+#: user-manual.txt:1492
+msgid ""
+"This option sends all locations stored in the Android device to the server."
+msgstr ""
+
+#. type: Title ====
+#: user-manual.txt:1494
+#, no-wrap
+msgid "Downloading dive locations to the _Subsurface_ divelog"
+msgstr ""
+
+#. type: Plain text
+#: user-manual.txt:1503
+msgid ""
+"Download dive(s) from a dive computer or enter them manually into "
+"_Subsurface_ before obtaining the GPS coordinates from the server. The "
+"download dialog can be reached via _Ctrl+G_ or from the _Subsurface_ Main "
+"Menu _Import -> Import GPS data from Subsurface Service_, resulting in the "
+"image on the left (*A*), below. On first use the DIVERID text box is blank. "
+"Provide a DIVERID, then select the _Download_ button to initiate the "
+"download process, after which the screen on the right (*B*) below appears:"
+msgstr ""
+
+#. type: Target for macro image
+#: user-manual.txt:1504
+#, no-wrap
+msgid "images/DownloadGPS.jpg"
+msgstr ""
+
+#. type: Plain text
+#: user-manual.txt:1512
+msgid ""
+"Note that the _Apply_ button is now active. By clicking on it, users can "
+"update the locations of the newly entered or uploaded dives in _Subsurface_ "
+"which applies the coordinates and names entered on the app for all the new "
+"dives that match the date-times of the uploaded GPS localities. If one has "
+"entered the name of the dive location in _Subsurface_ before downloading the "
+"GPS coordinates, this name will take precedence over downloaded one."
+msgstr ""
+
+#. type: Plain text
+#: user-manual.txt:1519
+msgid ""
+"Since _Subsurface_ matches GPS locations from the Android device and dive "
+"information from the dive computer based on date-time data, automatic "
+"assignment of GPS data to dives is dependent on agreement of the date-time "
+"information between these two devices. Although _Subsurface_ has a wide "
+"range tolerance, it may be unable to identify the appropriate dive if there "
+"is a large difference between the time in the dive computer and that of the "
+"Android device, resulting in no updates."
+msgstr ""
+
+#. type: Plain text
+#: user-manual.txt:1527
+msgid ""
+"Similar date-times may not always be possible and there may be many reasons "
+"for this (e.g. time zones), or _Subsurface_ may be unable to decide which is "
+"the correct position for a dive (e.g. on repetitive dives while running "
+"_background service_ there may be several locations that would be included "
+"in the time range that fit not only the first dive, but one or more "
+"subsequent dives as well).  A workaround for this situation to manually edit "
+"the date-time of a dive in the _Subsurface_ Dive List *before* downloading "
+"the GPS data and then to change the date-time back again *after* downloading "
+"GPS data."
+msgstr ""
+
+#. type: Plain text
+#: user-manual.txt:1531
+msgid "TIPS:"
+msgstr ""
+
+#. type: Plain text
+#: user-manual.txt:1538
+msgid ""
+"_Background service_, being a very powerful tool, may fill the location list "
+"with many unnecessary locations not corresponding to the exact dive point "
+"but reflecting the boat's route.  Currently these locations are difficult to "
+"delete from the server. In some situations it is therefore prudent to clean "
+"up the list on the Android device before sending the dive points to the web "
+"server by simply deleting the inappropriate locations. This might be "
+"necessary, for instance, if one wants to keep the location list clear to see "
+"dives in the web service map display (see above)."
+msgstr ""
+
+#. type: Plain text
+#: user-manual.txt:1542
+msgid ""
+"It may also make sense to give informative names to the locations sent to "
+"the web server, or at least to use an informative name in the _Name "
+"Template_ setting while running the _background service_, especially on a "
+"dive trip with many dives and dive locations."
+msgstr ""
+
+#. type: Title ===
+#: user-manual.txt:1544
+#, no-wrap
+msgid "Adding photographs to dives"
+msgstr ""
+
+#. type: Plain text
+#: user-manual.txt:1550
+msgid ""
+"Many (if not most) divers take a camera with them and take photographs "
+"during a dive. One would like to associate each photograph with a specific "
+"dive. _Subsurface_ allows one to load photos into a dive. Photos are "
+"superimposed on the dive profile, from where they can be viewed."
+msgstr ""
+
+#. type: Title ====
+#: user-manual.txt:1551
+#, no-wrap
+msgid "Loading photos and getting synchronisation between dive computer and camera"
+msgstr ""
+
+#. type: Plain text
+#: user-manual.txt:1555
+msgid ""
+"Left-lick on a dive or on a group of dives on the dive list. Then right-"
+"click on this dive or group of dives and choose the option _Load Images_:"
+msgstr ""
+
+#. type: Target for macro image
+#: user-manual.txt:1556
+#, no-wrap
+msgid "images/LoadImage1_f20.jpg"
+msgstr ""
+
+#. type: Plain text
+#: user-manual.txt:1560
+msgid ""
+"The system file browser appears. Select the folder and photographs that need "
+"to be loaded into _Subsurface_ and click the _Open_ button."
+msgstr ""
+
+#. type: Target for macro image
+#: user-manual.txt:1561
+#, no-wrap
+msgid "images/LoadImage2_f20.jpg"
+msgstr ""
+
+#. type: Plain text
+#: user-manual.txt:1570
+msgid ""
+"This brings one to the time synchronisation dialog, shown below. The "
+"critical problem is that the time synchronisation is not perfect between the "
+"dive computer used during a dive, and the camera used during that same dive. "
+"These two devices often differ by several minutes. If _Subsurface_ can "
+"achieve synchronisation, then the exact times of photographs can be used to "
+"position photographs on the dive profile."
+msgstr ""
+
+#. type: Plain text
+#: user-manual.txt:1572
+msgid "_Subsurface_ achieves this synchronisation in two ways:"
+msgstr ""
+
+#. type: Plain text
+#: user-manual.txt:1584
+#, no-wrap
+msgid ""
+"*Manually*: If the user wrote down the exact camera time at the start of a dive, the\n"
+"difference in time between the two devices can be determined. Actually, as long as the device\n"
+"settings for time has not been changed in either device, one could write down the times of\n"
+"both devices after the dive or even at the end of the day. One can then manually set the time\n"
+"difference in the _Time shift_ dialog. Towards the top of the dialog is a time setting tool\n"
+"immediately under the heading _Shift times of image(s) by_, evident in figure *A* below.\n"
+"If the camera time is 7 minutes later than that of the dive computer, set the time setting\n"
+"tool to a value of 00:07.  Select either the _earlier_ or _later_ radio button.\n"
+"In the above example, the _earlier_ option is appropriate, since the photos need to be shifted\n"
+"7 minutes earlier (camera is 7 minutes ahead of dive computer). Ignore any \"AM\" or \"PM\" suffix\n"
+"in that tool. Click the _OK_ button and synchronisation is achieved.\n"
+msgstr ""
+
+#. type: Target for macro image
+#: user-manual.txt:1585
+#, no-wrap
+msgid "images/LoadImage3b_f20.jpg"
+msgstr ""
+
+#. type: Plain text
+#: user-manual.txt:1603
+#, no-wrap
+msgid ""
+"*By photograph*: There is a very slick way of achieving synchronisation. If one takes a\n"
+"photograph of the face of the dive computer showing the time, then _Subsurface_ can obtain\n"
+"the exact time the photograph was taken, using the metadata that the camera stores within\n"
+"each photo. In order to do this, use the bottom half of the Time shift_ dialog. If one uses\n"
+"the bottom part, the top part of the dialog is ignored. Click on\n"
+"the horizontal bar entitled \"_Select image of divecomputer showing time_. This brings up\n"
+"a file browser with which one can select the photograph of the dive computer. Select the\n"
+"photograph using the file browser and click on _OK_. This photograph of the dive computer\n"
+"appears in the bottom panel of the _Shift times_ dialog. Now _Subsurface_ knows exactly\n"
+"when the photograph has been taken. Now set the date-time dialog to the left of the photo\n"
+"so that this tool reflects the date and time of the dive computer in the photo. When the\n"
+"date-time tool has been set, _Subsurface_ knows exactly what the time difference between\n"
+"camera and dive computer is, and synchronisation is achieved. There is a\n"
+"photograph with the face of the dive computer and with the date-time tool set to the\n"
+"date-time on image *B* above.\n"
+msgstr ""
+
+#. type: Plain text
+#: user-manual.txt:1606
+msgid ""
+"If the timestamp of a photograph is long before or after the dive, it is not "
+"placed on the dive profile. If the timestamp of the photo is within 30 "
+"minutes of the dive, it is shown."
+msgstr ""
+
+#. type: Title ====
+#: user-manual.txt:1607
+#, no-wrap
+msgid "Viewing the photos"
+msgstr ""
+
+#. type: Plain text
+#: user-manual.txt:1611
+msgid ""
+"In order to view the photos added to a dive, activate the _show-photos_ "
+"button in the tool bar to the left of the dive profile:"
+msgstr ""
+
+#. type: Target for macro image
+#: user-manual.txt:1612
+#, no-wrap
+msgid "images/icons/ShowPhotos_f20.png"
+msgstr ""
+
+#. type: Plain text
+#: user-manual.txt:1615
+msgid "After the images have been loaded, they appear in two places:"
+msgstr ""
+
+#. type: Plain text
+#: user-manual.txt:1617
+msgid "the _Photos_ tab of the *Dive Notes* panel."
+msgstr ""
+
+#. type: Plain text
+#: user-manual.txt:1619
+msgid ""
+"as tiny icons (stubs) on the dive profile at the appropriate positions "
+"reflecting the time each photograph was taken. See below:"
+msgstr ""
+
+#. type: Target for macro image
+#: user-manual.txt:1620
+#, no-wrap
+msgid "images/LoadImage4_f20.jpg"
+msgstr ""
+
+#. type: Plain text
+#: user-manual.txt:1624
+msgid ""
+"If one hovers with the mouse over any of the photo icons, then a thumbnail "
+"photo is shown of the appropriate photo. See the image below:"
+msgstr ""
+
+#. type: Target for macro image
+#: user-manual.txt:1625
+#, no-wrap
+msgid "images/LoadImage5_f20.jpg"
+msgstr ""
+
+#. type: Plain text
+#: user-manual.txt:1634
+msgid ""
+"Clicking on the thumbnail brings up a full size photo overlaid on the "
+"_Subsurface_ window. This allows good viewing of the photographs that have "
+"been added (see the image below). Note that the thumbnail has a small "
+"dustbin icon in the bottom right hand corner (see image above). If one "
+"selects the dustbin, the image is removed from the dive. Therefore some care "
+"is required when clicking on a thumbnail. Images can also be deleted using "
+"the _Photos_ tab (see text below)."
+msgstr ""
+
+#. type: Target for macro image
+#: user-manual.txt:1635
+#, no-wrap
+msgid "images/LoadImage6_f20.jpg"
+msgstr ""
+
+#. type: Title ====
+#: user-manual.txt:1637
+#, no-wrap
+msgid "The _Photos_ tab"
+msgstr ""
+
+#. type: Plain text
+#: user-manual.txt:1648
+msgid ""
+"Photographs associated with a dive are shown as thumbnails in the _Photos_ "
+"tab of the _Dive Notes_ panel. Photos taken in rapid succession during a "
+"dive (therefore sometimes with large overlap on the dive profile) can easily "
+"be accessed in the _Photos_ tab. This tab serves as a tool for individually "
+"accessing the photos of a dive, while the stubs on the dive profile give an "
+"indication of when during a dive a photo was taken. By single-clicking on a "
+"thumbnail in the _Photos_ panel, a photo is selected. By double-clicking a "
+"thumbnail, the full-sized image is shown, overlaying the _Subsurface_ "
+"window. A photo can be deleted from the _Photos_ panel by selecting it "
+"(single-click) and then by pressing the _Del_ key on the keyboard. This "
+"removes the photo both from the _Photos_ tab as well as the dive profile."
+msgstr ""
+
+#. type: Title ====
+#: user-manual.txt:1649
+#, no-wrap
+msgid "Photos on an external hard disk"
+msgstr ""
+
+#. type: Plain text
+#: user-manual.txt:1660
+msgid ""
+"Most underwater photographers store their photos on an external drive. If "
+"such a drive can be mapped (almost always the case) the photos can be "
+"directly accessed by _Subsurface_. This facilitates the interaction between "
+"_Subsurface_ and an external repository of photos. When associating a dive "
+"profile with photos from an external drive, the normal procedure of "
+"selection and synchronisation (see text above) is used.  However, after the "
+"external drive has been disconnected, _Subsurface_ cannot access these "
+"photos any more.  If the display of photos is activated (using the toolbox "
+"to the left of the _Dive Profile_), the program only shows a small white dot "
+"where each photo should be on the dive profile.  In addition the _Photos_ "
+"tab only shows the file names of the photos. This is normal behaviour.  If, "
+"later, the external drive with the photos is connected again, the photos can "
+"be seen in the normal way."
+msgstr ""
+
+#. type: Title ===
+#: user-manual.txt:1662
+#, no-wrap
+msgid "Logging special types of dives"
+msgstr ""
+
+#. type: Title ====
+#: user-manual.txt:1664
+#, no-wrap
+msgid "Sidemount dives"
+msgstr ""
+
+#. type: Plain text
+#: user-manual.txt:1668
+msgid ""
+"_Subsurface_ easily handles dives involving more than one cylinder. "
+"Sidemount dive logging involves three steps:"
+msgstr ""
+
+#. type: Plain text
+#: user-manual.txt:1677
+#, no-wrap
+msgid ""
+"*During the dive, recording cylinder switch events*. Since sidemount diving normally involves two\n"
+"cylinders with air or with the same gas mixture, _Subsurface_ distinguishes among these different\n"
+"cylinders. In contrast, most dive computers that allow gas switching only distinguish among different\n"
+"_gases_ used, not among different _cylinders_ used. This means that when sidemount dives are downloaded\n"
+"from these dive computers, the events of switching between cylinders with the same gas are not downloaded. This may mean\n"
+"that one may have to keep a written log of cylinder switch times using a slate, or (if the dive computer\n"
+"has this facility) marking each cylinder switch with a bookmark that can be retrieved later. Returning\n"
+"from a dive with the information about cylinder changes is the only tricky part of logging sidemount dives.\n"
+msgstr ""
+
+#. type: Plain text
+#: user-manual.txt:1680
+#, no-wrap
+msgid ""
+"*Within _Subsurface_ describe the cylinders used during the dive*. The diver needs to provide the\n"
+"specifications of the different cylinders, using the *Equipment* tab of the *Dive Info Panel* (see\n"
+"image below where two 12 litre cylinder were used).\n"
+msgstr ""
+
+#. type: Plain text
+#: user-manual.txt:1690
+#, no-wrap
+msgid ""
+"*Indicate cylinder change events on the _Subsurface_ dive profile*. Once the dive log has been imported\n"
+"from a dive computer into _Subsurface_, the cylinder switch events need to be indicated on the dive profile.\n"
+"Cylinder changes are recorded by right-clicking at the appropriate point on the dive profile and then\n"
+"selecting _Add gas change_. A list of the appropriate cylinders is shown with the\n"
+"currently used cylinder greyed out. In the image below Tank 1 is greyed out, leaving only Tank 2\n"
+"to be selected. Select the appropriate cylinder. The cylinder change is then indicated on the dive\n"
+"profile with a cylinder symbol. If the *Tank Bar* is activated using the toolbar to the left of the\n"
+"profile, then the cylinder change is also indicated on the Tank Bar (see image below). After all\n"
+"the cylinder change events have been recorded on the dive profile, the correct cylinder pressures\n"
+"for both cylinders are shown on the dive profile, as inthe image below.\n"
+msgstr ""
+
+#. type: Target for macro image
+#: user-manual.txt:1691
+#, no-wrap
+msgid "images/sidemount1.jpg"
+msgstr ""
+
+#. type: Title ==
+#: user-manual.txt:1693
+#, no-wrap
+msgid "Obtaining more information about dives entered into the logbook"
+msgstr ""
+
+#. type: Title ===
+#: user-manual.txt:1695
+#, no-wrap
+msgid "The *Dive Info* tab (for individual dives)"
+msgstr ""
+
+#. type: Plain text
+#: user-manual.txt:1702
+msgid ""
+"The Dive Info tab gives some summary information about a particular dive "
+"that has been selected in the *Dive List*. Useful information here includes "
+"the surface interval before the dive, the maximum and mean depths of the "
+"dive, the gas volume consumed, the surface air consumption (SAC) and the "
+"number of oxygen toxicity units (OTU) incurred."
+msgstr ""
+
+#. type: Plain text
+#: user-manual.txt:1709
+msgid ""
+"Gas consumption and SAC calculations: _Subsurface_ calculates SAC and Gas "
+"consumption taking in account gas incompressibility, particularly at tank "
+"pressures above 200 bar, making them more accurate.  Users should refer to "
+"xref:SAC_CALCULATION[Appendix D] for more information."
+msgstr ""
+
+#. type: Title ===
+#: user-manual.txt:1710
+#, no-wrap
+msgid "The *Extra Data* tab (usually for individual dives)"
+msgstr ""
+
+#. type: Plain text
+#: user-manual.txt:1718
+msgid ""
+"When using a dive computer, it often reports several data items that cannot "
+"easily be presented in a standardised way because the nature of the "
+"information differs from one dive computer to another. These data often "
+"comprise setup information, metadata about a dive, battery levels, no fly "
+"times, or gradient factors used during the dive. When possible, this "
+"information is presented in the *Extra Data* tab. Below is an image showing "
+"extra data for a dive using a Poseidon rebreather."
+msgstr ""
+
+#. type: Target for macro image
+#: user-manual.txt:1719
+#, no-wrap
+msgid "images/ExtraDataTab_f20.jpg"
+msgstr ""
+
+#. type: Title ===
+#: user-manual.txt:1721
+#, no-wrap
+msgid "The *Stats* tab (for groups of dives)"
+msgstr ""
+
+#. type: Plain text
+#: user-manual.txt:1732
+msgid ""
+"The Stats tab gives summary statistics for more than one dive, assuming that "
+"more than one dive has been selected in the *Dive List* using the standard "
+"Ctrl-click or Shift-click of the mouse. If only one dive has been selected, "
+"figures pertaining to only that dive are given. This tab shows the number of "
+"dives selected, the total amount of dive time in these dives, as well as the "
+"minimum, maximum and mean for the dive duration, water temperature and "
+"surface air consumption (SAC). It also shows the depth of the shallowest and "
+"deepest dives of those selected."
+msgstr ""
+
+#. type: Title ===
+#: user-manual.txt:1734
+#, no-wrap
+msgid "The *Dive Profile*"
+msgstr ""
+
+#. type: Target for macro image
+#: user-manual.txt:1736
+#, no-wrap
+msgid "images/Profile2.jpg"
+msgstr ""
+
+#. type: Plain text
+#: user-manual.txt:1747
+msgid ""
+"Of all the panels in _Subsurface_, the Dive Profile contains the most "
+"detailed information about each dive. The Dive Profile has a *button bar* on "
+"the left hand side that allows control over several display options. The "
+"functions of these buttons are described below. The main item in the Dive "
+"Profile is the graph of dive depth as a function of time. In addition to the "
+"obvious information of the depth it also shows the ascent and descent rates "
+"compared to the recommended speed of going up or down in the water column. "
+"This information is given using different colours:"
+msgstr ""
+
+#. type: delimited block |
+#: user-manual.txt:1754
+#, no-wrap
+msgid ""
+"|*Colour*|*Descent speed (m/min)*|*Ascent speed (m/min)*\n"
+"|Red|> 30|> 18\n"
+"|Orange|18 - 30|9 - 18\n"
+"|Yellow|9 - 18|4 - 9\n"
+"|Light green|1.5 - 9|1.5 - 4\n"
+"|Dark green|< 1.5|< 1.5\n"
+msgstr ""
+
+#. type: Plain text
+#: user-manual.txt:1759
+msgid ""
+"The profile also includes depth readings for the peaks and troughs in the "
+"graph.  Thus, users should see the depth of the deepest point and other "
+"peaks. Mean depth is marked with a horizontal red line."
+msgstr ""
+
+#. type: Named 'icon' AttributeList argument for style 'icon'
+#: user-manual.txt:1760
+#, no-wrap
+msgid "images/icons/scale.jpg"
+msgstr ""
+
+#. type: Plain text
+#: user-manual.txt:1765
+msgid ""
+"In some cases the dive profile does not fill the whole area of the *Dive "
+"Profile* panel. Clicking the *Scale* button in the toolbar on the left of "
+"the dive profile frequently increases the size of the dive profile to fill "
+"the area of the panel efficiently."
+msgstr ""
+
+#. type: Plain text
+#: user-manual.txt:1768
+#, no-wrap
+msgid ""
+"*Water temperature* is displayed with its own blue line with temperature values\n"
+"placed adjacent to significant changes.\n"
+msgstr ""
+
+#. type: Plain text
+#: user-manual.txt:1773
+msgid ""
+"The dive profile can include graphs of the *partial pressures* of O2, N2, "
+"and He during the dive (see figure above) as well as a calculated and dive "
+"computer reported deco ceilings (only visible for deep, long, or repetitive "
+"dives). Partial pressures of oxygen are indicated in green, those of "
+"nitrogen in black, and those of helium in dark red. These partial pressure "
+"graphs are shown below the profile data."
+msgstr ""
+
+#. type: Named 'icon' AttributeList argument for style 'icon'
+#: user-manual.txt:1774
+#, no-wrap
+msgid "images/icons/O2.jpg"
+msgstr ""
+
+#. type: Plain text
+#: user-manual.txt:1778
+msgid ""
+"Clicking this button allows display of the partial pressure of *oxygen* "
+"during the dive. This is depicted below the dive depth and water temperature "
+"graphs."
+msgstr ""
+
+#. type: Named 'icon' AttributeList argument for style 'icon'
+#: user-manual.txt:1779
+#, no-wrap
+msgid "images/icons/N2.jpg"
+msgstr ""
+
+#. type: Plain text
+#: user-manual.txt:1782
+msgid ""
+"Clicking this button allows display of the partial pressure of *nitrogen* "
+"during the dive."
+msgstr ""
+
+#. type: Named 'icon' AttributeList argument for style 'icon'
+#: user-manual.txt:1783
+#, no-wrap
+msgid "images/icons/He.jpg"
+msgstr ""
+
+#. type: Plain text
+#: user-manual.txt:1787
+msgid ""
+"Clicking this button allows display of the partial pressure of *helium* "
+"during the dive.  This is only of importance to divers using Trimix, "
+"Helitrox or similar breathing gasses."
+msgstr ""
+
+#. type: Plain text
+#: user-manual.txt:1800
+msgid ""
+"The *air consumption* graph displays the tank pressure and its change during "
+"the dive. The air consumption takes depth into account so that even when "
+"manually entering the start and end pressures the graph is not a straight "
+"line.  Similarly to the depth graph the slope of the tank pressure gives the "
+"user information about the momentary SAC rate (Surface Air Consumption) when "
+"using an air integrated dive computer.  Here the colour coding is not "
+"relative to some absolute values but relative to the average normalised air "
+"consumption during the dive. So areas that are red or orange indicate times "
+"of increased normalized air consumption while dark green reflects times when "
+"the diver was using less gas than average."
+msgstr ""
+
+#. type: Named 'icon' AttributeList argument for style 'icon'
+#: user-manual.txt:1801
+#, no-wrap
+msgid "images/icons/Heartbutton.png"
+msgstr ""
+
+#. type: Plain text
+#: user-manual.txt:1805
+msgid ""
+"Clicking on the heart rate button will allow the display of heart rate "
+"information during the dive if the dive computer was attached to a heart "
+"rate sensor."
+msgstr ""
+
+#. type: Plain text
+#: user-manual.txt:1813
+#, no-wrap
+msgid ""
+"It is possible to *zoom* into the profile graph. This is done either by using\n"
+"the scroll wheel / scroll gesture of your mouse or trackpad. By default\n"
+"_Subsurface_ always shows a profile area large enough for at least 30 minutes\n"
+"and 30m\n"
+" (100ft) – this way short or shallow dives are intuitively recognizable;\n"
+"something\n"
+"that free divers clearly won’t care about.\n"
+msgstr ""
+
+#. type: Target for macro image
+#: user-manual.txt:1814
+#, no-wrap
+msgid "images/MeasuringBar.png"
+msgstr ""
+
+#. type: Named 'icon' AttributeList argument for style 'icon'
+#: user-manual.txt:1816
+#, no-wrap
+msgid "images/icons/ruler.jpg"
+msgstr ""
+
+#. type: Plain text
+#: user-manual.txt:1824
+msgid ""
+"Measurements of *depth or time differences* can be achieved by using the "
+"*ruler button* on the left of the dive profile panel.  The measurement is "
+"done by dragging the red dots to the two points on the dive profile that the "
+"user wishes to measure. Information is then given in the horizontal white "
+"area underneath the two red dots."
+msgstr ""
+
+#. type: Named 'icon' AttributeList argument for style 'icon'
+#: user-manual.txt:1825
+#, no-wrap
+msgid "images/icons/ShowPhotos.png"
+msgstr ""
+
+#. type: Plain text
+#: user-manual.txt:1832
+msgid ""
+"Photographs that have been added to a dive can be shown on the profile by "
+"selecting the *Show-photo* button. The position of a photo on the profile "
+"indicates the exact time when this photo was taken. If this button is not "
+"active, the photos are hidden."
+msgstr ""
+
+#. type: Plain text
+#: user-manual.txt:1861
+msgid ""
+"The profile can also include the dive computer reported *ceiling* (more "
+"precisely, the deepest deco stop that the dive computer calculated for each "
+"particular moment in time) as a red overlay on the dive profile. Ascent "
+"ceilings arise when a direct ascent to the surface increases the risk of a "
+"diver suffering from decompression sickness (DCS) and it is necessary to "
+"either ascend slower or to perform decompression stop(s) before ascending to "
+"the surface. Not all dive computers record this information and make it "
+"available for download; for example all of the Suunto dive computers fail to "
+"make this very useful data available to divelog software. _Subsurface_ also "
+"calculates ceilings independently, shown as a green overlay on the dive "
+"profile.  Because of the differences in algorithms used and amount of data "
+"available (and other factors taken into consideration at the time of the "
+"calculation) it is unlikely that ceilings from dive computers and from "
+"_Subsurface_ are the same, even if the same algorithm and _gradient factors_ "
+"(see below) are used.  It is also quite common that _Subsurface_ calculates "
+"a ceiling for non-decompression dives when the dive computer stayed in non-"
+"deco mode during the whole dive (represented by the [green]#dark green# "
+"section in the profile at the beginning of this section). This is caused by "
+"the fact that _Subsurface’s_ calculations describe the deco obligation at "
+"each moment during a dive, while dive computers usually take the upcoming "
+"ascent into account. During the ascent some excess nitrogen (and possibly "
+"helium) are already breathed off so even though the diver technically "
+"encountered a ceiling at depth, the dive still does not require an explicit "
+"deco stop. This feature allows dive computers to offer longer non-stop "
+"bottom times."
+msgstr ""
+
+#. type: Named 'icon' AttributeList argument for style 'icon'
+#: user-manual.txt:1862
+#, no-wrap
+msgid "images/icons/cceiling.jpg"
+msgstr ""
+
+#. type: Plain text
+#: user-manual.txt:1867
+msgid ""
+"If the dive computer itself calculates a ceiling and makes it available to "
+"_Subsurface_ during upload of dives, this can be shown as a red area by "
+"checking *Dive computer reported ceiling* button on the Profile Panel."
+msgstr ""
+
+#. type: Named 'icon' AttributeList argument for style 'icon'
+#: user-manual.txt:1868
+#, no-wrap
+msgid "images/icons/ceiling1.jpg"
+msgstr ""
+
+#. type: Plain text
+#: user-manual.txt:1873
+msgid ""
+"If the *Calculated ceiling* button on the Profile Panel is clicked, then a "
+"ceiling, calculated by _Subsurface_, is shown in green if it exists for a "
+"particular dive (*A* in figure below). This setting can be modified in two "
+"ways:"
+msgstr ""
+
+#. type: Named 'icon' AttributeList argument for style 'icon'
+#: user-manual.txt:1874
+#, no-wrap
+msgid "images/icons/ceiling2.jpg"
+msgstr ""
+
+#. type: Plain text
+#: user-manual.txt:1878
+msgid ""
+"If, in addition, the *show all tissues* button on the Profile Panel is "
+"clicked, the ceiling is shown for the tissue compartments following the "
+"Bühlmann model (*B* in figure below)."
+msgstr ""
+
+#. type: Named 'icon' AttributeList argument for style 'icon'
+#: user-manual.txt:1879
+#, no-wrap
+msgid "images/icons/ceiling3.jpg"
+msgstr ""
+
+#. type: Plain text
+#: user-manual.txt:1883
+msgid ""
+"If, in addition, the *3m increments* button on the Profile Panel is clicked, "
+"then the ceiling is indicated in 3 m increments (*C* in figure below)."
+msgstr ""
+
+#. type: Target for macro image
+#: user-manual.txt:1884
+#, no-wrap
+msgid "images/Ceilings2.jpg"
+msgstr ""
+
+#. type: Named 'icon' AttributeList argument for style 'icon'
+#: user-manual.txt:1886
+#, no-wrap
+msgid "images/icons/ShowCylindersButton.jpg"
+msgstr ""
+
+#. type: Plain text
+#: user-manual.txt:1892
+msgid ""
+"By selecting this icon, the different cylinders used during a dive can be "
+"represented as a coloured bar at the bottom of the *Dive Profile*. In "
+"general oxygen is represented by a green bar, nitrogen with a yellow bar and "
+"helium with a red bar. The image below shows a dive which first uses a "
+"trimix cylinder (red and green), followed by a switch to a nitrox cylinder "
+"(yellow and green) after 23 minutes. Cylinders with air are shown as a light "
+"blue bar."
+msgstr ""
+
+#. type: Target for macro image
+#: user-manual.txt:1893
+#, no-wrap
+msgid "images/ShowCylinders_f20.jpg"
+msgstr ""
+
+#. type: Named 'icon' AttributeList argument for style 'icon'
+#: user-manual.txt:1896
+#, no-wrap
+msgid "images/tissues.jpg"
+msgstr ""
+
+#. type: Plain text
+#: user-manual.txt:1908
+msgid ""
+"Display inert gas tissue pressures relative to ambient inert gas pressure "
+"(horizontal grey line).  Tissue pressures are calculated using the Bühlmann "
+"ZH-L16 algorithm and are displayed as lines ranging from green (faster "
+"tissues) to blue (slower tissues).  The black line, graphed above the "
+"ambient pressure, is the maximum allowable tissue supersaturation (pressure "
+"limit) derived from the gradient factors specified in the *Preferences*. For "
+"divers involved in planned decompression diving, efficient rates of "
+"offgasing are obtained with tissue pressures between the ambient inert gas "
+"pressure (grey line) and the pressure limit (black line). This display is a "
+"representation of the tissue pressures during the whole dive. In contast, "
+"the xref:S_gas_pressure_graph[Gas Pressure Graph] in the *Information Box* "
+"on the *Dive Profile* is an instantaneous reflection of tissue pressures at "
+"the moment in time reflected by the position of the cursor on the dive "
+"profile."
+msgstr ""
+
+#. type: Target for macro image
+#: user-manual.txt:1909
+#, no-wrap
+msgid "images/tissuesGraph.jpg"
+msgstr ""
+
+#. type: Plain text
+#: user-manual.txt:1917
+msgid ""
+"Gradient Factor settings strongly affect the calculated ceilings and their "
+"depths.  For more information about Gradient factors, see the section on "
+"xref:S_GradientFactors[Gradient Factor Preference settings]. The currently "
+"used gradient factors (e.g. GF 35/75) are shown above the depth profile if "
+"the appropriate toolbar buttons are activated.  *N.B.:* The indicated "
+"gradient factors are NOT the gradient factors in use by the dive computer, "
+"but those used by _Subsurface_ to calculate deco obligations during the "
+"dive. For more information external to this manual see:"
+msgstr ""
+
+#. type: Plain text
+#: user-manual.txt:1919 user-manual.txt:2533
+#, no-wrap
+msgid " ** http://www.tek-dive.com/portal/upload/M-Values.pdf[Understanding M-values by Erik Baker, _Immersed_ Vol. 3, No. 3.]\n"
+msgstr ""
+
+#. type: Plain text
+#: user-manual.txt:1921 user-manual.txt:2535
+#, no-wrap
+msgid " ** link:http://www.rebreatherworld.com/general-and-new-to-rebreather-articles/5037-gradient-factors-for-dummies.html[Gradient factors for dummies, by Kevin Watts]\n"
+msgstr ""
+
+#. type: Title ===
+#: user-manual.txt:1923
+#, no-wrap
+msgid "The Dive Profile context menu"
+msgstr ""
+
+#. type: Plain text
+#: user-manual.txt:1941
+msgid ""
+"The context menu for the Dive Profile is accessed by right-clicking while "
+"the mouse cursor is over the Dive Profile panel. The menu allows the "
+"creation of Bookmarks or Gas Change Event markers or manual CCR set-point "
+"changes other than the ones that might have been imported from a Dive "
+"Computer. Markers are placed against the depth profile line and with the "
+"time of the event set by where the mouse cursor was when the right mouse "
+"button was initially clicked to bring up the menu. Gas Change events involve "
+"a selection of which gas is being switched to, the list of choices being "
+"based on the available gases defined in the Equipment Tab. Set-point change "
+"events open a dialog allowing to choose the next set-point value. As in the "
+"planner, a set-point value of zero indicates the diver is breathing from an "
+"open circuit system while any non-zero value indicates the use of a closed "
+"circuit rebreather (CCR).  By right-clicking while over an existing marker a "
+"menu appears, adding options to allow deletion of the marker or to allow all "
+"markers of that type to be hidden. Hidden events can be restored to view by "
+"selecting Unhide all events from the context menu."
+msgstr ""
+
+#. type: Title ===
+#: user-manual.txt:1942
+#, no-wrap
+msgid "The *Information Box*"
+msgstr ""
+
+#. type: Plain text
+#: user-manual.txt:1952
+msgid ""
+"The Information box displays a large range of information pertaining to the "
+"dive profile. Normally the Information Box is located to the top left of the "
+"*Dive Profile* panel. If the mouse points outside of the *Dive Profile* "
+"panel, then only the top line of the Information Box is visible (see left-"
+"hand part of figure (*A*) below). The Information Box can be moved around in "
+"the *Dive Profile* panel by click-dragging it with the mouse so that it is "
+"not obstructing important detail. The position of the Information Box is "
+"saved and used again during subsequent dive analyses."
+msgstr ""
+
+#. type: Target for macro image
+#: user-manual.txt:1953
+#, no-wrap
+msgid "images/InfoBox2.jpg"
+msgstr ""
+
+#. type: Plain text
+#: user-manual.txt:1970
+msgid ""
+"The moment the mouse points inside the *Dive Profile* panel, the information "
+"box expands and shows many data items. In this situation, the data reflect "
+"the time point along the dive profile indicated by the mouse cursor (see "
+"right-hand part of figure (*B*) above where the Information Box reflects the "
+"situation at the position of the cursor [arrow] in that image). Therefore, "
+"moving the cursor in the horizontal direction allows the Information Box to "
+"show information for any point along the dive profile.  In this mode, the "
+"Information Box gives extensive statistics about depth, gas and ceiling "
+"characteristics of the particular dive. These include: Time period into the "
+"dive (indicated by a @), depth, cylinder pressure (P), temperature, ascent/"
+"descent rate, surface air consumption (SAC), oxygen partial pressure, "
+"maximum operating depth, equivalent air depth (EAD), equivalent narcotic "
+"depth (END), equivalent air density depth (EADD), decompression requirements "
+"at that instant in time (Deco), time to surface (TTS), the calculated "
+"ceiling, as well as the calculated ceiling for several Bühlmann tissue "
+"compartments."
+msgstr ""
+
+#. type: Plain text
+#: user-manual.txt:1973
+msgid ""
+"The user has control over the display of several statistics, represented as "
+"four buttons on the left of the profile panel. These are:"
+msgstr ""
+
+#. type: Named 'icon' AttributeList argument for style 'icon'
+#: user-manual.txt:1974
+#, no-wrap
+msgid "images/icons/MOD.jpg"
+msgstr ""
+
+#. type: Plain text
+#: user-manual.txt:1981
+msgid ""
+"Clicking this button causes the Information Box to display the *Maximum "
+"Operating Depth (MOD)* of the dive, given the gas mixture used. MOD is "
+"dependent on the oxygen concentration in the breathing gas.  For air (21% "
+"oxygen) it is around 57 m. Below the MOD there is a markedly increased risk "
+"of exposure to the dangers associated with oxygen toxicity."
+msgstr ""
+
+#. type: Named 'icon' AttributeList argument for style 'icon'
+#: user-manual.txt:1982
+#, no-wrap
+msgid "images/icons/NDL.jpg"
+msgstr ""
+
+#. type: Plain text
+#: user-manual.txt:1991
+msgid ""
+"Clicking this button causes the Information Box to display the *No-deco "
+"Limit (NDL)* or the *Total Time to Surface (TTS)*. NDL is the time duration "
+"that a diver can continue with a dive, given the present depth, that does "
+"not require decompression (that is, before an ascent ceiling appears). Once "
+"one has exceeded the NDL and decompression is required (that is, there is an "
+"ascent ceiling above the diver, then TTS gives the number of minutes "
+"required before the diver can surface. TTS includes ascent time as well as "
+"decompression time."
+msgstr ""
+
+#. type: Named 'icon' AttributeList argument for style 'icon'
+#: user-manual.txt:1992
+#, no-wrap
+msgid "images/icons/SAC.jpg"
+msgstr ""
+
+#. type: Plain text
+#: user-manual.txt:2001
+msgid ""
+"Clicking this button causes the Information Box to display the *Surface Air "
+"Consumption (SAC)*.  SAC is an indication of the surface-normalised "
+"respiration rate of a diver. The value of SAC is less than the real "
+"respiration rate because a diver at 10m uses breathing gas at a rate roughly "
+"double that of the equivalent rate at the surface. SAC gives an indication "
+"of breathing gas consumption rate independent of the depth of the dive so "
+"that the respiratory rates of different dives can be compared. The units for "
+"SAC is litres/min or cub ft/min."
+msgstr ""
+
+#. type: Named 'icon' AttributeList argument for style 'icon'
+#: user-manual.txt:2002
+#, no-wrap
+msgid "images/icons/EAD.jpg"
+msgstr ""
+
+#. type: Plain text
+#: user-manual.txt:2017
+msgid ""
+"Clicking this button displays the *Equivalent Air Depth (EAD)* for nitrox "
+"dives as well as the *Equivalent Narcotic Depth (END)* for trimix dives. "
+"These are numbers of importance to divers who use breathing gases other than "
+"air. Their values are dependent on the composition of the breathing gas.  "
+"The EAD is the depth of a hypothetical air dive that has the same partial "
+"pressure of nitrogen as the current depth of the nitrox dive at hand. A "
+"nitrox dive leads to the same decompression obligation as an air dive to the "
+"depth equalling the EAD. The END is the depth of a hypothetical air dive "
+"that has the same sum of partial pressures of the narcotic gases nitrogen "
+"and oxygen as the current trimix dive. A trimix diver can expect the same "
+"narcotic effect as a diver breathing air diving at a depth equalling the END."
+msgstr ""
+
+#. type: Plain text
+#: user-manual.txt:2019
+msgid ""
+"Figure (*B*) above shows an information box with a nearly complete set of "
+"data."
+msgstr ""
+
+#. type: Title ====
+#: user-manual.txt:2021
+#, no-wrap
+msgid "The Gas Pressure Bar Graph"
+msgstr ""
+
+#. type: Plain text
+#: user-manual.txt:2028
+msgid ""
+"On the left of the *Information Box* is a vertical bar graph indicating the "
+"pressures of the nitrogen (and other inert gases, e.g. helium, if "
+"applicable) that the diver was inhaling _at a particular instant during the "
+"dive_, indicated by the position of the cursor on the *Dive Profile*. The "
+"drawing on the left below indicates the meaning of the different parts of "
+"the Gas Pressure Bar Graph."
+msgstr ""
+
+#. type: Target for macro image
+#: user-manual.txt:2029
+#, no-wrap
+msgid "images/GasPressureBarGraph.jpg"
+msgstr ""
+
+#. type: Plain text
+#: user-manual.txt:2035
+msgid ""
+"The light green area indicates the total gas, with the top margin of the "
+"light green area indicating the total gas pressure inhaled by the diver and "
+"measured from the bottom of the graph to the top of the light green area. "
+"This pressure has a _relative_ value in the graph and does not indicate "
+"absolute pressure."
+msgstr ""
+
+#. type: Plain text
+#: user-manual.txt:2041
+msgid ""
+"The horizontal black line underneath the light green margin indicates the "
+"equilibrium pressure of the inert gases inhaled by the diver, usually "
+"nitrogen. In the case of trimix, it is the pressures of nitrogen and helium "
+"combined. In this example, the user is diving with EAN32, so the inert gas "
+"pressure is 68% of the distance from the bottom of the graph to the total "
+"gas pressure value."
+msgstr ""
+
+#. type: Plain text
+#: user-manual.txt:2045
+msgid ""
+"The dark green area at the bottom of the graph represents the pressures of "
+"inert gas in each of the 16 tissue compartments, following the Bühlmann "
+"algorithm, the fast tissues being on the left hand side."
+msgstr ""
+
+#. type: Plain text
+#: user-manual.txt:2050
+msgid ""
+"The top black horizontal line indicates the gradient factor that applies to "
+"the depth of the diver at the particular point on the *Dive Profile*. The "
+"appropriate gradient factor is an interpolation between the FGLow and GFHigh "
+"values specified in the Graph tab of the *Preferences Panel* of *Subsurface*."
+msgstr ""
+
+#. type: Plain text
+#: user-manual.txt:2054
+msgid ""
+"The bottom margin of the red area in the graph indicates the Bühlman-derived "
+"M-value, that is the pressure value of inert gases at which bubble formation "
+"is expected to be severe, resulting in decompression sickness."
+msgstr ""
+
+#. type: Plain text
+#: user-manual.txt:2057
+msgid ""
+"These five values are indicated on the left in the graph above. The way the "
+"Gas Pressure Bar Graph changes during a dive is indicated on the right hand "
+"side of the above figure for a diver using EAN32."
+msgstr ""
+
+#. type: Plain text
+#: user-manual.txt:2060
+msgid ""
+"Graph *A* indicates the situation at the start of a dive with diver at the "
+"surface. The pressures in all the tissue compartments are still at the "
+"equilibrium pressure because no diving has taken place."
+msgstr ""
+
+#. type: Plain text
+#: user-manual.txt:2063
+msgid ""
+"Graph *B* indicates the situation after a descent to 30 meters. Few of the "
+"tissue compartments have had time to respond to the descent, their gas "
+"pressures being far below the equilibrium gas pressure."
+msgstr ""
+
+#. type: Plain text
+#: user-manual.txt:2068
+msgid ""
+"Graph *C* represents the pressures after 30 minutes at 30 m. The fast "
+"compartments have attained equilibrium (i.e. they have reached the hight of "
+"the black line indicating the equilibrium pressure). The slower compartments "
+"(towards the right) have not reached equilibrium and are in the process of "
+"slowly increasing in pressure."
+msgstr ""
+
+#. type: Plain text
+#: user-manual.txt:2074
+msgid ""
+"Graph *D* shows the pressures after ascent to a depth of 4.5 meters. Since, "
+"during ascent, the total inhaled gas pressure has decreased strongly from 4 "
+"bar to 1.45 bar, the pressures in the different tissue compartments now "
+"exceed that of the total gas pressure and approaches the gradient factor "
+"value (i.e.  the top black horizontal line). Further ascent will result in "
+"exceeding the gradient factor value (GFHigh), endangering the diver."
+msgstr ""
+
+#. type: Plain text
+#: user-manual.txt:2079
+msgid ""
+"Graph *E* indicates the situation after remaining at 4.5 meters for 10 "
+"minutes. The fast compartments have decreased in pressure. As expected, the "
+"pressures in the slow compartments have not changed much.  The pressures in "
+"the fast compartments do not approach the GFHigh value any more and the "
+"diver is safer than in the situation indicated in graph *D*."
+msgstr ""
+
+#. type: Title ==
+#: user-manual.txt:2082
+#, no-wrap
+msgid "Organising the logbook (Manipulating groups of dives)"
+msgstr ""
+
+#. type: Title ===
+#: user-manual.txt:2084
+#, no-wrap
+msgid "The Dive List context menu"
+msgstr ""
+
+#. type: Plain text
+#: user-manual.txt:2089
+msgid ""
+"Many actions within _Subsurface_ are dependent on a context menu used mostly "
+"to manipulate groups of dives. The context menu is found by selecting a dive "
+"or a group of dives and then right-clicking."
+msgstr ""
+
+#. type: Target for macro image
+#: user-manual.txt:2090
+#, no-wrap
+msgid "images/ContextMenu.jpg"
+msgstr ""
+
+#. type: Plain text
+#: user-manual.txt:2093
+msgid "The context menu is used in many manipulations described below."
+msgstr ""
+
+#. type: Title ====
+#: user-manual.txt:2094
+#, no-wrap
+msgid "Customising the information showed in the *Dive List* panel"
+msgstr ""
+
+#. type: Target for macro image
+#: user-manual.txt:2096
+#, no-wrap
+msgid "images/DiveListOptions.jpg"
+msgstr ""
+
+#. type: Plain text
+#: user-manual.txt:2104
+msgid ""
+"The default information in the *Dive List* includes, for each dive, "
+"Dive_number, Date, Rating, Dive_depth, Dive_duration and Dive_location. This "
+"information can be controlled and changed by right-clicking on the header "
+"bar of the *Dive List*. For instance, a right-click on the 'Date' header "
+"brings up a list of items that can be shown in the dive list (see above). "
+"Select an item to be shown in the *Dive List* or to be deleted from the dive "
+"list, and the list is immediately updated accordingly. Preferences for "
+"information shown in the *Dive List* is saved and used when _Subsurface_ is "
+"re-opened."
+msgstr ""
+
+#. type: Title ====
+#: user-manual.txt:2105
+#, no-wrap
+msgid "Selecting dives from a particular dive site"
+msgstr ""
+
+#. type: Plain text
+#: user-manual.txt:2111
+msgid ""
+"Many divers have long dive lists and it may be difficult to locate all the "
+"dives at a particular site.  By pressing _Ctl-F_ on the keyboard, a text box "
+"is opened at the top left hand of the *Dive List*.  Type the name of a dive "
+"site in this text box and the *Dive List* is immediately filtered to show "
+"only the dives for that site."
+msgstr ""
+
+#. type: Title ===
+#: user-manual.txt:2113
+#, no-wrap
+msgid "Renumbering the dives"
+msgstr ""
+
+#. type: Plain text
+#: user-manual.txt:2125
+msgid ""
+"Dives are normally numbered incrementally from non-recent dives (low "
+"sequence numbers) to recent dives (having the highest sequence numbers). The "
+"numbering of the dives is not always consistent. For instance, when non-"
+"recent dives are added to the dive list the numbering does not automatically "
+"follow on because of the dives that are more recent in date/time than the "
+"newly-added dive with an older date/time. Therefore, one may sometimes need "
+"to renumber the dives.  This is performed by selecting (from the Main Menu) "
+"_Log -> Renumber_. Users are given a choice with respect to the lowest "
+"sequence number to be used.  Completing this operation results in new "
+"sequence numbers (based on date/time)  for the dives in the *Dive List* "
+"panel."
+msgstr ""
+
+#. type: Title ===
+#: user-manual.txt:2127
+#, no-wrap
+msgid "Grouping dives into trips and manipulating trips"
+msgstr ""
+
+#. type: Plain text
+#: user-manual.txt:2135
+msgid ""
+"For regular divers, the dive list can rapidly become very long. _Subsurface_ "
+"can group dives into _trips_. It performs this by grouping dives that have "
+"date/times that are not separated in time by more than two days, thus "
+"creating a single heading for each diving trip represented in the dive log. "
+"Below is an ungrouped dive list (*A*, on the left) as well as the "
+"corresponding grouped dive list comprising five dive trips (*B*, on the "
+"right):"
+msgstr ""
+
+#. type: Target for macro image
+#: user-manual.txt:2136
+#, no-wrap
+msgid "images/Group2.jpg"
+msgstr ""
+
+#. type: Plain text
+#: user-manual.txt:2142
+msgid ""
+"Grouping into trips allows a rapid way of accessing individual dives without "
+"having to scan a long lists of dives. In order to group the dives in a dive "
+"list, (from the Main Menu) users must select _Log -> Autogroup_. The *Dive "
+"List* panel now shows only the titles for the trips."
+msgstr ""
+
+#. type: Title ====
+#: user-manual.txt:2143
+#, no-wrap
+msgid "Editing the title and associated information for a particular trip"
+msgstr ""
+
+#. type: Plain text
+#: user-manual.txt:2156
+msgid ""
+"Normally, in the dive list, minimal information is included in the trip "
+"title.  More information about a trip can be added by selecting its trip "
+"title from the *Dive List*. This shows a *Trip Notes* tab in the *Dive "
+"Notes* panel. Here users can add or edit information about the date/time, "
+"the trip location and any other general comments about the trip as a whole "
+"(e.g. the dive company that was dived with, the general weather and surface "
+"conditions during the trip, etc.).  After entering this information, users "
+"should select *Save* from the buttons at the top right of the *Trip Notes* "
+"tab. The trip title in the *Dive List* panel should now reflect some of the "
+"edited information."
+msgstr ""
+
+#. type: Title ====
+#: user-manual.txt:2157
+#, no-wrap
+msgid "Viewing the dives during a particular trip"
+msgstr ""
+
+#. type: Plain text
+#: user-manual.txt:2162
+msgid ""
+"Once the dives have been grouped into trips, users can expand one or more "
+"trips by clicking the arrow-head on the left of each trip title. This "
+"expands the selected trip, revealing the individual dives performed during "
+"the trip."
+msgstr ""
+
+#. type: Title ====
+#: user-manual.txt:2163
+#, no-wrap
+msgid "Collapsing or expanding dive information for different trips"
+msgstr ""
+
+#. type: Plain text
+#: user-manual.txt:2169
+msgid ""
+"If a user right-clicks after selecting a particular trip in the dive list, "
+"the resulting context menu allows several possibilities to expand or "
+"collapse dives within trips. This includes expanding all trips, collapsing "
+"all trips and collapsing all trips except the selected one."
+msgstr ""
+
+#. type: Title ====
+#: user-manual.txt:2170
+#, no-wrap
+msgid "Merging dives from more than one trip into a single trip"
+msgstr ""
+
+#. type: Plain text
+#: user-manual.txt:2175
+msgid ""
+"By right-clicking on a selected trip title in the *Dive List* panel, a "
+"context menu shows up that allows the merging of trips by either merging of "
+"the selected trip with the trip below or with the trip above."
+msgstr ""
+
+#. type: Title ====
+#: user-manual.txt:2176
+#, no-wrap
+msgid "Splitting a single trip into more than one trip"
+msgstr ""
+
+#. type: Plain text
+#: user-manual.txt:2186
+msgid ""
+"If a trip includes five dives, the user can split this trip into two trips "
+"(trip 1: top 3 dives; trip 2: bottom 2 dives) by selecting and right-"
+"clicking the top three dives. The resulting context menu allows the user to "
+"create a new trip by choosing the option *Create new trip above*. The top "
+"three dives are then grouped into a separate trip. The figures below shows "
+"the selection and context menu on the left (A) and the completed action on "
+"the right (B):"
+msgstr ""
+
+#. type: Target for macro image
+#: user-manual.txt:2187
+#, no-wrap
+msgid "images/SplitDive3a.jpg"
+msgstr ""
+
+#. type: Title ===
+#: user-manual.txt:2189
+#, no-wrap
+msgid "Manipulating single dives"
+msgstr ""
+
+#. type: Title ====
+#: user-manual.txt:2191
+#, no-wrap
+msgid "Delete a dive from the dive log"
+msgstr ""
+
+#. type: Plain text
+#: user-manual.txt:2198
+msgid ""
+"Dives can be permanently deleted from the dive log by selecting and right-"
+"clicking them to bring up the context menu, and then selecting *Delete "
+"dive(s)*. Typically this would apply to a case where a user wishes to delete "
+"workshop calibration dives of the dive computer or dives of extremely short "
+"duration."
+msgstr ""
+
+#. type: Title ====
+#: user-manual.txt:2199
+#, no-wrap
+msgid "Unlink a dive from a trip"
+msgstr ""
+
+#. type: Plain text
+#: user-manual.txt:2206
+msgid ""
+"Users can unlink dives from the trip to which they belong. In order to do "
+"this, select and right-click the relevant dives to bring up the context "
+"menu. Then select the option *Remove dive(s)  from trip*. The dive(s) now "
+"appear immediately above the trip to which they belonged."
+msgstr ""
+
+#. type: Title ====
+#: user-manual.txt:2207
+#, no-wrap
+msgid "Add a dive to the trip immediately above"
+msgstr ""
+
+#. type: Plain text
+#: user-manual.txt:2214
+msgid ""
+"Selected dives can be moved from the trip to which they belong and placed "
+"within the trip immediately above the currently active trip. To do this, "
+"select and right-click the dive(s) to bring up the context menu, and then "
+"select *Add dive(s) to trip immediately above*."
+msgstr ""
+
+#. type: Title ====
+#: user-manual.txt:2215
+#, no-wrap
+msgid "Shift the start time of dive(s)"
+msgstr ""
+
+#. type: Plain text
+#: user-manual.txt:2226
+msgid ""
+"Sometimes it is necessary to adjust the start time of a dive. This may apply "
+"to situations where dives are performed in different time zones or when the "
+"dive computer has an erroneous time. In order to do this, user must select "
+"and right-click the dive(s) to be adjusted. This action brings up the "
+"context menu on which the *Shift times* option should be selected. User must "
+"then specify the time (in hours and minutes) by which the dives should be "
+"adjusted and click on the option indicating whether the time adjustment "
+"should be forwards or backwards."
+msgstr ""
+
+#. type: Title ====
+#: user-manual.txt:2227
+#, no-wrap
+msgid "Merge dives into a single dive"
+msgstr ""
+
+#. type: Plain text
+#: user-manual.txt:2237
+msgid ""
+"Sometimes a dive is briefly interrupted, e.g. if a diver returns to the "
+"surface for a few minutes, resulting in two or more dives being recorded by "
+"the dive computer and appearing as different dives in the *Dive List* panel. "
+"Users can merge these dives onto a single dive by selecting the appropriate "
+"dives, right-clicking them to bring up the context menu and then selecting "
+"*Merge selected dives*. It may be necessary to edit the dive information in "
+"the *Dive Notes* panel to reflect events or conditions that apply to the "
+"merged dive. The figure below shows the depth profile of two such dives that "
+"were merged:"
+msgstr ""
+
+#. type: Target for macro image
+#: user-manual.txt:2238
+#, no-wrap
+msgid "images/MergedDive.png"
+msgstr ""
+
+#. type: Title ===
+#: user-manual.txt:2241
+#, no-wrap
+msgid "Filtering the dive list"
+msgstr ""
+
+#. type: Plain text
+#: user-manual.txt:2247
+msgid ""
+"The dives in the *Dive List* panel can be filtered, that is, one can select "
+"only some of the dives based on their attributes, e.g. dive tags, dive site, "
+"dive master, buddy or protective clothing. For instance, filtering allows "
+"one to list the deep dives at a particular dive site, or otherwise the cave "
+"dives with a particular buddy."
+msgstr ""
+
+#. type: Plain text
+#: user-manual.txt:2256
+msgid ""
+"To open the filter, select _Log -> Filter divelist_ from the main menu. This "
+"opens the _Filter Panel_ at the top of the _Subsurface_ window. Three icons "
+"are located at the top right hand of the filter panel. The _Filter Panel_ "
+"can be reset (i.e. all current filters cleared) by selecting the *+*. The "
+"_Filter Panel_ may also be minimised by selecting the middle icon. When "
+"minimised, only these three icons are shown.  The panel can be maximised by "
+"clicking the icon that minimised the panel. The filter may also be reset and "
+"closed by selecting the button with the flag.  An example of the _Filter "
+"Panel_ is shown in the figure below."
+msgstr ""
+
+#. type: Target for macro image
+#: user-manual.txt:2258
+#, no-wrap
+msgid "images/Filterpanel.jpg"
+msgstr ""
+
+#. type: Plain text
+#: user-manual.txt:2268
+msgid ""
+"Four filter criteria may be used to filter the dive list: dive tags, person "
+"(buddy / dive master), dive site and dive suit, each of which is represented "
+"by a check list with check boxes. Above each check list is a second-level "
+"filter tool, allowing the listing of only some of the attributes within that "
+"check list. For instance, typing \"_ca_\" in the filter textbox above the "
+"tags check list results in the tags check list being reduced to \"_cave_\" "
+"and \"_cavern_\". Filtering of the check list enables the rapid finding of "
+"search terms for filtering the dive list."
+msgstr ""
+
+#. type: Plain text
+#: user-manual.txt:2276
+msgid ""
+"To activate filtering of the dive list, the check box of at least one item "
+"in one of the four check lists needs to be checked. The dive list is then "
+"shortened to include only the dives that pertain to the selection criteria "
+"specified in the check lists.  The four check lists work as a filter with "
+"_AND_ operators, Subsurface filters therefore for _cave_ as a tag AND _Joe "
+"Smith_ as a buddy; but the filters within a category are inclusive - "
+"filtering for _cave_ and _boat_ shows those dives that have either one or "
+"both of these tags."
+msgstr ""
+
+#. type: Title ==
+#: user-manual.txt:2278
+#, no-wrap
+msgid "Exporting the dive log or parts of the dive log"
+msgstr ""
+
+#. type: Plain text
+#: user-manual.txt:2284
+msgid ""
+"The export function can be reached by selecting _File -> Export_, which "
+"brings up the Export dialog. This dialog always gives two options: save ALL "
+"dives, or save only the dives selected in *Dive List* panel of _Subsurface_. "
+"Click the appropriate radio button (see images below)."
+msgstr ""
+
+#. type: Target for macro image
+#: user-manual.txt:2285
+#, no-wrap
+msgid "images/Export.jpg"
+msgstr ""
+
+#. type: Plain text
+#: user-manual.txt:2288
+msgid "A dive log or part of it can be saved in three formats:"
+msgstr ""
+
+#. type: Plain text
+#: user-manual.txt:2290
+msgid ""
+"_Subsurface XML_ format. This is the native format used by _Subsurface_."
+msgstr ""
+
+#. type: Plain text
+#: user-manual.txt:2294
+msgid ""
+"Universal Dive Data Format (_UDDF_). Refer to _http://uddf.org_ for more "
+"information.  UDDF is a generic format that enables communication among many "
+"dive computers and computer programs."
+msgstr ""
+
+#. type: Plain text
+#: user-manual.txt:2298
+msgid ""
+"_Divelogs.de_, an Internet-based dive log repository. In order to upload to "
+"_Divelogs.de_, one needs a user-ID as well as a password for _Divelogs.de_. "
+"Log into _http://en.divelogs.de_ and subscribe to this service in order to "
+"upload dive log data from _Subsurface_."
+msgstr ""
+
+#. type: Plain text
+#: user-manual.txt:2302
+msgid ""
+"_CSV_ format, that includes the most critical information of the dive "
+"profile. Included information of a dive is: dive number, date, time, "
+"duration, depth, temperature and pressure."
+msgstr ""
+
+#. type: Plain text
+#: user-manual.txt:2305
+msgid ""
+"_Worldmap_ format, an HTML file with a world map upon which each dive and "
+"some information about it are indicated. This map is not editable."
+msgstr ""
+
+#. type: Plain text
+#: user-manual.txt:2313
+msgid ""
+"_HTML_ format, in which the dive(s) are stored in HTML files, readable with "
+"an Internet browser. Most modern web browsers are supported, but JavaScript "
+"must be enabled. This generated HTML file is not intended to be edited by "
+"the users.  The HTML dive log contains most of the information and also "
+"contains a search option to search the dive log. HTML export is specified on "
+"the second tab of the Export dialog (image *B* above)."
+msgstr ""
+
+#. type: Plain text
+#: user-manual.txt:2315
+msgid "_General Settings_, under the HTML tab, provides the following options:"
+msgstr ""
+
+#. type: Plain text
+#: user-manual.txt:2323
+#, no-wrap
+msgid ""
+"** Subsurface Numbers: if this option is checked, the dive(s) are exported with the\n"
+"numbers associated with them in Subsurface, Otherwise the dive(s) will be numbered\n"
+"starting from 1.\n"
+"** Export Yearly Statistics: if this option is checked, a yearly statistics table will\n"
+"be attached with the HTML exports.\n"
+"** Export List only: a list of dives will only be exported and the detailed dive\n"
+"information will not be available.\n"
+msgstr ""
+
+#. type: Plain text
+#: user-manual.txt:2326
+msgid ""
+"Under _Style Options_ some style-related options are available like font "
+"size and theme."
+msgstr ""
+
+#. type: Plain text
+#: user-manual.txt:2329
+msgid ""
+"Export to other formats can be achieved through third party facilities, for "
+"instance _www.divelogs.de_."
+msgstr ""
+
+#. type: Title ==
+#: user-manual.txt:2331
+#, no-wrap
+msgid "Keeping a _Subsurface_ dive log in the Cloud"
+msgstr ""
+
+#. type: Plain text
+#: user-manual.txt:2344
+msgid ""
+"For each diver, dive log information is highly important. Not only is it a "
+"record of diving activities for one's own pleasure, but it is important "
+"information required for admission to further training courses or "
+"(sometimes) even diving sites. The security of the dive log is therefore "
+"critical. In order to have a dive log that is resistant to failure of a home "
+"computer hard drive, loss or theft of equipment, the Cloud is an obvious "
+"solution. This also has the added benefit that one can access one's dive log "
+"from anywhere in the world without having to carry it with oneself. For this "
+"reason, facilities such as _divelogs.de_ and _Diving Log_ offer facilities "
+"to store dive log information on the Internet. Although _Subsurface_ does "
+"not offer integrated Cloud storage of dive logs, it is simple to achieve "
+"this using several of the existing facilities on the Internet."
+msgstr ""
+
+#. type: Plain text
+#: user-manual.txt:2349
+msgid ""
+"For instance http://www.dropbox.com/[_Dropbox_] offers a free application "
+"that allows files on the Dropbox servers to be seen as a local folder on "
+"one's desktop computer."
+msgstr ""
+
+#. type: Target for macro image
+#: user-manual.txt:2350
+#, no-wrap
+msgid "images/Cloud.jpg"
+msgstr ""
+
+#. type: Plain text
+#: user-manual.txt:2359
+msgid ""
+"The _Dropbox_ program creates a copy of the _Dropbox_ Internet Cloud content "
+"on one's desktop computer. When the computer is connected to the Internet, "
+"the Internet content is automatically updated. Therefore both the _Open_ and "
+"_Save_ of dive logs are done using the local copy of the dive log in the "
+"local _Dropbox_ folder, so there's no need for a direct internet connection. "
+"If the local copy is modified, e.g. by adding a dive, the remote copy in the "
+"_Dropbox_ server in the Cloud will be automatically updated whenever "
+"Internet access is available."
+msgstr ""
+
+#. type: Plain text
+#: user-manual.txt:2366
+msgid ""
+"In this way a dive log in one's _Dropbox_ folder can be accessed seamlessly "
+"from the Internet and can be accessed from any place with Internet access. "
+"Currently there are no costs involved for this service. Dropbox (Windows, "
+"Mac and Linux) can be installed by accessing the http://www.dropbox.com/"
+"install[_Install Page on the Dropbox website_]"
+msgstr ""
+
+#. type: Plain text
+#: user-manual.txt:2372
+msgid ""
+"Alternatively one can use _Dropbox_ as a mechanism to backup one's dive log. "
+"To Store a dive log in the Cloud, select _File->Save as_ from the "
+"_Subsurface_ main menu, navigate to the _Dropbox_ folder and select the "
+"_Save_ button. To access the dive log in the Cloud, select _File->Open "
+"Logbook_ from the _Subsurface_ main menu and navigate to the dive log file "
+"in the _Dropbox_ folder and select the _Open_ button."
+msgstr ""
+
+#. type: Plain text
+#: user-manual.txt:2375
+msgid ""
+"Several paid services exist on the Internet (e.g. Google, Amazon) where the "
+"same process could be used for the Cloud-based storage of dive logs."
+msgstr ""
+
+#. type: Title ==
+#: user-manual.txt:2378
+#, no-wrap
+msgid "Printing a dive log"
+msgstr ""
+
+#. type: Plain text
+#: user-manual.txt:2382
+msgid ""
+"_Subsurface_ provides a simple interface to print a whole dive log or only a "
+"few selected dives, including dive profiles and other contextual information."
+msgstr ""
+
+#. type: Plain text
+#: user-manual.txt:2384
+msgid "Before printing, two decisions are required:"
+msgstr ""
+
+#. type: Plain text
+#: user-manual.txt:2387
+msgid ""
+"Should the whole dive log be printed or only part of it? If only part of the "
+"dive log is required, then the user must select the required dives from the "
+"*Dive List* panel."
+msgstr ""
+
+#. type: Plain text
+#: user-manual.txt:2389
+msgid ""
+"What gas partial pressure information is required on the dive profile? Users "
+"should select the appropriate toggle-buttons on the button bar to the left "
+"of the Dive Profile panel."
+msgstr ""
+
+#. type: Plain text
+#: user-manual.txt:2393
+msgid ""
+"Now the print options should be selected to match the user's needs. To do "
+"this, user should select _File->Print_ from the Main menu. The following "
+"dialogue appears (see the image on the left [A], below)."
+msgstr ""
+
+#. type: Target for macro image
+#: user-manual.txt:2394
+#, no-wrap
+msgid "images/PrintDiveLog.jpg"
+msgstr ""
+
+#. type: Plain text
+#: user-manual.txt:2397
+msgid "Under _Print type_ users need to select one of three options:"
+msgstr ""
+
+#. type: Plain text
+#: user-manual.txt:2399
+msgid ""
+"Print the complete Dive List: to do this, _Table Print_ should be selected."
+msgstr ""
+
+#. type: Plain text
+#: user-manual.txt:2401
+msgid ""
+"Print the selected dives (dive profiles and all other information) at 6 "
+"dives per printed page: to do this, users should select _6 dives per page_."
+msgstr ""
+
+#. type: Plain text
+#: user-manual.txt:2403
+msgid ""
+"Print the selected dives (dive profiles and all other information) at 2 "
+"dives per printed page: to do this, users should select _2 dives per page_."
+msgstr ""
+
+#. type: Plain text
+#: user-manual.txt:2405
+msgid ""
+"Print the selected dives (dive profiles and all other information) at 1 dive "
+"per printed page: to do this, users should select _1 dive per page_."
+msgstr ""
+
+#. type: Plain text
+#: user-manual.txt:2407
+msgid "Under _Print options_ users need to select:"
+msgstr ""
+
+#. type: Plain text
+#: user-manual.txt:2411
+msgid ""
+"Printing only the dives that have been selected from the dive list prior to "
+"activating the print dialogue, achieved by checking the box _Print only "
+"selected dives_."
+msgstr ""
+
+#. type: Plain text
+#: user-manual.txt:2412
+msgid ""
+"Printing in colour, achieved by checking the box with _Print in colour_."
+msgstr ""
+
+#. type: Plain text
+#: user-manual.txt:2419
+msgid ""
+"The _Ordering_ affects the layout of the page (or part of it) for each "
+"dive.  The dive profile could be printed at the top of each dive, with the "
+"textual information underneath, or it could be printed with the textual "
+"information at the top with the dive profile underneath. Users should select "
+"the appropriate option in the print dialogue. See the image below which has "
+"a layout with text below the dive profile."
+msgstr ""
+
+#. type: Plain text
+#: user-manual.txt:2423
+msgid ""
+"Users can _Preview_ the printed page by selecting the _Preview_ button on "
+"the dialogue. After preview, changes to the options in the print dialogue "
+"can be made, resulting in a layout that fits personal taste."
+msgstr ""
+
+#. type: Plain text
+#: user-manual.txt:2433
+msgid ""
+"Next, select the _Print_ button in the dialogue. This activates the regular "
+"print dialogue used by the user operating system (image [*B*] in the middle, "
+"above), allowing them to choose a printer and to set its properties (image "
+"[*C*] on the right, above).  It is important to set the print resolution of "
+"the printer to an appropriate value by changing the printer properties. "
+"Finally, one can print the dives. Below is a (rather small)  example of the "
+"output for one particular page."
+msgstr ""
+
+#. type: Target for macro image
+#: user-manual.txt:2434
+#, no-wrap
+msgid "images/Printpreview.jpg"
+msgstr ""
+
+#. type: Title ==
+#: user-manual.txt:2438
+#, no-wrap
+msgid "Setting user _Preferences_ for _Subsurface_"
+msgstr ""
+
+#. type: Plain text
+#: user-manual.txt:2446
+msgid ""
+"There are several settings within _Subsurface_ that the user can specify. "
+"These are found when selecting _File->Preferences_. The settings are "
+"performed in five groups: *Defaults*, *Units*, *Graph*, *Language* and "
+"*Network*. All five sections operate on the same principles: the user must "
+"specify the settings that are to be changed, then these changes are saved "
+"using the *Apply* button. After applying all the new settings users can then "
+"leave the settings panel by selecting *OK*."
+msgstr ""
+
+#. type: Title ===
+#: user-manual.txt:2447
+#, no-wrap
+msgid "Defaults"
+msgstr ""
+
+#. type: Plain text
+#: user-manual.txt:2450
+msgid "There are several settings in the *Defaults* panel:"
+msgstr ""
+
+#. type: Target for macro image
+#: user-manual.txt:2451
+#, no-wrap
+msgid "images/Pref1.jpg"
+msgstr ""
+
+#. type: Plain text
+#: user-manual.txt:2455
+#, no-wrap
+msgid ""
+"  ** *Lists and tables*: Here one can specify the font type and font size of the\n"
+"*Dive Table* panel. By decreasing the font size of the *Dive Table*, users can see more dives on a screen.\n"
+msgstr ""
+
+#. type: Plain text
+#: user-manual.txt:2460
+#, no-wrap
+msgid ""
+"  ** *Dives*: For the _Default Dive File_ one need to specify the directory and\n"
+"file name of one's\n"
+"electronic dive log book. This is a file with filename extension .xml. When\n"
+"launched, _Subsurface_ will automatically load the specified dive log book.\n"
+msgstr ""
+
+#. type: Plain text
+#: user-manual.txt:2465
+#, no-wrap
+msgid ""
+"  ** *Display invalid*:  Dives can be marked as invalid (when a user wishes to hide\n"
+"dives that he/she don't consider valid dives, e.g. pool dives, but still want to\n"
+"keep them in the dive log). This controls whether those dives are displayed in\n"
+"the dive list.\n"
+msgstr ""
+
+#. type: Plain text
+#: user-manual.txt:2468
+#, no-wrap
+msgid ""
+"  ** *Default cylinder*: Here users can specify the default cylinder listed in\n"
+"the *Equipment* tab of the *Dive Notes* panel.\n"
+msgstr ""
+
+#. type: Plain text
+#: user-manual.txt:2476
+#, no-wrap
+msgid ""
+"  ** *Animations*: Some actions in showing the dive profile are performed using\n"
+"animations. For instance, the axis values for depth and time change from dive to\n"
+"dive. When viewing a different dive, these changes in axis characteristics do not\n"
+"happen instantaneously, but are animated. The _Speed_ of animations can be controlled\n"
+"by setting this slider\n"
+"with faster animation speed to the left, with a 0 value representing no animation\n"
+"at all.\n"
+msgstr ""
+
+#. type: Plain text
+#: user-manual.txt:2481
+#, no-wrap
+msgid ""
+" ** *Subsurface web service*: When one subscribes to the <<S_Companion,Subsurface web service>>, a very\n"
+"long and hard-to-remember userID is issued. This is the place to save that userID. By\n"
+"checking the option _Save User ID locally?_, one ensures that a local copy of that userID\n"
+"is saved.\n"
+msgstr ""
+
+#. type: Plain text
+#: user-manual.txt:2484
+#, no-wrap
+msgid ""
+" ** *Clear all settings*: As indicated in the button below this heading, all settings are\n"
+"cleared and set to default values.\n"
+msgstr ""
+
+#. type: Title ===
+#: user-manual.txt:2485
+#, no-wrap
+msgid "Units"
+msgstr ""
+
+#. type: Target for macro image
+#: user-manual.txt:2486
+#, no-wrap
+msgid "images/Pref2.jpg"
+msgstr ""
+
+#. type: Plain text
+#: user-manual.txt:2493
+msgid ""
+"Here user can choose between metric and imperial units of depth, pressure, "
+"volume, temperature and mass. By selecting the Metric or Imperial radio "
+"button at the top, users can specify that all units are in the chosen "
+"measurement system.  Alternatively, if one selects the *Personalise* radio "
+"button, units can be selected independently, with some units in the metric "
+"system and others in imperial."
+msgstr ""
+
+#. type: Title ===
+#: user-manual.txt:2494
+#, no-wrap
+msgid "Graph"
+msgstr ""
+
+#. type: Target for macro image
+#: user-manual.txt:2495
+#, no-wrap
+msgid "images/Pref3.jpg"
+msgstr ""
+
+#. type: Plain text
+#: user-manual.txt:2499
+msgid "This panel allows two type of selections:"
+msgstr ""
+
+#. type: Plain text
+#: user-manual.txt:2507
+#, no-wrap
+msgid ""
+"*Show*: Here users can specify the amount of information shown as part of\n"
+"the dive profile:\n"
+"** Thresholds: _Subsurface_ can display the nitrogen, oxygen and the helium partial pressures during\n"
+"the dive. These are enabled using the toolbar on the left hand side of the *Dive Profile*\n"
+"panel. For each of these graphs users can specify a threshold value on the right-hand side of the\n"
+"Preferences panel. If any of the graphs go above this threshold level, the graph is\n"
+"highlighted in red, indicating that the threshold has been exceeded.\n"
+msgstr ""
+
+#. type: Plain text
+#: user-manual.txt:2512
+#, no-wrap
+msgid ""
+"** _Draw dive computer reported ceiling red_: This checkbox allows exactly what it says.\n"
+"Not all dive computers report ceiling values. If the dive computer does report it, it may differ\n"
+"from the ceilings calculated by _Subsurface_. This is because of the different algorithms and gradient factors available for calculating ceilings, as well as the dynamic way that a\n"
+"dive computer can calculate ceilings during a dive.\n"
+msgstr ""
+
+#. type: Plain text
+#: user-manual.txt:2514
+#, no-wrap
+msgid "** _Show unused cylinders in Equipment Tab_: This checkbox allows display of information about unused cylinders when viewing the *Equipment Tab*. Conversely, if this box is not checked, and any cylinders entered using the *Equipment Tab* are not used (e.g. there was no gas switch to such a cylinder), then these cylinders are omitted from that list.\n"
+msgstr ""
+
+#. type: Plain text
+#: user-manual.txt:2517
+#, no-wrap
+msgid ""
+"** _Show average depth_: Activating this checkbox causes _Subsurface_ to draw a red line across\n"
+"the dive profile, indicating the mean depth of the dive.\n"
+msgstr ""
+
+#. type: Plain text
+#: user-manual.txt:2519
+#, no-wrap
+msgid "*Misc*:\n"
+msgstr ""
+
+#. type: Plain text
+#: user-manual.txt:2531
+#, no-wrap
+msgid ""
+"** Gradient Factors:* Here users can set the _gradient factors_ used while diving. GF_Low is\n"
+"the gradient factor at depth and GF_High is used just below the surface.\n"
+"At intermediate depths gradient factors between GF_Low and GF_High are used.\n"
+"Gradient factors add conservatism to the nitrogen exposure during a dive, in a\n"
+"similar way that many dive computers have a conservatism setting. The lower\n"
+"the value of a gradient factor, the more conservative the calculations are with\n"
+"respect to nitrogen loading and the deeper the ascent ceilings are. Gradient\n"
+"factors of 20/60 are considered conservative and values of 60/90 are considered\n"
+"harsh. Checking *GFLow at max depth* box causes GF_Low to be used at the\n"
+"deepest depth of a dive. If this box is not checked, GF_Low is applied at\n"
+"all depths deeper than the first deco stop. For more information see:\n"
+msgstr ""
+
+#. type: Title ===
+#: user-manual.txt:2536
+#, no-wrap
+msgid "Language"
+msgstr ""
+
+#. type: Plain text
+#: user-manual.txt:2538
+msgid "Choose a language that _Subsurface_ will use."
+msgstr ""
+
+#. type: Target for macro image
+#: user-manual.txt:2539
+#, no-wrap
+msgid "images/Pref4.jpg"
+msgstr ""
+
+#. type: Plain text
+#: user-manual.txt:2549
+msgid ""
+"A checkbox allows one to use the _System Default_ language which in most "
+"cases will be the correct setting; with this _Subsurface_ simply runs in the "
+"same language / country settings as the underlying OS. If this is for some "
+"reason undesirable users can uncheck this checkbox and pick a language / "
+"country combination from the list of included localizations. The _Filter_ "
+"text box allows one to list similar languages. For instance there are "
+"several system variants of English or French. This particular preference "
+"requires a restart of _Subsurface_ to take effect."
+msgstr ""
+
+#. type: Title ===
+#: user-manual.txt:2550
+#, no-wrap
+msgid "Network"
+msgstr ""
+
+#. type: Plain text
+#: user-manual.txt:2552
+msgid ""
+"This panel facilitates communication between _Subsurface_ and data sources "
+"on the Internet."
+msgstr ""
+
+#. type: Target for macro image
+#: user-manual.txt:2553
+#, no-wrap
+msgid "images/Pref5.jpg"
+msgstr ""
+
+#. type: Plain text
+#: user-manual.txt:2566
+msgid ""
+"This is important, for instance, when _Subsurface_ needs to communicate with "
+"Internet services such as the <<S_Companion,_Subsurface Companion app_>> or "
+"data export/import from _Divelogs.de_. These Internet requirements are "
+"determined by one's type of connection to the Internet and by the Internet "
+"Service Provider (ISP) used.  One's ISP should provide the appropriate "
+"information.  If a proxy server is used for Internet access, the appropriate "
+"information needs to be provided here. The type of proxy needs to be "
+"selected from the dropdown list.  after which the IP address of the host and "
+"the appropriate port number should be provided. If the proxy server uses "
+"authentication, the appropriate userID and password also needs to be "
+"provided so that _Subsurface_ can automatically pass through the proxy "
+"server to access the Internet."
+msgstr ""
+
+#. type: Title ==
+#: user-manual.txt:2568
+#, no-wrap
+msgid "The _Subsurface_ dive planner"
+msgstr ""
+
+#. type: Plain text
+#: user-manual.txt:2572
+msgid ""
+"Dive planning is an advanced feature of _Subsurface_, accessible by "
+"selecting _Log -> Plan Dive_ from the main menu. It allows calculation of "
+"nitrogen load during a dive by using the Bühlmann ZH-L16 algorithm with the "
+"addition of gradient factors as implemented by Erik Baker."
+msgstr ""
+
+#. type: delimited block *
+#: user-manual.txt:2580
+msgid ""
+"The _Subsurface_ dive planner IS CURRENTLY EXPERIMENTAL and assumes the user "
+"is already familiar with the _Subsurface_ user interface. It is explicitly "
+"used under the following conditions:"
+msgstr ""
+
+#. type: delimited block *
+#: user-manual.txt:2583
+msgid ""
+"The user is conversant with dive planning and has the necessary training to "
+"perform dive planning."
+msgstr ""
+
+#. type: delimited block *
+#: user-manual.txt:2584
+msgid "The user plans dives within his/her certification limits."
+msgstr ""
+
+#. type: delimited block *
+#: user-manual.txt:2587
+msgid ""
+"Dive planning makes large assumptions about the characteristics of the "
+"_average person_ and cannot compensate for individual physiology or health "
+"or personal history or life style characteristics."
+msgstr ""
+
+#. type: delimited block *
+#: user-manual.txt:2588
+msgid ""
+"The safety of a dive plan depends heavily on the way in which the planner is "
+"used."
+msgstr ""
+
+#. type: delimited block *
+#: user-manual.txt:2589
+msgid "The user is familiar with the user interface of _Subsurface_."
+msgstr ""
+
+#. type: delimited block *
+#: user-manual.txt:2591
+msgid ""
+"A user who is not absolutely sure about any of the above requirements should "
+"not use this feature."
+msgstr ""
+
+#. type: Title ===
+#: user-manual.txt:2593
+#, no-wrap
+msgid "The _Subsurface_ dive planner screen"
+msgstr ""
+
+#. type: Plain text
+#: user-manual.txt:2598
+msgid ""
+"Like the _Subsurface_ dive log, the planner screen is divided into several "
+"sections (see image below). The *setup* parameters for a dive are entered "
+"into the several sections on the left hand side of the screen.  The setup is "
+"divided into several sections: Available Gases, Rates, Planning, Gas Options "
+"and Dive Notes."
+msgstr ""
+
+#. type: Plain text
+#: user-manual.txt:2602
+msgid ""
+"At the top right hand is a green *design panel* upon which the profile of "
+"the dive can be manipulated directly by dragging and clicking as explained "
+"below. This feature makes the _Subsurface_ dive planner unique in ease of "
+"use."
+msgstr ""
+
+#. type: Plain text
+#: user-manual.txt:2606
+msgid ""
+"At the bottom right is a text panel with a heading of _Dive Plan Details_. "
+"This is where the details of the dive plan are provided in a way that can "
+"easily be copied to other software. This is also where any warning messages "
+"about the dive plan are printed."
+msgstr ""
+
+#. type: Target for macro image
+#: user-manual.txt:2607
+#, no-wrap
+msgid "images/PlannerWindow1.jpg"
+msgstr ""
+
+#. type: Title ===
+#: user-manual.txt:2610
+#, no-wrap
+msgid "Initiating dive planning"
+msgstr ""
+
+#. type: Plain text
+#: user-manual.txt:2614
+msgid ""
+"The dive planner comprises two parts: *constructing a dive plan* and "
+"*evaluating* that dive plan. To perform dive planning, perform these steps:"
+msgstr ""
+
+#. type: Plain text
+#: user-manual.txt:2618
+msgid ""
+"Clear the existing dive log by creating a new planning log. This is achieved "
+"by selecting _File -> New logbook_ from the main menu. This way, dive plans "
+"are kept separate from the existing dive log of completed dives."
+msgstr ""
+
+#. type: Plain text
+#: user-manual.txt:2623
+msgid ""
+"In the top left-hand area of the screen, ensure that the constant dive "
+"parameters are appropriate. These are: Start date and time of the dive, "
+"Atmospheric Pressure and Altitude above sea level of the dive site. The "
+"atmospheric pressure can also be entered as an altitude in metres, assuming "
+"an atmospheric pressure of 1.013 bar."
+msgstr ""
+
+#. type: Plain text
+#: user-manual.txt:2632
+msgid ""
+"In the table labelled _Available Gases_, add the information of the "
+"cylinders to be used as well as the gas composition within that cylinder. "
+"This is done in a similar way as for <<S_CylinderData,providing cylinder "
+"data for dive logs>>. Choose the cylinder type by double clicking the "
+"cylinder type and using the dropdown list, then specify the work pressure of "
+"this cylinder. By leaving the oxygen concentration (O2%) filed empty, the "
+"dive gas is assumed to be air. Otherwise enter the oxygen and/or helium "
+"concentration in the boxes provided in this dialogue. Add additional "
+"cylinders by using the \"+\" icon to the top righthand of the dialogue."
+msgstr ""
+
+#. type: Plain text
+#: user-manual.txt:2635
+msgid ""
+"The dialogue indicating _Dive Planner Points_ is usually not used at this "
+"stage of the dive planning."
+msgstr ""
+
+#. type: Title ===
+#: user-manual.txt:2636
+#, no-wrap
+msgid "Managing nitrogen, oxygen and gas consumption"
+msgstr ""
+
+#. type: Plain text
+#: user-manual.txt:2639
+msgid "The planning is performed in three stages:"
+msgstr ""
+
+#. type: Plain text
+#: user-manual.txt:2649
+#, no-wrap
+msgid ""
+"*a) Nitrogen management*: This is performed by specifying the rates for descent and ascent,\n"
+"as well as the gradient factors (GFLow and GFHigh) under the headings _Rates_ and _Planning_\n"
+"to the bottom left of the planning screen. Initially, the GFHigh and GFLow values in the _Preferences_\n"
+"panel of _Subsurface_ is used. If these are changed within the planner (see _Gas Options_ within\n"
+"the planner), the new values are\n"
+"used without changing the original specifications in the _Preferences_. Gradient Factor settings strongly affect the calculated ceilings and their depths.\n"
+"A very low GFLow value brings about decompression stops early on during the dive.\n"
+" ** For more information about Gradient factors, see the section on xref:S_GradientFactors[Gradient Factor Preference settings].\n"
+"For more information external to this manual see:\n"
+msgstr ""
+
+#. type: Plain text
+#: user-manual.txt:2654
+#, no-wrap
+msgid ""
+" *** link:http://www.tek-dive.com/portal/upload/M-Values.pdf[Understanding M-values by Erik Baker, _Immersed_ Vol. 3, No. 3.]\n"
+" *** link:http://www.rebreatherworld.com/general-and-new-to-rebreather-articles/5037-gradient-factors-for-dummies.html[Gradient factors for dummies, by Kevin Watts]\n"
+" *** link:http://www.amazon.com/Deco-Divers-Decompression-Theory-Physiology/dp/1905492073/ref=sr_1_1?s=books&ie=UTF8&qid=1403932320&sr=1-1&keywords=deco+for+divers[_Deco for Divers_, by Mark Powell (2008). Aquapress] Southend-on-Sea, UK. ISBN 10: 1-905492-07-3.\n"
+"An excellent non-technical review.\n"
+msgstr ""
+
+#. type: Plain text
+#: user-manual.txt:2662
+#, no-wrap
+msgid ""
+" ** The ascent rate is critical for nitrogen off-gassing at the end of the dive and is specified\n"
+"for several depth ranges, utilising the average (or mean) depth as a yardstick. The mean depth\n"
+"of the dive plan is indicated on the dive profile in the green panel of the dive planner. Ascent rates\n"
+"at deeper levels are often in the range of 8-12 m/min, while ascent rates near the surface are\n"
+"often in the range of 4-9 m/min. The descent rate is also specified. If the option _Drop to first depth_\n"
+"is activated, then the descent phase of the planned dive will be at the maximal descent rate specified\n"
+"in the _Rates_ section of the dive setup.\n"
+msgstr ""
+
+#. type: Plain text
+#: user-manual.txt:2672
+#, no-wrap
+msgid ""
+"*b) Oxygen management*: In the *Gas Options* part of the dive specification, the maximum partial\n"
+"pressure for oxygen needs to be specified for the\n"
+"bottom part of the dive (_bottom po2_) as well as for the decompression part of the dive (_deco po2_).\n"
+"The most commonly\n"
+"used values are 1.4 bar for the bottom part of the dive and 1.6 bar for any decompression\n"
+"stages. Normally, a partial pressure of 1.6 bar is not exceeded. PO2 settings and the depth at which switching to a gas takes place can also be edited in the\n"
+"_Available Gases_ dialog. Normally the planner decides on switching to a new gas when, during\n"
+"ascent, the partial pressure of the new gas has decreased to 1.6 bar.\n"
+msgstr ""
+
+#. type: Plain text
+#: user-manual.txt:2687
+#, no-wrap
+msgid ""
+"*c) Gas management*: One needs keep within the limits of the amount of gas contained in the dive\n"
+"cylinder(s), allowing for an appropriate margin for safe return to the surface, possibly\n"
+"sharing with a buddy. Under the _Gas Options_ heading, specify the best (but conservative) estimate\n"
+"of your surface-equivalent air consumption (SAC, also termed RMV) in\n"
+"litres/min (for the time being, only SI units are supported).  Specify the SAC during the\n"
+"bottom part of the dive (_bottom SAC_) as well as during the decompression or safety stops of the\n"
+"dive (_deco SAC_). Values of 20-30 l/min are common. For good gas management, a thumbsuck guess\n"
+"is not sufficient and one needs to\n"
+"monitor one's gas consumption on a regular basis, dependent on different dive conditions and/or equipment.\n"
+"The planner will calculate the total volume of gas used during the dive and will issue a warning\n"
+"if one exceeds the total amount of gas available. Good practice demands that one does not dive to\n"
+"the limit of the gas supply but that an appropriate reserve is kept for unforeseen circumstances.\n"
+"For technical diving, this reserve can be up to 66% of the total available gas.\n"
+msgstr ""
+
+#. type: Plain text
+#: user-manual.txt:2698
+msgid ""
+"Now (at last) one can start the detailed time-depth planning of the dive. "
+"_Subsurface_ offers a unique graphical interface for performing this part of "
+"the planning. The mechanics of doing this is similar to hand-entering a dive "
+"profile in the dive log part of _Subsurface_. Upon activating the planner, a "
+"default dive of depth 15 m for 40 min is offered in the green design surface "
+"to the top right hand of the screen. The white dots (waypoints) on the "
+"profile can be dragged with a mouse. Create more waypoints by double-"
+"clicking on the profile line and ensuring that the profile reflects the "
+"intended dive. Drag the waypoints to represent the depth and duration of the "
+"dive.  If any of the management limits (for nitrogen, oxygen or gas) is "
+"exceeded, the surface above the dive profile changes from BLUE to RED."
+msgstr ""
+
+#. type: Plain text
+#: user-manual.txt:2711
+msgid ""
+"Each waypoint on the dive profile creates a _Dive Planner Point_ in the "
+"table on the left of the dive planner panel. Ensure that the _Used Gas_ "
+"value in each row of that table corresponds to one of the gas mixtures "
+"specified in the table with _Available Gases_ immediately above the Dive "
+"Planner Points. Add new waypoints until the main features of the dive have "
+"been completed, e.g. the bottom time segment and deep stops (if these are "
+"implemented). Leave the remaining waypoints on the ascent to _Subsurface_. "
+"In most cases _Subsurface_ computes additional way points in order to fulfil "
+"decompression requirements for that dive. A waypoint can be moved by "
+"selecting that waypoint and by using the arrow keys.  The waypoints listed "
+"in the _Dive Planner Points_ dialogue can be edited by hand in order to "
+"obtain a precise presentation of the dive plan. In fact, one can create the "
+"whole dive profile by editing the _Dive Planner Points_ dialog."
+msgstr ""
+
+#. type: Plain text
+#: user-manual.txt:2719
+msgid ""
+"Indicate any changes in gas cylinder used by indicating gas changes as "
+"explained in the section <<S_CreateProfile,hand-creating a dive profile>>. "
+"These changes should reflect the cylinders and gas compositions defined in "
+"the table with _Available Gases_.  If two or more gases are used, automatic "
+"gas switches will be suggested during the ascent to the surface. However, "
+"these changes can be deleted by right-clicking the gas change and by "
+"manually creating a gas change by right-clicking on the appropriate waypoint."
+msgstr ""
+
+#. type: Plain text
+#: user-manual.txt:2728
+msgid ""
+"A non-zero value in the \"CC set point\" column of the table of dive planner "
+"points indicates a valid setpoint for oxygen partial pressure and that the "
+"segment is dived using a closed circuit rebreather (CCR). If the last "
+"manually entered segment is a CCR segment, the decompression phase is "
+"computed assuming the diver uses a CCR with the specified set-point. If the "
+"last segment (however short) is on open circuit (OC, indicated by a zero set-"
+"point) the decompression is computed in OC mode. The planner only considers "
+"gas changes in OC mode."
+msgstr ""
+
+#. type: Plain text
+#: user-manual.txt:2731
+msgid ""
+"Below is an example of a dive plan to 45m using EAN26, followed by an ascent "
+"using EAN50 and using the settings as described above."
+msgstr ""
+
+#. type: Target for macro image
+#: user-manual.txt:2732
+#, no-wrap
+msgid "images/DivePlanner2.jpg"
+msgstr ""
+
+#. type: Plain text
+#: user-manual.txt:2737
+msgid ""
+"Once the above has been completed, one can save it by clicking the _Save_ "
+"button towards the bottom left of the green design panel. The saved dive "
+"plan will appear in the *Dive List* panel of _Subsurface_."
+msgstr ""
+
+#. type: Title ===
+#: user-manual.txt:2738
+#, no-wrap
+msgid "The dive plan details"
+msgstr ""
+
+#. type: Plain text
+#: user-manual.txt:2747
+msgid ""
+"On the bottom right of the dive planner, under _Dive Plan Details_, the "
+"exact details of the dive plan are provided. These details may be modified "
+"by checking any of the options under the _Dive Notes_ section of the dive "
+"planner, immediately to the left of the _Dive Plan Details_. If a _Verbatim "
+"diveplan_ is requested, a detailed sentence-level explanation of the dive "
+"plan is given. If any of the management specifications have been exceeded "
+"during the planning, a warning message is printed underneath the dive plan "
+"information."
+msgstr ""
+
+#. type: Plain text
+#: user-manual.txt:2752
+msgid ""
+"If the option _Display segment duration_ is checked, then the duration of "
+"each depth level is indicated in the _Dive Plan Details_. This duration "
+"INCLUDES the transition time to get to that level. However, if the _Display "
+"transition in deco_ option is checked, the transitions are shown separately "
+"from the segment durations at a particular level."
+msgstr ""
+
+#. type: Title ===
+#: user-manual.txt:2754
+#, no-wrap
+msgid "Modifying an existing dive plan"
+msgstr ""
+
+#. type: Plain text
+#: user-manual.txt:2761
+msgid ""
+"Normally, when a dive plan has been saved, it is accessible from the *Dive "
+"List*, like any other dive log. Within the *Dive List* there is not a way to "
+"change a saved dive plan.  To perform changes to a dive plan, select it on "
+"the *Dive List*. Then, in the main menu, select _Log -> Re-plan dive_. This "
+"will open the selected dive plan within the dive planner, allowing changes "
+"to be made and saved as usual."
+msgstr ""
+
+#. type: Plain text
+#: user-manual.txt:2767
+msgid ""
+"In addition there is the option \"Save new\". This keeps the original "
+"planned dive and adds a (possibly modified) copy to the dive list. If that "
+"copy is saved with the same start time as the original, the two dives are "
+"considered two versions of the same dive and do not influence other each "
+"during decompression calculation (see next section)."
+msgstr ""
+
+#. type: Title ===
+#: user-manual.txt:2768
+#, no-wrap
+msgid "Planning for repetitive dives"
+msgstr ""
+
+#. type: Plain text
+#: user-manual.txt:2775
+msgid ""
+"Repetitive dives can easily be planned if the dates and start times of the "
+"repetitive dive set is specified appropriately in the top left-hand _Start "
+"Time_ field. _Subsurface_ calculates the gas loading figures correctly and "
+"the effect of the first dive is evaluated on later dives."
+msgstr ""
+
+#. type: Plain text
+#: user-manual.txt:2781
+msgid ""
+"If one has just completed a long/deep dive and is planning another dive, "
+"then highlight, in the *Dive List*, the dive that has just been completed "
+"and then activate the planner. Depending on the start time of the planned "
+"dive, the planner takes into account the gas loading incurred during the "
+"completed dive and allows planning within these limitations."
+msgstr ""
+
+#. type: Plain text
+#: user-manual.txt:2786
+msgid ""
+"If only a few standard configurations are used (e.g. in GUE), then a "
+"template dive can be created conforming to one of the configurations. If one "
+"now wishes to plan a dive using this configuration, just highlight the "
+"template dive in the *Dive List* and activate the planner: the planner takes "
+"into account the configuration in the highlighted dive."
+msgstr ""
+
+#. type: Title ===
+#: user-manual.txt:2787
+#, no-wrap
+msgid "Printing the dive plan"
+msgstr ""
+
+#. type: Plain text
+#: user-manual.txt:2792
+msgid ""
+"Selecting the _Print_ button in the planner allows printing of the _Dive "
+"Plan Details_ for wet notes. Alternatively one can cut and paste the _Dive "
+"Plan Details_ for inclusion in a text file or word processing document."
+msgstr ""
+
+#. type: Plain text
+#: user-manual.txt:2802
+msgid ""
+"Dive plans have many characteristics in common with dive logs (dive profile, "
+"dive notes, etc).  After a dive plan has been saved, the dive details and "
+"gas calculations are saved in the *Dive Notes* tab. While a dive plan is "
+"being designed, it can be printed using the _Print_ button in the dive "
+"planner. This prints the dive details and gas calculations in the _Dive Plan "
+"Details_ panel of the dive planner. However, after the plan has been saved, "
+"it is represented in a way very similar to a dive log and the gas "
+"calculations cannot be accessed in the same way as during the planning "
+"process. The only way to print the dive plan is to use the _File->Print_ "
+"facility on the main menu in the same way as for dive logs or by copy and "
+"paste to a word processor."
+msgstr ""
+
+#. type: Title ==
+#: user-manual.txt:2804
+#, no-wrap
+msgid "Configuring a dive computer"
+msgstr ""
+
+#. type: Plain text
+#: user-manual.txt:2812
+msgid ""
+"_Subsurface_ enables one to configure a dive computer. Currently the "
+"Heinrichs-Weikamp (OSTC 2, OSTC 3) and Suunto Vyper (Stinger, Mosquito, D3, "
+"Vyper, Vytec, Cobra, Gekko and Zoop) family of dive computers are supported. "
+"A large number of settings of these dive computers can be read and changed "
+"to different values. As a first step, ensure that the appropriate hardware "
+"driver is installed for the dive computer and that the device name of the "
+"dive computer is known.  See "
+"<<_appendix_a_operating_system_specific_information_for_importing_dive_information_from_a_dive_computer,"
+"APPENDIX A>> for information on how to do this."
+msgstr ""
+
+#. type: Plain text
+#: user-manual.txt:2817
+msgid ""
+"Once the dive computer is connected to the _Subsurface_ computer, select "
+"_File->Configure dive computer_ from the _Main Menu_. Provide the "
+"appropriate device name in the text box at the top of the configuration "
+"panel that opens and select the appropriate dive computer model from the "
+"panel on the lefthand (see image below)."
+msgstr ""
+
+#. type: Target for macro image
+#: user-manual.txt:2818
+#, no-wrap
+msgid "images/Configure_dc_f20.jpg"
+msgstr ""
+
+#. type: Plain text
+#: user-manual.txt:2821
+msgid ""
+"Using the appropriate buttons on the configuration panel, the following "
+"actions can be performed:"
+msgstr ""
+
+#. type: Plain text
+#: user-manual.txt:2824
+#, no-wrap
+msgid ""
+"*Retrieve available details*. This loads the existing configuration from the dive computer\n"
+"to _Subsurface_, showing this in the configuration panel.\n"
+msgstr ""
+
+#. type: Plain text
+#: user-manual.txt:2826
+#, no-wrap
+msgid ""
+"*Save changes to device*. This changes the configuration of the\n"
+"dive computer to correspond to the information shown in the configuration panel.\n"
+msgstr ""
+
+#. type: Plain text
+#: user-manual.txt:2828
+#, no-wrap
+msgid ""
+"*Backup*. This saves the configuration data to a file. _Subsurface_ asks for\n"
+"a file location and file name for the saved information.\n"
+msgstr ""
+
+#. type: Plain text
+#: user-manual.txt:2830
+#, no-wrap
+msgid ""
+"*Restore backup*. This loads the information from a backup file and displays it\n"
+"in the configuration panel.\n"
+msgstr ""
+
+#. type: Plain text
+#: user-manual.txt:2832
+#, no-wrap
+msgid ""
+"*Update firmware*. If new firmware is available for the dive computer, this is\n"
+"loaded into the dive computer.\n"
+msgstr ""
+
+#. type: Title ==
+#: user-manual.txt:2833
+#, no-wrap
+msgid "Description of the Subsurface Main Menu items"
+msgstr ""
+
+#. type: Plain text
+#: user-manual.txt:2838
+msgid ""
+"This section describes the functions and operation of the items in the Main "
+"Menu of Subsurface. Several of the items below are links to sections of this "
+"manual dealing with the appropriate operations."
+msgstr ""
+
+#. type: Title ===
+#: user-manual.txt:2839
+#, no-wrap
+msgid "File"
+msgstr ""
+
+#. type: Plain text
+#: user-manual.txt:2842
+msgid ""
+"<<S_NewLogbook,_New Logbook_>> - Close the currently open dive logbook and "
+"clear all dive information."
+msgstr ""
+
+#. type: Plain text
+#: user-manual.txt:2844
+msgid ""
+"_Open logbook_ - This opens the file manager in order to select a dive "
+"logbook to open."
+msgstr ""
+
+#. type: Plain text
+#: user-manual.txt:2845
+msgid "_Save_ - Save the dive logbook that is currently open."
+msgstr ""
+
+#. type: Plain text
+#: user-manual.txt:2846
+msgid "_Save as_ - Save the current logbook under a different file name."
+msgstr ""
+
+#. type: Plain text
+#: user-manual.txt:2847
+msgid "_Close_ - Close the dive logbook that is currently open."
+msgstr ""
+
+#. type: Plain text
+#: user-manual.txt:2849
+msgid ""
+"<<S_ExportLog,_Export_>> - Export the currently open dive logbook (or the "
+"selected dives in the logbook) to one of several formats."
+msgstr ""
+
+#. type: Plain text
+#: user-manual.txt:2850
+msgid "<<S_PrintDivelog,_Print_>> - Print the currently open logbook."
+msgstr ""
+
+#. type: Plain text
+#: user-manual.txt:2851
+msgid "<<S_Preferences,_Preferences_>> - Set the _Subsurface_ preferences."
+msgstr ""
+
+#. type: Plain text
+#: user-manual.txt:2852
+msgid ""
+"<<S_Configure,_Configure dive computer_>> - Edit the configuration of a dive "
+"computer."
+msgstr ""
+
+#. type: Plain text
+#: user-manual.txt:2853
+msgid "_Quit_ - Quit _Subsurface_."
+msgstr ""
+
+#. type: Title ===
+#: user-manual.txt:2854
+#, no-wrap
+msgid "Import"
+msgstr ""
+
+#. type: Plain text
+#: user-manual.txt:2857
+msgid ""
+"<<S_ImportDiveComputer,_Import from dive computer_>> - Import dive "
+"information from a dive computer."
+msgstr ""
+
+#. type: Plain text
+#: user-manual.txt:2859
+msgid ""
+"<<Unified_import,_Import Log Files_>> - Import dive information from a file "
+"in in a _Subsurface_-compatible format."
+msgstr ""
+
+#. type: Plain text
+#: user-manual.txt:2861
+msgid ""
+"<<S_Companion,_Import GPS data from Subsurface web service_>> - Load GPS "
+"coordinates from the _Subsurface_ mobile phone app."
+msgstr ""
+
+#. type: Plain text
+#: user-manual.txt:2863
+msgid ""
+"<<S_ImportingDivelogsDe,_Import from Divelogs.de_>> - Import dive "
+"information from _www.Divelogs.de_."
+msgstr ""
+
+#. type: Title ===
+#: user-manual.txt:2864
+#, no-wrap
+msgid "Log"
+msgstr ""
+
+#. type: Plain text
+#: user-manual.txt:2866
+msgid ""
+"<<S_EnterData,_Add Dive_>> - Manually add a new dive to the *Dive List* "
+"panel."
+msgstr ""
+
+#. type: Plain text
+#: user-manual.txt:2867
+msgid ""
+"<<S_DivePlanner,_Plan Dive_>> - This feature allows the planning of dives."
+msgstr ""
+
+#. type: Plain text
+#: user-manual.txt:2868
+msgid ""
+"<<S_Replan,_Re-plan dive_>> - Edit a dive plan that has been saved into the "
+"*Dive List*."
+msgstr ""
+
+#. type: Plain text
+#: user-manual.txt:2870
+msgid ""
+"<<S_CopyComponents,_Copy dive components_>> - By selecting this option, one "
+"can copy information from several fields of a dive log onto the clipboard."
+msgstr ""
+
+#. type: Plain text
+#: user-manual.txt:2871
+msgid ""
+"_Paste dive components_ - Paste, into the selected dives in the *Dive List*,"
+msgstr ""
+
+#. type: Plain text
+#: user-manual.txt:2872
+msgid "the information copied using the _Copy dive components_ option."
+msgstr ""
+
+#. type: Plain text
+#: user-manual.txt:2874
+msgid ""
+"<<S_Renumber,_Renumber_>> - Renumber the dives listed in the *Dive List* "
+"panel."
+msgstr ""
+
+#. type: Plain text
+#: user-manual.txt:2876
+msgid ""
+"<<S_Group,_Auto Group_>> - Group the dives in the *Dive List* panel into "
+"dive trips."
+msgstr ""
+
+#. type: Plain text
+#: user-manual.txt:2877
+msgid ""
+"<<S_DeviceNames,_Edit Device Names_>> - Edit the names of dive computers to "
+"facilitate your logs."
+msgstr ""
+
+#. type: Plain text
+#: user-manual.txt:2878
+msgid ""
+"<<S_Filter,_Filter divelist_>> - Select only some dives, based on specific "
+"tags or dive criteria."
+msgstr ""
+
+#. type: Title ===
+#: user-manual.txt:2879
+#, no-wrap
+msgid "View"
+msgstr ""
+
+#. type: Plain text
+#: user-manual.txt:2882
+msgid ""
+"<<S_ViewPanels,_All_>> - View the four main _Subsurface_ panels "
+"simmultaneously."
+msgstr ""
+
+#. type: Plain text
+#: user-manual.txt:2883
+msgid "<<S_ViewPanels,_Dive List_>> - View only the *Dive List* panel."
+msgstr ""
+
+#. type: Plain text
+#: user-manual.txt:2884
+msgid "<<S_ViewPanels,_Profile_>> - View only the *Dive Profile* panel."
+msgstr ""
+
+#. type: Plain text
+#: user-manual.txt:2885
+msgid "<<S_ViewPanels,_Info_>> - View only the *Dive Notes* panel."
+msgstr ""
+
+#. type: Plain text
+#: user-manual.txt:2886
+msgid "<<S_ViewPanels,_Globe_>> - View only the *World Map* panel."
+msgstr ""
+
+#. type: Plain text
+#: user-manual.txt:2888
+msgid ""
+"_Yearly Statistics_ - Display summary statistics about dives during this and "
+"past years."
+msgstr ""
+
+#. type: Plain text
+#: user-manual.txt:2889
+msgid "_Prev DC_ - Switch to previous dive computer."
+msgstr ""
+
+#. type: Plain text
+#: user-manual.txt:2890
+msgid "_Next DC_ - Switch to next dive computer."
+msgstr ""
+
+#. type: Plain text
+#: user-manual.txt:2891
+msgid "_Full Screen_ - Toggles Full Screen mode."
+msgstr ""
+
+#. type: Title ===
+#: user-manual.txt:2892
+#, no-wrap
+msgid "Help"
+msgstr ""
+
+#. type: Plain text
+#: user-manual.txt:2895
+msgid ""
+"_About Subsurface_ - Show a panel with the version number of _Subsurface_ as "
+"well as licensing information."
+msgstr ""
+
+#. type: Plain text
+#: user-manual.txt:2897
+msgid ""
+"_Check for updates_ - Find out whether a newer version of Subsurface is "
+"available on the http://subsurface-divelog.org/[_Subsurface_ web site]."
+msgstr ""
+
+#. type: Plain text
+#: user-manual.txt:2898
+msgid "_User Manual_ - Open a window showing this user manual."
+msgstr ""
+
+#. type: Title ==
+#: user-manual.txt:2900
+#, no-wrap
+msgid "APPENDIX A: Operating system specific information for importing dive information from a dive computer."
+msgstr ""
+
+#. type: Title ===
+#: user-manual.txt:2902
+#, no-wrap
+msgid "Make sure that the OS has the required drivers installed"
+msgstr ""
+
+#. type: Named 'icon' AttributeList argument for style 'icon'
+#: user-manual.txt:2903
+#, no-wrap
+msgid "images/icons/drivers.jpg"
+msgstr ""
+
+#. type: Plain text
+#: user-manual.txt:2908
+msgid ""
+"The operating system of the desktop computer needs the appropriate drivers "
+"in order to communicate with the dive computer in whichever way the dive "
+"computer prefers (e.g. bluetooth, USB, infra-red)."
+msgstr ""
+
+#. type: Plain text
+#: user-manual.txt:2914
+msgid ""
+"On Linux users need to have the correct kernel module loaded. Most "
+"distributions will do this automatically, so the user does not need to load "
+"kernel modules. However, some communication protocols require an additional "
+"driver, especially for rarely used technology such as infra-red."
+msgstr ""
+
+#. type: Plain text
+#: user-manual.txt:2918
+msgid ""
+"On Windows, the OS should offer to download the correct driver once the user "
+"connects the dive computer to the USB port and operating system sees the "
+"equipment for the first time."
+msgstr ""
+
+#. type: Plain text
+#: user-manual.txt:2925
+msgid ""
+"On a Mac users sometimes have to manually hunt for the correct driver. For "
+"example the correct driver for the Mares Puck devices or any other dive "
+"computer using a USB-to-serial interface based on the Silicon Labs CP2101 or "
+"similar chip can be found as _Mac_OSX_VCP_Driver.zip_ at the http://www."
+"silabs.com/support/pages/document-library.aspx?p=Interface&f=USB"
+"%20Bridges&pn=CP2101[Silicon Labs document and software repository]."
+msgstr ""
+
+#. type: Title ===
+#: user-manual.txt:2927
+#, no-wrap
+msgid "How to Find the Device Name for USB devices and set its write permission"
+msgstr ""
+
+#. type: Named 'icon' AttributeList argument for style 'icon'
+#: user-manual.txt:2928
+#, no-wrap
+msgid "images/icons/usb.jpg"
+msgstr ""
+
+#. type: Plain text
+#: user-manual.txt:2936
+msgid ""
+"When a user connects the dive computer by using a USB connector, usually "
+"_Subsurface_ will either propose a drop down list that contains the correct "
+"device name (or mount point for the Uemis Zurich), or it will disable the "
+"device select drop down if no device name is needed at all. In the rare "
+"cases where this doesn't work, here are some suggestions of ways to find out "
+"what the device name is:"
+msgstr ""
+
+#. type: Block title
+#: user-manual.txt:2937 user-manual.txt:3020
+#, no-wrap
+msgid "On Windows:"
+msgstr ""
+
+#. type: Plain text
+#: user-manual.txt:2941
+msgid ""
+"Simply try COM1, COM2, etc. The drop down list should contain all connected "
+"COM devices."
+msgstr ""
+
+#. type: Block title
+#: user-manual.txt:2942 user-manual.txt:3035
+#, no-wrap
+msgid "On MacOS:"
+msgstr ""
+
+#. type: Plain text
+#: user-manual.txt:2945
+msgid "The drop down box should find all connected dive computers."
+msgstr ""
+
+#. type: Block title
+#: user-manual.txt:2946
+#, no-wrap
+msgid "On Linux:"
+msgstr ""
+
+#. type: Plain text
+#: user-manual.txt:2949
+msgid "There is a definitive way to find the port:"
+msgstr ""
+
+#. type: Plain text
+#: user-manual.txt:2951
+msgid "Disconnect the USB cable from the dive computer"
+msgstr ""
+
+#. type: Plain text
+#: user-manual.txt:2952
+msgid "Open a terminal"
+msgstr ""
+
+#. type: Plain text
+#: user-manual.txt:2953 user-manual.txt:2955
+msgid "Type the command: 'dmesg' and press enter"
+msgstr ""
+
+#. type: Plain text
+#: user-manual.txt:2954
+msgid "Plug in the USB cable of the dive computer"
+msgstr ""
+
+#. type: Plain text
+#: user-manual.txt:2957
+msgid "A message similar to this one should appear:"
+msgstr ""
+
+#. type: Plain text
+#: user-manual.txt:2973
+#, no-wrap
+msgid ""
+"\tusb 2-1.1: new full speed USB device number 14 using ehci_hcd\n"
+"\tusbcore: registered new interface driver usbserial\n"
+"\tUSB Serial support registered for generic\n"
+"\tusbcore: registered new interface driver usbserial_generic\n"
+"\tusbserial: USB Serial Driver core\n"
+"\tUSB Serial support registered for FTDI USB Serial Device\n"
+"\tftdi_sio 2-1.1:1.0: FTDI USB Serial Device converter detected\n"
+"\tusb 2-1.1: Detected FT232BM\n"
+"\tusb 2-1.1: Number of endpoints 2\n"
+"\tusb 2-1.1: Endpoint 1 MaxPacketSize 64\n"
+"\tusb 2-1.1: Endpoint 2 MaxPacketSize 64\n"
+"\tusb 2-1.1: Setting MaxPacketSize 64\n"
+"\tusb 2-1.1: FTDI USB Serial Device converter now attached to ttyUSB3\n"
+"\tusbcore: registered new interface driver ftdi_sio\n"
+"\tftdi_sio: v1.6.0:USB FTDI Serial Converters Driver\n"
+msgstr ""
+
+#. type: Plain text
+#: user-manual.txt:2978
+msgid ""
+"The third line from the bottom shows that the FTDI USB adapter is detected "
+"and connected to +ttyUSB3+. This information can now be used in the import "
+"settings as +/dev/ttyUSB3+ which directs Subsurface to the correct USB port."
+msgstr ""
+
+#. type: Plain text
+#: user-manual.txt:2980
+msgid "Ensuring that the user has write permission to the USB serial port:"
+msgstr ""
+
+#. type: Plain text
+#: user-manual.txt:2986
+msgid ""
+"On Unix-like operating systems the USB ports can only be accessed by users "
+"who are members of the +dialout+ group. If one is not root, one may not be a "
+"member of that group and will not be able to use the USB port. Let us assume "
+"one's username is 'johnB'."
+msgstr ""
+
+#. type: Plain text
+#: user-manual.txt:2990
+msgid ""
+"As root, type: +usermod -a -G dialout johnB+ (Ubuntu users: +sudo usermod -a "
+"-G dialout johnB+)  This makes johnB a member of the +dialout+ group."
+msgstr ""
+
+#. type: Plain text
+#: user-manual.txt:2995
+#, no-wrap
+msgid ""
+"Type: +id johnB+     This lists all the groups that johnB belongs to and\n"
+"verifies that\n"
+"the appropriate group membership has been created. The +dialout+ group should\n"
+"be listed\n"
+"among the different IDs.\n"
+msgstr ""
+
+#. type: Plain text
+#: user-manual.txt:2997
+#, no-wrap
+msgid ""
+"Under some circumstances this change takes only effect (eg. on Ubuntu) after\n"
+"one logs out and then logs in again.\n"
+msgstr ""
+
+#. type: Plain text
+#: user-manual.txt:3002
+msgid ""
+"With the appropriate device name (e.g. +dev/ttyUSB3+) and with write "
+"permission to the USB port, the dive computer interface can connect and one "
+"should be able to import dives."
+msgstr ""
+
+#. type: Title ===
+#: user-manual.txt:3004
+#, no-wrap
+msgid "Setting up bluetooth enabled devices"
+msgstr ""
+
+#. type: Named 'icon' AttributeList argument for style 'icon'
+#: user-manual.txt:3005
+#, no-wrap
+msgid "images/icons/bluetooth.jpg"
+msgstr ""
+
+#. type: Plain text
+#: user-manual.txt:3011
+msgid ""
+"For dive computers communicating through bluetooth like the Heinrichs "
+"Weikamp Frog or the Shearwater Predator and Petrel there is a different "
+"procedure to get the devices name to communicate with _Subsurface_. Follow "
+"these steps:"
+msgstr ""
+
+#. type: Plain text
+#: user-manual.txt:3013
+#, no-wrap
+msgid "*For the dive computer, after enabling Bluetooth, ensure it is in Upload mode.*\n"
+msgstr ""
+
+#. type: Plain text
+#: user-manual.txt:3017
+msgid ""
+"For Bluetooth pairing of the dive computer, refer to the manufacturer's user "
+"guide. When using a Shearwater Predator/Petrel, select _Dive Log -> Upload "
+"Log_ and wait for the _Wait PC_ message."
+msgstr ""
+
+#. type: Plain text
+#: user-manual.txt:3019
+#, no-wrap
+msgid "*Pair the _Subsurface_ computer with the dive computer.*\n"
+msgstr ""
+
+#. type: Plain text
+#: user-manual.txt:3028
+msgid ""
+"Bluetooth is most likely already enabled. For pairing with the dive computer "
+"choose _Control Panel->Bluetooth Devices->Add Wireless Device_.  This should "
+"bring up a dialog showing your dive computer (in Bluetooth mode) and "
+"allowing pairing. Right click on it and choose _Properties->COM Ports_ to "
+"identify the port used for your dive computer. If there are several ports "
+"listed, use the one saying \"Outgoing\" instead of \"Incoming\"."
+msgstr ""
+
+#. type: Plain text
+#: user-manual.txt:3031
+msgid ""
+"For downloading to _Subsurface_, the _Subsurface_ drop-down list should "
+"contain this COM port already. If not, enter it manually."
+msgstr ""
+
+#. type: Plain text
+#: user-manual.txt:3034
+msgid ""
+"Note: If there are issues afterwards when downloading from the dive computer "
+"using other software, remove the existing pairing with the dive computer."
+msgstr ""
+
+#. type: Plain text
+#: user-manual.txt:3041
+msgid ""
+"Click on the Bluetooth symbol in the menu bar and select _Set up Bluetooth "
+"Device..._. The dive computer should then show up in the list of devices. "
+"Select it and go through the pairing process. This step should only be "
+"needed once for initial setup."
+msgstr ""
+
+#. type: Plain text
+#: user-manual.txt:3044
+msgid ""
+"Once the pairing is completed the correct device is shown in the 'Device or "
+"Mount Point' drop-down in the _Subsurface_ *Import* dialog."
+msgstr ""
+
+#. type: Block title
+#: user-manual.txt:3045
+#, no-wrap
+msgid "On Linux"
+msgstr ""
+
+#. type: Plain text
+#: user-manual.txt:3053
+msgid ""
+"Ensure Bluetooth is enabled on the _Subsurface_ computer.  On most common "
+"distributions this should be true out of the box and pairing should be "
+"straight forward. For instance, Gnome3 shows a Bluetooth icon in the upper "
+"right corner of the desktop where one selects 'Set up New Device'. This "
+"should show a dialog where one can select the dive computer (which already "
+"should be in Bluetooth mode) and pair it.  If a PIN is required, try "
+"manually setting '0000'."
+msgstr ""
+
+#. type: Plain text
+#: user-manual.txt:3060
+msgid ""
+"In the rare cases where the above is not true, then depending on your "
+"system, try +initd+ or +systemd+. This might be different and also involve "
+"loading modules specific to your hardware. In case your system is running "
+"+systemd+, manually run +systemctl start bluetooth.service+ to enable it, in "
+"case of +initd+, run something like +rc.config start bluetoothd+ or +/etc/"
+"init.d/bluetooth start+."
+msgstr ""
+
+#. type: Plain text
+#: user-manual.txt:3062
+msgid "One may also use a manual approach by using such commands:"
+msgstr ""
+
+#. type: Plain text
+#: user-manual.txt:3067
+msgid ""
+"+hciconfig+ shows the Bluetooth devices available on your computer (not dive "
+"computer), most likely one will see a hci0, if not try +hcitool -a+ to see "
+"inactive devices and run +sudo hciconfig hci0 up+ to bring them up."
+msgstr ""
+
+#. type: Plain text
+#: user-manual.txt:3071
+msgid ""
+"+hcitool scanning+ gets a list of bluetooth enabled client devices, look for "
+"the dive computer and remember the MAC address are shown there"
+msgstr ""
+
+#. type: Plain text
+#: user-manual.txt:3075
+msgid ""
+"+bluez-simple-agent hci0 10:00:E8:C4:BE:C4+ pairs the dive computer with the "
+"bluetooth stack of the _Subsurface_ computer, copy/paste the MAC address "
+"from the output of 'hcitool scanning'"
+msgstr ""
+
+#. type: Plain text
+#: user-manual.txt:3078
+msgid ""
+"Unfortunately on Linux binding to a communication device has to be done "
+"manually by running:"
+msgstr ""
+
+#. type: Plain text
+#: user-manual.txt:3084
+msgid ""
+"+rfcomm bind /dev/rfcomm0 10:00:E8:C4:BE:C4+ binds the dive computer to a "
+"communication device in the desktop computer, in case rfcomm is already "
+"taken use rfcomm1 or up. IMPORTANT: Copy/paste the MAC address from the "
+"output of +hcitool scanning+, the MAC address shown above will not work."
+msgstr ""
+
+#. type: Plain text
+#: user-manual.txt:3087
+msgid ""
+"For downloading dives in _Subsurface_ specify the device name connected to "
+"the MAC address in the last step above, e.g. _/dev/rfcomm0_."
+msgstr ""
+
+#. type: Title ==
+#: user-manual.txt:3089
+#, no-wrap
+msgid "APPENDIX B: Dive Computer specific information for importing dive information."
+msgstr ""
+
+#. type: Title ===
+#: user-manual.txt:3092
+#, no-wrap
+msgid "Import from a Uemis Zurich"
+msgstr ""
+
+#. type: Named 'icon' AttributeList argument for style 'icon'
+#: user-manual.txt:3094
+#, no-wrap
+msgid "images/icons/iumis.jpg"
+msgstr ""
+
+#. type: Plain text
+#: user-manual.txt:3110
+msgid ""
+"_Subsurface_ downloads the information stored on the SDA (the built-in file "
+"system of the Uemis) including information about dive spots and equipment. "
+"Buddy information is not yet downloadable.  Things are very similar to a "
+"normal USB-connected dive computer (the Uemis is one of those that recharge "
+"when connected to the USB port).  The main difference is that one does not "
+"enter a device name, but instead the location where the UEMISSDA file system "
+"is mounted once connected to the dive computer. On Windows this is a drive "
+"letter ( often 'E:' or 'F:'), on a Mac this is '/Volumes/UEMISSDA' and on "
+"Linux systems this differs depending on the distribution. On Fedora it "
+"usually is '/var/run/media/<your_username>/UEMISSDA'. In all cases "
+"_Subsurface_ should suggest the correct location in the drop down list."
+msgstr ""
+
+#. type: Plain text
+#: user-manual.txt:3125
+msgid ""
+"After selecting the above device name, download the dives from the Uemis "
+"Zurich. One technical issue with the Uemis Zurich download implementation "
+"(this is a Uemis firmware limitation, not a _Subsurface_ issue) is that one "
+"cannot download more than about 40-50 dives without running out of memory on "
+"the SDA. This will usually only happen the very first time one downloads "
+"dives from the Uemis Zurich.  Normally when downloading at the end of a day "
+"or even after a dive trip, the capacity is sufficient. If _Subsurface_ "
+"displays an error that the dive computer ran out of space the solution is "
+"straight forward.  Disconnect the SDA, turn it off and on again, and "
+"reconnect it. You can now retry (or start a new download session) and the "
+"download will continue where it stopped previously. One may have to do this "
+"more than once, depending on how many dives are stored on the dive computer."
+msgstr ""
+
+#. type: Title ===
+#: user-manual.txt:3127
+#, no-wrap
+msgid "Importing dives from the Uwatec Galileo"
+msgstr ""
+
+#. type: Named 'icon' AttributeList argument for style 'icon'
+#: user-manual.txt:3129
+#, no-wrap
+msgid "images/icons/Galileo.jpg"
+msgstr ""
+
+#. type: Plain text
+#: user-manual.txt:3144
+msgid ""
+"The Uwatec Galileo dive computers use infra red (IrDA) communication between "
+"the dive computer and Subsurface. The Uwatec hardware uses a USB dongle "
+"based on the serial infra-red (SIR) protocol and the MSC7780 IrDA controller "
+"manufactured by MosChip and marketed by Scubapro and some electronics "
+"companies.  Under Linux, the kernel already provides for communication using "
+"the IrDA protocol. However, the user additionally needs to load a driver for "
+"the IrDA interface with the dive computer. The easiest way is to load the "
+"*irda-tools* package from the http://irda.sourceforge.net/docs/startirda."
+"html[Linux IrDA Project].  After the installation of the irda-tools, the "
+"*root user* can specify a device name from the console as follows: +irattach "
+"irda0+"
+msgstr ""
+
+#. type: Plain text
+#: user-manual.txt:3147
+msgid ""
+"After executing this command, Subsurface will recognise the Galileo dive "
+"computer and download dive information."
+msgstr ""
+
+#. type: Plain text
+#: user-manual.txt:3151
+msgid ""
+"Under Windows, a similar situation exists. Drivers for the MCS7780 are "
+"available from some Internet web sites e.g.  http://www.drivers-download.com/"
+"Drv/MosChip/MCS7780/[www.drivers-download.com]."
+msgstr ""
+
+#. type: Plain text
+#: user-manual.txt:3154
+msgid ""
+"For the Apple Mac, IrDA communication via the MCS7780 link is not available "
+"for OSX 10.6 or higher."
+msgstr ""
+
+#. type: Title ===
+#: user-manual.txt:3156
+#, no-wrap
+msgid "Importing dives from Heinrichs Weikamp DR5"
+msgstr ""
+
+#. type: Named 'icon' AttributeList argument for style 'icon'
+#: user-manual.txt:3158
+#, no-wrap
+msgid "images/icons/HW_DR5.jpg"
+msgstr ""
+
+#. type: Plain text
+#: user-manual.txt:3168
+msgid ""
+"When mounted as a USB drive the Heinrichs Weikamp DR5 saves a single UDDF "
+"file for every dive.  Mark all the dives you'd like to import or open.  "
+"Note: The DR5 does not seem to store gradient factors nor deco information, "
+"so for _Subsurface_ it is not possible to display them. Adjust the gradient "
+"factors in the _Graph Settings_ in _Subsurface_ to generate a deco overlay "
+"in the _Subsurface_ *Dive Profile* panel but please note that the deco "
+"calculated by _Subsurface_ will most likely differ from the one displayed on "
+"the DR5."
+msgstr ""
+
+#. type: Title ===
+#: user-manual.txt:3169
+#, no-wrap
+msgid "Import from Shearwater Predator using Bluetooth"
+msgstr ""
+
+#. type: Named 'icon' AttributeList argument for style 'icon'
+#: user-manual.txt:3171
+#, no-wrap
+msgid "images/icons/predator.jpg"
+msgstr ""
+
+#. type: Plain text
+#: user-manual.txt:3179
+msgid ""
+"Using a Shearwater Predator one may be able to pair Bluetooth but then "
+"encounter issues when downloading, showing errors like _Slip RX: unexp. SLIP "
+"END_ on the Predator.  This might also arise when using other dive log "
+"software and operating systems other than Linux. We have no detailed idea "
+"about the source and how to fix this, but it is reported to be solved "
+"sometimes by one of these steps:"
+msgstr ""
+
+#. type: Plain text
+#: user-manual.txt:3182
+msgid ""
+"use the Bluetooth dongle which came with the Shearwater Predator instead of "
+"the built-in one of the _Subsurface_ computer"
+msgstr ""
+
+#. type: Plain text
+#: user-manual.txt:3183
+msgid "switch to different Bluetooth drivers for the same hardware"
+msgstr ""
+
+#. type: Plain text
+#: user-manual.txt:3184
+msgid "switch off WiFi while using Bluetooth"
+msgstr ""
+
+#. type: Title ===
+#: user-manual.txt:3186
+#, no-wrap
+msgid "Importing dive logs from the Poseidon MkVI Discovery"
+msgstr ""
+
+#. type: Named 'icon' AttributeList argument for style 'icon'
+#: user-manual.txt:3188
+#, no-wrap
+msgid "images/MkVI.jpeg"
+msgstr ""
+
+#. type: Plain text
+#: user-manual.txt:3196
+msgid ""
+"Download of dive logs from the MkVI is performed using a custom "
+"communications adapter and the _Poseidon PC Configuration Software_, "
+"obtained when purchasing the MKVI equipment. The latter is a Windows "
+"application allowing configuration of equipment and storage of dive logs. "
+"Communication between dive computer and desktop computer utilises the IrDA "
+"infra-red protocol. Only data for one dive can be downloaded at a time, "
+"comprising three files:"
+msgstr ""
+
+#. type: Plain text
+#: user-manual.txt:3199
+msgid ""
+"Setup configuration for the dive and key dive parameters (file with a .txt "
+"extension)"
+msgstr ""
+
+#. type: Plain text
+#: user-manual.txt:3200
+msgid "Dive log details (file with a .csv extension)"
+msgstr ""
+
+#. type: Plain text
+#: user-manual.txt:3202
+msgid ""
+"Redbook format dive log (file with .cvsr extension). This is a compressed "
+"version of the dive log using a proprietary format."
+msgstr ""
+
+#. type: Plain text
+#: user-manual.txt:3204
+msgid ""
+"_Subsurface_ accesses the .txt and the .csv files to obtain dive log "
+"information."
+msgstr ""
+
+#. type: Title ===
+#: user-manual.txt:3206
+#, no-wrap
+msgid "Importing dive logs from the APD Inspiration CCR"
+msgstr ""
+
+#. type: Named 'icon' AttributeList argument for style 'icon'
+#: user-manual.txt:3208
+#, no-wrap
+msgid "images/APDComputer.jpg"
+msgstr ""
+
+#. type: Plain text
+#: user-manual.txt:3216
+msgid ""
+"The dive logs of an APD Inspiration or similar CCR dive computer are "
+"downloaded using a communications adapter and _AP Communicator_, obtained "
+"when purchasing the equipment. The dive logs can be viewed using the _AP Log "
+"Viewer_, within Windows or Mac/OS. However, APD logs can be viewed and "
+"managed from within _Subsurface_ (together with dives using many other types "
+"of dive computer). The APD inspiration dive logs are imported into "
+"_Subsurface_ as follows:"
+msgstr ""
+
+#. type: Plain text
+#: user-manual.txt:3218
+msgid "Open a dive within the _AP Log Viewer_."
+msgstr ""
+
+#. type: Plain text
+#: user-manual.txt:3219
+msgid "Select the tab at the top of the screen, entitled \"_Data_\"."
+msgstr ""
+
+#. type: Plain text
+#: user-manual.txt:3220
+msgid ""
+"If the raw dive log data show on the screen, click on \"_Copy to Clipboard_"
+"\"."
+msgstr ""
+
+#. type: Plain text
+#: user-manual.txt:3221
+msgid "Open a text editor, e.g. Notepad (Windows), TextWrangler (Mac)."
+msgstr ""
+
+#. type: Plain text
+#: user-manual.txt:3223
+msgid ""
+"Copy the contents of the clipboard into the text editor and save the text "
+"file with a filename extension of .CSV"
+msgstr ""
+
+#. type: Plain text
+#: user-manual.txt:3224
+msgid ""
+"Within _Subsurface_, select _Import->Import log files_ to open the xref:"
+"Unified_import[universal import dialogue]."
+msgstr ""
+
+#. type: Plain text
+#: user-manual.txt:3225
+msgid ""
+"In the dropdown list towards the bottom right of the dialogue, select \"_CSV "
+"files_\"."
+msgstr ""
+
+#. type: Plain text
+#: user-manual.txt:3227
+msgid ""
+"On the list of file names select the .CSV file that has been created above. "
+"An import dialogue opens."
+msgstr ""
+
+#. type: Plain text
+#: user-manual.txt:3229
+msgid ""
+"In the dropdown list on the middle right labeled '_Pre-configured imports_"
+"\", select _APD Log Viewer_."
+msgstr ""
+
+#. type: Plain text
+#: user-manual.txt:3230
+msgid ""
+"Ensure the other settings for the ADP dive log are appropriate, then select "
+"_OK_."
+msgstr ""
+
+#. type: Plain text
+#: user-manual.txt:3232
+msgid "The APD dive log will appear within _Subsurface_."
+msgstr ""
+
+#. type: Title ==
+#: user-manual.txt:3234
+#, no-wrap
+msgid "APPENDIX C: Exporting Dive log information from external dive log software."
+msgstr ""
+
+#. type: Plain text
+#: user-manual.txt:3243
+msgid ""
+"The import of dive log data from external dive log software is mostly "
+"performed using the dialogue found by selecting _Import_ from the Main Menu, "
+"then clicking on _Import Log Files_. This is a single-step process, more "
+"information about which can be found xref:Unified_import[here.] However, in "
+"some cases, a two-step process may be required:"
+msgstr ""
+
+#. type: Plain text
+#: user-manual.txt:3246
+msgid ""
+"Export the foreign dive log data to format that is accessible from "
+"_Subsurface_."
+msgstr ""
+
+#. type: Plain text
+#: user-manual.txt:3247
+msgid "Import the accessible dive log data into _Subsurface_."
+msgstr ""
+
+#. type: Plain text
+#: user-manual.txt:3251
+msgid ""
+"This appendix provides some information about approaches to export dive log "
+"data from foreign dive log software. The procedures below mostly apply to "
+"Linux and/or Windows."
+msgstr ""
+
+#. type: Title ===
+#: user-manual.txt:3253
+#, no-wrap
+msgid "Exporting dives from *Suunto Divemanager (DM3, DM4 or DM5)*"
+msgstr ""
+
+#. type: Named 'icon' AttributeList argument for style 'icon'
+#: user-manual.txt:3254
+#, no-wrap
+msgid "images/icons/suuntologo.jpg"
+msgstr ""
+
+#. type: Plain text
+#: user-manual.txt:3261
+msgid ""
+"DiveManager is a MS Windows application for Suunto dive computers.  "
+"Divemanager 3 (DM3) is an older version of the Suunto software. More recent "
+"Suunto dive computers use Divemanager version 4 or 5 (DM4 or DM5). The "
+"different versions of Divemanager use different methods and different file "
+"naming conventions to export dive log data."
+msgstr ""
+
+#. type: Plain text
+#: user-manual.txt:3263
+#, no-wrap
+msgid "*Divemanager 3 (DM3):*\n"
+msgstr ""
+
+#. type: Plain text
+#: user-manual.txt:3265
+msgid ""
+"Start 'Suunto Divemanager 3' and log in with the name containing the logs"
+msgstr ""
+
+#. type: Plain text
+#: user-manual.txt:3266
+msgid "Do not start the import wizard to import dives from the dive computer."
+msgstr ""
+
+#. type: Plain text
+#: user-manual.txt:3268
+msgid ""
+"In the navigation tree on the left side of the program-window, select the "
+"appropriate dives."
+msgstr ""
+
+#. type: Plain text
+#: user-manual.txt:3269
+msgid ""
+"Within the list of dives, select the dives you would like to import later:"
+msgstr ""
+
+#. type: Plain text
+#: user-manual.txt:3270
+msgid "To select certain dives: hold 'ctrl' and click the dive"
+msgstr ""
+
+#. type: Plain text
+#: user-manual.txt:3273
+msgid ""
+"To select all dives: Select the first dive, hold down shift and select the "
+"last dive"
+msgstr ""
+
+#. type: Plain text
+#: user-manual.txt:3274
+msgid "With the dives marked, use the program menu _File -> Export_"
+msgstr ""
+
+#. type: Plain text
+#: user-manual.txt:3275
+msgid ""
+"The export pop-up will show. Within this pop-up, there is one field called "
+"'Export Path'."
+msgstr ""
+
+#. type: Plain text
+#: user-manual.txt:3276
+msgid "Click the browse button next to the field Export Path"
+msgstr ""
+
+#. type: Plain text
+#: user-manual.txt:3281
+#, no-wrap
+msgid ""
+"** A file-manager like window pops up\n"
+"** Navigate to the directory for storing the\n"
+"Divelog.SDE file\n"
+"\t\t** Optionally change the name of the file for saving\n"
+"\t\t** Click 'Save'\n"
+msgstr ""
+
+#. type: Plain text
+#: user-manual.txt:3282
+#, no-wrap
+msgid "Back in the Export pop-up, press the button 'Export'\n"
+msgstr ""
+
+#. type: Plain text
+#: user-manual.txt:3283
+#, no-wrap
+msgid "The dives are now exported to the file Divelog.SDE.\n"
+msgstr ""
+
+#. type: Plain text
+#: user-manual.txt:3285
+#, no-wrap
+msgid "*Divemanager 4 (DM4) and Divemanager 5 (DM5):*\n"
+msgstr ""
+
+#. type: Plain text
+#: user-manual.txt:3290
+msgid ""
+"DM4 and DM5 use identical mechanisms for exporting dive logs.  To export a "
+"divelog from Divemanager one needs to locate the DM4/DM5 database where the "
+"dives are stored. the user can either look for the original database or make "
+"a backup of the dives. Both methods are described here."
+msgstr ""
+
+#. type: Plain text
+#: user-manual.txt:3292
+msgid "Locating the Suunto DM4 (or DM5) database:"
+msgstr ""
+
+#. type: Plain text
+#: user-manual.txt:3294 user-manual.txt:3303
+msgid "Start Suunto DM4/DM5"
+msgstr ""
+
+#. type: Plain text
+#: user-manual.txt:3295
+msgid "Select 'Help -> About'"
+msgstr ""
+
+#. type: Plain text
+#: user-manual.txt:3296
+msgid "Click 'Copy' after text 'Copy log folder path to clipboard'"
+msgstr ""
+
+#. type: Plain text
+#: user-manual.txt:3297
+msgid "Now open Windows Explorer"
+msgstr ""
+
+#. type: Plain text
+#: user-manual.txt:3298
+msgid "Paste the address to the path box at the top of the File Explorer"
+msgstr ""
+
+#. type: Plain text
+#: user-manual.txt:3299
+msgid "The database is called DM4.db or DM5.db"
+msgstr ""
+
+#. type: Plain text
+#: user-manual.txt:3301
+msgid "Making a backup copy of the Suunto DM4/DM5 database:"
+msgstr ""
+
+#. type: Plain text
+#: user-manual.txt:3304
+msgid "Select 'File - Create backup'"
+msgstr ""
+
+#. type: Plain text
+#: user-manual.txt:3306
+msgid ""
+"From the file menu select the location and name for the backup, we'll use "
+"DM4 (or DM5) in here with the default extension .bak"
+msgstr ""
+
+#. type: Plain text
+#: user-manual.txt:3307
+msgid "Click 'Save'"
+msgstr ""
+
+#. type: Plain text
+#: user-manual.txt:3308
+msgid "The dives are now exported to the file DM4.bak (or DM5.bak)"
+msgstr ""
+
+#. type: Title ===
+#: user-manual.txt:3310
+#, no-wrap
+msgid "Exporting from Mares Dive Organiser V2.1"
+msgstr ""
+
+#. type: Named 'icon' AttributeList argument for style 'icon'
+#: user-manual.txt:3313
+#, no-wrap
+msgid "images/icons/mareslogo.jpg"
+msgstr ""
+
+#. type: Plain text
+#: user-manual.txt:3321
+msgid ""
+"Mares Dive Organiser is a Windows application. The dive log is kept as a "
+"Microsoft SQL Compact Edition database with a '.sdf' filename extension. The "
+"database includes all Dive Organiser-registered divers on the particular "
+"computer and all Mares dive computers used. The safest way to obtain a copy "
+"of the dive database is to export the information to another compatible "
+"format which can be imported into _Subsurface_."
+msgstr ""
+
+#. type: Plain text
+#: user-manual.txt:3326
+msgid ""
+"Within Dive Organiser, select _Database -> Backup_ from the main menu and "
+"back up the database to the desk top.  This creates a zipped file "
+"DiveOrganiserxxxxx.dbf."
+msgstr ""
+
+#. type: Plain text
+#: user-manual.txt:3329
+msgid ""
+"Rename the file to DiveOrganiserxxxxx.zip. Inside the zipped directory is a "
+"file _DiveOrganiser.sdf_."
+msgstr ""
+
+#. type: Plain text
+#: user-manual.txt:3330
+msgid "Extract the _.sdf_ file from the zipped folder to your Desktop."
+msgstr ""
+
+#. type: Plain text
+#: user-manual.txt:3331
+msgid "The password for accessing the .zip file is _mares_."
+msgstr ""
+
+#. type: Title ===
+#: user-manual.txt:3333
+#, no-wrap
+msgid "Exporting dives from *DivingLog 5.0*"
+msgstr ""
+
+#. type: Named 'icon' AttributeList argument for style 'icon'
+#: user-manual.txt:3335
+#, no-wrap
+msgid "images/icons/divingloglogo.jpg"
+msgstr ""
+
+#. type: Plain text
+#: user-manual.txt:3344
+msgid ""
+"Unfortunately DivingLog XML files give us no indication on the preferences "
+"set on one's system. So in order for _Subsurface_ to be able to successfully "
+"import XML files from DivingLog one first needs to ensure that DivingLog is "
+"configured to use the Metric system (one can easily change this within "
+"Diving Log by selecting 'File -> Preferences -> Units and Language' by "
+"clicking the 'Metric' button). Then do the following:"
+msgstr ""
+
+#. type: Plain text
+#: user-manual.txt:3346
+msgid "In DivingLog open the 'File -> Export -> XML' menu"
+msgstr ""
+
+#. type: Plain text
+#: user-manual.txt:3347
+msgid "Select the dives to export"
+msgstr ""
+
+#. type: Plain text
+#: user-manual.txt:3348
+msgid "Click on the export button and select the filename"
+msgstr ""
+
+#. type: Title ==
+#: user-manual.txt:3350
+#, no-wrap
+msgid "APPENDIX D: Exporting a spreadsheet to CSV format"
+msgstr ""
+
+#. type: Plain text
+#: user-manual.txt:3360
+msgid ""
+"Many divers keep a diving log in some form of a digital file, commonly a "
+"spreadsheet with various fields of information. These logs can be easily "
+"imported into _Subsurface_ (xref:S_ImportingManualCSV[Importing dives "
+"from_manually kept CSV file]), after the spreadsheet is converted in a .CSV "
+"file.  This section explains the procedure to convert a diving logbook "
+"stored in a spreadsheet to a .CSV file that will later be imported from "
+"_Subsurface_.  Creating a .CSV is a straightforward task, although the "
+"procedure is somewhat different according to which spreadsheet program is "
+"used."
+msgstr ""
+
+#. type: Plain text
+#: user-manual.txt:3366
+msgid ""
+"The first step is to organize the diving data in the spreadsheet, so that "
+"the first row contains the names (or titles) of each column and the "
+"information for each dive is stored in a single row.  _Subsurface_ supports "
+"many data items (Dive #, Date, Time, Duration, Location, GPS, Max Depth, "
+"Mean Depth, Buddy, Notes, Weight and Tags).  The user can organize dive data "
+"following a few simple rules:"
+msgstr ""
+
+#. type: Plain text
+#: user-manual.txt:3368
+msgid ""
+"Date: use one of the following formats: yyyy-mm-dd, dd.mm.yyyy, mm/dd/yyyy"
+msgstr ""
+
+#. type: Plain text
+#: user-manual.txt:3369
+msgid "Duration: the format should be minutes:seconds."
+msgstr ""
+
+#. type: Plain text
+#: user-manual.txt:3370
+msgid ""
+"Unit system: only one unit system shold be used (i.e., no mixture between "
+"imperial and metric units)"
+msgstr ""
+
+#. type: Plain text
+#: user-manual.txt:3371
+msgid "Tags and buddies: values should be separated using a comma."
+msgstr ""
+
+#. type: Plain text
+#: user-manual.txt:3372
+msgid "GPS position: users must use decimal degrees, e.g. 30.22496 30.821798"
+msgstr ""
+
+#. type: Title ===
+#: user-manual.txt:3373
+#, no-wrap
+msgid "_LibreOffice Calc_ and _OpenOffice Calc_"
+msgstr ""
+
+#. type: Plain text
+#: user-manual.txt:3377
+msgid ""
+"These are open source spreadsheet applications forming parts of larger open "
+"source office suite applications. The user interaction with _LibreOffice_ "
+"and _OpenOffice_ is very similar.  In Libreoffice Calc the time format "
+"should be set to minutes:seconds - [mm]:ss and dates should be set to one "
+"of: yyyy-mm-dd, dd.mm.yyyy, mm/dd/yyyy. A typical dive log may look like "
+"this:"
+msgstr ""
+
+#. type: Target for macro image
+#: user-manual.txt:3378
+#, no-wrap
+msgid "images/LOffice_spreadsheetdata.jpg"
+msgstr ""
+
+#. type: Plain text
+#: user-manual.txt:3381
+msgid ""
+"To export the data as a .CSV file from within LibreOffice click _File -> "
+"Save As_. On the dialogue that comes up, select the _Text CSV (.csv)_ as the "
+"file type and select the option _Edit filter settings_."
+msgstr ""
+
+#. type: Target for macro image
+#: user-manual.txt:3382
+#, no-wrap
+msgid "images/LOffice_save_as_options.jpg"
+msgstr ""
+
+#. type: Plain text
+#: user-manual.txt:3385
+msgid ""
+"After selecting _Save_, select the appropriate field delimiter (choose _Tab_ "
+"to prevent conflicts with the comma when using this as a decimal point), "
+"then select _OK_."
+msgstr ""
+
+#. type: Target for macro image
+#: user-manual.txt:3386
+#, no-wrap
+msgid "images/LOffice_field_options.jpg"
+msgstr ""
+
+#. type: Plain text
+#: user-manual.txt:3389
+msgid ""
+"One can double check the .CSV file by opening it with a text editor, and "
+"then import the dive data as explained on the section xref:"
+"S_ImportingManualCSV[Importing dives from manually kept CSV files]."
+msgstr ""
+
+#. type: Title ===
+#: user-manual.txt:3390
+#, no-wrap
+msgid "Microsoft _Excel_"
+msgstr ""
+
+#. type: Plain text
+#: user-manual.txt:3396
+msgid ""
+"The field delimiter (called \"_list separator_\" in Microsoft manuals) is "
+"not accessible from within _Excel_ and needs to be set through the "
+"_Microsoft Control Panel_. After changing the separator character, all "
+"software on the Windows machine use the new character as a separator.  One "
+"can change the character back to the default character by following the same "
+"procedure, outlined below."
+msgstr ""
+
+#. type: Plain text
+#: user-manual.txt:3398
+msgid ""
+"In Microsoft Windows, click the *Start* button, and then select _Control "
+"Panel_ from the list on the right-hand side."
+msgstr ""
+
+#. type: Plain text
+#: user-manual.txt:3399
+msgid "Open the _Regional and Language Options_ dialog box."
+msgstr ""
+
+#. type: Plain text
+#: user-manual.txt:3402
+msgid ""
+"Do one of the following: ** In Windows 7, click the _Formats_ tab, and then "
+"click _Customize this format_.  ** In Windows XP, click the _Regional "
+"Options_ tab, and then click _Customize_."
+msgstr ""
+
+#. type: Plain text
+#: user-manual.txt:3403
+msgid ""
+"Type a new separator in the _List separator_ box. To use a TAB-delimited "
+"file, type the word TAB in the box."
+msgstr ""
+
+#. type: Plain text
+#: user-manual.txt:3404
+msgid "Click _OK_ twice."
+msgstr ""
+
+#. type: Plain text
+#: user-manual.txt:3406
+msgid "Below is an image of the _Control Panel_:"
+msgstr ""
+
+#. type: Target for macro image
+#: user-manual.txt:3407
+#, no-wrap
+msgid "images/Win_SaveCSV2.jpg"
+msgstr ""
+
+#. type: Plain text
+#: user-manual.txt:3410
+msgid "To export the dive log in CSV format:"
+msgstr ""
+
+#. type: Plain text
+#: user-manual.txt:3412
+msgid ""
+"With the dive log opened in _Excel_, select the round Windows button at the "
+"top left, then _Save As_."
+msgstr ""
+
+#. type: Target for macro image
+#: user-manual.txt:3413
+#, no-wrap
+msgid "images/Win_SaveCSV1.jpg"
+msgstr ""
+
+#. type: Plain text
+#: user-manual.txt:3416
+msgid ""
+"Click on the left-hand part of the _Save as_ option, NOT on the arrow on the "
+"right-hand. This brings up a dialogue for saving the spreadsheet in an "
+"alternative format. From the dropdown list at the bottom of the dialogue, "
+"marked _Save as Type:_, select _CSV(Comma delimited) (*.CSV)_. Ensure that "
+"the appropriate folder has been selected to save the CSV file into."
+msgstr ""
+
+#. type: Target for macro image
+#: user-manual.txt:3417
+#, no-wrap
+msgid "images/Win_SaveCSV3.jpg"
+msgstr ""
+
+#. type: Plain text
+#: user-manual.txt:3420
+msgid ""
+"Select the _Save_ button. The CSV-formatted file is saved into the folder "
+"that was selected. One can double check the .CSV file by opening it with a "
+"text editor, and then import the dive data as explained on the section xref:"
+"S_ImportingManualCSV[Importing dives from manually kept CSV files]."
+msgstr ""
+
+#. type: Title ==
+#: user-manual.txt:3421
+#, no-wrap
+msgid "APPENDIX E: FAQs."
+msgstr ""
+
+#. type: Title ===
+#: user-manual.txt:3423
+#, no-wrap
+msgid "Subsurface appears to miscalculate gas consumption and SAC"
+msgstr ""
+
+#. type: Plain text
+#: user-manual.txt:3427
+msgid ""
+"'Question': I dived with a 12.2 l tank, starting with 220 bar and ending "
+"with 100 bar, and I calculate a different SAC compared what _Subsurface_ "
+"calculates. Is _Subsurface_ miscalculating?"
+msgstr ""
+
+#. type: Plain text
+#: user-manual.txt:3433
+msgid ""
+"'Answer': Not really. What happens is that _Subsurface_ actually calculates "
+"gas consumption differently - and better - than you expect.  In particular, "
+"it takes the incompressibility of the gas into account.  Traditionally, Gas "
+"consumption and SAC should be: +consumption = tank size x (start pressure - "
+"end pressure)+"
+msgstr ""
+
+#. type: Plain text
+#: user-manual.txt:3439
+msgid ""
+"and that's true for an ideal gas, and it's what you get taught in dive "
+"theory.  But an \"ideal gas\" doesn't actually exist, and real gases "
+"actually don't compress linearly with pressure. Also, you are missing the "
+"fact that one atmosphere of pressure isn't actually one bar.  So the *real* "
+"calculation is:"
+msgstr ""
+
+#. type: Plain text
+#: user-manual.txt:3441
+msgid "+consumption = (amount_of_air_at_beginning - amount_of_air_at_end)+"
+msgstr ""
+
+#. type: Plain text
+#: user-manual.txt:3447
+msgid ""
+"where the amount of air is *not* just \"tank size times pressure in bar\".  "
+"It's a combination of: \"take compressibility into account\" (which is a "
+"fairly small issue under 220 bar - you'll see more differences when you do "
+"high-pressure tanks with 300bar) and \"convert bar to atm\" (which is the "
+"majority of your discrepancy).  Remember: one ATM is ~1.013 bar, so without "
+"the compressibility, your gas use is:"
+msgstr ""
+
+#. type: Plain text
+#: user-manual.txt:3449
+msgid "+12.2*((220-100)/1.013)+"
+msgstr ""
+
+#. type: Plain text
+#: user-manual.txt:3454
+msgid ""
+"which is about 1445, not 1464. So there was 19 l too much in your simple "
+"calculation that ignored the difference between 1 bar and one ATM.  The "
+"compressibility does show up above 200 bar, and takes that 1445 down about "
+"eight litres more, so you really did use only about 1437 l of air at surface "
+"pressure."
+msgstr ""
+
+#. type: Plain text
+#: user-manual.txt:3460
+msgid ""
+"So be happy: your SAC really is better than your calculations indicated.  Or "
+"be sad: your cylinder contains less air than you thought it did.  And as "
+"mentioned, the \"contains less air than you thought it did\" really starts "
+"becoming much more noticeable at high pressure. A 400 bar really does not "
+"contain twice as much air as a 200 bar one. At lower pressures, air acts "
+"pretty much like an ideal gas."
+msgstr ""
+
+#. type: Title ===
+#: user-manual.txt:3461
+#, no-wrap
+msgid "Some dive profiles have time discrepancies with the recorded samples from my dive computer..."
+msgstr ""
+
+#. type: Plain text
+#: user-manual.txt:3465
+msgid ""
+"_Subsurface_ ends up ignoring surface time for many things (average depth, "
+"divetime, SAC, etc).  'Question': Why do dive durations in my dive computer "
+"differ from that given by _Subsurface_?"
+msgstr ""
+
+#. type: Plain text
+#: user-manual.txt:3473
+msgid ""
+"'Answer': For example, if you end up doing a weight check (deep enough to "
+"trigger the \"dive started\")  but then come back up and wait five minutes "
+"for your buddies, your dive computer may say that your dive is 50 minutes "
+"long - because you have fifty minutes worth of samples - but subsurface will "
+"say it's 45 minutes - because you were actually diving for 45 minutes.  It's "
+"even more noticeable if you do things like divemastering the initial OW "
+"dives, when you may stay in the water for a long time, but spend most of it "
+"at the surface. And then you don't want that to count as some kind of long "
+"dive”."
+msgstr ""
diff --git a/Documentation/user-manual_fr.html.git b/Documentation/user-manual_fr.html.git
new file mode 100644
index 000000000..ff321c27a
--- /dev/null
+++ b/Documentation/user-manual_fr.html.git
@@ -0,0 +1,4593 @@
+<!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.8" />
+<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="images/Subsurface4Banner.jpg" alt="Banner" />
+</div>
+</div>
+<div class="paragraph"><p><span class="big">MANUEL UTILISATEUR</span></p></div>
+<div class="paragraph"><p><strong>Auteurs du manuel</strong> : Willem Ferguson, Jacco van Koll, Dirk Hohndel, Reinout Hoornweg,
+Linus Torvalds, Miika Turkia, Amit Chaudhuri, Jan Schubert, Salvador Cuñat, Pedro Neves</p></div>
+<div class="paragraph"><p><span class="blue"><em>Version 4.3, Décembre 2014</em></span></p></div>
+<div class="paragraph"><p>Bienvenue en tant qu&#8217;utilisateur de <em>Subsurface</em>, un programme avancé
+d&#8217;enregistrement de plongées (carnet de plongées) avec une bonne
+infrastructure pour décrire, organiser, interpréter et imprimer des plongées
+en scaphandre et en apnée. <em>Subsurface</em> offre de nombreux avantages par
+rapport à d&#8217;autres solutions logicielles similaires :</p></div>
+<div class="ulist"><ul>
+<li>
+<p>
+Do you need a flexible way of logging dives using recreational equipment,
+   even not using a dive computer?
+</p>
+</li>
+<li>
+<p>
+Do you use two different dive computer brands, each with its own proprietary
+   software for downloading dive logs? Do you dive with rebreathers as well as
+   open circuit or recreational equipment? Do you use a Reefnet Sensus
+   time-depth recorder in conjunction with a dive computer? <em>Subsurface</em> offers
+   a standard interface for downloading dive logs from all these different
+   pieces of equipment and to store and analyse the dive logs within a unified
+   system.
+</p>
+</li>
+<li>
+<p>
+Do you use more than one operating system? <em>Subsurface</em> is fully compatible
+   with Mac, Linux and Windows, allowing you to access your dive log on each of
+   your operating systems using a single application.
+</p>
+</li>
+<li>
+<p>
+Do you use Linux or Mac and your dive computer has only Windows-based
+   software for downloading dive information (e.g. Mares)? <em>Subsurface</em>
+   provides a way of downloading and analysing your dive logs on other
+   operating systems.
+</p>
+</li>
+<li>
+<p>
+Do you need an intuitive graphical dive planner that integrates with and
+   takes into account the dives that have already been logged?
+</p>
+</li>
+</ul></div>
+<div class="paragraph"><p><em>Subsurface</em> binaries are available for Windows PCs (Win XP or later), Intel
+based Macs (OS/X) and many Linux distributions. <em>Subsurface</em> can be built
+for many more hardware platforms and software environments where Qt and
+libdivecomputer are available.</p></div>
+<div class="paragraph"><p>The scope of this document is the use of the <em>Subsurface</em> program. To
+install the software, consult the <em>Downloads</em> page on the
+<a href="http://subsurface-divelog.org/"><em>Subsurface</em> web site</a>.  Please discuss
+issues with this program by sending an email to
+<a href="mailto:subsurface@subsurface-divelog.org">our mailing list</a> and report bugs
+at <a href="http://trac.hohndel.org">our bugtracker</a>.  For instructions on how to
+build the software and (if needed) its dependencies please consult the
+INSTALL file included with the source code.</p></div>
+<div class="paragraph"><p><strong>Audience</strong>: Recreational Scuba Divers, Free Divers, Tec Divers, Professional
+Divers</p></div>
+<div id="toc">
+  <div id="toctitle">Table of Contents</div>
+  <noscript><p><b>JavaScript must be enabled in your browser to display the table of contents.</b></p></noscript>
+</div>
+<div class="sect1">
+<h2 id="S_UserSurvey">1. Le sondage utilisateur</h2>
+<div class="sectionbody">
+<div class="paragraph"><p>In order to develop <em>Subsurface</em> in a way that serves its users in the best
+possible way, it is important to have some user information. Upon launching
+<em>Subsurface</em> after using this software for a week or so, a one-box user
+survey pops up. It is entirely optional and the user controls what, if any,
+data are sent to the <em>Subsurface</em> development team. Any data that the user
+chooses to send is extremely useful, and will only be used to steer future
+development and to customise the software to fit the needs of the
+<em>Subsurface</em> users. If one completes the survey, or clicks the option not to
+be asked again, that should be the last communication of this nature one
+receives.  However, if one&#8217;s diving and/or subsurface habits change and one
+wishes to provide another survey, this can be done by launching <em>Subsurface</em>
+with the <em>--survey</em> option on the command line.</p></div>
+</div>
+</div>
+<div class="sect1">
+<h2 id="S_StartUsing">2. Start Using the Program</h2>
+<div class="sectionbody">
+<div class="paragraph"><p>The <em>Subsurface</em> window is usually divided into four panels with a <strong>Main
+Menu</strong> (File Import Log View Filter Help) at the top of the window (for
+Windows and Linux) or the top of the screen (for Mac and Ubuntu Unity). The
+four panels are:</p></div>
+<div class="paragraph"><p>The <strong>Dive List</strong> to the bottom left containing a list of all the dives in the
+user&#8217;s dive log. A dive can be selected and highlighted on the dive list by
+clicking on it. In most situations the up/down keys can be used to switch
+between dives. The <strong>Dive List</strong> is an important tool for manipulating a dive
+log.</p></div>
+<div class="paragraph"><p>The <strong>Dive Map</strong> to the bottom right, showing the user&#8217;s dive sites on a world
+map and centred on the site of the last dive selected in the <strong>Dive List</strong>.</p></div>
+<div class="paragraph"><p>The <strong>Dive Info</strong> to the top left, giving more detailed information on the
+dive selected in the <strong>Dive List</strong>, including some statistics for the selected
+dive or for all highlighted dive(s).</p></div>
+<div class="paragraph"><p>The <strong>Dive Profile</strong> to the top right, showing a graphical dive profile of the
+selected dive in the <strong>Dive List</strong>.</p></div>
+<div class="paragraph"><p>The dividers between panels can be dragged in order to change the size of
+any of the panels. <em>Subsurface</em> remembers the position of the dividers, so
+the next time <em>Subsurface</em> starts it uses the positions of the dividers from
+when the program was last used.</p></div>
+<div class="paragraph"><p>If a dive is selected in the <strong>Dive List</strong>, the dive location, detailed
+information and profile of the <em>selected dive</em> are shown in the respective
+panels. On the other hand, if one highlights more than one dive the last
+highlighted dive is the <em>selected dive</em>, but summary data of all
+<em>highlighted dives</em> are shown in the <strong>Stats</strong> tab of the <strong>Dive Info</strong> panel
+(maximum, minimum and average depths, durations, water temperatures and SAC;
+total time and number of dives selected).</p></div>
+<div class="imageblock" id="S_ViewPanels" style="text-align:center;">
+<div class="content">
+<img src="images/main_window_f20.jpg" alt="The Main Window" />
+</div>
+</div>
+<div class="paragraph"><p>The user can determine which of the four panels are displayed by selecting
+the <strong>View</strong> option on the main menu. This feature gives the user several
+choices of display:</p></div>
+<div class="paragraph"><p><strong>All</strong>: show all four of the panels as in the screenshot above.</p></div>
+<div class="paragraph"><p><strong>Divelist</strong>: Show only the Dive List.</p></div>
+<div class="paragraph"><p><strong>Profile</strong>: Show only the Dive Profile of the selected dive.</p></div>
+<div class="paragraph"><p><strong>Info</strong>: Show only the Dive Notes about the last selected dive and statistics for
+all highlighted dives.</p></div>
+<div class="paragraph"><p><strong>Globe</strong>: Show only the world map, centred on the last selected dive.</p></div>
+<div class="paragraph"><p>Like many other functions that can be accessed via the Main Menu, these
+options can be triggered using keyboard shortcuts. The shortcuts for a
+particular system are shown with an underline in the main menu
+entries. Since different Operating Systems and the user chosen language may
+cause <em>Subsurface</em> to use different shortcut keys they are not listed here
+in the user manual.</p></div>
+<div class="paragraph"><p>When the program is started for the first time, it shows no information at
+all.  This is because the program doesn&#8217;t have any dive information
+available. In the following sections, the procedures to create a new logbook
+will be described.</p></div>
+</div>
+</div>
+<div class="sect1">
+<h2 id="S_NewLogbook">3. Creating a new logbook</h2>
+<div class="sectionbody">
+<div class="paragraph"><p>Select <em>File &#8594; New Logbook</em> from the main menu. All existing dive data are
+cleared so that new information can be added. If there are unsaved data in
+an open logbook, the user is asked whether the open logbook should be saved
+before a new logbook is created.</p></div>
+</div>
+</div>
+<div class="sect1">
+<h2 id="S_GetInformation">4. Storing dive information in the logbook</h2>
+<div class="sectionbody">
+<div class="paragraph"><p>Now that a new logbook was created, it is simple to add dive data to it.
+<em>Subsurface</em> allows several ways of adding dive data to a logbook, detailed
+in the following sections.</p></div>
+<div class="paragraph"><p>If the user has a handwritten divelog, a spreadsheet or another form of
+manually maintained divelog, dive data can be added to the logbook using one
+of these approaches:</p></div>
+<div class="paragraph"><p>Enter dive information by hand. This is useful if the diver did not use a
+dive computer and dives were recorded in a written logbook. See:
+<a href="#S_EnterData">Entering dive information by hand</a></p></div>
+<div class="paragraph"><p>Import dive log information that has been maintained either as a spreadsheet
+or as a CSV file. Refer to: <a href="#S_Appendix_D">APPENDIX D: Exporting a
+spreadsheet to CSV format</a> and the text about
+<a href="#S_ImportingManualCSV">Importing dives from manually created CSV files</a>
+and</p></div>
+<div class="paragraph"><p>If one has dives recorded using a dive computer, the depth profile of the
+dive and a large amount of additional information can be accessed. These
+dives can be imported from:</p></div>
+<div class="ulist"><ul>
+<li>
+<p>
+The divecomputer itself. See: <a href="#S_ImportDiveComputer">Importing new dive
+  information from a Dive Computer</a> or
+</p>
+</li>
+</ul></div>
+<div class="paragraph"><p>Proprietary software distributed by manufacturers of dive computers. Refer
+to: <a href="#S_ImportingAlienDiveLogs">Importing dive information from other
+digital data sources or other data formats</a>.</p></div>
+<div class="paragraph"><p>Import from spreadsheet or CSV files containing dive profiles.  See:
+<a href="#S_ImportingCSVDives">Importing dives in CSV format from dive computers
+or other dive log software</a></p></div>
+<div class="sect2">
+<h3 id="S_EnterData">4.1. Entering dive information by hand</h3>
+<div class="paragraph"><p>This is usually the approach for dives without a dive computer. The basic
+record of information within <em>Subsurface</em> is a dive. The most important
+information in a simple dive logbook usually includes dive type, date, time,
+duration, depth, the names of your dive buddy and of the dive master or dive
+guide, and some remarks about the dive. <em>Subsurface</em> can store much more
+information than this for each dive. In order to add a dive to a dive log,
+select <em>Log &#8594; Add Dive</em> from the Main Menu. The program then shows three
+panels to enter information for a dive: two tabs in the <strong>Dive Info</strong> panel
+(<strong>Dive Notes</strong> and <strong>Equipment</strong>), as well as the <strong>Dive Profile</strong> panel that
+displays a graphical profile of each dive. These panels are respectively
+marked <span class="red">A</span>, <span class="red">B</span> and <span class="red">C</span> in the figure below. Each of these
+tabs will now be explained for data entry.</p></div>
+<div class="imageblock" style="text-align:center;">
+<div class="content">
+<img src="images/AddDive1_f20.jpg" alt="FIGURE: Add dive" />
+</div>
+</div>
+<div class="paragraph"><p>When one edits a field in Dive notes or Equipment panels, <em>Subsurface</em>
+enters <strong>Editing Mode</strong>, indicated by the message in the blue box at the top
+of the <em>Dive Notes</em> panel (see the image below). This message is displayed
+in all the panels under Dive notes and Equipment when in <strong>Editing Mode</strong>.</p></div>
+<div class="imageblock" style="text-align:center;">
+<div class="content">
+<img src="images/BlueEditBar_f20.jpg" alt="Blue edit bar" />
+</div>
+</div>
+<div class="paragraph"><p>The <em>Save</em> button should only be selected after all the parts of a dive have
+been entered.  When entering dives by hand, the <em>Info</em>, <em>Equipment</em> and
+<em>Profile</em> tabs should be completed before saving the information. By
+selecting the <em>Save</em> button, a local copy of the information for this
+specific dive is saved in memory. When one closes Subsurface, the program
+will ask again, this time whether the complete dive log should be saved on
+disk or not.</p></div>
+<div class="sect3">
+<h4 id="_dive_notes">4.1.1. Dive Notes</h4>
+<div class="paragraph"><p>This panel contains the date, time and place information for a particular
+dive, environmental conditions, co-divers and buddies, as well as some
+descriptive information. If one clicks on the <strong>Dive Notes</strong> tab, the
+following fields are visible:</p></div>
+<div class="imageblock" style="text-align:center;">
+<div class="content">
+<img src="images/AddDive2_f20.jpg" alt="FIGURE: The Dive Notes tab" />
+</div>
+</div>
+<div class="paragraph"><p>The <strong>Time</strong> field reflects the date and the time of the dive. By clicking the
+date, a calendar is displayed from which one can choose the correct
+date. Press ESC to escape from the calendar.  The time values (hour and
+minutes) can also be edited directly by clicking on each of them in the text
+box and by overtyping the information displayed. The default date is the
+present date and the default time is an hour in advance of the present time.</p></div>
+<div class="paragraph"><p><strong>Air and water temperatures</strong>: the air and water temperatures during the
+dive can be typed directly on the fields to the right of the Start time.
+Temperature units are not needed, as they will be automatically supplied by
+<em>Subsurface</em>. Only the numerical value must be
+typed by the user (the units selected in the <em>Preferences</em>
+will determine whether metric or imperial units are used).</p></div>
+<div class="paragraph"><p><strong>Location</strong>: Here the name of the dive site can be entered, e.g. "Tihany, Lake
+Balaton,
+Hungary". Auto completion of location names will make this easier if one
+frequently dives at the same sites.</p></div>
+<div class="paragraph"><p><strong>Coordinates</strong>: The geographic coordinates of the dive site should be entered
+here. These can come from three sources:</p></div>
+<div class="paragraph"><p>One can find the coordinates on the world map in the bottom right hand part
+of the Subsurface window. The map displays a green bar indicating "No
+location data - Move the map and double-click to set the dive
+location". Upon a double-click at the appropriate place, the green bar
+disappears and the coordinates are stored.</p></div>
+<div class="paragraph"><p>The coordinates can be obtained from the <em>Subsurface</em> Companion app if the
+user has an Android device with GPS and if the coordinates of the dive site
+were stored using that device.  <a href="#S_Companion">Click here for more
+information</a></p></div>
+<div class="paragraph"><p>The coordinates can be entered by hand if they are known, using one of four
+formats with latitude followed by longitude:</p></div>
+<div class="literalblock">
+<div class="content">
+<pre><code>ISO 6709 Annex D format e.g. 30°13'28.9"N 30°49'1.5"E
+Degrees and decimal minutes, e.g. N30° 13.49760' , E30° 49.30788'
+Degrees minutes seconds, e.g. N30° 13' 29.8" , E30° 49' 1.5"
+Decimal degrees, e.g. 30.22496 , 30.821798</code></pre>
+</div></div>
+<div class="paragraph"><p>Southern hemisphere latitudes are given with a <strong>S</strong>, e.g. S30°, or with a
+negative value, e.g. -30.22496. Similarly western longitudes are given with
+a <strong>W</strong>, e.g. W07°, or with a negative value, e.g. -7.34323.</p></div>
+<div class="paragraph"><p>Please note that GPS coordinates of a dive site are linked to the Location
+name - so adding coordinates to dives that do not have a location
+description will cause unexpected behaviour (Subsurface will think that all
+of these dives have the same location and try to keep their GPS coordinates
+the same).</p></div>
+<div class="paragraph"><p><strong>Divemaster</strong>: The name of the dive master or dive guide for this dive can be
+entered here.
+Again, this field offers auto completion based on the list of dive masters in
+the current logbook.</p></div>
+<div class="paragraph"><p><strong>Buddy</strong>: In this field one can enter the name(s) of the buddy / buddies
+(separated by commas) who accompanied the user on the dive. Auto completion
+is offered based on the list of buddies in the current logbook.</p></div>
+<div class="paragraph"><p><strong>Suit</strong>: The type of diving suit used for the dive can be entered here.
+As with the other items, auto completion of the suit description is available.
+Some dry-suit users may choose to use this field to record what combination of
+suit and thermal protection undersuit was used.</p></div>
+<div class="paragraph"><p><strong>Rating</strong>: One can provide a subjective overall rating of the dive on a
+5-point scale by clicking the appropriate star on the rating scale.</p></div>
+<div class="paragraph"><p><strong>Visibility</strong>: Similarly, one can provide a rating of visibility during the
+dive on a
+5-point scale by clicking the appropriate star.</p></div>
+<div class="paragraph"><p><strong>Tags</strong>: Tags that describe the type of dive performed may
+be entered here (separated by commas). Examples of common tags are boat, drift,
+training, cave etc. <em>Subsurface</em> has many built-in tags. Auto completion is once again offered.
+For instance, if <code>cav</code> was typed, then the tags <strong>cave</strong> and <strong>cavern</strong> are
+shown for the user to choose from.</p></div>
+<div class="paragraph"><p><strong>Notes</strong>: Any additional information can be typed here.</p></div>
+<div class="paragraph"><p>The <strong>Save</strong> and <strong>Cancel</strong> buttons are used to save all the information for
+tabs in the info panel and in the dive profile panel, so there&#8217;s no need to
+use them until ALL other information has been added. Here is an example of a
+completed Dive Notes panel:</p></div>
+<div class="imageblock" style="text-align:center;">
+<div class="content">
+<img src="images/CompletedDiveInfo_f20.jpg" alt="FIGURE: A completed Dive Notes tab" />
+</div>
+</div>
+</div>
+<div class="sect3">
+<h4 id="_equipment">4.1.2. Equipment</h4>
+<div class="paragraph"><p>The Equipment tab allows the user to enter information about the type of
+cylinder and gas used, as well as the weights used for a dive. This is a
+highly interactive part of <em>Subsurface</em> and the information on cylinders and
+gases (entered here) affects the behaviour of the dive profile (top
+right-hand panel).</p></div>
+<div class="paragraph" id="S_CylinderData"><p><strong>Cylinders</strong>: The cylinder information is entered through a dialogue that looks
+like this:</p></div>
+<div class="imageblock" style="text-align:center;">
+<div class="content">
+<img src="images/Gas_dialogue1_f20.jpg" alt="FIGURE:Initial cylinder dialogue" />
+</div>
+</div>
+<div class="paragraph"><p>The + button at the top right allows the user to add more cylinders for this
+dive.  The dark dustbin icon on the left allows one to delete information
+for a particular cylinder. Note that it is not possible to delete a cylinder
+if it is used during the dive. One cylinder is implicitly used in the dive,
+even without a gas change event. Thus the first cylinder cannot be deleted
+until another cylinder is created.</p></div>
+<div class="paragraph"><p>Start by selecting a cylinder type on the left-hand side of the table.  To
+select a cylinder, click in the <strong>Type</strong> box.  This brings up a button that
+can be used to display a dropdown list of cylinders:</p></div>
+<div class="imageblock" style="text-align:center;">
+<div class="content">
+<img src="images/Gas_dialogue2_f20.jpg" alt="FIGURE:The cylinder drop-down list button" />
+</div>
+</div>
+<div class="paragraph"><p>The drop-down list can be used to select the cylinder type used for the dive
+or the user may start typing in the box which shows the available options
+for the entered characters. The <strong>Size</strong> of the cylinder as well as its
+working pressure (<strong>WorkPress</strong>) will automatically be shown in the
+dialogue. If a cylinder is not shown in the dropdown list, type the name and
+description of that cylinder into the <strong>Type</strong> field.</p></div>
+<div class="paragraph"><p>Next, indicate the starting pressure and the ending pressure of the gas used
+during the dive. The unit of pressure (metric/imperial) corresponds to the
+setting in the <em>Preferences</em>.</p></div>
+<div class="paragraph"><p>Finally, type in the gas mixture used in the <strong>O2%</strong> field. If air was used, a
+value of 21% can be entered on this field, or it might be left blank. If
+nitrox or trimix were used, their percentages of oxygen and/or helium must
+be specified.  Any inappropriate fields should be left empty. After typing
+the information for the cylinder, press <em>ENTER</em> on the keyboard or click
+outside the cell that contains the cursor. Information for any additional
+cylinders can be added by using the + button at the top right
+hand. Following is an example of a complete description for a dive made
+using two cylinders (air and EAN50):</p></div>
+<div class="imageblock" style="text-align:center;">
+<div class="content">
+<img src="images/CylinderDataEntry3_f20.jpg" alt="FIGURE: a completed cylinder dive information table" />
+</div>
+</div>
+<div class="paragraph"><p><strong>Weights</strong>: Information about the weight system used during a dive can be entered
+using a dialogue very similar to that for the cylinder information. If the user
+clicks the + button on the top right of the weights dialogue, the table looks
+like this:</p></div>
+<div class="imageblock" style="text-align:center;">
+<div class="content">
+<img src="images/WeightsDataEntry1_f20.jpg" alt="FIGURE: The Weights dialogue" />
+</div>
+</div>
+<div class="paragraph"><p>If one then clicks on the <strong>Type</strong> field, a drop-down list becomes accessible
+through a down-arrow:</p></div>
+<div class="imageblock" style="text-align:center;">
+<div class="content">
+<img src="images/WeightsDataEntry2_f20.jpg" alt="FIGURE: Weights type drop-down list button" />
+</div>
+</div>
+<div class="paragraph"><p>The drop-down list can then be used to select the type of weight system or
+the user may start typing in the box which shows the available options for
+the entered characters. In the <strong>Weight</strong> field, the weight used during the
+dive must be typed. After typing the information for the weight system the
+user must either press <em>ENTER</em> on the keyboard or click outside the cell
+that contains the cursor. It is possible to enter information for more than
+one weight system by adding an additional system using the + button on the
+top right hand. Weight systems can be deleted using the dustbin icon on the
+left hand. Here is an example of information for a dive with two types of
+weights: integrated and a weight belt:</p></div>
+<div class="imageblock" style="text-align:center;">
+<div class="content">
+<img src="images/WeightsDataEntry3_f20.jpg" alt="FIGURE: A completed weights information table" />
+</div>
+</div>
+<div class="paragraph"><p>There&#8217;s NO need to click the <em>Save</em> button before the dive profile has been
+completed.</p></div>
+</div>
+<div class="sect3">
+<h4 id="S_CreateProfile">4.1.3. Creating a Dive Profile</h4>
+<div class="paragraph"><p>The <strong>Dive Profile</strong> (a graphical representation of the depth of the dive as a
+function of time) is indicated in the panel on the top right hand of the
+<em>Subsurface</em> window. When a dive is manually added to a logbook,
+<em>Subsurface</em> presents a default dive profile that needs to be modified to
+best represent the dive being described:</p></div>
+<div class="imageblock" style="text-align:center;">
+<div class="content">
+<img src="images/DiveProfile1_f20.jpg" alt="FIGURE: Initial dive profile" />
+</div>
+</div>
+<div class="paragraph"><p><em>Modifying the dive profile</em>: When the cursor is moved around the dive
+profile, its position is indicated by two coloured lines (red and green) as
+shown below.  The depth and time that the cursor represents are indicated at
+the top of the black information box (@ and D). The units (metric/imperial)
+on the axes are determined by the <strong>Preference</strong> settings. The dive profile
+itself comprises several line segments demarcated by waypoints (white dots
+on the profile, as shown above). The default dive depth is 15 m.  If the
+dive depth was 20 m then the user needs to drag the appropriate waypoints
+downwards to represent 20 m. To add a waypoint, double-click on any line
+segment. To move an additional waypoint, drag it.  To remove this waypoint,
+right-click on it and choose "Remove this point" from the context menu. The
+user needs to drag the waypoints to represent an accurate time duration for
+the dive. Below is a dive profile that represents a dive to 20 m for 30 min,
+followed by a 5 minute safety stop at 5 m.</p></div>
+<div class="imageblock" style="text-align:center;">
+<div class="content">
+<img src="images/DiveProfile2_f20.jpg" alt="FIGURE: Edited dive profile" />
+</div>
+</div>
+<div class="paragraph"><p><em>Specifying the gas composition:</em> The gas composition used is clearly
+indicated along the line segments of the dive profile. This defaults to the
+first gas mixture specified in the <strong>Equipment</strong> tab, which was air in the
+case of the profile illustrated above. The gas mixtures of segments of the
+dive profile can be edited. This is done by right-clicking on the particular
+waypoint and selecting the appropriate gas from the context menu. Changing
+the gas for a waypoint affects the gas shown in the segment <em>to the left</em> of
+that waypoint. Note that only the gases defined in the <strong>Equipment</strong> tab
+appear in the context menu.</p></div>
+<div class="imageblock" style="text-align:center;">
+<div class="content">
+<img src="images/DiveProfile3_f20.jpg" alt="FIGURE: Gas composition context menu" />
+</div>
+</div>
+<div class="paragraph"><p>Below is the profile of a dive to 25 m for 30 min and with a switch from air
+to EAN50 at the end of the duration at 20m. In this case the first cylinder
+in the <strong>Equipment</strong> tab contained air and the second cylinder contained
+EAN50.</p></div>
+<div class="imageblock" style="text-align:center;">
+<div class="content">
+<img src="images/DiveProfile4_f20.jpg" alt="FIGURE: Completed dive profile" />
+</div>
+</div>
+</div>
+<div class="sect3">
+<h4 id="_saving_the_hand_entered_dive_information">4.1.4. Saving the hand-entered dive information</h4>
+<div class="paragraph"><p>The information entered in the <strong>Dive Notes</strong> tab, the <strong>Equipment</strong> tab as well
+as the <strong>Dive Profile</strong> can now be saved in the user&#8217;s logbook by using the
+two buttons on the top right hand of the Dive Notes tab. If the <em>Save</em>
+button is clicked, the dive data are saved in the current logbook. If the
+<em>Cancel</em> button is clicked, the newly entered dive data are discarded. When
+exiting <em>Subsurface</em>, the user will be prompted once more to save the
+logbook with the new dive(s).</p></div>
+</div>
+</div>
+<div class="sect2">
+<h3 id="S_ImportDiveComputer">4.2. Importing new dive information from a Dive Computer</h3>
+<div class="sect3">
+<h4 id="_connecting_and_importing_data_from_a_dive_computer">4.2.1. Connecting and importing data from a dive computer.</h4>
+<div class="paragraph"><p>The use of dive computers allows the collection of a large amount of
+information about each dive, e.g. a detailed record of depth, duration,
+rates of ascent/descent and of gas partial pressures. <em>Subsurface</em> can
+capture this information and present it as part of the dive information,
+using dive information from a wide range of dive computers. The latest list
+of supported dive computers can be found at:
+<a href="http://subsurface-divelog.org/documentation/supported-dive-computers/">
+Supported dive computers</a>.</p></div>
+<div class="admonitionblock">
+<table><tr>
+<td class="icon">
+<img src="images/icons/warning2.png" alt="Warning" />
+</td>
+<td class="content">Several dive computers consume more power when they are in their
+PC-Communication mode. <strong>This could drain the dive computer&#8217;s battery</strong>. We
+therefore recommend that the user checks if the dive computer is charged
+when connected to the USB port of a PC. For example, several Suunto and
+Mares dive computers do not recharge through the USB connection. Users
+should refer to the dive computer&#8217;s manual if they are unsure whether the
+dive computer recharges its batteries while connected to the USB port.</td>
+</tr></table>
+</div>
+<div class="paragraph"><p>To import dive information from a dive computer to a computer with
+<em>Subsurface</em>, it is necessary that the two pieces of equipment communicate
+with one another.  This involves setting up the communications port (or
+mount point) of the computer with <em>Subsurface</em> that communicates with the
+dive computer. In order to set up this communication, one needs to find the
+appropriate information to instruct <em>Subsurface</em> where and how to import the
+dive information.
+<a href="#_appendix_a_operating_system_specific_information_for_importing_dive_information_from_a_dive_computer">Appendix
+A</a> provides the technical information to help the user achieving this for
+different operating systems and
+<a href="#_appendix_b_dive_computer_specific_information_for_importing_dive_information">Appendix
+B</a> has dive computer specific information.</p></div>
+<div class="paragraph"><p>After this, the dive computer can be hooked up to the user&#8217;s PC, which can
+be achieved by following these steps:</p></div>
+<div class="olist arabic"><ol class="arabic">
+<li>
+<p>
+The interface cable should be connected to a free USB port (or the Infra-red
+        or Bluetooth connection set up as described later in this manual)
+</p>
+</li>
+<li>
+<p>
+The dive computer should be placed into PC Communication mode.
+        (Users should refer to the manual of their specific dive computer)
+</p>
+</li>
+</ol></div>
+<div class="paragraph"><p>In <em>Subsurface</em>, from the Main Menu, the user must select <em>Import &#8594; Import
+From Dive Computer</em>.  Dialogue <strong>A</strong> in the figure below appears:</p></div>
+<div class="imageblock" style="text-align:center;">
+<div class="content">
+<img src="images/ImportFromDC1_f20.jpg" alt="FIGURE: Download dialogue 1" />
+</div>
+</div>
+<div class="paragraph"><p>Dive computers tend to keep a certain number of dives in their memory, even
+though these dives have already been imported to <em>Subsurface</em>. For that
+reason <em>Subsurface</em> only imports dives that have not been uploaded
+before. This makes the download process faster on most dive computers and
+also saves battery power of the dive computer (at least for those not
+charging while connected via USB).  If, for some reason, the user wishes to
+import ALL dives from the dive computer, even though some may already be in
+the logbook, then check the check box labelled <em>Force download of all
+dives</em>.</p></div>
+<div class="paragraph"><p>The dialogue has two drop-down lists, <strong>Vendor</strong> and <strong>Dive Computer</strong>. On the
+<strong>vendor</strong> drop-down list select the make of the computer, e.g.  Suunto,
+Oceanic, Uwatec, Mares. On the <strong>Dive Computer</strong> drop-down list, the model
+name of the dive computer must be selected, e.g. D4 (Suunto), Veo200
+(Oceanic), or Puck (Mares).</p></div>
+<div class="paragraph"><p>The <strong>Device or Mount Point</strong> drop-down list contains the USB or Bluetooth
+port name that <em>Subsurface</em> needs in order to communicate with the dive
+computer.  The appropriate port name must be selected. Consult
+<a href="#_appendix_a_operating_system_specific_information_for_importing_dive_information_from_a_dive_computer">Appendix
+A</a> and
+<a href="#_appendix_b_dive_computer_specific_information_for_importing_dive_information">Appendix
+B</a> for technical details on how to find the appropriate port information for
+a particular dive computer and, in some cases, how to do the correct
+settings to the operating system of the computer on which <em>Subsurface</em> is
+running.</p></div>
+<div class="ulist"><ul>
+<li>
+<p>
+If all the dives on the dive computer need to be downloaded, check the
+   checkbox <em>Force download of all dives</em>. Normally, <em>Subsurface</em> only
+   downloads dives after the date-time of the last dive in the <strong>Dive List</strong>
+   panel. If one or more of your dives in <em>Subsurface</em> have been accidentally
+   deleted or if there are older dives that still need to be downloaded from
+   the dive computer, this checkbox needs to be activated. Some dive computers
+   (e.g. Mares Puck) do not provide a contents list to <em>Subsurface</em> before the
+   download in order to select only new dives.  Consequently, for these dive
+   computers, all dives are downloaded irrespective of the status of this check
+   box.
+</p>
+</li>
+<li>
+<p>
+If the checkbox <em>Always prefer downloaded dives</em> has been checked and,
+   during download, dives with identical date-times exist on the dive computer
+   and on the <em>Subsurface</em> <strong>Dive List</strong> panel, the record in the <em>Subsurface</em>
+   divelog will be overwritten by the record from the dive computer
+</p>
+</li>
+<li>
+<p>
+Do <strong>not</strong> check the checkboxes labelled <em>Save libdivecomputer logfile</em> and
+    <em>Save libdivecomputer dumpfile</em>. These are only used as diagnostic tools
+    when problems with downloads are experienced (see below).
+</p>
+</li>
+</ul></div>
+<div class="paragraph"><p>The <em>OK</em> button must then be clicked. Dialogue <strong>B</strong> in the figure above
+appears.</p></div>
+<div class="paragraph"><p>With communication established, one can see how the data are retrieved from
+the dive computer.  Depending on the make of the dive computer and/or number
+of recorded dives, this could take some time. The user should be
+patient. The <em>Download</em> dialogue shows a progress bar at the bottom of the
+dialogue (for some dive computers the progress information could be
+inaccurate as we cannot determine how much downloadable data there is until
+all data have been downloaded). When the download of the dive information is
+complete, all the imported dives appear in the <strong>Dive List</strong>, sorted by date
+and time. Disconnect and switch off the dive computer to conserve its
+battery power.  If a particular dive is selected, the <strong>Dive Profile</strong> panel
+shows an informative graph of dive depth against time for that particular
+dive.</p></div>
+<div class="paragraph"><p>If there is a problem in communicating with the dive computer, an error
+message will be shown, similar to this text: "Unable to open /dev/ttyUSB0
+Mares (Puck Pro)". Refer to the text in the box below.</p></div>
+<div class="sidebarblock">
+<div class="content">
+<div class="paragraph"><p><strong>PROBLEMS WITH DATA DOWNLOAD FROM A DIVE COMPUTER?</strong></p></div>
+<div class="admonitionblock">
+<table><tr>
+<td class="icon">
+<img src="images/icons/important.png" alt="Important" />
+</td>
+<td class="content">Check the following:</td>
+</tr></table>
+</div>
+<div class="paragraph"><p>Is the dive computer still in PC-communication or Upload mode?</p></div>
+<div class="paragraph"><p>Is the battery of the dive computer fully charged? If not then the battery
+must be charged or replaced.</p></div>
+<div class="paragraph"><p>Is the connecting cable faulty? Does the cable work perfectly using other
+software? Has it worked before, or is this the first time the cable is being
+used? Are the contacts on the dive computer and the cable clean?</p></div>
+<div class="paragraph"><p>Consult
+<a href="#_appendix_a_operating_system_specific_information_for_importing_dive_information_from_a_dive_computer">Appendix
+A</a> and make sure that the correct Mount Point was specified (see above).</p></div>
+<div class="paragraph"><p>On Unix-like operating systems, does the user have write permission to the
+USB port? If not, consult
+<a href="#_appendix_a_operating_system_specific_information_for_importing_dive_information_from_a_dive_computer">Appendix
+A</a></p></div>
+<div class="paragraph"><p>If the <em>Subsurface</em> computer does not recognise the USB adaptor by showing
+an appropriate device name next to the Mount Point, then there is a
+possibility that the cable or USB adaptor is faulty. A faulty cable is the
+most common cause of communication failure between dive computer and
+<em>Subsurface</em> computer. It is also possible that the <em>Subsurface</em> computer
+cannot interpret the data. Perform a download for diagnostic purposes with
+the following two check boxes checked in the download dialogue discussed
+above:</p></div>
+<div class="literalblock">
+<div class="content">
+<pre><code>Save libdivecomputer logfile
+Save libdivecomputer dumpfile</code></pre>
+</div></div>
+<div class="paragraph"><p><strong>Important</strong>: These check boxes are only used when problems are encountered
+during the download process: under normal circumstances they should not be checked.
+When checking these boxes, the user is prompted to select a folder to
+save the information to. The default folder is the one in which the <em>Subsurface</em>
+dive log is kept.</p></div>
+<div class="paragraph"><p><strong>Important:</strong> <em>After downloading with the above checkboxes
+checked, no dives are added to the
+<strong>Dive List</strong> but two files are created in the folder selected above</em>:</p></div>
+<div class="literalblock">
+<div class="content">
+<pre><code>subsurface.log
+subsurface.bin</code></pre>
+</div></div>
+<div class="paragraph"><p>These files should be send to the <em>Subsurface</em> mail list:
+<em>subsurface@subsurface-divelog.org</em> with a request for the files to be
+analysed. Provide the dive computer make and model as well as contextual
+information about the dives recorded on the dive computer.</p></div>
+</div></div>
+</div>
+<div class="sect3">
+<h4 id="S_DeviceNames">4.2.2. Changing the name of a dive computer</h4>
+<div class="paragraph"><p>It may be necessary to distinguish between different dive computers used to
+upload dive logs to <em>Subsurface</em>. For instance if one&#8217;s partner&#8217;s dive
+computer is the same make and model as one&#8217;s own and dive logs are uploaded
+from both dive computers to the same <em>Subsurface</em> computer, then one would
+perhaps like to call one dc "Alice&#8217;s Suunto D4" and the other one "Bob&#8217;s
+Suunto D4". Alternatively, perhaps a technical diver dives with two or more
+dive computers of the same model, the logs of both (or all) being uploaded.
+In this case it might be prudent to call one of them "Suunto D4 (1)" and
+another one "Suunto D4 (2)". This is easily done in <em>Subsurface</em>.  On the
+<strong>Main Menu</strong>, select <em>Log &#8594; Edit device names</em>. A dialog opens, indicating
+the current Model, ID and Nickname of the dive computers used for
+upload. Edit the Nickname field for the appropriate dive computer. After
+saving the Nickname, the dive logs show the nickname for that particular
+device instead of the model name, allowing easy identification of devices.</p></div>
+</div>
+<div class="sect3">
+<h4 id="S_EditDiveInfo">4.2.3. Updating the dive information imported from the dive computer.</h4>
+<div class="paragraph"><p>The information from the dive computer is not complete and more details must
+be added in order to have a fuller record of the dives. To do this, the
+<strong>Dive Notes</strong> and the <strong>Equipment</strong> tabs on the top left hand of the
+<em>Subsurface</em> window should be used.</p></div>
+</div>
+<div class="sect3">
+<h4 id="_dive_notes_2">4.2.4. Dive Notes</h4>
+<div class="paragraph"><p>The date and time of the dive, gas mixture and (often) water temperature is
+shown as obtained from the dive computer, but the user needs to add
+additional information by hand in order to have a more complete dive
+record.  If the contents of this tab is changed or edited in any way, the
+message in a blue box at the top of the panel indicates that the dive is
+being edited. If one clicks on the <strong>Dive Notes</strong> tab, the following fields
+are visible:</p></div>
+<div class="imageblock" style="text-align:center;">
+<div class="content">
+<img src="images/AddDive3_f20.jpg" alt="FIGURE: The Dive Notes tab" />
+</div>
+</div>
+<div class="paragraph"><p>The <strong>Time</strong> field reflects the date and time of the dive. By clicking the
+date, a calendar is displayed from which one can choose the correct
+date. Press ESC to close the calendar.  The time values (hour and minutes)
+can also be edited directly by clicking on each of them in the text box and
+by overtyping the information displayed.</p></div>
+<div class="paragraph"><p><strong>Air/water temperatures</strong>: Air and water temperatures during the dive are shown
+in these fields to the right of the Start time. Many dive computers supply water
+temperature information and this field may therefore contain information obtained from the dive computer.
+If air temperature is not provided by the dive computer, the first temperature reading
+might be used for the air temperature. Generally this is close enough to the real air temperature as
+the change in the temperature sensor reading is quite slow to follow the changes in the environment.
+If editing is required, only a value is required, the units of temperature will be
+automatically supplied by
+<em>Subsurface</em> (according to the <em>Preferences</em>, metric or imperial units will
+be used).</p></div>
+<div class="paragraph"><p><strong>Location</strong>: In this field one should type in text that describes the site
+where the dive was performed, e.g. "Tihany, Lake Balaton, Hungary".
+Auto completion of location names will
+make this easier if one frequently dives at the same sites.</p></div>
+<div class="paragraph"><p><strong>Coordinates</strong>: The geographic coordinates of the dive site should be entered
+here. These can come from three sources:</p></div>
+<div class="paragraph"><p>The user can find the coordinates on the world map in the bottom right hand
+part of the Subsurface window. The map displays a green bar indicating "Move
+the map and double-click to set the dive location". Double-click at the
+appropriate place, the green bar disappears and the coordinates are stored.</p></div>
+<div class="paragraph"><p>The user can obtain the coordinates from the <em>Subsurface</em> Companion app if
+an Android device with GPS was used and if the coordinates of the dive site
+were stored using that device.  <a href="#S_Companion">Click here for more
+information</a></p></div>
+<div class="paragraph"><p>The coordinates can be entered by hand if they are known, using one of four
+formats with latitude followed by longitude:</p></div>
+<div class="literalblock">
+<div class="content">
+<pre><code>ISO 6709 Annex D format e.g. 30°13'28.9"N 30°49'1.5"E
+Degrees and decimal minutes, e.g. N30° 13.49760' , E30° 49.30788'
+Degrees minutes seconds, e.g. N30° 13' 29.8" , E30° 49' 1.5"
+Decimal degrees, e.g. 30.22496 , 30.821798</code></pre>
+</div></div>
+<div class="paragraph"><p>Southern hemisphere latitudes are given with a <strong>S</strong>, e.g. S30°, or with a
+negative value, e.g. -30.22496. Similarly, western longitudes are given with
+a <strong>W</strong>, e.g. W07°, or with a negative value, e.g. -7.34323.</p></div>
+<div class="paragraph"><p>Please note that GPS coordinates of a dive site are linked to the Location
+name - so adding coordinates to dives that do not have a location
+description will cause unexpected behaviour (Subsurface will think that all
+of these dives have the same location and try to keep their GPS coordinates
+the same).</p></div>
+<div class="paragraph"><p><strong>Divemaster</strong>: The name of the dive master or dive guide for this dive should be
+entered in this field
+which offers auto completion based on the list of dive masters in
+the current logbook.</p></div>
+<div class="paragraph"><p><strong>Buddy</strong>: In this field, one enters the name(s) of the buddy / buddies
+(separated with commas) who accompanied him/her on the
+dive. Auto completion based on the list of buddies in the current logbook is
+offered.</p></div>
+<div class="paragraph"><p><strong>Suit</strong>: Here the type of diving suit used for the dive can be entered.
+Auto completion of the suit description is available.
+Some dry-suit users may choose to use this field to record what combination of
+suit and thermal protection undersuit was used.</p></div>
+<div class="paragraph"><p><strong>Rating</strong>: One can provide a subjective overall rating of the dive on a
+5-point scale by clicking the appropriate star on the rating scale.</p></div>
+<div class="paragraph"><p><strong>Visibility</strong>: Similarly, one can provide a rating of visibility during the
+dive on a
+5-point scale by clicking the appropriate star.</p></div>
+<div class="paragraph"><p><strong>Tags</strong>: Tags that describe the type of dive performed can be entered
+here (separated by commas). Examples of common tags are boat, drift, training,
+cave, etc.
+<em>Subsurface</em> has many built-in tags. If the user starts typing a tag, the
+program
+will list the tags that correspond to the typing. For instance, if the user
+typed
+<code>cav</code>, then the tags <strong>cave</strong> and <strong>cavern</strong> are shown for the user to choose from.</p></div>
+<div class="paragraph"><p><strong>Notes</strong>: Any additional information for the dive can be entered here.</p></div>
+<div class="paragraph"><p>The <strong>Save</strong> and <strong>Cancel</strong> buttons are used to save all the information for
+tabs in the info panel and in the dive profile panel, so there&#8217;s no need to
+use them until ALL other information has been added. Here is an example of a
+completed Dive Notes panel:</p></div>
+<div class="imageblock" style="text-align:center;">
+<div class="content">
+<img src="images/CompletedDiveInfo_f20.jpg" alt="FIGURE: A completed Dive Notes tab" />
+</div>
+</div>
+</div>
+<div class="sect3">
+<h4 id="_equipment_2">4.2.5. Equipment</h4>
+<div class="paragraph"><p>The Equipment tab allows one to enter information about the type of cylinder
+and gas used as well as the weights used for the dive. The message in a blue
+box at the top of the panel:</p></div>
+<div class="imageblock" style="text-align:center;">
+<div class="content">
+<img src="images/BlueEditBar_f20.jpg" alt="FIGURE: Blue edit bar" />
+</div>
+</div>
+<div class="paragraph"><p>indicates that the dive is being edited. This is a highly interactive part
+of <em>Subsurface</em> and the information on cylinders and gases (entered here)
+determines the behaviour of the dive profile (top right-hand panel).</p></div>
+<div class="paragraph"><p><strong>Cylinders</strong>: The cylinder information is entered through a dialogue that looks
+like this:</p></div>
+<div class="imageblock" style="text-align:center;">
+<div class="content">
+<img src="images/DC_gas-dialogue1_f20.jpg" alt="FIGURE: Initial cylinder dialogue" />
+</div>
+</div>
+<div class="paragraph"><p>In most cases <em>Subsurface</em> obtains the gas used from the dive computer and
+automatically inserts the gas composition(% oxygen) in the table. The<br />
+button at the top right allows the user to add more cylinders for this
+dive. The dark dustbin icon on the left allows the deletion of information
+for a cylinder.  Note that it is not possible to delete a cylinder if it is
+used during the dive. A cylinder might be implicitly used in the dive, even
+without a gas change event.</p></div>
+<div class="paragraph"><p>The user should start by selecting a cylinder type on the left-hand side of
+the table.  To select a cylinder, the <strong>cylinder type</strong> box should be
+clicked. This brings up a list button that can be used to display a dropdown
+list of cylinders:</p></div>
+<div class="imageblock" style="text-align:center;">
+<div class="content">
+<img src="images/DC_gas-dialogue2_f20.jpg" alt="FIGURE: The cylinder drop-down list button" />
+</div>
+</div>
+<div class="paragraph"><p>The drop-down list can then be used to select the cylinder type that was
+used for this dive or the user may start typing in the box which shows the
+available options for the entered characters. The <strong>Size</strong> of the cylinder as
+well as its working pressure (<strong>WorkPress</strong>) will automatically be shown in
+the dialogue.</p></div>
+<div class="paragraph"><p>Next one must indicate the starting pressure and the ending pressure of the
+specified gas during the dive. The unit of pressure (metric/imperial)
+corresponds to the settings chosen in the <em>Preferences</em>.</p></div>
+<div class="paragraph"><p>Finally, provide the gas mixture used. If air was used, the value of 21% can
+be entered or this field can be left blank. If nitrox or trimix were used,
+their percentages of oxygen and/or helium should be entered.  Any
+inappropriate fields should be left empty. After typing the information for
+the cylinder, either press <em>ENTER</em> on the keyboard or click outside the cell
+that contains the cursor. Information for any additional cylinders can be
+added by using the + button at the top right hand. Following is an example
+of a complete description for a dive using two cylinders (air and EAN50):</p></div>
+<div class="imageblock" style="text-align:center;">
+<div class="content">
+<img src="images/CylinderDataEntry3_f20.jpg" alt="FIGURE: a completed cylinder dive information table" />
+</div>
+</div>
+<div class="paragraph"><p><strong>Weights</strong>: Information about the weight system used can be entered
+using a dialogue very similar to that of the cylinder information. If one
+clicks
+the + button on the top right of the weights dialogue, the table looks like
+this:</p></div>
+<div class="imageblock" style="text-align:center;">
+<div class="content">
+<img src="images/WeightsDataEntry1_f20.jpg" alt="FIGURE:The Weights dialogue" />
+</div>
+</div>
+<div class="paragraph"><p>By clicking on the <strong>Type</strong> field, a drop-down list becomes accessible through
+a down-arrow:</p></div>
+<div class="imageblock" style="text-align:center;">
+<div class="content">
+<img src="images/WeightsDataEntry2_f20.jpg" alt="FIGURE:Weights type drop-down list button" />
+</div>
+</div>
+<div class="paragraph"><p>The drop-down list can then be used to select the type of weight system used
+during the dive or the user may start typing in the box which shows the
+available options for the entered characters.  In the <strong>Weight</strong> field, type
+in the amount of weight used during the dive. After specifying the weight
+system, the user can either press <em>ENTER</em> on the keyboard or click outside
+the cell with the cursor.  It is possible to enter information for more than
+one weight system by adding an additional system using the + button on the
+top right hand. Weight systems can be deleted using the dustbin icon on the
+left hand. Here is an example of information for a dive with two types of
+weights: integrated as well as a weight belt:</p></div>
+<div class="imageblock" style="text-align:center;">
+<div class="content">
+<img src="images/WeightsDataEntry3_f20.jpg" alt="FIGURE: A completed weights information table" />
+</div>
+</div>
+</div>
+<div class="sect3">
+<h4 id="_editing_several_selected_dives_simultaneously">4.2.6. Editing several selected dives simultaneously</h4>
+<div class="paragraph"><p><em>METHOD 1</em>: After uploading dives from a dive computer, the dive profiles of
+the uploaded dives are shown in the <strong>Dive profile</strong> tab, as well as a few
+items of information in the <strong>Dive Notes</strong> tab (e.g. water temperature) and in
+the <strong>Equipment</strong> tab (e.g. gas pressures and gas composition). However the
+other fields remain empty.  It may be useful to simultaneously edit some of
+the fields in the <strong>Dive Notes</strong> and <strong>Equipment</strong> tabs.  For instance, it is
+possible that a diver performed several dives during a single day, using
+identical equipment while diving at the same dive site or with the same dive
+master and/or buddy or tags. Instead of completing the information for each
+of these dives separately, one can select all the dives for that day in the
+<strong>Dive List</strong> and insert the same information in the <strong>Dive Notes</strong> and
+<strong>Equipment</strong> fields that need identical information. This is achieved by
+editing the dive notes or the equipment for any one of the selected dives.</p></div>
+<div class="paragraph"><p>The simultaneous editing only works with fields that do not already contain
+information.  This means that, if some fields have been edited for a
+particular dive among the selected dives, these are not changed while
+editing the dives simultaneously. Technically, the rule for editing several
+dives simultaneously is: if the data field being edited contains <em>exactly
+the same information</em> for all the dives that have been selected, the new,
+edited information is substituted for all the selected dives, otherwise only
+the edited dive is changed, even though several dives have been selected in
+the <strong>Dive List</strong>. This greatly speeds up the completion of the dive log after
+several similar dives.</p></div>
+<div class="paragraph" id="S_CopyComponents"><p><em>METHOD 2</em>:There is a different way of achieving the same goal. Select a
+dive with all the appropriate information typed into the <strong>Dive Notes</strong> and
+<strong>Equipment</strong> tabs. Then, from the main menu, select <em>Log &#8594; Copy dive
+components</em>.  A box is presented with a selection of check boxes for most of
+the fields in the <strong>Dive Notes</strong> and <strong>Equipment</strong> tabs.  Select the fields to
+be copied from the currently selected dive, then select <em>OK</em>. Now, in the
+<strong>Dive List</strong>, select the dives into which this information is to be
+pasted. Then, from the main menu, select <em>Log &#8594; Paste dive components</em>.
+All the selected dives now contain the data initially selected in the
+original source dive log.</p></div>
+</div>
+<div class="sect3">
+<h4 id="_adding_bookmarks_to_a_dive">4.2.7. Adding Bookmarks to a dive</h4>
+<div class="paragraph"><p>Many divers wish to annotate their dives with text that indicate particular
+events during the dive, e.g. "Saw dolphins", or "Released surface
+buoy". This is easily done:</p></div>
+<div class="paragraph"><p>Right-click at the appropriate point on the dive profile.  This brings up
+the dive profile context menu. Select <em>Add bookmark</em>. A red flag is placed
+on the dive profile at the point that was initially selected (see <strong>A</strong>
+below).</p></div>
+<div class="ulist"><ul>
+<li>
+<p>
+Right-click on the red flag. This brings up the context menu (see <strong>B</strong>
+   below). Select <em>Edit name</em>.
+</p>
+</li>
+</ul></div>
+<div class="paragraph"><p>A text box is shown. Type the explanatory text for the bookmark (see <strong>C</strong>
+below). Select <em>OK</em>.  This saves the text associated with the bookmark.</p></div>
+<div class="paragraph"><p>If one hovers using the mouse over the red bookmark, the appropriate text is
+shown at the bottom of the information box (see <strong>D</strong> below).</p></div>
+<div class="imageblock" style="text-align:center;">
+<div class="content">
+<img src="images/Bookmarks.jpg" alt="FIGURE: Bookmark dialog" />
+</div>
+</div>
+</div>
+<div class="sect3">
+<h4 id="_saving_the_updated_dive_information">4.2.8. Saving the updated dive information</h4>
+<div class="paragraph"><p>The information entered in the <strong>Dive Notes</strong> tab and the <strong>Equipment</strong> tab can
+be saved by using the two buttons on the top right hand of the <strong>Dive Notes</strong>
+tab. If the <em>Save</em> button is clicked, the dive data are saved. If the
+<em>Cancel</em> button is clicked, then the newly entered dive data are deleted,
+although the dive profile obtained from the dive computer will be
+retained. When the user exits <em>Subsurface</em> there is a final prompt to
+confirm that the new data should be saved.</p></div>
+</div>
+</div>
+<div class="sect2">
+<h3 id="_importing_dive_information_from_other_digital_data_sources_or_other_data_formats">4.3. Importing dive information from other digital data sources or other data formats</h3>
+<div class="paragraph" id="S_ImportingAlienDiveLogs"><p>If a user has been diving for some time, it is possible that several dives
+were logged using other dive log software. This information does not need
+retyping because these dive logs can probably be imported into
+<em>Subsurface</em>. <em>Subsurface</em> will import dive logs from a range of other dive
+log software. While some software is supported natively, for others the user
+has to export the logbook(s) to an intermediate format so that they can then
+be imported by <em>Subsurface</em>.  Currently, <em>Subsurface</em> supports importing CSV
+log files from several sources.  APD LogViewer, XP5, Sensus and Seabear
+files are preconfigured, but because the import is flexible, users can
+configure their own imports.  Manually kept log files (e.g. in spreadsheet)
+can also be imported by configuring the CSV import.  <em>Subsurface</em> can also
+import UDDF and UDCF files used by some divelog software and some dive
+computers, like the Heinrichs &amp; Weikamp DR5. Finally, for some divelog
+software like Mares Dive Organiser it is currently suggested to import the
+logbooks first into a webservice like <em>divelogs.de</em> and then import them
+from there with <em>Subsurface</em>, as divelogs.de supports a few additional
+logbook formats that <em>Subsurface</em> currently cannot parse.</p></div>
+<div class="paragraph"><p>If the format of other software is supported natively on Subsurface, it
+should be sufficient to select either <em>Import&#8594;Import log files</em> or
+<em>File&#8594;Open log file</em>. <em>Subsurface</em> supports the data formats of many dive
+computers, including Suunto and Shearwater. When importing dives,
+<em>Subsurface</em> tries to detect multiple records for the same dive and merges
+the information as best as it can. If there are no time zone issues (or
+other reasons that would cause the beginning time of the dives to be
+significantly different) <em>Subsurface</em> will not create duplicate entries.</p></div>
+<div class="sect3">
+<h4 id="_using_the_universal_import_dialogue">4.3.1. Using the universal import dialogue</h4>
+<div class="paragraph" id="Unified_import"><p>Importing dives from other software is performed through a universal
+interface that is activated by selecting <em>Import</em> from the Main Menu, then
+clicking on <em>Import Log Files</em>. This brings up the dialogue <strong>A</strong> below.</p></div>
+<div class="imageblock" style="text-align:center;">
+<div class="content">
+<img src="images/Import1_f20.jpg" alt="FIGURE: Import dialogue: step 1" />
+</div>
+</div>
+<div class="paragraph"><p>Towards the bottom right is a dropdown selector with a default label of
+<em>Dive Log Files</em> which gives access to the different types of direct imports
+available, as in dialogue <strong>B</strong>, above. Currently these are:</p></div>
+<div class="ulist"><ul>
+<li>
+<p>
+XML-formatted dive logs (DivingLog 5.0, MacDive and several other dive log
+   systems)
+</p>
+</li>
+<li>
+<p>
+UDDF-formatted dive logs (e.g. Kenozoooid)
+</p>
+</li>
+<li>
+<p>
+UDCF-formatted dive logs
+</p>
+</li>
+<li>
+<p>
+Poseidon MkVI CCR logs
+</p>
+</li>
+<li>
+<p>
+JDiveLog
+</p>
+</li>
+<li>
+<p>
+Suunto Dive Manager (DM3 and DM4)
+</p>
+</li>
+<li>
+<p>
+CSV (text-based and spreadsheet-based) dive logs, including APD CCR logs
+</p>
+</li>
+</ul></div>
+<div class="paragraph"><p>Selecting the appropriate file in the file list of the dialogue opens the
+imported dive log in the <em>Subsurface</em> <strong>Dive List</strong>. Some other formats, not
+accessible through the Import dialogue are also supported, as explained
+below.</p></div>
+</div>
+<div class="sect3">
+<h4 id="_importing_dive_logs_from_closed_circuit_rebreather_ccr_systems">4.3.2. Importing dive logs from closed circuit rebreather (CCR) systems</h4>
+<div class="admonitionblock">
+<table><tr>
+<td class="icon">
+<img src="images/APD.jpg" alt="Note" />
+</td>
+<td class="content">Closed system rebreathers use advanced technology to recirculate gas that
+has been breathed while doing two things to maintain a breathable oxygen
+concentration:
+a) remove carbon dioxide from the gas that has been exhaled
+regulate the oxygen concentration to remain within safe diving limits.
+Currently, within <em>Subsurface</em>, the Poseidon MkVI Discovery is the best
+supported CCR dive computer. The CCR interface of <em>Subsurface</em> is currently
+experimental and under active development. In contrast to a conventional
+open circuit dive computer, a CCR system computer does not allow the
+download of a log containing multiple dives. Rather, each dive is stored
+independently. This means that <em>Subsurface</em> cannot download a dive log
+directly from a CCR dive computer, but that it imports CCR dive logs in the
+same way that it imports dive log data from other databases.</td>
+</tr></table>
+</div>
+<div class="sect4">
+<h5 id="_import_a_ccr_dive">Import a CCR dive</h5>
+<div class="paragraph"><p>See the section dealing with <a href="#S_ImportingAlienDiveLogs">Importing dive
+information from other digital sources</a>. From the main menu of <em>Subsurface</em>,
+select <em>Import&#8594;Import log files</em> to bring up the
+<a href="#Unified_import">universal import dialogue</a>. As explained in the previous
+section, the bottom right hand of the import dialogue contains a dropdown
+list of appropriate devices that currently includes an option for MkVI
+files. Having selected the appropriate CCR format and the directory where
+the original dive logs have been stored from the CCR dive computer, one can
+select a particular dive log file (in the case of the MkVI it is a file with
+a .txt extension). After selecting the appropriate dive log, activate the
+<em>Open</em> button at the bottom right hand of the universal import dialogue.</p></div>
+</div>
+<div class="sect4">
+<h5 id="_displayed_information_for_a_dive">Displayed information for a  dive</h5>
+<div class="paragraph"><p><em>Partial pressures of gases</em>: The graph of oxygen partial pressure shows the
+information from the oxygen sensors of the CCR equipment. In the case of the
+Poseidon MKVI, the mean value of the two oxygen sensors are shown. In the
+case of the APD equipment, the mean of the three oxygen sensors are
+shown. If one sensor shows a very different oxygen PO2 reading compared to
+the others, the divergent sensor is ignored. For CCR dives the graph for
+oxygen partial pressure should be fairly flat, reflecting the setpoint
+settings during the dive.  Partial pressures for nitrogen (and helium, if
+applicable) are shown in the usual way as for other dives.</p></div>
+<div class="paragraph"><p><em>Cylinder pressures</em>: CCR dive computers like the Poseidon MkVI record the
+pressures of the oxygen and diluent cylinders. The pressure of the oxygen
+cylinder is shown on the dive profile. In addition, start and end pressures
+for both oxygen and diluent cylinders are shown in the <em>Equipment Tab</em>.</p></div>
+<div class="paragraph"><p><em>Equipment-specific information</em>: Equipment-specific information gathered by
+<em>Subsurface</em> is shown in the <em>Extra data</em> tab. This may include setup
+information or metadata about the dive.</p></div>
+<div class="paragraph"><p>More equipment-specific information for downloading CCR dive logs can be
+found in <a href="#S_PoseidonMkVI">Appendix B</a>.</p></div>
+</div>
+</div>
+<div class="sect3">
+<h4 id="_importing_from_mares_dive_organiser_v2_1">4.3.3. Importing from Mares Dive Organiser V2.1</h4>
+<div class="paragraph"><p>Since Mares utilise proprietary Windows software not compatible with
+multi-platform applications, these dive logs cannot be directly imported
+into <em>Subsurface</em>. Mares dive logs need to be imported using a three-step
+process, using <em>www.divelogs.de</em> as a mechanism to extract the dive log
+information.</p></div>
+<div class="paragraph"><p>The dive log data from Mares Dive Organiser need to be exported to the user&#8217;s
+desktop, using
+ a <em>.sdf</em> file name extension. Refer to <a href="#Mares_Export">Appendix C</a> for more
+information.
+Data should then be imported into <em>www.divelogs.de</em>. One needs to create a user
+account in
+<em>www.divelogs.de</em>, log into that web site, then
+select <em>Import Logbook &#8594; Dive Organiser</em> from the menu on the left hand side.
+The instructions must be carefully followed to transfer the dive information
+(in <em>.sdf</em> format) from the Dive Organiser database to <em>www.divelogs.de</em>.
+Finally,  import the dives
+from <em>divelogs.de</em> to <em>Subsurface</em>, using the instructions below.</p></div>
+</div>
+<div class="sect3">
+<h4 id="S_ImportingDivelogsDe">4.3.4. Importing dives from <strong>divelogs.de</strong></h4>
+<div class="paragraph"><p>The import of dive information from <em>divelogs.de</em> is simple, using a single
+dialogue box. The <em>Import&#8594;Import form Divelogs.de</em> option should be
+selected from the Main Menu. This brings up a dialogue box (see figure on
+left [<strong>A</strong>] below). Enter a user-ID and password for <em>divelogs.de</em> into the
+appropriate fields and then select the <em>Download</em> button. Download from
+<em>divelogs.de</em> starts immediately, displaying a progress bar in the dialogue
+box. At the end of the download, the success status is indicated (see figure
+on the right [<strong>B</strong>], below). The <em>Apply</em> button should then be selected,
+after which the imported dives appear in the <em>Subsurface</em> <strong>Dive List</strong> panel.</p></div>
+<div class="imageblock" style="text-align:center;">
+<div class="content">
+<img src="images/Divelogs1.jpg" alt="FIGURE:Download from Divelogs.de" />
+</div>
+</div>
+</div>
+<div class="sect3">
+<h4 id="S_ImportingCSVData">4.3.5. Importing data in CSV format</h4>
+<div class="paragraph"><p>A comma-separated file (.csv) can be used to import dive information either
+as dive profiles (as in the case of the APD Inspiration and Evolution closed
+circuit rebreathers) or as dive metadata (in case the user keeps dive data
+in a spreadsheet). For an introduction to CSV-formatted files see
+<a href="#S_CSV_Intro">A Diver&#8217;s Introduction To CSV Files</a>.</p></div>
+<div class="admonitionblock">
+<table><tr>
+<td class="icon">
+<img src="images/icons/important.png" alt="Important" />
+</td>
+<td class="content">The CSV import has a couple of caveats. You should avoid some special
+characters like ampersand (&amp;), less than (&lt;), greater than (&gt;) and double
+quotes ("), the latter if quoting text cells. The file should use UTF-8
+character set, if having non-ASCII characters. Also the size of the CSV file
+might cause problems. Importing 100 dives at a time (without dive profile)
+has worked previously, but larger files might exceed limits of the parser
+used. When having problems with CSV imports, try first with a smaller sample
+to make sure everything works.</td>
+</tr></table>
+</div>
+<div class="sect4">
+<h5 id="S_ImportingCSVDives">Importing dives in CSV format from dive computers or other dive log software</h5>
+<div class="paragraph"><p>CSV files are normally organised into a single line that provides the
+headers (or <em>field names</em>) of the data columns, followed by the data, one
+record per line. CSV files can be opened with a normal text editor.  For
+information of how to export a spreadsheet in CSV format see
+<a href="#S_Appendix_D">APPENDIX D: Exporting a spreadsheet to CSV format</a>.</p></div>
+<div class="paragraph"><p>Before being able to import the data to <em>Subsurface</em> one needs to know:</p></div>
+<div class="paragraph"><p>Which character separates the different columns within a single line of
+data? This field separator should be either a comma (,) or a TAB character.
+This can be determined by opening the file with a text editor. If it is
+comma-delimited, then the comma characters between the values are clearly
+visible. If no commas are evident and the numbers are aligned in columns,
+the file is probably TAB-delimited (i.e. it uses a TAB as a field separator,
+as in the above example).</p></div>
+<div class="paragraph"><p>Which data columns need to be imported into <em>Subsurface</em>? The Dive Time and
+Depth columns are always required. Open the file using a text editor and
+note the titles of the columns to be imported and their column positions.</p></div>
+<div class="olist loweralpha"><ol class="loweralpha">
+<li>
+<p>
+Is the numeric information (e.g. dive depth) in metric or in imperial unis?
+</p>
+</li>
+</ol></div>
+<div class="paragraph"><p>Armed with this information, importing the data into <em>Subsurface</em> is
+straightforward. Select <em>Import&#8594;Import Log Files</em> from the main menu. In
+the resulting file selection menu, select <em>CSV files</em>, after which a common
+configuration dialog appears for all the files with a CSV extension:</p></div>
+<div class="imageblock" style="text-align:center;">
+<div class="content">
+<img src="images/Import_CSV1.jpg" alt="FIGURE: CSV download dialogue" />
+</div>
+</div>
+<div class="paragraph"><p>There are pre-configured definitions for some dive computers, e.g. the APD
+rebreathers. If the user&#8217;s dive computer is on this list, it should be
+selected using the dropdown box labeled <em>Pre-configured imports</em>.</p></div>
+<div class="paragraph"><p>If the dive computer is not on the pre-configured list, the user must select
+the <em>Field Separator</em> (TAB or comma) for the particular CSV file, using the
+appropriate dropdown list. For each data column used for import, the user
+must check the appropriate check box and indicate in which column these data
+are found.</p></div>
+<div class="paragraph"><p>Finally <em>OK</em> should be clicked and the dive(s) are imported and listed in
+the <strong>Dive List</strong> tab of <em>Subsurface</em>.</p></div>
+</div>
+</div>
+<div class="sect3">
+<h4 id="S_ImportingManualCSV">4.3.6. Importing dives from a manually kept CSV file or a spreadsheet</h4>
+<div class="sidebarblock" id="S_CSV_Intro">
+<div class="content">
+<div class="paragraph"><p><strong>A Diver&#8217;s Introduction To CSV Files</strong></p></div>
+<div class="admonitionblock">
+<table><tr>
+<td class="icon">
+<img src="images/icons/important.png" alt="Important" />
+</td>
+<td class="content">CSV is an abbreviation for a data file format: <em>Comma-Separated
+Variables</em>. It is a file format allowing someone to view or edit the
+information using a text editor such as Notebook (Windows), gedit (Linux) or
+TextWrangler (OS/X). The two main advantages of the CSV format is that the
+data are easily editable as text without any proprietary software and
+ensuring all information is human-readable, not being obscured by the any
+custom or proprietary attributes that proprietary software insert into
+files.  Because of its simplicity the CSV format is used as an interchange
+format between many software packages, e.g. between spreadsheet,
+statistical, graphics, database and diving software. Within <em>Subsurface</em>,
+CSV files can also be used to import information from other sources such as
+spreadsheet-based dive logs and even from some dive computers.</td>
+</tr></table>
+</div>
+<div class="paragraph"><p>CSV files can be created or edited with a normal text editor. The most
+important attribute of a CSV file is the <em>field separator</em>, the character
+used to separate fields within a single line. The field separator is
+frequently a comma, a colon, a SPACE character or a TAB character. When
+exporting data from spreadsheet software, the field separator needs to be
+specified in order to create the CSV file. CSV files are normally organised
+into a single line that provides the headers (or <em>field names</em>) of the data
+columns, followed by the data, one record per line. Note that each field
+name may comprise more than one word separated by spaces; for instance <em>Dive
+site</em>, below. Here is an example of dive information for four dives using a
+comma as a field separator:</p></div>
+<div class="literalblock">
+<div class="content">
+<pre><code>Dive site,Dive date,Time,Dive_duration, Dive_depth,Dive buddy
+Illovo Beach,2012-11-23,10:45,46:15,18.4,John Smith
+Key Largo,2012-11-24,09:12,34:15,20.4,Jason McDonald
+Wismar Baltic,2012-12-01,10:13,35:27,15.4,Dieter Albrecht
+Pulau Weh,2012-12-20,09:46,55:56,38.6,Karaeng Bontonompo</code></pre>
+</div></div>
+<div class="paragraph"><p>In this format the data are not easily read by a human. Here is the same
+information in TAB-delimited format:</p></div>
+<div class="literalblock">
+<div class="content">
+<pre><code>Dive site       Dive date       Time    Dive_duration   Dive_depth      Dive buddy
+Illovo Beach    2012-11-23      10:45   46:15   18.4    John Smith
+Key Largo       2012-11-24      09:12   34:15   20.4    Jason McDonald
+Wismar Baltic   2012-12-01      10:13   35:27   15.4    Dieter Albrecht
+Pulau Weh       2012-12-20      09:46   55:56   38.6    Karaeng Bontonompo</code></pre>
+</div></div>
+<div class="paragraph"><p>It is clear why many people prefer the TAB-delimited format to the
+comma-delimited format. The disadvantage is that one cannot see the TAB
+characters. For instance, the space between <em>Dive</em> and <em>date</em> in the top
+line may be a SPACE character or a TAB character (in this case it is a SPACE
+character: the tabs are before and after <em>Dive date</em>). If the field names in
+the first line are long, the alignment with data in the other lines cannot
+be maintained. Here is a highly simplified and shortened TAB-delimited
+example of a CSV dive log from an APD closed-circuit rebreather (CCR) dive
+computer:</p></div>
+<div class="literalblock">
+<div class="content">
+<pre><code>Dive Time (s)   Depth (m)       pO₂ - Setpoint (Bar)  pO₂ - C1 Cell 1 (Bar) Ambient temp. (Celsius)
+0       0.0     0.70    0.81    13.1
+0       1.2     0.70    0.71    13.1
+0       0.0     0.70    0.71    13.1
+0       1.2     0.70    0.71    13.2
+0       1.2     0.70    0.71    13.1
+10      1.6     0.70    0.72    12.7
+20      1.6     0.70    0.71    12.6
+30      1.7     0.70    0.71    12.6
+40      1.8     0.70    0.68    12.5</code></pre>
+</div></div>
+<div class="paragraph"><p>CSV files can therefore be used in many contexts for importing data into a
+<em>Subsurface</em> dive log.</p></div>
+<div class="paragraph"><p>An important aspect of the CSV format required by <em>Subsurface</em> is the
+<em>Column Mapping</em>. In the example from different dive sites above, each line
+of data is organised as follows:</p></div>
+<div class="literalblock">
+<div class="content">
+<pre><code>Column 1:       Dive site (location)
+Column 2:       Dive date
+Column 3:       Dive time
+Column 4:       Dive duration
+Column 5:       Maximum dive depth (m)
+Column 6:       Name of dive buddy</code></pre>
+</div></div>
+<div class="paragraph"><p><em>Subsurface</em> requires the column number of each of these data items. For
+these data the column specification may look like this:</p></div>
+<div class="imageblock" style="text-align:center;">
+<div class="content">
+<img src="images/CSV_column_definition.jpg" alt="FIGURE: CSV column definition" />
+</div>
+</div>
+<div class="paragraph"><p>Knowledge of a few basic things about he content of the CSV file allows a
+smooth import of the dives into <em>Subsurface</em>.</p></div>
+</div></div>
+<div class="paragraph"><p>If one keeps dive logs in a spreadsheet, there is an option to import those
+dives, exported as a CSV file. See <a href="#S_Appendix_D">APPENDIX D: Exporting a
+spreadsheet to CSV format</a> for information of how to export a spreadsheet in
+CSV format.  When importing manually kept log files into <em>Subsurface</em>, the
+information needed is quite different from that accessible using a dive
+computer, as we are importing only summary data, not depth profile samples.</p></div>
+<div class="paragraph"><p>When importing dives in CSV format (see above), one needs to know the
+internal format of the CSV data to import.</p></div>
+<div class="paragraph"><p>Which character separates the different columns within a single line of
+data? A recommended field separator for the export is TAB, as commas might
+be part of the decimal data values themselves. Therefore the use of an
+appropriate field separator is very important. When exporting data from a
+spreadsheet it is likely to request the user to supply an appropriate field
+separator character.</p></div>
+<div class="paragraph"><p>Which columns need to be imported into <em>Subsurface</em>? Currently there are not
+any mandatory input fields, but some, e.g. dive duration are crucial for the
+log file to make any sense. Possible options can be seen in the image below
+and one should include as many as possible of the fields available in the
+original log file.</p></div>
+<div class="paragraph"><p>Units used for depth, weight and temperature. We consider depth to be either
+feet or meters, weight kilograms or pounds and temperature either Celsius or
+Fahrenheit. However, the users can select <em>Metric</em> or <em>Imperial</em> in the
+<strong>Preferences</strong> tab of <em>Subsurface</em>. No mixture of unit systems is allowed for
+the different fields.</p></div>
+<div class="paragraph"><p>Importing manually kept CSV log files is quite straight forward, but there
+might be many fields and counting the field numbers is error
+prone. Therefore validation of the data to be imported is critical.</p></div>
+<div class="paragraph"><p>To import the dives, select <em>Import&#8594;Import Log Files</em> from the menu bar. If
+the CSV option in the dropdown list is selected and the file list includes
+file names ending with .CSV, one can select the <em>Manual dives</em> tab that will
+bring up the following configuration dialog:</p></div>
+<div class="imageblock" style="text-align:center;">
+<div class="content">
+<img src="images/Import_CSV2.jpg" alt="FIGURE: Download dialog for Manual CSV logs" />
+</div>
+</div>
+<div class="paragraph"><p>Check the check boxes corresponding to the data in the original import
+file.  For each of the checked data items, a corresponding column number
+needs to be entered. For instance in the image above, the name of the dive
+site (i.e. location)  is located as the 11th item (or column) on each line
+of the CSV import file.  The input fields can be configured as appropriate,
+and when everything is done the <em>OK</em> button should be selected to perform
+the import. New dives should appear in the <strong>Dive List</strong> area of <em>Subsurface</em>.</p></div>
+</div>
+</div>
+<div class="sect2">
+<h3 id="S_Companion">4.4. Importing GPS coordinates with the <em>Subsurface Companion App</em> for mobile phones</h3>
+<div class="paragraph"><p>Using the <strong>Subsurface Companion App</strong> on an Android device with a GPS, the
+coordinates for the diving location can be automatically passed to the
+<em>Subsurface</em> dive log. The Companion App stores the dive locations on a
+dedicated Internet-based file server. <em>Subsurface</em>, in turn, can collect the
+localities from the file server.</p></div>
+<div class="paragraph"><p>To do this:</p></div>
+<div class="sect3">
+<h4 id="_create_a_companion_app_account">4.4.1. Create a Companion App account</h4>
+<div class="paragraph"><p>Register on the <a href="http://api.hohndel.org/login/"><em>Subsurface companion web
+page</em></a>.  A confirmation email with instructions and a personal <strong>DIVERID</strong>
+will be sent, a long number that gives access to the file server and
+Companion App capabilities.</p></div>
+<div class="paragraph"><p>Download the app from
+<a href="https://play.google.com/store/apps/details?id=org.subsurface">Google Play
+Store</a> or from
+<a href="http://f-droid.org/repository/browse/?fdfilter=subsurface&amp;fdid=org.subsurface">F-Droid</a>.</p></div>
+</div>
+<div class="sect3">
+<h4 id="_using_the_subsurface_companion_app_on_a_smartphone">4.4.2. Using the Subsurface companion app on a smartphone</h4>
+<div class="paragraph"><p>On first use the app has three options:</p></div>
+<div class="paragraph"><p><em>Create a new account.</em> Equivalent to registering in <em>Subsurface</em> companion
+page using an Internet browser. One can request a <strong>DIVERID</strong> using this
+option, but this is supplied via email and followed up by interaction with
+the <a href="http://api.hohndel.org/login/"><em>Subsurface companion web page</em></a> in order
+to activate the account.</p></div>
+<div class="paragraph"><p><em>Retrieve an account.</em> If users forgot their <strong>DIVERID</strong> they will receive an
+email to recover the number.</p></div>
+<div class="paragraph"><p><em>Use an existing account.</em> Users are prompted for their <strong>DIVERID</strong>. The app
+saves this <strong>DIVERID</strong> and does not ask for it again unless one uses the
+<em>Disconnect</em> menu option (see below).</p></div>
+<div class="admonitionblock">
+<table><tr>
+<td class="icon">
+<img src="images/icons/important.png" alt="Important" />
+</td>
+<td class="content">In the <em>Subsurface</em> main program, the <strong>DIVERID</strong> should also be entered on
+the Default Preferences panel, obtained by selecting
+<em>File&#8594;Preferences&#8594;Defaults</em> from the main menu in <em>Subsurface</em> itself.
+This facilitates synchronisation between <em>Subsurface</em> and the Companion App.</td>
+</tr></table>
+</div>
+<div class="sect4">
+<h5 id="_creating_new_dive_locations">Creating new dive locations</h5>
+<div class="paragraph"><p>Now one is ready to get a dive position and send it to the server. The
+Android display will look like the left hand image (<strong>A</strong>) below, but without
+any dives.</p></div>
+<div class="paragraph"><p>Touch the "+" icon on the top right to add a new dive site, a menu will be
+showed with 3 options:</p></div>
+<div class="paragraph"><p>Current: A prompt for a place name (or a request to activate the GPS if it
+is turned off) will be displayed, after which the current location is saved.</p></div>
+<div class="paragraph"><p>Use Map: This option allows the user to fix a position by searching a world
+map. A world map is shown (see <strong>B</strong> below) on which one should indicate the
+desired position with a <em>long press</em> on the touch sensitive screen (if the
+marked location is erroneous, simply indicate a new location)  and select
+the check symbol in the upper right. A dialog is shown allowing to enter the
+name of the dive location and the date-time of the dive (see <strong>C</strong> below). In
+order to import this dive location in <em>Subsurface</em> it&#8217;s advisable to set the
+time to agree with the time of that dive on the dive computer.</p></div>
+<div class="imageblock" style="text-align:center;">
+<div class="content">
+<img src="images/Companion_5.jpg" alt="FIGURE: Companion App, add location using map" />
+</div>
+</div>
+<div class="paragraph"><p>Import local GPX file: The android device searches for .gpx files and
+located archives will be shown. The selected .gpx file is opened and the
+stored locations shown. Now one needs to select the appropriate locations,
+then select the tab in the upper right, after which the locations will be
+sent to the web service and added to the list on the Android device.</p></div>
+</div>
+<div class="sect4">
+<h5 id="_dive_lists_of_dive_locations">Dive lists of dive locations</h5>
+<div class="paragraph"><p>The main screen shows a list of dive locations, each with a name, date and
+time (see <strong>A</strong> below). Some locations may have an arrow-up icon over the
+selection box to the left indicating that they require upload to the
+server. One can select individual dive locations from the list. A selected
+location has a check mark in the selection box on the left. Group operations
+(such as <em>Delete</em> or <em>Send</em>)  are performed on several locations that are
+selected.</p></div>
+<div class="paragraph"><p>Dive locations in this list can be viewed in two ways: a list of locations
+or a map indicating the dive locations. The display mode (List or Map) is
+changed by selecting <em>Dives</em> at the top left of the screen (see <strong>A</strong> below)
+and then selecting the display mode. The display mode can be changed either
+from the list of locations or from the map (see <strong>B</strong> below). If one selects a
+location (on the list or on the map), an editing panel opens (see <strong>C</strong> below)
+where the dive description or other details may be changed.</p></div>
+<div class="imageblock" style="text-align:center;">
+<div class="content">
+<img src="images/Companion_4.jpg" alt="FIGURE: Companion App, add location using map" />
+</div>
+</div>
+<div class="paragraph"><p>When one clicks on a dive (<strong>not</strong> selecting the check box), the name given to
+it, date/time and GPS coordinates will be shown, with two options at the top
+of the screen:</p></div>
+<div class="ulist"><ul>
+<li>
+<p>
+Edit (pencil): Change the text name or other characteristics of the dive
+  location.
+</p>
+</li>
+<li>
+<p>
+Maps: Display a map showing the dive location.
+</p>
+</li>
+</ul></div>
+<div class="paragraph"><p>After editing and saving a dive location (see <strong>C</strong> above), one needs to
+upload it to the web service, as explained below.</p></div>
+</div>
+<div class="sect4">
+<h5 id="_uploading_dive_locations">Uploading dive locations</h5>
+<div class="paragraph"><p>There are several ways to send locations to the server.  The easiest is by
+simply selecting the locations (See <strong>A</strong> below) and then touching the right
+arrow at the top right of the screen.</p></div>
+<div class="admonitionblock">
+<table><tr>
+<td class="icon">
+<img src="images/icons/important.png" alt="Important" />
+</td>
+<td class="content">Users must be careful, as the trash icon on the right means exactly what it
+should; it deletes the selected dive location(s).</td>
+</tr></table>
+</div>
+<div class="imageblock" style="text-align:center;">
+<div class="content">
+<img src="images/Companion_1.jpg" alt="FIGURE: Screen shots (A-B) of companion app" />
+</div>
+</div>
+<div class="paragraph"><p>After a dive trip using the Companion App, all dive locations are ready to
+be downloaded to a <em>Subsurface</em> dive log (see below).</p></div>
+</div>
+<div class="sect4">
+<h5 id="_settings_on_the_companion_app">Settings on the Companion app</h5>
+<div class="paragraph"><p>Selecting the <em>Settings</em> menu option results in the right hand image above
+(<strong>B</strong>).</p></div>
+</div>
+<div class="sect4">
+<h5 id="_server_and_account">Server and account</h5>
+<div class="ulist"><ul>
+<li>
+<p>
+<em>Web-service URL.</em> This is predefined (<a href="http://api.hohndel.org/">http://api.hohndel.org/</a>)
+</p>
+</li>
+</ul></div>
+<div class="paragraph"><p><em>User ID.</em> The DIVERID obtained by registering as described above. The
+easiest way to obtain it is simply to copy and paste from the confirmation
+email but, of course, users can also type this information.</p></div>
+</div>
+<div class="sect4">
+<h5 id="_synchronisation">Synchronisation</h5>
+<div class="paragraph"><p><em>Synchronize on startup.</em> If selected, dive locations in the Android device
+and those on the web service synchronise each time the app is started.</p></div>
+<div class="paragraph"><p><em>Upload new dives.</em> If selected, each time the user adds a dive location it
+is automatically sent to the server.</p></div>
+</div>
+<div class="sect4">
+<h5 id="_background_service">Background service</h5>
+<div class="paragraph"><p>Instead of entering a unique dive location, users can leave the service
+running in the background of their Android device, allowing the continuous
+collection of GPS locations.</p></div>
+<div class="paragraph"><p>The settings below define the behaviour of the service:</p></div>
+<div class="paragraph"><p><em>Min duration.</em> In minutes. The app will try to get a location every X
+minutes until stopped by the user.</p></div>
+<div class="ulist"><ul>
+<li>
+<p>
+<em>Min distance.</em> In meters. Minimum distance between two locations.
+</p>
+</li>
+<li>
+<p>
+<em>Name template.</em> The name the app will use when saving the locations.
+</p>
+</li>
+</ul></div>
+<div class="admonitionblock">
+<table><tr>
+<td class="icon">
+<img src="images/icons/info.jpg" alt="Tip" />
+</td>
+<td class="content"><em>How does the background service work?</em> Assuming the user sets 5 minutes and
+50 meters in the settings above, the app will start by recording a location
+at the current location, followed by another one at every 5 minutes <strong>or</strong>
+every time one moves 50m from previous location.  If subsequent locations
+are within a radius of 50 meters from the previous one, a new location is
+not saved. If the user is not moving, only one location is saved, but if the
+user is moving, a trace of the route is obtained by saving a location every
+50 meters.</td>
+</tr></table>
+</div>
+</div>
+<div class="sect4">
+<h5 id="_other">Other</h5>
+<div class="paragraph"><p><em>Mailing List.</em> The mail box for <em>Subsurface</em>. Users can send an email to
+the Subsurface mailing list.</p></div>
+<div class="ulist"><ul>
+<li>
+<p>
+<em>Subsurface website.</em> A link to the URL of Subsurface web
+</p>
+</li>
+<li>
+<p>
+<em>Version.</em> Displays the current version of the Companion App.
+</p>
+</li>
+</ul></div>
+</div>
+<div class="sect4">
+<h5 id="_search">Search</h5>
+<div class="paragraph"><p>Search the saved dive locations by name or by date and time.</p></div>
+</div>
+<div class="sect4">
+<h5 id="_start_service">Start service</h5>
+<div class="paragraph"><p>Initiates the <em>background service</em> following the previously defined
+settings.</p></div>
+</div>
+<div class="sect4">
+<h5 id="_disconnect">Disconnect</h5>
+<div class="paragraph"><p>This is a badly named option that disconnects the app from the server by
+resetting the user ID in the app, showing the first screen where an account
+can be created, retrieve the ID for an existing account or use the users own
+ID. The disconnect option is useful if a user&#8217;s Android device was used to
+download the dive locations of another registered diver.</p></div>
+</div>
+<div class="sect4">
+<h5 id="_send_all_locations">Send all locations</h5>
+<div class="paragraph"><p>This option sends all locations stored in the Android device to the server.</p></div>
+</div>
+</div>
+<div class="sect3">
+<h4 id="_downloading_dive_locations_to_the_em_subsurface_em_divelog">4.4.3. Downloading dive locations to the <em>Subsurface</em> divelog</h4>
+<div class="paragraph"><p>Download dive(s) from a dive computer or enter them manually into
+<em>Subsurface</em> before obtaining the GPS coordinates from the server. The
+download dialog can be reached via <em>Ctrl+G</em> or from the <em>Subsurface</em> Main
+Menu <em>Import &#8594; Import GPS data from Subsurface Service</em>, resulting in the
+image on the left (<strong>A</strong>), below. On first use the DIVERID text box is
+blank. Provide a DIVERID, then select the <em>Download</em> button to initiate the
+download process, after which the screen on the right (<strong>B</strong>) below appears:</p></div>
+<div class="imageblock" style="text-align:center;">
+<div class="content">
+<img src="images/DownloadGPS.jpg" alt="FIGURE: Downloading Companion app GPS data" />
+</div>
+</div>
+<div class="paragraph"><p>Note that the <em>Apply</em> button is now active. By clicking on it, users can
+update the locations of the newly entered or uploaded dives in <em>Subsurface</em>
+which applies the coordinates and names entered on the app for all the new
+dives that match the date-times of the uploaded GPS localities. If one has
+entered the name of the dive location in <em>Subsurface</em> before downloading the
+GPS coordinates, this name will take precedence over downloaded one.</p></div>
+<div class="paragraph"><p>Since <em>Subsurface</em> matches GPS locations from the Android device and dive
+information from the dive computer based on date-time data, automatic
+assignment of GPS data to dives is dependent on agreement of the date-time
+information between these two devices. Although <em>Subsurface</em> has a wide
+range tolerance, it may be unable to identify the appropriate dive if there
+is a large difference between the time in the dive computer and that of the
+Android device, resulting in no updates.</p></div>
+<div class="paragraph"><p>Similar date-times may not always be possible and there may be many reasons
+for this (e.g. time zones), or <em>Subsurface</em> may be unable to decide which is
+the correct position for a dive (e.g. on repetitive dives while running
+<em>background service</em> there may be several locations that would be included
+in the time range that fit not only the first dive, but one or more
+subsequent dives as well).  A workaround for this situation to manually edit
+the date-time of a dive in the <em>Subsurface</em> Dive List <strong>before</strong> downloading
+the GPS data and then to change the date-time back again <strong>after</strong> downloading
+GPS data.</p></div>
+<div class="admonitionblock">
+<table><tr>
+<td class="icon">
+<img src="images/icons/info.jpg" alt="Note" />
+</td>
+<td class="content">TIPS:</td>
+</tr></table>
+</div>
+<div class="paragraph"><p><em>Background service</em>, being a very powerful tool, may fill the location list
+with many unnecessary locations not corresponding to the exact dive point
+but reflecting the boat&#8217;s route.  Currently these locations are difficult to
+delete from the server. In some situations it is therefore prudent to clean
+up the list on the Android device before sending the dive points to the web
+server by simply deleting the inappropriate locations. This might be
+necessary, for instance, if one wants to keep the location list clear to see
+dives in the web service map display (see above).</p></div>
+<div class="paragraph"><p>It may also make sense to give informative names to the locations sent to
+the web server, or at least to use an informative name in the <em>Name
+Template</em> setting while running the <em>background service</em>, especially on a
+dive trip with many dives and dive locations.</p></div>
+</div>
+</div>
+<div class="sect2">
+<h3 id="S_LoadImage">4.5. Adding photographs to dives</h3>
+<div class="paragraph"><p>Many (if not most) divers take a camera with them and take photographs
+during a dive. One would like to associate each photograph with a specific
+dive. <em>Subsurface</em> allows one to load photos into a dive. Photos are
+superimposed on the dive profile, from where they can be viewed.</p></div>
+<div class="sect3">
+<h4 id="_loading_photos_and_getting_synchronisation_between_dive_computer_and_camera">4.5.1. Loading photos and getting synchronisation between dive computer and camera</h4>
+<div class="paragraph"><p>Left-lick on a dive or on a group of dives on the dive list. Then
+right-click on this dive or group of dives and choose the option <em>Load
+Images</em>:</p></div>
+<div class="imageblock" style="text-align:center;">
+<div class="content">
+<img src="images/LoadImage1_f20.jpg" alt="FIGURE: Load images option" />
+</div>
+</div>
+<div class="paragraph"><p>The system file browser appears. Select the folder and photographs that need
+to be loaded into <em>Subsurface</em> and click the <em>Open</em> button.</p></div>
+<div class="imageblock" style="text-align:center;">
+<div class="content">
+<img src="images/LoadImage2_f20.jpg" alt="FIGURE: Load images option" />
+</div>
+</div>
+<div class="paragraph"><p>This brings one to the time synchronisation dialog, shown below. The
+critical problem is that the time synchronisation is not perfect between the
+dive computer used during a dive, and the camera used during that same
+dive. These two devices often differ by several minutes. If <em>Subsurface</em> can
+achieve synchronisation, then the exact times of photographs can be used to
+position photographs on the dive profile.</p></div>
+<div class="paragraph"><p><em>Subsurface</em> achieves this synchronisation in two ways:</p></div>
+<div class="paragraph"><p><strong>Manually</strong>: If the user wrote down the exact camera time at the start of a dive, the
+difference in time between the two devices can be determined. Actually, as long as the device
+settings for time has not been changed in either device, one could write down the times of
+both devices after the dive or even at the end of the day. One can then manually set the time
+difference in the <em>Time shift</em> dialog. Towards the top of the dialog is a time setting tool
+immediately under the heading <em>Shift times of image(s) by</em>, evident in figure <strong>A</strong> below.
+If the camera time is 7 minutes later than that of the dive computer, set the time setting
+tool to a value of 00:07.  Select either the <em>earlier</em> or <em>later</em> radio button.
+In the above example, the <em>earlier</em> option is appropriate, since the photos need to be shifted
+7 minutes earlier (camera is 7 minutes ahead of dive computer). Ignore any "AM" or "PM" suffix
+in that tool. Click the <em>OK</em> button and synchronisation is achieved.</p></div>
+<div class="imageblock" style="text-align:center;">
+<div class="content">
+<img src="images/LoadImage3b_f20.jpg" alt="FIGURE: Synchronisation dialog" />
+</div>
+</div>
+<div class="paragraph"><p><strong>By photograph</strong>: There is a very slick way of achieving synchronisation. If one takes a
+photograph of the face of the dive computer showing the time, then <em>Subsurface</em> can obtain
+the exact time the photograph was taken, using the metadata that the camera stores within
+each photo. In order to do this, use the bottom half of the Time shift_ dialog. If one uses
+the bottom part, the top part of the dialog is ignored. Click on
+the horizontal bar entitled "<em>Select image of divecomputer showing time</em>. This brings up
+a file browser with which one can select the photograph of the dive computer. Select the
+photograph using the file browser and click on <em>OK</em>. This photograph of the dive computer
+appears in the bottom panel of the <em>Shift times</em> dialog. Now <em>Subsurface</em> knows exactly
+when the photograph has been taken. Now set the date-time dialog to the left of the photo
+so that this tool reflects the date and time of the dive computer in the photo. When the
+date-time tool has been set, <em>Subsurface</em> knows exactly what the time difference between
+camera and dive computer is, and synchronisation is achieved. There is a
+photograph with the face of the dive computer and with the date-time tool set to the
+date-time on image <strong>B</strong> above.</p></div>
+<div class="paragraph"><p>If the timestamp of a photograph is long before or after the dive, it is not
+placed on the dive profile. If the timestamp of the photo is within 30
+minutes of the dive, it is shown.</p></div>
+</div>
+<div class="sect3">
+<h4 id="_viewing_the_photos">4.5.2. Viewing the photos</h4>
+<div class="paragraph"><p>In order to view the photos added to a dive, activate the <em>show-photos</em>
+button in the tool bar to the left of the dive profile:</p></div>
+<div class="imageblock" style="text-align:left;">
+<div class="content">
+<img src="images/icons/ShowPhotos_f20.png" alt="FIGURE:Show photos toolbar button" />
+</div>
+</div>
+<div class="paragraph"><p>After the images have been loaded, they appear in two places:</p></div>
+<div class="ulist"><ul>
+<li>
+<p>
+the <em>Photos</em> tab of the <strong>Dive Notes</strong> panel.
+</p>
+</li>
+<li>
+<p>
+as tiny icons (stubs) on the dive profile at the appropriate positions
+   reflecting the time each photograph was taken. See below:
+</p>
+</li>
+</ul></div>
+<div class="imageblock" style="text-align:center;">
+<div class="content">
+<img src="images/LoadImage4_f20.jpg" alt="FIGURE: Photos on dive profile" />
+</div>
+</div>
+<div class="paragraph"><p>If one hovers with the mouse over any of the photo icons, then a thumbnail
+photo is shown of the appropriate photo. See the image below:</p></div>
+<div class="imageblock" style="text-align:center;">
+<div class="content">
+<img src="images/LoadImage5_f20.jpg" alt="FIGURE:Thumbnail photo on dive profile" />
+</div>
+</div>
+<div class="paragraph"><p>Clicking on the thumbnail brings up a full size photo overlaid on the
+<em>Subsurface</em> window. This allows good viewing of the photographs that have
+been added (see the image below). Note that the thumbnail has a small
+dustbin icon in the bottom right hand corner (see image above). If one
+selects the dustbin, the image is removed from the dive. Therefore some care
+is required when clicking on a thumbnail. Images can also be deleted using
+the <em>Photos</em> tab (see text below).</p></div>
+<div class="imageblock" style="text-align:center;">
+<div class="content">
+<img src="images/LoadImage6_f20.jpg" alt="FIGURE: Full-screen photo on dive profile" />
+</div>
+</div>
+</div>
+<div class="sect3">
+<h4 id="_the_em_photos_em_tab">4.5.3. The <em>Photos</em> tab</h4>
+<div class="paragraph"><p>Photographs associated with a dive are shown as thumbnails in the <em>Photos</em>
+tab of the <em>Dive Notes</em> panel. Photos taken in rapid succession during a
+dive (therefore sometimes with large overlap on the dive profile) can easily
+be accessed in the <em>Photos</em> tab. This tab serves as a tool for individually
+accessing the photos of a dive, while the stubs on the dive profile give an
+indication of when during a dive a photo was taken. By single-clicking on a
+thumbnail in the <em>Photos</em> panel, a photo is selected. By double-clicking a
+thumbnail, the full-sized image is shown, overlaying the <em>Subsurface</em>
+window. A photo can be deleted from the <em>Photos</em> panel by selecting it
+(single-click) and then by pressing the <em>Del</em> key on the keyboard. This
+removes the photo both from the <em>Photos</em> tab as well as the dive profile.</p></div>
+</div>
+<div class="sect3">
+<h4 id="_photos_on_an_external_hard_disk">4.5.4. Photos on an external hard disk</h4>
+<div class="paragraph"><p>Most underwater photographers store their photos on an external drive. If
+such a drive can be mapped (almost always the case) the photos can be
+directly accessed by <em>Subsurface</em>. This facilitates the interaction between
+<em>Subsurface</em> and an external repository of photos. When associating a dive
+profile with photos from an external drive, the normal procedure of
+selection and synchronisation (see text above) is used.  However, after the
+external drive has been disconnected, <em>Subsurface</em> cannot access these
+photos any more.  If the display of photos is activated (using the toolbox
+to the left of the <em>Dive Profile</em>), the program only shows a small white dot
+where each photo should be on the dive profile.  In addition the <em>Photos</em>
+tab only shows the file names of the photos. This is normal behaviour.  If,
+later, the external drive with the photos is connected again, the photos can
+be seen in the normal way.</p></div>
+</div>
+</div>
+<div class="sect2">
+<h3 id="_logging_special_types_of_dives">4.6. Logging special types of dives</h3>
+<div class="sect3">
+<h4 id="_sidemount_dives">4.6.1. Sidemount dives</h4>
+<div class="paragraph"><p><em>Subsurface</em> easily handles dives involving more than one
+cylinder. Sidemount dive logging involves three steps:</p></div>
+<div class="paragraph"><p><strong>During the dive, recording cylinder switch events</strong>. Since sidemount diving normally involves two
+cylinders with air or with the same gas mixture, <em>Subsurface</em> distinguishes among these different
+cylinders. In contrast, most dive computers that allow gas switching only distinguish among different
+<em>gases</em> used, not among different <em>cylinders</em> used. This means that when sidemount dives are downloaded
+from these dive computers, the events of switching between cylinders with the same gas are not downloaded. This may mean
+that one may have to keep a written log of cylinder switch times using a slate, or (if the dive computer
+has this facility) marking each cylinder switch with a bookmark that can be retrieved later. Returning
+from a dive with the information about cylinder changes is the only tricky part of logging sidemount dives.
+<strong>Within <em>Subsurface</em> describe the cylinders used during the dive</strong>. The diver needs to provide the
+specifications of the different cylinders, using the <strong>Equipment</strong> tab of the <strong>Dive Info Panel</strong> (see
+image below where two 12 litre cylinder were used).
+<strong>Indicate cylinder change events on the <em>Subsurface</em> dive profile</strong>. Once the dive log has been imported
+from a dive computer into <em>Subsurface</em>, the cylinder switch events need to be indicated on the dive profile.
+Cylinder changes are recorded by right-clicking at the appropriate point on the dive profile and then
+selecting <em>Add gas change</em>. A list of the appropriate cylinders is shown with the
+currently used cylinder greyed out. In the image below Tank 1 is greyed out, leaving only Tank 2
+to be selected. Select the appropriate cylinder. The cylinder change is then indicated on the dive
+profile with a cylinder symbol. If the <strong>Tank Bar</strong> is activated using the toolbar to the left of the
+profile, then the cylinder change is also indicated on the Tank Bar (see image below). After all
+the cylinder change events have been recorded on the dive profile, the correct cylinder pressures
+for both cylinders are shown on the dive profile, as inthe image below.</p></div>
+<div class="imageblock" style="text-align:center;">
+<div class="content">
+<img src="images/sidemount1.jpg" alt="FIGURE: Sidemount profile" />
+</div>
+</div>
+</div>
+</div>
+</div>
+</div>
+<div class="sect1">
+<h2 id="_obtaining_more_information_about_dives_entered_into_the_logbook">5. Obtaining more information about dives entered into the logbook</h2>
+<div class="sectionbody">
+<div class="sect2">
+<h3 id="_the_strong_dive_info_strong_tab_for_individual_dives">5.1. The <strong>Dive Info</strong> tab (for individual dives)</h3>
+<div class="paragraph"><p>The Dive Info tab gives some summary information about a particular dive
+that has been selected in the <strong>Dive List</strong>. Useful information here includes
+the surface interval before the dive, the maximum and mean depths of the
+dive, the gas volume consumed, the surface air consumption (SAC) and the
+number of oxygen toxicity units (OTU) incurred.</p></div>
+<div class="admonitionblock">
+<table><tr>
+<td class="icon">
+<img src="images/icons/info.jpg" alt="Note" />
+</td>
+<td class="content">Gas consumption and SAC calculations: <em>Subsurface</em> calculates SAC and Gas
+consumption taking in account gas incompressibility, particularly at tank
+pressures above 200 bar, making them more accurate.  Users should refer to
+<a href="#SAC_CALCULATION">Appendix D</a> for more information.</td>
+</tr></table>
+</div>
+</div>
+<div class="sect2">
+<h3 id="_the_strong_extra_data_strong_tab_usually_for_individual_dives">5.2. The <strong>Extra Data</strong> tab (usually for individual dives)</h3>
+<div class="paragraph"><p>When using a dive computer, it often reports several data items that cannot
+easily be presented in a standardised way because the nature of the
+information differs from one dive computer to another. These data often
+comprise setup information, metadata about a dive, battery levels, no fly
+times, or gradient factors used during the dive. When possible, this
+information is presented in the <strong>Extra Data</strong> tab. Below is an image showing
+extra data for a dive using a Poseidon rebreather.</p></div>
+<div class="imageblock" style="text-align:center;">
+<div class="content">
+<img src="images/ExtraDataTab_f20.jpg" alt="FIGURE: Extra Data tab" />
+</div>
+</div>
+</div>
+<div class="sect2">
+<h3 id="_the_strong_stats_strong_tab_for_groups_of_dives">5.3. The <strong>Stats</strong> tab (for groups of dives)</h3>
+<div class="paragraph"><p>The Stats tab gives summary statistics for more than one dive, assuming that
+more than one dive has been selected in the <strong>Dive List</strong> using the standard
+Ctrl-click or Shift-click of the mouse. If only one dive has been selected,
+figures pertaining to only that dive are given. This tab shows the number of
+dives selected, the total amount of dive time in these dives, as well as the
+minimum, maximum and mean for the dive duration, water temperature and
+surface air consumption (SAC). It also shows the depth of the shallowest and
+deepest dives of those selected.</p></div>
+</div>
+<div class="sect2">
+<h3 id="S_DiveProfile">5.4. The <strong>Dive Profile</strong></h3>
+<div class="imageblock" style="text-align:center;">
+<div class="content">
+<img src="images/Profile2.jpg" alt="Typical dive profile" />
+</div>
+</div>
+<div class="paragraph"><p>Of all the panels in <em>Subsurface</em>, the Dive Profile contains the most
+detailed information about each dive. The Dive Profile has a <strong>button bar</strong> on
+the left hand side that allows control over several display options. The
+functions of these buttons are described below. The main item in the Dive
+Profile is the graph of dive depth as a function of time. In addition to the
+obvious information of the depth it also shows the ascent and descent rates
+compared to the recommended speed of going up or down in the water
+column. This information is given using different colours:</p></div>
+<div class="tableblock">
+<table rules="all"
+width="100%"
+frame="border"
+cellspacing="0" cellpadding="4">
+<col width="33%" />
+<col width="33%" />
+<col width="33%" />
+<tbody>
+<tr>
+<td align="left" valign="top"><p class="table"><strong>Colour</strong></p></td>
+<td align="left" valign="top"><p class="table"><strong>Descent speed (m/min)</strong></p></td>
+<td align="left" valign="top"><p class="table"><strong>Ascent speed (m/min)</strong></p></td>
+</tr>
+<tr>
+<td align="left" valign="top"><p class="table">Red</p></td>
+<td align="left" valign="top"><p class="table">&gt; 30</p></td>
+<td align="left" valign="top"><p class="table">&gt; 18</p></td>
+</tr>
+<tr>
+<td align="left" valign="top"><p class="table">Orange</p></td>
+<td align="left" valign="top"><p class="table">18 - 30</p></td>
+<td align="left" valign="top"><p class="table">9 - 18</p></td>
+</tr>
+<tr>
+<td align="left" valign="top"><p class="table">Yellow</p></td>
+<td align="left" valign="top"><p class="table">9 - 18</p></td>
+<td align="left" valign="top"><p class="table">4 - 9</p></td>
+</tr>
+<tr>
+<td align="left" valign="top"><p class="table">Light green</p></td>
+<td align="left" valign="top"><p class="table">1.5 - 9</p></td>
+<td align="left" valign="top"><p class="table">1.5 - 4</p></td>
+</tr>
+<tr>
+<td align="left" valign="top"><p class="table">Dark green</p></td>
+<td align="left" valign="top"><p class="table">&lt; 1.5</p></td>
+<td align="left" valign="top"><p class="table">&lt; 1.5</p></td>
+</tr>
+</tbody>
+</table>
+</div>
+<div class="paragraph"><p>The profile also includes depth readings for the peaks and troughs in the
+graph.  Thus, users should see the depth of the deepest point and other
+peaks. Mean depth is marked with a horizontal red line.</p></div>
+<div class="admonitionblock">
+<table><tr>
+<td class="icon">
+<img src="images/icons/scale.jpg" alt="Note" />
+</td>
+<td class="content">In some cases the dive profile does not fill the whole area of the <strong>Dive
+Profile</strong> panel. Clicking the <strong>Scale</strong> button in the toolbar on the left of
+the dive profile frequently increases the size of the dive profile to fill
+the area of the panel efficiently.</td>
+</tr></table>
+</div>
+<div class="paragraph"><p><strong>Water temperature</strong> is displayed with its own blue line with temperature values
+placed adjacent to significant changes.</p></div>
+<div class="paragraph"><p>The dive profile can include graphs of the <strong>partial pressures</strong> of O2, N2,
+and He during the dive (see figure above) as well as a calculated and dive
+computer reported deco ceilings (only visible for deep, long, or repetitive
+dives). Partial pressures of oxygen are indicated in green, those of
+nitrogen in black, and those of helium in dark red. These partial pressure
+graphs are shown below the profile data.</p></div>
+<div class="admonitionblock">
+<table><tr>
+<td class="icon">
+<img src="images/icons/O2.jpg" alt="Note" />
+</td>
+<td class="content">Clicking this button allows display of the partial pressure of <strong>oxygen</strong>
+during the dive. This is depicted below the dive depth and water temperature
+graphs.</td>
+</tr></table>
+</div>
+<div class="admonitionblock">
+<table><tr>
+<td class="icon">
+<img src="images/icons/N2.jpg" alt="Note" />
+</td>
+<td class="content">Clicking this button allows display of the partial pressure of <strong>nitrogen</strong>
+during the dive.</td>
+</tr></table>
+</div>
+<div class="admonitionblock">
+<table><tr>
+<td class="icon">
+<img src="images/icons/He.jpg" alt="Note" />
+</td>
+<td class="content">Clicking this button allows display of the partial pressure of <strong>helium</strong>
+during the dive.  This is only of importance to divers using Trimix,
+Helitrox or similar breathing gasses.</td>
+</tr></table>
+</div>
+<div class="paragraph"><p>The <strong>air consumption</strong> graph displays the tank pressure and its change during
+the dive. The air consumption takes depth into account so that even when
+manually entering the start and end pressures the graph is not a straight
+line.  Similarly to the depth graph the slope of the tank pressure gives the
+user information about the momentary SAC rate (Surface Air Consumption) when
+using an air integrated dive computer.  Here the colour coding is not
+relative to some absolute values but relative to the average normalised air
+consumption during the dive. So areas that are red or orange indicate times
+of increased normalized air consumption while dark green reflects times when
+the diver was using less gas than average.</p></div>
+<div class="admonitionblock">
+<table><tr>
+<td class="icon">
+<img src="images/icons/Heartbutton.png" alt="Note" />
+</td>
+<td class="content">Clicking on the heart rate button will allow the display of heart rate
+information during the dive if the dive computer was attached to a heart
+rate sensor.</td>
+</tr></table>
+</div>
+<div class="paragraph"><p>It is possible to <strong>zoom</strong> into the profile graph. This is done either by using
+the scroll wheel / scroll gesture of your mouse or trackpad. By default
+<em>Subsurface</em> always shows a profile area large enough for at least 30 minutes
+and 30m
+ (100ft) – this way short or shallow dives are intuitively recognizable;
+something
+that free divers clearly won’t care about.</p></div>
+<div class="imageblock" style="text-align:center;">
+<div class="content">
+<img src="images/MeasuringBar.png" alt="FIGURE: Measuring Bar" />
+</div>
+</div>
+<div class="admonitionblock">
+<table><tr>
+<td class="icon">
+<img src="images/icons/ruler.jpg" alt="Note" />
+</td>
+<td class="content">Measurements of <strong>depth or time differences</strong> can be achieved by using the
+<strong>ruler button</strong> on the left of the dive profile panel.  The measurement is
+done by dragging the red dots to the two points on the dive profile that the
+user wishes to measure. Information is then given in the horizontal white
+area underneath the two red dots.</td>
+</tr></table>
+</div>
+<div class="admonitionblock">
+<table><tr>
+<td class="icon">
+<img src="images/icons/ShowPhotos.png" alt="Note" />
+</td>
+<td class="content">Photographs that have been added to a dive can be shown on the profile by
+selecting the <strong>Show-photo</strong> button. The position of a photo on the profile
+indicates the exact time when this photo was taken. If this button is not
+active, the photos are hidden.</td>
+</tr></table>
+</div>
+<div class="paragraph"><p>The profile can also include the dive computer reported <strong>ceiling</strong> (more
+precisely, the deepest deco stop that the dive computer calculated for each
+particular moment in time) as a red overlay on the dive profile. Ascent
+ceilings arise when a direct ascent to the surface increases the risk of a
+diver suffering from decompression sickness (DCS) and it is necessary to
+either ascend slower or to perform decompression stop(s) before ascending to
+the surface. Not all dive computers record this information and make it
+available for download; for example all of the Suunto dive computers fail to
+make this very useful data available to divelog software. <em>Subsurface</em> also
+calculates ceilings independently, shown as a green overlay on the dive
+profile.  Because of the differences in algorithms used and amount of data
+available (and other factors taken into consideration at the time of the
+calculation) it is unlikely that ceilings from dive computers and from
+<em>Subsurface</em> are the same, even if the same algorithm and <em>gradient factors</em>
+(see below) are used.  It is also quite common that <em>Subsurface</em> calculates
+a ceiling for non-decompression dives when the dive computer stayed in
+non-deco mode during the whole dive (represented by the <span class="green">dark green</span>
+section in the profile at the beginning of this section). This is caused by
+the fact that <em>Subsurface’s</em> calculations describe the deco obligation at
+each moment during a dive, while dive computers usually take the upcoming
+ascent into account. During the ascent some excess nitrogen (and possibly
+helium) are already breathed off so even though the diver technically
+encountered a ceiling at depth, the dive still does not require an explicit
+deco stop. This feature allows dive computers to offer longer non-stop
+bottom times.</p></div>
+<div class="admonitionblock">
+<table><tr>
+<td class="icon">
+<img src="images/icons/cceiling.jpg" alt="Note" />
+</td>
+<td class="content">If the dive computer itself calculates a ceiling and makes it available to
+<em>Subsurface</em> during upload of dives, this can be shown as a red area by
+checking <strong>Dive computer reported ceiling</strong> button on the Profile Panel.</td>
+</tr></table>
+</div>
+<div class="admonitionblock">
+<table><tr>
+<td class="icon">
+<img src="images/icons/ceiling1.jpg" alt="Note" />
+</td>
+<td class="content">If the <strong>Calculated ceiling</strong> button on the Profile Panel is clicked, then a
+ceiling, calculated by <em>Subsurface</em>, is shown in green if it exists for a
+particular dive (<strong>A</strong> in figure below). This setting can be modified in two
+ways:</td>
+</tr></table>
+</div>
+<div class="admonitionblock">
+<table><tr>
+<td class="icon">
+<img src="images/icons/ceiling2.jpg" alt="Note" />
+</td>
+<td class="content">If, in addition, the <strong>show all tissues</strong> button on the Profile Panel is
+clicked, the ceiling is shown for the tissue compartments following the
+Bühlmann model (<strong>B</strong> in figure below).</td>
+</tr></table>
+</div>
+<div class="admonitionblock">
+<table><tr>
+<td class="icon">
+<img src="images/icons/ceiling3.jpg" alt="Note" />
+</td>
+<td class="content">If, in addition, the <strong>3m increments</strong> button on the Profile Panel is clicked,
+then the ceiling is indicated in 3 m increments (<strong>C</strong> in figure below).</td>
+</tr></table>
+</div>
+<div class="imageblock" style="text-align:center;">
+<div class="content">
+<img src="images/Ceilings2.jpg" alt="Figure: Ceiling with 3m resolution" />
+</div>
+</div>
+<div class="admonitionblock">
+<table><tr>
+<td class="icon">
+<img src="images/icons/ShowCylindersButton.jpg" alt="Note" />
+</td>
+<td class="content">By selecting this icon, the different cylinders used during a dive can be
+represented as a coloured bar at the bottom of the <strong>Dive Profile</strong>. In
+general oxygen is represented by a green bar, nitrogen with a yellow bar and
+helium with a red bar. The image below shows a dive which first uses a
+trimix cylinder (red and green), followed by a switch to a nitrox cylinder
+(yellow and green) after 23 minutes. Cylinders with air are shown as a light
+blue bar.</td>
+</tr></table>
+</div>
+<div class="imageblock" style="text-align:center;">
+<div class="content">
+<img src="images/ShowCylinders_f20.jpg" alt="Figure: Cylinder use graph" />
+</div>
+</div>
+<div class="admonitionblock">
+<table><tr>
+<td class="icon">
+<img src="images/tissues.jpg" alt="Note" />
+</td>
+<td class="content">Display inert gas tissue pressures relative to ambient inert gas pressure
+(horizontal grey line).  Tissue pressures are calculated using the Bühlmann
+ZH-L16 algorithm and are displayed as lines ranging from green (faster
+tissues) to blue (slower tissues).  The black line, graphed above the
+ambient pressure, is the maximum allowable tissue supersaturation (pressure
+limit) derived from the gradient factors specified in the <strong>Preferences</strong>. For
+divers involved in planned decompression diving, efficient rates of
+offgasing are obtained with tissue pressures between the ambient inert gas
+pressure (grey line) and the pressure limit (black line). This display is a
+representation of the tissue pressures during the whole dive. In contast,
+the <a href="#S_gas_pressure_graph">Gas Pressure Graph</a> in the <strong>Information Box</strong>
+on the <strong>Dive Profile</strong> is an instantaneous reflection of tissue pressures at
+the moment in time reflected by the position of the cursor on the dive
+profile.</td>
+</tr></table>
+</div>
+<div class="imageblock" style="text-align:center;">
+<div class="content">
+<img src="images/tissuesGraph.jpg" alt="Figure: Inert gas tissue pressure graph" />
+</div>
+</div>
+<div class="paragraph"><p>Gradient Factor settings strongly affect the calculated ceilings and their
+depths.  For more information about Gradient factors, see the section on
+<a href="#S_GradientFactors">Gradient Factor Preference settings</a>. The currently
+used gradient factors (e.g. GF 35/75) are shown above the depth profile if
+the appropriate toolbar buttons are activated.  <strong>N.B.:</strong> The indicated
+gradient factors are NOT the gradient factors in use by the dive computer,
+but those used by <em>Subsurface</em> to calculate deco obligations during the
+dive. For more information external to this manual see:</p></div>
+<div class="ulist"><ul>
+<li>
+<p>
+<a href="http://www.tek-dive.com/portal/upload/M-Values.pdf">Understanding M-values by Erik Baker, <em>Immersed</em> Vol. 3, No. 3.</a>
+</p>
+</li>
+<li>
+<p>
+<a href="http://www.rebreatherworld.com/general-and-new-to-rebreather-articles/5037-gradient-factors-for-dummies.html">Gradient factors for dummies, by Kevin Watts</a>
+</p>
+</li>
+</ul></div>
+</div>
+<div class="sect2">
+<h3 id="_the_dive_profile_context_menu">5.5. The Dive Profile context menu</h3>
+<div class="paragraph"><p>The context menu for the Dive Profile is accessed by right-clicking while
+the mouse cursor is over the Dive Profile panel. The menu allows the
+creation of Bookmarks or Gas Change Event markers or manual CCR set-point
+changes other than the ones that might have been imported from a Dive
+Computer. Markers are placed against the depth profile line and with the
+time of the event set by where the mouse cursor was when the right mouse
+button was initially clicked to bring up the menu. Gas Change events involve
+a selection of which gas is being switched to, the list of choices being
+based on the available gases defined in the Equipment Tab. Set-point change
+events open a dialog allowing to choose the next set-point value. As in the
+planner, a set-point value of zero indicates the diver is breathing from an
+open circuit system while any non-zero value indicates the use of a closed
+circuit rebreather (CCR).  By right-clicking while over an existing marker a
+menu appears, adding options to allow deletion of the marker or to allow all
+markers of that type to be hidden. Hidden events can be restored to view by
+selecting Unhide all events from the context menu.</p></div>
+</div>
+<div class="sect2">
+<h3 id="_the_strong_information_box_strong">5.6. The <strong>Information Box</strong></h3>
+<div class="paragraph"><p>The Information box displays a large range of information pertaining to the
+dive profile. Normally the Information Box is located to the top left of the
+<strong>Dive Profile</strong> panel. If the mouse points outside of the <strong>Dive Profile</strong>
+panel, then only the top line of the Information Box is visible (see
+left-hand part of figure (<strong>A</strong>) below). The Information Box can be moved
+around in the <strong>Dive Profile</strong> panel by click-dragging it with the mouse so
+that it is not obstructing important detail. The position of the Information
+Box is saved and used again during subsequent dive analyses.</p></div>
+<div class="imageblock" style="text-align:center;">
+<div class="content">
+<img src="images/InfoBox2.jpg" alt="Figure: Information Box" />
+</div>
+</div>
+<div class="paragraph"><p>The moment the mouse points inside the <strong>Dive Profile</strong> panel, the information
+box expands and shows many data items. In this situation, the data reflect
+the time point along the dive profile indicated by the mouse cursor (see
+right-hand part of figure (<strong>B</strong>) above where the Information Box reflects the
+situation at the position of the cursor [arrow] in that image). Therefore,
+moving the cursor in the horizontal direction allows the Information Box to
+show information for any point along the dive profile.  In this mode, the
+Information Box gives extensive statistics about depth, gas and ceiling
+characteristics of the particular dive. These include: Time period into the
+dive (indicated by a @), depth, cylinder pressure (P), temperature,
+ascent/descent rate, surface air consumption (SAC), oxygen partial pressure,
+maximum operating depth, equivalent air depth (EAD), equivalent narcotic
+depth (END), equivalent air density depth (EADD), decompression requirements
+at that instant in time (Deco), time to surface (TTS), the calculated
+ceiling, as well as the calculated ceiling for several Bühlmann tissue
+compartments.</p></div>
+<div class="paragraph"><p>The user has control over the display of several statistics, represented as
+four buttons on the left of the profile panel. These are:</p></div>
+<div class="admonitionblock">
+<table><tr>
+<td class="icon">
+<img src="images/icons/MOD.jpg" alt="Note" />
+</td>
+<td class="content">Clicking this button causes the Information Box to display the <strong>Maximum
+Operating Depth (MOD)</strong> of the dive, given the gas mixture used. MOD is
+dependent on the oxygen concentration in the breathing gas.  For air (21%
+oxygen) it is around 57 m. Below the MOD there is a markedly increased risk
+of exposure to the dangers associated with oxygen toxicity.</td>
+</tr></table>
+</div>
+<div class="admonitionblock">
+<table><tr>
+<td class="icon">
+<img src="images/icons/NDL.jpg" alt="Note" />
+</td>
+<td class="content">Clicking this button causes the Information Box to display the <strong>No-deco
+Limit (NDL)</strong> or the <strong>Total Time to Surface (TTS)</strong>. NDL is the time duration
+that a diver can continue with a dive, given the present depth, that does
+not require decompression (that is, before an ascent ceiling appears). Once
+one has exceeded the NDL and decompression is required (that is, there is an
+ascent ceiling above the diver, then TTS gives the number of minutes
+required before the diver can surface. TTS includes ascent time as well as
+decompression time.</td>
+</tr></table>
+</div>
+<div class="admonitionblock">
+<table><tr>
+<td class="icon">
+<img src="images/icons/SAC.jpg" alt="Note" />
+</td>
+<td class="content">Clicking this button causes the Information Box to display the <strong>Surface Air
+Consumption (SAC)</strong>.  SAC is an indication of the surface-normalised
+respiration rate of a diver. The value of SAC is less than the real
+respiration rate because a diver at 10m uses breathing gas at a rate roughly
+double that of the equivalent rate at the surface. SAC gives an indication
+of breathing gas consumption rate independent of the depth of the dive so
+that the respiratory rates of different dives can be compared. The units for
+SAC is litres/min or cub ft/min.</td>
+</tr></table>
+</div>
+<div class="admonitionblock">
+<table><tr>
+<td class="icon">
+<img src="images/icons/EAD.jpg" alt="Note" />
+</td>
+<td class="content">Clicking this button displays the <strong>Equivalent Air Depth (EAD)</strong> for nitrox
+dives as well as the <strong>Equivalent Narcotic Depth (END)</strong> for trimix
+dives. These are numbers of importance to divers who use breathing gases
+other than air. Their values are dependent on the composition of the
+breathing gas.  The EAD is the depth of a hypothetical air dive that has the
+same partial pressure of nitrogen as the current depth of the nitrox dive at
+hand. A nitrox dive leads to the same decompression obligation as an air
+dive to the depth equalling the EAD. The END is the depth of a hypothetical
+air dive that has the same sum of partial pressures of the narcotic gases
+nitrogen and oxygen as the current trimix dive. A trimix diver can expect
+the same narcotic effect as a diver breathing air diving at a depth
+equalling the END.</td>
+</tr></table>
+</div>
+<div class="paragraph"><p>Figure (<strong>B</strong>) above shows an information box with a nearly complete set of
+data.</p></div>
+<div class="sect3">
+<h4 id="S_gas_pressure_graph">5.6.1. The Gas Pressure Bar Graph</h4>
+<div class="paragraph"><p>On the left of the <strong>Information Box</strong> is a vertical bar graph indicating the
+pressures of the nitrogen (and other inert gases, e.g. helium, if
+applicable) that the diver was inhaling <em>at a particular instant during the
+dive</em>, indicated by the position of the cursor on the <strong>Dive Profile</strong>. The
+drawing on the left below indicates the meaning of the different parts of
+the Gas Pressure Bar Graph.</p></div>
+<div class="imageblock" style="text-align:center;">
+<div class="content">
+<img src="images/GasPressureBarGraph.jpg" alt="FIGURE:Gas Pressure bar Graph" />
+</div>
+</div>
+<div class="paragraph"><p>The light green area indicates the total gas, with the top margin of the
+light green area indicating the total gas pressure inhaled by the diver and
+measured from the bottom of the graph to the top of the light green
+area. This pressure has a <em>relative</em> value in the graph and does not
+indicate absolute pressure.</p></div>
+<div class="paragraph"><p>The horizontal black line underneath the light green margin indicates the
+equilibrium pressure of the inert gases inhaled by the diver, usually
+nitrogen. In the case of trimix, it is the pressures of nitrogen and helium
+combined. In this example, the user is diving with EAN32, so the inert gas
+pressure is 68% of the distance from the bottom of the graph to the total
+gas pressure value.</p></div>
+<div class="paragraph"><p>The dark green area at the bottom of the graph represents the pressures of
+inert gas in each of the 16 tissue compartments, following the Bühlmann
+algorithm, the fast tissues being on the left hand side.</p></div>
+<div class="paragraph"><p>The top black horizontal line indicates the gradient factor that applies to
+the depth of the diver at the particular point on the <strong>Dive Profile</strong>. The
+appropriate gradient factor is an interpolation between the FGLow and GFHigh
+values specified in the Graph tab of the <strong>Preferences Panel</strong> of
+<strong>Subsurface</strong>.</p></div>
+<div class="paragraph"><p>The bottom margin of the red area in the graph indicates the Bühlman-derived
+M-value, that is the pressure value of inert gases at which bubble formation
+is expected to be severe, resulting in decompression sickness.</p></div>
+<div class="paragraph"><p>These five values are indicated on the left in the graph above. The way the
+Gas Pressure Bar Graph changes during a dive is indicated on the right hand
+side of the above figure for a diver using EAN32.</p></div>
+<div class="paragraph"><p>Graph <strong>A</strong> indicates the situation at the start of a dive with diver at the
+surface. The pressures in all the tissue compartments are still at the
+equilibrium pressure because no diving has taken place.</p></div>
+<div class="paragraph"><p>Graph <strong>B</strong> indicates the situation after a descent to 30 meters. Few of the
+tissue compartments have had time to respond to the descent, their gas
+pressures being far below the equilibrium gas pressure.</p></div>
+<div class="paragraph"><p>Graph <strong>C</strong> represents the pressures after 30 minutes at 30 m. The fast
+compartments have attained equilibrium (i.e. they have reached the hight of
+the black line indicating the equilibrium pressure). The slower compartments
+(towards the right) have not reached equilibrium and are in the process of
+slowly increasing in pressure.</p></div>
+<div class="paragraph"><p>Graph <strong>D</strong> shows the pressures after ascent to a depth of 4.5 meters. Since,
+during ascent, the total inhaled gas pressure has decreased strongly from 4
+bar to 1.45 bar, the pressures in the different tissue compartments now
+exceed that of the total gas pressure and approaches the gradient factor
+value (i.e.  the top black horizontal line). Further ascent will result in
+exceeding the gradient factor value (GFHigh), endangering the diver.</p></div>
+<div class="paragraph"><p>Graph <strong>E</strong> indicates the situation after remaining at 4.5 meters for 10
+minutes. The fast compartments have decreased in pressure. As expected, the
+pressures in the slow compartments have not changed much.  The pressures in
+the fast compartments do not approach the GFHigh value any more and the
+diver is safer than in the situation indicated in graph <strong>D</strong>.</p></div>
+</div>
+</div>
+</div>
+</div>
+<div class="sect1">
+<h2 id="_organising_the_logbook_manipulating_groups_of_dives">6. Organising the logbook (Manipulating groups of dives)</h2>
+<div class="sectionbody">
+<div class="sect2">
+<h3 id="_the_dive_list_context_menu">6.1. The Dive List context menu</h3>
+<div class="paragraph"><p>Many actions within <em>Subsurface</em> are dependent on a context menu used mostly
+to manipulate groups of dives. The context menu is found by selecting a dive
+or a group of dives and then right-clicking.</p></div>
+<div class="imageblock" style="text-align:center;">
+<div class="content">
+<img src="images/ContextMenu.jpg" alt="Figure: Context Menu" />
+</div>
+</div>
+<div class="paragraph"><p>The context menu is used in many manipulations described below.</p></div>
+<div class="sect3">
+<h4 id="_customising_the_information_showed_in_the_strong_dive_list_strong_panel">6.1.1. Customising the information showed in the <strong>Dive List</strong> panel</h4>
+<div class="imageblock" style="text-align:center;">
+<div class="content">
+<img src="images/DiveListOptions.jpg" alt="Example: Dive list info options" />
+</div>
+</div>
+<div class="paragraph"><p>The default information in the <strong>Dive List</strong> includes, for each dive,
+Dive_number, Date, Rating, Dive_depth, Dive_duration and Dive_location. This
+information can be controlled and changed by right-clicking on the header
+bar of the <strong>Dive List</strong>. For instance, a right-click on the <em>Date</em> header
+brings up a list of items that can be shown in the dive list (see
+above). Select an item to be shown in the <strong>Dive List</strong> or to be deleted from
+the dive list, and the list is immediately updated accordingly. Preferences
+for information shown in the <strong>Dive List</strong> is saved and used when <em>Subsurface</em>
+is re-opened.</p></div>
+</div>
+<div class="sect3">
+<h4 id="_selecting_dives_from_a_particular_dive_site">6.1.2. Selecting dives from a particular dive site</h4>
+<div class="paragraph"><p>Many divers have long dive lists and it may be difficult to locate all the
+dives at a particular site.  By pressing <em>Ctl-F</em> on the keyboard, a text box
+is opened at the top left hand of the <strong>Dive List</strong>.  Type the name of a dive
+site in this text box and the <strong>Dive List</strong> is immediately filtered to show
+only the dives for that site.</p></div>
+</div>
+</div>
+<div class="sect2">
+<h3 id="S_Renumber">6.2. Renumbering the dives</h3>
+<div class="paragraph"><p>Dives are normally numbered incrementally from non-recent dives (low
+sequence numbers) to recent dives (having the highest sequence numbers). The
+numbering of the dives is not always consistent. For instance, when
+non-recent dives are added to the dive list the numbering does not
+automatically follow on because of the dives that are more recent in
+date/time than the newly-added dive with an older date/time. Therefore, one
+may sometimes need to renumber the dives.  This is performed by selecting
+(from the Main Menu) <em>Log &#8594; Renumber</em>. Users are given a choice with
+respect to the lowest sequence number to be used.  Completing this operation
+results in new sequence numbers (based on date/time)  for the dives in the
+<strong>Dive List</strong> panel.</p></div>
+</div>
+<div class="sect2">
+<h3 id="S_Group">6.3. Grouping dives into trips and manipulating trips</h3>
+<div class="paragraph"><p>For regular divers, the dive list can rapidly become very long. <em>Subsurface</em>
+can group dives into <em>trips</em>. It performs this by grouping dives that have
+date/times that are not separated in time by more than two days, thus
+creating a single heading for each diving trip represented in the dive
+log. Below is an ungrouped dive list (<strong>A</strong>, on the left) as well as the
+corresponding grouped dive list comprising five dive trips (<strong>B</strong>, on the
+right):</p></div>
+<div class="imageblock" style="text-align:center;">
+<div class="content">
+<img src="images/Group2.jpg" alt="Figure: Grouping dives" />
+</div>
+</div>
+<div class="paragraph"><p>Grouping into trips allows a rapid way of accessing individual dives without
+having to scan a long lists of dives. In order to group the dives in a dive
+list, (from the Main Menu) users must select <em>Log &#8594; Autogroup</em>. The <strong>Dive
+List</strong> panel now shows only the titles for the trips.</p></div>
+<div class="sect3">
+<h4 id="_editing_the_title_and_associated_information_for_a_particular_trip">6.3.1. Editing the title and associated information for a particular trip</h4>
+<div class="paragraph"><p>Normally, in the dive list, minimal information is included in the trip
+title.  More information about a trip can be added by selecting its trip
+title from the <strong>Dive List</strong>. This shows a <strong>Trip Notes</strong> tab in the <strong>Dive
+Notes</strong> panel. Here users can add or edit information about the date/time,
+the trip location and any other general comments about the trip as a whole
+(e.g. the dive company that was dived with, the general weather and surface
+conditions during the trip, etc.).  After entering this information, users
+should select <strong>Save</strong> from the buttons at the top right of the <strong>Trip Notes</strong>
+tab. The trip title in the <strong>Dive List</strong> panel should now reflect some of the
+edited information.</p></div>
+</div>
+<div class="sect3">
+<h4 id="_viewing_the_dives_during_a_particular_trip">6.3.2. Viewing the dives during a particular trip</h4>
+<div class="paragraph"><p>Once the dives have been grouped into trips, users can expand one or more
+trips by clicking the arrow-head on the left of each trip title. This
+expands the selected trip, revealing the individual dives performed during
+the trip.</p></div>
+</div>
+<div class="sect3">
+<h4 id="_collapsing_or_expanding_dive_information_for_different_trips">6.3.3. Collapsing or expanding dive information for different trips</h4>
+<div class="paragraph"><p>If a user right-clicks after selecting a particular trip in the dive list,
+the resulting context menu allows several possibilities to expand or
+collapse dives within trips. This includes expanding all trips, collapsing
+all trips and collapsing all trips except the selected one.</p></div>
+</div>
+<div class="sect3">
+<h4 id="_merging_dives_from_more_than_one_trip_into_a_single_trip">6.3.4. Merging dives from more than one trip into a single trip</h4>
+<div class="paragraph"><p>By right-clicking on a selected trip title in the <strong>Dive List</strong> panel, a
+context menu shows up that allows the merging of trips by either merging of
+the selected trip with the trip below or with the trip above.</p></div>
+</div>
+<div class="sect3">
+<h4 id="_splitting_a_single_trip_into_more_than_one_trip">6.3.5. Splitting a single trip into more than one trip</h4>
+<div class="paragraph"><p>If a trip includes five dives, the user can split this trip into two trips
+(trip 1: top 3 dives; trip 2: bottom 2 dives) by selecting and
+right-clicking the top three dives. The resulting context menu allows the
+user to create a new trip by choosing the option <strong>Create new trip
+above</strong>. The top three dives are then grouped into a separate trip. The
+figures below shows the selection and context menu on the left (A) and the
+completed action on the right (B):</p></div>
+<div class="imageblock" style="text-align:center;">
+<div class="content">
+<img src="images/SplitDive3a.jpg" alt="FIGURE: Split a trip into 2 trips" />
+</div>
+</div>
+</div>
+</div>
+<div class="sect2">
+<h3 id="_manipulating_single_dives">6.4. Manipulating single dives</h3>
+<div class="sect3">
+<h4 id="_delete_a_dive_from_the_dive_log">6.4.1. Delete a dive from the dive log</h4>
+<div class="paragraph"><p>Dives can be permanently deleted from the dive log by selecting and
+right-clicking them to bring up the context menu, and then selecting <strong>Delete
+dive(s)</strong>. Typically this would apply to a case where a user wishes to delete
+workshop calibration dives of the dive computer or dives of extremely short
+duration.</p></div>
+</div>
+<div class="sect3">
+<h4 id="_unlink_a_dive_from_a_trip">6.4.2. Unlink a dive from a trip</h4>
+<div class="paragraph"><p>Users can unlink dives from the trip to which they belong. In order to do
+this, select and right-click the relevant dives to bring up the context
+menu. Then select the option <strong>Remove dive(s)  from trip</strong>. The dive(s) now
+appear immediately above the trip to which they belonged.</p></div>
+</div>
+<div class="sect3">
+<h4 id="_add_a_dive_to_the_trip_immediately_above">6.4.3. Add a dive to the trip immediately above</h4>
+<div class="paragraph"><p>Selected dives can be moved from the trip to which they belong and placed
+within the trip immediately above the currently active trip. To do this,
+select and right-click the dive(s) to bring up the context menu, and then
+select <strong>Add dive(s) to trip immediately above</strong>.</p></div>
+</div>
+<div class="sect3">
+<h4 id="_shift_the_start_time_of_dive_s">6.4.4. Shift the start time of dive(s)</h4>
+<div class="paragraph"><p>Sometimes it is necessary to adjust the start time of a dive. This may apply
+to situations where dives are performed in different time zones or when the
+dive computer has an erroneous time. In order to do this, user must select
+and right-click the dive(s) to be adjusted. This action brings up the
+context menu on which the <strong>Shift times</strong> option should be selected. User must
+then specify the time (in hours and minutes) by which the dives should be
+adjusted and click on the option indicating whether the time adjustment
+should be forwards or backwards.</p></div>
+</div>
+<div class="sect3">
+<h4 id="_merge_dives_into_a_single_dive">6.4.5. Merge dives into a single dive</h4>
+<div class="paragraph"><p>Sometimes a dive is briefly interrupted, e.g. if a diver returns to the
+surface for a few minutes, resulting in two or more dives being recorded by
+the dive computer and appearing as different dives in the <strong>Dive List</strong>
+panel. Users can merge these dives onto a single dive by selecting the
+appropriate dives, right-clicking them to bring up the context menu and then
+selecting <strong>Merge selected dives</strong>. It may be necessary to edit the dive
+information in the <strong>Dive Notes</strong> panel to reflect events or conditions that
+apply to the merged dive. The figure below shows the depth profile of two
+such dives that were merged:</p></div>
+<div class="imageblock" style="text-align:center;">
+<div class="content">
+<img src="images/MergedDive.png" alt="Example: Merged dive" />
+</div>
+</div>
+</div>
+</div>
+<div class="sect2">
+<h3 id="S_Filter">6.5. Filtering the dive list</h3>
+<div class="paragraph"><p>The dives in the <strong>Dive List</strong> panel can be filtered, that is, one can select
+only some of the dives based on their attributes, e.g. dive tags, dive site,
+dive master, buddy or protective clothing. For instance, filtering allows
+one to list the deep dives at a particular dive site, or otherwise the cave
+dives with a particular buddy.</p></div>
+<div class="paragraph"><p>To open the filter, select <em>Log &#8594; Filter divelist</em> from the main menu. This
+opens the <em>Filter Panel</em> at the top of the <em>Subsurface</em> window. Three icons
+are located at the top right hand of the filter panel. The <em>Filter Panel</em>
+can be reset (i.e. all current filters cleared) by selecting the <strong>+</strong>. The
+<em>Filter Panel</em> may also be minimised by selecting the middle icon. When
+minimised, only these three icons are shown.  The panel can be maximised by
+clicking the icon that minimised the panel. The filter may also be reset and
+closed by selecting the button with the flag.  An example of the <em>Filter
+Panel</em> is shown in the figure below.</p></div>
+<div class="imageblock" style="text-align:center;">
+<div class="content">
+<img src="images/Filterpanel.jpg" alt="Figure: Filter panel" />
+</div>
+</div>
+<div class="paragraph"><p>Four filter criteria may be used to filter the dive list: dive tags, person
+(buddy / dive master), dive site and dive suit, each of which is represented
+by a check list with check boxes. Above each check list is a second-level
+filter tool, allowing the listing of only some of the attributes within that
+check list. For instance, typing "<em>ca</em>" in the filter textbox above the tags
+check list results in the tags check list being reduced to "<em>cave</em>" and
+"<em>cavern</em>". Filtering of the check list enables the rapid finding of search
+terms for filtering the dive list.</p></div>
+<div class="paragraph"><p>To activate filtering of the dive list, the check box of at least one item
+in one of the four check lists needs to be checked. The dive list is then
+shortened to include only the dives that pertain to the selection criteria
+specified in the check lists.  The four check lists work as a filter with
+<em>AND</em> operators, Subsurface filters therefore for <em>cave</em> as a tag AND <em>Joe
+Smith</em> as a buddy; but the filters within a category are inclusive -
+filtering for <em>cave</em> and <em>boat</em> shows those dives that have either one or
+both of these tags.</p></div>
+</div>
+</div>
+</div>
+<div class="sect1">
+<h2 id="S_ExportLog">7. Exporting the dive log or parts of the dive log</h2>
+<div class="sectionbody">
+<div class="paragraph"><p>The export function can be reached by selecting <em>File &#8594; Export</em>, which
+brings up the Export dialog. This dialog always gives two options: save ALL
+dives, or save only the dives selected in <strong>Dive List</strong> panel of
+<em>Subsurface</em>. Click the appropriate radio button (see images below).</p></div>
+<div class="imageblock" style="text-align:center;">
+<div class="content">
+<img src="images/Export.jpg" alt="Figure: Export dialog" />
+</div>
+</div>
+<div class="paragraph"><p>A dive log or part of it can be saved in three formats:</p></div>
+<div class="ulist"><ul>
+<li>
+<p>
+<em>Subsurface XML</em> format. This is the native format used by <em>Subsurface</em>.
+</p>
+</li>
+</ul></div>
+<div class="paragraph"><p>Universal Dive Data Format (<em>UDDF</em>). Refer to <em>http://uddf.org</em> for more
+information.  UDDF is a generic format that enables communication among many
+dive computers and computer programs.</p></div>
+<div class="paragraph"><p><em>Divelogs.de</em>, an Internet-based dive log repository. In order to upload to
+<em>Divelogs.de</em>, one needs a user-ID as well as a password for
+<em>Divelogs.de</em>. Log into <em>http://en.divelogs.de</em> and subscribe to this
+service in order to upload dive log data from <em>Subsurface</em>.</p></div>
+<div class="paragraph"><p><em>CSV</em> format, that includes the most critical information of the dive
+profile. Included information of a dive is: dive number, date, time,
+duration, depth, temperature and pressure.</p></div>
+<div class="paragraph"><p><em>Worldmap</em> format, an HTML file with a world map upon which each dive and
+some information about it are indicated. This map is not editable.</p></div>
+<div class="paragraph"><p><em>HTML</em> format, in which the dive(s) are stored in HTML files, readable with
+an Internet browser. Most modern web browsers are supported, but JavaScript
+must be enabled. This generated HTML file is not intended to be edited by
+the users.  The HTML dive log contains most of the information and also
+contains a search option to search the dive log. HTML export is specified on
+the second tab of the Export dialog (image <strong>B</strong> above).</p></div>
+<div class="ulist"><ul>
+<li>
+<p>
+<em>General Settings</em>, under the HTML tab, provides the following options:
+</p>
+<div class="ulist"><ul>
+<li>
+<p>
+Subsurface Numbers: if this option is checked, the dive(s) are exported with the
+numbers associated with them in Subsurface, Otherwise the dive(s) will be numbered
+starting from 1.
+</p>
+</li>
+<li>
+<p>
+Export Yearly Statistics: if this option is checked, a yearly statistics table will
+be attached with the HTML exports.
+</p>
+</li>
+<li>
+<p>
+Export List only: a list of dives will only be exported and the detailed dive
+information will not be available.
+</p>
+</li>
+</ul></div>
+</li>
+</ul></div>
+<div class="paragraph"><p>Under <em>Style Options</em> some style-related options are available like font
+size and theme.</p></div>
+<div class="paragraph"><p>Export to other formats can be achieved through third party facilities, for
+instance <em>www.divelogs.de</em>.</p></div>
+</div>
+</div>
+<div class="sect1">
+<h2 id="S_Cloud_access">8. Keeping a <em>Subsurface</em> dive log in the Cloud</h2>
+<div class="sectionbody">
+<div class="paragraph"><p>For each diver, dive log information is highly important. Not only is it a
+record of diving activities for one&#8217;s own pleasure, but it is important
+information required for admission to further training courses or
+(sometimes) even diving sites. The security of the dive log is therefore
+critical. In order to have a dive log that is resistant to failure of a home
+computer hard drive, loss or theft of equipment, the Cloud is an obvious
+solution. This also has the added benefit that one can access one&#8217;s dive log
+from anywhere in the world without having to carry it with oneself. For this
+reason, facilities such as <em>divelogs.de</em> and <em>Diving Log</em> offer facilities
+to store dive log information on the Internet. Although <em>Subsurface</em> does
+not offer integrated Cloud storage of dive logs, it is simple to achieve
+this using several of the existing facilities on the Internet.</p></div>
+<div class="paragraph"><p>For instance <a href="http://www.dropbox.com/"><em>Dropbox</em></a> offers a free application
+that allows files on the Dropbox servers to be seen as a local folder on
+one&#8217;s desktop computer.</p></div>
+<div class="imageblock" style="text-align:center;">
+<div class="content">
+<img src="images/Cloud.jpg" alt="FIGURE: Dropbox folder" />
+</div>
+</div>
+<div class="paragraph"><p>The <em>Dropbox</em> program creates a copy of the <em>Dropbox</em> Internet Cloud content
+on one&#8217;s desktop computer. When the computer is connected to the Internet,
+the Internet content is automatically updated. Therefore both the <em>Open</em> and
+<em>Save</em> of dive logs are done using the local copy of the dive log in the
+local <em>Dropbox</em> folder, so there&#8217;s no need for a direct internet
+connection. If the local copy is modified, e.g. by adding a dive, the remote
+copy in the <em>Dropbox</em> server in the Cloud will be automatically updated
+whenever Internet access is available.</p></div>
+<div class="paragraph"><p>In this way a dive log in one&#8217;s <em>Dropbox</em> folder can be accessed seamlessly
+from the Internet and can be accessed from any place with Internet
+access. Currently there are no costs involved for this service. Dropbox
+(Windows, Mac and Linux) can be installed by accessing the
+<a href="http://www.dropbox.com/install"><em>Install Page on the Dropbox website</em></a>
+Alternatively one can use <em>Dropbox</em> as a mechanism to backup one&#8217;s dive
+log. To Store a dive log in the Cloud, select <em>File&#8594;Save as</em> from the
+<em>Subsurface</em> main menu, navigate to the <em>Dropbox</em> folder and select the
+<em>Save</em> button. To access the dive log in the Cloud, select <em>File&#8594;Open
+Logbook</em> from the <em>Subsurface</em> main menu and navigate to the dive log file
+in the <em>Dropbox</em> folder and select the <em>Open</em> button.</p></div>
+<div class="paragraph"><p>Several paid services exist on the Internet (e.g. Google, Amazon) where the
+same process could be used for the Cloud-based storage of dive logs.</p></div>
+</div>
+</div>
+<div class="sect1">
+<h2 id="S_PrintDivelog">9. Printing a dive log</h2>
+<div class="sectionbody">
+<div class="paragraph"><p><em>Subsurface</em> provides a simple interface to print a whole dive log or only a
+few selected dives, including dive profiles and other contextual
+information.</p></div>
+<div class="paragraph"><p>Before printing, two decisions are required:</p></div>
+<div class="paragraph"><p>Should the whole dive log be printed or only part of it? If only part of the
+dive log is required, then the user must select the required dives from the
+<strong>Dive List</strong> panel.
+What gas partial pressure information is required on the dive profile? Users
+should select the appropriate toggle-buttons on the button bar to the left
+of the Dive Profile panel.</p></div>
+<div class="paragraph"><p>Now the print options should be selected to match the user&#8217;s needs. To do
+this, user should select <em>File&#8594;Print</em> from the Main menu. The following
+dialogue appears (see the image on the left [A], below).</p></div>
+<div class="imageblock" style="text-align:center;">
+<div class="content">
+<img src="images/PrintDiveLog.jpg" alt="FIGURE: Print dialogue" />
+</div>
+</div>
+<div class="paragraph"><p>Under <em>Print type</em> users need to select one of three options:</p></div>
+<div class="ulist"><ul>
+<li>
+<p>
+Print the complete Dive List: to do this, <em>Table Print</em> should be selected.
+Print the selected dives (dive profiles and all other information) at 6
+dives per printed page: to do this, users should select <em>6 dives per page</em>.
+Print the selected dives (dive profiles and all other information) at 2
+dives per printed page: to do this, users should select <em>2 dives per page</em>.
+Print the selected dives (dive profiles and all other information) at 1 dive
+per printed page: to do this, users should select <em>1 dive per page</em>.
+</p>
+</li>
+</ul></div>
+<div class="paragraph"><p>Under <em>Print options</em> users need to select:</p></div>
+<div class="paragraph"><p>Printing only the dives that have been selected from the dive list prior to
+activating the print dialogue, achieved by checking the box <em>Print only
+selected dives</em>.
+- Printing in colour, achieved by checking the box with <em>Print in colour</em>.</p></div>
+<div class="paragraph"><p>The <em>Ordering</em> affects the layout of the page (or part of it) for each
+dive.  The dive profile could be printed at the top of each dive, with the
+textual information underneath, or it could be printed with the textual
+information at the top with the dive profile underneath. Users should select
+the appropriate option in the print dialogue. See the image below which has
+a layout with text below the dive profile.</p></div>
+<div class="paragraph"><p>Users can <em>Preview</em> the printed page by selecting the <em>Preview</em> button on
+the dialogue. After preview, changes to the options in the print dialogue
+can be made, resulting in a layout that fits personal taste.</p></div>
+<div class="paragraph"><p>Next, select the <em>Print</em> button in the dialogue. This activates the regular
+print dialogue used by the user operating system (image [<strong>B</strong>] in the middle,
+above), allowing them to choose a printer and to set its properties (image
+[<strong>C</strong>] on the right, above).  It is important to set the print resolution of
+the printer to an appropriate value by changing the printer
+properties. Finally, one can print the dives. Below is a (rather small)
+example of the output for one particular page.</p></div>
+<div class="imageblock" style="text-align:center;">
+<div class="content">
+<img src="images/Printpreview.jpg" alt="FIGURE: Print preview page" />
+</div>
+</div>
+</div>
+</div>
+<div class="sect1">
+<h2 id="S_Preferences">10. Setting user <em>Preferences</em> for <em>Subsurface</em></h2>
+<div class="sectionbody">
+<div class="paragraph"><p>There are several settings within <em>Subsurface</em> that the user can
+specify. These are found when selecting <em>File&#8594;Preferences</em>. The settings
+are performed in five groups: <strong>Defaults</strong>, <strong>Units</strong>, <strong>Graph</strong>, <strong>Language</strong> and
+<strong>Network</strong>. All five sections operate on the same principles: the user must
+specify the settings that are to be changed, then these changes are saved
+using the <strong>Apply</strong> button. After applying all the new settings users can then
+leave the settings panel by selecting <strong>OK</strong>.</p></div>
+<div class="sect2">
+<h3 id="_defaults">10.1. Defaults</h3>
+<div class="paragraph"><p>There are several settings in the <strong>Defaults</strong> panel:</p></div>
+<div class="imageblock" style="text-align:center;">
+<div class="content">
+<img src="images/Pref1.jpg" alt="FIGURE: Preferences defaults page" />
+</div>
+</div>
+<div class="ulist"><ul>
+<li>
+<p>
+<strong>Lists and tables</strong>: Here one can specify the font type and font size of the
+<strong>Dive Table</strong> panel. By decreasing the font size of the <strong>Dive Table</strong>, users can see more dives on a screen.
+</p>
+</li>
+<li>
+<p>
+<strong>Dives</strong>: For the <em>Default Dive File</em> one need to specify the directory and
+file name of one&#8217;s
+electronic dive log book. This is a file with filename extension .xml. When
+launched, <em>Subsurface</em> will automatically load the specified dive log book.
+</p>
+</li>
+<li>
+<p>
+<strong>Display invalid</strong>:  Dives can be marked as invalid (when a user wishes to hide
+dives that he/she don&#8217;t consider valid dives, e.g. pool dives, but still want to
+keep them in the dive log). This controls whether those dives are displayed in
+the dive list.
+</p>
+</li>
+<li>
+<p>
+<strong>Default cylinder</strong>: Here users can specify the default cylinder listed in
+the <strong>Equipment</strong> tab of the <strong>Dive Notes</strong> panel.
+</p>
+</li>
+<li>
+<p>
+<strong>Animations</strong>: Some actions in showing the dive profile are performed using
+animations. For instance, the axis values for depth and time change from dive to
+dive. When viewing a different dive, these changes in axis characteristics do not
+happen instantaneously, but are animated. The <em>Speed</em> of animations can be controlled
+by setting this slider
+with faster animation speed to the left, with a 0 value representing no animation
+at all.
+</p>
+</li>
+<li>
+<p>
+<strong>Subsurface web service</strong>: When one subscribes to the <a href="#S_Companion">Subsurface web service</a>, a very
+long and hard-to-remember userID is issued. This is the place to save that userID. By
+checking the option <em>Save User ID locally?</em>, one ensures that a local copy of that userID
+is saved.
+</p>
+</li>
+<li>
+<p>
+<strong>Clear all settings</strong>: As indicated in the button below this heading, all settings are
+cleared and set to default values.
+</p>
+</li>
+</ul></div>
+</div>
+<div class="sect2">
+<h3 id="_units">10.2. Units</h3>
+<div class="imageblock" style="text-align:center;">
+<div class="content">
+<img src="images/Pref2.jpg" alt="FIGURE: Preferences Units page" />
+</div>
+</div>
+<div class="paragraph"><p>Here user can choose between metric and imperial units of depth, pressure,
+volume, temperature and mass. By selecting the Metric or Imperial radio
+button at the top, users can specify that all units are in the chosen
+measurement system.  Alternatively, if one selects the <strong>Personalise</strong> radio
+button, units can be selected independently, with some units in the metric
+system and others in imperial.</p></div>
+</div>
+<div class="sect2">
+<h3 id="_graph">10.3. Graph</h3>
+<div class="imageblock" style="text-align:center;">
+<div class="content">
+<img src="images/Pref3.jpg" alt="FIGURE: Preferences Graph page" />
+</div>
+</div>
+<div class="paragraph" id="S_GradientFactors"><p>This panel allows two type of selections:</p></div>
+<div class="paragraph"><p><strong>Show</strong>: Here users can specify the amount of information shown as part of
+the dive profile:
+<strong>* Thresholds: <em>Subsurface</em> can display the nitrogen, oxygen and the helium partial pressures during
+the dive. These are enabled using the toolbar on the left hand side of the *Dive Profile</strong>
+panel. For each of these graphs users can specify a threshold value on the right-hand side of the
+Preferences panel. If any of the graphs go above this threshold level, the graph is
+highlighted in red, indicating that the threshold has been exceeded.</p></div>
+<div class="ulist"><ul>
+<li>
+<p>
+<em>Draw dive computer reported ceiling red</em>: This checkbox allows exactly what it says.
+Not all dive computers report ceiling values. If the dive computer does report it, it may differ
+from the ceilings calculated by <em>Subsurface</em>. This is because of the different algorithms and gradient factors available for calculating ceilings, as well as the dynamic way that a
+dive computer can calculate ceilings during a dive.
+</p>
+</li>
+<li>
+<p>
+<em>Show unused cylinders in Equipment Tab</em>: This checkbox allows display of information about unused cylinders when viewing the <strong>Equipment Tab</strong>. Conversely, if this box is not checked, and any cylinders entered using the <strong>Equipment Tab</strong> are not used (e.g. there was no gas switch to such a cylinder), then these cylinders are omitted from that list.
+</p>
+</li>
+<li>
+<p>
+<em>Show average depth</em>: Activating this checkbox causes <em>Subsurface</em> to draw a red line across
+the dive profile, indicating the mean depth of the dive.
+</p>
+<div class="ulist"><ul>
+<li>
+<p>
+<strong>Misc</strong>:
+</p>
+</li>
+</ul></div>
+</li>
+<li>
+<p>
+Gradient Factors:* Here users can set the <em>gradient factors</em> used while diving. GF_Low is
+the gradient factor at depth and GF_High is used just below the surface.
+At intermediate depths gradient factors between GF_Low and GF_High are used.
+Gradient factors add conservatism to the nitrogen exposure during a dive, in a
+similar way that many dive computers have a conservatism setting. The lower
+the value of a gradient factor, the more conservative the calculations are with
+respect to nitrogen loading and the deeper the ascent ceilings are. Gradient
+factors of 20/60 are considered conservative and values of 60/90 are considered
+harsh. Checking <strong>GFLow at max depth</strong> box causes GF_Low to be used at the
+deepest depth of a dive. If this box is not checked, GF_Low is applied at
+all depths deeper than the first deco stop. For more information see:
+</p>
+</li>
+<li>
+<p>
+<a href="http://www.tek-dive.com/portal/upload/M-Values.pdf">Understanding M-values by Erik Baker, <em>Immersed</em> Vol. 3, No. 3.</a>
+</p>
+</li>
+<li>
+<p>
+<a href="http://www.rebreatherworld.com/general-and-new-to-rebreather-articles/5037-gradient-factors-for-dummies.html">Gradient factors for dummies, by Kevin Watts</a>
+</p>
+</li>
+</ul></div>
+</div>
+<div class="sect2">
+<h3 id="_language">10.4. Language</h3>
+<div class="paragraph"><p>Choose a language that <em>Subsurface</em> will use.</p></div>
+<div class="imageblock" style="text-align:center;">
+<div class="content">
+<img src="images/Pref4.jpg" alt="FIGURE: Preferences Language page" />
+</div>
+</div>
+<div class="paragraph"><p>A checkbox allows one to use the <em>System Default</em> language which in most
+cases will be the correct setting; with this <em>Subsurface</em> simply runs in the
+same language / country settings as the underlying OS. If this is for some
+reason undesirable users can uncheck this checkbox and pick a language /
+country combination from the list of included localizations. The <em>Filter</em>
+text box allows one to list similar languages. For instance there are
+several system variants of English or French. This particular preference
+requires a restart of <em>Subsurface</em> to take effect.</p></div>
+</div>
+<div class="sect2">
+<h3 id="_network">10.5. Network</h3>
+<div class="paragraph"><p>This panel facilitates communication between <em>Subsurface</em> and data sources
+on the Internet.</p></div>
+<div class="imageblock" style="text-align:center;">
+<div class="content">
+<img src="images/Pref5.jpg" alt="FIGURE: Preferences Network page" />
+</div>
+</div>
+<div class="paragraph"><p>This is important, for instance, when <em>Subsurface</em> needs to communicate with
+Internet services such as the <a href="#S_Companion"><em>Subsurface Companion app</em></a> or
+data export/import from <em>Divelogs.de</em>. These Internet requirements are
+determined by one&#8217;s type of connection to the Internet and by the Internet
+Service Provider (ISP) used.  One&#8217;s ISP should provide the appropriate
+information.  If a proxy server is used for Internet access, the appropriate
+information needs to be provided here. The type of proxy needs to be
+selected from the dropdown list.  after which the IP address of the host and
+the appropriate port number should be provided. If the proxy server uses
+authentication, the appropriate userID and password also needs to be
+provided so that <em>Subsurface</em> can automatically pass through the proxy
+server to access the Internet.</p></div>
+</div>
+</div>
+</div>
+<div class="sect1">
+<h2 id="S_DivePlanner">11. The <em>Subsurface</em> dive planner</h2>
+<div class="sectionbody">
+<div class="paragraph"><p>Dive planning is an advanced feature of <em>Subsurface</em>, accessible by
+selecting <em>Log &#8594; Plan Dive</em> from the main menu. It allows calculation of
+nitrogen load during a dive by using the Bühlmann ZH-L16 algorithm with the
+addition of gradient factors as implemented by Erik Baker.</p></div>
+<div class="sidebarblock">
+<div class="content">
+<div class="admonitionblock">
+<table><tr>
+<td class="icon">
+<img src="images/icons/warning2.png" alt="Warning" />
+</td>
+<td class="content">The <em>Subsurface</em> dive planner IS CURRENTLY EXPERIMENTAL and assumes the user
+is already familiar with the <em>Subsurface</em> user interface. It is explicitly
+used under the following conditions:</td>
+</tr></table>
+</div>
+<div class="paragraph"><p>The user is conversant with dive planning and has the necessary training to
+perform dive planning.
+- The user plans dives within his/her certification limits.
+Dive planning makes large assumptions about the characteristics of the
+<em>average person</em> and cannot compensate for individual physiology or health
+or personal history or life style characteristics.
+- The safety of a dive plan depends heavily on the way in which the planner is
+  used.
+- The user is familiar with the user interface of <em>Subsurface</em>.
+A user who is not absolutely sure about any of the above requirements should
+not use this feature.</p></div>
+</div></div>
+<div class="sect2">
+<h3 id="_the_em_subsurface_em_dive_planner_screen">11.1. The <em>Subsurface</em> dive planner screen</h3>
+<div class="paragraph"><p>Like the <em>Subsurface</em> dive log, the planner screen is divided into several
+sections (see image below). The <strong>setup</strong> parameters for a dive are entered
+into the several sections on the left hand side of the screen.  The setup is
+divided into several sections: Available Gases, Rates, Planning, Gas Options
+and Dive Notes.</p></div>
+<div class="paragraph"><p>At the top right hand is a green <strong>design panel</strong> upon which the profile of
+the dive can be manipulated directly by dragging and clicking as explained
+below. This feature makes the <em>Subsurface</em> dive planner unique in ease of
+use.</p></div>
+<div class="paragraph"><p>At the bottom right is a text panel with a heading of <em>Dive Plan
+Details</em>. This is where the details of the dive plan are provided in a way
+that can easily be copied to other software. This is also where any warning
+messages about the dive plan are printed.</p></div>
+<div class="imageblock" style="text-align:center;">
+<div class="content">
+<img src="images/PlannerWindow1.jpg" alt="FIGURE: Dive planner startup window" />
+</div>
+</div>
+</div>
+<div class="sect2">
+<h3 id="_initiating_dive_planning">11.2. Initiating dive planning</h3>
+<div class="paragraph"><p>The dive planner comprises two parts: <strong>constructing a dive plan</strong> and
+<strong>evaluating</strong> that dive plan. To perform dive planning, perform these steps:</p></div>
+<div class="paragraph"><p>Clear the existing dive log by creating a new planning log. This is achieved
+by selecting <em>File &#8594; New logbook</em> from the main menu. This way, dive plans
+are kept separate from the existing dive log of completed dives.</p></div>
+<div class="paragraph"><p>In the top left-hand area of the screen, ensure that the constant dive
+parameters are appropriate. These are: Start date and time of the dive,
+Atmospheric Pressure and Altitude above sea level of the dive site. The
+atmospheric pressure can also be entered as an altitude in metres, assuming
+an atmospheric pressure of 1.013 bar.</p></div>
+<div class="paragraph"><p>In the table labelled <em>Available Gases</em>, add the information of the
+cylinders to be used as well as the gas composition within that
+cylinder. This is done in a similar way as for <a href="#S_CylinderData">providing cylinder data for dive logs</a>. Choose the cylinder type by double clicking
+the cylinder type and using the dropdown list, then specify the work
+pressure of this cylinder. By leaving the oxygen concentration (O2%) filed
+empty, the dive gas is assumed to be air. Otherwise enter the oxygen and/or
+helium concentration in the boxes provided in this dialogue. Add additional
+cylinders by using the "+" icon to the top righthand of the dialogue.</p></div>
+<div class="paragraph"><p>The dialogue indicating <em>Dive Planner Points</em> is usually not used at this
+stage of the dive planning.</p></div>
+</div>
+<div class="sect2">
+<h3 id="_managing_nitrogen_oxygen_and_gas_consumption">11.3. Managing nitrogen, oxygen and gas consumption</h3>
+<div class="paragraph"><p>The planning is performed in three stages:</p></div>
+<div class="paragraph"><p><strong>a) Nitrogen management</strong>: This is performed by specifying the rates for descent and ascent,
+as well as the gradient factors (GFLow and GFHigh) under the headings <em>Rates</em> and <em>Planning</em>
+to the bottom left of the planning screen. Initially, the GFHigh and GFLow values in the <em>Preferences</em>
+panel of <em>Subsurface</em> is used. If these are changed within the planner (see <em>Gas Options</em> within
+the planner), the new values are
+used without changing the original specifications in the <em>Preferences</em>. Gradient Factor settings strongly affect the calculated ceilings and their depths.
+A very low GFLow value brings about decompression stops early on during the dive.
+ ** For more information about Gradient factors, see the section on <a href="#S_GradientFactors">Gradient Factor Preference settings</a>.
+For more information external to this manual see:</p></div>
+<div class="ulist"><ul>
+<li>
+<p>
+<a href="http://www.tek-dive.com/portal/upload/M-Values.pdf">Understanding M-values by Erik Baker, <em>Immersed</em> Vol. 3, No. 3.</a>
+</p>
+</li>
+<li>
+<p>
+<a href="http://www.rebreatherworld.com/general-and-new-to-rebreather-articles/5037-gradient-factors-for-dummies.html">Gradient factors for dummies, by Kevin Watts</a>
+</p>
+</li>
+<li>
+<p>
+<a href="http://www.amazon.com/Deco-Divers-Decompression-Theory-Physiology/dp/1905492073/ref=sr_1_1?s=books&amp;ie=UTF8&amp;qid=1403932320&amp;sr=1-1&amp;keywords=deco+for+divers"><em>Deco for Divers</em>, by Mark Powell (2008). Aquapress</a> Southend-on-Sea, UK. ISBN 10: 1-905492-07-3.
+An excellent non-technical review.
+</p>
+<div class="ulist"><ul>
+<li>
+<p>
+The ascent rate is critical for nitrogen off-gassing at the end of the dive and is specified
+for several depth ranges, utilising the average (or mean) depth as a yardstick. The mean depth
+of the dive plan is indicated on the dive profile in the green panel of the dive planner. Ascent rates
+at deeper levels are often in the range of 8-12 m/min, while ascent rates near the surface are
+often in the range of 4-9 m/min. The descent rate is also specified. If the option <em>Drop to first depth</em>
+is activated, then the descent phase of the planned dive will be at the maximal descent rate specified
+in the <em>Rates</em> section of the dive setup.
+</p>
+</li>
+</ul></div>
+</li>
+</ul></div>
+<div class="paragraph"><p><strong>b) Oxygen management</strong>: In the <strong>Gas Options</strong> part of the dive specification, the maximum partial
+pressure for oxygen needs to be specified for the
+bottom part of the dive (<em>bottom po2</em>) as well as for the decompression part of the dive (<em>deco po2</em>).
+The most commonly
+used values are 1.4 bar for the bottom part of the dive and 1.6 bar for any decompression
+stages. Normally, a partial pressure of 1.6 bar is not exceeded. PO2 settings and the depth at which switching to a gas takes place can also be edited in the
+<em>Available Gases</em> dialog. Normally the planner decides on switching to a new gas when, during
+ascent, the partial pressure of the new gas has decreased to 1.6 bar.</p></div>
+<div class="paragraph"><p><strong>c) Gas management</strong>: One needs keep within the limits of the amount of gas contained in the dive
+cylinder(s), allowing for an appropriate margin for safe return to the surface, possibly
+sharing with a buddy. Under the <em>Gas Options</em> heading, specify the best (but conservative) estimate
+of your surface-equivalent air consumption (SAC, also termed RMV) in
+litres/min (for the time being, only SI units are supported).  Specify the SAC during the
+bottom part of the dive (<em>bottom SAC</em>) as well as during the decompression or safety stops of the
+dive (<em>deco SAC</em>). Values of 20-30 l/min are common. For good gas management, a thumbsuck guess
+is not sufficient and one needs to
+monitor one&#8217;s gas consumption on a regular basis, dependent on different dive conditions and/or equipment.
+The planner will calculate the total volume of gas used during the dive and will issue a warning
+if one exceeds the total amount of gas available. Good practice demands that one does not dive to
+the limit of the gas supply but that an appropriate reserve is kept for unforeseen circumstances.
+For technical diving, this reserve can be up to 66% of the total available gas.</p></div>
+<div class="paragraph"><p>Now (at last) one can start the detailed time-depth planning of the
+dive. <em>Subsurface</em> offers a unique graphical interface for performing this
+part of the planning. The mechanics of doing this is similar to
+hand-entering a dive profile in the dive log part of <em>Subsurface</em>. Upon
+activating the planner, a default dive of depth 15 m for 40 min is offered
+in the green design surface to the top right hand of the screen. The white
+dots (waypoints) on the profile can be dragged with a mouse. Create more
+waypoints by double-clicking on the profile line and ensuring that the
+profile reflects the intended dive. Drag the waypoints to represent the
+depth and duration of the dive.  If any of the management limits (for
+nitrogen, oxygen or gas) is exceeded, the surface above the dive profile
+changes from BLUE to RED.</p></div>
+<div class="paragraph"><p>Each waypoint on the dive profile creates a <em>Dive Planner Point</em> in the
+table on the left of the dive planner panel. Ensure that the <em>Used Gas</em>
+value in each row of that table corresponds to one of the gas mixtures
+specified in the table with <em>Available Gases</em> immediately above the Dive
+Planner Points. Add new waypoints until the main features of the dive have
+been completed, e.g. the bottom time segment and deep stops (if these are
+implemented). Leave the remaining waypoints on the ascent to
+<em>Subsurface</em>. In most cases <em>Subsurface</em> computes additional way points in
+order to fulfil decompression requirements for that dive. A waypoint can be
+moved by selecting that waypoint and by using the arrow keys.  The waypoints
+listed in the <em>Dive Planner Points</em> dialogue can be edited by hand in order
+to obtain a precise presentation of the dive plan. In fact, one can create
+the whole dive profile by editing the <em>Dive Planner Points</em> dialog.</p></div>
+<div class="paragraph"><p>Indicate any changes in gas cylinder used by indicating gas changes as
+explained in the section <a href="#S_CreateProfile">hand-creating a dive profile</a>. These changes should reflect the cylinders and gas compositions
+defined in the table with <em>Available Gases</em>.  If two or more gases are used,
+automatic gas switches will be suggested during the ascent to the
+surface. However, these changes can be deleted by right-clicking the gas
+change and by manually creating a gas change by right-clicking on the
+appropriate waypoint.</p></div>
+<div class="paragraph"><p>A non-zero value in the "CC set point" column of the table of dive planner
+points indicates a valid setpoint for oxygen partial pressure and that the
+segment is dived using a closed circuit rebreather (CCR). If the last
+manually entered segment is a CCR segment, the decompression phase is
+computed assuming the diver uses a CCR with the specified set-point. If the
+last segment (however short) is on open circuit (OC, indicated by a zero
+set-point) the decompression is computed in OC mode. The planner only
+considers gas changes in OC mode.</p></div>
+<div class="paragraph"><p>Below is an example of a dive plan to 45m using EAN26, followed by an ascent
+using EAN50 and using the settings as described above.</p></div>
+<div class="imageblock" style="text-align:center;">
+<div class="content">
+<img src="images/DivePlanner2.jpg" alt="FIGURE: Planning a dive: setup" />
+</div>
+</div>
+<div class="paragraph"><p>Once the above has been completed, one can save it by clicking the <em>Save</em>
+button towards the bottom left of the green design panel. The saved dive
+plan will appear in the <strong>Dive List</strong> panel of <em>Subsurface</em>.</p></div>
+</div>
+<div class="sect2">
+<h3 id="_the_dive_plan_details">11.4. The dive plan details</h3>
+<div class="paragraph"><p>On the bottom right of the dive planner, under <em>Dive Plan Details</em>, the
+exact details of the dive plan are provided. These details may be modified
+by checking any of the options under the <em>Dive Notes</em> section of the dive
+planner, immediately to the left of the <em>Dive Plan Details</em>. If a <em>Verbatim
+diveplan</em> is requested, a detailed sentence-level explanation of the dive
+plan is given. If any of the management specifications have been exceeded
+during the planning, a warning message is printed underneath the dive plan
+information.</p></div>
+<div class="paragraph"><p>If the option <em>Display segment duration</em> is checked, then the duration of
+each depth level is indicated in the <em>Dive Plan Details</em>. This duration
+INCLUDES the transition time to get to that level. However, if the <em>Display
+transition in deco</em> option is checked, the transitions are shown separately
+from the segment durations at a particular level.</p></div>
+</div>
+<div class="sect2">
+<h3 id="S_Replan">11.5. Modifying an existing dive plan</h3>
+<div class="paragraph"><p>Normally, when a dive plan has been saved, it is accessible from the <strong>Dive
+List</strong>, like any other dive log. Within the <strong>Dive List</strong> there is not a way to
+change a saved dive plan.  To perform changes to a dive plan, select it on
+the <strong>Dive List</strong>. Then, in the main menu, select <em>Log &#8594; Re-plan dive</em>. This
+will open the selected dive plan within the dive planner, allowing changes
+to be made and saved as usual.</p></div>
+<div class="paragraph"><p>In addition there is the option "Save new". This keeps the original planned
+dive and adds a (possibly modified) copy to the dive list. If that copy is
+saved with the same start time as the original, the two dives are considered
+two versions of the same dive and do not influence other each during
+decompression calculation (see next section).</p></div>
+</div>
+<div class="sect2">
+<h3 id="_planning_for_repetitive_dives">11.6. Planning for repetitive dives</h3>
+<div class="paragraph"><p>Repetitive dives can easily be planned if the dates and start times of the
+repetitive dive set is specified appropriately in the top left-hand <em>Start
+Time</em> field. <em>Subsurface</em> calculates the gas loading figures correctly and
+the effect of the first dive is evaluated on later dives.</p></div>
+<div class="paragraph"><p>If one has just completed a long/deep dive and is planning another dive,
+then highlight, in the <strong>Dive List</strong>, the dive that has just been completed
+and then activate the planner. Depending on the start time of the planned
+dive, the planner takes into account the gas loading incurred during the
+completed dive and allows planning within these limitations.</p></div>
+<div class="paragraph"><p>If only a few standard configurations are used (e.g. in GUE), then a
+template dive can be created conforming to one of the configurations. If one
+now wishes to plan a dive using this configuration, just highlight the
+template dive in the <strong>Dive List</strong> and activate the planner: the planner takes
+into account the configuration in the highlighted dive.</p></div>
+</div>
+<div class="sect2">
+<h3 id="_printing_the_dive_plan">11.7. Printing the dive plan</h3>
+<div class="paragraph"><p>Selecting the <em>Print</em> button in the planner allows printing of the <em>Dive
+Plan Details</em> for wet notes. Alternatively one can cut and paste the <em>Dive
+Plan Details</em> for inclusion in a text file or word processing document.</p></div>
+<div class="paragraph"><p>Dive plans have many characteristics in common with dive logs (dive profile,
+dive notes, etc).  After a dive plan has been saved, the dive details and
+gas calculations are saved in the <strong>Dive Notes</strong> tab. While a dive plan is
+being designed, it can be printed using the <em>Print</em> button in the dive
+planner. This prints the dive details and gas calculations in the <em>Dive Plan
+Details</em> panel of the dive planner. However, after the plan has been saved,
+it is represented in a way very similar to a dive log and the gas
+calculations cannot be accessed in the same way as during the planning
+process. The only way to print the dive plan is to use the <em>File&#8594;Print</em>
+facility on the main menu in the same way as for dive logs or by copy and
+paste to a word processor.</p></div>
+</div>
+</div>
+</div>
+<div class="sect1">
+<h2 id="S_Configure">12. Configuring a dive computer</h2>
+<div class="sectionbody">
+<div class="paragraph"><p><em>Subsurface</em> enables one to configure a dive computer. Currently the
+Heinrichs-Weikamp (OSTC 2, OSTC 3) and Suunto Vyper (Stinger, Mosquito, D3,
+Vyper, Vytec, Cobra, Gekko and Zoop) family of dive computers are
+supported. A large number of settings of these dive computers can be read
+and changed to different values. As a first step, ensure that the
+appropriate hardware driver is installed for the dive computer and that the
+device name of the dive computer is known.  See
+<a href="#_appendix_a_operating_system_specific_information_for_importing_dive_information_from_a_dive_computer">APPENDIX A</a> for information on how to do this.</p></div>
+<div class="paragraph"><p>Once the dive computer is connected to the <em>Subsurface</em> computer, select
+<em>File&#8594;Configure dive computer</em> from the <em>Main Menu</em>. Provide the
+appropriate device name in the text box at the top of the configuration
+panel that opens and select the appropriate dive computer model from the
+panel on the lefthand (see image below).</p></div>
+<div class="imageblock" style="text-align:center;">
+<div class="content">
+<img src="images/Configure_dc_f20.jpg" alt="FIGURE: Configure dive computer" />
+</div>
+</div>
+<div class="paragraph"><p>Using the appropriate buttons on the configuration panel, the following
+actions can be performed:</p></div>
+<div class="ulist"><ul>
+<li>
+<p>
+<strong>Retrieve available details</strong>. This loads the existing configuration from the dive computer
+   to <em>Subsurface</em>, showing this in the configuration panel.
+</p>
+</li>
+<li>
+<p>
+<strong>Save changes to device</strong>. This changes the configuration of the
+   dive computer to correspond to the information shown in the configuration panel.
+</p>
+</li>
+<li>
+<p>
+<strong>Backup</strong>. This saves the configuration data to a file. <em>Subsurface</em> asks for
+   a file location and file name for the saved information.
+</p>
+</li>
+<li>
+<p>
+<strong>Restore backup</strong>. This loads the information from a backup file and displays it
+   in the configuration panel.
+</p>
+</li>
+<li>
+<p>
+<strong>Update firmware</strong>. If new firmware is available for the dive computer, this is
+   loaded into the dive computer.
+</p>
+</li>
+</ul></div>
+</div>
+</div>
+<div class="sect1">
+<h2 id="_description_of_the_subsurface_main_menu_items">13. Description of the Subsurface Main Menu items</h2>
+<div class="sectionbody">
+<div class="paragraph"><p>This section describes the functions and operation of the items in the Main
+Menu of Subsurface. Several of the items below are links to sections of this
+manual dealing with the appropriate operations.</p></div>
+<div class="sect2">
+<h3 id="_file">13.1. File</h3>
+<div class="paragraph"><p><a href="#S_NewLogbook"><em>New Logbook</em></a> - Close the currently open dive logbook and
+clear all dive information.
+<em>Open logbook</em> - This opens the file manager in order to select a dive
+logbook to open.
+- <em>Save</em> - Save the dive logbook that is currently open.
+- <em>Save as</em> - Save the current logbook under a different file name.
+- <em>Close</em> - Close the dive logbook that is currently open.
+<a href="#S_ExportLog"><em>Export</em></a> - Export the currently open dive logbook (or the
+selected dives in the logbook) to one of several formats.
+- <a href="#S_PrintDivelog"><em>Print</em></a> - Print the currently open logbook.
+- <a href="#S_Preferences"><em>Preferences</em></a> - Set the <em>Subsurface</em> preferences.
+- <a href="#S_Configure"><em>Configure dive computer</em></a> - Edit the configuration of a dive
+  computer.
+- <em>Quit</em> - Quit <em>Subsurface</em>.</p></div>
+</div>
+<div class="sect2">
+<h3 id="_import">13.2. Import</h3>
+<div class="paragraph"><p><a href="#S_ImportDiveComputer"><em>Import from dive computer</em></a> - Import dive
+information from a dive computer.
+<a href="#Unified_import"><em>Import Log Files</em></a> - Import dive information from a file
+in in a <em>Subsurface</em>-compatible format.
+<a href="#S_Companion"><em>Import GPS data from Subsurface web service</em></a> - Load GPS
+coordinates from the <em>Subsurface</em> mobile phone app.
+<a href="#S_ImportingDivelogsDe"><em>Import from Divelogs.de</em></a> - Import dive
+information from <em>www.Divelogs.de</em>.</p></div>
+</div>
+<div class="sect2">
+<h3 id="_log">13.3. Log</h3>
+<div class="ulist"><ul>
+<li>
+<p>
+<a href="#S_EnterData"><em>Add Dive</em></a> - Manually add a new dive to the <strong>Dive List</strong>
+  panel.
+</p>
+</li>
+<li>
+<p>
+<a href="#S_DivePlanner"><em>Plan Dive</em></a> - This feature allows the planning of dives.
+</p>
+</li>
+<li>
+<p>
+<a href="#S_Replan"><em>Re-plan dive</em></a> - Edit a dive plan that has been saved into the
+  <strong>Dive List</strong>.
+</p>
+</li>
+<li>
+<p>
+<a href="#S_CopyComponents"><em>Copy dive components</em></a> - By selecting this option, one
+  can copy information from several fields of a dive log onto the clipboard.
+</p>
+</li>
+<li>
+<p>
+<em>Paste dive components</em> - Paste, into the selected dives in the <strong>Dive List</strong>,
+   the information copied using the <em>Copy dive components</em> option.
+<a href="#S_Renumber"><em>Renumber</em></a> - Renumber the dives listed in the <strong>Dive List</strong>
+panel.
+<a href="#S_Group"><em>Auto Group</em></a> - Group the dives in the <strong>Dive List</strong> panel into
+dive trips.
+</p>
+</li>
+<li>
+<p>
+<a href="#S_DeviceNames"><em>Edit Device Names</em></a> - Edit the names of dive computers to
+  facilitate your logs.
+</p>
+</li>
+<li>
+<p>
+<a href="#S_Filter"><em>Filter divelist</em></a> - Select only some dives, based on specific
+  tags or dive criteria.
+</p>
+</li>
+</ul></div>
+</div>
+<div class="sect2">
+<h3 id="_view">13.4. View</h3>
+<div class="paragraph"><p><a href="#S_ViewPanels"><em>All</em></a> - View the four main <em>Subsurface</em> panels
+simmultaneously.
+- <a href="#S_ViewPanels"><em>Dive List</em></a> - View only the <strong>Dive List</strong> panel.
+- <a href="#S_ViewPanels"><em>Profile</em></a> - View only the <strong>Dive Profile</strong> panel.
+- <a href="#S_ViewPanels"><em>Info</em></a> - View only the <strong>Dive Notes</strong> panel.
+- <a href="#S_ViewPanels"><em>Globe</em></a> - View only the <strong>World Map</strong> panel.
+<em>Yearly Statistics</em> - Display summary statistics about dives during this and
+past years.
+- <em>Prev DC</em> - Switch to previous dive computer.
+- <em>Next DC</em> - Switch to next dive computer.
+- <em>Full Screen</em> - Toggles Full Screen mode.</p></div>
+</div>
+<div class="sect2">
+<h3 id="_help">13.5. Help</h3>
+<div class="paragraph"><p><em>About Subsurface</em> - Show a panel with the version number of <em>Subsurface</em> as
+well as licensing information.
+<em>Check for updates</em> - Find out whether a newer version of Subsurface is
+available on the <a href="http://subsurface-divelog.org/"><em>Subsurface</em> web site</a>.
+- <em>User Manual</em> - Open a window showing this user manual.</p></div>
+</div>
+</div>
+</div>
+<div class="sect1">
+<h2 id="_appendix_a_operating_system_specific_information_for_importing_dive_information_from_a_dive_computer">14. APPENDIX A: Operating system specific information for importing dive information from a dive computer.</h2>
+<div class="sectionbody">
+<div class="sect2">
+<h3 id="_make_sure_that_the_os_has_the_required_drivers_installed">14.1. Make sure that the OS has the required drivers installed</h3>
+<div class="admonitionblock">
+<table><tr>
+<td class="icon">
+<img src="images/icons/drivers.jpg" alt="Note" />
+</td>
+<td class="content">The operating system of the desktop computer needs the appropriate drivers
+in order to communicate with the dive computer in whichever way the dive
+computer prefers (e.g. bluetooth, USB, infra-red).</td>
+</tr></table>
+</div>
+<div class="ulist"><ul>
+<li>
+<p>
+On Linux users need to have the correct kernel module loaded. Most
+          distributions will do this automatically, so the user does not need to load
+          kernel modules. However, some communication protocols require an additional
+          driver, especially for rarely used technology such as infra-red.
+</p>
+</li>
+<li>
+<p>
+On Windows, the OS should offer to download the correct driver once the user
+          connects the dive computer to the USB port and operating system sees the
+          equipment for the first time.
+</p>
+</li>
+</ul></div>
+<div class="paragraph"><p>On a Mac users sometimes have to manually hunt for the correct driver. For
+example the correct driver for the Mares Puck devices or any other dive
+computer using a USB-to-serial interface based on the Silicon Labs CP2101 or
+similar chip can be found as <em>Mac_OSX_VCP_Driver.zip</em> at the
+<a href="http://www.silabs.com/support/pages/document-library.aspx?p=Interface&amp;f=USB%20Bridges&amp;pn=CP2101">Silicon
+Labs document and software repository</a>.</p></div>
+</div>
+<div class="sect2">
+<h3 id="S_HowFindDeviceName">14.2. How to Find the Device Name for USB devices and set its write permission</h3>
+<div class="admonitionblock">
+<table><tr>
+<td class="icon">
+<img src="images/icons/usb.jpg" alt="Note" />
+</td>
+<td class="content">When a user connects the dive computer by using a USB connector, usually
+<em>Subsurface</em> will either propose a drop down list that contains the correct
+device name (or mount point for the Uemis Zurich), or it will disable the
+device select drop down if no device name is needed at all. In the rare
+cases where this doesn&#8217;t work, here are some suggestions of ways to find out
+what the device name is:</td>
+</tr></table>
+</div>
+<div class="paragraph"><div class="title">On Windows:</div><p>Simply try COM1, COM2, etc. The drop down list should contain all connected
+COM devices.</p></div>
+<div class="paragraph"><div class="title">On MacOS:</div><p>The drop down box should find all connected dive computers.</p></div>
+<div class="paragraph"><div class="title">On Linux:</div><p>There is a definitive way to find the port:</p></div>
+<div class="ulist"><ul>
+<li>
+<p>
+Disconnect the USB cable from the dive computer
+</p>
+</li>
+<li>
+<p>
+Open a terminal
+</p>
+</li>
+<li>
+<p>
+Type the command: <em>dmesg</em> and press enter
+</p>
+</li>
+<li>
+<p>
+Plug in the USB cable of the dive computer
+</p>
+</li>
+<li>
+<p>
+Type the command: <em>dmesg</em> and press enter
+</p>
+</li>
+</ul></div>
+<div class="paragraph"><p>A message similar to this one should appear:</p></div>
+<div class="literalblock">
+<div class="content">
+<pre><code>usb 2-1.1: new full speed USB device number 14 using ehci_hcd
+usbcore: registered new interface driver usbserial
+USB Serial support registered for generic
+usbcore: registered new interface driver usbserial_generic
+usbserial: USB Serial Driver core
+USB Serial support registered for FTDI USB Serial Device
+ftdi_sio 2-1.1:1.0: FTDI USB Serial Device converter detected
+usb 2-1.1: Detected FT232BM
+usb 2-1.1: Number of endpoints 2
+usb 2-1.1: Endpoint 1 MaxPacketSize 64
+usb 2-1.1: Endpoint 2 MaxPacketSize 64
+usb 2-1.1: Setting MaxPacketSize 64
+usb 2-1.1: FTDI USB Serial Device converter now attached to ttyUSB3
+usbcore: registered new interface driver ftdi_sio
+ftdi_sio: v1.6.0:USB FTDI Serial Converters Driver</code></pre>
+</div></div>
+<div class="paragraph"><p>The third line from the bottom shows that the FTDI USB adapter is detected
+and connected to <code>ttyUSB3</code>. This information can now be used in the import
+settings as <code>/dev/ttyUSB3</code> which directs Subsurface to the correct USB port.</p></div>
+<div class="paragraph"><p>Ensuring that the user has write permission to the USB serial port:</p></div>
+<div class="paragraph"><p>On Unix-like operating systems the USB ports can only be accessed by users
+who are members of the <code>dialout</code> group. If one is not root, one may not be a
+member of that group and will not be able to use the USB port. Let us assume
+one&#8217;s username is <em>johnB</em>.</p></div>
+<div class="paragraph"><p>As root, type: <code>usermod -a -G dialout johnB</code> (Ubuntu users: <code>sudo usermod -a
+-G dialout johnB</code>)  This makes johnB a member of the <code>dialout</code> group.
+Type: <code>id johnB</code>     This lists all the groups that johnB belongs to and
+verifies that
+the appropriate group membership has been created. The <code>dialout</code> group should
+be listed
+among the different IDs.
+Under some circumstances this change takes only effect (eg. on Ubuntu) after
+one logs out and then logs in again.</p></div>
+<div class="paragraph"><p>With the appropriate device name (e.g. <code>dev/ttyUSB3</code>) and with write
+permission to the USB port, the dive computer interface can connect and one
+should be able to import dives.</p></div>
+</div>
+<div class="sect2">
+<h3 id="S_HowFindBluetoothDeviceName">14.3. Setting up bluetooth enabled devices</h3>
+<div class="admonitionblock">
+<table><tr>
+<td class="icon">
+<img src="images/icons/bluetooth.jpg" alt="Note" />
+</td>
+<td class="content">For dive computers communicating through bluetooth like the Heinrichs
+Weikamp Frog or the Shearwater Predator and Petrel there is a different
+procedure to get the devices name to communicate with <em>Subsurface</em>. Follow
+these steps:</td>
+</tr></table>
+</div>
+<div class="ulist"><ul>
+<li>
+<p>
+<strong>For the dive computer, after enabling Bluetooth, ensure it is in Upload mode.</strong>
+</p>
+</li>
+</ul></div>
+<div class="paragraph"><p>For Bluetooth pairing of the dive computer, refer to the manufacturer&#8217;s user
+guide. When using a Shearwater Predator/Petrel, select <em>Dive Log &#8594; Upload
+Log</em> and wait for the <em>Wait PC</em> message.</p></div>
+<div class="ulist"><ul>
+<li>
+<p>
+<strong>Pair the <em>Subsurface</em> computer with the dive computer.</strong>
+</p>
+</li>
+</ul></div>
+<div class="paragraph"><div class="title">On Windows:</div><p>Bluetooth is most likely already enabled. For pairing with the dive computer
+choose <em>Control Panel&#8594;Bluetooth Devices&#8594;Add Wireless Device</em>.  This should
+bring up a dialog showing your dive computer (in Bluetooth mode) and
+allowing pairing. Right click on it and choose <em>Properties&#8594;COM Ports</em> to
+identify the port used for your dive computer. If there are several ports
+listed, use the one saying "Outgoing" instead of "Incoming".</p></div>
+<div class="paragraph"><p>For downloading to <em>Subsurface</em>, the <em>Subsurface</em> drop-down list should
+contain this COM port already. If not, enter it manually.</p></div>
+<div class="paragraph"><p>Note: If there are issues afterwards when downloading from the dive computer
+using other software, remove the existing pairing with the dive computer.</p></div>
+<div class="paragraph"><div class="title">On MacOS:</div><p>Click on the Bluetooth symbol in the menu bar and select <em>Set up Bluetooth
+Device&#8230;</em>. The dive computer should then show up in the list of
+devices. Select it and go through the pairing process. This step should only
+be needed once for initial setup.</p></div>
+<div class="paragraph"><p>Once the pairing is completed the correct device is shown in the <em>Device or
+Mount Point</em> drop-down in the <em>Subsurface</em> <strong>Import</strong> dialog.</p></div>
+<div class="paragraph"><div class="title">On Linux</div><p>Ensure Bluetooth is enabled on the <em>Subsurface</em> computer.  On most common
+distributions this should be true out of the box and pairing should be
+straight forward. For instance, Gnome3 shows a Bluetooth icon in the upper
+right corner of the desktop where one selects <em>Set up New Device</em>. This
+should show a dialog where one can select the dive computer (which already
+should be in Bluetooth mode) and pair it.  If a PIN is required, try
+manually setting <em>0000</em>.</p></div>
+<div class="paragraph"><p>In the rare cases where the above is not true, then depending on your
+system, try <code>initd</code> or <code>systemd</code>. This might be different and also involve
+loading modules specific to your hardware. In case your system is running
+<code>systemd</code>, manually run <code>systemctl start bluetooth.service</code> to enable it, in
+case of <code>initd</code>, run something like <code>rc.config start bluetoothd</code> or
+<code>/etc/init.d/bluetooth start</code>.</p></div>
+<div class="paragraph"><p>One may also use a manual approach by using such commands:</p></div>
+<div class="paragraph"><p><code>hciconfig</code> shows the Bluetooth devices available on your computer (not dive
+computer), most likely one will see a hci0, if not try <code>hcitool -a</code> to see
+inactive devices and run <code>sudo hciconfig hci0 up</code> to bring them up.</p></div>
+<div class="paragraph"><p><code>hcitool scanning</code> gets a list of bluetooth enabled client devices, look for
+the dive computer and remember the MAC address are shown there</p></div>
+<div class="paragraph"><p><code>bluez-simple-agent hci0 10:00:E8:C4:BE:C4</code> pairs the dive computer with the
+bluetooth stack of the <em>Subsurface</em> computer, copy/paste the MAC address
+from the output of <em>hcitool scanning</em></p></div>
+<div class="paragraph"><p>Unfortunately on Linux binding to a communication device has to be done
+manually by running:</p></div>
+<div class="paragraph"><p><code>rfcomm bind /dev/rfcomm0 10:00:E8:C4:BE:C4</code> binds the dive computer to a
+communication device in the desktop computer, in case rfcomm is already
+taken use rfcomm1 or up. IMPORTANT: Copy/paste the MAC address from the
+output of <code>hcitool scanning</code>, the MAC address shown above will not work.</p></div>
+<div class="paragraph"><p>For downloading dives in <em>Subsurface</em> specify the device name connected to
+the MAC address in the last step above, e.g. <em>/dev/rfcomm0</em>.</p></div>
+</div>
+</div>
+</div>
+<div class="sect1">
+<h2 id="_appendix_b_dive_computer_specific_information_for_importing_dive_information">15. APPENDIX B: Dive Computer specific information for importing dive information.</h2>
+<div class="sectionbody">
+<div class="sect2">
+<h3 id="S_ImportUemis">15.1. Import from a Uemis Zurich</h3>
+<div class="admonitionblock">
+<table><tr>
+<td class="icon">
+<img src="images/icons/iumis.jpg" alt="Note" />
+</td>
+<td class="content"><em>Subsurface</em> downloads the information stored on the SDA (the built-in file
+system of the Uemis) including information about dive spots and
+equipment. Buddy information is not yet downloadable.  Things are very
+similar to a normal USB-connected dive computer (the Uemis is one of those
+that recharge when connected to the USB port).  The main difference is that
+one does not enter a device name, but instead the location where the
+UEMISSDA file system is mounted once connected to the dive computer. On
+Windows this is a drive letter ( often <em>E:</em> or <em>F:</em>), on a Mac this is
+<em>/Volumes/UEMISSDA</em> and on Linux systems this differs depending on the
+distribution. On Fedora it usually is
+<em>/var/run/media/&lt;your_username&gt;/UEMISSDA</em>. In all cases <em>Subsurface</em> should
+suggest the correct location in the drop down list.</td>
+</tr></table>
+</div>
+<div class="paragraph"><p>After selecting the above device name, download the dives from the Uemis
+Zurich. One technical issue with the Uemis Zurich download implementation
+(this is a Uemis firmware limitation, not a <em>Subsurface</em> issue) is that one
+cannot download more than about 40-50 dives without running out of memory on
+the SDA. This will usually only happen the very first time one downloads
+dives from the Uemis Zurich.  Normally when downloading at the end of a day
+or even after a dive trip, the capacity is sufficient. If <em>Subsurface</em>
+displays an error that the dive computer ran out of space the solution is
+straight forward.  Disconnect the SDA, turn it off and on again, and
+reconnect it. You can now retry (or start a new download session) and the
+download will continue where it stopped previously. One may have to do this
+more than once, depending on how many dives are stored on the dive computer.</p></div>
+</div>
+<div class="sect2">
+<h3 id="S_ImportingGalileo">15.2. Importing dives from the Uwatec Galileo</h3>
+<div class="admonitionblock">
+<table><tr>
+<td class="icon">
+<img src="images/icons/Galileo.jpg" alt="Note" />
+</td>
+<td class="content">The Uwatec Galileo dive computers use infra red (IrDA) communication between
+the dive computer and Subsurface. The Uwatec hardware uses a USB dongle
+based on the serial infra-red (SIR) protocol and the MSC7780 IrDA controller
+manufactured by MosChip and marketed by Scubapro and some electronics
+companies.  Under Linux, the kernel already provides for communication using
+the IrDA protocol. However, the user additionally needs to load a driver for
+the IrDA interface with the dive computer. The easiest way is to load the
+<strong>irda-tools</strong> package from the
+<a href="http://irda.sourceforge.net/docs/startirda.html">Linux IrDA Project</a>.  After
+the installation of the irda-tools, the <strong>root user</strong> can specify a device
+name from the console as follows: <code>irattach irda0</code></td>
+</tr></table>
+</div>
+<div class="paragraph"><p>After executing this command, Subsurface will recognise the Galileo dive
+computer and download dive information.</p></div>
+<div class="paragraph"><p>Under Windows, a similar situation exists. Drivers for the MCS7780 are
+available from some Internet web sites e.g.
+<a href="http://www.drivers-download.com/Drv/MosChip/MCS7780/">www.drivers-download.com</a>.</p></div>
+<div class="paragraph"><p>For the Apple Mac, IrDA communication via the MCS7780 link is not available
+for OSX 10.6 or higher.</p></div>
+</div>
+<div class="sect2">
+<h3 id="S_ImportingDR5">15.3. Importing dives from Heinrichs Weikamp DR5</h3>
+<div class="admonitionblock">
+<table><tr>
+<td class="icon">
+<img src="images/icons/HW_DR5.jpg" alt="Note" />
+</td>
+<td class="content">When mounted as a USB drive the Heinrichs Weikamp DR5 saves a single UDDF
+file for every dive.  Mark all the dives you&#8217;d like to import or open.
+Note: The DR5 does not seem to store gradient factors nor deco information,
+so for <em>Subsurface</em> it is not possible to display them. Adjust the gradient
+factors in the <em>Graph Settings</em> in <em>Subsurface</em> to generate a deco overlay
+in the <em>Subsurface</em> <strong>Dive Profile</strong> panel but please note that the deco
+calculated by <em>Subsurface</em> will most likely differ from the one displayed on
+the DR5.</td>
+</tr></table>
+</div>
+</div>
+<div class="sect2">
+<h3 id="_import_from_shearwater_predator_using_bluetooth">15.4. Import from Shearwater Predator using Bluetooth</h3>
+<div class="admonitionblock">
+<table><tr>
+<td class="icon">
+<img src="images/icons/predator.jpg" alt="Note" />
+</td>
+<td class="content">Using a Shearwater Predator one may be able to pair Bluetooth but then
+encounter issues when downloading, showing errors like <em>Slip RX: unexp. SLIP
+END</em> on the Predator.  This might also arise when using other dive log
+software and operating systems other than Linux. We have no detailed idea
+about the source and how to fix this, but it is reported to be solved
+sometimes by one of these steps:</td>
+</tr></table>
+</div>
+<div class="ulist"><ul>
+<li>
+<p>
+use the Bluetooth dongle which came with the Shearwater Predator instead of
+   the built-in one of the <em>Subsurface</em> computer
+</p>
+</li>
+<li>
+<p>
+switch to different Bluetooth drivers for the same hardware
+</p>
+</li>
+<li>
+<p>
+switch off WiFi while using Bluetooth
+</p>
+</li>
+</ul></div>
+</div>
+<div class="sect2">
+<h3 id="S_PoseidonMkVI">15.5. Importing dive logs from the Poseidon MkVI Discovery</h3>
+<div class="admonitionblock">
+<table><tr>
+<td class="icon">
+<img src="images/MkVI.jpeg" alt="Note" />
+</td>
+<td class="content">Download of dive logs from the MkVI is performed using a custom
+communications adapter and the <em>Poseidon PC Configuration Software</em>,
+obtained when purchasing the MKVI equipment. The latter is a Windows
+application allowing configuration of equipment and storage of dive
+logs. Communication between dive computer and desktop computer utilises the
+IrDA infra-red protocol. Only data for one dive can be downloaded at a time,
+comprising three files:</td>
+</tr></table>
+</div>
+<div class="paragraph"><p>Setup configuration for the dive and key dive parameters (file with a .txt
+extension)
+- Dive log details (file with a .csv extension)
+Redbook format dive log (file with .cvsr extension). This is a compressed
+version of the dive log using a proprietary format.</p></div>
+<div class="paragraph"><p><em>Subsurface</em> accesses the .txt and the .csv files to obtain dive log
+information.</p></div>
+</div>
+<div class="sect2">
+<h3 id="_importing_dive_logs_from_the_apd_inspiration_ccr">15.6. Importing dive logs from the APD Inspiration CCR</h3>
+<div class="admonitionblock">
+<table><tr>
+<td class="icon">
+<img src="images/APDComputer.jpg" alt="Note" />
+</td>
+<td class="content">The dive logs of an APD Inspiration or similar CCR dive computer are
+downloaded using a communications adapter and <em>AP Communicator</em>, obtained
+when purchasing the equipment. The dive logs can be viewed using the <em>AP Log
+Viewer</em>, within Windows or Mac/OS. However, APD logs can be viewed and
+managed from within <em>Subsurface</em> (together with dives using many other types
+of dive computer). The APD inspiration dive logs are imported into
+<em>Subsurface</em> as follows:</td>
+</tr></table>
+</div>
+<div class="ulist"><ul>
+<li>
+<p>
+Open a dive within the <em>AP Log Viewer</em>.
+</p>
+</li>
+<li>
+<p>
+Select the tab at the top of the screen, entitled "<em>Data</em>".
+</p>
+</li>
+<li>
+<p>
+If the raw dive log data show on the screen, click on "<em>Copy to Clipboard</em>".
+</p>
+</li>
+<li>
+<p>
+Open a text editor, e.g. Notepad (Windows), TextWrangler (Mac).
+Copy the contents of the clipboard into the text editor and save the text
+file with a filename extension of .CSV
+</p>
+</li>
+<li>
+<p>
+Within <em>Subsurface</em>, select <em>Import&#8594;Import log files</em> to open the
+  <a href="#Unified_import">universal import dialogue</a>.
+</p>
+</li>
+<li>
+<p>
+In the dropdown list towards the bottom right of the dialogue, select "<em>CSV
+  files</em>".
+On the list of file names select the .CSV file that has been created
+above. An import dialogue opens.
+In the dropdown list on the middle right labeled '<em>Pre-configured imports</em>",
+select <em>APD Log Viewer</em>.
+</p>
+</li>
+<li>
+<p>
+Ensure the other settings for the ADP dive log are appropriate, then select
+  <em>OK</em>.
+</p>
+</li>
+</ul></div>
+<div class="paragraph"><p>The APD dive log will appear within <em>Subsurface</em>.</p></div>
+</div>
+</div>
+</div>
+<div class="sect1">
+<h2 id="_appendix_c_exporting_dive_log_information_from_external_dive_log_software">16. APPENDIX C: Exporting Dive log information from external dive log software.</h2>
+<div class="sectionbody">
+<div class="paragraph"><p>The import of dive log data from external dive log software is mostly
+performed using the dialogue found by selecting <em>Import</em> from the Main Menu,
+then clicking on <em>Import Log Files</em>. This is a single-step process, more
+information about which can be found <a href="#Unified_import">here.</a> However, in
+some cases, a two-step process may be required:</p></div>
+<div class="paragraph"><p>Export the foreign dive log data to format that is accessible from
+<em>Subsurface</em>.
+2. Import the accessible dive log data into <em>Subsurface</em>.</p></div>
+<div class="paragraph"><p>This appendix provides some information about approaches to export dive log
+data from foreign dive log software. The procedures below mostly apply to
+Linux and/or Windows.</p></div>
+<div class="sect2">
+<h3 id="S_ImportingDivesSuunto">16.1. Exporting dives from <strong>Suunto Divemanager (DM3, DM4 or DM5)</strong></h3>
+<div class="admonitionblock">
+<table><tr>
+<td class="icon">
+<img src="images/icons/suuntologo.jpg" alt="Note" />
+</td>
+<td class="content">DiveManager is a MS Windows application for Suunto dive computers.
+Divemanager 3 (DM3) is an older version of the Suunto software. More recent
+Suunto dive computers use Divemanager version 4 or 5 (DM4 or DM5). The
+different versions of Divemanager use different methods and different file
+naming conventions to export dive log data.</td>
+</tr></table>
+</div>
+<div class="paragraph"><p><strong>Divemanager 3 (DM3):</strong></p></div>
+<div class="olist arabic"><ol class="arabic">
+<li>
+<p>
+Start <em>Suunto Divemanager 3</em> and log in with the name containing the logs
+</p>
+</li>
+<li>
+<p>
+Do not start the import wizard to import dives from the dive computer.
+In the navigation tree on the left side of the program-window, select the
+appropriate dives.
+</p>
+</li>
+<li>
+<p>
+Within the list of dives, select the dives you would like to import later:
+</p>
+<div class="ulist"><ul>
+<li>
+<p>
+To select certain dives: hold <em>ctrl</em> and click the dive
+To select all dives: Select the first dive, hold down shift and select the
+last dive
+</p>
+</li>
+</ul></div>
+</li>
+<li>
+<p>
+With the dives marked, use the program menu <em>File &#8594; Export</em>
+</p>
+</li>
+<li>
+<p>
+The export pop-up will show. Within this pop-up, there is one field called
+   <em>Export Path</em>.
+</p>
+<div class="ulist"><ul>
+<li>
+<p>
+Click the browse button next to the field Export Path
+</p>
+<div class="ulist"><ul>
+<li>
+<p>
+A file-manager like window pops up
+</p>
+</li>
+<li>
+<p>
+Navigate to the directory for storing the
+Divelog.SDE file
+</p>
+</li>
+<li>
+<p>
+Optionally change the name of the file for saving
+</p>
+</li>
+<li>
+<p>
+Click <em>Save</em>
+</p>
+</li>
+</ul></div>
+</li>
+<li>
+<p>
+Back in the Export pop-up, press the button <em>Export</em>
+</p>
+</li>
+</ul></div>
+</li>
+<li>
+<p>
+The dives are now exported to the file Divelog.SDE.
+</p>
+</li>
+</ol></div>
+<div class="paragraph"><p><strong>Divemanager 4 (DM4) and Divemanager 5 (DM5):</strong></p></div>
+<div class="paragraph"><p>DM4 and DM5 use identical mechanisms for exporting dive logs.  To export a
+divelog from Divemanager one needs to locate the DM4/DM5 database where the
+dives are stored. the user can either look for the original database or make
+a backup of the dives. Both methods are described here.</p></div>
+<div class="paragraph"><p>Locating the Suunto DM4 (or DM5) database:</p></div>
+<div class="olist arabic"><ol class="arabic">
+<li>
+<p>
+Start Suunto DM4/DM5
+</p>
+</li>
+<li>
+<p>
+Select <em>Help &#8594; About</em>
+</p>
+</li>
+<li>
+<p>
+Click <em>Copy</em> after text <em>Copy log folder path to clipboard</em>
+</p>
+</li>
+<li>
+<p>
+Now open Windows Explorer
+</p>
+</li>
+<li>
+<p>
+Paste the address to the path box at the top of the File Explorer
+</p>
+</li>
+<li>
+<p>
+The database is called DM4.db or DM5.db
+</p>
+</li>
+</ol></div>
+<div class="paragraph"><p>Making a backup copy of the Suunto DM4/DM5 database:</p></div>
+<div class="olist arabic"><ol class="arabic">
+<li>
+<p>
+Start Suunto DM4/DM5
+</p>
+</li>
+<li>
+<p>
+Select <em>File - Create backup</em>
+</p>
+</li>
+<li>
+<p>
+From the file menu select the location and name for the backup, we&#8217;ll use
+   DM4 (or DM5) in here with the default extension .bak
+</p>
+</li>
+<li>
+<p>
+Click <em>Save</em>
+</p>
+</li>
+<li>
+<p>
+The dives are now exported to the file DM4.bak (or DM5.bak)
+</p>
+</li>
+</ol></div>
+</div>
+<div class="sect2">
+<h3 id="_exporting_from_mares_dive_organiser_v2_1">16.2. Exporting from Mares Dive Organiser V2.1</h3>
+<div class="admonitionblock" id="Mares_Export">
+<table><tr>
+<td class="icon">
+<img src="images/icons/mareslogo.jpg" alt="Note" />
+</td>
+<td class="content">Mares Dive Organiser is a Windows application. The dive log is kept as a
+Microsoft SQL Compact Edition database with a <em>.sdf</em> filename extension. The
+database includes all Dive Organiser-registered divers on the particular
+computer and all Mares dive computers used. The safest way to obtain a copy
+of the dive database is to export the information to another compatible
+format which can be imported into <em>Subsurface</em>.</td>
+</tr></table>
+</div>
+<div class="paragraph"><p>Within Dive Organiser, select <em>Database &#8594; Backup</em> from the main menu and
+back up the database to the desk top.  This creates a zipped file
+DiveOrganiserxxxxx.dbf.
+Rename the file to DiveOrganiserxxxxx.zip. Inside the zipped directory is a
+file <em>DiveOrganiser.sdf</em>.
+3. Extract the <em>.sdf</em> file from the zipped folder to your Desktop.
+4. The password for accessing the .zip file is <em>mares</em>.</p></div>
+</div>
+<div class="sect2">
+<h3 id="S_ImportingDivingLog">16.3. Exporting dives from <strong>DivingLog 5.0</strong></h3>
+<div class="admonitionblock">
+<table><tr>
+<td class="icon">
+<img src="images/icons/divingloglogo.jpg" alt="Note" />
+</td>
+<td class="content">Unfortunately DivingLog XML files give us no indication on the preferences
+set on one&#8217;s system. So in order for <em>Subsurface</em> to be able to successfully
+import XML files from DivingLog one first needs to ensure that DivingLog is
+configured to use the Metric system (one can easily change this within
+Diving Log by selecting <em>File &#8594; Preferences &#8594; Units and Language</em> by
+clicking the <em>Metric</em> button). Then do the following:</td>
+</tr></table>
+</div>
+<div class="olist arabic"><ol class="arabic">
+<li>
+<p>
+In DivingLog open the <em>File &#8594; Export &#8594; XML</em> menu
+</p>
+</li>
+<li>
+<p>
+Select the dives to export
+</p>
+</li>
+<li>
+<p>
+Click on the export button and select the filename
+</p>
+</li>
+</ol></div>
+</div>
+</div>
+</div>
+<div class="sect1">
+<h2 id="S_Appendix_D">17. APPENDIX D: Exporting a spreadsheet to CSV format</h2>
+<div class="sectionbody">
+<div class="paragraph"><p>Many divers keep a diving log in some form of a digital file, commonly a
+spreadsheet with various fields of information. These logs can be easily
+imported into <em>Subsurface</em> (<a href="#S_ImportingManualCSV">Importing dives
+from_manually kept CSV file</a>), after the spreadsheet is converted in a .CSV
+file.  This section explains the procedure to convert a diving logbook
+stored in a spreadsheet to a .CSV file that will later be imported from
+<em>Subsurface</em>.  Creating a .CSV is a straightforward task, although the
+procedure is somewhat different according to which spreadsheet program is
+used.</p></div>
+<div class="paragraph"><p>The first step is to organize the diving data in the spreadsheet, so that
+the first row contains the names (or titles) of each column and the
+information for each dive is stored in a single row.  <em>Subsurface</em> supports
+many data items (Dive #, Date, Time, Duration, Location, GPS, Max Depth,
+Mean Depth, Buddy, Notes, Weight and Tags).  The user can organize dive data
+following a few simple rules:</p></div>
+<div class="olist arabic"><ol class="arabic">
+<li>
+<p>
+Date: use one of the following formats: yyyy-mm-dd, dd.mm.yyyy, mm/dd/yyyy
+</p>
+</li>
+<li>
+<p>
+Duration: the format should be minutes:seconds.
+</p>
+</li>
+<li>
+<p>
+Unit system: only one unit system shold be used (i.e., no mixture between
+   imperial and metric units)
+</p>
+</li>
+<li>
+<p>
+Tags and buddies: values should be separated using a comma.
+</p>
+</li>
+<li>
+<p>
+GPS position: users must use decimal degrees, e.g. 30.22496 30.821798
+</p>
+</li>
+</ol></div>
+<div class="sect2">
+<h3 id="_em_libreoffice_calc_em_and_em_openoffice_calc_em">17.1. <em>LibreOffice Calc</em> and <em>OpenOffice Calc</em></h3>
+<div class="paragraph"><p>These are open source spreadsheet applications forming parts of larger open
+source office suite applications. The user interaction with <em>LibreOffice</em>
+and <em>OpenOffice</em> is very similar.  In Libreoffice Calc the time format
+should be set to minutes:seconds - [mm]:ss and dates should be set to one
+of: yyyy-mm-dd, dd.mm.yyyy, mm/dd/yyyy. A typical dive log may look like
+this:</p></div>
+<div class="imageblock" style="text-align:center;">
+<div class="content">
+<img src="images/LOffice_spreadsheetdata.jpg" alt="FIGURE: Spreadsheet data" />
+</div>
+</div>
+<div class="paragraph"><p>To export the data as a .CSV file from within LibreOffice click <em>File &#8594;
+Save As</em>. On the dialogue that comes up, select the <em>Text CSV (.csv)</em> as the
+file type and select the option <em>Edit filter settings</em>.</p></div>
+<div class="imageblock" style="text-align:center;">
+<div class="content">
+<img src="images/LOffice_save_as_options.jpg" alt="FIGURE: Save as options" />
+</div>
+</div>
+<div class="paragraph"><p>After selecting <em>Save</em>, select the appropriate field delimiter (choose <em>Tab</em>
+to prevent conflicts with the comma when using this as a decimal point),
+then select <em>OK</em>.</p></div>
+<div class="imageblock" style="text-align:center;">
+<div class="content">
+<img src="images/LOffice_field_options.jpg" alt="FIGURE: Field options" />
+</div>
+</div>
+<div class="paragraph"><p>One can double check the .CSV file by opening it with a text editor, and
+then import the dive data as explained on the section
+<a href="#S_ImportingManualCSV">Importing dives from manually kept CSV files</a>.</p></div>
+</div>
+<div class="sect2">
+<h3 id="_microsoft_em_excel_em">17.2. Microsoft <em>Excel</em></h3>
+<div class="paragraph"><p>The field delimiter (called "<em>list separator</em>" in Microsoft manuals) is not
+accessible from within <em>Excel</em> and needs to be set through the <em>Microsoft
+Control Panel</em>. After changing the separator character, all software on the
+Windows machine use the new character as a separator.  One can change the
+character back to the default character by following the same procedure,
+outlined below.</p></div>
+<div class="ulist"><ul>
+<li>
+<p>
+In Microsoft Windows, click the <strong>Start</strong> button, and then select <em>Control
+  Panel</em> from the list on the right-hand side.
+</p>
+</li>
+<li>
+<p>
+Open the <em>Regional and Language Options</em> dialog box.
+Do one of the following: <strong> In Windows 7, click the <em>Formats</em> tab, and then
+click <em>Customize this format</em>.  </strong> In Windows XP, click the <em>Regional
+Options</em> tab, and then click <em>Customize</em>.
+</p>
+</li>
+<li>
+<p>
+Type a new separator in the <em>List separator</em> box. To use a TAB-delimited
+  file, type the word TAB in the box.
+</p>
+</li>
+<li>
+<p>
+Click <em>OK</em> twice.
+</p>
+</li>
+</ul></div>
+<div class="paragraph"><p>Below is an image of the <em>Control Panel</em>:</p></div>
+<div class="imageblock" style="text-align:center;">
+<div class="content">
+<img src="images/Win_SaveCSV2.jpg" alt="FIGURE: Win List separator" />
+</div>
+</div>
+<div class="paragraph"><p>To export the dive log in CSV format:</p></div>
+<div class="paragraph"><p>With the dive log opened in <em>Excel</em>, select the round Windows button at the
+top left, then <em>Save As</em>.</p></div>
+<div class="imageblock" style="text-align:center;">
+<div class="content">
+<img src="images/Win_SaveCSV1.jpg" alt="FIGURE: Excel save as option" />
+</div>
+</div>
+<div class="paragraph"><p>Click on the left-hand part of the <em>Save as</em> option, NOT on the arrow on the
+right-hand. This brings up a dialogue for saving the spreadsheet in an
+alternative format. From the dropdown list at the bottom of the dialogue,
+marked <em>Save as Type:</em>, select <em>CSV(Comma delimited) (*.CSV)</em>. Ensure that
+the appropriate folder has been selected to save the CSV file into.</p></div>
+<div class="imageblock" style="text-align:center;">
+<div class="content">
+<img src="images/Win_SaveCSV3.jpg" alt="FIGURE: Excel save CSV dialogue" />
+</div>
+</div>
+<div class="paragraph"><p>Select the <em>Save</em> button. The CSV-formatted file is saved into the folder
+that was selected. One can double check the .CSV file by opening it with a
+text editor, and then import the dive data as explained on the section
+<a href="#S_ImportingManualCSV">Importing dives from manually kept CSV files</a>.</p></div>
+</div>
+</div>
+</div>
+<div class="sect1">
+<h2 id="_appendix_e_faqs">18. APPENDIX E: FAQs.</h2>
+<div class="sectionbody">
+<div class="sect2">
+<h3 id="_subsurface_appears_to_miscalculate_gas_consumption_and_sac">18.1. Subsurface appears to miscalculate gas consumption and SAC</h3>
+<div class="paragraph" id="SAC_CALCULATION"><p><em>Question</em>: I dived with a 12.2 l tank, starting with 220 bar and ending
+with 100 bar, and I calculate a different SAC compared what <em>Subsurface</em>
+calculates. Is <em>Subsurface</em> miscalculating?</p></div>
+<div class="paragraph"><p><em>Answer</em>: Not really. What happens is that <em>Subsurface</em> actually calculates
+gas consumption differently - and better - than you expect.  In particular,
+it takes the incompressibility of the gas into account.  Traditionally, Gas
+consumption and SAC should be: <code>consumption = tank size x (start pressure -
+end pressure)</code></p></div>
+<div class="paragraph"><p>and that&#8217;s true for an ideal gas, and it&#8217;s what you get taught in dive
+theory.  But an "ideal gas" doesn&#8217;t actually exist, and real gases actually
+don&#8217;t compress linearly with pressure. Also, you are missing the fact that
+one atmosphere of pressure isn&#8217;t actually one bar.  So the <strong>real</strong>
+calculation is:</p></div>
+<div class="paragraph"><p><code>consumption = (amount_of_air_at_beginning - amount_of_air_at_end)</code></p></div>
+<div class="paragraph"><p>where the amount of air is <strong>not</strong> just "tank size times pressure in bar".
+It&#8217;s a combination of: "take compressibility into account" (which is a
+fairly small issue under 220 bar - you&#8217;ll see more differences when you do
+high-pressure tanks with 300bar) and "convert bar to atm" (which is the
+majority of your discrepancy).  Remember: one ATM is ~1.013 bar, so without
+the compressibility, your gas use is:</p></div>
+<div class="paragraph"><p><code>12.2*((220-100)/1.013)</code></p></div>
+<div class="paragraph"><p>which is about 1445, not 1464. So there was 19 l too much in your simple
+calculation that ignored the difference between 1 bar and one ATM.  The
+compressibility does show up above 200 bar, and takes that 1445 down about
+eight litres more, so you really did use only about 1437 l of air at surface
+pressure.</p></div>
+<div class="paragraph"><p>So be happy: your SAC really is better than your calculations indicated.  Or
+be sad: your cylinder contains less air than you thought it did.  And as
+mentioned, the "contains less air than you thought it did" really starts
+becoming much more noticeable at high pressure. A 400 bar really does not
+contain twice as much air as a 200 bar one. At lower pressures, air acts
+pretty much like an ideal gas.</p></div>
+</div>
+<div class="sect2">
+<h3 id="_some_dive_profiles_have_time_discrepancies_with_the_recorded_samples_from_my_dive_computer_8230">18.2. Some dive profiles have time discrepancies with the recorded samples from my dive computer&#8230;</h3>
+<div class="paragraph"><p><em>Subsurface</em> ends up ignoring surface time for many things (average depth,
+divetime, SAC, etc).  <em>Question</em>: Why do dive durations in my dive computer
+differ from that given by <em>Subsurface</em>?</p></div>
+<div class="paragraph"><p><em>Answer</em>: For example, if you end up doing a weight check (deep enough to
+trigger the "dive started")  but then come back up and wait five minutes for
+your buddies, your dive computer may say that your dive is 50 minutes long -
+because you have fifty minutes worth of samples - but subsurface will say
+it&#8217;s 45 minutes - because you were actually diving for 45 minutes.  It&#8217;s
+even more noticeable if you do things like divemastering the initial OW
+dives, when you may stay in the water for a long time, but spend most of it
+at the surface. And then you don&#8217;t want that to count as some kind of long
+dive”.</p></div>
+</div>
+</div>
+</div>
+</div>
+<div id="footnotes"><hr /></div>
+<div id="footer">
+<div id="footer-text">
+Last updated 2015-01-14 16:18:29 CET
+</div>
+</div>
+</body>
+</html>
diff --git a/Documentation/user-manual_fr.txt b/Documentation/user-manual_fr.txt
new file mode 100644
index 000000000..6e458c0c9
--- /dev/null
+++ b/Documentation/user-manual_fr.txt
@@ -0,0 +1,3553 @@
+:icons:
+:toc:
+:toc-placement: manual
+:numbered:
+
+image::images/Subsurface4Banner.jpg["Banner", align="center"]
+
+[big]#MANUEL UTILISATEUR#
+
+*Auteurs du manuel* : Willem Ferguson, Jacco van Koll, Dirk Hohndel, Reinout Hoornweg,
+Linus Torvalds, Miika Turkia, Amit Chaudhuri, Jan Schubert, Salvador Cuñat, Pedro Neves
+
+[blue]#_Version 4.3, Décembre 2014_#
+
+
+Bienvenue en tant qu'utilisateur de _Subsurface_, un programme avancé
+d'enregistrement de plongées (carnet de plongées) avec une bonne
+infrastructure pour décrire, organiser, interpréter et imprimer des plongées
+en scaphandre et en apnée. _Subsurface_ offre de nombreux avantages par
+rapport à d'autres solutions logicielles similaires :
+
+ - Do you need a flexible way of logging dives using recreational equipment,
+   even not using a dive computer?
+ - Do you use two different dive computer brands, each with its own proprietary
+   software for downloading dive logs? Do you dive with rebreathers as well as
+   open circuit or recreational equipment? Do you use a Reefnet Sensus
+   time-depth recorder in conjunction with a dive computer? _Subsurface_ offers
+   a standard interface for downloading dive logs from all these different
+   pieces of equipment and to store and analyse the dive logs within a unified
+   system.
+ - Do you use more than one operating system? _Subsurface_ is fully compatible
+   with Mac, Linux and Windows, allowing you to access your dive log on each of
+   your operating systems using a single application.
+ - Do you use Linux or Mac and your dive computer has only Windows-based
+   software for downloading dive information (e.g. Mares)? _Subsurface_
+   provides a way of downloading and analysing your dive logs on other
+   operating systems.
+ - Do you need an intuitive graphical dive planner that integrates with and
+   takes into account the dives that have already been logged?
+
+_Subsurface_ binaries are available for Windows PCs (Win XP or later), Intel
+based Macs (OS/X) and many Linux distributions. _Subsurface_ can be built
+for many more hardware platforms and software environments where Qt and
+libdivecomputer are available.
+
+The scope of this document is the use of the _Subsurface_ program. To
+install the software, consult the _Downloads_ page on the
+http://subsurface-divelog.org/[_Subsurface_ web site].  Please discuss
+issues with this program by sending an email to
+mailto:subsurface@subsurface-divelog.org[our mailing list] and report bugs
+at http://trac.hohndel.org[our bugtracker].  For instructions on how to
+build the software and (if needed) its dependencies please consult the
+INSTALL file included with the source code.
+
+*Audience*: Recreational Scuba Divers, Free Divers, Tec Divers, Professional
+Divers
+
+toc::[]
+
+[[S_UserSurvey]]
+
+Le sondage utilisateur
+----------------------
+In order to develop _Subsurface_ in a way that serves its users in the best
+possible way, it is important to have some user information. Upon launching
+_Subsurface_ after using this software for a week or so, a one-box user
+survey pops up. It is entirely optional and the user controls what, if any,
+data are sent to the _Subsurface_ development team. Any data that the user
+chooses to send is extremely useful, and will only be used to steer future
+development and to customise the software to fit the needs of the
+_Subsurface_ users. If one completes the survey, or clicks the option not to
+be asked again, that should be the last communication of this nature one
+receives.  However, if one's diving and/or subsurface habits change and one
+wishes to provide another survey, this can be done by launching _Subsurface_
+with the _--survey_ option on the command line.
+
+[[S_StartUsing]]
+Start Using the Program
+-----------------------
+
+The _Subsurface_ window is usually divided into four panels with a *Main
+Menu* (File Import Log View Filter Help) at the top of the window (for
+Windows and Linux) or the top of the screen (for Mac and Ubuntu Unity). The
+four panels are:
+
+The *Dive List* to the bottom left containing a list of all the dives in the
+user's dive log. A dive can be selected and highlighted on the dive list by
+clicking on it. In most situations the up/down keys can be used to switch
+between dives. The *Dive List* is an important tool for manipulating a dive
+log.
+
+The *Dive Map* to the bottom right, showing the user's dive sites on a world
+map and centred on the site of the last dive selected in the *Dive List*.
+
+The *Dive Info* to the top left, giving more detailed information on the
+dive selected in the *Dive List*, including some statistics for the selected
+dive or for all highlighted dive(s).
+
+The *Dive Profile* to the top right, showing a graphical dive profile of the
+selected dive in the *Dive List*.
+
+The dividers between panels can be dragged in order to change the size of
+any of the panels. _Subsurface_ remembers the position of the dividers, so
+the next time _Subsurface_ starts it uses the positions of the dividers from
+when the program was last used.
+
+If a dive is selected in the *Dive List*, the dive location, detailed
+information and profile of the _selected dive_ are shown in the respective
+panels. On the other hand, if one highlights more than one dive the last
+highlighted dive is the _selected dive_, but summary data of all
+_highlighted dives_ are shown in the *Stats* tab of the *Dive Info* panel
+(maximum, minimum and average depths, durations, water temperatures and SAC;
+total time and number of dives selected).
+
+[[S_ViewPanels]]
+
+image::images/main_window_f20.jpg["The Main Window", align="center"]
+
+The user can determine which of the four panels are displayed by selecting
+the *View* option on the main menu. This feature gives the user several
+choices of display:
+
+*All*: show all four of the panels as in the screenshot above.
+
+*Divelist*: Show only the Dive List.
+
+*Profile*: Show only the Dive Profile of the selected dive.
+
+*Info*: Show only the Dive Notes about the last selected dive and statistics for
+all highlighted dives.
+
+*Globe*: Show only the world map, centred on the last selected dive.
+
+Like many other functions that can be accessed via the Main Menu, these
+options can be triggered using keyboard shortcuts. The shortcuts for a
+particular system are shown with an underline in the main menu
+entries. Since different Operating Systems and the user chosen language may
+cause _Subsurface_ to use different shortcut keys they are not listed here
+in the user manual.
+
+When the program is started for the first time, it shows no information at
+all.  This is because the program doesn't have any dive information
+available. In the following sections, the procedures to create a new logbook
+will be described.
+
+[[S_NewLogbook]]
+Creating a new logbook
+----------------------
+Select _File -> New Logbook_ from the main menu. All existing dive data are
+cleared so that new information can be added. If there are unsaved data in
+an open logbook, the user is asked whether the open logbook should be saved
+before a new logbook is created.
+
+[[S_GetInformation]]
+== Storing dive information in the logbook
+
+Now that a new logbook was created, it is simple to add dive data to it.
+_Subsurface_ allows several ways of adding dive data to a logbook, detailed
+in the following sections.
+
+If the user has a handwritten divelog, a spreadsheet or another form of
+manually maintained divelog, dive data can be added to the logbook using one
+of these approaches:
+
+Enter dive information by hand. This is useful if the diver did not use a
+dive computer and dives were recorded in a written logbook. See:
+xref:S_EnterData[Entering dive information by hand]
+
+Import dive log information that has been maintained either as a spreadsheet
+or as a CSV file. Refer to: xref:S_Appendix_D[APPENDIX D: Exporting a
+spreadsheet to CSV format] and the text about
+xref:S_ImportingManualCSV[Importing dives from manually created CSV files]
+and
+
+If one has dives recorded using a dive computer, the depth profile of the
+dive and a large amount of additional information can be accessed. These
+dives can be imported from:
+
+- The divecomputer itself. See: xref:S_ImportDiveComputer[Importing new dive
+  information from a Dive Computer] or
+
+Proprietary software distributed by manufacturers of dive computers. Refer
+to: xref:S_ImportingAlienDiveLogs[Importing dive information from other
+digital data sources or other data formats].
+
+Import from spreadsheet or CSV files containing dive profiles.  See:
+xref:S_ImportingCSVDives[Importing dives in CSV format from dive computers
+or other dive log software]
+
+
+[[S_EnterData]]
+=== Entering dive information by hand
+
+This is usually the approach for dives without a dive computer. The basic
+record of information within _Subsurface_ is a dive. The most important
+information in a simple dive logbook usually includes dive type, date, time,
+duration, depth, the names of your dive buddy and of the dive master or dive
+guide, and some remarks about the dive. _Subsurface_ can store much more
+information than this for each dive. In order to add a dive to a dive log,
+select _Log -> Add Dive_ from the Main Menu. The program then shows three
+panels to enter information for a dive: two tabs in the *Dive Info* panel
+(*Dive Notes* and *Equipment*), as well as the *Dive Profile* panel that
+displays a graphical profile of each dive. These panels are respectively
+marked [red]#A#, [red]#B# and [red]#C# in the figure below. Each of these
+tabs will now be explained for data entry.
+
+image::images/AddDive1_f20.jpg["FIGURE: Add dive", align="center"]
+
+When one edits a field in Dive notes or Equipment panels, _Subsurface_
+enters *Editing Mode*, indicated by the message in the blue box at the top
+of the _Dive Notes_ panel (see the image below). This message is displayed
+in all the panels under Dive notes and Equipment when in *Editing Mode*.
+
+image::images/BlueEditBar_f20.jpg["Blue edit bar", align="center"]
+
+The _Save_ button should only be selected after all the parts of a dive have
+been entered.  When entering dives by hand, the _Info_, _Equipment_ and
+_Profile_ tabs should be completed before saving the information. By
+selecting the _Save_ button, a local copy of the information for this
+specific dive is saved in memory. When one closes Subsurface, the program
+will ask again, this time whether the complete dive log should be saved on
+disk or not.
+
+==== Dive Notes
+
+This panel contains the date, time and place information for a particular
+dive, environmental conditions, co-divers and buddies, as well as some
+descriptive information. If one clicks on the *Dive Notes* tab, the
+following fields are visible:
+
+image::images/AddDive2_f20.jpg["FIGURE: The Dive Notes tab", align="center"]
+
+The *Time* field reflects the date and the time of the dive. By clicking the
+date, a calendar is displayed from which one can choose the correct
+date. Press ESC to escape from the calendar.  The time values (hour and
+minutes) can also be edited directly by clicking on each of them in the text
+box and by overtyping the information displayed. The default date is the
+present date and the default time is an hour in advance of the present time.
+
+*Air and water temperatures*: the air and water temperatures during the
+dive can be typed directly on the fields to the right of the Start time.
+Temperature units are not needed, as they will be automatically supplied by
+_Subsurface_. Only the numerical value must be
+typed by the user (the units selected in the 'Preferences'
+will determine whether metric or imperial units are used).
+
+*Location*: Here the name of the dive site can be entered, e.g. "Tihany, Lake
+Balaton,
+Hungary". Auto completion of location names will make this easier if one
+frequently dives at the same sites.
+
+*Coordinates*: The geographic coordinates of the dive site should be entered
+here. These can come from three sources:
+
+One can find the coordinates on the world map in the bottom right hand part
+of the Subsurface window. The map displays a green bar indicating "No
+location data - Move the map and double-click to set the dive
+location". Upon a double-click at the appropriate place, the green bar
+disappears and the coordinates are stored.
+
+The coordinates can be obtained from the _Subsurface_ Companion app if the
+user has an Android device with GPS and if the coordinates of the dive site
+were stored using that device.  xref:S_Companion[Click here for more
+information]
+
+The coordinates can be entered by hand if they are known, using one of four
+formats with latitude followed by longitude:
+
+	ISO 6709 Annex D format e.g. 30°13'28.9"N 30°49'1.5"E
+	Degrees and decimal minutes, e.g. N30° 13.49760' , E30° 49.30788'
+	Degrees minutes seconds, e.g. N30° 13' 29.8" , E30° 49' 1.5"
+	Decimal degrees, e.g. 30.22496 , 30.821798
+
+Southern hemisphere latitudes are given with a *S*, e.g. S30°, or with a
+negative value, e.g. -30.22496. Similarly western longitudes are given with
+a *W*, e.g. W07°, or with a negative value, e.g. -7.34323.
+
+Please note that GPS coordinates of a dive site are linked to the Location
+name - so adding coordinates to dives that do not have a location
+description will cause unexpected behaviour (Subsurface will think that all
+of these dives have the same location and try to keep their GPS coordinates
+the same).
+
+*Divemaster*: The name of the dive master or dive guide for this dive can be
+entered here.
+Again, this field offers auto completion based on the list of dive masters in
+the current logbook.
+
+*Buddy*: In this field one can enter the name(s) of the buddy / buddies
+(separated by commas) who accompanied the user on the dive. Auto completion
+is offered based on the list of buddies in the current logbook.
+
+*Suit*: The type of diving suit used for the dive can be entered here.
+As with the other items, auto completion of the suit description is available.
+Some dry-suit users may choose to use this field to record what combination of
+suit and thermal protection undersuit was used.
+
+*Rating*: One can provide a subjective overall rating of the dive on a
+5-point scale by clicking the appropriate star on the rating scale.
+
+*Visibility*: Similarly, one can provide a rating of visibility during the
+dive on a
+5-point scale by clicking the appropriate star.
+
+*Tags*: Tags that describe the type of dive performed may
+be entered here (separated by commas). Examples of common tags are boat, drift,
+training, cave etc. _Subsurface_ has many built-in tags. Auto completion is once again offered.
+For instance, if +cav+ was typed, then the tags *cave* and *cavern* are
+shown for the user to choose from.
+
+*Notes*: Any additional information can be typed here.
+
+The *Save* and *Cancel* buttons are used to save all the information for
+tabs in the info panel and in the dive profile panel, so there's no need to
+use them until ALL other information has been added. Here is an example of a
+completed Dive Notes panel:
+
+image::images/CompletedDiveInfo_f20.jpg["FIGURE: A completed Dive Notes tab", align="center"]
+
+==== Equipment
+
+The Equipment tab allows the user to enter information about the type of
+cylinder and gas used, as well as the weights used for a dive. This is a
+highly interactive part of _Subsurface_ and the information on cylinders and
+gases (entered here) affects the behaviour of the dive profile (top
+right-hand panel).
+
+[[S_CylinderData]]
+*Cylinders*: The cylinder information is entered through a dialogue that looks
+like this:
+
+image::images/Gas_dialogue1_f20.jpg["FIGURE:Initial cylinder dialogue", align="center"]
+
+The + button at the top right allows the user to add more cylinders for this
+dive.  The dark dustbin icon on the left allows one to delete information
+for a particular cylinder. Note that it is not possible to delete a cylinder
+if it is used during the dive. One cylinder is implicitly used in the dive,
+even without a gas change event. Thus the first cylinder cannot be deleted
+until another cylinder is created.
+
+Start by selecting a cylinder type on the left-hand side of the table.  To
+select a cylinder, click in the *Type* box.  This brings up a button that
+can be used to display a dropdown list of cylinders:
+
+image::images/Gas_dialogue2_f20.jpg["FIGURE:The cylinder drop-down list button", align="center"]
+
+The drop-down list can be used to select the cylinder type used for the dive
+or the user may start typing in the box which shows the available options
+for the entered characters. The *Size* of the cylinder as well as its
+working pressure (*WorkPress*) will automatically be shown in the
+dialogue. If a cylinder is not shown in the dropdown list, type the name and
+description of that cylinder into the *Type* field.
+
+Next, indicate the starting pressure and the ending pressure of the gas used
+during the dive. The unit of pressure (metric/imperial) corresponds to the
+setting in the _Preferences_.
+
+Finally, type in the gas mixture used in the *O2%* field. If air was used, a
+value of 21% can be entered on this field, or it might be left blank. If
+nitrox or trimix were used, their percentages of oxygen and/or helium must
+be specified.  Any inappropriate fields should be left empty. After typing
+the information for the cylinder, press _ENTER_ on the keyboard or click
+outside the cell that contains the cursor. Information for any additional
+cylinders can be added by using the + button at the top right
+hand. Following is an example of a complete description for a dive made
+using two cylinders (air and EAN50):
+
+image::images/CylinderDataEntry3_f20.jpg["FIGURE: a completed cylinder dive information table", align="center"]
+
+*Weights*: Information about the weight system used during a dive can be entered
+using a dialogue very similar to that for the cylinder information. If the user
+clicks the + button on the top right of the weights dialogue, the table looks
+like this:
+
+image::images/WeightsDataEntry1_f20.jpg["FIGURE: The Weights dialogue", align="center"]
+
+If one then clicks on the *Type* field, a drop-down list becomes accessible
+through a down-arrow:
+
+image::images/WeightsDataEntry2_f20.jpg["FIGURE: Weights type drop-down list button", align="center"]
+
+The drop-down list can then be used to select the type of weight system or
+the user may start typing in the box which shows the available options for
+the entered characters. In the *Weight* field, the weight used during the
+dive must be typed. After typing the information for the weight system the
+user must either press _ENTER_ on the keyboard or click outside the cell
+that contains the cursor. It is possible to enter information for more than
+one weight system by adding an additional system using the + button on the
+top right hand. Weight systems can be deleted using the dustbin icon on the
+left hand. Here is an example of information for a dive with two types of
+weights: integrated and a weight belt:
+
+image::images/WeightsDataEntry3_f20.jpg["FIGURE: A completed weights information table", align="center"]
+
+There's NO need to click the _Save_ button before the dive profile has been
+completed.
+
+[[S_CreateProfile]]
+==== Creating a Dive Profile
+
+The *Dive Profile* (a graphical representation of the depth of the dive as a
+function of time) is indicated in the panel on the top right hand of the
+_Subsurface_ window. When a dive is manually added to a logbook,
+_Subsurface_ presents a default dive profile that needs to be modified to
+best represent the dive being described:
+
+image::images/DiveProfile1_f20.jpg["FIGURE: Initial dive profile", align="center"]
+
+_Modifying the dive profile_: When the cursor is moved around the dive
+profile, its position is indicated by two coloured lines (red and green) as
+shown below.  The depth and time that the cursor represents are indicated at
+the top of the black information box (@ and D). The units (metric/imperial)
+on the axes are determined by the *Preference* settings. The dive profile
+itself comprises several line segments demarcated by waypoints (white dots
+on the profile, as shown above). The default dive depth is 15 m.  If the
+dive depth was 20 m then the user needs to drag the appropriate waypoints
+downwards to represent 20 m. To add a waypoint, double-click on any line
+segment. To move an additional waypoint, drag it.  To remove this waypoint,
+right-click on it and choose "Remove this point" from the context menu. The
+user needs to drag the waypoints to represent an accurate time duration for
+the dive. Below is a dive profile that represents a dive to 20 m for 30 min,
+followed by a 5 minute safety stop at 5 m.
+
+image::images/DiveProfile2_f20.jpg["FIGURE: Edited dive profile", align="center"]
+
+_Specifying the gas composition:_ The gas composition used is clearly
+indicated along the line segments of the dive profile. This defaults to the
+first gas mixture specified in the *Equipment* tab, which was air in the
+case of the profile illustrated above. The gas mixtures of segments of the
+dive profile can be edited. This is done by right-clicking on the particular
+waypoint and selecting the appropriate gas from the context menu. Changing
+the gas for a waypoint affects the gas shown in the segment _to the left_ of
+that waypoint. Note that only the gases defined in the *Equipment* tab
+appear in the context menu.
+
+image::images/DiveProfile3_f20.jpg["FIGURE: Gas composition context menu", align="center"]
+
+Below is the profile of a dive to 25 m for 30 min and with a switch from air
+to EAN50 at the end of the duration at 20m. In this case the first cylinder
+in the *Equipment* tab contained air and the second cylinder contained
+EAN50.
+
+image::images/DiveProfile4_f20.jpg["FIGURE: Completed dive profile", align="center"]
+
+==== Saving the hand-entered dive information
+
+The information entered in the *Dive Notes* tab, the *Equipment* tab as well
+as the *Dive Profile* can now be saved in the user's logbook by using the
+two buttons on the top right hand of the Dive Notes tab. If the _Save_
+button is clicked, the dive data are saved in the current logbook. If the
+_Cancel_ button is clicked, the newly entered dive data are discarded. When
+exiting _Subsurface_, the user will be prompted once more to save the
+logbook with the new dive(s).
+
+[[S_ImportDiveComputer]]
+=== Importing new dive information from a Dive Computer
+
+==== Connecting and importing data from a dive computer.
+
+The use of dive computers allows the collection of a large amount of
+information about each dive, e.g. a detailed record of depth, duration,
+rates of ascent/descent and of gas partial pressures. _Subsurface_ can
+capture this information and present it as part of the dive information,
+using dive information from a wide range of dive computers. The latest list
+of supported dive computers can be found at:
+link:http://subsurface-divelog.org/documentation/supported-dive-computers/[
+Supported dive computers].
+
+[icon="images/icons/warning2.png"]
+[WARNING]
+Several dive computers consume more power when they are in their
+PC-Communication mode. **This could drain the dive computer's battery**. We
+therefore recommend that the user checks if the dive computer is charged
+when connected to the USB port of a PC. For example, several Suunto and
+Mares dive computers do not recharge through the USB connection. Users
+should refer to the dive computer's manual if they are unsure whether the
+dive computer recharges its batteries while connected to the USB port.
+
+To import dive information from a dive computer to a computer with
+_Subsurface_, it is necessary that the two pieces of equipment communicate
+with one another.  This involves setting up the communications port (or
+mount point) of the computer with _Subsurface_ that communicates with the
+dive computer. In order to set up this communication, one needs to find the
+appropriate information to instruct _Subsurface_ where and how to import the
+dive information.
+xref:_appendix_a_operating_system_specific_information_for_importing_dive_information_from_a_dive_computer[Appendix
+A] provides the technical information to help the user achieving this for
+different operating systems and
+xref:_appendix_b_dive_computer_specific_information_for_importing_dive_information[Appendix
+B] has dive computer specific information.
+
+After this, the dive computer can be hooked up to the user's PC, which can
+be achieved by following these steps:
+
+1. The interface cable should be connected to a free USB port (or the Infra-red
+	or Bluetooth connection set up as described later in this manual)
+
+2. The dive computer should be placed into PC Communication mode.
+	(Users should refer to the manual of their specific dive computer)
+
+In _Subsurface_, from the Main Menu, the user must select _Import -> Import
+From Dive Computer_.  Dialogue *A* in the figure below appears:
+
+
+image::images/ImportFromDC1_f20.jpg["FIGURE: Download dialogue 1", align="center"]
+
+Dive computers tend to keep a certain number of dives in their memory, even
+though these dives have already been imported to _Subsurface_. For that
+reason _Subsurface_ only imports dives that have not been uploaded
+before. This makes the download process faster on most dive computers and
+also saves battery power of the dive computer (at least for those not
+charging while connected via USB).  If, for some reason, the user wishes to
+import ALL dives from the dive computer, even though some may already be in
+the logbook, then check the check box labelled _Force download of all
+dives_.
+
+The dialogue has two drop-down lists, *Vendor* and *Dive Computer*. On the
+*vendor* drop-down list select the make of the computer, e.g.  Suunto,
+Oceanic, Uwatec, Mares. On the *Dive Computer* drop-down list, the model
+name of the dive computer must be selected, e.g. D4 (Suunto), Veo200
+(Oceanic), or Puck (Mares).
+
+The *Device or Mount Point* drop-down list contains the USB or Bluetooth
+port name that _Subsurface_ needs in order to communicate with the dive
+computer.  The appropriate port name must be selected. Consult
+xref:_appendix_a_operating_system_specific_information_for_importing_dive_information_from_a_dive_computer[Appendix
+A] and
+xref:_appendix_b_dive_computer_specific_information_for_importing_dive_information[Appendix
+B] for technical details on how to find the appropriate port information for
+a particular dive computer and, in some cases, how to do the correct
+settings to the operating system of the computer on which _Subsurface_ is
+running.
+
+ - If all the dives on the dive computer need to be downloaded, check the
+   checkbox _Force download of all dives_. Normally, _Subsurface_ only
+   downloads dives after the date-time of the last dive in the *Dive List*
+   panel. If one or more of your dives in _Subsurface_ have been accidentally
+   deleted or if there are older dives that still need to be downloaded from
+   the dive computer, this checkbox needs to be activated. Some dive computers
+   (e.g. Mares Puck) do not provide a contents list to _Subsurface_ before the
+   download in order to select only new dives.  Consequently, for these dive
+   computers, all dives are downloaded irrespective of the status of this check
+   box.
+
+ - If the checkbox _Always prefer downloaded dives_ has been checked and,
+   during download, dives with identical date-times exist on the dive computer
+   and on the _Subsurface_ *Dive List* panel, the record in the _Subsurface_
+   divelog will be overwritten by the record from the dive computer
+
+ -  Do *not* check the checkboxes labelled _Save libdivecomputer logfile_ and
+    _Save libdivecomputer dumpfile_. These are only used as diagnostic tools
+    when problems with downloads are experienced (see below).
+
+The _OK_ button must then be clicked. Dialogue *B* in the figure above
+appears.
+
+With communication established, one can see how the data are retrieved from
+the dive computer.  Depending on the make of the dive computer and/or number
+of recorded dives, this could take some time. The user should be
+patient. The _Download_ dialogue shows a progress bar at the bottom of the
+dialogue (for some dive computers the progress information could be
+inaccurate as we cannot determine how much downloadable data there is until
+all data have been downloaded). When the download of the dive information is
+complete, all the imported dives appear in the *Dive List*, sorted by date
+and time. Disconnect and switch off the dive computer to conserve its
+battery power.  If a particular dive is selected, the *Dive Profile* panel
+shows an informative graph of dive depth against time for that particular
+dive.
+
+
+If there is a problem in communicating with the dive computer, an error
+message will be shown, similar to this text: "Unable to open /dev/ttyUSB0
+Mares (Puck Pro)". Refer to the text in the box below.
+
+
+****
+*PROBLEMS WITH DATA DOWNLOAD FROM A DIVE COMPUTER?*
+[icon="images/icons/important.png"]
+[IMPORTANT]
+Check the following:
+
+Is the dive computer still in PC-communication or Upload mode?
+
+Is the battery of the dive computer fully charged? If not then the battery
+must be charged or replaced.
+
+Is the connecting cable faulty? Does the cable work perfectly using other
+software? Has it worked before, or is this the first time the cable is being
+used? Are the contacts on the dive computer and the cable clean?
+
+Consult
+xref:_appendix_a_operating_system_specific_information_for_importing_dive_information_from_a_dive_computer[Appendix
+A] and make sure that the correct Mount Point was specified (see above).
+
+On Unix-like operating systems, does the user have write permission to the
+USB port? If not, consult
+xref:_appendix_a_operating_system_specific_information_for_importing_dive_information_from_a_dive_computer[Appendix
+A]
+
+If the _Subsurface_ computer does not recognise the USB adaptor by showing
+an appropriate device name next to the Mount Point, then there is a
+possibility that the cable or USB adaptor is faulty. A faulty cable is the
+most common cause of communication failure between dive computer and
+_Subsurface_ computer. It is also possible that the _Subsurface_ computer
+cannot interpret the data. Perform a download for diagnostic purposes with
+the following two check boxes checked in the download dialogue discussed
+above:
+
+	Save libdivecomputer logfile
+	Save libdivecomputer dumpfile
+
+*Important*: These check boxes are only used when problems are encountered
+during the download process: under normal circumstances they should not be checked.
+When checking these boxes, the user is prompted to select a folder to
+save the information to. The default folder is the one in which the _Subsurface_
+dive log is kept.
+
+*Important:* _After downloading with the above checkboxes
+checked, no dives are added to the
+*Dive List* but two files are created in the folder selected above_:
+
+	subsurface.log
+	subsurface.bin
+
+These files should be send to the _Subsurface_ mail list:
+_subsurface@subsurface-divelog.org_ with a request for the files to be
+analysed. Provide the dive computer make and model as well as contextual
+information about the dives recorded on the dive computer.
+****
+
+[[S_DeviceNames]]
+==== Changing the name of a dive computer
+
+It may be necessary to distinguish between different dive computers used to
+upload dive logs to _Subsurface_. For instance if one's partner's dive
+computer is the same make and model as one's own and dive logs are uploaded
+from both dive computers to the same _Subsurface_ computer, then one would
+perhaps like to call one dc "Alice's Suunto D4" and the other one "Bob's
+Suunto D4". Alternatively, perhaps a technical diver dives with two or more
+dive computers of the same model, the logs of both (or all) being uploaded.
+In this case it might be prudent to call one of them "Suunto D4 (1)" and
+another one "Suunto D4 (2)". This is easily done in _Subsurface_.  On the
+*Main Menu*, select _Log -> Edit device names_. A dialog opens, indicating
+the current Model, ID and Nickname of the dive computers used for
+upload. Edit the Nickname field for the appropriate dive computer. After
+saving the Nickname, the dive logs show the nickname for that particular
+device instead of the model name, allowing easy identification of devices.
+
+[[S_EditDiveInfo]]
+==== Updating the dive information imported from the dive computer.
+
+The information from the dive computer is not complete and more details must
+be added in order to have a fuller record of the dives. To do this, the
+*Dive Notes* and the *Equipment* tabs on the top left hand of the
+_Subsurface_ window should be used.
+
+==== Dive Notes
+
+The date and time of the dive, gas mixture and (often) water temperature is
+shown as obtained from the dive computer, but the user needs to add
+additional information by hand in order to have a more complete dive
+record.  If the contents of this tab is changed or edited in any way, the
+message in a blue box at the top of the panel indicates that the dive is
+being edited. If one clicks on the *Dive Notes* tab, the following fields
+are visible:
+
+image::images/AddDive3_f20.jpg["FIGURE: The Dive Notes tab", align="center"]
+
+The *Time* field reflects the date and time of the dive. By clicking the
+date, a calendar is displayed from which one can choose the correct
+date. Press ESC to close the calendar.  The time values (hour and minutes)
+can also be edited directly by clicking on each of them in the text box and
+by overtyping the information displayed.
+
+*Air/water temperatures*: Air and water temperatures during the dive are shown
+in these fields to the right of the Start time. Many dive computers supply water
+temperature information and this field may therefore contain information obtained from the dive computer.
+If air temperature is not provided by the dive computer, the first temperature reading
+might be used for the air temperature. Generally this is close enough to the real air temperature as
+the change in the temperature sensor reading is quite slow to follow the changes in the environment.
+If editing is required, only a value is required, the units of temperature will be
+automatically supplied by
+_Subsurface_ (according to the _Preferences_, metric or imperial units will
+be used).
+
+*Location*: In this field one should type in text that describes the site
+where the dive was performed, e.g. "Tihany, Lake Balaton, Hungary".
+Auto completion of location names will
+make this easier if one frequently dives at the same sites.
+
+*Coordinates*: The geographic coordinates of the dive site should be entered
+here. These can come from three sources:
+
+The user can find the coordinates on the world map in the bottom right hand
+part of the Subsurface window. The map displays a green bar indicating "Move
+the map and double-click to set the dive location". Double-click at the
+appropriate place, the green bar disappears and the coordinates are stored.
+
+The user can obtain the coordinates from the _Subsurface_ Companion app if
+an Android device with GPS was used and if the coordinates of the dive site
+were stored using that device.  xref:S_Companion[Click here for more
+information]
+
+The coordinates can be entered by hand if they are known, using one of four
+formats with latitude followed by longitude:
+
+	ISO 6709 Annex D format e.g. 30°13'28.9"N 30°49'1.5"E
+	Degrees and decimal minutes, e.g. N30° 13.49760' , E30° 49.30788'
+	Degrees minutes seconds, e.g. N30° 13' 29.8" , E30° 49' 1.5"
+	Decimal degrees, e.g. 30.22496 , 30.821798
+
+Southern hemisphere latitudes are given with a *S*, e.g. S30°, or with a
+negative value, e.g. -30.22496. Similarly, western longitudes are given with
+a *W*, e.g. W07°, or with a negative value, e.g. -7.34323.
+
+Please note that GPS coordinates of a dive site are linked to the Location
+name - so adding coordinates to dives that do not have a location
+description will cause unexpected behaviour (Subsurface will think that all
+of these dives have the same location and try to keep their GPS coordinates
+the same).
+
+*Divemaster*: The name of the dive master or dive guide for this dive should be
+entered in this field
+which offers auto completion based on the list of dive masters in
+the current logbook.
+
+*Buddy*: In this field, one enters the name(s) of the buddy / buddies
+(separated with commas) who accompanied him/her on the
+dive. Auto completion based on the list of buddies in the current logbook is
+offered.
+
+*Suit*: Here the type of diving suit used for the dive can be entered.
+Auto completion of the suit description is available.
+Some dry-suit users may choose to use this field to record what combination of
+suit and thermal protection undersuit was used.
+
+*Rating*: One can provide a subjective overall rating of the dive on a
+5-point scale by clicking the appropriate star on the rating scale.
+
+*Visibility*: Similarly, one can provide a rating of visibility during the
+dive on a
+5-point scale by clicking the appropriate star.
+
+*Tags*: Tags that describe the type of dive performed can be entered
+here (separated by commas). Examples of common tags are boat, drift, training,
+cave, etc.
+_Subsurface_ has many built-in tags. If the user starts typing a tag, the
+program
+will list the tags that correspond to the typing. For instance, if the user
+typed
++cav+, then the tags *cave* and *cavern* are shown for the user to choose from.
+
+*Notes*: Any additional information for the dive can be entered here.
+
+The *Save* and *Cancel* buttons are used to save all the information for
+tabs in the info panel and in the dive profile panel, so there's no need to
+use them until ALL other information has been added. Here is an example of a
+completed Dive Notes panel:
+
+image::images/CompletedDiveInfo_f20.jpg["FIGURE: A completed Dive Notes tab", align="center"]
+
+==== Equipment
+
+The Equipment tab allows one to enter information about the type of cylinder
+and gas used as well as the weights used for the dive. The message in a blue
+box at the top of the panel:
+
+image::images/BlueEditBar_f20.jpg["FIGURE: Blue edit bar", align="center"]
+
+indicates that the dive is being edited. This is a highly interactive part
+of _Subsurface_ and the information on cylinders and gases (entered here)
+determines the behaviour of the dive profile (top right-hand panel).
+
+*Cylinders*: The cylinder information is entered through a dialogue that looks
+like this:
+
+image::images/DC_gas-dialogue1_f20.jpg["FIGURE: Initial cylinder dialogue", align="center"]
+
+In most cases _Subsurface_ obtains the gas used from the dive computer and
+automatically inserts the gas composition(% oxygen) in the table. The +
+button at the top right allows the user to add more cylinders for this
+dive. The dark dustbin icon on the left allows the deletion of information
+for a cylinder.  Note that it is not possible to delete a cylinder if it is
+used during the dive. A cylinder might be implicitly used in the dive, even
+without a gas change event.
+
+The user should start by selecting a cylinder type on the left-hand side of
+the table.  To select a cylinder, the *cylinder type* box should be
+clicked. This brings up a list button that can be used to display a dropdown
+list of cylinders:
+
+image::images/DC_gas-dialogue2_f20.jpg["FIGURE: The cylinder drop-down list button", align="center"]
+
+The drop-down list can then be used to select the cylinder type that was
+used for this dive or the user may start typing in the box which shows the
+available options for the entered characters. The *Size* of the cylinder as
+well as its working pressure (*WorkPress*) will automatically be shown in
+the dialogue.
+
+Next one must indicate the starting pressure and the ending pressure of the
+specified gas during the dive. The unit of pressure (metric/imperial)
+corresponds to the settings chosen in the _Preferences_.
+
+Finally, provide the gas mixture used. If air was used, the value of 21% can
+be entered or this field can be left blank. If nitrox or trimix were used,
+their percentages of oxygen and/or helium should be entered.  Any
+inappropriate fields should be left empty. After typing the information for
+the cylinder, either press _ENTER_ on the keyboard or click outside the cell
+that contains the cursor. Information for any additional cylinders can be
+added by using the + button at the top right hand. Following is an example
+of a complete description for a dive using two cylinders (air and EAN50):
+
+image::images/CylinderDataEntry3_f20.jpg["FIGURE: a completed cylinder dive information table", align="center"]
+
+*Weights*: Information about the weight system used can be entered
+using a dialogue very similar to that of the cylinder information. If one
+clicks
+the + button on the top right of the weights dialogue, the table looks like
+this:
+
+image::images/WeightsDataEntry1_f20.jpg["FIGURE:The Weights dialogue", align="center"]
+
+By clicking on the *Type* field, a drop-down list becomes accessible through
+a down-arrow:
+
+image::images/WeightsDataEntry2_f20.jpg["FIGURE:Weights type drop-down list button", align="center"]
+
+The drop-down list can then be used to select the type of weight system used
+during the dive or the user may start typing in the box which shows the
+available options for the entered characters.  In the *Weight* field, type
+in the amount of weight used during the dive. After specifying the weight
+system, the user can either press _ENTER_ on the keyboard or click outside
+the cell with the cursor.  It is possible to enter information for more than
+one weight system by adding an additional system using the + button on the
+top right hand. Weight systems can be deleted using the dustbin icon on the
+left hand. Here is an example of information for a dive with two types of
+weights: integrated as well as a weight belt:
+
+image::images/WeightsDataEntry3_f20.jpg["FIGURE: A completed weights information table", align="center"]
+
+==== Editing several selected dives simultaneously
+
+_METHOD 1_: After uploading dives from a dive computer, the dive profiles of
+the uploaded dives are shown in the *Dive profile* tab, as well as a few
+items of information in the *Dive Notes* tab (e.g. water temperature) and in
+the *Equipment* tab (e.g. gas pressures and gas composition). However the
+other fields remain empty.  It may be useful to simultaneously edit some of
+the fields in the *Dive Notes* and *Equipment* tabs.  For instance, it is
+possible that a diver performed several dives during a single day, using
+identical equipment while diving at the same dive site or with the same dive
+master and/or buddy or tags. Instead of completing the information for each
+of these dives separately, one can select all the dives for that day in the
+*Dive List* and insert the same information in the *Dive Notes* and
+*Equipment* fields that need identical information. This is achieved by
+editing the dive notes or the equipment for any one of the selected dives.
+
+The simultaneous editing only works with fields that do not already contain
+information.  This means that, if some fields have been edited for a
+particular dive among the selected dives, these are not changed while
+editing the dives simultaneously. Technically, the rule for editing several
+dives simultaneously is: if the data field being edited contains _exactly
+the same information_ for all the dives that have been selected, the new,
+edited information is substituted for all the selected dives, otherwise only
+the edited dive is changed, even though several dives have been selected in
+the *Dive List*. This greatly speeds up the completion of the dive log after
+several similar dives.
+
+[[S_CopyComponents]]
+_METHOD 2_:There is a different way of achieving the same goal. Select a
+dive with all the appropriate information typed into the *Dive Notes* and
+*Equipment* tabs. Then, from the main menu, select _Log -> Copy dive
+components_.  A box is presented with a selection of check boxes for most of
+the fields in the *Dive Notes* and *Equipment* tabs.  Select the fields to
+be copied from the currently selected dive, then select _OK_. Now, in the
+*Dive List*, select the dives into which this information is to be
+pasted. Then, from the main menu, select _Log -> Paste dive components_.
+All the selected dives now contain the data initially selected in the
+original source dive log.
+
+==== Adding Bookmarks to a dive
+
+Many divers wish to annotate their dives with text that indicate particular
+events during the dive, e.g. "Saw dolphins", or "Released surface
+buoy". This is easily done:
+
+Right-click at the appropriate point on the dive profile.  This brings up
+the dive profile context menu. Select _Add bookmark_. A red flag is placed
+on the dive profile at the point that was initially selected (see *A*
+below).
+
+ - Right-click on the red flag. This brings up the context menu (see *B*
+   below). Select _Edit name_.
+
+A text box is shown. Type the explanatory text for the bookmark (see *C*
+below). Select _OK_.  This saves the text associated with the bookmark.
+
+If one hovers using the mouse over the red bookmark, the appropriate text is
+shown at the bottom of the information box (see *D* below).
+
+image::images/Bookmarks.jpg["FIGURE: Bookmark dialog", align="center"]
+
+
+==== Saving the updated dive information
+
+The information entered in the *Dive Notes* tab and the *Equipment* tab can
+be saved by using the two buttons on the top right hand of the *Dive Notes*
+tab. If the _Save_ button is clicked, the dive data are saved. If the
+_Cancel_ button is clicked, then the newly entered dive data are deleted,
+although the dive profile obtained from the dive computer will be
+retained. When the user exits _Subsurface_ there is a final prompt to
+confirm that the new data should be saved.
+
+=== Importing dive information from other digital data sources or other data formats
+
+[[S_ImportingAlienDiveLogs]]
+
+If a user has been diving for some time, it is possible that several dives
+were logged using other dive log software. This information does not need
+retyping because these dive logs can probably be imported into
+_Subsurface_. _Subsurface_ will import dive logs from a range of other dive
+log software. While some software is supported natively, for others the user
+has to export the logbook(s) to an intermediate format so that they can then
+be imported by _Subsurface_.  Currently, _Subsurface_ supports importing CSV
+log files from several sources.  APD LogViewer, XP5, Sensus and Seabear
+files are preconfigured, but because the import is flexible, users can
+configure their own imports.  Manually kept log files (e.g. in spreadsheet)
+can also be imported by configuring the CSV import.  _Subsurface_ can also
+import UDDF and UDCF files used by some divelog software and some dive
+computers, like the Heinrichs & Weikamp DR5. Finally, for some divelog
+software like Mares Dive Organiser it is currently suggested to import the
+logbooks first into a webservice like _divelogs.de_ and then import them
+from there with _Subsurface_, as divelogs.de supports a few additional
+logbook formats that _Subsurface_ currently cannot parse.
+
+If the format of other software is supported natively on Subsurface, it
+should be sufficient to select either _Import->Import log files_ or
+_File->Open log file_. _Subsurface_ supports the data formats of many dive
+computers, including Suunto and Shearwater. When importing dives,
+_Subsurface_ tries to detect multiple records for the same dive and merges
+the information as best as it can. If there are no time zone issues (or
+other reasons that would cause the beginning time of the dives to be
+significantly different) _Subsurface_ will not create duplicate entries.
+
+==== Using the universal import dialogue
+[[Unified_import]]
+
+Importing dives from other software is performed through a universal
+interface that is activated by selecting _Import_ from the Main Menu, then
+clicking on _Import Log Files_. This brings up the dialogue *A* below.
+
+image::images/Import1_f20.jpg["FIGURE: Import dialogue: step 1", align="center"]
+
+Towards the bottom right is a dropdown selector with a default label of
+_Dive Log Files_ which gives access to the different types of direct imports
+available, as in dialogue *B*, above. Currently these are:
+
+ - XML-formatted dive logs (DivingLog 5.0, MacDive and several other dive log
+   systems)
+ - UDDF-formatted dive logs (e.g. Kenozoooid)
+ - UDCF-formatted dive logs
+ - Poseidon MkVI CCR logs
+ - JDiveLog
+ - Suunto Dive Manager (DM3 and DM4)
+ - CSV (text-based and spreadsheet-based) dive logs, including APD CCR logs
+
+Selecting the appropriate file in the file list of the dialogue opens the
+imported dive log in the _Subsurface_ *Dive List*. Some other formats, not
+accessible through the Import dialogue are also supported, as explained
+below.
+
+==== Importing dive logs from closed circuit rebreather (CCR) systems
+
+[icon="images/APD.jpg"]
+[NOTE]
+Closed system rebreathers use advanced technology to recirculate gas that
+has been breathed while doing two things to maintain a breathable oxygen
+concentration:
+a) remove carbon dioxide from the gas that has been exhaled
+regulate the oxygen concentration to remain within safe diving limits.
+Currently, within _Subsurface_, the Poseidon MkVI Discovery is the best
+supported CCR dive computer. The CCR interface of _Subsurface_ is currently
+experimental and under active development. In contrast to a conventional
+open circuit dive computer, a CCR system computer does not allow the
+download of a log containing multiple dives. Rather, each dive is stored
+independently. This means that _Subsurface_ cannot download a dive log
+directly from a CCR dive computer, but that it imports CCR dive logs in the
+same way that it imports dive log data from other databases.
+
+===== Import a CCR dive
+
+See the section dealing with xref:S_ImportingAlienDiveLogs[Importing dive
+information from other digital sources]. From the main menu of _Subsurface_,
+select _Import->Import log files_ to bring up the
+xref:Unified_import[universal import dialogue]. As explained in the previous
+section, the bottom right hand of the import dialogue contains a dropdown
+list of appropriate devices that currently includes an option for MkVI
+files. Having selected the appropriate CCR format and the directory where
+the original dive logs have been stored from the CCR dive computer, one can
+select a particular dive log file (in the case of the MkVI it is a file with
+a .txt extension). After selecting the appropriate dive log, activate the
+_Open_ button at the bottom right hand of the universal import dialogue.
+
+===== Displayed information for a  dive
+
+_Partial pressures of gases_: The graph of oxygen partial pressure shows the
+information from the oxygen sensors of the CCR equipment. In the case of the
+Poseidon MKVI, the mean value of the two oxygen sensors are shown. In the
+case of the APD equipment, the mean of the three oxygen sensors are
+shown. If one sensor shows a very different oxygen PO2 reading compared to
+the others, the divergent sensor is ignored. For CCR dives the graph for
+oxygen partial pressure should be fairly flat, reflecting the setpoint
+settings during the dive.  Partial pressures for nitrogen (and helium, if
+applicable) are shown in the usual way as for other dives.
+
+_Cylinder pressures_: CCR dive computers like the Poseidon MkVI record the
+pressures of the oxygen and diluent cylinders. The pressure of the oxygen
+cylinder is shown on the dive profile. In addition, start and end pressures
+for both oxygen and diluent cylinders are shown in the _Equipment Tab_.
+
+_Equipment-specific information_: Equipment-specific information gathered by
+_Subsurface_ is shown in the _Extra data_ tab. This may include setup
+information or metadata about the dive.
+
+More equipment-specific information for downloading CCR dive logs can be
+found in xref:S_PoseidonMkVI[Appendix B].
+
+==== Importing from Mares Dive Organiser V2.1
+
+Since Mares utilise proprietary Windows software not compatible with
+multi-platform applications, these dive logs cannot be directly imported
+into _Subsurface_. Mares dive logs need to be imported using a three-step
+process, using _www.divelogs.de_ as a mechanism to extract the dive log
+information.
+
+The dive log data from Mares Dive Organiser need to be exported to the user's
+desktop, using
+ a _.sdf_ file name extension. Refer to xref:Mares_Export[Appendix C] for more
+information.
+Data should then be imported into _www.divelogs.de_. One needs to create a user
+account in
+_www.divelogs.de_, log into that web site, then
+select _Import Logbook -> Dive Organiser_ from the menu on the left hand side.
+The instructions must be carefully followed to transfer the dive information
+(in _.sdf_ format) from the Dive Organiser database to _www.divelogs.de_.
+Finally,  import the dives
+from _divelogs.de_ to _Subsurface_, using the instructions below.
+
+
+[[S_ImportingDivelogsDe]]
+==== Importing dives from *divelogs.de*
+
+The import of dive information from _divelogs.de_ is simple, using a single
+dialogue box. The _Import->Import form Divelogs.de_ option should be
+selected from the Main Menu. This brings up a dialogue box (see figure on
+left [*A*] below). Enter a user-ID and password for _divelogs.de_ into the
+appropriate fields and then select the _Download_ button. Download from
+_divelogs.de_ starts immediately, displaying a progress bar in the dialogue
+box. At the end of the download, the success status is indicated (see figure
+on the right [*B*], below). The _Apply_ button should then be selected,
+after which the imported dives appear in the _Subsurface_ *Dive List* panel.
+
+image::images/Divelogs1.jpg["FIGURE:Download from Divelogs.de", align="center"]
+
+[[S_ImportingCSVData]]
+==== Importing data in CSV format
+
+A comma-separated file (.csv) can be used to import dive information either
+as dive profiles (as in the case of the APD Inspiration and Evolution closed
+circuit rebreathers) or as dive metadata (in case the user keeps dive data
+in a spreadsheet). For an introduction to CSV-formatted files see
+xref:S_CSV_Intro[A Diver's Introduction To CSV Files].
+
+[icon="images/icons/important.png"]
+[IMPORTANT]
+The CSV import has a couple of caveats. You should avoid some special
+characters like ampersand (&), less than (<), greater than (>) and double
+quotes ("), the latter if quoting text cells. The file should use UTF-8
+character set, if having non-ASCII characters. Also the size of the CSV file
+might cause problems. Importing 100 dives at a time (without dive profile)
+has worked previously, but larger files might exceed limits of the parser
+used. When having problems with CSV imports, try first with a smaller sample
+to make sure everything works.
+
+[[S_ImportingCSVDives]]
+===== Importing dives in CSV format from dive computers or other dive log software
+
+CSV files are normally organised into a single line that provides the
+headers (or _field names_) of the data columns, followed by the data, one
+record per line. CSV files can be opened with a normal text editor.  For
+information of how to export a spreadsheet in CSV format see
+xref:S_Appendix_D[APPENDIX D: Exporting a spreadsheet to CSV format].
+
+Before being able to import the data to _Subsurface_ one needs to know:
+
+Which character separates the different columns within a single line of
+data? This field separator should be either a comma (,) or a TAB character.
+This can be determined by opening the file with a text editor. If it is
+comma-delimited, then the comma characters between the values are clearly
+visible. If no commas are evident and the numbers are aligned in columns,
+the file is probably TAB-delimited (i.e. it uses a TAB as a field separator,
+as in the above example).
+
+Which data columns need to be imported into _Subsurface_? The Dive Time and
+Depth columns are always required. Open the file using a text editor and
+note the titles of the columns to be imported and their column positions.
+
+c. Is the numeric information (e.g. dive depth) in metric or in imperial unis?
+
+Armed with this information, importing the data into _Subsurface_ is
+straightforward. Select _Import->Import Log Files_ from the main menu. In
+the resulting file selection menu, select _CSV files_, after which a common
+configuration dialog appears for all the files with a CSV extension:
+
+image::images/Import_CSV1.jpg["FIGURE: CSV download dialogue", align="center"]
+
+There are pre-configured definitions for some dive computers, e.g. the APD
+rebreathers. If the user's dive computer is on this list, it should be
+selected using the dropdown box labeled _Pre-configured imports_.
+
+If the dive computer is not on the pre-configured list, the user must select
+the _Field Separator_ (TAB or comma) for the particular CSV file, using the
+appropriate dropdown list. For each data column used for import, the user
+must check the appropriate check box and indicate in which column these data
+are found.
+
+Finally _OK_ should be clicked and the dive(s) are imported and listed in
+the *Dive List* tab of _Subsurface_.
+
+
+[[S_ImportingManualCSV]]
+==== Importing dives from a manually kept CSV file or a spreadsheet
+
+[[S_CSV_Intro]]
+****
+*A Diver's Introduction To CSV Files*
+[icon="images/icons/important.png"]
+[IMPORTANT]
+
+CSV is an abbreviation for a data file format: _Comma-Separated
+Variables_. It is a file format allowing someone to view or edit the
+information using a text editor such as Notebook (Windows), gedit (Linux) or
+TextWrangler (OS/X). The two main advantages of the CSV format is that the
+data are easily editable as text without any proprietary software and
+ensuring all information is human-readable, not being obscured by the any
+custom or proprietary attributes that proprietary software insert into
+files.  Because of its simplicity the CSV format is used as an interchange
+format between many software packages, e.g. between spreadsheet,
+statistical, graphics, database and diving software. Within _Subsurface_,
+CSV files can also be used to import information from other sources such as
+spreadsheet-based dive logs and even from some dive computers.
+
+CSV files can be created or edited with a normal text editor. The most
+important attribute of a CSV file is the _field separator_, the character
+used to separate fields within a single line. The field separator is
+frequently a comma, a colon, a SPACE character or a TAB character. When
+exporting data from spreadsheet software, the field separator needs to be
+specified in order to create the CSV file. CSV files are normally organised
+into a single line that provides the headers (or _field names_) of the data
+columns, followed by the data, one record per line. Note that each field
+name may comprise more than one word separated by spaces; for instance _Dive
+site_, below. Here is an example of dive information for four dives using a
+comma as a field separator:
+
+	Dive site,Dive date,Time,Dive_duration, Dive_depth,Dive buddy
+	Illovo Beach,2012-11-23,10:45,46:15,18.4,John Smith
+	Key Largo,2012-11-24,09:12,34:15,20.4,Jason McDonald
+	Wismar Baltic,2012-12-01,10:13,35:27,15.4,Dieter Albrecht
+	Pulau Weh,2012-12-20,09:46,55:56,38.6,Karaeng Bontonompo
+
+In this format the data are not easily read by a human. Here is the same
+information in TAB-delimited format:
+
+	Dive site	Dive date	Time	Dive_duration	Dive_depth	Dive buddy
+	Illovo Beach	2012-11-23	10:45	46:15	18.4	John Smith
+	Key Largo	2012-11-24	09:12	34:15	20.4	Jason McDonald
+	Wismar Baltic	2012-12-01	10:13	35:27	15.4	Dieter Albrecht
+	Pulau Weh	2012-12-20	09:46	55:56	38.6	Karaeng Bontonompo
+
+It is clear why many people prefer the TAB-delimited format to the
+comma-delimited format. The disadvantage is that one cannot see the TAB
+characters. For instance, the space between _Dive_ and _date_ in the top
+line may be a SPACE character or a TAB character (in this case it is a SPACE
+character: the tabs are before and after _Dive date_). If the field names in
+the first line are long, the alignment with data in the other lines cannot
+be maintained. Here is a highly simplified and shortened TAB-delimited
+example of a CSV dive log from an APD closed-circuit rebreather (CCR) dive
+computer:
+
+	Dive Time (s)	Depth (m)	pO₂ - Setpoint (Bar) 	pO₂ - C1 Cell 1 (Bar)	Ambient temp. (Celsius)
+	0       0.0     0.70    0.81    13.1
+	0       1.2     0.70    0.71    13.1
+	0       0.0     0.70    0.71    13.1
+	0       1.2     0.70    0.71    13.2
+	0       1.2     0.70    0.71    13.1
+	10      1.6     0.70    0.72    12.7
+	20      1.6     0.70    0.71    12.6
+	30      1.7     0.70    0.71    12.6
+	40      1.8     0.70    0.68    12.5
+
+CSV files can therefore be used in many contexts for importing data into a
+_Subsurface_ dive log.
+
+An important aspect of the CSV format required by _Subsurface_ is the
+_Column Mapping_. In the example from different dive sites above, each line
+of data is organised as follows:
+
+	Column 1:	Dive site (location)
+	Column 2:	Dive date
+	Column 3:	Dive time
+	Column 4:	Dive duration
+	Column 5:	Maximum dive depth (m)
+	Column 6:	Name of dive buddy
+
+_Subsurface_ requires the column number of each of these data items. For
+these data the column specification may look like this:
+
+image::images/CSV_column_definition.jpg["FIGURE: CSV column definition", align="center"]
+
+Knowledge of a few basic things about he content of the CSV file allows a
+smooth import of the dives into _Subsurface_.
+
+****
+
+If one keeps dive logs in a spreadsheet, there is an option to import those
+dives, exported as a CSV file. See xref:S_Appendix_D[APPENDIX D: Exporting a
+spreadsheet to CSV format] for information of how to export a spreadsheet in
+CSV format.  When importing manually kept log files into _Subsurface_, the
+information needed is quite different from that accessible using a dive
+computer, as we are importing only summary data, not depth profile samples.
+
+When importing dives in CSV format (see above), one needs to know the
+internal format of the CSV data to import.
+
+Which character separates the different columns within a single line of
+data? A recommended field separator for the export is TAB, as commas might
+be part of the decimal data values themselves. Therefore the use of an
+appropriate field separator is very important. When exporting data from a
+spreadsheet it is likely to request the user to supply an appropriate field
+separator character.
+
+Which columns need to be imported into _Subsurface_? Currently there are not
+any mandatory input fields, but some, e.g. dive duration are crucial for the
+log file to make any sense. Possible options can be seen in the image below
+and one should include as many as possible of the fields available in the
+original log file.
+
+Units used for depth, weight and temperature. We consider depth to be either
+feet or meters, weight kilograms or pounds and temperature either Celsius or
+Fahrenheit. However, the users can select _Metric_ or _Imperial_ in the
+*Preferences* tab of _Subsurface_. No mixture of unit systems is allowed for
+the different fields.
+
+Importing manually kept CSV log files is quite straight forward, but there
+might be many fields and counting the field numbers is error
+prone. Therefore validation of the data to be imported is critical.
+
+To import the dives, select _Import->Import Log Files_ from the menu bar. If
+the CSV option in the dropdown list is selected and the file list includes
+file names ending with .CSV, one can select the _Manual dives_ tab that will
+bring up the following configuration dialog:
+
+image::images/Import_CSV2.jpg["FIGURE: Download dialog for Manual CSV logs", align="center"]
+
+Check the check boxes corresponding to the data in the original import
+file.  For each of the checked data items, a corresponding column number
+needs to be entered. For instance in the image above, the name of the dive
+site (i.e. location)  is located as the 11th item (or column) on each line
+of the CSV import file.  The input fields can be configured as appropriate,
+and when everything is done the _OK_ button should be selected to perform
+the import. New dives should appear in the *Dive List* area of _Subsurface_.
+
+
+[[S_Companion]]
+=== Importing GPS coordinates with the _Subsurface Companion App_ for mobile phones
+
+Using the *Subsurface Companion App* on an Android device with a GPS, the
+coordinates for the diving location can be automatically passed to the
+_Subsurface_ dive log. The Companion App stores the dive locations on a
+dedicated Internet-based file server. _Subsurface_, in turn, can collect the
+localities from the file server.
+
+To do this:
+
+==== Create a Companion App account
+
+Register on the http://api.hohndel.org/login/[_Subsurface companion web
+page_].  A confirmation email with instructions and a personal *DIVERID*
+will be sent, a long number that gives access to the file server and
+Companion App capabilities.
+
+Download the app from
+https://play.google.com/store/apps/details?id=org.subsurface[Google Play
+Store] or from
+http://f-droid.org/repository/browse/?fdfilter=subsurface&fdid=org.subsurface[F-Droid].
+
+==== Using the Subsurface companion app on a smartphone
+
+On first use the app has three options:
+
+_Create a new account._ Equivalent to registering in _Subsurface_ companion
+page using an Internet browser. One can request a *DIVERID* using this
+option, but this is supplied via email and followed up by interaction with
+the http://api.hohndel.org/login/[_Subsurface companion web page_] in order
+to activate the account.
+
+_Retrieve an account._ If users forgot their *DIVERID* they will receive an
+email to recover the number.
+
+_Use an existing account._ Users are prompted for their *DIVERID*. The app
+saves this *DIVERID* and does not ask for it again unless one uses the
+_Disconnect_ menu option (see below).
+
+[icon="images/icons/important.png"]
+[IMPORTANT]
+In the _Subsurface_ main program, the *DIVERID* should also be entered on
+the Default Preferences panel, obtained by selecting
+_File->Preferences->Defaults_ from the main menu in _Subsurface_ itself.
+This facilitates synchronisation between _Subsurface_ and the Companion App.
+
+===== Creating new dive locations
+
+Now one is ready to get a dive position and send it to the server. The
+Android display will look like the left hand image (*A*) below, but without
+any dives.
+
+Touch the "+" icon on the top right to add a new dive site, a menu will be
+showed with 3 options:
+
+Current: A prompt for a place name (or a request to activate the GPS if it
+is turned off) will be displayed, after which the current location is saved.
+
+Use Map: This option allows the user to fix a position by searching a world
+map. A world map is shown (see *B* below) on which one should indicate the
+desired position with a _long press_ on the touch sensitive screen (if the
+marked location is erroneous, simply indicate a new location)  and select
+the check symbol in the upper right. A dialog is shown allowing to enter the
+name of the dive location and the date-time of the dive (see *C* below). In
+order to import this dive location in _Subsurface_ it's advisable to set the
+time to agree with the time of that dive on the dive computer.
+
+image::images/Companion_5.jpg["FIGURE: Companion App, add location using map", align="center"]
+
+
+Import local GPX file: The android device searches for .gpx files and
+located archives will be shown. The selected .gpx file is opened and the
+stored locations shown. Now one needs to select the appropriate locations,
+then select the tab in the upper right, after which the locations will be
+sent to the web service and added to the list on the Android device.
+
+===== Dive lists of dive locations
+
+The main screen shows a list of dive locations, each with a name, date and
+time (see *A* below). Some locations may have an arrow-up icon over the
+selection box to the left indicating that they require upload to the
+server. One can select individual dive locations from the list. A selected
+location has a check mark in the selection box on the left. Group operations
+(such as _Delete_ or _Send_)  are performed on several locations that are
+selected.
+
+Dive locations in this list can be viewed in two ways: a list of locations
+or a map indicating the dive locations. The display mode (List or Map) is
+changed by selecting _Dives_ at the top left of the screen (see *A* below)
+and then selecting the display mode. The display mode can be changed either
+from the list of locations or from the map (see *B* below). If one selects a
+location (on the list or on the map), an editing panel opens (see *C* below)
+where the dive description or other details may be changed.
+
+image::images/Companion_4.jpg["FIGURE: Companion App, add location using map", align="center"]
+
+
+When one clicks on a dive (*not* selecting the check box), the name given to
+it, date/time and GPS coordinates will be shown, with two options at the top
+of the screen:
+
+- Edit (pencil): Change the text name or other characteristics of the dive
+  location.
+
+- Maps: Display a map showing the dive location.
+
+After editing and saving a dive location (see *C* above), one needs to
+upload it to the web service, as explained below.
+
+===== Uploading dive locations
+
+There are several ways to send locations to the server.  The easiest is by
+simply selecting the locations (See *A* below) and then touching the right
+arrow at the top right of the screen.
+
+[icon="images/icons/important.png"]
+[IMPORTANT]
+Users must be careful, as the trash icon on the right means exactly what it
+should; it deletes the selected dive location(s).
+
+image::images/Companion_1.jpg["FIGURE: Screen shots (A-B) of companion app", align="center"]
+
+
+After a dive trip using the Companion App, all dive locations are ready to
+be downloaded to a _Subsurface_ dive log (see below).
+
+
+===== Settings on the Companion app
+
+Selecting the _Settings_ menu option results in the right hand image above
+(*B*).
+
+===== Server and account
+
+- _Web-service URL._ This is predefined (http://api.hohndel.org/)
+
+_User ID._ The DIVERID obtained by registering as described above. The
+easiest way to obtain it is simply to copy and paste from the confirmation
+email but, of course, users can also type this information.
+
+===== Synchronisation
+
+_Synchronize on startup._ If selected, dive locations in the Android device
+and those on the web service synchronise each time the app is started.
+
+_Upload new dives._ If selected, each time the user adds a dive location it
+is automatically sent to the server.
+
+===== Background service
+Instead of entering a unique dive location, users can leave the service
+running in the background of their Android device, allowing the continuous
+collection of GPS locations.
+
+
+The settings below define the behaviour of the service:
+
+_Min duration._ In minutes. The app will try to get a location every X
+minutes until stopped by the user.
+
+- _Min distance._ In meters. Minimum distance between two locations.
+
+- _Name template._ The name the app will use when saving the locations.
+
+[icon="images/icons/info.jpg"]
+[TIP]
+_How does the background service work?_ Assuming the user sets 5 minutes and
+50 meters in the settings above, the app will start by recording a location
+at the current location, followed by another one at every 5 minutes *or*
+every time one moves 50m from previous location.  If subsequent locations
+are within a radius of 50 meters from the previous one, a new location is
+not saved. If the user is not moving, only one location is saved, but if the
+user is moving, a trace of the route is obtained by saving a location every
+50 meters.
+
+===== Other
+
+_Mailing List._ The mail box for _Subsurface_. Users can send an email to
+the Subsurface mailing list.
+
+- _Subsurface website._ A link to the URL of Subsurface web
+
+- _Version._ Displays the current version of the Companion App.
+
+===== Search
+
+Search the saved dive locations by name or by date and time.
+
+===== Start service
+
+Initiates the _background service_ following the previously defined
+settings.
+
+===== Disconnect
+
+This is a badly named option that disconnects the app from the server by
+resetting the user ID in the app, showing the first screen where an account
+can be created, retrieve the ID for an existing account or use the users own
+ID. The disconnect option is useful if a user's Android device was used to
+download the dive locations of another registered diver.
+
+===== Send all locations
+
+This option sends all locations stored in the Android device to the server.
+
+
+==== Downloading dive locations to the _Subsurface_ divelog
+
+Download dive(s) from a dive computer or enter them manually into
+_Subsurface_ before obtaining the GPS coordinates from the server. The
+download dialog can be reached via _Ctrl+G_ or from the _Subsurface_ Main
+Menu _Import -> Import GPS data from Subsurface Service_, resulting in the
+image on the left (*A*), below. On first use the DIVERID text box is
+blank. Provide a DIVERID, then select the _Download_ button to initiate the
+download process, after which the screen on the right (*B*) below appears:
+
+image::images/DownloadGPS.jpg["FIGURE: Downloading Companion app GPS data", align="center"]
+
+Note that the _Apply_ button is now active. By clicking on it, users can
+update the locations of the newly entered or uploaded dives in _Subsurface_
+which applies the coordinates and names entered on the app for all the new
+dives that match the date-times of the uploaded GPS localities. If one has
+entered the name of the dive location in _Subsurface_ before downloading the
+GPS coordinates, this name will take precedence over downloaded one.
+
+Since _Subsurface_ matches GPS locations from the Android device and dive
+information from the dive computer based on date-time data, automatic
+assignment of GPS data to dives is dependent on agreement of the date-time
+information between these two devices. Although _Subsurface_ has a wide
+range tolerance, it may be unable to identify the appropriate dive if there
+is a large difference between the time in the dive computer and that of the
+Android device, resulting in no updates.
+
+Similar date-times may not always be possible and there may be many reasons
+for this (e.g. time zones), or _Subsurface_ may be unable to decide which is
+the correct position for a dive (e.g. on repetitive dives while running
+_background service_ there may be several locations that would be included
+in the time range that fit not only the first dive, but one or more
+subsequent dives as well).  A workaround for this situation to manually edit
+the date-time of a dive in the _Subsurface_ Dive List *before* downloading
+the GPS data and then to change the date-time back again *after* downloading
+GPS data.
+
+[icon="images/icons/info.jpg"]
+[NOTE]
+TIPS:
+
+_Background service_, being a very powerful tool, may fill the location list
+with many unnecessary locations not corresponding to the exact dive point
+but reflecting the boat's route.  Currently these locations are difficult to
+delete from the server. In some situations it is therefore prudent to clean
+up the list on the Android device before sending the dive points to the web
+server by simply deleting the inappropriate locations. This might be
+necessary, for instance, if one wants to keep the location list clear to see
+dives in the web service map display (see above).
+
+It may also make sense to give informative names to the locations sent to
+the web server, or at least to use an informative name in the _Name
+Template_ setting while running the _background service_, especially on a
+dive trip with many dives and dive locations.
+
+[[S_LoadImage]]
+=== Adding photographs to dives
+
+Many (if not most) divers take a camera with them and take photographs
+during a dive. One would like to associate each photograph with a specific
+dive. _Subsurface_ allows one to load photos into a dive. Photos are
+superimposed on the dive profile, from where they can be viewed.
+
+==== Loading photos and getting synchronisation between dive computer and camera
+
+Left-lick on a dive or on a group of dives on the dive list. Then
+right-click on this dive or group of dives and choose the option _Load
+Images_:
+
+image::images/LoadImage1_f20.jpg["FIGURE: Load images option", align="center"]
+
+The system file browser appears. Select the folder and photographs that need
+to be loaded into _Subsurface_ and click the _Open_ button.
+
+image::images/LoadImage2_f20.jpg["FIGURE: Load images option", align="center"]
+
+This brings one to the time synchronisation dialog, shown below. The
+critical problem is that the time synchronisation is not perfect between the
+dive computer used during a dive, and the camera used during that same
+dive. These two devices often differ by several minutes. If _Subsurface_ can
+achieve synchronisation, then the exact times of photographs can be used to
+position photographs on the dive profile.
+
+_Subsurface_ achieves this synchronisation in two ways:
+
+*Manually*: If the user wrote down the exact camera time at the start of a dive, the
+difference in time between the two devices can be determined. Actually, as long as the device
+settings for time has not been changed in either device, one could write down the times of
+both devices after the dive or even at the end of the day. One can then manually set the time
+difference in the _Time shift_ dialog. Towards the top of the dialog is a time setting tool
+immediately under the heading _Shift times of image(s) by_, evident in figure *A* below.
+If the camera time is 7 minutes later than that of the dive computer, set the time setting
+tool to a value of 00:07.  Select either the _earlier_ or _later_ radio button.
+In the above example, the _earlier_ option is appropriate, since the photos need to be shifted
+7 minutes earlier (camera is 7 minutes ahead of dive computer). Ignore any "AM" or "PM" suffix
+in that tool. Click the _OK_ button and synchronisation is achieved.
+
+image::images/LoadImage3b_f20.jpg["FIGURE: Synchronisation dialog", align="center"]
+
+
+*By photograph*: There is a very slick way of achieving synchronisation. If one takes a
+photograph of the face of the dive computer showing the time, then _Subsurface_ can obtain
+the exact time the photograph was taken, using the metadata that the camera stores within
+each photo. In order to do this, use the bottom half of the Time shift_ dialog. If one uses
+the bottom part, the top part of the dialog is ignored. Click on
+the horizontal bar entitled "_Select image of divecomputer showing time_. This brings up
+a file browser with which one can select the photograph of the dive computer. Select the
+photograph using the file browser and click on _OK_. This photograph of the dive computer
+appears in the bottom panel of the _Shift times_ dialog. Now _Subsurface_ knows exactly
+when the photograph has been taken. Now set the date-time dialog to the left of the photo
+so that this tool reflects the date and time of the dive computer in the photo. When the
+date-time tool has been set, _Subsurface_ knows exactly what the time difference between
+camera and dive computer is, and synchronisation is achieved. There is a
+photograph with the face of the dive computer and with the date-time tool set to the
+date-time on image *B* above.
+
+If the timestamp of a photograph is long before or after the dive, it is not
+placed on the dive profile. If the timestamp of the photo is within 30
+minutes of the dive, it is shown.
+
+==== Viewing the photos
+
+In order to view the photos added to a dive, activate the _show-photos_
+button in the tool bar to the left of the dive profile:
+
+image::images/icons/ShowPhotos_f20.png["FIGURE:Show photos toolbar button", align="left"]
+
+After the images have been loaded, they appear in two places:
+
+ - the _Photos_ tab of the *Dive Notes* panel.
+ - as tiny icons (stubs) on the dive profile at the appropriate positions
+   reflecting the time each photograph was taken. See below:
+
+image::images/LoadImage4_f20.jpg["FIGURE: Photos on dive profile", align="center"]
+
+If one hovers with the mouse over any of the photo icons, then a thumbnail
+photo is shown of the appropriate photo. See the image below:
+
+image::images/LoadImage5_f20.jpg["FIGURE:Thumbnail photo on dive profile", align="center"]
+
+Clicking on the thumbnail brings up a full size photo overlaid on the
+_Subsurface_ window. This allows good viewing of the photographs that have
+been added (see the image below). Note that the thumbnail has a small
+dustbin icon in the bottom right hand corner (see image above). If one
+selects the dustbin, the image is removed from the dive. Therefore some care
+is required when clicking on a thumbnail. Images can also be deleted using
+the _Photos_ tab (see text below).
+
+image::images/LoadImage6_f20.jpg["FIGURE: Full-screen photo on dive profile", align="center"]
+
+==== The _Photos_ tab
+
+Photographs associated with a dive are shown as thumbnails in the _Photos_
+tab of the _Dive Notes_ panel. Photos taken in rapid succession during a
+dive (therefore sometimes with large overlap on the dive profile) can easily
+be accessed in the _Photos_ tab. This tab serves as a tool for individually
+accessing the photos of a dive, while the stubs on the dive profile give an
+indication of when during a dive a photo was taken. By single-clicking on a
+thumbnail in the _Photos_ panel, a photo is selected. By double-clicking a
+thumbnail, the full-sized image is shown, overlaying the _Subsurface_
+window. A photo can be deleted from the _Photos_ panel by selecting it
+(single-click) and then by pressing the _Del_ key on the keyboard. This
+removes the photo both from the _Photos_ tab as well as the dive profile.
+
+==== Photos on an external hard disk
+
+Most underwater photographers store their photos on an external drive. If
+such a drive can be mapped (almost always the case) the photos can be
+directly accessed by _Subsurface_. This facilitates the interaction between
+_Subsurface_ and an external repository of photos. When associating a dive
+profile with photos from an external drive, the normal procedure of
+selection and synchronisation (see text above) is used.  However, after the
+external drive has been disconnected, _Subsurface_ cannot access these
+photos any more.  If the display of photos is activated (using the toolbox
+to the left of the _Dive Profile_), the program only shows a small white dot
+where each photo should be on the dive profile.  In addition the _Photos_
+tab only shows the file names of the photos. This is normal behaviour.  If,
+later, the external drive with the photos is connected again, the photos can
+be seen in the normal way.
+
+
+=== Logging special types of dives
+
+==== Sidemount dives
+
+_Subsurface_ easily handles dives involving more than one
+cylinder. Sidemount dive logging involves three steps:
+
+*During the dive, recording cylinder switch events*. Since sidemount diving normally involves two
+cylinders with air or with the same gas mixture, _Subsurface_ distinguishes among these different
+cylinders. In contrast, most dive computers that allow gas switching only distinguish among different
+_gases_ used, not among different _cylinders_ used. This means that when sidemount dives are downloaded
+from these dive computers, the events of switching between cylinders with the same gas are not downloaded. This may mean
+that one may have to keep a written log of cylinder switch times using a slate, or (if the dive computer
+has this facility) marking each cylinder switch with a bookmark that can be retrieved later. Returning
+from a dive with the information about cylinder changes is the only tricky part of logging sidemount dives.
+*Within _Subsurface_ describe the cylinders used during the dive*. The diver needs to provide the
+specifications of the different cylinders, using the *Equipment* tab of the *Dive Info Panel* (see
+image below where two 12 litre cylinder were used).
+*Indicate cylinder change events on the _Subsurface_ dive profile*. Once the dive log has been imported
+from a dive computer into _Subsurface_, the cylinder switch events need to be indicated on the dive profile.
+Cylinder changes are recorded by right-clicking at the appropriate point on the dive profile and then
+selecting _Add gas change_. A list of the appropriate cylinders is shown with the
+currently used cylinder greyed out. In the image below Tank 1 is greyed out, leaving only Tank 2
+to be selected. Select the appropriate cylinder. The cylinder change is then indicated on the dive
+profile with a cylinder symbol. If the *Tank Bar* is activated using the toolbar to the left of the
+profile, then the cylinder change is also indicated on the Tank Bar (see image below). After all
+the cylinder change events have been recorded on the dive profile, the correct cylinder pressures
+for both cylinders are shown on the dive profile, as inthe image below.
+
+image::images/sidemount1.jpg["FIGURE: Sidemount profile", align="center"]
+
+== Obtaining more information about dives entered into the logbook
+
+=== The *Dive Info* tab (for individual dives)
+
+The Dive Info tab gives some summary information about a particular dive
+that has been selected in the *Dive List*. Useful information here includes
+the surface interval before the dive, the maximum and mean depths of the
+dive, the gas volume consumed, the surface air consumption (SAC) and the
+number of oxygen toxicity units (OTU) incurred.
+
+[icon="images/icons/info.jpg"]
+[NOTE]
+Gas consumption and SAC calculations: _Subsurface_ calculates SAC and Gas
+consumption taking in account gas incompressibility, particularly at tank
+pressures above 200 bar, making them more accurate.  Users should refer to
+xref:SAC_CALCULATION[Appendix D] for more information.
+
+=== The *Extra Data* tab (usually for individual dives)
+
+When using a dive computer, it often reports several data items that cannot
+easily be presented in a standardised way because the nature of the
+information differs from one dive computer to another. These data often
+comprise setup information, metadata about a dive, battery levels, no fly
+times, or gradient factors used during the dive. When possible, this
+information is presented in the *Extra Data* tab. Below is an image showing
+extra data for a dive using a Poseidon rebreather.
+
+image::images/ExtraDataTab_f20.jpg["FIGURE: Extra Data tab", align="center"]
+
+=== The *Stats* tab (for groups of dives)
+
+The Stats tab gives summary statistics for more than one dive, assuming that
+more than one dive has been selected in the *Dive List* using the standard
+Ctrl-click or Shift-click of the mouse. If only one dive has been selected,
+figures pertaining to only that dive are given. This tab shows the number of
+dives selected, the total amount of dive time in these dives, as well as the
+minimum, maximum and mean for the dive duration, water temperature and
+surface air consumption (SAC). It also shows the depth of the shallowest and
+deepest dives of those selected.
+
+[[S_DiveProfile]]
+=== The *Dive Profile*
+
+image::images/Profile2.jpg["Typical dive profile", align="center"]
+
+Of all the panels in _Subsurface_, the Dive Profile contains the most
+detailed information about each dive. The Dive Profile has a *button bar* on
+the left hand side that allows control over several display options. The
+functions of these buttons are described below. The main item in the Dive
+Profile is the graph of dive depth as a function of time. In addition to the
+obvious information of the depth it also shows the ascent and descent rates
+compared to the recommended speed of going up or down in the water
+column. This information is given using different colours:
+|====================
+|*Colour*|*Descent speed (m/min)*|*Ascent speed (m/min)*
+|Red|> 30|> 18
+|Orange|18 - 30|9 - 18
+|Yellow|9 - 18|4 - 9
+|Light green|1.5 - 9|1.5 - 4
+|Dark green|< 1.5|< 1.5
+|=====================
+
+The profile also includes depth readings for the peaks and troughs in the
+graph.  Thus, users should see the depth of the deepest point and other
+peaks. Mean depth is marked with a horizontal red line.
+
+[icon="images/icons/scale.jpg"]
+[NOTE]
+In some cases the dive profile does not fill the whole area of the *Dive
+Profile* panel. Clicking the *Scale* button in the toolbar on the left of
+the dive profile frequently increases the size of the dive profile to fill
+the area of the panel efficiently.
+
+*Water temperature* is displayed with its own blue line with temperature values
+placed adjacent to significant changes.
+
+The dive profile can include graphs of the *partial pressures* of O2, N2,
+and He during the dive (see figure above) as well as a calculated and dive
+computer reported deco ceilings (only visible for deep, long, or repetitive
+dives). Partial pressures of oxygen are indicated in green, those of
+nitrogen in black, and those of helium in dark red. These partial pressure
+graphs are shown below the profile data.
+
+[icon="images/icons/O2.jpg"]
+[NOTE]
+Clicking this button allows display of the partial pressure of *oxygen*
+during the dive. This is depicted below the dive depth and water temperature
+graphs.
+
+[icon="images/icons/N2.jpg"]
+[NOTE]
+Clicking this button allows display of the partial pressure of *nitrogen*
+during the dive.
+
+[icon="images/icons/He.jpg"]
+[NOTE]
+Clicking this button allows display of the partial pressure of *helium*
+during the dive.  This is only of importance to divers using Trimix,
+Helitrox or similar breathing gasses.
+
+The *air consumption* graph displays the tank pressure and its change during
+the dive. The air consumption takes depth into account so that even when
+manually entering the start and end pressures the graph is not a straight
+line.  Similarly to the depth graph the slope of the tank pressure gives the
+user information about the momentary SAC rate (Surface Air Consumption) when
+using an air integrated dive computer.  Here the colour coding is not
+relative to some absolute values but relative to the average normalised air
+consumption during the dive. So areas that are red or orange indicate times
+of increased normalized air consumption while dark green reflects times when
+the diver was using less gas than average.
+
+[icon="images/icons/Heartbutton.png"]
+[NOTE]
+Clicking on the heart rate button will allow the display of heart rate
+information during the dive if the dive computer was attached to a heart
+rate sensor.
+
+It is possible to *zoom* into the profile graph. This is done either by using
+the scroll wheel / scroll gesture of your mouse or trackpad. By default
+_Subsurface_ always shows a profile area large enough for at least 30 minutes
+and 30m
+ (100ft) – this way short or shallow dives are intuitively recognizable;
+something
+that free divers clearly won’t care about.
+
+image::images/MeasuringBar.png["FIGURE: Measuring Bar", align="center"]
+
+[icon="images/icons/ruler.jpg"]
+[NOTE]
+Measurements of *depth or time differences* can be achieved by using the
+*ruler button* on the left of the dive profile panel.  The measurement is
+done by dragging the red dots to the two points on the dive profile that the
+user wishes to measure. Information is then given in the horizontal white
+area underneath the two red dots.
+
+[icon="images/icons/ShowPhotos.png"]
+[NOTE]
+Photographs that have been added to a dive can be shown on the profile by
+selecting the *Show-photo* button. The position of a photo on the profile
+indicates the exact time when this photo was taken. If this button is not
+active, the photos are hidden.
+
+
+The profile can also include the dive computer reported *ceiling* (more
+precisely, the deepest deco stop that the dive computer calculated for each
+particular moment in time) as a red overlay on the dive profile. Ascent
+ceilings arise when a direct ascent to the surface increases the risk of a
+diver suffering from decompression sickness (DCS) and it is necessary to
+either ascend slower or to perform decompression stop(s) before ascending to
+the surface. Not all dive computers record this information and make it
+available for download; for example all of the Suunto dive computers fail to
+make this very useful data available to divelog software. _Subsurface_ also
+calculates ceilings independently, shown as a green overlay on the dive
+profile.  Because of the differences in algorithms used and amount of data
+available (and other factors taken into consideration at the time of the
+calculation) it is unlikely that ceilings from dive computers and from
+_Subsurface_ are the same, even if the same algorithm and _gradient factors_
+(see below) are used.  It is also quite common that _Subsurface_ calculates
+a ceiling for non-decompression dives when the dive computer stayed in
+non-deco mode during the whole dive (represented by the [green]#dark green#
+section in the profile at the beginning of this section). This is caused by
+the fact that _Subsurface’s_ calculations describe the deco obligation at
+each moment during a dive, while dive computers usually take the upcoming
+ascent into account. During the ascent some excess nitrogen (and possibly
+helium) are already breathed off so even though the diver technically
+encountered a ceiling at depth, the dive still does not require an explicit
+deco stop. This feature allows dive computers to offer longer non-stop
+bottom times.
+
+[icon="images/icons/cceiling.jpg"]
+[NOTE]
+If the dive computer itself calculates a ceiling and makes it available to
+_Subsurface_ during upload of dives, this can be shown as a red area by
+checking *Dive computer reported ceiling* button on the Profile Panel.
+
+[icon="images/icons/ceiling1.jpg"]
+[NOTE]
+If the *Calculated ceiling* button on the Profile Panel is clicked, then a
+ceiling, calculated by _Subsurface_, is shown in green if it exists for a
+particular dive (*A* in figure below). This setting can be modified in two
+ways:
+
+[icon="images/icons/ceiling2.jpg"]
+[NOTE]
+If, in addition, the *show all tissues* button on the Profile Panel is
+clicked, the ceiling is shown for the tissue compartments following the
+Bühlmann model (*B* in figure below).
+
+[icon="images/icons/ceiling3.jpg"]
+[NOTE]
+If, in addition, the *3m increments* button on the Profile Panel is clicked,
+then the ceiling is indicated in 3 m increments (*C* in figure below).
+
+image::images/Ceilings2.jpg["Figure: Ceiling with 3m resolution", align="center"]
+
+[icon="images/icons/ShowCylindersButton.jpg"]
+[NOTE]
+By selecting this icon, the different cylinders used during a dive can be
+represented as a coloured bar at the bottom of the *Dive Profile*. In
+general oxygen is represented by a green bar, nitrogen with a yellow bar and
+helium with a red bar. The image below shows a dive which first uses a
+trimix cylinder (red and green), followed by a switch to a nitrox cylinder
+(yellow and green) after 23 minutes. Cylinders with air are shown as a light
+blue bar.
+
+image::images/ShowCylinders_f20.jpg["Figure: Cylinder use graph", align="center"]
+
+
+[icon="images/tissues.jpg"]
+
+[NOTE]
+Display inert gas tissue pressures relative to ambient inert gas pressure
+(horizontal grey line).  Tissue pressures are calculated using the Bühlmann
+ZH-L16 algorithm and are displayed as lines ranging from green (faster
+tissues) to blue (slower tissues).  The black line, graphed above the
+ambient pressure, is the maximum allowable tissue supersaturation (pressure
+limit) derived from the gradient factors specified in the *Preferences*. For
+divers involved in planned decompression diving, efficient rates of
+offgasing are obtained with tissue pressures between the ambient inert gas
+pressure (grey line) and the pressure limit (black line). This display is a
+representation of the tissue pressures during the whole dive. In contast,
+the xref:S_gas_pressure_graph[Gas Pressure Graph] in the *Information Box*
+on the *Dive Profile* is an instantaneous reflection of tissue pressures at
+the moment in time reflected by the position of the cursor on the dive
+profile.
+
+image::images/tissuesGraph.jpg["Figure: Inert gas tissue pressure graph", align="center"]
+
+Gradient Factor settings strongly affect the calculated ceilings and their
+depths.  For more information about Gradient factors, see the section on
+xref:S_GradientFactors[Gradient Factor Preference settings]. The currently
+used gradient factors (e.g. GF 35/75) are shown above the depth profile if
+the appropriate toolbar buttons are activated.  *N.B.:* The indicated
+gradient factors are NOT the gradient factors in use by the dive computer,
+but those used by _Subsurface_ to calculate deco obligations during the
+dive. For more information external to this manual see:
+
+ ** http://www.tek-dive.com/portal/upload/M-Values.pdf[Understanding M-values by Erik Baker, _Immersed_ Vol. 3, No. 3.]
+
+ ** link:http://www.rebreatherworld.com/general-and-new-to-rebreather-articles/5037-gradient-factors-for-dummies.html[Gradient factors for dummies, by Kevin Watts]
+
+
+=== The Dive Profile context menu
+
+The context menu for the Dive Profile is accessed by right-clicking while
+the mouse cursor is over the Dive Profile panel. The menu allows the
+creation of Bookmarks or Gas Change Event markers or manual CCR set-point
+changes other than the ones that might have been imported from a Dive
+Computer. Markers are placed against the depth profile line and with the
+time of the event set by where the mouse cursor was when the right mouse
+button was initially clicked to bring up the menu. Gas Change events involve
+a selection of which gas is being switched to, the list of choices being
+based on the available gases defined in the Equipment Tab. Set-point change
+events open a dialog allowing to choose the next set-point value. As in the
+planner, a set-point value of zero indicates the diver is breathing from an
+open circuit system while any non-zero value indicates the use of a closed
+circuit rebreather (CCR).  By right-clicking while over an existing marker a
+menu appears, adding options to allow deletion of the marker or to allow all
+markers of that type to be hidden. Hidden events can be restored to view by
+selecting Unhide all events from the context menu.
+
+=== The *Information Box*
+
+The Information box displays a large range of information pertaining to the
+dive profile. Normally the Information Box is located to the top left of the
+*Dive Profile* panel. If the mouse points outside of the *Dive Profile*
+panel, then only the top line of the Information Box is visible (see
+left-hand part of figure (*A*) below). The Information Box can be moved
+around in the *Dive Profile* panel by click-dragging it with the mouse so
+that it is not obstructing important detail. The position of the Information
+Box is saved and used again during subsequent dive analyses.
+
+image::images/InfoBox2.jpg["Figure: Information Box", align="center"]
+
+The moment the mouse points inside the *Dive Profile* panel, the information
+box expands and shows many data items. In this situation, the data reflect
+the time point along the dive profile indicated by the mouse cursor (see
+right-hand part of figure (*B*) above where the Information Box reflects the
+situation at the position of the cursor [arrow] in that image). Therefore,
+moving the cursor in the horizontal direction allows the Information Box to
+show information for any point along the dive profile.  In this mode, the
+Information Box gives extensive statistics about depth, gas and ceiling
+characteristics of the particular dive. These include: Time period into the
+dive (indicated by a @), depth, cylinder pressure (P), temperature,
+ascent/descent rate, surface air consumption (SAC), oxygen partial pressure,
+maximum operating depth, equivalent air depth (EAD), equivalent narcotic
+depth (END), equivalent air density depth (EADD), decompression requirements
+at that instant in time (Deco), time to surface (TTS), the calculated
+ceiling, as well as the calculated ceiling for several Bühlmann tissue
+compartments.
+
+The user has control over the display of several statistics, represented as
+four buttons on the left of the profile panel. These are:
+
+[icon="images/icons/MOD.jpg"]
+[NOTE]
+Clicking this button causes the Information Box to display the *Maximum
+Operating Depth (MOD)* of the dive, given the gas mixture used. MOD is
+dependent on the oxygen concentration in the breathing gas.  For air (21%
+oxygen) it is around 57 m. Below the MOD there is a markedly increased risk
+of exposure to the dangers associated with oxygen toxicity.
+
+[icon="images/icons/NDL.jpg"]
+[NOTE]
+Clicking this button causes the Information Box to display the *No-deco
+Limit (NDL)* or the *Total Time to Surface (TTS)*. NDL is the time duration
+that a diver can continue with a dive, given the present depth, that does
+not require decompression (that is, before an ascent ceiling appears). Once
+one has exceeded the NDL and decompression is required (that is, there is an
+ascent ceiling above the diver, then TTS gives the number of minutes
+required before the diver can surface. TTS includes ascent time as well as
+decompression time.
+
+[icon="images/icons/SAC.jpg"]
+[NOTE]
+Clicking this button causes the Information Box to display the *Surface Air
+Consumption (SAC)*.  SAC is an indication of the surface-normalised
+respiration rate of a diver. The value of SAC is less than the real
+respiration rate because a diver at 10m uses breathing gas at a rate roughly
+double that of the equivalent rate at the surface. SAC gives an indication
+of breathing gas consumption rate independent of the depth of the dive so
+that the respiratory rates of different dives can be compared. The units for
+SAC is litres/min or cub ft/min.
+
+[icon="images/icons/EAD.jpg"]
+[NOTE]
+Clicking this button displays the *Equivalent Air Depth (EAD)* for nitrox
+dives as well as the *Equivalent Narcotic Depth (END)* for trimix
+dives. These are numbers of importance to divers who use breathing gases
+other than air. Their values are dependent on the composition of the
+breathing gas.  The EAD is the depth of a hypothetical air dive that has the
+same partial pressure of nitrogen as the current depth of the nitrox dive at
+hand. A nitrox dive leads to the same decompression obligation as an air
+dive to the depth equalling the EAD. The END is the depth of a hypothetical
+air dive that has the same sum of partial pressures of the narcotic gases
+nitrogen and oxygen as the current trimix dive. A trimix diver can expect
+the same narcotic effect as a diver breathing air diving at a depth
+equalling the END.
+
+Figure (*B*) above shows an information box with a nearly complete set of
+data.
+
+[[S_gas_pressure_graph]]
+==== The Gas Pressure Bar Graph
+
+On the left of the *Information Box* is a vertical bar graph indicating the
+pressures of the nitrogen (and other inert gases, e.g. helium, if
+applicable) that the diver was inhaling _at a particular instant during the
+dive_, indicated by the position of the cursor on the *Dive Profile*. The
+drawing on the left below indicates the meaning of the different parts of
+the Gas Pressure Bar Graph.
+
+image::images/GasPressureBarGraph.jpg["FIGURE:Gas Pressure bar Graph", align="center"]
+
+The light green area indicates the total gas, with the top margin of the
+light green area indicating the total gas pressure inhaled by the diver and
+measured from the bottom of the graph to the top of the light green
+area. This pressure has a _relative_ value in the graph and does not
+indicate absolute pressure.
+
+The horizontal black line underneath the light green margin indicates the
+equilibrium pressure of the inert gases inhaled by the diver, usually
+nitrogen. In the case of trimix, it is the pressures of nitrogen and helium
+combined. In this example, the user is diving with EAN32, so the inert gas
+pressure is 68% of the distance from the bottom of the graph to the total
+gas pressure value.
+
+The dark green area at the bottom of the graph represents the pressures of
+inert gas in each of the 16 tissue compartments, following the Bühlmann
+algorithm, the fast tissues being on the left hand side.
+
+The top black horizontal line indicates the gradient factor that applies to
+the depth of the diver at the particular point on the *Dive Profile*. The
+appropriate gradient factor is an interpolation between the FGLow and GFHigh
+values specified in the Graph tab of the *Preferences Panel* of
+*Subsurface*.
+
+The bottom margin of the red area in the graph indicates the Bühlman-derived
+M-value, that is the pressure value of inert gases at which bubble formation
+is expected to be severe, resulting in decompression sickness.
+
+These five values are indicated on the left in the graph above. The way the
+Gas Pressure Bar Graph changes during a dive is indicated on the right hand
+side of the above figure for a diver using EAN32.
+
+Graph *A* indicates the situation at the start of a dive with diver at the
+surface. The pressures in all the tissue compartments are still at the
+equilibrium pressure because no diving has taken place.
+
+Graph *B* indicates the situation after a descent to 30 meters. Few of the
+tissue compartments have had time to respond to the descent, their gas
+pressures being far below the equilibrium gas pressure.
+
+Graph *C* represents the pressures after 30 minutes at 30 m. The fast
+compartments have attained equilibrium (i.e. they have reached the hight of
+the black line indicating the equilibrium pressure). The slower compartments
+(towards the right) have not reached equilibrium and are in the process of
+slowly increasing in pressure.
+
+Graph *D* shows the pressures after ascent to a depth of 4.5 meters. Since,
+during ascent, the total inhaled gas pressure has decreased strongly from 4
+bar to 1.45 bar, the pressures in the different tissue compartments now
+exceed that of the total gas pressure and approaches the gradient factor
+value (i.e.  the top black horizontal line). Further ascent will result in
+exceeding the gradient factor value (GFHigh), endangering the diver.
+
+Graph *E* indicates the situation after remaining at 4.5 meters for 10
+minutes. The fast compartments have decreased in pressure. As expected, the
+pressures in the slow compartments have not changed much.  The pressures in
+the fast compartments do not approach the GFHigh value any more and the
+diver is safer than in the situation indicated in graph *D*.
+
+
+
+== Organising the logbook (Manipulating groups of dives)
+
+=== The Dive List context menu
+
+Many actions within _Subsurface_ are dependent on a context menu used mostly
+to manipulate groups of dives. The context menu is found by selecting a dive
+or a group of dives and then right-clicking.
+
+image::images/ContextMenu.jpg["Figure: Context Menu", align="center"]
+
+The context menu is used in many manipulations described below.
+
+==== Customising the information showed in the *Dive List* panel
+
+image::images/DiveListOptions.jpg["Example: Dive list info options", align="center"]
+
+The default information in the *Dive List* includes, for each dive,
+Dive_number, Date, Rating, Dive_depth, Dive_duration and Dive_location. This
+information can be controlled and changed by right-clicking on the header
+bar of the *Dive List*. For instance, a right-click on the 'Date' header
+brings up a list of items that can be shown in the dive list (see
+above). Select an item to be shown in the *Dive List* or to be deleted from
+the dive list, and the list is immediately updated accordingly. Preferences
+for information shown in the *Dive List* is saved and used when _Subsurface_
+is re-opened.
+
+==== Selecting dives from a particular dive site
+
+Many divers have long dive lists and it may be difficult to locate all the
+dives at a particular site.  By pressing _Ctl-F_ on the keyboard, a text box
+is opened at the top left hand of the *Dive List*.  Type the name of a dive
+site in this text box and the *Dive List* is immediately filtered to show
+only the dives for that site.
+
+[[S_Renumber]]
+=== Renumbering the dives
+
+Dives are normally numbered incrementally from non-recent dives (low
+sequence numbers) to recent dives (having the highest sequence numbers). The
+numbering of the dives is not always consistent. For instance, when
+non-recent dives are added to the dive list the numbering does not
+automatically follow on because of the dives that are more recent in
+date/time than the newly-added dive with an older date/time. Therefore, one
+may sometimes need to renumber the dives.  This is performed by selecting
+(from the Main Menu) _Log -> Renumber_. Users are given a choice with
+respect to the lowest sequence number to be used.  Completing this operation
+results in new sequence numbers (based on date/time)  for the dives in the
+*Dive List* panel.
+
+[[S_Group]]
+=== Grouping dives into trips and manipulating trips
+
+For regular divers, the dive list can rapidly become very long. _Subsurface_
+can group dives into _trips_. It performs this by grouping dives that have
+date/times that are not separated in time by more than two days, thus
+creating a single heading for each diving trip represented in the dive
+log. Below is an ungrouped dive list (*A*, on the left) as well as the
+corresponding grouped dive list comprising five dive trips (*B*, on the
+right):
+
+image::images/Group2.jpg["Figure: Grouping dives", align="center"]
+
+Grouping into trips allows a rapid way of accessing individual dives without
+having to scan a long lists of dives. In order to group the dives in a dive
+list, (from the Main Menu) users must select _Log -> Autogroup_. The *Dive
+List* panel now shows only the titles for the trips.
+
+==== Editing the title and associated information for a particular trip
+
+Normally, in the dive list, minimal information is included in the trip
+title.  More information about a trip can be added by selecting its trip
+title from the *Dive List*. This shows a *Trip Notes* tab in the *Dive
+Notes* panel. Here users can add or edit information about the date/time,
+the trip location and any other general comments about the trip as a whole
+(e.g. the dive company that was dived with, the general weather and surface
+conditions during the trip, etc.).  After entering this information, users
+should select *Save* from the buttons at the top right of the *Trip Notes*
+tab. The trip title in the *Dive List* panel should now reflect some of the
+edited information.
+
+==== Viewing the dives during a particular trip
+
+Once the dives have been grouped into trips, users can expand one or more
+trips by clicking the arrow-head on the left of each trip title. This
+expands the selected trip, revealing the individual dives performed during
+the trip.
+
+==== Collapsing or expanding dive information for different trips
+
+If a user right-clicks after selecting a particular trip in the dive list,
+the resulting context menu allows several possibilities to expand or
+collapse dives within trips. This includes expanding all trips, collapsing
+all trips and collapsing all trips except the selected one.
+
+==== Merging dives from more than one trip into a single trip
+
+By right-clicking on a selected trip title in the *Dive List* panel, a
+context menu shows up that allows the merging of trips by either merging of
+the selected trip with the trip below or with the trip above.
+
+==== Splitting a single trip into more than one trip
+
+If a trip includes five dives, the user can split this trip into two trips
+(trip 1: top 3 dives; trip 2: bottom 2 dives) by selecting and
+right-clicking the top three dives. The resulting context menu allows the
+user to create a new trip by choosing the option *Create new trip
+above*. The top three dives are then grouped into a separate trip. The
+figures below shows the selection and context menu on the left (A) and the
+completed action on the right (B):
+
+image::images/SplitDive3a.jpg["FIGURE: Split a trip into 2 trips", align="center"]
+
+=== Manipulating single dives
+
+==== Delete a dive from the dive log
+
+Dives can be permanently deleted from the dive log by selecting and
+right-clicking them to bring up the context menu, and then selecting *Delete
+dive(s)*. Typically this would apply to a case where a user wishes to delete
+workshop calibration dives of the dive computer or dives of extremely short
+duration.
+
+==== Unlink a dive from a trip
+
+Users can unlink dives from the trip to which they belong. In order to do
+this, select and right-click the relevant dives to bring up the context
+menu. Then select the option *Remove dive(s)  from trip*. The dive(s) now
+appear immediately above the trip to which they belonged.
+
+==== Add a dive to the trip immediately above
+
+Selected dives can be moved from the trip to which they belong and placed
+within the trip immediately above the currently active trip. To do this,
+select and right-click the dive(s) to bring up the context menu, and then
+select *Add dive(s) to trip immediately above*.
+
+==== Shift the start time of dive(s)
+
+Sometimes it is necessary to adjust the start time of a dive. This may apply
+to situations where dives are performed in different time zones or when the
+dive computer has an erroneous time. In order to do this, user must select
+and right-click the dive(s) to be adjusted. This action brings up the
+context menu on which the *Shift times* option should be selected. User must
+then specify the time (in hours and minutes) by which the dives should be
+adjusted and click on the option indicating whether the time adjustment
+should be forwards or backwards.
+
+==== Merge dives into a single dive
+
+Sometimes a dive is briefly interrupted, e.g. if a diver returns to the
+surface for a few minutes, resulting in two or more dives being recorded by
+the dive computer and appearing as different dives in the *Dive List*
+panel. Users can merge these dives onto a single dive by selecting the
+appropriate dives, right-clicking them to bring up the context menu and then
+selecting *Merge selected dives*. It may be necessary to edit the dive
+information in the *Dive Notes* panel to reflect events or conditions that
+apply to the merged dive. The figure below shows the depth profile of two
+such dives that were merged:
+
+image::images/MergedDive.png["Example: Merged dive", align="center"]
+
+[[S_Filter]]
+=== Filtering the dive list
+
+The dives in the *Dive List* panel can be filtered, that is, one can select
+only some of the dives based on their attributes, e.g. dive tags, dive site,
+dive master, buddy or protective clothing. For instance, filtering allows
+one to list the deep dives at a particular dive site, or otherwise the cave
+dives with a particular buddy.
+
+To open the filter, select _Log -> Filter divelist_ from the main menu. This
+opens the _Filter Panel_ at the top of the _Subsurface_ window. Three icons
+are located at the top right hand of the filter panel. The _Filter Panel_
+can be reset (i.e. all current filters cleared) by selecting the *+*. The
+_Filter Panel_ may also be minimised by selecting the middle icon. When
+minimised, only these three icons are shown.  The panel can be maximised by
+clicking the icon that minimised the panel. The filter may also be reset and
+closed by selecting the button with the flag.  An example of the _Filter
+Panel_ is shown in the figure below.
+
+
+image::images/Filterpanel.jpg["Figure: Filter panel", align="center"]
+
+
+Four filter criteria may be used to filter the dive list: dive tags, person
+(buddy / dive master), dive site and dive suit, each of which is represented
+by a check list with check boxes. Above each check list is a second-level
+filter tool, allowing the listing of only some of the attributes within that
+check list. For instance, typing "_ca_" in the filter textbox above the tags
+check list results in the tags check list being reduced to "_cave_" and
+"_cavern_". Filtering of the check list enables the rapid finding of search
+terms for filtering the dive list.
+
+To activate filtering of the dive list, the check box of at least one item
+in one of the four check lists needs to be checked. The dive list is then
+shortened to include only the dives that pertain to the selection criteria
+specified in the check lists.  The four check lists work as a filter with
+_AND_ operators, Subsurface filters therefore for _cave_ as a tag AND _Joe
+Smith_ as a buddy; but the filters within a category are inclusive -
+filtering for _cave_ and _boat_ shows those dives that have either one or
+both of these tags.
+
+[[S_ExportLog]]
+== Exporting the dive log or parts of the dive log
+
+The export function can be reached by selecting _File -> Export_, which
+brings up the Export dialog. This dialog always gives two options: save ALL
+dives, or save only the dives selected in *Dive List* panel of
+_Subsurface_. Click the appropriate radio button (see images below).
+
+image::images/Export.jpg["Figure: Export dialog", align="center"]
+
+A dive log or part of it can be saved in three formats:
+
+* _Subsurface XML_ format. This is the native format used by _Subsurface_.
+
+Universal Dive Data Format (_UDDF_). Refer to _http://uddf.org_ for more
+information.  UDDF is a generic format that enables communication among many
+dive computers and computer programs.
+
+_Divelogs.de_, an Internet-based dive log repository. In order to upload to
+_Divelogs.de_, one needs a user-ID as well as a password for
+_Divelogs.de_. Log into _http://en.divelogs.de_ and subscribe to this
+service in order to upload dive log data from _Subsurface_.
+
+_CSV_ format, that includes the most critical information of the dive
+profile. Included information of a dive is: dive number, date, time,
+duration, depth, temperature and pressure.
+
+_Worldmap_ format, an HTML file with a world map upon which each dive and
+some information about it are indicated. This map is not editable.
+
+_HTML_ format, in which the dive(s) are stored in HTML files, readable with
+an Internet browser. Most modern web browsers are supported, but JavaScript
+must be enabled. This generated HTML file is not intended to be edited by
+the users.  The HTML dive log contains most of the information and also
+contains a search option to search the dive log. HTML export is specified on
+the second tab of the Export dialog (image *B* above).
+
+* _General Settings_, under the HTML tab, provides the following options:
+
+** Subsurface Numbers: if this option is checked, the dive(s) are exported with the
+numbers associated with them in Subsurface, Otherwise the dive(s) will be numbered
+starting from 1.
+** Export Yearly Statistics: if this option is checked, a yearly statistics table will
+be attached with the HTML exports.
+** Export List only: a list of dives will only be exported and the detailed dive
+information will not be available.
+
+Under _Style Options_ some style-related options are available like font
+size and theme.
+
+Export to other formats can be achieved through third party facilities, for
+instance _www.divelogs.de_.
+
+[[S_Cloud_access]]
+== Keeping a _Subsurface_ dive log in the Cloud
+
+For each diver, dive log information is highly important. Not only is it a
+record of diving activities for one's own pleasure, but it is important
+information required for admission to further training courses or
+(sometimes) even diving sites. The security of the dive log is therefore
+critical. In order to have a dive log that is resistant to failure of a home
+computer hard drive, loss or theft of equipment, the Cloud is an obvious
+solution. This also has the added benefit that one can access one's dive log
+from anywhere in the world without having to carry it with oneself. For this
+reason, facilities such as _divelogs.de_ and _Diving Log_ offer facilities
+to store dive log information on the Internet. Although _Subsurface_ does
+not offer integrated Cloud storage of dive logs, it is simple to achieve
+this using several of the existing facilities on the Internet.
+
+For instance http://www.dropbox.com/[_Dropbox_] offers a free application
+that allows files on the Dropbox servers to be seen as a local folder on
+one's desktop computer.
+
+image::images/Cloud.jpg["FIGURE: Dropbox folder", align="center"]
+
+The _Dropbox_ program creates a copy of the _Dropbox_ Internet Cloud content
+on one's desktop computer. When the computer is connected to the Internet,
+the Internet content is automatically updated. Therefore both the _Open_ and
+_Save_ of dive logs are done using the local copy of the dive log in the
+local _Dropbox_ folder, so there's no need for a direct internet
+connection. If the local copy is modified, e.g. by adding a dive, the remote
+copy in the _Dropbox_ server in the Cloud will be automatically updated
+whenever Internet access is available.
+
+In this way a dive log in one's _Dropbox_ folder can be accessed seamlessly
+from the Internet and can be accessed from any place with Internet
+access. Currently there are no costs involved for this service. Dropbox
+(Windows, Mac and Linux) can be installed by accessing the
+http://www.dropbox.com/install[_Install Page on the Dropbox website_]
+Alternatively one can use _Dropbox_ as a mechanism to backup one's dive
+log. To Store a dive log in the Cloud, select _File->Save as_ from the
+_Subsurface_ main menu, navigate to the _Dropbox_ folder and select the
+_Save_ button. To access the dive log in the Cloud, select _File->Open
+Logbook_ from the _Subsurface_ main menu and navigate to the dive log file
+in the _Dropbox_ folder and select the _Open_ button.
+
+Several paid services exist on the Internet (e.g. Google, Amazon) where the
+same process could be used for the Cloud-based storage of dive logs.
+
+
+[[S_PrintDivelog]]
+== Printing a dive log
+
+_Subsurface_ provides a simple interface to print a whole dive log or only a
+few selected dives, including dive profiles and other contextual
+information.
+
+Before printing, two decisions are required:
+
+Should the whole dive log be printed or only part of it? If only part of the
+dive log is required, then the user must select the required dives from the
+*Dive List* panel.
+What gas partial pressure information is required on the dive profile? Users
+should select the appropriate toggle-buttons on the button bar to the left
+of the Dive Profile panel.
+
+Now the print options should be selected to match the user's needs. To do
+this, user should select _File->Print_ from the Main menu. The following
+dialogue appears (see the image on the left [A], below).
+
+image::images/PrintDiveLog.jpg["FIGURE: Print dialogue", align="center"]
+
+Under _Print type_ users need to select one of three options:
+
+- Print the complete Dive List: to do this, _Table Print_ should be selected.
+Print the selected dives (dive profiles and all other information) at 6
+dives per printed page: to do this, users should select _6 dives per page_.
+Print the selected dives (dive profiles and all other information) at 2
+dives per printed page: to do this, users should select _2 dives per page_.
+Print the selected dives (dive profiles and all other information) at 1 dive
+per printed page: to do this, users should select _1 dive per page_.
+
+Under _Print options_ users need to select:
+
+Printing only the dives that have been selected from the dive list prior to
+activating the print dialogue, achieved by checking the box _Print only
+selected dives_.
+- Printing in colour, achieved by checking the box with _Print in colour_.
+
+The _Ordering_ affects the layout of the page (or part of it) for each
+dive.  The dive profile could be printed at the top of each dive, with the
+textual information underneath, or it could be printed with the textual
+information at the top with the dive profile underneath. Users should select
+the appropriate option in the print dialogue. See the image below which has
+a layout with text below the dive profile.
+
+Users can _Preview_ the printed page by selecting the _Preview_ button on
+the dialogue. After preview, changes to the options in the print dialogue
+can be made, resulting in a layout that fits personal taste.
+
+Next, select the _Print_ button in the dialogue. This activates the regular
+print dialogue used by the user operating system (image [*B*] in the middle,
+above), allowing them to choose a printer and to set its properties (image
+[*C*] on the right, above).  It is important to set the print resolution of
+the printer to an appropriate value by changing the printer
+properties. Finally, one can print the dives. Below is a (rather small)
+example of the output for one particular page.
+
+image::images/Printpreview.jpg["FIGURE: Print preview page", align="center"]
+
+
+[[S_Preferences]]
+== Setting user _Preferences_ for _Subsurface_
+
+There are several settings within _Subsurface_ that the user can
+specify. These are found when selecting _File->Preferences_. The settings
+are performed in five groups: *Defaults*, *Units*, *Graph*, *Language* and
+*Network*. All five sections operate on the same principles: the user must
+specify the settings that are to be changed, then these changes are saved
+using the *Apply* button. After applying all the new settings users can then
+leave the settings panel by selecting *OK*.
+
+=== Defaults
+
+There are several settings in the *Defaults* panel:
+
+image::images/Pref1.jpg["FIGURE: Preferences defaults page", align="center"]
+
+  ** *Lists and tables*: Here one can specify the font type and font size of the
+*Dive Table* panel. By decreasing the font size of the *Dive Table*, users can see more dives on a screen.
+
+  ** *Dives*: For the _Default Dive File_ one need to specify the directory and
+file name of one's
+electronic dive log book. This is a file with filename extension .xml. When
+launched, _Subsurface_ will automatically load the specified dive log book.
+
+  ** *Display invalid*:  Dives can be marked as invalid (when a user wishes to hide
+dives that he/she don't consider valid dives, e.g. pool dives, but still want to
+keep them in the dive log). This controls whether those dives are displayed in
+the dive list.
+
+  ** *Default cylinder*: Here users can specify the default cylinder listed in
+the *Equipment* tab of the *Dive Notes* panel.
+
+  ** *Animations*: Some actions in showing the dive profile are performed using
+animations. For instance, the axis values for depth and time change from dive to
+dive. When viewing a different dive, these changes in axis characteristics do not
+happen instantaneously, but are animated. The _Speed_ of animations can be controlled
+by setting this slider
+with faster animation speed to the left, with a 0 value representing no animation
+at all.
+
+ ** *Subsurface web service*: When one subscribes to the <<S_Companion,Subsurface web service>>, a very
+long and hard-to-remember userID is issued. This is the place to save that userID. By
+checking the option _Save User ID locally?_, one ensures that a local copy of that userID
+is saved.
+
+ ** *Clear all settings*: As indicated in the button below this heading, all settings are
+cleared and set to default values.
+
+=== Units
+image::images/Pref2.jpg["FIGURE: Preferences Units page", align="center"]
+
+Here user can choose between metric and imperial units of depth, pressure,
+volume, temperature and mass. By selecting the Metric or Imperial radio
+button at the top, users can specify that all units are in the chosen
+measurement system.  Alternatively, if one selects the *Personalise* radio
+button, units can be selected independently, with some units in the metric
+system and others in imperial.
+
+=== Graph
+image::images/Pref3.jpg["FIGURE: Preferences Graph page", align="center"]
+
+[[S_GradientFactors]]
+This panel allows two type of selections:
+
+*Show*: Here users can specify the amount of information shown as part of
+the dive profile:
+** Thresholds: _Subsurface_ can display the nitrogen, oxygen and the helium partial pressures during
+the dive. These are enabled using the toolbar on the left hand side of the *Dive Profile*
+panel. For each of these graphs users can specify a threshold value on the right-hand side of the
+Preferences panel. If any of the graphs go above this threshold level, the graph is
+highlighted in red, indicating that the threshold has been exceeded.
+
+** _Draw dive computer reported ceiling red_: This checkbox allows exactly what it says.
+Not all dive computers report ceiling values. If the dive computer does report it, it may differ
+from the ceilings calculated by _Subsurface_. This is because of the different algorithms and gradient factors available for calculating ceilings, as well as the dynamic way that a
+dive computer can calculate ceilings during a dive.
+
+** _Show unused cylinders in Equipment Tab_: This checkbox allows display of information about unused cylinders when viewing the *Equipment Tab*. Conversely, if this box is not checked, and any cylinders entered using the *Equipment Tab* are not used (e.g. there was no gas switch to such a cylinder), then these cylinders are omitted from that list.
+
+** _Show average depth_: Activating this checkbox causes _Subsurface_ to draw a red line across
+the dive profile, indicating the mean depth of the dive.
+
+* *Misc*:
+
+** Gradient Factors:* Here users can set the _gradient factors_ used while diving. GF_Low is
+the gradient factor at depth and GF_High is used just below the surface.
+At intermediate depths gradient factors between GF_Low and GF_High are used.
+Gradient factors add conservatism to the nitrogen exposure during a dive, in a
+similar way that many dive computers have a conservatism setting. The lower
+the value of a gradient factor, the more conservative the calculations are with
+respect to nitrogen loading and the deeper the ascent ceilings are. Gradient
+factors of 20/60 are considered conservative and values of 60/90 are considered
+harsh. Checking *GFLow at max depth* box causes GF_Low to be used at the
+deepest depth of a dive. If this box is not checked, GF_Low is applied at
+all depths deeper than the first deco stop. For more information see:
+
+ ** http://www.tek-dive.com/portal/upload/M-Values.pdf[Understanding M-values by Erik Baker, _Immersed_ Vol. 3, No. 3.]
+
+ ** link:http://www.rebreatherworld.com/general-and-new-to-rebreather-articles/5037-gradient-factors-for-dummies.html[Gradient factors for dummies, by Kevin Watts]
+
+=== Language
+Choose a language that _Subsurface_ will use.
+
+image::images/Pref4.jpg["FIGURE: Preferences Language page", align="center"]
+
+A checkbox allows one to use the _System Default_ language which in most
+cases will be the correct setting; with this _Subsurface_ simply runs in the
+same language / country settings as the underlying OS. If this is for some
+reason undesirable users can uncheck this checkbox and pick a language /
+country combination from the list of included localizations. The _Filter_
+text box allows one to list similar languages. For instance there are
+several system variants of English or French. This particular preference
+requires a restart of _Subsurface_ to take effect.
+
+=== Network
+This panel facilitates communication between _Subsurface_ and data sources
+on the Internet.
+
+image::images/Pref5.jpg["FIGURE: Preferences Network page", align="center"]
+
+This is important, for instance, when _Subsurface_ needs to communicate with
+Internet services such as the <<S_Companion,_Subsurface Companion app_>> or
+data export/import from _Divelogs.de_. These Internet requirements are
+determined by one's type of connection to the Internet and by the Internet
+Service Provider (ISP) used.  One's ISP should provide the appropriate
+information.  If a proxy server is used for Internet access, the appropriate
+information needs to be provided here. The type of proxy needs to be
+selected from the dropdown list.  after which the IP address of the host and
+the appropriate port number should be provided. If the proxy server uses
+authentication, the appropriate userID and password also needs to be
+provided so that _Subsurface_ can automatically pass through the proxy
+server to access the Internet.
+
+[[S_DivePlanner]]
+== The _Subsurface_ dive planner
+Dive planning is an advanced feature of _Subsurface_, accessible by
+selecting _Log -> Plan Dive_ from the main menu. It allows calculation of
+nitrogen load during a dive by using the Bühlmann ZH-L16 algorithm with the
+addition of gradient factors as implemented by Erik Baker.
+
+****
+[icon="images/icons/warning2.png"]
+[WARNING]
+
+The _Subsurface_ dive planner IS CURRENTLY EXPERIMENTAL and assumes the user
+is already familiar with the _Subsurface_ user interface. It is explicitly
+used under the following conditions:
+
+The user is conversant with dive planning and has the necessary training to
+perform dive planning.
+- The user plans dives within his/her certification limits.
+Dive planning makes large assumptions about the characteristics of the
+_average person_ and cannot compensate for individual physiology or health
+or personal history or life style characteristics.
+- The safety of a dive plan depends heavily on the way in which the planner is
+  used.
+- The user is familiar with the user interface of _Subsurface_.
+A user who is not absolutely sure about any of the above requirements should
+not use this feature.
+****
+
+=== The _Subsurface_ dive planner screen
+
+Like the _Subsurface_ dive log, the planner screen is divided into several
+sections (see image below). The *setup* parameters for a dive are entered
+into the several sections on the left hand side of the screen.  The setup is
+divided into several sections: Available Gases, Rates, Planning, Gas Options
+and Dive Notes.
+
+At the top right hand is a green *design panel* upon which the profile of
+the dive can be manipulated directly by dragging and clicking as explained
+below. This feature makes the _Subsurface_ dive planner unique in ease of
+use.
+
+At the bottom right is a text panel with a heading of _Dive Plan
+Details_. This is where the details of the dive plan are provided in a way
+that can easily be copied to other software. This is also where any warning
+messages about the dive plan are printed.
+
+image::images/PlannerWindow1.jpg["FIGURE: Dive planner startup window", align="center"]
+
+
+=== Initiating dive planning
+
+The dive planner comprises two parts: *constructing a dive plan* and
+*evaluating* that dive plan. To perform dive planning, perform these steps:
+
+Clear the existing dive log by creating a new planning log. This is achieved
+by selecting _File -> New logbook_ from the main menu. This way, dive plans
+are kept separate from the existing dive log of completed dives.
+
+In the top left-hand area of the screen, ensure that the constant dive
+parameters are appropriate. These are: Start date and time of the dive,
+Atmospheric Pressure and Altitude above sea level of the dive site. The
+atmospheric pressure can also be entered as an altitude in metres, assuming
+an atmospheric pressure of 1.013 bar.
+
+In the table labelled _Available Gases_, add the information of the
+cylinders to be used as well as the gas composition within that
+cylinder. This is done in a similar way as for <<S_CylinderData,providing
+cylinder data for dive logs>>. Choose the cylinder type by double clicking
+the cylinder type and using the dropdown list, then specify the work
+pressure of this cylinder. By leaving the oxygen concentration (O2%) filed
+empty, the dive gas is assumed to be air. Otherwise enter the oxygen and/or
+helium concentration in the boxes provided in this dialogue. Add additional
+cylinders by using the "+" icon to the top righthand of the dialogue.
+
+The dialogue indicating _Dive Planner Points_ is usually not used at this
+stage of the dive planning.
+
+=== Managing nitrogen, oxygen and gas consumption
+
+The planning is performed in three stages:
+
+*a) Nitrogen management*: This is performed by specifying the rates for descent and ascent,
+as well as the gradient factors (GFLow and GFHigh) under the headings _Rates_ and _Planning_
+to the bottom left of the planning screen. Initially, the GFHigh and GFLow values in the _Preferences_
+panel of _Subsurface_ is used. If these are changed within the planner (see _Gas Options_ within
+the planner), the new values are
+used without changing the original specifications in the _Preferences_. Gradient Factor settings strongly affect the calculated ceilings and their depths.
+A very low GFLow value brings about decompression stops early on during the dive.
+ ** For more information about Gradient factors, see the section on xref:S_GradientFactors[Gradient Factor Preference settings].
+For more information external to this manual see:
+
+ *** link:http://www.tek-dive.com/portal/upload/M-Values.pdf[Understanding M-values by Erik Baker, _Immersed_ Vol. 3, No. 3.]
+ *** link:http://www.rebreatherworld.com/general-and-new-to-rebreather-articles/5037-gradient-factors-for-dummies.html[Gradient factors for dummies, by Kevin Watts]
+ *** link:http://www.amazon.com/Deco-Divers-Decompression-Theory-Physiology/dp/1905492073/ref=sr_1_1?s=books&ie=UTF8&qid=1403932320&sr=1-1&keywords=deco+for+divers[_Deco for Divers_, by Mark Powell (2008). Aquapress] Southend-on-Sea, UK. ISBN 10: 1-905492-07-3.
+An excellent non-technical review.
+
+ ** The ascent rate is critical for nitrogen off-gassing at the end of the dive and is specified
+for several depth ranges, utilising the average (or mean) depth as a yardstick. The mean depth
+of the dive plan is indicated on the dive profile in the green panel of the dive planner. Ascent rates
+at deeper levels are often in the range of 8-12 m/min, while ascent rates near the surface are
+often in the range of 4-9 m/min. The descent rate is also specified. If the option _Drop to first depth_
+is activated, then the descent phase of the planned dive will be at the maximal descent rate specified
+in the _Rates_ section of the dive setup.
+
+
+*b) Oxygen management*: In the *Gas Options* part of the dive specification, the maximum partial
+pressure for oxygen needs to be specified for the
+bottom part of the dive (_bottom po2_) as well as for the decompression part of the dive (_deco po2_).
+The most commonly
+used values are 1.4 bar for the bottom part of the dive and 1.6 bar for any decompression
+stages. Normally, a partial pressure of 1.6 bar is not exceeded. PO2 settings and the depth at which switching to a gas takes place can also be edited in the
+_Available Gases_ dialog. Normally the planner decides on switching to a new gas when, during
+ascent, the partial pressure of the new gas has decreased to 1.6 bar.
+
+
+*c) Gas management*: One needs keep within the limits of the amount of gas contained in the dive
+cylinder(s), allowing for an appropriate margin for safe return to the surface, possibly
+sharing with a buddy. Under the _Gas Options_ heading, specify the best (but conservative) estimate
+of your surface-equivalent air consumption (SAC, also termed RMV) in
+litres/min (for the time being, only SI units are supported).  Specify the SAC during the
+bottom part of the dive (_bottom SAC_) as well as during the decompression or safety stops of the
+dive (_deco SAC_). Values of 20-30 l/min are common. For good gas management, a thumbsuck guess
+is not sufficient and one needs to
+monitor one's gas consumption on a regular basis, dependent on different dive conditions and/or equipment.
+The planner will calculate the total volume of gas used during the dive and will issue a warning
+if one exceeds the total amount of gas available. Good practice demands that one does not dive to
+the limit of the gas supply but that an appropriate reserve is kept for unforeseen circumstances.
+For technical diving, this reserve can be up to 66% of the total available gas.
+
+Now (at last) one can start the detailed time-depth planning of the
+dive. _Subsurface_ offers a unique graphical interface for performing this
+part of the planning. The mechanics of doing this is similar to
+hand-entering a dive profile in the dive log part of _Subsurface_. Upon
+activating the planner, a default dive of depth 15 m for 40 min is offered
+in the green design surface to the top right hand of the screen. The white
+dots (waypoints) on the profile can be dragged with a mouse. Create more
+waypoints by double-clicking on the profile line and ensuring that the
+profile reflects the intended dive. Drag the waypoints to represent the
+depth and duration of the dive.  If any of the management limits (for
+nitrogen, oxygen or gas) is exceeded, the surface above the dive profile
+changes from BLUE to RED.
+
+Each waypoint on the dive profile creates a _Dive Planner Point_ in the
+table on the left of the dive planner panel. Ensure that the _Used Gas_
+value in each row of that table corresponds to one of the gas mixtures
+specified in the table with _Available Gases_ immediately above the Dive
+Planner Points. Add new waypoints until the main features of the dive have
+been completed, e.g. the bottom time segment and deep stops (if these are
+implemented). Leave the remaining waypoints on the ascent to
+_Subsurface_. In most cases _Subsurface_ computes additional way points in
+order to fulfil decompression requirements for that dive. A waypoint can be
+moved by selecting that waypoint and by using the arrow keys.  The waypoints
+listed in the _Dive Planner Points_ dialogue can be edited by hand in order
+to obtain a precise presentation of the dive plan. In fact, one can create
+the whole dive profile by editing the _Dive Planner Points_ dialog.
+
+Indicate any changes in gas cylinder used by indicating gas changes as
+explained in the section <<S_CreateProfile,hand-creating a dive
+profile>>. These changes should reflect the cylinders and gas compositions
+defined in the table with _Available Gases_.  If two or more gases are used,
+automatic gas switches will be suggested during the ascent to the
+surface. However, these changes can be deleted by right-clicking the gas
+change and by manually creating a gas change by right-clicking on the
+appropriate waypoint.
+
+A non-zero value in the "CC set point" column of the table of dive planner
+points indicates a valid setpoint for oxygen partial pressure and that the
+segment is dived using a closed circuit rebreather (CCR). If the last
+manually entered segment is a CCR segment, the decompression phase is
+computed assuming the diver uses a CCR with the specified set-point. If the
+last segment (however short) is on open circuit (OC, indicated by a zero
+set-point) the decompression is computed in OC mode. The planner only
+considers gas changes in OC mode.
+
+Below is an example of a dive plan to 45m using EAN26, followed by an ascent
+using EAN50 and using the settings as described above.
+
+image::images/DivePlanner2.jpg["FIGURE: Planning a dive: setup", align="center"]
+
+Once the above has been completed, one can save it by clicking the _Save_
+button towards the bottom left of the green design panel. The saved dive
+plan will appear in the *Dive List* panel of _Subsurface_.
+
+=== The dive plan details
+
+On the bottom right of the dive planner, under _Dive Plan Details_, the
+exact details of the dive plan are provided. These details may be modified
+by checking any of the options under the _Dive Notes_ section of the dive
+planner, immediately to the left of the _Dive Plan Details_. If a _Verbatim
+diveplan_ is requested, a detailed sentence-level explanation of the dive
+plan is given. If any of the management specifications have been exceeded
+during the planning, a warning message is printed underneath the dive plan
+information.
+
+If the option _Display segment duration_ is checked, then the duration of
+each depth level is indicated in the _Dive Plan Details_. This duration
+INCLUDES the transition time to get to that level. However, if the _Display
+transition in deco_ option is checked, the transitions are shown separately
+from the segment durations at a particular level.
+
+[[S_Replan]]
+=== Modifying an existing dive plan
+
+Normally, when a dive plan has been saved, it is accessible from the *Dive
+List*, like any other dive log. Within the *Dive List* there is not a way to
+change a saved dive plan.  To perform changes to a dive plan, select it on
+the *Dive List*. Then, in the main menu, select _Log -> Re-plan dive_. This
+will open the selected dive plan within the dive planner, allowing changes
+to be made and saved as usual.
+
+In addition there is the option "Save new". This keeps the original planned
+dive and adds a (possibly modified) copy to the dive list. If that copy is
+saved with the same start time as the original, the two dives are considered
+two versions of the same dive and do not influence other each during
+decompression calculation (see next section).
+
+=== Planning for repetitive dives
+
+Repetitive dives can easily be planned if the dates and start times of the
+repetitive dive set is specified appropriately in the top left-hand _Start
+Time_ field. _Subsurface_ calculates the gas loading figures correctly and
+the effect of the first dive is evaluated on later dives.
+
+If one has just completed a long/deep dive and is planning another dive,
+then highlight, in the *Dive List*, the dive that has just been completed
+and then activate the planner. Depending on the start time of the planned
+dive, the planner takes into account the gas loading incurred during the
+completed dive and allows planning within these limitations.
+
+If only a few standard configurations are used (e.g. in GUE), then a
+template dive can be created conforming to one of the configurations. If one
+now wishes to plan a dive using this configuration, just highlight the
+template dive in the *Dive List* and activate the planner: the planner takes
+into account the configuration in the highlighted dive.
+
+=== Printing the dive plan
+
+Selecting the _Print_ button in the planner allows printing of the _Dive
+Plan Details_ for wet notes. Alternatively one can cut and paste the _Dive
+Plan Details_ for inclusion in a text file or word processing document.
+
+Dive plans have many characteristics in common with dive logs (dive profile,
+dive notes, etc).  After a dive plan has been saved, the dive details and
+gas calculations are saved in the *Dive Notes* tab. While a dive plan is
+being designed, it can be printed using the _Print_ button in the dive
+planner. This prints the dive details and gas calculations in the _Dive Plan
+Details_ panel of the dive planner. However, after the plan has been saved,
+it is represented in a way very similar to a dive log and the gas
+calculations cannot be accessed in the same way as during the planning
+process. The only way to print the dive plan is to use the _File->Print_
+facility on the main menu in the same way as for dive logs or by copy and
+paste to a word processor.
+
+[[S_Configure]]
+== Configuring a dive computer
+
+_Subsurface_ enables one to configure a dive computer. Currently the
+Heinrichs-Weikamp (OSTC 2, OSTC 3) and Suunto Vyper (Stinger, Mosquito, D3,
+Vyper, Vytec, Cobra, Gekko and Zoop) family of dive computers are
+supported. A large number of settings of these dive computers can be read
+and changed to different values. As a first step, ensure that the
+appropriate hardware driver is installed for the dive computer and that the
+device name of the dive computer is known.  See
+<<_appendix_a_operating_system_specific_information_for_importing_dive_information_from_a_dive_computer,APPENDIX
+A>> for information on how to do this.
+
+Once the dive computer is connected to the _Subsurface_ computer, select
+_File->Configure dive computer_ from the _Main Menu_. Provide the
+appropriate device name in the text box at the top of the configuration
+panel that opens and select the appropriate dive computer model from the
+panel on the lefthand (see image below).
+
+image::images/Configure_dc_f20.jpg["FIGURE: Configure dive computer", align="center"]
+
+Using the appropriate buttons on the configuration panel, the following
+actions can be performed:
+
+ - *Retrieve available details*. This loads the existing configuration from the dive computer
+   to _Subsurface_, showing this in the configuration panel.
+ - *Save changes to device*. This changes the configuration of the
+   dive computer to correspond to the information shown in the configuration panel.
+ - *Backup*. This saves the configuration data to a file. _Subsurface_ asks for
+   a file location and file name for the saved information.
+ - *Restore backup*. This loads the information from a backup file and displays it
+   in the configuration panel.
+ - *Update firmware*. If new firmware is available for the dive computer, this is
+   loaded into the dive computer.
+
+== Description of the Subsurface Main Menu items
+
+This section describes the functions and operation of the items in the Main
+Menu of Subsurface. Several of the items below are links to sections of this
+manual dealing with the appropriate operations.
+
+=== File
+<<S_NewLogbook,_New Logbook_>> - Close the currently open dive logbook and
+clear all dive information.
+_Open logbook_ - This opens the file manager in order to select a dive
+logbook to open.
+- _Save_ - Save the dive logbook that is currently open.
+- _Save as_ - Save the current logbook under a different file name.
+- _Close_ - Close the dive logbook that is currently open.
+<<S_ExportLog,_Export_>> - Export the currently open dive logbook (or the
+selected dives in the logbook) to one of several formats.
+- <<S_PrintDivelog,_Print_>> - Print the currently open logbook.
+- <<S_Preferences,_Preferences_>> - Set the _Subsurface_ preferences.
+- <<S_Configure,_Configure dive computer_>> - Edit the configuration of a dive
+  computer.
+- _Quit_ - Quit _Subsurface_.
+
+=== Import
+<<S_ImportDiveComputer,_Import from dive computer_>> - Import dive
+information from a dive computer.
+<<Unified_import,_Import Log Files_>> - Import dive information from a file
+in in a _Subsurface_-compatible format.
+<<S_Companion,_Import GPS data from Subsurface web service_>> - Load GPS
+coordinates from the _Subsurface_ mobile phone app.
+<<S_ImportingDivelogsDe,_Import from Divelogs.de_>> - Import dive
+information from _www.Divelogs.de_.
+
+=== Log
+- <<S_EnterData,_Add Dive_>> - Manually add a new dive to the *Dive List*
+  panel.
+- <<S_DivePlanner,_Plan Dive_>> - This feature allows the planning of dives.
+- <<S_Replan,_Re-plan dive_>> - Edit a dive plan that has been saved into the
+  *Dive List*.
+- <<S_CopyComponents,_Copy dive components_>> - By selecting this option, one
+  can copy information from several fields of a dive log onto the clipboard.
+- _Paste dive components_ - Paste, into the selected dives in the *Dive List*,
+   the information copied using the _Copy dive components_ option.
+<<S_Renumber,_Renumber_>> - Renumber the dives listed in the *Dive List*
+panel.
+<<S_Group,_Auto Group_>> - Group the dives in the *Dive List* panel into
+dive trips.
+- <<S_DeviceNames,_Edit Device Names_>> - Edit the names of dive computers to
+  facilitate your logs.
+- <<S_Filter,_Filter divelist_>> - Select only some dives, based on specific
+  tags or dive criteria.
+
+=== View
+<<S_ViewPanels,_All_>> - View the four main _Subsurface_ panels
+simmultaneously.
+- <<S_ViewPanels,_Dive List_>> - View only the *Dive List* panel.
+- <<S_ViewPanels,_Profile_>> - View only the *Dive Profile* panel.
+- <<S_ViewPanels,_Info_>> - View only the *Dive Notes* panel.
+- <<S_ViewPanels,_Globe_>> - View only the *World Map* panel.
+_Yearly Statistics_ - Display summary statistics about dives during this and
+past years.
+- _Prev DC_ - Switch to previous dive computer.
+- _Next DC_ - Switch to next dive computer.
+- _Full Screen_ - Toggles Full Screen mode.
+
+=== Help
+_About Subsurface_ - Show a panel with the version number of _Subsurface_ as
+well as licensing information.
+_Check for updates_ - Find out whether a newer version of Subsurface is
+available on the http://subsurface-divelog.org/[_Subsurface_ web site].
+- _User Manual_ - Open a window showing this user manual.
+
+
+== APPENDIX A: Operating system specific information for importing dive information from a dive computer.
+
+=== Make sure that the OS has the required drivers installed
+[icon="images/icons/drivers.jpg"]
+[NOTE]
+The operating system of the desktop computer needs the appropriate drivers
+in order to communicate with the dive computer in whichever way the dive
+computer prefers (e.g. bluetooth, USB, infra-red).
+
+	* On Linux users need to have the correct kernel module loaded. Most
+	  distributions will do this automatically, so the user does not need to load
+	  kernel modules. However, some communication protocols require an additional
+	  driver, especially for rarely used technology such as infra-red.
+
+	* On Windows, the OS should offer to download the correct driver once the user
+	  connects the dive computer to the USB port and operating system sees the
+	  equipment for the first time.
+
+On a Mac users sometimes have to manually hunt for the correct driver. For
+example the correct driver for the Mares Puck devices or any other dive
+computer using a USB-to-serial interface based on the Silicon Labs CP2101 or
+similar chip can be found as _Mac_OSX_VCP_Driver.zip_ at the
+http://www.silabs.com/support/pages/document-library.aspx?p=Interface&f=USB%20Bridges&pn=CP2101[Silicon
+Labs document and software repository].
+
+[[S_HowFindDeviceName]]
+=== How to Find the Device Name for USB devices and set its write permission
+[icon="images/icons/usb.jpg"]
+[NOTE]
+When a user connects the dive computer by using a USB connector, usually
+_Subsurface_ will either propose a drop down list that contains the correct
+device name (or mount point for the Uemis Zurich), or it will disable the
+device select drop down if no device name is needed at all. In the rare
+cases where this doesn't work, here are some suggestions of ways to find out
+what the device name is:
+
+.On Windows:
+
+Simply try COM1, COM2, etc. The drop down list should contain all connected
+COM devices.
+
+.On MacOS:
+
+The drop down box should find all connected dive computers.
+
+.On Linux:
+
+There is a definitive way to find the port:
+
+ - Disconnect the USB cable from the dive computer
+ - Open a terminal
+ - Type the command: 'dmesg' and press enter
+ - Plug in the USB cable of the dive computer
+ - Type the command: 'dmesg' and press enter
+
+A message similar to this one should appear:
+
+	usb 2-1.1: new full speed USB device number 14 using ehci_hcd
+	usbcore: registered new interface driver usbserial
+	USB Serial support registered for generic
+	usbcore: registered new interface driver usbserial_generic
+	usbserial: USB Serial Driver core
+	USB Serial support registered for FTDI USB Serial Device
+	ftdi_sio 2-1.1:1.0: FTDI USB Serial Device converter detected
+	usb 2-1.1: Detected FT232BM
+	usb 2-1.1: Number of endpoints 2
+	usb 2-1.1: Endpoint 1 MaxPacketSize 64
+	usb 2-1.1: Endpoint 2 MaxPacketSize 64
+	usb 2-1.1: Setting MaxPacketSize 64
+	usb 2-1.1: FTDI USB Serial Device converter now attached to ttyUSB3
+	usbcore: registered new interface driver ftdi_sio
+	ftdi_sio: v1.6.0:USB FTDI Serial Converters Driver
+
+The third line from the bottom shows that the FTDI USB adapter is detected
+and connected to +ttyUSB3+. This information can now be used in the import
+settings as +/dev/ttyUSB3+ which directs Subsurface to the correct USB port.
+
+Ensuring that the user has write permission to the USB serial port:
+
+On Unix-like operating systems the USB ports can only be accessed by users
+who are members of the +dialout+ group. If one is not root, one may not be a
+member of that group and will not be able to use the USB port. Let us assume
+one's username is 'johnB'.
+
+As root, type: +usermod -a -G dialout johnB+ (Ubuntu users: +sudo usermod -a
+-G dialout johnB+)  This makes johnB a member of the +dialout+ group.
+Type: +id johnB+     This lists all the groups that johnB belongs to and
+verifies that
+the appropriate group membership has been created. The +dialout+ group should
+be listed
+among the different IDs.
+Under some circumstances this change takes only effect (eg. on Ubuntu) after
+one logs out and then logs in again.
+
+With the appropriate device name (e.g. +dev/ttyUSB3+) and with write
+permission to the USB port, the dive computer interface can connect and one
+should be able to import dives.
+
+[[S_HowFindBluetoothDeviceName]]
+=== Setting up bluetooth enabled devices
+[icon="images/icons/bluetooth.jpg"]
+[NOTE]
+For dive computers communicating through bluetooth like the Heinrichs
+Weikamp Frog or the Shearwater Predator and Petrel there is a different
+procedure to get the devices name to communicate with _Subsurface_. Follow
+these steps:
+
+ * *For the dive computer, after enabling Bluetooth, ensure it is in Upload mode.*
+
+For Bluetooth pairing of the dive computer, refer to the manufacturer's user
+guide. When using a Shearwater Predator/Petrel, select _Dive Log -> Upload
+Log_ and wait for the _Wait PC_ message.
+
+ * *Pair the _Subsurface_ computer with the dive computer.*
+
+.On Windows:
+
+Bluetooth is most likely already enabled. For pairing with the dive computer
+choose _Control Panel->Bluetooth Devices->Add Wireless Device_.  This should
+bring up a dialog showing your dive computer (in Bluetooth mode) and
+allowing pairing. Right click on it and choose _Properties->COM Ports_ to
+identify the port used for your dive computer. If there are several ports
+listed, use the one saying "Outgoing" instead of "Incoming".
+
+For downloading to _Subsurface_, the _Subsurface_ drop-down list should
+contain this COM port already. If not, enter it manually.
+
+Note: If there are issues afterwards when downloading from the dive computer
+using other software, remove the existing pairing with the dive computer.
+
+.On MacOS:
+
+Click on the Bluetooth symbol in the menu bar and select _Set up Bluetooth
+Device..._. The dive computer should then show up in the list of
+devices. Select it and go through the pairing process. This step should only
+be needed once for initial setup.
+
+Once the pairing is completed the correct device is shown in the 'Device or
+Mount Point' drop-down in the _Subsurface_ *Import* dialog.
+
+.On Linux
+Ensure Bluetooth is enabled on the _Subsurface_ computer.  On most common
+distributions this should be true out of the box and pairing should be
+straight forward. For instance, Gnome3 shows a Bluetooth icon in the upper
+right corner of the desktop where one selects 'Set up New Device'. This
+should show a dialog where one can select the dive computer (which already
+should be in Bluetooth mode) and pair it.  If a PIN is required, try
+manually setting '0000'.
+
+In the rare cases where the above is not true, then depending on your
+system, try +initd+ or +systemd+. This might be different and also involve
+loading modules specific to your hardware. In case your system is running
++systemd+, manually run +systemctl start bluetooth.service+ to enable it, in
+case of +initd+, run something like +rc.config start bluetoothd+ or
++/etc/init.d/bluetooth start+.
+
+One may also use a manual approach by using such commands:
+
++hciconfig+ shows the Bluetooth devices available on your computer (not dive
+computer), most likely one will see a hci0, if not try +hcitool -a+ to see
+inactive devices and run +sudo hciconfig hci0 up+ to bring them up.
+
++hcitool scanning+ gets a list of bluetooth enabled client devices, look for
+the dive computer and remember the MAC address are shown there
+
++bluez-simple-agent hci0 10:00:E8:C4:BE:C4+ pairs the dive computer with the
+bluetooth stack of the _Subsurface_ computer, copy/paste the MAC address
+from the output of 'hcitool scanning'
+
+Unfortunately on Linux binding to a communication device has to be done
+manually by running:
+
++rfcomm bind /dev/rfcomm0 10:00:E8:C4:BE:C4+ binds the dive computer to a
+communication device in the desktop computer, in case rfcomm is already
+taken use rfcomm1 or up. IMPORTANT: Copy/paste the MAC address from the
+output of +hcitool scanning+, the MAC address shown above will not work.
+
+For downloading dives in _Subsurface_ specify the device name connected to
+the MAC address in the last step above, e.g. _/dev/rfcomm0_.
+
+
+== APPENDIX B: Dive Computer specific information for importing dive information.
+
+[[S_ImportUemis]]
+=== Import from a Uemis Zurich
+
+[icon="images/icons/iumis.jpg"]
+[NOTE]
+_Subsurface_ downloads the information stored on the SDA (the built-in file
+system of the Uemis) including information about dive spots and
+equipment. Buddy information is not yet downloadable.  Things are very
+similar to a normal USB-connected dive computer (the Uemis is one of those
+that recharge when connected to the USB port).  The main difference is that
+one does not enter a device name, but instead the location where the
+UEMISSDA file system is mounted once connected to the dive computer. On
+Windows this is a drive letter ( often 'E:' or 'F:'), on a Mac this is
+'/Volumes/UEMISSDA' and on Linux systems this differs depending on the
+distribution. On Fedora it usually is
+'/var/run/media/<your_username>/UEMISSDA'. In all cases _Subsurface_ should
+suggest the correct location in the drop down list.
+
+After selecting the above device name, download the dives from the Uemis
+Zurich. One technical issue with the Uemis Zurich download implementation
+(this is a Uemis firmware limitation, not a _Subsurface_ issue) is that one
+cannot download more than about 40-50 dives without running out of memory on
+the SDA. This will usually only happen the very first time one downloads
+dives from the Uemis Zurich.  Normally when downloading at the end of a day
+or even after a dive trip, the capacity is sufficient. If _Subsurface_
+displays an error that the dive computer ran out of space the solution is
+straight forward.  Disconnect the SDA, turn it off and on again, and
+reconnect it. You can now retry (or start a new download session) and the
+download will continue where it stopped previously. One may have to do this
+more than once, depending on how many dives are stored on the dive computer.
+
+[[S_ImportingGalileo]]
+=== Importing dives from the Uwatec Galileo
+
+[icon="images/icons/Galileo.jpg"]
+[NOTE]
+The Uwatec Galileo dive computers use infra red (IrDA) communication between
+the dive computer and Subsurface. The Uwatec hardware uses a USB dongle
+based on the serial infra-red (SIR) protocol and the MSC7780 IrDA controller
+manufactured by MosChip and marketed by Scubapro and some electronics
+companies.  Under Linux, the kernel already provides for communication using
+the IrDA protocol. However, the user additionally needs to load a driver for
+the IrDA interface with the dive computer. The easiest way is to load the
+*irda-tools* package from the
+http://irda.sourceforge.net/docs/startirda.html[Linux IrDA Project].  After
+the installation of the irda-tools, the *root user* can specify a device
+name from the console as follows: +irattach irda0+
+
+After executing this command, Subsurface will recognise the Galileo dive
+computer and download dive information.
+
+Under Windows, a similar situation exists. Drivers for the MCS7780 are
+available from some Internet web sites e.g.
+http://www.drivers-download.com/Drv/MosChip/MCS7780/[www.drivers-download.com].
+
+For the Apple Mac, IrDA communication via the MCS7780 link is not available
+for OSX 10.6 or higher.
+
+[[S_ImportingDR5]]
+=== Importing dives from Heinrichs Weikamp DR5
+
+[icon="images/icons/HW_DR5.jpg"]
+[NOTE]
+When mounted as a USB drive the Heinrichs Weikamp DR5 saves a single UDDF
+file for every dive.  Mark all the dives you'd like to import or open.
+Note: The DR5 does not seem to store gradient factors nor deco information,
+so for _Subsurface_ it is not possible to display them. Adjust the gradient
+factors in the _Graph Settings_ in _Subsurface_ to generate a deco overlay
+in the _Subsurface_ *Dive Profile* panel but please note that the deco
+calculated by _Subsurface_ will most likely differ from the one displayed on
+the DR5.
+
+=== Import from Shearwater Predator using Bluetooth
+
+[icon="images/icons/predator.jpg"]
+[NOTE]
+Using a Shearwater Predator one may be able to pair Bluetooth but then
+encounter issues when downloading, showing errors like _Slip RX: unexp. SLIP
+END_ on the Predator.  This might also arise when using other dive log
+software and operating systems other than Linux. We have no detailed idea
+about the source and how to fix this, but it is reported to be solved
+sometimes by one of these steps:
+
+ * use the Bluetooth dongle which came with the Shearwater Predator instead of
+   the built-in one of the _Subsurface_ computer
+ * switch to different Bluetooth drivers for the same hardware
+ * switch off WiFi while using Bluetooth
+
+[[S_PoseidonMkVI]]
+=== Importing dive logs from the Poseidon MkVI Discovery
+
+[icon="images/MkVI.jpeg"]
+[NOTE]
+Download of dive logs from the MkVI is performed using a custom
+communications adapter and the _Poseidon PC Configuration Software_,
+obtained when purchasing the MKVI equipment. The latter is a Windows
+application allowing configuration of equipment and storage of dive
+logs. Communication between dive computer and desktop computer utilises the
+IrDA infra-red protocol. Only data for one dive can be downloaded at a time,
+comprising three files:
+
+Setup configuration for the dive and key dive parameters (file with a .txt
+extension)
+- Dive log details (file with a .csv extension)
+Redbook format dive log (file with .cvsr extension). This is a compressed
+version of the dive log using a proprietary format.
+
+_Subsurface_ accesses the .txt and the .csv files to obtain dive log
+information.
+
+
+=== Importing dive logs from the APD Inspiration CCR
+
+[icon="images/APDComputer.jpg"]
+[NOTE]
+The dive logs of an APD Inspiration or similar CCR dive computer are
+downloaded using a communications adapter and _AP Communicator_, obtained
+when purchasing the equipment. The dive logs can be viewed using the _AP Log
+Viewer_, within Windows or Mac/OS. However, APD logs can be viewed and
+managed from within _Subsurface_ (together with dives using many other types
+of dive computer). The APD inspiration dive logs are imported into
+_Subsurface_ as follows:
+
+- Open a dive within the _AP Log Viewer_.
+- Select the tab at the top of the screen, entitled "_Data_".
+- If the raw dive log data show on the screen, click on "_Copy to Clipboard_".
+- Open a text editor, e.g. Notepad (Windows), TextWrangler (Mac).
+Copy the contents of the clipboard into the text editor and save the text
+file with a filename extension of .CSV
+- Within _Subsurface_, select _Import->Import log files_ to open the
+  xref:Unified_import[universal import dialogue].
+- In the dropdown list towards the bottom right of the dialogue, select "_CSV
+  files_".
+On the list of file names select the .CSV file that has been created
+above. An import dialogue opens.
+In the dropdown list on the middle right labeled '_Pre-configured imports_",
+select _APD Log Viewer_.
+- Ensure the other settings for the ADP dive log are appropriate, then select
+  _OK_.
+
+The APD dive log will appear within _Subsurface_.
+
+
+== APPENDIX C: Exporting Dive log information from external dive log software.
+
+The import of dive log data from external dive log software is mostly
+performed using the dialogue found by selecting _Import_ from the Main Menu,
+then clicking on _Import Log Files_. This is a single-step process, more
+information about which can be found xref:Unified_import[here.] However, in
+some cases, a two-step process may be required:
+
+Export the foreign dive log data to format that is accessible from
+_Subsurface_.
+2. Import the accessible dive log data into _Subsurface_.
+
+This appendix provides some information about approaches to export dive log
+data from foreign dive log software. The procedures below mostly apply to
+Linux and/or Windows.
+
+[[S_ImportingDivesSuunto]]
+=== Exporting dives from *Suunto Divemanager (DM3, DM4 or DM5)*
+[icon="images/icons/suuntologo.jpg"]
+[NOTE]
+DiveManager is a MS Windows application for Suunto dive computers.
+Divemanager 3 (DM3) is an older version of the Suunto software. More recent
+Suunto dive computers use Divemanager version 4 or 5 (DM4 or DM5). The
+different versions of Divemanager use different methods and different file
+naming conventions to export dive log data.
+
+*Divemanager 3 (DM3):*
+
+1. Start 'Suunto Divemanager 3' and log in with the name containing the logs
+2. Do not start the import wizard to import dives from the dive computer.
+In the navigation tree on the left side of the program-window, select the
+appropriate dives.
+4. Within the list of dives, select the dives you would like to import later:
+	* To select certain dives: hold 'ctrl' and click the dive
+To select all dives: Select the first dive, hold down shift and select the
+last dive
+5. With the dives marked, use the program menu _File -> Export_
+6. The export pop-up will show. Within this pop-up, there is one field called
+   'Export Path'.
+	* Click the browse button next to the field Export Path
+** A file-manager like window pops up
+** Navigate to the directory for storing the
+Divelog.SDE file
+		** Optionally change the name of the file for saving
+		** Click 'Save'
+	* Back in the Export pop-up, press the button 'Export'
+7. The dives are now exported to the file Divelog.SDE.
+
+*Divemanager 4 (DM4) and Divemanager 5 (DM5):*
+
+DM4 and DM5 use identical mechanisms for exporting dive logs.  To export a
+divelog from Divemanager one needs to locate the DM4/DM5 database where the
+dives are stored. the user can either look for the original database or make
+a backup of the dives. Both methods are described here.
+
+Locating the Suunto DM4 (or DM5) database:
+
+1. Start Suunto DM4/DM5
+2. Select 'Help -> About'
+3. Click 'Copy' after text 'Copy log folder path to clipboard'
+4. Now open Windows Explorer
+5. Paste the address to the path box at the top of the File Explorer
+6. The database is called DM4.db or DM5.db
+
+Making a backup copy of the Suunto DM4/DM5 database:
+
+1. Start Suunto DM4/DM5
+2. Select 'File - Create backup'
+3. From the file menu select the location and name for the backup, we'll use
+   DM4 (or DM5) in here with the default extension .bak
+4. Click 'Save'
+5. The dives are now exported to the file DM4.bak (or DM5.bak)
+
+
+=== Exporting from Mares Dive Organiser V2.1
+[[Mares_Export]]
+
+[icon="images/icons/mareslogo.jpg"]
+[NOTE]
+Mares Dive Organiser is a Windows application. The dive log is kept as a
+Microsoft SQL Compact Edition database with a '.sdf' filename extension. The
+database includes all Dive Organiser-registered divers on the particular
+computer and all Mares dive computers used. The safest way to obtain a copy
+of the dive database is to export the information to another compatible
+format which can be imported into _Subsurface_.
+
+Within Dive Organiser, select _Database -> Backup_ from the main menu and
+back up the database to the desk top.  This creates a zipped file
+DiveOrganiserxxxxx.dbf.
+Rename the file to DiveOrganiserxxxxx.zip. Inside the zipped directory is a
+file _DiveOrganiser.sdf_.
+3. Extract the _.sdf_ file from the zipped folder to your Desktop.
+4. The password for accessing the .zip file is _mares_.
+
+[[S_ImportingDivingLog]]
+=== Exporting dives from *DivingLog 5.0*
+
+[icon="images/icons/divingloglogo.jpg"]
+[NOTE]
+Unfortunately DivingLog XML files give us no indication on the preferences
+set on one's system. So in order for _Subsurface_ to be able to successfully
+import XML files from DivingLog one first needs to ensure that DivingLog is
+configured to use the Metric system (one can easily change this within
+Diving Log by selecting 'File -> Preferences -> Units and Language' by
+clicking the 'Metric' button). Then do the following:
+
+1. In DivingLog open the 'File -> Export -> XML' menu
+2. Select the dives to export
+3. Click on the export button and select the filename
+
+[[S_Appendix_D]]
+== APPENDIX D: Exporting a spreadsheet to CSV format
+
+Many divers keep a diving log in some form of a digital file, commonly a
+spreadsheet with various fields of information. These logs can be easily
+imported into _Subsurface_ (xref:S_ImportingManualCSV[Importing dives
+from_manually kept CSV file]), after the spreadsheet is converted in a .CSV
+file.  This section explains the procedure to convert a diving logbook
+stored in a spreadsheet to a .CSV file that will later be imported from
+_Subsurface_.  Creating a .CSV is a straightforward task, although the
+procedure is somewhat different according to which spreadsheet program is
+used.
+
+The first step is to organize the diving data in the spreadsheet, so that
+the first row contains the names (or titles) of each column and the
+information for each dive is stored in a single row.  _Subsurface_ supports
+many data items (Dive #, Date, Time, Duration, Location, GPS, Max Depth,
+Mean Depth, Buddy, Notes, Weight and Tags).  The user can organize dive data
+following a few simple rules:
+
+1. Date: use one of the following formats: yyyy-mm-dd, dd.mm.yyyy, mm/dd/yyyy
+2. Duration: the format should be minutes:seconds.
+3. Unit system: only one unit system shold be used (i.e., no mixture between
+   imperial and metric units)
+4. Tags and buddies: values should be separated using a comma.
+5. GPS position: users must use decimal degrees, e.g. 30.22496 30.821798
+
+=== _LibreOffice Calc_ and _OpenOffice Calc_
+
+These are open source spreadsheet applications forming parts of larger open
+source office suite applications. The user interaction with _LibreOffice_
+and _OpenOffice_ is very similar.  In Libreoffice Calc the time format
+should be set to minutes:seconds - [mm]:ss and dates should be set to one
+of: yyyy-mm-dd, dd.mm.yyyy, mm/dd/yyyy. A typical dive log may look like
+this:
+
+image::images/LOffice_spreadsheetdata.jpg["FIGURE: Spreadsheet data", align="center"]
+
+To export the data as a .CSV file from within LibreOffice click _File ->
+Save As_. On the dialogue that comes up, select the _Text CSV (.csv)_ as the
+file type and select the option _Edit filter settings_.
+
+image::images/LOffice_save_as_options.jpg["FIGURE: Save as options", align="center"]
+
+After selecting _Save_, select the appropriate field delimiter (choose _Tab_
+to prevent conflicts with the comma when using this as a decimal point),
+then select _OK_.
+
+image::images/LOffice_field_options.jpg["FIGURE: Field options", align="center"]
+
+One can double check the .CSV file by opening it with a text editor, and
+then import the dive data as explained on the section
+xref:S_ImportingManualCSV[Importing dives from manually kept CSV files].
+
+=== Microsoft _Excel_
+
+The field delimiter (called "_list separator_" in Microsoft manuals) is not
+accessible from within _Excel_ and needs to be set through the _Microsoft
+Control Panel_. After changing the separator character, all software on the
+Windows machine use the new character as a separator.  One can change the
+character back to the default character by following the same procedure,
+outlined below.
+
+- In Microsoft Windows, click the *Start* button, and then select _Control
+  Panel_ from the list on the right-hand side.
+- Open the _Regional and Language Options_ dialog box.
+Do one of the following: ** In Windows 7, click the _Formats_ tab, and then
+click _Customize this format_.  ** In Windows XP, click the _Regional
+Options_ tab, and then click _Customize_.
+- Type a new separator in the _List separator_ box. To use a TAB-delimited
+  file, type the word TAB in the box.
+- Click _OK_ twice.
+
+Below is an image of the _Control Panel_:
+
+image::images/Win_SaveCSV2.jpg["FIGURE: Win List separator", align="center"]
+
+To export the dive log in CSV format:
+
+With the dive log opened in _Excel_, select the round Windows button at the
+top left, then _Save As_.
+
+image::images/Win_SaveCSV1.jpg["FIGURE: Excel save as option", align="center"]
+
+Click on the left-hand part of the _Save as_ option, NOT on the arrow on the
+right-hand. This brings up a dialogue for saving the spreadsheet in an
+alternative format. From the dropdown list at the bottom of the dialogue,
+marked _Save as Type:_, select _CSV(Comma delimited) (*.CSV)_. Ensure that
+the appropriate folder has been selected to save the CSV file into.
+
+image::images/Win_SaveCSV3.jpg["FIGURE: Excel save CSV dialogue", align="center"]
+
+Select the _Save_ button. The CSV-formatted file is saved into the folder
+that was selected. One can double check the .CSV file by opening it with a
+text editor, and then import the dive data as explained on the section
+xref:S_ImportingManualCSV[Importing dives from manually kept CSV files].
+
+== APPENDIX E: FAQs.
+
+=== Subsurface appears to miscalculate gas consumption and SAC
+[[SAC_CALCULATION]]
+'Question': I dived with a 12.2 l tank, starting with 220 bar and ending
+with 100 bar, and I calculate a different SAC compared what _Subsurface_
+calculates. Is _Subsurface_ miscalculating?
+
+'Answer': Not really. What happens is that _Subsurface_ actually calculates
+gas consumption differently - and better - than you expect.  In particular,
+it takes the incompressibility of the gas into account.  Traditionally, Gas
+consumption and SAC should be: +consumption = tank size x (start pressure -
+end pressure)+
+
+and that's true for an ideal gas, and it's what you get taught in dive
+theory.  But an "ideal gas" doesn't actually exist, and real gases actually
+don't compress linearly with pressure. Also, you are missing the fact that
+one atmosphere of pressure isn't actually one bar.  So the *real*
+calculation is:
+
++consumption = (amount_of_air_at_beginning - amount_of_air_at_end)+
+
+where the amount of air is *not* just "tank size times pressure in bar".
+It's a combination of: "take compressibility into account" (which is a
+fairly small issue under 220 bar - you'll see more differences when you do
+high-pressure tanks with 300bar) and "convert bar to atm" (which is the
+majority of your discrepancy).  Remember: one ATM is ~1.013 bar, so without
+the compressibility, your gas use is:
+
++12.2*((220-100)/1.013)+
+
+which is about 1445, not 1464. So there was 19 l too much in your simple
+calculation that ignored the difference between 1 bar and one ATM.  The
+compressibility does show up above 200 bar, and takes that 1445 down about
+eight litres more, so you really did use only about 1437 l of air at surface
+pressure.
+
+So be happy: your SAC really is better than your calculations indicated.  Or
+be sad: your cylinder contains less air than you thought it did.  And as
+mentioned, the "contains less air than you thought it did" really starts
+becoming much more noticeable at high pressure. A 400 bar really does not
+contain twice as much air as a 200 bar one. At lower pressures, air acts
+pretty much like an ideal gas.
+
+=== Some dive profiles have time discrepancies with the recorded samples from my dive computer...
+
+_Subsurface_ ends up ignoring surface time for many things (average depth,
+divetime, SAC, etc).  'Question': Why do dive durations in my dive computer
+differ from that given by _Subsurface_?
+
+'Answer': For example, if you end up doing a weight check (deep enough to
+trigger the "dive started")  but then come back up and wait five minutes for
+your buddies, your dive computer may say that your dive is 50 minutes long -
+because you have fifty minutes worth of samples - but subsurface will say
+it's 45 minutes - because you were actually diving for 45 minutes.  It's
+even more noticeable if you do things like divemastering the initial OW
+dives, when you may stay in the water for a long time, but spend most of it
+at the surface. And then you don't want that to count as some kind of long
+dive”.