subsurface/Documentation/50-pot/subsurface-manual.pot

# 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: 2015-10-29 10:38+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
#: ./user-manual.txt:14
#, no-wrap
msgid "images/Subsurface4Banner.jpg"
msgstr ""

#. type: Plain text
#: ./user-manual.txt:17
msgid "[big]#USER MANUAL#"
msgstr ""

#. type: Plain text
#: ./user-manual.txt:20
#, no-wrap
msgid ""
"*Manual authors*: Willem Ferguson, Jacco van Koll, Dirk Hohndel, Reinout "
"Hoornweg,\n"
"Linus Torvalds, Miika Turkia, Amit Chaudhuri, Jan Schubert, Salvador Cuñat, "
"Pedro Neves\n"
msgstr ""

#. type: Plain text
#: ./user-manual.txt:22
msgid "[blue]#_Version 4.5, October 2015_#"
msgstr ""

#. type: Plain text
#: ./user-manual.txt:28
msgid ""
"Welcome as a user of _Subsurface_, an advanced dive logging program with "
"extensive infrastructure to describe, organise, interpret and print scuba "
"and free dives. _Subsurface_ offers many advantages over other similar "
"software solutions:"
msgstr ""

#. type: Plain text
#: ./user-manual.txt:31
msgid ""
"Do you need a flexible way of logging dives using recreational equipment, "
"even not using a dive computer?"
msgstr ""

#. type: Plain text
#: ./user-manual.txt:37
msgid ""
"Do you use two different dive computer brands, each with its own proprietary "
"software for downloading dive logs? Do you dive with rebreathers as well as "
"open circuit or recreational equipment? Do you use a Reefnet Sensus "
"time-depth recorder in conjunction with a dive computer? _Subsurface_ offers "
"a standard interface for downloading dive logs from all these different "
"pieces of equipment and to store and analyse the dive logs within a unified "
"system."
msgstr ""

#. type: Plain text
#: ./user-manual.txt:40
msgid ""
"Do you use more than one operating system? _Subsurface_ is fully compatible "
"with Mac, Linux and Windows, allowing you to access your dive log on each of "
"your operating systems using a single application."
msgstr ""

#. type: Plain text
#: ./user-manual.txt:43
msgid ""
"Do you use Linux or Mac and your dive computer has only Windows-based "
"software for downloading dive information (e.g. Mares)? _Subsurface_ "
"provides a way of downloading and analysing your dive logs on other "
"operating systems."
msgstr ""

#. type: Plain text
#: ./user-manual.txt:45
msgid ""
"Do you need an intuitive graphical dive planner that integrates with and "
"takes into account the dives that have already been logged?"
msgstr ""

#. type: Plain text
#: ./user-manual.txt:47
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 ""
"_Subsurface_ binaries are available for Windows PCs (Win XP or later), Intel "
"based Macs (OS/X) and many Linux distributions. _Subsurface_ can be built "
"for many more hardware platforms and software environments where Qt and "
"libdivecomputer are available."
msgstr ""

#. type: Plain text
#: ./user-manual.txt:61
msgid ""
"The scope of this document is the use of the _Subsurface_ program. To "
"install the software, consult the _Downloads_ page on the "
"http://subsurface-divelog.org/[_Subsurface_ web site].  Please discuss "
"issues with this program by sending an email to "
"mailto:subsurface@subsurface-divelog.org[our mailing list] and report bugs "
"at http://trac.hohndel.org[our bugtracker].  For instructions on how to "
"build the software and (if needed) its dependencies please consult the "
"INSTALL file included with the source code."
msgstr ""

#. type: Plain text
#: ./user-manual.txt:64
#, no-wrap
msgid ""
"*Audience*: Recreational Scuba Divers, Free Divers, Tec Divers, "
"Professional\n"
"Divers\n"
msgstr ""

#. type: Plain text
#: ./user-manual.txt:66
msgid "toc::[]"
msgstr ""

#. type: Title -
#: ./user-manual.txt:69
#, no-wrap
msgid "Using this manual"
msgstr ""

#. type: Plain text
#: ./user-manual.txt:72
msgid ""
"When opened from within _Subsurface_, this manual does not have external "
"controls for paging or selecting previous pages. However, two facilities are "
"provided:"
msgstr ""

#. type: Plain text
#: ./user-manual.txt:79
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."
msgstr ""

#. type: Target for macro image
#: ./user-manual.txt:80
#, no-wrap
msgid "images/usermanualfunctions.jpg"
msgstr ""

#. type: Plain text
#: ./user-manual.txt:91
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."
msgstr ""

#. type: Title -
#: ./user-manual.txt:94
#, no-wrap
msgid "The user survey"
msgstr ""

#. 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."
msgstr ""

#. type: Title -
#: ./user-manual.txt:109
#, no-wrap
msgid "Start Using the Program"
msgstr ""

#. type: Plain text
#: ./user-manual.txt:114
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 "
"Linux) or the top of the screen (for Mac and Ubuntu Unity). The four panels "
"are:"
msgstr ""

#. type: Plain text
#: ./user-manual.txt:120
msgid ""
"The *Dive List* to the bottom left containing a list of all the dives in the "
"user's dive log. A dive can be selected and highlighted on the dive list by "
"clicking on it. In most situations the up/down keys can be used to switch "
"between dives. The *Dive List* is an important tool for manipulating a dive "
"log."
msgstr ""

#. type: Plain text
#: ./user-manual.txt:124
msgid ""
"The *Dive Map* to the bottom right, showing the user's dive sites on a world "
"map and centred on the site of the last dive selected in the *Dive List*."
msgstr ""

#. type: Plain text
#: ./user-manual.txt:128
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)."
msgstr ""

#. type: Plain text
#: ./user-manual.txt:131
msgid ""
"The *Dive Profile* to the top right, showing a graphical dive profile of the "
"selected dive in the *Dive List*."
msgstr ""

#. type: Plain text
#: ./user-manual.txt: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."
msgstr ""

#. type: Plain text
#: ./user-manual.txt:144
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)."
msgstr ""

#. type: Target for macro image
#: ./user-manual.txt:147
#, no-wrap
msgid "images/main_window_f22.jpg"
msgstr ""

#. type: Plain text
#: ./user-manual.txt:152
msgid ""
"The user can determine which of the four panels are displayed by selecting "
"the *View* option on the main menu. This feature gives the user several "
"choices of display:"
msgstr ""

#. type: Plain text
#: ./user-manual.txt:154
#, no-wrap
msgid "*All*: show all four of the panels as in the screenshot above.\n"
msgstr ""

#. type: Plain text
#: ./user-manual.txt:156
#, no-wrap
msgid "*Divelist*: Show only the Dive List.\n"
msgstr ""

#. type: Plain text
#: ./user-manual.txt:158
#, no-wrap
msgid "*Profile*: Show only the Dive Profile of the selected dive.\n"
msgstr ""

#. type: Plain text
#: ./user-manual.txt:161
#, no-wrap
msgid ""
"*Info*: Show only the Notes about the last selected dive and statistics "
"for\n"
"all highlighted dives.\n"
msgstr ""

#. type: Plain text
#: ./user-manual.txt:163
#, no-wrap
msgid "*Globe*: Show only the world map, centred on the last selected dive.\n"
msgstr ""

#. 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 "
"particular system are shown with an underline in the main menu "
"entries. Since different Operating Systems and the user chosen language may "
"cause _Subsurface_ to use different shortcut keys they are not listed here "
"in the user manual."
msgstr ""

#. type: Plain text
#: ./user-manual.txt:173
msgid ""
"When the program is started for the first time, it shows no information at "
"all.  This is because the program doesn't have any dive information "
"available. In the following sections, the procedures to create a new logbook "
"will be described."
msgstr ""

#. type: Title -
#: ./user-manual.txt:176
#, no-wrap
msgid "Creating a new logbook"
msgstr ""

#. type: Plain text
#: ./user-manual.txt:181
msgid ""
"Select _File -> New Logbook_ from the main menu. All existing dive data are "
"cleared so that new information can be added. If there are unsaved data in "
"an open logbook, the user is asked whether the open logbook should be saved "
"before a new logbook is created."
msgstr ""

#. type: Title ==
#: ./user-manual.txt:183
#, no-wrap
msgid "Storing dive information in the logbook"
msgstr ""

#. type: Plain text
#: ./user-manual.txt:188
msgid ""
"Now that a new logbook was created, it is simple to add dive data to it.  "
"_Subsurface_ allows several ways of adding dive data to a logbook, detailed "
"in the following sections."
msgstr ""

#. type: Plain text
#: ./user-manual.txt:190
msgid "If the user has a handwritten divelog, a spreadsheet or another form of"
msgstr ""

#. type: Plain text
#: ./user-manual.txt:192
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"
msgstr ""

#. type: Plain text
#: ./user-manual.txt:196
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
msgid "Import dive log information that has been maintained either as a spreadsheet"
msgstr ""

#. type: Plain text
#: ./user-manual.txt:200
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 "
"in CSV format]."
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
msgid ""
"dive and a large amount of additional information can be accessed. These "
"dives can be imported from:"
msgstr ""

#. type: Plain text
#: ./user-manual.txt:206
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
msgid "Proprietary software distributed by manufacturers of dive computers. Refer"
msgstr ""

#. type: Plain text
#: ./user-manual.txt:209
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."
msgstr ""

#. type: Plain text
#: ./user-manual.txt:212
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
#, no-wrap
msgid "Entering dive information by hand"
msgstr ""

#. type: Plain text
#: ./user-manual.txt:229
msgid ""
"This is usually the approach for dives without a dive computer. The basic "
"record of information within _Subsurface_ is a dive. The most important "
"information in a simple dive logbook usually includes dive type, date, time, "
"duration, depth, the names of your dive buddy and of the dive master or dive "
"guide, and some remarks about the dive. _Subsurface_ can store much more "
"information than this for each dive. In order to add a dive to a dive log, "
"select _Log -> Add Dive_ from the Main Menu. The program then shows three "
"panels to enter information for a dive: two tabs in the *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
#, no-wrap
msgid "images/AddDive1_f22.jpg"
msgstr ""

#. type: Plain text
#: ./user-manual.txt:235
msgid ""
"When one edits 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
#, no-wrap
msgid "images/BlueEditBar_f22.jpg"
msgstr ""

#. type: Plain text
#: ./user-manual.txt:243
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."
msgstr ""

#. type: Title ====
#: ./user-manual.txt:245
#, no-wrap
msgid "Creating a Dive Profile"
msgstr ""

#. type: Plain text
#: ./user-manual.txt:252
msgid ""
"The *Dive Profile* (a graphical representation of the depth of the dive as a "
"function of time) is indicated in the panel on the top right hand of the "
"_Subsurface_ window. When a dive is manually added to a logbook, "
"_Subsurface_ presents a default dive profile that needs to be modified to "
"best represent the dive being described:"
msgstr ""

#. type: Target for macro image
#: ./user-manual.txt:253
#, no-wrap
msgid "images/DiveProfile1_f20.jpg"
msgstr ""

#. type: Plain text
#: ./user-manual.txt:271
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."
msgstr ""

#. type: Target for macro image
#: ./user-manual.txt:272
#, no-wrap
msgid "images/DiveProfile2_f20.jpg"
msgstr ""

#. type: Plain text
#: ./user-manual.txt:284
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)."
msgstr ""

#. type: Target for macro image
#: ./user-manual.txt:285
#, no-wrap
msgid "images/DiveProfile3_f20.jpg"
msgstr ""

#. type: Plain text
#: ./user-manual.txt:292
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."
msgstr ""

#. type: Title ===
#: ./user-manual.txt:294
#, no-wrap
msgid "Importing new dive information from a Dive Computer"
msgstr ""

#. type: Title ====
#: ./user-manual.txt:296
#, no-wrap
msgid "Connecting and importing data from a dive computer."
msgstr ""

#. type: Plain text
#: ./user-manual.txt:307
msgid ""
"The use of dive computers allows the collection of a large amount of "
"information about each dive, e.g. a detailed record of depth, duration, "
"rates of ascent/descent and of gas partial pressures. _Subsurface_ can "
"capture this information and present it as part of the dive information, "
"using dive information from a wide range of dive computers. The latest list "
"of supported dive computers can be found at: "
"link:http://subsurface-divelog.org/documentation/supported-dive-computers/[ "
"Supported dive computers]."
msgstr ""

#. type: Named 'icon' AttributeList argument for style 'icon'
#: ./user-manual.txt:308 ./user-manual.txt:676 ./user-manual.txt:3061
#, no-wrap
msgid "images/icons/warning2.png"
msgstr ""

#. type: Plain text
#: ./user-manual.txt:319
msgid ""
"Several dive computers consume more power when they are in their "
"PC-Communication mode. **This could drain the dive computer's battery**. We "
"therefore recommend that the user checks if the dive computer is charged "
"when connected to the USB port of a PC. For example, several Suunto and "
"Mares dive computers do not recharge through the USB connection. Users "
"should refer to the dive computer's manual if they are unsure whether the "
"dive computer recharges its batteries while connected to the USB port."
msgstr ""

#. type: Plain text
#: ./user-manual.txt:335
msgid ""
"To import dive information from a dive computer to a computer with "
"_Subsurface_, it is necessary that the two pieces of equipment communicate "
"with one another.  This involves setting up the communications port (or "
"mount point) of the computer with _Subsurface_ that communicates with the "
"dive computer. In order to set up this communication, one needs to find the "
"appropriate information to instruct _Subsurface_ where and how to import the "
"dive information.  "
"xref:_appendix_a_operating_system_specific_information_for_importing_dive_information_from_a_dive_computer[Appendix "
"A] provides the technical information to help the user achieving this for "
"different operating systems and "
"xref:_appendix_b_dive_computer_specific_information_for_importing_dive_information[Appendix "
"B] has dive computer specific information."
msgstr ""

#. type: Plain text
#: ./user-manual.txt:338
msgid ""
"After this, the dive computer can be hooked up to the user's PC, which can "
"be achieved by following these steps:"
msgstr ""

#. type: Plain text
#: ./user-manual.txt:340
msgid "The interface cable should be connected to a free USB port (or the Infra-red"
msgstr ""

#. type: Plain text
#: ./user-manual.txt:341
msgid "or Bluetooth connection set up as described later in this manual)"
msgstr ""

#. type: Plain text
#: ./user-manual.txt:343
msgid "The dive computer should be placed into PC Communication mode."
msgstr ""

#. type: Plain text
#: ./user-manual.txt:344
msgid "(Refer to the manual of the specific dive computer)"
msgstr ""

#. type: Plain text
#: ./user-manual.txt:348
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
#, no-wrap
msgid "images/DC_import_f20.jpg"
msgstr ""

#. type: Plain text
#: ./user-manual.txt:358
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)."
msgstr ""

#. type: Plain text
#: ./user-manual.txt:365
msgid ""
"The dialogue has two drop-down lists, *Vendor* and *Dive Computer*. On the "
"*vendor* drop-down list select the make of the computer, e.g.  Suunto, "
"Oceanic, Uwatec, Mares. On the *Dive Computer* drop-down list, the model "
"name of the dive computer must be selected, e.g. D4 (Suunto), Veo200 "
"(Oceanic), or Puck (Mares)."
msgstr ""

#. type: Plain text
#: ./user-manual.txt:376
msgid ""
"The *Device or Mount Point* drop-down list contains the USB or Bluetooth "
"port name that _Subsurface_ needs in order to communicate with the dive "
"computer.  The appropriate port name must be selected. Consult "
"xref:_appendix_a_operating_system_specific_information_for_importing_dive_information_from_a_dive_computer[Appendix "
"A] and "
"xref:_appendix_b_dive_computer_specific_information_for_importing_dive_information[Appendix "
"B] for technical details on how to find the appropriate port information for "
"a particular dive computer and, in some cases, how to do the correct "
"settings to the operating system of the computer on which _Subsurface_ is "
"running."
msgstr ""

#. type: Plain text
#: ./user-manual.txt:386
msgid ""
"If all the dives on the dive computer need to be downloaded, check the "
"checkbox _Force download of all dives_. Normally, _Subsurface_ only "
"downloads dives after the date-time of the last dive in the *Dive List* "
"panel. If one or more of your dives in _Subsurface_ have been accidentally "
"deleted or if there are older dives that still need to be downloaded from "
"the dive computer, this checkbox needs to be activated. Some dive computers "
"(e.g. Mares Puck) do not provide a contents list to _Subsurface_ before the "
"download in order to select only new dives.  Consequently, for these dive "
"computers, all dives are downloaded irrespective of the status of this check "
"box."
msgstr ""

#. type: Plain text
#: ./user-manual.txt:392
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."
msgstr ""

#. type: Plain text
#: ./user-manual.txt:395
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
msgid ""
"Do *not* check the checkboxes labelled _Save libdivecomputer logfile_ and "
"_Save libdivecomputer dumpfile_. These are only used as diagnostic tools "
"when problems with downloads are experienced (see below)."
msgstr ""

#. type: Plain text
#: ./user-manual.txt:419
msgid ""
"Then select the _Download_ 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 _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."
msgstr ""

#. type: Plain text
#: ./user-manual.txt:424
msgid ""
"After this has been completed, select the OK button.  The checked dives are "
"transferred to the *Dive List*."
msgstr ""

#. type: Plain text
#: ./user-manual.txt:428
msgid ""
"If there is a problem in communicating with the dive computer, an error "
"message will be shown, similar to this text: \"Unable to open /dev/ttyUSB0 "
"Mares (Puck Pro)\". Refer to the text in the box below."
msgstr ""

#. type: delimited block *
#: ./user-manual.txt:432
#, 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
#, no-wrap
msgid "images/icons/important.png"
msgstr ""

#. type: delimited block *
#: ./user-manual.txt:435
msgid "Check the following:"
msgstr ""

#. type: delimited block *
#: ./user-manual.txt:438
msgid "Is the dive computer still in PC-communication or Upload mode?"
msgstr ""

#. type: delimited block *
#: ./user-manual.txt:441
msgid ""
"Is the battery of the dive computer fully charged? If not then the battery "
"must be charged or replaced."
msgstr ""

#. type: delimited block *
#: ./user-manual.txt:445
msgid ""
"Is the connecting cable faulty? Does the cable work perfectly using other "
"software? Has it worked before, or is this the first time the cable is being "
"used? Are the contacts on the dive computer and the cable clean?"
msgstr ""

#. type: delimited block *
#: ./user-manual.txt:450
msgid ""
"Consult "
"xref:_appendix_a_operating_system_specific_information_for_importing_dive_information_from_a_dive_computer[Appendix "
"A] and make sure that the correct Mount Point was specified (see above)."
msgstr ""

#. type: delimited block *
#: ./user-manual.txt:454
msgid ""
"On Unix-like operating systems, does the user have write permission to the "
"USB port? If not, consult "
"xref:_appendix_a_operating_system_specific_information_for_importing_dive_information_from_a_dive_computer[Appendix "
"A]"
msgstr ""

#. type: delimited block *
#: ./user-manual.txt:462
msgid ""
"If the _Subsurface_ computer does not recognise the USB adaptor by showing "
"an appropriate device name next to the Mount Point, then there is a "
"possibility that the cable or USB adaptor is faulty. A faulty cable is the "
"most common cause of communication failure between dive computer and "
"_Subsurface_ computer. It is also possible that the _Subsurface_ computer "
"cannot interpret the data. Perform a download for diagnostic purposes with "
"the following two check boxes checked in the download dialogue discussed "
"above:"
msgstr ""

#. type: delimited block *
#: ./user-manual.txt:465
#, no-wrap
msgid ""
"\tSave libdivecomputer logfile\n"
"\tSave libdivecomputer dumpfile\n"
msgstr ""

#. type: delimited block *
#: ./user-manual.txt:471
#, no-wrap
msgid ""
"*Important*: These check boxes are only used when problems are encountered\n"
"during the download process: under normal circumstances they should not be "
"checked.\n"
"When checking these boxes, the user is prompted to select a folder to\n"
"save the information to. The default folder is the one in which the "
"_Subsurface_\n"
"dive log is kept.\n"
msgstr ""

#. type: delimited block *
#: ./user-manual.txt:475
#, no-wrap
msgid ""
"*Important:* _After downloading with the above checkboxes\n"
"checked, no dives are added to the\n"
"*Dive List* but two files are created in the folder selected above_:\n"
msgstr ""

#. type: delimited block *
#: ./user-manual.txt:478
#, no-wrap
msgid ""
"\tsubsurface.log\n"
"\tsubsurface.bin\n"
msgstr ""

#. type: delimited block *
#: ./user-manual.txt:484
msgid ""
"These files should be send to the _Subsurface_ mail list: "
"_subsurface@subsurface-divelog.org_ with a request for the files to be "
"analysed. Provide the dive computer make and model as well as contextual "
"information about the dives recorded on the dive computer."
msgstr ""

#. type: Title ====
#: ./user-manual.txt:487
#, 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
#, no-wrap
msgid "images/icons/bluetooth.jpg"
msgstr ""

#. type: Plain text
#: ./user-manual.txt:495
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 "
"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_."
msgstr ""

#. type: Plain text
#: ./user-manual.txt:498
msgid "Ensure that _Subsurface_ sees the Bluetooth adapter on the host computer."
msgstr ""

#. type: Plain text
#: ./user-manual.txt:499
msgid ""
"Ensure 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."
msgstr ""

#. type: Plain text
#: ./user-manual.txt:504
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."
msgstr ""

#. type: Title =====
#: ./user-manual.txt:505
#, no-wrap
msgid "On Linux or MacOS:"
msgstr ""

#. type: Target for macro image
#: ./user-manual.txt:507
#, no-wrap
msgid "images/DC_import_Bluetooth.jpg"
msgstr ""

#. type: Plain text
#: ./user-manual.txt:515
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 "
"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."
msgstr ""

#. type: delimited block *
#: ./user-manual.txt:547
msgid ""
"Currently _Subsurface_ 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."
msgstr ""

#. type: delimited block *
#: ./user-manual.txt:549
msgid "One way to achieve this is to use +bluetoothctl+:"
msgstr ""

#. type: delimited block *
#: ./user-manual.txt:560
#, no-wrap
msgid ""
"\t$ bluetoothctl\n"
"\t[bluetooth]# agent KeyboardOnly\n"
"\tAgent registered\n"
"\t[bluetooth]# default-agent\n"
"\tDefault agent request successful\n"
"\t[bluetooth]# pair 00:80:25:49:6C:E3\n"
"\tAttempting to pair with 00:80:25:49:6C:E3\n"
"\t[CHG] Device 00:80:25:49:6C:E3 Connected: yes\n"
"\tRequest PIN code\n"
"\t[agent] Enter PIN code: 0000\n"
msgstr ""

#. type: Plain text
#: ./user-manual.txt:566
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."
msgstr ""

#. type: Title ====
#: ./user-manual.txt:567 ./user-manual.txt:3537 ./user-manual.txt:3621
#, no-wrap
msgid "On Windows:"
msgstr ""

#. type: Target for macro image
#: ./user-manual.txt:568
#, no-wrap
msgid "images/DC_import_Bluetooth_Windows.png"
msgstr ""

#. type: Plain text
#: ./user-manual.txt:578
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."
msgstr ""

#. type: Plain text
#: ./user-manual.txt:585
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."
msgstr ""

#. type: Plain text
#: ./user-manual.txt:593
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."
msgstr ""

#. type: Plain text
#: ./user-manual.txt:598
msgid ""
"A log messageOn 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 "
"mode\"_ option."
msgstr ""

#. type: Plain text
#: ./user-manual.txt:608
#, no-wrap
msgid ""
"*IN CASE OF PROBLEMS*:  If the Bluetooth adapter from the _Subsurface_ "
"computer\n"
"gets stuck and the _Download_ process fails repeatedly,\n"
" _unpair_ the devices and then repeat the above steps. If this is not "
"successful,\n"
" xref:S_HowFindBluetoothDeviceName[_Appendix A_] contains\n"
"information for manually setting up and inspecting the Bluetooth "
"connection\n"
"with _Subsurface_.\n"
msgstr ""

#. type: Title ====
#: ./user-manual.txt:611
#, no-wrap
msgid "Changing the name of a dive computer"
msgstr ""

#. type: Plain text
#: ./user-manual.txt:627
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."
msgstr ""

#. type: Title ====
#: ./user-manual.txt:629
#, no-wrap
msgid "Updating the dive information imported from the dive computer."
msgstr ""

#. type: Plain text
#: ./user-manual.txt:636
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."
msgstr ""

#. type: Title =====
#: ./user-manual.txt:638
#, no-wrap
msgid "Notes"
msgstr ""

#. type: Plain text
#: ./user-manual.txt:643
msgid ""
"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
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):"
msgstr ""

#. type: Target for macro image
#: ./user-manual.txt:654
#, no-wrap
msgid "images/AddDive3_f22.jpg"
msgstr ""

#. type: Plain text
#: ./user-manual.txt:663
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 "
"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
#, 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"
"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"
"be used).\n"
msgstr ""

#. type: Plain text
#: ./user-manual.txt:676
#, no-wrap
msgid "*Location*:\n"
msgstr ""

#. type: Plain text
#: ./user-manual.txt:684
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 "
"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."
msgstr ""

#. type: Plain text
#: ./user-manual.txt:702
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):"
msgstr ""

#. type: Target for macro image
#: ./user-manual.txt:703
#, no-wrap
msgid "images/Locations1_f22.jpg"
msgstr ""

#. type: Plain text
#: ./user-manual.txt:708
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:"
msgstr ""

#. type: Plain text
#: ./user-manual.txt:715
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."
msgstr ""

#. type: Plain text
#: ./user-manual.txt:720
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]"
msgstr ""

#. type: Plain text
#: ./user-manual.txt:723
msgid ""
"The coordinates can be entered by hand if they are known, using one of four "
"formats with latitude followed by longitude:"
msgstr ""

#. type: Plain text
#: ./user-manual.txt:728
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. N30° 13' 29.8\" , E30° 49' 1.5\" Decimal degrees, e.g. 30.22496 , "
"30.821798"
msgstr ""

#. type: Plain text
#: ./user-manual.txt:736
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 "
"dive site information by selecting the button _Apply changes_ at the top of "
"the panel."
msgstr ""

#. type: Plain text
#: ./user-manual.txt:742
#, 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"
"dives have the same location and try to keep their GPS coordinates the\n"
"same).\n"
msgstr ""

#. type: Plain text
#: ./user-manual.txt:752
#, 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"
"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"
msgstr ""

#. type: Plain text
#: ./user-manual.txt:757
msgid ""
"Enter any other textual 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*."
msgstr ""

#. type: Plain text
#: ./user-manual.txt:762
#, 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"
"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
#, no-wrap
msgid ""
"*Divemaster*: The name of the dive master or dive guide for this dive should "
"be\n"
"entered in this field\n"
"which offers auto selection based on the list of dive masters in\n"
"the current logbook.\n"
msgstr ""

#. type: Plain text
#: ./user-manual.txt:772
#, no-wrap
msgid ""
"*Buddy*: In this field, one enters the name(s) of the buddy / buddies\n"
"(separated with commas) who accompanied him/her on the\n"
"dive. Auto selection based on the list of buddies in the current logbook "
"is\n"
"offered.\n"
msgstr ""

#. type: Plain text
#: ./user-manual.txt:777
#, 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"
msgstr ""

#. type: Plain text
#: ./user-manual.txt:780
#, no-wrap
msgid ""
"*Rating*: One can provide a subjective overall rating of the dive on a\n"
"5-point scale by clicking the appropriate star on the rating scale.\n"
msgstr ""

#. type: Plain text
#: ./user-manual.txt:784
#, no-wrap
msgid ""
"*Visibility*: Similarly, one can provide a rating of visibility during the\n"
"dive on a\n"
"5-point scale by clicking the appropriate star.\n"
msgstr ""

#. type: Plain text
#: ./user-manual.txt:793
#, no-wrap
msgid ""
"*Tags*: Tags that describe the type of dive performed can be entered\n"
"here (separated by commas). Examples of common tags are boat, drift, "
"training,\n"
"cave, etc.\n"
"_Subsurface_ has many built-in tags. If the user starts typing a tag, the\n"
"program\n"
"will list the tags that correspond to the typing. For instance, if the "
"user\n"
"typed\n"
"+cav+, then the tags *cave* and *cavern* are shown for the user to choose "
"from.\n"
msgstr ""

#. type: Plain text
#: ./user-manual.txt:795
#, no-wrap
msgid "*Notes*: Any additional information for the dive can be entered here.\n"
msgstr ""

#. type: Plain text
#: ./user-manual.txt:800
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."
msgstr ""

#. type: Title =====
#: ./user-manual.txt:801
#, no-wrap
msgid "Equipment"
msgstr ""

#. type: Plain text
#: ./user-manual.txt:806
msgid ""
"The Equipment tab allows one to enter information about the type of cylinder "
"and gas used as well as the weights used for the dive. The message in a blue "
"box at the top of the panel:"
msgstr ""

#. type: Plain text
#: ./user-manual.txt:813
msgid ""
"indicates that the dive is being edited. This is a highly interactive part "
"of _Subsurface_ and the information on cylinders and gases (entered here) "
"determines the behaviour of the *Dive profile* (top right-hand panel)."
msgstr ""

#. type: Plain text
#: ./user-manual.txt:817
#, no-wrap
msgid ""
"*Cylinders*: The cylinder information is entered through a dialogue that "
"looks\n"
"like this:\n"
msgstr ""

#. type: Target for macro image
#: ./user-manual.txt:818
#, no-wrap
msgid "images/DC_gas-dialogue1_f20.jpg"
msgstr ""

#. type: Plain text
#: ./user-manual.txt:827
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:"
msgstr ""

#. type: Target for macro image
#: ./user-manual.txt:833
#, no-wrap
msgid "images/DC_gas-dialogue2_f20.jpg"
msgstr ""

#. type: Plain text
#: ./user-manual.txt:840
msgid ""
"The drop-down list can then be used to select the cylinder type that was "
"used for this dive or the user may start typing in the box which shows the "
"available options for the entered characters. The *Size* of the cylinder as "
"well as its working pressure (_Work.press_) will automatically be shown in "
"the dialogue."
msgstr ""

#. type: Plain text
#: ./user-manual.txt:844
msgid ""
"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 _Preferences_."
msgstr ""

#. type: Plain text
#: ./user-manual.txt:855
msgid ""
"Finally, provide the gas mixture used. If air was used, the value of 21% can "
"be entered or this field can be left blank. If nitrox or trimix were used, "
"their percentages of oxygen and/or helium should be entered.  Any "
"inappropriate fields should be left empty. After typing the information for "
"the cylinder, 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):"
msgstr ""

#. type: Target for macro image
#: ./user-manual.txt:856
#, no-wrap
msgid "images/CylinderDataEntry3_f20.jpg"
msgstr ""

#. type: Plain text
#: ./user-manual.txt:863
#, no-wrap
msgid ""
"*Weights*: Information about the weight system used can be entered\n"
"using a dialogue very similar to that of the cylinder information. If one\n"
"clicks\n"
"the + button on the top right of the weights dialogue, the table looks "
"like\n"
"this:\n"
msgstr ""

#. type: Target for macro image
#: ./user-manual.txt:864
#, no-wrap
msgid "images/WeightsDataEntry1_f20.jpg"
msgstr ""

#. type: Plain text
#: ./user-manual.txt:868
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
#, no-wrap
msgid "images/WeightsDataEntry2_f20.jpg"
msgstr ""

#. type: Plain text
#: ./user-manual.txt:883
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:"
msgstr ""

#. type: Target for macro image
#: ./user-manual.txt:884
#, no-wrap
msgid "images/WeightsDataEntry3_f20.jpg"
msgstr ""

#. type: Title ====
#: ./user-manual.txt:886
#, no-wrap
msgid "Editing several selected dives simultaneously"
msgstr ""

#. type: Plain text
#: ./user-manual.txt:901
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."
msgstr ""

#. type: Plain text
#: ./user-manual.txt:911
msgid ""
"The simultaneous editing only works with fields that do not already contain "
"information.  This means that, if some fields have been edited for a "
"particular dive among the selected dives, these are not changed while "
"editing the dives simultaneously. Technically, the rule for editing several "
"dives simultaneously is: if the data field being edited contains _exactly "
"the same information_ for all the dives that have been selected, the new, "
"edited information is substituted for all the selected dives, otherwise only "
"the edited dive is changed, even though several dives have been selected in "
"the *Dive List*. This greatly speeds up the completion of the dive log after "
"several similar dives."
msgstr ""

#. type: Plain text
#: ./user-manual.txt:920
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 "
"*Equipment* tabs. Then, from the main menu, select _Log -> Copy dive "
"components_.  A box is presented with a selection of check boxes for most of "
"the fields in the *Notes* and *Equipment* tabs.  Select the fields to be "
"copied from the currently selected dive, then select _OK_. Now, in the *Dive "
"List*, select the dives into which this information is to be pasted. Then, "
"from the main menu, select _Log -> Paste dive components_.  All the selected "
"dives now contain the data initially selected in the original source dive "
"log."
msgstr ""

#. type: Title ====
#: ./user-manual.txt:921
#, no-wrap
msgid "Adding Bookmarks to a dive"
msgstr ""

#. type: Plain text
#: ./user-manual.txt:926
msgid ""
"Many divers wish to annotate their dives with text that indicate particular "
"events during the dive, e.g. \"Saw dolphins\", or \"Released surface "
"buoy\". This is easily done:"
msgstr ""

#. type: Plain text
#: ./user-manual.txt:930
msgid ""
"Right-click at the appropriate point on the dive profile.  This brings up "
"the dive profile context menu. Select _Add bookmark_. A red flag is placed "
"on the dive profile at the point that was initially selected (see *A* "
"below)."
msgstr ""

#. type: Plain text
#: ./user-manual.txt:932
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
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
msgid ""
"If one hovers using the mouse over the red bookmark, the appropriate text is "
"shown at the bottom of the information box (see *D* below)."
msgstr ""

#. type: Target for macro image
#: ./user-manual.txt:939
#, no-wrap
msgid "images/Bookmarks.jpg"
msgstr ""

#. type: Title ====
#: ./user-manual.txt:942
#, no-wrap
msgid "Saving the updated dive information"
msgstr ""

#. type: Plain text
#: ./user-manual.txt:953
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 "
"computer disk."
msgstr ""

#. type: Title ===
#: ./user-manual.txt:954
#, no-wrap
msgid ""
"Importing dive information from other digital data sources or other data "
"formats"
msgstr ""

#. type: Plain text
#: ./user-manual.txt:980
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_."
msgstr ""

#. type: Title ====
#: ./user-manual.txt:991
#, no-wrap
msgid "Using the universal import dialogue"
msgstr ""

#. type: Plain text
#: ./user-manual.txt:997
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."
msgstr ""

#. type: Target for macro image
#: ./user-manual.txt:998
#, no-wrap
msgid "images/Import1_f20.jpg"
msgstr ""

#. type: Plain text
#: ./user-manual.txt:1003
msgid ""
"Towards the bottom right is a dropdown selector with a default label of "
"_Dive Log Files_ which gives access to the different types of direct imports "
"available, as in dialogue *B*, above. Currently these are:"
msgstr ""

#. type: Plain text
#: ./user-manual.txt:1005
msgid ""
"XML-formatted dive logs (DivingLog 5.0, MacDive and several other dive log "
"systems)"
msgstr ""

#. type: Plain text
#: ./user-manual.txt:1006
msgid "Cochran dive logs"
msgstr ""

#. type: Plain text
#: ./user-manual.txt:1007
msgid "UDDF-formatted dive logs (e.g. Kenozoooid)"
msgstr ""

#. type: Plain text
#: ./user-manual.txt:1008
msgid "UDCF-formatted dive logs"
msgstr ""

#. type: Plain text
#: ./user-manual.txt:1009
msgid "Poseidon MkVI CCR logs"
msgstr ""

#. type: Plain text
#: ./user-manual.txt:1010
msgid "APD Inspiration/Evolution CCR logs"
msgstr ""

#. type: Plain text
#: ./user-manual.txt:1011
msgid "LiquiVision logs"
msgstr ""

#. type: Plain text
#: ./user-manual.txt:1012
msgid "divelog.de logs"
msgstr ""

#. type: Plain text
#: ./user-manual.txt:1013
msgid "OSTC Tools logs"
msgstr ""

#. type: Plain text
#: ./user-manual.txt:1014
msgid "JDiveLog"
msgstr ""

#. type: Plain text
#: ./user-manual.txt:1015
msgid "Suunto Dive Manager (DM3 and DM4)"
msgstr ""

#. type: Plain text
#: ./user-manual.txt:1016
msgid "CSV (text-based and spreadsheet-based) dive logs, including APD CCR logs"
msgstr ""

#. type: Plain text
#: ./user-manual.txt:1021
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 "
"accessible through the Import dialogue are also supported, as explained "
"below."
msgstr ""

#. type: Title ====
#: ./user-manual.txt:1022
#, no-wrap
msgid "Importing from  OSTCTools"
msgstr ""

#. type: Plain text
#: ./user-manual.txt:1031
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 "
"data from the dive computer and stores it as a binary file with file "
"extension _.dive_ . Subsurface can directly import these files when using "
"the universal import dialogue. From the dropdown list at the bottom right "
"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."
msgstr ""

#. type: Plain text
#: ./user-manual.txt:1035
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."
msgstr ""

#. type: Plain text
#: ./user-manual.txt:1040
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)."
msgstr ""

#. type: Title ====
#: ./user-manual.txt:1042
#, no-wrap
msgid "Importing from Mares Dive Organiser V2.1"
msgstr ""

#. type: Plain text
#: ./user-manual.txt:1049
msgid ""
"Since Mares utilise proprietary Windows software not compatible with "
"multi-platform applications, these dive logs cannot be directly imported "
"into _Subsurface_. Mares dive logs need to be imported using a three-step "
"process, using _www.divelogs.de_ as a mechanism to extract the dive log "
"information."
msgstr ""

#. type: Plain text
#: ./user-manual.txt:1054
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."
msgstr ""

#. type: Plain text
#: ./user-manual.txt:1060
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_."
msgstr ""

#. type: Plain text
#: ./user-manual.txt:1062
msgid ""
"Finally, import the dives from _divelogs.de_ to _Subsurface_, using the "
"instructions below."
msgstr ""

#. type: Title ====
#: ./user-manual.txt:1065
#, no-wrap
msgid "Importing dives from *divelogs.de*"
msgstr ""

#. type: Plain text
#: ./user-manual.txt:1078
msgid ""
"The import of 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."
msgstr ""

#. type: Target for macro image
#: ./user-manual.txt:1079
#, no-wrap
msgid "images/Divelogs1.jpg"
msgstr ""

#. type: Title ====
#: ./user-manual.txt:1082
#, no-wrap
msgid "Importing data in CSV format"
msgstr ""

#. type: Plain text
#: ./user-manual.txt:1093
msgid ""
"A comma-separated file (.csv) can be used to import dive information either "
"as dive profiles (as in the case of the APD Inspiration and Evolution closed "
"circuit rebreathers) or as dive metadata (in case the user keeps dive data "
"in a spreadsheet). The _CSV_ 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 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:S_Appendix_D[APPENDIX D: Exporting a spreadsheet to CSV format] for "
"information that may be helpful for importing spreadsheet-based data into "
"_Subsurface_."
msgstr ""

#. type: Title =====
#: ./user-manual.txt:1095
#, no-wrap
msgid "Importing dives in CSV format from dive computers or other dive log software"
msgstr ""

#. type: Plain text
#: ./user-manual.txt:1100
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 "
"_column headings_) of the data columns, followed by the data, one record per "
"line."
msgstr ""

#. type: Plain text
#: ./user-manual.txt:1102
msgid ""
"There are two types of _CSV_ dive logs that can be imported into "
"_Subsurface_:"
msgstr ""

#. type: Plain text
#: ./user-manual.txt:1108
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."
msgstr ""

#. type: Plain text
#: ./user-manual.txt:1117
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."
msgstr ""

#. type: Plain text
#: ./user-manual.txt:1120
msgid ""
"Before being able to import the _CSV_ data to _Subsurface_ *one needs to "
"know a few things about the data being imported*:"
msgstr ""

#. type: Plain text
#: ./user-manual.txt:1128
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 "
"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)."
msgstr ""

#. type: Plain text
#: ./user-manual.txt:1132
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 "
"editor and note the titles of the columns to be imported and their column "
"positions."
msgstr ""

#. type: Plain text
#: ./user-manual.txt:1134
msgid "Is the numeric information (e.g. dive depth) in metric or in imperial units?"
msgstr ""

#. type: Plain text
#: ./user-manual.txt:1141
msgid ""
"Armed with this information, importing the data into _Subsurface_ is "
"straightforward. Select _Import -> Import Log Files_ from the main menu. In "
"the resulting file selection menu, select _CSV files_ (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:"
msgstr ""

#. type: Target for macro image
#: ./user-manual.txt:1142
#, no-wrap
msgid "images/csv_import1_f20.jpg"
msgstr ""

#. type: Plain text
#: ./user-manual.txt:1153
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."
msgstr ""

#. type: Plain text
#: ./user-manual.txt:1165
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."
msgstr ""

#. type: Target for macro image
#: ./user-manual.txt:1166
#, no-wrap
msgid "images/csv_import2_f20.jpg"
msgstr ""

#. type: Plain text
#: ./user-manual.txt:1172
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."
msgstr ""

#. type: delimited block *
#: ./user-manual.txt:1176
#, no-wrap
msgid "*A Diver's Introduction to _CSV_ Files*\n"
msgstr ""

#. type: delimited block *
#: ./user-manual.txt:1190
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."
msgstr ""

#. type: delimited block *
#: ./user-manual.txt:1199
msgid ""
"_CSV_ files can be created or edited with a normal text editor. The most "
"important attribute of a _CSV_ file is the _field separator_, the character "
"used to separate fields within a single line. The field separator is "
"frequently a comma, a colon, a SPACE character or a TAB character. When "
"exporting data from spreadsheet software, the field separator needs to be "
"specified in order to create the _CSV_ file. _CSV_ files are normally "
"organised into a single line that provides the headers (or _field names_) of "
"the data columns, followed by the data, one record per line. Note that each "
"field name may comprise more than one word separated by spaces; for instance "
"_Dive site_, below. Here is an example of dive information for four dives "
"using a comma as a field separator:"
msgstr ""

#. type: delimited block *
#: ./user-manual.txt:1205
#, no-wrap
msgid ""
"\tDive site,Dive date,Time,Dive_duration, Dive_depth,Dive buddy\n"
"\tIllovo Beach,2012-11-23,10:45,46:15,18.4,John Smith\n"
"\tKey Largo,2012-11-24,09:12,34:15,20.4,Jason McDonald\n"
"\tWismar Baltic,2012-12-01,10:13,35:27,15.4,Dieter Albrecht\n"
"\tPulau Weh,2012-12-20,09:46,55:56,38.6,Karaeng Bontonompo\n"
msgstr ""

#. type: delimited block *
#: ./user-manual.txt:1207
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
#, no-wrap
msgid ""
"\tDive site\tDive date\tTime\tDive_duration\tDive_depth\tDive buddy\n"
"\tIllovo Beach\t2012-11-23\t10:45\t46:15\t18.4\tJohn Smith\n"
"\tKey Largo\t2012-11-24\t09:12\t34:15\t20.4\tJason McDonald\n"
"\tWismar Baltic\t2012-12-01\t10:13\t35:27\t15.4\tDieter Albrecht\n"
"\tPulau Weh\t2012-12-20\t09:46\t55:56\t38.6\tKaraeng Bontonompo\n"
msgstr ""

#. type: delimited block *
#: ./user-manual.txt:1221
msgid ""
"It is clear why many people prefer the TAB-delimited format to the "
"comma-delimited format. The disadvantage is that one cannot see the TAB "
"characters. For instance, the space between _Dive_ and _date_ in the top "
"line may be a SPACE character or a TAB character (in this case it is a SPACE "
"character: the tabs are before and after _Dive date_). If the field names in "
"the first line are long, the alignment with data in the other lines cannot "
"be maintained. Here is a highly simplified and shortened TAB-delimited "
"example of a _CSV_ dive log from an APD closed-circuit rebreather (CCR) dive "
"computer:"
msgstr ""

#. type: delimited block *
#: ./user-manual.txt:1232
#, no-wrap
msgid ""
"\tDive Time (s)\tDepth (m)\tpO₂ - Setpoint (Bar) \tpO₂ - C1 Cell 1 "
"(Bar)\tAmbient temp. (Celsius)\n"
"\t0       0.0     0.70    0.81    13.1\n"
"\t0       1.2     0.70    0.71    13.1\n"
"\t0       0.0     0.70    0.71    13.1\n"
"\t0       1.2     0.70    0.71    13.2\n"
"\t0       1.2     0.70    0.71    13.1\n"
"\t10      1.6     0.70    0.72    12.7\n"
"\t20      1.6     0.70    0.71    12.6\n"
"\t30      1.7     0.70    0.71    12.6\n"
"\t40      1.8     0.70    0.68    12.5\n"
msgstr ""

#. type: delimited block *
#: ./user-manual.txt:1238
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_."
msgstr ""

#. type: Plain text
#: ./user-manual.txt:1252
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 "
"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
#, no-wrap
msgid ""
"Importing GPS coordinates with the _Subsurface Companion App_ for mobile "
"phones"
msgstr ""

#. type: Plain text
#: ./user-manual.txt:1264
#, 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:"
msgstr ""

#. type: Title ====
#: ./user-manual.txt:1267
#, no-wrap
msgid "Create a Companion App account"
msgstr ""

#. type: Plain text
#: ./user-manual.txt:1272
msgid ""
"Register on the http://api.hohndel.org/login/[_Subsurface companion web "
"page_].  A confirmation email with instructions and a personal *DIVERID* "
"will be sent, a long number that gives access to the file server and "
"Companion App capabilities."
msgstr ""

#. type: Plain text
#: ./user-manual.txt:1277
msgid ""
"Download the app from "
"https://play.google.com/store/apps/details?id=org.subsurface[Google Play "
"Store] or from "
"http://f-droid.org/repository/browse/?fdfilter=subsurface&fdid=org.subsurface[F-Droid]."
msgstr ""

#. type: Title ====
#: ./user-manual.txt:1278
#, no-wrap
msgid "Using the Subsurface companion app on an Android smartphone"
msgstr ""

#. type: Plain text
#: ./user-manual.txt:1281
msgid "On first use the app has three options:"
msgstr ""

#. type: Plain text
#: ./user-manual.txt:1287
msgid ""
"_Create a new account._ Equivalent to registering in _Subsurface_ companion "
"page using an Internet browser. One can request a *DIVERID* using this "
"option, but this is supplied via email and followed up by interaction with "
"the http://api.hohndel.org/login/[_Subsurface companion web page_] in order "
"to activate the account."
msgstr ""

#. type: Plain text
#: ./user-manual.txt:1290
msgid ""
"_Retrieve an account._ If users forgot their *DIVERID* they will receive an "
"email to recover the number."
msgstr ""

#. type: Plain text
#: ./user-manual.txt:1294
msgid ""
"_Use an existing account._ Users are prompted for their *DIVERID*. The app "
"saves this *DIVERID* and does not ask for it again unless one uses the "
"_Disconnect_ menu option (see below)."
msgstr ""

#. type: Plain text
#: ./user-manual.txt:1302
msgid ""
"In the _Subsurface_ main program, the *DIVERID* should also be entered on "
"the Default Preferences panel, obtained by selecting _File -> Preferences -> "
"Defaults_ from the main menu in _Subsurface_ itself.  This facilitates "
"synchronisation between _Subsurface_ and the Companion App."
msgstr ""

#. type: Title =====
#: ./user-manual.txt:1303
#, no-wrap
msgid "Creating new dive locations"
msgstr ""

#. type: Plain text
#: ./user-manual.txt:1308
msgid ""
"Now one is ready to get a dive position and send it to the server. The "
"Android display will look like the left hand image (*A*) below, but without "
"any dives."
msgstr ""

#. type: Plain text
#: ./user-manual.txt:1311
msgid ""
"Touch the \"+\" icon on the top right to add a new dive site, a menu will be "
"showed with 3 options:"
msgstr ""

#. type: Plain text
#: ./user-manual.txt:1314
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
msgid ""
"Use Map: This option allows the user to fix a position by searching a world "
"map. A world map is shown (see *B* below) on which one should indicate the "
"desired position with a _long press_ on the touch sensitive screen (if the "
"marked location is erroneous, simply indicate a new location)  and select "
"the check symbol in the upper right. A dialog is shown allowing to enter the "
"name of the dive location and the date-time of the dive (see *C* below). In "
"order to import this dive location in _Subsurface_ it's advisable to set the "
"time to agree with the time of that dive on the dive computer."
msgstr ""

#. type: Target for macro image
#: ./user-manual.txt:1324
#, no-wrap
msgid "images/Companion_5.jpg"
msgstr ""

#. type: Plain text
#: ./user-manual.txt:1332
msgid ""
"Import local GPX file: The android device searches for .gpx files and "
"located archives will be shown. The selected .gpx file is opened and the "
"stored locations shown. Now one needs to select the appropriate locations, "
"then select the tab in the upper right, after which the locations will be "
"sent to the web service and added to the list on the Android device."
msgstr ""

#. type: Title =====
#: ./user-manual.txt:1333
#, no-wrap
msgid "Dive lists of dive locations"
msgstr ""

#. type: Plain text
#: ./user-manual.txt:1341
msgid ""
"The main screen shows a list of dive locations, each with a name, date and "
"time (see *A* below). Some locations may have an arrow-up icon over the "
"selection box to the left indicating that they require upload to the "
"server. One can select individual dive locations from the list. A selected "
"location has a check mark in the selection box on the left. Group operations "
"(such as _Delete_ or _Send_)  are performed on several locations that are "
"selected."
msgstr ""

#. type: Plain text
#: ./user-manual.txt:1349
msgid ""
"Dive locations in this list can be viewed in two ways: a list of locations "
"or a map indicating the dive locations. The display mode (List or Map) is "
"changed by selecting _Dives_ at the top left of the screen (see *A* below) "
"and then selecting the display mode. The display mode can be changed either "
"from the list of locations or from the map (see *B* below). If one selects a "
"location (on the list or on the map), an editing panel opens (see *C* below) "
"where the dive description or other details may be changed."
msgstr ""

#. type: Target for macro image
#: ./user-manual.txt:1350
#, no-wrap
msgid "images/Companion_4.jpg"
msgstr ""

#. type: Plain text
#: ./user-manual.txt:1356
msgid ""
"When one selects 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
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
msgid ""
"After editing and saving a dive location (see *C* above), one needs to "
"upload it to the web service, as explained below."
msgstr ""

#. type: Title =====
#: ./user-manual.txt:1364
#, no-wrap
msgid "Uploading dive locations"
msgstr ""

#. type: Plain text
#: ./user-manual.txt:1370
msgid ""
"There are several ways to send locations to the server.  The easiest is by "
"simply selecting the locations (See *A* below) and then touching the right "
"arrow at the top right of the screen."
msgstr ""

#. type: Plain text
#: ./user-manual.txt:1375
msgid ""
"Users must be careful, as the trash icon on the right means exactly what it "
"should; it deletes the selected dive location(s)."
msgstr ""

#. type: Target for macro image
#: ./user-manual.txt:1376
#, no-wrap
msgid "images/Companion_1.jpg"
msgstr ""

#. type: Plain text
#: ./user-manual.txt:1381
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
#, no-wrap
msgid "Settings on the Companion App"
msgstr ""

#. type: Plain text
#: ./user-manual.txt:1386
msgid ""
"Selecting the _Settings_ menu option results in the right hand image above "
"(*B*)."
msgstr ""

#. type: Title =====
#: ./user-manual.txt:1387
#, no-wrap
msgid "Server and account"
msgstr ""

#. type: Plain text
#: ./user-manual.txt:1390
msgid "_Web-service URL._ This is predefined (http://api.hohndel.org/)"
msgstr ""

#. type: Plain text
#: ./user-manual.txt:1394
msgid ""
"_User ID._ The DIVERID obtained by registering as described above. The "
"easiest way to obtain it is simply to copy and paste from the confirmation "
"email but, of course, users can also type this information."
msgstr ""

#. type: Title =====
#: ./user-manual.txt:1395
#, no-wrap
msgid "Synchronisation"
msgstr ""

#. type: Plain text
#: ./user-manual.txt:1399
msgid ""
"_Synchronize on startup_. If selected, dive locations in the Android device "
"and those on the web service synchronise each time the app is started."
msgstr ""

#. type: Plain text
#: ./user-manual.txt:1402
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
#, no-wrap
msgid "Background service"
msgstr ""

#. type: Plain text
#: ./user-manual.txt:1406
msgid ""
"Instead of entering a unique dive location, users can leave the service "
"running in the background of their Android device, allowing the continuous "
"collection of GPS locations."
msgstr ""

#. type: Plain text
#: ./user-manual.txt:1409
msgid "The settings below define the behaviour of the service:"
msgstr ""

#. type: Plain text
#: ./user-manual.txt:1412
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
msgid "_Min distance._ In meters. Minimum distance between two locations."
msgstr ""

#. type: Plain text
#: ./user-manual.txt:1416
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
#, no-wrap
msgid "images/icons/info.jpg"
msgstr ""

#. type: Plain text
#: ./user-manual.txt:1427
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."
msgstr ""

#. type: Title =====
#: ./user-manual.txt:1428
#, no-wrap
msgid "Other"
msgstr ""

#. type: Plain text
#: ./user-manual.txt:1432
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
msgid "_Subsurface website._ A link to the URL of Subsurface web"
msgstr ""

#. type: Plain text
#: ./user-manual.txt:1436
msgid "_Version._ Displays the current version of the Companion App."
msgstr ""

#. type: Title =====
#: ./user-manual.txt:1437
#, no-wrap
msgid "Search"
msgstr ""

#. type: Plain text
#: ./user-manual.txt:1440
msgid "Search the saved dive locations by name or by date and time."
msgstr ""

#. type: Title =====
#: ./user-manual.txt:1441
#, no-wrap
msgid "Start service"
msgstr ""

#. type: Plain text
#: ./user-manual.txt:1444
msgid ""
"Initiates the _background service_ following the previously defined "
"settings."
msgstr ""

#. type: Title =====
#: ./user-manual.txt:1445
#, no-wrap
msgid "Disconnect"
msgstr ""

#. type: Plain text
#: ./user-manual.txt:1453
msgid ""
"This is a badly named option that disconnects the app from the server by "
"resetting the user ID in the app, showing the first screen where an account "
"can be created, retrieve the ID for an existing account or use the users own "
"ID. The disconnect option is useful if a user's Android device was used to "
"download the dive locations of another registered diver."
msgstr ""

#. type: Title =====
#: ./user-manual.txt:1454
#, no-wrap
msgid "Send all locations"
msgstr ""

#. type: Plain text
#: ./user-manual.txt:1457
msgid "This option sends all locations stored in the Android device to the server."
msgstr ""

#. type: Title ====
#: ./user-manual.txt:1459
#, no-wrap
msgid "Using the Subsurface companion app on an _iPhone_ to record dive locations"
msgstr ""

#. type: Plain text
#: ./user-manual.txt:1464
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."
msgstr ""

#. type: Target for macro image
#: ./user-manual.txt:1465
#, no-wrap
msgid "images/iphone.jpg"
msgstr ""

#. type: Plain text
#: ./user-manual.txt:1472
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."
msgstr ""

#. type: Plain text
#: ./user-manual.txt:1478
msgid ""
"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."
msgstr ""

#. type: Title ====
#: ./user-manual.txt:1480
#, no-wrap
msgid "Downloading dive locations to the _Subsurface_ divelog"
msgstr ""

#. type: Plain text
#: ./user-manual.txt:1489
msgid ""
"Download dive(s) from a dive computer or enter them manually into "
"_Subsurface_ before obtaining the GPS coordinates from the server. The "
"download dialog can be reached via _Ctrl+G_ or from the _Subsurface_ Main "
"Menu _Import -> Import GPS data from Subsurface Service_, resulting in the "
"image on the left (*A*), below. On first use the DIVERID text box is "
"blank. Provide a DIVERID, then select the _Download_ button to initiate the "
"download process, after which the screen on the right (*B*) below appears:"
msgstr ""

#. type: Target for macro image
#: ./user-manual.txt:1490
#, no-wrap
msgid "images/DownloadGPS.jpg"
msgstr ""

#. type: Plain text
#: ./user-manual.txt:1498
msgid ""
"Note that the _Apply_ button is now active. By clicking on it, users can "
"update the locations of the newly entered or uploaded dives in _Subsurface_ "
"which applies the coordinates and names entered on the app for all the new "
"dives that match the date-times of the uploaded GPS localities. If one has "
"entered the name of the dive location in _Subsurface_ before downloading the "
"GPS coordinates, this name will take precedence over downloaded one."
msgstr ""

#. type: Plain text
#: ./user-manual.txt:1505
msgid ""
"Since _Subsurface_ matches GPS locations from the Android device and dive "
"information from the dive computer based on date-time data, automatic "
"assignment of GPS data to dives is dependent on agreement of the date-time "
"information between these two devices. Although _Subsurface_ has a wide "
"range tolerance, it may be unable to identify the appropriate dive if there "
"is a large difference between the time in the dive computer and that of the "
"Android device, resulting in no updates."
msgstr ""

#. type: Plain text
#: ./user-manual.txt:1513
msgid ""
"Similar date-times may not always be possible and there may be many reasons "
"for this (e.g. time zones), or _Subsurface_ may be unable to decide which is "
"the correct position for a dive (e.g. on repetitive dives while running "
"_background service_ there may be several locations that would be included "
"in the time range that fit not only the first dive, but one or more "
"subsequent dives as well).  A workaround for this situation to manually edit "
"the date-time of a dive in the _Subsurface_ Dive List *before* downloading "
"the GPS data and then to change the date-time back again *after* downloading "
"GPS data."
msgstr ""

#. type: Plain text
#: ./user-manual.txt:1517
msgid "TIPS:"
msgstr ""

#. type: Plain text
#: ./user-manual.txt:1524
msgid ""
"_Background service_, being a very powerful tool, may fill the location list "
"with many unnecessary locations not corresponding to the exact dive point "
"but reflecting the boat's route.  Currently these locations are difficult to "
"delete from the server. In some situations it is therefore prudent to clean "
"up the list on the Android device before sending the dive points to the web "
"server by simply deleting the inappropriate locations. This might be "
"necessary, for instance, if one wants to keep the location list clear to see "
"dives in the web service map display (see above)."
msgstr ""

#. type: Plain text
#: ./user-manual.txt:1528
msgid ""
"It may also make sense to give informative names to the locations sent to "
"the web server, or at least to use an informative name in the _Name "
"Template_ setting while running the _background service_, especially on a "
"dive trip with many dives and dive locations."
msgstr ""

#. type: Title ===
#: ./user-manual.txt:1530
#, no-wrap
msgid "Adding photographs to dives"
msgstr ""

#. type: Plain text
#: ./user-manual.txt:1536
msgid ""
"Many (if not most) divers take a camera with them and take photographs "
"during a dive. One would like to associate each photograph with a specific "
"dive. _Subsurface_ allows one to load photos into a dive. Photos are "
"superimposed on the dive profile, from where they can be viewed."
msgstr ""

#. type: Title ====
#: ./user-manual.txt:1537
#, no-wrap
msgid "Loading photos and getting synchronisation between dive computer and camera"
msgstr ""

#. type: Plain text
#: ./user-manual.txt:1541
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
#, no-wrap
msgid "images/LoadImage1_f20.jpg"
msgstr ""

#. type: Plain text
#: ./user-manual.txt:1546
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
#, no-wrap
msgid "images/LoadImage2_f20.jpg"
msgstr ""

#. type: Plain text
#: ./user-manual.txt:1556
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."
msgstr ""

#. type: Plain text
#: ./user-manual.txt:1558
msgid "_Subsurface_ achieves this synchronisation in three ways:"
msgstr ""

#. type: Plain text
#: ./user-manual.txt:1561
#, no-wrap
msgid ""
"*Pro-actively*: Before the dive, ensure synchronisation 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
#, no-wrap
msgid ""
"*Manually*: If the user wrote down the exact camera time at the start of a "
"dive, the\n"
"difference in time between the two devices can be determined. Actually, as "
"long as the device\n"
"settings for time has not been changed in either device, one could write "
"down the times of\n"
"both devices after the dive or even at the end of the day. One can then "
"manually set the time\n"
"difference in the _Time shift_ dialog. Towards the top of the dialog is a "
"time setting tool\n"
"immediately under the heading _Shift times of image(s) by_, evident in "
"figure *A* below.\n"
"If the camera time is 7 minutes later than that of the dive computer, set "
"the time setting\n"
"tool to a value of 00:07.  Select either the _earlier_ or _later_ radio "
"button.\n"
"In the above example, the _earlier_ option is appropriate, since the photos "
"need to be shifted\n"
"7 minutes earlier (camera is 7 minutes ahead of dive computer). Ignore any "
"\"AM\" or \"PM\" suffix\n"
"in that tool. Click the _OK_ button and synchronisation is achieved.\n"
msgstr ""

#. type: Target for macro image
#: ./user-manual.txt:1573
#, no-wrap
msgid "images/LoadImage3b_f20.jpg"
msgstr ""

#. type: Plain text
#: ./user-manual.txt:1591
#, no-wrap
msgid ""
"*By photograph*: There is a very slick way of achieving synchronisation. If "
"one takes a\n"
"photograph of the face of the dive computer showing the time, then "
"_Subsurface_ can obtain\n"
"the exact time the photograph was taken, using the metadata that the camera "
"stores within\n"
"each photo. In order to do this, use the bottom half of the _Time shift_ "
"dialog. If one uses\n"
"the bottom part, the top part of the dialog is ignored. Click on\n"
"the horizontal bar entitled \"_Select image of 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"
"photograph using the file browser and click on _OK_. This photograph of the "
"dive computer\n"
"appears in the bottom panel of the _Shift times_ dialog. Now _Subsurface_ "
"knows exactly\n"
"when the photograph has been taken. Now set the date-time dialog to the left "
"of the photo\n"
"so that this tool reflects the date and time of the dive computer in the "
"photo. When the\n"
"date-time tool has been set, _Subsurface_ knows exactly what the time "
"difference between\n"
"camera and dive computer is, and synchronisation is achieved.\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
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
#, no-wrap
msgid "Viewing the photos"
msgstr ""

#. type: Plain text
#: ./user-manual.txt:1598
msgid "After the images have been loaded, they appear in two places:"
msgstr ""

#. type: Plain text
#: ./user-manual.txt:1600
msgid "the _Photos_ tab of the *Notes* panel."
msgstr ""

#. type: Plain text
#: ./user-manual.txt:1604
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:"
msgstr ""

#. type: Target for macro image
#: ./user-manual.txt:1605
#, no-wrap
msgid "images/icons/ShowPhotos_f20.png"
msgstr ""

#. type: Plain text
#: ./user-manual.txt:1608
msgid "This results in a profile display as in the image below:"
msgstr ""

#. type: Target for macro image
#: ./user-manual.txt:1609
#, no-wrap
msgid "images/LoadImage4_f20.jpg"
msgstr ""

#. type: Plain text
#: ./user-manual.txt:1613
msgid ""
"If one hovers with the mouse over any of the photo icons, then a thumbnail "
"photo is shown of the appropriate photo. See the image below:"
msgstr ""

#. type: Target for macro image
#: ./user-manual.txt:1614
#, no-wrap
msgid "images/LoadImage5_f20.jpg"
msgstr ""

#. type: Plain text
#: ./user-manual.txt:1623
msgid ""
"Clicking on the thumbnail brings up a full size photo overlaid on the "
"_Subsurface_ window. This allows good viewing of the photographs that have "
"been added (see the image below). Note that the thumbnail has a small "
"dustbin icon in the bottom right hand corner (see image above). If one "
"selects the dustbin, the image is removed from the dive. Therefore some care "
"is required when clicking on a thumbnail. Images can also be deleted using "
"the _Photos_ tab (see text below)."
msgstr ""

#. type: Target for macro image
#: ./user-manual.txt:1624
#, no-wrap
msgid "images/LoadImage6_f20.jpg"
msgstr ""

#. type: Title ====
#: ./user-manual.txt:1626
#, no-wrap
msgid "The _Photos_ tab"
msgstr ""

#. type: Plain text
#: ./user-manual.txt:1637
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."
msgstr ""

#. type: Title ====
#: ./user-manual.txt:1638
#, no-wrap
msgid "Photos on an external hard disk"
msgstr ""

#. type: Plain text
#: ./user-manual.txt:1649
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."
msgstr ""

#. type: Title ====
#: ./user-manual.txt:1651
#, no-wrap
msgid "Moving photographs among directories, hard disks or computers"
msgstr ""

#. type: Plain text
#: ./user-manual.txt:1661
#, 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"
" 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"
" 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"
" 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
#, 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"
msgstr ""

#. type: Plain text
#: ./user-manual.txt:1668
msgid ""
"look through a particular directory (and all its subdirectories recursively) "
"where photos have been moved"
msgstr ""

#. type: Plain text
#: ./user-manual.txt:1669
msgid "to,"
msgstr ""

#. type: Plain text
#: ./user-manual.txt:1671
msgid "calculate fingerprints for all photos in this directory, and"
msgstr ""

#. type: Plain text
#: ./user-manual.txt:1673
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
msgid ""
"loaded into _Subsurface_ (even if the original file name has changed), to "
"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
#, no-wrap
msgid ""
"This is achieved 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
#, no-wrap
msgid "*Upgrading existing photo collections without fingerprints*\n"
msgstr ""

#. type: delimited block *
#: ./user-manual.txt:1690
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_."
msgstr ""

#. type: delimited block *
#: ./user-manual.txt:1692
msgid ""
"_Subsurface_ automatically checks and, if necessary, updates the "
"fingerprints associated with a single dive if:"
msgstr ""

#. type: delimited block *
#: ./user-manual.txt:1693
msgid ""
"The images associated with that dive are visible as thumbnails on the *Dive "
"Profile*."
msgstr ""

#. type: delimited block *
#: ./user-manual.txt:1694
msgid ""
"One edits anything in the *Notes tab* panel and save the edits by selecting "
"_Apply changes_."
msgstr ""

#. type: Title ===
#: ./user-manual.txt:1698
#, no-wrap
msgid "Logging special types of dives"
msgstr ""

#. type: Title ====
#: ./user-manual.txt:1701
#, no-wrap
msgid "Multicylinder dives"
msgstr ""

#. type: Plain text
#: ./user-manual.txt:1708
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:"
msgstr ""

#. type: Plain text
#: ./user-manual.txt:1712
#, 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"
msgstr ""

#. type: Plain text
#: ./user-manual.txt:1717
#, 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"
"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
#, no-wrap
msgid ""
"*Record the cylinder changes on the dive profile*: If the latter option\n"
"was followed, the diver needs to indicate the gas change event by "
"right-clicking at the appropriate point\n"
"in time on the *Dive Profile* panel and indicating the cylinder to which the "
"change was made. After\n"
"right-clicking, follow the context menu to \"Add gas change\" and select the "
"appropriate cylinder from\n"
"those defined during the first step, above (see image below). If the\n"
"*tank bar* button in the toolbar has been activated, the cylinder switches "
"are also indicated in the\n"
"tank bar.\n"
msgstr ""

#. type: Plain text
#: ./user-manual.txt:1729
msgid ""
"Having performed these tasks, _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 "
"decompression."
msgstr ""

#. type: Target for macro image
#: ./user-manual.txt:1730
#, no-wrap
msgid "images/multicylinder_dive.jpg"
msgstr ""

#. type: Title ====
#: ./user-manual.txt:1732
#, no-wrap
msgid "Sidemount dives"
msgstr ""

#. type: Plain text
#: ./user-manual.txt:1738
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:"
msgstr ""

#. type: Plain text
#: ./user-manual.txt:1747
#, 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"
"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
#, no-wrap
msgid ""
"*Within _Subsurface_ describe the cylinders used during the dive*. The diver "
"needs to provide the\n"
"specifications of the different cylinders, using the *Equipment* tab of the "
"*Info Panel* (see\n"
"image below where two 12 litre cylinder were used).\n"
msgstr ""

#. type: Plain text
#: ./user-manual.txt:1760
#, no-wrap
msgid ""
"*Indicate cylinder change events on the _Subsurface_ dive profile*. Once the "
"dive log has been imported\n"
"from a dive computer into _Subsurface_, the cylinder switch events need to "
"be indicated on the dive profile.\n"
"Cylinder changes are recorded by right-clicking at the appropriate point on "
"the dive profile and then\n"
"selecting _Add gas change_. A list of the appropriate cylinders is shown "
"with the\n"
"currently used cylinder greyed out. In the image below Tank 1 is greyed out, "
"leaving only Tank 2\n"
"to be selected. Select the appropriate cylinder. The cylinder change is then "
"indicated on the dive\n"
"profile with a cylinder symbol. If the *Tank Bar* is activated using the "
"toolbar to the left of the\n"
"profile, then the cylinder change is also indicated on the Tank Bar (see "
"image below). After all\n"
"the cylinder change events have been recorded on the dive profile, the "
"correct cylinder pressures\n"
"for both cylinders are shown on the dive profile, as in the image below.\n"
msgstr ""

#. type: Target for macro image
#: ./user-manual.txt:1761
#, no-wrap
msgid "images/sidemount1.jpg"
msgstr ""

#. type: Plain text
#: ./user-manual.txt:1764
msgid ""
"This section gives an example of the versatility of _Subsurface_ as a dive "
"logging tool."
msgstr ""

#. type: Title ====
#: ./user-manual.txt:1767
#, no-wrap
msgid "Semi-closed circuit rebreather (SCR) dives"
msgstr ""

#. type: Named 'icon' AttributeList argument for style 'icon'
#: ./user-manual.txt:1769
#, no-wrap
msgid "images/halcyon_RB80.jpg"
msgstr ""

#. type: Plain text
#: ./user-manual.txt:1779
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."
msgstr ""

#. type: Plain text
#: ./user-manual.txt:1781
msgid ""
"To log pSCR dives, no special procedures are required, just the normal steps "
"outlined above:"
msgstr ""

#. type: Plain text
#: ./user-manual.txt:1783
msgid "Select pSCR in the _Dive Mode_ dropdown list on the *Info* panel."
msgstr ""

#. type: Plain text
#: ./user-manual.txt:1787
msgid ""
"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 "
"xref:S_MulticylinderDives[multicylinder dives]."
msgstr ""

#. type: Plain text
#: ./user-manual.txt:1792
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 "
"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
#, no-wrap
msgid "images/pSCR_profile.jpg"
msgstr ""

#. type: Title ====
#: ./user-manual.txt:1798
#, no-wrap
msgid "Closed circuit rebreather (CCR) dives"
msgstr ""

#. type: Named 'icon' AttributeList argument for style 'icon'
#: ./user-manual.txt:1800
#, no-wrap
msgid "images/APD.jpg"
msgstr ""

#. type: Plain text
#: ./user-manual.txt:1805
msgid ""
"Closed system rebreathers use advanced technology to recirculate gas that "
"has been breathed while doing two things to maintain a breathable oxygen "
"concentration:"
msgstr ""

#. type: Plain text
#: ./user-manual.txt:1806
msgid "remove carbon dioxide from the gas that has been exhaled"
msgstr ""

#. type: Plain text
#: ./user-manual.txt:1815
msgid ""
"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 "
"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 _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."
msgstr ""

#. type: Title =====
#: ./user-manual.txt:1816
#, no-wrap
msgid "Import a CCR dive"
msgstr ""

#. type: Plain text
#: ./user-manual.txt:1830
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 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."
msgstr ""

#. type: Title =====
#: ./user-manual.txt:1831
#, no-wrap
msgid "Displayed information for a CCR dive"
msgstr ""

#. type: Plain text
#: ./user-manual.txt:1841
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 "
"recreational equipment (where pO~2~ values are calculated based on gas "
"composition and dive depth), CCR equipment provide actual measurements of "
"pO~2~, 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~2~ is NOT the mean oxygen partial pressure as "
"given by the CCR equipment, but a value calculated by _Subsurface_ as "
"follows:"
msgstr ""

#. type: Plain text
#: ./user-manual.txt:1843
msgid "For TWO O~2~ sensors the mean value of the two sensors are given."
msgstr ""

#. type: Plain text
#: ./user-manual.txt:1847
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."
msgstr ""

#. type: Plain text
#: ./user-manual.txt:1849
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
msgid "The mean pO~2~ of the sensors is indicated with a green line,"
msgstr ""

#. type: Plain text
#: ./user-manual.txt:1859
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 "
"(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."
msgstr ""

#. type: Target for macro image
#: ./user-manual.txt:1860
#, no-wrap
msgid "images/CCR_preferences_f20.jpg"
msgstr ""

#. type: Plain text
#: ./user-manual.txt:1867
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."
msgstr ""

#. type: Target for macro image
#: ./user-manual.txt:1868
#, no-wrap
msgid "images/CCR_setpoint_f20.jpg"
msgstr ""

#. type: Plain text
#: ./user-manual.txt:1872
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 "
"as follows:"
msgstr ""

#. type: Plain text
#: ./user-manual.txt:1874
msgid "Sensor 1: grey"
msgstr ""

#. type: Plain text
#: ./user-manual.txt:1875
msgid "Sensor 2: blue"
msgstr ""

#. type: Plain text
#: ./user-manual.txt:1876
msgid "Sensor 3: brown"
msgstr ""

#. type: Plain text
#: ./user-manual.txt:1880
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 "
"abnormally low or erratic readings from a particular sensor."
msgstr ""

#. type: Target for macro image
#: ./user-manual.txt:1881
#, no-wrap
msgid "images/CCR_sensor_data_f20.jpg"
msgstr ""

#. type: Plain text
#: ./user-manual.txt:1886
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, "
"if applicable) are shown in the usual way as for open circuit dives."
msgstr ""

#. type: Plain text
#: ./user-manual.txt:1890
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 "
"over a triangle, a description of that event is given as the bottom line in "
"the xref:S_InfoBox[Information Box]."
msgstr ""

#. type: Plain text
#: ./user-manual.txt:1898
msgid ""
"_Cylinder pressures_: 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 _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."
msgstr ""

#. type: Target for macro image
#: ./user-manual.txt:1899
#, no-wrap
msgid "images/CCR_dive_profile_f22.jpg"
msgstr ""

#. type: Plain text
#: ./user-manual.txt:1904
msgid ""
"_Equipment-specific information_: Equipment-specific information gathered by "
"_Subsurface_ is shown in the xref:S_ExtraDataTab[Extra data tab]. This may "
"include setup information or metadata about the dive."
msgstr ""

#. type: Plain text
#: ./user-manual.txt:1910
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 "
"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:"
msgstr ""

#. type: Named 'icon' AttributeList argument for style 'icon'
#: ./user-manual.txt:1911 ./user-manual.txt:2094
#, no-wrap
msgid "images/icons/cceiling.jpg"
msgstr ""

#. type: Plain text
#: ./user-manual.txt:1916
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:"
msgstr ""

#. type: Target for macro image
#: ./user-manual.txt:1917
#, no-wrap
msgid "images/CCR_dive_ceilingF22.jpg"
msgstr ""

#. type: Plain text
#: ./user-manual.txt:1921
msgid ""
"More equipment-specific information for downloading CCR dive logs for "
"Poseidon MkVI and APD equipment can be found in "
"xref:_appendix_b_dive_computer_specific_information_for_importing_dive_information[Appendix "
"B]."
msgstr ""

#. type: Title ==
#: ./user-manual.txt:1922
#, no-wrap
msgid "Obtaining more information about dives entered into the logbook"
msgstr ""

#. type: Title ===
#: ./user-manual.txt:1924
#, no-wrap
msgid "The *Info* tab (for individual dives)"
msgstr ""

#. type: Plain text
#: ./user-manual.txt:1931
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 "
"surface interval before the dive, the maximum and mean depths of the dive, "
"the gas volume consumed, the surface air consumption (SAC) and the number of "
"oxygen toxicity units (OTU) incurred."
msgstr ""

#. type: Plain text
#: ./user-manual.txt:1938
msgid ""
"Gas consumption and SAC calculations: _Subsurface_ calculates SAC and Gas "
"consumption taking in account gas incompressibility, particularly at tank "
"pressures above 200 bar, making them more accurate.  Users should refer to "
"xref:SAC_CALCULATION[Appendix F] for more information."
msgstr ""

#. type: Title ===
#: ./user-manual.txt:1940
#, no-wrap
msgid "The *Extra Data* tab (usually for individual dives)"
msgstr ""

#. type: Plain text
#: ./user-manual.txt:1948
msgid ""
"When using a dive computer, it often reports several data items that cannot "
"easily be presented in a standardised way because the nature of the "
"information differs from one dive computer to another. These data often "
"comprise setup information, metadata about a dive, battery levels, no fly "
"times, or gradient factors used during the dive. When possible, this "
"information is presented in the *Extra Data* tab. Below is an image showing "
"extra data for a dive using a Poseidon rebreather."
msgstr ""

#. type: Target for macro image
#: ./user-manual.txt:1949
#, no-wrap
msgid "images/ExtraDataTab_f20.jpg"
msgstr ""

#. type: Title ===
#: ./user-manual.txt:1951
#, no-wrap
msgid "The *Stats* tab (for groups of dives)"
msgstr ""

#. type: Plain text
#: ./user-manual.txt:1962
msgid ""
"The Stats tab gives summary statistics for more than one dive, assuming that "
"more than one dive has been selected in the *Dive List* using the standard "
"Ctrl-click or Shift-click of the mouse. If only one dive has been selected, "
"figures pertaining to only that dive are given. This tab shows the number of "
"dives selected, the total amount of dive time in these dives, as well as the "
"minimum, maximum and mean for the dive duration, water temperature and "
"surface air consumption (SAC). It also shows the depth of the shallowest and "
"deepest dives of those selected."
msgstr ""

#. type: Title ===
#: ./user-manual.txt:1964
#, no-wrap
msgid "The *Dive Profile*"
msgstr ""

#. type: Target for macro image
#: ./user-manual.txt:1966
#, no-wrap
msgid "images/Profile2.jpg"
msgstr ""

#. type: Plain text
#: ./user-manual.txt:1977
msgid ""
"Of all the panels in _Subsurface_, the Dive Profile contains the most "
"detailed information about each dive. The Dive Profile has a *button bar* on "
"the left hand side that allows control over several display options. The "
"functions of these buttons are described below. The main item in the Dive "
"Profile is the graph of dive depth as a function of time. In addition to the "
"obvious information of the depth it also shows the ascent and descent rates "
"compared to the recommended speed of going up or down in the water "
"column. This information is given using different colours:"
msgstr ""

#. type: delimited block |
#: ./user-manual.txt:1984
#, no-wrap
msgid ""
"|*Colour*|*Descent speed (m/min)*|*Ascent speed (m/min)*\n"
"|Red|> 30|> 18\n"
"|Orange|18 - 30|9 - 18\n"
"|Yellow|9 - 18|4 - 9\n"
"|Light green|1.5 - 9|1.5 - 4\n"
"|Dark green|< 1.5|< 1.5\n"
msgstr ""

#. type: Plain text
#: ./user-manual.txt:1989
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."
msgstr ""

#. type: Named 'icon' AttributeList argument for style 'icon'
#: ./user-manual.txt:1990
#, no-wrap
msgid "images/icons/scale.jpg"
msgstr ""

#. type: Plain text
#: ./user-manual.txt:1995
msgid ""
"In some cases the dive profile does not fill the whole area of the *Dive "
"Profile* panel. Clicking the *Scale* button in the toolbar on the left of "
"the dive profile frequently increases the size of the dive profile to fill "
"the area of the panel efficiently."
msgstr ""

#. type: Plain text
#: ./user-manual.txt:1998
#, no-wrap
msgid ""
"*Water temperature* is displayed with its own blue line with temperature "
"values\n"
"placed adjacent to significant changes.\n"
msgstr ""

#. type: Plain text
#: ./user-manual.txt:2005
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."
msgstr ""

#. type: Named 'icon' AttributeList argument for style 'icon'
#: ./user-manual.txt:2006
#, no-wrap
msgid "images/icons/O2.jpg"
msgstr ""

#. type: Plain text
#: ./user-manual.txt:2010
msgid ""
"Clicking this button allows display of the partial pressure of *oxygen* "
"during the dive. This is depicted below the dive depth and water temperature "
"graphs."
msgstr ""

#. type: Named 'icon' AttributeList argument for style 'icon'
#: ./user-manual.txt:2011
#, no-wrap
msgid "images/icons/N2.jpg"
msgstr ""

#. type: Plain text
#: ./user-manual.txt:2014
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
#, no-wrap
msgid "images/icons/He.jpg"
msgstr ""

#. type: Plain text
#: ./user-manual.txt:2019
msgid ""
"Clicking this button allows display of the partial pressure of *helium* "
"during the dive.  This is only of importance to divers using Trimix, "
"Helitrox or similar breathing gasses."
msgstr ""

#. type: Plain text
#: ./user-manual.txt:2032
msgid ""
"The *air consumption* graph displays the tank pressure and its change during "
"the dive. The air consumption takes depth into account so that even when "
"manually entering the start and end pressures the graph is not a straight "
"line.  Similarly to the depth graph the slope of the tank pressure gives the "
"user information about the momentary SAC rate (Surface Air Consumption) when "
"using an air integrated dive computer.  Here the colour coding is not "
"relative to some absolute values but relative to the average normalised air "
"consumption during the dive. So areas that are red or orange indicate times "
"of increased normalized air consumption while dark green reflects times when "
"the diver was using less gas than average."
msgstr ""

#. type: Named 'icon' AttributeList argument for style 'icon'
#: ./user-manual.txt:2033
#, no-wrap
msgid "images/icons/Heartbutton.png"
msgstr ""

#. type: Plain text
#: ./user-manual.txt:2037
msgid ""
"Clicking on the heart rate button will allow the display of heart rate "
"information during the dive if the dive computer was attached to a heart "
"rate sensor."
msgstr ""

#. type: Plain text
#: ./user-manual.txt:2045
#, no-wrap
msgid ""
"It is possible to *zoom* into the profile graph. This is done either by "
"using\n"
"the scroll wheel / scroll gesture of your mouse or trackpad. By default\n"
"_Subsurface_ always shows a profile area large enough for at least 30 "
"minutes\n"
"and 30m\n"
" (100ft) – this way short or shallow dives are intuitively recognizable;\n"
"something\n"
"that free divers clearly won’t care about.\n"
msgstr ""

#. type: Target for macro image
#: ./user-manual.txt:2046
#, no-wrap
msgid "images/MeasuringBar.png"
msgstr ""

#. type: Named 'icon' AttributeList argument for style 'icon'
#: ./user-manual.txt:2048
#, no-wrap
msgid "images/icons/ruler.jpg"
msgstr ""

#. type: Plain text
#: ./user-manual.txt:2056
msgid ""
"Measurements of *depth or time differences* can be achieved by using the "
"*ruler button* on the left of the dive profile panel.  The measurement is "
"done by dragging the red dots to the two points on the dive profile that the "
"user wishes to measure. Information is then given in the horizontal white "
"area underneath the two red dots."
msgstr ""

#. type: Named 'icon' AttributeList argument for style 'icon'
#: ./user-manual.txt:2057
#, no-wrap
msgid "images/icons/ShowPhotos.png"
msgstr ""

#. type: Plain text
#: ./user-manual.txt:2064
msgid ""
"Photographs that have been added to a dive can be shown on the profile by "
"selecting the *Show-photo* button. The position of a photo on the profile "
"indicates the exact time when this photo was taken. If this button is not "
"active, the photos are hidden."
msgstr ""

#. type: Plain text
#: ./user-manual.txt:2093
msgid ""
"The profile can also include the dive computer reported *ceiling* (more "
"precisely, the deepest deco stop that the dive computer calculated for each "
"particular moment in time) as a red overlay on the dive profile. Ascent "
"ceilings arise when a direct ascent to the surface increases the risk of a "
"diver suffering from decompression sickness (DCS) and it is necessary to "
"either ascend slower or to perform decompression stop(s) before ascending to "
"the surface. Not all dive computers record this information and make it "
"available for download; for example all of the Suunto dive computers fail to "
"make this very useful data available to divelog software. _Subsurface_ also "
"calculates ceilings independently, shown as a green overlay on the dive "
"profile.  Because of the differences in algorithms used and amount of data "
"available (and other factors taken into consideration at the time of the "
"calculation) it is unlikely that ceilings from dive computers and from "
"_Subsurface_ are the same, even if the same algorithm and _gradient factors_ "
"(see below) are used.  It is also quite common that _Subsurface_ calculates "
"a ceiling for non-decompression dives when the dive computer stayed in "
"non-deco mode during the whole dive (represented by the [green]#dark green# "
"section in the profile at the beginning of this section). This is caused by "
"the fact that _Subsurface’s_ calculations describe the deco obligation at "
"each moment during a dive, while dive computers usually take the upcoming "
"ascent into account. During the ascent some excess nitrogen (and possibly "
"helium) are already breathed off so even though the diver technically "
"encountered a ceiling at depth, the dive still does not require an explicit "
"deco stop. This feature allows dive computers to offer longer non-stop "
"bottom times."
msgstr ""

#. type: Plain text
#: ./user-manual.txt:2099
msgid ""
"If the dive computer itself calculates a ceiling and makes it available to "
"_Subsurface_ during upload of dives, this can be shown as a red area by "
"checking *Dive computer reported ceiling* button on the Profile Panel."
msgstr ""

#. type: Named 'icon' AttributeList argument for style 'icon'
#: ./user-manual.txt:2100
#, no-wrap
msgid "images/icons/ceiling1.jpg"
msgstr ""

#. type: Plain text
#: ./user-manual.txt:2105
msgid ""
"If the *Calculated ceiling* button on the Profile Panel is clicked, then a "
"ceiling, calculated by _Subsurface_, is shown in green if it exists for a "
"particular dive (*A* in figure below). This setting can be modified in two "
"ways:"
msgstr ""

#. type: Named 'icon' AttributeList argument for style 'icon'
#: ./user-manual.txt:2106
#, no-wrap
msgid "images/icons/ceiling2.jpg"
msgstr ""

#. type: Plain text
#: ./user-manual.txt:2110
msgid ""
"If, in addition, the *show all tissues* button on the Profile Panel is "
"clicked, the ceiling is shown for the tissue compartments following the "
"Bühlmann model (*B* in figure below)."
msgstr ""

#. type: Named 'icon' AttributeList argument for style 'icon'
#: ./user-manual.txt:2111
#, no-wrap
msgid "images/icons/ceiling3.jpg"
msgstr ""

#. type: Plain text
#: ./user-manual.txt:2115
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
#, no-wrap
msgid "images/Ceilings2.jpg"
msgstr ""

#. type: Named 'icon' AttributeList argument for style 'icon'
#: ./user-manual.txt:2118
#, no-wrap
msgid "images/icons/ShowCylindersButton.jpg"
msgstr ""

#. type: Plain text
#: ./user-manual.txt:2124
msgid ""
"By selecting this icon, the different cylinders used during a dive can be "
"represented as a coloured bar at the bottom of the *Dive Profile*. In "
"general oxygen is represented by a green bar, nitrogen with a yellow bar and "
"helium with a red bar. The image below shows a dive which first uses a "
"trimix cylinder (red and green), followed by a switch to a nitrox cylinder "
"(yellow and green) after 23 minutes. Cylinders with air are shown as a light "
"blue bar."
msgstr ""

#. type: Target for macro image
#: ./user-manual.txt:2125
#, no-wrap
msgid "images/ShowCylinders_f20.jpg"
msgstr ""

#. type: Named 'icon' AttributeList argument for style 'icon'
#: ./user-manual.txt:2128
#, no-wrap
msgid "images/tissues.jpg"
msgstr ""

#. type: Plain text
#: ./user-manual.txt:2140
msgid ""
"Display inert gas tissue pressures relative to ambient inert gas pressure "
"(horizontal grey line).  Tissue pressures are calculated using the Bühlmann "
"ZH-L16 algorithm and are displayed as lines ranging from green (faster "
"tissues) to blue (slower tissues).  The black line, graphed above the "
"ambient pressure, is the maximum allowable tissue supersaturation (pressure "
"limit) derived from the gradient factors specified in the *Preferences*. For "
"divers involved in planned decompression diving, efficient rates of "
"offgasing are obtained with tissue pressures between the ambient inert gas "
"pressure (grey line) and the pressure limit (black line). This display is a "
"representation of the tissue pressures during the whole dive. In 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."
msgstr ""

#. type: Target for macro image
#: ./user-manual.txt:2141
#, no-wrap
msgid "images/tissuesGraph.jpg"
msgstr ""

#. type: Plain text
#: ./user-manual.txt:2149
msgid ""
"Gradient Factor settings strongly affect the calculated ceilings and their "
"depths.  For more information about Gradient factors, see the section on "
"xref:S_GradientFactors[Gradient Factor Preference settings]. The currently "
"used gradient factors (e.g. GF 35/75) are shown above the depth profile if "
"the appropriate toolbar buttons are activated.  *N.B.:* The indicated "
"gradient factors are NOT the gradient factors in use by the dive computer, "
"but those used by _Subsurface_ to calculate deco obligations during the "
"dive. For more information external to this manual see:"
msgstr ""

#. type: Plain text
#: ./user-manual.txt:2151
#, no-wrap
msgid ""
" ** http://www.tek-dive.com/portal/upload/M-Values.pdf[Understanding "
"M-values by Erik Baker, _Immersed_ Vol. 3, No. 3.]\n"
msgstr ""

#. type: Plain text
#: ./user-manual.txt:2153
#, no-wrap
msgid ""
" ** "
"link:http://www.rebreatherworld.com/general-and-new-to-rebreather-articles/5037-gradient-factors-for-dummies.html[Gradient "
"factors for dummies, by Kevin Watts]\n"
msgstr ""

#. type: Title ===
#: ./user-manual.txt:2155
#, no-wrap
msgid "The Dive Profile context menu"
msgstr ""

#. type: Plain text
#: ./user-manual.txt:2173
msgid ""
"The context menu for the Dive Profile is accessed by right-clicking while "
"the mouse cursor is over the Dive Profile panel. The menu allows the "
"creation of Bookmarks or Gas Change Event markers or manual CCR set-point "
"changes other than the ones that might have been imported from a Dive "
"Computer. Markers are placed against the depth profile line and with the "
"time of the event set by where the mouse cursor was when the right mouse "
"button was initially clicked to bring up the menu. Gas Change events involve "
"a selection of which gas is being switched to, the list of choices being "
"based on the available gases defined in the *Equipment* Tab. Set-point "
"change events open a dialog allowing to choose the next set-point value. As "
"in the planner, a set-point value of zero indicates the diver is breathing "
"from an open circuit system while any non-zero value indicates the use of a "
"closed circuit rebreather (CCR).  By right-clicking while over an existing "
"marker a menu appears, adding options to allow deletion of the marker or to "
"allow all markers of that type to be hidden. Hidden events can be restored "
"to view by selecting Unhide all events from the context menu."
msgstr ""

#. type: Title ===
#: ./user-manual.txt:2175
#, no-wrap
msgid "The *Information Box*"
msgstr ""

#. type: Plain text
#: ./user-manual.txt:2185
msgid ""
"The Information box displays a large range of information pertaining to the "
"dive profile. Normally the Information Box is located to the top left of the "
"*Dive Profile* panel. If the mouse points outside of the *Dive Profile* "
"panel, then only the top line of the Information Box is visible (see "
"left-hand part of figure (*A*) below). The Information Box can be moved "
"around in the *Dive Profile* panel by click-dragging it with the mouse so "
"that it is not obstructing important detail. The position of the Information "
"Box is saved and used again during subsequent dive analyses."
msgstr ""

#. type: Target for macro image
#: ./user-manual.txt:2186
#, no-wrap
msgid "images/InfoBox2.jpg"
msgstr ""

#. type: Plain text
#: ./user-manual.txt:2203
msgid ""
"The moment the mouse points inside the *Dive Profile* panel, the information "
"box expands and shows many data items. In this situation, the data reflect "
"the time point along the dive profile indicated by the mouse cursor (see "
"right-hand part of figure (*B*) above where the Information Box reflects the "
"situation at the position of the cursor [arrow] in that image). Therefore, "
"moving the cursor in the horizontal direction allows the Information Box to "
"show information for any point along the dive profile.  In this mode, the "
"Information Box gives extensive statistics about depth, gas and ceiling "
"characteristics of the particular dive. These include: Time period into the "
"dive (indicated by a @), depth, cylinder pressure (P), temperature, "
"ascent/descent rate, surface air consumption (SAC), oxygen partial pressure, "
"maximum operating depth, equivalent air depth (EAD), equivalent narcotic "
"depth (END), equivalent air density depth (EADD), decompression requirements "
"at that instant in time (Deco), time to surface (TTS), the calculated "
"ceiling, as well as the calculated ceiling for several Bühlmann tissue "
"compartments."
msgstr ""

#. type: Plain text
#: ./user-manual.txt:2206
msgid ""
"The user has control over the display of several statistics, represented as "
"four buttons on the left of the profile panel. These are:"
msgstr ""

#. type: Named 'icon' AttributeList argument for style 'icon'
#: ./user-manual.txt:2207
#, no-wrap
msgid "images/icons/MOD.jpg"
msgstr ""

#. type: Plain text
#: ./user-manual.txt:2216
msgid ""
"Clicking this button causes the Information Box to display the *Maximum "
"Operating Depth (MOD)* of the dive, given the gas mixture used. MOD is "
"dependent on the oxygen concentration in the breathing gas.  For air (21% "
"oxygen) it is around 57 m 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."
msgstr ""

#. type: Named 'icon' AttributeList argument for style 'icon'
#: ./user-manual.txt:2217
#, no-wrap
msgid "images/icons/NDL.jpg"
msgstr ""

#. type: Plain text
#: ./user-manual.txt:2229
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_."
msgstr ""

#. type: Named 'icon' AttributeList argument for style 'icon'
#: ./user-manual.txt:2230
#, no-wrap
msgid "images/icons/SAC.jpg"
msgstr ""

#. type: Plain text
#: ./user-manual.txt:2239
msgid ""
"Clicking this button causes the Information Box to display the *Surface Air "
"Consumption (SAC)*.  SAC is an indication of the surface-normalised "
"respiration rate of a diver. The value of SAC is less than the real "
"respiration rate because a diver at 10m uses breathing gas at a rate roughly "
"double that of the equivalent rate at the surface. SAC gives an indication "
"of breathing gas consumption rate independent of the depth of the dive so "
"that the respiratory rates of different dives can be compared. The units for "
"SAC is litres/min or cub ft/min."
msgstr ""

#. type: Named 'icon' AttributeList argument for style 'icon'
#: ./user-manual.txt:2240
#, no-wrap
msgid "images/icons/EAD.jpg"
msgstr ""

#. type: Plain text
#: ./user-manual.txt:2255
msgid ""
"Clicking this button displays the *Equivalent Air Depth (EAD)* for nitrox "
"dives as well as the *Equivalent Narcotic Depth (END)* for trimix "
"dives. These are numbers of importance to divers who use breathing gases "
"other than air. Their values are dependent on the composition of the "
"breathing gas.  The EAD is the depth of a hypothetical air dive that has the "
"same partial pressure of nitrogen as the current depth of the nitrox dive at "
"hand. A nitrox dive leads to the same decompression obligation as an air "
"dive to the depth equalling the EAD. The END is the depth of a hypothetical "
"air dive that has the same sum of partial pressures of the narcotic gases "
"nitrogen and oxygen as the current trimix dive. A trimix diver can expect "
"the same narcotic effect as a diver breathing air diving at a depth "
"equalling the END."
msgstr ""

#. type: Plain text
#: ./user-manual.txt:2257
msgid ""
"Figure (*B*) above shows an information box with a nearly complete set of "
"data."
msgstr ""

#. type: Title ====
#: ./user-manual.txt:2259
#, no-wrap
msgid "The Gas Pressure Bar Graph"
msgstr ""

#. type: Plain text
#: ./user-manual.txt:2266
msgid ""
"On the left of the *Information Box* is a vertical bar graph indicating the "
"pressures of the nitrogen (and other inert gases, e.g. helium, if "
"applicable) that the diver was inhaling _at a particular instant during the "
"dive_, indicated by the position of the cursor on the *Dive Profile*. The "
"drawing on the left below indicates the meaning of the different parts of "
"the Gas Pressure Bar Graph."
msgstr ""

#. type: Target for macro image
#: ./user-manual.txt:2267
#, no-wrap
msgid "images/GasPressureBarGraph.jpg"
msgstr ""

#. type: Plain text
#: ./user-manual.txt:2273
msgid ""
"The light green area indicates the total gas, with the top margin of the "
"light green area indicating the total gas pressure inhaled by the diver and "
"measured from the bottom of the graph to the top of the light green "
"area. This pressure has a _relative_ value in the graph and does not "
"indicate absolute pressure."
msgstr ""

#. type: Plain text
#: ./user-manual.txt:2279
msgid ""
"The horizontal black line underneath the light green margin indicates the "
"equilibrium pressure of the inert gases inhaled by the diver, usually "
"nitrogen. In the case of trimix, it is the pressures of nitrogen and helium "
"combined. In this example, the user is diving with EAN32, so the inert gas "
"pressure is 68% of the distance from the bottom of the graph to the total "
"gas pressure value."
msgstr ""

#. type: Plain text
#: ./user-manual.txt:2283
msgid ""
"The dark green area at the bottom of the graph represents the pressures of "
"inert gas in each of the 16 tissue compartments, following the Bühlmann "
"algorithm, the fast tissues being on the left hand side."
msgstr ""

#. type: Plain text
#: ./user-manual.txt:2288
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 "
"gradient factor shown is an interpolation between the GFLow and GFHigh "
"values specified in the Graph tab of the *Preferences Panel* of "
"*Subsurface*."
msgstr ""

#. type: Plain text
#: ./user-manual.txt:2292
msgid ""
"The bottom margin of the red area in the graph indicates the Bühlman-derived "
"M-value, that is the pressure value of inert gases at which bubble formation "
"is expected to be severe, resulting in decompression sickness."
msgstr ""

#. type: Plain text
#: ./user-manual.txt:2295
msgid ""
"These five values are indicated on the left in the graph above. The way the "
"Gas Pressure Bar Graph changes during a dive is indicated on the right hand "
"side of the above figure for a diver using EAN32."
msgstr ""

#. type: Plain text
#: ./user-manual.txt:2298
msgid ""
"Graph *A* indicates the situation at the start of a dive with diver at the "
"surface. The pressures in all the tissue compartments are still at the "
"equilibrium pressure because no diving has taken place."
msgstr ""

#. type: Plain text
#: ./user-manual.txt:2301
msgid ""
"Graph *B* indicates the situation after a descent to 30 meters. Few of the "
"tissue compartments have had time to respond to the descent, their gas "
"pressures being far below the equilibrium gas pressure."
msgstr ""

#. type: Plain text
#: ./user-manual.txt:2306
msgid ""
"Graph *C* represents the pressures after 30 minutes at 30 m. The fast "
"compartments have attained equilibrium (i.e. they have reached the hight of "
"the black line indicating the equilibrium pressure). The slower compartments "
"(towards the right) have not reached equilibrium and are in the process of "
"slowly increasing in pressure."
msgstr ""

#. type: Plain text
#: ./user-manual.txt:2312
msgid ""
"Graph *D* shows the pressures after ascent to a depth of 4.5 meters. Since, "
"during ascent, the total inhaled gas pressure has decreased strongly from 4 "
"bar to 1.45 bar, the pressures in the different tissue compartments now "
"exceed that of the total gas pressure and approaches the gradient factor "
"value (i.e.  the top black horizontal line). Further ascent will result in "
"exceeding the gradient factor value (GFHigh), endangering the diver."
msgstr ""

#. type: Plain text
#: ./user-manual.txt:2317
msgid ""
"Graph *E* indicates the situation after remaining at 4.5 meters for 10 "
"minutes. The fast compartments have decreased in pressure. As expected, the "
"pressures in the slow compartments have not changed much.  The pressures in "
"the fast compartments do not approach the GFHigh value any more and the "
"diver is safer than in the situation indicated in graph *D*."
msgstr ""

#. type: Title ==
#: ./user-manual.txt:2320
#, no-wrap
msgid "Organising the logbook (Manipulating groups of dives)"
msgstr ""

#. type: Title ===
#: ./user-manual.txt:2322
#, no-wrap
msgid "The Dive List context menu"
msgstr ""

#. type: Plain text
#: ./user-manual.txt:2326
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."
msgstr ""

#.  TODO: NEEDS REPLACEMENT
#. type: Target for macro image
#: ./user-manual.txt:2328
#, 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."
msgstr ""

#. type: Title ====
#: ./user-manual.txt:2332
#, no-wrap
msgid "Customising the columns showed in the *Dive List* panel"
msgstr ""

#. type: Target for macro image
#: ./user-manual.txt:2334
#, no-wrap
msgid "images/DiveListOptions.jpg"
msgstr ""

#. type: Plain text
#: ./user-manual.txt:2342
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."
msgstr ""

#. type: Title ===
#: ./user-manual.txt:2344
#, no-wrap
msgid "Renumbering the dives"
msgstr ""

#. type: Plain text
#: ./user-manual.txt:2356
msgid ""
"Dives are normally numbered incrementally from non-recent dives (low "
"sequence numbers) to recent dives (having the highest sequence numbers). The "
"numbering of the dives is not always consistent. For instance, when "
"non-recent dives are added to the dive list the numbering does not "
"automatically follow on because of the dives that are more recent in "
"date/time than the newly-added dive with an older date/time. Therefore, one "
"may sometimes need to renumber the dives.  This is performed by selecting "
"(from the Main Menu) _Log -> Renumber_. Users are given a choice with "
"respect to the lowest sequence number to be used.  Completing this operation "
"results in new sequence numbers (based on date/time)  for the dives in the "
"*Dive List* panel."
msgstr ""

#. type: Plain text
#: ./user-manual.txt:2361
msgid ""
"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."
msgstr ""

#. type: Title ===
#: ./user-manual.txt:2363
#, no-wrap
msgid "Grouping dives into trips and manipulating trips"
msgstr ""

#. type: Plain text
#: ./user-manual.txt:2371
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 "
"ungrouped dive list (*A*, on the left) as well as the corresponding grouped "
"dive list comprising five dive trips (*B*, on the right):"
msgstr ""

#. type: Target for macro image
#: ./user-manual.txt:2372
#, no-wrap
msgid "images/Group2.jpg"
msgstr ""

#. type: Plain text
#: ./user-manual.txt:2378
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."
msgstr ""

#. type: Title ====
#: ./user-manual.txt:2379
#, no-wrap
msgid "Editing the title and associated information for a particular trip"
msgstr ""

#. type: Plain text
#: ./user-manual.txt:2392
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 "
"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 *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
#, no-wrap
msgid "Viewing the dives during a particular trip"
msgstr ""

#. type: Plain text
#: ./user-manual.txt:2398
msgid ""
"Once the dives have been grouped into trips, users can expand one or more "
"trips by clicking the arrow-head on the left of each trip title. This "
"expands the selected trip, revealing the individual dives performed during "
"the trip."
msgstr ""

#. type: Title ====
#: ./user-manual.txt:2399
#, no-wrap
msgid "Collapsing or expanding dive information for different trips"
msgstr ""

#. type: Plain text
#: ./user-manual.txt:2404
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."
msgstr ""

#. type: Title ====
#: ./user-manual.txt:2405
#, no-wrap
msgid "Merging dives from more than one trip into a single trip"
msgstr ""

#. type: Plain text
#: ./user-manual.txt:2410
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 "
"above. (Merge trip with trip below; Merge trip with trip above)"
msgstr ""

#. type: Title ====
#: ./user-manual.txt:2411
#, no-wrap
msgid "Splitting a single trip into more than one trip"
msgstr ""

#. type: Plain text
#: ./user-manual.txt:2421
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):"
msgstr ""

#. type: Target for macro image
#: ./user-manual.txt:2422
#, no-wrap
msgid "images/SplitDive3a.jpg"
msgstr ""

#. type: Title ===
#: ./user-manual.txt:2424
#, no-wrap
msgid "Manipulating single dives"
msgstr ""

#. type: Title ====
#: ./user-manual.txt:2426
#, no-wrap
msgid "Delete a dive from the dive log"
msgstr ""

#. type: Plain text
#: ./user-manual.txt:2433
msgid ""
"Dives can be permanently deleted from the dive log by selecting and "
"right-clicking them to bring up the context menu, and then selecting *Delete "
"dive(s)*. Typically this would apply to a case where a user wishes to delete "
"workshop calibration dives of the dive computer or dives of extremely short "
"duration."
msgstr ""

#. type: Title ====
#: ./user-manual.txt:2434
#, no-wrap
msgid "Unlink a dive from a trip"
msgstr ""

#. type: Plain text
#: ./user-manual.txt:2441
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."
msgstr ""

#. type: Title ====
#: ./user-manual.txt:2442
#, no-wrap
msgid "Add a dive to the trip immediately above"
msgstr ""

#. type: Plain text
#: ./user-manual.txt:2447
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 "
"bring up the context menu, and then select *Create new trip above*."
msgstr ""

#. type: Title ====
#: ./user-manual.txt:2448
#, no-wrap
msgid "Shift the start time of dive(s)"
msgstr ""

#. type: Plain text
#: ./user-manual.txt:2459
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."
msgstr ""

#. type: Title ====
#: ./user-manual.txt:2460
#, no-wrap
msgid "Merge dives into a single dive"
msgstr ""

#. type: Plain text
#: ./user-manual.txt:2470
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:"
msgstr ""

#. type: Target for macro image
#: ./user-manual.txt:2471
#, no-wrap
msgid "images/MergedDive.png"
msgstr ""

#. type: Title ====
#: ./user-manual.txt:2473
#, no-wrap
msgid "Undo dive manipulations"
msgstr ""

#. type: Plain text
#: ./user-manual.txt:2479
msgid ""
"Important actions on dives or trips, described above, can be undone or "
"redone.  This includes: _delete dives_, _merge dives_, _renumber dives_ and "
"_shift dive times_.  To do this after performing any of these actions, from "
"the *Main Menu* select _Edit_. This brings up the possibility to _Undo_ or "
"_Redo_ an action."
msgstr ""

#. type: Title ===
#: ./user-manual.txt:2482
#, no-wrap
msgid "Filtering the dive list"
msgstr ""

#. type: Plain text
#: ./user-manual.txt:2488
msgid ""
"The dives in the *Dive List* panel can be filtered, that is, one can select "
"only some of the dives based on their attributes, e.g. dive tags, dive site, "
"dive master, buddy or protective clothing. For instance, filtering allows "
"one to list the deep dives at a particular dive site, or otherwise the cave "
"dives with a particular buddy."
msgstr ""

#. type: Plain text
#: ./user-manual.txt:2496
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* "
"with the white cross."
msgstr ""

#. type: Target for macro image
#: ./user-manual.txt:2497
#, no-wrap
msgid "images/Filterpanel.jpg"
msgstr ""

#. type: Plain text
#: ./user-manual.txt:2506
msgid ""
"Four filter criteria may be used to filter the dive list: dive tags, person "
"(buddy / dive master), dive site and dive suit, each of which is represented "
"by a check list with check boxes. Above each check list is a second-level "
"filter tool, allowing the listing of only some of the attributes within that "
"check list. For instance, typing \"_ca_\" in the filter textbox above the "
"tags check list results in the tags check list being reduced to \"_cave_\" "
"and \"_cavern_\". Filtering of the check list enables the rapid finding of "
"search terms for filtering the dive list."
msgstr ""

#. type: Plain text
#: ./user-manual.txt:2514
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 "
"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
#, 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:"
msgstr ""

#. type: Plain text
#: ./user-manual.txt:2521
msgid "Export dive information to _Facebook_"
msgstr ""

#. type: Plain text
#: ./user-manual.txt:2523
msgid ""
"xref:S_Export_other[Export dive information to other destinations or "
"formats]"
msgstr ""

#. type: Title ===
#: ./user-manual.txt:2525
#, no-wrap
msgid "Exporting dive information to _Facebook_"
msgstr ""

#. type: Plain text
#: ./user-manual.txt:2534
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."
msgstr ""

#. type: Target for macro image
#: ./user-manual.txt:2535
#, no-wrap
msgid "images/facebook1_f20.jpg"
msgstr ""

#. type: Plain text
#: ./user-manual.txt:2540
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)."
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_."
msgstr ""

#. 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."
msgstr ""

#. type: Target for macro image
#: ./user-manual.txt:2558
#, no-wrap
msgid "images/facebook2_f20.jpg"
msgstr ""

#. type: Plain text
#: ./user-manual.txt:2562
msgid ""
"If required, then close the _Facebook_ connection by either closing "
"_Subsurface_ or by selecting _File -> Preferences -> Facebook_ from the Main "
"Menu, and clicking the appropriate button on the Facebook Preferences panel."
msgstr ""

#. type: Title ===
#: ./user-manual.txt:2564
#, no-wrap
msgid "Export dive information  to other destinations or formats"
msgstr ""

#. type: Plain text
#: ./user-manual.txt:2569
msgid ""
"For non-_Facebook exports_, the export function can be reached by selecting "
"_File -> Export_, which brings up the Export dialog. This dialog always "
"gives two options: save ALL dives, or save only the dives selected in *Dive "
"List* panel of _Subsurface_. Click the appropriate radio button (see images "
"below)."
msgstr ""

#. type: Target for macro image
#: ./user-manual.txt:2570
#, no-wrap
msgid "images/Export_f20.jpg"
msgstr ""

#. type: Plain text
#: ./user-manual.txt:2573
msgid "A dive log or part of it can be saved in three formats:"
msgstr ""

#. type: Plain text
#: ./user-manual.txt:2575
msgid "_Subsurface XML_ format. This is the native format used by _Subsurface_."
msgstr ""

#. type: Plain text
#: ./user-manual.txt:2579
msgid ""
"Universal Dive Data Format (_UDDF_). Refer to _http://uddf.org_ for more "
"information.  UDDF is a generic format that enables communication among many "
"dive computers and computer programs."
msgstr ""

#. type: Plain text
#: ./user-manual.txt:2583
msgid ""
"_Divelogs.de_, an Internet-based dive log repository. In order to upload to "
"_Divelogs.de_, one needs a user-ID as well as a password for "
"_Divelogs.de_. Log into _http://en.divelogs.de_ and subscribe to this "
"service in order to upload dive log data from _Subsurface_."
msgstr ""

#. type: Plain text
#: ./user-manual.txt:2587
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."
msgstr ""

#. type: Plain text
#: ./user-manual.txt:2592
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, "
"duration, depth, temperature and pressure: in short, most of the information "
"that recreational divers enter into handwritten log books."
msgstr ""

#. type: Plain text
#: ./user-manual.txt:2595
msgid ""
"_CSV dive profile_, that includes a large amount of detail for each dive, "
"including the depth profile, temperature and pressure information of each "
"dive."
msgstr ""

#. type: Plain text
#: ./user-manual.txt:2608
msgid ""
"_HTML_ format, in which the dive(s) are stored in HTML files, readable with "
"an Internet browser. Most modern web browsers are supported, but JavaScript "
"must be enabled. 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 *Dive Profile* 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 *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."
msgstr ""

#. type: Plain text
#: ./user-manual.txt:2613
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 "
"in text, as shown in the image below."
msgstr ""

#. type: Target for macro image
#: ./user-manual.txt:2614
#, no-wrap
msgid "images/mapview_f20.jpg"
msgstr ""

#. type: Plain text
#: ./user-manual.txt:2621
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."
msgstr ""

#. type: Plain text
#: ./user-manual.txt:2623
msgid "_General Settings_, under the HTML tab, provides the following options:"
msgstr ""

#. type: Plain text
#: ./user-manual.txt:2631
#, no-wrap
msgid ""
"** Subsurface Numbers: if this option is checked, the dive(s) are exported "
"with the\n"
"   numbers associated with them in Subsurface, Otherwise the dive(s) will be "
"numbered\n"
"   starting from 1.\n"
"** Export Yearly Statistics: if this option is checked, a yearly statistics "
"table will\n"
"   be attached to the HTML exports.\n"
"** Export List only: a list of dives only (date, time, depth, duration) will "
"be exported\n"
"   and the detailed dive information, e.g. dive profile, will not be "
"available.\n"
msgstr ""

#. type: Plain text
#: ./user-manual.txt:2634
msgid ""
"Under _Style Options_ some style-related options are available like font "
"size and theme."
msgstr ""

#. type: Plain text
#: ./user-manual.txt:2637
msgid ""
"Export to other formats can be achieved through third party facilities, for "
"instance _www.divelogs.de_."
msgstr ""

#. type: Title ==
#: ./user-manual.txt:2639
#, no-wrap
msgid "Keeping a _Subsurface_ dive log in the Cloud"
msgstr ""

#. type: Plain text
#: ./user-manual.txt:2650
msgid ""
"For each diver, dive log information is highly important. Not only is it a "
"record of diving activities for one's own pleasure, but it is important "
"information required for admission to further training courses or "
"(sometimes) even diving sites. The security of the dive log is therefore "
"critical. In order to have a dive log that is resistant to failure of a home "
"computer hard drive, loss or theft of equipment, the Cloud is an obvious "
"solution. This also has the added benefit that one can access one's dive log "
"from anywhere in the world without having to carry it with oneself. For this "
"reason, facilities such as _divelogs.de_ and _Diving Log_ offer to store "
"dive log information on the Internet."
msgstr ""

#. type: Plain text
#: ./user-manual.txt:2656
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 "
"a user on the cloud.  To use _Subsurface cloud storage_ , follow these "
"steps:"
msgstr ""

#. type: Title ===
#: ./user-manual.txt:2657
#, no-wrap
msgid "Create a cloud storage account"
msgstr ""

#. type: Plain text
#: ./user-manual.txt:2674
#, no-wrap
msgid ""
"** Open the *Network Preferences* by selecting _File_ -> _Preferences_ -> "
"_Network_.\n"
"** In the section headed _Subsurface cloud storage_, enter an email address "
"that\n"
"   _Subsurface_ can use for user registration.\n"
"** Enter a novel password that _Subsurface_ will use to store the\n"
"  dive log in the cloud.\n"
"** Click _Apply_ to send the above email address and password to the\n"
"  (remote) cloud server. The server responds by sending a verification PIN "
"to\n"
"  the above email address (This is the *only* occasion that _Subsurface_ "
"uses the\n"
"  email address provided above). The *Network Preferences* dialog now has a "
"new PIN text\n"
"   box, not visible previously.\n"
"** Enter the PIN in the corresponding text box in the *Network Preferences* "
"dialog\n"
"(this field is only visible while the server is waiting for email\n"
"address confirmation)\n"
"** Click _Apply_ again. The _Subsurface cloud storage_ account\n"
"will be marked as verified and the _Subsurface cloud storage_ service is "
"initialised for use.\n"
msgstr ""

#. type: Title ===
#: ./user-manual.txt:2675
#, no-wrap
msgid "Using _Subsurface cloud storage_"
msgstr ""

#. type: Plain text
#: ./user-manual.txt:2685
#, no-wrap
msgid ""
"** Once the cloud storage has been initialised, 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"
"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"
msgstr ""

#. type: Plain text
#: ./user-manual.txt:2690
#, 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"
"connected to the Internet.\n"
msgstr ""

#. type: Title ===
#: ./user-manual.txt:2692
#, no-wrap
msgid "Web access to _Subsurface cloud storage_"
msgstr ""

#. type: Plain text
#: ./user-manual.txt:2702
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."
msgstr ""

#. type: Title ===
#: ./user-manual.txt:2703
#, no-wrap
msgid "Other cloud services"
msgstr ""

#. type: Plain text
#: ./user-manual.txt:2713
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."
msgstr ""

#. type: Target for macro image
#: ./user-manual.txt:2714
#, no-wrap
msgid "images/Cloud.jpg"
msgstr ""

#. type: Plain text
#: ./user-manual.txt:2723
msgid ""
"The _Dropbox_ program creates a copy of the _Dropbox_ Internet Cloud content "
"on one's desktop computer. When the computer is connected to the Internet, "
"the Internet content is automatically updated. Therefore both the _Open_ and "
"_Save_ of dive logs are done using the local copy of the dive log in the "
"local _Dropbox_ folder, so there's no need for a direct internet "
"connection. If the local copy is modified, e.g. by adding a dive, the remote "
"copy in the _Dropbox_ server in the Cloud will be automatically updated "
"whenever Internet access is available."
msgstr ""

#. type: Plain text
#: ./user-manual.txt:2730
msgid ""
"In this way a dive log in one's _Dropbox_ folder can be accessed seamlessly "
"from the Internet and can be accessed from any place with Internet "
"access. Currently there are no costs involved for this service. Dropbox "
"(Windows, Mac and Linux) can be installed by accessing the "
"http://www.dropbox.com/install[_Install Page on the Dropbox website_]"
msgstr ""

#. type: Plain text
#: ./user-manual.txt:2736
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."
msgstr ""

#. type: Plain text
#: ./user-manual.txt:2739
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
#, no-wrap
msgid "Printing a dive log"
msgstr ""

#. type: Plain text
#: ./user-manual.txt:2746
#, no-wrap
msgid ""
"_Subsurface_ provides a simple and flexible interface 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:"
msgstr ""

#. type: Plain text
#: ./user-manual.txt:2751
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."
msgstr ""

#. type: Plain text
#: ./user-manual.txt:2753
msgid ""
"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 *Dive Profile* panel."
msgstr ""

#. type: Plain text
#: ./user-manual.txt:2756
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:"
msgstr ""

#. type: Target for macro image
#: ./user-manual.txt:2757 ./user-manual.txt:4185
#, no-wrap
msgid "images/Print1_f22.jpg"
msgstr ""

#. type: Plain text
#: ./user-manual.txt:2760
msgid "Under _Print type_ select one of two options:"
msgstr ""

#. type: Plain text
#: ./user-manual.txt:2762
msgid ""
"_Dive list print_: Print dives from the *Dive List* panel with profiles and "
"other information."
msgstr ""

#. type: Plain text
#: ./user-manual.txt:2763
msgid "_Statistics print_: Print yearly statistics of the dives."
msgstr ""

#. type: Plain text
#: ./user-manual.txt:2765
msgid "Under _Print options_ select:"
msgstr ""

#. type: Plain text
#: ./user-manual.txt:2770
msgid ""
"Printing only the dives selected from the dive list prior to 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."
msgstr ""

#. type: Plain text
#: ./user-manual.txt:2772
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)."
msgstr ""

#. type: Plain text
#: ./user-manual.txt:2775
msgid ""
"Under _Template_ select a template to be used as the page layout. There are "
"several templates (see image *B*, above)."
msgstr ""

#. type: Plain text
#: ./user-manual.txt:2777
msgid "_Table_: This prints a summary table of all dives selected (see below)."
msgstr ""

#. type: Target for macro image
#: ./user-manual.txt:2778
#, no-wrap
msgid "images/Print_summarylist_f22.jpg"
msgstr ""

#. type: Plain text
#: ./user-manual.txt:2781
msgid ""
"_Flow layout_: Print the text associated with each dive without printing the "
"dive profiles"
msgstr ""

#. type: Plain text
#: ./user-manual.txt:2782
msgid "of each dive (see below):"
msgstr ""

#. type: Target for macro image
#: ./user-manual.txt:2783
#, no-wrap
msgid "images/Print_flow_layout_f22.jpg"
msgstr ""

#. type: Plain text
#: ./user-manual.txt:2786
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
#, no-wrap
msgid "images/print2_f22.jpg"
msgstr ""

#. type: Plain text
#: ./user-manual.txt:2791
msgid "_Two Dives_: Print two dives per page, also showing the dive profiles."
msgstr ""

#. type: Plain text
#: ./user-manual.txt:2792
msgid "_Six Dives_: Print six dives per page, also showing the dive profiles."
msgstr ""

#. type: Plain text
#: ./user-manual.txt:2796
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."
msgstr ""

#. type: Plain text
#: ./user-manual.txt:2800
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):"
msgstr ""

#. type: Target for macro image
#: ./user-manual.txt:2801
#, no-wrap
msgid "images/Print_print_f22.jpg"
msgstr ""

#. type: Plain text
#: ./user-manual.txt:2806
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 "
"dives.  Below is a (rather small) example of the output for one particular "
"page."
msgstr ""

#. type: Target for macro image
#: ./user-manual.txt:2807
#, no-wrap
msgid "images/Printpreview.jpg"
msgstr ""

#. type: Title ===
#: ./user-manual.txt:2809
#, no-wrap
msgid "Writing a custom print template (advanced)"
msgstr ""

#. type: Plain text
#: ./user-manual.txt:2813
msgid ""
"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 _Template_ "
"dropdown list in the print dialogue. See <<S_APPENDIX_E,APPENDIX E>> for "
"information on how to write or modify a template."
msgstr ""

#. type: Title ==
#: ./user-manual.txt:2815
#, no-wrap
msgid "Configuring a dive computer"
msgstr ""

#. 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."
msgstr ""

#. type: Plain text
#: ./user-manual.txt:2828
msgid ""
"Once the dive computer is connected to the _Subsurface_ computer, select "
"_File -> Configure dive computer_ from the _Main Menu_. Provide the "
"appropriate device name in the text box at the top of the configuration "
"panel and select the appropriate dive computer model from the panel on the "
"left-hand (see image below)."
msgstr ""

#. type: Target for macro image
#: ./user-manual.txt:2829
#, no-wrap
msgid "images/Configure_dc_f20.jpg"
msgstr ""

#. type: Plain text
#: ./user-manual.txt:2832
msgid ""
"Using the appropriate buttons on the configuration panel, the following "
"actions can be performed:"
msgstr ""

#. type: Plain text
#: ./user-manual.txt:2835
#, no-wrap
msgid ""
"*Retrieve available details*. This loads the existing configuration from the "
"dive computer\n"
"to _Subsurface_, showing it in the configuration panel.\n"
msgstr ""

#. type: Plain text
#: ./user-manual.txt:2837
#, no-wrap
msgid ""
"*Save changes to device*. This changes the configuration of the\n"
"dive computer to correspond to the information shown in the configuration "
"panel.\n"
msgstr ""

#. type: Plain text
#: ./user-manual.txt:2839
#, no-wrap
msgid ""
"*Backup*. This saves the configuration data to a file. _Subsurface_ asks "
"for\n"
"a file location and file name for the saved information.\n"
msgstr ""

#. type: Plain text
#: ./user-manual.txt:2841
#, no-wrap
msgid ""
"*Restore backup*. This loads the information from a backup file and displays "
"it\n"
"in the configuration panel.\n"
msgstr ""

#. type: Plain text
#: ./user-manual.txt:2843
#, no-wrap
msgid ""
"*Update firmware*. If new firmware is available for the dive computer, this "
"is\n"
"loaded into the dive computer.\n"
msgstr ""

#. type: Title ==
#: ./user-manual.txt:2846
#, no-wrap
msgid "Setting user _Preferences_ for _Subsurface_"
msgstr ""

#. type: Plain text
#: ./user-manual.txt:2856
msgid ""
"There are several user-definable settings within _Subsurface_, found by "
"selecting _File -> Preferences_. The settings are performed 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."
msgstr ""

#. type: Title ===
#: ./user-manual.txt:2857
#, no-wrap
msgid "Defaults"
msgstr ""

#. type: Plain text
#: ./user-manual.txt:2860
msgid "There are several settings in the *Defaults* panel:"
msgstr ""

#. type: Target for macro image
#: ./user-manual.txt:2861
#, no-wrap
msgid "images/Pref1_f20.jpg"
msgstr ""

#. type: Plain text
#: ./user-manual.txt:2865
#, no-wrap
msgid ""
"  ** *Lists and tables*: Here one can specify the font type and font size of "
"the\n"
"     *Dive Table* panel. By decreasing the font size of the *Dive Table*, "
"users can see more dives on a screen.\n"
msgstr ""

#. type: Plain text
#: ./user-manual.txt:2870
#, no-wrap
msgid ""
"  ** *Dives*: For the _Default Dive File_ one needs to specify the directory "
"and\n"
"     file name of one's\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
#, 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
#, no-wrap
msgid ""
"_Local default file_: When checked, _Subsurface_ automatically loads a dive "
"log from the local hard disk\n"
"as described above.\n"
msgstr ""

#. type: Plain text
#: ./user-manual.txt:2875
#, 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"
msgstr ""

#. type: Plain text
#: ./user-manual.txt:2877
#, 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
#, no-wrap
msgid ""
"dives that he/she doesn't consider valid dives, e.g. pool dives, but still "
"want to\n"
"keep them in the dive log). This controls whether those dives are displayed "
"in\n"
"the dive list.\n"
msgstr ""

#. type: Plain text
#: ./user-manual.txt:2882
#, no-wrap
msgid "** *Default cylinder*: Specify the default cylinder listed in\n"
msgstr ""

#. type: Plain text
#: ./user-manual.txt:2883
#, no-wrap
msgid "the *Equipment* tab of the *Notes* panel.\n"
msgstr ""

#. type: Plain text
#: ./user-manual.txt:2885
#, no-wrap
msgid ""
"** *Animations*: Some actions in showing the dive profile are performed "
"using\n"
msgstr ""

#. type: Plain text
#: ./user-manual.txt:2891
#, no-wrap
msgid ""
"animations. For instance, the axis values for depth and time change from "
"dive to\n"
"dive. When viewing a different dive, these changes in axis characteristics "
"do not\n"
"happen instantaneously, but are animated. The _Speed_ of animations can be "
"controlled\n"
"by setting this slider\n"
"with faster animation speed to the left, and a 0 value representing no "
"animation\n"
"at all.\n"
msgstr ""

#. type: Plain text
#: ./user-manual.txt:2893
#, 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
#, no-wrap
msgid "cleared and set to default values.\n"
msgstr ""

#. type: Title ===
#: ./user-manual.txt:2895
#, no-wrap
msgid "Units"
msgstr ""

#. type: Target for macro image
#: ./user-manual.txt:2896
#, no-wrap
msgid "images/Pref2_f20.jpg"
msgstr ""

#. type: Plain text
#: ./user-manual.txt:2903
msgid ""
"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 *Personalise* radio "
"button, units can be selected independently, with some units in the metric "
"system and others in imperial."
msgstr ""

#. type: Plain text
#: ./user-manual.txt:2909
msgid ""
"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."
msgstr ""

#. type: Title ===
#: ./user-manual.txt:2910
#, no-wrap
msgid "Graph"
msgstr ""

#. type: Target for macro image
#: ./user-manual.txt:2912
#, no-wrap
msgid "images/Pref3_f20.jpg"
msgstr ""

#. type: Plain text
#: ./user-manual.txt:2916
msgid "This panel allows two type of selections:"
msgstr ""

#. type: Plain text
#: ./user-manual.txt:2936
#, no-wrap
msgid ""
"*Show*: Here users can specify the amount of information shown as part of\n"
"the dive profile:\n"
"** Thresholds: _Subsurface_ can display the nitrogen, oxygen and the helium "
"partial pressures during\n"
"   the dive, 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"
"   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"
"** _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"
"   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"
"   ascent.\n"
msgstr ""

#. type: Plain text
#: ./user-manual.txt:2938
#, no-wrap
msgid "*Misc*:\n"
msgstr ""

#. type: Plain text
#: ./user-manual.txt:2951
#, 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"
"   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"
"   harsh. Checking the *GFLow at max depth* box causes GF_Low to be used at "
"the\n"
"   deepest depth of a dive. If this box is not checked, GF_Low is applied "
"at\n"
"   all depths deeper than the first deco stop. For more information see:\n"
msgstr ""

#. type: Plain text
#: ./user-manual.txt:2953
#, no-wrap
msgid ""
" *** http://www.tek-dive.com/portal/upload/M-Values.pdf[Understanding "
"M-values by Erik Baker, _Immersed_ Vol. 3, No. 3.]\n"
msgstr ""

#. type: Plain text
#: ./user-manual.txt:2955
#, no-wrap
msgid ""
" *** "
"link:http://www.rebreatherworld.com/general-and-new-to-rebreather-articles/5037-gradient-factors-for-dummies.html[Gradient "
"factors for dummies, by Kevin Watts]\n"
msgstr ""

#. type: Plain text
#: ./user-manual.txt:2959
#, 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"
"    values. See the section on xref:S_CCR_dives[Closed Circuit Rebreather "
"dives].\n"
msgstr ""

#. type: Plain text
#: ./user-manual.txt:2963
#, no-wrap
msgid ""
" ** _CCR: Show individual O~2~ sensor values when viewing pO~2~:_ Show the "
"pO~2~\n"
"    values associated with each of the individual oxygen sensors of a CCR "
"system.\n"
"    See the section on xref:S_CCR_dives[Closed Circuit Rebreather dives].\n"
msgstr ""

#. type: Plain text
#: ./user-manual.txt:2965
#, no-wrap
msgid "*Configuring dive planning using rebreather equipment:*\n"
msgstr ""

#. type: Plain text
#: ./user-manual.txt:2967
#, 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
#, no-wrap
msgid ""
"CCR dive plan. This determines the pO~2~  maintained\n"
"during a particular dive. Setpoint changes during the dive can be added via "
"the\n"
"profile context menu.\n"
msgstr ""

#. type: Plain text
#: ./user-manual.txt:2972
#, no-wrap
msgid ""
"** _pSCR O~2~ metabolism rate:_ For a semiclosed rebreather (pSCR) system, "
"this is the\n"
msgstr ""

#. type: Plain text
#: ./user-manual.txt:2974
#, no-wrap
msgid ""
"volume of oxygen used by a diver during a minute. Set this value for pSCR "
"dive planning\n"
"and decompression calculations.\n"
msgstr ""

#. type: Plain text
#: ./user-manual.txt:2976
#, 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
#, no-wrap
msgid ""
"environment to that of the gas recirculated to the diver. Set this value for "
"a\n"
"pSCR dive plan. A 1:10 ratio is commonly used.\n"
msgstr ""

#. type: Title ===
#: ./user-manual.txt:2980
#, no-wrap
msgid "Language"
msgstr ""

#. type: Plain text
#: ./user-manual.txt:2982
msgid "Choose a language that _Subsurface_ will use."
msgstr ""

#. type: Target for macro image
#: ./user-manual.txt:2983
#, no-wrap
msgid "images/Pref4_f20.jpg"
msgstr ""

#. type: Plain text
#: ./user-manual.txt:2993
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*."
msgstr ""

#. type: Title ===
#: ./user-manual.txt:2994
#, no-wrap
msgid "Network"
msgstr ""

#. type: Plain text
#: ./user-manual.txt:3000
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."
msgstr ""

#. type: Target for macro image
#: ./user-manual.txt:3001
#, no-wrap
msgid "images/Pref5_f20.jpg"
msgstr ""

#. type: Plain text
#: ./user-manual.txt:3004
msgid "This dialogue has three sections:"
msgstr ""

#. type: Plain text
#: ./user-manual.txt:3012
#, no-wrap
msgid ""
"** _Proxy type_:\n"
"If a proxy server is used for Internet access, the type of proxy needs to be "
"selected from the dropdown list,\n"
"after which the IP address of the host and the appropriate port number "
"should\n"
"be provided. If the proxy server uses authentication, the appropriate userID "
"and\n"
"password are required so that _Subsurface_ can automatically pass\n"
"through the proxy server to access the Internet. This information is usually "
"obtained\n"
"from one's ISP.\n"
msgstr ""

#. type: Plain text
#: ./user-manual.txt:3017
#, 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"
"   Two additional options are given:\n"
msgstr ""

#. type: Plain text
#: ./user-manual.txt:3018
#, 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
#, no-wrap
msgid "while the user performs other tasks within _Subsurface_.\n"
msgstr ""

#. type: Plain text
#: ./user-manual.txt:3020
#, 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
#, no-wrap
msgid "information is saved in raw text form, not encoded in any way.\n"
msgstr ""

#. type: Plain text
#: ./user-manual.txt:3026
#, no-wrap
msgid ""
"** _Subsurface web service_: When one subscribes to the "
"<<S_Companion,Subsurface web service>>, a very\n"
"     long and hard-to-remember userID is issued. This is the place to save "
"that userID. By\n"
"     checking the option _Save User ID locally?_, one ensures that a local "
"copy of that userID\n"
"     is saved.\n"
msgstr ""

#. type: Title ===
#: ./user-manual.txt:3029
#, no-wrap
msgid "Facebook Accesss"
msgstr ""

#. type: Plain text
#: ./user-manual.txt:3032
msgid ""
"This panel allows one to log into a Facebook account in order to transfer "
"information from Subsurface to Facefook."
msgstr ""

#. type: Target for macro image
#: ./user-manual.txt:3033
#, no-wrap
msgid "images/Pref6_f20.jpg"
msgstr ""

#. type: Plain text
#: ./user-manual.txt:3041
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."
msgstr ""

#. type: Title ===
#: ./user-manual.txt:3042
#, no-wrap
msgid "Georeference"
msgstr ""

#. type: Plain text
#: ./user-manual.txt:3050
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 "
"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)."
msgstr ""

#. type: Target for macro image
#: ./user-manual.txt:3051
#, no-wrap
msgid "images/Pref7_f20.jpg"
msgstr ""

#. type: Title ==
#: ./user-manual.txt:3054
#, no-wrap
msgid "The _Subsurface_ dive planner"
msgstr ""

#. type: Plain text
#: ./user-manual.txt:3059
msgid ""
"Dive planning is an advanced feature of _Subsurface_, accessible by "
"selecting _Log -> Plan Dive_ from the main menu. It allows calculation of "
"nitrogen load during a dive by using the Bühlmann ZH-L16 algorithm with the "
"addition of gradient factors as implemented by Erik Baker."
msgstr ""

#. type: delimited block *
#: ./user-manual.txt:3067
msgid ""
"The _Subsurface_ dive planner IS CURRENTLY EXPERIMENTAL and assumes the user "
"is already familiar with the _Subsurface_ user interface. It is explicitly "
"used under the following conditions:"
msgstr ""

#. type: delimited block *
#: ./user-manual.txt:3070
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
msgid "The user plans dives within his/her certification limits."
msgstr ""

#. type: delimited block *
#: ./user-manual.txt:3074
msgid ""
"Dive planning makes large assumptions about the characteristics of the "
"_average person_ and cannot compensate for individual physiology or health "
"or personal history or life style characteristics."
msgstr ""

#. type: delimited block *
#: ./user-manual.txt:3075
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
msgid "The user is familiar with the user interface of _Subsurface_."
msgstr ""

#. type: delimited block *
#: ./user-manual.txt:3078
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
#, no-wrap
msgid "The _Subsurface_ dive planner screen"
msgstr ""

#. type: Plain text
#: ./user-manual.txt:3085
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."
msgstr ""

#. type: Plain text
#: ./user-manual.txt:3089
msgid ""
"At the top right hand is a green *design panel* upon which the profile of "
"the dive can be manipulated directly by dragging and clicking as explained "
"below. This feature makes the _Subsurface_ dive planner unique in ease of "
"use."
msgstr ""

#. type: Plain text
#: ./user-manual.txt:3093
msgid ""
"At the bottom right is a text panel with a heading of _Dive Plan "
"Details_. This is where the details of the dive plan are provided in a way "
"that can easily be copied to other software. This is also where any warning "
"messages about the dive plan are printed."
msgstr ""

#. type: Target for macro image
#: ./user-manual.txt:3094
#, no-wrap
msgid "images/PlannerWindow1_f20.jpg"
msgstr ""

#. type: Title ===
#: ./user-manual.txt:3097
#, no-wrap
msgid "Open circuit dives"
msgstr ""

#. type: Plain text
#: ./user-manual.txt:3100
msgid ""
"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:"
msgstr ""

#. type: Plain text
#: ./user-manual.txt:3103
#, no-wrap
msgid ""
"** Open Circuit (the default)\n"
"** CCR\n"
"** pSCR\n"
msgstr ""

#. type: Plain text
#: ./user-manual.txt:3105
msgid "Choose the Open Circuit option."
msgstr ""

#. type: Plain text
#: ./user-manual.txt:3109
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, "
"assuming a sea-level atmospheric pressure of 1.013 bar."
msgstr ""

#. type: Plain text
#: ./user-manual.txt:3118
msgid ""
"In the table labelled _Available Gases_, add the information of the "
"cylinders to be used as well as the gas composition within that "
"cylinder. This is done in a similar way as for "
"<<cylinder_definitions,providing cylinder data for dive logs>>. Choose the "
"cylinder type by double clicking the cylinder type and using the dropdown "
"list, then specify the work pressure of this cylinder. By leaving the oxygen "
"concentration (O2%) filed empty, the 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."
msgstr ""

#. type: Plain text
#: ./user-manual.txt:3120
msgid "The profile of the planned dive can be created in two ways:"
msgstr ""

#. type: Plain text
#: ./user-manual.txt:3125
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."
msgstr ""

#. type: Plain text
#: ./user-manual.txt:3133
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 "
"table represents the duration and the final depth of the descent from the "
"surface. Subsequent segments describe the bottom phase of the dive.  The _CC "
"set point_ 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 _Dive "
"planner points_ table automatically appear in the *Dive Profile* diagram."
msgstr ""

#. type: Title ====
#: ./user-manual.txt:3134
#, no-wrap
msgid "Recreational dives"
msgstr ""

#. type: Plain text
#: ./user-manual.txt:3149
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."
msgstr ""

#. type: Plain text
#: ./user-manual.txt:3154
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."
msgstr ""

#. type: Plain text
#: ./user-manual.txt:3157
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
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 "
"_Available gases_."
msgstr ""

#. type: Plain text
#: ./user-manual.txt:3166
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 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
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."
msgstr ""

#. type: Plain text
#: ./user-manual.txt:3183
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 "
"table under _Dive planner points_ 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 _Dive Planner Points_ table. _Subsurface_ will "
"automatically extend the bottom section of the dive to the maximum duration "
"within the no-decompression limits (NDL)."
msgstr ""

#. type: Plain text
#: ./user-manual.txt:3186
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
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 "
"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 "
"_Available gases_. 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."
msgstr ""

#. type: Plain text
#: ./user-manual.txt:3198
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."
msgstr ""

#. type: Target for macro image
#: ./user-manual.txt:3199
#, no-wrap
msgid "images/rec_diveplan.jpg"
msgstr ""

#. type: Title ====
#: ./user-manual.txt:3201
#, no-wrap
msgid "Non-recreational open circuit dives, including decompression"
msgstr ""

#. type: Plain text
#: ./user-manual.txt:3205
msgid ""
"Non-recreational dive planning involves exceeding the no-deco limits and/or "
"using multiple breathing gases.  Such dives are planned in three stages:"
msgstr ""

#. type: Plain text
#: ./user-manual.txt:3216
#, no-wrap
msgid ""
"*a) Nitrogen management*: This is performed 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"
" ** 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
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."
msgstr ""

#. type: Plain text
#: ./user-manual.txt:3223
msgid "For more information external to this manual see:"
msgstr ""

#. type: Plain text
#: ./user-manual.txt:3225
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
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
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: "
"1-905492-07-3.  An excellent non-technical review that discusses both the "
"Bühlmann deco model and the VPM-B model."
msgstr ""

#. type: Plain text
#: ./user-manual.txt:3236
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."
msgstr ""

#. type: Plain text
#: ./user-manual.txt:3245
#, no-wrap
msgid ""
"*b) Oxygen management*: In the *Gas Options* part of the dive specification, "
"the maximum partial\n"
"pressure for oxygen needs to be specified for the\n"
"bottom part of the dive (_bottom po2_) as well as for the decompression part "
"of the dive (_deco po2_).\n"
"The most commonly\n"
"used values are 1.4 bar for the bottom part of the dive and 1.6 bar for any "
"decompression\n"
"stages. Normally, a partial pressure of 1.6 bar is not exceeded. PO2 "
"settings and the depth at which switching to a gas takes place can also be "
"edited in the\n"
"_Available Gases_ dialog. Normally the planner decides on switching to a new "
"gas when, during\n"
"ascent, the partial pressure of the new gas has increased to 1.6 bar.\n"
msgstr ""

#. type: Plain text
#: ./user-manual.txt:3259
#, 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"
"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"
"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"
"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"
"For technical diving, this reserve can be up to 66% of the total available "
"gas.\n"
msgstr ""

#. type: Plain text
#: ./user-manual.txt:3271
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."
msgstr ""

#. type: Plain text
#: ./user-manual.txt:3283
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."
msgstr ""

#. type: Plain text
#: ./user-manual.txt:3291
msgid ""
"Indicate any changes in gas cylinder used by indicating gas changes as "
"explained in the section <<S_CreateProfile,hand-creating a dive "
"profile>>. These changes should reflect the cylinders and gas compositions "
"defined in the table with _Available Gases_.  If two or more gases are used, "
"automatic gas switches will be suggested during the ascent to the "
"surface. However, these changes can be deleted by right-clicking the gas "
"change and by manually creating a gas change by right-clicking on the "
"appropriate waypoint."
msgstr ""

#. type: Plain text
#: ./user-manual.txt:3300
msgid ""
"A non-zero value in the \"CC set point\" column of the table of dive planner "
"points indicates a valid setpoint for oxygen partial pressure and that the "
"segment is dived using a closed circuit rebreather (CCR). If the last "
"manually entered segment is a CCR segment, the decompression phase is "
"computed assuming the diver uses a CCR with the specified set-point. If the "
"last segment (however short) is on open circuit (OC, indicated by a zero "
"set-point) the decompression is computed in OC mode. The planner only "
"considers gas changes in OC mode."
msgstr ""

#. type: Plain text
#: ./user-manual.txt:3303
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
#, no-wrap
msgid "images/DivePlanner2_f20.jpg"
msgstr ""

#. type: Plain text
#: ./user-manual.txt:3309
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_."
msgstr ""

#. type: Plain text
#: ./user-manual.txt:3311
#, no-wrap
msgid "*The dive plan details*\n"
msgstr ""

#. type: Plain text
#: ./user-manual.txt:3319
msgid ""
"On the bottom right of the dive planner, under _Dive Plan Details_, the "
"exact details of the dive plan are provided. These details may be modified "
"by checking any of the options under the _Notes_ section of the dive "
"planner, immediately to the left of the _Dive Plan Details_. If a _Verbatim "
"dive plan_ is requested, a detailed sentence-level explanation of the dive "
"plan is given. If any of the management specifications have been exceeded "
"during the planning, a warning message is printed underneath the dive plan "
"information."
msgstr ""

#. type: Plain text
#: ./user-manual.txt:3324
msgid ""
"If the option _Display segment duration_ is checked, then the duration of "
"each depth level is indicated in the _Dive Plan Details_. This duration "
"INCLUDES the transition time to get to that level. However, if the _Display "
"transition in deco_ option is checked, the transitions are shown separately "
"from the segment durations at a particular level."
msgstr ""

#. type: Title ===
#: ./user-manual.txt:3325
#, no-wrap
msgid "Planning pSCR dives"
msgstr ""

#. type: Plain text
#: ./user-manual.txt:3340
#, no-wrap
msgid ""
"To plan a dive using a passive semi-closed rebreather (pSCR), select _pSCR_ "
"rather than\n"
"_Open circuit_ in the dropdown list.\n"
"The parameters of the pSCR dive can be set by selecting  _File ->   "
"Preferences ->   Graph_\n"
"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"
"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"
"are specified for pSCR dives. Below is a dive plan for a pSCR dive. The dive "
"is comparable\n"
"to that of the CCR dive below, but note the longer ascent duration due to "
"the lower oxygen\n"
"in the loop due to the oxygen drop across the mouthpiece of the pSCR "
"equipment.\n"
msgstr ""

#. type: Target for macro image
#: ./user-manual.txt:3341
#, no-wrap
msgid "images/Planner_pSCR1_f20.jpg"
msgstr ""

#. type: Title ===
#: ./user-manual.txt:3344
#, no-wrap
msgid "Planning CCR dives"
msgstr ""

#. type: Plain text
#: ./user-manual.txt:3348
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
#, no-wrap
msgid ""
"*Available gases*: In the _Available gases_ table, enter the cylinder "
"information for the\n"
"diluent cylinder and for any bail-out cylinders. Do NOT enter the "
"information for the oxygen\n"
"cylinder since it is implied when the _CCR_ dropdown selection is made.\n"
msgstr ""

#. type: Plain text
#: ./user-manual.txt:3362
#, 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"
"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"
msgstr ""

#. type: Plain text
#: ./user-manual.txt:3364
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
#, no-wrap
msgid "images/Planner_CCR1_f20.jpg"
msgstr ""

#. type: Plain text
#: ./user-manual.txt:3369
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."
msgstr ""

#. type: Title ===
#: ./user-manual.txt:3371
#, no-wrap
msgid "Modifying an existing dive plan"
msgstr ""

#. type: Plain text
#: ./user-manual.txt:3378
msgid ""
"Normally, when a dive plan has been saved, it is accessible from the *Dive "
"List*, like any other dive log. Within the *Dive List* there is not a way to "
"change a saved dive plan.  To perform changes to a dive plan, select it on "
"the *Dive List*. Then, in the main menu, select _Log -> Re-plan dive_. This "
"will open the selected dive plan within the dive planner, allowing changes "
"to be made and saved as usual."
msgstr ""

#. type: Plain text
#: ./user-manual.txt:3384
msgid ""
"In addition there is the option \"Save new\". This keeps the original "
"planned dive and adds a (possibly modified) copy to the dive list. If that "
"copy is saved with the same start time as the original, the two dives are "
"considered two versions of the same dive and do not influence other each "
"during decompression calculation (see next section)."
msgstr ""

#. type: Title ===
#: ./user-manual.txt:3385
#, no-wrap
msgid "Planning for repetitive dives"
msgstr ""

#. type: Plain text
#: ./user-manual.txt:3392
msgid ""
"Repetitive dives can easily be planned if the dates and start times of the "
"repetitive dive set is specified appropriately in the top left-hand _Start "
"Time_ field. _Subsurface_ calculates the gas loading figures correctly and "
"the effect of the first dive is evaluated on later dives."
msgstr ""

#. type: Plain text
#: ./user-manual.txt:3398
msgid ""
"If one has just completed a long/deep dive and is planning another dive, "
"then highlight, in the *Dive List*, the dive that has just been completed "
"and then activate the planner. Depending on the start time of the planned "
"dive, the planner takes into account the gas loading incurred during the "
"completed dive and allows planning within these limitations."
msgstr ""

#. type: Plain text
#: ./user-manual.txt:3403
msgid ""
"If only a few standard configurations are used (e.g. in GUE), then a "
"template dive can be created conforming to one of the configurations. If one "
"now wishes to plan a dive using this configuration, just highlight the "
"template dive in the *Dive List* and activate the planner: the planner takes "
"into account the configuration in the highlighted dive."
msgstr ""

#. type: Title ===
#: ./user-manual.txt:3404
#, no-wrap
msgid "Printing the dive plan"
msgstr ""

#. type: Plain text
#: ./user-manual.txt:3409
msgid ""
"Selecting the _Print_ button in the planner allows printing of the _Dive "
"Plan Details_ for wet notes. Alternatively one can cut and paste the _Dive "
"Plan Details_ for inclusion in a text file or word processing document."
msgstr ""

#. type: Plain text
#: ./user-manual.txt:3419
msgid ""
"Dive plans have many characteristics in common with dive logs (dive profile, "
"dive notes, etc).  After a dive plan has been saved, the dive details and "
"gas calculations are saved in the *Notes* tab. While a dive plan is being "
"designed, it can be printed using the _Print_ button in the dive "
"planner. This prints the dive details and gas calculations in the _Dive Plan "
"Details_ panel of the dive planner. However, after the plan has been saved, "
"it is represented in a way very similar to a dive log and the gas "
"calculations cannot be accessed in the same way as during the planning "
"process. The only way to print the dive plan is to use the _File -> Print_ "
"facility on the main menu in the same way as for dive logs or by copy and "
"paste to a word processor."
msgstr ""

#. type: Title ==
#: ./user-manual.txt:3420
#, no-wrap
msgid "Description of the Subsurface Main Menu items"
msgstr ""

#. type: Plain text
#: ./user-manual.txt:3425
msgid ""
"This section describes the functions and operation of the items in the Main "
"Menu of Subsurface. Several of the items below are links to sections of this "
"manual dealing with the appropriate operations."
msgstr ""

#. type: Title ===
#: ./user-manual.txt:3426
#, no-wrap
msgid "File"
msgstr ""

#. type: Plain text
#: ./user-manual.txt:3429
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."
msgstr ""

#. type: Plain text
#: ./user-manual.txt:3432
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."
msgstr ""

#. type: Plain text
#: ./user-manual.txt:3434
msgid ""
"_Save to cloud storage_ - Save the current dive log to "
"<<S_Cloud_storage,_Cloud storage_>>."
msgstr ""

#. type: Plain text
#: ./user-manual.txt:3435
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."
msgstr ""

#. type: Plain text
#: ./user-manual.txt:3438
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
msgid "<<S_PrintDivelog,_Print_>> - Print the currently open logbook."
msgstr ""

#. type: Plain text
#: ./user-manual.txt:3440
msgid "<<S_Preferences,_Preferences_>> - Set the _Subsurface_ preferences."
msgstr ""

#. type: Plain text
#: ./user-manual.txt:3441
msgid ""
"<<S_FindMovedImages, _Find moved images_>> - If photos taken during dives "
"have been moved to"
msgstr ""

#. type: Plain text
#: ./user-manual.txt:3442
msgid ""
"a different disk or directory, locate them and link them to the appropriate "
"dives."
msgstr ""

#. type: Plain text
#: ./user-manual.txt:3443
msgid ""
"<<S_Configure,_Configure dive computer_>> - Edit the configuration of a dive "
"computer."
msgstr ""

#. type: Plain text
#: ./user-manual.txt:3444
msgid "_Quit_ - Quit _Subsurface_."
msgstr ""

#. type: Title ===
#: ./user-manual.txt:3445
#, no-wrap
msgid "Import"
msgstr ""

#. type: Plain text
#: ./user-manual.txt:3448
msgid ""
"<<S_ImportDiveComputer,_Import from dive computer_>> - Import dive "
"information from a dive computer."
msgstr ""

#. type: Plain text
#: ./user-manual.txt:3450
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
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
msgid ""
"<<S_ImportingDivelogsDe,_Import from Divelogs.de_>> - Import dive "
"information from _www.Divelogs.de_."
msgstr ""

#. type: Title ===
#: ./user-manual.txt:3455
#, no-wrap
msgid "Log"
msgstr ""

#. type: Plain text
#: ./user-manual.txt:3457
msgid ""
"<<S_EnterData,_Add Dive_>> - Manually add a new dive to the *Dive List* "
"panel."
msgstr ""

#. type: Plain text
#: ./user-manual.txt:3458
msgid ""
"_Edit dive_ - Edit a dive of which the profile was entered by hande 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 ""

#. type: Plain text
#: ./user-manual.txt:3460
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
msgid ""
"<<S_CopyComponents,_Copy dive components_>> - By selecting this option, one "
"can copy information from several fields of a dive log onto the clipboard."
msgstr ""

#. type: Plain text
#: ./user-manual.txt:3464
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
msgid ""
"<<S_Renumber,_Renumber_>> - Renumber the dives listed in the *Dive List* "
"panel."
msgstr ""

#. type: Plain text
#: ./user-manual.txt:3468
msgid ""
"<<S_Group,_Auto Group_>> - Group the dives in the *Dive List* panel into "
"dive trips."
msgstr ""

#. type: Plain text
#: ./user-manual.txt:3469
msgid ""
"<<S_DeviceNames,_Edit Device Names_>> - Edit the names of dive computers to "
"facilitate your logs."
msgstr ""

#. type: Plain text
#: ./user-manual.txt:3470
msgid ""
"<<S_Filter,_Filter divelist_>> - Select only some dives, based on specific "
"tags or dive criteria."
msgstr ""

#. type: Title ===
#: ./user-manual.txt:3471
#, no-wrap
msgid "View"
msgstr ""

#. type: Plain text
#: ./user-manual.txt:3474
msgid ""
"<<S_ViewPanels,_All_>> - View the four main _Subsurface_ panels "
"simmultaneously."
msgstr ""

#. type: Plain text
#: ./user-manual.txt:3475
msgid "<<S_ViewPanels,_Dive List_>> - View only the *Dive List* panel."
msgstr ""

#. type: Plain text
#: ./user-manual.txt:3476
msgid "<<S_ViewPanels,_Profile_>> - View only the *Dive Profile* panel."
msgstr ""

#. type: Plain text
#: ./user-manual.txt:3477
msgid "<<S_ViewPanels,_Info_>> - View only the *Notes* panel."
msgstr ""

#. type: Plain text
#: ./user-manual.txt:3478
msgid "<<S_ViewPanels,_Globe_>> - View only the *World Map* panel."
msgstr ""

#. type: Plain text
#: ./user-manual.txt:3480
msgid ""
"_Yearly Statistics_ - Display summary statistics about dives during this and "
"past years."
msgstr ""

#. type: Plain text
#: ./user-manual.txt:3481
msgid ""
"_Prev DC_ - If a single dive was logged from more than one dive computer, "
"switch to data from"
msgstr ""

#. type: Plain text
#: ./user-manual.txt:3482
msgid "previous dive computer."
msgstr ""

#. type: Plain text
#: ./user-manual.txt:3483
msgid "_Next DC_ - Switch to next dive computer."
msgstr ""

#. type: Plain text
#: ./user-manual.txt:3484
msgid "_Full Screen_ - Toggles Full Screen mode."
msgstr ""

#. type: Title ===
#: ./user-manual.txt:3485
#, no-wrap
msgid "Share on"
msgstr ""

#. type: Plain text
#: ./user-manual.txt:3487
msgid ""
"<<S_Facebook,_Facebook_>> - Share the currently selected dive on your "
"Facebook timeline."
msgstr ""

#. type: Title ===
#: ./user-manual.txt:3489
#, no-wrap
msgid "Help"
msgstr ""

#. type: Plain text
#: ./user-manual.txt:3492
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
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
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 "
"diving habits have changed."
msgstr ""

#. type: Plain text
#: ./user-manual.txt:3497
msgid "_User manual_ - Open a window showing this user manual."
msgstr ""

#. type: Title ==
#: ./user-manual.txt:3500
#, no-wrap
msgid ""
"APPENDIX A: Operating system specific information for importing dive "
"information from a dive computer."
msgstr ""

#. type: Title ===
#: ./user-manual.txt:3502
#, 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
#, no-wrap
msgid "images/icons/drivers.jpg"
msgstr ""

#. type: Plain text
#: ./user-manual.txt:3508
msgid ""
"The operating system of the desktop computer needs the appropriate drivers "
"in order to communicate with the dive computer in whichever way the dive "
"computer prefers (e.g. Bluetooth, USB, infra-red)."
msgstr ""

#. type: Plain text
#: ./user-manual.txt:3514
msgid ""
"On Linux users need to have the correct kernel module loaded. Most "
"distributions will do this automatically, so the user does not need to load "
"kernel modules. However, some communication protocols require an additional "
"driver, especially for rarely used technology such as infra-red."
msgstr ""

#. type: Plain text
#: ./user-manual.txt:3518
msgid ""
"On Windows, the OS should offer to download the correct driver once the user "
"connects the dive computer to the USB port and operating system sees the "
"equipment for the first time."
msgstr ""

#. type: Plain text
#: ./user-manual.txt:3525
msgid ""
"On a Mac users sometimes have to manually hunt for the correct driver. For "
"example the correct driver for the Mares Puck devices or any other dive "
"computer using a USB-to-serial interface based on the Silicon Labs CP2101 or "
"similar chip can be found as _Mac_OSX_VCP_Driver.zip_ at the "
"http://www.silabs.com/support/pages/document-library.aspx?p=Interface&f=USB%20Bridges&pn=CP2101[Silicon "
"Labs document and software repository]."
msgstr ""

#. type: Title ===
#: ./user-manual.txt:3527
#, 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
#, no-wrap
msgid "images/icons/usb.jpg"
msgstr ""

#. type: Plain text
#: ./user-manual.txt:3536
msgid ""
"When a user connects the dive computer by using a USB connector, usually "
"_Subsurface_ will either propose a drop down list that contains the correct "
"device name (or mount point for the Uemis Zurich), or it will disable the "
"device select drop down if no device name is needed at all. In the rare "
"cases where this doesn't work, here are some suggestions of ways to find out "
"what the device name is:"
msgstr ""

#. type: Plain text
#: ./user-manual.txt:3541
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
#, no-wrap
msgid "On MacOS:"
msgstr ""

#. type: Plain text
#: ./user-manual.txt:3545
msgid "The drop down box should find all connected dive computers."
msgstr ""

#. type: Block title
#: ./user-manual.txt:3546
#, no-wrap
msgid "On Linux:"
msgstr ""

#. type: Plain text
#: ./user-manual.txt:3549
msgid "There is a definitive way to find the port:"
msgstr ""

#. type: Plain text
#: ./user-manual.txt:3551
msgid "Disconnect the USB cable from the dive computer"
msgstr ""

#. type: Plain text
#: ./user-manual.txt:3552
msgid "Open a terminal"
msgstr ""

#. type: Plain text
#: ./user-manual.txt:3553 ./user-manual.txt:3555
msgid "Type the command: 'dmesg' and press enter"
msgstr ""

#. type: Plain text
#: ./user-manual.txt:3554
msgid "Plug in the USB cable of the dive computer"
msgstr ""

#. type: Plain text
#: ./user-manual.txt:3557
msgid "A message similar to this one should appear:"
msgstr ""

#. type: Plain text
#: ./user-manual.txt:3573
#, no-wrap
msgid ""
"\tusb 2-1.1: new full speed USB device number 14 using ehci_hcd\n"
"\tusbcore: registered new interface driver usbserial\n"
"\tUSB Serial support registered for generic\n"
"\tusbcore: registered new interface driver usbserial_generic\n"
"\tusbserial: USB Serial Driver core\n"
"\tUSB Serial support registered for FTDI USB Serial Device\n"
"\tftdi_sio 2-1.1:1.0: FTDI USB Serial Device converter detected\n"
"\tusb 2-1.1: Detected FT232BM\n"
"\tusb 2-1.1: Number of endpoints 2\n"
"\tusb 2-1.1: Endpoint 1 MaxPacketSize 64\n"
"\tusb 2-1.1: Endpoint 2 MaxPacketSize 64\n"
"\tusb 2-1.1: Setting MaxPacketSize 64\n"
"\tusb 2-1.1: FTDI USB Serial Device converter now attached to ttyUSB3\n"
"\tusbcore: registered new interface driver ftdi_sio\n"
"\tftdi_sio: v1.6.0:USB FTDI Serial Converters Driver\n"
msgstr ""

#. type: Plain text
#: ./user-manual.txt:3578
msgid ""
"The third line from the bottom shows that the FTDI USB adapter is detected "
"and connected to +ttyUSB3+. This information can now be used in the import "
"settings as +/dev/ttyUSB3+ which directs Subsurface to the correct USB port."
msgstr ""

#. type: Plain text
#: ./user-manual.txt:3580
msgid "Ensuring that the user has write permission to the USB serial port:"
msgstr ""

#. type: Plain text
#: ./user-manual.txt:3586
msgid ""
"On Unix-like operating systems the USB ports can only be accessed by users "
"who are members of the +dialout+ group. If one is not root, one may not be a "
"member of that group and will not be able to use the USB port. Let us assume "
"one's username is 'johnB'."
msgstr ""

#. type: Plain text
#: ./user-manual.txt:3590
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
#, no-wrap
msgid ""
"Type: +id johnB+     This lists all the groups that johnB belongs to and\n"
"verifies that\n"
"the appropriate group membership has been created. The +dialout+ group "
"should\n"
"be listed\n"
"among the different IDs.\n"
msgstr ""

#. type: Plain text
#: ./user-manual.txt:3597
#, no-wrap
msgid ""
"Under some circumstances this change takes only effect (eg. on Ubuntu) "
"after\n"
"one logs out and then logs in again.\n"
msgstr ""

#. type: Plain text
#: ./user-manual.txt:3602
msgid ""
"With the appropriate device name (e.g. +dev/ttyUSB3+) and with write "
"permission to the USB port, the dive computer interface can connect and one "
"should be able to import dives."
msgstr ""

#. type: Title ===
#: ./user-manual.txt:3605
#, no-wrap
msgid "Manually setting up Bluetooth enabled devices"
msgstr ""

#. type: Plain text
#: ./user-manual.txt:3612
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 "
"_Subsurface_. Follow these steps:"
msgstr ""

#. type: Plain text
#: ./user-manual.txt:3614
#, no-wrap
msgid ""
"*For the dive computer, after enabling Bluetooth, ensure it is in Upload "
"mode.*\n"
msgstr ""

#. type: Plain text
#: ./user-manual.txt:3618
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 -> "
"Upload Log_ and wait for the _Wait PC_ message."
msgstr ""

#. type: Plain text
#: ./user-manual.txt:3620
#, no-wrap
msgid "*Pair the _Subsurface_ computer with the dive computer.*\n"
msgstr ""

#. type: Plain text
#: ./user-manual.txt:3629
msgid ""
"Bluetooth is most likely already enabled. For pairing with the dive computer "
"choose _Control Panel -> Bluetooth Devices -> Add Wireless Device_.  This "
"should bring up a dialog showing your dive computer (which should be in "
"Bluetooth mode) and allowing pairing. Right click on it and choose "
"_Properties-> COM Ports_ to identify the port used for your dive "
"computer. If there are several ports listed, use the one saying \"Outgoing\" "
"instead of \"Incoming\"."
msgstr ""

#. type: Plain text
#: ./user-manual.txt:3632
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
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
msgid ""
"Click on the Bluetooth symbol in the menu bar and select _Set up Bluetooth "
"Device..._. The dive computer should then show up in the list of "
"devices. Select it and go through the pairing process. This step should only "
"be needed once for initial setup."
msgstr ""

#. type: Plain text
#: ./user-manual.txt:3645
msgid ""
"Once the pairing is completed the correct device is shown in the 'Device or "
"Mount Point' drop-down in the _Subsurface_ *Import* dialog."
msgstr ""

#. type: Title ====
#: ./user-manual.txt:3646
#, no-wrap
msgid "On Linux"
msgstr ""

#. type: Plain text
#: ./user-manual.txt:3654
msgid ""
"Ensure Bluetooth is enabled on the _Subsurface_ computer.  On most common "
"distributions this should be true out of the box and pairing should be "
"straight forward. For instance, Gnome3 shows a Bluetooth icon 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
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 "
"will generally require the command prompt.  It is essentially a three step "
"process."
msgstr ""

#. type: Plain text
#: ./user-manual.txt:3660
msgid "Enable the Bluetooth controller and pair your dive computer"
msgstr ""

#. type: Plain text
#: ./user-manual.txt:3661
msgid "Establish an RFCOMM connection"
msgstr ""

#. type: Title =====
#: ./user-manual.txt:3662 ./user-manual.txt:3802
#, no-wrap
msgid "Download the dives with Subsurface"
msgstr ""

#. type: Plain text
#: ./user-manual.txt:3668
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 "
"'Upload Log'.  The display will read 'Initializing', then 'Wait PC 3:00' and "
"will countdown.  Once the connection is established, the display reads 'Wait "
"CMD ...' and the countdown continues. When downloading the dive from "
"Subsurface, the display reads 'Sending' then 'Sent Dive'."
msgstr ""

#. type: Plain text
#: ./user-manual.txt:3673
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 "
"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:"
msgstr ""

#. type: Plain text
#: ./user-manual.txt:3675
msgid "+sudo usermod -a -G dialout username+"
msgstr ""

#. type: Plain text
#: ./user-manual.txt:3677
msgid "Then log out and log in for the change to take effect."
msgstr ""

#. type: Title =====
#: ./user-manual.txt:3678
#, no-wrap
msgid "Enabling the Bluetooth controller and pairing your dive computer"
msgstr ""

#. type: Plain text
#: ./user-manual.txt:3684
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 "
"computer to upload mode, click the Bluetooth icon in the system tray and "
"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 \t00:11:22:33:44:55."
msgstr ""

#. type: Plain text
#: ./user-manual.txt:3687
msgid ""
"If the graphical method didn'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
#, no-wrap
msgid ""
"\t$ hciconfig\n"
"\thci0:\tType: BR/EDR  Bus: USB\n"
"\t\tBD Address: 01:23:45:67:89:AB  ACL MTU: 310:10  SCO MTU: 64:8\n"
"\t\t*DOWN*\n"
"\t\tRX bytes:504 acl:0 sco:0 events:22 errors:0\n"
"\t\tTX bytes:92 acl:0 sco:0 commands:21 errors:0\n"
msgstr ""

#. type: Plain text
#: ./user-manual.txt:3699
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 "
"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:"
msgstr ""

#. type: Plain text
#: ./user-manual.txt:3707
#, no-wrap
msgid ""
"\tsudo hciconfig hci0 up auth+  (enter password when prompted)\n"
"\thciconfig\n"
"\thci0:  Type: BR/EDR  Bus: USB\n"
"\t\tBD Address: 01:23:45:67:89:AB  ACL MTU: 310:10  SCO MTU: 64:8\n"
"\t\t*UP RUNNING PSCAN AUTH*\n"
"\t\tRX bytes:1026 acl:0 sco:0 events:47 errors:0\n"
"\t\tTX bytes:449 acl:0 sco:0 commands:46 errors:0\n"
msgstr ""

#. type: Plain text
#: ./user-manual.txt:3709
msgid "Check that the status now includes +'UP', 'RUNNING' AND 'AUTH'+."
msgstr ""

#. type: Plain text
#: ./user-manual.txt:3711
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
#, no-wrap
msgid "\tsudo hciconfig hci1 down\n"
msgstr ""

#. type: Plain text
#: ./user-manual.txt:3716
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 "
"bring up its own command prompt."
msgstr ""

#. type: Plain text
#: ./user-manual.txt:3737
#, no-wrap
msgid ""
"\tbluetoothctl\n"
"\t[NEW] Controller 01:23:45:67:89:AB localhost.localdomain [default]\n"
"\t[bluetooth]# agent on\n"
"\tAgent registered\n"
"\t[bluetooth]# default-agent\n"
"\tDefault agent request successful\n"
"\t[bluetooth]# scan on                        <----now set your dive "
"computer to upload mode\n"
"\tDiscovery started\n"
"\t[CHG] Controller 01:23:45:67:89:AB Discovering: yes\n"
"\t[NEW] Device 00:11:22:33:44:55 Petrel\n"
"\t[bluetooth]# trust 00:11:22:33:44:55        <----you can use the tab key "
"to autocomplete the MAC address\n"
"\t[CHG] Device 00:11:22:33:44:55 Trusted: yes\n"
"\tChanging 00:11:22:33:44:55 trust succeeded\n"
"\t[bluetooth]# pair 00:11:22:33:44:55\n"
"\tAttempting to pair with 00:11:22:33:44:55\n"
"\t[CHG] Device 00:11:22:33:44:55 Connected: yes\n"
"\t[CHG] Device 00:11:22:33:44:55 UUIDs: "
"00001101-0000-1000-8000-0089abc12345\n"
"\t[CHG] Device 00:11:22:33:44:55 Paired: yes\n"
"\tPairing successful\n"
"\t[CHG] Device 00:11:22:33:44:55 Connected: no\n"
msgstr ""

#. type: Plain text
#: ./user-manual.txt:3740
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
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-agent+ or just +simple-agent+."
msgstr ""

#. type: Plain text
#: ./user-manual.txt:3748
#, no-wrap
msgid ""
"\thcitool -i hci0 scanning\n"
"\tScanning ...\n"
"\t\t00:11:22:33:44:55       Petrel\n"
"\t\tbluez-simple-agent hci0 00:11:22:33:44:55\n"
msgstr ""

#. type: Plain text
#: ./user-manual.txt:3750
msgid "Once ther dive computer is pired, set up the RFCOMM connection"
msgstr ""

#. type: Title =====
#: ./user-manual.txt:3751
#, no-wrap
msgid "Establishing the RFCOMM connection"
msgstr ""

#. type: Plain text
#: ./user-manual.txt:3754
msgid "The command to establish an RFCOMM connection is:"
msgstr ""

#. type: Plain text
#: ./user-manual.txt:3756
msgid "+sudo rfcomm -i <controller> connect <dev> <bdaddr> [channel]+"
msgstr ""

#. type: Plain text
#: ./user-manual.txt:3758
msgid "+<controller>+ is the Bluetooth controller, +hci0+."
msgstr ""

#. type: Plain text
#: ./user-manual.txt:3759
msgid "+<dev>+ is the RFCOMM device file, +rfcomm0+"
msgstr ""

#. type: Plain text
#: ./user-manual.txt:3760
msgid "+<bdaddr>+ is the dive computer's MAC address, +00:11:22:33:44:55+"
msgstr ""

#. type: Plain text
#: ./user-manual.txt:3761
msgid "+[channel]+ is the dive computer's Bluetooth channel we need to connect to."
msgstr ""

#. type: Plain text
#: ./user-manual.txt:3764
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
msgid "_Shearwater Petrel 1_: channel 1"
msgstr ""

#. type: Plain text
#: ./user-manual.txt:3767
msgid "_Shearwater Petrel 2_: channel 5"
msgstr ""

#. type: Plain text
#: ./user-manual.txt:3768
msgid "_Shearwater Nerd_: channel 5"
msgstr ""

#. type: Plain text
#: ./user-manual.txt:3769
msgid "_Heinrichs-Weikamp OSTC Sport_: channel 1"
msgstr ""

#. type: Plain text
#: ./user-manual.txt:3771
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
#, 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
msgid "This gives the response:"
msgstr ""

#. type: Plain text
#: ./user-manual.txt:3778
#, no-wrap
msgid ""
"\tConnected /dev/rfcomm0 to 00:11:22:33:44:55 on channel 5\n"
"\tPress CTRL-C for hangup\n"
msgstr ""

#. type: Plain text
#: ./user-manual.txt:3780
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
#, no-wrap
msgid ""
"\tsudo rfcomm -i hci0 connect rfcomm0 00:11:22:33:44:55   (enter a password, "
"probably 0000, when prompted)\n"
"\tConnected /dev/rfcomm0 to 00:11:22:33:44:55 on channel 1\n"
"\tPress CTRL-C for hangup\n"
msgstr ""

#. type: Plain text
#: ./user-manual.txt:3788
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 "
"determine the appropriate channel. The output below is for a _Shearwater "
"Petrel 2_."
msgstr ""

#. type: Plain text
#: ./user-manual.txt:3798
#, no-wrap
msgid ""
"\tsdptool -i hci0 records 00:11:22:33:44:55\n"
"\tService Name: Serial Port\n"
"\tService RecHandle: 0x10000\n"
"\tService Class ID List:\n"
"\t\t\"Serial Port\" (0x1101)\n"
"\t\tProtocol Descriptor List:\n"
"\t\t\"L2CAP\" (0x0100)\n"
"\t\t\"RFCOMM\" (0x0003)\n"
"\t\tChannel: 5\n"
msgstr ""

#. type: Plain text
#: ./user-manual.txt:3801
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 "
"forum or the developer mailing list _subsurface@subsurface-divelog.org_."
msgstr ""

#. type: Plain text
#: ./user-manual.txt:3804
msgid ""
"After establishing the RFCOMM connection and while the dive computer's "
"upload mode countdown is still running, go to_Subsurface_, select "
"_Import->Import from dive computer_ and enter appropriate Vendor "
"(e.g. _Shearwater_), Dive Computer (_Petrel_), Device or Mount Point "
"(_/dev/rfcomm0_) and click _Download_."
msgstr ""

#. type: Title ==
#: ./user-manual.txt:3810
#, no-wrap
msgid "APPENDIX B: Dive Computer specific information for importing dive data."
msgstr ""

#. type: Title ===
#: ./user-manual.txt:3813
#, no-wrap
msgid "Importing from Uemis Zurich"
msgstr ""

#. type: Named 'icon' AttributeList argument for style 'icon'
#: ./user-manual.txt:3815
#, no-wrap
msgid "images/icons/iumis.jpg"
msgstr ""

#. type: Plain text
#: ./user-manual.txt:3831
msgid ""
"_Subsurface_ downloads the information stored on the SDA (the built-in file "
"system of the Uemis) including information about dive spots and "
"equipment. Buddy information is not yet downloadable.  Things are very "
"similar to a normal USB-connected dive computer (the Uemis is one of those "
"that recharge when connected to the USB port).  The main difference is that "
"one does not enter a device name, but instead the location where the "
"UEMISSDA file system is mounted once connected to the dive computer. On "
"Windows this is a drive letter ( often 'E:' or 'F:'), on a Mac this is "
"'/Volumes/UEMISSDA' and on Linux systems this differs depending on the "
"distribution. On Fedora it usually is "
"'/var/run/media/<your_username>/UEMISSDA'. In all cases _Subsurface_ should "
"suggest the correct location in the drop down list."
msgstr ""

#. type: Plain text
#: ./user-manual.txt:3846
msgid ""
"After selecting the above device name, download the dives from the Uemis "
"Zurich. One technical issue with the Uemis Zurich download implementation "
"(this is a Uemis firmware limitation, not a _Subsurface_ issue) is that one "
"cannot download more than about 40-50 dives without running out of memory on "
"the SDA. This will usually only happen the very first time one downloads "
"dives from the Uemis Zurich.  Normally when downloading at the end of a day "
"or even after a dive trip, the capacity is sufficient. If _Subsurface_ "
"displays an error that the dive computer ran out of space the solution is "
"straight forward.  Disconnect the SDA, turn it off and on again, and "
"reconnect it. You can now retry (or start a new download session) and the "
"download will continue where it stopped previously. One may have to do this "
"more than once, depending on how many dives are stored on the dive computer."
msgstr ""

#. type: Title ===
#: ./user-manual.txt:3848
#, no-wrap
msgid "Importing from Uwatec Galileo"
msgstr ""

#. type: Named 'icon' AttributeList argument for style 'icon'
#: ./user-manual.txt:3850
#, no-wrap
msgid "images/icons/Galileo.jpg"
msgstr ""

#. type: Plain text
#: ./user-manual.txt:3865
msgid ""
"The Uwatec Galileo dive computers use infra red (IrDA) communication between "
"the dive computer and Subsurface. The Uwatec hardware uses a USB dongle "
"based on the serial infra-red (SIR) protocol and the MSC7780 IrDA controller "
"manufactured by MosChip and marketed by Scubapro and some electronics "
"companies.  Under Linux, the kernel already provides for communication using "
"the IrDA protocol. However, the user additionally needs to load a driver for "
"the IrDA interface with the dive computer. The easiest way is to load the "
"*irda-tools* package from the "
"http://irda.sourceforge.net/docs/startirda.html[Linux IrDA Project].  After "
"the installation of the irda-tools, the *root user* can specify a device "
"name from the console as follows: +irattach irda0+"
msgstr ""

#. type: Plain text
#: ./user-manual.txt:3868
msgid ""
"After executing this command, Subsurface will recognise the Galileo dive "
"computer and download dive information."
msgstr ""

#. type: Plain text
#: ./user-manual.txt:3874
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."
msgstr ""

#. type: Plain text
#: ./user-manual.txt:3877
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
#, no-wrap
msgid "Importing from Heinrichs Weikamp DR5"
msgstr ""

#. type: Named 'icon' AttributeList argument for style 'icon'
#: ./user-manual.txt:3881
#, no-wrap
msgid "images/icons/HW_DR5.jpg"
msgstr ""

#. type: Plain text
#: ./user-manual.txt:3891
msgid ""
"When mounted as a USB drive the Heinrichs Weikamp DR5 saves a single UDDF "
"file for every dive.  Mark all the dives you'd like to import or open.  "
"Note: The DR5 does not seem to store gradient factors nor deco information, "
"so for _Subsurface_ it is not possible to display them. Adjust the gradient "
"factors in the _Graph Settings_ in _Subsurface_ to generate a deco overlay "
"in the _Subsurface_ *Dive Profile* panel but please note that the deco "
"calculated by _Subsurface_ will most likely differ from the one displayed on "
"the DR5."
msgstr ""

#. type: Title ===
#: ./user-manual.txt:3894
#, no-wrap
msgid "Importing from xDEEP BLACK"
msgstr ""

#. type: Named 'icon' AttributeList argument for style 'icon'
#: ./user-manual.txt:3896
#, no-wrap
msgid "images/icons/HW_xdeepblack.jpg"
msgstr ""

#. type: Plain text
#: ./user-manual.txt:3905
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 "
"available in LOGBOOK directory.  Note: The xDEEP BLACK saves NDL time but "
"does not seem to store gradient factors nor deco information, so for "
"_Subsurface_ it is not possible to display them. Adjust the gradient factors "
"in the _Graph Settings_ in _Subsurface_ to generate a deco overlay in the "
"_Subsurface_ *Dive Profile* panel but please note that the deco calculated "
"by _Subsurface_ will most likely differ from the one displayed on the xDEEP "
"BLACK."
msgstr ""

#. type: Title ===
#: ./user-manual.txt:3907
#, no-wrap
msgid "Importing from Shearwater Predator/Petrel/Nerd using Bluetooth"
msgstr ""

#. type: Named 'icon' AttributeList argument for style 'icon'
#: ./user-manual.txt:3909
#, no-wrap
msgid "images/icons/predator.jpg"
msgstr ""

#. type: Plain text
#: ./user-manual.txt:3912
msgid ""
"Specific instructions for downloading dives using Bluetooth are given in the "
"section above, <<S_Bluetooth,_Connecting Subsurface to a Bluetooth-enabled "
"dive computer_>>."
msgstr ""

#. type: Title ===
#: ./user-manual.txt:3914
#, no-wrap
msgid "Importing from Poseidon MkVI Discovery"
msgstr ""

#. type: Named 'icon' AttributeList argument for style 'icon'
#: ./user-manual.txt:3916
#, no-wrap
msgid "images/MkVI.jpeg"
msgstr ""

#. type: Plain text
#: ./user-manual.txt:3924
msgid ""
"Download of dive logs from the MkVI is performed using a custom "
"communications adapter and the _Poseidon PC Configuration Software_, "
"obtained when purchasing the MKVI equipment. The latter is a Windows "
"application allowing configuration of equipment and storage of dive "
"logs. Communication between dive computer and desktop computer utilises the "
"IrDA infra-red protocol. Only data for one dive can be downloaded at a time, "
"comprising three files:"
msgstr ""

#. type: Plain text
#: ./user-manual.txt:3927
msgid ""
"Setup configuration for the dive and key dive parameters (file with a .txt "
"extension)"
msgstr ""

#. type: Plain text
#: ./user-manual.txt:3928
msgid "Dive log details (file with a .csv extension)"
msgstr ""

#. type: Plain text
#: ./user-manual.txt:3930
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
msgid ""
"_Subsurface_ accesses the .txt and the .csv files to obtain dive log "
"information."
msgstr ""

#. type: Title ===
#: ./user-manual.txt:3934
#, no-wrap
msgid "Importing from APD Inspiration/Evolution CCR"
msgstr ""

#. type: Named 'icon' AttributeList argument for style 'icon'
#: ./user-manual.txt:3936
#, no-wrap
msgid "images/APDComputer.jpg"
msgstr ""

#. type: Plain text
#: ./user-manual.txt:3944
msgid ""
"The dive logs of an APD Inspiration or similar CCR dive computer are "
"downloaded using a communications adapter and _AP Communicator_, obtained "
"when purchasing the equipment. The dive logs can be viewed using the _AP Log "
"Viewer_, within Windows or Mac/OS. However, APD logs can be viewed and "
"managed from within _Subsurface_ (together with dives using many other types "
"of dive computer). The APD inspiration dive logs are imported into "
"_Subsurface_ as follows:"
msgstr ""

#. type: Plain text
#: ./user-manual.txt:3946
msgid "Download the dive using _AP Communicator_."
msgstr ""

#. type: Plain text
#: ./user-manual.txt:3947
msgid "Open a dive within the _AP Log Viewer_."
msgstr ""

#. type: Plain text
#: ./user-manual.txt:3948
msgid "Select the tab at the top of the screen, entitled \"_Data_\"."
msgstr ""

#. type: Plain text
#: ./user-manual.txt:3949
msgid ""
"With the raw dive log data show on the screen, click on \"_Copy to "
"Clipboard_\"."
msgstr ""

#. type: Plain text
#: ./user-manual.txt:3950
msgid "Open a text editor, e.g. Notepad (Windows) or TextWrangler (Mac)."
msgstr ""

#. type: Plain text
#: ./user-manual.txt:3952
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
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
msgid ""
"In the dropdown list towards the bottom right of the dialogue (labled "
"'Filter:'), select \"APD log viewer\"."
msgstr ""

#. type: Plain text
#: ./user-manual.txt:3957
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]."
msgstr ""

#. type: Target for macro image
#: ./user-manual.txt:3958
#, no-wrap
msgid "images/APD_CSVimportF22.jpg"
msgstr ""

#. type: Plain text
#: ./user-manual.txt:3966
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)"
msgstr ""

#. type: Plain text
#: ./user-manual.txt:3967
msgid "Click the _Ok_ button at the bottom of the import panel."
msgstr ""

#. type: Plain text
#: ./user-manual.txt:3972
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."
msgstr ""

#. type: Title ==
#: ./user-manual.txt:3973
#, no-wrap
msgid "APPENDIX C: Exporting Dive log information from external dive log software."
msgstr ""

#. type: Plain text
#: ./user-manual.txt:3982
msgid ""
"The import of dive log data from external dive log software is mostly "
"performed using the dialogue found by selecting _Import_ from the Main Menu, "
"then clicking on _Import Log Files_. This is a single-step process, more "
"information about which can be found xref:Unified_import[here.] However, in "
"some cases, a two-step process may be required:"
msgstr ""

#. type: Plain text
#: ./user-manual.txt:3984
msgid "Export the foreign dive log data to format that is accessible from"
msgstr ""

#. type: Plain text
#: ./user-manual.txt:3985
msgid "_Subsurface_."
msgstr ""

#. type: Plain text
#: ./user-manual.txt:3986
msgid "Import the accessible dive log data into _Subsurface_."
msgstr ""

#. type: Plain text
#: ./user-manual.txt:3990
msgid ""
"This appendix provides some information about approaches to export dive log "
"data from foreign dive log software. The procedures below mostly apply to "
"Linux and/or Windows."
msgstr ""

#. type: Title ===
#: ./user-manual.txt:3992
#, no-wrap
msgid "Exporting from *Suunto Divemanager (DM3, DM4 or DM5)*"
msgstr ""

#. type: Named 'icon' AttributeList argument for style 'icon'
#: ./user-manual.txt:3993
#, no-wrap
msgid "images/icons/suuntologo.jpg"
msgstr ""

#. type: Plain text
#: ./user-manual.txt:4000
msgid ""
"DiveManager is a MS Windows application for Suunto dive computers.  "
"Divemanager 3 (DM3) is an older version of the Suunto software. More recent "
"Suunto dive computers use Divemanager version 4 or 5 (DM4 or DM5). The "
"different versions of Divemanager use different methods and different file "
"naming conventions to export dive log data."
msgstr ""

#. type: Plain text
#: ./user-manual.txt:4002
#, no-wrap
msgid "*Divemanager 3 (DM3):*\n"
msgstr ""

#. type: Plain text
#: ./user-manual.txt:4004
msgid "Start 'Suunto Divemanager 3' and log in with the name containing the logs"
msgstr ""

#. type: Plain text
#: ./user-manual.txt:4005
msgid "Do not start the import wizard to import dives from the dive computer."
msgstr ""

#. type: Plain text
#: ./user-manual.txt:4007
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
msgid "Within the list of dives, select the dives you would like to import later:"
msgstr ""

#. type: Plain text
#: ./user-manual.txt:4009
msgid "To select certain dives: hold 'ctrl' and click the dive"
msgstr ""

#. type: Plain text
#: ./user-manual.txt:4011
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
msgid "With the dives marked, use the program menu _File -> Export_"
msgstr ""

#. type: Plain text
#: ./user-manual.txt:4013
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
msgid "Click the browse button next to the field Export Path"
msgstr ""

#. type: Plain text
#: ./user-manual.txt:4016
#, no-wrap
msgid ""
"** A file-manager like window pops up\n"
"** Navigate to the directory for storing the\n"
msgstr ""

#. type: Plain text
#: ./user-manual.txt:4017
#, no-wrap
msgid "Divelog.SDE file\n"
msgstr ""

#. type: Plain text
#: ./user-manual.txt:4019
#, no-wrap
msgid ""
"** Optionally change the name of the file for saving\n"
"** Click 'Save'\n"
msgstr ""

#. type: Plain text
#: ./user-manual.txt:4020
#, no-wrap
msgid "Back in the Export pop-up, press the button 'Export'\n"
msgstr ""

#. type: Plain text
#: ./user-manual.txt:4021
#, no-wrap
msgid "The dives are now exported to the file Divelog.SDE.\n"
msgstr ""

#. type: Plain text
#: ./user-manual.txt:4023
#, no-wrap
msgid "*Divemanager 4 (DM4) and Divemanager 5 (DM5):*\n"
msgstr ""

#. type: Plain text
#: ./user-manual.txt:4028
msgid ""
"DM4 and DM5 use identical mechanisms for exporting dive logs.  To export a "
"divelog from Divemanager one needs to locate the DM4/DM5 database where the "
"dives are stored. the user can either look for the original database or make "
"a backup of the dives. Both methods are described here."
msgstr ""

#. type: Plain text
#: ./user-manual.txt:4030
msgid "Locating the Suunto DM4 (or DM5) database:"
msgstr ""

#. type: Plain text
#: ./user-manual.txt:4032 ./user-manual.txt:4041
msgid "Start Suunto DM4/DM5"
msgstr ""

#. type: Plain text
#: ./user-manual.txt:4033
msgid "Select 'Help -> About'"
msgstr ""

#. type: Plain text
#: ./user-manual.txt:4034
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 ""

#. type: Plain text
#: ./user-manual.txt:4036
msgid "Paste the address to the path box at the top of the File Explorer"
msgstr ""

#. type: Plain text
#: ./user-manual.txt:4037
msgid "The database is called DM4.db or DM5.db"
msgstr ""

#. type: Plain text
#: ./user-manual.txt:4039
msgid "Making a backup copy of the Suunto DM4/DM5 database:"
msgstr ""

#. type: Plain text
#: ./user-manual.txt:4042
msgid "Select 'File - Create backup'"
msgstr ""

#. type: Plain text
#: ./user-manual.txt:4044
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
msgid "Click 'Save'"
msgstr ""

#. type: Plain text
#: ./user-manual.txt:4046
msgid "The dives are now exported to the file DM4.bak (or DM5.bak)"
msgstr ""

#. type: Title ===
#: ./user-manual.txt:4048
#, no-wrap
msgid "Exporting from Atomic Logbook"
msgstr ""

#. type: Named 'icon' AttributeList argument for style 'icon'
#: ./user-manual.txt:4051
#, no-wrap
msgid "images/icons/atomiclogo.jpg"
msgstr ""

#. type: Plain text
#: ./user-manual.txt:4058
msgid ""
"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."
msgstr ""

#. type: Title ===
#: ./user-manual.txt:4060
#, no-wrap
msgid "Exporting from Mares Dive Organiser V2.1"
msgstr ""

#. type: Named 'icon' AttributeList argument for style 'icon'
#: ./user-manual.txt:4063
#, no-wrap
msgid "images/icons/mareslogo.jpg"
msgstr ""

#. type: Plain text
#: ./user-manual.txt:4071
msgid ""
"Mares Dive Organiser is a Windows application. The dive log is kept as a "
"Microsoft SQL Compact Edition database with a '.sdf' filename extension. The "
"database includes all Dive Organiser-registered divers on the particular "
"computer and all Mares dive computers used. The safest way to obtain a copy "
"of the dive database is to export the information to another compatible "
"format which can be imported into _Subsurface_."
msgstr ""

#. type: Plain text
#: ./user-manual.txt:4076
msgid ""
"Within Dive Organiser, select _Database -> Backup_ from the main menu and "
"back up the database to the desk top.  This creates a zipped file "
"DiveOrganiserxxxxx.dbf."
msgstr ""

#. type: Plain text
#: ./user-manual.txt:4079
msgid ""
"Rename the file to DiveOrganiserxxxxx.zip. Inside the zipped directory is a "
"file _DiveOrganiser.sdf_."
msgstr ""

#. type: Plain text
#: ./user-manual.txt:4080
msgid "Extract the _.sdf_ file from the zipped folder to your Desktop."
msgstr ""

#. type: Plain text
#: ./user-manual.txt:4081
msgid "The password for accessing the .zip file is _mares_."
msgstr ""

#. type: Title ===
#: ./user-manual.txt:4083
#, no-wrap
msgid "Exporting from *DivingLog 5.0 and 6.0*"
msgstr ""

#. type: Named 'icon' AttributeList argument for style 'icon'
#: ./user-manual.txt:4085
#, no-wrap
msgid "images/icons/divingloglogo.jpg"
msgstr ""

#. type: Plain text
#: ./user-manual.txt:4092
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."
msgstr ""

#. type: Plain text
#: ./user-manual.txt:4094
msgid "To transfer all files from DivingLog to Subsurface, do the following:"
msgstr ""

#. type: Plain text
#: ./user-manual.txt:4096
msgid "In DivingLog open the 'File -> Export -> SQLite' menu"
msgstr ""

#. type: Plain text
#: ./user-manual.txt:4097
msgid "Select 'Settings' button"
msgstr ""

#. type: Plain text
#: ./user-manual.txt:4098
msgid "Set the 'RTF2Plaintext' to 'true'"
msgstr ""

#. type: Plain text
#: ./user-manual.txt:4099
msgid "Close the Settings dialog"
msgstr ""

#. type: Plain text
#: ./user-manual.txt:4100
msgid "Click 'Export' button and select the filename"
msgstr ""

#. type: Plain text
#: ./user-manual.txt:4104
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."
msgstr ""

#. type: Title ==
#: ./user-manual.txt:4105
#, no-wrap
msgid "APPENDIX D: Exporting a spreadsheet to CSV format"
msgstr ""

#. type: Plain text
#: ./user-manual.txt:4115
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."
msgstr ""

#. 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:"
msgstr ""

#. type: Plain text
#: ./user-manual.txt:4123
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
msgid "Duration: the format should be minutes:seconds."
msgstr ""

#. type: Plain text
#: ./user-manual.txt:4125
msgid ""
"Unit system: only one unit system should be used (i.e., no mixture between "
"imperial and metric units)"
msgstr ""

#. type: Plain text
#: ./user-manual.txt:4126
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"
msgstr ""

#. type: Title ===
#: ./user-manual.txt:4128
#, no-wrap
msgid "_LibreOffice Calc_ and _OpenOffice Calc_"
msgstr ""

#. type: Plain text
#: ./user-manual.txt:4132
msgid ""
"These are open source spreadsheet applications forming parts of larger open "
"source office suite applications. The user interaction with _LibreOffice_ "
"and _OpenOffice_ is very similar.  In Libreoffice Calc the time format "
"should be set to minutes:seconds - [mm]:ss and dates should be set to one "
"of: yyyy-mm-dd, dd.mm.yyyy, mm/dd/yyyy. A typical dive log may look like "
"this:"
msgstr ""

#. type: Target for macro image
#: ./user-manual.txt:4133
#, no-wrap
msgid "images/LOffice_spreadsheetdata.jpg"
msgstr ""

#. type: Plain text
#: ./user-manual.txt:4136
msgid ""
"To export the data as a .CSV file from within LibreOffice click _File -> "
"Save As_. On the dialogue that comes up, select the _Text CSV (.csv)_ as the "
"file type and select the option _Edit filter settings_."
msgstr ""

#. type: Target for macro image
#: ./user-manual.txt:4137
#, no-wrap
msgid "images/LOffice_save_as_options.jpg"
msgstr ""

#. type: Plain text
#: ./user-manual.txt:4140
msgid ""
"After selecting _Save_, select the appropriate field delimiter (choose _Tab_ "
"to prevent conflicts with the comma when using this as a decimal point), "
"then select _OK_."
msgstr ""

#. type: Target for macro image
#: ./user-manual.txt:4141
#, no-wrap
msgid "images/LOffice_field_options.jpg"
msgstr ""

#. type: Plain text
#: ./user-manual.txt:4144
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]."
msgstr ""

#. type: Title ===
#: ./user-manual.txt:4145
#, no-wrap
msgid "Microsoft _Excel_"
msgstr ""

#. type: Plain text
#: ./user-manual.txt:4151
msgid ""
"The field delimiter (called \"_list separator_\" in Microsoft manuals) is "
"not accessible from within _Excel_ and needs to be set through the "
"_Microsoft Control Panel_. After changing the separator character, all "
"software on the Windows machine use the new character as a separator.  One "
"can change the character back to the default character by following the same "
"procedure, outlined below."
msgstr ""

#. type: Plain text
#: ./user-manual.txt:4153
msgid ""
"In Microsoft Windows, click the *Start* button, and then select _Control "
"Panel_ from the list on the right-hand side."
msgstr ""

#. type: Plain text
#: ./user-manual.txt:4154
msgid "Open the _Regional and Language Options_ dialog box."
msgstr ""

#. type: Plain text
#: ./user-manual.txt:4157
msgid ""
"Do one of the following: ** In Windows 7, click the _Formats_ tab, and then "
"click _Customize this format_.  ** In Windows XP, click the _Regional "
"Options_ tab, and then click _Customize_."
msgstr ""

#. type: Plain text
#: ./user-manual.txt:4158
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
msgid "Click _OK_ twice."
msgstr ""

#. type: Plain text
#: ./user-manual.txt:4161
msgid "Below is an image of the _Control Panel_:"
msgstr ""

#. type: Target for macro image
#: ./user-manual.txt:4162
#, no-wrap
msgid "images/Win_SaveCSV2.jpg"
msgstr ""

#. type: Plain text
#: ./user-manual.txt:4165
msgid "To export the dive log in CSV format:"
msgstr ""

#. type: Plain text
#: ./user-manual.txt:4167
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
#, no-wrap
msgid "images/Win_SaveCSV1.jpg"
msgstr ""

#. type: Plain text
#: ./user-manual.txt:4171
msgid ""
"Click on the left-hand part of the _Save as_ option, NOT on the arrow on the "
"right-hand. This brings up a dialogue for saving the spreadsheet in an "
"alternative format. From the dropdown list at the bottom of the dialogue, "
"marked _Save as Type:_, select _CSV(Comma delimited) (*.CSV)_. Ensure that "
"the appropriate folder has been selected to save the CSV file into."
msgstr ""

#. type: Target for macro image
#: ./user-manual.txt:4172
#, no-wrap
msgid "images/Win_SaveCSV3.jpg"
msgstr ""

#. type: Plain text
#: ./user-manual.txt:4175
msgid ""
"Select the _Save_ button. The CSV-formatted file is saved into the folder "
"that was selected. One can double check the .CSV file by opening it with a "
"text editor, and then import the dive data as explained on the section "
"xref:S_ImportingCSVDives[Importing CSV dives]."
msgstr ""

#. type: Title ==
#: ./user-manual.txt:4177
#, no-wrap
msgid "APPENDIX E: Writing a custom print template"
msgstr ""

#. type: Plain text
#: ./user-manual.txt:4182
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_."
msgstr ""

#. type: Plain text
#: ./user-manual.txt:4184
msgid "Templates are accessed using the print dialogue (see image *B* below)."
msgstr ""

#. type: Plain text
#: ./user-manual.txt:4192
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_."
msgstr ""

#. type: Plain text
#: ./user-manual.txt:4194
msgid "The Edit Panel comprises three tabs:"
msgstr ""

#. type: Target for macro image
#: ./user-manual.txt:4195
#, no-wrap
msgid "images/Template1_f22.jpg"
msgstr ""

#. type: Plain text
#: ./user-manual.txt:4199
msgid ""
"The _Style_ tab (image *A* 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."
msgstr ""

#. type: Plain text
#: ./user-manual.txt:4203
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 "
"components of the dive log printout."
msgstr ""

#. type: Plain text
#: ./user-manual.txt:4212
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."
msgstr ""

#. type: Target for macro image
#: ./user-manual.txt:4213
#, no-wrap
msgid "images/Template2_f22.jpg"
msgstr ""

#. type: Plain text
#: ./user-manual.txt:4217
msgid ""
"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 _Export_ button in "
"the print dialogue to save the new template using a new template name."
msgstr ""

#. type: Plain text
#: ./user-manual.txt:4219
msgid ""
"To write a custom template the following elements must exist so that the "
"template will be correctly handled and rendered."
msgstr ""

#. type: Title ===
#: ./user-manual.txt:4220
#, no-wrap
msgid "Main dive loop"
msgstr ""

#. type: Plain text
#: ./user-manual.txt:4222
msgid ""
"_Subsurface_ exports a dive list called (*dives*) to the _Grantlee_ "
"backend. 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
#, no-wrap
msgid "template.html"
msgstr ""

#. type: delimited block .
#: ./user-manual.txt:4228
#, no-wrap
msgid ""
"\t{% for dive in dives %}\n"
"\t\t<h1> {{ dive.number }} </h1>\n"
"\t{% endfor %}\n"
msgstr ""

#. type: Block title
#: ./user-manual.txt:4230 ./user-manual.txt:4282 ./user-manual.txt:4301
#, no-wrap
msgid "output.html"
msgstr ""

#. type: delimited block .
#: ./user-manual.txt:4235
#, no-wrap
msgid ""
"\t<h1> 1 </h1>\n"
"\t<h1> 2 </h1>\n"
"\t<h1> 3 </h1>\n"
msgstr ""

#. type: Plain text
#: ./user-manual.txt:4238
msgid ""
"Additional information about _Grantlee_ can be found "
"http://www.grantlee.org/apidox/for_themers.html[here]"
msgstr ""

#. type: Title ===
#: ./user-manual.txt:4239
#, no-wrap
msgid "Grantlee exported variables"
msgstr ""

#. type: Plain text
#: ./user-manual.txt:4241
msgid "Only a subset of the dive data is exported:"
msgstr ""

#. type: delimited block |
#: ./user-manual.txt:4259
#, 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"
"|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"
"|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
msgid ""
"_Subsurface_ also exports *template_options* data. This data must be used as "
"_CSS_ values to provide a dynamically editable template. The exported data "
"is shown in the following table:"
msgstr ""

#. type: delimited block |
#: ./user-manual.txt:4275
#, no-wrap
msgid ""
"|*Name*|*Description*\n"
"|font| (*string*) font family\n"
"|borderwidth| (*int*) border-width value dynamically calculated as 0.1% of "
"the page width with minimum value of 1px\n"
"|font_size| (*double*) size of fonts in vw, ranges between 1.0 and 2.0\n"
"|line_spacing| (*double*) distance between text lines, ranges between 1.0 "
"and 3.0\n"
"|color1| (*string*) background color\n"
"|color2| (*string*) primary table cell color\n"
"|color3| (*string*) secondary table cell color\n"
"|color4| (*string*) primary text color\n"
"|color5| (*string*) secondary text color\n"
"|color6| (*string*) border colors\n"
msgstr ""

#. type: delimited block .
#: ./user-manual.txt:4280
#, no-wrap
msgid "\tborder-width: {{ template_options.borderwidth }}px;\n"
msgstr ""

#. type: delimited block .
#: ./user-manual.txt:4285
#, no-wrap
msgid "\tborder-width: 3px;\n"
msgstr ""

#. type: Plain text
#: ./user-manual.txt:4288
msgid ""
"Another variable that _Subsurface_ exports is *print_options*. This variable "
"contains a single member:"
msgstr ""

#. type: delimited block |
#: ./user-manual.txt:4291
#, no-wrap
msgid ""
"|*Name*|*Description*\n"
"|grayscale | Use _CSS_ filters to convert the page into grayscale (should be "
"added to body style to enable printing grayscale prints)\n"
msgstr ""

#. type: delimited block .
#: ./user-manual.txt:4299
#, no-wrap
msgid ""
"\tbody {\n"
"\t\t{{ print_options.grayscale }};\n"
"\t}\n"
msgstr ""

#. type: delimited block .
#: ./user-manual.txt:4306
#, no-wrap
msgid ""
"\tbody {\n"
"\t\t-webkit-filter: grayscale(100%);\n"
"\t}\n"
msgstr ""

#. type: Title ===
#: ./user-manual.txt:4308
#, no-wrap
msgid "Defined CSS selectors"
msgstr ""

#. type: Plain text
#: ./user-manual.txt:4312
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."
msgstr ""

#. type: delimited block |
#: ./user-manual.txt:4319
#, 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"
"in flow layout templates only (when data-numberofdives = 0)\n"
msgstr ""

#. type: Plain text
#: ./user-manual.txt:4322
msgid ""
"Rendering dive profiles is not supported for flow layout templates (when "
"data-numberofdives = 0)."
msgstr ""

#. type: Title ===
#: ./user-manual.txt:4323
#, no-wrap
msgid "Special attributes"
msgstr ""

#. type: Plain text
#: ./user-manual.txt:4327
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 "
"one page (_flow_ rendering)."
msgstr ""

#. type: Plain text
#: ./user-manual.txt:4329
msgid ""
"The *data-numberofdives* data attribute is added to the body tag to set the "
"rendering mode"
msgstr ""

#. type: Plain text
#: ./user-manual.txt:4331
msgid "render 6 dives per page:"
msgstr ""

#. type: delimited block .
#: ./user-manual.txt:4334
#, no-wrap
msgid "\t<body data-numberofdives = 6>\n"
msgstr ""

#. type: Plain text
#: ./user-manual.txt:4337
msgid "render as much dives as possible:"
msgstr ""

#. type: delimited block .
#: ./user-manual.txt:4340
#, no-wrap
msgid "\t<body data-numberofdives = 0>\n"
msgstr ""

#. type: Plain text
#: ./user-manual.txt:4343
msgid ""
"All CSS units should be in relative lengths only, to support printing on any "
"page size."
msgstr ""

#. type: Title ==
#: ./user-manual.txt:4344
#, no-wrap
msgid "APPENDIX F: FAQs."
msgstr ""

#. type: Title ===
#: ./user-manual.txt:4346
#, no-wrap
msgid "Subsurface appears to miscalculate gas consumption and SAC"
msgstr ""

#. type: Plain text
#: ./user-manual.txt:4350
msgid ""
"'Question': I dived with a 12.2 l tank, starting with 220 bar and ending "
"with 100 bar, and I calculate a different SAC compared what _Subsurface_ "
"calculates. Is _Subsurface_ miscalculating?"
msgstr ""

#. type: Plain text
#: ./user-manual.txt:4356
msgid ""
"'Answer': Not really. What happens is that _Subsurface_ actually calculates "
"gas consumption differently - and better - than you expect.  In particular, "
"it takes the incompressibility of the gas into account.  Traditionally, Gas "
"consumption and SAC should be: +consumption = tank size x (start pressure - "
"end pressure)+"
msgstr ""

#. type: Plain text
#: ./user-manual.txt:4362
msgid ""
"and that's true for an ideal gas, and it's what you get taught in dive "
"theory.  But an \"ideal gas\" doesn't actually exist, and real gases "
"actually don't compress linearly with pressure. Also, you are missing the "
"fact that one atmosphere of pressure isn't actually one bar.  So the *real* "
"calculation is:"
msgstr ""

#. type: Plain text
#: ./user-manual.txt:4364
msgid "+consumption = (amount_of_air_at_beginning - amount_of_air_at_end)+"
msgstr ""

#. type: Plain text
#: ./user-manual.txt:4370
msgid ""
"where the amount of air is *not* just \"tank size times pressure in bar\".  "
"It's a combination of: \"take compressibility into account\" (which is a "
"fairly small issue under 220 bar - you'll see more differences when you do "
"high-pressure tanks with 300bar) and \"convert bar to atm\" (which is the "
"majority of your discrepancy).  Remember: one ATM is ~1.013 bar, so without "
"the compressibility, your gas use is:"
msgstr ""

#. type: Plain text
#: ./user-manual.txt:4372
msgid "+12.2*((220-100)/1.013)+"
msgstr ""

#. type: Plain text
#: ./user-manual.txt:4377
msgid ""
"which is about 1445, not 1464. So there was 19 l too much in your simple "
"calculation that ignored the difference between 1 bar and one ATM.  The "
"compressibility does show up above 200 bar, and takes that 1445 down about "
"eight litres more, so you really did use only about 1437 l of air at surface "
"pressure."
msgstr ""

#. type: Plain text
#: ./user-manual.txt:4383
msgid ""
"So be happy: your SAC really is better than your calculations indicated.  Or "
"be sad: your cylinder contains less air than you thought it did.  And as "
"mentioned, the \"contains less air than you thought it did\" really starts "
"becoming much more noticeable at high pressure. A 400 bar really does not "
"contain twice as much air as a 200 bar one. At lower pressures, air acts "
"pretty much like an ideal gas."
msgstr ""

#. type: Title ===
#: ./user-manual.txt:4384
#, 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
msgid ""
"_Subsurface_ ends up ignoring surface time for many things (average depth, "
"divetime, SAC, etc).  'Question': Why do dive durations in my dive computer "
"differ from that given by _Subsurface_?"
msgstr ""

#. type: Plain text
#: ./user-manual.txt:4396
msgid ""
"'Answer': For example, if you end up doing a weight check (deep enough to "
"trigger the \"dive started\")  but then come back up and wait five minutes "
"for your buddies, your dive computer may say that your dive is 50 minutes "
"long - because you have fifty minutes worth of samples - but subsurface will "
"say it's 45 minutes - because you were actually diving for 45 minutes.  It's "
"even more noticeable if you do things like divemastering the initial OW "
"dives, when you may stay in the water for a long time, but spend most of it "
"at the surface. And then you don't want that to count as some kind of long "
"dive”."
msgstr ""

#. type: Title ===
#: ./user-manual.txt:4397
#, no-wrap
msgid "Some dive profiles are missing from the download"
msgstr ""

#. type: Plain text
#: ./user-manual.txt:4403
msgid ""
"'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."
msgstr ""

#. type: Plain text
#: ./user-manual.txt:4416
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 "
"these. However, if the logs are only on your dive computer, they cannot be "
"salvaged after being over written by new dives."
msgstr ""