diff options
156 files changed, 38523 insertions, 34436 deletions
diff --git a/.gitattributes b/.gitattributes index 2b45716e4..ca450ba95 100644 --- a/.gitattributes +++ b/.gitattributes @@ -1,2 +1,3 @@ .gitignore export-ignore .gitattributes export-ignore +Documentation/*.html.git text=auto diff --git a/CMakeLists.txt b/CMakeLists.txt index c636d1f36..ea6f17e66 100644 --- a/CMakeLists.txt +++ b/CMakeLists.txt @@ -1,5 +1,8 @@ # cmake based build of Subsurface +# Uncomment his to see all commands cmake actually executes +# set(CMAKE_VERBOSE_MAKEFILE ON) + project(Subsurface) cmake_minimum_required(VERSION 2.8.11) diff --git a/Documentation/50-pot/subsurface-mobile-manual.pot b/Documentation/50-pot/subsurface-mobile-manual.pot new file mode 100644 index 000000000..45a130b64 --- /dev/null +++ b/Documentation/50-pot/subsurface-mobile-manual.pot @@ -0,0 +1,632 @@ +# SOME DESCRIPTIVE TITLE +# Copyright (C) YEAR Free Software Foundation, Inc. +# This file is distributed under the same license as the subsurface-manual package. +# FIRST AUTHOR <EMAIL@ADDRESS>, YEAR. +# +#, fuzzy +msgid "" +msgstr "" +"Project-Id-Version: subsurface-manual VERSION\n" +"Report-Msgid-Bugs-To: subsurface@subsurface-divelog.org\n" +"POT-Creation-Date: 2016-03-12 13:31+0100\n" +"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" +"Last-Translator: FULL NAME <EMAIL@ADDRESS>\n" +"Language-Team: LANGUAGE <LL@li.org>\n" +"Language: \n" +"MIME-Version: 1.0\n" +"Content-Type: text/plain; charset=UTF-8\n" +"Content-Transfer-Encoding: 8bit\n" + +#. :website: http://subsurface-divelog.org +#. type: Target for macro image +#: mobile-manual.txt:14 +#, no-wrap +msgid "mobile-images/banner.jpg" +msgstr "" + +#. type: Plain text +#: mobile-manual.txt:17 +msgid "[big]#Subsurface-mobile for Android: USER MANUAL#" +msgstr "" + +#. type: Plain text +#: mobile-manual.txt:19 +#, no-wrap +msgid "*Manual author*: Willem Ferguson\n" +msgstr "" + +#. type: Plain text +#: mobile-manual.txt:21 +msgid "toc::[]" +msgstr "" + +#. type: Plain text +#: mobile-manual.txt:23 +msgid "[blue]#_Version 1.0, March 2016_#" +msgstr "" + +#. type: Plain text +#: mobile-manual.txt:31 +msgid "" +"Welcome as a user of _Subsurface_, advanced dive logging software with " +"extensive infrastructure to describe, organize, interpret and print scuba " +"and free dives. _Subsurface_ offers many advantages over other similar " +"software solutions, including compatibility with Windows, Mac-OS/X, Linux " +"(many distributions) and Android (iOS under development). In addition, " +"_Subsurface_ is open-source software that allows downloading dive " +"information from most dive computers." +msgstr "" + +#. type: Title - +#: mobile-manual.txt:33 +#, no-wrap +msgid "Introducing Subsurface-mobile" +msgstr "" + +#. type: Plain text +#: mobile-manual.txt:40 +msgid "" +"_Subsurface-mobile_ is an extension of _Subsurface_ on laptop and tabletop " +"computers. It runs on Android smartphone and tablet devices and is a tool " +"for viewing or sharing dive information at dive sites where a larger " +"computer is not useful. _Subsurface-mobile_ also allows the gathering of GPS " +"locations where dives are performed." +msgstr "" + +#. type: Plain text +#: mobile-manual.txt:43 +msgid "" +"A version of _Subsurface-mobile_ for iOS is under development but not yet " +"ready for testing." +msgstr "" + +#. type: Plain text +#: mobile-manual.txt:53 +msgid "" +"While _Subsurface-mobile_ allows one to enter and save dive information " +"using an Android device, users of _Subsurface-mobile_ typically use the " +"mobile app as an extension of the laptop/desktop version of _Subsurface_. " +"This allows the storage of dive logs on the Internet and which can be shared " +"by the Android version as well as the desktop version. While the desktop " +"version of _Subsurface_ shows much more detailed information for each dive, " +"the mobile version allows one to have a more accessible dive log on a dive " +"trip, useful for proving dive experience to dive shops or to review previous " +"dives." +msgstr "" + +#. type: Plain text +#: mobile-manual.txt:55 +msgid "_Subsurface-mobile_ allows one to:" +msgstr "" + +#. type: Plain text +#: mobile-manual.txt:57 +msgid "Download existing dive log information from the Internet." +msgstr "" + +#. type: Plain text +#: mobile-manual.txt:58 +msgid "View this information on an Android device." +msgstr "" + +#. type: Plain text +#: mobile-manual.txt:60 +msgid "" +"Edit many of the dive log data fields, e.g. divemaster, buddy, equipment or " +"notes about a dive." +msgstr "" + +#. type: Plain text +#: mobile-manual.txt:61 +msgid "Create and add new dive records to one's dive log." +msgstr "" + +#. type: Plain text +#: mobile-manual.txt:62 +msgid "Store the updated dive log on the Internet." +msgstr "" + +#. type: Plain text +#: mobile-manual.txt:63 +msgid "Record, store and apply GPS positions of dives." +msgstr "" + +#. type: Plain text +#: mobile-manual.txt:65 +msgid "View the localities of recorded GPS positions and of dives on a map." +msgstr "" + +#. type: Plain text +#: mobile-manual.txt:72 +msgid "" +"These items are discussed in greater detail in the following text. What " +"_Subsurface-mobile_ does not support (at this time) is downloading dive data " +"directly from a dive computer. That still has to happen with _Subsurface_ on " +"a desktop or laptop computer. We are investigating ways to support " +"downloading from a subset of the supported dive computers on Android " +"devices, but this is not yet ready for testing." +msgstr "" + +#. type: Title == +#: mobile-manual.txt:73 +#, no-wrap +msgid "Installing _Subsurface-mobile_ on an Android device" +msgstr "" + +#. type: Plain text +#: mobile-manual.txt:77 +msgid "" +"Find _Subsurface-mobile_ in the _Google Play Store_. Search for " +"_Subsurface-mobile_ and install it." +msgstr "" + +#. type: Title == +#: mobile-manual.txt:78 +#, no-wrap +msgid "Using _Subsurface-mobile_ for the first time" +msgstr "" + +#. type: Plain text +#: mobile-manual.txt:84 +msgid "" +"Upon starting _Subsurface-mobile_ for the first time, a Subsurface splash " +"screen is shown while the program loads. On some devices this may take " +"several seconds. After loading, the _Cloud Credentials screen_ appears (see " +"image below)." +msgstr "" + +#. type: Target for macro image +#: mobile-manual.txt:85 +#, no-wrap +msgid "mobile-images/landingscreen.jpg" +msgstr "" + +#. type: Plain text +#: mobile-manual.txt:93 +#, no-wrap +msgid "" +"Since _Subsurface_ is largely dependent on a dive log saved on the " +"Internet,\n" +"provide a user-ID and password for access to the _Subsurface Cloud_. These\n" +"credentials are obtained by opening the desktop version of _Subsurface_ " +"and\n" +"by clicking _File -> Preferences -> Network_, explained in detail in " +"the\n" +"user manual for the _Subsurface_ desktop version. Once the account has\n" +"been created and verified using the desktop version one can use " +"_Subsurface-mobile_.\n" +msgstr "" + +#. type: Plain text +#: mobile-manual.txt:102 +msgid "" +"When entering a password, it is possible to check a checkbox that enables " +"the text of the password to be shown. Checking the check box labelled " +"\"Remember\" allows _Susburface-mobile_ to keep the credentials for " +"subsequent logins (see image above). Having entered the credentials, tap " +"the disk icon at the bottom of the screen. _Subsurface-mobile_ attempts to " +"download the existing dive log from the_Subsurface_ cloud " +"server. Appropriate messages are shown onscreen. Finally a list of dives are " +"shown." +msgstr "" + +#. type: Title == +#: mobile-manual.txt:104 +#, no-wrap +msgid "Local copy of the dive log and synchronisation with Internet" +msgstr "" + +#. type: Plain text +#: mobile-manual.txt:114 +msgid "" +"Once the dive list has been downloaded from the Internet, " +"_Subsurface-mobile_ keeps a local copy on the mobile device. This means " +"that, if there is no Internet connection at a dive site, one can still " +"access the local copy and view and manipulate dive information. If there is " +"Internet connectivity, _Subsurface-mobile_ accesses the Internet-based dive " +"log to verify that the local copy is still the same as the Internet-stored " +"copy. If not, the local copy and the copy on the server are synchronised." +msgstr "" + +#. type: Title == +#: mobile-manual.txt:115 +#, no-wrap +msgid "A Few Remarks About The User Interface" +msgstr "" + +#. type: Plain text +#: mobile-manual.txt:124 +msgid "" +"At the bottom of many Subsurface-mobile screens is a round button that " +"provides for several actions and which allows the selection of the main " +"affirmative action (see image above and image below). On Android devices, " +"use the Android Back button for \"cancel\", \"discard\" or \"back\" " +"actions. For example, when editing dive information, tapping the action " +"button saves the changes, the Android back button can be used to cancel the " +"edit without saving changes." +msgstr "" + +#. type: Target for macro image +#: mobile-manual.txt:125 +#, no-wrap +msgid "mobile-images/actionbutton.jpg" +msgstr "" + +#. type: Plain text +#: mobile-manual.txt:132 +msgid "" +"Instead of the more traditional \"hamburger\" menu button in the top left or " +"right corner of the screen to open menus, _Subsurface-mobile_ uses a " +"different user interaction philosophy based on the Kirigami framework " +"developed by the Plasma developers. To open the main menu one has three " +"options:" +msgstr "" + +#. type: Plain text +#: mobile-manual.txt:135 +msgid "" +"Tap on the right-arrow symbol in the lower left corner of the screen (easy " +"to reach for hand held devices)" +msgstr "" + +#. type: Plain text +#: mobile-manual.txt:136 +msgid "Swipe towards the right across the left edge of the screen" +msgstr "" + +#. type: Plain text +#: mobile-manual.txt:138 +msgid "" +"Drag the action button visible on most screens with the main action to the " +"right" +msgstr "" + +#. type: Target for macro image +#: mobile-manual.txt:139 +#, no-wrap +msgid "mobile-images/menu.jpg" +msgstr "" + +#. type: Plain text +#: mobile-manual.txt:145 +msgid "" +"The images above indicate some of the important features of the menu " +"system. On the left is the main menu that is activated as described " +"above. In the middle is the menu that opens if one taps the _GPS_ option on " +"the main menu. On the right is the menu that opens if one taps the _Manage " +"Dives_ option on the main menu." +msgstr "" + +#. type: Plain text +#: mobile-manual.txt:148 +msgid "" +"Similarly, the context menu (currently only available on the dive details " +"screen) can be opened one of these three ways:" +msgstr "" + +#. type: Plain text +#: mobile-manual.txt:150 +msgid "Tap on the left-arrow symbol in the lower right corner of the screen" +msgstr "" + +#. type: Plain text +#: mobile-manual.txt:151 +msgid "Swipe to the left across the right edge of the screen" +msgstr "" + +#. type: Plain text +#: mobile-manual.txt:152 +msgid "Drag the action button to the left" +msgstr "" + +#. type: Title == +#: mobile-manual.txt:153 +#, no-wrap +msgid "Viewing the Dive List" +msgstr "" + +#. type: Plain text +#: mobile-manual.txt:161 +msgid "" +"Most of the actions of _Subsurface-mobile_ center around the dives on the " +"dive list. While the dive list is loading from the cloud, a message appears " +"at the bottom of the screen, indicating that the cloud is being accessed " +"(see image on left, below). Once the list is loaded one can scroll up and " +"down. Tapping a dive on the list brings up a display of _Details View_ for " +"that dive (see image on right below). This includes the dive profile as " +"well as additional information and notes." +msgstr "" + +#. type: Target for macro image +#: mobile-manual.txt:162 +#, no-wrap +msgid "mobile-images/divelist.jpg" +msgstr "" + +#. type: Plain text +#: mobile-manual.txt:166 +msgid "" +"One can view other dives by swiping the _Details view_ to the right (for the " +"previous dive) or to the left (following dive)." +msgstr "" + +#. type: Title == +#: mobile-manual.txt:167 +#, no-wrap +msgid "Editing dive details." +msgstr "" + +#. type: Plain text +#: mobile-manual.txt:177 +msgid "" +"At the bottom of the dive details screen the _Action Button_ contains a " +"pencil (image on right, above). Tapping the button brings up a panel with " +"edit boxes that allows one to change the existing dive information, " +"e.g. adding text to the dive notes or changing the names or values of some " +"of the information (see image below). It may be necessary to scroll the " +"window to access all the information. At the bottom of the edit screen is a " +"_Save_ action button. Tap this to save the new information. Having saved the " +"data, the dive list screen is updated and shown. To cancel any edits, tap " +"the Android Back Button." +msgstr "" + +#. type: Target for macro image +#: mobile-manual.txt:178 +#, no-wrap +msgid "mobile-images/editdive.jpg" +msgstr "" + +#. type: Title == +#: mobile-manual.txt:180 +#, no-wrap +msgid "Adding a new dive to the dive list" +msgstr "" + +#. type: Plain text +#: mobile-manual.txt:191 +msgid "" +"It is also possible to add an additional dive to the existing dive list. On " +"the main menu tap _Manage dives -> Add dive manually_. This opens a screen " +"that is identical to the editing screen discussed above. When a dive is " +"added manually, one cannot directly add a dive profile from a dive " +"computer. However, if one does not use a dive computer, the duration, depth " +"and several other bits of information about the new dive can be entered. The " +"_Action button_ at the bottom of the screen contains a disk symbol. Tap this " +"to save the new dive. To cancel any edits, tap the Android Back Button. The " +"left-hand image below shows a screenshot of a dive being created and the " +"right-hand image shows the same dive in _Details View_." +msgstr "" + +#. type: Target for macro image +#: mobile-manual.txt:192 +#, no-wrap +msgid "mobile-images/createdive.jpg" +msgstr "" + +#. type: Title == +#: mobile-manual.txt:194 +#, no-wrap +msgid "Deleting a dive" +msgstr "" + +#. type: Plain text +#: mobile-manual.txt:201 +msgid "" +"The _details view_ of a dive has a context menu on the right-hand side that " +"can be activated as described above (e.g. by tapping the arrow icon at the " +"bottom right of the screen or by dragging the _Action Button_ to the left). " +"The context menu has a single item: \"Delete dive\". If this option is " +"tapped, the dive shown in the _Details View_ is deleted. One has a brief " +"opportunity to undo the delete by tapping the _undo_ message that appears at " +"the bottom of the screen. If the _undo_ message is not tapped, the dive is " +"deleted." +msgstr "" + +#. type: Title == +#: mobile-manual.txt:202 +#, no-wrap +msgid "Dive log management" +msgstr "" + +#. type: Plain text +#: mobile-manual.txt:212 +#, no-wrap +msgid "" +"A central part of _Subsurface-mobile_ is the ability to store the dive\n" +"log using the _Subsurface_ cloud storage.\n" +"This provides security against loss or damage to the dive information " +"caintained in a local copy of\n" +"the dive log and allows the desktop version of _Subsurface_ to\n" +"access changes made using the mobile device. This ability is accessed\n" +"throug the main menu (by dragging the Action Button to the right, or\n" +"alternatively tap the right angle button at the bottom left of the " +"screen).\n" +" Tap the option _Manage dives_, enabling a number of options:\n" +msgstr "" + +#. type: Title === +#: mobile-manual.txt:213 +#, no-wrap +msgid "Add new dive manually" +msgstr "" + +#. type: Plain text +#: mobile-manual.txt:216 +msgid "This is described above under the section dealing with the dive list." +msgstr "" + +#. type: Title === +#: mobile-manual.txt:217 +#, no-wrap +msgid "Upload dive log to the _Subsurface_ cloud storage" +msgstr "" + +#. type: Plain text +#: mobile-manual.txt:223 +msgid "" +"One can upload the dives contained on the mobile device to the _Subsurface_ " +"cloud storage by tapping the option _Upload to cloud_. This synchronizes " +"the local changes to the dive log with the cloud storage." +msgstr "" + +#. type: Title === +#: mobile-manual.txt:224 +#, no-wrap +msgid "Download dive log from the cloud storage" +msgstr "" + +#. type: Plain text +#: mobile-manual.txt:229 +msgid "" +"In the dive management subpanel, tap the option _Refresh_, causing the local " +"divelog to be refreshed from the cloud so that the cloud and local versions " +"are synchronised." +msgstr "" + +#. type: Title === +#: mobile-manual.txt:230 +#, no-wrap +msgid "Changing the login credentials on the _Subsurface_ cloud" +msgstr "" + +#. type: Plain text +#: mobile-manual.txt:236 +msgid "" +"It may be necessary to change one's login credentials, for instance if one's " +"email address (initially used as a credential) has changed. To change the " +"credentials, open the main menu and tap _Cloud credentials_. This opens the " +"setup screen for specifying new credentials." +msgstr "" + +#. type: Title == +#: mobile-manual.txt:238 +#, no-wrap +msgid "Recording dive locations using GPS." +msgstr "" + +#. type: Plain text +#: mobile-manual.txt:244 +msgid "" +"The fact that most smartphones have GPS facilities allows one to record the " +"locations of dives. One can take the smartphone on the dive boat during a " +"dive and locations will be automatically recorded at regular intervals. " +"These locations can then be applied to dives in the dive list. Here is how " +"it's done:" +msgstr "" + +#. type: Title === +#: mobile-manual.txt:245 +#, no-wrap +msgid "Setting up the GPS" +msgstr "" + +#. type: Plain text +#: mobile-manual.txt:253 +msgid "" +"Open the main menu and tap _GPS -> Preferences_. Now specify the way in " +"which GPS data need to be automatically collected (image on right, " +"below). One can specify that data are collected at regular intervals, " +"e.g. every 10 minutes, or at regular distances, e.g. after the boat has " +"moved more than 200m, or a combination of both of the above " +"approaches. Provide the appropriate information and tap the _Save_ action " +"button. The program is now ready to collect GPS positions." +msgstr "" + +#. type: Target for macro image +#: mobile-manual.txt:254 +#, no-wrap +msgid "mobile-images/gpssetup.jpg" +msgstr "" + +#. type: Title === +#: mobile-manual.txt:256 +#, no-wrap +msgid "Collecting GPS positions" +msgstr "" + +#. type: Plain text +#: mobile-manual.txt:265 +msgid "" +"Ensure that the GPS on the Android device has been activated. At the bottom " +"of the GPS submenu is a check box _Run location service_ (image on left, " +"above). Check this box and _Subsurface-mobile_ starts to collect GPS " +"locations automatically, following the preferences specified as described " +"above. After the dive one can deactivate the collection of GPS data by " +"de-activating the same check box at the bottom of the main menu." +msgstr "" + +#. type: Title === +#: mobile-manual.txt:266 +#, no-wrap +msgid "Storing the GPS data on the _Subsurface_ cloud" +msgstr "" + +#. type: Plain text +#: mobile-manual.txt:273 +msgid "" +"Activate the main menu and select the _GPS_ option that brings up the " +"submenu of GPS-related actions (image on left, above). Tap _Upload GPS data_ " +"that saves the GPS data on the _Subsurface_ cloud server. These GPS data are " +"saved *separately* from the other dive log data. All collected GPS data are " +"kept on the Android device, independent of whether they have been uploaded " +"or not." +msgstr "" + +#. type: Title === +#: mobile-manual.txt:274 +#, no-wrap +msgid "Downloading GPS data from the _Subsurface_ cloud" +msgstr "" + +#. type: Plain text +#: mobile-manual.txt:278 +msgid "" +"Download the GPS data that have been saved on the cloud by selecting " +"_Download GPS Data_ from the GPS subpanel." +msgstr "" + +#. type: Title === +#: mobile-manual.txt:279 +#, no-wrap +msgid "Viewing GPS data" +msgstr "" + +#. type: Plain text +#: mobile-manual.txt:290 +msgid "" +"From the GPS submenu (image on left, above) select _Show GPS fixes_. This " +"brings up a list of GPS positions obtained using the location service (image " +"on left, below). Two actions are possible for each of the locations, enabled " +"if one taps the handle (the three horisontal stripes on the right, see image " +"on left, below) and then drags the specific item to the left (image on " +"right, below). This exposes two options. Tapping the dustbin deletes this " +"particular GPS location. Tapping the teardrop-shaped icon (actually a Google " +"Maps pin) opens up Google Maps with a pin indicating the exact map position " +"of the GPS record being viewed. The two above options can be hidden by " +"drawing the GPS record to the right, again using the handle." +msgstr "" + +#. type: Target for macro image +#: mobile-manual.txt:291 +#, no-wrap +msgid "mobile-images/gpsmanagement.jpg" +msgstr "" + +#. type: Title === +#: mobile-manual.txt:293 +#, no-wrap +msgid "Applying GPS data to dives in the dive log" +msgstr "" + +#. type: Plain text +#: mobile-manual.txt:301 +msgid "" +"Assuming that all the dives have been entered into the dive log or have been " +"downloaded from the _Subsurface_ cloud, one can apply the GPS positions to " +"these dives. GPS positions can therefore only be applied to dives in the " +"dive list. From the GPS subpanel, tap _Apply GPS fixes_. The dive list " +"contains the start and end times of each dive. Now, _Subsurface-mobile_ " +"applies the first GPS position that falls within the dive period of each " +"dive. This results in a GPS position for each dive that is saved as part of " +"the dive list." +msgstr "" diff --git a/Documentation/50-pot/subsurface-manual.pot b/Documentation/50-pot/subsurface-user-manual.pot index 934925a38..5165de7ae 100644 --- a/Documentation/50-pot/subsurface-manual.pot +++ b/Documentation/50-pot/subsurface-user-manual.pot @@ -8,7 +8,7 @@ msgid "" msgstr "" "Project-Id-Version: subsurface-manual VERSION\n" "Report-Msgid-Bugs-To: subsurface@subsurface-divelog.org\n" -"POT-Creation-Date: 2015-10-29 10:38+0100\n" +"POT-Creation-Date: 2016-03-12 13:31+0100\n" "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" "Last-Translator: FULL NAME <EMAIL@ADDRESS>\n" "Language-Team: LANGUAGE <LL@li.org>\n" @@ -19,18 +19,18 @@ msgstr "" #. :website: http://subsurface-divelog.org #. type: Target for macro image -#: ./user-manual.txt:14 +#: user-manual.txt:14 #, no-wrap msgid "images/Subsurface4Banner.jpg" msgstr "" #. type: Plain text -#: ./user-manual.txt:17 +#: user-manual.txt:17 msgid "[big]#USER MANUAL#" msgstr "" #. type: Plain text -#: ./user-manual.txt:20 +#: user-manual.txt:20 #, no-wrap msgid "" "*Manual authors*: Willem Ferguson, Jacco van Koll, Dirk Hohndel, Reinout " @@ -40,72 +40,67 @@ msgid "" msgstr "" #. type: Plain text -#: ./user-manual.txt:22 +#: user-manual.txt:22 msgid "[blue]#_Version 4.5, October 2015_#" msgstr "" #. type: Plain text -#: ./user-manual.txt:28 +#: 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 " +"extensive infrastructure to describe, organize, interpret and print scuba " "and free dives. _Subsurface_ offers many advantages over other similar " "software solutions:" msgstr "" #. type: Plain text -#: ./user-manual.txt:31 +#: user-manual.txt:31 msgid "" "Do you need a flexible way of logging dives using recreational equipment, " -"even not using a dive computer?" +"even without a dive computer?" msgstr "" #. type: Plain text -#: ./user-manual.txt:37 +#: 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 " +"time-depth recorder along with a dive computer? _Subsurface_ offers a " +"standard interface for downloading dive logs from all of these different " +"pieces of equipment, storing and analyzing the dive logs within a unified " "system." msgstr "" #. type: Plain text -#: ./user-manual.txt:40 +#: 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." +"with Mac, Linux and Windows, letting you access your dive log on each " +"operating system using a single application." msgstr "" #. type: Plain text -#: ./user-manual.txt:43 +#: user-manual.txt:43 msgid "" -"Do you use Linux or Mac and your dive computer has only Windows-based " +"Do you use Linux or Mac, but 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 " +"provides a way of downloading and analyzing your dive logs on other " "operating systems." msgstr "" #. type: Plain text -#: ./user-manual.txt:45 +#: 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?" +"Do you need an intuitive graphical dive planner that integrates with, and " +"takes into account, dives you’ve already logged?" msgstr "" #. type: Plain text -#: ./user-manual.txt:47 +#: user-manual.txt:51 msgid "" "Do you need a way of storing or backing up your dive log on the Internet, " -"allowing you to view your dive log from anywhere, using an Internet browser?" -msgstr "" - -#. type: Plain text -#: ./user-manual.txt:52 -msgid "" +"letting you view your dive log from anywhere using an Internet browser? " "_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 " @@ -113,10 +108,10 @@ msgid "" msgstr "" #. type: Plain text -#: ./user-manual.txt:61 +#: user-manual.txt:60 msgid "" -"The scope of this document is the use of the _Subsurface_ program. To " -"install the software, consult the _Downloads_ page on the " +"This manual explains how to use 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 " @@ -126,7 +121,7 @@ msgid "" msgstr "" #. type: Plain text -#: ./user-manual.txt:64 +#: user-manual.txt:63 #, no-wrap msgid "" "*Audience*: Recreational Scuba Divers, Free Divers, Tec Divers, " @@ -135,18 +130,18 @@ msgid "" msgstr "" #. type: Plain text -#: ./user-manual.txt:66 +#: user-manual.txt:65 msgid "toc::[]" msgstr "" #. type: Title - -#: ./user-manual.txt:69 +#: user-manual.txt:68 #, no-wrap msgid "Using this manual" msgstr "" #. type: Plain text -#: ./user-manual.txt:72 +#: user-manual.txt:71 msgid "" "When opened from within _Subsurface_, this manual does not have external " "controls for paging or selecting previous pages. However, two facilities are " @@ -154,69 +149,65 @@ msgid "" msgstr "" #. type: Plain text -#: ./user-manual.txt:79 +#: user-manual.txt:78 msgid "" "The _SEARCH_ function is activated by pressing control-F or command-F on the " "keyboard. A text box appears at the bottom right-hand of the window (see " -"image below). For instance, if one typed the word \"_weights_\" into the " -"search text box, this word will be searched for throughout this user " -"manual. To the right of the search text box are two arrows pointing upwards " -"and downwards. Selecting these allow finding, respectively, the previous and " -"the next occurence of the term being searched for." +"image below). For instance, typing the word \"_weights_\" into the search " +"text box, searches throughout the user manual. To the right of the search " +"text box are two arrows pointing up and down. These find the previous and " +"the next occurrence of the search term." msgstr "" #. type: Target for macro image -#: ./user-manual.txt:80 +#: user-manual.txt:78 #, no-wrap msgid "images/usermanualfunctions.jpg" msgstr "" #. type: Plain text -#: ./user-manual.txt:91 +#: user-manual.txt:90 msgid "" -"_PREVIOUS/NEXT LINK_. One can move between links (underlined words allowing " -"one to jump to specific sections in this user manual) by right-clicking on " -"the text of the manual. This brings up a context menu for jumping to " -"previous links selected while reading the manual (see image above). For " -"instance if a link in the manual has been selected, then the option to _Go " -"Back_ shows the text at the last link that was selected (similar to the " -"Previous Page button in a browser). Conversely the _Go Forward_ option " -"enables jumping to the text perused before selecting the _Go Back_ " -"option. The _Reload_ option causes the complete user manual to be reloaded " -"into the user manual window." +"_PREVIOUS/NEXT LINK_. Move between links (underlined words that jump to " +"specific sections in the user manual) by right-clicking on the text of the " +"manual. This brings up a context menu to previous links selected. (see " +"image above). For instance if a link has been selected, then the option to " +"_Go Back_ shows the text at the last link selected (similar to the Previous " +"Page button in a browser). Conversely the _Go Forward_ option jumps to the " +"text seen before selecting the _Go Back_ option. The _Reload_ option reloads " +"the complete user manual into the window." msgstr "" #. type: Title - -#: ./user-manual.txt:94 +#: user-manual.txt:92 #, no-wrap msgid "The user survey" msgstr "" #. type: Plain text -#: ./user-manual.txt:106 +#: user-manual.txt:103 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." +"In order to develop _Subsurface_ to serve its users in the best possible " +"way, it’s important to have user information. Upon launching _Subsurface_ " +"and using the 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. All data the user sends is useful, and " +"will only be used to steer future development and to customize the software " +"to fit the needs of the _Subsurface_ users. If you complete the survey, or " +"click the option not to be asked again, that should be the last " +"communication of this type you receive. However, if your diving and/or " +"subsurface habits change and you wish to fill in another survey, just launch " +"_Subsurface_ with the _--survey_ option on the command line." msgstr "" #. type: Title - -#: ./user-manual.txt:109 +#: user-manual.txt:106 #, no-wrap msgid "Start Using the Program" msgstr "" #. type: Plain text -#: ./user-manual.txt:114 +#: user-manual.txt:111 msgid "" "The _Subsurface_ window is usually divided into four panels with a *Main " "Menu* (File Import Log View Help) at the top of the window (for Windows and " @@ -225,92 +216,90 @@ msgid "" msgstr "" #. type: Plain text -#: ./user-manual.txt:120 +#: user-manual.txt:117 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." +"The *Dive List* on the bottom left, showing 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:124 +#: user-manual.txt:120 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*." +"The *Dive Map* on the bottom right, showing the user's dive sites on a world " +"map and centered on the site of the last dive selected in the *Dive List*." msgstr "" #. type: Plain text -#: ./user-manual.txt:128 +#: user-manual.txt:124 msgid "" -"The *Info* to the top left, giving more detailed information on the dive " +"The *Info* on 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:131 +#: user-manual.txt:127 msgid "" -"The *Dive Profile* to the top right, showing a graphical dive profile of the " +"The *Dive Profile* on the top right, showing a graphical dive profile of the " "selected dive in the *Dive List*." msgstr "" #. type: Plain text -#: ./user-manual.txt:136 +#: user-manual.txt:131 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." +"The dividers between panels can be dragged 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 the last " +"time the program was used." msgstr "" #. type: Plain text -#: ./user-manual.txt:144 +#: user-manual.txt:139 msgid "" "If a single 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 several dives are selected, the last " -"highlighted dive is the _selected dive_, but summary data of all " -"_highlighted dives_ are shown in the *Stats* tab of the *Info* panel " -"(maximum, minimum and average depths, durations, water temperatures and SAC; " -"total time and number of dives selected)." +"panels. If several dives are selected, the last highlighted dive is the " +"_selected dive_, but summary data of all _highlighted dives_ is shown in the " +"*Stats* tab of the *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:147 +#: user-manual.txt:142 #, no-wrap msgid "images/main_window_f22.jpg" msgstr "" #. type: Plain text -#: ./user-manual.txt:152 +#: user-manual.txt:146 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:" +"The user decides which of the four panels are displayed by selecting the " +"*View* option on the main menu. This feature has several choices of display:" msgstr "" #. type: Plain text -#: ./user-manual.txt:154 +#: user-manual.txt:148 #, no-wrap msgid "*All*: show all four of the panels as in the screenshot above.\n" msgstr "" #. type: Plain text -#: ./user-manual.txt:156 +#: user-manual.txt:150 #, no-wrap msgid "*Divelist*: Show only the Dive List.\n" msgstr "" #. type: Plain text -#: ./user-manual.txt:158 +#: user-manual.txt:152 #, no-wrap msgid "*Profile*: Show only the Dive Profile of the selected dive.\n" msgstr "" #. type: Plain text -#: ./user-manual.txt:161 +#: user-manual.txt:155 #, no-wrap msgid "" "*Info*: Show only the Notes about the last selected dive and statistics " @@ -319,91 +308,90 @@ msgid "" msgstr "" #. type: Plain text -#: ./user-manual.txt:163 +#: user-manual.txt:157 #, no-wrap -msgid "*Globe*: Show only the world map, centred on the last selected dive.\n" +msgid "*Globe*: Show only the world map, centered on the last selected dive.\n" msgstr "" #. type: Plain text -#: ./user-manual.txt:169 +#: user-manual.txt:163 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 " +"Like other functions that can be accessed via the Main Menu, these options " +"can also 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." +"entries. Since different Operating Systems and the user’s chosen language " +"may cause _Subsurface_ to use different shortcut keys, they are not listed " +"in this user manual." msgstr "" #. type: Plain text -#: ./user-manual.txt:173 +#: user-manual.txt:167 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." +"all, because it does not have any dive information available. In the " +"following sections, the procedures to create a new logbook will be " +"explained." msgstr "" #. type: Title - -#: ./user-manual.txt:176 +#: user-manual.txt:170 #, no-wrap msgid "Creating a new logbook" msgstr "" #. type: Plain text -#: ./user-manual.txt:181 +#: user-manual.txt:175 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 " +"cleared so 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:183 +#: user-manual.txt:177 #, no-wrap msgid "Storing dive information in the logbook" msgstr "" #. type: Plain text -#: ./user-manual.txt:188 +#: user-manual.txt:180 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." +"Now that a new logbook is created, it is simple to add dive data it. " +"_Subsurface_ allows several ways of adding dive data to a logbook." msgstr "" #. type: Plain text -#: ./user-manual.txt:190 +#: user-manual.txt:181 msgid "If the user has a handwritten divelog, a spreadsheet or another form of" msgstr "" #. type: Plain text -#: ./user-manual.txt:192 +#: user-manual.txt:183 msgid "" "manually maintained divelog, dive data can be added to the logbook using one " "of these approaches:" msgstr "" #. type: Plain text -#: ./user-manual.txt:194 -msgid "Enter dive information by hand. This is useful if the diver did not" +#: user-manual.txt:184 +msgid "Enter dive information by hand. This is useful if the diver didn’t" msgstr "" #. type: Plain text -#: ./user-manual.txt:196 +#: user-manual.txt:186 msgid "" "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:198 +#: user-manual.txt:188 msgid "Import dive log information that has been maintained either as a spreadsheet" msgstr "" #. type: Plain text -#: ./user-manual.txt:200 +#: user-manual.txt:190 msgid "" "or as a CSV file. Refer to: xref:S_Appendix_D[APPENDIX D: Exporting a " "spreadsheet to CSV format] and to xref:S_ImportingCSVDives[Importing dives " @@ -411,294 +399,288 @@ msgid "" msgstr "" #. type: Plain text -#: ./user-manual.txt:202 -msgid "If one has dives recorded using a dive computer, the depth profile of the" -msgstr "" - -#. type: Plain text -#: ./user-manual.txt:204 +#: user-manual.txt:193 msgid "" -"dive and a large amount of additional information can be accessed. These " -"dives can be imported from:" +"If a dive is recorded using a dive computer, the depth profile and a large " +"amount of additional information can be accessed. These dives can be " +"imported from:" msgstr "" #. type: Plain text -#: ./user-manual.txt:206 +#: user-manual.txt:194 msgid "" "The dive computer itself. See: xref:S_ImportDiveComputer[Importing new dive " "information from a Dive Computer] or" msgstr "" #. type: Plain text -#: ./user-manual.txt:208 +#: user-manual.txt:196 msgid "Proprietary software distributed by manufacturers of dive computers. Refer" msgstr "" #. type: Plain text -#: ./user-manual.txt:209 +#: user-manual.txt:197 msgid "" "to: xref:S_ImportingAlienDiveLogs[Importing dive information from other " "digital data sources or other data formats]." msgstr "" #. type: Plain text -#: ./user-manual.txt:211 -msgid "Import from spreadsheet or CSV files containing dive profiles." +#: user-manual.txt:198 +msgid "Spreadsheet or CSV files containing dive profiles." msgstr "" #. type: Plain text -#: ./user-manual.txt:212 +#: user-manual.txt:199 msgid "" "See: xref:S_ImportingCSVDives[Importing dives in CSV format from dive " "computers or other dive log software]" msgstr "" #. type: Title === -#: ./user-manual.txt:215 +#: user-manual.txt:202 #, no-wrap msgid "Entering dive information by hand" msgstr "" #. type: Plain text -#: ./user-manual.txt:229 +#: user-manual.txt:217 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 " +"duration, depth, the names of your dive buddy and 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 *Info* panel " -"(*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." +"information for each dive. To add a dive to a dive log, select _Log -> Add " +"Dive_ from the Main Menu. The program then shows three panels on which to " +"enter information for a dive: two tabs in the *Info* panel (*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:230 +#: user-manual.txt:218 #, no-wrap msgid "images/AddDive1_f22.jpg" msgstr "" #. type: Plain text -#: ./user-manual.txt:235 +#: user-manual.txt:222 msgid "" -"When one edits a field in Notes or Equipment panels, _Subsurface_ enters " +"When you edit a field in Notes or Equipment panels, _Subsurface_ enters " "*Editing Mode*, indicated by the message in the blue box at the top of the " "*Notes* panel (see the image below). This message is displayed in all the " "panels under Notes and Equipment when in *Editing Mode*." msgstr "" #. type: Target for macro image -#: ./user-manual.txt:236 ./user-manual.txt:807 +#: user-manual.txt:223 user-manual.txt:782 #, no-wrap msgid "images/BlueEditBar_f22.jpg" msgstr "" #. type: Plain text -#: ./user-manual.txt:243 +#: user-manual.txt:231 msgid "" "The _Apply changes_ 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 _Apply changes_ 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." +"information for this specific dive is saved in memory. The _Apply changes_ " +"button should ONLY be selected after all parts of a dive have been " +"entered. When you close 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:245 +#: user-manual.txt:233 #, no-wrap msgid "Creating a Dive Profile" msgstr "" #. type: Plain text -#: ./user-manual.txt:252 +#: user-manual.txt:240 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 " +"function of time) is shown 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:" +"best represent the dive described:" msgstr "" #. type: Target for macro image -#: ./user-manual.txt:253 +#: user-manual.txt:241 #, no-wrap msgid "images/DiveProfile1_f20.jpg" msgstr "" #. type: Plain text -#: ./user-manual.txt:271 +#: user-manual.txt:259 msgid "" "_Modifying the dive profile_: When the cursor is moved around the dive " -"profile, its position is indicated by two right-angled red lines as shown " -"below. The time and depth represented by the cursor 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. Drag the waypoints to represent an accurate time duration for the " -"dive. Below is a dive profile for a dive to 20 m for 30 min, followed by a 5 " -"minute safety stop at 5 m." +"profile, its position is shown by two right-angled red lines as seen below. " +"The time and depth represented by the cursor 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 you need to drag the appropriate waypoints downward to 20 m. To add a " +"waypoint, double-click on any line segment. To move an additional waypoint, " +"drag it. To remove a waypoint, right-click on it and choose \"Remove this " +"point\" from the context menu. Drag the waypoints to represent an accurate " +"time duration for the dive. Below is a dive profile for 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:272 +#: user-manual.txt:260 #, no-wrap msgid "images/DiveProfile2_f20.jpg" msgstr "" #. type: Plain text -#: ./user-manual.txt:284 +#: user-manual.txt:272 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 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 (see image below)." +"_Specifying the gas composition:_ The gas composition used is 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 above. The gas mixtures of segments of the dive profile can be " +"changed 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 (see image below)." msgstr "" #. type: Target for macro image -#: ./user-manual.txt:285 +#: user-manual.txt:273 #, no-wrap msgid "images/DiveProfile3_f20.jpg" msgstr "" #. type: Plain text -#: ./user-manual.txt:292 +#: user-manual.txt:280 msgid "" -"With the profile having been defined, more details must be added in order to " -"have a fuller record of the dive. To do this, the *Notes* and the " -"*Equipment* tabs on the top left hand of the _Subsurface_ window should be " -"used. Click on xref:S_Notes_dc[*this link*] for instructions to use these " -"tabs." +"With the profile now defined, more details must be added to have a fuller " +"record of the dive. To do this, the *Notes* and the *Equipment* tabs on the " +"top left hand of the _Subsurface_ window should be used. Click on " +"xref:S_Notes_dc[*this link*] for instructions on how to use these tabs." msgstr "" #. type: Title === -#: ./user-manual.txt:294 +#: user-manual.txt:281 #, no-wrap msgid "Importing new dive information from a Dive Computer" msgstr "" #. type: Title ==== -#: ./user-manual.txt:296 +#: user-manual.txt:283 #, no-wrap msgid "Connecting and importing data from a dive computer." msgstr "" #. type: Plain text -#: ./user-manual.txt:307 +#: user-manual.txt:293 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: " +"capture this information, using dive details 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:308 ./user-manual.txt:676 ./user-manual.txt:3061 +#: user-manual.txt:294 user-manual.txt:654 user-manual.txt:3026 #, no-wrap msgid "images/icons/warning2.png" msgstr "" #. type: Plain text -#: ./user-manual.txt:319 +#: user-manual.txt:304 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." +"Several dive computers consume more power when they are in PC-Communication " +"mode. **This could drain the dive computer's battery**. We recommend the " +"user checks to be sure 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:335 +#: user-manual.txt:320 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. " +"_Subsurface_, the two pieces of equipment must 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. To set up this communication, users need 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 " +"A] provides the technical information to help the user achieve 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:338 +#: user-manual.txt:322 msgid "" -"After this, the dive computer can be hooked up to the user's PC, which can " -"be achieved by following these steps:" +"After this, the dive computer can be hooked up to the user's PC using these " +"steps:" msgstr "" #. type: Plain text -#: ./user-manual.txt:340 +#: user-manual.txt:324 msgid "The interface cable should be connected to a free USB port (or the Infra-red" msgstr "" #. type: Plain text -#: ./user-manual.txt:341 +#: user-manual.txt:325 msgid "or Bluetooth connection set up as described later in this manual)" msgstr "" #. type: Plain text -#: ./user-manual.txt:343 +#: user-manual.txt:327 msgid "The dive computer should be placed into PC Communication mode." msgstr "" #. type: Plain text -#: ./user-manual.txt:344 +#: user-manual.txt:328 msgid "(Refer to the manual of the specific dive computer)" msgstr "" #. type: Plain text -#: ./user-manual.txt:348 +#: user-manual.txt:332 msgid "" "In _Subsurface_, from the Main Menu, select _Import -> Import From Dive " "Computer_. Dialogue *A* in the figure below appears:" msgstr "" #. type: Target for macro image -#: ./user-manual.txt:350 +#: user-manual.txt:334 #, no-wrap msgid "images/DC_import_f20.jpg" msgstr "" #. type: Plain text -#: ./user-manual.txt:358 +#: user-manual.txt:342 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, if the dive computer allows this, _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)." +"Dive computers tend to keep a certain number of dives in memory, even though " +"these dives have already been imported to _Subsurface_. For that reason, if " +"the dive computer allows this, _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)." msgstr "" #. type: Plain text -#: ./user-manual.txt:365 +#: user-manual.txt:349 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, " @@ -708,7 +690,7 @@ msgid "" msgstr "" #. type: Plain text -#: ./user-manual.txt:376 +#: user-manual.txt:360 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 " @@ -717,20 +699,19 @@ msgid "" "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." +"a specific 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:386 +#: user-manual.txt:370 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 " +"panel. If one or more of your dives in _Subsurface_ has 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 " +"the dive computer, this box needs to be checked. 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 " @@ -738,60 +719,60 @@ msgid "" msgstr "" #. type: Plain text -#: ./user-manual.txt:392 +#: user-manual.txt:376 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 dive in the _Subsurface_ " -"divelog will be overwritten by the dive record from the dive computer." +"divelog will be overwritten by the dive record from the computer." msgstr "" #. type: Plain text -#: ./user-manual.txt:395 +#: user-manual.txt:379 msgid "" "The checkbox marked _Download into new trip_ ensures that, after upload, the " "downloaded dives are grouped together as a new trip(s) in the *Dive List*." msgstr "" #. type: Plain text -#: ./user-manual.txt:399 +#: user-manual.txt:383 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)." +"when there are problems with downloads(see below)." msgstr "" #. type: Plain text -#: ./user-manual.txt:419 +#: user-manual.txt:402 msgid "" -"Then select the _Download_ button. With communication established, one can " +"Then select the _Download_ button. With communication established, you 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. 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). After successful download, Dialogue " -"*B* in the figure above appears. After the dives have been downloaded, they " -"appear in a tabular format on the right-hand side of the dialogue (see image " -"*B*, above). Each dive comprises a row in the table, with the date, duration " -"and depth shown. Next to each dive is a checkbox: check all the dives that " -"need to be transferred to the *Dive List*. In the case of the image above, " -"the last six dives are checked and will be transferred to the *Dive " -"List*. Then click the _OK_ button at the bottom of the dialogue. 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." +"bottom of the dialogue. Remember for some dive computers progress " +"information could be inaccurate since the program doesn’t know how much " +"downloadable data there is until the download is complete. After successful " +"download, Dialogue *B* in the figure above appears. After the dives have " +"been downloaded, they appear in a tabular format on the right-hand side of " +"the dialogue (see image *B*, above). Each dive comprises a row in the table, " +"with the date, duration and depth shown. Next to each dive is a checkbox: " +"check all the dives that need to be transferred to the *Dive List*. In the " +"case of the image above, the last six dives are checked and will be " +"transferred to the *Dive List*. Then click the _OK_ button at the bottom of " +"the dialogue. 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." msgstr "" #. type: Plain text -#: ./user-manual.txt:424 +#: user-manual.txt:407 msgid "" -"After this has been completed, select the OK button. The checked dives are " -"transferred to the *Dive List*." +"Then click the OK button. The checked dives are transferred to the *Dive " +"List*." msgstr "" #. type: Plain text -#: ./user-manual.txt:428 +#: user-manual.txt:411 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 " @@ -799,52 +780,52 @@ msgid "" msgstr "" #. type: delimited block * -#: ./user-manual.txt:432 +#: user-manual.txt:415 #, no-wrap msgid "*PROBLEMS WITH DATA DOWNLOAD FROM A DIVE COMPUTER?*\n" msgstr "" #. type: Named 'icon' AttributeList argument for style 'icon' -#: ./user-manual.txt:432 ./user-manual.txt:542 ./user-manual.txt:586 ./user-manual.txt:599 ./user-manual.txt:1176 ./user-manual.txt:1242 ./user-manual.txt:1295 ./user-manual.txt:1371 ./user-manual.txt:1685 +#: user-manual.txt:415 user-manual.txt:521 user-manual.txt:565 user-manual.txt:578 user-manual.txt:1149 user-manual.txt:1215 user-manual.txt:1266 user-manual.txt:1342 user-manual.txt:1653 #, no-wrap msgid "images/icons/important.png" msgstr "" #. type: delimited block * -#: ./user-manual.txt:435 +#: user-manual.txt:418 msgid "Check the following:" msgstr "" #. type: delimited block * -#: ./user-manual.txt:438 +#: user-manual.txt:421 msgid "Is the dive computer still in PC-communication or Upload mode?" msgstr "" #. type: delimited block * -#: ./user-manual.txt:441 +#: user-manual.txt:423 msgid "" -"Is the battery of the dive computer fully charged? If not then the battery " -"must be charged or replaced." +"Is the dive computer’s battery fully charged? If not then charge or replace " +"it." msgstr "" #. type: delimited block * -#: ./user-manual.txt:445 +#: user-manual.txt:427 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?" +"Is the connecting cable faulty? Does the cable work 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:450 +#: user-manual.txt:432 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)." +"A] to be sure the correct Mount Point was specified (see above)." msgstr "" #. type: delimited block * -#: ./user-manual.txt:454 +#: user-manual.txt:436 msgid "" "On Unix-like operating systems, does the user have write permission to the " "USB port? If not, consult " @@ -853,20 +834,19 @@ msgid "" msgstr "" #. type: delimited block * -#: ./user-manual.txt:462 +#: user-manual.txt:444 msgid "" -"If the _Subsurface_ computer does not recognise the USB adaptor by showing " +"If the _Subsurface_ computer does not recognize 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:" +"possibility the cable or USB adaptor is faulty. A faulty cable is the most " +"common cause of communication failure between a dive computer and " +"_Subsurface_ computer. It’s also possible the _Subsurface_ computer cannot " +"interpret the data. Perform a download for diagnostic purposes with the " +"following two boxes checked in the download dialogue discussed above:" msgstr "" #. type: delimited block * -#: ./user-manual.txt:465 +#: user-manual.txt:447 #, no-wrap msgid "" "\tSave libdivecomputer logfile\n" @@ -874,20 +854,20 @@ msgid "" msgstr "" #. type: delimited block * -#: ./user-manual.txt:471 +#: user-manual.txt:453 #, 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 " +"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 " +"When checking these boxes, the user is prompted to select a folder where the " +"information will be saved. The default folder is the one in which the\n" "_Subsurface_\n" "dive log is kept.\n" msgstr "" #. type: delimited block * -#: ./user-manual.txt:475 +#: user-manual.txt:457 #, no-wrap msgid "" "*Important:* _After downloading with the above checkboxes\n" @@ -896,7 +876,7 @@ msgid "" msgstr "" #. type: delimited block * -#: ./user-manual.txt:478 +#: user-manual.txt:460 #, no-wrap msgid "" "\tsubsurface.log\n" @@ -904,133 +884,113 @@ msgid "" msgstr "" #. type: delimited block * -#: ./user-manual.txt:484 +#: user-manual.txt:466 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 " +"analyzed. 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:487 +#: user-manual.txt:469 #, no-wrap msgid "Connecting _Subsurface_ to a Bluetooth-enabled dive computer" msgstr "" #. type: Named 'icon' AttributeList argument for style 'icon' -#: ./user-manual.txt:488 ./user-manual.txt:3606 +#: user-manual.txt:470 user-manual.txt:3578 #, no-wrap msgid "images/icons/bluetooth.jpg" msgstr "" #. type: Plain text -#: ./user-manual.txt:495 +#: user-manual.txt:477 msgid "" "Bluetooth is becoming a more common way of communication between dive " -"computers and _Subsurface_, for instance, the Shearwater Petrel Mk2 and the " -"OSTC Mk3. _Subsurface_ provides a largely operating system independent " +"computers and _Subsurface_, for or instance, the Shearwater Petrel Mk2 and " +"the OSTC Mk3. _Subsurface_ provides a largely operating system independent " "Bluetooth interface. Setting up _Subsurface_ for Bluetooth communication " "requires four steps:" msgstr "" #. type: Plain text -#: ./user-manual.txt:497 -msgid "" -"Ensure that Bluetooth is activated on the host computer running " -"_Subsurface_." +#: user-manual.txt:479 +msgid "Be sure Bluetooth is activated on the host computer running _Subsurface_." msgstr "" #. type: Plain text -#: ./user-manual.txt:498 -msgid "Ensure that _Subsurface_ sees the Bluetooth adapter on the host computer." +#: user-manual.txt:480 +msgid "Be sure _Subsurface_ sees the Bluetooth adapter on the host computer." msgstr "" #. type: Plain text -#: ./user-manual.txt:499 +#: user-manual.txt:481 msgid "" -"Ensure the Bluetooth-enabled dive computer is Bluetooth-discoverable and in " +"Be sure the Bluetooth-enabled dive computer is Bluetooth-discoverable and in " "PC upload mode." msgstr "" #. type: Plain text -#: ./user-manual.txt:500 -msgid "Ensure that _Subsurface_ is paired with the Bluetooth-enabled dive computer." +#: user-manual.txt:482 +msgid "Be sure _Subsurface_ is paired with the Bluetooth-enabled dive computer." msgstr "" #. type: Plain text -#: ./user-manual.txt:504 +#: user-manual.txt:486 msgid "" "Select the Download dialogue by selecting _Import -> Import from dive " -"computer_ from the *Main Menu*. If one checks the check box labelled " -"_\"Choose Bluetooth download mode\"_, the dialogue below appears." +"computer_ from the *Main Menu*. If you check the box labelled _\"Choose " +"Bluetooth download mode\"_, the dialogue below appears." msgstr "" #. type: Title ===== -#: ./user-manual.txt:505 +#: user-manual.txt:486 #, no-wrap msgid "On Linux or MacOS:" msgstr "" #. type: Target for macro image -#: ./user-manual.txt:507 +#: user-manual.txt:488 #, no-wrap msgid "images/DC_import_Bluetooth.jpg" msgstr "" #. type: Plain text -#: ./user-manual.txt:515 +#: user-manual.txt:519 msgid "" "On the _Linux_ or _MacOS_ platforms the name of the _Subsurface_ computer " -"and its Bluetooth address are shown on the right-hand side, On the lefthand " +"and its Bluetooth address are shown on the right hand side, On the left hand " "side, if the computer has connected more than one local Bluetooth devices " "the user can use the list box to indicate which one needs to connect to " "_Subsurface_. The power state (on/off) of the Bluetooth adapter is shown " -"below the address and can be changed by checking the _Turn on/off_ check " -"box." -msgstr "" - -#. type: Plain text -#: ./user-manual.txt:520 -msgid "" -"If the Bluetooth address is not shown, then _Subsurface_ does not see the " -"local Bluetooth device. Ensure that the Bluetooth driver is installed " -"correctly on the _Subsurface_ computer and check if it can be used by other " -"Bluetooth utilities like _bluetoothctl_ or _bluemoon_. This achieves the " -"first two steps above." -msgstr "" - -#. type: Plain text -#: ./user-manual.txt:524 -msgid "" -"Ensure that the Bluetooth-enabled dive computer is in PC-upload mode and " -"that it is discoverable by other Bluetooth devices. Consult the manual of " -"the dive computer to perform this. Now the third item in the list above has " -"been achieved." -msgstr "" - -#. type: Plain text -#: ./user-manual.txt:540 -msgid "" -"Select the _Scan_ button towards the bottom left of the dialogue " -"above. After searching for a small amount of time, the dive computer should " -"be listed (perhaps as one of a number of Bluetooth devices) in the main list " -"box on the lefthand side of the dialogue (see image above). If this is not " -"achieved, select the _Clear_ button and then scan again for Bluetooth " -"devices using the _Scan_ button. After performing these actions _Subsurface_ " -"should see the dive computer. The label of the discovered dive computer " -"contains the name of the device, its address and its pairing status. If the " -"device is not paired and has a red background colour, a context menu can be " -"opened by selecting the item with a right-click. Select the the _Pair_ " -"option and wait for the task to complete. If this dive computer is being " -"paired to Subsurface for the first time, it is possible that Subsurface will " -"request a Pass Code or PIN number. The most commonly-used Pass Code is 0000, " -"and this works for the Shearwater Petrel. If necessary, consult the user " -"manual of the dive computer being used." +"below the address and can be changed by checking the _Turn on/off_ box. If " +"the Bluetooth address is not shown, then _Subsurface_ does not see the local " +"Bluetooth device. Be sure the Bluetooth driver is installed correctly on the " +"_Subsurface_ computer and check if it can be used by other Bluetooth " +"utilities like _bluetoothctl_ or _bluemoon_. This finishes the first two " +"steps above. Be sure the Bluetooth-enabled dive computer is in PC-upload " +"mode and it is discoverable by other Bluetooth devices. Consult the manual " +"of the dive computer for more information. Now the third item in the list " +"above has been finished. Select the _Scan_ button towards the bottom left " +"of the dialogue above. After searching, the dive computer should be listed " +"(perhaps as one of a number of Bluetooth devices) in the main list box on " +"the lefthand side of the dialogue (see image above). If this does not work, " +"select the _Clear_ button, then scan again for Bluetooth devices using the " +"_Scan_ button. After taking these actions _Subsurface_ should see the dive " +"computer. The label of the discovered dive computer contains the name of " +"the device, its address and its pairing status. If the device is not paired " +"and has a red background color, a context menu can be opened by selecting " +"the item with a right-click. Select the the _Pair_ option and wait for the " +"task to complete. If this dive computer is being paired to Subsurface for " +"the first time, it’s possible Subsurface will request a Pass Code or PIN " +"number. The most commonly-used Pass Code is 0000, and this works for the " +"Shearwater Petrel. If necessary, consult the user manual of the dive " +"computer being used." msgstr "" #. type: delimited block * -#: ./user-manual.txt:547 +#: user-manual.txt:526 msgid "" "Currently _Subsurface_ does not support Bluetooth pairing with dive " "computers that require a custom PIN code. In order to pair the devices, use " @@ -1038,12 +998,12 @@ msgid "" msgstr "" #. type: delimited block * -#: ./user-manual.txt:549 +#: user-manual.txt:528 msgid "One way to achieve this is to use +bluetoothctl+:" msgstr "" #. type: delimited block * -#: ./user-manual.txt:560 +#: user-manual.txt:539 #, no-wrap msgid "" "\t$ bluetoothctl\n" @@ -1059,66 +1019,65 @@ msgid "" msgstr "" #. type: Plain text -#: ./user-manual.txt:566 +#: user-manual.txt:545 msgid "" -"After the devices are paired the _Save_ button of the dialogue can be " -"pressed. This closes the Bluetooth dialogue. Now select _Download_ in the " -"_Download from dive computer_ dialogue which should still be open. The " -"downloaded dives are shown on the righthand side of the download dialogue." +"After the devices are paired, press the _Save_ button of the dialogue. This " +"closes the Bluetooth dialogue. Now select _Download_ in the _Download from " +"dive computer_ dialogue which should still be open. The downloaded dives are " +"shown on the righthand side of the download dialogue." msgstr "" #. type: Title ==== -#: ./user-manual.txt:567 ./user-manual.txt:3537 ./user-manual.txt:3621 +#: user-manual.txt:546 user-manual.txt:3505 user-manual.txt:3593 #, no-wrap msgid "On Windows:" msgstr "" #. type: Target for macro image -#: ./user-manual.txt:568 +#: user-manual.txt:547 #, no-wrap msgid "images/DC_import_Bluetooth_Windows.png" msgstr "" #. type: Plain text -#: ./user-manual.txt:578 +#: user-manual.txt:557 msgid "" "On _Windows_ platforms the _Local Bluetooth device details section_ on the " -"right is not displayed as is the case on the Linux/Mac implementations. To " -"successfully initiate a scan (by pressing the _Scan_ button) check that the " -"Bluetooth device on the _Subsurface_ computer is turned on by selecting the " -"dive computer from the list of available Bluetooth devices (see image " -"above). If the dive computer is accessed by Subsurface for the first time, " -"it is possible that Subsurface will request a Pass Code/PIN number. Supply " -"the Pass Code recommended in the user manual of the dive computer. A Pass " -"Code of 0000 is often appropriate." +"right is not displayed as is the case on the Linux/Mac systems. To start a " +"scan (by pressing the _Scan_ button) check that the Bluetooth device on the " +"_Subsurface_ computer is turned on by selecting the dive computer from the " +"list of available Bluetooth devices (see image above). If the dive computer " +"is being accessed by Subsurface for the first time, it’s possible Subsurface " +"will request a Pass Code or PIN number. Supply the Pass Code recommended in " +"the user manual of the dive computer. A Pass Code or PIN of 0000 is often " +"the default." msgstr "" #. type: Plain text -#: ./user-manual.txt:585 +#: user-manual.txt:564 msgid "" "The pairing step is checked and done automatically during the download " "process. If the devices have never been paired the system will ask for your " -"permissions and put a message on the right side of the screen: _Add a " -"device, Tap to set up your DC device_. Always allow this pairing. After a " -"discovered item is selected, select the _Save_ button. Finally select the " -"_Download_ button on the _Download_ dialogue and wait for the process to " -"complete." +"permission and put a message on the right side of the screen: _Add a device, " +"Tap to set up your DC device_. Always allow this pairing. After a discovered " +"item is selected, select the _Save_ button. Finally select the _Download_ " +"button on the _Download_ dialogue and wait for the process to complete." msgstr "" #. type: Plain text -#: ./user-manual.txt:593 +#: user-manual.txt:572 msgid "" "Currently _Subsurface_ works only with local Bluetooth adapters which use " "Microsoft Bluetooth Stack. If the local device uses _Widcomm_, _Stonestreet " -"One Bluetopia Bluetooth_ or _BlueSoleil_ drivers it will definitely not " -"work. However, Bluetooth hardware/dongles from these manufacturers " -"(e.g. iSonic) that support the Microsoft Bluetooth Stack do work." +"One Bluetopia Bluetooth_ or _BlueSoleil_ drivers it will not work. However, " +"Bluetooth hardware/dongles from these manufacturers (e.g. iSonic) that " +"support the Microsoft Bluetooth Stack do work." msgstr "" #. type: Plain text -#: ./user-manual.txt:598 +#: user-manual.txt:577 msgid "" -"A log messageOn the bottom left of the _Remote Bluetooth device selection_ " +"A log message on the bottom left of the _Remote Bluetooth device selection_ " "shows details about the current status of the Bluetooth agent. To select " "another dive computer for download using the \"Remote Bluetooth selection " "dialogue\" press the three-dots button from the _\"Choose Bluetooth download " @@ -1126,7 +1085,7 @@ msgid "" msgstr "" #. type: Plain text -#: ./user-manual.txt:608 +#: user-manual.txt:587 #, no-wrap msgid "" "*IN CASE OF PROBLEMS*: If the Bluetooth adapter from the _Subsurface_ " @@ -1141,105 +1100,102 @@ msgid "" msgstr "" #. type: Title ==== -#: ./user-manual.txt:611 +#: user-manual.txt:590 #, no-wrap msgid "Changing the name of a dive computer" msgstr "" #. type: Plain text -#: ./user-manual.txt:627 +#: user-manual.txt:606 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, consider 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." +"upload dive logs to _Subsurface_. For instance if a buddy’s dive computer is " +"the same make and model as your own and dive logs are uploaded from both " +"dive computers to the same _Subsurface_ computer, then you might like to " +"call one \"Alice's Suunto D4\" and the other \"Bob's Suunto " +"D4\". Alternatively, consider a technical diver who 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 \"Suunto D4 (2)\". This is easily done in _Subsurface_. On the " +"*Main Menu*, select _Log -> Edit device names_. A dialog box opens, showing " +"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:629 +#: user-manual.txt:608 #, no-wrap msgid "Updating the dive information imported from the dive computer." msgstr "" #. type: Plain text -#: ./user-manual.txt:636 +#: user-manual.txt:615 msgid "" "With the uploaded dives in the *Dive List*, 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 *Notes* and the *Equipment* tabs " -"on the top left hand of the _Subsurface_ window should be used." +"computer is not complete and more details must be added to have a full " +"record of the dives. To do this, the *Notes* and the *Equipment* tabs on the " +"top left hand of the _Subsurface_ window should be used." msgstr "" #. type: Title ===== -#: ./user-manual.txt:638 +#: user-manual.txt:617 #, no-wrap msgid "Notes" msgstr "" #. type: Plain text -#: ./user-manual.txt:643 +#: user-manual.txt:622 msgid "" -"To have a more complete dive record the user needs to add additional " +"To have a more complete dive record, the user needs to add additional " "information by hand. The procedure below is virtually identical for " "hand-entered dives and for dives downloaded from a dive computer." msgstr "" #. type: Plain text -#: ./user-manual.txt:653 +#: user-manual.txt:632 msgid "" -"In some cases, one has to provide the date and time of the dive, e.g. when " -"entering a dive by hand or when a dive computer does not provide the date " -"and time of the dive. (Usually the date and time of the dive, gas mixture " -"and water temperature are shown as obtained from the dive computer) If the " -"contents of the *Notes 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 *Notes* tab, the following fields are visible " +"In some cases, you must provide the date and time of the dive, for example " +"when entering a dive by hand or when a dive computer doesn’t provide the " +"date and time of the dive. (Usually the date and time of the dive, gas " +"mixture and water temperature are shown as obtained from the dive computer) " +"If the contents of the *Notes tab* is changed or edited in any way, the " +"message in a blue box at the top of the panel shows the dive is being " +"edited. If you click on the *Notes* tab, the following fields are visible " "(left hand image, below):" msgstr "" #. type: Target for macro image -#: ./user-manual.txt:654 +#: user-manual.txt:633 #, no-wrap msgid "images/AddDive3_f22.jpg" msgstr "" #. type: Plain text -#: ./user-manual.txt:663 +#: user-manual.txt:642 msgid "" "The right hand image, above, shows a *Notes tab* filled with dive " "information. 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 " +"clicking the date, a calendar is displayed from which you 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 over-typing the information displayed." msgstr "" #. type: Plain text -#: ./user-manual.txt:674 +#: user-manual.txt:652 #, no-wrap msgid "" "*Air/water temperatures*: Air and water temperatures during the dive are " "shown\n" "in text boxes to the right of the Start time. Many dive computers supply " "water\n" -"temperature information and this box may therefore contain information.\n" -"If air temperature is not provided by the dive computer, the first " +"temperature information and this box may have information.\n" +"If air temperature isn’t 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" +"might be used for the air temperature. Generally this is close to the real " +"air temperature.\n" "If editing is required, only a value is required, the units of temperature " "will be\n" "automatically supplied by\n" @@ -1248,87 +1204,85 @@ msgid "" msgstr "" #. type: Plain text -#: ./user-manual.txt:676 +#: user-manual.txt:654 #, no-wrap msgid "*Location*:\n" msgstr "" #. type: Plain text -#: ./user-manual.txt:684 +#: user-manual.txt:662 msgid "" "Dive locations are managed as a *separate* part of the dive log. The dive " -"information in the *Notes* and *Equipment* tabs can therefore not be edited " +"information in the *Notes* and *Equipment* tabs can therefore NOT be edited " "at the same time as the dive site information. Save all the other dive " "information (e.g. divemaster, buddy, protective gear, notes about the dive) " -"by selecting _Apply changes_ on the *Notes* tab before editing the dive site " -"information. Only then, supply a dive site name in the textbox labelled " -"_Location_ on the *Notes* tab." +"by selecting _Apply changes_ on the *Notes* tab BEFORE editing the dive site " +"information. Then supply a dive site name in the textbox labelled _Location_ " +"on the *Notes* tab." msgstr "" #. type: Plain text -#: ./user-manual.txt:702 +#: user-manual.txt:680 msgid "" -"Type the name of the dive site, e.g. \"Tihany, Lake Balaton, Hungary\". If " -"several dives are performed at the same location, the dive site information " -"for the first dive is re-used. Existing dive location information can be " -"edited at any time by selecting (on the *Dive List* panel) a dive performed " -"at that site and by opening the location information by clicking the globe " -"button on the right of the location name (see image on the right, " -"above). When entering a dive location name, auto location of dive site names " -"makes it easy to select an existing dive site name (i.e. when typing the " -"name of a dive site, a dropdown list appears showing all sites with similar " -"names). If the dive site has been used before, click on the already-existing " -"name. The dive site names in the dropdown list contain either a globe " -"symbol (indicating existing dive sites in the _Subsurface_ database) or a " -"*+* symbol (indicating dive site names that appear consistent with the " -"current dive site name but which have not been added to the dive site " -"database). Therefore, if the present dive site has not been used before, a " -"message appears as follows (image *A* below):" +"Type in the name of the dive site, e.g. \"Tihany, Lake Balaton, Hungary\". " +"If several dives are made at the same location, the site information for the " +"first dive is re-used. Existing dive locations can be edited by selecting " +"(on the *Dive List* panel) a dive done at that site and by opening the " +"location information. Click the globe button on the right of the location " +"name (see image on the right, above). When entering a dive location name, " +"auto location of dive site names makes it easy to select an existing dive " +"site name. When typing the name of a dive site, a dropdown list appears " +"showing all sites with similar names. If the dive site has been used before, " +"click on the already-existing name. The dive site names in the dropdown " +"list contain either a globe symbol (indicating existing dive sites in the " +"_Subsurface_ database) or a *+* symbol (indicating dive site names that " +"appear consistent with the current dive site name but which haven’t been " +"added to the dive site database). If the present dive site has not been " +"used before, a message appears as follows (image *A* below):" msgstr "" #. type: Target for macro image -#: ./user-manual.txt:703 +#: user-manual.txt:681 #, no-wrap msgid "images/Locations1_f22.jpg" msgstr "" #. type: Plain text -#: ./user-manual.txt:708 +#: user-manual.txt:686 msgid "" "Doubleclick on the new dive site name. A panel appears to enter the " -"coordinates and other important information about the site (image *B*, " -"above). The most important items are the coordinates of the site. There are " -"three ways of specifying the coordinates:" +"coordinates and other information about the site (image *B*, above). The " +"most important items are the coordinates of the site. There are three ways " +"to specify coordinates:" msgstr "" #. type: Plain text -#: ./user-manual.txt:715 +#: user-manual.txt:692 msgid "" -"One can find the coordinates on the world map in the bottom right hand part " -"of the _Subsurface_ window. The map displays an orange bar indicating \"No " -"location data - Move the map and double-click to set the dive " -"location\". Upon a doubleclick at the appropriate place, the orange bar " -"disappears and the coordinates are stored." +"Use the world map in the bottom right hand part of the _Subsurface_ " +"window. The map displays an orange bar indicating \"No location data - Move " +"the map and double-click to set the dive location\". Doubleclick at the " +"appropriate place, and the orange bar disappears and the coordinates are " +"stored." msgstr "" #. type: Plain text -#: ./user-manual.txt:720 +#: user-manual.txt:697 msgid "" -"The coordinates can be obtained from the _Subsurface_ Companion app if the " -"user has an Android or iPhone device with GPS and if the coordinates of the " -"dive site were stored using that device. xref:S_Companion[Click here for " -"more information]" +"Use the _Subsurface_ Companion app if you have an Android or iPhone device " +"with GPS and if the dive site coordinates were stored using it. " +"xref:S_Companion[Click here for more information]" msgstr "" #. type: Plain text -#: ./user-manual.txt:723 +#: user-manual.txt:699 msgid "" -"The coordinates can be entered by hand if they are known, using one of four " -"formats with latitude followed by longitude:" +"Enter by hand if the coordinates are known, using one of four formats with " +"latitude followed by longitude:" msgstr "" #. type: Plain text -#: ./user-manual.txt:728 +#: user-manual.txt:704 msgid "" "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, " @@ -1337,37 +1291,36 @@ msgid "" msgstr "" #. type: Plain text -#: ./user-manual.txt:736 +#: user-manual.txt:712 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. Some keyboards " "don't have the degree sign (°). It can be replaced by a *d* like this: N30d " -"W20d. If both a dive site name and coordinates have been provided, Save the " +"W20d. If both a dive site name and coordinates have been provided, save the " "dive site information by selecting the button _Apply changes_ at the top of " "the panel." msgstr "" #. type: Plain text -#: ./user-manual.txt:742 +#: user-manual.txt:718 #, no-wrap msgid "" -"*Important*: GPS coordinates of a dive site are linked to the Location\n" -"name - so *saving* a dive site with only coordinates and no dive site name\n" -"causes unexpected behaviour (Subsurface will think that all of these\n" +"*Important*: GPS coordinates of a dive site are linked to the location\n" +"name - so *saving* a dive site with only coordinates and no name\n" +"causes problems. (Subsurface will think all of these\n" "dives have the same location and try to keep their GPS coordinates the\n" "same).\n" msgstr "" #. type: Plain text -#: ./user-manual.txt:752 +#: user-manual.txt:728 #, no-wrap msgid "" "*Dive site name lookup:* If coordinates have been typed into the " "appropriate\n" -"text box, one can perform an automated name lookup based on the " -"coordinates.\n" -"This is achieved when _Subsurface_ uses the Internet to find the name of the " +"text box, you can do an automated name lookup based on the coordinates.\n" +"This is done when _Subsurface_ uses the Internet to find the name of the " "dive site\n" "based on the coordinates that were typed. If a name has been found, it is\n" "automatically inserted into the tags box. The list box\n" @@ -1375,138 +1328,133 @@ msgid "" "of the dive site panel contains the names of other dives sites used at the\n" "current location. For instance if the dive site is \"Blue Hole\" and there " "are several\n" -"dive sites named \"Blue Hole\", all these sites are listed in this list " -"box.\n" +"sites named \"Blue Hole\", all of them are listed.\n" msgstr "" #. type: Plain text -#: ./user-manual.txt:757 +#: user-manual.txt:733 msgid "" -"Enter any other textual information about the dive site (Description and " +"Enter any other contextual information about the dive site (Description and " "Notes), then select _Apply Changes_ to save the geolocation for this dive " -"site. At a later stage the dive site information can be edited by clicking " -"the globe icon to the right of the dive site name in the *Notes tab*." +"site. The dive site information can later be edited by clicking the globe " +"icon to the right of the dive site name in the *Notes tab*." msgstr "" #. type: Plain text -#: ./user-manual.txt:762 +#: user-manual.txt:738 #, no-wrap msgid "" -"*Dive mode*: This is a dropdown box allowing one to choose the type of " +"*Dive mode*: This is a dropdown box allowing you to choose the type of " "dive\n" -"performed. The options are OC (Open Circuit SCUBA, the default seting, meant " -"for most recreational dives),\n" +"performed. The options are OC (Open Circuit SCUBA, the default setting, for " +"most recreational dives),\n" "Freedive (dive without SCUBA equipment), CCR (Closed-circuit\n" "rebreather) and pSCR (Passive semi-closed rebreather).\n" msgstr "" #. type: Plain text -#: ./user-manual.txt:767 +#: user-manual.txt:743 #, no-wrap msgid "" -"*Divemaster*: The name of the dive master or dive guide for this dive should " -"be\n" +"*Divemaster*: The name of the divemaster or dive guide should be\n" "entered in this field\n" "which offers auto selection based on the list of dive masters in\n" "the current logbook.\n" msgstr "" #. type: Plain text -#: ./user-manual.txt:772 +#: user-manual.txt:748 #, 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" +"*Buddy*: In this field, enter the name(s) of the buddy or buddies\n" +"(separated with commas) who were on the\n" "dive. Auto selection based on the list of buddies in the current logbook " "is\n" "offered.\n" msgstr "" #. type: Plain text -#: ./user-manual.txt:777 +#: user-manual.txt:753 #, no-wrap msgid "" "*Suit*: Here the type of dive suit used can be entered.\n" "Auto selection 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 undersuit was used.\n" +"suit and thermal under suit was used.\n" msgstr "" #. type: Plain text -#: ./user-manual.txt:780 +#: user-manual.txt:756 #, no-wrap msgid "" -"*Rating*: One can provide a subjective overall rating of the dive on a\n" +"*Rating*: You 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:784 +#: user-manual.txt:760 #, no-wrap msgid "" -"*Visibility*: Similarly, one can provide a rating of visibility during the\n" +"*Visibility*: You 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:793 +#: user-manual.txt:768 #, no-wrap msgid "" -"*Tags*: Tags that describe the type of dive performed can be entered\n" +"*Tags*: Tags that describe the type of dive done 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" +"_Subsurface_ has many built-in tags. If you 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" +"will list the tags that correspond to the typing. For instance, by typing\n" +"+cav+, the tags *cave* and *cavern* are shown to choose from.\n" msgstr "" #. type: Plain text -#: ./user-manual.txt:795 +#: user-manual.txt:770 #, no-wrap msgid "*Notes*: Any additional information for the dive can be entered here.\n" msgstr "" #. type: Plain text -#: ./user-manual.txt:800 +#: user-manual.txt:775 msgid "" "The _Apply changes_ and _Discard changes_ 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. The image xref:S_Notes_dc[at the beginning of this section] shows an " -"example of a *Notes tab* after completion of the dive information." +"information for tabs in the *Info* panel and in the *Dive Profile* " +"panel. Use them when *ALL* other information has been added. The image " +"xref:S_Notes_dc[at the beginning of this section] shows an example of a " +"*Notes tab* after completing the dive information." msgstr "" #. type: Title ===== -#: ./user-manual.txt:801 +#: user-manual.txt:776 #, no-wrap msgid "Equipment" msgstr "" #. type: Plain text -#: ./user-manual.txt:806 +#: user-manual.txt:781 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 " +"The Equipment tab lets you enter information about the type of cylinder and " +"gas used, as well as the weights used for the dive. The message in the blue " "box at the top of the panel:" msgstr "" #. type: Plain text -#: ./user-manual.txt:813 +#: user-manual.txt:788 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)." +"shows the dive is being edited. This is a highly interactive part of " +"_Subsurface_ and the information on cylinders and gases (entered here) " +"determines the behavior of the *Dive profile* (top right-hand panel)." msgstr "" #. type: Plain text -#: ./user-manual.txt:817 +#: user-manual.txt:792 #, no-wrap msgid "" "*Cylinders*: The cylinder information is entered through a dialogue that " @@ -1515,51 +1463,45 @@ msgid "" msgstr "" #. type: Target for macro image -#: ./user-manual.txt:818 +#: user-manual.txt:793 #, no-wrap msgid "images/DC_gas-dialogue1_f20.jpg" msgstr "" #. type: Plain text -#: ./user-manual.txt:827 +#: user-manual.txt:806 msgid "" "For hand-entered dives, this information needs to be typed in. For dive " -"computers, _Subsurface_ often obtains the gas used from the dive computer " -"and automatically inserts the gas composition(% oxygen or % helium) 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:832 -msgid "" -"The user should start by selecting a cylinder type on the left-hand side of " -"the table. To select a cylinder, the _Type_ box should be clicked. This " -"brings up a list button that can be used to display a dropdown list of " -"cylinders:" +"computers, _Subsurface_ often gets the gas used from the dive computer and " +"automatically inserts the gas composition(% oxygen or % helium) in the " +"table. The + button at the top right lets you add more cylinders for this " +"dive. The dark dust bin icon on the left lets you delete 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. Start by selecting a cylinder type on the " +"left-hand side of the table. To select a cylinder, the _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:833 +#: user-manual.txt:807 #, no-wrap msgid "images/DC_gas-dialogue2_f20.jpg" msgstr "" #. type: Plain text -#: ./user-manual.txt:840 +#: user-manual.txt:814 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 " +"used for this dive, or just 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 (_Work.press_) will automatically be shown in " "the dialogue." msgstr "" #. type: Plain text -#: ./user-manual.txt:844 +#: user-manual.txt:818 msgid "" "Next, indicate the starting pressure and the ending pressure of the " "specified gas during the dive. The unit of pressure (metric/imperial) " @@ -1567,7 +1509,7 @@ msgid "" msgstr "" #. type: Plain text -#: ./user-manual.txt:855 +#: user-manual.txt:829 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, " @@ -1576,109 +1518,109 @@ msgid "" "the cylinder, save the data either by pressing _ENTER_ on the keyboard or by " "clicking outside the cell containing 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):" +"hand. The following is an example of a complete description for a dive using " +"two cylinders (air and EAN50):" msgstr "" #. type: Target for macro image -#: ./user-manual.txt:856 +#: user-manual.txt:830 #, no-wrap msgid "images/CylinderDataEntry3_f20.jpg" msgstr "" #. type: Plain text -#: ./user-manual.txt:863 +#: user-manual.txt:837 #, 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" +"using a dialogue similar to that of the cylinder information. If you\n" +"click\n" "the + button on the top right of the weights dialogue, the table looks " "like\n" "this:\n" msgstr "" #. type: Target for macro image -#: ./user-manual.txt:864 +#: user-manual.txt:838 #, no-wrap msgid "images/WeightsDataEntry1_f20.jpg" msgstr "" #. type: Plain text -#: ./user-manual.txt:868 +#: user-manual.txt:842 msgid "" "By clicking on the _Type_ field, a drop-down list becomes accessible through " "a down-arrow:" msgstr "" #. type: Target for macro image -#: ./user-manual.txt:869 +#: user-manual.txt:843 #, no-wrap msgid "images/WeightsDataEntry2_f20.jpg" msgstr "" #. type: Plain text -#: ./user-manual.txt:883 +#: user-manual.txt:857 msgid "" "This can be used to select the type of weight system used during the dive or " -"the user may start typing in the box to specify a different weighting " -"mechanism that will be saved by _Subsurface_. In the *Weight* field, type " -"in the amount of weight used during the dive. After specifying the weight " -"system, save the data by either pressing _ENTER_ on the keyboard or by " -"clicking 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:" +"just may start typing in the box to specify a different weighting mechanism " +"that will be saved by _Subsurface_. In the *Weight* field, type in the " +"amount of weight used during the dive. After specifying the weight system, " +"save the data by pressing _ENTER_ on the keyboard or by clicking outside the " +"cell with the cursor. It’s 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 dust bin 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: Target for macro image -#: ./user-manual.txt:884 +#: user-manual.txt:858 #, no-wrap msgid "images/WeightsDataEntry3_f20.jpg" msgstr "" #. type: Title ==== -#: ./user-manual.txt:886 +#: user-manual.txt:860 #, no-wrap msgid "Editing several selected dives simultaneously" msgstr "" #. type: Plain text -#: ./user-manual.txt:901 +#: user-manual.txt:876 msgid "" "_METHOD 1_: After uploading dives from a dive computer, the dive profiles of " -"each uploaded dive is shown in the *Dive profile* tab, as well as a few " -"items of information in the *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 *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 *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." +"each is shown in the *Dive profile* tab, as well as a few items of " +"information in the *Notes* tab (e.g. water temperature) and in the " +"*Equipment* tab (e.g. gas pressures and gas composition). Other fields " +"remain empty. It may be useful to simultaneously edit some of the fields in " +"the *Notes* and *Equipment* tabs. For instance, it’s possible that a diver " +"performed several dives during a single day, using identical equipment at " +"the same dive site, or with the same divemaster and/or buddy or " +"tags. Instead of completing the information for each dive separately, select " +"all the dives for that day in the *Dive List* and insert the same " +"information in the *Notes* and *Equipment* fields that need identical " +"information. This is done by editing the dive notes or the equipment for any " +"one of the selected dives." msgstr "" #. type: Plain text -#: ./user-manual.txt:911 +#: user-manual.txt:886 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." +"Simultaneous editing only works with fields that do not already contain " +"information. This means 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 speeds up the completion of the dive log after several " +"similar dives." msgstr "" #. type: Plain text -#: ./user-manual.txt:920 +#: user-manual.txt:895 msgid "" "_METHOD 2_:There is a different way of achieving the same goal. Select a " "dive with all the appropriate information typed into the *Notes* and " @@ -1693,76 +1635,75 @@ msgid "" msgstr "" #. type: Title ==== -#: ./user-manual.txt:921 +#: user-manual.txt:896 #, no-wrap msgid "Adding Bookmarks to a dive" msgstr "" #. type: Plain text -#: ./user-manual.txt:926 +#: user-manual.txt:901 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:" +"Many divers wish to annotate dives with text that indicate particular " +"events, e.g. \"Saw dolphins\", or \"Released surface buoy\". This is easily " +"done:" msgstr "" #. type: Plain text -#: ./user-manual.txt:930 +#: user-manual.txt:905 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)." +"on the dive profile at that point (see *A* below)." msgstr "" #. type: Plain text -#: ./user-manual.txt:932 +#: user-manual.txt:907 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:935 +#: user-manual.txt:910 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:938 +#: user-manual.txt:913 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)." +"Hovering 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:939 +#: user-manual.txt:914 #, no-wrap msgid "images/Bookmarks.jpg" msgstr "" #. type: Title ==== -#: ./user-manual.txt:942 +#: user-manual.txt:917 #, no-wrap msgid "Saving the updated dive information" msgstr "" #. type: Plain text -#: ./user-manual.txt:953 +#: user-manual.txt:928 msgid "" "The information entered in the *Notes* tab and the *Equipment* tab can be " "saved by using the two buttons on the top right hand of the *Notes* tab. If " "the _Apply changes_ button is clicked, the dive data are saved in the memory " -"image of the dive. If the _Discard changes_ button is clicked, then the " -"newly entered dive data are erased from the computer memory, although the " -"dive profile is retained. When the user exits _Subsurface_ there is a final " -"prompt to confirm that the new data should now be saved permanently on the " +"image of the dive. If the _Discard changes_ button is clicked, the newly " +"entered dive data are erased from the computer memory, although the dive " +"profile is retained. When the user exits _Subsurface_ there is a final " +"prompt to confirm the new data should now be saved permanently on the " "computer disk." msgstr "" #. type: Title === -#: ./user-manual.txt:954 +#: user-manual.txt:929 #, no-wrap msgid "" "Importing dive information from other digital data sources or other data " @@ -1770,150 +1711,148 @@ msgid "" msgstr "" #. type: Plain text -#: ./user-manual.txt:980 +#: user-manual.txt:954 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 " +"If you’ve been diving for some time, it’s possible several dives were logged " +"using other dive log software. 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 software. While some software is supported natively, for others you will " +"need to export the logbook(s) to an intermediate format so 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. a 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:990 -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. Below follows more specific information to achieve data import to " -"_Subsurface_." +"import UDDF and UDCF files used by some dive log software and some dive " +"computers, like the Heinrichs & Weikamp DR5. Finally, for some dive log " +"software like Mares Dive Organizer we currently recommend you import the " +"logbooks first into a web service like _divelogs.de_ and then import from " +"there with _Subsurface_. Divelogs.de supports a few additional logbook " +"formats that _Subsurface_ currently cannot handle." +msgstr "" + +#. type: Plain text +#: user-manual.txt:964 +msgid "" +"If the format of other software is supported natively on Subsurface, 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. Below is more specific information to import " +"data to _Subsurface_." msgstr "" #. type: Title ==== -#: ./user-manual.txt:991 +#: user-manual.txt:964 #, no-wrap msgid "Using the universal import dialogue" msgstr "" #. type: Plain text -#: ./user-manual.txt:997 +#: user-manual.txt:970 msgid "" -"Importing dives from other software is performed through a universal " -"interface activated by selecting _Import_ from the Main Menu, then clicking " -"on _Import Log Files_. This brings up dialogue *A*, below." +"Importing dives from other software is done through a universal interface " +"activated by selecting _Import_ from the Main Menu, then clicking on _Import " +"Log Files_. This brings up dialogue *A*, below." msgstr "" #. type: Target for macro image -#: ./user-manual.txt:998 +#: user-manual.txt:971 #, no-wrap msgid "images/Import1_f20.jpg" msgstr "" #. type: Plain text -#: ./user-manual.txt:1003 +#: user-manual.txt:976 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:" +"_Dive Log Files_ which accesses different types of direct imports available, " +"as in dialogue *B*, above. Currently these are:" msgstr "" #. type: Plain text -#: ./user-manual.txt:1005 +#: user-manual.txt:978 msgid "" "XML-formatted dive logs (DivingLog 5.0, MacDive and several other dive log " "systems)" msgstr "" #. type: Plain text -#: ./user-manual.txt:1006 +#: user-manual.txt:979 msgid "Cochran dive logs" msgstr "" #. type: Plain text -#: ./user-manual.txt:1007 +#: user-manual.txt:980 msgid "UDDF-formatted dive logs (e.g. Kenozoooid)" msgstr "" #. type: Plain text -#: ./user-manual.txt:1008 +#: user-manual.txt:981 msgid "UDCF-formatted dive logs" msgstr "" #. type: Plain text -#: ./user-manual.txt:1009 +#: user-manual.txt:982 msgid "Poseidon MkVI CCR logs" msgstr "" #. type: Plain text -#: ./user-manual.txt:1010 +#: user-manual.txt:983 msgid "APD Inspiration/Evolution CCR logs" msgstr "" #. type: Plain text -#: ./user-manual.txt:1011 +#: user-manual.txt:984 msgid "LiquiVision logs" msgstr "" #. type: Plain text -#: ./user-manual.txt:1012 +#: user-manual.txt:985 msgid "divelog.de logs" msgstr "" #. type: Plain text -#: ./user-manual.txt:1013 +#: user-manual.txt:986 msgid "OSTC Tools logs" msgstr "" #. type: Plain text -#: ./user-manual.txt:1014 +#: user-manual.txt:987 msgid "JDiveLog" msgstr "" #. type: Plain text -#: ./user-manual.txt:1015 +#: user-manual.txt:988 msgid "Suunto Dive Manager (DM3 and DM4)" msgstr "" #. type: Plain text -#: ./user-manual.txt:1016 +#: user-manual.txt:989 msgid "CSV (text-based and spreadsheet-based) dive logs, including APD CCR logs" msgstr "" #. type: Plain text -#: ./user-manual.txt:1021 +#: user-manual.txt:994 msgid "" "Selecting the appropriate format and then the specific log file in the large " -"window containing the file list on the right of the dialogue opens the " -"imported dive log in the _Subsurface_ *Dive List*. Some other formats, not " +"window containing the file list on the right 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:1022 +#: user-manual.txt:995 #, no-wrap msgid "Importing from OSTCTools" msgstr "" #. type: Plain text -#: ./user-manual.txt:1031 +#: user-manual.txt:1004 msgid "" "_OSTC Tools_ is a Microsoft-based suite of dive download and dive management " "tools for the OSTC family of dive computers. _OSTC Tools_ downloads dive " @@ -1926,104 +1865,105 @@ msgid "" msgstr "" #. type: Plain text -#: ./user-manual.txt:1035 +#: user-manual.txt:1008 msgid "" -"Actually, all H&W devices supported by OSTCTools can be imported to " -"_Subsurface_, this includes OSTC, OSTC Mk2, OSTC 2N/2C, OSTC3, OSTC Sport, " -"and probably although untested, Frog, OSTC2 and OSTC CR." +"All H&W devices supported by OSTCTools can be imported to _Subsurface_. This " +"includes OSTC, OSTC Mk2, OSTC 2N/2C, OSTC3, OSTC Sport, and probably " +"although untested, Frog, OSTC2 and OSTC CR." msgstr "" #. type: Plain text -#: ./user-manual.txt:1040 +#: user-manual.txt:1013 msgid "" -"Please, remember that OSTCTools is *not* a true diving log software, but a " -"useful set of tools for analysis and management of OSTC devices. This way, " -"only raw dive computer data will be performed with the import to " -"_Subsurface_; one has to to manually complete the rest of data which may be " -"important (buddies, equipment, notes, etc)." +"Please remember that OSTCTools is *not* a true diving log software, but " +"rather a useful set of tools for analysis and management of OSTC " +"devices. Only raw dive computer data will be imported to _Subsurface_; you " +"have to manually complete the rest of the data you want (buddies, equipment, " +"notes, etc)." msgstr "" #. type: Title ==== -#: ./user-manual.txt:1042 +#: user-manual.txt:1015 #, no-wrap -msgid "Importing from Mares Dive Organiser V2.1" +msgid "Importing from Mares Dive Organizer V2.1" msgstr "" #. type: Plain text -#: ./user-manual.txt:1049 +#: user-manual.txt:1022 msgid "" -"Since Mares utilise proprietary Windows software not compatible with " +"Since Mares uses 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 " +"process, using _www.divelogs.de_ as a gateway to extract the dive log " "information." msgstr "" #. type: Plain text -#: ./user-manual.txt:1054 +#: user-manual.txt:1027 msgid "" -"Export the dive log data from Mares Dive Organiser to the user's desktop, " -"using a _.sdf_ file name extension. Refer to xref:Mares_Export[Appendix C] " -"for more information." +"Export the dive log data from Mares Dive Organizer to your desktop, using a " +"_.sdf_ file name extension. Refer to xref:Mares_Export[Appendix C] for more " +"information." msgstr "" #. type: Plain text -#: ./user-manual.txt:1060 +#: user-manual.txt:1033 msgid "" -"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_." +"Data should then be imported into _www.divelogs.de_. You will first need to " +"create a user account in _www.divelogs.de_. Log into that web site, then " +"select _Import Logbook -> Dive Organizer 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 Organizer database to " +"_www.divelogs.de_." msgstr "" #. type: Plain text -#: ./user-manual.txt:1062 +#: user-manual.txt:1035 msgid "" "Finally, import the dives from _divelogs.de_ to _Subsurface_, using the " "instructions below." msgstr "" #. type: Title ==== -#: ./user-manual.txt:1065 +#: user-manual.txt:1038 #, no-wrap msgid "Importing dives from *divelogs.de*" msgstr "" #. type: Plain text -#: ./user-manual.txt:1078 +#: user-manual.txt:1051 msgid "" -"The import of dive information from _divelogs.de_ is simple, using a single " +"Importing dive information from _divelogs.de_ is simple, using a single " "dialogue box. The _Import -> Import from Divelogs.de_ option should be " "selected from the Main Menu. This brings up a dialogue box (see image *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 image *B*, " -"below). The _Apply_ button should then be selected, after which the imported " -"dives appear in the _Subsurface_ *Dive List* panel." +"below). Enter a user-ID and password for _divelogs.de_ 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 shown (see image *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:1079 +#: user-manual.txt:1052 #, no-wrap msgid "images/Divelogs1.jpg" msgstr "" #. type: Title ==== -#: ./user-manual.txt:1082 +#: user-manual.txt:1055 #, no-wrap msgid "Importing data in CSV format" msgstr "" #. type: Plain text -#: ./user-manual.txt:1093 +#: user-manual.txt:1066 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). The _CSV_ format is a universal simplified format that " -"allows for easy information exchange between different computers or software " +"allows easy information exchange between different computers or software " "packages. For an introduction to CSV-formatted files see xref:S_CSV_Intro[A " "Diver's Introduction To CSV Files]. _Subsurface_ dive logs can also be " "exported in _CSV_ format to other software that reads this format. See " @@ -2033,61 +1973,61 @@ msgid "" msgstr "" #. type: Title ===== -#: ./user-manual.txt:1095 +#: user-manual.txt:1068 #, no-wrap msgid "Importing dives in CSV format from dive computers or other dive log software" msgstr "" #. type: Plain text -#: ./user-manual.txt:1100 +#: user-manual.txt:1073 msgid "" -"One can view a _CSV_ file by using an ordinary text editor. It is normally " -"organised into a single line that provides the headers (or _field names_ or " +"You can view a _CSV_ file by using an ordinary text editor. It’s normally " +"organized into a single line that provides the headers (or _field names_ or " "_column headings_) of the data columns, followed by the data, one record per " "line." msgstr "" #. type: Plain text -#: ./user-manual.txt:1102 +#: user-manual.txt:1075 msgid "" "There are two types of _CSV_ dive logs that can be imported into " "_Subsurface_:" msgstr "" #. type: Plain text -#: ./user-manual.txt:1108 +#: user-manual.txt:1081 msgid "" "_CSV dive details_: This dive log format contains similar information to " "that of a typical written dive log, e.g. dive date and time, dive depth, " -"dive duration, names of buddy and dive master and perhaps some information " -"about cylinder pressures before and after the dive, as well as a comment or " -"two about the dive. All the data for a single dive go on a single line of " -"text, following the order of the column headings." +"dive duration, names of buddy and divemaster and information about cylinder " +"pressures before and after the dive, as well as comments about the dive. All " +"the data for a single dive go on a single line of text, following the order " +"of the column headings." msgstr "" #. type: Plain text -#: ./user-manual.txt:1117 +#: user-manual.txt:1090 msgid "" "_CSV dive profile_: This dive log format includes much more information " "about a single dive. For instance there may be information at 30-second " -"intervals, indicating depth, water temperature at that depth, and cylinder " -"pressure at that moment in time. Each line contains the information for a " -"single instant in time during the dive, 30 seconds after that of the " -"previous instant. Many lines are required to complete the depth profile " -"information for a single dive. This is a common export format used by " -"closed-circuit rebreather (CCR) dive equipment and many software packages " -"that handle dive computer data and/or dive logs." +"intervals, indicating depth, water temperature, and cylinder pressure at " +"that moment in time. Each line contains the information for a single instant " +"in time during the dive, 30 seconds after that of the previous instant. Many " +"lines are required to complete the depth profile information for a single " +"dive. This is a common export format used by closed-circuit rebreather (CCR) " +"dive equipment and many software packages that handle dive computer data " +"and/or dive logs." msgstr "" #. type: Plain text -#: ./user-manual.txt:1120 +#: user-manual.txt:1093 msgid "" -"Before being able to import the _CSV_ data to _Subsurface_ *one needs to " +"Before being able to import the _CSV_ data to _Subsurface_ *you needs to " "know a few things about the data being imported*:" msgstr "" #. type: Plain text -#: ./user-manual.txt:1128 +#: user-manual.txt:1101 msgid "" "Which character separates the different columns within a single line of " "data? This field separator should be either a comma (,) a semicolon (;) or a " @@ -2099,7 +2039,7 @@ msgid "" msgstr "" #. type: Plain text -#: ./user-manual.txt:1132 +#: user-manual.txt:1105 msgid "" "Which data columns need to be imported into _Subsurface_? Is it a _CSV dive " "details_ file or a _CSV dive profile_ file? Open the file using a text " @@ -2108,14 +2048,14 @@ msgid "" msgstr "" #. type: Plain text -#: ./user-manual.txt:1134 +#: user-manual.txt:1107 msgid "Is the numeric information (e.g. dive depth) in metric or in imperial units?" msgstr "" #. type: Plain text -#: ./user-manual.txt:1141 +#: user-manual.txt:1114 msgid "" -"Armed with this information, importing the data into _Subsurface_ is " +"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_ (towards the bottom " "right). This shows all .CSV files in the selected directory. Select the file " @@ -2123,84 +2063,88 @@ msgid "" msgstr "" #. type: Target for macro image -#: ./user-manual.txt:1142 +#: user-manual.txt:1115 #, no-wrap msgid "images/csv_import1_f20.jpg" msgstr "" #. type: Plain text -#: ./user-manual.txt:1153 +#: user-manual.txt:1126 +#, no-wrap msgid "" -"Notice that, at the top left, there is a dropdown list containing " -"pre-configured settings for some of the more common dive computers and " -"software packages encountered by divers. If the _CSV_ file being imported " -"originated from any of these pre-configured items, then select it. Otherwise " -"use the _Manual Import_ option. The configuration panel also has dropdown " -"lists for the specification of the appropriate field separator (Tab, comma " -"or semicolon), the date format used in the _CSV_ file, the time units " -"(seconds, minutes or minutes:seconds), as well as the unit system (metric or " -"imperial). Selecting the appropriate options among these is critical for the " -"successful import of the data." +"At the top left, there is a dropdown list containing pre- configured\n" +"settings for common dive computers and software packages.\n" +" If the _CSV_ file being imported originated from any of\n" +"these pre-configured items, select it. Otherwise use the _Manual Import_\n" +"option. The configuration panel also has dropdown lists for the " +"specification of the appropriate\n" +"field separator (Tab, comma or semicolon), the date format used in the _CSV_ " +"file,\n" +"the time units (seconds, minutes or minutes:seconds), as well as the unit " +"system\n" +"(metric or imperial). Selecting the appropriate options among these is " +"critical for\n" +"the successful data import.\n" msgstr "" #. type: Plain text -#: ./user-manual.txt:1165 +#: user-manual.txt:1138 msgid "" -"The last remaining task is to ensure that all the data columns have the " -"appropriate column headings. The top blue row of the data table contains the " -"column headings found in the _CSV_ data file. The blue row of balloons " -"immediately above these contains the names understood by _Subsurface_. These " -"balloons can be moved using a drag-and-drop action. For instance, " -"_Subsurface_ expects the column heading for Dive number (\" # \") to be " -"\"Dive # \". If the column heading that _Subsurface_ expects is not in the " -"blue row, then drag the appropriate balloon from the upper area and drop it " -"in the appropriate blue cell at the top of the table. To indicate the " -"correct column for \"Dive #\", drag the ballooned item labelled \"Dive # \" " -"and drop it in the blue cell immediately above the white cell containing \" " -"# \". This is depicted in the image below." +"Complete this by ensuring that all the data columns have the appropriate " +"column headings. The top blue row of the data table contains the column " +"headings found in the _CSV_ data file. The blue row of balloons immediately " +"above these contains the names understood by _Subsurface_. These balloons " +"can be moved using a drag-and-drop action. For instance, _Subsurface_ " +"expects the column heading for Dive number (\" # \") to be \"Dive # \". If " +"the column heading that _Subsurface_ expects is not in the blue row, drag " +"the appropriate balloon from the upper area and drop it in the appropriate " +"blue cell at the top of the table. To indicate the correct column for \"Dive " +"#\", drag the ballooned item labelled \"Dive # \" and drop it in the blue " +"cell immediately above the white cell containing \" # \". This is depicted " +"in the image below." msgstr "" #. type: Target for macro image -#: ./user-manual.txt:1166 +#: user-manual.txt:1139 #, no-wrap msgid "images/csv_import2_f20.jpg" msgstr "" #. type: Plain text -#: ./user-manual.txt:1172 +#: user-manual.txt:1145 msgid "" -"Continue in this way to ensure that all the column headings in the blue row " -"of cells correspond to the headings listed in the top part of the " -"dialogue. Having completed this task, select the _OK_ button to the bottom " -"right of the dialogue. The data from the _CSV_ file are imported and shown " -"in the *Dive List* panel." +"Continue in this way to ensure all the column headings in the blue row of " +"cells correspond to the headings listed in the top part of the dialogue. " +"When finished, select the _OK_ button on the bottom right of the dialogue. " +"The data from the _CSV_ file are imported and shown in the *Dive List* " +"panel." msgstr "" #. type: delimited block * -#: ./user-manual.txt:1176 +#: user-manual.txt:1149 #, no-wrap msgid "*A Diver's Introduction to _CSV_ Files*\n" msgstr "" #. type: delimited block * -#: ./user-manual.txt:1190 +#: user-manual.txt:1163 msgid "" "_CSV_ is an abbreviation for a data file format: _Comma-Separated " -"Values_. It is a file format allowing someone to view or edit the " -"information using a text editor such as Notepad (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 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." +"Values_. It is a file format that lets you view or edit information using a " +"text editor like Notepad (Windows), gedit (Linux) or TextWrangler " +"(OS/X). There are two main advantages of the _CSV_ format. First, the data " +"are easily editable as text without any proprietary software. Second, all " +"information is human-readable, not obscured by any custom or proprietary " +"attributes that proprietary software inserts 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 like spreadsheet-based dive logs and " +"some dive computers." msgstr "" #. type: delimited block * -#: ./user-manual.txt:1199 +#: user-manual.txt:1172 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 " @@ -2208,7 +2152,7 @@ msgid "" "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 " +"organized 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 " @@ -2216,7 +2160,7 @@ msgid "" msgstr "" #. type: delimited block * -#: ./user-manual.txt:1205 +#: user-manual.txt:1178 #, no-wrap msgid "" "\tDive site,Dive date,Time,Dive_duration, Dive_depth,Dive buddy\n" @@ -2227,14 +2171,14 @@ msgid "" msgstr "" #. type: delimited block * -#: ./user-manual.txt:1207 +#: user-manual.txt:1180 msgid "" "The above data are not easily read by a human. Here is the same information " "in TAB-delimited format:" msgstr "" #. type: delimited block * -#: ./user-manual.txt:1213 +#: user-manual.txt:1186 #, no-wrap msgid "" "\tDive site\tDive date\tTime\tDive_duration\tDive_depth\tDive buddy\n" @@ -2245,7 +2189,7 @@ msgid "" msgstr "" #. type: delimited block * -#: ./user-manual.txt:1221 +#: user-manual.txt:1194 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 " @@ -2259,7 +2203,7 @@ msgid "" msgstr "" #. type: delimited block * -#: ./user-manual.txt:1232 +#: user-manual.txt:1205 #, no-wrap msgid "" "\tDive Time (s)\tDepth (m)\tpO₂ - Setpoint (Bar) \tpO₂ - C1 Cell 1 " @@ -2276,31 +2220,31 @@ msgid "" msgstr "" #. type: delimited block * -#: ./user-manual.txt:1238 +#: user-manual.txt:1211 msgid "" "When a _CSV_ file is selected for import, _Subsurface_ displays the column " "headers as well as some of the data in the first few lines of the _CSV_ " -"file, making it much easier to work with _CSV_ files. _CSV_ files can " -"therefore be used in many contexts for importing data into a _Subsurface_ " -"dive log. Knowledge of a few basic things about the content of the _CSV_ " -"file allows a smooth import of the dives into _Subsurface_." +"file, making it much easier to work with _CSV_ files. _CSV_ files can be " +"used in many contexts for importing data into a _Subsurface_ dive log. " +"Knowing a few basic things about the content of the _CSV_ file helps with a " +"smooth import of the dives into _Subsurface_." msgstr "" #. type: Plain text -#: ./user-manual.txt:1252 +#: user-manual.txt:1225 msgid "" -"The _CSV_ import has a couple of caveats. One should avoid some special " -"characters like ampersand (&), less than (<), greater than (>) and double " -"quotes (\") as part of the numbers or text within a cell. The file should " -"use UTF-8 character set, if using non-ASCII characters. Also the size of the " -"_CSV_ file might cause problems. Importing 100 dives at a time (_CSV dive " +"But, the _CSV_ import has a couple of caveats. Avoid some special characters " +"like ampersand (&), less than (<), greater than (>) and double quotes (\") " +"as part of the numbers or text within a cell. The file should use UTF-8 " +"character set, if using non-ASCII characters. Also the size of the _CSV_ " +"file might cause problems. Importing 100 dives at a time (_CSV dive " "details_) works, but larger files might exceed the limits of the parser " "used. When encountering problems with _CSV_ imports, first try with a " "smaller file to make sure everything works." msgstr "" #. type: Title === -#: ./user-manual.txt:1255 +#: user-manual.txt:1228 #, no-wrap msgid "" "Importing GPS coordinates with the _Subsurface Companion App_ for mobile " @@ -2308,40 +2252,37 @@ msgid "" msgstr "" #. type: Plain text -#: ./user-manual.txt:1264 +#: user-manual.txt:1237 #, no-wrap msgid "" "Using the *Subsurface Companion App* on an _Android device_ or\n" "xref:S_iphone[_iPhone_] with GPS, the coordinates\n" "for the diving\n" -"location can be automatically passed to the _Subsurface_\n" -"dive log. The Companion App stores the dive locations on\n" -"a dedicated Internet file server. _Subsurface_, in turn, can collect\n" -"the localities from the file server.\n" -msgstr "" - -#. type: Plain text -#: ./user-manual.txt:1266 -msgid "To do this:" +"location can be automatically passed to the _Subsurface_ dive log. The " +"Companion App\n" +"stores dive locations on a dedicated Internet server. _Subsurface_ can " +"collect\n" +"the locations from the server.\n" +"To do this:\n" msgstr "" #. type: Title ==== -#: ./user-manual.txt:1267 +#: user-manual.txt:1238 #, no-wrap msgid "Create a Companion App account" msgstr "" #. type: Plain text -#: ./user-manual.txt:1272 +#: user-manual.txt:1243 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 " +"will be sent, a long number giving you access to the file server and " "Companion App capabilities." msgstr "" #. type: Plain text -#: ./user-manual.txt:1277 +#: user-manual.txt:1248 msgid "" "Download the app from " "https://play.google.com/store/apps/details?id=org.subsurface[Google Play " @@ -2350,510 +2291,514 @@ msgid "" msgstr "" #. type: Title ==== -#: ./user-manual.txt:1278 +#: user-manual.txt:1249 #, no-wrap msgid "Using the Subsurface companion app on an Android smartphone" msgstr "" #. type: Plain text -#: ./user-manual.txt:1281 +#: user-manual.txt:1252 msgid "On first use the app has three options:" msgstr "" #. type: Plain text -#: ./user-manual.txt:1287 +#: user-manual.txt:1258 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." +"_Create a new account._ Equivalent to registering in the _Subsurface_ " +"companion page using an Internet browser. You can request a *DIVERID* using " +"this option, but it’s supplied via email and followed up by interaction with " +"the http://api.hohndel.org/login/[_Subsurface companion web page_] to " +"activate the account." msgstr "" #. type: Plain text -#: ./user-manual.txt:1290 +#: user-manual.txt:1261 msgid "" -"_Retrieve an account._ If users forgot their *DIVERID* they will receive an " +"_Retrieve an account._ If users forget their *DIVERID* they will receive an " "email to recover the number." msgstr "" #. type: Plain text -#: ./user-manual.txt:1294 +#: user-manual.txt:1265 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 " +"saves this *DIVERID* and doesn’t ask for it again unless you use the " "_Disconnect_ menu option (see below)." msgstr "" #. type: Plain text -#: ./user-manual.txt:1302 +#: user-manual.txt:1273 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." +"the Default Preferences panel, by selecting _File -> Preferences -> " +"Defaults_ from the main menu in _Subsurface_ itself. This helps " +"synchronization between _Subsurface_ and the Companion App." msgstr "" #. type: Title ===== -#: ./user-manual.txt:1303 +#: user-manual.txt:1274 #, no-wrap msgid "Creating new dive locations" msgstr "" #. type: Plain text -#: ./user-manual.txt:1308 +#: user-manual.txt:1279 msgid "" -"Now one is ready to get a dive position and send it to the server. The " +"Now you are 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:1311 +#: user-manual.txt:1282 msgid "" -"Touch the \"+\" icon on the top right to add a new dive site, a menu will be " -"showed with 3 options:" +"Touch the \"+\" icon on the top right to add a new dive site, a menu shows " +"with 3 options:" msgstr "" #. type: Plain text -#: ./user-manual.txt:1314 +#: user-manual.txt:1285 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:1323 +#: user-manual.txt:1294 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." +"Use Map: This option lets you fix a position by searching a world map. A " +"world map is shown (see *B* below) on which you can show the desired " +"position with a _long press_ on the touch sensitive screen (if the marked " +"location is wrong, simply choose a new location) and select the check " +"symbol in the upper right. A dialog is shown letting you enter the name of " +"the dive location and the date and time of the dive (see *C* below). In " +"order to import this dive location in _Subsurface_ you should set the time " +"to agree with the time of that dive on the dive computer." msgstr "" #. type: Target for macro image -#: ./user-manual.txt:1324 +#: user-manual.txt:1295 #, no-wrap msgid "images/Companion_5.jpg" msgstr "" #. type: Plain text -#: ./user-manual.txt:1332 +#: user-manual.txt:1303 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." +"stored locations shown. Now 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:1333 +#: user-manual.txt:1304 #, no-wrap msgid "Dive lists of dive locations" msgstr "" #. type: Plain text -#: ./user-manual.txt:1341 +#: user-manual.txt:1312 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 " +"selection box to the left showing they need to be uploaded to the " +"server. You 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." +"(like _Delete_ or _Send_) are performed on several selected locations." msgstr "" #. type: Plain text -#: ./user-manual.txt:1349 +#: user-manual.txt:1320 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." +"or a map showing them. 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 you select 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:1350 +#: user-manual.txt:1321 #, no-wrap msgid "images/Companion_4.jpg" msgstr "" #. type: Plain text -#: ./user-manual.txt:1356 +#: user-manual.txt:1327 msgid "" -"When one selects a dive (*not* selecting the check box), the name given to " +"When you select 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:1358 +#: user-manual.txt:1329 msgid "" "Edit (pencil): Change the text name or other characteristics of the dive " "location." msgstr "" #. type: Plain text -#: ./user-manual.txt:1360 -msgid "Maps: Display a map showing the dive location." -msgstr "" - -#. type: Plain text -#: ./user-manual.txt:1363 +#: user-manual.txt:1334 msgid "" -"After editing and saving a dive location (see *C* above), one needs to " -"upload it to the web service, as explained below." +"Maps: Display a map showing the dive location. After editing and saving a " +"dive location (see *C* above), upload it to the web service, as explained " +"below." msgstr "" #. type: Title ===== -#: ./user-manual.txt:1364 +#: user-manual.txt:1335 #, no-wrap msgid "Uploading dive locations" msgstr "" #. type: Plain text -#: ./user-manual.txt:1370 +#: user-manual.txt:1341 msgid "" -"There are several ways to send locations to the server. The easiest is by " +"There are several ways to send locations to the server. The easiest is " "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:1375 +#: user-manual.txt:1346 msgid "" -"Users must be careful, as the trash icon on the right means exactly what it " -"should; it deletes the selected dive location(s)." +"Be careful! 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:1376 +#: user-manual.txt:1347 #, no-wrap msgid "images/Companion_1.jpg" msgstr "" #. type: Plain text -#: ./user-manual.txt:1381 +#: user-manual.txt:1352 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:1383 +#: user-manual.txt:1354 #, no-wrap msgid "Settings on the Companion App" msgstr "" #. type: Plain text -#: ./user-manual.txt:1386 +#: user-manual.txt:1357 msgid "" "Selecting the _Settings_ menu option results in the right hand image above " "(*B*)." msgstr "" #. type: Title ===== -#: ./user-manual.txt:1387 +#: user-manual.txt:1358 #, no-wrap msgid "Server and account" msgstr "" #. type: Plain text -#: ./user-manual.txt:1390 +#: user-manual.txt:1361 msgid "_Web-service URL._ This is predefined (http://api.hohndel.org/)" msgstr "" #. type: Plain text -#: ./user-manual.txt:1394 +#: user-manual.txt:1364 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." +"easiest way to get it is to copy and paste from the confirmation email or " +"just type it in." msgstr "" #. type: Title ===== -#: ./user-manual.txt:1395 +#: user-manual.txt:1364 #, no-wrap msgid "Synchronisation" msgstr "" #. type: Plain text -#: ./user-manual.txt:1399 +#: user-manual.txt:1368 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." +"and those on the web service synchronize each time the app is started." msgstr "" #. type: Plain text -#: ./user-manual.txt:1402 +#: user-manual.txt:1371 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:1403 +#: user-manual.txt:1372 #, no-wrap msgid "Background service" msgstr "" #. type: Plain text -#: ./user-manual.txt:1406 +#: user-manual.txt:1375 msgid "" -"Instead of entering a unique dive location, users can leave the service " -"running in the background of their Android device, allowing the continuous " +"Instead of entering an unique dive location, you can leave the service " +"running in the background of your Android device, allowing a continuous " "collection of GPS locations." msgstr "" #. type: Plain text -#: ./user-manual.txt:1409 -msgid "The settings below define the behaviour of the service:" +#: user-manual.txt:1377 +msgid "The settings below define the behavior of the service:" msgstr "" #. type: Plain text -#: ./user-manual.txt:1412 +#: user-manual.txt:1380 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:1414 +#: user-manual.txt:1382 msgid "_Min distance._ In meters. Minimum distance between two locations." msgstr "" #. type: Plain text -#: ./user-manual.txt:1416 +#: user-manual.txt:1384 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:1417 ./user-manual.txt:1514 ./user-manual.txt:1932 +#: user-manual.txt:1385 user-manual.txt:1486 user-manual.txt:1900 #, no-wrap msgid "images/icons/info.jpg" msgstr "" #. type: Plain text -#: ./user-manual.txt:1427 +#: user-manual.txt:1395 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 50 m 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." +"_How does the background service work?_ Assuming the diver 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 50 m 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 diver is not moving, only one location is " +"saved. If the diver is moving, a trace of the route is obtained by saving a " +"location every 50 meters." msgstr "" #. type: Title ===== -#: ./user-manual.txt:1428 +#: user-manual.txt:1396 #, no-wrap msgid "Other" msgstr "" #. type: Plain text -#: ./user-manual.txt:1432 +#: user-manual.txt:1400 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:1434 +#: user-manual.txt:1402 msgid "_Subsurface website._ A link to the URL of Subsurface web" msgstr "" #. type: Plain text -#: ./user-manual.txt:1436 +#: user-manual.txt:1404 msgid "_Version._ Displays the current version of the Companion App." msgstr "" #. type: Title ===== -#: ./user-manual.txt:1437 +#: user-manual.txt:1405 #, no-wrap msgid "Search" msgstr "" #. type: Plain text -#: ./user-manual.txt:1440 +#: user-manual.txt:1408 msgid "Search the saved dive locations by name or by date and time." msgstr "" #. type: Title ===== -#: ./user-manual.txt:1441 +#: user-manual.txt:1409 #, no-wrap msgid "Start service" msgstr "" #. type: Plain text -#: ./user-manual.txt:1444 -msgid "" -"Initiates the _background service_ following the previously defined " -"settings." +#: user-manual.txt:1412 +msgid "Starts the _background service_ following the previously defined settings." msgstr "" #. type: Title ===== -#: ./user-manual.txt:1445 +#: user-manual.txt:1413 #, no-wrap msgid "Disconnect" msgstr "" #. type: Plain text -#: ./user-manual.txt:1453 +#: user-manual.txt:1421 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." +"This is admittedly a badly named option that disconnects the app from the " +"server. It resets 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 your Android device was " +"used to download the dive locations of another registered diver." msgstr "" #. type: Title ===== -#: ./user-manual.txt:1454 +#: user-manual.txt:1422 #, no-wrap msgid "Send all locations" msgstr "" #. type: Plain text -#: ./user-manual.txt:1457 +#: user-manual.txt:1425 msgid "This option sends all locations stored in the Android device to the server." msgstr "" #. type: Title ==== -#: ./user-manual.txt:1459 +#: user-manual.txt:1427 #, no-wrap msgid "Using the Subsurface companion app on an _iPhone_ to record dive locations" msgstr "" #. type: Plain text -#: ./user-manual.txt:1464 +#: user-manual.txt:1432 msgid "" -"The iPhone interface is quite simple. One needs to type the user ID " -"(obtained during registration) into the space reserved for it, then select " -"\"Dive in\" (see left part of the image below) and start collecting dive " -"location information." +"The iPhone interface is quite simple. Type the user ID (obtained during " +"registration) into the space reserved for it, then select \"Dive in\" (see " +"left part of the image below) and start collecting dive location " +"information." msgstr "" #. type: Target for macro image -#: ./user-manual.txt:1465 +#: user-manual.txt:1433 #, no-wrap msgid "images/iphone.jpg" msgstr "" #. type: Plain text -#: ./user-manual.txt:1472 +#: user-manual.txt:1444 msgid "" "Dives can be added automatically or manually. In manual mode, a dive " "location or waypoint is added to the GPS input stream. In automatic mode, a " -"continuous path of GPS locations is created from which, much later, after " -"import, subsurface can select the appropriate GPS locations based on the " -"times of dives. The default mode for the _iphone_ is automatic. When one " -"adds a dive, the location service is started automatically and a red bar " -"appears at the bottom of the screen. After the dive one can click on the red " -"bar to end the location service. While the location service is running one " -"can only add dives using the manual mechanism." +"continuous path of GPS locations is created from which, after import, " +"Subsurface can select the appropriate GPS locations based on the times of " +"dives. The default mode for the _iphone_ is automatic. When adding a dive, " +"the location service is started automatically and a red bar appears at the " +"bottom of the screen. After the dive, click on the red bar to end the " +"location service. While the location service is running you can only add " +"dives manually." msgstr "" #. type: Plain text -#: ./user-manual.txt:1478 +#: user-manual.txt:1450 msgid "" -"One can edit the site name afterwards by selecting the dive from the dive " +"You can edit the site name afterwards by selecting the dive from the dive " "list and clicking on the site name. There are no other editable fields. The " -"dive list is automatically uploaded from the iPhone to the webservice and " -"there is not an option to trigger upload manually." +"dive list is automatically uploaded from the iPhone to the web " +"service. There isn’t an option to trigger upload manually." msgstr "" #. type: Title ==== -#: ./user-manual.txt:1480 +#: user-manual.txt:1452 #, no-wrap msgid "Downloading dive locations to the _Subsurface_ divelog" msgstr "" #. type: Plain text -#: ./user-manual.txt:1489 +#: user-manual.txt:1461 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 " +"blank. Provide a DIVERID, then select the _Download_ button to start the " "download process, after which the screen on the right (*B*) below appears:" msgstr "" #. type: Target for macro image -#: ./user-manual.txt:1490 +#: user-manual.txt:1462 #, no-wrap msgid "images/DownloadGPS.jpg" msgstr "" #. type: Plain text -#: ./user-manual.txt:1498 +#: user-manual.txt:1470 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." +"Note that the _Apply_ button is now active. By clicking on it, you can " +"update the locations of the newly entered or uploaded dives in " +"_Subsurface_. That applies the coordinates and names entered on the app to " +"all the new dives that match the date-times of the uploaded GPS " +"localities. If you have 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:1505 +#: user-manual.txt:1477 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." +"assignment of GPS data to dives depends on agreeing date-time information " +"between the two devices. Although _Subsurface_ has a wide range tolerance, " +"it may not be able to identify the appropriate dive if there's a large " +"difference between the time in the dive computer and that of the Android " +"device. That results in no updates." msgstr "" #. type: Plain text -#: ./user-manual.txt:1513 +#: user-manual.txt:1485 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 " +"for this (e.g. time zones). _Subsurface_ may also 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." +"subsequent dives as well). A workaround 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:1517 +#: user-manual.txt:1489 msgid "TIPS:" msgstr "" #. type: Plain text -#: ./user-manual.txt:1524 +#: user-manual.txt:1492 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)." +"_Background service_ may fill the location list with unnecessary locations " +"that don’t correspond to the exact dive point but do correspond to the " +"boat's route." msgstr "" #. type: Plain text -#: ./user-manual.txt:1528 +#: user-manual.txt:1493 +msgid "" +"Right now, these locations are difficult to delete from the server. In some " +"situations it" +msgstr "" + +#. type: Plain text +#: user-manual.txt:1496 +msgid "" +"is better 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 you want to keep the " +"location list clear to see dives in the web service map display (see above)." +msgstr "" + +#. type: Plain text +#: user-manual.txt:1499 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 " @@ -2862,28 +2807,28 @@ msgid "" msgstr "" #. type: Title === -#: ./user-manual.txt:1530 +#: user-manual.txt:1501 #, no-wrap msgid "Adding photographs to dives" msgstr "" #. type: Plain text -#: ./user-manual.txt:1536 +#: user-manual.txt:1507 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." +"during a dive. To match each photograph with a specific dive, _Subsurface_ " +"lets you load photos into a dive. Photos are superimposed on the dive " +"profile, from where they can be viewed." msgstr "" #. type: Title ==== -#: ./user-manual.txt:1537 +#: user-manual.txt:1508 #, no-wrap -msgid "Loading photos and getting synchronisation between dive computer and camera" +msgid "Loading photos and synchronizing between dive computer and camera" msgstr "" #. type: Plain text -#: ./user-manual.txt:1541 +#: user-manual.txt:1512 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 " @@ -2891,66 +2836,66 @@ msgid "" msgstr "" #. type: Target for macro image -#: ./user-manual.txt:1542 +#: user-manual.txt:1513 #, no-wrap msgid "images/LoadImage1_f20.jpg" msgstr "" #. type: Plain text -#: ./user-manual.txt:1546 +#: user-manual.txt:1517 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:1547 +#: user-manual.txt:1518 #, no-wrap msgid "images/LoadImage2_f20.jpg" msgstr "" #. type: Plain text -#: ./user-manual.txt:1556 +#: user-manual.txt:1527 msgid "" -"This brings up 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." +"This brings up the time synchronization dialog, shown below. But be aware " +"that the time synchronization 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 synchronize, then the " +"exact times of photographs can be used to position photographs on the dive " +"profile." msgstr "" #. type: Plain text -#: ./user-manual.txt:1558 -msgid "_Subsurface_ achieves this synchronisation in three ways:" +#: user-manual.txt:1529 +msgid "_Subsurface_ synchronizes in three ways:" msgstr "" #. type: Plain text -#: ./user-manual.txt:1561 +#: user-manual.txt:1532 #, no-wrap msgid "" -"*Pro-actively*: Before the dive, ensure synchronisation of the dive computer " +"*Pro-actively*: Before the dive, ensure synchronization of the dive computer " "time settings with\n" "the time settings of the camera by changing the date-time settings on one or " "both of these devices.\n" msgstr "" #. type: Plain text -#: ./user-manual.txt:1572 +#: user-manual.txt:1543 #, 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 " +"*Manually*: If you wrote down the exact camera time at the start of a dive, " +"the\n" +"difference in time between the two devices can be determined. As long as the " +"device\n" +"settings for time has not been changed in either device, you could write " "down the times of\n" -"both devices after the dive or even at the end of the day. One can then " +"both devices after the dive or even at the end of the day. You 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" +"immediately under the heading _Shift times of image(s) by_, shown 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 " @@ -2959,31 +2904,30 @@ msgid "" "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" +"in that tool. Click the _OK_ button and synchronization is done.\n" msgstr "" #. type: Target for macro image -#: ./user-manual.txt:1573 +#: user-manual.txt:1544 #, no-wrap msgid "images/LoadImage3b_f20.jpg" msgstr "" #. type: Plain text -#: ./user-manual.txt:1591 +#: user-manual.txt:1562 #, no-wrap msgid "" -"*By photograph*: There is a very slick way of achieving synchronisation. If " -"one takes a\n" +"*By photograph*: There is a very slick way of synchronizing. If you take 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 " +"_Subsurface_ can get\n" +"the exact time the photograph was taken, using the metadata 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" +"each photo. To do this, use the bottom half of the _Time shift_ dialog. If " +"you use\n" "the bottom part, the top part of the dialog is ignored. Click on\n" -"the horizontal bar entitled \"_Select image of dive computer showing " +"the horizontal bar called \"_Select image of dive computer showing " "time_. This brings up\n" -"a file browser with which one can select the photograph of the dive computer " +"a file browser letting you select the photograph of the dive computer " "time. Select the\n" "photograph using the file browser and click on _OK_. This photograph of the " "dive computer\n" @@ -2991,164 +2935,162 @@ msgid "" "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" +"so it 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.\n" +"camera and dive computer is, and it can synchronize.\n" "Image *B* above shows a photograph of the face of the dive computer and with " "the date-time tool set to the\n" "date-time.\n" msgstr "" #. type: Plain text -#: ./user-manual.txt:1594 +#: user-manual.txt:1565 msgid "" "If the timestamp of a photograph is more than 30 minutes before or after the " "dive, it is not placed on the dive profile." msgstr "" #. type: Title ==== -#: ./user-manual.txt:1595 +#: user-manual.txt:1566 #, no-wrap msgid "Viewing the photos" msgstr "" #. type: Plain text -#: ./user-manual.txt:1598 +#: user-manual.txt:1569 msgid "After the images have been loaded, they appear in two places:" msgstr "" #. type: Plain text -#: ./user-manual.txt:1600 +#: user-manual.txt:1571 msgid "the _Photos_ tab of the *Notes* panel." msgstr "" #. type: Plain text -#: ./user-manual.txt:1604 +#: user-manual.txt:1575 msgid "" "as tiny icons (stubs) on the dive profile at the appropriate positions " -"reflecting the time each photograph was taken. In order to view the photos " -"on the dive profile, activate the _show-photos_ button in the tool bar to " -"the left of the dive profile:" +"reflecting the time each photograph was taken. To view the photos on the " +"dive profile, 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:1605 +#: user-manual.txt:1576 #, no-wrap msgid "images/icons/ShowPhotos_f20.png" msgstr "" #. type: Plain text -#: ./user-manual.txt:1608 +#: user-manual.txt:1579 msgid "This results in a profile display as in the image below:" msgstr "" #. type: Target for macro image -#: ./user-manual.txt:1609 +#: user-manual.txt:1580 #, no-wrap msgid "images/LoadImage4_f20.jpg" msgstr "" #. type: Plain text -#: ./user-manual.txt:1613 +#: user-manual.txt:1584 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:" +"If you hover the mouse over any of the photo icons, a thumbnail photo is " +"shown of the appropriate photo. See the image below:" msgstr "" #. type: Target for macro image -#: ./user-manual.txt:1614 +#: user-manual.txt:1585 #, no-wrap msgid "images/LoadImage5_f20.jpg" msgstr "" #. type: Plain text -#: ./user-manual.txt:1623 +#: user-manual.txt:1594 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)." +"_Subsurface_ window. This allows good viewing of the added photographs. (see " +"the image below). Note that the thumbnail has a small dustbin icon in the " +"bottom right hand corner (see image above). Selecting the dustbin removes " +"the image from the dive. Be careful 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:1624 +#: user-manual.txt:1595 #, no-wrap msgid "images/LoadImage6_f20.jpg" msgstr "" #. type: Title ==== -#: ./user-manual.txt:1626 +#: user-manual.txt:1597 #, no-wrap msgid "The _Photos_ tab" msgstr "" #. type: Plain text -#: ./user-manual.txt:1637 +#: user-manual.txt:1608 msgid "" "Photographs associated with a dive are shown as thumbnails in the _Photos_ " "tab of the _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." +"accessing the photos of a dive, while the stubs on the dive profile show " +"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:1638 +#: user-manual.txt:1609 #, no-wrap msgid "Photos on an external hard disk" msgstr "" #. type: Plain text -#: ./user-manual.txt:1649 +#: user-manual.txt:1619 msgid "" -"Most underwater photographers store their photos on an external drive. If " -"such a drive can be mapped by the operating system (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." +"Most underwater photographers store photos on an external drive. If such a " +"drive can be mapped by the operating system (almost always the case) the " +"photos can be directly accessed by _Subsurface_. This eases 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 synchronization (see text above) is used. 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. If the external drive with the photos " +"is re-connected, the photos can be seen in the normal way." msgstr "" #. type: Title ==== -#: ./user-manual.txt:1651 +#: user-manual.txt:1621 #, no-wrap msgid "Moving photographs among directories, hard disks or computers" msgstr "" #. type: Plain text -#: ./user-manual.txt:1661 +#: user-manual.txt:1631 #, no-wrap msgid "" "After a photograph has been loaded into _Subsurface_ and associated with a " "specific dive, the directory\n" -" where the photo lies is stored, allowing _Subsurface_ to find the " -"photograph when the dive is\n" +" where the photo lies is stored, letting _Subsurface_ find the photograph " +"when the dive is\n" " opened again. If the photo or the whole photo collection is moved to " "another drive or to a different\n" -" machine, it is unlikely that the directory structure will remain identical " -"to that of the original uploaded\n" +" machine, the directory structure will be different to that of the original " +"uploaded\n" " photo. When this happens, _Subsurface_ looks for the photos at their " "original location before they were moved,\n" -" cannot find them and therefore cannot display them. Because, after moving " -"photos, large numbers of photos\n" +" cannot find them and cannot display them. Because after moving photos, " +"large numbers of photos\n" " may need to be deleted and re-imported from the new location, _Subsurface_ " "has a mechanism that eases the\n" " process of updating the directory information for each photo: automatic " @@ -3156,7 +3098,7 @@ msgid "" msgstr "" #. type: Plain text -#: ./user-manual.txt:1666 +#: user-manual.txt:1635 #, no-wrap msgid "" "When a photo is loaded into _Subsurface_, a fingerprint for the image is " @@ -3164,47 +3106,41 @@ msgid "" " other reference information for that photo. After moving a photo collection " "(that has already been loaded\n" " into _Subsurface_) to a different directory, disk or computer, _Subsurface_ " -"can perform the\n" -" following steps:\n" +"can:\n" msgstr "" #. type: Plain text -#: ./user-manual.txt:1668 +#: user-manual.txt:1638 msgid "" "look through a particular directory (and all its subdirectories recursively) " -"where photos have been moved" +"where photos have been moved to," msgstr "" #. type: Plain text -#: ./user-manual.txt:1669 -msgid "to," -msgstr "" - -#. type: Plain text -#: ./user-manual.txt:1671 +#: user-manual.txt:1639 msgid "calculate fingerprints for all photos in this directory, and" msgstr "" #. type: Plain text -#: ./user-manual.txt:1673 +#: user-manual.txt:1641 msgid "" "if there is a match between a calculated fingerprint and the one originally " "calculated when a photo was" msgstr "" #. type: Plain text -#: ./user-manual.txt:1675 +#: user-manual.txt:1643 msgid "" -"loaded into _Subsurface_ (even if the original file name has changed), to " +"loaded into _Subsurface_ (even if the original file name has changed), " "automatically update the directory information so that _Subsurface_ can find " "the photo in the new moved directory." msgstr "" #. type: Plain text -#: ./user-manual.txt:1680 +#: user-manual.txt:1648 #, no-wrap msgid "" -"This is achieved by selecting from the Main Menu: _File -> Find moved " +"This is done by selecting from the Main Menu: _File -> Find moved " "images_. This brings up a window within\n" " which the NEW directory of the photos needs to be specified. Select the " "appropriate directory and click\n" @@ -3215,83 +3151,82 @@ msgid "" msgstr "" #. type: delimited block * -#: ./user-manual.txt:1685 +#: user-manual.txt:1653 #, no-wrap msgid "*Upgrading existing photo collections without fingerprints*\n" msgstr "" #. type: delimited block * -#: ./user-manual.txt:1690 +#: user-manual.txt:1658 msgid "" -"_Subsurface_ automatically calculates fingerprints for all images that can " -"be accessed by _Subsurface_. When manipulating images, ensure that all the " -"images associated with the dive log can be accessed by _Subsurface_." +"_Subsurface_ automatically calculates fingerprints for all images that it " +"can access. When manipulating images, be sure all the images associated " +"with the dive log can be accessed by _Subsurface_." msgstr "" #. type: delimited block * -#: ./user-manual.txt:1692 +#: user-manual.txt:1660 msgid "" "_Subsurface_ automatically checks and, if necessary, updates the " "fingerprints associated with a single dive if:" msgstr "" #. type: delimited block * -#: ./user-manual.txt:1693 +#: user-manual.txt:1661 msgid "" "The images associated with that dive are visible as thumbnails on the *Dive " "Profile*." msgstr "" #. type: delimited block * -#: ./user-manual.txt:1694 +#: user-manual.txt:1662 msgid "" -"One edits anything in the *Notes tab* panel and save the edits by selecting " -"_Apply changes_." +"If you edit anything in the *Notes tab* panel and save the edits by " +"selecting _Apply changes_." msgstr "" #. type: Title === -#: ./user-manual.txt:1698 +#: user-manual.txt:1666 #, no-wrap msgid "Logging special types of dives" msgstr "" #. type: Title ==== -#: ./user-manual.txt:1701 +#: user-manual.txt:1669 #, no-wrap msgid "Multicylinder dives" msgstr "" #. type: Plain text -#: ./user-manual.txt:1708 +#: user-manual.txt:1676 msgid "" "_Subsurface_ easily handles dives involving more than one " -"cylinder. Multi-cylinder diving usually happens (a) if a diver does not have " -"enough gas for the complete dive in a single cylinder; (b) if the diver " -"needs more than one gas mixture because of the depth or the decompression " -"needs of the dive. For this reason multi-cylinder dives are often used by " -"technical divers who dive deep or long. As far as _Subsurface_ is concerned, " -"there are only two types of information that need to be provided:" +"cylinder. Multi-cylinder diving usually happens (a) if a diver doesn’t have " +"enough gas for the complete dive in a single cylinder; (b) if a diver needs " +"more than one gas mixture because of the depth or the decompression needs of " +"the dive. For this reason multi-cylinder dives are often used by technical " +"divers who dive deep or long. As far as _Subsurface_ is concerned, there are " +"only two types of information that need to be provided:" msgstr "" #. type: Plain text -#: ./user-manual.txt:1712 +#: user-manual.txt:1680 #, no-wrap msgid "" "*Describe the cylinders used during the dive* This is performed in the " "*Equipment tab* of\n" "the *Info* panel, as xref:cylinder_definitions[described above]. Enter the " "cylinders one by one,\n" -"specifying the characteristics of the cylinder and the gas composition " -"within each cylinder.\n" +"specifying each’s characteristics and the gas composition within it.\n" msgstr "" #. type: Plain text -#: ./user-manual.txt:1717 +#: user-manual.txt:1685 #, no-wrap msgid "" -"*Record the times at which switches from one cylinder to another was done:* " -"This is information\n" -"provided by some dive computers (provided the diver indicated these changes " +"*Record the times at which the switch from one cylinder to another was " +"done:* This is information\n" +"tracked by some dive computers (provided the diver indicated these changes " "to the dive computer\n" "by pressing specific buttons). If the dive computer does not provide the " "information, the diver has to\n" @@ -3299,7 +3234,7 @@ msgid "" msgstr "" #. type: Plain text -#: ./user-manual.txt:1725 +#: user-manual.txt:1693 #, no-wrap msgid "" "*Record the cylinder changes on the dive profile*: If the latter option\n" @@ -3316,61 +3251,60 @@ msgid "" msgstr "" #. type: Plain text -#: ./user-manual.txt:1729 +#: user-manual.txt:1697 msgid "" -"Having performed these tasks, _Subsurface_ indicates the appropriate use of " +"When this is complete, _Subsurface_ indicates the appropriate use of " "cylinders in the dive profile. Below is a multi-cylinder dive, starting off " -"with EAN28, then changing cylinders to EAN50 after 26 minutes to perform " +"with EAN28, then changing cylinders to EAN50 after 26 minutes for " "decompression." msgstr "" #. type: Target for macro image -#: ./user-manual.txt:1730 +#: user-manual.txt:1698 #, no-wrap msgid "images/multicylinder_dive.jpg" msgstr "" #. type: Title ==== -#: ./user-manual.txt:1732 +#: user-manual.txt:1700 #, no-wrap msgid "Sidemount dives" msgstr "" #. type: Plain text -#: ./user-manual.txt:1738 +#: user-manual.txt:1706 msgid "" "Sidemount diving is just another form of multi-cylinder diving, often with " -"both or all cylinders having the same gas mixture. Although it is a popular " -"configuration for cave divers, sidemount diving can be performed by " -"recreational divers who have completed the appropriate training. Sidemount " -"dive logging involves, exactly as with multi-cylinder dives, above, three " -"steps:" +"both or all cylinders having the same gas mixture. Although it’s a popular " +"configuration for cave divers, Sidemount diving can be done by recreational " +"divers who’ve completed the appropriate training. sidemount dive logging " +"involves three steps, exactly as with multi-cylinder dives above:" msgstr "" #. type: Plain text -#: ./user-manual.txt:1747 +#: user-manual.txt:1715 #, no-wrap msgid "" "*During the dive, record 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" +"between these different\n" "cylinders. In contrast, many dive computers that allow gas switching only " -"distinguish among different\n" -"_gases_ used, not among different _cylinders_ used. This means that when " +"distinguish between different\n" +"_gases_ used, not among different _cylinders_ used. This means 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 " +"from these dive computers, the switching event between cylinders with the " +"same gas is not downloaded. This may mean\n" +"that a diver 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 " +"has the capability) marking each cylinder switch with a bookmark that can be " "retrieved later. Returning\n" "from a dive with the times of cylinder changes is the only tricky part of " "logging sidemount dives.\n" msgstr "" #. type: Plain text -#: ./user-manual.txt:1750 +#: user-manual.txt:1718 #, no-wrap msgid "" "*Within _Subsurface_ describe the cylinders used during the dive*. The diver " @@ -3381,85 +3315,85 @@ msgid "" msgstr "" #. type: Plain text -#: ./user-manual.txt:1760 +#: user-manual.txt:1728 #, 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" +"be shown on the dive profile.\n" "Cylinder changes are recorded by right-clicking at the appropriate point on " -"the dive profile and then\n" +"the dive profile, 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" +"shown 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" +"profile, then the cylinder change is also shown 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 in the image below.\n" msgstr "" #. type: Target for macro image -#: ./user-manual.txt:1761 +#: user-manual.txt:1729 #, no-wrap msgid "images/sidemount1.jpg" msgstr "" #. type: Plain text -#: ./user-manual.txt:1764 +#: user-manual.txt:1732 msgid "" "This section gives an example of the versatility of _Subsurface_ as a dive " "logging tool." msgstr "" #. type: Title ==== -#: ./user-manual.txt:1767 +#: user-manual.txt:1735 #, no-wrap msgid "Semi-closed circuit rebreather (SCR) dives" msgstr "" #. type: Named 'icon' AttributeList argument for style 'icon' -#: ./user-manual.txt:1769 +#: user-manual.txt:1737 #, no-wrap msgid "images/halcyon_RB80.jpg" msgstr "" #. type: Plain text -#: ./user-manual.txt:1779 +#: user-manual.txt:1747 msgid "" -"Passive semi-closed rebreathers (pSCR) comprise a technical advance in " -"diving equipment that recirculates the breathing gas that a diver breathes, " -"while removing carbon dioxide from the exhaled gas. While a small amount " -"(typically a tenth) of the exhaled breathing gas is released into the water, " -"a small amount of fresh gas is released from the back gas cylinder " -"(typically containing nitrox). A diver, using a single cylinder of " -"breathing gas can therefore dive for much longer periods than using a " -"recreational open-circuit configuration. With pSCR equipment, a very small " -"amount of breathing gas is released every time the breather inhales. With " -"active SCR (aSCR) equipment, in contrast, a small amount of breathing gas is " -"released continuously from the back cylinder." +"Passive semi-closed rebreathers (pSCR) are a technical advance in diving " +"equipment that recirculates the breathing gas a diver uses, while removing " +"carbon dioxide from the exhaled gas. While a small amount (typically a " +"tenth) of the exhaled breathing gas is released into the water, a small " +"amount of fresh gas is released from the back gas cylinder (typically " +"containing nitrox). A diver using a single cylinder of breathing gas can " +"therefore dive for much longer periods than using a recreational " +"open-circuit configuration. With pSCR equipment, a very small amount of " +"breathing gas is released every time the diver inhales. With active SCR " +"(aSCR) equipment, in contrast, a small amount of breathing gas is released " +"continuously from the back cylinder." msgstr "" #. type: Plain text -#: ./user-manual.txt:1781 +#: user-manual.txt:1749 msgid "" -"To log pSCR dives, no special procedures are required, just the normal steps " +"To log pSCR dives, no special procedures are required. Use the normal steps " "outlined above:" msgstr "" #. type: Plain text -#: ./user-manual.txt:1783 +#: user-manual.txt:1751 msgid "Select pSCR in the _Dive Mode_ dropdown list on the *Info* panel." msgstr "" #. type: Plain text -#: ./user-manual.txt:1787 +#: user-manual.txt:1755 msgid "" "pSCR diving often involves gas changes, requiring an additional cylinder. " "Define all the appropriate cylinders as described above and indicate the " @@ -3468,48 +3402,48 @@ msgid "" msgstr "" #. type: Plain text -#: ./user-manual.txt:1792 +#: user-manual.txt:1760 msgid "" -"If a pSCR _Dive Mode_ has been selected, the dive ceiling for pSCR dives is " -"adjusted for the oxygen drop across the mouthpiece which often requires " +"If a pSCR _Dive Mode_ has been selected, the dive ceiling for that is " +"adjusted for the oxygen drop across the mouthpiece, which often requires " "longer decompression periods. Below is a dive profile of a pSCR dive using " "EAN36 on the back cylinder and oxygen for decompression. Note that this dive " "lasted over two hours." msgstr "" #. type: Target for macro image -#: ./user-manual.txt:1793 +#: user-manual.txt:1761 #, no-wrap msgid "images/pSCR_profile.jpg" msgstr "" #. type: Title ==== -#: ./user-manual.txt:1798 +#: user-manual.txt:1766 #, no-wrap msgid "Closed circuit rebreather (CCR) dives" msgstr "" #. type: Named 'icon' AttributeList argument for style 'icon' -#: ./user-manual.txt:1800 +#: user-manual.txt:1768 #, no-wrap msgid "images/APD.jpg" msgstr "" #. type: Plain text -#: ./user-manual.txt:1805 +#: user-manual.txt:1773 msgid "" "Closed system rebreathers use advanced technology to recirculate gas that " -"has been breathed while doing two things to maintain a breathable oxygen " +"has been breathed. They also do two things to maintain a breathable oxygen " "concentration:" msgstr "" #. type: Plain text -#: ./user-manual.txt:1806 -msgid "remove carbon dioxide from the gas that has been exhaled" +#: user-manual.txt:1774 +msgid "remove carbon dioxide from the exhaled gas" msgstr "" #. type: Plain text -#: ./user-manual.txt:1815 +#: user-manual.txt:1783 msgid "" "regulate the oxygen concentration to remain within safe diving limits. The " "CCR interface of _Subsurface_ is currently experimental and under active " @@ -3519,18 +3453,18 @@ msgid "" "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 digital databases: one " -"dive at a time." +"same way it imports dive log data from other digital databases: one dive at " +"a time." msgstr "" #. type: Title ===== -#: ./user-manual.txt:1816 +#: user-manual.txt:1784 #, no-wrap msgid "Import a CCR dive" msgstr "" #. type: Plain text -#: ./user-manual.txt:1830 +#: user-manual.txt:1798 msgid "" "See the section dealing with xref:S_ImportingAlienDiveLogs[Importing dive " "information from other digital sources]. From the main menu of _Subsurface_, " @@ -3538,24 +3472,24 @@ msgid "" "xref:Unified_import[universal import dialogue]. As explained in that " "section, the bottom right hand of the import dialogue contains a dropdown " "list (labled _Filter:_) of appropriate devices that currently " -"includes(Poseidon) MkVI or APD log viewer files (import for other CCR " -"equipment is under active development). Having selected the appropriate CCR " +"include(Poseidon) MkVI or APD log viewer files. Import for other CCR " +"equipment is under active development. 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. The selected dive is imported to the " -"_Subsurface_ dive list." +"the CCR dive computer, 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, click the _Open_ button at the bottom right hand of the universal " +"import dialogue. The selected dive is imported to the _Subsurface_ dive " +"list." msgstr "" #. type: Title ===== -#: ./user-manual.txt:1831 +#: user-manual.txt:1799 #, no-wrap msgid "Displayed information for a CCR dive" msgstr "" #. type: Plain text -#: ./user-manual.txt:1841 +#: user-manual.txt:1809 msgid "" "_Partial pressures of gases_: The graph of oxygen partial pressure shows the " "information from the oxygen sensors of the CCR equipment. In contrast to " @@ -3569,68 +3503,68 @@ msgid "" msgstr "" #. type: Plain text -#: ./user-manual.txt:1843 +#: user-manual.txt:1811 msgid "For TWO O~2~ sensors the mean value of the two sensors are given." msgstr "" #. type: Plain text -#: ./user-manual.txt:1847 +#: user-manual.txt:1815 msgid "" "For THREE-sensor systems (e.g. APD), the mean value is also used. However " "differences of more than 0,1 bar in the simultaneous readings of different " -"sensors are treated as spurious. If one of the three sensors provides " -"spurious data, it is ignored." +"sensors are treated as false. If one of the three sensors provides false " +"data, it is ignored." msgstr "" #. type: Plain text -#: ./user-manual.txt:1849 +#: user-manual.txt:1817 msgid "" "If no sensor data are available, the pO~2~ value is assumed to be equal to " "the setpoint." msgstr "" #. type: Plain text -#: ./user-manual.txt:1851 +#: user-manual.txt:1819 msgid "The mean pO~2~ of the sensors is indicated with a green line," msgstr "" #. type: Plain text -#: ./user-manual.txt:1859 +#: user-manual.txt:1827 msgid "" "The oxygen setpoint values as well as the readings from the individual " "oxygen sensors can be shown. The display of additional CCR information is " -"turned on by checking the appropriate checkboxes in the _Preferences_ panel " +"turned on by checking the appropriate boxes in the _Preferences_ panel " "(accessible by selecting xref:S_CCR_options[_File -> Preferences -> " "Graph_]). This part of the _Preferences_ panel is shown in the image below, " "representing two checkboxes that modify the display of pO~2~ when the " -"appropriate toolbar button on the Dive Profile has been activated." +"appropriate toolbar button on the Dive Profile has been checked." msgstr "" #. type: Target for macro image -#: ./user-manual.txt:1860 +#: user-manual.txt:1828 #, no-wrap msgid "images/CCR_preferences_f20.jpg" msgstr "" #. type: Plain text -#: ./user-manual.txt:1867 +#: user-manual.txt:1835 msgid "" -"Checking any of these check boxes allows the display of additional " -"oxygen-related information whenever the pO~2~ toolbar button on the " -"_Profile_ panel is activated. The first checkbox allows the display of " -"setpoint information. This is a red line superimposed on the green oxygen " -"partial pressure graph and allows a comparison of the mean measured oxygen " -"partial pressure and the setpoint values, as shown below." +"Checking any of these boxes allows the display of additional oxygen-related " +"information whenever the pO~2~ toolbar button on the _Profile_ panel is " +"activated. The first checkbox allows the display of setpoint " +"information. This is a red line superimposed on the green oxygen partial " +"pressure graph and allows a comparison of the mean measured oxygen partial " +"pressure and the setpoint values, as shown below." msgstr "" #. type: Target for macro image -#: ./user-manual.txt:1868 +#: user-manual.txt:1836 #, no-wrap msgid "images/CCR_setpoint_f20.jpg" msgstr "" #. type: Plain text -#: ./user-manual.txt:1872 +#: user-manual.txt:1840 msgid "" "The second checkbox allows the display of the data from each individual " "oxygen sensor of the CCR equipment. The data for each sensor is colour-coded " @@ -3638,22 +3572,22 @@ msgid "" msgstr "" #. type: Plain text -#: ./user-manual.txt:1874 +#: user-manual.txt:1842 msgid "Sensor 1: grey" msgstr "" #. type: Plain text -#: ./user-manual.txt:1875 +#: user-manual.txt:1843 msgid "Sensor 2: blue" msgstr "" #. type: Plain text -#: ./user-manual.txt:1876 +#: user-manual.txt:1844 msgid "Sensor 3: brown" msgstr "" #. type: Plain text -#: ./user-manual.txt:1880 +#: user-manual.txt:1848 msgid "" "The mean oxygen pO~2~ is indicated by the green line. This allows the direct " "comparison of data from each of the oxygen sensors, useful for detecting " @@ -3661,13 +3595,13 @@ msgid "" msgstr "" #. type: Target for macro image -#: ./user-manual.txt:1881 +#: user-manual.txt:1849 #, no-wrap msgid "images/CCR_sensor_data_f20.jpg" msgstr "" #. type: Plain text -#: ./user-manual.txt:1886 +#: user-manual.txt:1854 msgid "" "The setpoint data can be overlaid on the oxygen sensor data by activating " "both of the above check boxes. Partial pressures for nitrogen (and helium, " @@ -3675,7 +3609,7 @@ msgid "" msgstr "" #. type: Plain text -#: ./user-manual.txt:1890 +#: user-manual.txt:1858 msgid "" "_Events_: Several events are logged, e.g. switching the mouthpiece to open " "circuit. These events are indicated by yellow triangles and, if one hovers " @@ -3684,7 +3618,7 @@ msgid "" msgstr "" #. type: Plain text -#: ./user-manual.txt:1898 +#: user-manual.txt:1866 msgid "" "_Cylinder pressures_: Some CCR dive computers like the Poseidon MkVI record " "the pressures of the oxygen and diluent cylinders. The pressures of these " @@ -3692,18 +3626,18 @@ msgid "" "addition, start and end pressures for both oxygen and diluent cylinders are " "shown in the _Equipment Tab_. Below is a dive profile for a CCR dive, " "including an overlay of setpoint and oxygen sensor data, as well as the " -"cylinder pressure data. In this case there is good agreement from the " -"readings of the two oxygen sensors." +"cylinder pressure data. In this case there is agreement from the readings of " +"the two oxygen sensors." msgstr "" #. type: Target for macro image -#: ./user-manual.txt:1899 +#: user-manual.txt:1867 #, no-wrap msgid "images/CCR_dive_profile_f22.jpg" msgstr "" #. type: Plain text -#: ./user-manual.txt:1904 +#: user-manual.txt:1872 msgid "" "_Equipment-specific information_: Equipment-specific information gathered by " "_Subsurface_ is shown in the xref:S_ExtraDataTab[Extra data tab]. This may " @@ -3711,7 +3645,7 @@ msgid "" msgstr "" #. type: Plain text -#: ./user-manual.txt:1910 +#: user-manual.txt:1878 msgid "" "The deco ceiling calculated by Subsurface is not very accurate because the " "precise pressure of nitrogen in the loop can usually not be determined from " @@ -3723,28 +3657,28 @@ msgid "" msgstr "" #. type: Named 'icon' AttributeList argument for style 'icon' -#: ./user-manual.txt:1911 ./user-manual.txt:2094 +#: user-manual.txt:1879 user-manual.txt:2058 #, no-wrap msgid "images/icons/cceiling.jpg" msgstr "" #. type: Plain text -#: ./user-manual.txt:1916 +#: user-manual.txt:1884 msgid "" -"The default colour of the computer-generated deco ceiling is white. However, " -"this can be set to red by checking the appropriate check box after selecting " -"_File -> Preferences -> Graph_. Below is a dive profile indicating the dive " +"The default color of the computer-generated deco ceiling is white. This can " +"be set to red by checking the appropriate check box after selecting _File -> " +"Preferences -> Graph_. Below is a dive profile indicating the dive " "computer-generated deco ceiling:" msgstr "" #. type: Target for macro image -#: ./user-manual.txt:1917 +#: user-manual.txt:1885 #, no-wrap msgid "images/CCR_dive_ceilingF22.jpg" msgstr "" #. type: Plain text -#: ./user-manual.txt:1921 +#: user-manual.txt:1889 msgid "" "More equipment-specific information for downloading CCR dive logs for " "Poseidon MkVI and APD equipment can be found in " @@ -3753,19 +3687,19 @@ msgid "" msgstr "" #. type: Title == -#: ./user-manual.txt:1922 +#: user-manual.txt:1890 #, no-wrap msgid "Obtaining more information about dives entered into the logbook" msgstr "" #. type: Title === -#: ./user-manual.txt:1924 +#: user-manual.txt:1892 #, no-wrap msgid "The *Info* tab (for individual dives)" msgstr "" #. type: Plain text -#: ./user-manual.txt:1931 +#: user-manual.txt:1899 msgid "" "The Info tab gives some summary information about a particular dive that has " "been selected in the *Dive List*. Useful information here includes the " @@ -3775,7 +3709,7 @@ msgid "" msgstr "" #. type: Plain text -#: ./user-manual.txt:1938 +#: user-manual.txt:1906 msgid "" "Gas consumption and SAC calculations: _Subsurface_ calculates SAC and Gas " "consumption taking in account gas incompressibility, particularly at tank " @@ -3784,13 +3718,13 @@ msgid "" msgstr "" #. type: Title === -#: ./user-manual.txt:1940 +#: user-manual.txt:1908 #, no-wrap msgid "The *Extra Data* tab (usually for individual dives)" msgstr "" #. type: Plain text -#: ./user-manual.txt:1948 +#: user-manual.txt:1916 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 " @@ -3802,60 +3736,60 @@ msgid "" msgstr "" #. type: Target for macro image -#: ./user-manual.txt:1949 +#: user-manual.txt:1917 #, no-wrap msgid "images/ExtraDataTab_f20.jpg" msgstr "" #. type: Title === -#: ./user-manual.txt:1951 +#: user-manual.txt:1919 #, no-wrap msgid "The *Stats* tab (for groups of dives)" msgstr "" #. type: Plain text -#: ./user-manual.txt:1962 +#: user-manual.txt:1930 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 " +"figures for 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:1964 +#: user-manual.txt:1932 #, no-wrap msgid "The *Dive Profile*" msgstr "" #. type: Target for macro image -#: ./user-manual.txt:1966 +#: user-manual.txt:1934 #, no-wrap msgid "images/Profile2.jpg" msgstr "" #. type: Plain text -#: ./user-manual.txt:1977 +#: user-manual.txt:1945 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 " +"the left hand side that lets you control 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:" +"Profile is the graph of dive depth as a function of time. In addition to " +"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 colors:" msgstr "" #. type: delimited block | -#: ./user-manual.txt:1984 +#: user-manual.txt:1952 #, no-wrap msgid "" -"|*Colour*|*Descent speed (m/min)*|*Ascent speed (m/min)*\n" +"|*Color*|*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" @@ -3864,31 +3798,31 @@ msgid "" msgstr "" #. type: Plain text -#: ./user-manual.txt:1989 +#: user-manual.txt:1957 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 " +"graph. So users should see the depth of the deepest point and other " "peaks. Mean depth is plotted as a grey line, indicating mean dive depth up " "to a particular moment during the dive." msgstr "" #. type: Named 'icon' AttributeList argument for style 'icon' -#: ./user-manual.txt:1990 +#: user-manual.txt:1958 #, no-wrap msgid "images/icons/scale.jpg" msgstr "" #. type: Plain text -#: ./user-manual.txt:1995 +#: user-manual.txt:1963 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." +"the dive profile increases the size of the dive profile to fill the area of " +"the panel." msgstr "" #. type: Plain text -#: ./user-manual.txt:1998 +#: user-manual.txt:1966 #, no-wrap msgid "" "*Water temperature* is displayed with its own blue line with temperature " @@ -3897,80 +3831,80 @@ msgid "" msgstr "" #. type: Plain text -#: ./user-manual.txt:2005 +#: user-manual.txt:1973 msgid "" "The dive profile can include graphs of the *partial pressures* of O~2~, " "N~2~, 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." +"nitrogen in black, and 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:2006 +#: user-manual.txt:1974 #, no-wrap msgid "images/icons/O2.jpg" msgstr "" #. type: Plain text -#: ./user-manual.txt:2010 +#: user-manual.txt:1978 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 " +"during the dive. This is shown below the dive depth and water temperature " "graphs." msgstr "" #. type: Named 'icon' AttributeList argument for style 'icon' -#: ./user-manual.txt:2011 +#: user-manual.txt:1979 #, no-wrap msgid "images/icons/N2.jpg" msgstr "" #. type: Plain text -#: ./user-manual.txt:2014 +#: user-manual.txt:1982 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:2015 +#: user-manual.txt:1983 #, no-wrap msgid "images/icons/He.jpg" msgstr "" #. type: Plain text -#: ./user-manual.txt:2019 +#: user-manual.txt:1987 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." +"during the dive. This is only important to divers using Trimix, Helitrox or " +"similar breathing gasses." msgstr "" #. type: Plain text -#: ./user-manual.txt:2032 +#: user-manual.txt:2000 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 " +"manually entering the start and end pressures the graph, is not a straight " +"line. Like the depth graph, the slope of the tank pressure gives you " +"information about the momentary SAC rate (Surface Air Consumption) when " +"using an air integrated dive computer. Here the color coding is not " +"relative to some absolute values but relative to the average normalized 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:2033 +#: user-manual.txt:2001 #, no-wrap msgid "images/icons/Heartbutton.png" msgstr "" #. type: Plain text -#: ./user-manual.txt:2037 +#: user-manual.txt:2005 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 " @@ -3978,7 +3912,7 @@ msgid "" msgstr "" #. type: Plain text -#: ./user-manual.txt:2045 +#: user-manual.txt:2012 #, no-wrap msgid "" "It is possible to *zoom* into the profile graph. This is done either by " @@ -3987,80 +3921,78 @@ msgid "" "_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" +" (100ft) – this way short or shallow dives are easily recognizable;\n" +"something free divers won’t care about.\n" msgstr "" #. type: Target for macro image -#: ./user-manual.txt:2046 +#: user-manual.txt:2012 #, no-wrap msgid "images/MeasuringBar.png" msgstr "" #. type: Named 'icon' AttributeList argument for style 'icon' -#: ./user-manual.txt:2048 +#: user-manual.txt:2014 #, no-wrap msgid "images/icons/ruler.jpg" msgstr "" #. type: Plain text -#: ./user-manual.txt:2056 +#: user-manual.txt:2022 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." +"done by dragging the red dots to the two points on the dive profile that you " +"wish 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:2057 +#: user-manual.txt:2023 #, no-wrap msgid "images/icons/ShowPhotos.png" msgstr "" #. type: Plain text -#: ./user-manual.txt:2064 +#: user-manual.txt:2030 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 " +"shows 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:2093 +#: user-manual.txt:2057 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 " +"ceilings occur 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: Plain text -#: ./user-manual.txt:2099 +"available for download; for example none of the Suunto dive computers make " +"these 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’s 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’s 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 because _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 a specific deco stop. This feature lets dive " +"computers offer longer non-stop bottom times." +msgstr "" + +#. type: Plain text +#: user-manual.txt:2063 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 " @@ -4068,13 +4000,13 @@ msgid "" msgstr "" #. type: Named 'icon' AttributeList argument for style 'icon' -#: ./user-manual.txt:2100 +#: user-manual.txt:2064 #, no-wrap msgid "images/icons/ceiling1.jpg" msgstr "" #. type: Plain text -#: ./user-manual.txt:2105 +#: user-manual.txt:2069 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 " @@ -4083,13 +4015,13 @@ msgid "" msgstr "" #. type: Named 'icon' AttributeList argument for style 'icon' -#: ./user-manual.txt:2106 +#: user-manual.txt:2070 #, no-wrap msgid "images/icons/ceiling2.jpg" msgstr "" #. type: Plain text -#: ./user-manual.txt:2110 +#: user-manual.txt:2074 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 " @@ -4097,56 +4029,55 @@ msgid "" msgstr "" #. type: Named 'icon' AttributeList argument for style 'icon' -#: ./user-manual.txt:2111 +#: user-manual.txt:2075 #, no-wrap msgid "images/icons/ceiling3.jpg" msgstr "" #. type: Plain text -#: ./user-manual.txt:2115 +#: user-manual.txt:2079 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:2116 +#: user-manual.txt:2080 #, no-wrap msgid "images/Ceilings2.jpg" msgstr "" #. type: Named 'icon' AttributeList argument for style 'icon' -#: ./user-manual.txt:2118 +#: user-manual.txt:2082 #, no-wrap msgid "images/icons/ShowCylindersButton.jpg" msgstr "" #. type: Plain text -#: ./user-manual.txt:2124 +#: user-manual.txt:2088 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." +"represented as a colored bar at the bottom of the *Dive Profile*. In general " +"oxygen is represented by a green bar, nitrogen a yellow bar and helium 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:2125 +#: user-manual.txt:2089 #, no-wrap msgid "images/ShowCylinders_f20.jpg" msgstr "" #. type: Named 'icon' AttributeList argument for style 'icon' -#: ./user-manual.txt:2128 +#: user-manual.txt:2092 #, no-wrap msgid "images/tissues.jpg" msgstr "" #. type: Plain text -#: ./user-manual.txt:2140 +#: user-manual.txt:2105 msgid "" "Display inert gas tissue pressures relative to ambient inert gas pressure " "(horizontal grey line). Tissue pressures are calculated using the Bühlmann " @@ -4154,24 +4085,23 @@ msgid "" "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 contrast, " -"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." +"divers doing planned decompression diving, efficient rates of offgassing 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 contrast, 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, at the position of the cursor on the dive profile." msgstr "" #. type: Target for macro image -#: ./user-manual.txt:2141 +#: user-manual.txt:2106 #, no-wrap msgid "images/tissuesGraph.jpg" msgstr "" #. type: Plain text -#: ./user-manual.txt:2149 +#: user-manual.txt:2114 msgid "" "Gradient Factor settings strongly affect the calculated ceilings and their " "depths. For more information about Gradient factors, see the section on " @@ -4184,7 +4114,7 @@ msgid "" msgstr "" #. type: Plain text -#: ./user-manual.txt:2151 +#: user-manual.txt:2116 #, no-wrap msgid "" " ** http://www.tek-dive.com/portal/upload/M-Values.pdf[Understanding " @@ -4192,7 +4122,7 @@ msgid "" msgstr "" #. type: Plain text -#: ./user-manual.txt:2153 +#: user-manual.txt:2118 #, no-wrap msgid "" " ** " @@ -4201,43 +4131,43 @@ msgid "" msgstr "" #. type: Title === -#: ./user-manual.txt:2155 +#: user-manual.txt:2120 #, no-wrap msgid "The Dive Profile context menu" msgstr "" #. type: Plain text -#: ./user-manual.txt:2173 +#: user-manual.txt:2139 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." +"the mouse cursor is over the Dive Profile panel. The menu lets you create " +"Bookmarks, 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, with the time of the event set by " +"where the mouse cursor was when the right mouse button was first clicked to " +"bring up the menu. Gas Change events involve a selection of which gas is " +"being switched TO. The list of choices is based on the available gases " +"defined in the *Equipment* Tab. Setpoint change events open a dialog letting " +"you choose the next setpoint value. As in the planner, a setpoint value of " +"zero shows the diver is breathing from an open circuit system while any " +"non-zero value shows 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:2175 +#: user-manual.txt:2141 #, no-wrap msgid "The *Information Box*" msgstr "" #. type: Plain text -#: ./user-manual.txt:2185 +#: user-manual.txt:2150 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 " +"The Information box displays a large range of information about 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 " @@ -4247,47 +4177,46 @@ msgid "" msgstr "" #. type: Target for macro image -#: ./user-manual.txt:2186 +#: user-manual.txt:2151 #, no-wrap msgid "images/InfoBox2.jpg" msgstr "" #. type: Plain text -#: ./user-manual.txt:2203 +#: user-manual.txt:2168 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." +"When 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 shown 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). Moving the cursor " +"horizontally lets the Information Box 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:2206 +#: user-manual.txt:2171 msgid "" -"The user has control over the display of several statistics, represented as " -"four buttons on the left of the profile panel. These are:" +"The user has control over the display of some statistics, shown as four " +"buttons on the left of the profile panel. These are:" msgstr "" #. type: Named 'icon' AttributeList argument for style 'icon' -#: ./user-manual.txt:2207 +#: user-manual.txt:2172 #, no-wrap msgid "images/icons/MOD.jpg" msgstr "" #. type: Plain text -#: ./user-manual.txt:2216 +#: user-manual.txt:2181 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 " @@ -4295,116 +4224,115 @@ msgid "" "oxygen) it is around 57 m if a maximum pO~2~ of 1.4 is specified in the " "*Preferences* section (select _File_ -> Preferences -> Graph_ and edit the " "text box _Max pO~2~ when showing MOD_. Below the MOD there is a markedly " -"increased risk of exposure to the dangers associated with oxygen toxicity." +"increased risk of exposure to the dangers of oxygen toxicity." msgstr "" #. type: Named 'icon' AttributeList argument for style 'icon' -#: ./user-manual.txt:2217 +#: user-manual.txt:2182 #, no-wrap msgid "images/icons/NDL.jpg" msgstr "" #. type: Plain text -#: ./user-manual.txt:2229 +#: user-manual.txt:2194 msgid "" "Clicking this button causes the Information Box to display either 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. TTS is calculated assuming an ascent surface air " -"consumption (SAC) for the gas currently used. Even if the profile contains " -"several gas switches, TTS at a specific moment during the dive is calculated " -"using the current gas. For TTS longer than 2 hours, it is not accurately " -"calculated and Subsurface only indicates _TTS > 2h_." +"appears). Once a diver 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. TTS is calculated assuming an ascent " +"surface air consumption (SAC) for the gas currently used. Even if the " +"profile contains several gas switches, TTS at a specific moment during the " +"dive is calculated using the current gas. TTS longer than 2 hours is not " +"accurately calculated and Subsurface only indicates _TTS > 2h_." msgstr "" #. type: Named 'icon' AttributeList argument for style 'icon' -#: ./user-manual.txt:2230 +#: user-manual.txt:2195 #, no-wrap msgid "images/icons/SAC.jpg" msgstr "" #. type: Plain text -#: ./user-manual.txt:2239 +#: user-manual.txt:2204 msgid "" "Clicking this button causes the Information Box to display the *Surface Air " -"Consumption (SAC)*. SAC is an indication of the surface-normalised " +"Consumption (SAC)*. SAC is an indication of the surface-normalized " "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." +"of breathing gas consumption rate independent of the depth of the dive, so " +"the respiratory rates of different dives can be compared. The units for SAC " +"is liters/min or cubic ft/min." msgstr "" #. type: Named 'icon' AttributeList argument for style 'icon' -#: ./user-manual.txt:2240 +#: user-manual.txt:2205 #, no-wrap msgid "images/icons/EAD.jpg" msgstr "" #. type: Plain text -#: ./user-manual.txt:2255 +#: user-manual.txt:2220 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." +"dives. These are important to divers breathe 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:2257 +#: user-manual.txt:2222 msgid "" "Figure (*B*) above shows an information box with a nearly complete set of " "data." msgstr "" #. type: Title ==== -#: ./user-manual.txt:2259 +#: user-manual.txt:2224 #, no-wrap msgid "The Gas Pressure Bar Graph" msgstr "" #. type: Plain text -#: ./user-manual.txt:2266 +#: user-manual.txt:2231 msgid "" -"On the left of the *Information Box* is a vertical bar graph indicating the " +"On the left of the *Information Box* is a vertical bar graph showing 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 " +"dive_. It is shown 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:2267 +#: user-manual.txt:2232 #, no-wrap msgid "images/GasPressureBarGraph.jpg" msgstr "" #. type: Plain text -#: ./user-manual.txt:2273 +#: user-manual.txt:2238 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 " +"light green area showing 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:2279 +#: user-manual.txt:2244 msgid "" "The horizontal black line underneath the light green margin indicates the " "equilibrium pressure of the inert gases inhaled by the diver, usually " @@ -4415,7 +4343,7 @@ msgid "" msgstr "" #. type: Plain text -#: ./user-manual.txt:2283 +#: user-manual.txt:2248 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 " @@ -4423,7 +4351,7 @@ msgid "" msgstr "" #. type: Plain text -#: ./user-manual.txt:2288 +#: user-manual.txt:2253 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 " @@ -4433,39 +4361,39 @@ msgid "" msgstr "" #. type: Plain text -#: ./user-manual.txt:2292 +#: user-manual.txt:2257 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 " +"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:2295 +#: user-manual.txt:2260 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." +"These five values are shown on the left in the graph above. The way the Gas " +"Pressure Bar Graph changes during a dive can be seen on the right hand side " +"of the above figure for a diver using EAN32." msgstr "" #. type: Plain text -#: ./user-manual.txt:2298 +#: user-manual.txt:2263 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." +"Graph *A* indicates the start of a dive with the 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:2301 +#: user-manual.txt:2266 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." +"tissue compartments have had time to respond to the descent, so their gas " +"pressures are far below the equilibrium gas pressure." msgstr "" #. type: Plain text -#: ./user-manual.txt:2306 +#: user-manual.txt:2271 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 " @@ -4475,18 +4403,18 @@ msgid "" msgstr "" #. type: Plain text -#: ./user-manual.txt:2312 +#: user-manual.txt:2277 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 " +"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 " +"exceed that of the total gas pressure and approach 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:2317 +#: user-manual.txt:2282 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 " @@ -4496,184 +4424,180 @@ msgid "" msgstr "" #. type: Title == -#: ./user-manual.txt:2320 +#: user-manual.txt:2285 #, no-wrap -msgid "Organising the logbook (Manipulating groups of dives)" +msgid "Organizing the logbook (Manipulating groups of dives)" msgstr "" #. type: Title === -#: ./user-manual.txt:2322 +#: user-manual.txt:2287 #, no-wrap msgid "The Dive List context menu" msgstr "" #. type: Plain text -#: ./user-manual.txt:2326 +#: user-manual.txt:2291 msgid "" -"Several actions on either a single dive or a group of dives can be performed " -"using the Dive List Context Menu, found by selecting either a single dive or " -"a group of dives and then right-clicking." +"Several actions on either a single dive, or a group of dives, can be " +"performed using the Dive List Context Menu. It is found by selecting either " +"a single dive or a group of dives and then right-clicking." msgstr "" #. TODO: NEEDS REPLACEMENT #. type: Target for macro image -#: ./user-manual.txt:2328 +#: user-manual.txt:2293 #, no-wrap msgid "images/ContextMenu.jpg" msgstr "" #. type: Plain text -#: ./user-manual.txt:2331 -msgid "The context menu is used in many manipulations described below." +#: user-manual.txt:2296 +msgid "The context menu is used in many functions described below." msgstr "" #. type: Title ==== -#: ./user-manual.txt:2332 +#: user-manual.txt:2297 #, no-wrap -msgid "Customising the columns showed in the *Dive List* panel" +msgid "Customizing the columns showed in the *Dive List* panel" msgstr "" #. type: Target for macro image -#: ./user-manual.txt:2334 +#: user-manual.txt:2299 #, no-wrap msgid "images/DiveListOptions.jpg" msgstr "" #. type: Plain text -#: ./user-manual.txt:2342 +#: user-manual.txt:2307 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 (reflected by the check symbols) and the list is immediately " +"above). Select an item to be shown in the *Dive List* or be deleted " +"(reflected by the check symbols) and the list is immediately " "updated. Preferences for information shown in the *Dive List* are saved and " "used when _Subsurface_ is re-opened." msgstr "" #. type: Title === -#: ./user-manual.txt:2344 +#: user-manual.txt:2309 #, no-wrap msgid "Renumbering the dives" msgstr "" #. type: Plain text -#: ./user-manual.txt:2356 +#: user-manual.txt:2321 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." +"sequence numbers) to recent dives (higher sequence numbers). Numbering of " +"dives is not always consistent. For instance, when non-recent dives are " +"added, correct 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. So you may need to renumber the dives. Do this by " +"selecting (from the Main Menu) _Log -> Renumber_. Users are given a choice " +"of the lowest sequence number to be used. This results in new sequence " +"numbers (based on date/time) for the dives in the *Dive List* panel." msgstr "" #. type: Plain text -#: ./user-manual.txt:2361 +#: user-manual.txt:2326 msgid "" -"One can also renumber a few selected dives in the dive list. Select the " +"You can also renumber a few selected dives in the dive list. Select the " "dives that need renumbering. Right-click on the selected list and use the " "Dive List Context Menu to perform the renumbering. A popup window appears " -"requiring the user to specify the starting number for the renumbering " -"process." +"letting the user specify the starting number for the process." msgstr "" #. type: Title === -#: ./user-manual.txt:2363 +#: user-manual.txt:2328 #, no-wrap msgid "Grouping dives into trips and manipulating trips" msgstr "" #. type: Plain text -#: ./user-manual.txt:2371 +#: user-manual.txt:2336 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 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 " +"can group dives into _trips_. It does this by grouping dives that have " +"date/times not separated in time by more than two days, so 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):" +"dive list of five dive trips (*B*, on the right):" msgstr "" #. type: Target for macro image -#: ./user-manual.txt:2372 +#: user-manual.txt:2337 #, no-wrap msgid "images/Group2.jpg" msgstr "" #. type: Plain text -#: ./user-manual.txt:2378 +#: user-manual.txt:2343 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) select _Log -> Autogroup_. The *Dive List* panel " -"now shows only the titles for the trips." +"having to scan a long lists of dives. To group the dives in a dive list, " +"(from the Main Menu) select _Log -> Autogroup_. The *Dive List* panel now " +"shows only the titles for the trips." msgstr "" #. type: Title ==== -#: ./user-manual.txt:2379 +#: user-manual.txt:2344 #, no-wrap msgid "Editing the title and associated information for a particular trip" msgstr "" #. type: Plain text -#: ./user-manual.txt:2392 +#: user-manual.txt:2357 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 *Notes* " -"panel. Here one can add or edit information about the date/time, the trip " +"panel. Here you 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 " +"dive company that was used, the general weather and surface conditions " "during the trip, etc.). After entering this information, 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 the edited information." msgstr "" #. type: Title ==== -#: ./user-manual.txt:2393 +#: user-manual.txt:2358 #, no-wrap msgid "Viewing the dives during a particular trip" msgstr "" #. type: Plain text -#: ./user-manual.txt:2398 +#: user-manual.txt:2363 msgid "" -"Once the dives have been grouped into trips, users can expand one or more " +"Once the dives have been grouped into trips, you 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." +"expands the selected trip, revealing individual dives done during the trip." msgstr "" #. type: Title ==== -#: ./user-manual.txt:2399 +#: user-manual.txt:2364 #, no-wrap msgid "Collapsing or expanding dive information for different trips" msgstr "" #. type: Plain text -#: ./user-manual.txt:2404 +#: user-manual.txt:2369 msgid "" "After selecting a particular trip in the dive list, the context menu allows " -"several possibilities to expand or collapse dives within trips. This " -"includes expanding all trips and collapsing all trips." +"several options to expand or collapse dives within trips. This includes " +"expanding all trips and collapsing all trips." msgstr "" #. type: Title ==== -#: ./user-manual.txt:2405 +#: user-manual.txt:2370 #, no-wrap msgid "Merging dives from more than one trip into a single trip" msgstr "" #. type: Plain text -#: ./user-manual.txt:2410 +#: user-manual.txt:2375 msgid "" "After selecting a trip title, the context menu allows the merging of trips " "by either merging the selected trip with the trip below or with the trip " @@ -4681,75 +4605,74 @@ msgid "" msgstr "" #. type: Title ==== -#: ./user-manual.txt:2411 +#: user-manual.txt:2376 #, no-wrap msgid "Splitting a single trip into more than one trip" msgstr "" #. type: Plain text -#: ./user-manual.txt:2421 +#: user-manual.txt:2385 msgid "" -"If a trip includes ten dives, the user can split this trip into two trips " -"(trip 1: top 4 dives; trip 2: bottom 6 dives) by selecting and " -"right-clicking the top four dives. The resulting context menu allows the " -"user to create a new trip by choosing the option *Create new trip " -"above*. The top four 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):" +"If a trip includes ten dives, you can split this trip into two trips (trip " +"1: top 4 dives; trip 2: bottom 6 dives) by selecting and right-clicking the " +"top four dives. The resulting context menu lets the user create a new trip " +"by choosing the option *Create new trip above*. The top four dives are then " +"grouped into a separate trip. The figures below show 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:2422 +#: user-manual.txt:2386 #, no-wrap msgid "images/SplitDive3a.jpg" msgstr "" #. type: Title === -#: ./user-manual.txt:2424 +#: user-manual.txt:2388 #, no-wrap msgid "Manipulating single dives" msgstr "" #. type: Title ==== -#: ./user-manual.txt:2426 +#: user-manual.txt:2390 #, no-wrap msgid "Delete a dive from the dive log" msgstr "" #. type: Plain text -#: ./user-manual.txt:2433 +#: user-manual.txt:2397 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 " +"right-clicking them to bring up the context menu, 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:2434 +#: user-manual.txt:2398 #, no-wrap msgid "Unlink a dive from a trip" msgstr "" #. type: Plain text -#: ./user-manual.txt:2441 +#: user-manual.txt:2405 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 or below the trip to which they belonged, depending " -"on the date and time of the unlinked dive." +"You can unlink dives from the trip to which they belong. 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 or below the trip to which they belonged, depending on the date and " +"time of the unlinked dive." msgstr "" #. type: Title ==== -#: ./user-manual.txt:2442 +#: user-manual.txt:2406 #, no-wrap msgid "Add a dive to the trip immediately above" msgstr "" #. type: Plain text -#: ./user-manual.txt:2447 +#: user-manual.txt:2411 msgid "" "Selected dives can be moved from the trip to which they belong and placed " "within a separate trip. To do this, select and right-click the dive(s) to " @@ -4757,37 +4680,36 @@ msgid "" msgstr "" #. type: Title ==== -#: ./user-manual.txt:2448 +#: user-manual.txt:2412 #, no-wrap msgid "Shift the start time of dive(s)" msgstr "" #. type: Plain text -#: ./user-manual.txt:2459 +#: user-manual.txt:2422 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, 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 ealier or later." +"Sometimes it’s necessary to adjust the start time of a dive. This may apply " +"to situations where dives are done in different time zones or when the dive " +"computer has a wrong time. To do this, select and right-click the dive(s) to " +"be adjusted. This brings up the context menu on which the *Shift times* " +"option should be selected. You must then specify the time (in hours and " +"minutes) by which the dives should be adjusted and click on the option of " +"whether the time adjustment should be earlier or later." msgstr "" #. type: Title ==== -#: ./user-manual.txt:2460 +#: user-manual.txt:2423 #, no-wrap msgid "Merge dives into a single dive" msgstr "" #. type: Plain text -#: ./user-manual.txt:2470 +#: user-manual.txt:2433 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 " +"Sometimes a dive is briefly interrupted, for example, if a diver returns to " +"the surface for a few minutes. That results in two or more dives being " +"recorded by the dive computer and appearing as different dives in the *Dive " +"List* panel. You 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 *Notes* panel to reflect events or conditions that apply " @@ -4796,19 +4718,19 @@ msgid "" msgstr "" #. type: Target for macro image -#: ./user-manual.txt:2471 +#: user-manual.txt:2434 #, no-wrap msgid "images/MergedDive.png" msgstr "" #. type: Title ==== -#: ./user-manual.txt:2473 +#: user-manual.txt:2436 #, no-wrap msgid "Undo dive manipulations" msgstr "" #. type: Plain text -#: ./user-manual.txt:2479 +#: user-manual.txt:2442 msgid "" "Important actions on dives or trips, described above, can be undone or " "redone. This includes: _delete dives_, _merge dives_, _renumber dives_ and " @@ -4818,162 +4740,159 @@ msgid "" msgstr "" #. type: Title === -#: ./user-manual.txt:2482 +#: user-manual.txt:2445 #, no-wrap msgid "Filtering the dive list" msgstr "" #. type: Plain text -#: ./user-manual.txt:2488 +#: user-manual.txt:2451 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." +"The dives in the *Dive List* panel can be filtered, so you 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 lets you 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:2496 +#: user-manual.txt:2459 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 (see image below). The " "_Filter Panel_ can be reset (i.e. all current filters cleared) by selecting " -"the *yellow angled arrow*. The _Filter Panel_ may also be minimised by " -"selecting the *green up-arrow\". 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 *red button* " +"the *yellow angled arrow*. The _Filter Panel_ may also be minimized by " +"selecting the *green up-arrow\". When minimized, only these three icons are " +"shown. The panel can be maximized by clicking the same icon that minimized " +"it. The filter may also be reset and closed by selecting the *red button* " "with the white cross." msgstr "" #. type: Target for macro image -#: ./user-manual.txt:2497 +#: user-manual.txt:2460 #, no-wrap msgid "images/Filterpanel.jpg" msgstr "" #. type: Plain text -#: ./user-manual.txt:2506 +#: user-manual.txt:2469 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 " +"(buddy / divemaster), dive site and dive suit. Each of these 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." +"filter tool, allowing the listing of only some attributes within that check " +"list. For instance, typing \"_ca_\" in the filter text box above the tags " +"check list, results in the list being reduced to \"_cave_\" and " +"\"_cavern_\". Filtering the check list helps to rapidly find search terms " +"for filtering the dive list." msgstr "" #. type: Plain text -#: ./user-manual.txt:2514 +#: user-manual.txt:2477 msgid "" "To activate filtering of the dive list, check at least one check box in one " "of the four check lists. The dive list is then shortened to include only the " "dives that pertain to the 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 " +"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:2516 +#: user-manual.txt:2479 #, no-wrap msgid "Exporting the dive log or parts of the dive log" msgstr "" #. type: Plain text -#: ./user-manual.txt:2519 -msgid "There are two routes for the export of dive information from Subsurface:" +#: user-manual.txt:2482 +msgid "There are two ways to export dive information from Subsurface:" msgstr "" #. type: Plain text -#: ./user-manual.txt:2521 +#: user-manual.txt:2484 msgid "Export dive information to _Facebook_" msgstr "" #. type: Plain text -#: ./user-manual.txt:2523 +#: user-manual.txt:2486 msgid "" "xref:S_Export_other[Export dive information to other destinations or " "formats]" msgstr "" #. type: Title === -#: ./user-manual.txt:2525 +#: user-manual.txt:2488 #, no-wrap msgid "Exporting dive information to _Facebook_" msgstr "" #. type: Plain text -#: ./user-manual.txt:2534 +#: user-manual.txt:2497 msgid "" "Export of dives to _Facebook_ is handled differently from other types of " "export because a connection to _Facebook_ is required, needing a _Facebook_ " -"userID and password. If, from the *Main Menu*, one selects _File -> " -"Preferences -> Facebook_, a login screen is presented (image *A* to the " -"left, below). Provide a _Facebook_ userID and password. Once a successful " -"login to _Facebook_ has been achieved, the panel in image *B*, below is " -"presented, including a _Disconnect from Facebook_ button to close the " -"_Facebook_ connection." +"userID and password. If, from the *Main Menu*, you select _File -> " +"Preferences -> Facebook_, a login screen comes up. (image *A* to the left, " +"below). Provide a _Facebook_ userID and password. Once logged into to " +"_Facebook_ , the panel in image *B*, below is shown, including a _Disconnect " +"from Facebook_ button to close the _Facebook_ connection." msgstr "" #. type: Target for macro image -#: ./user-manual.txt:2535 +#: user-manual.txt:2498 #, no-wrap msgid "images/facebook1_f20.jpg" msgstr "" #. type: Plain text -#: ./user-manual.txt:2540 +#: user-manual.txt:2503 msgid "" -"From the _Subsurface_ window it is easy to determine whether _Subsurface_ " -"has a valid connection to _Facebook_ From the *Main Menu*, select _Share on " -"-> Facebook_ (image *A*, below). Normally, the _Facebook_ option is greyed " +"From the _Subsurface_ window it’s easy to determine whether _Subsurface_ has " +"a valid connection to _Facebook_ From the *Main Menu*, select _Share on -> " +"Facebook_ (image *A*, below). Normally, the _Facebook_ option is greyed " "out. But if there is a connection to _Facebook_, this option is active " -"(i.e. in black colour and can be selected)." +"(i.e. in black color and can be selected)." msgstr "" #. type: Plain text -#: ./user-manual.txt:2550 +#: user-manual.txt:2514 msgid "" -"Having established a login to _Facebook_, transfer of a dive profile to " -"one's _Facebook_ timeline is easy. Ensure that the dive to be transfered to " -"the timeline is depicted in the _Subsurface_ *Dive Profile* panel. If, from " -"the *Main Menu*, one selects _Share on -> Facebook_ (see image *A* below), a " -"dialogue is shown, determining the amount of additional information " -"transferred with the dive profile (image *B*, below). In order to transfer a " -"dive profile to _Facebook_, the name of a _Facebook_ album needs to be " -"provided. The checkboxes on the lefthand side allow one to determine how " -"much additional information should be transferred with the dive " -"profile. This information is shown in the text box on the right hand side of " -"the panel (image *B*, below). One can easily edit the message that will be " -"posted with the dive profile. Having specified the additional information " -"and verified the text, select the _OK_ button that triggers the transfer to " -"_Facebook_. After a while, an acknowledgement dialogue appears, indicating " -"successful transfer to _Facebook_." +"Having established a login to _Facebook_, transferring a dive profileto a " +"_Facebook_ timeline is easy. Be sure the dive to be transferred to the " +"timeline is shown in the _Subsurface_ *Dive Profile* panel. If, from the " +"*Main Menu*, you select _Share on -> Facebook_ (see image *A* below), a " +"dialogue box is shown, determining the amount of additional information " +"transferred along with the dive profile (image *B*, below). To transfer a " +"dive profile to _Facebook_, the name of a _Facebook_ album is needed. The " +"checkboxes on the left hand side let you decide how much additional " +"information should be transferred with the dive profile. This information is " +"shown in the text box on the right hand side of the panel (image *B*, " +"below). You can easily edit the message that will be posted with the dive " +"profile. After specifying the additional information and verifying the " +"text, select the _OK_ button that triggers the transfer to _Facebook_. After " +"the transfer is done, an acknowledgement dialogue appears, indicating it was " +"successful." msgstr "" #. type: Plain text -#: ./user-manual.txt:2557 +#: user-manual.txt:2519 msgid "" -"Both the album created and the post to one's timeline will be marked as " -"private. In order for friends to be able to see the post, change its " -"permissions from a regular Facebook login either in a browser or a Facebook " -"app. While this is an extra step this is the better solution to avoid having " -"unwanted posts in one's public timeline." +"Both the album created and the post to your timeline will be marked as " +"private. In order for friends to be able to see it, change its permissions " +"from a regular Facebook login either in a browser or a Facebook app." msgstr "" #. type: Target for macro image -#: ./user-manual.txt:2558 +#: user-manual.txt:2520 #, no-wrap msgid "images/facebook2_f20.jpg" msgstr "" #. type: Plain text -#: ./user-manual.txt:2562 +#: user-manual.txt:2524 msgid "" "If required, then close the _Facebook_ connection by either closing " "_Subsurface_ or by selecting _File -> Preferences -> Facebook_ from the Main " @@ -4981,15 +4900,15 @@ msgid "" msgstr "" #. type: Title === -#: ./user-manual.txt:2564 +#: user-manual.txt:2526 #, no-wrap -msgid "Export dive information to other destinations or formats" +msgid "Export dive information to other destinations or formats" msgstr "" #. type: Plain text -#: ./user-manual.txt:2569 +#: user-manual.txt:2531 msgid "" -"For non-_Facebook exports_, the export function can be reached by selecting " +"For non-_Facebook exports_, the export function can be found 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 " @@ -4997,23 +4916,23 @@ msgid "" msgstr "" #. type: Target for macro image -#: ./user-manual.txt:2570 +#: user-manual.txt:2532 #, no-wrap msgid "images/Export_f20.jpg" msgstr "" #. type: Plain text -#: ./user-manual.txt:2573 +#: user-manual.txt:2535 msgid "A dive log or part of it can be saved in three formats:" msgstr "" #. type: Plain text -#: ./user-manual.txt:2575 +#: user-manual.txt:2537 msgid "_Subsurface XML_ format. This is the native format used by _Subsurface_." msgstr "" #. type: Plain text -#: ./user-manual.txt:2579 +#: user-manual.txt:2541 msgid "" "Universal Dive Data Format (_UDDF_). Refer to _http://uddf.org_ for more " "information. UDDF is a generic format that enables communication among many " @@ -5021,24 +4940,24 @@ msgid "" msgstr "" #. type: Plain text -#: ./user-manual.txt:2583 +#: user-manual.txt:2545 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_, you need 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_." +"service to upload dive log data from _Subsurface_." msgstr "" #. type: Plain text -#: ./user-manual.txt:2587 +#: user-manual.txt:2549 msgid "" -"_DiveShare_ is also a dive log repository on the Internet focusing on the " -"recreational dives. In order to upload dives one has to provide a used ID, " -"so registration with _http://scubadiveshare.com_ is required." +"_DiveShare_ is also a dive log repository on the Internet focusing on " +"recreational dives. To upload dives, you need a user ID, so registration " +"with _http://scubadiveshare.com_ is required." msgstr "" #. type: Plain text -#: ./user-manual.txt:2592 +#: user-manual.txt:2554 msgid "" "_CSV dive details_, that includes the most critical information of the dive " "profile. Included information of a dive is: dive number, date, time, buddy, " @@ -5047,7 +4966,7 @@ msgid "" msgstr "" #. type: Plain text -#: ./user-manual.txt:2595 +#: user-manual.txt:2557 msgid "" "_CSV dive profile_, that includes a large amount of detail for each dive, " "including the depth profile, temperature and pressure information of each " @@ -5055,7 +4974,7 @@ msgid "" msgstr "" #. type: Plain text -#: ./user-manual.txt:2608 +#: user-manual.txt:2570 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 " @@ -5065,43 +4984,43 @@ msgid "" "pressure, gas pressures and MOD. The HTML export contains a search option to " "search the dive log. HTML export is specified on the second tab of the " "Export dialog (image *B* above). A typical use of this option is to export " -"all one's dives to a smartphone or a tablet where it would serve as a very " -"portable record of dives useful for dive companies that wish to verify the " -"dive history of a diver, often doing away with the need to carry one's " -"original logbook with one when doing dives with dive companies." +"all one's dives to a smartphone or a tablet where it would serve as a " +"portable record of dives. That is useful for dive companies that wish to " +"verify the dive history of a diver, often doing away with the need to carry " +"an original logbook when doing dives with dive companies." msgstr "" #. type: Plain text -#: ./user-manual.txt:2613 +#: user-manual.txt:2575 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. If one " -"selects any of the dive sites on the map, a summary of the dive is available " +"some information about it are indicated. This map is not editable. If you " +"select any of the dive sites on the map, a summary of the dive is available " "in text, as shown in the image below." msgstr "" #. type: Target for macro image -#: ./user-manual.txt:2614 +#: user-manual.txt:2576 #, no-wrap msgid "images/mapview_f20.jpg" msgstr "" #. type: Plain text -#: ./user-manual.txt:2621 +#: user-manual.txt:2583 msgid "" "_Image depths_, which creates a text file that contains the file names of " "all photos or images attached to any of the selected dives in the _Dive " -"List_, together with the depth under water where of each of those photos " -"were taken." +"List_, together with the depth underwater where of each of those photos was " +"taken." msgstr "" #. type: Plain text -#: ./user-manual.txt:2623 +#: user-manual.txt:2585 msgid "_General Settings_, under the HTML tab, provides the following options:" msgstr "" #. type: Plain text -#: ./user-manual.txt:2631 +#: user-manual.txt:2593 #, no-wrap msgid "" "** Subsurface Numbers: if this option is checked, the dive(s) are exported " @@ -5119,59 +5038,58 @@ msgid "" msgstr "" #. type: Plain text -#: ./user-manual.txt:2634 +#: user-manual.txt:2596 msgid "" "Under _Style Options_ some style-related options are available like font " "size and theme." msgstr "" #. type: Plain text -#: ./user-manual.txt:2637 +#: user-manual.txt:2599 msgid "" -"Export to other formats can be achieved through third party facilities, for " +"Export to other formats can be done through third party facilities, for " "instance _www.divelogs.de_." msgstr "" #. type: Title == -#: ./user-manual.txt:2639 +#: user-manual.txt:2601 #, no-wrap msgid "Keeping a _Subsurface_ dive log in the Cloud" msgstr "" #. type: Plain text -#: ./user-manual.txt:2650 +#: user-manual.txt:2611 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 " +"record of diving activities for one's own pleasure, but it’s important " +"information required for admission to training courses or sometimes even " +"diving sites. The security of the dive log is critical. 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 you can access your dive log from anywhere in the world. For this " "reason, facilities such as _divelogs.de_ and _Diving Log_ offer to store " "dive log information on the Internet." msgstr "" #. type: Plain text -#: ./user-manual.txt:2656 +#: user-manual.txt:2617 msgid "" "_Subsurface_ includes access to a transparently integrated cloud storage " "back end that is available to all Subsurface users. Storing and retrieving a " "dive log from the cloud is no more difficult than accessing the dives on the " -"local hard disk. The only requirement is that one should first register as " +"local hard disk. The only requirement is that you should first register as " "a user on the cloud. To use _Subsurface cloud storage_ , follow these " "steps:" msgstr "" #. type: Title === -#: ./user-manual.txt:2657 +#: user-manual.txt:2618 #, no-wrap msgid "Create a cloud storage account" msgstr "" #. type: Plain text -#: ./user-manual.txt:2674 +#: user-manual.txt:2635 #, no-wrap msgid "" "** Open the *Network Preferences* by selecting _File_ -> _Preferences_ -> " @@ -5199,90 +5117,90 @@ msgid "" msgstr "" #. type: Title === -#: ./user-manual.txt:2675 +#: user-manual.txt:2636 #, no-wrap msgid "Using _Subsurface cloud storage_" msgstr "" #. type: Plain text -#: ./user-manual.txt:2685 +#: user-manual.txt:2646 #, no-wrap msgid "" -"** Once the cloud storage has been initialised, two new items appear in " +"** Once the cloud storage has been initialized, two new items appear in " "the\n" " _File_ menu of the main menu system: _Open cloud storage_ and _Save to " "cloud storage_.\n" -"These options allow the user to load and save data to the _Subsurface\n" +"These options let you load and save data to the _Subsurface\n" "cloud storage_ server.\n" -"** In the _Defaults Preferences_ tab, one can select to use the _Subsurface " +"** In the _Defaults Preferences_ tab, you can select to use the _Subsurface " "cloud\n" -"storage_ data as one's default data file by checking the check box marked " -"_Cloud storage default file_.\n" -" This means that the data from\n" -"the _Subsurface cloud storage_ is loaded when _Subsurface_ starts ans saved " -"there when one closes _Subsurface_.\n" +"storage_ data as the default data file by checking the box marked _Cloud " +"storage default file_.\n" +" This means the data from\n" +"the _Subsurface cloud storage_ is loaded when _Subsurface_ starts and saved " +"there when _Subsurface_ closes.\n" msgstr "" #. type: Plain text -#: ./user-manual.txt:2690 +#: user-manual.txt:2651 #, no-wrap msgid "" "** _Subsurface_ keeps a local copy of the data and the cloud facility " "remains fully\n" "functional even if used while disconnected to the Internet. _Subsurface_ " -"simply synchronises the\n" -"data with the cloud server the next time ithe program is used while the " +"simply synchronizes the\n" +"data with the cloud server the next time the program is used while the " "computer is\n" "connected to the Internet.\n" msgstr "" #. type: Title === -#: ./user-manual.txt:2692 +#: user-manual.txt:2653 #, no-wrap msgid "Web access to _Subsurface cloud storage_" msgstr "" #. type: Plain text -#: ./user-manual.txt:2702 +#: user-manual.txt:2663 msgid "" "One of the nice side benefits of using _Subsurface cloud storage_ is that " -"one can also access one's dive data from any web browser. Simply open " +"you can also access your dive data from any web browser. Simply open " "https://cloud.subsurface-divelog.org[_https://cloud.subsurface-divelog.org_], " "log in with the same email and password, and you can see an HTML export of " -"the last dive data that was synced to the _Subsurface cloud storage_. The " -"dive information that is shown is only the contents of the recorded dive " -"logs, NOT the calculated values shown in the *Profile* panel, including some " -"cylinder pressures, deco ceilings and O~2~/He/N~2~ partial pressures." +"the last dive data that was synced to _Subsurface cloud storage_. The dive " +"information shown is only the contents of the recorded dive logs, NOT the " +"calculated values shown in the *Profile* panel, including some cylinder " +"pressures, deco ceilings and O~2~/He/N~2~ partial pressures." msgstr "" #. type: Title === -#: ./user-manual.txt:2703 +#: user-manual.txt:2664 #, no-wrap msgid "Other cloud services" msgstr "" #. type: Plain text -#: ./user-manual.txt:2713 +#: user-manual.txt:2674 msgid "" -"If one prefers not to use the integrated cloud storage of dive logs (and " -"don't need the web access), it is also simple to store dive logs in the " -"cloud 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." +"If you prefers not to use the integrated cloud storage of dive logs (and " +"don't need the web access), it’s simple to store dive logs in the cloud " +"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 a desktop " +"computer." msgstr "" #. type: Target for macro image -#: ./user-manual.txt:2714 +#: user-manual.txt:2675 #, no-wrap msgid "images/Cloud.jpg" msgstr "" #. type: Plain text -#: ./user-manual.txt:2723 +#: user-manual.txt:2684 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, " +"on your 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 " @@ -5292,206 +5210,205 @@ msgid "" msgstr "" #. type: Plain text -#: ./user-manual.txt:2730 +#: user-manual.txt:2691 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 " +"In this way a dive log in your _Dropbox_ folder can be accessed seamlessly " +"from the Internet and can be accessed anywhere 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:2736 +#: user-manual.txt:2697 msgid "" -"Alternatively one can use _Dropbox_ as a mechanism to backup one's dive " -"log. To Store a dive log on _Dropbox_, 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 _Dropbox_, 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." +"Alternatively you can use _Dropbox_ as a way back up your dive log. To Store " +"a dive log on _Dropbox_, 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 _Dropbox_, 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:2739 +#: user-manual.txt:2700 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:2742 +#: user-manual.txt:2703 #, no-wrap msgid "Printing a dive log" msgstr "" #. type: Plain text -#: ./user-manual.txt:2746 +#: user-manual.txt:2707 #, no-wrap msgid "" -"_Subsurface_ provides a simple and flexible interface to print a whole dive " -"log or only a few selected dives.\n" +"_Subsurface_ provides a simple and flexible way to print a whole dive log or " +"only a few selected dives.\n" " Pre-installed templates or a custom written template can be used to choose " "where the data are fitted into the page.\n" msgstr "" #. type: Plain text -#: ./user-manual.txt:2748 -msgid "Before printing, two decisions are required:" +#: user-manual.txt:2709 +msgid "Some decisions need to be made before printing:" msgstr "" #. type: Plain text -#: ./user-manual.txt:2751 +#: user-manual.txt:2712 msgid "" -"Should the whole dive log be printed or only part of it? If only part of the " -"dive log is required, then select the required dives from the *Dive List* " -"panel." +"Should the whole dive log be printed or only part of it? If only part is " +"required, select the required dives from the *Dive List* panel." msgstr "" #. type: Plain text -#: ./user-manual.txt:2753 +#: user-manual.txt:2714 msgid "" -"If the dive profiles needs printing, what gas partial pressure information " +"If the dive profiles are printed, what gas partial pressure information " "should be shown? Select the appropriate toggle-buttons on the button bar to " "the left of the *Dive Profile* panel." msgstr "" #. type: Plain text -#: ./user-manual.txt:2756 +#: user-manual.txt:2717 msgid "" -"If _File -> Print_ is selected from the Main menu, the the dialogue below " -"(image *A*) appears. Three specifications are needed to achieve the desired " -"information and page layout:" +"If _File -> Print_ is selected from the Main menu, the dialogue below (image " +"*A*) appears. Three specifications are needed to get the desired information " +"and page layout:" msgstr "" #. type: Target for macro image -#: ./user-manual.txt:2757 ./user-manual.txt:4185 +#: user-manual.txt:2718 user-manual.txt:4162 #, no-wrap msgid "images/Print1_f22.jpg" msgstr "" #. type: Plain text -#: ./user-manual.txt:2760 +#: user-manual.txt:2721 msgid "Under _Print type_ select one of two options:" msgstr "" #. type: Plain text -#: ./user-manual.txt:2762 +#: user-manual.txt:2723 msgid "" "_Dive list print_: Print dives from the *Dive List* panel with profiles and " "other information." msgstr "" #. type: Plain text -#: ./user-manual.txt:2763 +#: user-manual.txt:2724 msgid "_Statistics print_: Print yearly statistics of the dives." msgstr "" #. type: Plain text -#: ./user-manual.txt:2765 +#: user-manual.txt:2726 msgid "Under _Print options_ select:" msgstr "" #. type: Plain text -#: ./user-manual.txt:2770 +#: user-manual.txt:2731 msgid "" -"Printing only the dives selected from the dive list prior to activating the " +"Printing only the dives selected from the dive list before activating the " "print dialogue by checking the box _Print only selected dives_. If this " -"check box is *not* checked all dives in the *Dive List* panel are printed." +"check box is *not* checked ALL dives in the *Dive List* panel are printed." msgstr "" #. type: Plain text -#: ./user-manual.txt:2772 +#: user-manual.txt:2733 msgid "" -"Printing in colour, achieved by checking the box with _Print in colour_. If " -"this check box is not checked, printing is in monochrome (grey scale)." +"Printing in color, done by checking the box with _Print in color. If this " +"check box is not checked, printing is in black and white." msgstr "" #. type: Plain text -#: ./user-manual.txt:2775 +#: user-manual.txt:2736 msgid "" "Under _Template_ select a template to be used as the page layout. There are " -"several templates (see image *B*, above)." +"several choices. (see image *B*, above)." msgstr "" #. type: Plain text -#: ./user-manual.txt:2777 +#: user-manual.txt:2738 msgid "_Table_: This prints a summary table of all dives selected (see below)." msgstr "" #. type: Target for macro image -#: ./user-manual.txt:2778 +#: user-manual.txt:2739 #, no-wrap msgid "images/Print_summarylist_f22.jpg" msgstr "" #. type: Plain text -#: ./user-manual.txt:2781 +#: user-manual.txt:2742 msgid "" "_Flow layout_: Print the text associated with each dive without printing the " "dive profiles" msgstr "" #. type: Plain text -#: ./user-manual.txt:2782 +#: user-manual.txt:2743 msgid "of each dive (see below):" msgstr "" #. type: Target for macro image -#: ./user-manual.txt:2783 +#: user-manual.txt:2744 #, no-wrap msgid "images/Print_flow_layout_f22.jpg" msgstr "" #. type: Plain text -#: ./user-manual.txt:2786 +#: user-manual.txt:2747 msgid "" "_One Dive_: Print one dive per page, also showing the dive profile (see " "below)" msgstr "" #. type: Target for macro image -#: ./user-manual.txt:2787 +#: user-manual.txt:2748 #, no-wrap msgid "images/print2_f22.jpg" msgstr "" #. type: Plain text -#: ./user-manual.txt:2791 +#: user-manual.txt:2752 msgid "_Two Dives_: Print two dives per page, also showing the dive profiles." msgstr "" #. type: Plain text -#: ./user-manual.txt:2792 +#: user-manual.txt:2753 msgid "_Six Dives_: Print six dives per page, also showing the dive profiles." msgstr "" #. type: Plain text -#: ./user-manual.txt:2796 +#: user-manual.txt:2757 msgid "" -"Users can _Preview_ the printed page by selecting the _Preview_ button on " -"the dialogue (see image *A* at the start of this section). After preview, " -"changes to the options in the print dialogue can be made, resulting in a " -"layout that fits personal taste." +"You can _Preview_ the printed page by selecting the _Preview_ button on the " +"dialogue (see image *A* at the start of this section). After preview, you " +"can change the options in the print dialogue, so the layout fits personal " +"taste." msgstr "" #. type: Plain text -#: ./user-manual.txt:2800 +#: user-manual.txt:2761 msgid "" "Next, select the _Print_ button (see image *A* at the start of this " -"section). This activates the regular print dialogue used by the user " -"operating system, allowing one to choose a printer and to set its properties " -"(see image below):" +"section). This activates the regular print dialogue used by the operating " +"system, letting you choose a printer and set its properties (see image " +"below):" msgstr "" #. type: Target for macro image -#: ./user-manual.txt:2801 +#: user-manual.txt:2762 #, no-wrap msgid "images/Print_print_f22.jpg" msgstr "" #. type: Plain text -#: ./user-manual.txt:2806 +#: user-manual.txt:2767 msgid "" "Set the print resolution of the printer to an appropriate value by changing " "the printer _Properties_. Finally, select the _Print_ button to print the " @@ -5500,22 +5417,22 @@ msgid "" msgstr "" #. type: Target for macro image -#: ./user-manual.txt:2807 +#: user-manual.txt:2768 #, no-wrap msgid "images/Printpreview.jpg" msgstr "" #. type: Title === -#: ./user-manual.txt:2809 +#: user-manual.txt:2770 #, no-wrap msgid "Writing a custom print template (advanced)" msgstr "" #. type: Plain text -#: ./user-manual.txt:2813 +#: user-manual.txt:2776 msgid "" "Writing a custom template is an effective way to produce highly customized " -"printouts. Subsurface uses HTML templates to render printing. One can create " +"printouts. Subsurface uses HTML templates to render printing. You can create " "a template, export a new template, import an existing template and delete an " "existing template by using the appropriate buttons under the _Template_ " "dropdown list in the print dialogue. See <<S_APPENDIX_E,APPENDIX E>> for " @@ -5523,28 +5440,28 @@ msgid "" msgstr "" #. type: Title == -#: ./user-manual.txt:2815 +#: user-manual.txt:2778 #, no-wrap msgid "Configuring a dive computer" msgstr "" #. type: Plain text -#: ./user-manual.txt:2823 +#: user-manual.txt:2787 msgid "" -"_Subsurface_ enables one to configure a dive computer. Currently the " +"_Subsurface_ lets you 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 (also " -"required for downloading dives) 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." +"and changed to different values. To begin, be sure the appropriate hardware " +"driver is installed for the dive computer (also required for downloading " +"dives) and 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:2828 +#: user-manual.txt:2792 msgid "" "Once the dive computer is connected to the _Subsurface_ computer, select " "_File -> Configure dive computer_ from the _Main Menu_. Provide the " @@ -5554,20 +5471,20 @@ msgid "" msgstr "" #. type: Target for macro image -#: ./user-manual.txt:2829 +#: user-manual.txt:2793 #, no-wrap msgid "images/Configure_dc_f20.jpg" msgstr "" #. type: Plain text -#: ./user-manual.txt:2832 +#: user-manual.txt:2796 msgid "" "Using the appropriate buttons on the configuration panel, the following " -"actions can be performed:" +"actions can be done:" msgstr "" #. type: Plain text -#: ./user-manual.txt:2835 +#: user-manual.txt:2799 #, no-wrap msgid "" "*Retrieve available details*. This loads the existing configuration from the " @@ -5576,7 +5493,7 @@ msgid "" msgstr "" #. type: Plain text -#: ./user-manual.txt:2837 +#: user-manual.txt:2801 #, no-wrap msgid "" "*Save changes to device*. This changes the configuration of the\n" @@ -5585,7 +5502,7 @@ msgid "" msgstr "" #. type: Plain text -#: ./user-manual.txt:2839 +#: user-manual.txt:2803 #, no-wrap msgid "" "*Backup*. This saves the configuration data to a file. _Subsurface_ asks " @@ -5594,7 +5511,7 @@ msgid "" msgstr "" #. type: Plain text -#: ./user-manual.txt:2841 +#: user-manual.txt:2805 #, no-wrap msgid "" "*Restore backup*. This loads the information from a backup file and displays " @@ -5603,7 +5520,7 @@ msgid "" msgstr "" #. type: Plain text -#: ./user-manual.txt:2843 +#: user-manual.txt:2807 #, no-wrap msgid "" "*Update firmware*. If new firmware is available for the dive computer, this " @@ -5612,58 +5529,58 @@ msgid "" msgstr "" #. type: Title == -#: ./user-manual.txt:2846 +#: user-manual.txt:2810 #, no-wrap msgid "Setting user _Preferences_ for _Subsurface_" msgstr "" #. type: Plain text -#: ./user-manual.txt:2856 +#: user-manual.txt:2819 msgid "" "There are several user-definable settings within _Subsurface_, found by " -"selecting _File -> Preferences_. The settings are performed in seven groups: " +"selecting _File -> Preferences_. The settings are in seven groups: " "*Defaults*, *Units*, *Graph*, *Language* and *Network*, *Facebook* and " -"*Georeference*, all of which 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*. If *Discard* is selected, " -"changes to the preferences are not saved." +"*Georeference*. All operate on the same principles: the user must specify " +"settings that are to be changed, then save them using the *Apply* " +"button. After applying all the new settings users can then leave the " +"settings panel by selecting *OK*. If *Discard* is selected, changes to the " +"preferences are not saved." msgstr "" #. type: Title === -#: ./user-manual.txt:2857 +#: user-manual.txt:2820 #, no-wrap msgid "Defaults" msgstr "" #. type: Plain text -#: ./user-manual.txt:2860 +#: user-manual.txt:2823 msgid "There are several settings in the *Defaults* panel:" msgstr "" #. type: Target for macro image -#: ./user-manual.txt:2861 +#: user-manual.txt:2824 #, no-wrap msgid "images/Pref1_f20.jpg" msgstr "" #. type: Plain text -#: ./user-manual.txt:2865 +#: user-manual.txt:2828 #, no-wrap msgid "" -" ** *Lists and tables*: Here one can specify the font type and font size of " +" ** *Lists and tables*: Here you 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" +" *Dive Table* panel: By decreasing the font size of the *Dive Table*, " +"you can see more dives on a screen.\n" msgstr "" #. type: Plain text -#: ./user-manual.txt:2870 +#: user-manual.txt:2833 #, no-wrap msgid "" -" ** *Dives*: For the _Default Dive File_ one needs to specify the directory " +" ** *Dives*: For the _Default Dive File_ you need to specify the directory " "and\n" -" file name of one's\n" +" file name of your\n" " electronic dive log book. This is a file with filename extension of " "either _.xml_ or _.ssrf_. When\n" " launched, _Subsurface_ will automatically load the specified dive log " @@ -5671,7 +5588,7 @@ msgid "" msgstr "" #. type: Plain text -#: ./user-manual.txt:2871 +#: user-manual.txt:2834 #, no-wrap msgid "" "_No default file_: When checked, _Subsurface_ does not automatically load a " @@ -5679,7 +5596,7 @@ msgid "" msgstr "" #. type: Plain text -#: ./user-manual.txt:2873 +#: user-manual.txt:2836 #, no-wrap msgid "" "_Local default file_: When checked, _Subsurface_ automatically loads a dive " @@ -5688,17 +5605,17 @@ msgid "" msgstr "" #. type: Plain text -#: ./user-manual.txt:2875 +#: user-manual.txt:2838 #, no-wrap msgid "" "_Cloud storage default file_: When checked, _Subsurface automatically loads " "the dive log from the cloud\n" -"device that was initialised using the *Preferences* _Network_ tab (see " +"device that was initialized using the *Preferences* _Network_ tab (see " "below).\n" msgstr "" #. type: Plain text -#: ./user-manual.txt:2877 +#: user-manual.txt:2840 #, no-wrap msgid "" "** *Display invalid*: Dives can be marked as invalid (when a user wishes to " @@ -5706,7 +5623,7 @@ msgid "" msgstr "" #. type: Plain text -#: ./user-manual.txt:2880 +#: user-manual.txt:2843 #, no-wrap msgid "" "dives that he/she doesn't consider valid dives, e.g. pool dives, but still " @@ -5717,19 +5634,19 @@ msgid "" msgstr "" #. type: Plain text -#: ./user-manual.txt:2882 +#: user-manual.txt:2845 #, no-wrap msgid "** *Default cylinder*: Specify the default cylinder listed in\n" msgstr "" #. type: Plain text -#: ./user-manual.txt:2883 +#: user-manual.txt:2846 #, no-wrap msgid "the *Equipment* tab of the *Notes* panel.\n" msgstr "" #. type: Plain text -#: ./user-manual.txt:2885 +#: user-manual.txt:2848 #, no-wrap msgid "" "** *Animations*: Some actions in showing the dive profile are performed " @@ -5737,7 +5654,7 @@ msgid "" msgstr "" #. type: Plain text -#: ./user-manual.txt:2891 +#: user-manual.txt:2854 #, no-wrap msgid "" "animations. For instance, the axis values for depth and time change from " @@ -5753,7 +5670,7 @@ msgid "" msgstr "" #. type: Plain text -#: ./user-manual.txt:2893 +#: user-manual.txt:2856 #, no-wrap msgid "" "** *Clear all settings*: As indicated in the button below this heading, all " @@ -5761,110 +5678,111 @@ msgid "" msgstr "" #. type: Plain text -#: ./user-manual.txt:2894 +#: user-manual.txt:2857 #, no-wrap msgid "cleared and set to default values.\n" msgstr "" #. type: Title === -#: ./user-manual.txt:2895 +#: user-manual.txt:2858 #, no-wrap msgid "Units" msgstr "" #. type: Target for macro image -#: ./user-manual.txt:2896 +#: user-manual.txt:2859 #, no-wrap msgid "images/Pref2_f20.jpg" msgstr "" #. type: Plain text -#: ./user-manual.txt:2903 +#: user-manual.txt:2866 msgid "" -"Here users can choose between metric and imperial units of depth, pressure, " +"Here you 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, one 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." +"button at the top, you can specify that all units are in the chosen " +"measurement system. Alternatively, if you select the *Personalize* radio " +"button, units can be selected independently, with some in the metric system " +"and others in imperial." msgstr "" #. type: Plain text -#: ./user-manual.txt:2909 +#: user-manual.txt:2872 msgid "" -"Irrespective of the above settings, dive time measurements can be either in " +"Regardless of the above settings, dive time measurements can be either in " "seconds or minutes. Choose the appropriate option. GPS coordinates can be " "represented either as traditional coordinates (degrees, minutes, seconds) or " "as decimal degrees Choose the appropriate option." msgstr "" #. type: Title === -#: ./user-manual.txt:2910 +#: user-manual.txt:2873 #, no-wrap msgid "Graph" msgstr "" #. type: Target for macro image -#: ./user-manual.txt:2912 +#: user-manual.txt:2875 #, no-wrap msgid "images/Pref3_f20.jpg" msgstr "" #. type: Plain text -#: ./user-manual.txt:2916 +#: user-manual.txt:2879 msgid "This panel allows two type of selections:" msgstr "" #. type: Plain text -#: ./user-manual.txt:2936 +#: user-manual.txt:2901 #, no-wrap msgid "" -"*Show*: Here users can specify the amount of information shown as part of\n" +"*Show*: Here you 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, enabled by using the toolbar on the left hand side of the *Dive " +" the dive, done by 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" +" panel. For each of these graphs you can specify a threshold value on the " +"right-hand side of the\n" " Preferences panel. If any of the graphs go above the specified threshold " "level, the graph is\n" -" highlighted in red, indicating that the particular partial pressure " -"threshold has been exceeded.\n" +" highlighted in red, indicating the particular partial pressure threshold " +"has been exceeded.\n" "** _Max pO~2~ is used for calculating the MOD when displaying the maximum " "operative depth (MOD)\n" " for a dive. Specify an appropriate partial pressure. A value of 1.4 is " "commonly used.\n" -"** _Draw dive computer reported ceiling red_: This checkbox allows exactly " +"** _Draw dive computer reported ceiling red_: This checkbox does exactly " "what it says. By default\n" " the computer reported ceiling is shown in white.\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_ because of the different " "algorithms and\n" -" gradient factors, as well as the dynamic way that a\n" -" dive computer can calculate ceilings during a dive.\n" +" gradient factors, as well as the dynamic way a\n" +" dive computer calculates ceilings during a dive.\n" "** _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 if 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" +"information about unused cylinders when viewing the\n" +"*Equipment Tab*. If this box is not checked, and if any cylinders entered " +"using the *Equipment Tab* are not used (e.g. there\n" +"was no gas switch to such a cylinder), then these cylinders are omitted from " +"that list.\n" "** _Show average depth_: If this box is checked, the *Dive Profile* panel " -"contains a grey line that indicates\n" -" the mean depth of the dive up to any time instant during the " +"contains a grey line that shows\n" +" the mean depth of the dive, up to any time instant during the " "dive. Normally this is a u-shaped line indicating the deepest mean depth " -"just before the\n" +"just before\n" " ascent.\n" msgstr "" #. type: Plain text -#: ./user-manual.txt:2938 +#: user-manual.txt:2903 #, no-wrap msgid "*Misc*:\n" msgstr "" #. type: Plain text -#: ./user-manual.txt:2951 +#: user-manual.txt:2916 #, no-wrap msgid "" "** Gradient Factors (GFLow and GFHigh):* Set the _gradient factors_ used " @@ -5873,9 +5791,9 @@ msgid "" "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 " +" Gradient factors add conservatism to nitrogen exposure during a dive, in " +"a\n" +" similar way that many dive computers have a conservative setting. The " "lower\n" " the value of a gradient factor, the more conservative the calculations " "are with\n" @@ -5891,7 +5809,7 @@ msgid "" msgstr "" #. type: Plain text -#: ./user-manual.txt:2953 +#: user-manual.txt:2918 #, no-wrap msgid "" " *** http://www.tek-dive.com/portal/upload/M-Values.pdf[Understanding " @@ -5899,7 +5817,7 @@ msgid "" msgstr "" #. type: Plain text -#: ./user-manual.txt:2955 +#: user-manual.txt:2920 #, no-wrap msgid "" " *** " @@ -5908,19 +5826,19 @@ msgid "" msgstr "" #. type: Plain text -#: ./user-manual.txt:2959 +#: user-manual.txt:2924 #, no-wrap msgid "" -" ** _CCR: Show setpoints when viewing pO2:_ With this checkbox ativated, the " -"pO~2~\n" -" graph on the dive profile has an overlay in red which inticates the CCR " +" ** _CCR: Show setpoints when viewing pO2:_ With this checkbox activated, " +"the pO~2~\n" +" graph on the dive profile has an overlay in red which indicates the CCR " "setpoint\n" " values. See the section on xref:S_CCR_dives[Closed Circuit Rebreather " "dives].\n" msgstr "" #. type: Plain text -#: ./user-manual.txt:2963 +#: user-manual.txt:2928 #, no-wrap msgid "" " ** _CCR: Show individual O~2~ sensor values when viewing pO~2~:_ Show the " @@ -5931,13 +5849,13 @@ msgid "" msgstr "" #. type: Plain text -#: ./user-manual.txt:2965 +#: user-manual.txt:2930 #, no-wrap msgid "*Configuring dive planning using rebreather equipment:*\n" msgstr "" #. type: Plain text -#: ./user-manual.txt:2967 +#: user-manual.txt:2932 #, no-wrap msgid "" "** _Default CCR setpoint for dive planning:_ Specify the O~2~ setpoint for " @@ -5945,7 +5863,7 @@ msgid "" msgstr "" #. type: Plain text -#: ./user-manual.txt:2970 +#: user-manual.txt:2935 #, no-wrap msgid "" "CCR dive plan. This determines the pO~2~ maintained\n" @@ -5955,15 +5873,15 @@ msgid "" msgstr "" #. type: Plain text -#: ./user-manual.txt:2972 +#: user-manual.txt:2937 #, no-wrap msgid "" -"** _pSCR O~2~ metabolism rate:_ For a semiclosed rebreather (pSCR) system, " +"** _pSCR O~2~ metabolism rate:_ For a semi-closed rebreather (pSCR) system, " "this is the\n" msgstr "" #. type: Plain text -#: ./user-manual.txt:2974 +#: user-manual.txt:2939 #, no-wrap msgid "" "volume of oxygen used by a diver during a minute. Set this value for pSCR " @@ -5972,7 +5890,7 @@ msgid "" msgstr "" #. type: Plain text -#: ./user-manual.txt:2976 +#: user-manual.txt:2941 #, no-wrap msgid "" "** _pSCR ratio:_ For pSCR equipment the dump ratio is the ratio of gas " @@ -5980,7 +5898,7 @@ msgid "" msgstr "" #. type: Plain text -#: ./user-manual.txt:2978 +#: user-manual.txt:2943 #, no-wrap msgid "" "environment to that of the gas recirculated to the diver. Set this value for " @@ -5989,66 +5907,65 @@ msgid "" msgstr "" #. type: Title === -#: ./user-manual.txt:2980 +#: user-manual.txt:2945 #, no-wrap msgid "Language" msgstr "" #. type: Plain text -#: ./user-manual.txt:2982 +#: user-manual.txt:2947 msgid "Choose a language that _Subsurface_ will use." msgstr "" #. type: Target for macro image -#: ./user-manual.txt:2983 +#: user-manual.txt:2948 #, no-wrap msgid "images/Pref4_f20.jpg" msgstr "" #. type: Plain text -#: ./user-manual.txt:2993 +#: user-manual.txt:2958 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 operating system. If this " -"is for some reason undesirable one 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*." +"A checkbox lets you 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 operating system. To change " +"it, uncheck this checkbox and pick a language / country combination from the " +"list of locations. The _Filter_ text box lists 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:2994 +#: user-manual.txt:2959 #, no-wrap msgid "Network" msgstr "" #. type: Plain text -#: ./user-manual.txt:3000 +#: user-manual.txt:2966 msgid "" "This panel facilitates communication between _Subsurface_ and data sources " "on the Internet. This is important, for instance, when _Subsurface_ needs " -"to communicate with Internet services such as Cloud storage or the " +"to communicate with web services such as Cloud storage or the " "<<S_Companion,_Subsurface Companion app_>>. 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 " +"determined by your type of connection to the Internet and by the Internet " +"Service Provider (ISP) used. Your ISP should provide the appropriate " "information." msgstr "" #. type: Target for macro image -#: ./user-manual.txt:3001 +#: user-manual.txt:2967 #, no-wrap msgid "images/Pref5_f20.jpg" msgstr "" #. type: Plain text -#: ./user-manual.txt:3004 +#: user-manual.txt:2970 msgid "This dialogue has three sections:" msgstr "" #. type: Plain text -#: ./user-manual.txt:3012 +#: user-manual.txt:2978 #, no-wrap msgid "" "** _Proxy type_:\n" @@ -6065,20 +5982,20 @@ msgid "" msgstr "" #. type: Plain text -#: ./user-manual.txt:3017 +#: user-manual.txt:2983 #, no-wrap msgid "" -"** _Subsurface cloud storage_: To store one's dive log in the cloud, a valid " +"** _Subsurface cloud storage_: To store your dive log in the cloud, a valid " "email address\n" -" and password are required. This allows _Subsurface_ to email security " +" and password are required. This lets _Subsurface_ email security " "information\n" -" regarding cloud storage to a user, and to set up the cloud storage " +" regarding cloud storage to you, and to set up cloud storage " "appropriately.\n" " Two additional options are given:\n" msgstr "" #. type: Plain text -#: ./user-manual.txt:3018 +#: user-manual.txt:2984 #, no-wrap msgid "" "_Sync to cloud in the background_: This option allows saving of dive " @@ -6086,13 +6003,13 @@ msgid "" msgstr "" #. type: Plain text -#: ./user-manual.txt:3019 +#: user-manual.txt:2985 #, no-wrap -msgid "while the user performs other tasks within _Subsurface_.\n" +msgid "while you do other things within _Subsurface_.\n" msgstr "" #. type: Plain text -#: ./user-manual.txt:3020 +#: user-manual.txt:2986 #, no-wrap msgid "" "_Save password locally_: This allows local storage of the cloud storage " @@ -6100,95 +6017,94 @@ msgid "" msgstr "" #. type: Plain text -#: ./user-manual.txt:3021 +#: user-manual.txt:2987 #, no-wrap msgid "information is saved in raw text form, not encoded in any way.\n" msgstr "" #. type: Plain text -#: ./user-manual.txt:3026 +#: user-manual.txt:2991 #, no-wrap msgid "" -"** _Subsurface web service_: When one subscribes to the " +"** _Subsurface web service_: When you subscribe 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" +" checking the option _Save User ID locally?_, you ensure a local copy of " +"that userID is saved.\n" msgstr "" #. type: Title === -#: ./user-manual.txt:3029 +#: user-manual.txt:2994 #, no-wrap -msgid "Facebook Accesss" +msgid "Facebook Access" msgstr "" #. type: Plain text -#: ./user-manual.txt:3032 +#: user-manual.txt:2997 msgid "" -"This panel allows one to log into a Facebook account in order to transfer " -"information from Subsurface to Facefook." +"This panel lets you log into a Facebook account in order to transfer " +"information from Subsurface to Facebook." msgstr "" #. type: Target for macro image -#: ./user-manual.txt:3033 +#: user-manual.txt:2998 #, no-wrap msgid "images/Pref6_f20.jpg" msgstr "" #. type: Plain text -#: ./user-manual.txt:3041 +#: user-manual.txt:3006 msgid "" -"If one provides a valid Facebook userID and password, a connection to " -"Facebook is created. The connection to Facebook is closed when one closes " -"down Subsurface. Currently the checkbox labelled \"Keep me logged in to " +"If you provide a valid Facebook userID and password, a connection to " +"Facebook is created. That connection is closed when one closing down " +"Subsurface. Currently the checkbox labelled \"Keep me logged in to " "Subsurface\", on the login screen has no effect. See the section " "xref:S_facebook[Exporting dive profiles to Facebook] for more information." msgstr "" #. type: Title === -#: ./user-manual.txt:3042 +#: user-manual.txt:3007 #, no-wrap msgid "Georeference" msgstr "" #. type: Plain text -#: ./user-manual.txt:3050 +#: user-manual.txt:3015 msgid "" "_Subsurface_ provides a geo-lookup service (that is, given the coordinates " -"of a dive site (derived from a click on the *Dive Map panel* at the bottom " +"of a dive site) derived from a click on the *Dive Map panel* at the bottom " "right of the _Subsurface_ window, or from a GPS instrument or from the " -"_Subsurface_ Companion app), a lookup on the Internet is performed to find " -"the name of the closest known location. Obviously this function only works " -"if _Subsurface_ has an Internet connection. The preference of the dive site " -"name can be configured, e.g. _Country/State/City_ or _City/State/Country_ " -"(see image below)." +"_Subsurface_ Companion app). A search on the Internet is done to find the " +"name of the closest known location. This function only works if _Subsurface_ " +"has an Internet connection. The preference of the dive site name can be " +"configured, e.g. _Country/State/City_ or _City/State/Country_ (see image " +"below)." msgstr "" #. type: Target for macro image -#: ./user-manual.txt:3051 +#: user-manual.txt:3016 #, no-wrap msgid "images/Pref7_f20.jpg" msgstr "" #. type: Title == -#: ./user-manual.txt:3054 +#: user-manual.txt:3019 #, no-wrap msgid "The _Subsurface_ dive planner" msgstr "" #. type: Plain text -#: ./user-manual.txt:3059 +#: user-manual.txt:3024 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." +"Dive planning is an advanced feature of _Subsurface_, accessed 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:3067 +#: user-manual.txt:3032 msgid "" "The _Subsurface_ dive planner IS CURRENTLY EXPERIMENTAL and assumes the user " "is already familiar with the _Subsurface_ user interface. It is explicitly " @@ -6196,19 +6112,19 @@ msgid "" msgstr "" #. type: delimited block * -#: ./user-manual.txt:3070 +#: user-manual.txt:3035 msgid "" "The user is conversant with dive planning and has the necessary training to " "perform dive planning." msgstr "" #. type: delimited block * -#: ./user-manual.txt:3071 +#: user-manual.txt:3036 msgid "The user plans dives within his/her certification limits." msgstr "" #. type: delimited block * -#: ./user-manual.txt:3074 +#: user-manual.txt:3039 msgid "" "Dive planning makes large assumptions about the characteristics of the " "_average person_ and cannot compensate for individual physiology or health " @@ -6216,51 +6132,50 @@ msgid "" msgstr "" #. type: delimited block * -#: ./user-manual.txt:3075 +#: user-manual.txt:3040 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:3076 +#: user-manual.txt:3041 msgid "The user is familiar with the user interface of _Subsurface_." msgstr "" #. type: delimited block * -#: ./user-manual.txt:3078 +#: user-manual.txt:3043 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:3080 +#: user-manual.txt:3045 #, no-wrap msgid "The _Subsurface_ dive planner screen" msgstr "" #. type: Plain text -#: ./user-manual.txt:3085 +#: user-manual.txt:3050 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 Notes." +"into the sections on the left hand side of the screen. They are: Available " +"Gases, Rates, Planning, Gas Options and Notes." msgstr "" #. type: Plain text -#: ./user-manual.txt:3089 +#: user-manual.txt:3054 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 " +"At the top right hand is a green *design panel* on 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:3093 +#: user-manual.txt:3058 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 " @@ -6269,26 +6184,26 @@ msgid "" msgstr "" #. type: Target for macro image -#: ./user-manual.txt:3094 +#: user-manual.txt:3059 #, no-wrap msgid "images/PlannerWindow1_f20.jpg" msgstr "" #. type: Title === -#: ./user-manual.txt:3097 +#: user-manual.txt:3062 #, no-wrap msgid "Open circuit dives" msgstr "" #. type: Plain text -#: ./user-manual.txt:3100 +#: user-manual.txt:3065 msgid "" -"Towards the centre bottom of the planner (circled in blue in the image " +"Towards the center bottom of the planner (circled in blue in the image " "above) is a dropbox with three options. Select the appropriate one of these:" msgstr "" #. type: Plain text -#: ./user-manual.txt:3103 +#: user-manual.txt:3068 #, no-wrap msgid "" "** Open Circuit (the default)\n" @@ -6297,22 +6212,22 @@ msgid "" msgstr "" #. type: Plain text -#: ./user-manual.txt:3105 +#: user-manual.txt:3070 msgid "Choose the Open Circuit option." msgstr "" #. type: Plain text -#: ./user-manual.txt:3109 +#: user-manual.txt:3074 msgid "" -"In the top left-hand area of the planning screen, ensure that the constant " -"dive parameters are appropriate. These are: Start date and time of the " -"intended dive, Atmospheric Pressure and Altitude above sea level of the dive " -"site. The atmospheric pressure can also be entered as an altitude in metres, " +"In the top left-hand area of the planning screen, be sure the constant dive " +"parameters are appropriate. These are: Start date and time of the intended " +"dive, Atmospheric Pressure and Altitude above sea level of the dive " +"site. The atmospheric pressure can also be entered as an altitude in meters, " "assuming a sea-level atmospheric pressure of 1.013 bar." msgstr "" #. type: Plain text -#: ./user-manual.txt:3118 +#: user-manual.txt:3083 msgid "" "In the table labelled _Available Gases_, add the information of the " "cylinders to be used as well as the gas composition within that " @@ -6327,22 +6242,22 @@ msgid "" msgstr "" #. type: Plain text -#: ./user-manual.txt:3120 +#: user-manual.txt:3085 msgid "The profile of the planned dive can be created in two ways:" msgstr "" #. type: Plain text -#: ./user-manual.txt:3125 +#: user-manual.txt:3090 msgid "" -"Drag the waypoints (the small white circles) on the existing dive profile in " -"a way to represent the dive. Additional waypoints can be created by " -"double-clicking the existing dive profile. Waypoints can be deleted by " -"right-clicking a particular waypoint and selecting the _delete_ item from " -"the resulting context menu." +"Drag the waypoints (the small white circles) on the existing dive profile to " +"represent the dive. Additional waypoints can be created by double-clicking " +"the existing dive profile. Waypoints can be deleted by right-clicking a " +"particular waypoint and selecting the _delete_ item from the resulting " +"context menu." msgstr "" #. type: Plain text -#: ./user-manual.txt:3133 +#: user-manual.txt:3098 msgid "" "The most efficient way to create a dive profile is to enter the appropriate " "values into the table marked _Dive planner points_. The first line of the " @@ -6356,55 +6271,58 @@ msgid "" msgstr "" #. type: Title ==== -#: ./user-manual.txt:3134 +#: user-manual.txt:3099 #, no-wrap msgid "Recreational dives" msgstr "" #. type: Plain text -#: ./user-manual.txt:3149 +#: user-manual.txt:3116 +#, no-wrap msgid "" "Recreational mode is what comes closest to planning a dive based on the " -"non-decompression limit (NDL). It computes the maximal time a diver can " -"stay at the current depth without incurring any mandatory decompression " +"non-decompression limit (NDL).\n" +"It computes the maximum time a diver can stay at the current depth without " +"needing mandatory decompression\n" "stops and without using more than the existing gas (minus a reserve). The " -"planner automatically takes into account the nitrogen load incurred in " -"previous dives. But conventional dive tables are also used in a way that can " -"take into account previous dives. Why use a dive planner for recreational " -"dives? Using recreational dive tables, the maximum depth of a dive is taken " -"into account. However, few dives are undertaken at a constant depth " -"corresponding to the maximum depth (i.e. a \"square\" dive profile). This " -"means that dive tables overestimate the nitrogen load incurred during " -"previous dives. The _Subsurface_ dive planner calculates nitrogen load " -"according to the real dive profiles of all uploaded previous dives, in a " -"similar way as dive computers calculate nitrogen load during a dive. This " -"means that the diver gets 'credit' in terms of nitrogen loading for not " -"remaining at maximum depth during previous dives, enabling planning of a " -"longer subsequent dive. For the planner to work it is therefore crucial to " -"upload all previous dives onto _Subsurface_ before performing dive planning." -msgstr "" - -#. type: Plain text -#: ./user-manual.txt:3151 -msgid "To plan a dive, the appropriate settings need to be defined." +"planner automatically takes\n" +"into account the nitrogen load incurred in previous dives. But conventional " +"dive tables are also used in a\n" +"way that can take into account previous dives. Why use a dive planner for " +"recreational dives? Using\n" +"recreational dive tables, the maximum depth of a dive is taken into " +"account. But few dives are\n" +"done at a constant depth corresponding to the maximum depth (i.e. a " +"\"square\" dive profile). This means\n" +"dive tables overestimate the nitrogen load incurred during previous " +"dives. The _Subsurface_\n" +"dive planner calculates nitrogen load according to the real dive profiles of " +"all uploaded previous dives,\n" +"in a similar way as dive computers calculate nitrogen load during a " +"dive. This means that the diver gets 'credit,'\n" +"in terms of nitrogen load, for not remaining at maximum depth during\n" +"previous dives, so a longer subsequent dive can be planned.\n" +" For the planner to work it's crucial to upload all previous dives\n" +"onto _Subsurface_ before doing dive planning.\n" +"To plan a dive, the appropriate settings need to be defined.\n" msgstr "" #. type: Plain text -#: ./user-manual.txt:3154 +#: user-manual.txt:3119 msgid "" -"Ensure that the date and time is set to that of the intended dive. This " -"allows calculation of the nitrogen load incurred during previous dives." +"Ensure the date and time is set to that of the intended dive. This allows " +"calculation of the nitrogen load incurred during previous dives." msgstr "" #. type: Plain text -#: ./user-manual.txt:3157 +#: user-manual.txt:3122 msgid "" "Immediately under the heading _Planning_ are two checkboxes _Recreational_ " "and _Safety Stop_. Check these two boxes." msgstr "" #. type: Plain text -#: ./user-manual.txt:3161 +#: user-manual.txt:3126 msgid "" "Then define the cylinder size, the gas mixture (air or % oxygen) and the " "starting cylinder pressure in the top left-hand section of the planner under " @@ -6412,35 +6330,34 @@ msgid "" msgstr "" #. type: Plain text -#: ./user-manual.txt:3166 +#: user-manual.txt:3131 msgid "" "The planner calculates whether the specified cylinder contains enough " -"air/gas to complete the planned dive. In order for this to be realistic, " +"air/gas to complete the planned dive. In order for this to be accurate, " "under _Gas options_, specify an appropriate surface air consumption (SAC) " "rate for _Bottom SAC_. Suitable values are between 15 l/min and 30 l/min, " "with novice divers or difficult dives requiring SAC rates closer to 30l/min." msgstr "" #. type: Plain text -#: ./user-manual.txt:3175 +#: user-manual.txt:3140 msgid "" -"Define the amount of gas that the cylinder must have at the end of the " -"bottom section of the dive just before ascent. A value of 50 bar is often " -"used. The reason for this reserve gas is to provide for the possible need to " -"bring one's buddy to the surface using gas sharing. How much gas is used in " -"sharing depends on the depth of the ascent. This can be a bit hard to " -"estimate, so most agencies assume a fixed amount of gas, or actually of " -"pressure e.g. 40 or 50 bar or 25% or 33% (rule of thirds). But _Subsurface_ " -"can do better because it knows about the ascent and that is why we add the " -"amount of gas during the ascent (i.e. the \"deco gas“). Subsurface still " -"uses a fixed pressure „reserve“ but that is supposed to be for the " -"additional gas used around the realisation that there is a problem and one's " -"pulse rate goes up when one starts to buddy breathe. This reserve amount is " -"user configurable." +"Define the amount of gas the cylinder must have at the end of the bottom " +"section of the dive just before ascent. A value of 50 bar is often used. The " +"reason for this reserve gas is to provide for the possible need to bring a " +"buddy to the surface using gas sharing. How much gas is used in sharing " +"depends on the depth of the ascent. This can be difficult to estimate, so " +"most agencies assume a fixed amount of gas, or actually of pressure e.g. 40 " +"or 50 bar or 25% or 33% (rule of thirds). But _Subsurface_ can do better " +"because it knows about the ascent and that is why we add the amount of gas " +"during the ascent (i.e. the \"deco gas“). Subsurface still uses a fixed " +"pressure \"reserve\" but that's supposed to be for the additional gas used " +"when there's a problem and your pulse rate goes up when you start to buddy " +"breathe. This reserve amount is user configurable." msgstr "" #. type: Plain text -#: ./user-manual.txt:3183 +#: user-manual.txt:3148 msgid "" "Define the depth of the dive by dragging the waypoints (white dots) on the " "dive profile or (even better) defining the appropriate depths using the " @@ -6453,18 +6370,18 @@ msgid "" msgstr "" #. type: Plain text -#: ./user-manual.txt:3186 +#: user-manual.txt:3151 msgid "" "The ascent speed can be changed. The default ascent speeds are those " "considered safe for recreational divers." msgstr "" #. type: Plain text -#: ./user-manual.txt:3194 +#: user-manual.txt:3159 msgid "" -"The dive profile in the planner indicates the maximum dive time within " -"no-deco limits using the Bühlmann ZH-L16 algorithm and the gas and depth " -"settings specified as described above. The _Subsurface_ planner allows rapid " +"The dive profile in the planner shows the maximum dive time within no-deco " +"limits using the Bühlmann ZH-L16 algorithm and the gas and depth settings " +"specified as described above. The _Subsurface_ planner allows rapid " "assessment of dive duration as a function of dive depth, given the nitrogen " "load incurred during previous dives. The dive plan includes estimates of the " "amount of air/gas used, depending on the cylinder settings specified under " @@ -6476,40 +6393,40 @@ msgid "" msgstr "" #. type: Plain text -#: ./user-manual.txt:3198 +#: user-manual.txt:3163 msgid "" "Below is an image of a dive plan for a recreational dive at 30 " -"metres. Although the no-deco limit (NDL) is 23 minutes, the duration of the " -"dive is limited by the amount of air in the cylinder, reflected by the " -"information in the text box at the bottom right of the panel that requires " -"sufficient air for buddy-sharing during the ascent." +"meters. Although the no-deco limit (NDL) is 23 minutes, the duration of the " +"dive is limited by the amount of air in the cylinder. That is shown in the " +"text box at the bottom right of the panel, requiring sufficient air for " +"buddy-sharing during ascent." msgstr "" #. type: Target for macro image -#: ./user-manual.txt:3199 +#: user-manual.txt:3164 #, no-wrap msgid "images/rec_diveplan.jpg" msgstr "" #. type: Title ==== -#: ./user-manual.txt:3201 +#: user-manual.txt:3166 #, no-wrap msgid "Non-recreational open circuit dives, including decompression" msgstr "" #. type: Plain text -#: ./user-manual.txt:3205 +#: user-manual.txt:3170 msgid "" "Non-recreational dive planning involves exceeding the no-deco limits and/or " -"using multiple breathing gases. Such dives are planned in three stages:" +"using multiple breathing gases. These dives are planned in three stages:" msgstr "" #. type: Plain text -#: ./user-manual.txt:3216 +#: user-manual.txt:3182 #, no-wrap msgid "" -"*a) Nitrogen management*: This is performed by specifying the rates for " -"descent and ascent,\n" +"*a) Nitrogen management*: This is done by specifying the rates for descent " +"and ascent,\n" "as well as the deco model (GFLow, GFHigh or Conservatism level) under the " "headings _Rates_ and _Planning_\n" "to the bottom left of the planning screen. Two deco models are supported the " @@ -6521,47 +6438,47 @@ msgid "" "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 values 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 " +"used without changing the original values in the _Preferences_.\n" +"Gradient Factor settings strongly affect the calculated ceilings and their " +"depths.\n" +"A very low GFLow value brings on decompression stops early during the " "dive.\n" " ** For more information about Gradient factors, see the section on " "xref:S_GradientFactors[Gradient Factor Preference settings].\n" msgstr "" #. type: Plain text -#: ./user-manual.txt:3221 +#: user-manual.txt:3187 msgid "" "If the VPM-B model is selected, the Conservatism_level needs to be specified " "on a scale of 0 (least conservative) to 4 (most conservative). This model " "tends to give deco stops at deeper levels than the Bühlmann model and often " "results in slightly shorter dive durations than the Bühlmann model. When " -"selecting one of these models, keep in mind that they are NOT exact " -"physiological models but only mathematical models that appear to work in " -"practice." +"selecting one of these models, keep in mind they are NOT exact physiological " +"models but only mathematical models that appear to work in practice." msgstr "" #. type: Plain text -#: ./user-manual.txt:3223 +#: user-manual.txt:3189 msgid "For more information external to this manual see:" msgstr "" #. type: Plain text -#: ./user-manual.txt:3225 +#: user-manual.txt:3191 msgid "" "link:http://www.tek-dive.com/portal/upload/M-Values.pdf[Understanding " "M-values by Erik Baker, _Immersed_ Vol. 3, No. 3.]" msgstr "" #. type: Plain text -#: ./user-manual.txt:3226 +#: user-manual.txt:3192 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]" msgstr "" #. type: Plain text -#: ./user-manual.txt:3228 +#: user-manual.txt:3194 msgid "" "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: " @@ -6570,21 +6487,21 @@ msgid "" msgstr "" #. type: Plain text -#: ./user-manual.txt:3236 +#: user-manual.txt:3202 msgid "" "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 by a " -"light grey line on the dive profile. 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." +"and is specified for several depth ranges, using the average (or mean) depth " +"as a yardstick. The mean depth of the dive plan is shown by a light grey " +"line on the dive profile. 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, the descent phase of the planned dive will be " +"at the maximal descent rate specified in the _Rates_ section of the dive " +"setup." msgstr "" #. type: Plain text -#: ./user-manual.txt:3245 +#: user-manual.txt:3211 #, no-wrap msgid "" "*b) Oxygen management*: In the *Gas Options* part of the dive specification, " @@ -6604,88 +6521,85 @@ msgid "" msgstr "" #. type: Plain text -#: ./user-manual.txt:3259 +#: user-manual.txt:3228 #, no-wrap msgid "" -"*c) Gas management*: With open-circuit dives this is a primary " -"consideration. One needs to keep within the limits of the amount of gas " -"within the dive\n" +"*c) Gas management*: With open-circuit dives this is a primary\n" +"consideration. Divers need to keep within the limits of the amount of\n" +"gas within the dive\n" "cylinder(s), allowing for an appropriate margin for a 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 " +"liters/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 15-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" +"management, a guess\n" +"is not sufficient and you needs to\n" +"monitor gas consumption on a regular basis, dependent on different dive " +"conditions and/or equipment.\n" "The planner calculates the total volume of gas used during the dive and " "issues 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" +"if you exceeds the total amount of gas available. Good practice demands that " +"divers not dive to\n" +"the limit of the gas supply but that an appropriate reserve is kept\n" +"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:3271 +#: user-manual.txt:3240 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 bue 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. It is NOT necessary to specify the ascent " -"part of the dive since the planner calculates this, based on the settings " -"that have been specified. If any of the management limits (for nitrogen, " -"oxygen or gas) is exceeded, the surface above the dive profile changes from " -"BLUE to RED." +"Now you can start the detailed time-depth planning of the dive. _Subsurface_ " +"offers an unique graphical interface for doing planning. Themechanics are " +"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 blue 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 the profile reflects the intended dive. Drag the waypoints to " +"represent the depth and duration of the dive. It is NOT necessary to specify " +"the ascent part of the dive since the planner calculates this, based on the " +"settings that have been specified. If any of the management limits (for " +"nitrogen, oxygen or gas) are exceeded, the surface above the dive profile " +"changes from BLUE to RED." msgstr "" #. type: Plain text -#: ./user-manual.txt:3283 +#: user-manual.txt:3252 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 _Available Gases_ table. 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." +"table on the left of the dive planner panel. Be sure the _Used Gas_ value in " +"each row of that table corresponds to one of the gas mixtures specified in " +"the _Available Gases_ table. 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 fulfill decompression requirements for that dive. A waypoint can be " +"moved by selecting it and by using the arrow keys. The waypoints listed in " +"the _Dive Planner Points_ dialogue can be edited by hand in order to get a " +"precise presentation of the dive plan. In fact, you can create the whole " +"dive profile by editing the _Dive Planner Points_ dialog." msgstr "" #. type: Plain text -#: ./user-manual.txt:3291 +#: user-manual.txt:3260 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." +"Show 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. These changes " +"can be deleted by right-clicking the gas change and manually creating a gas " +"change by right-clicking on the appropriate waypoint." msgstr "" #. type: Plain text -#: ./user-manual.txt:3300 +#: user-manual.txt:3269 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 " @@ -6698,34 +6612,34 @@ msgid "" msgstr "" #. type: Plain text -#: ./user-manual.txt:3303 +#: user-manual.txt:3272 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:3304 +#: user-manual.txt:3273 #, no-wrap msgid "images/DivePlanner2_f20.jpg" msgstr "" #. type: Plain text -#: ./user-manual.txt:3309 +#: user-manual.txt:3278 msgid "" -"Once the above has been completed, one can save it by clicking the _Save_ " -"button towards the top middle of the planner. The saved dive plan will " -"appear in the *Dive List* panel of _Subsurface_." +"Once the above steps have been completed, save by clicking the _Save_ button " +"towards the top middle of the planner. The saved dive plan will appear in " +"the *Dive List* panel of _Subsurface_." msgstr "" #. type: Plain text -#: ./user-manual.txt:3311 +#: user-manual.txt:3280 #, no-wrap msgid "*The dive plan details*\n" msgstr "" #. type: Plain text -#: ./user-manual.txt:3319 +#: user-manual.txt:3288 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 " @@ -6738,7 +6652,7 @@ msgid "" msgstr "" #. type: Plain text -#: ./user-manual.txt:3324 +#: user-manual.txt:3293 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 " @@ -6748,13 +6662,13 @@ msgid "" msgstr "" #. type: Title === -#: ./user-manual.txt:3325 +#: user-manual.txt:3294 #, no-wrap msgid "Planning pSCR dives" msgstr "" #. type: Plain text -#: ./user-manual.txt:3340 +#: user-manual.txt:3309 #, no-wrap msgid "" "To plan a dive using a passive semi-closed rebreather (pSCR), select _pSCR_ " @@ -6767,8 +6681,8 @@ msgid "" "ratio (default 10:1) as well as the metabolism rate. The calculation also " "takes the oxygen drop\n" "accross the mouthpiece of the rebreather into account. If the\n" -"pO~2~ drops below what is considered a save value, a warning appears in the " -"_Dive plan\n" +"pO~2~ drops below what is considered safe, a warning appears in the _Dive " +"plan\n" "details_. A typical pSCR configuration is with a single cylinder and one or " "more bail-out\n" "cylinders. Therefore the setup of the _Available gases_ and the _Dive " @@ -6784,26 +6698,26 @@ msgid "" msgstr "" #. type: Target for macro image -#: ./user-manual.txt:3341 +#: user-manual.txt:3310 #, no-wrap msgid "images/Planner_pSCR1_f20.jpg" msgstr "" #. type: Title === -#: ./user-manual.txt:3344 +#: user-manual.txt:3313 #, no-wrap msgid "Planning CCR dives" msgstr "" #. type: Plain text -#: ./user-manual.txt:3348 +#: user-manual.txt:3317 msgid "" "To plan a dive using a closed circuit rebreather, select the _CCR_ option in " "the dropdown list, circled in blue in the image below." msgstr "" #. type: Plain text -#: ./user-manual.txt:3352 +#: user-manual.txt:3321 #, no-wrap msgid "" "*Available gases*: In the _Available gases_ table, enter the cylinder " @@ -6814,7 +6728,7 @@ msgid "" msgstr "" #. type: Plain text -#: ./user-manual.txt:3362 +#: user-manual.txt:3331 #, no-wrap msgid "" "*Entering setpoints*: Specify a default setpoint in the Preferences tab, by " @@ -6824,56 +6738,56 @@ msgid "" "use the default setpoint value. Then, different setpoints can be specified " "for dive segments\n" "in the _Dive planner points_ table. A zero setpoint\n" -"means the diver bails out to open circuit mode for that segment. The " -"decompression is always calculated\n" +"means the diver bails out to open circuit mode for that " +"segment. Decompression is always calculated\n" "using the setpoint of the last manually entered segment. So, to plan a bail " "out ascent for a\n" "CCR dive, add a one-minute dive segment to the end with a setpoint value of " "0. The decompression\n" "algorithm does not switch deco-gases automatically while in CCR mode " -"(i.e. when a positive setpoint is specified) but,\n" -"of course, this is calculated for bail out ascents.\n" +"(i.e. when a positive setpoint is specified) but\n" +"this is calculated for bail out ascents.\n" msgstr "" #. type: Plain text -#: ./user-manual.txt:3364 +#: user-manual.txt:3333 msgid "The dive profile for a CCR dive may look something like the image below." msgstr "" #. type: Target for macro image -#: ./user-manual.txt:3365 +#: user-manual.txt:3334 #, no-wrap msgid "images/Planner_CCR1_f20.jpg" msgstr "" #. type: Plain text -#: ./user-manual.txt:3369 +#: user-manual.txt:3338 msgid "" "Note that, in the _Dive plan details_, the gas consumption for a CCR segment " -"is not calculated, so gas consumptions of 0 litres are the norm." +"is not calculated, so gas consumptions of 0 liters are the norm." msgstr "" #. type: Title === -#: ./user-manual.txt:3371 +#: user-manual.txt:3340 #, no-wrap msgid "Modifying an existing dive plan" msgstr "" #. type: Plain text -#: ./user-manual.txt:3378 +#: user-manual.txt:3347 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." +"List*, like any other dive log. Within the *Dive List* there is no way to " +"change a saved dive plan. To change 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, letting changes be made and " +"saved as usual." msgstr "" #. type: Plain text -#: ./user-manual.txt:3384 +#: user-manual.txt:3353 msgid "" -"In addition there is the option \"Save new\". This keeps the original " +"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 " @@ -6881,56 +6795,56 @@ msgid "" msgstr "" #. type: Title === -#: ./user-manual.txt:3385 +#: user-manual.txt:3354 #, no-wrap msgid "Planning for repetitive dives" msgstr "" #. type: Plain text -#: ./user-manual.txt:3392 +#: user-manual.txt:3361 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." +"repetitive dive set are specified appropriately in the top left-hand _Start " +"Time_ field. _Subsurface_ calculates the gas loading figures and the affect " +"of the first dive is evaluated on later dives." msgstr "" #. type: Plain text -#: ./user-manual.txt:3398 +#: user-manual.txt:3367 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." +"If you have just completed a long/deep dive and are planning another dive, " +"then highlight, in the *Dive List*, the dive that has just been done then " +"activate the planner. Depending on the start time of the planned dive, the " +"planner takes into account the gas loading during the completed dive and " +"plans accordingly." msgstr "" #. type: Plain text -#: ./user-manual.txt:3403 +#: user-manual.txt:3372 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." +"template dive can be created conforming to one of the configurations. If you " +"want to plan a dive using this configuration, 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:3404 +#: user-manual.txt:3373 #, no-wrap msgid "Printing the dive plan" msgstr "" #. type: Plain text -#: ./user-manual.txt:3409 +#: user-manual.txt:3378 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." +"Plan Details_ for wet notes. You can also cut and paste the _Dive Plan " +"Details_ to include in a text file or word processing document." msgstr "" #. type: Plain text -#: ./user-manual.txt:3419 +#: user-manual.txt:3388 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 " @@ -6941,18 +6855,18 @@ msgid "" "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 " +"function 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:3420 +#: user-manual.txt:3389 #, no-wrap msgid "Description of the Subsurface Main Menu items" msgstr "" #. type: Plain text -#: ./user-manual.txt:3425 +#: user-manual.txt:3394 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 " @@ -6960,302 +6874,293 @@ msgid "" msgstr "" #. type: Title === -#: ./user-manual.txt:3426 +#: user-manual.txt:3395 #, no-wrap msgid "File" msgstr "" #. type: Plain text -#: ./user-manual.txt:3429 +#: user-manual.txt:3398 msgid "" "<<S_NewLogbook,_New Logbook_>> - Close the currently open dive logbook and " "clear all dive information." msgstr "" #. type: Plain text -#: ./user-manual.txt:3431 -msgid "" -"_Open logbook_ - This opens the file manager in order to select a dive " -"logbook to open." +#: user-manual.txt:3400 +msgid "_Open logbook_ - Open the file manager to select a dive logbook to open." msgstr "" #. type: Plain text -#: ./user-manual.txt:3432 +#: user-manual.txt:3401 msgid "" "_Open cloud storage_ - Open the dive log previously saved in " "<<S_Cloud_storage,_Cloud storage_>>." msgstr "" #. type: Plain text -#: ./user-manual.txt:3433 -msgid "_Save_ - Save the dive logbook that is currently open." +#: user-manual.txt:3402 +msgid "_Save_ - Save the dive logbook currently open." msgstr "" #. type: Plain text -#: ./user-manual.txt:3434 +#: user-manual.txt:3403 msgid "" "_Save to cloud storage_ - Save the current dive log to " "<<S_Cloud_storage,_Cloud storage_>>." msgstr "" #. type: Plain text -#: ./user-manual.txt:3435 +#: user-manual.txt:3404 msgid "_Save as_ - Save the current logbook under a different file name." msgstr "" #. type: Plain text -#: ./user-manual.txt:3436 -msgid "_Close_ - Close the dive logbook that is currently open." +#: user-manual.txt:3405 +msgid "_Close_ - Close the dive logbook currently open." msgstr "" #. type: Plain text -#: ./user-manual.txt:3438 +#: user-manual.txt:3407 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:3439 +#: user-manual.txt:3408 msgid "<<S_PrintDivelog,_Print_>> - Print the currently open logbook." msgstr "" #. type: Plain text -#: ./user-manual.txt:3440 +#: user-manual.txt:3409 msgid "<<S_Preferences,_Preferences_>> - Set the _Subsurface_ preferences." msgstr "" #. type: Plain text -#: ./user-manual.txt:3441 +#: user-manual.txt:3410 msgid "" "<<S_FindMovedImages, _Find moved images_>> - If photos taken during dives " "have been moved to" msgstr "" #. type: Plain text -#: ./user-manual.txt:3442 +#: user-manual.txt:3411 msgid "" "a different disk or directory, locate them and link them to the appropriate " "dives." msgstr "" #. type: Plain text -#: ./user-manual.txt:3443 +#: user-manual.txt:3412 msgid "" "<<S_Configure,_Configure dive computer_>> - Edit the configuration of a dive " "computer." msgstr "" #. type: Plain text -#: ./user-manual.txt:3444 +#: user-manual.txt:3413 msgid "_Quit_ - Quit _Subsurface_." msgstr "" #. type: Title === -#: ./user-manual.txt:3445 +#: user-manual.txt:3414 #, no-wrap msgid "Import" msgstr "" #. type: Plain text -#: ./user-manual.txt:3448 +#: user-manual.txt:3417 msgid "" "<<S_ImportDiveComputer,_Import from dive computer_>> - Import dive " "information from a dive computer." msgstr "" #. type: Plain text -#: ./user-manual.txt:3450 +#: user-manual.txt:3419 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:3452 +#: user-manual.txt:3421 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:3454 +#: user-manual.txt:3423 msgid "" "<<S_ImportingDivelogsDe,_Import from Divelogs.de_>> - Import dive " "information from _www.Divelogs.de_." msgstr "" #. type: Title === -#: ./user-manual.txt:3455 +#: user-manual.txt:3424 #, no-wrap msgid "Log" msgstr "" #. type: Plain text -#: ./user-manual.txt:3457 +#: user-manual.txt:3426 msgid "" "<<S_EnterData,_Add Dive_>> - Manually add a new dive to the *Dive List* " "panel." msgstr "" #. type: Plain text -#: ./user-manual.txt:3458 +#: user-manual.txt:3427 msgid "" -"_Edit dive_ - Edit a dive of which the profile was entered by hande and not " -"from a dive computer." +"_Edit dive_ - Edit a dive where the profile was entered by hand and not from " +"a dive computer." msgstr "" #. type: Plain text -#: ./user-manual.txt:3459 -msgid "<<S_DivePlanner,_Plan Dive_>> - This feature allows the planning of dives." +#: user-manual.txt:3428 +msgid "<<S_DivePlanner,_Plan Dive_>> - Plan dives." msgstr "" #. type: Plain text -#: ./user-manual.txt:3460 +#: user-manual.txt:3429 msgid "" "<<S_Replan,_Edit dive in planner_>> - Edit a dive plan that has been saved " "into the *Dive List*." msgstr "" #. type: Plain text -#: ./user-manual.txt:3462 +#: user-manual.txt:3431 msgid "" -"<<S_CopyComponents,_Copy dive components_>> - By selecting this option, one " -"can copy information from several fields of a dive log onto the clipboard." +"<<S_CopyComponents,_Copy dive components_>> - Copy information from several " +"fields of a dive log onto the clipboard." msgstr "" #. type: Plain text -#: ./user-manual.txt:3464 +#: user-manual.txt:3433 msgid "" "_Paste dive components_ - Paste, into the selected dives in the *Dive List*, " "the information copied using the _Copy dive components_ option." msgstr "" #. type: Plain text -#: ./user-manual.txt:3466 +#: user-manual.txt:3435 msgid "" "<<S_Renumber,_Renumber_>> - Renumber the dives listed in the *Dive List* " "panel." msgstr "" #. type: Plain text -#: ./user-manual.txt:3468 +#: user-manual.txt:3437 msgid "" "<<S_Group,_Auto Group_>> - Group the dives in the *Dive List* panel into " "dive trips." msgstr "" #. type: Plain text -#: ./user-manual.txt:3469 +#: user-manual.txt:3438 msgid "" "<<S_DeviceNames,_Edit Device Names_>> - Edit the names of dive computers to " -"facilitate your logs." +"coordinate your logs." msgstr "" #. type: Plain text -#: ./user-manual.txt:3470 +#: user-manual.txt:3439 msgid "" "<<S_Filter,_Filter divelist_>> - Select only some dives, based on specific " "tags or dive criteria." msgstr "" #. type: Title === -#: ./user-manual.txt:3471 +#: user-manual.txt:3440 #, no-wrap msgid "View" msgstr "" #. type: Plain text -#: ./user-manual.txt:3474 -msgid "" -"<<S_ViewPanels,_All_>> - View the four main _Subsurface_ panels " -"simmultaneously." +#: user-manual.txt:3443 +msgid "<<S_ViewPanels,_All_>> - View the four main _Subsurface_ panels all at once." msgstr "" #. type: Plain text -#: ./user-manual.txt:3475 +#: user-manual.txt:3444 msgid "<<S_ViewPanels,_Dive List_>> - View only the *Dive List* panel." msgstr "" #. type: Plain text -#: ./user-manual.txt:3476 +#: user-manual.txt:3445 msgid "<<S_ViewPanels,_Profile_>> - View only the *Dive Profile* panel." msgstr "" #. type: Plain text -#: ./user-manual.txt:3477 +#: user-manual.txt:3446 msgid "<<S_ViewPanels,_Info_>> - View only the *Notes* panel." msgstr "" #. type: Plain text -#: ./user-manual.txt:3478 +#: user-manual.txt:3447 msgid "<<S_ViewPanels,_Globe_>> - View only the *World Map* panel." msgstr "" #. type: Plain text -#: ./user-manual.txt:3480 +#: user-manual.txt:3449 msgid "" "_Yearly Statistics_ - Display summary statistics about dives during this and " "past years." msgstr "" #. type: Plain text -#: ./user-manual.txt:3481 +#: user-manual.txt:3450 msgid "" -"_Prev DC_ - If a single dive was logged from more than one dive computer, " -"switch to data from" +"_Prev DC_ - Switch to data from previous dive computer, if a single dive was " +"logged from more than one." msgstr "" #. type: Plain text -#: ./user-manual.txt:3482 -msgid "previous dive computer." -msgstr "" - -#. type: Plain text -#: ./user-manual.txt:3483 +#: user-manual.txt:3451 msgid "_Next DC_ - Switch to next dive computer." msgstr "" #. type: Plain text -#: ./user-manual.txt:3484 +#: user-manual.txt:3452 msgid "_Full Screen_ - Toggles Full Screen mode." msgstr "" #. type: Title === -#: ./user-manual.txt:3485 +#: user-manual.txt:3453 #, no-wrap msgid "Share on" msgstr "" #. type: Plain text -#: ./user-manual.txt:3487 +#: user-manual.txt:3455 msgid "" "<<S_Facebook,_Facebook_>> - Share the currently selected dive on your " "Facebook timeline." msgstr "" #. type: Title === -#: ./user-manual.txt:3489 +#: user-manual.txt:3457 #, no-wrap msgid "Help" msgstr "" #. type: Plain text -#: ./user-manual.txt:3492 +#: user-manual.txt:3460 msgid "" "_About Subsurface_ - Show a panel with the version number of _Subsurface_ as " "well as licensing information." msgstr "" #. type: Plain text -#: ./user-manual.txt:3494 +#: user-manual.txt:3462 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:3496 +#: user-manual.txt:3464 msgid "" "<<S_UserSurvey,_User survey_>> - Help to make _Subsurface_ even better by " "taking part in our user survey or by completing another survey if your " @@ -7263,12 +7168,12 @@ msgid "" msgstr "" #. type: Plain text -#: ./user-manual.txt:3497 +#: user-manual.txt:3465 msgid "_User manual_ - Open a window showing this user manual." msgstr "" #. type: Title == -#: ./user-manual.txt:3500 +#: user-manual.txt:3468 #, no-wrap msgid "" "APPENDIX A: Operating system specific information for importing dive " @@ -7276,27 +7181,27 @@ msgid "" msgstr "" #. type: Title === -#: ./user-manual.txt:3502 +#: user-manual.txt:3470 #, 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:3503 +#: user-manual.txt:3471 #, no-wrap msgid "images/icons/drivers.jpg" msgstr "" #. type: Plain text -#: ./user-manual.txt:3508 +#: user-manual.txt:3476 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)." +"in order to communicate with the dive computer, the way the dive computer " +"prefers (e.g. Bluetooth, USB, infra-red)." msgstr "" #. type: Plain text -#: ./user-manual.txt:3514 +#: user-manual.txt:3482 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 " @@ -7305,7 +7210,7 @@ msgid "" msgstr "" #. type: Plain text -#: ./user-manual.txt:3518 +#: user-manual.txt:3486 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 " @@ -7313,7 +7218,7 @@ msgid "" msgstr "" #. type: Plain text -#: ./user-manual.txt:3525 +#: user-manual.txt:3493 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 " @@ -7324,84 +7229,83 @@ msgid "" msgstr "" #. type: Title === -#: ./user-manual.txt:3527 +#: user-manual.txt:3495 #, 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:3528 +#: user-manual.txt:3496 #, no-wrap msgid "images/icons/usb.jpg" msgstr "" #. type: Plain text -#: ./user-manual.txt:3536 +#: user-manual.txt:3504 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:" +"When connecting a dive computer by using a USB connector, usually " +"_Subsurface_ will either propose a drop down list with 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 ways to find out what the device name is:" msgstr "" #. type: Plain text -#: ./user-manual.txt:3541 +#: user-manual.txt:3509 msgid "" "Simply try COM1, COM2, etc. The drop down list should contain all connected " "COM devices." msgstr "" #. type: Title ==== -#: ./user-manual.txt:3542 ./user-manual.txt:3636 +#: user-manual.txt:3510 user-manual.txt:3608 #, no-wrap msgid "On MacOS:" msgstr "" #. type: Plain text -#: ./user-manual.txt:3545 +#: user-manual.txt:3513 msgid "The drop down box should find all connected dive computers." msgstr "" #. type: Block title -#: ./user-manual.txt:3546 +#: user-manual.txt:3514 #, no-wrap msgid "On Linux:" msgstr "" #. type: Plain text -#: ./user-manual.txt:3549 +#: user-manual.txt:3517 msgid "There is a definitive way to find the port:" msgstr "" #. type: Plain text -#: ./user-manual.txt:3551 +#: user-manual.txt:3519 msgid "Disconnect the USB cable from the dive computer" msgstr "" #. type: Plain text -#: ./user-manual.txt:3552 +#: user-manual.txt:3520 msgid "Open a terminal" msgstr "" #. type: Plain text -#: ./user-manual.txt:3553 ./user-manual.txt:3555 +#: user-manual.txt:3521 user-manual.txt:3523 msgid "Type the command: 'dmesg' and press enter" msgstr "" #. type: Plain text -#: ./user-manual.txt:3554 +#: user-manual.txt:3522 msgid "Plug in the USB cable of the dive computer" msgstr "" #. type: Plain text -#: ./user-manual.txt:3557 +#: user-manual.txt:3525 msgid "A message similar to this one should appear:" msgstr "" #. type: Plain text -#: ./user-manual.txt:3573 +#: user-manual.txt:3541 #, no-wrap msgid "" "\tusb 2-1.1: new full speed USB device number 14 using ehci_hcd\n" @@ -7422,7 +7326,7 @@ msgid "" msgstr "" #. type: Plain text -#: ./user-manual.txt:3578 +#: user-manual.txt:3546 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 " @@ -7430,28 +7334,31 @@ msgid "" msgstr "" #. type: Plain text -#: ./user-manual.txt:3580 -msgid "Ensuring that the user has write permission to the USB serial port:" +#: user-manual.txt:3548 +msgid "Ensuring the user has write permission to the USB serial port:" msgstr "" #. type: Plain text -#: ./user-manual.txt:3586 +#: user-manual.txt:3558 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'." +"who are members special group that can be e.g. +dialout+ or +uucp+. This " +"can be verified by listing the appropriate device permissions e.g. by +ls -l " +"/dev/ttyUSB0+. Note that the number in the file name depends on how many USB " +"devices you have connected, and must be adjusted appropriately. If one is " +"not root, one may not be a member of that group and won't be able to use the " +"USB port. Let us assume one's username is 'johnB'." msgstr "" #. type: Plain text -#: ./user-manual.txt:3590 +#: user-manual.txt:3562 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:3595 +#: user-manual.txt:3567 #, no-wrap msgid "" "Type: +id johnB+ This lists all the groups that johnB belongs to and\n" @@ -7463,7 +7370,7 @@ msgid "" msgstr "" #. type: Plain text -#: ./user-manual.txt:3597 +#: user-manual.txt:3569 #, no-wrap msgid "" "Under some circumstances this change takes only effect (eg. on Ubuntu) " @@ -7472,7 +7379,7 @@ msgid "" msgstr "" #. type: Plain text -#: ./user-manual.txt:3602 +#: user-manual.txt:3574 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 " @@ -7480,30 +7387,30 @@ msgid "" msgstr "" #. type: Title === -#: ./user-manual.txt:3605 +#: user-manual.txt:3577 #, no-wrap msgid "Manually setting up Bluetooth enabled devices" msgstr "" #. type: Plain text -#: ./user-manual.txt:3612 +#: user-manual.txt:3584 msgid "" "For dive computers communicating through Bluetooth like the Heinrichs " "Weikamp Frog or the Shearwater Predator, Petrel and Nerd there is a " -"different procedure to get the devices name to communicate with " +"different procedure to get the device’s name to communicate with " "_Subsurface_. Follow these steps:" msgstr "" #. type: Plain text -#: ./user-manual.txt:3614 +#: user-manual.txt:3586 #, no-wrap msgid "" -"*For the dive computer, after enabling Bluetooth, ensure it is in Upload " +"*For the dive computer, after enabling Bluetooth, be sure it is in Upload " "mode.*\n" msgstr "" #. type: Plain text -#: ./user-manual.txt:3618 +#: user-manual.txt:3590 msgid "" "For Bluetooth pairing of the dive computer, refer to the manufacturer's user " "guide. When using a Shearwater Predator/Petrel/Nerd, select _Dive Log -> " @@ -7511,13 +7418,13 @@ msgid "" msgstr "" #. type: Plain text -#: ./user-manual.txt:3620 +#: user-manual.txt:3592 #, no-wrap msgid "*Pair the _Subsurface_ computer with the dive computer.*\n" msgstr "" #. type: Plain text -#: ./user-manual.txt:3629 +#: user-manual.txt:3601 msgid "" "Bluetooth is most likely already enabled. For pairing with the dive computer " "choose _Control Panel -> Bluetooth Devices -> Add Wireless Device_. This " @@ -7529,21 +7436,21 @@ msgid "" msgstr "" #. type: Plain text -#: ./user-manual.txt:3632 +#: user-manual.txt:3604 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:3635 +#: user-manual.txt:3607 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:3642 +#: user-manual.txt:3614 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 " @@ -7552,33 +7459,32 @@ msgid "" msgstr "" #. type: Plain text -#: ./user-manual.txt:3645 +#: user-manual.txt:3617 msgid "" -"Once the pairing is completed the correct device is shown in the 'Device or " +"Once the pairing is complete, the correct device is shown in the 'Device or " "Mount Point' drop-down in the _Subsurface_ *Import* dialog." msgstr "" #. type: Title ==== -#: ./user-manual.txt:3646 +#: user-manual.txt:3618 #, no-wrap msgid "On Linux" msgstr "" #. type: Plain text -#: ./user-manual.txt:3654 +#: user-manual.txt:3626 msgid "" -"Ensure Bluetooth is enabled on the _Subsurface_ computer. On most common " +"Be sure 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 on the right " -"of the toolbar at the top of the screen. Users have reported difficulties " -"with some Bluetooth controllers. If you have an onboard controller, try " -"that first. It is simplest if you remove any USB Bluetooth dongles. If you " -"have a USB dongle that came with your dive computer, try that before any " -"others." +"straightforward. For instance, Gnome3 shows a Bluetooth icon on the right of " +"the toolbar at the top of the screen. Users have reported difficulties with " +"some Bluetooth controllers. If you have an onboard controller, try that " +"first. It is simplest if you remove any USB Bluetooth dongles. If you have " +"a USB dongle that came with your dive computer, try that before any others." msgstr "" #. type: Plain text -#: ./user-manual.txt:3658 +#: user-manual.txt:3630 msgid "" "Setting up a connection to download dives from your Bluetooth-enabled " "device, such as the _Shearwater Petrel_, is not yet an automated process and " @@ -7587,23 +7493,23 @@ msgid "" msgstr "" #. type: Plain text -#: ./user-manual.txt:3660 +#: user-manual.txt:3632 msgid "Enable the Bluetooth controller and pair your dive computer" msgstr "" #. type: Plain text -#: ./user-manual.txt:3661 +#: user-manual.txt:3633 msgid "Establish an RFCOMM connection" msgstr "" #. type: Title ===== -#: ./user-manual.txt:3662 ./user-manual.txt:3802 +#: user-manual.txt:3634 user-manual.txt:3774 #, no-wrap msgid "Download the dives with Subsurface" msgstr "" #. type: Plain text -#: ./user-manual.txt:3668 +#: user-manual.txt:3640 msgid "" "Ensure the dive computer is in upload mode. On the _Shearwater Petrel_, " "_Petrel 2_ and _Nerd_ cycle through the menu, select 'Dive Log', then " @@ -7614,7 +7520,7 @@ msgid "" msgstr "" #. type: Plain text -#: ./user-manual.txt:3673 +#: user-manual.txt:3645 msgid "" "To establish the connection, establish root access through +sudo+ or +su+. " "The correct permission is required to download the dives in the computer. On " @@ -7624,23 +7530,23 @@ msgid "" msgstr "" #. type: Plain text -#: ./user-manual.txt:3675 +#: user-manual.txt:3647 msgid "+sudo usermod -a -G dialout username+" msgstr "" #. type: Plain text -#: ./user-manual.txt:3677 +#: user-manual.txt:3649 msgid "Then log out and log in for the change to take effect." msgstr "" #. type: Title ===== -#: ./user-manual.txt:3678 +#: user-manual.txt:3650 #, no-wrap msgid "Enabling the Bluetooth controller and pairing your dive computer" msgstr "" #. type: Plain text -#: ./user-manual.txt:3684 +#: user-manual.txt:3656 msgid "" "Attempt to set up the Bluetooth controller and pair your dive computer using " "the graphical environment of the operating system. After setting the dive " @@ -7651,15 +7557,15 @@ msgid "" msgstr "" #. type: Plain text -#: ./user-manual.txt:3687 +#: user-manual.txt:3659 msgid "" -"If the graphical method didn't work, pair the device from the command " +"If the graphical method doesn't work, pair the device from the command " "line. Open a terminal and use +hciconfig+ to check the Bluetooth controller " "status" msgstr "" #. type: Plain text -#: ./user-manual.txt:3694 +#: user-manual.txt:3666 #, no-wrap msgid "" "\t$ hciconfig\n" @@ -7671,7 +7577,7 @@ msgid "" msgstr "" #. type: Plain text -#: ./user-manual.txt:3699 +#: user-manual.txt:3671 msgid "" "This indicates a Bluetooth controller with MAC address 01:23:45:67:89:AB, " "connected as hci0. Its status is 'DOWN', i.e. not powered. Additional " @@ -7681,7 +7587,7 @@ msgid "" msgstr "" #. type: Plain text -#: ./user-manual.txt:3707 +#: user-manual.txt:3679 #, no-wrap msgid "" "\tsudo hciconfig hci0 up auth+ (enter password when prompted)\n" @@ -7694,25 +7600,25 @@ msgid "" msgstr "" #. type: Plain text -#: ./user-manual.txt:3709 +#: user-manual.txt:3681 msgid "Check that the status now includes +'UP', 'RUNNING' AND 'AUTH'+." msgstr "" #. type: Plain text -#: ./user-manual.txt:3711 +#: user-manual.txt:3683 msgid "" "If there are multiple controllers running, it's easiest to off the unused " "controller(s). For example, for +hci1+:" msgstr "" #. type: Plain text -#: ./user-manual.txt:3713 +#: user-manual.txt:3685 #, no-wrap msgid "\tsudo hciconfig hci1 down\n" msgstr "" #. type: Plain text -#: ./user-manual.txt:3716 +#: user-manual.txt:3688 msgid "" "Next step is to 'trust' and 'pair' the dive computer. On distros with Bluez " "5, such as Fedora 22, one can use a tool called +blutootctl+, which will " @@ -7720,7 +7626,7 @@ msgid "" msgstr "" #. type: Plain text -#: ./user-manual.txt:3737 +#: user-manual.txt:3709 #, no-wrap msgid "" "\tbluetoothctl\n" @@ -7749,14 +7655,14 @@ msgid "" msgstr "" #. type: Plain text -#: ./user-manual.txt:3740 +#: user-manual.txt:3712 msgid "" "If asked for a password, enter 0000. It's ok if the last line says " "'Connected: no'. The important part is the line above, +Pairing successful+." msgstr "" #. type: Plain text -#: ./user-manual.txt:3743 +#: user-manual.txt:3715 msgid "" "If the system has Bluez version 4 (e.g. Ubuntu 12.04 through to 15.04), " "there is probably not a +bluetoothctl+, but a script called " @@ -7764,7 +7670,7 @@ msgid "" msgstr "" #. type: Plain text -#: ./user-manual.txt:3748 +#: user-manual.txt:3720 #, no-wrap msgid "" "\thcitool -i hci0 scanning\n" @@ -7774,82 +7680,82 @@ msgid "" msgstr "" #. type: Plain text -#: ./user-manual.txt:3750 +#: user-manual.txt:3722 msgid "Once ther dive computer is pired, set up the RFCOMM connection" msgstr "" #. type: Title ===== -#: ./user-manual.txt:3751 +#: user-manual.txt:3723 #, no-wrap msgid "Establishing the RFCOMM connection" msgstr "" #. type: Plain text -#: ./user-manual.txt:3754 +#: user-manual.txt:3726 msgid "The command to establish an RFCOMM connection is:" msgstr "" #. type: Plain text -#: ./user-manual.txt:3756 +#: user-manual.txt:3728 msgid "+sudo rfcomm -i <controller> connect <dev> <bdaddr> [channel]+" msgstr "" #. type: Plain text -#: ./user-manual.txt:3758 +#: user-manual.txt:3730 msgid "+<controller>+ is the Bluetooth controller, +hci0+." msgstr "" #. type: Plain text -#: ./user-manual.txt:3759 +#: user-manual.txt:3731 msgid "+<dev>+ is the RFCOMM device file, +rfcomm0+" msgstr "" #. type: Plain text -#: ./user-manual.txt:3760 +#: user-manual.txt:3732 msgid "+<bdaddr>+ is the dive computer's MAC address, +00:11:22:33:44:55+" msgstr "" #. type: Plain text -#: ./user-manual.txt:3761 +#: user-manual.txt:3733 msgid "+[channel]+ is the dive computer's Bluetooth channel we need to connect to." msgstr "" #. type: Plain text -#: ./user-manual.txt:3764 +#: user-manual.txt:3736 msgid "" "If one omits it, channel 1 is assumed. Based on a limited number of user " "reports, the appropriate channel for the dive computer is probably:" msgstr "" #. type: Plain text -#: ./user-manual.txt:3766 +#: user-manual.txt:3738 msgid "_Shearwater Petrel 1_: channel 1" msgstr "" #. type: Plain text -#: ./user-manual.txt:3767 +#: user-manual.txt:3739 msgid "_Shearwater Petrel 2_: channel 5" msgstr "" #. type: Plain text -#: ./user-manual.txt:3768 +#: user-manual.txt:3740 msgid "_Shearwater Nerd_: channel 5" msgstr "" #. type: Plain text -#: ./user-manual.txt:3769 +#: user-manual.txt:3741 msgid "_Heinrichs-Weikamp OSTC Sport_: channel 1" msgstr "" #. type: Plain text -#: ./user-manual.txt:3771 +#: user-manual.txt:3743 msgid "" "E.g. to connect a _Shearwater Petrel 2_, set the dive computer to upload " "mode and enter:" msgstr "" #. type: Plain text -#: ./user-manual.txt:3773 +#: user-manual.txt:3745 #, no-wrap msgid "" "\tsudo rfcomm -i hci0 connect rfcomm0 00:11:22:33:44:55 5 (enter a password, " @@ -7857,12 +7763,12 @@ msgid "" msgstr "" #. type: Plain text -#: ./user-manual.txt:3775 +#: user-manual.txt:3747 msgid "This gives the response:" msgstr "" #. type: Plain text -#: ./user-manual.txt:3778 +#: user-manual.txt:3750 #, no-wrap msgid "" "\tConnected /dev/rfcomm0 to 00:11:22:33:44:55 on channel 5\n" @@ -7870,14 +7776,14 @@ msgid "" msgstr "" #. type: Plain text -#: ./user-manual.txt:3780 +#: user-manual.txt:3752 msgid "" "To connect a _Shearwater Petrel 1+ or + HW OSTC Sport+, set the dive " "computer to upload mode and enter:" msgstr "" #. type: Plain text -#: ./user-manual.txt:3784 +#: user-manual.txt:3756 #, no-wrap msgid "" "\tsudo rfcomm -i hci0 connect rfcomm0 00:11:22:33:44:55 (enter a password, " @@ -7887,7 +7793,7 @@ msgid "" msgstr "" #. type: Plain text -#: ./user-manual.txt:3788 +#: user-manual.txt:3760 msgid "" "If the specific channel the dive computer needs is not known, or the channel " "in the list above doesn't work, the command +sdptool records+ should help " @@ -7896,7 +7802,7 @@ msgid "" msgstr "" #. type: Plain text -#: ./user-manual.txt:3798 +#: user-manual.txt:3770 #, no-wrap msgid "" "\tsdptool -i hci0 records 00:11:22:33:44:55\n" @@ -7911,7 +7817,7 @@ msgid "" msgstr "" #. type: Plain text -#: ./user-manual.txt:3801 +#: user-manual.txt:3773 msgid "" "For a Bluetooth dive computer not in the list above, or if the channel " "listed is not correct, please let the Subsurface developers know on the user " @@ -7919,7 +7825,7 @@ msgid "" msgstr "" #. type: Plain text -#: ./user-manual.txt:3804 +#: user-manual.txt:3776 msgid "" "After establishing the RFCOMM connection and while the dive computer's " "upload mode countdown is still running, go to_Subsurface_, select " @@ -7929,34 +7835,34 @@ msgid "" msgstr "" #. type: Title == -#: ./user-manual.txt:3810 +#: user-manual.txt:3782 #, no-wrap msgid "APPENDIX B: Dive Computer specific information for importing dive data." msgstr "" #. type: Title === -#: ./user-manual.txt:3813 +#: user-manual.txt:3785 #, no-wrap msgid "Importing from Uemis Zurich" msgstr "" #. type: Named 'icon' AttributeList argument for style 'icon' -#: ./user-manual.txt:3815 +#: user-manual.txt:3787 #, no-wrap msgid "images/icons/iumis.jpg" msgstr "" #. type: Plain text -#: ./user-manual.txt:3831 +#: user-manual.txt:3803 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 " +"you don’t 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 " @@ -7964,36 +7870,36 @@ msgid "" msgstr "" #. type: Plain text -#: ./user-manual.txt:3846 +#: user-manual.txt:3818 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 " +"(this is a Uemis firmware limitation, not a _Subsurface_ issue) is that you " "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 " +"the SDA. This will usually only happen the very first time you download " "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 " +"displays an error that the dive computer ran out of space, the solution is " +"straightforward. 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 " +"download will continue where it stopped previously. You 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:3848 +#: user-manual.txt:3820 #, no-wrap msgid "Importing from Uwatec Galileo" msgstr "" #. type: Named 'icon' AttributeList argument for style 'icon' -#: ./user-manual.txt:3850 +#: user-manual.txt:3822 #, no-wrap msgid "images/icons/Galileo.jpg" msgstr "" #. type: Plain text -#: ./user-manual.txt:3865 +#: user-manual.txt:3837 msgid "" "The Uwatec Galileo dive computers use infra red (IrDA) communication between " "the dive computer and Subsurface. The Uwatec hardware uses a USB dongle " @@ -8009,44 +7915,44 @@ msgid "" msgstr "" #. type: Plain text -#: ./user-manual.txt:3868 +#: user-manual.txt:3840 msgid "" -"After executing this command, Subsurface will recognise the Galileo dive " +"After executing this command, Subsurface will recognize the Galileo dive " "computer and download dive information." msgstr "" #. type: Plain text -#: ./user-manual.txt:3874 +#: user-manual.txt:3846 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]. " "Windows-based IrDA drivers for the Uwatec can also be downloaded from the " -"ScubaPro web site, drivers being located on the download page for the " +"ScubaPro web site, with drivers located on the download page for the " "ScubaPro SmartTrak software." msgstr "" #. type: Plain text -#: ./user-manual.txt:3877 +#: user-manual.txt:3849 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:3879 +#: user-manual.txt:3851 #, no-wrap msgid "Importing from Heinrichs Weikamp DR5" msgstr "" #. type: Named 'icon' AttributeList argument for style 'icon' -#: ./user-manual.txt:3881 +#: user-manual.txt:3853 #, no-wrap msgid "images/icons/HW_DR5.jpg" msgstr "" #. type: Plain text -#: ./user-manual.txt:3891 +#: user-manual.txt:3863 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. " @@ -8059,19 +7965,19 @@ msgid "" msgstr "" #. type: Title === -#: ./user-manual.txt:3894 +#: user-manual.txt:3866 #, no-wrap msgid "Importing from xDEEP BLACK" msgstr "" #. type: Named 'icon' AttributeList argument for style 'icon' -#: ./user-manual.txt:3896 +#: user-manual.txt:3868 #, no-wrap msgid "images/icons/HW_xdeepblack.jpg" msgstr "" #. type: Plain text -#: ./user-manual.txt:3905 +#: user-manual.txt:3877 msgid "" "Each dive has to be individually saved as UDDF file using \"Export UDDF\" " "option in BLACK's logbook menu. When mounted as a USB drive UDDF files are " @@ -8085,19 +7991,19 @@ msgid "" msgstr "" #. type: Title === -#: ./user-manual.txt:3907 +#: user-manual.txt:3879 #, no-wrap msgid "Importing from Shearwater Predator/Petrel/Nerd using Bluetooth" msgstr "" #. type: Named 'icon' AttributeList argument for style 'icon' -#: ./user-manual.txt:3909 +#: user-manual.txt:3881 #, no-wrap msgid "images/icons/predator.jpg" msgstr "" #. type: Plain text -#: ./user-manual.txt:3912 +#: user-manual.txt:3884 msgid "" "Specific instructions for downloading dives using Bluetooth are given in the " "section above, <<S_Bluetooth,_Connecting Subsurface to a Bluetooth-enabled " @@ -8105,69 +8011,69 @@ msgid "" msgstr "" #. type: Title === -#: ./user-manual.txt:3914 +#: user-manual.txt:3886 #, no-wrap msgid "Importing from Poseidon MkVI Discovery" msgstr "" #. type: Named 'icon' AttributeList argument for style 'icon' -#: ./user-manual.txt:3916 +#: user-manual.txt:3888 #, no-wrap msgid "images/MkVI.jpeg" msgstr "" #. type: Plain text -#: ./user-manual.txt:3924 +#: user-manual.txt:3896 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 " +"logs. Communication between dive computer and desktop computer utilizes the " "IrDA infra-red protocol. Only data for one dive can be downloaded at a time, " -"comprising three files:" +"in three files:" msgstr "" #. type: Plain text -#: ./user-manual.txt:3927 +#: user-manual.txt:3899 msgid "" "Setup configuration for the dive and key dive parameters (file with a .txt " "extension)" msgstr "" #. type: Plain text -#: ./user-manual.txt:3928 +#: user-manual.txt:3900 msgid "Dive log details (file with a .csv extension)" msgstr "" #. type: Plain text -#: ./user-manual.txt:3930 +#: user-manual.txt:3902 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:3932 +#: user-manual.txt:3904 msgid "" -"_Subsurface_ accesses the .txt and the .csv files to obtain dive log " +"_Subsurface_ accesses the .txt and the .csv files to get dive log " "information." msgstr "" #. type: Title === -#: ./user-manual.txt:3934 +#: user-manual.txt:3906 #, no-wrap msgid "Importing from APD Inspiration/Evolution CCR" msgstr "" #. type: Named 'icon' AttributeList argument for style 'icon' -#: ./user-manual.txt:3936 +#: user-manual.txt:3908 #, no-wrap msgid "images/APDComputer.jpg" msgstr "" #. type: Plain text -#: ./user-manual.txt:3944 +#: user-manual.txt:3916 msgid "" "The dive logs of an APD Inspiration or similar CCR dive computer are " "downloaded using a communications adapter and _AP Communicator_, obtained " @@ -8179,103 +8085,104 @@ msgid "" msgstr "" #. type: Plain text -#: ./user-manual.txt:3946 +#: user-manual.txt:3918 msgid "Download the dive using _AP Communicator_." msgstr "" #. type: Plain text -#: ./user-manual.txt:3947 +#: user-manual.txt:3919 msgid "Open a dive within the _AP Log Viewer_." msgstr "" #. type: Plain text -#: ./user-manual.txt:3948 +#: user-manual.txt:3920 msgid "Select the tab at the top of the screen, entitled \"_Data_\"." msgstr "" #. type: Plain text -#: ./user-manual.txt:3949 +#: user-manual.txt:3921 msgid "" "With the raw dive log data show on the screen, click on \"_Copy to " "Clipboard_\"." msgstr "" #. type: Plain text -#: ./user-manual.txt:3950 +#: user-manual.txt:3922 msgid "Open a text editor, e.g. Notepad (Windows) or TextWrangler (Mac)." msgstr "" #. type: Plain text -#: ./user-manual.txt:3952 +#: user-manual.txt:3924 msgid "" "Copy the contents of the clipboard into the text editor and save the text " "file with a filename extension of _.apd_" msgstr "" #. type: Plain text -#: ./user-manual.txt:3953 +#: user-manual.txt:3925 msgid "" "Within _Subsurface_, select _Import -> Import log files_ to open the " "xref:Unified_import[universal import dialogue]." msgstr "" #. type: Plain text -#: ./user-manual.txt:3954 +#: user-manual.txt:3926 msgid "" -"In the dropdown list towards the bottom right of the dialogue (labled " +"In the dropdown list towards the bottom right of the dialogue (labeled " "'Filter:'), select \"APD log viewer\"." msgstr "" #. type: Plain text -#: ./user-manual.txt:3957 +#: user-manual.txt:3930 +#, no-wrap msgid "" -"On the list of file names select the _.apd_ file that has been created " -"above. An import dialogue opens indicating the default settings for the data " -"in the _.apd_ file. If any changes are required, do this as for " -"xref:S_ImportingCSVDives[CSV imports]." +"On the list of file names select the _.apd_ file created. An import\n" +"dialogue opens showing the default settings for the data in the\n" +"_.apd_ file. If changes are required,\n" +" do this as for xref:S_ImportingCSVDives[CSV imports].\n" msgstr "" #. type: Target for macro image -#: ./user-manual.txt:3958 +#: user-manual.txt:3931 #, no-wrap msgid "images/APD_CSVimportF22.jpg" msgstr "" #. type: Plain text -#: ./user-manual.txt:3966 +#: user-manual.txt:3939 msgid "" -"The top left hand dropdown box in the import panel allows one to select the " -"APD dive computer for which the dive log needs to be imported. The default " -"it is DC1, _i.e._ the first of the two dive computers the APD uses. It is " -"possible to sequentially import the data for both dive computers by first " -"importing CD1 and then DC2.(*Hint*: The logs for the two dive computers are " -"viewed by selecting _View -> Next DC_ from the Main Menu after the uploading " -"has been completed)" +"The top left hand dropdown box in the import panel lets you select the APD " +"dive computer for which the dive log needs to be imported. The default it is " +"DC1, _i.e._ the first of the two dive computers the APD uses. It is possible " +"to sequentially import the data for both dive computers by first importing " +"CD1 and then DC2.(*Hint*: The logs for the two dive computers are viewed by " +"selecting _View -> Next DC_ from the Main Menu after the uploading has been " +"completed)" msgstr "" #. type: Plain text -#: ./user-manual.txt:3967 +#: user-manual.txt:3940 msgid "Click the _Ok_ button at the bottom of the import panel." msgstr "" #. type: Plain text -#: ./user-manual.txt:3972 +#: user-manual.txt:3945 msgid "" -"The APD dive log will appear within _Subsurface_. The dive " -"computer-generated ceiling generated by the Inspiration can be viewed by " -"selecting the appropriate button on the left of the *Dive Profile*. Cylinder " -"pressure data are not logged by the APD equipment but can be manually " -"entered in the _Equipment_ Tab." +"The APD dive log will appear within _Subsurface_. The dive computer- " +"generated ceiling provided by the Inspiration can be viewed by selecting the " +"appropriate button on the left of the *Dive Profile*. Cylinder pressure data " +"are not logged by the APD equipment but can be manually entered in the " +"_Equipment_ Tab." msgstr "" #. type: Title == -#: ./user-manual.txt:3973 +#: user-manual.txt:3946 #, no-wrap msgid "APPENDIX C: Exporting Dive log information from external dive log software." msgstr "" #. type: Plain text -#: ./user-manual.txt:3982 +#: user-manual.txt:3955 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, " @@ -8285,22 +8192,22 @@ msgid "" msgstr "" #. type: Plain text -#: ./user-manual.txt:3984 +#: user-manual.txt:3957 msgid "Export the foreign dive log data to format that is accessible from" msgstr "" #. type: Plain text -#: ./user-manual.txt:3985 +#: user-manual.txt:3958 msgid "_Subsurface_." msgstr "" #. type: Plain text -#: ./user-manual.txt:3986 +#: user-manual.txt:3959 msgid "Import the accessible dive log data into _Subsurface_." msgstr "" #. type: Plain text -#: ./user-manual.txt:3990 +#: user-manual.txt:3963 msgid "" "This appendix provides some information about approaches to export dive log " "data from foreign dive log software. The procedures below mostly apply to " @@ -8308,19 +8215,19 @@ msgid "" msgstr "" #. type: Title === -#: ./user-manual.txt:3992 +#: user-manual.txt:3965 #, no-wrap msgid "Exporting from *Suunto Divemanager (DM3, DM4 or DM5)*" msgstr "" #. type: Named 'icon' AttributeList argument for style 'icon' -#: ./user-manual.txt:3993 +#: user-manual.txt:3966 #, no-wrap msgid "images/icons/suuntologo.jpg" msgstr "" #. type: Plain text -#: ./user-manual.txt:4000 +#: user-manual.txt:3973 msgid "" "DiveManager is a MS Windows application for Suunto dive computers. " "Divemanager 3 (DM3) is an older version of the Suunto software. More recent " @@ -8330,64 +8237,64 @@ msgid "" msgstr "" #. type: Plain text -#: ./user-manual.txt:4002 +#: user-manual.txt:3975 #, no-wrap msgid "*Divemanager 3 (DM3):*\n" msgstr "" #. type: Plain text -#: ./user-manual.txt:4004 +#: user-manual.txt:3977 msgid "Start 'Suunto Divemanager 3' and log in with the name containing the logs" msgstr "" #. type: Plain text -#: ./user-manual.txt:4005 +#: user-manual.txt:3978 msgid "Do not start the import wizard to import dives from the dive computer." msgstr "" #. type: Plain text -#: ./user-manual.txt:4007 +#: user-manual.txt:3980 msgid "" "In the navigation tree on the left side of the program-window, select the " "appropriate dives." msgstr "" #. type: Plain text -#: ./user-manual.txt:4008 +#: user-manual.txt:3981 msgid "Within the list of dives, select the dives you would like to import later:" msgstr "" #. type: Plain text -#: ./user-manual.txt:4009 +#: user-manual.txt:3982 msgid "To select certain dives: hold 'ctrl' and click the dive" msgstr "" #. type: Plain text -#: ./user-manual.txt:4011 +#: user-manual.txt:3984 msgid "" "To select all dives: Select the first dive, hold down shift and select the " "last dive" msgstr "" #. type: Plain text -#: ./user-manual.txt:4012 +#: user-manual.txt:3985 msgid "With the dives marked, use the program menu _File -> Export_" msgstr "" #. type: Plain text -#: ./user-manual.txt:4013 +#: user-manual.txt:3986 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:4014 +#: user-manual.txt:3987 msgid "Click the browse button next to the field Export Path" msgstr "" #. type: Plain text -#: ./user-manual.txt:4016 +#: user-manual.txt:3989 #, no-wrap msgid "" "** A file-manager like window pops up\n" @@ -8395,13 +8302,13 @@ msgid "" msgstr "" #. type: Plain text -#: ./user-manual.txt:4017 +#: user-manual.txt:3990 #, no-wrap msgid "Divelog.SDE file\n" msgstr "" #. type: Plain text -#: ./user-manual.txt:4019 +#: user-manual.txt:3992 #, no-wrap msgid "" "** Optionally change the name of the file for saving\n" @@ -8409,108 +8316,108 @@ msgid "" msgstr "" #. type: Plain text -#: ./user-manual.txt:4020 +#: user-manual.txt:3993 #, no-wrap msgid "Back in the Export pop-up, press the button 'Export'\n" msgstr "" #. type: Plain text -#: ./user-manual.txt:4021 +#: user-manual.txt:3994 #, no-wrap msgid "The dives are now exported to the file Divelog.SDE.\n" msgstr "" #. type: Plain text -#: ./user-manual.txt:4023 +#: user-manual.txt:3996 #, no-wrap msgid "*Divemanager 4 (DM4) and Divemanager 5 (DM5):*\n" msgstr "" #. type: Plain text -#: ./user-manual.txt:4028 +#: user-manual.txt:4001 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." +"divelog from Divemanager you need to locate the DM4/DM5 database where the " +"dives are stored. You 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:4030 +#: user-manual.txt:4003 msgid "Locating the Suunto DM4 (or DM5) database:" msgstr "" #. type: Plain text -#: ./user-manual.txt:4032 ./user-manual.txt:4041 +#: user-manual.txt:4005 user-manual.txt:4014 msgid "Start Suunto DM4/DM5" msgstr "" #. type: Plain text -#: ./user-manual.txt:4033 +#: user-manual.txt:4006 msgid "Select 'Help -> About'" msgstr "" #. type: Plain text -#: ./user-manual.txt:4034 +#: user-manual.txt:4007 msgid "Click 'Copy' after text 'Copy log folder path to clipboard'" msgstr "" #. type: Plain text -#: ./user-manual.txt:4035 -msgid "Now open Windows Explorer" +#: user-manual.txt:4008 +msgid "Open Windows Explorer" msgstr "" #. type: Plain text -#: ./user-manual.txt:4036 +#: user-manual.txt:4009 msgid "Paste the address to the path box at the top of the File Explorer" msgstr "" #. type: Plain text -#: ./user-manual.txt:4037 +#: user-manual.txt:4010 msgid "The database is called DM4.db or DM5.db" msgstr "" #. type: Plain text -#: ./user-manual.txt:4039 +#: user-manual.txt:4012 msgid "Making a backup copy of the Suunto DM4/DM5 database:" msgstr "" #. type: Plain text -#: ./user-manual.txt:4042 +#: user-manual.txt:4015 msgid "Select 'File - Create backup'" msgstr "" #. type: Plain text -#: ./user-manual.txt:4044 +#: user-manual.txt:4017 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:4045 +#: user-manual.txt:4018 msgid "Click 'Save'" msgstr "" #. type: Plain text -#: ./user-manual.txt:4046 +#: user-manual.txt:4019 msgid "The dives are now exported to the file DM4.bak (or DM5.bak)" msgstr "" #. type: Title === -#: ./user-manual.txt:4048 +#: user-manual.txt:4021 #, no-wrap msgid "Exporting from Atomic Logbook" msgstr "" #. type: Named 'icon' AttributeList argument for style 'icon' -#: ./user-manual.txt:4051 +#: user-manual.txt:4024 #, no-wrap msgid "images/icons/atomiclogo.jpg" msgstr "" #. type: Plain text -#: ./user-manual.txt:4058 +#: user-manual.txt:4031 msgid "" "Atomic Logbook is a Windows software by Atomic Aquatics. It allows " "downloading of dive information from Cobalt and Cobalt 2 dive computers. " @@ -8520,178 +8427,176 @@ msgid "" msgstr "" #. type: Title === -#: ./user-manual.txt:4060 +#: user-manual.txt:4033 #, no-wrap msgid "Exporting from Mares Dive Organiser V2.1" msgstr "" #. type: Named 'icon' AttributeList argument for style 'icon' -#: ./user-manual.txt:4063 +#: user-manual.txt:4036 #, no-wrap msgid "images/icons/mareslogo.jpg" msgstr "" #. type: Plain text -#: ./user-manual.txt:4071 +#: user-manual.txt:4044 msgid "" -"Mares Dive Organiser is a Windows application. The dive log is kept as a " +"Mares Dive Organizer 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_." +"database includes all Dive Organizer-registered divers on the particular " +"computer and all Mares dive computers used. The safest way to get a copy of " +"the dive database is to export the information to another compatible format " +"which can then be imported into _Subsurface_." msgstr "" #. type: Plain text -#: ./user-manual.txt:4076 +#: user-manual.txt:4049 msgid "" -"Within Dive Organiser, select _Database -> Backup_ from the main menu and " +"Within Dive Organizer, select _Database -> Backup_ from the main menu and " "back up the database to the desk top. This creates a zipped file " -"DiveOrganiserxxxxx.dbf." +"DiveOrganizerxxxxx.dbf." msgstr "" #. type: Plain text -#: ./user-manual.txt:4079 +#: user-manual.txt:4052 msgid "" -"Rename the file to DiveOrganiserxxxxx.zip. Inside the zipped directory is a " -"file _DiveOrganiser.sdf_." +"Rename the file to DiveOrganizerxxxxx.zip. Inside the zipped directory is a " +"file _DiveOrganizer.sdf_." msgstr "" #. type: Plain text -#: ./user-manual.txt:4080 +#: user-manual.txt:4053 msgid "Extract the _.sdf_ file from the zipped folder to your Desktop." msgstr "" #. type: Plain text -#: ./user-manual.txt:4081 +#: user-manual.txt:4054 msgid "The password for accessing the .zip file is _mares_." msgstr "" #. type: Title === -#: ./user-manual.txt:4083 +#: user-manual.txt:4056 #, no-wrap msgid "Exporting from *DivingLog 5.0 and 6.0*" msgstr "" #. type: Named 'icon' AttributeList argument for style 'icon' -#: ./user-manual.txt:4085 +#: user-manual.txt:4058 #, no-wrap msgid "images/icons/divingloglogo.jpg" msgstr "" #. type: Plain text -#: ./user-manual.txt:4092 +#: user-manual.txt:4065 msgid "" "The best way to bring your logs from DivingLog to Subsurface is to convert " "the whole database. This is because other export formats do not include all " -"the details, and we would lack e.g. gas switches and information of what " -"units are used. With database import, all this information is included and " -"readily available for us." +"the details, and would lack, for example, gas switches and information of " +"what units are used. With database import, all this information is included " +"and readily available." msgstr "" #. type: Plain text -#: ./user-manual.txt:4094 -msgid "To transfer all files from DivingLog to Subsurface, do the following:" +#: user-manual.txt:4067 +msgid "To transfer all files from DivingLog to Subsurface:" msgstr "" #. type: Plain text -#: ./user-manual.txt:4096 +#: user-manual.txt:4069 msgid "In DivingLog open the 'File -> Export -> SQLite' menu" msgstr "" #. type: Plain text -#: ./user-manual.txt:4097 +#: user-manual.txt:4070 msgid "Select 'Settings' button" msgstr "" #. type: Plain text -#: ./user-manual.txt:4098 +#: user-manual.txt:4071 msgid "Set the 'RTF2Plaintext' to 'true'" msgstr "" #. type: Plain text -#: ./user-manual.txt:4099 +#: user-manual.txt:4072 msgid "Close the Settings dialog" msgstr "" #. type: Plain text -#: ./user-manual.txt:4100 +#: user-manual.txt:4073 msgid "Click 'Export' button and select the filename" msgstr "" #. type: Plain text -#: ./user-manual.txt:4104 +#: user-manual.txt:4077 msgid "" "Once this is done, open the saved database file with Subsurface and the " -"dives are automatically converted to our own format. Last step to do is save " -"the log file in Subsurface." +"dives are automatically converted to Subsurface’s own format. Last step to " +"do is save the log file in Subsurface." msgstr "" #. type: Title == -#: ./user-manual.txt:4105 +#: user-manual.txt:4078 #, no-wrap msgid "APPENDIX D: Exporting a spreadsheet to CSV format" msgstr "" #. type: Plain text -#: ./user-manual.txt:4115 +#: user-manual.txt:4088 msgid "" -"Many divers keep a diving log in some form of a digital file, commonly a " +"Many divers keep a dive log in some form of digital file, commonly a " "spreadsheet with various fields of information. These logs can be easily " "imported into _Subsurface_ 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." +"stored in a spreadsheet to a .CSV file that will later be imported to " +"_Subsurface_. Creating a .CSV is straightforward, although the procedure is " +"somewhat different according to which spreadsheet program is used." msgstr "" #. type: Plain text -#: ./user-manual.txt:4121 +#: user-manual.txt:4094 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:" +"Organize the diving data in the spreadsheet, so 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 number, Date, " +"Time, Duration, Location, GPS, Max Depth, Mean Depth, Buddy, Notes, Weight " +"and Tags). Organize dive data following a few simple rules:" msgstr "" #. type: Plain text -#: ./user-manual.txt:4123 +#: user-manual.txt:4096 msgid "Date: use one of the following formats: yyyy-mm-dd, dd.mm.yyyy, mm/dd/yyyy" msgstr "" #. type: Plain text -#: ./user-manual.txt:4124 +#: user-manual.txt:4097 msgid "Duration: the format should be minutes:seconds." msgstr "" #. type: Plain text -#: ./user-manual.txt:4125 +#: user-manual.txt:4098 msgid "" -"Unit system: only one unit system should be used (i.e., no mixture between " -"imperial and metric units)" +"Unit system: only one unit system should be used (no mix of imperial and " +"metric units)" msgstr "" #. type: Plain text -#: ./user-manual.txt:4126 +#: user-manual.txt:4099 msgid "Tags and buddies: values should be separated using a comma." msgstr "" #. type: Plain text -#: ./user-manual.txt:4127 -msgid "GPS position: users must use decimal degrees, e.g. 30.22496 30.821798" +#: user-manual.txt:4100 +msgid "GPS position: use decimal degrees, e.g. 30.22496 30.821798" msgstr "" #. type: Title === -#: ./user-manual.txt:4128 +#: user-manual.txt:4100 #, no-wrap msgid "_LibreOffice Calc_ and _OpenOffice Calc_" msgstr "" #. type: Plain text -#: ./user-manual.txt:4132 +#: user-manual.txt:4104 msgid "" "These are open source spreadsheet applications forming parts of larger open " "source office suite applications. The user interaction with _LibreOffice_ " @@ -8702,13 +8607,13 @@ msgid "" msgstr "" #. type: Target for macro image -#: ./user-manual.txt:4133 +#: user-manual.txt:4105 #, no-wrap msgid "images/LOffice_spreadsheetdata.jpg" msgstr "" #. type: Plain text -#: ./user-manual.txt:4136 +#: user-manual.txt:4108 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 " @@ -8716,13 +8621,13 @@ msgid "" msgstr "" #. type: Target for macro image -#: ./user-manual.txt:4137 +#: user-manual.txt:4109 #, no-wrap msgid "images/LOffice_save_as_options.jpg" msgstr "" #. type: Plain text -#: ./user-manual.txt:4140 +#: user-manual.txt:4112 msgid "" "After selecting _Save_, select the appropriate field delimiter (choose _Tab_ " "to prevent conflicts with the comma when using this as a decimal point), " @@ -8730,50 +8635,50 @@ msgid "" msgstr "" #. type: Target for macro image -#: ./user-manual.txt:4141 +#: user-manual.txt:4113 #, no-wrap msgid "images/LOffice_field_options.jpg" msgstr "" #. type: Plain text -#: ./user-manual.txt:4144 +#: user-manual.txt:4116 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_ImportingCSVDives[Importing CSV dives]." +"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_ImportingCSVDives[Importing " +"CSV dives]." msgstr "" #. type: Title === -#: ./user-manual.txt:4145 +#: user-manual.txt:4117 #, no-wrap msgid "Microsoft _Excel_" msgstr "" #. type: Plain text -#: ./user-manual.txt:4151 +#: user-manual.txt:4123 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 " +"software on the Windows machine uses the new character as a separator. You " "can change the character back to the default character by following the same " "procedure, outlined below." msgstr "" #. type: Plain text -#: ./user-manual.txt:4153 +#: user-manual.txt:4125 msgid "" -"In Microsoft Windows, click the *Start* button, and then select _Control " -"Panel_ from the list on the right-hand side." +"In Microsoft Windows, click the *Start* button, then select _Control Panel_ " +"from the list on the right-hand side." msgstr "" #. type: Plain text -#: ./user-manual.txt:4154 +#: user-manual.txt:4126 msgid "Open the _Regional and Language Options_ dialog box." msgstr "" #. type: Plain text -#: ./user-manual.txt:4157 +#: user-manual.txt:4129 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 " @@ -8781,190 +8686,190 @@ msgid "" msgstr "" #. type: Plain text -#: ./user-manual.txt:4158 +#: user-manual.txt:4130 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:4159 +#: user-manual.txt:4131 msgid "Click _OK_ twice." msgstr "" #. type: Plain text -#: ./user-manual.txt:4161 +#: user-manual.txt:4133 msgid "Below is an image of the _Control Panel_:" msgstr "" #. type: Target for macro image -#: ./user-manual.txt:4162 +#: user-manual.txt:4134 #, no-wrap msgid "images/Win_SaveCSV2.jpg" msgstr "" #. type: Plain text -#: ./user-manual.txt:4165 +#: user-manual.txt:4137 msgid "To export the dive log in CSV format:" msgstr "" #. type: Plain text -#: ./user-manual.txt:4167 +#: user-manual.txt:4139 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:4168 +#: user-manual.txt:4140 #, no-wrap msgid "images/Win_SaveCSV1.jpg" msgstr "" #. type: Plain text -#: ./user-manual.txt:4171 +#: user-manual.txt:4146 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." +"marked _Save as Type:_, select _CSV(Comma delimited) (*.CSV)_. Be sure the " +"appropriate folder has been selected to save the CSV file into." msgstr "" #. type: Target for macro image -#: ./user-manual.txt:4172 +#: user-manual.txt:4147 #, no-wrap msgid "images/Win_SaveCSV3.jpg" msgstr "" #. type: Plain text -#: ./user-manual.txt:4175 +#: user-manual.txt:4153 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 " +"that was selected. You can double check the .CSV file by opening it with a " +"text editor, then import the dive data as explained on the section " "xref:S_ImportingCSVDives[Importing CSV dives]." msgstr "" #. type: Title == -#: ./user-manual.txt:4177 +#: user-manual.txt:4154 #, no-wrap msgid "APPENDIX E: Writing a custom print template" msgstr "" #. type: Plain text -#: ./user-manual.txt:4182 +#: user-manual.txt:4159 msgid "" -"_Subsurface_ provides a mechanism to create or modify templates for printing " -"dive logs in order to produce customised printouts of dive logs. Templates, " -"written in HTML as well as a simple Grantlee instruction set, are rendered " -"to the print device by _Subsurface_." +"_Subsurface_ has a way to create or modify templates for printing dive logs " +"to produce customized printouts of them. Templates written in HTML, as well " +"as a simple Grantlee instruction set, are rendered to the print device by " +"_Subsurface_." msgstr "" #. type: Plain text -#: ./user-manual.txt:4184 +#: user-manual.txt:4161 msgid "Templates are accessed using the print dialogue (see image *B* below)." msgstr "" #. type: Plain text -#: ./user-manual.txt:4192 +#: user-manual.txt:4169 msgid "" -"The buttons under the _Template_ dropdown box allows one to _Edit_, " -"_Delete_, _Import_ and to _Export_ templates (see image *A* above). New or " -"modified templates are stored as HTML files in the same directory as the " -"dive log being processed. In order to create or modify a template, select " -"one of the templates from the template dropdown list in the print dialogue " -"(see image *B* above). Choose an existing template that resembles the final " -"desired printout. Then select _Edit_." +"The buttons under the _Template_ dropdown box lets you _Edit_, _Delete_, " +"_Import_ and _Export_ templates (see image *A* above). New or modified " +"templates are stored as HTML files in the same directory as the dive log " +"being processed. In order to create or modify a template, select one of the " +"templates from the template dropdown list in the print dialogue (see image " +"*B* above). Choose an existing template that resembles the final desired " +"printout. Then select _Edit_." msgstr "" #. type: Plain text -#: ./user-manual.txt:4194 -msgid "The Edit Panel comprises three tabs:" +#: user-manual.txt:4171 +msgid "The Edit Panel has three tabs:" msgstr "" #. type: Target for macro image -#: ./user-manual.txt:4195 +#: user-manual.txt:4172 #, no-wrap msgid "images/Template1_f22.jpg" msgstr "" #. type: Plain text -#: ./user-manual.txt:4199 +#: user-manual.txt:4176 msgid "" -"The _Style_ tab (image *A* above) controls the font, line spacing and colour " +"The _Style_ tab (image *A* above) controls the font, line spacing and color " "template used for printing the dive log. The style attributes are " -"editable. Choose one of the four colour palets used for colour printing." +"editable. Choose one of the four color palettes used for color printing." msgstr "" #. type: Plain text -#: ./user-manual.txt:4203 +#: user-manual.txt:4180 msgid "" -"The _Colors_ tab (image *B* above) allows editing the colours used for " -"printing the dive log. The colours are highly customisable: the _Edit_ " -"buttons in the _Colors_ tab allows choosing abritrary colours for different " +"The _Colors_ tab (image *B* above) allows editing the colors used for " +"printing the dive log. The colors are highly customizable: the _Edit_ " +"buttons in the _Colors_ tab allows choosing arbitrary colors for different " "components of the dive log printout." msgstr "" #. type: Plain text -#: ./user-manual.txt:4212 +#: user-manual.txt:4189 msgid "" "The _Template_ tab of the Edit Panel (see image below) allows creating a " "template using HTML as well as a few Grantlee programming " -"primitives. Grantlee provides the ability to create and format HTML code in " -"a highly simple but efficient way (see below). The HTML of the template can " -"be edited and saved. The saved template is stored in the same directory as " -"the dive being processed. By default, a _Custom_ template is a skeleton with " -"no specific print instructions. The informastion being printed needs to be " -"specified and formatted in the by replacing the section marked with: \"<!-- " +"primitives. Grantlee can create and format HTML code in a highly simple but " +"efficient way (see below). The HTML of the template can be edited and " +"saved. The saved template is stored in the same directory as the dive being " +"processed. By default, a _Custom_ template is a skeleton with no specific " +"print instructions. The information printed needs to be specified and " +"formatted in the template by replacing the section marked with: \"<!-- " "Template must be filled -->\". Writing HTML code with Grantlee instructions " -"allows unlimited freedom in determining what is printed an in which way it " +"allows unlimited freedom in determining what is printed and in which way it " "should be rendered." msgstr "" #. type: Target for macro image -#: ./user-manual.txt:4213 +#: user-manual.txt:4190 #, no-wrap msgid "images/Template2_f22.jpg" msgstr "" #. type: Plain text -#: ./user-manual.txt:4217 +#: user-manual.txt:4195 msgid "" -"One can adapt any of the existing templates and save it to the dive log " +"You can adapt any of the existing templates and save it to the dive log " "directory. The standard templates (e.g. One dive, Six dives, Table) can be " "modified in this way. After completing the edits, use the _Export_ button in " "the print dialogue to save the new template using a new template name." msgstr "" #. type: Plain text -#: ./user-manual.txt:4219 +#: user-manual.txt:4197 msgid "" -"To write a custom template the following elements must exist so that the " +"To write a custom template, the following elements must exist so the " "template will be correctly handled and rendered." msgstr "" #. type: Title === -#: ./user-manual.txt:4220 +#: user-manual.txt:4198 #, no-wrap msgid "Main dive loop" msgstr "" #. type: Plain text -#: ./user-manual.txt:4222 +#: user-manual.txt:4200 msgid "" -"_Subsurface_ exports a dive list called (*dives*) to the _Grantlee_ " -"backend. It is possible to iterate over the list as follows:" +"_Subsurface_ exports a dive list called (*dives*) to the _Grantlee_ back " +"end. It is possible to iterate over the list as follows:" msgstr "" #. type: Block title -#: ./user-manual.txt:4223 ./user-manual.txt:4277 ./user-manual.txt:4294 +#: user-manual.txt:4200 user-manual.txt:4265 user-manual.txt:4282 #, no-wrap msgid "template.html" msgstr "" #. type: delimited block . -#: ./user-manual.txt:4228 +#: user-manual.txt:4205 #, no-wrap msgid "" "\t{% for dive in dives %}\n" @@ -8973,13 +8878,13 @@ msgid "" msgstr "" #. type: Block title -#: ./user-manual.txt:4230 ./user-manual.txt:4282 ./user-manual.txt:4301 +#: user-manual.txt:4207 user-manual.txt:4270 user-manual.txt:4289 #, no-wrap msgid "output.html" msgstr "" #. type: delimited block . -#: ./user-manual.txt:4235 +#: user-manual.txt:4212 #, no-wrap msgid "" "\t<h1> 1 </h1>\n" @@ -8988,48 +8893,59 @@ msgid "" msgstr "" #. type: Plain text -#: ./user-manual.txt:4238 +#: user-manual.txt:4215 msgid "" -"Additional information about _Grantlee_ can be found " +"Additional information about _Grantlee_ can be found at " "http://www.grantlee.org/apidox/for_themers.html[here]" msgstr "" #. type: Title === -#: ./user-manual.txt:4239 +#: user-manual.txt:4216 #, no-wrap msgid "Grantlee exported variables" msgstr "" #. type: Plain text -#: ./user-manual.txt:4241 +#: user-manual.txt:4218 msgid "Only a subset of the dive data is exported:" msgstr "" #. type: delimited block | -#: ./user-manual.txt:4259 +#: user-manual.txt:4247 #, no-wrap msgid "" "|*Name*|*Description*\n" "|number| (*int*) dive number\n" "|id| (*int*) unique dive ID, should be used to fetch the dive profile\n" -"|date| (*string*) data of the dive\n" +"|date| (*string*) date of the dive\n" "|time| (*string*) time of the dive\n" "|location| (*string*) location of the dive\n" "|duration| (*string*) duration of the dive\n" "|depth| (*string*) depth of the dive\n" -"|divemaster| (*string*) divemaster data\n" -"|buddy| (*string*) buddy data\n" -"|airTemp| (*string*) air temperature of dive\n" -"|waterTemp| (*string*) water temperature of dive\n" +"|divemaster| (*string*) dive master for the dive\n" +"|buddy| (*string*) buddy for the dive\n" +"|airTemp| (*string*) air temperature of the dive\n" +"|waterTemp| (*string*) water temperature of the dive\n" "|notes| (*string*) dive notes\n" -"|rating| (*int*) dive rating ranges from 0 to 5\n" -"|sac| (*string*) sac value\n" -"|tags| (*string*) all dive tags concatenate together\n" -"|gas| (*string*) used gas cylinder\n" -msgstr "" - -#. type: Plain text -#: ./user-manual.txt:4263 +"|rating| (*int*) dive rating which ranges from 0 to 5\n" +"|sac| (*string*) SAC value for the dive\n" +"|tags| (*string*) list of dive tags for the dive\n" +"|gas| (*string*) list of gases used in the dive\n" +"|suit| (*string*) the suit used for the dive\n" +"|cylinders| (*string*) complete information of all used cylinders\n" +"|cylinder0-7| (*string*) information about a specific cylinder\n" +"|weights| (*string*) complete information of all used weight systems\n" +"|weight0-5| (*string*) information about a specific weight system\n" +"|maxcns| (*string*) maxCNS value for the dive\n" +"|otu| (*string*) OTU value for the dive\n" +"|sumWeight| (*string*) the summed weight of all used weight systems\n" +"|startPressure| (*string*) the start pressure\n" +"|endPressure| (*string*) the end pressure\n" +"|firstGas| (*string*) first used gas\n" +msgstr "" + +#. type: Plain text +#: user-manual.txt:4251 msgid "" "_Subsurface_ also exports *template_options* data. This data must be used as " "_CSS_ values to provide a dynamically editable template. The exported data " @@ -9037,7 +8953,7 @@ msgid "" msgstr "" #. type: delimited block | -#: ./user-manual.txt:4275 +#: user-manual.txt:4263 #, no-wrap msgid "" "|*Name*|*Description*\n" @@ -9056,26 +8972,26 @@ msgid "" msgstr "" #. type: delimited block . -#: ./user-manual.txt:4280 +#: user-manual.txt:4268 #, no-wrap msgid "\tborder-width: {{ template_options.borderwidth }}px;\n" msgstr "" #. type: delimited block . -#: ./user-manual.txt:4285 +#: user-manual.txt:4273 #, no-wrap msgid "\tborder-width: 3px;\n" msgstr "" #. type: Plain text -#: ./user-manual.txt:4288 +#: user-manual.txt:4276 msgid "" "Another variable that _Subsurface_ exports is *print_options*. This variable " "contains a single member:" msgstr "" #. type: delimited block | -#: ./user-manual.txt:4291 +#: user-manual.txt:4279 #, no-wrap msgid "" "|*Name*|*Description*\n" @@ -9084,7 +9000,7 @@ msgid "" msgstr "" #. type: delimited block . -#: ./user-manual.txt:4299 +#: user-manual.txt:4287 #, no-wrap msgid "" "\tbody {\n" @@ -9093,7 +9009,7 @@ msgid "" msgstr "" #. type: delimited block . -#: ./user-manual.txt:4306 +#: user-manual.txt:4294 #, no-wrap msgid "" "\tbody {\n" @@ -9102,103 +9018,103 @@ msgid "" msgstr "" #. type: Title === -#: ./user-manual.txt:4308 +#: user-manual.txt:4296 #, no-wrap msgid "Defined CSS selectors" msgstr "" #. type: Plain text -#: ./user-manual.txt:4312 +#: user-manual.txt:4299 msgid "" -"As the dive profile is placed after rendering, _Subsurface_ uses a special " -"_CSS_ selectors to do some searches in the HTML output. The _CSS_ selectors " -"in the following table should be added." +"As the dive profile is placed after rendering, _Subsurface_ uses special " +"_CSS_ selectors to searche in the HTML output. The _CSS_ selectors in the " +"following table should be added." msgstr "" #. type: delimited block | -#: ./user-manual.txt:4319 +#: user-manual.txt:4306 #, no-wrap msgid "" "|*Selector*|*Type*|*Description*\n" "|dive_{{ dive.id }} | id | is used to fetch the relevant dive profile\n" -"|diveProfile | class | each div that will contain a dive profile should have " -"this class selector in addition to the dive_{{ dive.id }} id selector\n" -"|dontbreak | class | prevents the div with this class to be divided into two " -"pages, this can be used\n" +"|diveProfile | class | each dive that will contain a dive profile should " +"have this class selector in addition to the dive_{{ dive.id }} id selector\n" +"|dontbreak | class | prevents the dive with this class from being divided " +"into two pages. This can be used\n" "in flow layout templates only (when data-numberofdives = 0)\n" msgstr "" #. type: Plain text -#: ./user-manual.txt:4322 +#: user-manual.txt:4309 msgid "" "Rendering dive profiles is not supported for flow layout templates (when " "data-numberofdives = 0)." msgstr "" #. type: Title === -#: ./user-manual.txt:4323 +#: user-manual.txt:4310 #, no-wrap msgid "Special attributes" msgstr "" #. type: Plain text -#: ./user-manual.txt:4327 +#: user-manual.txt:4314 msgid "" "There are two ways of rendering- either rendering a specific number of dives " -"in each page or make _Subsurface_ try to fit as much dives as possible into " +"in each page or make _Subsurface_ try to fit as many dives as possible into " "one page (_flow_ rendering)." msgstr "" #. type: Plain text -#: ./user-manual.txt:4329 +#: user-manual.txt:4316 msgid "" "The *data-numberofdives* data attribute is added to the body tag to set the " -"rendering mode" +"rendering mode." msgstr "" #. type: Plain text -#: ./user-manual.txt:4331 +#: user-manual.txt:4318 msgid "render 6 dives per page:" msgstr "" #. type: delimited block . -#: ./user-manual.txt:4334 +#: user-manual.txt:4321 #, no-wrap msgid "\t<body data-numberofdives = 6>\n" msgstr "" #. type: Plain text -#: ./user-manual.txt:4337 +#: user-manual.txt:4324 msgid "render as much dives as possible:" msgstr "" #. type: delimited block . -#: ./user-manual.txt:4340 +#: user-manual.txt:4327 #, no-wrap msgid "\t<body data-numberofdives = 0>\n" msgstr "" #. type: Plain text -#: ./user-manual.txt:4343 +#: user-manual.txt:4330 msgid "" "All CSS units should be in relative lengths only, to support printing on any " "page size." msgstr "" #. type: Title == -#: ./user-manual.txt:4344 +#: user-manual.txt:4331 #, no-wrap msgid "APPENDIX F: FAQs." msgstr "" #. type: Title === -#: ./user-manual.txt:4346 +#: user-manual.txt:4333 #, no-wrap msgid "Subsurface appears to miscalculate gas consumption and SAC" msgstr "" #. type: Plain text -#: ./user-manual.txt:4350 +#: user-manual.txt:4337 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_ " @@ -9206,17 +9122,17 @@ msgid "" msgstr "" #. type: Plain text -#: ./user-manual.txt:4356 +#: user-manual.txt:4343 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 " +"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:4362 +#: user-manual.txt:4349 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 " @@ -9226,12 +9142,12 @@ msgid "" msgstr "" #. type: Plain text -#: ./user-manual.txt:4364 +#: user-manual.txt:4351 msgid "+consumption = (amount_of_air_at_beginning - amount_of_air_at_end)+" msgstr "" #. type: Plain text -#: ./user-manual.txt:4370 +#: user-manual.txt:4357 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 " @@ -9242,12 +9158,12 @@ msgid "" msgstr "" #. type: Plain text -#: ./user-manual.txt:4372 +#: user-manual.txt:4359 msgid "+12.2*((220-100)/1.013)+" msgstr "" #. type: Plain text -#: ./user-manual.txt:4377 +#: user-manual.txt:4364 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 " @@ -9257,7 +9173,7 @@ msgid "" msgstr "" #. type: Plain text -#: ./user-manual.txt:4383 +#: user-manual.txt:4370 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 " @@ -9268,7 +9184,7 @@ msgid "" msgstr "" #. type: Title === -#: ./user-manual.txt:4384 +#: user-manual.txt:4371 #, no-wrap msgid "" "Some dive profiles have time discrepancies with the recorded samples from my " @@ -9276,7 +9192,7 @@ msgid "" msgstr "" #. type: Plain text -#: ./user-manual.txt:4388 +#: user-manual.txt:4375 msgid "" "_Subsurface_ ends up ignoring surface time for many things (average depth, " "divetime, SAC, etc). 'Question': Why do dive durations in my dive computer " @@ -9284,7 +9200,7 @@ msgid "" msgstr "" #. type: Plain text -#: ./user-manual.txt:4396 +#: user-manual.txt:4383 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 " @@ -9298,37 +9214,31 @@ msgid "" msgstr "" #. type: Title === -#: ./user-manual.txt:4397 +#: user-manual.txt:4384 #, no-wrap msgid "Some dive profiles are missing from the download" msgstr "" #. type: Plain text -#: ./user-manual.txt:4403 +#: user-manual.txt:4398 msgid "" -"'Question': I cannot download all my dives, only the most recent ones even " +"'Question': I cannot download all my dives, only the most recent ones, even " "though my dive computer's manual states that it records history of e.g. 999 " -"dives." -msgstr "" - -#. type: Plain text -#: ./user-manual.txt:4412 -msgid "" -"'Answer': Dive history is different than the dive profiles on the log. The " -"history only keeps track of the total number of dives and total amount of " -"time spent below surface. The logs, on the other hand, store the dive " -"profile, but they have limited amount of memory to do so. The exact amount " -"of dive profiles that can be stored on the device depend on sample interval " -"and duration of the dives. Once the memory is full the oldest dives get " -"overwritten with new dives. Thus we are only able to download the last 13, " -"30 or 199 dives." +"dives? 'Answer': Dive history is different than the dive profiles on the " +"log. The history only keeps track of the total number of dives and total " +"amount of time spent below surface. The logs, on the other hand, store the " +"dive profile, but they have a limited amount of memory to do so. The exact " +"amount of dive profiles that can be stored on the device depends on sample " +"interval and duration of the dives. Once the memory is full the oldest dives " +"get overwritten with new dives. Thus we are only able to download the last " +"13, 30 or 199 dives." msgstr "" #. type: Plain text -#: ./user-manual.txt:4416 +#: user-manual.txt:4402 msgid "" "If you have downloaded your dives to different dive logging software before " -"they were overwritten, there is a high chance that Subsurface can import " +"they were overwritten, there is a good chance that Subsurface can import " "these. However, if the logs are only on your dive computer, they cannot be " -"salvaged after being over written by new dives." +"salvaged after being overwritten by new dives." msgstr "" diff --git a/Documentation/fr/po/subsurface-mobile-manual.fr.po b/Documentation/fr/po/subsurface-mobile-manual.fr.po new file mode 100644 index 000000000..527a15a40 --- /dev/null +++ b/Documentation/fr/po/subsurface-mobile-manual.fr.po @@ -0,0 +1,628 @@ +# French translations for subsurface-manual package +# Copyright (C) 2016 Free Software Foundation, Inc. +# This file is distributed under the same license as the subsurface-manual package. +# +# Guillaume GARDET <guillaume.gardet@free.fr>, 2016. +msgid "" +msgstr "" +"Project-Id-Version: subsurface-manual VERSION\n" +"Report-Msgid-Bugs-To: subsurface@subsurface-divelog.org\n" +"POT-Creation-Date: 2016-03-12 13:31+0100\n" +"PO-Revision-Date: 2016-03-12 13:57+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 +#: mobile-manual.txt:14 +#, no-wrap +msgid "mobile-images/banner.jpg" +msgstr "mobile-images/banner.jpg" + +#. type: Plain text +#: mobile-manual.txt:17 +msgid "[big]#Subsurface-mobile for Android: USER MANUAL#" +msgstr "[big]#Subsurface-mobile pour Android: MANUEL UTILISATEUR#" + +#. type: Plain text +#: mobile-manual.txt:19 +#, no-wrap +msgid "*Manual author*: Willem Ferguson\n" +msgstr "" + +#. type: Plain text +#: mobile-manual.txt:21 +msgid "toc::[]" +msgstr "toc::[]" + +#. type: Plain text +#: mobile-manual.txt:23 +msgid "[blue]#_Version 1.0, March 2016_#" +msgstr "[blue]#_Version 1.0, Mars 2016_#" + +#. type: Plain text +#: mobile-manual.txt:31 +msgid "" +"Welcome as a user of _Subsurface_, advanced dive logging software with " +"extensive infrastructure to describe, organize, interpret and print scuba " +"and free dives. _Subsurface_ offers many advantages over other similar " +"software solutions, including compatibility with Windows, Mac-OS/X, Linux " +"(many distributions) and Android (iOS under development). In addition, " +"_Subsurface_ is open-source software that allows downloading dive " +"information from most dive computers." +msgstr "" + +#. type: Title - +#: mobile-manual.txt:33 +#, no-wrap +msgid "Introducing Subsurface-mobile" +msgstr "" + +#. type: Plain text +#: mobile-manual.txt:40 +msgid "" +"_Subsurface-mobile_ is an extension of _Subsurface_ on laptop and tabletop " +"computers. It runs on Android smartphone and tablet devices and is a tool " +"for viewing or sharing dive information at dive sites where a larger " +"computer is not useful. _Subsurface-mobile_ also allows the gathering of GPS " +"locations where dives are performed." +msgstr "" + +#. type: Plain text +#: mobile-manual.txt:43 +msgid "" +"A version of _Subsurface-mobile_ for iOS is under development but not yet " +"ready for testing." +msgstr "" + +#. type: Plain text +#: mobile-manual.txt:53 +msgid "" +"While _Subsurface-mobile_ allows one to enter and save dive information " +"using an Android device, users of _Subsurface-mobile_ typically use the " +"mobile app as an extension of the laptop/desktop version of _Subsurface_. " +"This allows the storage of dive logs on the Internet and which can be shared " +"by the Android version as well as the desktop version. While the desktop " +"version of _Subsurface_ shows much more detailed information for each dive, " +"the mobile version allows one to have a more accessible dive log on a dive " +"trip, useful for proving dive experience to dive shops or to review previous " +"dives." +msgstr "" + +#. type: Plain text +#: mobile-manual.txt:55 +msgid "_Subsurface-mobile_ allows one to:" +msgstr "" + +#. type: Plain text +#: mobile-manual.txt:57 +msgid "Download existing dive log information from the Internet." +msgstr "" + +#. type: Plain text +#: mobile-manual.txt:58 +msgid "View this information on an Android device." +msgstr "" + +#. type: Plain text +#: mobile-manual.txt:60 +msgid "" +"Edit many of the dive log data fields, e.g. divemaster, buddy, equipment or " +"notes about a dive." +msgstr "" + +#. type: Plain text +#: mobile-manual.txt:61 +msgid "Create and add new dive records to one's dive log." +msgstr "" + +#. type: Plain text +#: mobile-manual.txt:62 +msgid "Store the updated dive log on the Internet." +msgstr "" + +#. type: Plain text +#: mobile-manual.txt:63 +msgid "Record, store and apply GPS positions of dives." +msgstr "" + +#. type: Plain text +#: mobile-manual.txt:65 +msgid "View the localities of recorded GPS positions and of dives on a map." +msgstr "" + +#. type: Plain text +#: mobile-manual.txt:72 +msgid "" +"These items are discussed in greater detail in the following text. What " +"_Subsurface-mobile_ does not support (at this time) is downloading dive data " +"directly from a dive computer. That still has to happen with _Subsurface_ on " +"a desktop or laptop computer. We are investigating ways to support " +"downloading from a subset of the supported dive computers on Android " +"devices, but this is not yet ready for testing." +msgstr "" + +#. type: Title == +#: mobile-manual.txt:73 +#, no-wrap +msgid "Installing _Subsurface-mobile_ on an Android device" +msgstr "" + +#. type: Plain text +#: mobile-manual.txt:77 +msgid "" +"Find _Subsurface-mobile_ in the _Google Play Store_. Search for _Subsurface-" +"mobile_ and install it." +msgstr "" + +#. type: Title == +#: mobile-manual.txt:78 +#, no-wrap +msgid "Using _Subsurface-mobile_ for the first time" +msgstr "" + +#. type: Plain text +#: mobile-manual.txt:84 +msgid "" +"Upon starting _Subsurface-mobile_ for the first time, a Subsurface splash " +"screen is shown while the program loads. On some devices this may take " +"several seconds. After loading, the _Cloud Credentials screen_ appears (see " +"image below)." +msgstr "" + +#. type: Target for macro image +#: mobile-manual.txt:85 +#, no-wrap +msgid "mobile-images/landingscreen.jpg" +msgstr "" + +#. type: Plain text +#: mobile-manual.txt:93 +#, no-wrap +msgid "" +"Since _Subsurface_ is largely dependent on a dive log saved on the Internet,\n" +"provide a user-ID and password for access to the _Subsurface Cloud_. These\n" +"credentials are obtained by opening the desktop version of _Subsurface_ and\n" +"by clicking _File -> Preferences -> Network_, explained in detail in the\n" +"user manual for the _Subsurface_ desktop version. Once the account has\n" +"been created and verified using the desktop version one can use " +"_Subsurface-mobile_.\n" +msgstr "" + +#. type: Plain text +#: mobile-manual.txt:102 +msgid "" +"When entering a password, it is possible to check a checkbox that enables " +"the text of the password to be shown. Checking the check box labelled " +"\"Remember\" allows _Susburface-mobile_ to keep the credentials for " +"subsequent logins (see image above). Having entered the credentials, tap " +"the disk icon at the bottom of the screen. _Subsurface-mobile_ attempts to " +"download the existing dive log from the_Subsurface_ cloud server. " +"Appropriate messages are shown onscreen. Finally a list of dives are shown." +msgstr "" + +#. type: Title == +#: mobile-manual.txt:104 +#, no-wrap +msgid "Local copy of the dive log and synchronisation with Internet" +msgstr "" + +#. type: Plain text +#: mobile-manual.txt:114 +msgid "" +"Once the dive list has been downloaded from the Internet, _Subsurface-" +"mobile_ keeps a local copy on the mobile device. This means that, if there " +"is no Internet connection at a dive site, one can still access the local " +"copy and view and manipulate dive information. If there is Internet " +"connectivity, _Subsurface-mobile_ accesses the Internet-based dive log to " +"verify that the local copy is still the same as the Internet-stored copy. If " +"not, the local copy and the copy on the server are synchronised." +msgstr "" + +#. type: Title == +#: mobile-manual.txt:115 +#, no-wrap +msgid "A Few Remarks About The User Interface" +msgstr "" + +#. type: Plain text +#: mobile-manual.txt:124 +msgid "" +"At the bottom of many Subsurface-mobile screens is a round button that " +"provides for several actions and which allows the selection of the main " +"affirmative action (see image above and image below). On Android devices, " +"use the Android Back button for \"cancel\", \"discard\" or \"back\" actions. " +"For example, when editing dive information, tapping the action button saves " +"the changes, the Android back button can be used to cancel the edit without " +"saving changes." +msgstr "" + +#. type: Target for macro image +#: mobile-manual.txt:125 +#, no-wrap +msgid "mobile-images/actionbutton.jpg" +msgstr "" + +#. type: Plain text +#: mobile-manual.txt:132 +msgid "" +"Instead of the more traditional \"hamburger\" menu button in the top left or " +"right corner of the screen to open menus, _Subsurface-mobile_ uses a " +"different user interaction philosophy based on the Kirigami framework " +"developed by the Plasma developers. To open the main menu one has three " +"options:" +msgstr "" + +#. type: Plain text +#: mobile-manual.txt:135 +msgid "" +"Tap on the right-arrow symbol in the lower left corner of the screen (easy " +"to reach for hand held devices)" +msgstr "" + +#. type: Plain text +#: mobile-manual.txt:136 +msgid "Swipe towards the right across the left edge of the screen" +msgstr "" + +#. type: Plain text +#: mobile-manual.txt:138 +msgid "" +"Drag the action button visible on most screens with the main action to the " +"right" +msgstr "" + +#. type: Target for macro image +#: mobile-manual.txt:139 +#, no-wrap +msgid "mobile-images/menu.jpg" +msgstr "" + +#. type: Plain text +#: mobile-manual.txt:145 +msgid "" +"The images above indicate some of the important features of the menu " +"system. On the left is the main menu that is activated as described above. " +"In the middle is the menu that opens if one taps the _GPS_ option on the " +"main menu. On the right is the menu that opens if one taps the _Manage " +"Dives_ option on the main menu." +msgstr "" + +#. type: Plain text +#: mobile-manual.txt:148 +msgid "" +"Similarly, the context menu (currently only available on the dive details " +"screen) can be opened one of these three ways:" +msgstr "" + +#. type: Plain text +#: mobile-manual.txt:150 +msgid "Tap on the left-arrow symbol in the lower right corner of the screen" +msgstr "" + +#. type: Plain text +#: mobile-manual.txt:151 +msgid "Swipe to the left across the right edge of the screen" +msgstr "" + +#. type: Plain text +#: mobile-manual.txt:152 +msgid "Drag the action button to the left" +msgstr "" + +#. type: Title == +#: mobile-manual.txt:153 +#, no-wrap +msgid "Viewing the Dive List" +msgstr "" + +#. type: Plain text +#: mobile-manual.txt:161 +msgid "" +"Most of the actions of _Subsurface-mobile_ center around the dives on the " +"dive list. While the dive list is loading from the cloud, a message appears " +"at the bottom of the screen, indicating that the cloud is being accessed " +"(see image on left, below). Once the list is loaded one can scroll up and " +"down. Tapping a dive on the list brings up a display of _Details View_ for " +"that dive (see image on right below). This includes the dive profile as " +"well as additional information and notes." +msgstr "" + +#. type: Target for macro image +#: mobile-manual.txt:162 +#, no-wrap +msgid "mobile-images/divelist.jpg" +msgstr "" + +#. type: Plain text +#: mobile-manual.txt:166 +msgid "" +"One can view other dives by swiping the _Details view_ to the right (for the " +"previous dive) or to the left (following dive)." +msgstr "" + +#. type: Title == +#: mobile-manual.txt:167 +#, no-wrap +msgid "Editing dive details." +msgstr "" + +#. type: Plain text +#: mobile-manual.txt:177 +msgid "" +"At the bottom of the dive details screen the _Action Button_ contains a " +"pencil (image on right, above). Tapping the button brings up a panel with " +"edit boxes that allows one to change the existing dive information, e.g. " +"adding text to the dive notes or changing the names or values of some of the " +"information (see image below). It may be necessary to scroll the window to " +"access all the information. At the bottom of the edit screen is a _Save_ " +"action button. Tap this to save the new information. Having saved the data, " +"the dive list screen is updated and shown. To cancel any edits, tap the " +"Android Back Button." +msgstr "" + +#. type: Target for macro image +#: mobile-manual.txt:178 +#, no-wrap +msgid "mobile-images/editdive.jpg" +msgstr "" + +#. type: Title == +#: mobile-manual.txt:180 +#, no-wrap +msgid "Adding a new dive to the dive list" +msgstr "" + +#. type: Plain text +#: mobile-manual.txt:191 +msgid "" +"It is also possible to add an additional dive to the existing dive list. On " +"the main menu tap _Manage dives -> Add dive manually_. This opens a screen " +"that is identical to the editing screen discussed above. When a dive is " +"added manually, one cannot directly add a dive profile from a dive computer. " +"However, if one does not use a dive computer, the duration, depth and " +"several other bits of information about the new dive can be entered. The " +"_Action button_ at the bottom of the screen contains a disk symbol. Tap this " +"to save the new dive. To cancel any edits, tap the Android Back Button. The " +"left-hand image below shows a screenshot of a dive being created and the " +"right-hand image shows the same dive in _Details View_." +msgstr "" + +#. type: Target for macro image +#: mobile-manual.txt:192 +#, no-wrap +msgid "mobile-images/createdive.jpg" +msgstr "" + +#. type: Title == +#: mobile-manual.txt:194 +#, no-wrap +msgid "Deleting a dive" +msgstr "" + +#. type: Plain text +#: mobile-manual.txt:201 +msgid "" +"The _details view_ of a dive has a context menu on the right-hand side that " +"can be activated as described above (e.g. by tapping the arrow icon at the " +"bottom right of the screen or by dragging the _Action Button_ to the left). " +"The context menu has a single item: \"Delete dive\". If this option is " +"tapped, the dive shown in the _Details View_ is deleted. One has a brief " +"opportunity to undo the delete by tapping the _undo_ message that appears at " +"the bottom of the screen. If the _undo_ message is not tapped, the dive is " +"deleted." +msgstr "" + +#. type: Title == +#: mobile-manual.txt:202 +#, no-wrap +msgid "Dive log management" +msgstr "" + +#. type: Plain text +#: mobile-manual.txt:212 +#, no-wrap +msgid "" +"A central part of _Subsurface-mobile_ is the ability to store the dive\n" +"log using the _Subsurface_ cloud storage.\n" +"This provides security against loss or damage to the dive information " +"caintained in a local copy of\n" +"the dive log and allows the desktop version of _Subsurface_ to\n" +"access changes made using the mobile device. This ability is accessed\n" +"throug the main menu (by dragging the Action Button to the right, or\n" +"alternatively tap the right angle button at the bottom left of the screen).\n" +" Tap the option _Manage dives_, enabling a number of options:\n" +msgstr "" + +#. type: Title === +#: mobile-manual.txt:213 +#, no-wrap +msgid "Add new dive manually" +msgstr "" + +#. type: Plain text +#: mobile-manual.txt:216 +msgid "This is described above under the section dealing with the dive list." +msgstr "" + +#. type: Title === +#: mobile-manual.txt:217 +#, no-wrap +msgid "Upload dive log to the _Subsurface_ cloud storage" +msgstr "" + +#. type: Plain text +#: mobile-manual.txt:223 +msgid "" +"One can upload the dives contained on the mobile device to the _Subsurface_ " +"cloud storage by tapping the option _Upload to cloud_. This synchronizes " +"the local changes to the dive log with the cloud storage." +msgstr "" + +#. type: Title === +#: mobile-manual.txt:224 +#, no-wrap +msgid "Download dive log from the cloud storage" +msgstr "" + +#. type: Plain text +#: mobile-manual.txt:229 +msgid "" +"In the dive management subpanel, tap the option _Refresh_, causing the local " +"divelog to be refreshed from the cloud so that the cloud and local versions " +"are synchronised." +msgstr "" + +#. type: Title === +#: mobile-manual.txt:230 +#, no-wrap +msgid "Changing the login credentials on the _Subsurface_ cloud" +msgstr "" + +#. type: Plain text +#: mobile-manual.txt:236 +msgid "" +"It may be necessary to change one's login credentials, for instance if one's " +"email address (initially used as a credential) has changed. To change the " +"credentials, open the main menu and tap _Cloud credentials_. This opens the " +"setup screen for specifying new credentials." +msgstr "" + +#. type: Title == +#: mobile-manual.txt:238 +#, no-wrap +msgid "Recording dive locations using GPS." +msgstr "" + +#. type: Plain text +#: mobile-manual.txt:244 +msgid "" +"The fact that most smartphones have GPS facilities allows one to record the " +"locations of dives. One can take the smartphone on the dive boat during a " +"dive and locations will be automatically recorded at regular intervals. " +"These locations can then be applied to dives in the dive list. Here is how " +"it's done:" +msgstr "" + +#. type: Title === +#: mobile-manual.txt:245 +#, no-wrap +msgid "Setting up the GPS" +msgstr "" + +#. type: Plain text +#: mobile-manual.txt:253 +msgid "" +"Open the main menu and tap _GPS -> Preferences_. Now specify the way in " +"which GPS data need to be automatically collected (image on right, below). " +"One can specify that data are collected at regular intervals, e.g. every 10 " +"minutes, or at regular distances, e.g. after the boat has moved more than " +"200m, or a combination of both of the above approaches. Provide the " +"appropriate information and tap the _Save_ action button. The program is now " +"ready to collect GPS positions." +msgstr "" + +#. type: Target for macro image +#: mobile-manual.txt:254 +#, no-wrap +msgid "mobile-images/gpssetup.jpg" +msgstr "" + +#. type: Title === +#: mobile-manual.txt:256 +#, no-wrap +msgid "Collecting GPS positions" +msgstr "" + +#. type: Plain text +#: mobile-manual.txt:265 +msgid "" +"Ensure that the GPS on the Android device has been activated. At the bottom " +"of the GPS submenu is a check box _Run location service_ (image on left, " +"above). Check this box and _Subsurface-mobile_ starts to collect GPS " +"locations automatically, following the preferences specified as described " +"above. After the dive one can deactivate the collection of GPS data by de-" +"activating the same check box at the bottom of the main menu." +msgstr "" + +#. type: Title === +#: mobile-manual.txt:266 +#, no-wrap +msgid "Storing the GPS data on the _Subsurface_ cloud" +msgstr "" + +#. type: Plain text +#: mobile-manual.txt:273 +msgid "" +"Activate the main menu and select the _GPS_ option that brings up the " +"submenu of GPS-related actions (image on left, above). Tap _Upload GPS data_ " +"that saves the GPS data on the _Subsurface_ cloud server. These GPS data are " +"saved *separately* from the other dive log data. All collected GPS data are " +"kept on the Android device, independent of whether they have been uploaded " +"or not." +msgstr "" + +#. type: Title === +#: mobile-manual.txt:274 +#, no-wrap +msgid "Downloading GPS data from the _Subsurface_ cloud" +msgstr "" + +#. type: Plain text +#: mobile-manual.txt:278 +msgid "" +"Download the GPS data that have been saved on the cloud by selecting " +"_Download GPS Data_ from the GPS subpanel." +msgstr "" + +#. type: Title === +#: mobile-manual.txt:279 +#, no-wrap +msgid "Viewing GPS data" +msgstr "" + +#. type: Plain text +#: mobile-manual.txt:290 +msgid "" +"From the GPS submenu (image on left, above) select _Show GPS fixes_. This " +"brings up a list of GPS positions obtained using the location service (image " +"on left, below). Two actions are possible for each of the locations, enabled " +"if one taps the handle (the three horisontal stripes on the right, see image " +"on left, below) and then drags the specific item to the left (image on " +"right, below). This exposes two options. Tapping the dustbin deletes this " +"particular GPS location. Tapping the teardrop-shaped icon (actually a Google " +"Maps pin) opens up Google Maps with a pin indicating the exact map position " +"of the GPS record being viewed. The two above options can be hidden by " +"drawing the GPS record to the right, again using the handle." +msgstr "" + +#. type: Target for macro image +#: mobile-manual.txt:291 +#, no-wrap +msgid "mobile-images/gpsmanagement.jpg" +msgstr "" + +#. type: Title === +#: mobile-manual.txt:293 +#, no-wrap +msgid "Applying GPS data to dives in the dive log" +msgstr "" + +#. type: Plain text +#: mobile-manual.txt:301 +msgid "" +"Assuming that all the dives have been entered into the dive log or have been " +"downloaded from the _Subsurface_ cloud, one can apply the GPS positions to " +"these dives. GPS positions can therefore only be applied to dives in the " +"dive list. From the GPS subpanel, tap _Apply GPS fixes_. The dive list " +"contains the start and end times of each dive. Now, _Subsurface-mobile_ " +"applies the first GPS position that falls within the dive period of each " +"dive. This results in a GPS position for each dive that is saved as part of " +"the dive list." +msgstr "" diff --git a/Documentation/fr/po/subsurface-manual.fr.po b/Documentation/fr/po/subsurface-user-manual.fr.po index 8eb0409a2..19365e01c 100644 --- a/Documentation/fr/po/subsurface-manual.fr.po +++ b/Documentation/fr/po/subsurface-user-manual.fr.po @@ -2,13 +2,13 @@ # 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. +# Guillaume GARDET <guillaume.gardet@free.fr>, 2015, 2016. msgid "" msgstr "" "Project-Id-Version: \n" "Report-Msgid-Bugs-To: subsurface@subsurface-divelog.org\n" -"POT-Creation-Date: 2015-10-29 10:38+0100\n" -"PO-Revision-Date: 2015-10-29 10:38+0100\n" +"POT-Creation-Date: 2016-03-12 13:31+0100\n" +"PO-Revision-Date: 2016-03-12 13:55+0100\n" "Last-Translator: Guillaume GARDET <guillaume.gardet@opensuse.org>\n" "Language-Team: French <opensuse-fr@opensuse.org>\n" "Language: fr\n" @@ -49,7 +49,7 @@ msgstr "[blue]#_Version 4.5, Octobre 2015_#" #: 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 " +"extensive infrastructure to describe, organize, interpret and print scuba " "and free dives. _Subsurface_ offers many advantages over other similar " "software solutions:" msgstr "" @@ -63,7 +63,7 @@ msgstr "" #: user-manual.txt:31 msgid "" "Do you need a flexible way of logging dives using recreational equipment, " -"even not using a dive computer?" +"even without a dive computer?" msgstr "" "Avez-vous besoin d'une façon d'enregistrer vos plongées utilisant des " "équipements loisirs, même sans utiliser d'ordinateur de plongée ?" @@ -74,9 +74,9 @@ 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." +"depth recorder along with a dive computer? _Subsurface_ offers a standard " +"interface for downloading dive logs from all of these different pieces of " +"equipment, storing and analyzing the dive logs within a unified system." msgstr "" "Utilisez-vous deux marques différentes d'ordinateurs de plongée, chacun avec " "son propre logiciel propriétaire pour télécharger les enregistrements des " @@ -84,15 +84,15 @@ msgstr "" "ou de loisir ? Utilisez-vous un enregistreur de profondeur et de durée " "Reefnet Sensus avec un ordinateur de plongée ? _Subsurface_ offre une " "interface standard pour télécharger les enregistrements des plongées à " -"partir de tous ces équipements de plongée et pour enregistrer et analyser " +"partir de tous ces équipements de plongée, en enregistrant et en analysant " "ces enregistrements dans un système unique." #. 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." +"with Mac, Linux and Windows, letting you access your dive log on each " +"operating system using a single application." msgstr "" "Utilisez-vous plus d'un système d'exploitation ? _Subsurface_ est " "intégralement compatible avec Mac, Linux et Windows, ce qui vous permet " @@ -102,12 +102,12 @@ msgstr "" #. type: Plain text #: user-manual.txt:43 msgid "" -"Do you use Linux or Mac and your dive computer has only Windows-based " +"Do you use Linux or Mac, but 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 " +"provides a way of downloading and analyzing your dive logs on other " "operating systems." msgstr "" -"Utilisez-vous Linux ou Mac et votre ordinateur de plongée n'a que des " +"Utilisez-vous Linux ou Mac mais votre ordinateur de plongée n'a que des " "logiciels pour Windows pour télécharger les informations de plongées (par " "exemple Mares) ? _Subsurface_ fournit un moyen de télécharger et d'analyser " "vos enregistrements de plongées sur d'autres systèmes d'exploitation." @@ -115,47 +115,42 @@ 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?" +"Do you need an intuitive graphical dive planner that integrates with, and " +"takes into account, dives you’ve already logged?" msgstr "" "Avez-vous besoin d'un planificateur de plongée graphique intuitif qui " "intègre et prend en compte les plongées qui ont déjà été enregistrées ?" #. type: Plain text -#: user-manual.txt:47 +#: user-manual.txt:51 msgid "" "Do you need a way of storing or backing up your dive log on the Internet, " -"allowing you to view your dive log from anywhere, using an Internet browser?" -msgstr "" -"Avez-vous besoin d'un moyen d'enregistrer ou de sauvegarder votre carnet de " -"plongée sur Internet, Vous permettant de visualiser votre carnet depuis " -"n'importe où, en utilisant un navigateur Internet ?" - -#. type: Plain text -#: user-manual.txt:52 -msgid "" +"letting you view your dive log from anywhere using an Internet browser? " "_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 "" -"_Subsurface_ est disponible pour Windows (Win XP ou plus récent), les Macs " -"basés sur processeurs Intel (OS/X) et de nombreuses distributions Linux. " -"_Subsurface_ peut être compilé pour bien plus de plateformes matérielles et " -"d'environnements logiciels où Qt et libdivecomputer sont disponibles." +"Avez-vous besoin d'un moyen d'nregistrer et de sauvegarder vos plongées sur " +"Internet, vous permettant de les voir depuis n'importe où en utilisant un " +"navigateur Internet ? _Subsurface_ est disponible pour Windows (Win XP ou " +"plus récent), les Macs basés sur processeurs Intel (OS/X) et de nombreuses " +"distributions Linux. _Subsurface_ peut être compilé pour bien plus de " +"plateformes matérielles et d'environnements logiciels où Qt et " +"libdivecomputer sont disponibles." #. type: Plain text -#: user-manual.txt:61 +#: user-manual.txt:60 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." +"This manual explains how to use 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 "" -"Le but de ce document est l'utilisation du programme Subsurface. Pour " +"Ce manuel explique comment utiliser le programme _Subsurface_. Pour " "installer le logiciel, consultez la page _Téléchargement_ sur le http://" "subsurface-divelog.org/[site web de _Subsurface_]. En cas de problème, vous " "pouvez envoyer un e-mail sur mailto:subsurface@subsurface-divelog.org[notre " @@ -165,7 +160,7 @@ msgstr "" "dans les sources logicielles." #. type: Plain text -#: user-manual.txt:64 +#: user-manual.txt:63 #, no-wrap msgid "" "*Audience*: Recreational Scuba Divers, Free Divers, Tec Divers, Professional\n" @@ -175,18 +170,18 @@ msgstr "" "professionnels\n" #. type: Plain text -#: user-manual.txt:66 +#: user-manual.txt:65 msgid "toc::[]" msgstr "toc::[]" #. type: Title - -#: user-manual.txt:69 +#: user-manual.txt:68 #, no-wrap msgid "Using this manual" msgstr "Utilisation de ce manuel" #. type: Plain text -#: user-manual.txt:72 +#: user-manual.txt:71 msgid "" "When opened from within _Subsurface_, this manual does not have external " "controls for paging or selecting previous pages. However, two facilities are " @@ -194,59 +189,69 @@ msgid "" msgstr "" #. type: Plain text -#: user-manual.txt:79 +#: user-manual.txt:78 msgid "" "The _SEARCH_ function is activated by pressing control-F or command-F on the " "keyboard. A text box appears at the bottom right-hand of the window (see " -"image below). For instance, if one typed the word \"_weights_\" into the " -"search text box, this word will be searched for throughout this user manual. " -"To the right of the search text box are two arrows pointing upwards and " -"downwards. Selecting these allow finding, respectively, the previous and the " -"next occurence of the term being searched for." +"image below). For instance, typing the word \"_weights_\" into the search " +"text box, searches throughout the user manual. To the right of the search " +"text box are two arrows pointing up and down. These find the previous and " +"the next occurrence of the search term." msgstr "" #. type: Target for macro image -#: user-manual.txt:80 +#: user-manual.txt:78 #, no-wrap msgid "images/usermanualfunctions.jpg" msgstr "images/usermanualfunctions.jpg" #. type: Plain text -#: user-manual.txt:91 +#: user-manual.txt:90 msgid "" -"_PREVIOUS/NEXT LINK_. One can move between links (underlined words allowing " -"one to jump to specific sections in this user manual) by right-clicking on " -"the text of the manual. This brings up a context menu for jumping to " -"previous links selected while reading the manual (see image above). For " -"instance if a link in the manual has been selected, then the option to _Go " -"Back_ shows the text at the last link that was selected (similar to the " -"Previous Page button in a browser). Conversely the _Go Forward_ option " -"enables jumping to the text perused before selecting the _Go Back_ option. " -"The _Reload_ option causes the complete user manual to be reloaded into the " -"user manual window." +"_PREVIOUS/NEXT LINK_. Move between links (underlined words that jump to " +"specific sections in the user manual) by right-clicking on the text of the " +"manual. This brings up a context menu to previous links selected. (see " +"image above). For instance if a link has been selected, then the option to " +"_Go Back_ shows the text at the last link selected (similar to the Previous " +"Page button in a browser). Conversely the _Go Forward_ option jumps to the " +"text seen before selecting the _Go Back_ option. The _Reload_ option reloads " +"the complete user manual into the window." msgstr "" #. type: Title - -#: user-manual.txt:94 +#: user-manual.txt:92 #, no-wrap msgid "The user survey" msgstr "Le sondage utilisateur" #. type: Plain text -#: user-manual.txt:106 -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." +#: user-manual.txt:103 +#, fuzzy +#| 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." +msgid "" +"In order to develop _Subsurface_ to serve its users in the best possible " +"way, it’s important to have user information. Upon launching _Subsurface_ " +"and using the 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. All data the user sends is useful, and " +"will only be used to steer future development and to customize the software " +"to fit the needs of the _Subsurface_ users. If you complete the survey, or " +"click the option not to be asked again, that should be the last " +"communication of this type you receive. However, if your diving and/or " +"subsurface habits change and you wish to fill in another survey, just launch " +"_Subsurface_ with the _--survey_ option on the command line." msgstr "" "Dans le but de développer _Subsurface_ d'une manière qui serve ses " "utilisateurs de la meilleur manière qu'il soit, il est important d'avoir des " @@ -265,13 +270,13 @@ msgstr "" "ligne de commande." #. type: Title - -#: user-manual.txt:109 +#: user-manual.txt:106 #, no-wrap msgid "Start Using the Program" msgstr "Commencer à utiliser le programme" #. type: Plain text -#: user-manual.txt:114 +#: user-manual.txt:111 msgid "" "The _Subsurface_ window is usually divided into four panels with a *Main " "Menu* (File Import Log View Help) at the top of the window (for Windows and " @@ -284,13 +289,19 @@ msgstr "" "quatre panneaux sont :" #. type: Plain text -#: user-manual.txt:120 +#: user-manual.txt:117 +#, fuzzy +#| 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." 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." +"The *Dive List* on the bottom left, showing 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 "" "La *liste des plongées* en bas à gauche, contenant une liste de toutes les " "plongées du journal (carnet) de plongées de l'utilisateur. Une plongée peut " @@ -300,19 +311,29 @@ msgstr "" "important pour manipuler un journal (carnet) de plongée." #. type: Plain text -#: user-manual.txt:124 +#: user-manual.txt:120 +#, fuzzy +#| 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*." 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*." +"The *Dive Map* on the bottom right, showing the user's dive sites on a world " +"map and centered on the site of the last dive selected in the *Dive List*." msgstr "" "La *carte de plongée* en bas à droite, affiche les sites de plongées de " "l'utilisateur, sur une carte mondiale et centrée sur le site de la dernière " "plongée sélectionnée dans la *liste des plongées*." #. type: Plain text -#: user-manual.txt:128 +#: user-manual.txt:124 +#, fuzzy +#| msgid "" +#| "The *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)." msgid "" -"The *Info* to the top left, giving more detailed information on the dive " +"The *Info* on 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 "" @@ -322,21 +343,31 @@ msgstr "" "en surbrillance." #. type: Plain text -#: user-manual.txt:131 +#: user-manual.txt:127 +#, fuzzy +#| msgid "" +#| "The *Dive Profile* to the top right, showing a graphical dive profile of " +#| "the selected dive in the *Dive List*." msgid "" -"The *Dive Profile* to the top right, showing a graphical dive profile of the " +"The *Dive Profile* on the top right, showing a graphical dive profile of the " "selected dive in the *Dive List*." msgstr "" "Le *profil de plongée* en haut à droite, affiche un profil de plongée " "graphique de la plongée sélectionnée dans la *liste des plongées*." #. type: Plain text -#: user-manual.txt:136 -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." +#: user-manual.txt:131 +#, fuzzy +#| 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." +msgid "" +"The dividers between panels can be dragged 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 the last " +"time the program was used." msgstr "" "Les séparateurs entre ces panneaux peuvent être déplacés pour modifier la " "taille de chaque panneau. _Subsurface_ mémorise la position de ces " @@ -344,15 +375,24 @@ msgstr "" "positions." #. type: Plain text -#: user-manual.txt:144 +#: user-manual.txt:139 +#, fuzzy +#| msgid "" +#| "If a single 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 several dives are selected, the " +#| "last highlighted dive is the _selected dive_, but summary data of all " +#| "_highlighted dives_ are shown in the *Stats* tab of the *Info* panel " +#| "(maximum, minimum and average depths, durations, water temperatures and " +#| "SAC; total time and number of dives selected)." msgid "" "If a single 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 several dives are selected, the last " -"highlighted dive is the _selected dive_, but summary data of all " -"_highlighted dives_ are shown in the *Stats* tab of the *Info* panel " -"(maximum, minimum and average depths, durations, water temperatures and SAC; " -"total time and number of dives selected)." +"panels. If several dives are selected, the last highlighted dive is the " +"_selected dive_, but summary data of all _highlighted dives_ is shown in the " +"*Stats* tab of the *Info* panel (maximum, minimum and average depths, " +"durations, water temperatures and SAC; total time and number of dives " +"selected)." msgstr "" "Si une unique plongée est sélectionnée dans la *liste des plongées*, " "l'emplacement de la plongée, les informations détaillées et le profil de la " @@ -365,42 +405,46 @@ msgstr "" "nombre de plongées sélectionnées)." #. type: Target for macro image -#: user-manual.txt:147 +#: user-manual.txt:142 #, no-wrap msgid "images/main_window_f22.jpg" msgstr "images/main_window_f22.jpg" #. type: Plain text -#: user-manual.txt:152 +#: user-manual.txt:146 +#, fuzzy +#| 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:" 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:" +"The user decides which of the four panels are displayed by selecting the " +"*View* option on the main menu. This feature has several choices of display:" msgstr "" "L'utilisateur peut déterminer si lesquels des quatre panneaux sont affichés " "en sélectionnant l'option *Vue* dans le menu principal. Cette fonctionnalité " "permet plusieurs choix d'affichage :" #. type: Plain text -#: user-manual.txt:154 +#: user-manual.txt:148 #, no-wrap msgid "*All*: show all four of the panels as in the screenshot above.\n" msgstr "*Tout* : affiche les quatre panneaux tels que sur la capture d'écran ci-dessus.\n" #. type: Plain text -#: user-manual.txt:156 +#: user-manual.txt:150 #, no-wrap msgid "*Divelist*: Show only the Dive List.\n" msgstr "*Liste des plongées* : affiche uniquement la liste des plongées.\n" #. type: Plain text -#: user-manual.txt:158 +#: user-manual.txt:152 #, no-wrap msgid "*Profile*: Show only the Dive Profile of the selected dive.\n" msgstr "*Profil* : affiche uniquement le profile de plongée de la plongée sélectionnée.\n" #. type: Plain text -#: user-manual.txt:161 +#: user-manual.txt:155 #, no-wrap msgid "" "*Info*: Show only the Notes about the last selected dive and statistics for\n" @@ -410,19 +454,28 @@ msgstr "" "toutes les plongées mises en surbrillance.\n" #. type: Plain text -#: user-manual.txt:163 -#, no-wrap -msgid "*Globe*: Show only the world map, centred on the last selected dive.\n" +#: user-manual.txt:157 +#, fuzzy, no-wrap +#| msgid "*Globe*: Show only the world map, centred on the last selected dive.\n" +msgid "*Globe*: Show only the world map, centered on the last selected dive.\n" msgstr "*Globe* : affiche uniquement la carte mondiale, centrée sur la dernière plongée sélectionnée.\n" #. type: Plain text -#: user-manual.txt:169 -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 " +#: user-manual.txt:163 +#, fuzzy +#| 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." +msgid "" +"Like other functions that can be accessed via the Main Menu, these options " +"can also 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 " +"Since different Operating Systems and the user’s chosen language may cause " +"_Subsurface_ to use different shortcut keys, they are not listed in this " "user manual." msgstr "" "Comme la plupart des autre fonctions qui peuvent être accédée via le menu " @@ -433,12 +486,17 @@ msgstr "" "raccourcis et ne sont donc pas détaillées ici." #. type: Plain text -#: user-manual.txt:173 +#: user-manual.txt:167 +#, fuzzy +#| 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." 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." +"all, because it does not have any dive information available. In the " +"following sections, the procedures to create a new logbook will be explained." msgstr "" "Lorsque le programme est lancé pour la première fois, il n'affiche aucune " "information. Ceci parce que le programme n'a aucune information de plongée " @@ -446,17 +504,23 @@ msgstr "" "carnet de plongée sera détaillée." #. type: Title - -#: user-manual.txt:176 +#: user-manual.txt:170 #, no-wrap msgid "Creating a new logbook" msgstr "Créer un nouveau carnet de plongée" #. type: Plain text -#: user-manual.txt:181 +#: user-manual.txt:175 +#, fuzzy +#| 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." 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 " +"cleared so 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 "" "Sélectionner _Fichier -> Nouveau carnet de plongée_ à partir du menu " @@ -466,31 +530,35 @@ msgstr "" "faut les enregistrer ou non avant de créer le nouveau carnet." #. type: Title == -#: user-manual.txt:183 +#: user-manual.txt:177 #, no-wrap msgid "Storing dive information in the logbook" msgstr "Enregistrement des informations de plongée dans le carnet" #. type: Plain text -#: user-manual.txt:188 +#: user-manual.txt:180 +#, fuzzy +#| 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." 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." +"Now that a new logbook is created, it is simple to add dive data it. " +"_Subsurface_ allows several ways of adding dive data to a logbook." msgstr "" "Maintenant qu'un nouveau carnet de plongée a été créé, il est simple de lui " "ajouter des données. _Subsurface_ permet plusieurs façons pour ajouter des " "données de plongée au carnet. Plus de détails dans les sections suivantes." #. type: Plain text -#: user-manual.txt:190 +#: user-manual.txt:181 msgid "If the user has a handwritten divelog, a spreadsheet or another form of" msgstr "" "Si l'utilisateur possède un carnet manuscrit, un tableur ou une autre forme " "de " #. type: Plain text -#: user-manual.txt:192 +#: user-manual.txt:183 msgid "" "manually maintained divelog, dive data can be added to the logbook using one " "of these approaches:" @@ -499,14 +567,16 @@ msgstr "" "au carnet en utilisant une des approches suivantes :" #. type: Plain text -#: user-manual.txt:194 -msgid "Enter dive information by hand. This is useful if the diver did not" +#: user-manual.txt:184 +#, fuzzy +#| msgid "Enter dive information by hand. This is useful if the diver did not" +msgid "Enter dive information by hand. This is useful if the diver didn’t" msgstr "" "Entrer les informations de plongée à la main. Cela est utile si le plongeur " "n'a pas" #. type: Plain text -#: user-manual.txt:196 +#: user-manual.txt:186 msgid "" "use a dive computer and dives were recorded in a written logbook. See: xref:" "S_EnterData[Entering dive information by hand]" @@ -516,7 +586,7 @@ msgstr "" "à la main]" #. type: Plain text -#: user-manual.txt:198 +#: user-manual.txt:188 msgid "" "Import dive log information that has been maintained either as a spreadsheet" msgstr "" @@ -524,7 +594,7 @@ msgstr "" "tableur" #. type: Plain text -#: user-manual.txt:200 +#: user-manual.txt:190 msgid "" "or as a CSV file. Refer to: xref:S_Appendix_D[APPENDIX D: Exporting a " "spreadsheet to CSV format] and to xref:S_ImportingCSVDives[Importing dives " @@ -535,24 +605,21 @@ msgstr "" "S_ImportingCSVDives[Importer des plongées au format CSV]." #. type: Plain text -#: user-manual.txt:202 -msgid "" -"If one has dives recorded using a dive computer, the depth profile of the" -msgstr "" -"Si les plongées ont été enregistrées en utilisant un ordinateur de plongée, " -"le profil de profondeur de la" - -#. type: Plain text -#: user-manual.txt:204 +#: user-manual.txt:193 +#, fuzzy +#| msgid "" +#| "dive and a large amount of additional information can be accessed. These " +#| "dives can be imported from:" msgid "" -"dive and a large amount of additional information can be accessed. These " -"dives can be imported from:" +"If a dive is recorded using a dive computer, the depth profile and a large " +"amount of additional information can be accessed. These dives can be " +"imported from:" msgstr "" "plongée et de nombreuses informations supplémentaires peuvent être " "utilisées. Ces plongées peuvent être importées à partir de :" #. type: Plain text -#: user-manual.txt:206 +#: user-manual.txt:194 msgid "" "The dive computer itself. See: xref:S_ImportDiveComputer[Importing new dive " "information from a Dive Computer] or" @@ -561,7 +628,7 @@ msgstr "" "de nouvelles informations de plongée à partir de l'ordinateur de plongée] ou" #. type: Plain text -#: user-manual.txt:208 +#: user-manual.txt:196 msgid "" "Proprietary software distributed by manufacturers of dive computers. Refer" msgstr "" @@ -569,7 +636,7 @@ msgstr "" "Voir" #. type: Plain text -#: user-manual.txt:209 +#: user-manual.txt:197 msgid "" "to: xref:S_ImportingAlienDiveLogs[Importing dive information from other " "digital data sources or other data formats]." @@ -578,14 +645,16 @@ msgstr "" "sources de données numériques ou d'autres formats de données]." #. type: Plain text -#: user-manual.txt:211 -msgid "Import from spreadsheet or CSV files containing dive profiles." +#: user-manual.txt:198 +#, fuzzy +#| msgid "Import from spreadsheet or CSV files containing dive profiles." +msgid "Spreadsheet or CSV files containing dive profiles." msgstr "" "Importer à partir d'un tableur ou de fichiers CSV contenant les profils de " "plongées." #. type: Plain text -#: user-manual.txt:212 +#: user-manual.txt:199 msgid "" "See: xref:S_ImportingCSVDives[Importing dives in CSV format from dive " "computers or other dive log software]" @@ -594,251 +663,249 @@ msgstr "" "des ordinateurs de plongées ou d'autres logiciels de carnet de plongée]" #. type: Title === -#: user-manual.txt:215 +#: user-manual.txt:202 #, no-wrap msgid "Entering dive information by hand" msgstr "Entrer les informations de plongée à la main" #. type: Plain text -#: user-manual.txt:229 +#: user-manual.txt:217 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 " +"duration, depth, the names of your dive buddy and 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 *Info* panel " -"(*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." +"information for each dive. To add a dive to a dive log, select _Log -> Add " +"Dive_ from the Main Menu. The program then shows three panels on which to " +"enter information for a dive: two tabs in the *Info* panel (*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:230 +#: user-manual.txt:218 #, no-wrap msgid "images/AddDive1_f22.jpg" msgstr "images/AddDive1_f22.jpg" #. type: Plain text -#: user-manual.txt:235 +#: user-manual.txt:222 msgid "" -"When one edits a field in Notes or Equipment panels, _Subsurface_ enters " +"When you edit a field in Notes or Equipment panels, _Subsurface_ enters " "*Editing Mode*, indicated by the message in the blue box at the top of the " "*Notes* panel (see the image below). This message is displayed in all the " "panels under Notes and Equipment when in *Editing Mode*." msgstr "" #. type: Target for macro image -#: user-manual.txt:236 user-manual.txt:807 +#: user-manual.txt:223 user-manual.txt:782 #, no-wrap msgid "images/BlueEditBar_f22.jpg" msgstr "images/BlueEditBar_f22.jpg" #. type: Plain text -#: user-manual.txt:243 +#: user-manual.txt:231 msgid "" "The _Apply changes_ 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 _Apply changes_ 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." +"information for this specific dive is saved in memory. The _Apply changes_ " +"button should ONLY be selected after all parts of a dive have been entered. " +"When you close 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:245 +#: user-manual.txt:233 #, no-wrap msgid "Creating a Dive Profile" msgstr "" #. type: Plain text -#: user-manual.txt:252 +#: user-manual.txt:240 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 " +"function of time) is shown 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:" +"best represent the dive described:" msgstr "" #. type: Target for macro image -#: user-manual.txt:253 +#: user-manual.txt:241 #, no-wrap msgid "images/DiveProfile1_f20.jpg" msgstr "images/DiveProfile1_f20.jpg" #. type: Plain text -#: user-manual.txt:271 +#: user-manual.txt:259 msgid "" "_Modifying the dive profile_: When the cursor is moved around the dive " -"profile, its position is indicated by two right-angled red lines as shown " -"below. The time and depth represented by the cursor 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. " -"Drag the waypoints to represent an accurate time duration for the dive. " -"Below is a dive profile for a dive to 20 m for 30 min, followed by a 5 " -"minute safety stop at 5 m." +"profile, its position is shown by two right-angled red lines as seen below. " +"The time and depth represented by the cursor 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 you need to drag the appropriate waypoints downward to 20 m. To add a " +"waypoint, double-click on any line segment. To move an additional waypoint, " +"drag it. To remove a waypoint, right-click on it and choose \"Remove this " +"point\" from the context menu. Drag the waypoints to represent an accurate " +"time duration for the dive. Below is a dive profile for 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:272 +#: user-manual.txt:260 #, no-wrap msgid "images/DiveProfile2_f20.jpg" msgstr "images/DiveProfile2_f20.jpg" #. type: Plain text -#: user-manual.txt:284 +#: user-manual.txt:272 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 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 (see image below)." +"_Specifying the gas composition:_ The gas composition used is 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 above. The gas mixtures of segments of the dive profile can be " +"changed 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 (see image below)." msgstr "" #. type: Target for macro image -#: user-manual.txt:285 +#: user-manual.txt:273 #, no-wrap msgid "images/DiveProfile3_f20.jpg" msgstr "images/DiveProfile3_f20.jpg" #. type: Plain text -#: user-manual.txt:292 +#: user-manual.txt:280 msgid "" -"With the profile having been defined, more details must be added in order to " -"have a fuller record of the dive. To do this, the *Notes* and the " -"*Equipment* tabs on the top left hand of the _Subsurface_ window should be " -"used. Click on xref:S_Notes_dc[*this link*] for instructions to use these " -"tabs." +"With the profile now defined, more details must be added to have a fuller " +"record of the dive. To do this, the *Notes* and the *Equipment* tabs on the " +"top left hand of the _Subsurface_ window should be used. Click on xref:" +"S_Notes_dc[*this link*] for instructions on how to use these tabs." msgstr "" #. type: Title === -#: user-manual.txt:294 +#: user-manual.txt:281 #, no-wrap msgid "Importing new dive information from a Dive Computer" msgstr "Importer de nouvelles informations de plongée à partir de l'ordinateur de plongée" #. type: Title ==== -#: user-manual.txt:296 +#: user-manual.txt:283 #, no-wrap msgid "Connecting and importing data from a dive computer." msgstr "" #. type: Plain text -#: user-manual.txt:307 +#: user-manual.txt:293 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]." +"capture this information, using dive details 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:308 user-manual.txt:676 user-manual.txt:3061 +#: user-manual.txt:294 user-manual.txt:654 user-manual.txt:3026 #, no-wrap msgid "images/icons/warning2.png" msgstr "images/icons/warning2.png" #. type: Plain text -#: user-manual.txt:319 +#: user-manual.txt:304 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." +"Several dive computers consume more power when they are in PC-Communication " +"mode. **This could drain the dive computer's battery**. We recommend the " +"user checks to be sure 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:335 +#: user-manual.txt:320 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:" +"_Subsurface_, the two pieces of equipment must 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. " +"To set up this communication, users need 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 " +"A] provides the technical information to help the user achieve 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:338 +#: user-manual.txt:322 msgid "" -"After this, the dive computer can be hooked up to the user's PC, which can " -"be achieved by following these steps:" +"After this, the dive computer can be hooked up to the user's PC using these " +"steps:" msgstr "" #. type: Plain text -#: user-manual.txt:340 +#: user-manual.txt:324 msgid "" "The interface cable should be connected to a free USB port (or the Infra-red" msgstr "" #. type: Plain text -#: user-manual.txt:341 +#: user-manual.txt:325 msgid "or Bluetooth connection set up as described later in this manual)" msgstr "" #. type: Plain text -#: user-manual.txt:343 +#: user-manual.txt:327 msgid "The dive computer should be placed into PC Communication mode." msgstr "" #. type: Plain text -#: user-manual.txt:344 +#: user-manual.txt:328 msgid "(Refer to the manual of the specific dive computer)" msgstr "(Se reporter au manuel de l'ordinateur de plongée)" #. type: Plain text -#: user-manual.txt:348 +#: user-manual.txt:332 msgid "" "In _Subsurface_, from the Main Menu, select _Import -> Import From Dive " "Computer_. Dialogue *A* in the figure below appears:" msgstr "" #. type: Target for macro image -#: user-manual.txt:350 +#: user-manual.txt:334 #, no-wrap msgid "images/DC_import_f20.jpg" msgstr "images/DC_import_f20.jpg" #. type: Plain text -#: user-manual.txt:358 +#: user-manual.txt:342 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, if the dive computer allows this, _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)." +"Dive computers tend to keep a certain number of dives in memory, even though " +"these dives have already been imported to _Subsurface_. For that reason, if " +"the dive computer allows this, _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)." msgstr "" #. type: Plain text -#: user-manual.txt:365 +#: user-manual.txt:349 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, " @@ -848,7 +915,7 @@ msgid "" msgstr "" #. type: Plain text -#: user-manual.txt:376 +#: user-manual.txt:360 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 " @@ -857,80 +924,80 @@ msgid "" "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." +"a specific 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:386 +#: user-manual.txt:370 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 " +"panel. If one or more of your dives in _Subsurface_ has 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 " +"the dive computer, this box needs to be checked. 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:392 +#: user-manual.txt:376 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 dive in the _Subsurface_ " -"divelog will be overwritten by the dive record from the dive computer." +"divelog will be overwritten by the dive record from the computer." msgstr "" #. type: Plain text -#: user-manual.txt:395 +#: user-manual.txt:379 msgid "" "The checkbox marked _Download into new trip_ ensures that, after upload, the " "downloaded dives are grouped together as a new trip(s) in the *Dive List*." msgstr "" #. type: Plain text -#: user-manual.txt:399 +#: user-manual.txt:383 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)." +"when there are problems with downloads(see below)." msgstr "" #. type: Plain text -#: user-manual.txt:419 +#: user-manual.txt:402 msgid "" -"Then select the _Download_ button. With communication established, one can " +"Then select the _Download_ button. With communication established, you 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. 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). After successful download, Dialogue " -"*B* in the figure above appears. After the dives have been downloaded, they " -"appear in a tabular format on the right-hand side of the dialogue (see image " -"*B*, above). Each dive comprises a row in the table, with the date, duration " -"and depth shown. Next to each dive is a checkbox: check all the dives that " -"need to be transferred to the *Dive List*. In the case of the image above, " -"the last six dives are checked and will be transferred to the *Dive List*. " -"Then click the _OK_ button at the bottom of the dialogue. 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." +"bottom of the dialogue. Remember for some dive computers progress " +"information could be inaccurate since the program doesn’t know how much " +"downloadable data there is until the download is complete. After successful " +"download, Dialogue *B* in the figure above appears. After the dives have " +"been downloaded, they appear in a tabular format on the right-hand side of " +"the dialogue (see image *B*, above). Each dive comprises a row in the table, " +"with the date, duration and depth shown. Next to each dive is a checkbox: " +"check all the dives that need to be transferred to the *Dive List*. In the " +"case of the image above, the last six dives are checked and will be " +"transferred to the *Dive List*. Then click the _OK_ button at the bottom of " +"the dialogue. 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." msgstr "" #. type: Plain text -#: user-manual.txt:424 +#: user-manual.txt:407 msgid "" -"After this has been completed, select the OK button. The checked dives are " -"transferred to the *Dive List*." +"Then click the OK button. The checked dives are transferred to the *Dive " +"List*." msgstr "" #. type: Plain text -#: user-manual.txt:428 +#: user-manual.txt:411 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 " @@ -938,54 +1005,54 @@ msgid "" msgstr "" #. type: delimited block * -#: user-manual.txt:432 +#: user-manual.txt:415 #, no-wrap msgid "*PROBLEMS WITH DATA DOWNLOAD FROM A DIVE COMPUTER?*\n" msgstr "" #. type: Named 'icon' AttributeList argument for style 'icon' -#: user-manual.txt:432 user-manual.txt:542 user-manual.txt:586 -#: user-manual.txt:599 user-manual.txt:1176 user-manual.txt:1242 -#: user-manual.txt:1295 user-manual.txt:1371 user-manual.txt:1685 +#: user-manual.txt:415 user-manual.txt:521 user-manual.txt:565 +#: user-manual.txt:578 user-manual.txt:1149 user-manual.txt:1215 +#: user-manual.txt:1266 user-manual.txt:1342 user-manual.txt:1653 #, no-wrap msgid "images/icons/important.png" msgstr "images/icons/important.png" #. type: delimited block * -#: user-manual.txt:435 +#: user-manual.txt:418 msgid "Check the following:" msgstr "" #. type: delimited block * -#: user-manual.txt:438 +#: user-manual.txt:421 msgid "Is the dive computer still in PC-communication or Upload mode?" msgstr "" #. type: delimited block * -#: user-manual.txt:441 +#: user-manual.txt:423 msgid "" -"Is the battery of the dive computer fully charged? If not then the battery " -"must be charged or replaced." +"Is the dive computer’s battery fully charged? If not then charge or replace " +"it." msgstr "" #. type: delimited block * -#: user-manual.txt:445 +#: user-manual.txt:427 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?" +"Is the connecting cable faulty? Does the cable work 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:450 +#: user-manual.txt:432 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)." +"A] to be sure the correct Mount Point was specified (see above)." msgstr "" #. type: delimited block * -#: user-manual.txt:454 +#: user-manual.txt:436 msgid "" "On Unix-like operating systems, does the user have write permission to the " "USB port? If not, consult xref:" @@ -994,20 +1061,19 @@ msgid "" msgstr "" #. type: delimited block * -#: user-manual.txt:462 +#: user-manual.txt:444 msgid "" -"If the _Subsurface_ computer does not recognise the USB adaptor by showing " +"If the _Subsurface_ computer does not recognize 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:" +"possibility the cable or USB adaptor is faulty. A faulty cable is the most " +"common cause of communication failure between a dive computer and " +"_Subsurface_ computer. It’s also possible the _Subsurface_ computer cannot " +"interpret the data. Perform a download for diagnostic purposes with the " +"following two boxes checked in the download dialogue discussed above:" msgstr "" #. type: delimited block * -#: user-manual.txt:465 +#: user-manual.txt:447 #, no-wrap msgid "" "\tSave libdivecomputer logfile\n" @@ -1015,18 +1081,18 @@ msgid "" msgstr "" #. type: delimited block * -#: user-manual.txt:471 +#: user-manual.txt:453 #, 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" +"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 where the information will be saved. The default folder is the one in which the\n" +"_Subsurface_\n" "dive log is kept.\n" msgstr "" #. type: delimited block * -#: user-manual.txt:475 +#: user-manual.txt:457 #, no-wrap msgid "" "*Important:* _After downloading with the above checkboxes\n" @@ -1035,7 +1101,7 @@ msgid "" msgstr "" #. type: delimited block * -#: user-manual.txt:478 +#: user-manual.txt:460 #, no-wrap msgid "" "\tsubsurface.log\n" @@ -1043,133 +1109,115 @@ msgid "" msgstr "" #. type: delimited block * -#: user-manual.txt:484 +#: user-manual.txt:466 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 " +"analyzed. 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:487 +#: user-manual.txt:469 #, no-wrap msgid "Connecting _Subsurface_ to a Bluetooth-enabled dive computer" msgstr "" #. type: Named 'icon' AttributeList argument for style 'icon' -#: user-manual.txt:488 user-manual.txt:3606 +#: user-manual.txt:470 user-manual.txt:3578 #, no-wrap msgid "images/icons/bluetooth.jpg" msgstr "images/icons/bluetooth.jpg" #. type: Plain text -#: user-manual.txt:495 +#: user-manual.txt:477 msgid "" "Bluetooth is becoming a more common way of communication between dive " -"computers and _Subsurface_, for instance, the Shearwater Petrel Mk2 and the " -"OSTC Mk3. _Subsurface_ provides a largely operating system independent " +"computers and _Subsurface_, for or instance, the Shearwater Petrel Mk2 and " +"the OSTC Mk3. _Subsurface_ provides a largely operating system independent " "Bluetooth interface. Setting up _Subsurface_ for Bluetooth communication " "requires four steps:" msgstr "" #. type: Plain text -#: user-manual.txt:497 +#: user-manual.txt:479 msgid "" -"Ensure that Bluetooth is activated on the host computer running _Subsurface_." +"Be sure Bluetooth is activated on the host computer running _Subsurface_." msgstr "" #. type: Plain text -#: user-manual.txt:498 -msgid "" -"Ensure that _Subsurface_ sees the Bluetooth adapter on the host computer." +#: user-manual.txt:480 +msgid "Be sure _Subsurface_ sees the Bluetooth adapter on the host computer." msgstr "" #. type: Plain text -#: user-manual.txt:499 +#: user-manual.txt:481 msgid "" -"Ensure the Bluetooth-enabled dive computer is Bluetooth-discoverable and in " +"Be sure the Bluetooth-enabled dive computer is Bluetooth-discoverable and in " "PC upload mode." msgstr "" #. type: Plain text -#: user-manual.txt:500 +#: user-manual.txt:482 msgid "" -"Ensure that _Subsurface_ is paired with the Bluetooth-enabled dive computer." +"Be sure _Subsurface_ is paired with the Bluetooth-enabled dive computer." msgstr "" #. type: Plain text -#: user-manual.txt:504 +#: user-manual.txt:486 msgid "" "Select the Download dialogue by selecting _Import -> Import from dive " -"computer_ from the *Main Menu*. If one checks the check box labelled _" -"\"Choose Bluetooth download mode\"_, the dialogue below appears." +"computer_ from the *Main Menu*. If you check the box labelled _\"Choose " +"Bluetooth download mode\"_, the dialogue below appears." msgstr "" #. type: Title ===== -#: user-manual.txt:505 +#: user-manual.txt:486 #, no-wrap msgid "On Linux or MacOS:" msgstr "Sur Linux ou MacOS :" #. type: Target for macro image -#: user-manual.txt:507 +#: user-manual.txt:488 #, no-wrap msgid "images/DC_import_Bluetooth.jpg" msgstr "images/DC_import_Bluetooth.jpg" #. type: Plain text -#: user-manual.txt:515 +#: user-manual.txt:519 msgid "" "On the _Linux_ or _MacOS_ platforms the name of the _Subsurface_ computer " -"and its Bluetooth address are shown on the right-hand side, On the lefthand " +"and its Bluetooth address are shown on the right hand side, On the left hand " "side, if the computer has connected more than one local Bluetooth devices " "the user can use the list box to indicate which one needs to connect to " "_Subsurface_. The power state (on/off) of the Bluetooth adapter is shown " -"below the address and can be changed by checking the _Turn on/off_ check box." -msgstr "" - -#. type: Plain text -#: user-manual.txt:520 -msgid "" -"If the Bluetooth address is not shown, then _Subsurface_ does not see the " -"local Bluetooth device. Ensure that the Bluetooth driver is installed " -"correctly on the _Subsurface_ computer and check if it can be used by other " -"Bluetooth utilities like _bluetoothctl_ or _bluemoon_. This achieves the " -"first two steps above." -msgstr "" - -#. type: Plain text -#: user-manual.txt:524 -msgid "" -"Ensure that the Bluetooth-enabled dive computer is in PC-upload mode and " -"that it is discoverable by other Bluetooth devices. Consult the manual of " -"the dive computer to perform this. Now the third item in the list above has " -"been achieved." -msgstr "" - -#. type: Plain text -#: user-manual.txt:540 -msgid "" -"Select the _Scan_ button towards the bottom left of the dialogue above. " -"After searching for a small amount of time, the dive computer should be " -"listed (perhaps as one of a number of Bluetooth devices) in the main list " -"box on the lefthand side of the dialogue (see image above). If this is not " -"achieved, select the _Clear_ button and then scan again for Bluetooth " -"devices using the _Scan_ button. After performing these actions _Subsurface_ " -"should see the dive computer. The label of the discovered dive computer " -"contains the name of the device, its address and its pairing status. If the " -"device is not paired and has a red background colour, a context menu can be " -"opened by selecting the item with a right-click. Select the the _Pair_ " -"option and wait for the task to complete. If this dive computer is being " -"paired to Subsurface for the first time, it is possible that Subsurface will " -"request a Pass Code or PIN number. The most commonly-used Pass Code is 0000, " -"and this works for the Shearwater Petrel. If necessary, consult the user " -"manual of the dive computer being used." +"below the address and can be changed by checking the _Turn on/off_ box. If " +"the Bluetooth address is not shown, then _Subsurface_ does not see the local " +"Bluetooth device. Be sure the Bluetooth driver is installed correctly on the " +"_Subsurface_ computer and check if it can be used by other Bluetooth " +"utilities like _bluetoothctl_ or _bluemoon_. This finishes the first two " +"steps above. Be sure the Bluetooth-enabled dive computer is in PC-upload " +"mode and it is discoverable by other Bluetooth devices. Consult the manual " +"of the dive computer for more information. Now the third item in the list " +"above has been finished. Select the _Scan_ button towards the bottom left " +"of the dialogue above. After searching, the dive computer should be listed " +"(perhaps as one of a number of Bluetooth devices) in the main list box on " +"the lefthand side of the dialogue (see image above). If this does not work, " +"select the _Clear_ button, then scan again for Bluetooth devices using the " +"_Scan_ button. After taking these actions _Subsurface_ should see the dive " +"computer. The label of the discovered dive computer contains the name of " +"the device, its address and its pairing status. If the device is not paired " +"and has a red background color, a context menu can be opened by selecting " +"the item with a right-click. Select the the _Pair_ option and wait for the " +"task to complete. If this dive computer is being paired to Subsurface for " +"the first time, it’s possible Subsurface will request a Pass Code or PIN " +"number. The most commonly-used Pass Code is 0000, and this works for the " +"Shearwater Petrel. If necessary, consult the user manual of the dive " +"computer being used." msgstr "" #. type: delimited block * -#: user-manual.txt:547 +#: user-manual.txt:526 msgid "" "Currently _Subsurface_ does not support Bluetooth pairing with dive " "computers that require a custom PIN code. In order to pair the devices, use " @@ -1177,12 +1225,12 @@ msgid "" msgstr "" #. type: delimited block * -#: user-manual.txt:549 +#: user-manual.txt:528 msgid "One way to achieve this is to use +bluetoothctl+:" msgstr "" #. type: delimited block * -#: user-manual.txt:560 +#: user-manual.txt:539 #, no-wrap msgid "" "\t$ bluetoothctl\n" @@ -1198,66 +1246,65 @@ msgid "" msgstr "" #. type: Plain text -#: user-manual.txt:566 +#: user-manual.txt:545 msgid "" -"After the devices are paired the _Save_ button of the dialogue can be " -"pressed. This closes the Bluetooth dialogue. Now select _Download_ in the " -"_Download from dive computer_ dialogue which should still be open. The " -"downloaded dives are shown on the righthand side of the download dialogue." +"After the devices are paired, press the _Save_ button of the dialogue. This " +"closes the Bluetooth dialogue. Now select _Download_ in the _Download from " +"dive computer_ dialogue which should still be open. The downloaded dives are " +"shown on the righthand side of the download dialogue." msgstr "" #. type: Title ==== -#: user-manual.txt:567 user-manual.txt:3537 user-manual.txt:3621 +#: user-manual.txt:546 user-manual.txt:3505 user-manual.txt:3593 #, no-wrap msgid "On Windows:" msgstr "Sur Windows :" #. type: Target for macro image -#: user-manual.txt:568 +#: user-manual.txt:547 #, no-wrap msgid "images/DC_import_Bluetooth_Windows.png" msgstr "images/DC_import_Bluetooth_Windows.png" #. type: Plain text -#: user-manual.txt:578 +#: user-manual.txt:557 msgid "" "On _Windows_ platforms the _Local Bluetooth device details section_ on the " -"right is not displayed as is the case on the Linux/Mac implementations. To " -"successfully initiate a scan (by pressing the _Scan_ button) check that the " -"Bluetooth device on the _Subsurface_ computer is turned on by selecting the " -"dive computer from the list of available Bluetooth devices (see image " -"above). If the dive computer is accessed by Subsurface for the first time, " -"it is possible that Subsurface will request a Pass Code/PIN number. Supply " -"the Pass Code recommended in the user manual of the dive computer. A Pass " -"Code of 0000 is often appropriate." +"right is not displayed as is the case on the Linux/Mac systems. To start a " +"scan (by pressing the _Scan_ button) check that the Bluetooth device on the " +"_Subsurface_ computer is turned on by selecting the dive computer from the " +"list of available Bluetooth devices (see image above). If the dive computer " +"is being accessed by Subsurface for the first time, it’s possible Subsurface " +"will request a Pass Code or PIN number. Supply the Pass Code recommended in " +"the user manual of the dive computer. A Pass Code or PIN of 0000 is often " +"the default." msgstr "" #. type: Plain text -#: user-manual.txt:585 +#: user-manual.txt:564 msgid "" "The pairing step is checked and done automatically during the download " "process. If the devices have never been paired the system will ask for your " -"permissions and put a message on the right side of the screen: _Add a " -"device, Tap to set up your DC device_. Always allow this pairing. After a " -"discovered item is selected, select the _Save_ button. Finally select the " -"_Download_ button on the _Download_ dialogue and wait for the process to " -"complete." +"permission and put a message on the right side of the screen: _Add a device, " +"Tap to set up your DC device_. Always allow this pairing. After a discovered " +"item is selected, select the _Save_ button. Finally select the _Download_ " +"button on the _Download_ dialogue and wait for the process to complete." msgstr "" #. type: Plain text -#: user-manual.txt:593 +#: user-manual.txt:572 msgid "" "Currently _Subsurface_ works only with local Bluetooth adapters which use " "Microsoft Bluetooth Stack. If the local device uses _Widcomm_, _Stonestreet " -"One Bluetopia Bluetooth_ or _BlueSoleil_ drivers it will definitely not " -"work. However, Bluetooth hardware/dongles from these manufacturers (e.g. " -"iSonic) that support the Microsoft Bluetooth Stack do work." +"One Bluetopia Bluetooth_ or _BlueSoleil_ drivers it will not work. However, " +"Bluetooth hardware/dongles from these manufacturers (e.g. iSonic) that " +"support the Microsoft Bluetooth Stack do work." msgstr "" #. type: Plain text -#: user-manual.txt:598 +#: user-manual.txt:577 msgid "" -"A log messageOn the bottom left of the _Remote Bluetooth device selection_ " +"A log message on the bottom left of the _Remote Bluetooth device selection_ " "shows details about the current status of the Bluetooth agent. To select " "another dive computer for download using the \"Remote Bluetooth selection " "dialogue\" press the three-dots button from the _\"Choose Bluetooth download " @@ -1265,7 +1312,7 @@ msgid "" msgstr "" #. type: Plain text -#: user-manual.txt:608 +#: user-manual.txt:587 #, no-wrap msgid "" "*IN CASE OF PROBLEMS*: If the Bluetooth adapter from the _Subsurface_ computer\n" @@ -1277,100 +1324,98 @@ msgid "" msgstr "" #. type: Title ==== -#: user-manual.txt:611 +#: user-manual.txt:590 #, no-wrap msgid "Changing the name of a dive computer" msgstr "" #. type: Plain text -#: user-manual.txt:627 +#: user-manual.txt:606 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, consider 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." +"upload dive logs to _Subsurface_. For instance if a buddy’s dive computer is " +"the same make and model as your own and dive logs are uploaded from both " +"dive computers to the same _Subsurface_ computer, then you might like to " +"call one \"Alice's Suunto D4\" and the other \"Bob's Suunto D4\". " +"Alternatively, consider a technical diver who 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 \"Suunto D4 (2)\". This is easily done in _Subsurface_. On the " +"*Main Menu*, select _Log -> Edit device names_. A dialog box opens, showing " +"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:629 +#: user-manual.txt:608 #, no-wrap msgid "Updating the dive information imported from the dive computer." msgstr "" #. type: Plain text -#: user-manual.txt:636 +#: user-manual.txt:615 msgid "" "With the uploaded dives in the *Dive List*, 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 *Notes* and the *Equipment* tabs " -"on the top left hand of the _Subsurface_ window should be used." +"computer is not complete and more details must be added to have a full " +"record of the dives. To do this, the *Notes* and the *Equipment* tabs on the " +"top left hand of the _Subsurface_ window should be used." msgstr "" #. type: Title ===== -#: user-manual.txt:638 +#: user-manual.txt:617 #, no-wrap msgid "Notes" msgstr "Notes" #. type: Plain text -#: user-manual.txt:643 +#: user-manual.txt:622 msgid "" -"To have a more complete dive record the user needs to add additional " +"To have a more complete dive record, the user needs to add additional " "information by hand. The procedure below is virtually identical for hand-" "entered dives and for dives downloaded from a dive computer." msgstr "" #. type: Plain text -#: user-manual.txt:653 +#: user-manual.txt:632 msgid "" -"In some cases, one has to provide the date and time of the dive, e.g. when " -"entering a dive by hand or when a dive computer does not provide the date " -"and time of the dive. (Usually the date and time of the dive, gas mixture " -"and water temperature are shown as obtained from the dive computer) If the " -"contents of the *Notes 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 *Notes* tab, the following fields are visible (left " -"hand image, below):" +"In some cases, you must provide the date and time of the dive, for example " +"when entering a dive by hand or when a dive computer doesn’t provide the " +"date and time of the dive. (Usually the date and time of the dive, gas " +"mixture and water temperature are shown as obtained from the dive computer) " +"If the contents of the *Notes tab* is changed or edited in any way, the " +"message in a blue box at the top of the panel shows the dive is being " +"edited. If you click on the *Notes* tab, the following fields are visible " +"(left hand image, below):" msgstr "" #. type: Target for macro image -#: user-manual.txt:654 +#: user-manual.txt:633 #, no-wrap msgid "images/AddDive3_f22.jpg" msgstr "images/AddDive3_f22.jpg" #. type: Plain text -#: user-manual.txt:663 +#: user-manual.txt:642 msgid "" "The right hand image, above, shows a *Notes tab* filled with dive " "information. 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 " +"clicking the date, a calendar is displayed from which you 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 over-typing the information displayed." msgstr "" #. type: Plain text -#: user-manual.txt:674 +#: user-manual.txt:652 #, no-wrap msgid "" "*Air/water temperatures*: Air and water temperatures during the dive are shown\n" "in text boxes to the right of the Start time. Many dive computers supply water\n" -"temperature information and this box may therefore contain information.\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" +"temperature information and this box may have information.\n" +"If air temperature isn’t provided by the dive computer, the first temperature reading\n" +"might be used for the air temperature. Generally this is close to the real air temperature.\n" "If editing is required, only a value is required, the units of temperature will be\n" "automatically supplied by\n" "_Subsurface_ (following the _Preferences_, metric or imperial units will\n" @@ -1378,87 +1423,84 @@ msgid "" msgstr "" #. type: Plain text -#: user-manual.txt:676 +#: user-manual.txt:654 #, no-wrap msgid "*Location*:\n" msgstr "" #. type: Plain text -#: user-manual.txt:684 +#: user-manual.txt:662 msgid "" "Dive locations are managed as a *separate* part of the dive log. The dive " -"information in the *Notes* and *Equipment* tabs can therefore not be edited " +"information in the *Notes* and *Equipment* tabs can therefore NOT be edited " "at the same time as the dive site information. Save all the other dive " "information (e.g. divemaster, buddy, protective gear, notes about the dive) " -"by selecting _Apply changes_ on the *Notes* tab before editing the dive site " -"information. Only then, supply a dive site name in the textbox labelled " -"_Location_ on the *Notes* tab." +"by selecting _Apply changes_ on the *Notes* tab BEFORE editing the dive site " +"information. Then supply a dive site name in the textbox labelled _Location_ " +"on the *Notes* tab." msgstr "" #. type: Plain text -#: user-manual.txt:702 +#: user-manual.txt:680 msgid "" -"Type the name of the dive site, e.g. \"Tihany, Lake Balaton, Hungary\". If " -"several dives are performed at the same location, the dive site information " -"for the first dive is re-used. Existing dive location information can be " -"edited at any time by selecting (on the *Dive List* panel) a dive performed " -"at that site and by opening the location information by clicking the globe " -"button on the right of the location name (see image on the right, above). " -"When entering a dive location name, auto location of dive site names makes " -"it easy to select an existing dive site name (i.e. when typing the name of a " -"dive site, a dropdown list appears showing all sites with similar names). If " -"the dive site has been used before, click on the already-existing name. The " -"dive site names in the dropdown list contain either a globe symbol " -"(indicating existing dive sites in the _Subsurface_ database) or a *+* " -"symbol (indicating dive site names that appear consistent with the current " -"dive site name but which have not been added to the dive site database). " -"Therefore, if the present dive site has not been used before, a message " -"appears as follows (image *A* below):" +"Type in the name of the dive site, e.g. \"Tihany, Lake Balaton, Hungary\". " +"If several dives are made at the same location, the site information for the " +"first dive is re-used. Existing dive locations can be edited by selecting " +"(on the *Dive List* panel) a dive done at that site and by opening the " +"location information. Click the globe button on the right of the location " +"name (see image on the right, above). When entering a dive location name, " +"auto location of dive site names makes it easy to select an existing dive " +"site name. When typing the name of a dive site, a dropdown list appears " +"showing all sites with similar names. If the dive site has been used before, " +"click on the already-existing name. The dive site names in the dropdown " +"list contain either a globe symbol (indicating existing dive sites in the " +"_Subsurface_ database) or a *+* symbol (indicating dive site names that " +"appear consistent with the current dive site name but which haven’t been " +"added to the dive site database). If the present dive site has not been " +"used before, a message appears as follows (image *A* below):" msgstr "" #. type: Target for macro image -#: user-manual.txt:703 +#: user-manual.txt:681 #, no-wrap msgid "images/Locations1_f22.jpg" msgstr "images/Locations1_f22.jpg" #. type: Plain text -#: user-manual.txt:708 +#: user-manual.txt:686 msgid "" "Doubleclick on the new dive site name. A panel appears to enter the " -"coordinates and other important information about the site (image *B*, " -"above). The most important items are the coordinates of the site. There are " -"three ways of specifying the coordinates:" +"coordinates and other information about the site (image *B*, above). The " +"most important items are the coordinates of the site. There are three ways " +"to specify coordinates:" msgstr "" #. type: Plain text -#: user-manual.txt:715 +#: user-manual.txt:692 msgid "" -"One can find the coordinates on the world map in the bottom right hand part " -"of the _Subsurface_ window. The map displays an orange bar indicating \"No " -"location data - Move the map and double-click to set the dive location\". " -"Upon a doubleclick at the appropriate place, the orange bar disappears and " -"the coordinates are stored." +"Use the world map in the bottom right hand part of the _Subsurface_ window. " +"The map displays an orange bar indicating \"No location data - Move the map " +"and double-click to set the dive location\". Doubleclick at the appropriate " +"place, and the orange bar disappears and the coordinates are stored." msgstr "" #. type: Plain text -#: user-manual.txt:720 +#: user-manual.txt:697 msgid "" -"The coordinates can be obtained from the _Subsurface_ Companion app if the " -"user has an Android or iPhone device with GPS and if the coordinates of the " -"dive site were stored using that device. xref:S_Companion[Click here for " -"more information]" +"Use the _Subsurface_ Companion app if you have an Android or iPhone device " +"with GPS and if the dive site coordinates were stored using it. xref:" +"S_Companion[Click here for more information]" msgstr "" #. type: Plain text -#: user-manual.txt:723 +#: user-manual.txt:699 msgid "" -"The coordinates can be entered by hand if they are known, using one of four " -"formats with latitude followed by longitude:" +"Enter by hand if the coordinates are known, using one of four formats with " +"latitude followed by longitude:" msgstr "" #. type: Plain text -#: user-manual.txt:728 +#: user-manual.txt:704 msgid "" "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. " @@ -1466,163 +1508,162 @@ msgid "" msgstr "" #. type: Plain text -#: user-manual.txt:736 +#: user-manual.txt:712 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. Some keyboards " "don't have the degree sign (°). It can be replaced by a *d* like this: N30d " -"W20d. If both a dive site name and coordinates have been provided, Save the " +"W20d. If both a dive site name and coordinates have been provided, save the " "dive site information by selecting the button _Apply changes_ at the top of " "the panel." msgstr "" #. type: Plain text -#: user-manual.txt:742 +#: user-manual.txt:718 #, no-wrap msgid "" -"*Important*: GPS coordinates of a dive site are linked to the Location\n" -"name - so *saving* a dive site with only coordinates and no dive site name\n" -"causes unexpected behaviour (Subsurface will think that all of these\n" +"*Important*: GPS coordinates of a dive site are linked to the location\n" +"name - so *saving* a dive site with only coordinates and no name\n" +"causes problems. (Subsurface will think all of these\n" "dives have the same location and try to keep their GPS coordinates the\n" "same).\n" msgstr "" #. type: Plain text -#: user-manual.txt:752 +#: user-manual.txt:728 #, no-wrap msgid "" "*Dive site name lookup:* If coordinates have been typed into the appropriate\n" -"text box, one can perform an automated name lookup based on the coordinates.\n" -"This is achieved when _Subsurface_ uses the Internet to find the name of the dive site\n" +"text box, you can do an automated name lookup based on the coordinates.\n" +"This is done when _Subsurface_ uses the Internet to find the name of the dive site\n" "based on the coordinates that were typed. If a name has been found, it is\n" "automatically inserted into the tags box. The list box\n" "(Titled _Dive sites on same coordinates_\") at the bottom\n" "of the dive site panel contains the names of other dives sites used at the\n" "current location. For instance if the dive site is \"Blue Hole\" and there are several\n" -"dive sites named \"Blue Hole\", all these sites are listed in this list box.\n" +"sites named \"Blue Hole\", all of them are listed.\n" msgstr "" #. type: Plain text -#: user-manual.txt:757 +#: user-manual.txt:733 msgid "" -"Enter any other textual information about the dive site (Description and " +"Enter any other contextual information about the dive site (Description and " "Notes), then select _Apply Changes_ to save the geolocation for this dive " -"site. At a later stage the dive site information can be edited by clicking " -"the globe icon to the right of the dive site name in the *Notes tab*." +"site. The dive site information can later be edited by clicking the globe " +"icon to the right of the dive site name in the *Notes tab*." msgstr "" #. type: Plain text -#: user-manual.txt:762 +#: user-manual.txt:738 #, no-wrap msgid "" -"*Dive mode*: This is a dropdown box allowing one to choose the type of dive\n" -"performed. The options are OC (Open Circuit SCUBA, the default seting, meant for most recreational dives),\n" +"*Dive mode*: This is a dropdown box allowing you to choose the type of dive\n" +"performed. The options are OC (Open Circuit SCUBA, the default setting, for most recreational dives),\n" "Freedive (dive without SCUBA equipment), CCR (Closed-circuit\n" "rebreather) and pSCR (Passive semi-closed rebreather).\n" msgstr "" #. type: Plain text -#: user-manual.txt:767 +#: user-manual.txt:743 #, no-wrap msgid "" -"*Divemaster*: The name of the dive master or dive guide for this dive should be\n" +"*Divemaster*: The name of the divemaster or dive guide should be\n" "entered in this field\n" "which offers auto selection based on the list of dive masters in\n" "the current logbook.\n" msgstr "" #. type: Plain text -#: user-manual.txt:772 +#: user-manual.txt:748 #, 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" +"*Buddy*: In this field, enter the name(s) of the buddy or buddies\n" +"(separated with commas) who were on the\n" "dive. Auto selection based on the list of buddies in the current logbook is\n" "offered.\n" msgstr "" #. type: Plain text -#: user-manual.txt:777 +#: user-manual.txt:753 #, no-wrap msgid "" "*Suit*: Here the type of dive suit used can be entered.\n" "Auto selection 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 undersuit was used.\n" +"suit and thermal under suit was used.\n" msgstr "" #. type: Plain text -#: user-manual.txt:780 +#: user-manual.txt:756 #, no-wrap msgid "" -"*Rating*: One can provide a subjective overall rating of the dive on a\n" +"*Rating*: You 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:784 +#: user-manual.txt:760 #, no-wrap msgid "" -"*Visibility*: Similarly, one can provide a rating of visibility during the\n" +"*Visibility*: You 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:793 +#: user-manual.txt:768 #, no-wrap msgid "" -"*Tags*: Tags that describe the type of dive performed can be entered\n" +"*Tags*: Tags that describe the type of dive done 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" +"_Subsurface_ has many built-in tags. If you 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" +"will list the tags that correspond to the typing. For instance, by typing\n" +"+cav+, the tags *cave* and *cavern* are shown to choose from.\n" msgstr "" #. type: Plain text -#: user-manual.txt:795 +#: user-manual.txt:770 #, no-wrap msgid "*Notes*: Any additional information for the dive can be entered here.\n" msgstr "" #. type: Plain text -#: user-manual.txt:800 +#: user-manual.txt:775 msgid "" "The _Apply changes_ and _Discard changes_ 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. " -"The image xref:S_Notes_dc[at the beginning of this section] shows an example " -"of a *Notes tab* after completion of the dive information." +"information for tabs in the *Info* panel and in the *Dive Profile* panel. " +"Use them when *ALL* other information has been added. The image xref:" +"S_Notes_dc[at the beginning of this section] shows an example of a *Notes " +"tab* after completing the dive information." msgstr "" #. type: Title ===== -#: user-manual.txt:801 +#: user-manual.txt:776 #, no-wrap msgid "Equipment" msgstr "" #. type: Plain text -#: user-manual.txt:806 +#: user-manual.txt:781 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 " +"The Equipment tab lets you enter information about the type of cylinder and " +"gas used, as well as the weights used for the dive. The message in the blue " "box at the top of the panel:" msgstr "" #. type: Plain text -#: user-manual.txt:813 +#: user-manual.txt:788 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)." +"shows the dive is being edited. This is a highly interactive part of " +"_Subsurface_ and the information on cylinders and gases (entered here) " +"determines the behavior of the *Dive profile* (top right-hand panel)." msgstr "" #. type: Plain text -#: user-manual.txt:817 +#: user-manual.txt:792 #, no-wrap msgid "" "*Cylinders*: The cylinder information is entered through a dialogue that looks\n" @@ -1630,51 +1671,45 @@ msgid "" msgstr "" #. type: Target for macro image -#: user-manual.txt:818 +#: user-manual.txt:793 #, no-wrap msgid "images/DC_gas-dialogue1_f20.jpg" msgstr "images/DC_gas-dialogue1_f20.jpg" #. type: Plain text -#: user-manual.txt:827 +#: user-manual.txt:806 msgid "" "For hand-entered dives, this information needs to be typed in. For dive " -"computers, _Subsurface_ often obtains the gas used from the dive computer " -"and automatically inserts the gas composition(% oxygen or % helium) 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:832 -msgid "" -"The user should start by selecting a cylinder type on the left-hand side of " -"the table. To select a cylinder, the _Type_ box should be clicked. This " -"brings up a list button that can be used to display a dropdown list of " -"cylinders:" +"computers, _Subsurface_ often gets the gas used from the dive computer and " +"automatically inserts the gas composition(% oxygen or % helium) in the " +"table. The + button at the top right lets you add more cylinders for this " +"dive. The dark dust bin icon on the left lets you delete 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. Start by selecting a cylinder type on the left-" +"hand side of the table. To select a cylinder, the _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:833 +#: user-manual.txt:807 #, no-wrap msgid "images/DC_gas-dialogue2_f20.jpg" msgstr "images/DC_gas-dialogue2_f20.jpg" #. type: Plain text -#: user-manual.txt:840 +#: user-manual.txt:814 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 " +"used for this dive, or just 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 (_Work.press_) will automatically be shown in " "the dialogue." msgstr "" #. type: Plain text -#: user-manual.txt:844 +#: user-manual.txt:818 msgid "" "Next, indicate the starting pressure and the ending pressure of the " "specified gas during the dive. The unit of pressure (metric/imperial) " @@ -1682,7 +1717,7 @@ msgid "" msgstr "" #. type: Plain text -#: user-manual.txt:855 +#: user-manual.txt:829 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, " @@ -1691,108 +1726,108 @@ msgid "" "the cylinder, save the data either by pressing _ENTER_ on the keyboard or by " "clicking outside the cell containing 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):" +"hand. The following is an example of a complete description for a dive using " +"two cylinders (air and EAN50):" msgstr "" #. type: Target for macro image -#: user-manual.txt:856 +#: user-manual.txt:830 #, no-wrap msgid "images/CylinderDataEntry3_f20.jpg" msgstr "images/CylinderDataEntry3_f20.jpg" #. type: Plain text -#: user-manual.txt:863 +#: user-manual.txt:837 #, 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" +"using a dialogue similar to that of the cylinder information. If you\n" +"click\n" "the + button on the top right of the weights dialogue, the table looks like\n" "this:\n" msgstr "" #. type: Target for macro image -#: user-manual.txt:864 +#: user-manual.txt:838 #, no-wrap msgid "images/WeightsDataEntry1_f20.jpg" msgstr "images/WeightsDataEntry1_f20.jpg" #. type: Plain text -#: user-manual.txt:868 +#: user-manual.txt:842 msgid "" "By clicking on the _Type_ field, a drop-down list becomes accessible through " "a down-arrow:" msgstr "" #. type: Target for macro image -#: user-manual.txt:869 +#: user-manual.txt:843 #, no-wrap msgid "images/WeightsDataEntry2_f20.jpg" msgstr "images/WeightsDataEntry2_f20.jpg" #. type: Plain text -#: user-manual.txt:883 +#: user-manual.txt:857 msgid "" "This can be used to select the type of weight system used during the dive or " -"the user may start typing in the box to specify a different weighting " -"mechanism that will be saved by _Subsurface_. In the *Weight* field, type " -"in the amount of weight used during the dive. After specifying the weight " -"system, save the data by either pressing _ENTER_ on the keyboard or by " -"clicking 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:" +"just may start typing in the box to specify a different weighting mechanism " +"that will be saved by _Subsurface_. In the *Weight* field, type in the " +"amount of weight used during the dive. After specifying the weight system, " +"save the data by pressing _ENTER_ on the keyboard or by clicking outside the " +"cell with the cursor. It’s 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 dust bin 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: Target for macro image -#: user-manual.txt:884 +#: user-manual.txt:858 #, no-wrap msgid "images/WeightsDataEntry3_f20.jpg" msgstr "images/WeightsDataEntry3_f20.jpg" #. type: Title ==== -#: user-manual.txt:886 +#: user-manual.txt:860 #, no-wrap msgid "Editing several selected dives simultaneously" msgstr "" #. type: Plain text -#: user-manual.txt:901 +#: user-manual.txt:876 msgid "" "_METHOD 1_: After uploading dives from a dive computer, the dive profiles of " -"each uploaded dive is shown in the *Dive profile* tab, as well as a few " -"items of information in the *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 *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 *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." +"each is shown in the *Dive profile* tab, as well as a few items of " +"information in the *Notes* tab (e.g. water temperature) and in the " +"*Equipment* tab (e.g. gas pressures and gas composition). Other fields " +"remain empty. It may be useful to simultaneously edit some of the fields in " +"the *Notes* and *Equipment* tabs. For instance, it’s possible that a diver " +"performed several dives during a single day, using identical equipment at " +"the same dive site, or with the same divemaster and/or buddy or tags. " +"Instead of completing the information for each dive separately, select all " +"the dives for that day in the *Dive List* and insert the same information in " +"the *Notes* and *Equipment* fields that need identical information. This is " +"done by editing the dive notes or the equipment for any one of the selected " +"dives." msgstr "" #. type: Plain text -#: user-manual.txt:911 +#: user-manual.txt:886 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." +"Simultaneous editing only works with fields that do not already contain " +"information. This means 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 speeds up the completion of the dive log after several " +"similar dives." msgstr "" #. type: Plain text -#: user-manual.txt:920 +#: user-manual.txt:895 msgid "" "_METHOD 2_:There is a different way of achieving the same goal. Select a " "dive with all the appropriate information typed into the *Notes* and " @@ -1807,225 +1842,223 @@ msgid "" msgstr "" #. type: Title ==== -#: user-manual.txt:921 +#: user-manual.txt:896 #, no-wrap msgid "Adding Bookmarks to a dive" msgstr "" #. type: Plain text -#: user-manual.txt:926 +#: user-manual.txt:901 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:" +"Many divers wish to annotate dives with text that indicate particular " +"events, e.g. \"Saw dolphins\", or \"Released surface buoy\". This is easily " +"done:" msgstr "" #. type: Plain text -#: user-manual.txt:930 +#: user-manual.txt:905 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)." +"on the dive profile at that point (see *A* below)." msgstr "" #. type: Plain text -#: user-manual.txt:932 +#: user-manual.txt:907 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:935 +#: user-manual.txt:910 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:938 +#: user-manual.txt:913 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)." +"Hovering 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:939 +#: user-manual.txt:914 #, no-wrap msgid "images/Bookmarks.jpg" msgstr "images/Bookmarks.jpg" #. type: Title ==== -#: user-manual.txt:942 +#: user-manual.txt:917 #, no-wrap msgid "Saving the updated dive information" msgstr "" #. type: Plain text -#: user-manual.txt:953 +#: user-manual.txt:928 msgid "" "The information entered in the *Notes* tab and the *Equipment* tab can be " "saved by using the two buttons on the top right hand of the *Notes* tab. If " "the _Apply changes_ button is clicked, the dive data are saved in the memory " -"image of the dive. If the _Discard changes_ button is clicked, then the " -"newly entered dive data are erased from the computer memory, although the " -"dive profile is retained. When the user exits _Subsurface_ there is a final " -"prompt to confirm that the new data should now be saved permanently on the " +"image of the dive. If the _Discard changes_ button is clicked, the newly " +"entered dive data are erased from the computer memory, although the dive " +"profile is retained. When the user exits _Subsurface_ there is a final " +"prompt to confirm the new data should now be saved permanently on the " "computer disk." msgstr "" #. type: Title === -#: user-manual.txt:954 +#: user-manual.txt:929 #, no-wrap msgid "Importing dive information from other digital data sources or other data formats" msgstr "Importer les informations à partir d'autres sources de données numériques ou d'autres formats de données" #. type: Plain text -#: user-manual.txt:980 +#: user-manual.txt:954 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. a 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:990 -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. " -"Below follows more specific information to achieve data import to " -"_Subsurface_." +"If you’ve been diving for some time, it’s possible several dives were logged " +"using other dive log software. 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 you will " +"need to export the logbook(s) to an intermediate format so 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. a spreadsheet) " +"can also be imported by configuring the CSV import. _Subsurface_ can also " +"import UDDF and UDCF files used by some dive log software and some dive " +"computers, like the Heinrichs & Weikamp DR5. Finally, for some dive log " +"software like Mares Dive Organizer we currently recommend you import the " +"logbooks first into a web service like _divelogs.de_ and then import from " +"there with _Subsurface_. Divelogs.de supports a few additional logbook " +"formats that _Subsurface_ currently cannot handle." +msgstr "" + +#. type: Plain text +#: user-manual.txt:964 +msgid "" +"If the format of other software is supported natively on Subsurface, 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. Below is more specific information to import " +"data to _Subsurface_." msgstr "" #. type: Title ==== -#: user-manual.txt:991 +#: user-manual.txt:964 #, no-wrap msgid "Using the universal import dialogue" msgstr "" #. type: Plain text -#: user-manual.txt:997 +#: user-manual.txt:970 msgid "" -"Importing dives from other software is performed through a universal " -"interface activated by selecting _Import_ from the Main Menu, then clicking " -"on _Import Log Files_. This brings up dialogue *A*, below." +"Importing dives from other software is done through a universal interface " +"activated by selecting _Import_ from the Main Menu, then clicking on _Import " +"Log Files_. This brings up dialogue *A*, below." msgstr "" #. type: Target for macro image -#: user-manual.txt:998 +#: user-manual.txt:971 #, no-wrap msgid "images/Import1_f20.jpg" msgstr "images/Import1_f20.jpg" #. type: Plain text -#: user-manual.txt:1003 +#: user-manual.txt:976 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:" +"_Dive Log Files_ which accesses different types of direct imports available, " +"as in dialogue *B*, above. Currently these are:" msgstr "" #. type: Plain text -#: user-manual.txt:1005 +#: user-manual.txt:978 msgid "" "XML-formatted dive logs (DivingLog 5.0, MacDive and several other dive log " "systems)" msgstr "" #. type: Plain text -#: user-manual.txt:1006 +#: user-manual.txt:979 msgid "Cochran dive logs" msgstr "" #. type: Plain text -#: user-manual.txt:1007 +#: user-manual.txt:980 msgid "UDDF-formatted dive logs (e.g. Kenozoooid)" msgstr "" #. type: Plain text -#: user-manual.txt:1008 +#: user-manual.txt:981 msgid "UDCF-formatted dive logs" msgstr "" #. type: Plain text -#: user-manual.txt:1009 +#: user-manual.txt:982 msgid "Poseidon MkVI CCR logs" msgstr "" #. type: Plain text -#: user-manual.txt:1010 +#: user-manual.txt:983 msgid "APD Inspiration/Evolution CCR logs" msgstr "" #. type: Plain text -#: user-manual.txt:1011 +#: user-manual.txt:984 msgid "LiquiVision logs" msgstr "" #. type: Plain text -#: user-manual.txt:1012 +#: user-manual.txt:985 msgid "divelog.de logs" msgstr "" #. type: Plain text -#: user-manual.txt:1013 +#: user-manual.txt:986 msgid "OSTC Tools logs" msgstr "" #. type: Plain text -#: user-manual.txt:1014 +#: user-manual.txt:987 msgid "JDiveLog" msgstr "" #. type: Plain text -#: user-manual.txt:1015 +#: user-manual.txt:988 msgid "Suunto Dive Manager (DM3 and DM4)" msgstr "" #. type: Plain text -#: user-manual.txt:1016 +#: user-manual.txt:989 msgid "" "CSV (text-based and spreadsheet-based) dive logs, including APD CCR logs" msgstr "" #. type: Plain text -#: user-manual.txt:1021 +#: user-manual.txt:994 msgid "" "Selecting the appropriate format and then the specific log file in the large " -"window containing the file list on the right of the dialogue opens the " -"imported dive log in the _Subsurface_ *Dive List*. Some other formats, not " +"window containing the file list on the right 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:1022 +#: user-manual.txt:995 #, no-wrap msgid "Importing from OSTCTools" msgstr "" #. type: Plain text -#: user-manual.txt:1031 +#: user-manual.txt:1004 msgid "" "_OSTC Tools_ is a Microsoft-based suite of dive download and dive management " "tools for the OSTC family of dive computers. _OSTC Tools_ downloads dive " @@ -2038,104 +2071,105 @@ msgid "" msgstr "" #. type: Plain text -#: user-manual.txt:1035 +#: user-manual.txt:1008 msgid "" -"Actually, all H&W devices supported by OSTCTools can be imported to " -"_Subsurface_, this includes OSTC, OSTC Mk2, OSTC 2N/2C, OSTC3, OSTC Sport, " -"and probably although untested, Frog, OSTC2 and OSTC CR." +"All H&W devices supported by OSTCTools can be imported to _Subsurface_. This " +"includes OSTC, OSTC Mk2, OSTC 2N/2C, OSTC3, OSTC Sport, and probably " +"although untested, Frog, OSTC2 and OSTC CR." msgstr "" #. type: Plain text -#: user-manual.txt:1040 +#: user-manual.txt:1013 msgid "" -"Please, remember that OSTCTools is *not* a true diving log software, but a " -"useful set of tools for analysis and management of OSTC devices. This way, " -"only raw dive computer data will be performed with the import to " -"_Subsurface_; one has to to manually complete the rest of data which may be " -"important (buddies, equipment, notes, etc)." +"Please remember that OSTCTools is *not* a true diving log software, but " +"rather a useful set of tools for analysis and management of OSTC devices. " +"Only raw dive computer data will be imported to _Subsurface_; you have to " +"manually complete the rest of the data you want (buddies, equipment, notes, " +"etc)." msgstr "" #. type: Title ==== -#: user-manual.txt:1042 +#: user-manual.txt:1015 #, no-wrap -msgid "Importing from Mares Dive Organiser V2.1" +msgid "Importing from Mares Dive Organizer V2.1" msgstr "" #. type: Plain text -#: user-manual.txt:1049 +#: user-manual.txt:1022 msgid "" -"Since Mares utilise proprietary Windows software not compatible with multi-" +"Since Mares uses 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 " +"process, using _www.divelogs.de_ as a gateway to extract the dive log " "information." msgstr "" #. type: Plain text -#: user-manual.txt:1054 +#: user-manual.txt:1027 msgid "" -"Export the dive log data from Mares Dive Organiser to the user's desktop, " -"using a _.sdf_ file name extension. Refer to xref:Mares_Export[Appendix C] " -"for more information." +"Export the dive log data from Mares Dive Organizer to your desktop, using a " +"_.sdf_ file name extension. Refer to xref:Mares_Export[Appendix C] for more " +"information." msgstr "" #. type: Plain text -#: user-manual.txt:1060 +#: user-manual.txt:1033 msgid "" -"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_." +"Data should then be imported into _www.divelogs.de_. You will first need to " +"create a user account in _www.divelogs.de_. Log into that web site, then " +"select _Import Logbook -> Dive Organizer 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 Organizer database to _www." +"divelogs.de_." msgstr "" #. type: Plain text -#: user-manual.txt:1062 +#: user-manual.txt:1035 msgid "" "Finally, import the dives from _divelogs.de_ to _Subsurface_, using the " "instructions below." msgstr "" #. type: Title ==== -#: user-manual.txt:1065 +#: user-manual.txt:1038 #, no-wrap msgid "Importing dives from *divelogs.de*" msgstr "" #. type: Plain text -#: user-manual.txt:1078 +#: user-manual.txt:1051 msgid "" -"The import of dive information from _divelogs.de_ is simple, using a single " +"Importing dive information from _divelogs.de_ is simple, using a single " "dialogue box. The _Import -> Import from Divelogs.de_ option should be " "selected from the Main Menu. This brings up a dialogue box (see image *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 image *B*, below). " -"The _Apply_ button should then be selected, after which the imported dives " -"appear in the _Subsurface_ *Dive List* panel." +"below). Enter a user-ID and password for _divelogs.de_ 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 shown (see image *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:1079 +#: user-manual.txt:1052 #, no-wrap msgid "images/Divelogs1.jpg" msgstr "images/Divelogs1.jpg" #. type: Title ==== -#: user-manual.txt:1082 +#: user-manual.txt:1055 #, no-wrap msgid "Importing data in CSV format" msgstr "Importer des données au format CSV" #. type: Plain text -#: user-manual.txt:1093 +#: user-manual.txt:1066 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). The _CSV_ format is a universal simplified format that " -"allows for easy information exchange between different computers or software " +"allows easy information exchange between different computers or software " "packages. For an introduction to CSV-formatted files see xref:S_CSV_Intro[A " "Diver's Introduction To CSV Files]. _Subsurface_ dive logs can also be " "exported in _CSV_ format to other software that reads this format. See xref:" @@ -2145,61 +2179,61 @@ msgid "" msgstr "" #. type: Title ===== -#: user-manual.txt:1095 +#: user-manual.txt:1068 #, no-wrap msgid "Importing dives in CSV format from dive computers or other dive log software" msgstr "Importer les plongées au format CSV à partir des ordinateurs de plongées ou d'autres logiciels de carnet de plongée" #. type: Plain text -#: user-manual.txt:1100 +#: user-manual.txt:1073 msgid "" -"One can view a _CSV_ file by using an ordinary text editor. It is normally " -"organised into a single line that provides the headers (or _field names_ or " +"You can view a _CSV_ file by using an ordinary text editor. It’s normally " +"organized into a single line that provides the headers (or _field names_ or " "_column headings_) of the data columns, followed by the data, one record per " "line." msgstr "" #. type: Plain text -#: user-manual.txt:1102 +#: user-manual.txt:1075 msgid "" "There are two types of _CSV_ dive logs that can be imported into " "_Subsurface_:" msgstr "" #. type: Plain text -#: user-manual.txt:1108 +#: user-manual.txt:1081 msgid "" "_CSV dive details_: This dive log format contains similar information to " "that of a typical written dive log, e.g. dive date and time, dive depth, " -"dive duration, names of buddy and dive master and perhaps some information " -"about cylinder pressures before and after the dive, as well as a comment or " -"two about the dive. All the data for a single dive go on a single line of " -"text, following the order of the column headings." +"dive duration, names of buddy and divemaster and information about cylinder " +"pressures before and after the dive, as well as comments about the dive. All " +"the data for a single dive go on a single line of text, following the order " +"of the column headings." msgstr "" #. type: Plain text -#: user-manual.txt:1117 +#: user-manual.txt:1090 msgid "" "_CSV dive profile_: This dive log format includes much more information " "about a single dive. For instance there may be information at 30-second " -"intervals, indicating depth, water temperature at that depth, and cylinder " -"pressure at that moment in time. Each line contains the information for a " -"single instant in time during the dive, 30 seconds after that of the " -"previous instant. Many lines are required to complete the depth profile " -"information for a single dive. This is a common export format used by closed-" -"circuit rebreather (CCR) dive equipment and many software packages that " -"handle dive computer data and/or dive logs." +"intervals, indicating depth, water temperature, and cylinder pressure at " +"that moment in time. Each line contains the information for a single instant " +"in time during the dive, 30 seconds after that of the previous instant. Many " +"lines are required to complete the depth profile information for a single " +"dive. This is a common export format used by closed-circuit rebreather (CCR) " +"dive equipment and many software packages that handle dive computer data and/" +"or dive logs." msgstr "" #. type: Plain text -#: user-manual.txt:1120 +#: user-manual.txt:1093 msgid "" -"Before being able to import the _CSV_ data to _Subsurface_ *one needs to " +"Before being able to import the _CSV_ data to _Subsurface_ *you needs to " "know a few things about the data being imported*:" msgstr "" #. type: Plain text -#: user-manual.txt:1128 +#: user-manual.txt:1101 msgid "" "Which character separates the different columns within a single line of " "data? This field separator should be either a comma (,) a semicolon (;) or a " @@ -2211,7 +2245,7 @@ msgid "" msgstr "" #. type: Plain text -#: user-manual.txt:1132 +#: user-manual.txt:1105 msgid "" "Which data columns need to be imported into _Subsurface_? Is it a _CSV dive " "details_ file or a _CSV dive profile_ file? Open the file using a text " @@ -2220,15 +2254,15 @@ msgid "" msgstr "" #. type: Plain text -#: user-manual.txt:1134 +#: user-manual.txt:1107 msgid "" "Is the numeric information (e.g. dive depth) in metric or in imperial units?" msgstr "" #. type: Plain text -#: user-manual.txt:1141 +#: user-manual.txt:1114 msgid "" -"Armed with this information, importing the data into _Subsurface_ is " +"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_ (towards the bottom " "right). This shows all .CSV files in the selected directory. Select the file " @@ -2236,84 +2270,83 @@ msgid "" msgstr "" #. type: Target for macro image -#: user-manual.txt:1142 +#: user-manual.txt:1115 #, no-wrap msgid "images/csv_import1_f20.jpg" msgstr "images/csv_import1_f20.jpg" #. type: Plain text -#: user-manual.txt:1153 +#: user-manual.txt:1126 +#, no-wrap msgid "" -"Notice that, at the top left, there is a dropdown list containing pre-" -"configured settings for some of the more common dive computers and software " -"packages encountered by divers. If the _CSV_ file being imported originated " -"from any of these pre-configured items, then select it. Otherwise use the " -"_Manual Import_ option. The configuration panel also has dropdown lists for " -"the specification of the appropriate field separator (Tab, comma or " -"semicolon), the date format used in the _CSV_ file, the time units (seconds, " -"minutes or minutes:seconds), as well as the unit system (metric or " -"imperial). Selecting the appropriate options among these is critical for the " -"successful import of the data." +"At the top left, there is a dropdown list containing pre- configured\n" +"settings for common dive computers and software packages.\n" +" If the _CSV_ file being imported originated from any of\n" +"these pre-configured items, select it. Otherwise use the _Manual Import_\n" +"option. The configuration panel also has dropdown lists for the specification of the appropriate\n" +"field separator (Tab, comma or semicolon), the date format used in the _CSV_ file,\n" +"the time units (seconds, minutes or minutes:seconds), as well as the unit system\n" +"(metric or imperial). Selecting the appropriate options among these is critical for\n" +"the successful data import.\n" msgstr "" #. type: Plain text -#: user-manual.txt:1165 +#: user-manual.txt:1138 msgid "" -"The last remaining task is to ensure that all the data columns have the " -"appropriate column headings. The top blue row of the data table contains the " -"column headings found in the _CSV_ data file. The blue row of balloons " -"immediately above these contains the names understood by _Subsurface_. These " -"balloons can be moved using a drag-and-drop action. For instance, " -"_Subsurface_ expects the column heading for Dive number (\" # \") to be " -"\"Dive # \". If the column heading that _Subsurface_ expects is not in the " -"blue row, then drag the appropriate balloon from the upper area and drop it " -"in the appropriate blue cell at the top of the table. To indicate the " -"correct column for \"Dive #\", drag the ballooned item labelled \"Dive # \" " -"and drop it in the blue cell immediately above the white cell containing \" " -"# \". This is depicted in the image below." +"Complete this by ensuring that all the data columns have the appropriate " +"column headings. The top blue row of the data table contains the column " +"headings found in the _CSV_ data file. The blue row of balloons immediately " +"above these contains the names understood by _Subsurface_. These balloons " +"can be moved using a drag-and-drop action. For instance, _Subsurface_ " +"expects the column heading for Dive number (\" # \") to be \"Dive # \". If " +"the column heading that _Subsurface_ expects is not in the blue row, drag " +"the appropriate balloon from the upper area and drop it in the appropriate " +"blue cell at the top of the table. To indicate the correct column for \"Dive " +"#\", drag the ballooned item labelled \"Dive # \" and drop it in the blue " +"cell immediately above the white cell containing \" # \". This is depicted " +"in the image below." msgstr "" #. type: Target for macro image -#: user-manual.txt:1166 +#: user-manual.txt:1139 #, no-wrap msgid "images/csv_import2_f20.jpg" msgstr "images/csv_import2_f20.jpg" #. type: Plain text -#: user-manual.txt:1172 +#: user-manual.txt:1145 msgid "" -"Continue in this way to ensure that all the column headings in the blue row " -"of cells correspond to the headings listed in the top part of the dialogue. " -"Having completed this task, select the _OK_ button to the bottom right of " -"the dialogue. The data from the _CSV_ file are imported and shown in the " -"*Dive List* panel." +"Continue in this way to ensure all the column headings in the blue row of " +"cells correspond to the headings listed in the top part of the dialogue. " +"When finished, select the _OK_ button on the bottom right of the dialogue. " +"The data from the _CSV_ file are imported and shown in the *Dive List* panel." msgstr "" #. type: delimited block * -#: user-manual.txt:1176 +#: user-manual.txt:1149 #, no-wrap msgid "*A Diver's Introduction to _CSV_ Files*\n" msgstr "" #. type: delimited block * -#: user-manual.txt:1190 +#: user-manual.txt:1163 msgid "" "_CSV_ is an abbreviation for a data file format: _Comma-Separated Values_. " -"It is a file format allowing someone to view or edit the information using a " -"text editor such as Notepad (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 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." +"It is a file format that lets you view or edit information using a text " +"editor like Notepad (Windows), gedit (Linux) or TextWrangler (OS/X). There " +"are two main advantages of the _CSV_ format. First, the data are easily " +"editable as text without any proprietary software. Second, all information " +"is human-readable, not obscured by any custom or proprietary attributes that " +"proprietary software inserts 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 like spreadsheet-based dive logs and some " +"dive computers." msgstr "" #. type: delimited block * -#: user-manual.txt:1199 +#: user-manual.txt:1172 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 " @@ -2321,7 +2354,7 @@ msgid "" "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 " +"organized 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 " @@ -2329,7 +2362,7 @@ msgid "" msgstr "" #. type: delimited block * -#: user-manual.txt:1205 +#: user-manual.txt:1178 #, no-wrap msgid "" "\tDive site,Dive date,Time,Dive_duration, Dive_depth,Dive buddy\n" @@ -2340,14 +2373,14 @@ msgid "" msgstr "" #. type: delimited block * -#: user-manual.txt:1207 +#: user-manual.txt:1180 msgid "" "The above data are not easily read by a human. Here is the same information " "in TAB-delimited format:" msgstr "" #. type: delimited block * -#: user-manual.txt:1213 +#: user-manual.txt:1186 #, no-wrap msgid "" "\tDive site\tDive date\tTime\tDive_duration\tDive_depth\tDive buddy\n" @@ -2358,7 +2391,7 @@ msgid "" msgstr "" #. type: delimited block * -#: user-manual.txt:1221 +#: user-manual.txt:1194 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 " @@ -2372,7 +2405,7 @@ msgid "" msgstr "" #. type: delimited block * -#: user-manual.txt:1232 +#: user-manual.txt:1205 #, no-wrap msgid "" "\tDive Time (s)\tDepth (m)\tpO₂ - Setpoint (Bar) \tpO₂ - C1 Cell 1 (Bar)\tAmbient temp. (Celsius)\n" @@ -2388,70 +2421,65 @@ msgid "" msgstr "" #. type: delimited block * -#: user-manual.txt:1238 +#: user-manual.txt:1211 msgid "" "When a _CSV_ file is selected for import, _Subsurface_ displays the column " "headers as well as some of the data in the first few lines of the _CSV_ " -"file, making it much easier to work with _CSV_ files. _CSV_ files can " -"therefore be used in many contexts for importing data into a _Subsurface_ " -"dive log. Knowledge of a few basic things about the content of the _CSV_ " -"file allows a smooth import of the dives into _Subsurface_." +"file, making it much easier to work with _CSV_ files. _CSV_ files can be " +"used in many contexts for importing data into a _Subsurface_ dive log. " +"Knowing a few basic things about the content of the _CSV_ file helps with a " +"smooth import of the dives into _Subsurface_." msgstr "" #. type: Plain text -#: user-manual.txt:1252 +#: user-manual.txt:1225 msgid "" -"The _CSV_ import has a couple of caveats. One should avoid some special " -"characters like ampersand (&), less than (<), greater than (>) and double " -"quotes (\") as part of the numbers or text within a cell. The file should " -"use UTF-8 character set, if using non-ASCII characters. Also the size of the " -"_CSV_ file might cause problems. Importing 100 dives at a time (_CSV dive " +"But, the _CSV_ import has a couple of caveats. Avoid some special characters " +"like ampersand (&), less than (<), greater than (>) and double quotes (\") " +"as part of the numbers or text within a cell. The file should use UTF-8 " +"character set, if using non-ASCII characters. Also the size of the _CSV_ " +"file might cause problems. Importing 100 dives at a time (_CSV dive " "details_) works, but larger files might exceed the limits of the parser " "used. When encountering problems with _CSV_ imports, first try with a " "smaller file to make sure everything works." msgstr "" #. type: Title === -#: user-manual.txt:1255 +#: user-manual.txt:1228 #, no-wrap msgid "Importing GPS coordinates with the _Subsurface Companion App_ for mobile phones" msgstr "" #. type: Plain text -#: user-manual.txt:1264 +#: user-manual.txt:1237 #, no-wrap msgid "" "Using the *Subsurface Companion App* on an _Android device_ or\n" "xref:S_iphone[_iPhone_] with GPS, the coordinates\n" "for the diving\n" -"location can be automatically passed to the _Subsurface_\n" -"dive log. The Companion App stores the dive locations on\n" -"a dedicated Internet file server. _Subsurface_, in turn, can collect\n" -"the localities from the file server.\n" -msgstr "" - -#. type: Plain text -#: user-manual.txt:1266 -msgid "To do this:" +"location can be automatically passed to the _Subsurface_ dive log. The Companion App\n" +"stores dive locations on a dedicated Internet server. _Subsurface_ can collect\n" +"the locations from the server.\n" +"To do this:\n" msgstr "" #. type: Title ==== -#: user-manual.txt:1267 +#: user-manual.txt:1238 #, no-wrap msgid "Create a Companion App account" msgstr "" #. type: Plain text -#: user-manual.txt:1272 +#: user-manual.txt:1243 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 " +"will be sent, a long number giving you access to the file server and " "Companion App capabilities." msgstr "" #. type: Plain text -#: user-manual.txt:1277 +#: user-manual.txt:1248 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/?" @@ -2459,509 +2487,514 @@ msgid "" msgstr "" #. type: Title ==== -#: user-manual.txt:1278 +#: user-manual.txt:1249 #, no-wrap msgid "Using the Subsurface companion app on an Android smartphone" msgstr "" #. type: Plain text -#: user-manual.txt:1281 +#: user-manual.txt:1252 msgid "On first use the app has three options:" msgstr "" #. type: Plain text -#: user-manual.txt:1287 +#: user-manual.txt:1258 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." +"_Create a new account._ Equivalent to registering in the _Subsurface_ " +"companion page using an Internet browser. You can request a *DIVERID* using " +"this option, but it’s supplied via email and followed up by interaction with " +"the http://api.hohndel.org/login/[_Subsurface companion web page_] to " +"activate the account." msgstr "" #. type: Plain text -#: user-manual.txt:1290 +#: user-manual.txt:1261 msgid "" -"_Retrieve an account._ If users forgot their *DIVERID* they will receive an " +"_Retrieve an account._ If users forget their *DIVERID* they will receive an " "email to recover the number." msgstr "" #. type: Plain text -#: user-manual.txt:1294 +#: user-manual.txt:1265 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 " +"saves this *DIVERID* and doesn’t ask for it again unless you use the " "_Disconnect_ menu option (see below)." msgstr "" #. type: Plain text -#: user-manual.txt:1302 +#: user-manual.txt:1273 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." +"the Default Preferences panel, by selecting _File -> Preferences -> " +"Defaults_ from the main menu in _Subsurface_ itself. This helps " +"synchronization between _Subsurface_ and the Companion App." msgstr "" #. type: Title ===== -#: user-manual.txt:1303 +#: user-manual.txt:1274 #, no-wrap msgid "Creating new dive locations" msgstr "" #. type: Plain text -#: user-manual.txt:1308 +#: user-manual.txt:1279 msgid "" -"Now one is ready to get a dive position and send it to the server. The " +"Now you are 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:1311 +#: user-manual.txt:1282 msgid "" -"Touch the \"+\" icon on the top right to add a new dive site, a menu will be " -"showed with 3 options:" +"Touch the \"+\" icon on the top right to add a new dive site, a menu shows " +"with 3 options:" msgstr "" #. type: Plain text -#: user-manual.txt:1314 +#: user-manual.txt:1285 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:1323 +#: user-manual.txt:1294 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." +"Use Map: This option lets you fix a position by searching a world map. A " +"world map is shown (see *B* below) on which you can show the desired " +"position with a _long press_ on the touch sensitive screen (if the marked " +"location is wrong, simply choose a new location) and select the check " +"symbol in the upper right. A dialog is shown letting you enter the name of " +"the dive location and the date and time of the dive (see *C* below). In " +"order to import this dive location in _Subsurface_ you should set the time " +"to agree with the time of that dive on the dive computer." msgstr "" #. type: Target for macro image -#: user-manual.txt:1324 +#: user-manual.txt:1295 #, no-wrap msgid "images/Companion_5.jpg" msgstr "images/Companion_5.jpg" #. type: Plain text -#: user-manual.txt:1332 +#: user-manual.txt:1303 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." +"stored locations shown. Now 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:1333 +#: user-manual.txt:1304 #, no-wrap msgid "Dive lists of dive locations" msgstr "" #. type: Plain text -#: user-manual.txt:1341 +#: user-manual.txt:1312 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." +"selection box to the left showing they need to be uploaded to the server. " +"You can select individual dive locations from the list. A selected location " +"has a check mark in the selection box on the left. Group operations (like " +"_Delete_ or _Send_) are performed on several selected locations." msgstr "" #. type: Plain text -#: user-manual.txt:1349 +#: user-manual.txt:1320 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." +"or a map showing them. 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 you select 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:1350 +#: user-manual.txt:1321 #, no-wrap msgid "images/Companion_4.jpg" msgstr "images/Companion_4.jpg" #. type: Plain text -#: user-manual.txt:1356 +#: user-manual.txt:1327 msgid "" -"When one selects a dive (*not* selecting the check box), the name given to " +"When you select 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:1358 +#: user-manual.txt:1329 msgid "" "Edit (pencil): Change the text name or other characteristics of the dive " "location." msgstr "" #. type: Plain text -#: user-manual.txt:1360 -msgid "Maps: Display a map showing the dive location." -msgstr "" - -#. type: Plain text -#: user-manual.txt:1363 +#: user-manual.txt:1334 msgid "" -"After editing and saving a dive location (see *C* above), one needs to " -"upload it to the web service, as explained below." +"Maps: Display a map showing the dive location. After editing and saving a " +"dive location (see *C* above), upload it to the web service, as explained " +"below." msgstr "" #. type: Title ===== -#: user-manual.txt:1364 +#: user-manual.txt:1335 #, no-wrap msgid "Uploading dive locations" msgstr "" #. type: Plain text -#: user-manual.txt:1370 +#: user-manual.txt:1341 msgid "" -"There are several ways to send locations to the server. The easiest is by " +"There are several ways to send locations to the server. The easiest is " "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:1375 +#: user-manual.txt:1346 msgid "" -"Users must be careful, as the trash icon on the right means exactly what it " -"should; it deletes the selected dive location(s)." +"Be careful! 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:1376 +#: user-manual.txt:1347 #, no-wrap msgid "images/Companion_1.jpg" msgstr "images/Companion_1.jpg" #. type: Plain text -#: user-manual.txt:1381 +#: user-manual.txt:1352 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:1383 +#: user-manual.txt:1354 #, no-wrap msgid "Settings on the Companion App" msgstr "" #. type: Plain text -#: user-manual.txt:1386 +#: user-manual.txt:1357 msgid "" "Selecting the _Settings_ menu option results in the right hand image above " "(*B*)." msgstr "" #. type: Title ===== -#: user-manual.txt:1387 +#: user-manual.txt:1358 #, no-wrap msgid "Server and account" msgstr "" #. type: Plain text -#: user-manual.txt:1390 +#: user-manual.txt:1361 msgid "_Web-service URL._ This is predefined (http://api.hohndel.org/)" msgstr "" #. type: Plain text -#: user-manual.txt:1394 +#: user-manual.txt:1364 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." +"easiest way to get it is to copy and paste from the confirmation email or " +"just type it in." msgstr "" #. type: Title ===== -#: user-manual.txt:1395 +#: user-manual.txt:1364 #, no-wrap msgid "Synchronisation" msgstr "" #. type: Plain text -#: user-manual.txt:1399 +#: user-manual.txt:1368 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." +"and those on the web service synchronize each time the app is started." msgstr "" #. type: Plain text -#: user-manual.txt:1402 +#: user-manual.txt:1371 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:1403 +#: user-manual.txt:1372 #, no-wrap msgid "Background service" msgstr "" #. type: Plain text -#: user-manual.txt:1406 +#: user-manual.txt:1375 msgid "" -"Instead of entering a unique dive location, users can leave the service " -"running in the background of their Android device, allowing the continuous " +"Instead of entering an unique dive location, you can leave the service " +"running in the background of your Android device, allowing a continuous " "collection of GPS locations." msgstr "" #. type: Plain text -#: user-manual.txt:1409 -msgid "The settings below define the behaviour of the service:" +#: user-manual.txt:1377 +msgid "The settings below define the behavior of the service:" msgstr "" #. type: Plain text -#: user-manual.txt:1412 +#: user-manual.txt:1380 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:1414 +#: user-manual.txt:1382 msgid "_Min distance._ In meters. Minimum distance between two locations." msgstr "" #. type: Plain text -#: user-manual.txt:1416 +#: user-manual.txt:1384 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:1417 user-manual.txt:1514 user-manual.txt:1932 +#: user-manual.txt:1385 user-manual.txt:1486 user-manual.txt:1900 #, no-wrap msgid "images/icons/info.jpg" msgstr "images/icons/info.jpg" #. type: Plain text -#: user-manual.txt:1427 +#: user-manual.txt:1395 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 50 m 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." +"_How does the background service work?_ Assuming the diver 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 50 m 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 diver is not moving, only one location is " +"saved. If the diver is moving, a trace of the route is obtained by saving a " +"location every 50 meters." msgstr "" #. type: Title ===== -#: user-manual.txt:1428 +#: user-manual.txt:1396 #, no-wrap msgid "Other" msgstr "" #. type: Plain text -#: user-manual.txt:1432 +#: user-manual.txt:1400 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:1434 +#: user-manual.txt:1402 msgid "_Subsurface website._ A link to the URL of Subsurface web" msgstr "" #. type: Plain text -#: user-manual.txt:1436 +#: user-manual.txt:1404 msgid "_Version._ Displays the current version of the Companion App." msgstr "" #. type: Title ===== -#: user-manual.txt:1437 +#: user-manual.txt:1405 #, no-wrap msgid "Search" msgstr "" #. type: Plain text -#: user-manual.txt:1440 +#: user-manual.txt:1408 msgid "Search the saved dive locations by name or by date and time." msgstr "" #. type: Title ===== -#: user-manual.txt:1441 +#: user-manual.txt:1409 #, no-wrap msgid "Start service" msgstr "" #. type: Plain text -#: user-manual.txt:1444 +#: user-manual.txt:1412 msgid "" -"Initiates the _background service_ following the previously defined settings." +"Starts the _background service_ following the previously defined settings." msgstr "" #. type: Title ===== -#: user-manual.txt:1445 +#: user-manual.txt:1413 #, no-wrap msgid "Disconnect" msgstr "" #. type: Plain text -#: user-manual.txt:1453 +#: user-manual.txt:1421 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." +"This is admittedly a badly named option that disconnects the app from the " +"server. It resets 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 your Android device was " +"used to download the dive locations of another registered diver." msgstr "" #. type: Title ===== -#: user-manual.txt:1454 +#: user-manual.txt:1422 #, no-wrap msgid "Send all locations" msgstr "" #. type: Plain text -#: user-manual.txt:1457 +#: user-manual.txt:1425 msgid "" "This option sends all locations stored in the Android device to the server." msgstr "" #. type: Title ==== -#: user-manual.txt:1459 +#: user-manual.txt:1427 #, no-wrap msgid "Using the Subsurface companion app on an _iPhone_ to record dive locations" msgstr "" #. type: Plain text -#: user-manual.txt:1464 +#: user-manual.txt:1432 msgid "" -"The iPhone interface is quite simple. One needs to type the user ID " -"(obtained during registration) into the space reserved for it, then select " -"\"Dive in\" (see left part of the image below) and start collecting dive " -"location information." +"The iPhone interface is quite simple. Type the user ID (obtained during " +"registration) into the space reserved for it, then select \"Dive in\" (see " +"left part of the image below) and start collecting dive location information." msgstr "" #. type: Target for macro image -#: user-manual.txt:1465 +#: user-manual.txt:1433 #, no-wrap msgid "images/iphone.jpg" msgstr "images/iphone.jpg" #. type: Plain text -#: user-manual.txt:1472 +#: user-manual.txt:1444 msgid "" "Dives can be added automatically or manually. In manual mode, a dive " "location or waypoint is added to the GPS input stream. In automatic mode, a " -"continuous path of GPS locations is created from which, much later, after " -"import, subsurface can select the appropriate GPS locations based on the " -"times of dives. The default mode for the _iphone_ is automatic. When one " -"adds a dive, the location service is started automatically and a red bar " -"appears at the bottom of the screen. After the dive one can click on the red " -"bar to end the location service. While the location service is running one " -"can only add dives using the manual mechanism." +"continuous path of GPS locations is created from which, after import, " +"Subsurface can select the appropriate GPS locations based on the times of " +"dives. The default mode for the _iphone_ is automatic. When adding a dive, " +"the location service is started automatically and a red bar appears at the " +"bottom of the screen. After the dive, click on the red bar to end the " +"location service. While the location service is running you can only add " +"dives manually." msgstr "" #. type: Plain text -#: user-manual.txt:1478 +#: user-manual.txt:1450 msgid "" -"One can edit the site name afterwards by selecting the dive from the dive " +"You can edit the site name afterwards by selecting the dive from the dive " "list and clicking on the site name. There are no other editable fields. The " -"dive list is automatically uploaded from the iPhone to the webservice and " -"there is not an option to trigger upload manually." +"dive list is automatically uploaded from the iPhone to the web service. " +"There isn’t an option to trigger upload manually." msgstr "" #. type: Title ==== -#: user-manual.txt:1480 +#: user-manual.txt:1452 #, no-wrap msgid "Downloading dive locations to the _Subsurface_ divelog" msgstr "" #. type: Plain text -#: user-manual.txt:1489 +#: user-manual.txt:1461 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:" +"Provide a DIVERID, then select the _Download_ button to start the download " +"process, after which the screen on the right (*B*) below appears:" msgstr "" #. type: Target for macro image -#: user-manual.txt:1490 +#: user-manual.txt:1462 #, no-wrap msgid "images/DownloadGPS.jpg" msgstr "images/DownloadGPS.jpg" #. type: Plain text -#: user-manual.txt:1498 +#: user-manual.txt:1470 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 " +"Note that the _Apply_ button is now active. By clicking on it, you can " +"update the locations of the newly entered or uploaded dives in _Subsurface_. " +"That applies the coordinates and names entered on the app to all the new " +"dives that match the date-times of the uploaded GPS localities. If you have " "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:1505 +#: user-manual.txt:1477 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." +"assignment of GPS data to dives depends on agreeing date-time information " +"between the two devices. Although _Subsurface_ has a wide range tolerance, " +"it may not be able to identify the appropriate dive if there's a large " +"difference between the time in the dive computer and that of the Android " +"device. That results in no updates." msgstr "" #. type: Plain text -#: user-manual.txt:1513 +#: user-manual.txt:1485 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 " +"for this (e.g. time zones). _Subsurface_ may also 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." +"subsequent dives as well). A workaround 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:1517 +#: user-manual.txt:1489 msgid "TIPS:" msgstr "" #. type: Plain text -#: user-manual.txt:1524 +#: user-manual.txt:1492 +msgid "" +"_Background service_ may fill the location list with unnecessary locations " +"that don’t correspond to the exact dive point but do correspond to the " +"boat's route." +msgstr "" + +#. type: Plain text +#: user-manual.txt:1493 +msgid "" +"Right now, these locations are difficult to delete from the server. In some " +"situations it" +msgstr "" + +#. type: Plain text +#: user-manual.txt:1496 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)." +"is better 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 you want to keep the location list " +"clear to see dives in the web service map display (see above)." msgstr "" #. type: Plain text -#: user-manual.txt:1528 +#: user-manual.txt:1499 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 " @@ -2970,371 +3003,363 @@ msgid "" msgstr "" #. type: Title === -#: user-manual.txt:1530 +#: user-manual.txt:1501 #, no-wrap msgid "Adding photographs to dives" msgstr "" #. type: Plain text -#: user-manual.txt:1536 +#: user-manual.txt:1507 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." +"during a dive. To match each photograph with a specific dive, _Subsurface_ " +"lets you load photos into a dive. Photos are superimposed on the dive " +"profile, from where they can be viewed." msgstr "" #. type: Title ==== -#: user-manual.txt:1537 +#: user-manual.txt:1508 #, no-wrap -msgid "Loading photos and getting synchronisation between dive computer and camera" +msgid "Loading photos and synchronizing between dive computer and camera" msgstr "" #. type: Plain text -#: user-manual.txt:1541 +#: user-manual.txt:1512 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:1542 +#: user-manual.txt:1513 #, no-wrap msgid "images/LoadImage1_f20.jpg" msgstr "images/LoadImage1_f20.jpg" #. type: Plain text -#: user-manual.txt:1546 +#: user-manual.txt:1517 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:1547 +#: user-manual.txt:1518 #, no-wrap msgid "images/LoadImage2_f20.jpg" msgstr "images/LoadImage2_f20.jpg" #. type: Plain text -#: user-manual.txt:1556 +#: user-manual.txt:1527 msgid "" -"This brings up 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." +"This brings up the time synchronization dialog, shown below. But be aware " +"that the time synchronization 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 synchronize, then the " +"exact times of photographs can be used to position photographs on the dive " +"profile." msgstr "" #. type: Plain text -#: user-manual.txt:1558 -msgid "_Subsurface_ achieves this synchronisation in three ways:" +#: user-manual.txt:1529 +msgid "_Subsurface_ synchronizes in three ways:" msgstr "" #. type: Plain text -#: user-manual.txt:1561 +#: user-manual.txt:1532 #, no-wrap msgid "" -"*Pro-actively*: Before the dive, ensure synchronisation of the dive computer time settings with\n" +"*Pro-actively*: Before the dive, ensure synchronization of the dive computer time settings with\n" "the time settings of the camera by changing the date-time settings on one or both of these devices.\n" msgstr "" #. type: Plain text -#: user-manual.txt:1572 +#: user-manual.txt:1543 #, 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" +"*Manually*: If you wrote down the exact camera time at the start of a dive, the\n" +"difference in time between the two devices can be determined. As long as the device\n" +"settings for time has not been changed in either device, you could write down the times of\n" +"both devices after the dive or even at the end of the day. You 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" +"immediately under the heading _Shift times of image(s) by_, shown 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" +"in that tool. Click the _OK_ button and synchronization is done.\n" msgstr "" #. type: Target for macro image -#: user-manual.txt:1573 +#: user-manual.txt:1544 #, no-wrap msgid "images/LoadImage3b_f20.jpg" msgstr "images/LoadImage3b_f20.jpg" #. type: Plain text -#: user-manual.txt:1591 +#: user-manual.txt:1562 #, 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" +"*By photograph*: There is a very slick way of synchronizing. If you take a\n" +"photograph of the face of the dive computer showing the time, then _Subsurface_ can get\n" +"the exact time the photograph was taken, using the metadata the camera stores within\n" +"each photo. To do this, use the bottom half of the _Time shift_ dialog. If you use\n" "the bottom part, the top part of the dialog is ignored. Click on\n" -"the horizontal bar entitled \"_Select image of dive computer showing time_. This brings up\n" -"a file browser with which one can select the photograph of the dive computer time. Select the\n" +"the horizontal bar called \"_Select image of dive computer showing time_. This brings up\n" +"a file browser letting you select the photograph of the dive computer time. 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" +"so it 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.\n" +"camera and dive computer is, and it can synchronize.\n" "Image *B* above shows a photograph of the face of the dive computer and with the date-time tool set to the\n" "date-time.\n" msgstr "" #. type: Plain text -#: user-manual.txt:1594 +#: user-manual.txt:1565 msgid "" "If the timestamp of a photograph is more than 30 minutes before or after the " "dive, it is not placed on the dive profile." msgstr "" #. type: Title ==== -#: user-manual.txt:1595 +#: user-manual.txt:1566 #, no-wrap msgid "Viewing the photos" msgstr "" #. type: Plain text -#: user-manual.txt:1598 +#: user-manual.txt:1569 msgid "After the images have been loaded, they appear in two places:" msgstr "" #. type: Plain text -#: user-manual.txt:1600 +#: user-manual.txt:1571 msgid "the _Photos_ tab of the *Notes* panel." msgstr "" #. type: Plain text -#: user-manual.txt:1604 +#: user-manual.txt:1575 msgid "" "as tiny icons (stubs) on the dive profile at the appropriate positions " -"reflecting the time each photograph was taken. In order to view the photos " -"on the dive profile, activate the _show-photos_ button in the tool bar to " -"the left of the dive profile:" +"reflecting the time each photograph was taken. To view the photos on the " +"dive profile, 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:1605 +#: user-manual.txt:1576 #, no-wrap msgid "images/icons/ShowPhotos_f20.png" msgstr "images/icons/ShowPhotos_f20.png" #. type: Plain text -#: user-manual.txt:1608 +#: user-manual.txt:1579 msgid "This results in a profile display as in the image below:" msgstr "" #. type: Target for macro image -#: user-manual.txt:1609 +#: user-manual.txt:1580 #, no-wrap msgid "images/LoadImage4_f20.jpg" msgstr "images/LoadImage4_f20.jpg" #. type: Plain text -#: user-manual.txt:1613 +#: user-manual.txt:1584 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:" +"If you hover the mouse over any of the photo icons, a thumbnail photo is " +"shown of the appropriate photo. See the image below:" msgstr "" #. type: Target for macro image -#: user-manual.txt:1614 +#: user-manual.txt:1585 #, no-wrap msgid "images/LoadImage5_f20.jpg" msgstr "images/LoadImage5_f20.jpg" #. type: Plain text -#: user-manual.txt:1623 +#: user-manual.txt:1594 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)." +"_Subsurface_ window. This allows good viewing of the added photographs. (see " +"the image below). Note that the thumbnail has a small dustbin icon in the " +"bottom right hand corner (see image above). Selecting the dustbin removes " +"the image from the dive. Be careful 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:1624 +#: user-manual.txt:1595 #, no-wrap msgid "images/LoadImage6_f20.jpg" msgstr "images/LoadImage6_f20.jpg" #. type: Title ==== -#: user-manual.txt:1626 +#: user-manual.txt:1597 #, no-wrap msgid "The _Photos_ tab" msgstr "" #. type: Plain text -#: user-manual.txt:1637 +#: user-manual.txt:1608 msgid "" "Photographs associated with a dive are shown as thumbnails in the _Photos_ " "tab of the _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." +"accessing the photos of a dive, while the stubs on the dive profile show " +"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:1638 +#: user-manual.txt:1609 #, no-wrap msgid "Photos on an external hard disk" msgstr "" #. type: Plain text -#: user-manual.txt:1649 +#: user-manual.txt:1619 msgid "" -"Most underwater photographers store their photos on an external drive. If " -"such a drive can be mapped by the operating system (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." +"Most underwater photographers store photos on an external drive. If such a " +"drive can be mapped by the operating system (almost always the case) the " +"photos can be directly accessed by _Subsurface_. This eases 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 synchronization (see text above) is used. 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. If the external drive with the photos " +"is re-connected, the photos can be seen in the normal way." msgstr "" #. type: Title ==== -#: user-manual.txt:1651 +#: user-manual.txt:1621 #, no-wrap msgid "Moving photographs among directories, hard disks or computers" msgstr "" #. type: Plain text -#: user-manual.txt:1661 +#: user-manual.txt:1631 #, no-wrap msgid "" "After a photograph has been loaded into _Subsurface_ and associated with a specific dive, the directory\n" -" where the photo lies is stored, allowing _Subsurface_ to find the photograph when the dive is\n" +" where the photo lies is stored, letting _Subsurface_ find the photograph when the dive is\n" " opened again. If the photo or the whole photo collection is moved to another drive or to a different\n" -" machine, it is unlikely that the directory structure will remain identical to that of the original uploaded\n" +" machine, the directory structure will be different to that of the original uploaded\n" " photo. When this happens, _Subsurface_ looks for the photos at their original location before they were moved,\n" -" cannot find them and therefore cannot display them. Because, after moving photos, large numbers of photos\n" +" cannot find them and cannot display them. Because after moving photos, large numbers of photos\n" " may need to be deleted and re-imported from the new location, _Subsurface_ has a mechanism that eases the\n" " process of updating the directory information for each photo: automatic updates using fingerprints.\n" msgstr "" #. type: Plain text -#: user-manual.txt:1666 +#: user-manual.txt:1635 #, no-wrap msgid "" "When a photo is loaded into _Subsurface_, a fingerprint for the image is calculated and stored with the\n" " other reference information for that photo. After moving a photo collection (that has already been loaded\n" -" into _Subsurface_) to a different directory, disk or computer, _Subsurface_ can perform the\n" -" following steps:\n" +" into _Subsurface_) to a different directory, disk or computer, _Subsurface_ can:\n" msgstr "" #. type: Plain text -#: user-manual.txt:1668 +#: user-manual.txt:1638 msgid "" "look through a particular directory (and all its subdirectories recursively) " -"where photos have been moved" +"where photos have been moved to," msgstr "" #. type: Plain text -#: user-manual.txt:1669 -msgid "to," -msgstr "" - -#. type: Plain text -#: user-manual.txt:1671 +#: user-manual.txt:1639 msgid "calculate fingerprints for all photos in this directory, and" msgstr "" #. type: Plain text -#: user-manual.txt:1673 +#: user-manual.txt:1641 msgid "" "if there is a match between a calculated fingerprint and the one originally " "calculated when a photo was" msgstr "" #. type: Plain text -#: user-manual.txt:1675 +#: user-manual.txt:1643 msgid "" -"loaded into _Subsurface_ (even if the original file name has changed), to " +"loaded into _Subsurface_ (even if the original file name has changed), " "automatically update the directory information so that _Subsurface_ can find " "the photo in the new moved directory." msgstr "" #. type: Plain text -#: user-manual.txt:1680 +#: user-manual.txt:1648 #, no-wrap msgid "" -"This is achieved by selecting from the Main Menu: _File -> Find moved images_. This brings up a window within\n" +"This is done by selecting from the Main Menu: _File -> Find moved images_. This brings up a window within\n" " which the NEW directory of the photos needs to be specified. Select the appropriate directory and click\n" " the _Scan_ button towards the bottom right of the panel. The process may require several minutes to\n" " complete, after which _Subsurface_ will show the appropriate photographs when a particular dive is opened.\n" msgstr "" #. type: delimited block * -#: user-manual.txt:1685 +#: user-manual.txt:1653 #, no-wrap msgid "*Upgrading existing photo collections without fingerprints*\n" msgstr "" #. type: delimited block * -#: user-manual.txt:1690 +#: user-manual.txt:1658 msgid "" -"_Subsurface_ automatically calculates fingerprints for all images that can " -"be accessed by _Subsurface_. When manipulating images, ensure that all the " -"images associated with the dive log can be accessed by _Subsurface_." +"_Subsurface_ automatically calculates fingerprints for all images that it " +"can access. When manipulating images, be sure all the images associated " +"with the dive log can be accessed by _Subsurface_." msgstr "" #. type: delimited block * -#: user-manual.txt:1692 +#: user-manual.txt:1660 msgid "" "_Subsurface_ automatically checks and, if necessary, updates the " "fingerprints associated with a single dive if:" msgstr "" #. type: delimited block * -#: user-manual.txt:1693 +#: user-manual.txt:1661 msgid "" "The images associated with that dive are visible as thumbnails on the *Dive " "Profile*." msgstr "" #. type: delimited block * -#: user-manual.txt:1694 +#: user-manual.txt:1662 msgid "" -"One edits anything in the *Notes tab* panel and save the edits by selecting " -"_Apply changes_." +"If you edit anything in the *Notes tab* panel and save the edits by " +"selecting _Apply changes_." msgstr "" #. type: Title === -#: user-manual.txt:1698 +#: user-manual.txt:1666 #, no-wrap msgid "Logging special types of dives" msgstr "" #. type: Title ==== -#: user-manual.txt:1701 +#: user-manual.txt:1669 #, no-wrap msgid "Multicylinder dives" msgstr "" #. type: Plain text -#: user-manual.txt:1708 +#: user-manual.txt:1676 msgid "" "_Subsurface_ easily handles dives involving more than one cylinder. Multi-" -"cylinder diving usually happens (a) if a diver does not have enough gas for " -"the complete dive in a single cylinder; (b) if the diver needs more than one " +"cylinder diving usually happens (a) if a diver doesn’t have enough gas for " +"the complete dive in a single cylinder; (b) if a diver needs more than one " "gas mixture because of the depth or the decompression needs of the dive. For " "this reason multi-cylinder dives are often used by technical divers who dive " "deep or long. As far as _Subsurface_ is concerned, there are only two types " @@ -3342,26 +3367,26 @@ msgid "" msgstr "" #. type: Plain text -#: user-manual.txt:1712 +#: user-manual.txt:1680 #, no-wrap msgid "" "*Describe the cylinders used during the dive* This is performed in the *Equipment tab* of\n" "the *Info* panel, as xref:cylinder_definitions[described above]. Enter the cylinders one by one,\n" -"specifying the characteristics of the cylinder and the gas composition within each cylinder.\n" +"specifying each’s characteristics and the gas composition within it.\n" msgstr "" #. type: Plain text -#: user-manual.txt:1717 +#: user-manual.txt:1685 #, no-wrap msgid "" -"*Record the times at which switches from one cylinder to another was done:* This is information\n" -"provided by some dive computers (provided the diver indicated these changes to the dive computer\n" +"*Record the times at which the switch from one cylinder to another was done:* This is information\n" +"tracked by some dive computers (provided the diver indicated these changes to the dive computer\n" "by pressing specific buttons). If the dive computer does not provide the information, the diver has to\n" "record these changes using a different method, e.g. writing it on a slate.\n" msgstr "" #. type: Plain text -#: user-manual.txt:1725 +#: user-manual.txt:1693 #, no-wrap msgid "" "*Record the cylinder changes on the dive profile*: If the latter option\n" @@ -3374,53 +3399,52 @@ msgid "" msgstr "" #. type: Plain text -#: user-manual.txt:1729 +#: user-manual.txt:1697 msgid "" -"Having performed these tasks, _Subsurface_ indicates the appropriate use of " +"When this is complete, _Subsurface_ indicates the appropriate use of " "cylinders in the dive profile. Below is a multi-cylinder dive, starting off " -"with EAN28, then changing cylinders to EAN50 after 26 minutes to perform " +"with EAN28, then changing cylinders to EAN50 after 26 minutes for " "decompression." msgstr "" #. type: Target for macro image -#: user-manual.txt:1730 +#: user-manual.txt:1698 #, no-wrap msgid "images/multicylinder_dive.jpg" msgstr "images/multicylinder_dive.jpg" #. type: Title ==== -#: user-manual.txt:1732 +#: user-manual.txt:1700 #, no-wrap msgid "Sidemount dives" msgstr "" #. type: Plain text -#: user-manual.txt:1738 +#: user-manual.txt:1706 msgid "" "Sidemount diving is just another form of multi-cylinder diving, often with " -"both or all cylinders having the same gas mixture. Although it is a popular " -"configuration for cave divers, sidemount diving can be performed by " -"recreational divers who have completed the appropriate training. Sidemount " -"dive logging involves, exactly as with multi-cylinder dives, above, three " -"steps:" +"both or all cylinders having the same gas mixture. Although it’s a popular " +"configuration for cave divers, Sidemount diving can be done by recreational " +"divers who’ve completed the appropriate training. sidemount dive logging " +"involves three steps, exactly as with multi-cylinder dives above:" msgstr "" #. type: Plain text -#: user-manual.txt:1747 +#: user-manual.txt:1715 #, no-wrap msgid "" "*During the dive, record 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, many 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" +"cylinders with air or with the same gas mixture, _Subsurface_ distinguishes between these different\n" +"cylinders. In contrast, many dive computers that allow gas switching only distinguish between different\n" +"_gases_ used, not among different _cylinders_ used. This means when sidemount dives are downloaded\n" +"from these dive computers, the switching event between cylinders with the same gas is not downloaded. This may mean\n" +"that a diver may have to keep a written log of cylinder switch times using a slate, or (if the dive computer\n" +"has the capability) marking each cylinder switch with a bookmark that can be retrieved later. Returning\n" "from a dive with the times of cylinder changes is the only tricky part of logging sidemount dives.\n" msgstr "" #. type: Plain text -#: user-manual.txt:1750 +#: user-manual.txt:1718 #, no-wrap msgid "" "*Within _Subsurface_ describe the cylinders used during the dive*. The diver needs to provide the\n" @@ -3429,76 +3453,76 @@ msgid "" msgstr "" #. type: Plain text -#: user-manual.txt:1760 +#: user-manual.txt:1728 #, 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" +"from a dive computer into _Subsurface_, the cylinder switch events need to be shown on the dive profile.\n" +"Cylinder changes are recorded by right-clicking at the appropriate point on the dive profile, 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" +"to be selected. Select the appropriate cylinder. The cylinder change is then shown 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" +"profile, then the cylinder change is also shown 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 in the image below.\n" msgstr "" #. type: Target for macro image -#: user-manual.txt:1761 +#: user-manual.txt:1729 #, no-wrap msgid "images/sidemount1.jpg" msgstr "images/sidemount1.jpg" #. type: Plain text -#: user-manual.txt:1764 +#: user-manual.txt:1732 msgid "" "This section gives an example of the versatility of _Subsurface_ as a dive " "logging tool." msgstr "" #. type: Title ==== -#: user-manual.txt:1767 +#: user-manual.txt:1735 #, no-wrap msgid "Semi-closed circuit rebreather (SCR) dives" msgstr "" #. type: Named 'icon' AttributeList argument for style 'icon' -#: user-manual.txt:1769 +#: user-manual.txt:1737 #, no-wrap msgid "images/halcyon_RB80.jpg" msgstr "images/halcyon_RB80.jpg" #. type: Plain text -#: user-manual.txt:1779 +#: user-manual.txt:1747 msgid "" -"Passive semi-closed rebreathers (pSCR) comprise a technical advance in " -"diving equipment that recirculates the breathing gas that a diver breathes, " -"while removing carbon dioxide from the exhaled gas. While a small amount " -"(typically a tenth) of the exhaled breathing gas is released into the water, " -"a small amount of fresh gas is released from the back gas cylinder " -"(typically containing nitrox). A diver, using a single cylinder of " -"breathing gas can therefore dive for much longer periods than using a " -"recreational open-circuit configuration. With pSCR equipment, a very small " -"amount of breathing gas is released every time the breather inhales. With " -"active SCR (aSCR) equipment, in contrast, a small amount of breathing gas is " -"released continuously from the back cylinder." +"Passive semi-closed rebreathers (pSCR) are a technical advance in diving " +"equipment that recirculates the breathing gas a diver uses, while removing " +"carbon dioxide from the exhaled gas. While a small amount (typically a " +"tenth) of the exhaled breathing gas is released into the water, a small " +"amount of fresh gas is released from the back gas cylinder (typically " +"containing nitrox). A diver using a single cylinder of breathing gas can " +"therefore dive for much longer periods than using a recreational open-" +"circuit configuration. With pSCR equipment, a very small amount of breathing " +"gas is released every time the diver inhales. With active SCR (aSCR) " +"equipment, in contrast, a small amount of breathing gas is released " +"continuously from the back cylinder." msgstr "" #. type: Plain text -#: user-manual.txt:1781 +#: user-manual.txt:1749 msgid "" -"To log pSCR dives, no special procedures are required, just the normal steps " +"To log pSCR dives, no special procedures are required. Use the normal steps " "outlined above:" msgstr "" #. type: Plain text -#: user-manual.txt:1783 +#: user-manual.txt:1751 msgid "Select pSCR in the _Dive Mode_ dropdown list on the *Info* panel." msgstr "" #. type: Plain text -#: user-manual.txt:1787 +#: user-manual.txt:1755 msgid "" "pSCR diving often involves gas changes, requiring an additional cylinder. " "Define all the appropriate cylinders as described above and indicate the " @@ -3507,48 +3531,48 @@ msgid "" msgstr "" #. type: Plain text -#: user-manual.txt:1792 +#: user-manual.txt:1760 msgid "" -"If a pSCR _Dive Mode_ has been selected, the dive ceiling for pSCR dives is " -"adjusted for the oxygen drop across the mouthpiece which often requires " +"If a pSCR _Dive Mode_ has been selected, the dive ceiling for that is " +"adjusted for the oxygen drop across the mouthpiece, which often requires " "longer decompression periods. Below is a dive profile of a pSCR dive using " "EAN36 on the back cylinder and oxygen for decompression. Note that this dive " "lasted over two hours." msgstr "" #. type: Target for macro image -#: user-manual.txt:1793 +#: user-manual.txt:1761 #, no-wrap msgid "images/pSCR_profile.jpg" msgstr "images/pSCR_profile.jpg" #. type: Title ==== -#: user-manual.txt:1798 +#: user-manual.txt:1766 #, no-wrap msgid "Closed circuit rebreather (CCR) dives" msgstr "" #. type: Named 'icon' AttributeList argument for style 'icon' -#: user-manual.txt:1800 +#: user-manual.txt:1768 #, no-wrap msgid "images/APD.jpg" msgstr "images/APD.jpg" #. type: Plain text -#: user-manual.txt:1805 +#: user-manual.txt:1773 msgid "" "Closed system rebreathers use advanced technology to recirculate gas that " -"has been breathed while doing two things to maintain a breathable oxygen " +"has been breathed. They also do two things to maintain a breathable oxygen " "concentration:" msgstr "" #. type: Plain text -#: user-manual.txt:1806 -msgid "remove carbon dioxide from the gas that has been exhaled" +#: user-manual.txt:1774 +msgid "remove carbon dioxide from the exhaled gas" msgstr "" #. type: Plain text -#: user-manual.txt:1815 +#: user-manual.txt:1783 msgid "" "regulate the oxygen concentration to remain within safe diving limits. The " "CCR interface of _Subsurface_ is currently experimental and under active " @@ -3557,42 +3581,42 @@ msgid "" "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 digital databases: one dive at a time." +"computer, but that it imports CCR dive logs in the same way it imports dive " +"log data from other digital databases: one dive at a time." msgstr "" #. type: Title ===== -#: user-manual.txt:1816 +#: user-manual.txt:1784 #, no-wrap msgid "Import a CCR dive" msgstr "" #. type: Plain text -#: user-manual.txt:1830 +#: user-manual.txt:1798 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 that section, the " "bottom right hand of the import dialogue contains a dropdown list (labled " -"_Filter:_) of appropriate devices that currently includes(Poseidon) MkVI or " -"APD log viewer files (import for other CCR equipment is under active " -"development). Having selected the appropriate CCR format and the directory " +"_Filter:_) of appropriate devices that currently include(Poseidon) MkVI or " +"APD log viewer files. Import for other CCR equipment is under active " +"development. 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. The selected dive is imported to the _Subsurface_ dive list." +"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, click the " +"_Open_ button at the bottom right hand of the universal import dialogue. " +"The selected dive is imported to the _Subsurface_ dive list." msgstr "" #. type: Title ===== -#: user-manual.txt:1831 +#: user-manual.txt:1799 #, no-wrap msgid "Displayed information for a CCR dive" msgstr "" #. type: Plain text -#: user-manual.txt:1841 +#: user-manual.txt:1809 msgid "" "_Partial pressures of gases_: The graph of oxygen partial pressure shows the " "information from the oxygen sensors of the CCR equipment. In contrast to " @@ -3606,68 +3630,68 @@ msgid "" msgstr "" #. type: Plain text -#: user-manual.txt:1843 +#: user-manual.txt:1811 msgid "For TWO O~2~ sensors the mean value of the two sensors are given." msgstr "" #. type: Plain text -#: user-manual.txt:1847 +#: user-manual.txt:1815 msgid "" "For THREE-sensor systems (e.g. APD), the mean value is also used. However " "differences of more than 0,1 bar in the simultaneous readings of different " -"sensors are treated as spurious. If one of the three sensors provides " -"spurious data, it is ignored." +"sensors are treated as false. If one of the three sensors provides false " +"data, it is ignored." msgstr "" #. type: Plain text -#: user-manual.txt:1849 +#: user-manual.txt:1817 msgid "" "If no sensor data are available, the pO~2~ value is assumed to be equal to " "the setpoint." msgstr "" #. type: Plain text -#: user-manual.txt:1851 +#: user-manual.txt:1819 msgid "The mean pO~2~ of the sensors is indicated with a green line," msgstr "" #. type: Plain text -#: user-manual.txt:1859 +#: user-manual.txt:1827 msgid "" "The oxygen setpoint values as well as the readings from the individual " "oxygen sensors can be shown. The display of additional CCR information is " -"turned on by checking the appropriate checkboxes in the _Preferences_ panel " +"turned on by checking the appropriate boxes in the _Preferences_ panel " "(accessible by selecting xref:S_CCR_options[_File -> Preferences -> " "Graph_]). This part of the _Preferences_ panel is shown in the image below, " "representing two checkboxes that modify the display of pO~2~ when the " -"appropriate toolbar button on the Dive Profile has been activated." +"appropriate toolbar button on the Dive Profile has been checked." msgstr "" #. type: Target for macro image -#: user-manual.txt:1860 +#: user-manual.txt:1828 #, no-wrap msgid "images/CCR_preferences_f20.jpg" msgstr "images/CCR_preferences_f20.jpg" #. type: Plain text -#: user-manual.txt:1867 +#: user-manual.txt:1835 msgid "" -"Checking any of these check boxes allows the display of additional oxygen-" -"related information whenever the pO~2~ toolbar button on the _Profile_ panel " -"is activated. The first checkbox allows the display of setpoint " -"information. This is a red line superimposed on the green oxygen partial " -"pressure graph and allows a comparison of the mean measured oxygen partial " -"pressure and the setpoint values, as shown below." +"Checking any of these boxes allows the display of additional oxygen-related " +"information whenever the pO~2~ toolbar button on the _Profile_ panel is " +"activated. The first checkbox allows the display of setpoint information. " +"This is a red line superimposed on the green oxygen partial pressure graph " +"and allows a comparison of the mean measured oxygen partial pressure and the " +"setpoint values, as shown below." msgstr "" #. type: Target for macro image -#: user-manual.txt:1868 +#: user-manual.txt:1836 #, no-wrap msgid "images/CCR_setpoint_f20.jpg" msgstr "images/CCR_setpoint_f20.jpg" #. type: Plain text -#: user-manual.txt:1872 +#: user-manual.txt:1840 msgid "" "The second checkbox allows the display of the data from each individual " "oxygen sensor of the CCR equipment. The data for each sensor is colour-coded " @@ -3675,22 +3699,22 @@ msgid "" msgstr "" #. type: Plain text -#: user-manual.txt:1874 +#: user-manual.txt:1842 msgid "Sensor 1: grey" msgstr "" #. type: Plain text -#: user-manual.txt:1875 +#: user-manual.txt:1843 msgid "Sensor 2: blue" msgstr "" #. type: Plain text -#: user-manual.txt:1876 +#: user-manual.txt:1844 msgid "Sensor 3: brown" msgstr "" #. type: Plain text -#: user-manual.txt:1880 +#: user-manual.txt:1848 msgid "" "The mean oxygen pO~2~ is indicated by the green line. This allows the direct " "comparison of data from each of the oxygen sensors, useful for detecting " @@ -3698,13 +3722,13 @@ msgid "" msgstr "" #. type: Target for macro image -#: user-manual.txt:1881 +#: user-manual.txt:1849 #, no-wrap msgid "images/CCR_sensor_data_f20.jpg" msgstr "images/CCR_sensor_data_f20.jpg" #. type: Plain text -#: user-manual.txt:1886 +#: user-manual.txt:1854 msgid "" "The setpoint data can be overlaid on the oxygen sensor data by activating " "both of the above check boxes. Partial pressures for nitrogen (and helium, " @@ -3712,7 +3736,7 @@ msgid "" msgstr "" #. type: Plain text -#: user-manual.txt:1890 +#: user-manual.txt:1858 msgid "" "_Events_: Several events are logged, e.g. switching the mouthpiece to open " "circuit. These events are indicated by yellow triangles and, if one hovers " @@ -3721,7 +3745,7 @@ msgid "" msgstr "" #. type: Plain text -#: user-manual.txt:1898 +#: user-manual.txt:1866 msgid "" "_Cylinder pressures_: Some CCR dive computers like the Poseidon MkVI record " "the pressures of the oxygen and diluent cylinders. The pressures of these " @@ -3729,18 +3753,18 @@ msgid "" "addition, start and end pressures for both oxygen and diluent cylinders are " "shown in the _Equipment Tab_. Below is a dive profile for a CCR dive, " "including an overlay of setpoint and oxygen sensor data, as well as the " -"cylinder pressure data. In this case there is good agreement from the " -"readings of the two oxygen sensors." +"cylinder pressure data. In this case there is agreement from the readings of " +"the two oxygen sensors." msgstr "" #. type: Target for macro image -#: user-manual.txt:1899 +#: user-manual.txt:1867 #, no-wrap msgid "images/CCR_dive_profile_f22.jpg" msgstr "images/CCR_dive_profile_f22.jpg" #. type: Plain text -#: user-manual.txt:1904 +#: user-manual.txt:1872 msgid "" "_Equipment-specific information_: Equipment-specific information gathered by " "_Subsurface_ is shown in the xref:S_ExtraDataTab[Extra data tab]. This may " @@ -3748,7 +3772,7 @@ msgid "" msgstr "" #. type: Plain text -#: user-manual.txt:1910 +#: user-manual.txt:1878 msgid "" "The deco ceiling calculated by Subsurface is not very accurate because the " "precise pressure of nitrogen in the loop can usually not be determined from " @@ -3760,28 +3784,28 @@ msgid "" msgstr "" #. type: Named 'icon' AttributeList argument for style 'icon' -#: user-manual.txt:1911 user-manual.txt:2094 +#: user-manual.txt:1879 user-manual.txt:2058 #, no-wrap msgid "images/icons/cceiling.jpg" msgstr "images/icons/cceiling.jpg" #. type: Plain text -#: user-manual.txt:1916 +#: user-manual.txt:1884 msgid "" -"The default colour of the computer-generated deco ceiling is white. However, " -"this can be set to red by checking the appropriate check box after selecting " -"_File -> Preferences -> Graph_. Below is a dive profile indicating the dive " -"computer-generated deco ceiling:" +"The default color of the computer-generated deco ceiling is white. This can " +"be set to red by checking the appropriate check box after selecting _File -> " +"Preferences -> Graph_. Below is a dive profile indicating the dive computer-" +"generated deco ceiling:" msgstr "" #. type: Target for macro image -#: user-manual.txt:1917 +#: user-manual.txt:1885 #, no-wrap msgid "images/CCR_dive_ceilingF22.jpg" msgstr "images/CCR_dive_ceilingF22.jpg" #. type: Plain text -#: user-manual.txt:1921 +#: user-manual.txt:1889 msgid "" "More equipment-specific information for downloading CCR dive logs for " "Poseidon MkVI and APD equipment can be found in xref:" @@ -3790,19 +3814,19 @@ msgid "" msgstr "" #. type: Title == -#: user-manual.txt:1922 +#: user-manual.txt:1890 #, no-wrap msgid "Obtaining more information about dives entered into the logbook" msgstr "" #. type: Title === -#: user-manual.txt:1924 +#: user-manual.txt:1892 #, no-wrap msgid "The *Info* tab (for individual dives)" msgstr "" #. type: Plain text -#: user-manual.txt:1931 +#: user-manual.txt:1899 msgid "" "The Info tab gives some summary information about a particular dive that has " "been selected in the *Dive List*. Useful information here includes the " @@ -3812,7 +3836,7 @@ msgid "" msgstr "" #. type: Plain text -#: user-manual.txt:1938 +#: user-manual.txt:1906 msgid "" "Gas consumption and SAC calculations: _Subsurface_ calculates SAC and Gas " "consumption taking in account gas incompressibility, particularly at tank " @@ -3821,13 +3845,13 @@ msgid "" msgstr "" #. type: Title === -#: user-manual.txt:1940 +#: user-manual.txt:1908 #, no-wrap msgid "The *Extra Data* tab (usually for individual dives)" msgstr "" #. type: Plain text -#: user-manual.txt:1948 +#: user-manual.txt:1916 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 " @@ -3839,60 +3863,67 @@ msgid "" msgstr "" #. type: Target for macro image -#: user-manual.txt:1949 +#: user-manual.txt:1917 #, no-wrap msgid "images/ExtraDataTab_f20.jpg" msgstr "images/ExtraDataTab_f20.jpg" #. type: Title === -#: user-manual.txt:1951 +#: user-manual.txt:1919 #, no-wrap msgid "The *Stats* tab (for groups of dives)" msgstr "" #. type: Plain text -#: user-manual.txt:1962 +#: user-manual.txt:1930 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 " +"figures for 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:1964 +#: user-manual.txt:1932 #, no-wrap msgid "The *Dive Profile*" msgstr "" #. type: Target for macro image -#: user-manual.txt:1966 +#: user-manual.txt:1934 #, no-wrap msgid "images/Profile2.jpg" msgstr "images/Profile2.jpg" #. type: Plain text -#: user-manual.txt:1977 +#: user-manual.txt:1945 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 " +"the left hand side that lets you control 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:" +"Profile is the graph of dive depth as a function of time. In addition to " +"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 colors:" msgstr "" #. type: delimited block | -#: user-manual.txt:1984 -#, no-wrap -msgid "" -"|*Colour*|*Descent speed (m/min)*|*Ascent speed (m/min)*\n" +#: user-manual.txt:1952 +#, fuzzy, 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" +msgid "" +"|*Color*|*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" @@ -3907,31 +3938,31 @@ msgstr "" "|Vert foncé|< 1.5|< 1.5\n" #. type: Plain text -#: user-manual.txt:1989 +#: user-manual.txt:1957 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 plotted as a grey line, indicating mean dive depth up " -"to a particular moment during the dive." +"graph. So users should see the depth of the deepest point and other peaks. " +"Mean depth is plotted as a grey line, indicating mean dive depth up to a " +"particular moment during the dive." msgstr "" #. type: Named 'icon' AttributeList argument for style 'icon' -#: user-manual.txt:1990 +#: user-manual.txt:1958 #, no-wrap msgid "images/icons/scale.jpg" msgstr "images/icons/scale.jpg" #. type: Plain text -#: user-manual.txt:1995 +#: user-manual.txt:1963 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." +"the dive profile increases the size of the dive profile to fill the area of " +"the panel." msgstr "" #. type: Plain text -#: user-manual.txt:1998 +#: user-manual.txt:1966 #, no-wrap msgid "" "*Water temperature* is displayed with its own blue line with temperature values\n" @@ -3939,80 +3970,80 @@ msgid "" msgstr "" #. type: Plain text -#: user-manual.txt:2005 +#: user-manual.txt:1973 msgid "" "The dive profile can include graphs of the *partial pressures* of O~2~, " "N~2~, 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." +"nitrogen in black, and 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:2006 +#: user-manual.txt:1974 #, no-wrap msgid "images/icons/O2.jpg" msgstr "images/icons/O2.jpg" #. type: Plain text -#: user-manual.txt:2010 +#: user-manual.txt:1978 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 " +"during the dive. This is shown below the dive depth and water temperature " "graphs." msgstr "" #. type: Named 'icon' AttributeList argument for style 'icon' -#: user-manual.txt:2011 +#: user-manual.txt:1979 #, no-wrap msgid "images/icons/N2.jpg" msgstr "images/icons/N2.jpg" #. type: Plain text -#: user-manual.txt:2014 +#: user-manual.txt:1982 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:2015 +#: user-manual.txt:1983 #, no-wrap msgid "images/icons/He.jpg" msgstr "images/icons/He.jpg" #. type: Plain text -#: user-manual.txt:2019 +#: user-manual.txt:1987 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." +"during the dive. This is only important to divers using Trimix, Helitrox or " +"similar breathing gasses." msgstr "" #. type: Plain text -#: user-manual.txt:2032 +#: user-manual.txt:2000 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 " +"manually entering the start and end pressures the graph, is not a straight " +"line. Like the depth graph, the slope of the tank pressure gives you " +"information about the momentary SAC rate (Surface Air Consumption) when " +"using an air integrated dive computer. Here the color coding is not " +"relative to some absolute values but relative to the average normalized 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:2033 +#: user-manual.txt:2001 #, no-wrap msgid "images/icons/Heartbutton.png" msgstr "images/icons/Heartbutton.png" #. type: Plain text -#: user-manual.txt:2037 +#: user-manual.txt:2005 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 " @@ -4020,87 +4051,85 @@ msgid "" msgstr "" #. type: Plain text -#: user-manual.txt:2045 +#: user-manual.txt:2012 #, 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" +" (100ft) – this way short or shallow dives are easily recognizable;\n" +"something free divers won’t care about.\n" msgstr "" #. type: Target for macro image -#: user-manual.txt:2046 +#: user-manual.txt:2012 #, no-wrap msgid "images/MeasuringBar.png" msgstr "images/MeasuringBar.png" #. type: Named 'icon' AttributeList argument for style 'icon' -#: user-manual.txt:2048 +#: user-manual.txt:2014 #, no-wrap msgid "images/icons/ruler.jpg" msgstr "images/icons/ruler.jpg" #. type: Plain text -#: user-manual.txt:2056 +#: user-manual.txt:2022 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." +"done by dragging the red dots to the two points on the dive profile that you " +"wish 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:2057 +#: user-manual.txt:2023 #, no-wrap msgid "images/icons/ShowPhotos.png" msgstr "images/icons/ShowPhotos.png" #. type: Plain text -#: user-manual.txt:2064 +#: user-manual.txt:2030 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 " +"shows 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:2093 +#: user-manual.txt:2057 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 " +"ceilings occur 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: Plain text -#: user-manual.txt:2099 +"available for download; for example none of the Suunto dive computers make " +"these 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’s 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’s 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 because _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 a specific deco stop. This feature lets dive " +"computers offer longer non-stop bottom times." +msgstr "" + +#. type: Plain text +#: user-manual.txt:2063 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 " @@ -4108,13 +4137,13 @@ msgid "" msgstr "" #. type: Named 'icon' AttributeList argument for style 'icon' -#: user-manual.txt:2100 +#: user-manual.txt:2064 #, no-wrap msgid "images/icons/ceiling1.jpg" msgstr "images/icons/ceiling1.jpg" #. type: Plain text -#: user-manual.txt:2105 +#: user-manual.txt:2069 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 " @@ -4123,13 +4152,13 @@ msgid "" msgstr "" #. type: Named 'icon' AttributeList argument for style 'icon' -#: user-manual.txt:2106 +#: user-manual.txt:2070 #, no-wrap msgid "images/icons/ceiling2.jpg" msgstr "images/icons/ceiling2.jpg" #. type: Plain text -#: user-manual.txt:2110 +#: user-manual.txt:2074 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 " @@ -4137,56 +4166,55 @@ msgid "" msgstr "" #. type: Named 'icon' AttributeList argument for style 'icon' -#: user-manual.txt:2111 +#: user-manual.txt:2075 #, no-wrap msgid "images/icons/ceiling3.jpg" msgstr "images/icons/ceiling3.jpg" #. type: Plain text -#: user-manual.txt:2115 +#: user-manual.txt:2079 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:2116 +#: user-manual.txt:2080 #, no-wrap msgid "images/Ceilings2.jpg" msgstr "images/Ceilings2.jpg" #. type: Named 'icon' AttributeList argument for style 'icon' -#: user-manual.txt:2118 +#: user-manual.txt:2082 #, no-wrap msgid "images/icons/ShowCylindersButton.jpg" msgstr "images/icons/ShowCylindersButton.jpg" #. type: Plain text -#: user-manual.txt:2124 +#: user-manual.txt:2088 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." +"represented as a colored bar at the bottom of the *Dive Profile*. In general " +"oxygen is represented by a green bar, nitrogen a yellow bar and helium 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:2125 +#: user-manual.txt:2089 #, no-wrap msgid "images/ShowCylinders_f20.jpg" msgstr "images/ShowCylinders_f20.jpg" #. type: Named 'icon' AttributeList argument for style 'icon' -#: user-manual.txt:2128 +#: user-manual.txt:2092 #, no-wrap msgid "images/tissues.jpg" msgstr "images/tissues.jpg" #. type: Plain text -#: user-manual.txt:2140 +#: user-manual.txt:2105 msgid "" "Display inert gas tissue pressures relative to ambient inert gas pressure " "(horizontal grey line). Tissue pressures are calculated using the Bühlmann " @@ -4194,24 +4222,23 @@ msgid "" "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 contrast, " -"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." +"divers doing planned decompression diving, efficient rates of offgassing 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 contrast, 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, at the position of the cursor on the dive profile." msgstr "" #. type: Target for macro image -#: user-manual.txt:2141 +#: user-manual.txt:2106 #, no-wrap msgid "images/tissuesGraph.jpg" msgstr "images/tissuesGraph.jpg" #. type: Plain text -#: user-manual.txt:2149 +#: user-manual.txt:2114 msgid "" "Gradient Factor settings strongly affect the calculated ceilings and their " "depths. For more information about Gradient factors, see the section on " @@ -4224,55 +4251,55 @@ msgid "" msgstr "" #. type: Plain text -#: user-manual.txt:2151 +#: user-manual.txt:2116 #, 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 " ** http://www.tek-dive.com/portal/upload/M-Values.pdf[Understanding M-values by Erik Baker, _Immersed_ Vol. 3, No. 3.]\n" #. type: Plain text -#: user-manual.txt:2153 +#: user-manual.txt:2118 #, 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 " ** 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" #. type: Title === -#: user-manual.txt:2155 +#: user-manual.txt:2120 #, no-wrap msgid "The Dive Profile context menu" msgstr "" #. type: Plain text -#: user-manual.txt:2173 +#: user-manual.txt:2139 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." +"the mouse cursor is over the Dive Profile panel. The menu lets you create " +"Bookmarks, 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, with the time of the event set by " +"where the mouse cursor was when the right mouse button was first clicked to " +"bring up the menu. Gas Change events involve a selection of which gas is " +"being switched TO. The list of choices is based on the available gases " +"defined in the *Equipment* Tab. Setpoint change events open a dialog letting " +"you choose the next setpoint value. As in the planner, a setpoint value of " +"zero shows the diver is breathing from an open circuit system while any non-" +"zero value shows 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:2175 +#: user-manual.txt:2141 #, no-wrap msgid "The *Information Box*" msgstr "" #. type: Plain text -#: user-manual.txt:2185 +#: user-manual.txt:2150 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 " +"The Information box displays a large range of information about 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 " @@ -4282,47 +4309,46 @@ msgid "" msgstr "" #. type: Target for macro image -#: user-manual.txt:2186 +#: user-manual.txt:2151 #, no-wrap msgid "images/InfoBox2.jpg" msgstr "images/InfoBox2.jpg" #. type: Plain text -#: user-manual.txt:2203 +#: user-manual.txt:2168 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." +"When 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 shown 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). Moving the cursor " +"horizontally lets the Information Box 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:2206 +#: user-manual.txt:2171 msgid "" -"The user has control over the display of several statistics, represented as " -"four buttons on the left of the profile panel. These are:" +"The user has control over the display of some statistics, shown as four " +"buttons on the left of the profile panel. These are:" msgstr "" #. type: Named 'icon' AttributeList argument for style 'icon' -#: user-manual.txt:2207 +#: user-manual.txt:2172 #, no-wrap msgid "images/icons/MOD.jpg" msgstr "images/icons/MOD.jpg" #. type: Plain text -#: user-manual.txt:2216 +#: user-manual.txt:2181 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 " @@ -4330,115 +4356,115 @@ msgid "" "oxygen) it is around 57 m if a maximum pO~2~ of 1.4 is specified in the " "*Preferences* section (select _File_ -> Preferences -> Graph_ and edit the " "text box _Max pO~2~ when showing MOD_. Below the MOD there is a markedly " -"increased risk of exposure to the dangers associated with oxygen toxicity." +"increased risk of exposure to the dangers of oxygen toxicity." msgstr "" #. type: Named 'icon' AttributeList argument for style 'icon' -#: user-manual.txt:2217 +#: user-manual.txt:2182 #, no-wrap msgid "images/icons/NDL.jpg" msgstr "images/icons/NDL.jpg" #. type: Plain text -#: user-manual.txt:2229 +#: user-manual.txt:2194 msgid "" "Clicking this button causes the Information Box to display either 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. TTS is calculated assuming an ascent surface air " -"consumption (SAC) for the gas currently used. Even if the profile contains " -"several gas switches, TTS at a specific moment during the dive is calculated " -"using the current gas. For TTS longer than 2 hours, it is not accurately " -"calculated and Subsurface only indicates _TTS > 2h_." +"appears). Once a diver 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. TTS is calculated assuming an ascent " +"surface air consumption (SAC) for the gas currently used. Even if the " +"profile contains several gas switches, TTS at a specific moment during the " +"dive is calculated using the current gas. TTS longer than 2 hours is not " +"accurately calculated and Subsurface only indicates _TTS > 2h_." msgstr "" #. type: Named 'icon' AttributeList argument for style 'icon' -#: user-manual.txt:2230 +#: user-manual.txt:2195 #, no-wrap msgid "images/icons/SAC.jpg" msgstr "images/icons/SAC.jpg" #. type: Plain text -#: user-manual.txt:2239 +#: user-manual.txt:2204 msgid "" "Clicking this button causes the Information Box to display the *Surface Air " -"Consumption (SAC)*. SAC is an indication of the surface-normalised " +"Consumption (SAC)*. SAC is an indication of the surface-normalized " "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." +"of breathing gas consumption rate independent of the depth of the dive, so " +"the respiratory rates of different dives can be compared. The units for SAC " +"is liters/min or cubic ft/min." msgstr "" #. type: Named 'icon' AttributeList argument for style 'icon' -#: user-manual.txt:2240 +#: user-manual.txt:2205 #, no-wrap msgid "images/icons/EAD.jpg" msgstr "images/icons/EAD.jpg" #. type: Plain text -#: user-manual.txt:2255 +#: user-manual.txt:2220 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." +"These are important to divers breathe 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:2257 +#: user-manual.txt:2222 msgid "" "Figure (*B*) above shows an information box with a nearly complete set of " "data." msgstr "" #. type: Title ==== -#: user-manual.txt:2259 +#: user-manual.txt:2224 #, no-wrap msgid "The Gas Pressure Bar Graph" msgstr "" #. type: Plain text -#: user-manual.txt:2266 +#: user-manual.txt:2231 msgid "" -"On the left of the *Information Box* is a vertical bar graph indicating the " +"On the left of the *Information Box* is a vertical bar graph showing 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 " +"dive_. It is shown 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:2267 +#: user-manual.txt:2232 #, no-wrap msgid "images/GasPressureBarGraph.jpg" msgstr "images/GasPressureBarGraph.jpg" #. type: Plain text -#: user-manual.txt:2273 +#: user-manual.txt:2238 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 " +"light green area showing 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:2279 +#: user-manual.txt:2244 msgid "" "The horizontal black line underneath the light green margin indicates the " "equilibrium pressure of the inert gases inhaled by the diver, usually " @@ -4449,7 +4475,7 @@ msgid "" msgstr "" #. type: Plain text -#: user-manual.txt:2283 +#: user-manual.txt:2248 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 " @@ -4457,7 +4483,7 @@ msgid "" msgstr "" #. type: Plain text -#: user-manual.txt:2288 +#: user-manual.txt:2253 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 " @@ -4466,39 +4492,39 @@ msgid "" msgstr "" #. type: Plain text -#: user-manual.txt:2292 +#: user-manual.txt:2257 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 " +"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:2295 +#: user-manual.txt:2260 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." +"These five values are shown on the left in the graph above. The way the Gas " +"Pressure Bar Graph changes during a dive can be seen on the right hand side " +"of the above figure for a diver using EAN32." msgstr "" #. type: Plain text -#: user-manual.txt:2298 +#: user-manual.txt:2263 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." +"Graph *A* indicates the start of a dive with the 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:2301 +#: user-manual.txt:2266 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." +"tissue compartments have had time to respond to the descent, so their gas " +"pressures are far below the equilibrium gas pressure." msgstr "" #. type: Plain text -#: user-manual.txt:2306 +#: user-manual.txt:2271 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 " @@ -4508,18 +4534,18 @@ msgid "" msgstr "" #. type: Plain text -#: user-manual.txt:2312 +#: user-manual.txt:2277 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 " +"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 " +"exceed that of the total gas pressure and approach 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:2317 +#: user-manual.txt:2282 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 " @@ -4529,184 +4555,180 @@ msgid "" msgstr "" #. type: Title == -#: user-manual.txt:2320 +#: user-manual.txt:2285 #, no-wrap -msgid "Organising the logbook (Manipulating groups of dives)" +msgid "Organizing the logbook (Manipulating groups of dives)" msgstr "" #. type: Title === -#: user-manual.txt:2322 +#: user-manual.txt:2287 #, no-wrap msgid "The Dive List context menu" msgstr "" #. type: Plain text -#: user-manual.txt:2326 +#: user-manual.txt:2291 msgid "" -"Several actions on either a single dive or a group of dives can be performed " -"using the Dive List Context Menu, found by selecting either a single dive or " -"a group of dives and then right-clicking." +"Several actions on either a single dive, or a group of dives, can be " +"performed using the Dive List Context Menu. It is found by selecting either " +"a single dive or a group of dives and then right-clicking." msgstr "" #. TODO: NEEDS REPLACEMENT #. type: Target for macro image -#: user-manual.txt:2328 +#: user-manual.txt:2293 #, no-wrap msgid "images/ContextMenu.jpg" msgstr "images/ContextMenu.jpg" #. type: Plain text -#: user-manual.txt:2331 -msgid "The context menu is used in many manipulations described below." +#: user-manual.txt:2296 +msgid "The context menu is used in many functions described below." msgstr "" #. type: Title ==== -#: user-manual.txt:2332 +#: user-manual.txt:2297 #, no-wrap -msgid "Customising the columns showed in the *Dive List* panel" +msgid "Customizing the columns showed in the *Dive List* panel" msgstr "" #. type: Target for macro image -#: user-manual.txt:2334 +#: user-manual.txt:2299 #, no-wrap msgid "images/DiveListOptions.jpg" msgstr "images/DiveListOptions.jpg" #. type: Plain text -#: user-manual.txt:2342 +#: user-manual.txt:2307 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 (reflected by the check symbols) and the list is immediately updated. " -"Preferences for information shown in the *Dive List* are saved and used when " -"_Subsurface_ is re-opened." +"Select an item to be shown in the *Dive List* or be deleted (reflected by " +"the check symbols) and the list is immediately updated. Preferences for " +"information shown in the *Dive List* are saved and used when _Subsurface_ is " +"re-opened." msgstr "" #. type: Title === -#: user-manual.txt:2344 +#: user-manual.txt:2309 #, no-wrap msgid "Renumbering the dives" msgstr "" #. type: Plain text -#: user-manual.txt:2356 +#: user-manual.txt:2321 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." +"sequence numbers) to recent dives (higher sequence numbers). Numbering of " +"dives is not always consistent. For instance, when non-recent dives are " +"added, correct 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. So you may need to renumber the dives. Do this by " +"selecting (from the Main Menu) _Log -> Renumber_. Users are given a choice " +"of the lowest sequence number to be used. This results in new sequence " +"numbers (based on date/time) for the dives in the *Dive List* panel." msgstr "" #. type: Plain text -#: user-manual.txt:2361 +#: user-manual.txt:2326 msgid "" -"One can also renumber a few selected dives in the dive list. Select the " +"You can also renumber a few selected dives in the dive list. Select the " "dives that need renumbering. Right-click on the selected list and use the " "Dive List Context Menu to perform the renumbering. A popup window appears " -"requiring the user to specify the starting number for the renumbering " -"process." +"letting the user specify the starting number for the process." msgstr "" #. type: Title === -#: user-manual.txt:2363 +#: user-manual.txt:2328 #, no-wrap msgid "Grouping dives into trips and manipulating trips" msgstr "" #. type: Plain text -#: user-manual.txt:2371 +#: user-manual.txt:2336 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 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 " +"can group dives into _trips_. It does this by grouping dives that have date/" +"times not separated in time by more than two days, so 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):" +"dive list of five dive trips (*B*, on the right):" msgstr "" #. type: Target for macro image -#: user-manual.txt:2372 +#: user-manual.txt:2337 #, no-wrap msgid "images/Group2.jpg" msgstr "images/Group2.jpg" #. type: Plain text -#: user-manual.txt:2378 +#: user-manual.txt:2343 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) select _Log -> Autogroup_. The *Dive List* panel " -"now shows only the titles for the trips." +"having to scan a long lists of dives. To group the dives in a dive list, " +"(from the Main Menu) select _Log -> Autogroup_. The *Dive List* panel now " +"shows only the titles for the trips." msgstr "" #. type: Title ==== -#: user-manual.txt:2379 +#: user-manual.txt:2344 #, no-wrap msgid "Editing the title and associated information for a particular trip" msgstr "" #. type: Plain text -#: user-manual.txt:2392 +#: user-manual.txt:2357 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 *Notes* " -"panel. Here one can add or edit information about the date/time, the trip " +"panel. Here you 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 " +"dive company that was used, the general weather and surface conditions " "during the trip, etc.). After entering this information, 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 the edited information." msgstr "" #. type: Title ==== -#: user-manual.txt:2393 +#: user-manual.txt:2358 #, no-wrap msgid "Viewing the dives during a particular trip" msgstr "" #. type: Plain text -#: user-manual.txt:2398 +#: user-manual.txt:2363 msgid "" -"Once the dives have been grouped into trips, users can expand one or more " +"Once the dives have been grouped into trips, you 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." +"expands the selected trip, revealing individual dives done during the trip." msgstr "" #. type: Title ==== -#: user-manual.txt:2399 +#: user-manual.txt:2364 #, no-wrap msgid "Collapsing or expanding dive information for different trips" msgstr "" #. type: Plain text -#: user-manual.txt:2404 +#: user-manual.txt:2369 msgid "" "After selecting a particular trip in the dive list, the context menu allows " -"several possibilities to expand or collapse dives within trips. This " -"includes expanding all trips and collapsing all trips." +"several options to expand or collapse dives within trips. This includes " +"expanding all trips and collapsing all trips." msgstr "" #. type: Title ==== -#: user-manual.txt:2405 +#: user-manual.txt:2370 #, no-wrap msgid "Merging dives from more than one trip into a single trip" msgstr "" #. type: Plain text -#: user-manual.txt:2410 +#: user-manual.txt:2375 msgid "" "After selecting a trip title, the context menu allows the merging of trips " "by either merging the selected trip with the trip below or with the trip " @@ -4714,75 +4736,73 @@ msgid "" msgstr "" #. type: Title ==== -#: user-manual.txt:2411 +#: user-manual.txt:2376 #, no-wrap msgid "Splitting a single trip into more than one trip" msgstr "" #. type: Plain text -#: user-manual.txt:2421 +#: user-manual.txt:2385 msgid "" -"If a trip includes ten dives, the user can split this trip into two trips " -"(trip 1: top 4 dives; trip 2: bottom 6 dives) by selecting and right-" -"clicking the top four dives. The resulting context menu allows the user to " -"create a new trip by choosing the option *Create new trip above*. The top " -"four 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):" +"If a trip includes ten dives, you can split this trip into two trips (trip " +"1: top 4 dives; trip 2: bottom 6 dives) by selecting and right-clicking the " +"top four dives. The resulting context menu lets the user create a new trip " +"by choosing the option *Create new trip above*. The top four dives are then " +"grouped into a separate trip. The figures below show 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:2422 +#: user-manual.txt:2386 #, no-wrap msgid "images/SplitDive3a.jpg" msgstr "images/SplitDive3a.jpg" #. type: Title === -#: user-manual.txt:2424 +#: user-manual.txt:2388 #, no-wrap msgid "Manipulating single dives" msgstr "" #. type: Title ==== -#: user-manual.txt:2426 +#: user-manual.txt:2390 #, no-wrap msgid "Delete a dive from the dive log" msgstr "" #. type: Plain text -#: user-manual.txt:2433 +#: user-manual.txt:2397 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." +"clicking them to bring up the context menu, 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:2434 +#: user-manual.txt:2398 #, no-wrap msgid "Unlink a dive from a trip" msgstr "" #. type: Plain text -#: user-manual.txt:2441 +#: user-manual.txt:2405 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 or below the trip to which they belonged, depending " -"on the date and time of the unlinked dive." +"You can unlink dives from the trip to which they belong. 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 or below the trip to which they belonged, depending on the date and " +"time of the unlinked dive." msgstr "" #. type: Title ==== -#: user-manual.txt:2442 +#: user-manual.txt:2406 #, no-wrap msgid "Add a dive to the trip immediately above" msgstr "" #. type: Plain text -#: user-manual.txt:2447 +#: user-manual.txt:2411 msgid "" "Selected dives can be moved from the trip to which they belong and placed " "within a separate trip. To do this, select and right-click the dive(s) to " @@ -4790,57 +4810,57 @@ msgid "" msgstr "" #. type: Title ==== -#: user-manual.txt:2448 +#: user-manual.txt:2412 #, no-wrap msgid "Shift the start time of dive(s)" msgstr "" #. type: Plain text -#: user-manual.txt:2459 +#: user-manual.txt:2422 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, 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 ealier " -"or later." +"Sometimes it’s necessary to adjust the start time of a dive. This may apply " +"to situations where dives are done in different time zones or when the dive " +"computer has a wrong time. To do this, select and right-click the dive(s) to " +"be adjusted. This brings up the context menu on which the *Shift times* " +"option should be selected. You must then specify the time (in hours and " +"minutes) by which the dives should be adjusted and click on the option of " +"whether the time adjustment should be earlier or later." msgstr "" #. type: Title ==== -#: user-manual.txt:2460 +#: user-manual.txt:2423 #, no-wrap msgid "Merge dives into a single dive" msgstr "" #. type: Plain text -#: user-manual.txt:2470 +#: user-manual.txt:2433 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 *Notes* panel to reflect events or conditions that apply to the merged " -"dive. The figure below shows the depth profile of two dives that were merged:" +"Sometimes a dive is briefly interrupted, for example, if a diver returns to " +"the surface for a few minutes. That results in two or more dives being " +"recorded by the dive computer and appearing as different dives in the *Dive " +"List* panel. You 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 *Notes* panel to reflect events or conditions that apply " +"to the merged dive. The figure below shows the depth profile of two dives " +"that were merged:" msgstr "" #. type: Target for macro image -#: user-manual.txt:2471 +#: user-manual.txt:2434 #, no-wrap msgid "images/MergedDive.png" msgstr "images/MergedDive.png" #. type: Title ==== -#: user-manual.txt:2473 +#: user-manual.txt:2436 #, no-wrap msgid "Undo dive manipulations" msgstr "" #. type: Plain text -#: user-manual.txt:2479 +#: user-manual.txt:2442 msgid "" "Important actions on dives or trips, described above, can be undone or " "redone. This includes: _delete dives_, _merge dives_, _renumber dives_ and " @@ -4850,85 +4870,84 @@ msgid "" msgstr "" #. type: Title === -#: user-manual.txt:2482 +#: user-manual.txt:2445 #, no-wrap msgid "Filtering the dive list" msgstr "" #. type: Plain text -#: user-manual.txt:2488 +#: user-manual.txt:2451 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." +"The dives in the *Dive List* panel can be filtered, so you 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 lets you 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:2496 +#: user-manual.txt:2459 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 (see image below). The " "_Filter Panel_ can be reset (i.e. all current filters cleared) by selecting " -"the *yellow angled arrow*. The _Filter Panel_ may also be minimised by " -"selecting the *green up-arrow\". 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 *red button* " +"the *yellow angled arrow*. The _Filter Panel_ may also be minimized by " +"selecting the *green up-arrow\". When minimized, only these three icons are " +"shown. The panel can be maximized by clicking the same icon that minimized " +"it. The filter may also be reset and closed by selecting the *red button* " "with the white cross." msgstr "" #. type: Target for macro image -#: user-manual.txt:2497 +#: user-manual.txt:2460 #, no-wrap msgid "images/Filterpanel.jpg" msgstr "images/Filterpanel.jpg" #. type: Plain text -#: user-manual.txt:2506 +#: user-manual.txt:2469 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 " +"(buddy / divemaster), dive site and dive suit. Each of these 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." +"filter tool, allowing the listing of only some attributes within that check " +"list. For instance, typing \"_ca_\" in the filter text box above the tags " +"check list, results in the list being reduced to \"_cave_\" and \"_cavern_" +"\". Filtering the check list helps to rapidly find search terms for " +"filtering the dive list." msgstr "" #. type: Plain text -#: user-manual.txt:2514 +#: user-manual.txt:2477 msgid "" "To activate filtering of the dive list, check at least one check box in one " "of the four check lists. The dive list is then shortened to include only the " "dives that pertain to the 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 " +"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:2516 +#: user-manual.txt:2479 #, no-wrap msgid "Exporting the dive log or parts of the dive log" msgstr "" #. type: Plain text -#: user-manual.txt:2519 -msgid "" -"There are two routes for the export of dive information from Subsurface:" +#: user-manual.txt:2482 +msgid "There are two ways to export dive information from Subsurface:" msgstr "" #. type: Plain text -#: user-manual.txt:2521 +#: user-manual.txt:2484 msgid "Export dive information to _Facebook_" msgstr "Exporter les informations de plongée vers _Facebook_" #. type: Plain text -#: user-manual.txt:2523 +#: user-manual.txt:2486 msgid "" "xref:S_Export_other[Export dive information to other destinations or formats]" msgstr "" @@ -4936,22 +4955,31 @@ msgstr "" "destinations ou formats]" #. type: Title === -#: user-manual.txt:2525 +#: user-manual.txt:2488 #, no-wrap msgid "Exporting dive information to _Facebook_" msgstr "Export des informations de plongée vers _Facebook_" #. type: Plain text -#: user-manual.txt:2534 +#: user-manual.txt:2497 +#, fuzzy +#| msgid "" +#| "Export of dives to _Facebook_ is handled differently from other types of " +#| "export because a connection to _Facebook_ is required, needing a " +#| "_Facebook_ userID and password. If, from the *Main Menu*, one selects " +#| "_File -> Preferences -> Facebook_, a login screen is presented (image *A* " +#| "to the left, below). Provide a _Facebook_ userID and password. Once a " +#| "successful login to _Facebook_ has been achieved, the panel in image *B*, " +#| "below is presented, including a _Disconnect from Facebook_ button to " +#| "close the _Facebook_ connection." msgid "" "Export of dives to _Facebook_ is handled differently from other types of " "export because a connection to _Facebook_ is required, needing a _Facebook_ " -"userID and password. If, from the *Main Menu*, one selects _File -> " -"Preferences -> Facebook_, a login screen is presented (image *A* to the " -"left, below). Provide a _Facebook_ userID and password. Once a successful " -"login to _Facebook_ has been achieved, the panel in image *B*, below is " -"presented, including a _Disconnect from Facebook_ button to close the " -"_Facebook_ connection." +"userID and password. If, from the *Main Menu*, you select _File -> " +"Preferences -> Facebook_, a login screen comes up. (image *A* to the left, " +"below). Provide a _Facebook_ userID and password. Once logged into to " +"_Facebook_ , the panel in image *B*, below is shown, including a _Disconnect " +"from Facebook_ button to close the _Facebook_ connection." msgstr "" "L'export des plongées vers _Facebook_ est géré différemment des autres types " "d'export car une connexion vers _Facebook_ est nécessaire, nécessitant un " @@ -4963,39 +4991,56 @@ msgstr "" "Facebook_ pour fermer la connexion _Facebook_." #. type: Target for macro image -#: user-manual.txt:2535 +#: user-manual.txt:2498 #, no-wrap msgid "images/facebook1_f20.jpg" msgstr "images/facebook1_f20.jpg" #. type: Plain text -#: user-manual.txt:2540 +#: user-manual.txt:2503 msgid "" -"From the _Subsurface_ window it is easy to determine whether _Subsurface_ " -"has a valid connection to _Facebook_ From the *Main Menu*, select _Share on -" -"> Facebook_ (image *A*, below). Normally, the _Facebook_ option is greyed " -"out. But if there is a connection to _Facebook_, this option is active (i.e. " -"in black colour and can be selected)." +"From the _Subsurface_ window it’s easy to determine whether _Subsurface_ has " +"a valid connection to _Facebook_ From the *Main Menu*, select _Share on -> " +"Facebook_ (image *A*, below). Normally, the _Facebook_ option is greyed out. " +"But if there is a connection to _Facebook_, this option is active (i.e. in " +"black color and can be selected)." msgstr "" #. type: Plain text -#: user-manual.txt:2550 -msgid "" -"Having established a login to _Facebook_, transfer of a dive profile to " -"one's _Facebook_ timeline is easy. Ensure that the dive to be transfered to " -"the timeline is depicted in the _Subsurface_ *Dive Profile* panel. If, from " -"the *Main Menu*, one selects _Share on -> Facebook_ (see image *A* below), a " -"dialogue is shown, determining the amount of additional information " -"transferred with the dive profile (image *B*, below). In order to transfer a " -"dive profile to _Facebook_, the name of a _Facebook_ album needs to be " -"provided. The checkboxes on the lefthand side allow one to determine how " -"much additional information should be transferred with the dive profile. " -"This information is shown in the text box on the right hand side of the " -"panel (image *B*, below). One can easily edit the message that will be " -"posted with the dive profile. Having specified the additional information " -"and verified the text, select the _OK_ button that triggers the transfer to " -"_Facebook_. After a while, an acknowledgement dialogue appears, indicating " -"successful transfer to _Facebook_." +#: user-manual.txt:2514 +#, fuzzy +#| msgid "" +#| "Having established a login to _Facebook_, transfer of a dive profile to " +#| "one's _Facebook_ timeline is easy. Ensure that the dive to be transfered " +#| "to the timeline is depicted in the _Subsurface_ *Dive Profile* panel. If, " +#| "from the *Main Menu*, one selects _Share on -> Facebook_ (see image *A* " +#| "below), a dialogue is shown, determining the amount of additional " +#| "information transferred with the dive profile (image *B*, below). In " +#| "order to transfer a dive profile to _Facebook_, the name of a _Facebook_ " +#| "album needs to be provided. The checkboxes on the lefthand side allow one " +#| "to determine how much additional information should be transferred with " +#| "the dive profile. This information is shown in the text box on the right " +#| "hand side of the panel (image *B*, below). One can easily edit the " +#| "message that will be posted with the dive profile. Having specified the " +#| "additional information and verified the text, select the _OK_ button that " +#| "triggers the transfer to _Facebook_. After a while, an acknowledgement " +#| "dialogue appears, indicating successful transfer to _Facebook_." +msgid "" +"Having established a login to _Facebook_, transferring a dive profileto a " +"_Facebook_ timeline is easy. Be sure the dive to be transferred to the " +"timeline is shown in the _Subsurface_ *Dive Profile* panel. If, from the " +"*Main Menu*, you select _Share on -> Facebook_ (see image *A* below), a " +"dialogue box is shown, determining the amount of additional information " +"transferred along with the dive profile (image *B*, below). To transfer a " +"dive profile to _Facebook_, the name of a _Facebook_ album is needed. The " +"checkboxes on the left hand side let you decide how much additional " +"information should be transferred with the dive profile. This information is " +"shown in the text box on the right hand side of the panel (image *B*, " +"below). You can easily edit the message that will be posted with the dive " +"profile. After specifying the additional information and verifying the " +"text, select the _OK_ button that triggers the transfer to _Facebook_. After " +"the transfer is done, an acknowledgement dialogue appears, indicating it was " +"successful." msgstr "" "Une fois qu'une connexion à _Facebook_ est établie, transférer un profil de " "plongée vers _Facebook_ est facile. Assurez-vous que la plongée à transférer " @@ -5014,13 +5059,18 @@ msgstr "" "moment, une fenêtre apparait indiquant le succès du transfert." #. type: Plain text -#: user-manual.txt:2557 -msgid "" -"Both the album created and the post to one's timeline will be marked as " -"private. In order for friends to be able to see the post, change its " -"permissions from a regular Facebook login either in a browser or a Facebook " -"app. While this is an extra step this is the better solution to avoid having " -"unwanted posts in one's public timeline." +#: user-manual.txt:2519 +#, fuzzy +#| msgid "" +#| "Both the album created and the post to one's timeline will be marked as " +#| "private. In order for friends to be able to see the post, change its " +#| "permissions from a regular Facebook login either in a browser or a " +#| "Facebook app. While this is an extra step this is the better solution to " +#| "avoid having unwanted posts in one's public timeline." +msgid "" +"Both the album created and the post to your timeline will be marked as " +"private. In order for friends to be able to see it, change its permissions " +"from a regular Facebook login either in a browser or a Facebook app." msgstr "" "À la fois l'album créé et la publication sur votre ligne temporelle seront " "marquées comme privés. Pour que vos amis puissent voir la publication, " @@ -5030,13 +5080,13 @@ msgstr "" "publications non désirées sur votre ligne temporelle publique." #. type: Target for macro image -#: user-manual.txt:2558 +#: user-manual.txt:2520 #, no-wrap msgid "images/facebook2_f20.jpg" msgstr "images/facebook2_f20.jpg" #. type: Plain text -#: user-manual.txt:2562 +#: user-manual.txt:2524 msgid "" "If required, then close the _Facebook_ connection by either closing " "_Subsurface_ or by selecting _File -> Preferences -> Facebook_ from the Main " @@ -5048,15 +5098,16 @@ msgstr "" "préférences Facebook." #. type: Title === -#: user-manual.txt:2564 -#, no-wrap -msgid "Export dive information to other destinations or formats" -msgstr "" +#: user-manual.txt:2526 +#, fuzzy, no-wrap +#| msgid "xref:S_Export_other[Export dive information to other destinations or formats]" +msgid "Export dive information to other destinations or formats" +msgstr "xref:S_Export_other[Exporter des informations de plongée vers d'autres destinations ou formats]" #. type: Plain text -#: user-manual.txt:2569 +#: user-manual.txt:2531 msgid "" -"For non-_Facebook exports_, the export function can be reached by selecting " +"For non-_Facebook exports_, the export function can be found 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 " @@ -5064,24 +5115,24 @@ msgid "" msgstr "" #. type: Target for macro image -#: user-manual.txt:2570 +#: user-manual.txt:2532 #, no-wrap msgid "images/Export_f20.jpg" msgstr "images/Export_f20.jpg" #. type: Plain text -#: user-manual.txt:2573 +#: user-manual.txt:2535 msgid "A dive log or part of it can be saved in three formats:" msgstr "" #. type: Plain text -#: user-manual.txt:2575 +#: user-manual.txt:2537 msgid "" "_Subsurface XML_ format. This is the native format used by _Subsurface_." msgstr "" #. type: Plain text -#: user-manual.txt:2579 +#: user-manual.txt:2541 msgid "" "Universal Dive Data Format (_UDDF_). Refer to _http://uddf.org_ for more " "information. UDDF is a generic format that enables communication among many " @@ -5089,24 +5140,24 @@ msgid "" msgstr "" #. type: Plain text -#: user-manual.txt:2583 +#: user-manual.txt:2545 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_." +"_Divelogs.de_, you need a user-ID as well as a password for _Divelogs.de_. " +"Log into _http://en.divelogs.de_ and subscribe to this service to upload " +"dive log data from _Subsurface_." msgstr "" #. type: Plain text -#: user-manual.txt:2587 +#: user-manual.txt:2549 msgid "" -"_DiveShare_ is also a dive log repository on the Internet focusing on the " -"recreational dives. In order to upload dives one has to provide a used ID, " -"so registration with _http://scubadiveshare.com_ is required." +"_DiveShare_ is also a dive log repository on the Internet focusing on " +"recreational dives. To upload dives, you need a user ID, so registration " +"with _http://scubadiveshare.com_ is required." msgstr "" #. type: Plain text -#: user-manual.txt:2592 +#: user-manual.txt:2554 msgid "" "_CSV dive details_, that includes the most critical information of the dive " "profile. Included information of a dive is: dive number, date, time, buddy, " @@ -5115,7 +5166,7 @@ msgid "" msgstr "" #. type: Plain text -#: user-manual.txt:2595 +#: user-manual.txt:2557 msgid "" "_CSV dive profile_, that includes a large amount of detail for each dive, " "including the depth profile, temperature and pressure information of each " @@ -5123,7 +5174,7 @@ msgid "" msgstr "" #. type: Plain text -#: user-manual.txt:2608 +#: user-manual.txt:2570 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 " @@ -5133,43 +5184,43 @@ msgid "" "pressure, gas pressures and MOD. The HTML export contains a search option to " "search the dive log. HTML export is specified on the second tab of the " "Export dialog (image *B* above). A typical use of this option is to export " -"all one's dives to a smartphone or a tablet where it would serve as a very " -"portable record of dives useful for dive companies that wish to verify the " -"dive history of a diver, often doing away with the need to carry one's " -"original logbook with one when doing dives with dive companies." +"all one's dives to a smartphone or a tablet where it would serve as a " +"portable record of dives. That is useful for dive companies that wish to " +"verify the dive history of a diver, often doing away with the need to carry " +"an original logbook when doing dives with dive companies." msgstr "" #. type: Plain text -#: user-manual.txt:2613 +#: user-manual.txt:2575 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. If one " -"selects any of the dive sites on the map, a summary of the dive is available " +"some information about it are indicated. This map is not editable. If you " +"select any of the dive sites on the map, a summary of the dive is available " "in text, as shown in the image below." msgstr "" #. type: Target for macro image -#: user-manual.txt:2614 +#: user-manual.txt:2576 #, no-wrap msgid "images/mapview_f20.jpg" msgstr "images/mapview_f20.jpg" #. type: Plain text -#: user-manual.txt:2621 +#: user-manual.txt:2583 msgid "" "_Image depths_, which creates a text file that contains the file names of " "all photos or images attached to any of the selected dives in the _Dive " -"List_, together with the depth under water where of each of those photos " -"were taken." +"List_, together with the depth underwater where of each of those photos was " +"taken." msgstr "" #. type: Plain text -#: user-manual.txt:2623 +#: user-manual.txt:2585 msgid "_General Settings_, under the HTML tab, provides the following options:" msgstr "" #. type: Plain text -#: user-manual.txt:2631 +#: user-manual.txt:2593 #, no-wrap msgid "" "** Subsurface Numbers: if this option is checked, the dive(s) are exported with the\n" @@ -5182,58 +5233,57 @@ msgid "" msgstr "" #. type: Plain text -#: user-manual.txt:2634 +#: user-manual.txt:2596 msgid "" "Under _Style Options_ some style-related options are available like font " "size and theme." msgstr "" #. type: Plain text -#: user-manual.txt:2637 +#: user-manual.txt:2599 msgid "" -"Export to other formats can be achieved through third party facilities, for " +"Export to other formats can be done through third party facilities, for " "instance _www.divelogs.de_." msgstr "" #. type: Title == -#: user-manual.txt:2639 +#: user-manual.txt:2601 #, no-wrap msgid "Keeping a _Subsurface_ dive log in the Cloud" msgstr "" #. type: Plain text -#: user-manual.txt:2650 +#: user-manual.txt:2611 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 " +"record of diving activities for one's own pleasure, but it’s important " +"information required for admission to training courses or sometimes even " +"diving sites. The security of the dive log is critical. 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 you can access your dive log from anywhere in the world. For this " "reason, facilities such as _divelogs.de_ and _Diving Log_ offer to store " "dive log information on the Internet." msgstr "" #. type: Plain text -#: user-manual.txt:2656 +#: user-manual.txt:2617 msgid "" "_Subsurface_ includes access to a transparently integrated cloud storage " "back end that is available to all Subsurface users. Storing and retrieving a " "dive log from the cloud is no more difficult than accessing the dives on the " -"local hard disk. The only requirement is that one should first register as " +"local hard disk. The only requirement is that you should first register as " "a user on the cloud. To use _Subsurface cloud storage_ , follow these steps:" msgstr "" #. type: Title === -#: user-manual.txt:2657 +#: user-manual.txt:2618 #, no-wrap msgid "Create a cloud storage account" msgstr "" #. type: Plain text -#: user-manual.txt:2674 +#: user-manual.txt:2635 #, no-wrap msgid "" "** Open the *Network Preferences* by selecting _File_ -> _Preferences_ -> _Network_.\n" @@ -5254,83 +5304,82 @@ msgid "" msgstr "" #. type: Title === -#: user-manual.txt:2675 +#: user-manual.txt:2636 #, no-wrap msgid "Using _Subsurface cloud storage_" msgstr "" #. type: Plain text -#: user-manual.txt:2685 +#: user-manual.txt:2646 #, no-wrap msgid "" -"** Once the cloud storage has been initialised, two new items appear in the\n" +"** Once the cloud storage has been initialized, two new items appear in the\n" " _File_ menu of the main menu system: _Open cloud storage_ and _Save to cloud storage_.\n" -"These options allow the user to load and save data to the _Subsurface\n" +"These options let you load and save data to the _Subsurface\n" "cloud storage_ server.\n" -"** In the _Defaults Preferences_ tab, one can select to use the _Subsurface cloud\n" -"storage_ data as one's default data file by checking the check box marked _Cloud storage default file_.\n" -" This means that the data from\n" -"the _Subsurface cloud storage_ is loaded when _Subsurface_ starts ans saved there when one closes _Subsurface_.\n" +"** In the _Defaults Preferences_ tab, you can select to use the _Subsurface cloud\n" +"storage_ data as the default data file by checking the box marked _Cloud storage default file_.\n" +" This means the data from\n" +"the _Subsurface cloud storage_ is loaded when _Subsurface_ starts and saved there when _Subsurface_ closes.\n" msgstr "" #. type: Plain text -#: user-manual.txt:2690 +#: user-manual.txt:2651 #, no-wrap msgid "" "** _Subsurface_ keeps a local copy of the data and the cloud facility remains fully\n" -"functional even if used while disconnected to the Internet. _Subsurface_ simply synchronises the\n" -"data with the cloud server the next time ithe program is used while the computer is\n" +"functional even if used while disconnected to the Internet. _Subsurface_ simply synchronizes the\n" +"data with the cloud server the next time the program is used while the computer is\n" "connected to the Internet.\n" msgstr "" #. type: Title === -#: user-manual.txt:2692 +#: user-manual.txt:2653 #, no-wrap msgid "Web access to _Subsurface cloud storage_" msgstr "" #. type: Plain text -#: user-manual.txt:2702 +#: user-manual.txt:2663 msgid "" "One of the nice side benefits of using _Subsurface cloud storage_ is that " -"one can also access one's dive data from any web browser. Simply open " -"https://cloud.subsurface-divelog.org[_https://cloud.subsurface-divelog." -"org_], log in with the same email and password, and you can see an HTML " -"export of the last dive data that was synced to the _Subsurface cloud " -"storage_. The dive information that is shown is only the contents of the " -"recorded dive logs, NOT the calculated values shown in the *Profile* panel, " -"including some cylinder pressures, deco ceilings and O~2~/He/N~2~ partial " -"pressures." +"you can also access your dive data from any web browser. Simply open https://" +"cloud.subsurface-divelog.org[_https://cloud.subsurface-divelog.org_], log in " +"with the same email and password, and you can see an HTML export of the last " +"dive data that was synced to _Subsurface cloud storage_. The dive " +"information shown is only the contents of the recorded dive logs, NOT the " +"calculated values shown in the *Profile* panel, including some cylinder " +"pressures, deco ceilings and O~2~/He/N~2~ partial pressures." msgstr "" #. type: Title === -#: user-manual.txt:2703 +#: user-manual.txt:2664 #, no-wrap msgid "Other cloud services" msgstr "" #. type: Plain text -#: user-manual.txt:2713 +#: user-manual.txt:2674 msgid "" -"If one prefers not to use the integrated cloud storage of dive logs (and " -"don't need the web access), it is also simple to store dive logs in the " -"cloud 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." +"If you prefers not to use the integrated cloud storage of dive logs (and " +"don't need the web access), it’s simple to store dive logs in the cloud " +"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 a desktop " +"computer." msgstr "" #. type: Target for macro image -#: user-manual.txt:2714 +#: user-manual.txt:2675 #, no-wrap msgid "images/Cloud.jpg" msgstr "images/Cloud.jpg" #. type: Plain text -#: user-manual.txt:2723 +#: user-manual.txt:2684 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, " +"on your 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. " @@ -5340,204 +5389,203 @@ msgid "" msgstr "" #. type: Plain text -#: user-manual.txt:2730 +#: user-manual.txt:2691 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. " +"In this way a dive log in your _Dropbox_ folder can be accessed seamlessly " +"from the Internet and can be accessed anywhere 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:2736 +#: user-manual.txt:2697 msgid "" -"Alternatively one can use _Dropbox_ as a mechanism to backup one's dive log. " -"To Store a dive log on _Dropbox_, 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 _Dropbox_, 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." +"Alternatively you can use _Dropbox_ as a way back up your dive log. To Store " +"a dive log on _Dropbox_, 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 _Dropbox_, 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:2739 +#: user-manual.txt:2700 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:2742 +#: user-manual.txt:2703 #, no-wrap msgid "Printing a dive log" msgstr "" #. type: Plain text -#: user-manual.txt:2746 +#: user-manual.txt:2707 #, no-wrap msgid "" -"_Subsurface_ provides a simple and flexible interface to print a whole dive log or only a few selected dives.\n" +"_Subsurface_ provides a simple and flexible way to print a whole dive log or only a few selected dives.\n" " Pre-installed templates or a custom written template can be used to choose where the data are fitted into the page.\n" msgstr "" #. type: Plain text -#: user-manual.txt:2748 -msgid "Before printing, two decisions are required:" +#: user-manual.txt:2709 +msgid "Some decisions need to be made before printing:" msgstr "" #. type: Plain text -#: user-manual.txt:2751 +#: user-manual.txt:2712 msgid "" -"Should the whole dive log be printed or only part of it? If only part of the " -"dive log is required, then select the required dives from the *Dive List* " -"panel." +"Should the whole dive log be printed or only part of it? If only part is " +"required, select the required dives from the *Dive List* panel." msgstr "" #. type: Plain text -#: user-manual.txt:2753 +#: user-manual.txt:2714 msgid "" -"If the dive profiles needs printing, what gas partial pressure information " +"If the dive profiles are printed, what gas partial pressure information " "should be shown? Select the appropriate toggle-buttons on the button bar to " "the left of the *Dive Profile* panel." msgstr "" #. type: Plain text -#: user-manual.txt:2756 +#: user-manual.txt:2717 msgid "" -"If _File -> Print_ is selected from the Main menu, the the dialogue below " -"(image *A*) appears. Three specifications are needed to achieve the desired " -"information and page layout:" +"If _File -> Print_ is selected from the Main menu, the dialogue below (image " +"*A*) appears. Three specifications are needed to get the desired information " +"and page layout:" msgstr "" #. type: Target for macro image -#: user-manual.txt:2757 user-manual.txt:4185 +#: user-manual.txt:2718 user-manual.txt:4162 #, no-wrap msgid "images/Print1_f22.jpg" msgstr "images/Print1_f22.jpg" #. type: Plain text -#: user-manual.txt:2760 +#: user-manual.txt:2721 msgid "Under _Print type_ select one of two options:" msgstr "" #. type: Plain text -#: user-manual.txt:2762 +#: user-manual.txt:2723 msgid "" "_Dive list print_: Print dives from the *Dive List* panel with profiles and " "other information." msgstr "" #. type: Plain text -#: user-manual.txt:2763 +#: user-manual.txt:2724 msgid "_Statistics print_: Print yearly statistics of the dives." msgstr "" #. type: Plain text -#: user-manual.txt:2765 +#: user-manual.txt:2726 msgid "Under _Print options_ select:" msgstr "" #. type: Plain text -#: user-manual.txt:2770 +#: user-manual.txt:2731 msgid "" -"Printing only the dives selected from the dive list prior to activating the " +"Printing only the dives selected from the dive list before activating the " "print dialogue by checking the box _Print only selected dives_. If this " -"check box is *not* checked all dives in the *Dive List* panel are printed." +"check box is *not* checked ALL dives in the *Dive List* panel are printed." msgstr "" #. type: Plain text -#: user-manual.txt:2772 +#: user-manual.txt:2733 msgid "" -"Printing in colour, achieved by checking the box with _Print in colour_. If " -"this check box is not checked, printing is in monochrome (grey scale)." +"Printing in color, done by checking the box with _Print in color. If this " +"check box is not checked, printing is in black and white." msgstr "" #. type: Plain text -#: user-manual.txt:2775 +#: user-manual.txt:2736 msgid "" "Under _Template_ select a template to be used as the page layout. There are " -"several templates (see image *B*, above)." +"several choices. (see image *B*, above)." msgstr "" #. type: Plain text -#: user-manual.txt:2777 +#: user-manual.txt:2738 msgid "_Table_: This prints a summary table of all dives selected (see below)." msgstr "" #. type: Target for macro image -#: user-manual.txt:2778 +#: user-manual.txt:2739 #, no-wrap msgid "images/Print_summarylist_f22.jpg" msgstr "images/Print_summarylist_f22.jpg" #. type: Plain text -#: user-manual.txt:2781 +#: user-manual.txt:2742 msgid "" "_Flow layout_: Print the text associated with each dive without printing the " "dive profiles" msgstr "" #. type: Plain text -#: user-manual.txt:2782 +#: user-manual.txt:2743 msgid "of each dive (see below):" msgstr "" #. type: Target for macro image -#: user-manual.txt:2783 +#: user-manual.txt:2744 #, no-wrap msgid "images/Print_flow_layout_f22.jpg" msgstr "images/Print_flow_layout_f22.jpg" #. type: Plain text -#: user-manual.txt:2786 +#: user-manual.txt:2747 msgid "" "_One Dive_: Print one dive per page, also showing the dive profile (see " "below)" msgstr "" #. type: Target for macro image -#: user-manual.txt:2787 +#: user-manual.txt:2748 #, no-wrap msgid "images/print2_f22.jpg" msgstr "images/print2_f22.jpg" #. type: Plain text -#: user-manual.txt:2791 +#: user-manual.txt:2752 msgid "_Two Dives_: Print two dives per page, also showing the dive profiles." msgstr "" #. type: Plain text -#: user-manual.txt:2792 +#: user-manual.txt:2753 msgid "_Six Dives_: Print six dives per page, also showing the dive profiles." msgstr "" #. type: Plain text -#: user-manual.txt:2796 +#: user-manual.txt:2757 msgid "" -"Users can _Preview_ the printed page by selecting the _Preview_ button on " -"the dialogue (see image *A* at the start of this section). After preview, " -"changes to the options in the print dialogue can be made, resulting in a " -"layout that fits personal taste." +"You can _Preview_ the printed page by selecting the _Preview_ button on the " +"dialogue (see image *A* at the start of this section). After preview, you " +"can change the options in the print dialogue, so the layout fits personal " +"taste." msgstr "" #. type: Plain text -#: user-manual.txt:2800 +#: user-manual.txt:2761 msgid "" "Next, select the _Print_ button (see image *A* at the start of this " -"section). This activates the regular print dialogue used by the user " -"operating system, allowing one to choose a printer and to set its properties " -"(see image below):" +"section). This activates the regular print dialogue used by the operating " +"system, letting you choose a printer and set its properties (see image " +"below):" msgstr "" #. type: Target for macro image -#: user-manual.txt:2801 +#: user-manual.txt:2762 #, no-wrap msgid "images/Print_print_f22.jpg" msgstr "images/Print_print_f22.jpg" #. type: Plain text -#: user-manual.txt:2806 +#: user-manual.txt:2767 msgid "" "Set the print resolution of the printer to an appropriate value by changing " "the printer _Properties_. Finally, select the _Print_ button to print the " @@ -5546,22 +5594,22 @@ msgid "" msgstr "" #. type: Target for macro image -#: user-manual.txt:2807 +#: user-manual.txt:2768 #, no-wrap msgid "images/Printpreview.jpg" msgstr "images/Printpreview.jpg" #. type: Title === -#: user-manual.txt:2809 +#: user-manual.txt:2770 #, no-wrap msgid "Writing a custom print template (advanced)" msgstr "Créer un modèle d'impression personnalisé (avancé)" #. type: Plain text -#: user-manual.txt:2813 +#: user-manual.txt:2776 msgid "" "Writing a custom template is an effective way to produce highly customized " -"printouts. Subsurface uses HTML templates to render printing. One can create " +"printouts. Subsurface uses HTML templates to render printing. You can create " "a template, export a new template, import an existing template and delete an " "existing template by using the appropriate buttons under the _Template_ " "dropdown list in the print dialogue. See <<S_APPENDIX_E,APPENDIX E>> for " @@ -5569,23 +5617,36 @@ msgid "" msgstr "" #. type: Title == -#: user-manual.txt:2815 +#: user-manual.txt:2778 #, no-wrap msgid "Configuring a dive computer" msgstr "Configurer un ordinateur de plongée" #. type: Plain text -#: user-manual.txt:2823 -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 (also required for downloading " -"dives) 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." +#: user-manual.txt:2787 +#, fuzzy +#| 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 (also " +#| "required for downloading dives) 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." +msgid "" +"_Subsurface_ lets you 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. To begin, be sure the appropriate hardware driver is " +"installed for the dive computer (also required for downloading dives) and " +"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 "" "_Subsurface_ permet de configurer son ordinateur de plongée. Actuellement, " "les familles d'ordinateurs supportés sont Heinrichs-Weikamp (OSTC 2, OSTC 3) " @@ -5599,7 +5660,7 @@ msgstr "" "ANNEXE A>> pour plus d'informations sur la manière de procéder." #. type: Plain text -#: user-manual.txt:2828 +#: user-manual.txt:2792 msgid "" "Once the dive computer is connected to the _Subsurface_ computer, select " "_File -> Configure dive computer_ from the _Main Menu_. Provide the " @@ -5614,22 +5675,26 @@ msgstr "" "plongée à partir du panneau à gauche (voir l'image ci-dessous)." #. type: Target for macro image -#: user-manual.txt:2829 +#: user-manual.txt:2793 #, no-wrap msgid "images/Configure_dc_f20.jpg" msgstr "images/Configure_dc_f20.jpg" #. type: Plain text -#: user-manual.txt:2832 +#: user-manual.txt:2796 +#, fuzzy +#| msgid "" +#| "Using the appropriate buttons on the configuration panel, the following " +#| "actions can be performed:" msgid "" "Using the appropriate buttons on the configuration panel, the following " -"actions can be performed:" +"actions can be done:" msgstr "" "En utilisant les boutons appropriés du panneau de configuration, les actions " "suivantes peuvent être réalisées :" #. type: Plain text -#: user-manual.txt:2835 +#: user-manual.txt:2799 #, no-wrap msgid "" "*Retrieve available details*. This loads the existing configuration from the dive computer\n" @@ -5639,7 +5704,7 @@ msgstr "" "dans _Subsurface_, en l'affichant dans le panneau de configuration.\n" #. type: Plain text -#: user-manual.txt:2837 +#: user-manual.txt:2801 #, no-wrap msgid "" "*Save changes to device*. This changes the configuration of the\n" @@ -5649,7 +5714,7 @@ msgstr "" "de plongée pour correspondre aux informations affichées dans le panneau de configuration.\n" #. type: Plain text -#: user-manual.txt:2839 +#: user-manual.txt:2803 #, no-wrap msgid "" "*Backup*. This saves the configuration data to a file. _Subsurface_ asks for\n" @@ -5659,7 +5724,7 @@ msgstr "" "l'emplacement et le nom du fichier pour enregistrer les informations.\n" #. type: Plain text -#: user-manual.txt:2841 +#: user-manual.txt:2805 #, no-wrap msgid "" "*Restore backup*. This loads the information from a backup file and displays it\n" @@ -5669,7 +5734,7 @@ msgstr "" "dans le panneau de configuration.\n" #. type: Plain text -#: user-manual.txt:2843 +#: user-manual.txt:2807 #, no-wrap msgid "" "*Update firmware*. If new firmware is available for the dive computer, this is\n" @@ -5679,67 +5744,67 @@ msgstr "" "il sera chargé dans l'ordinateur de plongée.\n" #. type: Title == -#: user-manual.txt:2846 +#: user-manual.txt:2810 #, no-wrap msgid "Setting user _Preferences_ for _Subsurface_" msgstr "" #. type: Plain text -#: user-manual.txt:2856 +#: user-manual.txt:2819 msgid "" "There are several user-definable settings within _Subsurface_, found by " -"selecting _File -> Preferences_. The settings are performed in seven groups: " +"selecting _File -> Preferences_. The settings are in seven groups: " "*Defaults*, *Units*, *Graph*, *Language* and *Network*, *Facebook* and " -"*Georeference*, all of which 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*. If *Discard* is selected, " -"changes to the preferences are not saved." +"*Georeference*. All operate on the same principles: the user must specify " +"settings that are to be changed, then save them using the *Apply* button. " +"After applying all the new settings users can then leave the settings panel " +"by selecting *OK*. If *Discard* is selected, changes to the preferences are " +"not saved." msgstr "" #. type: Title === -#: user-manual.txt:2857 +#: user-manual.txt:2820 #, no-wrap msgid "Defaults" msgstr "" #. type: Plain text -#: user-manual.txt:2860 +#: user-manual.txt:2823 msgid "There are several settings in the *Defaults* panel:" msgstr "" #. type: Target for macro image -#: user-manual.txt:2861 +#: user-manual.txt:2824 #, no-wrap msgid "images/Pref1_f20.jpg" msgstr "images/Pref1_f20.jpg" #. type: Plain text -#: user-manual.txt:2865 +#: user-manual.txt:2828 #, 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" +" ** *Lists and tables*: Here you can specify the font type and font size of the\n" +" *Dive Table* panel: By decreasing the font size of the *Dive Table*, you can see more dives on a screen.\n" msgstr "" #. type: Plain text -#: user-manual.txt:2870 +#: user-manual.txt:2833 #, no-wrap msgid "" -" ** *Dives*: For the _Default Dive File_ one needs to specify the directory and\n" -" file name of one's\n" +" ** *Dives*: For the _Default Dive File_ you need to specify the directory and\n" +" file name of your\n" " electronic dive log book. This is a file with filename extension of either _.xml_ or _.ssrf_. When\n" " launched, _Subsurface_ will automatically load the specified dive log book. There are three options:\n" msgstr "" #. type: Plain text -#: user-manual.txt:2871 +#: user-manual.txt:2834 #, no-wrap msgid "_No default file_: When checked, _Subsurface_ does not automatically load a dive log at startup.\n" msgstr "" #. type: Plain text -#: user-manual.txt:2873 +#: user-manual.txt:2836 #, no-wrap msgid "" "_Local default file_: When checked, _Subsurface_ automatically loads a dive log from the local hard disk\n" @@ -5747,21 +5812,21 @@ msgid "" msgstr "" #. type: Plain text -#: user-manual.txt:2875 +#: user-manual.txt:2838 #, no-wrap msgid "" "_Cloud storage default file_: When checked, _Subsurface automatically loads the dive log from the cloud\n" -"device that was initialised using the *Preferences* _Network_ tab (see below).\n" +"device that was initialized using the *Preferences* _Network_ tab (see below).\n" msgstr "" #. type: Plain text -#: user-manual.txt:2877 +#: user-manual.txt:2840 #, no-wrap msgid "** *Display invalid*: Dives can be marked as invalid (when a user wishes to hide\n" msgstr "" #. type: Plain text -#: user-manual.txt:2880 +#: user-manual.txt:2843 #, no-wrap msgid "" "dives that he/she doesn't consider valid dives, e.g. pool dives, but still want to\n" @@ -5770,25 +5835,25 @@ msgid "" msgstr "" #. type: Plain text -#: user-manual.txt:2882 +#: user-manual.txt:2845 #, no-wrap msgid "** *Default cylinder*: Specify the default cylinder listed in\n" msgstr "" #. type: Plain text -#: user-manual.txt:2883 +#: user-manual.txt:2846 #, no-wrap msgid "the *Equipment* tab of the *Notes* panel.\n" msgstr "" #. type: Plain text -#: user-manual.txt:2885 +#: user-manual.txt:2848 #, no-wrap msgid "** *Animations*: Some actions in showing the dive profile are performed using\n" msgstr "" #. type: Plain text -#: user-manual.txt:2891 +#: user-manual.txt:2854 #, no-wrap msgid "" "animations. For instance, the axis values for depth and time change from dive to\n" @@ -5800,106 +5865,108 @@ msgid "" msgstr "" #. type: Plain text -#: user-manual.txt:2893 +#: user-manual.txt:2856 #, no-wrap msgid "** *Clear all settings*: As indicated in the button below this heading, all settings are\n" msgstr "" #. type: Plain text -#: user-manual.txt:2894 +#: user-manual.txt:2857 #, no-wrap msgid "cleared and set to default values.\n" msgstr "" #. type: Title === -#: user-manual.txt:2895 +#: user-manual.txt:2858 #, no-wrap msgid "Units" msgstr "" #. type: Target for macro image -#: user-manual.txt:2896 +#: user-manual.txt:2859 #, no-wrap msgid "images/Pref2_f20.jpg" msgstr "images/Pref2_f20.jpg" #. type: Plain text -#: user-manual.txt:2903 +#: user-manual.txt:2866 msgid "" -"Here users can choose between metric and imperial units of depth, pressure, " +"Here you 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, one 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." +"button at the top, you can specify that all units are in the chosen " +"measurement system. Alternatively, if you select the *Personalize* radio " +"button, units can be selected independently, with some in the metric system " +"and others in imperial." msgstr "" #. type: Plain text -#: user-manual.txt:2909 +#: user-manual.txt:2872 msgid "" -"Irrespective of the above settings, dive time measurements can be either in " +"Regardless of the above settings, dive time measurements can be either in " "seconds or minutes. Choose the appropriate option. GPS coordinates can be " "represented either as traditional coordinates (degrees, minutes, seconds) or " "as decimal degrees Choose the appropriate option." msgstr "" #. type: Title === -#: user-manual.txt:2910 +#: user-manual.txt:2873 #, no-wrap msgid "Graph" msgstr "" #. type: Target for macro image -#: user-manual.txt:2912 +#: user-manual.txt:2875 #, no-wrap msgid "images/Pref3_f20.jpg" msgstr "images/Pref3_f20.jpg" #. type: Plain text -#: user-manual.txt:2916 +#: user-manual.txt:2879 msgid "This panel allows two type of selections:" msgstr "" #. type: Plain text -#: user-manual.txt:2936 +#: user-manual.txt:2901 #, no-wrap msgid "" -"*Show*: Here users can specify the amount of information shown as part of\n" +"*Show*: Here you 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, enabled by 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" +" the dive, done by using the toolbar on the left hand side of the *Dive Profile*\n" +" panel. For each of these graphs you can specify a threshold value on the right-hand side of the\n" " Preferences panel. If any of the graphs go above the specified threshold level, the graph is\n" -" highlighted in red, indicating that the particular partial pressure threshold has been exceeded.\n" +" highlighted in red, indicating the particular partial pressure threshold has been exceeded.\n" "** _Max pO~2~ is used for calculating the MOD when displaying the maximum operative depth (MOD)\n" " for a dive. Specify an appropriate partial pressure. A value of 1.4 is commonly used.\n" -"** _Draw dive computer reported ceiling red_: This checkbox allows exactly what it says. By default\n" +"** _Draw dive computer reported ceiling red_: This checkbox does exactly what it says. By default\n" " the computer reported ceiling is shown in white.\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_ because of the different algorithms and\n" -" gradient factors, as well as the dynamic way that a\n" -" dive computer can calculate ceilings during a dive.\n" -"** _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 if 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" -"** _Show average depth_: If this box is checked, the *Dive Profile* panel contains a grey line that indicates\n" -" the mean depth of the dive up to any time instant during the dive. Normally this is a u-shaped line indicating the deepest mean depth just before the\n" +" gradient factors, as well as the dynamic way a\n" +" dive computer calculates ceilings during a dive.\n" +"** _Show unused cylinders in Equipment Tab_: This checkbox allows display of information about unused cylinders when viewing the\n" +"*Equipment Tab*. If this box is not checked, and if any cylinders entered using the *Equipment Tab* are not used (e.g. there\n" +"was no gas switch to such a cylinder), then these cylinders are omitted from that list.\n" +"** _Show average depth_: If this box is checked, the *Dive Profile* panel contains a grey line that shows\n" +" the mean depth of the dive, up to any time instant during the dive. Normally this is a u-shaped line indicating the deepest mean depth just before\n" " ascent.\n" msgstr "" #. type: Plain text -#: user-manual.txt:2938 +#: user-manual.txt:2903 #, no-wrap msgid "*Misc*:\n" msgstr "" #. type: Plain text -#: user-manual.txt:2951 +#: user-manual.txt:2916 #, no-wrap msgid "" "** Gradient Factors (GFLow and GFHigh):* 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" +" Gradient factors add conservatism to nitrogen exposure during a dive, in a\n" +" similar way that many dive computers have a conservative 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 70/90 are considered\n" @@ -5909,28 +5976,28 @@ msgid "" msgstr "" #. type: Plain text -#: user-manual.txt:2953 +#: user-manual.txt:2918 #, 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 " *** http://www.tek-dive.com/portal/upload/M-Values.pdf[Understanding M-values by Erik Baker, _Immersed_ Vol. 3, No. 3.]\n" #. type: Plain text -#: user-manual.txt:2955 +#: user-manual.txt:2920 #, 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 " *** 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" #. type: Plain text -#: user-manual.txt:2959 +#: user-manual.txt:2924 #, no-wrap msgid "" -" ** _CCR: Show setpoints when viewing pO2:_ With this checkbox ativated, the pO~2~\n" -" graph on the dive profile has an overlay in red which inticates the CCR setpoint\n" +" ** _CCR: Show setpoints when viewing pO2:_ With this checkbox activated, the pO~2~\n" +" graph on the dive profile has an overlay in red which indicates the CCR setpoint\n" " values. See the section on xref:S_CCR_dives[Closed Circuit Rebreather dives].\n" msgstr "" #. type: Plain text -#: user-manual.txt:2963 +#: user-manual.txt:2928 #, no-wrap msgid "" " ** _CCR: Show individual O~2~ sensor values when viewing pO~2~:_ Show the pO~2~\n" @@ -5939,19 +6006,19 @@ msgid "" msgstr "" #. type: Plain text -#: user-manual.txt:2965 +#: user-manual.txt:2930 #, no-wrap msgid "*Configuring dive planning using rebreather equipment:*\n" msgstr "" #. type: Plain text -#: user-manual.txt:2967 +#: user-manual.txt:2932 #, no-wrap msgid "** _Default CCR setpoint for dive planning:_ Specify the O~2~ setpoint for a\n" msgstr "" #. type: Plain text -#: user-manual.txt:2970 +#: user-manual.txt:2935 #, no-wrap msgid "" "CCR dive plan. This determines the pO~2~ maintained\n" @@ -5960,13 +6027,13 @@ msgid "" msgstr "" #. type: Plain text -#: user-manual.txt:2972 +#: user-manual.txt:2937 #, no-wrap -msgid "** _pSCR O~2~ metabolism rate:_ For a semiclosed rebreather (pSCR) system, this is the\n" +msgid "** _pSCR O~2~ metabolism rate:_ For a semi-closed rebreather (pSCR) system, this is the\n" msgstr "" #. type: Plain text -#: user-manual.txt:2974 +#: user-manual.txt:2939 #, no-wrap msgid "" "volume of oxygen used by a diver during a minute. Set this value for pSCR dive planning\n" @@ -5974,13 +6041,13 @@ msgid "" msgstr "" #. type: Plain text -#: user-manual.txt:2976 +#: user-manual.txt:2941 #, no-wrap msgid "** _pSCR ratio:_ For pSCR equipment the dump ratio is the ratio of gas released to the\n" msgstr "" #. type: Plain text -#: user-manual.txt:2978 +#: user-manual.txt:2943 #, no-wrap msgid "" "environment to that of the gas recirculated to the diver. Set this value for a\n" @@ -5988,66 +6055,64 @@ msgid "" msgstr "" #. type: Title === -#: user-manual.txt:2980 +#: user-manual.txt:2945 #, no-wrap msgid "Language" msgstr "" #. type: Plain text -#: user-manual.txt:2982 +#: user-manual.txt:2947 msgid "Choose a language that _Subsurface_ will use." msgstr "" #. type: Target for macro image -#: user-manual.txt:2983 +#: user-manual.txt:2948 #, no-wrap msgid "images/Pref4_f20.jpg" msgstr "images/Pref4_f20.jpg" #. type: Plain text -#: user-manual.txt:2993 +#: user-manual.txt:2958 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 operating system. If this " -"is for some reason undesirable one 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*." +"A checkbox lets you 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 operating system. To change " +"it, uncheck this checkbox and pick a language / country combination from the " +"list of locations. The _Filter_ text box lists 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:2994 +#: user-manual.txt:2959 #, no-wrap msgid "Network" msgstr "" #. type: Plain text -#: user-manual.txt:3000 +#: user-manual.txt:2966 msgid "" "This panel facilitates communication between _Subsurface_ and data sources " "on the Internet. This is important, for instance, when _Subsurface_ needs " -"to communicate with Internet services such as Cloud storage or the " -"<<S_Companion,_Subsurface Companion app_>>. 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." +"to communicate with web services such as Cloud storage or the <<S_Companion," +"_Subsurface Companion app_>>. These Internet requirements are determined by " +"your type of connection to the Internet and by the Internet Service Provider " +"(ISP) used. Your ISP should provide the appropriate information." msgstr "" #. type: Target for macro image -#: user-manual.txt:3001 +#: user-manual.txt:2967 #, no-wrap msgid "images/Pref5_f20.jpg" msgstr "images/Pref5_f20.jpg" #. type: Plain text -#: user-manual.txt:3004 +#: user-manual.txt:2970 msgid "This dialogue has three sections:" msgstr "" #. type: Plain text -#: user-manual.txt:3012 +#: user-manual.txt:2978 #, no-wrap msgid "" "** _Proxy type_:\n" @@ -6060,77 +6125,88 @@ msgid "" msgstr "" #. type: Plain text -#: user-manual.txt:3017 +#: user-manual.txt:2983 #, no-wrap msgid "" -"** _Subsurface cloud storage_: To store one's dive log in the cloud, a valid email address\n" -" and password are required. This allows _Subsurface_ to email security information\n" -" regarding cloud storage to a user, and to set up the cloud storage appropriately.\n" +"** _Subsurface cloud storage_: To store your dive log in the cloud, a valid email address\n" +" and password are required. This lets _Subsurface_ email security information\n" +" regarding cloud storage to you, and to set up cloud storage appropriately.\n" " Two additional options are given:\n" msgstr "" #. type: Plain text -#: user-manual.txt:3018 +#: user-manual.txt:2984 #, no-wrap msgid "_Sync to cloud in the background_: This option allows saving of dive information to the cloud storage\n" msgstr "" #. type: Plain text -#: user-manual.txt:3019 +#: user-manual.txt:2985 #, no-wrap -msgid "while the user performs other tasks within _Subsurface_.\n" +msgid "while you do other things within _Subsurface_.\n" msgstr "" #. type: Plain text -#: user-manual.txt:3020 +#: user-manual.txt:2986 #, no-wrap msgid "_Save password locally_: This allows local storage of the cloud storage password. Note that this\n" msgstr "" #. type: Plain text -#: user-manual.txt:3021 +#: user-manual.txt:2987 #, no-wrap msgid "information is saved in raw text form, not encoded in any way.\n" msgstr "" #. type: Plain text -#: user-manual.txt:3026 +#: user-manual.txt:2991 #, no-wrap msgid "" -"** _Subsurface web service_: When one subscribes to the <<S_Companion,Subsurface web service>>, a very\n" +"** _Subsurface web service_: When you subscribe 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" +" checking the option _Save User ID locally?_, you ensure a local copy of that userID is saved.\n" msgstr "" #. type: Title === -#: user-manual.txt:3029 -#, no-wrap -msgid "Facebook Accesss" +#: user-manual.txt:2994 +#, fuzzy, no-wrap +#| msgid "Facebook Accesss" +msgid "Facebook Access" msgstr "Accès Facebook" #. type: Plain text -#: user-manual.txt:3032 +#: user-manual.txt:2997 +#, fuzzy +#| msgid "" +#| "This panel allows one to log into a Facebook account in order to transfer " +#| "information from Subsurface to Facefook." msgid "" -"This panel allows one to log into a Facebook account in order to transfer " -"information from Subsurface to Facefook." +"This panel lets you log into a Facebook account in order to transfer " +"information from Subsurface to Facebook." msgstr "" "Ce panneau vous permet de vous connecter à votre compte Facebook pour " "transférer des informations de Subsurface vers Facebook." #. type: Target for macro image -#: user-manual.txt:3033 +#: user-manual.txt:2998 #, no-wrap msgid "images/Pref6_f20.jpg" msgstr "images/Pref6_f20.jpg" #. type: Plain text -#: user-manual.txt:3041 +#: user-manual.txt:3006 +#, fuzzy +#| msgid "" +#| "If one provides a valid Facebook userID and password, a connection to " +#| "Facebook is created. The connection to Facebook is closed when one closes " +#| "down Subsurface. Currently the checkbox labelled \"Keep me logged in to " +#| "Subsurface\", on the login screen has no effect. See the section xref:" +#| "S_facebook[Exporting dive profiles to Facebook] for more information." msgid "" -"If one provides a valid Facebook userID and password, a connection to " -"Facebook is created. The connection to Facebook is closed when one closes " -"down Subsurface. Currently the checkbox labelled \"Keep me logged in to " -"Subsurface\", on the login screen has no effect. See the section xref:" +"If you provide a valid Facebook userID and password, a connection to " +"Facebook is created. That connection is closed when one closing down " +"Subsurface. Currently the checkbox labelled \"Keep me logged in to Subsurface" +"\", on the login screen has no effect. See the section xref:" "S_facebook[Exporting dive profiles to Facebook] for more information." msgstr "" "Si un identifiant Facebook et un mot de passe valides ont été fournis, une " @@ -6141,47 +6217,47 @@ msgstr "" "vers Facebook] pour plus d'informations." #. type: Title === -#: user-manual.txt:3042 +#: user-manual.txt:3007 #, no-wrap msgid "Georeference" msgstr "" #. type: Plain text -#: user-manual.txt:3050 +#: user-manual.txt:3015 msgid "" "_Subsurface_ provides a geo-lookup service (that is, given the coordinates " -"of a dive site (derived from a click on the *Dive Map panel* at the bottom " +"of a dive site) derived from a click on the *Dive Map panel* at the bottom " "right of the _Subsurface_ window, or from a GPS instrument or from the " -"_Subsurface_ Companion app), a lookup on the Internet is performed to find " -"the name of the closest known location. Obviously this function only works " -"if _Subsurface_ has an Internet connection. The preference of the dive site " -"name can be configured, e.g. _Country/State/City_ or _City/State/Country_ " -"(see image below)." +"_Subsurface_ Companion app). A search on the Internet is done to find the " +"name of the closest known location. This function only works if _Subsurface_ " +"has an Internet connection. The preference of the dive site name can be " +"configured, e.g. _Country/State/City_ or _City/State/Country_ (see image " +"below)." msgstr "" #. type: Target for macro image -#: user-manual.txt:3051 +#: user-manual.txt:3016 #, no-wrap msgid "images/Pref7_f20.jpg" msgstr "images/Pref7_f20.jpg" #. type: Title == -#: user-manual.txt:3054 +#: user-manual.txt:3019 #, no-wrap msgid "The _Subsurface_ dive planner" msgstr "" #. type: Plain text -#: user-manual.txt:3059 +#: user-manual.txt:3024 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." +"Dive planning is an advanced feature of _Subsurface_, accessed 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:3067 +#: user-manual.txt:3032 msgid "" "The _Subsurface_ dive planner IS CURRENTLY EXPERIMENTAL and assumes the user " "is already familiar with the _Subsurface_ user interface. It is explicitly " @@ -6189,19 +6265,19 @@ msgid "" msgstr "" #. type: delimited block * -#: user-manual.txt:3070 +#: user-manual.txt:3035 msgid "" "The user is conversant with dive planning and has the necessary training to " "perform dive planning." msgstr "" #. type: delimited block * -#: user-manual.txt:3071 +#: user-manual.txt:3036 msgid "The user plans dives within his/her certification limits." msgstr "" #. type: delimited block * -#: user-manual.txt:3074 +#: user-manual.txt:3039 msgid "" "Dive planning makes large assumptions about the characteristics of the " "_average person_ and cannot compensate for individual physiology or health " @@ -6209,51 +6285,50 @@ msgid "" msgstr "" #. type: delimited block * -#: user-manual.txt:3075 +#: user-manual.txt:3040 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:3076 +#: user-manual.txt:3041 msgid "The user is familiar with the user interface of _Subsurface_." msgstr "" #. type: delimited block * -#: user-manual.txt:3078 +#: user-manual.txt:3043 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:3080 +#: user-manual.txt:3045 #, no-wrap msgid "The _Subsurface_ dive planner screen" msgstr "" #. type: Plain text -#: user-manual.txt:3085 +#: user-manual.txt:3050 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 Notes." +"into the sections on the left hand side of the screen. They are: Available " +"Gases, Rates, Planning, Gas Options and Notes." msgstr "" #. type: Plain text -#: user-manual.txt:3089 +#: user-manual.txt:3054 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 " +"At the top right hand is a green *design panel* on 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:3093 +#: user-manual.txt:3058 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 " @@ -6262,26 +6337,26 @@ msgid "" msgstr "" #. type: Target for macro image -#: user-manual.txt:3094 +#: user-manual.txt:3059 #, no-wrap msgid "images/PlannerWindow1_f20.jpg" msgstr "images/PlannerWindow1_f20.jpg" #. type: Title === -#: user-manual.txt:3097 +#: user-manual.txt:3062 #, no-wrap msgid "Open circuit dives" msgstr "" #. type: Plain text -#: user-manual.txt:3100 +#: user-manual.txt:3065 msgid "" -"Towards the centre bottom of the planner (circled in blue in the image " +"Towards the center bottom of the planner (circled in blue in the image " "above) is a dropbox with three options. Select the appropriate one of these:" msgstr "" #. type: Plain text -#: user-manual.txt:3103 +#: user-manual.txt:3068 #, no-wrap msgid "" "** Open Circuit (the default)\n" @@ -6290,22 +6365,22 @@ msgid "" msgstr "" #. type: Plain text -#: user-manual.txt:3105 +#: user-manual.txt:3070 msgid "Choose the Open Circuit option." msgstr "" #. type: Plain text -#: user-manual.txt:3109 +#: user-manual.txt:3074 msgid "" -"In the top left-hand area of the planning screen, ensure that the constant " -"dive parameters are appropriate. These are: Start date and time of the " -"intended dive, Atmospheric Pressure and Altitude above sea level of the dive " -"site. The atmospheric pressure can also be entered as an altitude in metres, " +"In the top left-hand area of the planning screen, be sure the constant dive " +"parameters are appropriate. These are: Start date and time of the intended " +"dive, Atmospheric Pressure and Altitude above sea level of the dive site. " +"The atmospheric pressure can also be entered as an altitude in meters, " "assuming a sea-level atmospheric pressure of 1.013 bar." msgstr "" #. type: Plain text -#: user-manual.txt:3118 +#: user-manual.txt:3083 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. " @@ -6320,22 +6395,22 @@ msgid "" msgstr "" #. type: Plain text -#: user-manual.txt:3120 +#: user-manual.txt:3085 msgid "The profile of the planned dive can be created in two ways:" msgstr "" #. type: Plain text -#: user-manual.txt:3125 +#: user-manual.txt:3090 msgid "" -"Drag the waypoints (the small white circles) on the existing dive profile in " -"a way to represent the dive. Additional waypoints can be created by double-" -"clicking the existing dive profile. Waypoints can be deleted by right-" -"clicking a particular waypoint and selecting the _delete_ item from the " -"resulting context menu." +"Drag the waypoints (the small white circles) on the existing dive profile to " +"represent the dive. Additional waypoints can be created by double-clicking " +"the existing dive profile. Waypoints can be deleted by right-clicking a " +"particular waypoint and selecting the _delete_ item from the resulting " +"context menu." msgstr "" #. type: Plain text -#: user-manual.txt:3133 +#: user-manual.txt:3098 msgid "" "The most efficient way to create a dive profile is to enter the appropriate " "values into the table marked _Dive planner points_. The first line of the " @@ -6349,55 +6424,48 @@ msgid "" msgstr "" #. type: Title ==== -#: user-manual.txt:3134 +#: user-manual.txt:3099 #, no-wrap msgid "Recreational dives" msgstr "" #. type: Plain text -#: user-manual.txt:3149 +#: user-manual.txt:3116 +#, no-wrap msgid "" -"Recreational mode is what comes closest to planning a dive based on the non-" -"decompression limit (NDL). It computes the maximal time a diver can stay at " -"the current depth without incurring any mandatory decompression stops and " -"without using more than the existing gas (minus a reserve). The planner " -"automatically takes into account the nitrogen load incurred in previous " -"dives. But conventional dive tables are also used in a way that can take " -"into account previous dives. Why use a dive planner for recreational dives? " -"Using recreational dive tables, the maximum depth of a dive is taken into " -"account. However, few dives are undertaken at a constant depth corresponding " -"to the maximum depth (i.e. a \"square\" dive profile). This means that dive " -"tables overestimate the nitrogen load incurred during previous dives. The " -"_Subsurface_ dive planner calculates nitrogen load according to the real " -"dive profiles of all uploaded previous dives, in a similar way as dive " -"computers calculate nitrogen load during a dive. This means that the diver " -"gets 'credit' in terms of nitrogen loading for not remaining at maximum " -"depth during previous dives, enabling planning of a longer subsequent dive. " -"For the planner to work it is therefore crucial to upload all previous dives " -"onto _Subsurface_ before performing dive planning." -msgstr "" - -#. type: Plain text -#: user-manual.txt:3151 -msgid "To plan a dive, the appropriate settings need to be defined." +"Recreational mode is what comes closest to planning a dive based on the non-decompression limit (NDL).\n" +"It computes the maximum time a diver can stay at the current depth without needing mandatory decompression\n" +"stops and without using more than the existing gas (minus a reserve). The planner automatically takes\n" +"into account the nitrogen load incurred in previous dives. But conventional dive tables are also used in a\n" +"way that can take into account previous dives. Why use a dive planner for recreational dives? Using\n" +"recreational dive tables, the maximum depth of a dive is taken into account. But few dives are\n" +"done at a constant depth corresponding to the maximum depth (i.e. a \"square\" dive profile). This means\n" +"dive tables overestimate the nitrogen load incurred during previous dives. The _Subsurface_\n" +"dive planner calculates nitrogen load according to the real dive profiles of all uploaded previous dives,\n" +"in a similar way as dive computers calculate nitrogen load during a dive. This means that the diver gets 'credit,'\n" +"in terms of nitrogen load, for not remaining at maximum depth during\n" +"previous dives, so a longer subsequent dive can be planned.\n" +" For the planner to work it's crucial to upload all previous dives\n" +"onto _Subsurface_ before doing dive planning.\n" +"To plan a dive, the appropriate settings need to be defined.\n" msgstr "" #. type: Plain text -#: user-manual.txt:3154 +#: user-manual.txt:3119 msgid "" -"Ensure that the date and time is set to that of the intended dive. This " -"allows calculation of the nitrogen load incurred during previous dives." +"Ensure the date and time is set to that of the intended dive. This allows " +"calculation of the nitrogen load incurred during previous dives." msgstr "" #. type: Plain text -#: user-manual.txt:3157 +#: user-manual.txt:3122 msgid "" "Immediately under the heading _Planning_ are two checkboxes _Recreational_ " "and _Safety Stop_. Check these two boxes." msgstr "" #. type: Plain text -#: user-manual.txt:3161 +#: user-manual.txt:3126 msgid "" "Then define the cylinder size, the gas mixture (air or % oxygen) and the " "starting cylinder pressure in the top left-hand section of the planner under " @@ -6405,35 +6473,34 @@ msgid "" msgstr "" #. type: Plain text -#: user-manual.txt:3166 +#: user-manual.txt:3131 msgid "" "The planner calculates whether the specified cylinder contains enough air/" -"gas to complete the planned dive. In order for this to be realistic, under " +"gas to complete the planned dive. In order for this to be accurate, under " "_Gas options_, specify an appropriate surface air consumption (SAC) rate for " "_Bottom SAC_. Suitable values are between 15 l/min and 30 l/min, with novice " "divers or difficult dives requiring SAC rates closer to 30l/min." msgstr "" #. type: Plain text -#: user-manual.txt:3175 +#: user-manual.txt:3140 msgid "" -"Define the amount of gas that the cylinder must have at the end of the " -"bottom section of the dive just before ascent. A value of 50 bar is often " -"used. The reason for this reserve gas is to provide for the possible need to " -"bring one's buddy to the surface using gas sharing. How much gas is used in " -"sharing depends on the depth of the ascent. This can be a bit hard to " -"estimate, so most agencies assume a fixed amount of gas, or actually of " -"pressure e.g. 40 or 50 bar or 25% or 33% (rule of thirds). But _Subsurface_ " -"can do better because it knows about the ascent and that is why we add the " -"amount of gas during the ascent (i.e. the \"deco gas“). Subsurface still " -"uses a fixed pressure „reserve“ but that is supposed to be for the " -"additional gas used around the realisation that there is a problem and one's " -"pulse rate goes up when one starts to buddy breathe. This reserve amount is " -"user configurable." +"Define the amount of gas the cylinder must have at the end of the bottom " +"section of the dive just before ascent. A value of 50 bar is often used. The " +"reason for this reserve gas is to provide for the possible need to bring a " +"buddy to the surface using gas sharing. How much gas is used in sharing " +"depends on the depth of the ascent. This can be difficult to estimate, so " +"most agencies assume a fixed amount of gas, or actually of pressure e.g. 40 " +"or 50 bar or 25% or 33% (rule of thirds). But _Subsurface_ can do better " +"because it knows about the ascent and that is why we add the amount of gas " +"during the ascent (i.e. the \"deco gas“). Subsurface still uses a fixed " +"pressure \"reserve\" but that's supposed to be for the additional gas used " +"when there's a problem and your pulse rate goes up when you start to buddy " +"breathe. This reserve amount is user configurable." msgstr "" #. type: Plain text -#: user-manual.txt:3183 +#: user-manual.txt:3148 msgid "" "Define the depth of the dive by dragging the waypoints (white dots) on the " "dive profile or (even better) defining the appropriate depths using the " @@ -6446,18 +6513,18 @@ msgid "" msgstr "" #. type: Plain text -#: user-manual.txt:3186 +#: user-manual.txt:3151 msgid "" "The ascent speed can be changed. The default ascent speeds are those " "considered safe for recreational divers." msgstr "" #. type: Plain text -#: user-manual.txt:3194 +#: user-manual.txt:3159 msgid "" -"The dive profile in the planner indicates the maximum dive time within no-" -"deco limits using the Bühlmann ZH-L16 algorithm and the gas and depth " -"settings specified as described above. The _Subsurface_ planner allows rapid " +"The dive profile in the planner shows the maximum dive time within no-deco " +"limits using the Bühlmann ZH-L16 algorithm and the gas and depth settings " +"specified as described above. The _Subsurface_ planner allows rapid " "assessment of dive duration as a function of dive depth, given the nitrogen " "load incurred during previous dives. The dive plan includes estimates of the " "amount of air/gas used, depending on the cylinder settings specified under " @@ -6469,69 +6536,69 @@ msgid "" msgstr "" #. type: Plain text -#: user-manual.txt:3198 +#: user-manual.txt:3163 msgid "" -"Below is an image of a dive plan for a recreational dive at 30 metres. " +"Below is an image of a dive plan for a recreational dive at 30 meters. " "Although the no-deco limit (NDL) is 23 minutes, the duration of the dive is " -"limited by the amount of air in the cylinder, reflected by the information " -"in the text box at the bottom right of the panel that requires sufficient " -"air for buddy-sharing during the ascent." +"limited by the amount of air in the cylinder. That is shown in the text box " +"at the bottom right of the panel, requiring sufficient air for buddy-sharing " +"during ascent." msgstr "" #. type: Target for macro image -#: user-manual.txt:3199 +#: user-manual.txt:3164 #, no-wrap msgid "images/rec_diveplan.jpg" msgstr "images/rec_diveplan.jpg" #. type: Title ==== -#: user-manual.txt:3201 +#: user-manual.txt:3166 #, no-wrap msgid "Non-recreational open circuit dives, including decompression" msgstr "" #. type: Plain text -#: user-manual.txt:3205 +#: user-manual.txt:3170 msgid "" "Non-recreational dive planning involves exceeding the no-deco limits and/or " -"using multiple breathing gases. Such dives are planned in three stages:" +"using multiple breathing gases. These dives are planned in three stages:" msgstr "" #. type: Plain text -#: user-manual.txt:3216 +#: user-manual.txt:3182 #, no-wrap msgid "" -"*a) Nitrogen management*: This is performed by specifying the rates for descent and ascent,\n" +"*a) Nitrogen management*: This is done by specifying the rates for descent and ascent,\n" "as well as the deco model (GFLow, GFHigh or Conservatism level) under the headings _Rates_ and _Planning_\n" "to the bottom left of the planning screen. Two deco models are supported the Bühlmann model and the VPM-B\n" "model. Select one of the two models. When selecting the Bühlmann model, the gradient factors (GF_high and GF_low\n" "need to be specified. 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 values 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" +"used without changing the original values in the _Preferences_.\n" +"Gradient Factor settings strongly affect the calculated ceilings and their depths.\n" +"A very low GFLow value brings on decompression stops early during the dive.\n" " ** For more information about Gradient factors, see the section on xref:S_GradientFactors[Gradient Factor Preference settings].\n" msgstr "" #. type: Plain text -#: user-manual.txt:3221 +#: user-manual.txt:3187 msgid "" "If the VPM-B model is selected, the Conservatism_level needs to be specified " "on a scale of 0 (least conservative) to 4 (most conservative). This model " "tends to give deco stops at deeper levels than the Bühlmann model and often " "results in slightly shorter dive durations than the Bühlmann model. When " -"selecting one of these models, keep in mind that they are NOT exact " -"physiological models but only mathematical models that appear to work in " -"practice." +"selecting one of these models, keep in mind they are NOT exact physiological " +"models but only mathematical models that appear to work in practice." msgstr "" #. type: Plain text -#: user-manual.txt:3223 +#: user-manual.txt:3189 msgid "For more information external to this manual see:" msgstr "" #. type: Plain text -#: user-manual.txt:3225 +#: user-manual.txt:3191 msgid "" "link:http://www.tek-dive.com/portal/upload/M-Values.pdf[Understanding M-" "values by Erik Baker, _Immersed_ Vol. 3, No. 3.]" @@ -6540,7 +6607,7 @@ msgstr "" "values by Erik Baker, _Immersed_ Vol. 3, No. 3.]" #. type: Plain text -#: user-manual.txt:3226 +#: user-manual.txt:3192 msgid "" "link:http://www.rebreatherworld.com/general-and-new-to-rebreather-" "articles/5037-gradient-factors-for-dummies.html[Gradient factors for " @@ -6551,7 +6618,7 @@ msgstr "" "dummies, by Kevin Watts]" #. type: Plain text -#: user-manual.txt:3228 +#: user-manual.txt:3194 msgid "" "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" @@ -6566,21 +6633,21 @@ msgstr "" "traite à la fois des modèles de décompression Bühlmann et VPM-B." #. type: Plain text -#: user-manual.txt:3236 +#: user-manual.txt:3202 msgid "" "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 by a " -"light grey line on the dive profile. 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." +"and is specified for several depth ranges, using the average (or mean) depth " +"as a yardstick. The mean depth of the dive plan is shown by a light grey " +"line on the dive profile. 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, the descent phase of the planned dive will be " +"at the maximal descent rate specified in the _Rates_ section of the dive " +"setup." msgstr "" #. type: Plain text -#: user-manual.txt:3245 +#: user-manual.txt:3211 #, no-wrap msgid "" "*b) Oxygen management*: In the *Gas Options* part of the dive specification, the maximum partial\n" @@ -6594,74 +6661,76 @@ msgid "" msgstr "" #. type: Plain text -#: user-manual.txt:3259 +#: user-manual.txt:3228 #, no-wrap msgid "" -"*c) Gas management*: With open-circuit dives this is a primary consideration. One needs to keep within the limits of the amount of gas within the dive\n" +"*c) Gas management*: With open-circuit dives this is a primary\n" +"consideration. Divers need to keep within the limits of the amount of\n" +"gas within the dive\n" "cylinder(s), allowing for an appropriate margin for a 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" +"liters/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 15-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" +"dive (_deco SAC_). Values of 15-30 l/min are common. For good gas management, a guess\n" +"is not sufficient and you needs to\n" +"monitor gas consumption on a regular basis, dependent on different dive conditions and/or equipment.\n" "The planner calculates the total volume of gas used during the dive and issues 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" +"if you exceeds the total amount of gas available. Good practice demands that divers not dive to\n" +"the limit of the gas supply but that an appropriate reserve is kept\n" +"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:3271 +#: user-manual.txt:3240 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 bue 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. It is NOT necessary to specify the ascent part of the dive since the " -"planner calculates this, based on the settings that have been specified. If " -"any of the management limits (for nitrogen, oxygen or gas) is exceeded, the " -"surface above the dive profile changes from BLUE to RED." +"Now you can start the detailed time-depth planning of the dive. _Subsurface_ " +"offers an unique graphical interface for doing planning. Themechanics are " +"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 blue 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 the profile reflects the intended dive. Drag the waypoints to " +"represent the depth and duration of the dive. It is NOT necessary to specify " +"the ascent part of the dive since the planner calculates this, based on the " +"settings that have been specified. If any of the management limits (for " +"nitrogen, oxygen or gas) are exceeded, the surface above the dive profile " +"changes from BLUE to RED." msgstr "" #. type: Plain text -#: user-manual.txt:3283 +#: user-manual.txt:3252 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 _Available Gases_ table. 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." +"table on the left of the dive planner panel. Be sure the _Used Gas_ value in " +"each row of that table corresponds to one of the gas mixtures specified in " +"the _Available Gases_ table. 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 fulfill decompression requirements for that dive. A waypoint can be " +"moved by selecting it and by using the arrow keys. The waypoints listed in " +"the _Dive Planner Points_ dialogue can be edited by hand in order to get a " +"precise presentation of the dive plan. In fact, you can create the whole " +"dive profile by editing the _Dive Planner Points_ dialog." msgstr "" #. type: Plain text -#: user-manual.txt:3291 +#: user-manual.txt:3260 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." +"Show 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. These changes " +"can be deleted by right-clicking the gas change and manually creating a gas " +"change by right-clicking on the appropriate waypoint." msgstr "" #. type: Plain text -#: user-manual.txt:3300 +#: user-manual.txt:3269 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 " @@ -6674,34 +6743,34 @@ msgid "" msgstr "" #. type: Plain text -#: user-manual.txt:3303 +#: user-manual.txt:3272 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:3304 +#: user-manual.txt:3273 #, no-wrap msgid "images/DivePlanner2_f20.jpg" msgstr "images/DivePlanner2_f20.jpg" #. type: Plain text -#: user-manual.txt:3309 +#: user-manual.txt:3278 msgid "" -"Once the above has been completed, one can save it by clicking the _Save_ " -"button towards the top middle of the planner. The saved dive plan will " -"appear in the *Dive List* panel of _Subsurface_." +"Once the above steps have been completed, save by clicking the _Save_ button " +"towards the top middle of the planner. The saved dive plan will appear in " +"the *Dive List* panel of _Subsurface_." msgstr "" #. type: Plain text -#: user-manual.txt:3311 +#: user-manual.txt:3280 #, no-wrap msgid "*The dive plan details*\n" msgstr "" #. type: Plain text -#: user-manual.txt:3319 +#: user-manual.txt:3288 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 " @@ -6714,7 +6783,7 @@ msgid "" msgstr "" #. type: Plain text -#: user-manual.txt:3324 +#: user-manual.txt:3293 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 " @@ -6724,13 +6793,13 @@ msgid "" msgstr "" #. type: Title === -#: user-manual.txt:3325 +#: user-manual.txt:3294 #, no-wrap msgid "Planning pSCR dives" msgstr "" #. type: Plain text -#: user-manual.txt:3340 +#: user-manual.txt:3309 #, no-wrap msgid "" "To plan a dive using a passive semi-closed rebreather (pSCR), select _pSCR_ rather than\n" @@ -6739,7 +6808,7 @@ msgid "" "from the main menu, where the gas consumption calculation takes into account the pSCR dump\n" "ratio (default 10:1) as well as the metabolism rate. The calculation also takes the oxygen drop\n" "accross the mouthpiece of the rebreather into account. If the\n" -"pO~2~ drops below what is considered a save value, a warning appears in the _Dive plan\n" +"pO~2~ drops below what is considered safe, a warning appears in the _Dive plan\n" "details_. A typical pSCR configuration is with a single cylinder and one or more bail-out\n" "cylinders. Therefore the setup of the _Available gases_ and the _Dive planner points_ tables\n" "are very similar to that of a CCR dive plan, described below. However, no oxygen setpoints\n" @@ -6749,26 +6818,26 @@ msgid "" msgstr "" #. type: Target for macro image -#: user-manual.txt:3341 +#: user-manual.txt:3310 #, no-wrap msgid "images/Planner_pSCR1_f20.jpg" msgstr "images/Planner_pSCR1_f20.jpg" #. type: Title === -#: user-manual.txt:3344 +#: user-manual.txt:3313 #, no-wrap msgid "Planning CCR dives" msgstr "" #. type: Plain text -#: user-manual.txt:3348 +#: user-manual.txt:3317 msgid "" "To plan a dive using a closed circuit rebreather, select the _CCR_ option in " "the dropdown list, circled in blue in the image below." msgstr "" #. type: Plain text -#: user-manual.txt:3352 +#: user-manual.txt:3321 #, no-wrap msgid "" "*Available gases*: In the _Available gases_ table, enter the cylinder information for the\n" @@ -6777,60 +6846,60 @@ msgid "" msgstr "" #. type: Plain text -#: user-manual.txt:3362 +#: user-manual.txt:3331 #, no-wrap msgid "" "*Entering setpoints*: Specify a default setpoint in the Preferences tab, by selecting _File -> Preferences -> Graph_ from\n" "the main menu. All user-entered segments in the _Dive planner points_ table\n" "use the default setpoint value. Then, different setpoints can be specified for dive segments\n" "in the _Dive planner points_ table. A zero setpoint\n" -"means the diver bails out to open circuit mode for that segment. The decompression is always calculated\n" +"means the diver bails out to open circuit mode for that segment. Decompression is always calculated\n" "using the setpoint of the last manually entered segment. So, to plan a bail out ascent for a\n" "CCR dive, add a one-minute dive segment to the end with a setpoint value of 0. The decompression\n" -"algorithm does not switch deco-gases automatically while in CCR mode (i.e. when a positive setpoint is specified) but,\n" -"of course, this is calculated for bail out ascents.\n" +"algorithm does not switch deco-gases automatically while in CCR mode (i.e. when a positive setpoint is specified) but\n" +"this is calculated for bail out ascents.\n" msgstr "" #. type: Plain text -#: user-manual.txt:3364 +#: user-manual.txt:3333 msgid "" "The dive profile for a CCR dive may look something like the image below." msgstr "" #. type: Target for macro image -#: user-manual.txt:3365 +#: user-manual.txt:3334 #, no-wrap msgid "images/Planner_CCR1_f20.jpg" msgstr "images/Planner_CCR1_f20.jpg" #. type: Plain text -#: user-manual.txt:3369 +#: user-manual.txt:3338 msgid "" "Note that, in the _Dive plan details_, the gas consumption for a CCR segment " -"is not calculated, so gas consumptions of 0 litres are the norm." +"is not calculated, so gas consumptions of 0 liters are the norm." msgstr "" #. type: Title === -#: user-manual.txt:3371 +#: user-manual.txt:3340 #, no-wrap msgid "Modifying an existing dive plan" msgstr "" #. type: Plain text -#: user-manual.txt:3378 +#: user-manual.txt:3347 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." +"List*, like any other dive log. Within the *Dive List* there is no way to " +"change a saved dive plan. To change 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, letting changes be made and " +"saved as usual." msgstr "" #. type: Plain text -#: user-manual.txt:3384 +#: user-manual.txt:3353 msgid "" -"In addition there is the option \"Save new\". This keeps the original " +"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 " @@ -6838,56 +6907,56 @@ msgid "" msgstr "" #. type: Title === -#: user-manual.txt:3385 +#: user-manual.txt:3354 #, no-wrap msgid "Planning for repetitive dives" msgstr "" #. type: Plain text -#: user-manual.txt:3392 +#: user-manual.txt:3361 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." +"repetitive dive set are specified appropriately in the top left-hand _Start " +"Time_ field. _Subsurface_ calculates the gas loading figures and the affect " +"of the first dive is evaluated on later dives." msgstr "" #. type: Plain text -#: user-manual.txt:3398 +#: user-manual.txt:3367 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." +"If you have just completed a long/deep dive and are planning another dive, " +"then highlight, in the *Dive List*, the dive that has just been done then " +"activate the planner. Depending on the start time of the planned dive, the " +"planner takes into account the gas loading during the completed dive and " +"plans accordingly." msgstr "" #. type: Plain text -#: user-manual.txt:3403 +#: user-manual.txt:3372 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." +"template dive can be created conforming to one of the configurations. If you " +"want to plan a dive using this configuration, 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:3404 +#: user-manual.txt:3373 #, no-wrap msgid "Printing the dive plan" msgstr "" #. type: Plain text -#: user-manual.txt:3409 +#: user-manual.txt:3378 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." +"Plan Details_ for wet notes. You can also cut and paste the _Dive Plan " +"Details_ to include in a text file or word processing document." msgstr "" #. type: Plain text -#: user-manual.txt:3419 +#: user-manual.txt:3388 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 " @@ -6897,19 +6966,19 @@ msgid "" "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 " +"way to print the dive plan is to use the _File -> Print_ function 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:3420 +#: user-manual.txt:3389 #, no-wrap msgid "Description of the Subsurface Main Menu items" msgstr "Description des éléments du menu principal de Subsurface" #. type: Plain text -#: user-manual.txt:3425 +#: user-manual.txt:3394 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 " @@ -6920,13 +6989,13 @@ msgstr "" "des sections de ce manuel traitant des opérations relatives." #. type: Title === -#: user-manual.txt:3426 +#: user-manual.txt:3395 #, no-wrap msgid "File" msgstr "Fichier" #. type: Plain text -#: user-manual.txt:3429 +#: user-manual.txt:3398 msgid "" "<<S_NewLogbook,_New Logbook_>> - Close the currently open dive logbook and " "clear all dive information." @@ -6935,47 +7004,54 @@ msgstr "" "actuellement ouvert et supprime toutes les informations de plongées." #. type: Plain text -#: user-manual.txt:3431 +#: user-manual.txt:3400 +#, fuzzy +#| msgid "" +#| "_Open logbook_ - This opens the file manager in order to select a dive " +#| "logbook to open." msgid "" -"_Open logbook_ - This opens the file manager in order to select a dive " -"logbook to open." +"_Open logbook_ - Open the file manager to select a dive logbook to open." msgstr "" "_Ouvrir un carnet de plongée_ - Cela ouvre une fenêtre pour sélectionner le " "carnet de plongée à ouvrir." #. type: Plain text -#: user-manual.txt:3432 +#: user-manual.txt:3401 msgid "" "_Open cloud storage_ - Open the dive log previously saved in " "<<S_Cloud_storage,_Cloud storage_>>." msgstr "" #. type: Plain text -#: user-manual.txt:3433 -msgid "_Save_ - Save the dive logbook that is currently open." +#: user-manual.txt:3402 +#, fuzzy +#| msgid "_Save_ - Save the dive logbook that is currently open." +msgid "_Save_ - Save the dive logbook currently open." msgstr "" "_Sauvegarder_ - Enregistrer le carnet de plongée qui est actuellement ouvert." #. type: Plain text -#: user-manual.txt:3434 +#: user-manual.txt:3403 msgid "" "_Save to cloud storage_ - Save the current dive log to <<S_Cloud_storage," "_Cloud storage_>>." msgstr "" #. type: Plain text -#: user-manual.txt:3435 +#: user-manual.txt:3404 msgid "_Save as_ - Save the current logbook under a different file name." msgstr "" "_Enregsitrer sous_ - Enregistrer le carnet actuel sous un nom différent." #. type: Plain text -#: user-manual.txt:3436 -msgid "_Close_ - Close the dive logbook that is currently open." +#: user-manual.txt:3405 +#, fuzzy +#| msgid "_Close_ - Close the dive logbook that is currently open." +msgid "_Close_ - Close the dive logbook currently open." msgstr "_Fermer_ - Fermer le carnet de plongée actuellement ouvert." #. type: Plain text -#: user-manual.txt:3438 +#: user-manual.txt:3407 msgid "" "<<S_ExportLog,_Export_>> - Export the currently open dive logbook (or the " "selected dives in the logbook) to one of several formats." @@ -6985,34 +7061,34 @@ msgstr "" "formats." #. type: Plain text -#: user-manual.txt:3439 +#: user-manual.txt:3408 msgid "<<S_PrintDivelog,_Print_>> - Print the currently open logbook." msgstr "" "<<S_PrintDivelog,_Imprimer_>> - Imprimer le carnet de plongée actuellement " "ouvert." #. type: Plain text -#: user-manual.txt:3440 +#: user-manual.txt:3409 msgid "<<S_Preferences,_Preferences_>> - Set the _Subsurface_ preferences." msgstr "" "<<S_Preferences,_Préférences_>> - Définir les préférences de _Subsurface_." #. type: Plain text -#: user-manual.txt:3441 +#: user-manual.txt:3410 msgid "" "<<S_FindMovedImages, _Find moved images_>> - If photos taken during dives " "have been moved to" msgstr "" #. type: Plain text -#: user-manual.txt:3442 +#: user-manual.txt:3411 msgid "" "a different disk or directory, locate them and link them to the appropriate " "dives." msgstr "" #. type: Plain text -#: user-manual.txt:3443 +#: user-manual.txt:3412 msgid "" "<<S_Configure,_Configure dive computer_>> - Edit the configuration of a dive " "computer." @@ -7021,18 +7097,18 @@ msgstr "" "configuration d'un ordinateur de plongée." #. type: Plain text -#: user-manual.txt:3444 +#: user-manual.txt:3413 msgid "_Quit_ - Quit _Subsurface_." msgstr "_Quitter_ - Quitter _Subsurface_." #. type: Title === -#: user-manual.txt:3445 +#: user-manual.txt:3414 #, no-wrap msgid "Import" msgstr "Importer" #. type: Plain text -#: user-manual.txt:3448 +#: user-manual.txt:3417 msgid "" "<<S_ImportDiveComputer,_Import from dive computer_>> - Import dive " "information from a dive computer." @@ -7041,7 +7117,7 @@ msgstr "" "Importer des informations de plongées à partir de l'ordinateur de plongée." #. type: Plain text -#: user-manual.txt:3450 +#: user-manual.txt:3419 msgid "" "<<Unified_import,_Import Log Files_>> - Import dive information from a file " "in in a _Subsurface_-compatible format." @@ -7051,7 +7127,7 @@ msgstr "" "_Subsurface_." #. type: Plain text -#: user-manual.txt:3452 +#: user-manual.txt:3421 msgid "" "<<S_Companion,_Import GPS data from Subsurface web service_>> - Load GPS " "coordinates from the _Subsurface_ mobile phone app." @@ -7061,7 +7137,7 @@ msgstr "" "(téléphones et tablettes)." #. type: Plain text -#: user-manual.txt:3454 +#: user-manual.txt:3423 msgid "" "<<S_ImportingDivelogsDe,_Import from Divelogs.de_>> - Import dive " "information from _www.Divelogs.de_." @@ -7070,13 +7146,13 @@ msgstr "" "informations de plongées à partir de _www.Divelogs.de_." #. type: Title === -#: user-manual.txt:3455 +#: user-manual.txt:3424 #, no-wrap msgid "Log" msgstr "Journal (log)" #. type: Plain text -#: user-manual.txt:3457 +#: user-manual.txt:3426 msgid "" "<<S_EnterData,_Add Dive_>> - Manually add a new dive to the *Dive List* " "panel." @@ -7085,22 +7161,19 @@ msgstr "" "plongée au panneau de la *liste des plongées*." #. type: Plain text -#: user-manual.txt:3458 +#: user-manual.txt:3427 msgid "" -"_Edit dive_ - Edit a dive of which the profile was entered by hande and not " -"from a dive computer." +"_Edit dive_ - Edit a dive where the profile was entered by hand and not from " +"a dive computer." msgstr "" #. type: Plain text -#: user-manual.txt:3459 -msgid "" -"<<S_DivePlanner,_Plan Dive_>> - This feature allows the planning of dives." -msgstr "" -"<<S_DivePlanner,_Planifier une plongée_>> - Cette fonctionnalité permet de " -"planifier des plongées." +#: user-manual.txt:3428 +msgid "<<S_DivePlanner,_Plan Dive_>> - Plan dives." +msgstr "<<S_DivePlanner,_Planifier une plongée_>> - Planifier des plongées." #. type: Plain text -#: user-manual.txt:3460 +#: user-manual.txt:3429 msgid "" "<<S_Replan,_Edit dive in planner_>> - Edit a dive plan that has been saved " "into the *Dive List*." @@ -7109,17 +7182,17 @@ msgstr "" "plongée planifiée qui a été enregistrée dans la *liste des plongées*." #. type: Plain text -#: user-manual.txt:3462 +#: user-manual.txt:3431 msgid "" -"<<S_CopyComponents,_Copy dive components_>> - By selecting this option, one " -"can copy information from several fields of a dive log onto the clipboard." +"<<S_CopyComponents,_Copy dive components_>> - Copy information from several " +"fields of a dive log onto the clipboard." msgstr "" -"<<S_CopyComponents,_Copier les composants de la plongée_>> - En " -"sélectionnant cette option, vous pouvez copier les informations de plusieurs " -"champs d'un journal de plongée vers le presse-papier." +"<<S_CopyComponents,_Copier les composants de la plongée_>> - Copier les " +"informations de plusieurs champs d'un journal de plongée vers le presse-" +"papier." #. type: Plain text -#: user-manual.txt:3464 +#: user-manual.txt:3433 msgid "" "_Paste dive components_ - Paste, into the selected dives in the *Dive List*, " "the information copied using the _Copy dive components_ option." @@ -7129,7 +7202,7 @@ msgstr "" "préalable avec l'option _Copier les composants de la plongée_." #. type: Plain text -#: user-manual.txt:3466 +#: user-manual.txt:3435 msgid "" "<<S_Renumber,_Renumber_>> - Renumber the dives listed in the *Dive List* " "panel." @@ -7138,7 +7211,7 @@ msgstr "" "le panneau de la *liste des plongées*." #. type: Plain text -#: user-manual.txt:3468 +#: user-manual.txt:3437 msgid "" "<<S_Group,_Auto Group_>> - Group the dives in the *Dive List* panel into " "dive trips." @@ -7147,16 +7220,16 @@ msgstr "" "*liste des plongées* dans des voyages de plongées." #. type: Plain text -#: user-manual.txt:3469 +#: user-manual.txt:3438 msgid "" "<<S_DeviceNames,_Edit Device Names_>> - Edit the names of dive computers to " -"facilitate your logs." +"coordinate your logs." msgstr "" "<<S_DeviceNames,_Editer les noms des ordinateurs de plongée_>> - Modifier " -"les noms des ordinateurs de plongée pour faciliter vos journaux (logs)." +"les noms des ordinateurs de plongée pour coordonner vos journaux (logs)." #. type: Plain text -#: user-manual.txt:3470 +#: user-manual.txt:3439 msgid "" "<<S_Filter,_Filter divelist_>> - Select only some dives, based on specific " "tags or dive criteria." @@ -7165,48 +7238,47 @@ msgstr "" "certaines plongées, à partir de tags ou de critères de plongées." #. type: Title === -#: user-manual.txt:3471 +#: user-manual.txt:3440 #, no-wrap msgid "View" msgstr "Vue" #. type: Plain text -#: user-manual.txt:3474 +#: user-manual.txt:3443 msgid "" -"<<S_ViewPanels,_All_>> - View the four main _Subsurface_ panels " -"simmultaneously." +"<<S_ViewPanels,_All_>> - View the four main _Subsurface_ panels all at once." msgstr "" "<<S_ViewPanels,_Tout_>> - Affiche les quatre panneaux principaux de " "_Subsurface_ simultanément." #. type: Plain text -#: user-manual.txt:3475 +#: user-manual.txt:3444 msgid "<<S_ViewPanels,_Dive List_>> - View only the *Dive List* panel." msgstr "" "<<S_ViewPanels,_Liste des plongées_>> - Affiche uniquement le panneau de la " "*liste des plongées*." #. type: Plain text -#: user-manual.txt:3476 +#: user-manual.txt:3445 msgid "<<S_ViewPanels,_Profile_>> - View only the *Dive Profile* panel." msgstr "" "<<S_ViewPanels,_Profil_>> - Affiche uniquement le panneau du *profil de la " "plongée*." #. type: Plain text -#: user-manual.txt:3477 +#: user-manual.txt:3446 msgid "<<S_ViewPanels,_Info_>> - View only the *Notes* panel." msgstr "<<S_ViewPanels,_Info_>> - Affiche uniquement le panneau des *notes*." #. type: Plain text -#: user-manual.txt:3478 +#: user-manual.txt:3447 msgid "<<S_ViewPanels,_Globe_>> - View only the *World Map* panel." msgstr "" "<<S_ViewPanels,_Globe_>> - Affiche uniquement le panneau de la *carte " "mondiale*." #. type: Plain text -#: user-manual.txt:3480 +#: user-manual.txt:3449 msgid "" "_Yearly Statistics_ - Display summary statistics about dives during this and " "past years." @@ -7215,35 +7287,30 @@ msgstr "" "plongées effectuées." #. type: Plain text -#: user-manual.txt:3481 +#: user-manual.txt:3450 msgid "" -"_Prev DC_ - If a single dive was logged from more than one dive computer, " -"switch to data from" +"_Prev DC_ - Switch to data from previous dive computer, if a single dive was " +"logged from more than one." msgstr "" #. type: Plain text -#: user-manual.txt:3482 -msgid "previous dive computer." -msgstr "ordinateur de plongée précédent." - -#. type: Plain text -#: user-manual.txt:3483 +#: user-manual.txt:3451 msgid "_Next DC_ - Switch to next dive computer." msgstr "_Ordinateur suivant_ - Passer à l'ordinateur de plongée suivant." #. type: Plain text -#: user-manual.txt:3484 +#: user-manual.txt:3452 msgid "_Full Screen_ - Toggles Full Screen mode." msgstr "_Plein écran_ - Passer en mode plein écran." #. type: Title === -#: user-manual.txt:3485 +#: user-manual.txt:3453 #, no-wrap msgid "Share on" msgstr "" #. type: Plain text -#: user-manual.txt:3487 +#: user-manual.txt:3455 msgid "" "<<S_Facebook,_Facebook_>> - Share the currently selected dive on your " "Facebook timeline." @@ -7252,13 +7319,13 @@ msgstr "" "Facebook." #. type: Title === -#: user-manual.txt:3489 +#: user-manual.txt:3457 #, no-wrap msgid "Help" msgstr "Aide" #. type: Plain text -#: user-manual.txt:3492 +#: user-manual.txt:3460 msgid "" "_About Subsurface_ - Show a panel with the version number of _Subsurface_ as " "well as licensing information." @@ -7267,7 +7334,7 @@ msgstr "" "_Subsurface_ ainsi que les informations de licence." #. type: Plain text -#: user-manual.txt:3494 +#: user-manual.txt:3462 msgid "" "_Check for updates_ - Find out whether a newer version of Subsurface is " "available on the http://subsurface-divelog.org/[_Subsurface_ web site]." @@ -7277,7 +7344,7 @@ msgstr "" "_Subsurface_ ]." #. type: Plain text -#: user-manual.txt:3496 +#: user-manual.txt:3464 msgid "" "<<S_UserSurvey,_User survey_>> - Help to make _Subsurface_ even better by " "taking part in our user survey or by completing another survey if your " @@ -7288,42 +7355,47 @@ msgstr "" "sondage, si vos habitudes de plongées ont changées." #. type: Plain text -#: user-manual.txt:3497 +#: user-manual.txt:3465 msgid "_User manual_ - Open a window showing this user manual." msgstr "" "_Manuel utilisateur_ - Ouvre une fenêtre affichant ce manuel utilisateur." #. type: Title == -#: user-manual.txt:3500 +#: user-manual.txt:3468 #, no-wrap msgid "APPENDIX A: Operating system specific information for importing dive information from a dive computer." msgstr "ANNEXE A : informations spécifiques au système d'exploitation utilisé pour importer les informations de plongées depuis un ordinateur de plongée." #. type: Title === -#: user-manual.txt:3502 +#: user-manual.txt:3470 #, no-wrap msgid "Make sure that the OS has the required drivers installed" msgstr "Assurez-vous que les pilotes (drivers) nécessaires sont installés" #. type: Named 'icon' AttributeList argument for style 'icon' -#: user-manual.txt:3503 +#: user-manual.txt:3471 #, no-wrap msgid "images/icons/drivers.jpg" msgstr "images/icons/drivers.jpg" #. type: Plain text -#: user-manual.txt:3508 +#: user-manual.txt:3476 +#, fuzzy +#| 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)." 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)." +"in order to communicate with the dive computer, the way the dive computer " +"prefers (e.g. Bluetooth, USB, infra-red)." msgstr "" "Le système d'exploitation de l'ordinateur nécessite les bons pilotes pour " "communiquer avec l'ordinateur de plongée de la façon utilisée par " "l'ordinateur de plongée (Bluetooth, USB, infra-rouge)." #. type: Plain text -#: user-manual.txt:3514 +#: user-manual.txt:3482 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 " @@ -7337,7 +7409,7 @@ msgstr "" "particulièrement pour certaines technologies telles que l'infra-rouge." #. type: Plain text -#: user-manual.txt:3518 +#: user-manual.txt:3486 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 " @@ -7348,7 +7420,7 @@ msgstr "" "port USB de son ordinateur de bureau." #. type: Plain text -#: user-manual.txt:3525 +#: user-manual.txt:3493 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 " @@ -7366,26 +7438,33 @@ msgstr "" "documents et logiciels Silicon Labs]." #. type: Title === -#: user-manual.txt:3527 +#: user-manual.txt:3495 #, no-wrap msgid "How to Find the Device Name for USB devices and set its write permission" msgstr "Comment trouver le nom du périphérique branché sur USB et paramétrer les permissions en écriture" #. type: Named 'icon' AttributeList argument for style 'icon' -#: user-manual.txt:3528 +#: user-manual.txt:3496 #, no-wrap msgid "images/icons/usb.jpg" msgstr "images/icons/usb.jpg" #. type: Plain text -#: user-manual.txt:3536 +#: user-manual.txt:3504 +#, fuzzy +#| 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:" 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:" +"When connecting a dive computer by using a USB connector, usually " +"_Subsurface_ will either propose a drop down list with 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 ways to find out what the device name is:" msgstr "" "Lorsqu'un utilisateur connecte un ordinateur de plongée en utilisant l'USB, " "généralement _Subsurface_ proposera soit une liste déroulante contenant le " @@ -7395,7 +7474,7 @@ msgstr "" "nom de votre périphérique ;" #. type: Plain text -#: user-manual.txt:3541 +#: user-manual.txt:3509 msgid "" "Simply try COM1, COM2, etc. The drop down list should contain all connected " "COM devices." @@ -7404,56 +7483,56 @@ msgstr "" "tous les périphériques COM connectés." #. type: Title ==== -#: user-manual.txt:3542 user-manual.txt:3636 +#: user-manual.txt:3510 user-manual.txt:3608 #, no-wrap msgid "On MacOS:" msgstr "Sur MacOS :" #. type: Plain text -#: user-manual.txt:3545 +#: user-manual.txt:3513 msgid "The drop down box should find all connected dive computers." msgstr "" "La liste déroulante devrait contenir tous les ordinateurs de plongée " "connectés." #. type: Block title -#: user-manual.txt:3546 +#: user-manual.txt:3514 #, no-wrap msgid "On Linux:" msgstr "Sur Linux :" #. type: Plain text -#: user-manual.txt:3549 +#: user-manual.txt:3517 msgid "There is a definitive way to find the port:" msgstr "Il existe un moyen sûr de trouver le port :" #. type: Plain text -#: user-manual.txt:3551 +#: user-manual.txt:3519 msgid "Disconnect the USB cable from the dive computer" msgstr "Déconnecter le cable USB de l'ordinateur de plongée" #. type: Plain text -#: user-manual.txt:3552 +#: user-manual.txt:3520 msgid "Open a terminal" msgstr "Ouvrir un terminal" #. type: Plain text -#: user-manual.txt:3553 user-manual.txt:3555 +#: user-manual.txt:3521 user-manual.txt:3523 msgid "Type the command: 'dmesg' and press enter" msgstr "Taper la commande 'dmesg' et appuyer sur la touche Entrer" #. type: Plain text -#: user-manual.txt:3554 +#: user-manual.txt:3522 msgid "Plug in the USB cable of the dive computer" msgstr "Connecter le cable USB de l'ordinateur de plongée" #. type: Plain text -#: user-manual.txt:3557 +#: user-manual.txt:3525 msgid "A message similar to this one should appear:" msgstr "Un message similaire à celui-ci devrait apparaitre :" #. type: Plain text -#: user-manual.txt:3573 +#: user-manual.txt:3541 #, no-wrap msgid "" "\tusb 2-1.1: new full speed USB device number 14 using ehci_hcd\n" @@ -7489,7 +7568,7 @@ msgstr "" "\tftdi_sio: v1.6.0:USB FTDI Serial Converters Driver\n" #. type: Plain text -#: user-manual.txt:3578 +#: user-manual.txt:3546 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 " @@ -7501,19 +7580,30 @@ msgstr "" "que Subsurface utilise le bon port USB." #. type: Plain text -#: user-manual.txt:3580 -msgid "Ensuring that the user has write permission to the USB serial port:" +#: user-manual.txt:3548 +#, fuzzy +#| msgid "Ensuring that the user has write permission to the USB serial port:" +msgid "Ensuring the user has write permission to the USB serial port:" msgstr "" "S'assurer que l'utilisateur possède les droits d'écriture sur le port série " "USB :" #. type: Plain text -#: user-manual.txt:3586 +#: user-manual.txt:3558 +#, fuzzy +#| 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'." 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'." +"who are members special group that can be e.g. +dialout+ or +uucp+. This " +"can be verified by listing the appropriate device permissions e.g. by +ls -" +"l /dev/ttyUSB0+. Note that the number in the file name depends on how many " +"USB devices you have connected, and must be adjusted appropriately. If one " +"is not root, one may not be a member of that group and won't be able to use " +"the USB port. Let us assume one's username is 'johnB'." msgstr "" "Sur les systèmes similaires à Unix, les ports USB ne peuvent être accédés " "que par des utilisateurs membres du groupe +dialout+. Si vous n'êtes pas " @@ -7521,7 +7611,7 @@ msgstr "" "utiliser le port USB. Si votre nom d'utilisateur est 'johnB' :" #. type: Plain text -#: user-manual.txt:3590 +#: user-manual.txt:3562 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." @@ -7531,7 +7621,7 @@ msgstr "" "+dialout+." #. type: Plain text -#: user-manual.txt:3595 +#: user-manual.txt:3567 #, no-wrap msgid "" "Type: +id johnB+ This lists all the groups that johnB belongs to and\n" @@ -7547,15 +7637,17 @@ msgstr "" "parmi les différents IDs.\n" #. type: Plain text -#: user-manual.txt:3597 +#: user-manual.txt:3569 #, 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 "Sous certaines circonstances, les modifications ne prennent effet qu'après une déconnexionpuis reconnexion sur l'ordinateur (sous Ubuntu, par exemple)." +msgstr "" +"Sous certaines circonstances, les modifications ne prennent effet qu'après une déconnexion\n" +"puis reconnexion sur l'ordinateur (sous Ubuntu, par exemple).\n" #. type: Plain text -#: user-manual.txt:3602 +#: user-manual.txt:3574 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 " @@ -7566,28 +7658,28 @@ msgstr "" "vous devriez pouvoir importer vos plongées." #. type: Title === -#: user-manual.txt:3605 +#: user-manual.txt:3577 #, no-wrap msgid "Manually setting up Bluetooth enabled devices" msgstr "" #. type: Plain text -#: user-manual.txt:3612 +#: user-manual.txt:3584 msgid "" "For dive computers communicating through Bluetooth like the Heinrichs " "Weikamp Frog or the Shearwater Predator, Petrel and Nerd there is a " -"different procedure to get the devices name to communicate with " +"different procedure to get the device’s name to communicate with " "_Subsurface_. Follow these steps:" msgstr "" #. type: Plain text -#: user-manual.txt:3614 +#: user-manual.txt:3586 #, no-wrap -msgid "*For the dive computer, after enabling Bluetooth, ensure it is in Upload mode.*\n" +msgid "*For the dive computer, after enabling Bluetooth, be sure it is in Upload mode.*\n" msgstr "" #. type: Plain text -#: user-manual.txt:3618 +#: user-manual.txt:3590 msgid "" "For Bluetooth pairing of the dive computer, refer to the manufacturer's user " "guide. When using a Shearwater Predator/Petrel/Nerd, select _Dive Log -> " @@ -7595,13 +7687,13 @@ msgid "" msgstr "" #. type: Plain text -#: user-manual.txt:3620 +#: user-manual.txt:3592 #, no-wrap msgid "*Pair the _Subsurface_ computer with the dive computer.*\n" msgstr "" #. type: Plain text -#: user-manual.txt:3629 +#: user-manual.txt:3601 msgid "" "Bluetooth is most likely already enabled. For pairing with the dive computer " "choose _Control Panel -> Bluetooth Devices -> Add Wireless Device_. This " @@ -7613,21 +7705,21 @@ msgid "" msgstr "" #. type: Plain text -#: user-manual.txt:3632 +#: user-manual.txt:3604 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:3635 +#: user-manual.txt:3607 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:3642 +#: user-manual.txt:3614 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. " @@ -7636,33 +7728,32 @@ msgid "" msgstr "" #. type: Plain text -#: user-manual.txt:3645 +#: user-manual.txt:3617 msgid "" -"Once the pairing is completed the correct device is shown in the 'Device or " +"Once the pairing is complete, the correct device is shown in the 'Device or " "Mount Point' drop-down in the _Subsurface_ *Import* dialog." msgstr "" #. type: Title ==== -#: user-manual.txt:3646 +#: user-manual.txt:3618 #, no-wrap msgid "On Linux" msgstr "Sur Linux" #. type: Plain text -#: user-manual.txt:3654 +#: user-manual.txt:3626 msgid "" -"Ensure Bluetooth is enabled on the _Subsurface_ computer. On most common " +"Be sure 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 on the right " -"of the toolbar at the top of the screen. Users have reported difficulties " -"with some Bluetooth controllers. If you have an onboard controller, try " -"that first. It is simplest if you remove any USB Bluetooth dongles. If you " -"have a USB dongle that came with your dive computer, try that before any " -"others." +"straightforward. For instance, Gnome3 shows a Bluetooth icon on the right of " +"the toolbar at the top of the screen. Users have reported difficulties with " +"some Bluetooth controllers. If you have an onboard controller, try that " +"first. It is simplest if you remove any USB Bluetooth dongles. If you have " +"a USB dongle that came with your dive computer, try that before any others." msgstr "" #. type: Plain text -#: user-manual.txt:3658 +#: user-manual.txt:3630 msgid "" "Setting up a connection to download dives from your Bluetooth-enabled " "device, such as the _Shearwater Petrel_, is not yet an automated process and " @@ -7671,23 +7762,23 @@ msgid "" msgstr "" #. type: Plain text -#: user-manual.txt:3660 +#: user-manual.txt:3632 msgid "Enable the Bluetooth controller and pair your dive computer" msgstr "" #. type: Plain text -#: user-manual.txt:3661 +#: user-manual.txt:3633 msgid "Establish an RFCOMM connection" msgstr "" #. type: Title ===== -#: user-manual.txt:3662 user-manual.txt:3802 +#: user-manual.txt:3634 user-manual.txt:3774 #, no-wrap msgid "Download the dives with Subsurface" msgstr "" #. type: Plain text -#: user-manual.txt:3668 +#: user-manual.txt:3640 msgid "" "Ensure the dive computer is in upload mode. On the _Shearwater Petrel_, " "_Petrel 2_ and _Nerd_ cycle through the menu, select 'Dive Log', then " @@ -7698,7 +7789,7 @@ msgid "" msgstr "" #. type: Plain text -#: user-manual.txt:3673 +#: user-manual.txt:3645 msgid "" "To establish the connection, establish root access through +sudo+ or +su+. " "The correct permission is required to download the dives in the computer. On " @@ -7708,23 +7799,23 @@ msgid "" msgstr "" #. type: Plain text -#: user-manual.txt:3675 +#: user-manual.txt:3647 msgid "+sudo usermod -a -G dialout username+" msgstr "" #. type: Plain text -#: user-manual.txt:3677 +#: user-manual.txt:3649 msgid "Then log out and log in for the change to take effect." msgstr "" #. type: Title ===== -#: user-manual.txt:3678 +#: user-manual.txt:3650 #, no-wrap msgid "Enabling the Bluetooth controller and pairing your dive computer" msgstr "" #. type: Plain text -#: user-manual.txt:3684 +#: user-manual.txt:3656 msgid "" "Attempt to set up the Bluetooth controller and pair your dive computer using " "the graphical environment of the operating system. After setting the dive " @@ -7735,14 +7826,14 @@ msgid "" msgstr "" #. type: Plain text -#: user-manual.txt:3687 +#: user-manual.txt:3659 msgid "" -"If the graphical method didn't work, pair the device from the command line. " +"If the graphical method doesn't work, pair the device from the command line. " "Open a terminal and use +hciconfig+ to check the Bluetooth controller status" msgstr "" #. type: Plain text -#: user-manual.txt:3694 +#: user-manual.txt:3666 #, no-wrap msgid "" "\t$ hciconfig\n" @@ -7754,7 +7845,7 @@ msgid "" msgstr "" #. type: Plain text -#: user-manual.txt:3699 +#: user-manual.txt:3671 msgid "" "This indicates a Bluetooth controller with MAC address 01:23:45:67:89:AB, " "connected as hci0. Its status is 'DOWN', i.e. not powered. Additional " @@ -7764,7 +7855,7 @@ msgid "" msgstr "" #. type: Plain text -#: user-manual.txt:3707 +#: user-manual.txt:3679 #, no-wrap msgid "" "\tsudo hciconfig hci0 up auth+ (enter password when prompted)\n" @@ -7777,25 +7868,25 @@ msgid "" msgstr "" #. type: Plain text -#: user-manual.txt:3709 +#: user-manual.txt:3681 msgid "Check that the status now includes +'UP', 'RUNNING' AND 'AUTH'+." msgstr "" #. type: Plain text -#: user-manual.txt:3711 +#: user-manual.txt:3683 msgid "" "If there are multiple controllers running, it's easiest to off the unused " "controller(s). For example, for +hci1+:" msgstr "" #. type: Plain text -#: user-manual.txt:3713 +#: user-manual.txt:3685 #, no-wrap msgid "\tsudo hciconfig hci1 down\n" msgstr "" #. type: Plain text -#: user-manual.txt:3716 +#: user-manual.txt:3688 msgid "" "Next step is to 'trust' and 'pair' the dive computer. On distros with Bluez " "5, such as Fedora 22, one can use a tool called +blutootctl+, which will " @@ -7803,7 +7894,7 @@ msgid "" msgstr "" #. type: Plain text -#: user-manual.txt:3737 +#: user-manual.txt:3709 #, no-wrap msgid "" "\tbluetoothctl\n" @@ -7829,14 +7920,14 @@ msgid "" msgstr "" #. type: Plain text -#: user-manual.txt:3740 +#: user-manual.txt:3712 msgid "" "If asked for a password, enter 0000. It's ok if the last line says " "'Connected: no'. The important part is the line above, +Pairing successful+." msgstr "" #. type: Plain text -#: user-manual.txt:3743 +#: user-manual.txt:3715 msgid "" "If the system has Bluez version 4 (e.g. Ubuntu 12.04 through to 15.04), " "there is probably not a +bluetoothctl+, but a script called +bluez-simple-" @@ -7844,7 +7935,7 @@ msgid "" msgstr "" #. type: Plain text -#: user-manual.txt:3748 +#: user-manual.txt:3720 #, no-wrap msgid "" "\thcitool -i hci0 scanning\n" @@ -7854,94 +7945,94 @@ msgid "" msgstr "" #. type: Plain text -#: user-manual.txt:3750 +#: user-manual.txt:3722 msgid "Once ther dive computer is pired, set up the RFCOMM connection" msgstr "" #. type: Title ===== -#: user-manual.txt:3751 +#: user-manual.txt:3723 #, no-wrap msgid "Establishing the RFCOMM connection" msgstr "" #. type: Plain text -#: user-manual.txt:3754 +#: user-manual.txt:3726 msgid "The command to establish an RFCOMM connection is:" msgstr "" #. type: Plain text -#: user-manual.txt:3756 +#: user-manual.txt:3728 msgid "+sudo rfcomm -i <controller> connect <dev> <bdaddr> [channel]+" msgstr "" #. type: Plain text -#: user-manual.txt:3758 +#: user-manual.txt:3730 msgid "+<controller>+ is the Bluetooth controller, +hci0+." msgstr "" #. type: Plain text -#: user-manual.txt:3759 +#: user-manual.txt:3731 msgid "+<dev>+ is the RFCOMM device file, +rfcomm0+" msgstr "" #. type: Plain text -#: user-manual.txt:3760 +#: user-manual.txt:3732 msgid "+<bdaddr>+ is the dive computer's MAC address, +00:11:22:33:44:55+" msgstr "" #. type: Plain text -#: user-manual.txt:3761 +#: user-manual.txt:3733 msgid "" "+[channel]+ is the dive computer's Bluetooth channel we need to connect to." msgstr "" #. type: Plain text -#: user-manual.txt:3764 +#: user-manual.txt:3736 msgid "" "If one omits it, channel 1 is assumed. Based on a limited number of user " "reports, the appropriate channel for the dive computer is probably:" msgstr "" #. type: Plain text -#: user-manual.txt:3766 +#: user-manual.txt:3738 msgid "_Shearwater Petrel 1_: channel 1" msgstr "" #. type: Plain text -#: user-manual.txt:3767 +#: user-manual.txt:3739 msgid "_Shearwater Petrel 2_: channel 5" msgstr "" #. type: Plain text -#: user-manual.txt:3768 +#: user-manual.txt:3740 msgid "_Shearwater Nerd_: channel 5" msgstr "" #. type: Plain text -#: user-manual.txt:3769 +#: user-manual.txt:3741 msgid "_Heinrichs-Weikamp OSTC Sport_: channel 1" msgstr "" #. type: Plain text -#: user-manual.txt:3771 +#: user-manual.txt:3743 msgid "" "E.g. to connect a _Shearwater Petrel 2_, set the dive computer to upload " "mode and enter:" msgstr "" #. type: Plain text -#: user-manual.txt:3773 +#: user-manual.txt:3745 #, no-wrap msgid "\tsudo rfcomm -i hci0 connect rfcomm0 00:11:22:33:44:55 5 (enter a password, probably 0000, when prompted)\n" msgstr "" #. type: Plain text -#: user-manual.txt:3775 +#: user-manual.txt:3747 msgid "This gives the response:" msgstr "" #. type: Plain text -#: user-manual.txt:3778 +#: user-manual.txt:3750 #, no-wrap msgid "" "\tConnected /dev/rfcomm0 to 00:11:22:33:44:55 on channel 5\n" @@ -7949,14 +8040,14 @@ msgid "" msgstr "" #. type: Plain text -#: user-manual.txt:3780 +#: user-manual.txt:3752 msgid "" "To connect a _Shearwater Petrel 1+ or + HW OSTC Sport+, set the dive " "computer to upload mode and enter:" msgstr "" #. type: Plain text -#: user-manual.txt:3784 +#: user-manual.txt:3756 #, no-wrap msgid "" "\tsudo rfcomm -i hci0 connect rfcomm0 00:11:22:33:44:55 (enter a password, probably 0000, when prompted)\n" @@ -7965,7 +8056,7 @@ msgid "" msgstr "" #. type: Plain text -#: user-manual.txt:3788 +#: user-manual.txt:3760 msgid "" "If the specific channel the dive computer needs is not known, or the channel " "in the list above doesn't work, the command +sdptool records+ should help " @@ -7974,7 +8065,7 @@ msgid "" msgstr "" #. type: Plain text -#: user-manual.txt:3798 +#: user-manual.txt:3770 #, no-wrap msgid "" "\tsdptool -i hci0 records 00:11:22:33:44:55\n" @@ -7989,7 +8080,7 @@ msgid "" msgstr "" #. type: Plain text -#: user-manual.txt:3801 +#: user-manual.txt:3773 msgid "" "For a Bluetooth dive computer not in the list above, or if the channel " "listed is not correct, please let the Subsurface developers know on the user " @@ -7997,7 +8088,7 @@ msgid "" msgstr "" #. type: Plain text -#: user-manual.txt:3804 +#: user-manual.txt:3776 msgid "" "After establishing the RFCOMM connection and while the dive computer's " "upload mode countdown is still running, go to_Subsurface_, select _Import-" @@ -8007,31 +8098,31 @@ msgid "" msgstr "" #. type: Title == -#: user-manual.txt:3810 +#: user-manual.txt:3782 #, no-wrap msgid "APPENDIX B: Dive Computer specific information for importing dive data." msgstr "" #. type: Title === -#: user-manual.txt:3813 +#: user-manual.txt:3785 #, no-wrap msgid "Importing from Uemis Zurich" msgstr "" #. type: Named 'icon' AttributeList argument for style 'icon' -#: user-manual.txt:3815 +#: user-manual.txt:3787 #, no-wrap msgid "images/icons/iumis.jpg" msgstr "images/icons/iumis.jpg" #. type: Plain text -#: user-manual.txt:3831 +#: user-manual.txt:3803 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 " +"when connected to the USB port). The main difference is that you don’t " "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 " @@ -8041,36 +8132,36 @@ msgid "" msgstr "" #. type: Plain text -#: user-manual.txt:3846 +#: user-manual.txt:3818 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 " +"(this is a Uemis firmware limitation, not a _Subsurface_ issue) is that you " "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 " +"the SDA. This will usually only happen the very first time you download " "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 " +"displays an error that the dive computer ran out of space, the solution is " +"straightforward. 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 " +"download will continue where it stopped previously. You 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:3848 +#: user-manual.txt:3820 #, no-wrap msgid "Importing from Uwatec Galileo" msgstr "" #. type: Named 'icon' AttributeList argument for style 'icon' -#: user-manual.txt:3850 +#: user-manual.txt:3822 #, no-wrap msgid "images/icons/Galileo.jpg" msgstr "images/icons/Galileo.jpg" #. type: Plain text -#: user-manual.txt:3865 +#: user-manual.txt:3837 msgid "" "The Uwatec Galileo dive computers use infra red (IrDA) communication between " "the dive computer and Subsurface. The Uwatec hardware uses a USB dongle " @@ -8086,43 +8177,43 @@ msgid "" msgstr "" #. type: Plain text -#: user-manual.txt:3868 +#: user-manual.txt:3840 msgid "" -"After executing this command, Subsurface will recognise the Galileo dive " +"After executing this command, Subsurface will recognize the Galileo dive " "computer and download dive information." msgstr "" #. type: Plain text -#: user-manual.txt:3874 +#: user-manual.txt:3846 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]. Windows-based IrDA drivers " -"for the Uwatec can also be downloaded from the ScubaPro web site, drivers " -"being located on the download page for the ScubaPro SmartTrak software." +"for the Uwatec can also be downloaded from the ScubaPro web site, with " +"drivers located on the download page for the ScubaPro SmartTrak software." msgstr "" #. type: Plain text -#: user-manual.txt:3877 +#: user-manual.txt:3849 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:3879 +#: user-manual.txt:3851 #, no-wrap msgid "Importing from Heinrichs Weikamp DR5" msgstr "" #. type: Named 'icon' AttributeList argument for style 'icon' -#: user-manual.txt:3881 +#: user-manual.txt:3853 #, no-wrap msgid "images/icons/HW_DR5.jpg" msgstr "images/icons/HW_DR5.jpg" #. type: Plain text -#: user-manual.txt:3891 +#: user-manual.txt:3863 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. " @@ -8135,19 +8226,19 @@ msgid "" msgstr "" #. type: Title === -#: user-manual.txt:3894 +#: user-manual.txt:3866 #, no-wrap msgid "Importing from xDEEP BLACK" msgstr "" #. type: Named 'icon' AttributeList argument for style 'icon' -#: user-manual.txt:3896 +#: user-manual.txt:3868 #, no-wrap msgid "images/icons/HW_xdeepblack.jpg" msgstr "images/icons/HW_xdeepblack.jpg" #. type: Plain text -#: user-manual.txt:3905 +#: user-manual.txt:3877 msgid "" "Each dive has to be individually saved as UDDF file using \"Export UDDF\" " "option in BLACK's logbook menu. When mounted as a USB drive UDDF files are " @@ -8161,19 +8252,19 @@ msgid "" msgstr "" #. type: Title === -#: user-manual.txt:3907 +#: user-manual.txt:3879 #, no-wrap msgid "Importing from Shearwater Predator/Petrel/Nerd using Bluetooth" msgstr "" #. type: Named 'icon' AttributeList argument for style 'icon' -#: user-manual.txt:3909 +#: user-manual.txt:3881 #, no-wrap msgid "images/icons/predator.jpg" msgstr "images/icons/predator.jpg" #. type: Plain text -#: user-manual.txt:3912 +#: user-manual.txt:3884 msgid "" "Specific instructions for downloading dives using Bluetooth are given in the " "section above, <<S_Bluetooth,_Connecting Subsurface to a Bluetooth-enabled " @@ -8181,69 +8272,69 @@ msgid "" msgstr "" #. type: Title === -#: user-manual.txt:3914 +#: user-manual.txt:3886 #, no-wrap msgid "Importing from Poseidon MkVI Discovery" msgstr "" #. type: Named 'icon' AttributeList argument for style 'icon' -#: user-manual.txt:3916 +#: user-manual.txt:3888 #, no-wrap msgid "images/MkVI.jpeg" msgstr "images/MkVI.jpeg" #. type: Plain text -#: user-manual.txt:3924 +#: user-manual.txt:3896 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:" +"Communication between dive computer and desktop computer utilizes the IrDA " +"infra-red protocol. Only data for one dive can be downloaded at a time, in " +"three files:" msgstr "" #. type: Plain text -#: user-manual.txt:3927 +#: user-manual.txt:3899 msgid "" "Setup configuration for the dive and key dive parameters (file with a .txt " "extension)" msgstr "" #. type: Plain text -#: user-manual.txt:3928 +#: user-manual.txt:3900 msgid "Dive log details (file with a .csv extension)" msgstr "" #. type: Plain text -#: user-manual.txt:3930 +#: user-manual.txt:3902 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:3932 +#: user-manual.txt:3904 msgid "" -"_Subsurface_ accesses the .txt and the .csv files to obtain dive log " +"_Subsurface_ accesses the .txt and the .csv files to get dive log " "information." msgstr "" #. type: Title === -#: user-manual.txt:3934 +#: user-manual.txt:3906 #, no-wrap msgid "Importing from APD Inspiration/Evolution CCR" msgstr "" #. type: Named 'icon' AttributeList argument for style 'icon' -#: user-manual.txt:3936 +#: user-manual.txt:3908 #, no-wrap msgid "images/APDComputer.jpg" msgstr "images/APDComputer.jpg" #. type: Plain text -#: user-manual.txt:3944 +#: user-manual.txt:3916 msgid "" "The dive logs of an APD Inspiration or similar CCR dive computer are " "downloaded using a communications adapter and _AP Communicator_, obtained " @@ -8255,103 +8346,104 @@ msgid "" msgstr "" #. type: Plain text -#: user-manual.txt:3946 +#: user-manual.txt:3918 msgid "Download the dive using _AP Communicator_." msgstr "" #. type: Plain text -#: user-manual.txt:3947 +#: user-manual.txt:3919 msgid "Open a dive within the _AP Log Viewer_." msgstr "" #. type: Plain text -#: user-manual.txt:3948 +#: user-manual.txt:3920 msgid "Select the tab at the top of the screen, entitled \"_Data_\"." msgstr "" #. type: Plain text -#: user-manual.txt:3949 +#: user-manual.txt:3921 msgid "" "With the raw dive log data show on the screen, click on \"_Copy to Clipboard_" "\"." msgstr "" #. type: Plain text -#: user-manual.txt:3950 +#: user-manual.txt:3922 msgid "Open a text editor, e.g. Notepad (Windows) or TextWrangler (Mac)." msgstr "" #. type: Plain text -#: user-manual.txt:3952 +#: user-manual.txt:3924 msgid "" "Copy the contents of the clipboard into the text editor and save the text " "file with a filename extension of _.apd_" msgstr "" #. type: Plain text -#: user-manual.txt:3953 +#: user-manual.txt:3925 msgid "" "Within _Subsurface_, select _Import -> Import log files_ to open the xref:" "Unified_import[universal import dialogue]." msgstr "" #. type: Plain text -#: user-manual.txt:3954 +#: user-manual.txt:3926 msgid "" -"In the dropdown list towards the bottom right of the dialogue (labled " +"In the dropdown list towards the bottom right of the dialogue (labeled " "'Filter:'), select \"APD log viewer\"." msgstr "" #. type: Plain text -#: user-manual.txt:3957 +#: user-manual.txt:3930 +#, no-wrap msgid "" -"On the list of file names select the _.apd_ file that has been created " -"above. An import dialogue opens indicating the default settings for the data " -"in the _.apd_ file. If any changes are required, do this as for xref:" -"S_ImportingCSVDives[CSV imports]." +"On the list of file names select the _.apd_ file created. An import\n" +"dialogue opens showing the default settings for the data in the\n" +"_.apd_ file. If changes are required,\n" +" do this as for xref:S_ImportingCSVDives[CSV imports].\n" msgstr "" #. type: Target for macro image -#: user-manual.txt:3958 +#: user-manual.txt:3931 #, no-wrap msgid "images/APD_CSVimportF22.jpg" msgstr "images/APD_CSVimportF22.jpg" #. type: Plain text -#: user-manual.txt:3966 +#: user-manual.txt:3939 msgid "" -"The top left hand dropdown box in the import panel allows one to select the " -"APD dive computer for which the dive log needs to be imported. The default " -"it is DC1, _i.e._ the first of the two dive computers the APD uses. It is " -"possible to sequentially import the data for both dive computers by first " -"importing CD1 and then DC2.(*Hint*: The logs for the two dive computers are " -"viewed by selecting _View -> Next DC_ from the Main Menu after the uploading " -"has been completed)" +"The top left hand dropdown box in the import panel lets you select the APD " +"dive computer for which the dive log needs to be imported. The default it is " +"DC1, _i.e._ the first of the two dive computers the APD uses. It is possible " +"to sequentially import the data for both dive computers by first importing " +"CD1 and then DC2.(*Hint*: The logs for the two dive computers are viewed by " +"selecting _View -> Next DC_ from the Main Menu after the uploading has been " +"completed)" msgstr "" #. type: Plain text -#: user-manual.txt:3967 +#: user-manual.txt:3940 msgid "Click the _Ok_ button at the bottom of the import panel." msgstr "" #. type: Plain text -#: user-manual.txt:3972 +#: user-manual.txt:3945 msgid "" -"The APD dive log will appear within _Subsurface_. The dive computer-" -"generated ceiling generated by the Inspiration can be viewed by selecting " -"the appropriate button on the left of the *Dive Profile*. Cylinder pressure " -"data are not logged by the APD equipment but can be manually entered in the " +"The APD dive log will appear within _Subsurface_. The dive computer- " +"generated ceiling provided by the Inspiration can be viewed by selecting the " +"appropriate button on the left of the *Dive Profile*. Cylinder pressure data " +"are not logged by the APD equipment but can be manually entered in the " "_Equipment_ Tab." msgstr "" #. type: Title == -#: user-manual.txt:3973 +#: user-manual.txt:3946 #, no-wrap msgid "APPENDIX C: Exporting Dive log information from external dive log software." msgstr "" #. type: Plain text -#: user-manual.txt:3982 +#: user-manual.txt:3955 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, " @@ -8361,22 +8453,22 @@ msgid "" msgstr "" #. type: Plain text -#: user-manual.txt:3984 +#: user-manual.txt:3957 msgid "Export the foreign dive log data to format that is accessible from" msgstr "" #. type: Plain text -#: user-manual.txt:3985 +#: user-manual.txt:3958 msgid "_Subsurface_." msgstr "" #. type: Plain text -#: user-manual.txt:3986 +#: user-manual.txt:3959 msgid "Import the accessible dive log data into _Subsurface_." msgstr "" #. type: Plain text -#: user-manual.txt:3990 +#: user-manual.txt:3963 msgid "" "This appendix provides some information about approaches to export dive log " "data from foreign dive log software. The procedures below mostly apply to " @@ -8384,19 +8476,19 @@ msgid "" msgstr "" #. type: Title === -#: user-manual.txt:3992 +#: user-manual.txt:3965 #, no-wrap msgid "Exporting from *Suunto Divemanager (DM3, DM4 or DM5)*" msgstr "" #. type: Named 'icon' AttributeList argument for style 'icon' -#: user-manual.txt:3993 +#: user-manual.txt:3966 #, no-wrap msgid "images/icons/suuntologo.jpg" msgstr "images/icons/suuntologo.jpg" #. type: Plain text -#: user-manual.txt:4000 +#: user-manual.txt:3973 msgid "" "DiveManager is a MS Windows application for Suunto dive computers. " "Divemanager 3 (DM3) is an older version of the Suunto software. More recent " @@ -8406,66 +8498,66 @@ msgid "" msgstr "" #. type: Plain text -#: user-manual.txt:4002 +#: user-manual.txt:3975 #, no-wrap msgid "*Divemanager 3 (DM3):*\n" msgstr "" #. type: Plain text -#: user-manual.txt:4004 +#: user-manual.txt:3977 msgid "" "Start 'Suunto Divemanager 3' and log in with the name containing the logs" msgstr "" #. type: Plain text -#: user-manual.txt:4005 +#: user-manual.txt:3978 msgid "Do not start the import wizard to import dives from the dive computer." msgstr "" #. type: Plain text -#: user-manual.txt:4007 +#: user-manual.txt:3980 msgid "" "In the navigation tree on the left side of the program-window, select the " "appropriate dives." msgstr "" #. type: Plain text -#: user-manual.txt:4008 +#: user-manual.txt:3981 msgid "" "Within the list of dives, select the dives you would like to import later:" msgstr "" #. type: Plain text -#: user-manual.txt:4009 +#: user-manual.txt:3982 msgid "To select certain dives: hold 'ctrl' and click the dive" msgstr "" #. type: Plain text -#: user-manual.txt:4011 +#: user-manual.txt:3984 msgid "" "To select all dives: Select the first dive, hold down shift and select the " "last dive" msgstr "" #. type: Plain text -#: user-manual.txt:4012 +#: user-manual.txt:3985 msgid "With the dives marked, use the program menu _File -> Export_" msgstr "" #. type: Plain text -#: user-manual.txt:4013 +#: user-manual.txt:3986 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:4014 +#: user-manual.txt:3987 msgid "Click the browse button next to the field Export Path" msgstr "" #. type: Plain text -#: user-manual.txt:4016 +#: user-manual.txt:3989 #, no-wrap msgid "" "** A file-manager like window pops up\n" @@ -8473,13 +8565,13 @@ msgid "" msgstr "" #. type: Plain text -#: user-manual.txt:4017 +#: user-manual.txt:3990 #, no-wrap msgid "Divelog.SDE file\n" msgstr "" #. type: Plain text -#: user-manual.txt:4019 +#: user-manual.txt:3992 #, no-wrap msgid "" "** Optionally change the name of the file for saving\n" @@ -8487,108 +8579,108 @@ msgid "" msgstr "" #. type: Plain text -#: user-manual.txt:4020 +#: user-manual.txt:3993 #, no-wrap msgid "Back in the Export pop-up, press the button 'Export'\n" msgstr "" #. type: Plain text -#: user-manual.txt:4021 +#: user-manual.txt:3994 #, no-wrap msgid "The dives are now exported to the file Divelog.SDE.\n" msgstr "" #. type: Plain text -#: user-manual.txt:4023 +#: user-manual.txt:3996 #, no-wrap msgid "*Divemanager 4 (DM4) and Divemanager 5 (DM5):*\n" msgstr "" #. type: Plain text -#: user-manual.txt:4028 +#: user-manual.txt:4001 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." +"divelog from Divemanager you need to locate the DM4/DM5 database where the " +"dives are stored. You 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:4030 +#: user-manual.txt:4003 msgid "Locating the Suunto DM4 (or DM5) database:" msgstr "" #. type: Plain text -#: user-manual.txt:4032 user-manual.txt:4041 +#: user-manual.txt:4005 user-manual.txt:4014 msgid "Start Suunto DM4/DM5" msgstr "" #. type: Plain text -#: user-manual.txt:4033 +#: user-manual.txt:4006 msgid "Select 'Help -> About'" msgstr "" #. type: Plain text -#: user-manual.txt:4034 +#: user-manual.txt:4007 msgid "Click 'Copy' after text 'Copy log folder path to clipboard'" msgstr "" #. type: Plain text -#: user-manual.txt:4035 -msgid "Now open Windows Explorer" -msgstr "" +#: user-manual.txt:4008 +msgid "Open Windows Explorer" +msgstr "Ouvrir l'explorateur Windows" #. type: Plain text -#: user-manual.txt:4036 +#: user-manual.txt:4009 msgid "Paste the address to the path box at the top of the File Explorer" msgstr "" #. type: Plain text -#: user-manual.txt:4037 +#: user-manual.txt:4010 msgid "The database is called DM4.db or DM5.db" msgstr "" #. type: Plain text -#: user-manual.txt:4039 +#: user-manual.txt:4012 msgid "Making a backup copy of the Suunto DM4/DM5 database:" msgstr "" #. type: Plain text -#: user-manual.txt:4042 +#: user-manual.txt:4015 msgid "Select 'File - Create backup'" msgstr "" #. type: Plain text -#: user-manual.txt:4044 +#: user-manual.txt:4017 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:4045 +#: user-manual.txt:4018 msgid "Click 'Save'" msgstr "" #. type: Plain text -#: user-manual.txt:4046 +#: user-manual.txt:4019 msgid "The dives are now exported to the file DM4.bak (or DM5.bak)" msgstr "" #. type: Title === -#: user-manual.txt:4048 +#: user-manual.txt:4021 #, no-wrap msgid "Exporting from Atomic Logbook" msgstr "" #. type: Named 'icon' AttributeList argument for style 'icon' -#: user-manual.txt:4051 +#: user-manual.txt:4024 #, no-wrap msgid "images/icons/atomiclogo.jpg" msgstr "images/icons/atomiclogo.jpg" #. type: Plain text -#: user-manual.txt:4058 +#: user-manual.txt:4031 msgid "" "Atomic Logbook is a Windows software by Atomic Aquatics. It allows " "downloading of dive information from Cobalt and Cobalt 2 dive computers. " @@ -8598,130 +8690,139 @@ msgid "" msgstr "" #. type: Title === -#: user-manual.txt:4060 +#: user-manual.txt:4033 #, no-wrap msgid "Exporting from Mares Dive Organiser V2.1" msgstr "" #. type: Named 'icon' AttributeList argument for style 'icon' -#: user-manual.txt:4063 +#: user-manual.txt:4036 #, no-wrap msgid "images/icons/mareslogo.jpg" msgstr "images/icons/mareslogo.jpg" #. type: Plain text -#: user-manual.txt:4071 +#: user-manual.txt:4044 msgid "" -"Mares Dive Organiser is a Windows application. The dive log is kept as a " +"Mares Dive Organizer 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_." +"database includes all Dive Organizer-registered divers on the particular " +"computer and all Mares dive computers used. The safest way to get a copy of " +"the dive database is to export the information to another compatible format " +"which can then be imported into _Subsurface_." msgstr "" #. type: Plain text -#: user-manual.txt:4076 +#: user-manual.txt:4049 msgid "" -"Within Dive Organiser, select _Database -> Backup_ from the main menu and " +"Within Dive Organizer, select _Database -> Backup_ from the main menu and " "back up the database to the desk top. This creates a zipped file " -"DiveOrganiserxxxxx.dbf." +"DiveOrganizerxxxxx.dbf." msgstr "" #. type: Plain text -#: user-manual.txt:4079 +#: user-manual.txt:4052 msgid "" -"Rename the file to DiveOrganiserxxxxx.zip. Inside the zipped directory is a " -"file _DiveOrganiser.sdf_." +"Rename the file to DiveOrganizerxxxxx.zip. Inside the zipped directory is a " +"file _DiveOrganizer.sdf_." msgstr "" #. type: Plain text -#: user-manual.txt:4080 +#: user-manual.txt:4053 msgid "Extract the _.sdf_ file from the zipped folder to your Desktop." msgstr "" #. type: Plain text -#: user-manual.txt:4081 +#: user-manual.txt:4054 msgid "The password for accessing the .zip file is _mares_." msgstr "" #. type: Title === -#: user-manual.txt:4083 +#: user-manual.txt:4056 #, no-wrap msgid "Exporting from *DivingLog 5.0 and 6.0*" msgstr "" #. type: Named 'icon' AttributeList argument for style 'icon' -#: user-manual.txt:4085 +#: user-manual.txt:4058 #, no-wrap msgid "images/icons/divingloglogo.jpg" msgstr "images/icons/divingloglogo.jpg" #. type: Plain text -#: user-manual.txt:4092 +#: user-manual.txt:4065 msgid "" "The best way to bring your logs from DivingLog to Subsurface is to convert " "the whole database. This is because other export formats do not include all " -"the details, and we would lack e.g. gas switches and information of what " -"units are used. With database import, all this information is included and " -"readily available for us." +"the details, and would lack, for example, gas switches and information of " +"what units are used. With database import, all this information is included " +"and readily available." msgstr "" #. type: Plain text -#: user-manual.txt:4094 -msgid "To transfer all files from DivingLog to Subsurface, do the following:" +#: user-manual.txt:4067 +msgid "To transfer all files from DivingLog to Subsurface:" msgstr "" #. type: Plain text -#: user-manual.txt:4096 +#: user-manual.txt:4069 msgid "In DivingLog open the 'File -> Export -> SQLite' menu" msgstr "" #. type: Plain text -#: user-manual.txt:4097 +#: user-manual.txt:4070 msgid "Select 'Settings' button" msgstr "" #. type: Plain text -#: user-manual.txt:4098 +#: user-manual.txt:4071 msgid "Set the 'RTF2Plaintext' to 'true'" msgstr "" #. type: Plain text -#: user-manual.txt:4099 +#: user-manual.txt:4072 msgid "Close the Settings dialog" msgstr "" #. type: Plain text -#: user-manual.txt:4100 +#: user-manual.txt:4073 msgid "Click 'Export' button and select the filename" msgstr "" #. type: Plain text -#: user-manual.txt:4104 +#: user-manual.txt:4077 msgid "" "Once this is done, open the saved database file with Subsurface and the " -"dives are automatically converted to our own format. Last step to do is save " -"the log file in Subsurface." +"dives are automatically converted to Subsurface’s own format. Last step to " +"do is save the log file in Subsurface." msgstr "" #. type: Title == -#: user-manual.txt:4105 +#: user-manual.txt:4078 #, no-wrap msgid "APPENDIX D: Exporting a spreadsheet to CSV format" msgstr "ANNEXE D : Exporter un tableur vers le format CSV" #. type: Plain text -#: user-manual.txt:4115 +#: user-manual.txt:4088 +#, fuzzy +#| 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_ 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." msgid "" -"Many divers keep a diving log in some form of a digital file, commonly a " +"Many divers keep a dive log in some form of digital file, commonly a " "spreadsheet with various fields of information. These logs can be easily " "imported into _Subsurface_ 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." +"stored in a spreadsheet to a .CSV file that will later be imported to " +"_Subsurface_. Creating a .CSV is straightforward, although the procedure is " +"somewhat different according to which spreadsheet program is used." msgstr "" "De nombreux plongeurs conservent un carnet de plongée sous forme de fichier " "numérique, souvent un tableur avec différents champs et informations. Ces " @@ -8733,14 +8834,21 @@ msgstr "" "selon le tableur utilisé." #. type: Plain text -#: user-manual.txt:4121 -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:" +#: user-manual.txt:4094 +#, fuzzy +#| 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:" +msgid "" +"Organize the diving data in the spreadsheet, so 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 number, Date, " +"Time, Duration, Location, GPS, Max Depth, Mean Depth, Buddy, Notes, Weight " +"and Tags). Organize dive data following a few simple rules:" msgstr "" "La première étape est d'organiser les données de plongées dans le tableur " "pour que la première ligne contienne le nom (ou le titre) de chaque colonne " @@ -8751,47 +8859,46 @@ msgstr "" "règles simples :" #. type: Plain text -#: user-manual.txt:4123 +#: user-manual.txt:4096 msgid "" "Date: use one of the following formats: yyyy-mm-dd, dd.mm.yyyy, mm/dd/yyyy" msgstr "" "Date : utiliser un des formats suivants : aaaa-mm-jj, jj.mm.aaaa, mm/jj/aaaa" #. type: Plain text -#: user-manual.txt:4124 +#: user-manual.txt:4097 msgid "Duration: the format should be minutes:seconds." msgstr "Durée : le format est minutes:secondes." #. type: Plain text -#: user-manual.txt:4125 +#: user-manual.txt:4098 msgid "" -"Unit system: only one unit system should be used (i.e., no mixture between " -"imperial and metric units)" +"Unit system: only one unit system should be used (no mix of imperial and " +"metric units)" msgstr "" "Système d'unité : un seul système d'unité doit être utilisé (pas de mélange " "entre les unités impériales et métriques)" #. type: Plain text -#: user-manual.txt:4126 +#: user-manual.txt:4099 msgid "Tags and buddies: values should be separated using a comma." msgstr "" "Étiquettes et équipiers : les valeurs doivent être séparées par des virgules." #. type: Plain text -#: user-manual.txt:4127 -msgid "GPS position: users must use decimal degrees, e.g. 30.22496 30.821798" +#: user-manual.txt:4100 +msgid "GPS position: use decimal degrees, e.g. 30.22496 30.821798" msgstr "" -"Position GPS : vous devez utiliser les degrés décimaux, par exemple : " -"30.22496 30.821798" +"Position GPS : utilisez les degrés décimaux, par exemple : 30.22496 30.821798" #. type: Title === -#: user-manual.txt:4128 +#: user-manual.txt:4100 #, no-wrap msgid "_LibreOffice Calc_ and _OpenOffice Calc_" msgstr "_LibreOffice Calc_ et _OpenOffice Calc_" #. type: Plain text -#: user-manual.txt:4132 +#: user-manual.txt:4104 msgid "" "These are open source spreadsheet applications forming parts of larger open " "source office suite applications. The user interaction with _LibreOffice_ " @@ -8802,13 +8909,13 @@ msgid "" msgstr "" #. type: Target for macro image -#: user-manual.txt:4133 +#: user-manual.txt:4105 #, no-wrap msgid "images/LOffice_spreadsheetdata.jpg" msgstr "images/LOffice_spreadsheetdata.jpg" #. type: Plain text -#: user-manual.txt:4136 +#: user-manual.txt:4108 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 " @@ -8816,13 +8923,13 @@ msgid "" msgstr "" #. type: Target for macro image -#: user-manual.txt:4137 +#: user-manual.txt:4109 #, no-wrap msgid "images/LOffice_save_as_options.jpg" msgstr "images/LOffice_save_as_options.jpg" #. type: Plain text -#: user-manual.txt:4140 +#: user-manual.txt:4112 msgid "" "After selecting _Save_, select the appropriate field delimiter (choose _Tab_ " "to prevent conflicts with the comma when using this as a decimal point), " @@ -8830,50 +8937,50 @@ msgid "" msgstr "" #. type: Target for macro image -#: user-manual.txt:4141 +#: user-manual.txt:4113 #, no-wrap msgid "images/LOffice_field_options.jpg" msgstr "images/LOffice_field_options.jpg" #. type: Plain text -#: user-manual.txt:4144 +#: user-manual.txt:4116 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_ImportingCSVDives[Importing CSV dives]." +"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_ImportingCSVDives[Importing " +"CSV dives]." msgstr "" #. type: Title === -#: user-manual.txt:4145 +#: user-manual.txt:4117 #, no-wrap msgid "Microsoft _Excel_" msgstr "Microsoft _Excel_" #. type: Plain text -#: user-manual.txt:4151 +#: user-manual.txt:4123 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 " +"software on the Windows machine uses the new character as a separator. You " "can change the character back to the default character by following the same " "procedure, outlined below." msgstr "" #. type: Plain text -#: user-manual.txt:4153 +#: user-manual.txt:4125 msgid "" -"In Microsoft Windows, click the *Start* button, and then select _Control " -"Panel_ from the list on the right-hand side." +"In Microsoft Windows, click the *Start* button, then select _Control Panel_ " +"from the list on the right-hand side." msgstr "" #. type: Plain text -#: user-manual.txt:4154 +#: user-manual.txt:4126 msgid "Open the _Regional and Language Options_ dialog box." msgstr "" #. type: Plain text -#: user-manual.txt:4157 +#: user-manual.txt:4129 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 " @@ -8881,190 +8988,190 @@ msgid "" msgstr "" #. type: Plain text -#: user-manual.txt:4158 +#: user-manual.txt:4130 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:4159 +#: user-manual.txt:4131 msgid "Click _OK_ twice." msgstr "" #. type: Plain text -#: user-manual.txt:4161 +#: user-manual.txt:4133 msgid "Below is an image of the _Control Panel_:" msgstr "" #. type: Target for macro image -#: user-manual.txt:4162 +#: user-manual.txt:4134 #, no-wrap msgid "images/Win_SaveCSV2.jpg" msgstr "images/Win_SaveCSV2.jpg" #. type: Plain text -#: user-manual.txt:4165 +#: user-manual.txt:4137 msgid "To export the dive log in CSV format:" msgstr "" #. type: Plain text -#: user-manual.txt:4167 +#: user-manual.txt:4139 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:4168 +#: user-manual.txt:4140 #, no-wrap msgid "images/Win_SaveCSV1.jpg" msgstr "images/Win_SaveCSV1.jpg" #. type: Plain text -#: user-manual.txt:4171 +#: user-manual.txt:4146 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." +"marked _Save as Type:_, select _CSV(Comma delimited) (*.CSV)_. Be sure the " +"appropriate folder has been selected to save the CSV file into." msgstr "" #. type: Target for macro image -#: user-manual.txt:4172 +#: user-manual.txt:4147 #, no-wrap msgid "images/Win_SaveCSV3.jpg" msgstr "images/Win_SaveCSV3.jpg" #. type: Plain text -#: user-manual.txt:4175 +#: user-manual.txt:4153 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:" +"that was selected. You can double check the .CSV file by opening it with a " +"text editor, then import the dive data as explained on the section xref:" "S_ImportingCSVDives[Importing CSV dives]." msgstr "" #. type: Title == -#: user-manual.txt:4177 +#: user-manual.txt:4154 #, no-wrap msgid "APPENDIX E: Writing a custom print template" msgstr "ANNEXE E : Créer un modèle d'impression personnalisé" #. type: Plain text -#: user-manual.txt:4182 +#: user-manual.txt:4159 msgid "" -"_Subsurface_ provides a mechanism to create or modify templates for printing " -"dive logs in order to produce customised printouts of dive logs. Templates, " -"written in HTML as well as a simple Grantlee instruction set, are rendered " -"to the print device by _Subsurface_." +"_Subsurface_ has a way to create or modify templates for printing dive logs " +"to produce customized printouts of them. Templates written in HTML, as well " +"as a simple Grantlee instruction set, are rendered to the print device by " +"_Subsurface_." msgstr "" #. type: Plain text -#: user-manual.txt:4184 +#: user-manual.txt:4161 msgid "Templates are accessed using the print dialogue (see image *B* below)." msgstr "" #. type: Plain text -#: user-manual.txt:4192 +#: user-manual.txt:4169 msgid "" -"The buttons under the _Template_ dropdown box allows one to _Edit_, " -"_Delete_, _Import_ and to _Export_ templates (see image *A* above). New or " -"modified templates are stored as HTML files in the same directory as the " -"dive log being processed. In order to create or modify a template, select " -"one of the templates from the template dropdown list in the print dialogue " -"(see image *B* above). Choose an existing template that resembles the final " -"desired printout. Then select _Edit_." +"The buttons under the _Template_ dropdown box lets you _Edit_, _Delete_, " +"_Import_ and _Export_ templates (see image *A* above). New or modified " +"templates are stored as HTML files in the same directory as the dive log " +"being processed. In order to create or modify a template, select one of the " +"templates from the template dropdown list in the print dialogue (see image " +"*B* above). Choose an existing template that resembles the final desired " +"printout. Then select _Edit_." msgstr "" #. type: Plain text -#: user-manual.txt:4194 -msgid "The Edit Panel comprises three tabs:" +#: user-manual.txt:4171 +msgid "The Edit Panel has three tabs:" msgstr "" #. type: Target for macro image -#: user-manual.txt:4195 +#: user-manual.txt:4172 #, no-wrap msgid "images/Template1_f22.jpg" msgstr "images/Template1_f22.jpg" #. type: Plain text -#: user-manual.txt:4199 +#: user-manual.txt:4176 msgid "" -"The _Style_ tab (image *A* above) controls the font, line spacing and colour " +"The _Style_ tab (image *A* above) controls the font, line spacing and color " "template used for printing the dive log. The style attributes are editable. " -"Choose one of the four colour palets used for colour printing." +"Choose one of the four color palettes used for color printing." msgstr "" #. type: Plain text -#: user-manual.txt:4203 +#: user-manual.txt:4180 msgid "" -"The _Colors_ tab (image *B* above) allows editing the colours used for " -"printing the dive log. The colours are highly customisable: the _Edit_ " -"buttons in the _Colors_ tab allows choosing abritrary colours for different " +"The _Colors_ tab (image *B* above) allows editing the colors used for " +"printing the dive log. The colors are highly customizable: the _Edit_ " +"buttons in the _Colors_ tab allows choosing arbitrary colors for different " "components of the dive log printout." msgstr "" #. type: Plain text -#: user-manual.txt:4212 +#: user-manual.txt:4189 msgid "" "The _Template_ tab of the Edit Panel (see image below) allows creating a " "template using HTML as well as a few Grantlee programming primitives. " -"Grantlee provides the ability to create and format HTML code in a highly " -"simple but efficient way (see below). The HTML of the template can be edited " -"and saved. The saved template is stored in the same directory as the dive " -"being processed. By default, a _Custom_ template is a skeleton with no " -"specific print instructions. The informastion being printed needs to be " -"specified and formatted in the by replacing the section marked with: \"<!-- " -"Template must be filled -->\". Writing HTML code with Grantlee instructions " -"allows unlimited freedom in determining what is printed an in which way it " -"should be rendered." +"Grantlee can create and format HTML code in a highly simple but efficient " +"way (see below). The HTML of the template can be edited and saved. The saved " +"template is stored in the same directory as the dive being processed. By " +"default, a _Custom_ template is a skeleton with no specific print " +"instructions. The information printed needs to be specified and formatted in " +"the template by replacing the section marked with: \"<!-- Template must be " +"filled -->\". Writing HTML code with Grantlee instructions allows unlimited " +"freedom in determining what is printed and in which way it should be " +"rendered." msgstr "" #. type: Target for macro image -#: user-manual.txt:4213 +#: user-manual.txt:4190 #, no-wrap msgid "images/Template2_f22.jpg" msgstr "images/Template2_f22.jpg" #. type: Plain text -#: user-manual.txt:4217 +#: user-manual.txt:4195 msgid "" -"One can adapt any of the existing templates and save it to the dive log " +"You can adapt any of the existing templates and save it to the dive log " "directory. The standard templates (e.g. One dive, Six dives, Table) can be " "modified in this way. After completing the edits, use the _Export_ button in " "the print dialogue to save the new template using a new template name." msgstr "" #. type: Plain text -#: user-manual.txt:4219 +#: user-manual.txt:4197 msgid "" -"To write a custom template the following elements must exist so that the " +"To write a custom template, the following elements must exist so the " "template will be correctly handled and rendered." msgstr "" #. type: Title === -#: user-manual.txt:4220 +#: user-manual.txt:4198 #, no-wrap msgid "Main dive loop" msgstr "" #. type: Plain text -#: user-manual.txt:4222 +#: user-manual.txt:4200 msgid "" -"_Subsurface_ exports a dive list called (*dives*) to the _Grantlee_ backend. " -"It is possible to iterate over the list as follows:" +"_Subsurface_ exports a dive list called (*dives*) to the _Grantlee_ back " +"end. It is possible to iterate over the list as follows:" msgstr "" #. type: Block title -#: user-manual.txt:4223 user-manual.txt:4277 user-manual.txt:4294 +#: user-manual.txt:4200 user-manual.txt:4265 user-manual.txt:4282 #, no-wrap msgid "template.html" msgstr "" #. type: delimited block . -#: user-manual.txt:4228 +#: user-manual.txt:4205 #, no-wrap msgid "" "\t{% for dive in dives %}\n" @@ -9073,13 +9180,13 @@ msgid "" msgstr "" #. type: Block title -#: user-manual.txt:4230 user-manual.txt:4282 user-manual.txt:4301 +#: user-manual.txt:4207 user-manual.txt:4270 user-manual.txt:4289 #, no-wrap msgid "output.html" msgstr "" #. type: delimited block . -#: user-manual.txt:4235 +#: user-manual.txt:4212 #, no-wrap msgid "" "\t<h1> 1 </h1>\n" @@ -9088,48 +9195,59 @@ msgid "" msgstr "" #. type: Plain text -#: user-manual.txt:4238 +#: user-manual.txt:4215 msgid "" -"Additional information about _Grantlee_ can be found http://www.grantlee.org/" -"apidox/for_themers.html[here]" +"Additional information about _Grantlee_ can be found at http://www.grantlee." +"org/apidox/for_themers.html[here]" msgstr "" #. type: Title === -#: user-manual.txt:4239 +#: user-manual.txt:4216 #, no-wrap msgid "Grantlee exported variables" msgstr "" #. type: Plain text -#: user-manual.txt:4241 +#: user-manual.txt:4218 msgid "Only a subset of the dive data is exported:" msgstr "" #. type: delimited block | -#: user-manual.txt:4259 +#: user-manual.txt:4247 #, no-wrap msgid "" "|*Name*|*Description*\n" "|number| (*int*) dive number\n" "|id| (*int*) unique dive ID, should be used to fetch the dive profile\n" -"|date| (*string*) data of the dive\n" +"|date| (*string*) date of the dive\n" "|time| (*string*) time of the dive\n" "|location| (*string*) location of the dive\n" "|duration| (*string*) duration of the dive\n" "|depth| (*string*) depth of the dive\n" -"|divemaster| (*string*) divemaster data\n" -"|buddy| (*string*) buddy data\n" -"|airTemp| (*string*) air temperature of dive\n" -"|waterTemp| (*string*) water temperature of dive\n" +"|divemaster| (*string*) dive master for the dive\n" +"|buddy| (*string*) buddy for the dive\n" +"|airTemp| (*string*) air temperature of the dive\n" +"|waterTemp| (*string*) water temperature of the dive\n" "|notes| (*string*) dive notes\n" -"|rating| (*int*) dive rating ranges from 0 to 5\n" -"|sac| (*string*) sac value\n" -"|tags| (*string*) all dive tags concatenate together\n" -"|gas| (*string*) used gas cylinder\n" -msgstr "" - -#. type: Plain text -#: user-manual.txt:4263 +"|rating| (*int*) dive rating which ranges from 0 to 5\n" +"|sac| (*string*) SAC value for the dive\n" +"|tags| (*string*) list of dive tags for the dive\n" +"|gas| (*string*) list of gases used in the dive\n" +"|suit| (*string*) the suit used for the dive\n" +"|cylinders| (*string*) complete information of all used cylinders\n" +"|cylinder0-7| (*string*) information about a specific cylinder\n" +"|weights| (*string*) complete information of all used weight systems\n" +"|weight0-5| (*string*) information about a specific weight system\n" +"|maxcns| (*string*) maxCNS value for the dive\n" +"|otu| (*string*) OTU value for the dive\n" +"|sumWeight| (*string*) the summed weight of all used weight systems\n" +"|startPressure| (*string*) the start pressure\n" +"|endPressure| (*string*) the end pressure\n" +"|firstGas| (*string*) first used gas\n" +msgstr "" + +#. type: Plain text +#: user-manual.txt:4251 msgid "" "_Subsurface_ also exports *template_options* data. This data must be used as " "_CSS_ values to provide a dynamically editable template. The exported data " @@ -9137,7 +9255,7 @@ msgid "" msgstr "" #. type: delimited block | -#: user-manual.txt:4275 +#: user-manual.txt:4263 #, no-wrap msgid "" "|*Name*|*Description*\n" @@ -9154,26 +9272,26 @@ msgid "" msgstr "" #. type: delimited block . -#: user-manual.txt:4280 +#: user-manual.txt:4268 #, no-wrap msgid "\tborder-width: {{ template_options.borderwidth }}px;\n" msgstr "" #. type: delimited block . -#: user-manual.txt:4285 +#: user-manual.txt:4273 #, no-wrap msgid "\tborder-width: 3px;\n" msgstr "" #. type: Plain text -#: user-manual.txt:4288 +#: user-manual.txt:4276 msgid "" "Another variable that _Subsurface_ exports is *print_options*. This variable " "contains a single member:" msgstr "" #. type: delimited block | -#: user-manual.txt:4291 +#: user-manual.txt:4279 #, no-wrap msgid "" "|*Name*|*Description*\n" @@ -9181,7 +9299,7 @@ msgid "" msgstr "" #. type: delimited block . -#: user-manual.txt:4299 +#: user-manual.txt:4287 #, no-wrap msgid "" "\tbody {\n" @@ -9190,7 +9308,7 @@ msgid "" msgstr "" #. type: delimited block . -#: user-manual.txt:4306 +#: user-manual.txt:4294 #, no-wrap msgid "" "\tbody {\n" @@ -9199,101 +9317,101 @@ msgid "" msgstr "" #. type: Title === -#: user-manual.txt:4308 +#: user-manual.txt:4296 #, no-wrap msgid "Defined CSS selectors" msgstr "" #. type: Plain text -#: user-manual.txt:4312 +#: user-manual.txt:4299 msgid "" -"As the dive profile is placed after rendering, _Subsurface_ uses a special " -"_CSS_ selectors to do some searches in the HTML output. The _CSS_ selectors " -"in the following table should be added." +"As the dive profile is placed after rendering, _Subsurface_ uses special " +"_CSS_ selectors to searche in the HTML output. The _CSS_ selectors in the " +"following table should be added." msgstr "" #. type: delimited block | -#: user-manual.txt:4319 +#: user-manual.txt:4306 #, no-wrap msgid "" "|*Selector*|*Type*|*Description*\n" "|dive_{{ dive.id }} | id | is used to fetch the relevant dive profile\n" -"|diveProfile | class | each div that will contain a dive profile should have this class selector in addition to the dive_{{ dive.id }} id selector\n" -"|dontbreak | class | prevents the div with this class to be divided into two pages, this can be used\n" +"|diveProfile | class | each dive that will contain a dive profile should have this class selector in addition to the dive_{{ dive.id }} id selector\n" +"|dontbreak | class | prevents the dive with this class from being divided into two pages. This can be used\n" "in flow layout templates only (when data-numberofdives = 0)\n" msgstr "" #. type: Plain text -#: user-manual.txt:4322 +#: user-manual.txt:4309 msgid "" "Rendering dive profiles is not supported for flow layout templates (when " "data-numberofdives = 0)." msgstr "" #. type: Title === -#: user-manual.txt:4323 +#: user-manual.txt:4310 #, no-wrap msgid "Special attributes" msgstr "" #. type: Plain text -#: user-manual.txt:4327 +#: user-manual.txt:4314 msgid "" "There are two ways of rendering- either rendering a specific number of dives " -"in each page or make _Subsurface_ try to fit as much dives as possible into " +"in each page or make _Subsurface_ try to fit as many dives as possible into " "one page (_flow_ rendering)." msgstr "" #. type: Plain text -#: user-manual.txt:4329 +#: user-manual.txt:4316 msgid "" "The *data-numberofdives* data attribute is added to the body tag to set the " -"rendering mode" +"rendering mode." msgstr "" #. type: Plain text -#: user-manual.txt:4331 +#: user-manual.txt:4318 msgid "render 6 dives per page:" msgstr "" #. type: delimited block . -#: user-manual.txt:4334 +#: user-manual.txt:4321 #, no-wrap msgid "\t<body data-numberofdives = 6>\n" msgstr "" #. type: Plain text -#: user-manual.txt:4337 +#: user-manual.txt:4324 msgid "render as much dives as possible:" msgstr "" #. type: delimited block . -#: user-manual.txt:4340 +#: user-manual.txt:4327 #, no-wrap msgid "\t<body data-numberofdives = 0>\n" msgstr "" #. type: Plain text -#: user-manual.txt:4343 +#: user-manual.txt:4330 msgid "" "All CSS units should be in relative lengths only, to support printing on any " "page size." msgstr "" #. type: Title == -#: user-manual.txt:4344 +#: user-manual.txt:4331 #, no-wrap msgid "APPENDIX F: FAQs." msgstr "" #. type: Title === -#: user-manual.txt:4346 +#: user-manual.txt:4333 #, no-wrap msgid "Subsurface appears to miscalculate gas consumption and SAC" msgstr "" #. type: Plain text -#: user-manual.txt:4350 +#: user-manual.txt:4337 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_ " @@ -9301,17 +9419,17 @@ msgid "" msgstr "" #. type: Plain text -#: user-manual.txt:4356 +#: user-manual.txt:4343 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 " +"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:4362 +#: user-manual.txt:4349 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 " @@ -9321,12 +9439,12 @@ msgid "" msgstr "" #. type: Plain text -#: user-manual.txt:4364 +#: user-manual.txt:4351 msgid "+consumption = (amount_of_air_at_beginning - amount_of_air_at_end)+" msgstr "" #. type: Plain text -#: user-manual.txt:4370 +#: user-manual.txt:4357 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 " @@ -9337,12 +9455,12 @@ msgid "" msgstr "" #. type: Plain text -#: user-manual.txt:4372 +#: user-manual.txt:4359 msgid "+12.2*((220-100)/1.013)+" msgstr "" #. type: Plain text -#: user-manual.txt:4377 +#: user-manual.txt:4364 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 " @@ -9352,7 +9470,7 @@ msgid "" msgstr "" #. type: Plain text -#: user-manual.txt:4383 +#: user-manual.txt:4370 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 " @@ -9363,13 +9481,13 @@ msgid "" msgstr "" #. type: Title === -#: user-manual.txt:4384 +#: user-manual.txt:4371 #, no-wrap msgid "Some dive profiles have time discrepancies with the recorded samples from my dive computer..." msgstr "" #. type: Plain text -#: user-manual.txt:4388 +#: user-manual.txt:4375 msgid "" "_Subsurface_ ends up ignoring surface time for many things (average depth, " "divetime, SAC, etc). 'Question': Why do dive durations in my dive computer " @@ -9377,7 +9495,7 @@ msgid "" msgstr "" #. type: Plain text -#: user-manual.txt:4396 +#: user-manual.txt:4383 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 " @@ -9391,42 +9509,54 @@ msgid "" msgstr "" #. type: Title === -#: user-manual.txt:4397 +#: user-manual.txt:4384 #, no-wrap msgid "Some dive profiles are missing from the download" msgstr "" #. type: Plain text -#: user-manual.txt:4403 +#: user-manual.txt:4398 msgid "" -"'Question': I cannot download all my dives, only the most recent ones even " +"'Question': I cannot download all my dives, only the most recent ones, even " "though my dive computer's manual states that it records history of e.g. 999 " -"dives." -msgstr "" - -#. type: Plain text -#: user-manual.txt:4412 -msgid "" -"'Answer': Dive history is different than the dive profiles on the log. The " -"history only keeps track of the total number of dives and total amount of " -"time spent below surface. The logs, on the other hand, store the dive " -"profile, but they have limited amount of memory to do so. The exact amount " -"of dive profiles that can be stored on the device depend on sample interval " -"and duration of the dives. Once the memory is full the oldest dives get " -"overwritten with new dives. Thus we are only able to download the last 13, " -"30 or 199 dives." +"dives? 'Answer': Dive history is different than the dive profiles on the " +"log. The history only keeps track of the total number of dives and total " +"amount of time spent below surface. The logs, on the other hand, store the " +"dive profile, but they have a limited amount of memory to do so. The exact " +"amount of dive profiles that can be stored on the device depends on sample " +"interval and duration of the dives. Once the memory is full the oldest dives " +"get overwritten with new dives. Thus we are only able to download the last " +"13, 30 or 199 dives." msgstr "" #. type: Plain text -#: user-manual.txt:4416 +#: user-manual.txt:4402 msgid "" "If you have downloaded your dives to different dive logging software before " -"they were overwritten, there is a high chance that Subsurface can import " +"they were overwritten, there is a good chance that Subsurface can import " "these. However, if the logs are only on your dive computer, they cannot be " -"salvaged after being over written by new dives." +"salvaged after being overwritten by new dives." msgstr "" #~ msgid "" +#~ "Do you need a way of storing or backing up your dive log on the Internet, " +#~ "allowing you to view your dive log from anywhere, using an Internet " +#~ "browser?" +#~ msgstr "" +#~ "Avez-vous besoin d'un moyen d'enregistrer ou de sauvegarder votre carnet " +#~ "de plongée sur Internet, Vous permettant de visualiser votre carnet " +#~ "depuis n'importe où, en utilisant un navigateur Internet ?" + +#~ msgid "" +#~ "If one has dives recorded using a dive computer, the depth profile of the" +#~ msgstr "" +#~ "Si les plongées ont été enregistrées en utilisant un ordinateur de " +#~ "plongée, le profil de profondeur de la" + +#~ msgid "previous dive computer." +#~ msgstr "ordinateur de plongée précédent." + +#~ msgid "" #~ "When opened from within _Subsurface_, this manual does not have external " #~ "controls. However, a _SEARCH_ function is important. This is activated by " #~ "pressing control-F or command-F on the keyboard. A text box appears at " diff --git a/Documentation/make_POT.sh b/Documentation/make_POT.sh index afe9cf895..bbf465790 100755 --- a/Documentation/make_POT.sh +++ b/Documentation/make_POT.sh @@ -3,20 +3,23 @@ # Author(s): Guillaume GARDET <guillaume.gardet@free.fr> # # History: +# - 2016-03-12: Generate 2 POT files: one for mobile-manual and another for user-manual # - 2015-01-14: Initial release # # Package deps: - po4a (for po4a-gettextize) # - perl-Unicode-LineBreak # Some vars -File_to_translate="./user-manual.txt" +Files_to_translate="mobile-manual.txt user-manual.txt" POT_files_folder="./50-pot" -POT_name="subsurface-manual.pot" -#Generate a POT file from user-manual.txt file in current folder -cmd="po4a-gettextize --msgid-bugs-address subsurface@subsurface-divelog.org \ - --package-name subsurface-manual -o porefs=full,nowrap \ - -f asciidoc -M UTF-8 -m $File_to_translate -p $POT_files_folder/$POT_name" -echo "Generating POT file:" -echo $cmd -$cmd +for File_to_translate in $Files_to_translate; do + POT_name=subsurface-$(basename $File_to_translate ".txt").pot + #Generate a POT file *.txt file in current folder + cmd="po4a-gettextize --msgid-bugs-address subsurface@subsurface-divelog.org \ + --package-name subsurface-manual -o porefs=full,nowrap \ + -f asciidoc -M UTF-8 -m $File_to_translate -p $POT_files_folder/$POT_name" + echo "Generating POT file:" + echo $cmd + $cmd +done
\ No newline at end of file diff --git a/Documentation/make_PO_to_ASCIIDOC.sh b/Documentation/make_PO_to_ASCIIDOC.sh index 95fbf40ab..c619e0a4c 100755 --- a/Documentation/make_PO_to_ASCIIDOC.sh +++ b/Documentation/make_PO_to_ASCIIDOC.sh @@ -3,6 +3,7 @@ # Author(s): Guillaume GARDET <guillaume.gardet@free.fr> # # History: +# - 2016-03-12: Generate 2 PO files: one for mobile-manual and another for user-manual # - 2015-01-14: Initial release # # Known bugs: @@ -13,7 +14,7 @@ # - gettext-tools (for msginit and msgmerge) # Some vars -File_to_translate="./user-manual.txt" +Files_to_translate="mobile-manual.txt user-manual.txt" POT_files_folder="./50-pot/" langs="fr" # Language list which uses POT/PO files for translation PO_filename_root="subsurface-manual" @@ -35,23 +36,24 @@ for lang in $langs; do git pull for file in $(ls $POT_files_folder/*.pot); do - filename=$(basename ${file%.pot}).$lang.po + filename=$(basename $file ".pot").$lang.po if [ ! -f $PO_folder/$filename ]; then echo "** Initializing PO file for $lang" mkdir -p $PO_folder msginit -l $lang --input=$file --output-file=$PO_folder/$filename fi; echo "** Updating PO file for '$lang' from POT file" - msgmerge --previous --lang=$lang --update $PO_folder/$filename $POT_files_folder/*.pot + msgmerge --previous --lang=$lang --update $PO_folder/$filename $file done fi # Generate translated ASCIIDOC files echo "* Generating ASCIIDOC files for '$lang'" - for file in $File_to_translate; do - Translated_file=$(basename ${File_to_translate%.txt})_$lang.txt - cmd="po4a-translate --keep $translation_limit -f asciidoc -M UTF-8 -m $File_to_translate -p $PO_folder/$PO_filename_root.$lang.po -l $Translated_file" + for file in $Files_to_translate; do + Translated_file=$(basename $file ".txt")_$lang.txt + PO_name=subsurface-$(basename $file ".txt").$lang.po + cmd="po4a-translate --keep $translation_limit -f asciidoc -M UTF-8 -m $file -p $PO_folder/$PO_name -l $Translated_file" echo $cmd $cmd done diff --git a/Documentation/mobile-images/Edit.jpg b/Documentation/mobile-images/Edit.jpg Binary files differdeleted file mode 100644 index 16873c13c..000000000 --- a/Documentation/mobile-images/Edit.jpg +++ /dev/null diff --git a/Documentation/mobile-images/Left.jpg b/Documentation/mobile-images/Left.jpg Binary files differdeleted file mode 100644 index 803737806..000000000 --- a/Documentation/mobile-images/Left.jpg +++ /dev/null diff --git a/Documentation/mobile-images/LeftRight.jpg b/Documentation/mobile-images/LeftRight.jpg Binary files differdeleted file mode 100644 index a1409f908..000000000 --- a/Documentation/mobile-images/LeftRight.jpg +++ /dev/null diff --git a/Documentation/mobile-images/Quit.jpg b/Documentation/mobile-images/Quit.jpg Binary files differdeleted file mode 100644 index 4a450865d..000000000 --- a/Documentation/mobile-images/Quit.jpg +++ /dev/null diff --git a/Documentation/mobile-images/actionbutton.jpg b/Documentation/mobile-images/actionbutton.jpg Binary files differnew file mode 100644 index 000000000..7cdef795d --- /dev/null +++ b/Documentation/mobile-images/actionbutton.jpg diff --git a/Documentation/mobile-images/createdive.jpg b/Documentation/mobile-images/createdive.jpg Binary files differnew file mode 100644 index 000000000..6da7c14d9 --- /dev/null +++ b/Documentation/mobile-images/createdive.jpg diff --git a/Documentation/mobile-images/divelist.jpg b/Documentation/mobile-images/divelist.jpg Binary files differindex b8db72dd8..165a9e941 100644 --- a/Documentation/mobile-images/divelist.jpg +++ b/Documentation/mobile-images/divelist.jpg diff --git a/Documentation/mobile-images/editdive.jpg b/Documentation/mobile-images/editdive.jpg Binary files differindex 36daac3d7..43bd21083 100644 --- a/Documentation/mobile-images/editdive.jpg +++ b/Documentation/mobile-images/editdive.jpg diff --git a/Documentation/mobile-images/gpsmanagement.jpg b/Documentation/mobile-images/gpsmanagement.jpg Binary files differindex c441b4e7c..6a160e254 100644 --- a/Documentation/mobile-images/gpsmanagement.jpg +++ b/Documentation/mobile-images/gpsmanagement.jpg diff --git a/Documentation/mobile-images/gpssetup.jpg b/Documentation/mobile-images/gpssetup.jpg Binary files differindex ca30bf7d2..6021ce0e3 100644 --- a/Documentation/mobile-images/gpssetup.jpg +++ b/Documentation/mobile-images/gpssetup.jpg diff --git a/Documentation/mobile-images/landingscreen.jpg b/Documentation/mobile-images/landingscreen.jpg Binary files differindex 1141b0f2b..143eb69ec 100644 --- a/Documentation/mobile-images/landingscreen.jpg +++ b/Documentation/mobile-images/landingscreen.jpg diff --git a/Documentation/mobile-images/managedive.jpg b/Documentation/mobile-images/managedive.jpg Binary files differdeleted file mode 100644 index 4383a0305..000000000 --- a/Documentation/mobile-images/managedive.jpg +++ /dev/null diff --git a/Documentation/mobile-images/map.jpg b/Documentation/mobile-images/map.jpg Binary files differdeleted file mode 100644 index c1712cbda..000000000 --- a/Documentation/mobile-images/map.jpg +++ /dev/null diff --git a/Documentation/mobile-images/menu.jpg b/Documentation/mobile-images/menu.jpg Binary files differnew file mode 100644 index 000000000..db906088b --- /dev/null +++ b/Documentation/mobile-images/menu.jpg diff --git a/Documentation/mobile-manual.html b/Documentation/mobile-manual.html.git index cdbf3d1d9..835ad63f3 100644 --- a/Documentation/mobile-manual.html +++ b/Documentation/mobile-manual.html.git @@ -413,33 +413,24 @@ asciidoc.install(3); <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="paragraph"><p><span class="blue"><em>Beta release, February 2016</em></span></p></div> -<div class="admonitionblock"> -<table><tr> -<td class="icon"> -<img src="./images/icons/important.png" alt="Important" /> -</td> -<td class="content">For this BETA release it is critical that users report any problems -with the use of the mobile software. After all, one of the objectives -of a beta release is to distribute the software to a broader circle -of users using different Android devices and configurations in order to -iron out any bugs, errors or inconsistencies. Please report -such issues by email to <a href="mailto:subsurface@subsurface-divelog.org">subsurface@subsurface-divelog.org</a></td> -</tr></table> -</div> -<div class="paragraph"><p>Welcome as a user of <em>Subsurface</em>, an advanced dive logging program with +<div class="paragraph"><p><span class="blue"><em>Version 1.0, March 2016</em></span></p></div> +<div class="paragraph"><p>Welcome as a user of <em>Subsurface</em>, advanced dive logging software with extensive infrastructure to describe, organize, interpret and print scuba and free dives. <em>Subsurface</em> offers many advantages over other similar software solutions, including compatibility with Windows, Mac-OS/X, Linux (many -distributions) as well as Android. In addition, <em>Subsurface</em> allows downloading dive -information from most dive computers. <em>Subsurface</em> software is open-source.</p></div> +distributions) and Android (iOS under development). In addition, <em>Subsurface</em> is +open-source software that allows downloading dive +information from most dive computers.</p></div> <div class="sect1"> <h2 id="_introducing_subsurface_mobile">1. Introducing Subsurface-mobile</h2> <div class="sectionbody"> -<div class="paragraph"><p><em>Subsurface-mobile</em> is an extension of <em>Subsurface</em> that runs on laptop and +<div class="paragraph"><p><em>Subsurface-mobile</em> is an extension of <em>Subsurface</em> on laptop and tabletop computers. It runs on Android smartphone and tablet devices and is a -tool for viewing or sharing dive information at dive sites. It also allows +tool for viewing or sharing dive information at dive sites where a larger +computer is not useful. <em>Subsurface-mobile</em> also allows the gathering of GPS locations where dives are performed.</p></div> +<div class="paragraph"><p>A version of <em>Subsurface-mobile</em> for iOS is under development but not yet +ready for testing.</p></div> <div class="paragraph"><p>While <em>Subsurface-mobile</em> allows one to enter and save dive information using an Android device, users of <em>Subsurface-mobile</em> typically use the mobile app as an extension of the laptop/desktop version of <em>Subsurface</em>. @@ -448,7 +439,8 @@ can be shared by the Android version as well as the desktop version. While the desktop version of <em>Subsurface</em> shows much more detailed information for each dive, the mobile version allows one to have a more accessible dive log on a dive trip, useful for proving dive experience to dive shops or to review -previous dives. <em>Subsurface-mobile</em> allows one to:</p></div> +previous dives.</p></div> +<div class="paragraph"><p><em>Subsurface-mobile</em> allows one to:</p></div> <div class="ulist"><ul> <li> <p> @@ -488,14 +480,19 @@ View the localities of recorded GPS positions and of dives </p> </li> </ul></div> -<div class="paragraph"><p>These items are discussed in greater detail in the following text.</p></div> +<div class="paragraph"><p>These items are discussed in greater detail in the following text. +What <em>Subsurface-mobile</em> does not support (at this time) is downloading +dive data directly from a dive computer. That still has to happen with +<em>Subsurface</em> on a desktop or laptop computer. We are investigating ways +to support downloading from a subset of the supported dive computers on +Android devices, but this is not yet ready for testing.</p></div> </div> </div> <div class="sect1"> <h2 id="_installing_em_subsurface_mobile_em_on_an_android_device">2. Installing <em>Subsurface-mobile</em> on an Android device</h2> <div class="sectionbody"> -<div class="paragraph"><p>Install <em>Subsurface-mobile</em> from the Google -Play Store. Search for <em>Subsurface-mobile</em> and install it.</p></div> +<div class="paragraph"><p>Find <em>Subsurface-mobile</em> in the <em>Google +Play Store</em>. Search for <em>Subsurface-mobile</em> and install it.</p></div> </div> </div> <div class="sect1"> @@ -503,26 +500,27 @@ Play Store. Search for <em>Subsurface-mobile</em> and install it.</p></div> <div class="sectionbody"> <div class="paragraph"><p>Upon starting <em>Subsurface-mobile</em> for the first time, a Subsurface splash screen is shown while the program loads. On some devices this -may take several seconds. After loading, the <em>landing screen</em> appears -(see image on left, below). There are three options.</p></div> +may take several seconds. After loading, the <em>Cloud Credentials screen</em> appears +(see image below).</p></div> <div class="imageblock" style="text-align:center;"> <div class="content"> <img src="mobile-images/landingscreen.jpg" alt="FIGURE: Mobile landing screen" /> </div> </div> <div class="paragraph"><p>Since <em>Subsurface</em> is largely dependent on a dive log saved on the Internet, -select the top option "Connect to Cloudstorage" and enter an email address -and password for access to the <em>Subsurface</em> Internet storage server. If -you do not have credentials to log in, this is obtained through the -desktop version of <em>Subsurface</em>. When entering a password, it is possible to check +provide a user-ID and password for access to the <em>Subsurface Cloud</em>. These +credentials are obtained by opening the desktop version of <em>Subsurface</em> and +by clicking <em>File → Preferences → Network</em>, explained in detail in the +user manual for the <em>Subsurface</em> desktop version. Once the account has +been created and verified using the desktop version one can use <em>Subsurface-mobile</em>.</p></div> +<div class="paragraph"><p>When entering a password, it is possible to check a checkbox that enables the text of the password to be shown. Checking the check box labelled "Remember" allows <em>Susburface-mobile</em> to keep the -credentials for subsequent logins (see image on right, above). -Having entered the credentials, tap "Save". -<em>Subsurface-mobile</em> attempts to download the existing dive log from the -Internet server. Appropriate messages are shown onscreen. Finally -a list of dives are shown (image on left, below).</p></div> -<div class="paragraph"><p>For the beta release, do not choose the options "Transfer from dive computer" or "Add dive manually"</p></div> +credentials for subsequent logins (see image above). +Having entered the credentials, tap the disk icon at the bottom of the screen. +<em>Subsurface-mobile</em> attempts to download the existing dive log from the_Subsurface_ cloud +server. Appropriate messages are shown onscreen. Finally +a list of dives are shown.</p></div> </div> </div> <div class="sect1"> @@ -530,95 +528,112 @@ a list of dives are shown (image on left, below).</p></div> <div class="sectionbody"> <div class="paragraph"><p>Once the dive list has been downloaded from the Internet, <em>Subsurface-mobile</em> keeps a local -copy on the Android device. This means that, if there is no Internet connection +copy on the mobile device. This means that, if there is no Internet connection at a dive site, one can still access the local copy and view and manipulate dive information. If there is Internet connectivity, <em>Subsurface-mobile</em> accesses the Internet-based dive log to verify that the local copy is still the -same as the Internet-stored copy. If not, the local copy is synchronised with the version on -the Internet.</p></div> +same as the Internet-stored copy. If not, the local copy and the copy on +the server are synchronised.</p></div> </div> </div> <div class="sect1"> -<h2 id="_the_action_button">5. The Action Button</h2> +<h2 id="_a_few_remarks_about_the_user_interface">5. A Few Remarks About The User Interface</h2> <div class="sectionbody"> -<div class="paragraph"><p>At the bottom of of most Subsurface-mobile screens is a round button that provides -information and enables several actions. The Action Button often has one -or more triangular arrow points. Arrows alongside the <em>Action Button</em> indicate -drag movements that are available by dragging the <em>Action Button</em>. Arrows indicate -that one or more <em>Action Screens</em> are available(i.e. menus that become visible as side -panels) On the other hand icons inside the <em>Action Button</em> indicate -specific actions that can be performed by tapping the button. Examples of different -formats of the <em>Action Button</em> are presented in the images below:</p></div> -<div class="admonitionblock"> -<table><tr> -<td class="icon"> -<img src="mobile-images/Left.jpg" alt="Important" /> -</td> -<td class="content">This action button indicates that an <em>Action Panel</em> can be viewed -by dragging the <em>Action Button</em> to the right. Doing this exposes the main <em>Action Panel</em> -that allows many actions with respect to one’s dive log. The different <em>Action Panels</em> -are described below.</td> -</tr></table> -</div> -<div class="admonitionblock"> -<table><tr> -<td class="icon"> -<img src="mobile-images/LeftRight.jpg" alt="Important" /> -</td> -<td class="content">This action button indicates that one of two different <em>Action Panels</em> can be viewed -by dragging the <em>Action Button</em> either to the right or to the left.</td> -</tr></table> -</div> -<div class="admonitionblock"> -<table><tr> -<td class="icon"> -<img src="mobile-images/Edit.jpg" alt="Important" /> -</td> -<td class="content">This action button contains an icon that indicates that, in addition to the drag action -described above, one can edit one or more fields by tapping the <em>Action Button</em>.</td> -</tr></table> -</div> -<div class="admonitionblock"> -<table><tr> -<td class="icon"> -<img src="mobile-images/Quit.jpg" alt="Important" /> -</td> -<td class="content">This action button contains an icon that indicates that, in addition to the drag action -described above, one can abord or an edit of dive data by tapping the <em>Action Button</em>.</td> -</tr></table> +<div class="paragraph"><p>At the bottom of many Subsurface-mobile screens is a round button that provides for +several actions and which allows the selection of the main affirmative action +(see image above and image below). +On Android devices, use the Android Back +button for "cancel", "discard" or "back" actions. For example, when +editing dive information, tapping the action button saves the changes, the +Android back button can be used to cancel the edit without saving changes.</p></div> +<div class="imageblock" style="text-align:center;"> +<div class="content"> +<img src="mobile-images/actionbutton.jpg" alt="FIGURE: Action Button" /> </div> </div> +<div class="paragraph"><p>Instead of the more traditional "hamburger" menu button in the top left or +right corner of the screen to open menus, <em>Subsurface-mobile</em> uses a +different user interaction philosophy based on the Kirigami framework +developed by the Plasma developers. To open the main menu one has +three options:</p></div> +<div class="ulist"><ul> +<li> +<p> +Tap on the right-arrow symbol in the lower left corner of the screen + (easy to reach for hand held devices) +</p> +</li> +<li> +<p> +Swipe towards the right across the left edge of the screen +</p> +</li> +<li> +<p> +Drag the action button visible on most screens with the main action to + the right +</p> +</li> +</ul></div> +<div class="imageblock" style="text-align:center;"> +<div class="content"> +<img src="mobile-images/menu.jpg" alt="FIGURE: Dive management subpanel" /> +</div> +</div> +<div class="paragraph"><p>The images above indicate some of the important features of the menu system. +On the left is the main menu that is activated as described above. In the middle is +the menu that opens if one taps the <em>GPS</em> option on the main menu. On the right is +the menu that opens if one taps the <em>Manage Dives</em> option on the main menu.</p></div> +<div class="paragraph"><p>Similarly, the context menu (currently only available on the dive details screen) can be +opened one of these three ways:</p></div> +<div class="ulist"><ul> +<li> +<p> +Tap on the left-arrow symbol in the lower right corner of the screen +</p> +</li> +<li> +<p> +Swipe to the left across the right edge of the screen +</p> +</li> +<li> +<p> +Drag the action button to the left +</p> +</li> +</ul></div> +</div> </div> <div class="sect1"> <h2 id="_viewing_the_dive_list">6. Viewing the Dive List</h2> <div class="sectionbody"> <div class="paragraph"><p>Most of the actions of <em>Subsurface-mobile</em> center around the dives on the -dive list. One can scroll up and down the dive list. Tapping a dive on -the list brings up a display of <em>Details View</em> for that dive. -This includes the dive profile as well as additional information and notes -(see image on right, below).</p></div> -<div class="paragraph"><p>One can view other dives by swiping the <em>Details view</em> to the right (for the -previous dive) or to the left (following dive).</p></div> +dive list. While the dive list is loading from the cloud, +a message appears at the bottom of the screen, indicating that the cloud is +being accessed (see image on left, below). Once the list is loaded one can scroll up and down. +Tapping a dive on the list brings up a display of <em>Details View</em> for that dive (see image on right below). +This includes the dive profile as well as additional information and notes.</p></div> <div class="imageblock" style="text-align:center;"> <div class="content"> <img src="mobile-images/divelist.jpg" alt="FIGURE: Dive list screen" /> </div> </div> +<div class="paragraph"><p>One can view other dives by swiping the <em>Details view</em> to the right (for the +previous dive) or to the left (following dive).</p></div> </div> </div> <div class="sect1"> <h2 id="_editing_dive_details">7. Editing dive details.</h2> <div class="sectionbody"> -<div class="paragraph"><p>At the bottom of the screen an <em>Action Button</em> -allows aditional actions with respect to a dive that is being shown. In the -details screen (image on right, above) the action button shows a pencil. +<div class="paragraph"><p>At the bottom of the dive details screen the <em>Action Button</em> contains a pencil (image on right, above). Tapping the button brings up a panel with edit boxes that allows one to change the existing dive information, e.g. adding text to the dive notes or changing the names or values of some of the information (see image below). It may be necessary to scroll the window to access all the information. -At the bottom of the edit screen is a "Save" button. Tap this to save +At the bottom of the edit screen is a <em>Save</em> action button. Tap this to save the new information. Having saved the data, the dive list screen is -shown. To cancel any edits, tap the Action Button.</p></div> +updated and shown. To cancel any edits, tap the Android Back Button.</p></div> <div class="imageblock" style="text-align:center;"> <div class="content"> <img src="mobile-images/editdive.jpg" alt="FIGURE: Dive edit screen" /> @@ -627,54 +642,86 @@ shown. To cancel any edits, tap the Action Button.</p></div> </div> </div> <div class="sect1"> -<h2 id="_dive_log_management">8. Dive log management</h2> +<h2 id="_adding_a_new_dive_to_the_dive_list">8. Adding a new dive to the dive list</h2> +<div class="sectionbody"> +<div class="paragraph"><p>It is also possible to add an additional dive to the existing dive list. On the +main menu tap <em>Manage dives → Add dive manually</em>. This opens a screen that is +identical to the editing screen discussed above. When a dive is added manually, one +cannot directly add a dive profile from a dive computer. However, if one does not use a +dive computer, the duration, depth and several other bits of information about +the new dive can be entered. The <em>Action button</em> at the bottom of the screen +contains a disk symbol. Tap this to save the new dive. To cancel any edits, tap the Android Back Button. +The left-hand image below shows a screenshot of a dive being created and the right-hand image shows +the same dive in <em>Details View</em>.</p></div> +<div class="imageblock" style="text-align:center;"> +<div class="content"> +<img src="mobile-images/createdive.jpg" alt="FIGURE: Dive edit screen" /> +</div> +</div> +</div> +</div> +<div class="sect1"> +<h2 id="_deleting_a_dive">9. Deleting a dive</h2> <div class="sectionbody"> -<div class="paragraph"><p>A central part of <em>Subsurface-mobile</em> is the ability to store the dive log on the Internet. +<div class="paragraph"><p>The <em>details view</em> of a dive has a context menu on the right-hand side that can be activated as described above +(e.g. by tapping the arrow icon at the bottom right of the screen or by dragging the <em>Action Button</em> to the left). +The context menu has a single item: "Delete dive". If this option is tapped, the dive shown in the <em>Details View</em> +is deleted. One has a brief opportunity to undo the delete by tapping the <em>undo</em> message that appears at the bottom of +the screen. If the <em>undo</em> message is not tapped, the dive is deleted.</p></div> +</div> +</div> +<div class="sect1"> +<h2 id="_dive_log_management">10. Dive log management</h2> +<div class="sectionbody"> +<div class="paragraph"><p>A central part of <em>Subsurface-mobile</em> is the ability to store the dive +log using the <em>Subsurface</em> cloud storage. This provides security against loss or damage to the dive information caintained in a local copy of -the dive log. This ability is accessed throug the Action Panel. Drag the Action Button to the right. -(alternatively tap the Menu button at the top left of the Android screen). -This brings up the Action Panel (image on left, below). Tap the option "Manage dives" (image below in middle).</p></div> +the dive log and allows the desktop version of <em>Subsurface</em> to +access changes made using the mobile device. This ability is accessed +throug the main menu (by dragging the Action Button to the right, or +alternatively tap the right angle button at the bottom left of the screen). + Tap the option <em>Manage dives</em>, enabling a number of options:</p></div> <div class="sect2"> -<h3 id="_upload_dive_log_to_the_internet">8.1. Upload dive log to the Internet</h3> -<div class="paragraph"><p>Assuming that the correct credentials have been specified, one can upload the dives contained on the Androis device -to the Internet by tapping the option "Upload to cloud". This saves the local -copy of the dive log to the cloud.</p></div> +<h3 id="_add_new_dive_manually">10.1. Add new dive manually</h3> +<div class="paragraph"><p>This is described above under the section dealing with the dive list.</p></div> </div> <div class="sect2"> -<h3 id="_download_dive_log_from_the_internet">8.2. Download dive log from the Internet</h3> -<div class="paragraph"><p>In the dive management subpanel, tap the option "Refresh" (image below in middle). This causes -the local divelog to be refreshed from the cloud so that the Internet and local versions are synchronised.</p></div> -<div class="imageblock" style="text-align:center;"> -<div class="content"> -<img src="mobile-images/managedive.jpg" alt="FIGURE: Dive management subpanel" /> -</div> +<h3 id="_upload_dive_log_to_the_em_subsurface_em_cloud_storage">10.2. Upload dive log to the <em>Subsurface</em> cloud storage</h3> +<div class="paragraph"><p>One can upload the dives contained on the mobile device +to the <em>Subsurface</em> cloud storage by tapping the option <em>Upload to cloud</em>. +This synchronizes the local changes to +the dive log with the cloud storage.</p></div> </div> +<div class="sect2"> +<h3 id="_download_dive_log_from_the_cloud_storage">10.3. Download dive log from the cloud storage</h3> +<div class="paragraph"><p>In the dive management subpanel, tap the option <em>Refresh</em>, causing +the local divelog to be refreshed from the cloud so that the cloud +and local versions are synchronised.</p></div> </div> <div class="sect2"> -<h3 id="_add_dive_manually">8.3. Add dive manually</h3> -<div class="paragraph"><p>Dives can easily be entered by hand. This allows one to describe a dive and add it to the dive log. -In the dive management subpanel tap "Add dive manually". The edit screen opens (image above on right). -Fill in all the appropriate information, then tap the "Save" button at the bottom of the screen. It may be -necessary to scroll down to see the "Save" button. The dive is then saved as part of the dive log. In the -details dive view, a profile of the dive is created.</p></div> +<h3 id="_changing_the_login_credentials_on_the_em_subsurface_em_cloud">10.4. Changing the login credentials on the <em>Subsurface</em> cloud</h3> +<div class="paragraph"><p>It may be necessary to change one’s login credentials, for instance if one’s email +address (initially used as a credential) has changed. To change the credentials, +open the main menu and tap <em>Cloud credentials</em>. This opens the setup screen +for specifying new credentials.</p></div> </div> </div> </div> <div class="sect1"> -<h2 id="_recording_dive_locations_using_gps">9. Recording dive locations using GPS.</h2> +<h2 id="_recording_dive_locations_using_gps">11. Recording dive locations using GPS.</h2> <div class="sectionbody"> <div class="paragraph"><p>The fact that most smartphones have GPS facilities allows one to record the locations of dives. One can take the smartphone on the dive boat -during a dive and locations will be automatically recorded at regular intervals.</p></div> +during a dive and locations will be automatically recorded at regular intervals. +These locations can then be applied to dives in the dive list. Here is how it’s done:</p></div> <div class="sect2"> -<h3 id="_setting_up_the_gps">9.1. Setting up the GPS</h3> -<div class="paragraph"><p>Drag the Action Button to the right. This brings up the Action Panel (image -on left, above). Select "Preferences". Now specify the way -in which GPS data need to be automatically collected (image on left, below). One can specify that +<h3 id="_setting_up_the_gps">11.1. Setting up the GPS</h3> +<div class="paragraph"><p>Open the main menu and tap <em>GPS → Preferences</em>. Now specify the way +in which GPS data need to be automatically collected (image on right, below). One can specify that data are collected at regular intervals, e.g. every 10 minutes, or at regular distances, e.g. after the boat has moved more than 200m, or a combination of both of the above approaches. Provide the appropriate information and -tap the "Save" button. The program is now ready to collect GPS positions.</p></div> +tap the <em>Save</em> action button. The program is now ready to collect GPS positions.</p></div> <div class="imageblock" style="text-align:center;"> <div class="content"> <img src="mobile-images/gpssetup.jpg" alt="FIGURE: GPS setup screen" /> @@ -682,47 +729,39 @@ tap the "Save" button. The program is now ready to collect GPS positions.</p></d </div> </div> <div class="sect2"> -<h3 id="_collecting_gps_positions">9.2. Collecting GPS positions</h3> +<h3 id="_collecting_gps_positions">11.2. Collecting GPS positions</h3> <div class="paragraph"><p>Ensure that the GPS on the Android device has been activated. At the bottom -of the Action Panel is a check box "Run location service" (image on right, above). +of the GPS submenu is a check box <em>Run location service</em> (image on left, above). Check this box and <em>Subsurface-mobile</em> starts to collect GPS locations automatically, following the preferences specified as described above. After the dive one can deactivate the collection of GPS data by de-activating -the same check box at the bottom of the Action Panel.</p></div> +the same check box at the bottom of the main menu.</p></div> </div> <div class="sect2"> -<h3 id="_storing_the_gps_data">9.3. Storing the GPS data</h3> -<div class="paragraph"><p>Activate the Action Panel (image on right, above) by drawing the Action Button to the right. -Select the "GPS" option that brings up a submenu of GPS-related actions -(image on left, below). Tap "Upload GPS data" that saves the GPS data -on the <em>Subsurface</em> Internet server. These GPS data are saved separately +<h3 id="_storing_the_gps_data_on_the_em_subsurface_em_cloud">11.3. Storing the GPS data on the <em>Subsurface</em> cloud</h3> +<div class="paragraph"><p>Activate the main menu and select the <em>GPS</em> option that brings up the submenu of GPS-related actions +(image on left, above). Tap <em>Upload GPS data</em> that saves the GPS data +on the <em>Subsurface</em> cloud server. These GPS data are saved <strong>separately</strong> from the other dive log data. All collected GPS data are kept on the Android device, independent of whether they have been uploaded or not.</p></div> </div> <div class="sect2"> -<h3 id="_viewing_gps_data">9.4. Viewing GPS data</h3> -<div class="paragraph"><p>From the GPS submenu (image on left, below) select "Show GPS fixes". This brings +<h3 id="_downloading_gps_data_from_the_em_subsurface_em_cloud">11.4. Downloading GPS data from the <em>Subsurface</em> cloud</h3> +<div class="paragraph"><p>Download the GPS data that have been saved on the cloud by +selecting <em>Download GPS Data</em> from the GPS subpanel.</p></div> +</div> +<div class="sect2"> +<h3 id="_viewing_gps_data">11.5. Viewing GPS data</h3> +<div class="paragraph"><p>From the GPS submenu (image on left, above) select <em>Show GPS fixes</em>. This brings up a list of GPS positions obtained using the location service (image -in middle, below). Two actions are possible for each of the locations, enabled if -one taps the handle (the three horisontal stripes on the right, see image in middle, below) and +on left, below). Two actions are possible for each of the locations, enabled if +one taps the handle (the three horisontal stripes on the right, see image on left, below) and then drags the specific item to the left (image on right, below). This exposes two options. Tapping the dustbin deletes this particular GPS location. Tapping the teardrop-shaped icon (actually a Google Maps pin) opens up Google Maps with a pin -indicating the exact map position of the record being viewed. The two above +indicating the exact map position of the GPS record being viewed. The two above options can be hidden by drawing the GPS record to the right, again using the handle.</p></div> -</div> -</div> -</div> -<div class="sect1"> -<h2 id="_saving_gps_positions_on_the_internet">10. Saving GPS positions on the Internet</h2> -<div class="sectionbody"> -<div class="paragraph"><p>One can save the collected GPS data on the Internet by -selecting "Upload GPS Data" from the GPS submanu (Image on left, below).</p></div> -<div class="sect2"> -<h3 id="_downloading_gps_data_from_the_internet">10.1. Downloading GPS data from the Internet</h3> -<div class="paragraph"><p>One can download the GPS data that have been saved on the Internet by -selecting "Download GPS Data" from the GPS subpanel (Image on left, below).</p></div> <div class="imageblock" style="text-align:center;"> <div class="content"> <img src="mobile-images/gpsmanagement.jpg" alt="FIGURE: GPS management" /> @@ -730,14 +769,14 @@ selecting "Download GPS Data" from the GPS subpanel (Image on left, below).</p>< </div> </div> <div class="sect2"> -<h3 id="_applying_gps_data_to_dives_in_the_dive_log">10.2. Applying GPS data to dives in the dive log</h3> +<h3 id="_applying_gps_data_to_dives_in_the_dive_log">11.6. Applying GPS data to dives in the dive log</h3> <div class="paragraph"><p>Assuming that all the dives have been entered into the dive log or have -been downloaded from the Internet, one can apply the GPS positions to -these dives. GPS positions can therefore only be applied to dives in the dive log. -From the GPS subpanel, tap "Apply GPS fixes" (image on left, above). The dive log contains the start +been downloaded from the <em>Subsurface</em> cloud, one can apply the GPS positions to +these dives. GPS positions can therefore only be applied to dives in the dive list. +From the GPS subpanel, tap <em>Apply GPS fixes</em>. The dive list contains the start and end times of each dive. Now, <em>Subsurface-mobile</em> applies the first GPS position that falls within the dive period of each dive. This results -in a GPS position for each dive that is saved as part of the dive log.</p></div> +in a GPS position for each dive that is saved as part of the dive list.</p></div> </div> </div> </div> @@ -745,8 +784,7 @@ in a GPS position for each dive that is saved as part of the dive log.</p></div> <div id="footnotes"><hr /></div> <div id="footer"> <div id="footer-text"> -Last updated - 2016-02-09 12:16:22 SAST +Last updated 2016-03-10 08:57:35 PST </div> </div> </body> diff --git a/Documentation/mobile-manual.txt b/Documentation/mobile-manual.txt index 001ac0020..a1a189dd5 100644 --- a/Documentation/mobile-manual.txt +++ b/Documentation/mobile-manual.txt @@ -1,10 +1,8 @@ // Subsurface-mobile User Manual // ============================= -// :author: Manual authors: Jacco van Koll, Dirk Hohndel, Reinout Hoornweg, -// Linus Torvalds, Miika Turkia, Amit Chaudhuri, Jan Schubert, Willem -// Ferguson, Salvador Cuñat, Pedro Neves -// :revnumber: 4.5 -// :revdate: October 2015 +// :author: Manual authors: Willem Ferguson, Dirk Hohndel +// :revnumber: 1.0 +// :revdate: March 2016 :icons: :toc: :toc-placement: manual @@ -19,53 +17,46 @@ image::mobile-images/banner.jpg["Banner",align="center"] toc::[] -[blue]#_Beta release, March 2016_# +[blue]#_Version 1.0, March 2016_# -IMPORTANT: For this BETA release it is critical that users report any problems -with the use of the mobile software. After all, one of the objectives -of a beta release is to distribute the software to a broader circle -of users using different Android devices and configurations in order to -iron out any bugs, errors or inconsistencies. Please report -such issues by email to subsurface@subsurface-divelog.org - -Welcome as a user of _Subsurface_, an advanced dive logging program for -desktop and laptop computers with +Welcome as a user of _Subsurface_, advanced dive logging software with extensive infrastructure to describe, organize, interpret and print scuba and free dives. _Subsurface_ offers many advantages over other similar -software solutions, including compatibility with Windows, Mac-OS/X, and Linux (many -distributions). _Subsurface_ allows downloading dive -information from most dive computers. _Subsurface_ software is open-source. +software solutions, including compatibility with Windows, Mac-OS/X, Linux (many +distributions) and Android (iOS under development). In addition, _Subsurface_ is +open-source software that allows downloading dive +information from most dive computers. Introducing Subsurface-mobile ----------------------------- -_Subsurface-mobile_ is an extension of _Subsurface_ which runs on Android -smartphone and tablet devices and is a tool for viewing or sharing dive -information at dive sites. It also allows +_Subsurface-mobile_ is an extension of _Subsurface_ on laptop and +tabletop computers. It runs on Android smartphone and tablet devices and is a +tool for viewing or sharing dive information at dive sites where a larger +computer is not useful. _Subsurface-mobile_ also allows the gathering of GPS locations where dives are performed. A version of _Subsurface-mobile_ for iOS is under development but not yet ready for testing. -While _Subsurface-mobile_ allows you to enter and save dive information -on a mobile device, at this point it is designed as -an extension of the laptop/desktop version of _Subsurface_. -To make this possible, you need to store your dive logs in the -_Subsurface_ cloud storage on the Internet, which then makes it possible -to share the dive log between the Android version and the desktop version. +While _Subsurface-mobile_ allows one to enter and save dive information +using an Android device, users of _Subsurface-mobile_ typically use the +mobile app as an extension of the laptop/desktop version of _Subsurface_. +This allows the storage of dive logs on the Internet and which +can be shared by the Android version as well as the desktop version. While the desktop version of _Subsurface_ shows much more detailed information -for each dive, the mobile version allows you to have a more accessible dive log +for each dive, the mobile version allows one to have a more accessible dive log on a dive trip, useful for proving dive experience to dive shops or to review previous dives. -_Subsurface-mobile_ allows you to: +_Subsurface-mobile_ allows one to: -- Download existing dive log information from _Subsurface_ cloud storage. -- View this information on an mobile device. +- Download existing dive log information from the Internet. +- View this information on an Android device. - Edit many of the dive log data fields, e.g. divemaster, buddy, equipment or notes about a dive. -- Manually add new dive records to your dive log. -- Store the updated dive log in the Subsurface cloud. +- Create and add new dive records to one's dive log. +- Store the updated dive log on the Internet. - Record, store and apply GPS positions of dives. - View the localities of recorded GPS positions and of dives on a map. @@ -79,43 +70,34 @@ Android devices, but this is not yet ready for testing. == Installing _Subsurface-mobile_ on an Android device -Install _Subsurface-mobile_ from the Google -Play Store. Search for _Subsurface-mobile_ and install it. - -For the Beta version you still need to opt-in to the beta test at -https://play.google.com/apps/testing/org.subsurfacedivelog.mobile -This will no longer be necessary once the first release has been published -to the play store. +Find _Subsurface-mobile_ in the _Google +Play Store_. Search for _Subsurface-mobile_ and install it. == Using _Subsurface-mobile_ for the first time Upon starting _Subsurface-mobile_ for the first time, a Subsurface -splash screen is shown while the program loads. This -may take several seconds. After loading, the _landing screen_ appears -(see image on left, below). +splash screen is shown while the program loads. On some devices this +may take several seconds. After loading, the _Cloud Credentials screen_ appears +(see image below). image::mobile-images/landingscreen.jpg["FIGURE: Mobile landing screen",align="center"] -Since _Subsurface-mobile_ is largely dependent on a dive log saved in the -_Subsurface_ cloud storage, the first step is connecting to your cloud -storage. Please note that you need to set up your cloud cloud storage -credentials from the full _Subsurface_ application on your desktop or -laptop. Only once the account has been created and verified from there -will you be able to use _Subsurface-mobile_. - -Enter the email address and password that you used when creating your -_Subsurface_ cloud storage account. To make it easier to type in the -password correctly, you can make it visible by checking the corresponding -box. +Since _Subsurface_ is largely dependent on a dive log saved on the Internet, +provide a user-ID and password for access to the _Subsurface Cloud_. These +credentials are obtained by opening the desktop version of _Subsurface_ and +by clicking _File -> Preferences -> Network_, explained in detail in the +user manual for the _Subsurface_ desktop version. Once the account has +been created and verified using the desktop version one can use _Subsurface-mobile_. -Checking the +When entering a password, it is possible to check +a checkbox that enables the text of the password to be shown. Checking the check box labelled "Remember" allows _Susburface-mobile_ to keep the -credentials for subsequent logins (see image on right, above). -Having entered the credentials, tap the "Save" button and the bottom of -the screen. -_Subsurface-mobile_ attempts to download the existing dive log from the -_Subsurface_ cloud storage. Appropriate messages are shown onscreen. Finally -a list of dives are shown (image on left, below). +credentials for subsequent logins (see image above). +Having entered the credentials, tap the disk icon at the bottom of the screen. +_Subsurface-mobile_ attempts to download the existing dive log from the_Subsurface_ cloud +server. Appropriate messages are shown onscreen. Finally +a list of dives are shown. + == Local copy of the dive log and synchronisation with Internet @@ -130,163 +112,188 @@ the server are synchronised. == A Few Remarks About The User Interface +At the bottom of many Subsurface-mobile screens is a round button that provides for +several actions and which allows the selection of the main affirmative action +(see image above and image below). +On Android devices, use the Android Back +button for "cancel", "discard" or "back" actions. For example, when +editing dive information, tapping the action button saves the changes, the +Android back button can be used to cancel the edit without saving changes. + +image::mobile-images/actionbutton.jpg["FIGURE: Action Button",align="center"] + Instead of the more traditional "hamburger" menu button in the top left or -right corner of the screen to open menues, _Subsurface-mobile_ uses a +right corner of the screen to open menus, _Subsurface-mobile_ uses a different user interaction philosophy based on the Kirigami framework -developed by the Plasme developers. In order to open the main menu you -have three options: +developed by the Plasma developers. To open the main menu one has +three options: -- Tap on the right angle symbol in the lower left corner of the screen - (easy to reach when holding your device in your hand) -- Swipe across the left edge of the screen from the outside +- Tap on the right-arrow symbol in the lower left corner of the screen + (easy to reach for hand held devices) +- Swipe towards the right across the left edge of the screen - Drag the action button visible on most screens with the main action to the right -Similarly, the context menu (only available on a few screens) can be -opened one of these three ways: - -- Tap on the left angle symbol in the lower right corner of the screen -- Swipe across the right edge of the screen from the outside -- Drag the action button to the left +image::mobile-images/menu.jpg["FIGURE: Dive management subpanel",align="center"] -== The Action Button +The images above indicate some of the important features of the menu system. +On the left is the main menu that is activated as described above. In the middle is +the menu that opens if one taps the _GPS_ option on the main menu. On the right is +the menu that opens if one taps the _Manage Dives_ option on the main menu. -At the bottom of of most Subsurface-mobile screens is a round button that provides -the main, affirmative action. On Android devices, use the Android Back -button for "cancel", "discard" or "back" actions. For example, when -editing dive information, tapping the action button saves the changes, the -Android back button can be used to cancel the edit without saving changes. +Similarly, the context menu (currently only available on the dive details screen) can be +opened one of these three ways: +- Tap on the left-arrow symbol in the lower right corner of the screen +- Swipe to the left across the right edge of the screen +- Drag the action button to the left == Viewing the Dive List Most of the actions of _Subsurface-mobile_ center around the dives on the -dive list. One can scroll up and down the dive list. Tapping a dive on -the list brings up a display of _Details View_ for that dive. -This includes the dive profile as well as additional information and notes -(see image on right, below). +dive list. While the dive list is loading from the cloud, +a message appears at the bottom of the screen, indicating that the cloud is +being accessed (see image on left, below). Once the list is loaded one can scroll up and down. +Tapping a dive on the list brings up a display of _Details View_ for that dive (see image on right below). +This includes the dive profile as well as additional information and notes. + +image::mobile-images/divelist.jpg["FIGURE: Dive list screen",align="center"] One can view other dives by swiping the _Details view_ to the right (for the previous dive) or to the left (following dive). -image::mobile-images/divelist.jpg["FIGURE: Dive list screen",align="center"] - == Editing dive details. -At the bottom of the screen an _Action Button_ -allows aditional actions with respect to a dive that is being shown. In the -details screen (image on right, above) the action button shows a pencil. +At the bottom of the dive details screen the _Action Button_ contains a pencil (image on right, above). Tapping the button brings up a panel with edit boxes that allows one to change the existing dive information, e.g. adding text to the dive notes or changing the names or values of some of the information (see image below). It may be necessary to scroll the window to access all the information. -At the bottom of the edit screen is a "Save" button. Tap this to save +At the bottom of the edit screen is a _Save_ action button. Tap this to save the new information. Having saved the data, the dive list screen is -shown. To cancel any edits, tap the Android Back Button. +updated and shown. To cancel any edits, tap the Android Back Button. image::mobile-images/editdive.jpg["FIGURE: Dive edit screen",align="center"] +== Adding a new dive to the dive list + +It is also possible to add an additional dive to the existing dive list. On the +main menu tap _Manage dives -> Add dive manually_. This opens a screen that is +identical to the editing screen discussed above. When a dive is added manually, one +cannot directly add a dive profile from a dive computer. However, if one does not use a +dive computer, the duration, depth and several other bits of information about +the new dive can be entered. The _Action button_ at the bottom of the screen +contains a disk symbol. Tap this to save the new dive. To cancel any edits, tap the Android Back Button. +The left-hand image below shows a screenshot of a dive being created and the right-hand image shows +the same dive in _Details View_. + +image::mobile-images/createdive.jpg["FIGURE: Dive edit screen",align="center"] + +== Deleting a dive + +The _details view_ of a dive has a context menu on the right-hand side that can be activated as described above +(e.g. by tapping the arrow icon at the bottom right of the screen or by dragging the _Action Button_ to the left). +The context menu has a single item: "Delete dive". If this option is tapped, the dive shown in the _Details View_ +is deleted. One has a brief opportunity to undo the delete by tapping the _undo_ message that appears at the bottom of +the screen. If the _undo_ message is not tapped, the dive is deleted. + == Dive log management A central part of _Subsurface-mobile_ is the ability to store the dive -log in the _Subsurface_ cloud storage. +log using the _Subsurface_ cloud storage. This provides security against loss or damage to the dive information caintained in a local copy of -the dive log and allows to access any changes made on the mobile device -from _Subsurface_ on your desktop or laptop. This ability is accessed -throug the main menu. Drag the Action Button to the right, or -alternatively tap the right angle button at the bottom left of the screen. -This brings up the Action Panel (image on left, below). Tap the option "Manage dives" (image below in middle). +the dive log and allows the desktop version of _Subsurface_ to +access changes made using the mobile device. This ability is accessed +throug the main menu (by dragging the Action Button to the right, or +alternatively tap the right angle button at the bottom left of the screen). + Tap the option _Manage dives_, enabling a number of options: + +=== Add new dive manually + +This is described above under the section dealing with the dive list. === Upload dive log to the _Subsurface_ cloud storage -You can simply upload the dives contained on the mobile device -to the _Subsurface_ cloud storage by tapping the option "Upload to cloud". +One can upload the dives contained on the mobile device +to the _Subsurface_ cloud storage by tapping the option _Upload to cloud_. This synchronizes the local changes to the dive log with the cloud storage. -=== Download dive log from the Internet - -In the dive management subpanel, tap the option "Refresh" (image below in middle). This causes -the local divelog to be refreshed from the cloud so that the Internet and local versions are synchronised. +=== Download dive log from the cloud storage +In the dive management subpanel, tap the option _Refresh_, causing +the local divelog to be refreshed from the cloud so that the cloud +and local versions are synchronised. -image::mobile-images/managedive.jpg["FIGURE: Dive management subpanel",align="center"] +=== Changing the login credentials on the _Subsurface_ cloud -=== Add dive manually +It may be necessary to change one's login credentials, for instance if one's email +address (initially used as a credential) has changed. To change the credentials, +open the main menu and tap _Cloud credentials_. This opens the setup screen +for specifying new credentials. -Dives can easily be entered by hand. This allows one to describe a dive and add it to the dive log. -In the dive management subpanel tap "Add dive manually". The edit screen opens (image above on right). -Fill in all the appropriate information, then tap the "Save" button at the bottom of the screen. -The dive is then saved as part of the dive log. In the -details dive view, a profile of the dive is created. == Recording dive locations using GPS. The fact that most smartphones have GPS facilities allows one to record the locations of dives. One can take the smartphone on the dive boat during a dive and locations will be automatically recorded at regular intervals. +These locations can then be applied to dives in the dive list. Here is how it's done: === Setting up the GPS -Drag the Action Button to the right. This brings up the Action Panel (image -on left, above). Select "Preferences". Now specify the way -in which GPS data need to be automatically collected (image on left, below). One can specify that +Open the main menu and tap _GPS -> Preferences_. Now specify the way +in which GPS data need to be automatically collected (image on right, below). One can specify that data are collected at regular intervals, e.g. every 10 minutes, or at regular distances, e.g. after the boat has moved more than 200m, or a combination of both of the above approaches. Provide the appropriate information and -tap the "Save" button. The program is now ready to collect GPS positions. +tap the _Save_ action button. The program is now ready to collect GPS positions. image::mobile-images/gpssetup.jpg["FIGURE: GPS setup screen",align="center"] === Collecting GPS positions Ensure that the GPS on the Android device has been activated. At the bottom -of the Action Panel is a check box "Run location service" (image on right, above). +of the GPS submenu is a check box _Run location service_ (image on left, above). Check this box and _Subsurface-mobile_ starts to collect GPS locations automatically, following the preferences specified as described above. After the dive one can deactivate the collection of GPS data by de-activating -the same check box at the bottom of the Action Panel. +the same check box at the bottom of the main menu. -=== Storing the GPS data +=== Storing the GPS data on the _Subsurface_ cloud -Activate the Action Panel (image on right, above) by drawing the Action Button to the right. -Select the "GPS" option that brings up a submenu of GPS-related actions -(image on left, below). Tap "Upload GPS data" that saves the GPS data -on the _Subsurface_ Internet server. These GPS data are saved separately +Activate the main menu and select the _GPS_ option that brings up the submenu of GPS-related actions +(image on left, above). Tap _Upload GPS data_ that saves the GPS data +on the _Subsurface_ cloud server. These GPS data are saved *separately* from the other dive log data. All collected GPS data are kept on the Android device, independent of whether they have been uploaded or not. +=== Downloading GPS data from the _Subsurface_ cloud + +Download the GPS data that have been saved on the cloud by +selecting _Download GPS Data_ from the GPS subpanel. + === Viewing GPS data -From the GPS submenu (image on left, below) select "Show GPS fixes". This brings +From the GPS submenu (image on left, above) select _Show GPS fixes_. This brings up a list of GPS positions obtained using the location service (image -in middle, below). Two actions are possible for each of the locations, enabled if -one taps the handle (the three horisontal stripes on the right, see image in middle, below) and +on left, below). Two actions are possible for each of the locations, enabled if +one taps the handle (the three horisontal stripes on the right, see image on left, below) and then drags the specific item to the left (image on right, below). This exposes two options. Tapping the dustbin deletes this particular GPS location. Tapping the teardrop-shaped icon (actually a Google Maps pin) opens up Google Maps with a pin -indicating the exact map position of the record being viewed. The two above +indicating the exact map position of the GPS record being viewed. The two above options can be hidden by drawing the GPS record to the right, again using the handle. -== Saving GPS positions on the Internet - -One can save the collected GPS data on the Internet by -selecting "Upload GPS Data" from the GPS submanu (Image on left, below). - -=== Downloading GPS data from the Internet - -One can download the GPS data that have been saved on the Internet by -selecting "Download GPS Data" from the GPS subpanel (Image on left, below). - image::mobile-images/gpsmanagement.jpg["FIGURE: GPS management",align="center"] === Applying GPS data to dives in the dive log Assuming that all the dives have been entered into the dive log or have -been downloaded from the Internet, one can apply the GPS positions to -these dives. GPS positions can therefore only be applied to dives in the dive log. -From the GPS subpanel, tap "Apply GPS fixes" (image on left, above). The dive log contains the start +been downloaded from the _Subsurface_ cloud, one can apply the GPS positions to +these dives. GPS positions can therefore only be applied to dives in the dive list. +From the GPS subpanel, tap _Apply GPS fixes_. The dive list contains the start and end times of each dive. Now, _Subsurface-mobile_ applies the first GPS position that falls within the dive period of each dive. This results -in a GPS position for each dive that is saved as part of the dive log. +in a GPS position for each dive that is saved as part of the dive list. diff --git a/Documentation/mobile-manual_es.html.git b/Documentation/mobile-manual_es.html.git new file mode 100644 index 000000000..e9af75571 --- /dev/null +++ b/Documentation/mobile-manual_es.html.git @@ -0,0 +1,813 @@ +<!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.9" /> +<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"> +/*<+'])'); + // Function that scans the DOM tree for header elements (the DOM2 + // nodeIterator API would be a better technique but not supported by all + // browsers). + var iterate = function (el) { + for (var i = el.firstChild; i != null; i = i.nextSibling) { + if (i.nodeType == 1 /* Node.ELEMENT_NODE */) { + var mo = re.exec(i.tagName); + if (mo && (i.getAttribute("class") || i.getAttribute("className")) != "float") { + result[result.length] = new TocEntry(i, getText(i), mo[1]-1); + } + iterate(i); + } + } + } + iterate(el); + return result; + } + + var toc = document.getElementById("toc"); + if (!toc) { + return; + } + + // Delete existing TOC entries in case we're reloading the TOC. + var tocEntriesToRemove = []; + var i; + for (i = 0; i < toc.childNodes.length; i++) { + var entry = toc.childNodes[i]; + if (entry.nodeName.toLowerCase() == 'div' + && entry.getAttribute("class") + && entry.getAttribute("class").match(/^toclevel/)) + tocEntriesToRemove.push(entry); + } + for (i = 0; i < tocEntriesToRemove.length; i++) { + toc.removeChild(tocEntriesToRemove[i]); + } + + // Rebuild TOC entries. + var entries = tocEntries(document.getElementById("content"), toclevels); + for (var i = 0; i < entries.length; ++i) { + var entry = entries[i]; + if (entry.element.id == "") + entry.element.id = "_toc_" + i; + var a = document.createElement("a"); + a.href = "#" + entry.element.id; + a.appendChild(document.createTextNode(entry.text)); + var div = document.createElement("div"); + div.appendChild(a); + div.className = "toclevel" + entry.toclevel; + toc.appendChild(div); + } + if (entries.length == 0) + toc.parentNode.removeChild(toc); +}, + + +///////////////////////////////////////////////////////////////////// +// Footnotes generator +///////////////////////////////////////////////////////////////////// + +/* Based on footnote generation code from: + * http://www.brandspankingnew.net/archive/2005/07/format_footnote.html + */ + +footnotes: function () { + // Delete existing footnote entries in case we're reloading the footnodes. + var i; + var noteholder = document.getElementById("footnotes"); + if (!noteholder) { + return; + } + var entriesToRemove = []; + for (i = 0; i < noteholder.childNodes.length; i++) { + var entry = noteholder.childNodes[i]; + if (entry.nodeName.toLowerCase() == 'div' && entry.getAttribute("class") == "footnote") + entriesToRemove.push(entry); + } + for (i = 0; i < entriesToRemove.length; i++) { + noteholder.removeChild(entriesToRemove[i]); + } + + // Rebuild footnote entries. + var cont = document.getElementById("content"); + var spans = cont.getElementsByTagName("span"); + var refs = {}; + var n = 0; + for (i=0; i<spans.length; i++) { + if (spans[i].className == "footnote") { + n++; + var note = spans[i].getAttribute("data-note"); + if (!note) { + // Use [\s\S] in place of . so multi-line matches work. + // Because JavaScript has no s (dotall) regex flag. + note = spans[i].innerHTML.match(/\s*\[([\s\S]*)]\s*/)[1]; + spans[i].innerHTML = + "[<a id='_footnoteref_" + n + "' href='#_footnote_" + n + + "' title='View footnote' class='footnote'>" + n + "</a>]"; + spans[i].setAttribute("data-note", note); + } + noteholder.innerHTML += + "<div class='footnote' id='_footnote_" + n + "'>" + + "<a href='#_footnoteref_" + n + "' title='Return to text'>" + + n + "</a>. " + note + "</div>"; + var id =spans[i].getAttribute("id"); + if (id != null) refs["#"+id] = n; + } + } + if (n == 0) + noteholder.parentNode.removeChild(noteholder); + else { + // Process footnoterefs. + for (i=0; i<spans.length; i++) { + if (spans[i].className == "footnoteref") { + var href = spans[i].getElementsByTagName("a")[0].getAttribute("href"); + href = href.match(/#.*/)[0]; // Because IE return full URL. + n = refs[href]; + spans[i].innerHTML = + "[<a href='#_footnote_" + n + + "' title='View footnote' class='footnote'>" + n + "</a>]"; + } + } + } +}, + +install: function(toclevels) { + var timerId; + + function reinstall() { + asciidoc.footnotes(); + if (toclevels) { + asciidoc.toc(toclevels); + } + } + + function reinstallAndRemoveTimer() { + clearInterval(timerId); + reinstall(); + } + + timerId = setInterval(reinstall, 500); + if (document.addEventListener) + document.addEventListener("DOMContentLoaded", reinstallAndRemoveTimer, false); + else + window.onload = reinstallAndRemoveTimer; +} + +} +asciidoc.install(3); +/*]]>*/ +</script> +</head> +<body class="article"> +<div id="header"> +</div> +<div id="content"> +<div class="imageblock" style="text-align:center;"> +<div class="content"> +<img src="mobile-images/banner.jpg" alt="Banner" /> +</div> +</div> +<div class="paragraph"><p><span class="big">Subsurface-mobile para Android: MANUAL DE USUARIO</span></p></div> +<div class="paragraph"><p><strong>Manual author</strong>: Willem Ferguson</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="paragraph"><p><span class="blue"><em>Version 1.0, Marzo 2016</em></span></p></div> +<div class="paragraph"><p>Bienvenido a <em>Subsurface</em> un avanzado programa de registro de inmersiones con +extensa infraestructura para describir, organizar, interpretar e imprimir +inmersiones, con botella o a pulmón. <em>Subsurface</em> ofrece muchas ventajas sobre +otras soluciones de software similares, entre ellas se incluye la +compatibilidad con Windows, Mac-OS/X, Linux (muchas distribuciones) y también +Android (en desarrollo un versión para iOS). Además, <em>Subsurface</em> es un +software de código abierto que permite descargar información de inmersiones +desde la mayoría de los ordenadores de buceo.</p></div> +<div class="sect1"> +<h2 id="_presentación_de_subsurface_mobile">1. Presentación de Subsurface-mobile</h2> +<div class="sectionbody"> +<div class="paragraph"><p><em>Subsurface-mobile</em> es una extensión del <em>Subsurface</em> que ejecutamos en +ordenadores portátiles o de sobremesa. Corre en teléfonos y tabletas Android y +es una herramienta para ver o compartir información de buceo en el mismo lugar +de la inmersión, donde no suele ser posible disponer de un ordenador completo. +También permite recoger las posiciones GPS donde se realizan las inmersiones.</p></div> +<div class="paragraph"><p>Está en desarrollo una versión de <em>Subsurface-mobile</em> para iOS pero aún no +está lista para probarla.</p></div> +<div class="paragraph"><p>Aunque <em>Subsurface-mobile</em> nos permite introducir y guardar información de +buceo utilizando un dispositivo android, los usuarios de <em>Subsurface-mobile</em> +utilizan, habitualmente, la app como una extension de la versión para +ordenadores de <em>Subsurface</em>. Esto permite el almacenamiento de divelogs en +Internet, que pueden compartirse entre las versiones para Android y PC. Aunque +la versión para ordenador muestra una información mucho más detallada de cada +inmersión, la versión para móvil nos permite tener esta información más +accesible durante un viaje, lo que puede resultar util para demostrar nuestra +experiencia de buceo en tiendas o centros, o simplemente revisar inmersiones +anteriores.</p></div> +<div class="paragraph"><p><em>Subsurface-mobile</em> nos permite:</p></div> +<div class="ulist"><ul> +<li> +<p> +Descargar la información del divelog desde internet. +</p> +</li> +<li> +<p> +Visualizar esta información en un dispositivo Android. +</p> +</li> +<li> +<p> +Editar muchos de los campos de datos del registro, por ejemplo, el + dive-master, el compañero, las anotaciones, etc. +</p> +</li> +<li> +<p> +Crear y añadir nuevas inmersiones a nuestro divelog. Guardar el divelog + actualizado en Internet. +</p> +</li> +<li> +<p> +Registrar y aplicar las posiciones GPS de las inmersiones. +</p> +</li> +<li> +<p> +Visualizar las localizaciones de las posiciones GPS en un mapa. +</p> +</li> +</ul></div> +<div class="paragraph"><p>Todas estas posibilidades se comentan con más detalle en el texto siguiente.</p></div> +<div class="paragraph"><p>Lo que <em>Subsurface-mobile</em> no soporta (en estos momentos) es descargar datos +directamente desde el ordenador de buceo. Esto aún debe realizarse desde un +PC. Estamos investigando formas de descargar desde una parte de los +ordenadores de buceo soportados a los dispositivos Android, pero esta parte +aún no esta lista para ser probada.</p></div> +</div> +</div> +<div class="sect1"> +<h2 id="_instalar_em_subsurface_mobile_em_en_un_dispositivo_android">2. Instalar <em>Subsurface-mobile</em> en un dispositivo Android</h2> +<div class="sectionbody"> +<div class="paragraph"><p>Encuentra Subsurface-mobile_ en el Play Store de Google. Busca +<em>Subsurface-mobile</em> e instalalo.</p></div> +</div> +</div> +<div class="sect1"> +<h2 id="_utilizar_em_subsurface_mobile_em_por_primera_vez">3. Utilizar <em>Subsurface-mobile</em> por primera vez</h2> +<div class="sectionbody"> +<div class="paragraph"><p>Al iniciar <em>Subsurface-mobile</em> se muestra una pantalla de presentación +mientras se carga el programa. En algunos dispositivos esto puede llevar +algunos segundos. Tras haber cargado, aparecerá una <em>pantalla de credenciales +de la nube</em> (ver la imagen de la izquierda, a continuación).</p></div> +<div class="imageblock" style="text-align:center;"> +<div class="content"> +<img src="mobile-images/landingscreen.jpg" alt="FIGURA: Pantalla inicial" /> +</div> +</div> +<div class="paragraph"><p>Dado que <em>Subsurface-mobile</em> es totalmente dependiente del registro guardado +en Internet, introduce una dirección de correo electrónico y la password para +acceder al servidor de almacenamiento en la nube de <em>Subsurface</em>. Estas +credenciales se obtienen abriendo la versión de <em>Subsurface</em> para ordenador y +pulsando <em>Archivo → Preferencias → Red</em>, y se explica en detalle en el manual +de la versión de ordenador de <em>Subsurface</em>. Una vez que se ha creado y +verificado utilizando la versión de ordenador, se puede utilizar +<em>Subsurface-mobile</em>.</p></div> +<div class="paragraph"><p>Al introducir la password, es posible seleccionar la casilla "Recordar" que +permite a <em>Subsurface-mobile</em> guardar las credenciales para próximas +conexiones (ver la imagen anterior), Tras haber introducido las credenciales, +pulsa el icono del disco, en la parte inferior de la pantalla. +<em>Subsurface-mobile</em> intentará descargar la información guardada en el servidor +y, finalmente, se mostrará una lista de inmersiones (imagen a la izquierda a +continuación).</p></div> +</div> +</div> +<div class="sect1"> +<h2 id="_copia_local_del_divelog_y_sincronización_con_internet">4. Copia local del divelog y sincronización con Internet</h2> +<div class="sectionbody"> +<div class="paragraph"><p>Una vez que se haya descargado la lista de inmersiones desde Internet, +<em>Subsurface-mobile</em> guardará una copia en el dispositivo móvil. Esto +significa que, si no hay conexión a Internet en el punto de buceo, aún se +puede acceder a la copia local y manipular la información. Si existe conexión +a Internet, <em>Subsurface-mobile</em> accede al registro guardado en la nube para +verificar si la copia local es aún la misma que la remota. Si no fuera así, la +copia local se sincronizará con la versión del servidor.</p></div> +</div> +</div> +<div class="sect1"> +<h2 id="_algunas_observaciones_sobre_la_interfaz_de_usuario">5. Algunas observaciones sobre la interfaz de usuario</h2> +<div class="sectionbody"> +<div class="paragraph"><p>En la parte inferior de muchas de las pantallas de <em>Subsurface-mobile</em>, +aparece un botón redondo que habilita varias acciones y permite la selección +de la principal acción afirmativa (ver las imágenes anterior y a +continuación). En dispositivos Android, se utiliza el botón "Volver" para +realizar las acciones de cancelar, descartar o volver. Por ejemplo, al editar +una inmersión, pulsar el <em>botón de acciones</em> guarda los cambios, mientras que +el botón "Volver" de Android, puede utilizarse para cancelar la edición sin +guardar los cambios.</p></div> +<div class="imageblock" style="text-align:center;"> +<div class="content"> +<img src="mobile-images/actionbutton.jpg" alt="FIGURE: Action Button" /> +</div> +</div> +<div class="paragraph"><p>Para abrir menús, en vez del tradicional botón tipo "hamburgesa" en la esquina +superior derecha de la pantalla, <em>Subsurface-mobile</em> utiliza una filosofía de +interacción con el usuario diferente, basada en el sistema Kirigami, diseñado +por el equipo de desarrolladores de Plasma. Para abrir el menú principal se +dispone de tres opciones:</p></div> +<div class="ulist"><ul> +<li> +<p> +Pulsar el símbolo de flecha-derecha en la parte inferior izquierda de la + pantalla (fácil de alcanzar con una sola mano en dispositivos tipo + smartphone). +</p> +</li> +<li> +<p> +Desplazar hacia la derecha desde el borde de la pantalla. +</p> +</li> +<li> +<p> +Arrastrar hacia la derecha el <em>botón de acciones</em> visible en la mayoría de + pantallas. +</p> +</li> +</ul></div> +<div class="imageblock" style="text-align:center;"> +<div class="content"> +<img src="mobile-images/menu.jpg" alt="FIGURE: Dive management subpanel" /> +</div> +</div> +<div class="paragraph"><p>Las imágenes anteriores muestran algunas de las características más +importantes del sistema de menús. A la izquierda está el menú principal que +se activa como se ha explicado antes. En el centro está el menú que se abre al +pulsar la opción <em>GPS</em> desde el principal. A la derecha, el menú que se abre +al pulsar la opción _Manage Dives_desde el principal.</p></div> +<div class="paragraph"><p>De forma similar, el menú contextual (actualmente solo disponible en la +pantalla de detalles de la inmersión) puede abrirse de una de estas tres +formas:</p></div> +<div class="ulist"><ul> +<li> +<p> +Pulsando en el símbolo de la flecha-izquierda en la esquina inferior derecha + de la pantalla. +</p> +</li> +<li> +<p> +Desplazando hacia la izquierda desde el borde de la pantalla. +</p> +</li> +<li> +<p> +Arrastrando el "botón de acciones" hacia la izquierda. +</p> +</li> +</ul></div> +</div> +</div> +<div class="sect1"> +<h2 id="_visualizar_la_lista_de_inmersiones">6. Visualizar la lista de inmersiones</h2> +<div class="sectionbody"> +<div class="paragraph"><p>La mayoría de las acciones de <em>Subsurface-mobile</em> se centran alrededor de las +inmersiones de la lista. Mientras se carga la lista desde la nube, aparece un +mensaje en la parte inferior de la pantalla, indicando que se está accediendo +a la misma (ver imagen izquierda a continuación). Una vez que la lista se ha +cargado, nos podemos desplazar arriba y abajo. +Al pulsar una inmersión de la lista aparecerá una pantalla de <em>Vista de +Detalles</em> para dicho buceo (ver imagen derecha a continuación). En ella se +incluye el perfil de la inmersión, información adicional y notas.</p></div> +<div class="imageblock" style="text-align:center;"> +<div class="content"> +<img src="mobile-images/divelist.jpg" alt="FIGURE: Dive list screen" /> +</div> +</div> +<div class="paragraph"><p>Se pueden visualizar otras inmersiones desplazando la <em>Vista de Detalles</em> +hacia la derecha, para el buceo posterior, o hacia la izquierda para el +anterior.</p></div> +</div> +</div> +<div class="sect1"> +<h2 id="_editar_los_detalles_de_la_inmersión">7. Editar los detalles de la inmersión.</h2> +<div class="sectionbody"> +<div class="paragraph"><p>En la parte inferior de la pantalla, el <em>Botón de Acciones</em> contiene un lápiz +(imagen anterior derecha). +Pulsar el botón hará que se muestre un panel con casillas de edición que nos +permitirán modificar la información existente, p.e. añadiendo texto a las +notas o cambiando nombres o valores en otras casillas (ver imagen a +continuación). Puede ser necesario desplazar la ventana para poder acceder a +toda la información. En la parte inferior de la pantalla de edición, el +<em>Botón de Acciones</em> mostrará un icono de <em>Guardar</em>. Púlsalo para guardar los +cambios efectuados. Tras haberlos guardado, la pantalla de la lista de +inmersiones se actualizará y mostrará. Si se desea cancelar la edición se +pulsa el botón "Volver" de Android.</p></div> +<div class="imageblock" style="text-align:center;"> +<div class="content"> +<img src="mobile-images/editdive.jpg" alt="FIGURE: Dive edit screen" /> +</div> +</div> +</div> +</div> +<div class="sect1"> +<h2 id="_añadir_una_nueva_inmersión_a_la_lista">8. Añadir una nueva inmersión a la lista</h2> +<div class="sectionbody"> +<div class="paragraph"><p>También es posible añadir una inmersión adicional a la lista existente. Desde +el menú principal, pulsar <em>Manage dives → Add dive manually</em>. Esto abrirá una +pantalla idéntica a la de edición comentada anteriormente. Al añadir +manualmente una inmersión, no se puede añadir un perfil del ordenador de +buceo. Sin embargo, si no se usa un ordenador de buceo, la duración, +profundidad y varias otras informaciones pueden ser introducidas. +El <em>Botón de acciones</em>, en la parte inferior de la pantalla, contendrá el +icono de un disco. Púlsalo para guardar la nueva inmersión. Para cancelar las +ediciones pulsa el botón "Volver" de Android. +La imagen de la izquierda, a continuación, muestra una captura de pantalla de +una inmersión que está siendo creada, y la imagen de la derecha muestra la +misma inmersión en la <em>Vista de detalles</em>.</p></div> +<div class="imageblock" style="text-align:center;"> +<div class="content"> +<img src="mobile-images/createdive.jpg" alt="FIGURE: Dive edit screen" /> +</div> +</div> +</div> +</div> +<div class="sect1"> +<h2 id="_borrar_una_inmersión">9. Borrar una inmersión</h2> +<div class="sectionbody"> +<div class="paragraph"><p>La <em>Vista de detalles</em> de una inmersión tiene un menú contextual en el lado +derecho que puede activarse como se ha descrito anteriormente (p.e. pulsando +el icono de flecha en la parte inferior derecha de la pantalla o arrastrando +el <em>Botón de acciones</em> hacia la izquierda). +El menú contextual contiene una sola opción: "Delete dive". Si se pulsa esta +opción, la inmersión mostrada en la <em>Vista de detalles</em> será borrada. Se +dispone de una breve posibilidad de anular el borrado pulsando el botón <em>undo</em> +en el mensaje que aparecerá en la parte inferior de la pantalla. Si no se +pulsa dicho botón la inmersión se borrará.</p></div> +</div> +</div> +<div class="sect1"> +<h2 id="_mantenimiento_del_divelog">10. Mantenimiento del divelog</h2> +<div class="sectionbody"> +<div class="paragraph"><p>Una parte central de <em>Subsurface-mobile</em> es su capacidad para guardar la +información de buceo haciendo uso del almacenamiento en la nube de +<em>Subsurface</em>. Esto proporciona seguridad frente a los daños o la perdida de +la copia del divelog guardada localmente y permite a la versión de sobremesa +de <em>Subsurface</em> acceder a los cambios realizados con el dispositivo móvil. +Se accede a esta capacidad a través del menú principal (arrastrando el <em>Botón +de acciones</em> hacia la derecha, o pulsando la flecha en la parte inferior +izquierda de la pantalla). +Pulsa la opción <em>Manage dives</em> que nos permitirá un nuevo número de acciones:</p></div> +<div class="sect2"> +<h3 id="_añadir_manualmente_una_nueva_inmersión">10.1. Añadir manualmente una nueva inmersión</h3> +<div class="paragraph"><p>Se ha descrito anteriormente en la sección referida a la lista de inmersiones.</p></div> +</div> +<div class="sect2"> +<h3 id="_subir_el_divelog_al_almacenamiento_en_la_nube_de_em_subsurface_em">10.2. Subir el divelog al almacenamiento en la nube de <em>Subsurface</em></h3> +<div class="paragraph"><p>Se pueden subir las inmersiones contenidas en el dispositivo móvil al +almacenamiento en la nube de <em>Subsurface</em> pulsando la opción <em>Upload to +cloud</em>. Esto sincronizará los cambios efectuados localmente con el divelog en +el almacenamiento en la nube.</p></div> +</div> +<div class="sect2"> +<h3 id="_descargar_el_divelog_desde_internet">10.3. Descargar el divelog desde internet</h3> +<div class="paragraph"><p>En el subpanel <em>Dive managements</em>, pulsa la opción <em>Refresh</em> . Con esto se +consigue que la copia local del dispositivo Android se sincronice con la copia +del divelog en la nube.</p></div> +</div> +<div class="sect2"> +<h3 id="_cambiar_las_credenciales_de_acceso_a_la_nube_de_em_subsurface_em">10.4. Cambiar las credenciales de acceso a la nube de <em>Subsurface</em></h3> +<div class="paragraph"><p>Puede que sea necesario cambiar las credenciales de acceso, por ejemplo si +nuestro correo electrónico (usado como credencial) ha cambiado. Para modificar +los datos en <em>Subsuface-mobile</em>, abre el menú principal y pulsa <em>Cloud +credentials</em>. Esto abrirá la pantalla de ajustes para especificar las nuevas +credenciales.</p></div> +</div> +</div> +</div> +<div class="sect1"> +<h2 id="_registrar_puntos_de_buceo_usando_el_gps">11. Registrar puntos de buceo usando el GPS</h2> +<div class="sectionbody"> +<div class="paragraph"><p>El hecho de que la mayoría de smartphones dispongan de GPS nos permite +registrar las ubicaciones de las inmersiones. Se puede llevar el teléfono en +el barco de buceo durante la inmersión y se registrarán automáticamente +posiciones a intervalos regulares. +Estas posiciones pueden ser aplicadas a inmersiones de la lista. A +continuación se explica como:</p></div> +<div class="sect2"> +<h3 id="_ajustar_el_gps">11.1. Ajustar el GPS</h3> +<div class="paragraph"><p>Abre el menú principal y pulsa <em>GPS → Preferences</em>. Ahora especifica la forma +en que se deben recoger automáticamente las posiciones (imagen derecha a +continuación). Se puede especificar que los datos se recojan a intervalos +regulares, p.e. cada 10 minutos, o a distancias regulares, p.e. después de que +el barco se haya desplazado más de 200 metros, o una combinación de ambas +opciones. Introduce los parámetros deseados y pulsa el botón "Guardar". El +app está preparada para recoger posiciones GPS.</p></div> +<div class="imageblock" style="text-align:center;"> +<div class="content"> +<img src="mobile-images/gpssetup.jpg" alt="FIGURE: GPS setup screen" /> +</div> +</div> +</div> +<div class="sect2"> +<h3 id="_recoger_posiciones_gps">11.2. Recoger posiciones GPS</h3> +<div class="paragraph"><p>Asegúrate de que el GPS del dispositivo Android está activado. En la parte +inferior del menú principal y del submenú <em>GPS</em> hay una casilla seleccionable +<em>Run location service</em> (imagen derecha a continuación). Selecciona la casilla y +<em>Subsurface-mobile</em> comenzará a tomar lecturas de las posiciones GPS siguiendo +las indicaciones guardadas en las preferencias, como se ha indicado +anteriormente. Despues de la inmersión se puede detener el servicio, +deseleccionando la misma casilla que se había marcado antes.</p></div> +</div> +<div class="sect2"> +<h3 id="_guardar_los_datos_del_gps_en_la_nube_de_em_subsurface_em">11.3. Guardar los datos del GPS en la nube de <em>Subsurface</em></h3> +<div class="paragraph"><p>Activa el menú principal y selecciona la opción <em>GPS</em> que despliega el menú de +acciones relacionadas con el GPS (imagen anterior izquierda). Pulsa <em>Upload +GPS data</em> con ello, los datos recogidos en el dispositivo móvil se guardarán +en la nube de <em>Subsurface</em>. Estas posiciones GPS se guardan <strong>separadamente</strong> +del resto de datos del divelog. Todas las posiciones GPS recogidas se +conservan en el dispositivo móvil, independientemente de que se hayan subido o +no.</p></div> +</div> +<div class="sect2"> +<h3 id="_visualizar_datos_gps">11.4. Visualizar datos GPS</h3> +<div class="paragraph"><p>Desde el menú GPS (imagen izquierda anterior) seleccionar <em>Show GPS fixes</em>. +Esto mostrará una lista de posiciones GPS recogidas usando en servicio de +ubicación (imagen izquierda a continuación). Se pueden efectuar dos acciones +para cada una de las posiciones, habilitadas si se pulsa el botón (las tres +bandas horizontales de la derecha, ver imagen izquierda a continuación) y se +arrastra la posición hacia la izquierda (imagen derecha a continuación). Esta +acción muestra dos opciones. Pulsar la papelera borra esta posición GPS en +concreto. Pulsar el icono con forma de lágrima (un pin de Google maps) abre +Google Maps en el navegador con un pin que indica la posición exacta en el +mapa de las coordenadas GPS que se están visualizando. Las dos opciones +indicadas, pueden ocultarse de nuevo arrastrando el registro de posición hacia +la derecha.</p></div> +<div class="imageblock" style="text-align:center;"> +<div class="content"> +<img src="mobile-images/gpsmanagement.jpg" alt="FIGURE: GPS management" /> +</div> +</div> +</div> +<div class="sect2"> +<h3 id="_aplicar_los_datos_gps_a_las_inmersiones_del_divelog">11.5. Aplicar los datos GPS a las inmersiones del divelog</h3> +<div class="paragraph"><p>Suponiendo que se hayan introducido a mano o descargado desde la nube de +<em>Subsurface</em> todas las inmersiones del divelog, se pueden aplicar las +posiciones GPS a dichas inmersiones. Las posiciones GPS solo pueden aplicarse +a inmersiones que estén en la lista de inmersiones. +Desde el subpanel <em>GPS</em>, pulsar <em>Apply GPS fixes</em>. La lista de inmersiones +contiene la hora de inicio y fin de cada inmersión. <em>Subsurface-mobile</em> +aplicará la primera posición que se encuentre dentro del periodo de duración +del buceo, o la inmediatamente anterior al inicio si no hubiera ninguna dentro +del periodo.</p></div> +</div> +</div> +</div> +</div> +<div id="footnotes"><hr /></div> +<div id="footer"> +<div id="footer-text"> +Last updated 2016-03-13 12:43:54 PDT +</div> +</div> +</body> +</html> diff --git a/Documentation/mobile-manual_es.txt b/Documentation/mobile-manual_es.txt new file mode 100644 index 000000000..6cee275cc --- /dev/null +++ b/Documentation/mobile-manual_es.txt @@ -0,0 +1,324 @@ +// Subsurface-mobile User Manual +// ============================= +// :author: Manual authors: Willem Ferguson, Dirk Hohndel +// :revnumber: 1 +// :revdate: March 2016 +:icons: +:toc: +:toc-placement: manual +:numbered: +// :website: http://subsurface-divelog.org + +image::mobile-images/banner.jpg["Banner",align="center"] + +[big]#Subsurface-mobile para Android: MANUAL DE USUARIO# + +*Manual author*: Willem Ferguson + +toc::[] + +[blue]#_Version 1.0, Marzo 2016_# + +Bienvenido a _Subsurface_ un avanzado programa de registro de inmersiones con +extensa infraestructura para describir, organizar, interpretar e imprimir +inmersiones, con botella o a pulmón. _Subsurface_ ofrece muchas ventajas sobre +otras soluciones de software similares, entre ellas se incluye la +compatibilidad con Windows, Mac-OS/X, Linux (muchas distribuciones) y también +Android (en desarrollo un versión para iOS). Además, _Subsurface_ es un +software de código abierto que permite descargar información de inmersiones +desde la mayoría de los ordenadores de buceo. + +Presentación de Subsurface-mobile +---------------------------------- + +_Subsurface-mobile_ es una extensión del _Subsurface_ que ejecutamos en +ordenadores portátiles o de sobremesa. Corre en teléfonos y tabletas Android y +es una herramienta para ver o compartir información de buceo en el mismo lugar +de la inmersión, donde no suele ser posible disponer de un ordenador completo. +También permite recoger las posiciones GPS donde se realizan las inmersiones. + +Está en desarrollo una versión de _Subsurface-mobile_ para iOS pero aún no +está lista para probarla. + +Aunque _Subsurface-mobile_ nos permite introducir y guardar información de +buceo utilizando un dispositivo android, los usuarios de _Subsurface-mobile_ +utilizan, habitualmente, la app como una extension de la versión para +ordenadores de _Subsurface_. Esto permite el almacenamiento de divelogs en +Internet, que pueden compartirse entre las versiones para Android y PC. Aunque +la versión para ordenador muestra una información mucho más detallada de cada +inmersión, la versión para móvil nos permite tener esta información más +accesible durante un viaje, lo que puede resultar util para demostrar nuestra +experiencia de buceo en tiendas o centros, o simplemente revisar inmersiones +anteriores. + +_Subsurface-mobile_ nos permite: + +- Descargar la información del divelog desde internet. +- Visualizar esta información en un dispositivo Android. +- Editar muchos de los campos de datos del registro, por ejemplo, el + dive-master, el compañero, las anotaciones, etc. +- Crear y añadir nuevas inmersiones a nuestro divelog. Guardar el divelog + actualizado en Internet. +- Registrar y aplicar las posiciones GPS de las inmersiones. +- Visualizar las localizaciones de las posiciones GPS en un mapa. + +Todas estas posibilidades se comentan con más detalle en el texto siguiente. + +Lo que _Subsurface-mobile_ no soporta (en estos momentos) es descargar datos +directamente desde el ordenador de buceo. Esto aún debe realizarse desde un +PC. Estamos investigando formas de descargar desde una parte de los +ordenadores de buceo soportados a los dispositivos Android, pero esta parte +aún no esta lista para ser probada. + +== Instalar _Subsurface-mobile_ en un dispositivo Android + +Encuentra Subsurface-mobile_ en el Play Store de Google. Busca +_Subsurface-mobile_ e instalalo. + +== Utilizar _Subsurface-mobile_ por primera vez + +Al iniciar _Subsurface-mobile_ se muestra una pantalla de presentación +mientras se carga el programa. En algunos dispositivos esto puede llevar +algunos segundos. Tras haber cargado, aparecerá una _pantalla de credenciales +de la nube_ (ver la imagen de la izquierda, a continuación). + +image::mobile-images/landingscreen.jpg["FIGURA: Pantalla inicial",align="center"] + +Dado que _Subsurface-mobile_ es totalmente dependiente del registro guardado +en Internet, introduce una dirección de correo electrónico y la password para +acceder al servidor de almacenamiento en la nube de _Subsurface_. Estas +credenciales se obtienen abriendo la versión de _Subsurface_ para ordenador y +pulsando _Archivo -> Preferencias -> Red_, y se explica en detalle en el manual +de la versión de ordenador de _Subsurface_. Una vez que se ha creado y +verificado utilizando la versión de ordenador, se puede utilizar +_Subsurface-mobile_. + +Al introducir la password, es posible seleccionar la casilla "Recordar" que +permite a _Subsurface-mobile_ guardar las credenciales para próximas +conexiones (ver la imagen anterior), Tras haber introducido las credenciales, +pulsa el icono del disco, en la parte inferior de la pantalla. +_Subsurface-mobile_ intentará descargar la información guardada en el servidor +y, finalmente, se mostrará una lista de inmersiones (imagen a la izquierda a +continuación). + +== Copia local del divelog y sincronización con Internet + +Una vez que se haya descargado la lista de inmersiones desde Internet, +_Subsurface-mobile_ guardará una copia en el dispositivo móvil. Esto +significa que, si no hay conexión a Internet en el punto de buceo, aún se +puede acceder a la copia local y manipular la información. Si existe conexión +a Internet, _Subsurface-mobile_ accede al registro guardado en la nube para +verificar si la copia local es aún la misma que la remota. Si no fuera así, la +copia local se sincronizará con la versión del servidor. + +== Algunas observaciones sobre la interfaz de usuario + +En la parte inferior de muchas de las pantallas de _Subsurface-mobile_, +aparece un botón redondo que habilita varias acciones y permite la selección +de la principal acción afirmativa (ver las imágenes anterior y a +continuación). En dispositivos Android, se utiliza el botón "Volver" para +realizar las acciones de cancelar, descartar o volver. Por ejemplo, al editar +una inmersión, pulsar el _botón de acciones_ guarda los cambios, mientras que +el botón "Volver" de Android, puede utilizarse para cancelar la edición sin +guardar los cambios. + +image::mobile-images/actionbutton.jpg["FIGURE: Action Button",align="center"] + +Para abrir menús, en vez del tradicional botón tipo "hamburgesa" en la esquina +superior derecha de la pantalla, _Subsurface-mobile_ utiliza una filosofía de +interacción con el usuario diferente, basada en el sistema Kirigami, diseñado +por el equipo de desarrolladores de Plasma. Para abrir el menú principal se +dispone de tres opciones: + +- Pulsar el símbolo de flecha-derecha en la parte inferior izquierda de la + pantalla (fácil de alcanzar con una sola mano en dispositivos tipo + smartphone). +- Desplazar hacia la derecha desde el borde de la pantalla. +- Arrastrar hacia la derecha el _botón de acciones_ visible en la mayoría de + pantallas. + +image::mobile-images/menu.jpg["FIGURE: Dive management subpanel",align="center"] + +Las imágenes anteriores muestran algunas de las características más +importantes del sistema de menús. A la izquierda está el menú principal que +se activa como se ha explicado antes. En el centro está el menú que se abre al +pulsar la opción _GPS_ desde el principal. A la derecha, el menú que se abre +al pulsar la opción _Manage Dives_desde el principal. + +De forma similar, el menú contextual (actualmente solo disponible en la +pantalla de detalles de la inmersión) puede abrirse de una de estas tres +formas: + +- Pulsando en el símbolo de la flecha-izquierda en la esquina inferior derecha + de la pantalla. +- Desplazando hacia la izquierda desde el borde de la pantalla. +- Arrastrando el "botón de acciones" hacia la izquierda. + +== Visualizar la lista de inmersiones + +La mayoría de las acciones de _Subsurface-mobile_ se centran alrededor de las +inmersiones de la lista. Mientras se carga la lista desde la nube, aparece un +mensaje en la parte inferior de la pantalla, indicando que se está accediendo +a la misma (ver imagen izquierda a continuación). Una vez que la lista se ha +cargado, nos podemos desplazar arriba y abajo. +Al pulsar una inmersión de la lista aparecerá una pantalla de _Vista de +Detalles_ para dicho buceo (ver imagen derecha a continuación). En ella se +incluye el perfil de la inmersión, información adicional y notas. + +image::mobile-images/divelist.jpg["FIGURE: Dive list screen",align="center"] + +Se pueden visualizar otras inmersiones desplazando la _Vista de Detalles_ +hacia la derecha, para el buceo posterior, o hacia la izquierda para el +anterior. + +== Editar los detalles de la inmersión. + +En la parte inferior de la pantalla, el _Botón de Acciones_ contiene un lápiz +(imagen anterior derecha). +Pulsar el botón hará que se muestre un panel con casillas de edición que nos +permitirán modificar la información existente, p.e. añadiendo texto a las +notas o cambiando nombres o valores en otras casillas (ver imagen a +continuación). Puede ser necesario desplazar la ventana para poder acceder a +toda la información. En la parte inferior de la pantalla de edición, el +_Botón de Acciones_ mostrará un icono de _Guardar_. Púlsalo para guardar los +cambios efectuados. Tras haberlos guardado, la pantalla de la lista de +inmersiones se actualizará y mostrará. Si se desea cancelar la edición se +pulsa el botón "Volver" de Android. + +image::mobile-images/editdive.jpg["FIGURE: Dive edit screen",align="center"] + +== Añadir una nueva inmersión a la lista + +También es posible añadir una inmersión adicional a la lista existente. Desde +el menú principal, pulsar _Manage dives -> Add dive manually_. Esto abrirá una +pantalla idéntica a la de edición comentada anteriormente. Al añadir +manualmente una inmersión, no se puede añadir un perfil del ordenador de +buceo. Sin embargo, si no se usa un ordenador de buceo, la duración, +profundidad y varias otras informaciones pueden ser introducidas. +El _Botón de acciones_, en la parte inferior de la pantalla, contendrá el +icono de un disco. Púlsalo para guardar la nueva inmersión. Para cancelar las +ediciones pulsa el botón "Volver" de Android. +La imagen de la izquierda, a continuación, muestra una captura de pantalla de +una inmersión que está siendo creada, y la imagen de la derecha muestra la +misma inmersión en la _Vista de detalles_. + +image::mobile-images/createdive.jpg["FIGURE: Dive edit screen",align="center"] + +== Borrar una inmersión + +La _Vista de detalles_ de una inmersión tiene un menú contextual en el lado +derecho que puede activarse como se ha descrito anteriormente (p.e. pulsando +el icono de flecha en la parte inferior derecha de la pantalla o arrastrando +el _Botón de acciones_ hacia la izquierda). +El menú contextual contiene una sola opción: "Delete dive". Si se pulsa esta +opción, la inmersión mostrada en la _Vista de detalles_ será borrada. Se +dispone de una breve posibilidad de anular el borrado pulsando el botón _undo_ +en el mensaje que aparecerá en la parte inferior de la pantalla. Si no se +pulsa dicho botón la inmersión se borrará. + +== Mantenimiento del divelog + +Una parte central de _Subsurface-mobile_ es su capacidad para guardar la +información de buceo haciendo uso del almacenamiento en la nube de +_Subsurface_. Esto proporciona seguridad frente a los daños o la perdida de +la copia del divelog guardada localmente y permite a la versión de sobremesa +de _Subsurface_ acceder a los cambios realizados con el dispositivo móvil. +Se accede a esta capacidad a través del menú principal (arrastrando el _Botón +de acciones_ hacia la derecha, o pulsando la flecha en la parte inferior +izquierda de la pantalla). +Pulsa la opción _Manage dives_ que nos permitirá un nuevo número de acciones: + +=== Añadir manualmente una nueva inmersión + +Se ha descrito anteriormente en la sección referida a la lista de inmersiones. + +=== Subir el divelog al almacenamiento en la nube de _Subsurface_ + +Se pueden subir las inmersiones contenidas en el dispositivo móvil al +almacenamiento en la nube de _Subsurface_ pulsando la opción _Upload to +cloud_. Esto sincronizará los cambios efectuados localmente con el divelog en +el almacenamiento en la nube. + +=== Descargar el divelog desde internet + +En el subpanel _Dive managements_, pulsa la opción _Refresh_ . Con esto se +consigue que la copia local del dispositivo Android se sincronice con la copia +del divelog en la nube. + +=== Cambiar las credenciales de acceso a la nube de _Subsurface_ + +Puede que sea necesario cambiar las credenciales de acceso, por ejemplo si +nuestro correo electrónico (usado como credencial) ha cambiado. Para modificar +los datos en _Subsuface-mobile_, abre el menú principal y pulsa _Cloud +credentials_. Esto abrirá la pantalla de ajustes para especificar las nuevas +credenciales. + +== Registrar puntos de buceo usando el GPS + +El hecho de que la mayoría de smartphones dispongan de GPS nos permite +registrar las ubicaciones de las inmersiones. Se puede llevar el teléfono en +el barco de buceo durante la inmersión y se registrarán automáticamente +posiciones a intervalos regulares. +Estas posiciones pueden ser aplicadas a inmersiones de la lista. A +continuación se explica como: + +=== Ajustar el GPS + +Abre el menú principal y pulsa _GPS -> Preferences_. Ahora especifica la forma +en que se deben recoger automáticamente las posiciones (imagen derecha a +continuación). Se puede especificar que los datos se recojan a intervalos +regulares, p.e. cada 10 minutos, o a distancias regulares, p.e. después de que +el barco se haya desplazado más de 200 metros, o una combinación de ambas +opciones. Introduce los parámetros deseados y pulsa el botón "Guardar". El +app está preparada para recoger posiciones GPS. + +image::mobile-images/gpssetup.jpg["FIGURE: GPS setup screen",align="center"] + +=== Recoger posiciones GPS + +Asegúrate de que el GPS del dispositivo Android está activado. En la parte +inferior del menú principal y del submenú _GPS_ hay una casilla seleccionable +_Run location service_ (imagen derecha a continuación). Selecciona la casilla y +_Subsurface-mobile_ comenzará a tomar lecturas de las posiciones GPS siguiendo +las indicaciones guardadas en las preferencias, como se ha indicado +anteriormente. Despues de la inmersión se puede detener el servicio, +deseleccionando la misma casilla que se había marcado antes. + +=== Guardar los datos del GPS en la nube de _Subsurface_ + +Activa el menú principal y selecciona la opción _GPS_ que despliega el menú de +acciones relacionadas con el GPS (imagen anterior izquierda). Pulsa _Upload +GPS data_ con ello, los datos recogidos en el dispositivo móvil se guardarán +en la nube de _Subsurface_. Estas posiciones GPS se guardan *separadamente* +del resto de datos del divelog. Todas las posiciones GPS recogidas se +conservan en el dispositivo móvil, independientemente de que se hayan subido o +no. + +=== Visualizar datos GPS + +Desde el menú GPS (imagen izquierda anterior) seleccionar _Show GPS fixes_. +Esto mostrará una lista de posiciones GPS recogidas usando en servicio de +ubicación (imagen izquierda a continuación). Se pueden efectuar dos acciones +para cada una de las posiciones, habilitadas si se pulsa el botón (las tres +bandas horizontales de la derecha, ver imagen izquierda a continuación) y se +arrastra la posición hacia la izquierda (imagen derecha a continuación). Esta +acción muestra dos opciones. Pulsar la papelera borra esta posición GPS en +concreto. Pulsar el icono con forma de lágrima (un pin de Google maps) abre +Google Maps en el navegador con un pin que indica la posición exacta en el +mapa de las coordenadas GPS que se están visualizando. Las dos opciones +indicadas, pueden ocultarse de nuevo arrastrando el registro de posición hacia +la derecha. + +image::mobile-images/gpsmanagement.jpg["FIGURE: GPS management",align="center"] + +=== Aplicar los datos GPS a las inmersiones del divelog + +Suponiendo que se hayan introducido a mano o descargado desde la nube de +_Subsurface_ todas las inmersiones del divelog, se pueden aplicar las +posiciones GPS a dichas inmersiones. Las posiciones GPS solo pueden aplicarse +a inmersiones que estén en la lista de inmersiones. +Desde el subpanel _GPS_, pulsar _Apply GPS fixes_. La lista de inmersiones +contiene la hora de inicio y fin de cada inmersión. _Subsurface-mobile_ +aplicará la primera posición que se encuentre dentro del periodo de duración +del buceo, o la inmediatamente anterior al inicio si no hubiera ninguna dentro +del periodo. diff --git a/Documentation/mobile-manual_fr.html.git b/Documentation/mobile-manual_fr.html.git new file mode 100644 index 000000000..77551be6d --- /dev/null +++ b/Documentation/mobile-manual_fr.html.git @@ -0,0 +1,797 @@ +<!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"> +/*<+'])'); + // Function that scans the DOM tree for header elements (the DOM2 + // nodeIterator API would be a better technique but not supported by all + // browsers). + var iterate = function (el) { + for (var i = el.firstChild; i != null; i = i.nextSibling) { + if (i.nodeType == 1 /* Node.ELEMENT_NODE */) { + var mo = re.exec(i.tagName); + if (mo && (i.getAttribute("class") || i.getAttribute("className")) != "float") { + result[result.length] = new TocEntry(i, getText(i), mo[1]-1); + } + iterate(i); + } + } + } + iterate(el); + return result; + } + + var toc = document.getElementById("toc"); + if (!toc) { + return; + } + + // Delete existing TOC entries in case we're reloading the TOC. + var tocEntriesToRemove = []; + var i; + for (i = 0; i < toc.childNodes.length; i++) { + var entry = toc.childNodes[i]; + if (entry.nodeName.toLowerCase() == 'div' + && entry.getAttribute("class") + && entry.getAttribute("class").match(/^toclevel/)) + tocEntriesToRemove.push(entry); + } + for (i = 0; i < tocEntriesToRemove.length; i++) { + toc.removeChild(tocEntriesToRemove[i]); + } + + // Rebuild TOC entries. + var entries = tocEntries(document.getElementById("content"), toclevels); + for (var i = 0; i < entries.length; ++i) { + var entry = entries[i]; + if (entry.element.id == "") + entry.element.id = "_toc_" + i; + var a = document.createElement("a"); + a.href = "#" + entry.element.id; + a.appendChild(document.createTextNode(entry.text)); + var div = document.createElement("div"); + div.appendChild(a); + div.className = "toclevel" + entry.toclevel; + toc.appendChild(div); + } + if (entries.length == 0) + toc.parentNode.removeChild(toc); +}, + + +///////////////////////////////////////////////////////////////////// +// Footnotes generator +///////////////////////////////////////////////////////////////////// + +/* Based on footnote generation code from: + * http://www.brandspankingnew.net/archive/2005/07/format_footnote.html + */ + +footnotes: function () { + // Delete existing footnote entries in case we're reloading the footnodes. + var i; + var noteholder = document.getElementById("footnotes"); + if (!noteholder) { + return; + } + var entriesToRemove = []; + for (i = 0; i < noteholder.childNodes.length; i++) { + var entry = noteholder.childNodes[i]; + if (entry.nodeName.toLowerCase() == 'div' && entry.getAttribute("class") == "footnote") + entriesToRemove.push(entry); + } + for (i = 0; i < entriesToRemove.length; i++) { + noteholder.removeChild(entriesToRemove[i]); + } + + // Rebuild footnote entries. + var cont = document.getElementById("content"); + var spans = cont.getElementsByTagName("span"); + var refs = {}; + var n = 0; + for (i=0; i<spans.length; i++) { + if (spans[i].className == "footnote") { + n++; + var note = spans[i].getAttribute("data-note"); + if (!note) { + // Use [\s\S] in place of . so multi-line matches work. + // Because JavaScript has no s (dotall) regex flag. + note = spans[i].innerHTML.match(/\s*\[([\s\S]*)]\s*/)[1]; + spans[i].innerHTML = + "[<a id='_footnoteref_" + n + "' href='#_footnote_" + n + + "' title='View footnote' class='footnote'>" + n + "</a>]"; + spans[i].setAttribute("data-note", note); + } + noteholder.innerHTML += + "<div class='footnote' id='_footnote_" + n + "'>" + + "<a href='#_footnoteref_" + n + "' title='Return to text'>" + + n + "</a>. " + note + "</div>"; + var id =spans[i].getAttribute("id"); + if (id != null) refs["#"+id] = n; + } + } + if (n == 0) + noteholder.parentNode.removeChild(noteholder); + else { + // Process footnoterefs. + for (i=0; i<spans.length; i++) { + if (spans[i].className == "footnoteref") { + var href = spans[i].getElementsByTagName("a")[0].getAttribute("href"); + href = href.match(/#.*/)[0]; // Because IE return full URL. + n = refs[href]; + spans[i].innerHTML = + "[<a href='#_footnote_" + n + + "' title='View footnote' class='footnote'>" + n + "</a>]"; + } + } + } +}, + +install: function(toclevels) { + var timerId; + + function reinstall() { + asciidoc.footnotes(); + if (toclevels) { + asciidoc.toc(toclevels); + } + } + + function reinstallAndRemoveTimer() { + clearInterval(timerId); + reinstall(); + } + + timerId = setInterval(reinstall, 500); + if (document.addEventListener) + document.addEventListener("DOMContentLoaded", reinstallAndRemoveTimer, false); + else + window.onload = reinstallAndRemoveTimer; +} + +} +asciidoc.install(3); +/*]]>*/ +</script> +</head> +<body class="article"> +<div id="header"> +</div> +<div id="content"> +<div class="imageblock" style="text-align:center;"> +<div class="content"> +<img src="mobile-images/banner.jpg" alt="Banner" /> +</div> +</div> +<div class="paragraph"><p><span class="big">Subsurface-mobile pour Android: MANUEL UTILISATEUR</span></p></div> +<div class="paragraph"><p><strong>Manual author</strong>: Willem Ferguson</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="paragraph"><p><span class="blue"><em>Version 1.0, Mars 2016</em></span></p></div> +<div class="paragraph"><p>Welcome as a user of <em>Subsurface</em>, advanced dive logging software with +extensive infrastructure to describe, organize, interpret and print scuba +and free dives. <em>Subsurface</em> offers many advantages over other similar +software solutions, including compatibility with Windows, Mac-OS/X, Linux +(many distributions) and Android (iOS under development). In addition, +<em>Subsurface</em> is open-source software that allows downloading dive +information from most dive computers.</p></div> +<div class="sect1"> +<h2 id="_introducing_subsurface_mobile">1. Introducing Subsurface-mobile</h2> +<div class="sectionbody"> +<div class="paragraph"><p><em>Subsurface-mobile</em> is an extension of <em>Subsurface</em> on laptop and tabletop +computers. It runs on Android smartphone and tablet devices and is a tool +for viewing or sharing dive information at dive sites where a larger +computer is not useful. <em>Subsurface-mobile</em> also allows the gathering of GPS +locations where dives are performed.</p></div> +<div class="paragraph"><p>A version of <em>Subsurface-mobile</em> for iOS is under development but not yet +ready for testing.</p></div> +<div class="paragraph"><p>While <em>Subsurface-mobile</em> allows one to enter and save dive information +using an Android device, users of <em>Subsurface-mobile</em> typically use the +mobile app as an extension of the laptop/desktop version of <em>Subsurface</em>. +This allows the storage of dive logs on the Internet and which can be shared +by the Android version as well as the desktop version. While the desktop +version of <em>Subsurface</em> shows much more detailed information for each dive, +the mobile version allows one to have a more accessible dive log on a dive +trip, useful for proving dive experience to dive shops or to review previous +dives.</p></div> +<div class="paragraph"><p><em>Subsurface-mobile</em> allows one to:</p></div> +<div class="ulist"><ul> +<li> +<p> +Download existing dive log information from the Internet. +</p> +</li> +<li> +<p> +View this information on an Android device. +</p> +</li> +<li> +<p> +Edit many of the dive log data fields, e.g. divemaster, buddy, equipment or + notes about a dive. +</p> +</li> +<li> +<p> +Create and add new dive records to one’s dive log. +</p> +</li> +<li> +<p> +Store the updated dive log on the Internet. +</p> +</li> +<li> +<p> +Record, store and apply GPS positions of dives. +</p> +</li> +<li> +<p> +View the localities of recorded GPS positions and of dives on a map. +</p> +</li> +</ul></div> +<div class="paragraph"><p>These items are discussed in greater detail in the following text. What +<em>Subsurface-mobile</em> does not support (at this time) is downloading dive data +directly from a dive computer. That still has to happen with <em>Subsurface</em> on +a desktop or laptop computer. We are investigating ways to support +downloading from a subset of the supported dive computers on Android +devices, but this is not yet ready for testing.</p></div> +</div> +</div> +<div class="sect1"> +<h2 id="_installing_em_subsurface_mobile_em_on_an_android_device">2. Installing <em>Subsurface-mobile</em> on an Android device</h2> +<div class="sectionbody"> +<div class="paragraph"><p>Find <em>Subsurface-mobile</em> in the <em>Google Play Store</em>. Search for +<em>Subsurface-mobile</em> and install it.</p></div> +</div> +</div> +<div class="sect1"> +<h2 id="_using_em_subsurface_mobile_em_for_the_first_time">3. Using <em>Subsurface-mobile</em> for the first time</h2> +<div class="sectionbody"> +<div class="paragraph"><p>Upon starting <em>Subsurface-mobile</em> for the first time, a Subsurface splash +screen is shown while the program loads. On some devices this may take +several seconds. After loading, the <em>Cloud Credentials screen</em> appears (see +image below).</p></div> +<div class="imageblock" style="text-align:center;"> +<div class="content"> +<img src="mobile-images/landingscreen.jpg" alt="FIGURE: Mobile landing screen" /> +</div> +</div> +<div class="paragraph"><p>Since <em>Subsurface</em> is largely dependent on a dive log saved on the Internet, +provide a user-ID and password for access to the <em>Subsurface Cloud</em>. These +credentials are obtained by opening the desktop version of <em>Subsurface</em> and +by clicking <em>File → Preferences → Network</em>, explained in detail in the +user manual for the <em>Subsurface</em> desktop version. Once the account has +been created and verified using the desktop version one can use <em>Subsurface-mobile</em>.</p></div> +<div class="paragraph"><p>When entering a password, it is possible to check a checkbox that enables +the text of the password to be shown. Checking the check box labelled +"Remember" allows <em>Susburface-mobile</em> to keep the credentials for subsequent +logins (see image above). Having entered the credentials, tap the disk icon +at the bottom of the screen. <em>Subsurface-mobile</em> attempts to download the +existing dive log from the_Subsurface_ cloud server. Appropriate messages +are shown onscreen. Finally a list of dives are shown.</p></div> +</div> +</div> +<div class="sect1"> +<h2 id="_local_copy_of_the_dive_log_and_synchronisation_with_internet">4. Local copy of the dive log and synchronisation with Internet</h2> +<div class="sectionbody"> +<div class="paragraph"><p>Once the dive list has been downloaded from the Internet, +<em>Subsurface-mobile</em> keeps a local copy on the mobile device. This means +that, if there is no Internet connection at a dive site, one can still +access the local copy and view and manipulate dive information. If there is +Internet connectivity, <em>Subsurface-mobile</em> accesses the Internet-based dive +log to verify that the local copy is still the same as the Internet-stored +copy. If not, the local copy and the copy on the server are synchronised.</p></div> +</div> +</div> +<div class="sect1"> +<h2 id="_a_few_remarks_about_the_user_interface">5. A Few Remarks About The User Interface</h2> +<div class="sectionbody"> +<div class="paragraph"><p>At the bottom of many Subsurface-mobile screens is a round button that +provides for several actions and which allows the selection of the main +affirmative action (see image above and image below). On Android devices, +use the Android Back button for "cancel", "discard" or "back" actions. For +example, when editing dive information, tapping the action button saves the +changes, the Android back button can be used to cancel the edit without +saving changes.</p></div> +<div class="imageblock" style="text-align:center;"> +<div class="content"> +<img src="mobile-images/actionbutton.jpg" alt="FIGURE: Action Button" /> +</div> +</div> +<div class="paragraph"><p>Instead of the more traditional "hamburger" menu button in the top left or +right corner of the screen to open menus, <em>Subsurface-mobile</em> uses a +different user interaction philosophy based on the Kirigami framework +developed by the Plasma developers. To open the main menu one has three +options:</p></div> +<div class="ulist"><ul> +<li> +<p> +Tap on the right-arrow symbol in the lower left corner of the screen (easy + to reach for hand held devices) +</p> +</li> +<li> +<p> +Swipe towards the right across the left edge of the screen +</p> +</li> +<li> +<p> +Drag the action button visible on most screens with the main action to the + right +</p> +</li> +</ul></div> +<div class="imageblock" style="text-align:center;"> +<div class="content"> +<img src="mobile-images/menu.jpg" alt="FIGURE: Dive management subpanel" /> +</div> +</div> +<div class="paragraph"><p>The images above indicate some of the important features of the menu +system. On the left is the main menu that is activated as described +above. In the middle is the menu that opens if one taps the <em>GPS</em> option on +the main menu. On the right is the menu that opens if one taps the <em>Manage +Dives</em> option on the main menu.</p></div> +<div class="paragraph"><p>Similarly, the context menu (currently only available on the dive details +screen) can be opened one of these three ways:</p></div> +<div class="ulist"><ul> +<li> +<p> +Tap on the left-arrow symbol in the lower right corner of the screen +</p> +</li> +<li> +<p> +Swipe to the left across the right edge of the screen +</p> +</li> +<li> +<p> +Drag the action button to the left +</p> +</li> +</ul></div> +</div> +</div> +<div class="sect1"> +<h2 id="_viewing_the_dive_list">6. Viewing the Dive List</h2> +<div class="sectionbody"> +<div class="paragraph"><p>Most of the actions of <em>Subsurface-mobile</em> center around the dives on the +dive list. While the dive list is loading from the cloud, a message appears +at the bottom of the screen, indicating that the cloud is being accessed +(see image on left, below). Once the list is loaded one can scroll up and +down. Tapping a dive on the list brings up a display of <em>Details View</em> for +that dive (see image on right below). This includes the dive profile as +well as additional information and notes.</p></div> +<div class="imageblock" style="text-align:center;"> +<div class="content"> +<img src="mobile-images/divelist.jpg" alt="FIGURE: Dive list screen" /> +</div> +</div> +<div class="paragraph"><p>One can view other dives by swiping the <em>Details view</em> to the right (for the +previous dive) or to the left (following dive).</p></div> +</div> +</div> +<div class="sect1"> +<h2 id="_editing_dive_details">7. Editing dive details.</h2> +<div class="sectionbody"> +<div class="paragraph"><p>At the bottom of the dive details screen the <em>Action Button</em> contains a +pencil (image on right, above). Tapping the button brings up a panel with +edit boxes that allows one to change the existing dive information, +e.g. adding text to the dive notes or changing the names or values of some +of the information (see image below). It may be necessary to scroll the +window to access all the information. At the bottom of the edit screen is a +<em>Save</em> action button. Tap this to save the new information. Having saved the +data, the dive list screen is updated and shown. To cancel any edits, tap +the Android Back Button.</p></div> +<div class="imageblock" style="text-align:center;"> +<div class="content"> +<img src="mobile-images/editdive.jpg" alt="FIGURE: Dive edit screen" /> +</div> +</div> +</div> +</div> +<div class="sect1"> +<h2 id="_adding_a_new_dive_to_the_dive_list">8. Adding a new dive to the dive list</h2> +<div class="sectionbody"> +<div class="paragraph"><p>It is also possible to add an additional dive to the existing dive list. On +the main menu tap <em>Manage dives → Add dive manually</em>. This opens a screen +that is identical to the editing screen discussed above. When a dive is +added manually, one cannot directly add a dive profile from a dive +computer. However, if one does not use a dive computer, the duration, depth +and several other bits of information about the new dive can be entered. The +<em>Action button</em> at the bottom of the screen contains a disk symbol. Tap this +to save the new dive. To cancel any edits, tap the Android Back Button. The +left-hand image below shows a screenshot of a dive being created and the +right-hand image shows the same dive in <em>Details View</em>.</p></div> +<div class="imageblock" style="text-align:center;"> +<div class="content"> +<img src="mobile-images/createdive.jpg" alt="FIGURE: Dive edit screen" /> +</div> +</div> +</div> +</div> +<div class="sect1"> +<h2 id="_deleting_a_dive">9. Deleting a dive</h2> +<div class="sectionbody"> +<div class="paragraph"><p>The <em>details view</em> of a dive has a context menu on the right-hand side that +can be activated as described above (e.g. by tapping the arrow icon at the +bottom right of the screen or by dragging the <em>Action Button</em> to the left). +The context menu has a single item: "Delete dive". If this option is tapped, +the dive shown in the <em>Details View</em> is deleted. One has a brief opportunity +to undo the delete by tapping the <em>undo</em> message that appears at the bottom +of the screen. If the <em>undo</em> message is not tapped, the dive is deleted.</p></div> +</div> +</div> +<div class="sect1"> +<h2 id="_dive_log_management">10. Dive log management</h2> +<div class="sectionbody"> +<div class="paragraph"><p>A central part of <em>Subsurface-mobile</em> is the ability to store the dive +log using the <em>Subsurface</em> cloud storage. +This provides security against loss or damage to the dive information caintained in a local copy of +the dive log and allows the desktop version of <em>Subsurface</em> to +access changes made using the mobile device. This ability is accessed +throug the main menu (by dragging the Action Button to the right, or +alternatively tap the right angle button at the bottom left of the screen). + Tap the option <em>Manage dives</em>, enabling a number of options:</p></div> +<div class="sect2"> +<h3 id="_add_new_dive_manually">10.1. Add new dive manually</h3> +<div class="paragraph"><p>This is described above under the section dealing with the dive list.</p></div> +</div> +<div class="sect2"> +<h3 id="_upload_dive_log_to_the_em_subsurface_em_cloud_storage">10.2. Upload dive log to the <em>Subsurface</em> cloud storage</h3> +<div class="paragraph"><p>One can upload the dives contained on the mobile device to the <em>Subsurface</em> +cloud storage by tapping the option <em>Upload to cloud</em>. This synchronizes +the local changes to the dive log with the cloud storage.</p></div> +</div> +<div class="sect2"> +<h3 id="_download_dive_log_from_the_cloud_storage">10.3. Download dive log from the cloud storage</h3> +<div class="paragraph"><p>In the dive management subpanel, tap the option <em>Refresh</em>, causing the local +divelog to be refreshed from the cloud so that the cloud and local versions +are synchronised.</p></div> +</div> +<div class="sect2"> +<h3 id="_changing_the_login_credentials_on_the_em_subsurface_em_cloud">10.4. Changing the login credentials on the <em>Subsurface</em> cloud</h3> +<div class="paragraph"><p>It may be necessary to change one’s login credentials, for instance if one’s +email address (initially used as a credential) has changed. To change the +credentials, open the main menu and tap <em>Cloud credentials</em>. This opens the +setup screen for specifying new credentials.</p></div> +</div> +</div> +</div> +<div class="sect1"> +<h2 id="_recording_dive_locations_using_gps">11. Recording dive locations using GPS.</h2> +<div class="sectionbody"> +<div class="paragraph"><p>The fact that most smartphones have GPS facilities allows one to record the +locations of dives. One can take the smartphone on the dive boat during a +dive and locations will be automatically recorded at regular intervals. +These locations can then be applied to dives in the dive list. Here is how +it’s done:</p></div> +<div class="sect2"> +<h3 id="_setting_up_the_gps">11.1. Setting up the GPS</h3> +<div class="paragraph"><p>Open the main menu and tap <em>GPS → Preferences</em>. Now specify the way in +which GPS data need to be automatically collected (image on right, +below). One can specify that data are collected at regular intervals, +e.g. every 10 minutes, or at regular distances, e.g. after the boat has +moved more than 200m, or a combination of both of the above +approaches. Provide the appropriate information and tap the <em>Save</em> action +button. The program is now ready to collect GPS positions.</p></div> +<div class="imageblock" style="text-align:center;"> +<div class="content"> +<img src="mobile-images/gpssetup.jpg" alt="FIGURE: GPS setup screen" /> +</div> +</div> +</div> +<div class="sect2"> +<h3 id="_collecting_gps_positions">11.2. Collecting GPS positions</h3> +<div class="paragraph"><p>Ensure that the GPS on the Android device has been activated. At the bottom +of the GPS submenu is a check box <em>Run location service</em> (image on left, +above). Check this box and <em>Subsurface-mobile</em> starts to collect GPS +locations automatically, following the preferences specified as described +above. After the dive one can deactivate the collection of GPS data by +de-activating the same check box at the bottom of the main menu.</p></div> +</div> +<div class="sect2"> +<h3 id="_storing_the_gps_data_on_the_em_subsurface_em_cloud">11.3. Storing the GPS data on the <em>Subsurface</em> cloud</h3> +<div class="paragraph"><p>Activate the main menu and select the <em>GPS</em> option that brings up the +submenu of GPS-related actions (image on left, above). Tap <em>Upload GPS data</em> +that saves the GPS data on the <em>Subsurface</em> cloud server. These GPS data are +saved <strong>separately</strong> from the other dive log data. All collected GPS data are +kept on the Android device, independent of whether they have been uploaded +or not.</p></div> +</div> +<div class="sect2"> +<h3 id="_downloading_gps_data_from_the_em_subsurface_em_cloud">11.4. Downloading GPS data from the <em>Subsurface</em> cloud</h3> +<div class="paragraph"><p>Download the GPS data that have been saved on the cloud by selecting +<em>Download GPS Data</em> from the GPS subpanel.</p></div> +</div> +<div class="sect2"> +<h3 id="_viewing_gps_data">11.5. Viewing GPS data</h3> +<div class="paragraph"><p>From the GPS submenu (image on left, above) select <em>Show GPS fixes</em>. This +brings up a list of GPS positions obtained using the location service (image +on left, below). Two actions are possible for each of the locations, enabled +if one taps the handle (the three horisontal stripes on the right, see image +on left, below) and then drags the specific item to the left (image on +right, below). This exposes two options. Tapping the dustbin deletes this +particular GPS location. Tapping the teardrop-shaped icon (actually a Google +Maps pin) opens up Google Maps with a pin indicating the exact map position +of the GPS record being viewed. The two above options can be hidden by +drawing the GPS record to the right, again using the handle.</p></div> +<div class="imageblock" style="text-align:center;"> +<div class="content"> +<img src="mobile-images/gpsmanagement.jpg" alt="FIGURE: GPS management" /> +</div> +</div> +</div> +<div class="sect2"> +<h3 id="_applying_gps_data_to_dives_in_the_dive_log">11.6. Applying GPS data to dives in the dive log</h3> +<div class="paragraph"><p>Assuming that all the dives have been entered into the dive log or have been +downloaded from the <em>Subsurface</em> cloud, one can apply the GPS positions to +these dives. GPS positions can therefore only be applied to dives in the +dive list. From the GPS subpanel, tap <em>Apply GPS fixes</em>. The dive list +contains the start and end times of each dive. Now, <em>Subsurface-mobile</em> +applies the first GPS position that falls within the dive period of each +dive. This results in a GPS position for each dive that is saved as part of +the dive list.</p></div> +</div> +</div> +</div> +</div> +<div id="footnotes"><hr /></div> +<div id="footer"> +<div id="footer-text"> +Last updated 2016-03-12 13:57:29 CET +</div> +</div> +</body> +</html> diff --git a/Documentation/mobile-manual_fr.txt b/Documentation/mobile-manual_fr.txt new file mode 100644 index 000000000..c8b75b02a --- /dev/null +++ b/Documentation/mobile-manual_fr.txt @@ -0,0 +1,299 @@ +:icons: +:toc: +:toc-placement: manual +:numbered: + +image::mobile-images/banner.jpg["Banner", align="center"] + +[big]#Subsurface-mobile pour Android: MANUEL UTILISATEUR# + +*Manual author*: Willem Ferguson + +toc::[] + +[blue]#_Version 1.0, Mars 2016_# + +Welcome as a user of _Subsurface_, advanced dive logging software with +extensive infrastructure to describe, organize, interpret and print scuba +and free dives. _Subsurface_ offers many advantages over other similar +software solutions, including compatibility with Windows, Mac-OS/X, Linux +(many distributions) and Android (iOS under development). In addition, +_Subsurface_ is open-source software that allows downloading dive +information from most dive computers. + +Introducing Subsurface-mobile +----------------------------- + +_Subsurface-mobile_ is an extension of _Subsurface_ on laptop and tabletop +computers. It runs on Android smartphone and tablet devices and is a tool +for viewing or sharing dive information at dive sites where a larger +computer is not useful. _Subsurface-mobile_ also allows the gathering of GPS +locations where dives are performed. + +A version of _Subsurface-mobile_ for iOS is under development but not yet +ready for testing. + +While _Subsurface-mobile_ allows one to enter and save dive information +using an Android device, users of _Subsurface-mobile_ typically use the +mobile app as an extension of the laptop/desktop version of _Subsurface_. +This allows the storage of dive logs on the Internet and which can be shared +by the Android version as well as the desktop version. While the desktop +version of _Subsurface_ shows much more detailed information for each dive, +the mobile version allows one to have a more accessible dive log on a dive +trip, useful for proving dive experience to dive shops or to review previous +dives. + +_Subsurface-mobile_ allows one to: + +- Download existing dive log information from the Internet. +- View this information on an Android device. +- Edit many of the dive log data fields, e.g. divemaster, buddy, equipment or + notes about a dive. +- Create and add new dive records to one's dive log. +- Store the updated dive log on the Internet. +- Record, store and apply GPS positions of dives. +- View the localities of recorded GPS positions and of dives on a map. + +These items are discussed in greater detail in the following text. What +_Subsurface-mobile_ does not support (at this time) is downloading dive data +directly from a dive computer. That still has to happen with _Subsurface_ on +a desktop or laptop computer. We are investigating ways to support +downloading from a subset of the supported dive computers on Android +devices, but this is not yet ready for testing. + +== Installing _Subsurface-mobile_ on an Android device + +Find _Subsurface-mobile_ in the _Google Play Store_. Search for +_Subsurface-mobile_ and install it. + +== Using _Subsurface-mobile_ for the first time + +Upon starting _Subsurface-mobile_ for the first time, a Subsurface splash +screen is shown while the program loads. On some devices this may take +several seconds. After loading, the _Cloud Credentials screen_ appears (see +image below). + +image::mobile-images/landingscreen.jpg["FIGURE: Mobile landing screen", align="center"] + +Since _Subsurface_ is largely dependent on a dive log saved on the Internet, +provide a user-ID and password for access to the _Subsurface Cloud_. These +credentials are obtained by opening the desktop version of _Subsurface_ and +by clicking _File -> Preferences -> Network_, explained in detail in the +user manual for the _Subsurface_ desktop version. Once the account has +been created and verified using the desktop version one can use _Subsurface-mobile_. + +When entering a password, it is possible to check a checkbox that enables +the text of the password to be shown. Checking the check box labelled +"Remember" allows _Susburface-mobile_ to keep the credentials for subsequent +logins (see image above). Having entered the credentials, tap the disk icon +at the bottom of the screen. _Subsurface-mobile_ attempts to download the +existing dive log from the_Subsurface_ cloud server. Appropriate messages +are shown onscreen. Finally a list of dives are shown. + + +== Local copy of the dive log and synchronisation with Internet + +Once the dive list has been downloaded from the Internet, +_Subsurface-mobile_ keeps a local copy on the mobile device. This means +that, if there is no Internet connection at a dive site, one can still +access the local copy and view and manipulate dive information. If there is +Internet connectivity, _Subsurface-mobile_ accesses the Internet-based dive +log to verify that the local copy is still the same as the Internet-stored +copy. If not, the local copy and the copy on the server are synchronised. + +== A Few Remarks About The User Interface + +At the bottom of many Subsurface-mobile screens is a round button that +provides for several actions and which allows the selection of the main +affirmative action (see image above and image below). On Android devices, +use the Android Back button for "cancel", "discard" or "back" actions. For +example, when editing dive information, tapping the action button saves the +changes, the Android back button can be used to cancel the edit without +saving changes. + +image::mobile-images/actionbutton.jpg["FIGURE: Action Button", align="center"] + +Instead of the more traditional "hamburger" menu button in the top left or +right corner of the screen to open menus, _Subsurface-mobile_ uses a +different user interaction philosophy based on the Kirigami framework +developed by the Plasma developers. To open the main menu one has three +options: + +- Tap on the right-arrow symbol in the lower left corner of the screen (easy + to reach for hand held devices) +- Swipe towards the right across the left edge of the screen +- Drag the action button visible on most screens with the main action to the + right + +image::mobile-images/menu.jpg["FIGURE: Dive management subpanel", align="center"] + +The images above indicate some of the important features of the menu +system. On the left is the main menu that is activated as described +above. In the middle is the menu that opens if one taps the _GPS_ option on +the main menu. On the right is the menu that opens if one taps the _Manage +Dives_ option on the main menu. + +Similarly, the context menu (currently only available on the dive details +screen) can be opened one of these three ways: + +- Tap on the left-arrow symbol in the lower right corner of the screen +- Swipe to the left across the right edge of the screen +- Drag the action button to the left + +== Viewing the Dive List + +Most of the actions of _Subsurface-mobile_ center around the dives on the +dive list. While the dive list is loading from the cloud, a message appears +at the bottom of the screen, indicating that the cloud is being accessed +(see image on left, below). Once the list is loaded one can scroll up and +down. Tapping a dive on the list brings up a display of _Details View_ for +that dive (see image on right below). This includes the dive profile as +well as additional information and notes. + +image::mobile-images/divelist.jpg["FIGURE: Dive list screen", align="center"] + +One can view other dives by swiping the _Details view_ to the right (for the +previous dive) or to the left (following dive). + +== Editing dive details. + +At the bottom of the dive details screen the _Action Button_ contains a +pencil (image on right, above). Tapping the button brings up a panel with +edit boxes that allows one to change the existing dive information, +e.g. adding text to the dive notes or changing the names or values of some +of the information (see image below). It may be necessary to scroll the +window to access all the information. At the bottom of the edit screen is a +_Save_ action button. Tap this to save the new information. Having saved the +data, the dive list screen is updated and shown. To cancel any edits, tap +the Android Back Button. + +image::mobile-images/editdive.jpg["FIGURE: Dive edit screen", align="center"] + +== Adding a new dive to the dive list + +It is also possible to add an additional dive to the existing dive list. On +the main menu tap _Manage dives -> Add dive manually_. This opens a screen +that is identical to the editing screen discussed above. When a dive is +added manually, one cannot directly add a dive profile from a dive +computer. However, if one does not use a dive computer, the duration, depth +and several other bits of information about the new dive can be entered. The +_Action button_ at the bottom of the screen contains a disk symbol. Tap this +to save the new dive. To cancel any edits, tap the Android Back Button. The +left-hand image below shows a screenshot of a dive being created and the +right-hand image shows the same dive in _Details View_. + +image::mobile-images/createdive.jpg["FIGURE: Dive edit screen", align="center"] + +== Deleting a dive + +The _details view_ of a dive has a context menu on the right-hand side that +can be activated as described above (e.g. by tapping the arrow icon at the +bottom right of the screen or by dragging the _Action Button_ to the left). +The context menu has a single item: "Delete dive". If this option is tapped, +the dive shown in the _Details View_ is deleted. One has a brief opportunity +to undo the delete by tapping the _undo_ message that appears at the bottom +of the screen. If the _undo_ message is not tapped, the dive is deleted. + +== Dive log management + +A central part of _Subsurface-mobile_ is the ability to store the dive +log using the _Subsurface_ cloud storage. +This provides security against loss or damage to the dive information caintained in a local copy of +the dive log and allows the desktop version of _Subsurface_ to +access changes made using the mobile device. This ability is accessed +throug the main menu (by dragging the Action Button to the right, or +alternatively tap the right angle button at the bottom left of the screen). + Tap the option _Manage dives_, enabling a number of options: + +=== Add new dive manually + +This is described above under the section dealing with the dive list. + +=== Upload dive log to the _Subsurface_ cloud storage + +One can upload the dives contained on the mobile device to the _Subsurface_ +cloud storage by tapping the option _Upload to cloud_. This synchronizes +the local changes to the dive log with the cloud storage. + +=== Download dive log from the cloud storage + +In the dive management subpanel, tap the option _Refresh_, causing the local +divelog to be refreshed from the cloud so that the cloud and local versions +are synchronised. + +=== Changing the login credentials on the _Subsurface_ cloud + +It may be necessary to change one's login credentials, for instance if one's +email address (initially used as a credential) has changed. To change the +credentials, open the main menu and tap _Cloud credentials_. This opens the +setup screen for specifying new credentials. + + +== Recording dive locations using GPS. + +The fact that most smartphones have GPS facilities allows one to record the +locations of dives. One can take the smartphone on the dive boat during a +dive and locations will be automatically recorded at regular intervals. +These locations can then be applied to dives in the dive list. Here is how +it's done: + +=== Setting up the GPS + +Open the main menu and tap _GPS -> Preferences_. Now specify the way in +which GPS data need to be automatically collected (image on right, +below). One can specify that data are collected at regular intervals, +e.g. every 10 minutes, or at regular distances, e.g. after the boat has +moved more than 200m, or a combination of both of the above +approaches. Provide the appropriate information and tap the _Save_ action +button. The program is now ready to collect GPS positions. + +image::mobile-images/gpssetup.jpg["FIGURE: GPS setup screen", align="center"] + +=== Collecting GPS positions + +Ensure that the GPS on the Android device has been activated. At the bottom +of the GPS submenu is a check box _Run location service_ (image on left, +above). Check this box and _Subsurface-mobile_ starts to collect GPS +locations automatically, following the preferences specified as described +above. After the dive one can deactivate the collection of GPS data by +de-activating the same check box at the bottom of the main menu. + +=== Storing the GPS data on the _Subsurface_ cloud + +Activate the main menu and select the _GPS_ option that brings up the +submenu of GPS-related actions (image on left, above). Tap _Upload GPS data_ +that saves the GPS data on the _Subsurface_ cloud server. These GPS data are +saved *separately* from the other dive log data. All collected GPS data are +kept on the Android device, independent of whether they have been uploaded +or not. + +=== Downloading GPS data from the _Subsurface_ cloud + +Download the GPS data that have been saved on the cloud by selecting +_Download GPS Data_ from the GPS subpanel. + +=== Viewing GPS data + +From the GPS submenu (image on left, above) select _Show GPS fixes_. This +brings up a list of GPS positions obtained using the location service (image +on left, below). Two actions are possible for each of the locations, enabled +if one taps the handle (the three horisontal stripes on the right, see image +on left, below) and then drags the specific item to the left (image on +right, below). This exposes two options. Tapping the dustbin deletes this +particular GPS location. Tapping the teardrop-shaped icon (actually a Google +Maps pin) opens up Google Maps with a pin indicating the exact map position +of the GPS record being viewed. The two above options can be hidden by +drawing the GPS record to the right, again using the handle. + +image::mobile-images/gpsmanagement.jpg["FIGURE: GPS management", align="center"] + +=== Applying GPS data to dives in the dive log + +Assuming that all the dives have been entered into the dive log or have been +downloaded from the _Subsurface_ cloud, one can apply the GPS positions to +these dives. GPS positions can therefore only be applied to dives in the +dive list. From the GPS subpanel, tap _Apply GPS fixes_. The dive list +contains the start and end times of each dive. Now, _Subsurface-mobile_ +applies the first GPS position that falls within the dive period of each +dive. This results in a GPS position for each dive that is saved as part of +the dive list. diff --git a/Documentation/user-manual.html.git b/Documentation/user-manual.html.git index ba678a6ef..dc2e19dc4 100644 --- a/Documentation/user-manual.html.git +++ b/Documentation/user-manual.html.git @@ -1,6681 +1,6681 @@ -<!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.9" />
-<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; }
-
-
-@media screen {
- body {
- max-width: 50em; /* approximately 80 characters wide */
- margin-left: 16em;
- }
-
- #toc {
- position: fixed;
- top: 0;
- left: 0;
- bottom: 0;
- width: 13em;
- padding: 0.5em;
- padding-bottom: 1.5em;
- margin: 0;
- overflow: auto;
- border-right: 3px solid #f8f8f8;
- background-color: white;
- }
-
- #toc .toclevel1 {
- margin-top: 0.5em;
- }
-
- #toc .toclevel2 {
- margin-top: 0.25em;
- display: list-item;
- color: #aaaaaa;
- }
-
- #toctitle {
- margin-top: 0.5em;
- }
-}
-</style>
-<script type="text/javascript">
-/*<+'])');
- // 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">USER MANUAL</span></p></div>
-<div class="paragraph"><p><strong>Manual authors</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.5, October 2015</em></span></p></div>
-<div class="paragraph"><p>Welcome as a user of <em>Subsurface</em>, an advanced dive logging program with
-extensive infrastructure to describe, organize, interpret and print scuba
-and free dives. <em>Subsurface</em> offers many advantages over other similar
-software solutions:</p></div>
-<div class="ulist"><ul>
-<li>
-<p>
-Do you need a flexible way of logging dives using recreational equipment,
- even without 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 along with a dive computer? <em>Subsurface</em> offers a standard
- interface for downloading dive logs from all of these different pieces of
- equipment, storing and analyzing 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, letting you access your dive log on each
- operating system using a single application.
-</p>
-</li>
-<li>
-<p>
-Do you use Linux or Mac, but your dive computer has only Windows- based software
- for downloading dive information (e.g. Mares)? <em>Subsurface</em> provides a way of
- downloading and analyzing 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, dives you’ve already logged?
-</p>
-</li>
-<li>
-<p>
-Do you need a way of storing or backing up your dive log on the Internet, letting
- you view your dive log from anywhere using an Internet browser?
-<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>
-</li>
-</ul></div>
-<div class="paragraph"><p>This manual explains how to use 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="_using_this_manual">1. Using this manual</h2>
-<div class="sectionbody">
-<div class="paragraph"><p>When opened from within <em>Subsurface</em>, this manual does not have external controls for
-paging or selecting previous pages. However, two facilities are provided:</p></div>
-<div class="ulist"><ul>
-<li>
-<p>
-The <em>SEARCH</em> function is activated by pressing control-F or command-F on
-the keyboard. A text box appears at the bottom right-hand of the window (see image below).
-For instance, typing the word "<em>weights</em>" into the search text
-box, searches throughout the user manual. To the right of the
-search text box are two arrows pointing up and down. These find
-the previous and the next occurrence of the search term.
-<span class="image">
-<img src=":images/usermanualfunctions.jpg" alt="User manual functions" />
-</span>
-</p>
-</li>
-<li>
-<p>
-<em>PREVIOUS/NEXT LINK</em>. Move between links (underlined words that
-jump to specific sections in the user manual) by right-clicking on the text of the manual.
-This brings up a context menu to previous links selected.
-(see image above). For instance if a link has been selected, then the option
-to <em>Go Back</em> shows the text at the last link selected
-(similar to the Previous Page button in a browser). Conversely the <em>Go Forward</em> option
-jumps to the
-text seen before selecting the <em>Go Back</em> option. The <em>Reload</em>
-option reloads the complete user manual into the window.
-</p>
-</li>
-</ul></div>
-</div>
-</div>
-<div class="sect1">
-<h2 id="S_UserSurvey">2. The user survey</h2>
-<div class="sectionbody">
-<div class="paragraph"><p>In order to develop <em>Subsurface</em> to serve its users in the best possible way,
-it’s important to have user information. Upon launching <em>Subsurface</em>
-and using the 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. All data the user sends is useful, and will only be
-used to steer future development and to customize the software to fit the needs of
-the <em>Subsurface</em> users. If you complete the survey, or click the option not to
-be asked again, that should be the last communication of this type you receive.
-However, if your diving and/or subsurface habits change and you wish to fill in
-another survey, just launch <em>Subsurface</em> with the <em>--survey</em> option on the command line.</p></div>
-</div>
-</div>
-<div class="sect1">
-<h2 id="S_StartUsing">3. 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 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="olist arabic"><ol class="arabic">
-<li>
-<p>
-The <strong>Dive List</strong> on the bottom left, showing 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 <strong>Dive List</strong> is an important tool for manipulating a dive log.
-</p>
-</li>
-<li>
-<p>
-The <strong>Dive Map</strong> on the bottom right, showing the user’s dive sites on a world map
-and centered on the site of the last dive selected in the <strong>Dive List</strong>.
-</p>
-</li>
-<li>
-<p>
-The <strong>Info</strong> on 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>
-</li>
-<li>
-<p>
-The <strong>Dive Profile</strong> on the top right, showing a graphical dive profile of the
-selected dive in the <strong>Dive List</strong>.
-</p>
-</li>
-</ol></div>
-<div class="paragraph"><p>The dividers between panels can be dragged 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 the last time the program was used.</p></div>
-<div class="paragraph"><p>If a single 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. If
-several dives are selected, the last highlighted dive is the <em>selected
-dive</em>, but summary data of all <em>highlighted dives</em> is shown in the <strong>Stats</strong> tab
-of the <strong>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_f22.jpg" alt="The Main Window" />
-</div>
-</div>
-<div class="paragraph"><p>The user decides which of the four panels are displayed by selecting the
-<strong>View</strong> option on the main menu. This feature has 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 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, centered on the last selected dive.</p></div>
-<div class="paragraph"><p>Like other functions that can be accessed via the Main Menu, these options
-can also 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’s chosen language may cause <em>Subsurface</em> to use different
-shortcut keys, they are not listed in this user manual.</p></div>
-<div class="paragraph"><p>When the program is started for the first time, it shows no
-information at all, because it does not have any dive information available. In the
-following sections, the procedures to create a new logbook will be explained.</p></div>
-</div>
-</div>
-<div class="sect1">
-<h2 id="S_NewLogbook">4. Creating a new logbook</h2>
-<div class="sectionbody">
-<div class="paragraph"><p>Select <em>File → New Logbook</em> from the main menu. All existing dive data are
-cleared so 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">5. Storing dive information in the logbook</h2>
-<div class="sectionbody">
-<div class="paragraph"><p>Now that a new logbook is created, it is simple to add dive data it.
-<em>Subsurface</em> allows several ways of adding dive data to a logbook.
-1) 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 didn’t
- 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="ulist"><ul>
-<li>
-<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
- to <a href="#S_ImportingCSVDives">Importing dives in CSV format</a>.
-2) If a dive is recorded using a dive computer, the depth profile
-and a large amount of additional information can be accessed.
-These dives can be imported from:
-</p>
-</li>
-<li>
-<p>
-The dive computer itself. See: <a href="#S_ImportDiveComputer">Importing new dive information from a Dive Computer</a> or
-</p>
-</li>
-<li>
-<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>
-</li>
-<li>
-<p>
-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>
-</li>
-</ul></div>
-<div class="sect2">
-<h3 id="S_EnterData">5.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 the dive master or dive guide, and
-some remarks about the dive. <em>Subsurface</em> can store much more
-information for each dive. To add a dive to a dive log, select <em>Log
-→ Add Dive</em> from the Main Menu. The program then shows three panels
-on which to enter
-information for a dive: two tabs in the <strong>Info</strong> panel (<strong>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_f22.jpg" alt="FIGURE: Add dive" />
-</div>
-</div>
-<div class="paragraph"><p>When you edit a field in 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 <strong>Notes</strong> panel (see the image below). This message is
-displayed in all the panels under 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_f22.jpg" alt="Blue edit bar" />
-</div>
-</div>
-<div class="paragraph"><p>The <em>Apply changes</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>Apply changes</em> button, a local copy of the information
-for this specific dive is saved in memory. The <em>Apply changes</em> button should ONLY be selected after all parts
-of a dive have been entered. When you close 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="S_CreateProfile">5.1.1. 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 shown 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 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 shown by two right-angled red lines as seen below.
-The time and depth
-represented by the cursor 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 you need to drag the appropriate waypoints
-downward to 20 m. To add a waypoint, double-click on
-any line segment. To move an additional waypoint, drag it.
-To remove a waypoint, right-click on it and choose "Remove this point" from the
-context menu. Drag the waypoints to represent an
-accurate
-time duration for the dive. Below is a dive profile for 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 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 above. The gas mixtures of segments of the dive profile can
-be changed 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 (see image below).</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>With the profile now defined, more details must be added to have
-a fuller record of the dive. To do this,
-the <strong>Notes</strong> and the <strong>Equipment</strong> tabs on the top left hand of the
-<em>Subsurface</em> window should be used. Click on
-<a href="#S_Notes_dc"><strong>this link</strong></a> for instructions on how to use these tabs.</p></div>
-</div>
-</div>
-<div class="sect2">
-<h3 id="S_ImportDiveComputer">5.2. Importing new dive information from a Dive Computer</h3>
-<div class="sect3">
-<h4 id="_connecting_and_importing_data_from_a_dive_computer">5.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,
-using dive details 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
-PC-Communication mode. <strong>This could drain the dive computer’s battery</strong>. We
-recommend the user checks to be sure 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.</td>
-</tr></table>
-</div>
-<div class="paragraph"><p>To import dive information from a dive computer to a computer with
-<em>Subsurface</em>,
-the two pieces of equipment must 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. To set up
-this communication, users need 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 achieve 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’s PC using 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.
- (Refer to the manual of the specific dive computer)
-</p>
-</li>
-<li>
-<p>
-In <em>Subsurface</em>, from the Main Menu, select <em>Import → Import
- From Dive Computer</em>.
- Dialogue <strong>A</strong> in the figure below appears:
-</p>
-</li>
-</ol></div>
-<div class="imageblock" style="text-align:center;">
-<div class="content">
-<img src="images/DC_import_f20.jpg" alt="FIGURE: Download dialogue 1" />
-</div>
-</div>
-<div class="paragraph"><p>Dive computers tend to keep a certain number of dives in memory, even
-though these dives have already been imported to <em>Subsurface</em>. For that reason, if
-the dive computer allows this,
-<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).</p></div>
-<div class="ulist"><ul>
-<li>
-<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>
-</li>
-<li>
-<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
- specific 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>
-</li>
-<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> has been accidentally deleted or if there
- are older dives that still need to be downloaded from the dive computer, this
- box needs to be checked. 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 dive in the <em>Subsurface</em> divelog will be overwritten
- by the dive record from the computer.
-</p>
-</li>
-<li>
-<p>
-The checkbox marked <em>Download into new trip</em> ensures that, after upload, the downloaded dives
- are grouped together as a new trip(s) in the <strong>Dive List</strong>.
-</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 there are problems with downloads(see below).
-</p>
-</li>
-<li>
-<p>
-Then select the <em>Download</em> button.
- With communication established, you 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. Be patient. The <em>Download</em> dialogue
- shows a
- progress bar at the bottom of the dialogue. Remember for some dive computers
- progress information could be inaccurate since the program doesn’t know how much
- downloadable data there is until the download is complete. After successful download, Dialogue <strong>B</strong>
- in the figure above appears.
- After the dives have been downloaded, they appear in a tabular format on the right-hand
- side of the dialogue (see image <strong>B</strong>, above). Each dive comprises a row in the table, with the date, duration
- and depth shown. Next to each dive is a checkbox: check all the dives that need to
- be transferred to the <strong>Dive List</strong>. In the case of the image above, the last six dives are
- checked and will be transferred to the <strong>Dive List</strong>. Then
- click the <em>OK</em> button at the bottom of the dialogue. 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.
-</p>
-</li>
-</ul></div>
-<div class="paragraph"><p>Then click the OK button.
-The checked dives are transferred to the <strong>Dive List</strong>.</p></div>
-<div class="ulist"><ul>
-<li>
-<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>
-</li>
-</ul></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="ulist"><ul>
-<li>
-<p>
-Is the dive computer still in PC-communication or
- Upload mode?
-</p>
-</li>
-<li>
-<p>
-Is the dive computer’s battery fully charged? If not then charge or replace it.
-</p>
-</li>
-<li>
-<p>
-Is the connecting cable faulty? Does the cable work 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>
-</li>
-<li>
-<p>
-Consult
- <a href="#_appendix_a_operating_system_specific_information_for_importing_dive_information_from_a_dive_computer">Appendix A</a>
- to be sure the correct Mount Point
- was specified (see above).
-</p>
-</li>
-<li>
-<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>
-</li>
-</ul></div>
-<div class="paragraph"><p>If the <em>Subsurface</em> computer does not recognize the USB adaptor by
-showing an appropriate device name next to the Mount Point, then there is a
-possibility the cable or USB adaptor is faulty. A faulty cable is the most
-common cause of communication failure between a dive computer and <em>Subsurface</em>
-computer. It’s also possible the <em>Subsurface</em> computer cannot interpret
-the data. Perform a download for diagnostic purposes with the following
-two 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 where the information will be saved. 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 analyzed. 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_Bluetooth">5.2.2. Connecting <em>Subsurface</em> to a Bluetooth-enabled dive computer</h4>
-<div class="paragraph"><p>Bluetooth is becoming a more common way of communication between dive computers
-and <em>Subsurface</em>, for or instance, the Shearwater Petrel
-Mk2 and the OSTC Mk3. <em>Subsurface</em> provides a largely operating system independent
-Bluetooth interface. Setting up <em>Subsurface</em> for Bluetooth communication requires
-four steps:</p></div>
-<div class="ulist"><ul>
-<li>
-<p>
-Be sure Bluetooth is activated on the host computer running <em>Subsurface</em>.
-</p>
-</li>
-<li>
-<p>
-Be sure <em>Subsurface</em> sees the Bluetooth adapter on the host computer.
-</p>
-</li>
-<li>
-<p>
-Be sure the Bluetooth-enabled dive computer is Bluetooth-discoverable and in PC upload mode.
-</p>
-</li>
-<li>
-<p>
-Be sure <em>Subsurface</em> is paired with the Bluetooth-enabled dive computer.
-</p>
-</li>
-</ul></div>
-<div class="paragraph"><p>Select the Download dialogue by selecting
-<em>Import → Import from dive computer</em> from the <strong>Main Menu</strong>. If you check the
-box labelled <em>"Choose Bluetooth download mode"</em>, the dialogue below appears.
-===== On Linux or MacOS:</p></div>
-<div class="imageblock" style="text-align:center;">
-<div class="content">
-<img src="images/DC_import_Bluetooth.jpg" alt="FIGURE: Download Bluetooth" />
-</div>
-</div>
-<div class="paragraph"><p>On the <em>Linux</em> or <em>MacOS</em> platforms the name
-of the <em>Subsurface</em> computer and its Bluetooth address are shown on the right hand side,
-On the left hand side, if the
-computer has connected more than one local Bluetooth devices the user can use
-the list box to indicate which one needs to connect to <em>Subsurface</em>.
-The power state (on/off) of the Bluetooth adapter is shown below
-the address and can be changed by checking the <em>Turn on/off</em> box.
-If the Bluetooth address is not shown, then <em>Subsurface</em> does not see the local
-Bluetooth device. Be sure the Bluetooth driver is installed correctly on the
-<em>Subsurface</em> computer and check if it can be used by other Bluetooth utilities like
-<em>bluetoothctl</em> or <em>bluemoon</em>. This finishes the first two steps above.
-Be sure the Bluetooth-enabled dive computer is in PC-upload mode and it
-is discoverable by other Bluetooth devices. Consult the manual of the dive
-computer for more information. Now the third item in the list above has been finished.
-Select the <em>Scan</em> button towards the bottom left of the dialogue above. After
-searching, the dive computer should be listed
-(perhaps as one of a number of Bluetooth devices) in the main list box on the
-lefthand side of the dialogue (see image above). If this does not work, select
-the <em>Clear</em> button, then scan again for Bluetooth devices using the <em>Scan</em>
-button. After taking these actions <em>Subsurface</em> should see the dive computer.
-The label of the discovered dive computer contains the name of the device, its
-address and its pairing status. If the device is not paired and has a red
-background color, a context menu can be opened by selecting the item with a
-right-click.
-Select the the <em>Pair</em> option and wait for the task to complete. If this dive computer
-is being paired to Subsurface for the first time, it’s possible Subsurface will
-request a Pass Code or PIN number. The most commonly-used Pass Code is 0000,
-and this works for the Shearwater Petrel. If necessary, consult the user manual of the
-dive computer being used.</p></div>
-<div class="sidebarblock">
-<div class="content">
-<div class="admonitionblock">
-<table><tr>
-<td class="icon">
-<img src="images/icons/important.png" alt="Important" />
-</td>
-<td class="content">Currently <em>Subsurface</em> does not support Bluetooth pairing with dive
-computers that require a custom PIN code. In order to pair the devices, use other
-OS utilities as suggested below.</td>
-</tr></table>
-</div>
-<div class="paragraph"><p>One way to achieve this is to use <code>bluetoothctl</code>:</p></div>
-<div class="literalblock">
-<div class="content">
-<pre><code>$ bluetoothctl
-[bluetooth]# agent KeyboardOnly
-Agent registered
-[bluetooth]# default-agent
-Default agent request successful
-[bluetooth]# pair 00:80:25:49:6C:E3
-Attempting to pair with 00:80:25:49:6C:E3
-[CHG] Device 00:80:25:49:6C:E3 Connected: yes
-Request PIN code
-[agent] Enter PIN code: 0000</code></pre>
-</div></div>
-</div></div>
-<div class="paragraph"><p>After the devices are paired, press the <em>Save</em> button of the dialogue.
-This closes the Bluetooth dialogue. Now select <em>Download</em> in the <em>Download from
-dive computer</em> dialogue which should still be open. The downloaded dives are
-shown on the righthand side of the download dialogue.</p></div>
-<div class="sect4">
-<h5 id="_on_windows">On Windows:</h5>
-<div class="imageblock" style="text-align:center;">
-<div class="content">
-<img src="images/DC_import_Bluetooth_Windows.png" alt="FIGURE: Download Bluetooth on Windows" />
-</div>
-</div>
-<div class="paragraph"><p>On <em>Windows</em> platforms the <em>Local Bluetooth device details section</em> on the right is not displayed as
-is the case on the Linux/Mac systems.
-To start a scan (by pressing the <em>Scan</em> button)
-check that the Bluetooth device on the <em>Subsurface</em> computer is turned on by selecting
-the dive computer from the list of available Bluetooth devices (see image above). If the dive computer
-is being accessed by Subsurface for the first time, it’s possible Subsurface will
-request a Pass Code or PIN number. Supply the Pass Code recommended in the user manual of the dive computer.
-A Pass Code or PIN of 0000 is often the default.</p></div>
-<div class="paragraph"><p>The pairing step is checked and done automatically during
-the download process. If the devices have never been paired the system will ask
-for your permission and put a message on the right side of the screen: <em>Add a
-device, Tap to set up your DC device</em>. Always allow this pairing. After a
-discovered item is selected, select the <em>Save</em> button.
-Finally select the <em>Download</em> button on the <em>Download</em> dialogue and wait for the process to complete.</p></div>
-<div class="admonitionblock">
-<table><tr>
-<td class="icon">
-<img src="images/icons/important.png" alt="Important" />
-</td>
-<td class="content">Currently <em>Subsurface</em> works only with local Bluetooth
-adapters which use Microsoft Bluetooth Stack. If the local device uses
-<em>Widcomm</em>, <em>Stonestreet One Bluetopia Bluetooth</em> or <em>BlueSoleil</em> drivers it
-will not work. However, Bluetooth hardware/dongles from these manufacturers
-(e.g. iSonic) that support the Microsoft Bluetooth Stack do work.</td>
-</tr></table>
-</div>
-<div class="paragraph"><p>A log message on the bottom left of the <em>Remote Bluetooth device selection</em>
-shows details about the current status of the Bluetooth agent. To
-select another dive computer for download using the "Remote Bluetooth selection dialogue"
-press the three-dots button from the <em>"Choose Bluetooth download mode"</em> option.</p></div>
-<div class="admonitionblock">
-<table><tr>
-<td class="icon">
-<img src="images/icons/important.png" alt="Important" />
-</td>
-<td class="content"><strong>IN CASE OF PROBLEMS</strong>: If the Bluetooth adapter from the <em>Subsurface</em> computer
-gets stuck and the <em>Download</em> process fails repeatedly,
- <em>unpair</em> the devices and then repeat the above steps. If this is not successful,
- <a href="#S_HowFindBluetoothDeviceName"><em>Appendix A</em></a> contains
-information for manually setting up and inspecting the Bluetooth connection
-with <em>Subsurface</em>.</td>
-</tr></table>
-</div>
-</div>
-</div>
-<div class="sect3">
-<h4 id="S_DeviceNames">5.2.3. 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 a buddy’s dive computer is the
-same make and model as your own and dive logs are uploaded from both dive computers
-to the same <em>Subsurface</em> computer, then
-you might like to call one "Alice’s Suunto D4" and the other
-"Bob’s Suunto D4". Alternatively, consider a technical diver who 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 "Suunto D4 (2)". This is easily done in <em>Subsurface</em>.
-On the <strong>Main Menu</strong>, select <em>Log → Edit device names</em>. A dialog box opens, showing 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">5.2.4. Updating the dive information imported from the dive computer.</h4>
-<div class="paragraph"><p>With the uploaded dives in the <strong>Dive List</strong>, the information from the dive
-computer is not complete and more details must be added to have
-a full record of the dives. To do this,
-the <strong>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 class="sect4">
-<h5 id="S_Notes_dc">Notes</h5>
-<div class="paragraph"><p>To have a more complete dive record, the user needs to add
-additional information by hand. The procedure
-below is virtually identical for hand-entered dives and for dives downloaded from a dive computer.</p></div>
-<div class="paragraph"><p>In some cases,
-you must provide the date and time of the dive, for example when entering a dive by hand or when a
-dive computer doesn’t provide the date and time of the dive.
-(Usually the date and time of the dive, gas mixture and water temperature are
-shown as obtained from the dive computer)
-If the contents of the <strong>Notes tab</strong> is changed or edited in any way, the message in a blue box at
-the top of the panel shows the dive is being edited. If you
-click on the <strong>Notes</strong> tab, the following fields are
-visible (left hand image, below):</p></div>
-<div class="imageblock" style="text-align:center;">
-<div class="content">
-<img src="images/AddDive3_f22.jpg" alt="FIGURE: The Notes tab" />
-</div>
-</div>
-<div class="paragraph"><p>The right hand image, above, shows a <strong>Notes tab</strong> filled with dive information.
-The <strong>Time</strong> field reflects the date and time of the dive. By clicking
-the date, a calendar is displayed from which
-you 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 over-typing the
-information displayed.</p></div>
-<div class="paragraph"><p><strong>Air/water temperatures</strong>: Air and water temperatures during the dive are shown
-in text boxes to the right of the Start time. Many dive computers supply water
-temperature information and this box may have information.
-If air temperature isn’t provided by the dive computer, the first temperature reading
-might be used for the air temperature. Generally this is close to the real air temperature.
-If editing is required, only a value is required, the units of temperature will be
-automatically supplied by
-<em>Subsurface</em> (following the <em>Preferences</em>, metric or imperial units will
-be used).</p></div>
-<div class="paragraph"><p><strong>Location</strong>:</p></div>
-<div class="admonitionblock">
-<table><tr>
-<td class="icon">
-<img src="images/icons/warning2.png" alt="Warning" />
-</td>
-<td class="content">Dive locations are managed as a <strong>separate</strong> part of the dive log.
-The dive information in the <strong>Notes</strong> and <strong>Equipment</strong> tabs can therefore NOT be edited at the same
-time as the dive site information. Save all the other dive information (e.g.
-divemaster, buddy, protective gear, notes about the dive) by selecting <em>Apply changes</em> on the
-<strong>Notes</strong> tab BEFORE editing the dive site information. Then supply a dive site name in the
-textbox labelled <em>Location</em> on the <strong>Notes</strong> tab.</td>
-</tr></table>
-</div>
-<div class="paragraph"><p>Type in the name of the dive site, e.g. "Tihany, Lake Balaton, Hungary".
-If several dives are
-made at the same location, the site information for the first dive is re-used.
-Existing dive locations
-can be edited by selecting (on the <strong>Dive List</strong> panel) a dive done at that site
-and by opening the location information. Click the globe button on the
-right of the location name (see image on the right, above). When entering a dive location name, auto location of
-dive site names makes it easy to select an existing dive site name.
-When typing the name of a dive site,
-a dropdown list appears showing all sites with similar names. If the dive
-site has been used before, click on the already-existing name.
-The dive site names in the dropdown list contain either a globe symbol (indicating
-existing dive sites in the <em>Subsurface</em> database)
-or a <strong>+</strong> symbol (indicating dive site names that appear consistent with the
-current dive site name but which haven’t been added to the dive site database).
-If the present
-dive site has not been used before, a message appears as follows (image <strong>A</strong> below):</p></div>
-<div class="imageblock" style="text-align:center;">
-<div class="content">
-<img src="images/Locations1_f22.jpg" alt="FIGURE:Location description panel" />
-</div>
-</div>
-<div class="paragraph"><p>Doubleclick on the new dive site name. A panel appears to enter the coordinates and
-other information about the site (image <strong>B</strong>, above). The most important
-items are the coordinates of the site. There are three ways to specify coordinates:</p></div>
-<div class="olist loweralpha"><ol class="loweralpha">
-<li>
-<p>
-Use the world map in the bottom right hand part
- of the <em>Subsurface</em> window. The map displays an orange bar indicating "No location
- data - Move the map and double-click to set the dive location". Doubleclick
- at the appropriate place, and the orange bar disappears and the coordinates are
- stored.
-</p>
-</li>
-<li>
-<p>
-Use the <em>Subsurface</em> Companion app if you
- have an Android or iPhone device with GPS and if the dive site coordinates
- were stored using it.
- <a href="#S_Companion">Click here for more information</a>
-</p>
-</li>
-<li>
-<p>
-Enter by hand if the coordinates are known, using one of
- four formats with latitude followed by longitude:
-</p>
-<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>
-</li>
-</ol></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. Some keyboards
-don’t have the degree sign (°). It can be replaced by a <strong>d</strong> like this: N30d W20d.
-If both a dive site name and coordinates have been provided, save the
-dive site information by selecting the button <em>Apply changes</em> at the top of
-the panel.</p></div>
-<div class="paragraph"><p><strong>Important</strong>: GPS coordinates of a dive site are linked to the location
-name - so <strong>saving</strong> a dive site with only coordinates and no name
-causes problems. (Subsurface will think all of these
-dives have the same location and try to keep their GPS coordinates the
-same).</p></div>
-<div class="paragraph"><p><strong>Dive site name lookup:</strong> If coordinates have been typed into the appropriate
-text box, you can do an automated name lookup based on the coordinates.
-This is done when <em>Subsurface</em> uses the Internet to find the name of the dive site
-based on the coordinates that were typed. If a name has been found, it is
-automatically inserted into the tags box. The list box
-(Titled <em>Dive sites on same coordinates</em>") at the bottom
-of the dive site panel contains the names of other dives sites used at the
-current location. For instance if the dive site is "Blue Hole" and there are several
-sites named "Blue Hole", all of them are listed.</p></div>
-<div class="paragraph"><p>Enter any other contextual information about the dive site (Description and Notes),
-then select <em>Apply Changes</em> to save the geolocation for this dive site.
-The dive site information can later be edited by clicking the globe icon to the right of the
-dive site name in the <strong>Notes tab</strong>.</p></div>
-<div class="paragraph"><p><strong>Dive mode</strong>: This is a dropdown box allowing you to choose the type of dive
-performed. The options are OC (Open Circuit SCUBA, the default setting, for most recreational dives),
-Freedive (dive without SCUBA equipment), CCR (Closed-circuit
-rebreather) and pSCR (Passive semi-closed rebreather).</p></div>
-<div class="paragraph"><p><strong>Divemaster</strong>: The name of the divemaster or dive guide should be
-entered in this field
-which offers auto selection based on the list of dive masters in
-the current logbook.</p></div>
-<div class="paragraph"><p><strong>Buddy</strong>: In this field, enter the name(s) of the buddy or buddies
-(separated with commas) who were on the
-dive. Auto selection 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 dive suit used can be entered.
-Auto selection of the suit description is available.
-Some dry-suit users may choose to use this field to record what combination of
-suit and thermal under suit was used.</p></div>
-<div class="paragraph"><p><strong>Rating</strong>: You 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>: You 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 done 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 you starts typing a tag, the
-program
-will list the tags that correspond to the typing. For instance, by typing
-<code>cav</code>, the tags <strong>cave</strong> and <strong>cavern</strong> are shown 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 <em>Apply changes</em> and <em>Discard changes</em> buttons are used to save all the information for tabs
-in the <strong>Info</strong> panel and in the <strong>Dive Profile</strong> panel. Use them
-when <strong>ALL</strong> other information has been added. The image <a href="#S_Notes_dc">at the beginning of this section</a>
-shows an example of a <strong>Notes tab</strong> after completing the dive information.</p></div>
-</div>
-<div class="sect4">
-<h5 id="_equipment">Equipment</h5>
-<div class="paragraph"><p>The Equipment tab lets you enter information about the type of
-cylinder and gas used, as well as the weights used for the dive. The
-message in the blue box at the top of the panel:</p></div>
-<div class="imageblock" style="text-align:center;">
-<div class="content">
-<img src="images/BlueEditBar_f22.jpg" alt="FIGURE: Blue edit bar" />
-</div>
-</div>
-<div class="paragraph"><p>shows 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 behavior of the <strong>Dive profile</strong>
-(top right-hand panel).</p></div>
-<div class="paragraph" id="cylinder_definitions"><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>For hand-entered dives, this information needs to be typed in. For dive computers,
-<em>Subsurface</em> often gets the gas used from the dive computer and
-automatically inserts the gas composition(% oxygen or % helium) in the table. The + button
-at the top right lets you add more cylinders for this dive. The dark
-dust bin icon on the left lets you delete 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.
-Start by selecting a cylinder type on the left-hand side of the
-table. To select a cylinder, the <em>Type</em> 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 just 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 (<em>Work.press</em>) will
-automatically be shown in the dialogue.</p></div>
-<div class="paragraph"><p>Next, 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, save the data
-either by pressing <em>ENTER</em> on the keyboard or by clicking outside the cell
-containing
-the cursor. Information for any additional cylinders can be added by using the<br />
-button at the top right hand. The 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 similar to that of the cylinder information. If you
-click
-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 <em>Type</em> 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>This can be used to select the type of weight system
-used during the dive or just may start typing in the box
-to specify a different weighting mechanism that will be saved by <em>Subsurface</em>.
-In the <strong>Weight</strong>
-field, type in the amount of weight used during the dive. After
-specifying the weight
-system, save the data by pressing <em>ENTER</em> on the keyboard or by clicking outside the
-cell with the cursor.
-It’s 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 dust bin 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>
-<div class="sect3">
-<h4 id="_editing_several_selected_dives_simultaneously">5.2.5. 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 each is shown in the <strong>Dive profile</strong> tab, as well
-as a few items of information
-in the <strong>Notes</strong> tab (e.g. water temperature) and in the <strong>Equipment</strong> tab (e.g. gas pressures
-and gas composition). Other fields remain empty.
-It may be useful to simultaneously edit some of the
-fields in the <strong>Notes</strong> and <strong>Equipment</strong> tabs. For instance, it’s possible
-that a diver performed several dives during a single day, using identical equipment at the same
-dive site, or with the same divemaster and/or buddy or tags. Instead
-of completing the information for each
-dive separately, select all the dives for that day in the <strong>Dive List</strong> and
-insert the same information in the <strong>Notes</strong> and <strong>Equipment</strong> fields that need
-identical information. This is done by editing the dive notes or the equipment for any one
-of the selected dives.</p></div>
-<div class="paragraph"><p>Simultaneous editing only works with fields that do not already contain information.
-This means 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 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>Notes</strong> and <strong>Equipment</strong> tabs. Then, from the main menu, select <em>Log → Copy dive components</em>.
-A box is presented with a selection of check boxes for most of the fields in the <strong>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 → 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">5.2.6. Adding Bookmarks to a dive</h4>
-<div class="paragraph"><p>Many divers wish to annotate dives with text that indicate particular events,
-e.g. "Saw dolphins", or "Released surface buoy". This is easily
-done:</p></div>
-<div class="ulist"><ul>
-<li>
-<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 that point (see <strong>A</strong> below).
-</p>
-</li>
-<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>
-<li>
-<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>
-</li>
-<li>
-<p>
-Hovering the mouse over the red bookmark, the appropriate text is shown at
- the bottom of the information box (see <strong>D</strong> below).
-</p>
-</li>
-</ul></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">5.2.7. Saving the updated dive information</h4>
-<div class="paragraph"><p>The information entered in the <strong>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>Notes</strong> tab. If the <em>Apply changes</em> button
-is clicked,
-the dive data are saved in the memory image of the dive. If the <em>Discard changes</em>
-button is clicked, the newly entered dive data are
-erased from the computer memory, although the dive profile is
-retained. When the user exits <em>Subsurface</em> there is a final prompt to confirm
-the new data should now be saved permanently on the computer disk.</p></div>
-</div>
-</div>
-<div class="sect2">
-<h3 id="_importing_dive_information_from_other_digital_data_sources_or_other_data_formats">5.3. Importing dive information from other digital data sources or other data formats</h3>
-<div class="paragraph" id="S_ImportingAlienDiveLogs"><p>If you’ve been diving for some time, it’s possible several dives were
-logged using other dive log software. 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 you will need to
-export the logbook(s) to an intermediate format so 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. a spreadsheet) can also be imported by
-configuring the CSV import.
-<em>Subsurface</em> can also import UDDF and UDCF files used by some dive log
-software and some dive computers, like the Heinrichs & Weikamp DR5. Finally,
-for some dive log software like Mares Dive Organizer we currently recommend you
-import the logbooks first into a web service like <em>divelogs.de</em> and then import
-from there with
-<em>Subsurface</em>. Divelogs.de supports a few additional logbook formats that
-<em>Subsurface</em> currently cannot handle.</p></div>
-<div class="paragraph"><p>If the format of other software is supported natively on Subsurface, select
-either <em>Import → Import log files</em> or <em>File → 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. Below is more specific information
-to import data to <em>Subsurface</em>.
-==== Using the universal import dialogue</p></div>
-<div class="paragraph" id="Unified_import"><p>Importing dives from other software is done through a universal interface
-activated by selecting <em>Import</em> from the Main Menu, then clicking on
-<em>Import Log Files</em>. This brings up 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 accesses 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>
-Cochran dive logs
-</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>
-APD Inspiration/Evolution CCR logs
-</p>
-</li>
-<li>
-<p>
-LiquiVision logs
-</p>
-</li>
-<li>
-<p>
-divelog.de logs
-</p>
-</li>
-<li>
-<p>
-OSTC Tools 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 format and then the specific log file in the large window
-containing the file list on the right 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 class="sect3">
-<h4 id="_importing_from_ostctools">5.3.1. Importing from OSTCTools</h4>
-<div class="paragraph"><p><em>OSTC Tools</em> is a Microsoft-based suite of dive download and dive management tools for the OSTC
-family of dive computers. <em>OSTC Tools</em> downloads dive data from the dive computer and stores it
-as a binary file with file extension <em>.dive</em> . Subsurface can directly import these files when using
-the universal import dialogue. From the dropdown list at the bottom right select
-<em>OSTCTools Files (.dive .DIVE)</em>. This makes the <em>OSTC Tools</em> dive logs visible in the file list
-panel. Select one or more dive, then click the <em>Open</em> button. The OSTC dives are shown in the
-<strong>Dive List</strong> panel.</p></div>
-<div class="paragraph"><p>All H&W devices supported by OSTCTools can be imported to <em>Subsurface</em>. This includes
-OSTC, OSTC Mk2, OSTC 2N/2C, OSTC3, OSTC Sport, and probably although untested, Frog, OSTC2 and
-OSTC CR.</p></div>
-<div class="paragraph"><p>Please remember that OSTCTools is <strong>not</strong> a true diving log software, but rather a useful set of tools
-for analysis and management of OSTC devices. Only raw dive computer data will be
-imported to <em>Subsurface</em>; you have to manually complete the rest of the
-data you want (buddies, equipment, notes, etc).</p></div>
-</div>
-<div class="sect3">
-<h4 id="_importing_from_mares_dive_organizer_v2_1">5.3.2. Importing from Mares Dive Organizer V2.1</h4>
-<div class="paragraph"><p>Since Mares uses 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 gateway to extract the dive log information.</p></div>
-<div class="olist arabic"><ol class="arabic">
-<li>
-<p>
-Export the dive log data from Mares Dive Organizer to your
- desktop, using
- a <em>.sdf</em> file name extension. Refer to <a href="#Mares_Export">Appendix C</a> for more
- information.
-</p>
-</li>
-<li>
-<p>
-Data should then be imported into <em>www.divelogs.de</em>. You will first need to create a user
- account in
- <em>www.divelogs.de</em>. Log into that web site, then
- select <em>Import Logbook → Dive Organizer from the menu on the left hand side.
- The instructions must be carefully followed to transfer the dive information
- (in _.sdf</em> format) from the Dive Organizer database to <em>www.divelogs.de</em>.
-</p>
-</li>
-<li>
-<p>
-Finally, import the dives
- from <em>divelogs.de</em> to <em>Subsurface</em>, using the instructions below.
-</p>
-</li>
-</ol></div>
-</div>
-<div class="sect3">
-<h4 id="S_ImportingDivelogsDe">5.3.3. Importing dives from <strong>divelogs.de</strong></h4>
-<div class="paragraph"><p>Importing dive information from <em>divelogs.de</em> is simple, using a single
-dialogue box. The <em>Import → Import from Divelogs.de</em> option should be selected
-from the Main Menu. This
-brings up a dialogue box (see image <strong>A</strong> below). Enter a
-user-ID and password for <em>divelogs.de</em> 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 shown (see image <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">5.3.4. 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). The <em>CSV</em> format is a universal
-simplified format that allows easy information exchange between different computers or
-software packages. For an introduction to CSV-formatted files see <a href="#S_CSV_Intro">A Diver’s
-Introduction To CSV Files</a>. <em>Subsurface</em> dive logs can also be exported in <em>CSV</em> format to
-other software that reads this format. See <a href="#S_Appendix_D">APPENDIX D: Exporting a spreadsheet
-to CSV format</a> for information that may be helpful for importing spreadsheet-based data
-into <em>Subsurface</em>.</p></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>You can view a <em>CSV</em> file by using an ordinary text editor. It’s normally organized into
-a single line that provides the headers (or <em>field names</em> or <em>column headings</em>) of the data
-columns, followed by the data, one record per line.</p></div>
-<div class="paragraph"><p>There are two types of <em>CSV</em> dive logs that can be imported into <em>Subsurface</em>:</p></div>
-<div class="olist arabic"><ol class="arabic">
-<li>
-<p>
-<em>CSV dive details</em>: This dive log format contains similar information to that of a
- typical written dive log, e.g. dive date and time, dive depth, dive duration, names of
- buddy and divemaster and information about cylinder pressures before and
- after the dive, as well as comments about the dive. All the data for a single
- dive go on a single line of text, following the order of the column headings.
-</p>
-</li>
-<li>
-<p>
-<em>CSV dive profile</em>: This dive log format includes much more information about a single
- dive. For instance there may be information at 30-second intervals, indicating depth, water
- temperature, and cylinder pressure at that moment in time. Each line contains
- the information for a single instant in time during the dive, 30 seconds after that
- of the previous instant. Many lines
- are required to complete the depth profile information for a single dive. This is a common
- export format used by closed-circuit rebreather (CCR) dive equipment and many software
- packages that handle dive computer data and/or dive logs.
-</p>
-</li>
-</ol></div>
-<div class="paragraph"><p>Before being able to import the <em>CSV</em> data to <em>Subsurface</em> <strong>you needs to know a few
-things about the data being imported</strong>:</p></div>
-<div class="olist loweralpha"><ol class="loweralpha">
-<li>
-<p>
-Which character separates the different columns within a single line of
- data? This field separator should be either a comma (,) a semicolon (;) or a TAB character.
- This can be determined by opening the file with a text editor. If it is
- comma-delimited or semicolon-delimited, the comma or semicolon
- characters between the values are clearly visible. If these are not evident and
- the numbers are aligned in columns,
- the file is probably TAB-delimited (i.e. it uses a TAB as a field separator).
-</p>
-</li>
-<li>
-<p>
-Which data columns need to be imported into <em>Subsurface</em>? Is it a <em>CSV dive details</em>
- file or a <em>CSV dive profile</em> file? Open the file using a text editor and note
- the titles of the columns to be imported and their column positions.
-</p>
-</li>
-<li>
-<p>
-Is the numeric information (e.g. dive depth) in metric or in imperial units?
-</p>
-</li>
-</ol></div>
-<div class="paragraph"><p>With this information, importing the data into <em>Subsurface</em> is
-straightforward. Select
-<em>Import → Import Log Files</em> from the main menu. In the resulting file
-selection menu, select <em>CSV files</em> (towards the bottom right). This shows all .CSV files in the selected
-directory. Select the file that needs to be imported. A configuration panel
-appears as depicted below:</p></div>
-<div class="imageblock" style="text-align:center;">
-<div class="content">
-<img src="images/csv_import1_f20.jpg" alt="FIGURE: CSV download dialogue 1" />
-</div>
-</div>
-<div class="paragraph"><p>At the top left, there is a dropdown list containing pre- configured
-settings for common dive computers and software packages.
- If the <em>CSV</em> file being imported originated from any of
-these pre-configured items, select it. Otherwise use the <em>Manual Import</em>
-option. The configuration panel also has dropdown lists for the specification of the appropriate
-field separator (Tab, comma or semicolon), the date format used in the <em>CSV</em> file,
-the time units (seconds, minutes or minutes:seconds), as well as the unit system
-(metric or imperial). Selecting the appropriate options among these is critical for
-the successful data import.</p></div>
-<div class="paragraph"><p>Complete this by ensuring that all the data columns have the appropriate
-column headings. The top blue row of the data table contains the column
-headings found in the <em>CSV</em> data file. The blue row of balloons immediately above these
-contains the names understood by <em>Subsurface</em>. These balloons can be moved using a drag-and-drop action. For
-instance, <em>Subsurface</em> expects the column heading for Dive number (" # ") to be "Dive # ". If
-the column heading that <em>Subsurface</em> expects is not in the blue row, drag the
-appropriate balloon from the upper area and drop it in the appropriate blue
-cell at the top of the table. To indicate the correct column for "Dive #", drag
-the ballooned item labelled "Dive # " and drop it in the blue
-cell immediately above the white cell containing " # ". This is depicted in
-the image below.</p></div>
-<div class="imageblock" style="text-align:center;">
-<div class="content">
-<img src="images/csv_import2_f20.jpg" alt="FIGURE: CSV download dialogue 2" />
-</div>
-</div>
-<div class="paragraph"><p>Continue in this way to ensure all the column headings in the blue row of
-cells correspond to the headings listed in the top part of the dialogue.
-When finished, select the <em>OK</em> button on the bottom right of the dialogue.
-The data from the <em>CSV</em> file are imported and shown in the <strong>Dive List</strong> panel.</p></div>
-<div class="sidebarblock" id="S_CSV_Intro">
-<div class="content">
-<div class="paragraph"><p><strong>A Diver’s Introduction to <em>CSV</em> Files</strong></p></div>
-<div class="admonitionblock">
-<table><tr>
-<td class="icon">
-<img src="images/icons/important.png" alt="Important" />
-</td>
-<td class="content"><em>CSV</em> is an abbreviation for a data file format: <em>Comma-Separated Values</em>. It is a
-file format that lets you view or edit information using a text editor like
-Notepad (Windows), gedit (Linux) or TextWrangler (OS/X). There are two main advantages of
-the <em>CSV</em> format. First, the data are easily editable as text without any proprietary software.
-Second, all information is human-readable, not obscured by any custom or
-proprietary attributes that proprietary software inserts into files.
-Because of its simplicity the <em>CSV</em> 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>, <em>CSV</em> files can also
-be used to import information from other sources like spreadsheet-based dive logs and
-some dive computers.</td>
-</tr></table>
-</div>
-<div class="paragraph"><p><em>CSV</em> files can be created or edited with a normal text editor. The most important attribute of a
-<em>CSV</em> 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 <em>CSV</em> file. <em>CSV</em> files are
-normally organized 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>The above 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 <em>CSV</em> 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>When a <em>CSV</em> file is selected for import, <em>Subsurface</em> displays the column headers as well as some of the data
-in the first few lines of the <em>CSV</em> file, making it much easier to work with <em>CSV</em> files.
-<em>CSV</em> files can be used in many contexts for importing data into a <em>Subsurface</em> dive log.
-Knowing a few basic things about the content of the <em>CSV</em> file helps with a smooth import
-of the dives into <em>Subsurface</em>.</p></div>
-</div></div>
-<div class="admonitionblock">
-<table><tr>
-<td class="icon">
-<img src="images/icons/important.png" alt="Important" />
-</td>
-<td class="content">But, the <em>CSV</em> import has a couple of caveats. Avoid some special characters
-like ampersand (&), less than (<), greater than (>) and double quotes (") as part
-of the numbers or text within a cell. The
-file should use UTF-8 character set, if using non-ASCII characters. Also the
-size of the <em>CSV</em> file might cause problems. Importing 100 dives at a time
-(<em>CSV dive details</em>) works, but larger files might exceed
-the limits of the parser used. When encountering problems with <em>CSV</em> imports, first try with
-a smaller file to make sure everything works.</td>
-</tr></table>
-</div>
-</div>
-</div>
-</div>
-<div class="sect2">
-<h3 id="S_Companion">5.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 <em>Android device</em> or
-<a href="#S_iphone"><em>iPhone</em></a> with GPS, the coordinates
-for the diving
-location can be automatically passed to the <em>Subsurface</em> dive log. The Companion App
-stores dive locations on a dedicated Internet server. <em>Subsurface</em> can collect
-the locations from the server.
-To do this:</p></div>
-<div class="sect3">
-<h4 id="_create_a_companion_app_account">5.4.1. Create a Companion App account</h4>
-<div class="ulist"><ul>
-<li>
-<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 giving you access to the file server and Companion App capabilities.
-</p>
-</li>
-<li>
-<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&fdid=org.subsurface">F-Droid</a>.
-</p>
-</li>
-</ul></div>
-</div>
-<div class="sect3">
-<h4 id="_using_the_subsurface_companion_app_on_an_android_smartphone">5.4.2. Using the Subsurface companion app on an Android smartphone</h4>
-<div class="paragraph"><p>On first use the app has three options:</p></div>
-<div class="ulist"><ul>
-<li>
-<p>
-<em>Create a new account.</em> Equivalent to registering in the <em>Subsurface</em> companion
- page using an Internet browser. You can request a <strong>DIVERID</strong> using this option,
- but it’s supplied via email and followed up by interaction with the
- <a href="http://api.hohndel.org/login/"><em>Subsurface companion web page</em></a> to
- activate the account.
-</p>
-</li>
-<li>
-<p>
-<em>Retrieve an account.</em> If users forget their <strong>DIVERID</strong> they will receive an email
- to recover the number.
-</p>
-</li>
-<li>
-<p>
-<em>Use an existing account.</em> Users are prompted for their <strong>DIVERID</strong>. The app saves
- this <strong>DIVERID</strong> and doesn’t ask for it again unless you use the <em>Disconnect</em> menu
- option (see below).
-</p>
-</li>
-</ul></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, by selecting <em>File → Preferences → Defaults</em> from the main menu
-in <em>Subsurface</em> itself.
-This helps synchronization 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 you are 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
-shows with 3 options:</p></div>
-<div class="ulist"><ul>
-<li>
-<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>
-</li>
-<li>
-<p>
-Use Map: This option lets you fix a position by searching a world map. A
- world map is shown (see <strong>B</strong> below) on which you can show the desired position
- with a <em>long press</em> on the touch
- sensitive screen (if the marked location is wrong, simply choose a new location)
- and select the check symbol in the upper right. A dialog is shown letting you enter the
- name of the dive location and the date and time of the dive (see <strong>C</strong> below). In order to import this
- dive location in <em>Subsurface</em> you should set the time to agree with the time of
- that dive on the dive computer.
-</p>
-</li>
-</ul></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="ulist"><ul>
-<li>
-<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 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>
-</li>
-</ul></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
-showing they need to be uploaded to the server. You
-can select individual dive locations from the list. A selected location has a
-check mark in the selection box on the left. Group operations (like <em>Delete</em> or <em>Send</em>)
-are performed on several selected locations.</p></div>
-<div class="paragraph"><p>Dive locations in this list can be viewed in two ways: a list of locations or a
-map showing them. 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 you select 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 you select 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.
-After editing and saving a dive location (see <strong>C</strong> above),
-upload it to the web
-service, as explained below.
-</p>
-</li>
-</ul></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 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">Be careful! 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>
-<li>
-<p>
-<em>User ID.</em> The DIVERID obtained by registering as described above. The easiest way to
- get it is to copy and paste from the confirmation email or just type it in.
-===== Synchronisation
-</p>
-</li>
-<li>
-<p>
-<em>Synchronize on startup</em>. If selected, dive locations in the Android device and those
- on the web service synchronize each time the app is started.
-</p>
-</li>
-<li>
-<p>
-<em>Upload new dives.</em> If selected, each time the user adds a dive location it is
- automatically sent to the server.
-</p>
-</li>
-</ul></div>
-</div>
-<div class="sect4">
-<h5 id="_background_service">Background service</h5>
-<div class="paragraph"><p>Instead of entering an unique dive location, you can leave the service running
-in the background of your Android device, allowing a continuous collection of GPS locations.</p></div>
-<div class="paragraph"><p>The settings below define the behavior of the service:</p></div>
-<div class="ulist"><ul>
-<li>
-<p>
-<em>Min duration.</em> In minutes. The app will try to get a location every X minutes
- until stopped by the user.
-</p>
-</li>
-<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 diver 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 50 m
-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 diver is not moving, only one location is saved.
-If the diver 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="ulist"><ul>
-<li>
-<p>
-<em>Mailing List.</em> The mail box for <em>Subsurface</em>. Users can send an email to the
-Subsurface mailing list.
-</p>
-</li>
-<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>Starts 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 admittedly a badly named option that disconnects the app from the server.
-It resets 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 your 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="S_iphone">5.4.3. Using the Subsurface companion app on an <em>iPhone</em> to record dive locations</h4>
-<div class="paragraph"><p>The iPhone interface is quite simple. Type the user ID (obtained
-during registration) into the space reserved for it, then select "Dive in"
-(see left part of the image below) and start collecting dive location information.</p></div>
-<div class="imageblock" style="text-align:center;">
-<div class="content">
-<img src="images/iphone.jpg" alt="FIGURE: Using iPhone companion application" width="640" />
-</div>
-</div>
-<div class="paragraph"><p>Dives can be added automatically or manually. In manual mode, a dive location or waypoint is added to the GPS input stream. In automatic
-mode, a continuous path of GPS locations is created from which,
-after import, Subsurface can select the appropriate GPS
-locations based on the times of dives. The default mode for the
-<em>iphone</em> is automatic. When adding a dive, the
-location service is started automatically and a red bar appears at the bottom
-of the screen. After the dive, click on the red
-bar to end the location service. While the location
-service is running you can only add dives manually.</p></div>
-<div class="paragraph"><p>You can edit the site name afterwards by selecting the dive
-from the dive list and clicking on the site name. There are no other
-editable fields. The dive list is automatically uploaded from the iPhone
-to the web service. There isn’t an option to
-trigger upload manually.</p></div>
-</div>
-<div class="sect3">
-<h4 id="_downloading_dive_locations_to_the_em_subsurface_em_divelog">5.4.4. 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
-→ 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 start 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, you can update the locations
-of the newly entered or uploaded dives in <em>Subsurface</em>. That applies the
-coordinates and names entered on the app to all the new dives that match the
-date-times of the uploaded GPS localities. If you have 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 depends
-on agreeing date-time information between the two devices. Although <em>Subsurface</em> has
-a wide range tolerance, it may not be able to identify the appropriate dive if there’s
-a large difference between the time in the dive computer and that of the Android device.
-That results 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).
-<em>Subsurface</em> may also 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 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="ulist"><ul>
-<li>
-<p>
-<em>Background service</em> may fill the location list with
- unnecessary locations that don’t correspond to the exact dive point but do correspond to the boat’s route.
- Right now, these locations are difficult to delete from the server. In some situations it
- is better 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 you want to keep the location list clear to see dives in the web service map display (see above).
-</p>
-</li>
-<li>
-<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>
-</li>
-</ul></div>
-</div>
-</div>
-<div class="sect2">
-<h3 id="S_LoadImage">5.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. To match each photograph with a specific
-dive, <em>Subsurface</em> lets you 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_synchronizing_between_dive_computer_and_camera">5.5.1. Loading photos and synchronizing 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 up the time synchronization dialog, shown below. But be
-aware that the time
-synchronization 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 synchronize,
-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> synchronizes in three ways:</p></div>
-<div class="ulist"><ul>
-<li>
-<p>
-<strong>Pro-actively</strong>: Before the dive, ensure synchronization of the dive computer time settings with
- the time settings of the camera by changing the date-time settings on one or both of these devices.
-</p>
-</li>
-<li>
-<p>
-<strong>Manually</strong>: If you wrote down the exact camera time at the start of a dive, the
- difference in time between the two devices can be determined. As long as the device
- settings for time has not been changed in either device, you could write down the times of
- both devices after the dive or even at the end of the day. You 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>, shown 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 synchronization is done.
-</p>
-</li>
-</ul></div>
-<div class="imageblock" style="text-align:center;">
-<div class="content">
-<img src="images/LoadImage3b_f20.jpg" alt="FIGURE: Synchronization dialog" />
-</div>
-</div>
-<div class="ulist"><ul>
-<li>
-<p>
-<strong>By photograph</strong>: There is a very slick way of synchronizing. If you take a
- photograph of the face of the dive computer showing the time, then <em>Subsurface</em> can get
- the exact time the photograph was taken, using the metadata the camera stores within
- each photo. To do this, use the bottom half of the <em>Time shift</em> dialog. If you use
- the bottom part, the top part of the dialog is ignored. Click on
- the horizontal bar called "<em>Select image of dive computer showing time</em>. This brings up
- a file browser letting you select the photograph of the dive computer time. 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 it 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 it can synchronize.
- Image <strong>B</strong> above shows a photograph of the face of the dive computer and with the date-time tool set to the
- date-time.
-</p>
-</li>
-</ul></div>
-<div class="paragraph"><p>If the timestamp of a photograph is more than 30 minutes before or after the dive, it is not placed on
-the dive profile.</p></div>
-</div>
-<div class="sect3">
-<h4 id="_viewing_the_photos">5.5.2. Viewing the photos</h4>
-<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>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.
- To view the photos on the dive profile, activate the <em>show-photos</em> button in the tool bar
- to the left of the dive profile:
-</p>
-</li>
-</ul></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>This results in a profile display as in the image below:</p></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 you hover the mouse over any of the photo icons, 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 added photographs. (see the image below). Note that the thumbnail
-has a small dustbin icon in the bottom right hand corner (see image above). Selecting
-the dustbin removes the image from the dive. Be careful
-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">5.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>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
-show 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">5.5.4. Photos on an external hard disk</h4>
-<div class="paragraph"><p>Most underwater photographers store photos on an external drive. If such a drive can be mapped by the operating system
-(almost always the case) the photos can be directly accessed by <em>Subsurface</em>. This eases 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 synchronization (see text above) is used.
-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.
-If the external drive with the photos is re-connected, the photos can be seen in the normal way.</p></div>
-</div>
-<div class="sect3">
-<h4 id="S_FindMovedImages">5.5.5. Moving photographs among directories, hard disks or computers</h4>
-<div class="paragraph"><p>After a photograph has been loaded into <em>Subsurface</em> and associated with a specific dive, the directory
- where the photo lies is stored, letting <em>Subsurface</em> find the photograph when the dive is
- opened again. If the photo or the whole photo collection is moved to another drive or to a different
- machine, the directory structure will be different to that of the original uploaded
- photo. When this happens, <em>Subsurface</em> looks for the photos at their original location before they were moved,
- cannot find them and cannot display them. Because after moving photos, large numbers of photos
- may need to be deleted and re-imported from the new location, <em>Subsurface</em> has a mechanism that eases the
- process of updating the directory information for each photo: automatic updates using fingerprints.</p></div>
-<div class="paragraph"><p>When a photo is loaded into <em>Subsurface</em>, a fingerprint for the image is calculated and stored with the
- other reference information for that photo. After moving a photo collection (that has already been loaded
- into <em>Subsurface</em>) to a different directory, disk or computer, <em>Subsurface</em> can:</p></div>
-<div class="ulist"><ul>
-<li>
-<p>
-look through a particular directory (and all its subdirectories recursively) where photos have been moved
-to,
-</p>
-</li>
-<li>
-<p>
-calculate fingerprints for all photos in this directory, and
-</p>
-</li>
-<li>
-<p>
-if there is a match between a calculated fingerprint and the one originally calculated when a photo was
- loaded into <em>Subsurface</em> (even if the original file name has changed), automatically update the
- directory information so that <em>Subsurface</em> can find the photo in the new moved directory.
-</p>
-</li>
-</ul></div>
-<div class="paragraph"><p>This is done by selecting from the Main Menu: <em>File → Find moved images</em>. This brings up a window within
- which the NEW directory of the photos needs to be specified. Select the appropriate directory and click
- the <em>Scan</em> button towards the bottom right of the panel. The process may require several minutes to
- complete, after which <em>Subsurface</em> will show the appropriate photographs when a particular dive is opened.</p></div>
-<div class="sidebarblock" id="Image_fingerprint_upgrade">
-<div class="content">
-<div class="paragraph"><p><strong>Upgrading existing photo collections without fingerprints</strong></p></div>
-<div class="admonitionblock">
-<table><tr>
-<td class="icon">
-<img src="images/icons/important.png" alt="Important" />
-</td>
-<td class="content"><em>Subsurface</em> automatically calculates fingerprints for all images that it can access.
-When manipulating images, be sure all the images associated with the dive log can be accessed by <em>Subsurface</em>.</td>
-</tr></table>
-</div>
-<div class="paragraph"><p><em>Subsurface</em> automatically checks and, if necessary, updates the fingerprints associated with a single dive if:
-- The images associated with that dive are visible as thumbnails on the <strong>Dive Profile</strong>.
-- If you edit anything in the <strong>Notes tab</strong> panel and save the edits by selecting <em>Apply changes</em>.</p></div>
-</div></div>
-</div>
-</div>
-<div class="sect2">
-<h3 id="_logging_special_types_of_dives">5.6. Logging special types of dives</h3>
-<div class="sect3">
-<h4 id="S_MulticylinderDives">5.6.1. Multicylinder dives</h4>
-<div class="paragraph"><p><em>Subsurface</em> easily handles dives involving more than one cylinder. Multi-cylinder diving usually happens
-(a) if a diver doesn’t have enough gas for the complete dive in a single cylinder; (b) if a diver
-needs more than one gas mixture because of the depth or the decompression needs of the dive. For this reason
-multi-cylinder dives are often used by technical divers who dive deep or long. As far
-as <em>Subsurface</em> is concerned, there are only two types of information that need to be provided:</p></div>
-<div class="ulist"><ul>
-<li>
-<p>
-<strong>Describe the cylinders used during the dive</strong> This is performed in the <strong>Equipment tab</strong> of
- the <strong>Info</strong> panel, as <a href="#cylinder_definitions">described above</a>. Enter the cylinders one by one,
- specifying each’s characteristics and the gas composition within it.
-</p>
-</li>
-<li>
-<p>
-<strong>Record the times at which the switch from one cylinder to another was done:</strong> This is information
- tracked by some dive computers (provided the diver indicated these changes to the dive computer
- by pressing specific buttons). If the dive computer does not provide the information, the diver has to
- record these changes using a different method, e.g. writing it on a slate.
-</p>
-</li>
-<li>
-<p>
-<strong>Record the cylinder changes on the dive profile</strong>: If the latter option
- was followed, the diver needs to indicate the gas change event by right-clicking at the appropriate point
- in time on the <strong>Dive Profile</strong> panel and indicating the cylinder to which the change was made. After
- right-clicking, follow the context menu to "Add gas change" and select the appropriate cylinder from
- those defined during the first step, above (see image below). If the
- <strong>tank bar</strong> button in the toolbar has been activated, the cylinder switches are also indicated in the
- tank bar.
-</p>
-</li>
-</ul></div>
-<div class="paragraph"><p>When this is complete, <em>Subsurface</em> indicates the appropriate use of cylinders in the dive profile.
-Below is a multi-cylinder dive, starting off with EAN28, then changing cylinders to EAN50 after 26 minutes
-for decompression.</p></div>
-<div class="imageblock" style="text-align:center;">
-<div class="content">
-<img src="images/multicylinder_dive.jpg" alt="FIGURE: Multicylinder profile" />
-</div>
-</div>
-</div>
-<div class="sect3">
-<h4 id="_sidemount_dives">5.6.2. Sidemount dives</h4>
-<div class="paragraph"><p>Sidemount diving is just another form of multi-cylinder diving, often with both or all cylinders having
-the same gas mixture. Although it’s a popular configuration for cave divers, Sidemount
-diving can be done by recreational divers who’ve completed the appropriate training. sidemount
-dive logging involves three steps, exactly as with multi-cylinder dives above:</p></div>
-<div class="ulist"><ul>
-<li>
-<p>
-<strong>During the dive, record cylinder switch events</strong>. Since sidemount diving normally involves two
- cylinders with air or with the same gas mixture, <em>Subsurface</em> distinguishes between these different
- cylinders. In contrast, many dive computers that allow gas switching only distinguish between different
- <em>gases</em> used, not among different <em>cylinders</em> used. This means when sidemount dives are downloaded
- from these dive computers, the switching event between cylinders with the same gas is not downloaded. This may mean
- that a diver may have to keep a written log of cylinder switch times using a slate, or (if the dive computer
- has the capability) marking each cylinder switch with a bookmark that can be retrieved later. Returning
- from a dive with the times of cylinder changes is the only tricky part of logging sidemount dives.
-</p>
-</li>
-<li>
-<p>
-<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>Info Panel</strong> (see
- image below where two 12 litre cylinder were used).
-</p>
-</li>
-<li>
-<p>
-<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 shown on the dive profile.
- Cylinder changes are recorded by right-clicking at the appropriate point on the dive profile, 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 shown 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 shown 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 in the image below.
-</p>
-</li>
-</ul></div>
-<div class="imageblock" style="text-align:center;">
-<div class="content">
-<img src="images/sidemount1.jpg" alt="FIGURE: Sidemount profile" />
-</div>
-</div>
-<div class="paragraph"><p>This section gives an example of the versatility of <em>Subsurface</em> as a dive logging tool.</p></div>
-</div>
-<div class="sect3">
-<h4 id="S_sSCR_dives">5.6.3. Semi-closed circuit rebreather (SCR) dives</h4>
-<div class="admonitionblock">
-<table><tr>
-<td class="icon">
-<img src="images/halcyon_RB80.jpg" alt="Note" />
-</td>
-<td class="content">Passive semi-closed rebreathers (pSCR) are a technical advance in diving equipment that
-recirculates the breathing gas a diver uses, while removing carbon dioxide from
-the exhaled gas. While a small amount (typically a tenth) of the exhaled breathing gas is released into the water,
-a small amount of fresh gas is released from the back gas cylinder (typically containing nitrox).
-A diver using a single cylinder of breathing gas can therefore dive for much longer periods than
-using a recreational open-circuit configuration. With pSCR equipment, a very small amount of breathing
-gas is released every time the diver inhales. With active SCR (aSCR) equipment, in contrast, a small amount of
-breathing gas is released continuously from the back cylinder.</td>
-</tr></table>
-</div>
-<div class="paragraph"><p>To log pSCR dives, no special procedures are required. Use the normal steps outlined above:</p></div>
-<div class="ulist"><ul>
-<li>
-<p>
-Select pSCR in the <em>Dive Mode</em> dropdown list on the <strong>Info</strong> panel.
-</p>
-</li>
-<li>
-<p>
-pSCR diving often involves gas changes, requiring an additional cylinder.
- Define all the appropriate cylinders as described above
- and indicate the cylinder/gas changes as described above in the section on <a href="#S_MulticylinderDives">multicylinder dives</a>.
-</p>
-</li>
-</ul></div>
-<div class="paragraph"><p>If a pSCR <em>Dive Mode</em> has been selected, the dive ceiling for that is adjusted for the oxygen
-drop across the mouthpiece, which often requires longer decompression periods. Below is a dive profile
-of a pSCR dive using EAN36 on the back cylinder and oxygen for decompression. Note that this dive lasted
-over two hours.</p></div>
-<div class="imageblock" style="text-align:center;">
-<div class="content">
-<img src="images/pSCR_profile.jpg" alt="FIGURE: pSCR profile" />
-</div>
-</div>
-</div>
-<div class="sect3">
-<h4 id="S_CCR_dives">5.6.4. Closed circuit rebreather (CCR) dives</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. They also do two things to maintain a
-breathable oxygen concentration:
-a) remove carbon dioxide from the exhaled gas
-b) regulate the oxygen concentration to remain within safe diving limits.
-The CCR interface of <em>Subsurface</em> is currently experimental
-and under active development. Subsurface currently supports Poseidon MkVI
-and APD Discovery/Evolution dive computers. In contrast to a conventional recreational
-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 it
-imports dive log data from other digital databases: one dive at a time.</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 → Import
-log files</em> to bring up the <a href="#Unified_import">universal import dialogue</a>. As
-explained in that section, the bottom right
-hand of the import dialogue contains a dropdown list (labled <em>Filter:</em>) of appropriate devices
-that currently include(Poseidon) MkVI or APD log viewer files. Import for other
-CCR equipment is under active development. Having selected the appropriate CCR format and
-the directory where the original dive logs have been stored from the CCR dive
-computer, 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,
-click the <em>Open</em> button at the bottom right hand of the universal import dialogue.
-The selected dive is imported to the <em>Subsurface</em> dive list.</p></div>
-</div>
-<div class="sect4">
-<h5 id="_displayed_information_for_a_ccr_dive">Displayed information for a CCR 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 contrast to recreational
-equipment (where pO<sub>2</sub> values are calculated based on gas composition and dive depth),
-CCR equipment provide actual measurements of pO<sub>2</sub>, derived from oxygen sensors.
-In this case the graph for oxygen partial pressure
-should be fairly flat, reflecting the setpoint settings during the dive. The mean
-pO<sub>2</sub> is NOT the mean oxygen partial pressure as given by the CCR equipment, but
-a value calculated by <em>Subsurface</em> as follows:</p></div>
-<div class="ulist"><ul>
-<li>
-<p>
-For TWO O<sub>2</sub> sensors the mean value of the two sensors are given.
-</p>
-</li>
-<li>
-<p>
-For THREE-sensor systems (e.g. APD), the mean value is also used. However
- differences of more than 0,1 bar in the simultaneous readings of different sensors are
- treated as false. If one of the three sensors provides false data, it is ignored.
-</p>
-</li>
-<li>
-<p>
-If no sensor data are available, the pO<sub>2</sub> value is assumed to be equal to the setpoint.
-</p>
-</li>
-</ul></div>
-<div class="paragraph"><p>The mean pO<sub>2</sub> of the sensors is indicated with a green line,</p></div>
-<div class="paragraph"><p>The oxygen setpoint values as well as the readings from the individual
-oxygen sensors can be shown. The display of additional CCR information is turned on by
-checking the appropriate boxes in the <em>Preferences</em> panel (accessible by
-selecting <a href="#S_CCR_options"><em>File → Preferences → Graph</em></a>). This part of
-the <em>Preferences</em> panel is shown in the image below, representing two checkboxes that modify
-the display of pO<sub>2</sub> when the appropriate toolbar button on the Dive Profile
-has been checked.</p></div>
-<div class="imageblock" style="text-align:center;">
-<div class="content">
-<img src="images/CCR_preferences_f20.jpg" alt="FIGURE: CCR preferences panel" />
-</div>
-</div>
-<div class="paragraph"><p>Checking any of these boxes allows the display of additional oxygen-related
-information whenever the pO<sub>2</sub> toolbar button on the <em>Profile</em> panel is activated.
-The first checkbox allows the display of setpoint information. This is a red line
-superimposed on the green oxygen partial pressure graph and allows a comparison of the
-mean measured oxygen partial pressure and the setpoint values, as shown below.</p></div>
-<div class="imageblock" style="text-align:center;">
-<div class="content">
-<img src="images/CCR_setpoint_f20.jpg" alt="FIGURE: CCR setpoint and po2 graph" />
-</div>
-</div>
-<div class="paragraph"><p>The second checkbox allows the display of the data from each individual oxygen sensor
-of the CCR equipment. The data for each sensor is colour-coded as follows:</p></div>
-<div class="ulist"><ul>
-<li>
-<p>
-Sensor 1: grey
-</p>
-</li>
-<li>
-<p>
-Sensor 2: blue
-</p>
-</li>
-<li>
-<p>
-Sensor 3: brown
-</p>
-</li>
-</ul></div>
-<div class="paragraph"><p>The mean oxygen pO<sub>2</sub> is indicated by the green line. This allows the direct comparison
-of data from each of the oxygen sensors, useful for detecting abnormally low or erratic
-readings from a particular sensor.</p></div>
-<div class="imageblock" style="text-align:center;">
-<div class="content">
-<img src="images/CCR_sensor_data_f20.jpg" alt="FIGURE: CCR sensor data graph" />
-</div>
-</div>
-<div class="paragraph"><p>The setpoint data can be overlaid on the oxygen sensor data by activating both of the above
-check boxes. Partial pressures for nitrogen (and helium, if applicable) are shown in the
-usual way as for open circuit dives.</p></div>
-<div class="paragraph"><p><em>Events</em>: Several events are logged, e.g. switching the mouthpiece to open circuit.
-These events are indicated by yellow triangles and, if one hovers over a triangle,
-a description of that event is given as the bottom line in the <a href="#S_InfoBox">Information Box</a>.</p></div>
-<div class="paragraph"><p><em>Cylinder pressures</em>: Some CCR dive computers like the Poseidon MkVI record the
-pressures of the oxygen and diluent cylinders. The pressures of these two cylinders
-are shown as green lines overlapping the depth profile. In addition, start and
-end pressures for both oxygen and diluent cylinders are shown in the <em>Equipment Tab</em>.
-Below is a dive profile for a CCR dive, including an overlay
-of setpoint and oxygen sensor data, as well as the cylinder pressure data. In this
-case there is agreement from the readings of the two oxygen sensors.</p></div>
-<div class="imageblock" style="text-align:center;">
-<div class="content">
-<img src="images/CCR_dive_profile_f22.jpg" alt="FIGURE: CCR dive profile" />
-</div>
-</div>
-<div class="paragraph"><p><em>Equipment-specific information</em>: Equipment-specific information gathered by
-<em>Subsurface</em> is shown in the <a href="#S_ExtraDataTab">Extra data tab</a>. This may include setup information
-or metadata about the dive.</p></div>
-<div class="paragraph"><p>The deco ceiling calculated by Subsurface is not very accurate because the precise pressure of nitrogen
-in the loop can usually not be determined from the dive log imported from the CCR equipment. Many CCR dive
-computers, however, report an internally-calculated deco ceiling that is reported in the dive log,
-reflecting a more accurate assessment. The display of this ceiling is activated
-by clicking the appropriate button to the left of the dive profile:</p></div>
-<div class="imageblock">
-<div class="content">
-<img src="images/icons/cceiling.jpg" alt="DC ceiling icon" />
-</div>
-</div>
-<div class="paragraph"><p>The default color of the computer-generated deco ceiling is white. This can be set to red
-by checking the appropriate check box after selecting <em>File → Preferences → Graph</em>.
-Below is a dive profile indicating the dive computer-generated deco ceiling:</p></div>
-<div class="imageblock" style="text-align:center;">
-<div class="content">
-<img src="images/CCR_dive_ceilingF22.jpg" alt="FIGURE: CCR computer-generated deco ceiling" />
-</div>
-</div>
-<div class="paragraph"><p>More equipment-specific information for downloading CCR dive logs for
-Poseidon MkVI and APD equipment can be found in <a href="#_appendix_b_dive_computer_specific_information_for_importing_dive_information">Appendix B</a>.</p></div>
-</div>
-</div>
-</div>
-</div>
-</div>
-<div class="sect1">
-<h2 id="_obtaining_more_information_about_dives_entered_into_the_logbook">6. Obtaining more information about dives entered into the logbook</h2>
-<div class="sectionbody">
-<div class="sect2">
-<h3 id="_the_strong_info_strong_tab_for_individual_dives">6.1. The <strong>Info</strong> tab (for individual dives)</h3>
-<div class="paragraph"><p>The 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 F</a> for more information.</td>
-</tr></table>
-</div>
-</div>
-<div class="sect2">
-<h3 id="S_ExtraDataTab">6.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">6.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 for 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">6.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 lets you control 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
-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 colors:</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>Color</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">> 30</p></td>
-<td align="left" valign="top"><p class="table">> 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">< 1.5</p></td>
-<td align="left" valign="top"><p class="table">< 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.
-So users should see the depth of the deepest point and other peaks. Mean depth
-is plotted as a grey line, indicating mean dive depth up to a particular moment during the dive.</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
-increases the size of the dive profile to fill the area of the panel.</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 O<sub>2</sub>, N<sub>2</sub>, 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, nitrogen in black,
-and 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 shown 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 important 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.
-Like the depth graph, the slope of the tank pressure gives you information
-about the
-momentary SAC rate (Surface Air Consumption) when using an air integrated dive computer.
-Here the color
-coding is not relative to some absolute values but relative to the average
-normalized 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 easily recognizable;
-something free divers won’t care about.
-<span class="image">
-<img src=":images/MeasuringBar.png" alt="FIGURE: Measuring Bar" />
-</span></p></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 you wish 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
-shows 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
-occur 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 none of the Suunto dive computers make these 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’s 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’s 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 because <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 a specific deco stop. This feature lets dive computers 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 colored bar at the bottom
-of the <strong>Dive Profile</strong>. In general oxygen is represented by a green bar, nitrogen a yellow bar and helium 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 doing planned decompression diving, efficient rates of offgassing 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 contrast, 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, at 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">6.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 lets you create
-Bookmarks, 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,
-with the time of the event set by where the mouse cursor was when the right
-mouse button was first clicked to bring up the menu. Gas Change events
-involve a selection of which gas is being switched TO. The list of choices is based on
-the available gases defined in the <strong>Equipment</strong> Tab. Setpoint change
-events open a dialog letting you choose the next setpoint value. As
-in the planner, a setpoint value of zero shows the diver is
-breathing from an open circuit system while any non-zero value
-shows 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="S_InfoBox">6.6. The <strong>Information Box</strong></h3>
-<div class="paragraph"><p>The Information box displays a large range of information about 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>When 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 shown 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). Moving the cursor horizontally lets the Information Box 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 some statistics, shown 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 if a maximum pO<sub>2</sub> of 1.4 is specified in the <strong>Preferences</strong> section
-(select <em>File</em> → Preferences → Graph_ and edit the text box <em>Max pO<sub>2</sub> when showing MOD</em>.
-Below the MOD there is a markedly increased
-risk of exposure to the dangers of 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 either 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 a diver 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. TTS is calculated assuming an ascent surface air consumption (SAC) for
-the gas currently used. Even if the profile contains several gas
-switches, TTS at a specific moment during the dive is calculated using the current gas.
-TTS longer than 2 hours is not accurately calculated and Subsurface only indicates <em>TTS > 2h</em>.</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-normalized 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 the respiratory rates of different dives
-can be compared. The units for SAC is liters/min or cubic 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
-important to divers breathe 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">6.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 showing 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>. It is shown 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="ulist"><ul>
-<li>
-<p>
-The light green area indicates the total gas, with the top margin of the light green
- area showing 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>
-</li>
-<li>
-<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>
-</li>
-<li>
-<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>
-</li>
-<li>
-<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 gradient factor shown is an
- interpolation between the GFLow and GFHigh values specified in the Graph tab of the <strong>Preferences
- Panel</strong> of <strong>Subsurface</strong>.
-</p>
-</li>
-<li>
-<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>
-</li>
-</ul></div>
-<div class="paragraph"><p>These five values are shown on the left in the graph above. The way the Gas Pressure Bar Graph changes
-during a dive can be seen on the right hand side of the above figure for a diver using EAN32.</p></div>
-<div class="ulist"><ul>
-<li>
-<p>
-Graph <strong>A</strong> indicates the start of a dive with the diver at the surface. The pressures in all
- the tissue compartments are still at the equilibrium pressure because no diving has taken place.
-</p>
-</li>
-<li>
-<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, so their gas pressures are far below the equilibrium gas pressure.
-</p>
-</li>
-<li>
-<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>
-</li>
-<li>
-<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 approach 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>
-</li>
-<li>
-<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>
-</li>
-</ul></div>
-</div>
-</div>
-</div>
-</div>
-<div class="sect1">
-<h2 id="_organizing_the_logbook_manipulating_groups_of_dives">7. Organizing the logbook (Manipulating groups of dives)</h2>
-<div class="sectionbody">
-<div class="sect2">
-<h3 id="_the_dive_list_context_menu">7.1. The Dive List context menu</h3>
-<div class="paragraph"><p>Several actions on either a single dive, or a group of dives, can be performed using the Dive List
-Context Menu. It is found by selecting either a single 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 functions described below.</p></div>
-<div class="sect3">
-<h4 id="_customizing_the_columns_showed_in_the_strong_dive_list_strong_panel">7.1.1. Customizing the columns 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 be
-deleted (reflected by the check symbols) and the list is immediately updated. Preferences for information
-shown in the <strong>Dive List</strong> are saved and used when <em>Subsurface</em> is re-opened.</p></div>
-</div>
-</div>
-<div class="sect2">
-<h3 id="S_Renumber">7.2. Renumbering the dives</h3>
-<div class="paragraph"><p>Dives are normally numbered incrementally from non-recent dives (low sequence
-numbers) to recent dives (higher sequence numbers). Numbering
-of dives is not always consistent. For instance, when non-recent dives are
-added, correct 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. So you may need to renumber the dives.
-Do this by selecting (from the Main Menu) <em>Log → Renumber</em>. Users are
-given a choice of the lowest sequence number to be used.
-This results in new sequence numbers (based on date/time)
-for the dives in the <strong>Dive List</strong> panel.</p></div>
-<div class="paragraph"><p>You can also renumber a few selected dives in the dive list. Select the dives that
-need renumbering. Right-click on the selected list and use the Dive List Context Menu
-to perform the renumbering. A popup window appears letting the user specify
-the starting number for the process.</p></div>
-</div>
-<div class="sect2">
-<h3 id="S_Group">7.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 does this by grouping dives that have
-date/times not separated in time by more than two days, so 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 of 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. To group the dives in a dive list,
-(from the Main Menu) select <em>Log → 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">7.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>Notes</strong> panel. Here
-you 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 used, the general weather and surface conditions during the trip, etc.).
-After entering this
-information, 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 the
-edited information.</p></div>
-</div>
-<div class="sect3">
-<h4 id="_viewing_the_dives_during_a_particular_trip">7.3.2. Viewing the dives during a particular trip</h4>
-<div class="paragraph"><p>Once the dives have been grouped into trips, you can expand one or more
-trips by clicking the arrow-head on the left of each trip title. This expands
-the selected trip, revealing individual dives done during the trip.</p></div>
-</div>
-<div class="sect3">
-<h4 id="_collapsing_or_expanding_dive_information_for_different_trips">7.3.3. Collapsing or expanding dive information for different trips</h4>
-<div class="paragraph"><p>After selecting a particular trip in the dive list, the
-context menu allows several options to expand or collapse dives
-within trips. This includes expanding all trips and collapsing all trips.</p></div>
-</div>
-<div class="sect3">
-<h4 id="_merging_dives_from_more_than_one_trip_into_a_single_trip">7.3.4. Merging dives from more than one trip into a single trip</h4>
-<div class="paragraph"><p>After selecting a trip title, the context menu allows the merging
-of trips by either merging the selected trip with the trip below or with the
-trip above. (Merge trip with trip below; Merge trip with trip above)</p></div>
-</div>
-<div class="sect3">
-<h4 id="_splitting_a_single_trip_into_more_than_one_trip">7.3.5. Splitting a single trip into more than one trip</h4>
-<div class="paragraph"><p>If a trip includes ten dives, you can split this trip into two trips (trip 1:
-top 4 dives; trip 2: bottom 6 dives) by selecting and right-clicking the top
-four dives. The resulting context menu lets the user create a new trip by
-choosing the option <strong>Create new trip above</strong>. The top four dives are then
-grouped
-into a separate trip. The figures below show 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">7.4. Manipulating single dives</h3>
-<div class="sect3">
-<h4 id="_delete_a_dive_from_the_dive_log">7.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, 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">7.4.2. Unlink a dive from a trip</h4>
-<div class="paragraph"><p>You can unlink dives from the trip to which they belong. 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 or below the trip to
-which they belonged, depending on the date and time of the unlinked dive.</p></div>
-</div>
-<div class="sect3">
-<h4 id="_add_a_dive_to_the_trip_immediately_above">7.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
-a separate trip. To do this, select and right-click
-the dive(s) to bring up the context menu, and then select <strong>Create new trip above</strong>.</p></div>
-</div>
-<div class="sect3">
-<h4 id="_shift_the_start_time_of_dive_s">7.4.4. Shift the start time of dive(s)</h4>
-<div class="paragraph"><p>Sometimes it’s necessary to adjust the start time of a dive. This may apply to
-situations where dives are done in different time zones or when the dive
-computer has a wrong time. To do this, select and right-click
-the dive(s) to be
-adjusted. This brings up the context menu on which the <strong>Shift times</strong>
-option should be selected. You must then specify the
-time
-(in hours and minutes) by which the dives should be adjusted and click on the
-option of whether the time adjustment should be earlier or later.</p></div>
-</div>
-<div class="sect3">
-<h4 id="_merge_dives_into_a_single_dive">7.4.5. Merge dives into a single dive</h4>
-<div class="paragraph"><p>Sometimes a dive is briefly interrupted, for example, if a diver returns to the surface
-for a few minutes. That results in two or more dives being recorded by the dive
-computer and appearing as different dives in the <strong>Dive List</strong> panel. You 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>Notes</strong>
-panel to reflect events or conditions that apply to the merged dive. The figure
-below shows the depth profile of two 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 class="sect3">
-<h4 id="_undo_dive_manipulations">7.4.6. Undo dive manipulations</h4>
-<div class="paragraph"><p>Important actions on dives or trips, described above, can be undone or redone.
-This includes: <em>delete dives</em>, <em>merge dives</em>, <em>renumber dives</em> and <em>shift dive times</em>.
-To do this after performing any of these actions, from the <strong>Main Menu</strong> select
-<em>Edit</em>. This brings up the possibility to <em>Undo</em> or <em>Redo</em> an action.</p></div>
-</div>
-</div>
-<div class="sect2">
-<h3 id="S_Filter">7.5. Filtering the dive list</h3>
-<div class="paragraph"><p>The dives in the <strong>Dive List</strong> panel can be filtered, so you 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 lets you 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 → 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 (see image below). The <em>Filter Panel</em> can be reset
-(i.e. all current filters cleared) by selecting the <strong>yellow angled arrow</strong>. The <em>Filter Panel</em> may also be
-minimized by selecting the <strong>green up-arrow". When minimized, only these three icons are shown.
-The panel can be maximized by clicking the same icon that minimized it. The filter may also be
-reset and closed by selecting the *red button</strong> with the white cross.</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 / divemaster), dive site
-and dive suit. Each of these 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
-attributes within that check list. For instance, typing "<em>ca</em>" in the filter
-text box above the tags check list, results in the list being reduced
-to "<em>cave</em>" and "<em>cavern</em>". Filtering the check list helps to rapidly find
-search terms for filtering the dive list.</p></div>
-<div class="paragraph"><p>To activate filtering of the dive list, check at least one check box in one of
-the four check lists. The dive list is then shortened to include
-only the dives that pertain to the 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">8. Exporting the dive log or parts of the dive log</h2>
-<div class="sectionbody">
-<div class="paragraph"><p>There are two ways to export dive information from Subsurface:</p></div>
-<div class="ulist"><ul>
-<li>
-<p>
-Export dive information to <em>Facebook</em>
-</p>
-</li>
-<li>
-<p>
-<a href="#S_Export_other">Export dive information to other destinations or formats</a>
-</p>
-</li>
-</ul></div>
-<div class="sect2">
-<h3 id="S_facebook">8.1. Exporting dive information to <em>Facebook</em></h3>
-<div class="paragraph"><p>Export of dives to <em>Facebook</em> is handled differently from other types of export because
-a connection to <em>Facebook</em> is required, needing a <em>Facebook</em> userID and password.
-If, from the <strong>Main Menu</strong>, you select <em>File → Preferences → Facebook</em>, a login screen comes up.
-(image <strong>A</strong> to the left, below). Provide a <em>Facebook</em> userID and password.
-Once logged into to <em>Facebook</em> , the panel
-in image <strong>B</strong>, below is shown, including a <em>Disconnect from Facebook</em> button to close the
-<em>Facebook</em> connection.</p></div>
-<div class="imageblock" style="text-align:center;">
-<div class="content">
-<img src="images/facebook1_f20.jpg" alt="Figure: Facebook login" />
-</div>
-</div>
-<div class="paragraph"><p>From the <em>Subsurface</em> window it’s easy to determine whether <em>Subsurface</em> has a valid connection to <em>Facebook</em>
-From the <strong>Main Menu</strong>, select <em>Share on → Facebook</em> (image <strong>A</strong>, below). Normally, the <em>Facebook</em> option is greyed out. But
-if there is a connection to <em>Facebook</em>, this option is active (i.e. in black color and can be selected).</p></div>
-<div class="paragraph"><p>Having established a login to <em>Facebook</em>, transferring a dive profileto a <em>Facebook</em> timeline is easy.
-Be sure the dive to be transferred to the timeline is shown in the <em>Subsurface</em> <strong>Dive Profile</strong> panel. If, from the <strong>Main Menu</strong>, you
-select <em>Share on → Facebook</em> (see image <strong>A</strong> below), a dialogue box is shown, determining the amount of additional information transferred along
-with the dive profile (image <strong>B</strong>, below). To transfer a dive profile to <em>Facebook</em>, the name of a
-<em>Facebook</em> album is needed. The checkboxes on the left hand side let you decide how much
-additional information should be transferred with the dive profile. This information is shown in the text box
-on the right hand side of the panel (image <strong>B</strong>, below). You can easily edit the message that will be posted
-with the dive profile. After specifying the additional information and verifying the text, select
-the <em>OK</em> button that triggers the transfer to <em>Facebook</em>. After the transfer
-is done, an acknowledgement dialogue appears, indicating it was successful.</p></div>
-<div class="paragraph"><p>Both the album created and the post to your timeline will be marked as
-private. In order for friends to be able to see it,
-change its permissions from a regular Facebook login either in a
-browser or a Facebook app.</p></div>
-<div class="imageblock" style="text-align:center;">
-<div class="content">
-<img src="images/facebook2_f20.jpg" alt="Figure: Facebook login" />
-</div>
-</div>
-<div class="paragraph"><p>If required, then close the <em>Facebook</em> connection by either closing <em>Subsurface</em> or by selecting <em>File → Preferences → Facebook</em> from
-the Main Menu, and clicking the appropriate button on the Facebook Preferences panel.</p></div>
-</div>
-<div class="sect2">
-<h3 id="S_Export_other">8.2. Export dive information to other destinations or formats</h3>
-<div class="paragraph"><p>For non-<em>Facebook exports</em>, the export function can be found by selecting <em>File → 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_f20.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>
-<li>
-<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>
-</li>
-<li>
-<p>
-<em>Divelogs.de</em>, an Internet-based dive log repository. In order to upload to <em>Divelogs.de</em>,
- you need 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 to upload dive log data from <em>Subsurface</em>.
-</p>
-</li>
-<li>
-<p>
-<em>DiveShare</em> is also a dive log repository on the Internet focusing on recreational
- dives. To upload dives, you need a user ID, so registration with
- <em>http://scubadiveshare.com</em> is required.
-</p>
-</li>
-<li>
-<p>
-<em>CSV dive details</em>, that includes the most critical information of the dive
- profile. Included information of a dive is: dive number, date, time, buddy,
- duration, depth, temperature and pressure: in short, most of the information
- that recreational divers enter into handwritten log books.
-</p>
-</li>
-<li>
-<p>
-<em>CSV dive profile</em>, that includes a large amount of detail for each dive, including
- the depth profile, temperature and pressure information of each dive.
-</p>
-</li>
-<li>
-<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. The HTML export cannot be changed or edited.
- It contains most of the information recorded in the dive log. However, it does not show the
- calculated values in the <strong>Dive Profile</strong> panel, e.g. calculated cylinder pressure, gas
- pressures and MOD. The HTML export 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). A typical use of this option is to export all one’s
- dives to a smartphone or a tablet where it would serve as a portable record
- of dives. That is useful for dive companies that wish to verify the dive history of a diver,
- often doing away with the need to carry an original logbook
- when doing dives with dive companies.
-</p>
-</li>
-<li>
-<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. If you select any
- of the dive sites on the map, a summary of the dive is available in text, as shown
- in the image below.
-</p>
-</li>
-</ul></div>
-<div class="imageblock" style="text-align:center;">
-<div class="content">
-<img src="images/mapview_f20.jpg" alt="Figure: HTML Map export view" />
-</div>
-</div>
-<div class="ulist"><ul>
-<li>
-<p>
-<em>Image depths</em>, which creates a text file that contains the file names of all
- photos or images attached
- to any of the selected dives in the <em>Dive List</em>, together with the depth underwater where
- of each of those photos was taken.
-</p>
-</li>
-<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 to the HTML exports.
-</p>
-</li>
-<li>
-<p>
-Export List only: a list of dives only (date, time, depth, duration) will be exported
- and the detailed dive information, e.g. dive profile, will not be available.
-</p>
-</li>
-</ul></div>
-</li>
-<li>
-<p>
-Under <em>Style Options</em> some style-related options are available like font
- size and theme.
-</p>
-</li>
-</ul></div>
-<div class="paragraph"><p>Export to other formats can be done through third party facilities, for
-instance <em>www.divelogs.de</em>.</p></div>
-</div>
-</div>
-</div>
-<div class="sect1">
-<h2 id="S_Cloud_access">9. 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’s own pleasure, but it’s important information required
-for admission to training courses or sometimes even diving sites. The
-security of the dive log is critical. 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 you can access your dive
-log from anywhere in the world. For this reason, facilities such as <em>divelogs.de</em> and <em>Diving Log</em> offer to store
-dive log information on the Internet.</p></div>
-<div class="paragraph"><p><em>Subsurface</em> includes access to a transparently integrated cloud storage
-back end that is available to all Subsurface users. Storing and retrieving a dive log
-from the cloud is no more difficult than accessing the dives on the local hard disk.
-The only requirement is that you should first register as a user on the cloud.
-To use <em>Subsurface cloud storage</em> , follow these steps:</p></div>
-<div class="sect2">
-<h3 id="_create_a_cloud_storage_account">9.1. Create a cloud storage account</h3>
-<div class="ulist"><ul>
-<li>
-<p>
-Open the <strong>Network Preferences</strong> by selecting <em>File</em> → <em>Preferences</em> → <em>Network</em>.
-</p>
-</li>
-<li>
-<p>
-In the section headed <em>Subsurface cloud storage</em>, enter an email address that
- <em>Subsurface</em> can use for user registration.
-</p>
-</li>
-<li>
-<p>
-Enter a novel password that <em>Subsurface</em> will use to store the
- dive log in the cloud.
-</p>
-</li>
-<li>
-<p>
-Click <em>Apply</em> to send the above email address and password to the
- (remote) cloud server. The server responds by sending a verification PIN to
- the above email address (This is the <strong>only</strong> occasion that <em>Subsurface</em> uses the
- email address provided above). The <strong>Network Preferences</strong> dialog now has a new PIN text
- box, not visible previously.
-</p>
-</li>
-<li>
-<p>
-Enter the PIN in the corresponding text box in the <strong>Network Preferences</strong> dialog
-(this field is only visible while the server is waiting for email
-address confirmation)
-</p>
-</li>
-<li>
-<p>
-Click <em>Apply</em> again. The <em>Subsurface cloud storage</em> account
-will be marked as verified and the <em>Subsurface cloud storage</em> service is initialised for use.
-</p>
-</li>
-</ul></div>
-</div>
-<div class="sect2">
-<h3 id="_using_em_subsurface_cloud_storage_em">9.2. Using <em>Subsurface cloud storage</em></h3>
-<div class="ulist"><ul>
-<li>
-<p>
-Once the cloud storage has been initialized, two new items appear in the
- <em>File</em> menu of the main menu system: <em>Open cloud storage</em> and <em>Save to cloud storage</em>.
-These options let you load and save data to the <em>Subsurface
-cloud storage</em> server.
-</p>
-</li>
-<li>
-<p>
-In the <em>Defaults Preferences</em> tab, you can select to use the <em>Subsurface cloud
-storage</em> data as the default data file by checking the box marked <em>Cloud storage default file</em>.
- This means the data from
-the <em>Subsurface cloud storage</em> is loaded when <em>Subsurface</em> starts and saved there when <em>Subsurface</em> closes.
-</p>
-</li>
-<li>
-<p>
-<em>Subsurface</em> keeps a local copy of the data and the cloud facility remains fully
-functional even if used while disconnected to the Internet. <em>Subsurface</em> simply synchronizes the
-data with the cloud server the next time the program is used while the computer is
-connected to the Internet.
-</p>
-</li>
-</ul></div>
-</div>
-<div class="sect2">
-<h3 id="S_Cloud_storage">9.3. Web access to <em>Subsurface cloud storage</em></h3>
-<div class="paragraph"><p>One of the nice side benefits of using <em>Subsurface cloud storage</em> is that
-you can also access your dive data from any web browser. Simply open
-<a href="https://cloud.subsurface-divelog.org"><em>https://cloud.subsurface-divelog.org</em></a>,
-log in with the same email and password, and you can see an HTML export of
-the last dive data that was synced to <em>Subsurface cloud storage</em>. The dive information
-shown is only the contents of the recorded dive logs, NOT the calculated values
-shown in the <strong>Profile</strong> panel,
-including some cylinder pressures, deco ceilings and O<sub>2</sub>/He/N<sub>2</sub> partial pressures.</p></div>
-</div>
-<div class="sect2">
-<h3 id="_other_cloud_services">9.4. Other cloud services</h3>
-<div class="paragraph"><p>If you prefers not to use the integrated cloud storage of dive logs (and
-don’t need the web access), it’s simple to store
-dive logs in the cloud using several of the existing facilities on the
-Internet.
-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 a 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 your
-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’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
-your <em>Dropbox</em> folder can be accessed seamlessly from the Internet and can
-be accessed anywhere 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 you can use <em>Dropbox</em> as a way back up your dive log. To
-Store a dive log on <em>Dropbox</em>, select <em>File → 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 <em>Dropbox</em>, select <em>File → 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>
-<div class="sect1">
-<h2 id="S_PrintDivelog">10. Printing a dive log</h2>
-<div class="sectionbody">
-<div class="paragraph"><p><em>Subsurface</em> provides a simple and flexible way to print a whole dive log or only a few selected dives.
- Pre-installed templates or a custom written template can be used to choose where the data are fitted into the page.</p></div>
-<div class="paragraph"><p>Some decisions need to be made before printing:</p></div>
-<div class="ulist"><ul>
-<li>
-<p>
-Should the whole dive log be printed or only part of it? If only part
- is required, select the required dives from the <strong>Dive List</strong> panel.
-</p>
-</li>
-<li>
-<p>
-If the dive profiles are printed, what gas partial pressure information should be shown? Select
- the appropriate toggle-buttons on the button bar to the left of the <strong>Dive Profile</strong> panel.
-</p>
-</li>
-</ul></div>
-<div class="paragraph"><p>If <em>File → Print</em> is selected from the Main menu, the dialogue below (image <strong>A</strong>) appears. Three
-specifications are needed to get the desired information and page layout:</p></div>
-<div class="imageblock" style="text-align:center;">
-<div class="content">
-<img src="images/Print1_f22.jpg" alt="FIGURE: Print dialogue" />
-</div>
-</div>
-<div class="olist arabic"><ol class="arabic">
-<li>
-<p>
-Under <em>Print type</em> select one of two options:
-</p>
-<div class="ulist"><ul>
-<li>
-<p>
-<em>Dive list print</em>: Print dives from the <strong>Dive List</strong> panel with profiles and other information.
-</p>
-</li>
-<li>
-<p>
-<em>Statistics print</em>: Print yearly statistics of the dives.
-</p>
-</li>
-</ul></div>
-</li>
-<li>
-<p>
-Under <em>Print options</em> select:
-</p>
-<div class="ulist"><ul>
-<li>
-<p>
-Printing only the dives selected from the dive list before
- activating the print dialogue by checking the box <em>Print only
- selected dives</em>. If this check box is <strong>not</strong> checked ALL dives in
- the <strong>Dive List</strong> panel are printed.
-</p>
-</li>
-<li>
-<p>
-Printing in color, done by checking the box with _Print in color. If this check box
- is not checked, printing is in black and white.
-</p>
-</li>
-</ul></div>
-</li>
-<li>
-<p>
-Under <em>Template</em> select a template to be used as the page layout. There are several choices.
-(see image <strong>B</strong>, above).
-</p>
-<div class="ulist"><ul>
-<li>
-<p>
-<em>Table</em>: This prints a summary table of all dives selected (see below).
-</p>
-</li>
-</ul></div>
-</li>
-</ol></div>
-<div class="imageblock" style="text-align:center;">
-<div class="content">
-<img src="images/Print_summarylist_f22.jpg" alt="FIGURE: Print summary table" />
-</div>
-</div>
-<div class="ulist"><ul>
-<li>
-<p>
-<em>Flow layout</em>: Print the text associated with each dive without printing the dive profiles
- of each dive (see below):
-</p>
-</li>
-</ul></div>
-<div class="imageblock" style="text-align:center;">
-<div class="content">
-<img src="images/Print_flow_layout_f22.jpg" alt="FIGURE: Print flow layout" />
-</div>
-</div>
-<div class="ulist"><ul>
-<li>
-<p>
-<em>One Dive</em>: Print one dive per page, also showing the dive profile (see below)
-</p>
-</li>
-</ul></div>
-<div class="imageblock" style="text-align:center;">
-<div class="content">
-<img src="images/print2_f22.jpg" alt="FIGURE: Print one dive / page" />
-</div>
-</div>
-<div class="ulist"><ul>
-<li>
-<p>
-<em>Two Dives</em>: Print two dives per page, also showing the dive profiles.
-</p>
-</li>
-<li>
-<p>
-<em>Six Dives</em>: Print six dives per page, also showing the dive profiles.
-</p>
-</li>
-</ul></div>
-<div class="paragraph"><p>You can <em>Preview</em> the printed page by selecting the <em>Preview</em> button on the
-dialogue (see image <strong>A</strong> at the start of this section). After preview, you can change
-the options in the print dialogue, so the layout fits personal taste.</p></div>
-<div class="paragraph"><p>Next, select the <em>Print</em> button (see image <strong>A</strong> at the start of this section). This activates the regular print
-dialogue used by the operating system,
-letting you choose a printer and set its properties (see image below):</p></div>
-<div class="imageblock" style="text-align:center;">
-<div class="content">
-<img src="images/Print_print_f22.jpg" alt="FIGURE: Print dialog" />
-</div>
-</div>
-<div class="paragraph"><p>Set the print resolution of the printer to an appropriate value by changing
-the printer <em>Properties</em>. Finally, select the <em>Print</em> button to 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 class="sect2">
-<h3 id="_writing_a_custom_print_template_advanced">10.1. Writing a custom print template (advanced)</h3>
-<div class="paragraph"><p>Writing a custom template is an effective way to produce highly customized printouts. Subsurface uses HTML templates
-to render printing. You can create a template, export a new template, import an existing template and delete an existing template by using
-the appropriate buttons under the <em>Template</em> dropdown list in the print dialogue. See <a href="#S_APPENDIX_E">APPENDIX E</a> for information on how
-to write or modify a template.</p></div>
-</div>
-</div>
-</div>
-<div class="sect1">
-<h2 id="S_Configure">11. Configuring a dive computer</h2>
-<div class="sectionbody">
-<div class="paragraph"><p><em>Subsurface</em> lets you 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. To begin, be sure the appropriate hardware driver
-is installed for the dive computer (also required for downloading dives) and 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 → 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 and select the appropriate dive
-computer model from the panel on the left-hand (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 done:</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 it 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="S_Preferences">12. Setting user <em>Preferences</em> for <em>Subsurface</em></h2>
-<div class="sectionbody">
-<div class="paragraph"><p>There are several user-definable settings within <em>Subsurface</em>, found by selecting
-<em>File → Preferences</em>. The settings are in
-seven groups: <strong>Defaults</strong>, <strong>Units</strong>, <strong>Graph</strong>, <strong>Language</strong> and <strong>Network</strong>, <strong>Facebook</strong> and <strong>Georeference</strong>.
-All operate on the same principles: the user must specify settings that are to be changed, then
-save them using the <strong>Apply</strong> button. After applying all the new settings users can then
-leave the settings panel by selecting <strong>OK</strong>. If <strong>Discard</strong> is selected, changes to the preferences
-are not saved.</p></div>
-<div class="sect2">
-<h3 id="_defaults">12.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_f20.jpg" alt="FIGURE: Preferences defaults page" />
-</div>
-</div>
-<div class="ulist"><ul>
-<li>
-<p>
-<strong>Lists and tables</strong>: Here you 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>, you can see more dives on a screen.
-</p>
-</li>
-<li>
-<p>
-<strong>Dives</strong>: For the <em>Default Dive File</em> you need to specify the directory and
- file name of your
- electronic dive log book. This is a file with filename extension of either <em>.xml</em> or <em>.ssrf</em>. When
- launched, <em>Subsurface</em> will automatically load the specified dive log book. There are three options:
-</p>
-<div class="ulist"><ul>
-<li>
-<p>
-<em>No default file</em>: When checked, <em>Subsurface</em> does not automatically load a dive log at startup.
-</p>
-</li>
-<li>
-<p>
-<em>Local default file</em>: When checked, <em>Subsurface</em> automatically loads a dive log from the local hard disk
- as described above.
-</p>
-</li>
-<li>
-<p>
-<em>Cloud storage default file</em>: When checked, <em>Subsurface automatically loads the dive log from the cloud
- device that was initialized using the <strong>Preferences</strong> _Network</em> tab (see below).
-</p>
-</li>
-</ul></div>
-</li>
-<li>
-<p>
-<strong>Display invalid</strong>: Dives can be marked as invalid (when a user wishes to hide
- dives that he/she doesn’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>: Specify the default cylinder listed in
- the <strong>Equipment</strong> tab of the <strong>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, and a 0 value representing no animation
- at all.
-</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">12.2. Units</h3>
-<div class="imageblock" style="text-align:center;">
-<div class="content">
-<img src="images/Pref2_f20.jpg" alt="FIGURE: Preferences Units page" />
-</div>
-</div>
-<div class="paragraph"><p>Here you 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, you can specify that all units are in the chosen measurement system.
-Alternatively, if you select the <strong>Personalize</strong> radio button, units can be selected
-independently, with some in the metric system and others in imperial.</p></div>
-<div class="paragraph"><p>Regardless
-of the above settings, dive time measurements can be either in seconds or minutes.
-Choose the appropriate option. GPS coordinates can be represented either as
-traditional coordinates (degrees, minutes, seconds) or as decimal degrees
-Choose the appropriate option.</p></div>
-</div>
-<div class="sect2">
-<h3 id="_graph">12.3. Graph</h3>
-<div class="imageblock" id="S_CCR_options" style="text-align:center;">
-<div class="content">
-<img src="images/Pref3_f20.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="ulist"><ul>
-<li>
-<p>
-<strong>Show</strong>: Here you can specify the amount of information shown as part of
- the dive profile:
-</p>
-<div class="ulist"><ul>
-<li>
-<p>
-Thresholds: <em>Subsurface</em> can display the nitrogen, oxygen and the helium partial pressures during
- the dive, done by using the toolbar on the left hand side of the <strong>Dive Profile</strong>
- panel. For each of these graphs you can specify a threshold value on the right-hand side of the
- Preferences panel. If any of the graphs go above the specified threshold level, the graph is
- highlighted in red, indicating the particular partial pressure threshold has been exceeded.
-</p>
-</li>
-<li>
-<p>
-_Max pO<sub>2</sub> is used for calculating the MOD when displaying the maximum operative depth (MOD)
- for a dive. Specify an appropriate partial pressure. A value of 1.4 is commonly used.
-</p>
-</li>
-<li>
-<p>
-<em>Draw dive computer reported ceiling red</em>: This checkbox does exactly what it says. By default
- the computer reported ceiling is shown in white.
- 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> because of the different algorithms and
- gradient factors, as well as the dynamic way a
- dive computer calculates 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>. If this box is not checked, and if 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>: If this box is checked, the <strong>Dive Profile</strong> panel contains a grey line that shows
- the mean depth of the dive, up to any time instant during the dive. Normally this is a u-shaped line indicating the deepest mean depth just before
- ascent.
-</p>
-</li>
-</ul></div>
-</li>
-<li>
-<p>
-<strong>Misc</strong>:
-</p>
-<div class="ulist" id="GradientFactors_Ref"><ul>
-<li>
-<p>
-Gradient Factors (GFLow and GFHigh):* 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 nitrogen exposure during a dive, in a
- similar way that many dive computers have a conservative 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 70/90 are considered
- harsh. Checking the <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>
-<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>
-</li>
-<li>
-<p>
-<em>CCR: Show setpoints when viewing pO2:</em> With this checkbox activated, the pO<sub>2</sub>
- graph on the dive profile has an overlay in red which indicates the CCR setpoint
- values. See the section on <a href="#S_CCR_dives">Closed Circuit Rebreather dives</a>.
-</p>
-</li>
-<li>
-<p>
-<em>CCR: Show individual O<sub>2</sub> sensor values when viewing pO<sub>2</sub>:</em> Show the pO<sub>2</sub>
- values associated with each of the individual oxygen sensors of a CCR system.
- See the section on <a href="#S_CCR_dives">Closed Circuit Rebreather dives</a>.
-</p>
-</li>
-</ul></div>
-</li>
-<li>
-<p>
-<strong>Configuring dive planning using rebreather equipment:</strong>
-</p>
-<div class="ulist"><ul>
-<li>
-<p>
-<em>Default CCR setpoint for dive planning:</em> Specify the O<sub>2</sub> setpoint for a
- CCR dive plan. This determines the pO<sub>2</sub> maintained
- during a particular dive. Setpoint changes during the dive can be added via the
- profile context menu.
-</p>
-</li>
-<li>
-<p>
-<em>pSCR O<sub>2</sub> metabolism rate:</em> For a semi-closed rebreather (pSCR) system, this is the
- volume of oxygen used by a diver during a minute. Set this value for pSCR dive planning
- and decompression calculations.
-</p>
-</li>
-<li>
-<p>
-<em>pSCR ratio:</em> For pSCR equipment the dump ratio is the ratio of gas released to the
- environment to that of the gas recirculated to the diver. Set this value for a
- pSCR dive plan. A 1:10 ratio is commonly used.
-</p>
-</li>
-</ul></div>
-</li>
-</ul></div>
-</div>
-<div class="sect2">
-<h3 id="_language">12.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_f20.jpg" alt="FIGURE: Preferences Language page" />
-</div>
-</div>
-<div class="paragraph"><p>A checkbox lets you 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 operating system.
-To change it, uncheck this checkbox and pick a language / country
-combination from the list of locations. The <em>Filter</em> text box
-lists similar languages. For instance there are several system variants of English
-or French. <strong>This particular preference requires a restart of <em>Subsurface</em> to take
-effect</strong>.</p></div>
-</div>
-<div class="sect2">
-<h3 id="_network">12.5. Network</h3>
-<div class="paragraph"><p>This panel facilitates communication between <em>Subsurface</em> and data sources on the Internet.
-This is important, for instance, when <em>Subsurface</em> needs to communicate with web
-services such as Cloud storage or the <a href="#S_Companion"><em>Subsurface Companion app</em></a>. These Internet requirements are determined by your type of
-connection to the Internet and by the Internet Service Provider (ISP) used.
-Your ISP should provide the appropriate information.</p></div>
-<div class="imageblock" style="text-align:center;">
-<div class="content">
-<img src="images/Pref5_f20.jpg" alt="FIGURE: Preferences Network page" />
-</div>
-</div>
-<div class="paragraph"><p>This dialogue has three sections:</p></div>
-<div class="ulist"><ul>
-<li>
-<p>
-<em>Proxy type</em>:
-If a proxy server is used for Internet access, 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 are required so that <em>Subsurface</em> can automatically pass
-through the proxy server to access the Internet. This information is usually obtained
-from one’s ISP.
-</p>
-</li>
-<li>
-<p>
-<em>Subsurface cloud storage</em>: To store your dive log in the cloud, a valid email address
- and password are required. This lets <em>Subsurface</em> email security information
- regarding cloud storage to you, and to set up cloud storage appropriately.
- Two additional options are given:
-</p>
-<div class="ulist"><ul>
-<li>
-<p>
-<em>Sync to cloud in the background</em>: This option allows saving of dive information to the cloud storage
- while you do other things within <em>Subsurface</em>.
-</p>
-</li>
-<li>
-<p>
-<em>Save password locally</em>: This allows local storage of the cloud storage password. Note that this
- information is saved in raw text form, not encoded in any way.
-</p>
-</li>
-</ul></div>
-</li>
-<li>
-<p>
-<em>Subsurface web service</em>: When you subscribe 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>, you ensure a local copy of that userID is saved.
-</p>
-</li>
-</ul></div>
-</div>
-<div class="sect2">
-<h3 id="S_Facebook">12.6. Facebook Access</h3>
-<div class="paragraph"><p>This panel lets you log into a Facebook account in order to transfer information
-from Subsurface to Facebook.</p></div>
-<div class="imageblock" style="text-align:center;">
-<div class="content">
-<img src="images/Pref6_f20.jpg" alt="FIGURE: Facebook login panel" />
-</div>
-</div>
-<div class="paragraph"><p>If you provide a valid Facebook userID and password, a
-connection to Facebook is created. That connection is closed when one
-closing down Subsurface. Currently the checkbox labelled "Keep me logged in to Subsurface",
-on the login screen has no effect.
-See the section <a href="#S_facebook">Exporting dive profiles to Facebook</a>
-for more information.</p></div>
-</div>
-<div class="sect2">
-<h3 id="_georeference">12.7. Georeference</h3>
-<div class="paragraph"><p><em>Subsurface</em> provides a geo-lookup service (that is, given the coordinates of a dive site) derived from
-a click on the <strong>Dive Map panel</strong> at the bottom right of the <em>Subsurface</em> window, or from a GPS instrument or
-from the <em>Subsurface</em> Companion app). A search on the Internet is done to find
-the name of the closest known location. This function only works if <em>Subsurface</em> has an
-Internet connection. The preference of the dive site name can be configured, e.g. <em>Country/State/City</em>
-or <em>City/State/Country</em> (see image below).</p></div>
-<div class="imageblock" style="text-align:center;">
-<div class="content">
-<img src="images/Pref7_f20.jpg" alt="FIGURE: Facebook login panel" />
-</div>
-</div>
-</div>
-</div>
-</div>
-<div class="sect1">
-<h2 id="S_DivePlanner">13. The <em>Subsurface</em> dive planner</h2>
-<div class="sectionbody">
-<div class="paragraph"><p>Dive planning is an advanced feature of <em>Subsurface</em>, accessed by selecting
-<em>Log → 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="ulist"><ul>
-<li>
-<p>
-The user is conversant with dive planning and has the necessary training to perform
- dive planning.
-</p>
-</li>
-<li>
-<p>
-The user plans dives within his/her certification limits.
-</p>
-</li>
-<li>
-<p>
-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.
-</p>
-</li>
-<li>
-<p>
-The safety of a dive plan depends heavily on the way in which the planner is used.
-</p>
-</li>
-<li>
-<p>
-The user is familiar with the user interface of <em>Subsurface</em>.
-</p>
-</li>
-<li>
-<p>
-A user who is not absolutely sure about any of the above requirements should not use
- this feature.
-</p>
-</li>
-</ul></div>
-</div></div>
-<div class="sect2">
-<h3 id="_the_em_subsurface_em_dive_planner_screen">13.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 sections on the left hand side of the screen.
-They are: Available Gases, Rates, Planning, Gas Options and Notes.</p></div>
-<div class="paragraph"><p>At the top right hand is a green <strong>design panel</strong> on 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_f20.jpg" alt="FIGURE: Dive planner startup window" />
-</div>
-</div>
-</div>
-<div class="sect2">
-<h3 id="_open_circuit_dives">13.2. Open circuit dives</h3>
-<div class="ulist"><ul>
-<li>
-<p>
-Towards the center bottom of the planner (circled in blue in the image above) is a dropbox with three options. Select the appropriate one of these:
-</p>
-<div class="ulist"><ul>
-<li>
-<p>
-Open Circuit (the default)
-</p>
-</li>
-<li>
-<p>
-CCR
-</p>
-</li>
-<li>
-<p>
-pSCR
-</p>
-</li>
-</ul></div>
-</li>
-<li>
-<p>
-Choose the Open Circuit option.
-</p>
-</li>
-<li>
-<p>
-In the top left-hand area of the planning screen, be sure the constant dive parameters are
- appropriate. These are: Start date and time of the intended dive, Atmospheric Pressure and Altitude
- above sea level of the dive site. The atmospheric pressure can also be entered as an altitude
- in meters, assuming a sea-level atmospheric pressure of 1.013 bar.
-</p>
-</li>
-<li>
-<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="#cylinder_definitions">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 cylinder is assumed to contain 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 right-hand of the dialogue.
-</p>
-</li>
-<li>
-<p>
-The profile of the planned dive can be created in two ways:
-</p>
-<div class="ulist"><ul>
-<li>
-<p>
-Drag the waypoints
- (the small white circles) on the existing dive profile to represent the dive. Additional
- waypoints can be created by double-clicking the existing dive profile. Waypoints can be deleted
- by right-clicking a particular waypoint and selecting the <em>delete</em> item from the resulting
- context menu.
-</p>
-</li>
-<li>
-<p>
-The most efficient way to create a dive profile is to enter the appropriate values into the table
- marked <em>Dive planner points</em>. The first line of the table represents the duration and the final
- depth of the descent from the surface. Subsequent segments describe the bottom phase of the dive.
- The <em>CC set point</em> column is only relevant for closed circuit divers.
- The ascent is usually not specified because this is what the planner is supposed to calculate.
- Add additional segments to the profile by selecting the "+" icon at the top right hand of the
- table. Segments entered into the <em>Dive planner points</em> table automatically appear in the <strong>Dive
- Profile</strong> diagram.
-</p>
-</li>
-</ul></div>
-</li>
-</ul></div>
-<div class="sect3">
-<h4 id="_recreational_dives">13.2.1. Recreational dives</h4>
-<div class="paragraph"><p>Recreational mode is what comes closest to planning a dive based on the non-decompression limit (NDL).
-It computes the maximum time a diver can stay at the current depth without needing mandatory decompression
-stops and without using more than the existing gas (minus a reserve). The planner automatically takes
-into account the nitrogen load incurred in previous dives. But conventional dive tables are also used in a
-way that can take into account previous dives. Why use a dive planner for recreational dives? Using
-recreational dive tables, the maximum depth of a dive is taken into account. But few dives are
-done at a constant depth corresponding to the maximum depth (i.e. a "square" dive profile). This means
-dive tables overestimate the nitrogen load incurred during previous dives. The <em>Subsurface</em>
-dive planner calculates nitrogen load according to the real dive profiles of all uploaded previous dives,
-in a similar way as dive computers calculate nitrogen load during a dive. This means that the diver gets <em>credit,</em>
-in terms of nitrogen load, for not remaining at maximum depth during
-previous dives, so a longer subsequent dive can be planned.
- For the planner to work it’s crucial to upload all previous dives
-onto <em>Subsurface</em> before doing dive planning.
-To plan a dive, the appropriate settings need to be defined.</p></div>
-<div class="ulist"><ul>
-<li>
-<p>
-Ensure the date and time is set to that of the intended dive. This allows calculation of
-the nitrogen load incurred during previous dives.
-</p>
-</li>
-<li>
-<p>
-Immediately under the heading <em>Planning</em> are two checkboxes <em>Recreational</em> and <em>Safety Stop</em>.
- Check these two boxes.
-</p>
-</li>
-<li>
-<p>
-Then define the cylinder size,
- the gas mixture (air or % oxygen) and the starting cylinder pressure in the top left-hand
- section of the planner under <em>Available gases</em>.
-</p>
-</li>
-<li>
-<p>
-The planner calculates whether the specified cylinder contains enough air/gas to complete
- the planned dive. In order for this to be accurate, under <em>Gas options</em>, specify an appropriate
- surface air consumption (SAC) rate for <em>Bottom SAC</em>. Suitable values are between 15 l/min and 30 l/min,
- with novice divers or difficult dives requiring SAC rates closer to 30l/min.
-</p>
-</li>
-<li>
-<p>
-Define the amount of gas the cylinder must have at the end of the bottom section of the
- dive just before ascent. A value of 50 bar is often used. The reason for this reserve gas is to provide for the possible
- need to bring a buddy to the surface using gas sharing. How much gas is used in
- sharing depends on the depth of the ascent. This can be difficult to estimate, so most agencies assume a
- fixed amount of gas, or actually of pressure e.g. 40 or 50 bar or 25% or 33% (rule of thirds). But <em>Subsurface</em> can do better
- because it knows about the ascent and that is why we add the amount of gas during the ascent (i.e. the "deco gas“).
- Subsurface still uses a fixed pressure "reserve" but that’s supposed to be for the additional gas used when
- there’s a problem and your pulse rate goes up when you start to buddy breathe. This reserve amount is user configurable.
-</p>
-</li>
-<li>
-<p>
-Define the depth of the dive by dragging the waypoints (white dots) on the dive profile or
- (even better) defining the appropriate depths using the table under <em>Dive planner points</em> as
- desribed under the previous heading. If
- this is a multilevel dive, set the appropriate dive depths to represent the dive plan by adding
- waypoints to the dive profile or by adding appropriate dive planner points to the <em>Dive Planner Points</em>
- table. <em>Subsurface</em> will automatically extend the bottom section of the dive to the maximum
- duration within the no-decompression limits (NDL).
-</p>
-</li>
-<li>
-<p>
-The ascent speed can be changed. The default ascent speeds are those considered safe for recreational
- divers.
-</p>
-</li>
-</ul></div>
-<div class="paragraph"><p>The dive profile in the planner shows the maximum dive time within no-deco limits using the
-Bühlmann ZH-L16 algorithm and the gas and depth settings specified as described above. The <em>Subsurface</em> planner
-allows rapid assessment of dive duration as a function of dive depth, given the nitrogen load incurred during previous dives. The
-dive plan includes estimates of the amount of air/gas used, depending on the cylinder settings specified
-under <em>Available gases</em>. If the initial cylinder pressure is set to 0, the dive duration shown is the
-true no-deco limit (NDL) without taking into account gas used during the dive. If the surface above the dive profile is RED
-it means that recreational dive limits are exceeded and either the dive duration or the dive depth needs to be reduced.</p></div>
-<div class="paragraph"><p>Below is an image of a dive plan for a recreational dive at 30 meters. Although the no-deco limit (NDL) is 23
-minutes, the duration of the dive is limited by the amount of air in the cylinder. That is shown in the
-text box at the bottom right of the panel, requiring sufficient air for buddy-sharing during ascent.</p></div>
-<div class="imageblock" style="text-align:center;">
-<div class="content">
-<img src="images/rec_diveplan.jpg" alt="FIGURE: A recreational dive plan: setup" />
-</div>
-</div>
-</div>
-<div class="sect3">
-<h4 id="_non_recreational_open_circuit_dives_including_decompression">13.2.2. Non-recreational open circuit dives, including decompression</h4>
-<div class="paragraph"><p>Non-recreational dive planning involves exceeding the no-deco limits and/or using multiple breathing gases.
-These dives are planned in three stages:</p></div>
-<div class="paragraph"><p><strong>a) Nitrogen management</strong>: This is done by specifying the rates for descent and ascent,
-as well as the deco model (GFLow, GFHigh or Conservatism level) under the headings <em>Rates</em> and <em>Planning</em>
-to the bottom left of the planning screen. Two deco models are supported the Bühlmann model and the VPM-B
-model. Select one of the two models. When selecting the Bühlmann model, the gradient factors (GF_high and GF_low
-need to be specified. 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 values in the <em>Preferences</em>.
-Gradient Factor settings strongly affect the calculated ceilings and their depths.
-A very low GFLow value brings on decompression stops early during the dive.
- ** For more information about Gradient factors, see the section on <a href="#S_GradientFactors">Gradient Factor Preference settings</a>.</p></div>
-<div class="paragraph"><p>If the VPM-B model is selected, the Conservatism_level needs to be specified on a scale of 0 (least conservative) to 4 (most conservative).
-This model tends to give deco stops at deeper levels than the Bühlmann model and often results in slightly shorter
-dive durations than the Bühlmann model. When selecting one of these models, keep in mind they are NOT exact physiological models but
-only mathematical models that appear to work in practice.</p></div>
-<div class="paragraph"><p>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&ie=UTF8&qid=1403932320&sr=1-1&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 that discusses both the Bühlmann deco model and the VPM-B model.
-</p>
-</li>
-</ul></div>
-<div class="paragraph"><p>The ascent rate is critical for nitrogen off-gassing at the end of the dive and is specified
-for several depth ranges, using the average (or mean) depth as a yardstick. The mean depth
-of the dive plan is shown by a light grey line on the dive profile. 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, 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></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 increased to 1.6 bar.</p></div>
-<div class="paragraph"><p><strong>c) Gas management</strong>: With open-circuit dives this is a primary
-consideration. Divers need to keep within the limits of the amount of
-gas within the dive
-cylinder(s), allowing for an appropriate margin for a 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
-liters/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 15-30 l/min are common. For good gas management, a guess
-is not sufficient and you needs to
-monitor gas consumption on a regular basis, dependent on different dive conditions and/or equipment.
-The planner calculates the total volume of gas used during the dive and issues a warning
-if you exceeds the total amount of gas available. Good practice demands that divers 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 you can start the detailed time-depth planning of the dive. <em>Subsurface</em> offers an unique
-graphical interface for doing planning. Themechanics are
-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 blue 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 the profile reflects the intended dive. Drag the waypoints to represent
-the depth and duration of the dive. It is NOT necessary to specify the ascent part of the dive
-since the planner calculates this, based on the settings that have been specified.
-If any of the management limits (for nitrogen, oxygen or gas) are 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. Be sure the <em>Used Gas</em> value in each row
-of that table corresponds to one of the gas mixtures specified in the <em>Available Gases</em> table.
-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 fulfill decompression requirements for that
-dive. A waypoint can be moved by selecting it 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 get a precise presentation of the dive plan. In fact, you can create the
-whole dive profile by editing the <em>Dive Planner Points</em> dialog.</p></div>
-<div class="paragraph"><p>Show 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. These changes can be deleted by right-clicking the gas change and
-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_f20.jpg" alt="FIGURE: Planning a dive: setup" />
-</div>
-</div>
-<div class="paragraph"><p>Once the above steps have been completed, save by clicking the <em>Save</em> button
-towards the top middle of the planner. The saved dive plan will appear
-in the <strong>Dive List</strong> panel of <em>Subsurface</em>.</p></div>
-<div class="paragraph"><p><strong>The dive plan details</strong></p></div>
-<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>Notes</em> section of the dive planner, immediately to the left
-of the <em>Dive Plan Details</em>. If a <em>Verbatim dive plan</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>
-<div class="sect2">
-<h3 id="_planning_pscr_dives">13.3. Planning pSCR dives</h3>
-<div class="paragraph"><p>To plan a dive using a passive semi-closed rebreather (pSCR), select <em>pSCR</em> rather than
-<em>Open circuit</em> in the dropdown list.
-The parameters of the pSCR dive can be set by selecting <em>File → Preferences → Graph</em>
-from the main menu, where the gas consumption calculation takes into account the pSCR dump
-ratio (default 10:1) as well as the metabolism rate. The calculation also takes the oxygen drop
-accross the mouthpiece of the rebreather into account. If the
-pO<sub>2</sub> drops below what is considered safe, a warning appears in the <em>Dive plan
-details</em>. A typical pSCR configuration is with a single cylinder and one or more bail-out
-cylinders. Therefore the setup of the <em>Available gases</em> and the <em>Dive planner points</em> tables
-are very similar to that of a CCR dive plan, described below. However, no oxygen setpoints
-are specified for pSCR dives. Below is a dive plan for a pSCR dive. The dive is comparable
-to that of the CCR dive below, but note the longer ascent duration due to the lower oxygen
-in the loop due to the oxygen drop across the mouthpiece of the pSCR equipment.</p></div>
-<div class="imageblock" style="text-align:center;">
-<div class="content">
-<img src="images/Planner_pSCR1_f20.jpg" alt="FIGURE: Planning a pSCR dive: setup" />
-</div>
-</div>
-</div>
-<div class="sect2">
-<h3 id="_planning_ccr_dives">13.4. Planning CCR dives</h3>
-<div class="paragraph"><p>To plan a dive using a closed circuit rebreather, select the <em>CCR</em> option in the dropdown
-list, circled in blue in the image below.</p></div>
-<div class="paragraph"><p><strong>Available gases</strong>: In the <em>Available gases</em> table, enter the cylinder information for the
-diluent cylinder and for any bail-out cylinders. Do NOT enter the information for the oxygen
-cylinder since it is implied when the <em>CCR</em> dropdown selection is made.</p></div>
-<div class="paragraph"><p><strong>Entering setpoints</strong>: Specify a default setpoint in the Preferences tab, by selecting <em>File → Preferences → Graph</em> from
-the main menu. All user-entered segments in the <em>Dive planner points</em> table
-use the default setpoint value. Then, different setpoints can be specified for dive segments
-in the <em>Dive planner points</em> table. A zero setpoint
-means the diver bails out to open circuit mode for that segment. Decompression is always calculated
-using the setpoint of the last manually entered segment. So, to plan a bail out ascent for a
-CCR dive, add a one-minute dive segment to the end with a setpoint value of 0. The decompression
-algorithm does not switch deco-gases automatically while in CCR mode (i.e. when a positive setpoint is specified) but
-this is calculated for bail out ascents.</p></div>
-<div class="paragraph"><p>The dive profile for a CCR dive may look something like the image below.</p></div>
-<div class="imageblock" style="text-align:center;">
-<div class="content">
-<img src="images/Planner_CCR1_f20.jpg" alt="FIGURE: Planning a CCR dive: setup" />
-</div>
-</div>
-<div class="paragraph"><p>Note that, in the <em>Dive plan details</em>, the gas consumption for a CCR segment is not calculated,
-so gas consumptions of 0 liters are the norm.</p></div>
-</div>
-<div class="sect2">
-<h3 id="S_Replan">13.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 no way to change a saved dive plan.
-To change a dive plan, select it on the <strong>Dive List</strong>. Then, in the main menu,
-select <em>Log → Re-plan dive</em>. This will open the selected dive plan within the dive planner,
-letting changes 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">13.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
-are specified appropriately in the top left-hand <em>Start Time</em> field. <em>Subsurface</em>
-calculates the gas loading figures and the affect of the first dive is
-evaluated on later dives.</p></div>
-<div class="paragraph"><p>If you have just completed a long/deep dive and are planning
-another dive, then highlight, in the <strong>Dive List</strong>, the dive that has just been done
-then activate the planner. Depending on the start time of the planned dive,
-the planner takes into account the gas loading during the completed dive
-and plans accordingly.</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 you want to plan a dive using
-this configuration, 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">13.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. You can also cut and paste the <em>Dive Plan Details</em> to
-include 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>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 → Print</em> function 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="_description_of_the_subsurface_main_menu_items">14. 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">14.1. File</h3>
-<div class="ulist"><ul>
-<li>
-<p>
-<a href="#S_NewLogbook"><em>New Logbook</em></a> - Close the currently open dive logbook and
- clear all dive information.
-</p>
-</li>
-<li>
-<p>
-<em>Open logbook</em> - Open the file manager to select a dive
- logbook to open.
-</p>
-</li>
-<li>
-<p>
-<em>Open cloud storage</em> - Open the dive log previously saved in <a href="#S_Cloud_storage"><em>Cloud storage</em></a>.
-</p>
-</li>
-<li>
-<p>
-<em>Save</em> - Save the dive logbook currently open.
-</p>
-</li>
-<li>
-<p>
-<em>Save to cloud storage</em> - Save the current dive log to <a href="#S_Cloud_storage"><em>Cloud storage</em></a>.
-</p>
-</li>
-<li>
-<p>
-<em>Save as</em> - Save the current logbook under a different file name.
-</p>
-</li>
-<li>
-<p>
-<em>Close</em> - Close the dive logbook currently open.
-</p>
-</li>
-<li>
-<p>
-<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.
-</p>
-</li>
-<li>
-<p>
-<a href="#S_PrintDivelog"><em>Print</em></a> - Print the currently open logbook.
-</p>
-</li>
-<li>
-<p>
-<a href="#S_Preferences"><em>Preferences</em></a> - Set the <em>Subsurface</em> preferences.
-</p>
-</li>
-<li>
-<p>
-<a href="#S_FindMovedImages"><em>Find moved images</em></a> - If photos taken during dives have been moved to
- a different disk or directory, locate them and link them to the appropriate dives.
-</p>
-</li>
-<li>
-<p>
-<a href="#S_Configure"><em>Configure dive computer</em></a> - Edit the configuration of a dive computer.
-</p>
-</li>
-<li>
-<p>
-<em>Quit</em> - Quit <em>Subsurface</em>.
-</p>
-</li>
-</ul></div>
-</div>
-<div class="sect2">
-<h3 id="_import">14.2. Import</h3>
-<div class="ulist"><ul>
-<li>
-<p>
-<a href="#S_ImportDiveComputer"><em>Import from dive computer</em></a> - Import dive information
- from a dive computer.
-</p>
-</li>
-<li>
-<p>
-<a href="#Unified_import"><em>Import Log Files</em></a> - Import dive information from a file in
- in a <em>Subsurface</em>-compatible format.
-</p>
-</li>
-<li>
-<p>
-<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.
-</p>
-</li>
-<li>
-<p>
-<a href="#S_ImportingDivelogsDe"><em>Import from Divelogs.de</em></a> - Import dive information
- from <em>www.Divelogs.de</em>.
-</p>
-</li>
-</ul></div>
-</div>
-<div class="sect2">
-<h3 id="_log">14.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>
-<em>Edit dive</em> - Edit a dive where the profile was entered by hand and not from a dive computer.
-</p>
-</li>
-<li>
-<p>
-<a href="#S_DivePlanner"><em>Plan Dive</em></a> - Plan dives.
-</p>
-</li>
-<li>
-<p>
-<a href="#S_Replan"><em>Edit dive in planner</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> - 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.
-</p>
-</li>
-<li>
-<p>
-<a href="#S_Renumber"><em>Renumber</em></a> - Renumber the dives listed in the <strong>Dive List</strong>
- panel.
-</p>
-</li>
-<li>
-<p>
-<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 coordinate 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">14.4. View</h3>
-<div class="ulist"><ul>
-<li>
-<p>
-<a href="#S_ViewPanels"><em>All</em></a> - View the four main <em>Subsurface</em> panels
- all at once.
-</p>
-</li>
-<li>
-<p>
-<a href="#S_ViewPanels"><em>Dive List</em></a> - View only the <strong>Dive List</strong> panel.
-</p>
-</li>
-<li>
-<p>
-<a href="#S_ViewPanels"><em>Profile</em></a> - View only the <strong>Dive Profile</strong> panel.
-</p>
-</li>
-<li>
-<p>
-<a href="#S_ViewPanels"><em>Info</em></a> - View only the <strong>Notes</strong> panel.
-</p>
-</li>
-<li>
-<p>
-<a href="#S_ViewPanels"><em>Globe</em></a> - View only the <strong>World Map</strong> panel.
-</p>
-</li>
-<li>
-<p>
-<em>Yearly Statistics</em> - Display summary statistics about dives during this and past
- years.
-</p>
-</li>
-<li>
-<p>
-<em>Prev DC</em> - Switch to data from previous dive computer, if a single dive was logged from more than one.
-</p>
-</li>
-<li>
-<p>
-<em>Next DC</em> - Switch to next dive computer.
-</p>
-</li>
-<li>
-<p>
-<em>Full Screen</em> - Toggles Full Screen mode.
-</p>
-</li>
-</ul></div>
-</div>
-<div class="sect2">
-<h3 id="_share_on">14.5. Share on</h3>
-<div class="ulist"><ul>
-<li>
-<p>
-<a href="#S_Facebook"><em>Facebook</em></a> - Share the currently selected dive on your Facebook timeline.
-</p>
-</li>
-</ul></div>
-</div>
-<div class="sect2">
-<h3 id="_help">14.6. Help</h3>
-<div class="ulist"><ul>
-<li>
-<p>
-<em>About Subsurface</em> - Show a panel with the version number of <em>Subsurface</em> as
- well as licensing information.
-</p>
-</li>
-<li>
-<p>
-<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>.
-</p>
-</li>
-<li>
-<p>
-<a href="#S_UserSurvey"><em>User survey</em></a> - Help to make <em>Subsurface</em> even better by taking part in our user survey
- or by completing another survey if your diving habits have changed.
-</p>
-</li>
-<li>
-<p>
-<em>User manual</em> - Open a window showing this user manual.
-</p>
-</li>
-</ul></div>
-</div>
-</div>
-</div>
-<div class="sect1">
-<h2 id="_appendix_a_operating_system_specific_information_for_importing_dive_information_from_a_dive_computer">15. 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">15.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, the 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>
-<li>
-<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&f=USB%20Bridges&pn=CP2101">Silicon Labs document and software repository</a>.
-</p>
-</li>
-</ul></div>
-</div>
-<div class="sect2">
-<h3 id="S_HowFindDeviceName">15.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 connecting a dive computer by using a USB connector, usually
-<em>Subsurface</em> will either propose a drop down list with 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
-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 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
-won’t be able to use the USB port. Let us assume one’s username is <em>johnB</em>.</p></div>
-<div class="ulist"><ul>
-<li>
-<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.
-</p>
-</li>
-<li>
-<p>
-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.
-</p>
-</li>
-<li>
-<p>
-Under some circumstances this change takes only effect (eg. on Ubuntu) after
-one logs out and then logs in again.
-</p>
-</li>
-</ul></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">15.3. Manually 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, Petrel and Nerd there is a
-different procedure to get the device’s 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, be sure 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’s user guide. When using a Shearwater Predator/Petrel/Nerd, select
-<em>Dive Log → 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="sect3">
-<h4 id="_on_windows_2">15.3.1. On Windows:</h4>
-<div class="paragraph"><p>Bluetooth is most likely already enabled. For pairing with the dive computer choose
-<em>Control Panel → Bluetooth Devices → Add Wireless Device</em>.
-This should bring up a dialog showing your dive computer (which should be in Bluetooth mode) and
-allowing pairing. Right click on it and choose <em>Properties→ 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>
-<div class="sect3">
-<h4 id="_on_macos">15.3.2. On MacOS:</h4>
-<div class="paragraph"><p>Click on the Bluetooth symbol in the menu bar and select <em>Set up
-Bluetooth Device…</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 complete, 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>
-<div class="sect3">
-<h4 id="_on_linux">15.3.3. On Linux</h4>
-<div class="paragraph"><p>Be sure 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 straightforward. For instance, Gnome3 shows a
-Bluetooth icon on the right of the toolbar at the top of the screen.
-Users have reported difficulties with some Bluetooth controllers. If you have an onboard controller,
-try that first. It is simplest if you remove any USB Bluetooth dongles. If you have a USB dongle that
-came with your dive computer, try that before any others.</p></div>
-<div class="paragraph"><p>Setting up a connection to download dives from your Bluetooth-enabled device, such as the
-<em>Shearwater Petrel</em>, is not yet an automated process and will generally require the command prompt.
-It is essentially a three step process.</p></div>
-<div class="ulist"><ul>
-<li>
-<p>
-Enable the Bluetooth controller and pair your dive computer
-</p>
-</li>
-<li>
-<p>
-Establish an RFCOMM connection
-</p>
-</li>
-<li>
-<p>
-Download the dives with Subsurface
-</p>
-</li>
-</ul></div>
-<div class="paragraph"><p>Ensure the dive computer is in upload mode. On the <em>Shearwater Petrel</em>, <em>Petrel 2</em> and <em>Nerd</em>
-cycle through the menu, select <em>Dive Log</em>, then <em>Upload Log</em>. The display will read <em>Initializing</em>, then
-<em>Wait PC 3:00</em> and will countdown. Once the connection is established, the display reads <em>Wait CMD …</em>
-and the countdown continues. When downloading the dive from Subsurface, the display reads <em>Sending</em> then
-<em>Sent Dive</em>.</p></div>
-<div class="paragraph"><p>To establish the connection, establish root access through <code>sudo</code> or <code>su</code>.
-The correct permission is required to download the dives in the computer. On most Linux systems this means becoming
-a member of the dialout group (This is identical as for many dive computers using a Linux USB port, described
-in the previous section). On the command terminal, enter:</p></div>
-<div class="paragraph"><p><code>sudo usermod -a -G dialout username</code></p></div>
-<div class="paragraph"><p>Then log out and log in for the change to take effect.</p></div>
-<div class="sect4">
-<h5 id="_enabling_the_bluetooth_controller_and_pairing_your_dive_computer">Enabling the Bluetooth controller and pairing your dive computer</h5>
-<div class="paragraph"><p>Attempt to set up the Bluetooth controller and pair your dive computer using the graphical
-environment of the operating system. After setting the dive computer to upload mode, click the Bluetooth icon in the system tray
-and select <em>Add new device</em>. The dive computer should appear. If asked for a password, enter 0000.
-Write down or copy the MAC address of your dive computer - this needed later and should be in the form 00:11:22:33:44:55.</p></div>
-<div class="paragraph"><p>If the graphical method doesn’t work, pair the device from the command line. Open a terminal
-and use <code>hciconfig</code> to check the Bluetooth controller status</p></div>
-<div class="literalblock">
-<div class="content">
-<pre><code>$ hciconfig
-hci0: Type: BR/EDR Bus: USB
- BD Address: 01:23:45:67:89:AB ACL MTU: 310:10 SCO MTU: 64:8
- *DOWN*
- RX bytes:504 acl:0 sco:0 events:22 errors:0
- TX bytes:92 acl:0 sco:0 commands:21 errors:0</code></pre>
-</div></div>
-<div class="paragraph"><p>This indicates a Bluetooth controller with MAC address 01:23:45:67:89:AB, connected as hci0.
-Its status is <em>DOWN</em>, i.e. not powered. Additional controllers will appear as hci1, etc.
-If there is not a Bluetooth dongle plugged in upon booting the computer, hci0 is probably the onboard.
-Now power on the controller and enable authentication:</p></div>
-<div class="literalblock">
-<div class="content">
-<pre><code>sudo hciconfig hci0 up auth+ (enter password when prompted)
-hciconfig
-hci0: Type: BR/EDR Bus: USB
- BD Address: 01:23:45:67:89:AB ACL MTU: 310:10 SCO MTU: 64:8
- *UP RUNNING PSCAN AUTH*
- RX bytes:1026 acl:0 sco:0 events:47 errors:0
- TX bytes:449 acl:0 sco:0 commands:46 errors:0</code></pre>
-</div></div>
-<div class="paragraph"><p>Check that the status now includes <code><em>UP</em>, <em>RUNNING</em> AND <em>AUTH</em></code>.</p></div>
-<div class="paragraph"><p>If there are multiple controllers running, it’s easiest to off the unused controller(s). For example, for <code>hci1</code>:</p></div>
-<div class="literalblock">
-<div class="content">
-<pre><code>sudo hciconfig hci1 down</code></pre>
-</div></div>
-<div class="paragraph"><p>Next step is to <em>trust</em> and <em>pair</em> the dive computer. On distros with Bluez 5, such as Fedora 22,
-one can use a tool called <code>blutootctl</code>, which will bring up its own command prompt.</p></div>
-<div class="literalblock">
-<div class="content">
-<pre><code>bluetoothctl
-[NEW] Controller 01:23:45:67:89:AB localhost.localdomain [default]
-[bluetooth]# agent on
-Agent registered
-[bluetooth]# default-agent
-Default agent request successful
-[bluetooth]# scan on <----now set your dive computer to upload mode
-Discovery started
-[CHG] Controller 01:23:45:67:89:AB Discovering: yes
-[NEW] Device 00:11:22:33:44:55 Petrel
-[bluetooth]# trust 00:11:22:33:44:55 <----you can use the tab key to autocomplete the MAC address
-[CHG] Device 00:11:22:33:44:55 Trusted: yes
-Changing 00:11:22:33:44:55 trust succeeded
-[bluetooth]# pair 00:11:22:33:44:55
-Attempting to pair with 00:11:22:33:44:55
-[CHG] Device 00:11:22:33:44:55 Connected: yes
-[CHG] Device 00:11:22:33:44:55 UUIDs: 00001101-0000-1000-8000-0089abc12345
-[CHG] Device 00:11:22:33:44:55 Paired: yes
-Pairing successful
-[CHG] Device 00:11:22:33:44:55 Connected: no</code></pre>
-</div></div>
-<div class="paragraph"><p>If asked for a password, enter 0000. It’s ok if the last line says <em>Connected: no</em>. The important part
-is the line above, <code>Pairing successful</code>.</p></div>
-<div class="paragraph"><p>If the system has Bluez version 4 (e.g. Ubuntu 12.04 through to 15.04), there is probably not a
-<code>bluetoothctl</code>, but a script called <code>bluez-simple-agent</code> or just <code>simple-agent</code>.</p></div>
-<div class="literalblock">
-<div class="content">
-<pre><code>hcitool -i hci0 scanning
-Scanning ...
- 00:11:22:33:44:55 Petrel
- bluez-simple-agent hci0 00:11:22:33:44:55</code></pre>
-</div></div>
-<div class="paragraph"><p>Once ther dive computer is pired, set up the RFCOMM connection</p></div>
-</div>
-<div class="sect4">
-<h5 id="_establishing_the_rfcomm_connection">Establishing the RFCOMM connection</h5>
-<div class="paragraph"><p>The command to establish an RFCOMM connection is:</p></div>
-<div class="paragraph"><p><code>sudo rfcomm -i <controller> connect <dev> <bdaddr> [channel]</code></p></div>
-<div class="ulist"><ul>
-<li>
-<p>
-<code><controller></code> is the Bluetooth controller, <code>hci0</code>.
-</p>
-</li>
-<li>
-<p>
-<code><dev></code> is the RFCOMM device file, <code>rfcomm0</code>
-</p>
-</li>
-<li>
-<p>
-<code><bdaddr></code> is the dive computer’s MAC address, <code>00:11:22:33:44:55</code>
-</p>
-</li>
-<li>
-<p>
-<code>[channel]</code> is the dive computer’s Bluetooth channel we need to connect to.
-</p>
-</li>
-</ul></div>
-<div class="paragraph"><p>If one omits it, channel 1 is assumed. Based on a limited number of user reports,
-the appropriate channel for the dive computer is probably:</p></div>
-<div class="ulist"><ul>
-<li>
-<p>
-<em>Shearwater Petrel 1</em>: channel 1
-</p>
-</li>
-<li>
-<p>
-<em>Shearwater Petrel 2</em>: channel 5
-</p>
-</li>
-<li>
-<p>
-<em>Shearwater Nerd</em>: channel 5
-</p>
-</li>
-<li>
-<p>
-<em>Heinrichs-Weikamp OSTC Sport</em>: channel 1
-</p>
-</li>
-</ul></div>
-<div class="paragraph"><p>E.g. to connect a <em>Shearwater Petrel 2</em>, set the dive computer to upload mode and enter:</p></div>
-<div class="literalblock">
-<div class="content">
-<pre><code>sudo rfcomm -i hci0 connect rfcomm0 00:11:22:33:44:55 5 (enter a password, probably 0000, when prompted)</code></pre>
-</div></div>
-<div class="paragraph"><p>This gives the response:</p></div>
-<div class="literalblock">
-<div class="content">
-<pre><code>Connected /dev/rfcomm0 to 00:11:22:33:44:55 on channel 5
-Press CTRL-C for hangup</code></pre>
-</div></div>
-<div class="paragraph"><p>To connect a _Shearwater Petrel 1+ or + HW OSTC Sport+, set the dive computer to upload mode and enter:</p></div>
-<div class="literalblock">
-<div class="content">
-<pre><code>sudo rfcomm -i hci0 connect rfcomm0 00:11:22:33:44:55 (enter a password, probably 0000, when prompted)
-Connected /dev/rfcomm0 to 00:11:22:33:44:55 on channel 1
-Press CTRL-C for hangup</code></pre>
-</div></div>
-<div class="paragraph"><p>If the specific channel the dive computer needs is not known, or the channel in the list above doesn’t
-work, the command <code>sdptool records</code> should help determine the appropriate channel. The output
-below is for a <em>Shearwater Petrel 2</em>.</p></div>
-<div class="literalblock">
-<div class="content">
-<pre><code>sdptool -i hci0 records 00:11:22:33:44:55
-Service Name: Serial Port
-Service RecHandle: 0x10000
-Service Class ID List:
- "Serial Port" (0x1101)
- Protocol Descriptor List:
- "L2CAP" (0x0100)
- "RFCOMM" (0x0003)
- Channel: 5</code></pre>
-</div></div>
-<div class="paragraph"><p>For a Bluetooth dive computer not in the list above, or if the channel listed is not correct, please
-let the Subsurface developers know on the user forum or the developer mailing list <em>subsurface@subsurface-divelog.org</em>.</p></div>
-</div>
-<div class="sect4">
-<h5 id="_download_the_dives_with_subsurface">Download the dives with Subsurface</h5>
-<div class="paragraph"><p>After establishing the RFCOMM connection and while the dive computer’s upload mode countdown is still running, go to_Subsurface_, select <em>Import→Import from dive computer</em> and enter appropriate Vendor (e.g. <em>Shearwater</em>), Dive Computer (<em>Petrel</em>), Device or Mount Point (<em>/dev/rfcomm0</em>) and click <em>Download</em>.</p></div>
-</div>
-</div>
-</div>
-</div>
-</div>
-<div class="sect1">
-<h2 id="_appendix_b_dive_computer_specific_information_for_importing_dive_information">16. APPENDIX B: Dive Computer specific information for importing dive data.</h2>
-<div class="sectionbody">
-<div class="sect2">
-<h3 id="S_ImportUemis">16.1. Importing from 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 you don’t 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/<your_username>/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 you 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 you download 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 straightforward.
-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. You
-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">16.2. Importing from 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 recognize 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>. Windows-based IrDA
-drivers for the Uwatec can also be downloaded from the ScubaPro web site, with drivers located on
-the download page for the ScubaPro SmartTrak software.</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">16.3. Importing 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’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="S_ImportingXDeep">16.4. Importing from xDEEP BLACK</h3>
-<div class="admonitionblock">
-<table><tr>
-<td class="icon">
-<img src="images/icons/HW_xdeepblack.jpg" alt="Note" />
-</td>
-<td class="content">Each dive has to be individually saved as UDDF file using "Export UDDF" option in BLACK’s logbook menu.
-When mounted as a USB drive UDDF files are available in LOGBOOK directory.
-Note: The xDEEP BLACK saves NDL time but 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 xDEEP BLACK.</td>
-</tr></table>
-</div>
-</div>
-<div class="sect2">
-<h3 id="_importing_from_shearwater_predator_petrel_nerd_using_bluetooth">16.5. Importing from Shearwater Predator/Petrel/Nerd using Bluetooth</h3>
-<div class="admonitionblock">
-<table><tr>
-<td class="icon">
-<img src="images/icons/predator.jpg" alt="Note" />
-</td>
-<td class="content">Specific instructions for downloading dives using Bluetooth are given in the section above, <a href="#S_Bluetooth"><em>Connecting Subsurface to a Bluetooth-enabled dive computer</em></a>.</td>
-</tr></table>
-</div>
-</div>
-<div class="sect2">
-<h3 id="S_PoseidonMkVI">16.6. Importing from 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 utilizes the IrDA infra-red protocol. Only data for one dive
-can be downloaded at a time, in three files:</td>
-</tr></table>
-</div>
-<div class="ulist"><ul>
-<li>
-<p>
-Setup configuration for the dive and key dive parameters (file with a .txt
- extension)
-</p>
-</li>
-<li>
-<p>
-Dive log details (file with a .csv extension)
-</p>
-</li>
-<li>
-<p>
-Redbook format dive log (file with .cvsr extension). This is a compressed
- version of the dive log using a proprietary format.
-</p>
-</li>
-</ul></div>
-<div class="paragraph"><p><em>Subsurface</em> accesses the .txt and the .csv files to get dive log information.</p></div>
-</div>
-<div class="sect2">
-<h3 id="_importing_from_apd_inspiration_evolution_ccr">16.7. Importing from APD Inspiration/Evolution 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>
-Download the dive using <em>AP Communicator</em>.
-</p>
-</li>
-<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>
-With 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) or TextWrangler (Mac).
-</p>
-</li>
-<li>
-<p>
-Copy the contents of the clipboard into the text editor and save the text file
- with a filename extension of <em>.apd</em>
-</p>
-</li>
-<li>
-<p>
-Within <em>Subsurface</em>, select <em>Import → 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 (labeled <em>Filter:</em>), select "APD log viewer".
-</p>
-</li>
-<li>
-<p>
-On the list of file names select the <em>.apd</em> file created. An import
- dialogue opens showing the default settings for the data in the
-<em>.apd</em> file. If changes are required,
- do this as for <a href="#S_ImportingCSVDives">CSV imports</a>.
-</p>
-</li>
-</ul></div>
-<div class="imageblock" style="text-align:center;">
-<div class="content">
-<img src="images/APD_CSVimportF22.jpg" alt="Figure: APD log viewer import" />
-</div>
-</div>
-<div class="ulist"><ul>
-<li>
-<p>
-The top left hand dropdown box in the import panel lets you select the APD dive computer
- for which the dive log needs to be imported. The default it is DC1, <em>i.e.</em> the
- first of the two dive computers the APD uses. It is possible to sequentially
- import the data for both dive computers by first importing CD1 and then DC2.(<strong>Hint</strong>: The logs
- for the two dive computers are viewed by selecting <em>View → Next DC</em> from
- the Main Menu after the uploading has been completed)
-</p>
-</li>
-<li>
-<p>
-Click the <em>Ok</em> button at the bottom of the import panel.
-</p>
-</li>
-</ul></div>
-<div class="paragraph"><p>The APD dive log will appear within <em>Subsurface</em>. The dive computer- generated ceiling
-provided by the Inspiration can be viewed by selecting the appropriate
-button on the left of the <strong>Dive Profile</strong>. Cylinder pressure data are not logged
-by the APD equipment but can be manually entered in the <em>Equipment</em> Tab.</p></div>
-</div>
-</div>
-</div>
-<div class="sect1">
-<h2 id="_appendix_c_exporting_dive_log_information_from_external_dive_log_software">17. 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="olist arabic"><ol class="arabic">
-<li>
-<p>
-Export the foreign dive log data to format that is accessible from
- <em>Subsurface</em>.
-</p>
-</li>
-<li>
-<p>
-Import the accessible dive log data into <em>Subsurface</em>.
-</p>
-</li>
-</ol></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">17.1. Exporting 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.
-</p>
-</li>
-<li>
-<p>
-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
-</p>
-</li>
-<li>
-<p>
-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 → 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 you need to locate the DM4/DM5 database
-where the dives are stored. You 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 → About</em>
-</p>
-</li>
-<li>
-<p>
-Click <em>Copy</em> after text <em>Copy log folder path to clipboard</em>
-</p>
-</li>
-<li>
-<p>
-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’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_atomic_logbook">17.2. Exporting from Atomic Logbook</h3>
-<div class="admonitionblock" id="Atomic_Export">
-<table><tr>
-<td class="icon">
-<img src="images/icons/atomiclogo.jpg" alt="Note" />
-</td>
-<td class="content">Atomic Logbook is a Windows software by Atomic Aquatics. It allows
-downloading of dive information from Cobalt and Cobalt 2 dive computers.
-The divelog is kept in a SQLite database at
-C:\ProgramData\AtomicsAquatics\Cobalt-Logbook\Cobalt.db. This file can
-be directly imported to Subsurface.</td>
-</tr></table>
-</div>
-</div>
-<div class="sect2">
-<h3 id="_exporting_from_mares_dive_organiser_v2_1">17.3. 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 Organizer 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 Organizer-registered divers on the particular
-computer and all Mares dive computers used. The safest way to get a copy
-of the dive database is to export the information to another compatible format
-which can then be imported into <em>Subsurface</em>.</td>
-</tr></table>
-</div>
-<div class="olist arabic"><ol class="arabic">
-<li>
-<p>
-Within Dive Organizer, select
- <em>Database → Backup</em> from the main menu and back up the database to the desk
- top.
- This creates a zipped file DiveOrganizerxxxxx.dbf.
-</p>
-</li>
-<li>
-<p>
-Rename the file to
- DiveOrganizerxxxxx.zip. Inside the zipped directory is a file
- <em>DiveOrganizer.sdf</em>.
-</p>
-</li>
-<li>
-<p>
-Extract the <em>.sdf</em> file from the zipped folder to your Desktop.
-</p>
-</li>
-<li>
-<p>
-The password for accessing the .zip file is <em>mares</em>.
-</p>
-</li>
-</ol></div>
-</div>
-<div class="sect2">
-<h3 id="S_ImportingDivingLog">17.4. Exporting from <strong>DivingLog 5.0 and 6.0</strong></h3>
-<div class="admonitionblock">
-<table><tr>
-<td class="icon">
-<img src="images/icons/divingloglogo.jpg" alt="Note" />
-</td>
-<td class="content">The best way to bring your logs from DivingLog to Subsurface is to
-convert the whole database. This is because other export formats do not
-include all the details, and would lack, for example, gas switches and
-information of what units are used. With database import, all this
-information is included and readily available.</td>
-</tr></table>
-</div>
-<div class="paragraph"><p>To transfer all files from DivingLog to Subsurface:</p></div>
-<div class="olist arabic"><ol class="arabic">
-<li>
-<p>
-In DivingLog open the <em>File → Export → SQLite</em> menu
-</p>
-</li>
-<li>
-<p>
-Select <em>Settings</em> button
-</p>
-</li>
-<li>
-<p>
-Set the <em>RTF2Plaintext</em> to <em>true</em>
-</p>
-</li>
-<li>
-<p>
-Close the Settings dialog
-</p>
-</li>
-<li>
-<p>
-Click <em>Export</em> button and select the filename
-</p>
-</li>
-</ol></div>
-<div class="paragraph"><p>Once this is done, open the saved database file with Subsurface and the
-dives are automatically converted to Subsurface’s own format. Last step to do is
-save the log file in Subsurface.</p></div>
-</div>
-</div>
-</div>
-<div class="sect1">
-<h2 id="_appendix_d_exporting_a_spreadsheet_to_csv_format">18. APPENDIX D: Exporting a spreadsheet to CSV format</h2>
-<div class="sectionbody">
-<div class="paragraph" id="S_Appendix_D"><p>Many divers keep a dive log in some form of digital file, commonly a spreadsheet
-with various fields of information. These logs can be easily imported into <em>Subsurface</em> 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 to <em>Subsurface</em>.
-Creating a .CSV is straightforward, although the procedure is somewhat different
-according to which spreadsheet program is used.</p></div>
-<div class="paragraph"><p>Organize the diving data in the spreadsheet, so 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 number, Date,
-Time, Duration, Location, GPS, Max Depth, Mean Depth, Buddy, Notes, Weight and Tags).
-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 should be used (no mix of imperial and metric units)
-</p>
-</li>
-<li>
-<p>
-Tags and buddies: values should be separated using a comma.
-</p>
-</li>
-<li>
-<p>
-GPS position: use decimal degrees, e.g. 30.22496 30.821798
-=== <em>LibreOffice Calc</em> and <em>OpenOffice Calc</em>
-</p>
-</li>
-</ol></div>
-<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 → 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>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_ImportingCSVDives">Importing CSV dives</a>.</p></div>
-<div class="sect2">
-<h3 id="_microsoft_em_excel_em">18.1. 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 uses the new character as a separator.
-You 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, 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.
-</p>
-</li>
-<li>
-<p>
-Do one of the following:
-</p>
-<div class="ulist"><ul>
-<li>
-<p>
-In Windows 7, click the <em>Formats</em> tab, and then click <em>Customize this format</em>.
-</p>
-</li>
-<li>
-<p>
-In Windows XP, click the <em>Regional Options</em> tab, and then click <em>Customize</em>.
-</p>
-</li>
-</ul></div>
-</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>. Be sure 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. You can double check the .CSV file by
-opening it with a text editor, then import the dive data as
-explained on the section <a href="#S_ImportingCSVDives">Importing CSV dives</a>.</p></div>
-</div>
-</div>
-</div>
-<div class="sect1">
-<h2 id="S_APPENDIX_E">19. APPENDIX E: Writing a custom print template</h2>
-<div class="sectionbody">
-<div class="paragraph"><p><em>Subsurface</em> has a way to create or modify templates for printing dive logs to
-produce customized printouts of them. Templates written in HTML, as well as a simple
-Grantlee instruction set, are rendered to the print device by <em>Subsurface</em>.</p></div>
-<div class="paragraph"><p>Templates are accessed using the print dialogue (see image <strong>B</strong> below).</p></div>
-<div class="imageblock" style="text-align:center;">
-<div class="content">
-<img src="images/Print1_f22.jpg" alt="FIGURE: Print dialogue" />
-</div>
-</div>
-<div class="paragraph"><p>The buttons under the <em>Template</em> dropdown box lets you <em>Edit</em>, <em>Delete</em>,
-<em>Import</em> and <em>Export</em> templates (see image <strong>A</strong> above). New or modified templates are stored as HTML
-files in the same directory as the dive log being processed. In order to create or modify
-a template, select one of the templates from the template dropdown list in the print dialogue
-(see image <strong>B</strong> above). Choose an existing template that resembles the final desired printout. Then select <em>Edit</em>.</p></div>
-<div class="paragraph"><p>The Edit Panel has three tabs:</p></div>
-<div class="imageblock" style="text-align:center;">
-<div class="content">
-<img src="images/Template1_f22.jpg" alt="FIGURE: template edit dialogue" />
-</div>
-</div>
-<div class="paragraph"><p>1) The <em>Style</em> tab (image <strong>A</strong> above) controls the font, line spacing and color template used for printing the dive log.
- The style attributes are editable. Choose one of the four color palettes used for color printing.</p></div>
-<div class="paragraph"><p>2) The <em>Colors</em> tab (image <strong>B</strong> above) allows editing the colors used for printing the dive log. The colors are highly
- customizable: the <em>Edit</em> buttons in the <em>Colors</em> tab allows choosing arbitrary colors for different
- components of the dive log printout.</p></div>
-<div class="paragraph"><p>3) The <em>Template</em> tab of the Edit Panel (see image below) allows creating a template using HTML as well as a few
- Grantlee programming primitives. Grantlee can create and format HTML code in
- a highly simple but efficient way (see below). The HTML of the template can be edited and saved. The saved
- template is stored in the same directory as the dive being processed. By default, a <em>Custom</em>
- template is a skeleton with no specific print instructions. The information printed
- needs to be specified and formatted in the template by replacing the section marked with:
- "<!-- Template must be filled -→". Writing HTML code with Grantlee instructions allows unlimited
- freedom in determining what is printed and in which way it should be rendered.</p></div>
-<div class="imageblock" style="text-align:center;">
-<div class="content">
-<img src="images/Template2_f22.jpg" alt="FIGURE:Template tab" />
-</div>
-</div>
-<div class="paragraph"><p>You can adapt any of the existing templates and save it to the dive log directory. The standard templates (e.g. One dive, Six dives,
-Table) can be modified in this way. After completing the edits, use the <em>Export</em> button in the print
-dialogue to save the new template using a new template name.</p></div>
-<div class="paragraph"><p>To write a custom template, the following elements must exist so the template will be correctly handled and rendered.</p></div>
-<div class="sect2">
-<h3 id="_main_dive_loop">19.1. Main dive loop</h3>
-<div class="paragraph"><p><em>Subsurface</em> exports a dive list called (<strong>dives</strong>) to the <em>Grantlee</em> back end. It is possible to iterate over the list as follows:
-.template.html</p></div>
-<div class="literalblock">
-<div class="content">
-<pre><code> {% for dive in dives %}
- <h1> {{ dive.number }} </h1>
- {% endfor %}</code></pre>
-</div></div>
-<div class="literalblock">
-<div class="title">output.html</div>
-<div class="content">
-<pre><code> <h1> 1 </h1>
- <h1> 2 </h1>
- <h1> 3 </h1></code></pre>
-</div></div>
-<div class="paragraph"><p>Additional information about <em>Grantlee</em> can be found at <a href="http://www.grantlee.org/apidox/for_themers.html">here</a></p></div>
-</div>
-<div class="sect2">
-<h3 id="_grantlee_exported_variables">19.2. Grantlee exported variables</h3>
-<div class="paragraph"><p>Only a subset of the dive data is exported:</p></div>
-<div class="tableblock">
-<table rules="all"
-width="100%"
-frame="border"
-cellspacing="0" cellpadding="4">
-<col width="50%" />
-<col width="50%" />
-<tbody>
-<tr>
-<td align="left" valign="top"><p class="table"><strong>Name</strong></p></td>
-<td align="left" valign="top"><p class="table"><strong>Description</strong></p></td>
-</tr>
-<tr>
-<td align="left" valign="top"><p class="table">number</p></td>
-<td align="left" valign="top"><p class="table">(<strong>int</strong>) dive number</p></td>
-</tr>
-<tr>
-<td align="left" valign="top"><p class="table">id</p></td>
-<td align="left" valign="top"><p class="table">(<strong>int</strong>) unique dive ID, should be used to fetch the dive profile</p></td>
-</tr>
-<tr>
-<td align="left" valign="top"><p class="table">date</p></td>
-<td align="left" valign="top"><p class="table">(<strong>string</strong>) date of the dive</p></td>
-</tr>
-<tr>
-<td align="left" valign="top"><p class="table">time</p></td>
-<td align="left" valign="top"><p class="table">(<strong>string</strong>) time of the dive</p></td>
-</tr>
-<tr>
-<td align="left" valign="top"><p class="table">location</p></td>
-<td align="left" valign="top"><p class="table">(<strong>string</strong>) location of the dive</p></td>
-</tr>
-<tr>
-<td align="left" valign="top"><p class="table">duration</p></td>
-<td align="left" valign="top"><p class="table">(<strong>string</strong>) duration of the dive</p></td>
-</tr>
-<tr>
-<td align="left" valign="top"><p class="table">depth</p></td>
-<td align="left" valign="top"><p class="table">(<strong>string</strong>) depth of the dive</p></td>
-</tr>
-<tr>
-<td align="left" valign="top"><p class="table">divemaster</p></td>
-<td align="left" valign="top"><p class="table">(<strong>string</strong>) dive master for the dive</p></td>
-</tr>
-<tr>
-<td align="left" valign="top"><p class="table">buddy</p></td>
-<td align="left" valign="top"><p class="table">(<strong>string</strong>) buddy for the dive</p></td>
-</tr>
-<tr>
-<td align="left" valign="top"><p class="table">airTemp</p></td>
-<td align="left" valign="top"><p class="table">(<strong>string</strong>) air temperature of the dive</p></td>
-</tr>
-<tr>
-<td align="left" valign="top"><p class="table">waterTemp</p></td>
-<td align="left" valign="top"><p class="table">(<strong>string</strong>) water temperature of the dive</p></td>
-</tr>
-<tr>
-<td align="left" valign="top"><p class="table">notes</p></td>
-<td align="left" valign="top"><p class="table">(<strong>string</strong>) dive notes</p></td>
-</tr>
-<tr>
-<td align="left" valign="top"><p class="table">rating</p></td>
-<td align="left" valign="top"><p class="table">(<strong>int</strong>) dive rating which ranges from 0 to 5</p></td>
-</tr>
-<tr>
-<td align="left" valign="top"><p class="table">sac</p></td>
-<td align="left" valign="top"><p class="table">(<strong>string</strong>) SAC value for the dive</p></td>
-</tr>
-<tr>
-<td align="left" valign="top"><p class="table">tags</p></td>
-<td align="left" valign="top"><p class="table">(<strong>string</strong>) list of dive tags for the dive</p></td>
-</tr>
-<tr>
-<td align="left" valign="top"><p class="table">gas</p></td>
-<td align="left" valign="top"><p class="table">(<strong>string</strong>) list of gases used in the dive</p></td>
-</tr>
-<tr>
-<td align="left" valign="top"><p class="table">suit</p></td>
-<td align="left" valign="top"><p class="table">(<strong>string</strong>) the suit used for the dive</p></td>
-</tr>
-<tr>
-<td align="left" valign="top"><p class="table">cylinders</p></td>
-<td align="left" valign="top"><p class="table">(<strong>string</strong>) complete information of all used cylinders</p></td>
-</tr>
-<tr>
-<td align="left" valign="top"><p class="table">cylinder0-7</p></td>
-<td align="left" valign="top"><p class="table">(<strong>string</strong>) information about a specific cylinder</p></td>
-</tr>
-<tr>
-<td align="left" valign="top"><p class="table">weights</p></td>
-<td align="left" valign="top"><p class="table">(<strong>string</strong>) complete information of all used weight systems</p></td>
-</tr>
-<tr>
-<td align="left" valign="top"><p class="table">weight0-5</p></td>
-<td align="left" valign="top"><p class="table">(<strong>string</strong>) information about a specific weight system</p></td>
-</tr>
-<tr>
-<td align="left" valign="top"><p class="table">maxcns</p></td>
-<td align="left" valign="top"><p class="table">(<strong>string</strong>) maxCNS value for the dive</p></td>
-</tr>
-<tr>
-<td align="left" valign="top"><p class="table">otu</p></td>
-<td align="left" valign="top"><p class="table">(<strong>string</strong>) OTU value for the dive</p></td>
-</tr>
-</tbody>
-</table>
-</div>
-<div class="paragraph"><p><em>Subsurface</em> also exports <strong>template_options</strong> data. This data must be used as <em>CSS</em> values to provide a dynamically
-editable template. The exported data is shown in the following table:</p></div>
-<div class="tableblock">
-<table rules="all"
-width="100%"
-frame="border"
-cellspacing="0" cellpadding="4">
-<col width="50%" />
-<col width="50%" />
-<tbody>
-<tr>
-<td align="left" valign="top"><p class="table"><strong>Name</strong></p></td>
-<td align="left" valign="top"><p class="table"><strong>Description</strong></p></td>
-</tr>
-<tr>
-<td align="left" valign="top"><p class="table">font</p></td>
-<td align="left" valign="top"><p class="table">(<strong>string</strong>) font family</p></td>
-</tr>
-<tr>
-<td align="left" valign="top"><p class="table">borderwidth</p></td>
-<td align="left" valign="top"><p class="table">(<strong>int</strong>) border-width value dynamically calculated as 0.1% of the page width with minimum value of 1px</p></td>
-</tr>
-<tr>
-<td align="left" valign="top"><p class="table">font_size</p></td>
-<td align="left" valign="top"><p class="table">(<strong>double</strong>) size of fonts in vw, ranges between 1.0 and 2.0</p></td>
-</tr>
-<tr>
-<td align="left" valign="top"><p class="table">line_spacing</p></td>
-<td align="left" valign="top"><p class="table">(<strong>double</strong>) distance between text lines, ranges between 1.0 and 3.0</p></td>
-</tr>
-<tr>
-<td align="left" valign="top"><p class="table">color1</p></td>
-<td align="left" valign="top"><p class="table">(<strong>string</strong>) background color</p></td>
-</tr>
-<tr>
-<td align="left" valign="top"><p class="table">color2</p></td>
-<td align="left" valign="top"><p class="table">(<strong>string</strong>) primary table cell color</p></td>
-</tr>
-<tr>
-<td align="left" valign="top"><p class="table">color3</p></td>
-<td align="left" valign="top"><p class="table">(<strong>string</strong>) secondary table cell color</p></td>
-</tr>
-<tr>
-<td align="left" valign="top"><p class="table">color4</p></td>
-<td align="left" valign="top"><p class="table">(<strong>string</strong>) primary text color</p></td>
-</tr>
-<tr>
-<td align="left" valign="top"><p class="table">color5</p></td>
-<td align="left" valign="top"><p class="table">(<strong>string</strong>) secondary text color</p></td>
-</tr>
-<tr>
-<td align="left" valign="top"><p class="table">color6</p></td>
-<td align="left" valign="top"><p class="table">(<strong>string</strong>) border colors</p></td>
-</tr>
-</tbody>
-</table>
-</div>
-<div class="literalblock">
-<div class="title">template.html</div>
-<div class="content">
-<pre><code> border-width: {{ template_options.borderwidth }}px;</code></pre>
-</div></div>
-<div class="literalblock">
-<div class="title">output.html</div>
-<div class="content">
-<pre><code> border-width: 3px;</code></pre>
-</div></div>
-<div class="paragraph"><p>Another variable that <em>Subsurface</em> exports is <strong>print_options</strong>. This variable contains a single member:</p></div>
-<div class="tableblock">
-<table rules="all"
-width="100%"
-frame="border"
-cellspacing="0" cellpadding="4">
-<col width="50%" />
-<col width="50%" />
-<tbody>
-<tr>
-<td align="left" valign="top"><p class="table"><strong>Name</strong></p></td>
-<td align="left" valign="top"><p class="table"><strong>Description</strong></p></td>
-</tr>
-<tr>
-<td align="left" valign="top"><p class="table">grayscale</p></td>
-<td align="left" valign="top"><p class="table">Use <em>CSS</em> filters to convert the page into grayscale (should be added to body style to enable printing grayscale prints)</p></td>
-</tr>
-</tbody>
-</table>
-</div>
-<div class="literalblock">
-<div class="title">template.html</div>
-<div class="content">
-<pre><code> body {
- {{ print_options.grayscale }};
- }</code></pre>
-</div></div>
-<div class="literalblock">
-<div class="title">output.html</div>
-<div class="content">
-<pre><code> body {
- -webkit-filter: grayscale(100%);
- }</code></pre>
-</div></div>
-</div>
-<div class="sect2">
-<h3 id="_defined_css_selectors">19.3. Defined CSS selectors</h3>
-<div class="paragraph"><p>As the dive profile is placed after rendering, <em>Subsurface</em> uses special <em>CSS</em> selectors to searche
-in the HTML output. The <em>CSS</em> selectors in the following table should be added.</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>Selector</strong></p></td>
-<td align="left" valign="top"><p class="table"><strong>Type</strong></p></td>
-<td align="left" valign="top"><p class="table"><strong>Description</strong></p></td>
-</tr>
-<tr>
-<td align="left" valign="top"><p class="table">dive_{{ dive.id }}</p></td>
-<td align="left" valign="top"><p class="table">id</p></td>
-<td align="left" valign="top"><p class="table">is used to fetch the relevant dive profile</p></td>
-</tr>
-<tr>
-<td align="left" valign="top"><p class="table">diveProfile</p></td>
-<td align="left" valign="top"><p class="table">class</p></td>
-<td align="left" valign="top"><p class="table">each dive that will contain a dive profile should have this class selector in addition to the dive_{{ dive.id }} id selector</p></td>
-</tr>
-<tr>
-<td align="left" valign="top"><p class="table">dontbreak</p></td>
-<td align="left" valign="top"><p class="table">class</p></td>
-<td align="left" valign="top"><p class="table">prevents the dive with this class from being divided into two pages. This can be used
-in flow layout templates only (when data-numberofdives = 0)</p></td>
-</tr>
-</tbody>
-</table>
-</div>
-<div class="admonitionblock">
-<table><tr>
-<td class="icon">
-<img src="./images/icons/important.png" alt="Important" />
-</td>
-<td class="content">Rendering dive profiles is not supported for flow layout templates (when data-numberofdives = 0).</td>
-</tr></table>
-</div>
-</div>
-<div class="sect2">
-<h3 id="_special_attributes">19.4. Special attributes</h3>
-<div class="paragraph"><p>There are two ways of rendering- either rendering a specific number of dives in each page or make <em>Subsurface</em> try to
-fit as many dives as possible into one page (<em>flow</em> rendering).</p></div>
-<div class="paragraph"><p>The <strong>data-numberofdives</strong> data attribute is added to the body tag to set the rendering mode.</p></div>
-<div class="ulist"><ul>
-<li>
-<p>
-render 6 dives per page:
-</p>
-</li>
-</ul></div>
-<div class="literalblock">
-<div class="content">
-<pre><code> <body data-numberofdives = 6></code></pre>
-</div></div>
-<div class="ulist"><ul>
-<li>
-<p>
-render as much dives as possible:
-</p>
-</li>
-</ul></div>
-<div class="literalblock">
-<div class="content">
-<pre><code> <body data-numberofdives = 0></code></pre>
-</div></div>
-<div class="admonitionblock">
-<table><tr>
-<td class="icon">
-<img src="./images/icons/important.png" alt="Important" />
-</td>
-<td class="content">All CSS units should be in relative lengths only, to support printing on any page size.</td>
-</tr></table>
-</div>
-</div>
-</div>
-</div>
-<div class="sect1">
-<h2 id="_appendix_f_faqs">20. APPENDIX F: FAQs.</h2>
-<div class="sectionbody">
-<div class="sect2">
-<h3 id="S_APPENDIX_F">20.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’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 <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’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:</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">20.2. Some dive profiles have time discrepancies with the recorded samples from my dive computer…</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’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”.</p></div>
-</div>
-<div class="sect2">
-<h3 id="_some_dive_profiles_are_missing_from_the_download">20.3. Some dive profiles are missing from the download</h3>
-<div class="paragraph" id="DC_HISTORY"><p><em>Question</em>: I cannot download all my dives, only the most recent ones,
-even though my dive computer’s manual states that it records history of
-e.g. 999 dives?
-<em>Answer</em>: Dive history is different than the dive profiles on the log.
-The history only keeps track of the total number of dives and total
-amount of time spent below surface. The logs, on the other hand, store
-the dive profile, but they have a limited amount of memory to do so. The
-exact amount of dive profiles that can be stored on the device depends on
-sample interval and duration of the dives. Once the memory is full the
-oldest dives get overwritten with new dives. Thus we are only able to
-download the last 13, 30 or 199 dives.</p></div>
-<div class="paragraph"><p>If you have downloaded your dives to different dive logging software
-before they were overwritten, there is a good chance that Subsurface can
-import these. However, if the logs are only on your dive computer, they
-cannot be salvaged after being overwritten by new dives.</p></div>
-</div>
-</div>
-</div>
-</div>
-<div id="footnotes"><hr /></div>
-<div id="footer">
-<div id="footer-text">
-Last updated 2015-12-16 06:35:54 PST
-</div>
-</div>
-</body>
-</html>
+<!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.9" /> +<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; } + + +@media screen { + body { + max-width: 50em; /* approximately 80 characters wide */ + margin-left: 16em; + } + + #toc { + position: fixed; + top: 0; + left: 0; + bottom: 0; + width: 13em; + padding: 0.5em; + padding-bottom: 1.5em; + margin: 0; + overflow: auto; + border-right: 3px solid #f8f8f8; + background-color: white; + } + + #toc .toclevel1 { + margin-top: 0.5em; + } + + #toc .toclevel2 { + margin-top: 0.25em; + display: list-item; + color: #aaaaaa; + } + + #toctitle { + margin-top: 0.5em; + } +} +</style> +<script type="text/javascript"> +/*<+'])'); + // 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">USER MANUAL</span></p></div> +<div class="paragraph"><p><strong>Manual authors</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.5, October 2015</em></span></p></div> +<div class="paragraph"><p>Welcome as a user of <em>Subsurface</em>, an advanced dive logging program with +extensive infrastructure to describe, organize, interpret and print scuba +and free dives. <em>Subsurface</em> offers many advantages over other similar +software solutions:</p></div> +<div class="ulist"><ul> +<li> +<p> +Do you need a flexible way of logging dives using recreational equipment, + even without 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 along with a dive computer? <em>Subsurface</em> offers a standard + interface for downloading dive logs from all of these different pieces of + equipment, storing and analyzing 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, letting you access your dive log on each + operating system using a single application. +</p> +</li> +<li> +<p> +Do you use Linux or Mac, but your dive computer has only Windows- based software + for downloading dive information (e.g. Mares)? <em>Subsurface</em> provides a way of + downloading and analyzing 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, dives you’ve already logged? +</p> +</li> +<li> +<p> +Do you need a way of storing or backing up your dive log on the Internet, letting + you view your dive log from anywhere using an Internet browser? +<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> +</li> +</ul></div> +<div class="paragraph"><p>This manual explains how to use 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="_using_this_manual">1. Using this manual</h2> +<div class="sectionbody"> +<div class="paragraph"><p>When opened from within <em>Subsurface</em>, this manual does not have external controls for +paging or selecting previous pages. However, two facilities are provided:</p></div> +<div class="ulist"><ul> +<li> +<p> +The <em>SEARCH</em> function is activated by pressing control-F or command-F on +the keyboard. A text box appears at the bottom right-hand of the window (see image below). +For instance, typing the word "<em>weights</em>" into the search text +box, searches throughout the user manual. To the right of the +search text box are two arrows pointing up and down. These find +the previous and the next occurrence of the search term. +<span class="image"> +<img src=":images/usermanualfunctions.jpg" alt="User manual functions" /> +</span> +</p> +</li> +<li> +<p> +<em>PREVIOUS/NEXT LINK</em>. Move between links (underlined words that +jump to specific sections in the user manual) by right-clicking on the text of the manual. +This brings up a context menu to previous links selected. +(see image above). For instance if a link has been selected, then the option +to <em>Go Back</em> shows the text at the last link selected +(similar to the Previous Page button in a browser). Conversely the <em>Go Forward</em> option +jumps to the +text seen before selecting the <em>Go Back</em> option. The <em>Reload</em> +option reloads the complete user manual into the window. +</p> +</li> +</ul></div> +</div> +</div> +<div class="sect1"> +<h2 id="S_UserSurvey">2. The user survey</h2> +<div class="sectionbody"> +<div class="paragraph"><p>In order to develop <em>Subsurface</em> to serve its users in the best possible way, +it’s important to have user information. Upon launching <em>Subsurface</em> +and using the 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. All data the user sends is useful, and will only be +used to steer future development and to customize the software to fit the needs of +the <em>Subsurface</em> users. If you complete the survey, or click the option not to +be asked again, that should be the last communication of this type you receive. +However, if your diving and/or subsurface habits change and you wish to fill in +another survey, just launch <em>Subsurface</em> with the <em>--survey</em> option on the command line.</p></div> +</div> +</div> +<div class="sect1"> +<h2 id="S_StartUsing">3. 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 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="olist arabic"><ol class="arabic"> +<li> +<p> +The <strong>Dive List</strong> on the bottom left, showing 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 <strong>Dive List</strong> is an important tool for manipulating a dive log. +</p> +</li> +<li> +<p> +The <strong>Dive Map</strong> on the bottom right, showing the user’s dive sites on a world map +and centered on the site of the last dive selected in the <strong>Dive List</strong>. +</p> +</li> +<li> +<p> +The <strong>Info</strong> on 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> +</li> +<li> +<p> +The <strong>Dive Profile</strong> on the top right, showing a graphical dive profile of the +selected dive in the <strong>Dive List</strong>. +</p> +</li> +</ol></div> +<div class="paragraph"><p>The dividers between panels can be dragged 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 the last time the program was used.</p></div> +<div class="paragraph"><p>If a single 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. If +several dives are selected, the last highlighted dive is the <em>selected +dive</em>, but summary data of all <em>highlighted dives</em> is shown in the <strong>Stats</strong> tab +of the <strong>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_f22.jpg" alt="The Main Window" /> +</div> +</div> +<div class="paragraph"><p>The user decides which of the four panels are displayed by selecting the +<strong>View</strong> option on the main menu. This feature has 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 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, centered on the last selected dive.</p></div> +<div class="paragraph"><p>Like other functions that can be accessed via the Main Menu, these options +can also 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’s chosen language may cause <em>Subsurface</em> to use different +shortcut keys, they are not listed in this user manual.</p></div> +<div class="paragraph"><p>When the program is started for the first time, it shows no +information at all, because it does not have any dive information available. In the +following sections, the procedures to create a new logbook will be explained.</p></div> +</div> +</div> +<div class="sect1"> +<h2 id="S_NewLogbook">4. Creating a new logbook</h2> +<div class="sectionbody"> +<div class="paragraph"><p>Select <em>File → New Logbook</em> from the main menu. All existing dive data are +cleared so 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">5. Storing dive information in the logbook</h2> +<div class="sectionbody"> +<div class="paragraph"><p>Now that a new logbook is created, it is simple to add dive data it. +<em>Subsurface</em> allows several ways of adding dive data to a logbook. +1) 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 didn’t + 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="ulist"><ul> +<li> +<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 + to <a href="#S_ImportingCSVDives">Importing dives in CSV format</a>. +2) If a dive is recorded using a dive computer, the depth profile +and a large amount of additional information can be accessed. +These dives can be imported from: +</p> +</li> +<li> +<p> +The dive computer itself. See: <a href="#S_ImportDiveComputer">Importing new dive information from a Dive Computer</a> or +</p> +</li> +<li> +<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> +</li> +<li> +<p> +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> +</li> +</ul></div> +<div class="sect2"> +<h3 id="S_EnterData">5.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 the dive master or dive guide, and +some remarks about the dive. <em>Subsurface</em> can store much more +information for each dive. To add a dive to a dive log, select <em>Log +→ Add Dive</em> from the Main Menu. The program then shows three panels +on which to enter +information for a dive: two tabs in the <strong>Info</strong> panel (<strong>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_f22.jpg" alt="FIGURE: Add dive" /> +</div> +</div> +<div class="paragraph"><p>When you edit a field in 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 <strong>Notes</strong> panel (see the image below). This message is +displayed in all the panels under 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_f22.jpg" alt="Blue edit bar" /> +</div> +</div> +<div class="paragraph"><p>The <em>Apply changes</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>Apply changes</em> button, a local copy of the information +for this specific dive is saved in memory. The <em>Apply changes</em> button should ONLY be selected after all parts +of a dive have been entered. When you close 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="S_CreateProfile">5.1.1. 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 shown 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 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 shown by two right-angled red lines as seen below. +The time and depth +represented by the cursor 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 you need to drag the appropriate waypoints +downward to 20 m. To add a waypoint, double-click on +any line segment. To move an additional waypoint, drag it. +To remove a waypoint, right-click on it and choose "Remove this point" from the +context menu. Drag the waypoints to represent an +accurate +time duration for the dive. Below is a dive profile for 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 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 above. The gas mixtures of segments of the dive profile can +be changed 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 (see image below).</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>With the profile now defined, more details must be added to have +a fuller record of the dive. To do this, +the <strong>Notes</strong> and the <strong>Equipment</strong> tabs on the top left hand of the +<em>Subsurface</em> window should be used. Click on +<a href="#S_Notes_dc"><strong>this link</strong></a> for instructions on how to use these tabs.</p></div> +</div> +</div> +<div class="sect2"> +<h3 id="S_ImportDiveComputer">5.2. Importing new dive information from a Dive Computer</h3> +<div class="sect3"> +<h4 id="_connecting_and_importing_data_from_a_dive_computer">5.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, +using dive details 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 +PC-Communication mode. <strong>This could drain the dive computer’s battery</strong>. We +recommend the user checks to be sure 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.</td> +</tr></table> +</div> +<div class="paragraph"><p>To import dive information from a dive computer to a computer with +<em>Subsurface</em>, +the two pieces of equipment must 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. To set up +this communication, users need 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 achieve 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’s PC using 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. + (Refer to the manual of the specific dive computer) +</p> +</li> +<li> +<p> +In <em>Subsurface</em>, from the Main Menu, select <em>Import → Import + From Dive Computer</em>. + Dialogue <strong>A</strong> in the figure below appears: +</p> +</li> +</ol></div> +<div class="imageblock" style="text-align:center;"> +<div class="content"> +<img src="images/DC_import_f20.jpg" alt="FIGURE: Download dialogue 1" /> +</div> +</div> +<div class="paragraph"><p>Dive computers tend to keep a certain number of dives in memory, even +though these dives have already been imported to <em>Subsurface</em>. For that reason, if +the dive computer allows this, +<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).</p></div> +<div class="ulist"><ul> +<li> +<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> +</li> +<li> +<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 + specific 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> +</li> +<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> has been accidentally deleted or if there + are older dives that still need to be downloaded from the dive computer, this + box needs to be checked. 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 dive in the <em>Subsurface</em> divelog will be overwritten + by the dive record from the computer. +</p> +</li> +<li> +<p> +The checkbox marked <em>Download into new trip</em> ensures that, after upload, the downloaded dives + are grouped together as a new trip(s) in the <strong>Dive List</strong>. +</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 there are problems with downloads(see below). +</p> +</li> +<li> +<p> +Then select the <em>Download</em> button. + With communication established, you 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. Be patient. The <em>Download</em> dialogue + shows a + progress bar at the bottom of the dialogue. Remember for some dive computers + progress information could be inaccurate since the program doesn’t know how much + downloadable data there is until the download is complete. After successful download, Dialogue <strong>B</strong> + in the figure above appears. + After the dives have been downloaded, they appear in a tabular format on the right-hand + side of the dialogue (see image <strong>B</strong>, above). Each dive comprises a row in the table, with the date, duration + and depth shown. Next to each dive is a checkbox: check all the dives that need to + be transferred to the <strong>Dive List</strong>. In the case of the image above, the last six dives are + checked and will be transferred to the <strong>Dive List</strong>. Then + click the <em>OK</em> button at the bottom of the dialogue. 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. +</p> +</li> +</ul></div> +<div class="paragraph"><p>Then click the OK button. +The checked dives are transferred to the <strong>Dive List</strong>.</p></div> +<div class="ulist"><ul> +<li> +<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> +</li> +</ul></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="ulist"><ul> +<li> +<p> +Is the dive computer still in PC-communication or + Upload mode? +</p> +</li> +<li> +<p> +Is the dive computer’s battery fully charged? If not then charge or replace it. +</p> +</li> +<li> +<p> +Is the connecting cable faulty? Does the cable work 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> +</li> +<li> +<p> +Consult + <a href="#_appendix_a_operating_system_specific_information_for_importing_dive_information_from_a_dive_computer">Appendix A</a> + to be sure the correct Mount Point + was specified (see above). +</p> +</li> +<li> +<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> +</li> +</ul></div> +<div class="paragraph"><p>If the <em>Subsurface</em> computer does not recognize the USB adaptor by +showing an appropriate device name next to the Mount Point, then there is a +possibility the cable or USB adaptor is faulty. A faulty cable is the most +common cause of communication failure between a dive computer and <em>Subsurface</em> +computer. It’s also possible the <em>Subsurface</em> computer cannot interpret +the data. Perform a download for diagnostic purposes with the following +two 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 where the information will be saved. 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 analyzed. 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_Bluetooth">5.2.2. Connecting <em>Subsurface</em> to a Bluetooth-enabled dive computer</h4> +<div class="paragraph"><p>Bluetooth is becoming a more common way of communication between dive computers +and <em>Subsurface</em>, for or instance, the Shearwater Petrel +Mk2 and the OSTC Mk3. <em>Subsurface</em> provides a largely operating system independent +Bluetooth interface. Setting up <em>Subsurface</em> for Bluetooth communication requires +four steps:</p></div> +<div class="ulist"><ul> +<li> +<p> +Be sure Bluetooth is activated on the host computer running <em>Subsurface</em>. +</p> +</li> +<li> +<p> +Be sure <em>Subsurface</em> sees the Bluetooth adapter on the host computer. +</p> +</li> +<li> +<p> +Be sure the Bluetooth-enabled dive computer is Bluetooth-discoverable and in PC upload mode. +</p> +</li> +<li> +<p> +Be sure <em>Subsurface</em> is paired with the Bluetooth-enabled dive computer. +</p> +</li> +</ul></div> +<div class="paragraph"><p>Select the Download dialogue by selecting +<em>Import → Import from dive computer</em> from the <strong>Main Menu</strong>. If you check the +box labelled <em>"Choose Bluetooth download mode"</em>, the dialogue below appears. +===== On Linux or MacOS:</p></div> +<div class="imageblock" style="text-align:center;"> +<div class="content"> +<img src="images/DC_import_Bluetooth.jpg" alt="FIGURE: Download Bluetooth" /> +</div> +</div> +<div class="paragraph"><p>On the <em>Linux</em> or <em>MacOS</em> platforms the name +of the <em>Subsurface</em> computer and its Bluetooth address are shown on the right hand side, +On the left hand side, if the +computer has connected more than one local Bluetooth devices the user can use +the list box to indicate which one needs to connect to <em>Subsurface</em>. +The power state (on/off) of the Bluetooth adapter is shown below +the address and can be changed by checking the <em>Turn on/off</em> box. +If the Bluetooth address is not shown, then <em>Subsurface</em> does not see the local +Bluetooth device. Be sure the Bluetooth driver is installed correctly on the +<em>Subsurface</em> computer and check if it can be used by other Bluetooth utilities like +<em>bluetoothctl</em> or <em>bluemoon</em>. This finishes the first two steps above. +Be sure the Bluetooth-enabled dive computer is in PC-upload mode and it +is discoverable by other Bluetooth devices. Consult the manual of the dive +computer for more information. Now the third item in the list above has been finished. +Select the <em>Scan</em> button towards the bottom left of the dialogue above. After +searching, the dive computer should be listed +(perhaps as one of a number of Bluetooth devices) in the main list box on the +lefthand side of the dialogue (see image above). If this does not work, select +the <em>Clear</em> button, then scan again for Bluetooth devices using the <em>Scan</em> +button. After taking these actions <em>Subsurface</em> should see the dive computer. +The label of the discovered dive computer contains the name of the device, its +address and its pairing status. If the device is not paired and has a red +background color, a context menu can be opened by selecting the item with a +right-click. +Select the the <em>Pair</em> option and wait for the task to complete. If this dive computer +is being paired to Subsurface for the first time, it’s possible Subsurface will +request a Pass Code or PIN number. The most commonly-used Pass Code is 0000, +and this works for the Shearwater Petrel. If necessary, consult the user manual of the +dive computer being used.</p></div> +<div class="sidebarblock"> +<div class="content"> +<div class="admonitionblock"> +<table><tr> +<td class="icon"> +<img src="images/icons/important.png" alt="Important" /> +</td> +<td class="content">Currently <em>Subsurface</em> does not support Bluetooth pairing with dive +computers that require a custom PIN code. In order to pair the devices, use other +OS utilities as suggested below.</td> +</tr></table> +</div> +<div class="paragraph"><p>One way to achieve this is to use <code>bluetoothctl</code>:</p></div> +<div class="literalblock"> +<div class="content"> +<pre><code>$ bluetoothctl +[bluetooth]# agent KeyboardOnly +Agent registered +[bluetooth]# default-agent +Default agent request successful +[bluetooth]# pair 00:80:25:49:6C:E3 +Attempting to pair with 00:80:25:49:6C:E3 +[CHG] Device 00:80:25:49:6C:E3 Connected: yes +Request PIN code +[agent] Enter PIN code: 0000</code></pre> +</div></div> +</div></div> +<div class="paragraph"><p>After the devices are paired, press the <em>Save</em> button of the dialogue. +This closes the Bluetooth dialogue. Now select <em>Download</em> in the <em>Download from +dive computer</em> dialogue which should still be open. The downloaded dives are +shown on the righthand side of the download dialogue.</p></div> +<div class="sect4"> +<h5 id="_on_windows">On Windows:</h5> +<div class="imageblock" style="text-align:center;"> +<div class="content"> +<img src="images/DC_import_Bluetooth_Windows.png" alt="FIGURE: Download Bluetooth on Windows" /> +</div> +</div> +<div class="paragraph"><p>On <em>Windows</em> platforms the <em>Local Bluetooth device details section</em> on the right is not displayed as +is the case on the Linux/Mac systems. +To start a scan (by pressing the <em>Scan</em> button) +check that the Bluetooth device on the <em>Subsurface</em> computer is turned on by selecting +the dive computer from the list of available Bluetooth devices (see image above). If the dive computer +is being accessed by Subsurface for the first time, it’s possible Subsurface will +request a Pass Code or PIN number. Supply the Pass Code recommended in the user manual of the dive computer. +A Pass Code or PIN of 0000 is often the default.</p></div> +<div class="paragraph"><p>The pairing step is checked and done automatically during +the download process. If the devices have never been paired the system will ask +for your permission and put a message on the right side of the screen: <em>Add a +device, Tap to set up your DC device</em>. Always allow this pairing. After a +discovered item is selected, select the <em>Save</em> button. +Finally select the <em>Download</em> button on the <em>Download</em> dialogue and wait for the process to complete.</p></div> +<div class="admonitionblock"> +<table><tr> +<td class="icon"> +<img src="images/icons/important.png" alt="Important" /> +</td> +<td class="content">Currently <em>Subsurface</em> works only with local Bluetooth +adapters which use Microsoft Bluetooth Stack. If the local device uses +<em>Widcomm</em>, <em>Stonestreet One Bluetopia Bluetooth</em> or <em>BlueSoleil</em> drivers it +will not work. However, Bluetooth hardware/dongles from these manufacturers +(e.g. iSonic) that support the Microsoft Bluetooth Stack do work.</td> +</tr></table> +</div> +<div class="paragraph"><p>A log message on the bottom left of the <em>Remote Bluetooth device selection</em> +shows details about the current status of the Bluetooth agent. To +select another dive computer for download using the "Remote Bluetooth selection dialogue" +press the three-dots button from the <em>"Choose Bluetooth download mode"</em> option.</p></div> +<div class="admonitionblock"> +<table><tr> +<td class="icon"> +<img src="images/icons/important.png" alt="Important" /> +</td> +<td class="content"><strong>IN CASE OF PROBLEMS</strong>: If the Bluetooth adapter from the <em>Subsurface</em> computer +gets stuck and the <em>Download</em> process fails repeatedly, + <em>unpair</em> the devices and then repeat the above steps. If this is not successful, + <a href="#S_HowFindBluetoothDeviceName"><em>Appendix A</em></a> contains +information for manually setting up and inspecting the Bluetooth connection +with <em>Subsurface</em>.</td> +</tr></table> +</div> +</div> +</div> +<div class="sect3"> +<h4 id="S_DeviceNames">5.2.3. 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 a buddy’s dive computer is the +same make and model as your own and dive logs are uploaded from both dive computers +to the same <em>Subsurface</em> computer, then +you might like to call one "Alice’s Suunto D4" and the other +"Bob’s Suunto D4". Alternatively, consider a technical diver who 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 "Suunto D4 (2)". This is easily done in <em>Subsurface</em>. +On the <strong>Main Menu</strong>, select <em>Log → Edit device names</em>. A dialog box opens, showing 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">5.2.4. Updating the dive information imported from the dive computer.</h4> +<div class="paragraph"><p>With the uploaded dives in the <strong>Dive List</strong>, the information from the dive +computer is not complete and more details must be added to have +a full record of the dives. To do this, +the <strong>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 class="sect4"> +<h5 id="S_Notes_dc">Notes</h5> +<div class="paragraph"><p>To have a more complete dive record, the user needs to add +additional information by hand. The procedure +below is virtually identical for hand-entered dives and for dives downloaded from a dive computer.</p></div> +<div class="paragraph"><p>In some cases, +you must provide the date and time of the dive, for example when entering a dive by hand or when a +dive computer doesn’t provide the date and time of the dive. +(Usually the date and time of the dive, gas mixture and water temperature are +shown as obtained from the dive computer) +If the contents of the <strong>Notes tab</strong> is changed or edited in any way, the message in a blue box at +the top of the panel shows the dive is being edited. If you +click on the <strong>Notes</strong> tab, the following fields are +visible (left hand image, below):</p></div> +<div class="imageblock" style="text-align:center;"> +<div class="content"> +<img src="images/AddDive3_f22.jpg" alt="FIGURE: The Notes tab" /> +</div> +</div> +<div class="paragraph"><p>The right hand image, above, shows a <strong>Notes tab</strong> filled with dive information. +The <strong>Time</strong> field reflects the date and time of the dive. By clicking +the date, a calendar is displayed from which +you 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 over-typing the +information displayed.</p></div> +<div class="paragraph"><p><strong>Air/water temperatures</strong>: Air and water temperatures during the dive are shown +in text boxes to the right of the Start time. Many dive computers supply water +temperature information and this box may have information. +If air temperature isn’t provided by the dive computer, the first temperature reading +might be used for the air temperature. Generally this is close to the real air temperature. +If editing is required, only a value is required, the units of temperature will be +automatically supplied by +<em>Subsurface</em> (following the <em>Preferences</em>, metric or imperial units will +be used).</p></div> +<div class="paragraph"><p><strong>Location</strong>:</p></div> +<div class="admonitionblock"> +<table><tr> +<td class="icon"> +<img src="images/icons/warning2.png" alt="Warning" /> +</td> +<td class="content">Dive locations are managed as a <strong>separate</strong> part of the dive log. +The dive information in the <strong>Notes</strong> and <strong>Equipment</strong> tabs can therefore NOT be edited at the same +time as the dive site information. Save all the other dive information (e.g. +divemaster, buddy, protective gear, notes about the dive) by selecting <em>Apply changes</em> on the +<strong>Notes</strong> tab BEFORE editing the dive site information. Then supply a dive site name in the +textbox labelled <em>Location</em> on the <strong>Notes</strong> tab.</td> +</tr></table> +</div> +<div class="paragraph"><p>Type in the name of the dive site, e.g. "Tihany, Lake Balaton, Hungary". +If several dives are +made at the same location, the site information for the first dive is re-used. +Existing dive locations +can be edited by selecting (on the <strong>Dive List</strong> panel) a dive done at that site +and by opening the location information. Click the globe button on the +right of the location name (see image on the right, above). When entering a dive location name, auto location of +dive site names makes it easy to select an existing dive site name. +When typing the name of a dive site, +a dropdown list appears showing all sites with similar names. If the dive +site has been used before, click on the already-existing name. +The dive site names in the dropdown list contain either a globe symbol (indicating +existing dive sites in the <em>Subsurface</em> database) +or a <strong>+</strong> symbol (indicating dive site names that appear consistent with the +current dive site name but which haven’t been added to the dive site database). +If the present +dive site has not been used before, a message appears as follows (image <strong>A</strong> below):</p></div> +<div class="imageblock" style="text-align:center;"> +<div class="content"> +<img src="images/Locations1_f22.jpg" alt="FIGURE:Location description panel" /> +</div> +</div> +<div class="paragraph"><p>Doubleclick on the new dive site name. A panel appears to enter the coordinates and +other information about the site (image <strong>B</strong>, above). The most important +items are the coordinates of the site. There are three ways to specify coordinates:</p></div> +<div class="olist loweralpha"><ol class="loweralpha"> +<li> +<p> +Use the world map in the bottom right hand part + of the <em>Subsurface</em> window. The map displays an orange bar indicating "No location + data - Move the map and double-click to set the dive location". Doubleclick + at the appropriate place, and the orange bar disappears and the coordinates are + stored. +</p> +</li> +<li> +<p> +Use the <em>Subsurface</em> Companion app if you + have an Android or iPhone device with GPS and if the dive site coordinates + were stored using it. + <a href="#S_Companion">Click here for more information</a> +</p> +</li> +<li> +<p> +Enter by hand if the coordinates are known, using one of + four formats with latitude followed by longitude: +</p> +<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> +</li> +</ol></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. Some keyboards +don’t have the degree sign (°). It can be replaced by a <strong>d</strong> like this: N30d W20d. +If both a dive site name and coordinates have been provided, save the +dive site information by selecting the button <em>Apply changes</em> at the top of +the panel.</p></div> +<div class="paragraph"><p><strong>Important</strong>: GPS coordinates of a dive site are linked to the location +name - so <strong>saving</strong> a dive site with only coordinates and no name +causes problems. (Subsurface will think all of these +dives have the same location and try to keep their GPS coordinates the +same).</p></div> +<div class="paragraph"><p><strong>Dive site name lookup:</strong> If coordinates have been typed into the appropriate +text box, you can do an automated name lookup based on the coordinates. +This is done when <em>Subsurface</em> uses the Internet to find the name of the dive site +based on the coordinates that were typed. If a name has been found, it is +automatically inserted into the tags box. The list box +(Titled <em>Dive sites on same coordinates</em>") at the bottom +of the dive site panel contains the names of other dives sites used at the +current location. For instance if the dive site is "Blue Hole" and there are several +sites named "Blue Hole", all of them are listed.</p></div> +<div class="paragraph"><p>Enter any other contextual information about the dive site (Description and Notes), +then select <em>Apply Changes</em> to save the geolocation for this dive site. +The dive site information can later be edited by clicking the globe icon to the right of the +dive site name in the <strong>Notes tab</strong>.</p></div> +<div class="paragraph"><p><strong>Dive mode</strong>: This is a dropdown box allowing you to choose the type of dive +performed. The options are OC (Open Circuit SCUBA, the default setting, for most recreational dives), +Freedive (dive without SCUBA equipment), CCR (Closed-circuit +rebreather) and pSCR (Passive semi-closed rebreather).</p></div> +<div class="paragraph"><p><strong>Divemaster</strong>: The name of the divemaster or dive guide should be +entered in this field +which offers auto selection based on the list of dive masters in +the current logbook.</p></div> +<div class="paragraph"><p><strong>Buddy</strong>: In this field, enter the name(s) of the buddy or buddies +(separated with commas) who were on the +dive. Auto selection 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 dive suit used can be entered. +Auto selection of the suit description is available. +Some dry-suit users may choose to use this field to record what combination of +suit and thermal under suit was used.</p></div> +<div class="paragraph"><p><strong>Rating</strong>: You 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>: You 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 done 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 you starts typing a tag, the +program +will list the tags that correspond to the typing. For instance, by typing +<code>cav</code>, the tags <strong>cave</strong> and <strong>cavern</strong> are shown 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 <em>Apply changes</em> and <em>Discard changes</em> buttons are used to save all the information for tabs +in the <strong>Info</strong> panel and in the <strong>Dive Profile</strong> panel. Use them +when <strong>ALL</strong> other information has been added. The image <a href="#S_Notes_dc">at the beginning of this section</a> +shows an example of a <strong>Notes tab</strong> after completing the dive information.</p></div> +</div> +<div class="sect4"> +<h5 id="_equipment">Equipment</h5> +<div class="paragraph"><p>The Equipment tab lets you enter information about the type of +cylinder and gas used, as well as the weights used for the dive. The +message in the blue box at the top of the panel:</p></div> +<div class="imageblock" style="text-align:center;"> +<div class="content"> +<img src="images/BlueEditBar_f22.jpg" alt="FIGURE: Blue edit bar" /> +</div> +</div> +<div class="paragraph"><p>shows 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 behavior of the <strong>Dive profile</strong> +(top right-hand panel).</p></div> +<div class="paragraph" id="cylinder_definitions"><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>For hand-entered dives, this information needs to be typed in. For dive computers, +<em>Subsurface</em> often gets the gas used from the dive computer and +automatically inserts the gas composition(% oxygen or % helium) in the table. The + button +at the top right lets you add more cylinders for this dive. The dark +dust bin icon on the left lets you delete 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. +Start by selecting a cylinder type on the left-hand side of the +table. To select a cylinder, the <em>Type</em> 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 just 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 (<em>Work.press</em>) will +automatically be shown in the dialogue.</p></div> +<div class="paragraph"><p>Next, 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, save the data +either by pressing <em>ENTER</em> on the keyboard or by clicking outside the cell +containing +the cursor. Information for any additional cylinders can be added by using the<br /> +button at the top right hand. The 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 similar to that of the cylinder information. If you +click +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 <em>Type</em> 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>This can be used to select the type of weight system +used during the dive or just may start typing in the box +to specify a different weighting mechanism that will be saved by <em>Subsurface</em>. +In the <strong>Weight</strong> +field, type in the amount of weight used during the dive. After +specifying the weight +system, save the data by pressing <em>ENTER</em> on the keyboard or by clicking outside the +cell with the cursor. +It’s 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 dust bin 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> +<div class="sect3"> +<h4 id="_editing_several_selected_dives_simultaneously">5.2.5. 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 each is shown in the <strong>Dive profile</strong> tab, as well +as a few items of information +in the <strong>Notes</strong> tab (e.g. water temperature) and in the <strong>Equipment</strong> tab (e.g. gas pressures +and gas composition). Other fields remain empty. +It may be useful to simultaneously edit some of the +fields in the <strong>Notes</strong> and <strong>Equipment</strong> tabs. For instance, it’s possible +that a diver performed several dives during a single day, using identical equipment at the same +dive site, or with the same divemaster and/or buddy or tags. Instead +of completing the information for each +dive separately, select all the dives for that day in the <strong>Dive List</strong> and +insert the same information in the <strong>Notes</strong> and <strong>Equipment</strong> fields that need +identical information. This is done by editing the dive notes or the equipment for any one +of the selected dives.</p></div> +<div class="paragraph"><p>Simultaneous editing only works with fields that do not already contain information. +This means 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 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>Notes</strong> and <strong>Equipment</strong> tabs. Then, from the main menu, select <em>Log → Copy dive components</em>. +A box is presented with a selection of check boxes for most of the fields in the <strong>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 → 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">5.2.6. Adding Bookmarks to a dive</h4> +<div class="paragraph"><p>Many divers wish to annotate dives with text that indicate particular events, +e.g. "Saw dolphins", or "Released surface buoy". This is easily +done:</p></div> +<div class="ulist"><ul> +<li> +<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 that point (see <strong>A</strong> below). +</p> +</li> +<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> +<li> +<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> +</li> +<li> +<p> +Hovering the mouse over the red bookmark, the appropriate text is shown at + the bottom of the information box (see <strong>D</strong> below). +</p> +</li> +</ul></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">5.2.7. Saving the updated dive information</h4> +<div class="paragraph"><p>The information entered in the <strong>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>Notes</strong> tab. If the <em>Apply changes</em> button +is clicked, +the dive data are saved in the memory image of the dive. If the <em>Discard changes</em> +button is clicked, the newly entered dive data are +erased from the computer memory, although the dive profile is +retained. When the user exits <em>Subsurface</em> there is a final prompt to confirm +the new data should now be saved permanently on the computer disk.</p></div> +</div> +</div> +<div class="sect2"> +<h3 id="_importing_dive_information_from_other_digital_data_sources_or_other_data_formats">5.3. Importing dive information from other digital data sources or other data formats</h3> +<div class="paragraph" id="S_ImportingAlienDiveLogs"><p>If you’ve been diving for some time, it’s possible several dives were +logged using other dive log software. 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 you will need to +export the logbook(s) to an intermediate format so 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. a spreadsheet) can also be imported by +configuring the CSV import. +<em>Subsurface</em> can also import UDDF and UDCF files used by some dive log +software and some dive computers, like the Heinrichs & Weikamp DR5. Finally, +for some dive log software like Mares Dive Organizer we currently recommend you +import the logbooks first into a web service like <em>divelogs.de</em> and then import +from there with +<em>Subsurface</em>. Divelogs.de supports a few additional logbook formats that +<em>Subsurface</em> currently cannot handle.</p></div> +<div class="paragraph"><p>If the format of other software is supported natively on Subsurface, select +either <em>Import → Import log files</em> or <em>File → 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. Below is more specific information +to import data to <em>Subsurface</em>. +==== Using the universal import dialogue</p></div> +<div class="paragraph" id="Unified_import"><p>Importing dives from other software is done through a universal interface +activated by selecting <em>Import</em> from the Main Menu, then clicking on +<em>Import Log Files</em>. This brings up 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 accesses 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> +Cochran dive logs +</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> +APD Inspiration/Evolution CCR logs +</p> +</li> +<li> +<p> +LiquiVision logs +</p> +</li> +<li> +<p> +divelog.de logs +</p> +</li> +<li> +<p> +OSTC Tools 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 format and then the specific log file in the large window +containing the file list on the right 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 class="sect3"> +<h4 id="_importing_from_ostctools">5.3.1. Importing from OSTCTools</h4> +<div class="paragraph"><p><em>OSTC Tools</em> is a Microsoft-based suite of dive download and dive management tools for the OSTC +family of dive computers. <em>OSTC Tools</em> downloads dive data from the dive computer and stores it +as a binary file with file extension <em>.dive</em> . Subsurface can directly import these files when using +the universal import dialogue. From the dropdown list at the bottom right select +<em>OSTCTools Files (.dive .DIVE)</em>. This makes the <em>OSTC Tools</em> dive logs visible in the file list +panel. Select one or more dive, then click the <em>Open</em> button. The OSTC dives are shown in the +<strong>Dive List</strong> panel.</p></div> +<div class="paragraph"><p>All H&W devices supported by OSTCTools can be imported to <em>Subsurface</em>. This includes +OSTC, OSTC Mk2, OSTC 2N/2C, OSTC3, OSTC Sport, and probably although untested, Frog, OSTC2 and +OSTC CR.</p></div> +<div class="paragraph"><p>Please remember that OSTCTools is <strong>not</strong> a true diving log software, but rather a useful set of tools +for analysis and management of OSTC devices. Only raw dive computer data will be +imported to <em>Subsurface</em>; you have to manually complete the rest of the +data you want (buddies, equipment, notes, etc).</p></div> +</div> +<div class="sect3"> +<h4 id="_importing_from_mares_dive_organizer_v2_1">5.3.2. Importing from Mares Dive Organizer V2.1</h4> +<div class="paragraph"><p>Since Mares uses 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 gateway to extract the dive log information.</p></div> +<div class="olist arabic"><ol class="arabic"> +<li> +<p> +Export the dive log data from Mares Dive Organizer to your + desktop, using + a <em>.sdf</em> file name extension. Refer to <a href="#Mares_Export">Appendix C</a> for more + information. +</p> +</li> +<li> +<p> +Data should then be imported into <em>www.divelogs.de</em>. You will first need to create a user + account in + <em>www.divelogs.de</em>. Log into that web site, then + select <em>Import Logbook → Dive Organizer from the menu on the left hand side. + The instructions must be carefully followed to transfer the dive information + (in _.sdf</em> format) from the Dive Organizer database to <em>www.divelogs.de</em>. +</p> +</li> +<li> +<p> +Finally, import the dives + from <em>divelogs.de</em> to <em>Subsurface</em>, using the instructions below. +</p> +</li> +</ol></div> +</div> +<div class="sect3"> +<h4 id="S_ImportingDivelogsDe">5.3.3. Importing dives from <strong>divelogs.de</strong></h4> +<div class="paragraph"><p>Importing dive information from <em>divelogs.de</em> is simple, using a single +dialogue box. The <em>Import → Import from Divelogs.de</em> option should be selected +from the Main Menu. This +brings up a dialogue box (see image <strong>A</strong> below). Enter a +user-ID and password for <em>divelogs.de</em> 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 shown (see image <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">5.3.4. 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). The <em>CSV</em> format is a universal +simplified format that allows easy information exchange between different computers or +software packages. For an introduction to CSV-formatted files see <a href="#S_CSV_Intro">A Diver’s +Introduction To CSV Files</a>. <em>Subsurface</em> dive logs can also be exported in <em>CSV</em> format to +other software that reads this format. See <a href="#S_Appendix_D">APPENDIX D: Exporting a spreadsheet +to CSV format</a> for information that may be helpful for importing spreadsheet-based data +into <em>Subsurface</em>.</p></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>You can view a <em>CSV</em> file by using an ordinary text editor. It’s normally organized into +a single line that provides the headers (or <em>field names</em> or <em>column headings</em>) of the data +columns, followed by the data, one record per line.</p></div> +<div class="paragraph"><p>There are two types of <em>CSV</em> dive logs that can be imported into <em>Subsurface</em>:</p></div> +<div class="olist arabic"><ol class="arabic"> +<li> +<p> +<em>CSV dive details</em>: This dive log format contains similar information to that of a + typical written dive log, e.g. dive date and time, dive depth, dive duration, names of + buddy and divemaster and information about cylinder pressures before and + after the dive, as well as comments about the dive. All the data for a single + dive go on a single line of text, following the order of the column headings. +</p> +</li> +<li> +<p> +<em>CSV dive profile</em>: This dive log format includes much more information about a single + dive. For instance there may be information at 30-second intervals, indicating depth, water + temperature, and cylinder pressure at that moment in time. Each line contains + the information for a single instant in time during the dive, 30 seconds after that + of the previous instant. Many lines + are required to complete the depth profile information for a single dive. This is a common + export format used by closed-circuit rebreather (CCR) dive equipment and many software + packages that handle dive computer data and/or dive logs. +</p> +</li> +</ol></div> +<div class="paragraph"><p>Before being able to import the <em>CSV</em> data to <em>Subsurface</em> <strong>you needs to know a few +things about the data being imported</strong>:</p></div> +<div class="olist loweralpha"><ol class="loweralpha"> +<li> +<p> +Which character separates the different columns within a single line of + data? This field separator should be either a comma (,) a semicolon (;) or a TAB character. + This can be determined by opening the file with a text editor. If it is + comma-delimited or semicolon-delimited, the comma or semicolon + characters between the values are clearly visible. If these are not evident and + the numbers are aligned in columns, + the file is probably TAB-delimited (i.e. it uses a TAB as a field separator). +</p> +</li> +<li> +<p> +Which data columns need to be imported into <em>Subsurface</em>? Is it a <em>CSV dive details</em> + file or a <em>CSV dive profile</em> file? Open the file using a text editor and note + the titles of the columns to be imported and their column positions. +</p> +</li> +<li> +<p> +Is the numeric information (e.g. dive depth) in metric or in imperial units? +</p> +</li> +</ol></div> +<div class="paragraph"><p>With this information, importing the data into <em>Subsurface</em> is +straightforward. Select +<em>Import → Import Log Files</em> from the main menu. In the resulting file +selection menu, select <em>CSV files</em> (towards the bottom right). This shows all .CSV files in the selected +directory. Select the file that needs to be imported. A configuration panel +appears as depicted below:</p></div> +<div class="imageblock" style="text-align:center;"> +<div class="content"> +<img src="images/csv_import1_f20.jpg" alt="FIGURE: CSV download dialogue 1" /> +</div> +</div> +<div class="paragraph"><p>At the top left, there is a dropdown list containing pre- configured +settings for common dive computers and software packages. + If the <em>CSV</em> file being imported originated from any of +these pre-configured items, select it. Otherwise use the <em>Manual Import</em> +option. The configuration panel also has dropdown lists for the specification of the appropriate +field separator (Tab, comma or semicolon), the date format used in the <em>CSV</em> file, +the time units (seconds, minutes or minutes:seconds), as well as the unit system +(metric or imperial). Selecting the appropriate options among these is critical for +the successful data import.</p></div> +<div class="paragraph"><p>Complete this by ensuring that all the data columns have the appropriate +column headings. The top blue row of the data table contains the column +headings found in the <em>CSV</em> data file. The blue row of balloons immediately above these +contains the names understood by <em>Subsurface</em>. These balloons can be moved using a drag-and-drop action. For +instance, <em>Subsurface</em> expects the column heading for Dive number (" # ") to be "Dive # ". If +the column heading that <em>Subsurface</em> expects is not in the blue row, drag the +appropriate balloon from the upper area and drop it in the appropriate blue +cell at the top of the table. To indicate the correct column for "Dive #", drag +the ballooned item labelled "Dive # " and drop it in the blue +cell immediately above the white cell containing " # ". This is depicted in +the image below.</p></div> +<div class="imageblock" style="text-align:center;"> +<div class="content"> +<img src="images/csv_import2_f20.jpg" alt="FIGURE: CSV download dialogue 2" /> +</div> +</div> +<div class="paragraph"><p>Continue in this way to ensure all the column headings in the blue row of +cells correspond to the headings listed in the top part of the dialogue. +When finished, select the <em>OK</em> button on the bottom right of the dialogue. +The data from the <em>CSV</em> file are imported and shown in the <strong>Dive List</strong> panel.</p></div> +<div class="sidebarblock" id="S_CSV_Intro"> +<div class="content"> +<div class="paragraph"><p><strong>A Diver’s Introduction to <em>CSV</em> Files</strong></p></div> +<div class="admonitionblock"> +<table><tr> +<td class="icon"> +<img src="images/icons/important.png" alt="Important" /> +</td> +<td class="content"><em>CSV</em> is an abbreviation for a data file format: <em>Comma-Separated Values</em>. It is a +file format that lets you view or edit information using a text editor like +Notepad (Windows), gedit (Linux) or TextWrangler (OS/X). There are two main advantages of +the <em>CSV</em> format. First, the data are easily editable as text without any proprietary software. +Second, all information is human-readable, not obscured by any custom or +proprietary attributes that proprietary software inserts into files. +Because of its simplicity the <em>CSV</em> 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>, <em>CSV</em> files can also +be used to import information from other sources like spreadsheet-based dive logs and +some dive computers.</td> +</tr></table> +</div> +<div class="paragraph"><p><em>CSV</em> files can be created or edited with a normal text editor. The most important attribute of a +<em>CSV</em> 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 <em>CSV</em> file. <em>CSV</em> files are +normally organized 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>The above 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 <em>CSV</em> 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>When a <em>CSV</em> file is selected for import, <em>Subsurface</em> displays the column headers as well as some of the data +in the first few lines of the <em>CSV</em> file, making it much easier to work with <em>CSV</em> files. +<em>CSV</em> files can be used in many contexts for importing data into a <em>Subsurface</em> dive log. +Knowing a few basic things about the content of the <em>CSV</em> file helps with a smooth import +of the dives into <em>Subsurface</em>.</p></div> +</div></div> +<div class="admonitionblock"> +<table><tr> +<td class="icon"> +<img src="images/icons/important.png" alt="Important" /> +</td> +<td class="content">But, the <em>CSV</em> import has a couple of caveats. Avoid some special characters +like ampersand (&), less than (<), greater than (>) and double quotes (") as part +of the numbers or text within a cell. The +file should use UTF-8 character set, if using non-ASCII characters. Also the +size of the <em>CSV</em> file might cause problems. Importing 100 dives at a time +(<em>CSV dive details</em>) works, but larger files might exceed +the limits of the parser used. When encountering problems with <em>CSV</em> imports, first try with +a smaller file to make sure everything works.</td> +</tr></table> +</div> +</div> +</div> +</div> +<div class="sect2"> +<h3 id="S_Companion">5.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 <em>Android device</em> or +<a href="#S_iphone"><em>iPhone</em></a> with GPS, the coordinates +for the diving +location can be automatically passed to the <em>Subsurface</em> dive log. The Companion App +stores dive locations on a dedicated Internet server. <em>Subsurface</em> can collect +the locations from the server. +To do this:</p></div> +<div class="sect3"> +<h4 id="_create_a_companion_app_account">5.4.1. Create a Companion App account</h4> +<div class="ulist"><ul> +<li> +<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 giving you access to the file server and Companion App capabilities. +</p> +</li> +<li> +<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&fdid=org.subsurface">F-Droid</a>. +</p> +</li> +</ul></div> +</div> +<div class="sect3"> +<h4 id="_using_the_subsurface_companion_app_on_an_android_smartphone">5.4.2. Using the Subsurface companion app on an Android smartphone</h4> +<div class="paragraph"><p>On first use the app has three options:</p></div> +<div class="ulist"><ul> +<li> +<p> +<em>Create a new account.</em> Equivalent to registering in the <em>Subsurface</em> companion + page using an Internet browser. You can request a <strong>DIVERID</strong> using this option, + but it’s supplied via email and followed up by interaction with the + <a href="http://api.hohndel.org/login/"><em>Subsurface companion web page</em></a> to + activate the account. +</p> +</li> +<li> +<p> +<em>Retrieve an account.</em> If users forget their <strong>DIVERID</strong> they will receive an email + to recover the number. +</p> +</li> +<li> +<p> +<em>Use an existing account.</em> Users are prompted for their <strong>DIVERID</strong>. The app saves + this <strong>DIVERID</strong> and doesn’t ask for it again unless you use the <em>Disconnect</em> menu + option (see below). +</p> +</li> +</ul></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, by selecting <em>File → Preferences → Defaults</em> from the main menu +in <em>Subsurface</em> itself. +This helps synchronization 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 you are 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 +shows with 3 options:</p></div> +<div class="ulist"><ul> +<li> +<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> +</li> +<li> +<p> +Use Map: This option lets you fix a position by searching a world map. A + world map is shown (see <strong>B</strong> below) on which you can show the desired position + with a <em>long press</em> on the touch + sensitive screen (if the marked location is wrong, simply choose a new location) + and select the check symbol in the upper right. A dialog is shown letting you enter the + name of the dive location and the date and time of the dive (see <strong>C</strong> below). In order to import this + dive location in <em>Subsurface</em> you should set the time to agree with the time of + that dive on the dive computer. +</p> +</li> +</ul></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="ulist"><ul> +<li> +<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 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> +</li> +</ul></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 +showing they need to be uploaded to the server. You +can select individual dive locations from the list. A selected location has a +check mark in the selection box on the left. Group operations (like <em>Delete</em> or <em>Send</em>) +are performed on several selected locations.</p></div> +<div class="paragraph"><p>Dive locations in this list can be viewed in two ways: a list of locations or a +map showing them. 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 you select 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 you select 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. +After editing and saving a dive location (see <strong>C</strong> above), +upload it to the web +service, as explained below. +</p> +</li> +</ul></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 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">Be careful! 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> +<li> +<p> +<em>User ID.</em> The DIVERID obtained by registering as described above. The easiest way to + get it is to copy and paste from the confirmation email or just type it in. +===== Synchronisation +</p> +</li> +<li> +<p> +<em>Synchronize on startup</em>. If selected, dive locations in the Android device and those + on the web service synchronize each time the app is started. +</p> +</li> +<li> +<p> +<em>Upload new dives.</em> If selected, each time the user adds a dive location it is + automatically sent to the server. +</p> +</li> +</ul></div> +</div> +<div class="sect4"> +<h5 id="_background_service">Background service</h5> +<div class="paragraph"><p>Instead of entering an unique dive location, you can leave the service running +in the background of your Android device, allowing a continuous collection of GPS locations.</p></div> +<div class="paragraph"><p>The settings below define the behavior of the service:</p></div> +<div class="ulist"><ul> +<li> +<p> +<em>Min duration.</em> In minutes. The app will try to get a location every X minutes + until stopped by the user. +</p> +</li> +<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 diver 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 50 m +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 diver is not moving, only one location is saved. +If the diver 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="ulist"><ul> +<li> +<p> +<em>Mailing List.</em> The mail box for <em>Subsurface</em>. Users can send an email to the +Subsurface mailing list. +</p> +</li> +<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>Starts 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 admittedly a badly named option that disconnects the app from the server. +It resets 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 your 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="S_iphone">5.4.3. Using the Subsurface companion app on an <em>iPhone</em> to record dive locations</h4> +<div class="paragraph"><p>The iPhone interface is quite simple. Type the user ID (obtained +during registration) into the space reserved for it, then select "Dive in" +(see left part of the image below) and start collecting dive location information.</p></div> +<div class="imageblock" style="text-align:center;"> +<div class="content"> +<img src="images/iphone.jpg" alt="FIGURE: Using iPhone companion application" width="640" /> +</div> +</div> +<div class="paragraph"><p>Dives can be added automatically or manually. In manual mode, a dive location or waypoint is added to the GPS input stream. In automatic +mode, a continuous path of GPS locations is created from which, +after import, Subsurface can select the appropriate GPS +locations based on the times of dives. The default mode for the +<em>iphone</em> is automatic. When adding a dive, the +location service is started automatically and a red bar appears at the bottom +of the screen. After the dive, click on the red +bar to end the location service. While the location +service is running you can only add dives manually.</p></div> +<div class="paragraph"><p>You can edit the site name afterwards by selecting the dive +from the dive list and clicking on the site name. There are no other +editable fields. The dive list is automatically uploaded from the iPhone +to the web service. There isn’t an option to +trigger upload manually.</p></div> +</div> +<div class="sect3"> +<h4 id="_downloading_dive_locations_to_the_em_subsurface_em_divelog">5.4.4. 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 +→ 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 start 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, you can update the locations +of the newly entered or uploaded dives in <em>Subsurface</em>. That applies the +coordinates and names entered on the app to all the new dives that match the +date-times of the uploaded GPS localities. If you have 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 depends +on agreeing date-time information between the two devices. Although <em>Subsurface</em> has +a wide range tolerance, it may not be able to identify the appropriate dive if there’s +a large difference between the time in the dive computer and that of the Android device. +That results 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). +<em>Subsurface</em> may also 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 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="ulist"><ul> +<li> +<p> +<em>Background service</em> may fill the location list with + unnecessary locations that don’t correspond to the exact dive point but do correspond to the boat’s route. + Right now, these locations are difficult to delete from the server. In some situations it + is better 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 you want to keep the location list clear to see dives in the web service map display (see above). +</p> +</li> +<li> +<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> +</li> +</ul></div> +</div> +</div> +<div class="sect2"> +<h3 id="S_LoadImage">5.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. To match each photograph with a specific +dive, <em>Subsurface</em> lets you 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_synchronizing_between_dive_computer_and_camera">5.5.1. Loading photos and synchronizing 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 up the time synchronization dialog, shown below. But be +aware that the time +synchronization 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 synchronize, +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> synchronizes in three ways:</p></div> +<div class="ulist"><ul> +<li> +<p> +<strong>Pro-actively</strong>: Before the dive, ensure synchronization of the dive computer time settings with + the time settings of the camera by changing the date-time settings on one or both of these devices. +</p> +</li> +<li> +<p> +<strong>Manually</strong>: If you wrote down the exact camera time at the start of a dive, the + difference in time between the two devices can be determined. As long as the device + settings for time has not been changed in either device, you could write down the times of + both devices after the dive or even at the end of the day. You 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>, shown 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 synchronization is done. +</p> +</li> +</ul></div> +<div class="imageblock" style="text-align:center;"> +<div class="content"> +<img src="images/LoadImage3b_f20.jpg" alt="FIGURE: Synchronization dialog" /> +</div> +</div> +<div class="ulist"><ul> +<li> +<p> +<strong>By photograph</strong>: There is a very slick way of synchronizing. If you take a + photograph of the face of the dive computer showing the time, then <em>Subsurface</em> can get + the exact time the photograph was taken, using the metadata the camera stores within + each photo. To do this, use the bottom half of the <em>Time shift</em> dialog. If you use + the bottom part, the top part of the dialog is ignored. Click on + the horizontal bar called "<em>Select image of dive computer showing time</em>. This brings up + a file browser letting you select the photograph of the dive computer time. 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 it 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 it can synchronize. + Image <strong>B</strong> above shows a photograph of the face of the dive computer and with the date-time tool set to the + date-time. +</p> +</li> +</ul></div> +<div class="paragraph"><p>If the timestamp of a photograph is more than 30 minutes before or after the dive, it is not placed on +the dive profile.</p></div> +</div> +<div class="sect3"> +<h4 id="_viewing_the_photos">5.5.2. Viewing the photos</h4> +<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>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. + To view the photos on the dive profile, activate the <em>show-photos</em> button in the tool bar + to the left of the dive profile: +</p> +</li> +</ul></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>This results in a profile display as in the image below:</p></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 you hover the mouse over any of the photo icons, 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 added photographs. (see the image below). Note that the thumbnail +has a small dustbin icon in the bottom right hand corner (see image above). Selecting +the dustbin removes the image from the dive. Be careful +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">5.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>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 +show 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">5.5.4. Photos on an external hard disk</h4> +<div class="paragraph"><p>Most underwater photographers store photos on an external drive. If such a drive can be mapped by the operating system +(almost always the case) the photos can be directly accessed by <em>Subsurface</em>. This eases 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 synchronization (see text above) is used. +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. +If the external drive with the photos is re-connected, the photos can be seen in the normal way.</p></div> +</div> +<div class="sect3"> +<h4 id="S_FindMovedImages">5.5.5. Moving photographs among directories, hard disks or computers</h4> +<div class="paragraph"><p>After a photograph has been loaded into <em>Subsurface</em> and associated with a specific dive, the directory + where the photo lies is stored, letting <em>Subsurface</em> find the photograph when the dive is + opened again. If the photo or the whole photo collection is moved to another drive or to a different + machine, the directory structure will be different to that of the original uploaded + photo. When this happens, <em>Subsurface</em> looks for the photos at their original location before they were moved, + cannot find them and cannot display them. Because after moving photos, large numbers of photos + may need to be deleted and re-imported from the new location, <em>Subsurface</em> has a mechanism that eases the + process of updating the directory information for each photo: automatic updates using fingerprints.</p></div> +<div class="paragraph"><p>When a photo is loaded into <em>Subsurface</em>, a fingerprint for the image is calculated and stored with the + other reference information for that photo. After moving a photo collection (that has already been loaded + into <em>Subsurface</em>) to a different directory, disk or computer, <em>Subsurface</em> can:</p></div> +<div class="ulist"><ul> +<li> +<p> +look through a particular directory (and all its subdirectories recursively) where photos have been moved +to, +</p> +</li> +<li> +<p> +calculate fingerprints for all photos in this directory, and +</p> +</li> +<li> +<p> +if there is a match between a calculated fingerprint and the one originally calculated when a photo was + loaded into <em>Subsurface</em> (even if the original file name has changed), automatically update the + directory information so that <em>Subsurface</em> can find the photo in the new moved directory. +</p> +</li> +</ul></div> +<div class="paragraph"><p>This is done by selecting from the Main Menu: <em>File → Find moved images</em>. This brings up a window within + which the NEW directory of the photos needs to be specified. Select the appropriate directory and click + the <em>Scan</em> button towards the bottom right of the panel. The process may require several minutes to + complete, after which <em>Subsurface</em> will show the appropriate photographs when a particular dive is opened.</p></div> +<div class="sidebarblock" id="Image_fingerprint_upgrade"> +<div class="content"> +<div class="paragraph"><p><strong>Upgrading existing photo collections without fingerprints</strong></p></div> +<div class="admonitionblock"> +<table><tr> +<td class="icon"> +<img src="images/icons/important.png" alt="Important" /> +</td> +<td class="content"><em>Subsurface</em> automatically calculates fingerprints for all images that it can access. +When manipulating images, be sure all the images associated with the dive log can be accessed by <em>Subsurface</em>.</td> +</tr></table> +</div> +<div class="paragraph"><p><em>Subsurface</em> automatically checks and, if necessary, updates the fingerprints associated with a single dive if: +- The images associated with that dive are visible as thumbnails on the <strong>Dive Profile</strong>. +- If you edit anything in the <strong>Notes tab</strong> panel and save the edits by selecting <em>Apply changes</em>.</p></div> +</div></div> +</div> +</div> +<div class="sect2"> +<h3 id="_logging_special_types_of_dives">5.6. Logging special types of dives</h3> +<div class="sect3"> +<h4 id="S_MulticylinderDives">5.6.1. Multicylinder dives</h4> +<div class="paragraph"><p><em>Subsurface</em> easily handles dives involving more than one cylinder. Multi-cylinder diving usually happens +(a) if a diver doesn’t have enough gas for the complete dive in a single cylinder; (b) if a diver +needs more than one gas mixture because of the depth or the decompression needs of the dive. For this reason +multi-cylinder dives are often used by technical divers who dive deep or long. As far +as <em>Subsurface</em> is concerned, there are only two types of information that need to be provided:</p></div> +<div class="ulist"><ul> +<li> +<p> +<strong>Describe the cylinders used during the dive</strong> This is performed in the <strong>Equipment tab</strong> of + the <strong>Info</strong> panel, as <a href="#cylinder_definitions">described above</a>. Enter the cylinders one by one, + specifying each’s characteristics and the gas composition within it. +</p> +</li> +<li> +<p> +<strong>Record the times at which the switch from one cylinder to another was done:</strong> This is information + tracked by some dive computers (provided the diver indicated these changes to the dive computer + by pressing specific buttons). If the dive computer does not provide the information, the diver has to + record these changes using a different method, e.g. writing it on a slate. +</p> +</li> +<li> +<p> +<strong>Record the cylinder changes on the dive profile</strong>: If the latter option + was followed, the diver needs to indicate the gas change event by right-clicking at the appropriate point + in time on the <strong>Dive Profile</strong> panel and indicating the cylinder to which the change was made. After + right-clicking, follow the context menu to "Add gas change" and select the appropriate cylinder from + those defined during the first step, above (see image below). If the + <strong>tank bar</strong> button in the toolbar has been activated, the cylinder switches are also indicated in the + tank bar. +</p> +</li> +</ul></div> +<div class="paragraph"><p>When this is complete, <em>Subsurface</em> indicates the appropriate use of cylinders in the dive profile. +Below is a multi-cylinder dive, starting off with EAN28, then changing cylinders to EAN50 after 26 minutes +for decompression.</p></div> +<div class="imageblock" style="text-align:center;"> +<div class="content"> +<img src="images/multicylinder_dive.jpg" alt="FIGURE: Multicylinder profile" /> +</div> +</div> +</div> +<div class="sect3"> +<h4 id="_sidemount_dives">5.6.2. Sidemount dives</h4> +<div class="paragraph"><p>Sidemount diving is just another form of multi-cylinder diving, often with both or all cylinders having +the same gas mixture. Although it’s a popular configuration for cave divers, Sidemount +diving can be done by recreational divers who’ve completed the appropriate training. sidemount +dive logging involves three steps, exactly as with multi-cylinder dives above:</p></div> +<div class="ulist"><ul> +<li> +<p> +<strong>During the dive, record cylinder switch events</strong>. Since sidemount diving normally involves two + cylinders with air or with the same gas mixture, <em>Subsurface</em> distinguishes between these different + cylinders. In contrast, many dive computers that allow gas switching only distinguish between different + <em>gases</em> used, not among different <em>cylinders</em> used. This means when sidemount dives are downloaded + from these dive computers, the switching event between cylinders with the same gas is not downloaded. This may mean + that a diver may have to keep a written log of cylinder switch times using a slate, or (if the dive computer + has the capability) marking each cylinder switch with a bookmark that can be retrieved later. Returning + from a dive with the times of cylinder changes is the only tricky part of logging sidemount dives. +</p> +</li> +<li> +<p> +<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>Info Panel</strong> (see + image below where two 12 litre cylinder were used). +</p> +</li> +<li> +<p> +<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 shown on the dive profile. + Cylinder changes are recorded by right-clicking at the appropriate point on the dive profile, 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 shown 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 shown 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 in the image below. +</p> +</li> +</ul></div> +<div class="imageblock" style="text-align:center;"> +<div class="content"> +<img src="images/sidemount1.jpg" alt="FIGURE: Sidemount profile" /> +</div> +</div> +<div class="paragraph"><p>This section gives an example of the versatility of <em>Subsurface</em> as a dive logging tool.</p></div> +</div> +<div class="sect3"> +<h4 id="S_sSCR_dives">5.6.3. Semi-closed circuit rebreather (SCR) dives</h4> +<div class="admonitionblock"> +<table><tr> +<td class="icon"> +<img src="images/halcyon_RB80.jpg" alt="Note" /> +</td> +<td class="content">Passive semi-closed rebreathers (pSCR) are a technical advance in diving equipment that +recirculates the breathing gas a diver uses, while removing carbon dioxide from +the exhaled gas. While a small amount (typically a tenth) of the exhaled breathing gas is released into the water, +a small amount of fresh gas is released from the back gas cylinder (typically containing nitrox). +A diver using a single cylinder of breathing gas can therefore dive for much longer periods than +using a recreational open-circuit configuration. With pSCR equipment, a very small amount of breathing +gas is released every time the diver inhales. With active SCR (aSCR) equipment, in contrast, a small amount of +breathing gas is released continuously from the back cylinder.</td> +</tr></table> +</div> +<div class="paragraph"><p>To log pSCR dives, no special procedures are required. Use the normal steps outlined above:</p></div> +<div class="ulist"><ul> +<li> +<p> +Select pSCR in the <em>Dive Mode</em> dropdown list on the <strong>Info</strong> panel. +</p> +</li> +<li> +<p> +pSCR diving often involves gas changes, requiring an additional cylinder. + Define all the appropriate cylinders as described above + and indicate the cylinder/gas changes as described above in the section on <a href="#S_MulticylinderDives">multicylinder dives</a>. +</p> +</li> +</ul></div> +<div class="paragraph"><p>If a pSCR <em>Dive Mode</em> has been selected, the dive ceiling for that is adjusted for the oxygen +drop across the mouthpiece, which often requires longer decompression periods. Below is a dive profile +of a pSCR dive using EAN36 on the back cylinder and oxygen for decompression. Note that this dive lasted +over two hours.</p></div> +<div class="imageblock" style="text-align:center;"> +<div class="content"> +<img src="images/pSCR_profile.jpg" alt="FIGURE: pSCR profile" /> +</div> +</div> +</div> +<div class="sect3"> +<h4 id="S_CCR_dives">5.6.4. Closed circuit rebreather (CCR) dives</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. They also do two things to maintain a +breathable oxygen concentration: +a) remove carbon dioxide from the exhaled gas +b) regulate the oxygen concentration to remain within safe diving limits. +The CCR interface of <em>Subsurface</em> is currently experimental +and under active development. Subsurface currently supports Poseidon MkVI +and APD Discovery/Evolution dive computers. In contrast to a conventional recreational +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 it +imports dive log data from other digital databases: one dive at a time.</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 → Import +log files</em> to bring up the <a href="#Unified_import">universal import dialogue</a>. As +explained in that section, the bottom right +hand of the import dialogue contains a dropdown list (labled <em>Filter:</em>) of appropriate devices +that currently include(Poseidon) MkVI or APD log viewer files. Import for other +CCR equipment is under active development. Having selected the appropriate CCR format and +the directory where the original dive logs have been stored from the CCR dive +computer, 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, +click the <em>Open</em> button at the bottom right hand of the universal import dialogue. +The selected dive is imported to the <em>Subsurface</em> dive list.</p></div> +</div> +<div class="sect4"> +<h5 id="_displayed_information_for_a_ccr_dive">Displayed information for a CCR 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 contrast to recreational +equipment (where pO<sub>2</sub> values are calculated based on gas composition and dive depth), +CCR equipment provide actual measurements of pO<sub>2</sub>, derived from oxygen sensors. +In this case the graph for oxygen partial pressure +should be fairly flat, reflecting the setpoint settings during the dive. The mean +pO<sub>2</sub> is NOT the mean oxygen partial pressure as given by the CCR equipment, but +a value calculated by <em>Subsurface</em> as follows:</p></div> +<div class="ulist"><ul> +<li> +<p> +For TWO O<sub>2</sub> sensors the mean value of the two sensors are given. +</p> +</li> +<li> +<p> +For THREE-sensor systems (e.g. APD), the mean value is also used. However + differences of more than 0,1 bar in the simultaneous readings of different sensors are + treated as false. If one of the three sensors provides false data, it is ignored. +</p> +</li> +<li> +<p> +If no sensor data are available, the pO<sub>2</sub> value is assumed to be equal to the setpoint. +</p> +</li> +</ul></div> +<div class="paragraph"><p>The mean pO<sub>2</sub> of the sensors is indicated with a green line,</p></div> +<div class="paragraph"><p>The oxygen setpoint values as well as the readings from the individual +oxygen sensors can be shown. The display of additional CCR information is turned on by +checking the appropriate boxes in the <em>Preferences</em> panel (accessible by +selecting <a href="#S_CCR_options"><em>File → Preferences → Graph</em></a>). This part of +the <em>Preferences</em> panel is shown in the image below, representing two checkboxes that modify +the display of pO<sub>2</sub> when the appropriate toolbar button on the Dive Profile +has been checked.</p></div> +<div class="imageblock" style="text-align:center;"> +<div class="content"> +<img src="images/CCR_preferences_f20.jpg" alt="FIGURE: CCR preferences panel" /> +</div> +</div> +<div class="paragraph"><p>Checking any of these boxes allows the display of additional oxygen-related +information whenever the pO<sub>2</sub> toolbar button on the <em>Profile</em> panel is activated. +The first checkbox allows the display of setpoint information. This is a red line +superimposed on the green oxygen partial pressure graph and allows a comparison of the +mean measured oxygen partial pressure and the setpoint values, as shown below.</p></div> +<div class="imageblock" style="text-align:center;"> +<div class="content"> +<img src="images/CCR_setpoint_f20.jpg" alt="FIGURE: CCR setpoint and po2 graph" /> +</div> +</div> +<div class="paragraph"><p>The second checkbox allows the display of the data from each individual oxygen sensor +of the CCR equipment. The data for each sensor is colour-coded as follows:</p></div> +<div class="ulist"><ul> +<li> +<p> +Sensor 1: grey +</p> +</li> +<li> +<p> +Sensor 2: blue +</p> +</li> +<li> +<p> +Sensor 3: brown +</p> +</li> +</ul></div> +<div class="paragraph"><p>The mean oxygen pO<sub>2</sub> is indicated by the green line. This allows the direct comparison +of data from each of the oxygen sensors, useful for detecting abnormally low or erratic +readings from a particular sensor.</p></div> +<div class="imageblock" style="text-align:center;"> +<div class="content"> +<img src="images/CCR_sensor_data_f20.jpg" alt="FIGURE: CCR sensor data graph" /> +</div> +</div> +<div class="paragraph"><p>The setpoint data can be overlaid on the oxygen sensor data by activating both of the above +check boxes. Partial pressures for nitrogen (and helium, if applicable) are shown in the +usual way as for open circuit dives.</p></div> +<div class="paragraph"><p><em>Events</em>: Several events are logged, e.g. switching the mouthpiece to open circuit. +These events are indicated by yellow triangles and, if one hovers over a triangle, +a description of that event is given as the bottom line in the <a href="#S_InfoBox">Information Box</a>.</p></div> +<div class="paragraph"><p><em>Cylinder pressures</em>: Some CCR dive computers like the Poseidon MkVI record the +pressures of the oxygen and diluent cylinders. The pressures of these two cylinders +are shown as green lines overlapping the depth profile. In addition, start and +end pressures for both oxygen and diluent cylinders are shown in the <em>Equipment Tab</em>. +Below is a dive profile for a CCR dive, including an overlay +of setpoint and oxygen sensor data, as well as the cylinder pressure data. In this +case there is agreement from the readings of the two oxygen sensors.</p></div> +<div class="imageblock" style="text-align:center;"> +<div class="content"> +<img src="images/CCR_dive_profile_f22.jpg" alt="FIGURE: CCR dive profile" /> +</div> +</div> +<div class="paragraph"><p><em>Equipment-specific information</em>: Equipment-specific information gathered by +<em>Subsurface</em> is shown in the <a href="#S_ExtraDataTab">Extra data tab</a>. This may include setup information +or metadata about the dive.</p></div> +<div class="paragraph"><p>The deco ceiling calculated by Subsurface is not very accurate because the precise pressure of nitrogen +in the loop can usually not be determined from the dive log imported from the CCR equipment. Many CCR dive +computers, however, report an internally-calculated deco ceiling that is reported in the dive log, +reflecting a more accurate assessment. The display of this ceiling is activated +by clicking the appropriate button to the left of the dive profile:</p></div> +<div class="imageblock"> +<div class="content"> +<img src="images/icons/cceiling.jpg" alt="DC ceiling icon" /> +</div> +</div> +<div class="paragraph"><p>The default color of the computer-generated deco ceiling is white. This can be set to red +by checking the appropriate check box after selecting <em>File → Preferences → Graph</em>. +Below is a dive profile indicating the dive computer-generated deco ceiling:</p></div> +<div class="imageblock" style="text-align:center;"> +<div class="content"> +<img src="images/CCR_dive_ceilingF22.jpg" alt="FIGURE: CCR computer-generated deco ceiling" /> +</div> +</div> +<div class="paragraph"><p>More equipment-specific information for downloading CCR dive logs for +Poseidon MkVI and APD equipment can be found in <a href="#_appendix_b_dive_computer_specific_information_for_importing_dive_information">Appendix B</a>.</p></div> +</div> +</div> +</div> +</div> +</div> +<div class="sect1"> +<h2 id="_obtaining_more_information_about_dives_entered_into_the_logbook">6. Obtaining more information about dives entered into the logbook</h2> +<div class="sectionbody"> +<div class="sect2"> +<h3 id="_the_strong_info_strong_tab_for_individual_dives">6.1. The <strong>Info</strong> tab (for individual dives)</h3> +<div class="paragraph"><p>The 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 F</a> for more information.</td> +</tr></table> +</div> +</div> +<div class="sect2"> +<h3 id="S_ExtraDataTab">6.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">6.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 for 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">6.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 lets you control 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 +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 colors:</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>Color</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">> 30</p></td> +<td align="left" valign="top"><p class="table">> 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">< 1.5</p></td> +<td align="left" valign="top"><p class="table">< 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. +So users should see the depth of the deepest point and other peaks. Mean depth +is plotted as a grey line, indicating mean dive depth up to a particular moment during the dive.</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 +increases the size of the dive profile to fill the area of the panel.</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 O<sub>2</sub>, N<sub>2</sub>, 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, nitrogen in black, +and 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 shown 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 important 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. +Like the depth graph, the slope of the tank pressure gives you information +about the +momentary SAC rate (Surface Air Consumption) when using an air integrated dive computer. +Here the color +coding is not relative to some absolute values but relative to the average +normalized 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 easily recognizable; +something free divers won’t care about. +<span class="image"> +<img src=":images/MeasuringBar.png" alt="FIGURE: Measuring Bar" /> +</span></p></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 you wish 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 +shows 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 +occur 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 none of the Suunto dive computers make these 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’s 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’s 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 because <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 a specific deco stop. This feature lets dive computers 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 colored bar at the bottom +of the <strong>Dive Profile</strong>. In general oxygen is represented by a green bar, nitrogen a yellow bar and helium 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 doing planned decompression diving, efficient rates of offgassing 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 contrast, 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, at 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">6.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 lets you create +Bookmarks, 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, +with the time of the event set by where the mouse cursor was when the right +mouse button was first clicked to bring up the menu. Gas Change events +involve a selection of which gas is being switched TO. The list of choices is based on +the available gases defined in the <strong>Equipment</strong> Tab. Setpoint change +events open a dialog letting you choose the next setpoint value. As +in the planner, a setpoint value of zero shows the diver is +breathing from an open circuit system while any non-zero value +shows 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="S_InfoBox">6.6. The <strong>Information Box</strong></h3> +<div class="paragraph"><p>The Information box displays a large range of information about 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>When 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 shown 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). Moving the cursor horizontally lets the Information Box 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 some statistics, shown 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 if a maximum pO<sub>2</sub> of 1.4 is specified in the <strong>Preferences</strong> section +(select <em>File</em> → Preferences → Graph_ and edit the text box <em>Max pO<sub>2</sub> when showing MOD</em>. +Below the MOD there is a markedly increased +risk of exposure to the dangers of 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 either 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 a diver 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. TTS is calculated assuming an ascent surface air consumption (SAC) for +the gas currently used. Even if the profile contains several gas +switches, TTS at a specific moment during the dive is calculated using the current gas. +TTS longer than 2 hours is not accurately calculated and Subsurface only indicates <em>TTS > 2h</em>.</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-normalized 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 the respiratory rates of different dives +can be compared. The units for SAC is liters/min or cubic 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 +important to divers breathe 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">6.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 showing 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>. It is shown 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="ulist"><ul> +<li> +<p> +The light green area indicates the total gas, with the top margin of the light green + area showing 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> +</li> +<li> +<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> +</li> +<li> +<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> +</li> +<li> +<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 gradient factor shown is an + interpolation between the GFLow and GFHigh values specified in the Graph tab of the <strong>Preferences + Panel</strong> of <strong>Subsurface</strong>. +</p> +</li> +<li> +<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> +</li> +</ul></div> +<div class="paragraph"><p>These five values are shown on the left in the graph above. The way the Gas Pressure Bar Graph changes +during a dive can be seen on the right hand side of the above figure for a diver using EAN32.</p></div> +<div class="ulist"><ul> +<li> +<p> +Graph <strong>A</strong> indicates the start of a dive with the diver at the surface. The pressures in all + the tissue compartments are still at the equilibrium pressure because no diving has taken place. +</p> +</li> +<li> +<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, so their gas pressures are far below the equilibrium gas pressure. +</p> +</li> +<li> +<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> +</li> +<li> +<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 approach 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> +</li> +<li> +<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> +</li> +</ul></div> +</div> +</div> +</div> +</div> +<div class="sect1"> +<h2 id="_organizing_the_logbook_manipulating_groups_of_dives">7. Organizing the logbook (Manipulating groups of dives)</h2> +<div class="sectionbody"> +<div class="sect2"> +<h3 id="_the_dive_list_context_menu">7.1. The Dive List context menu</h3> +<div class="paragraph"><p>Several actions on either a single dive, or a group of dives, can be performed using the Dive List +Context Menu. It is found by selecting either a single 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 functions described below.</p></div> +<div class="sect3"> +<h4 id="_customizing_the_columns_showed_in_the_strong_dive_list_strong_panel">7.1.1. Customizing the columns 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 be +deleted (reflected by the check symbols) and the list is immediately updated. Preferences for information +shown in the <strong>Dive List</strong> are saved and used when <em>Subsurface</em> is re-opened.</p></div> +</div> +</div> +<div class="sect2"> +<h3 id="S_Renumber">7.2. Renumbering the dives</h3> +<div class="paragraph"><p>Dives are normally numbered incrementally from non-recent dives (low sequence +numbers) to recent dives (higher sequence numbers). Numbering +of dives is not always consistent. For instance, when non-recent dives are +added, correct 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. So you may need to renumber the dives. +Do this by selecting (from the Main Menu) <em>Log → Renumber</em>. Users are +given a choice of the lowest sequence number to be used. +This results in new sequence numbers (based on date/time) +for the dives in the <strong>Dive List</strong> panel.</p></div> +<div class="paragraph"><p>You can also renumber a few selected dives in the dive list. Select the dives that +need renumbering. Right-click on the selected list and use the Dive List Context Menu +to perform the renumbering. A popup window appears letting the user specify +the starting number for the process.</p></div> +</div> +<div class="sect2"> +<h3 id="S_Group">7.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 does this by grouping dives that have +date/times not separated in time by more than two days, so 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 of 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. To group the dives in a dive list, +(from the Main Menu) select <em>Log → 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">7.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>Notes</strong> panel. Here +you 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 used, the general weather and surface conditions during the trip, etc.). +After entering this +information, 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 the +edited information.</p></div> +</div> +<div class="sect3"> +<h4 id="_viewing_the_dives_during_a_particular_trip">7.3.2. Viewing the dives during a particular trip</h4> +<div class="paragraph"><p>Once the dives have been grouped into trips, you can expand one or more +trips by clicking the arrow-head on the left of each trip title. This expands +the selected trip, revealing individual dives done during the trip.</p></div> +</div> +<div class="sect3"> +<h4 id="_collapsing_or_expanding_dive_information_for_different_trips">7.3.3. Collapsing or expanding dive information for different trips</h4> +<div class="paragraph"><p>After selecting a particular trip in the dive list, the +context menu allows several options to expand or collapse dives +within trips. This includes expanding all trips and collapsing all trips.</p></div> +</div> +<div class="sect3"> +<h4 id="_merging_dives_from_more_than_one_trip_into_a_single_trip">7.3.4. Merging dives from more than one trip into a single trip</h4> +<div class="paragraph"><p>After selecting a trip title, the context menu allows the merging +of trips by either merging the selected trip with the trip below or with the +trip above. (Merge trip with trip below; Merge trip with trip above)</p></div> +</div> +<div class="sect3"> +<h4 id="_splitting_a_single_trip_into_more_than_one_trip">7.3.5. Splitting a single trip into more than one trip</h4> +<div class="paragraph"><p>If a trip includes ten dives, you can split this trip into two trips (trip 1: +top 4 dives; trip 2: bottom 6 dives) by selecting and right-clicking the top +four dives. The resulting context menu lets the user create a new trip by +choosing the option <strong>Create new trip above</strong>. The top four dives are then +grouped +into a separate trip. The figures below show 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">7.4. Manipulating single dives</h3> +<div class="sect3"> +<h4 id="_delete_a_dive_from_the_dive_log">7.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, 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">7.4.2. Unlink a dive from a trip</h4> +<div class="paragraph"><p>You can unlink dives from the trip to which they belong. 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 or below the trip to +which they belonged, depending on the date and time of the unlinked dive.</p></div> +</div> +<div class="sect3"> +<h4 id="_add_a_dive_to_the_trip_immediately_above">7.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 +a separate trip. To do this, select and right-click +the dive(s) to bring up the context menu, and then select <strong>Create new trip above</strong>.</p></div> +</div> +<div class="sect3"> +<h4 id="_shift_the_start_time_of_dive_s">7.4.4. Shift the start time of dive(s)</h4> +<div class="paragraph"><p>Sometimes it’s necessary to adjust the start time of a dive. This may apply to +situations where dives are done in different time zones or when the dive +computer has a wrong time. To do this, select and right-click +the dive(s) to be +adjusted. This brings up the context menu on which the <strong>Shift times</strong> +option should be selected. You must then specify the +time +(in hours and minutes) by which the dives should be adjusted and click on the +option of whether the time adjustment should be earlier or later.</p></div> +</div> +<div class="sect3"> +<h4 id="_merge_dives_into_a_single_dive">7.4.5. Merge dives into a single dive</h4> +<div class="paragraph"><p>Sometimes a dive is briefly interrupted, for example, if a diver returns to the surface +for a few minutes. That results in two or more dives being recorded by the dive +computer and appearing as different dives in the <strong>Dive List</strong> panel. You 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>Notes</strong> +panel to reflect events or conditions that apply to the merged dive. The figure +below shows the depth profile of two 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 class="sect3"> +<h4 id="_undo_dive_manipulations">7.4.6. Undo dive manipulations</h4> +<div class="paragraph"><p>Important actions on dives or trips, described above, can be undone or redone. +This includes: <em>delete dives</em>, <em>merge dives</em>, <em>renumber dives</em> and <em>shift dive times</em>. +To do this after performing any of these actions, from the <strong>Main Menu</strong> select +<em>Edit</em>. This brings up the possibility to <em>Undo</em> or <em>Redo</em> an action.</p></div> +</div> +</div> +<div class="sect2"> +<h3 id="S_Filter">7.5. Filtering the dive list</h3> +<div class="paragraph"><p>The dives in the <strong>Dive List</strong> panel can be filtered, so you 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 lets you 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 → 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 (see image below). The <em>Filter Panel</em> can be reset +(i.e. all current filters cleared) by selecting the <strong>yellow angled arrow</strong>. The <em>Filter Panel</em> may also be +minimized by selecting the <strong>green up-arrow". When minimized, only these three icons are shown. +The panel can be maximized by clicking the same icon that minimized it. The filter may also be +reset and closed by selecting the *red button</strong> with the white cross.</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 / divemaster), dive site +and dive suit. Each of these 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 +attributes within that check list. For instance, typing "<em>ca</em>" in the filter +text box above the tags check list, results in the list being reduced +to "<em>cave</em>" and "<em>cavern</em>". Filtering the check list helps to rapidly find +search terms for filtering the dive list.</p></div> +<div class="paragraph"><p>To activate filtering of the dive list, check at least one check box in one of +the four check lists. The dive list is then shortened to include +only the dives that pertain to the 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">8. Exporting the dive log or parts of the dive log</h2> +<div class="sectionbody"> +<div class="paragraph"><p>There are two ways to export dive information from Subsurface:</p></div> +<div class="ulist"><ul> +<li> +<p> +Export dive information to <em>Facebook</em> +</p> +</li> +<li> +<p> +<a href="#S_Export_other">Export dive information to other destinations or formats</a> +</p> +</li> +</ul></div> +<div class="sect2"> +<h3 id="S_facebook">8.1. Exporting dive information to <em>Facebook</em></h3> +<div class="paragraph"><p>Export of dives to <em>Facebook</em> is handled differently from other types of export because +a connection to <em>Facebook</em> is required, needing a <em>Facebook</em> userID and password. +If, from the <strong>Main Menu</strong>, you select <em>File → Preferences → Facebook</em>, a login screen comes up. +(image <strong>A</strong> to the left, below). Provide a <em>Facebook</em> userID and password. +Once logged into to <em>Facebook</em> , the panel +in image <strong>B</strong>, below is shown, including a <em>Disconnect from Facebook</em> button to close the +<em>Facebook</em> connection.</p></div> +<div class="imageblock" style="text-align:center;"> +<div class="content"> +<img src="images/facebook1_f20.jpg" alt="Figure: Facebook login" /> +</div> +</div> +<div class="paragraph"><p>From the <em>Subsurface</em> window it’s easy to determine whether <em>Subsurface</em> has a valid connection to <em>Facebook</em> +From the <strong>Main Menu</strong>, select <em>Share on → Facebook</em> (image <strong>A</strong>, below). Normally, the <em>Facebook</em> option is greyed out. But +if there is a connection to <em>Facebook</em>, this option is active (i.e. in black color and can be selected).</p></div> +<div class="paragraph"><p>Having established a login to <em>Facebook</em>, transferring a dive profileto a <em>Facebook</em> timeline is easy. +Be sure the dive to be transferred to the timeline is shown in the <em>Subsurface</em> <strong>Dive Profile</strong> panel. If, from the <strong>Main Menu</strong>, you +select <em>Share on → Facebook</em> (see image <strong>A</strong> below), a dialogue box is shown, determining the amount of additional information transferred along +with the dive profile (image <strong>B</strong>, below). To transfer a dive profile to <em>Facebook</em>, the name of a +<em>Facebook</em> album is needed. The checkboxes on the left hand side let you decide how much +additional information should be transferred with the dive profile. This information is shown in the text box +on the right hand side of the panel (image <strong>B</strong>, below). You can easily edit the message that will be posted +with the dive profile. After specifying the additional information and verifying the text, select +the <em>OK</em> button that triggers the transfer to <em>Facebook</em>. After the transfer +is done, an acknowledgement dialogue appears, indicating it was successful.</p></div> +<div class="paragraph"><p>Both the album created and the post to your timeline will be marked as +private. In order for friends to be able to see it, +change its permissions from a regular Facebook login either in a +browser or a Facebook app.</p></div> +<div class="imageblock" style="text-align:center;"> +<div class="content"> +<img src="images/facebook2_f20.jpg" alt="Figure: Facebook login" /> +</div> +</div> +<div class="paragraph"><p>If required, then close the <em>Facebook</em> connection by either closing <em>Subsurface</em> or by selecting <em>File → Preferences → Facebook</em> from +the Main Menu, and clicking the appropriate button on the Facebook Preferences panel.</p></div> +</div> +<div class="sect2"> +<h3 id="S_Export_other">8.2. Export dive information to other destinations or formats</h3> +<div class="paragraph"><p>For non-<em>Facebook exports</em>, the export function can be found by selecting <em>File → 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_f20.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> +<li> +<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> +</li> +<li> +<p> +<em>Divelogs.de</em>, an Internet-based dive log repository. In order to upload to <em>Divelogs.de</em>, + you need 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 to upload dive log data from <em>Subsurface</em>. +</p> +</li> +<li> +<p> +<em>DiveShare</em> is also a dive log repository on the Internet focusing on recreational + dives. To upload dives, you need a user ID, so registration with + <em>http://scubadiveshare.com</em> is required. +</p> +</li> +<li> +<p> +<em>CSV dive details</em>, that includes the most critical information of the dive + profile. Included information of a dive is: dive number, date, time, buddy, + duration, depth, temperature and pressure: in short, most of the information + that recreational divers enter into handwritten log books. +</p> +</li> +<li> +<p> +<em>CSV dive profile</em>, that includes a large amount of detail for each dive, including + the depth profile, temperature and pressure information of each dive. +</p> +</li> +<li> +<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. The HTML export cannot be changed or edited. + It contains most of the information recorded in the dive log. However, it does not show the + calculated values in the <strong>Dive Profile</strong> panel, e.g. calculated cylinder pressure, gas + pressures and MOD. The HTML export 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). A typical use of this option is to export all one’s + dives to a smartphone or a tablet where it would serve as a portable record + of dives. That is useful for dive companies that wish to verify the dive history of a diver, + often doing away with the need to carry an original logbook + when doing dives with dive companies. +</p> +</li> +<li> +<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. If you select any + of the dive sites on the map, a summary of the dive is available in text, as shown + in the image below. +</p> +</li> +</ul></div> +<div class="imageblock" style="text-align:center;"> +<div class="content"> +<img src="images/mapview_f20.jpg" alt="Figure: HTML Map export view" /> +</div> +</div> +<div class="ulist"><ul> +<li> +<p> +<em>Image depths</em>, which creates a text file that contains the file names of all + photos or images attached + to any of the selected dives in the <em>Dive List</em>, together with the depth underwater where + of each of those photos was taken. +</p> +</li> +<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 to the HTML exports. +</p> +</li> +<li> +<p> +Export List only: a list of dives only (date, time, depth, duration) will be exported + and the detailed dive information, e.g. dive profile, will not be available. +</p> +</li> +</ul></div> +</li> +<li> +<p> +Under <em>Style Options</em> some style-related options are available like font + size and theme. +</p> +</li> +</ul></div> +<div class="paragraph"><p>Export to other formats can be done through third party facilities, for +instance <em>www.divelogs.de</em>.</p></div> +</div> +</div> +</div> +<div class="sect1"> +<h2 id="S_Cloud_access">9. 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’s own pleasure, but it’s important information required +for admission to training courses or sometimes even diving sites. The +security of the dive log is critical. 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 you can access your dive +log from anywhere in the world. For this reason, facilities such as <em>divelogs.de</em> and <em>Diving Log</em> offer to store +dive log information on the Internet.</p></div> +<div class="paragraph"><p><em>Subsurface</em> includes access to a transparently integrated cloud storage +back end that is available to all Subsurface users. Storing and retrieving a dive log +from the cloud is no more difficult than accessing the dives on the local hard disk. +The only requirement is that you should first register as a user on the cloud. +To use <em>Subsurface cloud storage</em> , follow these steps:</p></div> +<div class="sect2"> +<h3 id="_create_a_cloud_storage_account">9.1. Create a cloud storage account</h3> +<div class="ulist"><ul> +<li> +<p> +Open the <strong>Network Preferences</strong> by selecting <em>File</em> → <em>Preferences</em> → <em>Network</em>. +</p> +</li> +<li> +<p> +In the section headed <em>Subsurface cloud storage</em>, enter an email address that + <em>Subsurface</em> can use for user registration. +</p> +</li> +<li> +<p> +Enter a novel password that <em>Subsurface</em> will use to store the + dive log in the cloud. +</p> +</li> +<li> +<p> +Click <em>Apply</em> to send the above email address and password to the + (remote) cloud server. The server responds by sending a verification PIN to + the above email address (This is the <strong>only</strong> occasion that <em>Subsurface</em> uses the + email address provided above). The <strong>Network Preferences</strong> dialog now has a new PIN text + box, not visible previously. +</p> +</li> +<li> +<p> +Enter the PIN in the corresponding text box in the <strong>Network Preferences</strong> dialog +(this field is only visible while the server is waiting for email +address confirmation) +</p> +</li> +<li> +<p> +Click <em>Apply</em> again. The <em>Subsurface cloud storage</em> account +will be marked as verified and the <em>Subsurface cloud storage</em> service is initialised for use. +</p> +</li> +</ul></div> +</div> +<div class="sect2"> +<h3 id="_using_em_subsurface_cloud_storage_em">9.2. Using <em>Subsurface cloud storage</em></h3> +<div class="ulist"><ul> +<li> +<p> +Once the cloud storage has been initialized, two new items appear in the + <em>File</em> menu of the main menu system: <em>Open cloud storage</em> and <em>Save to cloud storage</em>. +These options let you load and save data to the <em>Subsurface +cloud storage</em> server. +</p> +</li> +<li> +<p> +In the <em>Defaults Preferences</em> tab, you can select to use the <em>Subsurface cloud +storage</em> data as the default data file by checking the box marked <em>Cloud storage default file</em>. + This means the data from +the <em>Subsurface cloud storage</em> is loaded when <em>Subsurface</em> starts and saved there when <em>Subsurface</em> closes. +</p> +</li> +<li> +<p> +<em>Subsurface</em> keeps a local copy of the data and the cloud facility remains fully +functional even if used while disconnected to the Internet. <em>Subsurface</em> simply synchronizes the +data with the cloud server the next time the program is used while the computer is +connected to the Internet. +</p> +</li> +</ul></div> +</div> +<div class="sect2"> +<h3 id="S_Cloud_storage">9.3. Web access to <em>Subsurface cloud storage</em></h3> +<div class="paragraph"><p>One of the nice side benefits of using <em>Subsurface cloud storage</em> is that +you can also access your dive data from any web browser. Simply open +<a href="https://cloud.subsurface-divelog.org"><em>https://cloud.subsurface-divelog.org</em></a>, +log in with the same email and password, and you can see an HTML export of +the last dive data that was synced to <em>Subsurface cloud storage</em>. The dive information +shown is only the contents of the recorded dive logs, NOT the calculated values +shown in the <strong>Profile</strong> panel, +including some cylinder pressures, deco ceilings and O<sub>2</sub>/He/N<sub>2</sub> partial pressures.</p></div> +</div> +<div class="sect2"> +<h3 id="_other_cloud_services">9.4. Other cloud services</h3> +<div class="paragraph"><p>If you prefers not to use the integrated cloud storage of dive logs (and +don’t need the web access), it’s simple to store +dive logs in the cloud using several of the existing facilities on the +Internet. +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 a 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 your +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’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 +your <em>Dropbox</em> folder can be accessed seamlessly from the Internet and can +be accessed anywhere 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 you can use <em>Dropbox</em> as a way back up your dive log. To +Store a dive log on <em>Dropbox</em>, select <em>File → 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 <em>Dropbox</em>, select <em>File → 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> +<div class="sect1"> +<h2 id="S_PrintDivelog">10. Printing a dive log</h2> +<div class="sectionbody"> +<div class="paragraph"><p><em>Subsurface</em> provides a simple and flexible way to print a whole dive log or only a few selected dives. + Pre-installed templates or a custom written template can be used to choose where the data are fitted into the page.</p></div> +<div class="paragraph"><p>Some decisions need to be made before printing:</p></div> +<div class="ulist"><ul> +<li> +<p> +Should the whole dive log be printed or only part of it? If only part + is required, select the required dives from the <strong>Dive List</strong> panel. +</p> +</li> +<li> +<p> +If the dive profiles are printed, what gas partial pressure information should be shown? Select + the appropriate toggle-buttons on the button bar to the left of the <strong>Dive Profile</strong> panel. +</p> +</li> +</ul></div> +<div class="paragraph"><p>If <em>File → Print</em> is selected from the Main menu, the dialogue below (image <strong>A</strong>) appears. Three +specifications are needed to get the desired information and page layout:</p></div> +<div class="imageblock" style="text-align:center;"> +<div class="content"> +<img src="images/Print1_f22.jpg" alt="FIGURE: Print dialogue" /> +</div> +</div> +<div class="olist arabic"><ol class="arabic"> +<li> +<p> +Under <em>Print type</em> select one of two options: +</p> +<div class="ulist"><ul> +<li> +<p> +<em>Dive list print</em>: Print dives from the <strong>Dive List</strong> panel with profiles and other information. +</p> +</li> +<li> +<p> +<em>Statistics print</em>: Print yearly statistics of the dives. +</p> +</li> +</ul></div> +</li> +<li> +<p> +Under <em>Print options</em> select: +</p> +<div class="ulist"><ul> +<li> +<p> +Printing only the dives selected from the dive list before + activating the print dialogue by checking the box <em>Print only + selected dives</em>. If this check box is <strong>not</strong> checked ALL dives in + the <strong>Dive List</strong> panel are printed. +</p> +</li> +<li> +<p> +Printing in color, done by checking the box with _Print in color. If this check box + is not checked, printing is in black and white. +</p> +</li> +</ul></div> +</li> +<li> +<p> +Under <em>Template</em> select a template to be used as the page layout. There are several choices. +(see image <strong>B</strong>, above). +</p> +<div class="ulist"><ul> +<li> +<p> +<em>Table</em>: This prints a summary table of all dives selected (see below). +</p> +</li> +</ul></div> +</li> +</ol></div> +<div class="imageblock" style="text-align:center;"> +<div class="content"> +<img src="images/Print_summarylist_f22.jpg" alt="FIGURE: Print summary table" /> +</div> +</div> +<div class="ulist"><ul> +<li> +<p> +<em>Flow layout</em>: Print the text associated with each dive without printing the dive profiles + of each dive (see below): +</p> +</li> +</ul></div> +<div class="imageblock" style="text-align:center;"> +<div class="content"> +<img src="images/Print_flow_layout_f22.jpg" alt="FIGURE: Print flow layout" /> +</div> +</div> +<div class="ulist"><ul> +<li> +<p> +<em>One Dive</em>: Print one dive per page, also showing the dive profile (see below) +</p> +</li> +</ul></div> +<div class="imageblock" style="text-align:center;"> +<div class="content"> +<img src="images/print2_f22.jpg" alt="FIGURE: Print one dive / page" /> +</div> +</div> +<div class="ulist"><ul> +<li> +<p> +<em>Two Dives</em>: Print two dives per page, also showing the dive profiles. +</p> +</li> +<li> +<p> +<em>Six Dives</em>: Print six dives per page, also showing the dive profiles. +</p> +</li> +</ul></div> +<div class="paragraph"><p>You can <em>Preview</em> the printed page by selecting the <em>Preview</em> button on the +dialogue (see image <strong>A</strong> at the start of this section). After preview, you can change +the options in the print dialogue, so the layout fits personal taste.</p></div> +<div class="paragraph"><p>Next, select the <em>Print</em> button (see image <strong>A</strong> at the start of this section). This activates the regular print +dialogue used by the operating system, +letting you choose a printer and set its properties (see image below):</p></div> +<div class="imageblock" style="text-align:center;"> +<div class="content"> +<img src="images/Print_print_f22.jpg" alt="FIGURE: Print dialog" /> +</div> +</div> +<div class="paragraph"><p>Set the print resolution of the printer to an appropriate value by changing +the printer <em>Properties</em>. Finally, select the <em>Print</em> button to 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 class="sect2"> +<h3 id="_writing_a_custom_print_template_advanced">10.1. Writing a custom print template (advanced)</h3> +<div class="paragraph"><p>Writing a custom template is an effective way to produce highly customized printouts. Subsurface uses HTML templates +to render printing. You can create a template, export a new template, import an existing template and delete an existing template by using +the appropriate buttons under the <em>Template</em> dropdown list in the print dialogue. See <a href="#S_APPENDIX_E">APPENDIX E</a> for information on how +to write or modify a template.</p></div> +</div> +</div> +</div> +<div class="sect1"> +<h2 id="S_Configure">11. Configuring a dive computer</h2> +<div class="sectionbody"> +<div class="paragraph"><p><em>Subsurface</em> lets you 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. To begin, be sure the appropriate hardware driver +is installed for the dive computer (also required for downloading dives) and 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 → 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 and select the appropriate dive +computer model from the panel on the left-hand (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 done:</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 it 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="S_Preferences">12. Setting user <em>Preferences</em> for <em>Subsurface</em></h2> +<div class="sectionbody"> +<div class="paragraph"><p>There are several user-definable settings within <em>Subsurface</em>, found by selecting +<em>File → Preferences</em>. The settings are in +seven groups: <strong>Defaults</strong>, <strong>Units</strong>, <strong>Graph</strong>, <strong>Language</strong> and <strong>Network</strong>, <strong>Facebook</strong> and <strong>Georeference</strong>. +All operate on the same principles: the user must specify settings that are to be changed, then +save them using the <strong>Apply</strong> button. After applying all the new settings users can then +leave the settings panel by selecting <strong>OK</strong>. If <strong>Discard</strong> is selected, changes to the preferences +are not saved.</p></div> +<div class="sect2"> +<h3 id="_defaults">12.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_f20.jpg" alt="FIGURE: Preferences defaults page" /> +</div> +</div> +<div class="ulist"><ul> +<li> +<p> +<strong>Lists and tables</strong>: Here you 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>, you can see more dives on a screen. +</p> +</li> +<li> +<p> +<strong>Dives</strong>: For the <em>Default Dive File</em> you need to specify the directory and + file name of your + electronic dive log book. This is a file with filename extension of either <em>.xml</em> or <em>.ssrf</em>. When + launched, <em>Subsurface</em> will automatically load the specified dive log book. There are three options: +</p> +<div class="ulist"><ul> +<li> +<p> +<em>No default file</em>: When checked, <em>Subsurface</em> does not automatically load a dive log at startup. +</p> +</li> +<li> +<p> +<em>Local default file</em>: When checked, <em>Subsurface</em> automatically loads a dive log from the local hard disk + as described above. +</p> +</li> +<li> +<p> +<em>Cloud storage default file</em>: When checked, <em>Subsurface automatically loads the dive log from the cloud + device that was initialized using the <strong>Preferences</strong> _Network</em> tab (see below). +</p> +</li> +</ul></div> +</li> +<li> +<p> +<strong>Display invalid</strong>: Dives can be marked as invalid (when a user wishes to hide + dives that he/she doesn’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>: Specify the default cylinder listed in + the <strong>Equipment</strong> tab of the <strong>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, and a 0 value representing no animation + at all. +</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">12.2. Units</h3> +<div class="imageblock" style="text-align:center;"> +<div class="content"> +<img src="images/Pref2_f20.jpg" alt="FIGURE: Preferences Units page" /> +</div> +</div> +<div class="paragraph"><p>Here you 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, you can specify that all units are in the chosen measurement system. +Alternatively, if you select the <strong>Personalize</strong> radio button, units can be selected +independently, with some in the metric system and others in imperial.</p></div> +<div class="paragraph"><p>Regardless +of the above settings, dive time measurements can be either in seconds or minutes. +Choose the appropriate option. GPS coordinates can be represented either as +traditional coordinates (degrees, minutes, seconds) or as decimal degrees +Choose the appropriate option.</p></div> +</div> +<div class="sect2"> +<h3 id="_graph">12.3. Graph</h3> +<div class="imageblock" id="S_CCR_options" style="text-align:center;"> +<div class="content"> +<img src="images/Pref3_f20.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="ulist"><ul> +<li> +<p> +<strong>Show</strong>: Here you can specify the amount of information shown as part of + the dive profile: +</p> +<div class="ulist"><ul> +<li> +<p> +Thresholds: <em>Subsurface</em> can display the nitrogen, oxygen and the helium partial pressures during + the dive, done by using the toolbar on the left hand side of the <strong>Dive Profile</strong> + panel. For each of these graphs you can specify a threshold value on the right-hand side of the + Preferences panel. If any of the graphs go above the specified threshold level, the graph is + highlighted in red, indicating the particular partial pressure threshold has been exceeded. +</p> +</li> +<li> +<p> +_Max pO<sub>2</sub> is used for calculating the MOD when displaying the maximum operative depth (MOD) + for a dive. Specify an appropriate partial pressure. A value of 1.4 is commonly used. +</p> +</li> +<li> +<p> +<em>Draw dive computer reported ceiling red</em>: This checkbox does exactly what it says. By default + the computer reported ceiling is shown in white. + 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> because of the different algorithms and + gradient factors, as well as the dynamic way a + dive computer calculates 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>. If this box is not checked, and if 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>: If this box is checked, the <strong>Dive Profile</strong> panel contains a grey line that shows + the mean depth of the dive, up to any time instant during the dive. Normally this is a u-shaped line indicating the deepest mean depth just before + ascent. +</p> +</li> +</ul></div> +</li> +<li> +<p> +<strong>Misc</strong>: +</p> +<div class="ulist" id="GradientFactors_Ref"><ul> +<li> +<p> +Gradient Factors (GFLow and GFHigh):* 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 nitrogen exposure during a dive, in a + similar way that many dive computers have a conservative 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 70/90 are considered + harsh. Checking the <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> +<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> +</li> +<li> +<p> +<em>CCR: Show setpoints when viewing pO2:</em> With this checkbox activated, the pO<sub>2</sub> + graph on the dive profile has an overlay in red which indicates the CCR setpoint + values. See the section on <a href="#S_CCR_dives">Closed Circuit Rebreather dives</a>. +</p> +</li> +<li> +<p> +<em>CCR: Show individual O<sub>2</sub> sensor values when viewing pO<sub>2</sub>:</em> Show the pO<sub>2</sub> + values associated with each of the individual oxygen sensors of a CCR system. + See the section on <a href="#S_CCR_dives">Closed Circuit Rebreather dives</a>. +</p> +</li> +</ul></div> +</li> +<li> +<p> +<strong>Configuring dive planning using rebreather equipment:</strong> +</p> +<div class="ulist"><ul> +<li> +<p> +<em>Default CCR setpoint for dive planning:</em> Specify the O<sub>2</sub> setpoint for a + CCR dive plan. This determines the pO<sub>2</sub> maintained + during a particular dive. Setpoint changes during the dive can be added via the + profile context menu. +</p> +</li> +<li> +<p> +<em>pSCR O<sub>2</sub> metabolism rate:</em> For a semi-closed rebreather (pSCR) system, this is the + volume of oxygen used by a diver during a minute. Set this value for pSCR dive planning + and decompression calculations. +</p> +</li> +<li> +<p> +<em>pSCR ratio:</em> For pSCR equipment the dump ratio is the ratio of gas released to the + environment to that of the gas recirculated to the diver. Set this value for a + pSCR dive plan. A 1:10 ratio is commonly used. +</p> +</li> +</ul></div> +</li> +</ul></div> +</div> +<div class="sect2"> +<h3 id="_language">12.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_f20.jpg" alt="FIGURE: Preferences Language page" /> +</div> +</div> +<div class="paragraph"><p>A checkbox lets you 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 operating system. +To change it, uncheck this checkbox and pick a language / country +combination from the list of locations. The <em>Filter</em> text box +lists similar languages. For instance there are several system variants of English +or French. <strong>This particular preference requires a restart of <em>Subsurface</em> to take +effect</strong>.</p></div> +</div> +<div class="sect2"> +<h3 id="_network">12.5. Network</h3> +<div class="paragraph"><p>This panel facilitates communication between <em>Subsurface</em> and data sources on the Internet. +This is important, for instance, when <em>Subsurface</em> needs to communicate with web +services such as Cloud storage or the <a href="#S_Companion"><em>Subsurface Companion app</em></a>. These Internet requirements are determined by your type of +connection to the Internet and by the Internet Service Provider (ISP) used. +Your ISP should provide the appropriate information.</p></div> +<div class="imageblock" style="text-align:center;"> +<div class="content"> +<img src="images/Pref5_f20.jpg" alt="FIGURE: Preferences Network page" /> +</div> +</div> +<div class="paragraph"><p>This dialogue has three sections:</p></div> +<div class="ulist"><ul> +<li> +<p> +<em>Proxy type</em>: +If a proxy server is used for Internet access, 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 are required so that <em>Subsurface</em> can automatically pass +through the proxy server to access the Internet. This information is usually obtained +from one’s ISP. +</p> +</li> +<li> +<p> +<em>Subsurface cloud storage</em>: To store your dive log in the cloud, a valid email address + and password are required. This lets <em>Subsurface</em> email security information + regarding cloud storage to you, and to set up cloud storage appropriately. + Two additional options are given: +</p> +<div class="ulist"><ul> +<li> +<p> +<em>Sync to cloud in the background</em>: This option allows saving of dive information to the cloud storage + while you do other things within <em>Subsurface</em>. +</p> +</li> +<li> +<p> +<em>Save password locally</em>: This allows local storage of the cloud storage password. Note that this + information is saved in raw text form, not encoded in any way. +</p> +</li> +</ul></div> +</li> +<li> +<p> +<em>Subsurface web service</em>: When you subscribe 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>, you ensure a local copy of that userID is saved. +</p> +</li> +</ul></div> +</div> +<div class="sect2"> +<h3 id="S_Facebook">12.6. Facebook Access</h3> +<div class="paragraph"><p>This panel lets you log into a Facebook account in order to transfer information +from Subsurface to Facebook.</p></div> +<div class="imageblock" style="text-align:center;"> +<div class="content"> +<img src="images/Pref6_f20.jpg" alt="FIGURE: Facebook login panel" /> +</div> +</div> +<div class="paragraph"><p>If you provide a valid Facebook userID and password, a +connection to Facebook is created. That connection is closed when one +closing down Subsurface. Currently the checkbox labelled "Keep me logged in to Subsurface", +on the login screen has no effect. +See the section <a href="#S_facebook">Exporting dive profiles to Facebook</a> +for more information.</p></div> +</div> +<div class="sect2"> +<h3 id="_georeference">12.7. Georeference</h3> +<div class="paragraph"><p><em>Subsurface</em> provides a geo-lookup service (that is, given the coordinates of a dive site) derived from +a click on the <strong>Dive Map panel</strong> at the bottom right of the <em>Subsurface</em> window, or from a GPS instrument or +from the <em>Subsurface</em> Companion app). A search on the Internet is done to find +the name of the closest known location. This function only works if <em>Subsurface</em> has an +Internet connection. The preference of the dive site name can be configured, e.g. <em>Country/State/City</em> +or <em>City/State/Country</em> (see image below).</p></div> +<div class="imageblock" style="text-align:center;"> +<div class="content"> +<img src="images/Pref7_f20.jpg" alt="FIGURE: Facebook login panel" /> +</div> +</div> +</div> +</div> +</div> +<div class="sect1"> +<h2 id="S_DivePlanner">13. The <em>Subsurface</em> dive planner</h2> +<div class="sectionbody"> +<div class="paragraph"><p>Dive planning is an advanced feature of <em>Subsurface</em>, accessed by selecting +<em>Log → 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="ulist"><ul> +<li> +<p> +The user is conversant with dive planning and has the necessary training to perform + dive planning. +</p> +</li> +<li> +<p> +The user plans dives within his/her certification limits. +</p> +</li> +<li> +<p> +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. +</p> +</li> +<li> +<p> +The safety of a dive plan depends heavily on the way in which the planner is used. +</p> +</li> +<li> +<p> +The user is familiar with the user interface of <em>Subsurface</em>. +</p> +</li> +<li> +<p> +A user who is not absolutely sure about any of the above requirements should not use + this feature. +</p> +</li> +</ul></div> +</div></div> +<div class="sect2"> +<h3 id="_the_em_subsurface_em_dive_planner_screen">13.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 sections on the left hand side of the screen. +They are: Available Gases, Rates, Planning, Gas Options and Notes.</p></div> +<div class="paragraph"><p>At the top right hand is a green <strong>design panel</strong> on 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_f20.jpg" alt="FIGURE: Dive planner startup window" /> +</div> +</div> +</div> +<div class="sect2"> +<h3 id="_open_circuit_dives">13.2. Open circuit dives</h3> +<div class="ulist"><ul> +<li> +<p> +Towards the center bottom of the planner (circled in blue in the image above) is a dropbox with three options. Select the appropriate one of these: +</p> +<div class="ulist"><ul> +<li> +<p> +Open Circuit (the default) +</p> +</li> +<li> +<p> +CCR +</p> +</li> +<li> +<p> +pSCR +</p> +</li> +</ul></div> +</li> +<li> +<p> +Choose the Open Circuit option. +</p> +</li> +<li> +<p> +In the top left-hand area of the planning screen, be sure the constant dive parameters are + appropriate. These are: Start date and time of the intended dive, Atmospheric Pressure and Altitude + above sea level of the dive site. The atmospheric pressure can also be entered as an altitude + in meters, assuming a sea-level atmospheric pressure of 1.013 bar. +</p> +</li> +<li> +<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="#cylinder_definitions">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 cylinder is assumed to contain 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 right-hand of the dialogue. +</p> +</li> +<li> +<p> +The profile of the planned dive can be created in two ways: +</p> +<div class="ulist"><ul> +<li> +<p> +Drag the waypoints + (the small white circles) on the existing dive profile to represent the dive. Additional + waypoints can be created by double-clicking the existing dive profile. Waypoints can be deleted + by right-clicking a particular waypoint and selecting the <em>delete</em> item from the resulting + context menu. +</p> +</li> +<li> +<p> +The most efficient way to create a dive profile is to enter the appropriate values into the table + marked <em>Dive planner points</em>. The first line of the table represents the duration and the final + depth of the descent from the surface. Subsequent segments describe the bottom phase of the dive. + The <em>CC set point</em> column is only relevant for closed circuit divers. + The ascent is usually not specified because this is what the planner is supposed to calculate. + Add additional segments to the profile by selecting the "+" icon at the top right hand of the + table. Segments entered into the <em>Dive planner points</em> table automatically appear in the <strong>Dive + Profile</strong> diagram. +</p> +</li> +</ul></div> +</li> +</ul></div> +<div class="sect3"> +<h4 id="_recreational_dives">13.2.1. Recreational dives</h4> +<div class="paragraph"><p>Recreational mode is what comes closest to planning a dive based on the non-decompression limit (NDL). +It computes the maximum time a diver can stay at the current depth without needing mandatory decompression +stops and without using more than the existing gas (minus a reserve). The planner automatically takes +into account the nitrogen load incurred in previous dives. But conventional dive tables are also used in a +way that can take into account previous dives. Why use a dive planner for recreational dives? Using +recreational dive tables, the maximum depth of a dive is taken into account. But few dives are +done at a constant depth corresponding to the maximum depth (i.e. a "square" dive profile). This means +dive tables overestimate the nitrogen load incurred during previous dives. The <em>Subsurface</em> +dive planner calculates nitrogen load according to the real dive profiles of all uploaded previous dives, +in a similar way as dive computers calculate nitrogen load during a dive. This means that the diver gets <em>credit,</em> +in terms of nitrogen load, for not remaining at maximum depth during +previous dives, so a longer subsequent dive can be planned. + For the planner to work it’s crucial to upload all previous dives +onto <em>Subsurface</em> before doing dive planning. +To plan a dive, the appropriate settings need to be defined.</p></div> +<div class="ulist"><ul> +<li> +<p> +Ensure the date and time is set to that of the intended dive. This allows calculation of +the nitrogen load incurred during previous dives. +</p> +</li> +<li> +<p> +Immediately under the heading <em>Planning</em> are two checkboxes <em>Recreational</em> and <em>Safety Stop</em>. + Check these two boxes. +</p> +</li> +<li> +<p> +Then define the cylinder size, + the gas mixture (air or % oxygen) and the starting cylinder pressure in the top left-hand + section of the planner under <em>Available gases</em>. +</p> +</li> +<li> +<p> +The planner calculates whether the specified cylinder contains enough air/gas to complete + the planned dive. In order for this to be accurate, under <em>Gas options</em>, specify an appropriate + surface air consumption (SAC) rate for <em>Bottom SAC</em>. Suitable values are between 15 l/min and 30 l/min, + with novice divers or difficult dives requiring SAC rates closer to 30l/min. +</p> +</li> +<li> +<p> +Define the amount of gas the cylinder must have at the end of the bottom section of the + dive just before ascent. A value of 50 bar is often used. The reason for this reserve gas is to provide for the possible + need to bring a buddy to the surface using gas sharing. How much gas is used in + sharing depends on the depth of the ascent. This can be difficult to estimate, so most agencies assume a + fixed amount of gas, or actually of pressure e.g. 40 or 50 bar or 25% or 33% (rule of thirds). But <em>Subsurface</em> can do better + because it knows about the ascent and that is why we add the amount of gas during the ascent (i.e. the "deco gas“). + Subsurface still uses a fixed pressure "reserve" but that’s supposed to be for the additional gas used when + there’s a problem and your pulse rate goes up when you start to buddy breathe. This reserve amount is user configurable. +</p> +</li> +<li> +<p> +Define the depth of the dive by dragging the waypoints (white dots) on the dive profile or + (even better) defining the appropriate depths using the table under <em>Dive planner points</em> as + desribed under the previous heading. If + this is a multilevel dive, set the appropriate dive depths to represent the dive plan by adding + waypoints to the dive profile or by adding appropriate dive planner points to the <em>Dive Planner Points</em> + table. <em>Subsurface</em> will automatically extend the bottom section of the dive to the maximum + duration within the no-decompression limits (NDL). +</p> +</li> +<li> +<p> +The ascent speed can be changed. The default ascent speeds are those considered safe for recreational + divers. +</p> +</li> +</ul></div> +<div class="paragraph"><p>The dive profile in the planner shows the maximum dive time within no-deco limits using the +Bühlmann ZH-L16 algorithm and the gas and depth settings specified as described above. The <em>Subsurface</em> planner +allows rapid assessment of dive duration as a function of dive depth, given the nitrogen load incurred during previous dives. The +dive plan includes estimates of the amount of air/gas used, depending on the cylinder settings specified +under <em>Available gases</em>. If the initial cylinder pressure is set to 0, the dive duration shown is the +true no-deco limit (NDL) without taking into account gas used during the dive. If the surface above the dive profile is RED +it means that recreational dive limits are exceeded and either the dive duration or the dive depth needs to be reduced.</p></div> +<div class="paragraph"><p>Below is an image of a dive plan for a recreational dive at 30 meters. Although the no-deco limit (NDL) is 23 +minutes, the duration of the dive is limited by the amount of air in the cylinder. That is shown in the +text box at the bottom right of the panel, requiring sufficient air for buddy-sharing during ascent.</p></div> +<div class="imageblock" style="text-align:center;"> +<div class="content"> +<img src="images/rec_diveplan.jpg" alt="FIGURE: A recreational dive plan: setup" /> +</div> +</div> +</div> +<div class="sect3"> +<h4 id="_non_recreational_open_circuit_dives_including_decompression">13.2.2. Non-recreational open circuit dives, including decompression</h4> +<div class="paragraph"><p>Non-recreational dive planning involves exceeding the no-deco limits and/or using multiple breathing gases. +These dives are planned in three stages:</p></div> +<div class="paragraph"><p><strong>a) Nitrogen management</strong>: This is done by specifying the rates for descent and ascent, +as well as the deco model (GFLow, GFHigh or Conservatism level) under the headings <em>Rates</em> and <em>Planning</em> +to the bottom left of the planning screen. Two deco models are supported the Bühlmann model and the VPM-B +model. Select one of the two models. When selecting the Bühlmann model, the gradient factors (GF_high and GF_low +need to be specified. 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 values in the <em>Preferences</em>. +Gradient Factor settings strongly affect the calculated ceilings and their depths. +A very low GFLow value brings on decompression stops early during the dive. + ** For more information about Gradient factors, see the section on <a href="#S_GradientFactors">Gradient Factor Preference settings</a>.</p></div> +<div class="paragraph"><p>If the VPM-B model is selected, the Conservatism_level needs to be specified on a scale of 0 (least conservative) to 4 (most conservative). +This model tends to give deco stops at deeper levels than the Bühlmann model and often results in slightly shorter +dive durations than the Bühlmann model. When selecting one of these models, keep in mind they are NOT exact physiological models but +only mathematical models that appear to work in practice.</p></div> +<div class="paragraph"><p>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&ie=UTF8&qid=1403932320&sr=1-1&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 that discusses both the Bühlmann deco model and the VPM-B model. +</p> +</li> +</ul></div> +<div class="paragraph"><p>The ascent rate is critical for nitrogen off-gassing at the end of the dive and is specified +for several depth ranges, using the average (or mean) depth as a yardstick. The mean depth +of the dive plan is shown by a light grey line on the dive profile. 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, 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></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 increased to 1.6 bar.</p></div> +<div class="paragraph"><p><strong>c) Gas management</strong>: With open-circuit dives this is a primary +consideration. Divers need to keep within the limits of the amount of +gas within the dive +cylinder(s), allowing for an appropriate margin for a 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 +liters/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 15-30 l/min are common. For good gas management, a guess +is not sufficient and you needs to +monitor gas consumption on a regular basis, dependent on different dive conditions and/or equipment. +The planner calculates the total volume of gas used during the dive and issues a warning +if you exceeds the total amount of gas available. Good practice demands that divers 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 you can start the detailed time-depth planning of the dive. <em>Subsurface</em> offers an unique +graphical interface for doing planning. Themechanics are +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 blue 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 the profile reflects the intended dive. Drag the waypoints to represent +the depth and duration of the dive. It is NOT necessary to specify the ascent part of the dive +since the planner calculates this, based on the settings that have been specified. +If any of the management limits (for nitrogen, oxygen or gas) are 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. Be sure the <em>Used Gas</em> value in each row +of that table corresponds to one of the gas mixtures specified in the <em>Available Gases</em> table. +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 fulfill decompression requirements for that +dive. A waypoint can be moved by selecting it 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 get a precise presentation of the dive plan. In fact, you can create the +whole dive profile by editing the <em>Dive Planner Points</em> dialog.</p></div> +<div class="paragraph"><p>Show 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. These changes can be deleted by right-clicking the gas change and +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_f20.jpg" alt="FIGURE: Planning a dive: setup" /> +</div> +</div> +<div class="paragraph"><p>Once the above steps have been completed, save by clicking the <em>Save</em> button +towards the top middle of the planner. The saved dive plan will appear +in the <strong>Dive List</strong> panel of <em>Subsurface</em>.</p></div> +<div class="paragraph"><p><strong>The dive plan details</strong></p></div> +<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>Notes</em> section of the dive planner, immediately to the left +of the <em>Dive Plan Details</em>. If a <em>Verbatim dive plan</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> +<div class="sect2"> +<h3 id="_planning_pscr_dives">13.3. Planning pSCR dives</h3> +<div class="paragraph"><p>To plan a dive using a passive semi-closed rebreather (pSCR), select <em>pSCR</em> rather than +<em>Open circuit</em> in the dropdown list. +The parameters of the pSCR dive can be set by selecting <em>File → Preferences → Graph</em> +from the main menu, where the gas consumption calculation takes into account the pSCR dump +ratio (default 10:1) as well as the metabolism rate. The calculation also takes the oxygen drop +accross the mouthpiece of the rebreather into account. If the +pO<sub>2</sub> drops below what is considered safe, a warning appears in the <em>Dive plan +details</em>. A typical pSCR configuration is with a single cylinder and one or more bail-out +cylinders. Therefore the setup of the <em>Available gases</em> and the <em>Dive planner points</em> tables +are very similar to that of a CCR dive plan, described below. However, no oxygen setpoints +are specified for pSCR dives. Below is a dive plan for a pSCR dive. The dive is comparable +to that of the CCR dive below, but note the longer ascent duration due to the lower oxygen +in the loop due to the oxygen drop across the mouthpiece of the pSCR equipment.</p></div> +<div class="imageblock" style="text-align:center;"> +<div class="content"> +<img src="images/Planner_pSCR1_f20.jpg" alt="FIGURE: Planning a pSCR dive: setup" /> +</div> +</div> +</div> +<div class="sect2"> +<h3 id="_planning_ccr_dives">13.4. Planning CCR dives</h3> +<div class="paragraph"><p>To plan a dive using a closed circuit rebreather, select the <em>CCR</em> option in the dropdown +list, circled in blue in the image below.</p></div> +<div class="paragraph"><p><strong>Available gases</strong>: In the <em>Available gases</em> table, enter the cylinder information for the +diluent cylinder and for any bail-out cylinders. Do NOT enter the information for the oxygen +cylinder since it is implied when the <em>CCR</em> dropdown selection is made.</p></div> +<div class="paragraph"><p><strong>Entering setpoints</strong>: Specify a default setpoint in the Preferences tab, by selecting <em>File → Preferences → Graph</em> from +the main menu. All user-entered segments in the <em>Dive planner points</em> table +use the default setpoint value. Then, different setpoints can be specified for dive segments +in the <em>Dive planner points</em> table. A zero setpoint +means the diver bails out to open circuit mode for that segment. Decompression is always calculated +using the setpoint of the last manually entered segment. So, to plan a bail out ascent for a +CCR dive, add a one-minute dive segment to the end with a setpoint value of 0. The decompression +algorithm does not switch deco-gases automatically while in CCR mode (i.e. when a positive setpoint is specified) but +this is calculated for bail out ascents.</p></div> +<div class="paragraph"><p>The dive profile for a CCR dive may look something like the image below.</p></div> +<div class="imageblock" style="text-align:center;"> +<div class="content"> +<img src="images/Planner_CCR1_f20.jpg" alt="FIGURE: Planning a CCR dive: setup" /> +</div> +</div> +<div class="paragraph"><p>Note that, in the <em>Dive plan details</em>, the gas consumption for a CCR segment is not calculated, +so gas consumptions of 0 liters are the norm.</p></div> +</div> +<div class="sect2"> +<h3 id="S_Replan">13.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 no way to change a saved dive plan. +To change a dive plan, select it on the <strong>Dive List</strong>. Then, in the main menu, +select <em>Log → Re-plan dive</em>. This will open the selected dive plan within the dive planner, +letting changes 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">13.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 +are specified appropriately in the top left-hand <em>Start Time</em> field. <em>Subsurface</em> +calculates the gas loading figures and the affect of the first dive is +evaluated on later dives.</p></div> +<div class="paragraph"><p>If you have just completed a long/deep dive and are planning +another dive, then highlight, in the <strong>Dive List</strong>, the dive that has just been done +then activate the planner. Depending on the start time of the planned dive, +the planner takes into account the gas loading during the completed dive +and plans accordingly.</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 you want to plan a dive using +this configuration, 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">13.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. You can also cut and paste the <em>Dive Plan Details</em> to +include 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>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 → Print</em> function 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="_description_of_the_subsurface_main_menu_items">14. 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">14.1. File</h3> +<div class="ulist"><ul> +<li> +<p> +<a href="#S_NewLogbook"><em>New Logbook</em></a> - Close the currently open dive logbook and + clear all dive information. +</p> +</li> +<li> +<p> +<em>Open logbook</em> - Open the file manager to select a dive + logbook to open. +</p> +</li> +<li> +<p> +<em>Open cloud storage</em> - Open the dive log previously saved in <a href="#S_Cloud_storage"><em>Cloud storage</em></a>. +</p> +</li> +<li> +<p> +<em>Save</em> - Save the dive logbook currently open. +</p> +</li> +<li> +<p> +<em>Save to cloud storage</em> - Save the current dive log to <a href="#S_Cloud_storage"><em>Cloud storage</em></a>. +</p> +</li> +<li> +<p> +<em>Save as</em> - Save the current logbook under a different file name. +</p> +</li> +<li> +<p> +<em>Close</em> - Close the dive logbook currently open. +</p> +</li> +<li> +<p> +<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. +</p> +</li> +<li> +<p> +<a href="#S_PrintDivelog"><em>Print</em></a> - Print the currently open logbook. +</p> +</li> +<li> +<p> +<a href="#S_Preferences"><em>Preferences</em></a> - Set the <em>Subsurface</em> preferences. +</p> +</li> +<li> +<p> +<a href="#S_FindMovedImages"><em>Find moved images</em></a> - If photos taken during dives have been moved to + a different disk or directory, locate them and link them to the appropriate dives. +</p> +</li> +<li> +<p> +<a href="#S_Configure"><em>Configure dive computer</em></a> - Edit the configuration of a dive computer. +</p> +</li> +<li> +<p> +<em>Quit</em> - Quit <em>Subsurface</em>. +</p> +</li> +</ul></div> +</div> +<div class="sect2"> +<h3 id="_import">14.2. Import</h3> +<div class="ulist"><ul> +<li> +<p> +<a href="#S_ImportDiveComputer"><em>Import from dive computer</em></a> - Import dive information + from a dive computer. +</p> +</li> +<li> +<p> +<a href="#Unified_import"><em>Import Log Files</em></a> - Import dive information from a file in + in a <em>Subsurface</em>-compatible format. +</p> +</li> +<li> +<p> +<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. +</p> +</li> +<li> +<p> +<a href="#S_ImportingDivelogsDe"><em>Import from Divelogs.de</em></a> - Import dive information + from <em>www.Divelogs.de</em>. +</p> +</li> +</ul></div> +</div> +<div class="sect2"> +<h3 id="_log">14.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> +<em>Edit dive</em> - Edit a dive where the profile was entered by hand and not from a dive computer. +</p> +</li> +<li> +<p> +<a href="#S_DivePlanner"><em>Plan Dive</em></a> - Plan dives. +</p> +</li> +<li> +<p> +<a href="#S_Replan"><em>Edit dive in planner</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> - 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. +</p> +</li> +<li> +<p> +<a href="#S_Renumber"><em>Renumber</em></a> - Renumber the dives listed in the <strong>Dive List</strong> + panel. +</p> +</li> +<li> +<p> +<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 coordinate 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">14.4. View</h3> +<div class="ulist"><ul> +<li> +<p> +<a href="#S_ViewPanels"><em>All</em></a> - View the four main <em>Subsurface</em> panels + all at once. +</p> +</li> +<li> +<p> +<a href="#S_ViewPanels"><em>Dive List</em></a> - View only the <strong>Dive List</strong> panel. +</p> +</li> +<li> +<p> +<a href="#S_ViewPanels"><em>Profile</em></a> - View only the <strong>Dive Profile</strong> panel. +</p> +</li> +<li> +<p> +<a href="#S_ViewPanels"><em>Info</em></a> - View only the <strong>Notes</strong> panel. +</p> +</li> +<li> +<p> +<a href="#S_ViewPanels"><em>Globe</em></a> - View only the <strong>World Map</strong> panel. +</p> +</li> +<li> +<p> +<em>Yearly Statistics</em> - Display summary statistics about dives during this and past + years. +</p> +</li> +<li> +<p> +<em>Prev DC</em> - Switch to data from previous dive computer, if a single dive was logged from more than one. +</p> +</li> +<li> +<p> +<em>Next DC</em> - Switch to next dive computer. +</p> +</li> +<li> +<p> +<em>Full Screen</em> - Toggles Full Screen mode. +</p> +</li> +</ul></div> +</div> +<div class="sect2"> +<h3 id="_share_on">14.5. Share on</h3> +<div class="ulist"><ul> +<li> +<p> +<a href="#S_Facebook"><em>Facebook</em></a> - Share the currently selected dive on your Facebook timeline. +</p> +</li> +</ul></div> +</div> +<div class="sect2"> +<h3 id="_help">14.6. Help</h3> +<div class="ulist"><ul> +<li> +<p> +<em>About Subsurface</em> - Show a panel with the version number of <em>Subsurface</em> as + well as licensing information. +</p> +</li> +<li> +<p> +<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>. +</p> +</li> +<li> +<p> +<a href="#S_UserSurvey"><em>User survey</em></a> - Help to make <em>Subsurface</em> even better by taking part in our user survey + or by completing another survey if your diving habits have changed. +</p> +</li> +<li> +<p> +<em>User manual</em> - Open a window showing this user manual. +</p> +</li> +</ul></div> +</div> +</div> +</div> +<div class="sect1"> +<h2 id="_appendix_a_operating_system_specific_information_for_importing_dive_information_from_a_dive_computer">15. 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">15.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, the 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> +<li> +<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&f=USB%20Bridges&pn=CP2101">Silicon Labs document and software repository</a>. +</p> +</li> +</ul></div> +</div> +<div class="sect2"> +<h3 id="S_HowFindDeviceName">15.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 connecting a dive computer by using a USB connector, usually +<em>Subsurface</em> will either propose a drop down list with 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 +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 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 +won’t be able to use the USB port. Let us assume one’s username is <em>johnB</em>.</p></div> +<div class="ulist"><ul> +<li> +<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. +</p> +</li> +<li> +<p> +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. +</p> +</li> +<li> +<p> +Under some circumstances this change takes only effect (eg. on Ubuntu) after +one logs out and then logs in again. +</p> +</li> +</ul></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">15.3. Manually 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, Petrel and Nerd there is a +different procedure to get the device’s 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, be sure 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’s user guide. When using a Shearwater Predator/Petrel/Nerd, select +<em>Dive Log → 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="sect3"> +<h4 id="_on_windows_2">15.3.1. On Windows:</h4> +<div class="paragraph"><p>Bluetooth is most likely already enabled. For pairing with the dive computer choose +<em>Control Panel → Bluetooth Devices → Add Wireless Device</em>. +This should bring up a dialog showing your dive computer (which should be in Bluetooth mode) and +allowing pairing. Right click on it and choose <em>Properties→ 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> +<div class="sect3"> +<h4 id="_on_macos">15.3.2. On MacOS:</h4> +<div class="paragraph"><p>Click on the Bluetooth symbol in the menu bar and select <em>Set up +Bluetooth Device…</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 complete, 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> +<div class="sect3"> +<h4 id="_on_linux">15.3.3. On Linux</h4> +<div class="paragraph"><p>Be sure 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 straightforward. For instance, Gnome3 shows a +Bluetooth icon on the right of the toolbar at the top of the screen. +Users have reported difficulties with some Bluetooth controllers. If you have an onboard controller, +try that first. It is simplest if you remove any USB Bluetooth dongles. If you have a USB dongle that +came with your dive computer, try that before any others.</p></div> +<div class="paragraph"><p>Setting up a connection to download dives from your Bluetooth-enabled device, such as the +<em>Shearwater Petrel</em>, is not yet an automated process and will generally require the command prompt. +It is essentially a three step process.</p></div> +<div class="ulist"><ul> +<li> +<p> +Enable the Bluetooth controller and pair your dive computer +</p> +</li> +<li> +<p> +Establish an RFCOMM connection +</p> +</li> +<li> +<p> +Download the dives with Subsurface +</p> +</li> +</ul></div> +<div class="paragraph"><p>Ensure the dive computer is in upload mode. On the <em>Shearwater Petrel</em>, <em>Petrel 2</em> and <em>Nerd</em> +cycle through the menu, select <em>Dive Log</em>, then <em>Upload Log</em>. The display will read <em>Initializing</em>, then +<em>Wait PC 3:00</em> and will countdown. Once the connection is established, the display reads <em>Wait CMD …</em> +and the countdown continues. When downloading the dive from Subsurface, the display reads <em>Sending</em> then +<em>Sent Dive</em>.</p></div> +<div class="paragraph"><p>To establish the connection, establish root access through <code>sudo</code> or <code>su</code>. +The correct permission is required to download the dives in the computer. On most Linux systems this means becoming +a member of the dialout group (This is identical as for many dive computers using a Linux USB port, described +in the previous section). On the command terminal, enter:</p></div> +<div class="paragraph"><p><code>sudo usermod -a -G dialout username</code></p></div> +<div class="paragraph"><p>Then log out and log in for the change to take effect.</p></div> +<div class="sect4"> +<h5 id="_enabling_the_bluetooth_controller_and_pairing_your_dive_computer">Enabling the Bluetooth controller and pairing your dive computer</h5> +<div class="paragraph"><p>Attempt to set up the Bluetooth controller and pair your dive computer using the graphical +environment of the operating system. After setting the dive computer to upload mode, click the Bluetooth icon in the system tray +and select <em>Add new device</em>. The dive computer should appear. If asked for a password, enter 0000. +Write down or copy the MAC address of your dive computer - this needed later and should be in the form 00:11:22:33:44:55.</p></div> +<div class="paragraph"><p>If the graphical method doesn’t work, pair the device from the command line. Open a terminal +and use <code>hciconfig</code> to check the Bluetooth controller status</p></div> +<div class="literalblock"> +<div class="content"> +<pre><code>$ hciconfig +hci0: Type: BR/EDR Bus: USB + BD Address: 01:23:45:67:89:AB ACL MTU: 310:10 SCO MTU: 64:8 + *DOWN* + RX bytes:504 acl:0 sco:0 events:22 errors:0 + TX bytes:92 acl:0 sco:0 commands:21 errors:0</code></pre> +</div></div> +<div class="paragraph"><p>This indicates a Bluetooth controller with MAC address 01:23:45:67:89:AB, connected as hci0. +Its status is <em>DOWN</em>, i.e. not powered. Additional controllers will appear as hci1, etc. +If there is not a Bluetooth dongle plugged in upon booting the computer, hci0 is probably the onboard. +Now power on the controller and enable authentication:</p></div> +<div class="literalblock"> +<div class="content"> +<pre><code>sudo hciconfig hci0 up auth+ (enter password when prompted) +hciconfig +hci0: Type: BR/EDR Bus: USB + BD Address: 01:23:45:67:89:AB ACL MTU: 310:10 SCO MTU: 64:8 + *UP RUNNING PSCAN AUTH* + RX bytes:1026 acl:0 sco:0 events:47 errors:0 + TX bytes:449 acl:0 sco:0 commands:46 errors:0</code></pre> +</div></div> +<div class="paragraph"><p>Check that the status now includes <code><em>UP</em>, <em>RUNNING</em> AND <em>AUTH</em></code>.</p></div> +<div class="paragraph"><p>If there are multiple controllers running, it’s easiest to off the unused controller(s). For example, for <code>hci1</code>:</p></div> +<div class="literalblock"> +<div class="content"> +<pre><code>sudo hciconfig hci1 down</code></pre> +</div></div> +<div class="paragraph"><p>Next step is to <em>trust</em> and <em>pair</em> the dive computer. On distros with Bluez 5, such as Fedora 22, +one can use a tool called <code>blutootctl</code>, which will bring up its own command prompt.</p></div> +<div class="literalblock"> +<div class="content"> +<pre><code>bluetoothctl +[NEW] Controller 01:23:45:67:89:AB localhost.localdomain [default] +[bluetooth]# agent on +Agent registered +[bluetooth]# default-agent +Default agent request successful +[bluetooth]# scan on <----now set your dive computer to upload mode +Discovery started +[CHG] Controller 01:23:45:67:89:AB Discovering: yes +[NEW] Device 00:11:22:33:44:55 Petrel +[bluetooth]# trust 00:11:22:33:44:55 <----you can use the tab key to autocomplete the MAC address +[CHG] Device 00:11:22:33:44:55 Trusted: yes +Changing 00:11:22:33:44:55 trust succeeded +[bluetooth]# pair 00:11:22:33:44:55 +Attempting to pair with 00:11:22:33:44:55 +[CHG] Device 00:11:22:33:44:55 Connected: yes +[CHG] Device 00:11:22:33:44:55 UUIDs: 00001101-0000-1000-8000-0089abc12345 +[CHG] Device 00:11:22:33:44:55 Paired: yes +Pairing successful +[CHG] Device 00:11:22:33:44:55 Connected: no</code></pre> +</div></div> +<div class="paragraph"><p>If asked for a password, enter 0000. It’s ok if the last line says <em>Connected: no</em>. The important part +is the line above, <code>Pairing successful</code>.</p></div> +<div class="paragraph"><p>If the system has Bluez version 4 (e.g. Ubuntu 12.04 through to 15.04), there is probably not a +<code>bluetoothctl</code>, but a script called <code>bluez-simple-agent</code> or just <code>simple-agent</code>.</p></div> +<div class="literalblock"> +<div class="content"> +<pre><code>hcitool -i hci0 scanning +Scanning ... + 00:11:22:33:44:55 Petrel + bluez-simple-agent hci0 00:11:22:33:44:55</code></pre> +</div></div> +<div class="paragraph"><p>Once ther dive computer is pired, set up the RFCOMM connection</p></div> +</div> +<div class="sect4"> +<h5 id="_establishing_the_rfcomm_connection">Establishing the RFCOMM connection</h5> +<div class="paragraph"><p>The command to establish an RFCOMM connection is:</p></div> +<div class="paragraph"><p><code>sudo rfcomm -i <controller> connect <dev> <bdaddr> [channel]</code></p></div> +<div class="ulist"><ul> +<li> +<p> +<code><controller></code> is the Bluetooth controller, <code>hci0</code>. +</p> +</li> +<li> +<p> +<code><dev></code> is the RFCOMM device file, <code>rfcomm0</code> +</p> +</li> +<li> +<p> +<code><bdaddr></code> is the dive computer’s MAC address, <code>00:11:22:33:44:55</code> +</p> +</li> +<li> +<p> +<code>[channel]</code> is the dive computer’s Bluetooth channel we need to connect to. +</p> +</li> +</ul></div> +<div class="paragraph"><p>If one omits it, channel 1 is assumed. Based on a limited number of user reports, +the appropriate channel for the dive computer is probably:</p></div> +<div class="ulist"><ul> +<li> +<p> +<em>Shearwater Petrel 1</em>: channel 1 +</p> +</li> +<li> +<p> +<em>Shearwater Petrel 2</em>: channel 5 +</p> +</li> +<li> +<p> +<em>Shearwater Nerd</em>: channel 5 +</p> +</li> +<li> +<p> +<em>Heinrichs-Weikamp OSTC Sport</em>: channel 1 +</p> +</li> +</ul></div> +<div class="paragraph"><p>E.g. to connect a <em>Shearwater Petrel 2</em>, set the dive computer to upload mode and enter:</p></div> +<div class="literalblock"> +<div class="content"> +<pre><code>sudo rfcomm -i hci0 connect rfcomm0 00:11:22:33:44:55 5 (enter a password, probably 0000, when prompted)</code></pre> +</div></div> +<div class="paragraph"><p>This gives the response:</p></div> +<div class="literalblock"> +<div class="content"> +<pre><code>Connected /dev/rfcomm0 to 00:11:22:33:44:55 on channel 5 +Press CTRL-C for hangup</code></pre> +</div></div> +<div class="paragraph"><p>To connect a _Shearwater Petrel 1+ or + HW OSTC Sport+, set the dive computer to upload mode and enter:</p></div> +<div class="literalblock"> +<div class="content"> +<pre><code>sudo rfcomm -i hci0 connect rfcomm0 00:11:22:33:44:55 (enter a password, probably 0000, when prompted) +Connected /dev/rfcomm0 to 00:11:22:33:44:55 on channel 1 +Press CTRL-C for hangup</code></pre> +</div></div> +<div class="paragraph"><p>If the specific channel the dive computer needs is not known, or the channel in the list above doesn’t +work, the command <code>sdptool records</code> should help determine the appropriate channel. The output +below is for a <em>Shearwater Petrel 2</em>.</p></div> +<div class="literalblock"> +<div class="content"> +<pre><code>sdptool -i hci0 records 00:11:22:33:44:55 +Service Name: Serial Port +Service RecHandle: 0x10000 +Service Class ID List: + "Serial Port" (0x1101) + Protocol Descriptor List: + "L2CAP" (0x0100) + "RFCOMM" (0x0003) + Channel: 5</code></pre> +</div></div> +<div class="paragraph"><p>For a Bluetooth dive computer not in the list above, or if the channel listed is not correct, please +let the Subsurface developers know on the user forum or the developer mailing list <em>subsurface@subsurface-divelog.org</em>.</p></div> +</div> +<div class="sect4"> +<h5 id="_download_the_dives_with_subsurface">Download the dives with Subsurface</h5> +<div class="paragraph"><p>After establishing the RFCOMM connection and while the dive computer’s upload mode countdown is still running, go to_Subsurface_, select <em>Import→Import from dive computer</em> and enter appropriate Vendor (e.g. <em>Shearwater</em>), Dive Computer (<em>Petrel</em>), Device or Mount Point (<em>/dev/rfcomm0</em>) and click <em>Download</em>.</p></div> +</div> +</div> +</div> +</div> +</div> +<div class="sect1"> +<h2 id="_appendix_b_dive_computer_specific_information_for_importing_dive_information">16. APPENDIX B: Dive Computer specific information for importing dive data.</h2> +<div class="sectionbody"> +<div class="sect2"> +<h3 id="S_ImportUemis">16.1. Importing from 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 you don’t 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/<your_username>/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 you 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 you download 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 straightforward. +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. You +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">16.2. Importing from 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 recognize 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>. Windows-based IrDA +drivers for the Uwatec can also be downloaded from the ScubaPro web site, with drivers located on +the download page for the ScubaPro SmartTrak software.</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">16.3. Importing 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’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="S_ImportingXDeep">16.4. Importing from xDEEP BLACK</h3> +<div class="admonitionblock"> +<table><tr> +<td class="icon"> +<img src="images/icons/HW_xdeepblack.jpg" alt="Note" /> +</td> +<td class="content">Each dive has to be individually saved as UDDF file using "Export UDDF" option in BLACK’s logbook menu. +When mounted as a USB drive UDDF files are available in LOGBOOK directory. +Note: The xDEEP BLACK saves NDL time but 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 xDEEP BLACK.</td> +</tr></table> +</div> +</div> +<div class="sect2"> +<h3 id="_importing_from_shearwater_predator_petrel_nerd_using_bluetooth">16.5. Importing from Shearwater Predator/Petrel/Nerd using Bluetooth</h3> +<div class="admonitionblock"> +<table><tr> +<td class="icon"> +<img src="images/icons/predator.jpg" alt="Note" /> +</td> +<td class="content">Specific instructions for downloading dives using Bluetooth are given in the section above, <a href="#S_Bluetooth"><em>Connecting Subsurface to a Bluetooth-enabled dive computer</em></a>.</td> +</tr></table> +</div> +</div> +<div class="sect2"> +<h3 id="S_PoseidonMkVI">16.6. Importing from 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 utilizes the IrDA infra-red protocol. Only data for one dive +can be downloaded at a time, in three files:</td> +</tr></table> +</div> +<div class="ulist"><ul> +<li> +<p> +Setup configuration for the dive and key dive parameters (file with a .txt + extension) +</p> +</li> +<li> +<p> +Dive log details (file with a .csv extension) +</p> +</li> +<li> +<p> +Redbook format dive log (file with .cvsr extension). This is a compressed + version of the dive log using a proprietary format. +</p> +</li> +</ul></div> +<div class="paragraph"><p><em>Subsurface</em> accesses the .txt and the .csv files to get dive log information.</p></div> +</div> +<div class="sect2"> +<h3 id="_importing_from_apd_inspiration_evolution_ccr">16.7. Importing from APD Inspiration/Evolution 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> +Download the dive using <em>AP Communicator</em>. +</p> +</li> +<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> +With 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) or TextWrangler (Mac). +</p> +</li> +<li> +<p> +Copy the contents of the clipboard into the text editor and save the text file + with a filename extension of <em>.apd</em> +</p> +</li> +<li> +<p> +Within <em>Subsurface</em>, select <em>Import → 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 (labeled <em>Filter:</em>), select "APD log viewer". +</p> +</li> +<li> +<p> +On the list of file names select the <em>.apd</em> file created. An import + dialogue opens showing the default settings for the data in the +<em>.apd</em> file. If changes are required, + do this as for <a href="#S_ImportingCSVDives">CSV imports</a>. +</p> +</li> +</ul></div> +<div class="imageblock" style="text-align:center;"> +<div class="content"> +<img src="images/APD_CSVimportF22.jpg" alt="Figure: APD log viewer import" /> +</div> +</div> +<div class="ulist"><ul> +<li> +<p> +The top left hand dropdown box in the import panel lets you select the APD dive computer + for which the dive log needs to be imported. The default it is DC1, <em>i.e.</em> the + first of the two dive computers the APD uses. It is possible to sequentially + import the data for both dive computers by first importing CD1 and then DC2.(<strong>Hint</strong>: The logs + for the two dive computers are viewed by selecting <em>View → Next DC</em> from + the Main Menu after the uploading has been completed) +</p> +</li> +<li> +<p> +Click the <em>Ok</em> button at the bottom of the import panel. +</p> +</li> +</ul></div> +<div class="paragraph"><p>The APD dive log will appear within <em>Subsurface</em>. The dive computer- generated ceiling +provided by the Inspiration can be viewed by selecting the appropriate +button on the left of the <strong>Dive Profile</strong>. Cylinder pressure data are not logged +by the APD equipment but can be manually entered in the <em>Equipment</em> Tab.</p></div> +</div> +</div> +</div> +<div class="sect1"> +<h2 id="_appendix_c_exporting_dive_log_information_from_external_dive_log_software">17. 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="olist arabic"><ol class="arabic"> +<li> +<p> +Export the foreign dive log data to format that is accessible from + <em>Subsurface</em>. +</p> +</li> +<li> +<p> +Import the accessible dive log data into <em>Subsurface</em>. +</p> +</li> +</ol></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">17.1. Exporting 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. +</p> +</li> +<li> +<p> +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 +</p> +</li> +<li> +<p> +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 → 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 you need to locate the DM4/DM5 database +where the dives are stored. You 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 → About</em> +</p> +</li> +<li> +<p> +Click <em>Copy</em> after text <em>Copy log folder path to clipboard</em> +</p> +</li> +<li> +<p> +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’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_atomic_logbook">17.2. Exporting from Atomic Logbook</h3> +<div class="admonitionblock" id="Atomic_Export"> +<table><tr> +<td class="icon"> +<img src="images/icons/atomiclogo.jpg" alt="Note" /> +</td> +<td class="content">Atomic Logbook is a Windows software by Atomic Aquatics. It allows +downloading of dive information from Cobalt and Cobalt 2 dive computers. +The divelog is kept in a SQLite database at +C:\ProgramData\AtomicsAquatics\Cobalt-Logbook\Cobalt.db. This file can +be directly imported to Subsurface.</td> +</tr></table> +</div> +</div> +<div class="sect2"> +<h3 id="_exporting_from_mares_dive_organiser_v2_1">17.3. 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 Organizer 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 Organizer-registered divers on the particular +computer and all Mares dive computers used. The safest way to get a copy +of the dive database is to export the information to another compatible format +which can then be imported into <em>Subsurface</em>.</td> +</tr></table> +</div> +<div class="olist arabic"><ol class="arabic"> +<li> +<p> +Within Dive Organizer, select + <em>Database → Backup</em> from the main menu and back up the database to the desk + top. + This creates a zipped file DiveOrganizerxxxxx.dbf. +</p> +</li> +<li> +<p> +Rename the file to + DiveOrganizerxxxxx.zip. Inside the zipped directory is a file + <em>DiveOrganizer.sdf</em>. +</p> +</li> +<li> +<p> +Extract the <em>.sdf</em> file from the zipped folder to your Desktop. +</p> +</li> +<li> +<p> +The password for accessing the .zip file is <em>mares</em>. +</p> +</li> +</ol></div> +</div> +<div class="sect2"> +<h3 id="S_ImportingDivingLog">17.4. Exporting from <strong>DivingLog 5.0 and 6.0</strong></h3> +<div class="admonitionblock"> +<table><tr> +<td class="icon"> +<img src="images/icons/divingloglogo.jpg" alt="Note" /> +</td> +<td class="content">The best way to bring your logs from DivingLog to Subsurface is to +convert the whole database. This is because other export formats do not +include all the details, and would lack, for example, gas switches and +information of what units are used. With database import, all this +information is included and readily available.</td> +</tr></table> +</div> +<div class="paragraph"><p>To transfer all files from DivingLog to Subsurface:</p></div> +<div class="olist arabic"><ol class="arabic"> +<li> +<p> +In DivingLog open the <em>File → Export → SQLite</em> menu +</p> +</li> +<li> +<p> +Select <em>Settings</em> button +</p> +</li> +<li> +<p> +Set the <em>RTF2Plaintext</em> to <em>true</em> +</p> +</li> +<li> +<p> +Close the Settings dialog +</p> +</li> +<li> +<p> +Click <em>Export</em> button and select the filename +</p> +</li> +</ol></div> +<div class="paragraph"><p>Once this is done, open the saved database file with Subsurface and the +dives are automatically converted to Subsurface’s own format. Last step to do is +save the log file in Subsurface.</p></div> +</div> +</div> +</div> +<div class="sect1"> +<h2 id="_appendix_d_exporting_a_spreadsheet_to_csv_format">18. APPENDIX D: Exporting a spreadsheet to CSV format</h2> +<div class="sectionbody"> +<div class="paragraph" id="S_Appendix_D"><p>Many divers keep a dive log in some form of digital file, commonly a spreadsheet +with various fields of information. These logs can be easily imported into <em>Subsurface</em> 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 to <em>Subsurface</em>. +Creating a .CSV is straightforward, although the procedure is somewhat different +according to which spreadsheet program is used.</p></div> +<div class="paragraph"><p>Organize the diving data in the spreadsheet, so 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 number, Date, +Time, Duration, Location, GPS, Max Depth, Mean Depth, Buddy, Notes, Weight and Tags). +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 should be used (no mix of imperial and metric units) +</p> +</li> +<li> +<p> +Tags and buddies: values should be separated using a comma. +</p> +</li> +<li> +<p> +GPS position: use decimal degrees, e.g. 30.22496 30.821798 +=== <em>LibreOffice Calc</em> and <em>OpenOffice Calc</em> +</p> +</li> +</ol></div> +<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 → 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>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_ImportingCSVDives">Importing CSV dives</a>.</p></div> +<div class="sect2"> +<h3 id="_microsoft_em_excel_em">18.1. 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 uses the new character as a separator. +You 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, 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. +</p> +</li> +<li> +<p> +Do one of the following: +</p> +<div class="ulist"><ul> +<li> +<p> +In Windows 7, click the <em>Formats</em> tab, and then click <em>Customize this format</em>. +</p> +</li> +<li> +<p> +In Windows XP, click the <em>Regional Options</em> tab, and then click <em>Customize</em>. +</p> +</li> +</ul></div> +</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>. Be sure 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. You can double check the .CSV file by +opening it with a text editor, then import the dive data as +explained on the section <a href="#S_ImportingCSVDives">Importing CSV dives</a>.</p></div> +</div> +</div> +</div> +<div class="sect1"> +<h2 id="S_APPENDIX_E">19. APPENDIX E: Writing a custom print template</h2> +<div class="sectionbody"> +<div class="paragraph"><p><em>Subsurface</em> has a way to create or modify templates for printing dive logs to +produce customized printouts of them. Templates written in HTML, as well as a simple +Grantlee instruction set, are rendered to the print device by <em>Subsurface</em>.</p></div> +<div class="paragraph"><p>Templates are accessed using the print dialogue (see image <strong>B</strong> below).</p></div> +<div class="imageblock" style="text-align:center;"> +<div class="content"> +<img src="images/Print1_f22.jpg" alt="FIGURE: Print dialogue" /> +</div> +</div> +<div class="paragraph"><p>The buttons under the <em>Template</em> dropdown box lets you <em>Edit</em>, <em>Delete</em>, +<em>Import</em> and <em>Export</em> templates (see image <strong>A</strong> above). New or modified templates are stored as HTML +files in the same directory as the dive log being processed. In order to create or modify +a template, select one of the templates from the template dropdown list in the print dialogue +(see image <strong>B</strong> above). Choose an existing template that resembles the final desired printout. Then select <em>Edit</em>.</p></div> +<div class="paragraph"><p>The Edit Panel has three tabs:</p></div> +<div class="imageblock" style="text-align:center;"> +<div class="content"> +<img src="images/Template1_f22.jpg" alt="FIGURE: template edit dialogue" /> +</div> +</div> +<div class="paragraph"><p>1) The <em>Style</em> tab (image <strong>A</strong> above) controls the font, line spacing and color template used for printing the dive log. + The style attributes are editable. Choose one of the four color palettes used for color printing.</p></div> +<div class="paragraph"><p>2) The <em>Colors</em> tab (image <strong>B</strong> above) allows editing the colors used for printing the dive log. The colors are highly + customizable: the <em>Edit</em> buttons in the <em>Colors</em> tab allows choosing arbitrary colors for different + components of the dive log printout.</p></div> +<div class="paragraph"><p>3) The <em>Template</em> tab of the Edit Panel (see image below) allows creating a template using HTML as well as a few + Grantlee programming primitives. Grantlee can create and format HTML code in + a highly simple but efficient way (see below). The HTML of the template can be edited and saved. The saved + template is stored in the same directory as the dive being processed. By default, a <em>Custom</em> + template is a skeleton with no specific print instructions. The information printed + needs to be specified and formatted in the template by replacing the section marked with: + "<!-- Template must be filled -→". Writing HTML code with Grantlee instructions allows unlimited + freedom in determining what is printed and in which way it should be rendered.</p></div> +<div class="imageblock" style="text-align:center;"> +<div class="content"> +<img src="images/Template2_f22.jpg" alt="FIGURE:Template tab" /> +</div> +</div> +<div class="paragraph"><p>You can adapt any of the existing templates and save it to the dive log directory. The standard templates (e.g. One dive, Six dives, +Table) can be modified in this way. After completing the edits, use the <em>Export</em> button in the print +dialogue to save the new template using a new template name.</p></div> +<div class="paragraph"><p>To write a custom template, the following elements must exist so the template will be correctly handled and rendered.</p></div> +<div class="sect2"> +<h3 id="_main_dive_loop">19.1. Main dive loop</h3> +<div class="paragraph"><p><em>Subsurface</em> exports a dive list called (<strong>dives</strong>) to the <em>Grantlee</em> back end. It is possible to iterate over the list as follows: +.template.html</p></div> +<div class="literalblock"> +<div class="content"> +<pre><code> {% for dive in dives %} + <h1> {{ dive.number }} </h1> + {% endfor %}</code></pre> +</div></div> +<div class="literalblock"> +<div class="title">output.html</div> +<div class="content"> +<pre><code> <h1> 1 </h1> + <h1> 2 </h1> + <h1> 3 </h1></code></pre> +</div></div> +<div class="paragraph"><p>Additional information about <em>Grantlee</em> can be found at <a href="http://www.grantlee.org/apidox/for_themers.html">here</a></p></div> +</div> +<div class="sect2"> +<h3 id="_grantlee_exported_variables">19.2. Grantlee exported variables</h3> +<div class="paragraph"><p>Only a subset of the dive data is exported:</p></div> +<div class="tableblock"> +<table rules="all" +width="100%" +frame="border" +cellspacing="0" cellpadding="4"> +<col width="50%" /> +<col width="50%" /> +<tbody> +<tr> +<td align="left" valign="top"><p class="table"><strong>Name</strong></p></td> +<td align="left" valign="top"><p class="table"><strong>Description</strong></p></td> +</tr> +<tr> +<td align="left" valign="top"><p class="table">number</p></td> +<td align="left" valign="top"><p class="table">(<strong>int</strong>) dive number</p></td> +</tr> +<tr> +<td align="left" valign="top"><p class="table">id</p></td> +<td align="left" valign="top"><p class="table">(<strong>int</strong>) unique dive ID, should be used to fetch the dive profile</p></td> +</tr> +<tr> +<td align="left" valign="top"><p class="table">date</p></td> +<td align="left" valign="top"><p class="table">(<strong>string</strong>) date of the dive</p></td> +</tr> +<tr> +<td align="left" valign="top"><p class="table">time</p></td> +<td align="left" valign="top"><p class="table">(<strong>string</strong>) time of the dive</p></td> +</tr> +<tr> +<td align="left" valign="top"><p class="table">location</p></td> +<td align="left" valign="top"><p class="table">(<strong>string</strong>) location of the dive</p></td> +</tr> +<tr> +<td align="left" valign="top"><p class="table">duration</p></td> +<td align="left" valign="top"><p class="table">(<strong>string</strong>) duration of the dive</p></td> +</tr> +<tr> +<td align="left" valign="top"><p class="table">depth</p></td> +<td align="left" valign="top"><p class="table">(<strong>string</strong>) depth of the dive</p></td> +</tr> +<tr> +<td align="left" valign="top"><p class="table">divemaster</p></td> +<td align="left" valign="top"><p class="table">(<strong>string</strong>) dive master for the dive</p></td> +</tr> +<tr> +<td align="left" valign="top"><p class="table">buddy</p></td> +<td align="left" valign="top"><p class="table">(<strong>string</strong>) buddy for the dive</p></td> +</tr> +<tr> +<td align="left" valign="top"><p class="table">airTemp</p></td> +<td align="left" valign="top"><p class="table">(<strong>string</strong>) air temperature of the dive</p></td> +</tr> +<tr> +<td align="left" valign="top"><p class="table">waterTemp</p></td> +<td align="left" valign="top"><p class="table">(<strong>string</strong>) water temperature of the dive</p></td> +</tr> +<tr> +<td align="left" valign="top"><p class="table">notes</p></td> +<td align="left" valign="top"><p class="table">(<strong>string</strong>) dive notes</p></td> +</tr> +<tr> +<td align="left" valign="top"><p class="table">rating</p></td> +<td align="left" valign="top"><p class="table">(<strong>int</strong>) dive rating which ranges from 0 to 5</p></td> +</tr> +<tr> +<td align="left" valign="top"><p class="table">sac</p></td> +<td align="left" valign="top"><p class="table">(<strong>string</strong>) SAC value for the dive</p></td> +</tr> +<tr> +<td align="left" valign="top"><p class="table">tags</p></td> +<td align="left" valign="top"><p class="table">(<strong>string</strong>) list of dive tags for the dive</p></td> +</tr> +<tr> +<td align="left" valign="top"><p class="table">gas</p></td> +<td align="left" valign="top"><p class="table">(<strong>string</strong>) list of gases used in the dive</p></td> +</tr> +<tr> +<td align="left" valign="top"><p class="table">suit</p></td> +<td align="left" valign="top"><p class="table">(<strong>string</strong>) the suit used for the dive</p></td> +</tr> +<tr> +<td align="left" valign="top"><p class="table">cylinders</p></td> +<td align="left" valign="top"><p class="table">(<strong>string</strong>) complete information of all used cylinders</p></td> +</tr> +<tr> +<td align="left" valign="top"><p class="table">cylinder0-7</p></td> +<td align="left" valign="top"><p class="table">(<strong>string</strong>) information about a specific cylinder</p></td> +</tr> +<tr> +<td align="left" valign="top"><p class="table">weights</p></td> +<td align="left" valign="top"><p class="table">(<strong>string</strong>) complete information of all used weight systems</p></td> +</tr> +<tr> +<td align="left" valign="top"><p class="table">weight0-5</p></td> +<td align="left" valign="top"><p class="table">(<strong>string</strong>) information about a specific weight system</p></td> +</tr> +<tr> +<td align="left" valign="top"><p class="table">maxcns</p></td> +<td align="left" valign="top"><p class="table">(<strong>string</strong>) maxCNS value for the dive</p></td> +</tr> +<tr> +<td align="left" valign="top"><p class="table">otu</p></td> +<td align="left" valign="top"><p class="table">(<strong>string</strong>) OTU value for the dive</p></td> +</tr> +</tbody> +</table> +</div> +<div class="paragraph"><p><em>Subsurface</em> also exports <strong>template_options</strong> data. This data must be used as <em>CSS</em> values to provide a dynamically +editable template. The exported data is shown in the following table:</p></div> +<div class="tableblock"> +<table rules="all" +width="100%" +frame="border" +cellspacing="0" cellpadding="4"> +<col width="50%" /> +<col width="50%" /> +<tbody> +<tr> +<td align="left" valign="top"><p class="table"><strong>Name</strong></p></td> +<td align="left" valign="top"><p class="table"><strong>Description</strong></p></td> +</tr> +<tr> +<td align="left" valign="top"><p class="table">font</p></td> +<td align="left" valign="top"><p class="table">(<strong>string</strong>) font family</p></td> +</tr> +<tr> +<td align="left" valign="top"><p class="table">borderwidth</p></td> +<td align="left" valign="top"><p class="table">(<strong>int</strong>) border-width value dynamically calculated as 0.1% of the page width with minimum value of 1px</p></td> +</tr> +<tr> +<td align="left" valign="top"><p class="table">font_size</p></td> +<td align="left" valign="top"><p class="table">(<strong>double</strong>) size of fonts in vw, ranges between 1.0 and 2.0</p></td> +</tr> +<tr> +<td align="left" valign="top"><p class="table">line_spacing</p></td> +<td align="left" valign="top"><p class="table">(<strong>double</strong>) distance between text lines, ranges between 1.0 and 3.0</p></td> +</tr> +<tr> +<td align="left" valign="top"><p class="table">color1</p></td> +<td align="left" valign="top"><p class="table">(<strong>string</strong>) background color</p></td> +</tr> +<tr> +<td align="left" valign="top"><p class="table">color2</p></td> +<td align="left" valign="top"><p class="table">(<strong>string</strong>) primary table cell color</p></td> +</tr> +<tr> +<td align="left" valign="top"><p class="table">color3</p></td> +<td align="left" valign="top"><p class="table">(<strong>string</strong>) secondary table cell color</p></td> +</tr> +<tr> +<td align="left" valign="top"><p class="table">color4</p></td> +<td align="left" valign="top"><p class="table">(<strong>string</strong>) primary text color</p></td> +</tr> +<tr> +<td align="left" valign="top"><p class="table">color5</p></td> +<td align="left" valign="top"><p class="table">(<strong>string</strong>) secondary text color</p></td> +</tr> +<tr> +<td align="left" valign="top"><p class="table">color6</p></td> +<td align="left" valign="top"><p class="table">(<strong>string</strong>) border colors</p></td> +</tr> +</tbody> +</table> +</div> +<div class="literalblock"> +<div class="title">template.html</div> +<div class="content"> +<pre><code> border-width: {{ template_options.borderwidth }}px;</code></pre> +</div></div> +<div class="literalblock"> +<div class="title">output.html</div> +<div class="content"> +<pre><code> border-width: 3px;</code></pre> +</div></div> +<div class="paragraph"><p>Another variable that <em>Subsurface</em> exports is <strong>print_options</strong>. This variable contains a single member:</p></div> +<div class="tableblock"> +<table rules="all" +width="100%" +frame="border" +cellspacing="0" cellpadding="4"> +<col width="50%" /> +<col width="50%" /> +<tbody> +<tr> +<td align="left" valign="top"><p class="table"><strong>Name</strong></p></td> +<td align="left" valign="top"><p class="table"><strong>Description</strong></p></td> +</tr> +<tr> +<td align="left" valign="top"><p class="table">grayscale</p></td> +<td align="left" valign="top"><p class="table">Use <em>CSS</em> filters to convert the page into grayscale (should be added to body style to enable printing grayscale prints)</p></td> +</tr> +</tbody> +</table> +</div> +<div class="literalblock"> +<div class="title">template.html</div> +<div class="content"> +<pre><code> body { + {{ print_options.grayscale }}; + }</code></pre> +</div></div> +<div class="literalblock"> +<div class="title">output.html</div> +<div class="content"> +<pre><code> body { + -webkit-filter: grayscale(100%); + }</code></pre> +</div></div> +</div> +<div class="sect2"> +<h3 id="_defined_css_selectors">19.3. Defined CSS selectors</h3> +<div class="paragraph"><p>As the dive profile is placed after rendering, <em>Subsurface</em> uses special <em>CSS</em> selectors to searche +in the HTML output. The <em>CSS</em> selectors in the following table should be added.</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>Selector</strong></p></td> +<td align="left" valign="top"><p class="table"><strong>Type</strong></p></td> +<td align="left" valign="top"><p class="table"><strong>Description</strong></p></td> +</tr> +<tr> +<td align="left" valign="top"><p class="table">dive_{{ dive.id }}</p></td> +<td align="left" valign="top"><p class="table">id</p></td> +<td align="left" valign="top"><p class="table">is used to fetch the relevant dive profile</p></td> +</tr> +<tr> +<td align="left" valign="top"><p class="table">diveProfile</p></td> +<td align="left" valign="top"><p class="table">class</p></td> +<td align="left" valign="top"><p class="table">each dive that will contain a dive profile should have this class selector in addition to the dive_{{ dive.id }} id selector</p></td> +</tr> +<tr> +<td align="left" valign="top"><p class="table">dontbreak</p></td> +<td align="left" valign="top"><p class="table">class</p></td> +<td align="left" valign="top"><p class="table">prevents the dive with this class from being divided into two pages. This can be used +in flow layout templates only (when data-numberofdives = 0)</p></td> +</tr> +</tbody> +</table> +</div> +<div class="admonitionblock"> +<table><tr> +<td class="icon"> +<img src="./images/icons/important.png" alt="Important" /> +</td> +<td class="content">Rendering dive profiles is not supported for flow layout templates (when data-numberofdives = 0).</td> +</tr></table> +</div> +</div> +<div class="sect2"> +<h3 id="_special_attributes">19.4. Special attributes</h3> +<div class="paragraph"><p>There are two ways of rendering- either rendering a specific number of dives in each page or make <em>Subsurface</em> try to +fit as many dives as possible into one page (<em>flow</em> rendering).</p></div> +<div class="paragraph"><p>The <strong>data-numberofdives</strong> data attribute is added to the body tag to set the rendering mode.</p></div> +<div class="ulist"><ul> +<li> +<p> +render 6 dives per page: +</p> +</li> +</ul></div> +<div class="literalblock"> +<div class="content"> +<pre><code> <body data-numberofdives = 6></code></pre> +</div></div> +<div class="ulist"><ul> +<li> +<p> +render as much dives as possible: +</p> +</li> +</ul></div> +<div class="literalblock"> +<div class="content"> +<pre><code> <body data-numberofdives = 0></code></pre> +</div></div> +<div class="admonitionblock"> +<table><tr> +<td class="icon"> +<img src="./images/icons/important.png" alt="Important" /> +</td> +<td class="content">All CSS units should be in relative lengths only, to support printing on any page size.</td> +</tr></table> +</div> +</div> +</div> +</div> +<div class="sect1"> +<h2 id="_appendix_f_faqs">20. APPENDIX F: FAQs.</h2> +<div class="sectionbody"> +<div class="sect2"> +<h3 id="S_APPENDIX_F">20.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’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 <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’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:</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">20.2. Some dive profiles have time discrepancies with the recorded samples from my dive computer…</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’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”.</p></div> +</div> +<div class="sect2"> +<h3 id="_some_dive_profiles_are_missing_from_the_download">20.3. Some dive profiles are missing from the download</h3> +<div class="paragraph" id="DC_HISTORY"><p><em>Question</em>: I cannot download all my dives, only the most recent ones, +even though my dive computer’s manual states that it records history of +e.g. 999 dives? +<em>Answer</em>: Dive history is different than the dive profiles on the log. +The history only keeps track of the total number of dives and total +amount of time spent below surface. The logs, on the other hand, store +the dive profile, but they have a limited amount of memory to do so. The +exact amount of dive profiles that can be stored on the device depends on +sample interval and duration of the dives. Once the memory is full the +oldest dives get overwritten with new dives. Thus we are only able to +download the last 13, 30 or 199 dives.</p></div> +<div class="paragraph"><p>If you have downloaded your dives to different dive logging software +before they were overwritten, there is a good chance that Subsurface can +import these. However, if the logs are only on your dive computer, they +cannot be salvaged after being overwritten by new dives.</p></div> +</div> +</div> +</div> +</div> +<div id="footnotes"><hr /></div> +<div id="footer"> +<div id="footer-text"> +Last updated 2015-12-16 06:35:54 PST +</div> +</div> +</body> +</html> diff --git a/Documentation/user-manual_es.html.git b/Documentation/user-manual_es.html.git index c1dac8401..0d555636c 100644 --- a/Documentation/user-manual_es.html.git +++ b/Documentation/user-manual_es.html.git @@ -1,6955 +1,6955 @@ -<!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.9" />
-<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; }
-
-
-@media screen {
- body {
- max-width: 50em; /* approximately 80 characters wide */
- margin-left: 16em;
- }
-
- #toc {
- position: fixed;
- top: 0;
- left: 0;
- bottom: 0;
- width: 13em;
- padding: 0.5em;
- padding-bottom: 1.5em;
- margin: 0;
- overflow: auto;
- border-right: 3px solid #f8f8f8;
- background-color: white;
- }
-
- #toc .toclevel1 {
- margin-top: 0.5em;
- }
-
- #toc .toclevel2 {
- margin-top: 0.25em;
- display: list-item;
- color: #aaaaaa;
- }
-
- #toctitle {
- margin-top: 0.5em;
- }
-}
-</style>
-<script type="text/javascript">
-/*<+'])');
- // 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">MANUAL DE USUARIO</span></p></div>
-<div class="paragraph"><p><strong>Autores</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>Versión 4.5, Septiembre 2015</em></span></p></div>
-<div class="paragraph"><p>Bienvenido como usuario de <em>Subsurface</em>, un avanzado programa de registro de
-inmersiones con extensa infraestructura para describir, organizar e
-interpretar buceos en apnea o con botella. <em>Subsurface</em> ofrece muchas ventajas
-sobre otras soluciones de software similares:</p></div>
-<div class="ulist"><ul>
-<li>
-<p>
-¿Necesitas una forma flexible de registrar inmersiones usando equipo
-recreativo, incluso aunque no uses ordenador?
-</p>
-</li>
-<li>
-<p>
-¿Utilizas dos ordenadores de buceo diferentes, cada uno con su software
-propietario para descargar los diarios de buceo? ¿Buceas con reciclador y con
-circuito abierto o equipo recreativo? ¿Usas un bottom-timer junto a un ordenador
-de buceo? <em>Subsurface</em> ofrece una interfaz estándar para descargar diarios de
-buceo desde todas estas piezas de equipo y para almacenarlos y analizarlos en un
-sistema unificado.
-</p>
-</li>
-<li>
-<p>
-¿Usas más de un sistema operativo? <em>Subsurface</em> es totalmente compatible con
-Mac, Linux y Windows permitiéndote acceder a tu registro de buceo de de la
-misma forma desde cualquiera de estos sistemas operativos.
-</p>
-</li>
-<li>
-<p>
-¿Utilizas Linux o Mac pero tu ordenador de buceo solo tiene software basado en
-Windows para descargar la información de buceo (p.e. Mares)? <em>Subsurface</em> te
-proporciona una manera de almacenar y analizar las inmersiones en otro sistema
-operativo.
-</p>
-</li>
-<li>
-<p>
-¿Necesitas un planificador de inmersiones gráfico que sea intuitivo, tenga
-en cuenta las inmersiones ya guardadas y se integre con ellas?
-</p>
-</li>
-<li>
-<p>
-¿Necesitas una forma de guardar tus divelogs en internet, que te permita
-visualizarlo desde cualquier parte, simplemente usando un navegador web?
-</p>
-</li>
-</ul></div>
-<div class="paragraph"><p>Hay binarios disponibles para PCs con Windows (XP o posterior), Macs basados en
-Intel (OS/X) y muchas distribuciones de Linux. <em>Subsurface</em> puede compilarse
-para muchas otras plataformas de hardware y entornos de software en los que
-estén disponibles Qt y libdivecomputer.</p></div>
-<div class="paragraph"><p>El ámbito de este documento es el uso del programa <em>Subsurface</em>. Para instalar
-el software, consulta la página Descargas en <a href="http://subsurface-divelog.org/">la
-web</a>. Por favor, comenta los problemas que tengas con este programa enviando un
-mail a <a href="mailto:subsurface@subsurface-divelog.org">nuestra lista de correo</a> e informa de
-fallos en <a href="http://trac.hohndel.org">nuestro bugtracker</a>. Para instrucciones acerca
-de como compilar el software y (en caso necesario) sus dependencias, por favor,
-consulta el archivo INSTALL incluido con el código fuente.</p></div>
-<div class="paragraph"><p><strong>Audiencia</strong>: Buceadores recreativos, Buceadores en apnea, Buceadores técnicos,
-Buceadores profesionales.</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="_utilizar_este_manual">1. Utilizar este manual</h2>
-<div class="sectionbody">
-<div class="paragraph"><p>Cuando se abre desde dentro de <em>Subsurface</em> este manual no tiene controles
-externos para paginar o seleccionar páginas anteriores, sin embargo se
-proporcionan dos utilidades:</p></div>
-<div class="ulist"><ul>
-<li>
-<p>
-La función <em>BUSCAR</em> se activa pulsando control-F o command-F en el teclado.
-Aparecerá una ventana de texto al pié de la ventana (ver imagen a continuación).
-Por ejemplo, si se tecleó la palabra "<em>lastre</em>" en la casilla de búsqueda, se
-buscará esta palabra por todo el manual. A la derecha de la casilla de texto
-hay dos flechas, una hacia arriba y otra hacia abajo. Pulsándolas se irá a la
-anterior o posterior aparición de la palabra buscada.
-</p>
-</li>
-</ul></div>
-<div class="imageblock" style="text-align:center;">
-<div class="content">
-<img src="images/usermanualfunctions.jpg" alt="User manual functions" />
-</div>
-</div>
-<div class="ulist"><ul>
-<li>
-<p>
-<em>LINK ANTERIOR/POSTERIOR</em>. Se puede navegar entre links (palabras resaltadas
-que permiten saltar a secciones específicas del manual) haciendo clic-derecho
-en el texto. Esto muestra un menú contextual que permite navegar a links
-del manual visitados anteriormente (ver imagen anterior). Por ejemplo, si se
-ha seleccionado un link del manual, la opción <em>Atrás</em> muestra el texto del
-último link seleccionado. A la inversa, la opción <em>Adelante</em> permite saltar
-al texto visitado antes de usar la opción <em>Atrás</em>. La opción <em>Recargar</em> hace
-que se recargue el manual completo en la ventana.
-</p>
-</li>
-</ul></div>
-</div>
-</div>
-<div class="sect1">
-<h2 id="S_UserSurvey">2. La Encuesta de Usuarios</h2>
-<div class="sectionbody">
-<div class="paragraph"><p>Para poder desarrollar <em>Subsurface</em> de una forma que sirva a sus usuarios de la
-mejor manera posible, es importante tener alguna información de los mismos. Al
-abrir <em>Subsurface</em> tras haberlo usado una semana más o menos,
-se desplegará una encuesta al usuario. Es completamente opcional y el usuario
-controla que datos se enviarán al equipo de desarrollo de <em>Subsurface</em>, si es
-que se envía alguno. Cualquier dato que el usuario decida enviar será
-extremadamente útil, y solo se usará para dirigir el desarrollo futuro y
-personalizar el software a medida de los usuarios de <em>Subsurface</em>. Si se
-completa la encuesta o se hace clic en la opción "No preguntarme de nuevo, será
-la última comunicación de esta naturaleza que se reciba. Sin embargo, si cambian
-nuestros hábitos o los de <em>Subsurface</em> y se desea volver a enviar la encuesta,
-se puede hacer lanzando <em>Subsurface</em> desde la línea de comandos con la opción
---survey.</p></div>
-</div>
-</div>
-<div class="sect1">
-<h2 id="S_StartUsing">3. Empezar a usar el programa</h2>
-<div class="sectionbody">
-<div class="paragraph"><p>La ventana <em>Subsurface</em> está, habitualmente, dividida en cuatro paneles con un
-<strong>Menú principal</strong> (Archivo Importar Registro Vista Ayuda) en la parte superior
-(en Windows y Linux) o en la parte superior de la pantalla (en Mac y Ubuntu
-Unity). Los cuatro paneles son:</p></div>
-<div class="olist arabic"><ol class="arabic">
-<li>
-<p>
-La <strong>Lista de inmersiones</strong> abajo a la izquierda. Contienen una lista de todos
-los buceos en tu registro. Puedes seleccionar y resaltar una inmersión de la
-lista haciendo clic sobre ella. En casi todos los casos también se pueden
-utilizar las teclas de cursor arriba/abajo para cambiar de inmersión. La Lista
-de Inmersiones es una herramienta importante para manipular un diario de
-inmersiones.
-</p>
-</li>
-<li>
-<p>
-El <strong>Mapa</strong> abajo a la derecha, muestra los lugares de buceo del usuario en un
-mapamundi y aparece centrado en el punto de la última inmersión seleccionada de
-la <strong>Lista de Inmersiones</strong>.
-</p>
-</li>
-<li>
-<p>
-La <strong>Información</strong> arriba a la izquierda, presentando
-información más detallada de la inmersión seleccionada en la <strong>Lista de
-inmersiones</strong>, incluyendo algunas estadísticas de la inmersión seleccionada o de
-todas las inmersiones resaltadas.
-</p>
-</li>
-<li>
-<p>
-El <strong>Perfil de la inmersión</strong> arriba a la derecha, muestra un perfil gráfico
-del buceo seleccionado en la <strong>Lista de inmersiones</strong>.
-</p>
-</li>
-</ol></div>
-<div class="paragraph"><p>Los divisores que hay entre los paneles pueden arrastrarse para modificar el
-tamaño de cualquiera de ellos. <em>Subsurface</em> recuerda la posición de los
-divisores, así, la próxima vez que se inicie <em>Subsurface</em> utiliza las posiciones
-utilizadas la vez anterior.</p></div>
-<div class="paragraph"><p>Si se selecciona una única inmersión en la <strong>Lista de inmersiones</strong>, se muestra su
-ubicación, información detallada y su perfil en sus paneles respectivos. Por
-otra parte, si uno selecciona más de un buceo, el último resaltado actuará como
-<em>inmersión seleccionada</em>, pero los datos resumidos de las <em>inmersiones
-resaltadas</em> se mostrarán en la pestaña <strong>Estadísticas</strong> del panel <strong>Información</strong>
-(máximas, mínimas y medias de profundidades, duraciones,
-temperaturas del agua, consumos de gases; el tiempo total y el número de
-inmersiones seleccionadas).</p></div>
-<div class="imageblock" id="S_ViewPanels" style="text-align:center;">
-<div class="content">
-<img src="images/main_window_f22.jpg" alt="La ventana principal" />
-</div>
-</div>
-<div class="paragraph"><p>El usuario puede elegir cual de los cuatro paneles se mostrará seleccionando la
-opción <strong>Vista</strong> en el menú principal, la cual le presentará varias opciones de
-visualización:</p></div>
-<div class="paragraph"><p><strong>Todo</strong>: muestra los cuatro paneles como en la captura de pantalla de arriba.</p></div>
-<div class="paragraph"><p><strong>Lista de inmersiones</strong>: Solo muestra la lista de buceos.</p></div>
-<div class="paragraph"><p><strong>Perfil</strong>: Muestra solo el perfil de inmersión del buceo seleccionado.</p></div>
-<div class="paragraph"><p><strong>Info</strong>: Solo muestra las notas sobre la última inmersión seleccionada y
-estadísticas para todas las resaltadas.</p></div>
-<div class="paragraph"><p><strong>Globo</strong>: Solo muestra el mapamundi centrado en la última inmersión seleccionada.</p></div>
-<div class="paragraph"><p>Como muchas otras funciones que pueden accederse desde el Menú Principal, estas
-opciones también pueden lanzarse utilizando atajos de teclado. Los atajos para
-un sistema en particular se muestran con un subrallado en las entradas del menú.
-Ya que los diferentes Sistemas Operativos y el lenguaje seleccionado por el
-usuario pueden hacer que <em>Subsurface</em> utilice diferentes atajos, no intentaremos
-listarlos en este manual.</p></div>
-<div class="paragraph"><p>Al iniciar el programa por primera vez no muestra ninguna información. Esto se
-debe a que el programa no tiene ninguna información disponible. En las secciones
-siguientes se describirán los procedimientos para crear un nuevo registro.</p></div>
-</div>
-</div>
-<div class="sect1">
-<h2 id="S_NewLogbook">4. Crear un nuevo diario</h2>
-<div class="sectionbody">
-<div class="paragraph"><p>Selecciona <em>Archivo → Nuevo Registro</em> en el menú principal. Todos los datos de
-buceo existentes se borran para poder añadir nueva información. Si hubieran
-datos no guardados en un diario abierto, al usuario se le preguntará si desea
-guardar el diario abierto antes de crear uno nuevo.</p></div>
-</div>
-</div>
-<div class="sect1">
-<h2 id="S_GetInformation">5. Guardar información en el diario de buceo</h2>
-<div class="sectionbody">
-<div class="paragraph"><p>Ahora que se ha creado un nuevo diario, es simple añadirle datos de buceo.
-<em>Subsurface</em> permite varias maneras distintas de añadir información a un diario,
-todas las cuales las veremos en detalle en las secciones
-siguientes.</p></div>
-<div class="paragraph"><p>1) Si el usuario tiene un diario en papel, una hoja de cálculo u otra
-forma de diario manual, se pueden añadir los datos de una de estas formas:</p></div>
-<div class="ulist"><ul>
-<li>
-<p>
-Introducir la información de buceo a mano. Esto es útil si el buceador no
-usa un ordenador de buceo y las inmersiones se guardaban en un diario
-escrito. Ver <a href="#S_EnterData">Introducir información de buceo a mano</a>.
-</p>
-</li>
-<li>
-<p>
-Importar datos de buceo que se han guardado bien como hoja de cálculo o
-bien como un archivo CSV. Ver el <a href="#S_Appendix_D">APÉNDICE D: Exportar una hoja de cáculo a formato CSV</a>
-y el texto <a href="#S_ImportingCSVDives">Importar buceos de archivos <em>CSV</em> creados a mano</a>.
-</p>
-</li>
-</ul></div>
-<div class="paragraph"><p>2) Si el usuario ya tiene inmersiones registradas con un ordenador de buceo,
-el perfil de profundidad del buceo y otra gran cantidad de información ya está
-disponible.Estas inmersiones pueden importarse de las siguientes formas:</p></div>
-<div class="ulist"><ul>
-<li>
-<p>
-El propio ordenador de buceo. Ver <a href="#S_ImportDiveComputer">Importar nueva información desde un ordenador de buceo</a>)
-</p>
-</li>
-<li>
-<p>
-Software propietario distribuido por los fabricantes de los ordenadores de
- buceo.
- Ver <a href="#S_ImportingAlienDiveLogs">Importar información de inmersiones de otras fuentes u otros formatos de datos</a>.
-</p>
-</li>
-</ul></div>
-<div class="sect2">
-<h3 id="S_EnterData">5.1. Introducir información de buceo a mano</h3>
-<div class="paragraph"><p>Este es habitualmente el caso para inmersiones sin ordenador de buceo. La unidad
-básica de información en <em>Subsurface</em> es una inmersión. La información más
-importante en un diario de inmersiones incluye, habitualmente, el tipo de
-inmersión, fecha, hora, duración, profundidad, los nombres de los compañeros de
-buceo o el dive master o el guía, y algunas anotaciones acerca de la inmersión.
-<em>Subsurface</em> puede conservar mucha más información por cada inmersión. Para
-añadir una inmersión a un registro de buceo, selecciona <em>Registro → Añadir
-Inmersión</em> en el menú principal. El programa muestra entonces tres paneles para
-introducir información: Dos pestañas en el panel <strong>Información</strong>
-(<strong>Notas</strong> y <strong>Equipo</strong>), así como el panel perfil que muestra un
-perfil gráfico de cada buceo. Estos paneles estan marcados respectivamente como
-<span class="red">A</span>, <span class="red">B</span> y <span class="red">C</span> en la figura de abajo. Ahora veremos cada una de
-las pestañas usadas para introducir la información.</p></div>
-<div class="imageblock" style="text-align:center;">
-<div class="content">
-<img src="images/AddDive1_f22.jpg" alt="FIGURA: Añadir inmersión" />
-</div>
-</div>
-<div class="paragraph"><p>Al editar un campo de los paneles <em>Notas</em> o <em>Equipo</em>, <em>Subsurface</em>
-entra en el modo de edición. Esto se indica con el mensaje en un recuadro azul
-en la parte de arriba del panel <strong>Notas</strong>. Este mensaje se
-muestra en todos los paneles dependientes de <em>Notas</em> mientras
-se esté en modo de edición.</p></div>
-<div class="imageblock" style="text-align:center;">
-<div class="content">
-<img src="images/BlueEditBar_f22.jpg" alt="Blue edit bar" />
-</div>
-</div>
-<div class="paragraph"><p>El botón <em>Aplicar cambios</em> solo debería utilizarse cuando todas las partes de la
-inmersión hayan sido rellenadas. Cuando se introduzcan inmersiones a mano,
-deberían haberse completado las pestañas <em>Información</em>, <em>Equipo</em> y <em>Perfil</em>
-antes de guardar la información. Al seleccionar el botón <em>Aplicar cambios</em>, se guarda
-en memoria una copia local de la información. Al salir de <em>Subsurface</em>, el
-programa preguntará de nuevo, esta vez si se guarda el diario completo en el
-disco o no.</p></div>
-<div class="sect3">
-<h4 id="S_CreateProfile">5.1.1. Crear un perfil de inmersión</h4>
-<div class="paragraph"><p>EL <strong>Perfil de la Inmersión</strong> (una representación gráfica de la profundidad de
-buceo en función del tiempo) se muestra en el panel de arriba a la derecha de la
-ventana de <em>Subsurface</em> . Cuando se añade manualmente una inmersión a un diario,
-<em>Subsurface</em> presenta un perfil por defecto que necesita modificarse para
-representar mejor el buceo que se está describiendo.</p></div>
-<div class="imageblock" style="text-align:center;">
-<div class="content">
-<img src="images/DiveProfile1_f20.jpg" alt="FIGURA: Perfil de inmersión inicial" />
-</div>
-</div>
-<div class="paragraph"><p><em>Modificar el perfil de la inmersión</em>: Cuando se mueve el cursor por el perfil,
-su posición se indica por dos líneas de colores (roja y verde), como se muestra
-a continuación. La profundidad y el tiempo se indican en el cajetín negro de
-información. Las
-unidades (métricas/imperiales) de los ejes vienen determinadas por los ajustes
-de las Preferencias. El perfil de la inmersión comprende varios segmentos
-definidos por puntos de referencia (puntos en blanco en el perfil, como los que
-se muestran arriba). La profundidad por defecto es de 15m.
-Si la profundidad de la inmersión fue de 20m, el usuario tiene que arrastrar los
-puntos de referencia adecuados hacia abajo hasta que representen los 20m. Para
-añadir un punto hay que hacer doble clic en cualquier segmento. Para borrar un
-punto de referencia, hacer clic-derecho sobre él y seleccionar "Borrar este
-punto" del menú contextual. También se necesitará arrastrar los puntos para
-representar una duración adecuada del buceo. A continuación hay un perfil de
-inmersión que representa un buceo a 20m durante 30 minutos, seguido de una
-parada de seguridad de 5 minutos a 5m.</p></div>
-<div class="imageblock" style="text-align:center;">
-<div class="content">
-<img src="images/DiveProfile2_f20.jpg" alt="FIGURA: Perfil de buceo editado" />
-</div>
-</div>
-<div class="paragraph"><p><em>Especificar la composición del gas</em>: La composición del gas usado se indica
-claramente a lo largo de los segmentos del perfil. Esta resulta, por defecto, en
-la primera mezcla de gases especificada en la pestaña <strong>Equipo</strong>, que era aire en
-el caso del perfil ilustrado arriba. Las mezclas de gases de los segmentos del
-perfil pueden editarse, Esto se hace clicando en la descripción del gas para un
-punto de referencia concreto y eligiendo la mezcla apropiada del menú
-contextual. Cambiar el gas de un punto de referencia afecta al gas mostrado a la
-izquierda <em>a la izquierda</em> del punto. Nótese que únicamente los gases definidos
-en la pestaña <strong>Equipo</strong> aparecen en el menú contextual (ver imagen a continuación).</p></div>
-<div class="imageblock" style="text-align:center;">
-<div class="content">
-<img src="images/DiveProfile3_f20.jpg" alt="FIGURA: Menú contextual de la composición del gas" />
-</div>
-</div>
-<div class="paragraph"><p>Habiendo sido definido el perfil, se deben añadir más detalles para tener un
-registro más completo del buceo. Para hacer esto, deberían utilizarse las
-pestañas <strong>Notas</strong> y <strong>Equipo</strong> arrriba a la izquierda en la ventana de <em>Subsurface</em>.
-Haz clic en <a href="#S_Notes_dc"><strong>este enlace</strong></a> para ver instrucciones acerca del
-uso de estas pestañas.</p></div>
-</div>
-</div>
-<div class="sect2">
-<h3 id="S_ImportDiveComputer">5.2. Importar nueva información desde un ordenador de buceo</h3>
-<div class="sect3">
-<h4 id="_conectar_e_importar_datos_desde_un_ordenador_de_buceo">5.2.1. Conectar e importar datos desde un ordenador de buceo.</h4>
-<div class="paragraph"><p>El uso de ordenadores de buceo permite recoger una gran cantidad de información
-de cada inmersión, por ejemplo un registro detallado de la profundidad,
-duración, ratios de ascenso/descenso y de presiones parciales de los gases.
-<em>Subsurface</em> puede capturar esta información y presentarla como parte de la
-información de la inmersión. <em>Subsurface</em> puede obtener información de un amplio
-abanico de ordenadores de buceo, la última lista de los cuales puede encontrarse
-en:
-<a href="http://subsurface-divelog.org/documentation/supported-dive-computers/">Ordenadores de buceo soportados.</a></p></div>
-<div class="admonitionblock">
-<table><tr>
-<td class="icon">
-<img src="images/icons/warning2.png" alt="Warning" />
-</td>
-<td class="content">Algunos ordenadores de buceo consumen más energía cuando están en modo
-comunicación-PC. <strong>Esto puede descargar la batería del ordenador de buceo</strong>. Así
-pues, recomendamos que el usuario verifique si su ordenador está recargando
-mientras está conectado al puerto USB de un PC. Por ejemplo, varios ordenadores
-Suunto y Mares no recargan a través de de la conexión USB. Los usuarios deberían
-consultar el manual de su ordenador de buceo si no están seguros de si recargará
-o descargará sus baterías mientras está conectado al puerto USB.</td>
-</tr></table>
-</div>
-<div class="paragraph"><p>Para importar información desde un ordenador de buceo al PC con <em>Subsurface</em> es
-necesario que ambas piezas de equipo estén comunicadas. Esto requiere ajustar el
-puerto de comunicaciones (o el punto de montaje) del PC con <em>Subsurface</em> que
-conecta con el ordenador de buceo. Para poder ajustar esta comunicación, es
-necesario encontrar la información adecuada para indicar a <em>Subsurface</em> donde y
-como importar la información. El
-<a href="#_apendice_a_informacion_especifica_del_sistema_operativo_para_importar_inmersiones_desde_un_ordenador_de_buceo">Apéndice A</a>
-proporciona información técnica para ayudarte a conseguir esto en diferentes
-sistemas operativos y el
-<a href="#_appendix_b_dive_computer_specific_information_for_importing_dive_information">Apéndice B</a>
-contiene información específica de ordenadores de buceo.</p></div>
-<div class="paragraph"><p>Ahora es el momento de conectar el ordenador de buceo al PC del usuario, para
-lo que hay que seguir estos pasos:</p></div>
-<div class="olist arabic"><ol class="arabic">
-<li>
-<p>
-Conectar el cable de conexión a un puerto USB libre (o activar la conexión
- infrarroja o bluetooth como describiremos más adelante en este manual).
-</p>
-</li>
-<li>
-<p>
-Poner el ordenador de buceo en modo de comunicación con PC. Consulta el
- manual de tu ordenador de buceo en concreto.
-</p>
-</li>
-<li>
-<p>
-En <em>Subsurface</em>, desde el Menú principal, seleccionar Importar → Importar del
- ordenador de buceo. Aparecerá el diálogo <strong>A</strong> en la figura a continuación:
-</p>
-</li>
-</ol></div>
-<div class="imageblock" style="text-align:center;">
-<div class="content">
-<img src="images/DC_import_f20.jpg" alt="FIGURA: Diálogo de descarga 1" />
-</div>
-</div>
-<div class="paragraph"><p>Los ordenadores de buceo tienden a mantener un cierto número de inmersiones en
-su memoria, incluso cuando estas inmersiones ya han sido importadas a
-<em>Subsurface</em>. Por este motivo <em>Subsurface</em> solo importa buceos que no han sido
-descargados previamente, si el ordenador de buceo lo permite. Esto hace que el
-proceso de descarga sea más rápido en la mayoría de ordenadores de buceo y
-ahorra batería en el ordenador (por lo menos en aquellos que no cargan mientras
-están conectados vía USB).</p></div>
-<div class="ulist"><ul>
-<li>
-<p>
-El diálogo tiene dos listas desplegables, <strong>Vendedor</strong> y <strong>Ordenador de buceo</strong>.
- En la lista desplegable <strong>Vendedor</strong> se selecciona la marca del ordenador, p.e.
- Suunto, Oceanic, Uwatec, Mares. En el desplegable <strong>Ordenador de buceo</strong>, se
- selecciona el modelo del ordenador, p.e. D4 (Suunto), Veo200 (Oceanic) o Puck
- (Mares).
-</p>
-</li>
-<li>
-<p>
-El desplegable <strong>Dispositivo o punto de montaje</strong> contiene el nombre del puerto
- USB o Bluetooth que <em>Subsurface</em> necesita conocer para comunicarse con el
- ordenador de buceo. Debe seleccionarse el nombre de puerto apropiado. Consultar
- el
- <a href="#_apendice_a_informacion_especifica_del_sistema_operativo_para_importar_inmersiones_desde_un_ordenador_de_buceo">Apéndice A</a>
- y <a href="#_appendix_b_dive_computer_specific_information_for_importing_dive_information">Apéndice B</a>
- para detalles técnicos de como encontrar la información apropiada sobre
- puertos, para un ordenador en concreto y, en algunos casos, como hacer los
- ajustes correctos al Sistema Operativo del ordenador que ejecuta <em>Subsurface</em>.
-</p>
-</li>
-<li>
-<p>
-Si todas las inmersiones del ordenador de buceo han de descargarse, hay que
- seleccionar la casilla Forzar descarga de todas las inmersiones. Normalmente
- <em>Subsurface</em> solo descarga las inmersiones posteriores a la fecha/hora de la
- última inmersión del panel <strong>Lista de inmersiones</strong>. Si una o más de sus
- inmersiones en <em>Subsurface</em> se han borrado accidentalmente o si hay buceos más
- antiguos que todavía necesitan descargarse del ordenador de buceo, debe
- activarse esta casilla. Algunos ordenadores (p.e. Mares Puck) no facilitan una
- lista de contenido antes de la descarga para poder seleccionar solo las
- inmersiones nuevas. En consecuencia, para estos ordenadores de buceo, se
- descarga la totalidad de los buceos.
-</p>
-</li>
-<li>
-<p>
-Si se ha seleccionado la casilla <em>Preferir siempre inmersiones descargadas</em> y,
- durante la descarga, existen inmersiones con idénticas fechas/horas en el
- ordenador de buceo y en el panel <strong>Lista de inmersiones</strong> de <em>Subsurface</em> , se
- sobrescribirá la inmersión de <em>Subsurface</em> con los datos del ordenador de buceo.
-</p>
-</li>
-<li>
-<p>
-<strong>NO</strong> seleccionar las casillas etiquetadas <em>Guardar registro de
- libdivecomputer</em> y <em>Guardar volcado de libdivecomputer</em>. Estas opciones se
- utilizan como herramientas diagnósticas cuando se experimentan problemas con las
- descargas (ver a continuación).
-</p>
-</li>
-<li>
-<p>
-Ahora pulsar el botón <em>Descargar</em>.
- Con la comunicación establecida puede verse como se transfiere la información
- del ordenador de buceo. Dependiendo del ordenador de buceo y/o el número de
- inmersiones guardadas, esto podría llevar algún tiempo. El usuario debe ser
- paciente. El diálogo <em>Descarga</em> muestra una barra de progreso en la parte
- inferior de la ventana (en algunos ordenadores de buceo la información del
- progreso puede ser imprecisa al no poder determinarse cuantos datos había hasta
- haberse descargado). Tras una descarga correcta, aparecerá el diálogo <strong>B</strong> de
- la imagen anterior. Las inmersiones descargadas aparecen en una tabla en el
- lado derecho del diálogo. Cada inmersión se sitúa en una fila en la que se
- muestra la fecha, la duración y la profundidad. Junto a cada buceo hay una
- casilla seleccionable. Marca todas las inmersiones que deban trasladarse a la
- <em>Lista de Inmersiones</em>. Luego pulsa el botón <em>Aceptar</em> en la parte de abajo
- del diálogo. En el caso de la imagen anterior, las últimas seis inmersiones
- han sido seleccionadas y se transferirán a la lista. Todas las inmersiones
- importadas aparecen en la <strong>Lista de inmersiones</strong>
- ordenadas por fecha y hora. Es el momento de desconectar y apagar el ordenador
- de buceo para ahorrar batería.
-</p>
-</li>
-<li>
-<p>
-Si hubiera algún problema de comunicación con el ordenador de buceo, se
- mostraría un mensaje de error similar a este: "No puedo abrir /dev/ttyUSB0 Mares
- (Puck Pro)". Ver el texto en la figura a continuación.
-</p>
-</li>
-</ul></div>
-<div class="sidebarblock">
-<div class="content">
-<div class="paragraph"><p><strong>PROBLEMAS EN LA DESCARGA DE DATOS DESDE UN ORDENADOR DE BUCEO</strong></p></div>
-<div class="admonitionblock">
-<table><tr>
-<td class="icon">
-<img src="images/icons/important.png" alt="Important" />
-</td>
-<td class="content">Comprueba lo siguiente:</td>
-</tr></table>
-</div>
-<div class="ulist"><ul>
-<li>
-<p>
-¿ Está el ordenador de buceo todavía en modo "PC-Communication" o "Upload" ?
-</p>
-</li>
-<li>
-<p>
-¿ Está completamente cargada la batería del ordenador de buceo ? Si nó debe
- cargarse o ser reemplazada.
-</p>
-</li>
-<li>
-<p>
-¿ Falla el cable ? ¿ Funciona bien el cable usando otro software ? ¿ Ha
- funcionado antes o es la primera vez que se usa ? ¿ Están limpios los contactos
- entre el cable y el ordenador de buceo ?
-</p>
-</li>
-<li>
-<p>
-Consultar el
- <a href="#_apendice_a_informacion_especifica_del_sistema_operativo_para_importar_inmersiones_desde_un_ordenador_de_buceo">Apéndice A</a>
- y asegurarse de que se especificó el punto de montaje correcto.
-</p>
-</li>
-<li>
-<p>
-En sistemas operativos tipo unix, comprobar que el usuario tiene permisos de
- escritura en el puerto USB. Si nó, consultar el
- <a href="#_apendice_a_informacion_especifica_del_sistema_operativo_para_importar_inmersiones_desde_un_ordenador_de_buceo">Apéndice A</a>.
-</p>
-</li>
-</ul></div>
-<div class="paragraph"><p>Si el PC con <em>Subsurface</em> no reconoce el adaptador USB mostrando un nombre de
-dispositivo correcto, existe la posibilidad de que fallen el cable o el
-adaptador estén fallando. Un cable que falla es la causa más común de problemas
-de comunicación entre el PC y el ordenador de buceo. También existe la
-posibilidad de que el PC con <em>Subsurface</em> no pueda interpretar los datos. Habría
-que efectuar una descarga con propósito diagnóstico con las sigientes casillas
-seleccionadas en el dialogo de descarga:</p></div>
-<div class="literalblock">
-<div class="content">
-<pre><code>Guardar registro de libdivecomputer
-Guardar volcado de libdivecomputer</code></pre>
-</div></div>
-<div class="paragraph"><p><strong>Importante</strong>: Estas casillas solo se utilizan si aparecen problemas durante el
-proceso de descarga; en condiciones normales no deberían estar seleccionadas. Al
-seleccionar cada una de estas opciones, se le solicita al usuario una carpeta en
-la que guardar los ficheros de información. Por defecto esta carpeta es la misma
-en la que se guarda el archivo del diario de <em>Subsurface</em>.</p></div>
-<div class="paragraph"><p><strong>Importante</strong>: Al terminar de descargar con estas casillas seleccionadas no se
-muestran buceos en la Lista de inmersiones pero se cran dos ficheros en la
-carpeta seleccionada arriba:</p></div>
-<div class="literalblock">
-<div class="content">
-<pre><code>_Subsurface_.log
-_Subsurface_.bin</code></pre>
-</div></div>
-<div class="paragraph"><p>Estos ficheros deberían ser remitidos a la lista de correo de <em>Subsurface</em>:
-<em>subsurface</em>@hohndel.org_ solicitando que los ficheros sean analizados,
-facilitando el fabricante y el modelo de tu ordenador de buceo y alguna
-información sobre las inmersiones grabadas en el ordenador de buceo.</p></div>
-</div></div>
-</div>
-<div class="sect3">
-<h4 id="S_Bluetooth">5.2.2. Conectar <em>Subsurface</em> con ordenadores de buceo con Bluetooth</h4>
-<div class="paragraph"><p>Bluetooth se está convirtiendo en una forma cada vez más común de comunicación
-entre los ordenadores de buceo y <em>Subsurface</em>. Por ejemplo, este mecanismo se
-usa en el Shearwater Petrel Mk2 o el OSTC3. <em>Subsurface</em> proporciona un
-interfaz Bluetooth muy independiente del sistema operativo utilizado. Ajustar
-<em>Susburface</em> para comunicación con Bluetooth requiere cuatro pasos:</p></div>
-<div class="ulist"><ul>
-<li>
-<p>
-Asegurarse de que Bluetooth está activado en el ordenador que ejecuta
- <em>Subsurface</em>.
-</p>
-</li>
-<li>
-<p>
-Asegurarse de que <em>Subsurface</em> localiza el adaptador Bluetooth del
- ordenador.
-</p>
-</li>
-<li>
-<p>
-Asegurarse de que el Bluetooth del ordenador de buceo está está en modo
- descarga y es visible.
-</p>
-</li>
-<li>
-<p>
-Asegurarse de que <em>Subsurface</em> está emparejado con el ordenador de buceo.
-</p>
-</li>
-</ul></div>
-<div class="paragraph"><p>Abre el diálogo de descarga seleccionando <em>Import → Importar del ordenador
-de buceo</em> desde el <strong>Menú Principal</strong>. Si se selecciona la casilla etiquetada
-<em>"Elegir modo de descarga Bluetooth"</em> , aparecerá el diálogo que se muestra
-a continuación.</p></div>
-</div>
-<div class="sect3">
-<h4 id="_en_linux_o_macos">5.2.3. En Linux o MacOS</h4>
-<div class="imageblock" style="text-align:center;">
-<div class="content">
-<img src="images/DC_import_Bluetooth.jpg" alt="FIGURA: Descarga Bluetooth" />
-</div>
-</div>
-<div class="paragraph"><p>En plataformas <em>Linux</em> o <em>MacOS</em> el nombre del ordenador con <em>Subsurface</em>
-se muestran en el lado derecho. En el lado izquierdo, si el ordenador tiene
-conectado más de un dispositivo Bluetooth, se puede seleccionar cual se desea
-conectar a <em>Subsurface</em>.
-Bajo la dirección se muestra el estado del adaptador (activado/desactivado) y
-puede cambiarse pulsando el botón <em>Activar/desactivar</em>.</p></div>
-<div class="paragraph"><p>Si no se muestra la dirección Bluetooth, es que <em>Subsurface</em> no localiza el
-dispositivo Bluetooth del ordenador en que se ejecuta. Asegúrate de que el
-driver Bluetooth está instalado correctamente y comprueba que se puede usar
-con otras utilidades Bluetooth como <em>bluetoothctl</em>, bluemoon u otras. Con esto
-se completaría los primeros dos pasos indicados anteriormente.</p></div>
-<div class="paragraph"><p>Asegúrate de que el ordenador de buceo es visible y se encuentra en modo
-descarga (Nota del traductor: es posible que este modo aparezca en inglés como
-"Upload" o su traducción literal "Subida"). Consulta el manual del ordenador
-de buceo para completar este paso, que sería el tercero de la lista anterior.</p></div>
-<div class="paragraph"><p>Selecciona el botón <em>Buscar</em> en la parte de abajo a la izquierda del diálogo
-anterior, Tras buscar unos momentos, el ordenador de buceo debería aparecer en
-la relación (tal vez entre otros dispositivos Bluetooth) de la lista de la
-izquierda del diálogo (ver imagen anterior). Si no es así, pulsa el botón,
-<em>Limpiar</em> y efectúa una nueva búsqueda utilizando el botón <em>Buscar</em>. Si
-<em>Subsurface</em> "ve" el ordenador de buceo, la línea de la lista contendrá el
-nombre del dispositivo, su dirección y su estado de emparejamiento. Si el
-dispositivo no está emparejado y tiene un fondo rojo, se puede abrir un menú
-contextual seleccionando su línea y pulsando clic-derecho.
-Pulsa el botón <em>Emparejar</em> y espera a que se complete la tarea. Si este
-ordenador de buceo se está emparejando con <em>Subsurface</em> por primera vez, es
-posible que se requiera una clave o número PIN. La clave más utilizada suele
-ser 0000, y funciona para el Shearwater Petrel. En caso necesario, consulta el
-manual de usuario del ordenador de buceo.</p></div>
-<div class="sidebarblock">
-<div class="content">
-<div class="admonitionblock">
-<table><tr>
-<td class="icon">
-<img src="images/icons/important.png" alt="Important" />
-</td>
-<td class="content">Actualmente <em>Subsurface</em> no soporta emparejamiento con ordenadores de buceo que
-requieran un PIN definido. Para poder emparejar los dispositivos en este caso,
-habría que utiliza alguna otra utilidad del SO.</td>
-</tr></table>
-</div>
-<div class="paragraph"><p>Una forma de hacerlo es usar <code>bluetoothctl</code>:</p></div>
-<div class="literalblock">
-<div class="content">
-<pre><code>$ bluetoothctl
-[bluetooth]# agent KeyboardOnly
-Agent registered
-[bluetooth]# default-agent
-Default agent request successful
-[bluetooth]# pair 00:80:25:49:6C:E3
-Attempting to pair with 00:80:25:49:6C:E3
-[CHG] Device 00:80:25:49:6C:E3 Connected: yes
-Request PIN code
-[agent] Enter PIN code: 0000</code></pre>
-</div></div>
-</div></div>
-<div class="paragraph"><p>Después de que los dispositivos se hayan emparejado, se puede pulsar el botón
-<em>Guardar</em>. Esto cerrará el diálogo. Ahora pulsa <em>Descargar</em> en el diálogo
-<em>Descargar del ordenador de buceo</em> que debería permanecer abierto. Los buceos
-descargado se mostrarán en el lado derecho de la ventana de descarga.</p></div>
-</div>
-<div class="sect3">
-<h4 id="_en_windows">5.2.4. En Windows</h4>
-<div class="imageblock" style="text-align:center;">
-<div class="content">
-<img src="images/DC_import_Bluetooth_Windows.png" alt="FIGURE: Descarga Bluetooth en Windows" />
-</div>
-</div>
-<div class="paragraph"><p>En plataformas Windows no está disponible la <em>sección de detalles de los
-dispositivos Bluetooth</em>. Para iniciar correctamente un escaneo pulsando el
-botón <em>Buscar</em> , comprueba que el dispositivo <em>Bluetooth</em> del ordenador con
-<em>Subsurface</em> está activado seleccionando el ordenador de la lista de
-dispositivos Bluetooth disponibles (ver imagen anterior). Si se accede por
-primera vez al ordenador de buceo con <em>Subsurface</em>, es posible que se
-requiera una clave/PIN. Introduce el recomendado en el manual de ordenador
-de buceo. A menudo es correcto un pin 0000.</p></div>
-<div class="paragraph"><p>El paso del emparejado se efectúa de forma
-automática durante el proceso de descarga. Si los dispositivos no se han
-emparejado nunca, el sistema te pedirá permiso y mostrará un mensaje en el
-lado derecho de la pantalla: <em>Añadir un dispositivo. Pulsa para configurar tu
-dispositivo DC</em>. Siempre debes autorizar el emparejado. Tras haber seleccionado
-uno de los dispositivos encontrados, pulsa <em>Guardar</em>. Finalmente, selecciona
-el botón <em>Descargar</em> del diálogo de descargas y espera a que se complete el
-proceso.</p></div>
-<div class="admonitionblock">
-<table><tr>
-<td class="icon">
-<img src="images/icons/important.png" alt="Important" />
-</td>
-<td class="content">Hay que tener en cuenta que, actualmente, <em>Subsurface</em> solo funciona con
-adaptadores Bluetooth locales que usen Microsoft Bluetooth Stack. Si el
-dispositivo local usa drivers <em>Widcomm</em>, <em>Stonestreet One Bluetopia Bluetooth</em> o
-<em>BlueSolei</em> no funcionará, sin embargo, los receptores de estos fabricantes
-que usen el Microsoft Bluetooth Stack sí funcionarán.</td>
-</tr></table>
-</div>
-<div class="paragraph"><p>Un mensaje de aviso en la parte inferior izquierda de la <em>Selección de
-dispositivos Bluetooth remotos</em> muestra detalles del estado actual del agente
-Bluetooth.
-Si se desea seleccionar otro ordenador de buceo utilizando la <em>Selección de
-dispositivo Bluetooth remoto</em> pulsa el botón con tres puntos de <em>Elegir modo
-de descarga _Bluetooth</em>.</p></div>
-<div class="admonitionblock">
-<table><tr>
-<td class="icon">
-<img src="images/icons/important.png" alt="Important" />
-</td>
-<td class="content"><strong>EN CASO DE PROBLEMAS</strong>: Si el adaptador Bluetooth del ordenador con <em>Subsurface</em>
-se cuelga y el proceso de descarga falla repetidamente, <em>desempareja</em> los
-dispositivos y repite los pasos indicados anteriormente. Si a pesar de ello
-se sigue sin tener éxito, el <a href="#S_HowFindBluetoothDeviceName"><em>Apéndice A</em></a>
-contiene información para ajustar manualmente e inspeccionar la conexión
-Bluetooth con <em>Subsurface</em>.</td>
-</tr></table>
-</div>
-</div>
-<div class="sect3">
-<h4 id="S_DeviceNames">5.2.5. Cambiar el nombre de un ordenador de buceo</h4>
-<div class="paragraph"><p>Es posible que sea necesario distinguir entre diferentes ordenadores de buceo
-usados para cargar inmersiones en <em>Subsurface</em>. Por ejemplo, si el ordenador del
-compañero es de la misma marca y modelo que el del usuario y los diarios de
-ambos se cargan en el mismo PC con <em>Subsurface</em>, puede que se quiera llamar a
-uno "Suunto D4 de Alice" y al otro "Suunto D4 de Bob". Por otro lado, puede que
-un buceador técnico utilice dos o más ordenadores de buceo del mismo modelo,
-este caso podría ser prudente llamar a uno "Suunto D4 (1)" y al otro "Suunto D4
-(2)".</p></div>
-<div class="paragraph"><p>Esto se hace fácilmente en <em>Subsurface</em>. Desde el <strong>Menú Principal</strong>, se
-selecciona <em>Registro → Editar nombres de dispositivos</em>. Se abrirá un diálogo en
-el que se indica el modelo actual, su ID y un nombre para el ordenador de buceo
-utilizado para cargar inmersiones. Se edita el campo del nombre al que se quiera
-asignar al ordenador. Tras guardar el nombre, en el perfil de la inmersión
-aparecerá el nombre que se haya asignado a ese dispositivo en particular en
-lugar del modelo, permitiendo una identificación de dispositivos más fácil.</p></div>
-</div>
-<div class="sect3">
-<h4 id="S_EditDiveInfo">5.2.6. Actualizar la información de buceo importada del ordenador.</h4>
-<div class="paragraph"><p>Con los buceos descargados en la <strong>Lista de inmersiones</strong>, la información del
-ordenador no está completa y es necesario añadir más detalles para tener un
-registro más detallado de las inmersiones. Para ello se usan las pestañas
-<strong>Notas</strong> y <strong>Equipo</strong> arriba a la izquierda de la ventana de
-<em>Subsurface</em>.</p></div>
-<div class="sect4">
-<h5 id="S_Notes_dc">Notas</h5>
-<div class="paragraph"><p>El usuario debe añadir información a mano para poder tener un registro más
-completo. La información a continuación es casi idéntica para inmersiones
-creadas manualmente y para inmersiones descargadas del ordenador.</p></div>
-<div class="paragraph"><p>En algunos casos, se debe proporcionar la fecha y la hora de la inmersión, por
-ejemplo al crear un buceo a mano o cuando un ordenador no facilita la fecha y
-la hora de la inmersión (habitualmente la fecha y hora del buceo, la mezcla de gases
-y, la temperatura del agua se obtienen del ordenador de buceo). Si se cambia o
-edita de alguna manera el contenido de esta
-pestaña, el mensaje de la barra azul arriba del panel indicará que se está
-editando el buceo. Si se pulsa en la pestaña <strong>Notas</strong>, se
-visualizan los siguientes campos (imagen a la izquierda, a continuación:</p></div>
-<div class="imageblock" style="text-align:center;">
-<div class="content">
-<img src="images/AddDive3_f22.jpg" alt="FIGURA: La pestaña Notas" />
-</div>
-</div>
-<div class="paragraph"><p>La imagen derecha anterior muestra una pestaña <strong>Notas</strong> llena de información.
-El campo <strong>Hora</strong> refleja la fecha y la hora de la inmersión. Clicando la fecha se
-muestra un calendario desde el que seleccionar la fecha correcta. Pulsa ESC para
-salir del calendario. La hora y los minutos también pueden editarse clicando en
-cada uno de ellos y sobreescribiendo la información mostrada.</p></div>
-<div class="paragraph"><p><strong>Temperaturas Aire/Agua</strong>: Las temperaturas de aire y agua durante la inmersión
-se muestran en estos campos a la derecha de la Hora de Inicio. Muchos
-ordenadores de buceo suministran información sobre la temperatura del agua y
-este campo puede que ya contenga información obtenida del mismo. Si no se
-proporciona la temperatura del aire, puede utilizarse la primera lectura del
-ordenador. En general, suele estar bastante cerca de la temperatura real del
-aire ya que el cambio en la lectura del sensor de temperatura es bastante lento
-para seguir los cambios en el entorno. Si fuera necesario, no hay que teclear
-las unidades de temperatura: <em>Subsurface</em> las suministra automáticamente de
-acuerdo con las <em>Preferencias</em> (métricas o imperiales).</p></div>
-<div class="paragraph"><p><strong>Ubicación</strong>:</p></div>
-<div class="admonitionblock">
-<table><tr>
-<td class="icon">
-<img src="images/icons/warning2.png" alt="Warning" />
-</td>
-<td class="content">Las localizaciones de buceo se gestionan como una parte <strong>separada</strong> del divelog.
-La información de buceo de las pestañas <strong>Notas</strong> y <strong>Equipo</strong> no se puede editar
-al mismo tiempo que la información de los puntos de buceo. Guarda toda la otra
-información (p.e. divemaster, compañero, equipo, etc) seleccionando <em>Aplicar
-cambios</em> en la pestaña <strong>Notas</strong> antes de editar la información del punto de
-buceo. Introduce, solo entonces, el nombre del lugar de la inmersión en el
-campo de texto etiquetado <em>Ubicación</em> de la pestaña <strong>Notas</strong>.</td>
-</tr></table>
-</div>
-<div class="paragraph"><p>Teclea el nombre del punto de buceo, p.e. "Tihany, Lake Balaton, Hungary".
-Si se han efectuado varias inmersiones en el mismo lugar, la información del
-primer buceo se reutiliza.
-La información existente puede editarse en cualquier momento seleccionando
-(en el panel <strong>Lista de Inmersiones</strong>) un buceo efectuado en el lugar deseado y
-abriendo la información de la ubicación haciendo clic en el botón con el globo
-a la derecha del nombre del lugar (ver la imagen de arriba a la derecha).
-Cuando se introduce el nombre de una ubicación, el auto completado de nombres
-hace que sea fácil seleccionar un punto de buceo que ya exista en el divelog
-(p.e. al teclear el nombre de un punto de buceo, aparece una lista desplegable
- mostrando todos los lugares con nombres similares). Si el lugar se ha utilizado
-antes, pulsa en el nombre preexistente.</p></div>
-<div class="paragraph"><p>Los nombres de la lista desplegable contienen, bien un símbolo de un globo (que
-indica que existe en la base de datos de <em>Subsurface</em>), bien un símbolo <strong>+</strong> (que
-indicaría un nombre que puede ser añadido a la base de datos).
-Así pues, si este punto de buceo no ha sido usado con anterioridad, aparece un
-mensaje como el siguiente (imagen <strong>A</strong> a continuación):</p></div>
-<div class="imageblock" style="text-align:center;">
-<div class="content">
-<img src="images/Locations1_f22.jpg" alt="FIGURA: Panel de descripción de ubicación" />
-</div>
-</div>
-<div class="paragraph"><p>Haz doble clic en el icono + en el lado derecho. Aparecerá un panel para
-introducir las coordenadas y otra información sobre el lugar que pueda ser
-importante (imagen <strong>B</strong>, anterior). Lo más importante son las coordenadas del
-punto. Hay tres formas de especificarlas:</p></div>
-<div class="olist loweralpha"><ol class="loweralpha">
-<li>
-<p>
-El usuario puede encontrar las coordenadas en el mapamundi situado abajo a la
- derecha en la ventana de <em>Subsurface</em>. El mapa muestra una barra marrón indicando
- "Sin datos de ubicación - Mueve el mapa y haz doble clic para fijar la posición
- del buceo". Al hacer doble clic en el lugar apropiado, la barra marrón desaparece
- y las coordenadas quedan grabadas
-</p>
-</li>
-<li>
-<p>
-Se pueden obtener las coordenadas desde la app <em>Subsurface</em> Companion si se
- dispone de un dispositivo android o iPhone con GPS y se guardaron las
- coordenadas del punto de buceo usando ese dispositivo.
- <a href="#S_Companion">Pulsa aquí para más información</a>
-</p>
-</li>
-<li>
-<p>
-Se pueden introducir las coordenadas a mano, si son conocidas, usando uno de
- estos cuatro formatos, con la latitud seguida de la longitud:
-</p>
-<div class="literalblock">
-<div class="content">
-<pre><code>Formato ISO 6709 Annex D, p.e. 30°13'28.9"N 30°49'1.5"E
-Grados y minutos decimales, p.e. N30º 13.49760', E30º 49.30788'
-Grados minutos y segundos, p.e. N30° 13' 29.8" , E30° 49' 1.5"
-Grados decimales, p.e. 30.22496 , 30.821798</code></pre>
-</div></div>
-</li>
-</ol></div>
-<div class="paragraph"><p>Las latitudes del hemisferio sur se dan con una <strong>S</strong>, p.e. S30º o con un valor
-negativo, p.e. -30.22496. De igual forma, las longitudes al oeste se facilita
-con una <strong>W</strong>, p.e. W07°, o con un valor negativo, p.e. -7.34323. Algunos teclados
-no tienen el símbolo °. Puede reemplazarse con una <strong>d</strong> como en N30d W20d.
-Si se ha proporcionado un nombre y unas coordenadas, guarda la información
-seleccionando el botón <em>Aplicar cambios</em> arriba en el panel.</p></div>
-<div class="paragraph"><p><strong>Importante</strong>: Las coordenadas GPS de un punto están unidas a un nombre, por
-tanto, guardar inmersiones con coordenadas sin una descripción del lugar
-causará comportamientos inesperados (<em>Subsurface</em> creerá que todos estos puntos
-son el mismo e intentará hacer que toas las coordenadas sean iguales).</p></div>
-<div class="paragraph"><p><strong>Búsqueda de nombres de puntos de buceo</strong>: Si se han introducido coordenadas,
-se puede efectuar una busca automatizada del nombre basada en ellas. Se hace
-cuando <em>Subsurface_utiliza internet para encontrar el nombre del punto de
-buceo basado en las coordenadas introducidas. Si se encuentra un nombre, se
-introduce automáticamente en la casilla de texto. El campo llamado _Puntos de
-buceo en las mismas coordenadas</em>, en la parte baja del panel, contiene nombres
-de otros puntos de buceo en posiciones muy cercanas al actual.</p></div>
-<div class="paragraph"><p>Introduce cualquier otra información textual sobre el punto de buceo
-(Descripción y Notas), entonces selecciona <em>Aplicar cambios</em> para guardar la
-información de este punto de buceo. En una etapa posterior esta información
-puede editarse pulsando el icono del globo a la derecha del nombre del punto en
-la pestaña <strong>Notas</strong>.</p></div>
-<div class="paragraph"><p><strong>Modo de buceo</strong>: Esta es una casilla desplegable que permite elegir el tipo de
-inmersión que se ha realizado. Las opciones son OC (circuito abierto, del
-inglés "open circuit", el ajuste por defecto, valido para la mayoría de buceos
-recreativos), Apnea, CCR (rebreather de circuito cerrado, del inglés "closed
-circuit rebreather") o pSCR (rebreather pasivo de circuito semi-cerrado).</p></div>
-<div class="paragraph"><p><strong>Divemaster</strong>: Introducir el nombre del divemaster o el del guía de inmersión. De
-nuevo, este campo ofrece autocompletado basándose en la lista de divemasters del
-diario actual.</p></div>
-<div class="paragraph"><p><strong>Compañero</strong>: Introducir el nombre(s) del compañero(s) que te acompañaron en la
-inmersión, separados por comas. También se ofrece autocompletado basada en la
-lista de compañeros del registro.</p></div>
-<div class="paragraph"><p><strong>Traje</strong>: Introducir el tipo de traje de buceo que utilizaste para la inmersión.
-Como en los casos anteriores está disponible el autocompletado. Los usuarios de
-traje seco pueden utilizar este campo para registrar que combinación de traje y
-protección térmica utilizaron.</p></div>
-<div class="paragraph"><p><strong>Valoración</strong>: Aquí se puede proporcionar una calificación subjetiva de la
-inmersión en una escala de 5 puntos, clicando en la estrella correspondiente.</p></div>
-<div class="paragraph"><p><strong>Visibilidad</strong>: Igualmente se puede proporcionar una calificación de a la
-visibilidad que había durante la inmersión en una escala de 5 puntos, clicando
-la estrella adecuada.</p></div>
-<div class="paragraph"><p><strong>Etiquetas</strong>: Se pueden introducir etiquetas (separándolas con comas) que
-describan el tipo de inmersión que se efectuó. Algunos ejemplos de etiquetas
-habituales son: barco, a la deriva, entrenamiento, cueva, etc. <em>Subsurface</em>
-tiene muchas etiquetas predefinidas. De nuevo se ofrece autocompletado, por
-ejemplo, si el usuario teclea <code>p</code>, se muestran las etiquetas <strong>pecio</strong>, <strong>piscina</strong>
-y <strong>profunda</strong> para que elija entre ellas.</p></div>
-<div class="paragraph"><p><strong>Notas</strong>: Teclea aquí cualquier información adicional que desees conservar.</p></div>
-<div class="paragraph"><p>Los botones <em>Aplicar cambios</em> y <em>Descartar cambios</em> se utilizan para guardar
-toda la información de los campos del panel de <strong>Información</strong> y del panel de
-<strong>Perfil</strong>, por lo que no hay necesidad de usarlos hasta que se ha añadido
-<strong>TODA</strong> la información. La imagen <a href="#S_Notes_dc">al inicio de esta sección</a>
-muestra un ejemplo de la pestaña <strong>Notas</strong> rellenadas.</p></div>
-</div>
-</div>
-<div class="sect3">
-<h4 id="_equipo">5.2.7. Equipo</h4>
-<div class="paragraph"><p>La pestaña Equipo permite al usuario introducir información acerca del tipo de
-botella y gas utilizado, así como el lastre utilizado en una inmersión. El
-mensaje en azul arriba del panel</p></div>
-<div class="imageblock" style="text-align:center;">
-<div class="content">
-<img src="images/BlueEditBar_f22.jpg" alt="FIGURA: Barra azul de edición" />
-</div>
-</div>
-<div class="paragraph"><p>indica que la inmersión se está editando. Esta parte de <em>Subsurface</em> es
-altamente interactiva y la información de botellas y gases que se introduzca
-determinará el comportamiento del perfil de la inmersión (panel de arriba a la
-derecha).</p></div>
-<div class="paragraph" id="cylinder_definitions"><p><strong>Botellas</strong>: La información de las botellas se introduce con un dialogo como
-este:</p></div>
-<div class="imageblock" style="text-align:center;">
-<div class="content">
-<img src="images/DC_gas-dialogue1_f20.jpg" alt="FIGURA: Diálogo de Botellas inicial" />
-</div>
-</div>
-<div class="paragraph"><p>En las inmersiones manuales, esta información ha de ser introducida a mano. En
-el caso de los ordenadores, a menudo, <em>Subsurface</em> obtiene el gas usado del
-propio ordenador de buceo insertando automáticamente la composición (% oxigeno)
-en la tabla. El botón + arriba a la derecha permite al usuario añadir más
-botellas para esta inmersión. El icono oscuro de papelera le permitirá borrar
-la información de una botella. Nótese que no se puede borrar una botella si
-se usa durante el buceo. Una botella puede estar usándose implícitamente,
-incluso sin un evento de cambio de gas.</p></div>
-<div class="paragraph"><p>Se empieza por seleccionar un tipo de botella. Para ello hay que hacer clic en
-la casilla <strong>Tipo de botella</strong>. Esto hará aparecer un botón que puede usarse para
-mostrar una lista desplegable de botellas.</p></div>
-<div class="imageblock" style="text-align:center;">
-<div class="content">
-<img src="images/DC_gas-dialogue2_f20.jpg" alt="FIGURA: Botón del desplegable de la lista de botellas" />
-</div>
-</div>
-<div class="paragraph"><p>La lista desplegable puede usarse para seleccionar el tipo de botella que
-utilizó en esta inmersión, o el usuario puede empezar a teclear en la casilla,
-lo que mostrará las opciones disponibles para las letras introducidas. El
-<strong>Tamaño</strong> así como su <em>Presión de trabajo</em> se mostrarán automáticamente en el
-dialogo.</p></div>
-<div class="paragraph"><p>A continuación es necesario indicar la presión inicial y final del gas usado
-durante el buceo. Las unidades de presión (métricas/imperiales) corresponden a
-las fijadas en la elección de <em>preferencias</em>.</p></div>
-<div class="paragraph"><p>Finalmente, hay que introducir la mezcla de gas que se usó. Si se utilizó aire,
-se puede poner 21% o dejarlo en blanco. Si se usó nitrox o trimix, hay que
-especificar sus porcentaje de oxigeno y de helio. Se deja en blanco el campo que
-no corresponda utilizar. Tras teclear la información para la botella, hay que
-pulsar <em>ENTER</em> en el teclado o hacer clic fuera de la casilla que contiene el
-cursor. Puede añadirse información para cualquier botella adicional usando el
-botón + de arriba a la derecha. Aquí hay un ejemplo de descripción completa para
-una inmersión en la que se han utilizado dos botellas (aire y EAN50):</p></div>
-<div class="imageblock" style="text-align:center;">
-<div class="content">
-<img src="images/CylinderDataEntry3_f20.jpg" alt="FIGURA: Tabla con la informaación de botellas completada" />
-</div>
-</div>
-<div class="paragraph"><p><strong>Lastre</strong>: Se puede introducir información sobre el sistema de lastre utilizado
-en una inmersión, usando un dialogo muy similar al de la información de las
-botellas. Si se pulsa el botón + de arriba a la derecha en el dialogo de lastre,
-la tabla aparecerá como sigue</p></div>
-<div class="imageblock" style="text-align:center;">
-<div class="content">
-<img src="images/WeightsDataEntry1_f20.jpg" alt="FIGURA: El diálogo Lastre" />
-</div>
-</div>
-<div class="paragraph"><p>Si se hace clic en el campo <em>Tipo</em>, se accede a una lista desplegable con la
-flecha:</p></div>
-<div class="imageblock" style="text-align:center;">
-<div class="content">
-<img src="images/WeightsDataEntry2_f20.jpg" alt="FIGURA: Desplegable con la lista de tipos de lastre" />
-</div>
-</div>
-<div class="paragraph"><p>La lista desplegable puede usarse para seleccionar el tipo de sistema de lastre
-utilizado durante la inmersión, o simplemente teclear en la casilla, con lo que
-se mostrarán las opciones disponibles para los caracteres introducidos. En el
-campo <strong>Peso</strong> se teclea el peso usado durante el buceo. Tras teclear la
-información se pulsa <em>ENTER</em> en el teclado o se hace clic fuera de la casilla
-que contiene el cursor.
-Se puede poner información para más de un sistema de lastre añadiendo otro con
-el botón + de arriba a la derecha. Se pueden borrar lastres usando el icono de
-papelera de la izquierda. A continuación, un ejemplo de información para una
-inmersión con dos tipos de lastre: integrado y cinturón:</p></div>
-<div class="imageblock" style="text-align:center;">
-<div class="content">
-<img src="images/WeightsDataEntry3_f20.jpg" alt="FIGURA: Tabla con información de lastre completada" />
-</div>
-</div>
-</div>
-<div class="sect3">
-<h4 id="_editar_simultaneamente_varias_inmersiones_seleccionadas">5.2.8. Editar simultáneamente varias inmersiones seleccionadas</h4>
-<div class="paragraph"><p><em>METODO 1</em>: Tras descargar inmersiones de un ordenador de buceo, los perfiles
-de los buceos descargados se mostrarán en el panel "Perfil de la inmersión",
-así como algunas otras informaciones en las pestañas "Notas" y
-"Equipo". Sin embargo, otros campos permanecerán vacíos.</p></div>
-<div class="paragraph"><p>Puede resultar útil editar simultáneamente algunos de los campos de las "Notas
-de la Inmersión" o del "Equipo". Por ejemplo, es posible que un buceador
-efectuara varias inmersiones en un solo día utilizando el mismo equipo, o en el
-mismo punto de buceo o con el mismo guía o compañero. En lugar de completar la
-información de las inmersiones una por una, se pueden seleccionar todos los
-buceos deseados en la "Lista de Inmersiones" e insertar la información común en
-las "Notas" y "Equipo".</p></div>
-<div class="paragraph"><p>La edición simultánea solo funciona con campos que no contienen aún ninguna
-información. Esto significa que si, para una inmersión en concreto, uno de los
-campos ya ha sido rellenado, no será modificado por la edición simultánea en
-ese buceo en concreto. Técnicamente, la regla para editar varias inmersiones a
-la vez es: "si el campo que estamos editando contiene <em>exactamente la misma
-información</em> en todas las inmersiones que hemos seleccionado, la nueva
-información introducida se sustituye en todas las inmersiones seleccionadas, de
-lo contrario solo se cambia la inmersión que estemos editando aunque haya
-varias seleccionadas.</p></div>
-<div class="paragraph"><p>Esto acelera notablemente el rellenado del divelog después de haber efectuado
-varios buceos similares.</p></div>
-<div class="paragraph" id="S_CopyComponents"><p><em>METODO 2</em>: Hay una forma diferente de hacer lo mismo. Seleccionamos un buceo
-que contenga toda la información apropiada en las pestañas <strong>Notas</strong> y <strong>Equipo</strong>.
-Entonces, desde el menú principal, seleccionamos
-<em>Registro → Copiar componentes</em>. Aparecerá una ventana con casillas
-seleccionables para la mayoría de campos de las pestañas <strong>Notas</strong>
-y <strong>Equipo</strong>. Selecciona los campos a copiar desde la inmersión seleccionada,
-luego pulsa <em>Aceptar</em>. Ahora selecciona en la <strong>Lista de Inmersiones</strong> los buceos
-a los que pegar esta información. Desde el menú principal, selecciona <em>Registro
- → Pegar componentes</em>. Tras esto, todas las inmersiones seleccionadas
- contendrán los datos seleccionados previamente de la anterior inmersión.</p></div>
-</div>
-<div class="sect3">
-<h4 id="_anadir_marcas_a_una_inmersion">5.2.9. Añadir Marcas a una inmersión</h4>
-<div class="paragraph"><p>Muchos buceadores desean anotar en sus inmersiones textos que indiquen sucesos
-concretos durante el buceo, p.e. "Avistamos delfines" o "Lanzada boya deco".
-Esto se hace fácilmente:</p></div>
-<div class="ulist"><ul>
-<li>
-<p>
-Clic derecho sobre el punto adecuado del perfil de inmersión, se desplegará
- el menú contextual del perfil. Se selecciona <em>Añadir marca</em>. Una bandera roja
- aparecerá sobre el perfil en el punto inicialmente seleccionado (ver <strong>A</strong> a
- continuación).
-</p>
-</li>
-<li>
-<p>
-Clic derecho sobre la bandera roja. Se desplegará el menú contextual (ver
- <strong>B</strong> a continuación). Se selecciona <em>Editar nombre</em>.
-</p>
-</li>
-<li>
-<p>
-Se mostrará una casilla de texto. Se teclea en ella el texto oportuno para la
- marca (ver <strong>C</strong> a continuación). Se selecciona <em>Aceptar</em>, con lo que se guarda el
- texto asociado a la marca.
-</p>
-</li>
-<li>
-<p>
-Cuando el ratón pase sobre el marcador rojo, el texto guardado se mostrará en
- la parte de debajo del cajetín de información (ver <strong>D</strong> a continuación).
-</p>
-</li>
-</ul></div>
-<div class="imageblock" style="text-align:center;">
-<div class="content">
-<img src="images/Bookmarks.jpg" alt="FIGURA: Diálogo de marcadores" />
-</div>
-</div>
-</div>
-<div class="sect3">
-<h4 id="_guardar_la_informacion_de_buceo_actualizada">5.2.10. Guardar la información de buceo actualizada</h4>
-<div class="paragraph"><p>La información introducida en las pestañas Notas y Equipo puede
-guardarse utilizando los dos botones de arriba a la derecha de la pestaña
-<strong>Notas</strong>. Si se pulsa <em>Aplicar cambios</em> los datos del buceo se guardan en la
-imagen en memoria de la inmersión. Si se pulsa <em>Descartar cambios</em> los datos
-de buceo recién introducidos se borran de la memoria, aunque el perfil y los
-datos descargados del ordenador quedarán retenidos. Cuando el usuario salga de
-<em>Subsurface</em> hay una pregunta final para confirmar si los nuevos datos de deben
-guardar en caso de no haberlo hecho antes.</p></div>
-</div>
-</div>
-<div class="sect2">
-<h3 id="_importar_informacion_de_inmersiones_de_otras_fuentes_u_otros_formatos_de_datos">5.3. Importar información de inmersiones de otras fuentes u otros formatos de datos</h3>
-<div class="paragraph" id="S_ImportingAlienDiveLogs"><p>Si el usuario bucea desde hace algún tiempo, es posible que bastantes
-inmersiones hayan sido registradas usando otro software. No es necesario teclear
-de nuevo esta información ya que, probablemente, estos diarios puedan importarse
-a <em>Subsurface</em>. <em>Subsurface</em> puede importar un amplio abanico de diarios de
-otros softwares de registro. Mientras que algún software se soporta nativamente,
-en otros casos el usuario debe exportar el(los) diario(s) a un
-formato intermedio para que pueda ser importado a <em>Subsurface</em>.
-Actualmente, <em>Subsurface</em> soporta importar archivos <em>CSV</em> de diferentes origenes.
-Los archivos de APD LogViewer, XP5, Sensus y Seabear están preconfigurados,
-pero dado que es flexible, los usuarios pueden configurar sus propias
-importaciones. Diarios creados manualmente (p.e. en hojas de cálculo) también
-pueden importarse configurando manualmente el CSV. <em>Subsurface</em> también puede
-importar archivos UDDF y UDCF, usados por algún software y algunos ordenadores
-de buceo como el H&W DR5 o el XDeep Black BT. Finalmente, para algunos programas
-de registro como el Mares Dive Organiser, se sugiere exportar los diarios primero
-a un servicio web como <em>divelogs.de</em> e importarlos desde allí a <em>Subsurface</em>, ya
-que <em>divelogs.de</em> soporta algunos pocos formatos que <em>Subsurface</em> no puede leer
-en la actualidad.</p></div>
-<div class="paragraph"><p>Si el formato del otro software está soportado nativamente en <em>Subsurface,
-debería ser suficiente con seleccionar bien _Importar→Importar archivos de
-registro</em>, bien <em>Archivo→Abrir registro</em> . <em>Subsurface</em> soporta directamente
-los formatos de datos de muchos ordenadores de buceo, incluyendo Suunto y
-Shearwater.</p></div>
-<div class="paragraph"><p>Al importar inmersiones, <em>Subsurface</em> intenta detectar múltiples registros del
-mismo buceo y mezcla la información lo mejor que puede. Si no existen problemas
-con las zonas horarias (u otras razones que hagan que la hora de comienzo de las
-inmersiones sean significativamente diferentes) <em>Subsurface</em> no creará entradas
-duplicadas. A continuación sigue más información relativa a importar datos a
-<em>Subsurface</em></p></div>
-<div class="sect3">
-<h4 id="Unified_import">5.3.1. Utilizar el diálogo de importación universal</h4>
-<div class="paragraph"><p>El importar buceos desde otros programas se hace a través de una interfaz
-universal que se activa seleccionando Importar desde el menú principal y
-haciendo clic en <em>Importar archivos de registro</em>. Con ello se mostrará el
-dialogo <strong>A</strong> a continuación.</p></div>
-<div class="imageblock" style="text-align:center;">
-<div class="content">
-<img src="images/Import1_f20.jpg" alt="FIGURA: Importar: paso 1" />
-</div>
-</div>
-<div class="paragraph"><p>Abajo a la derecha hay un desplegable con una etiqueta por defecto Archivos de
-registro que da acceso a los diferentes tipos de archivo disponibles para
-importar directamente, como en el dialogo <strong>B</strong> anterior. Actualmente son:</p></div>
-<div class="ulist"><ul>
-<li>
-<p>
-Diarios en formato XML (DivingLog 5.0, MacDive y varios otros)
-</p>
-</li>
-<li>
-<p>
-Archivos de Cochran
-</p>
-</li>
-<li>
-<p>
-Diarios en formato UDDF (p.e. Kenozoooid)
-</p>
-</li>
-<li>
-<p>
-Diarios en formato UDCF
-</p>
-</li>
-<li>
-<p>
-Diarios de CCR Poseidon MKVI
-</p>
-</li>
-<li>
-<p>
-Diarios de CCR APD Inspiration/Evolution
-</p>
-</li>
-<li>
-<p>
-Diarios de LiquidVision
-</p>
-</li>
-<li>
-<p>
-Diarios de divelogs.de
-</p>
-</li>
-<li>
-<p>
-Diarios de DataTrak
-</p>
-</li>
-<li>
-<p>
-Diarios de OSTCTools
-</p>
-</li>
-<li>
-<p>
-JDiveLog
-</p>
-</li>
-<li>
-<p>
-Suunto Dive Manager (DM3 y DM4)
-</p>
-</li>
-<li>
-<p>
-Diarios en formato <em>CSV</em> (basados en texto o en hojas de cálculo), incluidos
-diarios de CCR APD.
-</p>
-</li>
-</ul></div>
-<div class="paragraph"><p>Seleccionar el archivo correspondiente en la lista del diálogo abre el archivo
-importado directamente en la <strong>Lista de Inmersiones</strong> de <em>Subsurface</em>. También
-están soportados algunos otros formatos, no accesibles desde el diálogo
-Importar, como se explica a continuación.</p></div>
-</div>
-<div class="sect3">
-<h4 id="_importar_desde_ostctools">5.3.2. Importar desde OSTCTools</h4>
-<div class="paragraph"><p><em>OSTCTools</em> es un conjunto de herramientas basadas en Windows de descarga y
-gestión para la familia de ordenadores OSTC. <em>OSTCTools</em> puede descargar datos
-de las inmersiones y guardarlos en archivos binarios con extensión <em>.dive</em> .
-Subsurface puede importar directamente estos archivos utilizando el diálogo de
-importación universal. Desde la lista desplegable abajo a la derecha, se
-selecciona la opción correspondiente, lo cual hará visibles los diarios en la
-lista del panel. Se seleccionan una o varias inmersiones, y se hace click en el
-botón <em>Abrir</em>. Las inmersiones importadas desde OSTCTools se mostrarán en el
-panel <strong>Lista de inmersiones</strong>.</p></div>
-<div class="paragraph"><p>Actualmente, todos los ordenadores de H&W que soporte OSTCTools pueden importarse
-a <em>Subsurface</em>, esto incluye OSTC, OSTC Mk2, OSTC 2N/2C, OSTC3, OSTC Sport, y,
-probablemente aunque sin probar, Frog, OSTC2 y OSTC CR.</p></div>
-<div class="paragraph"><p>Por favor, recuerda que OSTCTools <strong>no</strong> es un auténtico software de registro de
-diarios de buceo, sino un útil conjunto de herramientas de gestión y análisis
-para dispositivos OSTC. Así pues, importar inmersiones a <em>Subsurface</em> sólo
-nos proporcionará datos relativos al ordenador de buceo; el usuario tendrá
-que completar manualmente el resto de datos que le puedan resultar importantes
-(compañeros, equipo, notas, etc).</p></div>
-</div>
-<div class="sect3">
-<h4 id="_importar_desde_mares_dive_organiser_v2_1">5.3.3. Importar desde Mares Dive Organiser V2.1</h4>
-<div class="paragraph"><p>Dado que Mares utiliza software propiedad de Microsoft no compatible con
-aplicaciones multiplataforma, estos diarios no pueden importarse directamente a
-<em>Subsurface</em>. Los diarios de Mares necesitan ser importados usando un proceso en
-tres pasos, utilizando <em>www.divelogs.de</em> como mecanismo para extraer la
-información.</p></div>
-<div class="olist arabic"><ol class="arabic">
-<li>
-<p>
-Los datos del Mares Dive Organiser necesitan exportarse al escritorio del
- usuario utilizando una extensión de archivo <em>.sdf</em>. Dirigirse a
- <a href="#Mares_Export">Apendice C</a> para más información.
-</p>
-</li>
-<li>
-<p>
-Los datos deben ser importados entonces desde <em>www.divelogs.de</em>. Se necesita
- crear una cuenta de usuario en <em>www.divelogs.de</em>, entrar a la página, entonces
- seleccionar <em>Import Logbook → Dive Organiser</em> en el menú de la izquierda. Hay
- que seguir cuidadosamente las instrucciones para transferir la información (en
- formato <em>.sdf</em>) desde la base de datos de Dive Organiser a <em>www.divelogs.de</em>.
-</p>
-</li>
-<li>
-<p>
-Finalmente importar las inmersiones desde <em>divelogs.de</em> a <em>Subsurface</em>,
- utilizando las instrucciones a continuación.
-</p>
-</li>
-</ol></div>
-</div>
-<div class="sect3">
-<h4 id="S_ImportingDivelogsDe">5.3.4. Importar inmersiones desde <strong>divelogs.de</strong></h4>
-<div class="paragraph"><p>Importar información de inmersiones desde <em>divelogs.de</em> es simple, se usa un
-único diálogo. Se selecciona <em>Importar → Importar desde Divelogs.de</em> en el menú
-principal. Esto despliega un diálogo (ver figura <strong>A</strong> abajo a la izquierda). Es
-necesario introducir un usuario y password para <em>divelogs.de</em> en los campos que
-se indiquen y luego pulsar el botón <em>Descargar</em>. La descarga desde divelogs.de
-comienza inmediatamente y se refleja en una barra de progreso de la ventana del
-diálogo. Al finalizar la descarga se indica el estado de "exito" (ver figura
-<strong>B</strong> abajo a la derecha). Se selecciona el botón <em>Aplicar</em>, tras lo cual las
-inmersiones importadas aparecerán en el panel <strong>Lista de Inmersiones</strong>.</p></div>
-<div class="imageblock" style="text-align:center;">
-<div class="content">
-<img src="images/Divelogs1.jpg" alt="FIGURE:Descargar desde Divelogs.de" />
-</div>
-</div>
-</div>
-<div class="sect3">
-<h4 id="S_ImportingCSVData">5.3.5. Importar datos en formato CSV</h4>
-<div class="paragraph"><p>Se puede utilizar un archivo .csv (valores separados por comas) para importar
-información de buceo así como perfiles de inmersión (como en el caso de los
-CCRs APD Inspiration o el Evolution) o como metadatos de buceo (en caso de que
-el usuario guarde los datos en una hoja de cálculo). El formato <em>CSV</em> es un
-formato universal simplificado que permite un intercambio facil de información
-entre difeerentes ordenadores o paquetes de software. Para una introducción a
-archivos en formato <em>CSV</em> ver <a href="#S_CSV_Intro">Introducción de un buceador a los archivos CSV</a>.
-Los diarios de <em>Subsurface</em> también pueden exportarse a formato <em>CSV</em> para
-otro software que lea este formato. Ver el <a href="#S_Appendix_D">APPENDIX D: Exportar una hoja de cálculo a formato CSV</a>
-para información que puede resultar útil para importar datos basados en hojas
-de cálculo a <em>Subsurface</em>.</p></div>
-</div>
-<div class="sect3">
-<h4 id="S_ImportingCSVDives">5.3.6. Importar inmersiones en formato <em>CSV</em> desde ordenadores u otro software</h4>
-<div class="paragraph"><p>Se puede visualizar un archivo <em>CSV</em> usando un editor de textos ordinario. Se
-organiza, normalmente, en una sola línea que proporciona las cabeceras (o
-<em>nombres de campo</em> o <em>encabezamientos</em>) de las columnas de datos, seguidos por
-los datos a un registro (inmersión en nuestro caso) por línea.</p></div>
-<div class="paragraph"><p>Hay dos tipos de archivo <em>CSV</em> que pueden importarse en <em>Subsurface</em>:</p></div>
-<div class="olist arabic"><ol class="arabic">
-<li>
-<p>
-<em>Detalles de inmersión CSV</em>: Este formato contiene información similar a la
- de un típico diario escrito, p.e. fecha, hora, profundidad, duración, nombre
- de los compañeros y divemaster, y tal vez alguna información sobre botellas,
- así como algunos comentarios sobre la inmersión. Toda la información sobre
- un buceo va en una sola línea siguiendo el orden del encabezamiento de las
- columnas.
-</p>
-</li>
-<li>
-<p>
-<em>Perfil de inmersión CSV</em>: Este formato incluye mucha más información
- sobre una sola inmersión. Por ejemplo, puede haber información a intervalos
- de 30 segundos indicando la profundidad, la temperatura del agua a esa
- profundidad y presión de las botellas en ese instante. Cada línea contiene
- la información de un solo instante durante la inmersión, 30 segundos tras el
- anterior. Se requieren muchas líneas para completar la información del
- perfil de profundidad de un buceo. Es un formato utilizado comúnmente para
- exportar por los equipos de buceo en circuito cerrado (CCR) y muchos
- paquetes de software que manejan ordenadores de buceo y/o diarios.
-</p>
-</li>
-</ol></div>
-<div class="paragraph"><p>Antes de poder importar los datos a <em>Subsurface</em> se necesitan saber algunas
-cosas sobre los mismos:</p></div>
-<div class="olist loweralpha"><ol class="loweralpha">
-<li>
-<p>
-¿ Que carácter separa las distintas columnas en una línea de datos ? Este
- separador de campos debería ser una coma (,) un punto y coma (;) o un
- tabulador. Puede averiguarse abriendo el archivo con un editor de textos.
- Si se trata de una coma, el carácter será claramente visible entre valores.
- Si no hay comas a la vista, seguramente esté delimitado por tabuladores.
-</p>
-</li>
-<li>
-<p>
-¿ Que columnas de datos necesitamos importar a <em>Subsurface</em> ? ¿ Es un archivo
- de <em>Detalles de inmersión CSV</em> o de <em>Perfil de inmersión CSV</em> ? Ábrelo con un
- editor de textos y fíjate en los títulos de las columnas a importar y sus
- posiciones.
-</p>
-</li>
-<li>
-<p>
-¿ Está la información numérica (la profundidad por ejemplo) en unidades
- métricas o imperiales ?
-</p>
-</li>
-</ol></div>
-<div class="paragraph"><p>Armado con esta información, importar en <em>Subsurface</em> es muy fácil. Selecciona
-<em>Importar→Importar CSV</em> en el menú principal. Aparecerá el siguiente dialogo:</p></div>
-<div class="imageblock" style="text-align:center;">
-<div class="content">
-<img src="images/csv_import1_f20.jpg" alt="FIGURE: Diálogo 1, Descarga CSV" />
-</div>
-</div>
-<div class="paragraph"><p>Fíjate que, arriba a la izquierda, hay una lista desplegable que contiene ajustes
-preconfigurados para algunos de los ordenadores de buceo y paquetes de software
-más comunes que podemos encontrar los buceadores. Si el archivo <em>CSV</em> que vamos
-a importar se originó en alguno de estos paquetes o dispositivos, selecciónalo.
-En otro caso, utiliza la opción <em>Importación manual</em>. El panel de configuración
-también tiene listas desplegables para especificar el separador de campos
-adecuado (tabulado, coma o punto y coma), el formato de fecha usado en el CSV,
-las unidades de tiempo (segundos, minutos o minutos:segundos), así como el
-sistema de unidades (métrico o imperial) utilizado. Seleccionar las opciones
-correctas es crítico para importar correctamente los datos.</p></div>
-<div class="paragraph"><p>La última tarea es asegurarse que todas las columnas de datos tienen las
-cabeceras correctas. La línea superior de la parte blanca de la tabla contiene
-las cabeceras de columnas encontradas en el archivo <em>CSV. La fila de celdas
-azules inmediatamente sobre la anterior contiene los nombres que _Subsurface</em>
-ha entendido. La zona blanca inmediatamente debajo de las listas desplegables
-contiene los nombres de campos que <em>Subsurface</em> reconoce. Estos nombres están
-en globos azules que se pueden arrastrar y soltar en las celdas azules a las
-que correspondan en la parte superior de la tabla. Esto se muestra en la
-imagen a continuación.</p></div>
-<div class="imageblock" style="text-align:center;">
-<div class="content">
-<img src="images/csv_import2_f20.jpg" alt="FIGURA: Diálogo 2, Descarga CSV" />
-</div>
-</div>
-<div class="paragraph"><p>Continua haciendo hasta que todas los encabezamientos de columnas en la fila
-azul de celdas correspondan a las cabeceras listadas en la parte alta del
-diálogo. Habiendo completado esta tarea, selecciona el botón <em>OK</em> abajo a la
-derecha del diálogo. Los datos del archivo <em>CSV</em> se importarán y se mostrarán
-en el panel <strong>Lista de inmersiones</strong>.</p></div>
-<div class="sidebarblock" id="S_CSV_Intro">
-<div class="content">
-<div class="paragraph"><p><strong>Introducción de un buceador a los archivos <em>CSV</em></strong></p></div>
-<div class="admonitionblock">
-<table><tr>
-<td class="icon">
-<img src="images/icons/important.png" alt="Important" />
-</td>
-<td class="content"><em>CSV</em> es una abreviatura para un formato de archivo de datos: <em>Comma-Separated
-Variables</em> en inglés. Es un formato de archivo que permite visualizar o editar
-la información usando un editor de textos como el Bloc de Notas (Windows),
-Gedit (linux) o TextWrangler (OS/X). Las dos principales ventajas del formato
-CSV son que los datos son fácilmente editables como texto sin usar ningún
-software propietario y asegurando que toda la información es legible, no siendo
-ofuscada por ningún atributo de los que el software propietario inserta en los
-archivos.
-A causa de su simplicidad, el formato <em>CSV</em> se utiliza como formato de intercambio
-entre muchos paquetes de software, por ejemplo entre hojas de cálculo,
-estadísticas, gráficos, bases de datos y software de buceo. En <em>Subsurface</em>, los
-archivos <em>CSV</em> también se pueden usar para importar información de otras fuentes
-tales como diarios basados en hojas de cálculo o, incluso, de algunos ordenadores.</td>
-</tr></table>
-</div>
-<div class="paragraph"><p>El atributo más importante de un archivo <em>CSV</em> es el <em>separador de campos</em>, esto
-es, el carácter utilizado para separar campos dentro de una línea. El separador
-de campos es, habitualmente, una coma, un punto y coma, un espacio o un
-tabulador. Al exportar datos desde una hoja de cálculo, se necesita especificar
-el carácter separador para poder crear el archivo CSV. Los archivos <em>CSV</em> están,
-normalmente, organizados en una sola línea que proporciona las cabeceras (o
-<em>nombres de campos</em>) de las columnas de datos, seguido por los datos, a un
-registro por línea. Nótese que cada nombre de campo puede estar formado por más
-de una palabra separadas por espacios; por ejemplo <em>Punto de buceo</em>. A
-continuación, un ejemplo de información de cuatro inmersiones utilizando la coma
-como separador de campos:</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>En este formato los datos no son legibles con facilidad para los humanos. A
-continuación los mismos datos usando el tabulador como separador:</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>Es obvio por qué mucha gente prefiere el formato con tabulador al separado por
-comas. La desventaja es que los tabuladores no se pueden ver. Por ejemplo el
-espacio entre <em>Dive</em> y <em>date</em> en la primera línea puede ser un espacio o un
-tabulador (en este caso un espacio). Si los nombres de campo de la primera línea
-son largos, no se puede mantener la alineación con los otros campos de datos.
-A continuación un ejemplo muy simplificado y recortado de un diario <em>CSV</em> del
-ordenador de buceo de un rebreather CCR APD:</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>Cuando un archivo <em>CSV</em> se selecciona para importar, <em>Subsurface</em> muestra las
-cabeceras de las columnas y unas pocas lineas de datos del archivo, facilitando
-mucho, de esta forma, trabajar con archivos <em>CSV</em>.
-Conocer algunas cosas básicas sobre el contenido del archivo <em>CSV</em> permite una
-importación mejor de las inmersiones a <em>Subsurface</em>.</p></div>
-</div></div>
-<div class="paragraph"><p>+[IMPORTANT]
-La importación <em>CSV</em> tiene un par de advertencias. Se deberían evitar algunos
-caracteres especiales como el signo &, menor que (<), mayor que (>) y comillas
-(") como parte de los número o del texto de una casilla. El archivo debería
-usar el conjunto de caracteres UTF-8, si se usan caracteres no ASCII. También
-podría causar problemas el tamaño del archivo <em>CSV</em>. Importar 100 buceos de una
-sola vez (<em>Detalles de inmersión CSV</em>) funciona, pero archivos mayores podrían
-exceder los límites del analizador utilizado. Si se encontraran problemas al
-importar <em>CSV</em> sería conveniente probar con un archivo más pequeño solo para
-asegurarse de que el resto funciona.</p></div>
-</div>
-</div>
-<div class="sect2">
-<h3 id="S_Companion">5.4. Importar coordenadas GPS con la app <em>Subsurface</em> Companion para teléfonos móviles</h3>
-<div class="paragraph"><p>Utilizando la app <em>Subsurface</em> Companion en un dispositivo Android o <a href="#S_iphone"><em>iPhone</em></a>
-con GPS, se pueden pasar automáticamente las coordenadas de los
-puntos de buceo al registro de <em>Subsurface</em>. La app Companion guarda las
-ubicaciones de buceo en un servidor dedicado basado en internet. <em>Subsurface</em>
-puede recoger las coordenadas desde este servidor.</p></div>
-<div class="paragraph"><p>Para hacer esto:</p></div>
-<div class="sect3">
-<h4 id="_crear_una_cuenta_para_la_app_companion">5.4.1. Crear una cuenta para la app Companion</h4>
-<div class="ulist"><ul>
-<li>
-<p>
-Registrarse en la <a href="http://api.hohndel.org/login/">página web de <em>Subsurface</em>
- companion</a>. Se recibirá un correo de confirmación con instrucciones y un
- <strong>DIVERID</strong> personal, un largo número que te dará acceso a las capacidades de la
- app Companion.
-</p>
-</li>
-<li>
-<p>
-Descargar la app desde
- <a href="https://play.google.com/store/apps/details?id=org.subsurface">Google Play Store</a>
- o desde
- <a href="http://f-droid.org/repository/browse/?fdfilter=subsurface&fdid=org.subsurface">F-Droid</a>.
-</p>
-</li>
-</ul></div>
-</div>
-<div class="sect3">
-<h4 id="_utilizar_em_subsurface_em_companion_en_un_smartphone_android">5.4.2. Utilizar <em>Subsurface</em> companion en un smartphone Android</h4>
-<div class="paragraph"><p>La primera vez que se utiliza, la app tiene tres opciones:</p></div>
-<div class="ulist"><ul>
-<li>
-<p>
-<em>Create a new account</em>. Equivalente a registrase en la página de <em>Subsurface</em>
- companion utilizando un navegador de internet. Se puede solicitar un <strong>DIVERID</strong>
- con esta opción que se recibirá vía correo electrónico y se confirmará a través
- de la <a href="http://api.hohndel.org/login/">_página web de Subsurface companion</a> para
- activar la cuenta.
-</p>
-</li>
-<li>
-<p>
-<em>Retrieve an account</em>. Si el usuario olvidó su <strong>DIVERID</strong> recibirá un correo
- para recuperar el número.
-</p>
-</li>
-<li>
-<p>
-<em>Use an existing account</em>. Se pide el <strong>DIVERID</strong>. La app conserva el <strong>DIVERID</strong>
- y no lo vuelve a pedir, a menos que se utilice la opción <em>Disconnect</em> en el menú
- (ver a continuación).
-</p>
-</li>
-</ul></div>
-<div class="admonitionblock">
-<table><tr>
-<td class="icon">
-<img src="images/icons/important.png" alt="Important" />
-</td>
-<td class="content">En <em>Subsurface</em> el DIVERID también debe marcarse en el panel Preferencias, al
-que se llega seleccionando Archivo→Preferencias→Predeterminadas desde el menú
-principal en el propio <em>Subsurface</em>.
-Esto facilitará la sincronización entre <em>Subsurface</em> y la app Companion.</td>
-</tr></table>
-</div>
-</div>
-<div class="sect3">
-<h4 id="_crear_nuevas_ubicaciones_de_buceo">5.4.3. Crear nuevas ubicaciones de buceo</h4>
-<div class="paragraph"><p>Ahora se está preparado para tomar una posición de buceo y enviarla al servidor.
-La pantalla de Android se verá como lo imagen de abajo a la izquierda (<strong>A</strong>),
-pero sin ninguna inmersión.</p></div>
-<div class="paragraph"><p>Tocando el icono "+" de arriba a la derecha se abrirá un menú con tres opciones:</p></div>
-<div class="ulist"><ul>
-<li>
-<p>
-Current: Se pedirá un nombre para el lugar (o que se active el GPS si estaba
- apagado). Tras lo cual se guardará la posición actual.
-</p>
-</li>
-<li>
-<p>
-Use map: Esta opción permite al usuario fijar una posición buscándola en un
- mapamundi. Se muestra un mapamundi(ver <strong>B</strong> a continuación) sobre el cual indicar
- la posición con una pulsación larga en la pantalla táctil (si la posición
- marcada es errónea, simplemente se indica una nueva). A continuación hay que
- seleccionar el símbolo de chequeo arriba a la derecha. Se mostrará un dialogo
- que permitirá introducir un nombre para el punto seleccionado y la fecha y hora
- del buceo (ver <strong>C</strong> abajo). De cara a importar esta posición de buceo a
- <em>Subsurface</em> es recomendable fijar la misma hora de inmersión que la marcada por
- el ordenador de buceo.
-</p>
-</li>
-</ul></div>
-<div class="imageblock" style="text-align:center;">
-<div class="content">
-<img src="images/Companion_5.jpg" alt="FIGURA: Companion App, añadir posición usando e mapa" />
-</div>
-</div>
-<div class="ulist"><ul>
-<li>
-<p>
-Importar desde archivos GPX: El dispositivo android buscará archivos .gpx y
- mostrará los que se localicen. El archivo que se seleccione se abrirá y se
- mostrarán las posiciones que contiene. Ahora hay que elegir las ubicaciones
- correctas y luego seleccionar el símbolo de chequeo arriba ala derecha, tras lo
- cual las posiciones se enviarán al servicio web y se añadirán a la lista del
- dispositivo android.
-</p>
-</li>
-</ul></div>
-</div>
-<div class="sect3">
-<h4 id="_listas_de_ubicaciones_de_buceo">5.4.4. Listas de ubicaciones de buceo</h4>
-<div class="paragraph"><p>La pantalla principal muestra una lista de ubicaciones de buceo, cada una con un
-nombre, fecha y hora (ver <strong>A</strong> debajo). Algunas posiciones pueden tener una
-flechita sobre la casilla de selección, lo que indica que necesitan remitirse al
-servidor. Se pueden seleccionar posiciones individuales de la lista. Una
-posición seleccionada tiene una marca de chequeo en la casilla de selección. Se
-pueden efectuar operaciones en grupo (como <em>Delete</em> o <em>Send</em>) sobre todas las
-operaciones seleccionadas a la vez.</p></div>
-<div class="paragraph"><p>Las posiciones de buceo de la lista pueden visualizarse de dos maneras: una
-lista de ubicaciones o un mapa sobre el que se indican las posiciones. La forma
-de visualizarla (lista o mapa) se modifica seleccionando <em>Dives</em> arriba a la
-izquierda de la pantalla (ver <strong>A</strong> abajo) y luego eligiendo el modo. Si se
-selecciona una ubicación (en la lista o en el mapa), se abre un panel de edición
-(ver *C abajo) donde pueden cambiarse algunos detalles.</p></div>
-<div class="imageblock" style="text-align:center;">
-<div class="content">
-<img src="images/Companion_4.jpg" alt="FIGURE: Companion App, añadir posición usando el mapa" />
-</div>
-</div>
-<div class="paragraph"><p>Cuando se pulsa sobre una posición (<strong>sin</strong> seleccionar la casilla), se mostrarán
-el nombre del punto, la fecha y hora y las coordenadas GPS, con dos opciones
-arriba de la pantalla:</p></div>
-<div class="ulist"><ul>
-<li>
-<p>
-Edit (lapiz): Permite cambiar el nombre u otras características del punto de
- buceo.
-</p>
-</li>
-<li>
-<p>
-Maps: Muestra el punto de buceo sobre un mapa.
-</p>
-</li>
-</ul></div>
-<div class="paragraph"><p>Tras editar y guardar la posición de buceo (ver <strong>C</strong> abajo), se necesita subirla
-al servidor, como se explicará a continuación.</p></div>
-</div>
-<div class="sect3">
-<h4 id="_subir_puntos_de_buceo">5.4.5. Subir puntos de buceo</h4>
-<div class="paragraph"><p>Hay varias formas de enviar los buceos al servidor; la más fácil es simplemente
-seleccionar la inmersión (ver la imagen <strong>A</strong> abajo) y luego pulsar la flecha
-arriba a la derecha de la pantalla.</p></div>
-<div class="admonitionblock">
-<table><tr>
-<td class="icon">
-<img src="images/icons/important.png" alt="Important" />
-</td>
-<td class="content">El usuario debe tener cuidado ya que el icono de papelera de la derecha
-significa exactamente lo que se supone: borra los puntos de buceo seleccionados.</td>
-</tr></table>
-</div>
-<div class="imageblock" style="text-align:center;">
-<div class="content">
-<img src="images/Companion_1.jpg" alt="FIGURA: Capturas (A-B) de la app companion" />
-</div>
-</div>
-<div class="paragraph"><p>Después de un viaje de buceo usando Companion, todos los puntos de inmersión
-estarán listos para ser descargados a un diario de <em>Subsurface</em> (ver a
-continuación).</p></div>
-</div>
-<div class="sect3">
-<h4 id="_ajustes_de_la_companion_app">5.4.6. Ajustes de la Companion app</h4>
-<div class="paragraph"><p>Seleccionar la opción Settings del menú, resulta en la imagen B de arriba a la
-derecha.</p></div>
-<div class="sect4">
-<h5 id="_server_and_account">Server and account</h5>
-<div class="ulist"><ul>
-<li>
-<p>
-<em>Web-service URL</em>. Esta está predefinida (<a href="http://api.hohndel.org/">http://api.hohndel.org/</a>)
-</p>
-</li>
-<li>
-<p>
-<em>User ID.</em> El DIVERID obtenido al registrarse como indicábamos antes. La forma
- más fácil de introducirlo es simplemente copiar y pegar desde el correo de
- confirmación pero, desde luego, el usuario teclearlo carácter a carácter.
-</p>
-</li>
-</ul></div>
-</div>
-<div class="sect4">
-<h5 id="_synchronization">Synchronization</h5>
-<div class="ulist"><ul>
-<li>
-<p>
-<em>Synchronize on startup</em>. Si se selecciona, los puntos de buceo del
- dispositivo android y los del servicio web se sincronizarán cada vez que se
- inicie la app.
-</p>
-</li>
-<li>
-<p>
-<em>Upload new dives</em>. Si se selecciona, cada vez que el usuario añada una
- ubicación de buceo, se enviará automáticamente al servidor.
-</p>
-</li>
-</ul></div>
-</div>
-<div class="sect4">
-<h5 id="_background_service">Background service</h5>
-<div class="paragraph"><p>En vez de tomar una sola ubicación de buceo, los usuarios pueden dejar el
-servicio ejecutándose en segundo plano en tu dispositivo android, tomando
-continuamente posiciones GPS</p></div>
-<div class="paragraph"><p>Los ajustes, a continuación, definirán el comportamiento del servicio:</p></div>
-<div class="ulist"><ul>
-<li>
-<p>
-<em>Min duration</em>. En minutos. La app intentará tomar una posición cada X minutos
- hasta que el usuario la detenga.
-</p>
-</li>
-<li>
-<p>
-<em>Min distance</em>. En metros. Distancia mínima entre dos posiciones.
-</p>
-</li>
-<li>
-<p>
-<em>Name template</em>. La plantilla de nombre que usará la app cuando guarde las
- posiciones.
-</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>¿ Como trabaja el servicio en segundo plano ?</em> Suponiendo que el usuario ha
-fijado 5 minutos y 50 metros en los ajustes anteriores, la app tomará una
-posición en la ubicación actual, seguida por otra cada 5 minutos <strong>o</strong> cada vez
-que se desplace 50 metros de la posición anterior. Si las siguientes ubicaciones
-están en el radio de 50 metros de la anterior, no se guardarán. De esta forma,
-si el usuario no se está moviendo, solo se guarda una posición, pero si se
-mueve, puede llegar a tener una traza de su viaje al guardar una ubicación cada
-50 metros.</td>
-</tr></table>
-</div>
-</div>
-<div class="sect4">
-<h5 id="_other">Other</h5>
-<div class="ulist"><ul>
-<li>
-<p>
-<em>Mailing List</em>. El buzón de correo de <em>Subsurface</em>. El usuario enviar mails a
- la lista de correo de <em>Subsurface</em>.
-</p>
-</li>
-<li>
-<p>
-<em>Subsurface website</em>. Un link a la URL de la página de <em>Subsurface</em>.
-</p>
-</li>
-<li>
-<p>
-<em>Version</em>. Muestra la versión actual de la app Companion.
-</p>
-</li>
-</ul></div>
-</div>
-<div class="sect4">
-<h5 id="_search">Search</h5>
-<div class="paragraph"><p>Se utiliza para buscar en las ubicaciones de buceo guardadas, por nombre o por
-fecha y hora.</p></div>
-</div>
-<div class="sect4">
-<h5 id="_start_service">Start service</h5>
-<div class="paragraph"><p>Inicia el servicio en segundo plano siguiendo los ajustes previamente definidos.</p></div>
-</div>
-<div class="sect4">
-<h5 id="_disconnect">Disconnect</h5>
-<div class="paragraph"><p>Esta opción está mal nombrada. "Desconecta" la app del servidor reseteando el
-DIVERID en la app, y retorna a la primera pantalla desde la que se puede crear
-una cuenta, reactivar el DIVERID o volver a poner el del usuario. Desconectar
-puede ser útil si se desea descargar a un dispositivo android posiciones de otro
-buceador registrado o enviar la posición actual al servidor con el ID de otro
-buceador registrado.</p></div>
-</div>
-<div class="sect4">
-<h5 id="_send_all_locations">Send all locations</h5>
-<div class="paragraph"><p>Esta opción envía todas las posiciones guardadas en el dispositivo android al
-servidor.</p></div>
-</div>
-</div>
-<div class="sect3">
-<h4 id="S_iphone">5.4.7. Usar la app Subsurface companion en un <em>iPhone</em> para registra puntos de buceo</h4>
-<div class="paragraph"><p>El interfaz de iPhone es bastante simple. Se necesita introducir la ID de
-usuario (obtenida durante el registro) en el espacio reservado para ello, luego
-seleccionar "Dive in" (ver parte izquierda de la imágen de abajo) y se empieza
-a recoger información de las ubicaciones.</p></div>
-<div class="imageblock" style="text-align:center;">
-<div class="content">
-<img src="images/iphone.jpg" alt="FIGURE: Usiar la aplicación iPhone companion" width="640" />
-</div>
-</div>
-<div class="paragraph"><p>Las inmersiones se pueden añadir de forma automática o manual. En modo manual,
-se añade una sola ubicación de buceo o "waypoint" al flujo de entrada de datos
-del GPS. En modo automático se crea una traza continua de posiciones GPS de las
-cuales, posteriormente, después de haberse importado, <em>Subsurface</em> puede
-seleccionar las posiciones correctas en base a las horas de los buceos. El modo
-por defecto para el <em>iPhone</em> es el automático. Cuando se añade una inmersión,
-el servicio de posicionamiento se inicia automáticamente y aparece una barra
-roja en la parte de abajo de la pantalla. Tras el buceo, se puede hacer clic en
-la barra roja para detener el servicio de posicionamiento. Mientras el servicio
-se está ejecutando, solo se pueden añadir inmersiones usando el mecanismo
-manual.</p></div>
-<div class="paragraph"><p>Se puede editar el nombre del punto de buceo posteriormente, seleccionando la
-inmersión de la lista y clicando en el nombre. No hay otros campos editables.
-La lista se sube automáticamente desde el <em>iPhone</em> al servicio web y no hay
-opción a hacerlo manualmente.</p></div>
-</div>
-<div class="sect3">
-<h4 id="_descargar_ubicaciones_de_buceo_al_diario_en_em_subsurface_em">5.4.8. Descargar ubicaciones de buceo al diario en <em>Subsurface</em></h4>
-<div class="paragraph"><p>Hay que descargar a <em>Subsurface</em> las inmersiones del ordenador de buceo, o
-crearlas manualmente, antes de obtener las coordenadas del servifor. El diálogo
-de descarga se puede obtener vía <em>Ctrl+G</em> o desde el menú principal de
-<em>Subsurface</em>, <em>Importar → Importar datos GPS del servicio Subsurface</em>,
-resultando la imagen de abajo a la izquierda (A). La primera vez que se use, el
-campo DIVERID estará en blanco. Introducir el DIVERID. Después se pulsa el botón
-Descargar y comenzará la descarga, tras lo cual aparece la pantalla de abajo a
-la derecha (<strong>B</strong>):</p></div>
-<div class="imageblock" style="text-align:center;">
-<div class="content">
-<img src="images/DownloadGPS.jpg" alt="[FIGURE: Descargar datos GPS de la app Companion]" />
-</div>
-</div>
-<div class="paragraph"><p>Nótese que ahora está activo el botón <em>Aplicar</em>. Pulsarlo para actualizar las
-inmersiones recién creadas o descargadas a <em>Subsurface</em>, lo cual aplicará las
-coordenadas y los nombres que se hayan dado en la app en todas las inmersiones
-en las que coincidan las fechas y las horas de las posiciones GPS descargadas.
-Si se ha introducido en <em>Subsurface</em> el nombre del punto de buceo antes de
-descargar las coordenadas GPS, este nombre tendrá preferencia sobre los
-descargados.</p></div>
-<div class="paragraph"><p>Ya que <em>Subsurface</em> busca coincidencias entre las localizaciones GPS del
-dispositivo android y la información del ordenador de buceo basándose en la
-fecha y la hora, la asignación automática depende de la coincidencia entre los
-datos de ambos dispositivos. Aunque <em>Subsurface</em> tiene un margen de tolerancia
-muy amplio, puede ser incapaz de identificar la inmersión correcta, si hay mucha
-diferencia entre la hora del ordenador de buceo y la del dispositivo android,
-resultando en que no haya actualización.</p></div>
-<div class="paragraph"><p>Fechas y horas similares en los dispositivos no siempre son posibles y puede
-haber muchas razones para ello (p.e. zonas horarias), o <em>Subsurface</em> puede ser
-incapaz de decidir cual es la posición correcta de una inmersión (p.e. en
-inmersiones repetitivas mientras se ejecuta el servicio en 2º plano puede haber
-varios puntos incluidos en el rango de tiempo que casen no solo para la primera
-inmersión, sino también para las siguientes). Una solución alternativa para esta
-situación sería editar manualmente la hora en la lista de inmersiones de
-<em>Subsurface</em> <strong>antes</strong> de descargar los datos GPS, para hacerla coincidir con la
-de estos, y luego volver a cambiarla a la correcta <strong>después</strong> de la descarga.</p></div>
-<div class="admonitionblock">
-<table><tr>
-<td class="icon">
-<img src="images/icons/info.jpg" alt="Note" />
-</td>
-<td class="content">SUGERENCIAS:</td>
-</tr></table>
-</div>
-<div class="ulist"><ul>
-<li>
-<p>
-El servicio en segundo plano es una herramienta poderosa, pero puede llenar la
- lista de localizaciones con muchas posiciones innecesarias que no correspondan a
- los puntos exactos de buceo, sino a la ruta seguida por el barco. Actualmente,
- borrar estas posiciones del servidor resulta difícil. En algunas situaciones
- resulta, pues, prudente limpiar la lista del dispositivo android antes de enviar
- los puntos al servidor simplemente borrando los que no sean correctos. Esto
- puede ser necesario, por ejemplo, si se desea mantener limpia la lista de
- ubicaciones para poder visualizarlas en el mapa del servidor o del dispositivo
- android.
-</p>
-</li>
-<li>
-<p>
-También tendría sentido proporcionar nombres significativos a las
- localizaciones enviadas al servidor o, al menos, usar tal nombre en el ajuste
- <em>Name Template</em> si se va a ejecutar el background service, especialmente durante
- los viajes de buceo con muchas inmersiones y puntos de buceo.
-</p>
-</li>
-</ul></div>
-</div>
-</div>
-</div>
-</div>
-<div class="sect1">
-<h2 id="S_LoadImage">6. El cargador de fotografías de <em>Subsurface</em></h2>
-<div class="sectionbody">
-<div class="paragraph"><p>Muchos buceadores (si no la mayoría) llevan consigo una cámara y toman
-fotografías durante sus inmersiones. Sería interesante poder asociar cada
-fotografía con una inmersión concreta. <em>Subsurface</em> nos permite cargar fotos en
-una inmersión. Las fotos se superponen en el perfil de la inmersión, desde donde
-pueden visualizarse.</p></div>
-<div class="sect2">
-<h3 id="_cargar_fotos_y_sincronizar_la_camara_con_el_ordenador_de_buceo">6.1. Cargar fotos y sincronizar la cámara con el ordenador de buceo</h3>
-<div class="paragraph"><p>Se selecciona una inmersión o un grupo de ellas en la lista. Luego se hace
-clic-derecho en la selección y se elige la opción <em>Carga imagenes</em>:</p></div>
-<div class="imageblock" style="text-align:center;">
-<div class="content">
-<img src="images/LoadImage1_f20.jpg" alt="FIGURA: Opción de carga de imágenes" />
-</div>
-</div>
-<div class="paragraph"><p>Aparecerá el navegador de archivos del sistema. Se selecciona la carpeta y las
-fotografías que se necesitan cargar en <em>Subsurface</em> y se hace clic en el botón
-<em>Abrir</em>.</p></div>
-<div class="imageblock" style="text-align:center;">
-<div class="content">
-<img src="images/LoadImage2_f20.jpg" alt="FIGURA: Opción de carga de imágenes" />
-</div>
-</div>
-<div class="paragraph"><p>Esto desplegará el diálogo de sincronización que se muestra a continuación. El
-problema crítico es que la sincronización horaria entre la cámara y el ordenador
-de buceo no sea perfecta, en ocasiones difieren varios minutos. Si <em>Subsurface</em>
-puede sincronizarlos, entonces puede utilizar las horas de las fotografías para
-posicionarlas en el perfil de la inmersión.</p></div>
-<div class="paragraph"><p><em>Subsurface</em> puede conseguir esta sincronización de tres maneras:</p></div>
-<div class="ulist"><ul>
-<li>
-<p>
-<strong>Proactivamente</strong>: Antes de la inmersión, asegúrate de que los ajustes de la
- cámara coinciden con los del ordenador de buceo, cambiándolo en uno de los
- dispositivos o en ambos.
-</p>
-</li>
-<li>
-<p>
-<strong>Manualmente</strong>: Si el usuario anotó la hora exacta de la cámara al inicio de la
- inmersión, se puede obtener la diferencia de tiempo entre los dos dispositivos.
- En realidad, si no se han variado los ajustes horarios, se pueden conseguir tras
- la inmersión o, incluso, al final del día. Entonces se puede indicar manualmente
- la diferencia en el diálogo de <em>Desplazamiento horario</em>. En la parte de arriba
- del diálogo hay una herramienta para indicar tiempos, evidente en la figura <strong>A</strong>
- a continuación. Si la cámara lleva un adelanto de 7 minutos sobre el ordenador
- de buceo, fijamos en la herramienta un valor de 00:07. Se ignora cualquier
- sufijo "AM" o "PM". Seleccionamos el botón <em>OK</em> y se habrá obtenido la
- sincronización. Hay que marcar <em>Más pronto</em> o <em>Más tarde</em> según corresponda. En
- el ejemplo a continuación, la opción <em>Más pronto</em> es la correcta ya que la
- cámara de fotos va 7 minutos por delante del ordenador de buceo.
-</p>
-</li>
-</ul></div>
-<div class="imageblock" style="text-align:center;">
-<div class="content">
-<img src="images//LoadImage3b_f20.jpg" alt="FIGURA: Diálogo de sincronización" />
-</div>
-</div>
-<div class="ulist"><ul>
-<li>
-<p>
-<strong>Por fotografía</strong>: Hay una forma muy cómoda de conseguir sincronización. Si se
- toma una foto de la pantalla del ordenador mostrando la hora, <em>Subsurface</em> puede
- obtener la hora exacta a la que se tomó la foto usando los metadatos que la
- cámara guarda en cada foto. Para ello se utiliza la mitad inferior del diálogo
- <em>Desplazamiento horario</em>. Si se selecciona la barra horizontal titulada
- "<em>Selecciona la imagen del ordenador de buceo mostrando la hora</em>", aparece un
- navegador de archivos. Se selecciona la fotografía y se pulsa <em>Abrir</em>. La foto
- del ordenador de buceo aparecerá en el recuadro inferior del diálogo.
- <em>Subsurface</em> sabe exactamente cuando se tomó la foto. Ajusta la fecha y hora en
- el diálogo a la izquierda de la foto para que refleje los de la pantalla del
- ordenador. Tras el ajuste <em>Subsurface</em> conoce exactamente cual es la diferencia
- entre cámara y ordenador y se podrán sincronizar. La figura anterior muestra una
- fotografía del ordenador de buceo y la herramienta de tiempo ajustada a la fecha
- y hora de la imagen <strong>B</strong> anterior.
-</p>
-</li>
-</ul></div>
-<div class="paragraph"><p>Si la hora de la foto es muy anterior o posterior al buceo, no se sitúa sobre el
-perfil de la inmersión. Si está en un rango de 30 minutos, sí se muestra.</p></div>
-</div>
-<div class="sect2">
-<h3 id="_visualizar_las_imagenes">6.2. Visualizar las imágenes</h3>
-<div class="paragraph"><p>Después que las imágenes han sido cargadas aparecen en dos lugares:</p></div>
-<div class="ulist"><ul>
-<li>
-<p>
-La pestaña <em>Fotos</em> del panel <em>Notas</em>.
-</p>
-</li>
-<li>
-<p>
-Como pequeños iconos (chinchetas) sobre el perfil de inmersión, en posiciones
- que relejan la hora en que se tomó cada fotografía. Para ver las fotos sobre el
- perfil, activa el botón <em>Mostrar fotos</em> a la izquierda del perfil:
-</p>
-</li>
-</ul></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>Esto producirá un perfil como el que se muestra a continuación</p></div>
-<div class="imageblock" style="text-align:center;">
-<div class="content">
-<img src="images/LoadImage4_f20.jpg" alt="FIGURA: Fotos sobre un perfil de inmersión" />
-</div>
-</div>
-<div class="paragraph"><p>Si se sitúa el ratón sobre uno de los iconos, se mostrará una versión reducida
-de la foto. Ver imagen a continuación:</p></div>
-<div class="imageblock" style="text-align:center;">
-<div class="content">
-<img src="images/LoadImage5_f20.jpg" alt="FIGURA: Foto reducida sobre perfil de inmersión" />
-</div>
-</div>
-<div class="paragraph"><p>Si hacemos clic sobre la imagen reducida aparecerá la fotografía a tamaño
-completo sobre la ventana de <em>Subsurface</em>. Esto permite una buena visión de las
-fotos que han sido importadas. Ver imagen a continuación.
-Cada imagen reducida tiene una pequeña papelera en su esquina superior
-izquierda (ver imagen anterior). Si se selecciona la papelera, la foto se
-borra de la inmersión, así pues, hay que tener un poco de cuidado al clicar
-sobre las imágenes. Las imágenes también puede borrase desde la pestaña <em>Fotos</em>
-(ver en el siguiente punto).</p></div>
-<div class="imageblock" style="text-align:center;">
-<div class="content">
-<img src="images/LoadImage6_f20.jpg" alt="FIGURA: Foto a pantalla completa sobre el perfil de inmersión" />
-</div>
-</div>
-<div class="sect3">
-<h4 id="_la_pestana_em_fotos_em">6.2.1. La pestaña <em>Fotos</em></h4>
-<div class="paragraph"><p>Las fotografías asociadas a una inmersión se muestran como miniaturas en la
-pestaña <em>Fotos</em> del <em>Panel de inmersión</em>. Se puede acceder con facilidad a las
-fotos hechas en rápida sucesión durante la inmersión, desde la pestaña <em>Fotos</em>.
-Esta pestaña es una herramienta para acceder individualmente a las fotos de un
-buceo, mientras que las "chinchetas" en el perfil de inmersión proporcionan una
-indicación de cuando se tomó la foto. Clicando una sola vez sobre una de la
-miniaturas de la pestaña <em>Fotos</em>, seleccionamos una foto. Haciendo doble-clic
-sobre una miniatura, se muestra la imagen a tamaño completo superpuesta a la
-ventana de <em>Subsurface</em>. Podemos borrar una foto desde la pestaña <em>Fotos</em>
-seleccionándola (un solo clic) y pulsando a continuación la tecla <em>Supr</em> en el
-teclado. Esto eliminará la foto tanto de la pestaña <em>Fotos</em> como del <em>Perfil de
-la inmersión</em>.</p></div>
-</div>
-<div class="sect3">
-<h4 id="_fotos_en_disco_duro_externo">6.2.2. Fotos en disco duro externo</h4>
-<div class="paragraph"><p>La mayoría de fotosubs guardan sus fotografías en un disco duro externo. Si este
-disco puede mapearse (como es casi siempre el caso) <em>Subsurface</em> puede acceder
-directamente a las fotos. Esto facilita la interacción entre <em>Subsurface</em> y un
-repositorio externo de fotos. Cuando se asocia un perfil de inmersión con fotos
-de un disco externo se utiliza el procedimiento normal de selección
-y sincronización (ver en el texto anterior). Sin embargo, después de que el
-disco externo haya sido desconectado, <em>Subsurface ya no podrá acceder a las
-fotos. Si se ha activado la visualización de fotos sobre el perfil (utilizando
-la barra de herramientas a la izquierda del perfil), el programa solo mostrará
-unos pequeños puntos blancos donde deberían mostrarse las fotos. Además, la
-pestaña _Fotos</em> solo mostrará los nombres de los archivos de las imágenes. Este
-es el funcionamiento normal. Si, posteriormente, el disco externo con las fotos
-se vuelve a conectar, las fotos se visualizarán normalmente.</p></div>
-</div>
-<div class="sect3">
-<h4 id="S_FindMovedImages">6.2.3. Mover fotografías entre directorios, discos duros u ordenadores</h4>
-<div class="paragraph"><p>Tras haber cargado una fotografía en <em>subsurface</em> y haberla asociado a un buceo
-determinado, se archiva el directorio donde la foto permanece guardada, para poder
-encontrarla cuando se vuelva a abrir la inmersión. Si la foto o la colección
-completa de fotos se trasladan a otro disco o a una máquina distinta, sería
-bastante raro que la estructura de directorios fuera idéntica a la de la fotografía
-cargada originalmente. Cuando esto sucede, <em>Subsurface</em> busca las fotos en el
-directorio original desde el que fueron cargadas, no las encuentra y, por tanto,
-no las puede mostrar. Ya que, después de mover fotos, un gran número puede
-necesitar borrarse y reimportarse desde la nueva localización, <em>Subsurface</em>
-tiene un mecanismo que facilita el proceso de actualizar la información del
-directorio para cada foto: actualizaciones automáticas utilizando huellas.</p></div>
-<div class="paragraph"><p>Cuando se carga una foto en <em>Subsurface</em>, se calcula una huella para la imagen
-y se guarda con la otra información de referencia para la foto. Tras mover una
-colección de fotos (que ya ha sido cargada en <em>Subsurface</em>) a un directorio,
-disco u ordenador diferente, <em>Subsurface</em> puede llevar a cabo los siguientes
-pasos:</p></div>
-<div class="ulist"><ul>
-<li>
-<p>
-Buscar en un directorio concreto (y todos sus subdireectorios recursivamente)
-al que se han llevado las fotos.
-</p>
-</li>
-<li>
-<p>
-Calcular huellas para todas las fotos de este directorio, y
-</p>
-</li>
-<li>
-<p>
-si hay coincidencia entre una de las huellas calculadas y la que se calculó
-al cargar la foto en <em>Subsurface</em> (incluso si el nombre del archivo hubiera
-cambiado), actualizar automáticamente la información de directorio, de foma que
-<em>Subsurface</em> pueda encontrar la foto en el nuevo directorio.
-</p>
-</li>
-</ul></div>
-<div class="paragraph"><p>Esto se consigue seleccionando desde el Menú Principal: <em>Archivo → Encontrar
-imágenes desplazadas</em>. Esto presenta una ventana en la cual es necesario
-especificar el NUEVO directorio de las fotos. Se selecciona el directorio
-apropiado y se clica el botón <em>Escanear</em> en la parte inferior derecha del
-panel. El proceso puede requerir varios minutos para completarse, tras lo
-cual <em>Subsurface</em> mostrará las fotos correctas cuando se abra un buceo.</p></div>
-<div class="sidebarblock" id="Image_fingerprint_upgrade">
-<div class="content">
-<div class="paragraph"><p><strong>Actualizar colecciones de fotos existentes sin huella</strong></p></div>
-<div class="admonitionblock">
-<table><tr>
-<td class="icon">
-<img src="images/icons/important.png" alt="Important" />
-</td>
-<td class="content"><em>Subsurface</em> calcula automáticamente huellas para todas las imágenes a las
-que tiene acceso. Cuando manipules estas imágenes, asegúrate de que todas las
-imágenes asociadas al divelog queden accesibles. <em>Subsurface</em>, automáticamente
-comprueba y actualiza (en caso necesario) las huellas asociadas a cada buceo
-si:
-- Las imágenes asociadas a ese buceo son visibles como miniaturas en el perfil.
-- Se edita cualquier cosa en el panel <strong>Notas</strong> y se guardan las modificaciones
-con <em>Guardar cambios</em>.</td>
-</tr></table>
-</div>
-</div></div>
-</div>
-</div>
-<div class="sect2">
-<h3 id="_registrar_tipos_de_inmersion_especiales">6.3. Registrar tipos de inmersión especiales</h3>
-<div class="sect3">
-<h4 id="S_MulticylinderDives">6.3.1. Inmersiones multi botella</h4>
-<div class="paragraph"><p><em>Subsurface</em> maneja fácilmente inmersiones que requieren más de una botella. El
-buceo multi botella se produce habitualmente cuando (a) un buceador no tiene
-bastante gas para completar una inmersión con una sola botella o (b) cuando el
-buceador necesita más de una mezcla de gas a causa de la profundidad o de las
-necesidades descompresivas de la inmersión. Por este motivo, las inmersiones
-multi tanque son empleadas a menudo por los buceadores técnicos ya que bucean
-profundo y durante mucho tiempo. En lo que corresponde a <em>Subsurface</em>, solo hay
-dos clases de información que necesitan proporcionarse:</p></div>
-<div class="ulist"><ul>
-<li>
-<p>
-<strong>Describir las botellas usadas durante el buceo</strong>. Esto se hace en la pestaña
- <strong>Equipo</strong> del panel <strong>Información</strong> tal como <a href="#cylinder_definitions">se describe anteriormente</a>.
- se introducen las botellas una a una, especificando las características de la
- botella y la composición del gas de cada una de ellas.
-</p>
-</li>
-<li>
-<p>
-<strong>Registrar los momentos en que se cambia de una botella a otra</strong>. Esta es una
- información que facilitan algunos ordenadores (siempre y cuando el buceador
- se la diga al ordenador durante el buceo). Si el ordenador no la proporciona,
- el buceador necesita registrarla usando un método diferente, p.e. en una
- pizarra.
-</p>
-</li>
-<li>
-<p>
-<strong>Indica los cambios de botella en el perfil</strong>. Si se utilizó la última opción,
- el buceador ha de indicar el evento de cambio de gas haciendo clic derecho en
- el momento adecuado del panel <strong>Perfil de inmersión</strong> y señalar la botella a la
- que se cambió. Tras hacer clic derecho, seguir el menú contextual a "Añadir
- cambio de gas" y seleccionar la botella apropiada entre las definidas en el
- primer paso (ver imagen a continuación). Si el botón <strong>Barra de botellas</strong> de
- la barra de herramientas se ha activado, los cambios también se indicarán en
- la barra.
-</p>
-</li>
-</ul></div>
-<div class="paragraph"><p>Habiendo llevado a cabo estas tareas, <em>Subsurface</em> indica en el perfil de buceo
-el uso de diferentes botellas. A continuación, una inmersión multi botella que
-empieza con EAN28, se cambia a EAN50 despues de 26 minutos para efectuar la
-deco.</p></div>
-<div class="imageblock" style="text-align:center;">
-<div class="content">
-<img src="images/multicylinder_dive.jpg" alt="FIGURa: Perfil multi tanque" />
-</div>
-</div>
-</div>
-<div class="sect3">
-<h4 id="_inmersiones_en_montaje_lateral_sidemount">6.3.2. Inmersiones en montaje lateral (sidemount)</h4>
-<div class="paragraph"><p>El buceo en montaje lateral es solo otra forma de buceo multi tanque, a menudo
-con ambas o todas las botellas conteniendo la misma mezcla. Aunque es una
-configuración popular entre los espeleo buceadores, el buceo en lateral se
-puede efectuar por buceadores recreativos que hayan completado el entrenamiento
-adecuado. Registrar inmersiones en sidemount se hace en tres pasos:</p></div>
-<div class="ulist"><ul>
-<li>
-<p>
-*Durante el buceo, se registran los eventos de cambio de botella". Ya que bucear
- en lateral supone, normalmente, usar 2 botellas con aire o con la misma mezcla,
- <em>Subsurface</em> distingue entre estas botellas. En comparación, la mayoría de
- ordenadores de buceo que contemplan cambios de gas solo distinguen entre
- diferentes <em>gases</em> usados, no entre diferentes <em>botellas</em> usadas. Esto supone
- que, cuando se descargan inmersiones en sidemount desde estos ordenadores, los
- eventos de cambio entre las diferentes botellas no se descargan. Esto puede
- suponer que se tenga que guardar un registro manual de cambios de botella o
- (si el ordenador tiene esta posibilidad) marcando cada cambio de botella con
- una marca que se pueda descargar posteriormente. Regresar de una inmersión
- en lateral con la información de cambios de botella es la única parte con
- truco en cuanto a registrar buceos en sidemount.
-</p>
-</li>
-<li>
-<p>
-<strong>En <em>Subsurface</em> detalla las botellas usadas en la inmersión</strong>. El usuario
- registra las especificaciones para las diferentes botellas usando la pestaña
- <strong>Equipo</strong> del <strong>Panel de información</strong> (véase imagen a continuación en la que se
- usó una botella de 12 litros).
-</p>
-</li>
-<li>
-<p>
-<strong>Indicar eventos de cambio de botella sobre el perfil de <em>Subsurface</em></strong>. Una
- vez que se ha importado la inmersión desde el ordenador de buceo, es necesario
- indicar los eventos de cambio de botella sobre el perfil. Los cambios se
- anotan haciendo clic-derecho en el punto correspondiente del perfil y entonces
- seleccionando <em>Añadir cambio de gas</em>. Se muestra una lista de las botellas con
- la que se está utilizando en gris. En la imagen a continuación, Tank 1 está en
- gris, permitiendo solo la selección de Tank 2. Tras seleccionar la botella
- correspondiente el cambio se indicará sobre el perfil con un icono de una
- botella. Si está activada la <strong>Barra de botellas</strong> también se indicará el cambio
- sobre ella (ver imagen a continuación). Una vez que todos los cambios de
- botella han sido registrados sobre el perfil, las presiones correctas de ambas
- botellas se mostrarán en el perfil, como en la imagen de ejemplo.
-</p>
-</li>
-</ul></div>
-<div class="imageblock" style="text-align:center;">
-<div class="content">
-<img src="images/sidemount1.jpg" alt="FIGURE: Sidemount profile" />
-</div>
-</div>
-<div class="paragraph"><p>Esta sección es un ejemplo de la versatilidad de <em>Subsurface</em> como herramienta
-de registro de inmersiones.</p></div>
-</div>
-<div class="sect3">
-<h4 id="S_sSCR_dives">6.3.3. Inmersiones con rebreather de circuito semi cerrado (SCR)</h4>
-<div class="admonitionblock">
-<table><tr>
-<td class="icon">
-<img src="images/halcyon_RB80.jpg" alt="Note" />
-</td>
-<td class="content">Los rebreathers semi cerrados pasivos (pSCR) suponen un avance técnico en el
-equipo de buceo que recircula el gas que el buzo respira, y elimina el dióxido
-de carbono del gas exhalado. Al tiempo que una pequeña cantidad del gas exhalado
-(habitualmente una décima parte) se libera en el agua, una pequeña cantidad de
-gas de la botella se introduce en el circuito (habitualmente nitrox). Un buzo
-usando una sola botella de gas puede, pues, bucear durante periodos de tiempo
-mucho mayores que utilizando una configuración recreativa de circuito abierto.
-Con los pSCR una cantidad muy pequeña de gas se libera cada vez que el buzo
-inhala. Con los equipos SCR activos (aSCR), en cambio, una pequeña cantidad del
-gas respirado se libera continuamente.</td>
-</tr></table>
-</div>
-<div class="paragraph"><p>Para registrar inmersiones con pSCR, no se requieren procedimientos especiales,
-solo los pasos normales descritos con anterioridad:</p></div>
-<div class="ulist"><ul>
-<li>
-<p>
-Seleccionar el modo pSCR en el desplegable <em>Modo de inmersión</em> en el panel
- <strong>Información</strong>.
-</p>
-</li>
-<li>
-<p>
-El buceo con pSCR, a menudo, requiere cambios de gas, necesitando una botella
- adicional. Hay, pues, que describir todas las botellas como se indicó con
- anterioridad e indicar los cambios de botella/gas como se explicó en la
- sección <a href="#S_MulticylinderDives">Inmersiones multi botella</a>.
-</p>
-</li>
-</ul></div>
-<div class="paragraph"><p>Si se ha seleccionado pSCR en el <em>Modo de inmersión</em>, el techo de buceo para
-inmersiones pSCR se ajusta para la caída de oxígeno a través de la boquilla
-que, a menudo, requiere mayores períodos de descompresión. A continuación un
-perfil de inmersión de un buceo con pSCR usando EAN36 como gas de fondo y
-oxígeno para la descompresión. Fíjate que la inmersión duró unas dos horas.</p></div>
-<div class="imageblock" style="text-align:center;">
-<div class="content">
-<img src="images/pSCR_profile.jpg" alt="FIGURA: Perfil pSCR" />
-</div>
-</div>
-</div>
-<div class="sect3">
-<h4 id="S_CCR_dives">6.3.4. Inmersiones con rebreather de circuito cerrado (CCR)</h4>
-<div class="admonitionblock">
-<table><tr>
-<td class="icon">
-<img src="images/APD.jpg" alt="Note" />
-</td>
-<td class="content">Los rebreathers de circuito cerrado utilizan tecnología avanzada para
-reciclar el gas que se ha respirado, mientras mantienen una concentración de
-oxígeno respirable llevando a cabo dos acciones:
-a) Eliminan dióxido de carbono del gas que se ha exhalado.
-b) Regulan la concentración de oxígeno para que permanezca en los límites.
-La interfaz CCR de <em>Subsurface</em> es experimental actualmente y se halla bajo
-desarrollo activo. <em>Subsurface</em> soporta en estos momentos el Poseidon MKVI y
-los PD Discovery/Evolution En contraste con un ordenador
-de buceo recreativo convencional, el ordenador de un sistema CCR no permite
-descargar un diario que contenga múltiples inmersiones. En su lugar, cada buceo
-se guarda independientemente. Esto significa que <em>SUbsurface</em> no puede descargar
-el diario directamente desde un CCR, sino que lo importa de la misma manera que
-se importan datos de otras bases de datos digitales, una inmersión cada vez.</td>
-</tr></table>
-</div>
-</div>
-<div class="sect3">
-<h4 id="_importar_una_inmersion_con_ccr">6.3.5. Importar una inmersión con CCR</h4>
-<div class="paragraph"><p>Véase la sección que trata de <a href="#S_ImportingAlienDiveLogs">Importar información de buceo de otras fuentes digitales</a>.
-Desde el menú principal de <em>Subsurface</em>, seleccionar <em>Import → Importar archivos
-de registro</em> para desplegar el <a href="#Unified_import">Diálogo de importación universal</a>.
-Como se explicaba en esa sección, en la parte de abajo a la derecha hay una lista
-desplegable (etiquetada como <em>Filtro:</em>) de dispositivos que incluye los archivos del
-(Poseidon) MKVI o APD (la funcionalidad para otros dispositivos CCR está en desarrollo
-actualmente). Tras haber seleccionado el dispositivo y el directorio donde se
-hallan los archivos originales del ordenador CCR, se puede seleccionar un
-archivo concreto (en el caso del MKVI es un archivo con extensión .txt). Tras
-seleccionar el archivo, activar el botón <em>Abrir</em> de abajo a la derecha. Lee la
-sección a continuación para:</p></div>
-</div>
-<div class="sect3">
-<h4 id="_informacion_mostrada_para_un_buceo_con_ccr">6.3.6. Información mostrada para un buceo con CCR</h4>
-<div class="paragraph"><p><em>Presiones parciales de los gases</em>: El gráfico de presión parcial de oxígeno
-muestra la información de los sensores de oxígeno del equipo CCR. A diferencia
-del equipo de circuito abierto (donde los valores de pO<sub>2</sub> se calculan en base
-a la composición del gas y la profundidad), los equipos CCR proporcionan
-mediciones instantáneas de pO<sub>2</sub>, a partir de sensores de oxígeno. En este
-caso el gráfico de presión parcial de oxígeno debería se bastante plano,
-reflejando el ajuste del setpoint durante la inmersión. La pO<sub>2</sub> media no es
-la media de presiones parciales de oxígeno que facilita el equipo CCR, sino
-un valor calculado por <em>Subsurface</em> de la siguiente forma:</p></div>
-<div class="ulist"><ul>
-<li>
-<p>
-Para DOS sensores de O<sub>2</sub> se da en valor medio de ambos sensores.
-</p>
-</li>
-<li>
-<p>
-Para sistemas de TRES sensores (p.e. APD), también se usa la media. Sin
- embargo las lecturas simultaneas de diferentes sensores con diferencias de
- más de 0,1 bar, se consideran falsas y se ignoran.
-</p>
-</li>
-</ul></div>
-<div class="paragraph"><p>La pO<sub>2</sub> media de los sensores se indica con una línea verde.</p></div>
-<div class="paragraph"><p>El valor del setpoint así como las lecturas de de los sensores de oxígeno
-individuales puede mostrarse. La presentación en pantalla de información CCR
-adicional se activa seleccionando las opciones adecuadas en el panel <em>Preferencias</em>
-(accesible seleccionando <a href="#S_CCR_options"><em>Archivo → Preferencias → Gráfico</em></a>).
-Esta parte del panel <em>Preferencias</em>, mostrada en la siguiente imagen, se
-presenta como dos casillas seleccionables que modifican la presentación de la
-pO<sub>2</sub> cuando se halla activada la opción correspondiente de la barra de herramientas
-del Perfil de Inmersión.</p></div>
-<div class="imageblock" style="text-align:center;">
-<div class="content">
-<img src="images/CCR_preferences_f20.jpg" alt="FIGURA: Panel de preferencias de CCR" />
-</div>
-</div>
-<div class="paragraph"><p>Clicar cualquiera de las casillas seleccionables permite mostrar información
-adicional relativa al oxígeno, siempre que el botón pO<sub>2</sub> de la barra de
-herramientas del panel <em>Perfil</em> esté activado.</p></div>
-<div class="paragraph"><p>La primera casilla permite mostrar información del setpoint. Esta es una línea
-roja superpuesta al gráfico verde de presión parcial de oxígeno y permite
-comparar la media de presiones parciales de oxígeno medidas, frente al valor
-del setpoint, como se muestra a continuación.</p></div>
-<div class="paragraph"><p>image::images/CCR_setpoint_f20.jpg"FIGURA: Gráfico de pO2 y setpoint del CCR",align="center"]</p></div>
-<div class="paragraph"><p>La segunda casilla permite mostrar datos de cada sensor de oxígeno individual
-del equipo CCR. Los datos de cada sensor se colorean de la siguiente forma:</p></div>
-<div class="ulist"><ul>
-<li>
-<p>
-Sensor 1: gris
-</p>
-</li>
-<li>
-<p>
-Sensor 2: azul
-</p>
-</li>
-<li>
-<p>
-Sensor 3: marrón
-</p>
-</li>
-</ul></div>
-<div class="paragraph"><p>La media de pO<sub>2</sub> se indica por la línea verde. Así se pueden comparar los
-datos de cada uno de los sensores de oxígeno, lo cual es útil para detectar
-lecturas erráticas o anormalmente bajas de un sensor en particular.</p></div>
-<div class="imageblock" style="text-align:center;">
-<div class="content">
-<img src="images/CCR_sensor_data_f20.jpg" alt="FIGURA: Gráfico de datos de los sensores del CCR" />
-</div>
-</div>
-<div class="paragraph"><p>El dato del setpoint puede ser superpuesto sobre los datos de los sensores de
-oxígeno activando ambas casillas. Las presiones parciales del nitrógeno y del
-helio (en su caso) se muestran de la forma habitual para las inmersiones OC.</p></div>
-<div class="paragraph"><p><em>Eventos</em>: Se registran diversos eventos, p.e. los cambios a circuito abierto
-de la boquilla. Estos eventos se muestran como triángulos amarillos y, si se
-pasa el ratón sobre el icono, se da una descripción del evento en la línea
-inferior del <a href="#S_InfoBox">Recuadro de información</a>.</p></div>
-<div class="paragraph"><p><em>Presiones de las botellas</em>: Algunos ordenadores de buceo CCR, como el MKVI de
-Poseidon, registran las presiones de las botellas de oxígeno y diluyente. Las
-presiones de estas dos botellas se muestran como líneas verdes sobre el perfil
-de la inmersión. Además, las presiones iniciales y finales de ambas botellas se
-muestran en la pestaña <em>Equipo</em>. A continuación, un perfil de inmersión con CCR
-incluyendo capas con el setpoint, las lecturas de los sensores de oxígeno y la
-información de presión de las botellas. En este caso hay una buena coincidencia
-entre las lecturas de los dos sensores de oxígeno.</p></div>
-<div class="imageblock" style="text-align:center;">
-<div class="content">
-<img src="images/CCR_dive_profile_f22.jpg" alt="FIGURA: Perfil de inmersión con CCR" />
-</div>
-</div>
-<div class="paragraph"><p><em>Información especifica del equipo</em>: <em>Subsurface</em> recoge información que puede
-ser especifica de un tipo de equipo concreto. Se muestra en la <a href="#S_ExtraDataTab">pestaña Otros Datos</a>.
-Puede incluir información de ajustes o metadatos sobre la inmersión.</p></div>
-<div class="paragraph"><p>El techo calculado por <em>Subsurface</em> no es muy preciso dado que no se puede
-determinar fiablemente la presión de nitrógeno en el circuito desde el divelog
-importado del equipo del CCR. Muchos ordenadores de buceo CCR, sin embargo,
-informan del techo calculado internamente por ellos mismos y este se mostrará
-en el perfil activando el botón correspondiente a la izquierda del perfil:</p></div>
-<div class="imageblock">
-<div class="content">
-<img src="images/icons/cceiling.jpg" alt="Icono de techo" />
-</div>
-</div>
-<div class="paragraph"><p>El color por defecto del techo de deco generado por el ordenador es blanco. Sin
-embargo, puede ajustarse a rojo seleccionando la correspondiente casilla en
-<em>Archivo → Preferencias → Gráfico</em>. A continuación se muestra un perfil
-mostrando el techo deco generado por el ordenador de buceo:</p></div>
-<div class="imageblock">
-<div class="content">
-<img src="images/CCR_dive_ceilingF22.jpg" alt="FIGURA: Perfil de inmersión con CCR" />
-</div>
-</div>
-<div class="paragraph"><p>Se puede encontrar más información, específica para cada ordenador, sobre
-como descargar divelogs de CCR en el <a href="#_appendix_b_dive_computer_specific_information_for_importing_dive_information">Apéndice B</a></p></div>
-</div>
-</div>
-</div>
-</div>
-<div class="sect1">
-<h2 id="_obtener_mas_informacion_sobre_inmersiones_guardadas_en_el_diario">7. Obtener más información sobre inmersiones guardadas en el diario</h2>
-<div class="sectionbody">
-<div class="sect2">
-<h3 id="_la_pestana_informacion_para_inmersiones_individuales">7.1. La pestaña Información (para inmersiones individuales)</h3>
-<div class="paragraph"><p>La pestaña Información proporciona alguna información resumida
-sobre un buceo en particular que ha sido seleccionado en la <strong>Lista de
-inmersiones</strong>. La información útil incluye el intervalo en superficie antes de la
-inmersión, las profundidades máxima y media, el volumen de gas consumido, el
-C.A.S. (consumo de aire en superficie) y el número de unidades de toxicidad de
-oxígeno (OTU) en las que se ha incurrido.</p></div>
-<div class="admonitionblock">
-<table><tr>
-<td class="icon">
-<img src="images/icons/info.jpg" alt="Note" />
-</td>
-<td class="content">Consumo de gas y cálculos de CAS: <em>Subsurface</em> calcula el CAS y el consumo de gas
-teniendo en cuenta la incompresibilidad de los gases, particularmente a
-presiones en las botellas superiores a 200 bar, haciéndolos más precisos. Los
-usuarios deberían consultar el <a href="#SAC_CALCULATION">Apéndice F</a> para más información.</td>
-</tr></table>
-</div>
-</div>
-<div class="sect2">
-<h3 id="S_ExtraDataTab">7.2. La pestaña <strong>Otros datos</strong> (para inmersiones individuales)</h3>
-<div class="paragraph"><p>Cuando se utiliza un ordenador de buceo, a menudo facilita determinadas
-informaciones que no pueden presentarse de forma estandarizada ya que la
-naturaleza de la información varía de un ordenador a otro. Estos datos suelen
-comprender informaciones de ajustes, metadatos sobre una inmersión, niveles de
-batería, tiempos de "no vuelo" o factores de gradiente usados durante el buceo.
-Si es posible, toda esta información se presenta en la pestaña <strong>Otros datos</strong>. A
-continuación hay una imagen que muestra otros datos para un buceo con un
-rebreather Poseidon.</p></div>
-<div class="imageblock" style="text-align:center;">
-<div class="content">
-<img src="images/ExtraDataTab_f20.jpg" alt="FIGURA: Pestaña Otros datos" />
-</div>
-</div>
-</div>
-<div class="sect2">
-<h3 id="_la_pestana_estadisticas_para_grupos_de_inmersiones">7.3. La pestaña Estadísticas (para grupos de inmersiones)</h3>
-<div class="paragraph"><p>La pestaña Estadísticas facilita información resumida para más de una inmersión,
-suponiendo que se haya seleccionado más de un buceo en la <strong>Lista de inmersiones</strong>
-tcon los estándares "Ctrl+clic" o "Shift+clic" del ratón. Si solo se ha
-seleccionado una los cálculos se efectuarán solo para esa inmersión. Esta
-pestaña muestra el número de inmersiones seleccionadas, el tiempo total de buceo
-para estas inmersiones, así como los máximos, mínimos y medios para la duración,
-profundidad, temperatura en agua y superficie y CAS. También muestra la
-profundidad máxima de las inmersiones más profunda y más superficial de las
-seleccionadas.</p></div>
-</div>
-<div class="sect2">
-<h3 id="S_DiveProfile">7.4. El Perfil de inmersión</h3>
-<div class="imageblock" style="text-align:center;">
-<div class="content">
-<img src="images/Profile2.jpg" alt="Típico perfil de buceo" />
-</div>
-</div>
-<div class="paragraph"><p>De todos los paneles de <em>Subsurface</em>, el Perfil contiene la información más
-detallada de cada inmersión. El perfil de inmersión tiene una <strong>barra de botones</strong>
-en el lado izquierdo que permite controlar varias opciones. Las funciones de
-estos botones se describen más adelante. El objeto principal del perfil de
-inmersión es el gráfico de profundidad en función del tiempo. Además de la
-información obvia acerca de la profundidad, también muestra los ratios de
-ascenso y descenso en relación a las velocidades de ascenso y descenso
-recomendadas. Esta información se proporciona utilizando diferentes colores:</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>Color</strong></p></td>
-<td align="left" valign="top"><p class="table"><strong>Velocidad de descenso (m/min)</strong></p></td>
-<td align="left" valign="top"><p class="table"><strong>Velocidad de ascenso (m/min)</strong></p></td>
-</tr>
-<tr>
-<td align="left" valign="top"><p class="table">Rojo</p></td>
-<td align="left" valign="top"><p class="table">> 30</p></td>
-<td align="left" valign="top"><p class="table">> 18</p></td>
-</tr>
-<tr>
-<td align="left" valign="top"><p class="table">Naranja</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">Amarillo</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">Verde claro</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">Verde oscuro</p></td>
-<td align="left" valign="top"><p class="table">< 1.5</p></td>
-<td align="left" valign="top"><p class="table">< 1.5</p></td>
-</tr>
-</tbody>
-</table>
-</div>
-<div class="paragraph"><p>El perfil también incluye lecturas de profundidad para los picos y valles del
-gráfico. De esta forma, se debe poder visualizar la profundidad del punto más
-hondo y otros picos. La profundidad media se muestra como una línea gris que
-indica la profundidad media en cada momento de la inmersión.</p></div>
-<div class="admonitionblock">
-<table><tr>
-<td class="icon">
-<img src="images/icons/scale.jpg" alt="Note" />
-</td>
-<td class="content">En algunos casos el perfil de inmersión no llena el área completa del panel.
-Hacer clic en el botón Escala de la barra de herramientas de la izquierda,
-habitualmente, incrementa el tamaño del perfil hasta llenar el área de forma
-eficiente</td>
-</tr></table>
-</div>
-<div class="paragraph"><p><strong>La temperatura del agua</strong> se muestra con su propia línea azul con valores
-situados junto a cambios significativos.</p></div>
-<div class="paragraph"><p>El perfil de inmersión puede incluir <strong>gráficos de presiones parciales</strong> de O2, N2
-y He durante el buceo (ver la figura anterior) así como techos de deco
-calculados por <em>Subsurface</em> o registrados por el ordenador de buceo (solo
-visibles para buceos profundos, largos o repetitivos). La presión parcial del
-oxígeno se indica en verde, la del nitrógeno en negro y la del helio en rojo
-oscuro. Estos gráficos de presiones parciales se muestran bajo los datos de
-perfil.</p></div>
-<div class="admonitionblock">
-<table><tr>
-<td class="icon">
-<img src="images/icons/O2.jpg" alt="Note" />
-</td>
-<td class="content">Clicar este botón permite visualizar la presión parcial de oxígeno durante la
-inmersión. Se dibuja bajo los gráficos de profundidad y temperatura.</td>
-</tr></table>
-</div>
-<div class="admonitionblock">
-<table><tr>
-<td class="icon">
-<img src="images/icons/N2.jpg" alt="Note" />
-</td>
-<td class="content">Clicar este botón permite visualizar la presión parcial de nitrógeno durante la
-inmersión.</td>
-</tr></table>
-</div>
-<div class="admonitionblock">
-<table><tr>
-<td class="icon">
-<img src="images/icons/He.jpg" alt="Note" />
-</td>
-<td class="content">Clicar este botón permite visualizar la presión parcial de helio durante la
-inmersión. Esto solo es interesante para buceadores que usen trimix, helitrox o
-mezclas respiratorias similares.</td>
-</tr></table>
-</div>
-<div class="paragraph"><p>El gráfico de <strong>consumo de gas</strong> muestra la presión de la botella y su variación
-durante la inmersión. El consumo de gas tiene en cuenta la profundidad, de
-manera que, incluso cuando introduces manualmente las presiones inicial y final,
-el gráfico no es una línea recta. Al igual que el gráfico de profundidad, la
-pendiente de la presión de la botella facilita información acerca del CAS
-momentáneo, si se está usando ordenador con gas integrado. Aquí el color no se
-refiere a valores absolutos, sino que se calcula en relación a la media
-normalizada de aire consumido durante este buceo. Así pues, las áreas en rojo o
-naranja indican momentos de consumo por encima de la media mientras que el verde
-oscuro indicará momentos de consumo de gas por debajo de la media.</p></div>
-<div class="admonitionblock">
-<table><tr>
-<td class="icon">
-<img src="images/icons/Heartbutton.png" alt="Note" />
-</td>
-<td class="content">Hacer clic en el botón de ritmo cardiaco permitirá mostrar información de este
-parámetro durante la inmersión si el ordenador de buceo tiene conectado un
-sensor de ritmo cardiaco.</td>
-</tr></table>
-</div>
-<div class="paragraph"><p>Es posible <strong>hacer zoom</strong> en el gráfico del perfil. Se puede hacer con la rueda
-del ratón o el gesto equivalente en el trackpad. Por defecto, <em>Subsurface</em>
-siempre muestra un área suficientemente grande para mostrar al menos 30 minutos
-y 30 metros – de esta forma, las inmersiones cortas o superficiales se reconocen
-a simple vista; algo que a los apneístas les trae claramente sin cuidado.</p></div>
-<div class="imageblock" style="text-align:center;">
-<div class="content">
-<img src="images/MeasuringBar.png" alt="FIGURE: Barra de medidas" />
-</div>
-</div>
-<div class="admonitionblock">
-<table><tr>
-<td class="icon">
-<img src="images/icons/ruler.jpg" alt="Note" />
-</td>
-<td class="content">Pueden hacerse <strong>medidas de profundidad o tiempo</strong> utilizando el botón <strong>regla</strong> de
-la izquierda del perfil La medición se hace arrastrando los puntos rojos a los
-dos puntos del perfil entre los que deseas medir. La información se facilita en
-el área blanca horizontal bajo los dos puntos.</td>
-</tr></table>
-</div>
-<div class="admonitionblock">
-<table><tr>
-<td class="icon">
-<img src="images/icons/ShowPhotos_f20.png" alt="Note" />
-</td>
-<td class="content">Las fotografías que se han añadido a una inmersión pueden mostrarse en el perfil
-seleccionando el botón <strong>Mostrar foto</strong> en la barra de herramientas a la izquierda
-del perfil. La posición de la foto en el perfil indica la hora exacta a la que
-se tomó. Si el botón no está activado, las fotos permanecen ocultas.</td>
-</tr></table>
-</div>
-<div class="paragraph"><p>El perfil de buceo también puede incluir el <strong>techo</strong> registrado por el ordenador
-de buceo (o, más precisamente, la parada deco más profunda que el ordenador de
-buceo calcule para cada momento en el tiempo) como una capa roja en el perfil de
-la inmersión. Los techos de ascenso surgen cuando un ascenso directo a
-superficie incrementa el riesgo de que el buzo sufra enfermedad descompresiva
-(ED) y se necesita ascender más despacio, o efectuar paradas de descompresión
-antes de subir a la superficie. No todos los ordenadores de buceo guardan esta
-información y posibilitan su descarga; por ejemplo todos los ordenadores Suunto
-carecen de la posibilidad de facilitar estos datos tan útiles a los softwares de
-registro de inmersiones. <em>Subsurface</em> también calcula los techos
-independientemente, mostrándolos como una capa verde sobre el perfil. A causa de
-las diferencias en los algoritmos utilizados y la cantidad de datos disponibles
-(y otros factores tomados en consideración en el momento de los cálculos) es
-improbable que los techos de los ordenadores de buceo y de <em>Subsurface</em> sean los
-mismos, incluso si se utilizan el mismo algoritmo y los mismos factores de
-gradiente (ver más adelante). También es bastante común que <em>Subsurface</em> calcule
-un techo cuando el ordenador permaneció en modo no deco durante la inmersión
-completa (representada por la sección <span class="green">verde oscuro</span> del perfil). Esto se
-debe al hecho de que los cálculos de <em>Subsurface</em> describen la obligación de
-descompresión en ese punto del tiempo durante la inmersión, mientras los
-ordenadores de buceo habitualmente, tienen en cuenta el ascenso que va a venir.
-Durante el ascenso parte del exceso de nitrógeno (y posiblemente de helio) ya se
-ha eliminado a través de la respiración por lo que, aunque el buceador
-técnicamente encontrara un techo, la inmersión aún no requiere explícitamente
-una parada de descompresión. Esta característica permite a los ordenadores de
-buceo ofrecer tiempos de fondo más largos.</p></div>
-<div class="admonitionblock">
-<table><tr>
-<td class="icon">
-<img src="images/icons/cceiling.jpg" alt="Note" />
-</td>
-<td class="content">Si el propio ordenador de buceo calcula un techo y lo pone a disposición de
-<em>Subsurface</em> durante la descarga de inmersiones, puede ser mostrado como un
-árearoja seleccionando el botón <strong>Mostrar techo informado por el ordenador</strong> del
-panel de perfil.</td>
-</tr></table>
-</div>
-<div class="admonitionblock">
-<table><tr>
-<td class="icon">
-<img src="images/icons/ceiling1.jpg" alt="Note" />
-</td>
-<td class="content">Si hacemos clic en el botón <strong>Mostrar techo calculado</strong> por <em>Subsurface</em> del panel
-del perfil, se muestra en verde este techo, si existe, para una inmersión en
-particular (<strong>A</strong> en la figura a continuación). Este ajuste puede modificarse de
-dos maneras:</td>
-</tr></table>
-</div>
-<div class="admonitionblock">
-<table><tr>
-<td class="icon">
-<img src="images/icons/ceiling2.jpg" alt="Note" />
-</td>
-<td class="content">Si, además, se selecciona el botón <strong>Calcular todos los tejidos</strong> del panel de
-perfil, se muestra el techo para los distintos tejidos del modelo Bühlman (<strong>B</strong>
-en la figura de debajo).</td>
-</tr></table>
-</div>
-<div class="admonitionblock">
-<table><tr>
-<td class="icon">
-<img src="images/icons/ceiling3.jpg" alt="Note" />
-</td>
-<td class="content">Si, además, se selecciona el botón <strong>Mostrar el techo calculado con incrementos
-de 3m</strong> entonces el techo se muestra con saltos de 3 en 3 metros.</td>
-</tr></table>
-</div>
-<div class="imageblock" style="text-align:center;">
-<div class="content">
-<img src="images/Ceilings2.jpg" alt="Figura: Techo con resolución de 3 metros" />
-</div>
-</div>
-<div class="admonitionblock">
-<table><tr>
-<td class="icon">
-<img src="images/icons/ShowCylindersButton.jpg" alt="Note" />
-</td>
-<td class="content">Al seleccionar este icono, los diferentes gases utilizados durante una inmersión
-se presentarán en forma de barras de colores en la parte de abajo del perfil. En
-general, el oxígeno se presenta con una barra verde, el nitrógeno con una barra
-amarilla y el helio con una barra roja. La imagen a continuación muestra un buceo
-que primero utiliza una botella de trimix (rojo y verde), seguida por un cambio a
-una botella de nitrox (amarillo y verde) tras 23 minutos. Las botellas con aire
-se muestran con una barra azul claro.</td>
-</tr></table>
-</div>
-<div class="imageblock" style="text-align:center;">
-<div class="content">
-<img src="images/ShowCylinders_f20.jpg" alt="Figura: Gráfico de uso de botellas" />
-</div>
-</div>
-<div class="admonitionblock">
-<table><tr>
-<td class="icon">
-<img src="images/tissues.jpg" alt="Note" />
-</td>
-<td class="content">Muestra presiones de los gases inertes en los tejidos, en relación con la
-presión ambiental (línea gris horizontal).
-Las presiones en los tejidos se calculan utilizando el algoritmo Bühlmann ZH-16
-y se muestran como líneas de colores que varían desde el verde (tejidos rápidos)
-al azul (tejidos más lentos).
-La línea negra, dibujada sobre la presión ambiental, es la máxima sobresaturación
-de tejidos permitida, en la que se incluyen los factores de gradiente que se
-establecieron en <em>Preferencias</em>. Para buceadores que hacen buceo con descompresión
-planificada, se obtienen ritmos de desaturación eficientes manteniendo los tejidos
-entre la presión ambiental de los gases inertes (línea gris) y la presión límite
-(línea negra). Lo que se muestra en pantalla es una representación de la presión
-en los tejidos durante toda la inmersión. En contraste, el
-<a href="#S_gas_pressure_graph">Gráfico de presión de gases</a> de la ventana <strong>Información</strong>
-del <strong>Perfil</strong> es un reflejo de las presiones de los tejidos en el instante de
-tiempo señalado por la posición del cursor sobre el perfil de la inmersión.</td>
-</tr></table>
-</div>
-<div class="imageblock" style="text-align:center;">
-<div class="content">
-<img src="images/tissuesGraph.jpg" alt="Figura: Gráfico de presión de gases inertes en los tejidos" />
-</div>
-</div>
-<div class="paragraph"><p>El ajuste de los factores de gradiente afecta mucho a los techos calculados y
-sus profundidades. Para más información acerca de factores de gradiente,
-consultar la sección <a href="#S_GradientFactors">Ajuste de preferencias de factores de gradiente</a>.
-Los factores de gradiente que se están utilizando(p.e. 35/75)
-aparecen sobre el gráfico de profundidad si se activan los botones adecuados de
-la barra de herramientas.
-<strong>N.B.</strong>: Los factores de gradiente indicados NO son los utilizados por el
-ordenador de buceo, sino los que utiliza <em>Subsurface</em> para calcular las
-obligaciones descompresivas durante la inmersión. Para una explicación más
-detallada de los factores de gradiente, consultar los siguientes links:</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="_el_menu_contextual_del_perfil_de_inmersion">7.5. El menú contextual del Perfil de Inmersión</h3>
-<div class="paragraph"><p>Se accede al menú contextual del Perfil de Inmersión haciendo clic-derecho
-mientras el cursor del ratón está sobre el panel del Perfil de Inmersión. El
-menú permite la creación de marcadores, eventos de cambio de gas o cambios
-manuales en setpoint de un CCR, aparte de los que se hayan podido importar del
-ordenador de buceo. Las marcas se sitúan contra la línea de profundidad del
-perfil y con el tiempo fijado donde estaba el cursor cuando el botón derecho
-se clicó para desplegar el menú. Los eventos de cambio de gas suponen una
-selección sobre el gas al que estamos cambiando, habiendo sido definida la lista
-de posibilidades en la pestaña <strong>Equipo</strong>. Los eventos de cambio de setpoint
-abren un diálogo en el que se permite elegir el valor del próximo setpoint. Como
-en el planificador, un setpoint cero indica que el buceador está respirando en
-circuito abierto, mientras cualquier valor diferente de cero indica el uso de
-circuito cerrado. Si hacemos clic-derecho mientras estamos sobre
-un marcador preexistente, el menú se extiende añadiendo opciones para permitir
-el borrado del marcador o permitir ocultar todos los marcadores de ese tipo.</p></div>
-</div>
-<div class="sect2">
-<h3 id="S_InfoBox">7.6. El <strong>Recuadro Información</strong></h3>
-<div class="paragraph"><p>El recuadro de Información muestra una amplia gama de información del <strong>perfil de
-inmersión</strong>. Normalmente el recuadro se situa en la parte de arriba a la
-izquierda del panel <strong>Perfil de Inmersión</strong>. Si el ratón apunta fuera del panel,
-solo es visible la linea superior del recuadro (ver figura (<strong>A</strong>) abajo). El
-recuadro puede moverse en el panel <strong>Perfil de Inmersión</strong> pulsando y
-arrastrándolo con el ratón de forma que no cubra detalles importantes. La
-posición del recuadro queda guardada y se usará de nuevo en los siguientes
-análisis.</p></div>
-<div class="imageblock" style="text-align:center;">
-<div class="content">
-<img src="images/InfoBox2.jpg" alt="Figura: Recuadro de Información" />
-</div>
-</div>
-<div class="paragraph"><p>En el momento en que el ratón apunta dentro del panel <strong>Perfil de Inmersión</strong>, el
-recuadro de información se expande y muestra varios detalles de datos. En esta
-situación, los datos reflejan el punto temporal a lo largo del perfil indicado
-por el cursor del ratón (ver la parte derecha de la figura (<strong>B</strong>) anterior donde
-el recuadro refleja la información en la posición de la [flecha] del cursor en
-esa imagen). Por lo tanto, mover el cursor en dirección horizontal permite que
-el recuadro muestre información para cualquier punto a lo largo del perfil.</p></div>
-<div class="paragraph"><p>En este modo, el recuadro de información da extensas estadísticas sobre la
-profundidad, el gas y el techo de la inmersión. Entre ellas se incluyen: el
-lapso de tiempo en el buceo (indicado con @), la profundidad (Prof), la presión
-de la botella (Pres), la temperatura, la velocidad de ascenso/descenso, el
-consumo de aire en superficie (CAS), la presión parcial de oxígeno, la
-profundidad máxima operativa (PMO), la profundidad equivalente al aire (PEA), la
-profundidad narcótica equivalente (PNE), la densidad equivalente al aire (EADD),
-los requisitos descompresivos en ese momento del tiempo (Deco), el tiempo hasta
-la superficie (TTS), el techo calculado, así como el techo calculado para varios
-compartimentos de tejidos Bühlmann.</p></div>
-<div class="paragraph"><p>El usuario tiene control sobre como se muestran varias estadísticas,
-representadas en cuatro de los botones a la izquierda del panel del perfil.
-Son:</p></div>
-<div class="admonitionblock">
-<table><tr>
-<td class="icon">
-<img src="images/icons/MOD.jpg" alt="Note" />
-</td>
-<td class="content">Activar este botón hace que el Recuadro de Información muestre la <strong>Profundidad
-máxima operativa (PMO)</strong> de la inmersión para la mezcla de gases utilizada. La
-PMO depende de la concentración de oxígeno en el gas respirado. Para el aire
-(21% de oxígeno) se sitúa alrededor de 57 m si se ha especificado una pO<sub>2</sub>
-máxima de 1.4 en la sección <strong>Preferencias</strong>. Por debajo de la PMO existe un
-riesgo muy elevado de exposición a los peligros asociados con la toxicidad del
-oxígeno.</td>
-</tr></table>
-</div>
-<div class="admonitionblock">
-<table><tr>
-<td class="icon">
-<img src="images/icons/NDL.jpg" alt="Note" />
-</td>
-<td class="content">Activar este botón hace que el recuadro Información muestre, bien el <strong>Límite
-de no descompresión (LND)</strong> o el <strong>*Tiempo total hasta superficie (TTS)</strong>. El
-LND es el tiempo que un buzo puede permanecer sumergido a la profundidad actual
-sin requerir descompresión (esto es, sin que aparezca un techo para el ascenso).
-Una vez que se ha excedido el LND y se requiere descompresión, el TTS incluirá
-el total de minutos requeridos antes de que el buceador pueda salir a superficie.
-El TTS incluye el tiempo de ascenso y las paradas de descompresión. Se calcula
-suponiendo que se usa el gas actual. Incluso si el perfil incluye varios
-cambios de gas, el TTS en un momento dado de la inmersión se habrá calculado
-con el gas en uso en ese momento. Para TTS superiores a 2 horas, no se calcula
-con precisión y simplemente se indica <em>TTS > 2h</em>.</td>
-</tr></table>
-</div>
-<div class="admonitionblock">
-<table><tr>
-<td class="icon">
-<img src="images/icons/SAC.jpg" alt="Note" />
-</td>
-<td class="content">Activar este botón hace que el Recuadro de información muestre el <strong>Consumo de
-aire en superficie (CAS)</strong>. El CAS es un indicador del ritmo respiratorio del
-buceador calculado a nivel del mar. El valor del CAS es inferior al real ya que
-un buceador a 10m usa aproximadamente el doble del que consume en superficie. El
-SAC da una indicación del ritmo de consumo de gas independientemente de la
-profundidad de la inmersión de forma que se pueden comparar los ritmos de
-diferentes inmersiones. Las unidades del CAS son litros/min o pies^3/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">Activar este botón hace que el Recuadro de información muestre la <strong>Profundidad
-equivalente al aire (PEA)</strong> para los buceos con nitrox y la <strong>Profundidad
-narcótica equivalente (PNE)</strong> para buceos con trimix. Estas magnitudes son
-importantes para buceadores que utilicen mezclas de gases distintas del aire.
-Sus valores dependen de la composición del gas respirado. La PEA es la
-profundidad de un hipotético buceo con aire que tenga la misma presión parcial
-de nitrógeno que la inmersión con nitrox actual. Una inmersión con nitrox
-conllevaría una obligación de descompresión igual que una inmersión con aire a
-una profundidad igual a la PEA. La PNE es la profundidad de una hipotética
-inmersión con aire que tenga la misma suma de presiones parciales de gases
-narcóticos (oxígeno y nitrógeno) que la actual inmersión con trimix. Un buceador
-con trimix puede esperar los mismos efectos narcóticos que un buceador
-respirando aire a una profundidad igual a la PNE.</td>
-</tr></table>
-</div>
-<div class="paragraph"><p>La figura (<strong>B</strong>) anterior muestra un Recuadro de Información con un conjunto de
-datos casi completo.</p></div>
-<div class="sect3">
-<h4 id="S_gas_pressure_graph">7.6.1. El gráfico de barras de presión de gases</h4>
-<div class="paragraph"><p>A la izquierda del <strong>Recuadro de Información</strong> hay un gráfico de barras vertical
-que indica las presiones de los gases inertes que el buceador estaba respirando
-<em>en un momento dado de la inmersión</em>, señalado por la posición del cursor sobre
-el <strong>Perfil de inmersión</strong>. La figura abajo a la izquierda indica el significado
-de las diferentes partes del gráfico de barras.</p></div>
-<div class="imageblock" style="text-align:center;">
-<div class="content">
-<img src="images/GasPressureBarGraph.jpg" alt="FIGURE:Gráfico de barras de presiones de gases" />
-</div>
-</div>
-<div class="ulist"><ul>
-<li>
-<p>
-El área verde claro indica el gas total, con el margen superior de esta zona
- indicando la presión total de gas inhalada por el buceador y medida desde el
- fondo del gráfico a la parte superior. Esta presión tiene un valor <em>relativo</em>
- en el gráfico y no indica presión absoluta.
-</p>
-</li>
-<li>
-<p>
-La línea negra horizontal por debajo de la zona verde claro indica la presión de
- equilibrio de los gases inertes respirados, habitualmente nitrógeno. En el caso
- del trimix, es la presión combinada del helio y el nitrógeno. En este ejemplo,
- el usuario esta buceando con EAN32, por lo tanto la presión del gas inerte está
- al 68% de la distancia desde el fondo del gráfico hasta el valor de la presión
- total.
-</p>
-</li>
-<li>
-<p>
-La zona verde oscura en la parte baja del gráfico representa las presiones de
- los gases inertes en cada uno de los 16 compartimentos de tejidos, según el
- algoritmo de Bühlmann, estando los tejidos rápidos en el lado izquierdo.
-</p>
-</li>
-<li>
-<p>
-La línea horizontal negra superior indica el factor de gradiente que se aplica
- a la profundidad del buceador para el punto concreto del <strong>Perfil de Inmersión</strong>.
- Este factor de gradiente es una interpolación entre el GFbajo y el GFalto que
- se hayan especificado en la pestaña Gráfico del <strong>Panel de preferencias</strong> de
- <em>Subsurface</em>.
-</p>
-</li>
-<li>
-<p>
-El margen inferior de la zona roja del gráfico indica el valor M derivado de
- Bühlman, o sea el valor de la presión de gases inertes a partir de la cual la
- formación de burbujas se espera que sea severa, resultando en una enfermedad
- descompresiva.
-</p>
-</li>
-</ul></div>
-<div class="paragraph"><p>Estos cinco valores se indican a la izquierda en la figura anterior. La forma
-en que el gráfico de barras cambia durante una inmersión, se representa en el
-lado derecho de la figura anterior, para un buceador usando EAN32.</p></div>
-<div class="ulist"><ul>
-<li>
-<p>
-El gráfico <strong>A</strong> indica la situación al inicio de una inmersión, con el buzo
- en superficie. Las presiones en los compartimentos de tejidos todavía están
- a la presión de equilibrio ya que aún no se ha buceado.
-</p>
-</li>
-<li>
-<p>
-El gráfico <strong>B</strong> indica la situación tras un descenso a 30 metros. Pocos de
- los compartimentos de tejidos han tenido tiempo de responder al descenso, las
- presiones de los gases muy por debajo de presión de equilibrio.
-</p>
-</li>
-<li>
-<p>
-El gráfico <strong>C</strong> representa las presiones tras 30 minutos a 30 metros. Los
- compartimentos rápidos han llegado al equilibrio (p.e. han alcanzado la altura
- de la línea negra que indica la presión de equilibrio). Los compartimentos más
- lentos (hacia la derecha) no han alcanzado el equilibrio y están en proceso de
- incrementar lentamente la presión.
-</p>
-</li>
-<li>
-<p>
-El gráfico <strong>D</strong> muestra las presiones tras ascender a una profundidad de 4.5
- metros. Ya que, durante el ascenso, la presión total del gas inhalado ha caído
- mucho, de 4 bares a 1.45 bares, las presiones en los diferentes compartimentos
- de tejidos sobrepasan la presión total del gas y se aproximan al factor de
- gradiente (la línea negra superior en la imagen). Continuar el ascenso haría
- que rebasáramos el valor del factor de gradiente (GFalto), poniendo en peligro
- al buceador.
-</p>
-</li>
-<li>
-<p>
-El gráfico <strong>E</strong> indica la situación después de permanecer a 4.5 metros durante
- 10 minutos. Los compartimentos rápidos han bajado su presión. Como era de
- esperar, las presiones en los compartimentos lentos no han variado mucho. Las
- presiones en los compartimentos rápidos ya no se acercan al valor de GFalto y
- el buceador está más seguro que en la situación expuesta en el gráfico <strong>D</strong>.
-</p>
-</li>
-</ul></div>
-</div>
-</div>
-</div>
-</div>
-<div class="sect1">
-<h2 id="_organizar_el_registro_manipular_grupos_de_inmersiones">8. Organizar el registro (Manipular grupos de inmersiones)</h2>
-<div class="sectionbody">
-<div class="sect2">
-<h3 id="_el_menu_contextual_de_la_lista_de_inmersiones">8.1. El menú contextual de la Lista de Inmersiones</h3>
-<div class="paragraph"><p>Varias acciones sobre, bien una inmersión, bien un grupo de ellas, se pueden
-efectuar utilizando el Menú Contextual de la Lista de inmersiones, al que se
-accede seleccionando una inmersión o un grupo de ellas y haciendo clic-derecho.</p></div>
-<div class="imageblock" style="text-align:center;">
-<div class="content">
-<img src="images/ContextMenu.jpg" alt="Figura: Menú contextual" />
-</div>
-</div>
-<div class="paragraph"><p>El menú contextual se usa en muchas de las acciones que se describen a
-continuación.</p></div>
-<div class="sect3">
-<h4 id="_personalizar_las_columnas_mostradas_en_el_panel_strong_lista_de_inmersiones_strong">8.1.1. Personalizar las columnas mostradas en el panel <strong>Lista de inmersiones</strong></h4>
-<div class="imageblock" style="text-align:center;">
-<div class="content">
-<img src="images/DiveListOptions.jpg" alt="Ejemplo: Opciones de la Lista de inmersiones" />
-</div>
-</div>
-<div class="paragraph"><p>La información por defecto de la <strong>Lista de inmersiones</strong> incluye, para cada buceo,
-Numero de inmersión, Fecha, Calificación, Profundidad, Duración y Ubicación. Esta
-información puede controlarse y cambiarse haciendo clic derecho sobre la barra de
-encabezamiento de la <strong>Lista de inmersiones</strong>. Por ejemplo, un clic derecho sobre
-la cabecera 'Fecha’despliega una lista de valores que pueden mostrarse (ver la
-figura anterior). Si seleccionamos un valor para que se muestre o desaparezca de
-la lista, esta se actualiza inmediatamente. Las preferencias para la información
-que muestre la lista se guardan y reutilizan cada vez que se abre <em>Subsurface</em>.</p></div>
-</div>
-<div class="sect3">
-<h4 id="_seleccionar_inmersiones_en_una_ubicacion_concreta">8.1.2. Seleccionar inmersiones en una ubicación concreta</h4>
-<div class="paragraph"><p>Muchos buceadores tienen largas listas de inmersiones, y puede resultar difícil
-localizar todos los buceos en un punto en concreto. Presionando <em>Ctrl+F</em> en el
-teclado se abre una casilla de texto en la parte de arriba a la izquierda de la
-<strong>Lista de inmersiones</strong>. Si se teclea el nombre de una ubicación en esta casilla
-la <strong>Lista de inmersiones</strong> se filtra inmediatamente para mostrar solo los buceos
-en esta ubicación.</p></div>
-</div>
-</div>
-<div class="sect2">
-<h3 id="S_Renumber">8.2. Renumerar las inmersiones</h3>
-<div class="paragraph"><p>Las inmersiones normalmente se numeran incrementando desde las no-recientes
-(menores números de secuencia) a las más recientes (números de secuencia más
-altos). Numerar los buceos no siempre es consistente. Por ejemplo, cuando se
-añaden inmersiones antiguas a la lista, la numeración no sigue automáticamente
-por ser estas anteriores en fecha/hora a las ya existentes. Por lo tanto, en
-ocasiones, se puede necesitar renumerar los buceos. Esto se hace seleccionando
-(desde el menú principal) <em>Registro → Renumerar</em>. Se permite elegir el número de
-secuencia inferior que se va a usar. Completar esta operación supone obtener
-nuevos números de secuencia (basados en fecha/hora) para los buceos del panel
-<strong>Lista de Inmersiones</strong>.</p></div>
-<div class="paragraph"><p>También se pueden renumerar algunas inmersiones seleccionadas de la lista. Se
-seleccionan las inmersiones que necesiten renumerarse. Se hace clic-derecho
-sobre la lista seleccionada y se utiliza la lista contextual para efectuar el
-renumerado. Aparecerá una ventana solicitando al usuario que especifique el
-número de inicio para el proceso de numeración.</p></div>
-</div>
-<div class="sect2">
-<h3 id="S_Group">8.3. Agrupar las inmersiones en viajes y manipularlos</h3>
-<div class="paragraph"><p>Si buceas regularmente, la lista de inmersiones puede hacerse rápidamente muy
-larga. <em>Subsurface</em> puede agrupar los buceos en <em>viajes</em>. Lo hace agrupando
-inmersiones que tengan fechas/horas que no estén separadas más de dos días y
-crea una sola cabecera para cada viaje . Abajo hay una lista de inmersiones no
-agrupada (<strong>A</strong>, a la izquierda) y la lista agrupada correspondiente incluyendo
-cinco viajes (<strong>B</strong>, a la derecha):</p></div>
-<div class="imageblock" style="text-align:center;">
-<div class="content">
-<img src="images/Group2.jpg" alt="Figura: Agrupar inmersiones" />
-</div>
-</div>
-<div class="paragraph"><p>Agrupar en viajes permite una forma rápida de acceder a buceos individuales sin
-tener que pasar por largas listas de inmersiones. Para agrupar los buceos de una
-lista de inmersiones (desde el menú principal) se selecciona <em>Registro →
-Autoagrupar</em>. El panel Lista de Inmersiones ahora muestra solo los títulos de
-los viajes.</p></div>
-<div class="sect3">
-<h4 id="_editar_el_titulo_y_la_informacion_asociada_a_un_viaje_en_particular">8.3.1. Editar el título y la información asociada a un viaje en particular</h4>
-<div class="paragraph"><p>Normalmente, en la lista de inmersiones se incluye una mínima información en el
-título del viaje. Puede añadirse mucha más sobre un viaje seleccionando su
-título en la lista. Esto muestra una pestaña <strong>Notas del Viaje</strong> en el panel Notas
-de la inmersión. Aquí se puede añadir o editar información sobre dia/hora,
-ubicación del viaje, y otros comentarios generales. Al terminar, se selecciona
-<strong>Guardar</strong> en los botones de arriba a la derecha en la pestaña Notas del viaje.
-El título en la <strong>Lista de inmersiones</strong> debería reflejar ya algo de la
-información editada.</p></div>
-</div>
-<div class="sect3">
-<h4 id="_ver_los_buceos_de_un_viaje_en_concreto">8.3.2. Ver los buceos de un viaje en concreto</h4>
-<div class="paragraph"><p>Una vez que las inmersiones agrupadas en viajes, los usuarios pueden expandir
-uno o más viajes clicando la punta de flecha a la izquierda del título. Con ello
-se expande el viaje mostrando los buceos individuales efectuados.</p></div>
-</div>
-<div class="sect3">
-<h4 id="_colapsar_o_expandir_informacion_de_diferentes_viajes">8.3.3. Colapsar o expandir información de diferentes viajes</h4>
-<div class="paragraph"><p>Tras seleccionar un viaje concreto de la lista, el menú contextual resultante
-ofrece varias posibilidades de expandir o contraer buceos incluidos en viajes.
-Entre ellas expandir todos los viajes y contraer todos los viajes.</p></div>
-</div>
-<div class="sect3">
-<h4 id="_mezclar_inmersiones_de_mas_de_un_viaje_en_uno_solo">8.3.4. Mezclar inmersiones de más de un viaje en uno solo</h4>
-<div class="paragraph"><p>Tras seleccionar el título de un viaje del panel <strong>Lista de Inmersiones</strong>, el
-menú permite mezclar viajes con el viaje de abajo o con el de arriba.</p></div>
-</div>
-<div class="sect3">
-<h4 id="_separar_un_viaje_en_mas_de_uno">8.3.5. Separar un viaje en más de uno</h4>
-<div class="paragraph"><p>Si un viaje incluye diez inmersiones, el usuario puede separar el viaje en dos
-(viaje 1: cuatro inmersiones de arriba; viaje 2: seis inmersiones de abajo)
-seleccionando y haciendo clic-derecho en las cuatro inmersiones de arriba. El menú
-que aparecerá te permite crear un nuevo viaje seleccionando la opción <strong>Crear
-nuevo viaje arriba</strong>. Las cuatro inmersiones superiores quedan entonces agrupadas
-en un viaje separado. La siguiente figura muestra la selección y el menú a la
-izquierda (A), la acción completada a la derecha (B):</p></div>
-<div class="imageblock" style="text-align:center;">
-<div class="content">
-<img src="images/SplitDive3a.jpg" alt="FIGURA: Separar un viaje en dos" />
-</div>
-</div>
-</div>
-</div>
-<div class="sect2">
-<h3 id="_manipular_inmersiones_individuales">8.4. Manipular inmersiones individuales</h3>
-<div class="sect3">
-<h4 id="_borrar_una_inmersion_del_diario">8.4.1. Borrar una inmersión del diario</h4>
-<div class="paragraph"><p>Las inmersiones pueden borrarse permanentemente del diario seleccionándolas y
-haciendo clic-derecho para mostrar el menú y, entonces, seleccionando <strong>Borrar
-inmersión</strong>. Habitualmente esto se hará en casos donde se desee borrar
-inmersiones de prueba o buceos de duración extremadamente corta.</p></div>
-</div>
-<div class="sect3">
-<h4 id="_separar_una_inmersion_de_un_viaje">8.4.2. Separar una inmersión de un viaje</h4>
-<div class="paragraph"><p>Se pueden separar inmersiones del viaje al que pertenecen. Para ello se
-selecciona y hace clic-derecho en los buceos para mostrar el menú. Luego se
-selecciona <strong>Quitar inmersión(es) del viaje</strong>. Las inmersiones que han sido
-separadas aparecerán ahora encima o debajo del viaje al que pertenecieron, en
-función de la fecha y la hora de la inmersión separada.</p></div>
-</div>
-<div class="sect3">
-<h4 id="_anadir_una_inmersion_al_viaje_de_arriba">8.4.3. Añadir una inmersión al viaje de arriba</h4>
-<div class="paragraph"><p>Las inmersiones seleccionadas pueden moverse del viaje al que pertenecen al
-inmediatamente superior al actual. Para ello se selecciona y hace clic-derecho
-en los buceos para mostrar el menú, luego se selecciona <strong>Añadir inmersión(es) al
-viaje de arriba</strong>.</p></div>
-</div>
-<div class="sect3">
-<h4 id="_desplazar_la_hora_de_inicio_del_buceo_s">8.4.4. Desplazar la hora de inicio del buceo(s)</h4>
-<div class="paragraph"><p>En ocasiones es necesario ajustar la hora de comienzo de una inmersión. Esto
-puede aplicarse a situaciones en las que las inmersiones se han efectuado en
-diferentes zonas horarias o si el ordenador de buceo tiene mal configurada la
-hora. Se selecciona y hace clic-derecho en la inmersión(es) a ajustar. Esto
-despliega el menú. Seleccionar <strong>Desplazar horas</strong>. Se especifica el tiempo (en
-horas y minutos) en el que deben ajustarse los buceos y se hace clic en la
-opción que indica si el ajuste debe ser hacia adelante o hacia atrás.</p></div>
-</div>
-<div class="sect3">
-<h4 id="_juntar_buceos_en_uno_solo">8.4.5. Juntar buceos en uno solo</h4>
-<div class="paragraph"><p>En ocasiones una inmersión se interrumpe brevemente, p.e. si un buceador regresa
-a superficie unos pocos minutos, dando como resultado dos o más inmersiones
-grabadas por el ordenador y apareciendo como buceos distintos en el panel <strong>Lista
-de inmersiones</strong>. Se pueden unir estos buceos en uno solo seleccionando las
-correspondientes inmersiones y haciendo clic-derecho para mostrar el menú.
-Entonces se selecciona <strong>Mezclar inmersiones seleccionadas</strong>. Puede que sea
-necesario editar la información de la inmersión en el panel <strong>Notas</strong> para
-reflejar situaciones o condiciones que afecten al buceo
-resultante de la fusión. La figura a continuación muestra el perfil de dos
-inmersiones que fueron unidas:</p></div>
-<div class="imageblock" style="text-align:center;">
-<div class="content">
-<img src="images/MergedDive.png" alt="Ejemplo: Inmersión mezclada" />
-</div>
-</div>
-</div>
-<div class="sect3">
-<h4 id="_deshacer_manipulaciones_de_inmersiones">8.4.6. Deshacer manipulaciones de inmersiones</h4>
-<div class="paragraph"><p>Se pueden deshacer o rehacer acciones importantes, de las que se han comentado
-anteriormente, sobre inmersiones o viajes. Aquí se incluyen: <em>Borrar inmersión</em>,
-<em>Mezclar inmersiones</em>, <em>Renumerar inmersiones</em> y <em>Desplazar hora de buceo</em>.
-Para hacerlo, tras haber llevado a cabo cualquiera de estas acciones, se
-selecciona <em>Editar</em> desde el <strong>Menú Principal</strong>, lo que presentará un desplegable
-con las posibilidades <em>Deshacer</em> y <em>Rehacer</em>.</p></div>
-</div>
-</div>
-<div class="sect2">
-<h3 id="S_Filter">8.5. Filtrar la Lista de Inmersiones</h3>
-<div class="paragraph"><p>Los buceos del panel <strong>Lista de inmersiones</strong> pueden filtrarse, esto es, se pueden
-seleccionar únicamente algunos de los buceos basándose en sus atributos, p.e.
-las etiquetas, el lugar de buceo, el divemaster, compañeros o traje protector.
-El filtrado permite, por ejemplo, listar las inmersiones profundas en un punto
-determinado o, por el contrario, las inmersiones en cuevas con cierto
-compañero.</p></div>
-<div class="paragraph"><p>Para abrir el filtrado, seleccionar <em>Registro → Filtrar la lista de inmersiones</em>
-desde el menú principal. Esto abrirá el <em>Panel de filtrado</em> en la parte de arriba
-de la ventana de <em>Subsurface</em>. Arriba a la derecha del panel se ubican tres
-iconos (ver imagen a continuación).
-El <em>Panel de filtrado</em> puede reiniciarse (p.e. limpiar todos los filtros
-actuales) seleccionando la flecha amarilla. El <em>Panel de filtrado</em> también puede
-minimizarse seleccionando la <strong>flecha verde</strong>. Cuando está minimizado solo se
-muestran los tres iconos. El panel puede maximizarse clicando el icono que lo
-minimizó. El filtro se cierra y reinicia seleccionando el <strong>botón rojo</strong> con la
-cruz blanca.</p></div>
-<div class="imageblock" style="text-align:center;">
-<div class="content">
-<img src="images/Filterpanel.jpg" alt="Figura: Panel de filtrado" />
-</div>
-</div>
-<div class="paragraph"><p>Se pueden utilizar cuatro criterios para filtrar la lista de inmersiones:
-las etiquetas, las personas (compañeros/divemasters), punto de inmersión y traje
-de buceo, cada uno de los cuales viene representado por una lista seleccionable.
-Sobre cada lista hay un segundo nivel de filtrado. Por ejemplo, tecleando "<em>Ba</em>"
-en la casilla de texto sobre las ubicaciones, la lista podría quedar reducida a
-"<em>Bajo Piles I</em>", "<em>Bajo Piles II</em>" y "<em>Bajo de Testa</em>". Filtrar la lista
-permite encontrar rápidamente términos de búsqueda para filtrar la lista de
-inmersiones.</p></div>
-<div class="paragraph"><p>Para activar el filtrado de la lista de inmersiones, se necesita seleccionar
-al menos una casilla en una de las cuatro listas. La lista de inmersiones se
-reduce para mostrar solo los buceos que cumplen los criterios seleccionados en
-las listas. Las cuatro listas funcionan como un filtro con operadores <em>Y</em>,
-<em>Subsurface</em> filtraría, pues, para "<em>cueva</em>" como etiqueta y "<em>José García</em>"
-como compañero; pero los filtros dentro de una categoría son inclusivos, esto
-es, filtrar por etiquetas con "cueva" y "barco" mostraría todas las inmersiones
-en las que aparezcan las etiquetas "cueva" <em>O</em> "barco", solas o conjuntamente.</p></div>
-</div>
-</div>
-</div>
-<div class="sect1">
-<h2 id="S_ExportLog">9. Exportar el registro de inmersiones o parte del mismo</h2>
-<div class="sectionbody">
-<div class="paragraph"><p>Hay dos posibilidades de exportar información de buceo desde <em>Subsurface</em>:</p></div>
-<div class="ulist"><ul>
-<li>
-<p>
-Exportar información de buceo a <em>Facebook</em>
-</p>
-</li>
-<li>
-<p>
-<a href="#S_Export_other">Exportar información de buceo a otros destinos o formatos</a>
-</p>
-</li>
-</ul></div>
-<div class="sect2">
-<h3 id="S_facebook">9.1. Exportar información de buceo a <em>Facebook</em></h3>
-<div class="paragraph"><p>La exportación de inmersiones a <em>Facebook</em> se maneja de forma diferente a otros
-tipos de exportación porque se requiere una
-conexión a esta red social y se necesita un usuario de <em>Facebook</em> y su password.
-Si, desde el menú principal, seleccionamos <em>Archivo → Preferencias →
-Facebook</em>, se nos presentará una pantalla de acceso (ver imagen <strong>A</strong> de la
-izquierda a continuación). Introducimos nuestro usuario y password de
-<em>Facebook</em>. Una vez que nos hemos conectado a <em>Facebook</em>, se nos presenta el
-panel de la imagen <strong>B</strong> a continuación, donde se incluye un botón <em>Desconectar</em>
-para cerrar la conexión a <em>Facebook</em>.</p></div>
-<div class="imageblock" style="text-align:center;">
-<div class="content">
-<img src="images/facebook1_f20.jpg" alt="Figure: Acceso a Facebook" />
-</div>
-</div>
-<div class="paragraph"><p>Desde la ventana de <em>Subsurface</em> es fácil saber si se tiene una conexión válida
-con <em>Facebook</em>. Desde el <strong>Menú principal</strong>, selecciona <em>Compartir → Facebook</em>
-(ver imagen <strong>A</strong> a continuación. Normalmente la opción <em>Facebook</em> está
-desactivada, pero, si hay una conexión establecida, la opción está activa y
-puede ser selecciionada.
-Tras haber establecido una conexión con <em>Facebook</em>, transferir un perfil de
-inmersión a nuestro perfil de <em>Facebook</em> es sencillo.</p></div>
-<div class="paragraph"><p>Asegúrate de que la inmersión que quieres transferir al historial
-es la que se muestra en el panel <strong>Perfil de la inmersión</strong>. Si se pulsa
-<em>Compartir → Facebook</em> desde el <strong>Menú principal</strong> aparecerá un diálogo en el
-que se definirá la cantidad de información adicional que se desea transferir
-al historial junto con el perfil (ver imagen <strong>B</strong>, a continuación). Se necesita
-proporcionar el nombre de un álbum de <em>Facebook</em> para poder enviar el perfil de
-inmersión. Las casillas seleccionables de la izquierda nos permiten seleccionar
-la información que vamos a enviar. Esta información se muestra en la ventana de
-texto de la derecha (ver imagen <strong>B</strong> a continuación). El mensaje que se va a
-enviar se puede editar directamente en esta ventana de texto. Tras haber elegido
-la información y verificado lo que se va a subir, se selecciona el botón <em>OK</em>
-lo que inicia la transferencia a <em>Facebook</em>. Unos momentos después aparecerá
-un mensaje indicando una transferencia correcta.</p></div>
-<div class="paragraph"><p>El álbum creado y el post al historial se marcarán como privados. Para que
-los amigos puedan ver el post habrá que cambiar los permisos desde un acceso
-normal a <em>Facebook</em> desde un navegador o desde la app de <em>Facebook</em>. Aunque
-esto suponga un paso de más, los desarrolladores entienden que esta es la mejor
-solución para evitar subidas no deseadas en el historial público.</p></div>
-<div class="imageblock" style="text-align:center;">
-<div class="content">
-<img src="images/facebook2_f20.jpg" alt="Figure: Facebook login" />
-</div>
-</div>
-<div class="paragraph"><p>Si se considera necesario, cierra la conexión a <em>Facebook</em>, bien cerrando
-<em>Subsurface</em> o bien seleccionando <em>Archivo → Preferencias → Facebook</em> desde
-el menú principal, clicando el botón correspondiente en el panel <em>Facebook</em>.</p></div>
-</div>
-<div class="sect2">
-<h3 id="S_Export_other">9.2. Exportar información de buceo a otros destinos o formatos</h3>
-<div class="paragraph"><p>Para exportar a otros destinos,
-se llega a la función de exportación seleccionando <em>Archivo → Exportar</em> lo que
-despliega el diálogo de exportación. Este diálogo siempre ofrece dos opciones:
-guardar TODAS las inmersiones, o guardar solo las inmersiones seleccionadas en
-el panel <strong>Lista de Inmersiones</strong> de <em>Subsurface</em>. Marca la casilla seleccionable
-apropiada (ver imagen a continuación).</p></div>
-<div class="imageblock" style="text-align:center;">
-<div class="content">
-<img src="images/Export_f20.jpg" alt="Figura: Diálogo de exportación" />
-</div>
-</div>
-<div class="paragraph"><p>Un registro de buceo puede guardarse en tres formatos:</p></div>
-<div class="ulist"><ul>
-<li>
-<p>
-Formato XML de <em>Subsurface</em>. Es el formato usado nativamente por <em>Subsurface</em>.
-</p>
-</li>
-<li>
-<p>
-Universal Dive Data format (UDDF). Ver <a href="http://uddf.org">http://uddf.org</a> para más información.
- UDDF es un formato genérico que permite la comunicación entre muchos ordenadores
- de buceo y programas de de ordenador.
-</p>
-</li>
-<li>
-<p>
-<em>Divelogs.de</em>, un registro de inmersiones basado en internet. Para enviar
- buceos a <em>Divelogs.de</em>, se necesita un usuario y una password de <em>Divelogs.de</em>.
- Hay que registrarse en <em>htttp://es.divelogs.de</em> y suscribir el servicio para
- poder enviar datos de inmersiones desde <em>Subsurface</em>.
-</p>
-</li>
-<li>
-<p>
-<em>DiveShare</em> es también un repositorio de inmersiones basado en internet que se
- dirige a inmersiones recreativas. Para subir inmersiones se necesita una
- identificación de usuario, por lo que es necesario registrase en <em>http://scubadiveshare.com</em>.
-</p>
-</li>
-<li>
-<p>
-<em>Detalles de inmersión CSV</em>, que incluye la información más crítica del perfil de la
- inmersión. La información que se incluye es número, fecha, hora, duración,
- profundidad, temperatura y presión. En resumen, la mayoría de la información
- que un buceador recreativo conserva en un registro escrito.
-</p>
-</li>
-<li>
-<p>
-<em>Perfil de inmersión CSV</em>, que incluye una gran cantidad de detalles para
- cada inmersión, entre ellos el perfil de profundidad, temperaturas
- e información de presiones para cada inmersión.
-</p>
-</li>
-<li>
-<p>
-Formato <em>HTML</em>, en el cual los buceos se guardan en archivos HTML,
- visualizables con un navegador de internet.Se soportan la mayoría de navegadores
- modernos, pero debe estar activado Javascript. Este archivo <strong>NO</strong> es editable. El
- registro de inmersiones en HTML contiene la mayor parte de la información del
- divelog. Sin embargo, no muestra los valores calculados del panel <strong>Perfil de
- Inmersión</strong>, p.e. la presión calculada de la botella, presiones de los gases o
- PMO. Dispone de una opción de búsqueda que permite rastrear el diario. La exportación
- a HTML se especifica en la segunda pestaña del diálogo de exportación (imagen
- <strong>B</strong> anterior). Un uso típico de esta opción es exportar todas nuestros buceos
- a un smartphone o tablet donde nos serviría de registro portátil, util para
- compañías a las que les gusta verificar el historial de un buceador.
-</p>
-</li>
-<li>
-<p>
-Formato <em>mapamundi</em>, un archivo HTML con un mapa del mundo en el que quedará
- marcada cada inmersión y alguna información sobre ella. El mapa <strong>NO</strong> es
- editable. Si se selecciona cualquiera de los puntos de buceo
- sobre el mapa, se muestra en texto un sumario de la inmersión, como se ve
- en la imagen a continuación.
-</p>
-</li>
-</ul></div>
-<div class="imageblock" style="text-align:center;">
-<div class="content">
-<img src="images/mapview_f20.jpg" alt="Figura: Vista de exportación en formato Mapamundi" />
-</div>
-</div>
-<div class="ulist"><ul>
-<li>
-<p>
-<em>Profundidad de imágenes</em>, que crea un fichero de texto que contiene los
- nombres de todos los archivos de imágenes añadidos a cualquiera de los buceos
- seleccionados del la <em>Lista de inmersiones</em>, junto con la profundidad a la
- fue tomada la fotografía.
-</p>
-</li>
-<li>
-<p>
-<em>Ajustes generales</em>, en la pestaña HTML, se proporcionan las siguientes
- opciones:
-</p>
-<div class="ulist"><ul>
-<li>
-<p>
-Numeración de Subsurface: Si se activa esta opción, las inmersiones se
- exportan con la misma numeración que tienen asociada en <em>Subsurface</em>. De lo
- contrario, los buceos se numerarán a partir de 1.
-</p>
-</li>
-<li>
-<p>
-Exportar estadísticas anuales: Si se selecciona esta opción, se anexará una
- tabla con estadísticas anuales a los datos exportados a HTML.
-</p>
-</li>
-<li>
-<p>
-Solo exportar lista: Solo se exportará una lista de inmersiones. No se
- dispondrá de información detallada de los buceos.
-</p>
-</li>
-</ul></div>
-</li>
-<li>
-<p>
-<em>Opciones de estilo</em>: Algunas opciones relativas al estilo de visualización
- en el navegador, como el tamaño de la letra o el tema aplicado.
-</p>
-</li>
-</ul></div>
-</div>
-</div>
-</div>
-<div class="sect1">
-<h2 id="S_Cloud_access">10. Guardar un diario de <em>Subsurface</em> en la Nube</h2>
-<div class="sectionbody">
-<div class="paragraph"><p>Para cualquier buceador, la información contenida en su diario es muy importante.
-No es únicamente un registro de actividades de buceo para su propio placer
-personal, sino que es información importante requerida para su admisión en
-futuros cursos de entrenamiento o (en ocasiones) incluso en puntos de buceo. La
-seguridad del diario es, así pues, crítica. De cara a poseer un diario que pueda
-soportar el fallo del disco duro del ordenador de casa, el robo o la perdida del
-equipo, etc, la <em>nube</em> es una solución obvia. Esto, además, añade el beneficio
-de que se puede acceder al diario, casi, desde cualquier parte del mundo sin
-tener que llevarlo encima. Por este motivo, facilidades como <em>divelogs.de</em> y
-<em>Diving Log</em> ofrecen la posibilidad de guardar dicha información en internet.</p></div>
-<div class="paragraph"><p><em>Subsurface</em> incluye acceso a almacenamiento en la nube integrado de forma
-transparente, disponible para todos los usuarios de Subsurface. Guardar y
-recuperar un divelog desde la nube no es más difícil que hacerlo desde un disco
-duro. El único requisito es que, previamente, nos hemos de registrar como
-usuarios. Para utilizar el <em>Almacenamiento en la nube de Subsurface</em> sigue estos
-pasos:</p></div>
-<div class="sect2">
-<h3 id="_crea_una_cuenta_en_el_almacenamiento_en_la_nube">10.1. Crea una cuenta en el almacenamiento en la nube:</h3>
-<div class="ulist"><ul>
-<li>
-<p>
-Abrir las <em>Preferencias de Red</em> seleccionando <em>Archivo</em> → <em>Preferencias</em> →
- <em>Red</em>.
-</p>
-</li>
-<li>
-<p>
-En la sección llamada <em>Almacenamiento en la nube de Subsurface</em>, introduce un
- correo electrónico que <em>Subsurface</em> pueda utilizar para registrarnos.
-</p>
-</li>
-<li>
-<p>
-Introduce una contraseña que <em>Subsurface</em> utilizará para guardar y recuperar
- el divelog en la nube.
-</p>
-</li>
-<li>
-<p>
-Se clica en <em>Aplicar</em> o en <em>OK</em> para enviar el email y la password al
- servidor en la nube. El servidor responderá con un correo a la dirección
- facilitada que contendrá un PIN de verificación (está será la única ocasión
- en que <em>Subsurface</em> usará la dirección de correo proporcionada). El diálogo
- <em>Preferencias de Red</em> mostrará una nueva casilla de texto, que no se mostraba
- antes, para el PIN.
-</p>
-</li>
-<li>
-<p>
-Se introduce el PIN en la casilla correspondiente del diálogo (Este campo solo
- será visible mientras el servidor espera la confirmación de la dirección de
- correo).
-</p>
-</li>
-<li>
-<p>
-Clica de nuevo en <em>Aplicar</em> o en <em>OK</em> y la cuenta del <em>Almacenamiento
- de Subsurface en la nube</em> se marcará como verificada y se podrá utilizar el
- servicio.
-</p>
-</li>
-</ul></div>
-</div>
-<div class="sect2">
-<h3 id="_usar_el_em_almacenamiento_de_subsurface_en_la_nube_em">10.2. Usar el <em>Almacenamiento de Subsurface en la nube</em></h3>
-<div class="ulist"><ul>
-<li>
-<p>
-Una vez que se ha inicializado el almacenamiento en la nube, aparecen dos
- nuevas opciones en el desplegable <em>Archivo</em> del <em>Menú principal</em>: <em>Abrir
- almacenamiento en la nube</em> y <em>Guardar en almacenamiento en la nube</em>. Estas
- opciones permiten al usuario descargar y guardar los registros en el
- servidor de <em>Subsurface</em> en la nube.
-</p>
-</li>
-<li>
-<p>
-En la pestaña de <em>Preferencias predeterminadas</em> se puede seleccionar usar el
- almacenamiento en la nube como archivo por defecto seleccionando la casilla
- marcada como <em>Archivo por defecto en la nube</em>. Esto significa que los datos
- del almacenamiento en la nube se cargarán al iniciar <em>Subsurface</em> y se
- guardarán allí al salir del programa.
-</p>
-</li>
-<li>
-<p>
-<em>Subsurface</em> mantiene una copia local de los datos y sigue siendo completamente
- funcional si se utiliza desconectado. Simplemente sincronizará los datos con el
- servidor la próxima vez que se utilice el programa y exista conexión a internet.
-</p>
-</li>
-</ul></div>
-</div>
-<div class="sect2">
-<h3 id="S_Cloud_storage">10.3. Acceso web al <em>Almacenamiento de Subsurface en la nube</em></h3>
-<div class="paragraph"><p>Uno de los efectos interesantes de utilizar el <em>Almacenamiento de Subsurface
-en la nube</em> es que también se puede acceder a los datos con cualquier navegador.
-Simplemente se abre <a href="https://cloud.subsurface-divelog.org">https://cloud.subsurface-divelog.org</a>,
-se accede con los mismos e-mail y password, y se pueden visualizar los datos
-del registro hasta la última sincronización efectuada con el <em>Almacenamiento
-en la nube de Subsurface</em>. La información que se muestra son solo los contenidos
-de los registros, NO los valores calculados que aparecen en el panel <strong>Perfil</strong>,
-por ejemplo, presiones de botellas, techos deco o presiones parciales de
-O<sub>2</sub>/He/N<sub>2</sub>.</p></div>
-</div>
-<div class="sect2">
-<h3 id="_otros_servicios_en_la_nube">10.4. Otros servicios en la nube</h3>
-<div class="paragraph"><p>Si se prefiere no usar el almacenamiento en la nube integrado (y no se necesita
-tener acceso vía web a los datos), también resulta muy fácil guardar los
-divelogs en la nube usando uno de los servicios disponibles en internet.</p></div>
-<div class="paragraph"><p>Por ejemplo <a href="http://www.dropbox.com/"><em>Dropbox</em></a> ofrece una aplicación gratuita
-que permite que se vean como locales en nuestro ordenador los archivos guardados
-en sus servidores.</p></div>
-<div class="imageblock" style="text-align:center;">
-<div class="content">
-<img src="images/Cloud.jpg" alt="FIGURE: Carpeta de Dropbox" />
-</div>
-</div>
-<div class="paragraph"><p>El programa <em>Dropbox</em> crea una copia del contenido de <em>Dropbox</em> en la nube, en
-una carpeta de nuestro ordenador. Cuando el ordenador se conecta a internet, el
-contenido de nuestra carpeta y la nube se sincronizan. Así pues, las operaciones
-<em>Abrir</em> y <em>Guardar</em> de los diarios se efectúan sobre la copia local de la carpeta
-<em>Dropbox</em>, no siendo necesario disponer de conexión a internet al realizar estas
-operaciones. Si se modifica la copia local, p.e. al añadir una inmersión, la
-copia en el servidor <em>Dropbox</em> en la <em>nube</em> se actualizará automáticamente al
-volvernos a conectar a internet.</p></div>
-<div class="paragraph"><p>Actualmente el servicio no tiene ningún coste. Dropbox (Windows, Mac y Linux)
-se puede instalar accediendo a la <a href="http://www.dropbox.com/install"><em>página de instalación</em></a>
-<em>de Dropbox</em>.</p></div>
-<div class="paragraph"><p>Como alternativa, se puede utilizar <em>Dropbox</em> como mecanismo para mantener una
-copia de seguridad del diario.</p></div>
-<div class="paragraph"><p>Para guardar un diario en <em>Dropbox</em>, selecciona <em>Archivo→ Guardar como</em> desde
-menú principal de <em>Subsurface</em>, navega a la carpeta Dropbox y selecciona el
-botón <em>Guardar</em>. Para usar el diario en <em>Dropbox</em>, selecciona <em>Archivo→Abrir
-registro</em> desde el menú principal de <em>Subsurface</em>, navega al archivo en la
-carpeta Dropbox y selecciona el botón <em>Abrir</em>.</p></div>
-<div class="paragraph"><p>Existen varios servicios de pago en Internet (Google, Amazon …) con los que
-se puede seguir el mismo proceso para tener los diarios de buceo almacenados en
-la nube.</p></div>
-</div>
-</div>
-</div>
-<div class="sect1">
-<h2 id="S_PrintDivelog">11. Imprimir un diario</h2>
-<div class="sectionbody">
-<div class="paragraph"><p><em>Subsurface</em> proporciona un interfaz simple y flexible para imprimir el diario
-completo o solo unas pocas inmersiones seleccionadas. Se pueden utilizar
-plantillas pre instaladas o escritas a medida para seleccionar donde situar
-los datos en la página.</p></div>
-<div class="paragraph"><p>Antes de imprimir, se deben tomar dos decisiones:</p></div>
-<div class="ulist"><ul>
-<li>
-<p>
-¿ Se desea imprimir el registro completo o solo parte de él ? Si solo se desea
- parte del registro, entonces el usuario selecciona los buceos deseados en el
- panel <strong>Lista de inmersiones</strong>.
-</p>
-</li>
-<li>
-<p>
-¿ Que información sobre presiones parciales de los gases se desea tener en el
- perfil ? El usuario activaría los botones apropiados de la barra de la izquierda
- del panel <strong>Perfil de Inmersión</strong>.
-</p>
-</li>
-</ul></div>
-<div class="paragraph"><p>Si se ha seleccionado_Archivo → Imprimir_ desde el menú principal, aparecerá
-el diálogo siguiente (imagen *A). Se necesita especificar tres cosas para
-conseguir el diseño de información deseado:</p></div>
-<div class="imageblock" style="text-align:center;">
-<div class="content">
-<img src="images/Print1_f22.jpg" alt="FIGURA: Diálogo de imresión" />
-</div>
-</div>
-<div class="olist arabic"><ol class="arabic">
-<li>
-<p>
-En <em>Tipo de impresión</em> seleccionar una de las dos opciones:
-</p>
-<div class="ulist"><ul>
-<li>
-<p>
-<em>Impresión de lista de inmersiones</em>: Imprime buceos de la <strong>Lista de inmersiones</strong>
-con perfiles y otra información.
-</p>
-</li>
-<li>
-<p>
-<em>Impresión de estadísticas</em>: Imprime estadísticas anuales de las inmersiones.
-</p>
-</li>
-</ul></div>
-</li>
-<li>
-<p>
-En <em>Opciones de impresión</em> seleccionar:
-</p>
-<div class="ulist"><ul>
-<li>
-<p>
-<em>Imprimir solo inmersiones seleccionadas</em>. Se imprimirán solo las inmersiones de
-la lista que se hubieran seleccionado previamente. Si no se activa esta casilla,
-se imprimirán <strong>todas</strong> las inmersiones del registro.
-</p>
-</li>
-<li>
-<p>
-<em>Impresión en color</em>. Si no se selecciona se imprimirá en escala de grises
-(blanco y negro).
-</p>
-</li>
-</ul></div>
-</li>
-<li>
-<p>
-En <em>Plantilla</em> seleccionar una plantilla que usar como distribución de la
-página. Existen varias plantillas (ver imagen <strong>B</strong> anterior).
-</p>
-<div class="ulist"><ul>
-<li>
-<p>
-<em>Table</em>: Se imprime una tabla resumen de todas las inmersiones seleccionadas
-(ver imagen).
-</p>
-</li>
-</ul></div>
-</li>
-</ol></div>
-<div class="imageblock" style="text-align:center;">
-<div class="content">
-<img src="images/Print_summarylist_f22.jpg" alt="FIGURA: Imprimir tabla resumen" />
-</div>
-</div>
-<div class="ulist"><ul>
-<li>
-<p>
-<em>Flow layout</em>: Imprime el texto asociado a cada inmersión, sin imprimir los
-perfiles de los buceos (ver imagen):
-</p>
-</li>
-</ul></div>
-<div class="imageblock" style="text-align:center;">
-<div class="content">
-<img src="images/Print_flow_layout_f22.jpg" alt="FIGURE: Print flow layout" />
-</div>
-</div>
-<div class="paragraph"><p>-<em>One Dive</em>: Imprime una inmersión por página, mostrando el perfil (ver imagen)</p></div>
-<div class="imageblock" style="text-align:center;">
-<div class="content">
-<img src="images/print2_f22.jpg" alt="FIGURE: Print one dive / page" />
-</div>
-</div>
-<div class="ulist"><ul>
-<li>
-<p>
-<em>Two Dives</em>: Imprime dos inmersiones por página mostrando los perfiles.
-</p>
-</li>
-<li>
-<p>
-<em>Six Dives</em>: Imprime seis inmersiones por página mostrando los perfiles.
-</p>
-</li>
-</ul></div>
-<div class="paragraph"><p>Los usuarios pueden <em>Previsualizar</em> la página a imprimir pulsando el botón
-<em>Previsualizar</em> del diálogo (ver imagen <strong>A</strong> al inicio de la sección). Tras
-visualizar , se pueden efectuar cambios en las opciones del diálogo de impresión,
-hasta completar una distribución que se ajuste al gusto personal.</p></div>
-<div class="paragraph"><p>A continuación, selecciona el botón <em>Imprimir</em> (ver imagen <strong>A</strong> al inicio de
-esta sección). Esto activa el diálogo normal de impresión del sistema
-operativo, que nos permitirá elegir la impresora y configurar sus propiedades.</p></div>
-<div class="imageblock" style="text-align:center;">
-<div class="content">
-<img src="images/Print_print_f22.jpg" alt="FIGURE: Print one dive / page" />
-</div>
-</div>
-<div class="paragraph"><p>Ajusta la resolución de la impresora a un valor apropiado modificando sus
-propiedades . Finalmente selecciona el botón <em>Print</em> para imprimir los buceos.
-A continuación un ejemplo (bastante pequeño) de la salida de una página.</p></div>
-<div class="imageblock" style="text-align:center;">
-<div class="content">
-<img src="images/Printpreview.jpg" alt="FIGURE: Previsualización de impresión" />
-</div>
-</div>
-<div class="sect2">
-<h3 id="_escribir_una_plantilla_de_impresion_a_medida_avanzado">11.1. Escribir una plantilla de impresión a medida (avanzado)</h3>
-<div class="paragraph"><p>Escribir una plantilla a medida es una forma efectiva de producir impresiones
-altamente personalizadas. Subsurface utiliza plantillas HTML con Grantlee como
-sistema de impresión. Se puede crear una plantilla, exportar una nueva plantilla,
-importar una existente o borrarla. Ver el <a href="#S_APPENDIX_E">APÉNDICE E</a> para ver
-como escribir o modificar una plantilla.</p></div>
-</div>
-</div>
-</div>
-<div class="sect1">
-<h2 id="S_Configure">12. Configurar un ordenador de buceo</h2>
-<div class="sectionbody">
-<div class="paragraph"><p><em>Subsurface</em> permite configurar algunos ordenadores de buceo. En estos momentos,
-los Heinrichs-Weikamp OSTC2 y OSTC3 y los Suunto de la familia Vyper (Stinger,
-Mosquito, D3, Vyper, Vytec, Cobra, Gekko y Zoop). Se pueden leer y modificar un
-gran número de ajustes. En primer lugar hay que asegurarse de tener instalado el
-driver adecuado para el ordenador de buceo y de conocer el nombre de dispositivo
-asignado al ordenador por el sistema operativo.
-Ver el <a href="#_apendice_a_informacion_especifica_del_sistema_operativo_para_importar_inmersiones_desde_un_ordenador_de_buceo">APÉNDICE A</a>
-para información sobre como hacerlo.</p></div>
-<div class="paragraph"><p>Una vez que el ordenador de buceo está al PC con <em>Subsurface</em>, se selecciona
-<em>Archivo → Configurar ordenador de buceo</em> en el menú principal. Si se ha
-indicado el nombre de dispositivo correcto en el campo de texto de la parte
-superior, esto abrirá y seleccionará el modelo correcto en el panel de la
-izquierda (ver imagen a continuación).</p></div>
-<div class="imageblock" style="text-align:center;">
-<div class="content">
-<img src="images/Configure_dc_f20.jpg" alt="FIGURA: Configurar ordenador de buceo" />
-</div>
-</div>
-<div class="paragraph"><p>Utilizando los botones apropiados del panel de configuración, pueden llevarse
-a cabo las siguientes acciones:</p></div>
-<div class="ulist"><ul>
-<li>
-<p>
-<strong>Descargar detalles disponibles</strong>. Descarga a <em>Subsurface</em> la configuración
-del ordenador de buceo, mostrándola en el panel.
-</p>
-</li>
-<li>
-<p>
-<strong>Guardar cambios en el dispositivo</strong>. Esto cambia la configuración del
-ordenador de buceo para hacerla coincidir con la que se muestra en el panel.
-</p>
-</li>
-<li>
-<p>
-<strong>Copia de seguridad</strong>. Guarda los datos de configuración en un archivo.
-<em>Subsurface</em> solicitará una ubicación y un nombre de archivo para guardar la
-información.
-</p>
-</li>
-<li>
-<p>
-<strong>Restaurar copia de seguridad</strong>. Carga la información de un archivo de copia
-de seguridad y la muestra en el panel.
-</p>
-</li>
-<li>
-<p>
-<strong>Actualizar firmware</strong>. Si está disponible un nuevo firmware para el
-ordenador de buceo, este será cargado al mismo.
-</p>
-</li>
-</ul></div>
-</div>
-</div>
-<div class="sect1">
-<h2 id="S_Preferences">13. Ajustar las Preferencias del usuario para <em>Subsurface</em></h2>
-<div class="sectionbody">
-<div class="paragraph"><p>Hay varios ajustes en <em>Subsurface</em> que el usuario puede especificar. Se
-encuentran a través de <em>Archivo → Preferencias</em>. Los ajustes se efectúan en
-siete grupos: <strong>Predeterminados</strong>, <strong>Unidades</strong>, <strong>Gráfico</strong> , <strong>Lenguaje</strong>, <strong>Red</strong>,
-<strong>Facebook</strong> y <strong>Georeferencia</strong>. Las
-siete secciones funcionan con los mismos principios: el usuario debe especificar
-los ajustes que desee modificar, luego guárdarlos usando el botón <strong>Aplicar</strong>.
-Tras aplicarlos todos se puede salir seleccionando <strong>Aceptar</strong> o <strong>Cerrar sin
-guardar</strong> si finalmente decide no hacer los cambios.</p></div>
-<div class="sect2">
-<h3 id="_predeterminados">13.1. Predeterminados</h3>
-<div class="paragraph"><p>Hay varios ajustes en el panel <strong>Predeterminados</strong>:</p></div>
-<div class="imageblock" style="text-align:center;">
-<div class="content">
-<img src="images/Pref1_f20.jpg" alt="FIGURA: Pantalla de Predeterminados en Preferencias" />
-</div>
-</div>
-<div class="ulist"><ul>
-<li>
-<p>
-<strong>Listas y tablas</strong>: Aquí se pueden elegir el tipo de fuente y el tamaño de la
- misma en el panel <strong>Lista de inmersiones</strong>. Reduciendo el tamaño de la fuente, se
- pueden ver más buceos en una sola pantalla.
-</p>
-</li>
-<li>
-<p>
-<strong>Inmersiones</strong>: En este bloque se especifica la carpeta y nombre de archivo
- del registro de buceo electrónico. Es un archivo con extensión .xml o .ssrf. Al iniciar
- <em>Subsurface</em> sin argumentos cargará automáticamente el registro especificado
- aquí. Existen tres opciones:
-</p>
-<div class="ulist"><ul>
-<li>
-<p>
-<em>Sin archivo por defecto</em>: Si se selecciona, <em>Subsurface</em> no abre ningún
- archivo automáticamente al iniciarse
-</p>
-</li>
-<li>
-<p>
-<em>Archivo por defecto local</em>: Si se selecciona, <em>Subsurface</em> abre un archivo
- del disco duro local al iniciarse.
-</p>
-</li>
-<li>
-<p>
-<em>Archivo por defecto en la nube</em>: Si se selecciona, <em>Subsurface</em> abre el
- divelog en la nube que se inicializó desde la pestaña <em>Red</em> de las
- <strong>Preferencias</strong> (ver a continuación).
-</p>
-</li>
-</ul></div>
-</li>
-<li>
-<p>
-<strong>Mostrar invalidas</strong>: Las inmersiones pueden marcarse como "invalidas" (cuando
- el usuario desea ocultar buceos que no considere validos, p.e. en piscina, pero
- aún quiera mantenerlos registrados en el diario). Esta opción controla si estas
- inmersiones se muestran en la lista.
-</p>
-</li>
-<li>
-<p>
-<strong>Botella por defecto</strong>: Se puede especificar una botella por defecto de las
- que aparecen listadas en la pestaña <strong>Equipo</strong> del panel <strong>Notas</strong>.
- Es muy cómodo si se bucea habitualmente con el mismo tipo de botella, asigna a
- cada nueva inmersión una botella del tipo aquí definido.
-</p>
-</li>
-<li>
-<p>
-<strong>Animaciones</strong>: Algunas acciones, al mostrar el perfil, se ejecutan utilizando
- animaciones. Por ejemplo, los valores de los ejes para la profundidad y el
- tiempo cambian de una inmersión a otra. Al visualizar inmersiones distintas
- estos cambios en las características de los ejes no suceden de forma
- instantánea, sino que son animados. La <em>Velocidad</em> de las animaciones puede
- controlarse ajustando esta regleta, con mayor velocidad a la izquierda y
- significando "0" ninguna animación en absoluto.
-</p>
-</li>
-<li>
-<p>
-<strong>Servicio web de Subsurface</strong>: Cuando uno se suscribe al <a href="#S_Companion">servicio web de Subsurface</a>, se proporciona una ID de usuario muy larga y
- difícil de recordar. Este es el lugar donde guardar esa ID. Seleccionando la
- opción <em>¿Guardar localmente la ID de usuario?</em> nos aseguramos de que se guarda
- una copia de dicha ID en el ordenador.
-</p>
-</li>
-<li>
-<p>
-<strong>Borrar todos los ajustes</strong> Tal como se indica en el botón bajo esta cabecera,
- se borran todos los ajustes y se reinician con los valores por defecto.
-</p>
-</li>
-</ul></div>
-</div>
-<div class="sect2">
-<h3 id="_unidades">13.2. Unidades</h3>
-<div class="imageblock" style="text-align:center;">
-<div class="content">
-<img src="images/Pref2_f20.jpg" alt="FIGURA: Página de preferencias de unidades" />
-</div>
-</div>
-<div class="paragraph"><p>Aquí el usuario puede elegir entre medidas métricas o imperiales para
-profundidad, presión, volumen, temperatura y masa. Al seleccionar el botón de
-Métrico o Imperial de arriba, el usuario indica que todas las unidades vayan en
-las correspondientes al sistema elegido. Como alternativa, si se selecciona
-<strong>Personalizar</strong> se pueden mezclar, con algunas medidas en métrico y otras en
-imperial.</p></div>
-<div class="paragraph"><p>Independientemente de los ajustes citados, en la opción <em>Unidades de tiempo</em>
-se puede elegir si se desea que las
-velocidades de ascenso/descenso se muestren en m/s o en m/min. Los buzos con
-botella, habitualmente, manejan velocidades en m/min, sin embargo, los apneístas
-ascienden mucho más deprisa por lo que suelen utilizar velocidades en m/s.
-Igualmente, las coordenadas GPS pueden representarse de la forma tradiciona
-(grados, minutos, segundos) o como grados con decimales, elige la más adecuada
-a tus necesidades.</p></div>
-</div>
-<div class="sect2">
-<h3 id="_grafico">13.3. Gráfico</h3>
-<div class="imageblock" id="S_CCR_options" style="text-align:center;">
-<div class="content">
-<img src="images/Pref3_f20.jpg" alt="FIGURA: Página de Preferencias del gráfico" />
-</div>
-</div>
-<div class="paragraph" id="S_GradientFactors"><p>Este panel permite dos tipos de selecciones:</p></div>
-<div class="ulist"><ul>
-<li>
-<p>
-<strong>Mostrar</strong>: Aquí los usuarios eligen la cantidad de información que se muestra
- como parte del perfil de la inmersión:
-</p>
-<div class="ulist"><ul>
-<li>
-<p>
-<em>Umbrales</em>: <em>Subsurface</em> puede mostrar las presiones parciales de nitrógeno,
- oxígeno y helio durante el buceo. Se activan utilizando la barra de herramientas
- de la izquierda de panel <strong>Perfil de inmersión</strong>. Para cada uno de estos gases,
- los usuarios puede especifica un valor umbral a la derecha en el panel de
- Preferencias. Si cualquiera de los gráficos sube por encima de este nivel,
- entonces el gráfico se resalta en rojo, indicando que se ha excedido dicho
- umbral de presión parcial.
-</p>
-</li>
-<li>
-<p>
-<em>Max pO<sub>2</sub> al mostrar PMO</em> es el valor usado para calcular la profundidad
- máxima operativa (PMO) de un gas. Especifica una presión parcial apropiada.
- Habitualmente se usa un valor de 1.4.
-</p>
-</li>
-<li>
-<p>
-<em>Trazar en rojo el techo informado por el ordenador de buceo</em>: Esta casilla
- seleccionable permite exactamente lo que dice. El color por defecto es blanco.
- No todos los ordenadores de buceo
- facilitan los valores de los techos. Si el ordenador de buceo lo facilita, puede
- diferir de los techos calculados por <em>Subsurface</em>. Esto se debe al uso de
- diferentes algoritmos, diferentes factores de gradiente y a la forma dinámica en
- que los ordenadores de buceo calculan los techos durante la inmersión.
-</p>
-</li>
-<li>
-<p>
-<em>Mostrar botellas no usadas en la pestaña equipo</em>: Esta casilla seleccionable
- permite mostrar información sobre botellas que no se han utilizado durante la
- inmersión, en la pestaña Equipo. Por el contrario, si la casilla no está
- seleccionada, cualquier botella que se haya registrado en la pestaña Equipo y no
- haya sido utilizada (p.e. botellas de bail-out) se omiten en la lista mostrada
- aunque siguen estando guardadas.
-</p>
-</li>
-<li>
-<p>
-<em>Mostrar la profundidad media</em>: Activar esta casilla hace que <em>Subsurface</em>
- trace una línea gris a través del perfil, indicando la profundidad media del
- buceo en cada momento de la inmersión. Normalmente es una línea con forma de
- "u" que indicará la profundidad media mayor justo antes de iniciar el ascenso.
-</p>
-</li>
-</ul></div>
-</li>
-<li>
-<p>
-<strong>Varios</strong>:
-</p>
-<div class="ulist" id="GradientFactors_Ref"><ul>
-<li>
-<p>
-Factores de gradiente (GF_bajo y GF_alto)<strong>: Se fijan los <em>factores
- de gradiente</em> usados en la inmersión. El GF_bajo es el factor de gradiente a
- mayores profundidades y el GF_alto se usa justo debajo de la superficie. A
- profundidades intermedias se usan factores entre GF_bajo y GF_alto. Los factores
- de gradiente añaden conservadurismo a la exposición al nitrógeno durante un
- buceo, del mismo modo que muchos ordenadores de buceo tienen un ajuste del
- conservadurismo. Cuanto menor sea el valor de un factor de gradiente, más
- conservativos son los cálculos en relación a la carga de nitrógeno y más
- profundos serán los techos durante el ascenso. Factores de gradiente de 20/60
- son considerados conservadores y valores de 70/90 se consideran agresivos.
- Seleccionar la casilla *GF bajo a la máxima profundidad</strong> hace que se use el
- GF_bajo en la mayor profundidad de la inmersión. Si no se selecciona, GF_bajo se
- aplica a todas las profundidades mayores que la primera parada deco. Para más
- información, ver:
-</p>
-<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>
-</li>
-<li>
-<p>
-<em>CCR: Mostrar setpoints al visualizar pO<sub>2</sub></em>: Con esta casilla activada, el
- gráfico de pO<sub>2</sub> del perfil mostrará una línea en rojo que indicará los
- valores de setpoint del CCR. Véase la sección en <a href="#S_CCR_dives">Inmersiones con rebreather de circuito cerrado</a>.
-</p>
-</li>
-<li>
-<p>
-<em>CCR: Mostrar los valores de los sensores de O<sub>2</sub> al visualizar la pO<sub>2</sub></em>:
- Muestra los valores de pO<sub>2</sub> asociados con cada uno de los sensores de
- oxígeno de un sistema CCR. Ver la sección <a href="#S_CCR_dives">Inmersiones con rebreather de circuito cerrado</a>.
-</p>
-</li>
-</ul></div>
-</li>
-<li>
-<p>
-<strong>Configurar la planificación de inmersiones usando equipo de rebreather</strong>:
-</p>
-<div class="ulist"><ul>
-<li>
-<p>
-<em>Setpoint del CCR por defecto para la planificación de inmersiones</em>:
- Especifica el setpoint de O<sub>2</sub> para planificar buceos con CCR. Este valor
- determinará la pO<sub>2</sub> a mantener durante una inmersión. Los cambios
- efectuados durante el buceo se pueden añadir a través del menú contextual
- del perfil.
-</p>
-</li>
-<li>
-<p>
-<em>pSCR Ratio de O<sub>2</sub> en el metabolismo</em>: Para un rebreather semicerrado (pSCR)
- este es el volumen de oxígeno usado por el buceador en un minuto. Fija este
- valor para planificar buceos con pSCR y cálculos de descompresión.
-</p>
-</li>
-<li>
-<p>
-<em>pSCR Ratio</em>: En equipos pSCR el ratio de vertido es la cantidad de gas
- expulsada del circuito frente a la cantidad de gas recirculada en el circuito.
- Fija este valor para planificar buceos con pSCR. Se suele usar un ratio 1:10
-</p>
-</li>
-</ul></div>
-</li>
-</ul></div>
-</div>
-<div class="sect2">
-<h3 id="_lenguaje">13.4. Lenguaje</h3>
-<div class="paragraph"><p>Se elige el lenguaje que debe utilizar <em>Subsurface</em>.</p></div>
-<div class="imageblock" style="text-align:center;">
-<div class="content">
-<img src="images/Pref4_f20.jpg" alt="FIGURA: página de preferencias de lenguaje" />
-</div>
-</div>
-<div class="paragraph"><p>Una casilla de selección permite usar el lenguaje <em>Predeterminado del sistema</em>
-que, en la mayoría de los casos será el ajuste correcto; con esto <em>Subsurface</em>
-simplemente se ejecuta con los mismos ajustes de lenguaje/país que el SO
-subyacente. Si esto, por alguna razón, no fuera deseable, se puede deseleccionar
-la casilla y elegir una de las combinaciones de lenguaje/país incluidas en la
-lista de traducciones. La casilla de texto <em>Filtro</em> permite listar lenguajes
-similares. Por ejemplo hay diversas variantes de inglés o francés.</p></div>
-</div>
-<div class="sect2">
-<h3 id="_red">13.5. Red</h3>
-<div class="paragraph"><p>Este panel facilita la comunicación entre <em>Subsurface</em> y las fuentes de datos en
-internet.</p></div>
-<div class="paragraph"><p>Esto es importante cuando <em>Subsurface</em> tiene que comunicarse con servicios como
-el <a href="#S_Companion">servicio web de <em>Subsurface</em></a> o importar/exportar datos de
-<em>Divelogs.de</em>. El acceso a internet viene determinado por el tipo de conexión y
-por el proveedor de acceso (ISP) utilizado. El ISP debería proporcionar la
-información necesaria.</p></div>
-<div class="imageblock" style="text-align:center;">
-<div class="content">
-<img src="images/Pref5_f20.jpg" alt="FIGURA: página de preferencias de red" />
-</div>
-</div>
-<div class="paragraph"><p>Este diálogo tiene tres secciones:</p></div>
-<div class="ulist"><ul>
-<li>
-<p>
-<em>Tipo de proxy</em>:
- Si se utiliza un servidor proxy para acceder a internet, el tipo de proxy se
- selecciona del desplegable, tras
- lo cual debe facilitarse la dirección IP del servidor y el número de puerto. Si
- el servidor proxy utiliza autenticación también han de indicarse el usuario y su
- password para que <em>Subsurface</em> pueda pasar automáticamente a través del proxy
- para acceder a internet.
-</p>
-</li>
-<li>
-<p>
-<em>Almacenamiento en la nube de Subsurface</em>:
- Para poder guardar nuestro divelog en la nube, se precisa una dirección
- de correo electrónico y una password. Esto permite a <em>Subsurface</em> mandar
- un correo electrónico al usuario con información de seguridad relativa al
- almacenamiento en la nube. Tiene dos opciones adicionales:
-</p>
-<div class="ulist"><ul>
-<li>
-<p>
-<em>Sincronizar con la nube en segundo plano</em>: Permite guardar la información
- en la nube mientras el usuario lleva a cabo otras tareas en <em>Subsurface</em>.
-</p>
-</li>
-<li>
-<p>
-<em>Guardar contraseña localmente</em>: Permite guardar la contraseña de acceso
- a la nube en el disco duro. ¡¡¡ OJO !!! La contraseña se guarda en texto
- plano sin encriptar.
-</p>
-</li>
-</ul></div>
-</li>
-<li>
-<p>
-<em>Servicio web de Subsurface</em>:
- Al suscribirnos al <a href="#S_Companion">Servicio web de Subsurface</a>, se nos
- facilita una identificación de usuario muy larga y dificil de recordar.
- Este es el lugar donde guardarla. Seleccionando la opción, nos asegurammos
- de tener una copia local de la misma.
-</p>
-</li>
-</ul></div>
-</div>
-<div class="sect2">
-<h3 id="S_Facebook">13.6. Acceso a Facebook</h3>
-<div class="paragraph"><p>Este panel nos permite acceder a una cuenta de <em>Facebook</em> para poder enviar
-información desde <em>Subsurface</em>.</p></div>
-<div class="imageblock" style="text-align:center;">
-<div class="content">
-<img src="images/Pref6_f20.jpg" alt="FIGURE: Facebook login panel" />
-</div>
-</div>
-<div class="paragraph"><p>Si se proporciona un usuario y una clave validos, se crea una conexión a
-<em>Facebook</em>. La conexión se cierra cuando al cerrar <em>Subsurface</em>. La casilla
-seleccionable "No cerrar sesión con Subsurface" de la pantalla de acceso no
-tiene ningún efecto, en estos momentos.
-Ver la sección <a href="#S_facebook">Exportar perfiles de inmersión a Facebook</a>
-para más información.</p></div>
-</div>
-<div class="sect2">
-<h3 id="_georefencia">13.7. Georefencia</h3>
-<div class="paragraph"><p><em>Subsurface</em> proporciona un servicio de búsqueda geográfica (Esto es, la
-capacidad de buscar el nombre de un lugar, en base a unas coordenadas
-geográficas proporcionadas haciendo clic en el panel <strong>Globo</strong>, de un GPS o
-desde la app <em>Subsurface companion</em>) basado en internet, que localiza el
-nombre conocido más cercano a nuestra posición. Obviamente la función solo
-actúa con conexión a internet. La configuración se puede efectuar como en
-la imagen a continuación</p></div>
-<div class="imageblock" style="text-align:center;">
-<div class="content">
-<img src="images/Pref7_f20.jpg" alt="FIGURE: Facebook login panel" />
-</div>
-</div>
-</div>
-</div>
-</div>
-<div class="sect1">
-<h2 id="S_DivePlanner">14. El Planificador de <em>Subsurface</em></h2>
-<div class="sectionbody">
-<div class="paragraph"><p>La planificación de inmersiones es una característica avanzada de <em>Subsurface</em>
-accesible desde <em>Registro → Planificar Inmersión</em> en el menú principal. Permite
-calcular la carga de gases inertes durante una inmersión utilizando el algoritmo
-Bühlmann ZHL16 con factores de gradiente tal y como lo implementó 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">Esta prestación <strong>ES EXPERIMENTAL</strong> y supone que el usuario ya está familiarizado
-con el interfaz de <em>Subsurface</em>. Se utiliza <strong>EXPLICITAMENTE</strong> bajo las siguientes
-condiciones:</td>
-</tr></table>
-</div>
-<div class="ulist"><ul>
-<li>
-<p>
-El usuario está versado en la planificación de inmersiones y tiene el
- entrenamiento necesario para planificar inmersiones.
-</p>
-</li>
-<li>
-<p>
-El usuario planifica buceos dentro de los límites para los que está
- certificado.
-</p>
-</li>
-<li>
-<p>
-La planificación de inmersiones hace grandes suposiciones sobre las
- características de la <em>persona media</em> y no puede compensar las características
- fisiológicas individuales , de salud o de estilos de vida.
-</p>
-</li>
-<li>
-<p>
-La seguridad de un plan de buceo depende mucho de la forma en que se use el
- planificador.
-</p>
-</li>
-<li>
-<p>
-El usuario esta familiarizado con la interfaz de usuario de <em>Subsurface</em>.
-</p>
-</li>
-<li>
-<p>
-Un usuario que no este completamente seguro de cualquiera de los requisitos
- anteriores, no debería utilizar esta capacidad de <em>Subsurface</em>.
-</p>
-</li>
-</ul></div>
-</div></div>
-<div class="sect2">
-<h3 id="_la_pantalla_del_planificador_de_em_subsurface_em">14.1. La pantalla del planificador de <em>Subsurface</em></h3>
-<div class="paragraph"><p>Al igual que el diario de <em>Subsurface</em>, la pantalla del planificador se divide
-en varias secciones (ver imagen a continuación). Los parámetros de ajuste de una
-inmersión se introducen en las diversas secciones a la izquierda de la pantalla.
-El ajuste se divide en varias secciones: Gases disponibles, Ritmos, Planificar,
-Opciones de gases y Notas.</p></div>
-<div class="paragraph"><p>Arriba a la derecha hay un <strong>panel de diseño</strong> verde sobre el cual puede
-manipularse directamente el perfil de inmersión arrastrando y haciendo clic como
-se explica a continuación. Esta característica hace al planificador de
-<em>Subsurface</em> único en facilidad de uso.</p></div>
-<div class="paragraph"><p>Abajo a la derecha hay un panel de texto con la cabecera <em>Detalle del Plan</em>.
-Aquí es donde se proporcionan los detalles del plan de inmersión de forma que
-pueda copiarse con facilidad a otro software. También es donde se imprimirá
-cualquier mensaje de aviso sobre el plan de buceo.</p></div>
-<div class="imageblock" style="text-align:center;">
-<div class="content">
-<img src="images/PlannerWindow1_f20.jpg" alt="FIGURA: Ventana de inicio del planificador" />
-</div>
-</div>
-</div>
-<div class="sect2">
-<h3 id="_inmersiones_con_circuito_abierto">14.2. Inmersiones con circuito abierto</h3>
-<div class="ulist"><ul>
-<li>
-<p>
-En la parte de abajo al centro del planificador (círculo azul en la imágen
- anterior) hay un desplegable con tres opciones. Selecciona la correcta
- entre ellas:
-</p>
-<div class="ulist"><ul>
-<li>
-<p>
-Circuito abierto (por defecto)
-</p>
-</li>
-<li>
-<p>
-CCR
-</p>
-</li>
-<li>
-<p>
-pSCR
-</p>
-</li>
-</ul></div>
-</li>
-<li>
-<p>
-En el área de arriba a la izquierda de la pantalla del planificador, hay que
- asegurarse de que los parámetros constantes son correctos. Son: Fecha y hora
- de inicio de la inmersión, Presión atmosférica, y altura sobre el nivel del
- mar. Estos dos últimos están relacionados, variando uno se modifica el otro.
- La presión atmosférica por defecto a nivel del mar son 1.013 bar.
-</p>
-</li>
-<li>
-<p>
-En la tabla etiquetada como <em>Gases disponibles</em>, añadir la información de las
- botellas que se han de utilizar y la composición de los gases de cada botella.
- Esto se hace de forma similar a <a href="#cylinder_definitions">como se rellena la información de botellas en un diario</a>. Se elige el tipo de botella de la lista desplegable
- y se especifica la presión de trabajo de la botella. Si dejamos en blanco la
- concentración de oxígeno (O2%) se asume que el gas que contiene es aire. En otro
- caso, se introducen las concentraciones de oxígeno y/o helio en las casillas del
- diálogo. Si es necesario , se añaden botellas utilizando el icono "+" de arriba
- a la derecha.
-</p>
-</li>
-<li>
-<p>
-El perfil del buceo a planificar se puede crear de dos maneras:
-</p>
-<div class="ulist"><ul>
-<li>
-<p>
-Arrastrar los puntos del perfil
- (los pequeños círculos blancos) para que representen la inmersión. Se pueden
- crear puntos adicionales haciendo doble-clic sobre el perfil de buceo. Se
- pueden borrar haciendo clic-derecho en un punto concreto y seleccionando
- <em>borrar</em> en el menú contextual.
-</p>
-</li>
-<li>
-<p>
-La forma más eficiente de crear un perfil es introducir los valores
- apropiados en la tabla llamada <em>Puntos del planificador de inmersiones</em>.
- La primera línea de la tabla representa la duración y profundidad final
- de un descenso desde superficie. Los segmentos siguientes describirán la
- fase de fondo de la inmersión. La columna <em>CC set point</em> solo es relevante
- para para buceadores en circuito cerrado.
- El ascenso, normalmente, no se especifica, ya que esto es lo que se supone
- que el planificador debe calcular.
- Añade segmentos adicionales al perfil utilizando el icono "+" arriba a la
- derecha de la tabla. Los segmentos introducidos en la tabla aparecen de
- forma automática en el diagrama "Perfil de la inmersión".
-</p>
-</li>
-</ul></div>
-</li>
-</ul></div>
-<div class="sect3">
-<h4 id="_inmersiones_recreativas">14.2.1. Inmersiones recreativas</h4>
-<div class="paragraph"><p>El modo recreativo es lo que más se aproxima a planificar una inmersión
-basándonos en el límite de no descompresión (LND). Tiene en cuenta el tiempo
-que un buceador puede estar a la profundidad actual sin incurrir en paradas
-de descompresión obligatorias, y usando el gas disponible menos una reserva.
-El planificador tiene en cuenta automáticamente la carga nitrógeno acumulada
-en inmersiones previas. Sin embargo, las tablas convencionales también tienen
-en cuenta los buceos anteriores ¿Por qué utilizar un planificador para buceos
-recreativos? Al utilizar las tablas recreativas se tiene en cuenta la máxima
-profundidad de una inmersión. Sin embargo, pocas inmersiones se efectúan a
-una profundidad constante que corresponda con la máxima (perfil "cuadrado").
-Esto supone que las tablas sobre estiman la carga de nitrógeno acumulada de
-las inmersiones previas. El planificador de <em>Subsurface</em> calcula la carga de
-nitrógeno de acuerdo con los perfiles reales de las inmersiones anteriores de
-forma similar a como lo hacen los ordenadores de buceo durante la inmersión.
-Esto significa que el buceador es "bonificado" por no permanecer a profundidad
-máxima en las inmersiones anteriores, permitiendo planificar una inmersión
-posterior más larga. Para que el planificador funcione es, pues, crucial haber
-descargado a <em>Subsurface</em> todas las inmersiones anteriores antes de hacer la
-planificación.</p></div>
-<div class="paragraph"><p>Para planificar un buceo, es necesario definir los ajustes apropiados.</p></div>
-<div class="ulist"><ul>
-<li>
-<p>
-Asegurarse de que el día y la hora se han ajustado a los de la inmersión
-planeada. Esto permite calcular la carga de nitrógeno de los buceos anteriores.
-</p>
-</li>
-<li>
-<p>
-Justo bajo la cabecera <em>Planificar</em> hay dos casillas seleccionables
- <em>Recreativo</em> y <em>Parada de seguridad</em>. Para inmersiones recreativas se seleccionan
- ambas casillas.
-</p>
-</li>
-<li>
-<p>
-Luego se define el tamaño de las botellas, la mezcla de gas (aire o % de
- oxígeno) y la presión inicial de las botellas en la parte superior izquierda
- del planificador, en <em>Gases disponibles</em>.
-</p>
-</li>
-<li>
-<p>
-El planificador calcula si la botella elegida contiene suficiente aire/gas
- para completar la inmersión planeada. Para que esto sea realista, bajo
- <em>Opciones de gases</em>, se especifica un consumo de aire en superficie (CAS)
- adecuado para la opción <em>CAS en fondo</em>. Los valores adecuados se situarían
- entre 15 l/min y 30 l/min, siendo para buceadores noveles o buceos difíciles
- próximos a 30 l/min.
-</p>
-</li>
-<li>
-<p>
-Definir la cantidad de gas que se pretende que sobre en la botella al final
- de la inmersión, justo antes de iniciar el ascenso. Se suele usar un valor de
- 50 bar. La razón para esta reserva de gas guardarlo para una posible
- necesidad de ascender compartiendo aire con el compañero. Es bastante
- difícil estimar cuanto gas se usaría al compartir, así que la mayoría de
- agencias establecen una cantidad fija p.e 40 o 50 bares. <em>Subsurface</em> aún lo
- hace mejor, porque conoce el ascenso y tiene en cuenta el gas consumido en
- el mismo. Además de esto, <em>Subsurface</em> aún utiliza una reserva fija de
- presión. La cantidad de gas de esta reserva puede ser configurada por el
- usuario.
-</p>
-</li>
-<li>
-<p>
-Definir la profundidad de la inmersión arrastrando los puntos blancos en el
- perfil o introduciendo la profundidad en la tabla que se encuentra en <em>Puntos
- del planificador de inmersiones</em>. Si se tratara de una inmersión multinivel,
- se añaden los puntos necesarios que representen el plan, bien añadiéndolos en
- el perfil de la inmersión, bien en la tabla citada. <em>Subsurface</em> extenderá
- la sección de fondo de la inmersión a la duración máxima dentro del LND.
-</p>
-</li>
-<li>
-<p>
-Se puede modificar la velocidad de ascenso. Las velocidades de ascenso
- establecidas por defecto son aquellas consideradas seguras para el buceo
- recreativo.
-</p>
-</li>
-<li>
-<p>
-El perfil del planificador indica el tiempo máximo de inmersión dentro de
-los límites de no descompresión, utilizando el algoritmo Bülmann ZH-L16 y el
-gas y la profundidad especificados como se ha descrito anteriormente. El
-planificador de <em>Subsurface</em> permite una visualización rápida de la duración
-de una inmersión en función de la profundidad, teniendo en cuenta la carga de
-nitrógeno residual resultante de las inmersiones previas. El plan de buceo
-incluye una estimación de la cantidad de aire/gas que se va a utilizar,
-dependiendo de los ajustes de las botellas especificadas en <em>Gases disponibles</em>.
-Si la presión inicial de la botella se ajusta a "0", la duración del buceo que
-se mostrará será el auténtico límite de no descompresión (LND) sin tener en
-cuenta el gas utilizado durante la inmersión. Si la superficie sobre el perfil
-se vuelve roja, significa que se han sobrepasado los límites del buceo recreativo
-y se necesita reducir, bien la profundidad, bien la duración.
-</p>
-</li>
-</ul></div>
-<div class="paragraph"><p>A continuación se muestra una imagen de un plan para una inmersión recreativa
-a 30 metros. Aunque el límite de no descompresión es 23 minutos, la duración
-del buceo se ve limitada por la cantidad de aire en la botella, reflejada por
-la ventana de texto informativa abajo a la derecha del panel en la que se nos
-indica que no existe suficiente gas para compartir con el compañero durante el
-ascenso.</p></div>
-<div class="imageblock" style="text-align:center;">
-<div class="content">
-<img src="images/rec_diveplan.jpg" alt="FIGURE: A recreational dive plan: setup" />
-</div>
-</div>
-</div>
-<div class="sect3">
-<h4 id="_inmersiones_en_circuito_abierto_no_recreativas_incluyendo_descompresion">14.2.2. Inmersiones en circuito abierto no recreativas, incluyendo descompresión</h4>
-<div class="paragraph"><p>La planificación no recreativa supone exceder los límites de no descompresión
-y/o utilizar múltiples gases. Tales inmersiones se planifican en tres fases:</p></div>
-<div class="paragraph"><p><strong>a) Control de gases inertes</strong>: Esto se consigue especificando las velocidades
-de descenso y ascenso, así como el modelo descompresivo (GF bajo y GF alto o
-nivel de conservadurismo) bajo los encabezamientos <em>Velocidades</em> y <em>Planificar</em>
-en la parte inferior de la pantalla de planificación. Están soportados dos
-modelos descompresivos, el modelo Bühlmann y el modelo VPM-B. Elige uno de los
-dos modelos. Si se selecciona el modelo Bühlmann, se necesita especificar los
-factores de gradiente (GF_alto y GF_bajo). En principio se utilizarán los
-factores de gradiente especificados en la pantalla de <em>Preferencias</em> de
-<em>Subsurface</em>. Si se modifican en el planificador(ver <em>Opciones de gases</em>), se
-utilizan los nuevos valores sin modificar los marcados en las <em>Preferencias</em>.
-Los ajustes de los factores de gradiente afectan enormemente a los techos
-calculados y sus profundidades.
-Un <em>GF bajo</em> muy pequeño produce paradas de descompresión más pronto durante la
-inmersión.
-** Para más información sobre factores de gradiente visita la sección
-<a href="#S_GradientFactors">Ajustes de la Preferencias de factores de gradiente</a>.</p></div>
-<div class="paragraph"><p>Si se seleccioná ell modelo VPM-B, es necesario especificar el nivel de
-conservadurismo, en una escala de 0 (menos conservador) a 4 (más conservador).
-Este modelo tiende a dar paradas deco a mayores profundidades que el modelo de
-Bühlmann y, a menudo, produce perfiles ligeramente más cortos que este último.
-Cuando elijas uno de los modelos, recuerda que no son modelos fisiológicos
-exactos, sino modelos matemáticos que parecen funcionar en la práctica.</p></div>
-<div class="paragraph"><p>Para más información externa a este manual ver:</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, por 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&ie=UTF8&qid=1403932320&sr=1-1&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. Un excelente estudio no técnico en el que se discuten ambos modelos, el de Bühlmann y el VPM-B.
-</p>
-</li>
-</ul></div>
-<div class="paragraph"><p>La velocidad de ascenso es crítica para la desgasificación al final de la
-inmersión y se especifica para varios rangos utilizando la profundidad media
-como vara de medir. La profundidad media del plan se indica como una línea gris
-sobre el perfil. Las velocidades de ascenso en los niveles más
-profundos se sitúan, a menudo, en el rango de 8 a 12 m/min, mientras que en los
-niveles más superficiales suelen estar en los 3 a 6 m/min llegando en ocasiones
-a 1 m/min. La velocidad de descenso también se especifica. Si activamos la
-opción <em>Caer a la primera profundidad</em> , la fase de descenso se efectuará a la
-máxima velocidad indicada en la sección <em>Velocidades</em> de los ajustes.</p></div>
-<div class="paragraph"><p><strong>b) Control del oxígeno</strong>: En las <em>Opciones de gases</em> es necesario
-especificar la máxima presión parcial de oxígeno para la parte del fondo
-(<em>pO2 en fondo</em> ) y también para la fase de descompresión (<em>pO2 en deco</em>).
-Los valores más comunes son 1.4 bar para el fondo de la inmersión y 1.6 bar
-para las paradas de descompresión. Habitualmente no se excede una presión
-parcial de 1.6 bar de O2. Los ajustes de pO2 y la profundidad a la que cambiar
-de gases también pueden editarse en el diálogo <em>Gases disponibles</em>. Normalmente
-el planificador decide el cambio a otro gas cuando, durante el ascenso, la
-presión parcial del nuevo gas se sitúa por debajo de 1.6 bar.</p></div>
-<div class="paragraph"><p><strong>c) Control del gas</strong>: En inmersiones con circuito abierto esta es una
-consideración prioritaria. Es necesario mantenerse en los límites de la cantidad
-de gas de la botella, manteniendo un margen de seguridad apropiado para regresar
-a superficie, posiblemente compartiendo gas con un compañero. En las <em>Opciones
-de gases</em> especifica la mejor (pero conservativa) estimación de tu "consumo de
-aire equivalente a superficie" (CAS, del inglés SAC, también llamado RMV) en
-litros/minuto (en estos momentos solo están soportadas las unidades del Sistema
-Internacional). Se especifica el CAS para el fondo (<em>CAS en fondo</em>) y también
-para la fase de descompresión (<em>CAS en deco</em>). Son comunes valores de 15 a
-30 l/min. Para hacer una buena gestión del gas, una regla del pulgar no es
-suficiente y se necesita monitorizar el consumo regularmente, dependiendo de
-diferentes condiciones ambientales y de equipo. El planificador calculará el
-volumen total de gas a utilizar durante la inmersión y emitirá un aviso si se
-excede la cantidad total de gas disponible. Las buenas prácticas exigen que no
-se bucee al límite del gas disponible, sino que se mantenga una reserva de gas
-apropiada para atender circunstancias imprevistas. En el caso del buceo técnico,
-esta reserva puede ser, fácilmente, del 66% del gas disponible.</p></div>
-<div class="paragraph"><p>Ahora, por fin, se puede empezar la planificación detallada de tiempos y
-profundidades. <em>Subsurface</em> ofrece una interfaz gráfica única para llevar a cabo
-esta parte de la planificación. El mecanismo es similar a introducir a mano un
-perfil en el diario de inmersiones. Al activar el planificador, se genera un
-perfil por defecto de 40 minutos a 15 metros. Los puntos blancos (puntos de
-paso) del perfil, se pueden arrastrar con el ratón. Se crean más puntos haciendo
-doble-clic en la línea del perfil. Se arrastran los puntos de paso paso hasta
-estar seguros de que el perfil refleja la inmersión que se pretende efectuar.
-No es necesario especificar la fase de ascenso ya que será calculada por el
-planificador basándose en los ajustes que se hayan especificado.
-Si se sobrepasa cualquiera de los límites establecidos, la superficie sobre el
-perfil se volverá roja.</p></div>
-<div class="paragraph"><p>Cada punto de paso en el perfil crea un <em>punto en el planificador</em> en la tabla
-a la izquierda del panel del planificador. Hay que asegurarse de que el valor
-del <em>Gas usado</em> en cada fila de esta tabla corresponde a una de las mezclas
-especificadas en la tabla de <em>Gases disponibles</em>. Se añaden nuevos puntos hasta
-que las principales características del buceo estén completas, p.e. el segmento
-de tiempo en el fondo y paradas profundas (si se implementan). Se dejan los
-restantes puntos del ascenso a <em>Subsurface</em>. En la mayoría de los casos
-<em>Subsurface</em> calcula puntos de paso adicionales para completar los requisitos
-de descompresión de la inmersión.</p></div>
-<div class="paragraph"><p>Los puntos de paso relacionados en el diálogo <em>Puntos del planificador</em> pueden
-editarse a mano para obtener una representación precisa del plan. De hecho
-podría crearse el plan completo editando los puntos desde el diálogo.</p></div>
-<div class="paragraph"><p>Indica cualquier cambio de gas, tal como se explicaba en la sección
-<a href="#S_CreateProfile">Crear a mano un perfil de inmersión</a>. Estos cambios deberían
-reflejar las botellas y composiciones de gas definidas en la table <em>Gases
-disponibles</em>. Si se usan dos o más gases, se sugerirán automáticamente cambios
-de gas durante la fase de ascenso a superficie. Sin embargo, estos cambios
-pueden borrarse haciendo clic-derecho en el cambio de gas, o pueden crearse
-manualmente de la misma forma, haciendo clic-derecho en el punto de paso
-adecuado.</p></div>
-<div class="paragraph"><p>A continuación hay un ejemplo de planificación de inmersión a 45m usando EAN26,
-seguido de un ascenso usando EAN50:</p></div>
-<div class="imageblock" style="text-align:center;">
-<div class="content">
-<img src="images/DivePlanner2_f20.jpg" alt="FIGURA: Planificar una inmersión: construcción" />
-</div>
-</div>
-<div class="paragraph"><p>Una vez que lo anterior se ha completado, se puede guardar clicando el botón
-<em>Guardar</em> arriba en el centro del panel del planificador. El plan de buceo
-guardado aparecerá en el panel <strong>Lista de Inmersiones</strong>.</p></div>
-<div class="paragraph"><p><strong>Los detalles del plan de buceo</strong></p></div>
-<div class="paragraph"><p>En la parte inferior derecha del planificador, bajo el encabezamiento <em>Detalles
-del plan de buceo</em>, se proporcionan los detalles exactos del plan de inmersión.
-Estos detalles pueden modificarse seleccionando cualquiera de las opciones bajo
-el encabezamiento <em>Notas</em> del planificador, justo a la izquierda
-del anterior. Si se solicita un <em>Plan de buceo detallado</em>, se obtendrá un plan
-detallado al nivel de oraciones. Si cualquiera de los límites especificados se
-sobrepasa, se obtendrá un mensaje de aviso bajo la información del plan.</p></div>
-<div class="paragraph"><p>Si se selecciona la opción <em>Mostrar duración de segmentos</em>, se indicará la
-duración de cada segmento de profundidad en los <em>Detalles del plan de buceo</em>.
-Esta duración INCLUYE el tiempo de transición hasta llegar al nivel. Sin
-embargo, si se selecciona <em>Mostrar transiciones en deco</em>, las transiciones se
-muestran separadamente de las duraciones de las paradas en cada nivel.</p></div>
-</div>
-</div>
-<div class="sect2">
-<h3 id="_planificar_inmersiones_con_pscr">14.3. Planificar inmersiones con pSCR</h3>
-<div class="paragraph"><p>Para planificar una inmersión usando un rebreather pasivo de circuito
-semi-cerrado, selecciona <em>pSCR</em> en lugar de <em>Circuito abierto</em> en la lista
-desplegable.
-Los parámetros para la inmersción con pSCR se pueden ajustar seleccionando
-<em>Archivo → Preferencias → Gráfico</em> desde el menú principal, donde el cálculo
-de consumo de gas tiene en cuenta el ratio de vertido (por defecto 10:1) así
-como el ratio de metabolismo. El cálculo también tiene en cuenta la pérdida
-de oxígeno por la boquilla del rebreather. Si la pO<sub>2</sub> cae por debajo de lo que
-se considera un valor seguro, aparecerá un aviso en los <em>Detalles del plan de
-buceo</em>. Una configuración típica con pSCR es con una sola botella y una o más
-botellas de emergencia. Así pues, el ajuste de las tablas de <em>Gases disponibles</em>
-y <em>Puntos del planificador</em> son muy similares a las de un plan con CCR, como se
-ha descrito anteriormente. Sin embargo, no se especifican setpoints de oxígeno
-en las inmersiones con pSCR. A continuación hay un plan de inmersión para un
-buceo con pSCR. El buceo es comparable al anterior con CCR, pero hay que hacer
-notar la mayor duración del ascenso debido al menor contenido de oxígeno en el
-circuito por la caída de oxígeno en la boquilla del equipo pSCR.</p></div>
-<div class="imageblock" style="text-align:center;">
-<div class="content">
-<img src="images/Planner_pSCR1_f20.jpg" alt="FIGURE: Planning a pSCR dive: setup" />
-</div>
-</div>
-</div>
-<div class="sect2">
-<h3 id="_planificar_inmersiones_con_ccr">14.4. Planificar inmersiones con CCR</h3>
-<div class="paragraph"><p>Para planificar una inmersión utilizando un rebreather de circuito cerrado,
-selecciona la opción <em>CCR</em> en la lista desplegable (en un circulo azul en la
-imagen a continuación.</p></div>
-<div class="paragraph"><p><strong>Gases disponibles</strong>: en la tabla de <em>Gases disponibles</em>, introduce los datos de
-la botella de diluyente y las de bail-out. NO indiques información para la
-botella de oxígeno, ya que está implícita al haber seleccionado <em>CCR</em>.</p></div>
-<div class="paragraph"><p><strong>Introducir setpoints</strong>: Especifica un setpoint por defecto en la pestaña de
-Preferencias seleccionando <em>Archivo → Preferencias → Gráfico</em> desde el menú
-principal. Todos los segmentos introducidos por el usuario en los <em>Puntos del
-planificador</em> utilizan el valor del setpoint por defecto. Luego se pueden
-especificar diferentes setpoints para los diferentes segmentos en la tabla.
-Un setpoint cero significa que el buceador ha pasado a circuito abierto para
-el segmento en que se ha indicado. La descompresión siempre se calcula usando
-el setpoint del último segmento que se haya añadido manualmente. De esta forma,
-si se desea planificar un ascenso de emergencia, se añadiría un segmento de un
-minuto al final de la inmersión con un setpoint de valor cero. El algoritmo de
-descompresión no cambia de mezclas automáticamente mientras se está en modo CCR
-pero, desde luego, lo hace para ascensos de emergencia en circuito abierto.</p></div>
-<div class="paragraph"><p>El perfil para una inmersión con CCR puede parecerse a la imagen a continuación</p></div>
-<div class="imageblock" style="text-align:center;">
-<div class="content">
-<img src="images/Planner_CCR1_f20.jpg" alt="FIGURE: Planning a CCR dive: setup" />
-</div>
-</div>
-<div class="paragraph"><p>Fíjate que, en los <em>Detalles del plan de buceo</em>, no se calcula el consumo de
-gas para un segmento en CCR, por tanto, lo normal es obtener valores de 0 l.</p></div>
-</div>
-<div class="sect2">
-<h3 id="S_Replan">14.5. Modificar un plan de inmersión existente</h3>
-<div class="paragraph"><p>Normalmente, cuando se ha guardado un plan de inmersión, se encuentra disponible
-desde la <strong>Lista de Inmersiones</strong> como cualquier buceo. Desde la <strong>Lista de
-Inmersiones</strong> no hay forma de cambiar un plan. Para efectuar cambios a un plan de
-buceo, selecciónalo en la <strong>Lista de Inmersiones</strong>, luego, desde el menú principal
-selecciona <em>Registro → Re-planificar inmersión</em>, con ello se abrirá el plan en
-el planificador, permitiendo hacer las modificaciones oportunas y guardarlas de
-la forma habitual.</p></div>
-</div>
-<div class="sect2">
-<h3 id="_planificar_inmersiones_sucesivas">14.6. Planificar inmersiones sucesivas</h3>
-<div class="paragraph"><p>Se pueden planear fácilmente inmersiones sucesivas si la fecha y hora de las
-mismas se especifican correctamente en el campo arriba a la izquierda <em>Hora de
-inicio</em>. <em>SUbsurface</em> calcula las cargas de gases inertes de la primera
-inmersión y su efecto se evalúa en las posteriores.</p></div>
-<div class="paragraph"><p>Si se acaba de completar una inmersión larga/profunda y se está planificando
-otra, se selecciona de la <strong>Lista de inmersiones</strong> la que se acaba de completar y
-se activa el planificador. Dependiendo de la hora de inicio del buceo planeado,
-el planificador toma en cuenta la carga de gas en la que se ha incurrido durante
-la inmersión completada y permite planear con estas limitaciones.</p></div>
-<div class="paragraph"><p>Si solo se usan unas pocas configuraciones (p.e. en GUE), puede crearse una
-plantilla de acuerdo con una de las configuraciones. Si ahora se desea planear
-una inmersión usando esta configuración, simplemente se selecciona la plantilla
-de la <strong>Lista de inmersiones</strong> y se activa el planificador: el planificador tendrá
-en cuenta la configuración de la plantilla seleccionada.</p></div>
-</div>
-<div class="sect2">
-<h3 id="_imprimir_el_plan_de_inmersion">14.7. Imprimir el plan de inmersión</h3>
-<div class="paragraph"><p>Seleccionar el botón <em>Imprimir</em> permite imprimir los <em>Detalles del plan de
-buceo</em> para unas "wet notes". También se pueden copiar y pegar los <em>Detalles del
-plan de buceo</em> para incluirlos en un archivo de texto o un procesador de
-textos.</p></div>
-<div class="paragraph"><p>Los planes de inmersión tienen muchas características en común con los registros
-de buceo (perfil, notas, etc). Despues de haber guardado un plan, los detalles y
-los calculos de gas quedan almacenados en la pestaña <strong>Notas</strong>.
-Mientras se está diseñando un plan, se puede imprimir utilizando el botón
-<em>Imprimir</em> del planificador. Esto imprimirá los detalles y cálculos de gases del
-panel <em>Detalles del plan de inmersión</em> del planificador. Sin embargo, tras haber
-sido guardado, aparece de una forma muy similar a una anotación en el diario y
-no se puede acceder a los cáculos de gas de la misma forma que durante el proceso
-de planificación. En esta situación, la única manera de imprimir el plan es usar
-<em>Archivo → Imprimir</em> en el menú principal, igual que haríamos para imprimir un
-registro de inmersión.</p></div>
-</div>
-</div>
-</div>
-<div class="sect1">
-<h2 id="_descripcion_de_las_opciones_del_menu_principal_de_em_subsurface_em">15. Descripción de las opciones del menú principal de <em>Subsurface</em></h2>
-<div class="sectionbody">
-<div class="paragraph"><p>Esta sección describe las funciones y manejo de las opciones del menú principal
-de <em>Subsurface</em>. Varias de las opciones que veremos luego son links a secciones
-de este manual que describen las operaciones con más detalle.</p></div>
-<div class="sect2">
-<h3 id="_archivo">15.1. Archivo</h3>
-<div class="ulist"><ul>
-<li>
-<p>
-<a href="#S_NewLogbook"><em>NuevoRegistro</em></a> - Cierra el diario abierto en estos momentos
- y limpia toda la información.
-</p>
-</li>
-<li>
-<p>
-<em>Abrir Registro</em> - Abre el navegador de archivos para seleccionar un archivo
- de registro que abrir.
-</p>
-</li>
-<li>
-<p>
-<em>Abrir almacenamiento en la nube</em> - Abre el diario previamente configurado en
- <a href="#S_Cloud_storage"><em>Almacenamiento en la nube</em></a>.
-</p>
-</li>
-<li>
-<p>
-<em>Guardar</em> - Guarda el diario abierto en estos momentos.
-</p>
-</li>
-<li>
-<p>
-<em>Guardar en almacenamiento en la nube</em> - Guarda el diario actual en el
- <a href="#S_Cloud_storage"><em>Almacenamiento en la nube</em></a>.
-</p>
-</li>
-<li>
-<p>
-<em>Guardar como</em> - Guarda el diario actual con un nombre de archivo diferente.
-</p>
-</li>
-<li>
-<p>
-<em>Cerrar</em> - Cierra el registro de inmersiones abierto en estos momentos.
-</p>
-</li>
-<li>
-<p>
-<a href="#S_ExportLog"><em>Exportar</em></a> - Exporta el diario abierto actualmente (o las
- inmersiones seleccionadas en el diario) a algún otro formato.
-</p>
-</li>
-<li>
-<p>
-<a href="#S_PrintDivelog"><em>Imprimir</em></a> - Imprime el registro de inmersiones abierto.
-</p>
-</li>
-<li>
-<p>
-<a href="#S_Preferences"><em>Preferencias</em></a> - Fija las preferencias del usuario de
- <em>Subsurface</em>.
-</p>
-</li>
-<li>
-<p>
-<a href="#S_FindMovedImages"><em>Encontrar imágenes movidas</em></a> - Si las fotos que se
- hicieron durante las inmersiones se han cambiado de carpeta o de disco, las
- localiza y las une alas inmersiones correspondientes.
-</p>
-</li>
-<li>
-<p>
-<a href="#S_Configure"><em>Configurar ordenador de buceo</em></a> - Edita la configuración de
- un ordenador de buceo.
-</p>
-</li>
-<li>
-<p>
-<em>Salir</em> - Sale de <em>Subsurface</em>.
-</p>
-</li>
-</ul></div>
-</div>
-<div class="sect2">
-<h3 id="_importar">15.2. Importar</h3>
-<div class="ulist"><ul>
-<li>
-<p>
-<a href="#S_ImportDiveComputer"><em>Importar del ordenador de buceo</em></a> - Descarga
- información desde un ordenador de buceo.
-</p>
-</li>
-<li>
-<p>
-<a href="#Unified_import"><em>Importar Archivos de registro</em></a> - Importa información de
- buceo desde un fichero que esté en un formato compatible con <em>Subsurface</em>.
-</p>
-</li>
-<li>
-<p>
-<a href="#S_Companion"><em>Importar datos GPS del Servicio web de Subsurface</em></a> - Carga
- coordenadas GPS desde la app para teléfonos móviles.
-</p>
-</li>
-<li>
-<p>
-<a href="#S_ImportingDivelogsDe"><em>Importar desde Divelogs.de</em></a> - Importa información
- de buceo desde www.divelogs.de.
-</p>
-</li>
-</ul></div>
-</div>
-<div class="sect2">
-<h3 id="_registro">15.3. Registro</h3>
-<div class="ulist"><ul>
-<li>
-<p>
-<a href="#S_EnterData"><em>Añadir inmersión</em></a> - Añade manualmente una nueva inmersión al
- panel Lista de inmersiones.
-</p>
-</li>
-<li>
-<p>
-<em>Editar inmersión</em> - Edita una inmersión cuyo perfil se hizo manualmente y no
- descargándola desde un ordenador de buceo.
-</p>
-</li>
-<li>
-<p>
-<a href="#S_DivePlanner"><em>Planificar inmersión</em></a> - Esta característica permite
- planificar inmersiones.
-</p>
-</li>
-<li>
-<p>
-<a href="#S_Replan"><em>Editar inmersión en planificador</em></a> - Edita un plan de buceo que se ha
- guardado en la <strong>Lista de Inmersiones</strong>.
-</p>
-</li>
-<li>
-<p>
-<a href="#S_CopyComponents"><em>Copiar componentes</em></a> - Al seleccionar esta opción se
- se puede copiar información de varios campos de una inmersión al portapapeles.
-</p>
-</li>
-<li>
-<p>
-<em>Pegar componentes</em> - Pega, en las inmersiones previamente seleccionadas de
- la <strong>Lista de Inmersiones</strong>, la información copiada previamente usando la opción
- <em>Copiar componentes</em>.
-</p>
-</li>
-<li>
-<p>
-<a href="#S_Renumber"><em>Renumerar</em></a> - Renumera las inmersiones listadas en el panel
- Lista de inmersiones.
-</p>
-</li>
-<li>
-<p>
-<a href="#S_Group"><em>Auto agrupar</em></a> - Agrupa automáticamente los buceos de la Lista de
- inmersiones en viajes de buceo.
-</p>
-</li>
-<li>
-<p>
-<a href="#S_DeviceNames"><em>Editar nombres de dispositivos</em></a> - Edita los nombres
- asignados a los ordenadores de buceo.
-</p>
-</li>
-<li>
-<p>
-<a href="#S_Filter"><em>Filtrar la lista de inmersiones</em></a> - Seleccionar únicamente
- algunas inmersiones, basándose en criterios específicos.
-</p>
-</li>
-</ul></div>
-</div>
-<div class="sect2">
-<h3 id="_vista">15.4. Vista</h3>
-<div class="ulist"><ul>
-<li>
-<p>
-<a href="#S_ViewPanels"><em>Todo</em></a> - Se presentan los cuatro paneles principales de
- <em>Subsurface</em> simultáneamente.
-</p>
-</li>
-<li>
-<p>
-<a href="#S_ViewPanels"><em>Lista_de_inmersiones</em></a> - Se visualiza solo el panel Lista de
- inmersiones.
-</p>
-</li>
-<li>
-<p>
-<a href="#S_ViewPanels"><em>Perfil</em></a> - Se visualiza solo el panel Perfil de inmersión.
-</p>
-</li>
-<li>
-<p>
-<a href="#S_ViewPanels"><em>Info</em></a> - Se visualiza solo el panel Notas.
-</p>
-</li>
-<li>
-<p>
-<a href="#S_ViewPanels"><em>Globo</em></a> - Se presenta solo el panel Mapamundi.
-</p>
-</li>
-<li>
-<p>
-<em>Estadísticas anuales</em> - Muestra estadísticas anuales resumidas sobre las
- inmersiones efectuadas en este año y los pasados.
-</p>
-</li>
-<li>
-<p>
-<em>Anterior ordenador</em> - Si una inmersión se ha registrado con más de un ordenador
- de buceo, cambia a los datos del anterior ordenador de buceo.
-</p>
-</li>
-<li>
-<p>
-<em>Siguiente ordenador</em> - Cambia al siguiente ordenador de buceo.
-</p>
-</li>
-<li>
-<p>
-<em>Pantalla completa</em> - Activa el modo de pantalla completa.
-</p>
-</li>
-</ul></div>
-</div>
-<div class="sect2">
-<h3 id="_ayuda">15.5. Ayuda</h3>
-<div class="ulist"><ul>
-<li>
-<p>
-<em>Acerca de Subsurface</em> - Muestra un panel con el número de versión de
- <em>Subsurface</em> e información de la licencia.
-</p>
-</li>
-<li>
-<p>
-<em>Comprobar si hay actualizaciones</em> - Encuentra si hay disponible una nueva
- versión de <em>Subsurface</em> en la <a href="http://subsurface-divelog.org/">página web de <em>Subsurface</em></a>.
-</p>
-</li>
-<li>
-<p>
-<a href="#S_UserSurvey"><em>Encuesta de usuarios</em></a> - Ayuda a hacer mejor <em>Subsurface</em>
- tomando parte en nuestra encuesta a usuarios, o completando otra si tus hábitos
- de buceo han cambiado.
-</p>
-</li>
-<li>
-<p>
-<em>Manual de usuario</em> - Abre una ventana que muestra este manual.
-</p>
-</li>
-</ul></div>
-</div>
-</div>
-</div>
-<div class="sect1">
-<h2 id="_apendice_a_informacion_especifica_del_sistema_operativo_para_importar_inmersiones_desde_un_ordenador_de_buceo">16. APÉNDICE A: Información específica del sistema operativo para importar inmersiones desde un ordenador de buceo.</h2>
-<div class="sectionbody">
-<div class="sect2">
-<h3 id="_asegurate_de_que_el_so_tiene_instalados_los_drivers_necesarios">16.1. Asegúrate de que el SO tiene instalados los drivers necesarios</h3>
-<div class="admonitionblock">
-<table><tr>
-<td class="icon">
-<img src="images/icons/drivers.jpg" alt="Note" />
-</td>
-<td class="content">El sistema operativo del ordenador de sobremesa necesita los drivers correctos
-para comunicarse con el ordenador de buceo de la forma en que este lo prefiera
-(p.e. bluetooth, USB, infrarrojos).</td>
-</tr></table>
-</div>
-<div class="ulist"><ul>
-<li>
-<p>
-En Linux esto significa que el usuario tiene que tener cargados los módulos
-del kernel correctos. La mayoría de las distribuciones lo harán automáticamente.
-Sin embargo algunos protocolos de comunicación requieren un driver adicional,
-especialmente para tecnología poco usada como los infrarojos.
-</p>
-</li>
-<li>
-<p>
-En Windows, el SO debería ofrecer descargar el driver correcto cuando el
-usuario conecte su ordenador de buceo al puerto USB y el sistema operativo vea
-el dispositivo por primera vez.
-</p>
-</li>
-<li>
-<p>
-En un Mac, en ocasiones, el usuario tiene que buscar manualmente el driver
-correcto. Por ejemplo, el driver correcto para los dispositivos Mares Puck puede
-encontrarse como Mac_OSX_VCP_driver.zip en el
-<a href="http://www.silabs.com/support/pages/document-library.aspx?p=Interface&f=USB%20Bridges&pn=CP2101">repositorio
-de documentos y software de Silicon Labs</a>.
-</p>
-</li>
-</ul></div>
-</div>
-<div class="sect2">
-<h3 id="S_HowFindDeviceName">16.2. Como encontrar el nombre de dispositivo para conexiones USB y ajustar sus permisos de escritura</h3>
-<div class="admonitionblock">
-<table><tr>
-<td class="icon">
-<img src="images/icons/usb.jpg" alt="Note" />
-</td>
-<td class="content">Cuando un usuario conecta el ordenador de buceo utilizando un conector USB,
-normalmente <em>Subsurface</em> propondrá una lista desplegable que contendrá el nombre
-de dispositivo correcto (o punto de montaje para el Uemis Zurich), o
-deshabilitará el desplegable de selección si no se necesita ningún nombre. En
-los raros casos en que esto no funcione, aquí hay algunas instrucciones sobre
-formas de averiguar cual es el nombre de dispositivo.</td>
-</tr></table>
-</div>
-<div class="paragraph"><div class="title">En Windows:</div><p>Simplemente intenta COM1, COM2, etc. La lista desplegable debería contener todos
-los dispositivos COM conectados.</p></div>
-<div class="paragraph"><div class="title">En MacOS:</div><p>El desplegable debería encontrar todos los ordenadores de buceo conectados.</p></div>
-<div class="paragraph"><div class="title">En Linux:</div><p>Hay una forma definitiva de encontrar el puerto:</p></div>
-<div class="ulist"><ul>
-<li>
-<p>
-Desconectar el cable USB del ordenador de buceo
-</p>
-</li>
-<li>
-<p>
-Abrir un terminal
-</p>
-</li>
-<li>
-<p>
-Teclear el comando: dmesg y pulsar enter
-</p>
-</li>
-<li>
-<p>
-Conectar el cable USB del ordenador de buceo
-</p>
-</li>
-<li>
-<p>
-Teclear el comando: dmesg y pulsar enter
-</p>
-</li>
-</ul></div>
-<div class="paragraph"><p>En el terminal debería poderse ver un mensaje similar a este:</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>En la tercera línea desde abajo muestra que se detecta el adaptador USB FTDI y
-está conctado a <code>ttyUSB3</code> . Ahora puede usarse esta información en el ajuste de
-la importación como <code>/dev/ttyUSB3</code> lo que dirigirá a <em>Subsurface</em> al puerto USB
-correcto.</p></div>
-<div class="paragraph"><p>Asegurarse de que el usuario tiene permisos de escritura en el puerto serie USB:</p></div>
-<div class="paragraph"><p>En sistemas operativos tipo Unix los puertos USB solo pueden accederse por
-usuarios que sean miembros del grupo dialout. Si uno no es root, puede que no
-sea miembro de dicho grupo y no podrá utilizar el puerto USB. Asumamos que el
-nombre de usuario de uno es johnB.</p></div>
-<div class="ulist"><ul>
-<li>
-<p>
-Como root se teclea: <code>usermod -a -G dialout johnB</code> (usuarios de Ubuntu: <code>sudo
-usermod -a -G dialout johnB</code>) . Esto hace a johnB miembro del grupo <code>dialout</code>.
-</p>
-</li>
-<li>
-<p>
-Teclea: <code>id johnB</code> Esto listará todos los grupos a los que pertenece johnB y
-verifica que se ha creado la pertenencia correcta al grupo. El grupo <code>dialout</code>
-debería aparecer entre los diferentes IDs.
-</p>
-</li>
-<li>
-<p>
-En algunas circunstancias, este cambio solo tiene efecto (p.e. en Ubuntu) tras
-cerrar sesión y reiniciarla.
-</p>
-</li>
-</ul></div>
-<div class="paragraph"><p>Con el nombre de dispositivo apropiado (p.e. <code>/dev/ttyUSB3</code>) y con permisos de
-escritura para el puerto USB, el interface del ordenador de buceo puede
-conectarse y se debería poder importar las inmersiones.</p></div>
-</div>
-<div class="sect2">
-<h3 id="S_HowFindBluetoothDeviceName">16.3. Ajustar manualmente dispositivos con bluetooth</h3>
-<div class="admonitionblock">
-<table><tr>
-<td class="icon">
-<img src="images/icons/bluetooth.jpg" alt="Note" />
-</td>
-<td class="content">Para ordenadores de buceo que se comunican por bluetooth como el Heinrichs
-Weikamp Frog o el Shearwater Predator, Petrel y Nerd hay un procedimiento distinto
-para localizar los nombres de dispositivo con los que se comunicará
-<em>Subsurface</em>. En general consiste en estos pasos:</td>
-</tr></table>
-</div>
-<div class="ulist"><ul>
-<li>
-<p>
-<strong>En el ordenador de buceo, tras habilitar Bluetooth, asegurarse que está en
-modo Upload</strong>
-</p>
-</li>
-</ul></div>
-<div class="paragraph"><p>Para emparejar el ordenador de buceo, consulta la guía de usuario del
-fabricante. Si se está usando un Shearwater Predator/Petrel/Nerd, hay que seleccionar
-<em>Dive Log → Upload Log</em> y esperar al mensaje <em>Wait PC</em>.</p></div>
-<div class="ulist"><ul>
-<li>
-<p>
-<strong>Emparejar el PC con <em>Subsurface</em> con el ordenador de buceo.</strong>
-</p>
-</li>
-</ul></div>
-<div class="sect3">
-<h4 id="_en_windows_2">16.3.1. En Windows:</h4>
-<div class="paragraph"><p>Probablemente bluetooth ya esté activado. Para emparejar el dispositivo se
-selecciona <em>Panel de Control → Dispositivos Bluetooth → Añadir dispositivo
-Inalámbrico</em>. Esto debería desplegar un diálogo que mostraría tu ordenador de
-buceo (en modo bluetooth) y te permitiría emparejarlo. El ordenador de buceo
-debería mostrarse en la lista de dispositivos y podrías hacer clic-derecho en él
-y seleccionar <em>Propiedades → Puertos COM</em> para identificar el puerto usado por
-tu ordenador de buceo. Si se mostraran varios puertos, utiliza el que diga
-"Saliente" en vez de "Entrante".</p></div>
-<div class="paragraph"><p>Para descargar a <em>Subsurface</em>, la lista desplegable ya debería contener este
-puerto COM. Si no, introdúcelo manualmente.</p></div>
-<div class="paragraph"><p>Nota: Si tienes problemas descargando desde tu ordenador de buceo a otro
-software después, intenta borrar el emparejamiento y volverlo a hacer.</p></div>
-</div>
-<div class="sect3">
-<h4 id="_en_macos">16.3.2. En MacOS:</h4>
-<div class="paragraph"><p>Clica en el símbolo Bluetooth en la barra de menú y selecciona <em>Configurar
-Dispositivo Bluetooth …</em>. Asegúrate de que tu ordenador de buceo está en modo
-upload; entonces debería mostrar la lista de dispositivos. Selecciónalo y pasa
-por el proceso de emparejamiento. Este paso solo debería se necesario una vez
-para la configuración inicial.</p></div>
-<div class="paragraph"><p>Una vez que el emparejamiento está completo el dispositivo correcto se mostrará
-en el desplegable <em>Dispositivo o punto de montaje</em> del diálogo <strong>Importar</strong> de
-<em>Subsurface</em>.</p></div>
-</div>
-<div class="sect3">
-<h4 id="_en_linux">16.3.3. En Linux</h4>
-<div class="paragraph"><p>Asegúrate de que tienes activado el ordenador con <em>Subsurface</em>. En las
-distribuciones más habituales esto debería ser cierto de entrada y el
-emparejamiento debería se fácil. Por ejemplo, Gnome3 muestra un icono Bluetooth
-a la derecha de la barra de tareas, arriba en la pantalla.
-Los usuarios han informado de dificultades con algunos controladores de
-Bluetooth. Si tienes un controlador incluido en el PC, prueba primero con
-este. Es más fácil si quitas cualquier receptor USB que tengas activado.
-Si tienes un receptor USB que viniera con el ordenador de buceo, prueba con
-este antes que con cualquier otro.</p></div>
-<div class="paragraph"><p>Configurar una conexión para descargar inmersiones desde tu ordenador de buceo
-con capacidad Bluetooth, tal como el <em>Shearwater Petrel</em>, todavía no es un
-proceso automatizado y requerirá generalmente la línea de comandos.
-Se trata esencialmente de un proceso en tres pasos.</p></div>
-<div class="ulist"><ul>
-<li>
-<p>
-Activar el controlador Bluetooth y emparejarlo con el ordenador de buceo
-</p>
-</li>
-<li>
-<p>
-Establecer una conexión RFCOMM
-</p>
-</li>
-<li>
-<p>
-Descargar las inmersiones con <em>Subsurface</em>
-</p>
-</li>
-</ul></div>
-<div class="paragraph"><p>Asegurarse de que el ordenador de buceo está en modo "upload". En el <em>Petrel</em>
-y <em>Petrel 2</em> y <em>Nerd</em>, navega por el menú, selecciona <em>Dive Log</em>, luego <em>Upload log</em>. En
-la pantalla se leerá <em>Initializing</em>, luego <em>Wait PC 3:00</em> e iniciará una cuenta
-atrás. Una vez que la conexión esté establecida, en la pantalla se leerá
-<em>Wait CMD …</em> y la cuenta atrás seguirá. Cuando se descargue la inmersión a
-<em>Subsurface</em> en la pantalla se leerá <em>Sending</em> y luego <em>Sent dive</em>.</p></div>
-<div class="paragraph"><p>Para establecer la conexión, accede como root vía <code>sudo</code> o <code>su</code>.
-Se necesitan los permisos correctos para descargar las inmersiones al PC. En la
-mayoría de los sistemas Linux, esto significa hacerse miembro del grupo dialout
-(de forma idéntica como con los ordenadores de buceo que utilizan un puerto USB,
-como se describía en la sección anterior). En la línea de comando introduce:</p></div>
-<div class="paragraph"><p><code>sudo usermod -a -G dialout username</code></p></div>
-<div class="paragraph"><p>Luego desconecta el usuario y vuélvelo a conectar para que tenga efecto la
-modificación.</p></div>
-<div class="sect4">
-<h5 id="_activar_el_controlador_bluetooth_y_emparejar_el_ordenador_de_buceo">Activar el controlador Bluetooth y emparejar el ordenador de buceo</h5>
-<div class="paragraph"><p>Intenta configurar el controlador Bluetooth y emparejar tu ordenador de buceo
-utilizando el entorno gráfico del sistema operativo. Tras configurar el
-ordenador de buceo en modo "upload", haz clic en el icono Bluetooth en la
-barra del sistema y selecciona <em>Añadir nuevo dispositivo</em>. El ordenador de
-buceo debería aparecer. Si se pide una contraseña, introduce 0000. Anótate o
-copia la dirección MAC de tu ordenador de buceo, que necesitaremos más
-adelante, y debería ser de la forma 00:11:22:33:44:55.</p></div>
-<div class="paragraph"><p>Si el método gráfico no funcionó, empareja el dispositivo desde la línea de
-comandos. Abre un terminal y usa <code>hciconfig</code> para comprobar el estado del
-controlador Bluetooth</p></div>
-<div class="literalblock">
-<div class="content">
-<pre><code>$ hciconfig
-hci0: Type: BR/EDR Bus: USB
- BD Address: 01:23:45:67:89:AB ACL MTU: 310:10 SCO MTU: 64:8
- *DOWN*
- RX bytes:504 acl:0 sco:0 events:22 errors:0
- TX bytes:92 acl:0 sco:0 commands:21 errors:0</code></pre>
-</div></div>
-<div class="paragraph"><p>Esto indica un controlador Bluetooth con dirección MAC 01:23:45:67:89:AB,
-conectado como hci0. Su estado es DOWN, por ejemplo no activado. Otros
-controladores adicionales aparecerían como hci1, etc. Si no había un receptor
-Bluetooth conectado al PC en el momento del arranque, hci0 es, probablemente,
-el receptor interno.
-Ahora conectemos el controlador y activemos la autenticación:</p></div>
-<div class="literalblock">
-<div class="content">
-<pre><code>sudo hciconfig hci0 up auth (enter password when prompted)
-hciconfig
-hci0: Type: BR/EDR Bus: USB
- BD Address: 01:23:45:67:89:AB ACL MTU: 310:10 SCO MTU: 64:8
- *UP RUNNING PSCAN AUTH*
- RX bytes:1026 acl:0 sco:0 events:47 errors:0
- TX bytes:449 acl:0 sco:0 commands:46 errors:0</code></pre>
-</div></div>
-<div class="paragraph"><p>Comprueba que el estado ahora incluye <code><em>UP</em>, <em>RUNNING</em> y <em>AUTH</em></code>.</p></div>
-<div class="paragraph"><p>If se están ejecutando múltiples controladores, lo más simple es desconectar
-los no utilizados, por ejemplo, para <code>hci1</code>:</p></div>
-<div class="literalblock">
-<div class="content">
-<pre><code>sudo hciconfig hci1 down</code></pre>
-</div></div>
-<div class="paragraph"><p>El próximo paso es <em>trust</em> y <em>pair</em> el ordenador de buceo. En distribuciones
-con Bluez 5, como Fedora 22, se puede utilizar una herramienta llamada
-<code>blutoothctl</code>, que lanzará su propia linea de comandos.</p></div>
-<div class="literalblock">
-<div class="content">
-<pre><code>bluetoothctl
-[NEW] Controller 01:23:45:67:89:AB localhost.localdomain [default]
-[bluetooth]# agent on
-Agent registered
-[bluetooth]# default-agent
-Default agent request successful
-[bluetooth]# scan on <----now set your dive computer to upload mode
-Discovery started
-[CHG] Controller 01:23:45:67:89:AB Discovering: yes
-[NEW] Device 00:11:22:33:44:55 Petrel
-[bluetooth]# trust 00:11:22:33:44:55 <----you can use the tab key to autocomplete the MAC address
-[CHG] Device 00:11:22:33:44:55 Trusted: yes
-Changing 00:11:22:33:44:55 trust succeeded
-[bluetooth]# pair 00:11:22:33:44:55
-Attempting to pair with 00:11:22:33:44:55
-[CHG] Device 00:11:22:33:44:55 Connected: yes
-[CHG] Device 00:11:22:33:44:55 UUIDs: 00001101-0000-1000-8000-0089abc12345
-[CHG] Device 00:11:22:33:44:55 Paired: yes
-Pairing successful
-[CHG] Device 00:11:22:33:44:55 Connected: no</code></pre>
-</div></div>
-<div class="paragraph"><p>Si se solicita una contraseña, introduce 0000. Está bien aunque la última
-línea diga <em>Connected: no</em>. La parte importante es la anterior <code>Pairing
-successful</code>.</p></div>
-<div class="paragraph"><p>Si el sistema tiene Bluez 4 (p.e. Ubuntu 12.04 a 15.04), probablemente no haya
-<code>bluetoothctl</code>, sino un script llamado <code>bluez-simple-agent</code>.</p></div>
-<div class="literalblock">
-<div class="content">
-<pre><code>hcitool -i hci0 scanning
-Scanning ...
- 00:11:22:33:44:55 Petrel
- bluez-simple-agent hci0 00:11:22:33:44:55</code></pre>
-</div></div>
-<div class="paragraph"><p>Una vez que el ordenador esté emparejado, configura la conexión RFCOMM.</p></div>
-</div>
-<div class="sect4">
-<h5 id="_establecer_la_conexion_rfcomm">Establecer la conexión RFCOMM</h5>
-<div class="paragraph"><p>El comando para establecer una conexión RFCOMM es:</p></div>
-<div class="paragraph"><p><code>sudo rfcomm -i <controller> connect <dev> <bdaddr> [channel]</code></p></div>
-<div class="ulist"><ul>
-<li>
-<p>
-<code><controller></code> es el controlador Bluetooth, <code>hci0</code>.
-</p>
-</li>
-<li>
-<p>
-<code><dev></code> es el dispositivo RFCOMM, <code>rfcomm0</code>
-</p>
-</li>
-<li>
-<p>
-<code><bdaddr></code> es la dirección MAC del ordenador de buceo, +00:11:22:33:44:55
-</p>
-</li>
-<li>
-<p>
-<code>[channel]</code> es el canal Bluetooth al que nos queremos conectar.
-</p>
-</li>
-</ul></div>
-<div class="paragraph"><p>Si se omite el canal, se asume el 1. Basándonos en un número limitado de
-informaciones de usuarios el canal apropiado para el ordenador de buceo,
-probablemente sea:</p></div>
-<div class="ulist"><ul>
-<li>
-<p>
-<em>Shearwater Petrel 1</em>: channel 1
-</p>
-</li>
-<li>
-<p>
-<em>Shearwater Petrel 2</em>: channel 5
-</p>
-</li>
-<li>
-<p>
-<em>Shearwater Nerd</em>: channel 5
-</p>
-</li>
-<li>
-<p>
-<em>Heinrichs-Weikamp OSTC Sport</em>: channel 1
-</p>
-</li>
-</ul></div>
-<div class="paragraph"><p>P.e. para conectar un <em>Shearwater Petrel 2</em>, ajusta el ordenador de buceo a
-modo "upload" e introduce:</p></div>
-<div class="literalblock">
-<div class="content">
-<pre><code>sudo rfcomm -i hci0 connect rfcomm0 00:11:22:33:44:55 5</code></pre>
-</div></div>
-<div class="paragraph"><p>(introduce una contraseña, probablemente 0000, cuando se solicite)
-Se obtendrá la respuesta:</p></div>
-<div class="literalblock">
-<div class="content">
-<pre><code>Connected /dev/rfcomm0 to 00:11:22:33:44:55 on channel 5
-Press CTRL-C for hangup</code></pre>
-</div></div>
-<div class="paragraph"><p>Para conectar un <code>Shearwater Petrel 1</code> o <code>H&W OSTC Sport</code>, ajusta el ordenador
-de buceo a modo "upload" e introduce:</p></div>
-<div class="literalblock">
-<div class="content">
-<pre><code>sudo rfcomm -i hci0 connect rfcomm0 00:11:22:33:44:55 (intruduce el password, probablemente 0000, cuando se solicite)
-Connected /dev/rfcomm0 to 00:11:22:33:44:55 on channel 1
-Press CTRL-C for hangup</code></pre>
-</div></div>
-<div class="paragraph"><p>Si se desconoce el canal específico de un ordenador de buceo, o el canal de la
-lista anterior no funciona, el comando <code>sdptool records</code> debería ayudar a dar
-con el canal apropiado, la salida a continuación es para un Petrel 2:</p></div>
-<div class="literalblock">
-<div class="content">
-<pre><code>sdptool -i hci0 records 00:11:22:33:44:55
-Service Name: Serial Port
-Service RecHandle: 0x10000
-Service Class ID List:
- "Serial Port" (0x1101)
- Protocol Descriptor List:
- "L2CAP" (0x0100)
- "RFCOMM" (0x0003)
- Channel: 5</code></pre>
-</div></div>
-<div class="paragraph"><p>En el caso de ordenadores de buceo Bluetooth que no estén incluidos en la lista
-anterior, por favor, informa a los desarrolladores de Subsurface a través del
-foro de usuarios o de la lista de correo <em>subsurface@subsurface-divelog.org</em>.</p></div>
-</div>
-<div class="sect4">
-<h5 id="_descargar_las_inmersiones_con_subsurface">Descargar las inmersiones con Subsurface</h5>
-<div class="paragraph"><p>Tras establecer la conexión RFCOMM y mientras esta corriendo la cuenta atrás
-del ordenador de buceo, ves a <em>Subsurface</em>, selecciona desde el menú principal
-<em>Importar → Importar del ordenador de buceo</em> y selecciona el fabricante
-adecuado (p.e. <em>Shearwater</em>), el ordenador de buceo (p.e. <em>Petrel</em>), el punto
-de montaje o dispositivo (p.e. <em>/dev/rfcomm0</em>) y pulsa <em>Descargar</em>.</p></div>
-</div>
-</div>
-</div>
-</div>
-</div>
-<div class="sect1">
-<h2 id="_appendix_b_dive_computer_specific_information_for_importing_dive_information">17. APÉNDICE B: Información específica por ordenadores de buceo.</h2>
-<div class="sectionbody">
-<div class="sect2">
-<h3 id="S_ImportUemis">17.1. Importar desde un 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> descarga la información guardada en el SDA (el sistema de archivos
-interno del Uemis) incluyendo información sobre puntos de buceo y equipo. La
-información sobre el compañero aún no se puede descargar. Se hace de forma muy
-similar a un ordenador de buceo con conexión USB (el Uemis es uno de los que se
-recargan cuando están conectados al puerto USB). La principal diferencia es que
-no se introduce un nombre de dispositivo, sino la ubicación donde se montará el
-sistema de ficheros UEMISSDA una vez conectado tu ordenador de buceo. En Windows
-este es una letra de disco (a menudo <em>E:</em> o <em>F:</em>), en un Mac este es
-<em>/Volumes/UEMISSDA</em> y en sistemas Linux varía dependiendo de la distribución
-utilizada. En Fedora habitualmente es
-<em>/var/run/media/<nombre_usuario>/UEMISSDA</em>. En todos los casos <em>Subsurface</em>
-debería sugerir la ubicación correcta en la lista desplegable.</td>
-</tr></table>
-</div>
-<div class="paragraph"><p>Tras seleccionar el nombre anterior como nombre de dispositivo, se pueden
-descargar las inmersiones del Uemis Zurich. Un problema técnico con la
-implementación de descargas en el Uemis Zurich (es una limitación del firmware,
-no un problema de <em>Subsurface</em>) es que no se pueden descargar más de 40/50
-buceos sin quedarse sin memoria en el SDA. Esto, usualmente, solo pasará la
-primera vez que se descarguen inmersiones del Uemis Zurich (normalmente, al
-descargar al final de un día o incluso de un viaje la capacidad será
-suficiente). Si <em>Subsurface</em> muestra el error de que el ordenador de buceo se ha
-quedado sin espacio la solución es directa. Desconectar el SDA, apágarlo y
-volverlo a encender, y reconectarlo. Ahora se puede reintentar (o iniciar una
-nueva sesión de descarga) y continuará donde paró la última vez. Puede que se
-tenga que repetir esta operación más de una vez dependiendo de cuantos buceos
-haya guardados en el ordenador.</p></div>
-</div>
-<div class="sect2">
-<h3 id="S_ImportingGalileo">17.2. Importar buceos desde el Galileo de Uwatec</h3>
-<div class="admonitionblock">
-<table><tr>
-<td class="icon">
-<img src="images/icons/Galileo.jpg" alt="Note" />
-</td>
-<td class="content">Los ordenadores de buceo Galileo de Uwatec usan comunicaciones por infrarrojos
-(IrDA) entre el dispositivo y <em>Subsurface</em>. El hardware de Uwatec utiliza un USB
-basado en le protocolo serie/infrarrojo (SIR) y el controlador IrDA MSC7780
-fabricado por MosChip y comercializado por Scubapro y algunas compañías de
-electrónica. En Linux, el kernel ya proporciona comunicación usando el protocolo
-IrDA. Sin embargo, el usuario necesita cargar adicionalmente un driver para el
-interface IrDA con el ordenador de buceo. La forma más fácil es cargar el
-paquete <strong>irda-tools</strong> del <a href="http://irda.sourceforge.net/docs/startirda.html">Linux
-IrDA Project</a>. Tras la instalación de irda-tools, el <strong>usuario root</strong> puede
-especificar un nombre de dispositivo desde la consola así:</td>
-</tr></table>
-</div>
-<div class="paragraph"><p><code>irattach irda0</code></p></div>
-<div class="paragraph"><p>Después de ejecutar este comando, <em>Subsurface</em> reconocerá el ordenador Galileo y
-descargará la información de buceo.</p></div>
-<div class="paragraph"><p>En Windows existe una situación similar. Hay drivers para el MCS7780 disponibles
-en algunos sitios de internet p.e.
-<a href="http://www.drivers-download.com/Drv/MosChip/MCS7780/">www.drivers-download.com</a>.
-También se pueden encontrar drivers IrDA basados en Windows, para los
-ordenadores Uwatec en el sitio web de ScubaPro, pudiendo encontrarlos en la
-página de descargas del software SmarTrak.</p></div>
-<div class="paragraph"><p>Para el Mac de Apple, la comunicación IrDA vía MCS7780 no está disponible para
-OSX 10.6 o superior.</p></div>
-</div>
-<div class="sect2">
-<h3 id="S_ImportingDR5">17.3. Importar buceos desde 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">El H&W DR5 se monta como un disco USB y guarda un fichero UDDF para cada
-buceo. Marca todas las inmersiones que quieras abrir o importar. Nota: El DR5 no
-parece conservar factores de gradiente ni información de deco, por lo que
-<em>Subsurface</em> no puede mostrarla. Ajusta los factores de gradiente en
-<em>Subsurface</em> en <strong>Preferencias</strong> para generar una capa de deco en el panel del
-<strong>Perfil</strong>. Observa que la deco calculada por <em>Subsurface</em> diferirá, con toda
-seguridad, de la calculada por el DR5.</td>
-</tr></table>
-</div>
-</div>
-<div class="sect2">
-<h3 id="S_ImportingXDeep">17.4. Importar desde xDEEP BLACK</h3>
-<div class="admonitionblock">
-<table><tr>
-<td class="icon">
-<img src="images/icons/HW_xdeepblack.jpg" alt="Note" />
-</td>
-<td class="content">Cada inmersión se ha de guardar individualmente como archivo UDDF utilizando la
-opción "Exportar a UDDF" en el menú del logbook del BLACK. Al montar el BLACK
-como disco USB, los archivos UDDF están disponibles en el directorio LOGBOOK.
-Nota: El xDEEP BLACK guarda el LND pero no parece guardar factores de gradiente
-ni información sobre deco, por lo que <em>Subsurface</em> no puede mostralos. Ajusta
-los factores de gradiente en <em>Gráfico</em> en las <em>Preferencias</em> para generar una
-capa de deco en el <strong>Perfil deinmersión</strong> de <em>Subsurface</em> pero fíjate que la
-deco calculada por <em>Subsurface</em> diferirá con toda probabilidad de la que
-mostraría el xDEEP BLACK.</td>
-</tr></table>
-</div>
-</div>
-<div class="sect2">
-<h3 id="_importar_del_shearwater_predator_petrel_nerd_usando_bluetooth">17.5. Importar del Shearwater Predator/Petrel/Nerd usando Bluetooth</h3>
-<div class="admonitionblock">
-<table><tr>
-<td class="icon">
-<img src="images/icons/predator.jpg" alt="Note" />
-</td>
-<td class="content">En la sección anterior, <a href="#S_Bluetooth"><em>Conectar Subsurface a ordenadores de buceo con Bluetooth</em></a>
-se facilitan instrucciones específicas para descargar inmersiones usando Bluetooth.</td>
-</tr></table>
-</div>
-</div>
-<div class="sect2">
-<h3 id="S_PoseidonMkVI">17.6. Importar desde el Poseidon MKVI Discovery</h3>
-<div class="admonitionblock">
-<table><tr>
-<td class="icon">
-<img src="images/MkVI.jpeg" alt="Note" />
-</td>
-<td class="content">La descarga de diarios desde el MKVI se realiza utilizando un adaptador de
-comunicaciones personalizado y el <em>Poseidon PC Configuration Software</em>, que
-se obtiene al adquirir el equipo MKVI. La última es una aplicación de
-windows que permite configurar el equipo y guardar los diarios. La comunicación
-entre el ordenador de buceo y el PC utiliza el protocolo IrDA de infrarrojos.
-Solo se pueden descargar datos de una inmersión cada vez e incluyen tres
-archivos:</td>
-</tr></table>
-</div>
-<div class="ulist"><ul>
-<li>
-<p>
-Configuración de ajustes para la inmersión y parámetros clave de la misma (es
- el archivo con extensión .txt).
-</p>
-</li>
-<li>
-<p>
-Detalles del diario (archivo con extensión .csv).
-</p>
-</li>
-<li>
-<p>
-Diario en formato Redbook (archivo con extensión .cvsr). Es una versión
-comprimida del diario utilizando un formato propio.
-</p>
-</li>
-</ul></div>
-<div class="paragraph"><p><em>Subsurface</em> accede a los archivos .txt y .csv para obtener información.</p></div>
-</div>
-<div class="sect2">
-<h3 id="_importar_desde_el_ccr_apd_inspiration">17.7. Importar desde el CCR APD Inspiration</h3>
-<div class="admonitionblock">
-<table><tr>
-<td class="icon">
-<img src="images/APDComputer.jpg" alt="Note" />
-</td>
-<td class="content">Los diarios del ordenador de buceo de un APD Inspiration o similar, se
-descargan utilizando un adaptador y el <em>AP Communicator</em>, obtenidos al comprar
-el equipo. Los diarios se pueden visualizar utilizando el <em>AP Log Viewer</em> desde
-Windows o Mac/OS. Sin embargo, los diarios de APD se pueden ver o manejar desde
-<em>Subsurface</em> (junto a buceos en los que se haya utilizado otros muchos tipos de
-ordenador de buceo). Los diarios de APD Inspiration se importan a <em>Subsurface</em>
-como sigue:</td>
-</tr></table>
-</div>
-<div class="ulist"><ul>
-<li>
-<p>
-Descargar la inmersión usando <em>AP Communicator</em>.
-</p>
-</li>
-<li>
-<p>
-Abrir una inmersión con el <em>AP Log Viewer</em>.
-</p>
-</li>
-<li>
-<p>
-Seleccionar la pestaña llamada <em>Datos</em> (<em>Data</em>).
-</p>
-</li>
-<li>
-<p>
-Con los datos del diario "en crudo" mostrados en pantalla, pulsar en
- <em>Copiar al portapapeles</em>.
-</p>
-</li>
-<li>
-<p>
-Abrir un editor de texto (p.e. Notepad en windows o TextWrangler en Mac).
-</p>
-</li>
-<li>
-<p>
-Copiar el contenido del portapapeles al editor y guardar el archivo de texto
- con extensión de archivo <em>.apd</em>
-</p>
-</li>
-<li>
-<p>
-Desde Subsurface, seleccionar <em>Importar → Importar archivos de registro</em>
- para abrir el <a href="#Unified_import">diálogo de importación universal</a>.
-</p>
-</li>
-<li>
-<p>
-En la lista desplegable de abajo del diálogo (llamada <em>Filtro:</em>) seleccionar "APD log viewer".
-</p>
-</li>
-<li>
-<p>
-En la lista de nombres de archivo, seleccionar el archivo <em>.apd</em> que acabamos
- de crear y se abrirá un diálogo de importación que mostrará los ajustes por
- defecto para los datos en un archivo <em>.apd</em>. Si es necesario algún cambio
- hazlo como en <a href="#S_ImportingCSVDives">CSV imports</a>.
-</p>
-</li>
-</ul></div>
-<div class="imageblock" style="text-align:center;">
-<div class="content">
-<img src="images/APD_CSVimportF22.jpg" alt="Figure: APD log viewer import" />
-</div>
-</div>
-<div class="ulist"><ul>
-<li>
-<p>
-El primer desplegable a la izquierda en el panel de importación nos permite
-el ordenador de buceo APD del que importar el registro. Por defecto es DC1, el
-primero de los dos ordenadores que usa el APD. Es posible importar secuencialmente
-los datos de ambos ordenadores, importando primero el DC1 y luego el DC2.
-(<strong>Truco</strong>: Los registros de ambos ordenadores se pueden visualizar seleccionando
- <em>Vista → Siguiente Ordenador</em> desde el menú principal, o situando el cursor
- sobre el perfil y pulsando la flecha derecha/izquierda). Pulsa el botón OK en
-la parte de debajo del panel.
-</p>
-</li>
-</ul></div>
-<div class="paragraph"><p>El diario de APD aparecerá en <em>Subsurface</em>. El techo generado por el ordenador
-Inspiration puede visualizarse seleccionando el correspondiente botón de la
-izquierda del <strong>Perfil de inmersión</strong>. Los datos de presión de las botellas no
-se registran en el equipo APD pero pueden completarse a mano desde la pestaña
-<strong>Equipo</strong>.</p></div>
-</div>
-</div>
-</div>
-<div class="sect1">
-<h2 id="_apendice_c_exportar_informacion_de_diarios_desde_otros_softwares_externos">18. APÉNDICE C: Exportar información de diarios desde otros softwares externos.</h2>
-<div class="sectionbody">
-<div class="paragraph"><p>La importación de datos de diarios de buceos desde softwares externos se
-efectúa, habitualmente, utilizando el dialogo que resulta de seleccionar
-<em>Importar</em> desde el menú principal y luego Importar archivos de registro. Este
-proceso se efectúa en un solo paso y puede obtenerse más información
-<a href="#Unified_import">aquí</a> . Sin embargo, en algunos casos, puede ser necesario
-efectuar dos pasos:</p></div>
-<div class="olist arabic"><ol class="arabic">
-<li>
-<p>
-Exportar los datos del diario externo a un formato accesible por
- <em>Subsurface</em>.
-</p>
-</li>
-<li>
-<p>
-Importar el diario accesible a <em>Subsurface</em>.
-</p>
-</li>
-</ol></div>
-<div class="paragraph"><p>Este apéndice proporciona algo de información sobre como exportar datos de
-diarios desde softwares externos. Los procedimientos a continuación se aplican
-mayormente en Linux y/o Windows.</p></div>
-<div class="sect2">
-<h3 id="S_ImportingDivesSuunto">18.1. Exportar desde <strong>Suunto Divemanager (DM3, DM4 o DM5)</strong></h3>
-<div class="admonitionblock">
-<table><tr>
-<td class="icon">
-<img src="images/icons/suuntologo.jpg" alt="Note" />
-</td>
-<td class="content">Divemanager es una aplicación en MS Windows para ordenadores de buceo Suunto.
-Divemanager 3 (DM3) es una versión más antigua del software de Suunto. Los
-ordenadores de buceo más recientes usan Divemanager 4 o 5 (DM4 o DM5). Las
-diferentes versiones de Divemanager usan diferentes métodos y diferentes
-nomenclaturas de archivos al exportar datos.</td>
-</tr></table>
-</div>
-<div class="paragraph"><p><strong>Divemanager 3 (DM3):</strong></p></div>
-<div class="olist arabic"><ol class="arabic">
-<li>
-<p>
-Iniciar <em>Suunto Divemanager 3</em> y registrarse con el nombre que contiene los
- diarios.
-</p>
-</li>
-<li>
-<p>
-No iniciar el ayudante de importación para importar inmersiones desde el
- ordenador de buceo.
-</p>
-</li>
-<li>
-<p>
-En el árbol de la izquierda de la ventana del programa, seleccionar las
- inmersiones que correspondan.
-</p>
-</li>
-<li>
-<p>
-De la lista de buceos, seleccionar las inmersiones que se deseará descargar
- después:
-</p>
-<div class="ulist"><ul>
-<li>
-<p>
-Para seleccionar alguna: mantén pulsada la tecla <em>ctrl</em> y haz clic en la
- inmersión.
-</p>
-</li>
-<li>
-<p>
-Para seleccionarlas todas: Selecciona la primera, mantén pulsada la tecla
- <em>shift</em> y haz clic en la última inmersión.
-</p>
-</li>
-</ul></div>
-</li>
-<li>
-<p>
-Con las inmersiones marcadas se usa el menú <em>File → Export</em>
-</p>
-</li>
-<li>
-<p>
-Se mostrará el desplegable de exportación. En este desplegable hay un campo
- llamado Export Path.
-</p>
-<div class="ulist"><ul>
-<li>
-<p>
-Haz clic en el botón browse junto al campo Export Path
-</p>
-<div class="ulist"><ul>
-<li>
-<p>
-Se despliega un navegador de archivos
-</p>
-</li>
-</ul></div>
-</li>
-<li>
-<p>
-Navega a la carpeta donde quieras que se guarde el archivo Divelog.SDE
-</p>
-<div class="ulist"><ul>
-<li>
-<p>
-Opcionalmente cambia el nombre del archivo a guardar.
-</p>
-</li>
-<li>
-<p>
-Clica <em>Save</em>.
-</p>
-</li>
-</ul></div>
-</li>
-<li>
-<p>
-De vuelta en el desplegable de exportación, pulsa el botón <em>Export</em>.
-</p>
-</li>
-</ul></div>
-</li>
-<li>
-<p>
-Las inmersiones han quedado exportadas en el archivo Divelogs.SDE.
-</p>
-</li>
-</ol></div>
-<div class="paragraph"><p><strong>Divemanager 4 (DM4) y Divemanager 5 (DM5):</strong></p></div>
-<div class="paragraph"><p>DM4 y DM5 utilizan idénticos mecanismos para exportar los diarios.
-Para exportar un diario desde Divemanager, se necesita localizar la base de
-datos DM4/DM5 donde están guardadas las inmersiones. El usuario puede buscar la
-base de datos original o hacer una copia de respaldo. A continuación se
-describen ambos métodos.</p></div>
-<div class="paragraph"><p>Localizar la base de datos Suunto DM4 (o DM5):</p></div>
-<div class="olist arabic"><ol class="arabic">
-<li>
-<p>
-Iniciar Suunto DM4/DM5
-</p>
-</li>
-<li>
-<p>
-Seleccionar <em>Help → About</em> (Ayuda → Acerca de)
-</p>
-</li>
-<li>
-<p>
-Hacer clic en el botón <em>Copy</em> (Copiar) tras el texto <em>Copy log folder path to
- clipboard</em> (Copiar la ruta a la carpeta del registro al portapapeles)
-</p>
-</li>
-<li>
-<p>
-Abrir el explorador de Windows
-</p>
-</li>
-<li>
-<p>
-Pegar la ruta en la casilla de direcciones en la parte de arriba del
- explorador
-</p>
-</li>
-<li>
-<p>
-La base de datos se llama DM4.db o DM5.db
-</p>
-</li>
-</ol></div>
-<div class="paragraph"><p>Hacer una copia de respaldo de la base de datos de Suunto DM4/DM5:</p></div>
-<div class="olist arabic"><ol class="arabic">
-<li>
-<p>
-Iniciar Suunto DM4/DN5
-</p>
-</li>
-<li>
-<p>
-Seleccionar <em>File → Create backup</em> (Archivo → Copia de seguridad)
-</p>
-</li>
-<li>
-<p>
-Desde el menú de archivos, seleccionar la carpeta y el nombre para la copia,
-aquí usaremos DM4 (o DM5) con la extensión por defecto .bak
-</p>
-</li>
-<li>
-<p>
-Clicar <em>Save</em> (Guardar)
-</p>
-</li>
-<li>
-<p>
-Los buceos se han exportado al archivo DM4.bak (o DM5.bak)
-</p>
-</li>
-</ol></div>
-</div>
-<div class="sect2">
-<h3 id="Atomic_Export">18.2. Exportar desde Atomic Logbook</h3>
-<div class="admonitionblock">
-<table><tr>
-<td class="icon">
-<img src="./images/icons/note.png" alt="Note" />
-</td>
-<td class="content">Atomic Logbook es un software en Windows de Atomics Aquatics. Permite descargar
-información de buceo de los ordenadores Cobalt y Cobalt 2. El archivo se guarda
-en una base de datos SQlite en C:\ProgramData\AtomicsAquatics\Cobalt-Logbook\Cobalt.db.
-Este archivo se puede importar directamente a <em>Subsurface</em>.</td>
-</tr></table>
-</div>
-</div>
-<div class="sect2">
-<h3 id="Mares_Export">18.3. Exportar desde Mares Dive Organiser V2.1</h3>
-<div class="admonitionblock">
-<table><tr>
-<td class="icon">
-<img src="images/icons/mareslogo.jpg" alt="Note" />
-</td>
-<td class="content">Mares Dive Organiser es una aplicación de Windows. El diario de inmersiones se
-guarda en una base de datos Microsoft SQL Compact Edition con una extensión de
-nombre de archivo <em>.sdf</em>. La base de datos incluye a todos los buceadores
-registrados en el Dive Organiser del PC y a todos los ordenadores Mares usados.
-La forma más segura de obtener una copia de la base de datos de inmersiones es
-exportar la información a otro formato compatible que pueda ser importado a
-<em>Subsurface</em>.</td>
-</tr></table>
-</div>
-<div class="olist arabic"><ol class="arabic">
-<li>
-<p>
-En el Dive Organiser, selecciona <em>Database → Backup</em> en el menú principal y
- haz una copia de seguridad de la base de datos en el escritorio. Esto creará un
- archivo comprimido DiveOrganiserxxxxx.dbf
-</p>
-</li>
-<li>
-<p>
-Cambia el nombre del archivo a DiveOrganiserxxxxx.zip. Dentro de una carpeta
- comprimida en el archivo .zip, hay otro archivo llamado <em>DiveOrganiser.sdf</em>.
-</p>
-</li>
-<li>
-<p>
-Extrae a tu escritorio el archivo <em>.sdf</em> desde la carpeta comprimida.
-</p>
-</li>
-<li>
-<p>
-La password para acceder al archivo .zip es <em>mares</em>.
-</p>
-</li>
-</ol></div>
-</div>
-<div class="sect2">
-<h3 id="S_ImportingDivingLog">18.4. Exportar desde <strong>DivingLog 5.0 y 6.0</strong></h3>
-<div class="admonitionblock">
-<table><tr>
-<td class="icon">
-<img src="images/icons/divingloglogo.jpg" alt="Note" />
-</td>
-<td class="content">La mejor manera de traer tus diarios desde DivingLog a <em>Subsurface</em> es
-convertir la base de datos completa. Esto se debe a que otros formatos de
-exportación no incluyen todos los detalles, y careceríamos, por ejemplo, de
-cambios de gas e información acerca de que unidades se utilizan. Al importar
-la base de datos, toda esta información esta incluida y disponible.</td>
-</tr></table>
-</div>
-<div class="paragraph"><p>Para transferir todos los archivos desde DivingLog a <em>Subsurface</em> haz lo
-siguiente:</p></div>
-<div class="olist arabic"><ol class="arabic">
-<li>
-<p>
-En DivingLog abre el menú <em>Archivo → Exportar → SQLite</em>
-</p>
-</li>
-<li>
-<p>
-Selecciona el botón <em>Ajustes</em>
-</p>
-</li>
-<li>
-<p>
-Ajusta el <em>RTF2Plaintext</em> a <em>true</em>
-</p>
-</li>
-<li>
-<p>
-Cierra el diálogo <em>Ajustes</em>
-</p>
-</li>
-<li>
-<p>
-Pulsa el botón <em>Exportar</em> y selecciona el nombre de archivo
-</p>
-</li>
-</ol></div>
-<div class="paragraph"><p>Una vez hecho esto, abre con <em>Subsurface_la base de datos guardada y las
-inmersiones se convertirán automáticamente a nuestro formato. El último paso
-a efectuar es guardar el diario en _Subsurface</em>.</p></div>
-</div>
-</div>
-</div>
-<div class="sect1">
-<h2 id="S_Appendix_D">19. APÉNDICE D: Exportar una hoja de cálculo a formato CSV</h2>
-<div class="sectionbody">
-<div class="paragraph"><p>Muchos buceadores mantienen un diario en alguna forma de archivo digital, en
-muchos casos en una hoja de cálculo con varios campos de información. Estos
-registros se pueden importar con facilidad a <em>Subsurface</em>
-una vez que la hoja de cálculo se ha convertido a archivo .CSV .
-Esta sección explica el procedimiento para convertir un diario de buceo que
-se haya conservado en una hoja de cálculo en un archivo .CSV que se pueda,
-posteriormente, importar a <em>Subsurface</em>.
-Crear un .CSV es una tarea sencilla, aunque el procedimiento es algo distinto
-según el programa de hojas de cálculo que se utilice.</p></div>
-<div class="paragraph"><p>El primer paso consiste en organizar los datos en la hoja de cálculo, de forma
-que la primera fila contenga los nombres (o títulos) de cada columna y que la
-información de cada inmersión ocupe una sola fila.
-<em>Subsurface</em> soporta muchos tipos de datos (Número, Fecha, Hora, Duración,
-Ubicación, GPS, Prof. máxima, Prof. media, Compañero, Notas, Lastre y Etiquetas).
-El usuario puede organizar los datos siguiendo unas sencillas reglas:</p></div>
-<div class="olist arabic"><ol class="arabic">
-<li>
-<p>
-Fecha: Usar uno de los siguientes formatos: aaaa-mm-dd, dd.mm.aaaa o
- mm/dd/aaaa
-</p>
-</li>
-<li>
-<p>
-Duración: El formato debería ser minutos:segundos
-</p>
-</li>
-<li>
-<p>
-Sistema de unidades: Solo debe usarse un sistema. Evitar la mezcla sistemas.
-</p>
-</li>
-<li>
-<p>
-Etiquetas y compañeros: los valores deben separarse usando una coma.
-</p>
-</li>
-<li>
-<p>
-Posición GPS: Se deben utilizar grados decimales, p.e. 30.22496 30.821798
-</p>
-</li>
-</ol></div>
-<div class="sect2">
-<h3 id="_em_libreoffice_calc_em_y_em_openoffice_calc_em">19.1. <em>LibreOffice Calc</em> y <em>OpenOffice Calc</em></h3>
-<div class="paragraph"><p>Son aplicaciones de hojas de cálculo de código abierto que forman parte de
-suits mayores que, a su vez, también son código abierto. La interacción del
-usuario con <em>LibreOffice Calc</em> y _OpenOffice Calc_es muy similar.</p></div>
-<div class="paragraph"><p>En LibreOffice Calc el formato de tiempo debe ajustarse a minutos:segundos -
-[mm]:ss y las fechas se deben ajustar a aaaa-mm-dd, dd.mm.aaaa o mm/dd/aaaa.
-Un diario típico codría parecerse a esto:</p></div>
-<div class="imageblock" style="text-align:center;">
-<div class="content">
-<img src="images/LOffice_spreadsheetdata.jpg" alt="FIGURA: Datos de una hoja de cálculo" />
-</div>
-</div>
-<div class="paragraph"><p>Para exportar los datos en archivo .CSV, desde LibreOffice clicar <em>Archivo →
- Guardar como</em>. En el diálogo que se desplegará, seleccionar <em>Texto CSV (.csv)</em>
-como tipo de archivo y seleccionar la opción <em>Editar ajustes de filtros</em>.</p></div>
-<div class="imageblock" style="text-align:center;">
-<div class="content">
-<img src="images/LOffice_save_as_options.jpg" alt="FIGURA: Opciones de Guardar como" />
-</div>
-</div>
-<div class="paragraph"><p>Tras seleccionar <em>Guardar</em>, seleccionar el delimitador de campos apropiado
-(selecciona <em>TABULADOR</em> para evitar conflictos con las comas cuando estas se
-usen como coma decimal), luego seleccionar <em>OK</em>.</p></div>
-<div class="imageblock" style="text-align:center;">
-<div class="content">
-<img src="images/LOffice_field_options.jpg" alt="FIGURA: Opciones de campos" />
-</div>
-</div>
-<div class="paragraph"><p>Se puede verificar el archivo .CSV abriéndolo con un editor de textos y luego
-se importaría como se explicó en <a href="#S_ImportingCSVDives">Importar inmersiones desde archivos <em>CSV</em> manuales</a>.</p></div>
-</div>
-<div class="sect2">
-<h3 id="_microsoft_em_excel_em">19.2. Microsoft <em>Excel</em></h3>
-<div class="paragraph"><p>El delimitador de campos (llamado "separador de listas" en los manuales de
-Microsoft) no está accesible desde <em>Excel</em> y debe ajustarse desde el <em>Panel de
-Control</em>. Tras cambiar el carácter separador todo el software del ordenador con
-Windows usará el nuevo carácter como separador.
-Se puede volver a cambiar el carácter al inicial siguiendo el mismo sistema.</p></div>
-<div class="ulist"><ul>
-<li>
-<p>
-En Microsoft Windows, pulsar el botón <strong>Inicio</strong> y seleccionar el <em>Panel de
- Control</em> de la lista de la izquierda.
-</p>
-</li>
-<li>
-<p>
-Abrir el diálogo <em>Opciones de región y lenguaje</em>.
-</p>
-</li>
-<li>
-<p>
-Hacer una de las dos siguientes acciones:
-</p>
-<div class="ulist"><ul>
-<li>
-<p>
-En Windows 7, clicar la pestaña <em>Formatos</em> y luego <em>Personalizar este
- formato</em>
-</p>
-</li>
-<li>
-<p>
-En Windows XP, clicar la pestaña <em>Opciones de región</em> y luego <em>Personalizar</em>.
-</p>
-</li>
-</ul></div>
-</li>
-<li>
-<p>
-Teclear un nuevo separador en el <em>Separador de listas</em>. Para utilizar un
- tabulador teclea "TAB" en la casilla de texto.
-</p>
-</li>
-<li>
-<p>
-Pulsar <em>OK</em> dos veces.
-</p>
-</li>
-</ul></div>
-<div class="paragraph"><p>A continuación, una imagen del <em>Panel de Control</em>:</p></div>
-<div class="imageblock" style="text-align:center;">
-<div class="content">
-<img src="images/Win_SaveCSV2.jpg" alt="FIGURA: Separador de listas en Win" />
-</div>
-</div>
-<div class="paragraph"><p>Para exportar el archivo en formato CSV:</p></div>
-<div class="paragraph"><p>Con el diario abierto en <em>Excel</em>, seleccionar el botón redondo de Windows de
-arriba a la izquierda, luego <em>Guardar como</em>.</p></div>
-<div class="imageblock" style="text-align:center;">
-<div class="content">
-<img src="images/Win_SaveCSV1.jpg" alt="FIGURA: Opción Guardar como en Excel" />
-</div>
-</div>
-<div class="paragraph"><p>Clicar en la parte izquierda de la opción <em>Guardar como</em>, <strong>NO</strong> sobre la flecha
-de la derecha. Esto desplegará un diálogo para guardar la hoja de cálculo en un
-formato alternativo. De la lista desplegable abajo en el diálogo, seleccionar
-<em>CSV(delimitado por comas) (*.CSV)</em>. Asegurarse de que se ha seleccionado la
-carpeta correcta para guardar el archivo.</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>Seleccionar el botón <em>Guardar</em>. El archivo formateado en <em>CSV</em> se guardará en la
-carpeta que se hubiera seleccionado. Se puede verificar el archivo creado con
-un editor de textos y luego importar los datos de buceo como se explicó en
-<a href="#S_ImportingCSVDives">Importar inmersiones desde archivos <em>CSV</em> manuales</a>.</p></div>
-</div>
-</div>
-</div>
-<div class="sect1">
-<h2 id="S_APPENDIX_E">20. APÉNDICE E: Escribir una plantilla de impresión a medida</h2>
-<div class="sectionbody">
-<div class="paragraph"><p><em>Subsurface</em> proporciona un mecanismo para crear o modificar plantillas que
-permite producir impresiones a medida de los divelogs. Las plantillas escritas
-en HTML, y también como sencillo conjunto de instrucciones de Grantlee, se
-interpretan y envian a la impresora por <em>Subsurface</em>.</p></div>
-<div class="paragraph"><p>Se accede a las plantillas utilizando el diálogo de impresión (imagen <strong>B</strong> a
-continuación)</p></div>
-<div class="imageblock" style="text-align:center;">
-<div class="content">
-<img src="images/Print1_f22.jpg" alt="FIGURA: Diálogo de impresión" />
-</div>
-</div>
-<div class="paragraph"><p>Los botones en la parte de abajo de diálogo permiten <em>Editar</em>, <em>Borrar</em>,
-<em>Importar</em> y <em>Exportar</em> plantillas (ver imagen <strong>A</strong> anterior). Las plantillas,
-nuevas o modificadas, se guardan como archivos HTML en la misma carpeta en la
-que está el divelog que se está procesando. Para crear o modificar una plantilla,
-selecciona la plantilla <em>Custom</em> de la lista desplegable (imagen <strong>B</strong> anterior) y
-pulsa <em>Editar</em>.</p></div>
-<div class="paragraph"><p>El panel de edición incluye tres pestañas:</p></div>
-<div class="imageblock" style="text-align:center;">
-<div class="content">
-<img src="images/Template1_f22.jpg" alt="FIGURA: Diálogo de edición de plantillas" />
-</div>
-</div>
-<div class="paragraph"><p>1) La pestaña <em>Estilo</em> (imagen <strong>A</strong> anterior) controla la fuente, el espaciado de
- lineas y la plantilla de colores utilizada para imprimir. Los atributos de estilo
- son editables. Elige una de las cuatro paletas.</p></div>
-<div class="paragraph"><p>2) La pestaña <em>Colores</em> (imagen <strong>B</strong> anterior) permite editar los colores que se
- usarán para imprimir el registro. Los colores se pueden modificar: el botón
- <em>Editar</em> de la pestaña <em>Colores</em> permite elegir colores arbitrarios para los
- diferentes componentes de la impresión.</p></div>
-<div class="paragraph"><p>3) La pestaña <em>Plantilla</em> del panel de edición (imagen a continuación) permite crear
- una plantilla usando HTML y sentencias de Grantlee. Grantlee proporciona la
- habilidad de crear y formatear código HTML de forma muy simple pero muy eficiente
- (ver a continuación). El HTML de la plantilla puede editarse y guardarse. La
- plantilla salvada se guarda en la carpeta en la que está el divelog con el que
- se está trabajando. Por defecto, una plantilla <em>a medida</em> es un esqueleto sin
- instrucciones de impresión. La información a imprimir necesita ser especificada
- y formateada reemplazando la sección "<!-- Template must be filled -→".
- Escribir código HtMl con Grantlee da una libertad ilimitada para elegir lo que
- se imprime y como se va a visualizar.</p></div>
-<div class="imageblock" style="text-align:center;">
-<div class="content">
-<img src="images/Template2_f22.jpg" alt="FIGURE:Template tab" />
-</div>
-</div>
-<div class="paragraph"><p>El usuario también puede adaptar las plantillas existentes y guardarlas en la
-carpeta donde se halle el divelog (por ejemplo One Dive, Six Dives, Table, etc).</p></div>
-<div class="paragraph"><p>Para escribir una plantilla a medida, deben existir los siguientes elementos
-para que puedan ser manejadas e interpretadas:</p></div>
-<div class="sect2">
-<h3 id="_bucle_principal">20.1. Bucle principal</h3>
-<div class="paragraph"><p><em>Subsurface</em> pasa una lista de inmersiones llamada (<strong>dives</strong>) al sistema <em>Grantlee</em>.
-Se puede iterar sobre la lista de la siguiente manera:</p></div>
-<div class="literalblock">
-<div class="title">template.html</div>
-<div class="content">
-<pre><code> {% for dive in dives %}
- <h1> {{ dive.number }} </h1>
- {% endfor %}</code></pre>
-</div></div>
-<div class="literalblock">
-<div class="title">output.html</div>
-<div class="content">
-<pre><code> <h1> 1 </h1>
- <h1> 2 </h1>
- <h1> 3 </h1></code></pre>
-</div></div>
-<div class="paragraph"><p>Se puede encontrar información sobre <em>Grantlee</em> <a href="http://www.grantlee.org/apidox/for_themers.html">aquí</a></p></div>
-</div>
-<div class="sect2">
-<h3 id="_variables_pasadas_a_grantlee">20.2. Variables pasadas a Grantlee</h3>
-<div class="paragraph"><p>Solo se pasa un subconjunto de los datos de una inmersión:</p></div>
-<div class="tableblock">
-<table rules="all"
-width="100%"
-frame="border"
-cellspacing="0" cellpadding="4">
-<col width="50%" />
-<col width="50%" />
-<tbody>
-<tr>
-<td align="left" valign="top"><p class="table"><strong>Nombre</strong></p></td>
-<td align="left" valign="top"><p class="table"><strong>Descripción</strong></p></td>
-</tr>
-<tr>
-<td align="left" valign="top"><p class="table">number</p></td>
-<td align="left" valign="top"><p class="table">(<strong>int</strong>) número de la inmersión</p></td>
-</tr>
-<tr>
-<td align="left" valign="top"><p class="table">id</p></td>
-<td align="left" valign="top"><p class="table">(<strong>int</strong>) diveID único, se usará para descargar el perfil</p></td>
-</tr>
-<tr>
-<td align="left" valign="top"><p class="table">date</p></td>
-<td align="left" valign="top"><p class="table">(<strong>string</strong>) fecha de la inmersión</p></td>
-</tr>
-<tr>
-<td align="left" valign="top"><p class="table">time</p></td>
-<td align="left" valign="top"><p class="table">(<strong>string</strong>) hora de la inmersión</p></td>
-</tr>
-<tr>
-<td align="left" valign="top"><p class="table">location</p></td>
-<td align="left" valign="top"><p class="table">(<strong>string</strong>) ubicación del buceo</p></td>
-</tr>
-<tr>
-<td align="left" valign="top"><p class="table">duration</p></td>
-<td align="left" valign="top"><p class="table">(<strong>string</strong>) duración del buceo</p></td>
-</tr>
-<tr>
-<td align="left" valign="top"><p class="table">depth</p></td>
-<td align="left" valign="top"><p class="table">(<strong>string</strong>) profundidad de la inmersión</p></td>
-</tr>
-<tr>
-<td align="left" valign="top"><p class="table">divemaster</p></td>
-<td align="left" valign="top"><p class="table">(<strong>string</strong>) datos del divemaster</p></td>
-</tr>
-<tr>
-<td align="left" valign="top"><p class="table">buddy</p></td>
-<td align="left" valign="top"><p class="table">(<strong>string</strong>) datos del compañero</p></td>
-</tr>
-<tr>
-<td align="left" valign="top"><p class="table">airTemp</p></td>
-<td align="left" valign="top"><p class="table">(<strong>string</strong>) temperatura del aire</p></td>
-</tr>
-<tr>
-<td align="left" valign="top"><p class="table">waterTemp</p></td>
-<td align="left" valign="top"><p class="table">(<strong>string</strong>) temperatura del agua</p></td>
-</tr>
-<tr>
-<td align="left" valign="top"><p class="table">notes</p></td>
-<td align="left" valign="top"><p class="table">(<strong>string</strong>) notas de la inmersión</p></td>
-</tr>
-<tr>
-<td align="left" valign="top"><p class="table">rating</p></td>
-<td align="left" valign="top"><p class="table">(<strong>int</strong>) calificación del buceo, varía entre 0 y 5</p></td>
-</tr>
-<tr>
-<td align="left" valign="top"><p class="table">sac</p></td>
-<td align="left" valign="top"><p class="table">(<strong>string</strong>) valor del CAS</p></td>
-</tr>
-<tr>
-<td align="left" valign="top"><p class="table">tags</p></td>
-<td align="left" valign="top"><p class="table">(<strong>string</strong>) todas las etiquetas de la inmersión empalmadas</p></td>
-</tr>
-<tr>
-<td align="left" valign="top"><p class="table">gas</p></td>
-<td align="left" valign="top"><p class="table">(<strong>string</strong>) datos de la botella</p></td>
-</tr>
-</tbody>
-</table>
-</div>
-<div class="paragraph"><p><em>Subsurface</em> también pasa datos de la plantilla <strong>template_options</strong>. Estos datos
-deben usarse como valores <em>CSS</em> para proporcionar una plantilla editable de
-forma dinámica. Los datos exportados se muestran en la tabla a continuación:</p></div>
-<div class="tableblock">
-<table rules="all"
-width="100%"
-frame="border"
-cellspacing="0" cellpadding="4">
-<col width="50%" />
-<col width="50%" />
-<tbody>
-<tr>
-<td align="left" valign="top"><p class="table"><strong>Nombre</strong></p></td>
-<td align="left" valign="top"><p class="table"><strong>Descripción</strong></p></td>
-</tr>
-<tr>
-<td align="left" valign="top"><p class="table">font</p></td>
-<td align="left" valign="top"><p class="table">(<strong>string</strong>) familia de la fuente</p></td>
-</tr>
-<tr>
-<td align="left" valign="top"><p class="table">borderwidth</p></td>
-<td align="left" valign="top"><p class="table">(<strong>int</strong>) valor de la anchura del borde, calculado dinámicamente
-como 0.1% de la anchura de la página con un valor mínimo de 1px</p></td>
-</tr>
-<tr>
-<td align="left" valign="top"><p class="table">font_size</p></td>
-<td align="left" valign="top"><p class="table">(<strong>double</strong>) tamaño de la fuente en vw, varía entre 1.0 y 2.0</p></td>
-</tr>
-<tr>
-<td align="left" valign="top"><p class="table">line_spacing</p></td>
-<td align="left" valign="top"><p class="table">(<strong>double</strong>) distancia entre líneas de texto, varía entre 1.0 y 3.0</p></td>
-</tr>
-<tr>
-<td align="left" valign="top"><p class="table">color1</p></td>
-<td align="left" valign="top"><p class="table">(<strong>string</strong>) color del fondo</p></td>
-</tr>
-<tr>
-<td align="left" valign="top"><p class="table">color2</p></td>
-<td align="left" valign="top"><p class="table">(<strong>string</strong>) color primario de las celdas de la tabla</p></td>
-</tr>
-<tr>
-<td align="left" valign="top"><p class="table">color3</p></td>
-<td align="left" valign="top"><p class="table">(<strong>string</strong>) color secundario de las celdas de la tabla</p></td>
-</tr>
-<tr>
-<td align="left" valign="top"><p class="table">color4</p></td>
-<td align="left" valign="top"><p class="table">(<strong>string</strong>) color primario del texto</p></td>
-</tr>
-<tr>
-<td align="left" valign="top"><p class="table">color5</p></td>
-<td align="left" valign="top"><p class="table">(<strong>string</strong>) color secundario del texto</p></td>
-</tr>
-<tr>
-<td align="left" valign="top"><p class="table">color6</p></td>
-<td align="left" valign="top"><p class="table">(<strong>string</strong>) colores de los bordes</p></td>
-</tr>
-</tbody>
-</table>
-</div>
-<div class="literalblock">
-<div class="title">template.html</div>
-<div class="content">
-<pre><code> border-width: {{ template_options.borderwidth }}px;</code></pre>
-</div></div>
-<div class="literalblock">
-<div class="title">output.html</div>
-<div class="content">
-<pre><code> border-width: 3px;</code></pre>
-</div></div>
-<div class="paragraph"><p>Otra variable que pasa <em>Subsurface</em> es <strong>print_options</strong>. Esta variable solo
-contiene un único valor:</p></div>
-<div class="tableblock">
-<table rules="all"
-width="100%"
-frame="border"
-cellspacing="0" cellpadding="4">
-<col width="50%" />
-<col width="50%" />
-<tbody>
-<tr>
-<td align="left" valign="top"><p class="table"><strong>Nombre</strong></p></td>
-<td align="left" valign="top"><p class="table"><strong>Descripción</strong></p></td>
-</tr>
-<tr>
-<td align="left" valign="top"><p class="table">grayscale</p></td>
-<td align="left" valign="top"><p class="table">Utiliza filtros <em>CSS</em> para convertir la página a escala de grises
-(debe añadirse al estilo del cuerpo para activar la impresión en blanco y negro)</p></td>
-</tr>
-</tbody>
-</table>
-</div>
-<div class="literalblock">
-<div class="title">template.html</div>
-<div class="content">
-<pre><code> body {
- {{ print_options.grayscale }};
- }</code></pre>
-</div></div>
-<div class="literalblock">
-<div class="title">output.html</div>
-<div class="content">
-<pre><code> body {
- -webkit-filter: grayscale(100%);
- }</code></pre>
-</div></div>
-</div>
-<div class="sect2">
-<h3 id="_selectores_css_definidos">20.3. Selectores CSS definidos</h3>
-<div class="paragraph"><p>Como el perfil se coloca después del renderizado, <em>Subsurface</em> usa unos selectores
-<em>CSS</em> especiales para ejecutar algunas búsquedas en la salida HTML. Deben añadirse
-los selectores de la siguiente tabla:</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>Selector</strong></p></td>
-<td align="left" valign="top"><p class="table"><strong>Tipo</strong></p></td>
-<td align="left" valign="top"><p class="table"><strong>Descripción</strong></p></td>
-</tr>
-<tr>
-<td align="left" valign="top"><p class="table">dive_{{ dive.id }}</p></td>
-<td align="left" valign="top"><p class="table">id</p></td>
-<td align="left" valign="top"><p class="table">se utiliza para descargar el perfil de inmersión
-correspondiente</p></td>
-</tr>
-<tr>
-<td align="left" valign="top"><p class="table">diveProfile</p></td>
-<td align="left" valign="top"><p class="table">class</p></td>
-<td align="left" valign="top"><p class="table">cada div que contendrá un perfil de inmersión debe tener
-este selector de clase añadido al selector divee_{{ dive.id }}</p></td>
-</tr>
-<tr>
-<td align="left" valign="top"><p class="table">dontbreak</p></td>
-<td align="left" valign="top"><p class="table">class</p></td>
-<td align="left" valign="top"><p class="table">evita que el div que tenga esta clase se divida en dos
-páginas</p></td>
-</tr>
-</tbody>
-</table>
-</div>
-<div class="paragraph"><p>IMPORTANTE: Renderizar perfiles de inmersión no está soportado en plantillas
-de distribución de flujo (cuando datos-número de buceos = 0).</p></div>
-</div>
-<div class="sect2">
-<h3 id="_atributos_especiales">20.4. Atributos especiales</h3>
-<div class="paragraph"><p>Hay dos formas de renderizar: bien renderizar un número concreto de buceos por
-página, bien hacer que <em>Subsurface</em> intente introducir tantas inmersiones como
-sea posible en una sola página.</p></div>
-<div class="paragraph"><p>El atributo de datos <strong>data-numberofdives</strong> se añade a la etiqueta body para
-fijar el modo de renderizado.</p></div>
-<div class="ulist"><ul>
-<li>
-<p>
-Renderizar 6 inmersiones por página:
-</p>
-</li>
-</ul></div>
-<div class="literalblock">
-<div class="content">
-<pre><code> <body data-numberofdives = 6></code></pre>
-</div></div>
-<div class="ulist"><ul>
-<li>
-<p>
-Renderizar tantas inmersiones como sea posible:
-</p>
-</li>
-</ul></div>
-<div class="literalblock">
-<div class="content">
-<pre><code> <body data-numberofdives = 0></code></pre>
-</div></div>
-<div class="paragraph"><p>IMPORTANTE: Todas las unidades CSS deben estar en longitudes relativas para
-imprimir en cualquier tamaño de página.</p></div>
-</div>
-</div>
-</div>
-<div class="sect1">
-<h2 id="S_APPENDIX_F">21. APÉNDICE F: Preguntas Frecuentes</h2>
-<div class="sectionbody">
-<div class="sect2">
-<h3 id="_em_subsurface_em_parece_calcular_mal_el_consumo_de_gas_y_el_cas">21.1. <em>Subsurface</em> parece calcular mal el consumo de gas y el CAS</h3>
-<div class="paragraph" id="SAC_CALCULATION"><p><em>Pregunta</em>: Buceé con una botella de 12,2 l empezando con 220 bar y terminando
-con 100 bar y yo calculo un CAS distinto al que calcula <em>Subsurface</em> ¿Está
-calculándolo mal <em>Subsurface</em>?</p></div>
-<div class="paragraph"><p><em>Respuesta</em>: En realidad no. Lo que sucede es que <em>Subsurface</em> calcula el
-consumo de gas de forma diferente (y mejor) de lo que esperas. En particular,
-tiene en cuenta la incompresibilidad de los gases.
-Tradicionalmente para calcular el consumo y el CAS se usaba</p></div>
-<div class="paragraph"><p><code>consumo = tamaño_de_botella x (presión_inicial - presión_final)</code></p></div>
-<div class="paragraph"><p>y es cierto para un gas ideal y es lo que se enseña en la teoría del buceo. Pero
-actualmente no existe un "gas ideal" y los gases reales no se comprimen
-linealmente con la presión. Además, estás olvidando el hecho de que una
-atmósfera de presión no es un bar. Así pues, el cálculo <strong>real</strong> es</p></div>
-<div class="paragraph"><p><code>consumo = (cantidad_de_aire_al_inicio - cantidad_de_aire_al_final)</code></p></div>
-<div class="paragraph"><p>donde la cantidad de aire <strong>no</strong> es simplemente "tamaño_de_botella x
-presión_en_bares". Es una combinación de "tener en cuenta la compresibilidad de
-los gases" (que es bastante poco a 220 bar pero se nota mucho más a 300 bar) y
-"convertir los bares en atmósferas" (que es la mayor parte de la discrepancia).
-Recuerda: una atm es ~1.013 bar, por tanto sin compresibilidad, tu uso de gas es
-:</p></div>
-<div class="paragraph"><p><code>12.2*((220-100)/1.013)</code></p></div>
-<div class="paragraph"><p>que es aproximadamente 1445, no 1464. Así pues había 19 litros de más en tu
-cálculo que ignoraba la diferencia entre bar y atm. La compresibilidad aparece
-por encima de 200 bar y reduce los 1445 en unos 8 litros más por lo que
-realmente usaste unos 1437 litros al nivel del mar.</p></div>
-<div class="paragraph"><p>Por lo tanto, alégrate: tu CAS es mejor de lo que tus cálculos indicaban. O
-entristécete: tu botella contiene menos aire de lo que pensabas. Y como
-mencionábamos el "contiene menos aire de lo que pensabas" se hace más notorio a
-altas presiones. A 400 bar realmente no contiene el doble de aire que a 200 bar.
-A presiones más bajas, el aire se comporta bastante como un gas ideal.</p></div>
-</div>
-<div class="sect2">
-<h3 id="_algunos_perfiles_de_inmersion_tienen_discrepancias_de_tiempos_con_las_muestras_que_toma_mi_ordenador_de_buceo">21.2. Algunos perfiles de inmersión tienen discrepancias de tiempos con las muestras que toma mi ordenador de buceo …</h3>
-<div class="paragraph"><p><em>Subsurface</em> termina por ignorar el tiempo en superficie por varios motivos
-(profundidad media, tiempo de inmersión, CAS, etc).</p></div>
-<div class="paragraph"><p><em>Pregunta</em>: ¿Por qué las duraciones de los buceos en mi ordenador difieren de
-los proporcionados por <em>Subsurface</em>?</p></div>
-<div class="paragraph"><p><em>Respuesta</em>: Por ejemplo, si al terminar haces una prueba de lastre
-(suficientemente profunda para iniciar el ordenador de buceo) y luego subes y
-esperas 5 minutos a tus compañeros, tu ordenador puede decir que has hecho una
-inmersión de 50 minutos, pero <em>Subsurface</em> dirá que es de 45 minutos (porque
-realmente has estado buceando 45 minutos). Es mucho más notable si haces cosas
-como actuar de instructor en inmersiones de curso, donde puedes estar en el agua
-mucho rato pero pasar la mayor parte del tiempo en superficie. En este caso no
-querrás que te cuente como algún tipo de inmersión larga.</p></div>
-</div>
-<div class="sect2">
-<h3 id="_se_han_perdido_algunos_perfiles_en_la_descarga">21.3. Se han perdido algunos perfiles en la descarga</h3>
-<div class="paragraph" id="DC_HISTORY"><p><em>Pregunta</em>: No consigo descargar todas mis inmersiones, solo las más recientes,
-incluso aunque el manual de mi ordenador de buceo afirma que guarda el historial
-de, por ejemplo, 999 buceos.</p></div>
-<div class="paragraph"><p><em>Respuesta</em>: El historial de buceo es diferente de los perfiles de inmersión del
-registro. El historial solo conserva rastro del total de inmersiones y el tiempo
-total pasado bajo el agua. Los registros, por otra parte, conservan el perfil de
-inmersión, pero disponen de una cantidad limitada de memoria para hacerlo. La
-cantidad exacta de perfiles que pueden guardarse en un dispositivo dependen del
-intervalo de las muestras y de la duración de los buceos. Una vez que la memoria
-se ha llenado se sobre escriben las inmersiones más antiguas con nuevas. De
-esta forma, solo podemos descargar las últimas 13, 30 o 199 inmersiones.</p></div>
-<div class="paragraph"><p>Si has descargado tus inmersiones a otro divelog antes de que se sobrescribieran,
-hay muchas posibilidades de que Subsurface pueda importarlas. Sin embargo, si los
-registros estaban solo en el ordenador de buceo, no pueden recuperarse tras haber
-sido sobrescritos.</p></div>
-</div>
-</div>
-</div>
-</div>
-<div id="footnotes"><hr /></div>
-<div id="footer">
-<div id="footer-text">
-Last updated 2015-12-15 13:35:29 PST
-</div>
-</div>
-</body>
-</html>
+<!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.9" /> +<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; } + + +@media screen { + body { + max-width: 50em; /* approximately 80 characters wide */ + margin-left: 16em; + } + + #toc { + position: fixed; + top: 0; + left: 0; + bottom: 0; + width: 13em; + padding: 0.5em; + padding-bottom: 1.5em; + margin: 0; + overflow: auto; + border-right: 3px solid #f8f8f8; + background-color: white; + } + + #toc .toclevel1 { + margin-top: 0.5em; + } + + #toc .toclevel2 { + margin-top: 0.25em; + display: list-item; + color: #aaaaaa; + } + + #toctitle { + margin-top: 0.5em; + } +} +</style> +<script type="text/javascript"> +/*<+'])'); + // 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">MANUAL DE USUARIO</span></p></div> +<div class="paragraph"><p><strong>Autores</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>Versión 4.5, Septiembre 2015</em></span></p></div> +<div class="paragraph"><p>Bienvenido como usuario de <em>Subsurface</em>, un avanzado programa de registro de +inmersiones con extensa infraestructura para describir, organizar e +interpretar buceos en apnea o con botella. <em>Subsurface</em> ofrece muchas ventajas +sobre otras soluciones de software similares:</p></div> +<div class="ulist"><ul> +<li> +<p> +¿Necesitas una forma flexible de registrar inmersiones usando equipo +recreativo, incluso aunque no uses ordenador? +</p> +</li> +<li> +<p> +¿Utilizas dos ordenadores de buceo diferentes, cada uno con su software +propietario para descargar los diarios de buceo? ¿Buceas con reciclador y con +circuito abierto o equipo recreativo? ¿Usas un bottom-timer junto a un ordenador +de buceo? <em>Subsurface</em> ofrece una interfaz estándar para descargar diarios de +buceo desde todas estas piezas de equipo y para almacenarlos y analizarlos en un +sistema unificado. +</p> +</li> +<li> +<p> +¿Usas más de un sistema operativo? <em>Subsurface</em> es totalmente compatible con +Mac, Linux y Windows permitiéndote acceder a tu registro de buceo de de la +misma forma desde cualquiera de estos sistemas operativos. +</p> +</li> +<li> +<p> +¿Utilizas Linux o Mac pero tu ordenador de buceo solo tiene software basado en +Windows para descargar la información de buceo (p.e. Mares)? <em>Subsurface</em> te +proporciona una manera de almacenar y analizar las inmersiones en otro sistema +operativo. +</p> +</li> +<li> +<p> +¿Necesitas un planificador de inmersiones gráfico que sea intuitivo, tenga +en cuenta las inmersiones ya guardadas y se integre con ellas? +</p> +</li> +<li> +<p> +¿Necesitas una forma de guardar tus divelogs en internet, que te permita +visualizarlo desde cualquier parte, simplemente usando un navegador web? +</p> +</li> +</ul></div> +<div class="paragraph"><p>Hay binarios disponibles para PCs con Windows (XP o posterior), Macs basados en +Intel (OS/X) y muchas distribuciones de Linux. <em>Subsurface</em> puede compilarse +para muchas otras plataformas de hardware y entornos de software en los que +estén disponibles Qt y libdivecomputer.</p></div> +<div class="paragraph"><p>El ámbito de este documento es el uso del programa <em>Subsurface</em>. Para instalar +el software, consulta la página Descargas en <a href="http://subsurface-divelog.org/">la +web</a>. Por favor, comenta los problemas que tengas con este programa enviando un +mail a <a href="mailto:subsurface@subsurface-divelog.org">nuestra lista de correo</a> e informa de +fallos en <a href="http://trac.hohndel.org">nuestro bugtracker</a>. Para instrucciones acerca +de como compilar el software y (en caso necesario) sus dependencias, por favor, +consulta el archivo INSTALL incluido con el código fuente.</p></div> +<div class="paragraph"><p><strong>Audiencia</strong>: Buceadores recreativos, Buceadores en apnea, Buceadores técnicos, +Buceadores profesionales.</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="_utilizar_este_manual">1. Utilizar este manual</h2> +<div class="sectionbody"> +<div class="paragraph"><p>Cuando se abre desde dentro de <em>Subsurface</em> este manual no tiene controles +externos para paginar o seleccionar páginas anteriores, sin embargo se +proporcionan dos utilidades:</p></div> +<div class="ulist"><ul> +<li> +<p> +La función <em>BUSCAR</em> se activa pulsando control-F o command-F en el teclado. +Aparecerá una ventana de texto al pié de la ventana (ver imagen a continuación). +Por ejemplo, si se tecleó la palabra "<em>lastre</em>" en la casilla de búsqueda, se +buscará esta palabra por todo el manual. A la derecha de la casilla de texto +hay dos flechas, una hacia arriba y otra hacia abajo. Pulsándolas se irá a la +anterior o posterior aparición de la palabra buscada. +</p> +</li> +</ul></div> +<div class="imageblock" style="text-align:center;"> +<div class="content"> +<img src="images/usermanualfunctions.jpg" alt="User manual functions" /> +</div> +</div> +<div class="ulist"><ul> +<li> +<p> +<em>LINK ANTERIOR/POSTERIOR</em>. Se puede navegar entre links (palabras resaltadas +que permiten saltar a secciones específicas del manual) haciendo clic-derecho +en el texto. Esto muestra un menú contextual que permite navegar a links +del manual visitados anteriormente (ver imagen anterior). Por ejemplo, si se +ha seleccionado un link del manual, la opción <em>Atrás</em> muestra el texto del +último link seleccionado. A la inversa, la opción <em>Adelante</em> permite saltar +al texto visitado antes de usar la opción <em>Atrás</em>. La opción <em>Recargar</em> hace +que se recargue el manual completo en la ventana. +</p> +</li> +</ul></div> +</div> +</div> +<div class="sect1"> +<h2 id="S_UserSurvey">2. La Encuesta de Usuarios</h2> +<div class="sectionbody"> +<div class="paragraph"><p>Para poder desarrollar <em>Subsurface</em> de una forma que sirva a sus usuarios de la +mejor manera posible, es importante tener alguna información de los mismos. Al +abrir <em>Subsurface</em> tras haberlo usado una semana más o menos, +se desplegará una encuesta al usuario. Es completamente opcional y el usuario +controla que datos se enviarán al equipo de desarrollo de <em>Subsurface</em>, si es +que se envía alguno. Cualquier dato que el usuario decida enviar será +extremadamente útil, y solo se usará para dirigir el desarrollo futuro y +personalizar el software a medida de los usuarios de <em>Subsurface</em>. Si se +completa la encuesta o se hace clic en la opción "No preguntarme de nuevo, será +la última comunicación de esta naturaleza que se reciba. Sin embargo, si cambian +nuestros hábitos o los de <em>Subsurface</em> y se desea volver a enviar la encuesta, +se puede hacer lanzando <em>Subsurface</em> desde la línea de comandos con la opción +--survey.</p></div> +</div> +</div> +<div class="sect1"> +<h2 id="S_StartUsing">3. Empezar a usar el programa</h2> +<div class="sectionbody"> +<div class="paragraph"><p>La ventana <em>Subsurface</em> está, habitualmente, dividida en cuatro paneles con un +<strong>Menú principal</strong> (Archivo Importar Registro Vista Ayuda) en la parte superior +(en Windows y Linux) o en la parte superior de la pantalla (en Mac y Ubuntu +Unity). Los cuatro paneles son:</p></div> +<div class="olist arabic"><ol class="arabic"> +<li> +<p> +La <strong>Lista de inmersiones</strong> abajo a la izquierda. Contienen una lista de todos +los buceos en tu registro. Puedes seleccionar y resaltar una inmersión de la +lista haciendo clic sobre ella. En casi todos los casos también se pueden +utilizar las teclas de cursor arriba/abajo para cambiar de inmersión. La Lista +de Inmersiones es una herramienta importante para manipular un diario de +inmersiones. +</p> +</li> +<li> +<p> +El <strong>Mapa</strong> abajo a la derecha, muestra los lugares de buceo del usuario en un +mapamundi y aparece centrado en el punto de la última inmersión seleccionada de +la <strong>Lista de Inmersiones</strong>. +</p> +</li> +<li> +<p> +La <strong>Información</strong> arriba a la izquierda, presentando +información más detallada de la inmersión seleccionada en la <strong>Lista de +inmersiones</strong>, incluyendo algunas estadísticas de la inmersión seleccionada o de +todas las inmersiones resaltadas. +</p> +</li> +<li> +<p> +El <strong>Perfil de la inmersión</strong> arriba a la derecha, muestra un perfil gráfico +del buceo seleccionado en la <strong>Lista de inmersiones</strong>. +</p> +</li> +</ol></div> +<div class="paragraph"><p>Los divisores que hay entre los paneles pueden arrastrarse para modificar el +tamaño de cualquiera de ellos. <em>Subsurface</em> recuerda la posición de los +divisores, así, la próxima vez que se inicie <em>Subsurface</em> utiliza las posiciones +utilizadas la vez anterior.</p></div> +<div class="paragraph"><p>Si se selecciona una única inmersión en la <strong>Lista de inmersiones</strong>, se muestra su +ubicación, información detallada y su perfil en sus paneles respectivos. Por +otra parte, si uno selecciona más de un buceo, el último resaltado actuará como +<em>inmersión seleccionada</em>, pero los datos resumidos de las <em>inmersiones +resaltadas</em> se mostrarán en la pestaña <strong>Estadísticas</strong> del panel <strong>Información</strong> +(máximas, mínimas y medias de profundidades, duraciones, +temperaturas del agua, consumos de gases; el tiempo total y el número de +inmersiones seleccionadas).</p></div> +<div class="imageblock" id="S_ViewPanels" style="text-align:center;"> +<div class="content"> +<img src="images/main_window_f22.jpg" alt="La ventana principal" /> +</div> +</div> +<div class="paragraph"><p>El usuario puede elegir cual de los cuatro paneles se mostrará seleccionando la +opción <strong>Vista</strong> en el menú principal, la cual le presentará varias opciones de +visualización:</p></div> +<div class="paragraph"><p><strong>Todo</strong>: muestra los cuatro paneles como en la captura de pantalla de arriba.</p></div> +<div class="paragraph"><p><strong>Lista de inmersiones</strong>: Solo muestra la lista de buceos.</p></div> +<div class="paragraph"><p><strong>Perfil</strong>: Muestra solo el perfil de inmersión del buceo seleccionado.</p></div> +<div class="paragraph"><p><strong>Info</strong>: Solo muestra las notas sobre la última inmersión seleccionada y +estadísticas para todas las resaltadas.</p></div> +<div class="paragraph"><p><strong>Globo</strong>: Solo muestra el mapamundi centrado en la última inmersión seleccionada.</p></div> +<div class="paragraph"><p>Como muchas otras funciones que pueden accederse desde el Menú Principal, estas +opciones también pueden lanzarse utilizando atajos de teclado. Los atajos para +un sistema en particular se muestran con un subrallado en las entradas del menú. +Ya que los diferentes Sistemas Operativos y el lenguaje seleccionado por el +usuario pueden hacer que <em>Subsurface</em> utilice diferentes atajos, no intentaremos +listarlos en este manual.</p></div> +<div class="paragraph"><p>Al iniciar el programa por primera vez no muestra ninguna información. Esto se +debe a que el programa no tiene ninguna información disponible. En las secciones +siguientes se describirán los procedimientos para crear un nuevo registro.</p></div> +</div> +</div> +<div class="sect1"> +<h2 id="S_NewLogbook">4. Crear un nuevo diario</h2> +<div class="sectionbody"> +<div class="paragraph"><p>Selecciona <em>Archivo → Nuevo Registro</em> en el menú principal. Todos los datos de +buceo existentes se borran para poder añadir nueva información. Si hubieran +datos no guardados en un diario abierto, al usuario se le preguntará si desea +guardar el diario abierto antes de crear uno nuevo.</p></div> +</div> +</div> +<div class="sect1"> +<h2 id="S_GetInformation">5. Guardar información en el diario de buceo</h2> +<div class="sectionbody"> +<div class="paragraph"><p>Ahora que se ha creado un nuevo diario, es simple añadirle datos de buceo. +<em>Subsurface</em> permite varias maneras distintas de añadir información a un diario, +todas las cuales las veremos en detalle en las secciones +siguientes.</p></div> +<div class="paragraph"><p>1) Si el usuario tiene un diario en papel, una hoja de cálculo u otra +forma de diario manual, se pueden añadir los datos de una de estas formas:</p></div> +<div class="ulist"><ul> +<li> +<p> +Introducir la información de buceo a mano. Esto es útil si el buceador no +usa un ordenador de buceo y las inmersiones se guardaban en un diario +escrito. Ver <a href="#S_EnterData">Introducir información de buceo a mano</a>. +</p> +</li> +<li> +<p> +Importar datos de buceo que se han guardado bien como hoja de cálculo o +bien como un archivo CSV. Ver el <a href="#S_Appendix_D">APÉNDICE D: Exportar una hoja de cáculo a formato CSV</a> +y el texto <a href="#S_ImportingCSVDives">Importar buceos de archivos <em>CSV</em> creados a mano</a>. +</p> +</li> +</ul></div> +<div class="paragraph"><p>2) Si el usuario ya tiene inmersiones registradas con un ordenador de buceo, +el perfil de profundidad del buceo y otra gran cantidad de información ya está +disponible.Estas inmersiones pueden importarse de las siguientes formas:</p></div> +<div class="ulist"><ul> +<li> +<p> +El propio ordenador de buceo. Ver <a href="#S_ImportDiveComputer">Importar nueva información desde un ordenador de buceo</a>) +</p> +</li> +<li> +<p> +Software propietario distribuido por los fabricantes de los ordenadores de + buceo. + Ver <a href="#S_ImportingAlienDiveLogs">Importar información de inmersiones de otras fuentes u otros formatos de datos</a>. +</p> +</li> +</ul></div> +<div class="sect2"> +<h3 id="S_EnterData">5.1. Introducir información de buceo a mano</h3> +<div class="paragraph"><p>Este es habitualmente el caso para inmersiones sin ordenador de buceo. La unidad +básica de información en <em>Subsurface</em> es una inmersión. La información más +importante en un diario de inmersiones incluye, habitualmente, el tipo de +inmersión, fecha, hora, duración, profundidad, los nombres de los compañeros de +buceo o el dive master o el guía, y algunas anotaciones acerca de la inmersión. +<em>Subsurface</em> puede conservar mucha más información por cada inmersión. Para +añadir una inmersión a un registro de buceo, selecciona <em>Registro → Añadir +Inmersión</em> en el menú principal. El programa muestra entonces tres paneles para +introducir información: Dos pestañas en el panel <strong>Información</strong> +(<strong>Notas</strong> y <strong>Equipo</strong>), así como el panel perfil que muestra un +perfil gráfico de cada buceo. Estos paneles estan marcados respectivamente como +<span class="red">A</span>, <span class="red">B</span> y <span class="red">C</span> en la figura de abajo. Ahora veremos cada una de +las pestañas usadas para introducir la información.</p></div> +<div class="imageblock" style="text-align:center;"> +<div class="content"> +<img src="images/AddDive1_f22.jpg" alt="FIGURA: Añadir inmersión" /> +</div> +</div> +<div class="paragraph"><p>Al editar un campo de los paneles <em>Notas</em> o <em>Equipo</em>, <em>Subsurface</em> +entra en el modo de edición. Esto se indica con el mensaje en un recuadro azul +en la parte de arriba del panel <strong>Notas</strong>. Este mensaje se +muestra en todos los paneles dependientes de <em>Notas</em> mientras +se esté en modo de edición.</p></div> +<div class="imageblock" style="text-align:center;"> +<div class="content"> +<img src="images/BlueEditBar_f22.jpg" alt="Blue edit bar" /> +</div> +</div> +<div class="paragraph"><p>El botón <em>Aplicar cambios</em> solo debería utilizarse cuando todas las partes de la +inmersión hayan sido rellenadas. Cuando se introduzcan inmersiones a mano, +deberían haberse completado las pestañas <em>Información</em>, <em>Equipo</em> y <em>Perfil</em> +antes de guardar la información. Al seleccionar el botón <em>Aplicar cambios</em>, se guarda +en memoria una copia local de la información. Al salir de <em>Subsurface</em>, el +programa preguntará de nuevo, esta vez si se guarda el diario completo en el +disco o no.</p></div> +<div class="sect3"> +<h4 id="S_CreateProfile">5.1.1. Crear un perfil de inmersión</h4> +<div class="paragraph"><p>EL <strong>Perfil de la Inmersión</strong> (una representación gráfica de la profundidad de +buceo en función del tiempo) se muestra en el panel de arriba a la derecha de la +ventana de <em>Subsurface</em> . Cuando se añade manualmente una inmersión a un diario, +<em>Subsurface</em> presenta un perfil por defecto que necesita modificarse para +representar mejor el buceo que se está describiendo.</p></div> +<div class="imageblock" style="text-align:center;"> +<div class="content"> +<img src="images/DiveProfile1_f20.jpg" alt="FIGURA: Perfil de inmersión inicial" /> +</div> +</div> +<div class="paragraph"><p><em>Modificar el perfil de la inmersión</em>: Cuando se mueve el cursor por el perfil, +su posición se indica por dos líneas de colores (roja y verde), como se muestra +a continuación. La profundidad y el tiempo se indican en el cajetín negro de +información. Las +unidades (métricas/imperiales) de los ejes vienen determinadas por los ajustes +de las Preferencias. El perfil de la inmersión comprende varios segmentos +definidos por puntos de referencia (puntos en blanco en el perfil, como los que +se muestran arriba). La profundidad por defecto es de 15m. +Si la profundidad de la inmersión fue de 20m, el usuario tiene que arrastrar los +puntos de referencia adecuados hacia abajo hasta que representen los 20m. Para +añadir un punto hay que hacer doble clic en cualquier segmento. Para borrar un +punto de referencia, hacer clic-derecho sobre él y seleccionar "Borrar este +punto" del menú contextual. También se necesitará arrastrar los puntos para +representar una duración adecuada del buceo. A continuación hay un perfil de +inmersión que representa un buceo a 20m durante 30 minutos, seguido de una +parada de seguridad de 5 minutos a 5m.</p></div> +<div class="imageblock" style="text-align:center;"> +<div class="content"> +<img src="images/DiveProfile2_f20.jpg" alt="FIGURA: Perfil de buceo editado" /> +</div> +</div> +<div class="paragraph"><p><em>Especificar la composición del gas</em>: La composición del gas usado se indica +claramente a lo largo de los segmentos del perfil. Esta resulta, por defecto, en +la primera mezcla de gases especificada en la pestaña <strong>Equipo</strong>, que era aire en +el caso del perfil ilustrado arriba. Las mezclas de gases de los segmentos del +perfil pueden editarse, Esto se hace clicando en la descripción del gas para un +punto de referencia concreto y eligiendo la mezcla apropiada del menú +contextual. Cambiar el gas de un punto de referencia afecta al gas mostrado a la +izquierda <em>a la izquierda</em> del punto. Nótese que únicamente los gases definidos +en la pestaña <strong>Equipo</strong> aparecen en el menú contextual (ver imagen a continuación).</p></div> +<div class="imageblock" style="text-align:center;"> +<div class="content"> +<img src="images/DiveProfile3_f20.jpg" alt="FIGURA: Menú contextual de la composición del gas" /> +</div> +</div> +<div class="paragraph"><p>Habiendo sido definido el perfil, se deben añadir más detalles para tener un +registro más completo del buceo. Para hacer esto, deberían utilizarse las +pestañas <strong>Notas</strong> y <strong>Equipo</strong> arrriba a la izquierda en la ventana de <em>Subsurface</em>. +Haz clic en <a href="#S_Notes_dc"><strong>este enlace</strong></a> para ver instrucciones acerca del +uso de estas pestañas.</p></div> +</div> +</div> +<div class="sect2"> +<h3 id="S_ImportDiveComputer">5.2. Importar nueva información desde un ordenador de buceo</h3> +<div class="sect3"> +<h4 id="_conectar_e_importar_datos_desde_un_ordenador_de_buceo">5.2.1. Conectar e importar datos desde un ordenador de buceo.</h4> +<div class="paragraph"><p>El uso de ordenadores de buceo permite recoger una gran cantidad de información +de cada inmersión, por ejemplo un registro detallado de la profundidad, +duración, ratios de ascenso/descenso y de presiones parciales de los gases. +<em>Subsurface</em> puede capturar esta información y presentarla como parte de la +información de la inmersión. <em>Subsurface</em> puede obtener información de un amplio +abanico de ordenadores de buceo, la última lista de los cuales puede encontrarse +en: +<a href="http://subsurface-divelog.org/documentation/supported-dive-computers/">Ordenadores de buceo soportados.</a></p></div> +<div class="admonitionblock"> +<table><tr> +<td class="icon"> +<img src="images/icons/warning2.png" alt="Warning" /> +</td> +<td class="content">Algunos ordenadores de buceo consumen más energía cuando están en modo +comunicación-PC. <strong>Esto puede descargar la batería del ordenador de buceo</strong>. Así +pues, recomendamos que el usuario verifique si su ordenador está recargando +mientras está conectado al puerto USB de un PC. Por ejemplo, varios ordenadores +Suunto y Mares no recargan a través de de la conexión USB. Los usuarios deberían +consultar el manual de su ordenador de buceo si no están seguros de si recargará +o descargará sus baterías mientras está conectado al puerto USB.</td> +</tr></table> +</div> +<div class="paragraph"><p>Para importar información desde un ordenador de buceo al PC con <em>Subsurface</em> es +necesario que ambas piezas de equipo estén comunicadas. Esto requiere ajustar el +puerto de comunicaciones (o el punto de montaje) del PC con <em>Subsurface</em> que +conecta con el ordenador de buceo. Para poder ajustar esta comunicación, es +necesario encontrar la información adecuada para indicar a <em>Subsurface</em> donde y +como importar la información. El +<a href="#_apendice_a_informacion_especifica_del_sistema_operativo_para_importar_inmersiones_desde_un_ordenador_de_buceo">Apéndice A</a> +proporciona información técnica para ayudarte a conseguir esto en diferentes +sistemas operativos y el +<a href="#_appendix_b_dive_computer_specific_information_for_importing_dive_information">Apéndice B</a> +contiene información específica de ordenadores de buceo.</p></div> +<div class="paragraph"><p>Ahora es el momento de conectar el ordenador de buceo al PC del usuario, para +lo que hay que seguir estos pasos:</p></div> +<div class="olist arabic"><ol class="arabic"> +<li> +<p> +Conectar el cable de conexión a un puerto USB libre (o activar la conexión + infrarroja o bluetooth como describiremos más adelante en este manual). +</p> +</li> +<li> +<p> +Poner el ordenador de buceo en modo de comunicación con PC. Consulta el + manual de tu ordenador de buceo en concreto. +</p> +</li> +<li> +<p> +En <em>Subsurface</em>, desde el Menú principal, seleccionar Importar → Importar del + ordenador de buceo. Aparecerá el diálogo <strong>A</strong> en la figura a continuación: +</p> +</li> +</ol></div> +<div class="imageblock" style="text-align:center;"> +<div class="content"> +<img src="images/DC_import_f20.jpg" alt="FIGURA: Diálogo de descarga 1" /> +</div> +</div> +<div class="paragraph"><p>Los ordenadores de buceo tienden a mantener un cierto número de inmersiones en +su memoria, incluso cuando estas inmersiones ya han sido importadas a +<em>Subsurface</em>. Por este motivo <em>Subsurface</em> solo importa buceos que no han sido +descargados previamente, si el ordenador de buceo lo permite. Esto hace que el +proceso de descarga sea más rápido en la mayoría de ordenadores de buceo y +ahorra batería en el ordenador (por lo menos en aquellos que no cargan mientras +están conectados vía USB).</p></div> +<div class="ulist"><ul> +<li> +<p> +El diálogo tiene dos listas desplegables, <strong>Vendedor</strong> y <strong>Ordenador de buceo</strong>. + En la lista desplegable <strong>Vendedor</strong> se selecciona la marca del ordenador, p.e. + Suunto, Oceanic, Uwatec, Mares. En el desplegable <strong>Ordenador de buceo</strong>, se + selecciona el modelo del ordenador, p.e. D4 (Suunto), Veo200 (Oceanic) o Puck + (Mares). +</p> +</li> +<li> +<p> +El desplegable <strong>Dispositivo o punto de montaje</strong> contiene el nombre del puerto + USB o Bluetooth que <em>Subsurface</em> necesita conocer para comunicarse con el + ordenador de buceo. Debe seleccionarse el nombre de puerto apropiado. Consultar + el + <a href="#_apendice_a_informacion_especifica_del_sistema_operativo_para_importar_inmersiones_desde_un_ordenador_de_buceo">Apéndice A</a> + y <a href="#_appendix_b_dive_computer_specific_information_for_importing_dive_information">Apéndice B</a> + para detalles técnicos de como encontrar la información apropiada sobre + puertos, para un ordenador en concreto y, en algunos casos, como hacer los + ajustes correctos al Sistema Operativo del ordenador que ejecuta <em>Subsurface</em>. +</p> +</li> +<li> +<p> +Si todas las inmersiones del ordenador de buceo han de descargarse, hay que + seleccionar la casilla Forzar descarga de todas las inmersiones. Normalmente + <em>Subsurface</em> solo descarga las inmersiones posteriores a la fecha/hora de la + última inmersión del panel <strong>Lista de inmersiones</strong>. Si una o más de sus + inmersiones en <em>Subsurface</em> se han borrado accidentalmente o si hay buceos más + antiguos que todavía necesitan descargarse del ordenador de buceo, debe + activarse esta casilla. Algunos ordenadores (p.e. Mares Puck) no facilitan una + lista de contenido antes de la descarga para poder seleccionar solo las + inmersiones nuevas. En consecuencia, para estos ordenadores de buceo, se + descarga la totalidad de los buceos. +</p> +</li> +<li> +<p> +Si se ha seleccionado la casilla <em>Preferir siempre inmersiones descargadas</em> y, + durante la descarga, existen inmersiones con idénticas fechas/horas en el + ordenador de buceo y en el panel <strong>Lista de inmersiones</strong> de <em>Subsurface</em> , se + sobrescribirá la inmersión de <em>Subsurface</em> con los datos del ordenador de buceo. +</p> +</li> +<li> +<p> +<strong>NO</strong> seleccionar las casillas etiquetadas <em>Guardar registro de + libdivecomputer</em> y <em>Guardar volcado de libdivecomputer</em>. Estas opciones se + utilizan como herramientas diagnósticas cuando se experimentan problemas con las + descargas (ver a continuación). +</p> +</li> +<li> +<p> +Ahora pulsar el botón <em>Descargar</em>. + Con la comunicación establecida puede verse como se transfiere la información + del ordenador de buceo. Dependiendo del ordenador de buceo y/o el número de + inmersiones guardadas, esto podría llevar algún tiempo. El usuario debe ser + paciente. El diálogo <em>Descarga</em> muestra una barra de progreso en la parte + inferior de la ventana (en algunos ordenadores de buceo la información del + progreso puede ser imprecisa al no poder determinarse cuantos datos había hasta + haberse descargado). Tras una descarga correcta, aparecerá el diálogo <strong>B</strong> de + la imagen anterior. Las inmersiones descargadas aparecen en una tabla en el + lado derecho del diálogo. Cada inmersión se sitúa en una fila en la que se + muestra la fecha, la duración y la profundidad. Junto a cada buceo hay una + casilla seleccionable. Marca todas las inmersiones que deban trasladarse a la + <em>Lista de Inmersiones</em>. Luego pulsa el botón <em>Aceptar</em> en la parte de abajo + del diálogo. En el caso de la imagen anterior, las últimas seis inmersiones + han sido seleccionadas y se transferirán a la lista. Todas las inmersiones + importadas aparecen en la <strong>Lista de inmersiones</strong> + ordenadas por fecha y hora. Es el momento de desconectar y apagar el ordenador + de buceo para ahorrar batería. +</p> +</li> +<li> +<p> +Si hubiera algún problema de comunicación con el ordenador de buceo, se + mostraría un mensaje de error similar a este: "No puedo abrir /dev/ttyUSB0 Mares + (Puck Pro)". Ver el texto en la figura a continuación. +</p> +</li> +</ul></div> +<div class="sidebarblock"> +<div class="content"> +<div class="paragraph"><p><strong>PROBLEMAS EN LA DESCARGA DE DATOS DESDE UN ORDENADOR DE BUCEO</strong></p></div> +<div class="admonitionblock"> +<table><tr> +<td class="icon"> +<img src="images/icons/important.png" alt="Important" /> +</td> +<td class="content">Comprueba lo siguiente:</td> +</tr></table> +</div> +<div class="ulist"><ul> +<li> +<p> +¿ Está el ordenador de buceo todavía en modo "PC-Communication" o "Upload" ? +</p> +</li> +<li> +<p> +¿ Está completamente cargada la batería del ordenador de buceo ? Si nó debe + cargarse o ser reemplazada. +</p> +</li> +<li> +<p> +¿ Falla el cable ? ¿ Funciona bien el cable usando otro software ? ¿ Ha + funcionado antes o es la primera vez que se usa ? ¿ Están limpios los contactos + entre el cable y el ordenador de buceo ? +</p> +</li> +<li> +<p> +Consultar el + <a href="#_apendice_a_informacion_especifica_del_sistema_operativo_para_importar_inmersiones_desde_un_ordenador_de_buceo">Apéndice A</a> + y asegurarse de que se especificó el punto de montaje correcto. +</p> +</li> +<li> +<p> +En sistemas operativos tipo unix, comprobar que el usuario tiene permisos de + escritura en el puerto USB. Si nó, consultar el + <a href="#_apendice_a_informacion_especifica_del_sistema_operativo_para_importar_inmersiones_desde_un_ordenador_de_buceo">Apéndice A</a>. +</p> +</li> +</ul></div> +<div class="paragraph"><p>Si el PC con <em>Subsurface</em> no reconoce el adaptador USB mostrando un nombre de +dispositivo correcto, existe la posibilidad de que fallen el cable o el +adaptador estén fallando. Un cable que falla es la causa más común de problemas +de comunicación entre el PC y el ordenador de buceo. También existe la +posibilidad de que el PC con <em>Subsurface</em> no pueda interpretar los datos. Habría +que efectuar una descarga con propósito diagnóstico con las sigientes casillas +seleccionadas en el dialogo de descarga:</p></div> +<div class="literalblock"> +<div class="content"> +<pre><code>Guardar registro de libdivecomputer +Guardar volcado de libdivecomputer</code></pre> +</div></div> +<div class="paragraph"><p><strong>Importante</strong>: Estas casillas solo se utilizan si aparecen problemas durante el +proceso de descarga; en condiciones normales no deberían estar seleccionadas. Al +seleccionar cada una de estas opciones, se le solicita al usuario una carpeta en +la que guardar los ficheros de información. Por defecto esta carpeta es la misma +en la que se guarda el archivo del diario de <em>Subsurface</em>.</p></div> +<div class="paragraph"><p><strong>Importante</strong>: Al terminar de descargar con estas casillas seleccionadas no se +muestran buceos en la Lista de inmersiones pero se cran dos ficheros en la +carpeta seleccionada arriba:</p></div> +<div class="literalblock"> +<div class="content"> +<pre><code>_Subsurface_.log +_Subsurface_.bin</code></pre> +</div></div> +<div class="paragraph"><p>Estos ficheros deberían ser remitidos a la lista de correo de <em>Subsurface</em>: +<em>subsurface</em>@hohndel.org_ solicitando que los ficheros sean analizados, +facilitando el fabricante y el modelo de tu ordenador de buceo y alguna +información sobre las inmersiones grabadas en el ordenador de buceo.</p></div> +</div></div> +</div> +<div class="sect3"> +<h4 id="S_Bluetooth">5.2.2. Conectar <em>Subsurface</em> con ordenadores de buceo con Bluetooth</h4> +<div class="paragraph"><p>Bluetooth se está convirtiendo en una forma cada vez más común de comunicación +entre los ordenadores de buceo y <em>Subsurface</em>. Por ejemplo, este mecanismo se +usa en el Shearwater Petrel Mk2 o el OSTC3. <em>Subsurface</em> proporciona un +interfaz Bluetooth muy independiente del sistema operativo utilizado. Ajustar +<em>Susburface</em> para comunicación con Bluetooth requiere cuatro pasos:</p></div> +<div class="ulist"><ul> +<li> +<p> +Asegurarse de que Bluetooth está activado en el ordenador que ejecuta + <em>Subsurface</em>. +</p> +</li> +<li> +<p> +Asegurarse de que <em>Subsurface</em> localiza el adaptador Bluetooth del + ordenador. +</p> +</li> +<li> +<p> +Asegurarse de que el Bluetooth del ordenador de buceo está está en modo + descarga y es visible. +</p> +</li> +<li> +<p> +Asegurarse de que <em>Subsurface</em> está emparejado con el ordenador de buceo. +</p> +</li> +</ul></div> +<div class="paragraph"><p>Abre el diálogo de descarga seleccionando <em>Import → Importar del ordenador +de buceo</em> desde el <strong>Menú Principal</strong>. Si se selecciona la casilla etiquetada +<em>"Elegir modo de descarga Bluetooth"</em> , aparecerá el diálogo que se muestra +a continuación.</p></div> +</div> +<div class="sect3"> +<h4 id="_en_linux_o_macos">5.2.3. En Linux o MacOS</h4> +<div class="imageblock" style="text-align:center;"> +<div class="content"> +<img src="images/DC_import_Bluetooth.jpg" alt="FIGURA: Descarga Bluetooth" /> +</div> +</div> +<div class="paragraph"><p>En plataformas <em>Linux</em> o <em>MacOS</em> el nombre del ordenador con <em>Subsurface</em> +se muestran en el lado derecho. En el lado izquierdo, si el ordenador tiene +conectado más de un dispositivo Bluetooth, se puede seleccionar cual se desea +conectar a <em>Subsurface</em>. +Bajo la dirección se muestra el estado del adaptador (activado/desactivado) y +puede cambiarse pulsando el botón <em>Activar/desactivar</em>.</p></div> +<div class="paragraph"><p>Si no se muestra la dirección Bluetooth, es que <em>Subsurface</em> no localiza el +dispositivo Bluetooth del ordenador en que se ejecuta. Asegúrate de que el +driver Bluetooth está instalado correctamente y comprueba que se puede usar +con otras utilidades Bluetooth como <em>bluetoothctl</em>, bluemoon u otras. Con esto +se completaría los primeros dos pasos indicados anteriormente.</p></div> +<div class="paragraph"><p>Asegúrate de que el ordenador de buceo es visible y se encuentra en modo +descarga (Nota del traductor: es posible que este modo aparezca en inglés como +"Upload" o su traducción literal "Subida"). Consulta el manual del ordenador +de buceo para completar este paso, que sería el tercero de la lista anterior.</p></div> +<div class="paragraph"><p>Selecciona el botón <em>Buscar</em> en la parte de abajo a la izquierda del diálogo +anterior, Tras buscar unos momentos, el ordenador de buceo debería aparecer en +la relación (tal vez entre otros dispositivos Bluetooth) de la lista de la +izquierda del diálogo (ver imagen anterior). Si no es así, pulsa el botón, +<em>Limpiar</em> y efectúa una nueva búsqueda utilizando el botón <em>Buscar</em>. Si +<em>Subsurface</em> "ve" el ordenador de buceo, la línea de la lista contendrá el +nombre del dispositivo, su dirección y su estado de emparejamiento. Si el +dispositivo no está emparejado y tiene un fondo rojo, se puede abrir un menú +contextual seleccionando su línea y pulsando clic-derecho. +Pulsa el botón <em>Emparejar</em> y espera a que se complete la tarea. Si este +ordenador de buceo se está emparejando con <em>Subsurface</em> por primera vez, es +posible que se requiera una clave o número PIN. La clave más utilizada suele +ser 0000, y funciona para el Shearwater Petrel. En caso necesario, consulta el +manual de usuario del ordenador de buceo.</p></div> +<div class="sidebarblock"> +<div class="content"> +<div class="admonitionblock"> +<table><tr> +<td class="icon"> +<img src="images/icons/important.png" alt="Important" /> +</td> +<td class="content">Actualmente <em>Subsurface</em> no soporta emparejamiento con ordenadores de buceo que +requieran un PIN definido. Para poder emparejar los dispositivos en este caso, +habría que utiliza alguna otra utilidad del SO.</td> +</tr></table> +</div> +<div class="paragraph"><p>Una forma de hacerlo es usar <code>bluetoothctl</code>:</p></div> +<div class="literalblock"> +<div class="content"> +<pre><code>$ bluetoothctl +[bluetooth]# agent KeyboardOnly +Agent registered +[bluetooth]# default-agent +Default agent request successful +[bluetooth]# pair 00:80:25:49:6C:E3 +Attempting to pair with 00:80:25:49:6C:E3 +[CHG] Device 00:80:25:49:6C:E3 Connected: yes +Request PIN code +[agent] Enter PIN code: 0000</code></pre> +</div></div> +</div></div> +<div class="paragraph"><p>Después de que los dispositivos se hayan emparejado, se puede pulsar el botón +<em>Guardar</em>. Esto cerrará el diálogo. Ahora pulsa <em>Descargar</em> en el diálogo +<em>Descargar del ordenador de buceo</em> que debería permanecer abierto. Los buceos +descargado se mostrarán en el lado derecho de la ventana de descarga.</p></div> +</div> +<div class="sect3"> +<h4 id="_en_windows">5.2.4. En Windows</h4> +<div class="imageblock" style="text-align:center;"> +<div class="content"> +<img src="images/DC_import_Bluetooth_Windows.png" alt="FIGURE: Descarga Bluetooth en Windows" /> +</div> +</div> +<div class="paragraph"><p>En plataformas Windows no está disponible la <em>sección de detalles de los +dispositivos Bluetooth</em>. Para iniciar correctamente un escaneo pulsando el +botón <em>Buscar</em> , comprueba que el dispositivo <em>Bluetooth</em> del ordenador con +<em>Subsurface</em> está activado seleccionando el ordenador de la lista de +dispositivos Bluetooth disponibles (ver imagen anterior). Si se accede por +primera vez al ordenador de buceo con <em>Subsurface</em>, es posible que se +requiera una clave/PIN. Introduce el recomendado en el manual de ordenador +de buceo. A menudo es correcto un pin 0000.</p></div> +<div class="paragraph"><p>El paso del emparejado se efectúa de forma +automática durante el proceso de descarga. Si los dispositivos no se han +emparejado nunca, el sistema te pedirá permiso y mostrará un mensaje en el +lado derecho de la pantalla: <em>Añadir un dispositivo. Pulsa para configurar tu +dispositivo DC</em>. Siempre debes autorizar el emparejado. Tras haber seleccionado +uno de los dispositivos encontrados, pulsa <em>Guardar</em>. Finalmente, selecciona +el botón <em>Descargar</em> del diálogo de descargas y espera a que se complete el +proceso.</p></div> +<div class="admonitionblock"> +<table><tr> +<td class="icon"> +<img src="images/icons/important.png" alt="Important" /> +</td> +<td class="content">Hay que tener en cuenta que, actualmente, <em>Subsurface</em> solo funciona con +adaptadores Bluetooth locales que usen Microsoft Bluetooth Stack. Si el +dispositivo local usa drivers <em>Widcomm</em>, <em>Stonestreet One Bluetopia Bluetooth</em> o +<em>BlueSolei</em> no funcionará, sin embargo, los receptores de estos fabricantes +que usen el Microsoft Bluetooth Stack sí funcionarán.</td> +</tr></table> +</div> +<div class="paragraph"><p>Un mensaje de aviso en la parte inferior izquierda de la <em>Selección de +dispositivos Bluetooth remotos</em> muestra detalles del estado actual del agente +Bluetooth. +Si se desea seleccionar otro ordenador de buceo utilizando la <em>Selección de +dispositivo Bluetooth remoto</em> pulsa el botón con tres puntos de <em>Elegir modo +de descarga _Bluetooth</em>.</p></div> +<div class="admonitionblock"> +<table><tr> +<td class="icon"> +<img src="images/icons/important.png" alt="Important" /> +</td> +<td class="content"><strong>EN CASO DE PROBLEMAS</strong>: Si el adaptador Bluetooth del ordenador con <em>Subsurface</em> +se cuelga y el proceso de descarga falla repetidamente, <em>desempareja</em> los +dispositivos y repite los pasos indicados anteriormente. Si a pesar de ello +se sigue sin tener éxito, el <a href="#S_HowFindBluetoothDeviceName"><em>Apéndice A</em></a> +contiene información para ajustar manualmente e inspeccionar la conexión +Bluetooth con <em>Subsurface</em>.</td> +</tr></table> +</div> +</div> +<div class="sect3"> +<h4 id="S_DeviceNames">5.2.5. Cambiar el nombre de un ordenador de buceo</h4> +<div class="paragraph"><p>Es posible que sea necesario distinguir entre diferentes ordenadores de buceo +usados para cargar inmersiones en <em>Subsurface</em>. Por ejemplo, si el ordenador del +compañero es de la misma marca y modelo que el del usuario y los diarios de +ambos se cargan en el mismo PC con <em>Subsurface</em>, puede que se quiera llamar a +uno "Suunto D4 de Alice" y al otro "Suunto D4 de Bob". Por otro lado, puede que +un buceador técnico utilice dos o más ordenadores de buceo del mismo modelo, +este caso podría ser prudente llamar a uno "Suunto D4 (1)" y al otro "Suunto D4 +(2)".</p></div> +<div class="paragraph"><p>Esto se hace fácilmente en <em>Subsurface</em>. Desde el <strong>Menú Principal</strong>, se +selecciona <em>Registro → Editar nombres de dispositivos</em>. Se abrirá un diálogo en +el que se indica el modelo actual, su ID y un nombre para el ordenador de buceo +utilizado para cargar inmersiones. Se edita el campo del nombre al que se quiera +asignar al ordenador. Tras guardar el nombre, en el perfil de la inmersión +aparecerá el nombre que se haya asignado a ese dispositivo en particular en +lugar del modelo, permitiendo una identificación de dispositivos más fácil.</p></div> +</div> +<div class="sect3"> +<h4 id="S_EditDiveInfo">5.2.6. Actualizar la información de buceo importada del ordenador.</h4> +<div class="paragraph"><p>Con los buceos descargados en la <strong>Lista de inmersiones</strong>, la información del +ordenador no está completa y es necesario añadir más detalles para tener un +registro más detallado de las inmersiones. Para ello se usan las pestañas +<strong>Notas</strong> y <strong>Equipo</strong> arriba a la izquierda de la ventana de +<em>Subsurface</em>.</p></div> +<div class="sect4"> +<h5 id="S_Notes_dc">Notas</h5> +<div class="paragraph"><p>El usuario debe añadir información a mano para poder tener un registro más +completo. La información a continuación es casi idéntica para inmersiones +creadas manualmente y para inmersiones descargadas del ordenador.</p></div> +<div class="paragraph"><p>En algunos casos, se debe proporcionar la fecha y la hora de la inmersión, por +ejemplo al crear un buceo a mano o cuando un ordenador no facilita la fecha y +la hora de la inmersión (habitualmente la fecha y hora del buceo, la mezcla de gases +y, la temperatura del agua se obtienen del ordenador de buceo). Si se cambia o +edita de alguna manera el contenido de esta +pestaña, el mensaje de la barra azul arriba del panel indicará que se está +editando el buceo. Si se pulsa en la pestaña <strong>Notas</strong>, se +visualizan los siguientes campos (imagen a la izquierda, a continuación:</p></div> +<div class="imageblock" style="text-align:center;"> +<div class="content"> +<img src="images/AddDive3_f22.jpg" alt="FIGURA: La pestaña Notas" /> +</div> +</div> +<div class="paragraph"><p>La imagen derecha anterior muestra una pestaña <strong>Notas</strong> llena de información. +El campo <strong>Hora</strong> refleja la fecha y la hora de la inmersión. Clicando la fecha se +muestra un calendario desde el que seleccionar la fecha correcta. Pulsa ESC para +salir del calendario. La hora y los minutos también pueden editarse clicando en +cada uno de ellos y sobreescribiendo la información mostrada.</p></div> +<div class="paragraph"><p><strong>Temperaturas Aire/Agua</strong>: Las temperaturas de aire y agua durante la inmersión +se muestran en estos campos a la derecha de la Hora de Inicio. Muchos +ordenadores de buceo suministran información sobre la temperatura del agua y +este campo puede que ya contenga información obtenida del mismo. Si no se +proporciona la temperatura del aire, puede utilizarse la primera lectura del +ordenador. En general, suele estar bastante cerca de la temperatura real del +aire ya que el cambio en la lectura del sensor de temperatura es bastante lento +para seguir los cambios en el entorno. Si fuera necesario, no hay que teclear +las unidades de temperatura: <em>Subsurface</em> las suministra automáticamente de +acuerdo con las <em>Preferencias</em> (métricas o imperiales).</p></div> +<div class="paragraph"><p><strong>Ubicación</strong>:</p></div> +<div class="admonitionblock"> +<table><tr> +<td class="icon"> +<img src="images/icons/warning2.png" alt="Warning" /> +</td> +<td class="content">Las localizaciones de buceo se gestionan como una parte <strong>separada</strong> del divelog. +La información de buceo de las pestañas <strong>Notas</strong> y <strong>Equipo</strong> no se puede editar +al mismo tiempo que la información de los puntos de buceo. Guarda toda la otra +información (p.e. divemaster, compañero, equipo, etc) seleccionando <em>Aplicar +cambios</em> en la pestaña <strong>Notas</strong> antes de editar la información del punto de +buceo. Introduce, solo entonces, el nombre del lugar de la inmersión en el +campo de texto etiquetado <em>Ubicación</em> de la pestaña <strong>Notas</strong>.</td> +</tr></table> +</div> +<div class="paragraph"><p>Teclea el nombre del punto de buceo, p.e. "Tihany, Lake Balaton, Hungary". +Si se han efectuado varias inmersiones en el mismo lugar, la información del +primer buceo se reutiliza. +La información existente puede editarse en cualquier momento seleccionando +(en el panel <strong>Lista de Inmersiones</strong>) un buceo efectuado en el lugar deseado y +abriendo la información de la ubicación haciendo clic en el botón con el globo +a la derecha del nombre del lugar (ver la imagen de arriba a la derecha). +Cuando se introduce el nombre de una ubicación, el auto completado de nombres +hace que sea fácil seleccionar un punto de buceo que ya exista en el divelog +(p.e. al teclear el nombre de un punto de buceo, aparece una lista desplegable + mostrando todos los lugares con nombres similares). Si el lugar se ha utilizado +antes, pulsa en el nombre preexistente.</p></div> +<div class="paragraph"><p>Los nombres de la lista desplegable contienen, bien un símbolo de un globo (que +indica que existe en la base de datos de <em>Subsurface</em>), bien un símbolo <strong>+</strong> (que +indicaría un nombre que puede ser añadido a la base de datos). +Así pues, si este punto de buceo no ha sido usado con anterioridad, aparece un +mensaje como el siguiente (imagen <strong>A</strong> a continuación):</p></div> +<div class="imageblock" style="text-align:center;"> +<div class="content"> +<img src="images/Locations1_f22.jpg" alt="FIGURA: Panel de descripción de ubicación" /> +</div> +</div> +<div class="paragraph"><p>Haz doble clic en el icono + en el lado derecho. Aparecerá un panel para +introducir las coordenadas y otra información sobre el lugar que pueda ser +importante (imagen <strong>B</strong>, anterior). Lo más importante son las coordenadas del +punto. Hay tres formas de especificarlas:</p></div> +<div class="olist loweralpha"><ol class="loweralpha"> +<li> +<p> +El usuario puede encontrar las coordenadas en el mapamundi situado abajo a la + derecha en la ventana de <em>Subsurface</em>. El mapa muestra una barra marrón indicando + "Sin datos de ubicación - Mueve el mapa y haz doble clic para fijar la posición + del buceo". Al hacer doble clic en el lugar apropiado, la barra marrón desaparece + y las coordenadas quedan grabadas +</p> +</li> +<li> +<p> +Se pueden obtener las coordenadas desde la app <em>Subsurface</em> Companion si se + dispone de un dispositivo android o iPhone con GPS y se guardaron las + coordenadas del punto de buceo usando ese dispositivo. + <a href="#S_Companion">Pulsa aquí para más información</a> +</p> +</li> +<li> +<p> +Se pueden introducir las coordenadas a mano, si son conocidas, usando uno de + estos cuatro formatos, con la latitud seguida de la longitud: +</p> +<div class="literalblock"> +<div class="content"> +<pre><code>Formato ISO 6709 Annex D, p.e. 30°13'28.9"N 30°49'1.5"E +Grados y minutos decimales, p.e. N30º 13.49760', E30º 49.30788' +Grados minutos y segundos, p.e. N30° 13' 29.8" , E30° 49' 1.5" +Grados decimales, p.e. 30.22496 , 30.821798</code></pre> +</div></div> +</li> +</ol></div> +<div class="paragraph"><p>Las latitudes del hemisferio sur se dan con una <strong>S</strong>, p.e. S30º o con un valor +negativo, p.e. -30.22496. De igual forma, las longitudes al oeste se facilita +con una <strong>W</strong>, p.e. W07°, o con un valor negativo, p.e. -7.34323. Algunos teclados +no tienen el símbolo °. Puede reemplazarse con una <strong>d</strong> como en N30d W20d. +Si se ha proporcionado un nombre y unas coordenadas, guarda la información +seleccionando el botón <em>Aplicar cambios</em> arriba en el panel.</p></div> +<div class="paragraph"><p><strong>Importante</strong>: Las coordenadas GPS de un punto están unidas a un nombre, por +tanto, guardar inmersiones con coordenadas sin una descripción del lugar +causará comportamientos inesperados (<em>Subsurface</em> creerá que todos estos puntos +son el mismo e intentará hacer que toas las coordenadas sean iguales).</p></div> +<div class="paragraph"><p><strong>Búsqueda de nombres de puntos de buceo</strong>: Si se han introducido coordenadas, +se puede efectuar una busca automatizada del nombre basada en ellas. Se hace +cuando <em>Subsurface_utiliza internet para encontrar el nombre del punto de +buceo basado en las coordenadas introducidas. Si se encuentra un nombre, se +introduce automáticamente en la casilla de texto. El campo llamado _Puntos de +buceo en las mismas coordenadas</em>, en la parte baja del panel, contiene nombres +de otros puntos de buceo en posiciones muy cercanas al actual.</p></div> +<div class="paragraph"><p>Introduce cualquier otra información textual sobre el punto de buceo +(Descripción y Notas), entonces selecciona <em>Aplicar cambios</em> para guardar la +información de este punto de buceo. En una etapa posterior esta información +puede editarse pulsando el icono del globo a la derecha del nombre del punto en +la pestaña <strong>Notas</strong>.</p></div> +<div class="paragraph"><p><strong>Modo de buceo</strong>: Esta es una casilla desplegable que permite elegir el tipo de +inmersión que se ha realizado. Las opciones son OC (circuito abierto, del +inglés "open circuit", el ajuste por defecto, valido para la mayoría de buceos +recreativos), Apnea, CCR (rebreather de circuito cerrado, del inglés "closed +circuit rebreather") o pSCR (rebreather pasivo de circuito semi-cerrado).</p></div> +<div class="paragraph"><p><strong>Divemaster</strong>: Introducir el nombre del divemaster o el del guía de inmersión. De +nuevo, este campo ofrece autocompletado basándose en la lista de divemasters del +diario actual.</p></div> +<div class="paragraph"><p><strong>Compañero</strong>: Introducir el nombre(s) del compañero(s) que te acompañaron en la +inmersión, separados por comas. También se ofrece autocompletado basada en la +lista de compañeros del registro.</p></div> +<div class="paragraph"><p><strong>Traje</strong>: Introducir el tipo de traje de buceo que utilizaste para la inmersión. +Como en los casos anteriores está disponible el autocompletado. Los usuarios de +traje seco pueden utilizar este campo para registrar que combinación de traje y +protección térmica utilizaron.</p></div> +<div class="paragraph"><p><strong>Valoración</strong>: Aquí se puede proporcionar una calificación subjetiva de la +inmersión en una escala de 5 puntos, clicando en la estrella correspondiente.</p></div> +<div class="paragraph"><p><strong>Visibilidad</strong>: Igualmente se puede proporcionar una calificación de a la +visibilidad que había durante la inmersión en una escala de 5 puntos, clicando +la estrella adecuada.</p></div> +<div class="paragraph"><p><strong>Etiquetas</strong>: Se pueden introducir etiquetas (separándolas con comas) que +describan el tipo de inmersión que se efectuó. Algunos ejemplos de etiquetas +habituales son: barco, a la deriva, entrenamiento, cueva, etc. <em>Subsurface</em> +tiene muchas etiquetas predefinidas. De nuevo se ofrece autocompletado, por +ejemplo, si el usuario teclea <code>p</code>, se muestran las etiquetas <strong>pecio</strong>, <strong>piscina</strong> +y <strong>profunda</strong> para que elija entre ellas.</p></div> +<div class="paragraph"><p><strong>Notas</strong>: Teclea aquí cualquier información adicional que desees conservar.</p></div> +<div class="paragraph"><p>Los botones <em>Aplicar cambios</em> y <em>Descartar cambios</em> se utilizan para guardar +toda la información de los campos del panel de <strong>Información</strong> y del panel de +<strong>Perfil</strong>, por lo que no hay necesidad de usarlos hasta que se ha añadido +<strong>TODA</strong> la información. La imagen <a href="#S_Notes_dc">al inicio de esta sección</a> +muestra un ejemplo de la pestaña <strong>Notas</strong> rellenadas.</p></div> +</div> +</div> +<div class="sect3"> +<h4 id="_equipo">5.2.7. Equipo</h4> +<div class="paragraph"><p>La pestaña Equipo permite al usuario introducir información acerca del tipo de +botella y gas utilizado, así como el lastre utilizado en una inmersión. El +mensaje en azul arriba del panel</p></div> +<div class="imageblock" style="text-align:center;"> +<div class="content"> +<img src="images/BlueEditBar_f22.jpg" alt="FIGURA: Barra azul de edición" /> +</div> +</div> +<div class="paragraph"><p>indica que la inmersión se está editando. Esta parte de <em>Subsurface</em> es +altamente interactiva y la información de botellas y gases que se introduzca +determinará el comportamiento del perfil de la inmersión (panel de arriba a la +derecha).</p></div> +<div class="paragraph" id="cylinder_definitions"><p><strong>Botellas</strong>: La información de las botellas se introduce con un dialogo como +este:</p></div> +<div class="imageblock" style="text-align:center;"> +<div class="content"> +<img src="images/DC_gas-dialogue1_f20.jpg" alt="FIGURA: Diálogo de Botellas inicial" /> +</div> +</div> +<div class="paragraph"><p>En las inmersiones manuales, esta información ha de ser introducida a mano. En +el caso de los ordenadores, a menudo, <em>Subsurface</em> obtiene el gas usado del +propio ordenador de buceo insertando automáticamente la composición (% oxigeno) +en la tabla. El botón + arriba a la derecha permite al usuario añadir más +botellas para esta inmersión. El icono oscuro de papelera le permitirá borrar +la información de una botella. Nótese que no se puede borrar una botella si +se usa durante el buceo. Una botella puede estar usándose implícitamente, +incluso sin un evento de cambio de gas.</p></div> +<div class="paragraph"><p>Se empieza por seleccionar un tipo de botella. Para ello hay que hacer clic en +la casilla <strong>Tipo de botella</strong>. Esto hará aparecer un botón que puede usarse para +mostrar una lista desplegable de botellas.</p></div> +<div class="imageblock" style="text-align:center;"> +<div class="content"> +<img src="images/DC_gas-dialogue2_f20.jpg" alt="FIGURA: Botón del desplegable de la lista de botellas" /> +</div> +</div> +<div class="paragraph"><p>La lista desplegable puede usarse para seleccionar el tipo de botella que +utilizó en esta inmersión, o el usuario puede empezar a teclear en la casilla, +lo que mostrará las opciones disponibles para las letras introducidas. El +<strong>Tamaño</strong> así como su <em>Presión de trabajo</em> se mostrarán automáticamente en el +dialogo.</p></div> +<div class="paragraph"><p>A continuación es necesario indicar la presión inicial y final del gas usado +durante el buceo. Las unidades de presión (métricas/imperiales) corresponden a +las fijadas en la elección de <em>preferencias</em>.</p></div> +<div class="paragraph"><p>Finalmente, hay que introducir la mezcla de gas que se usó. Si se utilizó aire, +se puede poner 21% o dejarlo en blanco. Si se usó nitrox o trimix, hay que +especificar sus porcentaje de oxigeno y de helio. Se deja en blanco el campo que +no corresponda utilizar. Tras teclear la información para la botella, hay que +pulsar <em>ENTER</em> en el teclado o hacer clic fuera de la casilla que contiene el +cursor. Puede añadirse información para cualquier botella adicional usando el +botón + de arriba a la derecha. Aquí hay un ejemplo de descripción completa para +una inmersión en la que se han utilizado dos botellas (aire y EAN50):</p></div> +<div class="imageblock" style="text-align:center;"> +<div class="content"> +<img src="images/CylinderDataEntry3_f20.jpg" alt="FIGURA: Tabla con la informaación de botellas completada" /> +</div> +</div> +<div class="paragraph"><p><strong>Lastre</strong>: Se puede introducir información sobre el sistema de lastre utilizado +en una inmersión, usando un dialogo muy similar al de la información de las +botellas. Si se pulsa el botón + de arriba a la derecha en el dialogo de lastre, +la tabla aparecerá como sigue</p></div> +<div class="imageblock" style="text-align:center;"> +<div class="content"> +<img src="images/WeightsDataEntry1_f20.jpg" alt="FIGURA: El diálogo Lastre" /> +</div> +</div> +<div class="paragraph"><p>Si se hace clic en el campo <em>Tipo</em>, se accede a una lista desplegable con la +flecha:</p></div> +<div class="imageblock" style="text-align:center;"> +<div class="content"> +<img src="images/WeightsDataEntry2_f20.jpg" alt="FIGURA: Desplegable con la lista de tipos de lastre" /> +</div> +</div> +<div class="paragraph"><p>La lista desplegable puede usarse para seleccionar el tipo de sistema de lastre +utilizado durante la inmersión, o simplemente teclear en la casilla, con lo que +se mostrarán las opciones disponibles para los caracteres introducidos. En el +campo <strong>Peso</strong> se teclea el peso usado durante el buceo. Tras teclear la +información se pulsa <em>ENTER</em> en el teclado o se hace clic fuera de la casilla +que contiene el cursor. +Se puede poner información para más de un sistema de lastre añadiendo otro con +el botón + de arriba a la derecha. Se pueden borrar lastres usando el icono de +papelera de la izquierda. A continuación, un ejemplo de información para una +inmersión con dos tipos de lastre: integrado y cinturón:</p></div> +<div class="imageblock" style="text-align:center;"> +<div class="content"> +<img src="images/WeightsDataEntry3_f20.jpg" alt="FIGURA: Tabla con información de lastre completada" /> +</div> +</div> +</div> +<div class="sect3"> +<h4 id="_editar_simultaneamente_varias_inmersiones_seleccionadas">5.2.8. Editar simultáneamente varias inmersiones seleccionadas</h4> +<div class="paragraph"><p><em>METODO 1</em>: Tras descargar inmersiones de un ordenador de buceo, los perfiles +de los buceos descargados se mostrarán en el panel "Perfil de la inmersión", +así como algunas otras informaciones en las pestañas "Notas" y +"Equipo". Sin embargo, otros campos permanecerán vacíos.</p></div> +<div class="paragraph"><p>Puede resultar útil editar simultáneamente algunos de los campos de las "Notas +de la Inmersión" o del "Equipo". Por ejemplo, es posible que un buceador +efectuara varias inmersiones en un solo día utilizando el mismo equipo, o en el +mismo punto de buceo o con el mismo guía o compañero. En lugar de completar la +información de las inmersiones una por una, se pueden seleccionar todos los +buceos deseados en la "Lista de Inmersiones" e insertar la información común en +las "Notas" y "Equipo".</p></div> +<div class="paragraph"><p>La edición simultánea solo funciona con campos que no contienen aún ninguna +información. Esto significa que si, para una inmersión en concreto, uno de los +campos ya ha sido rellenado, no será modificado por la edición simultánea en +ese buceo en concreto. Técnicamente, la regla para editar varias inmersiones a +la vez es: "si el campo que estamos editando contiene <em>exactamente la misma +información</em> en todas las inmersiones que hemos seleccionado, la nueva +información introducida se sustituye en todas las inmersiones seleccionadas, de +lo contrario solo se cambia la inmersión que estemos editando aunque haya +varias seleccionadas.</p></div> +<div class="paragraph"><p>Esto acelera notablemente el rellenado del divelog después de haber efectuado +varios buceos similares.</p></div> +<div class="paragraph" id="S_CopyComponents"><p><em>METODO 2</em>: Hay una forma diferente de hacer lo mismo. Seleccionamos un buceo +que contenga toda la información apropiada en las pestañas <strong>Notas</strong> y <strong>Equipo</strong>. +Entonces, desde el menú principal, seleccionamos +<em>Registro → Copiar componentes</em>. Aparecerá una ventana con casillas +seleccionables para la mayoría de campos de las pestañas <strong>Notas</strong> +y <strong>Equipo</strong>. Selecciona los campos a copiar desde la inmersión seleccionada, +luego pulsa <em>Aceptar</em>. Ahora selecciona en la <strong>Lista de Inmersiones</strong> los buceos +a los que pegar esta información. Desde el menú principal, selecciona <em>Registro + → Pegar componentes</em>. Tras esto, todas las inmersiones seleccionadas + contendrán los datos seleccionados previamente de la anterior inmersión.</p></div> +</div> +<div class="sect3"> +<h4 id="_anadir_marcas_a_una_inmersion">5.2.9. Añadir Marcas a una inmersión</h4> +<div class="paragraph"><p>Muchos buceadores desean anotar en sus inmersiones textos que indiquen sucesos +concretos durante el buceo, p.e. "Avistamos delfines" o "Lanzada boya deco". +Esto se hace fácilmente:</p></div> +<div class="ulist"><ul> +<li> +<p> +Clic derecho sobre el punto adecuado del perfil de inmersión, se desplegará + el menú contextual del perfil. Se selecciona <em>Añadir marca</em>. Una bandera roja + aparecerá sobre el perfil en el punto inicialmente seleccionado (ver <strong>A</strong> a + continuación). +</p> +</li> +<li> +<p> +Clic derecho sobre la bandera roja. Se desplegará el menú contextual (ver + <strong>B</strong> a continuación). Se selecciona <em>Editar nombre</em>. +</p> +</li> +<li> +<p> +Se mostrará una casilla de texto. Se teclea en ella el texto oportuno para la + marca (ver <strong>C</strong> a continuación). Se selecciona <em>Aceptar</em>, con lo que se guarda el + texto asociado a la marca. +</p> +</li> +<li> +<p> +Cuando el ratón pase sobre el marcador rojo, el texto guardado se mostrará en + la parte de debajo del cajetín de información (ver <strong>D</strong> a continuación). +</p> +</li> +</ul></div> +<div class="imageblock" style="text-align:center;"> +<div class="content"> +<img src="images/Bookmarks.jpg" alt="FIGURA: Diálogo de marcadores" /> +</div> +</div> +</div> +<div class="sect3"> +<h4 id="_guardar_la_informacion_de_buceo_actualizada">5.2.10. Guardar la información de buceo actualizada</h4> +<div class="paragraph"><p>La información introducida en las pestañas Notas y Equipo puede +guardarse utilizando los dos botones de arriba a la derecha de la pestaña +<strong>Notas</strong>. Si se pulsa <em>Aplicar cambios</em> los datos del buceo se guardan en la +imagen en memoria de la inmersión. Si se pulsa <em>Descartar cambios</em> los datos +de buceo recién introducidos se borran de la memoria, aunque el perfil y los +datos descargados del ordenador quedarán retenidos. Cuando el usuario salga de +<em>Subsurface</em> hay una pregunta final para confirmar si los nuevos datos de deben +guardar en caso de no haberlo hecho antes.</p></div> +</div> +</div> +<div class="sect2"> +<h3 id="_importar_informacion_de_inmersiones_de_otras_fuentes_u_otros_formatos_de_datos">5.3. Importar información de inmersiones de otras fuentes u otros formatos de datos</h3> +<div class="paragraph" id="S_ImportingAlienDiveLogs"><p>Si el usuario bucea desde hace algún tiempo, es posible que bastantes +inmersiones hayan sido registradas usando otro software. No es necesario teclear +de nuevo esta información ya que, probablemente, estos diarios puedan importarse +a <em>Subsurface</em>. <em>Subsurface</em> puede importar un amplio abanico de diarios de +otros softwares de registro. Mientras que algún software se soporta nativamente, +en otros casos el usuario debe exportar el(los) diario(s) a un +formato intermedio para que pueda ser importado a <em>Subsurface</em>. +Actualmente, <em>Subsurface</em> soporta importar archivos <em>CSV</em> de diferentes origenes. +Los archivos de APD LogViewer, XP5, Sensus y Seabear están preconfigurados, +pero dado que es flexible, los usuarios pueden configurar sus propias +importaciones. Diarios creados manualmente (p.e. en hojas de cálculo) también +pueden importarse configurando manualmente el CSV. <em>Subsurface</em> también puede +importar archivos UDDF y UDCF, usados por algún software y algunos ordenadores +de buceo como el H&W DR5 o el XDeep Black BT. Finalmente, para algunos programas +de registro como el Mares Dive Organiser, se sugiere exportar los diarios primero +a un servicio web como <em>divelogs.de</em> e importarlos desde allí a <em>Subsurface</em>, ya +que <em>divelogs.de</em> soporta algunos pocos formatos que <em>Subsurface</em> no puede leer +en la actualidad.</p></div> +<div class="paragraph"><p>Si el formato del otro software está soportado nativamente en <em>Subsurface, +debería ser suficiente con seleccionar bien _Importar→Importar archivos de +registro</em>, bien <em>Archivo→Abrir registro</em> . <em>Subsurface</em> soporta directamente +los formatos de datos de muchos ordenadores de buceo, incluyendo Suunto y +Shearwater.</p></div> +<div class="paragraph"><p>Al importar inmersiones, <em>Subsurface</em> intenta detectar múltiples registros del +mismo buceo y mezcla la información lo mejor que puede. Si no existen problemas +con las zonas horarias (u otras razones que hagan que la hora de comienzo de las +inmersiones sean significativamente diferentes) <em>Subsurface</em> no creará entradas +duplicadas. A continuación sigue más información relativa a importar datos a +<em>Subsurface</em></p></div> +<div class="sect3"> +<h4 id="Unified_import">5.3.1. Utilizar el diálogo de importación universal</h4> +<div class="paragraph"><p>El importar buceos desde otros programas se hace a través de una interfaz +universal que se activa seleccionando Importar desde el menú principal y +haciendo clic en <em>Importar archivos de registro</em>. Con ello se mostrará el +dialogo <strong>A</strong> a continuación.</p></div> +<div class="imageblock" style="text-align:center;"> +<div class="content"> +<img src="images/Import1_f20.jpg" alt="FIGURA: Importar: paso 1" /> +</div> +</div> +<div class="paragraph"><p>Abajo a la derecha hay un desplegable con una etiqueta por defecto Archivos de +registro que da acceso a los diferentes tipos de archivo disponibles para +importar directamente, como en el dialogo <strong>B</strong> anterior. Actualmente son:</p></div> +<div class="ulist"><ul> +<li> +<p> +Diarios en formato XML (DivingLog 5.0, MacDive y varios otros) +</p> +</li> +<li> +<p> +Archivos de Cochran +</p> +</li> +<li> +<p> +Diarios en formato UDDF (p.e. Kenozoooid) +</p> +</li> +<li> +<p> +Diarios en formato UDCF +</p> +</li> +<li> +<p> +Diarios de CCR Poseidon MKVI +</p> +</li> +<li> +<p> +Diarios de CCR APD Inspiration/Evolution +</p> +</li> +<li> +<p> +Diarios de LiquidVision +</p> +</li> +<li> +<p> +Diarios de divelogs.de +</p> +</li> +<li> +<p> +Diarios de DataTrak +</p> +</li> +<li> +<p> +Diarios de OSTCTools +</p> +</li> +<li> +<p> +JDiveLog +</p> +</li> +<li> +<p> +Suunto Dive Manager (DM3 y DM4) +</p> +</li> +<li> +<p> +Diarios en formato <em>CSV</em> (basados en texto o en hojas de cálculo), incluidos +diarios de CCR APD. +</p> +</li> +</ul></div> +<div class="paragraph"><p>Seleccionar el archivo correspondiente en la lista del diálogo abre el archivo +importado directamente en la <strong>Lista de Inmersiones</strong> de <em>Subsurface</em>. También +están soportados algunos otros formatos, no accesibles desde el diálogo +Importar, como se explica a continuación.</p></div> +</div> +<div class="sect3"> +<h4 id="_importar_desde_ostctools">5.3.2. Importar desde OSTCTools</h4> +<div class="paragraph"><p><em>OSTCTools</em> es un conjunto de herramientas basadas en Windows de descarga y +gestión para la familia de ordenadores OSTC. <em>OSTCTools</em> puede descargar datos +de las inmersiones y guardarlos en archivos binarios con extensión <em>.dive</em> . +Subsurface puede importar directamente estos archivos utilizando el diálogo de +importación universal. Desde la lista desplegable abajo a la derecha, se +selecciona la opción correspondiente, lo cual hará visibles los diarios en la +lista del panel. Se seleccionan una o varias inmersiones, y se hace click en el +botón <em>Abrir</em>. Las inmersiones importadas desde OSTCTools se mostrarán en el +panel <strong>Lista de inmersiones</strong>.</p></div> +<div class="paragraph"><p>Actualmente, todos los ordenadores de H&W que soporte OSTCTools pueden importarse +a <em>Subsurface</em>, esto incluye OSTC, OSTC Mk2, OSTC 2N/2C, OSTC3, OSTC Sport, y, +probablemente aunque sin probar, Frog, OSTC2 y OSTC CR.</p></div> +<div class="paragraph"><p>Por favor, recuerda que OSTCTools <strong>no</strong> es un auténtico software de registro de +diarios de buceo, sino un útil conjunto de herramientas de gestión y análisis +para dispositivos OSTC. Así pues, importar inmersiones a <em>Subsurface</em> sólo +nos proporcionará datos relativos al ordenador de buceo; el usuario tendrá +que completar manualmente el resto de datos que le puedan resultar importantes +(compañeros, equipo, notas, etc).</p></div> +</div> +<div class="sect3"> +<h4 id="_importar_desde_mares_dive_organiser_v2_1">5.3.3. Importar desde Mares Dive Organiser V2.1</h4> +<div class="paragraph"><p>Dado que Mares utiliza software propiedad de Microsoft no compatible con +aplicaciones multiplataforma, estos diarios no pueden importarse directamente a +<em>Subsurface</em>. Los diarios de Mares necesitan ser importados usando un proceso en +tres pasos, utilizando <em>www.divelogs.de</em> como mecanismo para extraer la +información.</p></div> +<div class="olist arabic"><ol class="arabic"> +<li> +<p> +Los datos del Mares Dive Organiser necesitan exportarse al escritorio del + usuario utilizando una extensión de archivo <em>.sdf</em>. Dirigirse a + <a href="#Mares_Export">Apendice C</a> para más información. +</p> +</li> +<li> +<p> +Los datos deben ser importados entonces desde <em>www.divelogs.de</em>. Se necesita + crear una cuenta de usuario en <em>www.divelogs.de</em>, entrar a la página, entonces + seleccionar <em>Import Logbook → Dive Organiser</em> en el menú de la izquierda. Hay + que seguir cuidadosamente las instrucciones para transferir la información (en + formato <em>.sdf</em>) desde la base de datos de Dive Organiser a <em>www.divelogs.de</em>. +</p> +</li> +<li> +<p> +Finalmente importar las inmersiones desde <em>divelogs.de</em> a <em>Subsurface</em>, + utilizando las instrucciones a continuación. +</p> +</li> +</ol></div> +</div> +<div class="sect3"> +<h4 id="S_ImportingDivelogsDe">5.3.4. Importar inmersiones desde <strong>divelogs.de</strong></h4> +<div class="paragraph"><p>Importar información de inmersiones desde <em>divelogs.de</em> es simple, se usa un +único diálogo. Se selecciona <em>Importar → Importar desde Divelogs.de</em> en el menú +principal. Esto despliega un diálogo (ver figura <strong>A</strong> abajo a la izquierda). Es +necesario introducir un usuario y password para <em>divelogs.de</em> en los campos que +se indiquen y luego pulsar el botón <em>Descargar</em>. La descarga desde divelogs.de +comienza inmediatamente y se refleja en una barra de progreso de la ventana del +diálogo. Al finalizar la descarga se indica el estado de "exito" (ver figura +<strong>B</strong> abajo a la derecha). Se selecciona el botón <em>Aplicar</em>, tras lo cual las +inmersiones importadas aparecerán en el panel <strong>Lista de Inmersiones</strong>.</p></div> +<div class="imageblock" style="text-align:center;"> +<div class="content"> +<img src="images/Divelogs1.jpg" alt="FIGURE:Descargar desde Divelogs.de" /> +</div> +</div> +</div> +<div class="sect3"> +<h4 id="S_ImportingCSVData">5.3.5. Importar datos en formato CSV</h4> +<div class="paragraph"><p>Se puede utilizar un archivo .csv (valores separados por comas) para importar +información de buceo así como perfiles de inmersión (como en el caso de los +CCRs APD Inspiration o el Evolution) o como metadatos de buceo (en caso de que +el usuario guarde los datos en una hoja de cálculo). El formato <em>CSV</em> es un +formato universal simplificado que permite un intercambio facil de información +entre difeerentes ordenadores o paquetes de software. Para una introducción a +archivos en formato <em>CSV</em> ver <a href="#S_CSV_Intro">Introducción de un buceador a los archivos CSV</a>. +Los diarios de <em>Subsurface</em> también pueden exportarse a formato <em>CSV</em> para +otro software que lea este formato. Ver el <a href="#S_Appendix_D">APPENDIX D: Exportar una hoja de cálculo a formato CSV</a> +para información que puede resultar útil para importar datos basados en hojas +de cálculo a <em>Subsurface</em>.</p></div> +</div> +<div class="sect3"> +<h4 id="S_ImportingCSVDives">5.3.6. Importar inmersiones en formato <em>CSV</em> desde ordenadores u otro software</h4> +<div class="paragraph"><p>Se puede visualizar un archivo <em>CSV</em> usando un editor de textos ordinario. Se +organiza, normalmente, en una sola línea que proporciona las cabeceras (o +<em>nombres de campo</em> o <em>encabezamientos</em>) de las columnas de datos, seguidos por +los datos a un registro (inmersión en nuestro caso) por línea.</p></div> +<div class="paragraph"><p>Hay dos tipos de archivo <em>CSV</em> que pueden importarse en <em>Subsurface</em>:</p></div> +<div class="olist arabic"><ol class="arabic"> +<li> +<p> +<em>Detalles de inmersión CSV</em>: Este formato contiene información similar a la + de un típico diario escrito, p.e. fecha, hora, profundidad, duración, nombre + de los compañeros y divemaster, y tal vez alguna información sobre botellas, + así como algunos comentarios sobre la inmersión. Toda la información sobre + un buceo va en una sola línea siguiendo el orden del encabezamiento de las + columnas. +</p> +</li> +<li> +<p> +<em>Perfil de inmersión CSV</em>: Este formato incluye mucha más información + sobre una sola inmersión. Por ejemplo, puede haber información a intervalos + de 30 segundos indicando la profundidad, la temperatura del agua a esa + profundidad y presión de las botellas en ese instante. Cada línea contiene + la información de un solo instante durante la inmersión, 30 segundos tras el + anterior. Se requieren muchas líneas para completar la información del + perfil de profundidad de un buceo. Es un formato utilizado comúnmente para + exportar por los equipos de buceo en circuito cerrado (CCR) y muchos + paquetes de software que manejan ordenadores de buceo y/o diarios. +</p> +</li> +</ol></div> +<div class="paragraph"><p>Antes de poder importar los datos a <em>Subsurface</em> se necesitan saber algunas +cosas sobre los mismos:</p></div> +<div class="olist loweralpha"><ol class="loweralpha"> +<li> +<p> +¿ Que carácter separa las distintas columnas en una línea de datos ? Este + separador de campos debería ser una coma (,) un punto y coma (;) o un + tabulador. Puede averiguarse abriendo el archivo con un editor de textos. + Si se trata de una coma, el carácter será claramente visible entre valores. + Si no hay comas a la vista, seguramente esté delimitado por tabuladores. +</p> +</li> +<li> +<p> +¿ Que columnas de datos necesitamos importar a <em>Subsurface</em> ? ¿ Es un archivo + de <em>Detalles de inmersión CSV</em> o de <em>Perfil de inmersión CSV</em> ? Ábrelo con un + editor de textos y fíjate en los títulos de las columnas a importar y sus + posiciones. +</p> +</li> +<li> +<p> +¿ Está la información numérica (la profundidad por ejemplo) en unidades + métricas o imperiales ? +</p> +</li> +</ol></div> +<div class="paragraph"><p>Armado con esta información, importar en <em>Subsurface</em> es muy fácil. Selecciona +<em>Importar→Importar CSV</em> en el menú principal. Aparecerá el siguiente dialogo:</p></div> +<div class="imageblock" style="text-align:center;"> +<div class="content"> +<img src="images/csv_import1_f20.jpg" alt="FIGURE: Diálogo 1, Descarga CSV" /> +</div> +</div> +<div class="paragraph"><p>Fíjate que, arriba a la izquierda, hay una lista desplegable que contiene ajustes +preconfigurados para algunos de los ordenadores de buceo y paquetes de software +más comunes que podemos encontrar los buceadores. Si el archivo <em>CSV</em> que vamos +a importar se originó en alguno de estos paquetes o dispositivos, selecciónalo. +En otro caso, utiliza la opción <em>Importación manual</em>. El panel de configuración +también tiene listas desplegables para especificar el separador de campos +adecuado (tabulado, coma o punto y coma), el formato de fecha usado en el CSV, +las unidades de tiempo (segundos, minutos o minutos:segundos), así como el +sistema de unidades (métrico o imperial) utilizado. Seleccionar las opciones +correctas es crítico para importar correctamente los datos.</p></div> +<div class="paragraph"><p>La última tarea es asegurarse que todas las columnas de datos tienen las +cabeceras correctas. La línea superior de la parte blanca de la tabla contiene +las cabeceras de columnas encontradas en el archivo <em>CSV. La fila de celdas +azules inmediatamente sobre la anterior contiene los nombres que _Subsurface</em> +ha entendido. La zona blanca inmediatamente debajo de las listas desplegables +contiene los nombres de campos que <em>Subsurface</em> reconoce. Estos nombres están +en globos azules que se pueden arrastrar y soltar en las celdas azules a las +que correspondan en la parte superior de la tabla. Esto se muestra en la +imagen a continuación.</p></div> +<div class="imageblock" style="text-align:center;"> +<div class="content"> +<img src="images/csv_import2_f20.jpg" alt="FIGURA: Diálogo 2, Descarga CSV" /> +</div> +</div> +<div class="paragraph"><p>Continua haciendo hasta que todas los encabezamientos de columnas en la fila +azul de celdas correspondan a las cabeceras listadas en la parte alta del +diálogo. Habiendo completado esta tarea, selecciona el botón <em>OK</em> abajo a la +derecha del diálogo. Los datos del archivo <em>CSV</em> se importarán y se mostrarán +en el panel <strong>Lista de inmersiones</strong>.</p></div> +<div class="sidebarblock" id="S_CSV_Intro"> +<div class="content"> +<div class="paragraph"><p><strong>Introducción de un buceador a los archivos <em>CSV</em></strong></p></div> +<div class="admonitionblock"> +<table><tr> +<td class="icon"> +<img src="images/icons/important.png" alt="Important" /> +</td> +<td class="content"><em>CSV</em> es una abreviatura para un formato de archivo de datos: <em>Comma-Separated +Variables</em> en inglés. Es un formato de archivo que permite visualizar o editar +la información usando un editor de textos como el Bloc de Notas (Windows), +Gedit (linux) o TextWrangler (OS/X). Las dos principales ventajas del formato +CSV son que los datos son fácilmente editables como texto sin usar ningún +software propietario y asegurando que toda la información es legible, no siendo +ofuscada por ningún atributo de los que el software propietario inserta en los +archivos. +A causa de su simplicidad, el formato <em>CSV</em> se utiliza como formato de intercambio +entre muchos paquetes de software, por ejemplo entre hojas de cálculo, +estadísticas, gráficos, bases de datos y software de buceo. En <em>Subsurface</em>, los +archivos <em>CSV</em> también se pueden usar para importar información de otras fuentes +tales como diarios basados en hojas de cálculo o, incluso, de algunos ordenadores.</td> +</tr></table> +</div> +<div class="paragraph"><p>El atributo más importante de un archivo <em>CSV</em> es el <em>separador de campos</em>, esto +es, el carácter utilizado para separar campos dentro de una línea. El separador +de campos es, habitualmente, una coma, un punto y coma, un espacio o un +tabulador. Al exportar datos desde una hoja de cálculo, se necesita especificar +el carácter separador para poder crear el archivo CSV. Los archivos <em>CSV</em> están, +normalmente, organizados en una sola línea que proporciona las cabeceras (o +<em>nombres de campos</em>) de las columnas de datos, seguido por los datos, a un +registro por línea. Nótese que cada nombre de campo puede estar formado por más +de una palabra separadas por espacios; por ejemplo <em>Punto de buceo</em>. A +continuación, un ejemplo de información de cuatro inmersiones utilizando la coma +como separador de campos:</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>En este formato los datos no son legibles con facilidad para los humanos. A +continuación los mismos datos usando el tabulador como separador:</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>Es obvio por qué mucha gente prefiere el formato con tabulador al separado por +comas. La desventaja es que los tabuladores no se pueden ver. Por ejemplo el +espacio entre <em>Dive</em> y <em>date</em> en la primera línea puede ser un espacio o un +tabulador (en este caso un espacio). Si los nombres de campo de la primera línea +son largos, no se puede mantener la alineación con los otros campos de datos. +A continuación un ejemplo muy simplificado y recortado de un diario <em>CSV</em> del +ordenador de buceo de un rebreather CCR APD:</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>Cuando un archivo <em>CSV</em> se selecciona para importar, <em>Subsurface</em> muestra las +cabeceras de las columnas y unas pocas lineas de datos del archivo, facilitando +mucho, de esta forma, trabajar con archivos <em>CSV</em>. +Conocer algunas cosas básicas sobre el contenido del archivo <em>CSV</em> permite una +importación mejor de las inmersiones a <em>Subsurface</em>.</p></div> +</div></div> +<div class="paragraph"><p>+[IMPORTANT] +La importación <em>CSV</em> tiene un par de advertencias. Se deberían evitar algunos +caracteres especiales como el signo &, menor que (<), mayor que (>) y comillas +(") como parte de los número o del texto de una casilla. El archivo debería +usar el conjunto de caracteres UTF-8, si se usan caracteres no ASCII. También +podría causar problemas el tamaño del archivo <em>CSV</em>. Importar 100 buceos de una +sola vez (<em>Detalles de inmersión CSV</em>) funciona, pero archivos mayores podrían +exceder los límites del analizador utilizado. Si se encontraran problemas al +importar <em>CSV</em> sería conveniente probar con un archivo más pequeño solo para +asegurarse de que el resto funciona.</p></div> +</div> +</div> +<div class="sect2"> +<h3 id="S_Companion">5.4. Importar coordenadas GPS con la app <em>Subsurface</em> Companion para teléfonos móviles</h3> +<div class="paragraph"><p>Utilizando la app <em>Subsurface</em> Companion en un dispositivo Android o <a href="#S_iphone"><em>iPhone</em></a> +con GPS, se pueden pasar automáticamente las coordenadas de los +puntos de buceo al registro de <em>Subsurface</em>. La app Companion guarda las +ubicaciones de buceo en un servidor dedicado basado en internet. <em>Subsurface</em> +puede recoger las coordenadas desde este servidor.</p></div> +<div class="paragraph"><p>Para hacer esto:</p></div> +<div class="sect3"> +<h4 id="_crear_una_cuenta_para_la_app_companion">5.4.1. Crear una cuenta para la app Companion</h4> +<div class="ulist"><ul> +<li> +<p> +Registrarse en la <a href="http://api.hohndel.org/login/">página web de <em>Subsurface</em> + companion</a>. Se recibirá un correo de confirmación con instrucciones y un + <strong>DIVERID</strong> personal, un largo número que te dará acceso a las capacidades de la + app Companion. +</p> +</li> +<li> +<p> +Descargar la app desde + <a href="https://play.google.com/store/apps/details?id=org.subsurface">Google Play Store</a> + o desde + <a href="http://f-droid.org/repository/browse/?fdfilter=subsurface&fdid=org.subsurface">F-Droid</a>. +</p> +</li> +</ul></div> +</div> +<div class="sect3"> +<h4 id="_utilizar_em_subsurface_em_companion_en_un_smartphone_android">5.4.2. Utilizar <em>Subsurface</em> companion en un smartphone Android</h4> +<div class="paragraph"><p>La primera vez que se utiliza, la app tiene tres opciones:</p></div> +<div class="ulist"><ul> +<li> +<p> +<em>Create a new account</em>. Equivalente a registrase en la página de <em>Subsurface</em> + companion utilizando un navegador de internet. Se puede solicitar un <strong>DIVERID</strong> + con esta opción que se recibirá vía correo electrónico y se confirmará a través + de la <a href="http://api.hohndel.org/login/">_página web de Subsurface companion</a> para + activar la cuenta. +</p> +</li> +<li> +<p> +<em>Retrieve an account</em>. Si el usuario olvidó su <strong>DIVERID</strong> recibirá un correo + para recuperar el número. +</p> +</li> +<li> +<p> +<em>Use an existing account</em>. Se pide el <strong>DIVERID</strong>. La app conserva el <strong>DIVERID</strong> + y no lo vuelve a pedir, a menos que se utilice la opción <em>Disconnect</em> en el menú + (ver a continuación). +</p> +</li> +</ul></div> +<div class="admonitionblock"> +<table><tr> +<td class="icon"> +<img src="images/icons/important.png" alt="Important" /> +</td> +<td class="content">En <em>Subsurface</em> el DIVERID también debe marcarse en el panel Preferencias, al +que se llega seleccionando Archivo→Preferencias→Predeterminadas desde el menú +principal en el propio <em>Subsurface</em>. +Esto facilitará la sincronización entre <em>Subsurface</em> y la app Companion.</td> +</tr></table> +</div> +</div> +<div class="sect3"> +<h4 id="_crear_nuevas_ubicaciones_de_buceo">5.4.3. Crear nuevas ubicaciones de buceo</h4> +<div class="paragraph"><p>Ahora se está preparado para tomar una posición de buceo y enviarla al servidor. +La pantalla de Android se verá como lo imagen de abajo a la izquierda (<strong>A</strong>), +pero sin ninguna inmersión.</p></div> +<div class="paragraph"><p>Tocando el icono "+" de arriba a la derecha se abrirá un menú con tres opciones:</p></div> +<div class="ulist"><ul> +<li> +<p> +Current: Se pedirá un nombre para el lugar (o que se active el GPS si estaba + apagado). Tras lo cual se guardará la posición actual. +</p> +</li> +<li> +<p> +Use map: Esta opción permite al usuario fijar una posición buscándola en un + mapamundi. Se muestra un mapamundi(ver <strong>B</strong> a continuación) sobre el cual indicar + la posición con una pulsación larga en la pantalla táctil (si la posición + marcada es errónea, simplemente se indica una nueva). A continuación hay que + seleccionar el símbolo de chequeo arriba a la derecha. Se mostrará un dialogo + que permitirá introducir un nombre para el punto seleccionado y la fecha y hora + del buceo (ver <strong>C</strong> abajo). De cara a importar esta posición de buceo a + <em>Subsurface</em> es recomendable fijar la misma hora de inmersión que la marcada por + el ordenador de buceo. +</p> +</li> +</ul></div> +<div class="imageblock" style="text-align:center;"> +<div class="content"> +<img src="images/Companion_5.jpg" alt="FIGURA: Companion App, añadir posición usando e mapa" /> +</div> +</div> +<div class="ulist"><ul> +<li> +<p> +Importar desde archivos GPX: El dispositivo android buscará archivos .gpx y + mostrará los que se localicen. El archivo que se seleccione se abrirá y se + mostrarán las posiciones que contiene. Ahora hay que elegir las ubicaciones + correctas y luego seleccionar el símbolo de chequeo arriba ala derecha, tras lo + cual las posiciones se enviarán al servicio web y se añadirán a la lista del + dispositivo android. +</p> +</li> +</ul></div> +</div> +<div class="sect3"> +<h4 id="_listas_de_ubicaciones_de_buceo">5.4.4. Listas de ubicaciones de buceo</h4> +<div class="paragraph"><p>La pantalla principal muestra una lista de ubicaciones de buceo, cada una con un +nombre, fecha y hora (ver <strong>A</strong> debajo). Algunas posiciones pueden tener una +flechita sobre la casilla de selección, lo que indica que necesitan remitirse al +servidor. Se pueden seleccionar posiciones individuales de la lista. Una +posición seleccionada tiene una marca de chequeo en la casilla de selección. Se +pueden efectuar operaciones en grupo (como <em>Delete</em> o <em>Send</em>) sobre todas las +operaciones seleccionadas a la vez.</p></div> +<div class="paragraph"><p>Las posiciones de buceo de la lista pueden visualizarse de dos maneras: una +lista de ubicaciones o un mapa sobre el que se indican las posiciones. La forma +de visualizarla (lista o mapa) se modifica seleccionando <em>Dives</em> arriba a la +izquierda de la pantalla (ver <strong>A</strong> abajo) y luego eligiendo el modo. Si se +selecciona una ubicación (en la lista o en el mapa), se abre un panel de edición +(ver *C abajo) donde pueden cambiarse algunos detalles.</p></div> +<div class="imageblock" style="text-align:center;"> +<div class="content"> +<img src="images/Companion_4.jpg" alt="FIGURE: Companion App, añadir posición usando el mapa" /> +</div> +</div> +<div class="paragraph"><p>Cuando se pulsa sobre una posición (<strong>sin</strong> seleccionar la casilla), se mostrarán +el nombre del punto, la fecha y hora y las coordenadas GPS, con dos opciones +arriba de la pantalla:</p></div> +<div class="ulist"><ul> +<li> +<p> +Edit (lapiz): Permite cambiar el nombre u otras características del punto de + buceo. +</p> +</li> +<li> +<p> +Maps: Muestra el punto de buceo sobre un mapa. +</p> +</li> +</ul></div> +<div class="paragraph"><p>Tras editar y guardar la posición de buceo (ver <strong>C</strong> abajo), se necesita subirla +al servidor, como se explicará a continuación.</p></div> +</div> +<div class="sect3"> +<h4 id="_subir_puntos_de_buceo">5.4.5. Subir puntos de buceo</h4> +<div class="paragraph"><p>Hay varias formas de enviar los buceos al servidor; la más fácil es simplemente +seleccionar la inmersión (ver la imagen <strong>A</strong> abajo) y luego pulsar la flecha +arriba a la derecha de la pantalla.</p></div> +<div class="admonitionblock"> +<table><tr> +<td class="icon"> +<img src="images/icons/important.png" alt="Important" /> +</td> +<td class="content">El usuario debe tener cuidado ya que el icono de papelera de la derecha +significa exactamente lo que se supone: borra los puntos de buceo seleccionados.</td> +</tr></table> +</div> +<div class="imageblock" style="text-align:center;"> +<div class="content"> +<img src="images/Companion_1.jpg" alt="FIGURA: Capturas (A-B) de la app companion" /> +</div> +</div> +<div class="paragraph"><p>Después de un viaje de buceo usando Companion, todos los puntos de inmersión +estarán listos para ser descargados a un diario de <em>Subsurface</em> (ver a +continuación).</p></div> +</div> +<div class="sect3"> +<h4 id="_ajustes_de_la_companion_app">5.4.6. Ajustes de la Companion app</h4> +<div class="paragraph"><p>Seleccionar la opción Settings del menú, resulta en la imagen B de arriba a la +derecha.</p></div> +<div class="sect4"> +<h5 id="_server_and_account">Server and account</h5> +<div class="ulist"><ul> +<li> +<p> +<em>Web-service URL</em>. Esta está predefinida (<a href="http://api.hohndel.org/">http://api.hohndel.org/</a>) +</p> +</li> +<li> +<p> +<em>User ID.</em> El DIVERID obtenido al registrarse como indicábamos antes. La forma + más fácil de introducirlo es simplemente copiar y pegar desde el correo de + confirmación pero, desde luego, el usuario teclearlo carácter a carácter. +</p> +</li> +</ul></div> +</div> +<div class="sect4"> +<h5 id="_synchronization">Synchronization</h5> +<div class="ulist"><ul> +<li> +<p> +<em>Synchronize on startup</em>. Si se selecciona, los puntos de buceo del + dispositivo android y los del servicio web se sincronizarán cada vez que se + inicie la app. +</p> +</li> +<li> +<p> +<em>Upload new dives</em>. Si se selecciona, cada vez que el usuario añada una + ubicación de buceo, se enviará automáticamente al servidor. +</p> +</li> +</ul></div> +</div> +<div class="sect4"> +<h5 id="_background_service">Background service</h5> +<div class="paragraph"><p>En vez de tomar una sola ubicación de buceo, los usuarios pueden dejar el +servicio ejecutándose en segundo plano en tu dispositivo android, tomando +continuamente posiciones GPS</p></div> +<div class="paragraph"><p>Los ajustes, a continuación, definirán el comportamiento del servicio:</p></div> +<div class="ulist"><ul> +<li> +<p> +<em>Min duration</em>. En minutos. La app intentará tomar una posición cada X minutos + hasta que el usuario la detenga. +</p> +</li> +<li> +<p> +<em>Min distance</em>. En metros. Distancia mínima entre dos posiciones. +</p> +</li> +<li> +<p> +<em>Name template</em>. La plantilla de nombre que usará la app cuando guarde las + posiciones. +</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>¿ Como trabaja el servicio en segundo plano ?</em> Suponiendo que el usuario ha +fijado 5 minutos y 50 metros en los ajustes anteriores, la app tomará una +posición en la ubicación actual, seguida por otra cada 5 minutos <strong>o</strong> cada vez +que se desplace 50 metros de la posición anterior. Si las siguientes ubicaciones +están en el radio de 50 metros de la anterior, no se guardarán. De esta forma, +si el usuario no se está moviendo, solo se guarda una posición, pero si se +mueve, puede llegar a tener una traza de su viaje al guardar una ubicación cada +50 metros.</td> +</tr></table> +</div> +</div> +<div class="sect4"> +<h5 id="_other">Other</h5> +<div class="ulist"><ul> +<li> +<p> +<em>Mailing List</em>. El buzón de correo de <em>Subsurface</em>. El usuario enviar mails a + la lista de correo de <em>Subsurface</em>. +</p> +</li> +<li> +<p> +<em>Subsurface website</em>. Un link a la URL de la página de <em>Subsurface</em>. +</p> +</li> +<li> +<p> +<em>Version</em>. Muestra la versión actual de la app Companion. +</p> +</li> +</ul></div> +</div> +<div class="sect4"> +<h5 id="_search">Search</h5> +<div class="paragraph"><p>Se utiliza para buscar en las ubicaciones de buceo guardadas, por nombre o por +fecha y hora.</p></div> +</div> +<div class="sect4"> +<h5 id="_start_service">Start service</h5> +<div class="paragraph"><p>Inicia el servicio en segundo plano siguiendo los ajustes previamente definidos.</p></div> +</div> +<div class="sect4"> +<h5 id="_disconnect">Disconnect</h5> +<div class="paragraph"><p>Esta opción está mal nombrada. "Desconecta" la app del servidor reseteando el +DIVERID en la app, y retorna a la primera pantalla desde la que se puede crear +una cuenta, reactivar el DIVERID o volver a poner el del usuario. Desconectar +puede ser útil si se desea descargar a un dispositivo android posiciones de otro +buceador registrado o enviar la posición actual al servidor con el ID de otro +buceador registrado.</p></div> +</div> +<div class="sect4"> +<h5 id="_send_all_locations">Send all locations</h5> +<div class="paragraph"><p>Esta opción envía todas las posiciones guardadas en el dispositivo android al +servidor.</p></div> +</div> +</div> +<div class="sect3"> +<h4 id="S_iphone">5.4.7. Usar la app Subsurface companion en un <em>iPhone</em> para registra puntos de buceo</h4> +<div class="paragraph"><p>El interfaz de iPhone es bastante simple. Se necesita introducir la ID de +usuario (obtenida durante el registro) en el espacio reservado para ello, luego +seleccionar "Dive in" (ver parte izquierda de la imágen de abajo) y se empieza +a recoger información de las ubicaciones.</p></div> +<div class="imageblock" style="text-align:center;"> +<div class="content"> +<img src="images/iphone.jpg" alt="FIGURE: Usiar la aplicación iPhone companion" width="640" /> +</div> +</div> +<div class="paragraph"><p>Las inmersiones se pueden añadir de forma automática o manual. En modo manual, +se añade una sola ubicación de buceo o "waypoint" al flujo de entrada de datos +del GPS. En modo automático se crea una traza continua de posiciones GPS de las +cuales, posteriormente, después de haberse importado, <em>Subsurface</em> puede +seleccionar las posiciones correctas en base a las horas de los buceos. El modo +por defecto para el <em>iPhone</em> es el automático. Cuando se añade una inmersión, +el servicio de posicionamiento se inicia automáticamente y aparece una barra +roja en la parte de abajo de la pantalla. Tras el buceo, se puede hacer clic en +la barra roja para detener el servicio de posicionamiento. Mientras el servicio +se está ejecutando, solo se pueden añadir inmersiones usando el mecanismo +manual.</p></div> +<div class="paragraph"><p>Se puede editar el nombre del punto de buceo posteriormente, seleccionando la +inmersión de la lista y clicando en el nombre. No hay otros campos editables. +La lista se sube automáticamente desde el <em>iPhone</em> al servicio web y no hay +opción a hacerlo manualmente.</p></div> +</div> +<div class="sect3"> +<h4 id="_descargar_ubicaciones_de_buceo_al_diario_en_em_subsurface_em">5.4.8. Descargar ubicaciones de buceo al diario en <em>Subsurface</em></h4> +<div class="paragraph"><p>Hay que descargar a <em>Subsurface</em> las inmersiones del ordenador de buceo, o +crearlas manualmente, antes de obtener las coordenadas del servifor. El diálogo +de descarga se puede obtener vía <em>Ctrl+G</em> o desde el menú principal de +<em>Subsurface</em>, <em>Importar → Importar datos GPS del servicio Subsurface</em>, +resultando la imagen de abajo a la izquierda (A). La primera vez que se use, el +campo DIVERID estará en blanco. Introducir el DIVERID. Después se pulsa el botón +Descargar y comenzará la descarga, tras lo cual aparece la pantalla de abajo a +la derecha (<strong>B</strong>):</p></div> +<div class="imageblock" style="text-align:center;"> +<div class="content"> +<img src="images/DownloadGPS.jpg" alt="[FIGURE: Descargar datos GPS de la app Companion]" /> +</div> +</div> +<div class="paragraph"><p>Nótese que ahora está activo el botón <em>Aplicar</em>. Pulsarlo para actualizar las +inmersiones recién creadas o descargadas a <em>Subsurface</em>, lo cual aplicará las +coordenadas y los nombres que se hayan dado en la app en todas las inmersiones +en las que coincidan las fechas y las horas de las posiciones GPS descargadas. +Si se ha introducido en <em>Subsurface</em> el nombre del punto de buceo antes de +descargar las coordenadas GPS, este nombre tendrá preferencia sobre los +descargados.</p></div> +<div class="paragraph"><p>Ya que <em>Subsurface</em> busca coincidencias entre las localizaciones GPS del +dispositivo android y la información del ordenador de buceo basándose en la +fecha y la hora, la asignación automática depende de la coincidencia entre los +datos de ambos dispositivos. Aunque <em>Subsurface</em> tiene un margen de tolerancia +muy amplio, puede ser incapaz de identificar la inmersión correcta, si hay mucha +diferencia entre la hora del ordenador de buceo y la del dispositivo android, +resultando en que no haya actualización.</p></div> +<div class="paragraph"><p>Fechas y horas similares en los dispositivos no siempre son posibles y puede +haber muchas razones para ello (p.e. zonas horarias), o <em>Subsurface</em> puede ser +incapaz de decidir cual es la posición correcta de una inmersión (p.e. en +inmersiones repetitivas mientras se ejecuta el servicio en 2º plano puede haber +varios puntos incluidos en el rango de tiempo que casen no solo para la primera +inmersión, sino también para las siguientes). Una solución alternativa para esta +situación sería editar manualmente la hora en la lista de inmersiones de +<em>Subsurface</em> <strong>antes</strong> de descargar los datos GPS, para hacerla coincidir con la +de estos, y luego volver a cambiarla a la correcta <strong>después</strong> de la descarga.</p></div> +<div class="admonitionblock"> +<table><tr> +<td class="icon"> +<img src="images/icons/info.jpg" alt="Note" /> +</td> +<td class="content">SUGERENCIAS:</td> +</tr></table> +</div> +<div class="ulist"><ul> +<li> +<p> +El servicio en segundo plano es una herramienta poderosa, pero puede llenar la + lista de localizaciones con muchas posiciones innecesarias que no correspondan a + los puntos exactos de buceo, sino a la ruta seguida por el barco. Actualmente, + borrar estas posiciones del servidor resulta difícil. En algunas situaciones + resulta, pues, prudente limpiar la lista del dispositivo android antes de enviar + los puntos al servidor simplemente borrando los que no sean correctos. Esto + puede ser necesario, por ejemplo, si se desea mantener limpia la lista de + ubicaciones para poder visualizarlas en el mapa del servidor o del dispositivo + android. +</p> +</li> +<li> +<p> +También tendría sentido proporcionar nombres significativos a las + localizaciones enviadas al servidor o, al menos, usar tal nombre en el ajuste + <em>Name Template</em> si se va a ejecutar el background service, especialmente durante + los viajes de buceo con muchas inmersiones y puntos de buceo. +</p> +</li> +</ul></div> +</div> +</div> +</div> +</div> +<div class="sect1"> +<h2 id="S_LoadImage">6. El cargador de fotografías de <em>Subsurface</em></h2> +<div class="sectionbody"> +<div class="paragraph"><p>Muchos buceadores (si no la mayoría) llevan consigo una cámara y toman +fotografías durante sus inmersiones. Sería interesante poder asociar cada +fotografía con una inmersión concreta. <em>Subsurface</em> nos permite cargar fotos en +una inmersión. Las fotos se superponen en el perfil de la inmersión, desde donde +pueden visualizarse.</p></div> +<div class="sect2"> +<h3 id="_cargar_fotos_y_sincronizar_la_camara_con_el_ordenador_de_buceo">6.1. Cargar fotos y sincronizar la cámara con el ordenador de buceo</h3> +<div class="paragraph"><p>Se selecciona una inmersión o un grupo de ellas en la lista. Luego se hace +clic-derecho en la selección y se elige la opción <em>Carga imagenes</em>:</p></div> +<div class="imageblock" style="text-align:center;"> +<div class="content"> +<img src="images/LoadImage1_f20.jpg" alt="FIGURA: Opción de carga de imágenes" /> +</div> +</div> +<div class="paragraph"><p>Aparecerá el navegador de archivos del sistema. Se selecciona la carpeta y las +fotografías que se necesitan cargar en <em>Subsurface</em> y se hace clic en el botón +<em>Abrir</em>.</p></div> +<div class="imageblock" style="text-align:center;"> +<div class="content"> +<img src="images/LoadImage2_f20.jpg" alt="FIGURA: Opción de carga de imágenes" /> +</div> +</div> +<div class="paragraph"><p>Esto desplegará el diálogo de sincronización que se muestra a continuación. El +problema crítico es que la sincronización horaria entre la cámara y el ordenador +de buceo no sea perfecta, en ocasiones difieren varios minutos. Si <em>Subsurface</em> +puede sincronizarlos, entonces puede utilizar las horas de las fotografías para +posicionarlas en el perfil de la inmersión.</p></div> +<div class="paragraph"><p><em>Subsurface</em> puede conseguir esta sincronización de tres maneras:</p></div> +<div class="ulist"><ul> +<li> +<p> +<strong>Proactivamente</strong>: Antes de la inmersión, asegúrate de que los ajustes de la + cámara coinciden con los del ordenador de buceo, cambiándolo en uno de los + dispositivos o en ambos. +</p> +</li> +<li> +<p> +<strong>Manualmente</strong>: Si el usuario anotó la hora exacta de la cámara al inicio de la + inmersión, se puede obtener la diferencia de tiempo entre los dos dispositivos. + En realidad, si no se han variado los ajustes horarios, se pueden conseguir tras + la inmersión o, incluso, al final del día. Entonces se puede indicar manualmente + la diferencia en el diálogo de <em>Desplazamiento horario</em>. En la parte de arriba + del diálogo hay una herramienta para indicar tiempos, evidente en la figura <strong>A</strong> + a continuación. Si la cámara lleva un adelanto de 7 minutos sobre el ordenador + de buceo, fijamos en la herramienta un valor de 00:07. Se ignora cualquier + sufijo "AM" o "PM". Seleccionamos el botón <em>OK</em> y se habrá obtenido la + sincronización. Hay que marcar <em>Más pronto</em> o <em>Más tarde</em> según corresponda. En + el ejemplo a continuación, la opción <em>Más pronto</em> es la correcta ya que la + cámara de fotos va 7 minutos por delante del ordenador de buceo. +</p> +</li> +</ul></div> +<div class="imageblock" style="text-align:center;"> +<div class="content"> +<img src="images//LoadImage3b_f20.jpg" alt="FIGURA: Diálogo de sincronización" /> +</div> +</div> +<div class="ulist"><ul> +<li> +<p> +<strong>Por fotografía</strong>: Hay una forma muy cómoda de conseguir sincronización. Si se + toma una foto de la pantalla del ordenador mostrando la hora, <em>Subsurface</em> puede + obtener la hora exacta a la que se tomó la foto usando los metadatos que la + cámara guarda en cada foto. Para ello se utiliza la mitad inferior del diálogo + <em>Desplazamiento horario</em>. Si se selecciona la barra horizontal titulada + "<em>Selecciona la imagen del ordenador de buceo mostrando la hora</em>", aparece un + navegador de archivos. Se selecciona la fotografía y se pulsa <em>Abrir</em>. La foto + del ordenador de buceo aparecerá en el recuadro inferior del diálogo. + <em>Subsurface</em> sabe exactamente cuando se tomó la foto. Ajusta la fecha y hora en + el diálogo a la izquierda de la foto para que refleje los de la pantalla del + ordenador. Tras el ajuste <em>Subsurface</em> conoce exactamente cual es la diferencia + entre cámara y ordenador y se podrán sincronizar. La figura anterior muestra una + fotografía del ordenador de buceo y la herramienta de tiempo ajustada a la fecha + y hora de la imagen <strong>B</strong> anterior. +</p> +</li> +</ul></div> +<div class="paragraph"><p>Si la hora de la foto es muy anterior o posterior al buceo, no se sitúa sobre el +perfil de la inmersión. Si está en un rango de 30 minutos, sí se muestra.</p></div> +</div> +<div class="sect2"> +<h3 id="_visualizar_las_imagenes">6.2. Visualizar las imágenes</h3> +<div class="paragraph"><p>Después que las imágenes han sido cargadas aparecen en dos lugares:</p></div> +<div class="ulist"><ul> +<li> +<p> +La pestaña <em>Fotos</em> del panel <em>Notas</em>. +</p> +</li> +<li> +<p> +Como pequeños iconos (chinchetas) sobre el perfil de inmersión, en posiciones + que relejan la hora en que se tomó cada fotografía. Para ver las fotos sobre el + perfil, activa el botón <em>Mostrar fotos</em> a la izquierda del perfil: +</p> +</li> +</ul></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>Esto producirá un perfil como el que se muestra a continuación</p></div> +<div class="imageblock" style="text-align:center;"> +<div class="content"> +<img src="images/LoadImage4_f20.jpg" alt="FIGURA: Fotos sobre un perfil de inmersión" /> +</div> +</div> +<div class="paragraph"><p>Si se sitúa el ratón sobre uno de los iconos, se mostrará una versión reducida +de la foto. Ver imagen a continuación:</p></div> +<div class="imageblock" style="text-align:center;"> +<div class="content"> +<img src="images/LoadImage5_f20.jpg" alt="FIGURA: Foto reducida sobre perfil de inmersión" /> +</div> +</div> +<div class="paragraph"><p>Si hacemos clic sobre la imagen reducida aparecerá la fotografía a tamaño +completo sobre la ventana de <em>Subsurface</em>. Esto permite una buena visión de las +fotos que han sido importadas. Ver imagen a continuación. +Cada imagen reducida tiene una pequeña papelera en su esquina superior +izquierda (ver imagen anterior). Si se selecciona la papelera, la foto se +borra de la inmersión, así pues, hay que tener un poco de cuidado al clicar +sobre las imágenes. Las imágenes también puede borrase desde la pestaña <em>Fotos</em> +(ver en el siguiente punto).</p></div> +<div class="imageblock" style="text-align:center;"> +<div class="content"> +<img src="images/LoadImage6_f20.jpg" alt="FIGURA: Foto a pantalla completa sobre el perfil de inmersión" /> +</div> +</div> +<div class="sect3"> +<h4 id="_la_pestana_em_fotos_em">6.2.1. La pestaña <em>Fotos</em></h4> +<div class="paragraph"><p>Las fotografías asociadas a una inmersión se muestran como miniaturas en la +pestaña <em>Fotos</em> del <em>Panel de inmersión</em>. Se puede acceder con facilidad a las +fotos hechas en rápida sucesión durante la inmersión, desde la pestaña <em>Fotos</em>. +Esta pestaña es una herramienta para acceder individualmente a las fotos de un +buceo, mientras que las "chinchetas" en el perfil de inmersión proporcionan una +indicación de cuando se tomó la foto. Clicando una sola vez sobre una de la +miniaturas de la pestaña <em>Fotos</em>, seleccionamos una foto. Haciendo doble-clic +sobre una miniatura, se muestra la imagen a tamaño completo superpuesta a la +ventana de <em>Subsurface</em>. Podemos borrar una foto desde la pestaña <em>Fotos</em> +seleccionándola (un solo clic) y pulsando a continuación la tecla <em>Supr</em> en el +teclado. Esto eliminará la foto tanto de la pestaña <em>Fotos</em> como del <em>Perfil de +la inmersión</em>.</p></div> +</div> +<div class="sect3"> +<h4 id="_fotos_en_disco_duro_externo">6.2.2. Fotos en disco duro externo</h4> +<div class="paragraph"><p>La mayoría de fotosubs guardan sus fotografías en un disco duro externo. Si este +disco puede mapearse (como es casi siempre el caso) <em>Subsurface</em> puede acceder +directamente a las fotos. Esto facilita la interacción entre <em>Subsurface</em> y un +repositorio externo de fotos. Cuando se asocia un perfil de inmersión con fotos +de un disco externo se utiliza el procedimiento normal de selección +y sincronización (ver en el texto anterior). Sin embargo, después de que el +disco externo haya sido desconectado, <em>Subsurface ya no podrá acceder a las +fotos. Si se ha activado la visualización de fotos sobre el perfil (utilizando +la barra de herramientas a la izquierda del perfil), el programa solo mostrará +unos pequeños puntos blancos donde deberían mostrarse las fotos. Además, la +pestaña _Fotos</em> solo mostrará los nombres de los archivos de las imágenes. Este +es el funcionamiento normal. Si, posteriormente, el disco externo con las fotos +se vuelve a conectar, las fotos se visualizarán normalmente.</p></div> +</div> +<div class="sect3"> +<h4 id="S_FindMovedImages">6.2.3. Mover fotografías entre directorios, discos duros u ordenadores</h4> +<div class="paragraph"><p>Tras haber cargado una fotografía en <em>subsurface</em> y haberla asociado a un buceo +determinado, se archiva el directorio donde la foto permanece guardada, para poder +encontrarla cuando se vuelva a abrir la inmersión. Si la foto o la colección +completa de fotos se trasladan a otro disco o a una máquina distinta, sería +bastante raro que la estructura de directorios fuera idéntica a la de la fotografía +cargada originalmente. Cuando esto sucede, <em>Subsurface</em> busca las fotos en el +directorio original desde el que fueron cargadas, no las encuentra y, por tanto, +no las puede mostrar. Ya que, después de mover fotos, un gran número puede +necesitar borrarse y reimportarse desde la nueva localización, <em>Subsurface</em> +tiene un mecanismo que facilita el proceso de actualizar la información del +directorio para cada foto: actualizaciones automáticas utilizando huellas.</p></div> +<div class="paragraph"><p>Cuando se carga una foto en <em>Subsurface</em>, se calcula una huella para la imagen +y se guarda con la otra información de referencia para la foto. Tras mover una +colección de fotos (que ya ha sido cargada en <em>Subsurface</em>) a un directorio, +disco u ordenador diferente, <em>Subsurface</em> puede llevar a cabo los siguientes +pasos:</p></div> +<div class="ulist"><ul> +<li> +<p> +Buscar en un directorio concreto (y todos sus subdireectorios recursivamente) +al que se han llevado las fotos. +</p> +</li> +<li> +<p> +Calcular huellas para todas las fotos de este directorio, y +</p> +</li> +<li> +<p> +si hay coincidencia entre una de las huellas calculadas y la que se calculó +al cargar la foto en <em>Subsurface</em> (incluso si el nombre del archivo hubiera +cambiado), actualizar automáticamente la información de directorio, de foma que +<em>Subsurface</em> pueda encontrar la foto en el nuevo directorio. +</p> +</li> +</ul></div> +<div class="paragraph"><p>Esto se consigue seleccionando desde el Menú Principal: <em>Archivo → Encontrar +imágenes desplazadas</em>. Esto presenta una ventana en la cual es necesario +especificar el NUEVO directorio de las fotos. Se selecciona el directorio +apropiado y se clica el botón <em>Escanear</em> en la parte inferior derecha del +panel. El proceso puede requerir varios minutos para completarse, tras lo +cual <em>Subsurface</em> mostrará las fotos correctas cuando se abra un buceo.</p></div> +<div class="sidebarblock" id="Image_fingerprint_upgrade"> +<div class="content"> +<div class="paragraph"><p><strong>Actualizar colecciones de fotos existentes sin huella</strong></p></div> +<div class="admonitionblock"> +<table><tr> +<td class="icon"> +<img src="images/icons/important.png" alt="Important" /> +</td> +<td class="content"><em>Subsurface</em> calcula automáticamente huellas para todas las imágenes a las +que tiene acceso. Cuando manipules estas imágenes, asegúrate de que todas las +imágenes asociadas al divelog queden accesibles. <em>Subsurface</em>, automáticamente +comprueba y actualiza (en caso necesario) las huellas asociadas a cada buceo +si: +- Las imágenes asociadas a ese buceo son visibles como miniaturas en el perfil. +- Se edita cualquier cosa en el panel <strong>Notas</strong> y se guardan las modificaciones +con <em>Guardar cambios</em>.</td> +</tr></table> +</div> +</div></div> +</div> +</div> +<div class="sect2"> +<h3 id="_registrar_tipos_de_inmersion_especiales">6.3. Registrar tipos de inmersión especiales</h3> +<div class="sect3"> +<h4 id="S_MulticylinderDives">6.3.1. Inmersiones multi botella</h4> +<div class="paragraph"><p><em>Subsurface</em> maneja fácilmente inmersiones que requieren más de una botella. El +buceo multi botella se produce habitualmente cuando (a) un buceador no tiene +bastante gas para completar una inmersión con una sola botella o (b) cuando el +buceador necesita más de una mezcla de gas a causa de la profundidad o de las +necesidades descompresivas de la inmersión. Por este motivo, las inmersiones +multi tanque son empleadas a menudo por los buceadores técnicos ya que bucean +profundo y durante mucho tiempo. En lo que corresponde a <em>Subsurface</em>, solo hay +dos clases de información que necesitan proporcionarse:</p></div> +<div class="ulist"><ul> +<li> +<p> +<strong>Describir las botellas usadas durante el buceo</strong>. Esto se hace en la pestaña + <strong>Equipo</strong> del panel <strong>Información</strong> tal como <a href="#cylinder_definitions">se describe anteriormente</a>. + se introducen las botellas una a una, especificando las características de la + botella y la composición del gas de cada una de ellas. +</p> +</li> +<li> +<p> +<strong>Registrar los momentos en que se cambia de una botella a otra</strong>. Esta es una + información que facilitan algunos ordenadores (siempre y cuando el buceador + se la diga al ordenador durante el buceo). Si el ordenador no la proporciona, + el buceador necesita registrarla usando un método diferente, p.e. en una + pizarra. +</p> +</li> +<li> +<p> +<strong>Indica los cambios de botella en el perfil</strong>. Si se utilizó la última opción, + el buceador ha de indicar el evento de cambio de gas haciendo clic derecho en + el momento adecuado del panel <strong>Perfil de inmersión</strong> y señalar la botella a la + que se cambió. Tras hacer clic derecho, seguir el menú contextual a "Añadir + cambio de gas" y seleccionar la botella apropiada entre las definidas en el + primer paso (ver imagen a continuación). Si el botón <strong>Barra de botellas</strong> de + la barra de herramientas se ha activado, los cambios también se indicarán en + la barra. +</p> +</li> +</ul></div> +<div class="paragraph"><p>Habiendo llevado a cabo estas tareas, <em>Subsurface</em> indica en el perfil de buceo +el uso de diferentes botellas. A continuación, una inmersión multi botella que +empieza con EAN28, se cambia a EAN50 despues de 26 minutos para efectuar la +deco.</p></div> +<div class="imageblock" style="text-align:center;"> +<div class="content"> +<img src="images/multicylinder_dive.jpg" alt="FIGURa: Perfil multi tanque" /> +</div> +</div> +</div> +<div class="sect3"> +<h4 id="_inmersiones_en_montaje_lateral_sidemount">6.3.2. Inmersiones en montaje lateral (sidemount)</h4> +<div class="paragraph"><p>El buceo en montaje lateral es solo otra forma de buceo multi tanque, a menudo +con ambas o todas las botellas conteniendo la misma mezcla. Aunque es una +configuración popular entre los espeleo buceadores, el buceo en lateral se +puede efectuar por buceadores recreativos que hayan completado el entrenamiento +adecuado. Registrar inmersiones en sidemount se hace en tres pasos:</p></div> +<div class="ulist"><ul> +<li> +<p> +*Durante el buceo, se registran los eventos de cambio de botella". Ya que bucear + en lateral supone, normalmente, usar 2 botellas con aire o con la misma mezcla, + <em>Subsurface</em> distingue entre estas botellas. En comparación, la mayoría de + ordenadores de buceo que contemplan cambios de gas solo distinguen entre + diferentes <em>gases</em> usados, no entre diferentes <em>botellas</em> usadas. Esto supone + que, cuando se descargan inmersiones en sidemount desde estos ordenadores, los + eventos de cambio entre las diferentes botellas no se descargan. Esto puede + suponer que se tenga que guardar un registro manual de cambios de botella o + (si el ordenador tiene esta posibilidad) marcando cada cambio de botella con + una marca que se pueda descargar posteriormente. Regresar de una inmersión + en lateral con la información de cambios de botella es la única parte con + truco en cuanto a registrar buceos en sidemount. +</p> +</li> +<li> +<p> +<strong>En <em>Subsurface</em> detalla las botellas usadas en la inmersión</strong>. El usuario + registra las especificaciones para las diferentes botellas usando la pestaña + <strong>Equipo</strong> del <strong>Panel de información</strong> (véase imagen a continuación en la que se + usó una botella de 12 litros). +</p> +</li> +<li> +<p> +<strong>Indicar eventos de cambio de botella sobre el perfil de <em>Subsurface</em></strong>. Una + vez que se ha importado la inmersión desde el ordenador de buceo, es necesario + indicar los eventos de cambio de botella sobre el perfil. Los cambios se + anotan haciendo clic-derecho en el punto correspondiente del perfil y entonces + seleccionando <em>Añadir cambio de gas</em>. Se muestra una lista de las botellas con + la que se está utilizando en gris. En la imagen a continuación, Tank 1 está en + gris, permitiendo solo la selección de Tank 2. Tras seleccionar la botella + correspondiente el cambio se indicará sobre el perfil con un icono de una + botella. Si está activada la <strong>Barra de botellas</strong> también se indicará el cambio + sobre ella (ver imagen a continuación). Una vez que todos los cambios de + botella han sido registrados sobre el perfil, las presiones correctas de ambas + botellas se mostrarán en el perfil, como en la imagen de ejemplo. +</p> +</li> +</ul></div> +<div class="imageblock" style="text-align:center;"> +<div class="content"> +<img src="images/sidemount1.jpg" alt="FIGURE: Sidemount profile" /> +</div> +</div> +<div class="paragraph"><p>Esta sección es un ejemplo de la versatilidad de <em>Subsurface</em> como herramienta +de registro de inmersiones.</p></div> +</div> +<div class="sect3"> +<h4 id="S_sSCR_dives">6.3.3. Inmersiones con rebreather de circuito semi cerrado (SCR)</h4> +<div class="admonitionblock"> +<table><tr> +<td class="icon"> +<img src="images/halcyon_RB80.jpg" alt="Note" /> +</td> +<td class="content">Los rebreathers semi cerrados pasivos (pSCR) suponen un avance técnico en el +equipo de buceo que recircula el gas que el buzo respira, y elimina el dióxido +de carbono del gas exhalado. Al tiempo que una pequeña cantidad del gas exhalado +(habitualmente una décima parte) se libera en el agua, una pequeña cantidad de +gas de la botella se introduce en el circuito (habitualmente nitrox). Un buzo +usando una sola botella de gas puede, pues, bucear durante periodos de tiempo +mucho mayores que utilizando una configuración recreativa de circuito abierto. +Con los pSCR una cantidad muy pequeña de gas se libera cada vez que el buzo +inhala. Con los equipos SCR activos (aSCR), en cambio, una pequeña cantidad del +gas respirado se libera continuamente.</td> +</tr></table> +</div> +<div class="paragraph"><p>Para registrar inmersiones con pSCR, no se requieren procedimientos especiales, +solo los pasos normales descritos con anterioridad:</p></div> +<div class="ulist"><ul> +<li> +<p> +Seleccionar el modo pSCR en el desplegable <em>Modo de inmersión</em> en el panel + <strong>Información</strong>. +</p> +</li> +<li> +<p> +El buceo con pSCR, a menudo, requiere cambios de gas, necesitando una botella + adicional. Hay, pues, que describir todas las botellas como se indicó con + anterioridad e indicar los cambios de botella/gas como se explicó en la + sección <a href="#S_MulticylinderDives">Inmersiones multi botella</a>. +</p> +</li> +</ul></div> +<div class="paragraph"><p>Si se ha seleccionado pSCR en el <em>Modo de inmersión</em>, el techo de buceo para +inmersiones pSCR se ajusta para la caída de oxígeno a través de la boquilla +que, a menudo, requiere mayores períodos de descompresión. A continuación un +perfil de inmersión de un buceo con pSCR usando EAN36 como gas de fondo y +oxígeno para la descompresión. Fíjate que la inmersión duró unas dos horas.</p></div> +<div class="imageblock" style="text-align:center;"> +<div class="content"> +<img src="images/pSCR_profile.jpg" alt="FIGURA: Perfil pSCR" /> +</div> +</div> +</div> +<div class="sect3"> +<h4 id="S_CCR_dives">6.3.4. Inmersiones con rebreather de circuito cerrado (CCR)</h4> +<div class="admonitionblock"> +<table><tr> +<td class="icon"> +<img src="images/APD.jpg" alt="Note" /> +</td> +<td class="content">Los rebreathers de circuito cerrado utilizan tecnología avanzada para +reciclar el gas que se ha respirado, mientras mantienen una concentración de +oxígeno respirable llevando a cabo dos acciones: +a) Eliminan dióxido de carbono del gas que se ha exhalado. +b) Regulan la concentración de oxígeno para que permanezca en los límites. +La interfaz CCR de <em>Subsurface</em> es experimental actualmente y se halla bajo +desarrollo activo. <em>Subsurface</em> soporta en estos momentos el Poseidon MKVI y +los PD Discovery/Evolution En contraste con un ordenador +de buceo recreativo convencional, el ordenador de un sistema CCR no permite +descargar un diario que contenga múltiples inmersiones. En su lugar, cada buceo +se guarda independientemente. Esto significa que <em>SUbsurface</em> no puede descargar +el diario directamente desde un CCR, sino que lo importa de la misma manera que +se importan datos de otras bases de datos digitales, una inmersión cada vez.</td> +</tr></table> +</div> +</div> +<div class="sect3"> +<h4 id="_importar_una_inmersion_con_ccr">6.3.5. Importar una inmersión con CCR</h4> +<div class="paragraph"><p>Véase la sección que trata de <a href="#S_ImportingAlienDiveLogs">Importar información de buceo de otras fuentes digitales</a>. +Desde el menú principal de <em>Subsurface</em>, seleccionar <em>Import → Importar archivos +de registro</em> para desplegar el <a href="#Unified_import">Diálogo de importación universal</a>. +Como se explicaba en esa sección, en la parte de abajo a la derecha hay una lista +desplegable (etiquetada como <em>Filtro:</em>) de dispositivos que incluye los archivos del +(Poseidon) MKVI o APD (la funcionalidad para otros dispositivos CCR está en desarrollo +actualmente). Tras haber seleccionado el dispositivo y el directorio donde se +hallan los archivos originales del ordenador CCR, se puede seleccionar un +archivo concreto (en el caso del MKVI es un archivo con extensión .txt). Tras +seleccionar el archivo, activar el botón <em>Abrir</em> de abajo a la derecha. Lee la +sección a continuación para:</p></div> +</div> +<div class="sect3"> +<h4 id="_informacion_mostrada_para_un_buceo_con_ccr">6.3.6. Información mostrada para un buceo con CCR</h4> +<div class="paragraph"><p><em>Presiones parciales de los gases</em>: El gráfico de presión parcial de oxígeno +muestra la información de los sensores de oxígeno del equipo CCR. A diferencia +del equipo de circuito abierto (donde los valores de pO<sub>2</sub> se calculan en base +a la composición del gas y la profundidad), los equipos CCR proporcionan +mediciones instantáneas de pO<sub>2</sub>, a partir de sensores de oxígeno. En este +caso el gráfico de presión parcial de oxígeno debería se bastante plano, +reflejando el ajuste del setpoint durante la inmersión. La pO<sub>2</sub> media no es +la media de presiones parciales de oxígeno que facilita el equipo CCR, sino +un valor calculado por <em>Subsurface</em> de la siguiente forma:</p></div> +<div class="ulist"><ul> +<li> +<p> +Para DOS sensores de O<sub>2</sub> se da en valor medio de ambos sensores. +</p> +</li> +<li> +<p> +Para sistemas de TRES sensores (p.e. APD), también se usa la media. Sin + embargo las lecturas simultaneas de diferentes sensores con diferencias de + más de 0,1 bar, se consideran falsas y se ignoran. +</p> +</li> +</ul></div> +<div class="paragraph"><p>La pO<sub>2</sub> media de los sensores se indica con una línea verde.</p></div> +<div class="paragraph"><p>El valor del setpoint así como las lecturas de de los sensores de oxígeno +individuales puede mostrarse. La presentación en pantalla de información CCR +adicional se activa seleccionando las opciones adecuadas en el panel <em>Preferencias</em> +(accesible seleccionando <a href="#S_CCR_options"><em>Archivo → Preferencias → Gráfico</em></a>). +Esta parte del panel <em>Preferencias</em>, mostrada en la siguiente imagen, se +presenta como dos casillas seleccionables que modifican la presentación de la +pO<sub>2</sub> cuando se halla activada la opción correspondiente de la barra de herramientas +del Perfil de Inmersión.</p></div> +<div class="imageblock" style="text-align:center;"> +<div class="content"> +<img src="images/CCR_preferences_f20.jpg" alt="FIGURA: Panel de preferencias de CCR" /> +</div> +</div> +<div class="paragraph"><p>Clicar cualquiera de las casillas seleccionables permite mostrar información +adicional relativa al oxígeno, siempre que el botón pO<sub>2</sub> de la barra de +herramientas del panel <em>Perfil</em> esté activado.</p></div> +<div class="paragraph"><p>La primera casilla permite mostrar información del setpoint. Esta es una línea +roja superpuesta al gráfico verde de presión parcial de oxígeno y permite +comparar la media de presiones parciales de oxígeno medidas, frente al valor +del setpoint, como se muestra a continuación.</p></div> +<div class="paragraph"><p>image::images/CCR_setpoint_f20.jpg"FIGURA: Gráfico de pO2 y setpoint del CCR",align="center"]</p></div> +<div class="paragraph"><p>La segunda casilla permite mostrar datos de cada sensor de oxígeno individual +del equipo CCR. Los datos de cada sensor se colorean de la siguiente forma:</p></div> +<div class="ulist"><ul> +<li> +<p> +Sensor 1: gris +</p> +</li> +<li> +<p> +Sensor 2: azul +</p> +</li> +<li> +<p> +Sensor 3: marrón +</p> +</li> +</ul></div> +<div class="paragraph"><p>La media de pO<sub>2</sub> se indica por la línea verde. Así se pueden comparar los +datos de cada uno de los sensores de oxígeno, lo cual es útil para detectar +lecturas erráticas o anormalmente bajas de un sensor en particular.</p></div> +<div class="imageblock" style="text-align:center;"> +<div class="content"> +<img src="images/CCR_sensor_data_f20.jpg" alt="FIGURA: Gráfico de datos de los sensores del CCR" /> +</div> +</div> +<div class="paragraph"><p>El dato del setpoint puede ser superpuesto sobre los datos de los sensores de +oxígeno activando ambas casillas. Las presiones parciales del nitrógeno y del +helio (en su caso) se muestran de la forma habitual para las inmersiones OC.</p></div> +<div class="paragraph"><p><em>Eventos</em>: Se registran diversos eventos, p.e. los cambios a circuito abierto +de la boquilla. Estos eventos se muestran como triángulos amarillos y, si se +pasa el ratón sobre el icono, se da una descripción del evento en la línea +inferior del <a href="#S_InfoBox">Recuadro de información</a>.</p></div> +<div class="paragraph"><p><em>Presiones de las botellas</em>: Algunos ordenadores de buceo CCR, como el MKVI de +Poseidon, registran las presiones de las botellas de oxígeno y diluyente. Las +presiones de estas dos botellas se muestran como líneas verdes sobre el perfil +de la inmersión. Además, las presiones iniciales y finales de ambas botellas se +muestran en la pestaña <em>Equipo</em>. A continuación, un perfil de inmersión con CCR +incluyendo capas con el setpoint, las lecturas de los sensores de oxígeno y la +información de presión de las botellas. En este caso hay una buena coincidencia +entre las lecturas de los dos sensores de oxígeno.</p></div> +<div class="imageblock" style="text-align:center;"> +<div class="content"> +<img src="images/CCR_dive_profile_f22.jpg" alt="FIGURA: Perfil de inmersión con CCR" /> +</div> +</div> +<div class="paragraph"><p><em>Información especifica del equipo</em>: <em>Subsurface</em> recoge información que puede +ser especifica de un tipo de equipo concreto. Se muestra en la <a href="#S_ExtraDataTab">pestaña Otros Datos</a>. +Puede incluir información de ajustes o metadatos sobre la inmersión.</p></div> +<div class="paragraph"><p>El techo calculado por <em>Subsurface</em> no es muy preciso dado que no se puede +determinar fiablemente la presión de nitrógeno en el circuito desde el divelog +importado del equipo del CCR. Muchos ordenadores de buceo CCR, sin embargo, +informan del techo calculado internamente por ellos mismos y este se mostrará +en el perfil activando el botón correspondiente a la izquierda del perfil:</p></div> +<div class="imageblock"> +<div class="content"> +<img src="images/icons/cceiling.jpg" alt="Icono de techo" /> +</div> +</div> +<div class="paragraph"><p>El color por defecto del techo de deco generado por el ordenador es blanco. Sin +embargo, puede ajustarse a rojo seleccionando la correspondiente casilla en +<em>Archivo → Preferencias → Gráfico</em>. A continuación se muestra un perfil +mostrando el techo deco generado por el ordenador de buceo:</p></div> +<div class="imageblock"> +<div class="content"> +<img src="images/CCR_dive_ceilingF22.jpg" alt="FIGURA: Perfil de inmersión con CCR" /> +</div> +</div> +<div class="paragraph"><p>Se puede encontrar más información, específica para cada ordenador, sobre +como descargar divelogs de CCR en el <a href="#_appendix_b_dive_computer_specific_information_for_importing_dive_information">Apéndice B</a></p></div> +</div> +</div> +</div> +</div> +<div class="sect1"> +<h2 id="_obtener_mas_informacion_sobre_inmersiones_guardadas_en_el_diario">7. Obtener más información sobre inmersiones guardadas en el diario</h2> +<div class="sectionbody"> +<div class="sect2"> +<h3 id="_la_pestana_informacion_para_inmersiones_individuales">7.1. La pestaña Información (para inmersiones individuales)</h3> +<div class="paragraph"><p>La pestaña Información proporciona alguna información resumida +sobre un buceo en particular que ha sido seleccionado en la <strong>Lista de +inmersiones</strong>. La información útil incluye el intervalo en superficie antes de la +inmersión, las profundidades máxima y media, el volumen de gas consumido, el +C.A.S. (consumo de aire en superficie) y el número de unidades de toxicidad de +oxígeno (OTU) en las que se ha incurrido.</p></div> +<div class="admonitionblock"> +<table><tr> +<td class="icon"> +<img src="images/icons/info.jpg" alt="Note" /> +</td> +<td class="content">Consumo de gas y cálculos de CAS: <em>Subsurface</em> calcula el CAS y el consumo de gas +teniendo en cuenta la incompresibilidad de los gases, particularmente a +presiones en las botellas superiores a 200 bar, haciéndolos más precisos. Los +usuarios deberían consultar el <a href="#SAC_CALCULATION">Apéndice F</a> para más información.</td> +</tr></table> +</div> +</div> +<div class="sect2"> +<h3 id="S_ExtraDataTab">7.2. La pestaña <strong>Otros datos</strong> (para inmersiones individuales)</h3> +<div class="paragraph"><p>Cuando se utiliza un ordenador de buceo, a menudo facilita determinadas +informaciones que no pueden presentarse de forma estandarizada ya que la +naturaleza de la información varía de un ordenador a otro. Estos datos suelen +comprender informaciones de ajustes, metadatos sobre una inmersión, niveles de +batería, tiempos de "no vuelo" o factores de gradiente usados durante el buceo. +Si es posible, toda esta información se presenta en la pestaña <strong>Otros datos</strong>. A +continuación hay una imagen que muestra otros datos para un buceo con un +rebreather Poseidon.</p></div> +<div class="imageblock" style="text-align:center;"> +<div class="content"> +<img src="images/ExtraDataTab_f20.jpg" alt="FIGURA: Pestaña Otros datos" /> +</div> +</div> +</div> +<div class="sect2"> +<h3 id="_la_pestana_estadisticas_para_grupos_de_inmersiones">7.3. La pestaña Estadísticas (para grupos de inmersiones)</h3> +<div class="paragraph"><p>La pestaña Estadísticas facilita información resumida para más de una inmersión, +suponiendo que se haya seleccionado más de un buceo en la <strong>Lista de inmersiones</strong> +tcon los estándares "Ctrl+clic" o "Shift+clic" del ratón. Si solo se ha +seleccionado una los cálculos se efectuarán solo para esa inmersión. Esta +pestaña muestra el número de inmersiones seleccionadas, el tiempo total de buceo +para estas inmersiones, así como los máximos, mínimos y medios para la duración, +profundidad, temperatura en agua y superficie y CAS. También muestra la +profundidad máxima de las inmersiones más profunda y más superficial de las +seleccionadas.</p></div> +</div> +<div class="sect2"> +<h3 id="S_DiveProfile">7.4. El Perfil de inmersión</h3> +<div class="imageblock" style="text-align:center;"> +<div class="content"> +<img src="images/Profile2.jpg" alt="Típico perfil de buceo" /> +</div> +</div> +<div class="paragraph"><p>De todos los paneles de <em>Subsurface</em>, el Perfil contiene la información más +detallada de cada inmersión. El perfil de inmersión tiene una <strong>barra de botones</strong> +en el lado izquierdo que permite controlar varias opciones. Las funciones de +estos botones se describen más adelante. El objeto principal del perfil de +inmersión es el gráfico de profundidad en función del tiempo. Además de la +información obvia acerca de la profundidad, también muestra los ratios de +ascenso y descenso en relación a las velocidades de ascenso y descenso +recomendadas. Esta información se proporciona utilizando diferentes colores:</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>Color</strong></p></td> +<td align="left" valign="top"><p class="table"><strong>Velocidad de descenso (m/min)</strong></p></td> +<td align="left" valign="top"><p class="table"><strong>Velocidad de ascenso (m/min)</strong></p></td> +</tr> +<tr> +<td align="left" valign="top"><p class="table">Rojo</p></td> +<td align="left" valign="top"><p class="table">> 30</p></td> +<td align="left" valign="top"><p class="table">> 18</p></td> +</tr> +<tr> +<td align="left" valign="top"><p class="table">Naranja</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">Amarillo</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">Verde claro</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">Verde oscuro</p></td> +<td align="left" valign="top"><p class="table">< 1.5</p></td> +<td align="left" valign="top"><p class="table">< 1.5</p></td> +</tr> +</tbody> +</table> +</div> +<div class="paragraph"><p>El perfil también incluye lecturas de profundidad para los picos y valles del +gráfico. De esta forma, se debe poder visualizar la profundidad del punto más +hondo y otros picos. La profundidad media se muestra como una línea gris que +indica la profundidad media en cada momento de la inmersión.</p></div> +<div class="admonitionblock"> +<table><tr> +<td class="icon"> +<img src="images/icons/scale.jpg" alt="Note" /> +</td> +<td class="content">En algunos casos el perfil de inmersión no llena el área completa del panel. +Hacer clic en el botón Escala de la barra de herramientas de la izquierda, +habitualmente, incrementa el tamaño del perfil hasta llenar el área de forma +eficiente</td> +</tr></table> +</div> +<div class="paragraph"><p><strong>La temperatura del agua</strong> se muestra con su propia línea azul con valores +situados junto a cambios significativos.</p></div> +<div class="paragraph"><p>El perfil de inmersión puede incluir <strong>gráficos de presiones parciales</strong> de O2, N2 +y He durante el buceo (ver la figura anterior) así como techos de deco +calculados por <em>Subsurface</em> o registrados por el ordenador de buceo (solo +visibles para buceos profundos, largos o repetitivos). La presión parcial del +oxígeno se indica en verde, la del nitrógeno en negro y la del helio en rojo +oscuro. Estos gráficos de presiones parciales se muestran bajo los datos de +perfil.</p></div> +<div class="admonitionblock"> +<table><tr> +<td class="icon"> +<img src="images/icons/O2.jpg" alt="Note" /> +</td> +<td class="content">Clicar este botón permite visualizar la presión parcial de oxígeno durante la +inmersión. Se dibuja bajo los gráficos de profundidad y temperatura.</td> +</tr></table> +</div> +<div class="admonitionblock"> +<table><tr> +<td class="icon"> +<img src="images/icons/N2.jpg" alt="Note" /> +</td> +<td class="content">Clicar este botón permite visualizar la presión parcial de nitrógeno durante la +inmersión.</td> +</tr></table> +</div> +<div class="admonitionblock"> +<table><tr> +<td class="icon"> +<img src="images/icons/He.jpg" alt="Note" /> +</td> +<td class="content">Clicar este botón permite visualizar la presión parcial de helio durante la +inmersión. Esto solo es interesante para buceadores que usen trimix, helitrox o +mezclas respiratorias similares.</td> +</tr></table> +</div> +<div class="paragraph"><p>El gráfico de <strong>consumo de gas</strong> muestra la presión de la botella y su variación +durante la inmersión. El consumo de gas tiene en cuenta la profundidad, de +manera que, incluso cuando introduces manualmente las presiones inicial y final, +el gráfico no es una línea recta. Al igual que el gráfico de profundidad, la +pendiente de la presión de la botella facilita información acerca del CAS +momentáneo, si se está usando ordenador con gas integrado. Aquí el color no se +refiere a valores absolutos, sino que se calcula en relación a la media +normalizada de aire consumido durante este buceo. Así pues, las áreas en rojo o +naranja indican momentos de consumo por encima de la media mientras que el verde +oscuro indicará momentos de consumo de gas por debajo de la media.</p></div> +<div class="admonitionblock"> +<table><tr> +<td class="icon"> +<img src="images/icons/Heartbutton.png" alt="Note" /> +</td> +<td class="content">Hacer clic en el botón de ritmo cardiaco permitirá mostrar información de este +parámetro durante la inmersión si el ordenador de buceo tiene conectado un +sensor de ritmo cardiaco.</td> +</tr></table> +</div> +<div class="paragraph"><p>Es posible <strong>hacer zoom</strong> en el gráfico del perfil. Se puede hacer con la rueda +del ratón o el gesto equivalente en el trackpad. Por defecto, <em>Subsurface</em> +siempre muestra un área suficientemente grande para mostrar al menos 30 minutos +y 30 metros – de esta forma, las inmersiones cortas o superficiales se reconocen +a simple vista; algo que a los apneístas les trae claramente sin cuidado.</p></div> +<div class="imageblock" style="text-align:center;"> +<div class="content"> +<img src="images/MeasuringBar.png" alt="FIGURE: Barra de medidas" /> +</div> +</div> +<div class="admonitionblock"> +<table><tr> +<td class="icon"> +<img src="images/icons/ruler.jpg" alt="Note" /> +</td> +<td class="content">Pueden hacerse <strong>medidas de profundidad o tiempo</strong> utilizando el botón <strong>regla</strong> de +la izquierda del perfil La medición se hace arrastrando los puntos rojos a los +dos puntos del perfil entre los que deseas medir. La información se facilita en +el área blanca horizontal bajo los dos puntos.</td> +</tr></table> +</div> +<div class="admonitionblock"> +<table><tr> +<td class="icon"> +<img src="images/icons/ShowPhotos_f20.png" alt="Note" /> +</td> +<td class="content">Las fotografías que se han añadido a una inmersión pueden mostrarse en el perfil +seleccionando el botón <strong>Mostrar foto</strong> en la barra de herramientas a la izquierda +del perfil. La posición de la foto en el perfil indica la hora exacta a la que +se tomó. Si el botón no está activado, las fotos permanecen ocultas.</td> +</tr></table> +</div> +<div class="paragraph"><p>El perfil de buceo también puede incluir el <strong>techo</strong> registrado por el ordenador +de buceo (o, más precisamente, la parada deco más profunda que el ordenador de +buceo calcule para cada momento en el tiempo) como una capa roja en el perfil de +la inmersión. Los techos de ascenso surgen cuando un ascenso directo a +superficie incrementa el riesgo de que el buzo sufra enfermedad descompresiva +(ED) y se necesita ascender más despacio, o efectuar paradas de descompresión +antes de subir a la superficie. No todos los ordenadores de buceo guardan esta +información y posibilitan su descarga; por ejemplo todos los ordenadores Suunto +carecen de la posibilidad de facilitar estos datos tan útiles a los softwares de +registro de inmersiones. <em>Subsurface</em> también calcula los techos +independientemente, mostrándolos como una capa verde sobre el perfil. A causa de +las diferencias en los algoritmos utilizados y la cantidad de datos disponibles +(y otros factores tomados en consideración en el momento de los cálculos) es +improbable que los techos de los ordenadores de buceo y de <em>Subsurface</em> sean los +mismos, incluso si se utilizan el mismo algoritmo y los mismos factores de +gradiente (ver más adelante). También es bastante común que <em>Subsurface</em> calcule +un techo cuando el ordenador permaneció en modo no deco durante la inmersión +completa (representada por la sección <span class="green">verde oscuro</span> del perfil). Esto se +debe al hecho de que los cálculos de <em>Subsurface</em> describen la obligación de +descompresión en ese punto del tiempo durante la inmersión, mientras los +ordenadores de buceo habitualmente, tienen en cuenta el ascenso que va a venir. +Durante el ascenso parte del exceso de nitrógeno (y posiblemente de helio) ya se +ha eliminado a través de la respiración por lo que, aunque el buceador +técnicamente encontrara un techo, la inmersión aún no requiere explícitamente +una parada de descompresión. Esta característica permite a los ordenadores de +buceo ofrecer tiempos de fondo más largos.</p></div> +<div class="admonitionblock"> +<table><tr> +<td class="icon"> +<img src="images/icons/cceiling.jpg" alt="Note" /> +</td> +<td class="content">Si el propio ordenador de buceo calcula un techo y lo pone a disposición de +<em>Subsurface</em> durante la descarga de inmersiones, puede ser mostrado como un +árearoja seleccionando el botón <strong>Mostrar techo informado por el ordenador</strong> del +panel de perfil.</td> +</tr></table> +</div> +<div class="admonitionblock"> +<table><tr> +<td class="icon"> +<img src="images/icons/ceiling1.jpg" alt="Note" /> +</td> +<td class="content">Si hacemos clic en el botón <strong>Mostrar techo calculado</strong> por <em>Subsurface</em> del panel +del perfil, se muestra en verde este techo, si existe, para una inmersión en +particular (<strong>A</strong> en la figura a continuación). Este ajuste puede modificarse de +dos maneras:</td> +</tr></table> +</div> +<div class="admonitionblock"> +<table><tr> +<td class="icon"> +<img src="images/icons/ceiling2.jpg" alt="Note" /> +</td> +<td class="content">Si, además, se selecciona el botón <strong>Calcular todos los tejidos</strong> del panel de +perfil, se muestra el techo para los distintos tejidos del modelo Bühlman (<strong>B</strong> +en la figura de debajo).</td> +</tr></table> +</div> +<div class="admonitionblock"> +<table><tr> +<td class="icon"> +<img src="images/icons/ceiling3.jpg" alt="Note" /> +</td> +<td class="content">Si, además, se selecciona el botón <strong>Mostrar el techo calculado con incrementos +de 3m</strong> entonces el techo se muestra con saltos de 3 en 3 metros.</td> +</tr></table> +</div> +<div class="imageblock" style="text-align:center;"> +<div class="content"> +<img src="images/Ceilings2.jpg" alt="Figura: Techo con resolución de 3 metros" /> +</div> +</div> +<div class="admonitionblock"> +<table><tr> +<td class="icon"> +<img src="images/icons/ShowCylindersButton.jpg" alt="Note" /> +</td> +<td class="content">Al seleccionar este icono, los diferentes gases utilizados durante una inmersión +se presentarán en forma de barras de colores en la parte de abajo del perfil. En +general, el oxígeno se presenta con una barra verde, el nitrógeno con una barra +amarilla y el helio con una barra roja. La imagen a continuación muestra un buceo +que primero utiliza una botella de trimix (rojo y verde), seguida por un cambio a +una botella de nitrox (amarillo y verde) tras 23 minutos. Las botellas con aire +se muestran con una barra azul claro.</td> +</tr></table> +</div> +<div class="imageblock" style="text-align:center;"> +<div class="content"> +<img src="images/ShowCylinders_f20.jpg" alt="Figura: Gráfico de uso de botellas" /> +</div> +</div> +<div class="admonitionblock"> +<table><tr> +<td class="icon"> +<img src="images/tissues.jpg" alt="Note" /> +</td> +<td class="content">Muestra presiones de los gases inertes en los tejidos, en relación con la +presión ambiental (línea gris horizontal). +Las presiones en los tejidos se calculan utilizando el algoritmo Bühlmann ZH-16 +y se muestran como líneas de colores que varían desde el verde (tejidos rápidos) +al azul (tejidos más lentos). +La línea negra, dibujada sobre la presión ambiental, es la máxima sobresaturación +de tejidos permitida, en la que se incluyen los factores de gradiente que se +establecieron en <em>Preferencias</em>. Para buceadores que hacen buceo con descompresión +planificada, se obtienen ritmos de desaturación eficientes manteniendo los tejidos +entre la presión ambiental de los gases inertes (línea gris) y la presión límite +(línea negra). Lo que se muestra en pantalla es una representación de la presión +en los tejidos durante toda la inmersión. En contraste, el +<a href="#S_gas_pressure_graph">Gráfico de presión de gases</a> de la ventana <strong>Información</strong> +del <strong>Perfil</strong> es un reflejo de las presiones de los tejidos en el instante de +tiempo señalado por la posición del cursor sobre el perfil de la inmersión.</td> +</tr></table> +</div> +<div class="imageblock" style="text-align:center;"> +<div class="content"> +<img src="images/tissuesGraph.jpg" alt="Figura: Gráfico de presión de gases inertes en los tejidos" /> +</div> +</div> +<div class="paragraph"><p>El ajuste de los factores de gradiente afecta mucho a los techos calculados y +sus profundidades. Para más información acerca de factores de gradiente, +consultar la sección <a href="#S_GradientFactors">Ajuste de preferencias de factores de gradiente</a>. +Los factores de gradiente que se están utilizando(p.e. 35/75) +aparecen sobre el gráfico de profundidad si se activan los botones adecuados de +la barra de herramientas. +<strong>N.B.</strong>: Los factores de gradiente indicados NO son los utilizados por el +ordenador de buceo, sino los que utiliza <em>Subsurface</em> para calcular las +obligaciones descompresivas durante la inmersión. Para una explicación más +detallada de los factores de gradiente, consultar los siguientes links:</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="_el_menu_contextual_del_perfil_de_inmersion">7.5. El menú contextual del Perfil de Inmersión</h3> +<div class="paragraph"><p>Se accede al menú contextual del Perfil de Inmersión haciendo clic-derecho +mientras el cursor del ratón está sobre el panel del Perfil de Inmersión. El +menú permite la creación de marcadores, eventos de cambio de gas o cambios +manuales en setpoint de un CCR, aparte de los que se hayan podido importar del +ordenador de buceo. Las marcas se sitúan contra la línea de profundidad del +perfil y con el tiempo fijado donde estaba el cursor cuando el botón derecho +se clicó para desplegar el menú. Los eventos de cambio de gas suponen una +selección sobre el gas al que estamos cambiando, habiendo sido definida la lista +de posibilidades en la pestaña <strong>Equipo</strong>. Los eventos de cambio de setpoint +abren un diálogo en el que se permite elegir el valor del próximo setpoint. Como +en el planificador, un setpoint cero indica que el buceador está respirando en +circuito abierto, mientras cualquier valor diferente de cero indica el uso de +circuito cerrado. Si hacemos clic-derecho mientras estamos sobre +un marcador preexistente, el menú se extiende añadiendo opciones para permitir +el borrado del marcador o permitir ocultar todos los marcadores de ese tipo.</p></div> +</div> +<div class="sect2"> +<h3 id="S_InfoBox">7.6. El <strong>Recuadro Información</strong></h3> +<div class="paragraph"><p>El recuadro de Información muestra una amplia gama de información del <strong>perfil de +inmersión</strong>. Normalmente el recuadro se situa en la parte de arriba a la +izquierda del panel <strong>Perfil de Inmersión</strong>. Si el ratón apunta fuera del panel, +solo es visible la linea superior del recuadro (ver figura (<strong>A</strong>) abajo). El +recuadro puede moverse en el panel <strong>Perfil de Inmersión</strong> pulsando y +arrastrándolo con el ratón de forma que no cubra detalles importantes. La +posición del recuadro queda guardada y se usará de nuevo en los siguientes +análisis.</p></div> +<div class="imageblock" style="text-align:center;"> +<div class="content"> +<img src="images/InfoBox2.jpg" alt="Figura: Recuadro de Información" /> +</div> +</div> +<div class="paragraph"><p>En el momento en que el ratón apunta dentro del panel <strong>Perfil de Inmersión</strong>, el +recuadro de información se expande y muestra varios detalles de datos. En esta +situación, los datos reflejan el punto temporal a lo largo del perfil indicado +por el cursor del ratón (ver la parte derecha de la figura (<strong>B</strong>) anterior donde +el recuadro refleja la información en la posición de la [flecha] del cursor en +esa imagen). Por lo tanto, mover el cursor en dirección horizontal permite que +el recuadro muestre información para cualquier punto a lo largo del perfil.</p></div> +<div class="paragraph"><p>En este modo, el recuadro de información da extensas estadísticas sobre la +profundidad, el gas y el techo de la inmersión. Entre ellas se incluyen: el +lapso de tiempo en el buceo (indicado con @), la profundidad (Prof), la presión +de la botella (Pres), la temperatura, la velocidad de ascenso/descenso, el +consumo de aire en superficie (CAS), la presión parcial de oxígeno, la +profundidad máxima operativa (PMO), la profundidad equivalente al aire (PEA), la +profundidad narcótica equivalente (PNE), la densidad equivalente al aire (EADD), +los requisitos descompresivos en ese momento del tiempo (Deco), el tiempo hasta +la superficie (TTS), el techo calculado, así como el techo calculado para varios +compartimentos de tejidos Bühlmann.</p></div> +<div class="paragraph"><p>El usuario tiene control sobre como se muestran varias estadísticas, +representadas en cuatro de los botones a la izquierda del panel del perfil. +Son:</p></div> +<div class="admonitionblock"> +<table><tr> +<td class="icon"> +<img src="images/icons/MOD.jpg" alt="Note" /> +</td> +<td class="content">Activar este botón hace que el Recuadro de Información muestre la <strong>Profundidad +máxima operativa (PMO)</strong> de la inmersión para la mezcla de gases utilizada. La +PMO depende de la concentración de oxígeno en el gas respirado. Para el aire +(21% de oxígeno) se sitúa alrededor de 57 m si se ha especificado una pO<sub>2</sub> +máxima de 1.4 en la sección <strong>Preferencias</strong>. Por debajo de la PMO existe un +riesgo muy elevado de exposición a los peligros asociados con la toxicidad del +oxígeno.</td> +</tr></table> +</div> +<div class="admonitionblock"> +<table><tr> +<td class="icon"> +<img src="images/icons/NDL.jpg" alt="Note" /> +</td> +<td class="content">Activar este botón hace que el recuadro Información muestre, bien el <strong>Límite +de no descompresión (LND)</strong> o el <strong>*Tiempo total hasta superficie (TTS)</strong>. El +LND es el tiempo que un buzo puede permanecer sumergido a la profundidad actual +sin requerir descompresión (esto es, sin que aparezca un techo para el ascenso). +Una vez que se ha excedido el LND y se requiere descompresión, el TTS incluirá +el total de minutos requeridos antes de que el buceador pueda salir a superficie. +El TTS incluye el tiempo de ascenso y las paradas de descompresión. Se calcula +suponiendo que se usa el gas actual. Incluso si el perfil incluye varios +cambios de gas, el TTS en un momento dado de la inmersión se habrá calculado +con el gas en uso en ese momento. Para TTS superiores a 2 horas, no se calcula +con precisión y simplemente se indica <em>TTS > 2h</em>.</td> +</tr></table> +</div> +<div class="admonitionblock"> +<table><tr> +<td class="icon"> +<img src="images/icons/SAC.jpg" alt="Note" /> +</td> +<td class="content">Activar este botón hace que el Recuadro de información muestre el <strong>Consumo de +aire en superficie (CAS)</strong>. El CAS es un indicador del ritmo respiratorio del +buceador calculado a nivel del mar. El valor del CAS es inferior al real ya que +un buceador a 10m usa aproximadamente el doble del que consume en superficie. El +SAC da una indicación del ritmo de consumo de gas independientemente de la +profundidad de la inmersión de forma que se pueden comparar los ritmos de +diferentes inmersiones. Las unidades del CAS son litros/min o pies^3/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">Activar este botón hace que el Recuadro de información muestre la <strong>Profundidad +equivalente al aire (PEA)</strong> para los buceos con nitrox y la <strong>Profundidad +narcótica equivalente (PNE)</strong> para buceos con trimix. Estas magnitudes son +importantes para buceadores que utilicen mezclas de gases distintas del aire. +Sus valores dependen de la composición del gas respirado. La PEA es la +profundidad de un hipotético buceo con aire que tenga la misma presión parcial +de nitrógeno que la inmersión con nitrox actual. Una inmersión con nitrox +conllevaría una obligación de descompresión igual que una inmersión con aire a +una profundidad igual a la PEA. La PNE es la profundidad de una hipotética +inmersión con aire que tenga la misma suma de presiones parciales de gases +narcóticos (oxígeno y nitrógeno) que la actual inmersión con trimix. Un buceador +con trimix puede esperar los mismos efectos narcóticos que un buceador +respirando aire a una profundidad igual a la PNE.</td> +</tr></table> +</div> +<div class="paragraph"><p>La figura (<strong>B</strong>) anterior muestra un Recuadro de Información con un conjunto de +datos casi completo.</p></div> +<div class="sect3"> +<h4 id="S_gas_pressure_graph">7.6.1. El gráfico de barras de presión de gases</h4> +<div class="paragraph"><p>A la izquierda del <strong>Recuadro de Información</strong> hay un gráfico de barras vertical +que indica las presiones de los gases inertes que el buceador estaba respirando +<em>en un momento dado de la inmersión</em>, señalado por la posición del cursor sobre +el <strong>Perfil de inmersión</strong>. La figura abajo a la izquierda indica el significado +de las diferentes partes del gráfico de barras.</p></div> +<div class="imageblock" style="text-align:center;"> +<div class="content"> +<img src="images/GasPressureBarGraph.jpg" alt="FIGURE:Gráfico de barras de presiones de gases" /> +</div> +</div> +<div class="ulist"><ul> +<li> +<p> +El área verde claro indica el gas total, con el margen superior de esta zona + indicando la presión total de gas inhalada por el buceador y medida desde el + fondo del gráfico a la parte superior. Esta presión tiene un valor <em>relativo</em> + en el gráfico y no indica presión absoluta. +</p> +</li> +<li> +<p> +La línea negra horizontal por debajo de la zona verde claro indica la presión de + equilibrio de los gases inertes respirados, habitualmente nitrógeno. En el caso + del trimix, es la presión combinada del helio y el nitrógeno. En este ejemplo, + el usuario esta buceando con EAN32, por lo tanto la presión del gas inerte está + al 68% de la distancia desde el fondo del gráfico hasta el valor de la presión + total. +</p> +</li> +<li> +<p> +La zona verde oscura en la parte baja del gráfico representa las presiones de + los gases inertes en cada uno de los 16 compartimentos de tejidos, según el + algoritmo de Bühlmann, estando los tejidos rápidos en el lado izquierdo. +</p> +</li> +<li> +<p> +La línea horizontal negra superior indica el factor de gradiente que se aplica + a la profundidad del buceador para el punto concreto del <strong>Perfil de Inmersión</strong>. + Este factor de gradiente es una interpolación entre el GFbajo y el GFalto que + se hayan especificado en la pestaña Gráfico del <strong>Panel de preferencias</strong> de + <em>Subsurface</em>. +</p> +</li> +<li> +<p> +El margen inferior de la zona roja del gráfico indica el valor M derivado de + Bühlman, o sea el valor de la presión de gases inertes a partir de la cual la + formación de burbujas se espera que sea severa, resultando en una enfermedad + descompresiva. +</p> +</li> +</ul></div> +<div class="paragraph"><p>Estos cinco valores se indican a la izquierda en la figura anterior. La forma +en que el gráfico de barras cambia durante una inmersión, se representa en el +lado derecho de la figura anterior, para un buceador usando EAN32.</p></div> +<div class="ulist"><ul> +<li> +<p> +El gráfico <strong>A</strong> indica la situación al inicio de una inmersión, con el buzo + en superficie. Las presiones en los compartimentos de tejidos todavía están + a la presión de equilibrio ya que aún no se ha buceado. +</p> +</li> +<li> +<p> +El gráfico <strong>B</strong> indica la situación tras un descenso a 30 metros. Pocos de + los compartimentos de tejidos han tenido tiempo de responder al descenso, las + presiones de los gases muy por debajo de presión de equilibrio. +</p> +</li> +<li> +<p> +El gráfico <strong>C</strong> representa las presiones tras 30 minutos a 30 metros. Los + compartimentos rápidos han llegado al equilibrio (p.e. han alcanzado la altura + de la línea negra que indica la presión de equilibrio). Los compartimentos más + lentos (hacia la derecha) no han alcanzado el equilibrio y están en proceso de + incrementar lentamente la presión. +</p> +</li> +<li> +<p> +El gráfico <strong>D</strong> muestra las presiones tras ascender a una profundidad de 4.5 + metros. Ya que, durante el ascenso, la presión total del gas inhalado ha caído + mucho, de 4 bares a 1.45 bares, las presiones en los diferentes compartimentos + de tejidos sobrepasan la presión total del gas y se aproximan al factor de + gradiente (la línea negra superior en la imagen). Continuar el ascenso haría + que rebasáramos el valor del factor de gradiente (GFalto), poniendo en peligro + al buceador. +</p> +</li> +<li> +<p> +El gráfico <strong>E</strong> indica la situación después de permanecer a 4.5 metros durante + 10 minutos. Los compartimentos rápidos han bajado su presión. Como era de + esperar, las presiones en los compartimentos lentos no han variado mucho. Las + presiones en los compartimentos rápidos ya no se acercan al valor de GFalto y + el buceador está más seguro que en la situación expuesta en el gráfico <strong>D</strong>. +</p> +</li> +</ul></div> +</div> +</div> +</div> +</div> +<div class="sect1"> +<h2 id="_organizar_el_registro_manipular_grupos_de_inmersiones">8. Organizar el registro (Manipular grupos de inmersiones)</h2> +<div class="sectionbody"> +<div class="sect2"> +<h3 id="_el_menu_contextual_de_la_lista_de_inmersiones">8.1. El menú contextual de la Lista de Inmersiones</h3> +<div class="paragraph"><p>Varias acciones sobre, bien una inmersión, bien un grupo de ellas, se pueden +efectuar utilizando el Menú Contextual de la Lista de inmersiones, al que se +accede seleccionando una inmersión o un grupo de ellas y haciendo clic-derecho.</p></div> +<div class="imageblock" style="text-align:center;"> +<div class="content"> +<img src="images/ContextMenu.jpg" alt="Figura: Menú contextual" /> +</div> +</div> +<div class="paragraph"><p>El menú contextual se usa en muchas de las acciones que se describen a +continuación.</p></div> +<div class="sect3"> +<h4 id="_personalizar_las_columnas_mostradas_en_el_panel_strong_lista_de_inmersiones_strong">8.1.1. Personalizar las columnas mostradas en el panel <strong>Lista de inmersiones</strong></h4> +<div class="imageblock" style="text-align:center;"> +<div class="content"> +<img src="images/DiveListOptions.jpg" alt="Ejemplo: Opciones de la Lista de inmersiones" /> +</div> +</div> +<div class="paragraph"><p>La información por defecto de la <strong>Lista de inmersiones</strong> incluye, para cada buceo, +Numero de inmersión, Fecha, Calificación, Profundidad, Duración y Ubicación. Esta +información puede controlarse y cambiarse haciendo clic derecho sobre la barra de +encabezamiento de la <strong>Lista de inmersiones</strong>. Por ejemplo, un clic derecho sobre +la cabecera 'Fecha’despliega una lista de valores que pueden mostrarse (ver la +figura anterior). Si seleccionamos un valor para que se muestre o desaparezca de +la lista, esta se actualiza inmediatamente. Las preferencias para la información +que muestre la lista se guardan y reutilizan cada vez que se abre <em>Subsurface</em>.</p></div> +</div> +<div class="sect3"> +<h4 id="_seleccionar_inmersiones_en_una_ubicacion_concreta">8.1.2. Seleccionar inmersiones en una ubicación concreta</h4> +<div class="paragraph"><p>Muchos buceadores tienen largas listas de inmersiones, y puede resultar difícil +localizar todos los buceos en un punto en concreto. Presionando <em>Ctrl+F</em> en el +teclado se abre una casilla de texto en la parte de arriba a la izquierda de la +<strong>Lista de inmersiones</strong>. Si se teclea el nombre de una ubicación en esta casilla +la <strong>Lista de inmersiones</strong> se filtra inmediatamente para mostrar solo los buceos +en esta ubicación.</p></div> +</div> +</div> +<div class="sect2"> +<h3 id="S_Renumber">8.2. Renumerar las inmersiones</h3> +<div class="paragraph"><p>Las inmersiones normalmente se numeran incrementando desde las no-recientes +(menores números de secuencia) a las más recientes (números de secuencia más +altos). Numerar los buceos no siempre es consistente. Por ejemplo, cuando se +añaden inmersiones antiguas a la lista, la numeración no sigue automáticamente +por ser estas anteriores en fecha/hora a las ya existentes. Por lo tanto, en +ocasiones, se puede necesitar renumerar los buceos. Esto se hace seleccionando +(desde el menú principal) <em>Registro → Renumerar</em>. Se permite elegir el número de +secuencia inferior que se va a usar. Completar esta operación supone obtener +nuevos números de secuencia (basados en fecha/hora) para los buceos del panel +<strong>Lista de Inmersiones</strong>.</p></div> +<div class="paragraph"><p>También se pueden renumerar algunas inmersiones seleccionadas de la lista. Se +seleccionan las inmersiones que necesiten renumerarse. Se hace clic-derecho +sobre la lista seleccionada y se utiliza la lista contextual para efectuar el +renumerado. Aparecerá una ventana solicitando al usuario que especifique el +número de inicio para el proceso de numeración.</p></div> +</div> +<div class="sect2"> +<h3 id="S_Group">8.3. Agrupar las inmersiones en viajes y manipularlos</h3> +<div class="paragraph"><p>Si buceas regularmente, la lista de inmersiones puede hacerse rápidamente muy +larga. <em>Subsurface</em> puede agrupar los buceos en <em>viajes</em>. Lo hace agrupando +inmersiones que tengan fechas/horas que no estén separadas más de dos días y +crea una sola cabecera para cada viaje . Abajo hay una lista de inmersiones no +agrupada (<strong>A</strong>, a la izquierda) y la lista agrupada correspondiente incluyendo +cinco viajes (<strong>B</strong>, a la derecha):</p></div> +<div class="imageblock" style="text-align:center;"> +<div class="content"> +<img src="images/Group2.jpg" alt="Figura: Agrupar inmersiones" /> +</div> +</div> +<div class="paragraph"><p>Agrupar en viajes permite una forma rápida de acceder a buceos individuales sin +tener que pasar por largas listas de inmersiones. Para agrupar los buceos de una +lista de inmersiones (desde el menú principal) se selecciona <em>Registro → +Autoagrupar</em>. El panel Lista de Inmersiones ahora muestra solo los títulos de +los viajes.</p></div> +<div class="sect3"> +<h4 id="_editar_el_titulo_y_la_informacion_asociada_a_un_viaje_en_particular">8.3.1. Editar el título y la información asociada a un viaje en particular</h4> +<div class="paragraph"><p>Normalmente, en la lista de inmersiones se incluye una mínima información en el +título del viaje. Puede añadirse mucha más sobre un viaje seleccionando su +título en la lista. Esto muestra una pestaña <strong>Notas del Viaje</strong> en el panel Notas +de la inmersión. Aquí se puede añadir o editar información sobre dia/hora, +ubicación del viaje, y otros comentarios generales. Al terminar, se selecciona +<strong>Guardar</strong> en los botones de arriba a la derecha en la pestaña Notas del viaje. +El título en la <strong>Lista de inmersiones</strong> debería reflejar ya algo de la +información editada.</p></div> +</div> +<div class="sect3"> +<h4 id="_ver_los_buceos_de_un_viaje_en_concreto">8.3.2. Ver los buceos de un viaje en concreto</h4> +<div class="paragraph"><p>Una vez que las inmersiones agrupadas en viajes, los usuarios pueden expandir +uno o más viajes clicando la punta de flecha a la izquierda del título. Con ello +se expande el viaje mostrando los buceos individuales efectuados.</p></div> +</div> +<div class="sect3"> +<h4 id="_colapsar_o_expandir_informacion_de_diferentes_viajes">8.3.3. Colapsar o expandir información de diferentes viajes</h4> +<div class="paragraph"><p>Tras seleccionar un viaje concreto de la lista, el menú contextual resultante +ofrece varias posibilidades de expandir o contraer buceos incluidos en viajes. +Entre ellas expandir todos los viajes y contraer todos los viajes.</p></div> +</div> +<div class="sect3"> +<h4 id="_mezclar_inmersiones_de_mas_de_un_viaje_en_uno_solo">8.3.4. Mezclar inmersiones de más de un viaje en uno solo</h4> +<div class="paragraph"><p>Tras seleccionar el título de un viaje del panel <strong>Lista de Inmersiones</strong>, el +menú permite mezclar viajes con el viaje de abajo o con el de arriba.</p></div> +</div> +<div class="sect3"> +<h4 id="_separar_un_viaje_en_mas_de_uno">8.3.5. Separar un viaje en más de uno</h4> +<div class="paragraph"><p>Si un viaje incluye diez inmersiones, el usuario puede separar el viaje en dos +(viaje 1: cuatro inmersiones de arriba; viaje 2: seis inmersiones de abajo) +seleccionando y haciendo clic-derecho en las cuatro inmersiones de arriba. El menú +que aparecerá te permite crear un nuevo viaje seleccionando la opción <strong>Crear +nuevo viaje arriba</strong>. Las cuatro inmersiones superiores quedan entonces agrupadas +en un viaje separado. La siguiente figura muestra la selección y el menú a la +izquierda (A), la acción completada a la derecha (B):</p></div> +<div class="imageblock" style="text-align:center;"> +<div class="content"> +<img src="images/SplitDive3a.jpg" alt="FIGURA: Separar un viaje en dos" /> +</div> +</div> +</div> +</div> +<div class="sect2"> +<h3 id="_manipular_inmersiones_individuales">8.4. Manipular inmersiones individuales</h3> +<div class="sect3"> +<h4 id="_borrar_una_inmersion_del_diario">8.4.1. Borrar una inmersión del diario</h4> +<div class="paragraph"><p>Las inmersiones pueden borrarse permanentemente del diario seleccionándolas y +haciendo clic-derecho para mostrar el menú y, entonces, seleccionando <strong>Borrar +inmersión</strong>. Habitualmente esto se hará en casos donde se desee borrar +inmersiones de prueba o buceos de duración extremadamente corta.</p></div> +</div> +<div class="sect3"> +<h4 id="_separar_una_inmersion_de_un_viaje">8.4.2. Separar una inmersión de un viaje</h4> +<div class="paragraph"><p>Se pueden separar inmersiones del viaje al que pertenecen. Para ello se +selecciona y hace clic-derecho en los buceos para mostrar el menú. Luego se +selecciona <strong>Quitar inmersión(es) del viaje</strong>. Las inmersiones que han sido +separadas aparecerán ahora encima o debajo del viaje al que pertenecieron, en +función de la fecha y la hora de la inmersión separada.</p></div> +</div> +<div class="sect3"> +<h4 id="_anadir_una_inmersion_al_viaje_de_arriba">8.4.3. Añadir una inmersión al viaje de arriba</h4> +<div class="paragraph"><p>Las inmersiones seleccionadas pueden moverse del viaje al que pertenecen al +inmediatamente superior al actual. Para ello se selecciona y hace clic-derecho +en los buceos para mostrar el menú, luego se selecciona <strong>Añadir inmersión(es) al +viaje de arriba</strong>.</p></div> +</div> +<div class="sect3"> +<h4 id="_desplazar_la_hora_de_inicio_del_buceo_s">8.4.4. Desplazar la hora de inicio del buceo(s)</h4> +<div class="paragraph"><p>En ocasiones es necesario ajustar la hora de comienzo de una inmersión. Esto +puede aplicarse a situaciones en las que las inmersiones se han efectuado en +diferentes zonas horarias o si el ordenador de buceo tiene mal configurada la +hora. Se selecciona y hace clic-derecho en la inmersión(es) a ajustar. Esto +despliega el menú. Seleccionar <strong>Desplazar horas</strong>. Se especifica el tiempo (en +horas y minutos) en el que deben ajustarse los buceos y se hace clic en la +opción que indica si el ajuste debe ser hacia adelante o hacia atrás.</p></div> +</div> +<div class="sect3"> +<h4 id="_juntar_buceos_en_uno_solo">8.4.5. Juntar buceos en uno solo</h4> +<div class="paragraph"><p>En ocasiones una inmersión se interrumpe brevemente, p.e. si un buceador regresa +a superficie unos pocos minutos, dando como resultado dos o más inmersiones +grabadas por el ordenador y apareciendo como buceos distintos en el panel <strong>Lista +de inmersiones</strong>. Se pueden unir estos buceos en uno solo seleccionando las +correspondientes inmersiones y haciendo clic-derecho para mostrar el menú. +Entonces se selecciona <strong>Mezclar inmersiones seleccionadas</strong>. Puede que sea +necesario editar la información de la inmersión en el panel <strong>Notas</strong> para +reflejar situaciones o condiciones que afecten al buceo +resultante de la fusión. La figura a continuación muestra el perfil de dos +inmersiones que fueron unidas:</p></div> +<div class="imageblock" style="text-align:center;"> +<div class="content"> +<img src="images/MergedDive.png" alt="Ejemplo: Inmersión mezclada" /> +</div> +</div> +</div> +<div class="sect3"> +<h4 id="_deshacer_manipulaciones_de_inmersiones">8.4.6. Deshacer manipulaciones de inmersiones</h4> +<div class="paragraph"><p>Se pueden deshacer o rehacer acciones importantes, de las que se han comentado +anteriormente, sobre inmersiones o viajes. Aquí se incluyen: <em>Borrar inmersión</em>, +<em>Mezclar inmersiones</em>, <em>Renumerar inmersiones</em> y <em>Desplazar hora de buceo</em>. +Para hacerlo, tras haber llevado a cabo cualquiera de estas acciones, se +selecciona <em>Editar</em> desde el <strong>Menú Principal</strong>, lo que presentará un desplegable +con las posibilidades <em>Deshacer</em> y <em>Rehacer</em>.</p></div> +</div> +</div> +<div class="sect2"> +<h3 id="S_Filter">8.5. Filtrar la Lista de Inmersiones</h3> +<div class="paragraph"><p>Los buceos del panel <strong>Lista de inmersiones</strong> pueden filtrarse, esto es, se pueden +seleccionar únicamente algunos de los buceos basándose en sus atributos, p.e. +las etiquetas, el lugar de buceo, el divemaster, compañeros o traje protector. +El filtrado permite, por ejemplo, listar las inmersiones profundas en un punto +determinado o, por el contrario, las inmersiones en cuevas con cierto +compañero.</p></div> +<div class="paragraph"><p>Para abrir el filtrado, seleccionar <em>Registro → Filtrar la lista de inmersiones</em> +desde el menú principal. Esto abrirá el <em>Panel de filtrado</em> en la parte de arriba +de la ventana de <em>Subsurface</em>. Arriba a la derecha del panel se ubican tres +iconos (ver imagen a continuación). +El <em>Panel de filtrado</em> puede reiniciarse (p.e. limpiar todos los filtros +actuales) seleccionando la flecha amarilla. El <em>Panel de filtrado</em> también puede +minimizarse seleccionando la <strong>flecha verde</strong>. Cuando está minimizado solo se +muestran los tres iconos. El panel puede maximizarse clicando el icono que lo +minimizó. El filtro se cierra y reinicia seleccionando el <strong>botón rojo</strong> con la +cruz blanca.</p></div> +<div class="imageblock" style="text-align:center;"> +<div class="content"> +<img src="images/Filterpanel.jpg" alt="Figura: Panel de filtrado" /> +</div> +</div> +<div class="paragraph"><p>Se pueden utilizar cuatro criterios para filtrar la lista de inmersiones: +las etiquetas, las personas (compañeros/divemasters), punto de inmersión y traje +de buceo, cada uno de los cuales viene representado por una lista seleccionable. +Sobre cada lista hay un segundo nivel de filtrado. Por ejemplo, tecleando "<em>Ba</em>" +en la casilla de texto sobre las ubicaciones, la lista podría quedar reducida a +"<em>Bajo Piles I</em>", "<em>Bajo Piles II</em>" y "<em>Bajo de Testa</em>". Filtrar la lista +permite encontrar rápidamente términos de búsqueda para filtrar la lista de +inmersiones.</p></div> +<div class="paragraph"><p>Para activar el filtrado de la lista de inmersiones, se necesita seleccionar +al menos una casilla en una de las cuatro listas. La lista de inmersiones se +reduce para mostrar solo los buceos que cumplen los criterios seleccionados en +las listas. Las cuatro listas funcionan como un filtro con operadores <em>Y</em>, +<em>Subsurface</em> filtraría, pues, para "<em>cueva</em>" como etiqueta y "<em>José García</em>" +como compañero; pero los filtros dentro de una categoría son inclusivos, esto +es, filtrar por etiquetas con "cueva" y "barco" mostraría todas las inmersiones +en las que aparezcan las etiquetas "cueva" <em>O</em> "barco", solas o conjuntamente.</p></div> +</div> +</div> +</div> +<div class="sect1"> +<h2 id="S_ExportLog">9. Exportar el registro de inmersiones o parte del mismo</h2> +<div class="sectionbody"> +<div class="paragraph"><p>Hay dos posibilidades de exportar información de buceo desde <em>Subsurface</em>:</p></div> +<div class="ulist"><ul> +<li> +<p> +Exportar información de buceo a <em>Facebook</em> +</p> +</li> +<li> +<p> +<a href="#S_Export_other">Exportar información de buceo a otros destinos o formatos</a> +</p> +</li> +</ul></div> +<div class="sect2"> +<h3 id="S_facebook">9.1. Exportar información de buceo a <em>Facebook</em></h3> +<div class="paragraph"><p>La exportación de inmersiones a <em>Facebook</em> se maneja de forma diferente a otros +tipos de exportación porque se requiere una +conexión a esta red social y se necesita un usuario de <em>Facebook</em> y su password. +Si, desde el menú principal, seleccionamos <em>Archivo → Preferencias → +Facebook</em>, se nos presentará una pantalla de acceso (ver imagen <strong>A</strong> de la +izquierda a continuación). Introducimos nuestro usuario y password de +<em>Facebook</em>. Una vez que nos hemos conectado a <em>Facebook</em>, se nos presenta el +panel de la imagen <strong>B</strong> a continuación, donde se incluye un botón <em>Desconectar</em> +para cerrar la conexión a <em>Facebook</em>.</p></div> +<div class="imageblock" style="text-align:center;"> +<div class="content"> +<img src="images/facebook1_f20.jpg" alt="Figure: Acceso a Facebook" /> +</div> +</div> +<div class="paragraph"><p>Desde la ventana de <em>Subsurface</em> es fácil saber si se tiene una conexión válida +con <em>Facebook</em>. Desde el <strong>Menú principal</strong>, selecciona <em>Compartir → Facebook</em> +(ver imagen <strong>A</strong> a continuación. Normalmente la opción <em>Facebook</em> está +desactivada, pero, si hay una conexión establecida, la opción está activa y +puede ser selecciionada. +Tras haber establecido una conexión con <em>Facebook</em>, transferir un perfil de +inmersión a nuestro perfil de <em>Facebook</em> es sencillo.</p></div> +<div class="paragraph"><p>Asegúrate de que la inmersión que quieres transferir al historial +es la que se muestra en el panel <strong>Perfil de la inmersión</strong>. Si se pulsa +<em>Compartir → Facebook</em> desde el <strong>Menú principal</strong> aparecerá un diálogo en el +que se definirá la cantidad de información adicional que se desea transferir +al historial junto con el perfil (ver imagen <strong>B</strong>, a continuación). Se necesita +proporcionar el nombre de un álbum de <em>Facebook</em> para poder enviar el perfil de +inmersión. Las casillas seleccionables de la izquierda nos permiten seleccionar +la información que vamos a enviar. Esta información se muestra en la ventana de +texto de la derecha (ver imagen <strong>B</strong> a continuación). El mensaje que se va a +enviar se puede editar directamente en esta ventana de texto. Tras haber elegido +la información y verificado lo que se va a subir, se selecciona el botón <em>OK</em> +lo que inicia la transferencia a <em>Facebook</em>. Unos momentos después aparecerá +un mensaje indicando una transferencia correcta.</p></div> +<div class="paragraph"><p>El álbum creado y el post al historial se marcarán como privados. Para que +los amigos puedan ver el post habrá que cambiar los permisos desde un acceso +normal a <em>Facebook</em> desde un navegador o desde la app de <em>Facebook</em>. Aunque +esto suponga un paso de más, los desarrolladores entienden que esta es la mejor +solución para evitar subidas no deseadas en el historial público.</p></div> +<div class="imageblock" style="text-align:center;"> +<div class="content"> +<img src="images/facebook2_f20.jpg" alt="Figure: Facebook login" /> +</div> +</div> +<div class="paragraph"><p>Si se considera necesario, cierra la conexión a <em>Facebook</em>, bien cerrando +<em>Subsurface</em> o bien seleccionando <em>Archivo → Preferencias → Facebook</em> desde +el menú principal, clicando el botón correspondiente en el panel <em>Facebook</em>.</p></div> +</div> +<div class="sect2"> +<h3 id="S_Export_other">9.2. Exportar información de buceo a otros destinos o formatos</h3> +<div class="paragraph"><p>Para exportar a otros destinos, +se llega a la función de exportación seleccionando <em>Archivo → Exportar</em> lo que +despliega el diálogo de exportación. Este diálogo siempre ofrece dos opciones: +guardar TODAS las inmersiones, o guardar solo las inmersiones seleccionadas en +el panel <strong>Lista de Inmersiones</strong> de <em>Subsurface</em>. Marca la casilla seleccionable +apropiada (ver imagen a continuación).</p></div> +<div class="imageblock" style="text-align:center;"> +<div class="content"> +<img src="images/Export_f20.jpg" alt="Figura: Diálogo de exportación" /> +</div> +</div> +<div class="paragraph"><p>Un registro de buceo puede guardarse en tres formatos:</p></div> +<div class="ulist"><ul> +<li> +<p> +Formato XML de <em>Subsurface</em>. Es el formato usado nativamente por <em>Subsurface</em>. +</p> +</li> +<li> +<p> +Universal Dive Data format (UDDF). Ver <a href="http://uddf.org">http://uddf.org</a> para más información. + UDDF es un formato genérico que permite la comunicación entre muchos ordenadores + de buceo y programas de de ordenador. +</p> +</li> +<li> +<p> +<em>Divelogs.de</em>, un registro de inmersiones basado en internet. Para enviar + buceos a <em>Divelogs.de</em>, se necesita un usuario y una password de <em>Divelogs.de</em>. + Hay que registrarse en <em>htttp://es.divelogs.de</em> y suscribir el servicio para + poder enviar datos de inmersiones desde <em>Subsurface</em>. +</p> +</li> +<li> +<p> +<em>DiveShare</em> es también un repositorio de inmersiones basado en internet que se + dirige a inmersiones recreativas. Para subir inmersiones se necesita una + identificación de usuario, por lo que es necesario registrase en <em>http://scubadiveshare.com</em>. +</p> +</li> +<li> +<p> +<em>Detalles de inmersión CSV</em>, que incluye la información más crítica del perfil de la + inmersión. La información que se incluye es número, fecha, hora, duración, + profundidad, temperatura y presión. En resumen, la mayoría de la información + que un buceador recreativo conserva en un registro escrito. +</p> +</li> +<li> +<p> +<em>Perfil de inmersión CSV</em>, que incluye una gran cantidad de detalles para + cada inmersión, entre ellos el perfil de profundidad, temperaturas + e información de presiones para cada inmersión. +</p> +</li> +<li> +<p> +Formato <em>HTML</em>, en el cual los buceos se guardan en archivos HTML, + visualizables con un navegador de internet.Se soportan la mayoría de navegadores + modernos, pero debe estar activado Javascript. Este archivo <strong>NO</strong> es editable. El + registro de inmersiones en HTML contiene la mayor parte de la información del + divelog. Sin embargo, no muestra los valores calculados del panel <strong>Perfil de + Inmersión</strong>, p.e. la presión calculada de la botella, presiones de los gases o + PMO. Dispone de una opción de búsqueda que permite rastrear el diario. La exportación + a HTML se especifica en la segunda pestaña del diálogo de exportación (imagen + <strong>B</strong> anterior). Un uso típico de esta opción es exportar todas nuestros buceos + a un smartphone o tablet donde nos serviría de registro portátil, util para + compañías a las que les gusta verificar el historial de un buceador. +</p> +</li> +<li> +<p> +Formato <em>mapamundi</em>, un archivo HTML con un mapa del mundo en el que quedará + marcada cada inmersión y alguna información sobre ella. El mapa <strong>NO</strong> es + editable. Si se selecciona cualquiera de los puntos de buceo + sobre el mapa, se muestra en texto un sumario de la inmersión, como se ve + en la imagen a continuación. +</p> +</li> +</ul></div> +<div class="imageblock" style="text-align:center;"> +<div class="content"> +<img src="images/mapview_f20.jpg" alt="Figura: Vista de exportación en formato Mapamundi" /> +</div> +</div> +<div class="ulist"><ul> +<li> +<p> +<em>Profundidad de imágenes</em>, que crea un fichero de texto que contiene los + nombres de todos los archivos de imágenes añadidos a cualquiera de los buceos + seleccionados del la <em>Lista de inmersiones</em>, junto con la profundidad a la + fue tomada la fotografía. +</p> +</li> +<li> +<p> +<em>Ajustes generales</em>, en la pestaña HTML, se proporcionan las siguientes + opciones: +</p> +<div class="ulist"><ul> +<li> +<p> +Numeración de Subsurface: Si se activa esta opción, las inmersiones se + exportan con la misma numeración que tienen asociada en <em>Subsurface</em>. De lo + contrario, los buceos se numerarán a partir de 1. +</p> +</li> +<li> +<p> +Exportar estadísticas anuales: Si se selecciona esta opción, se anexará una + tabla con estadísticas anuales a los datos exportados a HTML. +</p> +</li> +<li> +<p> +Solo exportar lista: Solo se exportará una lista de inmersiones. No se + dispondrá de información detallada de los buceos. +</p> +</li> +</ul></div> +</li> +<li> +<p> +<em>Opciones de estilo</em>: Algunas opciones relativas al estilo de visualización + en el navegador, como el tamaño de la letra o el tema aplicado. +</p> +</li> +</ul></div> +</div> +</div> +</div> +<div class="sect1"> +<h2 id="S_Cloud_access">10. Guardar un diario de <em>Subsurface</em> en la Nube</h2> +<div class="sectionbody"> +<div class="paragraph"><p>Para cualquier buceador, la información contenida en su diario es muy importante. +No es únicamente un registro de actividades de buceo para su propio placer +personal, sino que es información importante requerida para su admisión en +futuros cursos de entrenamiento o (en ocasiones) incluso en puntos de buceo. La +seguridad del diario es, así pues, crítica. De cara a poseer un diario que pueda +soportar el fallo del disco duro del ordenador de casa, el robo o la perdida del +equipo, etc, la <em>nube</em> es una solución obvia. Esto, además, añade el beneficio +de que se puede acceder al diario, casi, desde cualquier parte del mundo sin +tener que llevarlo encima. Por este motivo, facilidades como <em>divelogs.de</em> y +<em>Diving Log</em> ofrecen la posibilidad de guardar dicha información en internet.</p></div> +<div class="paragraph"><p><em>Subsurface</em> incluye acceso a almacenamiento en la nube integrado de forma +transparente, disponible para todos los usuarios de Subsurface. Guardar y +recuperar un divelog desde la nube no es más difícil que hacerlo desde un disco +duro. El único requisito es que, previamente, nos hemos de registrar como +usuarios. Para utilizar el <em>Almacenamiento en la nube de Subsurface</em> sigue estos +pasos:</p></div> +<div class="sect2"> +<h3 id="_crea_una_cuenta_en_el_almacenamiento_en_la_nube">10.1. Crea una cuenta en el almacenamiento en la nube:</h3> +<div class="ulist"><ul> +<li> +<p> +Abrir las <em>Preferencias de Red</em> seleccionando <em>Archivo</em> → <em>Preferencias</em> → + <em>Red</em>. +</p> +</li> +<li> +<p> +En la sección llamada <em>Almacenamiento en la nube de Subsurface</em>, introduce un + correo electrónico que <em>Subsurface</em> pueda utilizar para registrarnos. +</p> +</li> +<li> +<p> +Introduce una contraseña que <em>Subsurface</em> utilizará para guardar y recuperar + el divelog en la nube. +</p> +</li> +<li> +<p> +Se clica en <em>Aplicar</em> o en <em>OK</em> para enviar el email y la password al + servidor en la nube. El servidor responderá con un correo a la dirección + facilitada que contendrá un PIN de verificación (está será la única ocasión + en que <em>Subsurface</em> usará la dirección de correo proporcionada). El diálogo + <em>Preferencias de Red</em> mostrará una nueva casilla de texto, que no se mostraba + antes, para el PIN. +</p> +</li> +<li> +<p> +Se introduce el PIN en la casilla correspondiente del diálogo (Este campo solo + será visible mientras el servidor espera la confirmación de la dirección de + correo). +</p> +</li> +<li> +<p> +Clica de nuevo en <em>Aplicar</em> o en <em>OK</em> y la cuenta del <em>Almacenamiento + de Subsurface en la nube</em> se marcará como verificada y se podrá utilizar el + servicio. +</p> +</li> +</ul></div> +</div> +<div class="sect2"> +<h3 id="_usar_el_em_almacenamiento_de_subsurface_en_la_nube_em">10.2. Usar el <em>Almacenamiento de Subsurface en la nube</em></h3> +<div class="ulist"><ul> +<li> +<p> +Una vez que se ha inicializado el almacenamiento en la nube, aparecen dos + nuevas opciones en el desplegable <em>Archivo</em> del <em>Menú principal</em>: <em>Abrir + almacenamiento en la nube</em> y <em>Guardar en almacenamiento en la nube</em>. Estas + opciones permiten al usuario descargar y guardar los registros en el + servidor de <em>Subsurface</em> en la nube. +</p> +</li> +<li> +<p> +En la pestaña de <em>Preferencias predeterminadas</em> se puede seleccionar usar el + almacenamiento en la nube como archivo por defecto seleccionando la casilla + marcada como <em>Archivo por defecto en la nube</em>. Esto significa que los datos + del almacenamiento en la nube se cargarán al iniciar <em>Subsurface</em> y se + guardarán allí al salir del programa. +</p> +</li> +<li> +<p> +<em>Subsurface</em> mantiene una copia local de los datos y sigue siendo completamente + funcional si se utiliza desconectado. Simplemente sincronizará los datos con el + servidor la próxima vez que se utilice el programa y exista conexión a internet. +</p> +</li> +</ul></div> +</div> +<div class="sect2"> +<h3 id="S_Cloud_storage">10.3. Acceso web al <em>Almacenamiento de Subsurface en la nube</em></h3> +<div class="paragraph"><p>Uno de los efectos interesantes de utilizar el <em>Almacenamiento de Subsurface +en la nube</em> es que también se puede acceder a los datos con cualquier navegador. +Simplemente se abre <a href="https://cloud.subsurface-divelog.org">https://cloud.subsurface-divelog.org</a>, +se accede con los mismos e-mail y password, y se pueden visualizar los datos +del registro hasta la última sincronización efectuada con el <em>Almacenamiento +en la nube de Subsurface</em>. La información que se muestra son solo los contenidos +de los registros, NO los valores calculados que aparecen en el panel <strong>Perfil</strong>, +por ejemplo, presiones de botellas, techos deco o presiones parciales de +O<sub>2</sub>/He/N<sub>2</sub>.</p></div> +</div> +<div class="sect2"> +<h3 id="_otros_servicios_en_la_nube">10.4. Otros servicios en la nube</h3> +<div class="paragraph"><p>Si se prefiere no usar el almacenamiento en la nube integrado (y no se necesita +tener acceso vía web a los datos), también resulta muy fácil guardar los +divelogs en la nube usando uno de los servicios disponibles en internet.</p></div> +<div class="paragraph"><p>Por ejemplo <a href="http://www.dropbox.com/"><em>Dropbox</em></a> ofrece una aplicación gratuita +que permite que se vean como locales en nuestro ordenador los archivos guardados +en sus servidores.</p></div> +<div class="imageblock" style="text-align:center;"> +<div class="content"> +<img src="images/Cloud.jpg" alt="FIGURE: Carpeta de Dropbox" /> +</div> +</div> +<div class="paragraph"><p>El programa <em>Dropbox</em> crea una copia del contenido de <em>Dropbox</em> en la nube, en +una carpeta de nuestro ordenador. Cuando el ordenador se conecta a internet, el +contenido de nuestra carpeta y la nube se sincronizan. Así pues, las operaciones +<em>Abrir</em> y <em>Guardar</em> de los diarios se efectúan sobre la copia local de la carpeta +<em>Dropbox</em>, no siendo necesario disponer de conexión a internet al realizar estas +operaciones. Si se modifica la copia local, p.e. al añadir una inmersión, la +copia en el servidor <em>Dropbox</em> en la <em>nube</em> se actualizará automáticamente al +volvernos a conectar a internet.</p></div> +<div class="paragraph"><p>Actualmente el servicio no tiene ningún coste. Dropbox (Windows, Mac y Linux) +se puede instalar accediendo a la <a href="http://www.dropbox.com/install"><em>página de instalación</em></a> +<em>de Dropbox</em>.</p></div> +<div class="paragraph"><p>Como alternativa, se puede utilizar <em>Dropbox</em> como mecanismo para mantener una +copia de seguridad del diario.</p></div> +<div class="paragraph"><p>Para guardar un diario en <em>Dropbox</em>, selecciona <em>Archivo→ Guardar como</em> desde +menú principal de <em>Subsurface</em>, navega a la carpeta Dropbox y selecciona el +botón <em>Guardar</em>. Para usar el diario en <em>Dropbox</em>, selecciona <em>Archivo→Abrir +registro</em> desde el menú principal de <em>Subsurface</em>, navega al archivo en la +carpeta Dropbox y selecciona el botón <em>Abrir</em>.</p></div> +<div class="paragraph"><p>Existen varios servicios de pago en Internet (Google, Amazon …) con los que +se puede seguir el mismo proceso para tener los diarios de buceo almacenados en +la nube.</p></div> +</div> +</div> +</div> +<div class="sect1"> +<h2 id="S_PrintDivelog">11. Imprimir un diario</h2> +<div class="sectionbody"> +<div class="paragraph"><p><em>Subsurface</em> proporciona un interfaz simple y flexible para imprimir el diario +completo o solo unas pocas inmersiones seleccionadas. Se pueden utilizar +plantillas pre instaladas o escritas a medida para seleccionar donde situar +los datos en la página.</p></div> +<div class="paragraph"><p>Antes de imprimir, se deben tomar dos decisiones:</p></div> +<div class="ulist"><ul> +<li> +<p> +¿ Se desea imprimir el registro completo o solo parte de él ? Si solo se desea + parte del registro, entonces el usuario selecciona los buceos deseados en el + panel <strong>Lista de inmersiones</strong>. +</p> +</li> +<li> +<p> +¿ Que información sobre presiones parciales de los gases se desea tener en el + perfil ? El usuario activaría los botones apropiados de la barra de la izquierda + del panel <strong>Perfil de Inmersión</strong>. +</p> +</li> +</ul></div> +<div class="paragraph"><p>Si se ha seleccionado_Archivo → Imprimir_ desde el menú principal, aparecerá +el diálogo siguiente (imagen *A). Se necesita especificar tres cosas para +conseguir el diseño de información deseado:</p></div> +<div class="imageblock" style="text-align:center;"> +<div class="content"> +<img src="images/Print1_f22.jpg" alt="FIGURA: Diálogo de imresión" /> +</div> +</div> +<div class="olist arabic"><ol class="arabic"> +<li> +<p> +En <em>Tipo de impresión</em> seleccionar una de las dos opciones: +</p> +<div class="ulist"><ul> +<li> +<p> +<em>Impresión de lista de inmersiones</em>: Imprime buceos de la <strong>Lista de inmersiones</strong> +con perfiles y otra información. +</p> +</li> +<li> +<p> +<em>Impresión de estadísticas</em>: Imprime estadísticas anuales de las inmersiones. +</p> +</li> +</ul></div> +</li> +<li> +<p> +En <em>Opciones de impresión</em> seleccionar: +</p> +<div class="ulist"><ul> +<li> +<p> +<em>Imprimir solo inmersiones seleccionadas</em>. Se imprimirán solo las inmersiones de +la lista que se hubieran seleccionado previamente. Si no se activa esta casilla, +se imprimirán <strong>todas</strong> las inmersiones del registro. +</p> +</li> +<li> +<p> +<em>Impresión en color</em>. Si no se selecciona se imprimirá en escala de grises +(blanco y negro). +</p> +</li> +</ul></div> +</li> +<li> +<p> +En <em>Plantilla</em> seleccionar una plantilla que usar como distribución de la +página. Existen varias plantillas (ver imagen <strong>B</strong> anterior). +</p> +<div class="ulist"><ul> +<li> +<p> +<em>Table</em>: Se imprime una tabla resumen de todas las inmersiones seleccionadas +(ver imagen). +</p> +</li> +</ul></div> +</li> +</ol></div> +<div class="imageblock" style="text-align:center;"> +<div class="content"> +<img src="images/Print_summarylist_f22.jpg" alt="FIGURA: Imprimir tabla resumen" /> +</div> +</div> +<div class="ulist"><ul> +<li> +<p> +<em>Flow layout</em>: Imprime el texto asociado a cada inmersión, sin imprimir los +perfiles de los buceos (ver imagen): +</p> +</li> +</ul></div> +<div class="imageblock" style="text-align:center;"> +<div class="content"> +<img src="images/Print_flow_layout_f22.jpg" alt="FIGURE: Print flow layout" /> +</div> +</div> +<div class="paragraph"><p>-<em>One Dive</em>: Imprime una inmersión por página, mostrando el perfil (ver imagen)</p></div> +<div class="imageblock" style="text-align:center;"> +<div class="content"> +<img src="images/print2_f22.jpg" alt="FIGURE: Print one dive / page" /> +</div> +</div> +<div class="ulist"><ul> +<li> +<p> +<em>Two Dives</em>: Imprime dos inmersiones por página mostrando los perfiles. +</p> +</li> +<li> +<p> +<em>Six Dives</em>: Imprime seis inmersiones por página mostrando los perfiles. +</p> +</li> +</ul></div> +<div class="paragraph"><p>Los usuarios pueden <em>Previsualizar</em> la página a imprimir pulsando el botón +<em>Previsualizar</em> del diálogo (ver imagen <strong>A</strong> al inicio de la sección). Tras +visualizar , se pueden efectuar cambios en las opciones del diálogo de impresión, +hasta completar una distribución que se ajuste al gusto personal.</p></div> +<div class="paragraph"><p>A continuación, selecciona el botón <em>Imprimir</em> (ver imagen <strong>A</strong> al inicio de +esta sección). Esto activa el diálogo normal de impresión del sistema +operativo, que nos permitirá elegir la impresora y configurar sus propiedades.</p></div> +<div class="imageblock" style="text-align:center;"> +<div class="content"> +<img src="images/Print_print_f22.jpg" alt="FIGURE: Print one dive / page" /> +</div> +</div> +<div class="paragraph"><p>Ajusta la resolución de la impresora a un valor apropiado modificando sus +propiedades . Finalmente selecciona el botón <em>Print</em> para imprimir los buceos. +A continuación un ejemplo (bastante pequeño) de la salida de una página.</p></div> +<div class="imageblock" style="text-align:center;"> +<div class="content"> +<img src="images/Printpreview.jpg" alt="FIGURE: Previsualización de impresión" /> +</div> +</div> +<div class="sect2"> +<h3 id="_escribir_una_plantilla_de_impresion_a_medida_avanzado">11.1. Escribir una plantilla de impresión a medida (avanzado)</h3> +<div class="paragraph"><p>Escribir una plantilla a medida es una forma efectiva de producir impresiones +altamente personalizadas. Subsurface utiliza plantillas HTML con Grantlee como +sistema de impresión. Se puede crear una plantilla, exportar una nueva plantilla, +importar una existente o borrarla. Ver el <a href="#S_APPENDIX_E">APÉNDICE E</a> para ver +como escribir o modificar una plantilla.</p></div> +</div> +</div> +</div> +<div class="sect1"> +<h2 id="S_Configure">12. Configurar un ordenador de buceo</h2> +<div class="sectionbody"> +<div class="paragraph"><p><em>Subsurface</em> permite configurar algunos ordenadores de buceo. En estos momentos, +los Heinrichs-Weikamp OSTC2 y OSTC3 y los Suunto de la familia Vyper (Stinger, +Mosquito, D3, Vyper, Vytec, Cobra, Gekko y Zoop). Se pueden leer y modificar un +gran número de ajustes. En primer lugar hay que asegurarse de tener instalado el +driver adecuado para el ordenador de buceo y de conocer el nombre de dispositivo +asignado al ordenador por el sistema operativo. +Ver el <a href="#_apendice_a_informacion_especifica_del_sistema_operativo_para_importar_inmersiones_desde_un_ordenador_de_buceo">APÉNDICE A</a> +para información sobre como hacerlo.</p></div> +<div class="paragraph"><p>Una vez que el ordenador de buceo está al PC con <em>Subsurface</em>, se selecciona +<em>Archivo → Configurar ordenador de buceo</em> en el menú principal. Si se ha +indicado el nombre de dispositivo correcto en el campo de texto de la parte +superior, esto abrirá y seleccionará el modelo correcto en el panel de la +izquierda (ver imagen a continuación).</p></div> +<div class="imageblock" style="text-align:center;"> +<div class="content"> +<img src="images/Configure_dc_f20.jpg" alt="FIGURA: Configurar ordenador de buceo" /> +</div> +</div> +<div class="paragraph"><p>Utilizando los botones apropiados del panel de configuración, pueden llevarse +a cabo las siguientes acciones:</p></div> +<div class="ulist"><ul> +<li> +<p> +<strong>Descargar detalles disponibles</strong>. Descarga a <em>Subsurface</em> la configuración +del ordenador de buceo, mostrándola en el panel. +</p> +</li> +<li> +<p> +<strong>Guardar cambios en el dispositivo</strong>. Esto cambia la configuración del +ordenador de buceo para hacerla coincidir con la que se muestra en el panel. +</p> +</li> +<li> +<p> +<strong>Copia de seguridad</strong>. Guarda los datos de configuración en un archivo. +<em>Subsurface</em> solicitará una ubicación y un nombre de archivo para guardar la +información. +</p> +</li> +<li> +<p> +<strong>Restaurar copia de seguridad</strong>. Carga la información de un archivo de copia +de seguridad y la muestra en el panel. +</p> +</li> +<li> +<p> +<strong>Actualizar firmware</strong>. Si está disponible un nuevo firmware para el +ordenador de buceo, este será cargado al mismo. +</p> +</li> +</ul></div> +</div> +</div> +<div class="sect1"> +<h2 id="S_Preferences">13. Ajustar las Preferencias del usuario para <em>Subsurface</em></h2> +<div class="sectionbody"> +<div class="paragraph"><p>Hay varios ajustes en <em>Subsurface</em> que el usuario puede especificar. Se +encuentran a través de <em>Archivo → Preferencias</em>. Los ajustes se efectúan en +siete grupos: <strong>Predeterminados</strong>, <strong>Unidades</strong>, <strong>Gráfico</strong> , <strong>Lenguaje</strong>, <strong>Red</strong>, +<strong>Facebook</strong> y <strong>Georeferencia</strong>. Las +siete secciones funcionan con los mismos principios: el usuario debe especificar +los ajustes que desee modificar, luego guárdarlos usando el botón <strong>Aplicar</strong>. +Tras aplicarlos todos se puede salir seleccionando <strong>Aceptar</strong> o <strong>Cerrar sin +guardar</strong> si finalmente decide no hacer los cambios.</p></div> +<div class="sect2"> +<h3 id="_predeterminados">13.1. Predeterminados</h3> +<div class="paragraph"><p>Hay varios ajustes en el panel <strong>Predeterminados</strong>:</p></div> +<div class="imageblock" style="text-align:center;"> +<div class="content"> +<img src="images/Pref1_f20.jpg" alt="FIGURA: Pantalla de Predeterminados en Preferencias" /> +</div> +</div> +<div class="ulist"><ul> +<li> +<p> +<strong>Listas y tablas</strong>: Aquí se pueden elegir el tipo de fuente y el tamaño de la + misma en el panel <strong>Lista de inmersiones</strong>. Reduciendo el tamaño de la fuente, se + pueden ver más buceos en una sola pantalla. +</p> +</li> +<li> +<p> +<strong>Inmersiones</strong>: En este bloque se especifica la carpeta y nombre de archivo + del registro de buceo electrónico. Es un archivo con extensión .xml o .ssrf. Al iniciar + <em>Subsurface</em> sin argumentos cargará automáticamente el registro especificado + aquí. Existen tres opciones: +</p> +<div class="ulist"><ul> +<li> +<p> +<em>Sin archivo por defecto</em>: Si se selecciona, <em>Subsurface</em> no abre ningún + archivo automáticamente al iniciarse +</p> +</li> +<li> +<p> +<em>Archivo por defecto local</em>: Si se selecciona, <em>Subsurface</em> abre un archivo + del disco duro local al iniciarse. +</p> +</li> +<li> +<p> +<em>Archivo por defecto en la nube</em>: Si se selecciona, <em>Subsurface</em> abre el + divelog en la nube que se inicializó desde la pestaña <em>Red</em> de las + <strong>Preferencias</strong> (ver a continuación). +</p> +</li> +</ul></div> +</li> +<li> +<p> +<strong>Mostrar invalidas</strong>: Las inmersiones pueden marcarse como "invalidas" (cuando + el usuario desea ocultar buceos que no considere validos, p.e. en piscina, pero + aún quiera mantenerlos registrados en el diario). Esta opción controla si estas + inmersiones se muestran en la lista. +</p> +</li> +<li> +<p> +<strong>Botella por defecto</strong>: Se puede especificar una botella por defecto de las + que aparecen listadas en la pestaña <strong>Equipo</strong> del panel <strong>Notas</strong>. + Es muy cómodo si se bucea habitualmente con el mismo tipo de botella, asigna a + cada nueva inmersión una botella del tipo aquí definido. +</p> +</li> +<li> +<p> +<strong>Animaciones</strong>: Algunas acciones, al mostrar el perfil, se ejecutan utilizando + animaciones. Por ejemplo, los valores de los ejes para la profundidad y el + tiempo cambian de una inmersión a otra. Al visualizar inmersiones distintas + estos cambios en las características de los ejes no suceden de forma + instantánea, sino que son animados. La <em>Velocidad</em> de las animaciones puede + controlarse ajustando esta regleta, con mayor velocidad a la izquierda y + significando "0" ninguna animación en absoluto. +</p> +</li> +<li> +<p> +<strong>Servicio web de Subsurface</strong>: Cuando uno se suscribe al <a href="#S_Companion">servicio web de Subsurface</a>, se proporciona una ID de usuario muy larga y + difícil de recordar. Este es el lugar donde guardar esa ID. Seleccionando la + opción <em>¿Guardar localmente la ID de usuario?</em> nos aseguramos de que se guarda + una copia de dicha ID en el ordenador. +</p> +</li> +<li> +<p> +<strong>Borrar todos los ajustes</strong> Tal como se indica en el botón bajo esta cabecera, + se borran todos los ajustes y se reinician con los valores por defecto. +</p> +</li> +</ul></div> +</div> +<div class="sect2"> +<h3 id="_unidades">13.2. Unidades</h3> +<div class="imageblock" style="text-align:center;"> +<div class="content"> +<img src="images/Pref2_f20.jpg" alt="FIGURA: Página de preferencias de unidades" /> +</div> +</div> +<div class="paragraph"><p>Aquí el usuario puede elegir entre medidas métricas o imperiales para +profundidad, presión, volumen, temperatura y masa. Al seleccionar el botón de +Métrico o Imperial de arriba, el usuario indica que todas las unidades vayan en +las correspondientes al sistema elegido. Como alternativa, si se selecciona +<strong>Personalizar</strong> se pueden mezclar, con algunas medidas en métrico y otras en +imperial.</p></div> +<div class="paragraph"><p>Independientemente de los ajustes citados, en la opción <em>Unidades de tiempo</em> +se puede elegir si se desea que las +velocidades de ascenso/descenso se muestren en m/s o en m/min. Los buzos con +botella, habitualmente, manejan velocidades en m/min, sin embargo, los apneístas +ascienden mucho más deprisa por lo que suelen utilizar velocidades en m/s. +Igualmente, las coordenadas GPS pueden representarse de la forma tradiciona +(grados, minutos, segundos) o como grados con decimales, elige la más adecuada +a tus necesidades.</p></div> +</div> +<div class="sect2"> +<h3 id="_grafico">13.3. Gráfico</h3> +<div class="imageblock" id="S_CCR_options" style="text-align:center;"> +<div class="content"> +<img src="images/Pref3_f20.jpg" alt="FIGURA: Página de Preferencias del gráfico" /> +</div> +</div> +<div class="paragraph" id="S_GradientFactors"><p>Este panel permite dos tipos de selecciones:</p></div> +<div class="ulist"><ul> +<li> +<p> +<strong>Mostrar</strong>: Aquí los usuarios eligen la cantidad de información que se muestra + como parte del perfil de la inmersión: +</p> +<div class="ulist"><ul> +<li> +<p> +<em>Umbrales</em>: <em>Subsurface</em> puede mostrar las presiones parciales de nitrógeno, + oxígeno y helio durante el buceo. Se activan utilizando la barra de herramientas + de la izquierda de panel <strong>Perfil de inmersión</strong>. Para cada uno de estos gases, + los usuarios puede especifica un valor umbral a la derecha en el panel de + Preferencias. Si cualquiera de los gráficos sube por encima de este nivel, + entonces el gráfico se resalta en rojo, indicando que se ha excedido dicho + umbral de presión parcial. +</p> +</li> +<li> +<p> +<em>Max pO<sub>2</sub> al mostrar PMO</em> es el valor usado para calcular la profundidad + máxima operativa (PMO) de un gas. Especifica una presión parcial apropiada. + Habitualmente se usa un valor de 1.4. +</p> +</li> +<li> +<p> +<em>Trazar en rojo el techo informado por el ordenador de buceo</em>: Esta casilla + seleccionable permite exactamente lo que dice. El color por defecto es blanco. + No todos los ordenadores de buceo + facilitan los valores de los techos. Si el ordenador de buceo lo facilita, puede + diferir de los techos calculados por <em>Subsurface</em>. Esto se debe al uso de + diferentes algoritmos, diferentes factores de gradiente y a la forma dinámica en + que los ordenadores de buceo calculan los techos durante la inmersión. +</p> +</li> +<li> +<p> +<em>Mostrar botellas no usadas en la pestaña equipo</em>: Esta casilla seleccionable + permite mostrar información sobre botellas que no se han utilizado durante la + inmersión, en la pestaña Equipo. Por el contrario, si la casilla no está + seleccionada, cualquier botella que se haya registrado en la pestaña Equipo y no + haya sido utilizada (p.e. botellas de bail-out) se omiten en la lista mostrada + aunque siguen estando guardadas. +</p> +</li> +<li> +<p> +<em>Mostrar la profundidad media</em>: Activar esta casilla hace que <em>Subsurface</em> + trace una línea gris a través del perfil, indicando la profundidad media del + buceo en cada momento de la inmersión. Normalmente es una línea con forma de + "u" que indicará la profundidad media mayor justo antes de iniciar el ascenso. +</p> +</li> +</ul></div> +</li> +<li> +<p> +<strong>Varios</strong>: +</p> +<div class="ulist" id="GradientFactors_Ref"><ul> +<li> +<p> +Factores de gradiente (GF_bajo y GF_alto)<strong>: Se fijan los <em>factores + de gradiente</em> usados en la inmersión. El GF_bajo es el factor de gradiente a + mayores profundidades y el GF_alto se usa justo debajo de la superficie. A + profundidades intermedias se usan factores entre GF_bajo y GF_alto. Los factores + de gradiente añaden conservadurismo a la exposición al nitrógeno durante un + buceo, del mismo modo que muchos ordenadores de buceo tienen un ajuste del + conservadurismo. Cuanto menor sea el valor de un factor de gradiente, más + conservativos son los cálculos en relación a la carga de nitrógeno y más + profundos serán los techos durante el ascenso. Factores de gradiente de 20/60 + son considerados conservadores y valores de 70/90 se consideran agresivos. + Seleccionar la casilla *GF bajo a la máxima profundidad</strong> hace que se use el + GF_bajo en la mayor profundidad de la inmersión. Si no se selecciona, GF_bajo se + aplica a todas las profundidades mayores que la primera parada deco. Para más + información, ver: +</p> +<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> +</li> +<li> +<p> +<em>CCR: Mostrar setpoints al visualizar pO<sub>2</sub></em>: Con esta casilla activada, el + gráfico de pO<sub>2</sub> del perfil mostrará una línea en rojo que indicará los + valores de setpoint del CCR. Véase la sección en <a href="#S_CCR_dives">Inmersiones con rebreather de circuito cerrado</a>. +</p> +</li> +<li> +<p> +<em>CCR: Mostrar los valores de los sensores de O<sub>2</sub> al visualizar la pO<sub>2</sub></em>: + Muestra los valores de pO<sub>2</sub> asociados con cada uno de los sensores de + oxígeno de un sistema CCR. Ver la sección <a href="#S_CCR_dives">Inmersiones con rebreather de circuito cerrado</a>. +</p> +</li> +</ul></div> +</li> +<li> +<p> +<strong>Configurar la planificación de inmersiones usando equipo de rebreather</strong>: +</p> +<div class="ulist"><ul> +<li> +<p> +<em>Setpoint del CCR por defecto para la planificación de inmersiones</em>: + Especifica el setpoint de O<sub>2</sub> para planificar buceos con CCR. Este valor + determinará la pO<sub>2</sub> a mantener durante una inmersión. Los cambios + efectuados durante el buceo se pueden añadir a través del menú contextual + del perfil. +</p> +</li> +<li> +<p> +<em>pSCR Ratio de O<sub>2</sub> en el metabolismo</em>: Para un rebreather semicerrado (pSCR) + este es el volumen de oxígeno usado por el buceador en un minuto. Fija este + valor para planificar buceos con pSCR y cálculos de descompresión. +</p> +</li> +<li> +<p> +<em>pSCR Ratio</em>: En equipos pSCR el ratio de vertido es la cantidad de gas + expulsada del circuito frente a la cantidad de gas recirculada en el circuito. + Fija este valor para planificar buceos con pSCR. Se suele usar un ratio 1:10 +</p> +</li> +</ul></div> +</li> +</ul></div> +</div> +<div class="sect2"> +<h3 id="_lenguaje">13.4. Lenguaje</h3> +<div class="paragraph"><p>Se elige el lenguaje que debe utilizar <em>Subsurface</em>.</p></div> +<div class="imageblock" style="text-align:center;"> +<div class="content"> +<img src="images/Pref4_f20.jpg" alt="FIGURA: página de preferencias de lenguaje" /> +</div> +</div> +<div class="paragraph"><p>Una casilla de selección permite usar el lenguaje <em>Predeterminado del sistema</em> +que, en la mayoría de los casos será el ajuste correcto; con esto <em>Subsurface</em> +simplemente se ejecuta con los mismos ajustes de lenguaje/país que el SO +subyacente. Si esto, por alguna razón, no fuera deseable, se puede deseleccionar +la casilla y elegir una de las combinaciones de lenguaje/país incluidas en la +lista de traducciones. La casilla de texto <em>Filtro</em> permite listar lenguajes +similares. Por ejemplo hay diversas variantes de inglés o francés.</p></div> +</div> +<div class="sect2"> +<h3 id="_red">13.5. Red</h3> +<div class="paragraph"><p>Este panel facilita la comunicación entre <em>Subsurface</em> y las fuentes de datos en +internet.</p></div> +<div class="paragraph"><p>Esto es importante cuando <em>Subsurface</em> tiene que comunicarse con servicios como +el <a href="#S_Companion">servicio web de <em>Subsurface</em></a> o importar/exportar datos de +<em>Divelogs.de</em>. El acceso a internet viene determinado por el tipo de conexión y +por el proveedor de acceso (ISP) utilizado. El ISP debería proporcionar la +información necesaria.</p></div> +<div class="imageblock" style="text-align:center;"> +<div class="content"> +<img src="images/Pref5_f20.jpg" alt="FIGURA: página de preferencias de red" /> +</div> +</div> +<div class="paragraph"><p>Este diálogo tiene tres secciones:</p></div> +<div class="ulist"><ul> +<li> +<p> +<em>Tipo de proxy</em>: + Si se utiliza un servidor proxy para acceder a internet, el tipo de proxy se + selecciona del desplegable, tras + lo cual debe facilitarse la dirección IP del servidor y el número de puerto. Si + el servidor proxy utiliza autenticación también han de indicarse el usuario y su + password para que <em>Subsurface</em> pueda pasar automáticamente a través del proxy + para acceder a internet. +</p> +</li> +<li> +<p> +<em>Almacenamiento en la nube de Subsurface</em>: + Para poder guardar nuestro divelog en la nube, se precisa una dirección + de correo electrónico y una password. Esto permite a <em>Subsurface</em> mandar + un correo electrónico al usuario con información de seguridad relativa al + almacenamiento en la nube. Tiene dos opciones adicionales: +</p> +<div class="ulist"><ul> +<li> +<p> +<em>Sincronizar con la nube en segundo plano</em>: Permite guardar la información + en la nube mientras el usuario lleva a cabo otras tareas en <em>Subsurface</em>. +</p> +</li> +<li> +<p> +<em>Guardar contraseña localmente</em>: Permite guardar la contraseña de acceso + a la nube en el disco duro. ¡¡¡ OJO !!! La contraseña se guarda en texto + plano sin encriptar. +</p> +</li> +</ul></div> +</li> +<li> +<p> +<em>Servicio web de Subsurface</em>: + Al suscribirnos al <a href="#S_Companion">Servicio web de Subsurface</a>, se nos + facilita una identificación de usuario muy larga y dificil de recordar. + Este es el lugar donde guardarla. Seleccionando la opción, nos asegurammos + de tener una copia local de la misma. +</p> +</li> +</ul></div> +</div> +<div class="sect2"> +<h3 id="S_Facebook">13.6. Acceso a Facebook</h3> +<div class="paragraph"><p>Este panel nos permite acceder a una cuenta de <em>Facebook</em> para poder enviar +información desde <em>Subsurface</em>.</p></div> +<div class="imageblock" style="text-align:center;"> +<div class="content"> +<img src="images/Pref6_f20.jpg" alt="FIGURE: Facebook login panel" /> +</div> +</div> +<div class="paragraph"><p>Si se proporciona un usuario y una clave validos, se crea una conexión a +<em>Facebook</em>. La conexión se cierra cuando al cerrar <em>Subsurface</em>. La casilla +seleccionable "No cerrar sesión con Subsurface" de la pantalla de acceso no +tiene ningún efecto, en estos momentos. +Ver la sección <a href="#S_facebook">Exportar perfiles de inmersión a Facebook</a> +para más información.</p></div> +</div> +<div class="sect2"> +<h3 id="_georefencia">13.7. Georefencia</h3> +<div class="paragraph"><p><em>Subsurface</em> proporciona un servicio de búsqueda geográfica (Esto es, la +capacidad de buscar el nombre de un lugar, en base a unas coordenadas +geográficas proporcionadas haciendo clic en el panel <strong>Globo</strong>, de un GPS o +desde la app <em>Subsurface companion</em>) basado en internet, que localiza el +nombre conocido más cercano a nuestra posición. Obviamente la función solo +actúa con conexión a internet. La configuración se puede efectuar como en +la imagen a continuación</p></div> +<div class="imageblock" style="text-align:center;"> +<div class="content"> +<img src="images/Pref7_f20.jpg" alt="FIGURE: Facebook login panel" /> +</div> +</div> +</div> +</div> +</div> +<div class="sect1"> +<h2 id="S_DivePlanner">14. El Planificador de <em>Subsurface</em></h2> +<div class="sectionbody"> +<div class="paragraph"><p>La planificación de inmersiones es una característica avanzada de <em>Subsurface</em> +accesible desde <em>Registro → Planificar Inmersión</em> en el menú principal. Permite +calcular la carga de gases inertes durante una inmersión utilizando el algoritmo +Bühlmann ZHL16 con factores de gradiente tal y como lo implementó 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">Esta prestación <strong>ES EXPERIMENTAL</strong> y supone que el usuario ya está familiarizado +con el interfaz de <em>Subsurface</em>. Se utiliza <strong>EXPLICITAMENTE</strong> bajo las siguientes +condiciones:</td> +</tr></table> +</div> +<div class="ulist"><ul> +<li> +<p> +El usuario está versado en la planificación de inmersiones y tiene el + entrenamiento necesario para planificar inmersiones. +</p> +</li> +<li> +<p> +El usuario planifica buceos dentro de los límites para los que está + certificado. +</p> +</li> +<li> +<p> +La planificación de inmersiones hace grandes suposiciones sobre las + características de la <em>persona media</em> y no puede compensar las características + fisiológicas individuales , de salud o de estilos de vida. +</p> +</li> +<li> +<p> +La seguridad de un plan de buceo depende mucho de la forma en que se use el + planificador. +</p> +</li> +<li> +<p> +El usuario esta familiarizado con la interfaz de usuario de <em>Subsurface</em>. +</p> +</li> +<li> +<p> +Un usuario que no este completamente seguro de cualquiera de los requisitos + anteriores, no debería utilizar esta capacidad de <em>Subsurface</em>. +</p> +</li> +</ul></div> +</div></div> +<div class="sect2"> +<h3 id="_la_pantalla_del_planificador_de_em_subsurface_em">14.1. La pantalla del planificador de <em>Subsurface</em></h3> +<div class="paragraph"><p>Al igual que el diario de <em>Subsurface</em>, la pantalla del planificador se divide +en varias secciones (ver imagen a continuación). Los parámetros de ajuste de una +inmersión se introducen en las diversas secciones a la izquierda de la pantalla. +El ajuste se divide en varias secciones: Gases disponibles, Ritmos, Planificar, +Opciones de gases y Notas.</p></div> +<div class="paragraph"><p>Arriba a la derecha hay un <strong>panel de diseño</strong> verde sobre el cual puede +manipularse directamente el perfil de inmersión arrastrando y haciendo clic como +se explica a continuación. Esta característica hace al planificador de +<em>Subsurface</em> único en facilidad de uso.</p></div> +<div class="paragraph"><p>Abajo a la derecha hay un panel de texto con la cabecera <em>Detalle del Plan</em>. +Aquí es donde se proporcionan los detalles del plan de inmersión de forma que +pueda copiarse con facilidad a otro software. También es donde se imprimirá +cualquier mensaje de aviso sobre el plan de buceo.</p></div> +<div class="imageblock" style="text-align:center;"> +<div class="content"> +<img src="images/PlannerWindow1_f20.jpg" alt="FIGURA: Ventana de inicio del planificador" /> +</div> +</div> +</div> +<div class="sect2"> +<h3 id="_inmersiones_con_circuito_abierto">14.2. Inmersiones con circuito abierto</h3> +<div class="ulist"><ul> +<li> +<p> +En la parte de abajo al centro del planificador (círculo azul en la imágen + anterior) hay un desplegable con tres opciones. Selecciona la correcta + entre ellas: +</p> +<div class="ulist"><ul> +<li> +<p> +Circuito abierto (por defecto) +</p> +</li> +<li> +<p> +CCR +</p> +</li> +<li> +<p> +pSCR +</p> +</li> +</ul></div> +</li> +<li> +<p> +En el área de arriba a la izquierda de la pantalla del planificador, hay que + asegurarse de que los parámetros constantes son correctos. Son: Fecha y hora + de inicio de la inmersión, Presión atmosférica, y altura sobre el nivel del + mar. Estos dos últimos están relacionados, variando uno se modifica el otro. + La presión atmosférica por defecto a nivel del mar son 1.013 bar. +</p> +</li> +<li> +<p> +En la tabla etiquetada como <em>Gases disponibles</em>, añadir la información de las + botellas que se han de utilizar y la composición de los gases de cada botella. + Esto se hace de forma similar a <a href="#cylinder_definitions">como se rellena la información de botellas en un diario</a>. Se elige el tipo de botella de la lista desplegable + y se especifica la presión de trabajo de la botella. Si dejamos en blanco la + concentración de oxígeno (O2%) se asume que el gas que contiene es aire. En otro + caso, se introducen las concentraciones de oxígeno y/o helio en las casillas del + diálogo. Si es necesario , se añaden botellas utilizando el icono "+" de arriba + a la derecha. +</p> +</li> +<li> +<p> +El perfil del buceo a planificar se puede crear de dos maneras: +</p> +<div class="ulist"><ul> +<li> +<p> +Arrastrar los puntos del perfil + (los pequeños círculos blancos) para que representen la inmersión. Se pueden + crear puntos adicionales haciendo doble-clic sobre el perfil de buceo. Se + pueden borrar haciendo clic-derecho en un punto concreto y seleccionando + <em>borrar</em> en el menú contextual. +</p> +</li> +<li> +<p> +La forma más eficiente de crear un perfil es introducir los valores + apropiados en la tabla llamada <em>Puntos del planificador de inmersiones</em>. + La primera línea de la tabla representa la duración y profundidad final + de un descenso desde superficie. Los segmentos siguientes describirán la + fase de fondo de la inmersión. La columna <em>CC set point</em> solo es relevante + para para buceadores en circuito cerrado. + El ascenso, normalmente, no se especifica, ya que esto es lo que se supone + que el planificador debe calcular. + Añade segmentos adicionales al perfil utilizando el icono "+" arriba a la + derecha de la tabla. Los segmentos introducidos en la tabla aparecen de + forma automática en el diagrama "Perfil de la inmersión". +</p> +</li> +</ul></div> +</li> +</ul></div> +<div class="sect3"> +<h4 id="_inmersiones_recreativas">14.2.1. Inmersiones recreativas</h4> +<div class="paragraph"><p>El modo recreativo es lo que más se aproxima a planificar una inmersión +basándonos en el límite de no descompresión (LND). Tiene en cuenta el tiempo +que un buceador puede estar a la profundidad actual sin incurrir en paradas +de descompresión obligatorias, y usando el gas disponible menos una reserva. +El planificador tiene en cuenta automáticamente la carga nitrógeno acumulada +en inmersiones previas. Sin embargo, las tablas convencionales también tienen +en cuenta los buceos anteriores ¿Por qué utilizar un planificador para buceos +recreativos? Al utilizar las tablas recreativas se tiene en cuenta la máxima +profundidad de una inmersión. Sin embargo, pocas inmersiones se efectúan a +una profundidad constante que corresponda con la máxima (perfil "cuadrado"). +Esto supone que las tablas sobre estiman la carga de nitrógeno acumulada de +las inmersiones previas. El planificador de <em>Subsurface</em> calcula la carga de +nitrógeno de acuerdo con los perfiles reales de las inmersiones anteriores de +forma similar a como lo hacen los ordenadores de buceo durante la inmersión. +Esto significa que el buceador es "bonificado" por no permanecer a profundidad +máxima en las inmersiones anteriores, permitiendo planificar una inmersión +posterior más larga. Para que el planificador funcione es, pues, crucial haber +descargado a <em>Subsurface</em> todas las inmersiones anteriores antes de hacer la +planificación.</p></div> +<div class="paragraph"><p>Para planificar un buceo, es necesario definir los ajustes apropiados.</p></div> +<div class="ulist"><ul> +<li> +<p> +Asegurarse de que el día y la hora se han ajustado a los de la inmersión +planeada. Esto permite calcular la carga de nitrógeno de los buceos anteriores. +</p> +</li> +<li> +<p> +Justo bajo la cabecera <em>Planificar</em> hay dos casillas seleccionables + <em>Recreativo</em> y <em>Parada de seguridad</em>. Para inmersiones recreativas se seleccionan + ambas casillas. +</p> +</li> +<li> +<p> +Luego se define el tamaño de las botellas, la mezcla de gas (aire o % de + oxígeno) y la presión inicial de las botellas en la parte superior izquierda + del planificador, en <em>Gases disponibles</em>. +</p> +</li> +<li> +<p> +El planificador calcula si la botella elegida contiene suficiente aire/gas + para completar la inmersión planeada. Para que esto sea realista, bajo + <em>Opciones de gases</em>, se especifica un consumo de aire en superficie (CAS) + adecuado para la opción <em>CAS en fondo</em>. Los valores adecuados se situarían + entre 15 l/min y 30 l/min, siendo para buceadores noveles o buceos difíciles + próximos a 30 l/min. +</p> +</li> +<li> +<p> +Definir la cantidad de gas que se pretende que sobre en la botella al final + de la inmersión, justo antes de iniciar el ascenso. Se suele usar un valor de + 50 bar. La razón para esta reserva de gas guardarlo para una posible + necesidad de ascender compartiendo aire con el compañero. Es bastante + difícil estimar cuanto gas se usaría al compartir, así que la mayoría de + agencias establecen una cantidad fija p.e 40 o 50 bares. <em>Subsurface</em> aún lo + hace mejor, porque conoce el ascenso y tiene en cuenta el gas consumido en + el mismo. Además de esto, <em>Subsurface</em> aún utiliza una reserva fija de + presión. La cantidad de gas de esta reserva puede ser configurada por el + usuario. +</p> +</li> +<li> +<p> +Definir la profundidad de la inmersión arrastrando los puntos blancos en el + perfil o introduciendo la profundidad en la tabla que se encuentra en <em>Puntos + del planificador de inmersiones</em>. Si se tratara de una inmersión multinivel, + se añaden los puntos necesarios que representen el plan, bien añadiéndolos en + el perfil de la inmersión, bien en la tabla citada. <em>Subsurface</em> extenderá + la sección de fondo de la inmersión a la duración máxima dentro del LND. +</p> +</li> +<li> +<p> +Se puede modificar la velocidad de ascenso. Las velocidades de ascenso + establecidas por defecto son aquellas consideradas seguras para el buceo + recreativo. +</p> +</li> +<li> +<p> +El perfil del planificador indica el tiempo máximo de inmersión dentro de +los límites de no descompresión, utilizando el algoritmo Bülmann ZH-L16 y el +gas y la profundidad especificados como se ha descrito anteriormente. El +planificador de <em>Subsurface</em> permite una visualización rápida de la duración +de una inmersión en función de la profundidad, teniendo en cuenta la carga de +nitrógeno residual resultante de las inmersiones previas. El plan de buceo +incluye una estimación de la cantidad de aire/gas que se va a utilizar, +dependiendo de los ajustes de las botellas especificadas en <em>Gases disponibles</em>. +Si la presión inicial de la botella se ajusta a "0", la duración del buceo que +se mostrará será el auténtico límite de no descompresión (LND) sin tener en +cuenta el gas utilizado durante la inmersión. Si la superficie sobre el perfil +se vuelve roja, significa que se han sobrepasado los límites del buceo recreativo +y se necesita reducir, bien la profundidad, bien la duración. +</p> +</li> +</ul></div> +<div class="paragraph"><p>A continuación se muestra una imagen de un plan para una inmersión recreativa +a 30 metros. Aunque el límite de no descompresión es 23 minutos, la duración +del buceo se ve limitada por la cantidad de aire en la botella, reflejada por +la ventana de texto informativa abajo a la derecha del panel en la que se nos +indica que no existe suficiente gas para compartir con el compañero durante el +ascenso.</p></div> +<div class="imageblock" style="text-align:center;"> +<div class="content"> +<img src="images/rec_diveplan.jpg" alt="FIGURE: A recreational dive plan: setup" /> +</div> +</div> +</div> +<div class="sect3"> +<h4 id="_inmersiones_en_circuito_abierto_no_recreativas_incluyendo_descompresion">14.2.2. Inmersiones en circuito abierto no recreativas, incluyendo descompresión</h4> +<div class="paragraph"><p>La planificación no recreativa supone exceder los límites de no descompresión +y/o utilizar múltiples gases. Tales inmersiones se planifican en tres fases:</p></div> +<div class="paragraph"><p><strong>a) Control de gases inertes</strong>: Esto se consigue especificando las velocidades +de descenso y ascenso, así como el modelo descompresivo (GF bajo y GF alto o +nivel de conservadurismo) bajo los encabezamientos <em>Velocidades</em> y <em>Planificar</em> +en la parte inferior de la pantalla de planificación. Están soportados dos +modelos descompresivos, el modelo Bühlmann y el modelo VPM-B. Elige uno de los +dos modelos. Si se selecciona el modelo Bühlmann, se necesita especificar los +factores de gradiente (GF_alto y GF_bajo). En principio se utilizarán los +factores de gradiente especificados en la pantalla de <em>Preferencias</em> de +<em>Subsurface</em>. Si se modifican en el planificador(ver <em>Opciones de gases</em>), se +utilizan los nuevos valores sin modificar los marcados en las <em>Preferencias</em>. +Los ajustes de los factores de gradiente afectan enormemente a los techos +calculados y sus profundidades. +Un <em>GF bajo</em> muy pequeño produce paradas de descompresión más pronto durante la +inmersión. +** Para más información sobre factores de gradiente visita la sección +<a href="#S_GradientFactors">Ajustes de la Preferencias de factores de gradiente</a>.</p></div> +<div class="paragraph"><p>Si se seleccioná ell modelo VPM-B, es necesario especificar el nivel de +conservadurismo, en una escala de 0 (menos conservador) a 4 (más conservador). +Este modelo tiende a dar paradas deco a mayores profundidades que el modelo de +Bühlmann y, a menudo, produce perfiles ligeramente más cortos que este último. +Cuando elijas uno de los modelos, recuerda que no son modelos fisiológicos +exactos, sino modelos matemáticos que parecen funcionar en la práctica.</p></div> +<div class="paragraph"><p>Para más información externa a este manual ver:</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, por 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&ie=UTF8&qid=1403932320&sr=1-1&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. Un excelente estudio no técnico en el que se discuten ambos modelos, el de Bühlmann y el VPM-B. +</p> +</li> +</ul></div> +<div class="paragraph"><p>La velocidad de ascenso es crítica para la desgasificación al final de la +inmersión y se especifica para varios rangos utilizando la profundidad media +como vara de medir. La profundidad media del plan se indica como una línea gris +sobre el perfil. Las velocidades de ascenso en los niveles más +profundos se sitúan, a menudo, en el rango de 8 a 12 m/min, mientras que en los +niveles más superficiales suelen estar en los 3 a 6 m/min llegando en ocasiones +a 1 m/min. La velocidad de descenso también se especifica. Si activamos la +opción <em>Caer a la primera profundidad</em> , la fase de descenso se efectuará a la +máxima velocidad indicada en la sección <em>Velocidades</em> de los ajustes.</p></div> +<div class="paragraph"><p><strong>b) Control del oxígeno</strong>: En las <em>Opciones de gases</em> es necesario +especificar la máxima presión parcial de oxígeno para la parte del fondo +(<em>pO2 en fondo</em> ) y también para la fase de descompresión (<em>pO2 en deco</em>). +Los valores más comunes son 1.4 bar para el fondo de la inmersión y 1.6 bar +para las paradas de descompresión. Habitualmente no se excede una presión +parcial de 1.6 bar de O2. Los ajustes de pO2 y la profundidad a la que cambiar +de gases también pueden editarse en el diálogo <em>Gases disponibles</em>. Normalmente +el planificador decide el cambio a otro gas cuando, durante el ascenso, la +presión parcial del nuevo gas se sitúa por debajo de 1.6 bar.</p></div> +<div class="paragraph"><p><strong>c) Control del gas</strong>: En inmersiones con circuito abierto esta es una +consideración prioritaria. Es necesario mantenerse en los límites de la cantidad +de gas de la botella, manteniendo un margen de seguridad apropiado para regresar +a superficie, posiblemente compartiendo gas con un compañero. En las <em>Opciones +de gases</em> especifica la mejor (pero conservativa) estimación de tu "consumo de +aire equivalente a superficie" (CAS, del inglés SAC, también llamado RMV) en +litros/minuto (en estos momentos solo están soportadas las unidades del Sistema +Internacional). Se especifica el CAS para el fondo (<em>CAS en fondo</em>) y también +para la fase de descompresión (<em>CAS en deco</em>). Son comunes valores de 15 a +30 l/min. Para hacer una buena gestión del gas, una regla del pulgar no es +suficiente y se necesita monitorizar el consumo regularmente, dependiendo de +diferentes condiciones ambientales y de equipo. El planificador calculará el +volumen total de gas a utilizar durante la inmersión y emitirá un aviso si se +excede la cantidad total de gas disponible. Las buenas prácticas exigen que no +se bucee al límite del gas disponible, sino que se mantenga una reserva de gas +apropiada para atender circunstancias imprevistas. En el caso del buceo técnico, +esta reserva puede ser, fácilmente, del 66% del gas disponible.</p></div> +<div class="paragraph"><p>Ahora, por fin, se puede empezar la planificación detallada de tiempos y +profundidades. <em>Subsurface</em> ofrece una interfaz gráfica única para llevar a cabo +esta parte de la planificación. El mecanismo es similar a introducir a mano un +perfil en el diario de inmersiones. Al activar el planificador, se genera un +perfil por defecto de 40 minutos a 15 metros. Los puntos blancos (puntos de +paso) del perfil, se pueden arrastrar con el ratón. Se crean más puntos haciendo +doble-clic en la línea del perfil. Se arrastran los puntos de paso paso hasta +estar seguros de que el perfil refleja la inmersión que se pretende efectuar. +No es necesario especificar la fase de ascenso ya que será calculada por el +planificador basándose en los ajustes que se hayan especificado. +Si se sobrepasa cualquiera de los límites establecidos, la superficie sobre el +perfil se volverá roja.</p></div> +<div class="paragraph"><p>Cada punto de paso en el perfil crea un <em>punto en el planificador</em> en la tabla +a la izquierda del panel del planificador. Hay que asegurarse de que el valor +del <em>Gas usado</em> en cada fila de esta tabla corresponde a una de las mezclas +especificadas en la tabla de <em>Gases disponibles</em>. Se añaden nuevos puntos hasta +que las principales características del buceo estén completas, p.e. el segmento +de tiempo en el fondo y paradas profundas (si se implementan). Se dejan los +restantes puntos del ascenso a <em>Subsurface</em>. En la mayoría de los casos +<em>Subsurface</em> calcula puntos de paso adicionales para completar los requisitos +de descompresión de la inmersión.</p></div> +<div class="paragraph"><p>Los puntos de paso relacionados en el diálogo <em>Puntos del planificador</em> pueden +editarse a mano para obtener una representación precisa del plan. De hecho +podría crearse el plan completo editando los puntos desde el diálogo.</p></div> +<div class="paragraph"><p>Indica cualquier cambio de gas, tal como se explicaba en la sección +<a href="#S_CreateProfile">Crear a mano un perfil de inmersión</a>. Estos cambios deberían +reflejar las botellas y composiciones de gas definidas en la table <em>Gases +disponibles</em>. Si se usan dos o más gases, se sugerirán automáticamente cambios +de gas durante la fase de ascenso a superficie. Sin embargo, estos cambios +pueden borrarse haciendo clic-derecho en el cambio de gas, o pueden crearse +manualmente de la misma forma, haciendo clic-derecho en el punto de paso +adecuado.</p></div> +<div class="paragraph"><p>A continuación hay un ejemplo de planificación de inmersión a 45m usando EAN26, +seguido de un ascenso usando EAN50:</p></div> +<div class="imageblock" style="text-align:center;"> +<div class="content"> +<img src="images/DivePlanner2_f20.jpg" alt="FIGURA: Planificar una inmersión: construcción" /> +</div> +</div> +<div class="paragraph"><p>Una vez que lo anterior se ha completado, se puede guardar clicando el botón +<em>Guardar</em> arriba en el centro del panel del planificador. El plan de buceo +guardado aparecerá en el panel <strong>Lista de Inmersiones</strong>.</p></div> +<div class="paragraph"><p><strong>Los detalles del plan de buceo</strong></p></div> +<div class="paragraph"><p>En la parte inferior derecha del planificador, bajo el encabezamiento <em>Detalles +del plan de buceo</em>, se proporcionan los detalles exactos del plan de inmersión. +Estos detalles pueden modificarse seleccionando cualquiera de las opciones bajo +el encabezamiento <em>Notas</em> del planificador, justo a la izquierda +del anterior. Si se solicita un <em>Plan de buceo detallado</em>, se obtendrá un plan +detallado al nivel de oraciones. Si cualquiera de los límites especificados se +sobrepasa, se obtendrá un mensaje de aviso bajo la información del plan.</p></div> +<div class="paragraph"><p>Si se selecciona la opción <em>Mostrar duración de segmentos</em>, se indicará la +duración de cada segmento de profundidad en los <em>Detalles del plan de buceo</em>. +Esta duración INCLUYE el tiempo de transición hasta llegar al nivel. Sin +embargo, si se selecciona <em>Mostrar transiciones en deco</em>, las transiciones se +muestran separadamente de las duraciones de las paradas en cada nivel.</p></div> +</div> +</div> +<div class="sect2"> +<h3 id="_planificar_inmersiones_con_pscr">14.3. Planificar inmersiones con pSCR</h3> +<div class="paragraph"><p>Para planificar una inmersión usando un rebreather pasivo de circuito +semi-cerrado, selecciona <em>pSCR</em> en lugar de <em>Circuito abierto</em> en la lista +desplegable. +Los parámetros para la inmersción con pSCR se pueden ajustar seleccionando +<em>Archivo → Preferencias → Gráfico</em> desde el menú principal, donde el cálculo +de consumo de gas tiene en cuenta el ratio de vertido (por defecto 10:1) así +como el ratio de metabolismo. El cálculo también tiene en cuenta la pérdida +de oxígeno por la boquilla del rebreather. Si la pO<sub>2</sub> cae por debajo de lo que +se considera un valor seguro, aparecerá un aviso en los <em>Detalles del plan de +buceo</em>. Una configuración típica con pSCR es con una sola botella y una o más +botellas de emergencia. Así pues, el ajuste de las tablas de <em>Gases disponibles</em> +y <em>Puntos del planificador</em> son muy similares a las de un plan con CCR, como se +ha descrito anteriormente. Sin embargo, no se especifican setpoints de oxígeno +en las inmersiones con pSCR. A continuación hay un plan de inmersión para un +buceo con pSCR. El buceo es comparable al anterior con CCR, pero hay que hacer +notar la mayor duración del ascenso debido al menor contenido de oxígeno en el +circuito por la caída de oxígeno en la boquilla del equipo pSCR.</p></div> +<div class="imageblock" style="text-align:center;"> +<div class="content"> +<img src="images/Planner_pSCR1_f20.jpg" alt="FIGURE: Planning a pSCR dive: setup" /> +</div> +</div> +</div> +<div class="sect2"> +<h3 id="_planificar_inmersiones_con_ccr">14.4. Planificar inmersiones con CCR</h3> +<div class="paragraph"><p>Para planificar una inmersión utilizando un rebreather de circuito cerrado, +selecciona la opción <em>CCR</em> en la lista desplegable (en un circulo azul en la +imagen a continuación.</p></div> +<div class="paragraph"><p><strong>Gases disponibles</strong>: en la tabla de <em>Gases disponibles</em>, introduce los datos de +la botella de diluyente y las de bail-out. NO indiques información para la +botella de oxígeno, ya que está implícita al haber seleccionado <em>CCR</em>.</p></div> +<div class="paragraph"><p><strong>Introducir setpoints</strong>: Especifica un setpoint por defecto en la pestaña de +Preferencias seleccionando <em>Archivo → Preferencias → Gráfico</em> desde el menú +principal. Todos los segmentos introducidos por el usuario en los <em>Puntos del +planificador</em> utilizan el valor del setpoint por defecto. Luego se pueden +especificar diferentes setpoints para los diferentes segmentos en la tabla. +Un setpoint cero significa que el buceador ha pasado a circuito abierto para +el segmento en que se ha indicado. La descompresión siempre se calcula usando +el setpoint del último segmento que se haya añadido manualmente. De esta forma, +si se desea planificar un ascenso de emergencia, se añadiría un segmento de un +minuto al final de la inmersión con un setpoint de valor cero. El algoritmo de +descompresión no cambia de mezclas automáticamente mientras se está en modo CCR +pero, desde luego, lo hace para ascensos de emergencia en circuito abierto.</p></div> +<div class="paragraph"><p>El perfil para una inmersión con CCR puede parecerse a la imagen a continuación</p></div> +<div class="imageblock" style="text-align:center;"> +<div class="content"> +<img src="images/Planner_CCR1_f20.jpg" alt="FIGURE: Planning a CCR dive: setup" /> +</div> +</div> +<div class="paragraph"><p>Fíjate que, en los <em>Detalles del plan de buceo</em>, no se calcula el consumo de +gas para un segmento en CCR, por tanto, lo normal es obtener valores de 0 l.</p></div> +</div> +<div class="sect2"> +<h3 id="S_Replan">14.5. Modificar un plan de inmersión existente</h3> +<div class="paragraph"><p>Normalmente, cuando se ha guardado un plan de inmersión, se encuentra disponible +desde la <strong>Lista de Inmersiones</strong> como cualquier buceo. Desde la <strong>Lista de +Inmersiones</strong> no hay forma de cambiar un plan. Para efectuar cambios a un plan de +buceo, selecciónalo en la <strong>Lista de Inmersiones</strong>, luego, desde el menú principal +selecciona <em>Registro → Re-planificar inmersión</em>, con ello se abrirá el plan en +el planificador, permitiendo hacer las modificaciones oportunas y guardarlas de +la forma habitual.</p></div> +</div> +<div class="sect2"> +<h3 id="_planificar_inmersiones_sucesivas">14.6. Planificar inmersiones sucesivas</h3> +<div class="paragraph"><p>Se pueden planear fácilmente inmersiones sucesivas si la fecha y hora de las +mismas se especifican correctamente en el campo arriba a la izquierda <em>Hora de +inicio</em>. <em>SUbsurface</em> calcula las cargas de gases inertes de la primera +inmersión y su efecto se evalúa en las posteriores.</p></div> +<div class="paragraph"><p>Si se acaba de completar una inmersión larga/profunda y se está planificando +otra, se selecciona de la <strong>Lista de inmersiones</strong> la que se acaba de completar y +se activa el planificador. Dependiendo de la hora de inicio del buceo planeado, +el planificador toma en cuenta la carga de gas en la que se ha incurrido durante +la inmersión completada y permite planear con estas limitaciones.</p></div> +<div class="paragraph"><p>Si solo se usan unas pocas configuraciones (p.e. en GUE), puede crearse una +plantilla de acuerdo con una de las configuraciones. Si ahora se desea planear +una inmersión usando esta configuración, simplemente se selecciona la plantilla +de la <strong>Lista de inmersiones</strong> y se activa el planificador: el planificador tendrá +en cuenta la configuración de la plantilla seleccionada.</p></div> +</div> +<div class="sect2"> +<h3 id="_imprimir_el_plan_de_inmersion">14.7. Imprimir el plan de inmersión</h3> +<div class="paragraph"><p>Seleccionar el botón <em>Imprimir</em> permite imprimir los <em>Detalles del plan de +buceo</em> para unas "wet notes". También se pueden copiar y pegar los <em>Detalles del +plan de buceo</em> para incluirlos en un archivo de texto o un procesador de +textos.</p></div> +<div class="paragraph"><p>Los planes de inmersión tienen muchas características en común con los registros +de buceo (perfil, notas, etc). Despues de haber guardado un plan, los detalles y +los calculos de gas quedan almacenados en la pestaña <strong>Notas</strong>. +Mientras se está diseñando un plan, se puede imprimir utilizando el botón +<em>Imprimir</em> del planificador. Esto imprimirá los detalles y cálculos de gases del +panel <em>Detalles del plan de inmersión</em> del planificador. Sin embargo, tras haber +sido guardado, aparece de una forma muy similar a una anotación en el diario y +no se puede acceder a los cáculos de gas de la misma forma que durante el proceso +de planificación. En esta situación, la única manera de imprimir el plan es usar +<em>Archivo → Imprimir</em> en el menú principal, igual que haríamos para imprimir un +registro de inmersión.</p></div> +</div> +</div> +</div> +<div class="sect1"> +<h2 id="_descripcion_de_las_opciones_del_menu_principal_de_em_subsurface_em">15. Descripción de las opciones del menú principal de <em>Subsurface</em></h2> +<div class="sectionbody"> +<div class="paragraph"><p>Esta sección describe las funciones y manejo de las opciones del menú principal +de <em>Subsurface</em>. Varias de las opciones que veremos luego son links a secciones +de este manual que describen las operaciones con más detalle.</p></div> +<div class="sect2"> +<h3 id="_archivo">15.1. Archivo</h3> +<div class="ulist"><ul> +<li> +<p> +<a href="#S_NewLogbook"><em>NuevoRegistro</em></a> - Cierra el diario abierto en estos momentos + y limpia toda la información. +</p> +</li> +<li> +<p> +<em>Abrir Registro</em> - Abre el navegador de archivos para seleccionar un archivo + de registro que abrir. +</p> +</li> +<li> +<p> +<em>Abrir almacenamiento en la nube</em> - Abre el diario previamente configurado en + <a href="#S_Cloud_storage"><em>Almacenamiento en la nube</em></a>. +</p> +</li> +<li> +<p> +<em>Guardar</em> - Guarda el diario abierto en estos momentos. +</p> +</li> +<li> +<p> +<em>Guardar en almacenamiento en la nube</em> - Guarda el diario actual en el + <a href="#S_Cloud_storage"><em>Almacenamiento en la nube</em></a>. +</p> +</li> +<li> +<p> +<em>Guardar como</em> - Guarda el diario actual con un nombre de archivo diferente. +</p> +</li> +<li> +<p> +<em>Cerrar</em> - Cierra el registro de inmersiones abierto en estos momentos. +</p> +</li> +<li> +<p> +<a href="#S_ExportLog"><em>Exportar</em></a> - Exporta el diario abierto actualmente (o las + inmersiones seleccionadas en el diario) a algún otro formato. +</p> +</li> +<li> +<p> +<a href="#S_PrintDivelog"><em>Imprimir</em></a> - Imprime el registro de inmersiones abierto. +</p> +</li> +<li> +<p> +<a href="#S_Preferences"><em>Preferencias</em></a> - Fija las preferencias del usuario de + <em>Subsurface</em>. +</p> +</li> +<li> +<p> +<a href="#S_FindMovedImages"><em>Encontrar imágenes movidas</em></a> - Si las fotos que se + hicieron durante las inmersiones se han cambiado de carpeta o de disco, las + localiza y las une alas inmersiones correspondientes. +</p> +</li> +<li> +<p> +<a href="#S_Configure"><em>Configurar ordenador de buceo</em></a> - Edita la configuración de + un ordenador de buceo. +</p> +</li> +<li> +<p> +<em>Salir</em> - Sale de <em>Subsurface</em>. +</p> +</li> +</ul></div> +</div> +<div class="sect2"> +<h3 id="_importar">15.2. Importar</h3> +<div class="ulist"><ul> +<li> +<p> +<a href="#S_ImportDiveComputer"><em>Importar del ordenador de buceo</em></a> - Descarga + información desde un ordenador de buceo. +</p> +</li> +<li> +<p> +<a href="#Unified_import"><em>Importar Archivos de registro</em></a> - Importa información de + buceo desde un fichero que esté en un formato compatible con <em>Subsurface</em>. +</p> +</li> +<li> +<p> +<a href="#S_Companion"><em>Importar datos GPS del Servicio web de Subsurface</em></a> - Carga + coordenadas GPS desde la app para teléfonos móviles. +</p> +</li> +<li> +<p> +<a href="#S_ImportingDivelogsDe"><em>Importar desde Divelogs.de</em></a> - Importa información + de buceo desde www.divelogs.de. +</p> +</li> +</ul></div> +</div> +<div class="sect2"> +<h3 id="_registro">15.3. Registro</h3> +<div class="ulist"><ul> +<li> +<p> +<a href="#S_EnterData"><em>Añadir inmersión</em></a> - Añade manualmente una nueva inmersión al + panel Lista de inmersiones. +</p> +</li> +<li> +<p> +<em>Editar inmersión</em> - Edita una inmersión cuyo perfil se hizo manualmente y no + descargándola desde un ordenador de buceo. +</p> +</li> +<li> +<p> +<a href="#S_DivePlanner"><em>Planificar inmersión</em></a> - Esta característica permite + planificar inmersiones. +</p> +</li> +<li> +<p> +<a href="#S_Replan"><em>Editar inmersión en planificador</em></a> - Edita un plan de buceo que se ha + guardado en la <strong>Lista de Inmersiones</strong>. +</p> +</li> +<li> +<p> +<a href="#S_CopyComponents"><em>Copiar componentes</em></a> - Al seleccionar esta opción se + se puede copiar información de varios campos de una inmersión al portapapeles. +</p> +</li> +<li> +<p> +<em>Pegar componentes</em> - Pega, en las inmersiones previamente seleccionadas de + la <strong>Lista de Inmersiones</strong>, la información copiada previamente usando la opción + <em>Copiar componentes</em>. +</p> +</li> +<li> +<p> +<a href="#S_Renumber"><em>Renumerar</em></a> - Renumera las inmersiones listadas en el panel + Lista de inmersiones. +</p> +</li> +<li> +<p> +<a href="#S_Group"><em>Auto agrupar</em></a> - Agrupa automáticamente los buceos de la Lista de + inmersiones en viajes de buceo. +</p> +</li> +<li> +<p> +<a href="#S_DeviceNames"><em>Editar nombres de dispositivos</em></a> - Edita los nombres + asignados a los ordenadores de buceo. +</p> +</li> +<li> +<p> +<a href="#S_Filter"><em>Filtrar la lista de inmersiones</em></a> - Seleccionar únicamente + algunas inmersiones, basándose en criterios específicos. +</p> +</li> +</ul></div> +</div> +<div class="sect2"> +<h3 id="_vista">15.4. Vista</h3> +<div class="ulist"><ul> +<li> +<p> +<a href="#S_ViewPanels"><em>Todo</em></a> - Se presentan los cuatro paneles principales de + <em>Subsurface</em> simultáneamente. +</p> +</li> +<li> +<p> +<a href="#S_ViewPanels"><em>Lista_de_inmersiones</em></a> - Se visualiza solo el panel Lista de + inmersiones. +</p> +</li> +<li> +<p> +<a href="#S_ViewPanels"><em>Perfil</em></a> - Se visualiza solo el panel Perfil de inmersión. +</p> +</li> +<li> +<p> +<a href="#S_ViewPanels"><em>Info</em></a> - Se visualiza solo el panel Notas. +</p> +</li> +<li> +<p> +<a href="#S_ViewPanels"><em>Globo</em></a> - Se presenta solo el panel Mapamundi. +</p> +</li> +<li> +<p> +<em>Estadísticas anuales</em> - Muestra estadísticas anuales resumidas sobre las + inmersiones efectuadas en este año y los pasados. +</p> +</li> +<li> +<p> +<em>Anterior ordenador</em> - Si una inmersión se ha registrado con más de un ordenador + de buceo, cambia a los datos del anterior ordenador de buceo. +</p> +</li> +<li> +<p> +<em>Siguiente ordenador</em> - Cambia al siguiente ordenador de buceo. +</p> +</li> +<li> +<p> +<em>Pantalla completa</em> - Activa el modo de pantalla completa. +</p> +</li> +</ul></div> +</div> +<div class="sect2"> +<h3 id="_ayuda">15.5. Ayuda</h3> +<div class="ulist"><ul> +<li> +<p> +<em>Acerca de Subsurface</em> - Muestra un panel con el número de versión de + <em>Subsurface</em> e información de la licencia. +</p> +</li> +<li> +<p> +<em>Comprobar si hay actualizaciones</em> - Encuentra si hay disponible una nueva + versión de <em>Subsurface</em> en la <a href="http://subsurface-divelog.org/">página web de <em>Subsurface</em></a>. +</p> +</li> +<li> +<p> +<a href="#S_UserSurvey"><em>Encuesta de usuarios</em></a> - Ayuda a hacer mejor <em>Subsurface</em> + tomando parte en nuestra encuesta a usuarios, o completando otra si tus hábitos + de buceo han cambiado. +</p> +</li> +<li> +<p> +<em>Manual de usuario</em> - Abre una ventana que muestra este manual. +</p> +</li> +</ul></div> +</div> +</div> +</div> +<div class="sect1"> +<h2 id="_apendice_a_informacion_especifica_del_sistema_operativo_para_importar_inmersiones_desde_un_ordenador_de_buceo">16. APÉNDICE A: Información específica del sistema operativo para importar inmersiones desde un ordenador de buceo.</h2> +<div class="sectionbody"> +<div class="sect2"> +<h3 id="_asegurate_de_que_el_so_tiene_instalados_los_drivers_necesarios">16.1. Asegúrate de que el SO tiene instalados los drivers necesarios</h3> +<div class="admonitionblock"> +<table><tr> +<td class="icon"> +<img src="images/icons/drivers.jpg" alt="Note" /> +</td> +<td class="content">El sistema operativo del ordenador de sobremesa necesita los drivers correctos +para comunicarse con el ordenador de buceo de la forma en que este lo prefiera +(p.e. bluetooth, USB, infrarrojos).</td> +</tr></table> +</div> +<div class="ulist"><ul> +<li> +<p> +En Linux esto significa que el usuario tiene que tener cargados los módulos +del kernel correctos. La mayoría de las distribuciones lo harán automáticamente. +Sin embargo algunos protocolos de comunicación requieren un driver adicional, +especialmente para tecnología poco usada como los infrarojos. +</p> +</li> +<li> +<p> +En Windows, el SO debería ofrecer descargar el driver correcto cuando el +usuario conecte su ordenador de buceo al puerto USB y el sistema operativo vea +el dispositivo por primera vez. +</p> +</li> +<li> +<p> +En un Mac, en ocasiones, el usuario tiene que buscar manualmente el driver +correcto. Por ejemplo, el driver correcto para los dispositivos Mares Puck puede +encontrarse como Mac_OSX_VCP_driver.zip en el +<a href="http://www.silabs.com/support/pages/document-library.aspx?p=Interface&f=USB%20Bridges&pn=CP2101">repositorio +de documentos y software de Silicon Labs</a>. +</p> +</li> +</ul></div> +</div> +<div class="sect2"> +<h3 id="S_HowFindDeviceName">16.2. Como encontrar el nombre de dispositivo para conexiones USB y ajustar sus permisos de escritura</h3> +<div class="admonitionblock"> +<table><tr> +<td class="icon"> +<img src="images/icons/usb.jpg" alt="Note" /> +</td> +<td class="content">Cuando un usuario conecta el ordenador de buceo utilizando un conector USB, +normalmente <em>Subsurface</em> propondrá una lista desplegable que contendrá el nombre +de dispositivo correcto (o punto de montaje para el Uemis Zurich), o +deshabilitará el desplegable de selección si no se necesita ningún nombre. En +los raros casos en que esto no funcione, aquí hay algunas instrucciones sobre +formas de averiguar cual es el nombre de dispositivo.</td> +</tr></table> +</div> +<div class="paragraph"><div class="title">En Windows:</div><p>Simplemente intenta COM1, COM2, etc. La lista desplegable debería contener todos +los dispositivos COM conectados.</p></div> +<div class="paragraph"><div class="title">En MacOS:</div><p>El desplegable debería encontrar todos los ordenadores de buceo conectados.</p></div> +<div class="paragraph"><div class="title">En Linux:</div><p>Hay una forma definitiva de encontrar el puerto:</p></div> +<div class="ulist"><ul> +<li> +<p> +Desconectar el cable USB del ordenador de buceo +</p> +</li> +<li> +<p> +Abrir un terminal +</p> +</li> +<li> +<p> +Teclear el comando: dmesg y pulsar enter +</p> +</li> +<li> +<p> +Conectar el cable USB del ordenador de buceo +</p> +</li> +<li> +<p> +Teclear el comando: dmesg y pulsar enter +</p> +</li> +</ul></div> +<div class="paragraph"><p>En el terminal debería poderse ver un mensaje similar a este:</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>En la tercera línea desde abajo muestra que se detecta el adaptador USB FTDI y +está conctado a <code>ttyUSB3</code> . Ahora puede usarse esta información en el ajuste de +la importación como <code>/dev/ttyUSB3</code> lo que dirigirá a <em>Subsurface</em> al puerto USB +correcto.</p></div> +<div class="paragraph"><p>Asegurarse de que el usuario tiene permisos de escritura en el puerto serie USB:</p></div> +<div class="paragraph"><p>En sistemas operativos tipo Unix los puertos USB solo pueden accederse por +usuarios que sean miembros del grupo dialout. Si uno no es root, puede que no +sea miembro de dicho grupo y no podrá utilizar el puerto USB. Asumamos que el +nombre de usuario de uno es johnB.</p></div> +<div class="ulist"><ul> +<li> +<p> +Como root se teclea: <code>usermod -a -G dialout johnB</code> (usuarios de Ubuntu: <code>sudo +usermod -a -G dialout johnB</code>) . Esto hace a johnB miembro del grupo <code>dialout</code>. +</p> +</li> +<li> +<p> +Teclea: <code>id johnB</code> Esto listará todos los grupos a los que pertenece johnB y +verifica que se ha creado la pertenencia correcta al grupo. El grupo <code>dialout</code> +debería aparecer entre los diferentes IDs. +</p> +</li> +<li> +<p> +En algunas circunstancias, este cambio solo tiene efecto (p.e. en Ubuntu) tras +cerrar sesión y reiniciarla. +</p> +</li> +</ul></div> +<div class="paragraph"><p>Con el nombre de dispositivo apropiado (p.e. <code>/dev/ttyUSB3</code>) y con permisos de +escritura para el puerto USB, el interface del ordenador de buceo puede +conectarse y se debería poder importar las inmersiones.</p></div> +</div> +<div class="sect2"> +<h3 id="S_HowFindBluetoothDeviceName">16.3. Ajustar manualmente dispositivos con bluetooth</h3> +<div class="admonitionblock"> +<table><tr> +<td class="icon"> +<img src="images/icons/bluetooth.jpg" alt="Note" /> +</td> +<td class="content">Para ordenadores de buceo que se comunican por bluetooth como el Heinrichs +Weikamp Frog o el Shearwater Predator, Petrel y Nerd hay un procedimiento distinto +para localizar los nombres de dispositivo con los que se comunicará +<em>Subsurface</em>. En general consiste en estos pasos:</td> +</tr></table> +</div> +<div class="ulist"><ul> +<li> +<p> +<strong>En el ordenador de buceo, tras habilitar Bluetooth, asegurarse que está en +modo Upload</strong> +</p> +</li> +</ul></div> +<div class="paragraph"><p>Para emparejar el ordenador de buceo, consulta la guía de usuario del +fabricante. Si se está usando un Shearwater Predator/Petrel/Nerd, hay que seleccionar +<em>Dive Log → Upload Log</em> y esperar al mensaje <em>Wait PC</em>.</p></div> +<div class="ulist"><ul> +<li> +<p> +<strong>Emparejar el PC con <em>Subsurface</em> con el ordenador de buceo.</strong> +</p> +</li> +</ul></div> +<div class="sect3"> +<h4 id="_en_windows_2">16.3.1. En Windows:</h4> +<div class="paragraph"><p>Probablemente bluetooth ya esté activado. Para emparejar el dispositivo se +selecciona <em>Panel de Control → Dispositivos Bluetooth → Añadir dispositivo +Inalámbrico</em>. Esto debería desplegar un diálogo que mostraría tu ordenador de +buceo (en modo bluetooth) y te permitiría emparejarlo. El ordenador de buceo +debería mostrarse en la lista de dispositivos y podrías hacer clic-derecho en él +y seleccionar <em>Propiedades → Puertos COM</em> para identificar el puerto usado por +tu ordenador de buceo. Si se mostraran varios puertos, utiliza el que diga +"Saliente" en vez de "Entrante".</p></div> +<div class="paragraph"><p>Para descargar a <em>Subsurface</em>, la lista desplegable ya debería contener este +puerto COM. Si no, introdúcelo manualmente.</p></div> +<div class="paragraph"><p>Nota: Si tienes problemas descargando desde tu ordenador de buceo a otro +software después, intenta borrar el emparejamiento y volverlo a hacer.</p></div> +</div> +<div class="sect3"> +<h4 id="_en_macos">16.3.2. En MacOS:</h4> +<div class="paragraph"><p>Clica en el símbolo Bluetooth en la barra de menú y selecciona <em>Configurar +Dispositivo Bluetooth …</em>. Asegúrate de que tu ordenador de buceo está en modo +upload; entonces debería mostrar la lista de dispositivos. Selecciónalo y pasa +por el proceso de emparejamiento. Este paso solo debería se necesario una vez +para la configuración inicial.</p></div> +<div class="paragraph"><p>Una vez que el emparejamiento está completo el dispositivo correcto se mostrará +en el desplegable <em>Dispositivo o punto de montaje</em> del diálogo <strong>Importar</strong> de +<em>Subsurface</em>.</p></div> +</div> +<div class="sect3"> +<h4 id="_en_linux">16.3.3. En Linux</h4> +<div class="paragraph"><p>Asegúrate de que tienes activado el ordenador con <em>Subsurface</em>. En las +distribuciones más habituales esto debería ser cierto de entrada y el +emparejamiento debería se fácil. Por ejemplo, Gnome3 muestra un icono Bluetooth +a la derecha de la barra de tareas, arriba en la pantalla. +Los usuarios han informado de dificultades con algunos controladores de +Bluetooth. Si tienes un controlador incluido en el PC, prueba primero con +este. Es más fácil si quitas cualquier receptor USB que tengas activado. +Si tienes un receptor USB que viniera con el ordenador de buceo, prueba con +este antes que con cualquier otro.</p></div> +<div class="paragraph"><p>Configurar una conexión para descargar inmersiones desde tu ordenador de buceo +con capacidad Bluetooth, tal como el <em>Shearwater Petrel</em>, todavía no es un +proceso automatizado y requerirá generalmente la línea de comandos. +Se trata esencialmente de un proceso en tres pasos.</p></div> +<div class="ulist"><ul> +<li> +<p> +Activar el controlador Bluetooth y emparejarlo con el ordenador de buceo +</p> +</li> +<li> +<p> +Establecer una conexión RFCOMM +</p> +</li> +<li> +<p> +Descargar las inmersiones con <em>Subsurface</em> +</p> +</li> +</ul></div> +<div class="paragraph"><p>Asegurarse de que el ordenador de buceo está en modo "upload". En el <em>Petrel</em> +y <em>Petrel 2</em> y <em>Nerd</em>, navega por el menú, selecciona <em>Dive Log</em>, luego <em>Upload log</em>. En +la pantalla se leerá <em>Initializing</em>, luego <em>Wait PC 3:00</em> e iniciará una cuenta +atrás. Una vez que la conexión esté establecida, en la pantalla se leerá +<em>Wait CMD …</em> y la cuenta atrás seguirá. Cuando se descargue la inmersión a +<em>Subsurface</em> en la pantalla se leerá <em>Sending</em> y luego <em>Sent dive</em>.</p></div> +<div class="paragraph"><p>Para establecer la conexión, accede como root vía <code>sudo</code> o <code>su</code>. +Se necesitan los permisos correctos para descargar las inmersiones al PC. En la +mayoría de los sistemas Linux, esto significa hacerse miembro del grupo dialout +(de forma idéntica como con los ordenadores de buceo que utilizan un puerto USB, +como se describía en la sección anterior). En la línea de comando introduce:</p></div> +<div class="paragraph"><p><code>sudo usermod -a -G dialout username</code></p></div> +<div class="paragraph"><p>Luego desconecta el usuario y vuélvelo a conectar para que tenga efecto la +modificación.</p></div> +<div class="sect4"> +<h5 id="_activar_el_controlador_bluetooth_y_emparejar_el_ordenador_de_buceo">Activar el controlador Bluetooth y emparejar el ordenador de buceo</h5> +<div class="paragraph"><p>Intenta configurar el controlador Bluetooth y emparejar tu ordenador de buceo +utilizando el entorno gráfico del sistema operativo. Tras configurar el +ordenador de buceo en modo "upload", haz clic en el icono Bluetooth en la +barra del sistema y selecciona <em>Añadir nuevo dispositivo</em>. El ordenador de +buceo debería aparecer. Si se pide una contraseña, introduce 0000. Anótate o +copia la dirección MAC de tu ordenador de buceo, que necesitaremos más +adelante, y debería ser de la forma 00:11:22:33:44:55.</p></div> +<div class="paragraph"><p>Si el método gráfico no funcionó, empareja el dispositivo desde la línea de +comandos. Abre un terminal y usa <code>hciconfig</code> para comprobar el estado del +controlador Bluetooth</p></div> +<div class="literalblock"> +<div class="content"> +<pre><code>$ hciconfig +hci0: Type: BR/EDR Bus: USB + BD Address: 01:23:45:67:89:AB ACL MTU: 310:10 SCO MTU: 64:8 + *DOWN* + RX bytes:504 acl:0 sco:0 events:22 errors:0 + TX bytes:92 acl:0 sco:0 commands:21 errors:0</code></pre> +</div></div> +<div class="paragraph"><p>Esto indica un controlador Bluetooth con dirección MAC 01:23:45:67:89:AB, +conectado como hci0. Su estado es DOWN, por ejemplo no activado. Otros +controladores adicionales aparecerían como hci1, etc. Si no había un receptor +Bluetooth conectado al PC en el momento del arranque, hci0 es, probablemente, +el receptor interno. +Ahora conectemos el controlador y activemos la autenticación:</p></div> +<div class="literalblock"> +<div class="content"> +<pre><code>sudo hciconfig hci0 up auth (enter password when prompted) +hciconfig +hci0: Type: BR/EDR Bus: USB + BD Address: 01:23:45:67:89:AB ACL MTU: 310:10 SCO MTU: 64:8 + *UP RUNNING PSCAN AUTH* + RX bytes:1026 acl:0 sco:0 events:47 errors:0 + TX bytes:449 acl:0 sco:0 commands:46 errors:0</code></pre> +</div></div> +<div class="paragraph"><p>Comprueba que el estado ahora incluye <code><em>UP</em>, <em>RUNNING</em> y <em>AUTH</em></code>.</p></div> +<div class="paragraph"><p>If se están ejecutando múltiples controladores, lo más simple es desconectar +los no utilizados, por ejemplo, para <code>hci1</code>:</p></div> +<div class="literalblock"> +<div class="content"> +<pre><code>sudo hciconfig hci1 down</code></pre> +</div></div> +<div class="paragraph"><p>El próximo paso es <em>trust</em> y <em>pair</em> el ordenador de buceo. En distribuciones +con Bluez 5, como Fedora 22, se puede utilizar una herramienta llamada +<code>blutoothctl</code>, que lanzará su propia linea de comandos.</p></div> +<div class="literalblock"> +<div class="content"> +<pre><code>bluetoothctl +[NEW] Controller 01:23:45:67:89:AB localhost.localdomain [default] +[bluetooth]# agent on +Agent registered +[bluetooth]# default-agent +Default agent request successful +[bluetooth]# scan on <----now set your dive computer to upload mode +Discovery started +[CHG] Controller 01:23:45:67:89:AB Discovering: yes +[NEW] Device 00:11:22:33:44:55 Petrel +[bluetooth]# trust 00:11:22:33:44:55 <----you can use the tab key to autocomplete the MAC address +[CHG] Device 00:11:22:33:44:55 Trusted: yes +Changing 00:11:22:33:44:55 trust succeeded +[bluetooth]# pair 00:11:22:33:44:55 +Attempting to pair with 00:11:22:33:44:55 +[CHG] Device 00:11:22:33:44:55 Connected: yes +[CHG] Device 00:11:22:33:44:55 UUIDs: 00001101-0000-1000-8000-0089abc12345 +[CHG] Device 00:11:22:33:44:55 Paired: yes +Pairing successful +[CHG] Device 00:11:22:33:44:55 Connected: no</code></pre> +</div></div> +<div class="paragraph"><p>Si se solicita una contraseña, introduce 0000. Está bien aunque la última +línea diga <em>Connected: no</em>. La parte importante es la anterior <code>Pairing +successful</code>.</p></div> +<div class="paragraph"><p>Si el sistema tiene Bluez 4 (p.e. Ubuntu 12.04 a 15.04), probablemente no haya +<code>bluetoothctl</code>, sino un script llamado <code>bluez-simple-agent</code>.</p></div> +<div class="literalblock"> +<div class="content"> +<pre><code>hcitool -i hci0 scanning +Scanning ... + 00:11:22:33:44:55 Petrel + bluez-simple-agent hci0 00:11:22:33:44:55</code></pre> +</div></div> +<div class="paragraph"><p>Una vez que el ordenador esté emparejado, configura la conexión RFCOMM.</p></div> +</div> +<div class="sect4"> +<h5 id="_establecer_la_conexion_rfcomm">Establecer la conexión RFCOMM</h5> +<div class="paragraph"><p>El comando para establecer una conexión RFCOMM es:</p></div> +<div class="paragraph"><p><code>sudo rfcomm -i <controller> connect <dev> <bdaddr> [channel]</code></p></div> +<div class="ulist"><ul> +<li> +<p> +<code><controller></code> es el controlador Bluetooth, <code>hci0</code>. +</p> +</li> +<li> +<p> +<code><dev></code> es el dispositivo RFCOMM, <code>rfcomm0</code> +</p> +</li> +<li> +<p> +<code><bdaddr></code> es la dirección MAC del ordenador de buceo, +00:11:22:33:44:55 +</p> +</li> +<li> +<p> +<code>[channel]</code> es el canal Bluetooth al que nos queremos conectar. +</p> +</li> +</ul></div> +<div class="paragraph"><p>Si se omite el canal, se asume el 1. Basándonos en un número limitado de +informaciones de usuarios el canal apropiado para el ordenador de buceo, +probablemente sea:</p></div> +<div class="ulist"><ul> +<li> +<p> +<em>Shearwater Petrel 1</em>: channel 1 +</p> +</li> +<li> +<p> +<em>Shearwater Petrel 2</em>: channel 5 +</p> +</li> +<li> +<p> +<em>Shearwater Nerd</em>: channel 5 +</p> +</li> +<li> +<p> +<em>Heinrichs-Weikamp OSTC Sport</em>: channel 1 +</p> +</li> +</ul></div> +<div class="paragraph"><p>P.e. para conectar un <em>Shearwater Petrel 2</em>, ajusta el ordenador de buceo a +modo "upload" e introduce:</p></div> +<div class="literalblock"> +<div class="content"> +<pre><code>sudo rfcomm -i hci0 connect rfcomm0 00:11:22:33:44:55 5</code></pre> +</div></div> +<div class="paragraph"><p>(introduce una contraseña, probablemente 0000, cuando se solicite) +Se obtendrá la respuesta:</p></div> +<div class="literalblock"> +<div class="content"> +<pre><code>Connected /dev/rfcomm0 to 00:11:22:33:44:55 on channel 5 +Press CTRL-C for hangup</code></pre> +</div></div> +<div class="paragraph"><p>Para conectar un <code>Shearwater Petrel 1</code> o <code>H&W OSTC Sport</code>, ajusta el ordenador +de buceo a modo "upload" e introduce:</p></div> +<div class="literalblock"> +<div class="content"> +<pre><code>sudo rfcomm -i hci0 connect rfcomm0 00:11:22:33:44:55 (intruduce el password, probablemente 0000, cuando se solicite) +Connected /dev/rfcomm0 to 00:11:22:33:44:55 on channel 1 +Press CTRL-C for hangup</code></pre> +</div></div> +<div class="paragraph"><p>Si se desconoce el canal específico de un ordenador de buceo, o el canal de la +lista anterior no funciona, el comando <code>sdptool records</code> debería ayudar a dar +con el canal apropiado, la salida a continuación es para un Petrel 2:</p></div> +<div class="literalblock"> +<div class="content"> +<pre><code>sdptool -i hci0 records 00:11:22:33:44:55 +Service Name: Serial Port +Service RecHandle: 0x10000 +Service Class ID List: + "Serial Port" (0x1101) + Protocol Descriptor List: + "L2CAP" (0x0100) + "RFCOMM" (0x0003) + Channel: 5</code></pre> +</div></div> +<div class="paragraph"><p>En el caso de ordenadores de buceo Bluetooth que no estén incluidos en la lista +anterior, por favor, informa a los desarrolladores de Subsurface a través del +foro de usuarios o de la lista de correo <em>subsurface@subsurface-divelog.org</em>.</p></div> +</div> +<div class="sect4"> +<h5 id="_descargar_las_inmersiones_con_subsurface">Descargar las inmersiones con Subsurface</h5> +<div class="paragraph"><p>Tras establecer la conexión RFCOMM y mientras esta corriendo la cuenta atrás +del ordenador de buceo, ves a <em>Subsurface</em>, selecciona desde el menú principal +<em>Importar → Importar del ordenador de buceo</em> y selecciona el fabricante +adecuado (p.e. <em>Shearwater</em>), el ordenador de buceo (p.e. <em>Petrel</em>), el punto +de montaje o dispositivo (p.e. <em>/dev/rfcomm0</em>) y pulsa <em>Descargar</em>.</p></div> +</div> +</div> +</div> +</div> +</div> +<div class="sect1"> +<h2 id="_appendix_b_dive_computer_specific_information_for_importing_dive_information">17. APÉNDICE B: Información específica por ordenadores de buceo.</h2> +<div class="sectionbody"> +<div class="sect2"> +<h3 id="S_ImportUemis">17.1. Importar desde un 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> descarga la información guardada en el SDA (el sistema de archivos +interno del Uemis) incluyendo información sobre puntos de buceo y equipo. La +información sobre el compañero aún no se puede descargar. Se hace de forma muy +similar a un ordenador de buceo con conexión USB (el Uemis es uno de los que se +recargan cuando están conectados al puerto USB). La principal diferencia es que +no se introduce un nombre de dispositivo, sino la ubicación donde se montará el +sistema de ficheros UEMISSDA una vez conectado tu ordenador de buceo. En Windows +este es una letra de disco (a menudo <em>E:</em> o <em>F:</em>), en un Mac este es +<em>/Volumes/UEMISSDA</em> y en sistemas Linux varía dependiendo de la distribución +utilizada. En Fedora habitualmente es +<em>/var/run/media/<nombre_usuario>/UEMISSDA</em>. En todos los casos <em>Subsurface</em> +debería sugerir la ubicación correcta en la lista desplegable.</td> +</tr></table> +</div> +<div class="paragraph"><p>Tras seleccionar el nombre anterior como nombre de dispositivo, se pueden +descargar las inmersiones del Uemis Zurich. Un problema técnico con la +implementación de descargas en el Uemis Zurich (es una limitación del firmware, +no un problema de <em>Subsurface</em>) es que no se pueden descargar más de 40/50 +buceos sin quedarse sin memoria en el SDA. Esto, usualmente, solo pasará la +primera vez que se descarguen inmersiones del Uemis Zurich (normalmente, al +descargar al final de un día o incluso de un viaje la capacidad será +suficiente). Si <em>Subsurface</em> muestra el error de que el ordenador de buceo se ha +quedado sin espacio la solución es directa. Desconectar el SDA, apágarlo y +volverlo a encender, y reconectarlo. Ahora se puede reintentar (o iniciar una +nueva sesión de descarga) y continuará donde paró la última vez. Puede que se +tenga que repetir esta operación más de una vez dependiendo de cuantos buceos +haya guardados en el ordenador.</p></div> +</div> +<div class="sect2"> +<h3 id="S_ImportingGalileo">17.2. Importar buceos desde el Galileo de Uwatec</h3> +<div class="admonitionblock"> +<table><tr> +<td class="icon"> +<img src="images/icons/Galileo.jpg" alt="Note" /> +</td> +<td class="content">Los ordenadores de buceo Galileo de Uwatec usan comunicaciones por infrarrojos +(IrDA) entre el dispositivo y <em>Subsurface</em>. El hardware de Uwatec utiliza un USB +basado en le protocolo serie/infrarrojo (SIR) y el controlador IrDA MSC7780 +fabricado por MosChip y comercializado por Scubapro y algunas compañías de +electrónica. En Linux, el kernel ya proporciona comunicación usando el protocolo +IrDA. Sin embargo, el usuario necesita cargar adicionalmente un driver para el +interface IrDA con el ordenador de buceo. La forma más fácil es cargar el +paquete <strong>irda-tools</strong> del <a href="http://irda.sourceforge.net/docs/startirda.html">Linux +IrDA Project</a>. Tras la instalación de irda-tools, el <strong>usuario root</strong> puede +especificar un nombre de dispositivo desde la consola así:</td> +</tr></table> +</div> +<div class="paragraph"><p><code>irattach irda0</code></p></div> +<div class="paragraph"><p>Después de ejecutar este comando, <em>Subsurface</em> reconocerá el ordenador Galileo y +descargará la información de buceo.</p></div> +<div class="paragraph"><p>En Windows existe una situación similar. Hay drivers para el MCS7780 disponibles +en algunos sitios de internet p.e. +<a href="http://www.drivers-download.com/Drv/MosChip/MCS7780/">www.drivers-download.com</a>. +También se pueden encontrar drivers IrDA basados en Windows, para los +ordenadores Uwatec en el sitio web de ScubaPro, pudiendo encontrarlos en la +página de descargas del software SmarTrak.</p></div> +<div class="paragraph"><p>Para el Mac de Apple, la comunicación IrDA vía MCS7780 no está disponible para +OSX 10.6 o superior.</p></div> +</div> +<div class="sect2"> +<h3 id="S_ImportingDR5">17.3. Importar buceos desde 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">El H&W DR5 se monta como un disco USB y guarda un fichero UDDF para cada +buceo. Marca todas las inmersiones que quieras abrir o importar. Nota: El DR5 no +parece conservar factores de gradiente ni información de deco, por lo que +<em>Subsurface</em> no puede mostrarla. Ajusta los factores de gradiente en +<em>Subsurface</em> en <strong>Preferencias</strong> para generar una capa de deco en el panel del +<strong>Perfil</strong>. Observa que la deco calculada por <em>Subsurface</em> diferirá, con toda +seguridad, de la calculada por el DR5.</td> +</tr></table> +</div> +</div> +<div class="sect2"> +<h3 id="S_ImportingXDeep">17.4. Importar desde xDEEP BLACK</h3> +<div class="admonitionblock"> +<table><tr> +<td class="icon"> +<img src="images/icons/HW_xdeepblack.jpg" alt="Note" /> +</td> +<td class="content">Cada inmersión se ha de guardar individualmente como archivo UDDF utilizando la +opción "Exportar a UDDF" en el menú del logbook del BLACK. Al montar el BLACK +como disco USB, los archivos UDDF están disponibles en el directorio LOGBOOK. +Nota: El xDEEP BLACK guarda el LND pero no parece guardar factores de gradiente +ni información sobre deco, por lo que <em>Subsurface</em> no puede mostralos. Ajusta +los factores de gradiente en <em>Gráfico</em> en las <em>Preferencias</em> para generar una +capa de deco en el <strong>Perfil deinmersión</strong> de <em>Subsurface</em> pero fíjate que la +deco calculada por <em>Subsurface</em> diferirá con toda probabilidad de la que +mostraría el xDEEP BLACK.</td> +</tr></table> +</div> +</div> +<div class="sect2"> +<h3 id="_importar_del_shearwater_predator_petrel_nerd_usando_bluetooth">17.5. Importar del Shearwater Predator/Petrel/Nerd usando Bluetooth</h3> +<div class="admonitionblock"> +<table><tr> +<td class="icon"> +<img src="images/icons/predator.jpg" alt="Note" /> +</td> +<td class="content">En la sección anterior, <a href="#S_Bluetooth"><em>Conectar Subsurface a ordenadores de buceo con Bluetooth</em></a> +se facilitan instrucciones específicas para descargar inmersiones usando Bluetooth.</td> +</tr></table> +</div> +</div> +<div class="sect2"> +<h3 id="S_PoseidonMkVI">17.6. Importar desde el Poseidon MKVI Discovery</h3> +<div class="admonitionblock"> +<table><tr> +<td class="icon"> +<img src="images/MkVI.jpeg" alt="Note" /> +</td> +<td class="content">La descarga de diarios desde el MKVI se realiza utilizando un adaptador de +comunicaciones personalizado y el <em>Poseidon PC Configuration Software</em>, que +se obtiene al adquirir el equipo MKVI. La última es una aplicación de +windows que permite configurar el equipo y guardar los diarios. La comunicación +entre el ordenador de buceo y el PC utiliza el protocolo IrDA de infrarrojos. +Solo se pueden descargar datos de una inmersión cada vez e incluyen tres +archivos:</td> +</tr></table> +</div> +<div class="ulist"><ul> +<li> +<p> +Configuración de ajustes para la inmersión y parámetros clave de la misma (es + el archivo con extensión .txt). +</p> +</li> +<li> +<p> +Detalles del diario (archivo con extensión .csv). +</p> +</li> +<li> +<p> +Diario en formato Redbook (archivo con extensión .cvsr). Es una versión +comprimida del diario utilizando un formato propio. +</p> +</li> +</ul></div> +<div class="paragraph"><p><em>Subsurface</em> accede a los archivos .txt y .csv para obtener información.</p></div> +</div> +<div class="sect2"> +<h3 id="_importar_desde_el_ccr_apd_inspiration">17.7. Importar desde el CCR APD Inspiration</h3> +<div class="admonitionblock"> +<table><tr> +<td class="icon"> +<img src="images/APDComputer.jpg" alt="Note" /> +</td> +<td class="content">Los diarios del ordenador de buceo de un APD Inspiration o similar, se +descargan utilizando un adaptador y el <em>AP Communicator</em>, obtenidos al comprar +el equipo. Los diarios se pueden visualizar utilizando el <em>AP Log Viewer</em> desde +Windows o Mac/OS. Sin embargo, los diarios de APD se pueden ver o manejar desde +<em>Subsurface</em> (junto a buceos en los que se haya utilizado otros muchos tipos de +ordenador de buceo). Los diarios de APD Inspiration se importan a <em>Subsurface</em> +como sigue:</td> +</tr></table> +</div> +<div class="ulist"><ul> +<li> +<p> +Descargar la inmersión usando <em>AP Communicator</em>. +</p> +</li> +<li> +<p> +Abrir una inmersión con el <em>AP Log Viewer</em>. +</p> +</li> +<li> +<p> +Seleccionar la pestaña llamada <em>Datos</em> (<em>Data</em>). +</p> +</li> +<li> +<p> +Con los datos del diario "en crudo" mostrados en pantalla, pulsar en + <em>Copiar al portapapeles</em>. +</p> +</li> +<li> +<p> +Abrir un editor de texto (p.e. Notepad en windows o TextWrangler en Mac). +</p> +</li> +<li> +<p> +Copiar el contenido del portapapeles al editor y guardar el archivo de texto + con extensión de archivo <em>.apd</em> +</p> +</li> +<li> +<p> +Desde Subsurface, seleccionar <em>Importar → Importar archivos de registro</em> + para abrir el <a href="#Unified_import">diálogo de importación universal</a>. +</p> +</li> +<li> +<p> +En la lista desplegable de abajo del diálogo (llamada <em>Filtro:</em>) seleccionar "APD log viewer". +</p> +</li> +<li> +<p> +En la lista de nombres de archivo, seleccionar el archivo <em>.apd</em> que acabamos + de crear y se abrirá un diálogo de importación que mostrará los ajustes por + defecto para los datos en un archivo <em>.apd</em>. Si es necesario algún cambio + hazlo como en <a href="#S_ImportingCSVDives">CSV imports</a>. +</p> +</li> +</ul></div> +<div class="imageblock" style="text-align:center;"> +<div class="content"> +<img src="images/APD_CSVimportF22.jpg" alt="Figure: APD log viewer import" /> +</div> +</div> +<div class="ulist"><ul> +<li> +<p> +El primer desplegable a la izquierda en el panel de importación nos permite +el ordenador de buceo APD del que importar el registro. Por defecto es DC1, el +primero de los dos ordenadores que usa el APD. Es posible importar secuencialmente +los datos de ambos ordenadores, importando primero el DC1 y luego el DC2. +(<strong>Truco</strong>: Los registros de ambos ordenadores se pueden visualizar seleccionando + <em>Vista → Siguiente Ordenador</em> desde el menú principal, o situando el cursor + sobre el perfil y pulsando la flecha derecha/izquierda). Pulsa el botón OK en +la parte de debajo del panel. +</p> +</li> +</ul></div> +<div class="paragraph"><p>El diario de APD aparecerá en <em>Subsurface</em>. El techo generado por el ordenador +Inspiration puede visualizarse seleccionando el correspondiente botón de la +izquierda del <strong>Perfil de inmersión</strong>. Los datos de presión de las botellas no +se registran en el equipo APD pero pueden completarse a mano desde la pestaña +<strong>Equipo</strong>.</p></div> +</div> +</div> +</div> +<div class="sect1"> +<h2 id="_apendice_c_exportar_informacion_de_diarios_desde_otros_softwares_externos">18. APÉNDICE C: Exportar información de diarios desde otros softwares externos.</h2> +<div class="sectionbody"> +<div class="paragraph"><p>La importación de datos de diarios de buceos desde softwares externos se +efectúa, habitualmente, utilizando el dialogo que resulta de seleccionar +<em>Importar</em> desde el menú principal y luego Importar archivos de registro. Este +proceso se efectúa en un solo paso y puede obtenerse más información +<a href="#Unified_import">aquí</a> . Sin embargo, en algunos casos, puede ser necesario +efectuar dos pasos:</p></div> +<div class="olist arabic"><ol class="arabic"> +<li> +<p> +Exportar los datos del diario externo a un formato accesible por + <em>Subsurface</em>. +</p> +</li> +<li> +<p> +Importar el diario accesible a <em>Subsurface</em>. +</p> +</li> +</ol></div> +<div class="paragraph"><p>Este apéndice proporciona algo de información sobre como exportar datos de +diarios desde softwares externos. Los procedimientos a continuación se aplican +mayormente en Linux y/o Windows.</p></div> +<div class="sect2"> +<h3 id="S_ImportingDivesSuunto">18.1. Exportar desde <strong>Suunto Divemanager (DM3, DM4 o DM5)</strong></h3> +<div class="admonitionblock"> +<table><tr> +<td class="icon"> +<img src="images/icons/suuntologo.jpg" alt="Note" /> +</td> +<td class="content">Divemanager es una aplicación en MS Windows para ordenadores de buceo Suunto. +Divemanager 3 (DM3) es una versión más antigua del software de Suunto. Los +ordenadores de buceo más recientes usan Divemanager 4 o 5 (DM4 o DM5). Las +diferentes versiones de Divemanager usan diferentes métodos y diferentes +nomenclaturas de archivos al exportar datos.</td> +</tr></table> +</div> +<div class="paragraph"><p><strong>Divemanager 3 (DM3):</strong></p></div> +<div class="olist arabic"><ol class="arabic"> +<li> +<p> +Iniciar <em>Suunto Divemanager 3</em> y registrarse con el nombre que contiene los + diarios. +</p> +</li> +<li> +<p> +No iniciar el ayudante de importación para importar inmersiones desde el + ordenador de buceo. +</p> +</li> +<li> +<p> +En el árbol de la izquierda de la ventana del programa, seleccionar las + inmersiones que correspondan. +</p> +</li> +<li> +<p> +De la lista de buceos, seleccionar las inmersiones que se deseará descargar + después: +</p> +<div class="ulist"><ul> +<li> +<p> +Para seleccionar alguna: mantén pulsada la tecla <em>ctrl</em> y haz clic en la + inmersión. +</p> +</li> +<li> +<p> +Para seleccionarlas todas: Selecciona la primera, mantén pulsada la tecla + <em>shift</em> y haz clic en la última inmersión. +</p> +</li> +</ul></div> +</li> +<li> +<p> +Con las inmersiones marcadas se usa el menú <em>File → Export</em> +</p> +</li> +<li> +<p> +Se mostrará el desplegable de exportación. En este desplegable hay un campo + llamado Export Path. +</p> +<div class="ulist"><ul> +<li> +<p> +Haz clic en el botón browse junto al campo Export Path +</p> +<div class="ulist"><ul> +<li> +<p> +Se despliega un navegador de archivos +</p> +</li> +</ul></div> +</li> +<li> +<p> +Navega a la carpeta donde quieras que se guarde el archivo Divelog.SDE +</p> +<div class="ulist"><ul> +<li> +<p> +Opcionalmente cambia el nombre del archivo a guardar. +</p> +</li> +<li> +<p> +Clica <em>Save</em>. +</p> +</li> +</ul></div> +</li> +<li> +<p> +De vuelta en el desplegable de exportación, pulsa el botón <em>Export</em>. +</p> +</li> +</ul></div> +</li> +<li> +<p> +Las inmersiones han quedado exportadas en el archivo Divelogs.SDE. +</p> +</li> +</ol></div> +<div class="paragraph"><p><strong>Divemanager 4 (DM4) y Divemanager 5 (DM5):</strong></p></div> +<div class="paragraph"><p>DM4 y DM5 utilizan idénticos mecanismos para exportar los diarios. +Para exportar un diario desde Divemanager, se necesita localizar la base de +datos DM4/DM5 donde están guardadas las inmersiones. El usuario puede buscar la +base de datos original o hacer una copia de respaldo. A continuación se +describen ambos métodos.</p></div> +<div class="paragraph"><p>Localizar la base de datos Suunto DM4 (o DM5):</p></div> +<div class="olist arabic"><ol class="arabic"> +<li> +<p> +Iniciar Suunto DM4/DM5 +</p> +</li> +<li> +<p> +Seleccionar <em>Help → About</em> (Ayuda → Acerca de) +</p> +</li> +<li> +<p> +Hacer clic en el botón <em>Copy</em> (Copiar) tras el texto <em>Copy log folder path to + clipboard</em> (Copiar la ruta a la carpeta del registro al portapapeles) +</p> +</li> +<li> +<p> +Abrir el explorador de Windows +</p> +</li> +<li> +<p> +Pegar la ruta en la casilla de direcciones en la parte de arriba del + explorador +</p> +</li> +<li> +<p> +La base de datos se llama DM4.db o DM5.db +</p> +</li> +</ol></div> +<div class="paragraph"><p>Hacer una copia de respaldo de la base de datos de Suunto DM4/DM5:</p></div> +<div class="olist arabic"><ol class="arabic"> +<li> +<p> +Iniciar Suunto DM4/DN5 +</p> +</li> +<li> +<p> +Seleccionar <em>File → Create backup</em> (Archivo → Copia de seguridad) +</p> +</li> +<li> +<p> +Desde el menú de archivos, seleccionar la carpeta y el nombre para la copia, +aquí usaremos DM4 (o DM5) con la extensión por defecto .bak +</p> +</li> +<li> +<p> +Clicar <em>Save</em> (Guardar) +</p> +</li> +<li> +<p> +Los buceos se han exportado al archivo DM4.bak (o DM5.bak) +</p> +</li> +</ol></div> +</div> +<div class="sect2"> +<h3 id="Atomic_Export">18.2. Exportar desde Atomic Logbook</h3> +<div class="admonitionblock"> +<table><tr> +<td class="icon"> +<img src="./images/icons/note.png" alt="Note" /> +</td> +<td class="content">Atomic Logbook es un software en Windows de Atomics Aquatics. Permite descargar +información de buceo de los ordenadores Cobalt y Cobalt 2. El archivo se guarda +en una base de datos SQlite en C:\ProgramData\AtomicsAquatics\Cobalt-Logbook\Cobalt.db. +Este archivo se puede importar directamente a <em>Subsurface</em>.</td> +</tr></table> +</div> +</div> +<div class="sect2"> +<h3 id="Mares_Export">18.3. Exportar desde Mares Dive Organiser V2.1</h3> +<div class="admonitionblock"> +<table><tr> +<td class="icon"> +<img src="images/icons/mareslogo.jpg" alt="Note" /> +</td> +<td class="content">Mares Dive Organiser es una aplicación de Windows. El diario de inmersiones se +guarda en una base de datos Microsoft SQL Compact Edition con una extensión de +nombre de archivo <em>.sdf</em>. La base de datos incluye a todos los buceadores +registrados en el Dive Organiser del PC y a todos los ordenadores Mares usados. +La forma más segura de obtener una copia de la base de datos de inmersiones es +exportar la información a otro formato compatible que pueda ser importado a +<em>Subsurface</em>.</td> +</tr></table> +</div> +<div class="olist arabic"><ol class="arabic"> +<li> +<p> +En el Dive Organiser, selecciona <em>Database → Backup</em> en el menú principal y + haz una copia de seguridad de la base de datos en el escritorio. Esto creará un + archivo comprimido DiveOrganiserxxxxx.dbf +</p> +</li> +<li> +<p> +Cambia el nombre del archivo a DiveOrganiserxxxxx.zip. Dentro de una carpeta + comprimida en el archivo .zip, hay otro archivo llamado <em>DiveOrganiser.sdf</em>. +</p> +</li> +<li> +<p> +Extrae a tu escritorio el archivo <em>.sdf</em> desde la carpeta comprimida. +</p> +</li> +<li> +<p> +La password para acceder al archivo .zip es <em>mares</em>. +</p> +</li> +</ol></div> +</div> +<div class="sect2"> +<h3 id="S_ImportingDivingLog">18.4. Exportar desde <strong>DivingLog 5.0 y 6.0</strong></h3> +<div class="admonitionblock"> +<table><tr> +<td class="icon"> +<img src="images/icons/divingloglogo.jpg" alt="Note" /> +</td> +<td class="content">La mejor manera de traer tus diarios desde DivingLog a <em>Subsurface</em> es +convertir la base de datos completa. Esto se debe a que otros formatos de +exportación no incluyen todos los detalles, y careceríamos, por ejemplo, de +cambios de gas e información acerca de que unidades se utilizan. Al importar +la base de datos, toda esta información esta incluida y disponible.</td> +</tr></table> +</div> +<div class="paragraph"><p>Para transferir todos los archivos desde DivingLog a <em>Subsurface</em> haz lo +siguiente:</p></div> +<div class="olist arabic"><ol class="arabic"> +<li> +<p> +En DivingLog abre el menú <em>Archivo → Exportar → SQLite</em> +</p> +</li> +<li> +<p> +Selecciona el botón <em>Ajustes</em> +</p> +</li> +<li> +<p> +Ajusta el <em>RTF2Plaintext</em> a <em>true</em> +</p> +</li> +<li> +<p> +Cierra el diálogo <em>Ajustes</em> +</p> +</li> +<li> +<p> +Pulsa el botón <em>Exportar</em> y selecciona el nombre de archivo +</p> +</li> +</ol></div> +<div class="paragraph"><p>Una vez hecho esto, abre con <em>Subsurface_la base de datos guardada y las +inmersiones se convertirán automáticamente a nuestro formato. El último paso +a efectuar es guardar el diario en _Subsurface</em>.</p></div> +</div> +</div> +</div> +<div class="sect1"> +<h2 id="S_Appendix_D">19. APÉNDICE D: Exportar una hoja de cálculo a formato CSV</h2> +<div class="sectionbody"> +<div class="paragraph"><p>Muchos buceadores mantienen un diario en alguna forma de archivo digital, en +muchos casos en una hoja de cálculo con varios campos de información. Estos +registros se pueden importar con facilidad a <em>Subsurface</em> +una vez que la hoja de cálculo se ha convertido a archivo .CSV . +Esta sección explica el procedimiento para convertir un diario de buceo que +se haya conservado en una hoja de cálculo en un archivo .CSV que se pueda, +posteriormente, importar a <em>Subsurface</em>. +Crear un .CSV es una tarea sencilla, aunque el procedimiento es algo distinto +según el programa de hojas de cálculo que se utilice.</p></div> +<div class="paragraph"><p>El primer paso consiste en organizar los datos en la hoja de cálculo, de forma +que la primera fila contenga los nombres (o títulos) de cada columna y que la +información de cada inmersión ocupe una sola fila. +<em>Subsurface</em> soporta muchos tipos de datos (Número, Fecha, Hora, Duración, +Ubicación, GPS, Prof. máxima, Prof. media, Compañero, Notas, Lastre y Etiquetas). +El usuario puede organizar los datos siguiendo unas sencillas reglas:</p></div> +<div class="olist arabic"><ol class="arabic"> +<li> +<p> +Fecha: Usar uno de los siguientes formatos: aaaa-mm-dd, dd.mm.aaaa o + mm/dd/aaaa +</p> +</li> +<li> +<p> +Duración: El formato debería ser minutos:segundos +</p> +</li> +<li> +<p> +Sistema de unidades: Solo debe usarse un sistema. Evitar la mezcla sistemas. +</p> +</li> +<li> +<p> +Etiquetas y compañeros: los valores deben separarse usando una coma. +</p> +</li> +<li> +<p> +Posición GPS: Se deben utilizar grados decimales, p.e. 30.22496 30.821798 +</p> +</li> +</ol></div> +<div class="sect2"> +<h3 id="_em_libreoffice_calc_em_y_em_openoffice_calc_em">19.1. <em>LibreOffice Calc</em> y <em>OpenOffice Calc</em></h3> +<div class="paragraph"><p>Son aplicaciones de hojas de cálculo de código abierto que forman parte de +suits mayores que, a su vez, también son código abierto. La interacción del +usuario con <em>LibreOffice Calc</em> y _OpenOffice Calc_es muy similar.</p></div> +<div class="paragraph"><p>En LibreOffice Calc el formato de tiempo debe ajustarse a minutos:segundos - +[mm]:ss y las fechas se deben ajustar a aaaa-mm-dd, dd.mm.aaaa o mm/dd/aaaa. +Un diario típico codría parecerse a esto:</p></div> +<div class="imageblock" style="text-align:center;"> +<div class="content"> +<img src="images/LOffice_spreadsheetdata.jpg" alt="FIGURA: Datos de una hoja de cálculo" /> +</div> +</div> +<div class="paragraph"><p>Para exportar los datos en archivo .CSV, desde LibreOffice clicar <em>Archivo → + Guardar como</em>. En el diálogo que se desplegará, seleccionar <em>Texto CSV (.csv)</em> +como tipo de archivo y seleccionar la opción <em>Editar ajustes de filtros</em>.</p></div> +<div class="imageblock" style="text-align:center;"> +<div class="content"> +<img src="images/LOffice_save_as_options.jpg" alt="FIGURA: Opciones de Guardar como" /> +</div> +</div> +<div class="paragraph"><p>Tras seleccionar <em>Guardar</em>, seleccionar el delimitador de campos apropiado +(selecciona <em>TABULADOR</em> para evitar conflictos con las comas cuando estas se +usen como coma decimal), luego seleccionar <em>OK</em>.</p></div> +<div class="imageblock" style="text-align:center;"> +<div class="content"> +<img src="images/LOffice_field_options.jpg" alt="FIGURA: Opciones de campos" /> +</div> +</div> +<div class="paragraph"><p>Se puede verificar el archivo .CSV abriéndolo con un editor de textos y luego +se importaría como se explicó en <a href="#S_ImportingCSVDives">Importar inmersiones desde archivos <em>CSV</em> manuales</a>.</p></div> +</div> +<div class="sect2"> +<h3 id="_microsoft_em_excel_em">19.2. Microsoft <em>Excel</em></h3> +<div class="paragraph"><p>El delimitador de campos (llamado "separador de listas" en los manuales de +Microsoft) no está accesible desde <em>Excel</em> y debe ajustarse desde el <em>Panel de +Control</em>. Tras cambiar el carácter separador todo el software del ordenador con +Windows usará el nuevo carácter como separador. +Se puede volver a cambiar el carácter al inicial siguiendo el mismo sistema.</p></div> +<div class="ulist"><ul> +<li> +<p> +En Microsoft Windows, pulsar el botón <strong>Inicio</strong> y seleccionar el <em>Panel de + Control</em> de la lista de la izquierda. +</p> +</li> +<li> +<p> +Abrir el diálogo <em>Opciones de región y lenguaje</em>. +</p> +</li> +<li> +<p> +Hacer una de las dos siguientes acciones: +</p> +<div class="ulist"><ul> +<li> +<p> +En Windows 7, clicar la pestaña <em>Formatos</em> y luego <em>Personalizar este + formato</em> +</p> +</li> +<li> +<p> +En Windows XP, clicar la pestaña <em>Opciones de región</em> y luego <em>Personalizar</em>. +</p> +</li> +</ul></div> +</li> +<li> +<p> +Teclear un nuevo separador en el <em>Separador de listas</em>. Para utilizar un + tabulador teclea "TAB" en la casilla de texto. +</p> +</li> +<li> +<p> +Pulsar <em>OK</em> dos veces. +</p> +</li> +</ul></div> +<div class="paragraph"><p>A continuación, una imagen del <em>Panel de Control</em>:</p></div> +<div class="imageblock" style="text-align:center;"> +<div class="content"> +<img src="images/Win_SaveCSV2.jpg" alt="FIGURA: Separador de listas en Win" /> +</div> +</div> +<div class="paragraph"><p>Para exportar el archivo en formato CSV:</p></div> +<div class="paragraph"><p>Con el diario abierto en <em>Excel</em>, seleccionar el botón redondo de Windows de +arriba a la izquierda, luego <em>Guardar como</em>.</p></div> +<div class="imageblock" style="text-align:center;"> +<div class="content"> +<img src="images/Win_SaveCSV1.jpg" alt="FIGURA: Opción Guardar como en Excel" /> +</div> +</div> +<div class="paragraph"><p>Clicar en la parte izquierda de la opción <em>Guardar como</em>, <strong>NO</strong> sobre la flecha +de la derecha. Esto desplegará un diálogo para guardar la hoja de cálculo en un +formato alternativo. De la lista desplegable abajo en el diálogo, seleccionar +<em>CSV(delimitado por comas) (*.CSV)</em>. Asegurarse de que se ha seleccionado la +carpeta correcta para guardar el archivo.</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>Seleccionar el botón <em>Guardar</em>. El archivo formateado en <em>CSV</em> se guardará en la +carpeta que se hubiera seleccionado. Se puede verificar el archivo creado con +un editor de textos y luego importar los datos de buceo como se explicó en +<a href="#S_ImportingCSVDives">Importar inmersiones desde archivos <em>CSV</em> manuales</a>.</p></div> +</div> +</div> +</div> +<div class="sect1"> +<h2 id="S_APPENDIX_E">20. APÉNDICE E: Escribir una plantilla de impresión a medida</h2> +<div class="sectionbody"> +<div class="paragraph"><p><em>Subsurface</em> proporciona un mecanismo para crear o modificar plantillas que +permite producir impresiones a medida de los divelogs. Las plantillas escritas +en HTML, y también como sencillo conjunto de instrucciones de Grantlee, se +interpretan y envian a la impresora por <em>Subsurface</em>.</p></div> +<div class="paragraph"><p>Se accede a las plantillas utilizando el diálogo de impresión (imagen <strong>B</strong> a +continuación)</p></div> +<div class="imageblock" style="text-align:center;"> +<div class="content"> +<img src="images/Print1_f22.jpg" alt="FIGURA: Diálogo de impresión" /> +</div> +</div> +<div class="paragraph"><p>Los botones en la parte de abajo de diálogo permiten <em>Editar</em>, <em>Borrar</em>, +<em>Importar</em> y <em>Exportar</em> plantillas (ver imagen <strong>A</strong> anterior). Las plantillas, +nuevas o modificadas, se guardan como archivos HTML en la misma carpeta en la +que está el divelog que se está procesando. Para crear o modificar una plantilla, +selecciona la plantilla <em>Custom</em> de la lista desplegable (imagen <strong>B</strong> anterior) y +pulsa <em>Editar</em>.</p></div> +<div class="paragraph"><p>El panel de edición incluye tres pestañas:</p></div> +<div class="imageblock" style="text-align:center;"> +<div class="content"> +<img src="images/Template1_f22.jpg" alt="FIGURA: Diálogo de edición de plantillas" /> +</div> +</div> +<div class="paragraph"><p>1) La pestaña <em>Estilo</em> (imagen <strong>A</strong> anterior) controla la fuente, el espaciado de + lineas y la plantilla de colores utilizada para imprimir. Los atributos de estilo + son editables. Elige una de las cuatro paletas.</p></div> +<div class="paragraph"><p>2) La pestaña <em>Colores</em> (imagen <strong>B</strong> anterior) permite editar los colores que se + usarán para imprimir el registro. Los colores se pueden modificar: el botón + <em>Editar</em> de la pestaña <em>Colores</em> permite elegir colores arbitrarios para los + diferentes componentes de la impresión.</p></div> +<div class="paragraph"><p>3) La pestaña <em>Plantilla</em> del panel de edición (imagen a continuación) permite crear + una plantilla usando HTML y sentencias de Grantlee. Grantlee proporciona la + habilidad de crear y formatear código HTML de forma muy simple pero muy eficiente + (ver a continuación). El HTML de la plantilla puede editarse y guardarse. La + plantilla salvada se guarda en la carpeta en la que está el divelog con el que + se está trabajando. Por defecto, una plantilla <em>a medida</em> es un esqueleto sin + instrucciones de impresión. La información a imprimir necesita ser especificada + y formateada reemplazando la sección "<!-- Template must be filled -→". + Escribir código HtMl con Grantlee da una libertad ilimitada para elegir lo que + se imprime y como se va a visualizar.</p></div> +<div class="imageblock" style="text-align:center;"> +<div class="content"> +<img src="images/Template2_f22.jpg" alt="FIGURE:Template tab" /> +</div> +</div> +<div class="paragraph"><p>El usuario también puede adaptar las plantillas existentes y guardarlas en la +carpeta donde se halle el divelog (por ejemplo One Dive, Six Dives, Table, etc).</p></div> +<div class="paragraph"><p>Para escribir una plantilla a medida, deben existir los siguientes elementos +para que puedan ser manejadas e interpretadas:</p></div> +<div class="sect2"> +<h3 id="_bucle_principal">20.1. Bucle principal</h3> +<div class="paragraph"><p><em>Subsurface</em> pasa una lista de inmersiones llamada (<strong>dives</strong>) al sistema <em>Grantlee</em>. +Se puede iterar sobre la lista de la siguiente manera:</p></div> +<div class="literalblock"> +<div class="title">template.html</div> +<div class="content"> +<pre><code> {% for dive in dives %} + <h1> {{ dive.number }} </h1> + {% endfor %}</code></pre> +</div></div> +<div class="literalblock"> +<div class="title">output.html</div> +<div class="content"> +<pre><code> <h1> 1 </h1> + <h1> 2 </h1> + <h1> 3 </h1></code></pre> +</div></div> +<div class="paragraph"><p>Se puede encontrar información sobre <em>Grantlee</em> <a href="http://www.grantlee.org/apidox/for_themers.html">aquí</a></p></div> +</div> +<div class="sect2"> +<h3 id="_variables_pasadas_a_grantlee">20.2. Variables pasadas a Grantlee</h3> +<div class="paragraph"><p>Solo se pasa un subconjunto de los datos de una inmersión:</p></div> +<div class="tableblock"> +<table rules="all" +width="100%" +frame="border" +cellspacing="0" cellpadding="4"> +<col width="50%" /> +<col width="50%" /> +<tbody> +<tr> +<td align="left" valign="top"><p class="table"><strong>Nombre</strong></p></td> +<td align="left" valign="top"><p class="table"><strong>Descripción</strong></p></td> +</tr> +<tr> +<td align="left" valign="top"><p class="table">number</p></td> +<td align="left" valign="top"><p class="table">(<strong>int</strong>) número de la inmersión</p></td> +</tr> +<tr> +<td align="left" valign="top"><p class="table">id</p></td> +<td align="left" valign="top"><p class="table">(<strong>int</strong>) diveID único, se usará para descargar el perfil</p></td> +</tr> +<tr> +<td align="left" valign="top"><p class="table">date</p></td> +<td align="left" valign="top"><p class="table">(<strong>string</strong>) fecha de la inmersión</p></td> +</tr> +<tr> +<td align="left" valign="top"><p class="table">time</p></td> +<td align="left" valign="top"><p class="table">(<strong>string</strong>) hora de la inmersión</p></td> +</tr> +<tr> +<td align="left" valign="top"><p class="table">location</p></td> +<td align="left" valign="top"><p class="table">(<strong>string</strong>) ubicación del buceo</p></td> +</tr> +<tr> +<td align="left" valign="top"><p class="table">duration</p></td> +<td align="left" valign="top"><p class="table">(<strong>string</strong>) duración del buceo</p></td> +</tr> +<tr> +<td align="left" valign="top"><p class="table">depth</p></td> +<td align="left" valign="top"><p class="table">(<strong>string</strong>) profundidad de la inmersión</p></td> +</tr> +<tr> +<td align="left" valign="top"><p class="table">divemaster</p></td> +<td align="left" valign="top"><p class="table">(<strong>string</strong>) datos del divemaster</p></td> +</tr> +<tr> +<td align="left" valign="top"><p class="table">buddy</p></td> +<td align="left" valign="top"><p class="table">(<strong>string</strong>) datos del compañero</p></td> +</tr> +<tr> +<td align="left" valign="top"><p class="table">airTemp</p></td> +<td align="left" valign="top"><p class="table">(<strong>string</strong>) temperatura del aire</p></td> +</tr> +<tr> +<td align="left" valign="top"><p class="table">waterTemp</p></td> +<td align="left" valign="top"><p class="table">(<strong>string</strong>) temperatura del agua</p></td> +</tr> +<tr> +<td align="left" valign="top"><p class="table">notes</p></td> +<td align="left" valign="top"><p class="table">(<strong>string</strong>) notas de la inmersión</p></td> +</tr> +<tr> +<td align="left" valign="top"><p class="table">rating</p></td> +<td align="left" valign="top"><p class="table">(<strong>int</strong>) calificación del buceo, varía entre 0 y 5</p></td> +</tr> +<tr> +<td align="left" valign="top"><p class="table">sac</p></td> +<td align="left" valign="top"><p class="table">(<strong>string</strong>) valor del CAS</p></td> +</tr> +<tr> +<td align="left" valign="top"><p class="table">tags</p></td> +<td align="left" valign="top"><p class="table">(<strong>string</strong>) todas las etiquetas de la inmersión empalmadas</p></td> +</tr> +<tr> +<td align="left" valign="top"><p class="table">gas</p></td> +<td align="left" valign="top"><p class="table">(<strong>string</strong>) datos de la botella</p></td> +</tr> +</tbody> +</table> +</div> +<div class="paragraph"><p><em>Subsurface</em> también pasa datos de la plantilla <strong>template_options</strong>. Estos datos +deben usarse como valores <em>CSS</em> para proporcionar una plantilla editable de +forma dinámica. Los datos exportados se muestran en la tabla a continuación:</p></div> +<div class="tableblock"> +<table rules="all" +width="100%" +frame="border" +cellspacing="0" cellpadding="4"> +<col width="50%" /> +<col width="50%" /> +<tbody> +<tr> +<td align="left" valign="top"><p class="table"><strong>Nombre</strong></p></td> +<td align="left" valign="top"><p class="table"><strong>Descripción</strong></p></td> +</tr> +<tr> +<td align="left" valign="top"><p class="table">font</p></td> +<td align="left" valign="top"><p class="table">(<strong>string</strong>) familia de la fuente</p></td> +</tr> +<tr> +<td align="left" valign="top"><p class="table">borderwidth</p></td> +<td align="left" valign="top"><p class="table">(<strong>int</strong>) valor de la anchura del borde, calculado dinámicamente +como 0.1% de la anchura de la página con un valor mínimo de 1px</p></td> +</tr> +<tr> +<td align="left" valign="top"><p class="table">font_size</p></td> +<td align="left" valign="top"><p class="table">(<strong>double</strong>) tamaño de la fuente en vw, varía entre 1.0 y 2.0</p></td> +</tr> +<tr> +<td align="left" valign="top"><p class="table">line_spacing</p></td> +<td align="left" valign="top"><p class="table">(<strong>double</strong>) distancia entre líneas de texto, varía entre 1.0 y 3.0</p></td> +</tr> +<tr> +<td align="left" valign="top"><p class="table">color1</p></td> +<td align="left" valign="top"><p class="table">(<strong>string</strong>) color del fondo</p></td> +</tr> +<tr> +<td align="left" valign="top"><p class="table">color2</p></td> +<td align="left" valign="top"><p class="table">(<strong>string</strong>) color primario de las celdas de la tabla</p></td> +</tr> +<tr> +<td align="left" valign="top"><p class="table">color3</p></td> +<td align="left" valign="top"><p class="table">(<strong>string</strong>) color secundario de las celdas de la tabla</p></td> +</tr> +<tr> +<td align="left" valign="top"><p class="table">color4</p></td> +<td align="left" valign="top"><p class="table">(<strong>string</strong>) color primario del texto</p></td> +</tr> +<tr> +<td align="left" valign="top"><p class="table">color5</p></td> +<td align="left" valign="top"><p class="table">(<strong>string</strong>) color secundario del texto</p></td> +</tr> +<tr> +<td align="left" valign="top"><p class="table">color6</p></td> +<td align="left" valign="top"><p class="table">(<strong>string</strong>) colores de los bordes</p></td> +</tr> +</tbody> +</table> +</div> +<div class="literalblock"> +<div class="title">template.html</div> +<div class="content"> +<pre><code> border-width: {{ template_options.borderwidth }}px;</code></pre> +</div></div> +<div class="literalblock"> +<div class="title">output.html</div> +<div class="content"> +<pre><code> border-width: 3px;</code></pre> +</div></div> +<div class="paragraph"><p>Otra variable que pasa <em>Subsurface</em> es <strong>print_options</strong>. Esta variable solo +contiene un único valor:</p></div> +<div class="tableblock"> +<table rules="all" +width="100%" +frame="border" +cellspacing="0" cellpadding="4"> +<col width="50%" /> +<col width="50%" /> +<tbody> +<tr> +<td align="left" valign="top"><p class="table"><strong>Nombre</strong></p></td> +<td align="left" valign="top"><p class="table"><strong>Descripción</strong></p></td> +</tr> +<tr> +<td align="left" valign="top"><p class="table">grayscale</p></td> +<td align="left" valign="top"><p class="table">Utiliza filtros <em>CSS</em> para convertir la página a escala de grises +(debe añadirse al estilo del cuerpo para activar la impresión en blanco y negro)</p></td> +</tr> +</tbody> +</table> +</div> +<div class="literalblock"> +<div class="title">template.html</div> +<div class="content"> +<pre><code> body { + {{ print_options.grayscale }}; + }</code></pre> +</div></div> +<div class="literalblock"> +<div class="title">output.html</div> +<div class="content"> +<pre><code> body { + -webkit-filter: grayscale(100%); + }</code></pre> +</div></div> +</div> +<div class="sect2"> +<h3 id="_selectores_css_definidos">20.3. Selectores CSS definidos</h3> +<div class="paragraph"><p>Como el perfil se coloca después del renderizado, <em>Subsurface</em> usa unos selectores +<em>CSS</em> especiales para ejecutar algunas búsquedas en la salida HTML. Deben añadirse +los selectores de la siguiente tabla:</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>Selector</strong></p></td> +<td align="left" valign="top"><p class="table"><strong>Tipo</strong></p></td> +<td align="left" valign="top"><p class="table"><strong>Descripción</strong></p></td> +</tr> +<tr> +<td align="left" valign="top"><p class="table">dive_{{ dive.id }}</p></td> +<td align="left" valign="top"><p class="table">id</p></td> +<td align="left" valign="top"><p class="table">se utiliza para descargar el perfil de inmersión +correspondiente</p></td> +</tr> +<tr> +<td align="left" valign="top"><p class="table">diveProfile</p></td> +<td align="left" valign="top"><p class="table">class</p></td> +<td align="left" valign="top"><p class="table">cada div que contendrá un perfil de inmersión debe tener +este selector de clase añadido al selector divee_{{ dive.id }}</p></td> +</tr> +<tr> +<td align="left" valign="top"><p class="table">dontbreak</p></td> +<td align="left" valign="top"><p class="table">class</p></td> +<td align="left" valign="top"><p class="table">evita que el div que tenga esta clase se divida en dos +páginas</p></td> +</tr> +</tbody> +</table> +</div> +<div class="paragraph"><p>IMPORTANTE: Renderizar perfiles de inmersión no está soportado en plantillas +de distribución de flujo (cuando datos-número de buceos = 0).</p></div> +</div> +<div class="sect2"> +<h3 id="_atributos_especiales">20.4. Atributos especiales</h3> +<div class="paragraph"><p>Hay dos formas de renderizar: bien renderizar un número concreto de buceos por +página, bien hacer que <em>Subsurface</em> intente introducir tantas inmersiones como +sea posible en una sola página.</p></div> +<div class="paragraph"><p>El atributo de datos <strong>data-numberofdives</strong> se añade a la etiqueta body para +fijar el modo de renderizado.</p></div> +<div class="ulist"><ul> +<li> +<p> +Renderizar 6 inmersiones por página: +</p> +</li> +</ul></div> +<div class="literalblock"> +<div class="content"> +<pre><code> <body data-numberofdives = 6></code></pre> +</div></div> +<div class="ulist"><ul> +<li> +<p> +Renderizar tantas inmersiones como sea posible: +</p> +</li> +</ul></div> +<div class="literalblock"> +<div class="content"> +<pre><code> <body data-numberofdives = 0></code></pre> +</div></div> +<div class="paragraph"><p>IMPORTANTE: Todas las unidades CSS deben estar en longitudes relativas para +imprimir en cualquier tamaño de página.</p></div> +</div> +</div> +</div> +<div class="sect1"> +<h2 id="S_APPENDIX_F">21. APÉNDICE F: Preguntas Frecuentes</h2> +<div class="sectionbody"> +<div class="sect2"> +<h3 id="_em_subsurface_em_parece_calcular_mal_el_consumo_de_gas_y_el_cas">21.1. <em>Subsurface</em> parece calcular mal el consumo de gas y el CAS</h3> +<div class="paragraph" id="SAC_CALCULATION"><p><em>Pregunta</em>: Buceé con una botella de 12,2 l empezando con 220 bar y terminando +con 100 bar y yo calculo un CAS distinto al que calcula <em>Subsurface</em> ¿Está +calculándolo mal <em>Subsurface</em>?</p></div> +<div class="paragraph"><p><em>Respuesta</em>: En realidad no. Lo que sucede es que <em>Subsurface</em> calcula el +consumo de gas de forma diferente (y mejor) de lo que esperas. En particular, +tiene en cuenta la incompresibilidad de los gases. +Tradicionalmente para calcular el consumo y el CAS se usaba</p></div> +<div class="paragraph"><p><code>consumo = tamaño_de_botella x (presión_inicial - presión_final)</code></p></div> +<div class="paragraph"><p>y es cierto para un gas ideal y es lo que se enseña en la teoría del buceo. Pero +actualmente no existe un "gas ideal" y los gases reales no se comprimen +linealmente con la presión. Además, estás olvidando el hecho de que una +atmósfera de presión no es un bar. Así pues, el cálculo <strong>real</strong> es</p></div> +<div class="paragraph"><p><code>consumo = (cantidad_de_aire_al_inicio - cantidad_de_aire_al_final)</code></p></div> +<div class="paragraph"><p>donde la cantidad de aire <strong>no</strong> es simplemente "tamaño_de_botella x +presión_en_bares". Es una combinación de "tener en cuenta la compresibilidad de +los gases" (que es bastante poco a 220 bar pero se nota mucho más a 300 bar) y +"convertir los bares en atmósferas" (que es la mayor parte de la discrepancia). +Recuerda: una atm es ~1.013 bar, por tanto sin compresibilidad, tu uso de gas es +:</p></div> +<div class="paragraph"><p><code>12.2*((220-100)/1.013)</code></p></div> +<div class="paragraph"><p>que es aproximadamente 1445, no 1464. Así pues había 19 litros de más en tu +cálculo que ignoraba la diferencia entre bar y atm. La compresibilidad aparece +por encima de 200 bar y reduce los 1445 en unos 8 litros más por lo que +realmente usaste unos 1437 litros al nivel del mar.</p></div> +<div class="paragraph"><p>Por lo tanto, alégrate: tu CAS es mejor de lo que tus cálculos indicaban. O +entristécete: tu botella contiene menos aire de lo que pensabas. Y como +mencionábamos el "contiene menos aire de lo que pensabas" se hace más notorio a +altas presiones. A 400 bar realmente no contiene el doble de aire que a 200 bar. +A presiones más bajas, el aire se comporta bastante como un gas ideal.</p></div> +</div> +<div class="sect2"> +<h3 id="_algunos_perfiles_de_inmersion_tienen_discrepancias_de_tiempos_con_las_muestras_que_toma_mi_ordenador_de_buceo">21.2. Algunos perfiles de inmersión tienen discrepancias de tiempos con las muestras que toma mi ordenador de buceo …</h3> +<div class="paragraph"><p><em>Subsurface</em> termina por ignorar el tiempo en superficie por varios motivos +(profundidad media, tiempo de inmersión, CAS, etc).</p></div> +<div class="paragraph"><p><em>Pregunta</em>: ¿Por qué las duraciones de los buceos en mi ordenador difieren de +los proporcionados por <em>Subsurface</em>?</p></div> +<div class="paragraph"><p><em>Respuesta</em>: Por ejemplo, si al terminar haces una prueba de lastre +(suficientemente profunda para iniciar el ordenador de buceo) y luego subes y +esperas 5 minutos a tus compañeros, tu ordenador puede decir que has hecho una +inmersión de 50 minutos, pero <em>Subsurface</em> dirá que es de 45 minutos (porque +realmente has estado buceando 45 minutos). Es mucho más notable si haces cosas +como actuar de instructor en inmersiones de curso, donde puedes estar en el agua +mucho rato pero pasar la mayor parte del tiempo en superficie. En este caso no +querrás que te cuente como algún tipo de inmersión larga.</p></div> +</div> +<div class="sect2"> +<h3 id="_se_han_perdido_algunos_perfiles_en_la_descarga">21.3. Se han perdido algunos perfiles en la descarga</h3> +<div class="paragraph" id="DC_HISTORY"><p><em>Pregunta</em>: No consigo descargar todas mis inmersiones, solo las más recientes, +incluso aunque el manual de mi ordenador de buceo afirma que guarda el historial +de, por ejemplo, 999 buceos.</p></div> +<div class="paragraph"><p><em>Respuesta</em>: El historial de buceo es diferente de los perfiles de inmersión del +registro. El historial solo conserva rastro del total de inmersiones y el tiempo +total pasado bajo el agua. Los registros, por otra parte, conservan el perfil de +inmersión, pero disponen de una cantidad limitada de memoria para hacerlo. La +cantidad exacta de perfiles que pueden guardarse en un dispositivo dependen del +intervalo de las muestras y de la duración de los buceos. Una vez que la memoria +se ha llenado se sobre escriben las inmersiones más antiguas con nuevas. De +esta forma, solo podemos descargar las últimas 13, 30 o 199 inmersiones.</p></div> +<div class="paragraph"><p>Si has descargado tus inmersiones a otro divelog antes de que se sobrescribieran, +hay muchas posibilidades de que Subsurface pueda importarlas. Sin embargo, si los +registros estaban solo en el ordenador de buceo, no pueden recuperarse tras haber +sido sobrescritos.</p></div> +</div> +</div> +</div> +</div> +<div id="footnotes"><hr /></div> +<div id="footer"> +<div id="footer-text"> +Last updated 2015-12-15 13:35:29 PST +</div> +</div> +</body> +</html> diff --git a/Documentation/user-manual_fr.html.git b/Documentation/user-manual_fr.html.git index 205167523..128f62872 100644 --- a/Documentation/user-manual_fr.html.git +++ b/Documentation/user-manual_fr.html.git @@ -1,6888 +1,6817 @@ -<!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.9" />
-<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; }
-
-
-@media screen {
- body {
- max-width: 50em; /* approximately 80 characters wide */
- margin-left: 16em;
- }
-
- #toc {
- position: fixed;
- top: 0;
- left: 0;
- bottom: 0;
- width: 13em;
- padding: 0.5em;
- padding-bottom: 1.5em;
- margin: 0;
- overflow: auto;
- border-right: 3px solid #f8f8f8;
- background-color: white;
- }
-
- #toc .toclevel1 {
- margin-top: 0.5em;
- }
-
- #toc .toclevel2 {
- margin-top: 0.25em;
- display: list-item;
- color: #aaaaaa;
- }
-
- #toctitle {
- margin-top: 0.5em;
- }
-}
-</style>
-<script type="text/javascript">
-/*<+'])');
- // 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.5, Octobre 2015</em></span></p></div>
-<div class="paragraph"><p>Bienvenue en tant qu’utilisateur de <em>Subsurface</em>, 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. <em>Subsurface</em> offre de nombreux avantages par
-rapport à d’autres solutions logicielles similaires :</p></div>
-<div class="ulist"><ul>
-<li>
-<p>
-Avez-vous besoin d’une façon d’enregistrer vos plongées utilisant des
- équipements loisirs, même sans utiliser d’ordinateur de plongée ?
-</p>
-</li>
-<li>
-<p>
-Utilisez-vous deux marques différentes d’ordinateurs de plongée, chacun avec
- son propre logiciel propriétaire pour télécharger les enregistrements des
- plongées ? Plongez-vous avec un recycleur ou un équipement en circuit ouvert
- ou de loisir ? Utilisez-vous un enregistreur de profondeur et de durée
- Reefnet Sensus avec un ordinateur de plongée ? <em>Subsurface</em> offre une
- interface standard pour télécharger les enregistrements des plongées à
- partir de tous ces équipements de plongée et pour enregistrer et analyser
- ces enregistrements dans un système unique.
-</p>
-</li>
-<li>
-<p>
-Utilisez-vous plus d’un système d’exploitation ? <em>Subsurface</em> est
- intégralement compatible avec Mac, Linux et Windows, ce qui vous permet
- d’accéder à vos enregistrements de plongées sur chaque système
- d’exploitation en utilisant une application unique.
-</p>
-</li>
-<li>
-<p>
-Utilisez-vous Linux ou Mac et votre ordinateur de plongée n’a que des
- logiciels pour Windows pour télécharger les informations de plongées (par
- exemple Mares) ? <em>Subsurface</em> fournit un moyen de télécharger et d’analyser
- vos enregistrements de plongées sur d’autres systèmes d’exploitation.
-</p>
-</li>
-<li>
-<p>
-Avez-vous besoin d’un planificateur de plongée graphique intuitif qui
- intègre et prend en compte les plongées qui ont déjà été enregistrées ?
-</p>
-</li>
-<li>
-<p>
-Avez-vous besoin d’un moyen d’enregistrer ou de sauvegarder votre carnet de
- plongée sur Internet, Vous permettant de visualiser votre carnet depuis
- n’importe où, en utilisant un navigateur Internet ?
-</p>
-</li>
-</ul></div>
-<div class="paragraph"><p><em>Subsurface</em> est disponible pour Windows (Win XP ou plus récent), les Macs
-basés sur processeurs Intel (OS/X) et de nombreuses distributions
-Linux. <em>Subsurface</em> peut être compilé pour bien plus de plateformes
-matérielles et d’environnements logiciels où Qt et libdivecomputer sont
-disponibles.</p></div>
-<div class="paragraph"><p>Le but de ce document est l’utilisation du programme Subsurface. Pour
-installer le logiciel, consultez la page <em>Téléchargement</em> sur le
-<a href="http://subsurface-divelog.org/">site web de <em>Subsurface</em></a>. En cas de
-problème, vous pouvez envoyer un e-mail sur
-<a href="mailto:subsurface@subsurface-divelog.org">notre liste de diffusion</a> et
-rapportez les bogues sur <a href="http://trac.hohndel.org">notre bugtracker</a>. Pour
-des instructions de compilation du logiciel et (si besoin) de ses
-dépendances, merci de consulter le fichier INSTALL inclus dans les sources
-logicielles.</p></div>
-<div class="paragraph"><p><strong>Public</strong> : Plongeurs loisirs, apnéistes, plongeurs Tek et plongeurs
-professionnels</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="_utilisation_de_ce_manuel">1. Utilisation de ce manuel</h2>
-<div class="sectionbody">
-<div class="paragraph"><p>When opened from within <em>Subsurface</em>, this manual does not have external
-controls for paging or selecting previous pages. However, two facilities are
-provided:</p></div>
-<div class="paragraph"><p>The <em>SEARCH</em> function is activated by pressing control-F or command-F on the
-keyboard. A text box appears at the bottom right-hand of the window (see
-image below). For instance, if one typed the word "<em>weights</em>" into the
-search text box, this word will be searched for throughout this user
-manual. To the right of the search text box are two arrows pointing upwards
-and downwards. Selecting these allow finding, respectively, the previous and
-the next occurence of the term being searched for.</p></div>
-<div class="imageblock" style="text-align:center;">
-<div class="content">
-<img src="images/usermanualfunctions.jpg" alt="User manual functions" />
-</div>
-</div>
-<div class="paragraph"><p><em>PREVIOUS/NEXT LINK</em>. One can move between links (underlined words allowing
-one to jump to specific sections in this user manual) by right-clicking on
-the text of the manual. This brings up a context menu for jumping to
-previous links selected while reading the manual (see image above). For
-instance if a link in the manual has been selected, then the option to <em>Go
-Back</em> shows the text at the last link that was selected (similar to the
-Previous Page button in a browser). Conversely the <em>Go Forward</em> option
-enables jumping to the text perused before selecting the <em>Go Back</em>
-option. The <em>Reload</em> option causes the complete user manual to be reloaded
-into the user manual window.</p></div>
-</div>
-</div>
-<div class="sect1">
-<h2 id="S_UserSurvey">2. Le sondage utilisateur</h2>
-<div class="sectionbody">
-<div class="paragraph"><p>Dans le but de développer <em>Subsurface</em> d’une manière qui serve ses
-utilisateurs de la meilleur manière qu’il soit, il est important d’avoir des
-informations sur les utilisateurs. À l’ouverture de <em>Subsurface</em> après avoir
-utilisé le logiciel pendant une semaine environ, une fenêtre de sondage
-apparait. Cela est complètement optionnel et l’utilisateur contrôle quelles
-informations sont envoyées ou non à l'équipe de développement de
-<em>Subsurface</em>. Toutes les données que l’utilisateur choisit d’envoyer sont
-extrêmement utiles et ne seront utilisées que pour les futures
-développements et modifications du logiciel pour coller au mieux aux besoins
-des utilisateurs de <em>Subsurface</em>. Si vous complétez le sondage ou cliquez
-sur l’option pour ne plus être sondé, cela devrait être la dernière
-communication de ce type que vous recevrez. Cependant, si vos habitudes de
-plongées ou d’utilisation de Subsurface changent, vous pouvez envoyer un
-nouveau sondage en démarrant <em>Subsurface</em> avec l’option <em>--survey</em> sur la
-ligne de commande.</p></div>
-</div>
-</div>
-<div class="sect1">
-<h2 id="S_StartUsing">3. Commencer à utiliser le programme</h2>
-<div class="sectionbody">
-<div class="paragraph"><p>La fenêtre <em>Subsurface</em> est généralement divisée en 4 panneaux avec un <strong>Menu
-principal</strong> (Fichier Importer Journal Vue Aide) en haut de la fenêtre (pour
-Windows et Linux) ou en haut de l'écran (pour Mac et Ubuntu Unity). Les
-quatre panneaux sont :</p></div>
-<div class="paragraph"><p>La <strong>liste des plongées</strong> en bas à gauche, contenant une liste de toutes les
-plongées du journal (carnet) de plongées de l’utilisateur. Une plongée peut
-être sélectionnée et mise en surbrillance dans la liste en cliquant
-dessus. Dans la plupart des cas, les touches haut/bas peuvent être utilisée
-pour passer d’une plongée à l’autre. La <strong>liste des plongées</strong> est un outil
-important pour manipuler un journal (carnet) de plongée.</p></div>
-<div class="paragraph"><p>La <strong>carte de plongée</strong> en bas à droite, affiche les sites de plongées de
-l’utilisateur, sur une carte mondiale et centrée sur le site de la dernière
-plongée sélectionnée dans la <strong>liste des plongées</strong>.</p></div>
-<div class="paragraph"><p>Les <strong>informations</strong> en haut à gauche, fournissent des informations détaillées
-sur la plongée sélectionnée dans la <strong>liste des plongées</strong>, dont des
-statistiques pour la plongée sélectionnée ou pour toutes les plongées mises
-en surbrillance.</p></div>
-<div class="paragraph"><p>Le <strong>profil de plongée</strong> en haut à droite, affiche un profil de plongée
-graphique de la plongée sélectionnée dans la <strong>liste des plongées</strong>.</p></div>
-<div class="paragraph"><p>Les séparateurs entre ces panneaux peuvent être déplacés pour modifier la
-taille de chaque panneau. <em>Subsurface</em> mémorise la position de ces
-séparateurs, pour qu’au prochain lancement <em>Subsurface</em> utilise ces
-positions.</p></div>
-<div class="paragraph"><p>Si une unique plongée est sélectionnée dans la <strong>liste des plongées</strong>,
-l’emplacement de la plongée, les informations détaillées et le profil de la
-<em>plongée sélectionnée</em> sont affichées dans les panneaux respectifs. D’autre
-part, si plusieurs plongées sont sélectionnées, la dernière mise en
-surbrillance est la <em>plongée sélectionnée</em>, mais les données de <em>toutes les
-plongées mises en surbrillances</em> sont affichées dans l’onglet <strong>Stats</strong> du
-panneau <strong>informations</strong> (profondeur maximale, minimale et moyenne, les
-durées, les températures de l’eau et le SAC (air consommé); temps total et
-nombre de plongées sélectionnées).</p></div>
-<div class="imageblock" id="S_ViewPanels" style="text-align:center;">
-<div class="content">
-<img src="images/main_window_f22.jpg" alt="The Main Window" />
-</div>
-</div>
-<div class="paragraph"><p>L’utilisateur peut déterminer si lesquels des quatre panneaux sont affichés
-en sélectionnant l’option <strong>Vue</strong> dans le menu principal. Cette fonctionnalité
-permet plusieurs choix d’affichage :</p></div>
-<div class="paragraph"><p><strong>Tout</strong> : affiche les quatre panneaux tels que sur la capture d'écran ci-dessus.</p></div>
-<div class="paragraph"><p><strong>Liste des plongées</strong> : affiche uniquement la liste des plongées.</p></div>
-<div class="paragraph"><p><strong>Profil</strong> : affiche uniquement le profile de plongée de la plongée sélectionnée.</p></div>
-<div class="paragraph"><p><strong>Info</strong> : affiche uniquement les notes de plongées de la dernière plongée sélectionnée et les statistiques pour
-toutes les plongées mises en surbrillance.</p></div>
-<div class="paragraph"><p><strong>Globe</strong> : affiche uniquement la carte mondiale, centrée sur la dernière plongée sélectionnée.</p></div>
-<div class="paragraph"><p>Comme la plupart des autre fonctions qui peuvent être accédée via le menu
-principal, ces options peuvent être utilisées par des raccourcis
-clavier. Les raccourcis pour un système particulier sont affichés avec un
-souligné des les entrées de menu. À cause des différents systèmes
-d’exploitation et des divers langues, <em>Subsurface</em> peut utiliser différentes
-touches de raccourcis et ne sont donc pas détaillées ici.</p></div>
-<div class="paragraph"><p>Lorsque le programme est lancé pour la première fois, il n’affiche aucune
-information. Ceci parce que le programme n’a aucune information de plongée
-disponible. Dans les sections suivantes, le procédure pour créer a nouveau
-carnet de plongée sera détaillée.</p></div>
-</div>
-</div>
-<div class="sect1">
-<h2 id="S_NewLogbook">4. Créer un nouveau carnet de plongée</h2>
-<div class="sectionbody">
-<div class="paragraph"><p>Sélectionner <em>Fichier → Nouveau carnet de plongée</em> à partir du menu
-principal. Toutes les données de plongées sont effacées pour que de
-nouvelles puissent être ajoutées. S’il existe des données non encore
-enregistrées dans le carnet ouvert, l’utilisateur devra sélectionner s’il
-faut les enregistrer ou non avant de créer le nouveau carnet.</p></div>
-</div>
-</div>
-<div class="sect1">
-<h2 id="S_GetInformation">5. Enregistrement des informations de plongée dans le carnet</h2>
-<div class="sectionbody">
-<div class="paragraph"><p>Maintenant qu’un nouveau carnet de plongée a été créé, il est simple de lui
-ajouter des données. <em>Subsurface</em> permet plusieurs façons pour ajouter des
-données de plongée au carnet. Plus de détails dans les sections suivantes.</p></div>
-<div class="paragraph"><p>1) Si l’utilisateur possède un carnet manuscrit, un tableur ou une autre forme
- de
- carnet maintenu manuellement, les données de plongée peuvent être ajoutées
- au carnet en utilisant une des approches suivantes :</p></div>
-<div class="ulist"><ul>
-<li>
-<p>
-Entrer les informations de plongée à la main. Cela est utile si le plongeur
- n’a pas
- utilisé d’ordinateur de plongée et que les plongées sont inscrites dans un
- carnet manuscrit. Voir <a href="#S_EnterData">Entrer les informations de plongée
- à la main</a>
-</p>
-</li>
-<li>
-<p>
-Importer les informations de plongée qui ont été maintenues soit dans un
- tableur
- soit dans un fichier CSV. Se reporter à : <a href="#S_Appendix_D">ANNEXE D :
- Exporter un tableur vers le format CSV</a> et à
- <a href="#S_ImportingCSVDives">Importer des plongées au format CSV</a>.
-</p>
-</li>
-</ul></div>
-<div class="paragraph"><p>2) Si les plongées ont été enregistrées en utilisant un ordinateur de plongée,
- le profil de profondeur de la
- plongée et de nombreuses informations supplémentaires peuvent être
- utilisées. Ces plongées peuvent être importées à partir de :</p></div>
-<div class="ulist"><ul>
-<li>
-<p>
-L’ordinateur de plongée lui-même. Voir : <a href="#S_ImportDiveComputer">Importer
- de nouvelles informations de plongée à partir de l’ordinateur de plongée</a> ou
-</p>
-</li>
-<li>
-<p>
-Logiciels propriétaires fournis par les fabricants d’ordinateurs de
- plongée. Voir
- <a href="#S_ImportingAlienDiveLogs">Importer les informations à partir d’autres
- sources de données numériques ou d’autres formats de données</a>.
-</p>
-</li>
-<li>
-<p>
-Importer à partir d’un tableur ou de fichiers CSV contenant les profils de
- plongées.
- Voir : <a href="#S_ImportingCSVDives">Importer les plongées au format CSV à partir
- des ordinateurs de plongées ou d’autres logiciels de carnet de plongée</a>
-</p>
-</li>
-</ul></div>
-<div class="sect2">
-<h3 id="S_EnterData">5.1. Entrer les informations de plongée à la main</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 → Add Dive</em> from the Main Menu. The program then shows three
-panels to enter information for a dive: two tabs in the <strong>Info</strong> panel
-(<strong>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_f22.jpg" alt="FIGURE: Add dive" />
-</div>
-</div>
-<div class="paragraph"><p>When one edits a field in 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
-<strong>Notes</strong> panel (see the image below). This message is displayed in all the
-panels under 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_f22.jpg" alt="Blue edit bar" />
-</div>
-</div>
-<div class="paragraph"><p>The <em>Apply changes</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>Apply changes</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="S_CreateProfile">5.1.1. 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 right-angled red lines as shown
-below. The time and depth represented by the cursor 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. Drag
-the waypoints to represent an accurate time duration for the dive. Below is
-a dive profile for 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 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 (see image below).</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>With the profile having been defined, more details must be added in order to
-have a fuller record of the dive. To do this, the <strong>Notes</strong> and the
-<strong>Equipment</strong> tabs on the top left hand of the <em>Subsurface</em> window should be
-used. Click on <a href="#S_Notes_dc"><strong>this link</strong></a> for instructions to use these
-tabs.</p></div>
-</div>
-</div>
-<div class="sect2">
-<h3 id="S_ImportDiveComputer">5.2. Importer de nouvelles informations de plongée à partir de l’ordinateur de plongée</h3>
-<div class="sect3">
-<h4 id="_connecting_and_importing_data_from_a_dive_computer">5.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’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’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’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.
- (Se reporter au manuel de l’ordinateur de plongée)
-</p>
-</li>
-<li>
-<p>
-In <em>Subsurface</em>, from the Main Menu, select <em>Import → Import From Dive
- Computer</em>. Dialogue <strong>A</strong> in the figure below appears:
-</p>
-</li>
-</ol></div>
-<div class="imageblock" style="text-align:center;">
-<div class="content">
-<img src="images/DC_import_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, if the dive computer allows this, <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).</p></div>
-<div class="ulist"><ul>
-<li>
-<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>
-</li>
-<li>
-<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>
-</li>
-<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 dive in the <em>Subsurface</em>
- divelog will be overwritten by the dive record from the dive computer.
-</p>
-</li>
-<li>
-<p>
-The checkbox marked <em>Download into new trip</em> ensures that, after upload, the
- downloaded dives are grouped together as a new trip(s) in the <strong>Dive List</strong>.
-</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>
-<li>
-<p>
-Then select the <em>Download</em> button. 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. 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). After successful download, Dialogue
- <strong>B</strong> in the figure above appears. After the dives have been downloaded, they
- appear in a tabular format on the right-hand side of the dialogue (see image
- <strong>B</strong>, above). Each dive comprises a row in the table, with the date, duration
- and depth shown. Next to each dive is a checkbox: check all the dives that
- need to be transferred to the <strong>Dive List</strong>. In the case of the image above,
- the last six dives are checked and will be transferred to the <strong>Dive
- List</strong>. Then click the <em>OK</em> button at the bottom of the dialogue. 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.
-</p>
-</li>
-</ul></div>
-<div class="paragraph"><p>After this has been completed, select the OK button. The checked dives are
-transferred to the <strong>Dive List</strong>.</p></div>
-<div class="ulist"><ul>
-<li>
-<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>
-</li>
-</ul></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="ulist"><ul>
-<li>
-<p>
-Is the dive computer still in PC-communication or Upload mode?
-</p>
-</li>
-<li>
-<p>
-Is the battery of the dive computer fully charged? If not then the battery
- must be charged or replaced.
-</p>
-</li>
-<li>
-<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>
-</li>
-<li>
-<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>
-</li>
-<li>
-<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>
-</li>
-</ul></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_Bluetooth">5.2.2. Connecting <em>Subsurface</em> to a Bluetooth-enabled dive computer</h4>
-<div class="paragraph"><p>Bluetooth is becoming a more common way of communication between dive
-computers and <em>Subsurface</em>, for instance, the Shearwater Petrel Mk2 and the
-OSTC Mk3. <em>Subsurface</em> provides a largely operating system independent
-Bluetooth interface. Setting up <em>Subsurface</em> for Bluetooth communication
-requires four steps:</p></div>
-<div class="ulist"><ul>
-<li>
-<p>
-Ensure that Bluetooth is activated on the host computer running
- <em>Subsurface</em>.
-</p>
-</li>
-<li>
-<p>
-Ensure that <em>Subsurface</em> sees the Bluetooth adapter on the host computer.
-</p>
-</li>
-<li>
-<p>
-Ensure the Bluetooth-enabled dive computer is Bluetooth-discoverable and in
- PC upload mode.
-</p>
-</li>
-<li>
-<p>
-Ensure that <em>Subsurface</em> is paired with the Bluetooth-enabled dive computer.
-</p>
-</li>
-</ul></div>
-<div class="paragraph"><p>Select the Download dialogue by selecting <em>Import → Import from dive
-computer</em> from the <strong>Main Menu</strong>. If one checks the check box labelled
-<em>"Choose Bluetooth download mode"</em>, the dialogue below appears.</p></div>
-<div class="sect4">
-<h5 id="_sur_linux_ou_macos">Sur Linux ou MacOS :</h5>
-<div class="imageblock" style="text-align:center;">
-<div class="content">
-<img src="images/DC_import_Bluetooth.jpg" alt="FIGURE: Download Bluetooth" />
-</div>
-</div>
-<div class="paragraph"><p>On the <em>Linux</em> or <em>MacOS</em> platforms the name of the <em>Subsurface</em> computer
-and its Bluetooth address are shown on the right-hand side, On the lefthand
-side, if the computer has connected more than one local Bluetooth devices
-the user can use the list box to indicate which one needs to connect to
-<em>Subsurface</em>. The power state (on/off) of the Bluetooth adapter is shown
-below the address and can be changed by checking the <em>Turn on/off</em> check
-box.</p></div>
-<div class="paragraph"><p>If the Bluetooth address is not shown, then <em>Subsurface</em> does not see the
-local Bluetooth device. Ensure that the Bluetooth driver is installed
-correctly on the <em>Subsurface</em> computer and check if it can be used by other
-Bluetooth utilities like <em>bluetoothctl</em> or <em>bluemoon</em>. This achieves the
-first two steps above.</p></div>
-<div class="paragraph"><p>Ensure that the Bluetooth-enabled dive computer is in PC-upload mode and
-that it is discoverable by other Bluetooth devices. Consult the manual of
-the dive computer to perform this. Now the third item in the list above has
-been achieved.</p></div>
-<div class="paragraph"><p>Select the <em>Scan</em> button towards the bottom left of the dialogue
-above. After searching for a small amount of time, the dive computer should
-be listed (perhaps as one of a number of Bluetooth devices) in the main list
-box on the lefthand side of the dialogue (see image above). If this is not
-achieved, select the <em>Clear</em> button and then scan again for Bluetooth
-devices using the <em>Scan</em> button. After performing these actions <em>Subsurface</em>
-should see the dive computer. The label of the discovered dive computer
-contains the name of the device, its address and its pairing status. If the
-device is not paired and has a red background colour, a context menu can be
-opened by selecting the item with a right-click. Select the the <em>Pair</em>
-option and wait for the task to complete. If this dive computer is being
-paired to Subsurface for the first time, it is possible that Subsurface will
-request a Pass Code or PIN number. The most commonly-used Pass Code is 0000,
-and this works for the Shearwater Petrel. If necessary, consult the user
-manual of the dive computer being used.</p></div>
-<div class="sidebarblock">
-<div class="content">
-<div class="admonitionblock">
-<table><tr>
-<td class="icon">
-<img src="images/icons/important.png" alt="Important" />
-</td>
-<td class="content">Currently <em>Subsurface</em> does not support Bluetooth pairing with dive
-computers that require a custom PIN code. In order to pair the devices, use
-other OS utilities as suggested below.</td>
-</tr></table>
-</div>
-<div class="paragraph"><p>One way to achieve this is to use <code>bluetoothctl</code>:</p></div>
-<div class="literalblock">
-<div class="content">
-<pre><code>$ bluetoothctl
-[bluetooth]# agent KeyboardOnly
-Agent registered
-[bluetooth]# default-agent
-Default agent request successful
-[bluetooth]# pair 00:80:25:49:6C:E3
-Attempting to pair with 00:80:25:49:6C:E3
-[CHG] Device 00:80:25:49:6C:E3 Connected: yes
-Request PIN code
-[agent] Enter PIN code: 0000</code></pre>
-</div></div>
-</div></div>
-<div class="paragraph"><p>After the devices are paired the <em>Save</em> button of the dialogue can be
-pressed. This closes the Bluetooth dialogue. Now select <em>Download</em> in the
-<em>Download from dive computer</em> dialogue which should still be open. The
-downloaded dives are shown on the righthand side of the download dialogue.</p></div>
-</div>
-<div class="sect4">
-<h5 id="_sur_windows">Sur Windows :</h5>
-<div class="imageblock" style="text-align:center;">
-<div class="content">
-<img src="images/DC_import_Bluetooth_Windows.png" alt="FIGURE: Download Bluetooth on Windows" />
-</div>
-</div>
-<div class="paragraph"><p>On <em>Windows</em> platforms the <em>Local Bluetooth device details section</em> on the
-right is not displayed as is the case on the Linux/Mac implementations. To
-successfully initiate a scan (by pressing the <em>Scan</em> button) check that the
-Bluetooth device on the <em>Subsurface</em> computer is turned on by selecting the
-dive computer from the list of available Bluetooth devices (see image
-above). If the dive computer is accessed by Subsurface for the first time,
-it is possible that Subsurface will request a Pass Code/PIN number. Supply
-the Pass Code recommended in the user manual of the dive computer. A Pass
-Code of 0000 is often appropriate.</p></div>
-<div class="paragraph"><p>The pairing step is checked and done automatically during the download
-process. If the devices have never been paired the system will ask for your
-permissions and put a message on the right side of the screen: <em>Add a
-device, Tap to set up your DC device</em>. Always allow this pairing. After a
-discovered item is selected, select the <em>Save</em> button. Finally select the
-<em>Download</em> button on the <em>Download</em> dialogue and wait for the process to
-complete.</p></div>
-<div class="admonitionblock">
-<table><tr>
-<td class="icon">
-<img src="images/icons/important.png" alt="Important" />
-</td>
-<td class="content">Currently <em>Subsurface</em> works only with local Bluetooth adapters which use
-Microsoft Bluetooth Stack. If the local device uses <em>Widcomm</em>, <em>Stonestreet
-One Bluetopia Bluetooth</em> or <em>BlueSoleil</em> drivers it will definitely not
-work. However, Bluetooth hardware/dongles from these manufacturers
-(e.g. iSonic) that support the Microsoft Bluetooth Stack do work.</td>
-</tr></table>
-</div>
-<div class="paragraph"><p>A log messageOn the bottom left of the <em>Remote Bluetooth device selection</em>
-shows details about the current status of the Bluetooth agent. To select
-another dive computer for download using the "Remote Bluetooth selection
-dialogue" press the three-dots button from the <em>"Choose Bluetooth download
-mode"</em> option.</p></div>
-<div class="admonitionblock">
-<table><tr>
-<td class="icon">
-<img src="images/icons/important.png" alt="Important" />
-</td>
-<td class="content"><strong>IN CASE OF PROBLEMS</strong>: If the Bluetooth adapter from the <em>Subsurface</em> computer
-gets stuck and the <em>Download</em> process fails repeatedly,
- <em>unpair</em> the devices and then repeat the above steps. If this is not successful,
- <a href="#S_HowFindBluetoothDeviceName"><em>Appendix A</em></a> contains
-information for manually setting up and inspecting the Bluetooth connection
-with <em>Subsurface</em>.</td>
-</tr></table>
-</div>
-</div>
-</div>
-<div class="sect3">
-<h4 id="S_DeviceNames">5.2.3. 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’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 <em>Subsurface</em> computer, then one would
-perhaps like to call one dc "Alice’s Suunto D4" and the other one "Bob’s
-Suunto D4". Alternatively, consider 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 → 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">5.2.4. Updating the dive information imported from the dive computer.</h4>
-<div class="paragraph"><p>With the uploaded dives in the <strong>Dive List</strong>, 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>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 class="sect4">
-<h5 id="S_Notes_dc">Notes</h5>
-<div class="paragraph"><p>To have a more complete dive record the user needs to add additional
-information by hand. The procedure below is virtually identical for
-hand-entered dives and for dives downloaded from a dive computer.</p></div>
-<div class="paragraph"><p>In some cases, one has to provide the date and time of the dive, e.g. when
-entering a dive by hand or when a dive computer does not provide the date
-and time of the dive. (Usually the date and time of the dive, gas mixture
-and water temperature are shown as obtained from the dive computer) If the
-contents of the <strong>Notes tab</strong> 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>Notes</strong> tab, the following fields are visible
-(left hand image, below):</p></div>
-<div class="imageblock" style="text-align:center;">
-<div class="content">
-<img src="images/AddDive3_f22.jpg" alt="FIGURE: The Notes tab" />
-</div>
-</div>
-<div class="paragraph"><p>The right hand image, above, shows a <strong>Notes tab</strong> filled with dive
-information. 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 over-typing the information displayed.</p></div>
-<div class="paragraph"><p><strong>Air/water temperatures</strong>: Air and water temperatures during the dive are shown
-in text boxes to the right of the Start time. Many dive computers supply water
-temperature information and this box may therefore contain information.
-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> (following the <em>Preferences</em>, metric or imperial units will
-be used).</p></div>
-<div class="paragraph"><p><strong>Location</strong>:</p></div>
-<div class="admonitionblock">
-<table><tr>
-<td class="icon">
-<img src="images/icons/warning2.png" alt="Warning" />
-</td>
-<td class="content">Dive locations are managed as a <strong>separate</strong> part of the dive log. The dive
-information in the <strong>Notes</strong> and <strong>Equipment</strong> tabs can therefore not be edited
-at the same time as the dive site information. Save all the other dive
-information (e.g. divemaster, buddy, protective gear, notes about the dive)
-by selecting <em>Apply changes</em> on the <strong>Notes</strong> tab before editing the dive site
-information. Only then, supply a dive site name in the textbox labelled
-<em>Location</em> on the <strong>Notes</strong> tab.</td>
-</tr></table>
-</div>
-<div class="paragraph"><p>Type the name of the dive site, e.g. "Tihany, Lake Balaton, Hungary". If
-several dives are performed at the same location, the dive site information
-for the first dive is re-used. Existing dive location information can be
-edited at any time by selecting (on the <strong>Dive List</strong> panel) a dive performed
-at that site and by opening the location information by clicking the globe
-button on the right of the location name (see image on the right,
-above). When entering a dive location name, auto location of dive site names
-makes it easy to select an existing dive site name (i.e. when typing the
-name of a dive site, a dropdown list appears showing all sites with similar
-names). If the dive site has been used before, click on the already-existing
-name. The dive site names in the dropdown list contain either a globe
-symbol (indicating existing dive sites in the <em>Subsurface</em> database) or a
-<strong>+</strong> symbol (indicating dive site names that appear consistent with the
-current dive site name but which have not been added to the dive site
-database). Therefore, if the present dive site has not been used before, a
-message appears as follows (image <strong>A</strong> below):</p></div>
-<div class="imageblock" style="text-align:center;">
-<div class="content">
-<img src="images/Locations1_f22.jpg" alt="FIGURE:Location description panel" />
-</div>
-</div>
-<div class="paragraph"><p>Doubleclick on the new dive site name. A panel appears to enter the
-coordinates and other important information about the site (image <strong>B</strong>,
-above). The most important items are the coordinates of the site. There are
-three ways of specifying the coordinates:</p></div>
-<div class="olist loweralpha"><ol class="loweralpha">
-<li>
-<p>
-One can find the coordinates on the world map in the bottom right hand part
- of the <em>Subsurface</em> window. The map displays an orange bar indicating "No
- location data - Move the map and double-click to set the dive
- location". Upon a doubleclick at the appropriate place, the orange bar
- disappears and the coordinates are stored.
-</p>
-</li>
-<li>
-<p>
-The coordinates can be obtained from the <em>Subsurface</em> Companion app if the
- user has an Android or iPhone 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>
-</li>
-<li>
-<p>
-The coordinates can be entered by hand if they are known, using one of four
- formats with latitude followed by longitude:
-</p>
-<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>
-</li>
-</ol></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. Some keyboards
-don’t have the degree sign (°). It can be replaced by a <strong>d</strong> like this: N30d
-W20d. If both a dive site name and coordinates have been provided, Save the
-dive site information by selecting the button <em>Apply changes</em> at the top of
-the panel.</p></div>
-<div class="paragraph"><p><strong>Important</strong>: GPS coordinates of a dive site are linked to the Location
-name - so <strong>saving</strong> a dive site with only coordinates and no dive site name
-causes 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>Dive site name lookup:</strong> If coordinates have been typed into the appropriate
-text box, one can perform an automated name lookup based on the coordinates.
-This is achieved when <em>Subsurface</em> uses the Internet to find the name of the dive site
-based on the coordinates that were typed. If a name has been found, it is
-automatically inserted into the tags box. The list box
-(Titled <em>Dive sites on same coordinates</em>") at the bottom
-of the dive site panel contains the names of other dives sites used at the
-current location. For instance if the dive site is "Blue Hole" and there are several
-dive sites named "Blue Hole", all these sites are listed in this list box.</p></div>
-<div class="paragraph"><p>Enter any other textual information about the dive site (Description and
-Notes), then select <em>Apply Changes</em> to save the geolocation for this dive
-site. At a later stage the dive site information can be edited by clicking
-the globe icon to the right of the dive site name in the <strong>Notes tab</strong>.</p></div>
-<div class="paragraph"><p><strong>Dive mode</strong>: This is a dropdown box allowing one to choose the type of dive
-performed. The options are OC (Open Circuit SCUBA, the default seting, meant for most recreational dives),
-Freedive (dive without SCUBA equipment), CCR (Closed-circuit
-rebreather) and pSCR (Passive semi-closed rebreather).</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 selection 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 selection 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 dive suit used can be entered.
-Auto selection of the suit description is available.
-Some dry-suit users may choose to use this field to record what combination of
-suit and thermal 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 <em>Apply changes</em> and <em>Discard changes</em> buttons are used to save all the
-information for tabs in the <strong>Info</strong> panel and in the <strong>Dive Profile</strong> panel, so
-there’s no need to use them until <strong>ALL</strong> other information has been
-added. The image <a href="#S_Notes_dc">at the beginning of this section</a> shows an
-example of a <strong>Notes tab</strong> after completion of the dive information.</p></div>
-</div>
-<div class="sect4">
-<h5 id="_equipment">Equipment</h5>
-<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_f22.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 <strong>Dive profile</strong> (top right-hand panel).</p></div>
-<div class="paragraph" id="cylinder_definitions"><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>For hand-entered dives, this information needs to be typed in. For dive
-computers, <em>Subsurface</em> often obtains the gas used from the dive computer
-and automatically inserts the gas composition(% oxygen or % helium) 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.</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 <em>Type</em> 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 (<em>Work.press</em>) will automatically be shown in
-the dialogue.</p></div>
-<div class="paragraph"><p>Next, 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, save the data either by pressing <em>ENTER</em> on the keyboard or by
-clicking outside the cell containing 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 <em>Type</em> 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>This can be used to select the type of weight system used during the dive or
-the user may start typing in the box to specify a different weighting
-mechanism that will be saved by <em>Subsurface</em>. In the <strong>Weight</strong> field, type
-in the amount of weight used during the dive. After specifying the weight
-system, save the data by either pressing <em>ENTER</em> on the keyboard or by
-clicking 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>
-<div class="sect3">
-<h4 id="_editing_several_selected_dives_simultaneously">5.2.5. 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
-each uploaded dive is shown in the <strong>Dive profile</strong> tab, as well as a few
-items of information in the <strong>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>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>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>Notes</strong> and
-<strong>Equipment</strong> tabs. Then, from the main menu, select <em>Log → Copy dive
-components</em>. A box is presented with a selection of check boxes for most of
-the fields in the <strong>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 → 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">5.2.6. 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="ulist"><ul>
-<li>
-<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>
-</li>
-<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>
-<li>
-<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>
-</li>
-<li>
-<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>
-</li>
-</ul></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">5.2.7. Saving the updated dive information</h4>
-<div class="paragraph"><p>The information entered in the <strong>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>Notes</strong> tab. If
-the <em>Apply changes</em> button is clicked, the dive data are saved in the memory
-image of the dive. If the <em>Discard changes</em> button is clicked, then the
-newly entered dive data are erased from the computer memory, although the
-dive profile is retained. When the user exits <em>Subsurface</em> there is a final
-prompt to confirm that the new data should now be saved permanently on the
-computer disk.</p></div>
-</div>
-</div>
-<div class="sect2">
-<h3 id="_importer_les_informations_à_partir_d_8217_autres_sources_de_données_numériques_ou_d_8217_autres_formats_de_données">5.3. Importer les informations à partir d’autres sources de données numériques ou d’autres formats de données</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. a 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 & 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 → Import log files</em> or <em>File
-→ 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. Below follows more specific information to achieve data import to
-<em>Subsurface</em>.</p></div>
-<div class="sect3">
-<h4 id="_using_the_universal_import_dialogue">5.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 activated by selecting <em>Import</em> from the Main Menu, then clicking
-on <em>Import Log Files</em>. This brings up 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>
-Cochran dive logs
-</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>
-APD Inspiration/Evolution CCR logs
-</p>
-</li>
-<li>
-<p>
-LiquiVision logs
-</p>
-</li>
-<li>
-<p>
-divelog.de logs
-</p>
-</li>
-<li>
-<p>
-OSTC Tools 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 format and then the specific log file in the large
-window containing the file list on the right 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_from_ostctools">5.3.2. Importing from OSTCTools</h4>
-<div class="paragraph"><p><em>OSTC Tools</em> is a Microsoft-based suite of dive download and dive management
-tools for the OSTC family of dive computers. <em>OSTC Tools</em> downloads dive
-data from the dive computer and stores it as a binary file with file
-extension <em>.dive</em> . Subsurface can directly import these files when using
-the universal import dialogue. From the dropdown list at the bottom right
-select <em>OSTCTools Files (.dive .DIVE)</em>. This makes the <em>OSTC Tools</em> dive
-logs visible in the file list panel. Select one or more dive, then click the
-<em>Open</em> button. The OSTC dives are shown in the <strong>Dive List</strong> panel.</p></div>
-<div class="paragraph"><p>Actually, all H&W devices supported by OSTCTools can be imported to
-<em>Subsurface</em>, this includes OSTC, OSTC Mk2, OSTC 2N/2C, OSTC3, OSTC Sport,
-and probably although untested, Frog, OSTC2 and OSTC CR.</p></div>
-<div class="paragraph"><p>Please, remember that OSTCTools is <strong>not</strong> a true diving log software, but a
-useful set of tools for analysis and management of OSTC devices. This way,
-only raw dive computer data will be performed with the import to
-<em>Subsurface</em>; one has to to manually complete the rest of data which may be
-important (buddies, equipment, notes, etc).</p></div>
-</div>
-<div class="sect3">
-<h4 id="_importing_from_mares_dive_organiser_v2_1">5.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="olist arabic"><ol class="arabic">
-<li>
-<p>
-Export the dive log data from Mares Dive Organiser to the user’s desktop,
- using a <em>.sdf</em> file name extension. Refer to <a href="#Mares_Export">Appendix C</a>
- for more information.
-</p>
-</li>
-<li>
-<p>
-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 → 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>.
-</p>
-</li>
-<li>
-<p>
-Finally, import the dives from <em>divelogs.de</em> to <em>Subsurface</em>, using the
- instructions below.
-</p>
-</li>
-</ol></div>
-</div>
-<div class="sect3">
-<h4 id="S_ImportingDivelogsDe">5.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 → Import from Divelogs.de</em> option should be
-selected from the Main Menu. This brings up a dialogue box (see image <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 image <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">5.3.5. Importer des données au format CSV</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). The <em>CSV</em> format is a universal simplified format that
-allows for easy information exchange between different computers or software
-packages. For an introduction to CSV-formatted files see <a href="#S_CSV_Intro">A
-Diver’s Introduction To CSV Files</a>. <em>Subsurface</em> dive logs can also be
-exported in <em>CSV</em> format to other software that reads this format. See
-<a href="#S_Appendix_D">APPENDIX D: Exporting a spreadsheet to CSV format</a> for
-information that may be helpful for importing spreadsheet-based data into
-<em>Subsurface</em>.</p></div>
-<div class="sect4">
-<h5 id="S_ImportingCSVDives">Importer les plongées au format CSV à partir des ordinateurs de plongées ou d’autres logiciels de carnet de plongée</h5>
-<div class="paragraph"><p>One can view a <em>CSV</em> file by using an ordinary text editor. It is normally
-organised into a single line that provides the headers (or <em>field names</em> or
-<em>column headings</em>) of the data columns, followed by the data, one record per
-line.</p></div>
-<div class="paragraph"><p>There are two types of <em>CSV</em> dive logs that can be imported into
-<em>Subsurface</em>:</p></div>
-<div class="olist arabic"><ol class="arabic">
-<li>
-<p>
-<em>CSV dive details</em>: This dive log format contains similar information to
- that of a typical written dive log, e.g. dive date and time, dive depth,
- dive duration, names of buddy and dive master and perhaps some information
- about cylinder pressures before and after the dive, as well as a comment or
- two about the dive. All the data for a single dive go on a single line of
- text, following the order of the column headings.
-</p>
-</li>
-<li>
-<p>
-<em>CSV dive profile</em>: This dive log format includes much more information
- about a single dive. For instance there may be information at 30-second
- intervals, indicating depth, water temperature at that depth, and cylinder
- pressure at that moment in time. Each line contains the information for a
- single instant in time during the dive, 30 seconds after that of the
- previous instant. Many lines are required to complete the depth profile
- information for a single dive. This is a common export format used by
- closed-circuit rebreather (CCR) dive equipment and many software packages
- that handle dive computer data and/or dive logs.
-</p>
-</li>
-</ol></div>
-<div class="paragraph"><p>Before being able to import the <em>CSV</em> data to <em>Subsurface</em> <strong>one needs to
-know a few things about the data being imported</strong>:</p></div>
-<div class="olist loweralpha"><ol class="loweralpha">
-<li>
-<p>
-Which character separates the different columns within a single line of
- data? This field separator should be either a comma (,) a semicolon (;) or a
- TAB character. This can be determined by opening the file with a text
- editor. If it is comma-delimited or semicolon-delimited, the comma or
- semicolon characters between the values are clearly visible. If these are
- not evident and the numbers are aligned in columns, the file is probably
- TAB-delimited (i.e. it uses a TAB as a field separator).
-</p>
-</li>
-<li>
-<p>
-Which data columns need to be imported into <em>Subsurface</em>? Is it a <em>CSV dive
- details</em> file or a <em>CSV dive profile</em> file? Open the file using a text
- editor and note the titles of the columns to be imported and their column
- positions.
-</p>
-</li>
-<li>
-<p>
-Is the numeric information (e.g. dive depth) in metric or in imperial units?
-</p>
-</li>
-</ol></div>
-<div class="paragraph"><p>Armed with this information, importing the data into <em>Subsurface</em> is
-straightforward. Select <em>Import → Import Log Files</em> from the main menu. In
-the resulting file selection menu, select <em>CSV files</em> (towards the bottom
-right). This shows all .CSV files in the selected directory. Select the file
-that needs to be imported. A configuration panel appears as depicted below:</p></div>
-<div class="imageblock" style="text-align:center;">
-<div class="content">
-<img src="images/csv_import1_f20.jpg" alt="FIGURE: CSV download dialogue 1" />
-</div>
-</div>
-<div class="paragraph"><p>Notice that, at the top left, there is a dropdown list containing
-pre-configured settings for some of the more common dive computers and
-software packages encountered by divers. If the <em>CSV</em> file being imported
-originated from any of these pre-configured items, then select it. Otherwise
-use the <em>Manual Import</em> option. The configuration panel also has dropdown
-lists for the specification of the appropriate field separator (Tab, comma
-or semicolon), the date format used in the <em>CSV</em> file, the time units
-(seconds, minutes or minutes:seconds), as well as the unit system (metric or
-imperial). Selecting the appropriate options among these is critical for the
-successful import of the data.</p></div>
-<div class="paragraph"><p>The last remaining task is to ensure that all the data columns have the
-appropriate column headings. The top blue row of the data table contains the
-column headings found in the <em>CSV</em> data file. The blue row of balloons
-immediately above these contains the names understood by <em>Subsurface</em>. These
-balloons can be moved using a drag-and-drop action. For instance,
-<em>Subsurface</em> expects the column heading for Dive number (" # ") to be "Dive
-# ". If the column heading that <em>Subsurface</em> expects is not in the blue row,
-then drag the appropriate balloon from the upper area and drop it in the
-appropriate blue cell at the top of the table. To indicate the correct
-column for "Dive #", drag the ballooned item labelled "Dive # " and drop it
-in the blue cell immediately above the white cell containing " # ". This is
-depicted in the image below.</p></div>
-<div class="imageblock" style="text-align:center;">
-<div class="content">
-<img src="images/csv_import2_f20.jpg" alt="FIGURE: CSV download dialogue 2" />
-</div>
-</div>
-<div class="paragraph"><p>Continue in this way to ensure that all the column headings in the blue row
-of cells correspond to the headings listed in the top part of the
-dialogue. Having completed this task, select the <em>OK</em> button to the bottom
-right of the dialogue. The data from the <em>CSV</em> file are imported and shown
-in the <strong>Dive List</strong> panel.</p></div>
-<div class="sidebarblock" id="S_CSV_Intro">
-<div class="content">
-<div class="paragraph"><p><strong>A Diver’s Introduction to <em>CSV</em> Files</strong></p></div>
-<div class="admonitionblock">
-<table><tr>
-<td class="icon">
-<img src="images/icons/important.png" alt="Important" />
-</td>
-<td class="content"><em>CSV</em> is an abbreviation for a data file format: <em>Comma-Separated
-Values</em>. It is a file format allowing someone to view or edit the
-information using a text editor such as Notepad (Windows), gedit (Linux) or
-TextWrangler (OS/X). The two main advantages of the <em>CSV</em> 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 any custom
-or proprietary attributes that proprietary software insert into files.
-Because of its simplicity the <em>CSV</em> 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>, <em>CSV</em> 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><em>CSV</em> files can be created or edited with a normal text editor. The most
-important attribute of a <em>CSV</em> 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 <em>CSV</em> file. <em>CSV</em> 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>The above 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 <em>CSV</em> 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>When a <em>CSV</em> file is selected for import, <em>Subsurface</em> displays the column
-headers as well as some of the data in the first few lines of the <em>CSV</em>
-file, making it much easier to work with <em>CSV</em> files. <em>CSV</em> files can
-therefore be used in many contexts for importing data into a <em>Subsurface</em>
-dive log. Knowledge of a few basic things about the content of the <em>CSV</em>
-file allows a smooth import of the dives into <em>Subsurface</em>.</p></div>
-</div></div>
-<div class="admonitionblock">
-<table><tr>
-<td class="icon">
-<img src="images/icons/important.png" alt="Important" />
-</td>
-<td class="content">The <em>CSV</em> import has a couple of caveats. One should avoid some special
-characters like ampersand (&), less than (<), greater than (>) and double
-quotes (") as part of the numbers or text within a cell. The file should use
-UTF-8 character set, if using non-ASCII characters. Also the size of the
-<em>CSV</em> file might cause problems. Importing 100 dives at a time (<em>CSV dive
-details</em>) works, but larger files might exceed the limits of the parser
-used. When encountering problems with <em>CSV</em> imports, first try with a
-smaller file to make sure everything works.</td>
-</tr></table>
-</div>
-</div>
-</div>
-</div>
-<div class="sect2">
-<h3 id="S_Companion">5.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 <em>Android device</em> or
-<a href="#S_iphone"><em>iPhone</em></a> with 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 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">5.4.1. Create a Companion App account</h4>
-<div class="ulist"><ul>
-<li>
-<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>
-</li>
-<li>
-<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&fdid=org.subsurface">F-Droid</a>.
-</p>
-</li>
-</ul></div>
-</div>
-<div class="sect3">
-<h4 id="_using_the_subsurface_companion_app_on_an_android_smartphone">5.4.2. Using the Subsurface companion app on an Android smartphone</h4>
-<div class="paragraph"><p>On first use the app has three options:</p></div>
-<div class="ulist"><ul>
-<li>
-<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>
-</li>
-<li>
-<p>
-<em>Retrieve an account.</em> If users forgot their <strong>DIVERID</strong> they will receive an
- email to recover the number.
-</p>
-</li>
-<li>
-<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>
-</li>
-</ul></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 → Preferences →
-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="ulist"><ul>
-<li>
-<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>
-</li>
-<li>
-<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’s advisable to set the
- time to agree with the time of that dive on the dive computer.
-</p>
-</li>
-</ul></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="ulist"><ul>
-<li>
-<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>
-</li>
-</ul></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 selects 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>
-<li>
-<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>
-</li>
-</ul></div>
-</div>
-<div class="sect4">
-<h5 id="_synchronisation">Synchronisation</h5>
-<div class="ulist"><ul>
-<li>
-<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>
-</li>
-<li>
-<p>
-<em>Upload new dives.</em> If selected, each time the user adds a dive location it
- is automatically sent to the server.
-</p>
-</li>
-</ul></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="ulist"><ul>
-<li>
-<p>
-<em>Min duration.</em> In minutes. The app will try to get a location every X
- minutes until stopped by the user.
-</p>
-</li>
-<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 50 m 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’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="S_iphone">5.4.3. Using the Subsurface companion app on an <em>iPhone</em> to record dive locations</h4>
-<div class="paragraph"><p>The iPhone interface is quite simple. One needs to type the user ID
-(obtained during registration) into the space reserved for it, then select
-"Dive in" (see left part of the image below) and start collecting dive
-location information.</p></div>
-<div class="imageblock" style="text-align:center;">
-<div class="content">
-<img src="images/iphone.jpg" alt="FIGURE: Using iPhone companion application" width="640" />
-</div>
-</div>
-<div class="paragraph"><p>Dives can be added automatically or manually. In manual mode, a dive
-location or waypoint is added to the GPS input stream. In automatic mode, a
-continuous path of GPS locations is created from which, much later, after
-import, subsurface can select the appropriate GPS locations based on the
-times of dives. The default mode for the <em>iphone</em> is automatic. When one
-adds a dive, the location service is started automatically and a red bar
-appears at the bottom of the screen. After the dive one can click on the red
-bar to end the location service. While the location service is running one
-can only add dives using the manual mechanism.</p></div>
-<div class="paragraph"><p>One can edit the site name afterwards by selecting the dive from the dive
-list and clicking on the site name. There are no other editable fields. The
-dive list is automatically uploaded from the iPhone to the webservice and
-there is not an option to trigger upload manually.</p></div>
-</div>
-<div class="sect3">
-<h4 id="_downloading_dive_locations_to_the_em_subsurface_em_divelog">5.4.4. 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 → 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="ulist"><ul>
-<li>
-<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’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>
-</li>
-<li>
-<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>
-</li>
-</ul></div>
-</div>
-</div>
-<div class="sect2">
-<h3 id="S_LoadImage">5.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">5.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 up 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 three ways:</p></div>
-<div class="ulist"><ul>
-<li>
-<p>
-<strong>Pro-actively</strong>: Before the dive, ensure synchronisation of the dive computer time settings with
- the time settings of the camera by changing the date-time settings on one or both of these devices.
-</p>
-</li>
-<li>
-<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>
-</li>
-</ul></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="ulist"><ul>
-<li>
-<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 <em>Time shift</em> 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 dive computer showing time</em>. This brings up
- a file browser with which one can select the photograph of the dive computer time. 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.
- Image <strong>B</strong> above shows a photograph of the face of the dive computer and with the date-time tool set to the
- date-time.
-</p>
-</li>
-</ul></div>
-<div class="paragraph"><p>If the timestamp of a photograph is more than 30 minutes before or after the
-dive, it is not placed on the dive profile.</p></div>
-</div>
-<div class="sect3">
-<h4 id="_viewing_the_photos">5.5.2. Viewing the photos</h4>
-<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>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. In order to view the photos
- on the dive profile, activate the <em>show-photos</em> button in the tool bar to
- the left of the dive profile:
-</p>
-</li>
-</ul></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>This results in a profile display as in the image below:</p></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">5.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>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">5.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 by the operating system (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 class="sect3">
-<h4 id="S_FindMovedImages">5.5.5. Moving photographs among directories, hard disks or computers</h4>
-<div class="paragraph"><p>After a photograph has been loaded into <em>Subsurface</em> and associated with a specific dive, the directory
- where the photo lies is stored, allowing <em>Subsurface</em> to find the photograph when the dive is
- opened again. If the photo or the whole photo collection is moved to another drive or to a different
- machine, it is unlikely that the directory structure will remain identical to that of the original uploaded
- photo. When this happens, <em>Subsurface</em> looks for the photos at their original location before they were moved,
- cannot find them and therefore cannot display them. Because, after moving photos, large numbers of photos
- may need to be deleted and re-imported from the new location, <em>Subsurface</em> has a mechanism that eases the
- process of updating the directory information for each photo: automatic updates using fingerprints.</p></div>
-<div class="paragraph"><p>When a photo is loaded into <em>Subsurface</em>, a fingerprint for the image is calculated and stored with the
- other reference information for that photo. After moving a photo collection (that has already been loaded
- into <em>Subsurface</em>) to a different directory, disk or computer, <em>Subsurface</em> can perform the
- following steps:</p></div>
-<div class="ulist"><ul>
-<li>
-<p>
-look through a particular directory (and all its subdirectories recursively)
- where photos have been moved
- to,
-</p>
-</li>
-<li>
-<p>
-calculate fingerprints for all photos in this directory, and
-</p>
-</li>
-<li>
-<p>
-if there is a match between a calculated fingerprint and the one originally
- calculated when a photo was
- loaded into <em>Subsurface</em> (even if the original file name has changed), to
- automatically update the directory information so that <em>Subsurface</em> can find
- the photo in the new moved directory.
-</p>
-</li>
-</ul></div>
-<div class="paragraph"><p>This is achieved by selecting from the Main Menu: <em>File → Find moved images</em>. This brings up a window within
- which the NEW directory of the photos needs to be specified. Select the appropriate directory and click
- the <em>Scan</em> button towards the bottom right of the panel. The process may require several minutes to
- complete, after which <em>Subsurface</em> will show the appropriate photographs when a particular dive is opened.</p></div>
-<div class="sidebarblock" id="Image_fingerprint_upgrade">
-<div class="content">
-<div class="paragraph"><p><strong>Upgrading existing photo collections without fingerprints</strong></p></div>
-<div class="admonitionblock">
-<table><tr>
-<td class="icon">
-<img src="images/icons/important.png" alt="Important" />
-</td>
-<td class="content"><em>Subsurface</em> automatically calculates fingerprints for all images that can
-be accessed by <em>Subsurface</em>. When manipulating images, ensure that all the
-images associated with the dive log can be accessed by <em>Subsurface</em>.</td>
-</tr></table>
-</div>
-<div class="paragraph"><p><em>Subsurface</em> automatically checks and, if necessary, updates the
-fingerprints associated with a single dive if:
-- The images associated with that dive are visible as thumbnails on the <strong>Dive
- Profile</strong>.
-- One edits anything in the <strong>Notes tab</strong> panel and save the edits by selecting
- <em>Apply changes</em>.</p></div>
-</div></div>
-</div>
-</div>
-<div class="sect2">
-<h3 id="_logging_special_types_of_dives">5.6. Logging special types of dives</h3>
-<div class="sect3">
-<h4 id="S_MulticylinderDives">5.6.1. Multicylinder dives</h4>
-<div class="paragraph"><p><em>Subsurface</em> easily handles dives involving more than one
-cylinder. Multi-cylinder diving usually happens (a) if a diver does not have
-enough gas for the complete dive in a single cylinder; (b) if the diver
-needs more than one gas mixture because of the depth or the decompression
-needs of the dive. For this reason multi-cylinder dives are often used by
-technical divers who dive deep or long. As far as <em>Subsurface</em> is concerned,
-there are only two types of information that need to be provided:</p></div>
-<div class="ulist"><ul>
-<li>
-<p>
-<strong>Describe the cylinders used during the dive</strong> This is performed in the <strong>Equipment tab</strong> of
- the <strong>Info</strong> panel, as <a href="#cylinder_definitions">described above</a>. Enter the cylinders one by one,
- specifying the characteristics of the cylinder and the gas composition within each cylinder.
-</p>
-</li>
-<li>
-<p>
-<strong>Record the times at which switches from one cylinder to another was done:</strong> This is information
- provided by some dive computers (provided the diver indicated these changes to the dive computer
- by pressing specific buttons). If the dive computer does not provide the information, the diver has to
- record these changes using a different method, e.g. writing it on a slate.
-</p>
-</li>
-<li>
-<p>
-<strong>Record the cylinder changes on the dive profile</strong>: If the latter option
- was followed, the diver needs to indicate the gas change event by right-clicking at the appropriate point
- in time on the <strong>Dive Profile</strong> panel and indicating the cylinder to which the change was made. After
- right-clicking, follow the context menu to "Add gas change" and select the appropriate cylinder from
- those defined during the first step, above (see image below). If the
- <strong>tank bar</strong> button in the toolbar has been activated, the cylinder switches are also indicated in the
- tank bar.
-</p>
-</li>
-</ul></div>
-<div class="paragraph"><p>Having performed these tasks, <em>Subsurface</em> indicates the appropriate use of
-cylinders in the dive profile. Below is a multi-cylinder dive, starting off
-with EAN28, then changing cylinders to EAN50 after 26 minutes to perform
-decompression.</p></div>
-<div class="imageblock" style="text-align:center;">
-<div class="content">
-<img src="images/multicylinder_dive.jpg" alt="FIGURE: Multicylinder profile" />
-</div>
-</div>
-</div>
-<div class="sect3">
-<h4 id="_sidemount_dives">5.6.2. Sidemount dives</h4>
-<div class="paragraph"><p>Sidemount diving is just another form of multi-cylinder diving, often with
-both or all cylinders having the same gas mixture. Although it is a popular
-configuration for cave divers, sidemount diving can be performed by
-recreational divers who have completed the appropriate training. Sidemount
-dive logging involves, exactly as with multi-cylinder dives, above, three
-steps:</p></div>
-<div class="ulist"><ul>
-<li>
-<p>
-<strong>During the dive, record 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, many 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 times of cylinder changes is the only tricky part of logging sidemount dives.
-</p>
-</li>
-<li>
-<p>
-<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>Info Panel</strong> (see
- image below where two 12 litre cylinder were used).
-</p>
-</li>
-<li>
-<p>
-<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 in the image below.
-</p>
-</li>
-</ul></div>
-<div class="imageblock" style="text-align:center;">
-<div class="content">
-<img src="images/sidemount1.jpg" alt="FIGURE: Sidemount profile" />
-</div>
-</div>
-<div class="paragraph"><p>This section gives an example of the versatility of <em>Subsurface</em> as a dive
-logging tool.</p></div>
-</div>
-<div class="sect3">
-<h4 id="S_sSCR_dives">5.6.3. Semi-closed circuit rebreather (SCR) dives</h4>
-<div class="admonitionblock">
-<table><tr>
-<td class="icon">
-<img src="images/halcyon_RB80.jpg" alt="Note" />
-</td>
-<td class="content">Passive semi-closed rebreathers (pSCR) comprise a technical advance in
-diving equipment that recirculates the breathing gas that a diver breathes,
-while removing carbon dioxide from the exhaled gas. While a small amount
-(typically a tenth) of the exhaled breathing gas is released into the water,
-a small amount of fresh gas is released from the back gas cylinder
-(typically containing nitrox). A diver, using a single cylinder of
-breathing gas can therefore dive for much longer periods than using a
-recreational open-circuit configuration. With pSCR equipment, a very small
-amount of breathing gas is released every time the breather inhales. With
-active SCR (aSCR) equipment, in contrast, a small amount of breathing gas is
-released continuously from the back cylinder.</td>
-</tr></table>
-</div>
-<div class="paragraph"><p>To log pSCR dives, no special procedures are required, just the normal steps
-outlined above:</p></div>
-<div class="ulist"><ul>
-<li>
-<p>
-Select pSCR in the <em>Dive Mode</em> dropdown list on the <strong>Info</strong> panel.
-</p>
-</li>
-<li>
-<p>
-pSCR diving often involves gas changes, requiring an additional cylinder.
- Define all the appropriate cylinders as described above and indicate the
- cylinder/gas changes as described above in the section on
- <a href="#S_MulticylinderDives">multicylinder dives</a>.
-</p>
-</li>
-</ul></div>
-<div class="paragraph"><p>If a pSCR <em>Dive Mode</em> has been selected, the dive ceiling for pSCR dives is
-adjusted for the oxygen drop across the mouthpiece which often requires
-longer decompression periods. Below is a dive profile of a pSCR dive using
-EAN36 on the back cylinder and oxygen for decompression. Note that this dive
-lasted over two hours.</p></div>
-<div class="imageblock" style="text-align:center;">
-<div class="content">
-<img src="images/pSCR_profile.jpg" alt="FIGURE: pSCR profile" />
-</div>
-</div>
-</div>
-<div class="sect3">
-<h4 id="S_CCR_dives">5.6.4. Closed circuit rebreather (CCR) dives</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. The
-CCR interface of <em>Subsurface</em> is currently experimental and under active
-development. Subsurface currently supports Poseidon MkVI and APD
-Discovery/Evolution dive computers. In contrast to a conventional
-recreational 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 digital databases: one
-dive at a time.</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 → Import log files</em> to bring up the
-<a href="#Unified_import">universal import dialogue</a>. As explained in that
-section, the bottom right hand of the import dialogue contains a dropdown
-list (labled <em>Filter:</em>) of appropriate devices that currently
-includes(Poseidon) MkVI or APD log viewer files (import for other CCR
-equipment is under active development). 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. The selected dive is imported to the
-<em>Subsurface</em> dive list.</p></div>
-</div>
-<div class="sect4">
-<h5 id="_displayed_information_for_a_ccr_dive">Displayed information for a CCR 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 contrast to
-recreational equipment (where pO<sub>2</sub> values are calculated based on gas
-composition and dive depth), CCR equipment provide actual measurements of
-pO<sub>2</sub>, derived from oxygen sensors. In this case the graph for oxygen
-partial pressure should be fairly flat, reflecting the setpoint settings
-during the dive. The mean pO<sub>2</sub> is NOT the mean oxygen partial pressure as
-given by the CCR equipment, but a value calculated by <em>Subsurface</em> as
-follows:</p></div>
-<div class="ulist"><ul>
-<li>
-<p>
-For TWO O<sub>2</sub> sensors the mean value of the two sensors are given.
-</p>
-</li>
-<li>
-<p>
-For THREE-sensor systems (e.g. APD), the mean value is also used. However
- differences of more than 0,1 bar in the simultaneous readings of different
- sensors are treated as spurious. If one of the three sensors provides
- spurious data, it is ignored.
-</p>
-</li>
-<li>
-<p>
-If no sensor data are available, the pO<sub>2</sub> value is assumed to be equal to
- the setpoint.
-</p>
-</li>
-</ul></div>
-<div class="paragraph"><p>The mean pO<sub>2</sub> of the sensors is indicated with a green line,</p></div>
-<div class="paragraph"><p>The oxygen setpoint values as well as the readings from the individual
-oxygen sensors can be shown. The display of additional CCR information is
-turned on by checking the appropriate checkboxes in the <em>Preferences</em> panel
-(accessible by selecting <a href="#S_CCR_options"><em>File → Preferences →
-Graph</em></a>). This part of the <em>Preferences</em> panel is shown in the image below,
-representing two checkboxes that modify the display of pO<sub>2</sub> when the
-appropriate toolbar button on the Dive Profile has been activated.</p></div>
-<div class="imageblock" style="text-align:center;">
-<div class="content">
-<img src="images/CCR_preferences_f20.jpg" alt="FIGURE: CCR preferences panel" />
-</div>
-</div>
-<div class="paragraph"><p>Checking any of these check boxes allows the display of additional
-oxygen-related information whenever the pO<sub>2</sub> toolbar button on the
-<em>Profile</em> panel is activated. The first checkbox allows the display of
-setpoint information. This is a red line superimposed on the green oxygen
-partial pressure graph and allows a comparison of the mean measured oxygen
-partial pressure and the setpoint values, as shown below.</p></div>
-<div class="imageblock" style="text-align:center;">
-<div class="content">
-<img src="images/CCR_setpoint_f20.jpg" alt="FIGURE: CCR setpoint and po2 graph" />
-</div>
-</div>
-<div class="paragraph"><p>The second checkbox allows the display of the data from each individual
-oxygen sensor of the CCR equipment. The data for each sensor is colour-coded
-as follows:</p></div>
-<div class="ulist"><ul>
-<li>
-<p>
-Sensor 1: grey
-</p>
-</li>
-<li>
-<p>
-Sensor 2: blue
-</p>
-</li>
-<li>
-<p>
-Sensor 3: brown
-</p>
-</li>
-</ul></div>
-<div class="paragraph"><p>The mean oxygen pO<sub>2</sub> is indicated by the green line. This allows the direct
-comparison of data from each of the oxygen sensors, useful for detecting
-abnormally low or erratic readings from a particular sensor.</p></div>
-<div class="imageblock" style="text-align:center;">
-<div class="content">
-<img src="images/CCR_sensor_data_f20.jpg" alt="FIGURE: CCR sensor data graph" />
-</div>
-</div>
-<div class="paragraph"><p>The setpoint data can be overlaid on the oxygen sensor data by activating
-both of the above check boxes. Partial pressures for nitrogen (and helium,
-if applicable) are shown in the usual way as for open circuit dives.</p></div>
-<div class="paragraph"><p><em>Events</em>: Several events are logged, e.g. switching the mouthpiece to open
-circuit. These events are indicated by yellow triangles and, if one hovers
-over a triangle, a description of that event is given as the bottom line in
-the <a href="#S_InfoBox">Information Box</a>.</p></div>
-<div class="paragraph"><p><em>Cylinder pressures</em>: Some CCR dive computers like the Poseidon MkVI record
-the pressures of the oxygen and diluent cylinders. The pressures of these
-two cylinders are shown as green lines overlapping the depth profile. In
-addition, start and end pressures for both oxygen and diluent cylinders are
-shown in the <em>Equipment Tab</em>. Below is a dive profile for a CCR dive,
-including an overlay of setpoint and oxygen sensor data, as well as the
-cylinder pressure data. In this case there is good agreement from the
-readings of the two oxygen sensors.</p></div>
-<div class="imageblock" style="text-align:center;">
-<div class="content">
-<img src="images/CCR_dive_profile_f22.jpg" alt="FIGURE: CCR dive profile" />
-</div>
-</div>
-<div class="paragraph"><p><em>Equipment-specific information</em>: Equipment-specific information gathered by
-<em>Subsurface</em> is shown in the <a href="#S_ExtraDataTab">Extra data tab</a>. This may
-include setup information or metadata about the dive.</p></div>
-<div class="paragraph"><p>The deco ceiling calculated by Subsurface is not very accurate because the
-precise pressure of nitrogen in the loop can usually not be determined from
-the dive log imported from the CCR equipment. Many CCR dive computers,
-however, report an internally-calculated deco ceiling that is reported in
-the dive log, reflecting a more accurate assessment. The display of this
-ceiling is activated by clicking the appropriate button to the left of the
-dive profile:</p></div>
-<div class="imageblock">
-<div class="content">
-<img src="images/icons/cceiling.jpg" alt="DC ceiling icon" />
-</div>
-</div>
-<div class="paragraph"><p>The default colour of the computer-generated deco ceiling is white. However,
-this can be set to red by checking the appropriate check box after selecting
-<em>File → Preferences → Graph</em>. Below is a dive profile indicating the dive
-computer-generated deco ceiling:</p></div>
-<div class="imageblock" style="text-align:center;">
-<div class="content">
-<img src="images/CCR_dive_ceilingF22.jpg" alt="FIGURE: CCR computer-generated deco ceiling" />
-</div>
-</div>
-<div class="paragraph"><p>More equipment-specific information for downloading CCR dive logs for
-Poseidon MkVI and APD equipment can be found in
-<a href="#_appendix_b_dive_computer_specific_information_for_importing_dive_information">Appendix
-B</a>.</p></div>
-</div>
-</div>
-</div>
-</div>
-</div>
-<div class="sect1">
-<h2 id="_obtaining_more_information_about_dives_entered_into_the_logbook">6. Obtaining more information about dives entered into the logbook</h2>
-<div class="sectionbody">
-<div class="sect2">
-<h3 id="_the_strong_info_strong_tab_for_individual_dives">6.1. The <strong>Info</strong> tab (for individual dives)</h3>
-<div class="paragraph"><p>The 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 F</a> for more information.</td>
-</tr></table>
-</div>
-</div>
-<div class="sect2">
-<h3 id="S_ExtraDataTab">6.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">6.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">6.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>Couleur</strong></p></td>
-<td align="left" valign="top"><p class="table"><strong>Vitesse de descente (m/min)</strong></p></td>
-<td align="left" valign="top"><p class="table"><strong>Vitesse de remontée (m/min)</strong></p></td>
-</tr>
-<tr>
-<td align="left" valign="top"><p class="table">Rouge</p></td>
-<td align="left" valign="top"><p class="table">> 30</p></td>
-<td align="left" valign="top"><p class="table">> 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">Jaune</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">Vert clair</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">Vert foncé</p></td>
-<td align="left" valign="top"><p class="table">< 1.5</p></td>
-<td align="left" valign="top"><p class="table">< 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 plotted as a grey line, indicating mean dive depth up
-to a particular moment during the dive.</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 O<sub>2</sub>,
-N<sub>2</sub>, 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 contrast,
-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">6.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 <strong>Equipment</strong> 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="S_InfoBox">6.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 if a maximum pO<sub>2</sub> of 1.4 is specified in the
-<strong>Preferences</strong> section (select <em>File</em> → Preferences → Graph_ and edit the
-text box <em>Max pO<sub>2</sub> when showing MOD</em>. 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 either 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. TTS is calculated assuming an ascent surface air
-consumption (SAC) for the gas currently used. Even if the profile contains
-several gas switches, TTS at a specific moment during the dive is calculated
-using the current gas. For TTS longer than 2 hours, it is not accurately
-calculated and Subsurface only indicates <em>TTS > 2h</em>.</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">6.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="ulist"><ul>
-<li>
-<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>
-</li>
-<li>
-<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>
-</li>
-<li>
-<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>
-</li>
-<li>
-<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
- gradient factor shown is an interpolation between the GFLow and GFHigh
- values specified in the Graph tab of the <strong>Preferences Panel</strong> of
- <strong>Subsurface</strong>.
-</p>
-</li>
-<li>
-<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>
-</li>
-</ul></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="ulist"><ul>
-<li>
-<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>
-</li>
-<li>
-<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>
-</li>
-<li>
-<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>
-</li>
-<li>
-<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>
-</li>
-<li>
-<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>
-</li>
-</ul></div>
-</div>
-</div>
-</div>
-</div>
-<div class="sect1">
-<h2 id="_organising_the_logbook_manipulating_groups_of_dives">7. Organising the logbook (Manipulating groups of dives)</h2>
-<div class="sectionbody">
-<div class="sect2">
-<h3 id="_the_dive_list_context_menu">7.1. The Dive List context menu</h3>
-<div class="paragraph"><p>Several actions on either a single dive or a group of dives can be performed
-using the Dive List Context Menu, found by selecting either a single 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_columns_showed_in_the_strong_dive_list_strong_panel">7.1.1. Customising the columns 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 (reflected by the check symbols) and the list is immediately
-updated. Preferences for information shown in the <strong>Dive List</strong> are saved and
-used when <em>Subsurface</em> is re-opened.</p></div>
-</div>
-</div>
-<div class="sect2">
-<h3 id="S_Renumber">7.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 → 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 class="paragraph"><p>One can also renumber a few selected dives in the dive list. Select the
-dives that need renumbering. Right-click on the selected list and use the
-Dive List Context Menu to perform the renumbering. A popup window appears
-requiring the user to specify the starting number for the renumbering
-process.</p></div>
-</div>
-<div class="sect2">
-<h3 id="S_Group">7.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 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) select <em>Log → 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">7.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>Notes</strong>
-panel. Here one 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, 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 the edited information.</p></div>
-</div>
-<div class="sect3">
-<h4 id="_viewing_the_dives_during_a_particular_trip">7.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">7.3.3. Collapsing or expanding dive information for different trips</h4>
-<div class="paragraph"><p>After selecting a particular trip in the dive list, the context menu allows
-several possibilities to expand or collapse dives within trips. This
-includes expanding all trips and collapsing all trips.</p></div>
-</div>
-<div class="sect3">
-<h4 id="_merging_dives_from_more_than_one_trip_into_a_single_trip">7.3.4. Merging dives from more than one trip into a single trip</h4>
-<div class="paragraph"><p>After selecting a trip title, the context menu allows the merging of trips
-by either merging the selected trip with the trip below or with the trip
-above. (Merge trip with trip below; Merge trip with trip above)</p></div>
-</div>
-<div class="sect3">
-<h4 id="_splitting_a_single_trip_into_more_than_one_trip">7.3.5. Splitting a single trip into more than one trip</h4>
-<div class="paragraph"><p>If a trip includes ten dives, the user can split this trip into two trips
-(trip 1: top 4 dives; trip 2: bottom 6 dives) by selecting and
-right-clicking the top four 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 four 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">7.4. Manipulating single dives</h3>
-<div class="sect3">
-<h4 id="_delete_a_dive_from_the_dive_log">7.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">7.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 or below the trip to which they belonged, depending
-on the date and time of the unlinked dive.</p></div>
-</div>
-<div class="sect3">
-<h4 id="_add_a_dive_to_the_trip_immediately_above">7.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 a separate trip. To do this, select and right-click the dive(s) to
-bring up the context menu, and then select <strong>Create new trip above</strong>.</p></div>
-</div>
-<div class="sect3">
-<h4 id="_shift_the_start_time_of_dive_s">7.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, 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 ealier or later.</p></div>
-</div>
-<div class="sect3">
-<h4 id="_merge_dives_into_a_single_dive">7.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>Notes</strong> panel to reflect events or conditions that apply
-to the merged dive. The figure below shows the depth profile of two 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 class="sect3">
-<h4 id="_undo_dive_manipulations">7.4.6. Undo dive manipulations</h4>
-<div class="paragraph"><p>Important actions on dives or trips, described above, can be undone or
-redone. This includes: <em>delete dives</em>, <em>merge dives</em>, <em>renumber dives</em> and
-<em>shift dive times</em>. To do this after performing any of these actions, from
-the <strong>Main Menu</strong> select <em>Edit</em>. This brings up the possibility to <em>Undo</em> or
-<em>Redo</em> an action.</p></div>
-</div>
-</div>
-<div class="sect2">
-<h3 id="S_Filter">7.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 → 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 (see image below). The
-<em>Filter Panel</em> can be reset (i.e. all current filters cleared) by selecting
-the <strong>yellow angled arrow</strong>. The <em>Filter Panel</em> may also be minimised by
-selecting the <strong>green up-arrow". 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 *red button</strong>
-with the white cross.</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, check at least one check box in one
-of the four check lists. The dive list is then shortened to include only the
-dives that pertain to the 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">8. Exporting the dive log or parts of the dive log</h2>
-<div class="sectionbody">
-<div class="paragraph"><p>There are two routes for the export of dive information from Subsurface:</p></div>
-<div class="ulist"><ul>
-<li>
-<p>
-Exporter les informations de plongée vers <em>Facebook</em>
-</p>
-</li>
-<li>
-<p>
-<a href="#S_Export_other">Exporter des informations de plongée vers d’autres
- destinations ou formats</a>
-</p>
-</li>
-</ul></div>
-<div class="sect2">
-<h3 id="S_facebook">8.1. Export des informations de plongée vers <em>Facebook</em></h3>
-<div class="paragraph"><p>L’export des plongées vers <em>Facebook</em> est géré différemment des autres types
-d’export car une connexion vers <em>Facebook</em> est nécessaire, nécessitant un
-identifiant et un mot de passe. À partir du menu principal, si vous
-sélectionnez <em>Fichier → Préférences → Facebook</em>, un écran de connexion est
-présenté (image <strong>A</strong> sur la gauche, ci dessous). Entrez l’identifiant et le
-mot de passe <em>Facebook</em>. Une fois connecté à <em>Facebook</em>, le panneau de
-l’image <strong>B</strong> ci dessous est présenté, avec un bouton <em>Déconnecter de
-Facebook</em> pour fermer la connexion <em>Facebook</em>.</p></div>
-<div class="imageblock" style="text-align:center;">
-<div class="content">
-<img src="images/facebook1_f20.jpg" alt="Figure: Facebook login" />
-</div>
-</div>
-<div class="paragraph"><p>From the <em>Subsurface</em> window it is easy to determine whether <em>Subsurface</em>
-has a valid connection to <em>Facebook</em> From the <strong>Main Menu</strong>, select <em>Share on
-→ Facebook</em> (image <strong>A</strong>, below). Normally, the <em>Facebook</em> option is greyed
-out. But if there is a connection to <em>Facebook</em>, this option is active
-(i.e. in black colour and can be selected).</p></div>
-<div class="paragraph"><p>Une fois qu’une connexion à <em>Facebook</em> est établie, transférer un profil de
-plongée vers <em>Facebook</em> est facile. Assurez-vous que la plongée à transférer
-est affichée dans le panneau <strong>Profil de plongée</strong> de <em>Subsurface</em>. Si, à
-partir du <strong>menu principal</strong>, vous sélectionnez <em>Partager sur → Facebook</em>,
-une fenêtre s’affiche, pour déterminer quelles informations seront
-transférées avec le profil de plongée (voir l’image <strong>B</strong> ci-dessous). Pour
-transférer un profil de plongée vers <em>Facebook</em>, le nom d’un album
-<em>Facebook</em> doit être fourni. Les cases à cocher sur la partie gauche
-permettent de sélectionner des informations supplémentaires à transférer
-avec le profil de plongée. Ces informations sont affichées dans le champs de
-texte sur la partie droite du panneau. (image <strong>B</strong> ci dessous). Vous pouvez
-facilement modifier le message qui sera envoyé avec le profil de
-plongée. Une fois les informations supplémentaires ajoutées et vérifiées,
-sélectionner le bouton <em>OK</em> qui lance le transfert vers <em>Facebook</em>. Après un
-moment, une fenêtre apparait indiquant le succès du transfert.</p></div>
-<div class="paragraph"><p>À la fois l’album créé et la publication sur votre ligne temporelle seront
-marquées comme privés. Pour que vos amis puissent voir la publication,
-modifier les permissions à partir d’une connexion Facebook standard depuis
-un navigateur ou l’application Facebook. Malgré que cela soit une étape
-supplémentaire, c’est la meilleure solution pour éviter d’avoir des
-publications non désirées sur votre ligne temporelle publique.</p></div>
-<div class="imageblock" style="text-align:center;">
-<div class="content">
-<img src="images/facebook2_f20.jpg" alt="Figure: Facebook login" />
-</div>
-</div>
-<div class="paragraph"><p>Si besoin, fermer la connexion <em>Facebook</em> en fermant <em>Subsurface</em> ou en
-sélectionnant _Fichier → Préférences → Facebook, à partir du menu
-principal et en cliquant sur le bouton approprié dans le panneau des
-préférences Facebook.</p></div>
-</div>
-<div class="sect2">
-<h3 id="S_Export_other">8.2. Export dive information to other destinations or formats</h3>
-<div class="paragraph"><p>For non-<em>Facebook exports</em>, the export function can be reached by selecting
-<em>File → 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_f20.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>
-<li>
-<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>
-</li>
-<li>
-<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>
-</li>
-<li>
-<p>
-<em>DiveShare</em> is also a dive log repository on the Internet focusing on the
- recreational dives. In order to upload dives one has to provide a used ID,
- so registration with <em>http://scubadiveshare.com</em> is required.
-</p>
-</li>
-<li>
-<p>
-<em>CSV dive details</em>, that includes the most critical information of the dive
- profile. Included information of a dive is: dive number, date, time, buddy,
- duration, depth, temperature and pressure: in short, most of the information
- that recreational divers enter into handwritten log books.
-</p>
-</li>
-<li>
-<p>
-<em>CSV dive profile</em>, that includes a large amount of detail for each dive,
- including the depth profile, temperature and pressure information of each
- dive.
-</p>
-</li>
-<li>
-<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. The HTML export cannot be changed or edited. It contains
- most of the information recorded in the dive log. However, it does not show
- the calculated values in the <strong>Dive Profile</strong> panel, e.g. calculated cylinder
- pressure, gas pressures and MOD. The HTML export 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). A typical use of this option is to export
- all one’s dives to a smartphone or a tablet where it would serve as a very
- portable record of dives useful for dive companies that wish to verify the
- dive history of a diver, often doing away with the need to carry one’s
- original logbook with one when doing dives with dive companies.
-</p>
-</li>
-<li>
-<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. If one
- selects any of the dive sites on the map, a summary of the dive is available
- in text, as shown in the image below.
-</p>
-</li>
-</ul></div>
-<div class="imageblock" style="text-align:center;">
-<div class="content">
-<img src="images/mapview_f20.jpg" alt="Figure: HTML Map export view" />
-</div>
-</div>
-<div class="ulist"><ul>
-<li>
-<p>
-<em>Image depths</em>, which creates a text file that contains the file names of
- all photos or images attached to any of the selected dives in the <em>Dive
- List</em>, together with the depth under water where of each of those photos
- were taken.
-</p>
-</li>
-<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 to the HTML exports.
-</p>
-</li>
-<li>
-<p>
-Export List only: a list of dives only (date, time, depth, duration) will be exported
- and the detailed dive information, e.g. dive profile, will not be available.
-</p>
-</li>
-</ul></div>
-</li>
-<li>
-<p>
-Under <em>Style Options</em> some style-related options are available like font
- size and theme.
-</p>
-</li>
-</ul></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>
-<div class="sect1">
-<h2 id="S_Cloud_access">9. 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’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 <em>divelogs.de</em> and <em>Diving Log</em> offer to store
-dive log information on the Internet.</p></div>
-<div class="paragraph"><p><em>Subsurface</em> includes access to a transparently integrated cloud storage
-back end that is available to all Subsurface users. Storing and retrieving a
-dive log from the cloud is no more difficult than accessing the dives on the
-local hard disk. The only requirement is that one should first register as
-a user on the cloud. To use <em>Subsurface cloud storage</em> , follow these
-steps:</p></div>
-<div class="sect2">
-<h3 id="_create_a_cloud_storage_account">9.1. Create a cloud storage account</h3>
-<div class="ulist"><ul>
-<li>
-<p>
-Open the <strong>Network Preferences</strong> by selecting <em>File</em> → <em>Preferences</em> → <em>Network</em>.
-</p>
-</li>
-<li>
-<p>
-In the section headed <em>Subsurface cloud storage</em>, enter an email address that
- <em>Subsurface</em> can use for user registration.
-</p>
-</li>
-<li>
-<p>
-Enter a novel password that <em>Subsurface</em> will use to store the
- dive log in the cloud.
-</p>
-</li>
-<li>
-<p>
-Click <em>Apply</em> to send the above email address and password to the
- (remote) cloud server. The server responds by sending a verification PIN to
- the above email address (This is the <strong>only</strong> occasion that <em>Subsurface</em> uses the
- email address provided above). The <strong>Network Preferences</strong> dialog now has a new PIN text
- box, not visible previously.
-</p>
-</li>
-<li>
-<p>
-Enter the PIN in the corresponding text box in the <strong>Network Preferences</strong> dialog
-(this field is only visible while the server is waiting for email
-address confirmation)
-</p>
-</li>
-<li>
-<p>
-Click <em>Apply</em> again. The <em>Subsurface cloud storage</em> account
-will be marked as verified and the <em>Subsurface cloud storage</em> service is initialised for use.
-</p>
-</li>
-</ul></div>
-</div>
-<div class="sect2">
-<h3 id="_using_em_subsurface_cloud_storage_em">9.2. Using <em>Subsurface cloud storage</em></h3>
-<div class="ulist"><ul>
-<li>
-<p>
-Once the cloud storage has been initialised, two new items appear in the
- <em>File</em> menu of the main menu system: <em>Open cloud storage</em> and <em>Save to cloud storage</em>.
-These options allow the user to load and save data to the <em>Subsurface
-cloud storage</em> server.
-</p>
-</li>
-<li>
-<p>
-In the <em>Defaults Preferences</em> tab, one can select to use the <em>Subsurface cloud
-storage</em> data as one’s default data file by checking the check box marked <em>Cloud storage default file</em>.
- This means that the data from
-the <em>Subsurface cloud storage</em> is loaded when <em>Subsurface</em> starts ans saved there when one closes <em>Subsurface</em>.
-</p>
-</li>
-<li>
-<p>
-<em>Subsurface</em> keeps a local copy of the data and the cloud facility remains fully
-functional even if used while disconnected to the Internet. <em>Subsurface</em> simply synchronises the
-data with the cloud server the next time ithe program is used while the computer is
-connected to the Internet.
-</p>
-</li>
-</ul></div>
-</div>
-<div class="sect2">
-<h3 id="S_Cloud_storage">9.3. Web access to <em>Subsurface cloud storage</em></h3>
-<div class="paragraph"><p>One of the nice side benefits of using <em>Subsurface cloud storage</em> is that
-one can also access one’s dive data from any web browser. Simply open
-<a href="https://cloud.subsurface-divelog.org"><em>https://cloud.subsurface-divelog.org</em></a>,
-log in with the same email and password, and you can see an HTML export of
-the last dive data that was synced to the <em>Subsurface cloud storage</em>. The
-dive information that is shown is only the contents of the recorded dive
-logs, NOT the calculated values shown in the <strong>Profile</strong> panel, including some
-cylinder pressures, deco ceilings and O<sub>2</sub>/He/N<sub>2</sub> partial pressures.</p></div>
-</div>
-<div class="sect2">
-<h3 id="_other_cloud_services">9.4. Other cloud services</h3>
-<div class="paragraph"><p>If one prefers not to use the integrated cloud storage of dive logs (and
-don’t need the web access), it is also simple to store dive logs in the
-cloud using several of the existing facilities on the Internet. 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’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’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’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’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’s dive
-log. To Store a dive log on <em>Dropbox</em>, select <em>File → 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 <em>Dropbox</em>, select <em>File → 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>
-<div class="sect1">
-<h2 id="S_PrintDivelog">10. Printing a dive log</h2>
-<div class="sectionbody">
-<div class="paragraph"><p><em>Subsurface</em> provides a simple and flexible interface to print a whole dive log or only a few selected dives.
- Pre-installed templates or a custom written template can be used to choose where the data are fitted into the page.</p></div>
-<div class="paragraph"><p>Before printing, two decisions are required:</p></div>
-<div class="ulist"><ul>
-<li>
-<p>
-Should the whole dive log be printed or only part of it? If only part of the
- dive log is required, then select the required dives from the <strong>Dive List</strong>
- panel.
-</p>
-</li>
-<li>
-<p>
-If the dive profiles needs printing, what gas partial pressure information
- should be shown? Select the appropriate toggle-buttons on the button bar to
- the left of the <strong>Dive Profile</strong> panel.
-</p>
-</li>
-</ul></div>
-<div class="paragraph"><p>If <em>File → Print</em> is selected from the Main menu, the the dialogue below
-(image <strong>A</strong>) appears. Three specifications are needed to achieve the desired
-information and page layout:</p></div>
-<div class="imageblock" style="text-align:center;">
-<div class="content">
-<img src="images/Print1_f22.jpg" alt="FIGURE: Print dialogue" />
-</div>
-</div>
-<div class="olist arabic"><ol class="arabic">
-<li>
-<p>
-Under <em>Print type</em> select one of two options:
-</p>
-<div class="ulist"><ul>
-<li>
-<p>
-<em>Dive list print</em>: Print dives from the <strong>Dive List</strong> panel with profiles and
- other information.
-</p>
-</li>
-<li>
-<p>
-<em>Statistics print</em>: Print yearly statistics of the dives.
-</p>
-</li>
-</ul></div>
-</li>
-<li>
-<p>
-Under <em>Print options</em> select:
-</p>
-<div class="ulist"><ul>
-<li>
-<p>
-Printing only the dives selected from the dive list prior to activating the
- print dialogue by checking the box <em>Print only selected dives</em>. If this
- check box is <strong>not</strong> checked all dives in the <strong>Dive List</strong> panel are printed.
-</p>
-</li>
-<li>
-<p>
-Printing in colour, achieved by checking the box with <em>Print in colour</em>. If
- this check box is not checked, printing is in monochrome (grey scale).
-</p>
-</li>
-</ul></div>
-</li>
-</ol></div>
-<div class="paragraph"><p>Under <em>Template</em> select a template to be used as the page layout. There are
-several templates (see image <strong>B</strong>, above).</p></div>
-<div class="ulist"><ul>
-<li>
-<p>
-<em>Table</em>: This prints a summary table of all dives selected (see below).
-</p>
-</li>
-</ul></div>
-<div class="imageblock" style="text-align:center;">
-<div class="content">
-<img src="images/Print_summarylist_f22.jpg" alt="FIGURE: Print summary table" />
-</div>
-</div>
-<div class="ulist"><ul>
-<li>
-<p>
-<em>Flow layout</em>: Print the text associated with each dive without printing the
- dive profiles
- of each dive (see below):
-</p>
-</li>
-</ul></div>
-<div class="imageblock" style="text-align:center;">
-<div class="content">
-<img src="images/Print_flow_layout_f22.jpg" alt="FIGURE: Print flow layout" />
-</div>
-</div>
-<div class="ulist"><ul>
-<li>
-<p>
-<em>One Dive</em>: Print one dive per page, also showing the dive profile (see
- below)
-</p>
-</li>
-</ul></div>
-<div class="imageblock" style="text-align:center;">
-<div class="content">
-<img src="images/print2_f22.jpg" alt="FIGURE: Print one dive / page" />
-</div>
-</div>
-<div class="ulist"><ul>
-<li>
-<p>
-<em>Two Dives</em>: Print two dives per page, also showing the dive profiles.
-</p>
-</li>
-<li>
-<p>
-<em>Six Dives</em>: Print six dives per page, also showing the dive profiles.
-</p>
-</li>
-</ul></div>
-<div class="paragraph"><p>Users can <em>Preview</em> the printed page by selecting the <em>Preview</em> button on
-the dialogue (see image <strong>A</strong> at the start of this section). 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 (see image <strong>A</strong> at the start of this
-section). This activates the regular print dialogue used by the user
-operating system, allowing one to choose a printer and to set its properties
-(see image below):</p></div>
-<div class="imageblock" style="text-align:center;">
-<div class="content">
-<img src="images/Print_print_f22.jpg" alt="FIGURE: Print dialog" />
-</div>
-</div>
-<div class="paragraph"><p>Set the print resolution of the printer to an appropriate value by changing
-the printer <em>Properties</em>. Finally, select the <em>Print</em> button to 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 class="sect2">
-<h3 id="_créer_un_modèle_d_8217_impression_personnalisé_avancé">10.1. Créer un modèle d’impression personnalisé (avancé)</h3>
-<div class="paragraph"><p>Writing a custom template is an effective way to produce highly customized
-printouts. Subsurface uses HTML templates to render printing. One can create
-a template, export a new template, import an existing template and delete an
-existing template by using the appropriate buttons under the <em>Template</em>
-dropdown list in the print dialogue. See <a href="#S_APPENDIX_E">APPENDIX E</a> for
-information on how to write or modify a template.</p></div>
-</div>
-</div>
-</div>
-<div class="sect1">
-<h2 id="S_Configure">11. Configurer un ordinateur de plongée</h2>
-<div class="sectionbody">
-<div class="paragraph"><p><em>Subsurface</em> permet de configurer son ordinateur de plongée. Actuellement,
-les familles d’ordinateurs supportés sont Heinrichs-Weikamp (OSTC 2, OSTC 3)
-et Suunto Vyper (Stinger, Mosquito, D3, Vyper, Vytec, Cobra, Gekko et
-Zoop). De nombreux paramètres de ces ordinateurs de plongée peuvent être
-lues et modifiées. La première étape est de s’assurer que les pilotes pour
-votre ordinateur de plongée sont installés (également nécessaire pour
-télécharger les plongées) et que le nom de périphérique de l’ordinateur de
-plongée est connu. Voir
-<a href="#_appendix_a_operating_system_specific_information_for_importing_dive_information_from_a_dive_computer">ANNEXE A</a> pour plus d’informations sur la manière de procéder.</p></div>
-<div class="paragraph"><p>Une fois que l’ordinateur de plongée est connecté à <em>Subsurface</em>,
-sélectionner <em>Fichier → Configurer l’ordinateur de plongée</em>, à partir du
-menu principal. Fournir le nom du périphérique dans le champ en haut du
-panneau de configuration et sélectionner le bon modèle d’ordinateur de
-plongée à partir du panneau à gauche (voir l’image ci-dessous).</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>En utilisant les boutons appropriés du panneau de configuration, les actions
-suivantes peuvent être réalisées :</p></div>
-<div class="ulist"><ul>
-<li>
-<p>
-<strong>Récupérer les détails disponibles</strong>. Cela charge la configuration existante à partir de l’ordinateur de plongée
- dans <em>Subsurface</em>, en l’affichant dans le panneau de configuration.
-</p>
-</li>
-<li>
-<p>
-<strong>Enregistrer les modifications sur le périphérique</strong>. Cela change la configuration de l’ordinateur
- de plongée pour correspondre aux informations affichées dans le panneau de configuration.
-</p>
-</li>
-<li>
-<p>
-<strong>Sauvegarder</strong>. Cela enregistre la configuration dans un fichier. <em>Subsurface</em> demande
- l’emplacement et le nom du fichier pour enregistrer les informations.
-</p>
-</li>
-<li>
-<p>
-<strong>Restaurer une sauvegarde</strong>. Cela charge les informations à partir d’un fichier de sauvegarde et l’affiche
- dans le panneau de configuration.
-</p>
-</li>
-<li>
-<p>
-<strong>Mettre à jour le firmware</strong>. Si un nouveau firmware est disponible pour l’ordinateur de plongée,
- il sera chargé dans l’ordinateur de plongée.
-</p>
-</li>
-</ul></div>
-</div>
-</div>
-<div class="sect1">
-<h2 id="S_Preferences">12. Setting user <em>Preferences</em> for <em>Subsurface</em></h2>
-<div class="sectionbody">
-<div class="paragraph"><p>There are several user-definable settings within <em>Subsurface</em>, found by
-selecting <em>File → Preferences</em>. The settings are performed in seven groups:
-<strong>Defaults</strong>, <strong>Units</strong>, <strong>Graph</strong>, <strong>Language</strong> and <strong>Network</strong>, <strong>Facebook</strong> and
-<strong>Georeference</strong>, all of which 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>. If <strong>Discard</strong> is selected,
-changes to the preferences are not saved.</p></div>
-<div class="sect2">
-<h3 id="_defaults">12.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_f20.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 needs to specify the directory and
- file name of one’s
- electronic dive log book. This is a file with filename extension of either <em>.xml</em> or <em>.ssrf</em>. When
- launched, <em>Subsurface</em> will automatically load the specified dive log book. There are three options:
-</p>
-<div class="ulist"><ul>
-<li>
-<p>
-<em>No default file</em>: When checked, <em>Subsurface</em> does not automatically load a dive log at startup.
-</p>
-</li>
-<li>
-<p>
-<em>Local default file</em>: When checked, <em>Subsurface</em> automatically loads a dive log from the local hard disk
- as described above.
-</p>
-</li>
-<li>
-<p>
-<em>Cloud storage default file</em>: When checked, <em>Subsurface automatically loads the dive log from the cloud
- device that was initialised using the <strong>Preferences</strong> _Network</em> tab (see below).
-</p>
-</li>
-</ul></div>
-</li>
-<li>
-<p>
-<strong>Display invalid</strong>: Dives can be marked as invalid (when a user wishes to hide
- dives that he/she doesn’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>: Specify the default cylinder listed in
- the <strong>Equipment</strong> tab of the <strong>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, and a 0 value representing no animation
- at all.
-</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">12.2. Units</h3>
-<div class="imageblock" style="text-align:center;">
-<div class="content">
-<img src="images/Pref2_f20.jpg" alt="FIGURE: Preferences Units page" />
-</div>
-</div>
-<div class="paragraph"><p>Here users 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, one 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 class="paragraph"><p>Irrespective of the above settings, dive time measurements can be either in
-seconds or minutes. Choose the appropriate option. GPS coordinates can be
-represented either as traditional coordinates (degrees, minutes, seconds) or
-as decimal degrees Choose the appropriate option.</p></div>
-</div>
-<div class="sect2">
-<h3 id="_graph">12.3. Graph</h3>
-<div class="imageblock" id="S_CCR_options" style="text-align:center;">
-<div class="content">
-<img src="images/Pref3_f20.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, enabled by using the toolbar on the left hand side of the <strong>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 the specified threshold level, the graph is
- highlighted in red, indicating that the particular partial pressure threshold has been exceeded.
-</strong> <em>Max pO<sub>2</sub> is used for calculating the MOD when displaying the maximum operative depth (MOD)
- for a dive. Specify an appropriate partial pressure. A value of 1.4 is commonly used.
-<strong> _Draw dive computer reported ceiling red</em>: This checkbox allows exactly what it says. By default
- the computer reported ceiling is shown in white.
- 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> because of the different algorithms and
- gradient factors, as well as the dynamic way that a
- dive computer can calculate ceilings during a dive.
-</strong> <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 if 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.
-<strong>* <em>Show average depth</em>: If this box is checked, the *Dive Profile</strong> panel contains a grey line that indicates
- the mean depth of the dive up to any time instant during the dive. Normally this is a u-shaped line indicating the deepest mean depth just before the
- ascent.</p></div>
-<div class="ulist"><ul>
-<li>
-<p>
-<strong>Misc</strong>:
-</p>
-<div class="ulist" id="GradientFactors_Ref"><ul>
-<li>
-<p>
-Gradient Factors (GFLow and GFHigh):* 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 70/90 are considered
- harsh. Checking the <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>
-<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>
-</li>
-<li>
-<p>
-<em>CCR: Show setpoints when viewing pO2:</em> With this checkbox ativated, the pO<sub>2</sub>
- graph on the dive profile has an overlay in red which inticates the CCR setpoint
- values. See the section on <a href="#S_CCR_dives">Closed Circuit Rebreather dives</a>.
-</p>
-</li>
-<li>
-<p>
-<em>CCR: Show individual O<sub>2</sub> sensor values when viewing pO<sub>2</sub>:</em> Show the pO<sub>2</sub>
- values associated with each of the individual oxygen sensors of a CCR system.
- See the section on <a href="#S_CCR_dives">Closed Circuit Rebreather dives</a>.
-</p>
-</li>
-</ul></div>
-</li>
-<li>
-<p>
-<strong>Configuring dive planning using rebreather equipment:</strong>
-</p>
-<div class="ulist"><ul>
-<li>
-<p>
-<em>Default CCR setpoint for dive planning:</em> Specify the O<sub>2</sub> setpoint for a
- CCR dive plan. This determines the pO<sub>2</sub> maintained
- during a particular dive. Setpoint changes during the dive can be added via the
- profile context menu.
-</p>
-</li>
-<li>
-<p>
-<em>pSCR O<sub>2</sub> metabolism rate:</em> For a semiclosed rebreather (pSCR) system, this is the
- volume of oxygen used by a diver during a minute. Set this value for pSCR dive planning
- and decompression calculations.
-</p>
-</li>
-<li>
-<p>
-<em>pSCR ratio:</em> For pSCR equipment the dump ratio is the ratio of gas released to the
- environment to that of the gas recirculated to the diver. Set this value for a
- pSCR dive plan. A 1:10 ratio is commonly used.
-</p>
-</li>
-</ul></div>
-</li>
-</ul></div>
-</div>
-<div class="sect2">
-<h3 id="_language">12.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_f20.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 operating system. If this
-is for some reason undesirable one 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. <strong>This particular
-preference requires a restart of <em>Subsurface</em> to take effect</strong>.</p></div>
-</div>
-<div class="sect2">
-<h3 id="_network">12.5. Network</h3>
-<div class="paragraph"><p>This panel facilitates communication between <em>Subsurface</em> and data sources
-on the Internet. This is important, for instance, when <em>Subsurface</em> needs
-to communicate with Internet services such as Cloud storage or the
-<a href="#S_Companion"><em>Subsurface Companion app</em></a>. 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.</p></div>
-<div class="imageblock" style="text-align:center;">
-<div class="content">
-<img src="images/Pref5_f20.jpg" alt="FIGURE: Preferences Network page" />
-</div>
-</div>
-<div class="paragraph"><p>This dialogue has three sections:</p></div>
-<div class="ulist"><ul>
-<li>
-<p>
-<em>Proxy type</em>:
-If a proxy server is used for Internet access, 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 are required so that <em>Subsurface</em> can automatically pass
-through the proxy server to access the Internet. This information is usually obtained
-from one’s ISP.
-</p>
-</li>
-<li>
-<p>
-<em>Subsurface cloud storage</em>: To store one’s dive log in the cloud, a valid email address
- and password are required. This allows <em>Subsurface</em> to email security information
- regarding cloud storage to a user, and to set up the cloud storage appropriately.
- Two additional options are given:
-</p>
-<div class="ulist"><ul>
-<li>
-<p>
-<em>Sync to cloud in the background</em>: This option allows saving of dive information to the cloud storage
- while the user performs other tasks within <em>Subsurface</em>.
-</p>
-</li>
-<li>
-<p>
-<em>Save password locally</em>: This allows local storage of the cloud storage password. Note that this
- information is saved in raw text form, not encoded in any way.
-</p>
-</li>
-</ul></div>
-</li>
-<li>
-<p>
-<em>Subsurface web service</em>: 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>
-</ul></div>
-</div>
-<div class="sect2">
-<h3 id="S_Facebook">12.6. Accès Facebook</h3>
-<div class="paragraph"><p>Ce panneau vous permet de vous connecter à votre compte Facebook pour
-transférer des informations de Subsurface vers Facebook.</p></div>
-<div class="imageblock" style="text-align:center;">
-<div class="content">
-<img src="images/Pref6_f20.jpg" alt="FIGURE: Facebook login panel" />
-</div>
-</div>
-<div class="paragraph"><p>Si un identifiant Facebook et un mot de passe valides ont été fournis, une
-connexion vers Facebook est créée. Cette connexion est fermée lorsque
-Subsurface est fermé. Pour le moment, la case à cocher nommée "Conserver ma
-connexion à Subsurface", sur l'écran de connexion, n’a aucun
-effet. Reportez-vous à la section <a href="#S_facebook">Export des profils de
-plongée vers Facebook</a> pour plus d’informations.</p></div>
-</div>
-<div class="sect2">
-<h3 id="_georeference">12.7. Georeference</h3>
-<div class="paragraph"><p><em>Subsurface</em> provides a geo-lookup service (that is, given the coordinates
-of a dive site (derived from a click on the <strong>Dive Map panel</strong> at the bottom
-right of the <em>Subsurface</em> window, or from a GPS instrument or from the
-<em>Subsurface</em> Companion app), a lookup on the Internet is performed to find
-the name of the closest known location. Obviously this function only works
-if <em>Subsurface</em> has an Internet connection. The preference of the dive site
-name can be configured, e.g. <em>Country/State/City</em> or <em>City/State/Country</em>
-(see image below).</p></div>
-<div class="imageblock" style="text-align:center;">
-<div class="content">
-<img src="images/Pref7_f20.jpg" alt="FIGURE: Facebook login panel" />
-</div>
-</div>
-</div>
-</div>
-</div>
-<div class="sect1">
-<h2 id="S_DivePlanner">13. 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 → 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="ulist"><ul>
-<li>
-<p>
-The user is conversant with dive planning and has the necessary training to
- perform dive planning.
-</p>
-</li>
-<li>
-<p>
-The user plans dives within his/her certification limits.
-</p>
-</li>
-<li>
-<p>
-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.
-</p>
-</li>
-<li>
-<p>
-The safety of a dive plan depends heavily on the way in which the planner is
- used.
-</p>
-</li>
-<li>
-<p>
-The user is familiar with the user interface of <em>Subsurface</em>.
-</p>
-</li>
-<li>
-<p>
-A user who is not absolutely sure about any of the above requirements should
- not use this feature.
-</p>
-</li>
-</ul></div>
-</div></div>
-<div class="sect2">
-<h3 id="_the_em_subsurface_em_dive_planner_screen">13.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 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_f20.jpg" alt="FIGURE: Dive planner startup window" />
-</div>
-</div>
-</div>
-<div class="sect2">
-<h3 id="_open_circuit_dives">13.2. Open circuit dives</h3>
-<div class="ulist"><ul>
-<li>
-<p>
-Towards the centre bottom of the planner (circled in blue in the image
- above) is a dropbox with three options. Select the appropriate one of these:
-</p>
-<div class="ulist"><ul>
-<li>
-<p>
-Open Circuit (the default)
-</p>
-</li>
-<li>
-<p>
-CCR
-</p>
-</li>
-<li>
-<p>
-pSCR
-</p>
-</li>
-</ul></div>
-</li>
-<li>
-<p>
-Choose the Open Circuit option.
-</p>
-</li>
-<li>
-<p>
-In the top left-hand area of the planning screen, ensure that the constant
- dive parameters are appropriate. These are: Start date and time of the
- intended 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 a sea-level atmospheric pressure of 1.013 bar.
-</p>
-</li>
-<li>
-<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="#cylinder_definitions">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 cylinder is assumed to contain
- 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 right-hand of the dialogue.
-</p>
-</li>
-<li>
-<p>
-The profile of the planned dive can be created in two ways:
-</p>
-<div class="ulist"><ul>
-<li>
-<p>
-Drag the waypoints (the small white circles) on the existing dive profile in
- a way to represent the dive. Additional waypoints can be created by
- double-clicking the existing dive profile. Waypoints can be deleted by
- right-clicking a particular waypoint and selecting the <em>delete</em> item from
- the resulting context menu.
-</p>
-</li>
-<li>
-<p>
-The most efficient way to create a dive profile is to enter the appropriate
- values into the table marked <em>Dive planner points</em>. The first line of the
- table represents the duration and the final depth of the descent from the
- surface. Subsequent segments describe the bottom phase of the dive. The <em>CC
- set point</em> column is only relevant for closed circuit divers. The ascent is
- usually not specified because this is what the planner is supposed to
- calculate. Add additional segments to the profile by selecting the "+" icon
- at the top right hand of the table. Segments entered into the <em>Dive planner
- points</em> table automatically appear in the <strong>Dive Profile</strong> diagram.
-</p>
-</li>
-</ul></div>
-</li>
-</ul></div>
-<div class="sect3">
-<h4 id="_recreational_dives">13.2.1. Recreational dives</h4>
-<div class="paragraph"><p>Recreational mode is what comes closest to planning a dive based on the
-non-decompression limit (NDL). It computes the maximal time a diver can
-stay at the current depth without incurring any mandatory decompression
-stops and without using more than the existing gas (minus a reserve). The
-planner automatically takes into account the nitrogen load incurred in
-previous dives. But conventional dive tables are also used in a way that can
-take into account previous dives. Why use a dive planner for recreational
-dives? Using recreational dive tables, the maximum depth of a dive is taken
-into account. However, few dives are undertaken at a constant depth
-corresponding to the maximum depth (i.e. a "square" dive profile). This
-means that dive tables overestimate the nitrogen load incurred during
-previous dives. The <em>Subsurface</em> dive planner calculates nitrogen load
-according to the real dive profiles of all uploaded previous dives, in a
-similar way as dive computers calculate nitrogen load during a dive. This
-means that the diver gets <em>credit</em> in terms of nitrogen loading for not
-remaining at maximum depth during previous dives, enabling planning of a
-longer subsequent dive. For the planner to work it is therefore crucial to
-upload all previous dives onto <em>Subsurface</em> before performing dive planning.</p></div>
-<div class="paragraph"><p>To plan a dive, the appropriate settings need to be defined.</p></div>
-<div class="paragraph"><p>Ensure that the date and time is set to that of the intended dive. This
-allows calculation of the nitrogen load incurred during previous dives.</p></div>
-<div class="ulist"><ul>
-<li>
-<p>
-Immediately under the heading <em>Planning</em> are two checkboxes <em>Recreational</em>
- and <em>Safety Stop</em>. Check these two boxes.
-</p>
-</li>
-<li>
-<p>
-Then define the cylinder size, the gas mixture (air or % oxygen) and the
- starting cylinder pressure in the top left-hand section of the planner under
- <em>Available gases</em>.
-</p>
-</li>
-<li>
-<p>
-The planner calculates whether the specified cylinder contains enough
- air/gas to complete the planned dive. In order for this to be realistic,
- under <em>Gas options</em>, specify an appropriate surface air consumption (SAC)
- rate for <em>Bottom SAC</em>. Suitable values are between 15 l/min and 30 l/min,
- with novice divers or difficult dives requiring SAC rates closer to 30l/min.
-</p>
-</li>
-<li>
-<p>
-Define the amount of gas that the cylinder must have at the end of the
- bottom section of the dive just before ascent. A value of 50 bar is often
- used. The reason for this reserve gas is to provide for the possible need to
- bring one’s buddy to the surface using gas sharing. How much gas is used in
- sharing depends on the depth of the ascent. This can be a bit hard to
- estimate, so most agencies assume a fixed amount of gas, or actually of
- pressure e.g. 40 or 50 bar or 25% or 33% (rule of thirds). But <em>Subsurface</em>
- can do better because it knows about the ascent and that is why we add the
- amount of gas during the ascent (i.e. the "deco gas“). Subsurface still
- uses a fixed pressure „reserve“ but that is supposed to be for the
- additional gas used around the realisation that there is a problem and one’s
- pulse rate goes up when one starts to buddy breathe. This reserve amount is
- user configurable.
-</p>
-</li>
-<li>
-<p>
-Define the depth of the dive by dragging the waypoints (white dots) on the
- dive profile or (even better) defining the appropriate depths using the
- table under <em>Dive planner points</em> as desribed under the previous heading. If
- this is a multilevel dive, set the appropriate dive depths to represent the
- dive plan by adding waypoints to the dive profile or by adding appropriate
- dive planner points to the <em>Dive Planner Points</em> table. <em>Subsurface</em> will
- automatically extend the bottom section of the dive to the maximum duration
- within the no-decompression limits (NDL).
-</p>
-</li>
-<li>
-<p>
-The ascent speed can be changed. The default ascent speeds are those
- considered safe for recreational divers.
-</p>
-</li>
-</ul></div>
-<div class="paragraph"><p>The dive profile in the planner indicates the maximum dive time within
-no-deco limits using the Bühlmann ZH-L16 algorithm and the gas and depth
-settings specified as described above. The <em>Subsurface</em> planner allows rapid
-assessment of dive duration as a function of dive depth, given the nitrogen
-load incurred during previous dives. The dive plan includes estimates of the
-amount of air/gas used, depending on the cylinder settings specified under
-<em>Available gases</em>. If the initial cylinder pressure is set to 0, the dive
-duration shown is the true no-deco limit (NDL) without taking into account
-gas used during the dive. If the surface above the dive profile is RED it
-means that recreational dive limits are exceeded and either the dive
-duration or the dive depth needs to be reduced.</p></div>
-<div class="paragraph"><p>Below is an image of a dive plan for a recreational dive at 30
-metres. Although the no-deco limit (NDL) is 23 minutes, the duration of the
-dive is limited by the amount of air in the cylinder, reflected by the
-information in the text box at the bottom right of the panel that requires
-sufficient air for buddy-sharing during the ascent.</p></div>
-<div class="imageblock" style="text-align:center;">
-<div class="content">
-<img src="images/rec_diveplan.jpg" alt="FIGURE: A recreational dive plan: setup" />
-</div>
-</div>
-</div>
-<div class="sect3">
-<h4 id="_non_recreational_open_circuit_dives_including_decompression">13.2.2. Non-recreational open circuit dives, including decompression</h4>
-<div class="paragraph"><p>Non-recreational dive planning involves exceeding the no-deco limits and/or
-using multiple breathing gases. Such dives are planned 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 deco model (GFLow, GFHigh or Conservatism level) under the headings <em>Rates</em> and <em>Planning</em>
-to the bottom left of the planning screen. Two deco models are supported the Bühlmann model and the VPM-B
-model. Select one of the two models. When selecting the Bühlmann model, the gradient factors (GF_high and GF_low
-need to be specified. 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 values 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>.</p></div>
-<div class="paragraph"><p>If the VPM-B model is selected, the Conservatism_level needs to be specified
-on a scale of 0 (least conservative) to 4 (most conservative). This model
-tends to give deco stops at deeper levels than the Bühlmann model and often
-results in slightly shorter dive durations than the Bühlmann model. When
-selecting one of these models, keep in mind that they are NOT exact
-physiological models but only mathematical models that appear to work in
-practice.</p></div>
-<div class="paragraph"><p>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>
-<a href="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"><em>Deco
-for Divers</em>, by Mark Powell (2008). Aquapress</a> Southend-on-Sea, UK. ISBN 10:
-1-905492-07-3. Un excellent livre non technique qui traite à la fois des
-modèles de décompression Bühlmann et VPM-B.
-</p>
-</li>
-</ul></div>
-<div class="paragraph"><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 by a
-light grey line on the dive profile. 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></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 increased to 1.6 bar.</p></div>
-<div class="paragraph"><p><strong>c) Gas management</strong>: With open-circuit dives this is a primary consideration. One needs to keep within the limits of the amount of gas within the dive
-cylinder(s), allowing for an appropriate margin for a 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 15-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 calculates the total volume of gas used during the dive and issues 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 bue 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. It is NOT necessary to specify the ascent
-part of the dive since the planner calculates this, based on the settings
-that have been specified. 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 <em>Available Gases</em> table. 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_f20.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 top middle of the planner. The saved dive plan will
-appear in the <strong>Dive List</strong> panel of <em>Subsurface</em>.</p></div>
-<div class="paragraph"><p><strong>The dive plan details</strong></p></div>
-<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>Notes</em> section of the dive
-planner, immediately to the left of the <em>Dive Plan Details</em>. If a <em>Verbatim
-dive plan</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>
-<div class="sect2">
-<h3 id="_planning_pscr_dives">13.3. Planning pSCR dives</h3>
-<div class="paragraph"><p>To plan a dive using a passive semi-closed rebreather (pSCR), select <em>pSCR</em> rather than
-<em>Open circuit</em> in the dropdown list.
-The parameters of the pSCR dive can be set by selecting <em>File → Preferences → Graph</em>
-from the main menu, where the gas consumption calculation takes into account the pSCR dump
-ratio (default 10:1) as well as the metabolism rate. The calculation also takes the oxygen drop
-accross the mouthpiece of the rebreather into account. If the
-pO<sub>2</sub> drops below what is considered a save value, a warning appears in the <em>Dive plan
-details</em>. A typical pSCR configuration is with a single cylinder and one or more bail-out
-cylinders. Therefore the setup of the <em>Available gases</em> and the <em>Dive planner points</em> tables
-are very similar to that of a CCR dive plan, described below. However, no oxygen setpoints
-are specified for pSCR dives. Below is a dive plan for a pSCR dive. The dive is comparable
-to that of the CCR dive below, but note the longer ascent duration due to the lower oxygen
-in the loop due to the oxygen drop across the mouthpiece of the pSCR equipment.</p></div>
-<div class="imageblock" style="text-align:center;">
-<div class="content">
-<img src="images/Planner_pSCR1_f20.jpg" alt="FIGURE: Planning a pSCR dive: setup" />
-</div>
-</div>
-</div>
-<div class="sect2">
-<h3 id="_planning_ccr_dives">13.4. Planning CCR dives</h3>
-<div class="paragraph"><p>To plan a dive using a closed circuit rebreather, select the <em>CCR</em> option in
-the dropdown list, circled in blue in the image below.</p></div>
-<div class="paragraph"><p><strong>Available gases</strong>: In the <em>Available gases</em> table, enter the cylinder information for the
-diluent cylinder and for any bail-out cylinders. Do NOT enter the information for the oxygen
-cylinder since it is implied when the <em>CCR</em> dropdown selection is made.</p></div>
-<div class="paragraph"><p><strong>Entering setpoints</strong>: Specify a default setpoint in the Preferences tab, by selecting <em>File → Preferences → Graph</em> from
-the main menu. All user-entered segments in the <em>Dive planner points</em> table
-use the default setpoint value. Then, different setpoints can be specified for dive segments
-in the <em>Dive planner points</em> table. A zero setpoint
-means the diver bails out to open circuit mode for that segment. The decompression is always calculated
-using the setpoint of the last manually entered segment. So, to plan a bail out ascent for a
-CCR dive, add a one-minute dive segment to the end with a setpoint value of 0. The decompression
-algorithm does not switch deco-gases automatically while in CCR mode (i.e. when a positive setpoint is specified) but,
-of course, this is calculated for bail out ascents.</p></div>
-<div class="paragraph"><p>The dive profile for a CCR dive may look something like the image below.</p></div>
-<div class="imageblock" style="text-align:center;">
-<div class="content">
-<img src="images/Planner_CCR1_f20.jpg" alt="FIGURE: Planning a CCR dive: setup" />
-</div>
-</div>
-<div class="paragraph"><p>Note that, in the <em>Dive plan details</em>, the gas consumption for a CCR segment
-is not calculated, so gas consumptions of 0 litres are the norm.</p></div>
-</div>
-<div class="sect2">
-<h3 id="S_Replan">13.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 → 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">13.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">13.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>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 → 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="_description_des_éléments_du_menu_principal_de_subsurface">14. Description des éléments du menu principal de Subsurface</h2>
-<div class="sectionbody">
-<div class="paragraph"><p>Cette section décrit les fonctions et les opérations des éléments du menu
-principal de Subsurface. Plusieurs éléments ci-dessous sont des liens vers
-des sections de ce manuel traitant des opérations relatives.</p></div>
-<div class="sect2">
-<h3 id="_fichier">14.1. Fichier</h3>
-<div class="ulist"><ul>
-<li>
-<p>
-<a href="#S_NewLogbook"><em>Nouveau carnet de plongée</em></a> - Fermer le carnet de plongée
- actuellement ouvert et supprime toutes les informations de plongées.
-</p>
-</li>
-<li>
-<p>
-<em>Ouvrir un carnet de plongée</em> - Cela ouvre une fenêtre pour sélectionner le
- carnet de plongée à ouvrir.
-</p>
-</li>
-<li>
-<p>
-<em>Open cloud storage</em> - Open the dive log previously saved in
- <a href="#S_Cloud_storage"><em>Cloud storage</em></a>.
-</p>
-</li>
-<li>
-<p>
-<em>Sauvegarder</em> - Enregistrer le carnet de plongée qui est actuellement
- ouvert.
-</p>
-</li>
-<li>
-<p>
-<em>Save to cloud storage</em> - Save the current dive log to
- <a href="#S_Cloud_storage"><em>Cloud storage</em></a>.
-</p>
-</li>
-<li>
-<p>
-<em>Enregsitrer sous</em> - Enregistrer le carnet actuel sous un nom différent.
-</p>
-</li>
-<li>
-<p>
-<em>Fermer</em> - Fermer le carnet de plongée actuellement ouvert.
-</p>
-</li>
-<li>
-<p>
-<a href="#S_ExportLog"><em>Exporter</em></a> - Exporter le carnet de plongée actuellement
- ouvert (ou les plongées sélectionnées dans le carnet) vers un des nombreux
- formats.
-</p>
-</li>
-<li>
-<p>
-<a href="#S_PrintDivelog"><em>Imprimer</em></a> - Imprimer le carnet de plongée actuellement
- ouvert.
-</p>
-</li>
-<li>
-<p>
-<a href="#S_Preferences"><em>Préférences</em></a> - Définir les préférences de <em>Subsurface</em>.
-</p>
-</li>
-<li>
-<p>
-<a href="#S_FindMovedImages"><em>Find moved images</em></a> - If photos taken during dives
- have been moved to
- a different disk or directory, locate them and link them to the appropriate
- dives.
-</p>
-</li>
-<li>
-<p>
-<a href="#S_Configure"><em>Configurer l’ordinateur de plongée</em></a> - Modifier la
- configuration d’un ordinateur de plongée.
-</p>
-</li>
-<li>
-<p>
-<em>Quitter</em> - Quitter <em>Subsurface</em>.
-</p>
-</li>
-</ul></div>
-</div>
-<div class="sect2">
-<h3 id="_importer">14.2. Importer</h3>
-<div class="ulist"><ul>
-<li>
-<p>
-<a href="#S_ImportDiveComputer"><em>Importer depuis un l’ordinateur de plongée</em></a> -
- Importer des informations de plongées à partir de l’ordinateur de plongée.
-</p>
-</li>
-<li>
-<p>
-<a href="#Unified_import"><em>Importer des fichiers de log</em></a> - Importer des
- informations de plongées à partir d’un fichier d’un format compatible avec
- <em>Subsurface</em>.
-</p>
-</li>
-<li>
-<p>
-<a href="#S_Companion"><em>Importer les données GPS depis le service web Subsurface</em></a> -
- Charge les coordonnées GPS à partir de l’application mobile <em>Subsurface</em>
- (téléphones et tablettes).
-</p>
-</li>
-<li>
-<p>
-<a href="#S_ImportingDivelogsDe"><em>Importer depuis Divelogs.de</em></a> - Importer des
- informations de plongées à partir de <em>www.Divelogs.de</em>.
-</p>
-</li>
-</ul></div>
-</div>
-<div class="sect2">
-<h3 id="_journal_log">14.3. Journal (log)</h3>
-<div class="ulist"><ul>
-<li>
-<p>
-<a href="#S_EnterData"><em>Ajouter une plongée</em></a> - Ajouter manuellement une nouvelle
- plongée au panneau de la <strong>liste des plongées</strong>.
-</p>
-</li>
-<li>
-<p>
-<em>Edit dive</em> - Edit a dive of which the profile was entered by hande and not
- from a dive computer.
-</p>
-</li>
-<li>
-<p>
-<a href="#S_DivePlanner"><em>Planifier une plongée</em></a> - Cette fonctionnalité permet de
- planifier des plongées.
-</p>
-</li>
-<li>
-<p>
-<a href="#S_Replan"><em>Modifier la plongée dans le planificateur</em></a> - Modifier une
- plongée planifiée qui a été enregistrée dans la <strong>liste des plongées</strong>.
-</p>
-</li>
-<li>
-<p>
-<a href="#S_CopyComponents"><em>Copier les composants de la plongée</em></a> - En
- sélectionnant cette option, vous pouvez copier les informations de plusieurs
- champs d’un journal de plongée vers le presse-papier.
-</p>
-</li>
-<li>
-<p>
-<em>Coller les composants de la plongée</em> - Colle, dans les plongées
- sélectionnées dans la <strong>liste des plongées</strong>, les informations copiées au
- préalable avec l’option <em>Copier les composants de la plongée</em>.
-</p>
-</li>
-<li>
-<p>
-<a href="#S_Renumber"><em>Renuméroter</em></a> - Renuméroter les plongées sélectionnées dans
- le panneau de la <strong>liste des plongées</strong>.
-</p>
-</li>
-<li>
-<p>
-<a href="#S_Group"><em>Grouper automatiquement</em></a> - Grouper les plongées du panneau de
- <strong>liste des plongées</strong> dans des voyages de plongées.
-</p>
-</li>
-<li>
-<p>
-<a href="#S_DeviceNames"><em>Editer les noms des ordinateurs de plongée</em></a> - Modifier
- les noms des ordinateurs de plongée pour faciliter vos journaux (logs).
-</p>
-</li>
-<li>
-<p>
-<a href="#S_Filter"><em>Filtrer la liste des plongées</em></a> - Sélectionner seulement
- certaines plongées, à partir de tags ou de critères de plongées.
-</p>
-</li>
-</ul></div>
-</div>
-<div class="sect2">
-<h3 id="_vue">14.4. Vue</h3>
-<div class="ulist"><ul>
-<li>
-<p>
-<a href="#S_ViewPanels"><em>Tout</em></a> - Affiche les quatre panneaux principaux de
- <em>Subsurface</em> simultanément.
-</p>
-</li>
-<li>
-<p>
-<a href="#S_ViewPanels"><em>Liste des plongées</em></a> - Affiche uniquement le panneau de la
- <strong>liste des plongées</strong>.
-</p>
-</li>
-<li>
-<p>
-<a href="#S_ViewPanels"><em>Profil</em></a> - Affiche uniquement le panneau du <strong>profil de la
- plongée</strong>.
-</p>
-</li>
-<li>
-<p>
-<a href="#S_ViewPanels"><em>Info</em></a> - Affiche uniquement le panneau des <strong>notes</strong>.
-</p>
-</li>
-<li>
-<p>
-<a href="#S_ViewPanels"><em>Globe</em></a> - Affiche uniquement le panneau de la <strong>carte
- mondiale</strong>.
-</p>
-</li>
-<li>
-<p>
-<em>Statistiques annuelles</em> - Affiche par année le résumé des statistiques des
- plongées effectuées.
-</p>
-</li>
-<li>
-<p>
-<em>Prev DC</em> - If a single dive was logged from more than one dive computer,
- switch to data from
- ordinateur de plongée précédent.
-</p>
-</li>
-<li>
-<p>
-<em>Ordinateur suivant</em> - Passer à l’ordinateur de plongée suivant.
-</p>
-</li>
-<li>
-<p>
-<em>Plein écran</em> - Passer en mode plein écran.
-</p>
-</li>
-</ul></div>
-</div>
-<div class="sect2">
-<h3 id="_share_on">14.5. Share on</h3>
-<div class="ulist"><ul>
-<li>
-<p>
-<a href="#S_Facebook"><em>Facebook</em></a> - Partager la plongée sélectionnée sur votre
- Facebook.
-</p>
-</li>
-</ul></div>
-</div>
-<div class="sect2">
-<h3 id="_aide">14.6. Aide</h3>
-<div class="ulist"><ul>
-<li>
-<p>
-<em>À propos de Subsurface</em> - Affiche un panneau avec le numéro de version de
- <em>Subsurface</em> ainsi que les informations de licence.
-</p>
-</li>
-<li>
-<p>
-<em>Vérifier les mises à jour</em> - Vérifier si une nouvelle version de
- Subsurface est disponible sur le <a href="http://subsurface-divelog.org/">site web de
- <em>Subsurface</em> </a>.
-</p>
-</li>
-<li>
-<p>
-<a href="#S_UserSurvey"><em>Sondge utilisateur</em></a> - Aider à rendre <em>Subsurface</em> encore
- meilleur en répondant à notre sondage utilisateur ou en répondant à un autre
- sondage, si vos habitudes de plongées ont changées.
-</p>
-</li>
-<li>
-<p>
-<em>Manuel utilisateur</em> - Ouvre une fenêtre affichant ce manuel utilisateur.
-</p>
-</li>
-</ul></div>
-</div>
-</div>
-</div>
-<div class="sect1">
-<h2 id="_annexe_a_informations_spécifiques_au_système_d_8217_exploitation_utilisé_pour_importer_les_informations_de_plongées_depuis_un_ordinateur_de_plongée">15. ANNEXE A : informations spécifiques au système d’exploitation utilisé pour importer les informations de plongées depuis un ordinateur de plongée.</h2>
-<div class="sectionbody">
-<div class="sect2">
-<h3 id="_assurez_vous_que_les_pilotes_drivers_nécessaires_sont_installés">15.1. Assurez-vous que les pilotes (drivers) nécessaires sont installés</h3>
-<div class="admonitionblock">
-<table><tr>
-<td class="icon">
-<img src="images/icons/drivers.jpg" alt="Note" />
-</td>
-<td class="content">Le système d’exploitation de l’ordinateur nécessite les bons pilotes pour
-communiquer avec l’ordinateur de plongée de la façon utilisée par
-l’ordinateur de plongée (Bluetooth, USB, infra-rouge).</td>
-</tr></table>
-</div>
-<div class="ulist"><ul>
-<li>
-<p>
-Sous Linux, les utilisateurs doivent avoir le bon module noyau de chargé. La
- plupart des distributions Linux le font automatiquement, de telle sorte que
- l’utilisateur n’ait rien à faire de particulier. Cependant, certains
- protocoles de communication nécessitent des pilotes additionnels, plus
- particulièrement pour certaines technologies telles que l’infra-rouge.
-</p>
-</li>
-<li>
-<p>
-Sous Windows, le bon pilote devrait être téléchargé automatiquement la
- première fois que l’utilisateur branche son ordinateur de plongée sur le
- port USB de son ordinateur de bureau.
-</p>
-</li>
-</ul></div>
-<div class="paragraph"><p>Sous Mac, les utilisateurs peuvent parfois avoir besoin d’installer
-manuellement le bon pilote. Par exemple, pour le Mares Puck ou n’importe
-quel autre ordinateur de plongée utilisant une interface USB-série basé sur
-le composant Silicon Labs CP2101 ou similaire, le bon pilote est disponible
-sous <em>Mac_OSX_VCP_Driver.zip</em> sur le
-<a href="http://www.silabs.com/support/pages/document-library.aspx?p=Interface&f=USB%20Bridges&pn=CP2101">dépôt
-de documents et logiciels Silicon Labs</a>.</p></div>
-</div>
-<div class="sect2">
-<h3 id="S_HowFindDeviceName">15.2. Comment trouver le nom du périphérique branché sur USB et paramétrer les permissions en écriture</h3>
-<div class="admonitionblock">
-<table><tr>
-<td class="icon">
-<img src="images/icons/usb.jpg" alt="Note" />
-</td>
-<td class="content">Lorsqu’un utilisateur connecte un ordinateur de plongée en utilisant l’USB,
-généralement <em>Subsurface</em> proposera soit une liste déroulante contenant le
-bon nom (ou le point de montage pour un Uemis Zurich) ou la liste sera
-désactivée si aucun nom de périphérique n’est nécessaire. Dans les rares cas
-où cela ne fonctionnerait pas, voici quelques suggestions pour trouver le
-nom de votre périphérique ;</td>
-</tr></table>
-</div>
-<div class="paragraph"><div class="title">Sur Windows :</div><p>Essayez simplement COM1, COM2, etc. La liste déroulante devrait contenir
-tous les périphériques COM connectés.</p></div>
-<div class="paragraph"><div class="title">Sur MacOS :</div><p>La liste déroulante devrait contenir tous les ordinateurs de plongée
-connectés.</p></div>
-<div class="paragraph"><div class="title">Sur Linux :</div><p>Il existe un moyen sûr de trouver le port :</p></div>
-<div class="ulist"><ul>
-<li>
-<p>
-Déconnecter le cable USB de l’ordinateur de plongée
-</p>
-</li>
-<li>
-<p>
-Ouvrir un terminal
-</p>
-</li>
-<li>
-<p>
-Taper la commande <em>dmesg</em> et appuyer sur la touche Entrer
-</p>
-</li>
-<li>
-<p>
-Connecter le cable USB de l’ordinateur de plongée
-</p>
-</li>
-<li>
-<p>
-Taper la commande <em>dmesg</em> et appuyer sur la touche Entrer
-</p>
-</li>
-</ul></div>
-<div class="paragraph"><p>Un message similaire à celui-ci devrait apparaitre :</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>La troisième ligne en partant du bas montre que l’adaptateur FTDI USB est
-détecté et connecté sur <code>ttyUSB3</code>. Cette information peut à présent être
-utilisée pour les paramètres d’importation en tant que <code>/dev/ttyUSB3</code> pour
-que Subsurface utilise le bon port USB.</p></div>
-<div class="paragraph"><p>S’assurer que l’utilisateur possède les droits d'écriture sur le port série
-USB :</p></div>
-<div class="paragraph"><p>Sur les systèmes similaires à Unix, les ports USB ne peuvent être accédés
-que par des utilisateurs membres du groupe <code>dialout</code>. Si vous n'êtes pas
-root, vous n'êtes peut-être pas membre de ce groupe et ne pouvez donc pas
-utiliser le port USB. Si votre nom d’utilisateur est <em>johnB</em> :</p></div>
-<div class="paragraph"><p>En tant que root, tapez : usermod -a -G dialout johnB+ (utilisateurs
-d’Ubuntu : <code>sudo usermod -a -G dialout johnB</code>) Cela ajoute johnB au groupe
-<code>dialout</code>.
-Tapez : <code>id johnB</code> Cela liste tous les groupes auquel johnB appartient et
-vérifiez que
-l’appartenance au groupe est bien effectif. Le groupe <code>dialout</code> devrait
-être listé
-parmi les différents IDs.
-Sous certaines circonstances, les modifications ne prennent effet qu’après une déconnexionpuis reconnexion sur l’ordinateur (sous Ubuntu, par exemple).
-Avec le bon nom de périphérique (par exemple <code>dev/ttyUSB3</code>) et avec un accès
-en écriture au port USB, l’ordinateur de plongée devrait se connecter et
-vous devriez pouvoir importer vos plongées.</p></div>
-</div>
-<div class="sect2">
-<h3 id="S_HowFindBluetoothDeviceName">15.3. Manually 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, Petrel and Nerd 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’s user
-guide. When using a Shearwater Predator/Petrel/Nerd, select <em>Dive Log →
-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="sect3">
-<h4 id="_sur_windows_2">15.3.1. Sur Windows :</h4>
-<div class="paragraph"><p>Bluetooth is most likely already enabled. For pairing with the dive computer
-choose <em>Control Panel → Bluetooth Devices → Add Wireless Device</em>. This
-should bring up a dialog showing your dive computer (which should be in
-Bluetooth mode) and allowing pairing. Right click on it and choose
-<em>Properties→ 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>
-<div class="sect3">
-<h4 id="_sur_macos">15.3.2. Sur MacOS :</h4>
-<div class="paragraph"><p>Click on the Bluetooth symbol in the menu bar and select <em>Set up Bluetooth
-Device…</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>
-<div class="sect3">
-<h4 id="_sur_linux">15.3.3. Sur Linux</h4>
-<div class="paragraph"><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 on the right
-of the toolbar at the top of the screen. Users have reported difficulties
-with some Bluetooth controllers. If you have an onboard controller, try
-that first. It is simplest if you remove any USB Bluetooth dongles. If you
-have a USB dongle that came with your dive computer, try that before any
-others.</p></div>
-<div class="paragraph"><p>Setting up a connection to download dives from your Bluetooth-enabled
-device, such as the <em>Shearwater Petrel</em>, is not yet an automated process and
-will generally require the command prompt. It is essentially a three step
-process.</p></div>
-<div class="ulist"><ul>
-<li>
-<p>
-Enable the Bluetooth controller and pair your dive computer
-</p>
-</li>
-<li>
-<p>
-Establish an RFCOMM connection
-</p>
-</li>
-<li>
-<p>
-Download the dives with Subsurface
-</p>
-</li>
-</ul></div>
-<div class="paragraph"><p>Ensure the dive computer is in upload mode. On the <em>Shearwater Petrel</em>,
-<em>Petrel 2</em> and <em>Nerd</em> cycle through the menu, select <em>Dive Log</em>, then
-<em>Upload Log</em>. The display will read <em>Initializing</em>, then <em>Wait PC 3:00</em> and
-will countdown. Once the connection is established, the display reads <em>Wait
-CMD …</em> and the countdown continues. When downloading the dive from
-Subsurface, the display reads <em>Sending</em> then <em>Sent Dive</em>.</p></div>
-<div class="paragraph"><p>To establish the connection, establish root access through <code>sudo</code> or <code>su</code>.
-The correct permission is required to download the dives in the computer. On
-most Linux systems this means becoming a member of the dialout group (This
-is identical as for many dive computers using a Linux USB port, described in
-the previous section). On the command terminal, enter:</p></div>
-<div class="paragraph"><p><code>sudo usermod -a -G dialout username</code></p></div>
-<div class="paragraph"><p>Then log out and log in for the change to take effect.</p></div>
-<div class="sect4">
-<h5 id="_enabling_the_bluetooth_controller_and_pairing_your_dive_computer">Enabling the Bluetooth controller and pairing your dive computer</h5>
-<div class="paragraph"><p>Attempt to set up the Bluetooth controller and pair your dive computer using
-the graphical environment of the operating system. After setting the dive
-computer to upload mode, click the Bluetooth icon in the system tray and
-select <em>Add new device</em>. The dive computer should appear. If asked for a
-password, enter 0000. Write down or copy the MAC address of your dive
-computer - this needed later and should be in the form 00:11:22:33:44:55.</p></div>
-<div class="paragraph"><p>If the graphical method didn’t work, pair the device from the command
-line. Open a terminal and use <code>hciconfig</code> to check the Bluetooth controller
-status</p></div>
-<div class="literalblock">
-<div class="content">
-<pre><code>$ hciconfig
-hci0: Type: BR/EDR Bus: USB
- BD Address: 01:23:45:67:89:AB ACL MTU: 310:10 SCO MTU: 64:8
- *DOWN*
- RX bytes:504 acl:0 sco:0 events:22 errors:0
- TX bytes:92 acl:0 sco:0 commands:21 errors:0</code></pre>
-</div></div>
-<div class="paragraph"><p>This indicates a Bluetooth controller with MAC address 01:23:45:67:89:AB,
-connected as hci0. Its status is <em>DOWN</em>, i.e. not powered. Additional
-controllers will appear as hci1, etc. If there is not a Bluetooth dongle
-plugged in upon booting the computer, hci0 is probably the onboard. Now
-power on the controller and enable authentication:</p></div>
-<div class="literalblock">
-<div class="content">
-<pre><code>sudo hciconfig hci0 up auth+ (enter password when prompted)
-hciconfig
-hci0: Type: BR/EDR Bus: USB
- BD Address: 01:23:45:67:89:AB ACL MTU: 310:10 SCO MTU: 64:8
- *UP RUNNING PSCAN AUTH*
- RX bytes:1026 acl:0 sco:0 events:47 errors:0
- TX bytes:449 acl:0 sco:0 commands:46 errors:0</code></pre>
-</div></div>
-<div class="paragraph"><p>Check that the status now includes <code><em>UP</em>, <em>RUNNING</em> AND <em>AUTH</em></code>.</p></div>
-<div class="paragraph"><p>If there are multiple controllers running, it’s easiest to off the unused
-controller(s). For example, for <code>hci1</code>:</p></div>
-<div class="literalblock">
-<div class="content">
-<pre><code>sudo hciconfig hci1 down</code></pre>
-</div></div>
-<div class="paragraph"><p>Next step is to <em>trust</em> and <em>pair</em> the dive computer. On distros with Bluez
-5, such as Fedora 22, one can use a tool called <code>blutootctl</code>, which will
-bring up its own command prompt.</p></div>
-<div class="literalblock">
-<div class="content">
-<pre><code>bluetoothctl
-[NEW] Controller 01:23:45:67:89:AB localhost.localdomain [default]
-[bluetooth]# agent on
-Agent registered
-[bluetooth]# default-agent
-Default agent request successful
-[bluetooth]# scan on <----now set your dive computer to upload mode
-Discovery started
-[CHG] Controller 01:23:45:67:89:AB Discovering: yes
-[NEW] Device 00:11:22:33:44:55 Petrel
-[bluetooth]# trust 00:11:22:33:44:55 <----you can use the tab key to autocomplete the MAC address
-[CHG] Device 00:11:22:33:44:55 Trusted: yes
-Changing 00:11:22:33:44:55 trust succeeded
-[bluetooth]# pair 00:11:22:33:44:55
-Attempting to pair with 00:11:22:33:44:55
-[CHG] Device 00:11:22:33:44:55 Connected: yes
-[CHG] Device 00:11:22:33:44:55 UUIDs: 00001101-0000-1000-8000-0089abc12345
-[CHG] Device 00:11:22:33:44:55 Paired: yes
-Pairing successful
-[CHG] Device 00:11:22:33:44:55 Connected: no</code></pre>
-</div></div>
-<div class="paragraph"><p>If asked for a password, enter 0000. It’s ok if the last line says
-<em>Connected: no</em>. The important part is the line above, <code>Pairing successful</code>.</p></div>
-<div class="paragraph"><p>If the system has Bluez version 4 (e.g. Ubuntu 12.04 through to 15.04),
-there is probably not a <code>bluetoothctl</code>, but a script called
-<code>bluez-simple-agent</code> or just <code>simple-agent</code>.</p></div>
-<div class="literalblock">
-<div class="content">
-<pre><code>hcitool -i hci0 scanning
-Scanning ...
- 00:11:22:33:44:55 Petrel
- bluez-simple-agent hci0 00:11:22:33:44:55</code></pre>
-</div></div>
-<div class="paragraph"><p>Once ther dive computer is pired, set up the RFCOMM connection</p></div>
-</div>
-<div class="sect4">
-<h5 id="_establishing_the_rfcomm_connection">Establishing the RFCOMM connection</h5>
-<div class="paragraph"><p>The command to establish an RFCOMM connection is:</p></div>
-<div class="paragraph"><p><code>sudo rfcomm -i <controller> connect <dev> <bdaddr> [channel]</code></p></div>
-<div class="ulist"><ul>
-<li>
-<p>
-<code><controller></code> is the Bluetooth controller, <code>hci0</code>.
-</p>
-</li>
-<li>
-<p>
-<code><dev></code> is the RFCOMM device file, <code>rfcomm0</code>
-</p>
-</li>
-<li>
-<p>
-<code><bdaddr></code> is the dive computer’s MAC address, <code>00:11:22:33:44:55</code>
-</p>
-</li>
-<li>
-<p>
-<code>[channel]</code> is the dive computer’s Bluetooth channel we need to connect to.
-</p>
-</li>
-</ul></div>
-<div class="paragraph"><p>If one omits it, channel 1 is assumed. Based on a limited number of user
-reports, the appropriate channel for the dive computer is probably:</p></div>
-<div class="ulist"><ul>
-<li>
-<p>
-<em>Shearwater Petrel 1</em>: channel 1
-</p>
-</li>
-<li>
-<p>
-<em>Shearwater Petrel 2</em>: channel 5
-</p>
-</li>
-<li>
-<p>
-<em>Shearwater Nerd</em>: channel 5
-</p>
-</li>
-<li>
-<p>
-<em>Heinrichs-Weikamp OSTC Sport</em>: channel 1
-</p>
-</li>
-</ul></div>
-<div class="paragraph"><p>E.g. to connect a <em>Shearwater Petrel 2</em>, set the dive computer to upload
-mode and enter:</p></div>
-<div class="literalblock">
-<div class="content">
-<pre><code>sudo rfcomm -i hci0 connect rfcomm0 00:11:22:33:44:55 5 (enter a password, probably 0000, when prompted)</code></pre>
-</div></div>
-<div class="paragraph"><p>This gives the response:</p></div>
-<div class="literalblock">
-<div class="content">
-<pre><code>Connected /dev/rfcomm0 to 00:11:22:33:44:55 on channel 5
-Press CTRL-C for hangup</code></pre>
-</div></div>
-<div class="paragraph"><p>To connect a _Shearwater Petrel 1+ or + HW OSTC Sport+, set the dive
-computer to upload mode and enter:</p></div>
-<div class="literalblock">
-<div class="content">
-<pre><code>sudo rfcomm -i hci0 connect rfcomm0 00:11:22:33:44:55 (enter a password, probably 0000, when prompted)
-Connected /dev/rfcomm0 to 00:11:22:33:44:55 on channel 1
-Press CTRL-C for hangup</code></pre>
-</div></div>
-<div class="paragraph"><p>If the specific channel the dive computer needs is not known, or the channel
-in the list above doesn’t work, the command <code>sdptool records</code> should help
-determine the appropriate channel. The output below is for a <em>Shearwater
-Petrel 2</em>.</p></div>
-<div class="literalblock">
-<div class="content">
-<pre><code>sdptool -i hci0 records 00:11:22:33:44:55
-Service Name: Serial Port
-Service RecHandle: 0x10000
-Service Class ID List:
- "Serial Port" (0x1101)
- Protocol Descriptor List:
- "L2CAP" (0x0100)
- "RFCOMM" (0x0003)
- Channel: 5</code></pre>
-</div></div>
-<div class="paragraph"><p>For a Bluetooth dive computer not in the list above, or if the channel
-listed is not correct, please let the Subsurface developers know on the user
-forum or the developer mailing list <em>subsurface@subsurface-divelog.org</em>.</p></div>
-</div>
-<div class="sect4">
-<h5 id="_download_the_dives_with_subsurface">Download the dives with Subsurface</h5>
-<div class="paragraph"><p>After establishing the RFCOMM connection and while the dive computer’s
-upload mode countdown is still running, go to_Subsurface_, select
-<em>Import→Import from dive computer</em> and enter appropriate Vendor
-(e.g. <em>Shearwater</em>), Dive Computer (<em>Petrel</em>), Device or Mount Point
-(<em>/dev/rfcomm0</em>) and click <em>Download</em>.</p></div>
-</div>
-</div>
-</div>
-</div>
-</div>
-<div class="sect1">
-<h2 id="_appendix_b_dive_computer_specific_information_for_importing_dive_information">16. APPENDIX B: Dive Computer specific information for importing dive data.</h2>
-<div class="sectionbody">
-<div class="sect2">
-<h3 id="S_ImportUemis">16.1. Importing from 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/<your_username>/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">16.2. Importing from 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>.
-Windows-based IrDA drivers for the Uwatec can also be downloaded from the
-ScubaPro web site, drivers being located on the download page for the
-ScubaPro SmartTrak software.</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">16.3. Importing 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’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="S_ImportingXDeep">16.4. Importing from xDEEP BLACK</h3>
-<div class="admonitionblock">
-<table><tr>
-<td class="icon">
-<img src="images/icons/HW_xdeepblack.jpg" alt="Note" />
-</td>
-<td class="content">Each dive has to be individually saved as UDDF file using "Export UDDF"
-option in BLACK’s logbook menu. When mounted as a USB drive UDDF files are
-available in LOGBOOK directory. Note: The xDEEP BLACK saves NDL time but
-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 xDEEP
-BLACK.</td>
-</tr></table>
-</div>
-</div>
-<div class="sect2">
-<h3 id="_importing_from_shearwater_predator_petrel_nerd_using_bluetooth">16.5. Importing from Shearwater Predator/Petrel/Nerd using Bluetooth</h3>
-<div class="admonitionblock">
-<table><tr>
-<td class="icon">
-<img src="images/icons/predator.jpg" alt="Note" />
-</td>
-<td class="content">Specific instructions for downloading dives using Bluetooth are given in the
-section above, <a href="#S_Bluetooth"><em>Connecting Subsurface to a Bluetooth-enabled dive computer</em></a>.</td>
-</tr></table>
-</div>
-</div>
-<div class="sect2">
-<h3 id="S_PoseidonMkVI">16.6. Importing from 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="ulist"><ul>
-<li>
-<p>
-Setup configuration for the dive and key dive parameters (file with a .txt
- extension)
-</p>
-</li>
-<li>
-<p>
-Dive log details (file with a .csv extension)
-</p>
-</li>
-<li>
-<p>
-Redbook format dive log (file with .cvsr extension). This is a compressed
- version of the dive log using a proprietary format.
-</p>
-</li>
-</ul></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_from_apd_inspiration_evolution_ccr">16.7. Importing from APD Inspiration/Evolution 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>
-Download the dive using <em>AP Communicator</em>.
-</p>
-</li>
-<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>
-With 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) or TextWrangler (Mac).
-</p>
-</li>
-<li>
-<p>
-Copy the contents of the clipboard into the text editor and save the text
- file with a filename extension of <em>.apd</em>
-</p>
-</li>
-<li>
-<p>
-Within <em>Subsurface</em>, select <em>Import → 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 (labled
- <em>Filter:</em>), select "APD log viewer".
-</p>
-</li>
-<li>
-<p>
-On the list of file names select the <em>.apd</em> file that has been created
- above. An import dialogue opens indicating the default settings for the data
- in the <em>.apd</em> file. If any changes are required, do this as for
- <a href="#S_ImportingCSVDives">CSV imports</a>.
-</p>
-</li>
-</ul></div>
-<div class="imageblock" style="text-align:center;">
-<div class="content">
-<img src="images/APD_CSVimportF22.jpg" alt="Figure: APD log viewer import" />
-</div>
-</div>
-<div class="ulist"><ul>
-<li>
-<p>
-The top left hand dropdown box in the import panel allows one to select the
- APD dive computer for which the dive log needs to be imported. The default
- it is DC1, <em>i.e.</em> the first of the two dive computers the APD uses. It is
- possible to sequentially import the data for both dive computers by first
- importing CD1 and then DC2.(<strong>Hint</strong>: The logs for the two dive computers are
- viewed by selecting <em>View → Next DC</em> from the Main Menu after the uploading
- has been completed)
-</p>
-</li>
-<li>
-<p>
-Click the <em>Ok</em> button at the bottom of the import panel.
-</p>
-</li>
-</ul></div>
-<div class="paragraph"><p>The APD dive log will appear within <em>Subsurface</em>. The dive
-computer-generated ceiling generated by the Inspiration can be viewed by
-selecting the appropriate button on the left of the <strong>Dive Profile</strong>. Cylinder
-pressure data are not logged by the APD equipment but can be manually
-entered in the <em>Equipment</em> Tab.</p></div>
-</div>
-</div>
-</div>
-<div class="sect1">
-<h2 id="_appendix_c_exporting_dive_log_information_from_external_dive_log_software">17. 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="olist arabic"><ol class="arabic">
-<li>
-<p>
-Export the foreign dive log data to format that is accessible from
- <em>Subsurface</em>.
-</p>
-</li>
-<li>
-<p>
-Import the accessible dive log data into <em>Subsurface</em>.
-</p>
-</li>
-</ol></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">17.1. Exporting 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.
-</p>
-</li>
-<li>
-<p>
-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
-</p>
-</li>
-<li>
-<p>
-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 → 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 → 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’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_atomic_logbook">17.2. Exporting from Atomic Logbook</h3>
-<div class="admonitionblock" id="Atomic_Export">
-<table><tr>
-<td class="icon">
-<img src="images/icons/atomiclogo.jpg" alt="Note" />
-</td>
-<td class="content">Atomic Logbook is a Windows software by Atomic Aquatics. It allows
-downloading of dive information from Cobalt and Cobalt 2 dive computers.
-The divelog is kept in a SQLite database at
-C:\ProgramData\AtomicsAquatics\Cobalt-Logbook\Cobalt.db. This file can be
-directly imported to Subsurface.</td>
-</tr></table>
-</div>
-</div>
-<div class="sect2">
-<h3 id="_exporting_from_mares_dive_organiser_v2_1">17.3. 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="olist arabic"><ol class="arabic">
-<li>
-<p>
-Within Dive Organiser, select <em>Database → Backup</em> from the main menu and
- back up the database to the desk top. This creates a zipped file
- DiveOrganiserxxxxx.dbf.
-</p>
-</li>
-<li>
-<p>
-Rename the file to DiveOrganiserxxxxx.zip. Inside the zipped directory is a
- file <em>DiveOrganiser.sdf</em>.
-</p>
-</li>
-<li>
-<p>
-Extract the <em>.sdf</em> file from the zipped folder to your Desktop.
-</p>
-</li>
-<li>
-<p>
-The password for accessing the .zip file is <em>mares</em>.
-</p>
-</li>
-</ol></div>
-</div>
-<div class="sect2">
-<h3 id="S_ImportingDivingLog">17.4. Exporting from <strong>DivingLog 5.0 and 6.0</strong></h3>
-<div class="admonitionblock">
-<table><tr>
-<td class="icon">
-<img src="images/icons/divingloglogo.jpg" alt="Note" />
-</td>
-<td class="content">The best way to bring your logs from DivingLog to Subsurface is to convert
-the whole database. This is because other export formats do not include all
-the details, and we would lack e.g. gas switches and information of what
-units are used. With database import, all this information is included and
-readily available for us.</td>
-</tr></table>
-</div>
-<div class="paragraph"><p>To transfer all files from DivingLog to Subsurface, do the following:</p></div>
-<div class="olist arabic"><ol class="arabic">
-<li>
-<p>
-In DivingLog open the <em>File → Export → SQLite</em> menu
-</p>
-</li>
-<li>
-<p>
-Select <em>Settings</em> button
-</p>
-</li>
-<li>
-<p>
-Set the <em>RTF2Plaintext</em> to <em>true</em>
-</p>
-</li>
-<li>
-<p>
-Close the Settings dialog
-</p>
-</li>
-<li>
-<p>
-Click <em>Export</em> button and select the filename
-</p>
-</li>
-</ol></div>
-<div class="paragraph"><p>Once this is done, open the saved database file with Subsurface and the
-dives are automatically converted to our own format. Last step to do is save
-the log file in Subsurface.</p></div>
-</div>
-</div>
-</div>
-<div class="sect1">
-<h2 id="_annexe_d_exporter_un_tableur_vers_le_format_csv">18. ANNEXE D : Exporter un tableur vers le format CSV</h2>
-<div class="sectionbody">
-<div class="paragraph" id="S_Appendix_D"><p>De nombreux plongeurs conservent un carnet de plongée sous forme de fichier
-numérique, souvent un tableur avec différents champs et informations. Ces
-données peuvent facilement être importées dans <em>Subsurface</em> après que le
-tableur a été converti en fichier CSV. Cette section explique la procedure
-pour convertir un carnet de plongée enregistrée sous forme de tableur vers
-un fichier CSV qui pourra ensuite être importé dans <em>Subsurface</em>. Créer un
-fichier CSV est une tache simple malgré que la procédure soit différente
-selon le tableur utilisé.</p></div>
-<div class="paragraph"><p>La première étape est d’organiser les données de plongées dans le tableur
-pour que la première ligne contienne le nom (ou le titre) de chaque colonne
-et que les informations de chaque plongée soient contenues sur une seule
-ligne. <em>Subsurface</em> supporte de nombreux éléments (Dive #, Date, Time,
-Duration, Location, GPS, Max Depth, Mean Depth, Buddy, Notes, Weight et
-Tags). L’utilisateur peut organiser les données de plongées selon quelques
-règles simples :</p></div>
-<div class="olist arabic"><ol class="arabic">
-<li>
-<p>
-Date : utiliser un des formats suivants : aaaa-mm-jj, jj.mm.aaaa, mm/jj/aaaa
-</p>
-</li>
-<li>
-<p>
-Durée : le format est minutes:secondes.
-</p>
-</li>
-<li>
-<p>
-Système d’unité : un seul système d’unité doit être utilisé (pas de mélange
- entre les unités impériales et métriques)
-</p>
-</li>
-<li>
-<p>
-Étiquettes et équipiers : les valeurs doivent être séparées par des
- virgules.
-</p>
-</li>
-<li>
-<p>
-Position GPS : vous devez utiliser les degrés décimaux, par exemple :
- 30.22496 30.821798
-</p>
-</li>
-</ol></div>
-<div class="sect2">
-<h3 id="_em_libreoffice_calc_em_et_em_openoffice_calc_em">18.1. <em>LibreOffice Calc</em> et <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 →
-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_ImportingCSVDives">Importing CSV dives</a>.</p></div>
-</div>
-<div class="sect2">
-<h3 id="_microsoft_em_excel_em">18.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.
-</p>
-</li>
-<li>
-<p>
-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_ImportingCSVDives">Importing CSV dives</a>.</p></div>
-</div>
-</div>
-</div>
-<div class="sect1">
-<h2 id="S_APPENDIX_E">19. ANNEXE E : Créer un modèle d’impression personnalisé</h2>
-<div class="sectionbody">
-<div class="paragraph"><p><em>Subsurface</em> provides a mechanism to create or modify templates for printing
-dive logs in order to produce customised printouts of dive logs. Templates,
-written in HTML as well as a simple Grantlee instruction set, are rendered
-to the print device by <em>Subsurface</em>.</p></div>
-<div class="paragraph"><p>Templates are accessed using the print dialogue (see image <strong>B</strong> below).</p></div>
-<div class="imageblock" style="text-align:center;">
-<div class="content">
-<img src="images/Print1_f22.jpg" alt="FIGURE: Print dialogue" />
-</div>
-</div>
-<div class="paragraph"><p>The buttons under the <em>Template</em> dropdown box allows one to <em>Edit</em>,
-<em>Delete</em>, <em>Import</em> and to <em>Export</em> templates (see image <strong>A</strong> above). New or
-modified templates are stored as HTML files in the same directory as the
-dive log being processed. In order to create or modify a template, select
-one of the templates from the template dropdown list in the print dialogue
-(see image <strong>B</strong> above). Choose an existing template that resembles the final
-desired printout. Then select <em>Edit</em>.</p></div>
-<div class="paragraph"><p>The Edit Panel comprises three tabs:</p></div>
-<div class="imageblock" style="text-align:center;">
-<div class="content">
-<img src="images/Template1_f22.jpg" alt="FIGURE: template edit dialogue" />
-</div>
-</div>
-<div class="paragraph"><p>1) The <em>Style</em> tab (image <strong>A</strong> above) controls the font, line spacing and colour
- template used for printing the dive log. The style attributes are
- editable. Choose one of the four colour palets used for colour printing.</p></div>
-<div class="paragraph"><p>2) The <em>Colors</em> tab (image <strong>B</strong> above) allows editing the colours used for
- printing the dive log. The colours are highly customisable: the <em>Edit</em>
- buttons in the <em>Colors</em> tab allows choosing abritrary colours for different
- components of the dive log printout.</p></div>
-<div class="paragraph"><p>3) The <em>Template</em> tab of the Edit Panel (see image below) allows creating a
- template using HTML as well as a few Grantlee programming
- primitives. Grantlee provides the ability to create and format HTML code in
- a highly simple but efficient way (see below). The HTML of the template can
- be edited and saved. The saved template is stored in the same directory as
- the dive being processed. By default, a <em>Custom</em> template is a skeleton with
- no specific print instructions. The informastion being printed needs to be
- specified and formatted in the by replacing the section marked with: "<!--
- Template must be filled -→". Writing HTML code with Grantlee instructions
- allows unlimited freedom in determining what is printed an in which way it
- should be rendered.</p></div>
-<div class="imageblock" style="text-align:center;">
-<div class="content">
-<img src="images/Template2_f22.jpg" alt="FIGURE:Template tab" />
-</div>
-</div>
-<div class="paragraph"><p>One can adapt any of the existing templates and save it to the dive log
-directory. The standard templates (e.g. One dive, Six dives, Table) can be
-modified in this way. After completing the edits, use the <em>Export</em> button in
-the print dialogue to save the new template using a new template name.</p></div>
-<div class="paragraph"><p>To write a custom template the following elements must exist so that the
-template will be correctly handled and rendered.</p></div>
-<div class="sect2">
-<h3 id="_main_dive_loop">19.1. Main dive loop</h3>
-<div class="paragraph"><p><em>Subsurface</em> exports a dive list called (<strong>dives</strong>) to the <em>Grantlee</em>
-backend. It is possible to iterate over the list as follows:</p></div>
-<div class="literalblock">
-<div class="title">template.html</div>
-<div class="content">
-<pre><code> {% for dive in dives %}
- <h1> {{ dive.number }} </h1>
- {% endfor %}</code></pre>
-</div></div>
-<div class="literalblock">
-<div class="title">output.html</div>
-<div class="content">
-<pre><code> <h1> 1 </h1>
- <h1> 2 </h1>
- <h1> 3 </h1></code></pre>
-</div></div>
-<div class="paragraph"><p>Additional information about <em>Grantlee</em> can be found
-<a href="http://www.grantlee.org/apidox/for_themers.html">here</a></p></div>
-</div>
-<div class="sect2">
-<h3 id="_grantlee_exported_variables">19.2. Grantlee exported variables</h3>
-<div class="paragraph"><p>Only a subset of the dive data is exported:</p></div>
-<div class="tableblock">
-<table rules="all"
-width="100%"
-frame="border"
-cellspacing="0" cellpadding="4">
-<col width="50%" />
-<col width="50%" />
-<tbody>
-<tr>
-<td align="left" valign="top"><p class="table"><strong>Name</strong></p></td>
-<td align="left" valign="top"><p class="table"><strong>Description</strong></p></td>
-</tr>
-<tr>
-<td align="left" valign="top"><p class="table">number</p></td>
-<td align="left" valign="top"><p class="table">(<strong>int</strong>) dive number</p></td>
-</tr>
-<tr>
-<td align="left" valign="top"><p class="table">id</p></td>
-<td align="left" valign="top"><p class="table">(<strong>int</strong>) unique dive ID, should be used to fetch the dive profile</p></td>
-</tr>
-<tr>
-<td align="left" valign="top"><p class="table">date</p></td>
-<td align="left" valign="top"><p class="table">(<strong>string</strong>) data of the dive</p></td>
-</tr>
-<tr>
-<td align="left" valign="top"><p class="table">time</p></td>
-<td align="left" valign="top"><p class="table">(<strong>string</strong>) time of the dive</p></td>
-</tr>
-<tr>
-<td align="left" valign="top"><p class="table">location</p></td>
-<td align="left" valign="top"><p class="table">(<strong>string</strong>) location of the dive</p></td>
-</tr>
-<tr>
-<td align="left" valign="top"><p class="table">duration</p></td>
-<td align="left" valign="top"><p class="table">(<strong>string</strong>) duration of the dive</p></td>
-</tr>
-<tr>
-<td align="left" valign="top"><p class="table">depth</p></td>
-<td align="left" valign="top"><p class="table">(<strong>string</strong>) depth of the dive</p></td>
-</tr>
-<tr>
-<td align="left" valign="top"><p class="table">divemaster</p></td>
-<td align="left" valign="top"><p class="table">(<strong>string</strong>) divemaster data</p></td>
-</tr>
-<tr>
-<td align="left" valign="top"><p class="table">buddy</p></td>
-<td align="left" valign="top"><p class="table">(<strong>string</strong>) buddy data</p></td>
-</tr>
-<tr>
-<td align="left" valign="top"><p class="table">airTemp</p></td>
-<td align="left" valign="top"><p class="table">(<strong>string</strong>) air temperature of dive</p></td>
-</tr>
-<tr>
-<td align="left" valign="top"><p class="table">waterTemp</p></td>
-<td align="left" valign="top"><p class="table">(<strong>string</strong>) water temperature of dive</p></td>
-</tr>
-<tr>
-<td align="left" valign="top"><p class="table">notes</p></td>
-<td align="left" valign="top"><p class="table">(<strong>string</strong>) dive notes</p></td>
-</tr>
-<tr>
-<td align="left" valign="top"><p class="table">rating</p></td>
-<td align="left" valign="top"><p class="table">(<strong>int</strong>) dive rating ranges from 0 to 5</p></td>
-</tr>
-<tr>
-<td align="left" valign="top"><p class="table">sac</p></td>
-<td align="left" valign="top"><p class="table">(<strong>string</strong>) sac value</p></td>
-</tr>
-<tr>
-<td align="left" valign="top"><p class="table">tags</p></td>
-<td align="left" valign="top"><p class="table">(<strong>string</strong>) all dive tags concatenate together</p></td>
-</tr>
-<tr>
-<td align="left" valign="top"><p class="table">gas</p></td>
-<td align="left" valign="top"><p class="table">(<strong>string</strong>) used gas cylinder</p></td>
-</tr>
-</tbody>
-</table>
-</div>
-<div class="paragraph"><p><em>Subsurface</em> also exports <strong>template_options</strong> data. This data must be used as
-<em>CSS</em> values to provide a dynamically editable template. The exported data
-is shown in the following table:</p></div>
-<div class="tableblock">
-<table rules="all"
-width="100%"
-frame="border"
-cellspacing="0" cellpadding="4">
-<col width="50%" />
-<col width="50%" />
-<tbody>
-<tr>
-<td align="left" valign="top"><p class="table"><strong>Name</strong></p></td>
-<td align="left" valign="top"><p class="table"><strong>Description</strong></p></td>
-</tr>
-<tr>
-<td align="left" valign="top"><p class="table">font</p></td>
-<td align="left" valign="top"><p class="table">(<strong>string</strong>) font family</p></td>
-</tr>
-<tr>
-<td align="left" valign="top"><p class="table">borderwidth</p></td>
-<td align="left" valign="top"><p class="table">(<strong>int</strong>) border-width value dynamically calculated as 0.1% of the page width with minimum value of 1px</p></td>
-</tr>
-<tr>
-<td align="left" valign="top"><p class="table">font_size</p></td>
-<td align="left" valign="top"><p class="table">(<strong>double</strong>) size of fonts in vw, ranges between 1.0 and 2.0</p></td>
-</tr>
-<tr>
-<td align="left" valign="top"><p class="table">line_spacing</p></td>
-<td align="left" valign="top"><p class="table">(<strong>double</strong>) distance between text lines, ranges between 1.0 and 3.0</p></td>
-</tr>
-<tr>
-<td align="left" valign="top"><p class="table">color1</p></td>
-<td align="left" valign="top"><p class="table">(<strong>string</strong>) background color</p></td>
-</tr>
-<tr>
-<td align="left" valign="top"><p class="table">color2</p></td>
-<td align="left" valign="top"><p class="table">(<strong>string</strong>) primary table cell color</p></td>
-</tr>
-<tr>
-<td align="left" valign="top"><p class="table">color3</p></td>
-<td align="left" valign="top"><p class="table">(<strong>string</strong>) secondary table cell color</p></td>
-</tr>
-<tr>
-<td align="left" valign="top"><p class="table">color4</p></td>
-<td align="left" valign="top"><p class="table">(<strong>string</strong>) primary text color</p></td>
-</tr>
-<tr>
-<td align="left" valign="top"><p class="table">color5</p></td>
-<td align="left" valign="top"><p class="table">(<strong>string</strong>) secondary text color</p></td>
-</tr>
-<tr>
-<td align="left" valign="top"><p class="table">color6</p></td>
-<td align="left" valign="top"><p class="table">(<strong>string</strong>) border colors</p></td>
-</tr>
-</tbody>
-</table>
-</div>
-<div class="literalblock">
-<div class="title">template.html</div>
-<div class="content">
-<pre><code> border-width: {{ template_options.borderwidth }}px;</code></pre>
-</div></div>
-<div class="literalblock">
-<div class="title">output.html</div>
-<div class="content">
-<pre><code> border-width: 3px;</code></pre>
-</div></div>
-<div class="paragraph"><p>Another variable that <em>Subsurface</em> exports is <strong>print_options</strong>. This variable
-contains a single member:</p></div>
-<div class="tableblock">
-<table rules="all"
-width="100%"
-frame="border"
-cellspacing="0" cellpadding="4">
-<col width="50%" />
-<col width="50%" />
-<tbody>
-<tr>
-<td align="left" valign="top"><p class="table"><strong>Name</strong></p></td>
-<td align="left" valign="top"><p class="table"><strong>Description</strong></p></td>
-</tr>
-<tr>
-<td align="left" valign="top"><p class="table">grayscale</p></td>
-<td align="left" valign="top"><p class="table">Use <em>CSS</em> filters to convert the page into grayscale (should be added to body style to enable printing grayscale prints)</p></td>
-</tr>
-</tbody>
-</table>
-</div>
-<div class="literalblock">
-<div class="title">template.html</div>
-<div class="content">
-<pre><code> body {
- {{ print_options.grayscale }};
- }</code></pre>
-</div></div>
-<div class="literalblock">
-<div class="title">output.html</div>
-<div class="content">
-<pre><code> body {
- -webkit-filter: grayscale(100%);
- }</code></pre>
-</div></div>
-</div>
-<div class="sect2">
-<h3 id="_defined_css_selectors">19.3. Defined CSS selectors</h3>
-<div class="paragraph"><p>As the dive profile is placed after rendering, <em>Subsurface</em> uses a special
-<em>CSS</em> selectors to do some searches in the HTML output. The <em>CSS</em> selectors
-in the following table should be added.</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>Selector</strong></p></td>
-<td align="left" valign="top"><p class="table"><strong>Type</strong></p></td>
-<td align="left" valign="top"><p class="table"><strong>Description</strong></p></td>
-</tr>
-<tr>
-<td align="left" valign="top"><p class="table">dive_{{ dive.id }}</p></td>
-<td align="left" valign="top"><p class="table">id</p></td>
-<td align="left" valign="top"><p class="table">is used to fetch the relevant dive profile</p></td>
-</tr>
-<tr>
-<td align="left" valign="top"><p class="table">diveProfile</p></td>
-<td align="left" valign="top"><p class="table">class</p></td>
-<td align="left" valign="top"><p class="table">each div that will contain a dive profile should have this class selector in addition to the dive_{{ dive.id }} id selector</p></td>
-</tr>
-<tr>
-<td align="left" valign="top"><p class="table">dontbreak</p></td>
-<td align="left" valign="top"><p class="table">class</p></td>
-<td align="left" valign="top"><p class="table">prevents the div with this class to be divided into two pages, this can be used
-in flow layout templates only (when data-numberofdives = 0)</p></td>
-</tr>
-</tbody>
-</table>
-</div>
-<div class="admonitionblock">
-<table><tr>
-<td class="icon">
-<img src="./images/icons/important.png" alt="Important" />
-</td>
-<td class="content">Rendering dive profiles is not supported for flow layout templates (when
-data-numberofdives = 0).</td>
-</tr></table>
-</div>
-</div>
-<div class="sect2">
-<h3 id="_special_attributes">19.4. Special attributes</h3>
-<div class="paragraph"><p>There are two ways of rendering- either rendering a specific number of dives
-in each page or make <em>Subsurface</em> try to fit as much dives as possible into
-one page (<em>flow</em> rendering).</p></div>
-<div class="paragraph"><p>The <strong>data-numberofdives</strong> data attribute is added to the body tag to set the
-rendering mode</p></div>
-<div class="ulist"><ul>
-<li>
-<p>
-render 6 dives per page:
-</p>
-</li>
-</ul></div>
-<div class="literalblock">
-<div class="content">
-<pre><code> <body data-numberofdives = 6></code></pre>
-</div></div>
-<div class="ulist"><ul>
-<li>
-<p>
-render as much dives as possible:
-</p>
-</li>
-</ul></div>
-<div class="literalblock">
-<div class="content">
-<pre><code> <body data-numberofdives = 0></code></pre>
-</div></div>
-<div class="admonitionblock">
-<table><tr>
-<td class="icon">
-<img src="./images/icons/important.png" alt="Important" />
-</td>
-<td class="content">All CSS units should be in relative lengths only, to support printing on any
-page size.</td>
-</tr></table>
-</div>
-</div>
-</div>
-</div>
-<div class="sect1">
-<h2 id="_appendix_f_faqs">20. APPENDIX F: FAQs.</h2>
-<div class="sectionbody">
-<div class="sect2">
-<h3 id="S_APPENDIX_F">20.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’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 <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’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:</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">20.2. Some dive profiles have time discrepancies with the recorded samples from my dive computer…</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’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”.</p></div>
-</div>
-<div class="sect2">
-<h3 id="_some_dive_profiles_are_missing_from_the_download">20.3. Some dive profiles are missing from the download</h3>
-<div class="paragraph" id="DC_HISTORY"><p><em>Question</em>: I cannot download all my dives, only the most recent ones even
-though my dive computer’s manual states that it records history of e.g. 999
-dives.</p></div>
-<div class="paragraph"><p><em>Answer</em>: Dive history is different than the dive profiles on the log. The
-history only keeps track of the total number of dives and total amount of
-time spent below surface. The logs, on the other hand, store the dive
-profile, but they have limited amount of memory to do so. The exact amount
-of dive profiles that can be stored on the device depend on sample interval
-and duration of the dives. Once the memory is full the oldest dives get
-overwritten with new dives. Thus we are only able to download the last 13,
-30 or 199 dives.</p></div>
-<div class="paragraph"><p>If you have downloaded your dives to different dive logging software before
-they were overwritten, there is a high chance that Subsurface can import
-these. However, if the logs are only on your dive computer, they cannot be
-salvaged after being over written by new dives.</p></div>
-</div>
-</div>
-</div>
-</div>
-<div id="footnotes"><hr /></div>
-<div id="footer">
-<div id="footer-text">
-Last updated 2015-12-15 13:35:30 PST
-</div>
-</div>
-</body>
-</html>
+<!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; } + + +@media screen { + body { + max-width: 50em; /* approximately 80 characters wide */ + margin-left: 16em; + } + + #toc { + position: fixed; + top: 0; + left: 0; + bottom: 0; + width: 13em; + padding: 0.5em; + padding-bottom: 1.5em; + margin: 0; + overflow: auto; + border-right: 3px solid #f8f8f8; + background-color: white; + } + + #toc .toclevel1 { + margin-top: 0.5em; + } + + #toc .toclevel2 { + margin-top: 0.25em; + display: list-item; + color: #aaaaaa; + } + + #toctitle { + margin-top: 0.5em; + } +} +</style> +<script type="text/javascript"> +/*<+'])'); + // 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.5, Octobre 2015</em></span></p></div> +<div class="paragraph"><p>Bienvenue en tant qu’utilisateur de <em>Subsurface</em>, 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. <em>Subsurface</em> offre de nombreux avantages par +rapport à d’autres solutions logicielles similaires :</p></div> +<div class="ulist"><ul> +<li> +<p> +Avez-vous besoin d’une façon d’enregistrer vos plongées utilisant des + équipements loisirs, même sans utiliser d’ordinateur de plongée ? +</p> +</li> +<li> +<p> +Utilisez-vous deux marques différentes d’ordinateurs de plongée, chacun avec + son propre logiciel propriétaire pour télécharger les enregistrements des + plongées ? Plongez-vous avec un recycleur ou un équipement en circuit ouvert + ou de loisir ? Utilisez-vous un enregistreur de profondeur et de durée + Reefnet Sensus avec un ordinateur de plongée ? <em>Subsurface</em> offre une + interface standard pour télécharger les enregistrements des plongées à + partir de tous ces équipements de plongée, en enregistrant et en analysant + ces enregistrements dans un système unique. +</p> +</li> +<li> +<p> +Utilisez-vous plus d’un système d’exploitation ? <em>Subsurface</em> est + intégralement compatible avec Mac, Linux et Windows, ce qui vous permet + d’accéder à vos enregistrements de plongées sur chaque système + d’exploitation en utilisant une application unique. +</p> +</li> +<li> +<p> +Utilisez-vous Linux ou Mac mais votre ordinateur de plongée n’a que des + logiciels pour Windows pour télécharger les informations de plongées (par + exemple Mares) ? <em>Subsurface</em> fournit un moyen de télécharger et d’analyser + vos enregistrements de plongées sur d’autres systèmes d’exploitation. +</p> +</li> +<li> +<p> +Avez-vous besoin d’un planificateur de plongée graphique intuitif qui + intègre et prend en compte les plongées qui ont déjà été enregistrées ? +Avez-vous besoin d’un moyen d’nregistrer et de sauvegarder vos plongées sur +Internet, vous permettant de les voir depuis n’importe où en utilisant un +navigateur Internet ? <em>Subsurface</em> est disponible pour Windows (Win XP ou +plus récent), les Macs basés sur processeurs Intel (OS/X) et de nombreuses +distributions Linux. <em>Subsurface</em> peut être compilé pour bien plus de +plateformes matérielles et d’environnements logiciels où Qt et +libdivecomputer sont disponibles. +</p> +</li> +</ul></div> +<div class="paragraph"><p>Ce manuel explique comment utiliser le programme <em>Subsurface</em>. Pour +installer le logiciel, consultez la page <em>Téléchargement</em> sur le +<a href="http://subsurface-divelog.org/">site web de <em>Subsurface</em></a>. En cas de +problème, vous pouvez envoyer un e-mail sur +<a href="mailto:subsurface@subsurface-divelog.org">notre liste de diffusion</a> et +rapportez les bogues sur <a href="http://trac.hohndel.org">notre bugtracker</a>. Pour +des instructions de compilation du logiciel et (si besoin) de ses +dépendances, merci de consulter le fichier INSTALL inclus dans les sources +logicielles.</p></div> +<div class="paragraph"><p><strong>Public</strong> : Plongeurs loisirs, apnéistes, plongeurs Tek et plongeurs +professionnels</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="_utilisation_de_ce_manuel">1. Utilisation de ce manuel</h2> +<div class="sectionbody"> +<div class="paragraph"><p>When opened from within <em>Subsurface</em>, this manual does not have external +controls for paging or selecting previous pages. However, two facilities are +provided:</p></div> +<div class="paragraph"><p>The <em>SEARCH</em> function is activated by pressing control-F or command-F on the +keyboard. A text box appears at the bottom right-hand of the window (see +image below). For instance, typing the word "<em>weights</em>" into the search +text box, searches throughout the user manual. To the right of the search +text box are two arrows pointing up and down. These find the previous and +the next occurrence of the search term. +<span class="image"> +<img src=":images/usermanualfunctions.jpg" alt="User manual functions" /> +</span></p></div> +<div class="paragraph"><p><em>PREVIOUS/NEXT LINK</em>. Move between links (underlined words that jump to +specific sections in the user manual) by right-clicking on the text of the +manual. This brings up a context menu to previous links selected. (see +image above). For instance if a link has been selected, then the option to +<em>Go Back</em> shows the text at the last link selected (similar to the Previous +Page button in a browser). Conversely the <em>Go Forward</em> option jumps to the +text seen before selecting the <em>Go Back</em> option. The <em>Reload</em> option reloads +the complete user manual into the window.</p></div> +</div> +</div> +<div class="sect1"> +<h2 id="S_UserSurvey">2. Le sondage utilisateur</h2> +<div class="sectionbody"> +<div class="paragraph"><p>In order to develop <em>Subsurface</em> to serve its users in the best possible +way, it’s important to have user information. Upon launching <em>Subsurface</em> +and using the 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. All data the user sends is useful, and +will only be used to steer future development and to customize the software +to fit the needs of the <em>Subsurface</em> users. If you complete the survey, or +click the option not to be asked again, that should be the last +communication of this type you receive. However, if your diving and/or +subsurface habits change and you wish to fill in another survey, just launch +<em>Subsurface</em> with the <em>--survey</em> option on the command line.</p></div> +</div> +</div> +<div class="sect1"> +<h2 id="S_StartUsing">3. Commencer à utiliser le programme</h2> +<div class="sectionbody"> +<div class="paragraph"><p>La fenêtre <em>Subsurface</em> est généralement divisée en 4 panneaux avec un <strong>Menu +principal</strong> (Fichier Importer Journal Vue Aide) en haut de la fenêtre (pour +Windows et Linux) ou en haut de l'écran (pour Mac et Ubuntu Unity). Les +quatre panneaux sont :</p></div> +<div class="paragraph"><p>The <strong>Dive List</strong> on the bottom left, showing 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 <strong>Dive List</strong> is an important tool for manipulating a dive log.</p></div> +<div class="paragraph"><p>The <strong>Dive Map</strong> on the bottom right, showing the user’s dive sites on a world +map and centered on the site of the last dive selected in the <strong>Dive List</strong>.</p></div> +<div class="paragraph"><p>The <strong>Info</strong> on 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> on 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 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 the last +time the program was used.</p></div> +<div class="paragraph"><p>If a single 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. If several dives are selected, the last highlighted dive is the +<em>selected dive</em>, but summary data of all <em>highlighted dives</em> is shown in the +<strong>Stats</strong> tab of the <strong>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_f22.jpg" alt="The Main Window" /> +</div> +</div> +<div class="paragraph"><p>The user decides which of the four panels are displayed by selecting the +<strong>View</strong> option on the main menu. This feature has several choices of display:</p></div> +<div class="paragraph"><p><strong>Tout</strong> : affiche les quatre panneaux tels que sur la capture d'écran ci-dessus.</p></div> +<div class="paragraph"><p><strong>Liste des plongées</strong> : affiche uniquement la liste des plongées.</p></div> +<div class="paragraph"><p><strong>Profil</strong> : affiche uniquement le profile de plongée de la plongée sélectionnée.</p></div> +<div class="paragraph"><p><strong>Info</strong> : affiche uniquement les notes de plongées de la dernière plongée sélectionnée et les statistiques pour +toutes les plongées mises en surbrillance.</p></div> +<div class="paragraph"><p><strong>Globe</strong>: Show only the world map, centered on the last selected dive.</p></div> +<div class="paragraph"><p>Like other functions that can be accessed via the Main Menu, these options +can also 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’s chosen language +may cause <em>Subsurface</em> to use different shortcut keys, they are not listed +in this user manual.</p></div> +<div class="paragraph"><p>When the program is started for the first time, it shows no information at +all, because it does not have any dive information available. In the +following sections, the procedures to create a new logbook will be +explained.</p></div> +</div> +</div> +<div class="sect1"> +<h2 id="S_NewLogbook">4. Créer un nouveau carnet de plongée</h2> +<div class="sectionbody"> +<div class="paragraph"><p>Select <em>File → New Logbook</em> from the main menu. All existing dive data are +cleared so 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">5. Enregistrement des informations de plongée dans le carnet</h2> +<div class="sectionbody"> +<div class="paragraph"><p>Now that a new logbook is created, it is simple to add dive data it. +<em>Subsurface</em> allows several ways of adding dive data to a logbook. +1) Si l’utilisateur possède un carnet manuscrit, un tableur ou une autre forme + de + carnet maintenu manuellement, les données de plongée peuvent être ajoutées + au carnet en utilisant une des approches suivantes : + - Enter dive information by hand. This is useful if the diver didn’t + utilisé d’ordinateur de plongée et que les plongées sont inscrites dans un + carnet manuscrit. Voir <a href="#S_EnterData">Entrer les informations de plongée + à la main</a></p></div> +<div class="ulist"><ul> +<li> +<p> +Importer les informations de plongée qui ont été maintenues soit dans un + tableur + soit dans un fichier CSV. Se reporter à : <a href="#S_Appendix_D">ANNEXE D : + Exporter un tableur vers le format CSV</a> et à + <a href="#S_ImportingCSVDives">Importer des plongées au format CSV</a>. +If a dive is recorded using a dive computer, the depth profile and a large +amount of additional information can be accessed. These dives can be +imported from: +</p> +</li> +<li> +<p> +L’ordinateur de plongée lui-même. Voir : <a href="#S_ImportDiveComputer">Importer + de nouvelles informations de plongée à partir de l’ordinateur de plongée</a> ou +</p> +</li> +<li> +<p> +Logiciels propriétaires fournis par les fabricants d’ordinateurs de + plongée. Voir + <a href="#S_ImportingAlienDiveLogs">Importer les informations à partir d’autres + sources de données numériques ou d’autres formats de données</a>. +</p> +</li> +<li> +<p> +Spreadsheet or CSV files containing dive profiles. + Voir : <a href="#S_ImportingCSVDives">Importer les plongées au format CSV à partir + des ordinateurs de plongées ou d’autres logiciels de carnet de plongée</a> +</p> +</li> +</ul></div> +<div class="sect2"> +<h3 id="S_EnterData">5.1. Entrer les informations de plongée à la main</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 the dive master or dive +guide, and some remarks about the dive. <em>Subsurface</em> can store much more +information for each dive. To add a dive to a dive log, select <em>Log → Add +Dive</em> from the Main Menu. The program then shows three panels on which to +enter information for a dive: two tabs in the <strong>Info</strong> panel (<strong>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_f22.jpg" alt="FIGURE: Add dive" /> +</div> +</div> +<div class="paragraph"><p>When you edit a field in 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 +<strong>Notes</strong> panel (see the image below). This message is displayed in all the +panels under 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_f22.jpg" alt="Blue edit bar" /> +</div> +</div> +<div class="paragraph"><p>The <em>Apply changes</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>Apply changes</em> button, a local copy of the +information for this specific dive is saved in memory. The <em>Apply changes</em> +button should ONLY be selected after all parts of a dive have been +entered. When you close 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="S_CreateProfile">5.1.1. 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 shown 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 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 shown by two right-angled red lines as seen below. +The time and depth represented by the cursor 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 you need to drag the appropriate waypoints downward to 20 m. To add a +waypoint, double-click on any line segment. To move an additional waypoint, +drag it. To remove a waypoint, right-click on it and choose "Remove this +point" from the context menu. Drag the waypoints to represent an accurate +time duration for the dive. Below is a dive profile for 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 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 above. The gas mixtures of segments of the dive profile can be +changed 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 (see image below).</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>With the profile now defined, more details must be added to have a fuller +record of the dive. To do this, the <strong>Notes</strong> and the <strong>Equipment</strong> tabs on the +top left hand of the <em>Subsurface</em> window should be used. Click on +<a href="#S_Notes_dc"><strong>this link</strong></a> for instructions on how to use these tabs.</p></div> +</div> +</div> +<div class="sect2"> +<h3 id="S_ImportDiveComputer">5.2. Importer de nouvelles informations de plongée à partir de l’ordinateur de plongée</h3> +<div class="sect3"> +<h4 id="_connecting_and_importing_data_from_a_dive_computer">5.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, using dive details 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 PC-Communication +mode. <strong>This could drain the dive computer’s battery</strong>. We recommend the +user checks to be sure 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.</td> +</tr></table> +</div> +<div class="paragraph"><p>To import dive information from a dive computer to a computer with +<em>Subsurface</em>, the two pieces of equipment must 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. To set up this communication, users need 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 achieve 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’s PC using 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. + (Se reporter au manuel de l’ordinateur de plongée) +</p> +</li> +<li> +<p> +In <em>Subsurface</em>, from the Main Menu, select <em>Import → Import From Dive + Computer</em>. Dialogue <strong>A</strong> in the figure below appears: +</p> +</li> +</ol></div> +<div class="imageblock" style="text-align:center;"> +<div class="content"> +<img src="images/DC_import_f20.jpg" alt="FIGURE: Download dialogue 1" /> +</div> +</div> +<div class="paragraph"><p>Dive computers tend to keep a certain number of dives in memory, even though +these dives have already been imported to <em>Subsurface</em>. For that reason, if +the dive computer allows this, <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).</p></div> +<div class="ulist"><ul> +<li> +<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> +</li> +<li> +<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 specific 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> +</li> +<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> has been accidentally + deleted or if there are older dives that still need to be downloaded from + the dive computer, this box needs to be checked. 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 dive in the <em>Subsurface</em> + divelog will be overwritten by the dive record from the computer. +</p> +</li> +<li> +<p> +The checkbox marked <em>Download into new trip</em> ensures that, after upload, the + downloaded dives are grouped together as a new trip(s) in the <strong>Dive List</strong>. +</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 there are problems with downloads(see below). +</p> +</li> +<li> +<p> +Then select the <em>Download</em> button. With communication established, you 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. Be patient. The <em>Download</em> dialogue shows a progress bar at the + bottom of the dialogue. Remember for some dive computers progress + information could be inaccurate since the program doesn’t know how much + downloadable data there is until the download is complete. After successful + download, Dialogue <strong>B</strong> in the figure above appears. After the dives have + been downloaded, they appear in a tabular format on the right-hand side of + the dialogue (see image <strong>B</strong>, above). Each dive comprises a row in the table, + with the date, duration and depth shown. Next to each dive is a checkbox: + check all the dives that need to be transferred to the <strong>Dive List</strong>. In the + case of the image above, the last six dives are checked and will be + transferred to the <strong>Dive List</strong>. Then click the <em>OK</em> button at the bottom of + the dialogue. 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. +</p> +</li> +</ul></div> +<div class="paragraph"><p>Then click the OK button. The checked dives are transferred to the <strong>Dive +List</strong>.</p></div> +<div class="ulist"><ul> +<li> +<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> +</li> +</ul></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="ulist"><ul> +<li> +<p> +Is the dive computer still in PC-communication or Upload mode? +</p> +</li> +<li> +<p> +Is the dive computer’s battery fully charged? If not then charge or replace + it. +</p> +</li> +<li> +<p> +Is the connecting cable faulty? Does the cable work 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> +</li> +<li> +<p> +Consult + <a href="#_appendix_a_operating_system_specific_information_for_importing_dive_information_from_a_dive_computer">Appendix + A</a> to be sure the correct Mount Point was specified (see above). +</p> +</li> +<li> +<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> +</li> +</ul></div> +<div class="paragraph"><p>If the <em>Subsurface</em> computer does not recognize the USB adaptor by showing +an appropriate device name next to the Mount Point, then there is a +possibility the cable or USB adaptor is faulty. A faulty cable is the most +common cause of communication failure between a dive computer and +<em>Subsurface</em> computer. It’s also possible the <em>Subsurface</em> computer cannot +interpret the data. Perform a download for diagnostic purposes with the +following two 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 where the information will be saved. 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 +analyzed. 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_Bluetooth">5.2.2. Connecting <em>Subsurface</em> to a Bluetooth-enabled dive computer</h4> +<div class="paragraph"><p>Bluetooth is becoming a more common way of communication between dive +computers and <em>Subsurface</em>, for or instance, the Shearwater Petrel Mk2 and +the OSTC Mk3. <em>Subsurface</em> provides a largely operating system independent +Bluetooth interface. Setting up <em>Subsurface</em> for Bluetooth communication +requires four steps:</p></div> +<div class="ulist"><ul> +<li> +<p> +Be sure Bluetooth is activated on the host computer running <em>Subsurface</em>. +</p> +</li> +<li> +<p> +Be sure <em>Subsurface</em> sees the Bluetooth adapter on the host computer. +</p> +</li> +<li> +<p> +Be sure the Bluetooth-enabled dive computer is Bluetooth-discoverable and in + PC upload mode. +</p> +</li> +<li> +<p> +Be sure <em>Subsurface</em> is paired with the Bluetooth-enabled dive computer. +</p> +</li> +</ul></div> +<div class="paragraph"><p>Select the Download dialogue by selecting <em>Import → Import from dive +computer</em> from the <strong>Main Menu</strong>. If you check the box labelled <em>"Choose +Bluetooth download mode"</em>, the dialogue below appears. +===== Sur Linux ou MacOS :</p></div> +<div class="imageblock" style="text-align:center;"> +<div class="content"> +<img src="images/DC_import_Bluetooth.jpg" alt="FIGURE: Download Bluetooth" /> +</div> +</div> +<div class="paragraph"><p>On the <em>Linux</em> or <em>MacOS</em> platforms the name of the <em>Subsurface</em> computer +and its Bluetooth address are shown on the right hand side, On the left hand +side, if the computer has connected more than one local Bluetooth devices +the user can use the list box to indicate which one needs to connect to +<em>Subsurface</em>. The power state (on/off) of the Bluetooth adapter is shown +below the address and can be changed by checking the <em>Turn on/off</em> box. If +the Bluetooth address is not shown, then <em>Subsurface</em> does not see the local +Bluetooth device. Be sure the Bluetooth driver is installed correctly on the +<em>Subsurface</em> computer and check if it can be used by other Bluetooth +utilities like <em>bluetoothctl</em> or <em>bluemoon</em>. This finishes the first two +steps above. Be sure the Bluetooth-enabled dive computer is in PC-upload +mode and it is discoverable by other Bluetooth devices. Consult the manual +of the dive computer for more information. Now the third item in the list +above has been finished. Select the <em>Scan</em> button towards the bottom left +of the dialogue above. After searching, the dive computer should be listed +(perhaps as one of a number of Bluetooth devices) in the main list box on +the lefthand side of the dialogue (see image above). If this does not work, +select the <em>Clear</em> button, then scan again for Bluetooth devices using the +<em>Scan</em> button. After taking these actions <em>Subsurface</em> should see the dive +computer. The label of the discovered dive computer contains the name of +the device, its address and its pairing status. If the device is not paired +and has a red background color, a context menu can be opened by selecting +the item with a right-click. Select the the <em>Pair</em> option and wait for the +task to complete. If this dive computer is being paired to Subsurface for +the first time, it’s possible Subsurface will request a Pass Code or PIN +number. The most commonly-used Pass Code is 0000, and this works for the +Shearwater Petrel. If necessary, consult the user manual of the dive +computer being used.</p></div> +<div class="sidebarblock"> +<div class="content"> +<div class="admonitionblock"> +<table><tr> +<td class="icon"> +<img src="images/icons/important.png" alt="Important" /> +</td> +<td class="content">Currently <em>Subsurface</em> does not support Bluetooth pairing with dive +computers that require a custom PIN code. In order to pair the devices, use +other OS utilities as suggested below.</td> +</tr></table> +</div> +<div class="paragraph"><p>One way to achieve this is to use <code>bluetoothctl</code>:</p></div> +<div class="literalblock"> +<div class="content"> +<pre><code>$ bluetoothctl +[bluetooth]# agent KeyboardOnly +Agent registered +[bluetooth]# default-agent +Default agent request successful +[bluetooth]# pair 00:80:25:49:6C:E3 +Attempting to pair with 00:80:25:49:6C:E3 +[CHG] Device 00:80:25:49:6C:E3 Connected: yes +Request PIN code +[agent] Enter PIN code: 0000</code></pre> +</div></div> +</div></div> +<div class="paragraph"><p>After the devices are paired, press the <em>Save</em> button of the dialogue. This +closes the Bluetooth dialogue. Now select <em>Download</em> in the <em>Download from +dive computer</em> dialogue which should still be open. The downloaded dives are +shown on the righthand side of the download dialogue.</p></div> +<div class="sect4"> +<h5 id="_sur_windows">Sur Windows :</h5> +<div class="imageblock" style="text-align:center;"> +<div class="content"> +<img src="images/DC_import_Bluetooth_Windows.png" alt="FIGURE: Download Bluetooth on Windows" /> +</div> +</div> +<div class="paragraph"><p>On <em>Windows</em> platforms the <em>Local Bluetooth device details section</em> on the +right is not displayed as is the case on the Linux/Mac systems. To start a +scan (by pressing the <em>Scan</em> button) check that the Bluetooth device on the +<em>Subsurface</em> computer is turned on by selecting the dive computer from the +list of available Bluetooth devices (see image above). If the dive computer +is being accessed by Subsurface for the first time, it’s possible Subsurface +will request a Pass Code or PIN number. Supply the Pass Code recommended in +the user manual of the dive computer. A Pass Code or PIN of 0000 is often +the default.</p></div> +<div class="paragraph"><p>The pairing step is checked and done automatically during the download +process. If the devices have never been paired the system will ask for your +permission and put a message on the right side of the screen: <em>Add a device, +Tap to set up your DC device</em>. Always allow this pairing. After a discovered +item is selected, select the <em>Save</em> button. Finally select the <em>Download</em> +button on the <em>Download</em> dialogue and wait for the process to complete.</p></div> +<div class="admonitionblock"> +<table><tr> +<td class="icon"> +<img src="images/icons/important.png" alt="Important" /> +</td> +<td class="content">Currently <em>Subsurface</em> works only with local Bluetooth adapters which use +Microsoft Bluetooth Stack. If the local device uses <em>Widcomm</em>, <em>Stonestreet +One Bluetopia Bluetooth</em> or <em>BlueSoleil</em> drivers it will not work. However, +Bluetooth hardware/dongles from these manufacturers (e.g. iSonic) that +support the Microsoft Bluetooth Stack do work.</td> +</tr></table> +</div> +<div class="paragraph"><p>A log message on the bottom left of the <em>Remote Bluetooth device selection</em> +shows details about the current status of the Bluetooth agent. To select +another dive computer for download using the "Remote Bluetooth selection +dialogue" press the three-dots button from the <em>"Choose Bluetooth download +mode"</em> option.</p></div> +<div class="admonitionblock"> +<table><tr> +<td class="icon"> +<img src="images/icons/important.png" alt="Important" /> +</td> +<td class="content"><strong>IN CASE OF PROBLEMS</strong>: If the Bluetooth adapter from the <em>Subsurface</em> computer +gets stuck and the <em>Download</em> process fails repeatedly, + <em>unpair</em> the devices and then repeat the above steps. If this is not successful, + <a href="#S_HowFindBluetoothDeviceName"><em>Appendix A</em></a> contains +information for manually setting up and inspecting the Bluetooth connection +with <em>Subsurface</em>.</td> +</tr></table> +</div> +</div> +</div> +<div class="sect3"> +<h4 id="S_DeviceNames">5.2.3. 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 a buddy’s dive computer is +the same make and model as your own and dive logs are uploaded from both +dive computers to the same <em>Subsurface</em> computer, then you might like to +call one "Alice’s Suunto D4" and the other "Bob’s Suunto D4". Alternatively, +consider a technical diver who 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 "Suunto D4 +(2)". This is easily done in <em>Subsurface</em>. On the <strong>Main Menu</strong>, select <em>Log +→ Edit device names</em>. A dialog box opens, showing 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">5.2.4. Updating the dive information imported from the dive computer.</h4> +<div class="paragraph"><p>With the uploaded dives in the <strong>Dive List</strong>, the information from the dive +computer is not complete and more details must be added to have a full +record of the dives. To do this, the <strong>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 class="sect4"> +<h5 id="S_Notes_dc">Notes</h5> +<div class="paragraph"><p>To have a more complete dive record, the user needs to add additional +information by hand. The procedure below is virtually identical for +hand-entered dives and for dives downloaded from a dive computer.</p></div> +<div class="paragraph"><p>In some cases, you must provide the date and time of the dive, for example +when entering a dive by hand or when a dive computer doesn’t provide the +date and time of the dive. (Usually the date and time of the dive, gas +mixture and water temperature are shown as obtained from the dive computer) +If the contents of the <strong>Notes tab</strong> is changed or edited in any way, the +message in a blue box at the top of the panel shows the dive is being +edited. If you click on the <strong>Notes</strong> tab, the following fields are visible +(left hand image, below):</p></div> +<div class="imageblock" style="text-align:center;"> +<div class="content"> +<img src="images/AddDive3_f22.jpg" alt="FIGURE: The Notes tab" /> +</div> +</div> +<div class="paragraph"><p>The right hand image, above, shows a <strong>Notes tab</strong> filled with dive +information. The <strong>Time</strong> field reflects the date and time of the dive. By +clicking the date, a calendar is displayed from which you 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 over-typing the information displayed.</p></div> +<div class="paragraph"><p><strong>Air/water temperatures</strong>: Air and water temperatures during the dive are shown +in text boxes to the right of the Start time. Many dive computers supply water +temperature information and this box may have information. +If air temperature isn’t provided by the dive computer, the first temperature reading +might be used for the air temperature. Generally this is close to the real air temperature. +If editing is required, only a value is required, the units of temperature will be +automatically supplied by +<em>Subsurface</em> (following the <em>Preferences</em>, metric or imperial units will +be used).</p></div> +<div class="paragraph"><p><strong>Location</strong>:</p></div> +<div class="admonitionblock"> +<table><tr> +<td class="icon"> +<img src="images/icons/warning2.png" alt="Warning" /> +</td> +<td class="content">Dive locations are managed as a <strong>separate</strong> part of the dive log. The dive +information in the <strong>Notes</strong> and <strong>Equipment</strong> tabs can therefore NOT be edited +at the same time as the dive site information. Save all the other dive +information (e.g. divemaster, buddy, protective gear, notes about the dive) +by selecting <em>Apply changes</em> on the <strong>Notes</strong> tab BEFORE editing the dive site +information. Then supply a dive site name in the textbox labelled <em>Location</em> +on the <strong>Notes</strong> tab.</td> +</tr></table> +</div> +<div class="paragraph"><p>Type in the name of the dive site, e.g. "Tihany, Lake Balaton, Hungary". If +several dives are made at the same location, the site information for the +first dive is re-used. Existing dive locations can be edited by selecting +(on the <strong>Dive List</strong> panel) a dive done at that site and by opening the +location information. Click the globe button on the right of the location +name (see image on the right, above). When entering a dive location name, +auto location of dive site names makes it easy to select an existing dive +site name. When typing the name of a dive site, a dropdown list appears +showing all sites with similar names. If the dive site has been used before, +click on the already-existing name. The dive site names in the dropdown +list contain either a globe symbol (indicating existing dive sites in the +<em>Subsurface</em> database) or a <strong>+</strong> symbol (indicating dive site names that +appear consistent with the current dive site name but which haven’t been +added to the dive site database). If the present dive site has not been +used before, a message appears as follows (image <strong>A</strong> below):</p></div> +<div class="imageblock" style="text-align:center;"> +<div class="content"> +<img src="images/Locations1_f22.jpg" alt="FIGURE:Location description panel" /> +</div> +</div> +<div class="paragraph"><p>Doubleclick on the new dive site name. A panel appears to enter the +coordinates and other information about the site (image <strong>B</strong>, above). The +most important items are the coordinates of the site. There are three ways +to specify coordinates:</p></div> +<div class="olist loweralpha"><ol class="loweralpha"> +<li> +<p> +Use the world map in the bottom right hand part of the <em>Subsurface</em> + window. The map displays an orange bar indicating "No location data - Move + the map and double-click to set the dive location". Doubleclick at the + appropriate place, and the orange bar disappears and the coordinates are + stored. +</p> +</li> +<li> +<p> +Use the <em>Subsurface</em> Companion app if you have an Android or iPhone device + with GPS and if the dive site coordinates were stored using it. + <a href="#S_Companion">Click here for more information</a> +</p> +</li> +<li> +<p> +Enter by hand if the coordinates are known, using one of four formats with + latitude followed by longitude: +</p> +<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> +</li> +</ol></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. Some keyboards +don’t have the degree sign (°). It can be replaced by a <strong>d</strong> like this: N30d +W20d. If both a dive site name and coordinates have been provided, save the +dive site information by selecting the button <em>Apply changes</em> at the top of +the panel.</p></div> +<div class="paragraph"><p><strong>Important</strong>: GPS coordinates of a dive site are linked to the location +name - so <strong>saving</strong> a dive site with only coordinates and no name +causes problems. (Subsurface will think all of these +dives have the same location and try to keep their GPS coordinates the +same).</p></div> +<div class="paragraph"><p><strong>Dive site name lookup:</strong> If coordinates have been typed into the appropriate +text box, you can do an automated name lookup based on the coordinates. +This is done when <em>Subsurface</em> uses the Internet to find the name of the dive site +based on the coordinates that were typed. If a name has been found, it is +automatically inserted into the tags box. The list box +(Titled <em>Dive sites on same coordinates</em>") at the bottom +of the dive site panel contains the names of other dives sites used at the +current location. For instance if the dive site is "Blue Hole" and there are several +sites named "Blue Hole", all of them are listed.</p></div> +<div class="paragraph"><p>Enter any other contextual information about the dive site (Description and +Notes), then select <em>Apply Changes</em> to save the geolocation for this dive +site. The dive site information can later be edited by clicking the globe +icon to the right of the dive site name in the <strong>Notes tab</strong>.</p></div> +<div class="paragraph"><p><strong>Dive mode</strong>: This is a dropdown box allowing you to choose the type of dive +performed. The options are OC (Open Circuit SCUBA, the default setting, for most recreational dives), +Freedive (dive without SCUBA equipment), CCR (Closed-circuit +rebreather) and pSCR (Passive semi-closed rebreather).</p></div> +<div class="paragraph"><p><strong>Divemaster</strong>: The name of the divemaster or dive guide should be +entered in this field +which offers auto selection based on the list of dive masters in +the current logbook.</p></div> +<div class="paragraph"><p><strong>Buddy</strong>: In this field, enter the name(s) of the buddy or buddies +(separated with commas) who were on the +dive. Auto selection 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 dive suit used can be entered. +Auto selection of the suit description is available. +Some dry-suit users may choose to use this field to record what combination of +suit and thermal under suit was used.</p></div> +<div class="paragraph"><p><strong>Rating</strong>: You 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>: You 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 done 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 you starts typing a tag, the +program +will list the tags that correspond to the typing. For instance, by typing +<code>cav</code>, the tags <strong>cave</strong> and <strong>cavern</strong> are shown 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 <em>Apply changes</em> and <em>Discard changes</em> buttons are used to save all the +information for tabs in the <strong>Info</strong> panel and in the <strong>Dive Profile</strong> +panel. Use them when <strong>ALL</strong> other information has been added. The image +<a href="#S_Notes_dc">at the beginning of this section</a> shows an example of a +<strong>Notes tab</strong> after completing the dive information.</p></div> +</div> +<div class="sect4"> +<h5 id="_equipment">Equipment</h5> +<div class="paragraph"><p>The Equipment tab lets you enter information about the type of cylinder and +gas used, as well as the weights used for the dive. The message in the blue +box at the top of the panel:</p></div> +<div class="imageblock" style="text-align:center;"> +<div class="content"> +<img src="images/BlueEditBar_f22.jpg" alt="FIGURE: Blue edit bar" /> +</div> +</div> +<div class="paragraph"><p>shows 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 behavior of the <strong>Dive profile</strong> (top right-hand panel).</p></div> +<div class="paragraph" id="cylinder_definitions"><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>For hand-entered dives, this information needs to be typed in. For dive +computers, <em>Subsurface</em> often gets the gas used from the dive computer and +automatically inserts the gas composition(% oxygen or % helium) in the +table. The + button at the top right lets you add more cylinders for this +dive. The dark dust bin icon on the left lets you delete 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. Start by selecting a cylinder type on the +left-hand side of the table. To select a cylinder, the <em>Type</em> 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 just 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 (<em>Work.press</em>) will automatically be shown in +the dialogue.</p></div> +<div class="paragraph"><p>Next, 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, save the data either by pressing <em>ENTER</em> on the keyboard or by +clicking outside the cell containing the cursor. Information for any +additional cylinders can be added by using the + button at the top right +hand. The 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 similar to that of the cylinder information. If you +click +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 <em>Type</em> 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>This can be used to select the type of weight system used during the dive or +just may start typing in the box to specify a different weighting mechanism +that will be saved by <em>Subsurface</em>. In the <strong>Weight</strong> field, type in the +amount of weight used during the dive. After specifying the weight system, +save the data by pressing <em>ENTER</em> on the keyboard or by clicking outside the +cell with the cursor. It’s 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 dust bin 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> +<div class="sect3"> +<h4 id="_editing_several_selected_dives_simultaneously">5.2.5. 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 +each is shown in the <strong>Dive profile</strong> tab, as well as a few items of +information in the <strong>Notes</strong> tab (e.g. water temperature) and in the +<strong>Equipment</strong> tab (e.g. gas pressures and gas composition). Other fields +remain empty. It may be useful to simultaneously edit some of the fields in +the <strong>Notes</strong> and <strong>Equipment</strong> tabs. For instance, it’s possible that a diver +performed several dives during a single day, using identical equipment at +the same dive site, or with the same divemaster and/or buddy or +tags. Instead of completing the information for each dive separately, select +all the dives for that day in the <strong>Dive List</strong> and insert the same +information in the <strong>Notes</strong> and <strong>Equipment</strong> fields that need identical +information. This is done by editing the dive notes or the equipment for any +one of the selected dives.</p></div> +<div class="paragraph"><p>Simultaneous editing only works with fields that do not already contain +information. This means 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 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>Notes</strong> and +<strong>Equipment</strong> tabs. Then, from the main menu, select <em>Log → Copy dive +components</em>. A box is presented with a selection of check boxes for most of +the fields in the <strong>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 → 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">5.2.6. Adding Bookmarks to a dive</h4> +<div class="paragraph"><p>Many divers wish to annotate dives with text that indicate particular +events, e.g. "Saw dolphins", or "Released surface buoy". This is easily +done:</p></div> +<div class="ulist"><ul> +<li> +<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 that point (see <strong>A</strong> below). +</p> +</li> +<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> +<li> +<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> +</li> +<li> +<p> +Hovering the mouse over the red bookmark, the appropriate text is shown at + the bottom of the information box (see <strong>D</strong> below). +</p> +</li> +</ul></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">5.2.7. Saving the updated dive information</h4> +<div class="paragraph"><p>The information entered in the <strong>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>Notes</strong> tab. If +the <em>Apply changes</em> button is clicked, the dive data are saved in the memory +image of the dive. If the <em>Discard changes</em> button is clicked, the newly +entered dive data are erased from the computer memory, although the dive +profile is retained. When the user exits <em>Subsurface</em> there is a final +prompt to confirm the new data should now be saved permanently on the +computer disk.</p></div> +</div> +</div> +<div class="sect2"> +<h3 id="_importer_les_informations_à_partir_d_8217_autres_sources_de_données_numériques_ou_d_8217_autres_formats_de_données">5.3. Importer les informations à partir d’autres sources de données numériques ou d’autres formats de données</h3> +<div class="paragraph" id="S_ImportingAlienDiveLogs"><p>If you’ve been diving for some time, it’s possible several dives were logged +using other dive log software. 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 you will +need to export the logbook(s) to an intermediate format so 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. a spreadsheet) +can also be imported by configuring the CSV import. <em>Subsurface</em> can also +import UDDF and UDCF files used by some dive log software and some dive +computers, like the Heinrichs & Weikamp DR5. Finally, for some dive log +software like Mares Dive Organizer we currently recommend you import the +logbooks first into a web service like <em>divelogs.de</em> and then import from +there with <em>Subsurface</em>. Divelogs.de supports a few additional logbook +formats that <em>Subsurface</em> currently cannot handle.</p></div> +<div class="paragraph"><p>If the format of other software is supported natively on Subsurface, select +either <em>Import → Import log files</em> or <em>File → 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. Below is more specific information to import +data to <em>Subsurface</em>. +==== Using the universal import dialogue</p></div> +<div class="paragraph" id="Unified_import"><p>Importing dives from other software is done through a universal interface +activated by selecting <em>Import</em> from the Main Menu, then clicking on <em>Import +Log Files</em>. This brings up 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 accesses 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> +Cochran dive logs +</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> +APD Inspiration/Evolution CCR logs +</p> +</li> +<li> +<p> +LiquiVision logs +</p> +</li> +<li> +<p> +divelog.de logs +</p> +</li> +<li> +<p> +OSTC Tools 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 format and then the specific log file in the large +window containing the file list on the right 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 class="sect3"> +<h4 id="_importing_from_ostctools">5.3.1. Importing from OSTCTools</h4> +<div class="paragraph"><p><em>OSTC Tools</em> is a Microsoft-based suite of dive download and dive management +tools for the OSTC family of dive computers. <em>OSTC Tools</em> downloads dive +data from the dive computer and stores it as a binary file with file +extension <em>.dive</em> . Subsurface can directly import these files when using +the universal import dialogue. From the dropdown list at the bottom right +select <em>OSTCTools Files (.dive .DIVE)</em>. This makes the <em>OSTC Tools</em> dive +logs visible in the file list panel. Select one or more dive, then click the +<em>Open</em> button. The OSTC dives are shown in the <strong>Dive List</strong> panel.</p></div> +<div class="paragraph"><p>All H&W devices supported by OSTCTools can be imported to <em>Subsurface</em>. This +includes OSTC, OSTC Mk2, OSTC 2N/2C, OSTC3, OSTC Sport, and probably +although untested, Frog, OSTC2 and OSTC CR.</p></div> +<div class="paragraph"><p>Please remember that OSTCTools is <strong>not</strong> a true diving log software, but +rather a useful set of tools for analysis and management of OSTC +devices. Only raw dive computer data will be imported to <em>Subsurface</em>; you +have to manually complete the rest of the data you want (buddies, equipment, +notes, etc).</p></div> +</div> +<div class="sect3"> +<h4 id="_importing_from_mares_dive_organizer_v2_1">5.3.2. Importing from Mares Dive Organizer V2.1</h4> +<div class="paragraph"><p>Since Mares uses 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 gateway to extract the dive log +information.</p></div> +<div class="olist arabic"><ol class="arabic"> +<li> +<p> +Export the dive log data from Mares Dive Organizer to your desktop, using a + <em>.sdf</em> file name extension. Refer to <a href="#Mares_Export">Appendix C</a> for more + information. +</p> +</li> +<li> +<p> +Data should then be imported into <em>www.divelogs.de</em>. You will first need to + create a user account in <em>www.divelogs.de</em>. Log into that web site, then + select <em>Import Logbook → Dive Organizer from the menu on the left hand + side. The instructions must be carefully followed to transfer the dive + information (in _.sdf</em> format) from the Dive Organizer database to + <em>www.divelogs.de</em>. +</p> +</li> +<li> +<p> +Finally, import the dives from <em>divelogs.de</em> to <em>Subsurface</em>, using the + instructions below. +</p> +</li> +</ol></div> +</div> +<div class="sect3"> +<h4 id="S_ImportingDivelogsDe">5.3.3. Importing dives from <strong>divelogs.de</strong></h4> +<div class="paragraph"><p>Importing dive information from <em>divelogs.de</em> is simple, using a single +dialogue box. The <em>Import → Import from Divelogs.de</em> option should be +selected from the Main Menu. This brings up a dialogue box (see image <strong>A</strong> +below). Enter a user-ID and password for <em>divelogs.de</em> 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 shown (see image <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">5.3.4. Importer des données au format CSV</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). The <em>CSV</em> format is a universal simplified format that +allows easy information exchange between different computers or software +packages. For an introduction to CSV-formatted files see <a href="#S_CSV_Intro">A +Diver’s Introduction To CSV Files</a>. <em>Subsurface</em> dive logs can also be +exported in <em>CSV</em> format to other software that reads this format. See +<a href="#S_Appendix_D">APPENDIX D: Exporting a spreadsheet to CSV format</a> for +information that may be helpful for importing spreadsheet-based data into +<em>Subsurface</em>.</p></div> +<div class="sect4"> +<h5 id="S_ImportingCSVDives">Importer les plongées au format CSV à partir des ordinateurs de plongées ou d’autres logiciels de carnet de plongée</h5> +<div class="paragraph"><p>You can view a <em>CSV</em> file by using an ordinary text editor. It’s normally +organized into a single line that provides the headers (or <em>field names</em> or +<em>column headings</em>) of the data columns, followed by the data, one record per +line.</p></div> +<div class="paragraph"><p>There are two types of <em>CSV</em> dive logs that can be imported into +<em>Subsurface</em>:</p></div> +<div class="olist arabic"><ol class="arabic"> +<li> +<p> +<em>CSV dive details</em>: This dive log format contains similar information to + that of a typical written dive log, e.g. dive date and time, dive depth, + dive duration, names of buddy and divemaster and information about cylinder + pressures before and after the dive, as well as comments about the dive. All + the data for a single dive go on a single line of text, following the order + of the column headings. +</p> +</li> +<li> +<p> +<em>CSV dive profile</em>: This dive log format includes much more information + about a single dive. For instance there may be information at 30-second + intervals, indicating depth, water temperature, and cylinder pressure at + that moment in time. Each line contains the information for a single instant + in time during the dive, 30 seconds after that of the previous instant. Many + lines are required to complete the depth profile information for a single + dive. This is a common export format used by closed-circuit rebreather (CCR) + dive equipment and many software packages that handle dive computer data + and/or dive logs. +</p> +</li> +</ol></div> +<div class="paragraph"><p>Before being able to import the <em>CSV</em> data to <em>Subsurface</em> <strong>you needs to +know a few things about the data being imported</strong>:</p></div> +<div class="olist loweralpha"><ol class="loweralpha"> +<li> +<p> +Which character separates the different columns within a single line of + data? This field separator should be either a comma (,) a semicolon (;) or a + TAB character. This can be determined by opening the file with a text + editor. If it is comma-delimited or semicolon-delimited, the comma or + semicolon characters between the values are clearly visible. If these are + not evident and the numbers are aligned in columns, the file is probably + TAB-delimited (i.e. it uses a TAB as a field separator). +</p> +</li> +<li> +<p> +Which data columns need to be imported into <em>Subsurface</em>? Is it a <em>CSV dive + details</em> file or a <em>CSV dive profile</em> file? Open the file using a text + editor and note the titles of the columns to be imported and their column + positions. +</p> +</li> +<li> +<p> +Is the numeric information (e.g. dive depth) in metric or in imperial units? +</p> +</li> +</ol></div> +<div class="paragraph"><p>With this information, importing the data into <em>Subsurface</em> is +straightforward. Select <em>Import → Import Log Files</em> from the main menu. In +the resulting file selection menu, select <em>CSV files</em> (towards the bottom +right). This shows all .CSV files in the selected directory. Select the file +that needs to be imported. A configuration panel appears as depicted below:</p></div> +<div class="imageblock" style="text-align:center;"> +<div class="content"> +<img src="images/csv_import1_f20.jpg" alt="FIGURE: CSV download dialogue 1" /> +</div> +</div> +<div class="paragraph"><p>At the top left, there is a dropdown list containing pre- configured +settings for common dive computers and software packages. + If the <em>CSV</em> file being imported originated from any of +these pre-configured items, select it. Otherwise use the <em>Manual Import</em> +option. The configuration panel also has dropdown lists for the specification of the appropriate +field separator (Tab, comma or semicolon), the date format used in the <em>CSV</em> file, +the time units (seconds, minutes or minutes:seconds), as well as the unit system +(metric or imperial). Selecting the appropriate options among these is critical for +the successful data import.</p></div> +<div class="paragraph"><p>Complete this by ensuring that all the data columns have the appropriate +column headings. The top blue row of the data table contains the column +headings found in the <em>CSV</em> data file. The blue row of balloons immediately +above these contains the names understood by <em>Subsurface</em>. These balloons +can be moved using a drag-and-drop action. For instance, <em>Subsurface</em> +expects the column heading for Dive number (" # ") to be "Dive # ". If the +column heading that <em>Subsurface</em> expects is not in the blue row, drag the +appropriate balloon from the upper area and drop it in the appropriate blue +cell at the top of the table. To indicate the correct column for "Dive #", +drag the ballooned item labelled "Dive # " and drop it in the blue cell +immediately above the white cell containing " # ". This is depicted in the +image below.</p></div> +<div class="imageblock" style="text-align:center;"> +<div class="content"> +<img src="images/csv_import2_f20.jpg" alt="FIGURE: CSV download dialogue 2" /> +</div> +</div> +<div class="paragraph"><p>Continue in this way to ensure all the column headings in the blue row of +cells correspond to the headings listed in the top part of the dialogue. +When finished, select the <em>OK</em> button on the bottom right of the dialogue. +The data from the <em>CSV</em> file are imported and shown in the <strong>Dive List</strong> +panel.</p></div> +<div class="sidebarblock" id="S_CSV_Intro"> +<div class="content"> +<div class="paragraph"><p><strong>A Diver’s Introduction to <em>CSV</em> Files</strong></p></div> +<div class="admonitionblock"> +<table><tr> +<td class="icon"> +<img src="images/icons/important.png" alt="Important" /> +</td> +<td class="content"><em>CSV</em> is an abbreviation for a data file format: <em>Comma-Separated +Values</em>. It is a file format that lets you view or edit information using a +text editor like Notepad (Windows), gedit (Linux) or TextWrangler +(OS/X). There are two main advantages of the <em>CSV</em> format. First, the data +are easily editable as text without any proprietary software. Second, all +information is human-readable, not obscured by any custom or proprietary +attributes that proprietary software inserts into files. Because of its +simplicity the <em>CSV</em> 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>, <em>CSV</em> files can also be used to +import information from other sources like spreadsheet-based dive logs and +some dive computers.</td> +</tr></table> +</div> +<div class="paragraph"><p><em>CSV</em> files can be created or edited with a normal text editor. The most +important attribute of a <em>CSV</em> 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 <em>CSV</em> file. <em>CSV</em> files are normally +organized 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>The above 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 <em>CSV</em> 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>When a <em>CSV</em> file is selected for import, <em>Subsurface</em> displays the column +headers as well as some of the data in the first few lines of the <em>CSV</em> +file, making it much easier to work with <em>CSV</em> files. <em>CSV</em> files can be +used in many contexts for importing data into a <em>Subsurface</em> dive log. +Knowing a few basic things about the content of the <em>CSV</em> file helps with a +smooth import of the dives into <em>Subsurface</em>.</p></div> +</div></div> +<div class="admonitionblock"> +<table><tr> +<td class="icon"> +<img src="images/icons/important.png" alt="Important" /> +</td> +<td class="content">But, the <em>CSV</em> import has a couple of caveats. Avoid some special characters +like ampersand (&), less than (<), greater than (>) and double quotes (") as +part of the numbers or text within a cell. The file should use UTF-8 +character set, if using non-ASCII characters. Also the size of the <em>CSV</em> +file might cause problems. Importing 100 dives at a time (<em>CSV dive +details</em>) works, but larger files might exceed the limits of the parser +used. When encountering problems with <em>CSV</em> imports, first try with a +smaller file to make sure everything works.</td> +</tr></table> +</div> +</div> +</div> +</div> +<div class="sect2"> +<h3 id="S_Companion">5.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 <em>Android device</em> or +<a href="#S_iphone"><em>iPhone</em></a> with GPS, the coordinates +for the diving +location can be automatically passed to the <em>Subsurface</em> dive log. The Companion App +stores dive locations on a dedicated Internet server. <em>Subsurface</em> can collect +the locations from the server. +To do this:</p></div> +<div class="sect3"> +<h4 id="_create_a_companion_app_account">5.4.1. Create a Companion App account</h4> +<div class="ulist"><ul> +<li> +<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 giving you access to the file server and + Companion App capabilities. +</p> +</li> +<li> +<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&fdid=org.subsurface">F-Droid</a>. +</p> +</li> +</ul></div> +</div> +<div class="sect3"> +<h4 id="_using_the_subsurface_companion_app_on_an_android_smartphone">5.4.2. Using the Subsurface companion app on an Android smartphone</h4> +<div class="paragraph"><p>On first use the app has three options:</p></div> +<div class="ulist"><ul> +<li> +<p> +<em>Create a new account.</em> Equivalent to registering in the <em>Subsurface</em> + companion page using an Internet browser. You can request a <strong>DIVERID</strong> using + this option, but it’s supplied via email and followed up by interaction with + the <a href="http://api.hohndel.org/login/"><em>Subsurface companion web page</em></a> to + activate the account. +</p> +</li> +<li> +<p> +<em>Retrieve an account.</em> If users forget their <strong>DIVERID</strong> they will receive an + email to recover the number. +</p> +</li> +<li> +<p> +<em>Use an existing account.</em> Users are prompted for their <strong>DIVERID</strong>. The app + saves this <strong>DIVERID</strong> and doesn’t ask for it again unless you use the + <em>Disconnect</em> menu option (see below). +</p> +</li> +</ul></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, by selecting <em>File → Preferences → +Defaults</em> from the main menu in <em>Subsurface</em> itself. This helps +synchronization 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 you are 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 shows +with 3 options:</p></div> +<div class="ulist"><ul> +<li> +<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> +</li> +<li> +<p> +Use Map: This option lets you fix a position by searching a world map. A + world map is shown (see <strong>B</strong> below) on which you can show the desired + position with a <em>long press</em> on the touch sensitive screen (if the marked + location is wrong, simply choose a new location) and select the check + symbol in the upper right. A dialog is shown letting you enter the name of + the dive location and the date and time of the dive (see <strong>C</strong> below). In + order to import this dive location in <em>Subsurface</em> you should set the time + to agree with the time of that dive on the dive computer. +</p> +</li> +</ul></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="ulist"><ul> +<li> +<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 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> +</li> +</ul></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 showing they need to be uploaded to the +server. You can select individual dive locations from the list. A selected +location has a check mark in the selection box on the left. Group operations +(like <em>Delete</em> or <em>Send</em>) are performed on several selected locations.</p></div> +<div class="paragraph"><p>Dive locations in this list can be viewed in two ways: a list of locations +or a map showing them. 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 you select 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 you select 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> +</ul></div> +<div class="paragraph"><p>Maps: Display a map showing the dive location. After editing and saving a +dive location (see <strong>C</strong> above), 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 +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">Be careful! 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> +<li> +<p> +<em>User ID.</em> The DIVERID obtained by registering as described above. The + easiest way to get it is to copy and paste from the confirmation email or + just type it in. +===== Synchronisation +</p> +</li> +<li> +<p> +<em>Synchronize on startup</em>. If selected, dive locations in the Android device + and those on the web service synchronize each time the app is started. +</p> +</li> +<li> +<p> +<em>Upload new dives.</em> If selected, each time the user adds a dive location it + is automatically sent to the server. +</p> +</li> +</ul></div> +</div> +<div class="sect4"> +<h5 id="_background_service">Background service</h5> +<div class="paragraph"><p>Instead of entering an unique dive location, you can leave the service +running in the background of your Android device, allowing a continuous +collection of GPS locations.</p></div> +<div class="paragraph"><p>The settings below define the behavior of the service:</p></div> +<div class="ulist"><ul> +<li> +<p> +<em>Min duration.</em> In minutes. The app will try to get a location every X + minutes until stopped by the user. +</p> +</li> +<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 diver 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 50 m 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 diver is not moving, only one location is +saved. If the diver 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>Starts 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 admittedly a badly named option that disconnects the app from the +server. It resets 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 your 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="S_iphone">5.4.3. Using the Subsurface companion app on an <em>iPhone</em> to record dive locations</h4> +<div class="paragraph"><p>The iPhone interface is quite simple. Type the user ID (obtained during +registration) into the space reserved for it, then select "Dive in" (see +left part of the image below) and start collecting dive location +information.</p></div> +<div class="imageblock" style="text-align:center;"> +<div class="content"> +<img src="images/iphone.jpg" alt="FIGURE: Using iPhone companion application" width="640" /> +</div> +</div> +<div class="paragraph"><p>Dives can be added automatically or manually. In manual mode, a dive +location or waypoint is added to the GPS input stream. In automatic mode, a +continuous path of GPS locations is created from which, after import, +Subsurface can select the appropriate GPS locations based on the times of +dives. The default mode for the <em>iphone</em> is automatic. When adding a dive, +the location service is started automatically and a red bar appears at the +bottom of the screen. After the dive, click on the red bar to end the +location service. While the location service is running you can only add +dives manually.</p></div> +<div class="paragraph"><p>You can edit the site name afterwards by selecting the dive from the dive +list and clicking on the site name. There are no other editable fields. The +dive list is automatically uploaded from the iPhone to the web +service. There isn’t an option to trigger upload manually.</p></div> +</div> +<div class="sect3"> +<h4 id="_downloading_dive_locations_to_the_em_subsurface_em_divelog">5.4.4. 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 → 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 start 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, you can +update the locations of the newly entered or uploaded dives in +<em>Subsurface</em>. That applies the coordinates and names entered on the app to +all the new dives that match the date-times of the uploaded GPS +localities. If you have 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 depends on agreeing date-time information +between the two devices. Although <em>Subsurface</em> has a wide range tolerance, +it may not be able to identify the appropriate dive if there’s a large +difference between the time in the dive computer and that of the Android +device. That results 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). <em>Subsurface</em> may also 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 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="ulist"><ul> +<li> +<p> +<em>Background service</em> may fill the location list with unnecessary locations + that don’t correspond to the exact dive point but do correspond to the + boat’s route. + Right now, these locations are difficult to delete from the server. In some + situations it + is better 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 you want to keep the + location list clear to see dives in the web service map display (see above). +</p> +</li> +<li> +<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> +</li> +</ul></div> +</div> +</div> +<div class="sect2"> +<h3 id="S_LoadImage">5.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. To match each photograph with a specific dive, <em>Subsurface</em> +lets you 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_synchronizing_between_dive_computer_and_camera">5.5.1. Loading photos and synchronizing 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 up the time synchronization dialog, shown below. But be aware +that the time synchronization 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 synchronize, 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> synchronizes in three ways:</p></div> +<div class="ulist"><ul> +<li> +<p> +<strong>Pro-actively</strong>: Before the dive, ensure synchronization of the dive computer time settings with + the time settings of the camera by changing the date-time settings on one or both of these devices. +</p> +</li> +<li> +<p> +<strong>Manually</strong>: If you wrote down the exact camera time at the start of a dive, the + difference in time between the two devices can be determined. As long as the device + settings for time has not been changed in either device, you could write down the times of + both devices after the dive or even at the end of the day. You 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>, shown 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 synchronization is done. +</p> +</li> +</ul></div> +<div class="imageblock" style="text-align:center;"> +<div class="content"> +<img src="images/LoadImage3b_f20.jpg" alt="FIGURE: Synchronization dialog" /> +</div> +</div> +<div class="ulist"><ul> +<li> +<p> +<strong>By photograph</strong>: There is a very slick way of synchronizing. If you take a + photograph of the face of the dive computer showing the time, then <em>Subsurface</em> can get + the exact time the photograph was taken, using the metadata the camera stores within + each photo. To do this, use the bottom half of the <em>Time shift</em> dialog. If you use + the bottom part, the top part of the dialog is ignored. Click on + the horizontal bar called "<em>Select image of dive computer showing time</em>. This brings up + a file browser letting you select the photograph of the dive computer time. 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 it 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 it can synchronize. + Image <strong>B</strong> above shows a photograph of the face of the dive computer and with the date-time tool set to the + date-time. +</p> +</li> +</ul></div> +<div class="paragraph"><p>If the timestamp of a photograph is more than 30 minutes before or after the +dive, it is not placed on the dive profile.</p></div> +</div> +<div class="sect3"> +<h4 id="_viewing_the_photos">5.5.2. Viewing the photos</h4> +<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>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. To view the photos on the + dive profile, activate the <em>show-photos</em> button in the tool bar to the left + of the dive profile: +</p> +</li> +</ul></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>This results in a profile display as in the image below:</p></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 you hover the mouse over any of the photo icons, 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 added photographs. (see +the image below). Note that the thumbnail has a small dustbin icon in the +bottom right hand corner (see image above). Selecting the dustbin removes +the image from the dive. Be careful 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">5.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>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 show +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">5.5.4. Photos on an external hard disk</h4> +<div class="paragraph"><p>Most underwater photographers store photos on an external drive. If such a +drive can be mapped by the operating system (almost always the case) the +photos can be directly accessed by <em>Subsurface</em>. This eases 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 synchronization (see text above) is used. 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. If the external drive with the photos +is re-connected, the photos can be seen in the normal way.</p></div> +</div> +<div class="sect3"> +<h4 id="S_FindMovedImages">5.5.5. Moving photographs among directories, hard disks or computers</h4> +<div class="paragraph"><p>After a photograph has been loaded into <em>Subsurface</em> and associated with a specific dive, the directory + where the photo lies is stored, letting <em>Subsurface</em> find the photograph when the dive is + opened again. If the photo or the whole photo collection is moved to another drive or to a different + machine, the directory structure will be different to that of the original uploaded + photo. When this happens, <em>Subsurface</em> looks for the photos at their original location before they were moved, + cannot find them and cannot display them. Because after moving photos, large numbers of photos + may need to be deleted and re-imported from the new location, <em>Subsurface</em> has a mechanism that eases the + process of updating the directory information for each photo: automatic updates using fingerprints.</p></div> +<div class="paragraph"><p>When a photo is loaded into <em>Subsurface</em>, a fingerprint for the image is calculated and stored with the + other reference information for that photo. After moving a photo collection (that has already been loaded + into <em>Subsurface</em>) to a different directory, disk or computer, <em>Subsurface</em> can:</p></div> +<div class="paragraph"><p>look through a particular directory (and all its subdirectories recursively) +where photos have been moved to, +- calculate fingerprints for all photos in this directory, and</p></div> +<div class="ulist"><ul> +<li> +<p> +if there is a match between a calculated fingerprint and the one originally + calculated when a photo was + loaded into <em>Subsurface</em> (even if the original file name has changed), + automatically update the directory information so that <em>Subsurface</em> can find + the photo in the new moved directory. +</p> +</li> +</ul></div> +<div class="paragraph"><p>This is done by selecting from the Main Menu: <em>File → Find moved images</em>. This brings up a window within + which the NEW directory of the photos needs to be specified. Select the appropriate directory and click + the <em>Scan</em> button towards the bottom right of the panel. The process may require several minutes to + complete, after which <em>Subsurface</em> will show the appropriate photographs when a particular dive is opened.</p></div> +<div class="sidebarblock" id="Image_fingerprint_upgrade"> +<div class="content"> +<div class="paragraph"><p><strong>Upgrading existing photo collections without fingerprints</strong></p></div> +<div class="admonitionblock"> +<table><tr> +<td class="icon"> +<img src="images/icons/important.png" alt="Important" /> +</td> +<td class="content"><em>Subsurface</em> automatically calculates fingerprints for all images that it +can access. When manipulating images, be sure all the images associated +with the dive log can be accessed by <em>Subsurface</em>.</td> +</tr></table> +</div> +<div class="paragraph"><p><em>Subsurface</em> automatically checks and, if necessary, updates the +fingerprints associated with a single dive if: +- The images associated with that dive are visible as thumbnails on the <strong>Dive + Profile</strong>. +- If you edit anything in the <strong>Notes tab</strong> panel and save the edits by + selecting <em>Apply changes</em>.</p></div> +</div></div> +</div> +</div> +<div class="sect2"> +<h3 id="_logging_special_types_of_dives">5.6. Logging special types of dives</h3> +<div class="sect3"> +<h4 id="S_MulticylinderDives">5.6.1. Multicylinder dives</h4> +<div class="paragraph"><p><em>Subsurface</em> easily handles dives involving more than one +cylinder. Multi-cylinder diving usually happens (a) if a diver doesn’t have +enough gas for the complete dive in a single cylinder; (b) if a diver needs +more than one gas mixture because of the depth or the decompression needs of +the dive. For this reason multi-cylinder dives are often used by technical +divers who dive deep or long. As far as <em>Subsurface</em> is concerned, there are +only two types of information that need to be provided:</p></div> +<div class="ulist"><ul> +<li> +<p> +<strong>Describe the cylinders used during the dive</strong> This is performed in the <strong>Equipment tab</strong> of + the <strong>Info</strong> panel, as <a href="#cylinder_definitions">described above</a>. Enter the cylinders one by one, + specifying each’s characteristics and the gas composition within it. +</p> +</li> +<li> +<p> +<strong>Record the times at which the switch from one cylinder to another was done:</strong> This is information + tracked by some dive computers (provided the diver indicated these changes to the dive computer + by pressing specific buttons). If the dive computer does not provide the information, the diver has to + record these changes using a different method, e.g. writing it on a slate. +</p> +</li> +<li> +<p> +<strong>Record the cylinder changes on the dive profile</strong>: If the latter option + was followed, the diver needs to indicate the gas change event by right-clicking at the appropriate point + in time on the <strong>Dive Profile</strong> panel and indicating the cylinder to which the change was made. After + right-clicking, follow the context menu to "Add gas change" and select the appropriate cylinder from + those defined during the first step, above (see image below). If the + <strong>tank bar</strong> button in the toolbar has been activated, the cylinder switches are also indicated in the + tank bar. +</p> +</li> +</ul></div> +<div class="paragraph"><p>When this is complete, <em>Subsurface</em> indicates the appropriate use of +cylinders in the dive profile. Below is a multi-cylinder dive, starting off +with EAN28, then changing cylinders to EAN50 after 26 minutes for +decompression.</p></div> +<div class="imageblock" style="text-align:center;"> +<div class="content"> +<img src="images/multicylinder_dive.jpg" alt="FIGURE: Multicylinder profile" /> +</div> +</div> +</div> +<div class="sect3"> +<h4 id="_sidemount_dives">5.6.2. Sidemount dives</h4> +<div class="paragraph"><p>Sidemount diving is just another form of multi-cylinder diving, often with +both or all cylinders having the same gas mixture. Although it’s a popular +configuration for cave divers, Sidemount diving can be done by recreational +divers who’ve completed the appropriate training. sidemount dive logging +involves three steps, exactly as with multi-cylinder dives above:</p></div> +<div class="ulist"><ul> +<li> +<p> +<strong>During the dive, record cylinder switch events</strong>. Since sidemount diving normally involves two + cylinders with air or with the same gas mixture, <em>Subsurface</em> distinguishes between these different + cylinders. In contrast, many dive computers that allow gas switching only distinguish between different + <em>gases</em> used, not among different <em>cylinders</em> used. This means when sidemount dives are downloaded + from these dive computers, the switching event between cylinders with the same gas is not downloaded. This may mean + that a diver may have to keep a written log of cylinder switch times using a slate, or (if the dive computer + has the capability) marking each cylinder switch with a bookmark that can be retrieved later. Returning + from a dive with the times of cylinder changes is the only tricky part of logging sidemount dives. +</p> +</li> +<li> +<p> +<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>Info Panel</strong> (see + image below where two 12 litre cylinder were used). +</p> +</li> +<li> +<p> +<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 shown on the dive profile. + Cylinder changes are recorded by right-clicking at the appropriate point on the dive profile, 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 shown 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 shown 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 in the image below. +</p> +</li> +</ul></div> +<div class="imageblock" style="text-align:center;"> +<div class="content"> +<img src="images/sidemount1.jpg" alt="FIGURE: Sidemount profile" /> +</div> +</div> +<div class="paragraph"><p>This section gives an example of the versatility of <em>Subsurface</em> as a dive +logging tool.</p></div> +</div> +<div class="sect3"> +<h4 id="S_sSCR_dives">5.6.3. Semi-closed circuit rebreather (SCR) dives</h4> +<div class="admonitionblock"> +<table><tr> +<td class="icon"> +<img src="images/halcyon_RB80.jpg" alt="Note" /> +</td> +<td class="content">Passive semi-closed rebreathers (pSCR) are a technical advance in diving +equipment that recirculates the breathing gas a diver uses, while removing +carbon dioxide from the exhaled gas. While a small amount (typically a +tenth) of the exhaled breathing gas is released into the water, a small +amount of fresh gas is released from the back gas cylinder (typically +containing nitrox). A diver using a single cylinder of breathing gas can +therefore dive for much longer periods than using a recreational +open-circuit configuration. With pSCR equipment, a very small amount of +breathing gas is released every time the diver inhales. With active SCR +(aSCR) equipment, in contrast, a small amount of breathing gas is released +continuously from the back cylinder.</td> +</tr></table> +</div> +<div class="paragraph"><p>To log pSCR dives, no special procedures are required. Use the normal steps +outlined above:</p></div> +<div class="ulist"><ul> +<li> +<p> +Select pSCR in the <em>Dive Mode</em> dropdown list on the <strong>Info</strong> panel. +</p> +</li> +<li> +<p> +pSCR diving often involves gas changes, requiring an additional cylinder. + Define all the appropriate cylinders as described above and indicate the + cylinder/gas changes as described above in the section on + <a href="#S_MulticylinderDives">multicylinder dives</a>. +</p> +</li> +</ul></div> +<div class="paragraph"><p>If a pSCR <em>Dive Mode</em> has been selected, the dive ceiling for that is +adjusted for the oxygen drop across the mouthpiece, which often requires +longer decompression periods. Below is a dive profile of a pSCR dive using +EAN36 on the back cylinder and oxygen for decompression. Note that this dive +lasted over two hours.</p></div> +<div class="imageblock" style="text-align:center;"> +<div class="content"> +<img src="images/pSCR_profile.jpg" alt="FIGURE: pSCR profile" /> +</div> +</div> +</div> +<div class="sect3"> +<h4 id="S_CCR_dives">5.6.4. Closed circuit rebreather (CCR) dives</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. They also do two things to maintain a breathable oxygen +concentration: +a) remove carbon dioxide from the exhaled gas +regulate the oxygen concentration to remain within safe diving limits. The +CCR interface of <em>Subsurface</em> is currently experimental and under active +development. Subsurface currently supports Poseidon MkVI and APD +Discovery/Evolution dive computers. In contrast to a conventional +recreational 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 it imports dive log data from other digital databases: one dive at +a time.</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 → Import log files</em> to bring up the +<a href="#Unified_import">universal import dialogue</a>. As explained in that +section, the bottom right hand of the import dialogue contains a dropdown +list (labled <em>Filter:</em>) of appropriate devices that currently +include(Poseidon) MkVI or APD log viewer files. Import for other CCR +equipment is under active development. Having selected the appropriate CCR +format and the directory where the original dive logs have been stored from +the CCR dive computer, 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, click the <em>Open</em> button at the bottom right hand of the universal +import dialogue. The selected dive is imported to the <em>Subsurface</em> dive +list.</p></div> +</div> +<div class="sect4"> +<h5 id="_displayed_information_for_a_ccr_dive">Displayed information for a CCR 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 contrast to +recreational equipment (where pO<sub>2</sub> values are calculated based on gas +composition and dive depth), CCR equipment provide actual measurements of +pO<sub>2</sub>, derived from oxygen sensors. In this case the graph for oxygen +partial pressure should be fairly flat, reflecting the setpoint settings +during the dive. The mean pO<sub>2</sub> is NOT the mean oxygen partial pressure as +given by the CCR equipment, but a value calculated by <em>Subsurface</em> as +follows:</p></div> +<div class="ulist"><ul> +<li> +<p> +For TWO O<sub>2</sub> sensors the mean value of the two sensors are given. +</p> +</li> +<li> +<p> +For THREE-sensor systems (e.g. APD), the mean value is also used. However + differences of more than 0,1 bar in the simultaneous readings of different + sensors are treated as false. If one of the three sensors provides false + data, it is ignored. +</p> +</li> +<li> +<p> +If no sensor data are available, the pO<sub>2</sub> value is assumed to be equal to + the setpoint. +</p> +</li> +</ul></div> +<div class="paragraph"><p>The mean pO<sub>2</sub> of the sensors is indicated with a green line,</p></div> +<div class="paragraph"><p>The oxygen setpoint values as well as the readings from the individual +oxygen sensors can be shown. The display of additional CCR information is +turned on by checking the appropriate boxes in the <em>Preferences</em> panel +(accessible by selecting <a href="#S_CCR_options"><em>File → Preferences → +Graph</em></a>). This part of the <em>Preferences</em> panel is shown in the image below, +representing two checkboxes that modify the display of pO<sub>2</sub> when the +appropriate toolbar button on the Dive Profile has been checked.</p></div> +<div class="imageblock" style="text-align:center;"> +<div class="content"> +<img src="images/CCR_preferences_f20.jpg" alt="FIGURE: CCR preferences panel" /> +</div> +</div> +<div class="paragraph"><p>Checking any of these boxes allows the display of additional oxygen-related +information whenever the pO<sub>2</sub> toolbar button on the <em>Profile</em> panel is +activated. The first checkbox allows the display of setpoint +information. This is a red line superimposed on the green oxygen partial +pressure graph and allows a comparison of the mean measured oxygen partial +pressure and the setpoint values, as shown below.</p></div> +<div class="imageblock" style="text-align:center;"> +<div class="content"> +<img src="images/CCR_setpoint_f20.jpg" alt="FIGURE: CCR setpoint and po2 graph" /> +</div> +</div> +<div class="paragraph"><p>The second checkbox allows the display of the data from each individual +oxygen sensor of the CCR equipment. The data for each sensor is colour-coded +as follows:</p></div> +<div class="ulist"><ul> +<li> +<p> +Sensor 1: grey +</p> +</li> +<li> +<p> +Sensor 2: blue +</p> +</li> +<li> +<p> +Sensor 3: brown +</p> +</li> +</ul></div> +<div class="paragraph"><p>The mean oxygen pO<sub>2</sub> is indicated by the green line. This allows the direct +comparison of data from each of the oxygen sensors, useful for detecting +abnormally low or erratic readings from a particular sensor.</p></div> +<div class="imageblock" style="text-align:center;"> +<div class="content"> +<img src="images/CCR_sensor_data_f20.jpg" alt="FIGURE: CCR sensor data graph" /> +</div> +</div> +<div class="paragraph"><p>The setpoint data can be overlaid on the oxygen sensor data by activating +both of the above check boxes. Partial pressures for nitrogen (and helium, +if applicable) are shown in the usual way as for open circuit dives.</p></div> +<div class="paragraph"><p><em>Events</em>: Several events are logged, e.g. switching the mouthpiece to open +circuit. These events are indicated by yellow triangles and, if one hovers +over a triangle, a description of that event is given as the bottom line in +the <a href="#S_InfoBox">Information Box</a>.</p></div> +<div class="paragraph"><p><em>Cylinder pressures</em>: Some CCR dive computers like the Poseidon MkVI record +the pressures of the oxygen and diluent cylinders. The pressures of these +two cylinders are shown as green lines overlapping the depth profile. In +addition, start and end pressures for both oxygen and diluent cylinders are +shown in the <em>Equipment Tab</em>. Below is a dive profile for a CCR dive, +including an overlay of setpoint and oxygen sensor data, as well as the +cylinder pressure data. In this case there is agreement from the readings of +the two oxygen sensors.</p></div> +<div class="imageblock" style="text-align:center;"> +<div class="content"> +<img src="images/CCR_dive_profile_f22.jpg" alt="FIGURE: CCR dive profile" /> +</div> +</div> +<div class="paragraph"><p><em>Equipment-specific information</em>: Equipment-specific information gathered by +<em>Subsurface</em> is shown in the <a href="#S_ExtraDataTab">Extra data tab</a>. This may +include setup information or metadata about the dive.</p></div> +<div class="paragraph"><p>The deco ceiling calculated by Subsurface is not very accurate because the +precise pressure of nitrogen in the loop can usually not be determined from +the dive log imported from the CCR equipment. Many CCR dive computers, +however, report an internally-calculated deco ceiling that is reported in +the dive log, reflecting a more accurate assessment. The display of this +ceiling is activated by clicking the appropriate button to the left of the +dive profile:</p></div> +<div class="imageblock"> +<div class="content"> +<img src="images/icons/cceiling.jpg" alt="DC ceiling icon" /> +</div> +</div> +<div class="paragraph"><p>The default color of the computer-generated deco ceiling is white. This can +be set to red by checking the appropriate check box after selecting <em>File → +Preferences → Graph</em>. Below is a dive profile indicating the dive +computer-generated deco ceiling:</p></div> +<div class="imageblock" style="text-align:center;"> +<div class="content"> +<img src="images/CCR_dive_ceilingF22.jpg" alt="FIGURE: CCR computer-generated deco ceiling" /> +</div> +</div> +<div class="paragraph"><p>More equipment-specific information for downloading CCR dive logs for +Poseidon MkVI and APD equipment can be found in +<a href="#_appendix_b_dive_computer_specific_information_for_importing_dive_information">Appendix +B</a>.</p></div> +</div> +</div> +</div> +</div> +</div> +<div class="sect1"> +<h2 id="_obtaining_more_information_about_dives_entered_into_the_logbook">6. Obtaining more information about dives entered into the logbook</h2> +<div class="sectionbody"> +<div class="sect2"> +<h3 id="_the_strong_info_strong_tab_for_individual_dives">6.1. The <strong>Info</strong> tab (for individual dives)</h3> +<div class="paragraph"><p>The 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 F</a> for more information.</td> +</tr></table> +</div> +</div> +<div class="sect2"> +<h3 id="S_ExtraDataTab">6.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">6.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 for 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">6.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 lets you control 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 +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 colors:</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>Color</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">> 30</p></td> +<td align="left" valign="top"><p class="table">> 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">< 1.5</p></td> +<td align="left" valign="top"><p class="table">< 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. So users should see the depth of the deepest point and other +peaks. Mean depth is plotted as a grey line, indicating mean dive depth up +to a particular moment during the dive.</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 increases the size of the dive profile to fill the area of +the panel.</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 O<sub>2</sub>, +N<sub>2</sub>, 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, +nitrogen in black, and 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 shown 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 important 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. Like the depth graph, the slope of the tank pressure gives you +information about the momentary SAC rate (Surface Air Consumption) when +using an air integrated dive computer. Here the color coding is not +relative to some absolute values but relative to the average normalized 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 easily recognizable; +something free divers won’t care about. +<span class="image"> +<img src=":images/MeasuringBar.png" alt="FIGURE: Measuring Bar" /> +</span></p></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 you +wish 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 +shows 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 occur 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 none of the Suunto dive computers make +these 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’s 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’s 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 because <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 a specific deco stop. This feature lets dive +computers 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 colored bar at the bottom of the <strong>Dive Profile</strong>. In general +oxygen is represented by a green bar, nitrogen a yellow bar and helium 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 doing planned decompression diving, efficient rates of offgassing 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 contrast, 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, at 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">6.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 lets you create +Bookmarks, 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, with the time of the event set by +where the mouse cursor was when the right mouse button was first clicked to +bring up the menu. Gas Change events involve a selection of which gas is +being switched TO. The list of choices is based on the available gases +defined in the <strong>Equipment</strong> Tab. Setpoint change events open a dialog letting +you choose the next setpoint value. As in the planner, a setpoint value of +zero shows the diver is breathing from an open circuit system while any +non-zero value shows 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="S_InfoBox">6.6. The <strong>Information Box</strong></h3> +<div class="paragraph"><p>The Information box displays a large range of information about 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>When 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 shown 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). Moving the cursor +horizontally lets the Information Box 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 some statistics, shown 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 if a maximum pO<sub>2</sub> of 1.4 is specified in the +<strong>Preferences</strong> section (select <em>File</em> → Preferences → Graph_ and edit the +text box <em>Max pO<sub>2</sub> when showing MOD</em>. Below the MOD there is a markedly +increased risk of exposure to the dangers of 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 either 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 a diver 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. TTS is calculated assuming an ascent +surface air consumption (SAC) for the gas currently used. Even if the +profile contains several gas switches, TTS at a specific moment during the +dive is calculated using the current gas. TTS longer than 2 hours is not +accurately calculated and Subsurface only indicates <em>TTS > 2h</em>.</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-normalized +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 +the respiratory rates of different dives can be compared. The units for SAC +is liters/min or cubic 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 important to divers breathe 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">6.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 showing 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>. It is shown 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="ulist"><ul> +<li> +<p> +The light green area indicates the total gas, with the top margin of the + light green area showing 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> +</li> +<li> +<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> +</li> +<li> +<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> +</li> +<li> +<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 + gradient factor shown is an interpolation between the GFLow and GFHigh + values specified in the Graph tab of the <strong>Preferences Panel</strong> of + <strong>Subsurface</strong>. +</p> +</li> +<li> +<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> +</li> +</ul></div> +<div class="paragraph"><p>These five values are shown on the left in the graph above. The way the Gas +Pressure Bar Graph changes during a dive can be seen on the right hand side +of the above figure for a diver using EAN32.</p></div> +<div class="ulist"><ul> +<li> +<p> +Graph <strong>A</strong> indicates the start of a dive with the diver at the surface. The + pressures in all the tissue compartments are still at the equilibrium + pressure because no diving has taken place. +</p> +</li> +<li> +<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, so their gas + pressures are far below the equilibrium gas pressure. +</p> +</li> +<li> +<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> +</li> +<li> +<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 approach 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> +</li> +<li> +<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> +</li> +</ul></div> +</div> +</div> +</div> +</div> +<div class="sect1"> +<h2 id="_organizing_the_logbook_manipulating_groups_of_dives">7. Organizing the logbook (Manipulating groups of dives)</h2> +<div class="sectionbody"> +<div class="sect2"> +<h3 id="_the_dive_list_context_menu">7.1. The Dive List context menu</h3> +<div class="paragraph"><p>Several actions on either a single dive, or a group of dives, can be +performed using the Dive List Context Menu. It is found by selecting either +a single 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 functions described below.</p></div> +<div class="sect3"> +<h4 id="_customizing_the_columns_showed_in_the_strong_dive_list_strong_panel">7.1.1. Customizing the columns 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 be deleted +(reflected by the check symbols) and the list is immediately +updated. Preferences for information shown in the <strong>Dive List</strong> are saved and +used when <em>Subsurface</em> is re-opened.</p></div> +</div> +</div> +<div class="sect2"> +<h3 id="S_Renumber">7.2. Renumbering the dives</h3> +<div class="paragraph"><p>Dives are normally numbered incrementally from non-recent dives (low +sequence numbers) to recent dives (higher sequence numbers). Numbering of +dives is not always consistent. For instance, when non-recent dives are +added, correct 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. So you may need to renumber the dives. Do this by +selecting (from the Main Menu) <em>Log → Renumber</em>. Users are given a choice +of the lowest sequence number to be used. This results in new sequence +numbers (based on date/time) for the dives in the <strong>Dive List</strong> panel.</p></div> +<div class="paragraph"><p>You can also renumber a few selected dives in the dive list. Select the +dives that need renumbering. Right-click on the selected list and use the +Dive List Context Menu to perform the renumbering. A popup window appears +letting the user specify the starting number for the process.</p></div> +</div> +<div class="sect2"> +<h3 id="S_Group">7.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 does this by grouping dives that have +date/times not separated in time by more than two days, so 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 of 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. To group the dives in a dive list, +(from the Main Menu) select <em>Log → 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">7.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>Notes</strong> +panel. Here you 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 used, the general weather and surface conditions +during the trip, etc.). After entering this information, 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 the edited information.</p></div> +</div> +<div class="sect3"> +<h4 id="_viewing_the_dives_during_a_particular_trip">7.3.2. Viewing the dives during a particular trip</h4> +<div class="paragraph"><p>Once the dives have been grouped into trips, you can expand one or more +trips by clicking the arrow-head on the left of each trip title. This +expands the selected trip, revealing individual dives done during the trip.</p></div> +</div> +<div class="sect3"> +<h4 id="_collapsing_or_expanding_dive_information_for_different_trips">7.3.3. Collapsing or expanding dive information for different trips</h4> +<div class="paragraph"><p>After selecting a particular trip in the dive list, the context menu allows +several options to expand or collapse dives within trips. This includes +expanding all trips and collapsing all trips.</p></div> +</div> +<div class="sect3"> +<h4 id="_merging_dives_from_more_than_one_trip_into_a_single_trip">7.3.4. Merging dives from more than one trip into a single trip</h4> +<div class="paragraph"><p>After selecting a trip title, the context menu allows the merging of trips +by either merging the selected trip with the trip below or with the trip +above. (Merge trip with trip below; Merge trip with trip above)</p></div> +</div> +<div class="sect3"> +<h4 id="_splitting_a_single_trip_into_more_than_one_trip">7.3.5. Splitting a single trip into more than one trip</h4> +<div class="paragraph"><p>If a trip includes ten dives, you can split this trip into two trips (trip +1: top 4 dives; trip 2: bottom 6 dives) by selecting and right-clicking the +top four dives. The resulting context menu lets the user create a new trip +by choosing the option <strong>Create new trip above</strong>. The top four dives are then +grouped into a separate trip. The figures below show 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">7.4. Manipulating single dives</h3> +<div class="sect3"> +<h4 id="_delete_a_dive_from_the_dive_log">7.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, 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">7.4.2. Unlink a dive from a trip</h4> +<div class="paragraph"><p>You can unlink dives from the trip to which they belong. 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 or below the trip to which they belonged, depending on the date and +time of the unlinked dive.</p></div> +</div> +<div class="sect3"> +<h4 id="_add_a_dive_to_the_trip_immediately_above">7.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 a separate trip. To do this, select and right-click the dive(s) to +bring up the context menu, and then select <strong>Create new trip above</strong>.</p></div> +</div> +<div class="sect3"> +<h4 id="_shift_the_start_time_of_dive_s">7.4.4. Shift the start time of dive(s)</h4> +<div class="paragraph"><p>Sometimes it’s necessary to adjust the start time of a dive. This may apply +to situations where dives are done in different time zones or when the dive +computer has a wrong time. To do this, select and right-click the dive(s) to +be adjusted. This brings up the context menu on which the <strong>Shift times</strong> +option should be selected. You must then specify the time (in hours and +minutes) by which the dives should be adjusted and click on the option of +whether the time adjustment should be earlier or later.</p></div> +</div> +<div class="sect3"> +<h4 id="_merge_dives_into_a_single_dive">7.4.5. Merge dives into a single dive</h4> +<div class="paragraph"><p>Sometimes a dive is briefly interrupted, for example, if a diver returns to +the surface for a few minutes. That results in two or more dives being +recorded by the dive computer and appearing as different dives in the <strong>Dive +List</strong> panel. You 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>Notes</strong> panel to reflect events or conditions that apply +to the merged dive. The figure below shows the depth profile of two 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 class="sect3"> +<h4 id="_undo_dive_manipulations">7.4.6. Undo dive manipulations</h4> +<div class="paragraph"><p>Important actions on dives or trips, described above, can be undone or +redone. This includes: <em>delete dives</em>, <em>merge dives</em>, <em>renumber dives</em> and +<em>shift dive times</em>. To do this after performing any of these actions, from +the <strong>Main Menu</strong> select <em>Edit</em>. This brings up the possibility to <em>Undo</em> or +<em>Redo</em> an action.</p></div> +</div> +</div> +<div class="sect2"> +<h3 id="S_Filter">7.5. Filtering the dive list</h3> +<div class="paragraph"><p>The dives in the <strong>Dive List</strong> panel can be filtered, so you 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 lets you 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 → 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 (see image below). The +<em>Filter Panel</em> can be reset (i.e. all current filters cleared) by selecting +the <strong>yellow angled arrow</strong>. The <em>Filter Panel</em> may also be minimized by +selecting the <strong>green up-arrow". When minimized, only these three icons are +shown. The panel can be maximized by clicking the same icon that minimized +it. The filter may also be reset and closed by selecting the *red button</strong> +with the white cross.</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 / divemaster), dive site and dive suit. Each of these 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 attributes within that check +list. For instance, typing "<em>ca</em>" in the filter text box above the tags +check list, results in the list being reduced to "<em>cave</em>" and +"<em>cavern</em>". Filtering the check list helps to rapidly find search terms for +filtering the dive list.</p></div> +<div class="paragraph"><p>To activate filtering of the dive list, check at least one check box in one +of the four check lists. The dive list is then shortened to include only the +dives that pertain to the 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">8. Exporting the dive log or parts of the dive log</h2> +<div class="sectionbody"> +<div class="paragraph"><p>There are two ways to export dive information from Subsurface:</p></div> +<div class="ulist"><ul> +<li> +<p> +Exporter les informations de plongée vers <em>Facebook</em> +</p> +</li> +<li> +<p> +<a href="#S_Export_other">Exporter des informations de plongée vers d’autres + destinations ou formats</a> +</p> +</li> +</ul></div> +<div class="sect2"> +<h3 id="S_facebook">8.1. Export des informations de plongée vers <em>Facebook</em></h3> +<div class="paragraph"><p>Export of dives to <em>Facebook</em> is handled differently from other types of +export because a connection to <em>Facebook</em> is required, needing a <em>Facebook</em> +userID and password. If, from the <strong>Main Menu</strong>, you select <em>File → +Preferences → Facebook</em>, a login screen comes up. (image <strong>A</strong> to the left, +below). Provide a <em>Facebook</em> userID and password. Once logged into to +<em>Facebook</em> , the panel in image <strong>B</strong>, below is shown, including a <em>Disconnect +from Facebook</em> button to close the <em>Facebook</em> connection.</p></div> +<div class="imageblock" style="text-align:center;"> +<div class="content"> +<img src="images/facebook1_f20.jpg" alt="Figure: Facebook login" /> +</div> +</div> +<div class="paragraph"><p>From the <em>Subsurface</em> window it’s easy to determine whether <em>Subsurface</em> has +a valid connection to <em>Facebook</em> From the <strong>Main Menu</strong>, select <em>Share on → +Facebook</em> (image <strong>A</strong>, below). Normally, the <em>Facebook</em> option is greyed +out. But if there is a connection to <em>Facebook</em>, this option is active +(i.e. in black color and can be selected).</p></div> +<div class="paragraph"><p>Having established a login to <em>Facebook</em>, transferring a dive profileto a +<em>Facebook</em> timeline is easy. Be sure the dive to be transferred to the +timeline is shown in the <em>Subsurface</em> <strong>Dive Profile</strong> panel. If, from the +<strong>Main Menu</strong>, you select <em>Share on → Facebook</em> (see image <strong>A</strong> below), a +dialogue box is shown, determining the amount of additional information +transferred along with the dive profile (image <strong>B</strong>, below). To transfer a +dive profile to <em>Facebook</em>, the name of a <em>Facebook</em> album is needed. The +checkboxes on the left hand side let you decide how much additional +information should be transferred with the dive profile. This information is +shown in the text box on the right hand side of the panel (image <strong>B</strong>, +below). You can easily edit the message that will be posted with the dive +profile. After specifying the additional information and verifying the +text, select the <em>OK</em> button that triggers the transfer to <em>Facebook</em>. After +the transfer is done, an acknowledgement dialogue appears, indicating it was +successful.</p></div> +<div class="paragraph"><p>Both the album created and the post to your timeline will be marked as +private. In order for friends to be able to see it, change its permissions +from a regular Facebook login either in a browser or a Facebook app.</p></div> +<div class="imageblock" style="text-align:center;"> +<div class="content"> +<img src="images/facebook2_f20.jpg" alt="Figure: Facebook login" /> +</div> +</div> +<div class="paragraph"><p>Si besoin, fermer la connexion <em>Facebook</em> en fermant <em>Subsurface</em> ou en +sélectionnant _Fichier → Préférences → Facebook, à partir du menu +principal et en cliquant sur le bouton approprié dans le panneau des +préférences Facebook.</p></div> +</div> +<div class="sect2"> +<h3 id="S_Export_other">8.2. Export dive information to other destinations or formats</h3> +<div class="paragraph"><p>For non-<em>Facebook exports</em>, the export function can be found by selecting +<em>File → 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_f20.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> +<li> +<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> +</li> +<li> +<p> +<em>Divelogs.de</em>, an Internet-based dive log repository. In order to upload to + <em>Divelogs.de</em>, you need 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 to upload dive log data from <em>Subsurface</em>. +</p> +</li> +<li> +<p> +<em>DiveShare</em> is also a dive log repository on the Internet focusing on + recreational dives. To upload dives, you need a user ID, so registration + with <em>http://scubadiveshare.com</em> is required. +</p> +</li> +<li> +<p> +<em>CSV dive details</em>, that includes the most critical information of the dive + profile. Included information of a dive is: dive number, date, time, buddy, + duration, depth, temperature and pressure: in short, most of the information + that recreational divers enter into handwritten log books. +</p> +</li> +<li> +<p> +<em>CSV dive profile</em>, that includes a large amount of detail for each dive, + including the depth profile, temperature and pressure information of each + dive. +</p> +</li> +<li> +<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. The HTML export cannot be changed or edited. It contains + most of the information recorded in the dive log. However, it does not show + the calculated values in the <strong>Dive Profile</strong> panel, e.g. calculated cylinder + pressure, gas pressures and MOD. The HTML export 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). A typical use of this option is to export + all one’s dives to a smartphone or a tablet where it would serve as a + portable record of dives. That is useful for dive companies that wish to + verify the dive history of a diver, often doing away with the need to carry + an original logbook when doing dives with dive companies. +</p> +</li> +<li> +<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. If you + select any of the dive sites on the map, a summary of the dive is available + in text, as shown in the image below. +</p> +</li> +</ul></div> +<div class="imageblock" style="text-align:center;"> +<div class="content"> +<img src="images/mapview_f20.jpg" alt="Figure: HTML Map export view" /> +</div> +</div> +<div class="ulist"><ul> +<li> +<p> +<em>Image depths</em>, which creates a text file that contains the file names of + all photos or images attached to any of the selected dives in the <em>Dive + List</em>, together with the depth underwater where of each of those photos was + taken. +</p> +</li> +<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 to the HTML exports. +</p> +</li> +<li> +<p> +Export List only: a list of dives only (date, time, depth, duration) will be exported + and the detailed dive information, e.g. dive profile, will not be available. +</p> +</li> +</ul></div> +</li> +<li> +<p> +Under <em>Style Options</em> some style-related options are available like font + size and theme. +</p> +</li> +</ul></div> +<div class="paragraph"><p>Export to other formats can be done through third party facilities, for +instance <em>www.divelogs.de</em>.</p></div> +</div> +</div> +</div> +<div class="sect1"> +<h2 id="S_Cloud_access">9. 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’s own pleasure, but it’s important +information required for admission to training courses or sometimes even +diving sites. The security of the dive log is critical. 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 you can access your dive log from anywhere in the world. For this +reason, facilities such as <em>divelogs.de</em> and <em>Diving Log</em> offer to store +dive log information on the Internet.</p></div> +<div class="paragraph"><p><em>Subsurface</em> includes access to a transparently integrated cloud storage +back end that is available to all Subsurface users. Storing and retrieving a +dive log from the cloud is no more difficult than accessing the dives on the +local hard disk. The only requirement is that you should first register as +a user on the cloud. To use <em>Subsurface cloud storage</em> , follow these +steps:</p></div> +<div class="sect2"> +<h3 id="_create_a_cloud_storage_account">9.1. Create a cloud storage account</h3> +<div class="ulist"><ul> +<li> +<p> +Open the <strong>Network Preferences</strong> by selecting <em>File</em> → <em>Preferences</em> → <em>Network</em>. +</p> +</li> +<li> +<p> +In the section headed <em>Subsurface cloud storage</em>, enter an email address that + <em>Subsurface</em> can use for user registration. +</p> +</li> +<li> +<p> +Enter a novel password that <em>Subsurface</em> will use to store the + dive log in the cloud. +</p> +</li> +<li> +<p> +Click <em>Apply</em> to send the above email address and password to the + (remote) cloud server. The server responds by sending a verification PIN to + the above email address (This is the <strong>only</strong> occasion that <em>Subsurface</em> uses the + email address provided above). The <strong>Network Preferences</strong> dialog now has a new PIN text + box, not visible previously. +</p> +</li> +<li> +<p> +Enter the PIN in the corresponding text box in the <strong>Network Preferences</strong> dialog +(this field is only visible while the server is waiting for email +address confirmation) +</p> +</li> +<li> +<p> +Click <em>Apply</em> again. The <em>Subsurface cloud storage</em> account +will be marked as verified and the <em>Subsurface cloud storage</em> service is initialised for use. +</p> +</li> +</ul></div> +</div> +<div class="sect2"> +<h3 id="_using_em_subsurface_cloud_storage_em">9.2. Using <em>Subsurface cloud storage</em></h3> +<div class="ulist"><ul> +<li> +<p> +Once the cloud storage has been initialized, two new items appear in the + <em>File</em> menu of the main menu system: <em>Open cloud storage</em> and <em>Save to cloud storage</em>. +These options let you load and save data to the <em>Subsurface +cloud storage</em> server. +</p> +</li> +<li> +<p> +In the <em>Defaults Preferences</em> tab, you can select to use the <em>Subsurface cloud +storage</em> data as the default data file by checking the box marked <em>Cloud storage default file</em>. + This means the data from +the <em>Subsurface cloud storage</em> is loaded when <em>Subsurface</em> starts and saved there when <em>Subsurface</em> closes. +</p> +</li> +<li> +<p> +<em>Subsurface</em> keeps a local copy of the data and the cloud facility remains fully +functional even if used while disconnected to the Internet. <em>Subsurface</em> simply synchronizes the +data with the cloud server the next time the program is used while the computer is +connected to the Internet. +</p> +</li> +</ul></div> +</div> +<div class="sect2"> +<h3 id="S_Cloud_storage">9.3. Web access to <em>Subsurface cloud storage</em></h3> +<div class="paragraph"><p>One of the nice side benefits of using <em>Subsurface cloud storage</em> is that +you can also access your dive data from any web browser. Simply open +<a href="https://cloud.subsurface-divelog.org"><em>https://cloud.subsurface-divelog.org</em></a>, +log in with the same email and password, and you can see an HTML export of +the last dive data that was synced to <em>Subsurface cloud storage</em>. The dive +information shown is only the contents of the recorded dive logs, NOT the +calculated values shown in the <strong>Profile</strong> panel, including some cylinder +pressures, deco ceilings and O<sub>2</sub>/He/N<sub>2</sub> partial pressures.</p></div> +</div> +<div class="sect2"> +<h3 id="_other_cloud_services">9.4. Other cloud services</h3> +<div class="paragraph"><p>If you prefers not to use the integrated cloud storage of dive logs (and +don’t need the web access), it’s simple to store dive logs in the cloud +using several of the existing facilities on the Internet. 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 a 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 your 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’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 your <em>Dropbox</em> folder can be accessed seamlessly +from the Internet and can be accessed anywhere 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 you can use <em>Dropbox</em> as a way back up your dive log. To Store +a dive log on <em>Dropbox</em>, select <em>File → 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 <em>Dropbox</em>, select <em>File → 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> +<div class="sect1"> +<h2 id="S_PrintDivelog">10. Printing a dive log</h2> +<div class="sectionbody"> +<div class="paragraph"><p><em>Subsurface</em> provides a simple and flexible way to print a whole dive log or only a few selected dives. + Pre-installed templates or a custom written template can be used to choose where the data are fitted into the page.</p></div> +<div class="paragraph"><p>Some decisions need to be made before printing:</p></div> +<div class="ulist"><ul> +<li> +<p> +Should the whole dive log be printed or only part of it? If only part is + required, select the required dives from the <strong>Dive List</strong> panel. +</p> +</li> +<li> +<p> +If the dive profiles are printed, what gas partial pressure information + should be shown? Select the appropriate toggle-buttons on the button bar to + the left of the <strong>Dive Profile</strong> panel. +</p> +</li> +</ul></div> +<div class="paragraph"><p>If <em>File → Print</em> is selected from the Main menu, the dialogue below (image +<strong>A</strong>) appears. Three specifications are needed to get the desired information +and page layout:</p></div> +<div class="imageblock" style="text-align:center;"> +<div class="content"> +<img src="images/Print1_f22.jpg" alt="FIGURE: Print dialogue" /> +</div> +</div> +<div class="olist arabic"><ol class="arabic"> +<li> +<p> +Under <em>Print type</em> select one of two options: +</p> +<div class="ulist"><ul> +<li> +<p> +<em>Dive list print</em>: Print dives from the <strong>Dive List</strong> panel with profiles and + other information. +</p> +</li> +<li> +<p> +<em>Statistics print</em>: Print yearly statistics of the dives. +</p> +</li> +</ul></div> +</li> +<li> +<p> +Under <em>Print options</em> select: +</p> +<div class="ulist"><ul> +<li> +<p> +Printing only the dives selected from the dive list before activating the + print dialogue by checking the box <em>Print only selected dives</em>. If this + check box is <strong>not</strong> checked ALL dives in the <strong>Dive List</strong> panel are printed. +</p> +</li> +<li> +<p> +Printing in color, done by checking the box with _Print in color. If this + check box is not checked, printing is in black and white. +</p> +</li> +</ul></div> +</li> +</ol></div> +<div class="paragraph"><p>Under <em>Template</em> select a template to be used as the page layout. There are +several choices. (see image <strong>B</strong>, above).</p></div> +<div class="ulist"><ul> +<li> +<p> +<em>Table</em>: This prints a summary table of all dives selected (see below). +</p> +</li> +</ul></div> +<div class="imageblock" style="text-align:center;"> +<div class="content"> +<img src="images/Print_summarylist_f22.jpg" alt="FIGURE: Print summary table" /> +</div> +</div> +<div class="ulist"><ul> +<li> +<p> +<em>Flow layout</em>: Print the text associated with each dive without printing the + dive profiles + of each dive (see below): +</p> +</li> +</ul></div> +<div class="imageblock" style="text-align:center;"> +<div class="content"> +<img src="images/Print_flow_layout_f22.jpg" alt="FIGURE: Print flow layout" /> +</div> +</div> +<div class="ulist"><ul> +<li> +<p> +<em>One Dive</em>: Print one dive per page, also showing the dive profile (see + below) +</p> +</li> +</ul></div> +<div class="imageblock" style="text-align:center;"> +<div class="content"> +<img src="images/print2_f22.jpg" alt="FIGURE: Print one dive / page" /> +</div> +</div> +<div class="ulist"><ul> +<li> +<p> +<em>Two Dives</em>: Print two dives per page, also showing the dive profiles. +</p> +</li> +<li> +<p> +<em>Six Dives</em>: Print six dives per page, also showing the dive profiles. +</p> +</li> +</ul></div> +<div class="paragraph"><p>You can <em>Preview</em> the printed page by selecting the <em>Preview</em> button on the +dialogue (see image <strong>A</strong> at the start of this section). After preview, you +can change the options in the print dialogue, so the layout fits personal +taste.</p></div> +<div class="paragraph"><p>Next, select the <em>Print</em> button (see image <strong>A</strong> at the start of this +section). This activates the regular print dialogue used by the operating +system, letting you choose a printer and set its properties (see image +below):</p></div> +<div class="imageblock" style="text-align:center;"> +<div class="content"> +<img src="images/Print_print_f22.jpg" alt="FIGURE: Print dialog" /> +</div> +</div> +<div class="paragraph"><p>Set the print resolution of the printer to an appropriate value by changing +the printer <em>Properties</em>. Finally, select the <em>Print</em> button to 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 class="sect2"> +<h3 id="_créer_un_modèle_d_8217_impression_personnalisé_avancé">10.1. Créer un modèle d’impression personnalisé (avancé)</h3> +<div class="paragraph"><p>Writing a custom template is an effective way to produce highly customized +printouts. Subsurface uses HTML templates to render printing. You can create +a template, export a new template, import an existing template and delete an +existing template by using the appropriate buttons under the <em>Template</em> +dropdown list in the print dialogue. See <a href="#S_APPENDIX_E">APPENDIX E</a> for +information on how to write or modify a template.</p></div> +</div> +</div> +</div> +<div class="sect1"> +<h2 id="S_Configure">11. Configurer un ordinateur de plongée</h2> +<div class="sectionbody"> +<div class="paragraph"><p><em>Subsurface</em> lets you 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. To begin, be sure the appropriate hardware +driver is installed for the dive computer (also required for downloading +dives) and 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>Une fois que l’ordinateur de plongée est connecté à <em>Subsurface</em>, +sélectionner <em>Fichier → Configurer l’ordinateur de plongée</em>, à partir du +menu principal. Fournir le nom du périphérique dans le champ en haut du +panneau de configuration et sélectionner le bon modèle d’ordinateur de +plongée à partir du panneau à gauche (voir l’image ci-dessous).</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 done:</p></div> +<div class="ulist"><ul> +<li> +<p> +<strong>Récupérer les détails disponibles</strong>. Cela charge la configuration existante à partir de l’ordinateur de plongée + dans <em>Subsurface</em>, en l’affichant dans le panneau de configuration. +</p> +</li> +<li> +<p> +<strong>Enregistrer les modifications sur le périphérique</strong>. Cela change la configuration de l’ordinateur + de plongée pour correspondre aux informations affichées dans le panneau de configuration. +</p> +</li> +<li> +<p> +<strong>Sauvegarder</strong>. Cela enregistre la configuration dans un fichier. <em>Subsurface</em> demande + l’emplacement et le nom du fichier pour enregistrer les informations. +</p> +</li> +<li> +<p> +<strong>Restaurer une sauvegarde</strong>. Cela charge les informations à partir d’un fichier de sauvegarde et l’affiche + dans le panneau de configuration. +</p> +</li> +<li> +<p> +<strong>Mettre à jour le firmware</strong>. Si un nouveau firmware est disponible pour l’ordinateur de plongée, + il sera chargé dans l’ordinateur de plongée. +</p> +</li> +</ul></div> +</div> +</div> +<div class="sect1"> +<h2 id="S_Preferences">12. Setting user <em>Preferences</em> for <em>Subsurface</em></h2> +<div class="sectionbody"> +<div class="paragraph"><p>There are several user-definable settings within <em>Subsurface</em>, found by +selecting <em>File → Preferences</em>. The settings are in seven groups: +<strong>Defaults</strong>, <strong>Units</strong>, <strong>Graph</strong>, <strong>Language</strong> and <strong>Network</strong>, <strong>Facebook</strong> and +<strong>Georeference</strong>. All operate on the same principles: the user must specify +settings that are to be changed, then save them using the <strong>Apply</strong> +button. After applying all the new settings users can then leave the +settings panel by selecting <strong>OK</strong>. If <strong>Discard</strong> is selected, changes to the +preferences are not saved.</p></div> +<div class="sect2"> +<h3 id="_defaults">12.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_f20.jpg" alt="FIGURE: Preferences defaults page" /> +</div> +</div> +<div class="ulist"><ul> +<li> +<p> +<strong>Lists and tables</strong>: Here you 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>, you can see more dives on a screen. +</p> +</li> +<li> +<p> +<strong>Dives</strong>: For the <em>Default Dive File</em> you need to specify the directory and + file name of your + electronic dive log book. This is a file with filename extension of either <em>.xml</em> or <em>.ssrf</em>. When + launched, <em>Subsurface</em> will automatically load the specified dive log book. There are three options: +</p> +<div class="ulist"><ul> +<li> +<p> +<em>No default file</em>: When checked, <em>Subsurface</em> does not automatically load a dive log at startup. +</p> +</li> +<li> +<p> +<em>Local default file</em>: When checked, <em>Subsurface</em> automatically loads a dive log from the local hard disk + as described above. +</p> +</li> +<li> +<p> +<em>Cloud storage default file</em>: When checked, <em>Subsurface automatically loads the dive log from the cloud + device that was initialized using the <strong>Preferences</strong> _Network</em> tab (see below). +</p> +</li> +</ul></div> +</li> +<li> +<p> +<strong>Display invalid</strong>: Dives can be marked as invalid (when a user wishes to hide + dives that he/she doesn’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>: Specify the default cylinder listed in + the <strong>Equipment</strong> tab of the <strong>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, and a 0 value representing no animation + at all. +</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">12.2. Units</h3> +<div class="imageblock" style="text-align:center;"> +<div class="content"> +<img src="images/Pref2_f20.jpg" alt="FIGURE: Preferences Units page" /> +</div> +</div> +<div class="paragraph"><p>Here you 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, you can specify that all units are in the chosen +measurement system. Alternatively, if you select the <strong>Personalize</strong> radio +button, units can be selected independently, with some in the metric system +and others in imperial.</p></div> +<div class="paragraph"><p>Regardless of the above settings, dive time measurements can be either in +seconds or minutes. Choose the appropriate option. GPS coordinates can be +represented either as traditional coordinates (degrees, minutes, seconds) or +as decimal degrees Choose the appropriate option.</p></div> +</div> +<div class="sect2"> +<h3 id="_graph">12.3. Graph</h3> +<div class="imageblock" id="S_CCR_options" style="text-align:center;"> +<div class="content"> +<img src="images/Pref3_f20.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 you 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, done by using the toolbar on the left hand side of the <strong>Dive Profile</strong> + panel. For each of these graphs you can specify a threshold value on the right-hand side of the + Preferences panel. If any of the graphs go above the specified threshold level, the graph is + highlighted in red, indicating the particular partial pressure threshold has been exceeded. +</strong> <em>Max pO<sub>2</sub> is used for calculating the MOD when displaying the maximum operative depth (MOD) + for a dive. Specify an appropriate partial pressure. A value of 1.4 is commonly used. +<strong> _Draw dive computer reported ceiling red</em>: This checkbox does exactly what it says. By default + the computer reported ceiling is shown in white. + 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> because of the different algorithms and + gradient factors, as well as the dynamic way a + dive computer calculates ceilings during a dive. +</strong> <em>Show unused cylinders in Equipment Tab</em>: This checkbox allows display of information about unused cylinders when viewing the +<strong>Equipment Tab</strong>. If this box is not checked, and if 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. +<strong>* <em>Show average depth</em>: If this box is checked, the *Dive Profile</strong> panel contains a grey line that shows + the mean depth of the dive, up to any time instant during the dive. Normally this is a u-shaped line indicating the deepest mean depth just before + ascent.</p></div> +<div class="ulist"><ul> +<li> +<p> +<strong>Misc</strong>: +</p> +<div class="ulist" id="GradientFactors_Ref"><ul> +<li> +<p> +Gradient Factors (GFLow and GFHigh):* 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 nitrogen exposure during a dive, in a + similar way that many dive computers have a conservative 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 70/90 are considered + harsh. Checking the <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> +<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> +</li> +<li> +<p> +<em>CCR: Show setpoints when viewing pO2:</em> With this checkbox activated, the pO<sub>2</sub> + graph on the dive profile has an overlay in red which indicates the CCR setpoint + values. See the section on <a href="#S_CCR_dives">Closed Circuit Rebreather dives</a>. +</p> +</li> +<li> +<p> +<em>CCR: Show individual O<sub>2</sub> sensor values when viewing pO<sub>2</sub>:</em> Show the pO<sub>2</sub> + values associated with each of the individual oxygen sensors of a CCR system. + See the section on <a href="#S_CCR_dives">Closed Circuit Rebreather dives</a>. +</p> +</li> +</ul></div> +</li> +<li> +<p> +<strong>Configuring dive planning using rebreather equipment:</strong> +</p> +<div class="ulist"><ul> +<li> +<p> +<em>Default CCR setpoint for dive planning:</em> Specify the O<sub>2</sub> setpoint for a + CCR dive plan. This determines the pO<sub>2</sub> maintained + during a particular dive. Setpoint changes during the dive can be added via the + profile context menu. +</p> +</li> +<li> +<p> +<em>pSCR O<sub>2</sub> metabolism rate:</em> For a semi-closed rebreather (pSCR) system, this is the + volume of oxygen used by a diver during a minute. Set this value for pSCR dive planning + and decompression calculations. +</p> +</li> +<li> +<p> +<em>pSCR ratio:</em> For pSCR equipment the dump ratio is the ratio of gas released to the + environment to that of the gas recirculated to the diver. Set this value for a + pSCR dive plan. A 1:10 ratio is commonly used. +</p> +</li> +</ul></div> +</li> +</ul></div> +</div> +<div class="sect2"> +<h3 id="_language">12.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_f20.jpg" alt="FIGURE: Preferences Language page" /> +</div> +</div> +<div class="paragraph"><p>A checkbox lets you 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 operating system. To change +it, uncheck this checkbox and pick a language / country combination from the +list of locations. The <em>Filter</em> text box lists similar languages. For +instance there are several system variants of English or French. <strong>This +particular preference requires a restart of <em>Subsurface</em> to take effect</strong>.</p></div> +</div> +<div class="sect2"> +<h3 id="_network">12.5. Network</h3> +<div class="paragraph"><p>This panel facilitates communication between <em>Subsurface</em> and data sources +on the Internet. This is important, for instance, when <em>Subsurface</em> needs +to communicate with web services such as Cloud storage or the +<a href="#S_Companion"><em>Subsurface Companion app</em></a>. These Internet requirements are +determined by your type of connection to the Internet and by the Internet +Service Provider (ISP) used. Your ISP should provide the appropriate +information.</p></div> +<div class="imageblock" style="text-align:center;"> +<div class="content"> +<img src="images/Pref5_f20.jpg" alt="FIGURE: Preferences Network page" /> +</div> +</div> +<div class="paragraph"><p>This dialogue has three sections:</p></div> +<div class="ulist"><ul> +<li> +<p> +<em>Proxy type</em>: +If a proxy server is used for Internet access, 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 are required so that <em>Subsurface</em> can automatically pass +through the proxy server to access the Internet. This information is usually obtained +from one’s ISP. +</p> +</li> +<li> +<p> +<em>Subsurface cloud storage</em>: To store your dive log in the cloud, a valid email address + and password are required. This lets <em>Subsurface</em> email security information + regarding cloud storage to you, and to set up cloud storage appropriately. + Two additional options are given: +</p> +<div class="ulist"><ul> +<li> +<p> +<em>Sync to cloud in the background</em>: This option allows saving of dive information to the cloud storage + while you do other things within <em>Subsurface</em>. +</p> +</li> +<li> +<p> +<em>Save password locally</em>: This allows local storage of the cloud storage password. Note that this + information is saved in raw text form, not encoded in any way. +</p> +</li> +</ul></div> +</li> +<li> +<p> +<em>Subsurface web service</em>: When you subscribe 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>, you ensure a local copy of that userID is saved. +</p> +</li> +</ul></div> +</div> +<div class="sect2"> +<h3 id="S_Facebook">12.6. Facebook Access</h3> +<div class="paragraph"><p>This panel lets you log into a Facebook account in order to transfer +information from Subsurface to Facebook.</p></div> +<div class="imageblock" style="text-align:center;"> +<div class="content"> +<img src="images/Pref6_f20.jpg" alt="FIGURE: Facebook login panel" /> +</div> +</div> +<div class="paragraph"><p>If you provide a valid Facebook userID and password, a connection to +Facebook is created. That connection is closed when one closing down +Subsurface. Currently the checkbox labelled "Keep me logged in to +Subsurface", on the login screen has no effect. See the section +<a href="#S_facebook">Exporting dive profiles to Facebook</a> for more information.</p></div> +</div> +<div class="sect2"> +<h3 id="_georeference">12.7. Georeference</h3> +<div class="paragraph"><p><em>Subsurface</em> provides a geo-lookup service (that is, given the coordinates +of a dive site) derived from a click on the <strong>Dive Map panel</strong> at the bottom +right of the <em>Subsurface</em> window, or from a GPS instrument or from the +<em>Subsurface</em> Companion app). A search on the Internet is done to find the +name of the closest known location. This function only works if <em>Subsurface</em> +has an Internet connection. The preference of the dive site name can be +configured, e.g. <em>Country/State/City</em> or <em>City/State/Country</em> (see image +below).</p></div> +<div class="imageblock" style="text-align:center;"> +<div class="content"> +<img src="images/Pref7_f20.jpg" alt="FIGURE: Facebook login panel" /> +</div> +</div> +</div> +</div> +</div> +<div class="sect1"> +<h2 id="S_DivePlanner">13. The <em>Subsurface</em> dive planner</h2> +<div class="sectionbody"> +<div class="paragraph"><p>Dive planning is an advanced feature of <em>Subsurface</em>, accessed by selecting +<em>Log → 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="ulist"><ul> +<li> +<p> +The user is conversant with dive planning and has the necessary training to + perform dive planning. +</p> +</li> +<li> +<p> +The user plans dives within his/her certification limits. +</p> +</li> +<li> +<p> +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. +</p> +</li> +<li> +<p> +The safety of a dive plan depends heavily on the way in which the planner is + used. +</p> +</li> +<li> +<p> +The user is familiar with the user interface of <em>Subsurface</em>. +</p> +</li> +<li> +<p> +A user who is not absolutely sure about any of the above requirements should + not use this feature. +</p> +</li> +</ul></div> +</div></div> +<div class="sect2"> +<h3 id="_the_em_subsurface_em_dive_planner_screen">13.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 sections on the left hand side of the screen. They are: Available +Gases, Rates, Planning, Gas Options and Notes.</p></div> +<div class="paragraph"><p>At the top right hand is a green <strong>design panel</strong> on 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_f20.jpg" alt="FIGURE: Dive planner startup window" /> +</div> +</div> +</div> +<div class="sect2"> +<h3 id="_open_circuit_dives">13.2. Open circuit dives</h3> +<div class="ulist"><ul> +<li> +<p> +Towards the center bottom of the planner (circled in blue in the image + above) is a dropbox with three options. Select the appropriate one of these: +</p> +<div class="ulist"><ul> +<li> +<p> +Open Circuit (the default) +</p> +</li> +<li> +<p> +CCR +</p> +</li> +<li> +<p> +pSCR +</p> +</li> +</ul></div> +</li> +<li> +<p> +Choose the Open Circuit option. +</p> +</li> +<li> +<p> +In the top left-hand area of the planning screen, be sure the constant dive + parameters are appropriate. These are: Start date and time of the intended + dive, Atmospheric Pressure and Altitude above sea level of the dive + site. The atmospheric pressure can also be entered as an altitude in meters, + assuming a sea-level atmospheric pressure of 1.013 bar. +</p> +</li> +<li> +<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="#cylinder_definitions">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 cylinder is assumed to contain + 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 right-hand of the dialogue. +</p> +</li> +<li> +<p> +The profile of the planned dive can be created in two ways: +</p> +<div class="ulist"><ul> +<li> +<p> +Drag the waypoints (the small white circles) on the existing dive profile to + represent the dive. Additional waypoints can be created by double-clicking + the existing dive profile. Waypoints can be deleted by right-clicking a + particular waypoint and selecting the <em>delete</em> item from the resulting + context menu. +</p> +</li> +<li> +<p> +The most efficient way to create a dive profile is to enter the appropriate + values into the table marked <em>Dive planner points</em>. The first line of the + table represents the duration and the final depth of the descent from the + surface. Subsequent segments describe the bottom phase of the dive. The <em>CC + set point</em> column is only relevant for closed circuit divers. The ascent is + usually not specified because this is what the planner is supposed to + calculate. Add additional segments to the profile by selecting the "+" icon + at the top right hand of the table. Segments entered into the <em>Dive planner + points</em> table automatically appear in the <strong>Dive Profile</strong> diagram. +</p> +</li> +</ul></div> +</li> +</ul></div> +<div class="sect3"> +<h4 id="_recreational_dives">13.2.1. Recreational dives</h4> +<div class="paragraph"><p>Recreational mode is what comes closest to planning a dive based on the non-decompression limit (NDL). +It computes the maximum time a diver can stay at the current depth without needing mandatory decompression +stops and without using more than the existing gas (minus a reserve). The planner automatically takes +into account the nitrogen load incurred in previous dives. But conventional dive tables are also used in a +way that can take into account previous dives. Why use a dive planner for recreational dives? Using +recreational dive tables, the maximum depth of a dive is taken into account. But few dives are +done at a constant depth corresponding to the maximum depth (i.e. a "square" dive profile). This means +dive tables overestimate the nitrogen load incurred during previous dives. The <em>Subsurface</em> +dive planner calculates nitrogen load according to the real dive profiles of all uploaded previous dives, +in a similar way as dive computers calculate nitrogen load during a dive. This means that the diver gets <em>credit,</em> +in terms of nitrogen load, for not remaining at maximum depth during +previous dives, so a longer subsequent dive can be planned. + For the planner to work it’s crucial to upload all previous dives +onto <em>Subsurface</em> before doing dive planning. +To plan a dive, the appropriate settings need to be defined.</p></div> +<div class="paragraph"><p>Ensure the date and time is set to that of the intended dive. This allows +calculation of the nitrogen load incurred during previous dives.</p></div> +<div class="ulist"><ul> +<li> +<p> +Immediately under the heading <em>Planning</em> are two checkboxes <em>Recreational</em> + and <em>Safety Stop</em>. Check these two boxes. +</p> +</li> +<li> +<p> +Then define the cylinder size, the gas mixture (air or % oxygen) and the + starting cylinder pressure in the top left-hand section of the planner under + <em>Available gases</em>. +</p> +</li> +<li> +<p> +The planner calculates whether the specified cylinder contains enough + air/gas to complete the planned dive. In order for this to be accurate, + under <em>Gas options</em>, specify an appropriate surface air consumption (SAC) + rate for <em>Bottom SAC</em>. Suitable values are between 15 l/min and 30 l/min, + with novice divers or difficult dives requiring SAC rates closer to 30l/min. +</p> +</li> +<li> +<p> +Define the amount of gas the cylinder must have at the end of the bottom + section of the dive just before ascent. A value of 50 bar is often used. The + reason for this reserve gas is to provide for the possible need to bring a + buddy to the surface using gas sharing. How much gas is used in sharing + depends on the depth of the ascent. This can be difficult to estimate, so + most agencies assume a fixed amount of gas, or actually of pressure e.g. 40 + or 50 bar or 25% or 33% (rule of thirds). But <em>Subsurface</em> can do better + because it knows about the ascent and that is why we add the amount of gas + during the ascent (i.e. the "deco gas“). Subsurface still uses a fixed + pressure "reserve" but that’s supposed to be for the additional gas used + when there’s a problem and your pulse rate goes up when you start to buddy + breathe. This reserve amount is user configurable. +</p> +</li> +<li> +<p> +Define the depth of the dive by dragging the waypoints (white dots) on the + dive profile or (even better) defining the appropriate depths using the + table under <em>Dive planner points</em> as desribed under the previous heading. If + this is a multilevel dive, set the appropriate dive depths to represent the + dive plan by adding waypoints to the dive profile or by adding appropriate + dive planner points to the <em>Dive Planner Points</em> table. <em>Subsurface</em> will + automatically extend the bottom section of the dive to the maximum duration + within the no-decompression limits (NDL). +</p> +</li> +<li> +<p> +The ascent speed can be changed. The default ascent speeds are those + considered safe for recreational divers. +</p> +</li> +</ul></div> +<div class="paragraph"><p>The dive profile in the planner shows the maximum dive time within no-deco +limits using the Bühlmann ZH-L16 algorithm and the gas and depth settings +specified as described above. The <em>Subsurface</em> planner allows rapid +assessment of dive duration as a function of dive depth, given the nitrogen +load incurred during previous dives. The dive plan includes estimates of the +amount of air/gas used, depending on the cylinder settings specified under +<em>Available gases</em>. If the initial cylinder pressure is set to 0, the dive +duration shown is the true no-deco limit (NDL) without taking into account +gas used during the dive. If the surface above the dive profile is RED it +means that recreational dive limits are exceeded and either the dive +duration or the dive depth needs to be reduced.</p></div> +<div class="paragraph"><p>Below is an image of a dive plan for a recreational dive at 30 +meters. Although the no-deco limit (NDL) is 23 minutes, the duration of the +dive is limited by the amount of air in the cylinder. That is shown in the +text box at the bottom right of the panel, requiring sufficient air for +buddy-sharing during ascent.</p></div> +<div class="imageblock" style="text-align:center;"> +<div class="content"> +<img src="images/rec_diveplan.jpg" alt="FIGURE: A recreational dive plan: setup" /> +</div> +</div> +</div> +<div class="sect3"> +<h4 id="_non_recreational_open_circuit_dives_including_decompression">13.2.2. Non-recreational open circuit dives, including decompression</h4> +<div class="paragraph"><p>Non-recreational dive planning involves exceeding the no-deco limits and/or +using multiple breathing gases. These dives are planned in three stages:</p></div> +<div class="paragraph"><p><strong>a) Nitrogen management</strong>: This is done by specifying the rates for descent and ascent, +as well as the deco model (GFLow, GFHigh or Conservatism level) under the headings <em>Rates</em> and <em>Planning</em> +to the bottom left of the planning screen. Two deco models are supported the Bühlmann model and the VPM-B +model. Select one of the two models. When selecting the Bühlmann model, the gradient factors (GF_high and GF_low +need to be specified. 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 values in the <em>Preferences</em>. +Gradient Factor settings strongly affect the calculated ceilings and their depths. +A very low GFLow value brings on decompression stops early during the dive. + ** For more information about Gradient factors, see the section on <a href="#S_GradientFactors">Gradient Factor Preference settings</a>.</p></div> +<div class="paragraph"><p>If the VPM-B model is selected, the Conservatism_level needs to be specified +on a scale of 0 (least conservative) to 4 (most conservative). This model +tends to give deco stops at deeper levels than the Bühlmann model and often +results in slightly shorter dive durations than the Bühlmann model. When +selecting one of these models, keep in mind they are NOT exact physiological +models but only mathematical models that appear to work in practice.</p></div> +<div class="paragraph"><p>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> +<a href="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"><em>Deco +for Divers</em>, by Mark Powell (2008). Aquapress</a> Southend-on-Sea, UK. ISBN 10: +1-905492-07-3. Un excellent livre non technique qui traite à la fois des +modèles de décompression Bühlmann et VPM-B. +</p> +</li> +</ul></div> +<div class="paragraph"><p>The ascent rate is critical for nitrogen off-gassing at the end of the dive +and is specified for several depth ranges, using the average (or mean) depth +as a yardstick. The mean depth of the dive plan is shown by a light grey +line on the dive profile. 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, 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></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 increased to 1.6 bar.</p></div> +<div class="paragraph"><p><strong>c) Gas management</strong>: With open-circuit dives this is a primary +consideration. Divers need to keep within the limits of the amount of +gas within the dive +cylinder(s), allowing for an appropriate margin for a 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 +liters/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 15-30 l/min are common. For good gas management, a guess +is not sufficient and you needs to +monitor gas consumption on a regular basis, dependent on different dive conditions and/or equipment. +The planner calculates the total volume of gas used during the dive and issues a warning +if you exceeds the total amount of gas available. Good practice demands that divers 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 you can start the detailed time-depth planning of the dive. <em>Subsurface</em> +offers an unique graphical interface for doing planning. Themechanics are +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 blue 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 the profile reflects the intended dive. Drag the waypoints to +represent the depth and duration of the dive. It is NOT necessary to specify +the ascent part of the dive since the planner calculates this, based on the +settings that have been specified. If any of the management limits (for +nitrogen, oxygen or gas) are 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. Be sure the <em>Used Gas</em> value in +each row of that table corresponds to one of the gas mixtures specified in +the <em>Available Gases</em> table. 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 fulfill decompression requirements for that dive. A waypoint can be +moved by selecting it 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 get a +precise presentation of the dive plan. In fact, you can create the whole +dive profile by editing the <em>Dive Planner Points</em> dialog.</p></div> +<div class="paragraph"><p>Show 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. These changes +can be deleted by right-clicking the gas change and 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_f20.jpg" alt="FIGURE: Planning a dive: setup" /> +</div> +</div> +<div class="paragraph"><p>Once the above steps have been completed, save by clicking the <em>Save</em> button +towards the top middle of the planner. The saved dive plan will appear in +the <strong>Dive List</strong> panel of <em>Subsurface</em>.</p></div> +<div class="paragraph"><p><strong>The dive plan details</strong></p></div> +<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>Notes</em> section of the dive +planner, immediately to the left of the <em>Dive Plan Details</em>. If a <em>Verbatim +dive plan</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> +<div class="sect2"> +<h3 id="_planning_pscr_dives">13.3. Planning pSCR dives</h3> +<div class="paragraph"><p>To plan a dive using a passive semi-closed rebreather (pSCR), select <em>pSCR</em> rather than +<em>Open circuit</em> in the dropdown list. +The parameters of the pSCR dive can be set by selecting <em>File → Preferences → Graph</em> +from the main menu, where the gas consumption calculation takes into account the pSCR dump +ratio (default 10:1) as well as the metabolism rate. The calculation also takes the oxygen drop +accross the mouthpiece of the rebreather into account. If the +pO<sub>2</sub> drops below what is considered safe, a warning appears in the <em>Dive plan +details</em>. A typical pSCR configuration is with a single cylinder and one or more bail-out +cylinders. Therefore the setup of the <em>Available gases</em> and the <em>Dive planner points</em> tables +are very similar to that of a CCR dive plan, described below. However, no oxygen setpoints +are specified for pSCR dives. Below is a dive plan for a pSCR dive. The dive is comparable +to that of the CCR dive below, but note the longer ascent duration due to the lower oxygen +in the loop due to the oxygen drop across the mouthpiece of the pSCR equipment.</p></div> +<div class="imageblock" style="text-align:center;"> +<div class="content"> +<img src="images/Planner_pSCR1_f20.jpg" alt="FIGURE: Planning a pSCR dive: setup" /> +</div> +</div> +</div> +<div class="sect2"> +<h3 id="_planning_ccr_dives">13.4. Planning CCR dives</h3> +<div class="paragraph"><p>To plan a dive using a closed circuit rebreather, select the <em>CCR</em> option in +the dropdown list, circled in blue in the image below.</p></div> +<div class="paragraph"><p><strong>Available gases</strong>: In the <em>Available gases</em> table, enter the cylinder information for the +diluent cylinder and for any bail-out cylinders. Do NOT enter the information for the oxygen +cylinder since it is implied when the <em>CCR</em> dropdown selection is made.</p></div> +<div class="paragraph"><p><strong>Entering setpoints</strong>: Specify a default setpoint in the Preferences tab, by selecting <em>File → Preferences → Graph</em> from +the main menu. All user-entered segments in the <em>Dive planner points</em> table +use the default setpoint value. Then, different setpoints can be specified for dive segments +in the <em>Dive planner points</em> table. A zero setpoint +means the diver bails out to open circuit mode for that segment. Decompression is always calculated +using the setpoint of the last manually entered segment. So, to plan a bail out ascent for a +CCR dive, add a one-minute dive segment to the end with a setpoint value of 0. The decompression +algorithm does not switch deco-gases automatically while in CCR mode (i.e. when a positive setpoint is specified) but +this is calculated for bail out ascents.</p></div> +<div class="paragraph"><p>The dive profile for a CCR dive may look something like the image below.</p></div> +<div class="imageblock" style="text-align:center;"> +<div class="content"> +<img src="images/Planner_CCR1_f20.jpg" alt="FIGURE: Planning a CCR dive: setup" /> +</div> +</div> +<div class="paragraph"><p>Note that, in the <em>Dive plan details</em>, the gas consumption for a CCR segment +is not calculated, so gas consumptions of 0 liters are the norm.</p></div> +</div> +<div class="sect2"> +<h3 id="S_Replan">13.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 no way to +change a saved dive plan. To change a dive plan, select it on the <strong>Dive +List</strong>. Then, in the main menu, select <em>Log → Re-plan dive</em>. This will open +the selected dive plan within the dive planner, letting changes 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">13.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 are specified appropriately in the top left-hand <em>Start +Time</em> field. <em>Subsurface</em> calculates the gas loading figures and the affect +of the first dive is evaluated on later dives.</p></div> +<div class="paragraph"><p>If you have just completed a long/deep dive and are planning another dive, +then highlight, in the <strong>Dive List</strong>, the dive that has just been done then +activate the planner. Depending on the start time of the planned dive, the +planner takes into account the gas loading during the completed dive and +plans accordingly.</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 you +want to plan a dive using this configuration, 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">13.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. You can also cut and paste the <em>Dive Plan +Details</em> to include 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>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 → Print</em> +function 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="_description_des_éléments_du_menu_principal_de_subsurface">14. Description des éléments du menu principal de Subsurface</h2> +<div class="sectionbody"> +<div class="paragraph"><p>Cette section décrit les fonctions et les opérations des éléments du menu +principal de Subsurface. Plusieurs éléments ci-dessous sont des liens vers +des sections de ce manuel traitant des opérations relatives.</p></div> +<div class="sect2"> +<h3 id="_fichier">14.1. Fichier</h3> +<div class="ulist"><ul> +<li> +<p> +<a href="#S_NewLogbook"><em>Nouveau carnet de plongée</em></a> - Fermer le carnet de plongée + actuellement ouvert et supprime toutes les informations de plongées. +</p> +</li> +<li> +<p> +<em>Open logbook</em> - Open the file manager to select a dive logbook to open. +</p> +</li> +<li> +<p> +<em>Open cloud storage</em> - Open the dive log previously saved in + <a href="#S_Cloud_storage"><em>Cloud storage</em></a>. +</p> +</li> +<li> +<p> +<em>Save</em> - Save the dive logbook currently open. +</p> +</li> +<li> +<p> +<em>Save to cloud storage</em> - Save the current dive log to + <a href="#S_Cloud_storage"><em>Cloud storage</em></a>. +</p> +</li> +<li> +<p> +<em>Enregsitrer sous</em> - Enregistrer le carnet actuel sous un nom différent. +</p> +</li> +<li> +<p> +<em>Close</em> - Close the dive logbook currently open. +</p> +</li> +<li> +<p> +<a href="#S_ExportLog"><em>Exporter</em></a> - Exporter le carnet de plongée actuellement + ouvert (ou les plongées sélectionnées dans le carnet) vers un des nombreux + formats. +</p> +</li> +<li> +<p> +<a href="#S_PrintDivelog"><em>Imprimer</em></a> - Imprimer le carnet de plongée actuellement + ouvert. +</p> +</li> +<li> +<p> +<a href="#S_Preferences"><em>Préférences</em></a> - Définir les préférences de <em>Subsurface</em>. +</p> +</li> +<li> +<p> +<a href="#S_FindMovedImages"><em>Find moved images</em></a> - If photos taken during dives + have been moved to + a different disk or directory, locate them and link them to the appropriate + dives. +</p> +</li> +<li> +<p> +<a href="#S_Configure"><em>Configurer l’ordinateur de plongée</em></a> - Modifier la + configuration d’un ordinateur de plongée. +</p> +</li> +<li> +<p> +<em>Quitter</em> - Quitter <em>Subsurface</em>. +</p> +</li> +</ul></div> +</div> +<div class="sect2"> +<h3 id="_importer">14.2. Importer</h3> +<div class="ulist"><ul> +<li> +<p> +<a href="#S_ImportDiveComputer"><em>Importer depuis un l’ordinateur de plongée</em></a> - + Importer des informations de plongées à partir de l’ordinateur de plongée. +</p> +</li> +<li> +<p> +<a href="#Unified_import"><em>Importer des fichiers de log</em></a> - Importer des + informations de plongées à partir d’un fichier d’un format compatible avec + <em>Subsurface</em>. +</p> +</li> +<li> +<p> +<a href="#S_Companion"><em>Importer les données GPS depis le service web Subsurface</em></a> - + Charge les coordonnées GPS à partir de l’application mobile <em>Subsurface</em> + (téléphones et tablettes). +</p> +</li> +<li> +<p> +<a href="#S_ImportingDivelogsDe"><em>Importer depuis Divelogs.de</em></a> - Importer des + informations de plongées à partir de <em>www.Divelogs.de</em>. +</p> +</li> +</ul></div> +</div> +<div class="sect2"> +<h3 id="_journal_log">14.3. Journal (log)</h3> +<div class="ulist"><ul> +<li> +<p> +<a href="#S_EnterData"><em>Ajouter une plongée</em></a> - Ajouter manuellement une nouvelle + plongée au panneau de la <strong>liste des plongées</strong>. +</p> +</li> +<li> +<p> +<em>Edit dive</em> - Edit a dive where the profile was entered by hand and not from + a dive computer. +</p> +</li> +<li> +<p> +<a href="#S_DivePlanner"><em>Planifier une plongée</em></a> - Planifier des plongées. +</p> +</li> +<li> +<p> +<a href="#S_Replan"><em>Modifier la plongée dans le planificateur</em></a> - Modifier une + plongée planifiée qui a été enregistrée dans la <strong>liste des plongées</strong>. +</p> +</li> +<li> +<p> +<a href="#S_CopyComponents"><em>Copier les composants de la plongée</em></a> - Copier les + informations de plusieurs champs d’un journal de plongée vers le + presse-papier. +</p> +</li> +<li> +<p> +<em>Coller les composants de la plongée</em> - Colle, dans les plongées + sélectionnées dans la <strong>liste des plongées</strong>, les informations copiées au + préalable avec l’option <em>Copier les composants de la plongée</em>. +</p> +</li> +<li> +<p> +<a href="#S_Renumber"><em>Renuméroter</em></a> - Renuméroter les plongées sélectionnées dans + le panneau de la <strong>liste des plongées</strong>. +</p> +</li> +<li> +<p> +<a href="#S_Group"><em>Grouper automatiquement</em></a> - Grouper les plongées du panneau de + <strong>liste des plongées</strong> dans des voyages de plongées. +</p> +</li> +<li> +<p> +<a href="#S_DeviceNames"><em>Editer les noms des ordinateurs de plongée</em></a> - Modifier + les noms des ordinateurs de plongée pour coordonner vos journaux (logs). +</p> +</li> +<li> +<p> +<a href="#S_Filter"><em>Filtrer la liste des plongées</em></a> - Sélectionner seulement + certaines plongées, à partir de tags ou de critères de plongées. +</p> +</li> +</ul></div> +</div> +<div class="sect2"> +<h3 id="_vue">14.4. Vue</h3> +<div class="ulist"><ul> +<li> +<p> +<a href="#S_ViewPanels"><em>Tout</em></a> - Affiche les quatre panneaux principaux de + <em>Subsurface</em> simultanément. +</p> +</li> +<li> +<p> +<a href="#S_ViewPanels"><em>Liste des plongées</em></a> - Affiche uniquement le panneau de la + <strong>liste des plongées</strong>. +</p> +</li> +<li> +<p> +<a href="#S_ViewPanels"><em>Profil</em></a> - Affiche uniquement le panneau du <strong>profil de la + plongée</strong>. +</p> +</li> +<li> +<p> +<a href="#S_ViewPanels"><em>Info</em></a> - Affiche uniquement le panneau des <strong>notes</strong>. +</p> +</li> +<li> +<p> +<a href="#S_ViewPanels"><em>Globe</em></a> - Affiche uniquement le panneau de la <strong>carte + mondiale</strong>. +</p> +</li> +<li> +<p> +<em>Statistiques annuelles</em> - Affiche par année le résumé des statistiques des + plongées effectuées. +</p> +</li> +<li> +<p> +<em>Prev DC</em> - Switch to data from previous dive computer, if a single dive was + logged from more than one. +</p> +</li> +<li> +<p> +<em>Ordinateur suivant</em> - Passer à l’ordinateur de plongée suivant. +</p> +</li> +<li> +<p> +<em>Plein écran</em> - Passer en mode plein écran. +</p> +</li> +</ul></div> +</div> +<div class="sect2"> +<h3 id="_share_on">14.5. Share on</h3> +<div class="ulist"><ul> +<li> +<p> +<a href="#S_Facebook"><em>Facebook</em></a> - Partager la plongée sélectionnée sur votre + Facebook. +</p> +</li> +</ul></div> +</div> +<div class="sect2"> +<h3 id="_aide">14.6. Aide</h3> +<div class="ulist"><ul> +<li> +<p> +<em>À propos de Subsurface</em> - Affiche un panneau avec le numéro de version de + <em>Subsurface</em> ainsi que les informations de licence. +</p> +</li> +<li> +<p> +<em>Vérifier les mises à jour</em> - Vérifier si une nouvelle version de + Subsurface est disponible sur le <a href="http://subsurface-divelog.org/">site web de + <em>Subsurface</em> </a>. +</p> +</li> +<li> +<p> +<a href="#S_UserSurvey"><em>Sondge utilisateur</em></a> - Aider à rendre <em>Subsurface</em> encore + meilleur en répondant à notre sondage utilisateur ou en répondant à un autre + sondage, si vos habitudes de plongées ont changées. +</p> +</li> +<li> +<p> +<em>Manuel utilisateur</em> - Ouvre une fenêtre affichant ce manuel utilisateur. +</p> +</li> +</ul></div> +</div> +</div> +</div> +<div class="sect1"> +<h2 id="_annexe_a_informations_spécifiques_au_système_d_8217_exploitation_utilisé_pour_importer_les_informations_de_plongées_depuis_un_ordinateur_de_plongée">15. ANNEXE A : informations spécifiques au système d’exploitation utilisé pour importer les informations de plongées depuis un ordinateur de plongée.</h2> +<div class="sectionbody"> +<div class="sect2"> +<h3 id="_assurez_vous_que_les_pilotes_drivers_nécessaires_sont_installés">15.1. Assurez-vous que les pilotes (drivers) nécessaires sont installés</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, the way the dive computer +prefers (e.g. Bluetooth, USB, infra-red).</td> +</tr></table> +</div> +<div class="ulist"><ul> +<li> +<p> +Sous Linux, les utilisateurs doivent avoir le bon module noyau de chargé. La + plupart des distributions Linux le font automatiquement, de telle sorte que + l’utilisateur n’ait rien à faire de particulier. Cependant, certains + protocoles de communication nécessitent des pilotes additionnels, plus + particulièrement pour certaines technologies telles que l’infra-rouge. +</p> +</li> +<li> +<p> +Sous Windows, le bon pilote devrait être téléchargé automatiquement la + première fois que l’utilisateur branche son ordinateur de plongée sur le + port USB de son ordinateur de bureau. +</p> +</li> +</ul></div> +<div class="paragraph"><p>Sous Mac, les utilisateurs peuvent parfois avoir besoin d’installer +manuellement le bon pilote. Par exemple, pour le Mares Puck ou n’importe +quel autre ordinateur de plongée utilisant une interface USB-série basé sur +le composant Silicon Labs CP2101 ou similaire, le bon pilote est disponible +sous <em>Mac_OSX_VCP_Driver.zip</em> sur le +<a href="http://www.silabs.com/support/pages/document-library.aspx?p=Interface&f=USB%20Bridges&pn=CP2101">dépôt +de documents et logiciels Silicon Labs</a>.</p></div> +</div> +<div class="sect2"> +<h3 id="S_HowFindDeviceName">15.2. Comment trouver le nom du périphérique branché sur USB et paramétrer les permissions en écriture</h3> +<div class="admonitionblock"> +<table><tr> +<td class="icon"> +<img src="images/icons/usb.jpg" alt="Note" /> +</td> +<td class="content">When connecting a dive computer by using a USB connector, usually +<em>Subsurface</em> will either propose a drop down list with 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 ways to find out what the device name is:</td> +</tr></table> +</div> +<div class="paragraph"><div class="title">Sur Windows :</div><p>Essayez simplement COM1, COM2, etc. La liste déroulante devrait contenir +tous les périphériques COM connectés.</p></div> +<div class="paragraph"><div class="title">Sur MacOS :</div><p>La liste déroulante devrait contenir tous les ordinateurs de plongée +connectés.</p></div> +<div class="paragraph"><div class="title">Sur Linux :</div><p>Il existe un moyen sûr de trouver le port :</p></div> +<div class="ulist"><ul> +<li> +<p> +Déconnecter le cable USB de l’ordinateur de plongée +</p> +</li> +<li> +<p> +Ouvrir un terminal +</p> +</li> +<li> +<p> +Taper la commande <em>dmesg</em> et appuyer sur la touche Entrer +</p> +</li> +<li> +<p> +Connecter le cable USB de l’ordinateur de plongée +</p> +</li> +<li> +<p> +Taper la commande <em>dmesg</em> et appuyer sur la touche Entrer +</p> +</li> +</ul></div> +<div class="paragraph"><p>Un message similaire à celui-ci devrait apparaitre :</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>La troisième ligne en partant du bas montre que l’adaptateur FTDI USB est +détecté et connecté sur <code>ttyUSB3</code>. Cette information peut à présent être +utilisée pour les paramètres d’importation en tant que <code>/dev/ttyUSB3</code> pour +que Subsurface utilise le bon port USB.</p></div> +<div class="paragraph"><p>Ensuring 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 special group that can be e.g. <code>dialout</code> or <code>uucp</code>. This +can be verified by listing the appropriate device permissions e.g. by <code>ls -l +/dev/ttyUSB0</code>. Note that the number in the file name depends on how many USB +devices you have connected, and must be adjusted appropriately. If one is +not root, one may not be a member of that group and won’t be able to use the +USB port. Let us assume one’s username is <em>johnB</em>.</p></div> +<div class="paragraph"><p>En tant que root, tapez : usermod -a -G dialout johnB+ (utilisateurs +d’Ubuntu : <code>sudo usermod -a -G dialout johnB</code>) Cela ajoute johnB au groupe +<code>dialout</code>. +Tapez : <code>id johnB</code> Cela liste tous les groupes auquel johnB appartient et +vérifiez que +l’appartenance au groupe est bien effectif. Le groupe <code>dialout</code> devrait +être listé +parmi les différents IDs. +Sous certaines circonstances, les modifications ne prennent effet qu’après une déconnexion +puis reconnexion sur l’ordinateur (sous Ubuntu, par exemple).</p></div> +<div class="paragraph"><p>Avec le bon nom de périphérique (par exemple <code>dev/ttyUSB3</code>) et avec un accès +en écriture au port USB, l’ordinateur de plongée devrait se connecter et +vous devriez pouvoir importer vos plongées.</p></div> +</div> +<div class="sect2"> +<h3 id="S_HowFindBluetoothDeviceName">15.3. Manually 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, Petrel and Nerd there is a +different procedure to get the device’s 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, be sure 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’s user +guide. When using a Shearwater Predator/Petrel/Nerd, select <em>Dive Log → +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="sect3"> +<h4 id="_sur_windows_2">15.3.1. Sur Windows :</h4> +<div class="paragraph"><p>Bluetooth is most likely already enabled. For pairing with the dive computer +choose <em>Control Panel → Bluetooth Devices → Add Wireless Device</em>. This +should bring up a dialog showing your dive computer (which should be in +Bluetooth mode) and allowing pairing. Right click on it and choose +<em>Properties→ 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> +<div class="sect3"> +<h4 id="_sur_macos">15.3.2. Sur MacOS :</h4> +<div class="paragraph"><p>Click on the Bluetooth symbol in the menu bar and select <em>Set up Bluetooth +Device…</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 complete, 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> +<div class="sect3"> +<h4 id="_sur_linux">15.3.3. Sur Linux</h4> +<div class="paragraph"><p>Be sure 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 +straightforward. For instance, Gnome3 shows a Bluetooth icon on the right of +the toolbar at the top of the screen. Users have reported difficulties with +some Bluetooth controllers. If you have an onboard controller, try that +first. It is simplest if you remove any USB Bluetooth dongles. If you have +a USB dongle that came with your dive computer, try that before any others.</p></div> +<div class="paragraph"><p>Setting up a connection to download dives from your Bluetooth-enabled +device, such as the <em>Shearwater Petrel</em>, is not yet an automated process and +will generally require the command prompt. It is essentially a three step +process.</p></div> +<div class="ulist"><ul> +<li> +<p> +Enable the Bluetooth controller and pair your dive computer +</p> +</li> +<li> +<p> +Establish an RFCOMM connection +</p> +</li> +<li> +<p> +Download the dives with Subsurface +</p> +</li> +</ul></div> +<div class="paragraph"><p>Ensure the dive computer is in upload mode. On the <em>Shearwater Petrel</em>, +<em>Petrel 2</em> and <em>Nerd</em> cycle through the menu, select <em>Dive Log</em>, then +<em>Upload Log</em>. The display will read <em>Initializing</em>, then <em>Wait PC 3:00</em> and +will countdown. Once the connection is established, the display reads <em>Wait +CMD …</em> and the countdown continues. When downloading the dive from +Subsurface, the display reads <em>Sending</em> then <em>Sent Dive</em>.</p></div> +<div class="paragraph"><p>To establish the connection, establish root access through <code>sudo</code> or <code>su</code>. +The correct permission is required to download the dives in the computer. On +most Linux systems this means becoming a member of the dialout group (This +is identical as for many dive computers using a Linux USB port, described in +the previous section). On the command terminal, enter:</p></div> +<div class="paragraph"><p><code>sudo usermod -a -G dialout username</code></p></div> +<div class="paragraph"><p>Then log out and log in for the change to take effect.</p></div> +<div class="sect4"> +<h5 id="_enabling_the_bluetooth_controller_and_pairing_your_dive_computer">Enabling the Bluetooth controller and pairing your dive computer</h5> +<div class="paragraph"><p>Attempt to set up the Bluetooth controller and pair your dive computer using +the graphical environment of the operating system. After setting the dive +computer to upload mode, click the Bluetooth icon in the system tray and +select <em>Add new device</em>. The dive computer should appear. If asked for a +password, enter 0000. Write down or copy the MAC address of your dive +computer - this needed later and should be in the form 00:11:22:33:44:55.</p></div> +<div class="paragraph"><p>If the graphical method doesn’t work, pair the device from the command +line. Open a terminal and use <code>hciconfig</code> to check the Bluetooth controller +status</p></div> +<div class="literalblock"> +<div class="content"> +<pre><code>$ hciconfig +hci0: Type: BR/EDR Bus: USB + BD Address: 01:23:45:67:89:AB ACL MTU: 310:10 SCO MTU: 64:8 + *DOWN* + RX bytes:504 acl:0 sco:0 events:22 errors:0 + TX bytes:92 acl:0 sco:0 commands:21 errors:0</code></pre> +</div></div> +<div class="paragraph"><p>This indicates a Bluetooth controller with MAC address 01:23:45:67:89:AB, +connected as hci0. Its status is <em>DOWN</em>, i.e. not powered. Additional +controllers will appear as hci1, etc. If there is not a Bluetooth dongle +plugged in upon booting the computer, hci0 is probably the onboard. Now +power on the controller and enable authentication:</p></div> +<div class="literalblock"> +<div class="content"> +<pre><code>sudo hciconfig hci0 up auth+ (enter password when prompted) +hciconfig +hci0: Type: BR/EDR Bus: USB + BD Address: 01:23:45:67:89:AB ACL MTU: 310:10 SCO MTU: 64:8 + *UP RUNNING PSCAN AUTH* + RX bytes:1026 acl:0 sco:0 events:47 errors:0 + TX bytes:449 acl:0 sco:0 commands:46 errors:0</code></pre> +</div></div> +<div class="paragraph"><p>Check that the status now includes <code><em>UP</em>, <em>RUNNING</em> AND <em>AUTH</em></code>.</p></div> +<div class="paragraph"><p>If there are multiple controllers running, it’s easiest to off the unused +controller(s). For example, for <code>hci1</code>:</p></div> +<div class="literalblock"> +<div class="content"> +<pre><code>sudo hciconfig hci1 down</code></pre> +</div></div> +<div class="paragraph"><p>Next step is to <em>trust</em> and <em>pair</em> the dive computer. On distros with Bluez +5, such as Fedora 22, one can use a tool called <code>blutootctl</code>, which will +bring up its own command prompt.</p></div> +<div class="literalblock"> +<div class="content"> +<pre><code>bluetoothctl +[NEW] Controller 01:23:45:67:89:AB localhost.localdomain [default] +[bluetooth]# agent on +Agent registered +[bluetooth]# default-agent +Default agent request successful +[bluetooth]# scan on <----now set your dive computer to upload mode +Discovery started +[CHG] Controller 01:23:45:67:89:AB Discovering: yes +[NEW] Device 00:11:22:33:44:55 Petrel +[bluetooth]# trust 00:11:22:33:44:55 <----you can use the tab key to autocomplete the MAC address +[CHG] Device 00:11:22:33:44:55 Trusted: yes +Changing 00:11:22:33:44:55 trust succeeded +[bluetooth]# pair 00:11:22:33:44:55 +Attempting to pair with 00:11:22:33:44:55 +[CHG] Device 00:11:22:33:44:55 Connected: yes +[CHG] Device 00:11:22:33:44:55 UUIDs: 00001101-0000-1000-8000-0089abc12345 +[CHG] Device 00:11:22:33:44:55 Paired: yes +Pairing successful +[CHG] Device 00:11:22:33:44:55 Connected: no</code></pre> +</div></div> +<div class="paragraph"><p>If asked for a password, enter 0000. It’s ok if the last line says +<em>Connected: no</em>. The important part is the line above, <code>Pairing successful</code>.</p></div> +<div class="paragraph"><p>If the system has Bluez version 4 (e.g. Ubuntu 12.04 through to 15.04), +there is probably not a <code>bluetoothctl</code>, but a script called +<code>bluez-simple-agent</code> or just <code>simple-agent</code>.</p></div> +<div class="literalblock"> +<div class="content"> +<pre><code>hcitool -i hci0 scanning +Scanning ... + 00:11:22:33:44:55 Petrel + bluez-simple-agent hci0 00:11:22:33:44:55</code></pre> +</div></div> +<div class="paragraph"><p>Once ther dive computer is pired, set up the RFCOMM connection</p></div> +</div> +<div class="sect4"> +<h5 id="_establishing_the_rfcomm_connection">Establishing the RFCOMM connection</h5> +<div class="paragraph"><p>The command to establish an RFCOMM connection is:</p></div> +<div class="paragraph"><p><code>sudo rfcomm -i <controller> connect <dev> <bdaddr> [channel]</code></p></div> +<div class="ulist"><ul> +<li> +<p> +<code><controller></code> is the Bluetooth controller, <code>hci0</code>. +</p> +</li> +<li> +<p> +<code><dev></code> is the RFCOMM device file, <code>rfcomm0</code> +</p> +</li> +<li> +<p> +<code><bdaddr></code> is the dive computer’s MAC address, <code>00:11:22:33:44:55</code> +</p> +</li> +<li> +<p> +<code>[channel]</code> is the dive computer’s Bluetooth channel we need to connect to. +</p> +</li> +</ul></div> +<div class="paragraph"><p>If one omits it, channel 1 is assumed. Based on a limited number of user +reports, the appropriate channel for the dive computer is probably:</p></div> +<div class="ulist"><ul> +<li> +<p> +<em>Shearwater Petrel 1</em>: channel 1 +</p> +</li> +<li> +<p> +<em>Shearwater Petrel 2</em>: channel 5 +</p> +</li> +<li> +<p> +<em>Shearwater Nerd</em>: channel 5 +</p> +</li> +<li> +<p> +<em>Heinrichs-Weikamp OSTC Sport</em>: channel 1 +</p> +</li> +</ul></div> +<div class="paragraph"><p>E.g. to connect a <em>Shearwater Petrel 2</em>, set the dive computer to upload +mode and enter:</p></div> +<div class="literalblock"> +<div class="content"> +<pre><code>sudo rfcomm -i hci0 connect rfcomm0 00:11:22:33:44:55 5 (enter a password, probably 0000, when prompted)</code></pre> +</div></div> +<div class="paragraph"><p>This gives the response:</p></div> +<div class="literalblock"> +<div class="content"> +<pre><code>Connected /dev/rfcomm0 to 00:11:22:33:44:55 on channel 5 +Press CTRL-C for hangup</code></pre> +</div></div> +<div class="paragraph"><p>To connect a _Shearwater Petrel 1+ or + HW OSTC Sport+, set the dive +computer to upload mode and enter:</p></div> +<div class="literalblock"> +<div class="content"> +<pre><code>sudo rfcomm -i hci0 connect rfcomm0 00:11:22:33:44:55 (enter a password, probably 0000, when prompted) +Connected /dev/rfcomm0 to 00:11:22:33:44:55 on channel 1 +Press CTRL-C for hangup</code></pre> +</div></div> +<div class="paragraph"><p>If the specific channel the dive computer needs is not known, or the channel +in the list above doesn’t work, the command <code>sdptool records</code> should help +determine the appropriate channel. The output below is for a <em>Shearwater +Petrel 2</em>.</p></div> +<div class="literalblock"> +<div class="content"> +<pre><code>sdptool -i hci0 records 00:11:22:33:44:55 +Service Name: Serial Port +Service RecHandle: 0x10000 +Service Class ID List: + "Serial Port" (0x1101) + Protocol Descriptor List: + "L2CAP" (0x0100) + "RFCOMM" (0x0003) + Channel: 5</code></pre> +</div></div> +<div class="paragraph"><p>For a Bluetooth dive computer not in the list above, or if the channel +listed is not correct, please let the Subsurface developers know on the user +forum or the developer mailing list <em>subsurface@subsurface-divelog.org</em>.</p></div> +</div> +<div class="sect4"> +<h5 id="_download_the_dives_with_subsurface">Download the dives with Subsurface</h5> +<div class="paragraph"><p>After establishing the RFCOMM connection and while the dive computer’s +upload mode countdown is still running, go to_Subsurface_, select +<em>Import→Import from dive computer</em> and enter appropriate Vendor +(e.g. <em>Shearwater</em>), Dive Computer (<em>Petrel</em>), Device or Mount Point +(<em>/dev/rfcomm0</em>) and click <em>Download</em>.</p></div> +</div> +</div> +</div> +</div> +</div> +<div class="sect1"> +<h2 id="_appendix_b_dive_computer_specific_information_for_importing_dive_information">16. APPENDIX B: Dive Computer specific information for importing dive data.</h2> +<div class="sectionbody"> +<div class="sect2"> +<h3 id="S_ImportUemis">16.1. Importing from 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 +you don’t 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/<your_username>/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 you +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 you download +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 +straightforward. 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. You 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">16.2. Importing from 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 recognize 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>. +Windows-based IrDA drivers for the Uwatec can also be downloaded from the +ScubaPro web site, with drivers located on the download page for the +ScubaPro SmartTrak software.</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">16.3. Importing 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’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="S_ImportingXDeep">16.4. Importing from xDEEP BLACK</h3> +<div class="admonitionblock"> +<table><tr> +<td class="icon"> +<img src="images/icons/HW_xdeepblack.jpg" alt="Note" /> +</td> +<td class="content">Each dive has to be individually saved as UDDF file using "Export UDDF" +option in BLACK’s logbook menu. When mounted as a USB drive UDDF files are +available in LOGBOOK directory. Note: The xDEEP BLACK saves NDL time but +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 xDEEP +BLACK.</td> +</tr></table> +</div> +</div> +<div class="sect2"> +<h3 id="_importing_from_shearwater_predator_petrel_nerd_using_bluetooth">16.5. Importing from Shearwater Predator/Petrel/Nerd using Bluetooth</h3> +<div class="admonitionblock"> +<table><tr> +<td class="icon"> +<img src="images/icons/predator.jpg" alt="Note" /> +</td> +<td class="content">Specific instructions for downloading dives using Bluetooth are given in the +section above, <a href="#S_Bluetooth"><em>Connecting Subsurface to a Bluetooth-enabled dive computer</em></a>.</td> +</tr></table> +</div> +</div> +<div class="sect2"> +<h3 id="S_PoseidonMkVI">16.6. Importing from 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 utilizes the +IrDA infra-red protocol. Only data for one dive can be downloaded at a time, +in three files:</td> +</tr></table> +</div> +<div class="ulist"><ul> +<li> +<p> +Setup configuration for the dive and key dive parameters (file with a .txt + extension) +</p> +</li> +<li> +<p> +Dive log details (file with a .csv extension) +</p> +</li> +<li> +<p> +Redbook format dive log (file with .cvsr extension). This is a compressed + version of the dive log using a proprietary format. +</p> +</li> +</ul></div> +<div class="paragraph"><p><em>Subsurface</em> accesses the .txt and the .csv files to get dive log +information.</p></div> +</div> +<div class="sect2"> +<h3 id="_importing_from_apd_inspiration_evolution_ccr">16.7. Importing from APD Inspiration/Evolution 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> +Download the dive using <em>AP Communicator</em>. +</p> +</li> +<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> +With 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) or TextWrangler (Mac). +</p> +</li> +<li> +<p> +Copy the contents of the clipboard into the text editor and save the text + file with a filename extension of <em>.apd</em> +</p> +</li> +<li> +<p> +Within <em>Subsurface</em>, select <em>Import → 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 (labeled + <em>Filter:</em>), select "APD log viewer". +On the list of file names select the <em>.apd</em> file created. An import +dialogue opens showing the default settings for the data in the +<em>.apd</em> file. If changes are required, + do this as for <a href="#S_ImportingCSVDives">CSV imports</a>. +</p> +</li> +</ul></div> +<div class="imageblock" style="text-align:center;"> +<div class="content"> +<img src="images/APD_CSVimportF22.jpg" alt="Figure: APD log viewer import" /> +</div> +</div> +<div class="ulist"><ul> +<li> +<p> +The top left hand dropdown box in the import panel lets you select the APD + dive computer for which the dive log needs to be imported. The default it is + DC1, <em>i.e.</em> the first of the two dive computers the APD uses. It is possible + to sequentially import the data for both dive computers by first importing + CD1 and then DC2.(<strong>Hint</strong>: The logs for the two dive computers are viewed by + selecting <em>View → Next DC</em> from the Main Menu after the uploading has been + completed) +</p> +</li> +<li> +<p> +Click the <em>Ok</em> button at the bottom of the import panel. +</p> +</li> +</ul></div> +<div class="paragraph"><p>The APD dive log will appear within <em>Subsurface</em>. The dive computer- +generated ceiling provided by the Inspiration can be viewed by selecting the +appropriate button on the left of the <strong>Dive Profile</strong>. Cylinder pressure data +are not logged by the APD equipment but can be manually entered in the +<em>Equipment</em> Tab.</p></div> +</div> +</div> +</div> +<div class="sect1"> +<h2 id="_appendix_c_exporting_dive_log_information_from_external_dive_log_software">17. 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="olist arabic"><ol class="arabic"> +<li> +<p> +Export the foreign dive log data to format that is accessible from + <em>Subsurface</em>. +</p> +</li> +<li> +<p> +Import the accessible dive log data into <em>Subsurface</em>. +</p> +</li> +</ol></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">17.1. Exporting 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. +</p> +</li> +<li> +<p> +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 +</p> +</li> +<li> +<p> +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 → 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 you need to locate the DM4/DM5 database where the +dives are stored. You 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 → About</em> +</p> +</li> +<li> +<p> +Click <em>Copy</em> after text <em>Copy log folder path to clipboard</em> +</p> +</li> +<li> +<p> +Ouvrir l’explorateur Windows +</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’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_atomic_logbook">17.2. Exporting from Atomic Logbook</h3> +<div class="admonitionblock" id="Atomic_Export"> +<table><tr> +<td class="icon"> +<img src="images/icons/atomiclogo.jpg" alt="Note" /> +</td> +<td class="content">Atomic Logbook is a Windows software by Atomic Aquatics. It allows +downloading of dive information from Cobalt and Cobalt 2 dive computers. +The divelog is kept in a SQLite database at +C:\ProgramData\AtomicsAquatics\Cobalt-Logbook\Cobalt.db. This file can be +directly imported to Subsurface.</td> +</tr></table> +</div> +</div> +<div class="sect2"> +<h3 id="_exporting_from_mares_dive_organiser_v2_1">17.3. 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 Organizer 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 Organizer-registered divers on the particular +computer and all Mares dive computers used. The safest way to get a copy of +the dive database is to export the information to another compatible format +which can then be imported into <em>Subsurface</em>.</td> +</tr></table> +</div> +<div class="olist arabic"><ol class="arabic"> +<li> +<p> +Within Dive Organizer, select <em>Database → Backup</em> from the main menu and + back up the database to the desk top. This creates a zipped file + DiveOrganizerxxxxx.dbf. +</p> +</li> +<li> +<p> +Rename the file to DiveOrganizerxxxxx.zip. Inside the zipped directory is a + file <em>DiveOrganizer.sdf</em>. +</p> +</li> +<li> +<p> +Extract the <em>.sdf</em> file from the zipped folder to your Desktop. +</p> +</li> +<li> +<p> +The password for accessing the .zip file is <em>mares</em>. +</p> +</li> +</ol></div> +</div> +<div class="sect2"> +<h3 id="S_ImportingDivingLog">17.4. Exporting from <strong>DivingLog 5.0 and 6.0</strong></h3> +<div class="admonitionblock"> +<table><tr> +<td class="icon"> +<img src="images/icons/divingloglogo.jpg" alt="Note" /> +</td> +<td class="content">The best way to bring your logs from DivingLog to Subsurface is to convert +the whole database. This is because other export formats do not include all +the details, and would lack, for example, gas switches and information of +what units are used. With database import, all this information is included +and readily available.</td> +</tr></table> +</div> +<div class="paragraph"><p>To transfer all files from DivingLog to Subsurface:</p></div> +<div class="olist arabic"><ol class="arabic"> +<li> +<p> +In DivingLog open the <em>File → Export → SQLite</em> menu +</p> +</li> +<li> +<p> +Select <em>Settings</em> button +</p> +</li> +<li> +<p> +Set the <em>RTF2Plaintext</em> to <em>true</em> +</p> +</li> +<li> +<p> +Close the Settings dialog +</p> +</li> +<li> +<p> +Click <em>Export</em> button and select the filename +</p> +</li> +</ol></div> +<div class="paragraph"><p>Once this is done, open the saved database file with Subsurface and the +dives are automatically converted to Subsurface’s own format. Last step to +do is save the log file in Subsurface.</p></div> +</div> +</div> +</div> +<div class="sect1"> +<h2 id="_annexe_d_exporter_un_tableur_vers_le_format_csv">18. ANNEXE D : Exporter un tableur vers le format CSV</h2> +<div class="sectionbody"> +<div class="paragraph" id="S_Appendix_D"><p>Many divers keep a dive log in some form of digital file, commonly a +spreadsheet with various fields of information. These logs can be easily +imported into <em>Subsurface</em> 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 to +<em>Subsurface</em>. Creating a .CSV is straightforward, although the procedure is +somewhat different according to which spreadsheet program is used.</p></div> +<div class="paragraph"><p>Organize the diving data in the spreadsheet, so 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 number, Date, +Time, Duration, Location, GPS, Max Depth, Mean Depth, Buddy, Notes, Weight +and Tags). Organize dive data following a few simple rules:</p></div> +<div class="olist arabic"><ol class="arabic"> +<li> +<p> +Date : utiliser un des formats suivants : aaaa-mm-jj, jj.mm.aaaa, mm/jj/aaaa +</p> +</li> +<li> +<p> +Durée : le format est minutes:secondes. +</p> +</li> +<li> +<p> +Système d’unité : un seul système d’unité doit être utilisé (pas de mélange + entre les unités impériales et métriques) +</p> +</li> +<li> +<p> +Étiquettes et équipiers : les valeurs doivent être séparées par des + virgules. +</p> +</li> +<li> +<p> +Position GPS : utilisez les degrés décimaux, par exemple : 30.22496 + 30.821798 +=== <em>LibreOffice Calc</em> et <em>OpenOffice Calc</em> +</p> +</li> +</ol></div> +<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 → +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>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_ImportingCSVDives">Importing +CSV dives</a>.</p></div> +<div class="sect2"> +<h3 id="_microsoft_em_excel_em">18.1. 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 uses the new character as a separator. You 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, 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. +</p> +</li> +<li> +<p> +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>. Be sure 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. You can double check the .CSV file by opening it with a +text editor, then import the dive data as explained on the section +<a href="#S_ImportingCSVDives">Importing CSV dives</a>.</p></div> +</div> +</div> +</div> +<div class="sect1"> +<h2 id="S_APPENDIX_E">19. ANNEXE E : Créer un modèle d’impression personnalisé</h2> +<div class="sectionbody"> +<div class="paragraph"><p><em>Subsurface</em> has a way to create or modify templates for printing dive logs +to produce customized printouts of them. Templates written in HTML, as well +as a simple Grantlee instruction set, are rendered to the print device by +<em>Subsurface</em>.</p></div> +<div class="paragraph"><p>Templates are accessed using the print dialogue (see image <strong>B</strong> below).</p></div> +<div class="imageblock" style="text-align:center;"> +<div class="content"> +<img src="images/Print1_f22.jpg" alt="FIGURE: Print dialogue" /> +</div> +</div> +<div class="paragraph"><p>The buttons under the <em>Template</em> dropdown box lets you <em>Edit</em>, <em>Delete</em>, +<em>Import</em> and <em>Export</em> templates (see image <strong>A</strong> above). New or modified +templates are stored as HTML files in the same directory as the dive log +being processed. In order to create or modify a template, select one of the +templates from the template dropdown list in the print dialogue (see image +<strong>B</strong> above). Choose an existing template that resembles the final desired +printout. Then select <em>Edit</em>.</p></div> +<div class="paragraph"><p>The Edit Panel has three tabs:</p></div> +<div class="imageblock" style="text-align:center;"> +<div class="content"> +<img src="images/Template1_f22.jpg" alt="FIGURE: template edit dialogue" /> +</div> +</div> +<div class="paragraph"><p>1) The <em>Style</em> tab (image <strong>A</strong> above) controls the font, line spacing and color + template used for printing the dive log. The style attributes are + editable. Choose one of the four color palettes used for color printing.</p></div> +<div class="paragraph"><p>2) The <em>Colors</em> tab (image <strong>B</strong> above) allows editing the colors used for + printing the dive log. The colors are highly customizable: the <em>Edit</em> + buttons in the <em>Colors</em> tab allows choosing arbitrary colors for different + components of the dive log printout.</p></div> +<div class="paragraph"><p>3) The <em>Template</em> tab of the Edit Panel (see image below) allows creating a + template using HTML as well as a few Grantlee programming + primitives. Grantlee can create and format HTML code in a highly simple but + efficient way (see below). The HTML of the template can be edited and + saved. The saved template is stored in the same directory as the dive being + processed. By default, a <em>Custom</em> template is a skeleton with no specific + print instructions. The information printed needs to be specified and + formatted in the template by replacing the section marked with: "<!-- + Template must be filled -→". Writing HTML code with Grantlee instructions + allows unlimited freedom in determining what is printed and in which way it + should be rendered.</p></div> +<div class="imageblock" style="text-align:center;"> +<div class="content"> +<img src="images/Template2_f22.jpg" alt="FIGURE:Template tab" /> +</div> +</div> +<div class="paragraph"><p>You can adapt any of the existing templates and save it to the dive log +directory. The standard templates (e.g. One dive, Six dives, Table) can be +modified in this way. After completing the edits, use the <em>Export</em> button in +the print dialogue to save the new template using a new template name.</p></div> +<div class="paragraph"><p>To write a custom template, the following elements must exist so the +template will be correctly handled and rendered.</p></div> +<div class="sect2"> +<h3 id="_main_dive_loop">19.1. Main dive loop</h3> +<div class="paragraph"><p><em>Subsurface</em> exports a dive list called (<strong>dives</strong>) to the <em>Grantlee</em> back +end. It is possible to iterate over the list as follows: +.template.html</p></div> +<div class="literalblock"> +<div class="content"> +<pre><code> {% for dive in dives %} + <h1> {{ dive.number }} </h1> + {% endfor %}</code></pre> +</div></div> +<div class="literalblock"> +<div class="title">output.html</div> +<div class="content"> +<pre><code> <h1> 1 </h1> + <h1> 2 </h1> + <h1> 3 </h1></code></pre> +</div></div> +<div class="paragraph"><p>Additional information about <em>Grantlee</em> can be found at +<a href="http://www.grantlee.org/apidox/for_themers.html">here</a></p></div> +</div> +<div class="sect2"> +<h3 id="_grantlee_exported_variables">19.2. Grantlee exported variables</h3> +<div class="paragraph"><p>Only a subset of the dive data is exported:</p></div> +<div class="tableblock"> +<table rules="all" +width="100%" +frame="border" +cellspacing="0" cellpadding="4"> +<col width="50%" /> +<col width="50%" /> +<tbody> +<tr> +<td align="left" valign="top"><p class="table"><strong>Name</strong></p></td> +<td align="left" valign="top"><p class="table"><strong>Description</strong></p></td> +</tr> +<tr> +<td align="left" valign="top"><p class="table">number</p></td> +<td align="left" valign="top"><p class="table">(<strong>int</strong>) dive number</p></td> +</tr> +<tr> +<td align="left" valign="top"><p class="table">id</p></td> +<td align="left" valign="top"><p class="table">(<strong>int</strong>) unique dive ID, should be used to fetch the dive profile</p></td> +</tr> +<tr> +<td align="left" valign="top"><p class="table">date</p></td> +<td align="left" valign="top"><p class="table">(<strong>string</strong>) date of the dive</p></td> +</tr> +<tr> +<td align="left" valign="top"><p class="table">time</p></td> +<td align="left" valign="top"><p class="table">(<strong>string</strong>) time of the dive</p></td> +</tr> +<tr> +<td align="left" valign="top"><p class="table">location</p></td> +<td align="left" valign="top"><p class="table">(<strong>string</strong>) location of the dive</p></td> +</tr> +<tr> +<td align="left" valign="top"><p class="table">duration</p></td> +<td align="left" valign="top"><p class="table">(<strong>string</strong>) duration of the dive</p></td> +</tr> +<tr> +<td align="left" valign="top"><p class="table">depth</p></td> +<td align="left" valign="top"><p class="table">(<strong>string</strong>) depth of the dive</p></td> +</tr> +<tr> +<td align="left" valign="top"><p class="table">divemaster</p></td> +<td align="left" valign="top"><p class="table">(<strong>string</strong>) dive master for the dive</p></td> +</tr> +<tr> +<td align="left" valign="top"><p class="table">buddy</p></td> +<td align="left" valign="top"><p class="table">(<strong>string</strong>) buddy for the dive</p></td> +</tr> +<tr> +<td align="left" valign="top"><p class="table">airTemp</p></td> +<td align="left" valign="top"><p class="table">(<strong>string</strong>) air temperature of the dive</p></td> +</tr> +<tr> +<td align="left" valign="top"><p class="table">waterTemp</p></td> +<td align="left" valign="top"><p class="table">(<strong>string</strong>) water temperature of the dive</p></td> +</tr> +<tr> +<td align="left" valign="top"><p class="table">notes</p></td> +<td align="left" valign="top"><p class="table">(<strong>string</strong>) dive notes</p></td> +</tr> +<tr> +<td align="left" valign="top"><p class="table">rating</p></td> +<td align="left" valign="top"><p class="table">(<strong>int</strong>) dive rating which ranges from 0 to 5</p></td> +</tr> +<tr> +<td align="left" valign="top"><p class="table">sac</p></td> +<td align="left" valign="top"><p class="table">(<strong>string</strong>) SAC value for the dive</p></td> +</tr> +<tr> +<td align="left" valign="top"><p class="table">tags</p></td> +<td align="left" valign="top"><p class="table">(<strong>string</strong>) list of dive tags for the dive</p></td> +</tr> +<tr> +<td align="left" valign="top"><p class="table">gas</p></td> +<td align="left" valign="top"><p class="table">(<strong>string</strong>) list of gases used in the dive</p></td> +</tr> +<tr> +<td align="left" valign="top"><p class="table">suit</p></td> +<td align="left" valign="top"><p class="table">(<strong>string</strong>) the suit used for the dive</p></td> +</tr> +<tr> +<td align="left" valign="top"><p class="table">cylinders</p></td> +<td align="left" valign="top"><p class="table">(<strong>string</strong>) complete information of all used cylinders</p></td> +</tr> +<tr> +<td align="left" valign="top"><p class="table">cylinder0-7</p></td> +<td align="left" valign="top"><p class="table">(<strong>string</strong>) information about a specific cylinder</p></td> +</tr> +<tr> +<td align="left" valign="top"><p class="table">weights</p></td> +<td align="left" valign="top"><p class="table">(<strong>string</strong>) complete information of all used weight systems</p></td> +</tr> +<tr> +<td align="left" valign="top"><p class="table">weight0-5</p></td> +<td align="left" valign="top"><p class="table">(<strong>string</strong>) information about a specific weight system</p></td> +</tr> +<tr> +<td align="left" valign="top"><p class="table">maxcns</p></td> +<td align="left" valign="top"><p class="table">(<strong>string</strong>) maxCNS value for the dive</p></td> +</tr> +<tr> +<td align="left" valign="top"><p class="table">otu</p></td> +<td align="left" valign="top"><p class="table">(<strong>string</strong>) OTU value for the dive</p></td> +</tr> +<tr> +<td align="left" valign="top"><p class="table">sumWeight</p></td> +<td align="left" valign="top"><p class="table">(<strong>string</strong>) the summed weight of all used weight systems</p></td> +</tr> +<tr> +<td align="left" valign="top"><p class="table">startPressure</p></td> +<td align="left" valign="top"><p class="table">(<strong>string</strong>) the start pressure</p></td> +</tr> +<tr> +<td align="left" valign="top"><p class="table">endPressure</p></td> +<td align="left" valign="top"><p class="table">(<strong>string</strong>) the end pressure</p></td> +</tr> +<tr> +<td align="left" valign="top"><p class="table">firstGas</p></td> +<td align="left" valign="top"><p class="table">(<strong>string</strong>) first used gas</p></td> +</tr> +</tbody> +</table> +</div> +<div class="paragraph"><p><em>Subsurface</em> also exports <strong>template_options</strong> data. This data must be used as +<em>CSS</em> values to provide a dynamically editable template. The exported data +is shown in the following table:</p></div> +<div class="tableblock"> +<table rules="all" +width="100%" +frame="border" +cellspacing="0" cellpadding="4"> +<col width="50%" /> +<col width="50%" /> +<tbody> +<tr> +<td align="left" valign="top"><p class="table"><strong>Name</strong></p></td> +<td align="left" valign="top"><p class="table"><strong>Description</strong></p></td> +</tr> +<tr> +<td align="left" valign="top"><p class="table">font</p></td> +<td align="left" valign="top"><p class="table">(<strong>string</strong>) font family</p></td> +</tr> +<tr> +<td align="left" valign="top"><p class="table">borderwidth</p></td> +<td align="left" valign="top"><p class="table">(<strong>int</strong>) border-width value dynamically calculated as 0.1% of the page width with minimum value of 1px</p></td> +</tr> +<tr> +<td align="left" valign="top"><p class="table">font_size</p></td> +<td align="left" valign="top"><p class="table">(<strong>double</strong>) size of fonts in vw, ranges between 1.0 and 2.0</p></td> +</tr> +<tr> +<td align="left" valign="top"><p class="table">line_spacing</p></td> +<td align="left" valign="top"><p class="table">(<strong>double</strong>) distance between text lines, ranges between 1.0 and 3.0</p></td> +</tr> +<tr> +<td align="left" valign="top"><p class="table">color1</p></td> +<td align="left" valign="top"><p class="table">(<strong>string</strong>) background color</p></td> +</tr> +<tr> +<td align="left" valign="top"><p class="table">color2</p></td> +<td align="left" valign="top"><p class="table">(<strong>string</strong>) primary table cell color</p></td> +</tr> +<tr> +<td align="left" valign="top"><p class="table">color3</p></td> +<td align="left" valign="top"><p class="table">(<strong>string</strong>) secondary table cell color</p></td> +</tr> +<tr> +<td align="left" valign="top"><p class="table">color4</p></td> +<td align="left" valign="top"><p class="table">(<strong>string</strong>) primary text color</p></td> +</tr> +<tr> +<td align="left" valign="top"><p class="table">color5</p></td> +<td align="left" valign="top"><p class="table">(<strong>string</strong>) secondary text color</p></td> +</tr> +<tr> +<td align="left" valign="top"><p class="table">color6</p></td> +<td align="left" valign="top"><p class="table">(<strong>string</strong>) border colors</p></td> +</tr> +</tbody> +</table> +</div> +<div class="literalblock"> +<div class="title">template.html</div> +<div class="content"> +<pre><code> border-width: {{ template_options.borderwidth }}px;</code></pre> +</div></div> +<div class="literalblock"> +<div class="title">output.html</div> +<div class="content"> +<pre><code> border-width: 3px;</code></pre> +</div></div> +<div class="paragraph"><p>Another variable that <em>Subsurface</em> exports is <strong>print_options</strong>. This variable +contains a single member:</p></div> +<div class="tableblock"> +<table rules="all" +width="100%" +frame="border" +cellspacing="0" cellpadding="4"> +<col width="50%" /> +<col width="50%" /> +<tbody> +<tr> +<td align="left" valign="top"><p class="table"><strong>Name</strong></p></td> +<td align="left" valign="top"><p class="table"><strong>Description</strong></p></td> +</tr> +<tr> +<td align="left" valign="top"><p class="table">grayscale</p></td> +<td align="left" valign="top"><p class="table">Use <em>CSS</em> filters to convert the page into grayscale (should be added to body style to enable printing grayscale prints)</p></td> +</tr> +</tbody> +</table> +</div> +<div class="literalblock"> +<div class="title">template.html</div> +<div class="content"> +<pre><code> body { + {{ print_options.grayscale }}; + }</code></pre> +</div></div> +<div class="literalblock"> +<div class="title">output.html</div> +<div class="content"> +<pre><code> body { + -webkit-filter: grayscale(100%); + }</code></pre> +</div></div> +</div> +<div class="sect2"> +<h3 id="_defined_css_selectors">19.3. Defined CSS selectors</h3> +<div class="paragraph"><p>As the dive profile is placed after rendering, <em>Subsurface</em> uses special +<em>CSS</em> selectors to searche in the HTML output. The <em>CSS</em> selectors in the +following table should be added.</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>Selector</strong></p></td> +<td align="left" valign="top"><p class="table"><strong>Type</strong></p></td> +<td align="left" valign="top"><p class="table"><strong>Description</strong></p></td> +</tr> +<tr> +<td align="left" valign="top"><p class="table">dive_{{ dive.id }}</p></td> +<td align="left" valign="top"><p class="table">id</p></td> +<td align="left" valign="top"><p class="table">is used to fetch the relevant dive profile</p></td> +</tr> +<tr> +<td align="left" valign="top"><p class="table">diveProfile</p></td> +<td align="left" valign="top"><p class="table">class</p></td> +<td align="left" valign="top"><p class="table">each dive that will contain a dive profile should have this class selector in addition to the dive_{{ dive.id }} id selector</p></td> +</tr> +<tr> +<td align="left" valign="top"><p class="table">dontbreak</p></td> +<td align="left" valign="top"><p class="table">class</p></td> +<td align="left" valign="top"><p class="table">prevents the dive with this class from being divided into two pages. This can be used +in flow layout templates only (when data-numberofdives = 0)</p></td> +</tr> +</tbody> +</table> +</div> +<div class="admonitionblock"> +<table><tr> +<td class="icon"> +<img src="./images/icons/important.png" alt="Important" /> +</td> +<td class="content">Rendering dive profiles is not supported for flow layout templates (when +data-numberofdives = 0).</td> +</tr></table> +</div> +</div> +<div class="sect2"> +<h3 id="_special_attributes">19.4. Special attributes</h3> +<div class="paragraph"><p>There are two ways of rendering- either rendering a specific number of dives +in each page or make <em>Subsurface</em> try to fit as many dives as possible into +one page (<em>flow</em> rendering).</p></div> +<div class="paragraph"><p>The <strong>data-numberofdives</strong> data attribute is added to the body tag to set the +rendering mode.</p></div> +<div class="ulist"><ul> +<li> +<p> +render 6 dives per page: +</p> +</li> +</ul></div> +<div class="literalblock"> +<div class="content"> +<pre><code> <body data-numberofdives = 6></code></pre> +</div></div> +<div class="ulist"><ul> +<li> +<p> +render as much dives as possible: +</p> +</li> +</ul></div> +<div class="literalblock"> +<div class="content"> +<pre><code> <body data-numberofdives = 0></code></pre> +</div></div> +<div class="admonitionblock"> +<table><tr> +<td class="icon"> +<img src="./images/icons/important.png" alt="Important" /> +</td> +<td class="content">All CSS units should be in relative lengths only, to support printing on any +page size.</td> +</tr></table> +</div> +</div> +</div> +</div> +<div class="sect1"> +<h2 id="_appendix_f_faqs">20. APPENDIX F: FAQs.</h2> +<div class="sectionbody"> +<div class="sect2"> +<h3 id="S_APPENDIX_F">20.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’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 <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’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:</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">20.2. Some dive profiles have time discrepancies with the recorded samples from my dive computer…</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’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”.</p></div> +</div> +<div class="sect2"> +<h3 id="_some_dive_profiles_are_missing_from_the_download">20.3. Some dive profiles are missing from the download</h3> +<div class="paragraph" id="DC_HISTORY"><p><em>Question</em>: I cannot download all my dives, only the most recent ones, even +though my dive computer’s manual states that it records history of e.g. 999 +dives? <em>Answer</em>: Dive history is different than the dive profiles on the +log. The history only keeps track of the total number of dives and total +amount of time spent below surface. The logs, on the other hand, store the +dive profile, but they have a limited amount of memory to do so. The exact +amount of dive profiles that can be stored on the device depends on sample +interval and duration of the dives. Once the memory is full the oldest dives +get overwritten with new dives. Thus we are only able to download the last +13, 30 or 199 dives.</p></div> +<div class="paragraph"><p>If you have downloaded your dives to different dive logging software before +they were overwritten, there is a good chance that Subsurface can import +these. However, if the logs are only on your dive computer, they cannot be +salvaged after being overwritten by new dives.</p></div> +</div> +</div> +</div> +</div> +<div id="footnotes"><hr /></div> +<div id="footer"> +<div id="footer-text"> +Last updated 2016-03-12 13:57:29 CET +</div> +</div> +</body> +</html> diff --git a/Documentation/user-manual_fr.txt b/Documentation/user-manual_fr.txt index 9a42072ff..12c886571 100644 --- a/Documentation/user-manual_fr.txt +++ b/Documentation/user-manual_fr.txt @@ -27,29 +27,27 @@ rapport à d'autres solutions logicielles similaires : ou de loisir ? Utilisez-vous un enregistreur de profondeur et de durée Reefnet Sensus avec un ordinateur de plongée ? _Subsurface_ offre une interface standard pour télécharger les enregistrements des plongées à - partir de tous ces équipements de plongée et pour enregistrer et analyser + partir de tous ces équipements de plongée, en enregistrant et en analysant ces enregistrements dans un système unique. - Utilisez-vous plus d'un système d'exploitation ? _Subsurface_ est intégralement compatible avec Mac, Linux et Windows, ce qui vous permet d'accéder à vos enregistrements de plongées sur chaque système d'exploitation en utilisant une application unique. - - Utilisez-vous Linux ou Mac et votre ordinateur de plongée n'a que des + - Utilisez-vous Linux ou Mac mais votre ordinateur de plongée n'a que des logiciels pour Windows pour télécharger les informations de plongées (par exemple Mares) ? _Subsurface_ fournit un moyen de télécharger et d'analyser vos enregistrements de plongées sur d'autres systèmes d'exploitation. - Avez-vous besoin d'un planificateur de plongée graphique intuitif qui intègre et prend en compte les plongées qui ont déjà été enregistrées ? - - Avez-vous besoin d'un moyen d'enregistrer ou de sauvegarder votre carnet de - plongée sur Internet, Vous permettant de visualiser votre carnet depuis - n'importe où, en utilisant un navigateur Internet ? - -_Subsurface_ est disponible pour Windows (Win XP ou plus récent), les Macs -basés sur processeurs Intel (OS/X) et de nombreuses distributions -Linux. _Subsurface_ peut être compilé pour bien plus de plateformes -matérielles et d'environnements logiciels où Qt et libdivecomputer sont -disponibles. - -Le but de ce document est l'utilisation du programme Subsurface. Pour +Avez-vous besoin d'un moyen d'nregistrer et de sauvegarder vos plongées sur +Internet, vous permettant de les voir depuis n'importe où en utilisant un +navigateur Internet ? _Subsurface_ est disponible pour Windows (Win XP ou +plus récent), les Macs basés sur processeurs Intel (OS/X) et de nombreuses +distributions Linux. _Subsurface_ peut être compilé pour bien plus de +plateformes matérielles et d'environnements logiciels où Qt et +libdivecomputer sont disponibles. + +Ce manuel explique comment utiliser le programme _Subsurface_. Pour installer le logiciel, consultez la page _Téléchargement_ sur le http://subsurface-divelog.org/[site web de _Subsurface_]. En cas de problème, vous pouvez envoyer un e-mail sur @@ -73,44 +71,35 @@ provided: The _SEARCH_ function is activated by pressing control-F or command-F on the keyboard. A text box appears at the bottom right-hand of the window (see -image below). For instance, if one typed the word "_weights_" into the -search text box, this word will be searched for throughout this user -manual. To the right of the search text box are two arrows pointing upwards -and downwards. Selecting these allow finding, respectively, the previous and -the next occurence of the term being searched for. - +image below). For instance, typing the word "_weights_" into the search +text box, searches throughout the user manual. To the right of the search +text box are two arrows pointing up and down. These find the previous and +the next occurrence of the search term. image::images/usermanualfunctions.jpg["User manual functions", align="center"] -_PREVIOUS/NEXT LINK_. One can move between links (underlined words allowing -one to jump to specific sections in this user manual) by right-clicking on -the text of the manual. This brings up a context menu for jumping to -previous links selected while reading the manual (see image above). For -instance if a link in the manual has been selected, then the option to _Go -Back_ shows the text at the last link that was selected (similar to the -Previous Page button in a browser). Conversely the _Go Forward_ option -enables jumping to the text perused before selecting the _Go Back_ -option. The _Reload_ option causes the complete user manual to be reloaded -into the user manual window. - +_PREVIOUS/NEXT LINK_. Move between links (underlined words that jump to +specific sections in the user manual) by right-clicking on the text of the +manual. This brings up a context menu to previous links selected. (see +image above). For instance if a link has been selected, then the option to +_Go Back_ shows the text at the last link selected (similar to the Previous +Page button in a browser). Conversely the _Go Forward_ option jumps to the +text seen before selecting the _Go Back_ option. The _Reload_ option reloads +the complete user manual into the window. [[S_UserSurvey]] Le sondage utilisateur ---------------------- -Dans le but de développer _Subsurface_ d'une manière qui serve ses -utilisateurs de la meilleur manière qu'il soit, il est important d'avoir des -informations sur les utilisateurs. À l'ouverture de _Subsurface_ après avoir -utilisé le logiciel pendant une semaine environ, une fenêtre de sondage -apparait. Cela est complètement optionnel et l'utilisateur contrôle quelles -informations sont envoyées ou non à l'équipe de développement de -_Subsurface_. Toutes les données que l'utilisateur choisit d'envoyer sont -extrêmement utiles et ne seront utilisées que pour les futures -développements et modifications du logiciel pour coller au mieux aux besoins -des utilisateurs de _Subsurface_. Si vous complétez le sondage ou cliquez -sur l'option pour ne plus être sondé, cela devrait être la dernière -communication de ce type que vous recevrez. Cependant, si vos habitudes de -plongées ou d'utilisation de Subsurface changent, vous pouvez envoyer un -nouveau sondage en démarrant _Subsurface_ avec l'option _--survey_ sur la -ligne de commande. +In order to develop _Subsurface_ to serve its users in the best possible +way, it’s important to have user information. Upon launching _Subsurface_ +and using the 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. All data the user sends is useful, and +will only be used to steer future development and to customize the software +to fit the needs of the _Subsurface_ users. If you complete the survey, or +click the option not to be asked again, that should be the last +communication of this type you receive. However, if your diving and/or +subsurface habits change and you wish to fill in another survey, just launch +_Subsurface_ with the _--survey_ option on the command line. [[S_StartUsing]] Commencer à utiliser le programme @@ -121,47 +110,40 @@ principal* (Fichier Importer Journal Vue Aide) en haut de la fenêtre (pour Windows et Linux) ou en haut de l'écran (pour Mac et Ubuntu Unity). Les quatre panneaux sont : -La *liste des plongées* en bas à gauche, contenant une liste de toutes les -plongées du journal (carnet) de plongées de l'utilisateur. Une plongée peut -être sélectionnée et mise en surbrillance dans la liste en cliquant -dessus. Dans la plupart des cas, les touches haut/bas peuvent être utilisée -pour passer d'une plongée à l'autre. La *liste des plongées* est un outil -important pour manipuler un journal (carnet) de plongée. - -La *carte de plongée* en bas à droite, affiche les sites de plongées de -l'utilisateur, sur une carte mondiale et centrée sur le site de la dernière -plongée sélectionnée dans la *liste des plongées*. - -Les *informations* en haut à gauche, fournissent des informations détaillées -sur la plongée sélectionnée dans la *liste des plongées*, dont des -statistiques pour la plongée sélectionnée ou pour toutes les plongées mises -en surbrillance. - -Le *profil de plongée* en haut à droite, affiche un profil de plongée -graphique de la plongée sélectionnée dans la *liste des plongées*. - -Les séparateurs entre ces panneaux peuvent être déplacés pour modifier la -taille de chaque panneau. _Subsurface_ mémorise la position de ces -séparateurs, pour qu'au prochain lancement _Subsurface_ utilise ces -positions. - -Si une unique plongée est sélectionnée dans la *liste des plongées*, -l'emplacement de la plongée, les informations détaillées et le profil de la -_plongée sélectionnée_ sont affichées dans les panneaux respectifs. D'autre -part, si plusieurs plongées sont sélectionnées, la dernière mise en -surbrillance est la _plongée sélectionnée_, mais les données de _toutes les -plongées mises en surbrillances_ sont affichées dans l'onglet *Stats* du -panneau *informations* (profondeur maximale, minimale et moyenne, les -durées, les températures de l'eau et le SAC (air consommé); temps total et -nombre de plongées sélectionnées). +The *Dive List* on the bottom left, showing 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* on the bottom right, showing the user's dive sites on a world +map and centered on the site of the last dive selected in the *Dive List*. + +The *Info* on 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* on the top right, showing a graphical dive profile of the +selected dive in the *Dive List*. + +The dividers between panels can be dragged 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 the last +time the program was used. + +If a single dive is selected in the *Dive List*, the dive location, detailed +information and profile of the _selected dive_ are shown in the respective +panels. If several dives are selected, the last highlighted dive is the +_selected dive_, but summary data of all _highlighted dives_ is shown in the +*Stats* tab of the *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_f22.jpg["The Main Window", align="center"] -L'utilisateur peut déterminer si lesquels des quatre panneaux sont affichés -en sélectionnant l'option *Vue* dans le menu principal. Cette fonctionnalité -permet plusieurs choix d'affichage : +The user decides which of the four panels are displayed by selecting the +*View* option on the main menu. This feature has several choices of display: *Tout* : affiche les quatre panneaux tels que sur la capture d'écran ci-dessus. @@ -172,43 +154,37 @@ permet plusieurs choix d'affichage : *Info* : affiche uniquement les notes de plongées de la dernière plongée sélectionnée et les statistiques pour toutes les plongées mises en surbrillance. -*Globe* : affiche uniquement la carte mondiale, centrée sur la dernière plongée sélectionnée. +*Globe*: Show only the world map, centered on the last selected dive. -Comme la plupart des autre fonctions qui peuvent être accédée via le menu -principal, ces options peuvent être utilisées par des raccourcis -clavier. Les raccourcis pour un système particulier sont affichés avec un -souligné des les entrées de menu. À cause des différents systèmes -d'exploitation et des divers langues, _Subsurface_ peut utiliser différentes -touches de raccourcis et ne sont donc pas détaillées ici. +Like other functions that can be accessed via the Main Menu, these options +can also 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’s chosen language +may cause _Subsurface_ to use different shortcut keys, they are not listed +in this user manual. -Lorsque le programme est lancé pour la première fois, il n'affiche aucune -information. Ceci parce que le programme n'a aucune information de plongée -disponible. Dans les sections suivantes, le procédure pour créer a nouveau -carnet de plongée sera détaillée. +When the program is started for the first time, it shows no information at +all, because it does not have any dive information available. In the +following sections, the procedures to create a new logbook will be +explained. [[S_NewLogbook]] Créer un nouveau carnet de plongée ---------------------------------- -Sélectionner _Fichier -> Nouveau carnet de plongée_ à partir du menu -principal. Toutes les données de plongées sont effacées pour que de -nouvelles puissent être ajoutées. S'il existe des données non encore -enregistrées dans le carnet ouvert, l'utilisateur devra sélectionner s'il -faut les enregistrer ou non avant de créer le nouveau carnet. +Select _File -> New Logbook_ from the main menu. All existing dive data are +cleared so 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]] == Enregistrement des informations de plongée dans le carnet - -Maintenant qu'un nouveau carnet de plongée a été créé, il est simple de lui -ajouter des données. _Subsurface_ permet plusieurs façons pour ajouter des -données de plongée au carnet. Plus de détails dans les sections suivantes. - +Now that a new logbook is created, it is simple to add dive data it. +_Subsurface_ allows several ways of adding dive data to a logbook. 1) Si l'utilisateur possède un carnet manuscrit, un tableur ou une autre forme de carnet maintenu manuellement, les données de plongée peuvent être ajoutées au carnet en utilisant une des approches suivantes : - - - Entrer les informations de plongée à la main. Cela est utile si le plongeur - n'a pas + - Enter dive information by hand. This is useful if the diver didn’t utilisé d'ordinateur de plongée et que les plongées sont inscrites dans un carnet manuscrit. Voir xref:S_EnterData[Entrer les informations de plongée à la main] @@ -218,12 +194,9 @@ données de plongée au carnet. Plus de détails dans les sections suivantes. soit dans un fichier CSV. Se reporter à : xref:S_Appendix_D[ANNEXE D : Exporter un tableur vers le format CSV] et à xref:S_ImportingCSVDives[Importer des plongées au format CSV]. - -2) Si les plongées ont été enregistrées en utilisant un ordinateur de plongée, - le profil de profondeur de la - plongée et de nombreuses informations supplémentaires peuvent être - utilisées. Ces plongées peuvent être importées à partir de : - +If a dive is recorded using a dive computer, the depth profile and a large +amount of additional information can be accessed. These dives can be +imported from: - L'ordinateur de plongée lui-même. Voir : xref:S_ImportDiveComputer[Importer de nouvelles informations de plongée à partir de l'ordinateur de plongée] ou @@ -231,9 +204,7 @@ données de plongée au carnet. Plus de détails dans les sections suivantes. plongée. Voir xref:S_ImportingAlienDiveLogs[Importer les informations à partir d'autres sources de données numériques ou d'autres formats de données]. - - - Importer à partir d'un tableur ou de fichiers CSV contenant les profils de - plongées. + - Spreadsheet or CSV files containing dive profiles. Voir : xref:S_ImportingCSVDives[Importer les plongées au format CSV à partir des ordinateurs de plongées ou d'autres logiciels de carnet de plongée] @@ -244,19 +215,18 @@ données de plongée au carnet. Plus de détails dans les sections suivantes. 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 +duration, depth, the names of your dive buddy and 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 *Info* panel -(*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. +information for each dive. To add a dive to a dive log, select _Log -> Add +Dive_ from the Main Menu. The program then shows three panels on which to +enter information for a dive: two tabs in the *Info* panel (*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_f22.jpg["FIGURE: Add dive", align="center"] - -When one edits a field in Notes or Equipment panels, _Subsurface_ enters +When you edit a field in Notes or Equipment panels, _Subsurface_ enters *Editing Mode*, indicated by the message in the blue box at the top of the *Notes* panel (see the image below). This message is displayed in all the panels under Notes and Equipment when in *Editing Mode*. @@ -267,56 +237,54 @@ The _Apply changes_ 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 _Apply changes_ 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. +information for this specific dive is saved in memory. The _Apply changes_ +button should ONLY be selected after all parts of a dive have been +entered. When you close Subsurface, the program will ask again, this time +whether the complete dive log should be saved on disk or not. [[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 +function of time) is shown 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: +best represent the dive 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 right-angled red lines as shown -below. The time and depth represented by the cursor 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. Drag -the waypoints to represent an accurate time duration for the dive. Below is -a dive profile for a dive to 20 m for 30 min, followed by a 5 minute safety -stop at 5 m. +profile, its position is shown by two right-angled red lines as seen below. +The time and depth represented by the cursor 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 you need to drag the appropriate waypoints downward to 20 m. To add a +waypoint, double-click on any line segment. To move an additional waypoint, +drag it. To remove a waypoint, right-click on it and choose "Remove this +point" from the context menu. Drag the waypoints to represent an accurate +time duration for the dive. Below is a dive profile for 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 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 (see image below). +_Specifying the gas composition:_ The gas composition used is 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 above. The gas mixtures of segments of the dive profile can be +changed 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 (see image below). image::images/DiveProfile3_f20.jpg["FIGURE: Gas composition context menu", align="center"] -With the profile having been defined, more details must be added in order to -have a fuller record of the dive. To do this, the *Notes* and the -*Equipment* tabs on the top left hand of the _Subsurface_ window should be -used. Click on xref:S_Notes_dc[*this link*] for instructions to use these -tabs. - +With the profile now defined, more details must be added to have a fuller +record of the dive. To do this, the *Notes* and the *Equipment* tabs on the +top left hand of the _Subsurface_ window should be used. Click on +xref:S_Notes_dc[*this link*] for instructions on how to use these tabs. [[S_ImportDiveComputer]] === Importer de nouvelles informations de plongée à partir de l'ordinateur de plongée @@ -325,37 +293,36 @@ tabs. 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: +capture this information, using dive details 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. +Several dive computers consume more power when they are in PC-Communication +mode. **This could drain the dive computer's battery**. We recommend the +user checks to be sure 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. +_Subsurface_, the two pieces of equipment must 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. To set up this communication, users need 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 +A] provides the technical information to help the user achieve 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: +After this, the dive computer can be hooked up to the user's PC using 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) @@ -369,12 +336,12 @@ be achieved by following these steps: image::images/DC_import_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, if the dive computer allows this, _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). +Dive computers tend to keep a certain number of dives in memory, even though +these dives have already been imported to _Subsurface_. For that reason, if +the dive computer allows this, _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). - 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, @@ -389,16 +356,15 @@ least for those not charging while connected via USB). 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. + a specific 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 + panel. If one or more of your dives in _Subsurface_ has 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 + the dive computer, this box needs to be checked. 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 @@ -407,37 +373,36 @@ least for those not charging while connected via USB). - 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 dive in the _Subsurface_ - divelog will be overwritten by the dive record from the dive computer. + divelog will be overwritten by the dive record from the computer. - The checkbox marked _Download into new trip_ ensures that, after upload, the downloaded dives are grouped together as a new trip(s) in the *Dive List*. - 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). - - - Then select the _Download_ button. With communication established, one can + when there are problems with downloads(see below). + - Then select the _Download_ button. With communication established, you 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. 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). After successful download, Dialogue - *B* in the figure above appears. After the dives have been downloaded, they - appear in a tabular format on the right-hand side of the dialogue (see image - *B*, above). Each dive comprises a row in the table, with the date, duration - and depth shown. Next to each dive is a checkbox: check all the dives that - need to be transferred to the *Dive List*. In the case of the image above, - the last six dives are checked and will be transferred to the *Dive - List*. Then click the _OK_ button at the bottom of the dialogue. 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. + bottom of the dialogue. Remember for some dive computers progress + information could be inaccurate since the program doesn’t know how much + downloadable data there is until the download is complete. After successful + download, Dialogue *B* in the figure above appears. After the dives have + been downloaded, they appear in a tabular format on the right-hand side of + the dialogue (see image *B*, above). Each dive comprises a row in the table, + with the date, duration and depth shown. Next to each dive is a checkbox: + check all the dives that need to be transferred to the *Dive List*. In the + case of the image above, the last six dives are checked and will be + transferred to the *Dive List*. Then click the _OK_ button at the bottom of + the dialogue. 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. -After this has been completed, select the OK button. The checked dives are -transferred to the *Dive List*. +Then click the OK button. The checked dives are transferred to the *Dive +List*. - 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 @@ -452,38 +417,37 @@ 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 dive computer’s battery fully charged? If not then charge or replace + it. - - 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? + - Is the connecting cable faulty? Does the cable work 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). + A] to be sure 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 +If the _Subsurface_ computer does not recognize 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: +possibility the cable or USB adaptor is faulty. A faulty cable is the most +common cause of communication failure between a dive computer and +_Subsurface_ computer. It’s also possible the _Subsurface_ computer cannot +interpret the data. Perform a download for diagnostic purposes with the +following two 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_ +during the download process. Under normal circumstances they should not be checked. +When checking these boxes, the user is prompted to select a folder where the information will be saved. The default folder is the one in which the +_Subsurface_ dive log is kept. *Important:* _After downloading with the above checkboxes @@ -495,7 +459,7 @@ checked, no dives are added to the 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 +analyzed. Provide the dive computer make and model as well as contextual information about the dives recorded on the dive computer. **** @@ -504,60 +468,52 @@ information about the dives recorded on the dive computer. [icon="images/icons/bluetooth.jpg"] Bluetooth is becoming a more common way of communication between dive -computers and _Subsurface_, for instance, the Shearwater Petrel Mk2 and the -OSTC Mk3. _Subsurface_ provides a largely operating system independent +computers and _Subsurface_, for or instance, the Shearwater Petrel Mk2 and +the OSTC Mk3. _Subsurface_ provides a largely operating system independent Bluetooth interface. Setting up _Subsurface_ for Bluetooth communication requires four steps: -- Ensure that Bluetooth is activated on the host computer running - _Subsurface_. -- Ensure that _Subsurface_ sees the Bluetooth adapter on the host computer. -- Ensure the Bluetooth-enabled dive computer is Bluetooth-discoverable and in +- Be sure Bluetooth is activated on the host computer running _Subsurface_. +- Be sure _Subsurface_ sees the Bluetooth adapter on the host computer. +- Be sure the Bluetooth-enabled dive computer is Bluetooth-discoverable and in PC upload mode. -- Ensure that _Subsurface_ is paired with the Bluetooth-enabled dive computer. +- Be sure _Subsurface_ is paired with the Bluetooth-enabled dive computer. Select the Download dialogue by selecting _Import -> Import from dive -computer_ from the *Main Menu*. If one checks the check box labelled -_"Choose Bluetooth download mode"_, the dialogue below appears. - +computer_ from the *Main Menu*. If you check the box labelled _"Choose +Bluetooth download mode"_, the dialogue below appears. ===== Sur Linux ou MacOS : image::images/DC_import_Bluetooth.jpg["FIGURE: Download Bluetooth", align="center"] On the _Linux_ or _MacOS_ platforms the name of the _Subsurface_ computer -and its Bluetooth address are shown on the right-hand side, On the lefthand +and its Bluetooth address are shown on the right hand side, On the left hand side, if the computer has connected more than one local Bluetooth devices the user can use the list box to indicate which one needs to connect to _Subsurface_. The power state (on/off) of the Bluetooth adapter is shown -below the address and can be changed by checking the _Turn on/off_ check -box. - -If the Bluetooth address is not shown, then _Subsurface_ does not see the -local Bluetooth device. Ensure that the Bluetooth driver is installed -correctly on the _Subsurface_ computer and check if it can be used by other -Bluetooth utilities like _bluetoothctl_ or _bluemoon_. This achieves the -first two steps above. - -Ensure that the Bluetooth-enabled dive computer is in PC-upload mode and -that it is discoverable by other Bluetooth devices. Consult the manual of -the dive computer to perform this. Now the third item in the list above has -been achieved. - -Select the _Scan_ button towards the bottom left of the dialogue -above. After searching for a small amount of time, the dive computer should -be listed (perhaps as one of a number of Bluetooth devices) in the main list -box on the lefthand side of the dialogue (see image above). If this is not -achieved, select the _Clear_ button and then scan again for Bluetooth -devices using the _Scan_ button. After performing these actions _Subsurface_ -should see the dive computer. The label of the discovered dive computer -contains the name of the device, its address and its pairing status. If the -device is not paired and has a red background colour, a context menu can be -opened by selecting the item with a right-click. Select the the _Pair_ -option and wait for the task to complete. If this dive computer is being -paired to Subsurface for the first time, it is possible that Subsurface will -request a Pass Code or PIN number. The most commonly-used Pass Code is 0000, -and this works for the Shearwater Petrel. If necessary, consult the user -manual of the dive computer being used. +below the address and can be changed by checking the _Turn on/off_ box. If +the Bluetooth address is not shown, then _Subsurface_ does not see the local +Bluetooth device. Be sure the Bluetooth driver is installed correctly on the +_Subsurface_ computer and check if it can be used by other Bluetooth +utilities like _bluetoothctl_ or _bluemoon_. This finishes the first two +steps above. Be sure the Bluetooth-enabled dive computer is in PC-upload +mode and it is discoverable by other Bluetooth devices. Consult the manual +of the dive computer for more information. Now the third item in the list +above has been finished. Select the _Scan_ button towards the bottom left +of the dialogue above. After searching, the dive computer should be listed +(perhaps as one of a number of Bluetooth devices) in the main list box on +the lefthand side of the dialogue (see image above). If this does not work, +select the _Clear_ button, then scan again for Bluetooth devices using the +_Scan_ button. After taking these actions _Subsurface_ should see the dive +computer. The label of the discovered dive computer contains the name of +the device, its address and its pairing status. If the device is not paired +and has a red background color, a context menu can be opened by selecting +the item with a right-click. Select the the _Pair_ option and wait for the +task to complete. If this dive computer is being paired to Subsurface for +the first time, it’s possible Subsurface will request a Pass Code or PIN +number. The most commonly-used Pass Code is 0000, and this works for the +Shearwater Petrel. If necessary, consult the user manual of the dive +computer being used. **** [icon="images/icons/important.png"] @@ -580,41 +536,40 @@ One way to achieve this is to use +bluetoothctl+: [agent] Enter PIN code: 0000 **** -After the devices are paired the _Save_ button of the dialogue can be -pressed. This closes the Bluetooth dialogue. Now select _Download_ in the -_Download from dive computer_ dialogue which should still be open. The -downloaded dives are shown on the righthand side of the download dialogue. +After the devices are paired, press the _Save_ button of the dialogue. This +closes the Bluetooth dialogue. Now select _Download_ in the _Download from +dive computer_ dialogue which should still be open. The downloaded dives are +shown on the righthand side of the download dialogue. ===== Sur Windows : image::images/DC_import_Bluetooth_Windows.png["FIGURE: Download Bluetooth on Windows", align="center"] On _Windows_ platforms the _Local Bluetooth device details section_ on the -right is not displayed as is the case on the Linux/Mac implementations. To -successfully initiate a scan (by pressing the _Scan_ button) check that the -Bluetooth device on the _Subsurface_ computer is turned on by selecting the -dive computer from the list of available Bluetooth devices (see image -above). If the dive computer is accessed by Subsurface for the first time, -it is possible that Subsurface will request a Pass Code/PIN number. Supply -the Pass Code recommended in the user manual of the dive computer. A Pass -Code of 0000 is often appropriate. +right is not displayed as is the case on the Linux/Mac systems. To start a +scan (by pressing the _Scan_ button) check that the Bluetooth device on the +_Subsurface_ computer is turned on by selecting the dive computer from the +list of available Bluetooth devices (see image above). If the dive computer +is being accessed by Subsurface for the first time, it’s possible Subsurface +will request a Pass Code or PIN number. Supply the Pass Code recommended in +the user manual of the dive computer. A Pass Code or PIN of 0000 is often +the default. The pairing step is checked and done automatically during the download process. If the devices have never been paired the system will ask for your -permissions and put a message on the right side of the screen: _Add a -device, Tap to set up your DC device_. Always allow this pairing. After a -discovered item is selected, select the _Save_ button. Finally select the -_Download_ button on the _Download_ dialogue and wait for the process to -complete. +permission and put a message on the right side of the screen: _Add a device, +Tap to set up your DC device_. Always allow this pairing. After a discovered +item is selected, select the _Save_ button. Finally select the _Download_ +button on the _Download_ dialogue and wait for the process to complete. [icon="images/icons/important.png"] [IMPORTANT] Currently _Subsurface_ works only with local Bluetooth adapters which use Microsoft Bluetooth Stack. If the local device uses _Widcomm_, _Stonestreet -One Bluetopia Bluetooth_ or _BlueSoleil_ drivers it will definitely not -work. However, Bluetooth hardware/dongles from these manufacturers -(e.g. iSonic) that support the Microsoft Bluetooth Stack do work. +One Bluetopia Bluetooth_ or _BlueSoleil_ drivers it will not work. However, +Bluetooth hardware/dongles from these manufacturers (e.g. iSonic) that +support the Microsoft Bluetooth Stack do work. -A log messageOn the bottom left of the _Remote Bluetooth device selection_ +A log message on the bottom left of the _Remote Bluetooth device selection_ shows details about the current status of the Bluetooth agent. To select another dive computer for download using the "Remote Bluetooth selection dialogue" press the three-dots button from the _"Choose Bluetooth download @@ -635,59 +590,58 @@ with _Subsurface_. ==== 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, consider 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. +upload dive logs to _Subsurface_. For instance if a buddy’s dive computer is +the same make and model as your own and dive logs are uploaded from both +dive computers to the same _Subsurface_ computer, then you might like to +call one "Alice's Suunto D4" and the other "Bob's Suunto D4". Alternatively, +consider a technical diver who 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 "Suunto D4 +(2)". This is easily done in _Subsurface_. On the *Main Menu*, select _Log +-> Edit device names_. A dialog box opens, showing 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. With the uploaded dives in the *Dive List*, 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 *Notes* and the *Equipment* tabs -on the top left hand of the _Subsurface_ window should be used. +computer is not complete and more details must be added to have a full +record of the dives. To do this, the *Notes* and the *Equipment* tabs on the +top left hand of the _Subsurface_ window should be used. [[S_Notes_dc]] ===== Notes -To have a more complete dive record the user needs to add additional +To have a more complete dive record, the user needs to add additional information by hand. The procedure below is virtually identical for hand-entered dives and for dives downloaded from a dive computer. -In some cases, one has to provide the date and time of the dive, e.g. when -entering a dive by hand or when a dive computer does not provide the date -and time of the dive. (Usually the date and time of the dive, gas mixture -and water temperature are shown as obtained from the dive computer) If the -contents of the *Notes 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 *Notes* tab, the following fields are visible +In some cases, you must provide the date and time of the dive, for example +when entering a dive by hand or when a dive computer doesn’t provide the +date and time of the dive. (Usually the date and time of the dive, gas +mixture and water temperature are shown as obtained from the dive computer) +If the contents of the *Notes tab* is changed or edited in any way, the +message in a blue box at the top of the panel shows the dive is being +edited. If you click on the *Notes* tab, the following fields are visible (left hand image, below): image::images/AddDive3_f22.jpg["FIGURE: The Notes tab", align="center"] The right hand image, above, shows a *Notes tab* filled with dive information. 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 +clicking the date, a calendar is displayed from which you 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 over-typing the information displayed. *Air/water temperatures*: Air and water temperatures during the dive are shown in text boxes to the right of the Start time. Many dive computers supply water -temperature information and this box may therefore contain information. -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. +temperature information and this box may have information. +If air temperature isn’t provided by the dive computer, the first temperature reading +might be used for the air temperature. Generally this is close to the real air temperature. If editing is required, only a value is required, the units of temperature will be automatically supplied by _Subsurface_ (following the _Preferences_, metric or imperial units will @@ -697,50 +651,47 @@ be used). [icon="images/icons/warning2.png"] [WARNING] Dive locations are managed as a *separate* part of the dive log. The dive -information in the *Notes* and *Equipment* tabs can therefore not be edited +information in the *Notes* and *Equipment* tabs can therefore NOT be edited at the same time as the dive site information. Save all the other dive information (e.g. divemaster, buddy, protective gear, notes about the dive) -by selecting _Apply changes_ on the *Notes* tab before editing the dive site -information. Only then, supply a dive site name in the textbox labelled -_Location_ on the *Notes* tab. - -Type the name of the dive site, e.g. "Tihany, Lake Balaton, Hungary". If -several dives are performed at the same location, the dive site information -for the first dive is re-used. Existing dive location information can be -edited at any time by selecting (on the *Dive List* panel) a dive performed -at that site and by opening the location information by clicking the globe -button on the right of the location name (see image on the right, -above). When entering a dive location name, auto location of dive site names -makes it easy to select an existing dive site name (i.e. when typing the -name of a dive site, a dropdown list appears showing all sites with similar -names). If the dive site has been used before, click on the already-existing -name. The dive site names in the dropdown list contain either a globe -symbol (indicating existing dive sites in the _Subsurface_ database) or a -*+* symbol (indicating dive site names that appear consistent with the -current dive site name but which have not been added to the dive site -database). Therefore, if the present dive site has not been used before, a -message appears as follows (image *A* below): +by selecting _Apply changes_ on the *Notes* tab BEFORE editing the dive site +information. Then supply a dive site name in the textbox labelled _Location_ +on the *Notes* tab. + +Type in the name of the dive site, e.g. "Tihany, Lake Balaton, Hungary". If +several dives are made at the same location, the site information for the +first dive is re-used. Existing dive locations can be edited by selecting +(on the *Dive List* panel) a dive done at that site and by opening the +location information. Click the globe button on the right of the location +name (see image on the right, above). When entering a dive location name, +auto location of dive site names makes it easy to select an existing dive +site name. When typing the name of a dive site, a dropdown list appears +showing all sites with similar names. If the dive site has been used before, +click on the already-existing name. The dive site names in the dropdown +list contain either a globe symbol (indicating existing dive sites in the +_Subsurface_ database) or a *+* symbol (indicating dive site names that +appear consistent with the current dive site name but which haven’t been +added to the dive site database). If the present dive site has not been +used before, a message appears as follows (image *A* below): image::images/Locations1_f22.jpg["FIGURE:Location description panel", align="center"] Doubleclick on the new dive site name. A panel appears to enter the -coordinates and other important information about the site (image *B*, -above). The most important items are the coordinates of the site. There are -three ways of specifying the coordinates: - -a. One can find the coordinates on the world map in the bottom right hand part - of the _Subsurface_ window. The map displays an orange bar indicating "No - location data - Move the map and double-click to set the dive - location". Upon a doubleclick at the appropriate place, the orange bar - disappears and the coordinates are stored. - -b. The coordinates can be obtained from the _Subsurface_ Companion app if the - user has an Android or iPhone device with GPS and if the coordinates of the - dive site were stored using that device. xref:S_Companion[Click here for - more information] - -c. The coordinates can be entered by hand if they are known, using one of four - formats with latitude followed by longitude: +coordinates and other information about the site (image *B*, above). The +most important items are the coordinates of the site. There are three ways +to specify coordinates: + +a. Use the world map in the bottom right hand part of the _Subsurface_ + window. The map displays an orange bar indicating "No location data - Move + the map and double-click to set the dive location". Doubleclick at the + appropriate place, and the orange bar disappears and the coordinates are + stored. + +b. Use the _Subsurface_ Companion app if you have an Android or iPhone device + with GPS and if the dive site coordinates were stored using it. + xref:S_Companion[Click here for more information] +c. Enter by hand if the coordinates 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, @@ -751,86 +702,85 @@ 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. Some keyboards don't have the degree sign (°). It can be replaced by a *d* like this: N30d -W20d. If both a dive site name and coordinates have been provided, Save the +W20d. If both a dive site name and coordinates have been provided, save the dive site information by selecting the button _Apply changes_ at the top of the panel. -*Important*: GPS coordinates of a dive site are linked to the Location -name - so *saving* a dive site with only coordinates and no dive site name -causes unexpected behaviour (Subsurface will think that all of these +*Important*: GPS coordinates of a dive site are linked to the location +name - so *saving* a dive site with only coordinates and no name +causes problems. (Subsurface will think all of these dives have the same location and try to keep their GPS coordinates the same). *Dive site name lookup:* If coordinates have been typed into the appropriate -text box, one can perform an automated name lookup based on the coordinates. -This is achieved when _Subsurface_ uses the Internet to find the name of the dive site +text box, you can do an automated name lookup based on the coordinates. +This is done when _Subsurface_ uses the Internet to find the name of the dive site based on the coordinates that were typed. If a name has been found, it is automatically inserted into the tags box. The list box (Titled _Dive sites on same coordinates_") at the bottom of the dive site panel contains the names of other dives sites used at the current location. For instance if the dive site is "Blue Hole" and there are several -dive sites named "Blue Hole", all these sites are listed in this list box. +sites named "Blue Hole", all of them are listed. -Enter any other textual information about the dive site (Description and +Enter any other contextual information about the dive site (Description and Notes), then select _Apply Changes_ to save the geolocation for this dive -site. At a later stage the dive site information can be edited by clicking -the globe icon to the right of the dive site name in the *Notes tab*. +site. The dive site information can later be edited by clicking the globe +icon to the right of the dive site name in the *Notes tab*. -*Dive mode*: This is a dropdown box allowing one to choose the type of dive -performed. The options are OC (Open Circuit SCUBA, the default seting, meant for most recreational dives), +*Dive mode*: This is a dropdown box allowing you to choose the type of dive +performed. The options are OC (Open Circuit SCUBA, the default setting, for most recreational dives), Freedive (dive without SCUBA equipment), CCR (Closed-circuit rebreather) and pSCR (Passive semi-closed rebreather). -*Divemaster*: The name of the dive master or dive guide for this dive should be +*Divemaster*: The name of the divemaster or dive guide should be entered in this field which offers auto selection 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 +*Buddy*: In this field, enter the name(s) of the buddy or buddies +(separated with commas) who were on the dive. Auto selection based on the list of buddies in the current logbook is offered. *Suit*: Here the type of dive suit used can be entered. Auto selection of the suit description is available. Some dry-suit users may choose to use this field to record what combination of -suit and thermal undersuit was used. +suit and thermal under suit was used. -*Rating*: One can provide a subjective overall rating of the dive on a +*Rating*: You 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 +*Visibility*: You 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 +*Tags*: Tags that describe the type of dive done 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 +_Subsurface_ has many built-in tags. If you 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. +will list the tags that correspond to the typing. For instance, by typing ++cav+, the tags *cave* and *cavern* are shown to choose from. *Notes*: Any additional information for the dive can be entered here. The _Apply changes_ and _Discard changes_ 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. The image xref:S_Notes_dc[at the beginning of this section] shows an -example of a *Notes tab* after completion of the dive information. +information for tabs in the *Info* panel and in the *Dive Profile* +panel. Use them when *ALL* other information has been added. The image +xref:S_Notes_dc[at the beginning of this section] shows an example of a +*Notes tab* after completing the dive information. ===== 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 +The Equipment tab lets you enter information about the type of cylinder and +gas used, as well as the weights used for the dive. The message in the blue box at the top of the panel: image::images/BlueEditBar_f22.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). +shows the dive is being edited. This is a highly interactive part of +_Subsurface_ and the information on cylinders and gases (entered here) +determines the behavior of the *Dive profile* (top right-hand panel). [[cylinder_definitions]] *Cylinders*: The cylinder information is entered through a dialogue that looks @@ -839,23 +789,21 @@ like this: image::images/DC_gas-dialogue1_f20.jpg["FIGURE: Initial cylinder dialogue", align="center"] For hand-entered dives, this information needs to be typed in. For dive -computers, _Subsurface_ often obtains the gas used from the dive computer -and automatically inserts the gas composition(% oxygen or % helium) 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 _Type_ box should be clicked. This -brings up a list button that can be used to display a dropdown list of -cylinders: +computers, _Subsurface_ often gets the gas used from the dive computer and +automatically inserts the gas composition(% oxygen or % helium) in the +table. The + button at the top right lets you add more cylinders for this +dive. The dark dust bin icon on the left lets you delete 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. Start by selecting a cylinder type on the +left-hand side of the table. To select a cylinder, the _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 +used for this dive, or just 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 (_Work.press_) will automatically be shown in the dialogue. @@ -871,14 +819,14 @@ inappropriate fields should be left empty. After typing the information for the cylinder, save the data either by pressing _ENTER_ on the keyboard or by clicking outside the cell containing 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): +hand. The 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 +using a dialogue similar to that of the cylinder information. If you +click the + button on the top right of the weights dialogue, the table looks like this: @@ -889,44 +837,44 @@ a down-arrow: image::images/WeightsDataEntry2_f20.jpg["FIGURE:Weights type drop-down list button", align="center"] This can be used to select the type of weight system used during the dive or -the user may start typing in the box to specify a different weighting -mechanism that will be saved by _Subsurface_. In the *Weight* field, type -in the amount of weight used during the dive. After specifying the weight -system, save the data by either pressing _ENTER_ on the keyboard or by -clicking 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: +just may start typing in the box to specify a different weighting mechanism +that will be saved by _Subsurface_. In the *Weight* field, type in the +amount of weight used during the dive. After specifying the weight system, +save the data by pressing _ENTER_ on the keyboard or by clicking outside the +cell with the cursor. It’s 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 dust bin 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 -each uploaded dive is shown in the *Dive profile* tab, as well as a few -items of information in the *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 *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 *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. +each is shown in the *Dive profile* tab, as well as a few items of +information in the *Notes* tab (e.g. water temperature) and in the +*Equipment* tab (e.g. gas pressures and gas composition). Other fields +remain empty. It may be useful to simultaneously edit some of the fields in +the *Notes* and *Equipment* tabs. For instance, it’s possible that a diver +performed several dives during a single day, using identical equipment at +the same dive site, or with the same divemaster and/or buddy or +tags. Instead of completing the information for each dive separately, select +all the dives for that day in the *Dive List* and insert the same +information in the *Notes* and *Equipment* fields that need identical +information. This is done by editing the dive notes or the equipment for any +one of the selected dives. + +Simultaneous editing only works with fields that do not already contain +information. This means 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 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 @@ -942,14 +890,13 @@ 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: +Many divers wish to annotate dives with text that indicate particular +events, 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). + on the dive profile at that point (see *A* below). - Right-click on the red flag. This brings up the context menu (see *B* below). Select _Edit name_. @@ -957,8 +904,8 @@ buoy". This is easily done: - 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). + - Hovering 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"] @@ -968,57 +915,54 @@ image::images/Bookmarks.jpg["FIGURE: Bookmark dialog", align="center"] The information entered in the *Notes* tab and the *Equipment* tab can be saved by using the two buttons on the top right hand of the *Notes* tab. If the _Apply changes_ button is clicked, the dive data are saved in the memory -image of the dive. If the _Discard changes_ button is clicked, then the -newly entered dive data are erased from the computer memory, although the -dive profile is retained. When the user exits _Subsurface_ there is a final -prompt to confirm that the new data should now be saved permanently on the +image of the dive. If the _Discard changes_ button is clicked, the newly +entered dive data are erased from the computer memory, although the dive +profile is retained. When the user exits _Subsurface_ there is a final +prompt to confirm the new data should now be saved permanently on the computer disk. === Importer les informations à partir d'autres sources de données numériques ou d'autres formats de données [[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 +If you’ve been diving for some time, it’s possible several dives were logged +using other dive log software. 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 software. While some software is supported natively, for others you will +need to export the logbook(s) to an intermediate format so 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. a 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. Below follows more specific information to achieve data import to -_Subsurface_. - +import UDDF and UDCF files used by some dive log software and some dive +computers, like the Heinrichs & Weikamp DR5. Finally, for some dive log +software like Mares Dive Organizer we currently recommend you import the +logbooks first into a web service like _divelogs.de_ and then import from +there with _Subsurface_. Divelogs.de supports a few additional logbook +formats that _Subsurface_ currently cannot handle. + +If the format of other software is supported natively on Subsurface, 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. Below is more specific information to import +data to _Subsurface_. ==== Using the universal import dialogue [[Unified_import]] -Importing dives from other software is performed through a universal -interface activated by selecting _Import_ from the Main Menu, then clicking -on _Import Log Files_. This brings up dialogue *A*, below. +Importing dives from other software is done through a universal interface +activated by selecting _Import_ from the Main Menu, then clicking on _Import +Log Files_. This brings up 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: +_Dive Log Files_ which accesses 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) @@ -1035,8 +979,8 @@ available, as in dialogue *B*, above. Currently these are: - CSV (text-based and spreadsheet-based) dive logs, including APD CCR logs Selecting the appropriate format and then the specific log file in the large -window containing the file list on the right of the dialogue opens the -imported dive log in the _Subsurface_ *Dive List*. Some other formats, not +window containing the file list on the right 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. @@ -1051,33 +995,34 @@ select _OSTCTools Files (.dive .DIVE)_. This makes the _OSTC Tools_ dive logs visible in the file list panel. Select one or more dive, then click the _Open_ button. The OSTC dives are shown in the *Dive List* panel. -Actually, all H&W devices supported by OSTCTools can be imported to -_Subsurface_, this includes OSTC, OSTC Mk2, OSTC 2N/2C, OSTC3, OSTC Sport, -and probably although untested, Frog, OSTC2 and OSTC CR. +All H&W devices supported by OSTCTools can be imported to _Subsurface_. This +includes OSTC, OSTC Mk2, OSTC 2N/2C, OSTC3, OSTC Sport, and probably +although untested, Frog, OSTC2 and OSTC CR. -Please, remember that OSTCTools is *not* a true diving log software, but a -useful set of tools for analysis and management of OSTC devices. This way, -only raw dive computer data will be performed with the import to -_Subsurface_; one has to to manually complete the rest of data which may be -important (buddies, equipment, notes, etc). +Please remember that OSTCTools is *not* a true diving log software, but +rather a useful set of tools for analysis and management of OSTC +devices. Only raw dive computer data will be imported to _Subsurface_; you +have to manually complete the rest of the data you want (buddies, equipment, +notes, etc). -==== Importing from Mares Dive Organiser V2.1 +==== Importing from Mares Dive Organizer V2.1 -Since Mares utilise proprietary Windows software not compatible with +Since Mares uses 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 +process, using _www.divelogs.de_ as a gateway to extract the dive log information. -1. Export the dive log data from Mares Dive Organiser to the user's desktop, - using a _.sdf_ file name extension. Refer to xref:Mares_Export[Appendix C] - for more information. -2. 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_. +1. Export the dive log data from Mares Dive Organizer to your desktop, using a + _.sdf_ file name extension. Refer to xref:Mares_Export[Appendix C] for more + information. +2. Data should then be imported into _www.divelogs.de_. You will first need to + create a user account in _www.divelogs.de_. Log into that web site, then + select _Import Logbook -> Dive Organizer 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 Organizer database to + _www.divelogs.de_. 3. Finally, import the dives from _divelogs.de_ to _Subsurface_, using the instructions below. @@ -1085,15 +1030,15 @@ information. [[S_ImportingDivelogsDe]] ==== Importing dives from *divelogs.de* -The import of dive information from _divelogs.de_ is simple, using a single +Importing dive information from _divelogs.de_ is simple, using a single dialogue box. The _Import -> Import from Divelogs.de_ option should be selected from the Main Menu. This brings up a dialogue box (see image *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 image *B*, -below). The _Apply_ button should then be selected, after which the imported -dives appear in the _Subsurface_ *Dive List* panel. +below). Enter a user-ID and password for _divelogs.de_ 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 shown (see image *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"] @@ -1104,7 +1049,7 @@ 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). The _CSV_ format is a universal simplified format that -allows for easy information exchange between different computers or software +allows easy information exchange between different computers or software packages. For an introduction to CSV-formatted files see xref:S_CSV_Intro[A Diver's Introduction To CSV Files]. _Subsurface_ dive logs can also be exported in _CSV_ format to other software that reads this format. See @@ -1115,8 +1060,8 @@ _Subsurface_. [[S_ImportingCSVDives]] ===== Importer les plongées au format CSV à partir des ordinateurs de plongées ou d'autres logiciels de carnet de plongée -One can view a _CSV_ file by using an ordinary text editor. It is normally -organised into a single line that provides the headers (or _field names_ or +You can view a _CSV_ file by using an ordinary text editor. It’s normally +organized into a single line that provides the headers (or _field names_ or _column headings_) of the data columns, followed by the data, one record per line. @@ -1125,22 +1070,22 @@ _Subsurface_: 1. _CSV dive details_: This dive log format contains similar information to that of a typical written dive log, e.g. dive date and time, dive depth, - dive duration, names of buddy and dive master and perhaps some information - about cylinder pressures before and after the dive, as well as a comment or - two about the dive. All the data for a single dive go on a single line of - text, following the order of the column headings. + dive duration, names of buddy and divemaster and information about cylinder + pressures before and after the dive, as well as comments about the dive. All + the data for a single dive go on a single line of text, following the order + of the column headings. 2. _CSV dive profile_: This dive log format includes much more information about a single dive. For instance there may be information at 30-second - intervals, indicating depth, water temperature at that depth, and cylinder - pressure at that moment in time. Each line contains the information for a - single instant in time during the dive, 30 seconds after that of the - previous instant. Many lines are required to complete the depth profile - information for a single dive. This is a common export format used by - closed-circuit rebreather (CCR) dive equipment and many software packages - that handle dive computer data and/or dive logs. - -Before being able to import the _CSV_ data to _Subsurface_ *one needs to + intervals, indicating depth, water temperature, and cylinder pressure at + that moment in time. Each line contains the information for a single instant + in time during the dive, 30 seconds after that of the previous instant. Many + lines are required to complete the depth profile information for a single + dive. This is a common export format used by closed-circuit rebreather (CCR) + dive equipment and many software packages that handle dive computer data + and/or dive logs. + +Before being able to import the _CSV_ data to _Subsurface_ *you needs to know a few things about the data being imported*: a. Which character separates the different columns within a single line of @@ -1158,7 +1103,7 @@ b. Which data columns need to be imported into _Subsurface_? Is it a _CSV dive c. Is the numeric information (e.g. dive depth) in metric or in imperial units? -Armed with this information, importing the data into _Subsurface_ is +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_ (towards the bottom right). This shows all .CSV files in the selected directory. Select the file @@ -1166,37 +1111,36 @@ that needs to be imported. A configuration panel appears as depicted below: image::images/csv_import1_f20.jpg["FIGURE: CSV download dialogue 1", align="center"] -Notice that, at the top left, there is a dropdown list containing -pre-configured settings for some of the more common dive computers and -software packages encountered by divers. If the _CSV_ file being imported -originated from any of these pre-configured items, then select it. Otherwise -use the _Manual Import_ option. The configuration panel also has dropdown -lists for the specification of the appropriate field separator (Tab, comma -or semicolon), the date format used in the _CSV_ file, the time units -(seconds, minutes or minutes:seconds), as well as the unit system (metric or -imperial). Selecting the appropriate options among these is critical for the -successful import of the data. - -The last remaining task is to ensure that all the data columns have the -appropriate column headings. The top blue row of the data table contains the -column headings found in the _CSV_ data file. The blue row of balloons -immediately above these contains the names understood by _Subsurface_. These -balloons can be moved using a drag-and-drop action. For instance, -_Subsurface_ expects the column heading for Dive number (" # ") to be "Dive -# ". If the column heading that _Subsurface_ expects is not in the blue row, -then drag the appropriate balloon from the upper area and drop it in the -appropriate blue cell at the top of the table. To indicate the correct -column for "Dive #", drag the ballooned item labelled "Dive # " and drop it -in the blue cell immediately above the white cell containing " # ". This is -depicted in the image below. +At the top left, there is a dropdown list containing pre- configured +settings for common dive computers and software packages. + If the _CSV_ file being imported originated from any of +these pre-configured items, select it. Otherwise use the _Manual Import_ +option. The configuration panel also has dropdown lists for the specification of the appropriate +field separator (Tab, comma or semicolon), the date format used in the _CSV_ file, +the time units (seconds, minutes or minutes:seconds), as well as the unit system +(metric or imperial). Selecting the appropriate options among these is critical for +the successful data import. + +Complete this by ensuring that all the data columns have the appropriate +column headings. The top blue row of the data table contains the column +headings found in the _CSV_ data file. The blue row of balloons immediately +above these contains the names understood by _Subsurface_. These balloons +can be moved using a drag-and-drop action. For instance, _Subsurface_ +expects the column heading for Dive number (" # ") to be "Dive # ". If the +column heading that _Subsurface_ expects is not in the blue row, drag the +appropriate balloon from the upper area and drop it in the appropriate blue +cell at the top of the table. To indicate the correct column for "Dive #", +drag the ballooned item labelled "Dive # " and drop it in the blue cell +immediately above the white cell containing " # ". This is depicted in the +image below. image::images/csv_import2_f20.jpg["FIGURE: CSV download dialogue 2", align="center"] -Continue in this way to ensure that all the column headings in the blue row -of cells correspond to the headings listed in the top part of the -dialogue. Having completed this task, select the _OK_ button to the bottom -right of the dialogue. The data from the _CSV_ file are imported and shown -in the *Dive List* panel. +Continue in this way to ensure all the column headings in the blue row of +cells correspond to the headings listed in the top part of the dialogue. +When finished, select the _OK_ button on the bottom right of the dialogue. +The data from the _CSV_ file are imported and shown in the *Dive List* +panel. [[S_CSV_Intro]] **** @@ -1205,17 +1149,17 @@ in the *Dive List* panel. [IMPORTANT] _CSV_ is an abbreviation for a data file format: _Comma-Separated -Values_. It is a file format allowing someone to view or edit the -information using a text editor such as Notepad (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 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. +Values_. It is a file format that lets you view or edit information using a +text editor like Notepad (Windows), gedit (Linux) or TextWrangler +(OS/X). There are two main advantages of the _CSV_ format. First, the data +are easily editable as text without any proprietary software. Second, all +information is human-readable, not obscured by any custom or proprietary +attributes that proprietary software inserts 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 like spreadsheet-based dive logs and +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 @@ -1223,7 +1167,7 @@ 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 +organized 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 @@ -1267,21 +1211,21 @@ computer: When a _CSV_ file is selected for import, _Subsurface_ displays the column headers as well as some of the data in the first few lines of the _CSV_ -file, making it much easier to work with _CSV_ files. _CSV_ files can -therefore be used in many contexts for importing data into a _Subsurface_ -dive log. Knowledge of a few basic things about the content of the _CSV_ -file allows a smooth import of the dives into _Subsurface_. +file, making it much easier to work with _CSV_ files. _CSV_ files can be +used in many contexts for importing data into a _Subsurface_ dive log. +Knowing a few basic things about the content of the _CSV_ file helps with a +smooth import of the dives into _Subsurface_. **** [icon="images/icons/important.png"] [IMPORTANT] -The _CSV_ import has a couple of caveats. One should avoid some special -characters like ampersand (&), less than (<), greater than (>) and double -quotes (") as part of the numbers or text within a cell. The file should use -UTF-8 character set, if using non-ASCII characters. Also the size of the -_CSV_ file might cause problems. Importing 100 dives at a time (_CSV dive +But, the _CSV_ import has a couple of caveats. Avoid some special characters +like ampersand (&), less than (<), greater than (>) and double quotes (") as +part of the numbers or text within a cell. The file should use UTF-8 +character set, if using non-ASCII characters. Also the size of the _CSV_ +file might cause problems. Importing 100 dives at a time (_CSV dive details_) works, but larger files might exceed the limits of the parser used. When encountering problems with _CSV_ imports, first try with a smaller file to make sure everything works. @@ -1293,18 +1237,16 @@ smaller file to make sure everything works. Using the *Subsurface Companion App* on an _Android device_ or xref:S_iphone[_iPhone_] with 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 file server. _Subsurface_, in turn, can collect -the localities from the file server. - +location can be automatically passed to the _Subsurface_ dive log. The Companion App +stores dive locations on a dedicated Internet server. _Subsurface_ can collect +the locations from the 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 + will be sent, a long number giving you access to the file server and Companion App capabilities. - Download the app from @@ -1316,99 +1258,97 @@ To do this: 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. +* _Create a new account._ Equivalent to registering in the _Subsurface_ + companion page using an Internet browser. You can request a *DIVERID* using + this option, but it’s supplied via email and followed up by interaction with + the http://api.hohndel.org/login/[_Subsurface companion web page_] to + activate the account. -* _Retrieve an account._ If users forgot their *DIVERID* they will receive an +* _Retrieve an account._ If users forget 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 + saves this *DIVERID* and doesn’t ask for it again unless you use 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. +the Default Preferences panel, by selecting _File -> Preferences -> +Defaults_ from the main menu in _Subsurface_ itself. This helps +synchronization 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 +Now you are 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: +Touch the "+" icon on the top right to add a new dive site, a menu shows +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. +* Use Map: This option lets you fix a position by searching a world map. A + world map is shown (see *B* below) on which you can show the desired + position with a _long press_ on the touch sensitive screen (if the marked + location is wrong, simply choose a new location) and select the check + symbol in the upper right. A dialog is shown letting you enter the name of + the dive location and the date and time of the dive (see *C* below). In + order to import this dive location in _Subsurface_ you should 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. + stored locations shown. Now 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 +selection box to the left showing they need to be uploaded to the +server. You 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. +(like _Delete_ or _Send_) are performed on several selected locations. 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. +or a map showing them. 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 you select 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 selects a dive (*not* selecting the check box), the name given to +When you select 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. +Maps: Display a map showing the dive location. After editing and saving a +dive location (see *C* above), 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 +There are several ways to send locations to the server. The easiest is 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). +Be careful! 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"] @@ -1427,24 +1367,22 @@ Selecting the _Settings_ menu option results in the right hand image above - _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. - + easiest way to get it is to copy and paste from the confirmation email or + just type it in. ===== 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. + and those on the web service synchronize 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 +Instead of entering an unique dive location, you can leave the service +running in the background of your Android device, allowing a continuous collection of GPS locations. - -The settings below define the behaviour of the service: +The settings below define the behavior of the service: - _Min duration._ In minutes. The app will try to get a location every X minutes until stopped by the user. @@ -1455,14 +1393,14 @@ The settings below define the behaviour of the service: [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 50 m 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. +_How does the background service work?_ Assuming the diver 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 50 m 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 diver is not moving, only one location is +saved. If the diver is moving, a trace of the route is obtained by saving a +location every 50 meters. ===== Other @@ -1479,16 +1417,15 @@ Search the saved dive locations by name or by date and time. ===== Start service -Initiates the _background service_ following the previously defined -settings. +Starts 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. +This is admittedly a badly named option that disconnects the app from the +server. It resets 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 your Android device was +used to download the dive locations of another registered diver. ===== Send all locations @@ -1497,27 +1434,27 @@ This option sends all locations stored in the Android device to the server. [[S_iphone]] ==== Using the Subsurface companion app on an _iPhone_ to record dive locations -The iPhone interface is quite simple. One needs to type the user ID -(obtained during registration) into the space reserved for it, then select -"Dive in" (see left part of the image below) and start collecting dive -location information. +The iPhone interface is quite simple. Type the user ID (obtained during +registration) into the space reserved for it, then select "Dive in" (see +left part of the image below) and start collecting dive location +information. image::images/iphone.jpg["FIGURE: Using iPhone companion application", align="center", width=640] Dives can be added automatically or manually. In manual mode, a dive location or waypoint is added to the GPS input stream. In automatic mode, a -continuous path of GPS locations is created from which, much later, after -import, subsurface can select the appropriate GPS locations based on the -times of dives. The default mode for the _iphone_ is automatic. When one -adds a dive, the location service is started automatically and a red bar -appears at the bottom of the screen. After the dive one can click on the red -bar to end the location service. While the location service is running one -can only add dives using the manual mechanism. - -One can edit the site name afterwards by selecting the dive from the dive +continuous path of GPS locations is created from which, after import, +Subsurface can select the appropriate GPS locations based on the times of +dives. The default mode for the _iphone_ is automatic. When adding a dive, +the location service is started automatically and a red bar appears at the +bottom of the screen. After the dive, click on the red bar to end the +location service. While the location service is running you can only add +dives manually. + +You can edit the site name afterwards by selecting the dive from the dive list and clicking on the site name. There are no other editable fields. The -dive list is automatically uploaded from the iPhone to the webservice and -there is not an option to trigger upload manually. +dive list is automatically uploaded from the iPhone to the web +service. There isn’t an option to trigger upload manually. ==== Downloading dive locations to the _Subsurface_ divelog @@ -1527,49 +1464,49 @@ _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 +blank. Provide a DIVERID, then select the _Download_ button to start 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. +Note that the _Apply_ button is now active. By clicking on it, you can +update the locations of the newly entered or uploaded dives in +_Subsurface_. That applies the coordinates and names entered on the app to +all the new dives that match the date-times of the uploaded GPS +localities. If you have 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. +assignment of GPS data to dives depends on agreeing date-time information +between the two devices. Although _Subsurface_ has a wide range tolerance, +it may not be able to identify the appropriate dive if there's a large +difference between the time in the dive computer and that of the Android +device. That results 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 +for this (e.g. time zones). _Subsurface_ may also 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. +subsequent dives as well). A workaround 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). - +- _Background service_ may fill the location list with unnecessary locations + that don’t correspond to the exact dive point but do correspond to the + boat's route. + Right now, these locations are difficult to delete from the server. In some + situations it + is better 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 you want 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 @@ -1579,11 +1516,11 @@ TIPS: === 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. +during a dive. To match each photograph with a specific dive, _Subsurface_ +lets you 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 +==== Loading photos and synchronizing 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 @@ -1596,45 +1533,45 @@ to be loaded into _Subsurface_ and click the _Open_ button. image::images/LoadImage2_f20.jpg["FIGURE: Load images option", align="center"] -This brings up 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. +This brings up the time synchronization dialog, shown below. But be aware +that the time synchronization 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 synchronize, then the +exact times of photographs can be used to position photographs on the dive +profile. -_Subsurface_ achieves this synchronisation in three ways: +_Subsurface_ synchronizes in three ways: -- *Pro-actively*: Before the dive, ensure synchronisation of the dive computer time settings with +- *Pro-actively*: Before the dive, ensure synchronization of the dive computer time settings with the time settings of the camera by changing the date-time settings on one or both of these devices. -- *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 +- *Manually*: If you wrote down the exact camera time at the start of a dive, the + difference in time between the two devices can be determined. As long as the device + settings for time has not been changed in either device, you could write down the times of + both devices after the dive or even at the end of the day. You 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. + immediately under the heading _Shift times of image(s) by_, shown 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. + in that tool. Click the _OK_ button and synchronization is done. -image::images/LoadImage3b_f20.jpg["FIGURE: Synchronisation dialog", align="center"] +image::images/LoadImage3b_f20.jpg["FIGURE: Synchronization 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 +- *By photograph*: There is a very slick way of synchronizing. If you take a + photograph of the face of the dive computer showing the time, then _Subsurface_ can get + the exact time the photograph was taken, using the metadata the camera stores within + each photo. To do this, use the bottom half of the _Time shift_ dialog. If you use the bottom part, the top part of the dialog is ignored. Click on - the horizontal bar entitled "_Select image of dive computer showing time_. This brings up - a file browser with which one can select the photograph of the dive computer time. Select the + the horizontal bar called "_Select image of dive computer showing time_. This brings up + a file browser letting you select the photograph of the dive computer time. 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 + so it 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. + camera and dive computer is, and it can synchronize. Image *B* above shows a photograph of the face of the dive computer and with the date-time tool set to the date-time. @@ -1647,9 +1584,9 @@ After the images have been loaded, they appear in two places: - the _Photos_ tab of the *Notes* panel. - as tiny icons (stubs) on the dive profile at the appropriate positions - reflecting the time each photograph was taken. In order to view the photos - on the dive profile, activate the _show-photos_ button in the tool bar to - the left of the dive profile: + reflecting the time each photograph was taken. To view the photos on the + dive profile, 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"] @@ -1657,18 +1594,17 @@ This results in a profile display as in the image 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: +If you hover the mouse over any of the photo icons, 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). +_Subsurface_ window. This allows good viewing of the added photographs. (see +the image below). Note that the thumbnail has a small dustbin icon in the +bottom right hand corner (see image above). Selecting the dustbin removes +the image from the dive. Be careful 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"] @@ -1678,60 +1614,55 @@ Photographs associated with a dive are shown as thumbnails in the _Photos_ tab of the _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. +accessing the photos of a dive, while the stubs on the dive profile show +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 by the operating system (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. +Most underwater photographers store photos on an external drive. If such a +drive can be mapped by the operating system (almost always the case) the +photos can be directly accessed by _Subsurface_. This eases 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 synchronization (see text above) is used. 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. If the external drive with the photos +is re-connected, the photos can be seen in the normal way. [[S_FindMovedImages]] ==== Moving photographs among directories, hard disks or computers After a photograph has been loaded into _Subsurface_ and associated with a specific dive, the directory - where the photo lies is stored, allowing _Subsurface_ to find the photograph when the dive is + where the photo lies is stored, letting _Subsurface_ find the photograph when the dive is opened again. If the photo or the whole photo collection is moved to another drive or to a different - machine, it is unlikely that the directory structure will remain identical to that of the original uploaded + machine, the directory structure will be different to that of the original uploaded photo. When this happens, _Subsurface_ looks for the photos at their original location before they were moved, - cannot find them and therefore cannot display them. Because, after moving photos, large numbers of photos + cannot find them and cannot display them. Because after moving photos, large numbers of photos may need to be deleted and re-imported from the new location, _Subsurface_ has a mechanism that eases the process of updating the directory information for each photo: automatic updates using fingerprints. When a photo is loaded into _Subsurface_, a fingerprint for the image is calculated and stored with the other reference information for that photo. After moving a photo collection (that has already been loaded - into _Subsurface_) to a different directory, disk or computer, _Subsurface_ can perform the - following steps: - -- look through a particular directory (and all its subdirectories recursively) - where photos have been moved - to, + into _Subsurface_) to a different directory, disk or computer, _Subsurface_ can: +look through a particular directory (and all its subdirectories recursively) +where photos have been moved to, - calculate fingerprints for all photos in this directory, and - if there is a match between a calculated fingerprint and the one originally calculated when a photo was - loaded into _Subsurface_ (even if the original file name has changed), to + loaded into _Subsurface_ (even if the original file name has changed), automatically update the directory information so that _Subsurface_ can find the photo in the new moved directory. -This is achieved by selecting from the Main Menu: _File -> Find moved images_. This brings up a window within +This is done by selecting from the Main Menu: _File -> Find moved images_. This brings up a window within which the NEW directory of the photos needs to be specified. Select the appropriate directory and click the _Scan_ button towards the bottom right of the panel. The process may require several minutes to complete, after which _Subsurface_ will show the appropriate photographs when a particular dive is opened. @@ -1743,16 +1674,16 @@ This is achieved by selecting from the Main Menu: _File -> Find moved image [icon="images/icons/important.png"] [IMPORTANT] -_Subsurface_ automatically calculates fingerprints for all images that can -be accessed by _Subsurface_. When manipulating images, ensure that all the -images associated with the dive log can be accessed by _Subsurface_. +_Subsurface_ automatically calculates fingerprints for all images that it +can access. When manipulating images, be sure all the images associated +with the dive log can be accessed by _Subsurface_. _Subsurface_ automatically checks and, if necessary, updates the fingerprints associated with a single dive if: - The images associated with that dive are visible as thumbnails on the *Dive Profile*. -- One edits anything in the *Notes tab* panel and save the edits by selecting - _Apply changes_. +- If you edit anything in the *Notes tab* panel and save the edits by + selecting _Apply changes_. **** @@ -1763,19 +1694,19 @@ fingerprints associated with a single dive if: ==== Multicylinder dives _Subsurface_ easily handles dives involving more than one -cylinder. Multi-cylinder diving usually happens (a) if a diver does not have -enough gas for the complete dive in a single cylinder; (b) if the diver -needs more than one gas mixture because of the depth or the decompression -needs of the dive. For this reason multi-cylinder dives are often used by -technical divers who dive deep or long. As far as _Subsurface_ is concerned, -there are only two types of information that need to be provided: +cylinder. Multi-cylinder diving usually happens (a) if a diver doesn’t have +enough gas for the complete dive in a single cylinder; (b) if a diver needs +more than one gas mixture because of the depth or the decompression needs of +the dive. For this reason multi-cylinder dives are often used by technical +divers who dive deep or long. As far as _Subsurface_ is concerned, there are +only two types of information that need to be provided: - *Describe the cylinders used during the dive* This is performed in the *Equipment tab* of the *Info* panel, as xref:cylinder_definitions[described above]. Enter the cylinders one by one, - specifying the characteristics of the cylinder and the gas composition within each cylinder. + specifying each’s characteristics and the gas composition within it. -- *Record the times at which switches from one cylinder to another was done:* This is information - provided by some dive computers (provided the diver indicated these changes to the dive computer +- *Record the times at which the switch from one cylinder to another was done:* This is information + tracked by some dive computers (provided the diver indicated these changes to the dive computer by pressing specific buttons). If the dive computer does not provide the information, the diver has to record these changes using a different method, e.g. writing it on a slate. @@ -1787,9 +1718,9 @@ there are only two types of information that need to be provided: *tank bar* button in the toolbar has been activated, the cylinder switches are also indicated in the tank bar. -Having performed these tasks, _Subsurface_ indicates the appropriate use of +When this is complete, _Subsurface_ indicates the appropriate use of cylinders in the dive profile. Below is a multi-cylinder dive, starting off -with EAN28, then changing cylinders to EAN50 after 26 minutes to perform +with EAN28, then changing cylinders to EAN50 after 26 minutes for decompression. image::images/multicylinder_dive.jpg["FIGURE: Multicylinder profile", align="center"] @@ -1797,31 +1728,30 @@ image::images/multicylinder_dive.jpg["FIGURE: Multicylinder profile", align="cen ==== Sidemount dives Sidemount diving is just another form of multi-cylinder diving, often with -both or all cylinders having the same gas mixture. Although it is a popular -configuration for cave divers, sidemount diving can be performed by -recreational divers who have completed the appropriate training. Sidemount -dive logging involves, exactly as with multi-cylinder dives, above, three -steps: +both or all cylinders having the same gas mixture. Although it’s a popular +configuration for cave divers, Sidemount diving can be done by recreational +divers who’ve completed the appropriate training. sidemount dive logging +involves three steps, exactly as with multi-cylinder dives above: - *During the dive, record 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, many 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 + cylinders with air or with the same gas mixture, _Subsurface_ distinguishes between these different + cylinders. In contrast, many dive computers that allow gas switching only distinguish between different + _gases_ used, not among different _cylinders_ used. This means when sidemount dives are downloaded + from these dive computers, the switching event between cylinders with the same gas is not downloaded. This may mean + that a diver may have to keep a written log of cylinder switch times using a slate, or (if the dive computer + has the capability) marking each cylinder switch with a bookmark that can be retrieved later. Returning from a dive with the times of 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 *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 + from a dive computer into _Subsurface_, the cylinder switch events need to be shown on the dive profile. + Cylinder changes are recorded by right-clicking at the appropriate point on the dive profile, 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 + to be selected. Select the appropriate cylinder. The cylinder change is then shown 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 + profile, then the cylinder change is also shown 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 in the image below. @@ -1836,19 +1766,19 @@ logging tool. [icon="images/halcyon_RB80.jpg"] [NOTE] -Passive semi-closed rebreathers (pSCR) comprise a technical advance in -diving equipment that recirculates the breathing gas that a diver breathes, -while removing carbon dioxide from the exhaled gas. While a small amount -(typically a tenth) of the exhaled breathing gas is released into the water, -a small amount of fresh gas is released from the back gas cylinder -(typically containing nitrox). A diver, using a single cylinder of -breathing gas can therefore dive for much longer periods than using a -recreational open-circuit configuration. With pSCR equipment, a very small -amount of breathing gas is released every time the breather inhales. With -active SCR (aSCR) equipment, in contrast, a small amount of breathing gas is -released continuously from the back cylinder. - -To log pSCR dives, no special procedures are required, just the normal steps +Passive semi-closed rebreathers (pSCR) are a technical advance in diving +equipment that recirculates the breathing gas a diver uses, while removing +carbon dioxide from the exhaled gas. While a small amount (typically a +tenth) of the exhaled breathing gas is released into the water, a small +amount of fresh gas is released from the back gas cylinder (typically +containing nitrox). A diver using a single cylinder of breathing gas can +therefore dive for much longer periods than using a recreational +open-circuit configuration. With pSCR equipment, a very small amount of +breathing gas is released every time the diver inhales. With active SCR +(aSCR) equipment, in contrast, a small amount of breathing gas is released +continuously from the back cylinder. + +To log pSCR dives, no special procedures are required. Use the normal steps outlined above: - Select pSCR in the _Dive Mode_ dropdown list on the *Info* panel. @@ -1858,8 +1788,8 @@ outlined above: cylinder/gas changes as described above in the section on xref:S_MulticylinderDives[multicylinder dives]. -If a pSCR _Dive Mode_ has been selected, the dive ceiling for pSCR dives is -adjusted for the oxygen drop across the mouthpiece which often requires +If a pSCR _Dive Mode_ has been selected, the dive ceiling for that is +adjusted for the oxygen drop across the mouthpiece, which often requires longer decompression periods. Below is a dive profile of a pSCR dive using EAN36 on the back cylinder and oxygen for decompression. Note that this dive lasted over two hours. @@ -1874,9 +1804,9 @@ image::images/pSCR_profile.jpg["FIGURE: pSCR profile", align="center"] [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 +has been breathed. They also do two things to maintain a breathable oxygen concentration: -a) remove carbon dioxide from the gas that has been exhaled +a) remove carbon dioxide from the exhaled gas regulate the oxygen concentration to remain within safe diving limits. The CCR interface of _Subsurface_ is currently experimental and under active development. Subsurface currently supports Poseidon MkVI and APD @@ -1885,8 +1815,8 @@ recreational 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 digital databases: one -dive at a time. +same way it imports dive log data from other digital databases: one dive at +a time. ===== Import a CCR dive @@ -1896,14 +1826,14 @@ select _Import -> Import log files_ to bring up the xref:Unified_import[universal import dialogue]. As explained in that section, the bottom right hand of the import dialogue contains a dropdown list (labled _Filter:_) of appropriate devices that currently -includes(Poseidon) MkVI or APD log viewer files (import for other CCR -equipment is under active development). Having selected the appropriate CCR +include(Poseidon) MkVI or APD log viewer files. Import for other CCR +equipment is under active development. 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. The selected dive is imported to the -_Subsurface_ dive list. +the CCR dive computer, 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, click the _Open_ button at the bottom right hand of the universal +import dialogue. The selected dive is imported to the _Subsurface_ dive +list. ===== Displayed information for a CCR dive @@ -1921,8 +1851,8 @@ follows: - For THREE-sensor systems (e.g. APD), the mean value is also used. However differences of more than 0,1 bar in the simultaneous readings of different - sensors are treated as spurious. If one of the three sensors provides - spurious data, it is ignored. + sensors are treated as false. If one of the three sensors provides false + data, it is ignored. - If no sensor data are available, the pO~2~ value is assumed to be equal to the setpoint. @@ -1931,20 +1861,20 @@ The mean pO~2~ of the sensors is indicated with a green line, The oxygen setpoint values as well as the readings from the individual oxygen sensors can be shown. The display of additional CCR information is -turned on by checking the appropriate checkboxes in the _Preferences_ panel +turned on by checking the appropriate boxes in the _Preferences_ panel (accessible by selecting xref:S_CCR_options[_File -> Preferences -> Graph_]). This part of the _Preferences_ panel is shown in the image below, representing two checkboxes that modify the display of pO~2~ when the -appropriate toolbar button on the Dive Profile has been activated. +appropriate toolbar button on the Dive Profile has been checked. image::images/CCR_preferences_f20.jpg["FIGURE: CCR preferences panel", align="center"] -Checking any of these check boxes allows the display of additional -oxygen-related information whenever the pO~2~ toolbar button on the -_Profile_ panel is activated. The first checkbox allows the display of -setpoint information. This is a red line superimposed on the green oxygen -partial pressure graph and allows a comparison of the mean measured oxygen -partial pressure and the setpoint values, as shown below. +Checking any of these boxes allows the display of additional oxygen-related +information whenever the pO~2~ toolbar button on the _Profile_ panel is +activated. The first checkbox allows the display of setpoint +information. This is a red line superimposed on the green oxygen partial +pressure graph and allows a comparison of the mean measured oxygen partial +pressure and the setpoint values, as shown below. image::images/CCR_setpoint_f20.jpg["FIGURE: CCR setpoint and po2 graph", align="center"] @@ -1977,8 +1907,8 @@ two cylinders are shown as green lines overlapping the depth profile. In addition, start and end pressures for both oxygen and diluent cylinders are shown in the _Equipment Tab_. Below is a dive profile for a CCR dive, including an overlay of setpoint and oxygen sensor data, as well as the -cylinder pressure data. In this case there is good agreement from the -readings of the two oxygen sensors. +cylinder pressure data. In this case there is agreement from the readings of +the two oxygen sensors. image::images/CCR_dive_profile_f22.jpg["FIGURE: CCR dive profile", align="center"] @@ -1996,9 +1926,9 @@ dive profile: image::images/icons/cceiling.jpg["DC ceiling icon"] -The default colour of the computer-generated deco ceiling is white. However, -this can be set to red by checking the appropriate check box after selecting -_File -> Preferences -> Graph_. Below is a dive profile indicating the dive +The default color of the computer-generated deco ceiling is white. This can +be set to red by checking the appropriate check box after selecting _File -> +Preferences -> Graph_. Below is a dive profile indicating the dive computer-generated deco ceiling: image::images/CCR_dive_ceilingF22.jpg["FIGURE: CCR computer-generated deco ceiling", align="center"] @@ -2043,8 +1973,8 @@ image::images/ExtraDataTab_f20.jpg["FIGURE: Extra Data tab", align="center"] 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 +figures for 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. @@ -2056,23 +1986,23 @@ 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 +the left hand side that lets you control 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: +Profile is the graph of dive depth as a function of time. In addition to +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 colors: |==================== -|*Couleur*|*Vitesse de descente (m/min)*|*Vitesse de remontée (m/min)* -|Rouge|> 30|> 18 +|*Color*|*Descent speed (m/min)*|*Ascent speed (m/min)* +|Red|> 30|> 18 |Orange|18 - 30|9 - 18 -|Jaune|9 - 18|4 - 9 -|Vert clair|1.5 - 9|1.5 - 4 -|Vert foncé|< 1.5|< 1.5 +|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 +graph. So users should see the depth of the deepest point and other peaks. Mean depth is plotted as a grey line, indicating mean dive depth up to a particular moment during the dive. @@ -2080,8 +2010,8 @@ to a particular moment during the dive. [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. +the dive profile increases the size of the dive profile to fill the area of +the panel. *Water temperature* is displayed with its own blue line with temperature values placed adjacent to significant changes. @@ -2090,13 +2020,13 @@ The dive profile can include graphs of the *partial pressures* of O~2~, N~2~, 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. +nitrogen in black, and 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 +during the dive. This is shown below the dive depth and water temperature graphs. [icon="images/icons/N2.jpg"] @@ -2107,16 +2037,16 @@ 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. +during the dive. This is only important 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 +manually entering the start and end pressures the graph, is not a straight +line. Like the depth graph, the slope of the tank pressure gives you +information about the momentary SAC rate (Surface Air Consumption) when +using an air integrated dive computer. Here the color coding is not +relative to some absolute values but relative to the average normalized 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. @@ -2131,53 +2061,50 @@ 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. - + (100ft) – this way short or shallow dives are easily recognizable; +something free divers 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. +done by dragging the red dots to the two points on the dive profile that you +wish 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 +shows 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 +ceilings occur 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. +available for download; for example none of the Suunto dive computers make +these 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’s 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’s 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 because _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 a specific deco stop. This feature lets dive +computers offer longer non-stop bottom times. [icon="images/icons/cceiling.jpg"] [NOTE] @@ -2208,12 +2135,11 @@ 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. +represented as a colored bar at the bottom of the *Dive Profile*. In general +oxygen is represented by a green bar, nitrogen a yellow bar and helium 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"] @@ -2227,14 +2153,13 @@ 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 contrast, -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. +divers doing planned decompression diving, efficient rates of offgassing 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 contrast, 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, at the position of the cursor on the dive profile. image::images/tissuesGraph.jpg["Figure: Inert gas tissue pressure graph", align="center"] @@ -2255,27 +2180,26 @@ dive. For more information external to this manual see: === 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 mouse cursor is over the Dive Profile panel. The menu lets you create +Bookmarks, 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, with the time of the event set by +where the mouse cursor was when the right mouse button was first clicked to +bring up the menu. Gas Change events involve a selection of which gas is +being switched TO. The list of choices is based on the available gases +defined in the *Equipment* Tab. Setpoint change events open a dialog letting +you choose the next setpoint value. As in the planner, a setpoint value of +zero shows the diver is breathing from an open circuit system while any +non-zero value shows 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. [[S_InfoBox]] === 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 +The Information box displays a large range of information about 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 @@ -2285,25 +2209,24 @@ 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: +When 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 shown 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). Moving the cursor +horizontally lets the Information Box 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 some statistics, shown as four +buttons on the left of the profile panel. These are: [icon="images/icons/MOD.jpg"] [NOTE] @@ -2313,7 +2236,7 @@ dependent on the oxygen concentration in the breathing gas. For air (21% oxygen) it is around 57 m if a maximum pO~2~ of 1.4 is specified in the *Preferences* section (select _File_ -> Preferences -> Graph_ and edit the text box _Max pO~2~ when showing MOD_. Below the MOD there is a markedly -increased risk of exposure to the dangers associated with oxygen toxicity. +increased risk of exposure to the dangers of oxygen toxicity. [icon="images/icons/NDL.jpg"] [NOTE] @@ -2321,40 +2244,39 @@ Clicking this button causes the Information Box to display either 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. TTS is calculated assuming an ascent surface air -consumption (SAC) for the gas currently used. Even if the profile contains -several gas switches, TTS at a specific moment during the dive is calculated -using the current gas. For TTS longer than 2 hours, it is not accurately -calculated and Subsurface only indicates _TTS > 2h_. +appears). Once a diver 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. TTS is calculated assuming an ascent +surface air consumption (SAC) for the gas currently used. Even if the +profile contains several gas switches, TTS at a specific moment during the +dive is calculated using the current gas. TTS longer than 2 hours is not +accurately calculated and Subsurface only indicates _TTS > 2h_. [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 +Consumption (SAC)*. SAC is an indication of the surface-normalized 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. +of breathing gas consumption rate independent of the depth of the dive, so +the respiratory rates of different dives can be compared. The units for SAC +is liters/min or cubic 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. +dives. These are important to divers breathe 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. @@ -2362,17 +2284,17 @@ data. [[S_gas_pressure_graph]] ==== The Gas Pressure Bar Graph -On the left of the *Information Box* is a vertical bar graph indicating the +On the left of the *Information Box* is a vertical bar graph showing 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 +dive_. It is shown 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 + light green area showing 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. @@ -2395,20 +2317,20 @@ image::images/GasPressureBarGraph.jpg["FIGURE:Gas Pressure bar Graph", align="ce *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 + 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. +These five values are shown on the left in the graph above. The way the Gas +Pressure Bar Graph changes during a dive can be seen 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 *A* indicates the start of a dive with the 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. + tissue compartments have had time to respond to the descent, so their gas + pressures are 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 @@ -2416,11 +2338,11 @@ side of the above figure for a diver using EAN32. (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 +- 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 + exceed that of the total gas pressure and approach 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 @@ -2431,19 +2353,19 @@ side of the above figure for a diver using EAN32. -== Organising the logbook (Manipulating groups of dives) +== Organizing the logbook (Manipulating groups of dives) === The Dive List context menu -Several actions on either a single dive or a group of dives can be performed -using the Dive List Context Menu, found by selecting either a single dive or -a group of dives and then right-clicking. +Several actions on either a single dive, or a group of dives, can be +performed using the Dive List Context Menu. It is found by selecting either +a single 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. +The context menu is used in many functions described below. -==== Customising the columns showed in the *Dive List* panel +==== Customizing the columns showed in the *Dive List* panel image::images/DiveListOptions.jpg["Example: Dive list info options", align="center"] @@ -2452,8 +2374,8 @@ 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 (reflected by the check symbols) and the list is immediately +above). Select an item to be shown in the *Dive List* or be deleted +(reflected by the check symbols) and the list is immediately updated. Preferences for information shown in the *Dive List* are saved and used when _Subsurface_ is re-opened. @@ -2461,64 +2383,60 @@ used when _Subsurface_ is re-opened. === 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. - -One can also renumber a few selected dives in the dive list. Select the +sequence numbers) to recent dives (higher sequence numbers). Numbering of +dives is not always consistent. For instance, when non-recent dives are +added, correct 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. So you may need to renumber the dives. Do this by +selecting (from the Main Menu) _Log -> Renumber_. Users are given a choice +of the lowest sequence number to be used. This results in new sequence +numbers (based on date/time) for the dives in the *Dive List* panel. + +You can also renumber a few selected dives in the dive list. Select the dives that need renumbering. Right-click on the selected list and use the Dive List Context Menu to perform the renumbering. A popup window appears -requiring the user to specify the starting number for the renumbering -process. +letting the user specify the starting number for the process. [[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 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 +can group dives into _trips_. It does this by grouping dives that have +date/times not separated in time by more than two days, so 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): +dive list of 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) select _Log -> Autogroup_. The *Dive List* panel -now shows only the titles for the trips. +having to scan a long lists of dives. To group the dives in a dive list, +(from the Main Menu) 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 *Notes* -panel. Here one can add or edit information about the date/time, the trip +panel. Here you 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 +dive company that was used, the general weather and surface conditions during the trip, etc.). After entering this information, 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 the edited information. ==== Viewing the dives during a particular trip -Once the dives have been grouped into trips, users can expand one or more +Once the dives have been grouped into trips, you 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. +expands the selected trip, revealing individual dives done during the trip. ==== Collapsing or expanding dive information for different trips After selecting a particular trip in the dive list, the context menu allows -several possibilities to expand or collapse dives within trips. This -includes expanding all trips and collapsing all trips. +several options to expand or collapse dives within trips. This includes +expanding all trips and collapsing all trips. ==== Merging dives from more than one trip into a single trip @@ -2527,14 +2445,12 @@ by either merging the selected trip with the trip below or with the trip above. (Merge trip with trip below; Merge trip with trip above) ==== Splitting a single trip into more than one trip - -If a trip includes ten dives, the user can split this trip into two trips -(trip 1: top 4 dives; trip 2: bottom 6 dives) by selecting and -right-clicking the top four dives. The resulting context menu allows the -user to create a new trip by choosing the option *Create new trip -above*. The top four 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): +If a trip includes ten dives, you can split this trip into two trips (trip +1: top 4 dives; trip 2: bottom 6 dives) by selecting and right-clicking the +top four dives. The resulting context menu lets the user create a new trip +by choosing the option *Create new trip above*. The top four dives are then +grouped into a separate trip. The figures below show 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"] @@ -2543,18 +2459,18 @@ image::images/SplitDive3a.jpg["FIGURE: Split a trip into 2 trips", align="center ==== 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 +right-clicking them to bring up the context menu, 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 or below the trip to which they belonged, depending -on the date and time of the unlinked dive. +You can unlink dives from the trip to which they belong. 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 or below the trip to which they belonged, depending on the date and +time of the unlinked dive. ==== Add a dive to the trip immediately above @@ -2563,22 +2479,20 @@ within a separate trip. To do this, select and right-click the dive(s) to bring up the context menu, and then select *Create new trip 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, 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 ealier or later. +Sometimes it’s necessary to adjust the start time of a dive. This may apply +to situations where dives are done in different time zones or when the dive +computer has a wrong time. To do this, select and right-click the dive(s) to +be adjusted. This brings up the context menu on which the *Shift times* +option should be selected. You must then specify the time (in hours and +minutes) by which the dives should be adjusted and click on the option of +whether the time adjustment should be earlier or later. ==== 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 +Sometimes a dive is briefly interrupted, for example, if a diver returns to +the surface for a few minutes. That results in two or more dives being +recorded by the dive computer and appearing as different dives in the *Dive +List* panel. You 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 *Notes* panel to reflect events or conditions that apply @@ -2599,45 +2513,45 @@ _Redo_ an action. [[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. +The dives in the *Dive List* panel can be filtered, so you 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 lets you 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 (see image below). The _Filter Panel_ can be reset (i.e. all current filters cleared) by selecting -the *yellow angled arrow*. The _Filter Panel_ may also be minimised by -selecting the *green up-arrow". 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 *red button* +the *yellow angled arrow*. The _Filter Panel_ may also be minimized by +selecting the *green up-arrow". When minimized, only these three icons are +shown. The panel can be maximized by clicking the same icon that minimized +it. The filter may also be reset and closed by selecting the *red button* with the white cross. 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 +(buddy / divemaster), dive site and dive suit. Each of these 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. +filter tool, allowing the listing of only some attributes within that check +list. For instance, typing "_ca_" in the filter text box above the tags +check list, results in the list being reduced to "_cave_" and +"_cavern_". Filtering the check list helps to rapidly find search terms for +filtering the dive list. To activate filtering of the dive list, check at least one check box in one of the four check lists. The dive list is then shortened to include only the dives that pertain to the 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 +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 -There are two routes for the export of dive information from Subsurface: +There are two ways to export dive information from Subsurface: - Exporter les informations de plongée vers _Facebook_ @@ -2647,45 +2561,41 @@ There are two routes for the export of dive information from Subsurface: [[S_facebook]] === Export des informations de plongée vers _Facebook_ -L'export des plongées vers _Facebook_ est géré différemment des autres types -d'export car une connexion vers _Facebook_ est nécessaire, nécessitant un -identifiant et un mot de passe. À partir du menu principal, si vous -sélectionnez _Fichier -> Préférences -> Facebook_, un écran de connexion est -présenté (image *A* sur la gauche, ci dessous). Entrez l'identifiant et le -mot de passe _Facebook_. Une fois connecté à _Facebook_, le panneau de -l'image *B* ci dessous est présenté, avec un bouton _Déconnecter de -Facebook_ pour fermer la connexion _Facebook_. +Export of dives to _Facebook_ is handled differently from other types of +export because a connection to _Facebook_ is required, needing a _Facebook_ +userID and password. If, from the *Main Menu*, you select _File -> +Preferences -> Facebook_, a login screen comes up. (image *A* to the left, +below). Provide a _Facebook_ userID and password. Once logged into to +_Facebook_ , the panel in image *B*, below is shown, including a _Disconnect +from Facebook_ button to close the _Facebook_ connection. image::images/facebook1_f20.jpg["Figure: Facebook login", align="center"] -From the _Subsurface_ window it is easy to determine whether _Subsurface_ -has a valid connection to _Facebook_ From the *Main Menu*, select _Share on --> Facebook_ (image *A*, below). Normally, the _Facebook_ option is greyed +From the _Subsurface_ window it’s easy to determine whether _Subsurface_ has +a valid connection to _Facebook_ From the *Main Menu*, select _Share on -> +Facebook_ (image *A*, below). Normally, the _Facebook_ option is greyed out. But if there is a connection to _Facebook_, this option is active -(i.e. in black colour and can be selected). - -Une fois qu'une connexion à _Facebook_ est établie, transférer un profil de -plongée vers _Facebook_ est facile. Assurez-vous que la plongée à transférer -est affichée dans le panneau *Profil de plongée* de _Subsurface_. Si, à -partir du *menu principal*, vous sélectionnez _Partager sur -> Facebook_, -une fenêtre s'affiche, pour déterminer quelles informations seront -transférées avec le profil de plongée (voir l'image *B* ci-dessous). Pour -transférer un profil de plongée vers _Facebook_, le nom d'un album -_Facebook_ doit être fourni. Les cases à cocher sur la partie gauche -permettent de sélectionner des informations supplémentaires à transférer -avec le profil de plongée. Ces informations sont affichées dans le champs de -texte sur la partie droite du panneau. (image *B* ci dessous). Vous pouvez -facilement modifier le message qui sera envoyé avec le profil de -plongée. Une fois les informations supplémentaires ajoutées et vérifiées, -sélectionner le bouton _OK_ qui lance le transfert vers _Facebook_. Après un -moment, une fenêtre apparait indiquant le succès du transfert. - -À la fois l'album créé et la publication sur votre ligne temporelle seront -marquées comme privés. Pour que vos amis puissent voir la publication, -modifier les permissions à partir d'une connexion Facebook standard depuis -un navigateur ou l'application Facebook. Malgré que cela soit une étape -supplémentaire, c'est la meilleure solution pour éviter d'avoir des -publications non désirées sur votre ligne temporelle publique. +(i.e. in black color and can be selected). + +Having established a login to _Facebook_, transferring a dive profileto a +_Facebook_ timeline is easy. Be sure the dive to be transferred to the +timeline is shown in the _Subsurface_ *Dive Profile* panel. If, from the +*Main Menu*, you select _Share on -> Facebook_ (see image *A* below), a +dialogue box is shown, determining the amount of additional information +transferred along with the dive profile (image *B*, below). To transfer a +dive profile to _Facebook_, the name of a _Facebook_ album is needed. The +checkboxes on the left hand side let you decide how much additional +information should be transferred with the dive profile. This information is +shown in the text box on the right hand side of the panel (image *B*, +below). You can easily edit the message that will be posted with the dive +profile. After specifying the additional information and verifying the +text, select the _OK_ button that triggers the transfer to _Facebook_. After +the transfer is done, an acknowledgement dialogue appears, indicating it was +successful. + +Both the album created and the post to your timeline will be marked as +private. In order for friends to be able to see it, change its permissions +from a regular Facebook login either in a browser or a Facebook app. image::images/facebook2_f20.jpg["Figure: Facebook login", align="center"] @@ -2695,8 +2605,8 @@ principal et en cliquant sur le bouton approprié dans le panneau des préférences Facebook. [[S_Export_other]] -=== Export dive information to other destinations or formats -For non-_Facebook exports_, the export function can be reached by selecting +=== Export dive information to other destinations or formats +For non-_Facebook exports_, the export function can be found 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 @@ -2713,13 +2623,13 @@ A dive log or part of it can be saved in three formats: 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_, you need 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_. + service to upload dive log data from _Subsurface_. -* _DiveShare_ is also a dive log repository on the Internet focusing on the - recreational dives. In order to upload dives one has to provide a used ID, - so registration with _http://scubadiveshare.com_ is required. +* _DiveShare_ is also a dive log repository on the Internet focusing on + recreational dives. To upload dives, you need a user ID, so registration + with _http://scubadiveshare.com_ is required. * _CSV dive details_, that includes the most critical information of the dive profile. Included information of a dive is: dive number, date, time, buddy, @@ -2738,14 +2648,14 @@ A dive log or part of it can be saved in three formats: pressure, gas pressures and MOD. The HTML export contains a search option to search the dive log. HTML export is specified on the second tab of the Export dialog (image *B* above). A typical use of this option is to export - all one's dives to a smartphone or a tablet where it would serve as a very - portable record of dives useful for dive companies that wish to verify the - dive history of a diver, often doing away with the need to carry one's - original logbook with one when doing dives with dive companies. + all one's dives to a smartphone or a tablet where it would serve as a + portable record of dives. That is useful for dive companies that wish to + verify the dive history of a diver, often doing away with the need to carry + an original logbook when doing dives with dive companies. * _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. If one - selects any of the dive sites on the map, a summary of the dive is available + some information about it are indicated. This map is not editable. If you + select any of the dive sites on the map, a summary of the dive is available in text, as shown in the image below. image::images/mapview_f20.jpg["Figure: HTML Map export view", align="center"] @@ -2753,8 +2663,8 @@ image::images/mapview_f20.jpg["Figure: HTML Map export view", align="center"] * _Image depths_, which creates a text file that contains the file names of all photos or images attached to any of the selected dives in the _Dive - List_, together with the depth under water where of each of those photos - were taken. + List_, together with the depth underwater where of each of those photos was + taken. * _General Settings_, under the HTML tab, provides the following options: @@ -2769,27 +2679,26 @@ image::images/mapview_f20.jpg["Figure: HTML Map export view", align="center"] * 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 +Export to other formats can be done 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 +record of diving activities for one's own pleasure, but it’s important +information required for admission to training courses or sometimes even +diving sites. The security of the dive log is critical. 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 you can access your dive log from anywhere in the world. For this reason, facilities such as _divelogs.de_ and _Diving Log_ offer to store dive log information on the Internet. _Subsurface_ includes access to a transparently integrated cloud storage back end that is available to all Subsurface users. Storing and retrieving a dive log from the cloud is no more difficult than accessing the dives on the -local hard disk. The only requirement is that one should first register as +local hard disk. The only requirement is that you should first register as a user on the cloud. To use _Subsurface cloud storage_ , follow these steps: @@ -2813,45 +2722,45 @@ will be marked as verified and the _Subsurface cloud storage_ service is initial === Using _Subsurface cloud storage_ -** Once the cloud storage has been initialised, two new items appear in the +** Once the cloud storage has been initialized, two new items appear in the _File_ menu of the main menu system: _Open cloud storage_ and _Save to cloud storage_. -These options allow the user to load and save data to the _Subsurface +These options let you load and save data to the _Subsurface cloud storage_ server. -** In the _Defaults Preferences_ tab, one can select to use the _Subsurface cloud -storage_ data as one's default data file by checking the check box marked _Cloud storage default file_. - This means that the data from -the _Subsurface cloud storage_ is loaded when _Subsurface_ starts ans saved there when one closes _Subsurface_. +** In the _Defaults Preferences_ tab, you can select to use the _Subsurface cloud +storage_ data as the default data file by checking the box marked _Cloud storage default file_. + This means the data from +the _Subsurface cloud storage_ is loaded when _Subsurface_ starts and saved there when _Subsurface_ closes. ** _Subsurface_ keeps a local copy of the data and the cloud facility remains fully -functional even if used while disconnected to the Internet. _Subsurface_ simply synchronises the -data with the cloud server the next time ithe program is used while the computer is +functional even if used while disconnected to the Internet. _Subsurface_ simply synchronizes the +data with the cloud server the next time the program is used while the computer is connected to the Internet. [[S_Cloud_storage]] === Web access to _Subsurface cloud storage_ One of the nice side benefits of using _Subsurface cloud storage_ is that -one can also access one's dive data from any web browser. Simply open +you can also access your dive data from any web browser. Simply open https://cloud.subsurface-divelog.org[_https://cloud.subsurface-divelog.org_], log in with the same email and password, and you can see an HTML export of -the last dive data that was synced to the _Subsurface cloud storage_. The -dive information that is shown is only the contents of the recorded dive -logs, NOT the calculated values shown in the *Profile* panel, including some -cylinder pressures, deco ceilings and O~2~/He/N~2~ partial pressures. +the last dive data that was synced to _Subsurface cloud storage_. The dive +information shown is only the contents of the recorded dive logs, NOT the +calculated values shown in the *Profile* panel, including some cylinder +pressures, deco ceilings and O~2~/He/N~2~ partial pressures. === Other cloud services -If one prefers not to use the integrated cloud storage of dive logs (and -don't need the web access), it is also simple to store dive logs in the -cloud 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. +If you prefers not to use the integrated cloud storage of dive logs (and +don't need the web access), it’s simple to store dive logs in the cloud +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 a 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, +on your 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 @@ -2859,17 +2768,17 @@ 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 +In this way a dive log in your _Dropbox_ folder can be accessed seamlessly +from the Internet and can be accessed anywhere 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 on _Dropbox_, 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 _Dropbox_, 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. +Alternatively you can use _Dropbox_ as a way back up your dive log. To Store +a dive log on _Dropbox_, 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 _Dropbox_, 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. @@ -2878,21 +2787,20 @@ same process could be used for the Cloud-based storage of dive logs. [[S_PrintDivelog]] == Printing a dive log -_Subsurface_ provides a simple and flexible interface to print a whole dive log or only a few selected dives. +_Subsurface_ provides a simple and flexible way to print a whole dive log or only a few selected dives. Pre-installed templates or a custom written template can be used to choose where the data are fitted into the page. -Before printing, two decisions are required: +Some decisions need to be made before printing: -- Should the whole dive log be printed or only part of it? If only part of the - dive log is required, then select the required dives from the *Dive List* - panel. -- If the dive profiles needs printing, what gas partial pressure information +- Should the whole dive log be printed or only part of it? If only part is + required, select the required dives from the *Dive List* panel. +- If the dive profiles are printed, what gas partial pressure information should be shown? Select the appropriate toggle-buttons on the button bar to the left of the *Dive Profile* panel. -If _File -> Print_ is selected from the Main menu, the the dialogue below -(image *A*) appears. Three specifications are needed to achieve the desired -information and page layout: +If _File -> Print_ is selected from the Main menu, the dialogue below (image +*A*) appears. Three specifications are needed to get the desired information +and page layout: image::images/Print1_f22.jpg["FIGURE: Print dialogue", align="center"] @@ -2904,14 +2812,14 @@ image::images/Print1_f22.jpg["FIGURE: Print dialogue", align="center"] 2. Under _Print options_ select: -- Printing only the dives selected from the dive list prior to activating the +- Printing only the dives selected from the dive list before activating the print dialogue by checking the box _Print only selected dives_. If this - check box is *not* checked all dives in the *Dive List* panel are printed. -- Printing in colour, achieved by checking the box with _Print in colour_. If - this check box is not checked, printing is in monochrome (grey scale). + check box is *not* checked ALL dives in the *Dive List* panel are printed. +- Printing in color, done by checking the box with _Print in color. If this + check box is not checked, printing is in black and white. Under _Template_ select a template to be used as the page layout. There are -several templates (see image *B*, above). +several choices. (see image *B*, above). - _Table_: This prints a summary table of all dives selected (see below). @@ -2932,15 +2840,15 @@ image::images/print2_f22.jpg["FIGURE: Print one dive / page", align="center"] - _Two Dives_: Print two dives per page, also showing the dive profiles. - _Six Dives_: Print six dives per page, also showing the dive profiles. -Users can _Preview_ the printed page by selecting the _Preview_ button on -the dialogue (see image *A* at the start of this section). After preview, -changes to the options in the print dialogue can be made, resulting in a -layout that fits personal taste. +You can _Preview_ the printed page by selecting the _Preview_ button on the +dialogue (see image *A* at the start of this section). After preview, you +can change the options in the print dialogue, so the layout fits personal +taste. Next, select the _Print_ button (see image *A* at the start of this -section). This activates the regular print dialogue used by the user -operating system, allowing one to choose a printer and to set its properties -(see image below): +section). This activates the regular print dialogue used by the operating +system, letting you choose a printer and set its properties (see image +below): image::images/Print_print_f22.jpg["FIGURE: Print dialog", align="center"] @@ -2954,7 +2862,7 @@ image::images/Printpreview.jpg["FIGURE: Print preview page", align="center"] === Créer un modèle d'impression personnalisé (avancé) Writing a custom template is an effective way to produce highly customized -printouts. Subsurface uses HTML templates to render printing. One can create +printouts. Subsurface uses HTML templates to render printing. You can create a template, export a new template, import an existing template and delete an existing template by using the appropriate buttons under the _Template_ dropdown list in the print dialogue. See <<S_APPENDIX_E,APPENDIX E>> for @@ -2963,16 +2871,16 @@ information on how to write or modify a template. [[S_Configure]] == Configurer un ordinateur de plongée -_Subsurface_ permet de configurer son ordinateur de plongée. Actuellement, -les familles d'ordinateurs supportés sont Heinrichs-Weikamp (OSTC 2, OSTC 3) -et Suunto Vyper (Stinger, Mosquito, D3, Vyper, Vytec, Cobra, Gekko et -Zoop). De nombreux paramètres de ces ordinateurs de plongée peuvent être -lues et modifiées. La première étape est de s'assurer que les pilotes pour -votre ordinateur de plongée sont installés (également nécessaire pour -télécharger les plongées) et que le nom de périphérique de l'ordinateur de -plongée est connu. Voir -<<_appendix_a_operating_system_specific_information_for_importing_dive_information_from_a_dive_computer,ANNEXE -A>> pour plus d'informations sur la manière de procéder. +_Subsurface_ lets you 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. To begin, be sure the appropriate hardware +driver is installed for the dive computer (also required for downloading +dives) and 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. Une fois que l'ordinateur de plongée est connecté à _Subsurface_, sélectionner _Fichier -> Configurer l'ordinateur de plongée_, à partir du @@ -2982,8 +2890,8 @@ plongée à partir du panneau à gauche (voir l'image ci-dessous). image::images/Configure_dc_f20.jpg["FIGURE: Configure dive computer", align="center"] -En utilisant les boutons appropriés du panneau de configuration, les actions -suivantes peuvent être réalisées : +Using the appropriate buttons on the configuration panel, the following +actions can be done: - *Récupérer les détails disponibles*. Cela charge la configuration existante à partir de l'ordinateur de plongée dans _Subsurface_, en l'affichant dans le panneau de configuration. @@ -3001,13 +2909,13 @@ suivantes peuvent être réalisées : == Setting user _Preferences_ for _Subsurface_ There are several user-definable settings within _Subsurface_, found by -selecting _File -> Preferences_. The settings are performed in seven groups: +selecting _File -> Preferences_. The settings are in seven groups: *Defaults*, *Units*, *Graph*, *Language* and *Network*, *Facebook* and -*Georeference*, all of which 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*. If *Discard* is selected, -changes to the preferences are not saved. +*Georeference*. All operate on the same principles: the user must specify +settings that are to be changed, then save them using the *Apply* +button. After applying all the new settings users can then leave the +settings panel by selecting *OK*. If *Discard* is selected, changes to the +preferences are not saved. === Defaults @@ -3015,18 +2923,18 @@ There are several settings in the *Defaults* panel: image::images/Pref1_f20.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. + ** *Lists and tables*: Here you can specify the font type and font size of the + *Dive Table* panel: By decreasing the font size of the *Dive Table*, you can see more dives on a screen. - ** *Dives*: For the _Default Dive File_ one needs to specify the directory and - file name of one's + ** *Dives*: For the _Default Dive File_ you need to specify the directory and + file name of your electronic dive log book. This is a file with filename extension of either _.xml_ or _.ssrf_. When launched, _Subsurface_ will automatically load the specified dive log book. There are three options: - _No default file_: When checked, _Subsurface_ does not automatically load a dive log at startup. - _Local default file_: When checked, _Subsurface_ automatically loads a dive log from the local hard disk as described above. - _Cloud storage default file_: When checked, _Subsurface automatically loads the dive log from the cloud - device that was initialised using the *Preferences* _Network_ tab (see below). + device that was initialized using the *Preferences* _Network_ tab (see below). ** *Display invalid*: Dives can be marked as invalid (when a user wishes to hide dives that he/she doesn't consider valid dives, e.g. pool dives, but still want to @@ -3050,14 +2958,14 @@ image::images/Pref1_f20.jpg["FIGURE: Preferences defaults page", align="center"] === Units image::images/Pref2_f20.jpg["FIGURE: Preferences Units page", align="center"] -Here users can choose between metric and imperial units of depth, pressure, +Here you 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, one 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. +button at the top, you can specify that all units are in the chosen +measurement system. Alternatively, if you select the *Personalize* radio +button, units can be selected independently, with some in the metric system +and others in imperial. -Irrespective of the above settings, dive time measurements can be either in +Regardless of the above settings, dive time measurements can be either in seconds or minutes. Choose the appropriate option. GPS coordinates can be represented either as traditional coordinates (degrees, minutes, seconds) or as decimal degrees Choose the appropriate option. @@ -3069,24 +2977,26 @@ image::images/Pref3_f20.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 +*Show*: Here you 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, enabled by 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 + the dive, done by using the toolbar on the left hand side of the *Dive Profile* + panel. For each of these graphs you can specify a threshold value on the right-hand side of the Preferences panel. If any of the graphs go above the specified threshold level, the graph is - highlighted in red, indicating that the particular partial pressure threshold has been exceeded. + highlighted in red, indicating the particular partial pressure threshold has been exceeded. ** _Max pO~2~ is used for calculating the MOD when displaying the maximum operative depth (MOD) for a dive. Specify an appropriate partial pressure. A value of 1.4 is commonly used. -** _Draw dive computer reported ceiling red_: This checkbox allows exactly what it says. By default +** _Draw dive computer reported ceiling red_: This checkbox does exactly what it says. By default the computer reported ceiling is shown in white. Not all dive computers report ceiling values. If the dive computer does report it, it may differ from the ceilings calculated by _Subsurface_ because of the different algorithms and - gradient factors, 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 if 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_: If this box is checked, the *Dive Profile* panel contains a grey line that indicates - the mean depth of the dive up to any time instant during the dive. Normally this is a u-shaped line indicating the deepest mean depth just before the + gradient factors, as well as the dynamic way a + dive computer calculates ceilings during a dive. +** _Show unused cylinders in Equipment Tab_: This checkbox allows display of information about unused cylinders when viewing the +*Equipment Tab*. If this box is not checked, and if 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_: If this box is checked, the *Dive Profile* panel contains a grey line that shows + the mean depth of the dive, up to any time instant during the dive. Normally this is a u-shaped line indicating the deepest mean depth just before ascent. * *Misc*: @@ -3095,8 +3005,8 @@ the dive profile: ** Gradient Factors (GFLow and GFHigh):* 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 + Gradient factors add conservatism to nitrogen exposure during a dive, in a + similar way that many dive computers have a conservative 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 70/90 are considered @@ -3108,8 +3018,8 @@ the dive profile: *** link:http://www.rebreatherworld.com/general-and-new-to-rebreather-articles/5037-gradient-factors-for-dummies.html[Gradient factors for dummies, by Kevin Watts] - ** _CCR: Show setpoints when viewing pO2:_ With this checkbox ativated, the pO~2~ - graph on the dive profile has an overlay in red which inticates the CCR setpoint + ** _CCR: Show setpoints when viewing pO2:_ With this checkbox activated, the pO~2~ + graph on the dive profile has an overlay in red which indicates the CCR setpoint values. See the section on xref:S_CCR_dives[Closed Circuit Rebreather dives]. ** _CCR: Show individual O~2~ sensor values when viewing pO~2~:_ Show the pO~2~ @@ -3123,7 +3033,7 @@ the dive profile: during a particular dive. Setpoint changes during the dive can be added via the profile context menu. - ** _pSCR O~2~ metabolism rate:_ For a semiclosed rebreather (pSCR) system, this is the + ** _pSCR O~2~ metabolism rate:_ For a semi-closed rebreather (pSCR) system, this is the volume of oxygen used by a diver during a minute. Set this value for pSCR dive planning and decompression calculations. @@ -3137,22 +3047,21 @@ Choose a language that _Subsurface_ will use. image::images/Pref4_f20.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 operating system. If this -is for some reason undesirable one 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*. +A checkbox lets you 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 operating system. To change +it, uncheck this checkbox and pick a language / country combination from the +list of locations. The _Filter_ text box lists 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. This is important, for instance, when _Subsurface_ needs -to communicate with Internet services such as Cloud storage or the +to communicate with web services such as Cloud storage or the <<S_Companion,_Subsurface Companion app_>>. 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 +determined by your type of connection to the Internet and by the Internet +Service Provider (ISP) used. Your ISP should provide the appropriate information. image::images/Pref5_f20.jpg["FIGURE: Preferences Network page", align="center"] @@ -3167,54 +3076,52 @@ password are required so that _Subsurface_ can automatically pass through the proxy server to access the Internet. This information is usually obtained from one's ISP. -** _Subsurface cloud storage_: To store one's dive log in the cloud, a valid email address - and password are required. This allows _Subsurface_ to email security information - regarding cloud storage to a user, and to set up the cloud storage appropriately. +** _Subsurface cloud storage_: To store your dive log in the cloud, a valid email address + and password are required. This lets _Subsurface_ email security information + regarding cloud storage to you, and to set up cloud storage appropriately. Two additional options are given: - _Sync to cloud in the background_: This option allows saving of dive information to the cloud storage - while the user performs other tasks within _Subsurface_. + while you do other things within _Subsurface_. - _Save password locally_: This allows local storage of the cloud storage password. Note that this information is saved in raw text form, not encoded in any way. -** _Subsurface web service_: When one subscribes to the <<S_Companion,Subsurface web service>>, a very +** _Subsurface web service_: When you subscribe 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. + checking the option _Save User ID locally?_, you ensure a local copy of that userID is saved. [[S_Facebook]] -=== Accès Facebook -Ce panneau vous permet de vous connecter à votre compte Facebook pour -transférer des informations de Subsurface vers Facebook. +=== Facebook Access +This panel lets you log into a Facebook account in order to transfer +information from Subsurface to Facebook. image::images/Pref6_f20.jpg["FIGURE: Facebook login panel", align="center"] -Si un identifiant Facebook et un mot de passe valides ont été fournis, une -connexion vers Facebook est créée. Cette connexion est fermée lorsque -Subsurface est fermé. Pour le moment, la case à cocher nommée "Conserver ma -connexion à Subsurface", sur l'écran de connexion, n'a aucun -effet. Reportez-vous à la section xref:S_facebook[Export des profils de -plongée vers Facebook] pour plus d'informations. +If you provide a valid Facebook userID and password, a connection to +Facebook is created. That connection is closed when one closing down +Subsurface. Currently the checkbox labelled "Keep me logged in to +Subsurface", on the login screen has no effect. See the section +xref:S_facebook[Exporting dive profiles to Facebook] for more information. === Georeference _Subsurface_ provides a geo-lookup service (that is, given the coordinates -of a dive site (derived from a click on the *Dive Map panel* at the bottom +of a dive site) derived from a click on the *Dive Map panel* at the bottom right of the _Subsurface_ window, or from a GPS instrument or from the -_Subsurface_ Companion app), a lookup on the Internet is performed to find -the name of the closest known location. Obviously this function only works -if _Subsurface_ has an Internet connection. The preference of the dive site -name can be configured, e.g. _Country/State/City_ or _City/State/Country_ -(see image below). +_Subsurface_ Companion app). A search on the Internet is done to find the +name of the closest known location. This function only works if _Subsurface_ +has an Internet connection. The preference of the dive site name can be +configured, e.g. _Country/State/City_ or _City/State/Country_ (see image +below). image::images/Pref7_f20.jpg["FIGURE: Facebook login panel", align="center"] [[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. +Dive planning is an advanced feature of _Subsurface_, accessed 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"] @@ -3241,12 +3148,11 @@ used under the following conditions: 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 Notes. +into the sections on the left hand side of the screen. They are: Available +Gases, Rates, Planning, Gas Options and 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 +At the top right hand is a green *design panel* on 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. @@ -3260,17 +3166,17 @@ image::images/PlannerWindow1_f20.jpg["FIGURE: Dive planner startup window", alig === Open circuit dives -- Towards the centre bottom of the planner (circled in blue in the image +- Towards the center bottom of the planner (circled in blue in the image above) is a dropbox with three options. Select the appropriate one of these: ** Open Circuit (the default) ** CCR ** pSCR - Choose the Open Circuit option. -- In the top left-hand area of the planning screen, ensure that the constant - dive parameters are appropriate. These are: Start date and time of the - intended dive, Atmospheric Pressure and Altitude above sea level of the dive - site. The atmospheric pressure can also be entered as an altitude in metres, +- In the top left-hand area of the planning screen, be sure the constant dive + parameters are appropriate. These are: Start date and time of the intended + dive, Atmospheric Pressure and Altitude above sea level of the dive + site. The atmospheric pressure can also be entered as an altitude in meters, assuming a sea-level atmospheric pressure of 1.013 bar. - In the table labelled _Available Gases_, add the information of the @@ -3285,11 +3191,11 @@ image::images/PlannerWindow1_f20.jpg["FIGURE: Dive planner startup window", alig the top right-hand of the dialogue. - The profile of the planned dive can be created in two ways: - * Drag the waypoints (the small white circles) on the existing dive profile in - a way to represent the dive. Additional waypoints can be created by - double-clicking the existing dive profile. Waypoints can be deleted by - right-clicking a particular waypoint and selecting the _delete_ item from - the resulting context menu. + * Drag the waypoints (the small white circles) on the existing dive profile to + represent the dive. Additional waypoints can be created by double-clicking + the existing dive profile. Waypoints can be deleted by right-clicking a + particular waypoint and selecting the _delete_ item from the resulting + context menu. * The most efficient way to create a dive profile is to enter the appropriate values into the table marked _Dive planner points_. The first line of the table represents the duration and the final depth of the descent from the @@ -3302,29 +3208,24 @@ image::images/PlannerWindow1_f20.jpg["FIGURE: Dive planner startup window", alig ==== Recreational dives -Recreational mode is what comes closest to planning a dive based on the -non-decompression limit (NDL). It computes the maximal time a diver can -stay at the current depth without incurring any mandatory decompression -stops and without using more than the existing gas (minus a reserve). The -planner automatically takes into account the nitrogen load incurred in -previous dives. But conventional dive tables are also used in a way that can -take into account previous dives. Why use a dive planner for recreational -dives? Using recreational dive tables, the maximum depth of a dive is taken -into account. However, few dives are undertaken at a constant depth -corresponding to the maximum depth (i.e. a "square" dive profile). This -means that dive tables overestimate the nitrogen load incurred during -previous dives. The _Subsurface_ dive planner calculates nitrogen load -according to the real dive profiles of all uploaded previous dives, in a -similar way as dive computers calculate nitrogen load during a dive. This -means that the diver gets 'credit' in terms of nitrogen loading for not -remaining at maximum depth during previous dives, enabling planning of a -longer subsequent dive. For the planner to work it is therefore crucial to -upload all previous dives onto _Subsurface_ before performing dive planning. - +Recreational mode is what comes closest to planning a dive based on the non-decompression limit (NDL). +It computes the maximum time a diver can stay at the current depth without needing mandatory decompression +stops and without using more than the existing gas (minus a reserve). The planner automatically takes +into account the nitrogen load incurred in previous dives. But conventional dive tables are also used in a +way that can take into account previous dives. Why use a dive planner for recreational dives? Using +recreational dive tables, the maximum depth of a dive is taken into account. But few dives are +done at a constant depth corresponding to the maximum depth (i.e. a "square" dive profile). This means +dive tables overestimate the nitrogen load incurred during previous dives. The _Subsurface_ +dive planner calculates nitrogen load according to the real dive profiles of all uploaded previous dives, +in a similar way as dive computers calculate nitrogen load during a dive. This means that the diver gets 'credit,' +in terms of nitrogen load, for not remaining at maximum depth during +previous dives, so a longer subsequent dive can be planned. + For the planner to work it's crucial to upload all previous dives +onto _Subsurface_ before doing dive planning. To plan a dive, the appropriate settings need to be defined. -Ensure that the date and time is set to that of the intended dive. This -allows calculation of the nitrogen load incurred during previous dives. +Ensure the date and time is set to that of the intended dive. This allows +calculation of the nitrogen load incurred during previous dives. - Immediately under the heading _Planning_ are two checkboxes _Recreational_ and _Safety Stop_. Check these two boxes. @@ -3334,24 +3235,23 @@ allows calculation of the nitrogen load incurred during previous dives. _Available gases_. - The planner calculates whether the specified cylinder contains enough - air/gas to complete the planned dive. In order for this to be realistic, + air/gas to complete the planned dive. In order for this to be accurate, under _Gas options_, specify an appropriate surface air consumption (SAC) rate for _Bottom SAC_. Suitable values are between 15 l/min and 30 l/min, with novice divers or difficult dives requiring SAC rates closer to 30l/min. -- Define the amount of gas that the cylinder must have at the end of the - bottom section of the dive just before ascent. A value of 50 bar is often - used. The reason for this reserve gas is to provide for the possible need to - bring one's buddy to the surface using gas sharing. How much gas is used in - sharing depends on the depth of the ascent. This can be a bit hard to - estimate, so most agencies assume a fixed amount of gas, or actually of - pressure e.g. 40 or 50 bar or 25% or 33% (rule of thirds). But _Subsurface_ - can do better because it knows about the ascent and that is why we add the - amount of gas during the ascent (i.e. the "deco gas“). Subsurface still - uses a fixed pressure „reserve“ but that is supposed to be for the - additional gas used around the realisation that there is a problem and one's - pulse rate goes up when one starts to buddy breathe. This reserve amount is - user configurable. +- Define the amount of gas the cylinder must have at the end of the bottom + section of the dive just before ascent. A value of 50 bar is often used. The + reason for this reserve gas is to provide for the possible need to bring a + buddy to the surface using gas sharing. How much gas is used in sharing + depends on the depth of the ascent. This can be difficult to estimate, so + most agencies assume a fixed amount of gas, or actually of pressure e.g. 40 + or 50 bar or 25% or 33% (rule of thirds). But _Subsurface_ can do better + because it knows about the ascent and that is why we add the amount of gas + during the ascent (i.e. the "deco gas“). Subsurface still uses a fixed + pressure "reserve" but that's supposed to be for the additional gas used + when there's a problem and your pulse rate goes up when you start to buddy + breathe. This reserve amount is user configurable. - Define the depth of the dive by dragging the waypoints (white dots) on the dive profile or (even better) defining the appropriate depths using the @@ -3365,9 +3265,9 @@ allows calculation of the nitrogen load incurred during previous dives. - The ascent speed can be changed. The default ascent speeds are those considered safe for recreational divers. -The dive profile in the planner indicates the maximum dive time within -no-deco limits using the Bühlmann ZH-L16 algorithm and the gas and depth -settings specified as described above. The _Subsurface_ planner allows rapid +The dive profile in the planner shows the maximum dive time within no-deco +limits using the Bühlmann ZH-L16 algorithm and the gas and depth settings +specified as described above. The _Subsurface_ planner allows rapid assessment of dive duration as a function of dive depth, given the nitrogen load incurred during previous dives. The dive plan includes estimates of the amount of air/gas used, depending on the cylinder settings specified under @@ -3378,36 +3278,36 @@ means that recreational dive limits are exceeded and either the dive duration or the dive depth needs to be reduced. Below is an image of a dive plan for a recreational dive at 30 -metres. Although the no-deco limit (NDL) is 23 minutes, the duration of the -dive is limited by the amount of air in the cylinder, reflected by the -information in the text box at the bottom right of the panel that requires -sufficient air for buddy-sharing during the ascent. +meters. Although the no-deco limit (NDL) is 23 minutes, the duration of the +dive is limited by the amount of air in the cylinder. That is shown in the +text box at the bottom right of the panel, requiring sufficient air for +buddy-sharing during ascent. image::images/rec_diveplan.jpg["FIGURE: A recreational dive plan: setup", align="center"] ==== Non-recreational open circuit dives, including decompression Non-recreational dive planning involves exceeding the no-deco limits and/or -using multiple breathing gases. Such dives are planned in three stages: +using multiple breathing gases. These dives are planned in three stages: -*a) Nitrogen management*: This is performed by specifying the rates for descent and ascent, +*a) Nitrogen management*: This is done by specifying the rates for descent and ascent, as well as the deco model (GFLow, GFHigh or Conservatism level) under the headings _Rates_ and _Planning_ to the bottom left of the planning screen. Two deco models are supported the Bühlmann model and the VPM-B model. Select one of the two models. When selecting the Bühlmann model, the gradient factors (GF_high and GF_low need to be specified. 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 values 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. +used without changing the original values in the _Preferences_. +Gradient Factor settings strongly affect the calculated ceilings and their depths. +A very low GFLow value brings on decompression stops early during the dive. ** For more information about Gradient factors, see the section on xref:S_GradientFactors[Gradient Factor Preference settings]. If the VPM-B model is selected, the Conservatism_level needs to be specified on a scale of 0 (least conservative) to 4 (most conservative). This model tends to give deco stops at deeper levels than the Bühlmann model and often results in slightly shorter dive durations than the Bühlmann model. When -selecting one of these models, keep in mind that they are NOT exact -physiological models but only mathematical models that appear to work in -practice. +selecting one of these models, keep in mind they are NOT exact physiological +models but only mathematical models that appear to work in practice. For more information external to this manual see: @@ -3421,14 +3321,14 @@ for Divers_, by Mark Powell (2008). Aquapress] Southend-on-Sea, UK. ISBN 10: modèles de décompression Bühlmann et VPM-B. 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 by a -light grey line on the dive profile. 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. +and is specified for several depth ranges, using the average (or mean) depth +as a yardstick. The mean depth of the dive plan is shown by a light grey +line on the dive profile. 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, 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 @@ -3439,57 +3339,57 @@ stages. Normally, a partial pressure of 1.6 bar is not exceeded. PO2 settings an _Available Gases_ dialog. Normally the planner decides on switching to a new gas when, during ascent, the partial pressure of the new gas has increased to 1.6 bar. -*c) Gas management*: With open-circuit dives this is a primary consideration. One needs to keep within the limits of the amount of gas within the dive +*c) Gas management*: With open-circuit dives this is a primary +consideration. Divers need to keep within the limits of the amount of +gas within the dive cylinder(s), allowing for an appropriate margin for a 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 +liters/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 15-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. +dive (_deco SAC_). Values of 15-30 l/min are common. For good gas management, a guess +is not sufficient and you needs to +monitor gas consumption on a regular basis, dependent on different dive conditions and/or equipment. The planner calculates the total volume of gas used during the dive and issues 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. +if you exceeds the total amount of gas available. Good practice demands that divers 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 bue 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. It is NOT necessary to specify the ascent -part of the dive since the planner calculates this, based on the settings -that have been specified. If any of the management limits (for nitrogen, -oxygen or gas) is exceeded, the surface above the dive profile changes from -BLUE to RED. +Now you can start the detailed time-depth planning of the dive. _Subsurface_ +offers an unique graphical interface for doing planning. Themechanics are +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 blue 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 the profile reflects the intended dive. Drag the waypoints to +represent the depth and duration of the dive. It is NOT necessary to specify +the ascent part of the dive since the planner calculates this, based on the +settings that have been specified. If any of the management limits (for +nitrogen, oxygen or gas) are 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 _Available Gases_ table. 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. +table on the left of the dive planner panel. Be sure the _Used Gas_ value in +each row of that table corresponds to one of the gas mixtures specified in +the _Available Gases_ table. 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 fulfill decompression requirements for that dive. A waypoint can be +moved by selecting it and by using the arrow keys. The waypoints listed in +the _Dive Planner Points_ dialogue can be edited by hand in order to get a +precise presentation of the dive plan. In fact, you can create the whole +dive profile by editing the _Dive Planner Points_ dialog. + +Show 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. These changes +can be deleted by right-clicking the gas change and 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 @@ -3505,9 +3405,9 @@ using EAN50 and using the settings as described above. image::images/DivePlanner2_f20.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 top middle of the planner. The saved dive plan will -appear in the *Dive List* panel of _Subsurface_. +Once the above steps have been completed, save by clicking the _Save_ button +towards the top middle of the planner. The saved dive plan will appear in +the *Dive List* panel of _Subsurface_. *The dive plan details* @@ -3534,7 +3434,7 @@ The parameters of the pSCR dive can be set by selecting _File -> Preferences from the main menu, where the gas consumption calculation takes into account the pSCR dump ratio (default 10:1) as well as the metabolism rate. The calculation also takes the oxygen drop accross the mouthpiece of the rebreather into account. If the -pO~2~ drops below what is considered a save value, a warning appears in the _Dive plan +pO~2~ drops below what is considered safe, a warning appears in the _Dive plan details_. A typical pSCR configuration is with a single cylinder and one or more bail-out cylinders. Therefore the setup of the _Available gases_ and the _Dive planner points_ tables are very similar to that of a CCR dive plan, described below. However, no oxygen setpoints @@ -3558,30 +3458,30 @@ cylinder since it is implied when the _CCR_ dropdown selection is made. the main menu. All user-entered segments in the _Dive planner points_ table use the default setpoint value. Then, different setpoints can be specified for dive segments in the _Dive planner points_ table. A zero setpoint -means the diver bails out to open circuit mode for that segment. The decompression is always calculated +means the diver bails out to open circuit mode for that segment. Decompression is always calculated using the setpoint of the last manually entered segment. So, to plan a bail out ascent for a CCR dive, add a one-minute dive segment to the end with a setpoint value of 0. The decompression -algorithm does not switch deco-gases automatically while in CCR mode (i.e. when a positive setpoint is specified) but, -of course, this is calculated for bail out ascents. +algorithm does not switch deco-gases automatically while in CCR mode (i.e. when a positive setpoint is specified) but +this is calculated for bail out ascents. The dive profile for a CCR dive may look something like the image below. image::images/Planner_CCR1_f20.jpg["FIGURE: Planning a CCR dive: setup", align="center"] Note that, in the _Dive plan details_, the gas consumption for a CCR segment -is not calculated, so gas consumptions of 0 litres are the norm. +is not calculated, so gas consumptions of 0 liters are the norm. [[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. +List*, like any other dive log. Within the *Dive List* there is no way to +change a saved dive plan. To change 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, letting changes be made and +saved as usual. -In addition there is the option "Save new". This keeps the original planned +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 @@ -3590,27 +3490,27 @@ 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. +repetitive dive set are specified appropriately in the top left-hand _Start +Time_ field. _Subsurface_ calculates the gas loading figures and the affect +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 you have just completed a long/deep dive and are planning another dive, +then highlight, in the *Dive List*, the dive that has just been done then +activate the planner. Depending on the start time of the planned dive, the +planner takes into account the gas loading during the completed dive and +plans accordingly. 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. +template dive can be created conforming to one of the configurations. If you +want to plan a dive using this configuration, 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. +Plan Details_ for wet notes. You can also cut and paste the _Dive Plan +Details_ to include 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 @@ -3621,7 +3521,7 @@ 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 +function on the main menu in the same way as for dive logs or by copy and paste to a word processor. == Description des éléments du menu principal de Subsurface @@ -3633,16 +3533,14 @@ des sections de ce manuel traitant des opérations relatives. === Fichier - <<S_NewLogbook,_Nouveau carnet de plongée_>> - Fermer le carnet de plongée actuellement ouvert et supprime toutes les informations de plongées. -- _Ouvrir un carnet de plongée_ - Cela ouvre une fenêtre pour sélectionner le - carnet de plongée à ouvrir. +- _Open logbook_ - Open the file manager to select a dive logbook to open. - _Open cloud storage_ - Open the dive log previously saved in <<S_Cloud_storage,_Cloud storage_>>. -- _Sauvegarder_ - Enregistrer le carnet de plongée qui est actuellement - ouvert. +- _Save_ - Save the dive logbook currently open. - _Save to cloud storage_ - Save the current dive log to <<S_Cloud_storage,_Cloud storage_>>. - _Enregsitrer sous_ - Enregistrer le carnet actuel sous un nom différent. -- _Fermer_ - Fermer le carnet de plongée actuellement ouvert. +- _Close_ - Close the dive logbook currently open. - <<S_ExportLog,_Exporter_>> - Exporter le carnet de plongée actuellement ouvert (ou les plongées sélectionnées dans le carnet) vers un des nombreux formats. @@ -3672,15 +3570,14 @@ des sections de ce manuel traitant des opérations relatives. === Journal (log) - <<S_EnterData,_Ajouter une plongée_>> - Ajouter manuellement une nouvelle plongée au panneau de la *liste des plongées*. -- _Edit dive_ - Edit a dive of which the profile was entered by hande and not - from a dive computer. -- <<S_DivePlanner,_Planifier une plongée_>> - Cette fonctionnalité permet de - planifier des plongées. +- _Edit dive_ - Edit a dive where the profile was entered by hand and not from + a dive computer. +- <<S_DivePlanner,_Planifier une plongée_>> - Planifier des plongées. - <<S_Replan,_Modifier la plongée dans le planificateur_>> - Modifier une plongée planifiée qui a été enregistrée dans la *liste des plongées*. -- <<S_CopyComponents,_Copier les composants de la plongée_>> - En - sélectionnant cette option, vous pouvez copier les informations de plusieurs - champs d'un journal de plongée vers le presse-papier. +- <<S_CopyComponents,_Copier les composants de la plongée_>> - Copier les + informations de plusieurs champs d'un journal de plongée vers le + presse-papier. - _Coller les composants de la plongée_ - Colle, dans les plongées sélectionnées dans la *liste des plongées*, les informations copiées au préalable avec l'option _Copier les composants de la plongée_. @@ -3689,7 +3586,7 @@ des sections de ce manuel traitant des opérations relatives. - <<S_Group,_Grouper automatiquement_>> - Grouper les plongées du panneau de *liste des plongées* dans des voyages de plongées. - <<S_DeviceNames,_Editer les noms des ordinateurs de plongée_>> - Modifier - les noms des ordinateurs de plongée pour faciliter vos journaux (logs). + les noms des ordinateurs de plongée pour coordonner vos journaux (logs). - <<S_Filter,_Filtrer la liste des plongées_>> - Sélectionner seulement certaines plongées, à partir de tags ou de critères de plongées. @@ -3705,9 +3602,8 @@ des sections de ce manuel traitant des opérations relatives. mondiale*. - _Statistiques annuelles_ - Affiche par année le résumé des statistiques des plongées effectuées. -- _Prev DC_ - If a single dive was logged from more than one dive computer, - switch to data from - ordinateur de plongée précédent. +- _Prev DC_ - Switch to data from previous dive computer, if a single dive was + logged from more than one. - _Ordinateur suivant_ - Passer à l'ordinateur de plongée suivant. - _Plein écran_ - Passer en mode plein écran. @@ -3734,9 +3630,9 @@ des sections de ce manuel traitant des opérations relatives. === Assurez-vous que les pilotes (drivers) nécessaires sont installés [icon="images/icons/drivers.jpg"] [NOTE] -Le système d'exploitation de l'ordinateur nécessite les bons pilotes pour -communiquer avec l'ordinateur de plongée de la façon utilisée par -l'ordinateur de plongée (Bluetooth, USB, infra-rouge). +The operating system of the desktop computer needs the appropriate drivers +in order to communicate with the dive computer, the way the dive computer +prefers (e.g. Bluetooth, USB, infra-red). * Sous Linux, les utilisateurs doivent avoir le bon module noyau de chargé. La plupart des distributions Linux le font automatiquement, de telle sorte que @@ -3760,12 +3656,11 @@ de documents et logiciels Silicon Labs]. === Comment trouver le nom du périphérique branché sur USB et paramétrer les permissions en écriture [icon="images/icons/usb.jpg"] [NOTE] -Lorsqu'un utilisateur connecte un ordinateur de plongée en utilisant l'USB, -généralement _Subsurface_ proposera soit une liste déroulante contenant le -bon nom (ou le point de montage pour un Uemis Zurich) ou la liste sera -désactivée si aucun nom de périphérique n'est nécessaire. Dans les rares cas -où cela ne fonctionnerait pas, voici quelques suggestions pour trouver le -nom de votre périphérique ; +When connecting a dive computer by using a USB connector, usually +_Subsurface_ will either propose a drop down list with 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 ways to find out what the device name is: .Sur Windows : @@ -3810,13 +3705,15 @@ détecté et connecté sur +ttyUSB3+. Cette information peut à présent être utilisée pour les paramètres d'importation en tant que +/dev/ttyUSB3+ pour que Subsurface utilise le bon port USB. -S'assurer que l'utilisateur possède les droits d'écriture sur le port série -USB : +Ensuring the user has write permission to the USB serial port: -Sur les systèmes similaires à Unix, les ports USB ne peuvent être accédés -que par des utilisateurs membres du groupe +dialout+. Si vous n'êtes pas -root, vous n'êtes peut-être pas membre de ce groupe et ne pouvez donc pas -utiliser le port USB. Si votre nom d'utilisateur est 'johnB' : +On Unix-like operating systems the USB ports can only be accessed by users +who are members special group that can be e.g. +dialout+ or +uucp+. This +can be verified by listing the appropriate device permissions e.g. by +ls -l +/dev/ttyUSB0+. Note that the number in the file name depends on how many USB +devices you have connected, and must be adjusted appropriately. If one is +not root, one may not be a member of that group and won't be able to use the +USB port. Let us assume one's username is 'johnB'. En tant que root, tapez : usermod -a -G dialout johnB+ (utilisateurs d'Ubuntu : +sudo usermod -a -G dialout johnB+) Cela ajoute johnB au groupe @@ -3826,7 +3723,9 @@ vérifiez que l'appartenance au groupe est bien effectif. Le groupe +dialout+ devrait être listé parmi les différents IDs. -Sous certaines circonstances, les modifications ne prennent effet qu'après une déconnexionpuis reconnexion sur l'ordinateur (sous Ubuntu, par exemple). +Sous certaines circonstances, les modifications ne prennent effet qu'après une déconnexion +puis reconnexion sur l'ordinateur (sous Ubuntu, par exemple). + Avec le bon nom de périphérique (par exemple +dev/ttyUSB3+) et avec un accès en écriture au port USB, l'ordinateur de plongée devrait se connecter et vous devriez pouvoir importer vos plongées. @@ -3838,10 +3737,10 @@ vous devriez pouvoir importer vos plongées. [NOTE] For dive computers communicating through Bluetooth like the Heinrichs Weikamp Frog or the Shearwater Predator, Petrel and Nerd there is a -different procedure to get the devices name to communicate with +different procedure to get the device’s name to communicate with _Subsurface_. Follow these steps: - * *For the dive computer, after enabling Bluetooth, ensure it is in Upload mode.* + * *For the dive computer, after enabling Bluetooth, be sure 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/Nerd, select _Dive Log -> @@ -3872,18 +3771,17 @@ 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 +Once the pairing is complete, the correct device is shown in the 'Device or Mount Point' drop-down in the _Subsurface_ *Import* dialog. ==== Sur Linux -Ensure Bluetooth is enabled on the _Subsurface_ computer. On most common +Be sure 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 on the right -of the toolbar at the top of the screen. Users have reported difficulties -with some Bluetooth controllers. If you have an onboard controller, try -that first. It is simplest if you remove any USB Bluetooth dongles. If you -have a USB dongle that came with your dive computer, try that before any -others. +straightforward. For instance, Gnome3 shows a Bluetooth icon on the right of +the toolbar at the top of the screen. Users have reported difficulties with +some Bluetooth controllers. If you have an onboard controller, try that +first. It is simplest if you remove any USB Bluetooth dongles. If you have +a USB dongle that came with your dive computer, try that before any others. Setting up a connection to download dives from your Bluetooth-enabled device, such as the _Shearwater Petrel_, is not yet an automated process and @@ -3920,7 +3818,7 @@ select 'Add new device'. The dive computer should appear. If asked for a password, enter 0000. Write down or copy the MAC address of your dive computer - this needed later and should be in the form 00:11:22:33:44:55. -If the graphical method didn't work, pair the device from the command +If the graphical method doesn't work, pair the device from the command line. Open a terminal and use +hciconfig+ to check the Bluetooth controller status @@ -4070,9 +3968,9 @@ 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 +you don’t 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 @@ -4080,15 +3978,15 @@ 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 +(this is a Uemis firmware limitation, not a _Subsurface_ issue) is that you 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 +the SDA. This will usually only happen the very first time you download 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 +displays an error that the dive computer ran out of space, the solution is +straightforward. 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 +download will continue where it stopped previously. You may have to do this more than once, depending on how many dives are stored on the dive computer. [[S_ImportingGalileo]] @@ -4108,14 +4006,14 @@ 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 +After executing this command, Subsurface will recognize 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]. Windows-based IrDA drivers for the Uwatec can also be downloaded from the -ScubaPro web site, drivers being located on the download page for the +ScubaPro web site, with drivers located on the download page for the ScubaPro SmartTrak software. For the Apple Mac, IrDA communication via the MCS7780 link is not available @@ -4169,9 +4067,9 @@ 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 +logs. Communication between dive computer and desktop computer utilizes the IrDA infra-red protocol. Only data for one dive can be downloaded at a time, -comprising three files: +in three files: - Setup configuration for the dive and key dive parameters (file with a .txt extension) @@ -4179,7 +4077,7 @@ comprising three files: - 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 +_Subsurface_ accesses the .txt and the .csv files to get dive log information. @@ -4205,29 +4103,29 @@ _Subsurface_ as follows: file with a filename extension of _.apd_ - 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 (labled +- In the dropdown list towards the bottom right of the dialogue (labeled 'Filter:'), select "APD log viewer". -- On the list of file names select the _.apd_ file that has been created - above. An import dialogue opens indicating the default settings for the data - in the _.apd_ file. If any changes are required, do this as for - xref:S_ImportingCSVDives[CSV imports]. +On the list of file names select the _.apd_ file created. An import +dialogue opens showing the default settings for the data in the +_.apd_ file. If changes are required, + do this as for xref:S_ImportingCSVDives[CSV imports]. image::images/APD_CSVimportF22.jpg["Figure: APD log viewer import", align="center"] -- The top left hand dropdown box in the import panel allows one to select the - APD dive computer for which the dive log needs to be imported. The default - it is DC1, _i.e._ the first of the two dive computers the APD uses. It is - possible to sequentially import the data for both dive computers by first - importing CD1 and then DC2.(*Hint*: The logs for the two dive computers are - viewed by selecting _View -> Next DC_ from the Main Menu after the uploading - has been completed) +- The top left hand dropdown box in the import panel lets you select the APD + dive computer for which the dive log needs to be imported. The default it is + DC1, _i.e._ the first of the two dive computers the APD uses. It is possible + to sequentially import the data for both dive computers by first importing + CD1 and then DC2.(*Hint*: The logs for the two dive computers are viewed by + selecting _View -> Next DC_ from the Main Menu after the uploading has been + completed) - Click the _Ok_ button at the bottom of the import panel. -The APD dive log will appear within _Subsurface_. The dive -computer-generated ceiling generated by the Inspiration can be viewed by -selecting the appropriate button on the left of the *Dive Profile*. Cylinder -pressure data are not logged by the APD equipment but can be manually -entered in the _Equipment_ Tab. +The APD dive log will appear within _Subsurface_. The dive computer- +generated ceiling provided by the Inspiration can be viewed by selecting the +appropriate button on the left of the *Dive Profile*. Cylinder pressure data +are not logged by the APD equipment but can be manually entered in the +_Equipment_ Tab. == APPENDIX C: Exporting Dive log information from external dive log software. @@ -4280,16 +4178,16 @@ naming conventions to export dive log data. *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. +divelog from Divemanager you need to locate the DM4/DM5 database where the +dives are stored. You 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 +4. Ouvrir l'explorateur Windows 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 @@ -4320,18 +4218,18 @@ directly imported to Subsurface. [icon="images/icons/mareslogo.jpg"] [NOTE] -Mares Dive Organiser is a Windows application. The dive log is kept as a +Mares Dive Organizer 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_. +database includes all Dive Organizer-registered divers on the particular +computer and all Mares dive computers used. The safest way to get a copy of +the dive database is to export the information to another compatible format +which can then be imported into _Subsurface_. -1. Within Dive Organiser, select _Database -> Backup_ from the main menu and +1. Within Dive Organizer, select _Database -> Backup_ from the main menu and back up the database to the desk top. This creates a zipped file - DiveOrganiserxxxxx.dbf. -2. Rename the file to DiveOrganiserxxxxx.zip. Inside the zipped directory is a - file _DiveOrganiser.sdf_. + DiveOrganizerxxxxx.dbf. +2. Rename the file to DiveOrganizerxxxxx.zip. Inside the zipped directory is a + file _DiveOrganizer.sdf_. 3. Extract the _.sdf_ file from the zipped folder to your Desktop. 4. The password for accessing the .zip file is _mares_. @@ -4342,11 +4240,11 @@ format which can be imported into _Subsurface_. [NOTE] The best way to bring your logs from DivingLog to Subsurface is to convert the whole database. This is because other export formats do not include all -the details, and we would lack e.g. gas switches and information of what -units are used. With database import, all this information is included and -readily available for us. +the details, and would lack, for example, gas switches and information of +what units are used. With database import, all this information is included +and readily available. -To transfer all files from DivingLog to Subsurface, do the following: +To transfer all files from DivingLog to Subsurface: 1. In DivingLog open the 'File -> Export -> SQLite' menu 2. Select 'Settings' button @@ -4355,28 +4253,25 @@ To transfer all files from DivingLog to Subsurface, do the following: 5. Click 'Export' button and select the filename Once this is done, open the saved database file with Subsurface and the -dives are automatically converted to our own format. Last step to do is save -the log file in Subsurface. +dives are automatically converted to Subsurface’s own format. Last step to +do is save the log file in Subsurface. == ANNEXE D : Exporter un tableur vers le format CSV [[S_Appendix_D]] -De nombreux plongeurs conservent un carnet de plongée sous forme de fichier -numérique, souvent un tableur avec différents champs et informations. Ces -données peuvent facilement être importées dans _Subsurface_ après que le -tableur a été converti en fichier CSV. Cette section explique la procedure -pour convertir un carnet de plongée enregistrée sous forme de tableur vers -un fichier CSV qui pourra ensuite être importé dans _Subsurface_. Créer un -fichier CSV est une tache simple malgré que la procédure soit différente -selon le tableur utilisé. - -La première étape est d'organiser les données de plongées dans le tableur -pour que la première ligne contienne le nom (ou le titre) de chaque colonne -et que les informations de chaque plongée soient contenues sur une seule -ligne. _Subsurface_ supporte de nombreux éléments (Dive #, Date, Time, -Duration, Location, GPS, Max Depth, Mean Depth, Buddy, Notes, Weight et -Tags). L'utilisateur peut organiser les données de plongées selon quelques -règles simples : +Many divers keep a dive log in some form of digital file, commonly a +spreadsheet with various fields of information. These logs can be easily +imported into _Subsurface_ 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 to +_Subsurface_. Creating a .CSV is straightforward, although the procedure is +somewhat different according to which spreadsheet program is used. + +Organize the diving data in the spreadsheet, so 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 number, Date, +Time, Duration, Location, GPS, Max Depth, Mean Depth, Buddy, Notes, Weight +and Tags). Organize dive data following a few simple rules: 1. Date : utiliser un des formats suivants : aaaa-mm-jj, jj.mm.aaaa, mm/jj/aaaa 2. Durée : le format est minutes:secondes. @@ -4384,9 +4279,8 @@ règles simples : entre les unités impériales et métriques) 4. Étiquettes et équipiers : les valeurs doivent être séparées par des virgules. -5. Position GPS : vous devez utiliser les degrés décimaux, par exemple : - 30.22496 30.821798 - +5. Position GPS : utilisez les degrés décimaux, par exemple : 30.22496 + 30.821798 === _LibreOffice Calc_ et _OpenOffice Calc_ These are open source spreadsheet applications forming parts of larger open @@ -4410,21 +4304,21 @@ 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_ImportingCSVDives[Importing CSV dives]. +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_ImportingCSVDives[Importing +CSV dives]. === 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 +Windows machine uses the new character as a separator. You 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. +- In Microsoft Windows, click the *Start* button, 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 @@ -4447,75 +4341,73 @@ 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. +marked _Save as Type:_, select _CSV(Comma delimited) (*.CSV)_. Be sure 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 +that was selected. You can double check the .CSV file by opening it with a +text editor, then import the dive data as explained on the section xref:S_ImportingCSVDives[Importing CSV dives]. - [[S_APPENDIX_E]] == ANNEXE E : Créer un modèle d'impression personnalisé -_Subsurface_ provides a mechanism to create or modify templates for printing -dive logs in order to produce customised printouts of dive logs. Templates, -written in HTML as well as a simple Grantlee instruction set, are rendered -to the print device by _Subsurface_. +_Subsurface_ has a way to create or modify templates for printing dive logs +to produce customized printouts of them. Templates written in HTML, as well +as a simple Grantlee instruction set, are rendered to the print device by +_Subsurface_. Templates are accessed using the print dialogue (see image *B* below). image::images/Print1_f22.jpg["FIGURE: Print dialogue", align="center"] -The buttons under the _Template_ dropdown box allows one to _Edit_, -_Delete_, _Import_ and to _Export_ templates (see image *A* above). New or -modified templates are stored as HTML files in the same directory as the -dive log being processed. In order to create or modify a template, select -one of the templates from the template dropdown list in the print dialogue -(see image *B* above). Choose an existing template that resembles the final -desired printout. Then select _Edit_. +The buttons under the _Template_ dropdown box lets you _Edit_, _Delete_, +_Import_ and _Export_ templates (see image *A* above). New or modified +templates are stored as HTML files in the same directory as the dive log +being processed. In order to create or modify a template, select one of the +templates from the template dropdown list in the print dialogue (see image +*B* above). Choose an existing template that resembles the final desired +printout. Then select _Edit_. -The Edit Panel comprises three tabs: +The Edit Panel has three tabs: image::images/Template1_f22.jpg["FIGURE: template edit dialogue", align="center"] -1) The _Style_ tab (image *A* above) controls the font, line spacing and colour +1) The _Style_ tab (image *A* above) controls the font, line spacing and color template used for printing the dive log. The style attributes are - editable. Choose one of the four colour palets used for colour printing. + editable. Choose one of the four color palettes used for color printing. -2) The _Colors_ tab (image *B* above) allows editing the colours used for - printing the dive log. The colours are highly customisable: the _Edit_ - buttons in the _Colors_ tab allows choosing abritrary colours for different +2) The _Colors_ tab (image *B* above) allows editing the colors used for + printing the dive log. The colors are highly customizable: the _Edit_ + buttons in the _Colors_ tab allows choosing arbitrary colors for different components of the dive log printout. 3) The _Template_ tab of the Edit Panel (see image below) allows creating a template using HTML as well as a few Grantlee programming - primitives. Grantlee provides the ability to create and format HTML code in - a highly simple but efficient way (see below). The HTML of the template can - be edited and saved. The saved template is stored in the same directory as - the dive being processed. By default, a _Custom_ template is a skeleton with - no specific print instructions. The informastion being printed needs to be - specified and formatted in the by replacing the section marked with: "<!-- + primitives. Grantlee can create and format HTML code in a highly simple but + efficient way (see below). The HTML of the template can be edited and + saved. The saved template is stored in the same directory as the dive being + processed. By default, a _Custom_ template is a skeleton with no specific + print instructions. The information printed needs to be specified and + formatted in the template by replacing the section marked with: "<!-- Template must be filled -->". Writing HTML code with Grantlee instructions - allows unlimited freedom in determining what is printed an in which way it + allows unlimited freedom in determining what is printed and in which way it should be rendered. image::images/Template2_f22.jpg["FIGURE:Template tab", align="center"] -One can adapt any of the existing templates and save it to the dive log +You can adapt any of the existing templates and save it to the dive log directory. The standard templates (e.g. One dive, Six dives, Table) can be modified in this way. After completing the edits, use the _Export_ button in the print dialogue to save the new template using a new template name. -To write a custom template the following elements must exist so that the +To write a custom template, the following elements must exist so the template will be correctly handled and rendered. === Main dive loop -_Subsurface_ exports a dive list called (*dives*) to the _Grantlee_ -backend. It is possible to iterate over the list as follows: - +_Subsurface_ exports a dive list called (*dives*) to the _Grantlee_ back +end. It is possible to iterate over the list as follows: .template.html .... {% for dive in dives %} @@ -4530,7 +4422,7 @@ backend. It is possible to iterate over the list as follows: <h1> 3 </h1> .... -Additional information about _Grantlee_ can be found +Additional information about _Grantlee_ can be found at http://www.grantlee.org/apidox/for_themers.html[here] === Grantlee exported variables @@ -4539,20 +4431,31 @@ Only a subset of the dive data is exported: |*Name*|*Description* |number| (*int*) dive number |id| (*int*) unique dive ID, should be used to fetch the dive profile -|date| (*string*) data of the dive +|date| (*string*) date of the dive |time| (*string*) time of the dive |location| (*string*) location of the dive |duration| (*string*) duration of the dive |depth| (*string*) depth of the dive -|divemaster| (*string*) divemaster data -|buddy| (*string*) buddy data -|airTemp| (*string*) air temperature of dive -|waterTemp| (*string*) water temperature of dive +|divemaster| (*string*) dive master for the dive +|buddy| (*string*) buddy for the dive +|airTemp| (*string*) air temperature of the dive +|waterTemp| (*string*) water temperature of the dive |notes| (*string*) dive notes -|rating| (*int*) dive rating ranges from 0 to 5 -|sac| (*string*) sac value -|tags| (*string*) all dive tags concatenate together -|gas| (*string*) used gas cylinder +|rating| (*int*) dive rating which ranges from 0 to 5 +|sac| (*string*) SAC value for the dive +|tags| (*string*) list of dive tags for the dive +|gas| (*string*) list of gases used in the dive +|suit| (*string*) the suit used for the dive +|cylinders| (*string*) complete information of all used cylinders +|cylinder0-7| (*string*) information about a specific cylinder +|weights| (*string*) complete information of all used weight systems +|weight0-5| (*string*) information about a specific weight system +|maxcns| (*string*) maxCNS value for the dive +|otu| (*string*) OTU value for the dive +|sumWeight| (*string*) the summed weight of all used weight systems +|startPressure| (*string*) the start pressure +|endPressure| (*string*) the end pressure +|firstGas| (*string*) first used gas |===================== _Subsurface_ also exports *template_options* data. This data must be used as @@ -4605,16 +4508,15 @@ contains a single member: .... === Defined CSS selectors - -As the dive profile is placed after rendering, _Subsurface_ uses a special -_CSS_ selectors to do some searches in the HTML output. The _CSS_ selectors -in the following table should be added. +As the dive profile is placed after rendering, _Subsurface_ uses special +_CSS_ selectors to searche in the HTML output. The _CSS_ selectors in the +following table should be added. |==================== |*Selector*|*Type*|*Description* |dive_{{ dive.id }} | id | is used to fetch the relevant dive profile -|diveProfile | class | each div that will contain a dive profile should have this class selector in addition to the dive_{{ dive.id }} id selector -|dontbreak | class | prevents the div with this class to be divided into two pages, this can be used +|diveProfile | class | each dive that will contain a dive profile should have this class selector in addition to the dive_{{ dive.id }} id selector +|dontbreak | class | prevents the dive with this class from being divided into two pages. This can be used in flow layout templates only (when data-numberofdives = 0) |===================== @@ -4624,11 +4526,11 @@ data-numberofdives = 0). === Special attributes There are two ways of rendering- either rendering a specific number of dives -in each page or make _Subsurface_ try to fit as much dives as possible into +in each page or make _Subsurface_ try to fit as many dives as possible into one page (_flow_ rendering). The *data-numberofdives* data attribute is added to the body tag to set the -rendering mode +rendering mode. - render 6 dives per page: @@ -4655,7 +4557,7 @@ 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 +it takes the incompressibility of the gas into account. Traditionally, gas consumption and SAC should be: +consumption = tank size x (start pressure - end pressure)+ @@ -4708,20 +4610,18 @@ dive”. === Some dive profiles are missing from the download [[DC_HISTORY]] -'Question': I cannot download all my dives, only the most recent ones even +'Question': I cannot download all my dives, only the most recent ones, even though my dive computer's manual states that it records history of e.g. 999 -dives. - -'Answer': Dive history is different than the dive profiles on the log. The -history only keeps track of the total number of dives and total amount of -time spent below surface. The logs, on the other hand, store the dive -profile, but they have limited amount of memory to do so. The exact amount -of dive profiles that can be stored on the device depend on sample interval -and duration of the dives. Once the memory is full the oldest dives get -overwritten with new dives. Thus we are only able to download the last 13, -30 or 199 dives. +dives? 'Answer': Dive history is different than the dive profiles on the +log. The history only keeps track of the total number of dives and total +amount of time spent below surface. The logs, on the other hand, store the +dive profile, but they have a limited amount of memory to do so. The exact +amount of dive profiles that can be stored on the device depends on sample +interval and duration of the dives. Once the memory is full the oldest dives +get overwritten with new dives. Thus we are only able to download the last +13, 30 or 199 dives. If you have downloaded your dives to different dive logging software before -they were overwritten, there is a high chance that Subsurface can import +they were overwritten, there is a good chance that Subsurface can import these. However, if the logs are only on your dive computer, they cannot be -salvaged after being over written by new dives. +salvaged after being overwritten by new dives. diff --git a/Documentation/user-manual_ru.html.git b/Documentation/user-manual_ru.html.git index 1cda8a63d..402583ecb 100644 --- a/Documentation/user-manual_ru.html.git +++ b/Documentation/user-manual_ru.html.git @@ -1,6192 +1,6192 @@ -<!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="ru">
-<head>
-<meta http-equiv="Content-Type" content="application/xhtml+xml; charset=UTF-8" />
-<meta name="generator" content="AsciiDoc 8.6.9" />
-<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; }
-
-
-@media screen {
- body {
- max-width: 50em; /* approximately 80 characters wide */
- margin-left: 16em;
- }
-
- #toc {
- position: fixed;
- top: 0;
- left: 0;
- bottom: 0;
- width: 13em;
- padding: 0.5em;
- padding-bottom: 1.5em;
- margin: 0;
- overflow: auto;
- border-right: 3px solid #f8f8f8;
- background-color: white;
- }
-
- #toc .toclevel1 {
- margin-top: 0.5em;
- }
-
- #toc .toclevel2 {
- margin-top: 0.25em;
- display: list-item;
- color: #aaaaaa;
- }
-
- #toctitle {
- margin-top: 0.5em;
- }
-}
-</style>
-<script type="text/javascript">
-/*<+'])');
- // 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">Руководство пользователя</span></p></div>
-<div class="paragraph"><p><strong>Авторы документа</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>Версия 4.5, Октябрь 2015</em></span></p></div>
-<div class="paragraph"><p>Вас приветствует <em>Subsurface</em>, современная программа для ведения журнала
-погружений с возможностями организации, документирования, анализа и печати
-погружений для SCUBA и фридайверов. <em>Subsurface</em> предлагает множество
-преимуществ по сравнению с другими решениями:</p></div>
-<div class="ulist"><ul>
-<li>
-<p>
-Вам нужен удобный инструмент для ведения журнала рекреационных погружений
- даже без использования дайв-компьютера?
-</p>
-</li>
-<li>
-<p>
-Вы используете два дайв-компьютера различных производителей, каждый со
- своим программным обеспечением, для загрузки профилей? Вы ныряете с
- ребризером и на открытом цикле? Используете Reefnet Sensus ботом-таймер
- совместно с дайв-компьютером? <em>Subsurface</em> предоставляет общий
- унифицированный интерфейс для загрузки журналов со всех этих устройств,
- хранения и анализа профилей.
-</p>
-</li>
-<li>
-<p>
-Вы используете более одной операционной системы? <em>Subsurface</em> полностью
- совместим с Mac, Linux и Windows, позволяя вам получить доступ к журналу
- на любой операционной системе одинаковым способом.
-</p>
-</li>
-<li>
-<p>
-Вы используете Linux или Mac, а для вашего дайв-компьютер есть программное
- обеспечение только для Windows (например, Mares)? <em>Subsurface</em> дает вам
- возможность работать с профилями погружения на других операционных системах.
-</p>
-</li>
-<li>
-<p>
-Вам нужен интуитивно понятный графический планировщик погружений, который
- принимает во внимание ранее выполненные погружения?
-</p>
-</li>
-<li>
-<p>
-Вам нужно хранить или создавать резервные копии журнала погружения в Интернет, с
- возможностью доступа к журналу откуда угодно, используя веб-броузер?
-</p>
-</li>
-</ul></div>
-<div class="paragraph"><p>Установочные образы <em>Subsurface</em> доступны для Windows PC (Win XP и позже),
-Intel Mac (OS/X) и множества дистрибутивов Linux. <em>Subsurface</em> может быть
-также скомпилирован на множестве других платформ, где доступны Qt и
-libdivecomputer.</p></div>
-<div class="paragraph"><p>Этот документ описывает использование программы <em>Subsurface</em>. Для установки
-обратитесь к странице <em>Downloads</em> на <a href="http://subsurface-divelog.org/">веб-сайте
-<em>Subsurface</em></a>. Вы можете обсудить эту программу, отправив email на адрес
-<a href="mailto:subsurface@subsurface-divelog.org">списка рассылки</a> и сообщить об ошибках на сайте
-<a href="http://trac.hohndel.org">треккера ошибок</a>. Инструкции по самостоятельной сборке
-<em>Subsurface</em> и, если необходимо, зависимостей, описаны в файле INSTALL, распространяемом
-вместе с исходными текстами.</p></div>
-<div class="paragraph"><p><strong>Аудитория</strong>: Рекреационные, технические и коммерческие дайверы, фридайверы</p></div>
-<div id="toc">
- <div id="toctitle">Содержание</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="_работа_с_этим_руководством">1. Работа с этим руководством</h2>
-<div class="sectionbody">
-<div class="paragraph"><p>Если руководство открыто из <em>Subsurface</em>, то вы не увидите никаких элементов
-управления. Однако вам доступны две удобных функции:</p></div>
-<div class="ulist"><ul>
-<li>
-<p>
-<em>ПОИСК</em> активируется нажатием комбинации клавиш control-F или command-F.
- Используйте текстовое поле в нижней части экрана для поиска нужной информации
- в руководстве. Справа от поля поиска кнопки с изображением стрелок вверх и
- вниз позволяют перемещаться по результатам поиска.
-</p>
-</li>
-</ul></div>
-<div class="imageblock" style="text-align:center;">
-<div class="content">
-<img src="images/usermanualfunctions.jpg" alt="Руководство пользователя" />
-</div>
-</div>
-<div class="ulist"><ul>
-<li>
-<p>
-<em>ИСТОРИЯ ПЕРЕХОДОВ</em>. Как и в случае работы с веб-браузером, вы можете
- переходить по ссылкам в руководстве. Контекстное меню (его вы можете вызвать
- правым щелчком мыши) позволяет вам перемещаться по истории переходов вперед и
- назад.
-</p>
-</li>
-</ul></div>
-</div>
-</div>
-<div class="sect1">
-<h2 id="S_UserSurvey">2. Опрос пользователей</h2>
-<div class="sectionbody">
-<div class="paragraph"><p>Для того, чтобы <em>Subsurface</em> удовлетворял всем потребностям наших пользователей,
-нам важно знать о вас. После нескольких дней использования <em>Subsurface</em> предложит
-вам заполнить опросник. Вы сами решаете заполнять ли его и какую информацию вы готовы
-предоставить. Эта информация помогает развивать проект в правильном направлении.
-Если вы отправите анкету или решите отказаться, в обоих случаях <em>Subsurface</em> больше
-не будет надоедать вам. Если в будущем ваши привычки или пожелания изменятся,
-вы можете вызвать опросник, запустив <em>Subsurface</em> с параметром
-командной строки <em>--survey</em>.</p></div>
-</div>
-</div>
-<div class="sect1">
-<h2 id="S_StartUsing">3. Начало работы с программой</h2>
-<div class="sectionbody">
-<div class="paragraph"><p>Окно <em>Subsurface</em> обычно разделено на четыре панели с <strong>Главным меню</strong> (Файл
-Импорт Журнал Вид Помощь) в верхней части окна (Windows и Linux) или в верхней
-части экрана (Mac и Ubuntu Unity). Эти четыре панели:</p></div>
-<div class="olist arabic"><ol class="arabic">
-<li>
-<p>
-<strong>Список погружений</strong> в левой нижней части, в котором отображаются все
-погружения из журнала. Погружение можно выбрать и подсветить нажав на нем
-мышкой. В большинстве случаев между погружениями можно перемещаться клавишами
-вверх/вниз. Список погружений - важный инструмент управления журналом.
-</p>
-</li>
-<li>
-<p>
-<strong>Карта погружений</strong> в правой нижней части. В ней показываются места
-погружений на карте мира. Карта отцентрирована по местоположению последнего
-выбранного погружения в <strong>Списке погружений</strong>
-</p>
-</li>
-<li>
-<p>
-<strong>Информация о погружении</strong> в левой верхней части. Предоставляет наиболее
-полную информацию о дайве, выбранном в <strong>Списке погружений</strong>, включая статистику
-одного или всех выбранных погружений.
-</p>
-</li>
-<li>
-<p>
-<strong>Профиль погружения</strong> в правой верхней части. Показывает графический профиль
-выбранного погружения.
-</p>
-</li>
-</ol></div>
-<div class="paragraph"><p>Разделители панелей можно двигать для того, чтобы изменить их размер.
-<em>Subsurface</em> запоминает положение разделителей так, что при следующем запуске
-программы размер панелей будет таким же, как и в предыдущий раз.</p></div>
-<div class="paragraph"><p>Если в <strong>Списке погружений</strong> выбран дайв, то в соответствующих панелях
-отображается местоположение, подробная информация и профиль этого погружения.
-Если же подсвечено более одного погружения, то последнее подсвеченное
-считается выбранным, но на вкладке <strong>Статистика</strong> информационной панели
-показывается сводная информация _всех подсвеченных_ дайвов (минимальная,
-максимальная и средняя глубина, длительность, температура воды и SAC;
-общее время на дне и количество погружений).</p></div>
-<div class="imageblock" id="S_ViewPanels" style="text-align:center;">
-<div class="content">
-<img src="images/main_window_f22.jpg" alt="Главное окно" />
-</div>
-</div>
-<div class="paragraph"><p>Вы можете выбрать какие из панелей показывать на главном экране. Для этого
-перейдите в пункт меню <strong>Вид</strong> и выберите один из вариантов отображения:</p></div>
-<div class="paragraph"><p><strong>Все</strong>: показываются все четыре панели, как на картинке выше.</p></div>
-<div class="paragraph"><p><strong>Список</strong>: показать только список погружений.</p></div>
-<div class="paragraph"><p><strong>Профиль</strong>: отобразить только профиль выбранного погружения.</p></div>
-<div class="paragraph"><p><strong>Информация</strong>: показать только информацию о выбранном дайве и статистику по
-подсвеченным погружениям.</p></div>
-<div class="paragraph"><p><strong>Карта</strong>: показать карту, отцентрированную по последнему выбранному погружению.</p></div>
-<div class="paragraph"><p>Как и большинство других функций, доступных из главного меню, вид главного
-экрана можно переключать комбинацией клавиш. Эти комбинации указаны рядом с
-соответствующими пунктами меню. В зависимости от операционной системы и
-выбранного языка интерфейса эти комбинации могут различаться, поэтому они не
-перечислены в данном руководстве.</p></div>
-<div class="paragraph"><p>При первом запуске программы главное окно не отображает вообще никакой
-информации. Дело в том, что в этот момент еще нет данных о погружениях. В
-следующих главах будут описаны шаги по созданию нового журнала погружений.</p></div>
-</div>
-</div>
-<div class="sect1">
-<h2 id="S_NewLogbook">4. Создание нового журнала</h2>
-<div class="sectionbody">
-<div class="paragraph"><p>В главном меню выберите <em>Файл → Новый журнал</em>. Все существующие данные
-очищаются чтобы можно было добавлять новую информацию. Если в открытом журнале
-были сделаны изменения, вам будет предложено сохранить данные перед
-созданием нового журнала.</p></div>
-</div>
-</div>
-<div class="sect1">
-<h2 id="S_GetInformation">5. Сохранение погружений в журнале</h2>
-<div class="sectionbody">
-<div class="paragraph"><p>Теперь, когда создан новый журнал, очень просто добавить погружения к нему.
-<em>Subsurface</em> предлагает несколько способов добавления погружений, которые подробно
-описаны далее:</p></div>
-<div class="paragraph"><p>1) Если вы ведете бумажный журнал, храните информацию в электронной таблице или
-используете другой ручной способ, данные о погружениях могут быть добавлены с
-помощью одного из перечисленных вариантов:</p></div>
-<div class="ulist"><ul>
-<li>
-<p>
-Ввод данных о погружении вручную. Это может оказаться полезным, если вы не
- используете дайв-компьютер и погружения были записаны в бумажном журнале. Смотрите:
- <a href="#S_EnterData">Ввод данных о погружении вручную</a>
-</p>
-</li>
-<li>
-<p>
-Импорт данных из журнала, который велся в электронной таблице или в виде CSV-файла.
- Обратитесь к главам <a href="#S_Appendix_D">ПРИЛОЖЕНИЕ Г: Экспорт таблиц в CSV формат</a> и
- <a href="#S_ImportingCSVDives">Импорт погружений в CSV формате</a>.
-</p>
-</li>
-</ul></div>
-<div class="paragraph"><p>2) Если ваши погружения записаны в дайв-компьютере, вы можете получить значительное
- количество информации, включая профиль погружения. Погружения могут быть импортированы
- из:</p></div>
-<div class="ulist"><ul>
-<li>
-<p>
-Непосредственно дайв-компьютера. Смотрите главу <a href="#S_ImportDiveComputer">Импорт данных нового погружения из дайв-компьютера</a> или
-</p>
-</li>
-<li>
-<p>
-Стороннего программного обеспечения, распространяемого производителями дайв-компьютеров.
- Обратитесь к <a href="#S_ImportingAlienDiveLogs">Импорт погружений из других источников и форматов данных</a>.
-</p>
-</li>
-<li>
-<p>
-Импорт из электронных таблиц и CSV-файлов, содержащих профили погружений. Смотрите
- <a href="#S_ImportingCSVDives">Импорт погружений в CSV-формате из дайв-компьютеров и другого ПО для ведения журналов</a>.
-</p>
-</li>
-</ul></div>
-<div class="sect2">
-<h3 id="S_EnterData">5.1. Ввод данных о погружении вручную</h3>
-<div class="paragraph"><p>Этот способ обычно используется для погружений без дайв-компьютера. Основная
-учетная запись в <em>Subsurface</em> - это дайв. В простом журнале погружений обычно
-фиксируется только наиболее важная информация: тип дайва, дата, время,
-длительность, глубина, имена напарников, дайв-мастера или гида, возможно
-некоторые заметки о погружении. <em>Subsurface</em> может хранить гораздо больше
-информации о каждом отдельном дайве. Чтобы добавить новый дайв в журнал
-выберите в главном меню <em>Журнал → Добавить погружение</em>. Программа при этом
-покажет три области, доступных для ввода данных: две вкладки на информационной
-панели (<strong>Примечания</strong> и <strong>Снаряжение</strong>) и панель <strong>Профиль</strong> с графиком погружения.
-Эти области отмечены соответственно как <span class="red">A</span>, <span class="red">B</span> и <span class="red">C</span> на
-картинке ниже. Далее будет пояснено как вводить данные.</p></div>
-<div class="imageblock" style="text-align:center;">
-<div class="content">
-<img src="images/AddDive1_f22.jpg" alt="Рисунок: Добавление погружения" />
-</div>
-</div>
-<div class="paragraph"><p>Когда вы щелкаете мышью в одном из полей указанных панелей, вы переходите в
-режим редактирования. Об этом свидетельствует сообщение на синем фоне в
-верхней части.</p></div>
-<div class="imageblock" style="text-align:center;">
-<div class="content">
-<img src="images/BlueEditBar_f22.jpg" alt="Синяя полоса редактирования" />
-</div>
-</div>
-<div class="paragraph"><p>Не нажимайте на кнопку <em>Применить изменения</em> до тех пор, пока вы не ввели все данные.
-При ручном вводе вам нужно заполнить поля на вкладках <em>Примечания</em>, <em>Снаряжение</em> и
-<em>Профиль</em> перед сохранением. При нажатии кнопки <em>Применить изменения</em>, информация о
-погружении сохраняется в памяти. При закрытии <em>Subsurface</em> вам будет предложено
-сохранить весь журнал на диск.</p></div>
-<div class="sect3">
-<h4 id="S_CreateProfile">5.1.1. Создание профиля погружения</h4>
-<div class="paragraph"><p><strong>Профиль погружения</strong> (графическое представление глубины дайва как функции
-от времени) отображается в правой верхней панели окна <em>Subsurface</em>. В случае
-ручного добавления погружения в журнал, <em>Subsurface</em> предлагает начальный
-профиль дайва, который необходимо изменить, чтобы он соответствовал реальному
-погружению:</p></div>
-<div class="imageblock" style="text-align:center;">
-<div class="content">
-<img src="images/DiveProfile1_f20.jpg" alt="Рисунок: Начальный профиль погружения" />
-</div>
-</div>
-<div class="paragraph"><p><em>Изменение профиля погружения</em>: при перемещении курсора по профилю погружения,
-его положение показывается двумя красными линиями. Глубина
-и время, соответствующие положению курсора, отображаются на координатных осях
-слева и внизу. Единицы измерения (имперская или метрическая система мер)
-берутся из <em>Настроек</em> приложения. Профиль дайва состоит из нескольких
-сегментов, определенных путевыми точками (белые точки, как показано на рисунке
-выше). Глубина по умолчанию составляет 15м. Если погружение было совершено на
-глубину 21м, вам необходимо передвинуть соответствующие точки вниз к нужной
-глубине. Для добавления новой точки, дважды щелкните на линии любого сегмента.
-Чтобы переместить точку, нажмите на нее мышкой и перетаскивайте. Для удаления
-путевой точки, нажмите на ней правой кнопкой мыши и во всплывающем меню
-выберите пункт "Удалить эту точку". Добавляйте и перемещайте точки до тех пор,
-пока профиль не будет соответствовать реальному погружению (глубина и время).
-Ниже приведен пример погружения на 20м в течение 30 минут с последующей
-остановкой безопасности на 5м на 5 минут.</p></div>
-<div class="imageblock" style="text-align:center;">
-<div class="content">
-<img src="images/DiveProfile2_f20.jpg" alt="Рисунок: Отредактированный профиль погружения" />
-</div>
-</div>
-<div class="paragraph"><p><em>Редактирование газовой смеси:</em> Название используемой газовой смеси
-отображается на профиле рядом с каждым сегментом погружения. По умолчанию
-используется первая смесь из списка газов, указанных на вкладке
-<strong>Снаряжение</strong>. В предыдущем примере это воздух. Чтобы изменить газ для отдельно
-взятого сегмента, нажмите правой кнопкой мыши на путевой точке и выберите
-смесь из выпадающего контекстного меню. Изменение газа в путевой точке
-изменяет сегмент <em>слева</em> от этой точки. Обратите также внимание, что в
-контекстном меню доступны только газы, определенные на вкладке <strong>Снаряжение</strong>.</p></div>
-<div class="imageblock" style="text-align:center;">
-<div class="content">
-<img src="images/DiveProfile3_f20.jpg" alt="Рисунок: Меню выбора газовой смеси" />
-</div>
-</div>
-<div class="paragraph"><p>После того, как профиль погружения был задан, необходимо указать дополнительные детали.
-Используйте для этого вкладки <strong>Примечания</strong> и <strong>Снаряжение</strong>, находящиеся в верхней левой
-части окна <em>Subsurface</em>. Перейдите по <a href="#S_Notes_dc">этой ссылке</a> для получения более
-подробной информации.</p></div>
-</div>
-</div>
-<div class="sect2">
-<h3 id="S_ImportDiveComputer">5.2. Импорт новых погружений из дайв-компьютера</h3>
-<div class="sect3">
-<h4 id="_подсоединение_дайв_компьютера_и_импорт_данных">5.2.1. Подсоединение дайв-компьютера и импорт данных</h4>
-<div class="paragraph"><p>Использование дайв-компьютеров позволяет получить большое количество подробной
-информации о погружении, например, точные значения глубин, длительности,
-скорости погружения и всплытия, парциального давления газов. <em>Subsurface</em>
-поддерживает множество моделей дайв-компьютеров,
-<a href="http://subsurface-divelog.org/documentation/supported-dive-computers/">
-актуальный список</a> доступен на веб-сайте.</p></div>
-<div class="admonitionblock">
-<table><tr>
-<td class="icon">
-<img src="images/icons/warning2.png" alt="Внимание" />
-</td>
-<td class="content">Некоторые модели дайв-компьютеров потребляют значительное количество энергии,
-будучи переведенным в режим обмена данными с компьютером. <strong>Это может привести
-к быстрому разряду батареи</strong>. Поэтому мы рекомендуем предварительно проверить
-уровень заряда батареи перед подключением к USB-порту вашего персонального
-компьютера. Так, некоторые модели Suunto и Mares не заряжаются, будучи
-подключенными к ПК. Советуем вам обратиться к руководству по использованию
-вашего дайв-компьютера, чтобы выяснить, заряжается ли его батарея при
-подключении к USB-порту.</td>
-</tr></table>
-</div>
-<div class="paragraph"><p>Для переноса данных из дайв-компьютера в ваш ПК необходимо установить
-соединение между ними. Для этого вам нужно выяснить порт или точку
-монтирования и сообщить эту информацию <em>Subsurface</em>. В
-<a href="#APPENDIX_A">Приложении А</a> приведена техническая информация,
-специфичная для различных операционных систем, а в
-<a href="#APPENDIX_B">Приложении Б</a> для отдельных моделей дайв-компьютеров.</p></div>
-<div class="paragraph"><p>Когда у вас есть необходимая информация, можно подключить дайв-компьютер к ПК,
-выполнив следующие шаги:</p></div>
-<div class="olist arabic"><ol class="arabic">
-<li>
-<p>
-Интерфейсный кабель должен быть подключен к свободному USB-порту
- (подключение через ИК-порт и Bluetooth рассматривается далее)
-</p>
-</li>
-<li>
-<p>
-Дайв-компьютер должен быть переведен в режим передачи данных
- (Обратитесь к руководству пользователя вашего дайв-компьютера)
-</p>
-</li>
-<li>
-<p>
-В главном меню <em>Subsurface</em> выберите <em>Импорт → Импорт из дайв-компьютера</em>.
- Вам будет представлено следующее диалоговое окно <strong>A</strong>:
-</p>
-</li>
-</ol></div>
-<div class="imageblock" style="text-align:center;">
-<div class="content">
-<img src="images/DC_import_f20.jpg" alt="Рисунок: Загрузка из дайв-компьютера 1" />
-</div>
-</div>
-<div class="paragraph"><p>Дайв-компьютеры обычно хранят в своей памяти информацию о нескольких последних
-погружениях, даже не смотря на то, что они уже были загружены в <em>Subsurface</em>.
-По этой причине <em>Subsurface</em> импортирует только те дайвы, которые еще не были
-загружены ранее. Это значительно ускоряет процесс импорта из большинства
-дайв-компьютеров, а также предохраняет батарею от разряда (если конечно ваш
-дайв-компьютер не заряжается, будучи подключенным к USB-порту).</p></div>
-<div class="ulist"><ul>
-<li>
-<p>
-В диалоговом окне присутствуют два выпадающих списка: <strong>Производитель</strong> и
- <strong>Модель</strong>. Сначала выберите производителя, например, Suunto, Oceanic, Uwatec
- или Mares. Затем в списке <strong>Модель</strong> выберите марку вашего дайв-компьютера,
- например, D4 (Suunto), Veo200 (Oceanic) или Puck (Mares).
-</p>
-</li>
-<li>
-<p>
-Поле <strong>Устройство или точка монтирования</strong> содержит список USB или Bluetooth
- портов, необходимых для связи <em>Subsurface</em> с вашим дайв-компьютером. Вы
- должны выбрать порт, соответствующий вашему устройству. Обратитесь к
- <a href="#APPENDIX_A">Приложению А</a> и
- <a href="#APPENDIX_B">Приложению Б</a> для получения технической информации о том,
- как выяснить название порта связи для определенного дайв-компьютера,
- а в некоторых случаях, как настроить операционную систему ПК, на котором
- запущен <em>Subsurface</em>.
-</p>
-</li>
-<li>
-<p>
-Если необходимо загрузить все дайвы, поставьте галочку в поле
- <em>Принудительная загрузка всех погружения</em>. Обычно <em>Subsurface</em> импортирует
- только погружения новее самого последнего в вашем журнале. Эта функция вам
- также может понадобиться, если вы случайно удалили погружения из журнала.
- Некоторые модели дайв-компьютеров (например, Mares Puck) не предоставляют
- список погружения в своей памяти перед импортом, поэтому <em>Subsurface</em> не
- может определить какие из дайвов являются новыми и загружает все погружения
- не зависимо от состояния этого поля.
-</p>
-</li>
-<li>
-<p>
-Если в поле <strong>Предпочтение загруженным</strong> стоит галочка,и во время импорта
- будут существовать погружения с одинаковой датой в журнале и в
- дайв-компьютере, <em>Subsurface</em> перезапишет данные такого дайва данными из
- дайв-компьютера.
-</p>
-</li>
-<li>
-<p>
-Если напротив поля _Загружать в новую поездку" стоит галочка, то после загрузки все
- новые погружения будут сгруппированы в одну поездку в <strong>Списке погружений</strong>
-</p>
-</li>
-<li>
-<p>
-<strong>Не выбирайте</strong> поля <em>Сохранить журнал libdivecomputer</em> и <em>Сохранить
- дамп-файл libdivecomputer</em>. Они используются для диагностики в случае
- возникновения проблем с импортом из дайв-компьютера (см. ниже).
-</p>
-</li>
-<li>
-<p>
-Нажмите кнопку <em>Загрузить</em>. При установленном соединении вы можете наблюдать
- как загружаются данные из дайв-компьютера. В зависимости от модели компьютера
- и количества погружений в памяти последнего, импорт может занять довольно долгое время,
- будьте терпеливы. Бегущая полоса, показывающая процесс загрузки, может не совсем
- точно отражать скорость загрузки, так как зачастую <em>Subsurface</em> не знает
- точно сколько погружений будет загружено до тех пор, пока импорт не завершен.
- После загрузки погружений они отобразятся в в виде таблицы в правой части окна
- (как показано на рисунке <strong>В</strong> выше). Проставьте галочки напротив тех погружений,
- которые должны быть перенесены в <strong>Список погружений</strong> и нажмите кнопку <strong>OK</strong>.
- Окно загрузки будет закрыто, а выбранные погружения появятся в списке.
- После окончания загрузки отключите дайв-компьютер и выключите его
- для экономии заряда батареи.
-</p>
-</li>
-<li>
-<p>
-В случае возникновения проблем связи с дайв-компьютером показывается
- информационное сообщение вида "Невозможно открыть /dev/ttyUSB0 Mares (Puck
- Pro)". Внимательно прочитайте следующую главу.
-</p>
-</li>
-</ul></div>
-<div class="sidebarblock">
-<div class="content">
-<div class="paragraph"><p><strong>Проблемы импорта из дайв-компьютера</strong></p></div>
-<div class="admonitionblock">
-<table><tr>
-<td class="icon">
-<img src="images/icons/important.png" alt="Важно" />
-</td>
-<td class="content">Проверьте следующее:</td>
-</tr></table>
-</div>
-<div class="ulist"><ul>
-<li>
-<p>
-Дайв-компьютер все еще находится в режиме передачи данных?
-</p>
-</li>
-<li>
-<p>
-Полностью ли заряжена батарея дайв-компьютера? Если нет, то следует ее
- зарядить или заменить.
-</p>
-</li>
-<li>
-<p>
-Рабочий ли интерфейсный кабель? Работает ли этот кабель при использовании
- других программ? Работал ли этот кабель ранее или вы используете его в
- первый раз?
-</p>
-</li>
-<li>
-<p>
-Обратитесь к
- <a href="#APPENDIX_A">Приложению А</a> и убедитесь что правильно указано устройство
- или точка монтирования (см. выше).
-</p>
-</li>
-<li>
-<p>
-На Unix-подобных операционных системах убедитесь что у вас есть права на
- открытие порта USB. Если нет, прочитайте
- <a href="#APPENDIX_A">Приложение А</a>.
-</p>
-</li>
-</ul></div>
-<div class="paragraph"><p>Если <em>Subsurface</em> не распознает USB адаптер, не показывая при правильное
-название устройства в поле <em>Устройство или точка монтирования</em>, велика
-вероятность, что кабель нерабочий. Это наиболее часто встречающаяся причина
-ошибок при импорте. Также существует вероятность того, что <em>Subsurface</em> не может
-распознать данные, полученные с дайв-компьютера. В этом случае выполните
-необходимо выполнить диагностическую загрузку, пометив галочками следующие два
-поля:</p></div>
-<div class="literalblock">
-<div class="content">
-<pre><code>Сохранить журнал libdivecomputer
-Сохранить дамп-файл libdivecomputer</code></pre>
-</div></div>
-<div class="paragraph"><p><strong>Важно</strong>: эти поля используются только для диагностики ошибок, возникших при
-импорте данных из дайв-компьютера, в обычной ситуации галочки в этих полях
-должны быть сняты. Когда они выбраны, вам при импорте будет предложено выбрать
-папку для сохранения диагностической информации. По умолчанию используется
-папка, в которой хранится журнал погружений.</p></div>
-<div class="paragraph"><p><strong>Важно</strong>: При импорте в диагностическом режиме, погружения в журнал не
-добавляются. Вместо этого в указанной вами папке будут созданы два файла:</p></div>
-<div class="literalblock">
-<div class="content">
-<pre><code>subsurface.log
-subsurface.bin</code></pre>
-</div></div>
-<div class="paragraph"><p>Эти файлы следует отправить разработчикам в mailto:subsurface@subsurface-divelog.org
-[список рассылки] с просьбой проанализировать проблему. Необходимо указать
-производителя и модель дайв-компьютера и дать словесное описание загружаемых
-погружений.</p></div>
-</div></div>
-</div>
-<div class="sect3">
-<h4 id="S_Bluetooth">5.2.2. Подключение <em>Subsurface</em> к дайв-компьютеру через Bluetooth</h4>
-<div class="paragraph"><p>Bluetooth все чаще встречается в качестве интерфейса для взаимодействия с дайв-компьютерами,
-например Shearwater Petrel Mk2 и OSTC Mk3. <em>Subsurface</em> предоставляет интерфейс взаимодействия
-с Bluetooth, слабо зависящий от операционной системы. Нестройка Bluetooth-соединения в <em>Subsurface</em>
-требует выполнения четырех шагов:</p></div>
-<div class="ulist"><ul>
-<li>
-<p>
-Удостоверьтесь, что Bluetooth активирован на вашем персональном компьютере.
-</p>
-</li>
-<li>
-<p>
-Убедитесь, что <em>Subsurface</em> распознает адаптер Bluetooth на этом компьютере.
-</p>
-</li>
-<li>
-<p>
-Проверьте, что дайв-компьютер переведен в режим связи с ПК и его можно обнаружить через Bluetooth.
-</p>
-</li>
-<li>
-<p>
-Проверьте, чтобы <em>Subsurface</em> был сопряжен с дайв-компьютером.
-</p>
-</li>
-</ul></div>
-<div class="paragraph"><p>Перейдите в окно "Загрузка из дайв-компьютера", выбрав в <strong>Главном меню</strong> <em>Импорт → Импорт из
-дайв-компьютера</em>. Если поставить галочку напротив пункта <em>Загрузка через Bluetooth</em>,
-вам будет представлено следующее окно:</p></div>
-<div class="sect4">
-<h5 id="_linux_или_macos">Linux или MacOS:</h5>
-<div class="imageblock" style="text-align:center;">
-<div class="content">
-<img src="images/DC_import_Bluetooth.jpg" alt="Рисунок: Сопряжение устройств Bluetooth" />
-</div>
-</div>
-<div class="paragraph"><p>На платформах <em>Linux</em> и <em>MacOS</em> в правой части окна показывается название
-компьютера, на котором запущен <em>Subsurface</em>, и его адрес Bluetooth. Если на
-компьютере найдено более одного локального Bluetooth-адаптера, то они будут
-представлены в выпадающем списке и вы можете указать тот, который необходимо
-использовать. Кнопка ниже позволяет включить ии выключить питание локального
-Bluetooth-адаптера.</p></div>
-<div class="paragraph"><p>Если Bluetooth-адрес не указан, это означает, что <em>Subsurface</em> не может распознать локальное
-Bluetooth-устройство. Убедитесь, что на компьютере установлен драйвер адаптера и проверьте, что
-он может использоваться другими программами для работы с Bluetooth (<em>bluetoothctl</em> или <em>bluemoon</em>).
-Эти шаги покрывают первые два из из перечисленных выше.</p></div>
-<div class="paragraph"><p>Проверьте, что дайв-компьютер переведен в режим связи с ПК и его можно обнаружить через Bluetooth.
-Обратитесь к руководству пользователя вашего дайв-компьютера, чтобы сделать это. Это действие
-завершает третий шаг.</p></div>
-<div class="paragraph"><p>Нажмите на кнопку <em>Сканировать</em> в левой нижней части окна. Спустя небольшое
-время поиска, ваш дайв-компьютер должен появиться в списке обнаруженных
-устройств (возможно наряду с другими найденными устройствами) в левой части
-диалогового окна (см. картинку выше). Если компьютер в списке не появился,
-нажмите кнопку <em>Очистить</em> и повторите процедуру сканирования. В итоге
-<em>Subsurface</em> должен обнаружить дайв-компьютер. В списке обнаруженных устройств
-показывается их название, адрес и статус сопряжения. Если устройство не
-сопряжено и подсвечено красным цветом, щелкните на нем правой кнопкой мыши и из
-контекстного меню выберите пункт <em>Сопряжение</em>. Дождитесь окончания этого
-действия. Если сопряжение с этим устройством производится впервые, <em>Subsurface</em>
-может запросить пароль или PIN-код. Наиболее часто используется код 0000 (например,
-это работает с Shearwater Petrel). При необходимости обратитесь к руководству
-пользователя вашего дайв-компьютера.</p></div>
-<div class="sidebarblock">
-<div class="content">
-<div class="admonitionblock">
-<table><tr>
-<td class="icon">
-<img src="images/icons/important.png" alt="Важно" />
-</td>
-<td class="content">В настоящий момент <em>Subsurface</em> не поддерживает сопряжение с дайв-компьютерами, которые требуют
-собственный PIN-код. В этом случае для сопряжения используйте другие утилиты операционной системы
-так, как это предложено ниже.</td>
-</tr></table>
-</div>
-<div class="paragraph"><p>Один и способов сопряжения - использование утилиты <code>bluetoothctl</code>:</p></div>
-<div class="literalblock">
-<div class="content">
-<pre><code>$ bluetoothctl
-[bluetooth]# agent KeyboardOnly
-Agent registered
-[bluetooth]# default-agent
-Default agent request successful
-[bluetooth]# pair 00:80:25:49:6C:E3
-Attempting to pair with 00:80:25:49:6C:E3
-[CHG] Device 00:80:25:49:6C:E3 Connected: yes
-Request PIN code
-[agent] Enter PIN code: 0000</code></pre>
-</div></div>
-</div></div>
-<div class="paragraph"><p>После сопряжения устройств можно нажать на кнопку <em>Сохранить</em>. Окно выбора
-Bluetooth-устройства будет закрыто. Теперь в окне <em>Загрузка из дайв-компьютера</em>
-нажмите кнопку <em>Загрузить</em>. Загруженные погружения будут показаны в списке в
-правой части окна.</p></div>
-</div>
-<div class="sect4">
-<h5 id="_windows">Windows</h5>
-<div class="imageblock" style="text-align:center;">
-<div class="content">
-<img src="images/DC_import_Bluetooth_Windows.png" alt="Рисунок: Сопряжение устройств Bluetooth в Windows" />
-</div>
-</div>
-<div class="paragraph"><p>На платформе <em>Windows</em> детали локального Bluetooth-адаптера не отображаются как в
-случае Mac и Linux.
-Для успешного обнаружения дайв-компьютера убедитесь, что на вашем компьютере
-включен Bluetooth. Используйте кнопку <em>Сканировать</em> для обнаружения устройств.
-Если сопряжение устройства производится впервые, вам возможно придется указать
-PIN-код. Обычно это 0000; при необходимости обратитесь к руководству пользователя
-вашего дайв-компьютера.</p></div>
-<div class="paragraph"><p>Сопряжение устройств происходит автоматически при загрузке погружений. Если до
-этого устройства никогда не были сопряжены, операционная система запросит
-подтверждение и выведет уведомление в правой части экрана: <em>Добавление устройства,
-нажмите чтобы настроить ваш дайв-компьютер</em>. Вам необходимо подтвердить сопряжение.
-Выберите устройство из списка обнаруженных и нажмите кнопку <em>Сохранить</em>. В окне
-<em>Загрузка из дайв-компьютера</em> нажмите кнопку <em>Загрузить</em> и дождитесь окончания процесса.</p></div>
-<div class="admonitionblock">
-<table><tr>
-<td class="icon">
-<img src="images/icons/important.png" alt="Важно" />
-</td>
-<td class="content">Учтите, что в настоящий момент <em>Subsurface</em> работает только с локальными Bluetooth-адаптерами
-и Bluetooth-брелками, использующими стэк Microsoft Bluetooth (например, iSonic).
-Прочие, использующие драйверы <em>Widcomm</em>, <em>Stonestreet One Bluetopia Bluetooth</em> или
-<em>BlueSolei</em>, заведомо работать не будут.</td>
-</tr></table>
-</div>
-<div class="paragraph"><p>Информационное сообщение в левой нижней части окна выбора Bluetooth-устройства
-показывает текущее состояние агента Bluetooth. Для выбора другого устройства,
-вызовите окно выбора Bluetooth-устройства нажатием на кнопку с троеточием
-справа от галочки <em>Загрузка через Bluetooth</em></p></div>
-<div class="admonitionblock">
-<table><tr>
-<td class="icon">
-<img src="images/icons/important.png" alt="Важно" />
-</td>
-<td class="content"><strong>В случае возникновения проблем</strong>: Если локальный Bluetooth-адаптер на компьютере с <em>Subsurface</em>
-"завис" и загрузка погружений постоянно завершается с ошибкой, <em>удалите</em> сопряжение с устройством
-и повторите шаги, перечисленные выше. Если и это не помогло, в
-<a href="#S_HowFindBluetoothDeviceName"><em>Приложении А</em></a> вы сможете найти информацию о том, как вручную
-настроить и проверить соединение с <em>Subsurface</em>.</td>
-</tr></table>
-</div>
-</div>
-</div>
-<div class="sect3">
-<h4 id="S_DeviceNames">5.2.3. Изменение названия дайв-компьютера</h4>
-<div class="paragraph"><p>Может возникнуть ситуация, когда вам будет необходимо каким-то образом
-различать дайв-компьютеры, используемые совместно с <em>Subsurface</em>. Например,
-если у вас с напарником одинаковые дайв-компьютеры и вы их используете для
-импорта данных на одном ПК, то вы возможно захотите назвать один из
-компьютеров как "Suunto D4 Ивана", а другой как "Suunto D4 Петра". Или же
-вы технический дайвер и используете два или более дайв-компьютеров одной
-модели. В этом случае мы можете назвать их "Suunto D4 (1)" и "Suunto D4 (2)".
-<em>Subsurface</em> позволяет вам легко это сделать. В <strong>Главном меню</strong> выберите
-<em>Журнал → Мои дайв-компьютеры</em>. В открывшемся окне вам будет представлен
-список всех компьютеров, использовавшихся для импорта погружений.
-Отредактируйте название соответствующего устройства. После сохранения
-в журнале будет отображаться это название вместо его модели.</p></div>
-</div>
-<div class="sect3">
-<h4 id="S_EditDiveInfo">5.2.4. Редактирование погружения, загруженного из компьютера</h4>
-<div class="paragraph"><p>Информация из дайв-компьютера может быть неполной и вам потребуется ее
-отредактировать. Для этого вам предоставляется две вкладки <strong>Примечания</strong> и
-<strong>Снаряжение</strong> в верхней левой панели <em>Subsurface</em>.</p></div>
-<div class="sect4">
-<h5 id="S_Notes_dc">Примечания</h5>
-<div class="paragraph"><p>Вам возможно придется указать дополнительную информацию, чтобы иметь более полную
-запись о погружении. Нижеописанная процедура одинакова как для погружений, введенных
-вручную, так и для загруженных из дайв-компьютера.</p></div>
-<div class="paragraph"><p>Дата и время погружения, газовая смесь и (обычно) температура присутствуют в
-импортированных дайвах, но вам может понадобиться дополнить
-информацию вручную. Если вы начнете менять какие-то данные на этой вкладке,
-сообщение на голубом фоне в верхней части окна будет уведомлять вас, что
-погружение редактируется.
-На вкладке <strong>Примечания</strong> вам доступны следующие поля
-для редактирования (картинка слева):</p></div>
-<div class="imageblock" style="text-align:center;">
-<div class="content">
-<img src="images/AddDive3_f22.jpg" alt="Рисунок: Вкладка Примечания" />
-</div>
-</div>
-<div class="paragraph"><p>На картинке справа показана заполненная вкладка <strong>Примечания</strong>.
-Поля <strong>Дата</strong> и <strong>Время</strong> соответствуют дате и времени дайва. При нажатии мышкой
-на поле даты отображается выпадающий календарь, в котором можно выбрать
-необходимую дату. Нажмите ESC чтобы закрыть календарь. Значение времени (часы
-и минуты) можно также непосредственно поменять, для чего необходимо нажать
-мышкой в нужном месте текстового поля и ввести цифры.</p></div>
-<div class="paragraph"><p><strong>Температура воды и воздуха</strong> во время дайва. Зачастую дайв-компьютеры
-записывают эту информацию и вам не нужно ее редактировать. Если же вы решите
-их заполнить вручную,единицы измерения заполнять не нужно, они будут автоматически
-подставлены программой (единицы, выбранные в *Настройках* указывают будет ли
-использоваться метрическая или имперская система мер).</p></div>
-<div class="paragraph"><p><strong>Местоположение</strong>:</p></div>
-<div class="admonitionblock">
-<table><tr>
-<td class="icon">
-<img src="images/icons/warning2.png" alt="Внимание" />
-</td>
-<td class="content">Управление дайв-сайтами выполняется отдельно от журнала погружений. Поэтому информация погружения
-на вкладках <strong>Примечания</strong> и <strong>Снаряжение</strong> не может быть отредактирована одновременно с данными
-дайв-сайта. Сохраните прочую информацию (партнеры, дайв-мастер, костюм) нажатием на кнопку
-<strong>Применить изменения</strong>. Только после этого укажите название местоположения в поле <em>Местоположение</em>.</td>
-</tr></table>
-</div>
-<div class="paragraph"><p>Укажите название дайв-сайта, например, «Эль-Мина рэк, Хургада, Египет».
-Если была указана информация для одного дайв-сайта, и у вас есть несколько погружений
-в этом же месте, то эта информация может быть использована без необходимости повторного ввода
-данных. Информация дайв-сайта может быть отредактирована в любой момент. Для этого выберите
-в списке любое погружение, выполнявшееся на этом сайте, и нажмите кнопку с изображением глобуса,
-которая находится справа от поля <strong>Местоположение</strong> (см. картинку справа выше). При вводе названия
-дайв-сайта <em>Subsurface</em> автоматически предложит вам список сайтов с похожими именами. Если сайт
-уже существует, выберите его из списка. Справа от названия сайта в выпадающем списке находится
-картинка либо с изображением глобуса (означает, что в базе данных <em>Subsurface</em> есть погружения
-на этом сайте), либо со значком <strong>+</strong> (сайты с похожим названием, которые еще не были добавлены
-в базу сайтов).</p></div>
-<div class="paragraph"><p>Если сайт ранее не существовал, вы увидите следующее сообщение (рисунок <strong>А</strong> ниже)</p></div>
-<div class="imageblock" style="text-align:center;">
-<div class="content">
-<img src="images/Locations1_f22.jpg" alt="FIGURE:Редактирование дайв-сайта" />
-</div>
-</div>
-<div class="paragraph"><p>Дважды щелкните мышью на наовом дайв-сайте. Вам будет представлена панель, на которой можно ввести
-координаты и прочую информацию о сайте (рисунок <strong>В</strong> выше). Наиболее важными являются географические
-координаты сайта. Их можно указать тремя способами:</p></div>
-<div class="paragraph"><p>а. Выбрать на карте, которая находится в правой нижней части окна
-<em>Subsurface</em>. На карте отображается оранжевая полоса с надписью «Выберите место
-на карте двойным щелчком мыши». При двойном нажатии в соответствующем месте
-карты, оранжевая полоса исчезнет и координаты точки будут заполнены в поле.</p></div>
-<div class="paragraph"><p>б. Координаты могут быть получены с помощью вспомогательного приложения
-<em>Subsurface</em>, если у вас есть устройство Android с GPS-датчиком и координаты
-дайв-сайта были сохранены в этом устройстве. <a href="#S_Companion">Нажмите, чтобы
-узнать больше</a></p></div>
-<div class="paragraph"><p>в. Если вам известны координаты, их можно ввести вручную в одном из четырех
-форматов, сначала широта, потом долгота:</p></div>
-<div class="literalblock">
-<div class="content">
-<pre><code>ISO 6709 Приложение D, например 30°13'28.9"Ю 30°49'1.5"В
-Градусы и десятичные минуты, например, Ю30° 13.49760' , В30° 49.30788'
-Градусы минуты секунды, например, Ю30° 13' 29.8" , В30° 49' 1.5"
-Десятичные градусы, например, 30.22496 , 30.821798</code></pre>
-</div></div>
-<div class="paragraph"><p>Широта южного полушария указывается с буквой <strong>Ю</strong>, например, Ю30°, или со знаком минус,
-например, -30.22496. Аналогично, долгота западного полушария указывается с буквой <strong>З</strong>,
-например, З07°, или со знаком минус, например,-7.34323. На некоторых клавиатурах отсутствует
-символ градусов ((°). Его можно заменить на <strong>d</strong>, например: С30d З20d.
-Если вы указали название дайв-сайта и его координаты, сохраните информацию, нажав на кнопку
-<em>Сохранить изменения</em> в верхней части панели.</p></div>
-<div class="paragraph"><p><strong>Важно</strong> координаты GPS привязаны к названию дайв-сайта, поэтому
-указание координат для погружений, у которых не указано местоположение, может
-привести к непредсказуемым результатам (<em>Subsurface</em> будет предлагать, что все
-эти погружения были в одном месте и имеют одинаковые координаты).</p></div>
-<div class="paragraph"><p><strong>Геопоиск дайв-сайтов:</strong> Если были указаны географические координаты сайта,
-вы можете выполнить автоматический поиск его названия. Для этого <em>Subsurface</em> требуется
-подключение к Интернет. Найденая информация будет отображаться в метках рядом с названием
-дайв-сайта. Список <em>Дайв-сайты с такими же координатами</em> в нижней части панели отображает сайты,
-находящиеся по соседству.</p></div>
-<div class="paragraph"><p>Укажите прочую текстовую информацию о дайв-сайте (Описание и Примечания) и нажмите кнопку
-<em>Применить изменения</em>, чтобы сохранить информацию и сайте. В дальнейшем информация о сайте может
-быть отредактирована нажатием на кнопку с изображением глобуса справа от поля Местоположение на
-вкладке <strong>Примечания</strong>.</p></div>
-<div class="paragraph"><p><strong>Режим погружения</strong>: С помощью выпадающего списка вы можете выбрать режим погружения. Вам
-предоставляются следующие варианты: OC (открытый цикл, значение по умолчанию, подходит для большинства рекреационных дайверов),
-Freedive (погружение без дыхательного аппарата), CCR (ребризер замкнутого цикла) и pSCR (
-пассивный полу-замкнутый ребризер).</p></div>
-<div class="paragraph"><p><strong>Инструктор</strong>: Имя гида или дайв-мастера, с которым производилось это
-погружение. Это поле также производит автодополнение на основании списка всех
-инструкторов в текущем журнале.</p></div>
-<div class="paragraph"><p><strong>Партнер</strong>: Имя buddy или имена партнеров (разделенные запятой), с которыми
-выполнялось данное погружение. Это поле делает автодополнение на основании
-списка всех партнеров в текущем журнале.</p></div>
-<div class="paragraph"><p><strong>Костюм</strong>: Тип костюма в котором осуществлялось погружение. Как и с другими
-полями, для него доступно автодополнение. Если вы ныряете в сухом костюме, то
-можете также указать тип утеплителя и его теплозащиту.</p></div>
-<div class="paragraph"><p><strong>Оценка</strong>: Ваша субъективная оценка этого погружения по 5-ти бальной шкале.
-Укажите рейтинг, нажав на соответствующей звездочке.</p></div>
-<div class="paragraph"><p><strong>Видимость</strong>: Видимость под водой, как и в предыдущем случае, оценивается по
-5-ти бальной шкале.</p></div>
-<div class="paragraph"><p><strong>Метки</strong>: Набор меток (разделенных запятой), описывающих это погружение,
-например: ночное, пещера, течение и т.п. <em>Subsurface</em> предоставляет также
-набор встроенных меток. Автодополнение доступно для этого поля. Например,
-набрав <code>cav</code>, вам предложат на выбор метки <strong>cave</strong> и <strong>cavern</strong>.</p></div>
-<div class="paragraph"><p><strong>Примечания</strong>: В это поле можно ввести любую дополнительную информацию.</p></div>
-<div class="paragraph"><p>Кнопка <strong>Применить изменения</strong> используются для сохранения информации на всех
-вкладках информационной панели и профиля погружения, поэтому нет необходимости
-нажимать ее до тех пор, пока вы не заполнили ВСЮ информацию. Картинка, помещенная
-<a href="#S_Notes_dc">в начале главы</a>, представляет пример полностью заполненной информационной панели.</p></div>
-</div>
-</div>
-<div class="sect3">
-<h4 id="_снаряжение">5.2.5. Снаряжение</h4>
-<div class="paragraph"><p>Вкладка Снаряжение позволяет ввести информацию об используемых баллонах и
-газах, а также грузовых системах. Голубая полоса в верхней части панели с
-сообщением:</p></div>
-<div class="imageblock" style="text-align:center;">
-<div class="content">
-<img src="images/BlueEditBar_f22.jpg" alt="Голубая полоса редактирования" />
-</div>
-</div>
-<div class="paragraph"><p>информирует о том, что в данный момент вы редактируете погружение. Эта часть
-<em>Subsurface</em> очень интерактивная и информация о баллонах и смесях влияет на
-поведение профиля погружения (верхняя правая панель).</p></div>
-<div class="paragraph" id="cylinder_definitions"><p><strong>Баллоны</strong>: Ввод информации о баллонах осуществляется с помощью диалога,
-изображенного на следующей картинке:</p></div>
-<div class="imageblock" style="text-align:center;">
-<div class="content">
-<img src="images/DC_gas-dialogue1_f20.jpg" alt="Рисунок: Начальный вид диалога редактирования баллонов" />
-</div>
-</div>
-<div class="paragraph"><p>В большинстве случаев <em>Subsurface</em> получает информацию о смесях из
-дайв-компьютера и подставляет ее в таблицу. Кнопка + в правом верхнем углу
-позволяет добавить новый баллон к текущему погружению. Темная иконка с
-изображением мусорной корзины удаляет выбранный баллон, однако
-только в том случае, если этот баллон уже не используется в погружении.
-Баллон может неявно использоваться даже в отсутствие событий смены газа.</p></div>
-<div class="paragraph"><p>Начните с выбора типа баллона из выпадающего списка в левой части таблицы. Для
-этого нажмите на ячейке в колонке <strong>Тип</strong>:</p></div>
-<div class="imageblock" style="text-align:center;">
-<div class="content">
-<img src="images/DC_gas-dialogue2_f20.jpg" alt="Рисунок: Список типов баллонов" />
-</div>
-</div>
-<div class="paragraph"><p>Вы можете использовать выпадающий список для выбора типа баллона для
-погружения, а можете начать вводить название типа с помощью клавиатуры. В этом
-случае вам будут предложены совпадающие типы. Поля <strong>Объем</strong> и <strong>Рабочее
-давление</strong> будут заполнены автоматически. Если баллон отсутствует в списке,
-укажите его название и описание в поле <strong>Тип</strong></p></div>
-<div class="paragraph"><p>Далее укажите начальное и конечное давление газа в баллоне. Единицы измерения
-давления (метрическая/имперская система мер) будут взяты из <em>Настроек</em>.</p></div>
-<div class="paragraph"><p>Наконец, укажите состав используемой смеси в поле <strong>O₂%</strong>. Если используется
-воздух, то можно указать значение 21% или вовсе оставить это поле пустым. В
-случае использования Nitrox или Trmix, необходимо указать процентное
-содержание кислорода и гелия в соответствующих полях.
-Прочие ненужные поля следует оставить незаполненными. После ввода всей
-необходимой информации нажмите клавишу <em>ENTER</em> либо щелкните курсором мыши вне
-ячейки, в которой находится курсор. Информация о дополнительных баллонах может
-быть добавлена нажатием на кнопку + в правом верхнем углу. Ниже приведен
-пример погружения с двумя баллонами (воздух и EAN50):</p></div>
-<div class="imageblock" style="text-align:center;">
-<div class="content">
-<img src="images/CylinderDataEntry3_f20.jpg" alt="Рисунок: заполненная таблица баллонов" />
-</div>
-</div>
-<div class="paragraph"><p><strong>Грузы</strong>: Информация о грузовых системах, используемых во время погружения,
-вводится таким же образом, как и информация о баллонах. Если нажать на кнопку
-+ в правом верхнем углу, таблица будет выглядеть приблизительно так:</p></div>
-<div class="imageblock" style="text-align:center;">
-<div class="content">
-<img src="images/WeightsDataEntry1_f20.jpg" alt="Рисунок: Редактирование грузовых систем" />
-</div>
-</div>
-<div class="paragraph"><p>При нажатии мышкой в поле <strong>Тип</strong>, выпадающий список можно вызвать, нажав
-клавишу вниз:</p></div>
-<div class="imageblock" style="text-align:center;">
-<div class="content">
-<img src="images/WeightsDataEntry2_f20.jpg" alt="Рисунок: Список типов грузов" />
-</div>
-</div>
-<div class="paragraph"><p>Вы можете использовать выпадающий список для выбора типа груза, либо начать
-вводить название с помощью клавиатуры. В этом случае вам будут предложены
-совпадающие типы. После выбора типа груза, укажите его вес в поле <strong>Вес</strong>.
-Нажмите клавишу <em>ENTER</em> либо щелкните курсором мыши вне ячейки, в которой
-находится курсор. Если вам нужно добавить дополнительную грузовую систему,
-нажмите на кнопке + в правом верхнем углу. Чтобы удалить груз, нажмите на
-иконку с изображением мусорной корзины.
-Вот пример заполненной таблицы с двумя грузовыми системами: интегрированная и
-пояс:</p></div>
-<div class="imageblock" style="text-align:center;">
-<div class="content">
-<img src="images/WeightsDataEntry3_f20.jpg" alt="Рисунок: Заполненная таблица грузов" />
-</div>
-</div>
-</div>
-<div class="sect3">
-<h4 id="_одновременное_редактирование_нескольких_погружений">5.2.6. Одновременное редактирование нескольких погружений</h4>
-<div class="paragraph"><p><em>СПОСОБ 1</em>: После загрузки данных из дайв-компьютера вы можете видеть профили погружений,
-дату и время, возможно температуру, но многие поля на вкладках <strong>Погружение</strong> и <strong>Снаряжение</strong>
-будут пустыми. И может оказаться очень удобным отредактировать эти поля у нескольких погружений
-одновременно. Например, вы совершили несколько последовательных погружений на одном дайв-сайте,
-в одной и той же конфигурации оборудования и с одним и тем же партнером. Вместо заполнения этой
-информации для каждого дайва, вы можете выбрать несколько погружений в списке и отредактировать
-необходимые поля для всех сразу.</p></div>
-<div class="paragraph"><p>Одновременное редактирование работает только для полей, которые не заполнены. Т.е. если
-у одного погружения среди нескольких выбранных были изменены какие-то поля, они не будут
-изменены при множественном редактировании. Технически правило одновременного редактирования
-звучит так: если редактируемое поле содержит <em>одинаковое</em> значение для всех выделенных
-погружений, только в этом случае новое значение будет сохранено для всех выделенных дайвов.
-В противном случае будет изменено только текущее редактируемое погружение.</p></div>
-<div class="paragraph" id="S_CopyComponents"><p><em>СПОСОБ 2</em>: Существует альтернативный способ выполнить поставленную задачу. Выберите
-подходящее погружение с заполненными полями на вкладках <strong>Погружение</strong> и <strong>Снаряжение</strong>. Затем
-в главном меню выберите <em>Журнал → Копировать параметры погружения</em>. В появившемся окне
-проставьте галочки напротив полей, которые необходимо скопировать и нажмите <em>OK</em>. Теперь
-в списке погружений выберите дайвы, в которые нужно скопировать поля и в главном меню
-выберите <em>Журнал → Вставить параметры погружения</em>.</p></div>
-</div>
-<div class="sect3">
-<h4 id="_добавление_закладок_к_погружению">5.2.7. Добавление закладок к погружению</h4>
-<div class="paragraph"><p>Многие дайверы комментируют свои погружения, добавляя закладки, отмечающие
-какие-то события по время дайва, например: "Встретили дельфинов", "Выпустили
-буй". Это легко сделать в <em>Subsurface</em>:</p></div>
-<div class="ulist"><ul>
-<li>
-<p>
-Нажмите правой кнопкой мыши в нужной точке профиля погружения. В появившемся
-контекстном меню выберите пункт <em>Добавить закладку</em>. На профиле в указанной
-точке времени появится иконка с изображением дайв-флага (рисунок <strong>А</strong> ниже).
-</p>
-</li>
-<li>
-<p>
-Нажмите правой кнопкой мыши на флаге. В появившемся контекстном меню
-(рисунок <strong>В</strong>) выберите <em>Изменить закладку</em>.
-</p>
-</li>
-<li>
-<p>
-В появившемся окне введите название закладки (рисунок <strong>С</strong>) и нажмите <em>ОК</em>
-чтобы сохранить изменения.
-</p>
-</li>
-<li>
-<p>
-При наведении курсора мыши на изображение флага, в нижней части
-информационного окна будет отображаться название закладки (рисунок <strong>D</strong> ниже).
-</p>
-</li>
-</ul></div>
-<div class="imageblock" style="text-align:center;">
-<div class="content">
-<img src="images/Bookmarks.jpg" alt="Рисунок: Добавление закладки" />
-</div>
-</div>
-</div>
-<div class="sect3">
-<h4 id="_сохранение_измененного_погружения">5.2.8. Сохранение измененного погружения</h4>
-<div class="paragraph"><p>Вы можете сохранить информацию со вкладок <strong>Погружение</strong> и <strong>Снаряжение</strong>, нажав
-кнопку <em>Применить изменения</em>. При нажатии кнопки <em>Отменить изменения</em>, введенные вами
-данные будут утеряны, но информация, загруженная из дайв-компьютера, будет сохранена.
-При закрытии <em>Subsurface</em> вам будет предложено сохранить данные журнала.</p></div>
-</div>
-<div class="sect3">
-<h4 id="S_ImportingAlienDiveLogs">5.2.9. Импорт данных из других источников и файлов</h4>
-<div class="paragraph"><p>Если вы ныряете уже достаточно долго, вероятно ваши погружения уже сохранены в
-какой-то другой программе для ведения журнала погружений. Вам не потребуется
-вводить ее заново, потому что с большой долей вероятности <em>Subsurface</em> сможет
-импортировать эти данные. <em>Subsurface</em> поддерживает множество форматов данных.
-Некоторые форматы поддерживаются непосредственно, для других программ может
-понадобиться сделать экспорт в промежуточный формат, для последующего импорта
-в <em>Subsurface</em>.
-В настоящий момент <em>Subsurface</em> поддерживает импорт из CSV-файлов нескольких
-форматов. Для файлов APD LogViewer, XP5 и Sensus подготовлены шаблоны, но вы
-можете создать и свой шаблон импорта.
-Файлы журнала погружений, которые вы ведете вручную (в электронной таблице)
-также могут быть загружены с помощью CSV-импорта.</p></div>
-<div class="paragraph"><p><em>Subsurface</em> также поддерживает импорт файлов с расширением UDDF и UDCF,
-которые используются некоторыми дайв-компьютерами, такими, как Heinrichs &
-Weikamp DR5. Наконец, для некоторых сторонних программ, например, Mares Dive
-Organiser, мы рекомендуем сначала экспортировать журнал в сторонний веб-сервис
-типа <em>divelogs.de</em>, а затем импортировать в <em>Subsurface</em>, так как
-<em>divelogs.de</em> поддерживает еще несколько других форматов, которые <em>Subsurface</em>
-в данный момент не распознает.</p></div>
-<div class="paragraph"><p>Если <em>Subsurface</em> поддерживает формат файла или стороннее программное обеспечение, то для
-импорта такого файла достаточно в главном меню выбрать <em>Файл → Открыть журнал</em> или
-<em>Импорт → Импорт журналов</em>. <em>Subsurface</em> поддерживает импорт с сторонних SQL баз данных
-Suunto Dive Manager и Shearwater. При импорте <em>Subsurface</em> пытается определить
-множественные записи относящиеся к одному погружению и объединить их. Если не
-обнаружено проблем (разница во временной зоне или значительная разница во времени),
-<em>Subsurface</em> не создаст дубликатов погружений.</p></div>
-</div>
-<div class="sect3">
-<h4 id="Unified_import">5.2.10. Использование универсального импорта</h4>
-<div class="paragraph"><p>Импорт погружений из сторонних форматов выполняется с помощью универсального
-диалога, который вы можете вызвать из Главного меню <em>Импорт → Импорт
-журналов</em>. Вам будет представлено диалоговое окно <strong>А</strong>:</p></div>
-<div class="imageblock" style="text-align:center;">
-<div class="content">
-<img src="images/Import1_f20.jpg" alt="Рисунок: Импорт журналов: шаг 1" />
-</div>
-</div>
-<div class="paragraph"><p>В нижней части окна находится выпадающий список типов файлов (как показано на
-рисунке В):</p></div>
-<div class="ulist"><ul>
-<li>
-<p>
-XML-файлы журналов ((Divinglog 5.0, MacDive и другие программы)
-</p>
-</li>
-<li>
-<p>
-Журналы Cochran
-</p>
-</li>
-<li>
-<p>
-UDDF журналы (например, Kenozoooid)
-</p>
-</li>
-<li>
-<p>
-UDCF журналы
-</p>
-</li>
-<li>
-<p>
-Журналы Poseidon MKVI CCR
-</p>
-</li>
-<li>
-<p>
-Журналы APD Inspiration/Evolution CCR
-</p>
-</li>
-<li>
-<p>
-Журналы LiquiVision
-</p>
-</li>
-<li>
-<p>
-Журналы divelog.de
-</p>
-</li>
-<li>
-<p>
-Журналы OSTC Tools
-</p>
-</li>
-<li>
-<p>
-JDiveLog
-</p>
-</li>
-<li>
-<p>
-Suunto Dive Manager (DM3 и DM4)
-</p>
-</li>
-<li>
-<p>
-CSV файлы (текстовые файлы и электронные таблицы), включая журналы APD CCR
-</p>
-</li>
-</ul></div>
-<div class="paragraph"><p>Выберите необходимый файл в списке и погружения будут добавлены в текущий
-журнал. Прочие форматы, которые не поддерживаются <em>Subsurface</em>, можно
-импортировать другим способом, который описан ниже.</p></div>
-</div>
-<div class="sect3">
-<h4 id="_импорт_из_ostc_tools">5.2.11. Импорт из OSTC Tools</h4>
-<div class="paragraph"><p><em>OSTC Tools</em> - набор программ для платформы Microsoft Windows для семейства дайв-компьютеров OSTC.
-, позволяющий загружать и организовывать погружения. <em>OSTC Tools</em> загружает данные погружений из
-дайв-компьютера и сохраняет их в файле с расширением <em>.dive</em>. Эти файлы могут быть загружены в
-<em>Subsurface</em> напрямую, используя диалог универсального импорта. В выпадающем списке в правой нижней
-части окна выберите <em>_Файлы OSTCTools (.dive .DIVE)</em>. Это действие отобразит файлы данного типа
-в панели выбора файлов. Выберите одно или несколько погружений и нажмите кнопку <em>Открыть</em>. Погружения
-будет отображены в <strong>Списке погружений</strong>.</p></div>
-<div class="paragraph"><p>Фактически, все устройства H&W, поддерживаемые OSTCTools, могут быть импортированы в <em>Subsurface</em>.
-Этот список включает в себя OSTC, OSTC Mk2, OSTC 2N/2C, OSTC3, OSTC Sport и, возможно, непроверенные
-Frog, OSTC2 и OSTC CR.</p></div>
-<div class="paragraph"><p>Помните, однако, что OSTCTools <strong>не является</strong> полноценным журналом погружений, а только набором
-инструментов для анализа и управления дайв-компьютерами OSTC. Поэтому только данные непосредственно
-из дайв-компьютера могут быть импортированы в <em>Subsurface</em>; остальную информация (партнеры,
-снаряжение, и т.д.) вам придется внести вручную.</p></div>
-</div>
-<div class="sect3">
-<h4 id="_импорт_из_mares_dive_organiser_v2_1">5.2.12. Импорт из Mares Dive Organiser V2.1</h4>
-<div class="paragraph"><p>Так как Mares использует несвободное программное обеспечение для Microsoft,
-эти журналы не могут быть импортированы в <em>Subsurface</em> напрямую. Вместо этого
-вам придется выполнить процедуру, состоящую из трех шагов, и использовать
-веб-сайт <em>www.divelogs.de</em> для извлечения информации о погружениях.</p></div>
-<div class="olist arabic"><ol class="arabic">
-<li>
-<p>
-Данные журнала необходимо экспортировать на ваш ПК в файл с расширением
-<em>.sdf</em>. Подробнее об этом написано в <a href="#Mares_Export">Приложении В</a>
-</p>
-</li>
-<li>
-<p>
-Выгрузить данные на веб-сайт <em>www.divelogs.de</em>. Вам будет необходимо
-создать учетную запись на сайте и войти под ней. После этого выберите
-<em>Import Logbook → Mares Dive Organizer</em>. Внимательно следуйте инструкциям
-и выгрузите файл с расширением <em>.sdf</em> в на сайт.
-</p>
-</li>
-<li>
-<p>
-Наконец, импортируйте журнал с веб-сайта <em>divelogs.de</em> в <em>Subsurface</em>
-используя следующие инструкции.
-</p>
-</li>
-</ol></div>
-</div>
-<div class="sect3">
-<h4 id="S_ImportingDivelogsDe">5.2.13. Импорт с веб-сайта <strong>divelogs.de</strong></h4>
-<div class="paragraph"><p>Импорт журнала с сайта <em>divelogs.de</em> очень простой и использует одно
-диалоговое окно. Для начала в Главном меню выберите <em>Импорт → Импорт с сайта
-divelogs.de). В появившемся окне (рисунок <strong>А</strong> слева ниже) введите свои имя
-пользователя и пароль для сайта _divelogs.de</em> и нажмите кнопку <em>Загрузить</em>.
-После нажатия кнопки в окне будет отображаться прогресс импорта, а в случае
-успешного окончания будет показано уведомление (рисунок <strong>В</strong> справа ниже). Вам
-необходимо нажать кнопку <em>Применить</em>, чтобы загруженные погружения появились в
-<strong>Списке погружений</strong>.</p></div>
-<div class="imageblock" style="text-align:center;">
-<div class="content">
-<img src="images/Divelogs1.jpg" alt="Рисунок:Импорт с сайта Divelogs.de" />
-</div>
-</div>
-</div>
-<div class="sect3">
-<h4 id="S_ImportingCSVData">5.2.14. Импорт погружений в формате CSV</h4>
-<div class="paragraph"><p>Файл со значениями, разделенными запятой (.csv) может использоваться как для импорта
-профиля погружения (в случае ребризеров замкнутого цикла APD Inspiration и Evolution), так
-и для загрузки общей информации о дайвах (если вы вели учет в электронной таблице). CSV
-является универсальным и простым форматом для обмена данными между компьютерам и программами.
-Более подробно об этом формате рассказывается в главе <a href="#S_CSV_Intro">Формат CSV для дайверов</a>.
-<em>Subsurface</em> позволяет также выгружать журнал погружений для дальнейшей загрузки в другие программы.
-Обратитесь к главе <a href="#S_Appendix_D">ПРИЛОЖЕНИЕ Г: Экспорт электронных таблиц в формат CSV</a>
-за информацией по загрузке данных из электронных таблиц в <em>Subsurface</em>.</p></div>
-</div>
-<div class="sect3">
-<h4 id="S_ImportingCSVDives">5.2.15. Импорт погружений в CSV-формате из дайв-компьютеров и других программ</h4>
-<div class="paragraph"><p>Для просмотре и редактирования CSV-файлов подойдет обычный текстовый редактор.
-Данные в CSV-файле обычно организованы следующим образом: одна строка
-заголовка и затем строки данных, по одной на каждую запись.</p></div>
-<div class="paragraph"><p>В <em>Subsurface</em> может быть импортировано два вида CSV-файлов:</p></div>
-<div class="olist arabic"><ol class="arabic">
-<li>
-<p>
-<em>Общая информация о погружении</em>: в этом случае файл содержит обычную для журнала информацию,
- например, дату и время, глубину, длительность, имена партнеров и дайв-мастера, возможно
- данные об баллонах и давлении до и после погружения, примечания. Все данные для одного
- погружения хранятся в одной строке, а порядке определенном в заголовке.
-</p>
-</li>
-<li>
-<p>
-<em>Профиль погружения</em>: журнал этого вида содержит гораздо больше информации об отдельно
- взятом погружении. Например, он может включать данные с 30-ти секундным интервалом о
- времени, глубине, температуре и давлении в баллоне в конкретный момент времени. Каждая строчка
- в таком файле является выборкой параметров погружения в определенный момент. Для описание профиля
- одного погружения необходимо много информации. Этот формат зачастую используется ребризерами
- закрытого цикла и многочисленными программами для работы с дайв-компьютерами и ведения журналов.
-</p>
-</li>
-</ol></div>
-<div class="paragraph"><p>Перед импортом CSV-файла в <em>Subsurface</em> вам <strong>необходимо выяснить некоторые свойства этого
-файла</strong>:</p></div>
-<div class="paragraph"><p>а. Какой символ служит разделителем колонок в одной строке данных? Этот символ должен быть
- запятой (,) или табуляцией? Вы можете определить это, открыв файл в текстовом редакторе.
- Если разделителем служит запятая, то она хорошо заметна между полями данных в строке. Если
- запятых не и числа выровнены в колонки, то с большей долей вероятности можно утверждать, что
- разделителем служит символ табуляции.</p></div>
-<div class="paragraph"><p>б. Данные из каких колонок должны быть импортированы в <em>Subsurface</em>? Содержит файл <em>Общую
- информацию</em> или <em>Профиль погружения</em>? Откройте файл, использую текстовый редактор, и
- отметьте для себя название колонок в заголовке и их позиционный номер.</p></div>
-<div class="paragraph"><p>в. В какой системе мер (имперской или метрической_ записаны данные (например, глубина)?</p></div>
-<div class="paragraph"><p>Вооружившись этой информацией, импорт данных в <em>Subsurface</em> не будет для вас проблемой.
-В Главном меню выберите <em>Импорт → Импорт журналов</em>. В окне выбора файлов выберите тип
-<em>CSV файлы</em> (в правом нижнем углу). Вам будет представлен список CSV-файлов в текущей
-директории. Выберите файл, который необходимо импортировать, после чего вы увидите окно
-конфигурации импорта:</p></div>
-<div class="imageblock" style="text-align:center;">
-<div class="content">
-<img src="images/csv_import1_f20.jpg" alt="Рисунок: Диалог 1 импорт CSV" />
-</div>
-</div>
-<div class="paragraph"><p>Обратите внимание на выпадающий список в левом верхнем углу. Он содержит настройки для
-часто встречающихся дайв-компьютеров и программ. Если ваш CSV-файл есть в этом списке,
-используйте его. В противном случае следует выбрать <em>Импорт вручную</em>. В окне конфигурации
-также есть выпадающие список для указания символа-разделителя, формата даты и длительности
-погружения, а также используемой системы мер. Для успешного импорта очень важно задать
-правильные значения в этих списках.</p></div>
-<div class="paragraph"><p>На последнем шаге вы должны сопоставить поля данных в файле их названиям. Первая белая
-строка таблицы данных содержит заголовки, найденные в CSV-файле. Голубая строка таблицы,
-находящаяся непосредственно на ней, содержит названия <em>Subsurface</em>. В белой области,
-находящейся сразу под выпадающими списками, представлены поля-метки, которые могут быть
-импортированы в <em>Subsurface</em>. Эти метки, заключенные в овалы голубого цвета, необходимо
-с помощью мыши перетащить на голубую полосу таблицы в соответствующую колонку.
-Например, для того, чтобы импортировать номер погружения ("Dive # " в английской версии,
-"№" в русской) <em>Subsurface</em>, перетащите метку "№" в ячейку над заголовком " # ", как показано
-на рисунке ниже:</p></div>
-<div class="imageblock" style="text-align:center;">
-<div class="content">
-<img src="images/csv_import2_f20.jpg" alt="Рисунок: Диалог 2 импорт CSV" />
-</div>
-</div>
-<div class="paragraph"><p>Продолжайте до тех пор, пока не сопоставите всем заголовкам соответствующие метки. После
-этого нажмите клавишу _ОК в нижней части окна. Данные будут импортированы и погружения
-будут отображены в панели <strong>Список погружений</strong>.</p></div>
-<div class="sidebarblock" id="S_CSV_Intro">
-<div class="content">
-<div class="paragraph"><p><strong>Формат CSV для дайверов</strong></p></div>
-<div class="admonitionblock">
-<table><tr>
-<td class="icon">
-<img src="images/icons/important.png" alt="Важно" />
-</td>
-<td class="content">Аббревиатура <em>CSV</em> происходит от английского <em>Comma-Separated Values</em>, что означает
-<em>значения, разделенные запятой</em>. Файлы этого формата можно отредактировать с помощь текстового
-редактора, например Notepad (Windows), gedit (Linux) или TextWrangler(OS/X). Преимущества
-этого формата заключаются в том, что а) для его редактирования не нужно никакого специализированного
-программного обеспечения, и б) в нем нет ничего лишнего и он может легко быть
-отредактирован человеком.
-Благодаря своей простоте, CSV-формат широко используется для обмена данными между различными
-программами, например между электронными таблицами, базами данных и программами для дайвинга.
-В <em>Subsurface</em> этот формат используется для импорта из других источников, таких как электронные
-таблицы, и даже некоторых дайв-компьютеров.</td>
-</tr></table>
-</div>
-<div class="paragraph"><p><em>CSV</em> файлы могут быть созданы и отредактированы с помощью обычного текстового редактора.
-Самым важным атрибутом таких файлов является символ, разделяющий поля в одной строке данных.
-Чаще всего таким символом является запятая, точка с запятой или табуляция. При экспорте из
-электронной таблицы вам необходимо указать какой символ-разделитель использовать. CSV-файлы
-обычно организованы следующим образом: в первой строке указаны заголовки (или <em>имена полей</em>),
-а в последующих строках находятся данные, по одной строке на запись. Обратите внимание, что название
-поля может состоять из нескольких слов, разделенных пробелами; "Дата дайва". Ниже приведен пример файла для четырех погружений
-с использованием запятой в качестве символа-разделителя:</p></div>
-<div class="literalblock">
-<div class="content">
-<pre><code>Место,Дата дайва,Время_дайва,Длительность, Глубина,Напарник
-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>В таком виде его не так просто прочитать человеку. Вот эти же данные с использованием символа табуляции:</p></div>
-<div class="literalblock">
-<div class="content">
-<pre><code>Место Дата дайва Время_дайва Длительность Глубина Напарник
-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>Понятно, почему большинство людей предпочитает использовать табуляцию как разделитель.
-Недостаток же в том, что мы не можете отличить табуляцию от пробела, как в заголовке <em>Дата дайва</em>
-(на самом деле между словами стоит пробел, а табуляция находится после заголовка).
-Также при слишком длинных названиях не всегда удается достичь выравнивания. Ниже приведен
-урезанный пример профиля погружения с ребризера замкнутого цикла APD, в котором используется
-табуляция в качестве разделителя:</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>При импорте <em>CSV</em> файлов <em>Subsurface</em> показывает не только заголовки, но и несколько первых
-строк данных, что значительно упрощает работу. Обладая базовыми знаниями о формате <em>CSV</em>,
-вы сможете без проблем импортировать свои данные в <em>Subsurface</em>.</p></div>
-</div></div>
-<div class="admonitionblock">
-<table><tr>
-<td class="icon">
-<img src="images/icons/important.png" alt="Важно" />
-</td>
-<td class="content">При импорте <em>CSV</em> есть несколько предостережений. Избегайте использования некоторых специальных
-символов, таких амперсанд (&), меньше (<), больше (>) и двойной кавычки (") в значениях ячеек.
-Файл должен быть сохранен в кодировке UTF-8, если вы используете символы отличные от латинских.
-Размер файла также может быть причиной определенных проблем. Импорт 100 погружений за раз
-(<em>Общая информация о погружениях_) вряд ли будет проблемой, но файлы большего размера могут.
-При возникновении проблем с _Импортом CSV</em> попробуйте для начала уменьшить размер файла.</td>
-</tr></table>
-</div>
-</div>
-</div>
-<div class="sect2">
-<h3 id="S_Companion">5.3. Импорт GPS координат из <em>вспомогательного приложения Subsurface</em> для мобильных телефонов</h3>
-<div class="paragraph"><p>Используя <strong>вспомогательное приложение Subsurface</strong> на устройствах Android с GPS
-датчиком или <a href="#S_iphone"><em>iPhone</em></a>, координаты дайв-сайтов могут быть автоматически
-переданы в журнал <em>Subsurface</em>. Вспомогательное приложение сохраняет координаты на
-выделенном сервере в Интернет. <em>Subsurface</em> в свою очередь умеет подгружать координаты
-погружений с этого сервера.</p></div>
-<div class="paragraph"><p>Чтобы воспользоваться этой функцией, вам необходимо:</p></div>
-<div class="sect3">
-<h4 id="_создать_учетную_запись_для_вспомогательного_приложения">5.3.1. Создать учетную запись для вспомогательного приложения</h4>
-<div class="ulist"><ul>
-<li>
-<p>
-Зарегистрируйтесь на <a href="http://api.hohndel.org/login/">странице вспомогательного
- приложения</a>. Вам будет прислано письмо-подтверждение с вашим персональным
- <strong>КЛЮЧОМ</strong>. Этот ключ используется для авторизации на сервере и работы приложения.
-</p>
-</li>
-<li>
-<p>
-Загрузите вспомогательное приложение с сайта
- <a href="https://play.google.com/store/apps/details?id=org.subsurface">Google Play
- Store</a> или с сайта
- <a href="http://f-droid.org/repository/browse/?fdfilter=subsurface&fdid=org.subsurface">F-Droid</a>.
-</p>
-</li>
-</ul></div>
-</div>
-<div class="sect3">
-<h4 id="_использование_приложения_на_android_смартфоне">5.3.2. Использование приложения на Android-смартфоне</h4>
-<div class="paragraph"><p>При первом запуске приложения у вас есть три возможности:</p></div>
-<div class="ulist"><ul>
-<li>
-<p>
-<em>Создать учетную запись.</em> Это эквивалентно созданию учетной записи с помощью
- интернет-броузера. Вы можете запросить <strong>КЛЮЧ</strong>, который будет прислан на вашу
- электронную почту, но затем вам будет нужно активировать учетную запись на
- <a href="http://api.hohndel.org/login/">странице вспомогательного приложения</a>.
-</p>
-</li>
-<li>
-<p>
-<em>Получить учетную запись.</em> С помощью этого варианта вы можете восстановить
- забытый ключ.
-</p>
-</li>
-<li>
-<p>
-<em>Использовать учетную запись</em>. Вам нужно ввести ваш персональный ключ.
- Приложение сохранит ключ и больше не будет его запрашивать, если только вы
- не выберите в меню пункт <em>Отключиться</em>.
-</p>
-</li>
-</ul></div>
-<div class="admonitionblock">
-<table><tr>
-<td class="icon">
-<img src="images/icons/important.png" alt="Важно" />
-</td>
-<td class="content">В программе <em>Subsurface</em> нужно также ввести ваш персональный <strong>КЛЮЧ</strong> в
-настройках приложения. Для этого выберите в меню <em>Файл → Настройки</em> и на
-вкладке <em>Общие</em> введите <strong>КЛЮЧ</strong> в поле <em>ID пользователя</em> веб-сервиса
-<em>Subsurface</em>. Это обеспечит синхронизацию между приложениями.</td>
-</tr></table>
-</div>
-<div class="sect4">
-<h5 id="_создание_нового_места_погружения">Создание нового места погружения</h5>
-<div class="paragraph"><p>Теперь вы готовы получить координаты места погружения и отправить их на
-сервер. Экран смартфона выглядит как на левой картинке (<strong>А</strong>) ниже, но без
-погружений.</p></div>
-<div class="paragraph"><p>Нажмите на значок со знаком "+" в правом верхнем углу, чтобы добавить новый
-дайв-сайт. Отобразится выпадающее меню с тремя вариантами:</p></div>
-<div class="ulist"><ul>
-<li>
-<p>
-Текущее положение: вам будет предложено ввести название места (и возможно
- потребуется включить GPS, если он был выключен), после чего текущее
- положение будет сохранено.
-</p>
-</li>
-<li>
-<p>
-Выбрать на карте: этот вариант позволяет выбрать интересующее вас
- местоположение на карте (см. рисунок <strong>В</strong>). Выбор точки осуществляется долгим
- нажатием на сенсорном экране. Если место выбрано неправильно, выберите
- другое, после чего нажмите на галочку в правом верхнем углу экрана. Укажите
- название точки и дату и время погружения (рисунок <strong>С</strong>). Для корректного
- импорта местоположения в <em>Subsurface</em> мы рекомендуем, чтобы время совпадало
- со временем дайва.
-</p>
-</li>
-</ul></div>
-<div class="imageblock" style="text-align:center;">
-<div class="content">
-<img src="images/Companion_5.jpg" alt="Рисунок: Добавление погружения" />
-</div>
-</div>
-<div class="ulist"><ul>
-<li>
-<p>
-Импорт GPX-файла: Ваше Android-устройство просканирует карту памяти и
- покажет найденные GPX-файлы. Нажмите на выбранном файле, выберите
- необходимые точки погружений и нажмите на галочку в правом верхнем углу
- экрана. После этого выбранные места погружений будут отправлены на сервер в
- Интернете и добавлены к списку дайвов в вашем смартфоне.
-</p>
-</li>
-</ul></div>
-</div>
-</div>
-<div class="sect3">
-<h4 id="_список_мест_погружений">5.3.3. Список мест погружений</h4>
-<div class="paragraph"><p>На главном экране приложения отображается список мест погружений с
-названиями, датой и временем. Слева от названия над полем выбора может
-показываться значок с изображением стрелки, указывающей вверх, означающий, что
-этот дайв ожидает отправки на сервер. Вы можете выбрать одно или несколько
-погружений, проставив галочки в поле рядом с названием. Групповые операции
-(<em>Отправить</em> и <em>Удалить</em>) применяются к выбранным погружениям.</p></div>
-<div class="paragraph"><p>Погружения можно просматривать двумя способами: текстовый список и карта.
-Режим отображения переключается нажатием на на текстовом поле <em>Погружения</em> в
-левой верхней части экрана (см. рисунок <strong>А</strong> ниже). Находясь в режиме карты, вы
-также можете нажать на текстовом поле <em>Карта</em> в левом верхнем углу (рисунок
-<strong>В</strong>) и выбрать другой режим. При выборе погружения на карте или в списке, вам
-будет представлен экран редактирования места дайва (рисунок <strong>С</strong>), на котором
-вы можете поменять название точки и прочие детали.</p></div>
-<div class="imageblock" style="text-align:center;">
-<div class="content">
-<img src="images/Companion_4.jpg" alt="Рисунок: Просмотр и редактирование мест погружений" />
-</div>
-</div>
-<div class="paragraph"><p>На экране редактирование вам доступно два инструмента (в правом верхнем углу
-экрана):</p></div>
-<div class="ulist"><ul>
-<li>
-<p>
-Редактировать (карандаш): для изменения названия и прочих параметров
-</p>
-</li>
-<li>
-<p>
-Карта: отобразить положение дайва на карте
-</p>
-</li>
-</ul></div>
-<div class="paragraph"><p>После редактирования и сохранения (рисунок <strong>С</strong>) вам необходимо отправить
-погружение на сервер, как объясняется ниже.</p></div>
-</div>
-<div class="sect3">
-<h4 id="_отправка_погружения_на_сервер">5.3.4. Отправка погружения на сервер</h4>
-<div class="paragraph"><p>Существует несколько способов выгрузки координат на сервер. Самый простой - отметить
-погружения в списке (см. рисунок <strong>A</strong> ниже) и нажать на кнопку с изображением стрелки в
-правом верхнем углу экрана.</p></div>
-<div class="admonitionblock">
-<table><tr>
-<td class="icon">
-<img src="images/icons/important.png" alt="Важно" />
-</td>
-<td class="content">Будьте внимательны: находящаяся рядом кнопка с изображением мусорной корзины
-удаляет точки погружений.</td>
-</tr></table>
-</div>
-<div class="imageblock" style="text-align:center;">
-<div class="content">
-<img src="images/Companion_1.jpg" alt="Рисунок: Вспомогательное приложение Subsurface" />
-</div>
-</div>
-<div class="paragraph"><p>После вашей поездки с использованием вспомогательного приложения,
-все погружения могут быть загружены в <em>Subsurface</em> (см. ниже).</p></div>
-<div class="sect4">
-<h5 id="_дополнительные_функции_вспомогательного_приложения">Дополнительные функции вспомогательного приложения</h5>
-<div class="paragraph"><p>В зависимости от размера экрана вашего Android-устройства дополнительные
-возможности приложения доступны вам только после нажатия кнопки <em>Меню</em>.
-Вам будет предложено на выбор 5 пунктов (рисунок <strong>В</strong> выше):</p></div>
-</div>
-<div class="sect4">
-<h5 id="_поиск">Поиск</h5>
-<div class="paragraph"><p>Позволяет вам найти места погружений по названию и указанном временном
-интервале.</p></div>
-</div>
-<div class="sect4">
-<h5 id="_запуск_фоновой_службы">Запуск фоновой службы</h5>
-<div class="paragraph"><p>Вместо ручного ввода мест погружений, вы можете запустить фоновую службы
-записи координат, которая автоматически будет сохранять места ваших дайвов.</p></div>
-<div class="paragraph"><p>Следующие <em>Настройки</em> (см. ниже) влияют на работу этой службы:</p></div>
-<div class="ulist"><ul>
-<li>
-<p>
-<em>Минимальный интервал</em> в минутах. Приложение будет пытаться определить и
- записать координаты местоположения каждые Х минут.
-</p>
-</li>
-<li>
-<p>
-<em>Минимальное расстояние</em> в метрах. Минимальное расстояние в метрах между
- двумя последовательными точками фиксации координат.
-</p>
-</li>
-<li>
-<p>
-<em>Шаблон названия</em>. Название автоматически создаваемых точек погружения.
-</p>
-</li>
-</ul></div>
-<div class="admonitionblock">
-<table><tr>
-<td class="icon">
-<img src="images/icons/info.jpg" alt="Подсказка" />
-</td>
-<td class="content"><em>Как работает фоновая служба?</em> Предположим вы установили временной интервал в
-5мин и минимальное расстояние равное 50 метрам. Приложение будет записывать
-координаты каждые 5 минут <strong>или</strong> если вы переместитесь более чем на 50 метров
-от предыдущей точки. Если же новая точка находится в радиусе 50м от
-предыдущей, то она не будет сохранена. Если вы не двигаетесь, то будут
-сохранены только координаты первой точки.</td>
-</tr></table>
-</div>
-</div>
-<div class="sect4">
-<h5 id="_отправить_все_местоположения">Отправить все местоположения</h5>
-<div class="paragraph"><p>Отправляет на сервер все местоположения, которые не были выгружены ранее.</p></div>
-</div>
-<div class="sect4">
-<h5 id="_отключиться">Отключиться</h5>
-<div class="paragraph"><p>Не самое удачное название. Эта функция удаляет сохраненные <strong>КЛЮЧ</strong>, который вы
-вводили при первом старте. Может пригодиться в том случае, если другой дайвер
-пользовался вашим смартфоном для записи координат погружений.</p></div>
-</div>
-<div class="sect4">
-<h5 id="_настройки">Настройки</h5>
-<div class="paragraph"><p>В _Настройках_ приложения вам доступны следующие параметры:</p></div>
-</div>
-<div class="sect4">
-<h5 id="_сервер_и_учетная_запись">Сервер и учетная запись</h5>
-<div class="ulist"><ul>
-<li>
-<p>
-<em>URL веб-сервиса</em>. По умолчанию используется <a href="http://api.hohndel.org/">http://api.hohndel.org/</a>
-</p>
-</li>
-<li>
-<p>
-<em>ID пользователя</em>. Ваш персональный ключ, полученный по email после
- регистрации на сайте. Вы можете скопировать его из письма и вставить сюда,
- либо ввести вручную.
-</p>
-</li>
-</ul></div>
-</div>
-<div class="sect4">
-<h5 id="_синхронизация">Синхронизация</h5>
-<div class="ulist"><ul>
-<li>
-<p>
-<em>Синхронизация при старте</em>. Если выбран этот параметр, при каждом старте приложения погружения
-на вашем Android-устройстве и веб-сервисе будут синхронизироваться.
-</p>
-</li>
-<li>
-<p>
-<em>Отправлять новые</em>. Если этот параметр установлен, добавленные точки будут
- автоматически отправляться на сервер.
-</p>
-</li>
-</ul></div>
-</div>
-<div class="sect4">
-<h5 id="_фоновая_служба">Фоновая служба</h5>
-<div class="paragraph"><p>Параметры фоновой службы уже были описаны выше.</p></div>
-</div>
-<div class="sect4">
-<h5 id="_разное">Разное</h5>
-<div class="ulist"><ul>
-<li>
-<p>
-<em>Список рассылки</em>. Отсюда вы можете отправить письмо разработчикам
- <em>Subsurface</em>.
-</p>
-</li>
-<li>
-<p>
-<em>Веб-сайт</em>. Ссылка на веб-сайт <em>Subsurface</em>.
-</p>
-</li>
-<li>
-<p>
-<em>Версия</em>. Текущая версия вспомогательного приложения.
-</p>
-</li>
-</ul></div>
-</div>
-</div>
-<div class="sect3">
-<h4 id="S_iphone">5.3.5. Запись координат погружений из <em>вспомогательного приложения Subsurface</em> для <em>iPhone</em></h4>
-<div class="paragraph"><p>Интерфейс приложения для iPhone крайне прост. Необходимо ввести ключ, полученный при
-регистрации, в соответствующее поле, затем нажать "Dive in" (см. левую картинку на рисунке
-ниже), после чего можно приступать к сбору информации о местоположении погружений.</p></div>
-<div class="imageblock" style="text-align:center;">
-<div class="content">
-<img src="images/iphone.jpg" alt="Рисунок: Использование вспомогательного приложения на iPhone" width="640" />
-</div>
-</div>
-<div class="paragraph"><p>Погружения могут быть добавлены автоматически или вручную. В ручном режиме, служба получения
-координат запускается автоматически, а в нижней части экрана появляется красная полоса. После
-завершения погружения вам нужно нажать на красной области, чтобы остановить службу
-позиционирования. При запущенной службе позиционирования вы можете добавлять погружения
-только в ручном режиме.</p></div>
-<div class="paragraph"><p>Позже вы можете отредактировать название места погружения, выбрав и нажав на него в списке.
-Другие поля для редактирования недоступны. Список дайвов автоматически выгружается на сервер,
-возможно вручную синхронизировать погружения отсутствует.</p></div>
-</div>
-<div class="sect3">
-<h4 id="_загрузка_координат_погружений_в_журнал_em_subsurface_em">5.3.6. Загрузка координат погружений в журнал <em>Subsurface</em></h4>
-<div class="paragraph"><p>Перед получением GPS-координат с сервера, погружения должны быть загружены в
-журнал из дайв-компьютера или введены вручную. Для загрузки координат выберите
-в главном меню <em>Импорт → Импорт координат</em> или нажмите комбинацию клавиш
-Ctrl-G. Вам будет представлено окно, как показано на рисунке <strong>А</strong> ниже. При
-первом импорте необходимо указать ключ, после чего нажмите кнопку <em>Загрузить</em>.
-Окно примет следующий вид (рисунок <strong>В</strong>):</p></div>
-<div class="imageblock" style="text-align:center;">
-<div class="content">
-<img src="images/DownloadGPS.jpg" alt="Рисунок: Импорт координат погружений" />
-</div>
-</div>
-<div class="paragraph"><p>Обратите внимание, что теперь кнопка <em>Применить</em> доступна. Нажатие на нее обновит
-названия мест и координаты недавно загруженных или введенных вручную погружений, у
-которых дата и время совпадают с временем фиксации на смартфоне. Если вы уже
-указали название дайв-сайта перед импортом координат, <em>Subsurface</em> отдаст
-предпочтение этим данных и не будет их перезаписывать.</p></div>
-<div class="paragraph"><p>Важно, чтобы часы на вашем смартфоне и дайв-компьютере были синхронизированы,
-так как <em>Subsurface</em> сопоставляет погружения именно по дате-времени, хотя и
-допускает некоторую погрешность. В случае большого разбега в показаниях
-времени координаты не будут обновлены.</p></div>
-<div class="paragraph"><p>Сопоставление по дате-времени может не сработать и по другим причинам
-например, из-за часовых поясов, или в случае нескольких повторных погружений в
-одном месте (в этом случае координаты будут сопоставлены только с первым
-погружением в серии). Для обхода этой проблемы мы рекомендуем вручную изменить
-дату-время погружения <strong>перед</strong> загрузкой GPS-координат и вернуть в начальное
-значение <strong>после</strong> импорта.</p></div>
-<div class="admonitionblock">
-<table><tr>
-<td class="icon">
-<img src="images/icons/info.jpg" alt="Замечание" />
-</td>
-<td class="content">Полезные советы:</td>
-</tr></table>
-</div>
-<div class="ulist"><ul>
-<li>
-<p>
-<em>Фоновая служба</em>, будучи хорошим подспорьем, может тем не менее заполнить весь
-список точками, не имеющими никакого отношения к погружениям, а отражающими
-путь судна. И в настоящий момент удаление этих точек с сервера довольно
-проблематично. Поэтому очень желательно удалить ненужные точки перед отправкой
-их на сервер. Это необходимо, если вы хотите видеть на карте только точки погружений.
-</p>
-</li>
-<li>
-<p>
-Желательно для погружений указывать информативные названия, и как минимум
-задать вразумительное название шаблона для автоматически добавляемых
-погружений.
-</p>
-</li>
-</ul></div>
-</div>
-</div>
-<div class="sect2">
-<h3 id="S_LoadImage">5.4. Добавление фотографий к погружениям</h3>
-<div class="paragraph"><p>Многие (если не все) дайверы берут с собой на погружение камеру, чтобы сделать
-несколько запоминающихся фото. <em>Subsurface</em> позволяет прикрепить эти
-фотографии к конкретному погружению и просматривать их на профиле погружения
-и на вкладке <em>Фотографии</em>.</p></div>
-<div class="sect3">
-<h4 id="_загрузка_фотографий_и_синхронизация_времени_между_фотоаппаратом_и_дайв_компьютером">5.4.1. Загрузка фотографий и синхронизация времени между фотоаппаратом и дайв-компьютером</h4>
-<div class="paragraph"><p>Нажмите левой кнопкой мыши на погружении в списке, чтобы выбрать его, а затем
-правой кнопкой мыши и выберите из контекстного меню пункт <em>Загрузить фото</em>:</p></div>
-<div class="imageblock" style="text-align:center;">
-<div class="content">
-<img src="images/LoadImage1_f20.jpg" alt="Рисунок: Меню загрузки фотографий" />
-</div>
-</div>
-<div class="paragraph"><p>В системном диалоге выбора файлов выберите фотографии для загрузки в
-<em>Subsurface</em> и нажмите клавишу <em>Открыть</em>:</p></div>
-<div class="imageblock" style="text-align:center;">
-<div class="content">
-<img src="images/LoadImage2_f20.jpg" alt="Рисунок: Выбор фотографий для загрузки" />
-</div>
-</div>
-<div class="paragraph"><p>Вам будет представлен диалог, показанный ниже. Проблема состоит в том, что
-зачастую время на дайв-компьютере и камере, используемых при погружении,
-не совпадают. Разница может составлять несколько минут. Если <em>Subsurface</em>
-сможет синхронизировать время между этими двумя устройствами, то сможет и
-правильно расположить фотографии на профиле погружения.</p></div>
-<div class="paragraph"><p>Добиться такой синхронизации в <em>Subsurface</em> можно двумя способами:</p></div>
-<div class="ulist"><ul>
-<li>
-<p>
-<strong>Вручную</strong>: Если вы записали точное время камеры в самом начале погружения,
-то вы можете вычислить смещение по времени. Если вы не меняли установки
-даты-времени на своих устройствах, то вы можете это сделать в конце дня после
-серии дайвов. После этого вы можете указать этот смещение в поле <em>Сдвинуть
-время изображений</em> , как показано на рисунке <strong>А</strong>. Если часы камеры спешат на
-7 минут от показаний часов дайв-компьютера, укажите значение смещения 00:07,
-выберите в переключателе <em>Раньше - Позже</em> значение <em>Раньше</em> (поскольку часы
-камеры спешат, нужно сдвинуть время на 7 минут раньше) и нажмите кнопку
-<em>ОК</em>.
-</p>
-</li>
-</ul></div>
-<div class="imageblock" style="text-align:center;">
-<div class="content">
-<img src="images/LoadImage3b_f20.jpg" alt="Рисунок: Диалог синхронизации" />
-</div>
-</div>
-<div class="ulist"><ul>
-<li>
-<p>
-<strong>По фотографии</strong>: <em>Subsurface</em> предлагает другой хитрый способ для синхронизации
-времени. Если вы сделаете фотографию экрана дайв-компьютера с показаниями
-часов, <em>Subsurface</em> сможет получить точное время камеры из информации,
-сохраняемой в каждой сделанной фотографии. Для этого используйте нижнюю часть
-диалогового окна <em>Сдвинуть время изображений</em>. При этом значения сдвига
-в верхней части окна игнорируются.
-Нажмите на горизонтально вытянутой кнопке <em>Выбрать изображения отображающие
-время на дайв-компьютере</em>. В окне выбора файлов укажите фото вашего
-дайв-компьютера и нажмите <em>Открыть</em>. <em>Subsurface</em> отобразит это фото в правой
-нижней части окна и к этому моменту будет знать время, когда эта фотография
-была сделана. Теперь вам только осталось в поле слева от фотографии указать
-дату-время компьютера, как указано на фото. Основываясь на этой информации,
-<em>Subsurface</em> может вычислить разницу во времени между камерой и
-дайв-компьютером. На рисунке <strong>В</strong> выше показано загруженное изображение компьютера
-и дата-время у него, перенесенные в поле слева.
-</p>
-</li>
-</ul></div>
-<div class="paragraph"><p>Если фотография была сделана задолго до или после погружения, она не будет
-показываться на профиле. <em>Subsurface</em> допускает интервал равный 30 минутам до и после погружения.</p></div>
-</div>
-<div class="sect3">
-<h4 id="_просмотр_фотографий">5.4.2. Просмотр фотографий</h4>
-<div class="paragraph"><p>После загрузки фотографии отображаются:</p></div>
-<div class="ulist"><ul>
-<li>
-<p>
-на вкладке <em>Фотографии</em> информационной панели
-</p>
-</li>
-<li>
-<p>
-в виде маленьких иконок на профиле погружения в соответствии
- со временем фото:
- Для просмотра добавленных фотографий на профиле погружений, активируйте
- переключатель <em>Фотографии</em> на панели слева от профиля погружения:
-</p>
-</li>
-</ul></div>
-<div class="imageblock" style="text-align:left;">
-<div class="content">
-<img src="images/icons/ShowPhotos_f20.png" alt="Рисунок: Переключатель Фотографии" />
-</div>
-</div>
-<div class="paragraph"><p>Профиль погружения при этом будет выглядеть следующим образом:</p></div>
-<div class="imageblock" style="text-align:center;">
-<div class="content">
-<img src="images/LoadImage4_f20.jpg" alt="Рисунок: Фотографии на профиле" />
-</div>
-</div>
-<div class="paragraph"><p>При наведении мышкой на иконку фото на профиле, будет показана миниатюрная
-фотография:</p></div>
-<div class="imageblock" style="text-align:center;">
-<div class="content">
-<img src="images/LoadImage5_f20.jpg" alt="Рисунок:Миниатюрное фото на профиле" />
-</div>
-</div>
-<div class="paragraph"><p>Обратите внимание, что в левом верхнем углу миниатюры есть изображение
-мусорной корзины, при нажатии на которое картинка будет удалена. Поэтому
-будьте внимательны, кожа щелкаете мышкой на картинке. При нажатии мышкой на
-миниатюрное фото (в профиле или на вкладке <em>Фотографии), полноразмерная
-фотография откроется во внешней программе для просмотра изображений. Фотографии также могут
-быть удалены на вкладке _Фотографии</em> (см. ниже).</p></div>
-<div class="imageblock" style="text-align:center;">
-<div class="content">
-<img src="images/LoadImage6_f20.jpg" alt="Рисунок: Просмотр полноразмерных фотографий" />
-</div>
-</div>
-</div>
-<div class="sect3">
-<h4 id="_вкладка_em_фотографии_em">5.4.3. Вкладка <em>Фотографии</em></h4>
-<div class="paragraph"><p>Фотографии, добавленные к погружению, отображаются миниатюрными картинками на
-вкладке <em>Фотографии</em> в <em>Информационной панели</em>. Снимки, сделанные в серии и
-имеющие короткий временной интервал, могут перекрывать друг друга на профиле,
-но легко различимы на этой вкладке. Одиночный щелчок мышью на фотографии
-выделяет ее, двойной щелчок мышью открывает окно просмотра фото во внешней
-программе. Фотографию можно удалить на вкладке <em>Фотографии</em>, выбрав ее щелчком
-мыши и нажатием клавиши <em>Del</em> (фотография будет удалена и из профиля).</p></div>
-</div>
-<div class="sect3">
-<h4 id="_фотографии_на_внешнем_жестком_диске">5.4.4. Фотографии на внешнем жестком диске</h4>
-<div class="paragraph"><p>Многие фотографы хранят свои снимки на внешнем накопителе. Если внешний диск
-подключен, то <em>Subsurface</em> в большинстве случаев увидит его, и таким образом
-будет обеспечен доступ к внешнему хранилищу фотографий. При этом вы добавляете
-фото с внешнего диска так, как описан выше. Однако после того, как внешний
-накопитель отключен, у <em>Subsurface</em> не будет доступа к фотографиям. Если на
-панели кнопок-переключателей (слева от профиля) нажата кнопка <em>Миниатюры
-фотографий</em>, то вместо картинок на профиле буду показываться белые точки, а на
-вкладке <em>Фотографии</em> только имена файлов вместо миниатюр. После подключения
-внешнего накопителя вы снова сможете увидеть фотографии.</p></div>
-</div>
-<div class="sect3">
-<h4 id="S_FindMovedImages">5.4.5. Перенос фотографий между директориями, жесткими дисками и компьютерами</h4>
-<div class="paragraph"><p>После загрузки фотографии в <em>Subsurface</em> и ее привязки к погружению, папка, в
-которой она находится, запоминается с тем, чтобы найти фото в следующий раз,
-когда вы откроете погружение. Если фотография или вся коллекция переносится на
-другой жесткий диск или компьютер, маловероятно что структура каталогов будет
-такой же, как до переноса. <em>Subsurface</em> попытается загрузить фотографии из их
-начального местоположения и не сможет их найти. Вместо того, чтобы удалять все
-фотографии и загружать их заново, <em>Subsurface</em> предлагает механизм, который значительно
-упрощает процесс обновления местоположения фотографий: обновление с помощью "отпечатков".</p></div>
-<div class="paragraph"><p>Когда фотография загружается в <em>Subsurface</em>, для нее вычисляется цифровой отпечаток, который
-сохраняется наряду с прочей информацией о фотографии. После переноса фото-коллекции (которая уже
-была загружена в <em>Subsurface</em>) в другую папку, диск или компьютер, <em>Subsurface</em> может выполнить
-следующие шаги:</p></div>
-<div class="ulist"><ul>
-<li>
-<p>
-рекурсивно просканировать указанную папку и вложенные поддиректории, куда фотографии были
- перенесены,
-</p>
-</li>
-<li>
-<p>
-вычислить отпечатки для всех найденных фотографий и
-</p>
-</li>
-<li>
-<p>
-если найдено соответствие между новым отпечатком и оригинальным, вычисленным при начальной
- загрузке фотографии (даже если имена файлов изменились), то информация о новом местоположении
- будет автоматически обновлена, с тем чтобы <em>Subsurface</em> мог найти ее в новой директории.
-</p>
-</li>
-</ul></div>
-<div class="paragraph"><p>Это можно сделать, выбрав в <strong>Главном меню</strong> пункт <em>Файл → Найти перемещенные фото</em>. Вам будет
-предложено выбрать папку, куда были перенесены фотографии. Выберите директорию и нажмите кнопку
-<em>Сканировать</em>. Этот процесс может занять несколько минут, после чего сможет отобразить фотографии
-для выбранного погружения.</p></div>
-<div class="sidebarblock" id="Image_fingerprint_upgrade">
-<div class="content">
-<div class="paragraph"><p><strong>Обновления существующих коллекций фотографий без отпечатков</strong></p></div>
-<div class="admonitionblock">
-<table><tr>
-<td class="icon">
-<img src="images/icons/important.png" alt="Важно" />
-</td>
-<td class="content"><em>Subsurface</em> автоматически вычисляет отпечатки всех фотографий, загруженных в него. При работе
-с фото, удостоверьтесь, что они доступны для <em>Subsurface</em>.</td>
-</tr></table>
-</div>
-<div class="paragraph"><p><em>Subsurface</em> каждый раз проверяет и, если необходимо, обновляет отпечатки фотографий в рамках отдельного погружения, если:
-- Ассоциированные фото отображаются на профиле в фите миниатюр.
-- Были внесены изменения на вкладке <strong>Примечания</strong> и была нажата кнопка <em>Применить изменения</em>.</p></div>
-</div></div>
-</div>
-</div>
-<div class="sect2">
-<h3 id="_ведение_журнала_для_специальных_типов_погружений">5.5. Ведение журнала для специальных типов погружений</h3>
-<div class="sect3">
-<h4 id="S_MulticylinderDives">5.5.1. Погружения с несколькими баллонами</h4>
-<div class="paragraph"><p><em>Subsurface</em> позволяет без проблем вести учет многобаллонных погружений. Такие погружения обычно
-выполняются если (а) не хватает воздуха для совершения погружения на одном баллоне; (б) нужно более
-одной смеси по причине большой глубины или для выполнения декомпрессионных процедур. Поэтому
-многобаллонные погружения зачастую выполняются техническими дайверами, которые ныряют дольше и глубже.
-Для <em>Subsurface</em> важна только следующая информация:</p></div>
-<div class="ulist"><ul>
-<li>
-<p>
-<strong>Описание баллонов погружения</strong>. Это выполняется на вкладке <strong>Снаряжение</strong> информационной панели так,
- как описано <a href="#cylinder_definitions">выше</a>. Перечислите все баллоны, указав их характеристики и
- типы смесей.
-</p>
-</li>
-<li>
-<p>
-<strong>Запишите время замены смесей</strong>: некоторые дайв-компьютеры предоставляют такую информацию (при
- условии, что вы нажали соответствующую кнопку). Если же компьютер не сохраняет эту информацию,
- вы можете записать время замены на слэйте.
-</p>
-</li>
-<li>
-<p>
-<strong>Укажите события замены смеси на профиле погружения</strong>: если вы выполнили предыдущий пункт, то вам
- нужно отметить эти события на профиле. Для этого щелкните на нем правой кнопкой мыши в соответствующее
- время и в контекстном меню выберите пункт "Добавить замену газа" и укажите нужный баллон из списка,
- созданного на первом шаге (см. рисунок ниже). Если на панели переключателей нажата кнопка <strong>Замена
- смесей</strong>, то эти события будут также отображены на полосе в нижней части профиля погружения.
-</p>
-</li>
-</ul></div>
-<div class="paragraph"><p>Если вы выполнили эти шаги, то <em>Subsurface</em> будет отображать выбранные баллоны для соответствующих
-сегментов погружения. Ниже на рисунке представлен профиль многобаллонного погружения, начинающегося
-с EAN28, и дальнейшим переходом на 26 минуте на EAN50 для выполнения декомпрессии.</p></div>
-<div class="imageblock" style="text-align:center;">
-<div class="content">
-<img src="images/multicylinder_dive.jpg" alt="Рисунок: Профиль многобаллонного погружения" />
-</div>
-</div>
-</div>
-<div class="sect3">
-<h4 id="_погружения_в_конфигурации_side_mount">5.5.2. Погружения в конфигурации side-mount</h4>
-<div class="paragraph"><p>Погружения в конфигурации с боковой подвеской является просто еще одной из разновидностей
-многобаллонных погружений, зачастую с двумя или всеми баллонами, заполненными одинаковой смесью.
-Хотя эта конфигурация наиболее популяра среди пещерных дайвером, она может использоваться и для
-рекреационных погружений после соответствующей подготовки. Как и в случае многобаллонных погружений,
-для учета таких погружений необходимо выполнить три шага:</p></div>
-<div class="ulist"><ul>
-<li>
-<p>
-<strong>Запись событий смена баллонов во время погружения</strong>. Поскольку сайд-маунт погружения
- обычно выполняются с двумя баллонами с воздухом или одинаковым газом, <em>Subsurface</em>
- различает баллоны между собой. Чего не скажешь о большинстве дайв-компьютеров, которые
- делают понимают переключение между разными <em>смесями</em>, а не <em>баллонами</em>. Это означает, что
- при импорте погружений с таких компьютеров события о смене баллонов с одинаковой смесью
- не будут загружены. Поэтому вам придется записывать эти события на слэйте, или, если
- ваш компьютер умеет, ставить закладки для таких событий, чтобы позже их загрузить.
- Сохранение событий замены баллонов - наиболее сложная задача при ведении журнала сайд-маунт погружений.
-</p>
-</li>
-<li>
-<p>
-<strong>Укажите конфигурацию баллонов</strong> на вкладке <strong>Снаряжение</strong> (см. рисунок ниже, на котором
- добавлено два 12-литровых баллона).
-</p>
-</li>
-<li>
-<p>
-<strong>Укажите события смены баллонов</strong>. После импорта погружения из дайв-компьютера в <em>Subsurface</em>,
-вам необходимо проставить события замены баллонов на профиле погружения. События добавляются
-щелчком правой кнопки мыши в соответствующем месте профиля и выбором пункта <em>Добавить замену смеси</em>
-в выпадающем контекстном меню. В списке показывает список доступных баллонов, при этом текущий
-активный баллон будет недоступен для выбора. На картинке ниже Баллон 1 недоступен, оставляя для
-выбора только Баллон 2. Выберите нужный баллон из списка. Событие смены баллона будет отображено на
-профиле соответствующей картинкой. Если активировано отображение <strong>Замена смесей</strong> (на панели
-инструментов слева от профиля), то соответствующая информация будет показываться в нижней части профиля.
-После добавления всех событий замены к профилю, на нем должны отображаться корректные значения
-давления по всех баллонах, как показано на следующем рисунке.
-</p>
-</li>
-</ul></div>
-<div class="imageblock" style="text-align:center;">
-<div class="content">
-<img src="images/sidemount1.jpg" alt="Рисунок: Профиль погружения в конфигурации сайд-маунт" />
-</div>
-</div>
-<div class="paragraph"><p>Эта глава демонстрирует гибкость <em>Subsurface</em> при ведении журналов погружений.</p></div>
-</div>
-<div class="sect3">
-<h4 id="S_sSCR_dives">5.5.3. Погружения с ребризером полузамкнутого цикла (SCR)</h4>
-<div class="admonitionblock">
-<table><tr>
-<td class="icon">
-<img src="images/halcyon_RB80.jpg" alt="Замечание" />
-</td>
-<td class="content">Пассивные ребризеры полузамкнутого цикла (pSCR) представляют собой дыхательный аппарат, рециркулирующий
-дыхательную смесь, удаляя из нее выдыхаемый углекислый газ. Приблизительно десятая часть выдыхаемого
-воздуха сбрасывается в воду, при этом свежая дыхательная смесь (обычно Nitrox) добавляется из баллона.
-Поэтому даже на одном баллоне можно провести гораздо больше времени под водой, чем используя
-рекреационную конфигурацию на открытом цикле. В случае pSCR свежая смесь подается из баллона при
-каждом вдохе. Активные ребризеры (aSCR) подают свежую смесь из баллона постоянно.</td>
-</tr></table>
-</div>
-<div class="paragraph"><p>Для учета погружений с использованием pSCR не требуется никаких специальных действий. Достаточно:</p></div>
-<div class="ulist"><ul>
-<li>
-<p>
-Выбрать режим погружения pSCR на вкладке <strong>Погружение</strong>
-</p>
-</li>
-<li>
-<p>
-Погружения с использованием pSCR обычно выполняются с заменой смесей. Укажите все необходимые
- баллоны как описано выше и укажите события замены смесей на профиле, как указано выше в главе
- <a href="#S_MulticylinderDives">Погружения с несколькими баллонами</a>.
-</p>
-</li>
-</ul></div>
-<div class="paragraph"><p>При выборе режима pSCR, расчетный потолок погружения учитывает снижение уровня кислорода в области
-загубника, что увеличивает время декомпрессии. Ниже приведен профиль pSCR погружения на смеси EAN36
-и с одним баллоном кислорода для декомпрессии. Обратите внимание, что погружение заняло более двух
-часов.</p></div>
-<div class="imageblock" style="text-align:center;">
-<div class="content">
-<img src="images/pSCR_profile.jpg" alt="Рисунок: Профиль погружения с pSCR" />
-</div>
-</div>
-</div>
-<div class="sect3">
-<h4 id="S_CCR_dives">5.5.4. Погружения с ребризером закрытого цикла (CCR)</h4>
-<div class="admonitionblock">
-<table><tr>
-<td class="icon">
-<img src="images/APD.jpg" alt="Замечание" />
-</td>
-<td class="content">Ребризеры замкнутого цикла используют передовые технологии для рециркуляции отработанного газа,
-выполняя две функции для поддержания концентрации кислорода, делая смест пригодной для дыхания:
-а) удаление углекислого газа из выдыхаемого воздуха
-б) поддержание концентрации кислорода в безопасных пределах.
-На текущий момент <em>Subsurface</em> обеспечивает наилучшую поддержку CCR дайв-компьютера Poseidon
-MkVI Discovery. Интерфейс работы с ребризерами замнутого цикла находится в активной разработке и на
-текущий момент считается экспериментальным. А отличие от рекреационных дайв-компьютеров, системы
-CCR не позволяют загружать журналы нескольких погружений одномоментно. Вместо этого каждое погружение
-хранится отдельно. Это означает, что <em>Subsurface</em> не может загружать погружения непосредственно с
-дайв-компьютера ребризера. Погружения должны быть импортированы таким же образом, как и из других
-цифровых источников.</td>
-</tr></table>
-</div>
-<div class="sect4">
-<h5 id="_импорт_погружения_с_ребризером_закрытого_цикла">Импорт погружения с ребризером закрытого цикла</h5>
-<div class="paragraph"><p>Прочитайте главу <a href="#S_ImportingAlienDiveLogs">Импорт погружений из других
-цифровых источников</a>. В главном меню <em>Subsurface</em> выберите <em>Импорт → Импорт
-журналов</em> чтобы открыть окно <a href="#Unified_import">Универсальный импорт</a>. Как
-описано в этой главе, в правой нижней части окна находится список
-поддерживаемых источников, среди которых есть и файлы (Poseidon) MkVI
-(поддержка другого CCR-оборудование активно развивается). Выбрав нужный формат
-и директорию с файлами-журналами, вам нужно выбрать конкретный журнал
-погружения (в случае MkVI это один файл с расширением .txt). После выбора
-файла нажмите на кнопку <em>Открыть</em>.</p></div>
-</div>
-</div>
-<div class="sect3">
-<h4 id="_информация_отображаемая_для_ccr_погружений">5.5.5. Информация, отображаемая для CCR-погружений</h4>
-<div class="paragraph"><p><em>Парциальные давления газов</em>: График парциального давления кислорода показывает информацию с
-кислородных датчиков ребризера. В отличие от рекреационного режима, где значения pO<sub>2</sub> высчитываются
-исходя из состава смеси и глубины, для CCR-погружений эти значения берутся от датчиков. В этом случае
-график должен быть достаточно ровным, соответствуя значению установки кислорода (set-point). Среднее значение
-pO<sub>2</sub> не является средним значением от датчика, а рассчитано <em>Subsurface</em> следующим
-образом:</p></div>
-<div class="ulist"><ul>
-<li>
-<p>
-для двух датчиков O<sub>2</sub> рассчитывается среднее значение.
-</p>
-</li>
-<li>
-<p>
-для систем с тремя датчиками (например, APD) также используется среднее значение. Однако разница
- в показаниях разных датчиков более 0,1 бар в один момент времени, такое значение считается
- ложны. Если один из датчиков возвращает ложное значение, то он игнорируется.
-</p>
-</li>
-<li>
-<p>
-если данные от датчиков отсутствуют, то значение pO<sub>2</sub> принимается равным установке.
-</p>
-</li>
-</ul></div>
-<div class="paragraph"><p>Среднее значение pO<sub>2</sub> сенсоров отображается зеленой линией.</p></div>
-<div class="paragraph"><p>Значения установок кислорода, а также показания индивидуальных датчиков, могут быть показаны на
-профиле. Отображение расширенной информации для CCR-погружения регулируется в <em>Настройках_ (доступны
-в <a href="#S_CCR_options">_Файл → Настройки → Профиль</em></a>. Вот настройки, влияющие на отображение pO<sub>2</sub>
-на профиле погружения при нажатой на панели переключателей кнопке <em>График pO<sub>2</sub></em>.</p></div>
-<div class="imageblock" style="text-align:center;">
-<div class="content">
-<img src="images/CCR_preferences_f20.jpg" alt="Рисунок: Настройки профиля CCR-погружения" />
-</div>
-</div>
-<div class="paragraph"><p>Первый параметр позволяет показать график значения установки (set-point), который отображается
-красной линией поверх графика парциального давления и позволяет сравнить значения среднего
-измеренного парциального значения с установкой, как показано на рисунке ниже:</p></div>
-<div class="imageblock" style="text-align:center;">
-<div class="content">
-<img src="images/CCR_setpoint_f20.jpg" alt="Рисунок: Графики pO~2~ и установки CCR" />
-</div>
-</div>
-<div class="paragraph"><p>Второй параметр позволяет вывести график от каждого сенсора ребризера. Цветовая кодировка сенсоров
-следующая:</p></div>
-<div class="ulist"><ul>
-<li>
-<p>
-Сенсор 1: серый
-</p>
-</li>
-<li>
-<p>
-Сенсор 2: голубой
-</p>
-</li>
-<li>
-<p>
-Сенсор 3: коричневый
-</p>
-</li>
-</ul></div>
-<div class="paragraph"><p>Среднее значение pO<sub>2</sub> показывается зеленым цветом. Такое отображение позволяет непосредственно
-сравнить данные от каждого сенсора и выявить странно низкие или абсолютно неверные показания.</p></div>
-<div class="imageblock" style="text-align:center;">
-<div class="content">
-<img src="images/CCR_sensor_data_f20.jpg" alt="Рисунок: Графики сенсоров CCR" />
-</div>
-</div>
-<div class="paragraph"><p>График установки может быть наложен поверх графика парциальных давлений, для этого нужно поставить
-галочки напротив обоих параметров. Парциальные давления азота (и гелия, если применимо) отображаются
-так же, как для погружения на открытом цикле.</p></div>
-<div class="paragraph"><p><em>События</em>: в случае погружений с ребризером могут быть записаны дополнительные события, например,
-перевод загубника в режим открытого цикла. Такие события отображаются на профиле в виде желтых
-треугольников. При наведении на него указателя мыши, в <a href="#S_InfoBox">плавающем информационном окне</a>
-показывается описание события.</p></div>
-<div class="paragraph"><p><em>Давление в баллонах:</em> некоторые CCR дайв-компьютеры (например, Poseidon MkVI) сохраняют информацию
-о давлении в баллонах с кислородом и дилуентом. График давлений в этих баллонах отображается
-зелеными линиями поверх профиля глубины. В дополнение к этому, информация о начальном и конечном
-давлениях в баллонах с дилуентом и кислородом показывается на вкладке <em>Снаряжение</em>.
-Ниже представлен профиль CCR-погружения, на котором показаны графики значений установки, сенсоров и
-давлений в баллонах. В этом случае мы видим согласованность показаний двух сенсоров.</p></div>
-<div class="imageblock" style="text-align:center;">
-<div class="content">
-<img src="images/CCR_dive_profile_f20.jpg" alt="Рисунок: Профиль CCR-погружения" />
-</div>
-</div>
-<div class="paragraph"><p><em>Дополнительная информация</em>: Информация, специфичная для конкретного оборудования, отображается в
-<em>Subsurface</em> на вкладке <a href="#S_ExtraDataTab">Дополнительная информация</a>. Она может включать настройки
-оборудования и прочие данные.</p></div>
-<div class="paragraph"><p>Деко-потолок, вычисленный <em>Subsurface</em>, не всегда точен, потому что зачастую невозможно узнать
-точное парциальное давление азота в цикле из журнала, импортированного из ребризера. Однако, многие
-дайв-компьютеры, поддерживающие ребризеры, сообщают информацию о своем вычисленном деко-потолке в
-журнале, и это значение может быть более точным. Для отображения этого потолка необходимо активировать
-соответствующую кнопку на панели слева от профиля погружения?</p></div>
-<div class="imageblock">
-<div class="content">
-<img src="images/icons/cceiling.jpg" alt="Кнопка отображения потолка дайв-компьютера" />
-</div>
-</div>
-<div class="paragraph"><p>По умолчанию потолок дайв-компьютера отображается на профиле погружения белым цветом. Вы можете
-отобразить его красным, выбрав соответствующий параметр в <em>Файл → Настройки → Профиль</em>. Ниже
-показан профиль погружения с отображенным потолком дайв-компьютера:</p></div>
-<div class="imageblock" style="text-align:center;">
-<div class="content">
-<img src="images/CCR_dive_ceilingF22.jpg" alt="Рисунок: Деко-потолок дайв-компьютера" />
-</div>
-</div>
-<div class="paragraph"><p>За более детальной информацией по загрузке погружений из ребризеров Poseidon MkVI и APD обратитесь
-к <a href="#S_PoseidonMkVI">ПРИЛОЖЕНИЮ Б</a>.</p></div>
-</div>
-</div>
-</div>
-</div>
-<div class="sect1">
-<h2 id="_подробная_информация_о_погружениях_в_журнале">6. Подробная информация о погружениях в журнале</h2>
-<div class="sectionbody">
-<div class="sect2">
-<h3 id="_вкладка_strong_информация_strong_для_одиночного_погружения">6.1. Вкладка <strong>Информация</strong> (для одиночного погружения)</h3>
-<div class="paragraph"><p>Вкладка <em>Информация</em> предоставляет суммарную информацию по погружению,
-выбранному в <strong>Списке погружений</strong>. Здесь отображается такая полезная
-информация, как поверхностный интервал перед погружением, максимальная и
-средняя глубина дайва, объемный расход газов, расход воздуха на поверхности
-(SAC) и единицы кислородного отравления (OTU).</p></div>
-<div class="admonitionblock">
-<table><tr>
-<td class="icon">
-<img src="images/icons/info.jpg" alt="Замечание" />
-</td>
-<td class="content">Вычисление SAC и расхода газов:
-<em>Subsurface</em> очень точно вычисляет SAC и расход газов принимая во внимание
-несжимаемость газов, что особенно важно при давлении в баллоне свыше 200 бар.
-Более подробно об этом описано в <a href="#SAC_CALCULATION">Приложение Ж</a>.</td>
-</tr></table>
-</div>
-</div>
-<div class="sect2">
-<h3 id="S_ExtraDataTab">6.2. Вкладка <strong>Дополнительно</strong> (обычно для индивидуального погружения)</h3>
-<div class="paragraph"><p>При использовании дайв-компьютера он обычно сообщает дополнительную информацию, которую невозможно
-отобразить единообразным образом, принимая во внимание, что эта информация различается для разных
-моделей. Обычно эта информация включает в себя настройки компьютера, уровень заряда батареи,
-неполетное время или установки градиент-фактора. Когда доступны, эти данные отображаются на вкладке
-<strong>Дополнительно</strong>. На рисунке ниже приведены дополнительные данные для погружение на ребризере Poseidon.</p></div>
-<div class="imageblock" style="text-align:center;">
-<div class="content">
-<img src="images/ExtraDataTab_f20.jpg" alt="Рисунок: Вкладка Дополнительно" />
-</div>
-</div>
-</div>
-<div class="sect2">
-<h3 id="_вкладка_strong_статистика_strong_для_нескольких_погружений">6.3. Вкладка <strong>Статистика</strong> (для нескольких погружений)</h3>
-<div class="paragraph"><p>Вкладка <em>Статистика</em> предоставляет суммарную статистику для нескольких
-погружений, предполагая, что вы выбрали несколько дайвов в <strong>Списке погружений</strong>
-(используйте клавиши Ctrl и Shift при выборе погружений мышкой). На вкладке
-отображается следующая полезная информация: количество выбранных погружений и их
-суммарное время, минимальные, максимальные и средние значения длительности,
-температуры воздуха и воды, SAC. Тут также отображается глубины самого
-глубокого и самого мелкого погружений среди выбранных.</p></div>
-</div>
-<div class="sect2">
-<h3 id="S_DiveProfile">6.4. Профиль погружения</h3>
-<div class="imageblock" style="text-align:center;">
-<div class="content">
-<img src="images/Profile2.jpg" alt="Рисунок: Пример профиля погружения" />
-</div>
-</div>
-<div class="paragraph"><p>Из всех панелей <em>Subsurface</em>, профиль предоставляет наиболее детальную
-информацию о погружении. Слева от профиля находится панель переключателей,
-позволяющая выбрать несколько вариантов отображения. Функции этих
-переключателей описаны ниже. Главным элементов профиля является график глубины
-как функция времени. В дополнение к информации о глубине, график также
-показывает скорость спуска/подъема относительно рекомендованной скорости. Эта
-информация закодирована разными цветами:</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>Цвет</strong></p></td>
-<td align="left" valign="top"><p class="table"><strong>Скорость спуска (м/мин)</strong></p></td>
-<td align="left" valign="top"><p class="table"><strong>Скорость подъема (м/мин)</strong></p></td>
-</tr>
-<tr>
-<td align="left" valign="top"><p class="table">Красный</p></td>
-<td align="left" valign="top"><p class="table">> 30</p></td>
-<td align="left" valign="top"><p class="table">>18</p></td>
-</tr>
-<tr>
-<td align="left" valign="top"><p class="table">Оранжевый</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">Желтый</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">Светло-зеленый</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">Темно-зеленый</p></td>
-<td align="left" valign="top"><p class="table">< 1.5</p></td>
-<td align="left" valign="top"><p class="table">< 1.5</p></td>
-</tr>
-</tbody>
-</table>
-</div>
-<div class="paragraph"><p>Профиль также отображает глубины пиков и провалов на графике. Серая линия показывает среднюю
-глубину в конкретный момент погружения.</p></div>
-<div class="admonitionblock">
-<table><tr>
-<td class="icon">
-<img src="images/icons/scale.jpg" alt="Замечание" />
-</td>
-<td class="content">В некоторых случаях профиль занимает по ширине не всю панель <strong>Профиль
-погружения</strong> Нажмите на переключатель <strong>Альтернативный масштаб</strong>, чтобы более
-эффективно использовать пространство экрана.</td>
-</tr></table>
-</div>
-<div class="paragraph"><p><strong>Температура воды</strong> отображается синей линией со указанием значений температуры
-в местах значительного изменения.</p></div>
-<div class="paragraph"><p>Профиль погружения может отображать графики парциальных давлений O₂, N₂ и He,
-расчетный потолок декомпрессии и потолок, посчитанный дайв-компьютером (виден
-только для глубоких, долгих или повторных погружений). Графики парциальных
-давлений показываются в нижней части профиля, каждый своим цветом для
-отдельного газа: кислород - зеленым, азот - черным, гелий - темно-красным.</p></div>
-<div class="admonitionblock">
-<table><tr>
-<td class="icon">
-<img src="images/icons/O2.jpg" alt="Замечание" />
-</td>
-<td class="content">Переключатель отображения графика парциального давления <strong>кислорода</strong>.</td>
-</tr></table>
-</div>
-<div class="admonitionblock">
-<table><tr>
-<td class="icon">
-<img src="images/icons/N2.jpg" alt="Замечание" />
-</td>
-<td class="content">Переключатель отображения графика парциального давления <strong>азота</strong>.</td>
-</tr></table>
-</div>
-<div class="admonitionblock">
-<table><tr>
-<td class="icon">
-<img src="images/icons/He.jpg" alt="Замечание" />
-</td>
-<td class="content">Переключатель отображения графика парциального давления <strong>гелия</strong>. Актуально
-только для дайверов, использующих Trimix, Helitrox или схожие дыхательные смеси.</td>
-</tr></table>
-</div>
-<div class="paragraph"><p>График <strong>расхода газа</strong> показывает давление в баллоне и его изменение во время
-погружения. Этот график принимает во внимание глубину, поэтому даже если вы
-вручную ввели начальное и конечное давление в баллоне, линия никогда не будет
-прямой. Аналогично графику глубины, график давления визуально предоставляет
-информацию о моментальном расходе газа (SAC) при использовании дайв-компьютера
-с интегрированным датчиком давления. Однако в этом случае цветовое кодирование
-осуществляется безотносительно какой-то абсолютной величины, а относительно
-усредненного расхода за время погружения. Таким образом, области красного
-или оранжевого цвета указывают на повышенный расход газа, в то время, как
-области темно-зеленого цвета говорят о расходе ниже среднего.</p></div>
-<div class="admonitionblock">
-<table><tr>
-<td class="icon">
-<img src="images/icons/Heartbutton.png" alt="Замечание" />
-</td>
-<td class="content">Нажатие на кнопку с изображение ритма сердца показывает информацию о частоте
-сердцебиения если дайв-компьютер оборудован датчиком пульса.</td>
-</tr></table>
-</div>
-<div class="paragraph"><p>Вы можете менять масштаб профиля с помощью колеса мыши или соответствующего
-жеста на сенсорной панели. По умолчанию <em>Subsurface</em> масштабирует панель
-профиля, так чтобы помещалось 30-минутное погружение на 30 метров. Очевидно,
-что для фридайверов это не актуально.</p></div>
-<div class="imageblock" style="text-align:center;">
-<div class="content">
-<img src="images/MeasuringBar.png" alt="Рисунок: Рулетка" />
-</div>
-</div>
-<div class="admonitionblock">
-<table><tr>
-<td class="icon">
-<img src="images/icons/ruler.jpg" alt="Замечание" />
-</td>
-<td class="content">С помощью рулетки вы можете измерять разницу <strong>глубины и времени</strong> между двумя
-точками погружения. Измерение производится путем перетаскиванию мышью двух
-красных точек. Результаты измерения отображаются в горизонтальной белой
-области ниже линии рулетки.</td>
-</tr></table>
-</div>
-<div class="admonitionblock">
-<table><tr>
-<td class="icon">
-<img src="images/icons/ShowPhotos.png" alt="Замечание" />
-</td>
-<td class="content">Добавленные к погружению фотографии могут быть отображены нажатием на
-переключатель <strong>Миниатюры фотографий</strong>. Положение фотографии на профиле
-соответствуют времени когда она была сделана. Если этот переключатель
-неактивен, фотографии не показываются.</td>
-</tr></table>
-</div>
-<div class="paragraph"><p>Профиле может показывать <strong>потолок</strong>, рассчитанный дайв-компьютером (а
-точнее, глубочайшая деко-остановка в данный момент времени). Он отображается
-полупрозрачной красной областью. Потолок появляется, когда при прямом подъеме
-на поверхность возникает риск возникновения декомпрессионной болезни (ДКБ) и в
-этом случае необходимо либо снизить скорость всплытия, либо выполнить
-несколько деко-остановок перед всплытием на поверхность. Не все
-дайв-компьютеры записывают эту информацию и делают ее доступной для загрузки;
-например, ни один из компьютеров Suunto не предоставляет этой информации.
-<em>Subsurface</em> независимо рассчитывает потолок и отображает его на профиле
-закрашенной областью зеленого цвета.
-Из-за разницы в алгоритмах, количества доступных данных и других факторов,
-доступных в момент расчета, расчетный потолок <em>Subsurface</em> и дайв-компьютера
-могут не совпадать, несмотря даже на то, что <em>градиент-факторы</em> могут
-совпадать (см. ниже).
-Зачастую <em>Subsurface</em> рассчитывает потолок для бездекомпрессионных погружений,
-в то время как компьютер не оставался в бездекомпрессионном режиме во все
-время дайва (представлен <span class="green">темно-зеленой</span> областью на профиле в начале
-этой главы). Это вызвано тем, что <em>Subsurface</em> рассчитывает деко-обязательства
-в каждый момент погружения, в то время, как дайв-компьютеры обычно принимают
-во внимание и время всплытия. Во время всплытия происходит рассыщение азота (и
-возможно гелия), поэтому даже технически "заработав" потолок на дне,
-обязательная деко-остановка не требуется. Это позволяет дайв-компьютерам
-рассчитывать большее время на дне.</p></div>
-<div class="admonitionblock">
-<table><tr>
-<td class="icon">
-<img src="images/icons/cceiling.jpg" alt="Замечание" />
-</td>
-<td class="content">Если дайв-компьютер умеет рассчитывать потолок и делает эту информацию
-доступной для <em>Subsurface</em> во время импорта, вы можете отображать этот
-потолок, нажать на переключатель <strong>Потолок компьютера</strong>.</td>
-</tr></table>
-</div>
-<div class="admonitionblock">
-<table><tr>
-<td class="icon">
-<img src="images/icons/ceiling1.jpg" alt="Замечание" />
-</td>
-<td class="content">Если переключатель <strong>Расчетный потолок</strong> нажат, потолок, если он существует,
-рассчитанный <em>Subsurface</em> будет показан на профиле зеленым цветом (рисунок <strong>А</strong>
-ниже). Вы можете далее поменять его отображение следующим образом:</td>
-</tr></table>
-</div>
-<div class="admonitionblock">
-<table><tr>
-<td class="icon">
-<img src="images/icons/ceiling2.jpg" alt="Замечание" />
-</td>
-<td class="content">Если нажат переключатель <strong>Расчет всех тканей</strong>, показывается потолок для всех
-типов тканей согласно модели Бюльмана (рисунок <strong>В</strong> ниже)</td>
-</tr></table>
-</div>
-<div class="admonitionblock">
-<table><tr>
-<td class="icon">
-<img src="images/icons/ceiling3.jpg" alt="Замечание" />
-</td>
-<td class="content">Если нажат переключатель <strong>3м шаг для расчетного потолка</strong>, потолок отображается
-ступеньками с шагом 3 метра.</td>
-</tr></table>
-</div>
-<div class="imageblock" style="text-align:center;">
-<div class="content">
-<img src="images/Ceilings2.jpg" alt="Рисунок: Потолок с 3м шагом" />
-</div>
-</div>
-<div class="admonitionblock">
-<table><tr>
-<td class="icon">
-<img src="images/icons/ShowCylindersButton.jpg" alt="Замечание" />
-</td>
-<td class="content">Если выбран этот переключатель, то баллоны, используемые в погружении, отображаются в виде цветной
-полосы в нижней части профиля погружения. Кодировка цветов следующая: кислород нарисован
-зеленой полосой, азот желтой, а гелий - красной. Рисунок ниже представляет профиль погружения с первой
-смесью Trimix (красно-зеленая полоса), с дальнейшим переходом на Nitrox (желто-зеленая полоса) на 23
-минуте. Баллоны с воздухом представлены светло-голубой полосой.</td>
-</tr></table>
-</div>
-<div class="imageblock" style="text-align:center;">
-<div class="content">
-<img src="images/ShowCylinders_f20.jpg" alt="Рисунок: График использования баллонов" />
-</div>
-</div>
-<div class="admonitionblock">
-<table><tr>
-<td class="icon">
-<img src="images/tissues.jpg" alt="Замечание" />
-</td>
-<td class="content">Показывает давление инертных газов в тканях относительно внешнего давления (горизонтальная серая
-линия). Давление в тканях рассчитывается по алгоритму Бюльмана ZH-L16 и отображается линиями, цвет
-которых варьируется от зеленого (самые быстрые ткани) до синего (самые медленные ткани).
-Черная линия, нарисованная выше графика внешнего давления, показывает максимальное допустимое
-перенасыщение согласно значений градиент-фактора, указанных в настройках. Для дайверов, планирующих
-декомпрессионные погружения, эффективное скорость рассыщения достигается при давлении в тканях
-большем чем окружающее давление (серая линия), но меньшем чем предельное (черная линия). Это
-представление отображает давление в тканях на протяжении всего погружения. Напротив,
-<a href="#S_gas_pressure_graph">Гистограмма давления газов</a> в плавающем <strong>Информационном окне</strong> отображает
-давление в момент времени, соответствующий положению указателя мыши на оси времени.</td>
-</tr></table>
-</div>
-<div class="imageblock" style="text-align:center;">
-<div class="content">
-<img src="images/tissuesGraph.jpg" alt="Рисунок: График насыщения тканей инертными газами" />
-</div>
-</div>
-<div class="paragraph"><p>Установки градиент-фактора непосредственно влияют на расчетный потолок и его глубину. Подробнее
-см. главу <a href="#S_GradientFactors">Установки градиент-фактора</a>. Текущие установки градиент-фактора
-(например, GF 35/75) указываются в верхней части профиля погружения.
-<strong>Обратите внимание:</strong> значение градиент-фактора на профиле - это НЕ значение, используемое
-дайв-компьютером, а установка, использующаяся самим <em>Subsurface</em> для расчета деко-обязательств.
-Более подробно по этой теме можно прочитать во внешних источниках:</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="_контекстное_меню_профиля_погружения">6.5. Контекстное меню профиля погружения</h3>
-<div class="paragraph"><p>Доступ к контекстному меню профиля погружения осуществляется нажатием правой кнопки мыши в любом
-месте графика. Меню позволяет добавлять закладки и события замены смеси или ручные установки для
-CCR-погружений в дополнение к тем, что были импортированы из дайв-компьютера. Маркеры помещаются
-на профиле в точках, соответствующих времени на горизонтальной оси в момент нажатия правой кнопкой
-мыши. При выборе события замены газа, вы далее должны выбрать смесь из списка доступных, как задано
-на вкладке Снаряжение. Добавления события смены установки CCR откроет окно, в котором можно задать
-новое значение. Как и в случает <strong>Планировщика</strong>, добавление установки со значением ноль означает, что
-дайвер перешел на открытый цикл, а ненулевое значение означает погружение на ребризере закрытого
-цикла (CCR).
-При щелчке правой кнопкой мыши на уже существующем
-маркере, меню будет расширено, позволяя вам удалить маркер и скрыть все
-маркеры данного типа. Чтобы восстановить скрытые маркеры, выберите в
-контекстном меню пункт <strong>Показывать все события</strong>.</p></div>
-</div>
-<div class="sect2">
-<h3 id="S_InfoBox">6.6. Информационное окно</h3>
-<div class="paragraph"><p>Информационное окно отображает подробную информацию, относящуюся к конкретной
-точке профиля погружения (рисунок <strong>В</strong>). Обычно это окно расположено в левой
-верхней части панели, но вы можете его перетащить в любое другое место, при
-этом позиция будет сохранена и не будет меняться при переключении между
-погружениями. Если мышка находится вне панели, информационное окно отображает
-только заголовок (рисунок <strong>А</strong>). Положение информационного окно запоминается между последовательными
-запусками <em>Subsurface</em>.</p></div>
-<div class="imageblock" style="text-align:center;">
-<div class="content">
-<img src="images/InfoBox2.jpg" alt="Рисунок: Информационное окно" />
-</div>
-</div>
-<div class="paragraph"><p>В момент наведения мышкой на профиль погружения, информационное окно
-распахивается и отображает различную информацию, относящуюся к той временной
-точке, где находится курсор мыши (рисунок *В). Таким образом, передвигая
-курсор мыши по горизонтальной оси времени, вы можете получить информацию о
-любом моменте погружения.
-В информационном окне представлены следующие данные: время погружения (@),
-глубина (Г), давление в баллоне (Д), температура (Т), скорость спуска/подъема
-(С), расход воздуха (SAC), парциальное давление кислорода, максимальная
-рабочая глубина (MOD), эквивалентная глубина по воздуху (EAD), эквивалентная
-наркозная глубина (END), эквивалентная глубина по плотности воздуха (EADD),
-декомпрессионные обязательства в данный момент времени (Деко), время до
-поверхности (TTS), расчетный потолок наряду с потолком для отдельных тканей по
-Бюльману.</p></div>
-<div class="paragraph"><p>Вы можете контролировать отображение некоторых из этих значений,
-воспользовавшись четырьмя переключателями на левой панели кнопок:</p></div>
-<div class="admonitionblock">
-<table><tr>
-<td class="icon">
-<img src="images/icons/MOD.jpg" alt="Замечание" />
-</td>
-<td class="content">Если этот переключатель нажат, информационное окно показывает <strong>максимальную
-рабочую глубину (MOD)</strong> для используемого газа. Значение MOD зависит от
-процентного содержания кислорода в смеси. Для воздуха (21% кислорода) это
-значение составляет около 57 метров. Погружения ниже MOD чреваты рисками,
-связанными с токсичностью кислорода.</td>
-</tr></table>
-</div>
-<div class="admonitionblock">
-<table><tr>
-<td class="icon">
-<img src="images/icons/NDL.jpg" alt="Замечание" />
-</td>
-<td class="content">Если этот переключатель нажат, информационное окно показывает
-<strong>бездекомпрессионный предел (NDL)</strong> или <strong>время до поверхности (TTS)</strong>. NDL
-указывает время, которое дайвер может оставаться на текущей глубине, без
-возникновения декомпрессионных обязательств (т.е. пока не появится потолок).
-Как только NDL превышен и появляются декомпрессионные обязательства, TTS
-указывает время до всплытия на поверхность, включая время всплытия и
-декомпрессии. TTS рассчитывается исходя и расхода (SAC) текущего газа, даже
-если на профиле указаны переходы на другие смеси.Значения TTS, превышающие 2
-часа, не могут быть точно рассчитаны и <em>Subsurface</em> отображает <em>TTS > 2ч</em>.</td>
-</tr></table>
-</div>
-<div class="admonitionblock">
-<table><tr>
-<td class="icon">
-<img src="images/icons/SAC.jpg" alt="Замечание" />
-</td>
-<td class="content">Если этот переключатель нажат, информационное окно показывает <strong>расход воздуха
-на поверхности (SAC)</strong>. SAC - объем дыхания, нормализованный для поверхности.
-Значение SAC меньше чем реальный расход газа, потому что на глубине 10м дайвер
-потребляет в два раза больше газа, чем на поверхности. Значение SAC не зависит
-от глубины и измеряются в литрах/мин или куб.футах/мин.</td>
-</tr></table>
-</div>
-<div class="admonitionblock">
-<table><tr>
-<td class="icon">
-<img src="images/icons/EAD.jpg" alt="Замечание" />
-</td>
-<td class="content">Если этот переключатель нажат, информационное окно показывает <strong>эквивалентную
-глубину по воздуху (EAD)</strong> для погружений на Nitrox и <strong>эквивалентную
-наркозную глубину (END)</strong> для Trimix. Эти значения важны для дайверов,
-погружающихся на смесях, отличных от воздуха. Значение этих величин зависят от
-состава газа. EAD - глубина гипотетического погружения на воздухе, в котором
-парциальное значение азота такое же, как и в текущем погружении на Nitrox.
-Дайв на Nitrox влечет такие же декомпрессионные обязательства, как и
-погружение на воздухе на глубину EAD. END - глубина гипотетического погружения
-на воздухе, в котором сумма парциальных давлений наркотических азота и
-кислорода такая же, как и в текущем погружении на Trimix. Тримиксный дайвер
-может ожидать такого же наркотического эффекта, погружайся он на воздухе на
-глубину END.</td>
-</tr></table>
-</div>
-<div class="paragraph"><p>На рисунке <strong>В</strong> выше показано информационное окно практически со всей доступной информацией.</p></div>
-<div class="sect3">
-<h4 id="S_gas_pressure_graph">6.6.1. Гистограмма давления газов</h4>
-<div class="paragraph"><p>В левой части <strong>Информационного окна</strong> расположена вертикальная гистограмма, отображающая давление
-азота (и других инертных газов, например гелия, там, где это применимо), вдыхаемых дайвером <em>в
-определенный момент времени</em>, соответствующий положению указателя мыши на оси времени. Рисунок ниже
-поясняет, что именно показывает гистограмма:</p></div>
-<div class="imageblock" style="text-align:center;">
-<div class="content">
-<img src="images/GasPressureBarGraph.jpg" alt="Рисунок: Гистограмма давления газов" />
-</div>
-</div>
-<div class="ulist"><ul>
-<li>
-<p>
-Светло-зеленая область означает общий объем газа, а верхняя граница этой области показывает
- общее давление газа, вдыхаемого дайвером (измеренное от нижней части гистограммы). Это давление
- имеет относительную величину и не показывает абсолютное давление.
-</p>
-</li>
-<li>
-<p>
-Горизонтальная черная линия ниже светло-зеленой границы указывает уравновешенное давление
- инертных газов, вдыхаемых дайвером, обычно азота. В случае Trimix, это значение будет составной
- величиной давлений азота и гелия. В нашем примере погружение выполнялось с использованием EAN32,
- поэтому эта линия отмечает 68% от общего расстояния от нижней части гистограммы до границы светло-
- зеленой области (общее давление газа).
-</p>
-</li>
-<li>
-<p>
-Темно-зеленая область в нижней части гистограммы отображает давление инертных газов в каждой из
- 16 групп тканей согласно алгоритма Бюльмана. "Быстрые" ткани расположены в левой части.
-</p>
-</li>
-<li>
-<p>
-Верхняя черная линия указывает на градиент-фактор, примененный к глубине в конкретной точке
- на <strong>Профиле погружения</strong>. Градиент-фактор интерполируется исходя из значений GFLow и GFHigh,
- указанных в вкладке <strong>Профиль</strong> в *Настройках*.
-</p>
-</li>
-<li>
-<p>
-Нижняя граница красной области на гистограмме отображает вычисленное по алгоритму Бюльмана
- M-значение, - давление инертного газа, при котором весьма вероятно формирование пузырьков,
- что в свою очередь может привести к декомпрессионной болезни.
-</p>
-</li>
-</ul></div>
-<div class="paragraph"><p>Эти пять величин показаны на рисунке выше в левой его части. Как меняется гистограмма на протяжении
-погружения, показано в правой части рисунка (погружение с использованием EAN32).</p></div>
-<div class="ulist"><ul>
-<li>
-<p>
-Гистограмма <strong>А</strong>. Дайвер перед погружением находится на поверхности. Давление в группах тканей
- такое же, как и уравновешенное давление.
-</p>
-</li>
-<li>
-<p>
-Гистограмма <strong>B</strong>. Дайвер погрузился на глубину 30 метров. Лишь некоторые ткани успели частично
- насытиться за время спуска, давление в тканях гораздо ниже уравновешенного давления.
-</p>
-</li>
-<li>
-<p>
-Гистограмма <strong>C</strong>. Дайвер провел 30 минут на глубине 30 метров. "Быстрые" ткани насытились до
- уровня уравновешенного давления (т.е. сравнялись по высоте с черной линий). Более "медленные"
- ткани, находящиеся справа, еще только находятся в процессе насыщения.
-</p>
-</li>
-<li>
-<p>
-Гистограмма <strong>D</strong>. Дайвер поднялся до глубины 4.5 метра. Так как во время подъема давление вдыхаемого
- газа значительно упало с 4 бар до 1.45 бар, давление различных групп тканей теперь значительно
- превышает эту величину и приближается к значению градиент-фактора (верхняя черная линия). Дальнейший
- подъем приведет к превышению значения градиент-фактора (GFHigh) и подвергнет дайвера риску.
-</p>
-</li>
-<li>
-<p>
-Гистограмма <strong>E</strong>. Дайвер оставался на глубине 4.5 метра в течение 10 минут. Насыщение "быстрых"
- тканей снизилось, в то время как насыщение "медленных тканей изменилось ожидаемо мало. Давление
- в "быстрых" тканях уже не приближается опасно близко к значению GFHigh и дайвер находится в более
- безопасной ситуации нежели чем случае <strong>D</strong>.
-</p>
-</li>
-</ul></div>
-</div>
-</div>
-</div>
-</div>
-<div class="sect1">
-<h2 id="_ведение_журнала_работа_с_группами_погружений">7. Ведение журнала (работа с группами погружений)</h2>
-<div class="sectionbody">
-<div class="sect2">
-<h3 id="_контекстное_меню_списка_погружений">7.1. Контекстное меню списка погружений</h3>
-<div class="paragraph"><p>Многие действия <em>Subsurface</em>, связанные с группами погружений, находятся в контекстном меню,
-которое вы можете вызвать, нажав правой кнопкой мыши на дайве или группе погружений.</p></div>
-<div class="imageblock" style="text-align:center;">
-<div class="content">
-<img src="images/ContextMenu.jpg" alt="Рисунок: Контекстное меню" />
-</div>
-</div>
-<div class="paragraph"><p>Это меню используется во многих сценариях, которые описаны ниже:</p></div>
-<div class="sect3">
-<h4 id="_выбор_колонок_списка_погружений">7.1.1. Выбор колонок списка погружений</h4>
-<div class="imageblock" style="text-align:left;">
-<div class="content">
-<img src="images/DiveListOptions.jpg" alt="Пример: Возможные колонки списка погружений" />
-</div>
-</div>
-<div class="paragraph"><p>По умолчанию в таблице <strong>списка погружений</strong> показывается следующая информация:
-номер, дата, рейтинг, глубина, длительность и местоположение. Вы можете
-изменить набор колонок, нажав правой кнопкой мыши на заголовке таблицы. Ниже
-приведен пример контекстного меню при нажатии правой кнопкой на заголовке
-<em>Дата</em>. Поставьте или удалите галочки чтобы показать или скрыть поля. <em>Subsurface</em>
-запоминает ваши предпочтения, так что при следующим запуске набор полей останется прежним.</p></div>
-</div>
-</div>
-<div class="sect2">
-<h3 id="S_Renumber">7.2. Перенумерация погружений</h3>
-<div class="paragraph"><p>Погружения обычно пронумерованы последовательно от более старых к более новым.
-Однако эта нумерация может быть нарушена. Например, при добавлении давних
-погружений, нумерация не будет последовательной, потому что существуют более
-поздние дайвы, нежели только что добавленные ранние погружения. В связи с этим
-вам может понадобиться перенумеровать погружения, для чего в главном меню
-выберите <em>Журнал → Перенумеровать</em>. Вам будет предоставлена возможность
-указать начальный номер, после чего погружения будут перенумерованы в
-соответствии с хронологическим порядком.</p></div>
-<div class="paragraph"><p>Вы также можете перенумеровать только избранные погружения. Для это выберите те, для которых
-необходимо изменить нумерацию. Щелкните правой кнопкой мыши на выделенных погружениях и используйте
-появившееся контекстное меню, чтобы выполнить перенумерацию. В появившемся окне вам будет необходимо
-указать начальный номер.</p></div>
-</div>
-<div class="sect2">
-<h3 id="S_Group">7.3. Группировка погружений и работа с поездками</h3>
-<div class="paragraph"><p>Если вы регулярно ныряете, журнал может очень быстро распухнуть. <em>Subsurface</em>
-позволяет группировать погружения в <em>поездки</em>. Это выполняется для погружений,
-у которых разрыв по времени не превышает двух дней. При этом для всех таких
-дайвов создается один заголовок в журнале. Ниже представлен несгруппированный
-список погружений (рисунок <strong>А</strong> слева) и тот же список,
-сгруппированный в пять поездок (рисунок <strong>В</strong> справа):</p></div>
-<div class="imageblock" style="text-align:center;">
-<div class="content">
-<img src="images/Group2.jpg" alt="Рисунок: Группировка погружений" />
-</div>
-</div>
-<div class="paragraph"><p>Группировка в поездки обеспечивает более быстрый доступ к отдельному
-погружения без необходимости просматривать длинный список. Для группировки
-погружений в главном меню выберите <em>Журнал → Авто-группировка</em>. Теперь список
-показывает только заголовки поездок.</p></div>
-<div class="sect3">
-<h4 id="_редактирование_поездки">7.3.1. Редактирование поездки</h4>
-<div class="paragraph"><p>Обычно в списке погружения для поездки показывается только ее название. Чтобы
-расширить эту информацию, выберите поездку в списке. после чего перейдите на
-вкладку <strong>Поездка</strong> в информационной панели. Здесь вы можете добавить информацию,
-касающуюся поездки в целом: дату и время, местоположение, название дайв-центра,
-погодные условия и т.п. Сохраните данные, нажав на кнопку <strong>Сохранить</strong> (на
-голубом фоне в верхней части панели).</p></div>
-</div>
-<div class="sect3">
-<h4 id="_просмотр_погружений_из_поездки">7.3.2. Просмотр погружений из поездки</h4>
-<div class="paragraph"><p>Чтобы получить доступ к индивидуальным погружения в группе, распахните поездку
-нажатием кнопки мыши на значок слева от названия поездки.</p></div>
-</div>
-<div class="sect3">
-<h4 id="_сворачивание_разворачивание_поездок">7.3.3. Сворачивание/разворачивание поездок</h4>
-<div class="paragraph"><p>При щелчке правой кнопкой мыши на поездке, контекстное меню предлагает
-несколько вариантов просмотра поездок: свернуть все, развернуть все, свернуть
-остальные кроме выбранной.</p></div>
-</div>
-<div class="sect3">
-<h4 id="_объединение_погружений_из_нескольких_поездок_в_одну">7.3.4. Объединение погружений из нескольких поездок в одну</h4>
-<div class="paragraph"><p>При щелчке правой кнопкой мыши на поездке, контекстное меню предлагает два
-варианта объединения поездок: объединить с поездкой выше или с поездкой ниже по
-списку.</p></div>
-</div>
-<div class="sect3">
-<h4 id="_разбиение_одной_поездки_на_несколько">7.3.5. Разбиение одной поездки на несколько</h4>
-<div class="paragraph"><p>Если, к примеру, поездка включает десять погружений, вы можете разбить ее на две
-(поездка 1: первые четыре дайва, поездка 2: оставшиеся 6 погружений), выделив первые
-четыре погружения в поездке и вызвав контекстное меню правой кнопкой мыши. В меню
-выберите пункт <strong>Создать поездку выше</strong>. Выбранные четыре погружения будут
-объединены в отдельную поездку. Рисунок ниже слева (А) иллюстрирует выбор погружений и
-контекстное меню, рисунок справа (Б) - погружения после разбиения:</p></div>
-<div class="imageblock" style="text-align:center;">
-<div class="content">
-<img src="images/SplitDive3a.jpg" alt="Рисунок: Разбиение поездки на две" />
-</div>
-</div>
-</div>
-</div>
-<div class="sect2">
-<h3 id="_работа_с_индивидуальными_погружениями">7.4. Работа с индивидуальными погружениями</h3>
-<div class="sect3">
-<h4 id="_удаление_погружения_из_журнала">7.4.1. Удаление погружения из журнала</h4>
-<div class="paragraph"><p>Вы можете навсегда удалить погружение из журнала, вызвав контекстное меню
-этого дайва и выбрав пункт <strong>Удалить</strong>. Вам может потребоваться это для удаления
-неверных погружений (калибровка дайв-компьютера, подбор грузов и т.п.)</p></div>
-</div>
-<div class="sect3">
-<h4 id="_удаление_погружения_из_поездки">7.4.2. Удаление погружения из поездки</h4>
-<div class="paragraph"><p>Чтобы удалить погружение из поездки, вызовите контекстное меню погружения
-щелчком правой кнопки мыши и выберите пункт <strong>Удалить из поездки</strong>. В списке это
-погружение окажется над поездкой из которой оно было удалено.</p></div>
-</div>
-<div class="sect3">
-<h4 id="_добавление_погружения_к_существующей_поездке">7.4.3. Добавление погружения к существующей поездке</h4>
-<div class="paragraph"><p>Несгруппированные погружения могут быть добавлены к уже существующим поездкам.
-В контекстном меню погружения(-й) выберите пункт <strong>Добавить к поездке
-сверху/снизу</strong>.</p></div>
-</div>
-<div class="sect3">
-<h4 id="_сдвиг_времени_начала_погружения">7.4.4. Сдвиг времени начала погружения</h4>
-<div class="paragraph"><p>Иногда вам может понадобиться изменить время начала погружения по причине
-разницы во времени между часовыми поясами или неверных установок часов
-дайв-компьютера. Для этого выделите одно или несколько погружений и в
-контекстном меню выберите пункт <strong>Сдвиг времени</strong>. В диалоговом окне вам
-необходимо указать величину сдвига в часах и минутах и направление.</p></div>
-</div>
-<div class="sect3">
-<h4 id="_объединение_нескольких_погружений_в_одно">7.4.5. Объединение нескольких погружений в одно</h4>
-<div class="paragraph"><p>Бывают ситуации, когда вы вынуждены прервать дайв и всплыть на поверхность на
-короткое время. Дайв-компьютер в этом случае может зарегистрировать это как
-два разных погружения. Вы можете объединить такие дайвы, выделив их и выбрав в
-контекстном меню пункт <strong>Объединить выбранные</strong>. После этого вам вероятнее все
-придется отредактировать данные объединенного погружения. Ниже приведен пример
-профиля такого объединенного погружения?</p></div>
-<div class="imageblock" style="text-align:center;">
-<div class="content">
-<img src="images/MergedDive.png" alt="Рисунок: Объединенное погружение" />
-</div>
-</div>
-</div>
-<div class="sect3">
-<h4 id="_отмена_манипуляций_с_погружением">7.4.6. Отмена манипуляций с погружением</h4>
-<div class="paragraph"><p>Критичные действия с погружениями или поездками, описанные выше, могут быть отменены либо
-выполнены повторно. Эти действия включают: <em>удаление погружений</em>, <em>объединение погружений</em> и
-<em>сдвиг времени погружения</em>. Для отмены или повторного выполнения операции выберите в <strong>Главном меню</strong>
-пункт <strong>Редактировать</strong> и в нем соответствующее действие.</p></div>
-</div>
-</div>
-<div class="sect2">
-<h3 id="S_Filter">7.5. Фильтрация списка погружений</h3>
-<div class="paragraph"><p>Вы можете отфильтровать погружения в списке, указав те или иные атрибуты дайва (метки, напарник,
-место погружения, костюм). Например, можно выбрать все глубокие погружения в определенном месте,
-либо пещерные дайвы с вашим другом.</p></div>
-<div class="paragraph"><p>Чтобы вызвать фильтр, выберите в главном меню <em>Журнал → Фильтр погружений</em>. Вам будет представлена
-<em>Панель фильтров</em>, расположенная в верхней части окна <em>Subsurface</em>. В правой части этой панели
-находятся три кнопки, которые позволяют очистить фильтры, спрятать панель или вовсе закрыть ее (при
-этом фильтры очищаются).</p></div>
-<div class="imageblock" style="text-align:center;">
-<div class="content">
-<img src="images/Filterpanel.jpg" alt="Рисунок: Панель фильтров" />
-</div>
-</div>
-<div class="paragraph"><p>Для фильтрации списка погружений используются четыре критерия: метки, люди (партнеры и инструктор),
-места погружений и костюм. Эти критерии представлены в виде списка значений с галочками. Помимо этого,
-над каждым списком находится поле вспомогательного фильтра, которое позволяет быстро найти значения
-в списке.</p></div>
-<div class="paragraph"><p>Эти четыре фильтра объединены логическим оператором <em>И</em>, однако значения в отдельно взятом фильтре
-объединены логическим оператором <em>ИЛИ</em>. Например, вы можете отфильтровать погружения следующим
-образом: <em>пещерное</em> ИЛИ <em>рэк</em>, где партнером был Василий.</p></div>
-</div>
-</div>
-</div>
-<div class="sect1">
-<h2 id="S_ExportLog">8. Экспорт всего или части журнала</h2>
-<div class="sectionbody">
-<div class="paragraph"><p>Существует два варианта экспорта погружений из <em>Subsurface</em>:</p></div>
-<div class="ulist"><ul>
-<li>
-<p>
-Экспорт информации о погружении в <em>Facebook</em>
-</p>
-</li>
-<li>
-<p>
-<a href="#S_Export_other">Экспорт данных погружения в другие форматы</a>
-</p>
-</li>
-</ul></div>
-<div class="sect2">
-<h3 id="S_facebook">8.1. Экспорт информации о погружении в <em>Facebook</em></h3>
-<div class="paragraph"><p>Экспорт в <em>Facebook</em> отличается от всех других видов экспорта, поскольку он требует подключения
-учетной записи, что в свою очередь требует от вас логин и пароль <em>Facebook</em>. Для авторизации
-необходимо в главном меню выбрать <em>Файл → Настройки</em> и там выбрать вкладку <em>Facebook</em>, на которой
-вам будет представлена форма авторизации (см. рисунок <strong>А</strong> слева внизу). Авторизуйтесь своими логином
-и паролем, после чего экран должен выглядеть как показано на рисунке <strong>В</strong>. При необходимости вы
-можете отключить <em>Subsurface</em> от <em>Facebook</em>, нажав на соответствующую кнопку.</p></div>
-<div class="imageblock" style="text-align:center;">
-<div class="content">
-<img src="images/facebook1_f20.jpg" alt="Рисунок: Авторизация Facebook" />
-</div>
-</div>
-<div class="paragraph"><p>После того как соединение с <em>Facebook</em> установлено, публикация профиля погружения в вашей Хронике не
-составит проблем. Выберите погружение в списке и убедитесь в том, что именно этот дайв должен быть
-опубликован. Нажмите кнопку с логотипом <em>Facebook</em>, расположенную в <strong>Информационной панели</strong> справа
-от поля <em>Примечания</em> (см. рисунок <strong>А</strong> ниже). По нажатию на эту кнопку вам будет представлено окно, в
-котором вы можете выбрать какую дополнительную информацию опубликовать вместе с профилем погружения
-(рисунок <strong>В</strong>). Обязательным является только поле <em>Альбом</em>. Кроме указания стандартных параметров
-погружения, вы можете вручную отредактировать сопроводительный текст. Для отправки профиля
-погружения в вашу Хронику <em>Facebook</em> нажмите кнопку <em>ОК</em>. Спустя короткое время вы должны получить
-подтверждение, что запись опубликована.</p></div>
-<div class="paragraph"><p>Созданный альбом и запись в хронике по умолчанию будут доступны только вам. Для того, чтобы ваши
-друзья смогли увидеть эти записи, вам необходимо изменить настройки безопасности приложений,
-войдя в <em>Facebook</em> с помощью обычного броузера или приложения <em>Facebook</em>. Возможно это и является
-некоторым неудобством, но разработчики придерживаются мнения, что такой дополнительный шаг позволит
-избежать нежелательных записей в вашей Хронике.</p></div>
-<div class="imageblock" style="text-align:center;">
-<div class="content">
-<img src="images/facebook2_f20.jpg" alt="Рисунок: Авторизация в Facebook" />
-</div>
-</div>
-<div class="paragraph"><p>Разорвать соединение с <em>Facebook</em> можно из <strong>Настроек</strong> приложения, либо просто закрыв <em>Subsurface</em>.</p></div>
-</div>
-<div class="sect2">
-<h3 id="S_Export_other">8.2. Экспорт данных погружения в другие форматы</h3>
-<div class="paragraph"><p>Функция экспорта доступна через главное меню <em>Файл → Экспорт</em>. Диалог
-экспорта всегда предлагает два варианта: все погружения или только те, что выбраны в
-<strong>Списке погружений</strong>. Выберите соответствующий пункт (см. рисунок ниже):</p></div>
-<div class="imageblock" style="text-align:center;">
-<div class="content">
-<img src="images/Export_f20.jpg" alt="Рисунок: Диалог экспорта" />
-</div>
-</div>
-<div class="paragraph"><p>Журнал или его часть могут быть сохранены в нескольких форматах:</p></div>
-<div class="ulist"><ul>
-<li>
-<p>
-Внутренний формат <em>Subsurface</em> XML
-</p>
-</li>
-<li>
-<p>
-Универсальный формат данных погружений (<em>UDDF</em>). Более полную информацию
-можно найти на сайте <em>http://uddf.org</em>. UDDF используется для обмена данными
-между дайв-компьютерами и программами.
-</p>
-</li>
-<li>
-<p>
-<em>Divelogs.de</em>, интернет-сервис для ведения журнала погружений. Вам
-необходимо зарегистрироваться на сайте и получить логин и пароль, чтобы
-воспользоваться этим сервисом.
-</p>
-</li>
-<li>
-<p>
-<em>DiveShare</em>, также интернет-сервис для хранения и обмена информацией о рекреационными
- погружениях. Для выгрузки данных в этот сервис нужен идентификатор пользователя, поэтому
- вам придется зарегистрироваться на сайте <em>http://scubadiveshare.com</em>.
-</p>
-</li>
-<li>
-<p>
-<em>Погружение в формате _CSV</em>, который включает только наиболее важную информацию о
-погружении: номер, дату, время, длительность, глубину, температуру и давление, т.е. большую
-часть того, что обычно записывается в бумажном журнале.
-</p>
-</li>
-<li>
-<p>
-<em>Профиль а формате _CSV</em>, который включает в себя множество информации, включая профиль
-глубины, показатели температуры и давления для каждого погружения.
-</p>
-</li>
-<li>
-<p>
-<em>HTML</em> формат. Журнал хранится в HTML-файлах, которые можно просмотреть с
-помощью интернет-браузера. Поддерживаются большинство современных браузеров, но
-обязательно должна быть включена поддержка Javascript. Предполагается, что вы
-не будете редактировать эти файлы. HTML-журнал содержит максимум информации и
-позволяет выполнять поиск в журнале. Этот вариант экспорта доступен на вкладке
-HTML (см. рисунок <strong>В</strong> выше). Вы можете выгрузить эти данные на смартфон или планшет и использовать
-как переносимый журнал для подтверждения своей квалификации в дайв-центре, если они захотят
-посмотреть вашу историю погружений.
-</p>
-</li>
-<li>
-<p>
-<em>Карта мира</em>. Это HTML файл, погружения отображаются на карте мира с
-минимальной информацией о погружении. Этот формат нельзя отредактировать.
-</p>
-</li>
-</ul></div>
-<div class="imageblock" style="text-align:center;">
-<div class="content">
-<img src="images/mapview_f20.jpg" alt="Рисунок: Погружения на карте мира" />
-</div>
-</div>
-<div class="ulist"><ul>
-<li>
-<p>
-<em>Глубины фото</em>. Создает текстовый файл, в котором содержатся имена файлов всех фотографий,
-прикрепленных к погружениям вместе с указанием глубины, на которой эти фотографии были сделаны.
-</p>
-</li>
-<li>
-<p>
-<em>Общие настройки</em> на вкладке HTML позволяет указать:
-</p>
-<div class="ulist"><ul>
-<li>
-<p>
-Нумерация Subsurface: если выбран этот параметр, то номера погружений будут
- выбираться из <em>Subsurface</em>, иначе дайвы будут пронумерованы начиная с 1.
-</p>
-</li>
-<li>
-<p>
-Статистика за год: если выбран этот параметр, в экспорт будет также включена статистика
- погружений по годам.
-</p>
-</li>
-<li>
-<p>
-Только список: будет экспортирован только список погружений, а
- дополнительная информация не будет доступна.
-</p>
-</li>
-</ul></div>
-</li>
-<li>
-<p>
-Группа <em>Настройки стиля</em> позволяют настроить внешнее оформление экспорта (шрифты и тему).
-</p>
-</li>
-</ul></div>
-<div class="paragraph"><p>Экспорт в другие форматы можно выполнить с помощью сторонних сервисов, таких
-как <em>www.divelogs.de</em>.</p></div>
-</div>
-</div>
-</div>
-<div class="sect1">
-<h2 id="S_Cloud_access">9. Хранение журнала <em>Subsurface</em> в облаке</h2>
-<div class="sectionbody">
-<div class="paragraph"><p>Журнал погружений важен для каждого дайвера. Вы ведете учет погружений не
-только для своего удовольствия, он необходим для дальнейшего прохождения
-курсов, а иногда в некоторых дайв-центрах. Поэтому вы должны обеспечить
-сохранность журнала. На случай выхода из строя жесткого диска вашего
-компьютера, кражи и утери оборудования, хранение в облаке - первое что приходит
-в голову. Еще один плюс - вы можете получить доступ к журналу в любой точке
-мира и вам не нужно иметь его с собой. Именно поэтому сервисы типа
-<em>divelogs.de</em> и <em>Diving Log</em> предлагают хранение журнала в Интернете.</p></div>
-<div class="paragraph"><p><em>Subsurface</em> предлашает встроенную поддержку облачного хранилища для всех своих
-пользователей. Сохранение и загрузка журнала погружений в облаке ничем не
-отличается от работы с жестким диском. От вас требуется только регистрация.
-Для использования облачного хранилища <em>Subsurface</em> необходимо выполнить
-следующие шаги:</p></div>
-<div class="sect2">
-<h3 id="_создание_учетной_записи_в_облаке">9.1. Создание учетной записи в облаке</h3>
-<div class="ulist"><ul>
-<li>
-<p>
-Перейдите в настройки сети (в <strong>Главном меню</strong> выберите <em>Файл</em> → <em>Настройки</em>
- → <em>Сеть</em>).
-</p>
-</li>
-<li>
-<p>
-В секции <em>Облачное хранилище Subsurface</em> укажите свой адрес электронной
- почты, который вы желаете использовать для регистрации.
-</p>
-</li>
-<li>
-<p>
-Укажите надежный пароль, который будет защищать ваш журнал в облаке.
-</p>
-</li>
-<li>
-<p>
-Нажмите кнопку <em>Применить</em>, чтобы отправить адрес почты и пароль на
- удаленный сервер в облаке. В ответ сервер пришлет вам PIN-код на указанный
- адрес (это <strong>единственный</strong> случай, когда <em>Subsurface</em> использует ваш адрес).
- Теперь в настройках сети появится поле PIN, которое ранее не было видно.
-</p>
-</li>
-<li>
-<p>
-ВВедите PIN-код в соответствующее текстовое поле (оно доступно только тогда,
- когда сервер ожидает подтверждения адреса электронной почты)
-</p>
-</li>
-<li>
-<p>
-Нажмите снова кнопку <em>Применить</em>. Ваша учетная запись будет отмечена
- как проверенная; облачное хранилище готово к работе.
-</p>
-</li>
-</ul></div>
-</div>
-<div class="sect2">
-<h3 id="_использование_облачного_хранилища">9.2. Использование облачного хранилища</h3>
-<div class="ulist"><ul>
-<li>
-<p>
-После успешной инициализации хранилища, в меню <em>Файл</em> появятся два новых пункта:
- <em>Открыть облачное хранилище</em> и <em>Сохранить в облаке</em>. Эти действия позволяют
- соответственно загрузить и сохранить журнал в облаке.
-</p>
-</li>
-<li>
-<p>
-в настройках приложения (вкладка <strong>Общие</strong>) вы можете выбрать опцию хранить журнал погружений
-по умолчанию в облаке. В этом случае <em>Subsurface</em> будет загружать журнал из облака при запуске
-и сохранять при выходе из программы.
-</p>
-</li>
-<li>
-<p>
-<em>Subsurface</em> хранит локальную копию облачного хранилища на жестком диске и позволяет вам
-работать с журналом даже при отсутствии Интернета. При подключении к Интернет ваши локальные
-изменения буду синхронизированы в облако.
-</p>
-</li>
-</ul></div>
-</div>
-<div class="sect2">
-<h3 id="S_Cloud_storage">9.3. Доступ из веб-браузера к облачному хранилищу <em>Subsurface</em></h3>
-<div class="paragraph"><p>Одним из преимуществ облачного хранилища является то, что вы можете получить доступ к данным
-вашего журнала погружений, используя обычный веб-браузер. Откройте ссылку
-<a href="https://cloud.subsurface-divelog.org"><em>https://cloud.subsurface-divelog.org</em></a>, введите свой
-адрес электронной почты и пароль, указанные при регистрации, и вы сможете просматривать журнал в
-HTML-формате (данные погружений последней синхронизации в облачное хранилище <em>Subsurface</em>).
-Информация о погружениях отображает только реальные данные из журнала, вычисляемые значения
-НЕ отображаются (давление в баллонах, деко-потолок, парциальные давления O<sub>2</sub>/He/N<sub>2</sub> и т.п.)</p></div>
-</div>
-<div class="sect2">
-<h3 id="_прочие_облачные_сервисы">9.4. Прочие облачные сервисы</h3>
-<div class="paragraph"><p>Если вы предпочитаете не использовать встроенное облачное хранилище
-<em>Subsurface</em> (и вам не нужен доступ к журналу из веб-браузера), то можно просто
-хранить журнал в облаке, используя другие облачные хранилища в Интернет.</p></div>
-<div class="paragraph"><p>Например, <a href="http://www.dropbox.com/"><em>Dropbox</em></a> предлагает приложение, которое
-позволяет видеть файлы на серверах Dropbox как локальные папки на вашем
-домашнем компьютере.</p></div>
-<div class="imageblock" style="text-align:center;">
-<div class="content">
-<img src="images/Cloud.jpg" alt="Рисунок: Папка Dropbox" />
-</div>
-</div>
-<div class="paragraph"><p>Программа <em>Dropbox</em> позволяет получить копию облачного интернет-хранилища на
-вашем компьютере. Когда компьютер подключен к Интернет, ваша локальная копия
-автоматически синхронизируется с облаком. При работе <em>Subsurface</em> операции
-открытия и сохранения выполняются с локальной копией и доступ в Интернет не
-нужен. Если локальная копия была изменена, например, вы добавили погружения,
-файлы в облаке будут автоматически обновлены как только появится соединение с
-Интернет.</p></div>
-<div class="paragraph"><p>Таким образом, журнал будет доступен из любой точки с доступом в
-Интернет. В настоящий момент эту услуга бесплатна. Программное обеспечение
-для Windows, Mac и Linux может быть загружено со
-<a href="http://www.dropbox.com/install"><em>страницы установки Dropbox</em></a>.
-Аналогично вы можете использовать <em>Dropbox</em> для хранения резервной копии
-журнала. Для этого в главном меню выберите <em>Файл → Сохранить как</em> и сохраните
-копию журнала в папку <em>Dropbox</em>. Чтобы открыть копию журнала, хранящегося в
-облаке, выберите в главном меню <em>Файл → Открыть журнал</em>, перейдите в папку
-<em>Dropbox</em> и укажите необходимый файл.</p></div>
-<div class="paragraph"><p>Существуют и другие платные и бесплатные схожие сервисы (Google, Amazon),
-которые вы можете использовать для хранения журнала в облаке.</p></div>
-</div>
-</div>
-</div>
-<div class="sect1">
-<h2 id="S_PrintDivelog">10. Печать журнала погружений</h2>
-<div class="sectionbody">
-<div class="paragraph"><p><em>Subsurface</em> предоставляет простой интерфейс для печати всего журнала или только выбранных погружений, включая профиль и сопутствующую информацию.
-Поставляемые или собственные шаблоны определяют как данные погружения расположены на странице.</p></div>
-<div class="paragraph"><p>Перед печатью вам нужно определиться с двумя вещами:</p></div>
-<div class="ulist"><ul>
-<li>
-<p>
-Нужно ли печатать весь журнал или только его часть? Если нужно распечатать
-только часть погружений, выделите эти дайвы с списке.
-</p>
-</li>
-<li>
-<p>
-Для каких газов нужно печатать графики парциального давления? Выберите
-соответствующие переключатели на панели слева от профиля.
-</p>
-</li>
-</ul></div>
-<div class="paragraph"><p>Теперь укажите параметры печати. Для этого в главном меню выберите <em>Файл → Print</em>.
-Вам будет представлено диалоговое окно (см. рисунок <strong>А</strong> ниже). Вам необходимо определиться с тремя параметрами:</p></div>
-<div class="imageblock" style="text-align:center;">
-<div class="content">
-<img src="images/Print1_f22.jpg" alt="Рисунок: Диалог печати" />
-</div>
-</div>
-<div class="olist arabic"><ol class="arabic">
-<li>
-<p>
-В секции <em>Варианты печати</em> выберите один из пунктов:
-</p>
-<div class="ulist"><ul>
-<li>
-<p>
-<em>Печать погружений</em>: печать погружений из списка с профилем и другой информацией.
-</p>
-</li>
-<li>
-<p>
-<em>Печать статистики</em>: печать статистики погружений по годам и месяцам.
-</p>
-</li>
-</ul></div>
-</li>
-<li>
-<p>
-В секции <em>Параметры печати</em> выберите:
-</p>
-<div class="ulist"><ul>
-<li>
-<p>
-Печать только выбранных погружений из списка. Если этот параметр не выбран,
- будут распечатаны все погружения из журнала.
-</p>
-</li>
-<li>
-<p>
-Параметр <em>Цветная печать</em> указывает будет ли печать цветной или монохромной.
-</p>
-</li>
-</ul></div>
-</li>
-<li>
-<p>
-В секции <em>Шаблон</em> выберите вариант расположения информации на странице. В штатной поставке
-вам предлагается несколько шаблонов (см. Рисунок В выше).
-</p>
-<div class="ulist"><ul>
-<li>
-<p>
-<em>Table</em>: Печать сводной таблицы погружений (картинка ниже).
-</p>
-</li>
-</ul></div>
-</li>
-</ol></div>
-<div class="imageblock" style="text-align:center;">
-<div class="content">
-<img src="images/Print_summarylist_f22.jpg" alt="Рисунок: Печать сводной таблицы" />
-</div>
-</div>
-<div class="ulist"><ul>
-<li>
-<p>
-<em>Flow layout</em>: Печать данных погружений без профилей:
-</p>
-</li>
-</ul></div>
-<div class="imageblock" style="text-align:center;">
-<div class="content">
-<img src="images/Print_flow_layout_f22.jpg" alt="Рисунок: Печать погружений без профиля" />
-</div>
-</div>
-<div class="ulist"><ul>
-<li>
-<p>
-<em>One Dive</em>: Печать одного погружения на странице вместе с профилем:
-</p>
-</li>
-</ul></div>
-<div class="imageblock" style="text-align:center;">
-<div class="content">
-<img src="images/print2_f22.jpg" alt="Рисунок: Печать одно погружение на странице" />
-</div>
-</div>
-<div class="ulist"><ul>
-<li>
-<p>
-<em>Two Dives</em>: Печать двух погружений на странице вместе с профилями
-</p>
-</li>
-<li>
-<p>
-<em>Six Dives</em>: Печать шести погружений на странице вместе с профилями
-</p>
-</li>
-</ul></div>
-<div class="paragraph"><p>Вы можете предварительно оценить результат печати, нажав на кнопку <em>Просмотр</em>.
-При необходимости поменяйте параметры печати, чтобы добиться желаемого
-результата.</p></div>
-<div class="paragraph"><p>Нажатие на кнопку <em>Печать</em> вызовет стандартный для вашей операционной системы диалог печати,
-в котором вы можете выбрать принтер и установить параметры для него:</p></div>
-<div class="imageblock" style="text-align:center;">
-<div class="content">
-<img src="images/Print_print_f22.jpg" alt="Рисунок: Системный диалог печати" />
-</div>
-</div>
-<div class="paragraph"><p>Установите требуемое разрешение печати и другие параметры и нажмите кнопку <em>Печать</em>. На картинке
-ниже показан пример одного из вариантов печати:</p></div>
-<div class="imageblock" style="text-align:center;">
-<div class="content">
-<img src="images/Printpreview.jpg" alt="Рисунок: Предварительный просмотр результа печати" />
-</div>
-</div>
-<div class="sect2">
-<h3 id="_создание_собственных_шаблонов_печати">10.1. Создание собственных шаблонов печати</h3>
-<div class="paragraph"><p>Собственные шаблоны позволяют вам максимально гибко настроить расположение данных погружения на странице. <em>Subsurface</em> использует HTML для разметки
-шаблонов. С помощью соответствующих кнопок, расположенных под списком шаблонов, вы можете редактировать, удалять, импортировать и экспортировать шаблоны. В
-<a href="#S_APPENDIX_E">ПРИЛОЖЕНИИ Д</a> вы сможете найти информацию о том, как создавать и редактировать шаблоны.</p></div>
-</div>
-</div>
-</div>
-<div class="sect1">
-<h2 id="S_Configure">11. Конфигурация дайв-компьютера</h2>
-<div class="sectionbody">
-<div class="paragraph"><p><em>Subsurface</em> предоставляет возможность конфигурации дайв-компьютеров. В настоящий момент поддерживаются
-компьютеры производства Heinrichs-Weikamp (OSTC 2 и OSTC 3) и семейство Suunto Vyper (Stinger, Mosquito,
-D3, Vyper, Vytec, Cobra, Gekko И Zoop). Множество параметров компьютера может быть считано и изменено.
-Первым шагом вы должны убедиться что установлены все необходимые драйверы оборудования и что вам известно
-имя устройства. Внимательно ознакомьтесь с информацией в <a href="#APPENDIX_A">ПРИЛОЖЕНИИ А</a>.</p></div>
-<div class="paragraph"><p>После того, как дайв-компьютер подключен, выберите <em>Файл → Настройка дайв-компьютера</em> в главном меню.
-Укажите имя устройства в текстовом поле в верхней части окна, и выберите соответствующую модель
-дайв-компьютера в списке слева (см. рисунок ниже).</p></div>
-<div class="imageblock" style="text-align:center;">
-<div class="content">
-<img src="images/Configure_dc_f20.jpg" alt="Рисунок: Конфигурация дайв-компьютера" />
-</div>
-</div>
-<div class="paragraph"><p>Вы можете выполнить следующие действия, используя соответствующие кнопки:</p></div>
-<div class="ulist"><ul>
-<li>
-<p>
-<strong>Загрузить настройки</strong>. Загружает существующие параметры дайв-компьютера в <em>Subsurface</em>. Загруженные
- параметры отображаются на конфигурационной панели.
-</p>
-</li>
-<li>
-<p>
-<strong>Сохранить в устройстве</strong>. Сохраняет измененные параметры в дайв-компьютер.
-</p>
-</li>
-<li>
-<p>
-<strong>Резервная копия</strong>. Сохраняет резервную копию настроек. <em>Subsurface</em> запросит директорию и имя
- файла.
-</p>
-</li>
-<li>
-<p>
-<strong>Восстановить</strong>. Загружает настройки для дайв-компьютера из ранее сделанной резервной копии.
-</p>
-</li>
-<li>
-<p>
-<strong>Обновить прошивку</strong>. Если доступна новая версия прошивки, она будет загружена в дайв-компьютер.
-</p>
-</li>
-</ul></div>
-</div>
-</div>
-<div class="sect1">
-<h2 id="S_Preferences">12. Настройки пользователя <em>Subsurface</em></h2>
-<div class="sectionbody">
-<div class="paragraph"><p>Вы можете настроить <em>Subsurface</em> для своих нужд, используя пункт главного меню
-<em>Файл → Настройки</em>. Настройки программы разделены на семь групп: <strong>Общие</strong>.
-<strong>Единицы</strong>, <strong>Профиль</strong>, <strong>Язык</strong> и <strong>Сеть</strong>, <strong>Facebook</strong> и <strong>Геопривязка</strong>. Выберите
-соответствующий раздел в левой части, внесите необходимые изменения ик нажмите
-кнопку <strong>Применить</strong>, чтобы сохранить настройки. Чтобы закрыть диалог настроек,
-нажмите кнопку <strong>ОК</strong>. Вы также можете закрыть окно настроек без сохранения.</p></div>
-<div class="sect2">
-<h3 id="_общие">12.1. Общие</h3>
-<div class="paragraph"><p>В этой группе доступны следующие настройки:</p></div>
-<div class="imageblock" style="text-align:center;">
-<div class="content">
-<img src="images/Pref1_f20.jpg" alt="Рисунок: Общие настройки" />
-</div>
-</div>
-<div class="ulist"><ul>
-<li>
-<p>
-<strong>Списки и таблицы</strong>: тут вы можете указать шрифт и его размер для списка
- погружений. Уменьшите размер шрифта, чтобы в списке помещалось больше дайвов.
-</p>
-</li>
-<li>
-<p>
-<strong>Погружения</strong>: укажите папку и имя файла с расширением <em>.xml</em> или <em>.ssrf</em>. При запуске
- <em>Subsurface</em> будет автоматически открывать этот журнал. Вам предоставляется три варианта:
-</p>
-<div class="ulist"><ul>
-<li>
-<p>
-<em>Отсутствует</em>: <em>Subsurface</em> автоматически не загружает журнал при запуске
-</p>
-</li>
-<li>
-<p>
-<em>Локальный файл</em>: Автоматически загружать журнал из локального файла при запуске.
-</p>
-</li>
-<li>
-<p>
-<em>Файл в облаке</em>: При старте журнал загружается из облачного хранилища (вам нужно настроить
- доступ на вкладке <strong>Сеть</strong>, это описано ниже).
-</p>
-</li>
-</ul></div>
-</li>
-<li>
-<p>
-<strong>Показывать ошибочные</strong>: Некоторые погружения могут быть помечены как
- ошибочные, например погружения в бассейне, но при этом вы не хотите удалять
- их из журнала. Этот параметр позволяет убрать такие дайва и списка.
-</p>
-</li>
-<li>
-<p>
-<strong>Баллон по умолчанию</strong>: укажите баллон, который будет использоваться по
- умолчанию на вкладке <strong>Снаряжение</strong>.
-</p>
-</li>
-<li>
-<p>
-<strong>Анимация</strong>: скорость анимации профиля при переключении между
- погружениями. Чем меньше значение, тем быстрее скорость. Значение 0
- полностью отключает анимацию.
-</p>
-</li>
-<li>
-<p>
-<strong>Сбросить все настройки</strong>: как следует из названия, эта кнопка сбрасывает
- все настройки в значение по умолчанию.
-</p>
-</li>
-</ul></div>
-</div>
-<div class="sect2">
-<h3 id="_единицы">12.2. Единицы</h3>
-<div class="imageblock" style="text-align:center;">
-<div class="content">
-<img src="images/Pref2_f20.jpg" alt="Рисунок: Настройки системы мер" />
-</div>
-</div>
-<div class="paragraph"><p>Здесь вы можете выбрать между имперской или метрической системой мер для
-единиц глубины, давления, объема, температуры и массы. Переключателями в
-верхней части вы выбираете системы мер для всех единиц сразу, либо выберите
-<strong>Настроить</strong> и укажите единицы для каждой величины по отдельности.</p></div>
-<div class="paragraph"><p>Независимо от вышеперечисленных настроек, вы можете указать единицы измерения
-времени (секунды или минуты). Координаты GPS могут быть представлены либо в
-традиционном формате (градусы, минуты, секунды) либо в десятичном.</p></div>
-</div>
-<div class="sect2">
-<h3 id="_профиль">12.3. Профиль</h3>
-<div class="imageblock" id="S_CCR_options" style="text-align:center;">
-<div class="content">
-<img src="images/Pref3_f20.jpg" alt="Рисунок: настройки профиля" />
-</div>
-</div>
-<div class="paragraph" id="S_GradientFactors"><p>В этой панели доступно две группы настроек:</p></div>
-<div class="ulist"><ul>
-<li>
-<p>
-<strong>Показывать</strong>: тут вы можете выбрать набор данных, отображаемых в профиле
-погружений:
-</p>
-<div class="ulist"><ul>
-<li>
-<p>
-<em>Пороговые значения</em>: <em>Subsurface</em> отображает на профиле погружения
-парциальные давления азота, кислорода и гелия. Вы можете включить их
-отображение с помощью кнопок-переключателей на слева от панели профиля.
-Для каждого их этих графиков вы можете указать пороговые значения, при
-превышении которых линия будет нарисована красным цветом.
-</p>
-</li>
-<li>
-<p>
-<em>Показывать потолок дайв-компьютера красным цветом</em>: Если дайв-компьютер
-записывает данные потолка, то вам может быть удобным различать его значения от
-тех, что посчитаны <em>Subsurface</em>. Зачастую эти значения различаются из-за
-разницы в алгоритмах, установках градиент-фактора и динамики расчет потолка.
-</p>
-</li>
-<li>
-<p>
-<em>Неиспользуемые баллоны</em>: следует ли отображать неиспользуемые баллоны в
-списке на вкладке Снаряжение.
-</p>
-</li>
-<li>
-<p>
-<em>Показывать среднюю глубину</em>: Если в этом поле стоит галочка, <em>Subsurface</em>
-будет показывать серой линией на профиле среднюю глубину погружения в конкретный момент времени.
-Обычно это линия имеет форму английской буквы U и отражает максимальную среднюю глубины непосредственно
-перед всплытием.
-</p>
-</li>
-</ul></div>
-</li>
-<li>
-<p>
-<strong>Разное</strong>:
-</p>
-<div class="ulist" id="S_GradientFactors"><ul>
-<li>
-<p>
-<em>Градиент фактор</em>: Значения GFLow для глубины и GFHigh для поверхности.
- Эти значения задают консерватизм азотной экспозиции во время погружения, так
- же, как вы настраиваете консерватизм вашего дайв-компьютера. Меньше значения
- градиент-фактора, тем консервативнее вычисления относительно азотного
- насыщения и тем глубже потолок всплытия. Установки 20/60 считаются достаточно
- консервативными, а значения 60/90 достаточно суровы. Если в поле <strong>GF Low на
- макс. глубине</strong> стоит галочка, значение нижнего градиент-фактора будет
- использоваться на максимальной глубине. В противном случае GF Low будет
- использоваться на всех глубинах ниже первой деко-остановки. Больше информации
- вы можете найти по ссылкам:
-</p>
-<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>
-</li>
-<li>
-<p>
-<em>CCR: показывать установки</em>. При выборе этого параметра, на графике pO<sub>2</sub>
- профиля погружения красной линией отображаются значения установок CCR (set-point).
- См. <a href="#S_CCR_dives">Погружения с ребризером закрытого цикла</a>.
-</p>
-</li>
-<li>
-<p>
-<em>CCR: индивидуальные значения сенсоров O<sub>2</sub></em>. Отображать показания отдельных кислородных
- датчиков ребризера замкнутого цикла на графике pO<sub>2</sub>.
- См. <a href="#S_CCR_dives">Погружения с ребризером закрытого цикла</a>.
-</p>
-</li>
-</ul></div>
-</li>
-<li>
-<p>
-<strong>Настройки для погружений с ребризером:</strong>
-</p>
-<div class="ulist"><ul>
-<li>
-<p>
-<em>Установка CCR для планировщика:</em> Укажите значение установки O<sub>2</sub> для планировщика. Она
- определяет начальную установку PO<sub>2</sub> для отдельно взятого погружения в его начале. Вы можете
- изменить значение установки через контекстное меню профиля погружения.
-</p>
-</li>
-<li>
-<p>
-<em>pSCR метаболизм O<sub>2</sub>:</em> Для ребризеров полузамкнутого цикла указывает объем кислорода,
- потребляемый дайвером в минуту. Установите это значение для планирования погружений с ребризером
- pSCR и для расчета декомпрессионных обязательств.
-</p>
-</li>
-<li>
-<p>
-<em>pSCR отношение сброса:</em> Отношение объема сброшенного газа к объему рециркулированного.
- Используется при планировании погружений на pSCR-оборудовании.
-</p>
-</li>
-</ul></div>
-</li>
-</ul></div>
-</div>
-<div class="sect2">
-<h3 id="_язык">12.4. Язык</h3>
-<div class="paragraph"><p>Тут вы можете выбрать язык интерфейса <em>Subsurface</em>.</p></div>
-<div class="imageblock" style="text-align:center;">
-<div class="content">
-<img src="images/Pref4_f20.jpg" alt="Рисунок: Настройки языка интерфейса" />
-</div>
-</div>
-<div class="paragraph"><p>Вы можете использовать системные настройки языка, что в большинстве случаев
-использует тот же язык, что и ваша операционная система. Если по какой-то
-причине вас это не устраивает, снимите галочку и выберите подходящий язык из
-списка. Вы можете использовать фильтр чтобы быстро найти нужный вам язык в
-списке. Смена языка требует перезапуска <em>Subsurface</em>.</p></div>
-</div>
-<div class="sect2">
-<h3 id="_сеть">12.5. Сеть</h3>
-<div class="paragraph"><p>Эти настройки обеспечивают связь <em>Subsurface</em> с различными источниками данных в Интернет. Они
-влияют на подключение к облачному хранилищу, импорт координат погружений из
-<a href="#S_Companion"><em>веб-сервиса Subsurface</em></a> и импорт/экспорт данных из <em>Divelogs.de</em>.
-Эти настройки зависят от вашего подключения и поставщика услуг Интернет, который должен предоставить
-вам необходимую информацию.</p></div>
-<div class="imageblock" style="text-align:center;">
-<div class="content">
-<img src="images/Pref5_f20.jpg" alt="Рисунок: Настройки сети" />
-</div>
-</div>
-<div class="paragraph"><p>Эта вкладка состоит из трех секций:</p></div>
-<div class="ulist"><ul>
-<li>
-<p>
-Прокси
-Если для соединения с Интернет используется прокси-сервер, вам необходимо выбрать его тип из
-выпадающего списка, после чего указать адрес и порт прокси-сервера. Если прокси-сервер требует
-авторизации, укажите имя пользователя и пароль. Обычно эту информацию предоставляет провайдер
-Интернет-услуг.
-</p>
-</li>
-<li>
-<p>
-<em>Облачное хранилище</em>: Для того, чтобы хранить журнал погружений в облаке, вам необходимо
- указать корректный адрес электронной почты и пароль. Это позволит <em>Subsurface</em> отправить вам
- PIN-код и подготовить хранилище. Дополнительно к этому вам предлагаются два параметра:
-</p>
-<div class="ulist"><ul>
-<li>
-<p>
-<em>Фоновая синхронизация</em> позволяет автоматически синхронизировать журнал в облако, в то время
- как вы выполняете другие задачи внутри <em>Subsurface</em>.
-</p>
-</li>
-<li>
-<p>
-<em>Локальное хранение пароля</em> сохраняет пароль на вашем компьютере. Обратите внимание, что
- пароль хранится в незашифрованном виде.
-</p>
-</li>
-</ul></div>
-</li>
-<li>
-<p>
-<em>Веб-сервис Subsurface</em>: при регистрации в <a href="#S_Companion">веб-сервисе <em>Subsurface</em></a>, вам
- генерируется длинный и труднозапоминаемый ключ. Этот ключ необходимо встравить в это поле.
- Поставьте галочку в поле <em>Сохранять ID пользователя</em>, чтобы сохранить этот ключ на вашем
- компьютере.
-</p>
-</li>
-</ul></div>
-</div>
-<div class="sect2">
-<h3 id="S_Facebook">12.6. Соединение с <em>Facebook</em></h3>
-<div class="paragraph"><p>Эта вкладка позволяет войти в <em>Facebook</em> для дальнейшей публикации погружений в этой социальной
-сети.</p></div>
-<div class="imageblock" style="text-align:center;">
-<div class="content">
-<img src="images/Pref6_f20.jpg" alt="Рисунок: Панель авторизации Facebook" />
-</div>
-</div>
-<div class="paragraph"><p>При указании корректных логина и пароля <em>Facebook</em> вы сможете публиковать профили погружений и
-комментарии к ним в своей хронике. Если вы закроете <em>Subsurface</em>, связь с <em>Facebook</em> будет
-разорвана. Параметр "Запомнить соединение с Subsurace" на текущий момент ни на что не влияет.
-См. подробнее в главе <a href="#S_facebook">Экспорт информации о погружении в <em>Facebook</em></a>.</p></div>
-</div>
-<div class="sect2">
-<h3 id="_геопоиск">12.7. Геопоиск</h3>
-<div class="paragraph"><p><em>Subsurface</em> предоставляет возможность геопоиска местоположений по GPS координатам (
-выбранным на карте, введенным вручную либо полученным из вспомогательного приложения)
-в Интернет. Очевидно, что эта функция работает только при наличии интернет-соединения.
-У вас есть возможно указаться формат названия дайв-сайта, например <em>Страна/Область/Город</em>
-(см. рисунок ниже).</p></div>
-<div class="imageblock" style="text-align:center;">
-<div class="content">
-<img src="images/Pref7_f20.jpg" alt="Рисунок: Настройки геопоиска" />
-</div>
-</div>
-</div>
-</div>
-</div>
-<div class="sect1">
-<h2 id="S_DivePlanner">13. Планировщик <em>Subsurface</em></h2>
-<div class="sectionbody">
-<div class="paragraph"><p>Планировщик погружений <em>Subsurface</em> доступен из главного меню <em>Журнал →
-Планировщик</em>. Расчеты азотного насыщения осуществляются по алгоритму Бюльмана
-ZH-L16 с добавлением градиент-факторов за авторством Эрика Бейкера.</p></div>
-<div class="sidebarblock">
-<div class="content">
-<div class="admonitionblock">
-<table><tr>
-<td class="icon">
-<img src="images/icons/warning2.png" alt="Внимание" />
-</td>
-<td class="content">Планировщик <em>Subsurface</em> ЯВЛЯЕТСЯ ЭКСПЕРИМЕНТАЛЬНЫМ и предполагает, что вы
-знакомы с пользовательским интерфейсом программы. Вы можете использовать
-планировщик только при условиях:</td>
-</tr></table>
-</div>
-<div class="ulist"><ul>
-<li>
-<p>
-Вы обучены планировать погружения и делали это ранее.
-</p>
-</li>
-<li>
-<p>
-План погружения находится в пределах ваших сертификатов.
-</p>
-</li>
-<li>
-<p>
-Планировщик делает расчеты для усредненного человека и не принимает во
-внимание ваши индивидуальные психологическое и физическое состояние и образ
-жизни.
-</p>
-</li>
-<li>
-<p>
-Безопасность плана очень зависит от того, как вы используете планировщик.
-</p>
-</li>
-<li>
-<p>
-Вы знакомы с пользовательским интерфейсом <em>Subsurface</em>.
-</p>
-</li>
-<li>
-<p>
-Если вы не уверены в выше изложенном, вам не следует
-использовать планировщик.
-</p>
-</li>
-</ul></div>
-</div></div>
-<div class="sect2">
-<h3 id="_экран_планировщика">13.1. Экран планировщика</h3>
-<div class="paragraph"><p>Как и журнал <em>Subsurface</em>, экран планировщика разделен на несколько областей
-(см. рисунок ниже). Установочные параметры плана задаются в левой части
-экрана. Эти параметры разделены на несколько групп: Доступные газы, Скорости, Планирование, Газы, Погружение.</p></div>
-<div class="paragraph"><p>В правой верхней части экрана находится профиль планируемого погружения,
-который можно менять только с помощью мыши. Это делает использование
-планировщика очень простым.</p></div>
-<div class="paragraph"><p>В правой нижней части экрана находится текстовая область <em>Детальный план
-погружения</em>. В ней показываются все детали плана и предупреждения.</p></div>
-<div class="imageblock" style="text-align:center;">
-<div class="content">
-<img src="images/PlannerWindow1_f20.jpg" alt="Рисунок: Начальные экран планировщика" />
-</div>
-</div>
-</div>
-<div class="sect2">
-<h3 id="_пример_планирования_погружения_на_открытом_цикле">13.2. Пример планирования погружения на открытом цикле</h3>
-<div class="ulist"><ul>
-<li>
-<p>
-В левой нижней части экрана планировщика расположен выпадающий список (на рисунке ниже обведен синей линией), предоставляющий варианта типа погружения:
-</p>
-<div class="ulist"><ul>
-<li>
-<p>
-Открытый цикл (по умолчанию)
-</p>
-</li>
-<li>
-<p>
-Ребризер замкнутого цикла (CCR)
-</p>
-</li>
-<li>
-<p>
-Пассивный ребризер полузамкнутого цикла (pSCR)
-</p>
-</li>
-</ul></div>
-</li>
-<li>
-<p>
-Выберите режим Открытого цикла.
-</p>
-</li>
-<li>
-<p>
-Удостоверьтесь, что начальные параметры погружения в верхней левой части
- экрана введены правильно. Они включают: начальные дата и время погружения,
- атмосферное давление в точке погружения. Давление может быть задано как
- высота в метрах над уровнем моря, считая атмосферное давление равным 1.013 бар.
-</p>
-</li>
-<li>
-<p>
-В таблице, озаглавленной <em>Доступные газы</em>, добавьте информацию об
- используемых баллонах и составах смесей. Сделать это можно таким же образом,
- как и в случае <a href="#cylinder_definitions">добавления баллонов к погружению</a>. Выберите
- тип баллона из выпадающего списка, укажите рабочее давление, Если поле
- процентного содержания кислорода (O<sub>2</sub>%) пустое, то эта смесь считается
- воздухом. В противном случае введите концентрацию кислорода/гелия.
- Дополнительные баллоны можно добавить нажатием на значок "+".
-</p>
-</li>
-<li>
-<p>
-Профиль планируемого погружения может быть создан двумя способами:
-</p>
-<div class="ulist"><ul>
-<li>
-<p>
-Перетаскивайте путевые точки (маленькие белые кружки), чтобы создать необходимый вам профиль.
- Дополнительные точки можно создать двойным щелчком мыши. Удалить точку можно правым щелчком мыши
- ней и выбрав пункт <em>Удалить эту точку</em> из появившегося контекстного меню.
-</p>
-</li>
-<li>
-<p>
-Наиболее эффективный способ создания профиля - ввод необходимых значений в таблицу,
- озаглавленную <em>Путевые точки плана</em>. Первая строка таблицы описывает время и глубину спуска с
- поверхности. Последующие сегменты описывают донную фазу погружения. Колонка <em>Установка CC</em> важна
- только для погружений с ребризером. Точки подъема обычно не указываются, поскольку именно их
- планировщик и должен рассчитать. Для добавления нового сегмента нажмите значок "+" в правом
- верхнем углу таблицы. Добавленные сегменты автоматически появляются на графике профиля погружения.
-</p>
-</li>
-</ul></div>
-</li>
-</ul></div>
-<div class="sect3">
-<h4 id="_рекреационные_погружения">13.2.1. Рекреационные погружения</h4>
-<div class="paragraph"><p>Планировщик <em>Subsurface</em> предлагает изощренный способ планирования рекреационных погружений, т.е.
-погружений в бездекомпрессионных пределах. Он также учитывает насыщение азотом после предыдущих
-погружений. Но традиционные таблицы тоже позволяют вести расчеты по остаточному азоту. Для чего
-тогда нужен планировщик в рекреационных дайвах? При использовании рекреационных таблиц во внимание
-принимается максимальная глубина погружения. Однако мало какие погружения выполняются на постоянной
-глубине, равной максимальной ("квадратный" профиль). Т.е. таблицы чересчур консервативны в отношении
-остаточного азота после предыдущих погружений. Планировщик <em>Subsurface</em> рассчитывает остаточное
-азотное насыщение исходя из реальных профилей ранее совершенных погружений также, как это делает
-дайв-компьютер во время погружения. Это означает, вы что получаете "кредит" в виде времени, не
-проведенного на максимальной глубине во время предыдущих погружений, и как следствие, более долгое
-время последующих погружений. Это также означает, что вы должны загрузить все предыдущие погружения
-в <em>Subsurface</em>, прежде чем пользоваться планировщиком.</p></div>
-<div class="paragraph"><p>Для планирования погружения вам необходимо указать параметры.</p></div>
-<div class="ulist"><ul>
-<li>
-<p>
-Убедитесь в правильности даты и времени планируемого погружения. Это позволит правильно вычислить
- остаточное насыщение азотом после предыдущих погружений.
-</p>
-</li>
-<li>
-<p>
-Сразу под заголовком <em>Планирование</em> поставьте галочки в полях <em>Рекреационный режим</em> и
- <em>Остановка безопасности</em>.
-</p>
-</li>
-<li>
-<p>
-Укажите объем баллонов, тип смеси (воздух или % кислорода) и начальное давление в таблице
- <em>Доступные смеси</em> в левой верхней части планировщика.
-</p>
-</li>
-<li>
-<p>
-Планировщик посчитает достаточно ли указанных газов для выполнения погружения. Для того, чтобы
- результат был реалистичным, в разделе <em>Газы</em> укажите ваш <em>SAC на дне</em>. Разумные значения лежат
- в интервале от 15 до 30л/мин (для новичков и сложных погружений ближе к 30л/мин)
-</p>
-</li>
-<li>
-<p>
-Укажите газовый резерв, который должен оставаться в баллоне в конце донной части погружения
- непосредственно перед подъемом. Зачастую это 50 бар. Этот резерв может понадобиться при всплытии
- случись необходимость поделиться воздухом с вашим партнером. Нельзя сколько точно газа может
- понадобиться, это зависит от глубины подъема и скорости. Поэтому большинство школ предусматривают
- фиксированный резерв равный 50 или 60 барам, или 25% или 33% (правило третей).
-</p>
-</li>
-<li>
-<p>
-Укажите глубину погружения, перетаскивая путевые точки на профиле или (что лучше) задавая
- необходимые глубины в таблице <em>Путевые точки плана</em>. Для многоуровневых погружений вы также можете
- добавить новые сегменты в таблицу или создать новые путевые точки непосредственно на профиле.
- <em>Subsurface</em> автоматически пересчитает донное время до максимального в рамках бездекомпрессионного
- предела (NDL).
-</p>
-</li>
-<li>
-<p>
-При необходимости измените скорость всплытия. Значения по умолчанию считаются безопасными для
- рекреационных дайверов.
-</p>
-</li>
-</ul></div>
-<div class="paragraph"><p>Профиль в планировщике погружений отражает максимальное время погружения в бездекомпрессионных
-пределах согласно алгоритму Бюльмана ZH-L16, а также параметрам газа и глубины, как описано выше.
-<em>Subsurface</em> позволяет быстро оценить длительность погружения как функцию глубины, учитывая
-азотное насыщение после предыдущих дайвов. План также включает оценку расхода газов исходя из
-установок в таблице <em>Доступные смеси</em>. Если начальное давление в баллоне установлено в 0, то
-отображаемое время погружения является истинным NDL без учета используемой смеси. Если профиль
-погружения отображается КРАСНЫМ цветом, это означает, что превышены рекреационные пределы и либо
-глубина, либо время должны уменьшены.</p></div>
-<div class="paragraph"><p>На рисунке ниже приведен план рекреационного погружения на 30 метров. Несмотря на то, что бездекомрпессионный
-предел (NDL) составляет 23 минуты, время погружения ограничено количеством воздуха. Текст в правой
-нижней части экрана сообщает о том, что необходим запас воздуха для поддержки партнера при всплытии.</p></div>
-<div class="imageblock" style="text-align:center;">
-<div class="content">
-<img src="images/rec_diveplan.jpg" alt="Рисунок: План рекреационного погружения" />
-</div>
-</div>
-</div>
-<div class="sect3">
-<h4 id="_нерекреационные_погружения_на_открытом_цикле_включая_декомпрессию">13.2.2. Нерекреационные погружения на открытом цикле, включая декомпрессию</h4>
-<div class="paragraph"><p>Нерекреационные погружения подразумевают превышение бездекомпрессионных пределов и/или использование
-нескольких дыхательный смесей. Планирование таких погружение состоит из трех фаз:</p></div>
-<div class="paragraph"><p><strong>а) Управление азотом</strong>: включает в себя указание скоростей спуска и всплытия, а
-также деко-модели (GFLow, GFHigh или степень консерватизма) в секциях <em>Скорость</em>
-и <em>Планирование</em> в левой нижней части экрана. Выберите одну из двух поддерживаемых
-деко-моделей: Бюльман или VPM-B. Для модели Бюльмана необходимо указать градиент-факторы
-(GFLow и GFHigh). Изначально значения GFLow и GFHigh берутся из настроек <em>Subsurface</em>,
-однако, если вы их поменяли в планировщике, значения по умолчанию в настройках не
-затрагиваются. Значения градиент-фактора влияют на расчет потолка и его глубину.
-Слишком низкие значения GFLow ведут к ранним и более глубоким деко-остановкам.
- ** Подробнее читайте в <a href="#S_GradientFactors">настройках градиент-фактора</a> и внешних источниках:</p></div>
-<div class="paragraph"><p>При выборе VPM-B модели необходимо указать уровень консерватизма в диапазоне от 0 (наименее
-консервативный) до 4 (наиболее консервативный). Эта модель обычно предлагает более глубокие
-остановки и зачастую делает погружения немного короче по сравнению с моделью Бюльмана. При выборе
-этих моделей помните, что это не реальные физиологические, а математические модели, которые
-похоже работают на практике.</p></div>
-<div class="paragraph"><p>Вы можете найти больше информации во внешних источниках:</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&ie=UTF8&qid=1403932320&sr=1-1&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.
-Превосходный обзор декомпрессионных моделей Бюльмана и VPM-B.
-</p>
-</li>
-</ul></div>
-<div class="paragraph"><p>Скорость всплытия важна в фазе рассыщения в конце дайва и указывается для
-нескольких диапазонов глубины, принимая во внимание среднюю глубину как точку
-отсчета. Средняя глубина отображается на профиле красной горизонтальной линией.
-Скорость всплытия на больших глубинах находится обычно в пределах 8-12 м/мин,
-в то время, как возле поверхности она обычно составляет 4-9 м/мин. Скорость
-спуска также указывается. Если установлен флажок <em>Падение к первой глубине</em>,
-то в фазе спуска будет использоваться максимальная скорость, указанная в секции <em>Скорости</em>.</p></div>
-<div class="paragraph"><p><strong>б) Управление кислородом</strong>: в секции <em>Газы</em> необходимо указать максимальное
-парциальное давление кислорода в донной фазе (<em>pO₂ на дне</em>) и во время
-декомпрессионных остановок (<em>pO₂ на деко</em>). Обычно используются значения
-1.4 и 1.6 бар соответственно, и парциальное давление 1.6 бар является
-максимально допустимым. Настройки pO₂ и глубина замены смеси могут быть также
-отредактированы в секции <em>Доступные смеси</em>. Обычно планировщик принимает
-решение о переключении на новую смесь, когда при подъеме парциальное давление
-кислорода в этой смеси опускается ниже значения 1.6 бар.</p></div>
-<div class="paragraph"><p><strong>в) Управление расходом газов:</strong> Вам необходимо контролировать и учитывать
-объем доступных газов, чтобы безопасно вернуться на поверхность,и , возможно,
-поделиться с напарником. В секции <em>Газы</em> укажите ваш лучший (но при этом
-достаточно консервативный) поверхностный расход воздуха (SAC, иногда именуемый
-RMV) в л/мин (в настоящий момент используется только метрическая система). Укажите
-SAC отдельно для донной фазы (<em>SAC на дне</em>) и для остановок декомпрессии (<em>SAC
-на деко</em>). Обычно это значения находятся в пределах 20-30 л/мин. Для более
-точного управления расходом газов не нужно строить догадки, регулярно
-контролируйте свой SAC, погружаясь в разных условиях и с разным снаряжением.
-Планировщик рассчитывает общий расход газов за все время погружения и выдаст
-предупреждение если расход превысит доступный объем газов. Для вашей
-безопасности всегда оставляйте резерв газов на случай непредвиденных обстоятельств.
-В техническом дайвинге такой резерв может составлять до 66% от общего объема газов.</p></div>
-<div class="paragraph"><p>И, наконец, вы можете приступить к планированию времени и глубины
-погружения. Для этого <em>Subsurface</em> предоставляет уникальный графический
-интерфейс. Принцип его работы такой же, как при ручном добавлении погружения в
-журнал. После активации планировщика вам будет предложен начальный профиль
-погружения на 15 м в течение 40 минут. Путевый точки можно перетаскивать
-мышью или с помощью стрелок клавиатуры, Для создания новой точки, дважды
-щелкните на линии сегмента. При превышении какого-либо предела (парциальное
-давление, объем), <em>Subsurface</em> изменит цвет фона профиля с
-ГОЛУБОГО на КРАСНЫЙ.</p></div>
-<div class="paragraph"><p>Каждая путевая точка на профиле создает запись в таблице <em>Путевые точки
-плана</em> в левой части экрана. Проверьте, чтобы значение в колонке <em>Используемый
-газ</em> соответствовало одной из смесей, указанных в таблице <em>Доступные смеси</em>.
-Добавьте необходимые путевые точки с тем, чтобы профиль соответствовал вашему
-плану, т.е. присутствовал донная фаза, глубокие остановки (если планируются).
-Путевые точки всплытия <em>Subsurface</em> расставит сам с учетом декомпрессионных
-обязательств.
-Путевые точки можно двигать с помощью мыши или стрелок на клавиатуре.
-Точки можно редактировать и создавать непосредственно в таблице
-<em>Путевые точки плана</em>. На самом деле, вы можете спланировать погружение
-пользуясь только этой таблицей.</p></div>
-<div class="paragraph"><p>Укажите замену баллонов/смесей так же, как это делается в случае
-<a href="#S_CreateProfile">ручного создания профиля погружения</a>. События замены смесей
-должны соответствовать баллонам и смесям из таблицы <em>Доступные смеси</em>. При
-наличии нескольких смесей, <em>Subsurface</em> будет автоматически предлагать замену,
-однако вы можете удалить и добавить событие самостоятельно, вызвав контекстное
-меню точки правым щелчком мыши.</p></div>
-<div class="paragraph"><p>Ненулевое значение в колонке "Установка СС" в таблице путевых точек означает корректное значение
-установки и что погружение на этом сегменте выполняется на CCR-ребризере. Если последний вручную
-введенный сегмент выполняется на CCR, декомпрессионные процедуры рассчитываются согласно значения
-указанной установки. Если же последний сегмент выполняется на открытом цикле (значение установки кислорода
-равно нулю), декомпрессионные обязательства рассчитываются в режиме ОЦ. Замена газов предусмотрена
-только для открытого цикла.</p></div>
-<div class="paragraph"><p>Ниже на рисунке приведен пример плана погружения на 45м с использованием EAN26
-и всплытием на EAN50, используя настройки, описанные выше:</p></div>
-<div class="imageblock" style="text-align:center;">
-<div class="content">
-<img src="images/DivePlanner2_f20.jpg" alt="Рисунок: Планирование погружения: настройки" />
-</div>
-</div>
-<div class="paragraph"><p>После окончания планирование, вы можете сохранить план, нажав на кнопку
-<em>Сохранить</em>. План появится в списке погружений.</p></div>
-<div class="paragraph"><p><strong>Детальный план погружения</strong></p></div>
-<div class="paragraph"><p>В правой нижней части экрана планировщика находится текстовая область с
-подробным словесным описанием плана погружения. Вы можете изменить его
-детализацию с помощью нескольких параметров в секции <em>Заметки погружения</em>.
-Если выбран пункт <em>Подробный план</em>, описание будет достаточно многословным.
-При превышении каких-либо пределов в нижней части будет выведено
-предупреждение.</p></div>
-<div class="paragraph"><p>При выборе пункта <em>Показать время сегмента</em>, план будет отображать время на
-каждой отдельно взятой глубине. Время сегмента ВКЛЮЧАЕТ время, необходимое чтобы
-перейти к заданной глубине. Однако, если выбран параметр <em>Показать переходы в
-деко</em>, то время переходом показывается отдельно от времени сегментов.</p></div>
-</div>
-</div>
-<div class="sect2">
-<h3 id="_планирование_погружений_на_ребризере_полузамкнутого_типа">13.3. Планирование погружений на ребризере полузамкнутого типа</h3>
-<div class="paragraph"><p>Для планирования таких погружений выберите pSCR в списке, как показано на рисунке выше (список
-обведен синей линией).
-Параметры pSCR-погружений также задаются в *Настройках* (в главном меню выберите <em>Файл → Настройки</em>
-и вкладку <em>Профиль</em>). К этим настройкам относятся уровень метаболизма и отношение сброса (1:10 по
-умолчанию). Расчеты принимают также во внимание снижение уровня кислорода в области загубника. Если
-значение pO<sub>2</sub> опускается ниже безопасного, в <em>Детальном плане</em> будет отображено предупреждение.
-Обычно pSCR погружение выполняется с одним основным баллоном и несколькими аварийными. Поэтому
-заполнение таблицы доступных баллонов и путевых точек очень похоже на погружение CCR, описанное
-ниже. Однако для pSCR-погружений не указываются установки кислорода. Ниже приведен план погружения
-с использованием pSCR. Он очень похож на план CCR ниже, но обратите внимание на более долгий подъем,
-что связано с более низким уровнем кислорода, вызванным снижением его количества в области загубника.</p></div>
-<div class="imageblock" style="text-align:center;">
-<div class="content">
-<img src="images/Planner_pSCR1_f20.jpg" alt="Рисунок: планирование pSCR-погружения" />
-</div>
-</div>
-</div>
-<div class="sect2">
-<h3 id="_планирование_погружений_на_ребризере_замкнутого_цикла">13.4. Планирование погружений на ребризере замкнутого цикла</h3>
-<div class="paragraph"><p>Для планирования таких погружений выберите CCR в списке, как показано на рисунке выше (список
-обведен синей линией).</p></div>
-<div class="paragraph"><p><strong>Доступные смеси</strong>: добавьте в таблицу доступных смесей информацию о баллонах дилуэнта и аварийных
-газах. НЕ вводите информацию о кислородном баллоне, поскольку он подразумевается при использовании
-режима CCR.</p></div>
-<div class="paragraph"><p><strong>Ввод установок</strong>: укажите значение установки по умолчанию в *Настройках* приложения (в главном меню
-выберите <em>Файл → Настройки</em> и вкладку <em>Профиль</em>). По умолчанию для всех добавляемых сегментов
-точка установки берется из настроек, он вы можете поменять их по своему желанию. Значение равное
-нулю означает, что дайвер перешел на открытый цикл. Декомпрессия всегда рассчитывается используя
-последнюю установку вручную добавленного сегмента. Чтобы запланировать переход на ОЦ во время подъема,
-добавьте одноминутный сегмент со значением установки равным нулю. Декомпрессионный алгоритм
-автоматически не меняет смеси в режиме CCR (когда указана положительная установка),
-но делает это для всплытий на открытом цикле.</p></div>
-<div class="paragraph"><p>Профиль погружения на ребризере замкнутого типа может выглядеть так:</p></div>
-<div class="imageblock" style="text-align:center;">
-<div class="content">
-<img src="images/Planner_CCR1_f20.jpg" alt="Рисунок: Планирование CCR-погружения, настройка" />
-</div>
-</div>
-<div class="paragraph"><p>Обратите внимание, что в <em>Детальном плане погружения</em> расход газа для CCR-сегментов не рассчитывается
-и всегда равен нулю.</p></div>
-</div>
-<div class="sect2">
-<h3 id="S_Replan">13.5. Изменение существующего плана</h3>
-<div class="paragraph"><p>Обычно, после сохранения плана, он доступен в <strong>Списке погружений</strong>. <em>Subsurface</em> не предоставляет
-возможности изменить план из списка. Для того, чтобы изменить план, выберите его в списке. Затем в
-главном меню выберите <em>Журнал → Перепланировать</em>. Это действие откроет планировщик с существующим
-планом, позволяя изменить его.</p></div>
-<div class="paragraph"><p>В случае перепланирования у вас появляется возможность <strong>Сохранить новый</strong> план, для того, чтобы
-не перезаписывать старый. Если новая копия сохраняется с тем же временем, что и старый план, то они
-считаются двумя версиями одного плана и не влияют друг на друга при вычислении декомпрессионных
-обязательств.</p></div>
-</div>
-<div class="sect2">
-<h3 id="_планирование_повторных_погружений">13.6. Планирование повторных погружений</h3>
-<div class="paragraph"><p><em>Subsurface</em> позволяет планировать повторные погружения при условии, что вы
-корректно укажете дату и время начала. При этом учитывается остаточное
-насыщение после предыдущего погружения.</p></div>
-<div class="paragraph"><p>Если вы только закончили долгое/глубокое погружение и планируете новое,
-выберите последний дайв в списке погружение и активируйте планировщик
-<em>Subsurface</em>. В зависимости от времени начала планируемого дайва, остаточное
-насыщение предыдущего погружения будет принято во внимание и план будет
-построен с учетом этих ограничений.</p></div>
-<div class="paragraph"><p>Если вы используете одну стандартную конфигурацию (например, как в GUE), то
-можно создать шаблонное погружение. Чтобы спланировать погружение с этой
-конфигурацией, выберите шаблонное погружение в списке и активируйте планировщик:
-для нового плана будет использоваться конфигурация из шаблона.</p></div>
-</div>
-<div class="sect2">
-<h3 id="_печать_плана_погружения">13.7. Печать плана погружения</h3>
-<div class="paragraph"><p>Вы можете распечатать план погружения с тем чтобы взять его с собой под воду, нажав кнопку <em>Печать</em>.
-Альтернативный способ - скопировать текст из <em>Детального плана погружения</em> и вставить его в в ваш
-любимый текстовый редактор.</p></div>
-<div class="paragraph"><p>План погружения имеет много общего с журналом обычного погружения (профиль, примечания и т.д.).
-После сохранения плана, его детали и расчет по газам сохраняются в *Примечаниях*. Во время
-планирования он может быть распечатан по нажатию кнопки <em>Печать</em>. Однако после сохранения план
-выглядит как обычный дайв.</p></div>
-</div>
-</div>
-</div>
-<div class="sect1">
-<h2 id="_пункты_главного_меню_subsurface">14. Пункты главного меню Subsurface</h2>
-<div class="sectionbody">
-<div class="paragraph"><p>В этой главе описываются пункты главного меню и их функции. Некоторые пункты
-ссылаются на соответствующие главы данного руководства для быстрой навигации.</p></div>
-<div class="sect2">
-<h3 id="_файл">14.1. Файл</h3>
-<div class="ulist"><ul>
-<li>
-<p>
-<a href="#S_NewLogbook"><em>Новый журнал</em></a> - Закрывает текущий открытый журнал и
- создает новый.
-</p>
-</li>
-<li>
-<p>
-<em>Открыть журнал</em> - Вызывает диалог выбора файла для открытия
- журнала.
-</p>
-</li>
-<li>
-<p>
-<em>Открыть облачное хранилище</em> - Загружает ранее сохраненный журнал из
- <a href="#S_Cloud_storage"><em>облачного хранилища</em></a>.
-</p>
-</li>
-<li>
-<p>
-<em>Сохранить</em> - Сохраняет текущий открытый журнал.
-</p>
-</li>
-<li>
-<p>
-<em>Сохранить в облаке</em> - Сохраняет журнал в <a href="#S_Cloud_storage"><em>облачном хранилище</em></a>.
-</p>
-</li>
-<li>
-<p>
-<em>Сохранить как</em> - Сохраняет текущий журнал в файл с новым именем
-</p>
-</li>
-<li>
-<p>
-<em>Закрыть</em> - Закрывает текущий журнал.
-</p>
-</li>
-<li>
-<p>
-<a href="#S_ExportLog"><em>Экспорт</em></a> - экспортирует текущий журнал или выбранные
- погружения в один из форматов.
-</p>
-</li>
-<li>
-<p>
-<a href="#S_PrintDivelog"><em>Печать</em></a> - печать журнала или выбранных погружений.
-</p>
-</li>
-<li>
-<p>
-<a href="#S_Preferences"><em>Настройки</em></a> - настройка параметров <em>Subsurface</em>
-</p>
-</li>
-<li>
-<p>
-<a href="#S_FindMovedImages"><em>Найти перемещенные фото</em></a> - Если ранее загруженные фотографии были перенесены
- в другое место, найти их и обновить их местоположение в соответствующих погружениях.
-</p>
-</li>
-<li>
-<p>
-<em>Выход</em> - Выйти из <em>Subsurface</em>
-</p>
-</li>
-</ul></div>
-</div>
-<div class="sect2">
-<h3 id="_импорт">14.2. Импорт</h3>
-<div class="ulist"><ul>
-<li>
-<p>
-<a href="#S_ImportDiveComputer"><em>Импорт из дайв-компьютера</em></a> - импорт погружений
- из дайв-компьютера
-</p>
-</li>
-<li>
-<p>
-<a href="#Unified_import"><em>Импорт журналов</em></a> - импорт погружений из сторонних
- форматов
-</p>
-</li>
-<li>
-<p>
-<a href="#S_Companion"><em>Импорт координат</em></a> - загрузка координат погружений из
- мобильного помощника <em>Subsurface</em>.
-</p>
-</li>
-<li>
-<p>
-<a href="#S_ImportingDivelogsDe"><em>Импорт с сайта divelogs.de</em></a> - импорт погружений
- из интернет-сервиса <em>www.Divelogs.de</em>.
-</p>
-</li>
-</ul></div>
-</div>
-<div class="sect2">
-<h3 id="_журнал">14.3. Журнал</h3>
-<div class="ulist"><ul>
-<li>
-<p>
-<a href="#S_EnterData"><em>Добавить погружение</em></a> - ручное добавление погружения.
-</p>
-</li>
-<li>
-<p>
-<em>Редактировать погружение</em> - Позволяет отредактировать погружение, введенное вручную.
-</p>
-</li>
-<li>
-<p>
-<a href="#S_DivePlanner"><em>Планировщик</em></a> - запускает планировщик погружений.
-</p>
-</li>
-<li>
-<p>
-<a href="#S_Replan"><em>Перепланирование погружения</em></a> - Редактировать существующий план погружения
-</p>
-</li>
-<li>
-<p>
-<a href="#S_CopyComponents"><em>Копировать параметры погружения</em></a> - скопировать указанные поля погружения
- в буфер обмена
-</p>
-</li>
-<li>
-<p>
-<em>Вставить параметры погружения</em> - вставить из буфера параметры, скопированные ранее,
- в выделенные погружения
-</p>
-</li>
-<li>
-<p>
-<a href="#S_Renumber"><em>Перенумеровать</em></a> - перенумерация списка погружений.
-</p>
-</li>
-<li>
-<p>
-<a href="#S_Group"><em>Авто-группировка</em></a> - автоматическая группировка погружений в
- поездки.
-</p>
-</li>
-<li>
-<p>
-<a href="#S_DeviceNames"><em>Мои дайв-компьютеры</em></a> - редактирование названий
- дайв-компьютеров.
-</p>
-</li>
-<li>
-<p>
-<a href="#S_Filter"><em>Фильтр погружений</em></a> - фильтрация списка погружений
-</p>
-</li>
-</ul></div>
-</div>
-<div class="sect2">
-<h3 id="_вид">14.4. Вид</h3>
-<div class="ulist"><ul>
-<li>
-<p>
-<a href="#S_ViewPanels"><em>Все</em></a> - показать все четыре панели <em>Subsurface</em>.
-</p>
-</li>
-<li>
-<p>
-<a href="#S_ViewPanels"><em>Список</em></a> - показать только список погружений.
-</p>
-</li>
-<li>
-<p>
-<a href="#S_ViewPanels"><em>Профиль</em></a> - показать только профиль погружения.
-</p>
-</li>
-<li>
-<p>
-<a href="#S_ViewPanels"><em>Информация</em></a> - показать только информационную панель.
-</p>
-</li>
-<li>
-<p>
-<a href="#S_ViewPanels"><em>Карта</em></a> - показать только карту.
-</p>
-</li>
-<li>
-<p>
-<em>Статистика по годам</em> - показать статистику журнала погружений по годам и
- месяцам.
-</p>
-</li>
-<li>
-<p>
-<em>Предыдущий компьютер</em> - переключиться на предыдущий компьютер.
-</p>
-</li>
-<li>
-<p>
-<em>Следующий компьютер</em> - переключиться на следующий компьютер.
-</p>
-</li>
-<li>
-<p>
-<em>Полный экран</em> - переключение полноэкранного режима.
-</p>
-</li>
-</ul></div>
-</div>
-<div class="sect2">
-<h3 id="_поделиться">14.5. Поделиться</h3>
-<div class="ulist"><ul>
-<li>
-<p>
-- <a href="#S_Facebook"><em>Facebook</em></a> - поделиться информацией о выбранном погружении в вашей хронике на Facebook.
-</p>
-</li>
-</ul></div>
-</div>
-<div class="sect2">
-<h3 id="_помощь">14.6. Помощь</h3>
-<div class="ulist"><ul>
-<li>
-<p>
-<em>О программе</em> - показывает информационное окно с указанием версии
- <em>Subsurface</em>
-</p>
-</li>
-<li>
-<p>
-<em>Проверить обновления</em> - проверяет доступность новой версии на
- <a href="http://subsurface-divelog.org/">_веб-сайте Subsurface</a>.
-</p>
-</li>
-<li>
-<p>
-<a href="#S_UserSurvey"><em>Опрос пользователей</em></a> - помогите нам улучшить <em>Subsurface</em>, заполнив опросник.
-</p>
-</li>
-<li>
-<p>
-<em>Руководство пользователя</em> - открывает этот документ в новом окне.
-</p>
-</li>
-</ul></div>
-</div>
-</div>
-</div>
-<div class="sect1">
-<h2 id="APPENDIX_A">15. ПРИЛОЖЕНИЕ А: Настройка ОС для импорта из дайв-компьютера</h2>
-<div class="sectionbody">
-<div class="sect2">
-<h3 id="_удостоверьтесь_что_установлены_необходимые_драйверы">15.1. Удостоверьтесь, что установлены необходимые драйверы</h3>
-<div class="admonitionblock">
-<table><tr>
-<td class="icon">
-<img src="images/icons/drivers.jpg" alt="Замечание" />
-</td>
-<td class="content">Операционной системе вашего настольного компьютера необходим соответствующий
-драйвер для с связи с дайв-компьютером в зависимости от того, каким образом
-дайв-компьютер подключен (Bluetooth, USB, инфракрасный порт).</td>
-</tr></table>
-</div>
-<div class="ulist"><ul>
-<li>
-<p>
-В Linux вам может понадобиться загрузить соответствующий модуль ядра.
- Большинство дистрибутивов делают это автоматически, так что вам не нужно
- предпринимать каких-то действий. Однако в некоторых случаях, например
- для ИК-устройств, вам придется загрузить дополнительный драйвер.
-</p>
-</li>
-<li>
-<p>
-В случае Windows OC сама предложит загрузить корректный драйвер сразу
- после подключения дайв-компьютера к USB-порту.
-</p>
-</li>
-<li>
-<p>
-Пользователям MAC возможно придется самим найти соответствующий драйвер.
- Например, для Mares Puck и других дайв-компьютеров, использующих
- интерфейс последовательного USB-порта на основе чипа Silicon Labs CP2101,
- необходимый драйвер с именем <em>Mac_OSX_VCP_Driver.zip</em> можно взять на
- сайте <a href="http://www.silabs.com/support/pages/document-library.aspx?p=Interface&f=USB%20Bridges&pn=CP2101">Silicon Labs document and software repository</a>.
-</p>
-</li>
-</ul></div>
-</div>
-<div class="sect2">
-<h3 id="S_HowFindDeviceName">15.2. Как определить имя USB-устройства и получить права доступа</h3>
-<div class="admonitionblock">
-<table><tr>
-<td class="icon">
-<img src="images/icons/usb.jpg" alt="Замечание" />
-</td>
-<td class="content">Когда вы подключаете дайв-компьютер с помощью USB-кабеля, обычно <em>Subsurface</em>
-предлагает либо список устройств (точек монтирования в случае Uemis Zurich),
-либо делает список недоступным, если имя устройства не требуется вовсе. В
-редких случаях, если это не работает, попробуй следовать этим инструкциям,
-чтобы определить имя устройства самостоятельно:</td>
-</tr></table>
-</div>
-<div class="paragraph"><div class="title">Windows:</div><p>Простым перебором попробуйте COM1, COM2 и т.д. Список содержит все
-подключенные COM-устройства.</p></div>
-<div class="paragraph"><div class="title">Mac OS:</div><p>Список должен содержать все подключенные устройства.</p></div>
-<div class="paragraph"><div class="title">Linux:</div><p>Наиболее точный способ определить название порта:</p></div>
-<div class="ulist"><ul>
-<li>
-<p>
-Отсоедините USB-кабель от дайв-компьютера
-</p>
-</li>
-<li>
-<p>
-Откройте терминал
-</p>
-</li>
-<li>
-<p>
-Введите команду <em>dmesg</em> и нажмите Enter
-</p>
-</li>
-<li>
-<p>
-Подсоедините USB-кабель к дайв-компьютеру
-</p>
-</li>
-<li>
-<p>
-Введите команду <em>dmesg</em> и нажмите Enter
-</p>
-</li>
-</ul></div>
-<div class="paragraph"><p>Вы должны увидеть схожие сообщения:</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>Третья строчка снизу показывает, что FTDI USB-адаптер обнаружен и подключен
-как устройство <code>ttyUSB3</code>. Для импорта в <em>Subsurface</em> используйте имя
-<code>/dev/ttyUSB3</code>.</p></div>
-<div class="paragraph"><p>Убедитесь, что у вас есть права на запись в устройство:</p></div>
-<div class="paragraph"><p>В Unix-подобных операционных системах доступ к USB-портам разрешен только
-пользователям, которые являются членами группы <code>dialout</code>. Если пользователь не
-root, то он возможно не входит в эту группу и не сможет использовать USB-порт.
-Допустим, что имя пользователя <em>johnb</em>.</p></div>
-<div class="ulist"><ul>
-<li>
-<p>
-Под пользователем root выполните команду <code>usermod -a -G dialout johnb</code> (для
- пользователей Ubuntu: <code>sudo usermod -a -G dialout johnb</code>)
-</p>
-</li>
-<li>
-<p>
-Выполните команду <code>id johnb</code>. Она отображает список всех групп, к которым
- принадлежит указанный пользователь. Убедитесь, что в списке групп
- присутствует группа <code>dialout</code>.
-</p>
-</li>
-<li>
-<p>
-В некоторых случаях (например, Ubuntu) может потребоваться закрыть текущий сеанс
- и войти в систему заново.
-</p>
-</li>
-</ul></div>
-<div class="paragraph"><p>Зная название устройства (например, <code>dev/ttyUSB3</code>) и имея права на доступ к
-USB-порту, у вас должно получиться импортировать погружения из
-дайв-компьютера.</p></div>
-</div>
-<div class="sect2">
-<h3 id="S_HowFindBluetoothDeviceName">15.3. Настройка Bluetooth-устройств</h3>
-<div class="admonitionblock">
-<table><tr>
-<td class="icon">
-<img src="images/icons/bluetooth.jpg" alt="Замечание" />
-</td>
-<td class="content">Для дайв-компьютеров с Bluetooth-интерфейсом (например, Heinrichs Weikamp Frog
-или Shearwater Predator, Petrel или Nerd), процедура получения имени устройства
-отличается от той, что описана выше:</td>
-</tr></table>
-</div>
-<div class="ulist"><ul>
-<li>
-<p>
-<strong>После включения Bluetooth на дайв-компьютере, убедитесь что он находится в режиме выгрузки.</strong>
-</p>
-</li>
-</ul></div>
-<div class="paragraph"><p>По вопросам сопряжения дайв-компьютера обратитесь к документации
-производителя. В случае Shearwater Predator/Petrel/Nerd выберите <em>Dive Log →
-Upload Log</em> и ожидайте сообщения <em>Wait PC</em>.</p></div>
-<div class="ulist"><ul>
-<li>
-<p>
-<strong>Сопряжение настольного и дайв-компьютера</strong>
-</p>
-</li>
-</ul></div>
-<div class="sect3">
-<h4 id="_windows_2">15.3.1. Windows:</h4>
-<div class="paragraph"><p>Bluetooth вероятнее всего уже включен. Для сопряжения устройств перейдите в
-<em>Панель управления→Устройства Bluetooth→Добавить беспроводное устройство</em>.
-Вам будет представлено окно, в котором должен показываться ваш дайв-компьютер.
-Нажмите на нем правой кнопкой мыши и из контекстного меню выберите
-<em>Свойства→COM порты</em>, чтобы определить название порта. Если вам показываются
-несколько портов, выберите тот, который помечен как "Исходящий".</p></div>
-<div class="paragraph"><p>Для импорта в <em>Subsurface</em> этот порт уже должен быть в списке. Если его там
-нет, то введите имя порта вручную.</p></div>
-<div class="paragraph"><p>Примечание: Если у вас возникают проблемы с загрузкой из дайв-компьютера после
-использования других программ, попробуйте удалить существующее сопряжение.</p></div>
-</div>
-<div class="sect3">
-<h4 id="_macos">15.3.2. MacOS:</h4>
-<div class="paragraph"><p>Нажмите на значке Bluetooth в строке меню и выберите <em>Настроить устройство
-Bluetooth…</em>. Дайв-компьютер должен появиться в списке устройств. Выберите
-его и выполните процедуру сопряжения. Этот шаг потребуется выполнить один
-раз.</p></div>
-<div class="paragraph"><p>После завершения сопряжения, устройство должно показываться в <em>Subsurface</em> в
-списке <em>Устройство или точка монтирования</em> в диалоге импорта.</p></div>
-</div>
-<div class="sect3">
-<h4 id="_linux">15.3.3. Linux:</h4>
-<div class="paragraph"><p>Удостоверьтесь, что Bluetooth включен на вашем настольном компьютере. Процесс
-сопряжения в этом случае достаточно прост. Например, в Gnome3 в правом верхнем
-углу рабочего стола должен быть значок Bluetooth. Выберите <em>Настроить новое
-устройство</em>. В появившемся окне выберите дайв-компьютер и выполните
-сопряжение. Если у вас запросят PIN-код, попробуйте ввести <em>0000</em>.</p></div>
-<div class="paragraph"><p>Установка соединения для загрузки погружений из дайв-компьютеров с интерфейсом Bluetooth, таких,
-как <em>Shearwater Petrel</em>, пока что не автоматизирована и в общем случае потребует от вас работы
-в коммандной строке. Этот процесс состоит из трех шагов.</p></div>
-<div class="ulist"><ul>
-<li>
-<p>
-Включите Bluetooth-адаптер и установите сопряжение с дайв-компьютером
-</p>
-</li>
-<li>
-<p>
-Установите RFCOMM-соединение
-</p>
-</li>
-<li>
-<p>
-Загрузите погружения с помощь <em>Subsurface</em>
-</p>
-</li>
-</ul></div>
-<div class="paragraph"><p>Убедитесь, что дайв-компьютер в режиме выгрузки. На <em>Shearwater Petrel</em>, <em>Petrel 2</em> и <em>Nerd</em> выберите
-в меню <em>Dive Log</em>, затем <em>Upload Log</em>. На дисплее высветится <em>Initializing</em>, <em>Wait PC 3:00</em> и
-начнется обратный отсчет. После установки соединения на дисплее высветится <em>Wait CMD …</em> и
-отсчет продолжится. Во время загрузки погружений на дисплее отображается надпись <em>Sending</em>, а
-затем <em>Sent Dive</em>.</p></div>
-<div class="paragraph"><p>Чтобы установить соединение, вам нужно получить полномочия суперпользователя с помощью команд
-<code>sudo</code> или <code>su</code>. Для загрузки погружений у пользователя должны быть полномочия. В большинстве
-Linux-дистрибутивов пользователю достаточно быть членом группы dialout (что также действительно
-и для дайв-компьютеров с USB-интерфейсом). В командой строке введите команду:</p></div>
-<div class="paragraph"><p><code>sudo usermod -a -G dialout username</code></p></div>
-<div class="paragraph"><p>После этого завершите сеанс и войдите в систему заново.</p></div>
-</div>
-<div class="sect3">
-<h4 id="_включение_bluetooth_контроллера_и_сопряжение_с_дайв_компьютером">15.3.4. Включение Bluetooth-контроллера и сопряжение с дайв-компьютером</h4>
-<div class="paragraph"><p>Попробуйте настроить Bluetooth-контроллер и сопряжение с дайв-компьютером посредством штатного
-графического интерфейса операционной системы. После перевода дайв-компьютера в режим выгрузки,
-щелкните по значку Bluetooth в области уведомлений и выберите <em>Добавить новое устройство</em>. Дайв-
-компьютер должен появиться в списке. Если у вас запросяи пароль, введите 0000. Запишите или скопируйте
-MAC-адрес дайв-компьютера, он понадобится позже (адрес имеет вид 00:11:22:33:44:55).</p></div>
-<div class="paragraph"><p>Если этот метод не сработал, попробуйте сделать сопряжение из командной строки. Откройте терминал и
-используйте <code>hciconfig</code>, чтобы проверить статус Bluetooth-контроллера:</p></div>
-<div class="literalblock">
-<div class="content">
-<pre><code>$ hciconfig
-hci0: Type: BR/EDR Bus: USB
- BD Address: 01:23:45:67:89:AB ACL MTU: 310:10 SCO MTU: 64:8
- *DOWN*
- RX bytes:504 acl:0 sco:0 events:22 errors:0
- TX bytes:92 acl:0 sco:0 commands:21 errors:0</code></pre>
-</div></div>
-<div class="paragraph"><p>Тут мы видим, что контроллер с адресом 01:23:45:67:89:AB подключен как hci0. Его состояние <em>DOWN</em>,
-т.е. выключен. Дополнительные контроллеры будут представлены как hci1, и т.д. Теперь необходимо
-включить питание контроллера:</p></div>
-<div class="literalblock">
-<div class="content">
-<pre><code>sudo hciconfig hci0 up auth+ (enter password when prompted)
-hciconfig
-hci0: Type: BR/EDR Bus: USB
- BD Address: 01:23:45:67:89:AB ACL MTU: 310:10 SCO MTU: 64:8
- *UP RUNNING PSCAN AUTH*
- RX bytes:1026 acl:0 sco:0 events:47 errors:0
- TX bytes:449 acl:0 sco:0 commands:46 errors:0</code></pre>
-</div></div>
-<div class="paragraph"><p>Удостоверьтесь, что статус контроллера теперь содержит <code><em>UP</em>, <em>RUNNING</em> и <em>AUTH</em></code>.</p></div>
-<div class="paragraph"><p>Если на компьютере несколько Bluetooth-контроллеров, остальные можно выключиться, чтобы избежать путаницы:</p></div>
-<div class="literalblock">
-<div class="content">
-<pre><code>sudo hciconfig hci1 down</code></pre>
-</div></div>
-<div class="paragraph"><p>Следующий шаг: установить доверенное сопряжение с дайв-компьютером. В дистрибутивах с установленным
-пакетом BlueZ (например, Fedora 22) вы можете использовать <code>blutootctl</code>, который имеет собственную подсказку:</p></div>
-<div class="literalblock">
-<div class="content">
-<pre><code>bluetoothctl
-[NEW] Controller 01:23:45:67:89:AB localhost.localdomain [default]
-[bluetooth]# agent on
-Agent registered
-[bluetooth]# default-agent
-Default agent request successful
-[bluetooth]# scan on <----теперь переведите дайв-компьютер в режим выгрузки
-Discovery started
-[CHG] Controller 01:23:45:67:89:AB Discovering: yes
-[NEW] Device 00:11:22:33:44:55 Petrel
-[bluetooth]# trust 00:11:22:33:44:55 <----вы можете использовать клавишу TAB для автодополнения MAC-адреса
-[CHG] Device 00:11:22:33:44:55 Trusted: yes
-Changing 00:11:22:33:44:55 trust succeeded
-[bluetooth]# pair 00:11:22:33:44:55
-Attempting to pair with 00:11:22:33:44:55
-[CHG] Device 00:11:22:33:44:55 Connected: yes
-[CHG] Device 00:11:22:33:44:55 UUIDs: 00001101-0000-1000-8000-0089abc12345
-[CHG] Device 00:11:22:33:44:55 Paired: yes
-Pairing successful
-[CHG] Device 00:11:22:33:44:55 Connected: no</code></pre>
-</div></div>
-<div class="paragraph"><p>Если будет запрошен пароль, введите 0000. Ничего страшного в том, что в последней строке содержится
-фраза <em>Connected: no</em>, главное тут - сообщение строкой выше <em>Pairing successful</em>.</p></div>
-<div class="paragraph"><p>Если в системе установлен пакет BlueZ версии 4 (например, в Ubuntu 12.04 до 15.04), то скорее всего
-в ней нет <code>bluetoothctl</code>, но есть утилита <code>bluez-simple-agent</code> или просто <code>simple-agent</code>.</p></div>
-<div class="literalblock">
-<div class="content">
-<pre><code>hcitool -i hci0 scanning
-Scanning ...
- 00:11:22:33:44:55 Petrel
- bluez-simple-agent hci0 00:11:22:33:44:55</code></pre>
-</div></div>
-<div class="paragraph"><p>После сопряжения необходимо установить RFCOMM-соединение.</p></div>
-</div>
-<div class="sect3">
-<h4 id="_установка_rfcomm_соединения">15.3.5. Установка RFCOMM-соединения</h4>
-<div class="paragraph"><p>Для установки RFCOMM-соединения используйте следующую команду:</p></div>
-<div class="paragraph"><p><code>sudo rfcomm -i <controller> connect <dev> <bdaddr> [channel]</code></p></div>
-<div class="ulist"><ul>
-<li>
-<p>
-<controller> - Bluetooth-контроллер, <code>hci0</code>.
-</p>
-</li>
-<li>
-<p>
-<dev> - устройство RFCOMM, <code>rfcomm0</code>
-</p>
-</li>
-<li>
-<p>
-<bdaddr> - MAC-адрес дайв-компьютера, <code>00:11:22:33:44:55</code>
-</p>
-</li>
-<li>
-<p>
-[channel] - Bluetooth-канал дайв-компьютера, к которому на необходимо подключиться.
-</p>
-</li>
-</ul></div>
-<div class="paragraph"><p>Если канал не указать, по умолчанию будет выбран 1. Основываясь на сообщениях наших пользователей,
-ниже приведен список каналов для различных моделей дайв-компьютеров:</p></div>
-<div class="ulist"><ul>
-<li>
-<p>
-<em>Shearwater Petrel 1</em>: канал 1
-</p>
-</li>
-<li>
-<p>
-<em>Shearwater Petrel 2</em>: канал 5
-</p>
-</li>
-<li>
-<p>
-<em>Shearwater Nerd</em>: канал 5
-</p>
-</li>
-<li>
-<p>
-<em>Heinrichs-Weikamp OSTC Sport</em>: канал 1
-</p>
-</li>
-</ul></div>
-<div class="paragraph"><p>Таким образом, чтобы подключить <em>Shearwater Petrel 2</em>, переведите его в режим выгрузки и введите команду:</p></div>
-<div class="literalblock">
-<div class="content">
-<pre><code>sudo rfcomm -i hci0 connect rfcomm0 00:11:22:33:44:55 5 (если вас запросят пароль, введите 0000)</code></pre>
-</div></div>
-<div class="paragraph"><p>В ответ вы должны получить сообщение:</p></div>
-<div class="literalblock">
-<div class="content">
-<pre><code>Connected /dev/rfcomm0 to 00:11:22:33:44:55 on channel 5
-Press CTRL-C for hangup</code></pre>
-</div></div>
-<div class="paragraph"><p>Для подключения _Shearwater Petrel 1+ или <code>HW OSTC Sport</code>, переведите компьютер в режим загрузки и введите команду:</p></div>
-<div class="literalblock">
-<div class="content">
-<pre><code>sudo rfcomm -i hci0 connect rfcomm0 00:11:22:33:44:55 (если вас запросят пароль, введите 0000)
-Connected /dev/rfcomm0 to 00:11:22:33:44:55 on channel 1
-Press CTRL-C for hangup</code></pre>
-</div></div>
-<div class="paragraph"><p>Если номер Bluetooth-канала неизвестен, либо указанный номер не работает, определить его вам поможет
-команда <code>sdptool records</code>. Ниже приведен её вывод для дайв-компьютера <em>Shearwater Petrel 2</em>:</p></div>
-<div class="literalblock">
-<div class="content">
-<pre><code>sdptool -i hci0 records 00:11:22:33:44:55
-Service Name: Serial Port
-Service RecHandle: 0x10000
-Service Class ID List:
- "Serial Port" (0x1101)
- Protocol Descriptor List:
- "L2CAP" (0x0100)
- "RFCOMM" (0x0003)
- Channel: 5</code></pre>
-</div></div>
-<div class="paragraph"><p>Если ваш дайв-компьютер не в списке, или номер канала отличается, пожалуйста, сообщите об этом
-разработчикам <em>Subsurface</em> через форум пользователей или список рассылки <em>subsurface@subsurface-divelog.org</em>.</p></div>
-</div>
-<div class="sect3">
-<h4 id="_загрузка_погружений_в_subsurface">15.3.6. Загрузка погружений в Subsurface</h4>
-<div class="paragraph"><p>После установки RFCOMM-соединения и пока идет обратный отсчет режима выгрузки на дайв-компьютере,
-перейдите в <em>Subsurface</em>, выберите <em>Импорт → Импорт из дайв-компьютера</em>, укажите производителя
-(например, <em>Shearwater</em>), модель (<em>Petrel</em>), устройство или точку монтирования (<em>/dev/rfcomm0</em>) и
-и нажмите <em>Загрузить</em>.</p></div>
-</div>
-</div>
-</div>
-</div>
-<div class="sect1">
-<h2 id="APPENDIX_B">16. ПРИЛОЖЕНИЕ Б: Настройка дайв-компьютеров для импорта</h2>
-<div class="sectionbody">
-<div class="sect2">
-<h3 id="S_ImportUemis">16.1. Импорт погружений из Uemis Zurich</h3>
-<div class="admonitionblock">
-<table><tr>
-<td class="icon">
-<img src="images/icons/iumis.jpg" alt="Замечание" />
-</td>
-<td class="content"><em>Subsurface</em> импортирует информацию, хранящуюся в SDA (внутренняя файловая
-система Uemis), включая данные о точках погружения и снаряжении. Информация о
-напарниках в данный момент недоступна. Сопряжение схоже с USB-компьютерами (и
-при этом Uemis заряжается от USB-порта). Главное отличие состоит в том, что
-вам нужно указывать не имя порта, а точку монтирования файловой системы
-UEMISSDA. В Windows это буква диска (зачастую E: или F:), в Mac это
-<em>/Volumes/UEMISSDA</em>, а в Linux это зависит от дистрибутива. Например, в Fedora
-это <em>/var/run/media/<имя<em>пользователя>/UEMISSDA</em>. В любом случае _Subsurface</em>
-предложить вам варианты в выпадающем списке на диалоге импорта.</td>
-</tr></table>
-</div>
-<div class="paragraph"><p>После того, как вы указали точку монтирования, выполните загрузку. Uemis
-Zurich имеет одно ограничение (это ограничение прошивки дайв-компьютера, а не
-<em>Subsurface</em>) - невозможно загрузить более 40-50 погружений за один раз,
-происходит переполнение SDA. Обычно это происходит при первой загрузке. Если
-вы импортируете погружения ежедневно или даже после поездки, емкости SDA
-вполне достаточно.
-Если <em>Subsurface</em> показывает сообщение о переполнении памяти дайв-компьютера,
-решение достаточно простое: отключите SDA, выключите и включите
-дайв-компьютер, и подключите заново. Начните импорт заново и <em>Subsurface</em>
-продолжит загрузку с того места где она прервалась. Возможно вам придется
-повторить процедуру несколько раз в зависимости от того, сколько погружений
-записано в памяти Uemis Zurich.</p></div>
-</div>
-<div class="sect2">
-<h3 id="S_ImportingGalileo">16.2. Импорт погружений из Uwatec Galileo</h3>
-<div class="admonitionblock">
-<table><tr>
-<td class="icon">
-<img src="images/icons/Galileo.jpg" alt="Замечание" />
-</td>
-<td class="content">Компьютеры Uwatec Galileo используют беспроводной инфракрасный канал
-связи (IrDA). Со стороны настолько ПК используется USB-брелок с поддержкой
-протокола последовательного обмена через IrDA (SIR) на контроллере MSC7780
-производства компании MosChip.
-В Linux ядро изначально поддерживает протокол последовательного обмена через
-IrDA, однако вам придется дополнительно загрузить драйвер для коммуникации с
-дайв-компьютером. Самый простой путь: установить пакет irda-tools,
-предварительно загрузив его с сайта
-<a href="http://irda.sourceforge.net/docs/startirda.html">Linux IrDA Project</a>. После
-установки, пользователем <strong>root</strong> выполните в консоли команду <code>irattach irda0</code>.</td>
-</tr></table>
-</div>
-<div class="paragraph"><p>После этого <em>Subsurface</em> распознает дайв-компьютер и вы можете выполнить
-импорт.</p></div>
-<div class="paragraph"><p>С Windows ситуация схожая. Драйвера для контроллера MCS7780 доступны на
-нескольких интернет-сайтах, например на
-<a href="http://www.drivers-download.com/Drv/MosChip/MCS7780/">www.drivers-download.com</a>. IrDA драйверы для
-Windows для компьютеров также могут быть загружены с веб-сайта ScubaPro со страницы загрузки
-программного обеспечения ScubaPro SmartTrak.</p></div>
-<div class="paragraph"><p>Для Apple Mac, IrDA-соединение через MCS7780 невозможно для версий OSX 10.6 и
-выше.</p></div>
-</div>
-<div class="sect2">
-<h3 id="S_ImportingDR5">16.3. Импорт погружений из Heinrichs Weikamp DR5</h3>
-<div class="admonitionblock">
-<table><tr>
-<td class="icon">
-<img src="images/icons/HW_DR5.jpg" alt="Замечание" />
-</td>
-<td class="content">Когда этот дайв-компьютер подключен как USB-диск, он сохраняет отдельный
-UDDF-файл для каждого погружения. Выделите все файл погружения для импорта или
-открытия.
-Примечание: DR5 не сохраняет ни градиент-факторы, ни информацию а
-деко-обязательствах, поэтому <em>Subsurface</em> не может отобразить ее.
-Отрегулируйте значения градиент-фактора в <em>Настройках_ _Subsurface</em>, чтобы
-увидеть деко-обязательства на профиле, но учтите, что они вероятнее всего
-будут отличаться от тех, что показывает DR5.</td>
-</tr></table>
-</div>
-</div>
-<div class="sect2">
-<h3 id="S_ImportingXDeep">16.4. Импорт погружений из xDEEP BLACK</h3>
-<div class="admonitionblock">
-<table><tr>
-<td class="icon">
-<img src="images/icons/HW_xdeepblack.jpg" alt="Замечание" />
-</td>
-<td class="content">Каждое погружение должно быть сохранено в файл формата UDDF, используя пункт меню "Export UDDF".
-Если дайв-компьютер подключен как USB-устройство, то UDDF-файлы должны быть доступны в директории LOGBOOK.
-Примечание: xDEEP BLACK сохраняет время NDL, но не хранит информации о градиент-факторах и декомпрессии,
-и следовательно <em>Subsurface</em> не сможет отобразить их. Установите значения градиент-фактора в <em>Настройках_
-(вкладка _Профиль</em>), чтобы отобразить декомпрессионный потолок на профиле погружения, но учтите, что
-вероятнее всего деко-обязательства, рассчитанные в <em>Subsurface</em> наверняка будут отличаться от тех, что
-показывает xDEEP BLACK.</td>
-</tr></table>
-</div>
-</div>
-<div class="sect2">
-<h3 id="_импорт_погружений_из_shearwater_predator_petrel_nerd_используя_bluetooth">16.5. Импорт погружений из Shearwater Predator/Petrel/Nerd используя Bluetooth</h3>
-<div class="admonitionblock">
-<table><tr>
-<td class="icon">
-<img src="images/icons/predator.jpg" alt="Замечание" />
-</td>
-<td class="content">Инструкции по загрузке погружений через Bluetooth приведены выше в главе <a href="#S_Bluetooth"><em>Подключение _Subsurface</em> к дайв-компьютеру через Bluetooth_</a></td>
-</tr></table>
-</div>
-</div>
-<div class="sect2">
-<h3 id="S_PoseidonMkVI">16.6. Импорт погружений из Poseidon MkVI Discovery</h3>
-<div class="admonitionblock">
-<table><tr>
-<td class="icon">
-<img src="images/MkVI.jpeg" alt="Замечание" />
-</td>
-<td class="content">Загрузка журналов погружений из MkVI осуществляется с помощью специального коммуникационного
-адаптера и программного обеспечения <em>Poseidon PC Configuration Software</em>, предоставляемых при
-покупке MKVI. Это программное обеспечение работает в ОС Windows и позволяет настраивать
-оборудование и хранить журналы погружений. Связь между настольным и дайв-компьютером
-осуществляется через инфракрасный порт. Одномоментно можно загрузить данные только одного
-погружения, состоящие из трех файлов:</td>
-</tr></table>
-</div>
-<div class="ulist"><ul>
-<li>
-<p>
-Конфигурация настроек и ключевые параметры погружения (файл с расширением .txt)
-</p>
-</li>
-<li>
-<p>
-Детали погружения (файл с расширением .csv)
-</p>
-</li>
-<li>
-<p>
-Собственный формат журнала погружения (файл с расширение .cvsr).
-</p>
-</li>
-</ul></div>
-<div class="paragraph"><p><em>Subsurface</em> использует файлы с расширением .txt и .csv для импорта погружения.</p></div>
-</div>
-<div class="sect2">
-<h3 id="_импорт_погружений_из_apd_inspiration_ccr">16.7. Импорт погружений из APD Inspiration CCR</h3>
-<div class="admonitionblock">
-<table><tr>
-<td class="icon">
-<img src="images/APDComputer.jpg" alt="Замечание" />
-</td>
-<td class="content">Журналы погружений APD Inspiration и похожих CCR дайв-компьютеров можно загрузить, используя
-специальный коммуникационный адаптер и программное обеспечение <em>AP Communicator</em>, предоставляемые
-при покупке оборудования. Просмотреть журналы на платформах Windows и Mac/OS можно, используя
-<em>AP Log Viewer</em>. Вы также можете получить доступ к этим погружениям и из <em>Subsurface</em>. Для
-импорта погружений APD Inspiration необходимо выполнить следующие шаги:</td>
-</tr></table>
-</div>
-<div class="ulist"><ul>
-<li>
-<p>
-Загрузите погружение используя <em>AP Communicator</em>.
-</p>
-</li>
-<li>
-<p>
-Откройте погружение в <em>AP Log Viewer</em>.
-</p>
-</li>
-<li>
-<p>
-Выберите вкладку "<em>Data</em>" в верхней части экрана.
-</p>
-</li>
-<li>
-<p>
-На экране необработанных данных нажмите на "<em>_Copy to Clipboard</em>".
-</p>
-</li>
-<li>
-<p>
-Откройте текстовый редактор, например, Notepad (Windows), или TextWrangler (Mac).
-</p>
-</li>
-<li>
-<p>
-Вставьте данные из буфера обмена в редактор и сохраните файл с расширением <em>.APD</em>
-</p>
-</li>
-<li>
-<p>
-Находясь в <em>Subsurface</em>, выберите в меню <em>Импорт → Импорт журналов</em>, чтобы открыть
- <a href="#Unified_import">диалог универсального импорта</a>.
-</p>
-</li>
-<li>
-<p>
-В окне в правой нижней части выберите тип "APD-файлы"
-</p>
-</li>
-<li>
-<p>
-В списке файлов выберите тот, что вы сохранили ранее из текстового редактора. Будет представлено
- окно импорта.
-</p>
-</li>
-<li>
-<p>
-Внесите по необходимости изменения в параметры импорта, как описано в главе <a href="#S_ImportingCSVDives">Импорт CSV-файлов</a>.
-</p>
-</li>
-</ul></div>
-<div class="imageblock" style="text-align:center;">
-<div class="content">
-<img src="images/APD_CSVimportF22.jpg" alt="Рисунок: Импорт файлов APD log viewer" />
-</div>
-</div>
-<div class="ulist"><ul>
-<li>
-<p>
-Выпадающий список в левом верхнем углу позволяет указать журнал какого именно компьютера необходимо
- импортировать. По умолчанию это первый компьютер (DC1). Вы можете последовательно импортировать
- данные погружения сначала для DC1, а потом для DC2 (при просмотре погружения в <em>Subsurface</em> вы можете
- переключаться между дайв-компьютерами, выбрав в главном меню <em>Вид → След. компьютер</em>).
-</p>
-</li>
-<li>
-<p>
-Нажмите кнопку <em>Ок</em>, чтобы выполнить импорт.
-</p>
-</li>
-</ul></div>
-<div class="paragraph"><p>Журнал погружения APD должен появиться в <em>Subsurface</em>. Деко-потолок, сгенерированный Inspiration,
-можно посмотреть на профиле, выбрав соответствующую кнопку на панели слева от профиля погружения.
-Оборудование APD не записывает данные о давлении в баллонах, но вы можете указать их самостоятельно
-на вкладке <em>Снаряжение</em>.</p></div>
-</div>
-</div>
-</div>
-<div class="sect1">
-<h2 id="APPENDIX_C">17. ПРИЛОЖЕНИЕ В: Импорт журнала погружений из сторонних программ</h2>
-<div class="sectionbody">
-<div class="paragraph"><p>Импорт погружений из сторонних программ ведения журналов достаточно прост и
-выполняется с помощью универсального импорта, доступного из главного
-меню <em>Импорт → Импорт журнала</em>. Подробнее эта функциональность описана в
-<a href="#Unified_import">отдельной главе</a>.
-Однако в некоторых случаях может потребоваться два шага:</p></div>
-<div class="olist arabic"><ol class="arabic">
-<li>
-<p>
-Экспорт "чужого" журнала в формат, который может быть разобран
-<em>Subsurface</em>.
-</p>
-</li>
-<li>
-<p>
-Импорт этого файла в <em>Subsurface</em>.
-</p>
-</li>
-</ol></div>
-<div class="paragraph"><p>В этом приложении мы попытаемся рассказать как экспортировать погружения из
-сторонних программ. В большей части это касается Linux и Windows.</p></div>
-<div class="sect2">
-<h3 id="S_ImportingDivesSuunto">17.1. Экспорт погружений из <strong>Suunto Divemanager (DM3,DM4 и DM5)</strong></h3>
-<div class="admonitionblock">
-<table><tr>
-<td class="icon">
-<img src="images/icons/suuntologo.jpg" alt="Замечание" />
-</td>
-<td class="content">Divemanager 3 (DM3) - старая версия журнала погружений. Современные
-дайв-компьютеры Suunto используют Divemanager версий 4 или 5 (DM4 или DM5). Эти две версии
-используют разные подходы и имена файлов для экспорта погружений.</td>
-</tr></table>
-</div>
-<div class="paragraph"><p><strong>Divemanager 3 (DM3):</strong></p></div>
-<div class="olist arabic"><ol class="arabic">
-<li>
-<p>
-Запустите <em>Suunto Divemanager 3</em> и войдите под пользователем, для которого
-есть погружения в журнале.
-</p>
-</li>
-<li>
-<p>
-Не запускайте импорт погружений из дайв-компьютера.
-</p>
-</li>
-<li>
-<p>
-В навигационной панели в левой части окна программы выберите погружения.
-</p>
-</li>
-<li>
-<p>
-Используйте мышь и клавиши Ctrl и Shift для выбора одиночных и нескольких
-погружений.
-</p>
-</li>
-<li>
-<p>
-Для выбранных погружений используйте пункт меню <em>File → Export</em>
-</p>
-</li>
-<li>
-<p>
-Во всплывающем окне есть одно единственное поле <em>Export Path</em>
-</p>
-<div class="ulist"><ul>
-<li>
-<p>
-Нажмите кнопку Обзор рядом в этим полем
-</p>
-<div class="ulist"><ul>
-<li>
-<p>
-вам будет представлено окно файлового проводника
-</p>
-</li>
-<li>
-<p>
-перейдите в директорию для сохранения файла Divelog.SDE
-</p>
-</li>
-<li>
-<p>
-при желании измените имя файла
-</p>
-</li>
-<li>
-<p>
-нажмите <em>Сохранить</em>
-</p>
-</li>
-</ul></div>
-</li>
-<li>
-<p>
-Вернувшись во всплывающее окно экспорта, нажмите кнопку <em>Export</em>
-</p>
-</li>
-</ul></div>
-</li>
-<li>
-<p>
-Погружения экспортированы в файл Divelog.SDE.
-</p>
-</li>
-</ol></div>
-<div class="paragraph"><p><strong>Divemanager 4 (DM4) и Divemanager 5 (DM5):</strong></p></div>
-<div class="paragraph"><p>Чтобы экспортировать данные журнала DM4 и DM5, вам необходимо узнать
-местоположение базы данных, в которой хранятся погружения. Вы можете
-использовать как основную, так и резервную копию базы. Ниже описаны оба варианта:</p></div>
-<div class="paragraph"><p>Местонахождение базы данных Suunto DM4 (или DM5):</p></div>
-<div class="olist arabic"><ol class="arabic">
-<li>
-<p>
-Запустите Suunto DM4/DM5
-</p>
-</li>
-<li>
-<p>
-Выберите в меню <em>Help → About</em>
-</p>
-</li>
-<li>
-<p>
-Нажмите <em>Copy</em> после текста <em>Copy log folder path to clipboard</em>
-</p>
-</li>
-<li>
-<p>
-Запустите проводник Windows
-</p>
-</li>
-<li>
-<p>
-Вставьте текст из буфера обмена в строку навигации проводника
-</p>
-</li>
-<li>
-<p>
-Файл базы данных называется DM4.db
-</p>
-</li>
-</ol></div>
-<div class="paragraph"><p>Создание резервной копии Suunto DM4:</p></div>
-<div class="olist arabic"><ol class="arabic">
-<li>
-<p>
-Запустите Suunto DM4/DM5
-</p>
-</li>
-<li>
-<p>
-Выберите в меню <em>File - Create backup</em>
-</p>
-</li>
-<li>
-<p>
-В диалоге выбора файла укажите путь и название резервной копии, в этом
-примере мы используем расширение .bak по умолчанию
-</p>
-</li>
-<li>
-<p>
-Нажмите <em>Save</em>
-</p>
-</li>
-<li>
-<p>
-Погружения сохранены в файл DM4.bak (или DM5.bak)
-</p>
-</li>
-</ol></div>
-</div>
-<div class="sect2">
-<h3 id="_экспорт_погружений_из_atomic_logbook">17.2. Экспорт погружений из Atomic Logbook</h3>
-<div class="admonitionblock" id="Atomic_Export">
-<table><tr>
-<td class="icon">
-<img src="images/icons/atomiclogo.jpg" alt="Замечание" />
-</td>
-<td class="content">Компания Atomic Aquatics предлагает собственное программное обеспечение Atomic Logbook для платформы
-Windows. Оно позволяет загружать журналы погружений с компьютеров Cobalt и Cobalt 2. Журнал хранится
-в базе данных SQLite в файле C:\ProgramData\AtomicsAquatics\Cobalt-Logbook\Cobalt.db. Этот файл
-может быть напрямую импортирован в <em>Subsurface</em>.</td>
-</tr></table>
-</div>
-</div>
-<div class="sect2">
-<h3 id="Mares_Export">17.3. Экспорт погружений из Mares Dive Organiser V2.1</h3>
-<div class="admonitionblock">
-<table><tr>
-<td class="icon">
-<img src="images/icons/mareslogo.jpg" alt="Замечание" />
-</td>
-<td class="content">Mares Dive Organiser работает исключительно под управлением ОС Windows. Журнал
-погружений хранится в фрмате SQL Compact Edition database в файле с
-расширением <em>.sdf</em>. База данных содержит данные о всех зарегистрированных
-дайверах на данном ПК и о всех используемых дайв-компьютерах Mares. На
-сегодняшний день самый надежный способ получить копию журнала -
-экспортировать погружения в другой формат, распознаваемый <em>Subsurface</em>.</td>
-</tr></table>
-</div>
-<div class="olist arabic"><ol class="arabic">
-<li>
-<p>
-Находясь в Dive Organiser, выберите в главном меню <em>Database → Backup</em> и
-создайте резервную копию базы данных на рабочем столе. Это создаст ZIP-архив с
-именем DiveOrganiserxxxxx.dbf.
-</p>
-</li>
-<li>
-<p>
-Переименуйте файл в DiveOrganiserxxxxx.zip. Внутри ZIP-архива находится
-файл <em>DiveOrganiser.sdf</em>.
-</p>
-</li>
-<li>
-<p>
-Извлеките файл с расширением <em>.sdf</em> на рабочий стол вашего ПК.
-</p>
-</li>
-<li>
-<p>
-Пароль для доступа к ZIP-архиву <em>mares</em>.
-</p>
-</li>
-</ol></div>
-</div>
-<div class="sect2">
-<h3 id="S_ImportingDivinglog">17.4. Экспорт погружений из <strong>DivingLog 5.0 и 6.0</strong></h3>
-<div class="admonitionblock">
-<table><tr>
-<td class="icon">
-<img src="images/icons/divingloglogo.jpg" alt="Замечание" />
-</td>
-<td class="content">Лучший способ перенести журнал погружений из DivingLog в <em>Subsurface</em> - полная конвертация базы
-данных. Прочие форматы не содержат все детали погружений, такие как события замены газов, единицы
-измерения и т.п. При конвертации базы данных, вся эта информация будет доступна.</td>
-</tr></table>
-</div>
-<div class="paragraph"><p>Для переноса всех файлов из DivingLog в <em>Subsurface</em> выполните следующие шаги:</p></div>
-<div class="olist arabic"><ol class="arabic">
-<li>
-<p>
-В главном меню DivingLog выберите <em>File → Export → SQLite</em>
-</p>
-</li>
-<li>
-<p>
-Нажмите на кнопку <em>Установки</em>
-</p>
-</li>
-<li>
-<p>
-Установите <em>RTF2Plaintext</em> в значение <em>true</em>
-</p>
-</li>
-<li>
-<p>
-Закройте диалоговое окно <em>Установки</em>
-</p>
-</li>
-<li>
-<p>
-Нажмите кнопку Экспорт и укажите имя файла
-</p>
-</li>
-</ol></div>
-<div class="paragraph"><p>После выполнения этих шагов, откройте сохраненный файл с помощью <em>Subsurface</em>, все погружения будут
-преобразованы в наш собственный формат. Последним шагом не забудьте сохранить журнал.</p></div>
-</div>
-</div>
-</div>
-<div class="sect1">
-<h2 id="S_Appendix_D">18. ПРИЛОЖЕНИЕ Г: Экспорт электронных таблиц в CSV-формат</h2>
-<div class="sectionbody">
-<div class="paragraph"><p>Многие дайверы ведут журнал погружений в каком-либо электронном формате, зачастую в виде таблицы
-с разнообразными информационными полями. Такие журналы могут быть импортированы в <em>Subsurface</em>, но
-прежде их надо конвертировать в формат CSV.
-Эта глава описывает шаги по конвертации журнала из электронных таблиц в CSV-формат для последующего
-импорта в <em>Subsurface</em>. Создание CSV-файла довольно тривиальная задача, хотя это процедура различается
-для разных программ для работы с электронными таблицами.</p></div>
-<div class="paragraph"><p>Первым шагом вам нужно правильно организовать данные в таблице так, что первая строка содержала
-названия (заголовки) каждой из колонок и информация по каждому погружению хранилась в одной строке.
-<em>Subsurface</em> поддерживает множество полей (№ погружения, Дата, Время, Длительность, Напарник, Грузы,
-Метки и Примечания). Вы можете организовать данные, следуя простым правилам:</p></div>
-<div class="olist arabic"><ol class="arabic">
-<li>
-<p>
-Дата. Используйте один из форматов: yyyy-mm-dd, dd.mm.yyyy, mm/dd/yyyy
-</p>
-</li>
-<li>
-<p>
-Длительность. Формат должен быть вида мин:сек.
-</p>
-</li>
-<li>
-<p>
-Система мер. Нужно использовать только одну систему (т.е. нельзя использовать фунты и градусы Цельсия)
-</p>
-</li>
-<li>
-<p>
-Метки и партнеры. Значения должны быть разделены запятой.
-</p>
-</li>
-<li>
-<p>
-GPS-координаты. Следует использоваться десятичные доли градусов, т.е. e.g. 30.22496 30.821798
-</p>
-</li>
-</ol></div>
-<div class="sect2">
-<h3 id="_em_libreoffice_calc_em_и_em_openoffice_calc_em">18.1. <em>LibreOffice Calc</em> и <em>OpenOffice Calc</em></h3>
-<div class="paragraph"><p>Эти программы для работы с электронными таблицами являются частью офисных пакетов с открытым кодом.
-Работы с <em>LibreOffice</em> и <em>OpenOffice</em> очень схожа. Формат времени должен быть вида минуты:секунды - [mm]:ss, а формат даты одним из yyyy-mm-dd, dd.mm.yyyy, mm/dd/yyyy. Типичный журнал может выгядеть так:</p></div>
-<div class="imageblock" style="text-align:center;">
-<div class="content">
-<img src="images/LOffice_spreadsheetdata.jpg" alt="Рисунок: Электронная таблица" />
-</div>
-</div>
-<div class="paragraph"><p>Для экспорта файла CSV из LibreOffice в меню выберите <em>Файл → Сохранить как</em>. В появившемся диалоге выберите тип файла <em>Текст CSV (.csv)</em> и выберите опцию <em>Редактировать настройки фильтра</em>.</p></div>
-<div class="imageblock" style="text-align:center;">
-<div class="content">
-<img src="images/LOffice_save_as_options.jpg" alt="Рисунок: Сохранение CSV-файла" />
-</div>
-</div>
-<div class="paragraph"><p>После нажатия на кнопку <em>Сохранить</em>, выберите <em>Tab</em> в качестве разделителя полей, чтобы избежать конфликтов при использовании запятой в качестве десятичного разделителя, и нажмите <em>OK</em>.</p></div>
-<div class="imageblock" style="text-align:center;">
-<div class="content">
-<img src="images/LOffice_field_options.jpg" alt="Рисунок: Настройки фильтра CSV" />
-</div>
-</div>
-<div class="paragraph"><p>Импортируйте только что сохраненный CSV-файл как описано в главе <a href="#S_ImportingCSVDives">Импорт погружений в CSV-формате</a>.</p></div>
-</div>
-<div class="sect2">
-<h3 id="_microsoft_em_excel_em">18.2. Microsoft <em>Excel</em></h3>
-<div class="paragraph"><p><em>Excel</em> не предоставляет возможности указать разделитель полей (в руководстве Microsoft он называется
-<em>разделитель списка</em>); сделать это можно из <em>Панели управления</em>. После изменения символа-разделителя,
-его будут использовать все программы на компьютере. Вы всегда можете вернуться к предыдущему значению,
-выполнив следующую процедуру:</p></div>
-<div class="ulist"><ul>
-<li>
-<p>
-В Windows нажмите кнопку <strong>Пуск</strong> и выберите <em>Панель управления</em> в правой части окна.
-</p>
-</li>
-<li>
-<p>
-Выберите <em>Региональные настройки</em>.
-</p>
-</li>
-<li>
-<p>
-Выполните следующее:
-</p>
-<div class="ulist"><ul>
-<li>
-<p>
-Для Windows 7, выберите вкладку <em>Формат) и нажмите _Настроить</em>
-</p>
-</li>
-<li>
-<p>
-Для Windows XP, выберите <em>Параметры региона</em> и нажмите <em>Настроить</em>
-</p>
-</li>
-</ul></div>
-</li>
-<li>
-<p>
-Введите новый символ-разделитель в поле <em>Разделитель списка</em>. Чтобы указать символ табуляции, введите слово TAB.
-</p>
-</li>
-<li>
-<p>
-Последовательно нажмите кнопку <em>ОК</em> дважды.
-</p>
-</li>
-</ul></div>
-<div class="paragraph"><p>Ниже приведен внешний вид <em>Панели управления</em>:</p></div>
-<div class="imageblock" style="text-align:center;">
-<div class="content">
-<img src="images/Win_SaveCSV2.jpg" alt="Рисунок: Разделитель списков в Windows" />
-</div>
-</div>
-<div class="paragraph"><p>Чтобы экспортировать журнал погружений в CSV формат:</p></div>
-<div class="paragraph"><p>Откройте журнал в <em>Excel</em>, нажмите на круглую кнопку с логотипом Windows в верхнем левом углу и выберите <em>Сохранить как</em></p></div>
-<div class="imageblock" style="text-align:center;">
-<div class="content">
-<img src="images/Win_SaveCSV1.jpg" alt="Рисунок: сохранить как в Excel" />
-</div>
-</div>
-<div class="paragraph"><p>Нажимайте непосредственно на пункт <em>Сохранить как</em>, а не на стрелочку справа от него. Это откроет диалоговое окно для сохранения таблицы в альтернативном формате. Из выпадающего списка в нижней части диалога выберите тип CSV, укажите папку для сохранения.</p></div>
-<div class="imageblock" style="text-align:center;">
-<div class="content">
-<img src="images/Win_SaveCSV3.jpg" alt="Рисунок: диалоговое окна сохранения CSV-файла в Excel" />
-</div>
-</div>
-<div class="paragraph"><p>Нажмите кнопку <em>Сохранить</em>. Импортируйте только что сохраненный CSV-файл как описано в главе <a href="#S_ImportingCSVDives">Импорт погружений в CSV-формате</a>.</p></div>
-</div>
-</div>
-</div>
-<div class="sect1">
-<h2 id="S_APPENDIX_E">19. ПРИЛОЖЕНИЕ Д: Создание собственных шаблонов печати</h2>
-<div class="sectionbody">
-<div class="paragraph"><p><em>Subsurface</em> предоставляет механизм по созданию и изменению шаблонов для печати погружений, что
-позволяет гибко менять положение информации на странице. Шаблоны используют HTML и набор инструкций
-библиотеки Grantlee.</p></div>
-<div class="paragraph"><p>Доступ к шаблонам осуществляется из диалога печати (см. рисунок В ниже).</p></div>
-<div class="imageblock" style="text-align:center;">
-<div class="content">
-<img src="images/Print1_f22.jpg" alt="Рисунок: Диалог печати" />
-</div>
-</div>
-<div class="paragraph"><p>Кнопки под выпадающим списком шаблонов позволяют <em>Редактировать</em>, <em>Удалить</em>, выполнить <em>Импорт</em> и
-<em>Экспорт</em>. Новые или измененные шаблоны хранятся в той же директории, что и журнал, с которым вы работаете
-в данный момент. Чтобы изменить существующий шаблон, выберите его названиек в списке и нажмите
-кнопку <em>Редактировать</em>.</p></div>
-<div class="paragraph"><p>Окно редактирования шаблона состоит из трех вкладок:</p></div>
-<div class="imageblock" style="text-align:center;">
-<div class="content">
-<img src="images/Template1_f22.jpg" alt="Рисунок: окно редактирования шаблона" />
-</div>
-</div>
-<div class="paragraph"><p>1) Вкладка <em>Стиль</em> (рисунок <strong>А</strong> выше) управляет шрифтами, междстрочным интервалом и палитрой цветов.</p></div>
-<div class="paragraph"><p>2) Вкладка <em>Цвета</em> (рисунок <strong>В</strong> выше) позволяет переопределить цвета шаблона</p></div>
-<div class="paragraph"><p>3) Вкладка <em>Шаблон</em> (рисунок ниже) дает вам возможность описать шаблон на языке HTML с использованием
- примитивов библиотеки Grantlee.</p></div>
-<div class="imageblock" style="text-align:center;">
-<div class="content">
-<img src="images/Template2_f22.jpg" alt="Рисунок: Вкладка редактирования шаблона" />
-</div>
-</div>
-<div class="paragraph"><p>Вы можете адаптировать существующие шаблоны под свои нужды и сохранить их в директории журнала погружений.
-После окончания редактирования, используйте функцию <em>Экспорт</em>, чтобы сохранить шаблон с новым именем.</p></div>
-<div class="paragraph"><p>Чтобы шаблон правильно отображался, в нем должны присутствовать следующие элементы:</p></div>
-<div class="sect2">
-<h3 id="_главный_цикл_погружений">19.1. Главный цикл погружений</h3>
-<div class="paragraph"><p><em>Subsurface</em> экспортирует в <em>Grantlee</em> список погружений под именем <strong>dives</strong>. Для итерации по погружениям:</p></div>
-<div class="literalblock">
-<div class="title">template.html</div>
-<div class="content">
-<pre><code> {% for dive in dives %}
- <h1> {{ dive.number }} </h1>
- {% endfor %}</code></pre>
-</div></div>
-<div class="literalblock">
-<div class="title">output.html</div>
-<div class="content">
-<pre><code> <h1> 1 </h1>
- <h1> 2 </h1>
- <h1> 3 </h1></code></pre>
-</div></div>
-<div class="paragraph"><p>Дополнительную информация о <em>Grantlee</em> вы можете найти <a href="http://www.grantlee.org/apidox/for_themers.html">здесь</a>.</p></div>
-</div>
-<div class="sect2">
-<h3 id="_переменные_доступные_в_grantlee">19.2. Переменные, доступные в Grantlee</h3>
-<div class="paragraph"><p><em>Subsurface</em> экспортирует только часть информации о погружении:</p></div>
-<div class="tableblock">
-<table rules="all"
-width="100%"
-frame="border"
-cellspacing="0" cellpadding="4">
-<col width="50%" />
-<col width="50%" />
-<tbody>
-<tr>
-<td align="left" valign="top"><p class="table"><strong>Название</strong></p></td>
-<td align="left" valign="top"><p class="table"><strong>Описание</strong></p></td>
-</tr>
-<tr>
-<td align="left" valign="top"><p class="table">number</p></td>
-<td align="left" valign="top"><p class="table">(<strong>int</strong>) номер погружения</p></td>
-</tr>
-<tr>
-<td align="left" valign="top"><p class="table">id</p></td>
-<td align="left" valign="top"><p class="table">(<strong>int</strong>) уникальный ID дайва, должен использоваться для получения профиляe</p></td>
-</tr>
-<tr>
-<td align="left" valign="top"><p class="table">date</p></td>
-<td align="left" valign="top"><p class="table">(<strong>string</strong>) дата погружения</p></td>
-</tr>
-<tr>
-<td align="left" valign="top"><p class="table">time</p></td>
-<td align="left" valign="top"><p class="table">(<strong>string</strong>) время погружения</p></td>
-</tr>
-<tr>
-<td align="left" valign="top"><p class="table">location</p></td>
-<td align="left" valign="top"><p class="table">(<strong>string</strong>) местоположение</p></td>
-</tr>
-<tr>
-<td align="left" valign="top"><p class="table">duration</p></td>
-<td align="left" valign="top"><p class="table">(<strong>string</strong>) длительность</p></td>
-</tr>
-<tr>
-<td align="left" valign="top"><p class="table">depth</p></td>
-<td align="left" valign="top"><p class="table">(<strong>string</strong>) глубина погружения</p></td>
-</tr>
-<tr>
-<td align="left" valign="top"><p class="table">divemaster</p></td>
-<td align="left" valign="top"><p class="table">(<strong>string</strong>) информация о дайв-мастере</p></td>
-</tr>
-<tr>
-<td align="left" valign="top"><p class="table">buddy</p></td>
-<td align="left" valign="top"><p class="table">(<strong>string</strong>) информация о партнерах</p></td>
-</tr>
-<tr>
-<td align="left" valign="top"><p class="table">airTemp</p></td>
-<td align="left" valign="top"><p class="table">(<strong>string</strong>) температура воздуха</p></td>
-</tr>
-<tr>
-<td align="left" valign="top"><p class="table">waterTemp</p></td>
-<td align="left" valign="top"><p class="table">(<strong>string</strong>) температура воды</p></td>
-</tr>
-<tr>
-<td align="left" valign="top"><p class="table">notes</p></td>
-<td align="left" valign="top"><p class="table">(<strong>string</strong>) примечания к погружению</p></td>
-</tr>
-<tr>
-<td align="left" valign="top"><p class="table">rating</p></td>
-<td align="left" valign="top"><p class="table">(<strong>int</strong>) рейтинг погружения (от 0 до 5)</p></td>
-</tr>
-<tr>
-<td align="left" valign="top"><p class="table">sac</p></td>
-<td align="left" valign="top"><p class="table">(<strong>string</strong>) значение SAC</p></td>
-</tr>
-<tr>
-<td align="left" valign="top"><p class="table">tags</p></td>
-<td align="left" valign="top"><p class="table">(<strong>string</strong>) все метки погружения, перечисленные через запятую</p></td>
-</tr>
-<tr>
-<td align="left" valign="top"><p class="table">gas</p></td>
-<td align="left" valign="top"><p class="table">(<strong>string</strong>) используемые баллоны</p></td>
-</tr>
-</tbody>
-</table>
-</div>
-<div class="paragraph"><p><em>Subsurface</em> также экспортирует структуру <strong>template_options</strong>. Эти данные должны использоваться
-в определении стилей CSS. В таблице ниже приведены доступные переменные:</p></div>
-<div class="tableblock">
-<table rules="all"
-width="100%"
-frame="border"
-cellspacing="0" cellpadding="4">
-<col width="50%" />
-<col width="50%" />
-<tbody>
-<tr>
-<td align="left" valign="top"><p class="table"><strong>Название</strong></p></td>
-<td align="left" valign="top"><p class="table"><strong>Описание</strong></p></td>
-</tr>
-<tr>
-<td align="left" valign="top"><p class="table">font</p></td>
-<td align="left" valign="top"><p class="table">(<strong>string</strong>) семество шрифтов</p></td>
-</tr>
-<tr>
-<td align="left" valign="top"><p class="table">borderwidth</p></td>
-<td align="left" valign="top"><p class="table">(<strong>int</strong>) значение border-width динамически высчитывается как 0.1% от ширины страницы, минимум 1px</p></td>
-</tr>
-<tr>
-<td align="left" valign="top"><p class="table">font_size</p></td>
-<td align="left" valign="top"><p class="table">(<strong>double</strong>) размер шрифта в vw (viewport width), в диапазоне от 1.0 до 2.0</p></td>
-</tr>
-<tr>
-<td align="left" valign="top"><p class="table">line_spacing</p></td>
-<td align="left" valign="top"><p class="table">(<strong>double</strong>) расстояние между строками, диапазон от 1.0 до 3.0</p></td>
-</tr>
-<tr>
-<td align="left" valign="top"><p class="table">color1</p></td>
-<td align="left" valign="top"><p class="table">(<strong>string</strong>) цвет фона</p></td>
-</tr>
-<tr>
-<td align="left" valign="top"><p class="table">color2</p></td>
-<td align="left" valign="top"><p class="table">(<strong>string</strong>) основной цвет ячейки таблицы</p></td>
-</tr>
-<tr>
-<td align="left" valign="top"><p class="table">color3</p></td>
-<td align="left" valign="top"><p class="table">(<strong>string</strong>) дополнительный цвет ячейки таблицы</p></td>
-</tr>
-<tr>
-<td align="left" valign="top"><p class="table">color4</p></td>
-<td align="left" valign="top"><p class="table">(<strong>string</strong>) основной цвет текста</p></td>
-</tr>
-<tr>
-<td align="left" valign="top"><p class="table">color5</p></td>
-<td align="left" valign="top"><p class="table">(<strong>string</strong>) дополнительный цвет текста</p></td>
-</tr>
-<tr>
-<td align="left" valign="top"><p class="table">color6</p></td>
-<td align="left" valign="top"><p class="table">(<strong>string</strong>) цвет рамки</p></td>
-</tr>
-</tbody>
-</table>
-</div>
-<div class="literalblock">
-<div class="title">template.html</div>
-<div class="content">
-<pre><code> border-width: {{ template_options.borderwidth }}px;</code></pre>
-</div></div>
-<div class="literalblock">
-<div class="title">output.html</div>
-<div class="content">
-<pre><code> border-width: 3px;</code></pre>
-</div></div>
-<div class="paragraph"><p>Дополнительно <em>Subsurface</em> экспортирует переменную <strong>print_options</strong>. У этой переменной одно поле.</p></div>
-<div class="tableblock">
-<table rules="all"
-width="100%"
-frame="border"
-cellspacing="0" cellpadding="4">
-<col width="50%" />
-<col width="50%" />
-<tbody>
-<tr>
-<td align="left" valign="top"><p class="table"><strong>Название</strong></p></td>
-<td align="left" valign="top"><p class="table"><strong>Описание</strong></p></td>
-</tr>
-<tr>
-<td align="left" valign="top"><p class="table">grayscale</p></td>
-<td align="left" valign="top"><p class="table">Используйте <em>CSS</em> фильтры для преобразования страницы в черно-белый цвет (необходимо добавлять в стиль body, чтобы сделать возможной черно-белую печать)</p></td>
-</tr>
-</tbody>
-</table>
-</div>
-<div class="literalblock">
-<div class="title">template.html</div>
-<div class="content">
-<pre><code> body {
- {{ print_options.grayscale }};
- }</code></pre>
-</div></div>
-<div class="literalblock">
-<div class="title">output.html</div>
-<div class="content">
-<pre><code> body {
- -webkit-filter: grayscale(100%);
- }</code></pre>
-</div></div>
-</div>
-<div class="sect2">
-<h3 id="_определенные_css_селекторы">19.3. Определенные CSS-селекторы</h3>
-<div class="paragraph"><p>Так как профиль погружения добавляется после рендеринга, <em>Subsurface</em> использует специальные <em>CSS</em>-селекторы
-для поиска в сгенерированном HTML. Вам понадобится добавить селекторы из табдицы ниже.</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>Селектор</strong></p></td>
-<td align="left" valign="top"><p class="table"><strong>Тип</strong></p></td>
-<td align="left" valign="top"><p class="table"><strong>Описание</strong></p></td>
-</tr>
-<tr>
-<td align="left" valign="top"><p class="table">dive_{{ dive.id }}</p></td>
-<td align="left" valign="top"><p class="table">id</p></td>
-<td align="left" valign="top"><p class="table">используется для получения соответствующего профиля погружения</p></td>
-</tr>
-<tr>
-<td align="left" valign="top"><p class="table">diveProfile</p></td>
-<td align="left" valign="top"><p class="table">class</p></td>
-<td align="left" valign="top"><p class="table">каждый div-элемент, содержащий профиль, должен иметь этот селектор класса в дополнение к dive_{{ dive.id }} id-селектору</p></td>
-</tr>
-<tr>
-<td align="left" valign="top"><p class="table">dontbreak</p></td>
-<td align="left" valign="top"><p class="table">class</p></td>
-<td align="left" valign="top"><p class="table">предотвращает div с этим классом от разбиаения на две страницы, может быть использован только в потоковых шаблонах (когда data-numberofdives = 0)</p></td>
-</tr>
-</tbody>
-</table>
-</div>
-</div>
-</div>
-</div>
-<div class="sect1">
-<h2 id="_приложение_е_частые_вопросы_и_ответы">20. ПРИЛОЖЕНИЕ Е: Частые вопросы и ответы</h2>
-<div class="sectionbody">
-<div class="paragraph"><p>ВАЖНО: Отображение профиля погружения не поддерживается в потоковых шаблонах (когда data-numberofdives = 0)</p></div>
-<div class="sect2">
-<h3 id="_специальные_атрибуты">20.1. Специальные атрибуты</h3>
-<div class="paragraph"><p>Существует два способа рендеринга - указанное количество погружений на странице и потоковое отображение
-(_Subsurface пытается разместить как можно больще погружений на странице).</p></div>
-<div class="paragraph"><p>Атрибут <strong>data-numberofdives</strong> указывает сколько погружений должно быть отображено на странице</p></div>
-<div class="ulist"><ul>
-<li>
-<p>
-отобразить 6 погружений на странице:
-</p>
-</li>
-</ul></div>
-<div class="literalblock">
-<div class="content">
-<pre><code> <body data-numberofdives = 6></code></pre>
-</div></div>
-<div class="ulist"><ul>
-<li>
-<p>
-отобразаить как можно больше погружений:
-</p>
-</li>
-</ul></div>
-<div class="literalblock">
-<div class="content">
-<pre><code> <body data-numberofdives = 0></code></pre>
-</div></div>
-<div class="paragraph"><p>ВАЖНО: Все размеры CSS должны быть в относительных единицах, чтобы поддерживать печать на бумаге любого размера.</p></div>
-</div>
-</div>
-</div>
-<div class="sect1">
-<h2 id="_приложение_ж_чаво">21. ПРИЛОЖЕНИЕ Ж: ЧаВо</h2>
-<div class="sectionbody">
-<div class="sect2">
-<h3 id="SAC_CALCULATION">21.1. Похоже, что <em>Subsurface</em> неправильно считает расход газов и SAC</h3>
-<div class="paragraph"><p><em>Вопрос</em>: Я погружался с баллоном 12.2л, начальное давление 220бар, конечное - 100 бар. Мои расчеты
-SAC не совпадают со значением в <em>Subsurface</em>. Возможно ли, что <em>Subsurface</em> считает неверно?</p></div>
-<div class="paragraph"><p><em>Ответ</em>: Нет. <em>Subsurface</em> рассчитывает расход газа иначе, и даже лучше, чем вы
-ожидаете. В частности, мы принимаем во внимание несжимаемость газа.
-Традиционно, расход и SAC считаются по формуле:
-<code>расход = объем баллона x (начальное давление - конечное давление)</code></p></div>
-<div class="paragraph"><p>и это правильно для идеального газа, и это то, чему вас учили в теории. Но
-"идеального газа" не существует, а реальные газы сжимаются нелинейно с ростом
-давления. Также вы упускаете тот факт, что давление одной атмосферы не
-равняется одному бар. Поэтому <strong>реальная</strong> формула будет:</p></div>
-<div class="paragraph"><p><code>расход = (объем_воздуха_в_начале - объем_воздуха_в_конце)</code></p></div>
-<div class="paragraph"><p>где объем воздуха это <strong>не</strong> просто "произведение объема на давление". Это
-комбинация из: "примем во внимание сжимаемость газа" (что в принципе не играет
-роли до 220 бар, это становится существенным для баллонов с давлением 300
-бар), и "переведем бар в атмосферы" (это основная причина несоответствия).
-Напомним: одна атмосфера равняется ~1.013 бар, так что даже без сжимаемости ваш расход газа составит:</p></div>
-<div class="paragraph"><p><code>12.2*((220-100)/1.013)</code></p></div>
-<div class="paragraph"><p>что будет около 1445, а не 1464. Т.е. в ваших расчета было лишних 19 литров
-из-за разницы между 1 бар и 1 АТМ. Сжимаемость начинает играть свою роль при
-давлениях свыше 200 бар и уменьшит расход еще приблизительно на 8 литров, т.о.
-вы расходовали около 1437 л при давлении на поверхности.</p></div>
-<div class="paragraph"><p>Поэтому радуйтесь: ваш SAC лучше, чем вы считали. Либо огорчайтесь: у вас в
-баллоне меньше воздуха, чем вы думали. И как уже упоминалось, "меньше чем
-думали" начинает работать при довольно высоком давлении. Баллон при 400 бар не
-содержит в два раза больше воздуха чем при 200 бар. При низких же давлениях
-воздух ведет себя почти как идеальный газ.</p></div>
-</div>
-<div class="sect2">
-<h3 id="_на_некоторых_профилях_наблюдаются_различия_во_времени_с_данных_дайв_компьютера_8230">21.2. На некоторых профилях наблюдаются различия во времени с данных дайв-компьютера…</h3>
-<div class="paragraph"><p><em>Subsurface</em> игнорирует поверхностное время при различных расчетах (средняя глубина, время дайва, SAC и т.д)
-<em>Вопрос</em>: почему время погружения на дайв-компьютере и в <em>Subsurface</em> различаются?</p></div>
-<div class="paragraph"><p><em>Ответ</em>: Например, вы решили выполнить проверку плавучести (достаточно глубокую, чтобы
-компьютер посчитал это началом погружения), после чего всплыли на поверхность и еще 5 минут
-прождали своего напарника. Ваш дайв-компьютер может посчитать длительность этого погружения
-50 минут, потому что компьютер находится в режиме погружения, а <em>Subsurface</em> посчитает
-длительность этого дайва равной 45 минутам, потому что вы действительно погружались 45 минут.
-Особенно это заметно, если вы обучаете новичков OW, вы долгое время находитесь
-в воде, но основное время проводите на поверхности. И это нельзя считать долгим погружением.</p></div>
-</div>
-<div class="sect2">
-<h3 id="_при_загрузке_отсутствуют_некоторые_погружения">21.3. При загрузке отсутствуют некоторые погружения</h3>
-<div class="paragraph" id="DC_HISTORY"><p><em>Вопрос</em>: У меня не получается загрузить все мои погружения, только недавние. При этом руководство
-по моему дайв-компьютеру утверждает, что он хранит историю ,например, 999 погружений.</p></div>
-<div class="paragraph"><p><em>Ответ</em>: История погружений и профиль погружения - две большие разницы. История
-хранит только общее количество погружений и общее время, проведенное под водой.
-С другой стороны, журнал хранит профили погружений, но объем его памяти
-ограничен. Точно количество хранимых профилей зависит от частоты дискретизации
-и длительности погружений. Как только память переполняется, старые погружения
-перетираются новыми. Поэтому мы можем загрузить последний 13, 30 или 199
-погружений.</p></div>
-<div class="paragraph"><p>Если вы выгрузили погружения в разные программы для ведения журналов перед тем как они были
-перезаписаны, есть вероятность, что <em>Subsurface</em> сможет импортировать их. Однако, если погружения
-были только в вашем дайв-компьютере, они не могут быть восстановлены после того как были
-перезаписаны новыми погружениями.</p></div>
-</div>
-</div>
-</div>
-</div>
-<div id="footnotes"><hr /></div>
-<div id="footer">
-<div id="footer-text">
-Последнее обновление 2015-12-15 13:35:30 PST
-</div>
-</div>
-</body>
-</html>
+<!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="ru"> +<head> +<meta http-equiv="Content-Type" content="application/xhtml+xml; charset=UTF-8" /> +<meta name="generator" content="AsciiDoc 8.6.9" /> +<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; } + + +@media screen { + body { + max-width: 50em; /* approximately 80 characters wide */ + margin-left: 16em; + } + + #toc { + position: fixed; + top: 0; + left: 0; + bottom: 0; + width: 13em; + padding: 0.5em; + padding-bottom: 1.5em; + margin: 0; + overflow: auto; + border-right: 3px solid #f8f8f8; + background-color: white; + } + + #toc .toclevel1 { + margin-top: 0.5em; + } + + #toc .toclevel2 { + margin-top: 0.25em; + display: list-item; + color: #aaaaaa; + } + + #toctitle { + margin-top: 0.5em; + } +} +</style> +<script type="text/javascript"> +/*<+'])'); + // 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">Руководство пользователя</span></p></div> +<div class="paragraph"><p><strong>Авторы документа</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>Версия 4.5, Октябрь 2015</em></span></p></div> +<div class="paragraph"><p>Вас приветствует <em>Subsurface</em>, современная программа для ведения журнала +погружений с возможностями организации, документирования, анализа и печати +погружений для SCUBA и фридайверов. <em>Subsurface</em> предлагает множество +преимуществ по сравнению с другими решениями:</p></div> +<div class="ulist"><ul> +<li> +<p> +Вам нужен удобный инструмент для ведения журнала рекреационных погружений + даже без использования дайв-компьютера? +</p> +</li> +<li> +<p> +Вы используете два дайв-компьютера различных производителей, каждый со + своим программным обеспечением, для загрузки профилей? Вы ныряете с + ребризером и на открытом цикле? Используете Reefnet Sensus ботом-таймер + совместно с дайв-компьютером? <em>Subsurface</em> предоставляет общий + унифицированный интерфейс для загрузки журналов со всех этих устройств, + хранения и анализа профилей. +</p> +</li> +<li> +<p> +Вы используете более одной операционной системы? <em>Subsurface</em> полностью + совместим с Mac, Linux и Windows, позволяя вам получить доступ к журналу + на любой операционной системе одинаковым способом. +</p> +</li> +<li> +<p> +Вы используете Linux или Mac, а для вашего дайв-компьютер есть программное + обеспечение только для Windows (например, Mares)? <em>Subsurface</em> дает вам + возможность работать с профилями погружения на других операционных системах. +</p> +</li> +<li> +<p> +Вам нужен интуитивно понятный графический планировщик погружений, который + принимает во внимание ранее выполненные погружения? +</p> +</li> +<li> +<p> +Вам нужно хранить или создавать резервные копии журнала погружения в Интернет, с + возможностью доступа к журналу откуда угодно, используя веб-броузер? +</p> +</li> +</ul></div> +<div class="paragraph"><p>Установочные образы <em>Subsurface</em> доступны для Windows PC (Win XP и позже), +Intel Mac (OS/X) и множества дистрибутивов Linux. <em>Subsurface</em> может быть +также скомпилирован на множестве других платформ, где доступны Qt и +libdivecomputer.</p></div> +<div class="paragraph"><p>Этот документ описывает использование программы <em>Subsurface</em>. Для установки +обратитесь к странице <em>Downloads</em> на <a href="http://subsurface-divelog.org/">веб-сайте +<em>Subsurface</em></a>. Вы можете обсудить эту программу, отправив email на адрес +<a href="mailto:subsurface@subsurface-divelog.org">списка рассылки</a> и сообщить об ошибках на сайте +<a href="http://trac.hohndel.org">треккера ошибок</a>. Инструкции по самостоятельной сборке +<em>Subsurface</em> и, если необходимо, зависимостей, описаны в файле INSTALL, распространяемом +вместе с исходными текстами.</p></div> +<div class="paragraph"><p><strong>Аудитория</strong>: Рекреационные, технические и коммерческие дайверы, фридайверы</p></div> +<div id="toc"> + <div id="toctitle">Содержание</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="_работа_с_этим_руководством">1. Работа с этим руководством</h2> +<div class="sectionbody"> +<div class="paragraph"><p>Если руководство открыто из <em>Subsurface</em>, то вы не увидите никаких элементов +управления. Однако вам доступны две удобных функции:</p></div> +<div class="ulist"><ul> +<li> +<p> +<em>ПОИСК</em> активируется нажатием комбинации клавиш control-F или command-F. + Используйте текстовое поле в нижней части экрана для поиска нужной информации + в руководстве. Справа от поля поиска кнопки с изображением стрелок вверх и + вниз позволяют перемещаться по результатам поиска. +</p> +</li> +</ul></div> +<div class="imageblock" style="text-align:center;"> +<div class="content"> +<img src="images/usermanualfunctions.jpg" alt="Руководство пользователя" /> +</div> +</div> +<div class="ulist"><ul> +<li> +<p> +<em>ИСТОРИЯ ПЕРЕХОДОВ</em>. Как и в случае работы с веб-браузером, вы можете + переходить по ссылкам в руководстве. Контекстное меню (его вы можете вызвать + правым щелчком мыши) позволяет вам перемещаться по истории переходов вперед и + назад. +</p> +</li> +</ul></div> +</div> +</div> +<div class="sect1"> +<h2 id="S_UserSurvey">2. Опрос пользователей</h2> +<div class="sectionbody"> +<div class="paragraph"><p>Для того, чтобы <em>Subsurface</em> удовлетворял всем потребностям наших пользователей, +нам важно знать о вас. После нескольких дней использования <em>Subsurface</em> предложит +вам заполнить опросник. Вы сами решаете заполнять ли его и какую информацию вы готовы +предоставить. Эта информация помогает развивать проект в правильном направлении. +Если вы отправите анкету или решите отказаться, в обоих случаях <em>Subsurface</em> больше +не будет надоедать вам. Если в будущем ваши привычки или пожелания изменятся, +вы можете вызвать опросник, запустив <em>Subsurface</em> с параметром +командной строки <em>--survey</em>.</p></div> +</div> +</div> +<div class="sect1"> +<h2 id="S_StartUsing">3. Начало работы с программой</h2> +<div class="sectionbody"> +<div class="paragraph"><p>Окно <em>Subsurface</em> обычно разделено на четыре панели с <strong>Главным меню</strong> (Файл +Импорт Журнал Вид Помощь) в верхней части окна (Windows и Linux) или в верхней +части экрана (Mac и Ubuntu Unity). Эти четыре панели:</p></div> +<div class="olist arabic"><ol class="arabic"> +<li> +<p> +<strong>Список погружений</strong> в левой нижней части, в котором отображаются все +погружения из журнала. Погружение можно выбрать и подсветить нажав на нем +мышкой. В большинстве случаев между погружениями можно перемещаться клавишами +вверх/вниз. Список погружений - важный инструмент управления журналом. +</p> +</li> +<li> +<p> +<strong>Карта погружений</strong> в правой нижней части. В ней показываются места +погружений на карте мира. Карта отцентрирована по местоположению последнего +выбранного погружения в <strong>Списке погружений</strong> +</p> +</li> +<li> +<p> +<strong>Информация о погружении</strong> в левой верхней части. Предоставляет наиболее +полную информацию о дайве, выбранном в <strong>Списке погружений</strong>, включая статистику +одного или всех выбранных погружений. +</p> +</li> +<li> +<p> +<strong>Профиль погружения</strong> в правой верхней части. Показывает графический профиль +выбранного погружения. +</p> +</li> +</ol></div> +<div class="paragraph"><p>Разделители панелей можно двигать для того, чтобы изменить их размер. +<em>Subsurface</em> запоминает положение разделителей так, что при следующем запуске +программы размер панелей будет таким же, как и в предыдущий раз.</p></div> +<div class="paragraph"><p>Если в <strong>Списке погружений</strong> выбран дайв, то в соответствующих панелях +отображается местоположение, подробная информация и профиль этого погружения. +Если же подсвечено более одного погружения, то последнее подсвеченное +считается выбранным, но на вкладке <strong>Статистика</strong> информационной панели +показывается сводная информация _всех подсвеченных_ дайвов (минимальная, +максимальная и средняя глубина, длительность, температура воды и SAC; +общее время на дне и количество погружений).</p></div> +<div class="imageblock" id="S_ViewPanels" style="text-align:center;"> +<div class="content"> +<img src="images/main_window_f22.jpg" alt="Главное окно" /> +</div> +</div> +<div class="paragraph"><p>Вы можете выбрать какие из панелей показывать на главном экране. Для этого +перейдите в пункт меню <strong>Вид</strong> и выберите один из вариантов отображения:</p></div> +<div class="paragraph"><p><strong>Все</strong>: показываются все четыре панели, как на картинке выше.</p></div> +<div class="paragraph"><p><strong>Список</strong>: показать только список погружений.</p></div> +<div class="paragraph"><p><strong>Профиль</strong>: отобразить только профиль выбранного погружения.</p></div> +<div class="paragraph"><p><strong>Информация</strong>: показать только информацию о выбранном дайве и статистику по +подсвеченным погружениям.</p></div> +<div class="paragraph"><p><strong>Карта</strong>: показать карту, отцентрированную по последнему выбранному погружению.</p></div> +<div class="paragraph"><p>Как и большинство других функций, доступных из главного меню, вид главного +экрана можно переключать комбинацией клавиш. Эти комбинации указаны рядом с +соответствующими пунктами меню. В зависимости от операционной системы и +выбранного языка интерфейса эти комбинации могут различаться, поэтому они не +перечислены в данном руководстве.</p></div> +<div class="paragraph"><p>При первом запуске программы главное окно не отображает вообще никакой +информации. Дело в том, что в этот момент еще нет данных о погружениях. В +следующих главах будут описаны шаги по созданию нового журнала погружений.</p></div> +</div> +</div> +<div class="sect1"> +<h2 id="S_NewLogbook">4. Создание нового журнала</h2> +<div class="sectionbody"> +<div class="paragraph"><p>В главном меню выберите <em>Файл → Новый журнал</em>. Все существующие данные +очищаются чтобы можно было добавлять новую информацию. Если в открытом журнале +были сделаны изменения, вам будет предложено сохранить данные перед +созданием нового журнала.</p></div> +</div> +</div> +<div class="sect1"> +<h2 id="S_GetInformation">5. Сохранение погружений в журнале</h2> +<div class="sectionbody"> +<div class="paragraph"><p>Теперь, когда создан новый журнал, очень просто добавить погружения к нему. +<em>Subsurface</em> предлагает несколько способов добавления погружений, которые подробно +описаны далее:</p></div> +<div class="paragraph"><p>1) Если вы ведете бумажный журнал, храните информацию в электронной таблице или +используете другой ручной способ, данные о погружениях могут быть добавлены с +помощью одного из перечисленных вариантов:</p></div> +<div class="ulist"><ul> +<li> +<p> +Ввод данных о погружении вручную. Это может оказаться полезным, если вы не + используете дайв-компьютер и погружения были записаны в бумажном журнале. Смотрите: + <a href="#S_EnterData">Ввод данных о погружении вручную</a> +</p> +</li> +<li> +<p> +Импорт данных из журнала, который велся в электронной таблице или в виде CSV-файла. + Обратитесь к главам <a href="#S_Appendix_D">ПРИЛОЖЕНИЕ Г: Экспорт таблиц в CSV формат</a> и + <a href="#S_ImportingCSVDives">Импорт погружений в CSV формате</a>. +</p> +</li> +</ul></div> +<div class="paragraph"><p>2) Если ваши погружения записаны в дайв-компьютере, вы можете получить значительное + количество информации, включая профиль погружения. Погружения могут быть импортированы + из:</p></div> +<div class="ulist"><ul> +<li> +<p> +Непосредственно дайв-компьютера. Смотрите главу <a href="#S_ImportDiveComputer">Импорт данных нового погружения из дайв-компьютера</a> или +</p> +</li> +<li> +<p> +Стороннего программного обеспечения, распространяемого производителями дайв-компьютеров. + Обратитесь к <a href="#S_ImportingAlienDiveLogs">Импорт погружений из других источников и форматов данных</a>. +</p> +</li> +<li> +<p> +Импорт из электронных таблиц и CSV-файлов, содержащих профили погружений. Смотрите + <a href="#S_ImportingCSVDives">Импорт погружений в CSV-формате из дайв-компьютеров и другого ПО для ведения журналов</a>. +</p> +</li> +</ul></div> +<div class="sect2"> +<h3 id="S_EnterData">5.1. Ввод данных о погружении вручную</h3> +<div class="paragraph"><p>Этот способ обычно используется для погружений без дайв-компьютера. Основная +учетная запись в <em>Subsurface</em> - это дайв. В простом журнале погружений обычно +фиксируется только наиболее важная информация: тип дайва, дата, время, +длительность, глубина, имена напарников, дайв-мастера или гида, возможно +некоторые заметки о погружении. <em>Subsurface</em> может хранить гораздо больше +информации о каждом отдельном дайве. Чтобы добавить новый дайв в журнал +выберите в главном меню <em>Журнал → Добавить погружение</em>. Программа при этом +покажет три области, доступных для ввода данных: две вкладки на информационной +панели (<strong>Примечания</strong> и <strong>Снаряжение</strong>) и панель <strong>Профиль</strong> с графиком погружения. +Эти области отмечены соответственно как <span class="red">A</span>, <span class="red">B</span> и <span class="red">C</span> на +картинке ниже. Далее будет пояснено как вводить данные.</p></div> +<div class="imageblock" style="text-align:center;"> +<div class="content"> +<img src="images/AddDive1_f22.jpg" alt="Рисунок: Добавление погружения" /> +</div> +</div> +<div class="paragraph"><p>Когда вы щелкаете мышью в одном из полей указанных панелей, вы переходите в +режим редактирования. Об этом свидетельствует сообщение на синем фоне в +верхней части.</p></div> +<div class="imageblock" style="text-align:center;"> +<div class="content"> +<img src="images/BlueEditBar_f22.jpg" alt="Синяя полоса редактирования" /> +</div> +</div> +<div class="paragraph"><p>Не нажимайте на кнопку <em>Применить изменения</em> до тех пор, пока вы не ввели все данные. +При ручном вводе вам нужно заполнить поля на вкладках <em>Примечания</em>, <em>Снаряжение</em> и +<em>Профиль</em> перед сохранением. При нажатии кнопки <em>Применить изменения</em>, информация о +погружении сохраняется в памяти. При закрытии <em>Subsurface</em> вам будет предложено +сохранить весь журнал на диск.</p></div> +<div class="sect3"> +<h4 id="S_CreateProfile">5.1.1. Создание профиля погружения</h4> +<div class="paragraph"><p><strong>Профиль погружения</strong> (графическое представление глубины дайва как функции +от времени) отображается в правой верхней панели окна <em>Subsurface</em>. В случае +ручного добавления погружения в журнал, <em>Subsurface</em> предлагает начальный +профиль дайва, который необходимо изменить, чтобы он соответствовал реальному +погружению:</p></div> +<div class="imageblock" style="text-align:center;"> +<div class="content"> +<img src="images/DiveProfile1_f20.jpg" alt="Рисунок: Начальный профиль погружения" /> +</div> +</div> +<div class="paragraph"><p><em>Изменение профиля погружения</em>: при перемещении курсора по профилю погружения, +его положение показывается двумя красными линиями. Глубина +и время, соответствующие положению курсора, отображаются на координатных осях +слева и внизу. Единицы измерения (имперская или метрическая система мер) +берутся из <em>Настроек</em> приложения. Профиль дайва состоит из нескольких +сегментов, определенных путевыми точками (белые точки, как показано на рисунке +выше). Глубина по умолчанию составляет 15м. Если погружение было совершено на +глубину 21м, вам необходимо передвинуть соответствующие точки вниз к нужной +глубине. Для добавления новой точки, дважды щелкните на линии любого сегмента. +Чтобы переместить точку, нажмите на нее мышкой и перетаскивайте. Для удаления +путевой точки, нажмите на ней правой кнопкой мыши и во всплывающем меню +выберите пункт "Удалить эту точку". Добавляйте и перемещайте точки до тех пор, +пока профиль не будет соответствовать реальному погружению (глубина и время). +Ниже приведен пример погружения на 20м в течение 30 минут с последующей +остановкой безопасности на 5м на 5 минут.</p></div> +<div class="imageblock" style="text-align:center;"> +<div class="content"> +<img src="images/DiveProfile2_f20.jpg" alt="Рисунок: Отредактированный профиль погружения" /> +</div> +</div> +<div class="paragraph"><p><em>Редактирование газовой смеси:</em> Название используемой газовой смеси +отображается на профиле рядом с каждым сегментом погружения. По умолчанию +используется первая смесь из списка газов, указанных на вкладке +<strong>Снаряжение</strong>. В предыдущем примере это воздух. Чтобы изменить газ для отдельно +взятого сегмента, нажмите правой кнопкой мыши на путевой точке и выберите +смесь из выпадающего контекстного меню. Изменение газа в путевой точке +изменяет сегмент <em>слева</em> от этой точки. Обратите также внимание, что в +контекстном меню доступны только газы, определенные на вкладке <strong>Снаряжение</strong>.</p></div> +<div class="imageblock" style="text-align:center;"> +<div class="content"> +<img src="images/DiveProfile3_f20.jpg" alt="Рисунок: Меню выбора газовой смеси" /> +</div> +</div> +<div class="paragraph"><p>После того, как профиль погружения был задан, необходимо указать дополнительные детали. +Используйте для этого вкладки <strong>Примечания</strong> и <strong>Снаряжение</strong>, находящиеся в верхней левой +части окна <em>Subsurface</em>. Перейдите по <a href="#S_Notes_dc">этой ссылке</a> для получения более +подробной информации.</p></div> +</div> +</div> +<div class="sect2"> +<h3 id="S_ImportDiveComputer">5.2. Импорт новых погружений из дайв-компьютера</h3> +<div class="sect3"> +<h4 id="_подсоединение_дайв_компьютера_и_импорт_данных">5.2.1. Подсоединение дайв-компьютера и импорт данных</h4> +<div class="paragraph"><p>Использование дайв-компьютеров позволяет получить большое количество подробной +информации о погружении, например, точные значения глубин, длительности, +скорости погружения и всплытия, парциального давления газов. <em>Subsurface</em> +поддерживает множество моделей дайв-компьютеров, +<a href="http://subsurface-divelog.org/documentation/supported-dive-computers/"> +актуальный список</a> доступен на веб-сайте.</p></div> +<div class="admonitionblock"> +<table><tr> +<td class="icon"> +<img src="images/icons/warning2.png" alt="Внимание" /> +</td> +<td class="content">Некоторые модели дайв-компьютеров потребляют значительное количество энергии, +будучи переведенным в режим обмена данными с компьютером. <strong>Это может привести +к быстрому разряду батареи</strong>. Поэтому мы рекомендуем предварительно проверить +уровень заряда батареи перед подключением к USB-порту вашего персонального +компьютера. Так, некоторые модели Suunto и Mares не заряжаются, будучи +подключенными к ПК. Советуем вам обратиться к руководству по использованию +вашего дайв-компьютера, чтобы выяснить, заряжается ли его батарея при +подключении к USB-порту.</td> +</tr></table> +</div> +<div class="paragraph"><p>Для переноса данных из дайв-компьютера в ваш ПК необходимо установить +соединение между ними. Для этого вам нужно выяснить порт или точку +монтирования и сообщить эту информацию <em>Subsurface</em>. В +<a href="#APPENDIX_A">Приложении А</a> приведена техническая информация, +специфичная для различных операционных систем, а в +<a href="#APPENDIX_B">Приложении Б</a> для отдельных моделей дайв-компьютеров.</p></div> +<div class="paragraph"><p>Когда у вас есть необходимая информация, можно подключить дайв-компьютер к ПК, +выполнив следующие шаги:</p></div> +<div class="olist arabic"><ol class="arabic"> +<li> +<p> +Интерфейсный кабель должен быть подключен к свободному USB-порту + (подключение через ИК-порт и Bluetooth рассматривается далее) +</p> +</li> +<li> +<p> +Дайв-компьютер должен быть переведен в режим передачи данных + (Обратитесь к руководству пользователя вашего дайв-компьютера) +</p> +</li> +<li> +<p> +В главном меню <em>Subsurface</em> выберите <em>Импорт → Импорт из дайв-компьютера</em>. + Вам будет представлено следующее диалоговое окно <strong>A</strong>: +</p> +</li> +</ol></div> +<div class="imageblock" style="text-align:center;"> +<div class="content"> +<img src="images/DC_import_f20.jpg" alt="Рисунок: Загрузка из дайв-компьютера 1" /> +</div> +</div> +<div class="paragraph"><p>Дайв-компьютеры обычно хранят в своей памяти информацию о нескольких последних +погружениях, даже не смотря на то, что они уже были загружены в <em>Subsurface</em>. +По этой причине <em>Subsurface</em> импортирует только те дайвы, которые еще не были +загружены ранее. Это значительно ускоряет процесс импорта из большинства +дайв-компьютеров, а также предохраняет батарею от разряда (если конечно ваш +дайв-компьютер не заряжается, будучи подключенным к USB-порту).</p></div> +<div class="ulist"><ul> +<li> +<p> +В диалоговом окне присутствуют два выпадающих списка: <strong>Производитель</strong> и + <strong>Модель</strong>. Сначала выберите производителя, например, Suunto, Oceanic, Uwatec + или Mares. Затем в списке <strong>Модель</strong> выберите марку вашего дайв-компьютера, + например, D4 (Suunto), Veo200 (Oceanic) или Puck (Mares). +</p> +</li> +<li> +<p> +Поле <strong>Устройство или точка монтирования</strong> содержит список USB или Bluetooth + портов, необходимых для связи <em>Subsurface</em> с вашим дайв-компьютером. Вы + должны выбрать порт, соответствующий вашему устройству. Обратитесь к + <a href="#APPENDIX_A">Приложению А</a> и + <a href="#APPENDIX_B">Приложению Б</a> для получения технической информации о том, + как выяснить название порта связи для определенного дайв-компьютера, + а в некоторых случаях, как настроить операционную систему ПК, на котором + запущен <em>Subsurface</em>. +</p> +</li> +<li> +<p> +Если необходимо загрузить все дайвы, поставьте галочку в поле + <em>Принудительная загрузка всех погружения</em>. Обычно <em>Subsurface</em> импортирует + только погружения новее самого последнего в вашем журнале. Эта функция вам + также может понадобиться, если вы случайно удалили погружения из журнала. + Некоторые модели дайв-компьютеров (например, Mares Puck) не предоставляют + список погружения в своей памяти перед импортом, поэтому <em>Subsurface</em> не + может определить какие из дайвов являются новыми и загружает все погружения + не зависимо от состояния этого поля. +</p> +</li> +<li> +<p> +Если в поле <strong>Предпочтение загруженным</strong> стоит галочка,и во время импорта + будут существовать погружения с одинаковой датой в журнале и в + дайв-компьютере, <em>Subsurface</em> перезапишет данные такого дайва данными из + дайв-компьютера. +</p> +</li> +<li> +<p> +Если напротив поля _Загружать в новую поездку" стоит галочка, то после загрузки все + новые погружения будут сгруппированы в одну поездку в <strong>Списке погружений</strong> +</p> +</li> +<li> +<p> +<strong>Не выбирайте</strong> поля <em>Сохранить журнал libdivecomputer</em> и <em>Сохранить + дамп-файл libdivecomputer</em>. Они используются для диагностики в случае + возникновения проблем с импортом из дайв-компьютера (см. ниже). +</p> +</li> +<li> +<p> +Нажмите кнопку <em>Загрузить</em>. При установленном соединении вы можете наблюдать + как загружаются данные из дайв-компьютера. В зависимости от модели компьютера + и количества погружений в памяти последнего, импорт может занять довольно долгое время, + будьте терпеливы. Бегущая полоса, показывающая процесс загрузки, может не совсем + точно отражать скорость загрузки, так как зачастую <em>Subsurface</em> не знает + точно сколько погружений будет загружено до тех пор, пока импорт не завершен. + После загрузки погружений они отобразятся в в виде таблицы в правой части окна + (как показано на рисунке <strong>В</strong> выше). Проставьте галочки напротив тех погружений, + которые должны быть перенесены в <strong>Список погружений</strong> и нажмите кнопку <strong>OK</strong>. + Окно загрузки будет закрыто, а выбранные погружения появятся в списке. + После окончания загрузки отключите дайв-компьютер и выключите его + для экономии заряда батареи. +</p> +</li> +<li> +<p> +В случае возникновения проблем связи с дайв-компьютером показывается + информационное сообщение вида "Невозможно открыть /dev/ttyUSB0 Mares (Puck + Pro)". Внимательно прочитайте следующую главу. +</p> +</li> +</ul></div> +<div class="sidebarblock"> +<div class="content"> +<div class="paragraph"><p><strong>Проблемы импорта из дайв-компьютера</strong></p></div> +<div class="admonitionblock"> +<table><tr> +<td class="icon"> +<img src="images/icons/important.png" alt="Важно" /> +</td> +<td class="content">Проверьте следующее:</td> +</tr></table> +</div> +<div class="ulist"><ul> +<li> +<p> +Дайв-компьютер все еще находится в режиме передачи данных? +</p> +</li> +<li> +<p> +Полностью ли заряжена батарея дайв-компьютера? Если нет, то следует ее + зарядить или заменить. +</p> +</li> +<li> +<p> +Рабочий ли интерфейсный кабель? Работает ли этот кабель при использовании + других программ? Работал ли этот кабель ранее или вы используете его в + первый раз? +</p> +</li> +<li> +<p> +Обратитесь к + <a href="#APPENDIX_A">Приложению А</a> и убедитесь что правильно указано устройство + или точка монтирования (см. выше). +</p> +</li> +<li> +<p> +На Unix-подобных операционных системах убедитесь что у вас есть права на + открытие порта USB. Если нет, прочитайте + <a href="#APPENDIX_A">Приложение А</a>. +</p> +</li> +</ul></div> +<div class="paragraph"><p>Если <em>Subsurface</em> не распознает USB адаптер, не показывая при правильное +название устройства в поле <em>Устройство или точка монтирования</em>, велика +вероятность, что кабель нерабочий. Это наиболее часто встречающаяся причина +ошибок при импорте. Также существует вероятность того, что <em>Subsurface</em> не может +распознать данные, полученные с дайв-компьютера. В этом случае выполните +необходимо выполнить диагностическую загрузку, пометив галочками следующие два +поля:</p></div> +<div class="literalblock"> +<div class="content"> +<pre><code>Сохранить журнал libdivecomputer +Сохранить дамп-файл libdivecomputer</code></pre> +</div></div> +<div class="paragraph"><p><strong>Важно</strong>: эти поля используются только для диагностики ошибок, возникших при +импорте данных из дайв-компьютера, в обычной ситуации галочки в этих полях +должны быть сняты. Когда они выбраны, вам при импорте будет предложено выбрать +папку для сохранения диагностической информации. По умолчанию используется +папка, в которой хранится журнал погружений.</p></div> +<div class="paragraph"><p><strong>Важно</strong>: При импорте в диагностическом режиме, погружения в журнал не +добавляются. Вместо этого в указанной вами папке будут созданы два файла:</p></div> +<div class="literalblock"> +<div class="content"> +<pre><code>subsurface.log +subsurface.bin</code></pre> +</div></div> +<div class="paragraph"><p>Эти файлы следует отправить разработчикам в mailto:subsurface@subsurface-divelog.org +[список рассылки] с просьбой проанализировать проблему. Необходимо указать +производителя и модель дайв-компьютера и дать словесное описание загружаемых +погружений.</p></div> +</div></div> +</div> +<div class="sect3"> +<h4 id="S_Bluetooth">5.2.2. Подключение <em>Subsurface</em> к дайв-компьютеру через Bluetooth</h4> +<div class="paragraph"><p>Bluetooth все чаще встречается в качестве интерфейса для взаимодействия с дайв-компьютерами, +например Shearwater Petrel Mk2 и OSTC Mk3. <em>Subsurface</em> предоставляет интерфейс взаимодействия +с Bluetooth, слабо зависящий от операционной системы. Нестройка Bluetooth-соединения в <em>Subsurface</em> +требует выполнения четырех шагов:</p></div> +<div class="ulist"><ul> +<li> +<p> +Удостоверьтесь, что Bluetooth активирован на вашем персональном компьютере. +</p> +</li> +<li> +<p> +Убедитесь, что <em>Subsurface</em> распознает адаптер Bluetooth на этом компьютере. +</p> +</li> +<li> +<p> +Проверьте, что дайв-компьютер переведен в режим связи с ПК и его можно обнаружить через Bluetooth. +</p> +</li> +<li> +<p> +Проверьте, чтобы <em>Subsurface</em> был сопряжен с дайв-компьютером. +</p> +</li> +</ul></div> +<div class="paragraph"><p>Перейдите в окно "Загрузка из дайв-компьютера", выбрав в <strong>Главном меню</strong> <em>Импорт → Импорт из +дайв-компьютера</em>. Если поставить галочку напротив пункта <em>Загрузка через Bluetooth</em>, +вам будет представлено следующее окно:</p></div> +<div class="sect4"> +<h5 id="_linux_или_macos">Linux или MacOS:</h5> +<div class="imageblock" style="text-align:center;"> +<div class="content"> +<img src="images/DC_import_Bluetooth.jpg" alt="Рисунок: Сопряжение устройств Bluetooth" /> +</div> +</div> +<div class="paragraph"><p>На платформах <em>Linux</em> и <em>MacOS</em> в правой части окна показывается название +компьютера, на котором запущен <em>Subsurface</em>, и его адрес Bluetooth. Если на +компьютере найдено более одного локального Bluetooth-адаптера, то они будут +представлены в выпадающем списке и вы можете указать тот, который необходимо +использовать. Кнопка ниже позволяет включить ии выключить питание локального +Bluetooth-адаптера.</p></div> +<div class="paragraph"><p>Если Bluetooth-адрес не указан, это означает, что <em>Subsurface</em> не может распознать локальное +Bluetooth-устройство. Убедитесь, что на компьютере установлен драйвер адаптера и проверьте, что +он может использоваться другими программами для работы с Bluetooth (<em>bluetoothctl</em> или <em>bluemoon</em>). +Эти шаги покрывают первые два из из перечисленных выше.</p></div> +<div class="paragraph"><p>Проверьте, что дайв-компьютер переведен в режим связи с ПК и его можно обнаружить через Bluetooth. +Обратитесь к руководству пользователя вашего дайв-компьютера, чтобы сделать это. Это действие +завершает третий шаг.</p></div> +<div class="paragraph"><p>Нажмите на кнопку <em>Сканировать</em> в левой нижней части окна. Спустя небольшое +время поиска, ваш дайв-компьютер должен появиться в списке обнаруженных +устройств (возможно наряду с другими найденными устройствами) в левой части +диалогового окна (см. картинку выше). Если компьютер в списке не появился, +нажмите кнопку <em>Очистить</em> и повторите процедуру сканирования. В итоге +<em>Subsurface</em> должен обнаружить дайв-компьютер. В списке обнаруженных устройств +показывается их название, адрес и статус сопряжения. Если устройство не +сопряжено и подсвечено красным цветом, щелкните на нем правой кнопкой мыши и из +контекстного меню выберите пункт <em>Сопряжение</em>. Дождитесь окончания этого +действия. Если сопряжение с этим устройством производится впервые, <em>Subsurface</em> +может запросить пароль или PIN-код. Наиболее часто используется код 0000 (например, +это работает с Shearwater Petrel). При необходимости обратитесь к руководству +пользователя вашего дайв-компьютера.</p></div> +<div class="sidebarblock"> +<div class="content"> +<div class="admonitionblock"> +<table><tr> +<td class="icon"> +<img src="images/icons/important.png" alt="Важно" /> +</td> +<td class="content">В настоящий момент <em>Subsurface</em> не поддерживает сопряжение с дайв-компьютерами, которые требуют +собственный PIN-код. В этом случае для сопряжения используйте другие утилиты операционной системы +так, как это предложено ниже.</td> +</tr></table> +</div> +<div class="paragraph"><p>Один и способов сопряжения - использование утилиты <code>bluetoothctl</code>:</p></div> +<div class="literalblock"> +<div class="content"> +<pre><code>$ bluetoothctl +[bluetooth]# agent KeyboardOnly +Agent registered +[bluetooth]# default-agent +Default agent request successful +[bluetooth]# pair 00:80:25:49:6C:E3 +Attempting to pair with 00:80:25:49:6C:E3 +[CHG] Device 00:80:25:49:6C:E3 Connected: yes +Request PIN code +[agent] Enter PIN code: 0000</code></pre> +</div></div> +</div></div> +<div class="paragraph"><p>После сопряжения устройств можно нажать на кнопку <em>Сохранить</em>. Окно выбора +Bluetooth-устройства будет закрыто. Теперь в окне <em>Загрузка из дайв-компьютера</em> +нажмите кнопку <em>Загрузить</em>. Загруженные погружения будут показаны в списке в +правой части окна.</p></div> +</div> +<div class="sect4"> +<h5 id="_windows">Windows</h5> +<div class="imageblock" style="text-align:center;"> +<div class="content"> +<img src="images/DC_import_Bluetooth_Windows.png" alt="Рисунок: Сопряжение устройств Bluetooth в Windows" /> +</div> +</div> +<div class="paragraph"><p>На платформе <em>Windows</em> детали локального Bluetooth-адаптера не отображаются как в +случае Mac и Linux. +Для успешного обнаружения дайв-компьютера убедитесь, что на вашем компьютере +включен Bluetooth. Используйте кнопку <em>Сканировать</em> для обнаружения устройств. +Если сопряжение устройства производится впервые, вам возможно придется указать +PIN-код. Обычно это 0000; при необходимости обратитесь к руководству пользователя +вашего дайв-компьютера.</p></div> +<div class="paragraph"><p>Сопряжение устройств происходит автоматически при загрузке погружений. Если до +этого устройства никогда не были сопряжены, операционная система запросит +подтверждение и выведет уведомление в правой части экрана: <em>Добавление устройства, +нажмите чтобы настроить ваш дайв-компьютер</em>. Вам необходимо подтвердить сопряжение. +Выберите устройство из списка обнаруженных и нажмите кнопку <em>Сохранить</em>. В окне +<em>Загрузка из дайв-компьютера</em> нажмите кнопку <em>Загрузить</em> и дождитесь окончания процесса.</p></div> +<div class="admonitionblock"> +<table><tr> +<td class="icon"> +<img src="images/icons/important.png" alt="Важно" /> +</td> +<td class="content">Учтите, что в настоящий момент <em>Subsurface</em> работает только с локальными Bluetooth-адаптерами +и Bluetooth-брелками, использующими стэк Microsoft Bluetooth (например, iSonic). +Прочие, использующие драйверы <em>Widcomm</em>, <em>Stonestreet One Bluetopia Bluetooth</em> или +<em>BlueSolei</em>, заведомо работать не будут.</td> +</tr></table> +</div> +<div class="paragraph"><p>Информационное сообщение в левой нижней части окна выбора Bluetooth-устройства +показывает текущее состояние агента Bluetooth. Для выбора другого устройства, +вызовите окно выбора Bluetooth-устройства нажатием на кнопку с троеточием +справа от галочки <em>Загрузка через Bluetooth</em></p></div> +<div class="admonitionblock"> +<table><tr> +<td class="icon"> +<img src="images/icons/important.png" alt="Важно" /> +</td> +<td class="content"><strong>В случае возникновения проблем</strong>: Если локальный Bluetooth-адаптер на компьютере с <em>Subsurface</em> +"завис" и загрузка погружений постоянно завершается с ошибкой, <em>удалите</em> сопряжение с устройством +и повторите шаги, перечисленные выше. Если и это не помогло, в +<a href="#S_HowFindBluetoothDeviceName"><em>Приложении А</em></a> вы сможете найти информацию о том, как вручную +настроить и проверить соединение с <em>Subsurface</em>.</td> +</tr></table> +</div> +</div> +</div> +<div class="sect3"> +<h4 id="S_DeviceNames">5.2.3. Изменение названия дайв-компьютера</h4> +<div class="paragraph"><p>Может возникнуть ситуация, когда вам будет необходимо каким-то образом +различать дайв-компьютеры, используемые совместно с <em>Subsurface</em>. Например, +если у вас с напарником одинаковые дайв-компьютеры и вы их используете для +импорта данных на одном ПК, то вы возможно захотите назвать один из +компьютеров как "Suunto D4 Ивана", а другой как "Suunto D4 Петра". Или же +вы технический дайвер и используете два или более дайв-компьютеров одной +модели. В этом случае мы можете назвать их "Suunto D4 (1)" и "Suunto D4 (2)". +<em>Subsurface</em> позволяет вам легко это сделать. В <strong>Главном меню</strong> выберите +<em>Журнал → Мои дайв-компьютеры</em>. В открывшемся окне вам будет представлен +список всех компьютеров, использовавшихся для импорта погружений. +Отредактируйте название соответствующего устройства. После сохранения +в журнале будет отображаться это название вместо его модели.</p></div> +</div> +<div class="sect3"> +<h4 id="S_EditDiveInfo">5.2.4. Редактирование погружения, загруженного из компьютера</h4> +<div class="paragraph"><p>Информация из дайв-компьютера может быть неполной и вам потребуется ее +отредактировать. Для этого вам предоставляется две вкладки <strong>Примечания</strong> и +<strong>Снаряжение</strong> в верхней левой панели <em>Subsurface</em>.</p></div> +<div class="sect4"> +<h5 id="S_Notes_dc">Примечания</h5> +<div class="paragraph"><p>Вам возможно придется указать дополнительную информацию, чтобы иметь более полную +запись о погружении. Нижеописанная процедура одинакова как для погружений, введенных +вручную, так и для загруженных из дайв-компьютера.</p></div> +<div class="paragraph"><p>Дата и время погружения, газовая смесь и (обычно) температура присутствуют в +импортированных дайвах, но вам может понадобиться дополнить +информацию вручную. Если вы начнете менять какие-то данные на этой вкладке, +сообщение на голубом фоне в верхней части окна будет уведомлять вас, что +погружение редактируется. +На вкладке <strong>Примечания</strong> вам доступны следующие поля +для редактирования (картинка слева):</p></div> +<div class="imageblock" style="text-align:center;"> +<div class="content"> +<img src="images/AddDive3_f22.jpg" alt="Рисунок: Вкладка Примечания" /> +</div> +</div> +<div class="paragraph"><p>На картинке справа показана заполненная вкладка <strong>Примечания</strong>. +Поля <strong>Дата</strong> и <strong>Время</strong> соответствуют дате и времени дайва. При нажатии мышкой +на поле даты отображается выпадающий календарь, в котором можно выбрать +необходимую дату. Нажмите ESC чтобы закрыть календарь. Значение времени (часы +и минуты) можно также непосредственно поменять, для чего необходимо нажать +мышкой в нужном месте текстового поля и ввести цифры.</p></div> +<div class="paragraph"><p><strong>Температура воды и воздуха</strong> во время дайва. Зачастую дайв-компьютеры +записывают эту информацию и вам не нужно ее редактировать. Если же вы решите +их заполнить вручную,единицы измерения заполнять не нужно, они будут автоматически +подставлены программой (единицы, выбранные в *Настройках* указывают будет ли +использоваться метрическая или имперская система мер).</p></div> +<div class="paragraph"><p><strong>Местоположение</strong>:</p></div> +<div class="admonitionblock"> +<table><tr> +<td class="icon"> +<img src="images/icons/warning2.png" alt="Внимание" /> +</td> +<td class="content">Управление дайв-сайтами выполняется отдельно от журнала погружений. Поэтому информация погружения +на вкладках <strong>Примечания</strong> и <strong>Снаряжение</strong> не может быть отредактирована одновременно с данными +дайв-сайта. Сохраните прочую информацию (партнеры, дайв-мастер, костюм) нажатием на кнопку +<strong>Применить изменения</strong>. Только после этого укажите название местоположения в поле <em>Местоположение</em>.</td> +</tr></table> +</div> +<div class="paragraph"><p>Укажите название дайв-сайта, например, «Эль-Мина рэк, Хургада, Египет». +Если была указана информация для одного дайв-сайта, и у вас есть несколько погружений +в этом же месте, то эта информация может быть использована без необходимости повторного ввода +данных. Информация дайв-сайта может быть отредактирована в любой момент. Для этого выберите +в списке любое погружение, выполнявшееся на этом сайте, и нажмите кнопку с изображением глобуса, +которая находится справа от поля <strong>Местоположение</strong> (см. картинку справа выше). При вводе названия +дайв-сайта <em>Subsurface</em> автоматически предложит вам список сайтов с похожими именами. Если сайт +уже существует, выберите его из списка. Справа от названия сайта в выпадающем списке находится +картинка либо с изображением глобуса (означает, что в базе данных <em>Subsurface</em> есть погружения +на этом сайте), либо со значком <strong>+</strong> (сайты с похожим названием, которые еще не были добавлены +в базу сайтов).</p></div> +<div class="paragraph"><p>Если сайт ранее не существовал, вы увидите следующее сообщение (рисунок <strong>А</strong> ниже)</p></div> +<div class="imageblock" style="text-align:center;"> +<div class="content"> +<img src="images/Locations1_f22.jpg" alt="FIGURE:Редактирование дайв-сайта" /> +</div> +</div> +<div class="paragraph"><p>Дважды щелкните мышью на наовом дайв-сайте. Вам будет представлена панель, на которой можно ввести +координаты и прочую информацию о сайте (рисунок <strong>В</strong> выше). Наиболее важными являются географические +координаты сайта. Их можно указать тремя способами:</p></div> +<div class="paragraph"><p>а. Выбрать на карте, которая находится в правой нижней части окна +<em>Subsurface</em>. На карте отображается оранжевая полоса с надписью «Выберите место +на карте двойным щелчком мыши». При двойном нажатии в соответствующем месте +карты, оранжевая полоса исчезнет и координаты точки будут заполнены в поле.</p></div> +<div class="paragraph"><p>б. Координаты могут быть получены с помощью вспомогательного приложения +<em>Subsurface</em>, если у вас есть устройство Android с GPS-датчиком и координаты +дайв-сайта были сохранены в этом устройстве. <a href="#S_Companion">Нажмите, чтобы +узнать больше</a></p></div> +<div class="paragraph"><p>в. Если вам известны координаты, их можно ввести вручную в одном из четырех +форматов, сначала широта, потом долгота:</p></div> +<div class="literalblock"> +<div class="content"> +<pre><code>ISO 6709 Приложение D, например 30°13'28.9"Ю 30°49'1.5"В +Градусы и десятичные минуты, например, Ю30° 13.49760' , В30° 49.30788' +Градусы минуты секунды, например, Ю30° 13' 29.8" , В30° 49' 1.5" +Десятичные градусы, например, 30.22496 , 30.821798</code></pre> +</div></div> +<div class="paragraph"><p>Широта южного полушария указывается с буквой <strong>Ю</strong>, например, Ю30°, или со знаком минус, +например, -30.22496. Аналогично, долгота западного полушария указывается с буквой <strong>З</strong>, +например, З07°, или со знаком минус, например,-7.34323. На некоторых клавиатурах отсутствует +символ градусов ((°). Его можно заменить на <strong>d</strong>, например: С30d З20d. +Если вы указали название дайв-сайта и его координаты, сохраните информацию, нажав на кнопку +<em>Сохранить изменения</em> в верхней части панели.</p></div> +<div class="paragraph"><p><strong>Важно</strong> координаты GPS привязаны к названию дайв-сайта, поэтому +указание координат для погружений, у которых не указано местоположение, может +привести к непредсказуемым результатам (<em>Subsurface</em> будет предлагать, что все +эти погружения были в одном месте и имеют одинаковые координаты).</p></div> +<div class="paragraph"><p><strong>Геопоиск дайв-сайтов:</strong> Если были указаны географические координаты сайта, +вы можете выполнить автоматический поиск его названия. Для этого <em>Subsurface</em> требуется +подключение к Интернет. Найденая информация будет отображаться в метках рядом с названием +дайв-сайта. Список <em>Дайв-сайты с такими же координатами</em> в нижней части панели отображает сайты, +находящиеся по соседству.</p></div> +<div class="paragraph"><p>Укажите прочую текстовую информацию о дайв-сайте (Описание и Примечания) и нажмите кнопку +<em>Применить изменения</em>, чтобы сохранить информацию и сайте. В дальнейшем информация о сайте может +быть отредактирована нажатием на кнопку с изображением глобуса справа от поля Местоположение на +вкладке <strong>Примечания</strong>.</p></div> +<div class="paragraph"><p><strong>Режим погружения</strong>: С помощью выпадающего списка вы можете выбрать режим погружения. Вам +предоставляются следующие варианты: OC (открытый цикл, значение по умолчанию, подходит для большинства рекреационных дайверов), +Freedive (погружение без дыхательного аппарата), CCR (ребризер замкнутого цикла) и pSCR ( +пассивный полу-замкнутый ребризер).</p></div> +<div class="paragraph"><p><strong>Инструктор</strong>: Имя гида или дайв-мастера, с которым производилось это +погружение. Это поле также производит автодополнение на основании списка всех +инструкторов в текущем журнале.</p></div> +<div class="paragraph"><p><strong>Партнер</strong>: Имя buddy или имена партнеров (разделенные запятой), с которыми +выполнялось данное погружение. Это поле делает автодополнение на основании +списка всех партнеров в текущем журнале.</p></div> +<div class="paragraph"><p><strong>Костюм</strong>: Тип костюма в котором осуществлялось погружение. Как и с другими +полями, для него доступно автодополнение. Если вы ныряете в сухом костюме, то +можете также указать тип утеплителя и его теплозащиту.</p></div> +<div class="paragraph"><p><strong>Оценка</strong>: Ваша субъективная оценка этого погружения по 5-ти бальной шкале. +Укажите рейтинг, нажав на соответствующей звездочке.</p></div> +<div class="paragraph"><p><strong>Видимость</strong>: Видимость под водой, как и в предыдущем случае, оценивается по +5-ти бальной шкале.</p></div> +<div class="paragraph"><p><strong>Метки</strong>: Набор меток (разделенных запятой), описывающих это погружение, +например: ночное, пещера, течение и т.п. <em>Subsurface</em> предоставляет также +набор встроенных меток. Автодополнение доступно для этого поля. Например, +набрав <code>cav</code>, вам предложат на выбор метки <strong>cave</strong> и <strong>cavern</strong>.</p></div> +<div class="paragraph"><p><strong>Примечания</strong>: В это поле можно ввести любую дополнительную информацию.</p></div> +<div class="paragraph"><p>Кнопка <strong>Применить изменения</strong> используются для сохранения информации на всех +вкладках информационной панели и профиля погружения, поэтому нет необходимости +нажимать ее до тех пор, пока вы не заполнили ВСЮ информацию. Картинка, помещенная +<a href="#S_Notes_dc">в начале главы</a>, представляет пример полностью заполненной информационной панели.</p></div> +</div> +</div> +<div class="sect3"> +<h4 id="_снаряжение">5.2.5. Снаряжение</h4> +<div class="paragraph"><p>Вкладка Снаряжение позволяет ввести информацию об используемых баллонах и +газах, а также грузовых системах. Голубая полоса в верхней части панели с +сообщением:</p></div> +<div class="imageblock" style="text-align:center;"> +<div class="content"> +<img src="images/BlueEditBar_f22.jpg" alt="Голубая полоса редактирования" /> +</div> +</div> +<div class="paragraph"><p>информирует о том, что в данный момент вы редактируете погружение. Эта часть +<em>Subsurface</em> очень интерактивная и информация о баллонах и смесях влияет на +поведение профиля погружения (верхняя правая панель).</p></div> +<div class="paragraph" id="cylinder_definitions"><p><strong>Баллоны</strong>: Ввод информации о баллонах осуществляется с помощью диалога, +изображенного на следующей картинке:</p></div> +<div class="imageblock" style="text-align:center;"> +<div class="content"> +<img src="images/DC_gas-dialogue1_f20.jpg" alt="Рисунок: Начальный вид диалога редактирования баллонов" /> +</div> +</div> +<div class="paragraph"><p>В большинстве случаев <em>Subsurface</em> получает информацию о смесях из +дайв-компьютера и подставляет ее в таблицу. Кнопка + в правом верхнем углу +позволяет добавить новый баллон к текущему погружению. Темная иконка с +изображением мусорной корзины удаляет выбранный баллон, однако +только в том случае, если этот баллон уже не используется в погружении. +Баллон может неявно использоваться даже в отсутствие событий смены газа.</p></div> +<div class="paragraph"><p>Начните с выбора типа баллона из выпадающего списка в левой части таблицы. Для +этого нажмите на ячейке в колонке <strong>Тип</strong>:</p></div> +<div class="imageblock" style="text-align:center;"> +<div class="content"> +<img src="images/DC_gas-dialogue2_f20.jpg" alt="Рисунок: Список типов баллонов" /> +</div> +</div> +<div class="paragraph"><p>Вы можете использовать выпадающий список для выбора типа баллона для +погружения, а можете начать вводить название типа с помощью клавиатуры. В этом +случае вам будут предложены совпадающие типы. Поля <strong>Объем</strong> и <strong>Рабочее +давление</strong> будут заполнены автоматически. Если баллон отсутствует в списке, +укажите его название и описание в поле <strong>Тип</strong></p></div> +<div class="paragraph"><p>Далее укажите начальное и конечное давление газа в баллоне. Единицы измерения +давления (метрическая/имперская система мер) будут взяты из <em>Настроек</em>.</p></div> +<div class="paragraph"><p>Наконец, укажите состав используемой смеси в поле <strong>O₂%</strong>. Если используется +воздух, то можно указать значение 21% или вовсе оставить это поле пустым. В +случае использования Nitrox или Trmix, необходимо указать процентное +содержание кислорода и гелия в соответствующих полях. +Прочие ненужные поля следует оставить незаполненными. После ввода всей +необходимой информации нажмите клавишу <em>ENTER</em> либо щелкните курсором мыши вне +ячейки, в которой находится курсор. Информация о дополнительных баллонах может +быть добавлена нажатием на кнопку + в правом верхнем углу. Ниже приведен +пример погружения с двумя баллонами (воздух и EAN50):</p></div> +<div class="imageblock" style="text-align:center;"> +<div class="content"> +<img src="images/CylinderDataEntry3_f20.jpg" alt="Рисунок: заполненная таблица баллонов" /> +</div> +</div> +<div class="paragraph"><p><strong>Грузы</strong>: Информация о грузовых системах, используемых во время погружения, +вводится таким же образом, как и информация о баллонах. Если нажать на кнопку ++ в правом верхнем углу, таблица будет выглядеть приблизительно так:</p></div> +<div class="imageblock" style="text-align:center;"> +<div class="content"> +<img src="images/WeightsDataEntry1_f20.jpg" alt="Рисунок: Редактирование грузовых систем" /> +</div> +</div> +<div class="paragraph"><p>При нажатии мышкой в поле <strong>Тип</strong>, выпадающий список можно вызвать, нажав +клавишу вниз:</p></div> +<div class="imageblock" style="text-align:center;"> +<div class="content"> +<img src="images/WeightsDataEntry2_f20.jpg" alt="Рисунок: Список типов грузов" /> +</div> +</div> +<div class="paragraph"><p>Вы можете использовать выпадающий список для выбора типа груза, либо начать +вводить название с помощью клавиатуры. В этом случае вам будут предложены +совпадающие типы. После выбора типа груза, укажите его вес в поле <strong>Вес</strong>. +Нажмите клавишу <em>ENTER</em> либо щелкните курсором мыши вне ячейки, в которой +находится курсор. Если вам нужно добавить дополнительную грузовую систему, +нажмите на кнопке + в правом верхнем углу. Чтобы удалить груз, нажмите на +иконку с изображением мусорной корзины. +Вот пример заполненной таблицы с двумя грузовыми системами: интегрированная и +пояс:</p></div> +<div class="imageblock" style="text-align:center;"> +<div class="content"> +<img src="images/WeightsDataEntry3_f20.jpg" alt="Рисунок: Заполненная таблица грузов" /> +</div> +</div> +</div> +<div class="sect3"> +<h4 id="_одновременное_редактирование_нескольких_погружений">5.2.6. Одновременное редактирование нескольких погружений</h4> +<div class="paragraph"><p><em>СПОСОБ 1</em>: После загрузки данных из дайв-компьютера вы можете видеть профили погружений, +дату и время, возможно температуру, но многие поля на вкладках <strong>Погружение</strong> и <strong>Снаряжение</strong> +будут пустыми. И может оказаться очень удобным отредактировать эти поля у нескольких погружений +одновременно. Например, вы совершили несколько последовательных погружений на одном дайв-сайте, +в одной и той же конфигурации оборудования и с одним и тем же партнером. Вместо заполнения этой +информации для каждого дайва, вы можете выбрать несколько погружений в списке и отредактировать +необходимые поля для всех сразу.</p></div> +<div class="paragraph"><p>Одновременное редактирование работает только для полей, которые не заполнены. Т.е. если +у одного погружения среди нескольких выбранных были изменены какие-то поля, они не будут +изменены при множественном редактировании. Технически правило одновременного редактирования +звучит так: если редактируемое поле содержит <em>одинаковое</em> значение для всех выделенных +погружений, только в этом случае новое значение будет сохранено для всех выделенных дайвов. +В противном случае будет изменено только текущее редактируемое погружение.</p></div> +<div class="paragraph" id="S_CopyComponents"><p><em>СПОСОБ 2</em>: Существует альтернативный способ выполнить поставленную задачу. Выберите +подходящее погружение с заполненными полями на вкладках <strong>Погружение</strong> и <strong>Снаряжение</strong>. Затем +в главном меню выберите <em>Журнал → Копировать параметры погружения</em>. В появившемся окне +проставьте галочки напротив полей, которые необходимо скопировать и нажмите <em>OK</em>. Теперь +в списке погружений выберите дайвы, в которые нужно скопировать поля и в главном меню +выберите <em>Журнал → Вставить параметры погружения</em>.</p></div> +</div> +<div class="sect3"> +<h4 id="_добавление_закладок_к_погружению">5.2.7. Добавление закладок к погружению</h4> +<div class="paragraph"><p>Многие дайверы комментируют свои погружения, добавляя закладки, отмечающие +какие-то события по время дайва, например: "Встретили дельфинов", "Выпустили +буй". Это легко сделать в <em>Subsurface</em>:</p></div> +<div class="ulist"><ul> +<li> +<p> +Нажмите правой кнопкой мыши в нужной точке профиля погружения. В появившемся +контекстном меню выберите пункт <em>Добавить закладку</em>. На профиле в указанной +точке времени появится иконка с изображением дайв-флага (рисунок <strong>А</strong> ниже). +</p> +</li> +<li> +<p> +Нажмите правой кнопкой мыши на флаге. В появившемся контекстном меню +(рисунок <strong>В</strong>) выберите <em>Изменить закладку</em>. +</p> +</li> +<li> +<p> +В появившемся окне введите название закладки (рисунок <strong>С</strong>) и нажмите <em>ОК</em> +чтобы сохранить изменения. +</p> +</li> +<li> +<p> +При наведении курсора мыши на изображение флага, в нижней части +информационного окна будет отображаться название закладки (рисунок <strong>D</strong> ниже). +</p> +</li> +</ul></div> +<div class="imageblock" style="text-align:center;"> +<div class="content"> +<img src="images/Bookmarks.jpg" alt="Рисунок: Добавление закладки" /> +</div> +</div> +</div> +<div class="sect3"> +<h4 id="_сохранение_измененного_погружения">5.2.8. Сохранение измененного погружения</h4> +<div class="paragraph"><p>Вы можете сохранить информацию со вкладок <strong>Погружение</strong> и <strong>Снаряжение</strong>, нажав +кнопку <em>Применить изменения</em>. При нажатии кнопки <em>Отменить изменения</em>, введенные вами +данные будут утеряны, но информация, загруженная из дайв-компьютера, будет сохранена. +При закрытии <em>Subsurface</em> вам будет предложено сохранить данные журнала.</p></div> +</div> +<div class="sect3"> +<h4 id="S_ImportingAlienDiveLogs">5.2.9. Импорт данных из других источников и файлов</h4> +<div class="paragraph"><p>Если вы ныряете уже достаточно долго, вероятно ваши погружения уже сохранены в +какой-то другой программе для ведения журнала погружений. Вам не потребуется +вводить ее заново, потому что с большой долей вероятности <em>Subsurface</em> сможет +импортировать эти данные. <em>Subsurface</em> поддерживает множество форматов данных. +Некоторые форматы поддерживаются непосредственно, для других программ может +понадобиться сделать экспорт в промежуточный формат, для последующего импорта +в <em>Subsurface</em>. +В настоящий момент <em>Subsurface</em> поддерживает импорт из CSV-файлов нескольких +форматов. Для файлов APD LogViewer, XP5 и Sensus подготовлены шаблоны, но вы +можете создать и свой шаблон импорта. +Файлы журнала погружений, которые вы ведете вручную (в электронной таблице) +также могут быть загружены с помощью CSV-импорта.</p></div> +<div class="paragraph"><p><em>Subsurface</em> также поддерживает импорт файлов с расширением UDDF и UDCF, +которые используются некоторыми дайв-компьютерами, такими, как Heinrichs & +Weikamp DR5. Наконец, для некоторых сторонних программ, например, Mares Dive +Organiser, мы рекомендуем сначала экспортировать журнал в сторонний веб-сервис +типа <em>divelogs.de</em>, а затем импортировать в <em>Subsurface</em>, так как +<em>divelogs.de</em> поддерживает еще несколько других форматов, которые <em>Subsurface</em> +в данный момент не распознает.</p></div> +<div class="paragraph"><p>Если <em>Subsurface</em> поддерживает формат файла или стороннее программное обеспечение, то для +импорта такого файла достаточно в главном меню выбрать <em>Файл → Открыть журнал</em> или +<em>Импорт → Импорт журналов</em>. <em>Subsurface</em> поддерживает импорт с сторонних SQL баз данных +Suunto Dive Manager и Shearwater. При импорте <em>Subsurface</em> пытается определить +множественные записи относящиеся к одному погружению и объединить их. Если не +обнаружено проблем (разница во временной зоне или значительная разница во времени), +<em>Subsurface</em> не создаст дубликатов погружений.</p></div> +</div> +<div class="sect3"> +<h4 id="Unified_import">5.2.10. Использование универсального импорта</h4> +<div class="paragraph"><p>Импорт погружений из сторонних форматов выполняется с помощью универсального +диалога, который вы можете вызвать из Главного меню <em>Импорт → Импорт +журналов</em>. Вам будет представлено диалоговое окно <strong>А</strong>:</p></div> +<div class="imageblock" style="text-align:center;"> +<div class="content"> +<img src="images/Import1_f20.jpg" alt="Рисунок: Импорт журналов: шаг 1" /> +</div> +</div> +<div class="paragraph"><p>В нижней части окна находится выпадающий список типов файлов (как показано на +рисунке В):</p></div> +<div class="ulist"><ul> +<li> +<p> +XML-файлы журналов ((Divinglog 5.0, MacDive и другие программы) +</p> +</li> +<li> +<p> +Журналы Cochran +</p> +</li> +<li> +<p> +UDDF журналы (например, Kenozoooid) +</p> +</li> +<li> +<p> +UDCF журналы +</p> +</li> +<li> +<p> +Журналы Poseidon MKVI CCR +</p> +</li> +<li> +<p> +Журналы APD Inspiration/Evolution CCR +</p> +</li> +<li> +<p> +Журналы LiquiVision +</p> +</li> +<li> +<p> +Журналы divelog.de +</p> +</li> +<li> +<p> +Журналы OSTC Tools +</p> +</li> +<li> +<p> +JDiveLog +</p> +</li> +<li> +<p> +Suunto Dive Manager (DM3 и DM4) +</p> +</li> +<li> +<p> +CSV файлы (текстовые файлы и электронные таблицы), включая журналы APD CCR +</p> +</li> +</ul></div> +<div class="paragraph"><p>Выберите необходимый файл в списке и погружения будут добавлены в текущий +журнал. Прочие форматы, которые не поддерживаются <em>Subsurface</em>, можно +импортировать другим способом, который описан ниже.</p></div> +</div> +<div class="sect3"> +<h4 id="_импорт_из_ostc_tools">5.2.11. Импорт из OSTC Tools</h4> +<div class="paragraph"><p><em>OSTC Tools</em> - набор программ для платформы Microsoft Windows для семейства дайв-компьютеров OSTC. +, позволяющий загружать и организовывать погружения. <em>OSTC Tools</em> загружает данные погружений из +дайв-компьютера и сохраняет их в файле с расширением <em>.dive</em>. Эти файлы могут быть загружены в +<em>Subsurface</em> напрямую, используя диалог универсального импорта. В выпадающем списке в правой нижней +части окна выберите <em>_Файлы OSTCTools (.dive .DIVE)</em>. Это действие отобразит файлы данного типа +в панели выбора файлов. Выберите одно или несколько погружений и нажмите кнопку <em>Открыть</em>. Погружения +будет отображены в <strong>Списке погружений</strong>.</p></div> +<div class="paragraph"><p>Фактически, все устройства H&W, поддерживаемые OSTCTools, могут быть импортированы в <em>Subsurface</em>. +Этот список включает в себя OSTC, OSTC Mk2, OSTC 2N/2C, OSTC3, OSTC Sport и, возможно, непроверенные +Frog, OSTC2 и OSTC CR.</p></div> +<div class="paragraph"><p>Помните, однако, что OSTCTools <strong>не является</strong> полноценным журналом погружений, а только набором +инструментов для анализа и управления дайв-компьютерами OSTC. Поэтому только данные непосредственно +из дайв-компьютера могут быть импортированы в <em>Subsurface</em>; остальную информация (партнеры, +снаряжение, и т.д.) вам придется внести вручную.</p></div> +</div> +<div class="sect3"> +<h4 id="_импорт_из_mares_dive_organiser_v2_1">5.2.12. Импорт из Mares Dive Organiser V2.1</h4> +<div class="paragraph"><p>Так как Mares использует несвободное программное обеспечение для Microsoft, +эти журналы не могут быть импортированы в <em>Subsurface</em> напрямую. Вместо этого +вам придется выполнить процедуру, состоящую из трех шагов, и использовать +веб-сайт <em>www.divelogs.de</em> для извлечения информации о погружениях.</p></div> +<div class="olist arabic"><ol class="arabic"> +<li> +<p> +Данные журнала необходимо экспортировать на ваш ПК в файл с расширением +<em>.sdf</em>. Подробнее об этом написано в <a href="#Mares_Export">Приложении В</a> +</p> +</li> +<li> +<p> +Выгрузить данные на веб-сайт <em>www.divelogs.de</em>. Вам будет необходимо +создать учетную запись на сайте и войти под ней. После этого выберите +<em>Import Logbook → Mares Dive Organizer</em>. Внимательно следуйте инструкциям +и выгрузите файл с расширением <em>.sdf</em> в на сайт. +</p> +</li> +<li> +<p> +Наконец, импортируйте журнал с веб-сайта <em>divelogs.de</em> в <em>Subsurface</em> +используя следующие инструкции. +</p> +</li> +</ol></div> +</div> +<div class="sect3"> +<h4 id="S_ImportingDivelogsDe">5.2.13. Импорт с веб-сайта <strong>divelogs.de</strong></h4> +<div class="paragraph"><p>Импорт журнала с сайта <em>divelogs.de</em> очень простой и использует одно +диалоговое окно. Для начала в Главном меню выберите <em>Импорт → Импорт с сайта +divelogs.de). В появившемся окне (рисунок <strong>А</strong> слева ниже) введите свои имя +пользователя и пароль для сайта _divelogs.de</em> и нажмите кнопку <em>Загрузить</em>. +После нажатия кнопки в окне будет отображаться прогресс импорта, а в случае +успешного окончания будет показано уведомление (рисунок <strong>В</strong> справа ниже). Вам +необходимо нажать кнопку <em>Применить</em>, чтобы загруженные погружения появились в +<strong>Списке погружений</strong>.</p></div> +<div class="imageblock" style="text-align:center;"> +<div class="content"> +<img src="images/Divelogs1.jpg" alt="Рисунок:Импорт с сайта Divelogs.de" /> +</div> +</div> +</div> +<div class="sect3"> +<h4 id="S_ImportingCSVData">5.2.14. Импорт погружений в формате CSV</h4> +<div class="paragraph"><p>Файл со значениями, разделенными запятой (.csv) может использоваться как для импорта +профиля погружения (в случае ребризеров замкнутого цикла APD Inspiration и Evolution), так +и для загрузки общей информации о дайвах (если вы вели учет в электронной таблице). CSV +является универсальным и простым форматом для обмена данными между компьютерам и программами. +Более подробно об этом формате рассказывается в главе <a href="#S_CSV_Intro">Формат CSV для дайверов</a>. +<em>Subsurface</em> позволяет также выгружать журнал погружений для дальнейшей загрузки в другие программы. +Обратитесь к главе <a href="#S_Appendix_D">ПРИЛОЖЕНИЕ Г: Экспорт электронных таблиц в формат CSV</a> +за информацией по загрузке данных из электронных таблиц в <em>Subsurface</em>.</p></div> +</div> +<div class="sect3"> +<h4 id="S_ImportingCSVDives">5.2.15. Импорт погружений в CSV-формате из дайв-компьютеров и других программ</h4> +<div class="paragraph"><p>Для просмотре и редактирования CSV-файлов подойдет обычный текстовый редактор. +Данные в CSV-файле обычно организованы следующим образом: одна строка +заголовка и затем строки данных, по одной на каждую запись.</p></div> +<div class="paragraph"><p>В <em>Subsurface</em> может быть импортировано два вида CSV-файлов:</p></div> +<div class="olist arabic"><ol class="arabic"> +<li> +<p> +<em>Общая информация о погружении</em>: в этом случае файл содержит обычную для журнала информацию, + например, дату и время, глубину, длительность, имена партнеров и дайв-мастера, возможно + данные об баллонах и давлении до и после погружения, примечания. Все данные для одного + погружения хранятся в одной строке, а порядке определенном в заголовке. +</p> +</li> +<li> +<p> +<em>Профиль погружения</em>: журнал этого вида содержит гораздо больше информации об отдельно + взятом погружении. Например, он может включать данные с 30-ти секундным интервалом о + времени, глубине, температуре и давлении в баллоне в конкретный момент времени. Каждая строчка + в таком файле является выборкой параметров погружения в определенный момент. Для описание профиля + одного погружения необходимо много информации. Этот формат зачастую используется ребризерами + закрытого цикла и многочисленными программами для работы с дайв-компьютерами и ведения журналов. +</p> +</li> +</ol></div> +<div class="paragraph"><p>Перед импортом CSV-файла в <em>Subsurface</em> вам <strong>необходимо выяснить некоторые свойства этого +файла</strong>:</p></div> +<div class="paragraph"><p>а. Какой символ служит разделителем колонок в одной строке данных? Этот символ должен быть + запятой (,) или табуляцией? Вы можете определить это, открыв файл в текстовом редакторе. + Если разделителем служит запятая, то она хорошо заметна между полями данных в строке. Если + запятых не и числа выровнены в колонки, то с большей долей вероятности можно утверждать, что + разделителем служит символ табуляции.</p></div> +<div class="paragraph"><p>б. Данные из каких колонок должны быть импортированы в <em>Subsurface</em>? Содержит файл <em>Общую + информацию</em> или <em>Профиль погружения</em>? Откройте файл, использую текстовый редактор, и + отметьте для себя название колонок в заголовке и их позиционный номер.</p></div> +<div class="paragraph"><p>в. В какой системе мер (имперской или метрической_ записаны данные (например, глубина)?</p></div> +<div class="paragraph"><p>Вооружившись этой информацией, импорт данных в <em>Subsurface</em> не будет для вас проблемой. +В Главном меню выберите <em>Импорт → Импорт журналов</em>. В окне выбора файлов выберите тип +<em>CSV файлы</em> (в правом нижнем углу). Вам будет представлен список CSV-файлов в текущей +директории. Выберите файл, который необходимо импортировать, после чего вы увидите окно +конфигурации импорта:</p></div> +<div class="imageblock" style="text-align:center;"> +<div class="content"> +<img src="images/csv_import1_f20.jpg" alt="Рисунок: Диалог 1 импорт CSV" /> +</div> +</div> +<div class="paragraph"><p>Обратите внимание на выпадающий список в левом верхнем углу. Он содержит настройки для +часто встречающихся дайв-компьютеров и программ. Если ваш CSV-файл есть в этом списке, +используйте его. В противном случае следует выбрать <em>Импорт вручную</em>. В окне конфигурации +также есть выпадающие список для указания символа-разделителя, формата даты и длительности +погружения, а также используемой системы мер. Для успешного импорта очень важно задать +правильные значения в этих списках.</p></div> +<div class="paragraph"><p>На последнем шаге вы должны сопоставить поля данных в файле их названиям. Первая белая +строка таблицы данных содержит заголовки, найденные в CSV-файле. Голубая строка таблицы, +находящаяся непосредственно на ней, содержит названия <em>Subsurface</em>. В белой области, +находящейся сразу под выпадающими списками, представлены поля-метки, которые могут быть +импортированы в <em>Subsurface</em>. Эти метки, заключенные в овалы голубого цвета, необходимо +с помощью мыши перетащить на голубую полосу таблицы в соответствующую колонку. +Например, для того, чтобы импортировать номер погружения ("Dive # " в английской версии, +"№" в русской) <em>Subsurface</em>, перетащите метку "№" в ячейку над заголовком " # ", как показано +на рисунке ниже:</p></div> +<div class="imageblock" style="text-align:center;"> +<div class="content"> +<img src="images/csv_import2_f20.jpg" alt="Рисунок: Диалог 2 импорт CSV" /> +</div> +</div> +<div class="paragraph"><p>Продолжайте до тех пор, пока не сопоставите всем заголовкам соответствующие метки. После +этого нажмите клавишу _ОК в нижней части окна. Данные будут импортированы и погружения +будут отображены в панели <strong>Список погружений</strong>.</p></div> +<div class="sidebarblock" id="S_CSV_Intro"> +<div class="content"> +<div class="paragraph"><p><strong>Формат CSV для дайверов</strong></p></div> +<div class="admonitionblock"> +<table><tr> +<td class="icon"> +<img src="images/icons/important.png" alt="Важно" /> +</td> +<td class="content">Аббревиатура <em>CSV</em> происходит от английского <em>Comma-Separated Values</em>, что означает +<em>значения, разделенные запятой</em>. Файлы этого формата можно отредактировать с помощь текстового +редактора, например Notepad (Windows), gedit (Linux) или TextWrangler(OS/X). Преимущества +этого формата заключаются в том, что а) для его редактирования не нужно никакого специализированного +программного обеспечения, и б) в нем нет ничего лишнего и он может легко быть +отредактирован человеком. +Благодаря своей простоте, CSV-формат широко используется для обмена данными между различными +программами, например между электронными таблицами, базами данных и программами для дайвинга. +В <em>Subsurface</em> этот формат используется для импорта из других источников, таких как электронные +таблицы, и даже некоторых дайв-компьютеров.</td> +</tr></table> +</div> +<div class="paragraph"><p><em>CSV</em> файлы могут быть созданы и отредактированы с помощью обычного текстового редактора. +Самым важным атрибутом таких файлов является символ, разделяющий поля в одной строке данных. +Чаще всего таким символом является запятая, точка с запятой или табуляция. При экспорте из +электронной таблицы вам необходимо указать какой символ-разделитель использовать. CSV-файлы +обычно организованы следующим образом: в первой строке указаны заголовки (или <em>имена полей</em>), +а в последующих строках находятся данные, по одной строке на запись. Обратите внимание, что название +поля может состоять из нескольких слов, разделенных пробелами; "Дата дайва". Ниже приведен пример файла для четырех погружений +с использованием запятой в качестве символа-разделителя:</p></div> +<div class="literalblock"> +<div class="content"> +<pre><code>Место,Дата дайва,Время_дайва,Длительность, Глубина,Напарник +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>В таком виде его не так просто прочитать человеку. Вот эти же данные с использованием символа табуляции:</p></div> +<div class="literalblock"> +<div class="content"> +<pre><code>Место Дата дайва Время_дайва Длительность Глубина Напарник +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>Понятно, почему большинство людей предпочитает использовать табуляцию как разделитель. +Недостаток же в том, что мы не можете отличить табуляцию от пробела, как в заголовке <em>Дата дайва</em> +(на самом деле между словами стоит пробел, а табуляция находится после заголовка). +Также при слишком длинных названиях не всегда удается достичь выравнивания. Ниже приведен +урезанный пример профиля погружения с ребризера замкнутого цикла APD, в котором используется +табуляция в качестве разделителя:</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>При импорте <em>CSV</em> файлов <em>Subsurface</em> показывает не только заголовки, но и несколько первых +строк данных, что значительно упрощает работу. Обладая базовыми знаниями о формате <em>CSV</em>, +вы сможете без проблем импортировать свои данные в <em>Subsurface</em>.</p></div> +</div></div> +<div class="admonitionblock"> +<table><tr> +<td class="icon"> +<img src="images/icons/important.png" alt="Важно" /> +</td> +<td class="content">При импорте <em>CSV</em> есть несколько предостережений. Избегайте использования некоторых специальных +символов, таких амперсанд (&), меньше (<), больше (>) и двойной кавычки (") в значениях ячеек. +Файл должен быть сохранен в кодировке UTF-8, если вы используете символы отличные от латинских. +Размер файла также может быть причиной определенных проблем. Импорт 100 погружений за раз +(<em>Общая информация о погружениях_) вряд ли будет проблемой, но файлы большего размера могут. +При возникновении проблем с _Импортом CSV</em> попробуйте для начала уменьшить размер файла.</td> +</tr></table> +</div> +</div> +</div> +<div class="sect2"> +<h3 id="S_Companion">5.3. Импорт GPS координат из <em>вспомогательного приложения Subsurface</em> для мобильных телефонов</h3> +<div class="paragraph"><p>Используя <strong>вспомогательное приложение Subsurface</strong> на устройствах Android с GPS +датчиком или <a href="#S_iphone"><em>iPhone</em></a>, координаты дайв-сайтов могут быть автоматически +переданы в журнал <em>Subsurface</em>. Вспомогательное приложение сохраняет координаты на +выделенном сервере в Интернет. <em>Subsurface</em> в свою очередь умеет подгружать координаты +погружений с этого сервера.</p></div> +<div class="paragraph"><p>Чтобы воспользоваться этой функцией, вам необходимо:</p></div> +<div class="sect3"> +<h4 id="_создать_учетную_запись_для_вспомогательного_приложения">5.3.1. Создать учетную запись для вспомогательного приложения</h4> +<div class="ulist"><ul> +<li> +<p> +Зарегистрируйтесь на <a href="http://api.hohndel.org/login/">странице вспомогательного + приложения</a>. Вам будет прислано письмо-подтверждение с вашим персональным + <strong>КЛЮЧОМ</strong>. Этот ключ используется для авторизации на сервере и работы приложения. +</p> +</li> +<li> +<p> +Загрузите вспомогательное приложение с сайта + <a href="https://play.google.com/store/apps/details?id=org.subsurface">Google Play + Store</a> или с сайта + <a href="http://f-droid.org/repository/browse/?fdfilter=subsurface&fdid=org.subsurface">F-Droid</a>. +</p> +</li> +</ul></div> +</div> +<div class="sect3"> +<h4 id="_использование_приложения_на_android_смартфоне">5.3.2. Использование приложения на Android-смартфоне</h4> +<div class="paragraph"><p>При первом запуске приложения у вас есть три возможности:</p></div> +<div class="ulist"><ul> +<li> +<p> +<em>Создать учетную запись.</em> Это эквивалентно созданию учетной записи с помощью + интернет-броузера. Вы можете запросить <strong>КЛЮЧ</strong>, который будет прислан на вашу + электронную почту, но затем вам будет нужно активировать учетную запись на + <a href="http://api.hohndel.org/login/">странице вспомогательного приложения</a>. +</p> +</li> +<li> +<p> +<em>Получить учетную запись.</em> С помощью этого варианта вы можете восстановить + забытый ключ. +</p> +</li> +<li> +<p> +<em>Использовать учетную запись</em>. Вам нужно ввести ваш персональный ключ. + Приложение сохранит ключ и больше не будет его запрашивать, если только вы + не выберите в меню пункт <em>Отключиться</em>. +</p> +</li> +</ul></div> +<div class="admonitionblock"> +<table><tr> +<td class="icon"> +<img src="images/icons/important.png" alt="Важно" /> +</td> +<td class="content">В программе <em>Subsurface</em> нужно также ввести ваш персональный <strong>КЛЮЧ</strong> в +настройках приложения. Для этого выберите в меню <em>Файл → Настройки</em> и на +вкладке <em>Общие</em> введите <strong>КЛЮЧ</strong> в поле <em>ID пользователя</em> веб-сервиса +<em>Subsurface</em>. Это обеспечит синхронизацию между приложениями.</td> +</tr></table> +</div> +<div class="sect4"> +<h5 id="_создание_нового_места_погружения">Создание нового места погружения</h5> +<div class="paragraph"><p>Теперь вы готовы получить координаты места погружения и отправить их на +сервер. Экран смартфона выглядит как на левой картинке (<strong>А</strong>) ниже, но без +погружений.</p></div> +<div class="paragraph"><p>Нажмите на значок со знаком "+" в правом верхнем углу, чтобы добавить новый +дайв-сайт. Отобразится выпадающее меню с тремя вариантами:</p></div> +<div class="ulist"><ul> +<li> +<p> +Текущее положение: вам будет предложено ввести название места (и возможно + потребуется включить GPS, если он был выключен), после чего текущее + положение будет сохранено. +</p> +</li> +<li> +<p> +Выбрать на карте: этот вариант позволяет выбрать интересующее вас + местоположение на карте (см. рисунок <strong>В</strong>). Выбор точки осуществляется долгим + нажатием на сенсорном экране. Если место выбрано неправильно, выберите + другое, после чего нажмите на галочку в правом верхнем углу экрана. Укажите + название точки и дату и время погружения (рисунок <strong>С</strong>). Для корректного + импорта местоположения в <em>Subsurface</em> мы рекомендуем, чтобы время совпадало + со временем дайва. +</p> +</li> +</ul></div> +<div class="imageblock" style="text-align:center;"> +<div class="content"> +<img src="images/Companion_5.jpg" alt="Рисунок: Добавление погружения" /> +</div> +</div> +<div class="ulist"><ul> +<li> +<p> +Импорт GPX-файла: Ваше Android-устройство просканирует карту памяти и + покажет найденные GPX-файлы. Нажмите на выбранном файле, выберите + необходимые точки погружений и нажмите на галочку в правом верхнем углу + экрана. После этого выбранные места погружений будут отправлены на сервер в + Интернете и добавлены к списку дайвов в вашем смартфоне. +</p> +</li> +</ul></div> +</div> +</div> +<div class="sect3"> +<h4 id="_список_мест_погружений">5.3.3. Список мест погружений</h4> +<div class="paragraph"><p>На главном экране приложения отображается список мест погружений с +названиями, датой и временем. Слева от названия над полем выбора может +показываться значок с изображением стрелки, указывающей вверх, означающий, что +этот дайв ожидает отправки на сервер. Вы можете выбрать одно или несколько +погружений, проставив галочки в поле рядом с названием. Групповые операции +(<em>Отправить</em> и <em>Удалить</em>) применяются к выбранным погружениям.</p></div> +<div class="paragraph"><p>Погружения можно просматривать двумя способами: текстовый список и карта. +Режим отображения переключается нажатием на на текстовом поле <em>Погружения</em> в +левой верхней части экрана (см. рисунок <strong>А</strong> ниже). Находясь в режиме карты, вы +также можете нажать на текстовом поле <em>Карта</em> в левом верхнем углу (рисунок +<strong>В</strong>) и выбрать другой режим. При выборе погружения на карте или в списке, вам +будет представлен экран редактирования места дайва (рисунок <strong>С</strong>), на котором +вы можете поменять название точки и прочие детали.</p></div> +<div class="imageblock" style="text-align:center;"> +<div class="content"> +<img src="images/Companion_4.jpg" alt="Рисунок: Просмотр и редактирование мест погружений" /> +</div> +</div> +<div class="paragraph"><p>На экране редактирование вам доступно два инструмента (в правом верхнем углу +экрана):</p></div> +<div class="ulist"><ul> +<li> +<p> +Редактировать (карандаш): для изменения названия и прочих параметров +</p> +</li> +<li> +<p> +Карта: отобразить положение дайва на карте +</p> +</li> +</ul></div> +<div class="paragraph"><p>После редактирования и сохранения (рисунок <strong>С</strong>) вам необходимо отправить +погружение на сервер, как объясняется ниже.</p></div> +</div> +<div class="sect3"> +<h4 id="_отправка_погружения_на_сервер">5.3.4. Отправка погружения на сервер</h4> +<div class="paragraph"><p>Существует несколько способов выгрузки координат на сервер. Самый простой - отметить +погружения в списке (см. рисунок <strong>A</strong> ниже) и нажать на кнопку с изображением стрелки в +правом верхнем углу экрана.</p></div> +<div class="admonitionblock"> +<table><tr> +<td class="icon"> +<img src="images/icons/important.png" alt="Важно" /> +</td> +<td class="content">Будьте внимательны: находящаяся рядом кнопка с изображением мусорной корзины +удаляет точки погружений.</td> +</tr></table> +</div> +<div class="imageblock" style="text-align:center;"> +<div class="content"> +<img src="images/Companion_1.jpg" alt="Рисунок: Вспомогательное приложение Subsurface" /> +</div> +</div> +<div class="paragraph"><p>После вашей поездки с использованием вспомогательного приложения, +все погружения могут быть загружены в <em>Subsurface</em> (см. ниже).</p></div> +<div class="sect4"> +<h5 id="_дополнительные_функции_вспомогательного_приложения">Дополнительные функции вспомогательного приложения</h5> +<div class="paragraph"><p>В зависимости от размера экрана вашего Android-устройства дополнительные +возможности приложения доступны вам только после нажатия кнопки <em>Меню</em>. +Вам будет предложено на выбор 5 пунктов (рисунок <strong>В</strong> выше):</p></div> +</div> +<div class="sect4"> +<h5 id="_поиск">Поиск</h5> +<div class="paragraph"><p>Позволяет вам найти места погружений по названию и указанном временном +интервале.</p></div> +</div> +<div class="sect4"> +<h5 id="_запуск_фоновой_службы">Запуск фоновой службы</h5> +<div class="paragraph"><p>Вместо ручного ввода мест погружений, вы можете запустить фоновую службы +записи координат, которая автоматически будет сохранять места ваших дайвов.</p></div> +<div class="paragraph"><p>Следующие <em>Настройки</em> (см. ниже) влияют на работу этой службы:</p></div> +<div class="ulist"><ul> +<li> +<p> +<em>Минимальный интервал</em> в минутах. Приложение будет пытаться определить и + записать координаты местоположения каждые Х минут. +</p> +</li> +<li> +<p> +<em>Минимальное расстояние</em> в метрах. Минимальное расстояние в метрах между + двумя последовательными точками фиксации координат. +</p> +</li> +<li> +<p> +<em>Шаблон названия</em>. Название автоматически создаваемых точек погружения. +</p> +</li> +</ul></div> +<div class="admonitionblock"> +<table><tr> +<td class="icon"> +<img src="images/icons/info.jpg" alt="Подсказка" /> +</td> +<td class="content"><em>Как работает фоновая служба?</em> Предположим вы установили временной интервал в +5мин и минимальное расстояние равное 50 метрам. Приложение будет записывать +координаты каждые 5 минут <strong>или</strong> если вы переместитесь более чем на 50 метров +от предыдущей точки. Если же новая точка находится в радиусе 50м от +предыдущей, то она не будет сохранена. Если вы не двигаетесь, то будут +сохранены только координаты первой точки.</td> +</tr></table> +</div> +</div> +<div class="sect4"> +<h5 id="_отправить_все_местоположения">Отправить все местоположения</h5> +<div class="paragraph"><p>Отправляет на сервер все местоположения, которые не были выгружены ранее.</p></div> +</div> +<div class="sect4"> +<h5 id="_отключиться">Отключиться</h5> +<div class="paragraph"><p>Не самое удачное название. Эта функция удаляет сохраненные <strong>КЛЮЧ</strong>, который вы +вводили при первом старте. Может пригодиться в том случае, если другой дайвер +пользовался вашим смартфоном для записи координат погружений.</p></div> +</div> +<div class="sect4"> +<h5 id="_настройки">Настройки</h5> +<div class="paragraph"><p>В _Настройках_ приложения вам доступны следующие параметры:</p></div> +</div> +<div class="sect4"> +<h5 id="_сервер_и_учетная_запись">Сервер и учетная запись</h5> +<div class="ulist"><ul> +<li> +<p> +<em>URL веб-сервиса</em>. По умолчанию используется <a href="http://api.hohndel.org/">http://api.hohndel.org/</a> +</p> +</li> +<li> +<p> +<em>ID пользователя</em>. Ваш персональный ключ, полученный по email после + регистрации на сайте. Вы можете скопировать его из письма и вставить сюда, + либо ввести вручную. +</p> +</li> +</ul></div> +</div> +<div class="sect4"> +<h5 id="_синхронизация">Синхронизация</h5> +<div class="ulist"><ul> +<li> +<p> +<em>Синхронизация при старте</em>. Если выбран этот параметр, при каждом старте приложения погружения +на вашем Android-устройстве и веб-сервисе будут синхронизироваться. +</p> +</li> +<li> +<p> +<em>Отправлять новые</em>. Если этот параметр установлен, добавленные точки будут + автоматически отправляться на сервер. +</p> +</li> +</ul></div> +</div> +<div class="sect4"> +<h5 id="_фоновая_служба">Фоновая служба</h5> +<div class="paragraph"><p>Параметры фоновой службы уже были описаны выше.</p></div> +</div> +<div class="sect4"> +<h5 id="_разное">Разное</h5> +<div class="ulist"><ul> +<li> +<p> +<em>Список рассылки</em>. Отсюда вы можете отправить письмо разработчикам + <em>Subsurface</em>. +</p> +</li> +<li> +<p> +<em>Веб-сайт</em>. Ссылка на веб-сайт <em>Subsurface</em>. +</p> +</li> +<li> +<p> +<em>Версия</em>. Текущая версия вспомогательного приложения. +</p> +</li> +</ul></div> +</div> +</div> +<div class="sect3"> +<h4 id="S_iphone">5.3.5. Запись координат погружений из <em>вспомогательного приложения Subsurface</em> для <em>iPhone</em></h4> +<div class="paragraph"><p>Интерфейс приложения для iPhone крайне прост. Необходимо ввести ключ, полученный при +регистрации, в соответствующее поле, затем нажать "Dive in" (см. левую картинку на рисунке +ниже), после чего можно приступать к сбору информации о местоположении погружений.</p></div> +<div class="imageblock" style="text-align:center;"> +<div class="content"> +<img src="images/iphone.jpg" alt="Рисунок: Использование вспомогательного приложения на iPhone" width="640" /> +</div> +</div> +<div class="paragraph"><p>Погружения могут быть добавлены автоматически или вручную. В ручном режиме, служба получения +координат запускается автоматически, а в нижней части экрана появляется красная полоса. После +завершения погружения вам нужно нажать на красной области, чтобы остановить службу +позиционирования. При запущенной службе позиционирования вы можете добавлять погружения +только в ручном режиме.</p></div> +<div class="paragraph"><p>Позже вы можете отредактировать название места погружения, выбрав и нажав на него в списке. +Другие поля для редактирования недоступны. Список дайвов автоматически выгружается на сервер, +возможно вручную синхронизировать погружения отсутствует.</p></div> +</div> +<div class="sect3"> +<h4 id="_загрузка_координат_погружений_в_журнал_em_subsurface_em">5.3.6. Загрузка координат погружений в журнал <em>Subsurface</em></h4> +<div class="paragraph"><p>Перед получением GPS-координат с сервера, погружения должны быть загружены в +журнал из дайв-компьютера или введены вручную. Для загрузки координат выберите +в главном меню <em>Импорт → Импорт координат</em> или нажмите комбинацию клавиш +Ctrl-G. Вам будет представлено окно, как показано на рисунке <strong>А</strong> ниже. При +первом импорте необходимо указать ключ, после чего нажмите кнопку <em>Загрузить</em>. +Окно примет следующий вид (рисунок <strong>В</strong>):</p></div> +<div class="imageblock" style="text-align:center;"> +<div class="content"> +<img src="images/DownloadGPS.jpg" alt="Рисунок: Импорт координат погружений" /> +</div> +</div> +<div class="paragraph"><p>Обратите внимание, что теперь кнопка <em>Применить</em> доступна. Нажатие на нее обновит +названия мест и координаты недавно загруженных или введенных вручную погружений, у +которых дата и время совпадают с временем фиксации на смартфоне. Если вы уже +указали название дайв-сайта перед импортом координат, <em>Subsurface</em> отдаст +предпочтение этим данных и не будет их перезаписывать.</p></div> +<div class="paragraph"><p>Важно, чтобы часы на вашем смартфоне и дайв-компьютере были синхронизированы, +так как <em>Subsurface</em> сопоставляет погружения именно по дате-времени, хотя и +допускает некоторую погрешность. В случае большого разбега в показаниях +времени координаты не будут обновлены.</p></div> +<div class="paragraph"><p>Сопоставление по дате-времени может не сработать и по другим причинам +например, из-за часовых поясов, или в случае нескольких повторных погружений в +одном месте (в этом случае координаты будут сопоставлены только с первым +погружением в серии). Для обхода этой проблемы мы рекомендуем вручную изменить +дату-время погружения <strong>перед</strong> загрузкой GPS-координат и вернуть в начальное +значение <strong>после</strong> импорта.</p></div> +<div class="admonitionblock"> +<table><tr> +<td class="icon"> +<img src="images/icons/info.jpg" alt="Замечание" /> +</td> +<td class="content">Полезные советы:</td> +</tr></table> +</div> +<div class="ulist"><ul> +<li> +<p> +<em>Фоновая служба</em>, будучи хорошим подспорьем, может тем не менее заполнить весь +список точками, не имеющими никакого отношения к погружениям, а отражающими +путь судна. И в настоящий момент удаление этих точек с сервера довольно +проблематично. Поэтому очень желательно удалить ненужные точки перед отправкой +их на сервер. Это необходимо, если вы хотите видеть на карте только точки погружений. +</p> +</li> +<li> +<p> +Желательно для погружений указывать информативные названия, и как минимум +задать вразумительное название шаблона для автоматически добавляемых +погружений. +</p> +</li> +</ul></div> +</div> +</div> +<div class="sect2"> +<h3 id="S_LoadImage">5.4. Добавление фотографий к погружениям</h3> +<div class="paragraph"><p>Многие (если не все) дайверы берут с собой на погружение камеру, чтобы сделать +несколько запоминающихся фото. <em>Subsurface</em> позволяет прикрепить эти +фотографии к конкретному погружению и просматривать их на профиле погружения +и на вкладке <em>Фотографии</em>.</p></div> +<div class="sect3"> +<h4 id="_загрузка_фотографий_и_синхронизация_времени_между_фотоаппаратом_и_дайв_компьютером">5.4.1. Загрузка фотографий и синхронизация времени между фотоаппаратом и дайв-компьютером</h4> +<div class="paragraph"><p>Нажмите левой кнопкой мыши на погружении в списке, чтобы выбрать его, а затем +правой кнопкой мыши и выберите из контекстного меню пункт <em>Загрузить фото</em>:</p></div> +<div class="imageblock" style="text-align:center;"> +<div class="content"> +<img src="images/LoadImage1_f20.jpg" alt="Рисунок: Меню загрузки фотографий" /> +</div> +</div> +<div class="paragraph"><p>В системном диалоге выбора файлов выберите фотографии для загрузки в +<em>Subsurface</em> и нажмите клавишу <em>Открыть</em>:</p></div> +<div class="imageblock" style="text-align:center;"> +<div class="content"> +<img src="images/LoadImage2_f20.jpg" alt="Рисунок: Выбор фотографий для загрузки" /> +</div> +</div> +<div class="paragraph"><p>Вам будет представлен диалог, показанный ниже. Проблема состоит в том, что +зачастую время на дайв-компьютере и камере, используемых при погружении, +не совпадают. Разница может составлять несколько минут. Если <em>Subsurface</em> +сможет синхронизировать время между этими двумя устройствами, то сможет и +правильно расположить фотографии на профиле погружения.</p></div> +<div class="paragraph"><p>Добиться такой синхронизации в <em>Subsurface</em> можно двумя способами:</p></div> +<div class="ulist"><ul> +<li> +<p> +<strong>Вручную</strong>: Если вы записали точное время камеры в самом начале погружения, +то вы можете вычислить смещение по времени. Если вы не меняли установки +даты-времени на своих устройствах, то вы можете это сделать в конце дня после +серии дайвов. После этого вы можете указать этот смещение в поле <em>Сдвинуть +время изображений</em> , как показано на рисунке <strong>А</strong>. Если часы камеры спешат на +7 минут от показаний часов дайв-компьютера, укажите значение смещения 00:07, +выберите в переключателе <em>Раньше - Позже</em> значение <em>Раньше</em> (поскольку часы +камеры спешат, нужно сдвинуть время на 7 минут раньше) и нажмите кнопку +<em>ОК</em>. +</p> +</li> +</ul></div> +<div class="imageblock" style="text-align:center;"> +<div class="content"> +<img src="images/LoadImage3b_f20.jpg" alt="Рисунок: Диалог синхронизации" /> +</div> +</div> +<div class="ulist"><ul> +<li> +<p> +<strong>По фотографии</strong>: <em>Subsurface</em> предлагает другой хитрый способ для синхронизации +времени. Если вы сделаете фотографию экрана дайв-компьютера с показаниями +часов, <em>Subsurface</em> сможет получить точное время камеры из информации, +сохраняемой в каждой сделанной фотографии. Для этого используйте нижнюю часть +диалогового окна <em>Сдвинуть время изображений</em>. При этом значения сдвига +в верхней части окна игнорируются. +Нажмите на горизонтально вытянутой кнопке <em>Выбрать изображения отображающие +время на дайв-компьютере</em>. В окне выбора файлов укажите фото вашего +дайв-компьютера и нажмите <em>Открыть</em>. <em>Subsurface</em> отобразит это фото в правой +нижней части окна и к этому моменту будет знать время, когда эта фотография +была сделана. Теперь вам только осталось в поле слева от фотографии указать +дату-время компьютера, как указано на фото. Основываясь на этой информации, +<em>Subsurface</em> может вычислить разницу во времени между камерой и +дайв-компьютером. На рисунке <strong>В</strong> выше показано загруженное изображение компьютера +и дата-время у него, перенесенные в поле слева. +</p> +</li> +</ul></div> +<div class="paragraph"><p>Если фотография была сделана задолго до или после погружения, она не будет +показываться на профиле. <em>Subsurface</em> допускает интервал равный 30 минутам до и после погружения.</p></div> +</div> +<div class="sect3"> +<h4 id="_просмотр_фотографий">5.4.2. Просмотр фотографий</h4> +<div class="paragraph"><p>После загрузки фотографии отображаются:</p></div> +<div class="ulist"><ul> +<li> +<p> +на вкладке <em>Фотографии</em> информационной панели +</p> +</li> +<li> +<p> +в виде маленьких иконок на профиле погружения в соответствии + со временем фото: + Для просмотра добавленных фотографий на профиле погружений, активируйте + переключатель <em>Фотографии</em> на панели слева от профиля погружения: +</p> +</li> +</ul></div> +<div class="imageblock" style="text-align:left;"> +<div class="content"> +<img src="images/icons/ShowPhotos_f20.png" alt="Рисунок: Переключатель Фотографии" /> +</div> +</div> +<div class="paragraph"><p>Профиль погружения при этом будет выглядеть следующим образом:</p></div> +<div class="imageblock" style="text-align:center;"> +<div class="content"> +<img src="images/LoadImage4_f20.jpg" alt="Рисунок: Фотографии на профиле" /> +</div> +</div> +<div class="paragraph"><p>При наведении мышкой на иконку фото на профиле, будет показана миниатюрная +фотография:</p></div> +<div class="imageblock" style="text-align:center;"> +<div class="content"> +<img src="images/LoadImage5_f20.jpg" alt="Рисунок:Миниатюрное фото на профиле" /> +</div> +</div> +<div class="paragraph"><p>Обратите внимание, что в левом верхнем углу миниатюры есть изображение +мусорной корзины, при нажатии на которое картинка будет удалена. Поэтому +будьте внимательны, кожа щелкаете мышкой на картинке. При нажатии мышкой на +миниатюрное фото (в профиле или на вкладке <em>Фотографии), полноразмерная +фотография откроется во внешней программе для просмотра изображений. Фотографии также могут +быть удалены на вкладке _Фотографии</em> (см. ниже).</p></div> +<div class="imageblock" style="text-align:center;"> +<div class="content"> +<img src="images/LoadImage6_f20.jpg" alt="Рисунок: Просмотр полноразмерных фотографий" /> +</div> +</div> +</div> +<div class="sect3"> +<h4 id="_вкладка_em_фотографии_em">5.4.3. Вкладка <em>Фотографии</em></h4> +<div class="paragraph"><p>Фотографии, добавленные к погружению, отображаются миниатюрными картинками на +вкладке <em>Фотографии</em> в <em>Информационной панели</em>. Снимки, сделанные в серии и +имеющие короткий временной интервал, могут перекрывать друг друга на профиле, +но легко различимы на этой вкладке. Одиночный щелчок мышью на фотографии +выделяет ее, двойной щелчок мышью открывает окно просмотра фото во внешней +программе. Фотографию можно удалить на вкладке <em>Фотографии</em>, выбрав ее щелчком +мыши и нажатием клавиши <em>Del</em> (фотография будет удалена и из профиля).</p></div> +</div> +<div class="sect3"> +<h4 id="_фотографии_на_внешнем_жестком_диске">5.4.4. Фотографии на внешнем жестком диске</h4> +<div class="paragraph"><p>Многие фотографы хранят свои снимки на внешнем накопителе. Если внешний диск +подключен, то <em>Subsurface</em> в большинстве случаев увидит его, и таким образом +будет обеспечен доступ к внешнему хранилищу фотографий. При этом вы добавляете +фото с внешнего диска так, как описан выше. Однако после того, как внешний +накопитель отключен, у <em>Subsurface</em> не будет доступа к фотографиям. Если на +панели кнопок-переключателей (слева от профиля) нажата кнопка <em>Миниатюры +фотографий</em>, то вместо картинок на профиле буду показываться белые точки, а на +вкладке <em>Фотографии</em> только имена файлов вместо миниатюр. После подключения +внешнего накопителя вы снова сможете увидеть фотографии.</p></div> +</div> +<div class="sect3"> +<h4 id="S_FindMovedImages">5.4.5. Перенос фотографий между директориями, жесткими дисками и компьютерами</h4> +<div class="paragraph"><p>После загрузки фотографии в <em>Subsurface</em> и ее привязки к погружению, папка, в +которой она находится, запоминается с тем, чтобы найти фото в следующий раз, +когда вы откроете погружение. Если фотография или вся коллекция переносится на +другой жесткий диск или компьютер, маловероятно что структура каталогов будет +такой же, как до переноса. <em>Subsurface</em> попытается загрузить фотографии из их +начального местоположения и не сможет их найти. Вместо того, чтобы удалять все +фотографии и загружать их заново, <em>Subsurface</em> предлагает механизм, который значительно +упрощает процесс обновления местоположения фотографий: обновление с помощью "отпечатков".</p></div> +<div class="paragraph"><p>Когда фотография загружается в <em>Subsurface</em>, для нее вычисляется цифровой отпечаток, который +сохраняется наряду с прочей информацией о фотографии. После переноса фото-коллекции (которая уже +была загружена в <em>Subsurface</em>) в другую папку, диск или компьютер, <em>Subsurface</em> может выполнить +следующие шаги:</p></div> +<div class="ulist"><ul> +<li> +<p> +рекурсивно просканировать указанную папку и вложенные поддиректории, куда фотографии были + перенесены, +</p> +</li> +<li> +<p> +вычислить отпечатки для всех найденных фотографий и +</p> +</li> +<li> +<p> +если найдено соответствие между новым отпечатком и оригинальным, вычисленным при начальной + загрузке фотографии (даже если имена файлов изменились), то информация о новом местоположении + будет автоматически обновлена, с тем чтобы <em>Subsurface</em> мог найти ее в новой директории. +</p> +</li> +</ul></div> +<div class="paragraph"><p>Это можно сделать, выбрав в <strong>Главном меню</strong> пункт <em>Файл → Найти перемещенные фото</em>. Вам будет +предложено выбрать папку, куда были перенесены фотографии. Выберите директорию и нажмите кнопку +<em>Сканировать</em>. Этот процесс может занять несколько минут, после чего сможет отобразить фотографии +для выбранного погружения.</p></div> +<div class="sidebarblock" id="Image_fingerprint_upgrade"> +<div class="content"> +<div class="paragraph"><p><strong>Обновления существующих коллекций фотографий без отпечатков</strong></p></div> +<div class="admonitionblock"> +<table><tr> +<td class="icon"> +<img src="images/icons/important.png" alt="Важно" /> +</td> +<td class="content"><em>Subsurface</em> автоматически вычисляет отпечатки всех фотографий, загруженных в него. При работе +с фото, удостоверьтесь, что они доступны для <em>Subsurface</em>.</td> +</tr></table> +</div> +<div class="paragraph"><p><em>Subsurface</em> каждый раз проверяет и, если необходимо, обновляет отпечатки фотографий в рамках отдельного погружения, если: +- Ассоциированные фото отображаются на профиле в фите миниатюр. +- Были внесены изменения на вкладке <strong>Примечания</strong> и была нажата кнопка <em>Применить изменения</em>.</p></div> +</div></div> +</div> +</div> +<div class="sect2"> +<h3 id="_ведение_журнала_для_специальных_типов_погружений">5.5. Ведение журнала для специальных типов погружений</h3> +<div class="sect3"> +<h4 id="S_MulticylinderDives">5.5.1. Погружения с несколькими баллонами</h4> +<div class="paragraph"><p><em>Subsurface</em> позволяет без проблем вести учет многобаллонных погружений. Такие погружения обычно +выполняются если (а) не хватает воздуха для совершения погружения на одном баллоне; (б) нужно более +одной смеси по причине большой глубины или для выполнения декомпрессионных процедур. Поэтому +многобаллонные погружения зачастую выполняются техническими дайверами, которые ныряют дольше и глубже. +Для <em>Subsurface</em> важна только следующая информация:</p></div> +<div class="ulist"><ul> +<li> +<p> +<strong>Описание баллонов погружения</strong>. Это выполняется на вкладке <strong>Снаряжение</strong> информационной панели так, + как описано <a href="#cylinder_definitions">выше</a>. Перечислите все баллоны, указав их характеристики и + типы смесей. +</p> +</li> +<li> +<p> +<strong>Запишите время замены смесей</strong>: некоторые дайв-компьютеры предоставляют такую информацию (при + условии, что вы нажали соответствующую кнопку). Если же компьютер не сохраняет эту информацию, + вы можете записать время замены на слэйте. +</p> +</li> +<li> +<p> +<strong>Укажите события замены смеси на профиле погружения</strong>: если вы выполнили предыдущий пункт, то вам + нужно отметить эти события на профиле. Для этого щелкните на нем правой кнопкой мыши в соответствующее + время и в контекстном меню выберите пункт "Добавить замену газа" и укажите нужный баллон из списка, + созданного на первом шаге (см. рисунок ниже). Если на панели переключателей нажата кнопка <strong>Замена + смесей</strong>, то эти события будут также отображены на полосе в нижней части профиля погружения. +</p> +</li> +</ul></div> +<div class="paragraph"><p>Если вы выполнили эти шаги, то <em>Subsurface</em> будет отображать выбранные баллоны для соответствующих +сегментов погружения. Ниже на рисунке представлен профиль многобаллонного погружения, начинающегося +с EAN28, и дальнейшим переходом на 26 минуте на EAN50 для выполнения декомпрессии.</p></div> +<div class="imageblock" style="text-align:center;"> +<div class="content"> +<img src="images/multicylinder_dive.jpg" alt="Рисунок: Профиль многобаллонного погружения" /> +</div> +</div> +</div> +<div class="sect3"> +<h4 id="_погружения_в_конфигурации_side_mount">5.5.2. Погружения в конфигурации side-mount</h4> +<div class="paragraph"><p>Погружения в конфигурации с боковой подвеской является просто еще одной из разновидностей +многобаллонных погружений, зачастую с двумя или всеми баллонами, заполненными одинаковой смесью. +Хотя эта конфигурация наиболее популяра среди пещерных дайвером, она может использоваться и для +рекреационных погружений после соответствующей подготовки. Как и в случае многобаллонных погружений, +для учета таких погружений необходимо выполнить три шага:</p></div> +<div class="ulist"><ul> +<li> +<p> +<strong>Запись событий смена баллонов во время погружения</strong>. Поскольку сайд-маунт погружения + обычно выполняются с двумя баллонами с воздухом или одинаковым газом, <em>Subsurface</em> + различает баллоны между собой. Чего не скажешь о большинстве дайв-компьютеров, которые + делают понимают переключение между разными <em>смесями</em>, а не <em>баллонами</em>. Это означает, что + при импорте погружений с таких компьютеров события о смене баллонов с одинаковой смесью + не будут загружены. Поэтому вам придется записывать эти события на слэйте, или, если + ваш компьютер умеет, ставить закладки для таких событий, чтобы позже их загрузить. + Сохранение событий замены баллонов - наиболее сложная задача при ведении журнала сайд-маунт погружений. +</p> +</li> +<li> +<p> +<strong>Укажите конфигурацию баллонов</strong> на вкладке <strong>Снаряжение</strong> (см. рисунок ниже, на котором + добавлено два 12-литровых баллона). +</p> +</li> +<li> +<p> +<strong>Укажите события смены баллонов</strong>. После импорта погружения из дайв-компьютера в <em>Subsurface</em>, +вам необходимо проставить события замены баллонов на профиле погружения. События добавляются +щелчком правой кнопки мыши в соответствующем месте профиля и выбором пункта <em>Добавить замену смеси</em> +в выпадающем контекстном меню. В списке показывает список доступных баллонов, при этом текущий +активный баллон будет недоступен для выбора. На картинке ниже Баллон 1 недоступен, оставляя для +выбора только Баллон 2. Выберите нужный баллон из списка. Событие смены баллона будет отображено на +профиле соответствующей картинкой. Если активировано отображение <strong>Замена смесей</strong> (на панели +инструментов слева от профиля), то соответствующая информация будет показываться в нижней части профиля. +После добавления всех событий замены к профилю, на нем должны отображаться корректные значения +давления по всех баллонах, как показано на следующем рисунке. +</p> +</li> +</ul></div> +<div class="imageblock" style="text-align:center;"> +<div class="content"> +<img src="images/sidemount1.jpg" alt="Рисунок: Профиль погружения в конфигурации сайд-маунт" /> +</div> +</div> +<div class="paragraph"><p>Эта глава демонстрирует гибкость <em>Subsurface</em> при ведении журналов погружений.</p></div> +</div> +<div class="sect3"> +<h4 id="S_sSCR_dives">5.5.3. Погружения с ребризером полузамкнутого цикла (SCR)</h4> +<div class="admonitionblock"> +<table><tr> +<td class="icon"> +<img src="images/halcyon_RB80.jpg" alt="Замечание" /> +</td> +<td class="content">Пассивные ребризеры полузамкнутого цикла (pSCR) представляют собой дыхательный аппарат, рециркулирующий +дыхательную смесь, удаляя из нее выдыхаемый углекислый газ. Приблизительно десятая часть выдыхаемого +воздуха сбрасывается в воду, при этом свежая дыхательная смесь (обычно Nitrox) добавляется из баллона. +Поэтому даже на одном баллоне можно провести гораздо больше времени под водой, чем используя +рекреационную конфигурацию на открытом цикле. В случае pSCR свежая смесь подается из баллона при +каждом вдохе. Активные ребризеры (aSCR) подают свежую смесь из баллона постоянно.</td> +</tr></table> +</div> +<div class="paragraph"><p>Для учета погружений с использованием pSCR не требуется никаких специальных действий. Достаточно:</p></div> +<div class="ulist"><ul> +<li> +<p> +Выбрать режим погружения pSCR на вкладке <strong>Погружение</strong> +</p> +</li> +<li> +<p> +Погружения с использованием pSCR обычно выполняются с заменой смесей. Укажите все необходимые + баллоны как описано выше и укажите события замены смесей на профиле, как указано выше в главе + <a href="#S_MulticylinderDives">Погружения с несколькими баллонами</a>. +</p> +</li> +</ul></div> +<div class="paragraph"><p>При выборе режима pSCR, расчетный потолок погружения учитывает снижение уровня кислорода в области +загубника, что увеличивает время декомпрессии. Ниже приведен профиль pSCR погружения на смеси EAN36 +и с одним баллоном кислорода для декомпрессии. Обратите внимание, что погружение заняло более двух +часов.</p></div> +<div class="imageblock" style="text-align:center;"> +<div class="content"> +<img src="images/pSCR_profile.jpg" alt="Рисунок: Профиль погружения с pSCR" /> +</div> +</div> +</div> +<div class="sect3"> +<h4 id="S_CCR_dives">5.5.4. Погружения с ребризером закрытого цикла (CCR)</h4> +<div class="admonitionblock"> +<table><tr> +<td class="icon"> +<img src="images/APD.jpg" alt="Замечание" /> +</td> +<td class="content">Ребризеры замкнутого цикла используют передовые технологии для рециркуляции отработанного газа, +выполняя две функции для поддержания концентрации кислорода, делая смест пригодной для дыхания: +а) удаление углекислого газа из выдыхаемого воздуха +б) поддержание концентрации кислорода в безопасных пределах. +На текущий момент <em>Subsurface</em> обеспечивает наилучшую поддержку CCR дайв-компьютера Poseidon +MkVI Discovery. Интерфейс работы с ребризерами замнутого цикла находится в активной разработке и на +текущий момент считается экспериментальным. А отличие от рекреационных дайв-компьютеров, системы +CCR не позволяют загружать журналы нескольких погружений одномоментно. Вместо этого каждое погружение +хранится отдельно. Это означает, что <em>Subsurface</em> не может загружать погружения непосредственно с +дайв-компьютера ребризера. Погружения должны быть импортированы таким же образом, как и из других +цифровых источников.</td> +</tr></table> +</div> +<div class="sect4"> +<h5 id="_импорт_погружения_с_ребризером_закрытого_цикла">Импорт погружения с ребризером закрытого цикла</h5> +<div class="paragraph"><p>Прочитайте главу <a href="#S_ImportingAlienDiveLogs">Импорт погружений из других +цифровых источников</a>. В главном меню <em>Subsurface</em> выберите <em>Импорт → Импорт +журналов</em> чтобы открыть окно <a href="#Unified_import">Универсальный импорт</a>. Как +описано в этой главе, в правой нижней части окна находится список +поддерживаемых источников, среди которых есть и файлы (Poseidon) MkVI +(поддержка другого CCR-оборудование активно развивается). Выбрав нужный формат +и директорию с файлами-журналами, вам нужно выбрать конкретный журнал +погружения (в случае MkVI это один файл с расширением .txt). После выбора +файла нажмите на кнопку <em>Открыть</em>.</p></div> +</div> +</div> +<div class="sect3"> +<h4 id="_информация_отображаемая_для_ccr_погружений">5.5.5. Информация, отображаемая для CCR-погружений</h4> +<div class="paragraph"><p><em>Парциальные давления газов</em>: График парциального давления кислорода показывает информацию с +кислородных датчиков ребризера. В отличие от рекреационного режима, где значения pO<sub>2</sub> высчитываются +исходя из состава смеси и глубины, для CCR-погружений эти значения берутся от датчиков. В этом случае +график должен быть достаточно ровным, соответствуя значению установки кислорода (set-point). Среднее значение +pO<sub>2</sub> не является средним значением от датчика, а рассчитано <em>Subsurface</em> следующим +образом:</p></div> +<div class="ulist"><ul> +<li> +<p> +для двух датчиков O<sub>2</sub> рассчитывается среднее значение. +</p> +</li> +<li> +<p> +для систем с тремя датчиками (например, APD) также используется среднее значение. Однако разница + в показаниях разных датчиков более 0,1 бар в один момент времени, такое значение считается + ложны. Если один из датчиков возвращает ложное значение, то он игнорируется. +</p> +</li> +<li> +<p> +если данные от датчиков отсутствуют, то значение pO<sub>2</sub> принимается равным установке. +</p> +</li> +</ul></div> +<div class="paragraph"><p>Среднее значение pO<sub>2</sub> сенсоров отображается зеленой линией.</p></div> +<div class="paragraph"><p>Значения установок кислорода, а также показания индивидуальных датчиков, могут быть показаны на +профиле. Отображение расширенной информации для CCR-погружения регулируется в <em>Настройках_ (доступны +в <a href="#S_CCR_options">_Файл → Настройки → Профиль</em></a>. Вот настройки, влияющие на отображение pO<sub>2</sub> +на профиле погружения при нажатой на панели переключателей кнопке <em>График pO<sub>2</sub></em>.</p></div> +<div class="imageblock" style="text-align:center;"> +<div class="content"> +<img src="images/CCR_preferences_f20.jpg" alt="Рисунок: Настройки профиля CCR-погружения" /> +</div> +</div> +<div class="paragraph"><p>Первый параметр позволяет показать график значения установки (set-point), который отображается +красной линией поверх графика парциального давления и позволяет сравнить значения среднего +измеренного парциального значения с установкой, как показано на рисунке ниже:</p></div> +<div class="imageblock" style="text-align:center;"> +<div class="content"> +<img src="images/CCR_setpoint_f20.jpg" alt="Рисунок: Графики pO~2~ и установки CCR" /> +</div> +</div> +<div class="paragraph"><p>Второй параметр позволяет вывести график от каждого сенсора ребризера. Цветовая кодировка сенсоров +следующая:</p></div> +<div class="ulist"><ul> +<li> +<p> +Сенсор 1: серый +</p> +</li> +<li> +<p> +Сенсор 2: голубой +</p> +</li> +<li> +<p> +Сенсор 3: коричневый +</p> +</li> +</ul></div> +<div class="paragraph"><p>Среднее значение pO<sub>2</sub> показывается зеленым цветом. Такое отображение позволяет непосредственно +сравнить данные от каждого сенсора и выявить странно низкие или абсолютно неверные показания.</p></div> +<div class="imageblock" style="text-align:center;"> +<div class="content"> +<img src="images/CCR_sensor_data_f20.jpg" alt="Рисунок: Графики сенсоров CCR" /> +</div> +</div> +<div class="paragraph"><p>График установки может быть наложен поверх графика парциальных давлений, для этого нужно поставить +галочки напротив обоих параметров. Парциальные давления азота (и гелия, если применимо) отображаются +так же, как для погружения на открытом цикле.</p></div> +<div class="paragraph"><p><em>События</em>: в случае погружений с ребризером могут быть записаны дополнительные события, например, +перевод загубника в режим открытого цикла. Такие события отображаются на профиле в виде желтых +треугольников. При наведении на него указателя мыши, в <a href="#S_InfoBox">плавающем информационном окне</a> +показывается описание события.</p></div> +<div class="paragraph"><p><em>Давление в баллонах:</em> некоторые CCR дайв-компьютеры (например, Poseidon MkVI) сохраняют информацию +о давлении в баллонах с кислородом и дилуентом. График давлений в этих баллонах отображается +зелеными линиями поверх профиля глубины. В дополнение к этому, информация о начальном и конечном +давлениях в баллонах с дилуентом и кислородом показывается на вкладке <em>Снаряжение</em>. +Ниже представлен профиль CCR-погружения, на котором показаны графики значений установки, сенсоров и +давлений в баллонах. В этом случае мы видим согласованность показаний двух сенсоров.</p></div> +<div class="imageblock" style="text-align:center;"> +<div class="content"> +<img src="images/CCR_dive_profile_f20.jpg" alt="Рисунок: Профиль CCR-погружения" /> +</div> +</div> +<div class="paragraph"><p><em>Дополнительная информация</em>: Информация, специфичная для конкретного оборудования, отображается в +<em>Subsurface</em> на вкладке <a href="#S_ExtraDataTab">Дополнительная информация</a>. Она может включать настройки +оборудования и прочие данные.</p></div> +<div class="paragraph"><p>Деко-потолок, вычисленный <em>Subsurface</em>, не всегда точен, потому что зачастую невозможно узнать +точное парциальное давление азота в цикле из журнала, импортированного из ребризера. Однако, многие +дайв-компьютеры, поддерживающие ребризеры, сообщают информацию о своем вычисленном деко-потолке в +журнале, и это значение может быть более точным. Для отображения этого потолка необходимо активировать +соответствующую кнопку на панели слева от профиля погружения?</p></div> +<div class="imageblock"> +<div class="content"> +<img src="images/icons/cceiling.jpg" alt="Кнопка отображения потолка дайв-компьютера" /> +</div> +</div> +<div class="paragraph"><p>По умолчанию потолок дайв-компьютера отображается на профиле погружения белым цветом. Вы можете +отобразить его красным, выбрав соответствующий параметр в <em>Файл → Настройки → Профиль</em>. Ниже +показан профиль погружения с отображенным потолком дайв-компьютера:</p></div> +<div class="imageblock" style="text-align:center;"> +<div class="content"> +<img src="images/CCR_dive_ceilingF22.jpg" alt="Рисунок: Деко-потолок дайв-компьютера" /> +</div> +</div> +<div class="paragraph"><p>За более детальной информацией по загрузке погружений из ребризеров Poseidon MkVI и APD обратитесь +к <a href="#S_PoseidonMkVI">ПРИЛОЖЕНИЮ Б</a>.</p></div> +</div> +</div> +</div> +</div> +<div class="sect1"> +<h2 id="_подробная_информация_о_погружениях_в_журнале">6. Подробная информация о погружениях в журнале</h2> +<div class="sectionbody"> +<div class="sect2"> +<h3 id="_вкладка_strong_информация_strong_для_одиночного_погружения">6.1. Вкладка <strong>Информация</strong> (для одиночного погружения)</h3> +<div class="paragraph"><p>Вкладка <em>Информация</em> предоставляет суммарную информацию по погружению, +выбранному в <strong>Списке погружений</strong>. Здесь отображается такая полезная +информация, как поверхностный интервал перед погружением, максимальная и +средняя глубина дайва, объемный расход газов, расход воздуха на поверхности +(SAC) и единицы кислородного отравления (OTU).</p></div> +<div class="admonitionblock"> +<table><tr> +<td class="icon"> +<img src="images/icons/info.jpg" alt="Замечание" /> +</td> +<td class="content">Вычисление SAC и расхода газов: +<em>Subsurface</em> очень точно вычисляет SAC и расход газов принимая во внимание +несжимаемость газов, что особенно важно при давлении в баллоне свыше 200 бар. +Более подробно об этом описано в <a href="#SAC_CALCULATION">Приложение Ж</a>.</td> +</tr></table> +</div> +</div> +<div class="sect2"> +<h3 id="S_ExtraDataTab">6.2. Вкладка <strong>Дополнительно</strong> (обычно для индивидуального погружения)</h3> +<div class="paragraph"><p>При использовании дайв-компьютера он обычно сообщает дополнительную информацию, которую невозможно +отобразить единообразным образом, принимая во внимание, что эта информация различается для разных +моделей. Обычно эта информация включает в себя настройки компьютера, уровень заряда батареи, +неполетное время или установки градиент-фактора. Когда доступны, эти данные отображаются на вкладке +<strong>Дополнительно</strong>. На рисунке ниже приведены дополнительные данные для погружение на ребризере Poseidon.</p></div> +<div class="imageblock" style="text-align:center;"> +<div class="content"> +<img src="images/ExtraDataTab_f20.jpg" alt="Рисунок: Вкладка Дополнительно" /> +</div> +</div> +</div> +<div class="sect2"> +<h3 id="_вкладка_strong_статистика_strong_для_нескольких_погружений">6.3. Вкладка <strong>Статистика</strong> (для нескольких погружений)</h3> +<div class="paragraph"><p>Вкладка <em>Статистика</em> предоставляет суммарную статистику для нескольких +погружений, предполагая, что вы выбрали несколько дайвов в <strong>Списке погружений</strong> +(используйте клавиши Ctrl и Shift при выборе погружений мышкой). На вкладке +отображается следующая полезная информация: количество выбранных погружений и их +суммарное время, минимальные, максимальные и средние значения длительности, +температуры воздуха и воды, SAC. Тут также отображается глубины самого +глубокого и самого мелкого погружений среди выбранных.</p></div> +</div> +<div class="sect2"> +<h3 id="S_DiveProfile">6.4. Профиль погружения</h3> +<div class="imageblock" style="text-align:center;"> +<div class="content"> +<img src="images/Profile2.jpg" alt="Рисунок: Пример профиля погружения" /> +</div> +</div> +<div class="paragraph"><p>Из всех панелей <em>Subsurface</em>, профиль предоставляет наиболее детальную +информацию о погружении. Слева от профиля находится панель переключателей, +позволяющая выбрать несколько вариантов отображения. Функции этих +переключателей описаны ниже. Главным элементов профиля является график глубины +как функция времени. В дополнение к информации о глубине, график также +показывает скорость спуска/подъема относительно рекомендованной скорости. Эта +информация закодирована разными цветами:</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>Цвет</strong></p></td> +<td align="left" valign="top"><p class="table"><strong>Скорость спуска (м/мин)</strong></p></td> +<td align="left" valign="top"><p class="table"><strong>Скорость подъема (м/мин)</strong></p></td> +</tr> +<tr> +<td align="left" valign="top"><p class="table">Красный</p></td> +<td align="left" valign="top"><p class="table">> 30</p></td> +<td align="left" valign="top"><p class="table">>18</p></td> +</tr> +<tr> +<td align="left" valign="top"><p class="table">Оранжевый</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">Желтый</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">Светло-зеленый</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">Темно-зеленый</p></td> +<td align="left" valign="top"><p class="table">< 1.5</p></td> +<td align="left" valign="top"><p class="table">< 1.5</p></td> +</tr> +</tbody> +</table> +</div> +<div class="paragraph"><p>Профиль также отображает глубины пиков и провалов на графике. Серая линия показывает среднюю +глубину в конкретный момент погружения.</p></div> +<div class="admonitionblock"> +<table><tr> +<td class="icon"> +<img src="images/icons/scale.jpg" alt="Замечание" /> +</td> +<td class="content">В некоторых случаях профиль занимает по ширине не всю панель <strong>Профиль +погружения</strong> Нажмите на переключатель <strong>Альтернативный масштаб</strong>, чтобы более +эффективно использовать пространство экрана.</td> +</tr></table> +</div> +<div class="paragraph"><p><strong>Температура воды</strong> отображается синей линией со указанием значений температуры +в местах значительного изменения.</p></div> +<div class="paragraph"><p>Профиль погружения может отображать графики парциальных давлений O₂, N₂ и He, +расчетный потолок декомпрессии и потолок, посчитанный дайв-компьютером (виден +только для глубоких, долгих или повторных погружений). Графики парциальных +давлений показываются в нижней части профиля, каждый своим цветом для +отдельного газа: кислород - зеленым, азот - черным, гелий - темно-красным.</p></div> +<div class="admonitionblock"> +<table><tr> +<td class="icon"> +<img src="images/icons/O2.jpg" alt="Замечание" /> +</td> +<td class="content">Переключатель отображения графика парциального давления <strong>кислорода</strong>.</td> +</tr></table> +</div> +<div class="admonitionblock"> +<table><tr> +<td class="icon"> +<img src="images/icons/N2.jpg" alt="Замечание" /> +</td> +<td class="content">Переключатель отображения графика парциального давления <strong>азота</strong>.</td> +</tr></table> +</div> +<div class="admonitionblock"> +<table><tr> +<td class="icon"> +<img src="images/icons/He.jpg" alt="Замечание" /> +</td> +<td class="content">Переключатель отображения графика парциального давления <strong>гелия</strong>. Актуально +только для дайверов, использующих Trimix, Helitrox или схожие дыхательные смеси.</td> +</tr></table> +</div> +<div class="paragraph"><p>График <strong>расхода газа</strong> показывает давление в баллоне и его изменение во время +погружения. Этот график принимает во внимание глубину, поэтому даже если вы +вручную ввели начальное и конечное давление в баллоне, линия никогда не будет +прямой. Аналогично графику глубины, график давления визуально предоставляет +информацию о моментальном расходе газа (SAC) при использовании дайв-компьютера +с интегрированным датчиком давления. Однако в этом случае цветовое кодирование +осуществляется безотносительно какой-то абсолютной величины, а относительно +усредненного расхода за время погружения. Таким образом, области красного +или оранжевого цвета указывают на повышенный расход газа, в то время, как +области темно-зеленого цвета говорят о расходе ниже среднего.</p></div> +<div class="admonitionblock"> +<table><tr> +<td class="icon"> +<img src="images/icons/Heartbutton.png" alt="Замечание" /> +</td> +<td class="content">Нажатие на кнопку с изображение ритма сердца показывает информацию о частоте +сердцебиения если дайв-компьютер оборудован датчиком пульса.</td> +</tr></table> +</div> +<div class="paragraph"><p>Вы можете менять масштаб профиля с помощью колеса мыши или соответствующего +жеста на сенсорной панели. По умолчанию <em>Subsurface</em> масштабирует панель +профиля, так чтобы помещалось 30-минутное погружение на 30 метров. Очевидно, +что для фридайверов это не актуально.</p></div> +<div class="imageblock" style="text-align:center;"> +<div class="content"> +<img src="images/MeasuringBar.png" alt="Рисунок: Рулетка" /> +</div> +</div> +<div class="admonitionblock"> +<table><tr> +<td class="icon"> +<img src="images/icons/ruler.jpg" alt="Замечание" /> +</td> +<td class="content">С помощью рулетки вы можете измерять разницу <strong>глубины и времени</strong> между двумя +точками погружения. Измерение производится путем перетаскиванию мышью двух +красных точек. Результаты измерения отображаются в горизонтальной белой +области ниже линии рулетки.</td> +</tr></table> +</div> +<div class="admonitionblock"> +<table><tr> +<td class="icon"> +<img src="images/icons/ShowPhotos.png" alt="Замечание" /> +</td> +<td class="content">Добавленные к погружению фотографии могут быть отображены нажатием на +переключатель <strong>Миниатюры фотографий</strong>. Положение фотографии на профиле +соответствуют времени когда она была сделана. Если этот переключатель +неактивен, фотографии не показываются.</td> +</tr></table> +</div> +<div class="paragraph"><p>Профиле может показывать <strong>потолок</strong>, рассчитанный дайв-компьютером (а +точнее, глубочайшая деко-остановка в данный момент времени). Он отображается +полупрозрачной красной областью. Потолок появляется, когда при прямом подъеме +на поверхность возникает риск возникновения декомпрессионной болезни (ДКБ) и в +этом случае необходимо либо снизить скорость всплытия, либо выполнить +несколько деко-остановок перед всплытием на поверхность. Не все +дайв-компьютеры записывают эту информацию и делают ее доступной для загрузки; +например, ни один из компьютеров Suunto не предоставляет этой информации. +<em>Subsurface</em> независимо рассчитывает потолок и отображает его на профиле +закрашенной областью зеленого цвета. +Из-за разницы в алгоритмах, количества доступных данных и других факторов, +доступных в момент расчета, расчетный потолок <em>Subsurface</em> и дайв-компьютера +могут не совпадать, несмотря даже на то, что <em>градиент-факторы</em> могут +совпадать (см. ниже). +Зачастую <em>Subsurface</em> рассчитывает потолок для бездекомпрессионных погружений, +в то время как компьютер не оставался в бездекомпрессионном режиме во все +время дайва (представлен <span class="green">темно-зеленой</span> областью на профиле в начале +этой главы). Это вызвано тем, что <em>Subsurface</em> рассчитывает деко-обязательства +в каждый момент погружения, в то время, как дайв-компьютеры обычно принимают +во внимание и время всплытия. Во время всплытия происходит рассыщение азота (и +возможно гелия), поэтому даже технически "заработав" потолок на дне, +обязательная деко-остановка не требуется. Это позволяет дайв-компьютерам +рассчитывать большее время на дне.</p></div> +<div class="admonitionblock"> +<table><tr> +<td class="icon"> +<img src="images/icons/cceiling.jpg" alt="Замечание" /> +</td> +<td class="content">Если дайв-компьютер умеет рассчитывать потолок и делает эту информацию +доступной для <em>Subsurface</em> во время импорта, вы можете отображать этот +потолок, нажать на переключатель <strong>Потолок компьютера</strong>.</td> +</tr></table> +</div> +<div class="admonitionblock"> +<table><tr> +<td class="icon"> +<img src="images/icons/ceiling1.jpg" alt="Замечание" /> +</td> +<td class="content">Если переключатель <strong>Расчетный потолок</strong> нажат, потолок, если он существует, +рассчитанный <em>Subsurface</em> будет показан на профиле зеленым цветом (рисунок <strong>А</strong> +ниже). Вы можете далее поменять его отображение следующим образом:</td> +</tr></table> +</div> +<div class="admonitionblock"> +<table><tr> +<td class="icon"> +<img src="images/icons/ceiling2.jpg" alt="Замечание" /> +</td> +<td class="content">Если нажат переключатель <strong>Расчет всех тканей</strong>, показывается потолок для всех +типов тканей согласно модели Бюльмана (рисунок <strong>В</strong> ниже)</td> +</tr></table> +</div> +<div class="admonitionblock"> +<table><tr> +<td class="icon"> +<img src="images/icons/ceiling3.jpg" alt="Замечание" /> +</td> +<td class="content">Если нажат переключатель <strong>3м шаг для расчетного потолка</strong>, потолок отображается +ступеньками с шагом 3 метра.</td> +</tr></table> +</div> +<div class="imageblock" style="text-align:center;"> +<div class="content"> +<img src="images/Ceilings2.jpg" alt="Рисунок: Потолок с 3м шагом" /> +</div> +</div> +<div class="admonitionblock"> +<table><tr> +<td class="icon"> +<img src="images/icons/ShowCylindersButton.jpg" alt="Замечание" /> +</td> +<td class="content">Если выбран этот переключатель, то баллоны, используемые в погружении, отображаются в виде цветной +полосы в нижней части профиля погружения. Кодировка цветов следующая: кислород нарисован +зеленой полосой, азот желтой, а гелий - красной. Рисунок ниже представляет профиль погружения с первой +смесью Trimix (красно-зеленая полоса), с дальнейшим переходом на Nitrox (желто-зеленая полоса) на 23 +минуте. Баллоны с воздухом представлены светло-голубой полосой.</td> +</tr></table> +</div> +<div class="imageblock" style="text-align:center;"> +<div class="content"> +<img src="images/ShowCylinders_f20.jpg" alt="Рисунок: График использования баллонов" /> +</div> +</div> +<div class="admonitionblock"> +<table><tr> +<td class="icon"> +<img src="images/tissues.jpg" alt="Замечание" /> +</td> +<td class="content">Показывает давление инертных газов в тканях относительно внешнего давления (горизонтальная серая +линия). Давление в тканях рассчитывается по алгоритму Бюльмана ZH-L16 и отображается линиями, цвет +которых варьируется от зеленого (самые быстрые ткани) до синего (самые медленные ткани). +Черная линия, нарисованная выше графика внешнего давления, показывает максимальное допустимое +перенасыщение согласно значений градиент-фактора, указанных в настройках. Для дайверов, планирующих +декомпрессионные погружения, эффективное скорость рассыщения достигается при давлении в тканях +большем чем окружающее давление (серая линия), но меньшем чем предельное (черная линия). Это +представление отображает давление в тканях на протяжении всего погружения. Напротив, +<a href="#S_gas_pressure_graph">Гистограмма давления газов</a> в плавающем <strong>Информационном окне</strong> отображает +давление в момент времени, соответствующий положению указателя мыши на оси времени.</td> +</tr></table> +</div> +<div class="imageblock" style="text-align:center;"> +<div class="content"> +<img src="images/tissuesGraph.jpg" alt="Рисунок: График насыщения тканей инертными газами" /> +</div> +</div> +<div class="paragraph"><p>Установки градиент-фактора непосредственно влияют на расчетный потолок и его глубину. Подробнее +см. главу <a href="#S_GradientFactors">Установки градиент-фактора</a>. Текущие установки градиент-фактора +(например, GF 35/75) указываются в верхней части профиля погружения. +<strong>Обратите внимание:</strong> значение градиент-фактора на профиле - это НЕ значение, используемое +дайв-компьютером, а установка, использующаяся самим <em>Subsurface</em> для расчета деко-обязательств. +Более подробно по этой теме можно прочитать во внешних источниках:</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="_контекстное_меню_профиля_погружения">6.5. Контекстное меню профиля погружения</h3> +<div class="paragraph"><p>Доступ к контекстному меню профиля погружения осуществляется нажатием правой кнопки мыши в любом +месте графика. Меню позволяет добавлять закладки и события замены смеси или ручные установки для +CCR-погружений в дополнение к тем, что были импортированы из дайв-компьютера. Маркеры помещаются +на профиле в точках, соответствующих времени на горизонтальной оси в момент нажатия правой кнопкой +мыши. При выборе события замены газа, вы далее должны выбрать смесь из списка доступных, как задано +на вкладке Снаряжение. Добавления события смены установки CCR откроет окно, в котором можно задать +новое значение. Как и в случает <strong>Планировщика</strong>, добавление установки со значением ноль означает, что +дайвер перешел на открытый цикл, а ненулевое значение означает погружение на ребризере закрытого +цикла (CCR). +При щелчке правой кнопкой мыши на уже существующем +маркере, меню будет расширено, позволяя вам удалить маркер и скрыть все +маркеры данного типа. Чтобы восстановить скрытые маркеры, выберите в +контекстном меню пункт <strong>Показывать все события</strong>.</p></div> +</div> +<div class="sect2"> +<h3 id="S_InfoBox">6.6. Информационное окно</h3> +<div class="paragraph"><p>Информационное окно отображает подробную информацию, относящуюся к конкретной +точке профиля погружения (рисунок <strong>В</strong>). Обычно это окно расположено в левой +верхней части панели, но вы можете его перетащить в любое другое место, при +этом позиция будет сохранена и не будет меняться при переключении между +погружениями. Если мышка находится вне панели, информационное окно отображает +только заголовок (рисунок <strong>А</strong>). Положение информационного окно запоминается между последовательными +запусками <em>Subsurface</em>.</p></div> +<div class="imageblock" style="text-align:center;"> +<div class="content"> +<img src="images/InfoBox2.jpg" alt="Рисунок: Информационное окно" /> +</div> +</div> +<div class="paragraph"><p>В момент наведения мышкой на профиль погружения, информационное окно +распахивается и отображает различную информацию, относящуюся к той временной +точке, где находится курсор мыши (рисунок *В). Таким образом, передвигая +курсор мыши по горизонтальной оси времени, вы можете получить информацию о +любом моменте погружения. +В информационном окне представлены следующие данные: время погружения (@), +глубина (Г), давление в баллоне (Д), температура (Т), скорость спуска/подъема +(С), расход воздуха (SAC), парциальное давление кислорода, максимальная +рабочая глубина (MOD), эквивалентная глубина по воздуху (EAD), эквивалентная +наркозная глубина (END), эквивалентная глубина по плотности воздуха (EADD), +декомпрессионные обязательства в данный момент времени (Деко), время до +поверхности (TTS), расчетный потолок наряду с потолком для отдельных тканей по +Бюльману.</p></div> +<div class="paragraph"><p>Вы можете контролировать отображение некоторых из этих значений, +воспользовавшись четырьмя переключателями на левой панели кнопок:</p></div> +<div class="admonitionblock"> +<table><tr> +<td class="icon"> +<img src="images/icons/MOD.jpg" alt="Замечание" /> +</td> +<td class="content">Если этот переключатель нажат, информационное окно показывает <strong>максимальную +рабочую глубину (MOD)</strong> для используемого газа. Значение MOD зависит от +процентного содержания кислорода в смеси. Для воздуха (21% кислорода) это +значение составляет около 57 метров. Погружения ниже MOD чреваты рисками, +связанными с токсичностью кислорода.</td> +</tr></table> +</div> +<div class="admonitionblock"> +<table><tr> +<td class="icon"> +<img src="images/icons/NDL.jpg" alt="Замечание" /> +</td> +<td class="content">Если этот переключатель нажат, информационное окно показывает +<strong>бездекомпрессионный предел (NDL)</strong> или <strong>время до поверхности (TTS)</strong>. NDL +указывает время, которое дайвер может оставаться на текущей глубине, без +возникновения декомпрессионных обязательств (т.е. пока не появится потолок). +Как только NDL превышен и появляются декомпрессионные обязательства, TTS +указывает время до всплытия на поверхность, включая время всплытия и +декомпрессии. TTS рассчитывается исходя и расхода (SAC) текущего газа, даже +если на профиле указаны переходы на другие смеси.Значения TTS, превышающие 2 +часа, не могут быть точно рассчитаны и <em>Subsurface</em> отображает <em>TTS > 2ч</em>.</td> +</tr></table> +</div> +<div class="admonitionblock"> +<table><tr> +<td class="icon"> +<img src="images/icons/SAC.jpg" alt="Замечание" /> +</td> +<td class="content">Если этот переключатель нажат, информационное окно показывает <strong>расход воздуха +на поверхности (SAC)</strong>. SAC - объем дыхания, нормализованный для поверхности. +Значение SAC меньше чем реальный расход газа, потому что на глубине 10м дайвер +потребляет в два раза больше газа, чем на поверхности. Значение SAC не зависит +от глубины и измеряются в литрах/мин или куб.футах/мин.</td> +</tr></table> +</div> +<div class="admonitionblock"> +<table><tr> +<td class="icon"> +<img src="images/icons/EAD.jpg" alt="Замечание" /> +</td> +<td class="content">Если этот переключатель нажат, информационное окно показывает <strong>эквивалентную +глубину по воздуху (EAD)</strong> для погружений на Nitrox и <strong>эквивалентную +наркозную глубину (END)</strong> для Trimix. Эти значения важны для дайверов, +погружающихся на смесях, отличных от воздуха. Значение этих величин зависят от +состава газа. EAD - глубина гипотетического погружения на воздухе, в котором +парциальное значение азота такое же, как и в текущем погружении на Nitrox. +Дайв на Nitrox влечет такие же декомпрессионные обязательства, как и +погружение на воздухе на глубину EAD. END - глубина гипотетического погружения +на воздухе, в котором сумма парциальных давлений наркотических азота и +кислорода такая же, как и в текущем погружении на Trimix. Тримиксный дайвер +может ожидать такого же наркотического эффекта, погружайся он на воздухе на +глубину END.</td> +</tr></table> +</div> +<div class="paragraph"><p>На рисунке <strong>В</strong> выше показано информационное окно практически со всей доступной информацией.</p></div> +<div class="sect3"> +<h4 id="S_gas_pressure_graph">6.6.1. Гистограмма давления газов</h4> +<div class="paragraph"><p>В левой части <strong>Информационного окна</strong> расположена вертикальная гистограмма, отображающая давление +азота (и других инертных газов, например гелия, там, где это применимо), вдыхаемых дайвером <em>в +определенный момент времени</em>, соответствующий положению указателя мыши на оси времени. Рисунок ниже +поясняет, что именно показывает гистограмма:</p></div> +<div class="imageblock" style="text-align:center;"> +<div class="content"> +<img src="images/GasPressureBarGraph.jpg" alt="Рисунок: Гистограмма давления газов" /> +</div> +</div> +<div class="ulist"><ul> +<li> +<p> +Светло-зеленая область означает общий объем газа, а верхняя граница этой области показывает + общее давление газа, вдыхаемого дайвером (измеренное от нижней части гистограммы). Это давление + имеет относительную величину и не показывает абсолютное давление. +</p> +</li> +<li> +<p> +Горизонтальная черная линия ниже светло-зеленой границы указывает уравновешенное давление + инертных газов, вдыхаемых дайвером, обычно азота. В случае Trimix, это значение будет составной + величиной давлений азота и гелия. В нашем примере погружение выполнялось с использованием EAN32, + поэтому эта линия отмечает 68% от общего расстояния от нижней части гистограммы до границы светло- + зеленой области (общее давление газа). +</p> +</li> +<li> +<p> +Темно-зеленая область в нижней части гистограммы отображает давление инертных газов в каждой из + 16 групп тканей согласно алгоритма Бюльмана. "Быстрые" ткани расположены в левой части. +</p> +</li> +<li> +<p> +Верхняя черная линия указывает на градиент-фактор, примененный к глубине в конкретной точке + на <strong>Профиле погружения</strong>. Градиент-фактор интерполируется исходя из значений GFLow и GFHigh, + указанных в вкладке <strong>Профиль</strong> в *Настройках*. +</p> +</li> +<li> +<p> +Нижняя граница красной области на гистограмме отображает вычисленное по алгоритму Бюльмана + M-значение, - давление инертного газа, при котором весьма вероятно формирование пузырьков, + что в свою очередь может привести к декомпрессионной болезни. +</p> +</li> +</ul></div> +<div class="paragraph"><p>Эти пять величин показаны на рисунке выше в левой его части. Как меняется гистограмма на протяжении +погружения, показано в правой части рисунка (погружение с использованием EAN32).</p></div> +<div class="ulist"><ul> +<li> +<p> +Гистограмма <strong>А</strong>. Дайвер перед погружением находится на поверхности. Давление в группах тканей + такое же, как и уравновешенное давление. +</p> +</li> +<li> +<p> +Гистограмма <strong>B</strong>. Дайвер погрузился на глубину 30 метров. Лишь некоторые ткани успели частично + насытиться за время спуска, давление в тканях гораздо ниже уравновешенного давления. +</p> +</li> +<li> +<p> +Гистограмма <strong>C</strong>. Дайвер провел 30 минут на глубине 30 метров. "Быстрые" ткани насытились до + уровня уравновешенного давления (т.е. сравнялись по высоте с черной линий). Более "медленные" + ткани, находящиеся справа, еще только находятся в процессе насыщения. +</p> +</li> +<li> +<p> +Гистограмма <strong>D</strong>. Дайвер поднялся до глубины 4.5 метра. Так как во время подъема давление вдыхаемого + газа значительно упало с 4 бар до 1.45 бар, давление различных групп тканей теперь значительно + превышает эту величину и приближается к значению градиент-фактора (верхняя черная линия). Дальнейший + подъем приведет к превышению значения градиент-фактора (GFHigh) и подвергнет дайвера риску. +</p> +</li> +<li> +<p> +Гистограмма <strong>E</strong>. Дайвер оставался на глубине 4.5 метра в течение 10 минут. Насыщение "быстрых" + тканей снизилось, в то время как насыщение "медленных тканей изменилось ожидаемо мало. Давление + в "быстрых" тканях уже не приближается опасно близко к значению GFHigh и дайвер находится в более + безопасной ситуации нежели чем случае <strong>D</strong>. +</p> +</li> +</ul></div> +</div> +</div> +</div> +</div> +<div class="sect1"> +<h2 id="_ведение_журнала_работа_с_группами_погружений">7. Ведение журнала (работа с группами погружений)</h2> +<div class="sectionbody"> +<div class="sect2"> +<h3 id="_контекстное_меню_списка_погружений">7.1. Контекстное меню списка погружений</h3> +<div class="paragraph"><p>Многие действия <em>Subsurface</em>, связанные с группами погружений, находятся в контекстном меню, +которое вы можете вызвать, нажав правой кнопкой мыши на дайве или группе погружений.</p></div> +<div class="imageblock" style="text-align:center;"> +<div class="content"> +<img src="images/ContextMenu.jpg" alt="Рисунок: Контекстное меню" /> +</div> +</div> +<div class="paragraph"><p>Это меню используется во многих сценариях, которые описаны ниже:</p></div> +<div class="sect3"> +<h4 id="_выбор_колонок_списка_погружений">7.1.1. Выбор колонок списка погружений</h4> +<div class="imageblock" style="text-align:left;"> +<div class="content"> +<img src="images/DiveListOptions.jpg" alt="Пример: Возможные колонки списка погружений" /> +</div> +</div> +<div class="paragraph"><p>По умолчанию в таблице <strong>списка погружений</strong> показывается следующая информация: +номер, дата, рейтинг, глубина, длительность и местоположение. Вы можете +изменить набор колонок, нажав правой кнопкой мыши на заголовке таблицы. Ниже +приведен пример контекстного меню при нажатии правой кнопкой на заголовке +<em>Дата</em>. Поставьте или удалите галочки чтобы показать или скрыть поля. <em>Subsurface</em> +запоминает ваши предпочтения, так что при следующим запуске набор полей останется прежним.</p></div> +</div> +</div> +<div class="sect2"> +<h3 id="S_Renumber">7.2. Перенумерация погружений</h3> +<div class="paragraph"><p>Погружения обычно пронумерованы последовательно от более старых к более новым. +Однако эта нумерация может быть нарушена. Например, при добавлении давних +погружений, нумерация не будет последовательной, потому что существуют более +поздние дайвы, нежели только что добавленные ранние погружения. В связи с этим +вам может понадобиться перенумеровать погружения, для чего в главном меню +выберите <em>Журнал → Перенумеровать</em>. Вам будет предоставлена возможность +указать начальный номер, после чего погружения будут перенумерованы в +соответствии с хронологическим порядком.</p></div> +<div class="paragraph"><p>Вы также можете перенумеровать только избранные погружения. Для это выберите те, для которых +необходимо изменить нумерацию. Щелкните правой кнопкой мыши на выделенных погружениях и используйте +появившееся контекстное меню, чтобы выполнить перенумерацию. В появившемся окне вам будет необходимо +указать начальный номер.</p></div> +</div> +<div class="sect2"> +<h3 id="S_Group">7.3. Группировка погружений и работа с поездками</h3> +<div class="paragraph"><p>Если вы регулярно ныряете, журнал может очень быстро распухнуть. <em>Subsurface</em> +позволяет группировать погружения в <em>поездки</em>. Это выполняется для погружений, +у которых разрыв по времени не превышает двух дней. При этом для всех таких +дайвов создается один заголовок в журнале. Ниже представлен несгруппированный +список погружений (рисунок <strong>А</strong> слева) и тот же список, +сгруппированный в пять поездок (рисунок <strong>В</strong> справа):</p></div> +<div class="imageblock" style="text-align:center;"> +<div class="content"> +<img src="images/Group2.jpg" alt="Рисунок: Группировка погружений" /> +</div> +</div> +<div class="paragraph"><p>Группировка в поездки обеспечивает более быстрый доступ к отдельному +погружения без необходимости просматривать длинный список. Для группировки +погружений в главном меню выберите <em>Журнал → Авто-группировка</em>. Теперь список +показывает только заголовки поездок.</p></div> +<div class="sect3"> +<h4 id="_редактирование_поездки">7.3.1. Редактирование поездки</h4> +<div class="paragraph"><p>Обычно в списке погружения для поездки показывается только ее название. Чтобы +расширить эту информацию, выберите поездку в списке. после чего перейдите на +вкладку <strong>Поездка</strong> в информационной панели. Здесь вы можете добавить информацию, +касающуюся поездки в целом: дату и время, местоположение, название дайв-центра, +погодные условия и т.п. Сохраните данные, нажав на кнопку <strong>Сохранить</strong> (на +голубом фоне в верхней части панели).</p></div> +</div> +<div class="sect3"> +<h4 id="_просмотр_погружений_из_поездки">7.3.2. Просмотр погружений из поездки</h4> +<div class="paragraph"><p>Чтобы получить доступ к индивидуальным погружения в группе, распахните поездку +нажатием кнопки мыши на значок слева от названия поездки.</p></div> +</div> +<div class="sect3"> +<h4 id="_сворачивание_разворачивание_поездок">7.3.3. Сворачивание/разворачивание поездок</h4> +<div class="paragraph"><p>При щелчке правой кнопкой мыши на поездке, контекстное меню предлагает +несколько вариантов просмотра поездок: свернуть все, развернуть все, свернуть +остальные кроме выбранной.</p></div> +</div> +<div class="sect3"> +<h4 id="_объединение_погружений_из_нескольких_поездок_в_одну">7.3.4. Объединение погружений из нескольких поездок в одну</h4> +<div class="paragraph"><p>При щелчке правой кнопкой мыши на поездке, контекстное меню предлагает два +варианта объединения поездок: объединить с поездкой выше или с поездкой ниже по +списку.</p></div> +</div> +<div class="sect3"> +<h4 id="_разбиение_одной_поездки_на_несколько">7.3.5. Разбиение одной поездки на несколько</h4> +<div class="paragraph"><p>Если, к примеру, поездка включает десять погружений, вы можете разбить ее на две +(поездка 1: первые четыре дайва, поездка 2: оставшиеся 6 погружений), выделив первые +четыре погружения в поездке и вызвав контекстное меню правой кнопкой мыши. В меню +выберите пункт <strong>Создать поездку выше</strong>. Выбранные четыре погружения будут +объединены в отдельную поездку. Рисунок ниже слева (А) иллюстрирует выбор погружений и +контекстное меню, рисунок справа (Б) - погружения после разбиения:</p></div> +<div class="imageblock" style="text-align:center;"> +<div class="content"> +<img src="images/SplitDive3a.jpg" alt="Рисунок: Разбиение поездки на две" /> +</div> +</div> +</div> +</div> +<div class="sect2"> +<h3 id="_работа_с_индивидуальными_погружениями">7.4. Работа с индивидуальными погружениями</h3> +<div class="sect3"> +<h4 id="_удаление_погружения_из_журнала">7.4.1. Удаление погружения из журнала</h4> +<div class="paragraph"><p>Вы можете навсегда удалить погружение из журнала, вызвав контекстное меню +этого дайва и выбрав пункт <strong>Удалить</strong>. Вам может потребоваться это для удаления +неверных погружений (калибровка дайв-компьютера, подбор грузов и т.п.)</p></div> +</div> +<div class="sect3"> +<h4 id="_удаление_погружения_из_поездки">7.4.2. Удаление погружения из поездки</h4> +<div class="paragraph"><p>Чтобы удалить погружение из поездки, вызовите контекстное меню погружения +щелчком правой кнопки мыши и выберите пункт <strong>Удалить из поездки</strong>. В списке это +погружение окажется над поездкой из которой оно было удалено.</p></div> +</div> +<div class="sect3"> +<h4 id="_добавление_погружения_к_существующей_поездке">7.4.3. Добавление погружения к существующей поездке</h4> +<div class="paragraph"><p>Несгруппированные погружения могут быть добавлены к уже существующим поездкам. +В контекстном меню погружения(-й) выберите пункт <strong>Добавить к поездке +сверху/снизу</strong>.</p></div> +</div> +<div class="sect3"> +<h4 id="_сдвиг_времени_начала_погружения">7.4.4. Сдвиг времени начала погружения</h4> +<div class="paragraph"><p>Иногда вам может понадобиться изменить время начала погружения по причине +разницы во времени между часовыми поясами или неверных установок часов +дайв-компьютера. Для этого выделите одно или несколько погружений и в +контекстном меню выберите пункт <strong>Сдвиг времени</strong>. В диалоговом окне вам +необходимо указать величину сдвига в часах и минутах и направление.</p></div> +</div> +<div class="sect3"> +<h4 id="_объединение_нескольких_погружений_в_одно">7.4.5. Объединение нескольких погружений в одно</h4> +<div class="paragraph"><p>Бывают ситуации, когда вы вынуждены прервать дайв и всплыть на поверхность на +короткое время. Дайв-компьютер в этом случае может зарегистрировать это как +два разных погружения. Вы можете объединить такие дайвы, выделив их и выбрав в +контекстном меню пункт <strong>Объединить выбранные</strong>. После этого вам вероятнее все +придется отредактировать данные объединенного погружения. Ниже приведен пример +профиля такого объединенного погружения?</p></div> +<div class="imageblock" style="text-align:center;"> +<div class="content"> +<img src="images/MergedDive.png" alt="Рисунок: Объединенное погружение" /> +</div> +</div> +</div> +<div class="sect3"> +<h4 id="_отмена_манипуляций_с_погружением">7.4.6. Отмена манипуляций с погружением</h4> +<div class="paragraph"><p>Критичные действия с погружениями или поездками, описанные выше, могут быть отменены либо +выполнены повторно. Эти действия включают: <em>удаление погружений</em>, <em>объединение погружений</em> и +<em>сдвиг времени погружения</em>. Для отмены или повторного выполнения операции выберите в <strong>Главном меню</strong> +пункт <strong>Редактировать</strong> и в нем соответствующее действие.</p></div> +</div> +</div> +<div class="sect2"> +<h3 id="S_Filter">7.5. Фильтрация списка погружений</h3> +<div class="paragraph"><p>Вы можете отфильтровать погружения в списке, указав те или иные атрибуты дайва (метки, напарник, +место погружения, костюм). Например, можно выбрать все глубокие погружения в определенном месте, +либо пещерные дайвы с вашим другом.</p></div> +<div class="paragraph"><p>Чтобы вызвать фильтр, выберите в главном меню <em>Журнал → Фильтр погружений</em>. Вам будет представлена +<em>Панель фильтров</em>, расположенная в верхней части окна <em>Subsurface</em>. В правой части этой панели +находятся три кнопки, которые позволяют очистить фильтры, спрятать панель или вовсе закрыть ее (при +этом фильтры очищаются).</p></div> +<div class="imageblock" style="text-align:center;"> +<div class="content"> +<img src="images/Filterpanel.jpg" alt="Рисунок: Панель фильтров" /> +</div> +</div> +<div class="paragraph"><p>Для фильтрации списка погружений используются четыре критерия: метки, люди (партнеры и инструктор), +места погружений и костюм. Эти критерии представлены в виде списка значений с галочками. Помимо этого, +над каждым списком находится поле вспомогательного фильтра, которое позволяет быстро найти значения +в списке.</p></div> +<div class="paragraph"><p>Эти четыре фильтра объединены логическим оператором <em>И</em>, однако значения в отдельно взятом фильтре +объединены логическим оператором <em>ИЛИ</em>. Например, вы можете отфильтровать погружения следующим +образом: <em>пещерное</em> ИЛИ <em>рэк</em>, где партнером был Василий.</p></div> +</div> +</div> +</div> +<div class="sect1"> +<h2 id="S_ExportLog">8. Экспорт всего или части журнала</h2> +<div class="sectionbody"> +<div class="paragraph"><p>Существует два варианта экспорта погружений из <em>Subsurface</em>:</p></div> +<div class="ulist"><ul> +<li> +<p> +Экспорт информации о погружении в <em>Facebook</em> +</p> +</li> +<li> +<p> +<a href="#S_Export_other">Экспорт данных погружения в другие форматы</a> +</p> +</li> +</ul></div> +<div class="sect2"> +<h3 id="S_facebook">8.1. Экспорт информации о погружении в <em>Facebook</em></h3> +<div class="paragraph"><p>Экспорт в <em>Facebook</em> отличается от всех других видов экспорта, поскольку он требует подключения +учетной записи, что в свою очередь требует от вас логин и пароль <em>Facebook</em>. Для авторизации +необходимо в главном меню выбрать <em>Файл → Настройки</em> и там выбрать вкладку <em>Facebook</em>, на которой +вам будет представлена форма авторизации (см. рисунок <strong>А</strong> слева внизу). Авторизуйтесь своими логином +и паролем, после чего экран должен выглядеть как показано на рисунке <strong>В</strong>. При необходимости вы +можете отключить <em>Subsurface</em> от <em>Facebook</em>, нажав на соответствующую кнопку.</p></div> +<div class="imageblock" style="text-align:center;"> +<div class="content"> +<img src="images/facebook1_f20.jpg" alt="Рисунок: Авторизация Facebook" /> +</div> +</div> +<div class="paragraph"><p>После того как соединение с <em>Facebook</em> установлено, публикация профиля погружения в вашей Хронике не +составит проблем. Выберите погружение в списке и убедитесь в том, что именно этот дайв должен быть +опубликован. Нажмите кнопку с логотипом <em>Facebook</em>, расположенную в <strong>Информационной панели</strong> справа +от поля <em>Примечания</em> (см. рисунок <strong>А</strong> ниже). По нажатию на эту кнопку вам будет представлено окно, в +котором вы можете выбрать какую дополнительную информацию опубликовать вместе с профилем погружения +(рисунок <strong>В</strong>). Обязательным является только поле <em>Альбом</em>. Кроме указания стандартных параметров +погружения, вы можете вручную отредактировать сопроводительный текст. Для отправки профиля +погружения в вашу Хронику <em>Facebook</em> нажмите кнопку <em>ОК</em>. Спустя короткое время вы должны получить +подтверждение, что запись опубликована.</p></div> +<div class="paragraph"><p>Созданный альбом и запись в хронике по умолчанию будут доступны только вам. Для того, чтобы ваши +друзья смогли увидеть эти записи, вам необходимо изменить настройки безопасности приложений, +войдя в <em>Facebook</em> с помощью обычного броузера или приложения <em>Facebook</em>. Возможно это и является +некоторым неудобством, но разработчики придерживаются мнения, что такой дополнительный шаг позволит +избежать нежелательных записей в вашей Хронике.</p></div> +<div class="imageblock" style="text-align:center;"> +<div class="content"> +<img src="images/facebook2_f20.jpg" alt="Рисунок: Авторизация в Facebook" /> +</div> +</div> +<div class="paragraph"><p>Разорвать соединение с <em>Facebook</em> можно из <strong>Настроек</strong> приложения, либо просто закрыв <em>Subsurface</em>.</p></div> +</div> +<div class="sect2"> +<h3 id="S_Export_other">8.2. Экспорт данных погружения в другие форматы</h3> +<div class="paragraph"><p>Функция экспорта доступна через главное меню <em>Файл → Экспорт</em>. Диалог +экспорта всегда предлагает два варианта: все погружения или только те, что выбраны в +<strong>Списке погружений</strong>. Выберите соответствующий пункт (см. рисунок ниже):</p></div> +<div class="imageblock" style="text-align:center;"> +<div class="content"> +<img src="images/Export_f20.jpg" alt="Рисунок: Диалог экспорта" /> +</div> +</div> +<div class="paragraph"><p>Журнал или его часть могут быть сохранены в нескольких форматах:</p></div> +<div class="ulist"><ul> +<li> +<p> +Внутренний формат <em>Subsurface</em> XML +</p> +</li> +<li> +<p> +Универсальный формат данных погружений (<em>UDDF</em>). Более полную информацию +можно найти на сайте <em>http://uddf.org</em>. UDDF используется для обмена данными +между дайв-компьютерами и программами. +</p> +</li> +<li> +<p> +<em>Divelogs.de</em>, интернет-сервис для ведения журнала погружений. Вам +необходимо зарегистрироваться на сайте и получить логин и пароль, чтобы +воспользоваться этим сервисом. +</p> +</li> +<li> +<p> +<em>DiveShare</em>, также интернет-сервис для хранения и обмена информацией о рекреационными + погружениях. Для выгрузки данных в этот сервис нужен идентификатор пользователя, поэтому + вам придется зарегистрироваться на сайте <em>http://scubadiveshare.com</em>. +</p> +</li> +<li> +<p> +<em>Погружение в формате _CSV</em>, который включает только наиболее важную информацию о +погружении: номер, дату, время, длительность, глубину, температуру и давление, т.е. большую +часть того, что обычно записывается в бумажном журнале. +</p> +</li> +<li> +<p> +<em>Профиль а формате _CSV</em>, который включает в себя множество информации, включая профиль +глубины, показатели температуры и давления для каждого погружения. +</p> +</li> +<li> +<p> +<em>HTML</em> формат. Журнал хранится в HTML-файлах, которые можно просмотреть с +помощью интернет-браузера. Поддерживаются большинство современных браузеров, но +обязательно должна быть включена поддержка Javascript. Предполагается, что вы +не будете редактировать эти файлы. HTML-журнал содержит максимум информации и +позволяет выполнять поиск в журнале. Этот вариант экспорта доступен на вкладке +HTML (см. рисунок <strong>В</strong> выше). Вы можете выгрузить эти данные на смартфон или планшет и использовать +как переносимый журнал для подтверждения своей квалификации в дайв-центре, если они захотят +посмотреть вашу историю погружений. +</p> +</li> +<li> +<p> +<em>Карта мира</em>. Это HTML файл, погружения отображаются на карте мира с +минимальной информацией о погружении. Этот формат нельзя отредактировать. +</p> +</li> +</ul></div> +<div class="imageblock" style="text-align:center;"> +<div class="content"> +<img src="images/mapview_f20.jpg" alt="Рисунок: Погружения на карте мира" /> +</div> +</div> +<div class="ulist"><ul> +<li> +<p> +<em>Глубины фото</em>. Создает текстовый файл, в котором содержатся имена файлов всех фотографий, +прикрепленных к погружениям вместе с указанием глубины, на которой эти фотографии были сделаны. +</p> +</li> +<li> +<p> +<em>Общие настройки</em> на вкладке HTML позволяет указать: +</p> +<div class="ulist"><ul> +<li> +<p> +Нумерация Subsurface: если выбран этот параметр, то номера погружений будут + выбираться из <em>Subsurface</em>, иначе дайвы будут пронумерованы начиная с 1. +</p> +</li> +<li> +<p> +Статистика за год: если выбран этот параметр, в экспорт будет также включена статистика + погружений по годам. +</p> +</li> +<li> +<p> +Только список: будет экспортирован только список погружений, а + дополнительная информация не будет доступна. +</p> +</li> +</ul></div> +</li> +<li> +<p> +Группа <em>Настройки стиля</em> позволяют настроить внешнее оформление экспорта (шрифты и тему). +</p> +</li> +</ul></div> +<div class="paragraph"><p>Экспорт в другие форматы можно выполнить с помощью сторонних сервисов, таких +как <em>www.divelogs.de</em>.</p></div> +</div> +</div> +</div> +<div class="sect1"> +<h2 id="S_Cloud_access">9. Хранение журнала <em>Subsurface</em> в облаке</h2> +<div class="sectionbody"> +<div class="paragraph"><p>Журнал погружений важен для каждого дайвера. Вы ведете учет погружений не +только для своего удовольствия, он необходим для дальнейшего прохождения +курсов, а иногда в некоторых дайв-центрах. Поэтому вы должны обеспечить +сохранность журнала. На случай выхода из строя жесткого диска вашего +компьютера, кражи и утери оборудования, хранение в облаке - первое что приходит +в голову. Еще один плюс - вы можете получить доступ к журналу в любой точке +мира и вам не нужно иметь его с собой. Именно поэтому сервисы типа +<em>divelogs.de</em> и <em>Diving Log</em> предлагают хранение журнала в Интернете.</p></div> +<div class="paragraph"><p><em>Subsurface</em> предлашает встроенную поддержку облачного хранилища для всех своих +пользователей. Сохранение и загрузка журнала погружений в облаке ничем не +отличается от работы с жестким диском. От вас требуется только регистрация. +Для использования облачного хранилища <em>Subsurface</em> необходимо выполнить +следующие шаги:</p></div> +<div class="sect2"> +<h3 id="_создание_учетной_записи_в_облаке">9.1. Создание учетной записи в облаке</h3> +<div class="ulist"><ul> +<li> +<p> +Перейдите в настройки сети (в <strong>Главном меню</strong> выберите <em>Файл</em> → <em>Настройки</em> + → <em>Сеть</em>). +</p> +</li> +<li> +<p> +В секции <em>Облачное хранилище Subsurface</em> укажите свой адрес электронной + почты, который вы желаете использовать для регистрации. +</p> +</li> +<li> +<p> +Укажите надежный пароль, который будет защищать ваш журнал в облаке. +</p> +</li> +<li> +<p> +Нажмите кнопку <em>Применить</em>, чтобы отправить адрес почты и пароль на + удаленный сервер в облаке. В ответ сервер пришлет вам PIN-код на указанный + адрес (это <strong>единственный</strong> случай, когда <em>Subsurface</em> использует ваш адрес). + Теперь в настройках сети появится поле PIN, которое ранее не было видно. +</p> +</li> +<li> +<p> +ВВедите PIN-код в соответствующее текстовое поле (оно доступно только тогда, + когда сервер ожидает подтверждения адреса электронной почты) +</p> +</li> +<li> +<p> +Нажмите снова кнопку <em>Применить</em>. Ваша учетная запись будет отмечена + как проверенная; облачное хранилище готово к работе. +</p> +</li> +</ul></div> +</div> +<div class="sect2"> +<h3 id="_использование_облачного_хранилища">9.2. Использование облачного хранилища</h3> +<div class="ulist"><ul> +<li> +<p> +После успешной инициализации хранилища, в меню <em>Файл</em> появятся два новых пункта: + <em>Открыть облачное хранилище</em> и <em>Сохранить в облаке</em>. Эти действия позволяют + соответственно загрузить и сохранить журнал в облаке. +</p> +</li> +<li> +<p> +в настройках приложения (вкладка <strong>Общие</strong>) вы можете выбрать опцию хранить журнал погружений +по умолчанию в облаке. В этом случае <em>Subsurface</em> будет загружать журнал из облака при запуске +и сохранять при выходе из программы. +</p> +</li> +<li> +<p> +<em>Subsurface</em> хранит локальную копию облачного хранилища на жестком диске и позволяет вам +работать с журналом даже при отсутствии Интернета. При подключении к Интернет ваши локальные +изменения буду синхронизированы в облако. +</p> +</li> +</ul></div> +</div> +<div class="sect2"> +<h3 id="S_Cloud_storage">9.3. Доступ из веб-браузера к облачному хранилищу <em>Subsurface</em></h3> +<div class="paragraph"><p>Одним из преимуществ облачного хранилища является то, что вы можете получить доступ к данным +вашего журнала погружений, используя обычный веб-браузер. Откройте ссылку +<a href="https://cloud.subsurface-divelog.org"><em>https://cloud.subsurface-divelog.org</em></a>, введите свой +адрес электронной почты и пароль, указанные при регистрации, и вы сможете просматривать журнал в +HTML-формате (данные погружений последней синхронизации в облачное хранилище <em>Subsurface</em>). +Информация о погружениях отображает только реальные данные из журнала, вычисляемые значения +НЕ отображаются (давление в баллонах, деко-потолок, парциальные давления O<sub>2</sub>/He/N<sub>2</sub> и т.п.)</p></div> +</div> +<div class="sect2"> +<h3 id="_прочие_облачные_сервисы">9.4. Прочие облачные сервисы</h3> +<div class="paragraph"><p>Если вы предпочитаете не использовать встроенное облачное хранилище +<em>Subsurface</em> (и вам не нужен доступ к журналу из веб-браузера), то можно просто +хранить журнал в облаке, используя другие облачные хранилища в Интернет.</p></div> +<div class="paragraph"><p>Например, <a href="http://www.dropbox.com/"><em>Dropbox</em></a> предлагает приложение, которое +позволяет видеть файлы на серверах Dropbox как локальные папки на вашем +домашнем компьютере.</p></div> +<div class="imageblock" style="text-align:center;"> +<div class="content"> +<img src="images/Cloud.jpg" alt="Рисунок: Папка Dropbox" /> +</div> +</div> +<div class="paragraph"><p>Программа <em>Dropbox</em> позволяет получить копию облачного интернет-хранилища на +вашем компьютере. Когда компьютер подключен к Интернет, ваша локальная копия +автоматически синхронизируется с облаком. При работе <em>Subsurface</em> операции +открытия и сохранения выполняются с локальной копией и доступ в Интернет не +нужен. Если локальная копия была изменена, например, вы добавили погружения, +файлы в облаке будут автоматически обновлены как только появится соединение с +Интернет.</p></div> +<div class="paragraph"><p>Таким образом, журнал будет доступен из любой точки с доступом в +Интернет. В настоящий момент эту услуга бесплатна. Программное обеспечение +для Windows, Mac и Linux может быть загружено со +<a href="http://www.dropbox.com/install"><em>страницы установки Dropbox</em></a>. +Аналогично вы можете использовать <em>Dropbox</em> для хранения резервной копии +журнала. Для этого в главном меню выберите <em>Файл → Сохранить как</em> и сохраните +копию журнала в папку <em>Dropbox</em>. Чтобы открыть копию журнала, хранящегося в +облаке, выберите в главном меню <em>Файл → Открыть журнал</em>, перейдите в папку +<em>Dropbox</em> и укажите необходимый файл.</p></div> +<div class="paragraph"><p>Существуют и другие платные и бесплатные схожие сервисы (Google, Amazon), +которые вы можете использовать для хранения журнала в облаке.</p></div> +</div> +</div> +</div> +<div class="sect1"> +<h2 id="S_PrintDivelog">10. Печать журнала погружений</h2> +<div class="sectionbody"> +<div class="paragraph"><p><em>Subsurface</em> предоставляет простой интерфейс для печати всего журнала или только выбранных погружений, включая профиль и сопутствующую информацию. +Поставляемые или собственные шаблоны определяют как данные погружения расположены на странице.</p></div> +<div class="paragraph"><p>Перед печатью вам нужно определиться с двумя вещами:</p></div> +<div class="ulist"><ul> +<li> +<p> +Нужно ли печатать весь журнал или только его часть? Если нужно распечатать +только часть погружений, выделите эти дайвы с списке. +</p> +</li> +<li> +<p> +Для каких газов нужно печатать графики парциального давления? Выберите +соответствующие переключатели на панели слева от профиля. +</p> +</li> +</ul></div> +<div class="paragraph"><p>Теперь укажите параметры печати. Для этого в главном меню выберите <em>Файл → Print</em>. +Вам будет представлено диалоговое окно (см. рисунок <strong>А</strong> ниже). Вам необходимо определиться с тремя параметрами:</p></div> +<div class="imageblock" style="text-align:center;"> +<div class="content"> +<img src="images/Print1_f22.jpg" alt="Рисунок: Диалог печати" /> +</div> +</div> +<div class="olist arabic"><ol class="arabic"> +<li> +<p> +В секции <em>Варианты печати</em> выберите один из пунктов: +</p> +<div class="ulist"><ul> +<li> +<p> +<em>Печать погружений</em>: печать погружений из списка с профилем и другой информацией. +</p> +</li> +<li> +<p> +<em>Печать статистики</em>: печать статистики погружений по годам и месяцам. +</p> +</li> +</ul></div> +</li> +<li> +<p> +В секции <em>Параметры печати</em> выберите: +</p> +<div class="ulist"><ul> +<li> +<p> +Печать только выбранных погружений из списка. Если этот параметр не выбран, + будут распечатаны все погружения из журнала. +</p> +</li> +<li> +<p> +Параметр <em>Цветная печать</em> указывает будет ли печать цветной или монохромной. +</p> +</li> +</ul></div> +</li> +<li> +<p> +В секции <em>Шаблон</em> выберите вариант расположения информации на странице. В штатной поставке +вам предлагается несколько шаблонов (см. Рисунок В выше). +</p> +<div class="ulist"><ul> +<li> +<p> +<em>Table</em>: Печать сводной таблицы погружений (картинка ниже). +</p> +</li> +</ul></div> +</li> +</ol></div> +<div class="imageblock" style="text-align:center;"> +<div class="content"> +<img src="images/Print_summarylist_f22.jpg" alt="Рисунок: Печать сводной таблицы" /> +</div> +</div> +<div class="ulist"><ul> +<li> +<p> +<em>Flow layout</em>: Печать данных погружений без профилей: +</p> +</li> +</ul></div> +<div class="imageblock" style="text-align:center;"> +<div class="content"> +<img src="images/Print_flow_layout_f22.jpg" alt="Рисунок: Печать погружений без профиля" /> +</div> +</div> +<div class="ulist"><ul> +<li> +<p> +<em>One Dive</em>: Печать одного погружения на странице вместе с профилем: +</p> +</li> +</ul></div> +<div class="imageblock" style="text-align:center;"> +<div class="content"> +<img src="images/print2_f22.jpg" alt="Рисунок: Печать одно погружение на странице" /> +</div> +</div> +<div class="ulist"><ul> +<li> +<p> +<em>Two Dives</em>: Печать двух погружений на странице вместе с профилями +</p> +</li> +<li> +<p> +<em>Six Dives</em>: Печать шести погружений на странице вместе с профилями +</p> +</li> +</ul></div> +<div class="paragraph"><p>Вы можете предварительно оценить результат печати, нажав на кнопку <em>Просмотр</em>. +При необходимости поменяйте параметры печати, чтобы добиться желаемого +результата.</p></div> +<div class="paragraph"><p>Нажатие на кнопку <em>Печать</em> вызовет стандартный для вашей операционной системы диалог печати, +в котором вы можете выбрать принтер и установить параметры для него:</p></div> +<div class="imageblock" style="text-align:center;"> +<div class="content"> +<img src="images/Print_print_f22.jpg" alt="Рисунок: Системный диалог печати" /> +</div> +</div> +<div class="paragraph"><p>Установите требуемое разрешение печати и другие параметры и нажмите кнопку <em>Печать</em>. На картинке +ниже показан пример одного из вариантов печати:</p></div> +<div class="imageblock" style="text-align:center;"> +<div class="content"> +<img src="images/Printpreview.jpg" alt="Рисунок: Предварительный просмотр результа печати" /> +</div> +</div> +<div class="sect2"> +<h3 id="_создание_собственных_шаблонов_печати">10.1. Создание собственных шаблонов печати</h3> +<div class="paragraph"><p>Собственные шаблоны позволяют вам максимально гибко настроить расположение данных погружения на странице. <em>Subsurface</em> использует HTML для разметки +шаблонов. С помощью соответствующих кнопок, расположенных под списком шаблонов, вы можете редактировать, удалять, импортировать и экспортировать шаблоны. В +<a href="#S_APPENDIX_E">ПРИЛОЖЕНИИ Д</a> вы сможете найти информацию о том, как создавать и редактировать шаблоны.</p></div> +</div> +</div> +</div> +<div class="sect1"> +<h2 id="S_Configure">11. Конфигурация дайв-компьютера</h2> +<div class="sectionbody"> +<div class="paragraph"><p><em>Subsurface</em> предоставляет возможность конфигурации дайв-компьютеров. В настоящий момент поддерживаются +компьютеры производства Heinrichs-Weikamp (OSTC 2 и OSTC 3) и семейство Suunto Vyper (Stinger, Mosquito, +D3, Vyper, Vytec, Cobra, Gekko И Zoop). Множество параметров компьютера может быть считано и изменено. +Первым шагом вы должны убедиться что установлены все необходимые драйверы оборудования и что вам известно +имя устройства. Внимательно ознакомьтесь с информацией в <a href="#APPENDIX_A">ПРИЛОЖЕНИИ А</a>.</p></div> +<div class="paragraph"><p>После того, как дайв-компьютер подключен, выберите <em>Файл → Настройка дайв-компьютера</em> в главном меню. +Укажите имя устройства в текстовом поле в верхней части окна, и выберите соответствующую модель +дайв-компьютера в списке слева (см. рисунок ниже).</p></div> +<div class="imageblock" style="text-align:center;"> +<div class="content"> +<img src="images/Configure_dc_f20.jpg" alt="Рисунок: Конфигурация дайв-компьютера" /> +</div> +</div> +<div class="paragraph"><p>Вы можете выполнить следующие действия, используя соответствующие кнопки:</p></div> +<div class="ulist"><ul> +<li> +<p> +<strong>Загрузить настройки</strong>. Загружает существующие параметры дайв-компьютера в <em>Subsurface</em>. Загруженные + параметры отображаются на конфигурационной панели. +</p> +</li> +<li> +<p> +<strong>Сохранить в устройстве</strong>. Сохраняет измененные параметры в дайв-компьютер. +</p> +</li> +<li> +<p> +<strong>Резервная копия</strong>. Сохраняет резервную копию настроек. <em>Subsurface</em> запросит директорию и имя + файла. +</p> +</li> +<li> +<p> +<strong>Восстановить</strong>. Загружает настройки для дайв-компьютера из ранее сделанной резервной копии. +</p> +</li> +<li> +<p> +<strong>Обновить прошивку</strong>. Если доступна новая версия прошивки, она будет загружена в дайв-компьютер. +</p> +</li> +</ul></div> +</div> +</div> +<div class="sect1"> +<h2 id="S_Preferences">12. Настройки пользователя <em>Subsurface</em></h2> +<div class="sectionbody"> +<div class="paragraph"><p>Вы можете настроить <em>Subsurface</em> для своих нужд, используя пункт главного меню +<em>Файл → Настройки</em>. Настройки программы разделены на семь групп: <strong>Общие</strong>. +<strong>Единицы</strong>, <strong>Профиль</strong>, <strong>Язык</strong> и <strong>Сеть</strong>, <strong>Facebook</strong> и <strong>Геопривязка</strong>. Выберите +соответствующий раздел в левой части, внесите необходимые изменения ик нажмите +кнопку <strong>Применить</strong>, чтобы сохранить настройки. Чтобы закрыть диалог настроек, +нажмите кнопку <strong>ОК</strong>. Вы также можете закрыть окно настроек без сохранения.</p></div> +<div class="sect2"> +<h3 id="_общие">12.1. Общие</h3> +<div class="paragraph"><p>В этой группе доступны следующие настройки:</p></div> +<div class="imageblock" style="text-align:center;"> +<div class="content"> +<img src="images/Pref1_f20.jpg" alt="Рисунок: Общие настройки" /> +</div> +</div> +<div class="ulist"><ul> +<li> +<p> +<strong>Списки и таблицы</strong>: тут вы можете указать шрифт и его размер для списка + погружений. Уменьшите размер шрифта, чтобы в списке помещалось больше дайвов. +</p> +</li> +<li> +<p> +<strong>Погружения</strong>: укажите папку и имя файла с расширением <em>.xml</em> или <em>.ssrf</em>. При запуске + <em>Subsurface</em> будет автоматически открывать этот журнал. Вам предоставляется три варианта: +</p> +<div class="ulist"><ul> +<li> +<p> +<em>Отсутствует</em>: <em>Subsurface</em> автоматически не загружает журнал при запуске +</p> +</li> +<li> +<p> +<em>Локальный файл</em>: Автоматически загружать журнал из локального файла при запуске. +</p> +</li> +<li> +<p> +<em>Файл в облаке</em>: При старте журнал загружается из облачного хранилища (вам нужно настроить + доступ на вкладке <strong>Сеть</strong>, это описано ниже). +</p> +</li> +</ul></div> +</li> +<li> +<p> +<strong>Показывать ошибочные</strong>: Некоторые погружения могут быть помечены как + ошибочные, например погружения в бассейне, но при этом вы не хотите удалять + их из журнала. Этот параметр позволяет убрать такие дайва и списка. +</p> +</li> +<li> +<p> +<strong>Баллон по умолчанию</strong>: укажите баллон, который будет использоваться по + умолчанию на вкладке <strong>Снаряжение</strong>. +</p> +</li> +<li> +<p> +<strong>Анимация</strong>: скорость анимации профиля при переключении между + погружениями. Чем меньше значение, тем быстрее скорость. Значение 0 + полностью отключает анимацию. +</p> +</li> +<li> +<p> +<strong>Сбросить все настройки</strong>: как следует из названия, эта кнопка сбрасывает + все настройки в значение по умолчанию. +</p> +</li> +</ul></div> +</div> +<div class="sect2"> +<h3 id="_единицы">12.2. Единицы</h3> +<div class="imageblock" style="text-align:center;"> +<div class="content"> +<img src="images/Pref2_f20.jpg" alt="Рисунок: Настройки системы мер" /> +</div> +</div> +<div class="paragraph"><p>Здесь вы можете выбрать между имперской или метрической системой мер для +единиц глубины, давления, объема, температуры и массы. Переключателями в +верхней части вы выбираете системы мер для всех единиц сразу, либо выберите +<strong>Настроить</strong> и укажите единицы для каждой величины по отдельности.</p></div> +<div class="paragraph"><p>Независимо от вышеперечисленных настроек, вы можете указать единицы измерения +времени (секунды или минуты). Координаты GPS могут быть представлены либо в +традиционном формате (градусы, минуты, секунды) либо в десятичном.</p></div> +</div> +<div class="sect2"> +<h3 id="_профиль">12.3. Профиль</h3> +<div class="imageblock" id="S_CCR_options" style="text-align:center;"> +<div class="content"> +<img src="images/Pref3_f20.jpg" alt="Рисунок: настройки профиля" /> +</div> +</div> +<div class="paragraph" id="S_GradientFactors"><p>В этой панели доступно две группы настроек:</p></div> +<div class="ulist"><ul> +<li> +<p> +<strong>Показывать</strong>: тут вы можете выбрать набор данных, отображаемых в профиле +погружений: +</p> +<div class="ulist"><ul> +<li> +<p> +<em>Пороговые значения</em>: <em>Subsurface</em> отображает на профиле погружения +парциальные давления азота, кислорода и гелия. Вы можете включить их +отображение с помощью кнопок-переключателей на слева от панели профиля. +Для каждого их этих графиков вы можете указать пороговые значения, при +превышении которых линия будет нарисована красным цветом. +</p> +</li> +<li> +<p> +<em>Показывать потолок дайв-компьютера красным цветом</em>: Если дайв-компьютер +записывает данные потолка, то вам может быть удобным различать его значения от +тех, что посчитаны <em>Subsurface</em>. Зачастую эти значения различаются из-за +разницы в алгоритмах, установках градиент-фактора и динамики расчет потолка. +</p> +</li> +<li> +<p> +<em>Неиспользуемые баллоны</em>: следует ли отображать неиспользуемые баллоны в +списке на вкладке Снаряжение. +</p> +</li> +<li> +<p> +<em>Показывать среднюю глубину</em>: Если в этом поле стоит галочка, <em>Subsurface</em> +будет показывать серой линией на профиле среднюю глубину погружения в конкретный момент времени. +Обычно это линия имеет форму английской буквы U и отражает максимальную среднюю глубины непосредственно +перед всплытием. +</p> +</li> +</ul></div> +</li> +<li> +<p> +<strong>Разное</strong>: +</p> +<div class="ulist" id="S_GradientFactors"><ul> +<li> +<p> +<em>Градиент фактор</em>: Значения GFLow для глубины и GFHigh для поверхности. + Эти значения задают консерватизм азотной экспозиции во время погружения, так + же, как вы настраиваете консерватизм вашего дайв-компьютера. Меньше значения + градиент-фактора, тем консервативнее вычисления относительно азотного + насыщения и тем глубже потолок всплытия. Установки 20/60 считаются достаточно + консервативными, а значения 60/90 достаточно суровы. Если в поле <strong>GF Low на + макс. глубине</strong> стоит галочка, значение нижнего градиент-фактора будет + использоваться на максимальной глубине. В противном случае GF Low будет + использоваться на всех глубинах ниже первой деко-остановки. Больше информации + вы можете найти по ссылкам: +</p> +<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> +</li> +<li> +<p> +<em>CCR: показывать установки</em>. При выборе этого параметра, на графике pO<sub>2</sub> + профиля погружения красной линией отображаются значения установок CCR (set-point). + См. <a href="#S_CCR_dives">Погружения с ребризером закрытого цикла</a>. +</p> +</li> +<li> +<p> +<em>CCR: индивидуальные значения сенсоров O<sub>2</sub></em>. Отображать показания отдельных кислородных + датчиков ребризера замкнутого цикла на графике pO<sub>2</sub>. + См. <a href="#S_CCR_dives">Погружения с ребризером закрытого цикла</a>. +</p> +</li> +</ul></div> +</li> +<li> +<p> +<strong>Настройки для погружений с ребризером:</strong> +</p> +<div class="ulist"><ul> +<li> +<p> +<em>Установка CCR для планировщика:</em> Укажите значение установки O<sub>2</sub> для планировщика. Она + определяет начальную установку PO<sub>2</sub> для отдельно взятого погружения в его начале. Вы можете + изменить значение установки через контекстное меню профиля погружения. +</p> +</li> +<li> +<p> +<em>pSCR метаболизм O<sub>2</sub>:</em> Для ребризеров полузамкнутого цикла указывает объем кислорода, + потребляемый дайвером в минуту. Установите это значение для планирования погружений с ребризером + pSCR и для расчета декомпрессионных обязательств. +</p> +</li> +<li> +<p> +<em>pSCR отношение сброса:</em> Отношение объема сброшенного газа к объему рециркулированного. + Используется при планировании погружений на pSCR-оборудовании. +</p> +</li> +</ul></div> +</li> +</ul></div> +</div> +<div class="sect2"> +<h3 id="_язык">12.4. Язык</h3> +<div class="paragraph"><p>Тут вы можете выбрать язык интерфейса <em>Subsurface</em>.</p></div> +<div class="imageblock" style="text-align:center;"> +<div class="content"> +<img src="images/Pref4_f20.jpg" alt="Рисунок: Настройки языка интерфейса" /> +</div> +</div> +<div class="paragraph"><p>Вы можете использовать системные настройки языка, что в большинстве случаев +использует тот же язык, что и ваша операционная система. Если по какой-то +причине вас это не устраивает, снимите галочку и выберите подходящий язык из +списка. Вы можете использовать фильтр чтобы быстро найти нужный вам язык в +списке. Смена языка требует перезапуска <em>Subsurface</em>.</p></div> +</div> +<div class="sect2"> +<h3 id="_сеть">12.5. Сеть</h3> +<div class="paragraph"><p>Эти настройки обеспечивают связь <em>Subsurface</em> с различными источниками данных в Интернет. Они +влияют на подключение к облачному хранилищу, импорт координат погружений из +<a href="#S_Companion"><em>веб-сервиса Subsurface</em></a> и импорт/экспорт данных из <em>Divelogs.de</em>. +Эти настройки зависят от вашего подключения и поставщика услуг Интернет, который должен предоставить +вам необходимую информацию.</p></div> +<div class="imageblock" style="text-align:center;"> +<div class="content"> +<img src="images/Pref5_f20.jpg" alt="Рисунок: Настройки сети" /> +</div> +</div> +<div class="paragraph"><p>Эта вкладка состоит из трех секций:</p></div> +<div class="ulist"><ul> +<li> +<p> +Прокси +Если для соединения с Интернет используется прокси-сервер, вам необходимо выбрать его тип из +выпадающего списка, после чего указать адрес и порт прокси-сервера. Если прокси-сервер требует +авторизации, укажите имя пользователя и пароль. Обычно эту информацию предоставляет провайдер +Интернет-услуг. +</p> +</li> +<li> +<p> +<em>Облачное хранилище</em>: Для того, чтобы хранить журнал погружений в облаке, вам необходимо + указать корректный адрес электронной почты и пароль. Это позволит <em>Subsurface</em> отправить вам + PIN-код и подготовить хранилище. Дополнительно к этому вам предлагаются два параметра: +</p> +<div class="ulist"><ul> +<li> +<p> +<em>Фоновая синхронизация</em> позволяет автоматически синхронизировать журнал в облако, в то время + как вы выполняете другие задачи внутри <em>Subsurface</em>. +</p> +</li> +<li> +<p> +<em>Локальное хранение пароля</em> сохраняет пароль на вашем компьютере. Обратите внимание, что + пароль хранится в незашифрованном виде. +</p> +</li> +</ul></div> +</li> +<li> +<p> +<em>Веб-сервис Subsurface</em>: при регистрации в <a href="#S_Companion">веб-сервисе <em>Subsurface</em></a>, вам + генерируется длинный и труднозапоминаемый ключ. Этот ключ необходимо встравить в это поле. + Поставьте галочку в поле <em>Сохранять ID пользователя</em>, чтобы сохранить этот ключ на вашем + компьютере. +</p> +</li> +</ul></div> +</div> +<div class="sect2"> +<h3 id="S_Facebook">12.6. Соединение с <em>Facebook</em></h3> +<div class="paragraph"><p>Эта вкладка позволяет войти в <em>Facebook</em> для дальнейшей публикации погружений в этой социальной +сети.</p></div> +<div class="imageblock" style="text-align:center;"> +<div class="content"> +<img src="images/Pref6_f20.jpg" alt="Рисунок: Панель авторизации Facebook" /> +</div> +</div> +<div class="paragraph"><p>При указании корректных логина и пароля <em>Facebook</em> вы сможете публиковать профили погружений и +комментарии к ним в своей хронике. Если вы закроете <em>Subsurface</em>, связь с <em>Facebook</em> будет +разорвана. Параметр "Запомнить соединение с Subsurace" на текущий момент ни на что не влияет. +См. подробнее в главе <a href="#S_facebook">Экспорт информации о погружении в <em>Facebook</em></a>.</p></div> +</div> +<div class="sect2"> +<h3 id="_геопоиск">12.7. Геопоиск</h3> +<div class="paragraph"><p><em>Subsurface</em> предоставляет возможность геопоиска местоположений по GPS координатам ( +выбранным на карте, введенным вручную либо полученным из вспомогательного приложения) +в Интернет. Очевидно, что эта функция работает только при наличии интернет-соединения. +У вас есть возможно указаться формат названия дайв-сайта, например <em>Страна/Область/Город</em> +(см. рисунок ниже).</p></div> +<div class="imageblock" style="text-align:center;"> +<div class="content"> +<img src="images/Pref7_f20.jpg" alt="Рисунок: Настройки геопоиска" /> +</div> +</div> +</div> +</div> +</div> +<div class="sect1"> +<h2 id="S_DivePlanner">13. Планировщик <em>Subsurface</em></h2> +<div class="sectionbody"> +<div class="paragraph"><p>Планировщик погружений <em>Subsurface</em> доступен из главного меню <em>Журнал → +Планировщик</em>. Расчеты азотного насыщения осуществляются по алгоритму Бюльмана +ZH-L16 с добавлением градиент-факторов за авторством Эрика Бейкера.</p></div> +<div class="sidebarblock"> +<div class="content"> +<div class="admonitionblock"> +<table><tr> +<td class="icon"> +<img src="images/icons/warning2.png" alt="Внимание" /> +</td> +<td class="content">Планировщик <em>Subsurface</em> ЯВЛЯЕТСЯ ЭКСПЕРИМЕНТАЛЬНЫМ и предполагает, что вы +знакомы с пользовательским интерфейсом программы. Вы можете использовать +планировщик только при условиях:</td> +</tr></table> +</div> +<div class="ulist"><ul> +<li> +<p> +Вы обучены планировать погружения и делали это ранее. +</p> +</li> +<li> +<p> +План погружения находится в пределах ваших сертификатов. +</p> +</li> +<li> +<p> +Планировщик делает расчеты для усредненного человека и не принимает во +внимание ваши индивидуальные психологическое и физическое состояние и образ +жизни. +</p> +</li> +<li> +<p> +Безопасность плана очень зависит от того, как вы используете планировщик. +</p> +</li> +<li> +<p> +Вы знакомы с пользовательским интерфейсом <em>Subsurface</em>. +</p> +</li> +<li> +<p> +Если вы не уверены в выше изложенном, вам не следует +использовать планировщик. +</p> +</li> +</ul></div> +</div></div> +<div class="sect2"> +<h3 id="_экран_планировщика">13.1. Экран планировщика</h3> +<div class="paragraph"><p>Как и журнал <em>Subsurface</em>, экран планировщика разделен на несколько областей +(см. рисунок ниже). Установочные параметры плана задаются в левой части +экрана. Эти параметры разделены на несколько групп: Доступные газы, Скорости, Планирование, Газы, Погружение.</p></div> +<div class="paragraph"><p>В правой верхней части экрана находится профиль планируемого погружения, +который можно менять только с помощью мыши. Это делает использование +планировщика очень простым.</p></div> +<div class="paragraph"><p>В правой нижней части экрана находится текстовая область <em>Детальный план +погружения</em>. В ней показываются все детали плана и предупреждения.</p></div> +<div class="imageblock" style="text-align:center;"> +<div class="content"> +<img src="images/PlannerWindow1_f20.jpg" alt="Рисунок: Начальные экран планировщика" /> +</div> +</div> +</div> +<div class="sect2"> +<h3 id="_пример_планирования_погружения_на_открытом_цикле">13.2. Пример планирования погружения на открытом цикле</h3> +<div class="ulist"><ul> +<li> +<p> +В левой нижней части экрана планировщика расположен выпадающий список (на рисунке ниже обведен синей линией), предоставляющий варианта типа погружения: +</p> +<div class="ulist"><ul> +<li> +<p> +Открытый цикл (по умолчанию) +</p> +</li> +<li> +<p> +Ребризер замкнутого цикла (CCR) +</p> +</li> +<li> +<p> +Пассивный ребризер полузамкнутого цикла (pSCR) +</p> +</li> +</ul></div> +</li> +<li> +<p> +Выберите режим Открытого цикла. +</p> +</li> +<li> +<p> +Удостоверьтесь, что начальные параметры погружения в верхней левой части + экрана введены правильно. Они включают: начальные дата и время погружения, + атмосферное давление в точке погружения. Давление может быть задано как + высота в метрах над уровнем моря, считая атмосферное давление равным 1.013 бар. +</p> +</li> +<li> +<p> +В таблице, озаглавленной <em>Доступные газы</em>, добавьте информацию об + используемых баллонах и составах смесей. Сделать это можно таким же образом, + как и в случае <a href="#cylinder_definitions">добавления баллонов к погружению</a>. Выберите + тип баллона из выпадающего списка, укажите рабочее давление, Если поле + процентного содержания кислорода (O<sub>2</sub>%) пустое, то эта смесь считается + воздухом. В противном случае введите концентрацию кислорода/гелия. + Дополнительные баллоны можно добавить нажатием на значок "+". +</p> +</li> +<li> +<p> +Профиль планируемого погружения может быть создан двумя способами: +</p> +<div class="ulist"><ul> +<li> +<p> +Перетаскивайте путевые точки (маленькие белые кружки), чтобы создать необходимый вам профиль. + Дополнительные точки можно создать двойным щелчком мыши. Удалить точку можно правым щелчком мыши + ней и выбрав пункт <em>Удалить эту точку</em> из появившегося контекстного меню. +</p> +</li> +<li> +<p> +Наиболее эффективный способ создания профиля - ввод необходимых значений в таблицу, + озаглавленную <em>Путевые точки плана</em>. Первая строка таблицы описывает время и глубину спуска с + поверхности. Последующие сегменты описывают донную фазу погружения. Колонка <em>Установка CC</em> важна + только для погружений с ребризером. Точки подъема обычно не указываются, поскольку именно их + планировщик и должен рассчитать. Для добавления нового сегмента нажмите значок "+" в правом + верхнем углу таблицы. Добавленные сегменты автоматически появляются на графике профиля погружения. +</p> +</li> +</ul></div> +</li> +</ul></div> +<div class="sect3"> +<h4 id="_рекреационные_погружения">13.2.1. Рекреационные погружения</h4> +<div class="paragraph"><p>Планировщик <em>Subsurface</em> предлагает изощренный способ планирования рекреационных погружений, т.е. +погружений в бездекомпрессионных пределах. Он также учитывает насыщение азотом после предыдущих +погружений. Но традиционные таблицы тоже позволяют вести расчеты по остаточному азоту. Для чего +тогда нужен планировщик в рекреационных дайвах? При использовании рекреационных таблиц во внимание +принимается максимальная глубина погружения. Однако мало какие погружения выполняются на постоянной +глубине, равной максимальной ("квадратный" профиль). Т.е. таблицы чересчур консервативны в отношении +остаточного азота после предыдущих погружений. Планировщик <em>Subsurface</em> рассчитывает остаточное +азотное насыщение исходя из реальных профилей ранее совершенных погружений также, как это делает +дайв-компьютер во время погружения. Это означает, вы что получаете "кредит" в виде времени, не +проведенного на максимальной глубине во время предыдущих погружений, и как следствие, более долгое +время последующих погружений. Это также означает, что вы должны загрузить все предыдущие погружения +в <em>Subsurface</em>, прежде чем пользоваться планировщиком.</p></div> +<div class="paragraph"><p>Для планирования погружения вам необходимо указать параметры.</p></div> +<div class="ulist"><ul> +<li> +<p> +Убедитесь в правильности даты и времени планируемого погружения. Это позволит правильно вычислить + остаточное насыщение азотом после предыдущих погружений. +</p> +</li> +<li> +<p> +Сразу под заголовком <em>Планирование</em> поставьте галочки в полях <em>Рекреационный режим</em> и + <em>Остановка безопасности</em>. +</p> +</li> +<li> +<p> +Укажите объем баллонов, тип смеси (воздух или % кислорода) и начальное давление в таблице + <em>Доступные смеси</em> в левой верхней части планировщика. +</p> +</li> +<li> +<p> +Планировщик посчитает достаточно ли указанных газов для выполнения погружения. Для того, чтобы + результат был реалистичным, в разделе <em>Газы</em> укажите ваш <em>SAC на дне</em>. Разумные значения лежат + в интервале от 15 до 30л/мин (для новичков и сложных погружений ближе к 30л/мин) +</p> +</li> +<li> +<p> +Укажите газовый резерв, который должен оставаться в баллоне в конце донной части погружения + непосредственно перед подъемом. Зачастую это 50 бар. Этот резерв может понадобиться при всплытии + случись необходимость поделиться воздухом с вашим партнером. Нельзя сколько точно газа может + понадобиться, это зависит от глубины подъема и скорости. Поэтому большинство школ предусматривают + фиксированный резерв равный 50 или 60 барам, или 25% или 33% (правило третей). +</p> +</li> +<li> +<p> +Укажите глубину погружения, перетаскивая путевые точки на профиле или (что лучше) задавая + необходимые глубины в таблице <em>Путевые точки плана</em>. Для многоуровневых погружений вы также можете + добавить новые сегменты в таблицу или создать новые путевые точки непосредственно на профиле. + <em>Subsurface</em> автоматически пересчитает донное время до максимального в рамках бездекомпрессионного + предела (NDL). +</p> +</li> +<li> +<p> +При необходимости измените скорость всплытия. Значения по умолчанию считаются безопасными для + рекреационных дайверов. +</p> +</li> +</ul></div> +<div class="paragraph"><p>Профиль в планировщике погружений отражает максимальное время погружения в бездекомпрессионных +пределах согласно алгоритму Бюльмана ZH-L16, а также параметрам газа и глубины, как описано выше. +<em>Subsurface</em> позволяет быстро оценить длительность погружения как функцию глубины, учитывая +азотное насыщение после предыдущих дайвов. План также включает оценку расхода газов исходя из +установок в таблице <em>Доступные смеси</em>. Если начальное давление в баллоне установлено в 0, то +отображаемое время погружения является истинным NDL без учета используемой смеси. Если профиль +погружения отображается КРАСНЫМ цветом, это означает, что превышены рекреационные пределы и либо +глубина, либо время должны уменьшены.</p></div> +<div class="paragraph"><p>На рисунке ниже приведен план рекреационного погружения на 30 метров. Несмотря на то, что бездекомрпессионный +предел (NDL) составляет 23 минуты, время погружения ограничено количеством воздуха. Текст в правой +нижней части экрана сообщает о том, что необходим запас воздуха для поддержки партнера при всплытии.</p></div> +<div class="imageblock" style="text-align:center;"> +<div class="content"> +<img src="images/rec_diveplan.jpg" alt="Рисунок: План рекреационного погружения" /> +</div> +</div> +</div> +<div class="sect3"> +<h4 id="_нерекреационные_погружения_на_открытом_цикле_включая_декомпрессию">13.2.2. Нерекреационные погружения на открытом цикле, включая декомпрессию</h4> +<div class="paragraph"><p>Нерекреационные погружения подразумевают превышение бездекомпрессионных пределов и/или использование +нескольких дыхательный смесей. Планирование таких погружение состоит из трех фаз:</p></div> +<div class="paragraph"><p><strong>а) Управление азотом</strong>: включает в себя указание скоростей спуска и всплытия, а +также деко-модели (GFLow, GFHigh или степень консерватизма) в секциях <em>Скорость</em> +и <em>Планирование</em> в левой нижней части экрана. Выберите одну из двух поддерживаемых +деко-моделей: Бюльман или VPM-B. Для модели Бюльмана необходимо указать градиент-факторы +(GFLow и GFHigh). Изначально значения GFLow и GFHigh берутся из настроек <em>Subsurface</em>, +однако, если вы их поменяли в планировщике, значения по умолчанию в настройках не +затрагиваются. Значения градиент-фактора влияют на расчет потолка и его глубину. +Слишком низкие значения GFLow ведут к ранним и более глубоким деко-остановкам. + ** Подробнее читайте в <a href="#S_GradientFactors">настройках градиент-фактора</a> и внешних источниках:</p></div> +<div class="paragraph"><p>При выборе VPM-B модели необходимо указать уровень консерватизма в диапазоне от 0 (наименее +консервативный) до 4 (наиболее консервативный). Эта модель обычно предлагает более глубокие +остановки и зачастую делает погружения немного короче по сравнению с моделью Бюльмана. При выборе +этих моделей помните, что это не реальные физиологические, а математические модели, которые +похоже работают на практике.</p></div> +<div class="paragraph"><p>Вы можете найти больше информации во внешних источниках:</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&ie=UTF8&qid=1403932320&sr=1-1&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. +Превосходный обзор декомпрессионных моделей Бюльмана и VPM-B. +</p> +</li> +</ul></div> +<div class="paragraph"><p>Скорость всплытия важна в фазе рассыщения в конце дайва и указывается для +нескольких диапазонов глубины, принимая во внимание среднюю глубину как точку +отсчета. Средняя глубина отображается на профиле красной горизонтальной линией. +Скорость всплытия на больших глубинах находится обычно в пределах 8-12 м/мин, +в то время, как возле поверхности она обычно составляет 4-9 м/мин. Скорость +спуска также указывается. Если установлен флажок <em>Падение к первой глубине</em>, +то в фазе спуска будет использоваться максимальная скорость, указанная в секции <em>Скорости</em>.</p></div> +<div class="paragraph"><p><strong>б) Управление кислородом</strong>: в секции <em>Газы</em> необходимо указать максимальное +парциальное давление кислорода в донной фазе (<em>pO₂ на дне</em>) и во время +декомпрессионных остановок (<em>pO₂ на деко</em>). Обычно используются значения +1.4 и 1.6 бар соответственно, и парциальное давление 1.6 бар является +максимально допустимым. Настройки pO₂ и глубина замены смеси могут быть также +отредактированы в секции <em>Доступные смеси</em>. Обычно планировщик принимает +решение о переключении на новую смесь, когда при подъеме парциальное давление +кислорода в этой смеси опускается ниже значения 1.6 бар.</p></div> +<div class="paragraph"><p><strong>в) Управление расходом газов:</strong> Вам необходимо контролировать и учитывать +объем доступных газов, чтобы безопасно вернуться на поверхность,и , возможно, +поделиться с напарником. В секции <em>Газы</em> укажите ваш лучший (но при этом +достаточно консервативный) поверхностный расход воздуха (SAC, иногда именуемый +RMV) в л/мин (в настоящий момент используется только метрическая система). Укажите +SAC отдельно для донной фазы (<em>SAC на дне</em>) и для остановок декомпрессии (<em>SAC +на деко</em>). Обычно это значения находятся в пределах 20-30 л/мин. Для более +точного управления расходом газов не нужно строить догадки, регулярно +контролируйте свой SAC, погружаясь в разных условиях и с разным снаряжением. +Планировщик рассчитывает общий расход газов за все время погружения и выдаст +предупреждение если расход превысит доступный объем газов. Для вашей +безопасности всегда оставляйте резерв газов на случай непредвиденных обстоятельств. +В техническом дайвинге такой резерв может составлять до 66% от общего объема газов.</p></div> +<div class="paragraph"><p>И, наконец, вы можете приступить к планированию времени и глубины +погружения. Для этого <em>Subsurface</em> предоставляет уникальный графический +интерфейс. Принцип его работы такой же, как при ручном добавлении погружения в +журнал. После активации планировщика вам будет предложен начальный профиль +погружения на 15 м в течение 40 минут. Путевый точки можно перетаскивать +мышью или с помощью стрелок клавиатуры, Для создания новой точки, дважды +щелкните на линии сегмента. При превышении какого-либо предела (парциальное +давление, объем), <em>Subsurface</em> изменит цвет фона профиля с +ГОЛУБОГО на КРАСНЫЙ.</p></div> +<div class="paragraph"><p>Каждая путевая точка на профиле создает запись в таблице <em>Путевые точки +плана</em> в левой части экрана. Проверьте, чтобы значение в колонке <em>Используемый +газ</em> соответствовало одной из смесей, указанных в таблице <em>Доступные смеси</em>. +Добавьте необходимые путевые точки с тем, чтобы профиль соответствовал вашему +плану, т.е. присутствовал донная фаза, глубокие остановки (если планируются). +Путевые точки всплытия <em>Subsurface</em> расставит сам с учетом декомпрессионных +обязательств. +Путевые точки можно двигать с помощью мыши или стрелок на клавиатуре. +Точки можно редактировать и создавать непосредственно в таблице +<em>Путевые точки плана</em>. На самом деле, вы можете спланировать погружение +пользуясь только этой таблицей.</p></div> +<div class="paragraph"><p>Укажите замену баллонов/смесей так же, как это делается в случае +<a href="#S_CreateProfile">ручного создания профиля погружения</a>. События замены смесей +должны соответствовать баллонам и смесям из таблицы <em>Доступные смеси</em>. При +наличии нескольких смесей, <em>Subsurface</em> будет автоматически предлагать замену, +однако вы можете удалить и добавить событие самостоятельно, вызвав контекстное +меню точки правым щелчком мыши.</p></div> +<div class="paragraph"><p>Ненулевое значение в колонке "Установка СС" в таблице путевых точек означает корректное значение +установки и что погружение на этом сегменте выполняется на CCR-ребризере. Если последний вручную +введенный сегмент выполняется на CCR, декомпрессионные процедуры рассчитываются согласно значения +указанной установки. Если же последний сегмент выполняется на открытом цикле (значение установки кислорода +равно нулю), декомпрессионные обязательства рассчитываются в режиме ОЦ. Замена газов предусмотрена +только для открытого цикла.</p></div> +<div class="paragraph"><p>Ниже на рисунке приведен пример плана погружения на 45м с использованием EAN26 +и всплытием на EAN50, используя настройки, описанные выше:</p></div> +<div class="imageblock" style="text-align:center;"> +<div class="content"> +<img src="images/DivePlanner2_f20.jpg" alt="Рисунок: Планирование погружения: настройки" /> +</div> +</div> +<div class="paragraph"><p>После окончания планирование, вы можете сохранить план, нажав на кнопку +<em>Сохранить</em>. План появится в списке погружений.</p></div> +<div class="paragraph"><p><strong>Детальный план погружения</strong></p></div> +<div class="paragraph"><p>В правой нижней части экрана планировщика находится текстовая область с +подробным словесным описанием плана погружения. Вы можете изменить его +детализацию с помощью нескольких параметров в секции <em>Заметки погружения</em>. +Если выбран пункт <em>Подробный план</em>, описание будет достаточно многословным. +При превышении каких-либо пределов в нижней части будет выведено +предупреждение.</p></div> +<div class="paragraph"><p>При выборе пункта <em>Показать время сегмента</em>, план будет отображать время на +каждой отдельно взятой глубине. Время сегмента ВКЛЮЧАЕТ время, необходимое чтобы +перейти к заданной глубине. Однако, если выбран параметр <em>Показать переходы в +деко</em>, то время переходом показывается отдельно от времени сегментов.</p></div> +</div> +</div> +<div class="sect2"> +<h3 id="_планирование_погружений_на_ребризере_полузамкнутого_типа">13.3. Планирование погружений на ребризере полузамкнутого типа</h3> +<div class="paragraph"><p>Для планирования таких погружений выберите pSCR в списке, как показано на рисунке выше (список +обведен синей линией). +Параметры pSCR-погружений также задаются в *Настройках* (в главном меню выберите <em>Файл → Настройки</em> +и вкладку <em>Профиль</em>). К этим настройкам относятся уровень метаболизма и отношение сброса (1:10 по +умолчанию). Расчеты принимают также во внимание снижение уровня кислорода в области загубника. Если +значение pO<sub>2</sub> опускается ниже безопасного, в <em>Детальном плане</em> будет отображено предупреждение. +Обычно pSCR погружение выполняется с одним основным баллоном и несколькими аварийными. Поэтому +заполнение таблицы доступных баллонов и путевых точек очень похоже на погружение CCR, описанное +ниже. Однако для pSCR-погружений не указываются установки кислорода. Ниже приведен план погружения +с использованием pSCR. Он очень похож на план CCR ниже, но обратите внимание на более долгий подъем, +что связано с более низким уровнем кислорода, вызванным снижением его количества в области загубника.</p></div> +<div class="imageblock" style="text-align:center;"> +<div class="content"> +<img src="images/Planner_pSCR1_f20.jpg" alt="Рисунок: планирование pSCR-погружения" /> +</div> +</div> +</div> +<div class="sect2"> +<h3 id="_планирование_погружений_на_ребризере_замкнутого_цикла">13.4. Планирование погружений на ребризере замкнутого цикла</h3> +<div class="paragraph"><p>Для планирования таких погружений выберите CCR в списке, как показано на рисунке выше (список +обведен синей линией).</p></div> +<div class="paragraph"><p><strong>Доступные смеси</strong>: добавьте в таблицу доступных смесей информацию о баллонах дилуэнта и аварийных +газах. НЕ вводите информацию о кислородном баллоне, поскольку он подразумевается при использовании +режима CCR.</p></div> +<div class="paragraph"><p><strong>Ввод установок</strong>: укажите значение установки по умолчанию в *Настройках* приложения (в главном меню +выберите <em>Файл → Настройки</em> и вкладку <em>Профиль</em>). По умолчанию для всех добавляемых сегментов +точка установки берется из настроек, он вы можете поменять их по своему желанию. Значение равное +нулю означает, что дайвер перешел на открытый цикл. Декомпрессия всегда рассчитывается используя +последнюю установку вручную добавленного сегмента. Чтобы запланировать переход на ОЦ во время подъема, +добавьте одноминутный сегмент со значением установки равным нулю. Декомпрессионный алгоритм +автоматически не меняет смеси в режиме CCR (когда указана положительная установка), +но делает это для всплытий на открытом цикле.</p></div> +<div class="paragraph"><p>Профиль погружения на ребризере замкнутого типа может выглядеть так:</p></div> +<div class="imageblock" style="text-align:center;"> +<div class="content"> +<img src="images/Planner_CCR1_f20.jpg" alt="Рисунок: Планирование CCR-погружения, настройка" /> +</div> +</div> +<div class="paragraph"><p>Обратите внимание, что в <em>Детальном плане погружения</em> расход газа для CCR-сегментов не рассчитывается +и всегда равен нулю.</p></div> +</div> +<div class="sect2"> +<h3 id="S_Replan">13.5. Изменение существующего плана</h3> +<div class="paragraph"><p>Обычно, после сохранения плана, он доступен в <strong>Списке погружений</strong>. <em>Subsurface</em> не предоставляет +возможности изменить план из списка. Для того, чтобы изменить план, выберите его в списке. Затем в +главном меню выберите <em>Журнал → Перепланировать</em>. Это действие откроет планировщик с существующим +планом, позволяя изменить его.</p></div> +<div class="paragraph"><p>В случае перепланирования у вас появляется возможность <strong>Сохранить новый</strong> план, для того, чтобы +не перезаписывать старый. Если новая копия сохраняется с тем же временем, что и старый план, то они +считаются двумя версиями одного плана и не влияют друг на друга при вычислении декомпрессионных +обязательств.</p></div> +</div> +<div class="sect2"> +<h3 id="_планирование_повторных_погружений">13.6. Планирование повторных погружений</h3> +<div class="paragraph"><p><em>Subsurface</em> позволяет планировать повторные погружения при условии, что вы +корректно укажете дату и время начала. При этом учитывается остаточное +насыщение после предыдущего погружения.</p></div> +<div class="paragraph"><p>Если вы только закончили долгое/глубокое погружение и планируете новое, +выберите последний дайв в списке погружение и активируйте планировщик +<em>Subsurface</em>. В зависимости от времени начала планируемого дайва, остаточное +насыщение предыдущего погружения будет принято во внимание и план будет +построен с учетом этих ограничений.</p></div> +<div class="paragraph"><p>Если вы используете одну стандартную конфигурацию (например, как в GUE), то +можно создать шаблонное погружение. Чтобы спланировать погружение с этой +конфигурацией, выберите шаблонное погружение в списке и активируйте планировщик: +для нового плана будет использоваться конфигурация из шаблона.</p></div> +</div> +<div class="sect2"> +<h3 id="_печать_плана_погружения">13.7. Печать плана погружения</h3> +<div class="paragraph"><p>Вы можете распечатать план погружения с тем чтобы взять его с собой под воду, нажав кнопку <em>Печать</em>. +Альтернативный способ - скопировать текст из <em>Детального плана погружения</em> и вставить его в в ваш +любимый текстовый редактор.</p></div> +<div class="paragraph"><p>План погружения имеет много общего с журналом обычного погружения (профиль, примечания и т.д.). +После сохранения плана, его детали и расчет по газам сохраняются в *Примечаниях*. Во время +планирования он может быть распечатан по нажатию кнопки <em>Печать</em>. Однако после сохранения план +выглядит как обычный дайв.</p></div> +</div> +</div> +</div> +<div class="sect1"> +<h2 id="_пункты_главного_меню_subsurface">14. Пункты главного меню Subsurface</h2> +<div class="sectionbody"> +<div class="paragraph"><p>В этой главе описываются пункты главного меню и их функции. Некоторые пункты +ссылаются на соответствующие главы данного руководства для быстрой навигации.</p></div> +<div class="sect2"> +<h3 id="_файл">14.1. Файл</h3> +<div class="ulist"><ul> +<li> +<p> +<a href="#S_NewLogbook"><em>Новый журнал</em></a> - Закрывает текущий открытый журнал и + создает новый. +</p> +</li> +<li> +<p> +<em>Открыть журнал</em> - Вызывает диалог выбора файла для открытия + журнала. +</p> +</li> +<li> +<p> +<em>Открыть облачное хранилище</em> - Загружает ранее сохраненный журнал из + <a href="#S_Cloud_storage"><em>облачного хранилища</em></a>. +</p> +</li> +<li> +<p> +<em>Сохранить</em> - Сохраняет текущий открытый журнал. +</p> +</li> +<li> +<p> +<em>Сохранить в облаке</em> - Сохраняет журнал в <a href="#S_Cloud_storage"><em>облачном хранилище</em></a>. +</p> +</li> +<li> +<p> +<em>Сохранить как</em> - Сохраняет текущий журнал в файл с новым именем +</p> +</li> +<li> +<p> +<em>Закрыть</em> - Закрывает текущий журнал. +</p> +</li> +<li> +<p> +<a href="#S_ExportLog"><em>Экспорт</em></a> - экспортирует текущий журнал или выбранные + погружения в один из форматов. +</p> +</li> +<li> +<p> +<a href="#S_PrintDivelog"><em>Печать</em></a> - печать журнала или выбранных погружений. +</p> +</li> +<li> +<p> +<a href="#S_Preferences"><em>Настройки</em></a> - настройка параметров <em>Subsurface</em> +</p> +</li> +<li> +<p> +<a href="#S_FindMovedImages"><em>Найти перемещенные фото</em></a> - Если ранее загруженные фотографии были перенесены + в другое место, найти их и обновить их местоположение в соответствующих погружениях. +</p> +</li> +<li> +<p> +<em>Выход</em> - Выйти из <em>Subsurface</em> +</p> +</li> +</ul></div> +</div> +<div class="sect2"> +<h3 id="_импорт">14.2. Импорт</h3> +<div class="ulist"><ul> +<li> +<p> +<a href="#S_ImportDiveComputer"><em>Импорт из дайв-компьютера</em></a> - импорт погружений + из дайв-компьютера +</p> +</li> +<li> +<p> +<a href="#Unified_import"><em>Импорт журналов</em></a> - импорт погружений из сторонних + форматов +</p> +</li> +<li> +<p> +<a href="#S_Companion"><em>Импорт координат</em></a> - загрузка координат погружений из + мобильного помощника <em>Subsurface</em>. +</p> +</li> +<li> +<p> +<a href="#S_ImportingDivelogsDe"><em>Импорт с сайта divelogs.de</em></a> - импорт погружений + из интернет-сервиса <em>www.Divelogs.de</em>. +</p> +</li> +</ul></div> +</div> +<div class="sect2"> +<h3 id="_журнал">14.3. Журнал</h3> +<div class="ulist"><ul> +<li> +<p> +<a href="#S_EnterData"><em>Добавить погружение</em></a> - ручное добавление погружения. +</p> +</li> +<li> +<p> +<em>Редактировать погружение</em> - Позволяет отредактировать погружение, введенное вручную. +</p> +</li> +<li> +<p> +<a href="#S_DivePlanner"><em>Планировщик</em></a> - запускает планировщик погружений. +</p> +</li> +<li> +<p> +<a href="#S_Replan"><em>Перепланирование погружения</em></a> - Редактировать существующий план погружения +</p> +</li> +<li> +<p> +<a href="#S_CopyComponents"><em>Копировать параметры погружения</em></a> - скопировать указанные поля погружения + в буфер обмена +</p> +</li> +<li> +<p> +<em>Вставить параметры погружения</em> - вставить из буфера параметры, скопированные ранее, + в выделенные погружения +</p> +</li> +<li> +<p> +<a href="#S_Renumber"><em>Перенумеровать</em></a> - перенумерация списка погружений. +</p> +</li> +<li> +<p> +<a href="#S_Group"><em>Авто-группировка</em></a> - автоматическая группировка погружений в + поездки. +</p> +</li> +<li> +<p> +<a href="#S_DeviceNames"><em>Мои дайв-компьютеры</em></a> - редактирование названий + дайв-компьютеров. +</p> +</li> +<li> +<p> +<a href="#S_Filter"><em>Фильтр погружений</em></a> - фильтрация списка погружений +</p> +</li> +</ul></div> +</div> +<div class="sect2"> +<h3 id="_вид">14.4. Вид</h3> +<div class="ulist"><ul> +<li> +<p> +<a href="#S_ViewPanels"><em>Все</em></a> - показать все четыре панели <em>Subsurface</em>. +</p> +</li> +<li> +<p> +<a href="#S_ViewPanels"><em>Список</em></a> - показать только список погружений. +</p> +</li> +<li> +<p> +<a href="#S_ViewPanels"><em>Профиль</em></a> - показать только профиль погружения. +</p> +</li> +<li> +<p> +<a href="#S_ViewPanels"><em>Информация</em></a> - показать только информационную панель. +</p> +</li> +<li> +<p> +<a href="#S_ViewPanels"><em>Карта</em></a> - показать только карту. +</p> +</li> +<li> +<p> +<em>Статистика по годам</em> - показать статистику журнала погружений по годам и + месяцам. +</p> +</li> +<li> +<p> +<em>Предыдущий компьютер</em> - переключиться на предыдущий компьютер. +</p> +</li> +<li> +<p> +<em>Следующий компьютер</em> - переключиться на следующий компьютер. +</p> +</li> +<li> +<p> +<em>Полный экран</em> - переключение полноэкранного режима. +</p> +</li> +</ul></div> +</div> +<div class="sect2"> +<h3 id="_поделиться">14.5. Поделиться</h3> +<div class="ulist"><ul> +<li> +<p> +- <a href="#S_Facebook"><em>Facebook</em></a> - поделиться информацией о выбранном погружении в вашей хронике на Facebook. +</p> +</li> +</ul></div> +</div> +<div class="sect2"> +<h3 id="_помощь">14.6. Помощь</h3> +<div class="ulist"><ul> +<li> +<p> +<em>О программе</em> - показывает информационное окно с указанием версии + <em>Subsurface</em> +</p> +</li> +<li> +<p> +<em>Проверить обновления</em> - проверяет доступность новой версии на + <a href="http://subsurface-divelog.org/">_веб-сайте Subsurface</a>. +</p> +</li> +<li> +<p> +<a href="#S_UserSurvey"><em>Опрос пользователей</em></a> - помогите нам улучшить <em>Subsurface</em>, заполнив опросник. +</p> +</li> +<li> +<p> +<em>Руководство пользователя</em> - открывает этот документ в новом окне. +</p> +</li> +</ul></div> +</div> +</div> +</div> +<div class="sect1"> +<h2 id="APPENDIX_A">15. ПРИЛОЖЕНИЕ А: Настройка ОС для импорта из дайв-компьютера</h2> +<div class="sectionbody"> +<div class="sect2"> +<h3 id="_удостоверьтесь_что_установлены_необходимые_драйверы">15.1. Удостоверьтесь, что установлены необходимые драйверы</h3> +<div class="admonitionblock"> +<table><tr> +<td class="icon"> +<img src="images/icons/drivers.jpg" alt="Замечание" /> +</td> +<td class="content">Операционной системе вашего настольного компьютера необходим соответствующий +драйвер для с связи с дайв-компьютером в зависимости от того, каким образом +дайв-компьютер подключен (Bluetooth, USB, инфракрасный порт).</td> +</tr></table> +</div> +<div class="ulist"><ul> +<li> +<p> +В Linux вам может понадобиться загрузить соответствующий модуль ядра. + Большинство дистрибутивов делают это автоматически, так что вам не нужно + предпринимать каких-то действий. Однако в некоторых случаях, например + для ИК-устройств, вам придется загрузить дополнительный драйвер. +</p> +</li> +<li> +<p> +В случае Windows OC сама предложит загрузить корректный драйвер сразу + после подключения дайв-компьютера к USB-порту. +</p> +</li> +<li> +<p> +Пользователям MAC возможно придется самим найти соответствующий драйвер. + Например, для Mares Puck и других дайв-компьютеров, использующих + интерфейс последовательного USB-порта на основе чипа Silicon Labs CP2101, + необходимый драйвер с именем <em>Mac_OSX_VCP_Driver.zip</em> можно взять на + сайте <a href="http://www.silabs.com/support/pages/document-library.aspx?p=Interface&f=USB%20Bridges&pn=CP2101">Silicon Labs document and software repository</a>. +</p> +</li> +</ul></div> +</div> +<div class="sect2"> +<h3 id="S_HowFindDeviceName">15.2. Как определить имя USB-устройства и получить права доступа</h3> +<div class="admonitionblock"> +<table><tr> +<td class="icon"> +<img src="images/icons/usb.jpg" alt="Замечание" /> +</td> +<td class="content">Когда вы подключаете дайв-компьютер с помощью USB-кабеля, обычно <em>Subsurface</em> +предлагает либо список устройств (точек монтирования в случае Uemis Zurich), +либо делает список недоступным, если имя устройства не требуется вовсе. В +редких случаях, если это не работает, попробуй следовать этим инструкциям, +чтобы определить имя устройства самостоятельно:</td> +</tr></table> +</div> +<div class="paragraph"><div class="title">Windows:</div><p>Простым перебором попробуйте COM1, COM2 и т.д. Список содержит все +подключенные COM-устройства.</p></div> +<div class="paragraph"><div class="title">Mac OS:</div><p>Список должен содержать все подключенные устройства.</p></div> +<div class="paragraph"><div class="title">Linux:</div><p>Наиболее точный способ определить название порта:</p></div> +<div class="ulist"><ul> +<li> +<p> +Отсоедините USB-кабель от дайв-компьютера +</p> +</li> +<li> +<p> +Откройте терминал +</p> +</li> +<li> +<p> +Введите команду <em>dmesg</em> и нажмите Enter +</p> +</li> +<li> +<p> +Подсоедините USB-кабель к дайв-компьютеру +</p> +</li> +<li> +<p> +Введите команду <em>dmesg</em> и нажмите Enter +</p> +</li> +</ul></div> +<div class="paragraph"><p>Вы должны увидеть схожие сообщения:</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>Третья строчка снизу показывает, что FTDI USB-адаптер обнаружен и подключен +как устройство <code>ttyUSB3</code>. Для импорта в <em>Subsurface</em> используйте имя +<code>/dev/ttyUSB3</code>.</p></div> +<div class="paragraph"><p>Убедитесь, что у вас есть права на запись в устройство:</p></div> +<div class="paragraph"><p>В Unix-подобных операционных системах доступ к USB-портам разрешен только +пользователям, которые являются членами группы <code>dialout</code>. Если пользователь не +root, то он возможно не входит в эту группу и не сможет использовать USB-порт. +Допустим, что имя пользователя <em>johnb</em>.</p></div> +<div class="ulist"><ul> +<li> +<p> +Под пользователем root выполните команду <code>usermod -a -G dialout johnb</code> (для + пользователей Ubuntu: <code>sudo usermod -a -G dialout johnb</code>) +</p> +</li> +<li> +<p> +Выполните команду <code>id johnb</code>. Она отображает список всех групп, к которым + принадлежит указанный пользователь. Убедитесь, что в списке групп + присутствует группа <code>dialout</code>. +</p> +</li> +<li> +<p> +В некоторых случаях (например, Ubuntu) может потребоваться закрыть текущий сеанс + и войти в систему заново. +</p> +</li> +</ul></div> +<div class="paragraph"><p>Зная название устройства (например, <code>dev/ttyUSB3</code>) и имея права на доступ к +USB-порту, у вас должно получиться импортировать погружения из +дайв-компьютера.</p></div> +</div> +<div class="sect2"> +<h3 id="S_HowFindBluetoothDeviceName">15.3. Настройка Bluetooth-устройств</h3> +<div class="admonitionblock"> +<table><tr> +<td class="icon"> +<img src="images/icons/bluetooth.jpg" alt="Замечание" /> +</td> +<td class="content">Для дайв-компьютеров с Bluetooth-интерфейсом (например, Heinrichs Weikamp Frog +или Shearwater Predator, Petrel или Nerd), процедура получения имени устройства +отличается от той, что описана выше:</td> +</tr></table> +</div> +<div class="ulist"><ul> +<li> +<p> +<strong>После включения Bluetooth на дайв-компьютере, убедитесь что он находится в режиме выгрузки.</strong> +</p> +</li> +</ul></div> +<div class="paragraph"><p>По вопросам сопряжения дайв-компьютера обратитесь к документации +производителя. В случае Shearwater Predator/Petrel/Nerd выберите <em>Dive Log → +Upload Log</em> и ожидайте сообщения <em>Wait PC</em>.</p></div> +<div class="ulist"><ul> +<li> +<p> +<strong>Сопряжение настольного и дайв-компьютера</strong> +</p> +</li> +</ul></div> +<div class="sect3"> +<h4 id="_windows_2">15.3.1. Windows:</h4> +<div class="paragraph"><p>Bluetooth вероятнее всего уже включен. Для сопряжения устройств перейдите в +<em>Панель управления→Устройства Bluetooth→Добавить беспроводное устройство</em>. +Вам будет представлено окно, в котором должен показываться ваш дайв-компьютер. +Нажмите на нем правой кнопкой мыши и из контекстного меню выберите +<em>Свойства→COM порты</em>, чтобы определить название порта. Если вам показываются +несколько портов, выберите тот, который помечен как "Исходящий".</p></div> +<div class="paragraph"><p>Для импорта в <em>Subsurface</em> этот порт уже должен быть в списке. Если его там +нет, то введите имя порта вручную.</p></div> +<div class="paragraph"><p>Примечание: Если у вас возникают проблемы с загрузкой из дайв-компьютера после +использования других программ, попробуйте удалить существующее сопряжение.</p></div> +</div> +<div class="sect3"> +<h4 id="_macos">15.3.2. MacOS:</h4> +<div class="paragraph"><p>Нажмите на значке Bluetooth в строке меню и выберите <em>Настроить устройство +Bluetooth…</em>. Дайв-компьютер должен появиться в списке устройств. Выберите +его и выполните процедуру сопряжения. Этот шаг потребуется выполнить один +раз.</p></div> +<div class="paragraph"><p>После завершения сопряжения, устройство должно показываться в <em>Subsurface</em> в +списке <em>Устройство или точка монтирования</em> в диалоге импорта.</p></div> +</div> +<div class="sect3"> +<h4 id="_linux">15.3.3. Linux:</h4> +<div class="paragraph"><p>Удостоверьтесь, что Bluetooth включен на вашем настольном компьютере. Процесс +сопряжения в этом случае достаточно прост. Например, в Gnome3 в правом верхнем +углу рабочего стола должен быть значок Bluetooth. Выберите <em>Настроить новое +устройство</em>. В появившемся окне выберите дайв-компьютер и выполните +сопряжение. Если у вас запросят PIN-код, попробуйте ввести <em>0000</em>.</p></div> +<div class="paragraph"><p>Установка соединения для загрузки погружений из дайв-компьютеров с интерфейсом Bluetooth, таких, +как <em>Shearwater Petrel</em>, пока что не автоматизирована и в общем случае потребует от вас работы +в коммандной строке. Этот процесс состоит из трех шагов.</p></div> +<div class="ulist"><ul> +<li> +<p> +Включите Bluetooth-адаптер и установите сопряжение с дайв-компьютером +</p> +</li> +<li> +<p> +Установите RFCOMM-соединение +</p> +</li> +<li> +<p> +Загрузите погружения с помощь <em>Subsurface</em> +</p> +</li> +</ul></div> +<div class="paragraph"><p>Убедитесь, что дайв-компьютер в режиме выгрузки. На <em>Shearwater Petrel</em>, <em>Petrel 2</em> и <em>Nerd</em> выберите +в меню <em>Dive Log</em>, затем <em>Upload Log</em>. На дисплее высветится <em>Initializing</em>, <em>Wait PC 3:00</em> и +начнется обратный отсчет. После установки соединения на дисплее высветится <em>Wait CMD …</em> и +отсчет продолжится. Во время загрузки погружений на дисплее отображается надпись <em>Sending</em>, а +затем <em>Sent Dive</em>.</p></div> +<div class="paragraph"><p>Чтобы установить соединение, вам нужно получить полномочия суперпользователя с помощью команд +<code>sudo</code> или <code>su</code>. Для загрузки погружений у пользователя должны быть полномочия. В большинстве +Linux-дистрибутивов пользователю достаточно быть членом группы dialout (что также действительно +и для дайв-компьютеров с USB-интерфейсом). В командой строке введите команду:</p></div> +<div class="paragraph"><p><code>sudo usermod -a -G dialout username</code></p></div> +<div class="paragraph"><p>После этого завершите сеанс и войдите в систему заново.</p></div> +</div> +<div class="sect3"> +<h4 id="_включение_bluetooth_контроллера_и_сопряжение_с_дайв_компьютером">15.3.4. Включение Bluetooth-контроллера и сопряжение с дайв-компьютером</h4> +<div class="paragraph"><p>Попробуйте настроить Bluetooth-контроллер и сопряжение с дайв-компьютером посредством штатного +графического интерфейса операционной системы. После перевода дайв-компьютера в режим выгрузки, +щелкните по значку Bluetooth в области уведомлений и выберите <em>Добавить новое устройство</em>. Дайв- +компьютер должен появиться в списке. Если у вас запросяи пароль, введите 0000. Запишите или скопируйте +MAC-адрес дайв-компьютера, он понадобится позже (адрес имеет вид 00:11:22:33:44:55).</p></div> +<div class="paragraph"><p>Если этот метод не сработал, попробуйте сделать сопряжение из командной строки. Откройте терминал и +используйте <code>hciconfig</code>, чтобы проверить статус Bluetooth-контроллера:</p></div> +<div class="literalblock"> +<div class="content"> +<pre><code>$ hciconfig +hci0: Type: BR/EDR Bus: USB + BD Address: 01:23:45:67:89:AB ACL MTU: 310:10 SCO MTU: 64:8 + *DOWN* + RX bytes:504 acl:0 sco:0 events:22 errors:0 + TX bytes:92 acl:0 sco:0 commands:21 errors:0</code></pre> +</div></div> +<div class="paragraph"><p>Тут мы видим, что контроллер с адресом 01:23:45:67:89:AB подключен как hci0. Его состояние <em>DOWN</em>, +т.е. выключен. Дополнительные контроллеры будут представлены как hci1, и т.д. Теперь необходимо +включить питание контроллера:</p></div> +<div class="literalblock"> +<div class="content"> +<pre><code>sudo hciconfig hci0 up auth+ (enter password when prompted) +hciconfig +hci0: Type: BR/EDR Bus: USB + BD Address: 01:23:45:67:89:AB ACL MTU: 310:10 SCO MTU: 64:8 + *UP RUNNING PSCAN AUTH* + RX bytes:1026 acl:0 sco:0 events:47 errors:0 + TX bytes:449 acl:0 sco:0 commands:46 errors:0</code></pre> +</div></div> +<div class="paragraph"><p>Удостоверьтесь, что статус контроллера теперь содержит <code><em>UP</em>, <em>RUNNING</em> и <em>AUTH</em></code>.</p></div> +<div class="paragraph"><p>Если на компьютере несколько Bluetooth-контроллеров, остальные можно выключиться, чтобы избежать путаницы:</p></div> +<div class="literalblock"> +<div class="content"> +<pre><code>sudo hciconfig hci1 down</code></pre> +</div></div> +<div class="paragraph"><p>Следующий шаг: установить доверенное сопряжение с дайв-компьютером. В дистрибутивах с установленным +пакетом BlueZ (например, Fedora 22) вы можете использовать <code>blutootctl</code>, который имеет собственную подсказку:</p></div> +<div class="literalblock"> +<div class="content"> +<pre><code>bluetoothctl +[NEW] Controller 01:23:45:67:89:AB localhost.localdomain [default] +[bluetooth]# agent on +Agent registered +[bluetooth]# default-agent +Default agent request successful +[bluetooth]# scan on <----теперь переведите дайв-компьютер в режим выгрузки +Discovery started +[CHG] Controller 01:23:45:67:89:AB Discovering: yes +[NEW] Device 00:11:22:33:44:55 Petrel +[bluetooth]# trust 00:11:22:33:44:55 <----вы можете использовать клавишу TAB для автодополнения MAC-адреса +[CHG] Device 00:11:22:33:44:55 Trusted: yes +Changing 00:11:22:33:44:55 trust succeeded +[bluetooth]# pair 00:11:22:33:44:55 +Attempting to pair with 00:11:22:33:44:55 +[CHG] Device 00:11:22:33:44:55 Connected: yes +[CHG] Device 00:11:22:33:44:55 UUIDs: 00001101-0000-1000-8000-0089abc12345 +[CHG] Device 00:11:22:33:44:55 Paired: yes +Pairing successful +[CHG] Device 00:11:22:33:44:55 Connected: no</code></pre> +</div></div> +<div class="paragraph"><p>Если будет запрошен пароль, введите 0000. Ничего страшного в том, что в последней строке содержится +фраза <em>Connected: no</em>, главное тут - сообщение строкой выше <em>Pairing successful</em>.</p></div> +<div class="paragraph"><p>Если в системе установлен пакет BlueZ версии 4 (например, в Ubuntu 12.04 до 15.04), то скорее всего +в ней нет <code>bluetoothctl</code>, но есть утилита <code>bluez-simple-agent</code> или просто <code>simple-agent</code>.</p></div> +<div class="literalblock"> +<div class="content"> +<pre><code>hcitool -i hci0 scanning +Scanning ... + 00:11:22:33:44:55 Petrel + bluez-simple-agent hci0 00:11:22:33:44:55</code></pre> +</div></div> +<div class="paragraph"><p>После сопряжения необходимо установить RFCOMM-соединение.</p></div> +</div> +<div class="sect3"> +<h4 id="_установка_rfcomm_соединения">15.3.5. Установка RFCOMM-соединения</h4> +<div class="paragraph"><p>Для установки RFCOMM-соединения используйте следующую команду:</p></div> +<div class="paragraph"><p><code>sudo rfcomm -i <controller> connect <dev> <bdaddr> [channel]</code></p></div> +<div class="ulist"><ul> +<li> +<p> +<controller> - Bluetooth-контроллер, <code>hci0</code>. +</p> +</li> +<li> +<p> +<dev> - устройство RFCOMM, <code>rfcomm0</code> +</p> +</li> +<li> +<p> +<bdaddr> - MAC-адрес дайв-компьютера, <code>00:11:22:33:44:55</code> +</p> +</li> +<li> +<p> +[channel] - Bluetooth-канал дайв-компьютера, к которому на необходимо подключиться. +</p> +</li> +</ul></div> +<div class="paragraph"><p>Если канал не указать, по умолчанию будет выбран 1. Основываясь на сообщениях наших пользователей, +ниже приведен список каналов для различных моделей дайв-компьютеров:</p></div> +<div class="ulist"><ul> +<li> +<p> +<em>Shearwater Petrel 1</em>: канал 1 +</p> +</li> +<li> +<p> +<em>Shearwater Petrel 2</em>: канал 5 +</p> +</li> +<li> +<p> +<em>Shearwater Nerd</em>: канал 5 +</p> +</li> +<li> +<p> +<em>Heinrichs-Weikamp OSTC Sport</em>: канал 1 +</p> +</li> +</ul></div> +<div class="paragraph"><p>Таким образом, чтобы подключить <em>Shearwater Petrel 2</em>, переведите его в режим выгрузки и введите команду:</p></div> +<div class="literalblock"> +<div class="content"> +<pre><code>sudo rfcomm -i hci0 connect rfcomm0 00:11:22:33:44:55 5 (если вас запросят пароль, введите 0000)</code></pre> +</div></div> +<div class="paragraph"><p>В ответ вы должны получить сообщение:</p></div> +<div class="literalblock"> +<div class="content"> +<pre><code>Connected /dev/rfcomm0 to 00:11:22:33:44:55 on channel 5 +Press CTRL-C for hangup</code></pre> +</div></div> +<div class="paragraph"><p>Для подключения _Shearwater Petrel 1+ или <code>HW OSTC Sport</code>, переведите компьютер в режим загрузки и введите команду:</p></div> +<div class="literalblock"> +<div class="content"> +<pre><code>sudo rfcomm -i hci0 connect rfcomm0 00:11:22:33:44:55 (если вас запросят пароль, введите 0000) +Connected /dev/rfcomm0 to 00:11:22:33:44:55 on channel 1 +Press CTRL-C for hangup</code></pre> +</div></div> +<div class="paragraph"><p>Если номер Bluetooth-канала неизвестен, либо указанный номер не работает, определить его вам поможет +команда <code>sdptool records</code>. Ниже приведен её вывод для дайв-компьютера <em>Shearwater Petrel 2</em>:</p></div> +<div class="literalblock"> +<div class="content"> +<pre><code>sdptool -i hci0 records 00:11:22:33:44:55 +Service Name: Serial Port +Service RecHandle: 0x10000 +Service Class ID List: + "Serial Port" (0x1101) + Protocol Descriptor List: + "L2CAP" (0x0100) + "RFCOMM" (0x0003) + Channel: 5</code></pre> +</div></div> +<div class="paragraph"><p>Если ваш дайв-компьютер не в списке, или номер канала отличается, пожалуйста, сообщите об этом +разработчикам <em>Subsurface</em> через форум пользователей или список рассылки <em>subsurface@subsurface-divelog.org</em>.</p></div> +</div> +<div class="sect3"> +<h4 id="_загрузка_погружений_в_subsurface">15.3.6. Загрузка погружений в Subsurface</h4> +<div class="paragraph"><p>После установки RFCOMM-соединения и пока идет обратный отсчет режима выгрузки на дайв-компьютере, +перейдите в <em>Subsurface</em>, выберите <em>Импорт → Импорт из дайв-компьютера</em>, укажите производителя +(например, <em>Shearwater</em>), модель (<em>Petrel</em>), устройство или точку монтирования (<em>/dev/rfcomm0</em>) и +и нажмите <em>Загрузить</em>.</p></div> +</div> +</div> +</div> +</div> +<div class="sect1"> +<h2 id="APPENDIX_B">16. ПРИЛОЖЕНИЕ Б: Настройка дайв-компьютеров для импорта</h2> +<div class="sectionbody"> +<div class="sect2"> +<h3 id="S_ImportUemis">16.1. Импорт погружений из Uemis Zurich</h3> +<div class="admonitionblock"> +<table><tr> +<td class="icon"> +<img src="images/icons/iumis.jpg" alt="Замечание" /> +</td> +<td class="content"><em>Subsurface</em> импортирует информацию, хранящуюся в SDA (внутренняя файловая +система Uemis), включая данные о точках погружения и снаряжении. Информация о +напарниках в данный момент недоступна. Сопряжение схоже с USB-компьютерами (и +при этом Uemis заряжается от USB-порта). Главное отличие состоит в том, что +вам нужно указывать не имя порта, а точку монтирования файловой системы +UEMISSDA. В Windows это буква диска (зачастую E: или F:), в Mac это +<em>/Volumes/UEMISSDA</em>, а в Linux это зависит от дистрибутива. Например, в Fedora +это <em>/var/run/media/<имя<em>пользователя>/UEMISSDA</em>. В любом случае _Subsurface</em> +предложить вам варианты в выпадающем списке на диалоге импорта.</td> +</tr></table> +</div> +<div class="paragraph"><p>После того, как вы указали точку монтирования, выполните загрузку. Uemis +Zurich имеет одно ограничение (это ограничение прошивки дайв-компьютера, а не +<em>Subsurface</em>) - невозможно загрузить более 40-50 погружений за один раз, +происходит переполнение SDA. Обычно это происходит при первой загрузке. Если +вы импортируете погружения ежедневно или даже после поездки, емкости SDA +вполне достаточно. +Если <em>Subsurface</em> показывает сообщение о переполнении памяти дайв-компьютера, +решение достаточно простое: отключите SDA, выключите и включите +дайв-компьютер, и подключите заново. Начните импорт заново и <em>Subsurface</em> +продолжит загрузку с того места где она прервалась. Возможно вам придется +повторить процедуру несколько раз в зависимости от того, сколько погружений +записано в памяти Uemis Zurich.</p></div> +</div> +<div class="sect2"> +<h3 id="S_ImportingGalileo">16.2. Импорт погружений из Uwatec Galileo</h3> +<div class="admonitionblock"> +<table><tr> +<td class="icon"> +<img src="images/icons/Galileo.jpg" alt="Замечание" /> +</td> +<td class="content">Компьютеры Uwatec Galileo используют беспроводной инфракрасный канал +связи (IrDA). Со стороны настолько ПК используется USB-брелок с поддержкой +протокола последовательного обмена через IrDA (SIR) на контроллере MSC7780 +производства компании MosChip. +В Linux ядро изначально поддерживает протокол последовательного обмена через +IrDA, однако вам придется дополнительно загрузить драйвер для коммуникации с +дайв-компьютером. Самый простой путь: установить пакет irda-tools, +предварительно загрузив его с сайта +<a href="http://irda.sourceforge.net/docs/startirda.html">Linux IrDA Project</a>. После +установки, пользователем <strong>root</strong> выполните в консоли команду <code>irattach irda0</code>.</td> +</tr></table> +</div> +<div class="paragraph"><p>После этого <em>Subsurface</em> распознает дайв-компьютер и вы можете выполнить +импорт.</p></div> +<div class="paragraph"><p>С Windows ситуация схожая. Драйвера для контроллера MCS7780 доступны на +нескольких интернет-сайтах, например на +<a href="http://www.drivers-download.com/Drv/MosChip/MCS7780/">www.drivers-download.com</a>. IrDA драйверы для +Windows для компьютеров также могут быть загружены с веб-сайта ScubaPro со страницы загрузки +программного обеспечения ScubaPro SmartTrak.</p></div> +<div class="paragraph"><p>Для Apple Mac, IrDA-соединение через MCS7780 невозможно для версий OSX 10.6 и +выше.</p></div> +</div> +<div class="sect2"> +<h3 id="S_ImportingDR5">16.3. Импорт погружений из Heinrichs Weikamp DR5</h3> +<div class="admonitionblock"> +<table><tr> +<td class="icon"> +<img src="images/icons/HW_DR5.jpg" alt="Замечание" /> +</td> +<td class="content">Когда этот дайв-компьютер подключен как USB-диск, он сохраняет отдельный +UDDF-файл для каждого погружения. Выделите все файл погружения для импорта или +открытия. +Примечание: DR5 не сохраняет ни градиент-факторы, ни информацию а +деко-обязательствах, поэтому <em>Subsurface</em> не может отобразить ее. +Отрегулируйте значения градиент-фактора в <em>Настройках_ _Subsurface</em>, чтобы +увидеть деко-обязательства на профиле, но учтите, что они вероятнее всего +будут отличаться от тех, что показывает DR5.</td> +</tr></table> +</div> +</div> +<div class="sect2"> +<h3 id="S_ImportingXDeep">16.4. Импорт погружений из xDEEP BLACK</h3> +<div class="admonitionblock"> +<table><tr> +<td class="icon"> +<img src="images/icons/HW_xdeepblack.jpg" alt="Замечание" /> +</td> +<td class="content">Каждое погружение должно быть сохранено в файл формата UDDF, используя пункт меню "Export UDDF". +Если дайв-компьютер подключен как USB-устройство, то UDDF-файлы должны быть доступны в директории LOGBOOK. +Примечание: xDEEP BLACK сохраняет время NDL, но не хранит информации о градиент-факторах и декомпрессии, +и следовательно <em>Subsurface</em> не сможет отобразить их. Установите значения градиент-фактора в <em>Настройках_ +(вкладка _Профиль</em>), чтобы отобразить декомпрессионный потолок на профиле погружения, но учтите, что +вероятнее всего деко-обязательства, рассчитанные в <em>Subsurface</em> наверняка будут отличаться от тех, что +показывает xDEEP BLACK.</td> +</tr></table> +</div> +</div> +<div class="sect2"> +<h3 id="_импорт_погружений_из_shearwater_predator_petrel_nerd_используя_bluetooth">16.5. Импорт погружений из Shearwater Predator/Petrel/Nerd используя Bluetooth</h3> +<div class="admonitionblock"> +<table><tr> +<td class="icon"> +<img src="images/icons/predator.jpg" alt="Замечание" /> +</td> +<td class="content">Инструкции по загрузке погружений через Bluetooth приведены выше в главе <a href="#S_Bluetooth"><em>Подключение _Subsurface</em> к дайв-компьютеру через Bluetooth_</a></td> +</tr></table> +</div> +</div> +<div class="sect2"> +<h3 id="S_PoseidonMkVI">16.6. Импорт погружений из Poseidon MkVI Discovery</h3> +<div class="admonitionblock"> +<table><tr> +<td class="icon"> +<img src="images/MkVI.jpeg" alt="Замечание" /> +</td> +<td class="content">Загрузка журналов погружений из MkVI осуществляется с помощью специального коммуникационного +адаптера и программного обеспечения <em>Poseidon PC Configuration Software</em>, предоставляемых при +покупке MKVI. Это программное обеспечение работает в ОС Windows и позволяет настраивать +оборудование и хранить журналы погружений. Связь между настольным и дайв-компьютером +осуществляется через инфракрасный порт. Одномоментно можно загрузить данные только одного +погружения, состоящие из трех файлов:</td> +</tr></table> +</div> +<div class="ulist"><ul> +<li> +<p> +Конфигурация настроек и ключевые параметры погружения (файл с расширением .txt) +</p> +</li> +<li> +<p> +Детали погружения (файл с расширением .csv) +</p> +</li> +<li> +<p> +Собственный формат журнала погружения (файл с расширение .cvsr). +</p> +</li> +</ul></div> +<div class="paragraph"><p><em>Subsurface</em> использует файлы с расширением .txt и .csv для импорта погружения.</p></div> +</div> +<div class="sect2"> +<h3 id="_импорт_погружений_из_apd_inspiration_ccr">16.7. Импорт погружений из APD Inspiration CCR</h3> +<div class="admonitionblock"> +<table><tr> +<td class="icon"> +<img src="images/APDComputer.jpg" alt="Замечание" /> +</td> +<td class="content">Журналы погружений APD Inspiration и похожих CCR дайв-компьютеров можно загрузить, используя +специальный коммуникационный адаптер и программное обеспечение <em>AP Communicator</em>, предоставляемые +при покупке оборудования. Просмотреть журналы на платформах Windows и Mac/OS можно, используя +<em>AP Log Viewer</em>. Вы также можете получить доступ к этим погружениям и из <em>Subsurface</em>. Для +импорта погружений APD Inspiration необходимо выполнить следующие шаги:</td> +</tr></table> +</div> +<div class="ulist"><ul> +<li> +<p> +Загрузите погружение используя <em>AP Communicator</em>. +</p> +</li> +<li> +<p> +Откройте погружение в <em>AP Log Viewer</em>. +</p> +</li> +<li> +<p> +Выберите вкладку "<em>Data</em>" в верхней части экрана. +</p> +</li> +<li> +<p> +На экране необработанных данных нажмите на "<em>_Copy to Clipboard</em>". +</p> +</li> +<li> +<p> +Откройте текстовый редактор, например, Notepad (Windows), или TextWrangler (Mac). +</p> +</li> +<li> +<p> +Вставьте данные из буфера обмена в редактор и сохраните файл с расширением <em>.APD</em> +</p> +</li> +<li> +<p> +Находясь в <em>Subsurface</em>, выберите в меню <em>Импорт → Импорт журналов</em>, чтобы открыть + <a href="#Unified_import">диалог универсального импорта</a>. +</p> +</li> +<li> +<p> +В окне в правой нижней части выберите тип "APD-файлы" +</p> +</li> +<li> +<p> +В списке файлов выберите тот, что вы сохранили ранее из текстового редактора. Будет представлено + окно импорта. +</p> +</li> +<li> +<p> +Внесите по необходимости изменения в параметры импорта, как описано в главе <a href="#S_ImportingCSVDives">Импорт CSV-файлов</a>. +</p> +</li> +</ul></div> +<div class="imageblock" style="text-align:center;"> +<div class="content"> +<img src="images/APD_CSVimportF22.jpg" alt="Рисунок: Импорт файлов APD log viewer" /> +</div> +</div> +<div class="ulist"><ul> +<li> +<p> +Выпадающий список в левом верхнем углу позволяет указать журнал какого именно компьютера необходимо + импортировать. По умолчанию это первый компьютер (DC1). Вы можете последовательно импортировать + данные погружения сначала для DC1, а потом для DC2 (при просмотре погружения в <em>Subsurface</em> вы можете + переключаться между дайв-компьютерами, выбрав в главном меню <em>Вид → След. компьютер</em>). +</p> +</li> +<li> +<p> +Нажмите кнопку <em>Ок</em>, чтобы выполнить импорт. +</p> +</li> +</ul></div> +<div class="paragraph"><p>Журнал погружения APD должен появиться в <em>Subsurface</em>. Деко-потолок, сгенерированный Inspiration, +можно посмотреть на профиле, выбрав соответствующую кнопку на панели слева от профиля погружения. +Оборудование APD не записывает данные о давлении в баллонах, но вы можете указать их самостоятельно +на вкладке <em>Снаряжение</em>.</p></div> +</div> +</div> +</div> +<div class="sect1"> +<h2 id="APPENDIX_C">17. ПРИЛОЖЕНИЕ В: Импорт журнала погружений из сторонних программ</h2> +<div class="sectionbody"> +<div class="paragraph"><p>Импорт погружений из сторонних программ ведения журналов достаточно прост и +выполняется с помощью универсального импорта, доступного из главного +меню <em>Импорт → Импорт журнала</em>. Подробнее эта функциональность описана в +<a href="#Unified_import">отдельной главе</a>. +Однако в некоторых случаях может потребоваться два шага:</p></div> +<div class="olist arabic"><ol class="arabic"> +<li> +<p> +Экспорт "чужого" журнала в формат, который может быть разобран +<em>Subsurface</em>. +</p> +</li> +<li> +<p> +Импорт этого файла в <em>Subsurface</em>. +</p> +</li> +</ol></div> +<div class="paragraph"><p>В этом приложении мы попытаемся рассказать как экспортировать погружения из +сторонних программ. В большей части это касается Linux и Windows.</p></div> +<div class="sect2"> +<h3 id="S_ImportingDivesSuunto">17.1. Экспорт погружений из <strong>Suunto Divemanager (DM3,DM4 и DM5)</strong></h3> +<div class="admonitionblock"> +<table><tr> +<td class="icon"> +<img src="images/icons/suuntologo.jpg" alt="Замечание" /> +</td> +<td class="content">Divemanager 3 (DM3) - старая версия журнала погружений. Современные +дайв-компьютеры Suunto используют Divemanager версий 4 или 5 (DM4 или DM5). Эти две версии +используют разные подходы и имена файлов для экспорта погружений.</td> +</tr></table> +</div> +<div class="paragraph"><p><strong>Divemanager 3 (DM3):</strong></p></div> +<div class="olist arabic"><ol class="arabic"> +<li> +<p> +Запустите <em>Suunto Divemanager 3</em> и войдите под пользователем, для которого +есть погружения в журнале. +</p> +</li> +<li> +<p> +Не запускайте импорт погружений из дайв-компьютера. +</p> +</li> +<li> +<p> +В навигационной панели в левой части окна программы выберите погружения. +</p> +</li> +<li> +<p> +Используйте мышь и клавиши Ctrl и Shift для выбора одиночных и нескольких +погружений. +</p> +</li> +<li> +<p> +Для выбранных погружений используйте пункт меню <em>File → Export</em> +</p> +</li> +<li> +<p> +Во всплывающем окне есть одно единственное поле <em>Export Path</em> +</p> +<div class="ulist"><ul> +<li> +<p> +Нажмите кнопку Обзор рядом в этим полем +</p> +<div class="ulist"><ul> +<li> +<p> +вам будет представлено окно файлового проводника +</p> +</li> +<li> +<p> +перейдите в директорию для сохранения файла Divelog.SDE +</p> +</li> +<li> +<p> +при желании измените имя файла +</p> +</li> +<li> +<p> +нажмите <em>Сохранить</em> +</p> +</li> +</ul></div> +</li> +<li> +<p> +Вернувшись во всплывающее окно экспорта, нажмите кнопку <em>Export</em> +</p> +</li> +</ul></div> +</li> +<li> +<p> +Погружения экспортированы в файл Divelog.SDE. +</p> +</li> +</ol></div> +<div class="paragraph"><p><strong>Divemanager 4 (DM4) и Divemanager 5 (DM5):</strong></p></div> +<div class="paragraph"><p>Чтобы экспортировать данные журнала DM4 и DM5, вам необходимо узнать +местоположение базы данных, в которой хранятся погружения. Вы можете +использовать как основную, так и резервную копию базы. Ниже описаны оба варианта:</p></div> +<div class="paragraph"><p>Местонахождение базы данных Suunto DM4 (или DM5):</p></div> +<div class="olist arabic"><ol class="arabic"> +<li> +<p> +Запустите Suunto DM4/DM5 +</p> +</li> +<li> +<p> +Выберите в меню <em>Help → About</em> +</p> +</li> +<li> +<p> +Нажмите <em>Copy</em> после текста <em>Copy log folder path to clipboard</em> +</p> +</li> +<li> +<p> +Запустите проводник Windows +</p> +</li> +<li> +<p> +Вставьте текст из буфера обмена в строку навигации проводника +</p> +</li> +<li> +<p> +Файл базы данных называется DM4.db +</p> +</li> +</ol></div> +<div class="paragraph"><p>Создание резервной копии Suunto DM4:</p></div> +<div class="olist arabic"><ol class="arabic"> +<li> +<p> +Запустите Suunto DM4/DM5 +</p> +</li> +<li> +<p> +Выберите в меню <em>File - Create backup</em> +</p> +</li> +<li> +<p> +В диалоге выбора файла укажите путь и название резервной копии, в этом +примере мы используем расширение .bak по умолчанию +</p> +</li> +<li> +<p> +Нажмите <em>Save</em> +</p> +</li> +<li> +<p> +Погружения сохранены в файл DM4.bak (или DM5.bak) +</p> +</li> +</ol></div> +</div> +<div class="sect2"> +<h3 id="_экспорт_погружений_из_atomic_logbook">17.2. Экспорт погружений из Atomic Logbook</h3> +<div class="admonitionblock" id="Atomic_Export"> +<table><tr> +<td class="icon"> +<img src="images/icons/atomiclogo.jpg" alt="Замечание" /> +</td> +<td class="content">Компания Atomic Aquatics предлагает собственное программное обеспечение Atomic Logbook для платформы +Windows. Оно позволяет загружать журналы погружений с компьютеров Cobalt и Cobalt 2. Журнал хранится +в базе данных SQLite в файле C:\ProgramData\AtomicsAquatics\Cobalt-Logbook\Cobalt.db. Этот файл +может быть напрямую импортирован в <em>Subsurface</em>.</td> +</tr></table> +</div> +</div> +<div class="sect2"> +<h3 id="Mares_Export">17.3. Экспорт погружений из Mares Dive Organiser V2.1</h3> +<div class="admonitionblock"> +<table><tr> +<td class="icon"> +<img src="images/icons/mareslogo.jpg" alt="Замечание" /> +</td> +<td class="content">Mares Dive Organiser работает исключительно под управлением ОС Windows. Журнал +погружений хранится в фрмате SQL Compact Edition database в файле с +расширением <em>.sdf</em>. База данных содержит данные о всех зарегистрированных +дайверах на данном ПК и о всех используемых дайв-компьютерах Mares. На +сегодняшний день самый надежный способ получить копию журнала - +экспортировать погружения в другой формат, распознаваемый <em>Subsurface</em>.</td> +</tr></table> +</div> +<div class="olist arabic"><ol class="arabic"> +<li> +<p> +Находясь в Dive Organiser, выберите в главном меню <em>Database → Backup</em> и +создайте резервную копию базы данных на рабочем столе. Это создаст ZIP-архив с +именем DiveOrganiserxxxxx.dbf. +</p> +</li> +<li> +<p> +Переименуйте файл в DiveOrganiserxxxxx.zip. Внутри ZIP-архива находится +файл <em>DiveOrganiser.sdf</em>. +</p> +</li> +<li> +<p> +Извлеките файл с расширением <em>.sdf</em> на рабочий стол вашего ПК. +</p> +</li> +<li> +<p> +Пароль для доступа к ZIP-архиву <em>mares</em>. +</p> +</li> +</ol></div> +</div> +<div class="sect2"> +<h3 id="S_ImportingDivinglog">17.4. Экспорт погружений из <strong>DivingLog 5.0 и 6.0</strong></h3> +<div class="admonitionblock"> +<table><tr> +<td class="icon"> +<img src="images/icons/divingloglogo.jpg" alt="Замечание" /> +</td> +<td class="content">Лучший способ перенести журнал погружений из DivingLog в <em>Subsurface</em> - полная конвертация базы +данных. Прочие форматы не содержат все детали погружений, такие как события замены газов, единицы +измерения и т.п. При конвертации базы данных, вся эта информация будет доступна.</td> +</tr></table> +</div> +<div class="paragraph"><p>Для переноса всех файлов из DivingLog в <em>Subsurface</em> выполните следующие шаги:</p></div> +<div class="olist arabic"><ol class="arabic"> +<li> +<p> +В главном меню DivingLog выберите <em>File → Export → SQLite</em> +</p> +</li> +<li> +<p> +Нажмите на кнопку <em>Установки</em> +</p> +</li> +<li> +<p> +Установите <em>RTF2Plaintext</em> в значение <em>true</em> +</p> +</li> +<li> +<p> +Закройте диалоговое окно <em>Установки</em> +</p> +</li> +<li> +<p> +Нажмите кнопку Экспорт и укажите имя файла +</p> +</li> +</ol></div> +<div class="paragraph"><p>После выполнения этих шагов, откройте сохраненный файл с помощью <em>Subsurface</em>, все погружения будут +преобразованы в наш собственный формат. Последним шагом не забудьте сохранить журнал.</p></div> +</div> +</div> +</div> +<div class="sect1"> +<h2 id="S_Appendix_D">18. ПРИЛОЖЕНИЕ Г: Экспорт электронных таблиц в CSV-формат</h2> +<div class="sectionbody"> +<div class="paragraph"><p>Многие дайверы ведут журнал погружений в каком-либо электронном формате, зачастую в виде таблицы +с разнообразными информационными полями. Такие журналы могут быть импортированы в <em>Subsurface</em>, но +прежде их надо конвертировать в формат CSV. +Эта глава описывает шаги по конвертации журнала из электронных таблиц в CSV-формат для последующего +импорта в <em>Subsurface</em>. Создание CSV-файла довольно тривиальная задача, хотя это процедура различается +для разных программ для работы с электронными таблицами.</p></div> +<div class="paragraph"><p>Первым шагом вам нужно правильно организовать данные в таблице так, что первая строка содержала +названия (заголовки) каждой из колонок и информация по каждому погружению хранилась в одной строке. +<em>Subsurface</em> поддерживает множество полей (№ погружения, Дата, Время, Длительность, Напарник, Грузы, +Метки и Примечания). Вы можете организовать данные, следуя простым правилам:</p></div> +<div class="olist arabic"><ol class="arabic"> +<li> +<p> +Дата. Используйте один из форматов: yyyy-mm-dd, dd.mm.yyyy, mm/dd/yyyy +</p> +</li> +<li> +<p> +Длительность. Формат должен быть вида мин:сек. +</p> +</li> +<li> +<p> +Система мер. Нужно использовать только одну систему (т.е. нельзя использовать фунты и градусы Цельсия) +</p> +</li> +<li> +<p> +Метки и партнеры. Значения должны быть разделены запятой. +</p> +</li> +<li> +<p> +GPS-координаты. Следует использоваться десятичные доли градусов, т.е. e.g. 30.22496 30.821798 +</p> +</li> +</ol></div> +<div class="sect2"> +<h3 id="_em_libreoffice_calc_em_и_em_openoffice_calc_em">18.1. <em>LibreOffice Calc</em> и <em>OpenOffice Calc</em></h3> +<div class="paragraph"><p>Эти программы для работы с электронными таблицами являются частью офисных пакетов с открытым кодом. +Работы с <em>LibreOffice</em> и <em>OpenOffice</em> очень схожа. Формат времени должен быть вида минуты:секунды - [mm]:ss, а формат даты одним из yyyy-mm-dd, dd.mm.yyyy, mm/dd/yyyy. Типичный журнал может выгядеть так:</p></div> +<div class="imageblock" style="text-align:center;"> +<div class="content"> +<img src="images/LOffice_spreadsheetdata.jpg" alt="Рисунок: Электронная таблица" /> +</div> +</div> +<div class="paragraph"><p>Для экспорта файла CSV из LibreOffice в меню выберите <em>Файл → Сохранить как</em>. В появившемся диалоге выберите тип файла <em>Текст CSV (.csv)</em> и выберите опцию <em>Редактировать настройки фильтра</em>.</p></div> +<div class="imageblock" style="text-align:center;"> +<div class="content"> +<img src="images/LOffice_save_as_options.jpg" alt="Рисунок: Сохранение CSV-файла" /> +</div> +</div> +<div class="paragraph"><p>После нажатия на кнопку <em>Сохранить</em>, выберите <em>Tab</em> в качестве разделителя полей, чтобы избежать конфликтов при использовании запятой в качестве десятичного разделителя, и нажмите <em>OK</em>.</p></div> +<div class="imageblock" style="text-align:center;"> +<div class="content"> +<img src="images/LOffice_field_options.jpg" alt="Рисунок: Настройки фильтра CSV" /> +</div> +</div> +<div class="paragraph"><p>Импортируйте только что сохраненный CSV-файл как описано в главе <a href="#S_ImportingCSVDives">Импорт погружений в CSV-формате</a>.</p></div> +</div> +<div class="sect2"> +<h3 id="_microsoft_em_excel_em">18.2. Microsoft <em>Excel</em></h3> +<div class="paragraph"><p><em>Excel</em> не предоставляет возможности указать разделитель полей (в руководстве Microsoft он называется +<em>разделитель списка</em>); сделать это можно из <em>Панели управления</em>. После изменения символа-разделителя, +его будут использовать все программы на компьютере. Вы всегда можете вернуться к предыдущему значению, +выполнив следующую процедуру:</p></div> +<div class="ulist"><ul> +<li> +<p> +В Windows нажмите кнопку <strong>Пуск</strong> и выберите <em>Панель управления</em> в правой части окна. +</p> +</li> +<li> +<p> +Выберите <em>Региональные настройки</em>. +</p> +</li> +<li> +<p> +Выполните следующее: +</p> +<div class="ulist"><ul> +<li> +<p> +Для Windows 7, выберите вкладку <em>Формат) и нажмите _Настроить</em> +</p> +</li> +<li> +<p> +Для Windows XP, выберите <em>Параметры региона</em> и нажмите <em>Настроить</em> +</p> +</li> +</ul></div> +</li> +<li> +<p> +Введите новый символ-разделитель в поле <em>Разделитель списка</em>. Чтобы указать символ табуляции, введите слово TAB. +</p> +</li> +<li> +<p> +Последовательно нажмите кнопку <em>ОК</em> дважды. +</p> +</li> +</ul></div> +<div class="paragraph"><p>Ниже приведен внешний вид <em>Панели управления</em>:</p></div> +<div class="imageblock" style="text-align:center;"> +<div class="content"> +<img src="images/Win_SaveCSV2.jpg" alt="Рисунок: Разделитель списков в Windows" /> +</div> +</div> +<div class="paragraph"><p>Чтобы экспортировать журнал погружений в CSV формат:</p></div> +<div class="paragraph"><p>Откройте журнал в <em>Excel</em>, нажмите на круглую кнопку с логотипом Windows в верхнем левом углу и выберите <em>Сохранить как</em></p></div> +<div class="imageblock" style="text-align:center;"> +<div class="content"> +<img src="images/Win_SaveCSV1.jpg" alt="Рисунок: сохранить как в Excel" /> +</div> +</div> +<div class="paragraph"><p>Нажимайте непосредственно на пункт <em>Сохранить как</em>, а не на стрелочку справа от него. Это откроет диалоговое окно для сохранения таблицы в альтернативном формате. Из выпадающего списка в нижней части диалога выберите тип CSV, укажите папку для сохранения.</p></div> +<div class="imageblock" style="text-align:center;"> +<div class="content"> +<img src="images/Win_SaveCSV3.jpg" alt="Рисунок: диалоговое окна сохранения CSV-файла в Excel" /> +</div> +</div> +<div class="paragraph"><p>Нажмите кнопку <em>Сохранить</em>. Импортируйте только что сохраненный CSV-файл как описано в главе <a href="#S_ImportingCSVDives">Импорт погружений в CSV-формате</a>.</p></div> +</div> +</div> +</div> +<div class="sect1"> +<h2 id="S_APPENDIX_E">19. ПРИЛОЖЕНИЕ Д: Создание собственных шаблонов печати</h2> +<div class="sectionbody"> +<div class="paragraph"><p><em>Subsurface</em> предоставляет механизм по созданию и изменению шаблонов для печати погружений, что +позволяет гибко менять положение информации на странице. Шаблоны используют HTML и набор инструкций +библиотеки Grantlee.</p></div> +<div class="paragraph"><p>Доступ к шаблонам осуществляется из диалога печати (см. рисунок В ниже).</p></div> +<div class="imageblock" style="text-align:center;"> +<div class="content"> +<img src="images/Print1_f22.jpg" alt="Рисунок: Диалог печати" /> +</div> +</div> +<div class="paragraph"><p>Кнопки под выпадающим списком шаблонов позволяют <em>Редактировать</em>, <em>Удалить</em>, выполнить <em>Импорт</em> и +<em>Экспорт</em>. Новые или измененные шаблоны хранятся в той же директории, что и журнал, с которым вы работаете +в данный момент. Чтобы изменить существующий шаблон, выберите его названиек в списке и нажмите +кнопку <em>Редактировать</em>.</p></div> +<div class="paragraph"><p>Окно редактирования шаблона состоит из трех вкладок:</p></div> +<div class="imageblock" style="text-align:center;"> +<div class="content"> +<img src="images/Template1_f22.jpg" alt="Рисунок: окно редактирования шаблона" /> +</div> +</div> +<div class="paragraph"><p>1) Вкладка <em>Стиль</em> (рисунок <strong>А</strong> выше) управляет шрифтами, междстрочным интервалом и палитрой цветов.</p></div> +<div class="paragraph"><p>2) Вкладка <em>Цвета</em> (рисунок <strong>В</strong> выше) позволяет переопределить цвета шаблона</p></div> +<div class="paragraph"><p>3) Вкладка <em>Шаблон</em> (рисунок ниже) дает вам возможность описать шаблон на языке HTML с использованием + примитивов библиотеки Grantlee.</p></div> +<div class="imageblock" style="text-align:center;"> +<div class="content"> +<img src="images/Template2_f22.jpg" alt="Рисунок: Вкладка редактирования шаблона" /> +</div> +</div> +<div class="paragraph"><p>Вы можете адаптировать существующие шаблоны под свои нужды и сохранить их в директории журнала погружений. +После окончания редактирования, используйте функцию <em>Экспорт</em>, чтобы сохранить шаблон с новым именем.</p></div> +<div class="paragraph"><p>Чтобы шаблон правильно отображался, в нем должны присутствовать следующие элементы:</p></div> +<div class="sect2"> +<h3 id="_главный_цикл_погружений">19.1. Главный цикл погружений</h3> +<div class="paragraph"><p><em>Subsurface</em> экспортирует в <em>Grantlee</em> список погружений под именем <strong>dives</strong>. Для итерации по погружениям:</p></div> +<div class="literalblock"> +<div class="title">template.html</div> +<div class="content"> +<pre><code> {% for dive in dives %} + <h1> {{ dive.number }} </h1> + {% endfor %}</code></pre> +</div></div> +<div class="literalblock"> +<div class="title">output.html</div> +<div class="content"> +<pre><code> <h1> 1 </h1> + <h1> 2 </h1> + <h1> 3 </h1></code></pre> +</div></div> +<div class="paragraph"><p>Дополнительную информация о <em>Grantlee</em> вы можете найти <a href="http://www.grantlee.org/apidox/for_themers.html">здесь</a>.</p></div> +</div> +<div class="sect2"> +<h3 id="_переменные_доступные_в_grantlee">19.2. Переменные, доступные в Grantlee</h3> +<div class="paragraph"><p><em>Subsurface</em> экспортирует только часть информации о погружении:</p></div> +<div class="tableblock"> +<table rules="all" +width="100%" +frame="border" +cellspacing="0" cellpadding="4"> +<col width="50%" /> +<col width="50%" /> +<tbody> +<tr> +<td align="left" valign="top"><p class="table"><strong>Название</strong></p></td> +<td align="left" valign="top"><p class="table"><strong>Описание</strong></p></td> +</tr> +<tr> +<td align="left" valign="top"><p class="table">number</p></td> +<td align="left" valign="top"><p class="table">(<strong>int</strong>) номер погружения</p></td> +</tr> +<tr> +<td align="left" valign="top"><p class="table">id</p></td> +<td align="left" valign="top"><p class="table">(<strong>int</strong>) уникальный ID дайва, должен использоваться для получения профиляe</p></td> +</tr> +<tr> +<td align="left" valign="top"><p class="table">date</p></td> +<td align="left" valign="top"><p class="table">(<strong>string</strong>) дата погружения</p></td> +</tr> +<tr> +<td align="left" valign="top"><p class="table">time</p></td> +<td align="left" valign="top"><p class="table">(<strong>string</strong>) время погружения</p></td> +</tr> +<tr> +<td align="left" valign="top"><p class="table">location</p></td> +<td align="left" valign="top"><p class="table">(<strong>string</strong>) местоположение</p></td> +</tr> +<tr> +<td align="left" valign="top"><p class="table">duration</p></td> +<td align="left" valign="top"><p class="table">(<strong>string</strong>) длительность</p></td> +</tr> +<tr> +<td align="left" valign="top"><p class="table">depth</p></td> +<td align="left" valign="top"><p class="table">(<strong>string</strong>) глубина погружения</p></td> +</tr> +<tr> +<td align="left" valign="top"><p class="table">divemaster</p></td> +<td align="left" valign="top"><p class="table">(<strong>string</strong>) информация о дайв-мастере</p></td> +</tr> +<tr> +<td align="left" valign="top"><p class="table">buddy</p></td> +<td align="left" valign="top"><p class="table">(<strong>string</strong>) информация о партнерах</p></td> +</tr> +<tr> +<td align="left" valign="top"><p class="table">airTemp</p></td> +<td align="left" valign="top"><p class="table">(<strong>string</strong>) температура воздуха</p></td> +</tr> +<tr> +<td align="left" valign="top"><p class="table">waterTemp</p></td> +<td align="left" valign="top"><p class="table">(<strong>string</strong>) температура воды</p></td> +</tr> +<tr> +<td align="left" valign="top"><p class="table">notes</p></td> +<td align="left" valign="top"><p class="table">(<strong>string</strong>) примечания к погружению</p></td> +</tr> +<tr> +<td align="left" valign="top"><p class="table">rating</p></td> +<td align="left" valign="top"><p class="table">(<strong>int</strong>) рейтинг погружения (от 0 до 5)</p></td> +</tr> +<tr> +<td align="left" valign="top"><p class="table">sac</p></td> +<td align="left" valign="top"><p class="table">(<strong>string</strong>) значение SAC</p></td> +</tr> +<tr> +<td align="left" valign="top"><p class="table">tags</p></td> +<td align="left" valign="top"><p class="table">(<strong>string</strong>) все метки погружения, перечисленные через запятую</p></td> +</tr> +<tr> +<td align="left" valign="top"><p class="table">gas</p></td> +<td align="left" valign="top"><p class="table">(<strong>string</strong>) используемые баллоны</p></td> +</tr> +</tbody> +</table> +</div> +<div class="paragraph"><p><em>Subsurface</em> также экспортирует структуру <strong>template_options</strong>. Эти данные должны использоваться +в определении стилей CSS. В таблице ниже приведены доступные переменные:</p></div> +<div class="tableblock"> +<table rules="all" +width="100%" +frame="border" +cellspacing="0" cellpadding="4"> +<col width="50%" /> +<col width="50%" /> +<tbody> +<tr> +<td align="left" valign="top"><p class="table"><strong>Название</strong></p></td> +<td align="left" valign="top"><p class="table"><strong>Описание</strong></p></td> +</tr> +<tr> +<td align="left" valign="top"><p class="table">font</p></td> +<td align="left" valign="top"><p class="table">(<strong>string</strong>) семество шрифтов</p></td> +</tr> +<tr> +<td align="left" valign="top"><p class="table">borderwidth</p></td> +<td align="left" valign="top"><p class="table">(<strong>int</strong>) значение border-width динамически высчитывается как 0.1% от ширины страницы, минимум 1px</p></td> +</tr> +<tr> +<td align="left" valign="top"><p class="table">font_size</p></td> +<td align="left" valign="top"><p class="table">(<strong>double</strong>) размер шрифта в vw (viewport width), в диапазоне от 1.0 до 2.0</p></td> +</tr> +<tr> +<td align="left" valign="top"><p class="table">line_spacing</p></td> +<td align="left" valign="top"><p class="table">(<strong>double</strong>) расстояние между строками, диапазон от 1.0 до 3.0</p></td> +</tr> +<tr> +<td align="left" valign="top"><p class="table">color1</p></td> +<td align="left" valign="top"><p class="table">(<strong>string</strong>) цвет фона</p></td> +</tr> +<tr> +<td align="left" valign="top"><p class="table">color2</p></td> +<td align="left" valign="top"><p class="table">(<strong>string</strong>) основной цвет ячейки таблицы</p></td> +</tr> +<tr> +<td align="left" valign="top"><p class="table">color3</p></td> +<td align="left" valign="top"><p class="table">(<strong>string</strong>) дополнительный цвет ячейки таблицы</p></td> +</tr> +<tr> +<td align="left" valign="top"><p class="table">color4</p></td> +<td align="left" valign="top"><p class="table">(<strong>string</strong>) основной цвет текста</p></td> +</tr> +<tr> +<td align="left" valign="top"><p class="table">color5</p></td> +<td align="left" valign="top"><p class="table">(<strong>string</strong>) дополнительный цвет текста</p></td> +</tr> +<tr> +<td align="left" valign="top"><p class="table">color6</p></td> +<td align="left" valign="top"><p class="table">(<strong>string</strong>) цвет рамки</p></td> +</tr> +</tbody> +</table> +</div> +<div class="literalblock"> +<div class="title">template.html</div> +<div class="content"> +<pre><code> border-width: {{ template_options.borderwidth }}px;</code></pre> +</div></div> +<div class="literalblock"> +<div class="title">output.html</div> +<div class="content"> +<pre><code> border-width: 3px;</code></pre> +</div></div> +<div class="paragraph"><p>Дополнительно <em>Subsurface</em> экспортирует переменную <strong>print_options</strong>. У этой переменной одно поле.</p></div> +<div class="tableblock"> +<table rules="all" +width="100%" +frame="border" +cellspacing="0" cellpadding="4"> +<col width="50%" /> +<col width="50%" /> +<tbody> +<tr> +<td align="left" valign="top"><p class="table"><strong>Название</strong></p></td> +<td align="left" valign="top"><p class="table"><strong>Описание</strong></p></td> +</tr> +<tr> +<td align="left" valign="top"><p class="table">grayscale</p></td> +<td align="left" valign="top"><p class="table">Используйте <em>CSS</em> фильтры для преобразования страницы в черно-белый цвет (необходимо добавлять в стиль body, чтобы сделать возможной черно-белую печать)</p></td> +</tr> +</tbody> +</table> +</div> +<div class="literalblock"> +<div class="title">template.html</div> +<div class="content"> +<pre><code> body { + {{ print_options.grayscale }}; + }</code></pre> +</div></div> +<div class="literalblock"> +<div class="title">output.html</div> +<div class="content"> +<pre><code> body { + -webkit-filter: grayscale(100%); + }</code></pre> +</div></div> +</div> +<div class="sect2"> +<h3 id="_определенные_css_селекторы">19.3. Определенные CSS-селекторы</h3> +<div class="paragraph"><p>Так как профиль погружения добавляется после рендеринга, <em>Subsurface</em> использует специальные <em>CSS</em>-селекторы +для поиска в сгенерированном HTML. Вам понадобится добавить селекторы из табдицы ниже.</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>Селектор</strong></p></td> +<td align="left" valign="top"><p class="table"><strong>Тип</strong></p></td> +<td align="left" valign="top"><p class="table"><strong>Описание</strong></p></td> +</tr> +<tr> +<td align="left" valign="top"><p class="table">dive_{{ dive.id }}</p></td> +<td align="left" valign="top"><p class="table">id</p></td> +<td align="left" valign="top"><p class="table">используется для получения соответствующего профиля погружения</p></td> +</tr> +<tr> +<td align="left" valign="top"><p class="table">diveProfile</p></td> +<td align="left" valign="top"><p class="table">class</p></td> +<td align="left" valign="top"><p class="table">каждый div-элемент, содержащий профиль, должен иметь этот селектор класса в дополнение к dive_{{ dive.id }} id-селектору</p></td> +</tr> +<tr> +<td align="left" valign="top"><p class="table">dontbreak</p></td> +<td align="left" valign="top"><p class="table">class</p></td> +<td align="left" valign="top"><p class="table">предотвращает div с этим классом от разбиаения на две страницы, может быть использован только в потоковых шаблонах (когда data-numberofdives = 0)</p></td> +</tr> +</tbody> +</table> +</div> +</div> +</div> +</div> +<div class="sect1"> +<h2 id="_приложение_е_частые_вопросы_и_ответы">20. ПРИЛОЖЕНИЕ Е: Частые вопросы и ответы</h2> +<div class="sectionbody"> +<div class="paragraph"><p>ВАЖНО: Отображение профиля погружения не поддерживается в потоковых шаблонах (когда data-numberofdives = 0)</p></div> +<div class="sect2"> +<h3 id="_специальные_атрибуты">20.1. Специальные атрибуты</h3> +<div class="paragraph"><p>Существует два способа рендеринга - указанное количество погружений на странице и потоковое отображение +(_Subsurface пытается разместить как можно больще погружений на странице).</p></div> +<div class="paragraph"><p>Атрибут <strong>data-numberofdives</strong> указывает сколько погружений должно быть отображено на странице</p></div> +<div class="ulist"><ul> +<li> +<p> +отобразить 6 погружений на странице: +</p> +</li> +</ul></div> +<div class="literalblock"> +<div class="content"> +<pre><code> <body data-numberofdives = 6></code></pre> +</div></div> +<div class="ulist"><ul> +<li> +<p> +отобразаить как можно больше погружений: +</p> +</li> +</ul></div> +<div class="literalblock"> +<div class="content"> +<pre><code> <body data-numberofdives = 0></code></pre> +</div></div> +<div class="paragraph"><p>ВАЖНО: Все размеры CSS должны быть в относительных единицах, чтобы поддерживать печать на бумаге любого размера.</p></div> +</div> +</div> +</div> +<div class="sect1"> +<h2 id="_приложение_ж_чаво">21. ПРИЛОЖЕНИЕ Ж: ЧаВо</h2> +<div class="sectionbody"> +<div class="sect2"> +<h3 id="SAC_CALCULATION">21.1. Похоже, что <em>Subsurface</em> неправильно считает расход газов и SAC</h3> +<div class="paragraph"><p><em>Вопрос</em>: Я погружался с баллоном 12.2л, начальное давление 220бар, конечное - 100 бар. Мои расчеты +SAC не совпадают со значением в <em>Subsurface</em>. Возможно ли, что <em>Subsurface</em> считает неверно?</p></div> +<div class="paragraph"><p><em>Ответ</em>: Нет. <em>Subsurface</em> рассчитывает расход газа иначе, и даже лучше, чем вы +ожидаете. В частности, мы принимаем во внимание несжимаемость газа. +Традиционно, расход и SAC считаются по формуле: +<code>расход = объем баллона x (начальное давление - конечное давление)</code></p></div> +<div class="paragraph"><p>и это правильно для идеального газа, и это то, чему вас учили в теории. Но +"идеального газа" не существует, а реальные газы сжимаются нелинейно с ростом +давления. Также вы упускаете тот факт, что давление одной атмосферы не +равняется одному бар. Поэтому <strong>реальная</strong> формула будет:</p></div> +<div class="paragraph"><p><code>расход = (объем_воздуха_в_начале - объем_воздуха_в_конце)</code></p></div> +<div class="paragraph"><p>где объем воздуха это <strong>не</strong> просто "произведение объема на давление". Это +комбинация из: "примем во внимание сжимаемость газа" (что в принципе не играет +роли до 220 бар, это становится существенным для баллонов с давлением 300 +бар), и "переведем бар в атмосферы" (это основная причина несоответствия). +Напомним: одна атмосфера равняется ~1.013 бар, так что даже без сжимаемости ваш расход газа составит:</p></div> +<div class="paragraph"><p><code>12.2*((220-100)/1.013)</code></p></div> +<div class="paragraph"><p>что будет около 1445, а не 1464. Т.е. в ваших расчета было лишних 19 литров +из-за разницы между 1 бар и 1 АТМ. Сжимаемость начинает играть свою роль при +давлениях свыше 200 бар и уменьшит расход еще приблизительно на 8 литров, т.о. +вы расходовали около 1437 л при давлении на поверхности.</p></div> +<div class="paragraph"><p>Поэтому радуйтесь: ваш SAC лучше, чем вы считали. Либо огорчайтесь: у вас в +баллоне меньше воздуха, чем вы думали. И как уже упоминалось, "меньше чем +думали" начинает работать при довольно высоком давлении. Баллон при 400 бар не +содержит в два раза больше воздуха чем при 200 бар. При низких же давлениях +воздух ведет себя почти как идеальный газ.</p></div> +</div> +<div class="sect2"> +<h3 id="_на_некоторых_профилях_наблюдаются_различия_во_времени_с_данных_дайв_компьютера_8230">21.2. На некоторых профилях наблюдаются различия во времени с данных дайв-компьютера…</h3> +<div class="paragraph"><p><em>Subsurface</em> игнорирует поверхностное время при различных расчетах (средняя глубина, время дайва, SAC и т.д) +<em>Вопрос</em>: почему время погружения на дайв-компьютере и в <em>Subsurface</em> различаются?</p></div> +<div class="paragraph"><p><em>Ответ</em>: Например, вы решили выполнить проверку плавучести (достаточно глубокую, чтобы +компьютер посчитал это началом погружения), после чего всплыли на поверхность и еще 5 минут +прождали своего напарника. Ваш дайв-компьютер может посчитать длительность этого погружения +50 минут, потому что компьютер находится в режиме погружения, а <em>Subsurface</em> посчитает +длительность этого дайва равной 45 минутам, потому что вы действительно погружались 45 минут. +Особенно это заметно, если вы обучаете новичков OW, вы долгое время находитесь +в воде, но основное время проводите на поверхности. И это нельзя считать долгим погружением.</p></div> +</div> +<div class="sect2"> +<h3 id="_при_загрузке_отсутствуют_некоторые_погружения">21.3. При загрузке отсутствуют некоторые погружения</h3> +<div class="paragraph" id="DC_HISTORY"><p><em>Вопрос</em>: У меня не получается загрузить все мои погружения, только недавние. При этом руководство +по моему дайв-компьютеру утверждает, что он хранит историю ,например, 999 погружений.</p></div> +<div class="paragraph"><p><em>Ответ</em>: История погружений и профиль погружения - две большие разницы. История +хранит только общее количество погружений и общее время, проведенное под водой. +С другой стороны, журнал хранит профили погружений, но объем его памяти +ограничен. Точно количество хранимых профилей зависит от частоты дискретизации +и длительности погружений. Как только память переполняется, старые погружения +перетираются новыми. Поэтому мы можем загрузить последний 13, 30 или 199 +погружений.</p></div> +<div class="paragraph"><p>Если вы выгрузили погружения в разные программы для ведения журналов перед тем как они были +перезаписаны, есть вероятность, что <em>Subsurface</em> сможет импортировать их. Однако, если погружения +были только в вашем дайв-компьютере, они не могут быть восстановлены после того как были +перезаписаны новыми погружениями.</p></div> +</div> +</div> +</div> +</div> +<div id="footnotes"><hr /></div> +<div id="footer"> +<div id="footer-text"> +Последнее обновление 2015-12-15 13:35:30 PST +</div> +</div> +</body> +</html> diff --git a/cmake/Modules/HandleFindGit2.cmake b/cmake/Modules/HandleFindGit2.cmake index 7a7da9a91..9d682117d 100644 --- a/cmake/Modules/HandleFindGit2.cmake +++ b/cmake/Modules/HandleFindGit2.cmake @@ -16,7 +16,7 @@ else() include_directories(${LIBGIT2_INCLUDE_DIR}) if(FORCE_LIBSSH) find_package(Libssh2 QUIET CONFIG) - if ("${LIBSSH2_VERSION}" STRGREATER "1.6.1") + if ("${LIBSSH2_VERSION}" STRLESS "1.7" AND "${LIBSSH2_VERSION}" STRGREATER "1.6.1") set(LIBSSH2_LIBRARIES Libssh2::libssh2) endif() # at least on my Mac I get the mixed case variable instead... diff --git a/cmake/Modules/version.cmake b/cmake/Modules/version.cmake index dcff01d74..a666e6975 100644 --- a/cmake/Modules/version.cmake +++ b/cmake/Modules/version.cmake @@ -10,7 +10,7 @@ execute_process( OUTPUT_VARIABLE CANONICAL_VERSION_STRING OUTPUT_STRIP_TRAILING_WHITESPACE ) -set(MOBILE_VERSION_STRING "0.93") +set(MOBILE_VERSION_STRING "1.0.4") configure_file(${SRC} ${DST} @ONLY) if(CMAKE_SYSTEM_NAME STREQUAL "Windows") diff --git a/desktop-widgets/configuredivecomputerdialog.cpp b/desktop-widgets/configuredivecomputerdialog.cpp index 8df184788..428b326e4 100644 --- a/desktop-widgets/configuredivecomputerdialog.cpp +++ b/desktop-widgets/configuredivecomputerdialog.cpp @@ -38,6 +38,8 @@ GasSpinBoxItemDelegate::~GasSpinBoxItemDelegate() QWidget *GasSpinBoxItemDelegate::createEditor(QWidget *parent, const QStyleOptionViewItem &option, const QModelIndex &index) const { + Q_UNUSED(option) + Q_UNUSED(index) // Create the spinbox and give it it's settings QSpinBox *sb = new QSpinBox(parent); if (type == PERCENT) { @@ -82,6 +84,8 @@ GasTypeComboBoxItemDelegate::~GasTypeComboBoxItemDelegate() QWidget *GasTypeComboBoxItemDelegate::createEditor(QWidget *parent, const QStyleOptionViewItem &option, const QModelIndex &index) const { + Q_UNUSED(option) + Q_UNUSED(index) // Create the combobox and populate it QComboBox *cb = new QComboBox(parent); cb->addItem(QString("Disabled")); @@ -327,6 +331,7 @@ ConfigureDiveComputerDialog::~ConfigureDiveComputerDialog() void ConfigureDiveComputerDialog::closeEvent(QCloseEvent *event) { + Q_UNUSED(event) dc_close(); QSettings settings; @@ -472,9 +477,9 @@ void ConfigureDiveComputerDialog::populateDeviceDetailsOSTC3() deviceDetails->alwaysShowppO2 = ui.alwaysShowppO2->isChecked(); deviceDetails->tempSensorOffset = ui.tempSensorOffsetDoubleSpinBox->value() * 10; deviceDetails->safetyStopLength = ui.safetyStopLengthSpinBox->value(); - deviceDetails->safetyStopStartDepth = ui.safetyStopStartDepthDoubleSpinBox->value(); - deviceDetails->safetyStopEndDepth = ui.safetyStopEndDepthDoubleSpinBox->value(); - deviceDetails->safetyStopResetDepth = ui.safetyStopResetDepthDoubleSpinBox->value(); + deviceDetails->safetyStopStartDepth = ui.safetyStopStartDepthDoubleSpinBox->value() * 10; + deviceDetails->safetyStopEndDepth = ui.safetyStopEndDepthDoubleSpinBox->value() * 10; + deviceDetails->safetyStopResetDepth = ui.safetyStopResetDepthDoubleSpinBox->value() * 10; //set gas values gas gas1; @@ -605,9 +610,9 @@ void ConfigureDiveComputerDialog::populateDeviceDetailsOSTC() deviceDetails->decoGasConsumption = ui.decoGasConsumption_3->value(); deviceDetails->graphicalSpeedIndicator = ui.graphicalSpeedIndicator_3->isChecked(); deviceDetails->safetyStopLength = ui.safetyStopLengthSpinBox_3->value(); - deviceDetails->safetyStopStartDepth = ui.safetyStopStartDepthDoubleSpinBox_3->value(); - deviceDetails->safetyStopEndDepth = ui.safetyStopEndDepthDoubleSpinBox_3->value(); - deviceDetails->safetyStopResetDepth = ui.safetyStopResetDepthDoubleSpinBox_3->value(); + deviceDetails->safetyStopStartDepth = ui.safetyStopStartDepthDoubleSpinBox_3->value() * 10; + deviceDetails->safetyStopEndDepth = ui.safetyStopEndDepthDoubleSpinBox_3->value() * 10; + deviceDetails->safetyStopResetDepth = ui.safetyStopResetDepthDoubleSpinBox_3->value() * 10; //set gas values gas gas1; @@ -856,9 +861,9 @@ void ConfigureDiveComputerDialog::reloadValuesOSTC3() ui.alwaysShowppO2->setChecked(deviceDetails->alwaysShowppO2); ui.tempSensorOffsetDoubleSpinBox->setValue((double)deviceDetails->tempSensorOffset / 10.0); ui.safetyStopLengthSpinBox->setValue(deviceDetails->safetyStopLength); - ui.safetyStopStartDepthDoubleSpinBox->setValue(deviceDetails->safetyStopStartDepth); - ui.safetyStopEndDepthDoubleSpinBox->setValue(deviceDetails->safetyStopEndDepth); - ui.safetyStopResetDepthDoubleSpinBox->setValue(deviceDetails->safetyStopResetDepth); + ui.safetyStopStartDepthDoubleSpinBox->setValue(deviceDetails->safetyStopStartDepth / 10.0); + ui.safetyStopEndDepthDoubleSpinBox->setValue(deviceDetails->safetyStopEndDepth / 10.0); + ui.safetyStopResetDepthDoubleSpinBox->setValue(deviceDetails->safetyStopResetDepth / 10.0); //load gas 1 values ui.ostc3GasTable->setItem(0, 1, new QTableWidgetItem(QString::number(deviceDetails->gas1.oxygen))); @@ -983,9 +988,9 @@ setNumberOfDives ui.decoGasConsumption_3->setValue(deviceDetails->decoGasConsumption); ui.graphicalSpeedIndicator_3->setChecked(deviceDetails->graphicalSpeedIndicator); ui.safetyStopLengthSpinBox_3->setValue(deviceDetails->safetyStopLength); - ui.safetyStopStartDepthDoubleSpinBox_3->setValue(deviceDetails->safetyStopStartDepth); - ui.safetyStopEndDepthDoubleSpinBox_3->setValue(deviceDetails->safetyStopEndDepth); - ui.safetyStopResetDepthDoubleSpinBox_3->setValue(deviceDetails->safetyStopResetDepth); + ui.safetyStopStartDepthDoubleSpinBox_3->setValue(deviceDetails->safetyStopStartDepth / 10.0); + ui.safetyStopEndDepthDoubleSpinBox_3->setValue(deviceDetails->safetyStopEndDepth / 10.0); + ui.safetyStopResetDepthDoubleSpinBox_3->setValue(deviceDetails->safetyStopResetDepth / 10.0); //load gas 1 values ui.ostcGasTable->setItem(0, 1, new QTableWidgetItem(QString::number(deviceDetails->gas1.oxygen))); @@ -1270,6 +1275,6 @@ void ConfigureDiveComputerDialog::dc_close() ui.DiveComputerList->setEnabled(true); ui.logToFile->setEnabled(true); ui.updateFirmwareButton->setEnabled(false); - ui.progressBar->setFormat("Disonnected from device"); + ui.progressBar->setFormat("Disconnected from device"); ui.progressBar->setValue(0); } diff --git a/desktop-widgets/divelistview.cpp b/desktop-widgets/divelistview.cpp index d2386ecf1..f3204a111 100644 --- a/desktop-widgets/divelistview.cpp +++ b/desktop-widgets/divelistview.cpp @@ -515,6 +515,7 @@ void DiveListView::toggleColumnVisibilityByIndex() void DiveListView::currentChanged(const QModelIndex ¤t, const QModelIndex &previous) { + Q_UNUSED(previous) if (!isVisible()) return; if (!current.isValid()) diff --git a/desktop-widgets/divelogexportdialog.cpp b/desktop-widgets/divelogexportdialog.cpp index 7a406b982..e7c53274c 100644 --- a/desktop-widgets/divelogexportdialog.cpp +++ b/desktop-widgets/divelogexportdialog.cpp @@ -105,24 +105,9 @@ void DiveLogExportDialog::exportHtmlInit(const QString &filename) exportHtmlInitLogic(filename, hes); } -void DiveLogExportDialog::exportHTMLsettings(const QString &filename) -{ - QSettings settings; - settings.beginGroup("HTML"); - settings.setValue("fontSelection", ui->fontSelection->currentIndex()); - settings.setValue("fontSizeSelection", ui->fontSizeSelection->currentIndex()); - settings.setValue("themeSelection", ui->themeSelection->currentIndex()); - settings.setValue("subsurfaceNumbers", ui->exportSubsurfaceNumber->isChecked()); - settings.setValue("yearlyStatistics", ui->exportStatistics->isChecked()); - settings.setValue("listOnly", ui->exportListOnly->isChecked()); - settings.setValue("exportPhotos", ui->exportPhotos->isChecked()); - settings.endGroup(); - -} - - void DiveLogExportDialog::on_exportGroup_buttonClicked(QAbstractButton *button) { + Q_UNUSED(button) showExplanation(); } @@ -210,7 +195,7 @@ void DiveLogExportDialog::export_depths(const char *filename, const bool selecte int i; const char *unit = NULL; - struct membuffer buf = { 0 }; + struct membuffer buf = {}; for_each_dive (i, dive) { if (selected_only && !dive->selected) diff --git a/desktop-widgets/divelogexportdialog.h b/desktop-widgets/divelogexportdialog.h index a5b5cc770..b72d96c50 100644 --- a/desktop-widgets/divelogexportdialog.h +++ b/desktop-widgets/divelogexportdialog.h @@ -32,7 +32,6 @@ private: Ui::DiveLogExportDialog *ui; void showExplanation(); void exportHtmlInit(const QString &filename); - void exportHTMLsettings(const QString &filename); void export_depths(const char *filename, const bool selected_only); }; diff --git a/desktop-widgets/divelogimportdialog.cpp b/desktop-widgets/divelogimportdialog.cpp index 363be800e..4e5607ed3 100644 --- a/desktop-widgets/divelogimportdialog.cpp +++ b/desktop-widgets/divelogimportdialog.cpp @@ -9,17 +9,19 @@ static QString subsurface_mimedata = "subsurface/csvcolumns"; static QString subsurface_index = "subsurface/csvindex"; +#define SILENCE_WARNING 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, "" + const DiveLogImportDialog::CSVAppConfig DiveLogImportDialog::CSVApps[CSVAPPS] = { // time, depth, temperature, po2, sensor1, sensor2, sensor3, cns, ndl, tts, stopdepth, pressure, setpoint // indices are 0 based, -1 means the column doesn't exist - { "Manual import", }, + { "Manual import", SILENCE_WARNING }, { "APD Log Viewer - DC1", 0, 1, 15, 6, 3, 4, 5, 17, -1, -1, 18, -1, 2, "Tab" }, { "APD Log Viewer - DC2", 0, 1, 15, 6, 7, 8, 9, 17, -1, -1, 18, -1, 2, "Tab" }, { "XP5", 0, 1, 9, -1, -1, -1, -1, -1, -1, -1, -1, -1, -1, "Tab" }, { "SensusCSV", 9, 10, -1, -1, -1, -1, -1, -1, -1, -1, -1, -1, -1, "," }, { "Seabear CSV", 0, 1, 5, -1, -1, -1, -1, -1, 2, 3, 4, 6, -1, ";" }, { "SubsurfaceCSV", -1, -1, -1, -1, -1, -1, -1, -1, -1, -1, -1, -1, -1, "Tab" }, - { NULL, } + { NULL, SILENCE_WARNING } }; enum Known { @@ -44,6 +46,8 @@ ColumnNameProvider::ColumnNameProvider(QObject *parent) : QAbstractListModel(par bool ColumnNameProvider::insertRows(int row, int count, const QModelIndex &parent) { + Q_UNUSED(count) + Q_UNUSED(parent) beginInsertRows(QModelIndex(), row, row); columnNames.append(QString()); endInsertRows(); @@ -52,6 +56,8 @@ bool ColumnNameProvider::insertRows(int row, int count, const QModelIndex &paren bool ColumnNameProvider::removeRows(int row, int count, const QModelIndex &parent) { + Q_UNUSED(count) + Q_UNUSED(parent) beginRemoveRows(QModelIndex(), row, row); columnNames.removeAt(row); endRemoveRows(); @@ -100,6 +106,7 @@ int ColumnNameProvider::mymatch(QString value) const ColumnNameView::ColumnNameView(QWidget *parent) { + Q_UNUSED(parent) setAcceptDrops(true); setDragEnabled(true); } @@ -161,6 +168,7 @@ void ColumnNameView::dropEvent(QDropEvent *event) ColumnDropCSVView::ColumnDropCSVView(QWidget *parent) { + Q_UNUSED(parent) setAcceptDrops(true); } diff --git a/desktop-widgets/diveplanner.cpp b/desktop-widgets/diveplanner.cpp index fd14944f0..f84781e96 100644 --- a/desktop-widgets/diveplanner.cpp +++ b/desktop-widgets/diveplanner.cpp @@ -306,7 +306,6 @@ PlannerSettingsWidget::PlannerSettingsWidget(QWidget *parent, Qt::WindowFlags f) ui.display_runtime->setChecked(prefs.display_runtime); ui.display_transitions->setChecked(prefs.display_transitions); ui.safetystop->setChecked(prefs.safetystop); - ui.reserve_gas->setValue(prefs.reserve_gas / 1000); ui.bottompo2->setValue(prefs.bottompo2 / 1000.0); ui.decopo2->setValue(prefs.decopo2 / 1000.0); ui.backgasBreaks->setChecked(prefs.doo2breaks); @@ -448,6 +447,18 @@ void PlannerSettingsWidget::settingsChanged() ui.bottomSAC->setValue((double) prefs.bottomsac / 1000.0); ui.decoStopSAC->setValue((double) prefs.decosac / 1000.0); } + if(get_units()->pressure == units::BAR) { + ui.reserve_gas->setSuffix(tr("bar")); + ui.reserve_gas->setSingleStep(1); + ui.reserve_gas->setValue(prefs.reserve_gas / 1000); + ui.reserve_gas->setMaximum(300); + } else { + ui.reserve_gas->setSuffix(tr("psi")); + ui.reserve_gas->setSingleStep(10); + ui.reserve_gas->setMaximum(5000); + ui.reserve_gas->setValue(mbar_to_PSI(prefs.reserve_gas)); + } + ui.bottomSAC->blockSignals(false); ui.decoStopSAC->blockSignals(false); updateUnitsUI(); @@ -458,10 +469,6 @@ void PlannerSettingsWidget::settingsChanged() ui.descRate->setSuffix(vs); } -void PlannerSettingsWidget::atmPressureChanged(const QString &pressure) -{ -} - void PlannerSettingsWidget::printDecoPlan() { } diff --git a/desktop-widgets/diveplanner.h b/desktop-widgets/diveplanner.h index b2e03a97b..1cc96adc3 100644 --- a/desktop-widgets/diveplanner.h +++ b/desktop-widgets/diveplanner.h @@ -68,7 +68,6 @@ public: public slots: void settingsChanged(); - void atmPressureChanged(const QString &pressure); void bottomSacChanged(const double bottomSac); void decoSacChanged(const double decosac); void printDecoPlan(); diff --git a/desktop-widgets/diveshareexportdialog.cpp b/desktop-widgets/diveshareexportdialog.cpp index c6a7771d8..ed6e2829a 100644 --- a/desktop-widgets/diveshareexportdialog.cpp +++ b/desktop-widgets/diveshareexportdialog.cpp @@ -119,7 +119,7 @@ void DiveShareExportDialog::doUpload() ui->progressBar->setRange(0, 0); //generate json - struct membuffer buf = { 0 }; + struct membuffer buf = {}; export_list(&buf, NULL, exportSelected, false); QByteArray json_data(buf.buffer, buf.len); free_buffer(&buf); diff --git a/desktop-widgets/downloadfromdivecomputer.cpp b/desktop-widgets/downloadfromdivecomputer.cpp index 4c8fa6b4a..be6018b36 100644 --- a/desktop-widgets/downloadfromdivecomputer.cpp +++ b/desktop-widgets/downloadfromdivecomputer.cpp @@ -626,11 +626,13 @@ DiveImportedModel::DiveImportedModel(QObject *o) : QAbstractTableModel(o), int DiveImportedModel::columnCount(const QModelIndex &model) const { + Q_UNUSED(model) return 3; } int DiveImportedModel::rowCount(const QModelIndex &model) const { + Q_UNUSED(model) return lastIndex - firstIndex + 1; } diff --git a/desktop-widgets/locationinformation.cpp b/desktop-widgets/locationinformation.cpp index 2501ad7fb..5ca858a6b 100644 --- a/desktop-widgets/locationinformation.cpp +++ b/desktop-widgets/locationinformation.cpp @@ -280,12 +280,14 @@ void LocationInformationWidget::reverseGeocode() DiveLocationFilterProxyModel::DiveLocationFilterProxyModel(QObject *parent) { + Q_UNUSED(parent) } DiveLocationLineEdit *location_line_edit = 0; bool DiveLocationFilterProxyModel::filterAcceptsRow(int source_row, const QModelIndex &source_parent) const { + Q_UNUSED(source_parent) if (source_row == 0) return true; @@ -301,6 +303,7 @@ bool DiveLocationFilterProxyModel::lessThan(const QModelIndex &source_left, cons DiveLocationModel::DiveLocationModel(QObject *o) { + Q_UNUSED(o) resetModel(); } @@ -361,16 +364,19 @@ QVariant DiveLocationModel::data(const QModelIndex &index, int role) const int DiveLocationModel::columnCount(const QModelIndex &parent) const { + Q_UNUSED(parent) return COLUMNS; } int DiveLocationModel::rowCount(const QModelIndex &parent) const { + Q_UNUSED(parent) return dive_site_table.nr + 2; } bool DiveLocationModel::setData(const QModelIndex &index, const QVariant &value, int role) { + Q_UNUSED(role) if (!index.isValid()) return false; if (index.row() > 1) @@ -415,6 +421,7 @@ DiveLocationLineEdit::DiveLocationLineEdit(QWidget *parent) : QLineEdit(parent), bool DiveLocationLineEdit::eventFilter(QObject *o, QEvent *e) { + Q_UNUSED(o) if (e->type() == QEvent::KeyPress) { QKeyEvent *keyEv = (QKeyEvent *)e; @@ -498,6 +505,7 @@ static struct dive_site *get_dive_site_name_start_which_str(const QString &str) void DiveLocationLineEdit::setTemporaryDiveSiteName(const QString &s) { + Q_UNUSED(s) QModelIndex i0 = model->index(0, DiveLocationModel::NAME); QModelIndex i1 = model->index(1, DiveLocationModel::NAME); model->setData(i0, text()); @@ -608,6 +616,7 @@ uint32_t DiveLocationLineEdit::currDiveSiteUuid() const DiveLocationListView::DiveLocationListView(QWidget *parent) { + Q_UNUSED(parent) } void DiveLocationListView::currentChanged(const QModelIndex ¤t, const QModelIndex &previous) diff --git a/desktop-widgets/mainwindow.cpp b/desktop-widgets/mainwindow.cpp index a3d6c4333..df0190e10 100644 --- a/desktop-widgets/mainwindow.cpp +++ b/desktop-widgets/mainwindow.cpp @@ -250,7 +250,7 @@ MainWindow::MainWindow() : QMainWindow(), set_git_update_cb(&updateProgress); // Toolbar Connections related to the Profile Update - SettingsObjectWrapper *sWrapper = SettingsObjectWrapper::instance(); sWrapper->techDetails; + SettingsObjectWrapper *sWrapper = SettingsObjectWrapper::instance(); connect(ui.profCalcAllTissues, &QAction::triggered, sWrapper->techDetails, &TechnicalDetailsSettings::setCalcalltissues); connect(ui.profCalcCeiling, &QAction::triggered, sWrapper->techDetails, &TechnicalDetailsSettings::setCalcceiling); connect(ui.profDcCeiling, &QAction::triggered, sWrapper->techDetails, &TechnicalDetailsSettings::setDCceiling); @@ -780,6 +780,10 @@ void MainWindow::on_actionEditDeviceNames_triggered() bool MainWindow::plannerStateClean() { + if (progressDialog) + // we are accessing the cloud, so let's not switch into Add or Plan mode + return false; + if (DivePlannerPointsModel::instance()->currentMode() != DivePlannerPointsModel::NOTHING || information()->isEditing()) { QMessageBox::warning(this, tr("Warning"), tr("Please save or cancel the current dive edit before trying to add a dive.")); @@ -1300,8 +1304,6 @@ void MainWindow::readSettings() { static bool firstRun = true; - SettingsObjectWrapper *settings = SettingsObjectWrapper::instance(); - QSettings s; //WARNING: Why those prefs are not on the prefs struct? s.beginGroup("DiveComputer"); default_dive_computer_vendor = getSetting(s, "dive_computer_vendor"); @@ -1853,7 +1855,6 @@ void MainWindow::editCurrentDive() void MainWindow::turnOffNdlTts() { - const bool triggered = false; SettingsObjectWrapper::instance()->techDetails->setCalcndltts(false); } diff --git a/desktop-widgets/modeldelegates.cpp b/desktop-widgets/modeldelegates.cpp index 02b5838ec..377a1baed 100644 --- a/desktop-widgets/modeldelegates.cpp +++ b/desktop-widgets/modeldelegates.cpp @@ -26,6 +26,8 @@ QSize DiveListDelegate::sizeHint(const QStyleOptionViewItem &option, const QModelIndex &index) const { + Q_UNUSED(option) + Q_UNUSED(index) return QSize(50, 22); } @@ -68,6 +70,8 @@ void StarWidgetsDelegate::paint(QPainter *painter, const QStyleOptionViewItem &o QSize StarWidgetsDelegate::sizeHint(const QStyleOptionViewItem &option, const QModelIndex &index) const { + Q_UNUSED(option) + Q_UNUSED(index) return minStarSize; } @@ -106,6 +110,7 @@ struct CurrSelected { QWidget *ComboBoxDelegate::createEditor(QWidget *parent, const QStyleOptionViewItem &option, const QModelIndex &index) const { + Q_UNUSED(option) MainWindow *m = MainWindow::instance(); QComboBox *comboDelegate = new QComboBox(parent); comboDelegate->setModel(model); @@ -220,6 +225,7 @@ bool ComboBoxDelegate::eventFilter(QObject *object, QEvent *event) void ComboBoxDelegate::updateEditorGeometry(QWidget *editor, const QStyleOptionViewItem &option, const QModelIndex &index) const { + Q_UNUSED(index) QRect defaultRect = option.rect; defaultRect.setX(defaultRect.x() - 1); defaultRect.setY(defaultRect.y() - 1); @@ -236,6 +242,10 @@ struct RevertCylinderData { void TankInfoDelegate::setModelData(QWidget *editor, QAbstractItemModel *model, const QModelIndex &thisindex) const { + Q_UNUSED(model) + Q_UNUSED(editor) + Q_UNUSED(thisindex) + CylindersModel *mymodel = qobject_cast<CylindersModel *>(currCombo.model); TankInfoModel *tanks = TankInfoModel::instance(); QModelIndexList matches = tanks->match(tanks->index(0, 0), Qt::DisplayRole, currCombo.activeText); @@ -265,6 +275,8 @@ TankInfoDelegate::TankInfoDelegate(QObject *parent) : ComboBoxDelegate(TankInfoM void TankInfoDelegate::reenableReplot(QWidget *widget, QAbstractItemDelegate::EndEditHint hint) { + Q_UNUSED(widget) + Q_UNUSED(hint) MainWindow::instance()->graphics()->setReplot(true); // FIXME: We need to replot after a cylinder is selected but the replot below overwrites // the newly selected cylinder. @@ -273,6 +285,7 @@ void TankInfoDelegate::reenableReplot(QWidget *widget, QAbstractItemDelegate::En void TankInfoDelegate::revertModelData(QWidget *widget, QAbstractItemDelegate::EndEditHint hint) { + Q_UNUSED(widget) if (hint == QAbstractItemDelegate::NoHint || hint == QAbstractItemDelegate::RevertModelCache) { CylindersModel *mymodel = qobject_cast<CylindersModel *>(currCombo.model); @@ -302,6 +315,8 @@ TankUseDelegate::TankUseDelegate(QObject *parent) : QStyledItemDelegate(parent) QWidget *TankUseDelegate::createEditor(QWidget * parent, const QStyleOptionViewItem & option, const QModelIndex & index) const { + Q_UNUSED(option) + Q_UNUSED(index) QComboBox *comboBox = new QComboBox(parent); for (int i = 0; i < NUM_GAS_USE; i++) comboBox->addItem(gettextFromC::instance()->trGettext(cylinderuse_text[i])); @@ -328,6 +343,7 @@ struct RevertWeightData { void WSInfoDelegate::revertModelData(QWidget *widget, QAbstractItemDelegate::EndEditHint hint) { + Q_UNUSED(widget) if (hint == QAbstractItemDelegate::NoHint || hint == QAbstractItemDelegate::RevertModelCache) { WeightModel *mymodel = qobject_cast<WeightModel *>(currCombo.model); @@ -338,6 +354,10 @@ void WSInfoDelegate::revertModelData(QWidget *widget, QAbstractItemDelegate::End void WSInfoDelegate::setModelData(QWidget *editor, QAbstractItemModel *model, const QModelIndex &thisindex) const { + Q_UNUSED(editor) + Q_UNUSED(model) + Q_UNUSED(thisindex) + WeightModel *mymodel = qobject_cast<WeightModel *>(currCombo.model); WSInfoModel *wsim = WSInfoModel::instance(); QModelIndexList matches = wsim->match(wsim->index(0, 0), Qt::DisplayRole, currCombo.activeText); @@ -374,6 +394,8 @@ QWidget *WSInfoDelegate::createEditor(QWidget *parent, const QStyleOptionViewIte void AirTypesDelegate::revertModelData(QWidget *widget, QAbstractItemDelegate::EndEditHint hint) { + Q_UNUSED(widget) + Q_UNUSED(hint) } void AirTypesDelegate::setModelData(QWidget *editor, QAbstractItemModel *model, const QModelIndex &index) const @@ -422,6 +444,7 @@ QWidget *DoubleSpinBoxDelegate::createEditor(QWidget *parent, const QStyleOption LocationFilterDelegate::LocationFilterDelegate(QObject *parent) { + Q_UNUSED(parent) } void LocationFilterDelegate::paint(QPainter *painter, const QStyleOptionViewItem &option, const QModelIndex &origIdx) const diff --git a/desktop-widgets/plugins/facebook/facebook_integration.cpp b/desktop-widgets/plugins/facebook/facebook_integration.cpp index 21ad6f733..58d757e87 100644 --- a/desktop-widgets/plugins/facebook/facebook_integration.cpp +++ b/desktop-widgets/plugins/facebook/facebook_integration.cpp @@ -7,6 +7,7 @@ FacebookPlugin::FacebookPlugin(QObject* parent) : fbConnectWidget(new FacebookConnectWidget()), fbUploadDialog(new SocialNetworkDialog()) { + Q_UNUSED(parent) } bool FacebookPlugin::isConnected() diff --git a/desktop-widgets/preferences/preferences_network.h b/desktop-widgets/preferences/preferences_network.h index 3e17d51b0..b56d7bb1a 100644 --- a/desktop-widgets/preferences/preferences_network.h +++ b/desktop-widgets/preferences/preferences_network.h @@ -18,11 +18,11 @@ public: public slots: void proxyType_changed(int i); + void cloudPinNeeded(); private: Ui::PreferencesNetwork *ui; - void cloudPinNeeded(); void passwordUpdateSuccessfull(); }; -#endif
\ No newline at end of file +#endif diff --git a/desktop-widgets/printdialog.cpp b/desktop-widgets/printdialog.cpp index d10e67921..72e4d20c8 100644 --- a/desktop-widgets/printdialog.cpp +++ b/desktop-widgets/printdialog.cpp @@ -203,6 +203,7 @@ void PrintDialog::printClicked(void) void PrintDialog::onPaintRequested(QPrinter *printerPtr) { + Q_UNUSED(printerPtr) createPrinterObj(); connect(printer, SIGNAL(progessUpdated(int)), progressBar, SLOT(setValue(int))); printer->print(); diff --git a/desktop-widgets/simplewidgets.cpp b/desktop-widgets/simplewidgets.cpp index c3c7072ca..6d46a49c7 100644 --- a/desktop-widgets/simplewidgets.cpp +++ b/desktop-widgets/simplewidgets.cpp @@ -67,6 +67,7 @@ double MinMaxAvgWidget::minimum() const MinMaxAvgWidget::MinMaxAvgWidget(QWidget *parent) : d(new MinMaxAvgWidgetPrivate(this)) { + Q_UNUSED(parent) } MinMaxAvgWidget::~MinMaxAvgWidget() @@ -243,6 +244,7 @@ void ShiftTimesDialog::buttonClicked(QAbstractButton *button) void ShiftTimesDialog::showEvent(QShowEvent *event) { + Q_UNUSED(event) ui.timeEdit->setTime(QTime(0, 0, 0, 0)); when = get_times(); //get time of first selected dive ui.currentTime->setText(get_dive_date_string(when)); @@ -475,6 +477,7 @@ void DateWidget::changeEvent(QEvent *event) #define DATEWIDGETWIDTH 80 void DateWidget::paintEvent(QPaintEvent *event) { + Q_UNUSED(event) static QPixmap pix = QPixmap(":/calendar").scaled(DATEWIDGETWIDTH, 64); QPainter painter(this); diff --git a/desktop-widgets/starwidget.cpp b/desktop-widgets/starwidget.cpp index d959ed3b9..a810883c2 100644 --- a/desktop-widgets/starwidget.cpp +++ b/desktop-widgets/starwidget.cpp @@ -62,6 +62,7 @@ void StarWidget::mouseReleaseEvent(QMouseEvent *event) void StarWidget::paintEvent(QPaintEvent *event) { + Q_UNUSED(event) QPainter p(this); QImage star = hasFocus() ? focusedImage(starActive()) : starActive(); QPixmap selected = QPixmap::fromImage(star); diff --git a/desktop-widgets/statistics/statisticswidget.cpp b/desktop-widgets/statistics/statisticswidget.cpp index 3e91fa317..d06f51a98 100644 --- a/desktop-widgets/statistics/statisticswidget.cpp +++ b/desktop-widgets/statistics/statisticswidget.cpp @@ -23,6 +23,9 @@ void YearlyStatisticsWidget::setModel(YearlyStatisticsModel *m) void YearlyStatisticsWidget::modelRowsInserted(const QModelIndex &index, int first, int last) { + Q_UNUSED(index) + Q_UNUSED(first) + Q_UNUSED(last) // stub } diff --git a/desktop-widgets/subsurfacewebservices.cpp b/desktop-widgets/subsurfacewebservices.cpp index 0dd9ad4ef..2ca3de187 100644 --- a/desktop-widgets/subsurfacewebservices.cpp +++ b/desktop-widgets/subsurfacewebservices.cpp @@ -194,7 +194,7 @@ bool DivelogsDeWebServices::prepare_dives_for_divelogs(const QString &tempfile, const char *membuf; xmlDoc *transformed; struct zip_source *s; - struct membuffer mb = { 0 }; + struct membuffer mb = {}; /* * Get the i'th dive in XML format so we can process it. @@ -961,6 +961,7 @@ void DivelogsDeWebServices::uploadFinished() void DivelogsDeWebServices::setStatusText(int status) { + Q_UNUSED(status) } void DivelogsDeWebServices::downloadError(QNetworkReply::NetworkError) diff --git a/desktop-widgets/subsurfacewebservices.h b/desktop-widgets/subsurfacewebservices.h index c00b6f63f..f7d15d0fd 100644 --- a/desktop-widgets/subsurfacewebservices.h +++ b/desktop-widgets/subsurfacewebservices.h @@ -106,7 +106,7 @@ slots: // need to declare them as no ops or Qt4 is unhappy virtual void startDownload() { } virtual void startUpload() { } - virtual void buttonClicked(QAbstractButton *button) { } + virtual void buttonClicked(QAbstractButton *button) { Q_UNUSED(button) } }; #ifdef __cplusplus diff --git a/icons/AppIcon167x167~ipad.png b/icons/AppIcon167x167~ipad.png Binary files differnew file mode 100644 index 000000000..965b5a32c --- /dev/null +++ b/icons/AppIcon167x167~ipad.png diff --git a/packaging/android/build.sh b/packaging/android/build.sh index 3ca68eb2d..17ccb03b3 100644 --- a/packaging/android/build.sh +++ b/packaging/android/build.sh @@ -355,10 +355,15 @@ cmake $MOBILE_CMAKE \ sed -i -e "s/-lcrypto//g" CMakeFiles/subsurface-mobile.dir/link.txt # set up the version number -SUBSURFACE_MOBILE_VERSION=$(grep MOBILE_VERSION_STRING ssrf-version.h | awk "{ print \$3 }" ) + +rm ssrf-version.h +make version +SUBSURFACE_MOBILE_VERSION=$(grep MOBILE_VERSION_STRING ssrf-version.h | awk '{ print $3 }' | tr -d \" ) +SUBSURFACE_MOBILE_VERSION="${SUBSURFACE_MOBILE_VERSION} ($(grep CANONICAL_VERSION_STRING ssrf-version.h | awk '{ print $3 }' | tr -d \"))" + rm -rf android-mobile cp -a $SUBSURFACE_SOURCE/android-mobile . -sed -i -e "s/@SUBSURFACE_MOBILE_VERSION@/$SUBSURFACE_MOBILE_VERSION/;s/@BUILD_NR@/$BUILD_NR/" android-mobile/AndroidManifest.xml +sed -i -e "s/@SUBSURFACE_MOBILE_VERSION@/\"$SUBSURFACE_MOBILE_VERSION\"/;s/@BUILD_NR@/$BUILD_NR/" android-mobile/AndroidManifest.xml # now build Subsurface and use the rest of the command line arguments make $@ diff --git a/packaging/ios/Info.plist b/packaging/ios/Info.plist deleted file mode 100644 index b25f58e7a..000000000 --- a/packaging/ios/Info.plist +++ /dev/null @@ -1,79 +0,0 @@ -<?xml version="1.0" encoding="UTF-8"?> -<!DOCTYPE plist PUBLIC "-//Apple//DTD PLIST 1.0//EN" "http://www.apple.com/DTDs/PropertyList-1.0.dtd"> -<plist version="1.0"> -<dict> - <key>CFBundleIcons</key> - <dict> - <key>CFBundlePrimaryIcon</key> - <dict> - <key>CFBundleIconFiles</key> - <array> - <string>AppIcon29x29.png</string> - <string>AppIcon29x29@2x.png</string> - <string>AppIcon40x40@2x.png</string> - <string>AppIcon57x57.png</string> - <string>AppIcon57x57@2x.png</string> - <string>AppIcon60x60@2x.png</string> - </array> - </dict> - </dict> - <key>CFBundleIcons~ipad</key> - <dict> - <key>CFBundlePrimaryIcon</key> - <dict> - <key>CFBundleIconFiles</key> - <array> - <string>AppIcon29x29.png</string> - <string>AppIcon29x29@2x.png</string> - <string>AppIcon40x40@2x.png</string> - <string>AppIcon57x57.png</string> - <string>AppIcon57x57@2x.png</string> - <string>AppIcon60x60@2x.png</string> - <string>AppIcon29x29~ipad.png</string> - <string>AppIcon29x29@2x~ipad.png</string> - <string>AppIcon40x40~ipad.png</string> - <string>AppIcon40x40@2x~ipad.png</string> - <string>AppIcon50x50~ipad.png</string> - <string>AppIcon50x50@2x~ipad.png</string> - <string>AppIcon72x72~ipad.png</string> - <string>AppIcon72x72@2x~ipad.png</string> - <string>AppIcon76x76~ipad.png</string> - <string>AppIcon76x76@2x~ipad.png</string> - </array> - </dict> - </dict> - <key>CFBundlePackageType</key> - <string>APPL</string> - <key>CFBundleGetInfoString</key> - <string>Created by Qt/QMake</string> - <key>CFBundleSignature</key> - <string>????</string> - <key>CFBundleExecutable</key> - <string>subsurface-ios</string> - <key>CFBundleIdentifier</key> - <string>org.subsurface-divelog.subsurface-mobile</string> - <key>CFBundleDisplayName</key> - <string>Subsruface-mobile</string> - <key>CFBundleName</key> - <string>Subsruface-mobile</string> - <key>CFBundleShortVersionString</key> - <string>0.93</string> - <key>CFBundleVersion</key> - <string>1.0</string> - <key>LSRequiresIPhoneOS</key> - <true/> - <key>UILaunchStoryboardName</key> - <string>SubsurfaceMobileLaunch</string> - <key>UISupportedInterfaceOrientations</key> - <array> - <string>UIInterfaceOrientationPortrait</string> - <string>UIInterfaceOrientationPortraitUpsideDown</string> - <string>UIInterfaceOrientationLandscapeLeft</string> - <string>UIInterfaceOrientationLandscapeRight</string> - </array> - <key>NOTE</key> - <string>This file was generated by Qt/QMake.</string> - <key>NSHumanReadableCopyright</key> - <string>Copyright © 2011-2016 Linus Torvalds, Dirk Hohndel, Tomaz Canabrava and the Subsurface developer team</string> -</dict> -</plist> diff --git a/packaging/ios/Info.plist.in b/packaging/ios/Info.plist.in new file mode 100644 index 000000000..4461ed291 --- /dev/null +++ b/packaging/ios/Info.plist.in @@ -0,0 +1,88 @@ +<?xml version="1.0" encoding="UTF-8"?> +<!DOCTYPE plist PUBLIC "-//Apple//DTD PLIST 1.0//EN" "http://www.apple.com/DTDs/PropertyList-1.0.dtd"> +<plist version="1.0"> +<dict> + <key>CFBundleDisplayName</key> + <string>Subsurface-mobile</string> + <key>CFBundleExecutable</key> + <string>Subsurface-mobile</string> + <key>CFBundleGetInfoString</key> + <string>Created by Qt/QMake</string> + <key>CFBundleIcons</key> + <dict> + <key>CFBundlePrimaryIcon</key> + <dict> + <key>CFBundleIconFiles</key> + <array> + <string>AppIcon29x29.png</string> + <string>AppIcon29x29@2x.png</string> + <string>AppIcon40x40@2x.png</string> + <string>AppIcon57x57.png</string> + <string>AppIcon57x57@2x.png</string> + <string>AppIcon60x60@2x.png</string> + </array> + </dict> + </dict> + <key>CFBundleIcons~ipad</key> + <dict> + <key>CFBundlePrimaryIcon</key> + <dict> + <key>CFBundleIconFiles</key> + <array> + <string>AppIcon29x29.png</string> + <string>AppIcon29x29@2x.png</string> + <string>AppIcon40x40@2x.png</string> + <string>AppIcon57x57.png</string> + <string>AppIcon57x57@2x.png</string> + <string>AppIcon60x60@2x.png</string> + <string>AppIcon29x29~ipad.png</string> + <string>AppIcon29x29@2x~ipad.png</string> + <string>AppIcon40x40~ipad.png</string> + <string>AppIcon40x40@2x~ipad.png</string> + <string>AppIcon50x50~ipad.png</string> + <string>AppIcon50x50@2x~ipad.png</string> + <string>AppIcon72x72~ipad.png</string> + <string>AppIcon72x72@2x~ipad.png</string> + <string>AppIcon76x76~ipad.png</string> + <string>AppIcon76x76@2x~ipad.png</string> + <string>AppIcon167x167~ipad.png</string> + </array> + </dict> + </dict> + <key>CFBundleIdentifier</key> + <string>org.subsurface-divelog.subsurface-mobile</string> + <key>CFBundleName</key> + <string>Subsurface-mobile</string> + <key>CFBundlePackageType</key> + <string>APPL</string> + <key>CFBundleShortVersionString</key> + <string>@MOBILE_VERSION@</string> + <key>CFBundleSignature</key> + <string>????</string> + <key>CFBundleVersion</key> + <string>@CANONICAL_VERSION@</string> + <key>LSRequiresIPhoneOS</key> + <true/> + <key>NOTE</key> + <string>This file was generated by Qt/QMake.</string> + <key>NSHumanReadableCopyright</key> + <string>Copyright © 2011-2016 Linus Torvalds, Dirk Hohndel, Tomaz Canabrava and the Subsurface developer team</string> + <key>NSMainNibFile</key> + <string>SubsurfaceMobileLaunch</string> + <key>UIBackgroundModes</key> + <array> + <string>location</string> + </array> + <key>UILaunchStoryboardName</key> + <string>SubsurfaceMobileLaunch</string> + <key>UISupportedInterfaceOrientations</key> + <array> + <string>UIInterfaceOrientationPortrait</string> + <string>UIInterfaceOrientationPortraitUpsideDown</string> + <string>UIInterfaceOrientationLandscapeLeft</string> + <string>UIInterfaceOrientationLandscapeRight</string> + </array> + <key>NSLocationAlwaysUsageDescription</key> + <string>When the GPS background service is running, Subsurface-mobile continues to collect GPS positions which can then be matched with dive records.</string> +</dict> +</plist> diff --git a/packaging/ios/README b/packaging/ios/README index f414fb441..b3d49cd55 100644 --- a/packaging/ios/README +++ b/packaging/ios/README @@ -1,14 +1,14 @@ Tool repo to crosscompile subsurface for iOS -------------------------------------------- +This is very rough - the interaction between the different tools seems quite +fragile. + Dependencies: -0. This only works on a Mac -1. XCode with iOS SDK and Qt5.5. See below -2. cmake -3. ant -4. dependencies of libdivecomputer and subsurface - - visit http://subsurface.hohndel.org/documentation/building/ +- This only works on a Mac +- XCode with iOS SDK and Qt5.6 +- cmake Steps to install: @@ -19,14 +19,30 @@ And QT for android from: http://qt-project.org/downloads, including the iOS bits Step 2. Extract and install these into known directories. Have a look in the top of build.sh for where the cross build tool expects -them. By default thats is: ../../../Qt/5.5 +them. By default thats is: ../../../Qt/5.6 -Step 2. +Step 3. Run bash build.sh in the terminal. -The script will download and build the whole dependency chain. +The script will download and build the whole dependency chain, but not the actual +Subsurface-mobile binary + +Step 4. +Launch QtCreator with the Subsurface-mobile/Subsurface-mobile.pro +Build Subsurface-mobile in QtCreator - you can build for the simulator and for +a device and even deploy to a connected device. + +This will likely require an Apple Developer account ($$$). In order to create a +bundle that can be distributed things get even more complex and the interaction +between QtCreator, Xcode and the Apple Developer Portal is still quite +confusing to me. + +WARNING: +======== -After this, Subsurface-mobile will be built for iOS. +The version number used in the Subsurface-mobile app is created in step 3. +So whenever you pull the latest git or commit a change, you need to re-run the +build.sh script so that the Info.plist used by QtCreator (well, by Xcode under +the hood) gets updated. Otherwise you will continue to see the old version +number, even though the sources have been recompiled which can be very +confusing. -The output folder is subsurface-build-ios and your newly created package shows -up as: -subsurface-build-ios/.... something diff --git a/packaging/ios/subsurface-ios/MainForm.ui.qml b/packaging/ios/Subsurface-mobile/MainForm.ui.qml index 7913bb2b8..7913bb2b8 100644 --- a/packaging/ios/subsurface-ios/MainForm.ui.qml +++ b/packaging/ios/Subsurface-mobile/MainForm.ui.qml diff --git a/packaging/ios/subsurface-ios/subsurface-ios.pro b/packaging/ios/Subsurface-mobile/Subsurface-mobile.pro index e3f657eb2..e3f657eb2 100644 --- a/packaging/ios/subsurface-ios/subsurface-ios.pro +++ b/packaging/ios/Subsurface-mobile/Subsurface-mobile.pro diff --git a/packaging/ios/subsurface-ios/deployment.pri b/packaging/ios/Subsurface-mobile/deployment.pri index 265ce71f3..265ce71f3 100644 --- a/packaging/ios/subsurface-ios/deployment.pri +++ b/packaging/ios/Subsurface-mobile/deployment.pri diff --git a/packaging/ios/subsurface-ios/main.qml b/packaging/ios/Subsurface-mobile/main.qml index 26b1a7998..26b1a7998 100644 --- a/packaging/ios/subsurface-ios/main.qml +++ b/packaging/ios/Subsurface-mobile/main.qml diff --git a/packaging/ios/subsurface-ios/qml.qrc b/packaging/ios/Subsurface-mobile/qml.qrc index 7684346a5..7684346a5 100644 --- a/packaging/ios/subsurface-ios/qml.qrc +++ b/packaging/ios/Subsurface-mobile/qml.qrc diff --git a/packaging/ios/build.sh b/packaging/ios/build.sh index 06cbfacdc..be313f094 100644 --- a/packaging/ios/build.sh +++ b/packaging/ios/build.sh @@ -26,9 +26,12 @@ LIBFTDI_VERSION=1.2 GITVERSION=$(git describe --tags --abbrev=12) CANONICALVERSION=$(git describe --tags --abbrev=12 | sed -e 's/-g.*$// ; s/^v//' | sed -e 's/-/./') MOBILEVERSION=$(grep MOBILE ../../cmake/Modules/version.cmake | cut -d\" -f 2) -echo "#define GIT_VERSION_STRING \"$GITVERSION\"" > subsurface-ios/ssrf-version.h -echo "#define CANONICAL_VERSION_STRING \"$CANONICALVERSION\"" >> subsurface-ios/ssrf-version.h -echo "#define MOBILE_VERSION_STRING \"$MOBILEVERSION\"" >> subsurface-ios/ssrf-version.h +echo "#define GIT_VERSION_STRING \"$GITVERSION\"" > subsurface-mobile/ssrf-version.h +echo "#define CANONICAL_VERSION_STRING \"$CANONICALVERSION\"" >> subsurface-mobile/ssrf-version.h +echo "#define MOBILE_VERSION_STRING \"$MOBILEVERSION\"" >> subsurface-mobile/ssrf-version.h + +# create Info.plist with the correct versions +cat Info.plist.in | sed "s/@MOBILE_VERSION@/$MOBILEVERSION/;s/@CANONICAL_VERSION@/$CANONICALVERSION/" > Info.plist # Build Subsurface-mobile by default SUBSURFACE_MOBILE=1 diff --git a/profile-widget/divecartesianaxis.cpp b/profile-widget/divecartesianaxis.cpp index 2c3b7fe79..a453d69ea 100644 --- a/profile-widget/divecartesianaxis.cpp +++ b/profile-widget/divecartesianaxis.cpp @@ -109,6 +109,7 @@ void DiveCartesianAxis::setOrientation(Orientation o) QColor DiveCartesianAxis::colorForValue(double value) { + Q_UNUSED(value) return QColor(Qt::black); } @@ -414,9 +415,9 @@ QString TimeAxis::textForValue(double value) return QString::number(nr); } -void TimeAxis::updateTicks() +void TimeAxis::updateTicks(color_indice_t color) { - DiveCartesianAxis::updateTicks(); + DiveCartesianAxis::updateTicks(color); if (maximum() > 600) { for (int i = 0; i < labels.count(); i++) { labels[i]->setVisible(i % 2); diff --git a/profile-widget/divecartesianaxis.h b/profile-widget/divecartesianaxis.h index 4e06b9a82..a603cebc7 100644 --- a/profile-widget/divecartesianaxis.h +++ b/profile-widget/divecartesianaxis.h @@ -95,7 +95,7 @@ class TimeAxis : public DiveCartesianAxis { Q_OBJECT public: TimeAxis(ProfileWidget2 *widget); - virtual void updateTicks(); + void updateTicks(color_indice_t color = TIME_GRID); protected: QString textForValue(double value); diff --git a/profile-widget/diveeventitem.cpp b/profile-widget/diveeventitem.cpp index 1986015f7..3e1de48f3 100644 --- a/profile-widget/diveeventitem.cpp +++ b/profile-widget/diveeventitem.cpp @@ -66,8 +66,13 @@ void DiveEventItem::setupPixmap() #ifndef SUBSURFACE_MOBILE int sz_bigger = metrics.sz_med + metrics.sz_small; // ex 40px #else +#if defined(Q_OS_IOS) + // on iOS devices we need to adjust for Device Pixel Ratio + int sz_bigger = metrics.sz_med * metrics.dpr; +#else int sz_bigger = metrics.sz_med; #endif +#endif int sz_pix = sz_bigger/2; // ex 20px #define EVENT_PIXMAP(PIX) QPixmap(QString(PIX)).scaled(sz_pix, sz_pix, Qt::KeepAspectRatio, Qt::SmoothTransformation) @@ -134,6 +139,9 @@ void DiveEventItem::setupToolTipString() void DiveEventItem::eventVisibilityChanged(const QString &eventName, bool visible) { + //WARN: lookslike we should implement this. + Q_UNUSED(eventName); + Q_UNUSED(visible); } bool DiveEventItem::shouldBeHidden() diff --git a/profile-widget/divepixmapitem.cpp b/profile-widget/divepixmapitem.cpp index 698172cc6..39c41d19d 100644 --- a/profile-widget/divepixmapitem.cpp +++ b/profile-widget/divepixmapitem.cpp @@ -83,6 +83,7 @@ void DivePictureItem::setPixmap(const QPixmap &pix) CloseButtonItem *button = NULL; void DivePictureItem::hoverEnterEvent(QGraphicsSceneHoverEvent *event) { + Q_UNUSED(event); Animations::scaleTo(this, 1.0); setZValue(5); @@ -109,6 +110,7 @@ void DivePictureItem::setFileUrl(const QString &s) void DivePictureItem::hoverLeaveEvent(QGraphicsSceneHoverEvent *event) { + Q_UNUSED(event); Animations::scaleTo(this, 0.2); setZValue(0); if(button){ @@ -126,6 +128,7 @@ DivePictureItem::~DivePictureItem(){ void DivePictureItem::mousePressEvent(QGraphicsSceneMouseEvent *event) { + Q_UNUSED(event); QDesktopServices::openUrl(QUrl::fromLocalFile(fileUrl)); } diff --git a/profile-widget/diveprofileitem.cpp b/profile-widget/diveprofileitem.cpp index 93c954fd4..022616ef1 100644 --- a/profile-widget/diveprofileitem.cpp +++ b/profile-widget/diveprofileitem.cpp @@ -56,6 +56,9 @@ void AbstractProfilePolygonItem::setModel(DivePlotDataModel *model) void AbstractProfilePolygonItem::modelDataRemoved(const QModelIndex &parent, int from, int to) { + Q_UNUSED(from); + Q_UNUSED(parent); + Q_UNUSED(to); setPolygon(QPolygonF()); qDeleteAll(texts); texts.clear(); @@ -94,8 +97,8 @@ bool AbstractProfilePolygonItem::shouldCalculateStuff(const QModelIndex &topLeft void AbstractProfilePolygonItem::modelDataChanged(const QModelIndex &topLeft, const QModelIndex &bottomRight) { - // We don't have enougth data to calculate things, quit. - + Q_UNUSED(topLeft); + Q_UNUSED(bottomRight); // Calculate the polygon. This is the polygon that will be painted on screen // on the ::paint method. Here we calculate the correct position of the points // regarting our cartesian plane ( made by the hAxis and vAxis ), the QPolygonF @@ -340,6 +343,8 @@ void DiveHeartrateItem::createTextItem(int sec, int hr) void DiveHeartrateItem::paint(QPainter *painter, const QStyleOptionGraphicsItem *option, QWidget *widget) { + Q_UNUSED(option); + Q_UNUSED(widget); if (polygon().isEmpty()) return; painter->save(); @@ -386,6 +391,9 @@ void DivePercentageItem::modelDataChanged(const QModelIndex &topLeft, const QMod void DivePercentageItem::paint(QPainter *painter, const QStyleOptionGraphicsItem *option, QWidget *widget) { + Q_UNUSED(option); + Q_UNUSED(widget); + if (polygon().isEmpty()) return; painter->save(); @@ -431,6 +439,9 @@ void DiveAmbPressureItem::modelDataChanged(const QModelIndex &topLeft, const QMo void DiveAmbPressureItem::paint(QPainter *painter, const QStyleOptionGraphicsItem *option, QWidget *widget) { + Q_UNUSED(option); + Q_UNUSED(widget); + if (polygon().isEmpty()) return; painter->save(); @@ -476,6 +487,9 @@ void DiveGFLineItem::modelDataChanged(const QModelIndex &topLeft, const QModelIn void DiveGFLineItem::paint(QPainter *painter, const QStyleOptionGraphicsItem *option, QWidget *widget) { + Q_UNUSED(option); + Q_UNUSED(widget); + if (polygon().isEmpty()) return; painter->save(); @@ -557,6 +571,9 @@ void DiveTemperatureItem::createTextItem(int sec, int mkelvin) void DiveTemperatureItem::paint(QPainter *painter, const QStyleOptionGraphicsItem *option, QWidget *widget) { + Q_UNUSED(option); + Q_UNUSED(widget); + if (polygon().isEmpty()) return; painter->save(); @@ -601,6 +618,9 @@ void DiveMeanDepthItem::modelDataChanged(const QModelIndex &topLeft, const QMode void DiveMeanDepthItem::paint(QPainter *painter, const QStyleOptionGraphicsItem *option, QWidget *widget) { + Q_UNUSED(option); + Q_UNUSED(widget); + if (polygon().isEmpty()) return; painter->save(); @@ -646,7 +666,7 @@ void DiveGasPressureItem::modelDataChanged(const QModelIndex &topLeft, const QMo if (displayed_dive.dc.divemode == CCR) o2mbar = GET_O2CYLINDER_PRESSURE(entry); - if (entry->cylinderindex != last_index) { + if ((int)entry->cylinderindex != last_index) { polygons.append(QPolygonF()); // this is the polygon that will be actually drawn on screen. last_index = entry->cylinderindex; } @@ -722,7 +742,7 @@ void DiveGasPressureItem::modelDataChanged(const QModelIndex &topLeft, const QMo if (!mbar) continue; - if (cyl != entry->cylinderindex) { // Pressure value near the left hand edge of the profile - other cylinders: + if (cyl != (int)entry->cylinderindex) { // Pressure value near the left hand edge of the profile - other cylinders: cyl = entry->cylinderindex; // For each other cylinder, write the gas lable and pressure if (!seen_cyl[cyl]) { plotPressureValue(mbar, entry->sec, alignVar, print_y_offset[cyl][1]); @@ -767,6 +787,9 @@ void DiveGasPressureItem::plotGasValue(int mbar, int sec, struct gasmix gasmix, void DiveGasPressureItem::paint(QPainter *painter, const QStyleOptionGraphicsItem *option, QWidget *widget) { + Q_UNUSED(option); + Q_UNUSED(widget); + if (polygon().isEmpty()) return; QPen pen; @@ -940,6 +963,9 @@ void PartialPressureGasItem::modelDataChanged(const QModelIndex &topLeft, const void PartialPressureGasItem::paint(QPainter *painter, const QStyleOptionGraphicsItem *option, QWidget *widget) { + Q_UNUSED(option); + Q_UNUSED(widget); + const qreal pWidth = 0.0; painter->save(); painter->setPen(QPen(normalColor, pWidth)); diff --git a/profile-widget/divetooltipitem.cpp b/profile-widget/divetooltipitem.cpp index 78de4641b..6d6405056 100644 --- a/profile-widget/divetooltipitem.cpp +++ b/profile-widget/divetooltipitem.cpp @@ -243,7 +243,7 @@ void ToolTipItem::refresh(const QPointF &pos) struct plot_data *entry; static QPixmap tissues(16,60); static QPainter painter(&tissues); - static struct membuffer mb = { 0 }; + static struct membuffer mb = {}; if(refreshTime.elapsed() < 40) return; diff --git a/profile-widget/profilewidget2.cpp b/profile-widget/profilewidget2.cpp index 38276b235..e4b03ebcb 100644 --- a/profile-widget/profilewidget2.cpp +++ b/profile-widget/profilewidget2.cpp @@ -573,7 +573,7 @@ void ProfileWidget2::plotDive(struct dive *d, bool force) if (prefs.deco_mode == VPMB) decoModelParameters->setText(QString("VPM-B +%1").arg(prefs.conservatism_level)); else - decoModelParameters->setText(QString("GF %1/%2").arg(prefs.gflow).arg(prefs.gfhigh)); + decoModelParameters->setText(QString("GF %1/%2").arg(diveplan.gflow).arg(diveplan.gfhigh)); #endif } @@ -605,9 +605,9 @@ void ProfileWidget2::plotDive(struct dive *d, bool force) currentdc = fake_dc(currentdc, false); } +#ifndef SUBSURFACE_MOBILE bool setpointflag = (currentdc->divemode == CCR) && prefs.pp_graphs.po2 && current_dive; bool sensorflag = setpointflag && prefs.show_ccr_sensors; -#ifndef SUBSURFACE_MOBILE o2SetpointGasItem->setVisible(setpointflag && prefs.show_ccr_setpoint); ccrsensor1GasItem->setVisible(sensorflag); ccrsensor2GasItem->setVisible(sensorflag && (currentdc->no_o2sensors > 1)); @@ -723,8 +723,8 @@ void ProfileWidget2::plotDive(struct dive *d, bool force) event->setVisible(!event->shouldBeHidden()); } QString dcText = get_dc_nickname(currentdc->model, currentdc->deviceid); - int nr; #ifndef SUBSURFACE_MOBILE + int nr; if ((nr = number_of_computers(&displayed_dive)) > 1) dcText += tr(" (#%1 of %2)").arg(dc_number + 1).arg(nr); #endif @@ -1302,7 +1302,7 @@ struct plot_data *ProfileWidget2::getEntryFromPos(QPointF pos) for (int i = 0; i < plotInfo.nr; i++) { entry = plotInfo.entry + i; - if (entry->sec >= seconds) + if ((int)entry->sec >= seconds) break; } return entry; @@ -1674,6 +1674,9 @@ void ProfileWidget2::disconnectTemporaryConnections() #ifndef SUBSURFACE_MOBILE void ProfileWidget2::pointInserted(const QModelIndex &parent, int start, int end) { + Q_UNUSED(parent) + Q_UNUSED(start) + Q_UNUSED(end) DiveHandler *item = new DiveHandler(); scene()->addItem(item); handles << item; diff --git a/profile-widget/profilewidget2.h b/profile-widget/profilewidget2.h index 438523340..5e05b14f8 100644 --- a/profile-widget/profilewidget2.h +++ b/profile-widget/profilewidget2.h @@ -141,14 +141,14 @@ slots: // Necessary to call from QAction's signals. protected: virtual ~ProfileWidget2(); - virtual void resizeEvent(QResizeEvent *event); + void resizeEvent(QResizeEvent *event) Q_DECL_OVERRIDE; #ifndef SUBSURFACE_MOBILE - virtual void wheelEvent(QWheelEvent *event); - virtual void mouseMoveEvent(QMouseEvent *event); - virtual void contextMenuEvent(QContextMenuEvent *event); - virtual void mouseDoubleClickEvent(QMouseEvent *event); - virtual void mousePressEvent(QMouseEvent *event); - virtual void mouseReleaseEvent(QMouseEvent *event); + void wheelEvent(QWheelEvent *event) Q_DECL_OVERRIDE; + void mouseMoveEvent(QMouseEvent *event) Q_DECL_OVERRIDE; + void contextMenuEvent(QContextMenuEvent *event) Q_DECL_OVERRIDE; + void mouseDoubleClickEvent(QMouseEvent *event) Q_DECL_OVERRIDE; + void mousePressEvent(QMouseEvent *event) Q_DECL_OVERRIDE; + void mouseReleaseEvent(QMouseEvent *event) Q_DECL_OVERRIDE; #endif void dropEvent(QDropEvent *event) Q_DECL_OVERRIDE; void dragEnterEvent(QDragEnterEvent *event) Q_DECL_OVERRIDE; diff --git a/profile-widget/tankitem.cpp b/profile-widget/tankitem.cpp index c0e75a371..aba41d660 100644 --- a/profile-widget/tankitem.cpp +++ b/profile-widget/tankitem.cpp @@ -5,6 +5,7 @@ #include <QPen> TankItem::TankItem(QObject *parent) : + QObject(parent), QGraphicsRectItem(), dataModel(0), pInfoEntry(0), @@ -78,8 +79,9 @@ void TankItem::createBar(qreal x, qreal w, struct gasmix *gas) void TankItem::modelDataChanged(const QModelIndex &topLeft, const QModelIndex &bottomRight) { + Q_UNUSED(topLeft); + Q_UNUSED(bottomRight); // We don't have enougth data to calculate things, quit. - if (!dataModel || !pInfoEntry || !pInfoNr) return; diff --git a/qt-mobile/qml/About.qml b/qt-mobile/qml/About.qml index 9b1b69c8b..b1ca6e6bc 100644 --- a/qt-mobile/qml/About.qml +++ b/qt-mobile/qml/About.qml @@ -6,7 +6,7 @@ import org.subsurfacedivelog.mobile 1.0 Kirigami.ScrollablePage { id: aboutPage - property int pageWidth: subsurfaceTheme.columnWidth - Kirigami.Units.gridUnit + property int pageWidth: subsurfaceTheme.columnWidth - Kirigami.Units.smallSpacing title: "About Subsurface-mobile" ColumnLayout { @@ -14,26 +14,22 @@ Kirigami.ScrollablePage { width: aboutPage.width Layout.margins: Kirigami.Units.gridUnit / 2 + Kirigami.Heading { text: "About Subsurface-mobile" - Layout.margins: Kirigami.Units.largeSpacing / 2 + Layout.topMargin: Kirigami.Units.gridUnit Layout.alignment: Qt.AlignHCenter Layout.maximumWidth: pageWidth wrapMode: TextEdit.WrapAtWordBoundaryOrAnywhere } - - Rectangle { - color: "transparent" - Layout.margins: Kirigami.Units.largeSpacing - Layout.fillWidth: true - Layout.minimumHeight: childrenRect.height - Image { - id: image - source: "qrc:/qml/subsurface-mobile-icon.png" - width: parent.width - Kirigami.Units.largeSpacing - fillMode: Image.PreserveAspectFit - horizontalAlignment: Image.AlignHCenter - } + Image { + id: image + source: "qrc:/qml/subsurface-mobile-icon.png" + width: pageWidth / 2 + height: width + fillMode: Image.Stretch + Layout.alignment: Qt.AlignCenter + horizontalAlignment: Image.AlignHCenter } Kirigami.Heading { diff --git a/qt-mobile/qml/CloudCredentials.qml b/qt-mobile/qml/CloudCredentials.qml index 3eeeb16b4..4f1484ce8 100644 --- a/qt-mobile/qml/CloudCredentials.qml +++ b/qt-mobile/qml/CloudCredentials.qml @@ -12,18 +12,28 @@ Item { property string username: login.text; property string password: password.text; - property bool issave: savePassword.checked; function saveCredentials() { manager.cloudUserName = login.text manager.cloudPassword = password.text - manager.saveCloudPassword = savePassword.checked manager.saveCloudCredentials() } ColumnLayout { id: outerLayout width: subsurfaceTheme.columnWidth - 2 * Kirigami.Units.gridUnit + + onVisibleChanged: { + if (visible) { + manager.appendTextToLog("Credential scrn: show kbd was: " + (Qt.inputMethod.isVisible ? "visible" : "invisible")) + Qt.inputMethod.show() + login.forceActiveFocus() + } else { + manager.appendTextToLog("Credential scrn: hide kbd was: " + (Qt.inputMethod.isVisible ? "visible" : "invisible")) + Qt.inputMethod.hide() + } + } + Kirigami.Heading { text: "Cloud credentials" level: headingLevel @@ -68,14 +78,6 @@ Item { Kirigami.Label { text: "Show password" } - - CheckBox { - checked: manager.saveCloudPassword - id: savePassword - } - Kirigami.Label { - text: "Remember" - } } Item { width: Kirigami.Units.gridUnit; height: width } } diff --git a/qt-mobile/qml/DiveDetails.qml b/qt-mobile/qml/DiveDetails.qml index 555e5ba0c..22cffdd6d 100644 --- a/qt-mobile/qml/DiveDetails.qml +++ b/qt-mobile/qml/DiveDetails.qml @@ -38,45 +38,57 @@ Kirigami.Page { states: [ State { name: "view" - PropertyChanges { target: diveDetailsPage; contextualActions: deleteAction } - PropertyChanges { target: detailsEditScroll; opened: false } + PropertyChanges { target: diveDetailsPage; contextualActions: Qt.platform.os == "ios" ? [ deleteAction, backAction ] : [ deleteAction ] } + PropertyChanges { target: detailsEditScroll; visible: false } }, State { name: "edit" - PropertyChanges { target: diveDetailsPage; contextualActions: null } - PropertyChanges { target: detailsEditScroll; opened: true } + PropertyChanges { target: diveDetailsPage; contextualActions: Qt.platform.os == "ios" ? [ cancelAction ] : null } + PropertyChanges { target: detailsEditScroll; visible: true } }, State { name: "add" - PropertyChanges { target: diveDetailsPage; contextualActions: null } - PropertyChanges { target: detailsEditScroll; opened: true } + PropertyChanges { target: diveDetailsPage; contextualActions: Qt.platform.os == "ios" ? [ cancelAction ] : null } + PropertyChanges { target: detailsEditScroll; visible: true } } ] - function endAddMode() { - // edit was canceled - so remove the dive from the dive list - manager.addDiveAborted(dive_id) - state = "view" - Qt.inputMethod.hide() + property QtObject deleteAction: Action { + text: "Delete dive" + iconName: "trash-empty" + onTriggered: { + contextDrawer.close() + var deletedId = diveDetailsListView.currentItem.modelData.dive.id + manager.deleteDive(deletedId) + stackView.pop() + showPassiveNotification("Dive deleted", 3000, "Undo", + function() { + manager.undoDelete(deletedId) + }); + } } - property list<QtObject> deleteAction: [ - Kirigami.Action { - text: "Delete dive" - iconName: "trash-empty" - onTriggered: { - var deletedId = diveDetailsListView.currentItem.modelData.dive.id - manager.deleteDive(deletedId) - showPassiveNotification("Dive deleted", 3000, "Undo", - function() { - manager.undoDelete(deletedId) - }); - contextDrawer.close() - stackView.pop() - } + property QtObject cancelAction: Kirigami.Action { + text: state === "edit" ? "Cancel edit" : "Cancel dive add" + iconName: "dialog-cancel" + onTriggered: { + contextDrawer.close() + if (state === "add") + returnTopPage() + else + endEditMode() } - ] + } + + property QtObject backAction: Action { + text: "Back to dive list" + iconName: "go-previous" + onTriggered: { + contextDrawer.close() + returnTopPage() + } + } mainAction: Action { iconName: state !== "view" ? "document-save" : "document-edit" @@ -94,7 +106,7 @@ Kirigami.Page { endEditMode() event.accepted = true; } else if (state === "add") { - endAddMode() + endEditMode() stackView.pop() event.accepted = true; } @@ -107,7 +119,10 @@ Kirigami.Page { } function endEditMode() { - // just cancel the edit state + // if we were adding a dive, we need to remove it + if (state === "add") + manager.addDiveAborted(dive_id) + // just cancel the edit/add state state = "view"; Qt.inputMethod.hide(); } diff --git a/qt-mobile/qml/DiveDetailsView.qml b/qt-mobile/qml/DiveDetailsView.qml index bf1408755..c8502d02f 100644 --- a/qt-mobile/qml/DiveDetailsView.qml +++ b/qt-mobile/qml/DiveDetailsView.qml @@ -104,7 +104,6 @@ Item { Layout.minimumHeight: width * 0.75 Layout.columnSpan: 4 clip: false - devicePixelRatio: Kirigami.Units.devicePixelRatio Rectangle { color: "transparent" opacity: 0.6 @@ -250,10 +249,25 @@ Item { Kirigami.Label { id: txtBuddy text: dive.buddy - Layout.columnSpan: 3 wrapMode: TextEdit.WrapAtWordBoundaryOrAnywhere - Layout.maximumWidth: detailsView.col2Width + detailsView.col3Width + detailsView.col4Width - Layout.preferredWidth: detailsView.col2Width + detailsView.col3Width + detailsView.col4Width + Layout.maximumWidth: detailsView.col2Width + Layout.preferredWidth: detailsView.col2Width + } + + Kirigami.Label { + text: "SAC:" + wrapMode: Text.WrapAtWordBoundaryOrAnywhere + opacity: 0.6 + Layout.maximumWidth: detailsView.col3Width + Layout.preferredWidth: detailsView.col3Width + Layout.alignment: Qt.AlignRight + } + Kirigami.Label { + id: txtSAC + text: dive.sac + wrapMode: TextEdit.WrapAtWordBoundaryOrAnywhere + Layout.maximumWidth: detailsView.col4Width + Layout.preferredWidth: detailsView.col4Width } Kirigami.Heading { diff --git a/qt-mobile/qml/DiveList.qml b/qt-mobile/qml/DiveList.qml index 3696d08ec..b689f0108 100644 --- a/qt-mobile/qml/DiveList.qml +++ b/qt-mobile/qml/DiveList.qml @@ -16,6 +16,11 @@ Kirigami.ScrollablePage { property int credentialStatus: manager.credentialStatus property int numDives: diveListView.count + property color textColor: subsurfaceTheme.diveListTextColor + + function scrollToTop() { + diveListView.positionViewAtBeginning() + } Component { id: diveDelegate @@ -47,6 +52,7 @@ Kirigami.ScrollablePage { font.weight: Font.Light elide: Text.ElideRight maximumLineCount: 1 // needed for elide to work at all + color: textColor anchors { left: parent.left leftMargin: horizontalPadding @@ -57,8 +63,8 @@ Kirigami.ScrollablePage { Kirigami.Label { id: dateLabel text: dive.date + " " + dive.time - opacity: 0.6 font.pointSize: subsurfaceTheme.smallPointSize + color: textColor anchors { right: parent.right top: parent.top @@ -74,30 +80,31 @@ Kirigami.ScrollablePage { } Kirigami.Label { text: 'Depth: ' - opacity: 0.6 font.pointSize: subsurfaceTheme.smallPointSize + color: textColor } Kirigami.Label { text: dive.depth width: Math.max(Kirigami.Units.gridUnit * 3, paintedWidth) // helps vertical alignment throughout listview font.pointSize: subsurfaceTheme.smallPointSize + color: textColor } Kirigami.Label { text: 'Duration: ' - opacity: 0.6 font.pointSize: subsurfaceTheme.smallPointSize + color: textColor } Kirigami.Label { text: dive.duration font.pointSize: subsurfaceTheme.smallPointSize + color: textColor } } Kirigami.Label { id: numberText text: "#" + dive.number - color: Kirigami.Theme.textColor font.pointSize: subsurfaceTheme.smallPointSize - opacity: 0.6 + color: textColor anchors { right: parent.right top: locationText.bottom @@ -135,6 +142,7 @@ Kirigami.ScrollablePage { leftMargin: Kirigami.Units.gridUnit / 2 right: parent.right } + color: textColor level: 2 } Rectangle { diff --git a/qt-mobile/qml/GpsList.qml b/qt-mobile/qml/GpsList.qml index 0a57486c5..54dc02121 100644 --- a/qt-mobile/qml/GpsList.qml +++ b/qt-mobile/qml/GpsList.qml @@ -29,7 +29,7 @@ Kirigami.ScrollablePage { */ Component { id: gpsDelegate - Kirigami.ActionsForListItem { + Kirigami.SwipeListItem { id: gpsFix enabled: true width: parent.width diff --git a/qt-mobile/qml/StartPage.qml b/qt-mobile/qml/StartPage.qml index 64b236ade..2d70cfcb3 100644 --- a/qt-mobile/qml/StartPage.qml +++ b/qt-mobile/qml/StartPage.qml @@ -9,8 +9,6 @@ ColumnLayout { id: startpage width: subsurfaceTheme.columnWidth - property int buttonWidth: width * 0.9 - function saveCredentials() { cloudCredentials.saveCredentials() } Kirigami.Heading { @@ -21,6 +19,7 @@ ColumnLayout { id: explanationText Layout.fillWidth: true Layout.margins: Kirigami.Units.gridUnit + Layout.topMargin: 0 text: "In order to use Subsurface-mobile you need to have a Subsurface cloud storage account " + "(which can be created with the Subsurface desktop application)." wrapMode: Text.WordWrap @@ -29,6 +28,7 @@ ColumnLayout { id: messageArea Layout.fillWidth: true Layout.margins: Kirigami.Units.gridUnit + Layout.topMargin: 0 text: manager.startPageText wrapMode: Text.WordWrap } @@ -36,7 +36,7 @@ ColumnLayout { id: cloudCredentials Layout.fillWidth: true Layout.margins: Kirigami.Units.gridUnit - Layout.topMargin: Kirigami.Units.gridUnit * 2 + Layout.topMargin: 0 property int headingLevel: 3 } } diff --git a/qt-mobile/qml/ThemeTest.qml b/qt-mobile/qml/ThemeTest.qml index b099b5722..c0916aea0 100644 --- a/qt-mobile/qml/ThemeTest.qml +++ b/qt-mobile/qml/ThemeTest.qml @@ -1,6 +1,7 @@ import QtQuick 2.5 import QtQuick.Controls 1.4 import QtQuick.Layouts 1.1 +import QtQuick.Window 2.2 import org.kde.kirigami 1.0 as Kirigami Kirigami.Page { @@ -62,7 +63,7 @@ Kirigami.Page { text: "Units.devicePixelRatio:" } Kirigami.Label { - text: Kirigami.Units.devicePixelRatio + text: Screen.devicePixelRatio } Kirigami.Heading { diff --git a/qt-mobile/qml/TopBar.qml b/qt-mobile/qml/TopBar.qml index cc99d9701..024b818b0 100644 --- a/qt-mobile/qml/TopBar.qml +++ b/qt-mobile/qml/TopBar.qml @@ -48,4 +48,12 @@ Rectangle { Layout.fillWidth: true } } + MouseArea { + anchors.fill: topPart + onClicked: { + if (stackView.depth == 1 && showingDiveList) { + scrollToTop() + } + } + } } diff --git a/qt-mobile/qml/main.qml b/qt-mobile/qml/main.qml index 675dad623..150e9769f 100644 --- a/qt-mobile/qml/main.qml +++ b/qt-mobile/qml/main.qml @@ -15,9 +15,10 @@ Kirigami.ApplicationWindow { property int oldStatus: -1 property alias accessingCloud: manager.accessingCloud property QtObject notification: null + property bool showingDiveList: false onAccessingCloudChanged: { if (accessingCloud) { - showPassiveNotification("Accessing Subsurface Cloud Storage", 5000); + showPassiveNotification("Accessing Subsurface Cloud Storage", 500000); } else { hidePassiveNotification(); } @@ -37,6 +38,10 @@ Kirigami.ApplicationWindow { detailsWindow.endEditMode() } + function scrollToTop() { + diveList.scrollToTop() + } + globalDrawer: Kirigami.GlobalDrawer { title: "Subsurface" titleIcon: "qrc:/qml/subsurface-mobile-icon.png" @@ -46,6 +51,14 @@ Kirigami.ApplicationWindow { Kirigami.Action { text: "Dive list" onTriggered: { + manager.appendTextToLog("requested dive list with credential status " + manager.credentialStatus) + if (manager.credentialStatus == QMLManager.UNKNOWN) { + // the user has asked to change credentials - if the credentials before that + // were valid, go back to dive list + if (oldStatus == QMLManager.VALID || oldStatus == QMLManager.VALID_EMAIL) { + manager.credentialStatus = oldStatus + } + } returnTopPage() globalDrawer.close() } @@ -58,7 +71,7 @@ Kirigami.ApplicationWindow { if (diveList.numDives > 0) { manager.startPageText = "Enter different credentials or return to dive list" } else { - manager.startPageText = "Enter valdi cloud storage credentials" + manager.startPageText = "Enter valid cloud storage credentials" } manager.credentialStatus = QMLManager.UNKNOWN @@ -103,6 +116,7 @@ Kirigami.ApplicationWindow { Kirigami.Action { text: "Refresh" onTriggered: { + globalDrawer.close() detailsWindow.endEditMode() manager.loadDives(); } @@ -110,6 +124,7 @@ Kirigami.ApplicationWindow { Action { text: "Upload to cloud" onTriggered: { + globalDrawer.close() detailsWindow.endEditMode() manager.saveChanges(); } @@ -178,13 +193,11 @@ Kirigami.ApplicationWindow { stackView.push(themetest) } } - Kirigami.Action { - checkable: true - checked: manager.verboseEnabled - text: checked ? "Disable verbose (for adb logcat)" : "Enable verbose (for adb logcat)" - onToggled: { - manager.verboseEnabled = checked; - } + }, + Kirigami.Action { + text: "User manual" + onTriggered: { + manager.showUserManual() } }, Kirigami.Action { @@ -240,8 +253,15 @@ Kirigami.ApplicationWindow { property color accentColor: "#2d5b9a" property color shadedColor: "#132744" property color accentTextColor: "#ececec" + property color diveListTextColor: Qt.rgba(0,0,0,0.76) // the Kirigami theme text color is too light property int columnWidth: Math.round(rootItem.width/(Kirigami.Units.gridUnit*30)) > 0 ? Math.round(rootItem.width / Math.round(rootItem.width/(Kirigami.Units.gridUnit*30))) : rootItem.width } +/* + toolBar: TopBar { + width: parent.width + height: Layout.minimumHeight + } + */ property Item stackView: pageStack pageStack.initialPage: DiveList { diff --git a/qt-mobile/qml/mobile-resources.qrc b/qt-mobile/qml/mobile-resources.qrc index f3fe82e08..a7d0013cf 100644 --- a/qt-mobile/qml/mobile-resources.qrc +++ b/qt-mobile/qml/mobile-resources.qrc @@ -24,41 +24,41 @@ <file alias="menu-back.png">icons/menu-back.png</file> </qresource> <qresource prefix="/imports"> - <file alias="org/kde/kirigami/qmldir">mobilecomponents/qmldir</file> - <file alias="org/kde/kirigami/Action.qml">mobilecomponents/Action.qml</file> - <file alias="org/kde/kirigami/ApplicationWindow.qml">mobilecomponents/ApplicationWindow.qml</file> - <file alias="org/kde/kirigami/BasicListItem.qml">mobilecomponents/BasicListItem.qml</file> - <file alias="org/kde/kirigami/GlobalDrawer.qml">mobilecomponents/GlobalDrawer.qml</file> - <file alias="org/kde/kirigami/ContextDrawer.qml">mobilecomponents/ContextDrawer.qml</file> - <file alias="org/kde/kirigami/Page.qml">mobilecomponents/Page.qml</file> - <file alias="org/kde/kirigami/ScrollablePage.qml">mobilecomponents/ScrollablePage.qml</file> - <file alias="org/kde/kirigami/Icon.qml">mobilecomponents/Icon.qml</file> - <file alias="org/kde/kirigami/Heading.qml">mobilecomponents/Heading.qml</file> - <file alias="org/kde/kirigami/OverlaySheet.qml">mobilecomponents/OverlaySheet.qml</file> - <file alias="org/kde/kirigami/ApplicationHeader.qml">mobilecomponents/ApplicationHeader.qml</file> - <file alias="org/kde/kirigami/private/PageRow.qml">mobilecomponents/private/PageRow.qml</file> - <file alias="org/kde/kirigami/Label.qml">mobilecomponents/Label.qml</file> - <file alias="org/kde/kirigami/AbstractListItem.qml">mobilecomponents/AbstractListItem.qml</file> - <file alias="org/kde/kirigami/ActionsForListItem.qml">mobilecomponents/ActionsForListItem.qml</file> - <file alias="org/kde/kirigami/OverlayDrawer.qml">mobilecomponents/OverlayDrawer.qml</file> - <file alias="org/kde/kirigami/Theme.qml">mobilecomponents/Theme.qml</file> - <file alias="org/kde/kirigami/Units.qml">mobilecomponents/Units.qml</file> - <file alias="org/kde/kirigami/private/RefreshableScrollView.qml">mobilecomponents/private/RefreshableScrollView.qml</file> - <file alias="org/kde/kirigami/private/ActionButton.qml">mobilecomponents/private/ActionButton.qml</file> - <file alias="org/kde/kirigami/private/MenuIcon.qml">mobilecomponents/private/MenuIcon.qml</file> - <file alias="org/kde/kirigami/private/ContextIcon.qml">mobilecomponents/private/ContextIcon.qml</file> - <file alias="org/kde/kirigami/private/AbstractDrawer.qml">mobilecomponents/private/AbstractDrawer.qml</file> - <file alias="org/kde/kirigami/private/PageStack.js">mobilecomponents/private/PageStack.js</file> - <file alias="org/kde/kirigami/private/PassiveNotification.qml">mobilecomponents/private/PassiveNotification.qml</file> - <file alias="org/kde/kirigami/icons/go-next.svg">mobilecomponents/icons/go-next.svg</file> - <file alias="org/kde/kirigami/icons/go-previous.svg">mobilecomponents/icons/go-previous.svg</file> - <file alias="org/kde/kirigami/icons/distribute-horizontal-x.svg">mobilecomponents/icons/distribute-horizontal-x.svg</file> - <file alias="org/kde/kirigami/icons/document-edit.svg">mobilecomponents/icons/document-edit.svg</file> - <file alias="org/kde/kirigami/icons/document-save.svg">mobilecomponents/icons/document-save.svg</file> - <file alias="org/kde/kirigami/icons/view-readermode.svg">mobilecomponents/icons/view-readermode.svg</file> - <file alias="org/kde/kirigami/icons/dialog-cancel.svg">mobilecomponents/icons/dialog-cancel.svg</file> - <file alias="org/kde/kirigami/icons/application-menu.svg">mobilecomponents/icons/application-menu.svg</file> - <file alias="org/kde/kirigami/icons/gps.svg">mobilecomponents/icons/gps.svg</file> - <file alias="org/kde/kirigami/icons/trash-empty.svg">mobilecomponents/icons/trash-empty.svg</file> + <file alias="org/kde/kirigami/qmldir">kirigami/qmldir</file> + <file alias="org/kde/kirigami/Action.qml">kirigami/Action.qml</file> + <file alias="org/kde/kirigami/ApplicationWindow.qml">kirigami/ApplicationWindow.qml</file> + <file alias="org/kde/kirigami/BasicListItem.qml">kirigami/BasicListItem.qml</file> + <file alias="org/kde/kirigami/GlobalDrawer.qml">kirigami/GlobalDrawer.qml</file> + <file alias="org/kde/kirigami/ContextDrawer.qml">kirigami/ContextDrawer.qml</file> + <file alias="org/kde/kirigami/Page.qml">kirigami/Page.qml</file> + <file alias="org/kde/kirigami/ScrollablePage.qml">kirigami/ScrollablePage.qml</file> + <file alias="org/kde/kirigami/Icon.qml">kirigami/Icon.qml</file> + <file alias="org/kde/kirigami/Heading.qml">kirigami/Heading.qml</file> + <file alias="org/kde/kirigami/OverlaySheet.qml">kirigami/OverlaySheet.qml</file> + <file alias="org/kde/kirigami/ApplicationHeader.qml">kirigami/ApplicationHeader.qml</file> + <file alias="org/kde/kirigami/private/PageRow.qml">kirigami/private/PageRow.qml</file> + <file alias="org/kde/kirigami/Label.qml">kirigami/Label.qml</file> + <file alias="org/kde/kirigami/AbstractListItem.qml">kirigami/AbstractListItem.qml</file> + <file alias="org/kde/kirigami/SwipeListItem.qml">kirigami/SwipeListItem.qml</file> + <file alias="org/kde/kirigami/OverlayDrawer.qml">kirigami/OverlayDrawer.qml</file> + <file alias="org/kde/kirigami/Theme.qml">kirigami/Theme.qml</file> + <file alias="org/kde/kirigami/Units.qml">kirigami/Units.qml</file> + <file alias="org/kde/kirigami/private/RefreshableScrollView.qml">kirigami/private/RefreshableScrollView.qml</file> + <file alias="org/kde/kirigami/private/ActionButton.qml">kirigami/private/ActionButton.qml</file> + <file alias="org/kde/kirigami/private/MenuIcon.qml">kirigami/private/MenuIcon.qml</file> + <file alias="org/kde/kirigami/private/ContextIcon.qml">kirigami/private/ContextIcon.qml</file> + <file alias="org/kde/kirigami/private/AbstractDrawer.qml">kirigami/private/AbstractDrawer.qml</file> + <file alias="org/kde/kirigami/private/PageStack.js">kirigami/private/PageStack.js</file> + <file alias="org/kde/kirigami/private/PassiveNotification.qml">kirigami/private/PassiveNotification.qml</file> + <file alias="org/kde/kirigami/icons/go-next.svg">kirigami/icons/go-next.svg</file> + <file alias="org/kde/kirigami/icons/go-previous.svg">kirigami/icons/go-previous.svg</file> + <file alias="org/kde/kirigami/icons/distribute-horizontal-x.svg">kirigami/icons/distribute-horizontal-x.svg</file> + <file alias="org/kde/kirigami/icons/document-edit.svg">kirigami/icons/document-edit.svg</file> + <file alias="org/kde/kirigami/icons/document-save.svg">kirigami/icons/document-save.svg</file> + <file alias="org/kde/kirigami/icons/view-readermode.svg">kirigami/icons/view-readermode.svg</file> + <file alias="org/kde/kirigami/icons/dialog-cancel.svg">kirigami/icons/dialog-cancel.svg</file> + <file alias="org/kde/kirigami/icons/application-menu.svg">kirigami/icons/application-menu.svg</file> + <file alias="org/kde/kirigami/icons/gps.svg">kirigami/icons/gps.svg</file> + <file alias="org/kde/kirigami/icons/trash-empty.svg">kirigami/icons/trash-empty.svg</file> </qresource> </RCC> diff --git a/qt-mobile/qmlmanager.cpp b/qt-mobile/qmlmanager.cpp index 6851ec079..301a02ce1 100644 --- a/qt-mobile/qmlmanager.cpp +++ b/qt-mobile/qmlmanager.cpp @@ -6,6 +6,7 @@ #include <QAuthenticator> #include <QDesktopServices> #include <QTextDocument> +#include <QRegularExpression> #include "qt-models/divelistmodel.h" #include <gpslistmodel.h> @@ -19,6 +20,9 @@ QMLManager *QMLManager::m_instance = NULL; +#define RED_FONT QLatin1Literal("<font color=\"red\">") +#define END_FONT QLatin1Literal("</font>") + static void appendTextToLogStandalone(const char *text) { QMLManager *self = QMLManager::instance(); @@ -42,10 +46,11 @@ extern "C" int gitProgressCB(int percent) QMLManager::QMLManager() : m_locationServiceEnabled(false), m_verboseEnabled(false), - m_credentialStatus(UNKNOWN), reply(0), deletedDive(0), - deletedTrip(0) + deletedTrip(0), + m_credentialStatus(UNKNOWN), + m_lastDevicePixelRatio(1.0) { m_instance = this; appendTextToLog(getUserAgent()); @@ -98,7 +103,6 @@ void QMLManager::finishSetup() // Initialize cloud credentials. setCloudUserName(prefs.cloud_storage_email); setCloudPassword(prefs.cloud_storage_password); - setSaveCloudPassword(prefs.save_password_local); // if the cloud credentials are valid, we should get the GPS Webservice ID as well QString url; if (!cloudUserName().isEmpty() && @@ -108,7 +112,7 @@ void QMLManager::finishSetup() } else { setCredentialStatus(INCOMPLETE); appendTextToLog(QStringLiteral("no cloud credentials")); - setStartPageText(tr("Please enter valid cloud credentials.")); + setStartPageText(RED_FONT + tr("Please enter valid cloud credentials.") + END_FONT); } setDistanceThreshold(prefs.distance_threshold); setTimeThreshold(prefs.time_threshold / 60); @@ -144,28 +148,22 @@ void QMLManager::saveCloudCredentials() bool cloudCredentialsChanged = false; s.beginGroup("CloudStorage"); s.setValue("email", cloudUserName()); - s.setValue("save_password_local", saveCloudPassword()); - if (saveCloudPassword()) - s.setValue("password", cloudPassword()); + s.setValue("password", cloudPassword()); s.sync(); if (!same_string(prefs.cloud_storage_email, qPrintable(cloudUserName()))) { free(prefs.cloud_storage_email); prefs.cloud_storage_email = strdup(qPrintable(cloudUserName())); cloudCredentialsChanged = true; } - if (saveCloudPassword() != prefs.save_password_local) - prefs.save_password_local = saveCloudPassword(); cloudCredentialsChanged |= !same_string(prefs.cloud_storage_password, qPrintable(cloudPassword())); - if (saveCloudPassword()) { - if (!same_string(prefs.cloud_storage_password, qPrintable(cloudPassword()))) { - free(prefs.cloud_storage_password); - prefs.cloud_storage_password = strdup(qPrintable(cloudPassword())); - } + if (!same_string(prefs.cloud_storage_password, qPrintable(cloudPassword()))) { + free(prefs.cloud_storage_password); + prefs.cloud_storage_password = strdup(qPrintable(cloudPassword())); } if (cloudUserName().isEmpty() || cloudPassword().isEmpty()) { - setStartPageText(tr("Please enter valid cloud credentials.")); + setStartPageText(RED_FONT + tr("Please enter valid cloud credentials.") + END_FONT); } else if (cloudCredentialsChanged) { free(prefs.userid); prefs.userid = NULL; @@ -209,6 +207,7 @@ void QMLManager::tryRetrieveDataFromBackend() void QMLManager::loadDives() { + setAccessingCloud(true); checkCredentialsAndExecute(&QMLManager::loadDivesWithValidCredentials); } @@ -218,7 +217,7 @@ void QMLManager::provideAuth(QNetworkReply *reply, QAuthenticator *auth) auth->password() == QString(prefs.cloud_storage_password)) { // OK, credentials have been tried and didn't work, so they are invalid appendTextToLog("Cloud credentials are invalid"); - setStartPageText(tr("Cloud credentials are invalid")); + setStartPageText(RED_FONT + tr("Cloud credentials are invalid") + END_FONT); setCredentialStatus(INVALID); reply->disconnect(); reply->abort(); @@ -231,7 +230,7 @@ void QMLManager::provideAuth(QNetworkReply *reply, QAuthenticator *auth) void QMLManager::handleSslErrors(const QList<QSslError> &errors) { - setStartPageText(tr("Cannot open cloud storage: Error creating https connection")); + setStartPageText(RED_FONT + tr("Cannot open cloud storage: Error creating https connection") + END_FONT); Q_FOREACH (QSslError e, errors) { qDebug() << e.errorString(); } @@ -244,7 +243,7 @@ void QMLManager::handleError(QNetworkReply::NetworkError nError) { QString errorString = reply->errorString(); qDebug() << "handleError" << nError << errorString; - setStartPageText(tr("Cannot open cloud storage: %1").arg(errorString)); + setStartPageText(RED_FONT + tr("Cannot open cloud storage: %1").arg(errorString) + END_FONT); reply->abort(); reply->deleteLater(); setAccessingCloud(false); @@ -253,7 +252,7 @@ void QMLManager::handleError(QNetworkReply::NetworkError nError) void QMLManager::retrieveUserid() { if (reply->attribute(QNetworkRequest::HttpStatusCodeAttribute) != 302) { - appendTextToLog(QStringLiteral("Cloud storage connection not working correctly: ") + reply->readAll()); + appendTextToLog(QStringLiteral("Cloud storage connection not working correctly: %1").arg(QString(reply->readAll()))); setAccessingCloud(false); return; } @@ -293,7 +292,7 @@ void QMLManager::loadDivesWithValidCredentials() { if (reply->attribute(QNetworkRequest::HttpStatusCodeAttribute) != 302) { appendTextToLog(QStringLiteral("Cloud storage connection not working correctly: ") + reply->readAll()); - setStartPageText(tr("Cannot connect to cloud storage")); + setStartPageText(RED_FONT + tr("Cannot connect to cloud storage") + END_FONT); setAccessingCloud(false); return; } @@ -305,7 +304,7 @@ void QMLManager::loadDivesWithValidCredentials() if (getCloudURL(url)) { QString errorString(get_error_string()); appendTextToLog(errorString); - setStartPageText(tr("Cloud storage error: %1").arg(errorString)); + setStartPageText(RED_FONT + tr("Cloud storage error: %1").arg(errorString) + END_FONT); setAccessingCloud(false); return; } @@ -331,7 +330,7 @@ void QMLManager::loadDivesWithValidCredentials() report_error("failed to open file %s", fileNamePrt.data()); QString errorString(get_error_string()); appendTextToLog(errorString); - setStartPageText(tr("Cloud storage error: %1").arg(errorString)); + setStartPageText(RED_FONT + tr("Cloud storage error: %1").arg(errorString) + END_FONT); return; } prefs.unit_system = informational_prefs.unit_system; @@ -415,6 +414,76 @@ void QMLManager::commitChanges(QString diveId, QString date, QString location, Q date.replace(drop, ""); } newDate = QDateTime::fromString(date, format); + if (!newDate.isValid()) { + qDebug() << "unable to parse date" << date << "with the given format" << format; + QRegularExpression isoDate("\\d+-\\d+-\\d+[^\\d]+\\d+:\\d+"); + if (date.contains(isoDate)) { + newDate = QDateTime::fromString(date, "yyyy-M-d h:m:s"); + if (newDate.isValid()) + goto parsed; + newDate = QDateTime::fromString(date, "yy-M-d h:m:s"); + if (newDate.isValid()) + goto parsed; + } + QRegularExpression isoDateNoSecs("\\d+-\\d+-\\d+[^\\d]+\\d+"); + if (date.contains(isoDateNoSecs)) { + newDate = QDateTime::fromString(date, "yyyy-M-d h:m"); + if (newDate.isValid()) + goto parsed; + newDate = QDateTime::fromString(date, "yy-M-d h:m"); + if (newDate.isValid()) + goto parsed; + } + QRegularExpression usDate("\\d+/\\d+/\\d+[^\\d]+\\d+:\\d+:\\d+"); + if (date.contains(usDate)) { + newDate = QDateTime::fromString(date, "M/d/yyyy h:m:s"); + if (newDate.isValid()) + goto parsed; + newDate = QDateTime::fromString(date, "M/d/yy h:m:s"); + if (newDate.isValid()) + goto parsed; + newDate = QDateTime::fromString(date.toLower(), "M/d/yyyy h:m:sap"); + if (newDate.isValid()) + goto parsed; + newDate = QDateTime::fromString(date.toLower(), "M/d/yy h:m:sap"); + if (newDate.isValid()) + goto parsed; + } + QRegularExpression usDateNoSecs("\\d+/\\d+/\\d+[^\\d]+\\d+:\\d+"); + if (date.contains(usDateNoSecs)) { + newDate = QDateTime::fromString(date, "M/d/yyyy h:m"); + if (newDate.isValid()) + goto parsed; + newDate = QDateTime::fromString(date, "M/d/yy h:m"); + if (newDate.isValid()) + goto parsed; + newDate = QDateTime::fromString(date.toLower(), "M/d/yyyy h:map"); + if (newDate.isValid()) + goto parsed; + newDate = QDateTime::fromString(date.toLower(), "M/d/yy h:map"); + if (newDate.isValid()) + goto parsed; + } + QRegularExpression leDate("\\d+\\.\\d+\\.\\d+[^\\d]+\\d+:\\d+:\\d+"); + if (date.contains(leDate)) { + newDate = QDateTime::fromString(date, "d.M.yyyy h:m:s"); + if (newDate.isValid()) + goto parsed; + newDate = QDateTime::fromString(date, "d.M.yy h:m:s"); + if (newDate.isValid()) + goto parsed; + } + QRegularExpression leDateNoSecs("\\d+\\.\\d+\\.\\d+[^\\d]+\\d+:\\d+"); + if (date.contains(leDateNoSecs)) { + newDate = QDateTime::fromString(date, "d.M.yyyy h:m"); + if (newDate.isValid()) + goto parsed; + newDate = QDateTime::fromString(date, "d.M.yy h:m"); + if (newDate.isValid()) + goto parsed; + } + } +parsed: if (newDate.isValid()) { // stupid Qt... two digit years are always 19xx - WTF??? // so if adding a hundred years gets you into something before a year from now... @@ -422,6 +491,8 @@ void QMLManager::commitChanges(QString diveId, QString date, QString location, Q if (newDate.addYears(100) < QDateTime::currentDateTime().addYears(1)) newDate = newDate.addYears(100); d->dc.when = d->when = newDate.toMSecsSinceEpoch() / 1000 + gettimezoneoffset(newDate.toMSecsSinceEpoch() / 1000); + } else { + qDebug() << "none of our parsing attempts worked for the date string"; } } struct dive_site *ds = get_dive_site_by_uuid(d->dive_site_uuid); @@ -532,15 +603,17 @@ void QMLManager::commitChanges(QString diveId, QString date, QString location, Q diveChanged = true; d->cylinder[0].start.mbar = parsePressureToMbar(startpressure); d->cylinder[0].end.mbar = parsePressureToMbar(endpressure); + if (d->cylinder[0].end.mbar > d->cylinder[0].start.mbar) + d->cylinder[0].end.mbar = d->cylinder[0].start.mbar; } // gasmix for first cylinder if (get_gas_string(d->cylinder[0].gasmix) != gasmix) { int o2 = parseGasMixO2(gasmix); int he = parseGasMixHE(gasmix); // the QML code SHOULD only accept valid gas mixes, but just to make sure - if (o2 >= 0 && o2 <= 100 && - he >= 0 && he <= 100 && - o2 + he <= 100) { + if (o2 >= 0 && o2 <= 1000 && + he >= 0 && he <= 1000 && + o2 + he <= 1000) { diveChanged = true; d->cylinder[0].gasmix.o2.permille = o2; d->cylinder[0].gasmix.he.permille = he; @@ -623,8 +696,8 @@ void QMLManager::saveChanges() appendTextToLog(get_error_string()); return; } - - setAccessingCloud(true); + if (prefs.git_local_only == false) + setAccessingCloud(true); if (save_dives(fileName.toUtf8().data())) { appendTextToLog(get_error_string()); setAccessingCloud(false); @@ -772,16 +845,6 @@ void QMLManager::appendTextToLog(const QString &newText) emit logTextChanged(); } -bool QMLManager::saveCloudPassword() const -{ - return m_saveCloudPassword; -} - -void QMLManager::setSaveCloudPassword(bool saveCloudPassword) -{ - m_saveCloudPassword = saveCloudPassword; -} - bool QMLManager::locationServiceEnabled() const { return m_locationServiceEnabled; @@ -824,7 +887,7 @@ QString QMLManager::cloudUserName() const void QMLManager::setCloudUserName(const QString &cloudUserName) { - m_cloudUserName = cloudUserName; + m_cloudUserName = cloudUserName.toLower(); emit cloudUserNameChanged(); } @@ -906,6 +969,13 @@ void QMLManager::showMap(const QString& location) } } +#define MOBILEUSERMANUAL QUrl(QLatin1Literal("https://subsurface-divelog.org/documentation/subsurface-mobile-user-manual/")) + +void QMLManager::showUserManual() +{ + QDesktopServices::openUrl(MOBILEUSERMANUAL); +} + // where in the QML dive list is that dive? int QMLManager::getIndex(const QString &diveId) { @@ -953,3 +1023,14 @@ void QMLManager::setAccessingCloud(bool status) m_accessingCloud = status; emit accessingCloudChanged(); } + +qreal QMLManager::lastDevicePixelRatio() +{ + return m_lastDevicePixelRatio; +} + +void QMLManager::screenChanged(QScreen *screen) +{ + m_lastDevicePixelRatio = screen->devicePixelRatio(); + emit sendScreenChanged(screen); +} diff --git a/qt-mobile/qmlmanager.h b/qt-mobile/qmlmanager.h index ff3507991..2113a1dfe 100644 --- a/qt-mobile/qmlmanager.h +++ b/qt-mobile/qmlmanager.h @@ -4,6 +4,7 @@ #include <QObject> #include <QString> #include <QNetworkAccessManager> +#include <QScreen> #include "gpslocation.h" @@ -12,7 +13,6 @@ class QMLManager : public QObject { Q_ENUMS(credentialStatus_t) Q_PROPERTY(QString cloudUserName READ cloudUserName WRITE setCloudUserName NOTIFY cloudUserNameChanged) Q_PROPERTY(QString cloudPassword READ cloudPassword WRITE setCloudPassword NOTIFY cloudPasswordChanged) - Q_PROPERTY(bool saveCloudPassword READ saveCloudPassword WRITE setSaveCloudPassword NOTIFY saveCloudPasswordChanged) Q_PROPERTY(QString logText READ logText WRITE setLogText NOTIFY logTextChanged) Q_PROPERTY(bool locationServiceEnabled READ locationServiceEnabled WRITE setLocationServiceEnabled NOTIFY locationServiceEnabledChanged) Q_PROPERTY(int distanceThreshold READ distanceThreshold WRITE setDistanceThreshold NOTIFY distanceThresholdChanged) @@ -43,9 +43,6 @@ public: QString cloudPassword() const; void setCloudPassword(const QString &cloudPassword); - bool saveCloudPassword() const; - void setSaveCloudPassword(bool saveCloudPassword); - bool locationServiceEnabled() const; void setLocationServiceEnabled(bool locationServiceEnable); @@ -70,7 +67,6 @@ public: QString logText() const; void setLogText(const QString &logText); - void appendTextToLog(const QString &newText); bool accessingCloud() const; void setAccessingCloud(bool status); @@ -108,6 +104,7 @@ public slots: void finishSetup(); void openLocalThenRemote(QString url); void showMap(const QString& location); + void showUserManual(); int getIndex(const QString& diveId); QString getNumber(const QString& diveId); QString getDate(const QString& diveId); @@ -115,13 +112,15 @@ public slots: QString getVersion() const; void deleteGpsFix(quint64 when); void refreshDiveList(); + void screenChanged(QScreen *screen); + qreal lastDevicePixelRatio(); + void appendTextToLog(const QString &newText); private: QString m_cloudUserName; QString m_cloudPassword; QString m_ssrfGpsWebUserid; QString m_startPageText; - bool m_saveCloudPassword; QString m_logText; bool m_locationServiceEnabled; bool m_verboseEnabled; @@ -136,11 +135,11 @@ private: struct dive_trip *deletedTrip; bool m_accessingCloud; credentialStatus_t m_credentialStatus; + qreal m_lastDevicePixelRatio; signals: void cloudUserNameChanged(); void cloudPasswordChanged(); - void saveCloudPasswordChanged(); void locationServiceEnabledChanged(); void verboseEnabledChanged(); void logTextChanged(); @@ -150,6 +149,7 @@ signals: void startPageTextChanged(); void credentialStatusChanged(); void accessingCloudChanged(); + void sendScreenChanged(QScreen *screen); }; #endif diff --git a/qt-mobile/qmlprofile.cpp b/qt-mobile/qmlprofile.cpp index 512aa6a3a..ad686561d 100644 --- a/qt-mobile/qmlprofile.cpp +++ b/qt-mobile/qmlprofile.cpp @@ -1,7 +1,10 @@ #include "qmlprofile.h" +#include "qmlmanager.h" #include "profile-widget/profilewidget2.h" #include "subsurface-core/dive.h" +#include "subsurface-core/metrics.h" #include <QTransform> +#include <QScreen> QMLProfile::QMLProfile(QQuickItem *parent) : QQuickPaintedItem(parent), @@ -13,7 +16,8 @@ QMLProfile::QMLProfile(QQuickItem *parent) : m_profileWidget->setProfileState(); m_profileWidget->setPrintMode(true); m_profileWidget->setFontPrintScale(0.8); - //m_profileWidget->setGeometry(this->geometry()); + connect(QMLManager::instance(), &QMLManager::sendScreenChanged, this, &QMLProfile::screenChanged); + setDevicePixelRatio(QMLManager::instance()->lastDevicePixelRatio()); } QMLProfile::~QMLProfile() @@ -24,13 +28,43 @@ QMLProfile::~QMLProfile() void QMLProfile::paint(QPainter *painter) { // let's look at the intended size of the content and scale our scene accordingly - QRect rect = m_profileWidget->contentsRect(); + QRect painterRect = painter->viewport(); + QRect profileRect = m_profileWidget->viewport()->rect(); + // qDebug() << "profile viewport and painter viewport" << profileRect << painterRect; qreal sceneSize = 104; // that should give us 2% margin all around (100x100 scene) - qreal sx = rect.width() / sceneSize; - qreal sy = rect.height() / sceneSize; - QTransform profileTransform; + qreal dprComp = devicePixelRatio() * painterRect.width() / profileRect.width(); + qreal sx = painterRect.width() / sceneSize / dprComp; + qreal sy = painterRect.height() / sceneSize / dprComp; + + // next figure out the weird magic by which we need to shift the painter so the profile is shown + int dpr = rint(devicePixelRatio()); + qreal magicShiftFactor = (dpr == 2 ? 0.25 : (dpr == 3 ? 0.33 : 0.0)); + + // now set up the transformations scale the profile and + // shift the painter (taking its existing transformation into account) + QTransform profileTransform = QTransform(); profileTransform.scale(sx, sy); + QTransform painterTransform = painter->transform(); + painterTransform.translate(-painterRect.width() * magicShiftFactor ,-painterRect.height() * magicShiftFactor); + +#if PROFILE_SCALING_DEBUG + // some debugging messages to help adjust this in case the magic above is insufficient + QMLManager::instance()->appendTextToLog(QString("dpr %1 profile viewport %2 %3 painter viewport %4 %5").arg(dpr).arg(profileRect.width()).arg(profileRect.height()) + .arg(painterRect.width()).arg(painterRect.height())); + QMLManager::instance()->appendTextToLog(QString("profile matrix %1 %2 %3 %4 %5 %6 %7 %8 %9").arg(profileTransform.m11()).arg(profileTransform.m12()).arg(profileTransform.m13()) + .arg(profileTransform.m21()).arg(profileTransform.m22()).arg(profileTransform.m23()) + .arg(profileTransform.m31()).arg(profileTransform.m32()).arg(profileTransform.m33())); + QMLManager::instance()->appendTextToLog(QString("painter matrix %1 %2 %3 %4 %5 %6 %7 %8 %9").arg(painterTransform.m11()).arg(painterTransform.m12()).arg(painterTransform.m13()) + .arg(painterTransform.m21()).arg(painterTransform.m22()).arg(painterTransform.m23()) + .arg(painterTransform.m31()).arg(painterTransform.m32()).arg(painterTransform.m33())); + qDebug() << "profile scaled by" << profileTransform.m11() << profileTransform.m22() << "and translated by" << profileTransform.m31() << profileTransform.m32(); + qDebug() << "exist profile transform" << m_profileWidget->transform() << "painter transform" << painter->transform(); +#endif + // apply the transformation + painter->setTransform(painterTransform); m_profileWidget->setTransform(profileTransform); + + // finally, render the profile m_profileWidget->render(painter); } @@ -65,6 +99,13 @@ void QMLProfile::setDevicePixelRatio(qreal dpr) { if (dpr != m_devicePixelRatio) { m_devicePixelRatio = dpr; + m_profileWidget->setFontPrintScale(0.8 * dpr); + updateDevicePixelRatio(dpr); emit devicePixelRatioChanged(); } } + +void QMLProfile::screenChanged(QScreen *screen) +{ + setDevicePixelRatio(screen->devicePixelRatio()); +} diff --git a/qt-mobile/qmlprofile.h b/qt-mobile/qmlprofile.h index 35332ce8d..c8a77d700 100644 --- a/qt-mobile/qmlprofile.h +++ b/qt-mobile/qmlprofile.h @@ -24,11 +24,13 @@ public: public slots: void setMargin(int margin); + void screenChanged(QScreen *screen); private: QString m_diveId; qreal m_devicePixelRatio; int m_margin; ProfileWidget2 *m_profileWidget; + signals: void rightAlignedChanged(); void diveIdChanged(); diff --git a/qt-models/cleanertablemodel.cpp b/qt-models/cleanertablemodel.cpp index d2405d42f..77d3f3369 100644 --- a/qt-models/cleanertablemodel.cpp +++ b/qt-models/cleanertablemodel.cpp @@ -7,6 +7,7 @@ CleanerTableModel::CleanerTableModel(QObject *parent) : QAbstractTableModel(pare int CleanerTableModel::columnCount(const QModelIndex &parent) const { + Q_UNUSED(parent); return headers.count(); } diff --git a/qt-models/cylindermodel.cpp b/qt-models/cylindermodel.cpp index 87edd5fe0..af01650a4 100644 --- a/qt-models/cylindermodel.cpp +++ b/qt-models/cylindermodel.cpp @@ -286,6 +286,7 @@ bool CylindersModel::setData(const QModelIndex &index, const QVariant &value, in int CylindersModel::rowCount(const QModelIndex &parent) const { + Q_UNUSED(parent); return rows; } diff --git a/qt-models/divecomputerextradatamodel.cpp b/qt-models/divecomputerextradatamodel.cpp index 8c0c828e3..0f89a2a6b 100644 --- a/qt-models/divecomputerextradatamodel.cpp +++ b/qt-models/divecomputerextradatamodel.cpp @@ -51,6 +51,7 @@ QVariant ExtraDataModel::data(const QModelIndex &index, int role) const int ExtraDataModel::rowCount(const QModelIndex &parent) const { + Q_UNUSED(parent); return rows; } diff --git a/qt-models/divecomputermodel.cpp b/qt-models/divecomputermodel.cpp index 51b1a767b..58641ff77 100644 --- a/qt-models/divecomputermodel.cpp +++ b/qt-models/divecomputermodel.cpp @@ -2,7 +2,7 @@ #include "dive.h" #include "divelist.h" -DiveComputerModel::DiveComputerModel(QMultiMap<QString, DiveComputerNode> &dcMap, QObject *parent) : CleanerTableModel() +DiveComputerModel::DiveComputerModel(QMultiMap<QString, DiveComputerNode> &dcMap, QObject *parent) : CleanerTableModel(parent) { setHeaderDataStrings(QStringList() << "" << tr("Model") << tr("Device ID") << tr("Nickname")); dcWorkingMap = dcMap; @@ -47,6 +47,7 @@ QVariant DiveComputerModel::data(const QModelIndex &index, int role) const int DiveComputerModel::rowCount(const QModelIndex &parent) const { + Q_UNUSED(parent); return numRows; } @@ -78,6 +79,10 @@ Qt::ItemFlags DiveComputerModel::flags(const QModelIndex &index) const bool DiveComputerModel::setData(const QModelIndex &index, const QVariant &value, int role) { + // We should test if the role == Qt::EditRole + Q_UNUSED(role); + + // WARN: This seems wrong - The values don't are ordered - we need a map from the Key to Index, or something. QList<DiveComputerNode> values = dcWorkingMap.values(); DiveComputerNode node = values.at(index.row()); dcWorkingMap.remove(node.model, node); diff --git a/qt-models/divelocationmodel.cpp b/qt-models/divelocationmodel.cpp index d185de1fe..f77953760 100644 --- a/qt-models/divelocationmodel.cpp +++ b/qt-models/divelocationmodel.cpp @@ -24,6 +24,7 @@ LocationInformationModel::LocationInformationModel(QObject *obj) : QAbstractTabl int LocationInformationModel::columnCount(const QModelIndex &parent) const { + Q_UNUSED(parent); return COLUMNS; } @@ -159,6 +160,8 @@ bool LocationInformationModel::setData(const QModelIndex &index, const QVariant bool LocationInformationModel::removeRows(int row, int count, const QModelIndex & parent) { + Q_UNUSED(count); + Q_UNUSED(parent); if(row >= rowCount()) return false; diff --git a/qt-models/divepicturemodel.cpp b/qt-models/divepicturemodel.cpp index 602663ec1..173cf9dd0 100644 --- a/qt-models/divepicturemodel.cpp +++ b/qt-models/divepicturemodel.cpp @@ -78,6 +78,7 @@ void DivePictureModel::updateDivePictures() int DivePictureModel::columnCount(const QModelIndex &parent) const { + Q_UNUSED(parent); return 2; } @@ -126,5 +127,6 @@ void DivePictureModel::removePicture(const QString &fileUrl, bool last) int DivePictureModel::rowCount(const QModelIndex &parent) const { + Q_UNUSED(parent); return numberOfPictures; } diff --git a/qt-models/diveplannermodel.cpp b/qt-models/diveplannermodel.cpp index eeae69a87..c3996d077 100644 --- a/qt-models/diveplannermodel.cpp +++ b/qt-models/diveplannermodel.cpp @@ -25,7 +25,7 @@ void DivePlannerPointsModel::removeSelectedPoints(const QVector<int> &rows) void DivePlannerPointsModel::createSimpleDive() { - struct gasmix gas = { 0 }; + struct gasmix gas = {}; // initialize the start time in the plan diveplan.when = displayed_dive.when; @@ -201,6 +201,7 @@ bool DivePlannerPointsModel::recalcQ() int DivePlannerPointsModel::columnCount(const QModelIndex &parent) const { + Q_UNUSED(parent); return COLUMNS; // to disable CCSETPOINT subtract one } @@ -253,7 +254,7 @@ QVariant DivePlannerPointsModel::data(const QModelIndex &index, int role) const bool DivePlannerPointsModel::setData(const QModelIndex &index, const QVariant &value, int role) { - struct gasmix gas = { 0 }; + struct gasmix gas = {}; int i, shift; if (role == Qt::EditRole) { divedatapoint &p = divepoints[index.row()]; @@ -295,7 +296,7 @@ void DivePlannerPointsModel::gaschange(const QModelIndex &index, QString newgas) { int i = index.row(); gasmix oldgas = divepoints[i].gasmix; - gasmix gas = { 0 }; + gasmix gas = {}; if (!validate_gas(newgas.toUtf8().data(), &gas)) return; while (i < rowCount() && gasmix_distance(&oldgas, &divepoints[i].gasmix) == 0) @@ -334,6 +335,7 @@ Qt::ItemFlags DivePlannerPointsModel::flags(const QModelIndex &index) const int DivePlannerPointsModel::rowCount(const QModelIndex &parent) const { + Q_UNUSED(parent); return divepoints.count(); } @@ -479,7 +481,10 @@ void DivePlannerPointsModel::setSafetyStop(bool value) void DivePlannerPointsModel::setReserveGas(int reserve) { - prefs.reserve_gas = reserve * 1000; + if (prefs.units.pressure == units::BAR) + prefs.reserve_gas = reserve * 1000; + else + prefs.reserve_gas = psi_to_mbar(reserve); emit dataChanged(createIndex(0, 0), createIndex(rowCount() - 1, COLUMNS - 1)); } @@ -586,8 +591,8 @@ int DivePlannerPointsModel::lastEnteredPoint() int DivePlannerPointsModel::addStop(int milimeters, int seconds, gasmix *gas_in, int ccpoint, bool entered) { - struct gasmix air = { 0 }; - struct gasmix gas = { 0 }; + struct gasmix air = {}; + struct gasmix gas = {}; bool usePrevious = false; if (gas_in) gas = *gas_in; diff --git a/qt-models/diveplotdatamodel.cpp b/qt-models/diveplotdatamodel.cpp index 1110f19df..7a7ab195f 100644 --- a/qt-models/diveplotdatamodel.cpp +++ b/qt-models/diveplotdatamodel.cpp @@ -14,6 +14,7 @@ DivePlotDataModel::DivePlotDataModel(QObject *parent) : int DivePlotDataModel::columnCount(const QModelIndex &parent) const { + Q_UNUSED(parent); return COLUMNS; } @@ -96,6 +97,7 @@ const plot_info &DivePlotDataModel::data() const int DivePlotDataModel::rowCount(const QModelIndex &parent) const { + Q_UNUSED(parent); return pInfo.nr; } diff --git a/qt-models/gpslistmodel.cpp b/qt-models/gpslistmodel.cpp index 84f5e7f3a..3ea03f040 100644 --- a/qt-models/gpslistmodel.cpp +++ b/qt-models/gpslistmodel.cpp @@ -35,6 +35,7 @@ void GpsListModel::clear() int GpsListModel::rowCount(const QModelIndex &parent) const { + Q_UNUSED(parent); return m_gpsFixes.count(); } diff --git a/qt-models/models.cpp b/qt-models/models.cpp index 6f6b501de..48b22797c 100644 --- a/qt-models/models.cpp +++ b/qt-models/models.cpp @@ -26,6 +26,7 @@ const QPixmap &trashForbiddenIcon() Qt::ItemFlags GasSelectionModel::flags(const QModelIndex &index) const { + Q_UNUSED(index); return Qt::ItemIsEnabled | Qt::ItemIsSelectable; } @@ -94,5 +95,6 @@ QVariant LanguageModel::data(const QModelIndex &index, int role) const int LanguageModel::rowCount(const QModelIndex &parent) const { + Q_UNUSED(parent); return languages.count(); } diff --git a/qt-models/tankinfomodel.cpp b/qt-models/tankinfomodel.cpp index 0a06a3b08..b32437392 100644 --- a/qt-models/tankinfomodel.cpp +++ b/qt-models/tankinfomodel.cpp @@ -16,6 +16,7 @@ const QString &TankInfoModel::biggerString() const bool TankInfoModel::insertRows(int row, int count, const QModelIndex &parent) { + Q_UNUSED(row); beginInsertRows(parent, rowCount(), rowCount()); rows += count; endInsertRows(); @@ -24,6 +25,8 @@ bool TankInfoModel::insertRows(int row, int count, const QModelIndex &parent) bool TankInfoModel::setData(const QModelIndex &index, const QVariant &value, int role) { + //WARN Seems wrong, we need to check for role == Qt::EditRole + Q_UNUSED(role); struct tank_info_t *info = &tank_info[index.row()]; switch (index.column()) { case DESCRIPTION: @@ -78,6 +81,7 @@ QVariant TankInfoModel::data(const QModelIndex &index, int role) const int TankInfoModel::rowCount(const QModelIndex &parent) const { + Q_UNUSED(parent); return rows + 1; } diff --git a/qt-models/treemodel.cpp b/qt-models/treemodel.cpp index 558f690b2..01db3520f 100644 --- a/qt-models/treemodel.cpp +++ b/qt-models/treemodel.cpp @@ -13,6 +13,7 @@ TreeItem::~TreeItem() Qt::ItemFlags TreeItem::flags(const QModelIndex &index) const { + Q_UNUSED(index); return Qt::ItemIsEnabled | Qt::ItemIsSelectable; } @@ -25,6 +26,8 @@ int TreeItem::row() const QVariant TreeItem::data(int column, int role) const { + Q_UNUSED(column); + Q_UNUSED(role); return QVariant(); } @@ -55,6 +58,9 @@ QVariant TreeModel::data(const QModelIndex &index, int role) const bool TreeItem::setData(const QModelIndex &index, const QVariant &value, int role) { + Q_UNUSED(index); + Q_UNUSED(value); + Q_UNUSED(role); return false; } @@ -99,5 +105,6 @@ int TreeModel::rowCount(const QModelIndex &parent) const int TreeModel::columnCount(const QModelIndex &parent) const { + Q_UNUSED(parent); return columns; } diff --git a/qt-models/weightmodel.cpp b/qt-models/weightmodel.cpp index 88ebeff6b..1ab8c24c8 100644 --- a/qt-models/weightmodel.cpp +++ b/qt-models/weightmodel.cpp @@ -143,6 +143,7 @@ Qt::ItemFlags WeightModel::flags(const QModelIndex &index) const int WeightModel::rowCount(const QModelIndex &parent) const { + Q_UNUSED(parent); return rows; } diff --git a/qt-models/weigthsysteminfomodel.cpp b/qt-models/weigthsysteminfomodel.cpp index 1ddc2e940..daa305284 100644 --- a/qt-models/weigthsysteminfomodel.cpp +++ b/qt-models/weigthsysteminfomodel.cpp @@ -11,6 +11,7 @@ WSInfoModel *WSInfoModel::instance() bool WSInfoModel::insertRows(int row, int count, const QModelIndex &parent) { + Q_UNUSED(row); beginInsertRows(parent, rowCount(), rowCount()); rows += count; endInsertRows(); @@ -19,6 +20,8 @@ bool WSInfoModel::insertRows(int row, int count, const QModelIndex &parent) bool WSInfoModel::setData(const QModelIndex &index, const QVariant &value, int role) { + //WARN: check for Qt::EditRole + Q_UNUSED(role); struct ws_info_t *info = &ws_info[index.row()]; switch (index.column()) { case DESCRIPTION: @@ -66,6 +69,7 @@ QVariant WSInfoModel::data(const QModelIndex &index, int role) const int WSInfoModel::rowCount(const QModelIndex &parent) const { + Q_UNUSED(parent); return rows + 1; } diff --git a/scripts/build.sh b/scripts/build.sh index e4164db4f..014d2d32b 100755 --- a/scripts/build.sh +++ b/scripts/build.sh @@ -23,6 +23,18 @@ exec 1> >(tee build.log) 2>&1 SRC=$(pwd) PLATFORM=$(uname) +# Verify that the Xcode Command Line Tools are installed +if [ $PLATFORM = Darwin ] ; then + if [ ! -d /usr/include ] ; then + echo "Error: Xcode Command Line Tools are not installed" + echo "" + echo "Please run:" + echo " xcode-select --install" + echo "to install them (you'll have to agree to Apple's licensing terms etc), then run build.sh again" + exit 1; + fi +fi + # normally this script builds the desktop version in subsurface/build # if the first argument is "-mobile" then build Subsurface-mobile in subsurface/build-mobile # if the first argument is "-both" then build both in subsurface/build and subsurface/build-mobile @@ -116,7 +128,7 @@ cd build if [ ! -f ../configure ] ; then autoreconf --install .. fi -../configure --prefix=$INSTALL_ROOT +../configure --prefix=$INSTALL_ROOT --disable-examples make -j4 make install @@ -140,10 +152,13 @@ fi mkdir -p build cd build if [ $PLATFORM = Darwin ] ; then - if [ -d "~/Qt/5.5" ] ; then + if [ -d "$HOME/Qt/5.5" ] ; then export CMAKE_PREFIX_PATH=~/Qt/5.5/clang_64/lib/cmake - elif [ -d "~/Qt/5.6" ] ; then + elif [ -d "$HOME/Qt/5.6" ] ; then export CMAKE_PREFIX_PATH=~/Qt/5.6/clang_64/lib/cmake + elif [ -d /usr/local/opt/qt5/lib ] ; then + # Homebrew location for qt5 package + export CMAKE_PREFIX_PATH=/usr/local/opt/qt5/lib/cmake else echo "cannot find Qt 5.5 or 5.6 in ~/Qt" exit 1 @@ -218,7 +233,7 @@ for (( i=0 ; i < ${#BUILDS[@]} ; i++ )) ; do mkdir -p $SRC/subsurface/$BUILDDIR cd $SRC/subsurface/$BUILDDIR - export CMAKE_PREFIX_PATH=$INSTALL_ROOT/lib/cmake + export CMAKE_PREFIX_PATH="$INSTALL_ROOT/lib/cmake;${CMAKE_PREFIX_PATH}" cmake -DCMAKE_BUILD_TYPE=Debug .. \ -DSUBSURFACE_TARGET_EXECUTABLE=$SUBSURFACE_EXECUTABLE \ -DLIBGIT2_INCLUDE_DIR=$INSTALL_ROOT/include \ @@ -227,6 +242,7 @@ for (( i=0 ; i < ${#BUILDS[@]} ; i++ )) ; do -DLIBDIVECOMPUTER_LIBRARIES=$INSTALL_ROOT/lib/libdivecomputer.a \ -DMARBLE_INCLUDE_DIR=$INSTALL_ROOT/include \ -DMARBLE_LIBRARIES=$INSTALL_ROOT/lib/libssrfmarblewidget.$SH_LIB_EXT \ + -DCMAKE_PREFIX_PATH=$CMAKE_PREFIX_PATH \ -DNO_PRINTING=OFF if [ $PLATFORM = Darwin ] ; then diff --git a/scripts/mobilecomponents.sh b/scripts/mobilecomponents.sh index 6d535fa26..ac3d1c1c4 100755 --- a/scripts/mobilecomponents.sh +++ b/scripts/mobilecomponents.sh @@ -35,14 +35,14 @@ git pull popd # now copy the components and a couple of icons into plae -MC=$SRC/subsurface/qt-mobile/qml/mobilecomponents -PMMC=kirigami/src +MC=$SRC/subsurface/qt-mobile/qml/kirigami +PMMC=kirigami/src/qml BREEZE=breeze-icons rm -rf $MC mkdir -p $MC/icons -cp -R $PMMC/qml/* $MC/ -cp $PMMC/fallbacktheme/*qml $MC/ +cp -R $PMMC/* $MC/ +cp $PMMC/../fallbacktheme/*qml $MC/ cp $BREEZE/icons/actions/24/dialog-cancel.svg $MC/icons cp $BREEZE/icons/actions/24/distribute-horizontal-x.svg $MC/icons @@ -55,4 +55,4 @@ cp $BREEZE/icons/actions/24/application-menu.svg $MC/icons cp $BREEZE/icons/actions/22/gps.svg $MC/icons cp $BREEZE/icons/actions/24/trash-empty.svg $MC/icons -echo org.kde.plasma.mobilecomponents synced from upstream +echo org.kde.plasma.kirigami synced from upstream diff --git a/subsurface-core/cochran.c b/subsurface-core/cochran.c index 40149d577..b42ed8233 100644 --- a/subsurface-core/cochran.c +++ b/subsurface-core/cochran.c @@ -1,3 +1,6 @@ +// Clang has a bug on zero-initialization of C structs. +#pragma clang diagnostic ignored "-Wmissing-field-initializers" + #include <stdlib.h> #include <stdio.h> #include <string.h> @@ -431,7 +434,7 @@ static void cochran_dive_event(struct divecomputer *dc, const unsigned char *s, * Parse sample data, extract events and build a dive */ static void cochran_parse_samples(struct dive *dive, const unsigned char *log, - const unsigned char *samples, int size, + const unsigned char *samples, unsigned int size, unsigned int *duration, double *max_depth, double *avg_depth, double *min_temp) { diff --git a/subsurface-core/compressibility.r b/subsurface-core/compressibility.r new file mode 100644 index 000000000..66310f3aa --- /dev/null +++ b/subsurface-core/compressibility.r @@ -0,0 +1,115 @@ +# Compressibility data gathered by Lubomir I Ivanov: +# +# "Data obtained by finding two books online: +# +# [1] +# PERRY’S CHEMICAL ENGINEERS’ HANDBOOK SEVENTH EDITION +# pretty serious book, from which the wiki AIR values come from! +# +# http://www.unhas.ac.id/rhiza/arsip/kuliah/Sistem-dan-Tekn-Kendali-Proses/PDF_Collections/REFERENSI/Perrys_Chemical_Engineering_Handbook.pdf +# page 2-165 +# +# [*](Computed from pressure-volume-temperature tables in Vasserman monographs) +# ^ i have no idea idea what this means, but the values might not be exactly +# experimental?! +# +# the only thing this book is missing is helium, thus [2]! +# +# [2] +# VOLUMETRIC BEHAVIOR OF HELIUM-ARGON MIXTURES AT HIGH PRESSURE AND MODERATE TEMPERATURE. +# +# https://shareok.org/bitstream/handle/11244/2062/6614196.PDF?sequence=1 +# page 108 +# +# +# the book has some tables with pressure values in atmosphere units. i'm +# converting them bars. one of the relevant tables is for 323K and one for 273K +# (both almost equal distance from 300K). +# +# this again is a linear mix operation between isotherms, which is probably not +# the most accurate solution but it works. +# +# all data sets contain Z values at 300k, while the pressures are in bars in +# the 1 to 500 range +# +# + +x = c(1, 5, 10, 20, 40, 60, 80, 100, 200, 300, 400, 500) +o2 = c(0.9994, 0.9968, 0.9941, 0.9884, 0.9771, 0.9676, 0.9597, 0.9542, 0.9560, 0.9972, 1.0689, 1.1572) +n2 = c(0.9998, 0.9990, 0.9983, 0.9971, 0.9964, 0.9973, 1.0000, 1.0052, 1.0559, 1.1422, 1.2480, 1.3629) +he = c(1.0005, 1.0024, 1.0048, 1.0096, 1.0191, 1.0286, 1.0381, 1.0476, 1.0943, 1.1402, 1.1854, 1.2297) + +options(digits=15) + +# +# Get the O2 virial coefficients +# +plot(x,o2) +o2fit = nls(o2 ~ 1.0 + p1*x + p2 *x^2 + p3*x^3, start=list(p1=0,p2=0,p3=0)) +summary(o2fit) + +new = data.frame(x = seq(min(x),max(x),len=200)) +lines(new$x,predict(o2fit,newdata=new)) + +# +# Get the N2 virial coefficients +# +plot(x,n2) +n2fit = nls(n2 ~ 1.0 + p1*x + p2 *x^2 + p3*x^3, start=list(p1=0,p2=0,p3=0)) +summary(n2fit) + +new = data.frame(x = seq(min(x),max(x),len=200)) +lines(new$x,predict(n2fit,newdata=new)) + +# +# Get the He virial coefficients +# +# NOTE! This will not confirm convergence, thus the warnOnly. +# That may be a sign that the data is possibly artificial. +# +plot(x,he) +hefit = nls(he ~ 1.0 + p1*x + p2 *x^2 + p3*x^3, + start=list(p1=0,p2=0,p3=0), + control=nls.control(warnOnly=TRUE)) +summary(hefit) + +new = data.frame(x = seq(min(x),max(x),len=200)) +lines(new$x,predict(hefit,newdata=new)) + +# +# Raw data from VOLUMETRIC BEHAVIOR OF HELIUM-ARGON MIXTURES [..] +# T=323.15K (50 C) +p323atm = c(674.837, 393.223, 237.310, 146.294, 91.4027, 57.5799, 36.4620, 23.1654, 14.7478, 9.4017, 5.9987, 3.8300, + 540.204, 319.943, 195.008, 120.951, 75.8599, 47.9005, 30.3791, 19.3193, 12.3080, 7.8495, 5.0100, 3.1992) + +Hez323 = c(1.28067, 1.16782, 1.10289, 1.06407, 1.04028, 1.02548, 1.01617, 1.01029, 1.00656, 1.00418, 1.00267, 1.00171, + 1.22738, 1.13754, 1.08493, 1.05312, 1.03349, 1.02122, 1.01349, 1.00859, 1.00548, 1.00349, 1.00223, 1.00143) + + +# T=273.15 (0 C) +p273atm = c(683.599, 391.213, 233.607, 143.091, 89.0521, 55.9640, 35.3851, 22.4593, 14.2908, 9.1072, 5.8095, 3.7083, + 534.047, 312.144, 188.741, 116.508, 72.8529, 45.9194, 29.0883, 18.4851, 11.7702, 7.5040, 4.7881, 3.0570) + +Hez273 = c(1.33969, 1.19985, 1.12121, 1.07494, 1.04689, 1.02957, 1.01874, 1.01191, 1.00758, 1.00484, 1.00309, 1.00197, + 1.26914, 1.16070, 1.09837, 1.06118, 1.03843, 1.02429, 1.01541, 1.00980, 1.00625, 1.00398, 1.00254, 1.00162) + +p323 = p323atm * 1.01325 +p273 = p273atm * 1.01325 + +x2=append(p323,p273) +he2=append(Hez323,Hez273) + +plot(x2,he2) + +hefit2 = nls(he2 ~ 1.0 + p1*x2 + p2*x2^2 + p3*x2^3, + start=list(p1=0,p2=0,p3=0)) +summary(hefit2) + +he3 = function(bar) +{ + 1.0 +0.00047961098687979363 * bar -0.00000004077670019935 * bar^2 +0.00000000000077707035 * bar^3 +} + +new = data.frame(x2 = seq(min(x2),max(x2),len=200)) +lines(new$x2,predict(hefit2,newdata=new)) +curve(he3, min(x2),max(x2),add=TRUE) diff --git a/subsurface-core/datatrak.c b/subsurface-core/datatrak.c index fb05c1701..204ebd9b3 100644 --- a/subsurface-core/datatrak.c +++ b/subsurface-core/datatrak.c @@ -1,3 +1,6 @@ +// Clang has a bug on zero-initialization of C structs. +#pragma clang diagnostic ignored "-Wmissing-field-initializers" + #include <stdlib.h> #include <stdio.h> #include <string.h> diff --git a/subsurface-core/deco.c b/subsurface-core/deco.c index dff88d338..3cd8c4a16 100644 --- a/subsurface-core/deco.c +++ b/subsurface-core/deco.c @@ -34,13 +34,13 @@ extern pressure_t first_ceiling_pressure; //! Option structure for Buehlmann decompression. struct buehlmann_config { - double satmult; //! safety at inert gas accumulation as percentage of effect (more than 100). - double desatmult; //! safety at inert gas depletion as percentage of effect (less than 100). - unsigned int last_deco_stop_in_mtr; //! depth of last_deco_stop. - double gf_high; //! gradient factor high (at surface). - double gf_low; //! gradient factor low (at bottom/start of deco calculation). - double gf_low_position_min; //! gf_low_position below surface_min_shallow. - bool gf_low_at_maxdepth; //! if true, gf_low applies at max depth instead of at deepest ceiling. + double satmult; //! safety at inert gas accumulation as percentage of effect (more than 100). + double desatmult; //! safety at inert gas depletion as percentage of effect (less than 100). + int last_deco_stop_in_mtr; //! depth of last_deco_stop. + double gf_high; //! gradient factor high (at surface). + double gf_low; //! gradient factor low (at bottom/start of deco calculation). + double gf_low_position_min; //! gf_low_position below surface_min_shallow. + bool gf_low_at_maxdepth; //! if true, gf_low applies at max depth instead of at deepest ceiling. }; struct buehlmann_config buehlmann_config = { @@ -572,9 +572,9 @@ void restore_deco_state(char *data) memcpy(&ci_pointing_to_guiding_tissue, data, sizeof(int)); } -unsigned int deco_allowed_depth(double tissues_tolerance, double surface_pressure, struct dive *dive, bool smooth) +int deco_allowed_depth(double tissues_tolerance, double surface_pressure, struct dive *dive, bool smooth) { - unsigned int depth; + int depth; double pressure_delta; /* Avoid negative depths */ diff --git a/subsurface-core/deco.h b/subsurface-core/deco.h index 08ff93422..fd3b94a9f 100644 --- a/subsurface-core/deco.h +++ b/subsurface-core/deco.h @@ -11,6 +11,7 @@ extern double tissue_inertgas_saturation[16]; extern double buehlmann_inertgas_a[16], buehlmann_inertgas_b[16]; extern double gf_low_pressure_this_dive; +extern int deco_allowed_depth(double tissues_tolerance, double surface_pressure, struct dive *dive, bool smooth); #ifdef __cplusplus } diff --git a/subsurface-core/dive.c b/subsurface-core/dive.c index 083767582..8fc9e993b 100644 --- a/subsurface-core/dive.c +++ b/subsurface-core/dive.c @@ -58,7 +58,7 @@ int event_gasmix_redundant(struct event *ev) he == ev->gas.mix.he.permille; } -struct event *add_event(struct divecomputer *dc, int time, int type, int flags, int value, const char *name) +struct event *add_event(struct divecomputer *dc, unsigned int time, int type, int flags, int value, const char *name) { int gas_index = -1; struct event *ev, **p; @@ -738,7 +738,8 @@ void per_cylinder_mean_depth(struct dive *dive, struct divecomputer *dc, int *me { int i; int depthtime[MAX_CYLINDERS] = { 0, }; - int lasttime = 0, lastdepth = 0; + uint32_t lasttime = 0; + int lastdepth = 0; int idx = 0; for (i = 0; i < MAX_CYLINDERS; i++) @@ -765,7 +766,7 @@ void per_cylinder_mean_depth(struct dive *dive, struct divecomputer *dc, int *me dc = fake_dc(dc, false); for (i = 0; i < dc->samples; i++) { struct sample *sample = dc->sample + i; - int time = sample->time.seconds; + uint32_t time = sample->time.seconds; int depth = sample->depth.mm; /* Make sure to move the event past 'lasttime' */ @@ -2619,7 +2620,8 @@ static struct divetag *taglist_add_divetag(struct tag_entry **tag_list, struct d struct divetag *taglist_add_tag(struct tag_entry **tag_list, const char *tag) { - int i = 0, is_default_tag = 0; + size_t i = 0; + int is_default_tag = 0; struct divetag *ret_tag, *new_tag; const char *translation; new_tag = malloc(sizeof(struct divetag)); @@ -2675,7 +2677,7 @@ static void taglist_merge(struct tag_entry **dst, struct tag_entry *src1, struct void taglist_init_global() { - int i; + size_t i; for (i = 0; i < sizeof(default_tags) / sizeof(char *); i++) taglist_add_tag(&g_tag_list, default_tags[i]); @@ -2846,7 +2848,7 @@ struct dive *merge_dives(struct dive *a, struct dive *b, int offset, bool prefer MERGE_TXT(res, a, b, divemaster); MERGE_MAX(res, a, b, rating); MERGE_TXT(res, a, b, suit); - MERGE_MIN(res, a, b, number); + MERGE_MAX(res, a, b, number); MERGE_NONZERO(res, a, b, cns); MERGE_NONZERO(res, a, b, visibility); MERGE_NONZERO(res, a, b, picture_list); @@ -2920,7 +2922,8 @@ static void force_fixup_dive(struct dive *d) */ static int split_dive_at(struct dive *dive, int a, int b) { - int i, t, nr; + int i, nr; + uint32_t t; struct dive *d1, *d2; struct divecomputer *dc1, *dc2; struct event *event, **evp; @@ -3371,7 +3374,7 @@ void dive_set_geodata_from_picture(struct dive *dive, struct picture *picture) } } -static void picture_free(struct picture *picture) +void picture_free(struct picture *picture) { if (!picture) return; @@ -3380,6 +3383,18 @@ static void picture_free(struct picture *picture) free(picture); } +// When handling pictures in different threads, we need to copy them so we don't +// run into problems when the main thread frees the picture. + +struct picture *clone_picture(struct picture *src) +{ + struct picture *dst; + + dst = alloc_picture(); + copy_pl(src, dst); + return dst; +} + void dive_remove_picture(char *filename) { struct picture **picture = ¤t_dive->picture_list; @@ -3415,7 +3430,7 @@ void make_first_dc() } /* always acts on the current dive */ -int count_divecomputers(void) +unsigned int count_divecomputers(void) { int ret = 1; struct divecomputer *dc = current_dive->dc.next; @@ -3455,7 +3470,7 @@ void delete_current_divecomputer(void) /* helper function to make it easier to work with our structures * we don't interpolate here, just use the value from the last sample up to that time */ -int get_depth_at_time(struct divecomputer *dc, int time) +int get_depth_at_time(struct divecomputer *dc, unsigned int time) { int depth = 0; if (dc && dc->sample) diff --git a/subsurface-core/dive.h b/subsurface-core/dive.h index f8970b237..204d34819 100644 --- a/subsurface-core/dive.h +++ b/subsurface-core/dive.h @@ -376,6 +376,7 @@ struct picture { for (struct picture *picture = (_divestruct).picture_list; picture; picture = picture->next) extern struct picture *alloc_picture(); +extern struct picture *clone_picture(struct picture *src); extern bool dive_check_picture_time(struct dive *d, int shift_time, timestamp_t timestamp); extern void dive_create_picture(struct dive *d, char *filename, int shift_time, bool match_all); extern void dive_add_picture(struct dive *d, struct picture *newpic); @@ -385,9 +386,10 @@ extern bool picture_check_valid(char *filename, int shift_time); extern void picture_load_exif_data(struct picture *p); extern timestamp_t picture_get_timestamp(char *filename); extern void dive_set_geodata_from_picture(struct dive *d, struct picture *pic); +extern void picture_free(struct picture *picture); extern int explicit_first_cylinder(struct dive *dive, struct divecomputer *dc); -extern int get_depth_at_time(struct divecomputer *dc, int time); +extern int get_depth_at_time(struct divecomputer *dc, unsigned int time); static inline int get_surface_pressure_in_mbar(const struct dive *dive, bool non_null) { @@ -493,7 +495,7 @@ extern const struct units SI_units, IMPERIAL_units; extern struct units xml_parsing_units; extern struct units *get_units(void); -extern int run_survey, verbose, quit; +extern int run_survey, verbose, quit, force_root; struct dive_table { int nr, allocated, preexisting; @@ -567,7 +569,7 @@ static inline struct divecomputer *get_dive_dc(struct dive *dive, int nr) extern timestamp_t dive_endtime(const struct dive *dive); extern void make_first_dc(void); -extern int count_divecomputers(void); +extern unsigned int count_divecomputers(void); extern void delete_current_divecomputer(void); /* @@ -695,6 +697,7 @@ extern struct zip *subsurface_zip_open_readonly(const char *path, int flags, int extern int subsurface_zip_close(struct zip *zip); extern void subsurface_console_init(bool dedicated); extern void subsurface_console_exit(void); +extern bool subsurface_user_is_root(void); extern void shift_times(const timestamp_t amount); extern timestamp_t get_times(); @@ -728,7 +731,6 @@ extern unsigned int dc_watertemp(struct divecomputer *dc); extern int split_dive(struct dive *); extern struct dive *merge_dives(struct dive *a, struct dive *b, int offset, bool prefer_downloaded); extern struct dive *try_to_merge(struct dive *a, struct dive *b, bool prefer_downloaded); -extern void renumber_dives(int start_nr, bool selected_only); extern struct event *clone_event(const struct event *src_ev); extern void copy_events(struct divecomputer *s, struct divecomputer *d); extern void free_events(struct event *ev); @@ -737,7 +739,7 @@ extern void copy_samples(struct divecomputer *s, struct divecomputer *d); extern bool is_cylinder_used(struct dive *dive, int idx); extern void fill_default_cylinder(cylinder_t *cyl); extern void add_gas_switch_event(struct dive *dive, struct divecomputer *dc, int time, int idx); -extern struct event *add_event(struct divecomputer *dc, int time, int type, int flags, int value, const char *name); +extern struct event *add_event(struct divecomputer *dc, unsigned int time, int type, int flags, int value, const char *name); extern void remove_event(struct event *event); extern void update_event_name(struct dive *d, struct event* event, char *name); extern void add_extra_data(struct divecomputer *dc, const char *key, const char *value); @@ -792,7 +794,6 @@ extern void subsurface_command_line_exit(int *, char ***); extern void add_segment(double pressure, const struct gasmix *gasmix, int period_in_seconds, int setpoint, const struct dive *dive, int sac); extern void clear_deco(double surface_pressure); extern void dump_tissues(void); -extern unsigned int deco_allowed_depth(double tissues_tolerance, double surface_pressure, struct dive *dive, bool smooth); extern void set_gf(short gflow, short gfhigh, bool gf_low_at_maxdepth); extern void cache_deco_state(char **datap); extern void restore_deco_state(char *data); @@ -804,7 +805,7 @@ extern double tissue_tolerance_calc(const struct dive *dive, double pressure); /* this should be converted to use our types */ struct divedatapoint { int time; - unsigned int depth; + int depth; struct gasmix gasmix; int setpoint; bool entered; diff --git a/subsurface-core/divelist.c b/subsurface-core/divelist.c index 1e9065d8b..543d9e17b 100644 --- a/subsurface-core/divelist.c +++ b/subsurface-core/divelist.c @@ -44,6 +44,7 @@ #include "display.h" #include "planner.h" #include "qthelperfromc.h" +#include "git-access.h" static short dive_list_changed = false; @@ -205,7 +206,8 @@ int const cns_table[][3] = { * so we calculated it "by hand" */ static int calculate_cns(struct dive *dive) { - int i, j, divenr; + int i, divenr; + size_t j; double cns = 0.0; struct divecomputer *dc = &dive->dc; struct dive *prev_dive; @@ -833,10 +835,14 @@ bool consecutive_selected() return consecutive; } +/* + * Merge two dives. 'a' is always before 'b' in the dive list + * (and thus in time). + */ struct dive *merge_two_dives(struct dive *a, struct dive *b) { struct dive *res; - int i, j, factor; + int i, j, nr, nrdiff; int id; if (!a || !b) @@ -852,7 +858,30 @@ struct dive *merge_two_dives(struct dive *a, struct dive *b) if (!res) return NULL; - factor = (a->number == 0 || b->number == 0) ? 0 : abs(b->number - a->number); + /* + * If 'a' and 'b' were numbered, and in proper order, + * then the resulting dive will get the first number, + * and the subsequent dives will be renumbered by the + * difference. + * + * So if you had a dive list 1 3 6 7 8, and you + * merge 1 and 3, the resulting numbered list will + * be 1 4 5 6, because we assume that there were + * some missing dives (originally dives 4 and 5), + * that now will still be missing (dives 2 and 3 + * in the renumbered world). + * + * Obviously the normal case is that everything is + * consecutive, and the difference will be 1, so the + * above example is not supposed to be normal. + */ + nrdiff = 0; + nr = a->number; + if (a->number && b->number > a->number) { + res->number = nr; + nrdiff = b->number - nr; + } + add_single_dive(i, res); delete_single_dive(i + 1); delete_single_dive(j); @@ -863,9 +892,25 @@ struct dive *merge_two_dives(struct dive *a, struct dive *b) // renumber dives from merged one in advance by difference between // merged dives numbers. Do not renumber if actual number is zero. - for (; j < dive_table.nr; j++) - if (!dive_table.dives[j]->number == 0) - dive_table.dives[j]->number -= factor; + for (; j < dive_table.nr; j++) { + struct dive *dive = dive_table.dives[j]; + int newnr; + + if (!dive->number) + continue; + newnr = dive->number - nrdiff; + + /* + * Don't renumber stuff that isn't in order! + * + * So if the new dive number isn't larger than the + * previous dive number, just stop here. + */ + if (newnr <= nr) + break; + dive->number = newnr; + nr = newnr; + } mark_divelist_changed(true); return res; @@ -1158,4 +1203,5 @@ void clear_dive_file_data() existing_filename = NULL; reset_min_datafile_version(); + saved_git_id = ""; } diff --git a/subsurface-core/equipment.c b/subsurface-core/equipment.c index 47c439735..9f3e49039 100644 --- a/subsurface-core/equipment.c +++ b/subsurface-core/equipment.c @@ -1,3 +1,6 @@ +// Clang has a bug on zero-initialization of C structs. +#pragma clang diagnostic ignored "-Wmissing-field-initializers" + /* equipment.c */ #include <stdio.h> #include <string.h> diff --git a/subsurface-core/file.c b/subsurface-core/file.c index 8286ce9f5..1337da3a2 100644 --- a/subsurface-core/file.c +++ b/subsurface-core/file.c @@ -57,7 +57,7 @@ int readfile(const char *filename, struct memblock *mem) if (ret < 0) goto free; buf[ret] = 0; - if (ret == mem->size) + if (ret == (int)mem->size) // converting to int loses a bit but size will never be that big goto out; errno = EIO; ret = -1; @@ -453,8 +453,7 @@ int check_git_sha(const char *filename) if (git && git != dummy_git_repository) { const char *sha = get_sha(git, branch); if (!same_string(sha, "") && - same_string(sha, saved_git_id) && - !unsaved_changes()) { + same_string(sha, saved_git_id)) { fprintf(stderr, "already have loaded SHA %s - don't load again\n", sha); return 0; } @@ -466,6 +465,7 @@ int parse_file(const char *filename) { struct git_repository *git; const char *branch = NULL; + char *current_sha = copy_string(saved_git_id); struct memblock mem; char *fmt; int ret; @@ -473,22 +473,25 @@ int parse_file(const char *filename) git = is_git_repository(filename, &branch, NULL, false); if (prefs.cloud_git_url && strstr(filename, prefs.cloud_git_url) - && git == dummy_git_repository) + && git == dummy_git_repository) { /* opening the cloud storage repository failed for some reason * give up here and don't send errors about git repositories */ + free(current_sha); return 0; - + } /* if this is a git repository, do we already have this exact state loaded ? * get the SHA and compare with what we currently have */ if (git && git != dummy_git_repository) { const char *sha = get_sha(git, branch); if (!same_string(sha, "") && - same_string(sha, saved_git_id) && + same_string(sha, current_sha) && !unsaved_changes()) { fprintf(stderr, "already have loaded SHA %s - don't load again\n", sha); + free(current_sha); return 0; } } + free(current_sha); if (git) return git_load_dives(git, branch); diff --git a/subsurface-core/gas-model.c b/subsurface-core/gas-model.c index 81765e003..ad1160f3b 100644 --- a/subsurface-core/gas-model.c +++ b/subsurface-core/gas-model.c @@ -26,36 +26,39 @@ double gas_compressibility_factor(struct gasmix *gas, double bar) { static const double o2_coefficients[3] = { - -0.00071809207370164567, - +0.00000281852572807643, - -0.00000000150290620491 + -7.18092073703e-04, + +2.81852572808e-06, + -1.50290620492e-09 }; static const double n2_coefficients[3] = { - -0.00021926035329221337, - +0.00000292844845531647, - -0.00000000207613482075 + -2.19260353292e-04, + +2.92844845532e-06, + -2.07613482075e-09 }; static const double he_coefficients[3] = { - +0.00047961098687979363, - -0.00000004077670019935, - +0.00000000000077707035 + +4.87320026468e-04, + -8.83632921053e-08, + +5.33304543646e-11 }; - double o2, he; + int o2, he; double x1, x2, x3; double Z; - o2 = get_o2(gas) / 1000.0; - he = get_he(gas) / 1000.0; + o2 = get_o2(gas); + he = get_he(gas); x1 = bar; x2 = x1*x1; x3 = x2*x1; Z = virial_m1(o2_coefficients, x1, x2, x3) * o2 + virial_m1(he_coefficients, x1, x2, x3) * he + - virial_m1(n2_coefficients, x1, x2, x3) * (1.0 - o2 - he); + virial_m1(n2_coefficients, x1, x2, x3) * (1000 - o2 - he); /* * We add the 1.0 at the very end - the linear mixing of the * three 1.0 terms is still 1.0 regardless of the gas mix. + * + * The * 0.001 is because we did the linear mixing using the + * raw permille gas values. */ - return Z + 1.0; + return Z * 0.001 + 1.0; } diff --git a/subsurface-core/gaspressures.c b/subsurface-core/gaspressures.c index 3cbb36773..5d3fc9791 100644 --- a/subsurface-core/gaspressures.c +++ b/subsurface-core/gaspressures.c @@ -200,7 +200,7 @@ static void fill_missing_tank_pressures(struct dive *dive, struct plot_info *pi, { int cyl, i; struct plot_data *entry; - pr_interpolate_t interpolate = { 0 }; + pr_interpolate_t interpolate = { 0, 0, 0, 0 }; pr_track_t *last_segment = NULL; int cur_pr[MAX_CYLINDERS]; // cur_pr[MAX_CYLINDERS] is the CCR diluent cylinder @@ -347,6 +347,7 @@ static void debug_print_pressures(struct plot_info *pi) */ void populate_pressure_information(struct dive *dive, struct divecomputer *dc, struct plot_info *pi, int o2_flag) { + (void) dc; int i, cylinderid, cylinderindex = -1; pr_track_t *track_pr[MAX_CYLINDERS] = { NULL, }; pr_track_t *current = NULL; diff --git a/subsurface-core/git-access.c b/subsurface-core/git-access.c index e986607ab..c902bf60b 100644 --- a/subsurface-core/git-access.c +++ b/subsurface-core/git-access.c @@ -1,3 +1,6 @@ +// Clang has a bug on zero-initialization of C structs. +#pragma clang diagnostic ignored "-Wmissing-field-initializers" + #include <stdio.h> #include <ctype.h> #include <string.h> @@ -664,7 +667,7 @@ static git_repository *create_local_repo(const char *localdir, const char *remot * to our cloud storage and the branch doesn't exist. * So we need to create the branch and push it to the remote */ cloned_repo = create_and_push_remote(localdir, remote, branch); -#if !defined(DEBUG) +#if !defined(DEBUG) && !defined(SUBSURFACE_MOBILE) } else if (is_subsurface_cloud) { report_error(translate("gettextFromC", "Error connecting to Subsurface cloud storage")); #endif diff --git a/subsurface-core/gpslocation.cpp b/subsurface-core/gpslocation.cpp index 9f1961cbf..075b1c046 100644 --- a/subsurface-core/gpslocation.cpp +++ b/subsurface-core/gpslocation.cpp @@ -33,7 +33,7 @@ GpsLocation::GpsLocation(void (*showMsgCB)(const char *), QObject *parent) : QOb QString("org.subsurfacedivelog"), QString("subsurfacelocation"), this); #ifdef SUBSURFACE_MOBILE if (hasLocationsSource()) - status("Found GPS"); + status(QString("Found GPS with positioning methods %1").arg(QString::number(m_GpsSource->supportedPositioningMethods(), 16))); #endif userAgent = getUserAgent(); loadFromStorage(); @@ -59,8 +59,7 @@ QGeoPositionInfoSource *GpsLocation::getGpsSource() #ifndef SUBSURFACE_MOBILE if (verbose) #endif - status("created GPS source"); - QString msg = QString("have position source %1").arg(m_GpsSource->sourceName()); + status(QString("Created position source %1").arg(m_GpsSource->sourceName())); connect(m_GpsSource, SIGNAL(positionUpdated(QGeoPositionInfo)), this, SLOT(newPosition(QGeoPositionInfo))); connect(m_GpsSource, SIGNAL(updateTimeout()), this, SLOT(updateTimeout())); m_GpsSource->setUpdateInterval(5 * 60 * 1000); // 5 minutes so the device doesn't drain the battery @@ -89,7 +88,7 @@ void GpsLocation::serviceEnable(bool toggle) } if (toggle) { gpsSource->startUpdates(); - status("Starting Subsurface GPS service"); + status(QString("Starting Subsurface GPS service with update interval %1").arg(gpsSource->updateInterval())); } else { gpsSource->stopUpdates(); status("Stopping Subsurface GPS service"); @@ -117,10 +116,8 @@ QString GpsLocation::currentPosition() void GpsLocation::newPosition(QGeoPositionInfo pos) { - int64_t lastTime; + int64_t lastTime = 0; QGeoCoordinate lastCoord; - QString msg("received new position %1"); - status(qPrintable(msg.arg(pos.coordinate().toString()))); int nr = m_trackers.count(); if (nr) { gpsTracker gt = m_trackers.last(); @@ -131,9 +128,11 @@ void GpsLocation::newPosition(QGeoPositionInfo pos) // if we are waiting for a position update or // if we have no record stored or if at least the configured minimum // time has passed or we moved at least the configured minimum distance - if (!nr || waitingForPosition || - (int64_t)pos.timestamp().toTime_t() > lastTime + prefs.time_threshold || + int64_t delta = (int64_t)pos.timestamp().toTime_t() + gettimezoneoffset() - lastTime; + if (!nr || waitingForPosition || delta > prefs.time_threshold || lastCoord.distanceTo(pos.coordinate()) > prefs.distance_threshold) { + QString msg("received new position %1 after delta %2 threshold %3"); + status(qPrintable(msg.arg(pos.coordinate().toString()).arg(delta).arg(prefs.time_threshold))); waitingForPosition = false; gpsTracker gt; gt.when = pos.timestamp().toTime_t(); diff --git a/subsurface-core/imagedownloader.cpp b/subsurface-core/imagedownloader.cpp index 9451f8a1b..daa49eadf 100644 --- a/subsurface-core/imagedownloader.cpp +++ b/subsurface-core/imagedownloader.cpp @@ -17,8 +17,14 @@ ImageDownloader::ImageDownloader(struct picture *pic) picture = pic; } +ImageDownloader::~ImageDownloader() +{ + picture_free(picture); +} + void ImageDownloader::load(bool fromHash){ QUrl url; + loadFromHash = fromHash; if(fromHash) url = cloudImageURL(picture->hash); else @@ -40,8 +46,11 @@ void ImageDownloader::saveImage(QNetworkReply *reply) QByteArray imageData = reply->readAll(); QImage image = QImage(); image.loadFromData(imageData); - if (image.isNull()) + if (image.isNull()) { + if (loadFromHash) + load(false); return; + } QCryptographicHash hash(QCryptographicHash::Sha1); hash.addData(imageData); QString path = QStandardPaths::standardLocations(QStandardPaths::CacheLocation).first(); @@ -59,6 +68,11 @@ void ImageDownloader::saveImage(QNetworkReply *reply) } reply->manager()->deleteLater(); reply->deleteLater(); + // This should be called to make the picture actually show. + // Problem is DivePictureModel is not in subsurface-core. + // Nevertheless, the image shows when the dive is selected the next time. + // DivePictureModel::instance()->updateDivePictures(); + } void loadPicture(struct picture *picture, bool fromHash) @@ -69,7 +83,7 @@ void loadPicture(struct picture *picture, bool fromHash) SHashedImage::SHashedImage(struct picture *picture) : QImage() { - QUrl url = QUrl::fromUserInput(QString(picture->filename)); + QUrl url = QUrl::fromUserInput(localFilePath(QString(picture->filename))); if(url.isLocalFile()) load(url.toLocalFile()); if (isNull()) { @@ -79,21 +93,21 @@ SHashedImage::SHashedImage(struct picture *picture) : QImage() if (filename.isNull()) { // That didn't produce a local filename. // Try the cloud server - QtConcurrent::run(loadPicture, picture, true); + QtConcurrent::run(loadPicture, clone_picture(picture), true); } else { // Load locally from translated file name load(filename); if (!isNull()) { // Make sure the hash still matches the image file - QtConcurrent::run(updateHash, picture); + QtConcurrent::run(updateHash, clone_picture(picture)); } else { // Interpret filename as URL - QtConcurrent::run(loadPicture, picture, false); + QtConcurrent::run(loadPicture, clone_picture(picture), false); } } } else { // We loaded successfully. Now, make sure hash is up to date. - QtConcurrent::run(hashPicture, picture); + QtConcurrent::run(hashPicture, clone_picture(picture)); } } diff --git a/subsurface-core/imagedownloader.h b/subsurface-core/imagedownloader.h index cd85c9509..f4e3df875 100644 --- a/subsurface-core/imagedownloader.h +++ b/subsurface-core/imagedownloader.h @@ -14,11 +14,13 @@ class ImageDownloader : public QObject { Q_OBJECT; public: ImageDownloader(struct picture *picture); + ~ImageDownloader(); void load(bool fromHash); private: struct picture *picture; QNetworkAccessManager manager; + bool loadFromHash; private slots: void saveImage(QNetworkReply *reply); diff --git a/subsurface-core/libdivecomputer.c b/subsurface-core/libdivecomputer.c index 0d0b397dc..549b894ce 100644 --- a/subsurface-core/libdivecomputer.c +++ b/subsurface-core/libdivecomputer.c @@ -1,3 +1,6 @@ +// Clang has a bug on zero-initialization of C structs. +#pragma clang diagnostic ignored "-Wmissing-field-initializers" + #include <stdio.h> #include <unistd.h> #include <inttypes.h> @@ -68,13 +71,14 @@ static dc_status_t create_parser(device_data_t *devdata, dc_parser_t **parser) return dc_parser_new(parser, devdata->device); } -static int parse_gasmixes(device_data_t *devdata, struct dive *dive, dc_parser_t *parser, int ngases) +static int parse_gasmixes(device_data_t *devdata, struct dive *dive, dc_parser_t *parser, unsigned int ngases) { static bool shown_warning = false; - int i, rc; + unsigned int i; + int rc; #if DC_VERSION_CHECK(0, 5, 0) && defined(DC_GASMIX_UNKNOWN) - int ntanks = 0; + unsigned int ntanks = 0; rc = dc_parser_get_field(parser, DC_FIELD_TANK_COUNT, 0, &ntanks); if (rc == DC_STATUS_SUCCESS) { if (ntanks && ntanks != ngases) { diff --git a/subsurface-core/linux.c b/subsurface-core/linux.c index d4131c7ea..b81f6bf53 100644 --- a/subsurface-core/linux.c +++ b/subsurface-core/linux.c @@ -25,6 +25,7 @@ void subsurface_OS_pref_setup(void) bool subsurface_ignore_font(const char *font) { // there are no old default fonts to ignore + (void)font; return false; } @@ -41,7 +42,7 @@ void subsurface_user_info(struct user_info *user) } if (username && *username) { char hostname[64]; - struct membuffer mb = { 0 }; + struct membuffer mb = {}; gethostname(hostname, sizeof(hostname)); put_format(&mb, "%s@%s", username, hostname); user->email = mb_cstring(&mb); @@ -126,7 +127,7 @@ int enumerate_devices(device_callback_t callback, void *userdata, int dc_type) if (fnmatch(patterns[i], ep->d_name, 0) == 0) { char filename[1024]; int n = snprintf(filename, sizeof(filename), "%s/%s", dirname, ep->d_name); - if (n >= sizeof(filename)) { + if (n >= (int)sizeof(filename)) { closedir(dp); return -1; } @@ -216,6 +217,7 @@ int subsurface_zip_close(struct zip *zip) /* win32 console */ void subsurface_console_init(bool dedicated) { + (void)dedicated; /* NOP */ } @@ -223,3 +225,8 @@ void subsurface_console_exit(void) { /* NOP */ } + +bool subsurface_user_is_root() +{ + return (geteuid() == 0); +} diff --git a/subsurface-core/load-git.c b/subsurface-core/load-git.c index cc702f6ae..a78082c07 100644 --- a/subsurface-core/load-git.c +++ b/subsurface-core/load-git.c @@ -1,3 +1,6 @@ +// Clang has a bug on zero-initialization of C structs. +#pragma clang diagnostic ignored "-Wmissing-field-initializers" + #include <stdio.h> #include <ctype.h> #include <string.h> diff --git a/subsurface-core/macos.c b/subsurface-core/macos.c index 8ca2c1c6f..500412cd8 100644 --- a/subsurface-core/macos.c +++ b/subsurface-core/macos.c @@ -119,7 +119,7 @@ int enumerate_devices(device_callback_t callback, void *userdata, int dc_type) if (fnmatch(patterns[i], ep->d_name, 0) == 0) { char filename[1024]; int n = snprintf(filename, sizeof(filename), "%s/%s", dirname, ep->d_name); - if (n >= sizeof(filename)) { + if (n >= (int)sizeof(filename)) { closedir(dp); return -1; } @@ -145,7 +145,7 @@ int enumerate_devices(device_callback_t callback, void *userdata, int dc_type) if (fnmatch("UEMISSDA", ep->d_name, 0) == 0) { char filename[1024]; int n = snprintf(filename, sizeof(filename), "%s/%s", dirname, ep->d_name); - if (n >= sizeof(filename)) { + if (n >= (int)sizeof(filename)) { closedir(dp); return -1; } @@ -211,3 +211,8 @@ void subsurface_console_exit(void) { /* NOP */ } + +bool subsurface_user_is_root() +{ + return (geteuid() == 0); +} diff --git a/subsurface-core/membuffer.c b/subsurface-core/membuffer.c index 2889a0cdc..053edb8f0 100644 --- a/subsurface-core/membuffer.c +++ b/subsurface-core/membuffer.c @@ -1,3 +1,6 @@ +// Clang has a bug on zero-initialization of C structs. +#pragma clang diagnostic ignored "-Wmissing-field-initializers" + #include <stdarg.h> #include <stdlib.h> #include <string.h> diff --git a/subsurface-core/metrics.cpp b/subsurface-core/metrics.cpp index db636794d..3c66528b8 100644 --- a/subsurface-core/metrics.cpp +++ b/subsurface-core/metrics.cpp @@ -15,7 +15,8 @@ IconMetrics::IconMetrics() : sz_med(-1), sz_big(-1), sz_pic(-1), - spacing(-1) + spacing(-1), + dpr(1.0) { } @@ -57,3 +58,8 @@ const IconMetrics & defaultIconMetrics() return dfltIconMetrics; } + +void updateDevicePixelRatio(double dpr) +{ + dfltIconMetrics.dpr = dpr; +} diff --git a/subsurface-core/metrics.h b/subsurface-core/metrics.h index 03d6b22e2..ca281b3b1 100644 --- a/subsurface-core/metrics.h +++ b/subsurface-core/metrics.h @@ -25,9 +25,12 @@ struct IconMetrics { int sz_pic; // ex 128px // icon spacing int spacing; // ex 2px + // devicePixelRatio + double dpr; // 1.0 for traditional screens, HiDPI screens up to 3.0 IconMetrics(); }; const IconMetrics & defaultIconMetrics(); +void updateDevicePixelRatio(double dpr); #endif // METRICS_H diff --git a/subsurface-core/parse-xml.c b/subsurface-core/parse-xml.c index a617648fb..e8782251e 100644 --- a/subsurface-core/parse-xml.c +++ b/subsurface-core/parse-xml.c @@ -1,3 +1,6 @@ +// Clang has a bug on zero-initialization of C structs. +#pragma clang diagnostic ignored "-Wmissing-field-initializers" + #include <stdio.h> #include <ctype.h> #include <string.h> @@ -20,7 +23,7 @@ #include "device.h" #include "membuffer.h" -int verbose, quit; +int verbose, quit, force_root; int metric = 1; int last_xml_version = -1; int diveid = -1; @@ -2010,7 +2013,7 @@ const char *preprocess_divelog_de(const char *buffer) if (ret) { xmlParserCtxtPtr ctx; char buf[] = ""; - int i; + size_t i; for (i = 0; i < strlen(ret); ++i) if (!isascii(ret[i])) @@ -2257,7 +2260,8 @@ extern int dm4_dive(void *param, int columns, char **data, char **column) { (void) columns; (void) column; - int i, interval, retval = 0; + unsigned int i; + int interval, retval = 0; sqlite3 *handle = (sqlite3 *)param; float *profileBlob; unsigned char *tempBlob; @@ -2385,7 +2389,8 @@ extern int dm5_dive(void *param, int columns, char **data, char **column) { (void) columns; (void) column; - int i, interval, retval = 0, block_size; + unsigned int i; + int interval, retval = 0, block_size; sqlite3 *handle = (sqlite3 *)param; unsigned const char *sampleBlob; char *err = NULL; diff --git a/subsurface-core/planner.c b/subsurface-core/planner.c index 1828d5a11..705aad1cb 100644 --- a/subsurface-core/planner.c +++ b/subsurface-core/planner.c @@ -9,6 +9,7 @@ #include <ctype.h> #include <string.h> #include "dive.h" +#include "deco.h" #include "divelist.h" #include "planner.h" #include "gettext.h" @@ -103,7 +104,7 @@ int get_gasidx(struct dive *dive, struct gasmix *mix) void interpolate_transition(struct dive *dive, duration_t t0, duration_t t1, depth_t d0, depth_t d1, const struct gasmix *gasmix, o2pressure_t po2) { - int j; + uint32_t j; for (j = t0.seconds; j < t1.seconds; j++) { int depth = interpolate(d0.mm, d1.mm, j - t0.seconds, t1.seconds - t0.seconds); @@ -476,11 +477,11 @@ static struct gaschanges *analyze_gaslist(struct diveplan *diveplan, int *gascha } /* sort all the stops into one ordered list */ -static unsigned int *sort_stops(int *dstops, int dnr, struct gaschanges *gstops, int gnr) +static int *sort_stops(int *dstops, int dnr, struct gaschanges *gstops, int gnr) { int i, gi, di; int total = dnr + gnr; - unsigned int *stoplevels = malloc(total * sizeof(int)); + int *stoplevels = malloc(total * sizeof(int)); /* no gaschanges */ if (gnr == 0) { @@ -534,7 +535,7 @@ static void add_plan_to_notes(struct diveplan *diveplan, struct dive *dive, bool const unsigned int sz_temp = 100000; char *buffer = (char *)malloc(sz_buffer); char *temp = (char *)malloc(sz_temp); - char *deco; + char *deco, *segmentsymbol; static char buf[1000]; int len, lastdepth = 0, lasttime = 0, lastsetpoint = -1, newdepth = 0, lastprintdepth = 0, lastprintsetpoint = -1; struct gasmix lastprintgasmix = {{ -1 }, { -1 }}; @@ -596,7 +597,7 @@ static void add_plan_to_notes(struct diveplan *diveplan, struct dive *dive, bool translate("gettextFromC", "Subsurface dive plan"), temp); if (!plan_verbatim) { - len += snprintf(buffer + len, sz_buffer - len, "<div><table><thead><tr><th>%s</th>", + len += snprintf(buffer + len, sz_buffer - len, "<div><table><thead><tr><th></th><th>%s</th>", translate("gettextFromC", "depth")); if (plan_display_duration) len += snprintf(buffer + len, sz_buffer - len, "<th style='padding-left: 10px;'>%s</th>", @@ -710,8 +711,20 @@ static void add_plan_to_notes(struct diveplan *diveplan, struct dive *dive, bool (!isascent && gaschange_before && nextdp && dp->depth != nextdp->depth) || (gaschange_after && lastentered) || (gaschange_after && !isascent) || (isascent && gaschange_after && nextdp && dp->depth != nextdp->depth )) { + // Print a symbol to indicate whether segment is an ascent, descent, constant depth (user entered) or deco stop + if (isascent) + segmentsymbol = "➚"; // up-right arrow for ascent + else if (dp->depth > lastdepth) + segmentsymbol = "➘"; // down-right arrow for descent + else if (dp->entered) + segmentsymbol = "➙"; // right arrow for entered entered segment at constant depth + else + segmentsymbol = "➖"; // heavey minus sign for deco stop + + len += snprintf(buffer + len, sz_buffer - len, "<tr><td style='padding-left: 10px; float: right;'>%s</td>", segmentsymbol); + snprintf(temp, sz_temp, translate("gettextFromC", "%3.0f%s"), depthvalue, depth_unit); - len += snprintf(buffer + len, sz_buffer - len, "<tr><td style='padding-left: 10px; float: right;'>%s</td>", temp); + len += snprintf(buffer + len, sz_buffer - len, "<td style='padding-left: 10px; float: right;'>%s</td>", temp); if (plan_display_duration) { snprintf(temp, sz_temp, translate("gettextFromC", "%3dmin"), (dp->time - lasttime + 30) / 60); len += snprintf(buffer + len, sz_buffer - len, "<td style='padding-left: 10px; float: right;'>%s</td>", temp); @@ -969,13 +982,13 @@ bool plan(struct diveplan *diveplan, char **cached_datap, bool is_planner, bool int po2; int transitiontime, gi; int current_cylinder; - unsigned int stopidx; + int stopidx; int depth; struct gaschanges *gaschanges = NULL; int gaschangenr; int *decostoplevels; int decostoplevelcount; - unsigned int *stoplevels = NULL; + int *stoplevels = NULL; bool stopping = false; bool pendinggaschange = false; int clock, previous_point_time; diff --git a/subsurface-core/profile.c b/subsurface-core/profile.c index 4d9a8444f..6576f6453 100644 --- a/subsurface-core/profile.c +++ b/subsurface-core/profile.c @@ -377,7 +377,7 @@ static int count_events(struct divecomputer *dc) return result; } -static int set_cylinder_index(struct plot_info *pi, int i, int cylinderindex, unsigned int end) +static int set_cylinder_index(struct plot_info *pi, int i, int cylinderindex, int end) { while (i < pi->nr) { struct plot_data *entry = pi->entry + i; @@ -392,7 +392,7 @@ static int set_cylinder_index(struct plot_info *pi, int i, int cylinderindex, un return i; } -static int set_setpoint(struct plot_info *pi, int i, int setpoint, unsigned int end) +static int set_setpoint(struct plot_info *pi, int i, int setpoint, int end) { while (i < pi->nr) { struct plot_data *entry = pi->entry + i; @@ -405,7 +405,7 @@ static int set_setpoint(struct plot_info *pi, int i, int setpoint, unsigned int } /* normally the first cylinder has index 0... if not, we need to fix this up here */ -static int set_first_cylinder_index(struct plot_info *pi, int i, int cylinderindex, unsigned int end) +static int set_first_cylinder_index(struct plot_info *pi, int i, int cylinderindex, int end) { while (i < pi->nr) { struct plot_data *entry = pi->entry + i; @@ -425,7 +425,7 @@ static void check_gas_change_events(struct dive *dive, struct divecomputer *dc, // for dive computers that tell us their first gas as an event on the first sample // we need to make sure things are setup correctly cylinderindex = explicit_first_cylinder(dive, dc); - set_first_cylinder_index(pi, 0, cylinderindex, ~0u); + set_first_cylinder_index(pi, 0, cylinderindex, INT_MAX); if (!ev) return; @@ -435,7 +435,7 @@ static void check_gas_change_events(struct dive *dive, struct divecomputer *dc, cylinderindex = get_cylinder_index(dive, ev); ev = get_next_event(ev->next, "gaschange"); } while (ev); - set_cylinder_index(pi, i, cylinderindex, ~0u); + set_cylinder_index(pi, i, cylinderindex, INT_MAX); } static void check_setpoint_events(struct dive *dive, struct divecomputer *dc, struct plot_info *pi) @@ -456,7 +456,7 @@ static void check_setpoint_events(struct dive *dive, struct divecomputer *dc, st dc->divemode = CCR; ev = get_next_event(ev->next, "SP change"); } while (ev); - set_setpoint(pi, i, setpoint.mbar, ~0u); + set_setpoint(pi, i, setpoint.mbar, INT_MAX); } @@ -466,7 +466,7 @@ struct plot_info calculate_max_limits_new(struct dive *dive, struct divecomputer bool seen = false; static struct plot_info pi; int maxdepth = dive->maxdepth.mm; - int maxtime = 0; + unsigned int maxtime = 0; int maxpressure = 0, minpressure = INT_MAX; int maxhr = 0, minhr = INT_MAX; int mintemp = dive->mintemp.mkelvin; @@ -606,7 +606,7 @@ struct plot_data *populate_plot_entries(struct dive *dive, struct divecomputer * break; /* Add events if they are between plot entries */ - while (ev && ev->time.seconds < lasttime + offset) { + while (ev && (int)ev->time.seconds < lasttime + offset) { INSERT_ENTRY(ev->time.seconds, interpolate(lastdepth, depth, ev->time.seconds - lasttime, delta), sac); ev = ev->next; } @@ -615,12 +615,12 @@ struct plot_data *populate_plot_entries(struct dive *dive, struct divecomputer * INSERT_ENTRY(lasttime + offset, interpolate(lastdepth, depth, offset, delta), sac); /* skip events that happened at this time */ - while (ev && ev->time.seconds == lasttime + offset) + while (ev && (int)ev->time.seconds == lasttime + offset) ev = ev->next; } /* Add events if they are between plot entries */ - while (ev && ev->time.seconds < time) { + while (ev && (int)ev->time.seconds < time) { INSERT_ENTRY(ev->time.seconds, interpolate(lastdepth, depth, ev->time.seconds - lasttime, delta), sac); ev = ev->next; } @@ -659,7 +659,7 @@ struct plot_data *populate_plot_entries(struct dive *dive, struct divecomputer * if (sample->rbt.seconds) entry->rbt = sample->rbt.seconds; /* skip events that happened at this time */ - while (ev && ev->time.seconds == time) + while (ev && (int)ev->time.seconds == time) ev = ev->next; lasttime = time; lastdepth = depth; diff --git a/subsurface-core/qthelper.cpp b/subsurface-core/qthelper.cpp index 7c67e0993..e103b44e5 100644 --- a/subsurface-core/qthelper.cpp +++ b/subsurface-core/qthelper.cpp @@ -1108,11 +1108,14 @@ QString fileFromHash(char *hash) return localFilenameOf[QByteArray::fromHex(hash)]; } +// This needs to operate on a copy of picture as it frees it after finishing! void updateHash(struct picture *picture) { QByteArray hash = hashFile(fileFromHash(picture->hash)); learnHash(picture, hash); + picture_free(picture); } +// This needs to operate on a copy of picture as it frees it after finishing! void hashPicture(struct picture *picture) { char *oldHash = copy_string(picture->hash); @@ -1120,13 +1123,14 @@ void hashPicture(struct picture *picture) if (!same_string(picture->hash, "") && !same_string(picture->hash, oldHash)) mark_divelist_changed((true)); free(oldHash); + picture_free(picture); } extern "C" void cache_picture(struct picture *picture) { QString filename = picture->filename; if (!hashOf.contains(filename)) - QtConcurrent::run(hashPicture, picture); + QtConcurrent::run(hashPicture, clone_picture(picture)); } void learnImages(const QDir dir, int max_recursions) @@ -1476,7 +1480,12 @@ void loadPreferences() s.beginGroup("CloudStorage"); GET_TXT("email", cloud_storage_email); +#ifndef SUBSURFACE_MOBILE GET_BOOL("save_password_local", save_password_local); +#else + // always save the password in Subsurface-mobile + prefs.save_password_local = true; +#endif if (prefs.save_password_local) { // GET_TEXT macro is not a single statement GET_TXT("password", cloud_storage_password); } @@ -1513,6 +1522,11 @@ void loadPreferences() GET_ENUM("cat2", taxonomy_category, geocoding.category[2]); s.endGroup(); + // GPS service time and distance thresholds + s.beginGroup("LocationService"); + GET_INT("time_threshold", time_threshold); + GET_INT("distance_threshold", distance_threshold); + s.endGroup(); } extern "C" bool isCloudUrl(const char *filename) diff --git a/subsurface-core/qtserialbluetooth.cpp b/subsurface-core/qtserialbluetooth.cpp index 025ab8c34..6b104157a 100644 --- a/subsurface-core/qtserialbluetooth.cpp +++ b/subsurface-core/qtserialbluetooth.cpp @@ -313,6 +313,7 @@ static int qt_serial_write(serial_t *device, const void* data, unsigned int size static int qt_serial_flush(serial_t *device, int queue) { + (void)queue; if (device == NULL) return DC_STATUS_INVALIDARGS; #if !defined(Q_OS_WIN) diff --git a/subsurface-core/save-git.c b/subsurface-core/save-git.c index 054c7e9b4..d089095b6 100644 --- a/subsurface-core/save-git.c +++ b/subsurface-core/save-git.c @@ -1,3 +1,6 @@ +// Clang has a bug on zero-initialization of C structs. +#pragma clang diagnostic ignored "-Wmissing-field-initializers" + #include <stdio.h> #include <ctype.h> #include <string.h> diff --git a/subsurface-core/save-html.c b/subsurface-core/save-html.c index 5fc5b000a..2d0ea9cf3 100644 --- a/subsurface-core/save-html.c +++ b/subsurface-core/save-html.c @@ -1,3 +1,6 @@ +// Clang has a bug on zero-initialization of C structs. +#pragma clang diagnostic ignored "-Wmissing-field-initializers" + #include "save-html.h" #include "qthelperfromc.h" #include "gettext.h" diff --git a/subsurface-core/save-xml.c b/subsurface-core/save-xml.c index eabcf4f26..2335637e8 100644 --- a/subsurface-core/save-xml.c +++ b/subsurface-core/save-xml.c @@ -1,3 +1,6 @@ +// Clang has a bug on zero-initialization of C structs. +#pragma clang diagnostic ignored "-Wmissing-field-initializers" + #include <stdio.h> #include <ctype.h> #include <string.h> diff --git a/subsurface-core/statistics.c b/subsurface-core/statistics.c index 373a6a0d0..6a05cffc1 100644 --- a/subsurface-core/statistics.c +++ b/subsurface-core/statistics.c @@ -48,7 +48,7 @@ static void process_temperatures(struct dive *dp, stats_t *stats) static void process_dive(struct dive *dp, stats_t *stats) { int old_tt, sac_time = 0; - int duration = dp->duration.seconds; + uint32_t duration = dp->duration.seconds; old_tt = stats->total_time.seconds; stats->total_time.seconds += duration; @@ -297,14 +297,14 @@ static void get_ranges(char *buffer, int size) } } -void get_selected_dives_text(char *buffer, int size) +void get_selected_dives_text(char *buffer, size_t size) { if (amount_selected == 1) { if (current_dive) snprintf(buffer, size, translate("gettextFromC", "for dive #%d"), current_dive->number); else snprintf(buffer, size, "%s", translate("gettextFromC", "for selected dive")); - } else if (amount_selected == dive_table.nr) { + } else if (amount_selected == (unsigned int)dive_table.nr) { snprintf(buffer, size, "%s", translate("gettextFromC", "for all dives")); } else if (amount_selected == 0) { snprintf(buffer, size, "%s", translate("gettextFromC", "(no dives)")); @@ -313,7 +313,7 @@ void get_selected_dives_text(char *buffer, int size) if (strlen(buffer) == size - 1) { /* add our own ellipse... the way Pango does this is ugly * as it will leave partial numbers there which I don't like */ - int offset = 4; + size_t offset = 4; while (offset < size && isdigit(buffer[size - offset])) offset++; strcpy(buffer + size - offset, "..."); diff --git a/subsurface-core/statistics.h b/subsurface-core/statistics.h index 890e6e53c..015c3481e 100644 --- a/subsurface-core/statistics.h +++ b/subsurface-core/statistics.h @@ -44,7 +44,7 @@ extern stats_t *stats_by_type; extern char *get_time_string_s(int seconds, int maxdays, bool freediving); extern char *get_minutes(int seconds); extern void process_all_dives(struct dive *dive, struct dive **prev_dive); -extern void get_selected_dives_text(char *buffer, int size); +extern void get_selected_dives_text(char *buffer, size_t size); extern void get_gas_used(struct dive *dive, volume_t gases[MAX_CYLINDERS]); extern void process_selected_dives(void); void selected_dives_gas_parts(volume_t *o2_tot, volume_t *he_tot); diff --git a/subsurface-core/subsurfacestartup.c b/subsurface-core/subsurfacestartup.c index 864134724..6e0dede1c 100644 --- a/subsurface-core/subsurfacestartup.c +++ b/subsurface-core/subsurfacestartup.c @@ -217,6 +217,10 @@ void parse_argument(const char *arg) run_survey = true; return; } + if (strcmp(arg, "--allow_run_as_root") == 0) { + ++force_root; + return; + } if (strcmp(arg, "--win32console") == 0) return; /* fallthrough */ @@ -233,18 +237,6 @@ void parse_argument(const char *arg) } while (*++p); } -void renumber_dives(int start_nr, bool selected_only) -{ - int i, nr = start_nr; - struct dive *dive; - - for_each_dive (i, dive) { - if (dive->selected) - dive->number = nr++; - } - mark_divelist_changed(true); -} - /* * Under a POSIX setup, the locale string should have a format * like [language[_territory][.codeset][@modifier]]. diff --git a/subsurface-core/time.c b/subsurface-core/time.c index b658954bc..0893f19d8 100644 --- a/subsurface-core/time.c +++ b/subsurface-core/time.c @@ -11,16 +11,16 @@ */ void utc_mkdate(timestamp_t timestamp, struct tm *tm) { - static const int mdays[] = { + static const unsigned int mdays[] = { 31, 28, 31, 30, 31, 30, 31, 31, 30, 31, 30, 31, }; - static const int mdays_leap[] = { + static const unsigned int mdays_leap[] = { 31, 29, 31, 30, 31, 30, 31, 31, 30, 31, 30, 31, }; unsigned long val; unsigned int leapyears; int m; - const int *mp; + const unsigned int *mp; memset(tm, 0, sizeof(*tm)); diff --git a/subsurface-core/uemis-downloader.c b/subsurface-core/uemis-downloader.c index 6f5c5f177..b9b532303 100644 --- a/subsurface-core/uemis-downloader.c +++ b/subsurface-core/uemis-downloader.c @@ -506,7 +506,8 @@ static bool uemis_get_answer(const char *path, char *request, int n_param_in, #if UEMIS_DEBUG & 4 fprintf(debugfile, "::w req.txt \"%s\"\n", sb); #endif - if (write(reqtxt_file, sb, strlen(sb)) != strlen(sb)) { + int written = write(reqtxt_file, sb, strlen(sb)); + if (written == -1 || (size_t)written != strlen(sb)) { *error_text = translate("gettextFromC", ERR_FS_SHORT_WRITE); return false; } @@ -784,7 +785,7 @@ static bool uemis_delete_dive(device_data_t *devdata, uint32_t diveid) * index into yet another data store that we read out later. In order to * correctly populate the location and gps data from that we need to remember * the addresses of those fields for every dive that references the divespot. */ -static bool process_raw_buffer(device_data_t *devdata, uint32_t deviceid, char *inbuf, char **max_divenr, bool keep_number, int *for_dive) +static bool process_raw_buffer(device_data_t *devdata, uint32_t deviceid, char *inbuf, char **max_divenr, int *for_dive) { char *buf = strdup(inbuf); char *tp, *bp, *tag, *type, *val; @@ -793,7 +794,7 @@ static bool process_raw_buffer(device_data_t *devdata, uint32_t deviceid, char * char *endptr = buf + inbuflen; bool is_log = false, is_dive = false; char *sections[10]; - int s, nr_sections = 0; + size_t s, nr_sections = 0; struct dive *dive = NULL; char dive_no[10]; @@ -974,7 +975,7 @@ static char *uemis_get_divenr(char *deviceidstr, int force) maxdiveid = dc->diveid; } } - if (max_deleted_seen >= 0 && maxdiveid < max_deleted_seen) { + if (max_deleted_seen >= 0 && maxdiveid < (uint32_t)max_deleted_seen) { maxdiveid = max_deleted_seen; #if UEMIS_DEBUG & 4 fprintf(debugfile, "overriding max seen with max deleted seen %d\n", max_deleted_seen); @@ -1154,7 +1155,7 @@ static bool get_matching_dive(int idx, char *newmax, int *uemis_mem_status, stru * we mark the search successful even if the dive has been deleted. */ found = true; if (strstr(mbuf, "deleted{bool{true") == NULL) { - process_raw_buffer(data, deviceidnr, mbuf, &newmax, false, NULL); + process_raw_buffer(data, deviceidnr, mbuf, &newmax, NULL); /* remember the last log file number as it is very likely that subsequent dives * have the same or higher logfile number. * UEMIS unfortunately deletes dives by deleting the dive details and not the logs. */ @@ -1223,7 +1224,7 @@ const char *do_uemis_import(device_data_t *data) char *deviceid = NULL; const char *result = NULL; char *endptr; - bool success, keep_number = false, once = true; + bool success, once = true; int match_dive_and_log = 0; int uemis_mem_status = UEMIS_MEM_OK; @@ -1231,9 +1232,6 @@ const char *do_uemis_import(device_data_t *data) home = getenv("HOME"); user = getenv("LOGNAME"); #endif - if (dive_table.nr == 0) - keep_number = true; - uemis_info(translate("gettextFromC", "Initialise communication")); if (!uemis_init(mountpath)) { free(reqtxt_path); @@ -1287,7 +1285,7 @@ const char *do_uemis_import(device_data_t *data) do_dump_buffer_to_file(realmbuf, "Divelogs"); #endif /* process the buffer we have assembled */ - if (!process_raw_buffer(data, deviceidnr, realmbuf, &newmax, keep_number, NULL)) { + if (!process_raw_buffer(data, deviceidnr, realmbuf, &newmax, NULL)) { /* if no dives were downloaded, mark end appropriately */ if (end == -2) end = start - 1; diff --git a/subsurface-core/uemis.c b/subsurface-core/uemis.c index 4135e0cfe..5635d5630 100644 --- a/subsurface-core/uemis.c +++ b/subsurface-core/uemis.c @@ -98,7 +98,7 @@ static int uemis_convert_base64(char *base64, uint8_t **data) } struct uemis_helper { - int diveid; + uint32_t diveid; int lbs; int divespot; int dive_site_uuid; @@ -106,7 +106,7 @@ struct uemis_helper { }; static struct uemis_helper *uemis_helper = NULL; -static struct uemis_helper *uemis_get_helper(int diveid) +static struct uemis_helper *uemis_get_helper(uint32_t diveid) { struct uemis_helper **php = &uemis_helper; struct uemis_helper *hp = *php; @@ -134,7 +134,7 @@ static void uemis_weight_unit(int diveid, int lbs) hp->lbs = lbs; } -int uemis_get_weight_unit(int diveid) +int uemis_get_weight_unit(uint32_t diveid) { struct uemis_helper *hp = uemis_helper; while (hp) { diff --git a/subsurface-core/uemis.h b/subsurface-core/uemis.h index 5f32fe76c..1758b4b32 100644 --- a/subsurface-core/uemis.h +++ b/subsurface-core/uemis.h @@ -13,7 +13,7 @@ extern "C" { #endif void uemis_parse_divelog_binary(char *base64, void *divep); -int uemis_get_weight_unit(int diveid); +int uemis_get_weight_unit(uint32_t diveid); void uemis_mark_divelocation(int diveid, int divespot, uint32_t dive_site_uuid); void uemis_set_divelocation(int divespot, char *text, double longitude, double latitude); int uemis_get_divespot_id_by_diveid(uint32_t diveid); diff --git a/subsurface-core/units.h b/subsurface-core/units.h index 9ad4b7282..029bb64fa 100644 --- a/subsurface-core/units.h +++ b/subsurface-core/units.h @@ -99,7 +99,7 @@ typedef struct typedef struct { - int32_t mkelvin; // up to 1750 degrees K + uint32_t mkelvin; // up to 1750 degrees K (temperatures in K are always positive) } temperature_t; typedef struct diff --git a/subsurface-core/windows.c b/subsurface-core/windows.c index a2386fd83..58d3beaad 100644 --- a/subsurface-core/windows.c +++ b/subsurface-core/windows.c @@ -446,3 +446,9 @@ void subsurface_console_exit(void) FreeConsole(); #endif } + +bool subsurface_user_is_root() +{ + /* FIXME: Detect admin rights */ + return (false); +} diff --git a/subsurface-core/worldmap-save.c b/subsurface-core/worldmap-save.c index f79978495..e7e8bcc30 100644 --- a/subsurface-core/worldmap-save.c +++ b/subsurface-core/worldmap-save.c @@ -1,3 +1,6 @@ +// Clang has a bug on zero-initialization of C structs. +#pragma clang diagnostic ignored "-Wmissing-field-initializers" + #include <stdarg.h> #include <stdlib.h> #include <string.h> diff --git a/subsurface-desktop-main.cpp b/subsurface-desktop-main.cpp index 2b7bf89f6..b93b642bd 100644 --- a/subsurface-desktop-main.cpp +++ b/subsurface-desktop-main.cpp @@ -59,6 +59,11 @@ int main(int argc, char **argv) files.push_back(a); } } + if (subsurface_user_is_root() && !force_root) { + printf("You are running Subsurface as root. This is not recommended.\n"); + printf("If you insist to do so, run with option --allow_run_as_root.\n"); + exit(0); + } #if !LIBGIT2_VER_MAJOR && LIBGIT2_VER_MINOR < 22 git_threads_init(); #else diff --git a/subsurface-mobile-helper.cpp b/subsurface-mobile-helper.cpp index f6c669438..214d65e79 100644 --- a/subsurface-mobile-helper.cpp +++ b/subsurface-mobile-helper.cpp @@ -12,6 +12,7 @@ #include "qt-gui.h" #include <QQuickWindow> +#include <QScreen> #include <QQmlApplicationEngine> #include <QQmlContext> #include <QSortFilterProxyModel> @@ -56,7 +57,7 @@ void run_ui() QSortFilterProxyModel *gpsSortModel = new QSortFilterProxyModel(0); gpsSortModel->setSourceModel(&gpsListModel); gpsSortModel->setDynamicSortFilter(true); - gpsSortModel->setSortRole(GpsListModel::GpsDateRole); + gpsSortModel->setSortRole(GpsListModel::GpsWhenRole); gpsSortModel->sort(0, Qt::DescendingOrder); QQmlContext *ctxt = engine.rootContext(); ctxt->setContextProperty("diveModel", sortModel); @@ -70,6 +71,12 @@ void run_ui() QQuickWindow *qml_window = qobject_cast<QQuickWindow *>(qqWindowObject); qml_window->setIcon(QIcon(":/subsurface-mobile-icon")); qqWindowObject->setProperty("messageText", QVariant("Subsurface-mobile startup")); + qDebug() << "qqwindow devicePixelRatio" << qml_window->devicePixelRatio() << qml_window->screen()->devicePixelRatio(); + QScreen *screen = qml_window->screen(); + QObject::connect(qml_window, &QQuickWindow::screenChanged, QMLManager::instance(), &QMLManager::screenChanged); + QMLManager::instance()->screenChanged(screen); + qDebug() << "qqwindow screen has ldpi/pdpi" << screen->logicalDotsPerInch() << screen->physicalDotsPerInch(); + #if !defined(Q_OS_ANDROID) qml_window->setHeight(1200); qml_window->setWidth(800); diff --git a/subsurface-mobile-main.cpp b/subsurface-mobile-main.cpp index 7ed3e4256..940c9225b 100644 --- a/subsurface-mobile-main.cpp +++ b/subsurface-mobile-main.cpp @@ -61,9 +61,10 @@ int main(int argc, char **argv) taglist_init_global(); init_ui(); loadPreferences(); - prefs.animation_speed = 0; + // some hard coded settings + prefs.animation_speed = 0; // we render the profile to pixmap, no animations - /* always show the divecomputer reported ceiling in red */ + // always show the divecomputer reported ceiling in red prefs.dcceiling = 1; prefs.redceiling = 1; diff --git a/tests/CMakeLists.txt b/tests/CMakeLists.txt index 23642fb3c..a31e2c6f8 100644 --- a/tests/CMakeLists.txt +++ b/tests/CMakeLists.txt @@ -1,7 +1,7 @@ # QTest based tests macro(TEST NAME FILE) - add_executable(${NAME} ${FILE} ) - target_link_libraries(${NAME} subsurface_corelib ${QT_TEST_LIBRARIES} ${SUBSURFACE_LINK_LIBRARIES}) + add_executable(${NAME} ${FILE} ${SUBSURFACE_RESOURCES} ) + target_link_libraries(${NAME} subsurface_corelib ${QT_TEST_LIBRARIES} ${SUBSURFACE_LINK_LIBRARIES} ) add_test(NAME ${NAME} COMMAND $<TARGET_FILE:${NAME}>) endmacro() diff --git a/tests/testgitstorage.cpp b/tests/testgitstorage.cpp index 891982151..30417b3c4 100644 --- a/tests/testgitstorage.cpp +++ b/tests/testgitstorage.cpp @@ -233,6 +233,7 @@ void TestGitStorage::testGitStorageCloudMerge2() QCOMPARE(parse_file(qPrintable(cloudTestRepo)), 0); process_dives(false, false); dive = get_dive(1); + QVERIFY(dive != NULL); free(dive->notes); dive->notes = strdup("These notes have been modified by TestGitStorage"); QCOMPARE(save_dives(qPrintable(cloudTestRepo)), 0); diff --git a/tests/testparse.cpp b/tests/testparse.cpp index 5528d0df2..8bb092b56 100644 --- a/tests/testparse.cpp +++ b/tests/testparse.cpp @@ -360,7 +360,6 @@ void TestParse::testParseCompareNewFormatOutput() void TestParse::testParseDLD() { struct memblock mem; - int ret, success = 0; QString filename = SUBSURFACE_SOURCE "/dives/TestDiveDivelogsDE.DLD"; QVERIFY(readfile(filename.toLatin1().data(), &mem) > 0); diff --git a/tests/testplan.cpp b/tests/testplan.cpp index 2b91ab785..50966af0c 100644 --- a/tests/testplan.cpp +++ b/tests/testplan.cpp @@ -70,7 +70,6 @@ void setupPlanVpmb60m30minAir(struct diveplan *dp) dp->decosac = 0; struct gasmix bottomgas = { {210}, {0} }; - pressure_t po2 = { 1600 }; displayed_dive.cylinder[0].gasmix = bottomgas; displayed_dive.surface_pressure.mbar = 1013; reset_cylinders(&displayed_dive, true); @@ -133,7 +132,6 @@ void setupPlanVpmbMultiLevelAir(struct diveplan *dp) dp->decosac = 0; struct gasmix bottomgas = { {210}, {0} }; - pressure_t po2 = { 1600 }; displayed_dive.cylinder[0].gasmix = bottomgas; displayed_dive.surface_pressure.mbar = 1013; reset_cylinders(&displayed_dive, true); @@ -204,7 +202,6 @@ void setupPlanVpmb30m20min(struct diveplan *dp) dp->decosac = 0; struct gasmix bottomgas = { {210}, {0} }; - pressure_t po2 = { 1600 }; displayed_dive.cylinder[0].gasmix = bottomgas; displayed_dive.surface_pressure.mbar = 1013; reset_cylinders(&displayed_dive, true); @@ -289,7 +286,7 @@ void TestPlan::testMetric() prefs.units.length = units::METERS; prefs.deco_mode = BUEHLMANN; - struct diveplan testPlan = { 0 }; + struct diveplan testPlan = {}; setupPlan(&testPlan); plan(&testPlan, &cache, 1, 0); @@ -325,7 +322,7 @@ void TestPlan::testImperial() prefs.units.length = units::FEET; prefs.deco_mode = BUEHLMANN; - struct diveplan testPlan = { 0 }; + struct diveplan testPlan = {}; setupPlan(&testPlan); plan(&testPlan, &cache, 1, 0); @@ -360,7 +357,7 @@ void TestPlan::testVpmbMetric60m30minAir() prefs.unit_system = METRIC; prefs.units.length = units::METERS; - struct diveplan testPlan = { 0 }; + struct diveplan testPlan = {}; setupPlanVpmb60m30minAir(&testPlan); setCurrentAppState("PlanDive"); @@ -386,7 +383,7 @@ void TestPlan::testVpmbMetric60m30minEan50() prefs.unit_system = METRIC; prefs.units.length = units::METERS; - struct diveplan testPlan = { 0 }; + struct diveplan testPlan = {}; setupPlanVpmb60m30minEan50(&testPlan); setCurrentAppState("PlanDive"); @@ -418,7 +415,7 @@ void TestPlan::testVpmbMetric60m30minTx() prefs.unit_system = METRIC; prefs.units.length = units::METERS; - struct diveplan testPlan = { 0 }; + struct diveplan testPlan = {}; setupPlanVpmb60m30minTx(&testPlan); setCurrentAppState("PlanDive"); @@ -450,7 +447,7 @@ void TestPlan::testVpmbMetric100m60min() prefs.unit_system = METRIC; prefs.units.length = units::METERS; - struct diveplan testPlan = { 0 }; + struct diveplan testPlan = {}; setupPlanVpmb100m60min(&testPlan); setCurrentAppState("PlanDive"); @@ -488,7 +485,7 @@ void TestPlan::testVpmbMetricMultiLevelAir() prefs.unit_system = METRIC; prefs.units.length = units::METERS; - struct diveplan testPlan = { 0 }; + struct diveplan testPlan = {}; setupPlanVpmbMultiLevelAir(&testPlan); setCurrentAppState("PlanDive"); @@ -514,7 +511,7 @@ void TestPlan::testVpmbMetric100m10min() prefs.unit_system = METRIC; prefs.units.length = units::METERS; - struct diveplan testPlan = { 0 }; + struct diveplan testPlan = {}; setupPlanVpmb100m10min(&testPlan); setCurrentAppState("PlanDive"); @@ -556,7 +553,7 @@ void TestPlan::testVpmbMetricRepeat() prefs.unit_system = METRIC; prefs.units.length = units::METERS; - struct diveplan testPlan = { 0 }; + struct diveplan testPlan = {}; setupPlanVpmb30m20min(&testPlan); setCurrentAppState("PlanDive"); diff --git a/xslt/uddf-export.xslt b/xslt/uddf-export.xslt index cb6a66f98..42dbbf0b9 100644 --- a/xslt/uddf-export.xslt +++ b/xslt/uddf-export.xslt @@ -38,6 +38,7 @@ <xsl:template match="/divelog/settings"/> + <xsl:template match="/divelog/divesites"/> <xsl:template match="/divelog/dives"> <uddf version="3.2.0" xmlns="http://www.streit.cc/uddf/3.2/"> @@ -121,7 +122,6 @@ </diver> <divesite> - <!-- There must be at least one divebase. Subsurface doesn't track this as a concept, so just assign them all to a single divebase. --> <divebase id="allbase"> <name>Subsurface Divebase</name> @@ -235,6 +235,13 @@ <xsl:value-of select="substring-after(@gps, ' ')"/> </longitude> </geography> + <xsl:if test="notes != ''"> + <sitedata> + <notes> + <xsl:value-of select="notes"/> + </notes> + </sitedata> + </xsl:if> </site> </xsl:template> diff --git a/xslt/xml2manualcsv.xslt b/xslt/xml2manualcsv.xslt index d6c1a8b3b..82f4979d4 100644 --- a/xslt/xml2manualcsv.xslt +++ b/xslt/xml2manualcsv.xslt @@ -17,6 +17,8 @@ <xsl:apply-templates select="dive|trip/dive"/> </xsl:template> + <xsl:template match="divesites/site/notes"/> + <xsl:template match="dive"> <xsl:text>"</xsl:text> <xsl:value-of select="@number"/> |
