path: root/Documentation/50-pot/subsurface-user-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: 2018-11-05 09:14+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: https://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:21
#, 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"
"Stefan Fuchs\n"
msgstr ""

#. type: Plain text
#: user-manual.txt:23
msgid "[blue]#_Version 4.8, September 2018_#"
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, organize, interpret and print scuba "
"and free dives. _Subsurface_ offers many advantages over other similar "
"software solutions:"
msgstr ""

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

#. type: Plain text
#: user-manual.txt:32
msgid ""
"Do you wish to seamlessly include GPS locations of dive sites into your dive "
"log?"
msgstr ""

#. type: Plain text
#: user-manual.txt:38
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 along with a dive computer? _Subsurface_ offers a "
"standard interface for downloading dive logs from all of these different "
"pieces of equipment, storing and analyzing the dive logs within a unified "
"system."
msgstr ""

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

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

#. type: Plain text
#: user-manual.txt:46
msgid ""
"Do you need an intuitive graphical dive planner that integrates with, and "
"takes into account, dives you’ve already logged?"
msgstr ""

#. type: Plain text
#: user-manual.txt:48
msgid ""
"Do you need a way of storing or backing up your dive log on the Internet, "
"letting you view your dive log from anywhere using an Internet browser?"
msgstr ""

#. type: Plain text
#: user-manual.txt:49
msgid "Do you wish to access or modify your dive log using a mobile phone?"
msgstr ""

#. type: Plain text
#: user-manual.txt:55
msgid ""
"_Subsurface_ binaries are available for Windows PCs (Win 7 or later from "
"version 4.6 of _Subsurface_ onwards), 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:64
msgid ""
"This manual explains how to use the _Subsurface_ program. To install the "
"software, consult the _Downloads_ page on the "
"https://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 https://github.com/Subsurface/subsurface/issues[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:67
#, no-wrap
msgid ""
"*Audience*: Recreational Scuba Divers, Free Divers, Tec Divers, "
"Professional\n"
"Divers\n"
msgstr ""

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

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

#. type: Plain text
#: user-manual.txt:75
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:82
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, typing the word \"_weights_\" into the search "
"text box, searches throughout the user manual. To the right of the search "
"text box are two arrows pointing up and down. These find the previous and "
"the next occurrence of the search term."
msgstr ""

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

#. type: Plain text
#: user-manual.txt:95
msgid ""
"_PREVIOUS/NEXT LINK_. Move between links (underlined words that jump to "
"specific sections in the user manual) by right-clicking on the text of the "
"manual.  This brings up a context menu to PREVIOUS links selected.  (see "
"image below). For instance if a link has been selected, then the option to "
"_Go Back_ shows the text at the previous link selected (similar to the "
"Previous Page button in a browser). Conversely the _Go Forward_ option jumps "
"to the text seen before selecting the _Go Back_ option. The _Reload_ option "
"reloads the complete user manual into the window."
msgstr ""

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

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

#. type: Plain text
#: user-manual.txt:112
msgid ""
"In order to develop _Subsurface_ to serve its users in the best possible "
"way, it’s important to have user information. Upon launching _Subsurface_ "
"and using the software for a week or so, a one-box user survey pops up. It "
"is entirely optional and the user controls what, if any, data are sent to "
"the _Subsurface_ development team. All data the user sends is useful, and "
"will only be used to steer future development and to customize the software "
"to fit the needs of the _Subsurface_ users. If you complete the survey, or "
"click the option not to be asked again, that should be the last "
"communication of this type you receive.  However, if your diving and/or "
"subsurface habits change and you wish to fill in another survey, just launch "
"_Subsurface_ with the _--survey_ option on the command line."
msgstr ""

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

#. type: Plain text
#: user-manual.txt:120
msgid ""
"The _Subsurface_ window is usually divided into four panels with a *Main "
"Menu* (File Edit Import Log View Share 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:126
msgid ""
"The *Dive List* on the bottom left, showing all the dives in the user's dive "
"log. A dive can be selected and highlighted on the dive list by clicking on "
"it. In most situations the up/down keys can be used to switch between "
"dives. The *Dive List* is an important tool for manipulating a dive log."
msgstr ""

#. type: Plain text
#: user-manual.txt:130
msgid ""
"The *Dive Map* on the bottom right, showing the user's dive sites on a world "
"map and centered on the site of the last dive selected in the *Dive "
"List*. The map scale can be increased or decreased."
msgstr ""

#. type: Plain text
#: user-manual.txt:134
msgid ""
"The *Info* on the top left, giving more detailed information on the dive "
"selected in the *Dive List*, including some statistics for the selected dive "
"or for all highlighted dive(s)."
msgstr ""

#. type: Plain text
#: user-manual.txt:138
msgid ""
"The *Dive Profile* on the top right, showing a graphical dive profile of the "
"selected dive in the *Dive List*. You can zoom into the dive profile for a "
"more detailed view."
msgstr ""

#. type: Plain text
#: user-manual.txt:142
msgid ""
"The dividers between panels can be dragged to change the size of any of the "
"panels. _Subsurface_ remembers the position of the dividers, so the next "
"time _Subsurface_ starts it uses the positions of the dividers from the last "
"time the program was used."
msgstr ""

#. type: Plain text
#: user-manual.txt:150
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. If several dives are selected, the last highlighted dive is the "
"_selected dive_, but summary data of all _highlighted dives_ is shown in the "
"*Stats* tab of the *Info* panel (maximum, minimum and average depths, "
"durations, water temperatures and SAC; total time and number of dives "
"selected)."
msgstr ""

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

#. type: Plain text
#: user-manual.txt:157
msgid ""
"Decide which of the four panels are displayed by selecting the *View* option "
"on the main menu. This feature has several choices of display:"
msgstr ""

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

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

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

#. type: Plain text
#: user-manual.txt:166
#, 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:168
#, no-wrap
msgid "*Globe*: Show only the world map, centered on the last selected dive.\n"
msgstr ""

#. type: Plain text
#: user-manual.txt:173
msgid ""
"Like other functions that can be accessed via the Main Menu, these options "
"can also be triggered using keyboard shortcuts. The shortcuts are shown with "
"an underline in the main menu entries, with the Alt-key pressed, or are "
"denoted after the menu item."
msgstr ""

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

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

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

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

#. type: Plain text
#: user-manual.txt:190
msgid ""
"Now that a new logbook is created, it is simple to add dive data it.  "
"_Subsurface_ allows several ways of adding dive data to a logbook."
msgstr ""

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

#. type: Plain text
#: user-manual.txt:194
msgid ""
"manually maintained divelog, dive data can be added to the logbook using one "
"of these approaches:"
msgstr ""

#. type: Plain text
#: user-manual.txt:196
msgid "Enter dive information by hand. This is useful if the diver didn’t"
msgstr ""

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

#. type: Plain text
#: user-manual.txt:202
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:206
msgid ""
"If a dive is recorded using a dive computer, the depth profile and a large "
"amount of additional information can be accessed.  These dives can be "
"imported from:"
msgstr ""

#. type: Plain text
#: user-manual.txt:208
msgid ""
"The dive computer itself. See: xref:S_ImportDiveComputer[Importing new dive "
"information from a Dive Computer];"
msgstr ""

#. type: Plain text
#: user-manual.txt:209
msgid "Proprietary software distributed by manufacturers of dive computers. Refer"
msgstr ""

#. type: Plain text
#: user-manual.txt:210
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 "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:230
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 the divemaster or dive "
"guide, and some remarks about the dive. _Subsurface_ can store much more "
"information for each dive.  To add a dive to a dive log, select _Log -> Add "
"Dive_ from the Main Menu. The program then shows three panels on which to "
"enter information for a dive: two tabs in the *Info* panel (*Notes* and "
"*Equipment*), as well as the *Dive Profile* panel that displays a graphical "
"profile of each dive. These panels are respectively marked [red]#A#, "
"[red]#B# and [red]#C# in the figure below. Each of these tabs will now be "
"explained for data entry."
msgstr ""

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

#. type: Plain text
#: user-manual.txt:235
msgid ""
"When you edit a field in Notes or Equipment panels, _Subsurface_ enters "
"*Editing Mode*, indicated by the message in the blue box at the top of the "
"*Notes* panel (see the image below). This message is displayed in all the "
"panels under Notes and Equipment when in *Editing Mode*."
msgstr ""

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

#. type: Plain text
#: user-manual.txt:245
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 applying the "
"information. By selecting the _Apply changes_ button, a local copy of the "
"information for this specific dive is saved in memory but NOT written to "
"disk.  The _Apply changes_ button should ONLY be selected after all parts of "
"a dive have been entered. When closing 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:247
#, no-wrap
msgid "Creating a Dive Profile"
msgstr ""

#. type: Plain text
#: user-manual.txt:254
msgid ""
"The *Dive Profile* (a graphical representation of the depth of the dive as a "
"function of time) is shown in the panel on the top right hand of the "
"_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 described:"
msgstr ""

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

#. type: Plain text
#: user-manual.txt:274
msgid ""
"_Modifying the dive profile_: When the cursor is moved around the dive "
"profile, its position is shown by two right-angled red lines as seen below.  "
"The time and depth represented by the cursor are indicated at the top of the "
"black information box (@ and D). The units (metric/imperial) on the axes are "
"determined by the *Preference* settings. The dive profile itself comprises "
"several line segments demarcated by waypoints (white dots on the profile, as "
"shown above). The default dive depth is 15 m.  If the dive depth was 20 m "
"then you need to drag the appropriate waypoints downward to 20 m. To add a "
"waypoint, double-click on any line segment. To move an additional waypoint, "
"drag it. Moving can also be done by selecting the waypoint and using the "
"arrow keys.  To remove a waypoint, right-click on it and choose \"Remove "
"this point\" from the context menu. Drag the waypoints to represent an "
"accurate time duration for the dive. Below is a dive profile for a dive to "
"20 m for 30 min, followed by a 5 minute safety stop at 5 m."
msgstr ""

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

#. type: Plain text
#: user-manual.txt:287
msgid ""
"_Specifying the gas composition:_ The gas composition used is indicated "
"along the line segments of the dive profile. This defaults to the first gas "
"mixture specified in the *Equipment* tab, which was air in the case of the "
"profile above. The gas mixtures of segments of the dive profile can be "
"changed by right-clicking on the particular waypoint and selecting the "
"appropriate gas from the context menu. Changing the gas for a waypoint "
"affects the gas shown in the segment _to the right_ 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:288
#, no-wrap
msgid "images/DiveProfile3_f20.jpg"
msgstr ""

#. type: Plain text
#: user-manual.txt:295
msgid ""
"With the profile now defined, more details must be added to have a fuller "
"record of the dive. To do this, the *Notes* and the *Equipment* tabs on the "
"top left hand of the _Subsurface_ window should be used. Click on "
"xref:S_Notes_dc[*this link*] for instructions on how to use these tabs."
msgstr ""

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

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

#. type: Plain text
#: user-manual.txt:308
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, using dive details from a wide range of dive "
"computers. The latest list of supported dive computers can be found at: "
"link:https://subsurface-divelog.org/documentation/supported-dive-computers/[ "
"Supported dive computers]."
msgstr ""

#. type: Named 'icon' AttributeList argument for style 'icon'
#: user-manual.txt:309 user-manual.txt:712 user-manual.txt:786 user-manual.txt:1166 user-manual.txt:3305 user-manual.txt:3708
#, 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 PC-Communication "
"mode. **This could drain the dive computer's battery**. We recommend the "
"user checks to be sure the dive computer is charged when connected to the "
"USB port of a PC. For example, several Suunto and Mares dive computers do "
"not recharge through the USB connection. Users should refer to the dive "
"computer's manual if they are unsure whether the dive computer recharges its "
"batteries while connected to the USB port."
msgstr ""

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

#. type: Plain text
#: user-manual.txt:337
msgid ""
"After this, the dive computer can be hooked up to the user's PC using these "
"steps:"
msgstr ""

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

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

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

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

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

#. type: Plain text
#: user-manual.txt:357
msgid ""
"Dive computers tend to keep a certain number of dives in memory, even though "
"these dives have already been imported to _Subsurface_. For that reason, if "
"the dive computer allows this, _Subsurface_ only imports dives that have not "
"been downloaded 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:364
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:379
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 specific dive computer and, in some cases, how to do the correct settings "
"to the operating system of the computer on which _Subsurface_ is running.  "
"Some dive computers disable this drop-down as they use other means to find "
"and connect to the device. For some dive computers the data entered here is "
"actually the mount point of the USB storage device as which the dive "
"computer identifies itself."
msgstr ""

#. type: Plain text
#: user-manual.txt:384
msgid ""
"Below the three drop downs are up to four shortcut buttons that allow you to "
"easily switch between multiple dive computers that you are frequently "
"downloading from. These buttons only appear once you have downloaded from "
"different dive computers."
msgstr ""

#. type: Plain text
#: user-manual.txt:394
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_ has been accidentally "
"deleted or if there are older dives that still need to be downloaded from "
"the dive computer, this box needs to be checked. Some dive computers "
"(e.g. Mares Puck) do not provide a contents list to _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:400
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 computer."
msgstr ""

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

#. type: Plain text
#: user-manual.txt:425
msgid ""
"Then select the _Download_ button.  With communication established, you can "
"see how the data are retrieved from the dive computer.  Depending on the "
"make of the dive computer and/or number of recorded dives, this could take "
"some time. Be patient. The _Download_ dialogue shows a progress bar at the "
"bottom of the dialogue. Remember for some dive computers progress "
"information could be inaccurate since _Subsurface_ doesn’t know how much "
"downloadable data there are until the download is complete.  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, showing the date, duration and depth. 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:429
msgid ""
"If there is a problem in communicating with the dive computer, an error "
"message is 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:433
#, no-wrap
msgid "*PROBLEMS WITH DATA DOWNLOAD FROM A DIVE COMPUTER?*\n"
msgstr ""

#. type: Named 'icon' AttributeList argument for style 'icon'
#: user-manual.txt:433 user-manual.txt:557 user-manual.txt:601 user-manual.txt:614 user-manual.txt:623 user-manual.txt:1321 user-manual.txt:1386 user-manual.txt:1571
#, no-wrap
msgid "images/icons/important.png"
msgstr ""

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

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

#. type: delimited block *
#: user-manual.txt:441
msgid ""
"Is the dive computer’s battery fully charged? If not then charge or replace "
"it."
msgstr ""

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

#. type: delimited block *
#: user-manual.txt:450
msgid ""
"Consult "
"xref:_appendix_a_operating_system_specific_information_for_importing_dive_information_from_a_dive_computer[Appendix "
"A] to be sure 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 recognize the USB adapter by showing "
"an appropriate device name next to the Mount Point, then there is a "
"possibility the cable or USB adaptor is faulty. A faulty cable is the most "
"common cause of communication failure between a dive computer and "
"_Subsurface_.  It’s also possible _Subsurface_ cannot interpret the "
"data. Perform a download for diagnostic purposes with the following two "
"boxes checked in the download dialogue discussed above:"
msgstr ""

#. type: delimited block *
#: user-manual.txt:465
#, 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 where the "
"information will be saved. The default folder is the one in which the\n"
"_Subsurface_\n"
"dive log is kept.\n"
msgstr ""

#. type: delimited block *
#: user-manual.txt:475
#, 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 "
"analyzed. Provide the dive computer make and model as well as contextual "
"information about the dives recorded on the dive computer."
msgstr ""

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

#. type: Plain text
#: user-manual.txt:500
msgid ""
"Bluetooth is becoming a more common way of communication between dive "
"computers and _Subsurface_. _Subsurface_ provides a largely operating system "
"independent Bluetooth interface. An increasing number of dive computers use "
"Bluetooth Low Energy (BTLE)  as a means of communication. However, BTLE is "
"not a standardised protocol, consequently adaptations need to be made for "
"communicating with each different dive computer model. See the "
"link:https://subsurface-divelog.org/documentation/supported-dive-computers/[list "
"of supported dive computers].  Bluetooth communication is often more "
"reliable if all Bluetooth devices seen by the _Subsurface_ computer are "
"removed and pairing with the Bluetooth dive computer is performed from "
"afresh. The Bluetooth and BTLE interfaces are under active development with "
"respect to new dive computers that use this mechanism of communication."
msgstr ""

#. type: Plain text
#: user-manual.txt:503
msgid "Setting up _Subsurface_ for Bluetooth communication requires four steps:"
msgstr ""

#. type: Plain text
#: user-manual.txt:505
msgid "Ensure Bluetooth is activated on the host computer running _Subsurface_."
msgstr ""

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

#. type: Plain text
#: user-manual.txt:507
msgid ""
"Ensure the Bluetooth-enabled dive computer is Bluetooth-discoverable and in "
"PC upload mode."
msgstr ""

#. type: Plain text
#: user-manual.txt:508
msgid "Ensure _Subsurface_ is paired with the Bluetooth-enabled dive computer."
msgstr ""

#. type: Plain text
#: user-manual.txt:512
msgid ""
"Select the Download dialogue by selecting _Import -> Import from dive "
"computer_ from the *Main Menu*. After checking the box labeled _\"Choose "
"Bluetooth download mode\"_, the dialogue below appears."
msgstr ""

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

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

#. type: Plain text
#: user-manual.txt:524
msgid ""
"Although the _Subsurface_ Bluetooth interface is intended to function "
"without Bluetooth pairing at the operating system level, it is always "
"prudent to follow up initial Bluetooth pairing problems by pairing the "
"Bluetooth dive computer with the _Subsurface_ computer using the operating "
"system services of the desktop computer. Delete all existing pairings and "
"start by scanning for Bluetooth devices from an empty list (on the desktop) "
"of Bluetooth devices. Once _Subsurface_ has recognised the Bluetooth dive "
"computer, subsequent divelog downloads are likely to be simple."
msgstr ""

#. type: Plain text
#: user-manual.txt:555
msgid ""
"On the _Linux_ or _MacOS_ platforms the name of the _Subsurface_ computer "
"and its Bluetooth address are shown on the right hand side.  The power state "
"(on/off) of the Bluetooth adapter is shown below the address and can be "
"changed by checking the _Turn on/off_ box.  If the Bluetooth address is not "
"shown, then _Subsurface_ does not see the local Bluetooth device. Ensure 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 completes the first two steps above.  Ensure the "
"Bluetooth-enabled dive computer is in PC-upload mode and it is discoverable "
"by other Bluetooth devices. Consult the manual of the dive computer for more "
"information. Now the third item in the list above has been finished.  Select "
"the _Scan_ button towards the bottom left of the dialogue above. After "
"searching, the dive computer should be listed (perhaps as one of a number of "
"Bluetooth devices) in the main list box on the lefthand side of the dialogue "
"(see image above). If this does not work, select the _Clear_ button, then "
"scan again for Bluetooth devices using the _Scan_ button. After taking these "
"actions _Subsurface_ should see the dive computer.  On the left hand side, "
"if the computer has more than one local Bluetooth devices connected, use the "
"list box to indicate which one needs to connect to _Subsurface_.  The label "
"of the discovered dive computer contains the name of the device, its address "
"and its pairing status. For BTLE devices the address often starts with "
"\"LE\".  If the device is not paired and has a red background color, a "
"context menu can be opened by selecting the item with a right-click.  Select "
"the _Pair_ option and wait for the task to complete. If this dive computer "
"is being paired to Subsurface for the first time, it’s possible Subsurface "
"will request a Pass Code or PIN number. The most commonly-used Pass Code is "
"0000, and this works for the Shearwater Petrel. If necessary, consult the "
"user manual of the dive computer being used."
msgstr ""

#. type: delimited block *
#: user-manual.txt:562
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:564
msgid "One way to achieve this is to use +bluetoothctl+:"
msgstr ""

#. type: delimited block *
#: user-manual.txt:575
#, 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:581
msgid ""
"After the devices are paired, press the _Save_ button of the dialogue.  This "
"closes the Bluetooth dialogue. Now select _Download_ in the _Download from "
"dive computer_ dialogue which should still be open. The downloaded dives are "
"shown on the righthand side of the download dialogue."
msgstr ""

#. type: Title ====
#: user-manual.txt:582 user-manual.txt:4035 user-manual.txt:4123
#, no-wrap
msgid "On Windows:"
msgstr ""

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

#. type: Plain text
#: user-manual.txt:593
msgid ""
"On _Windows_ platforms the _Local Bluetooth device details section_ on the "
"right is not displayed as is the case on the Linux/Mac systems.  To start a "
"scan (by pressing the _Scan_ button)  check that the Bluetooth device on the "
"_Subsurface_ computer is turned on by selecting the dive computer from the "
"list of available Bluetooth devices (see image above). If the dive computer "
"is being accessed by Subsurface for the first time, it’s possible Subsurface "
"will request a Pass Code or PIN number. Supply the Pass Code recommended in "
"the user manual of the dive computer.  A Pass Code or PIN of 0000 is often "
"the default."
msgstr ""

#. type: Plain text
#: user-manual.txt:600
msgid ""
"The pairing step is checked and done automatically during the download "
"process. If the devices have never been paired the system will ask "
"permission and put a message on the right side of the screen: _Add a device, "
"Tap to set up your DC device_. Always allow this pairing. After a discovered "
"item is selected, select the _Save_ button.  Finally select the _Download_ "
"button on the _Download_ dialogue and wait for the process to complete."
msgstr ""

#. type: Plain text
#: user-manual.txt:608
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 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:613
msgid ""
"A log message on the bottom left of the _Remote Bluetooth device selection_ "
"shows details about the current status of the Bluetooth agent. To select "
"another dive computer for download using the \"Remote Bluetooth selection "
"dialogue\" press the three-dots button from the _\"Choose Bluetooth download "
"mode\"_ option."
msgstr ""

#. type: Plain text
#: user-manual.txt:622
msgid ""
"The Subsurface support for BLTE dive computers on Windows is *EXPERIMENTAL* "
"and only supported on Windows 10.  Please make sure that you have the latest "
"version of Windows 10.  "
"link:https://en.wikipedia.org/wiki/Windows_10_version_history#Version_1803_(April_2018_Update)[Version "
"1803] is a minimum requirement. Also make sure that you have installed the "
"latest drivers for your motherboard and/or BTLE dongle."
msgstr ""

#. type: Plain text
#: user-manual.txt:632
#, 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:634
#, no-wrap
msgid "Changing the name of a dive computer"
msgstr ""

#. type: Plain text
#: user-manual.txt:650
msgid ""
"It may be necessary to distinguish between different dive computers used to "
"upload dive logs to _Subsurface_. For instance if a buddy’s dive computer is "
"the same make and model as your own and dive logs are uploaded from both "
"dive computers to the same _Subsurface_ computer, then you might like to "
"call one \"Alice's Suunto D4\" and the other \"Bob's Suunto "
"D4\". Alternatively, consider a technical diver who dives with two or more "
"dive computers of the same model, the logs of both (or all) being uploaded.  "
"In this case it might be prudent to call one of them \"Suunto D4 (1)\" and "
"another \"Suunto D4 (2)\". This is easily done in _Subsurface_.  On the "
"*Main Menu*, select _Log -> Edit device names_. A dialog box opens, showing "
"the current Model, ID and Nickname of the dive computers used for "
"upload. Edit the Nickname field for the appropriate dive computer. After "
"saving the Nickname, the dive logs show the nickname for that particular "
"device instead of the model name, allowing easy identification of devices."
msgstr ""

#. type: Title ====
#: user-manual.txt:652
#, no-wrap
msgid "Uploading data for a specific dive from more than one dive computer"
msgstr ""

#. type: Plain text
#: user-manual.txt:663
msgid ""
"Some divers use more than one dive computer at the same time, e.g. during "
"technical diving.  If you import the dive profiles from these different dive "
"computers into _Subsurface_, the profiles can be viewed "
"independently. During upload the data from the dive computers are "
"automatically merged into a single dive. The different profiles are "
"presented on the _Profile_ panel with the name of each dive computer "
"indicated at the bottom left.  *While the dive is highlighted in the _Dive "
"List_*, switch between the profiles of the different dive computers by using "
"either the left/right arrow keyboard keys or by selecting _View -> Previous "
"DC_ or _View -> Next DC_. The data in the _Notes_ panel are not affected by "
"the specific dive computer that is selected."
msgstr ""

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

#. type: Plain text
#: user-manual.txt:672
msgid ""
"With the uploaded dives in the *Dive List*, the information from the dive "
"computer is not complete and more details must be added to have a full "
"record of the dives. To do this, the *Notes* and the *Equipment* tabs on the "
"top left hand of the _Subsurface_ window should be used."
msgstr ""

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

#. type: Plain text
#: user-manual.txt:679
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:689
msgid ""
"In some cases, you must provide the date and time of the dive, for example "
"when entering a dive by hand or when a dive computer doesn’t provide the "
"date and time of the dive.  (Usually the date and time of the dive, gas "
"mixture and water temperature are shown as obtained from the dive computer)  "
"If the contents of the *Notes tab* is changed or edited in any way, the "
"message in a blue box at the top of the panel shows the dive is being "
"edited. If you click on the *Notes* tab, the following fields are visible "
"(left hand image, below):"
msgstr ""

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

#. type: Plain text
#: user-manual.txt:699
msgid ""
"The right hand image, above, shows a *Notes tab* filled with dive "
"information.  The *Date* and *Time* fields reflects the date and time of the "
"dive. By clicking the date, a calendar is displayed for selecting 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:709
#, 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 have information.\n"
"If air temperature isn’t provided by the dive computer, the first "
"temperature reading\n"
"might be used for the air temperature. Generally this is close to the real "
"air temperature.\n"
"If editing is required, only a value is required, the units of temperature "
"will be\n"
"automatically supplied by\n"
"_Subsurface_ (following the _Preferences_, metric or imperial units will\n"
"be used).\n"
msgstr ""

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

#. type: Plain text
#: user-manual.txt:720
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. Then supply a dive site name in the textbox labelled _Location_ "
"on the *Notes* tab."
msgstr ""

#. type: Plain text
#: user-manual.txt:728
#, no-wrap
msgid ""
"*Using existing dive locations:* Type in the name of the dive site, "
"e.g. \"Tihany, Lake Balaton, Hungary\".\n"
"If several dives are\n"
"made at the same location, the site information for the first dive is "
"re-used.\n"
"Therefore, if a dive site has been used before, the name of that site (and "
"sometimes\n"
"the names of similar sites) appears below the dive site text box (image "
"below). Double-click on\n"
"the appropriate dive site name and the dive location will be associated with "
"the\n"
"dive being entered. Then select _Apply Changes_ (image below) to save the "
"geolocation for this dive site.\n"
msgstr ""

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

#. type: Plain text
#: user-manual.txt:735
#, no-wrap
msgid ""
"*Entering a new dive location:* On the other hand, having dived at a new "
"dive location,\n"
"a new record needs to be created\n"
"that could be used for the new and for later dives at this new site. Type "
"the name of the new dive site into the text box\n"
"(image A below).\n"
msgstr ""

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

#. type: Plain text
#: user-manual.txt:743
msgid ""
"Double-click on the blue bar below the new dive location name. The blue bar "
"disappears (image B above) and the globe icon on the right-hand of the "
"location name text box turns blue.  In the Dive Map part of the _Subsurface_ "
"window, a world map appears (image C above). Click on the blue globe icon to "
"the right of the dive site name in the _Notes_ panel (image B above). This "
"opens a window for entering the details of the new dive location (image A "
"below).  The globe icon changes to indicate that the location data are being "
"edited. The only important data here are the geographic coordinates of the "
"dive location."
msgstr ""

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

#. type: Plain text
#: user-manual.txt:747
msgid "There are three ways of adding the coordinates:"
msgstr ""

#. type: Plain text
#: user-manual.txt:750
#, no-wrap
msgid ""
"*(1):* Enter coordinates by hand if they are known, using one of\n"
"   four formats with latitude followed by longitude:\n"
msgstr ""

#. type: Plain text
#: user-manual.txt:755
#, no-wrap
msgid ""
"\tISO 6709 Annex D format e.g. 30°13'28.9\"N 30°49'1.5\"E\n"
"\tDegrees and decimal minutes, e.g. N30° 13.49760' , E30° 49.30788'\n"
"\tDegrees minutes seconds, e.g. N30° 13' 29.8\" , E30° 49' 1.5\"\n"
"\tDecimal degrees, e.g. 30.22496 , 30.821798\n"
msgstr ""

#. type: Plain text
#: user-manual.txt:764
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.  Enter any other contextual information about the dive site "
"(Description and Notes), then select _Apply Changes_ to save the geolocation "
"for this dive site.  The dive site information can later be edited by "
"clicking the globe icon to the right of the dive site name in the *Notes "
"tab*."
msgstr ""

#. type: Plain text
#: user-manual.txt:776
#, no-wrap
msgid ""
"*(2):* Use the Dive Map to specify the coordinates. The Dive map now shows\n"
"all the existing dive locations in grey as well as an additional marker in "
"red\n"
"(image B above). Drag the red marker to the location of the dive site being "
"entered.\n"
"The map can be dragged and zoomed using the mouse wheel. Position the red "
"marker\n"
"by dragging it on the map, zooming in on the appropriate part of the map and "
"placing\n"
"the marker at an appropriate position (image B below). The coordinates of "
"the dive\n"
"location are automatically inserted into the appropriate text box in the "
"dive location\n"
"information window (image A below). Enter any other contextual information "
"about the dive site (Description and Notes),\n"
"then select _Apply Changes_ to save the geolocation for this dive site.\n"
"The dive site information can later be edited by clicking the globe icon to "
"the right of the\n"
"dive site name in the *Notes tab*.\n"
msgstr ""

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

#. type: Plain text
#: user-manual.txt:781
msgid ""
"Once the dive location data have been saved, the dive on the Dive List has a "
"globe icon immediately to the left of the location name of a particular "
"dive."
msgstr ""

#. type: Plain text
#: user-manual.txt:785
#, no-wrap
msgid ""
"*(3):* Obtain the coordinates using the _Subsurface-mobile_ App on an\n"
"   Android or iPhone device with GPS and if the dive site coordinates\n"
"   were stored using one of this app.\n"
msgstr ""

#. type: Plain text
#: user-manual.txt:793
msgid ""
"GPS coordinates of a dive site are linked to the location name - so *saving* "
"a dive site with only coordinates and no name causes problems. (Subsurface "
"will think all of these dives have the same location and try to keep their "
"GPS coordinates the same)."
msgstr ""

#. type: Plain text
#: user-manual.txt:803
#, no-wrap
msgid ""
"*Dive site name lookup:* If you typed coordinates into the appropriate\n"
"text box, you can do an automated name lookup based on the coordinates.\n"
"This is done when _Subsurface_ uses the Internet to find the name of the "
"dive site\n"
"based on the coordinates that were given. 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"
"sites named \"Blue Hole\", all of them are listed.\n"
msgstr ""

#. type: Plain text
#: user-manual.txt:808
msgid ""
"Enter any other contextual information about the dive site (Description and "
"Notes), then select _Apply Changes_ to save the geolocation for this dive "
"site.  The dive site information can later be edited by clicking the globe "
"icon to the right of the dive site name in the *Notes tab*."
msgstr ""

#. type: Plain text
#: user-manual.txt:813
#, no-wrap
msgid ""
"*Dive mode*: This is a dropdown box allowing you to choose the type of "
"dive\n"
"performed. The options are OC (Open Circuit SCUBA, the default setting, for "
"most recreational dives),\n"
"Freedive (dive without SCUBA equipment), CCR (Closed-circuit\n"
"rebreather) and pSCR (Passive semi-closed rebreather).\n"
msgstr ""

#. type: Plain text
#: user-manual.txt:818
#, no-wrap
msgid ""
"*Divemaster*: The name of the divemaster or dive guide should be\n"
"entered in this field\n"
"which offers auto selection based on the list of divemasters in\n"
"the current logbook.\n"
msgstr ""

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

#. type: Plain text
#: user-manual.txt:828
#, 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 under suit was used.\n"
msgstr ""

#. type: Plain text
#: user-manual.txt:831
#, no-wrap
msgid ""
"*Rating*: 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:834
#, no-wrap
msgid ""
"*Visibility*: Provide a rating of visibility during the\n"
"dive on a 5-point scale by clicking the appropriate star.\n"
msgstr ""

#. type: Plain text
#: user-manual.txt:841
#, no-wrap
msgid ""
"*Tags*: Tags that describe the type of dive done can be entered\n"
"here (separated by commas). Examples of common tags are boat, drift, "
"training,\n"
"cave, etc.\n"
"_Subsurface_ has many built-in tags. By starting to type a tag, _Subsurface_ "
"lists\n"
"the tags that correspond to the typing. For instance, by typing\n"
"+cav+, the tags *cave* and *cavern* are shown to choose from.\n"
msgstr ""

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

#. type: Plain text
#: user-manual.txt:848
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. Use them when *ALL* other information has been added. The image "
"xref:S_Notes_dc[at the beginning of this section] shows an example of a "
"*Notes tab* after completing the dive information."
msgstr ""

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

#. type: Plain text
#: user-manual.txt:854
msgid ""
"The Equipment tab allow entering information about the type of cylinder and "
"gas used, as well as the weights used for the dive. The message in the blue "
"box at the top of the panel:"
msgstr ""

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

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

#. type: Plain text
#: user-manual.txt:879
msgid ""
"For hand-entered dives, this information needs to be typed in. For dive "
"computers, _Subsurface_ often gets the gas used from the dive computer and "
"automatically inserts the gas composition(% oxygen or % helium) in the "
"table. The + button at the top right allows adding more cylinders for this "
"dive. The dark dustbin icon on the left allows you to delete information for "
"a cylinder.  Note that it is not possible to delete a cylinder if it is used "
"during the dive. A cylinder might be implicitly used in the dive, even "
"without a gas change event.  Start by selecting a cylinder type on the "
"left-hand side of the table.  To select a cylinder, the _Type_ box should be "
"clicked. This brings up a list button that can be used to display a dropdown "
"list of cylinders:"
msgstr ""

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

#. type: Plain text
#: user-manual.txt:887
msgid ""
"The drop-down list can then be used to select the cylinder type that was "
"used for this dive, or just start typing in the box which shows the "
"available options for the entered characters. The *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:891
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:902
msgid ""
"Finally, provide the gas mixture used. If air was used, the value of 21% can "
"be entered into the oxygen box 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. Here 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:903
#, no-wrap
msgid "images/CylinderDataEntry3_f20.jpg"
msgstr ""

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

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

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

#. type: Plain text
#: user-manual.txt:929
msgid ""
"This can be used to select the type of weight system used during the "
"dive. You may start typing in the box to specify a different weighting "
"mechanism that will be saved by _Subsurface_.  In the *Weight* field, type "
"in the amount of weight used during the dive. After specifying the weight "
"system, save the data by pressing _ENTER_ on the keyboard or by clicking "
"outside the cell with the cursor.  It’s possible to enter information for "
"more than one weight system by adding an additional system using the + "
"button on the top right hand. Weight systems can be deleted using the dust "
"bin icon on the left hand. Here is an example of information for a dive with "
"two types of weights: integrated as well as a weight belt:"
msgstr ""

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

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

#. type: Plain text
#: user-manual.txt:948
msgid ""
"_METHOD 1_: After downloading dives from a dive computer, the dive profiles "
"of each is shown in the *Dive profile* tab, as well as a few items of "
"information in the *Notes* tab (e.g. water temperature) and in the "
"*Equipment* tab (e.g. gas pressures and gas composition). Other fields "
"remain empty.  It may be useful to simultaneously edit some of the fields in "
"the *Notes* and *Equipment* tabs.  For instance, it’s possible that a diver "
"performed several dives during a single day, using identical equipment at "
"the same dive site, or with the same divemaster and/or buddy or "
"tags. Instead of completing the information for each dive separately, select "
"all the dives for that day in the *Dive List* and insert the same "
"information in the *Notes* and *Equipment* fields that need identical "
"information. This is done by editing the dive notes or the equipment for any "
"one of the selected dives."
msgstr ""

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

#. type: Plain text
#: user-manual.txt:967
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:969
#, no-wrap
msgid "Adding Bookmarks to a dive"
msgstr ""

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

#. type: Plain text
#: user-manual.txt:978
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 that point (see *A* below)."
msgstr ""

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

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

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

#. type: Plain text
#: user-manual.txt:1001
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, the newly "
"entered dive data are erased from the computer memory, although the dive "
"profile is retained. When the user exits _Subsurface_ there is a final "
"prompt to confirm the new data should now be saved permanently on the "
"computer disk."
msgstr ""

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

#. type: Plain text
#: user-manual.txt:1025
msgid ""
"Many divers log their dives using the proprietary software provided by the "
"manufacturers of their dive computers.  _Subsurface_ can import dive logs "
"from a range of other dive log software. While import from some software is "
"supported natively, others require export of the dive log to an intermediate "
"format that can then be imported into _Subsurface_.  Currently, _Subsurface_ "
"supports importing CSV log files from several sources.  Dive log import from "
"APD LogViewer, XP5, Sensus and Seabear files are preconfigured, but because "
"the import is flexible, users can configure their own imports.  Manually "
"kept log files (e.g. a spreadsheet) can also be imported by configuring the "
"CSV import.  _Subsurface_ can also import UDDF and UDCF files used by some "
"dive log software and some dive computers, like the Heinrichs & Weikamp "
"DR5. Finally, for some dive log software like Mares Dive Organizer we "
"currently recommend importing the logbook first into a web service like "
"_divelogs.de_ and then import from there with _Subsurface_. Divelogs.de "
"supports a few additional logbook formats that _Subsurface_ currently cannot "
"handle."
msgstr ""

#. type: Plain text
#: user-manual.txt:1037
msgid ""
"If the format of other software is supported natively on Subsurface, select "
"either _Import -> Import log files_ or _File -> Open log file_. Notice that "
"the import adds the imported data to the current *Dive list*, and the open "
"style starts a new dive list. _Subsurface_ supports the data formats of many "
"dive computers, including Suunto, Shearwater and some CCR equipment. When "
"importing dives, _Subsurface_ tries to detect multiple records for the same "
"dive and merges the information as best as it can. If there are no time zone "
"issues (or other reasons that would cause the beginning time of the dives to "
"be significantly different) _Subsurface_ will not create duplicate "
"entries. Below is more specific information to import data to _Subsurface_."
msgstr ""

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

#. type: Plain text
#: user-manual.txt:1044
msgid ""
"Importing dives from other software is done through a universal interface "
"activated by selecting _Import_ from the Main Menu, then clicking on _Import "
"Log Files_. This brings up dialogue *A*, below."
msgstr ""

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

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

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

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

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

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

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

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

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

#. type: Plain text
#: user-manual.txt:1059
msgid "divelogs.de logs"
msgstr ""

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

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

#. type: Plain text
#: user-manual.txt:1062
msgid "Suunto Dive Manager (DM3, DM4, DM5)"
msgstr ""

#. type: Plain text
#: user-manual.txt:1063
msgid "DL7 files used by Diver's Alert network (DAN)"
msgstr ""

#. type: Plain text
#: user-manual.txt:1064
msgid "Underwater technologies AV1 dive logs"
msgstr ""

#. type: Plain text
#: user-manual.txt:1065
msgid "Divesoft dive logs"
msgstr ""

#. type: Plain text
#: user-manual.txt:1066
msgid "Poseidon MK VI eCCR dive logs"
msgstr ""

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

#. type: Plain text
#: user-manual.txt:1072
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:1073
#, no-wrap
msgid "Importing from  OSTCTools"
msgstr ""

#. type: Plain text
#: user-manual.txt:1082
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:1086
msgid ""
"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:1091
msgid ""
"Please remember that OSTCTools is *not* true diving log software, but rather "
"a useful set of tools for analysis and management of OSTC devices. Only raw "
"dive computer data will be imported to _Subsurface_; the rest of the data "
"(buddies, equipment, notes, etc) need to be completed manually."
msgstr ""

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

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

#. type: Plain text
#: user-manual.txt:1105
msgid ""
"Export the dive log data from Mares Dive Organizer to your desktop, using a "
"_.sdf_ file name extension. Refer to xref:Mares_Export[Appendix C] for more "
"information."
msgstr ""

#. type: Plain text
#: user-manual.txt:1111
msgid ""
"Data should then be imported into _www.divelogs.de_. First, create a user "
"account in _www.divelogs.de_ and Log into that web site, then select _Import "
"Logbook -> Dive Organizer from the menu on the left hand side.  The "
"instructions must be carefully followed to transfer the dive information (in "
"_.sdf_ format) from the Dive Organizer database to _www.divelogs.de_."
msgstr ""

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

#. type: Title ====
#: user-manual.txt:1116
#, no-wrap
msgid "Importing Scubapro _SmartTrak_ divelogs"
msgstr ""

#. type: Plain text
#: user-manual.txt:1123
msgid ""
"_SmartTrak_ stores the raw data from a Uwatec/Scubapro dive computer along "
"with a plethora of other data manually added by the user, ranging from dive "
"points to buddies data or DAN survey info. However, this is Microsoft "
"Windows-based propietary software by Uwatec (today Scubapro)  using "
"Microsoft Access databases, preventing the integration the importer into the "
"_Subsurface_ core application."
msgstr ""

#. type: Plain text
#: user-manual.txt:1129
msgid ""
"A stand alone tool for Linux has been developed to import the _.slg_ files "
"generated by SmartTrak to Subsurface's _.xml_ format. It can be downloaded "
"from https://subsurface-divelog.org/downloads[the usual _Subsurface_ "
"repository], as a Windows installer or a Linux AppImage.  The application is "
"not currently supported on Mac."
msgstr ""

#. type: Plain text
#: user-manual.txt:1132
msgid ""
"It can also be built for Linux systems. Two dependencies need to be met in "
"your system before building: _glib2.0_ and _mdbtools_ (see below)."
msgstr ""

#. type: Plain text
#: user-manual.txt:1134
msgid ""
"In addition, a web service is available for divelog convertions from "
"SmartTrak to _Subsurface_ (see below)."
msgstr ""

#. type: Plain text
#: user-manual.txt:1137
msgid ""
"Feel free to contact the _Subsurface_ development team on "
"mailto:subsurface@subsurface-divelog.org[our mailing list] for assistance in "
"importing _SmartTrak_ dive logs."
msgstr ""

#. type: Title =====
#: user-manual.txt:1138
#, no-wrap
msgid "Building _smtk2ssrf_"
msgstr ""

#. type: Plain text
#: user-manual.txt:1142
msgid ""
"Assuming the above dependencies have been installed and the _Subsurface_ "
"source tree is in the directory _~/src/subsurface_, then:"
msgstr ""

#. type: Plain text
#: user-manual.txt:1144
msgid "Move to the source tree directory out of _Subsurface_ (e.g. ~/src)"
msgstr ""

#. type: Plain text
#: user-manual.txt:1147
msgid ""
"Run \" $ ./subsurface/scripts/smtk2ssrf-build.sh \", if every thing has gone "
"fine, you will now have an executable named smtk2ssrf in "
"~/src/subsurface/smtk-import/build"
msgstr ""

#. type: Plain text
#: user-manual.txt:1150
msgid ""
"You can run it from this directory, copy it to another one, e.g. _~/bin_ or "
"simply run \"sudo make install\", and the binary will be installed in "
"/usr/local/bin (which is commonly included in every $PATH)."
msgstr ""

#. type: Plain text
#: user-manual.txt:1152
msgid ""
"The script has some options mostly useful for development pourposes. If you "
"think you may need them, please read comments on script header itself."
msgstr ""

#. type: Plain text
#: user-manual.txt:1156
#, no-wrap
msgid ""
"*WARNING*: While building smtk2ssrf, a light version of _Subsurface_ is\n"
"built (usable but lacking a lot of features). So, if you commonly use the\n"
"built executable placed at ~/subsurface/build/, you will need to rebuild it "
"as\n"
"explained in this manual above.\n"
msgstr ""

#. type: Title =====
#: user-manual.txt:1157
#, no-wrap
msgid "Running"
msgstr ""

#. type: Plain text
#: user-manual.txt:1163
msgid ""
"_smtk2ssrf_ accepts 0, 2 or more parameters. If it is launched without "
"parameters in a graphical user interface, a simple window opens for choosing "
"the _.slg_ file(s) to import and a destination file to store the "
"_Subsurface_-formatted data into (see image below)."
msgstr ""

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

#. type: Plain text
#: user-manual.txt:1171
msgid ""
"Existing data in the destination file will be erased, so *DO NOT* use a "
"regular subsurface divelog file as a destination: rather, specify a *new* "
"filename as a destination."
msgstr ""

#. type: Plain text
#: user-manual.txt:1173
msgid ""
"If launched from a command line with two or more parameters, the format is "
"as follows:"
msgstr ""

#. type: Plain text
#: user-manual.txt:1175
#, no-wrap
msgid "\t$ smrtk2ssrf /input/file_1.slg /input/file_2.slg /output/file3.xml\n"
msgstr ""

#. type: Plain text
#: user-manual.txt:1183
msgid ""
"where _input_ is the directory containing the .slg file(s) and _output_ is "
"the directory where the _Subsurface_-formatted output is written to.  Files "
"_file_1.slg_ and _file_2.slg_ in the _input_ directory are imported and "
"stored in _file3.xml_ in the _output_ directory. Check any warning and error "
"messages in the console or in the graphical window: some may be relevant as "
"support for Galileo family of dive computers is still a work in progress."
msgstr ""

#. type: Title =====
#: user-manual.txt:1184
#, no-wrap
msgid "For the lazy: a web service to convert _SmartTrak_ to _Subsurface_"
msgstr ""

#. type: Plain text
#: user-manual.txt:1187
msgid "Open the website at:"
msgstr ""

#. type: Plain text
#: user-manual.txt:1189
msgid "_https://thetheoreticaldiver.org/rch-cgi-bin/smtk2ssrf.pl_"
msgstr ""

#. type: Plain text
#: user-manual.txt:1195
msgid ""
"This is a no-frills web service for converting _SmartTrak_ dive logs to "
"_Subsurface_. Select the browse button. This allows you to browse your "
"computer directories and to select the _SmartTrak_ divelog to be "
"converted. Once it has been selected, click the _Submit query_ button. After "
"a short while, a dialog box appears (image below) for saving the converted "
"file to the local computer."
msgstr ""

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

#. type: Title =====
#: user-manual.txt:1198
#, no-wrap
msgid "Merging the imported dives with the existing divelog"
msgstr ""

#. type: Plain text
#: user-manual.txt:1208
msgid ""
"Open the new file (generated in the previous steps) using _Subsurface_ and "
"check the dives and data.  If everything is fine, close the _.xml_ file and "
"open your regular divelog.  Then from the *Main Menu* select _Import -> "
"Import log file_ and choose the _.xml_ file containing the imported dives: "
"these will show in the *Dive List*, time ordered, along with the existing "
"dives.  The new dives, although time ordered, will keep the numbering system "
"from _SmartTrak_, so a renumbering action is needed. See the section on "
"xref:S_Renumber[Renumbering the dives] for instructions on this topic."
msgstr ""

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

#. type: Plain text
#: user-manual.txt:1223
msgid ""
"Importing dive information from _divelogs.de_ is simple, using a single "
"dialogue box. The _Import -> Import from Divelogs.de_ option should be "
"selected from the Main Menu. This brings up a dialogue box (see image *A* "
"below). Enter a user-ID and password for _divelogs.de_ and then select the "
"_Download_ button. Download from _divelogs.de_ starts immediately, "
"displaying a progress bar in the dialogue box. At the end of the download, "
"the success status is shown (see image *B*, below). The _Apply_ button "
"should then be selected, after which the imported dives appear in the "
"_Subsurface_ *Dive List* panel."
msgstr ""

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

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

#. type: Plain text
#: user-manual.txt:1238
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 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:1240
#, no-wrap
msgid "Importing dives in CSV format from dive computers or other dive log software"
msgstr ""

#. type: Plain text
#: user-manual.txt:1245
msgid ""
"_CSV_ files can be viewed using an ordinary text editor. A _CSV_ file is "
"normally organized into a single line that provides the headers (or _field "
"names_ or _column headings_) of the data columns, followed by the data, one "
"record per line."
msgstr ""

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

#. type: Plain text
#: user-manual.txt:1253
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 divemaster and information about cylinder "
"pressures before and after the dive, as well as comments about the dive. All "
"the data for a single dive go on a single line of text, following the order "
"of the column headings."
msgstr ""

#. type: Plain text
#: user-manual.txt:1262
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, 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:1265
msgid ""
"Before being able to import the _CSV_ data to _Subsurface_ *you need to know "
"a few things about the data being imported*:"
msgstr ""

#. type: Plain text
#: user-manual.txt:1273
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:1277
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:1279
msgid "Is the numeric information (e.g. dive depth) in metric or in imperial units?"
msgstr ""

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

#. type: Plain text
#: user-manual.txt:1298
#, no-wrap
msgid ""
"At the top left, there is a dropdown list containing pre- configured\n"
"settings for common dive computers and software packages.\n"
" If the _CSV_ file being imported originated from any of\n"
"these pre-configured items, select it. Otherwise use the _Manual Import_\n"
"option. The configuration panel also has dropdown lists for the "
"specification of the appropriate\n"
"field separator (Tab, comma or semicolon), the date format used in the _CSV_ "
"file,\n"
"the time units (seconds, minutes or minutes:seconds), as well as the unit "
"system\n"
"(metric or imperial). Selecting the appropriate options among these is "
"critical for\n"
"successful data import.\n"
msgstr ""

#. type: Plain text
#: user-manual.txt:1310
msgid ""
"Complete this by ensuring that all the data columns have the appropriate "
"column headings. The top blue row of the data table contains the column "
"headings found in the _CSV_ data file. The blue row of balloons immediately "
"above these contains the names understood by _Subsurface_. These balloons "
"can be moved using a drag-and-drop action. For instance, _Subsurface_ "
"expects the column heading for Dive number (\" # \") to be \"Dive # \". If "
"the column heading that _Subsurface_ expects is not in the blue row, drag "
"the appropriate balloon from the upper area and drop it in the appropriate "
"blue cell at the top of the table. For example, 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 \" # \", "
"depicted in the image below."
msgstr ""

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

#. type: Plain text
#: user-manual.txt:1317
msgid ""
"Continue in this way to ensure all the column headings in the blue row of "
"cells correspond to the headings listed in the top part of the dialogue.  "
"When finished, select the _OK_ button on the bottom right of the dialogue.  "
"The data from the _CSV_ file are imported and shown in the *Dive List* "
"panel."
msgstr ""

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

#. type: delimited block *
#: user-manual.txt:1335
msgid ""
"_CSV_ is an abbreviation for a data file format: _Comma-Separated "
"Values_. It is a file format that allows you to view or edit information "
"using a text editor like Notepad (Windows), gedit (Linux) or TextWrangler "
"(OS/X). There are two main advantages of the _CSV_ format.  First, the data "
"are easily editable as text without any proprietary software.  Second, all "
"information is human-readable, not obscured by any custom or proprietary "
"attributes that proprietary software inserts into files.  Because of its "
"simplicity the _CSV_ format is used as an interchange format between many "
"software packages, e.g. between spreadsheet, statistical, graphics, database "
"and diving software. Within _Subsurface_, _CSV_ files can also be used to "
"import information from other sources like spreadsheet-based dive logs and "
"some dive computers."
msgstr ""

#. type: delimited block *
#: user-manual.txt:1344
msgid ""
"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 "
"organized into a single line that provides the headers (or _field names_) of "
"the data columns, followed by the data, one record per line. Note that each "
"field name may comprise more than one word separated by spaces; for instance "
"_Dive site_, below. Here is an example of dive information for four dives "
"using a comma as a field separator:"
msgstr ""

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

#. type: delimited block *
#: user-manual.txt:1366
msgid ""
"It is clear why many people prefer the TAB-delimited format to the "
"comma-delimited format. The disadvantage is that you 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:1377
#, no-wrap
msgid ""
"\tDive Time (s)\tDepth (m)\tpO~2~ - Setpoint (Bar) \tpO~2~ - 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:1383
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 be "
"used in many contexts for importing data into a _Subsurface_ dive log.  "
"Knowing a few basic things about the content of the _CSV_ file helps with a "
"smooth import of the dives into _Subsurface_."
msgstr ""

#. type: Plain text
#: user-manual.txt:1396
msgid ""
"But, the _CSV_ import has a couple of caveats. Avoid some special characters "
"like ampersand (&), less than (<), greater than (>) and double quotes (\") "
"as part of the numbers or text within a cell. The file should use UTF-8 "
"character set, if using non-ASCII characters. Also the size of the _CSV_ "
"file might cause problems. Importing 100 dives at a time (_CSV dive "
"details_) works, but larger files might exceed the limits of the parser "
"used. When encountering problems with _CSV_ imports, first try with a "
"smaller file to make sure everything works."
msgstr ""

#. type: Title ===
#: user-manual.txt:1397
#, no-wrap
msgid "Importing Dive coordinates from a mobile device with GPS."
msgstr ""

#. type: Plain text
#: user-manual.txt:1401
msgid ""
"A smartphone with built-in GPS facilities can be used to store the locations "
"of dives.  This is performed by:"
msgstr ""

#. type: Plain text
#: user-manual.txt:1404
msgid ""
"Taking the mobile device along on the dive boat / liveabord while "
"automatically collecting dive site coordinate information."
msgstr ""

#. type: Plain text
#: user-manual.txt:1406
msgid ""
"Adding collected coordinate information to the dives using the "
"_Subsurface-mobile_ app."
msgstr ""

#. type: Plain text
#: user-manual.txt:1408
msgid ""
"Syncronising the logbook with the _Subsurface_ cloud using the "
"_Subsurface-mobile_ app."
msgstr ""

#. type: Plain text
#: user-manual.txt:1414
msgid ""
"Existing users might still be using the legacy _Companion app_. However, the "
"Companion App hasn't been under development in several years and has now "
"been removed from both Android and iOS app stores. The functionality is "
"fully integrated into _Subsurface-mobile_.  Please note that the old GPS fix "
"internet service will be shut down by the end 2018 at which point the "
"_Companion app_ will no longer be usable. Please switch to "
"_Subsurface-mobile_ instead."
msgstr ""

#. type: Title ====
#: user-manual.txt:1415
#, no-wrap
msgid "Storing and and using GPS locations using  _Subsurface-mobile_"
msgstr ""

#. type: Title =====
#: user-manual.txt:1417
#, no-wrap
msgid "Install _Subsurface-mobile_"
msgstr ""

#. type: Plain text
#: user-manual.txt:1423
msgid ""
"Find _Subsurface-mobile_ on Google Play and install it on an Android "
"device. The app is free. The iOS version is currently "
"experimental. _Subsurface-mobile_ has an extensive "
"https://subsurface-divelog.org/documentation/subsurface-mobile-user-manual[user "
"manual] accessible from within that app."
msgstr ""

#. type: Title =====
#: user-manual.txt:1424
#, no-wrap
msgid "Create a _Subsurface-mobile_ account"
msgstr ""

#. type: Plain text
#: user-manual.txt:1432
msgid ""
"This topic is discussed at length in the _Subsurface-mobile_ user manual. In "
"the Credentials screen of _Subsurface-mobile_ provide an e-mail address and "
"a user password that enables subsequent access. A PIN number is e-mailed "
"from the _Subsurface_ Internet server to the e-mail address that has been "
"provided.  Type the PIN into the appropriate text field in the Credentials "
"screen (see image below).  The _Subsurface_ Internet server notifies the "
"user that a new user has been registered."
msgstr ""

#. type: Plain text
#: user-manual.txt:1435
#, no-wrap
msgid ""
"*N.B.:* To successfully create a user account, the mobile device must have "
"Internet connectivity,\n"
"either through the cellular network or via wifi.\n"
msgstr ""

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

#. type: Title =====
#: user-manual.txt:1439
#, no-wrap
msgid "Configure auto-collecting of GPS coordinates"
msgstr ""

#. type: Plain text
#: user-manual.txt:1445
msgid ""
"Activate the main menu of _Subsurface-mobile_ by selecting the \"hamburger\" "
"menu button at the bottom left of the _Subsurface-mobile_ screen (see image "
"above), then select _GPS_ -> _Preferences_ (see image below). The collection "
"of GPS locations is done in the background and automatically, using two "
"settings:"
msgstr ""

#. type: Plain text
#: user-manual.txt:1447
msgid ""
"_Time threshold._ (minutes). The app will try to get a location every X "
"minutes"
msgstr ""

#. type: Plain text
#: user-manual.txt:1449
msgid "_Distance threshold._ (meters). Minimum distance between two locations."
msgstr ""

#. type: Plain text
#: user-manual.txt:1458
#, no-wrap
msgid ""
"*How are GPS coordinates collected?* Assuming the diver sets 5 minutes and "
"50\n"
"meters in the settings above, the app will start by recording a location at "
"the current\n"
"location, followed by another one at every 5 minutes *or* every time you "
"move 50 m\n"
"from previous location, whichever happens first.\n"
"If subsequent locations are within a radius of 50 meters from the previous "
"one,\n"
"a new location is not saved. If the diver is not moving, only one location "
"is\n"
"saved, at least until the _Time-threshold_ period has elapsed.\n"
"If the diver moves, a trace of the route is obtained by saving a location "
"every 50 meters.\n"
msgstr ""

#. type: Title =====
#: user-manual.txt:1459
#, no-wrap
msgid "Activate the automated recording of GPS locations"
msgstr ""

#. type: Plain text
#: user-manual.txt:1464
msgid ""
"The _Subsurface-mobile_ GPS menu has an option at the bottom labled _Run "
"location service_ (see image below). Selecting this starts the automated "
"recording of GPS positions."
msgstr ""

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

#. type: Title =====
#: user-manual.txt:1467
#, no-wrap
msgid "After the dive, stop the automated recording of GPS locations"
msgstr ""

#. type: Plain text
#: user-manual.txt:1470
msgid ""
"Select the menu option _Disable location service_ at the bottom of the "
"_Subsurface-mobile_ GPS menu."
msgstr ""

#. type: Title =====
#: user-manual.txt:1472
#, no-wrap
msgid "Apply the stored GPS locations to dives on the _Subsurface_ dive list."
msgstr ""

#. type: Plain text
#: user-manual.txt:1481
msgid ""
"_Subsurface_ collects the first GPS location recorded after the start of a "
"dive (obtained within _Subsurface_ from either the dive computer or from the "
"manually-entered dive information) and before the end of a dive. These "
"coordinates are shown in the _Coordinates_ field of the dive site panel for "
"each dive. Within the dive site panel, provide a name for the coordinates "
"that have been assigned to the dive, following the instructions under the "
"heading above xref:S_locations[_Location_ management]."
msgstr ""

#. type: Plain text
#: user-manual.txt:1486
msgid ""
"The "
"https://subsurface-divelog.org/documentation/subsurface-mobile-user-manual[user "
"manual for _Subsurface-mobile_] (accessible from within that app)  contains "
"detailed instructions for performing the collection of GPS data and for "
"managing, uploading and synchronising this information."
msgstr ""

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

#. type: Plain text
#: user-manual.txt:1497
msgid ""
"Many (if not most) divers take photographs or videos during a dive. We term "
"these as _media_, meaning either photos or videos. _Subsurface_ allows the "
"storage and display of these media for each dive. Images are superimposed on "
"the dive profile at the times during the dive when they were taken. Media "
"can be viewed either from the dive profile or from the _Media_ tab in the "
"*Notes Panel*. _Subsurface_ allows viewing of photographs as well as video "
"files in a unified interface."
msgstr ""

#. type: Title ====
#: user-manual.txt:1498
#, no-wrap
msgid "Loading media and synchronizing between dive computer and camera"
msgstr ""

#. type: Plain text
#: user-manual.txt:1506
msgid ""
"Right-click on a dive or on a group of dives on the dive list, bringing up "
"the xref:S_DiveListContextMenu[Dive list context Menu].  Select the "
"appropriate option to import media either from file or from the "
"Internet. The system file browser appears. Select the folder and media that "
"need to be loaded into _Subsurface_ and click the _Open_ button. Towards the "
"bottom of the file browser is a filter that allows showing media (photos and "
"videos), only photographs, only videos, or all files. Choose the appropriate "
"option."
msgstr ""

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

#. type: Plain text
#: user-manual.txt:1514
msgid ""
"If media are imported from the Internet, provide a URL pointing to a single "
"media.  If the URL points to a directory, no images are imported: images "
"from the Internet need to be imported one at a time. If media are loaded "
"from the Internet, _Subsurface_ assumes there is an Internet connection each "
"time this item is viewed within _Subsurface_."
msgstr ""

#. type: Plain text
#: user-manual.txt:1522
msgid ""
"Having selected the local folder or Internet image to be imported, the time "
"synchronization dialog appears (see image below). The time synchronization "
"is not perfect between the dive computer used during a dive and the camera "
"used during that same dive. These two devices often differ by several "
"minutes. _Subsurface_ attempts to synchronize them so that the exact times "
"of media can be used to position media on the dive profile."
msgstr ""

#. type: Plain text
#: user-manual.txt:1524
msgid "_Subsurface_ synchronizes camera with dive computer in three ways:"
msgstr ""

#. type: Plain text
#: user-manual.txt:1527
#, no-wrap
msgid ""
"*Pro-actively*: Before the dive, ensure synchronization of the dive computer "
"time settings with\n"
"the time settings of the camera by changing the date-time settings on one or "
"both of these devices.\n"
msgstr ""

#. type: Plain text
#: user-manual.txt:1538
#, no-wrap
msgid ""
"*Manually*: Writing down the exact camera time at the start of a dive allows "
"using the\n"
"difference in time between the two devices. As long as the device\n"
"settings for time has not been changed in either device, the times of\n"
"both devices after the dive or even at the end of the day allows manually "
"setting the time\n"
"difference in the _Time shift_ dialog (see image below). Towards the top of "
"the dialog is a time\n"
"setting tool immediately under the heading _Shift times of image(s) by_, in "
"the image 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 and select the _Earlier_ radio button.\n"
"This is appropriate, since the media 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 synchronization is done.\n"
msgstr ""

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

#. type: Plain text
#: user-manual.txt:1557
#, no-wrap
msgid ""
"*By photograph*: There is a very slick way of achieving synchronization, "
"requiring a\n"
"photograph of the face of the dive computer showing the time. _Subsurface_ "
"gets\n"
"the exact time the photograph was taken, using the metadata the camera "
"stores within\n"
"each photo and compares this with the time visible on the photo. To do this, "
"use the\n"
"bottom half of the _Time shift_ dialog. In this case the top part of the "
"dialog is ignored. Click on\n"
"the horizontal bar called _Select image of dive computer showing time_. This "
"brings up\n"
"a file browser for selecting 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 was taken. Now set the date-time dialog to the left of "
"the photo\n"
"so it reflects the date and time of the dive computer in the photo. When "
"the\n"
"date-time tool has been set, _Subsurface_ knows exactly what the time "
"difference between\n"
"camera and dive computer is, and it can synchronize the devices. The image "
"below shows\n"
"a photograph of the face of the dive computer and with the date-time tool "
"set to the\n"
"date-time.\n"
msgstr ""

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

#. type: Plain text
#: user-manual.txt:1564
msgid ""
"If the timestamp of a photograph or video is more than 30 minutes before or "
"after the dive, it is not placed on the dive profile (see the red warning in "
"the image above). However, If the appropriate checkbox is selected (see "
"image above) these images can still be placed on the _Media_ tab of the "
"*Notes* panel so that all media associated with a dive are visible, "
"including images taken before or after the dive."
msgstr ""

#. type: Title ====
#: user-manual.txt:1567
#, no-wrap
msgid "Viewing the media"
msgstr ""

#. type: delimited block *
#: user-manual.txt:1571
#, no-wrap
msgid "*Ensuring that thumbnails are created for video files*\n"
msgstr ""

#. type: delimited block *
#: user-manual.txt:1578
msgid ""
"Within a panel _Subsurface_ represents media by means of thumbnails "
"(i.e. small versions of images that allows listing many images. For a "
"photograph, a thumbnail can easily be created because the image is well "
"defined. But, since a video comprises many images, the question arises of "
"which image should be used for the thumbnail. Two actions are required to "
"create thumbnails of videos:"
msgstr ""

#. type: delimited block *
#: user-manual.txt:1580
msgid "The appropriate settings need to be set in the _Preferences_."
msgstr ""

#. type: delimited block *
#: user-manual.txt:1582
msgid ""
"The program _ffmpeg_ needs to be installed in the computer that runs "
"Subsurface."
msgstr ""

#. type: delimited block *
#: user-manual.txt:1584
msgid "Full details are provided in <<S_APPENDIX_F,APPENDIX F>>."
msgstr ""

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

#. type: Plain text
#: user-manual.txt:1589
msgid "the _Media_ tab of the *Notes Panel* (left part of image below)."
msgstr ""

#. type: Plain text
#: user-manual.txt:1593
msgid ""
"as tiny icons (stubs) on the dive profile at the appropriate positions "
"reflecting the time each photograph or video was taken.  To view the media "
"on the dive profile, activate the _Toggle media_ button in the tool bar to "
"the left of the dive profile:"
msgstr ""

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

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

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

#. type: Plain text
#: user-manual.txt:1602
msgid ""
"Hover the mouse over any of the media stubs. A thumbnail image is shown of "
"the appropriate media. See the image below:"
msgstr ""

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

#. type: Plain text
#: user-manual.txt:1612
msgid ""
"Clicking on the thumbnail brings up a full size photo or video overlaid on "
"the _Subsurface_ window, allowing a good view of the media (see the image "
"below). *Note* that the thumbnail on the dive profile has a small dustbin "
"icon in the bottom right hand corner (see image above). Selecting the "
"dustbin removes the image from the dive. Be careful when clicking on a "
"thumbnail. Images can also be deleted using the _Media_ tab (see text "
"below)."
msgstr ""

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

#. type: Title ====
#: user-manual.txt:1615
#, no-wrap
msgid "The _Media_ tab"
msgstr ""

#. type: Plain text
#: user-manual.txt:1627
msgid ""
"Media associated with a dive are shown as thumbnails in the _Media_ tab of "
"the *Notes Panel*. Media taken in rapid succession during a dive (therefore "
"sometimes with large overlap on the dive profile) can easily be accessed in "
"the _Media_ tab. This tab serves as a tool for individually accessing the "
"media of a dive, while the stubs on the dive profile show when during a dive "
"when a photo/video was taken. The size of the thumbnails in the _Media_ tab "
"can be changed using the _Zoom level_ slider at the bottom of the "
"panel. Single-click a thumbnail in the _Media_ panel to select a "
"photo/video. Double-click a thumbnail to view the full-sized image or play "
"the video, overlaying the _Subsurface_ window. Delete media from the _Media_ "
"panel by selecting it (single-click) and then by pressing the _Del_ key on "
"the keyboard. This removes it BOTH from the _Media_ tab as well as the dive "
"profile."
msgstr ""

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

#. type: Plain text
#: user-manual.txt:1637
msgid ""
"Most underwater photographers store media on an external drive. If such a "
"drive can be mapped by the operating system (almost always the case) the "
"media can be directly accessed by _Subsurface_. This eases the interaction "
"between _Subsurface_ and an external repository of media. When associating a "
"dive profile with media from an external drive, the normal procedure of "
"selection and synchronization (see text above) is used.  After the external "
"drive has been disconnected, _Subsurface_ cannot access these media any "
"more.  If the display of media is activated (using the toolbox icon to the "
"left of the _Dive Profile_), the program shows only the thumbnails and the "
"images cannot be viewed at full-screen size.  If the external drive with the "
"media is re-connected, the media can be seen in the normal way."
msgstr ""

#. type: Title ====
#: user-manual.txt:1638
#, no-wrap
msgid "Finding out which dives have associated media."
msgstr ""

#. type: Plain text
#: user-manual.txt:1644
msgid ""
"Inspecting each individual dive in order to determine whether there are "
"associated media can be time consuming. There is a rapid way of seeing which "
"dives have associated media and which not: activate the _Media_ checkbox in "
"the dropdown list obtained by right-clicking on the header bar of the "
"*Divelist*. In the *Divelist*, all dives with associated media have an icon "
"indicating whether the media were taken during the dive, just before/after "
"the dive or both during and before/after the dive.  More information is "
"provided in the section dealing with <<S_Divelist_columns, photo icons on "
"the *Divelist*>>."
msgstr ""

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

#. type: Plain text
#: user-manual.txt:1655
#, no-wrap
msgid ""
"After a photograph or video has been loaded into _Subsurface_ and associated "
"with a specific dive,\n"
"_Subsurface_ saves the path to the directory where the media lie as well as "
"the file name of the each photo/video,\n"
"in order to find it when the dive is opened again.\n"
"If the media or the whole media collection is moved to another drive or to a "
"different\n"
" machine, the path to the media changes. Now, _Subsurface_ looks for the "
"photos/videos at their original location before they were moved,\n"
"cannot find them and cannot display them. Because, after moving media, large "
"numbers of files\n"
" may need to be deleted and re-imported from the new disk, _Subsurface_ can "
"locate the media based on their filename and path.\n"
msgstr ""

#. type: Plain text
#: user-manual.txt:1661
#, no-wrap
msgid ""
"This is done by selecting from the Main Menu: _File ->      Find moved "
"images_. This brings up a window within\n"
"which the searching of the images can be controlled. The search is started "
"by clicking on _Select folder and scan_.\n"
"Since recorded during different dive trips might have the same filename, the "
"names of the parent folders are likewise compared.\n"
"Therefore, the root folder of the NEW picture collection should be "
"chosen. For finer control, it is possible to search\n"
"only for media of the currently selected dive(s) by selecting the "
"appropriate option.\n"
msgstr ""

#. type: Plain text
#: user-manual.txt:1665
msgid ""
"After the searching has completed, the original filenames and the new "
"locations of the photographs will be shown.  The matching parts of the paths "
"are emphasized. Media that are found at their known positions are not "
"listed. The proposed changes can be applied by clicking _Apply_ or rejected "
"by clicking _Cancel_."
msgstr ""

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

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

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

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

#. type: Plain text
#: user-manual.txt:1681
msgid ""
"_Subsurface_ easily handles dives involving more than one "
"cylinder. Multi-cylinder diving usually happens (a) if a diver doesn’t have "
"enough gas for the complete dive in a single cylinder; (b) if a diver needs "
"more than one gas mixture because of the depth or the decompression needs of "
"the dive. For this reason multi-cylinder dives are often used by technical "
"divers who dive deep or long. As far as _Subsurface_ is concerned, there are "
"only two types of information that need to be provided:"
msgstr ""

#. type: Plain text
#: user-manual.txt:1685
#, 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 its size and pressure, as well as the gas composition within "
"it.\n"
msgstr ""

#. type: Plain text
#: user-manual.txt:1691
#, no-wrap
msgid ""
"*Record the times at which the switch from one cylinder to another was "
"done:* This is information\n"
"tracked by some dive computers (provided the diver indicated these changes "
"to the dive computer\n"
"by pressing specific buttons). If the dive computer does not provide the "
"information, the diver has to\n"
"record these changes using a different method, e.g. writing it on a slate or "
"by creating a bookmark on the dive\n"
"computer.\n"
msgstr ""

#. type: Plain text
#: user-manual.txt:1699
#, 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"
"*gas bar* button in the toolbar has been activated, the cylinder switches "
"are also indicated in the\n"
"gas bar (image below).\n"
msgstr ""

#. type: Plain text
#: user-manual.txt:1703
msgid ""
"When this is complete, _Subsurface_ indicates the appropriate use of "
"cylinders in the dive profile.  Below is a two-cylinder dive, starting off "
"with EAN28, then changing cylinders to EAN50 after 26 minutes for "
"decompression."
msgstr ""

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

#. type: Plain text
#: user-manual.txt:1713
msgid ""
"Several dive computers perform automatic recording of cylinder pressure. In "
"this case no manual intervention is needed.  Older dive computers "
"(e.g. Uwatec Galileo, several Suunto models) handle more than one pressure "
"transducer on cylinders, switching from one sensor to another as the diver "
"switches among cylinders and providing a sequential record of cylinders "
"pressures during a dive. Some of the latest models (e.g. Shearwater Perdix "
"AI, Scubapro G2) record two or more pressure transducers concurrently and "
"continuously during the whole dive. In these cases _Suburface correctly "
"interprets the data.  There is continuous effort within the _Subsurface_ "
"development team to add new dive computer models to those that can be "
"downloaded from and to represent cylinder pressures correctly. Regardless of "
"the type of sensor handling of dive computers, technical divers are likely "
"to use both automated and manual methods of cylinder pressure logging when "
"more than two gases are used. However, automated recording of cylinder "
"pressure simplifies logging of sidemount dives (where two cylinders are "
"used). See the "
"link:https://subsurface-divelog.org/documentation/supported-dive-computers/[list "
"of supported dive computers]."
msgstr ""

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

#. type: Plain text
#: user-manual.txt:1721
msgid ""
"Sidemount diving is just another form of multi-cylinder diving, often with "
"both or all cylinders having the same gas mixture. Although it’s a popular "
"configuration for cave divers, sidemount diving can be done by recreational "
"divers who have completed the appropriate training. See the comments in the "
"last paragraph, above, about automated recording of cylinder "
"pressures. Manual logging of cylinder pressures during sidemount involves "
"three steps, exactly as with multi-cylinder dives above:"
msgstr ""

#. type: Plain text
#: user-manual.txt:1730
#, 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 "
"between these different\n"
"cylinders. In contrast, many dive computers that allow gas switching only "
"distinguish between different\n"
"_gases_ used, not among different _cylinders_ used. This means when "
"sidemount dives are downloaded\n"
"from these dive computers, the switching event between cylinders with the "
"same gas is not downloaded. This may mean\n"
"that a diver may have to keep a written log of cylinder switch times using a "
"slate, or (if the dive computer\n"
"has the capability) marking each cylinder switch with a bookmark that can be "
"retrieved later. Returning\n"
"from a dive with the times of cylinder changes is the only tedious part of "
"logging sidemount dives.\n"
msgstr ""

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

#. type: Plain text
#: user-manual.txt:1743
#, 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 shown on the dive profile.\n"
"Cylinder changes are recorded by right-clicking at the appropriate point on "
"the dive profile, then\n"
"selecting _Add gas change_. A list of the appropriate cylinders is shown "
"with the\n"
"currently used cylinder greyed out. In the image below Tank 1 is greyed out, "
"leaving only Tank 2\n"
"to be selected. Select the appropriate cylinder. The cylinder change is then "
"shown on the dive\n"
"profile with a cylinder symbol. If the *gas bar* is activated using the "
"toolbar to the left of the\n"
"profile, then the cylinder change is also shown on the gas 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:1744
#, no-wrap
msgid "images/sidemount1.jpg"
msgstr ""

#. type: Title ====
#: user-manual.txt:1747
#, no-wrap
msgid "Passive semi-closed circuit rebreather (pSCR) dives"
msgstr ""

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

#. type: Plain text
#: user-manual.txt:1759
msgid ""
"Passive semi-closed rebreathers (pSCR) are a technical advance in diving "
"equipment that recirculates the breathing gas a diver uses, while removing "
"carbon dioxide from the exhaled gas. While a small amount (typically a "
"tenth) of the exhaled breathing gas is released into the water, a small "
"amount of fresh gas is released from the driving gas cylinder.  A diver "
"using a single cylinder of breathing gas can therefore dive for much longer "
"periods than using a recreational open-circuit configuration. With pSCR "
"equipment, a very small amount of breathing gas is released every time the "
"diver inhales. With active SCR (aSCR) equipment, in contrast, a small amount "
"of breathing gas is released continuously from the driving cylinder."
msgstr ""

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

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

#. type: Plain text
#: user-manual.txt:1767
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:1774
msgid ""
"In pSCR diving, the inspired gas often has a pO~2~ below that of the fresh "
"gas from cylinder. This is because fresh gas is only supplied at a slow rate "
"and the diver continuously uses oxygen from the loop for metabolism, "
"resulting in the so-called \"pO~2~ drop over the mouthpiece\". For pSCR dive "
"profiles the dive ceiling is adjusted for this oxygen drop, and often "
"requires longer decompression periods. Below is a dive profile of a pSCR "
"dive using EAN36 as bottom gas and oxygen for decompression. Note that this "
"dive lasted over two hours."
msgstr ""

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

#. type: Plain text
#: user-manual.txt:1791
msgid ""
"_Visualising the pO~2~ drop_: The difference between the pO~2~ of the fresh "
"cylinder gas and the pO~2~ in the loop can be visualised in _Subsurface_ by "
"opening the _Profile_ panel in the _File -> Preferences_ menu item and then "
"providing suitable information in the section labelled _pSCR options_. The "
"_pSCR metabolic rate_ is your rate of oxygen metabolism in liters/min "
"(commonly between 0.5 and 2.5). The _Dilution ratio_ is the ratio indicating "
"how much gas in the loop is replaced with fresh gas, relative to the gas "
"being breathed (common values are between 1:3 and 1:10). These values are "
"also used when planning pSCR dives. If the oxygen content of the loop is not "
"recorded by an oxygen sensor, _Subsurface_ estimates the pO~2~ in the loop "
"using the information supplied above. This pO~2~ is shown as the green line "
"representing the oxygen partial pressure in the dive profile. If the oxygen "
"pressure in the loop is measured using an oxygen sensor connected to a dive "
"computer, this information is probably recorded by the dive computer and "
"these measured pO~2~ values are shown on the dive profile. In addition, the "
"_Preferences_ panel allows one to activate a checkbox labelled _Show "
"equivalent OC pO~2~ with pSCR pO~2~_. This activates display of the pO~2~ in "
"the fresh gas from the cylinder (an orange line). The vertical distance "
"between the orange graph and the green graph indicates the \"pO~2~ drop over "
"the mouthpiece\". Much of pSCR diving involves managing this pO~2~ "
"difference."
msgstr ""

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

#. type: Plain text
#: user-manual.txt:1806
msgid ""
"_pSCR and bailout_: Gases used in pSCR often yield very low pO~2~ values in "
"shallow water. For this reason the diver often completes the shallow "
"sections of a dive using open circuit (OC) rather than the rebreather. In "
"this case parts of the dive are performed OC, while the rest of the dive is "
"performed on the pSCR loop. To indicate such changes in divemode, "
"right-click on the dive profile at the appropriate time. From the context "
"menu, select _Change divemode_ and choose the appropriate option (see image "
"on left). Some dive computers record such changes in divemode as part of the "
"dive log.  The appropriate icon is shown on the depth profile (see image "
"below).  Below is a pSCR dive with the shallow sections using OC. An OC "
"divemode was entered right at the start, followed by a change to pSCR at "
"18m. During the ascent, there was a bailout to OC at 14m. Note, for the OC "
"sections, the pO~2~ is identical to the OC-pO~2~ whereas for the pSCR "
"section, the pO~2~ (green line)  differs from the OC-pO~2~ (orange line)."
msgstr ""

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

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

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

#. type: Plain text
#: user-manual.txt:1817
msgid ""
"Closed system rebreathers also recirculate gas that has been "
"breathed. However, they use advanced technology to maintain a breathable "
"oxygen concentration:"
msgstr ""

#. type: Plain text
#: user-manual.txt:1818
msgid "remove carbon dioxide from the exhaled gas."
msgstr ""

#. type: Plain text
#: user-manual.txt:1829
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, as well as Shearwater dive computers "
"connected to CCR systems. In contrast to a conventional recreational dive "
"computer, a CCR system computer usually 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 individual CCR dive profiles in the same way "
"it imports dive log data from other digital databases: one dive at a "
"time. However, the Shearwater based CCR systems are different in this "
"respect and allow multi-dive downloads."
msgstr ""

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

#. type: Plain text
#: user-manual.txt:1849
msgid ""
"For Shearwater CCR controllers, or independent Shearwater CCR logs, just "
"download the dive log as would be the case for non-CCR dives. _Subsurface_ "
"interprets the CCR dive log correctly.  Except for Shearwater CCR dive "
"computers, CCR dive data are currently obtained from the proprietary "
"software provided when purchasing CCR dive equipment. See the section "
"dealing with xref:S_ImportingAlienDiveLogs[Importing dive information from "
"other digital sources] and "
"<<_appendix_b_dive_computer_specific_information_for_importing_dive_information,Appendix "
"B>> for more complete information. Use that software to download the dive "
"data into a known directory. 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 (labeled _Filter:_) of appropriate "
"devices that currently include (Poseidon) MkVI or APD log viewer "
"files. Import for other CCR equipment is under active development. Having "
"selected the appropriate CCR format and the directory where the original "
"dive logs have been stored from the CCR dive computer, select a particular "
"dive log file (in the case of the MkVI it is a file with a .txt "
"extension). After selecting the appropriate dive log, click the _Open_ "
"button at the bottom right hand of the universal import dialogue.  The "
"selected dive is imported to the _Subsurface_ dive list."
msgstr ""

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

#. type: Plain text
#: user-manual.txt:1860
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:1862
msgid "For TWO O~2~ sensors the mean value of the two sensors are given."
msgstr ""

#. type: Plain text
#: user-manual.txt:1866
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 false. If one of the three sensors provides false "
"data, it is ignored."
msgstr ""

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

#. type: Plain text
#: user-manual.txt:1878
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 boxes in the _Preferences_ panel "
"(accessible by selecting xref:S_CCR_options[_File -> Preferences -> "
"Profile_]). 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 checked."
msgstr ""

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

#. type: Plain text
#: user-manual.txt:1886
msgid ""
"Checking any of these boxes allows the display of additional oxygen-related "
"information whenever the pO~2~ toolbar button on the _Profile_ panel is "
"activated.  The first checkbox allows the display of setpoint "
"information. This is an orange 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:1887
#, no-wrap
msgid "images/CCR_setpoint_f20.jpg"
msgstr ""

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

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

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

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

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

#. type: Plain text
#: user-manual.txt:1905
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:1909
msgid ""
"_Events_: Several events are logged, e.g. switching the mouthpiece to open "
"circuit.  These events are indicated by yellow triangles and, if you hover "
"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:1929
msgid ""
"_Bailout_: Bailout events during a CCR dive can be recorded in a "
"_Subsurface_ divelog. Right-click on the dive profile to generate a dive "
"profile context menu. Select _Change divemode_ and choose the appropriate "
"bailout option (probably OC). An appropriate icon is shown on the depth "
"profile (see image below). In most CCR equipment it is also possible to "
"bailout to pSCR, especially in cases where the electronics died and the "
"diluent supply is limited. This can also be reflected in the dive log and "
"Subsurface will calculate and graph the appropriate pO~2~ values. The case "
"during CCR training is more complex if the instructor prefers a low setpoint "
"such as 0.7 to be maintained during bailout. In this case the CCR equipment "
"maintains the low setpoint and overrides the OC or pSCR conditions. In such "
"cases it is probably more accurate not to record a bailout event in the dive "
"log since _Subsurface_ will calculate pO~2~ values based on the erroneous "
"assumption that there is no setpoint.  Below is a dive profile for a CCR "
"dive with bailout at 57 minutes. In this profile the green pO~2~ graph "
"diverges from the setpoint value and reflects the pO~2~ in the OC diluent "
"gas (in this case air).  The pO~2~ in the loop (shown as a meandering graph "
"for each oxygen sensor) is irrelevant because the actual inspired gas comes "
"directly from the diluent cylinder. In cases where bailout occurs using a "
"stage cylinder, indicate the bailout as well as the gas change event and "
"_Subsurface_ will calculate all the appropriate pO~2~ values. Some dive "
"computers record bailout events as well as gas change events: in this case "
"the events are shown automatically in the dive log."
msgstr ""

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

#. type: Plain text
#: user-manual.txt:1937
msgid ""
"_Deco ceiling_: 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:1938 user-manual.txt:2337
#, no-wrap
msgid "images/icons/cceiling.jpg"
msgstr ""

#. type: Plain text
#: user-manual.txt:1943
msgid ""
"The default color of the computer-generated deco ceiling is white. This can "
"be set to red by checking the appropriate check box after selecting _File -> "
"Preferences -> Profile_.  The profile above indicates the dive "
"computer-generated deco ceiling in red."
msgstr ""

#. type: Plain text
#: user-manual.txt:1951
msgid ""
"_Cylinder pressures_: Some CCR dive computers like Poseidon 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 agreement from the readings of "
"the two oxygen sensors."
msgstr ""

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

#. type: Plain text
#: user-manual.txt:1957
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:1960
msgid ""
"More equipment-specific procedures and information for downloading CCR dive "
"logs for Poseidon 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:1961
#, no-wrap
msgid "Obtaining more information about dives entered into the logbook"
msgstr ""

#. type: Title ===
#: user-manual.txt:1963
#, no-wrap
msgid "Using the Dive Map to obtain more dive information"
msgstr ""

#. type: Plain text
#: user-manual.txt:1966
msgid ""
"The Dive Map has a number of buttons useful for manipulation several aspects "
"of a dive. These are:"
msgstr ""

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

#. type: Plain text
#: user-manual.txt:1971
msgid ""
"Select this button to show the Dive Map as a satellite image or as a Google "
"Maps representation."
msgstr ""

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

#. type: Plain text
#: user-manual.txt:1975
msgid "Zoom in. Select a smaller area of the map."
msgstr ""

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

#. type: Plain text
#: user-manual.txt:1979
msgid "Zoom out. Select a larger area of the map."
msgstr ""

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

#. type: Plain text
#: user-manual.txt:1984
msgid ""
"The \"Hamburger\" button on the top right-hand of the Dive Map activates the "
"Map menu. The items are:"
msgstr ""

#. type: Plain text
#: user-manual.txt:1987
msgid ""
"Open location in _Google Maps_. Open the location of the active dive in a "
"separate Google Maps window with the dive site indicated by a Google Maps "
"teardrop marker."
msgstr ""

#. type: Plain text
#: user-manual.txt:1990
msgid ""
"Copy location to clipboard (decimal). Copy the coordinates of the active "
"dive to the clipboard in decimal degrees e.g. -25.933905 30.710572"
msgstr ""

#. type: Plain text
#: user-manual.txt:1993
msgid ""
"Copy location to clipboard (sexagesimal). Copy the coordinates of the active "
"dive to the clipboard in sexagecimal, e.g. 25°56'02.058\"S 30°42'38.059\"E"
msgstr ""

#. type: Plain text
#: user-manual.txt:1996
msgid ""
"Select visible dive locations. In the Dive List panel, highlight all the "
"dive sites visible in the Dive Map. This allows easy selection of the dives "
"within a particular geographical area to inspect them or to calculate "
"statistics for them."
msgstr ""

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

#. type: Plain text
#: user-manual.txt:2004
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: Named 'icon' AttributeList argument for style 'icon'
#: user-manual.txt:2005
#, no-wrap
msgid "images/icons/info.jpg"
msgstr ""

#. type: Plain text
#: user-manual.txt:2011
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.  Refer to "
"xref:SAC_CALCULATION[Appendix F] for more information."
msgstr ""

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

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

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

#. type: Plain text
#: user-manual.txt:2035
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 for only that dive are given. This tab shows the number of dives "
"selected, the total amount of dive time in these dives, as well as the "
"minimum, maximum and mean for the dive duration, water temperature and "
"surface air consumption (SAC). It also shows the depth of the shallowest and "
"deepest dives of those selected."
msgstr ""

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

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

#. type: Plain text
#: user-manual.txt:2050
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, allowing control of several display options. The "
"functions of these buttons are described below. The main item in the Dive "
"Profile is the graph of dive depth as a function of time. In addition to "
"depth, it also shows the ascent and descent rates compared to the "
"recommended speed of going up or down in the water column. This information "
"is given using different colors:"
msgstr ""

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

#. type: Plain text
#: user-manual.txt:2062
msgid ""
"The profile also includes depth readings for the peaks and troughs in the "
"graph.  So users should see the depth of the deepest point and other "
"peaks. Mean depth is plotted as a grey line, indicating mean dive depth up "
"to a particular moment during the dive."
msgstr ""

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

#. type: Plain text
#: user-manual.txt:2068
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 increases the size of the dive profile to fill the area of "
"the panel."
msgstr ""

#. type: Plain text
#: user-manual.txt:2071
#, no-wrap
msgid ""
"*Water temperature* is shown as a blue line with temperature values\n"
"placed adjacent to significant changes.\n"
msgstr ""

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

#. type: Plain text
#: user-manual.txt:2080
msgid ""
"The Information box displays a large range of information about the dive "
"profile. Normally the Information Box is located to the top left of the "
"*Dive Profile* panel. 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:2081
#, no-wrap
msgid "images/InfoBox2.jpg"
msgstr ""

#. type: Plain text
#: user-manual.txt:2097
msgid ""
"When the mouse points inside the *Dive Profile* panel, the information box "
"expands and shows many data items. In this situation, the data reflect the "
"time point along the dive profile shown by the mouse cursor (see right-hand "
"part of figure (*B*) above where the Information Box reflects the situation "
"at the position of the cursor [arrow] in that image). Moving the cursor "
"horizontally lets the Information Box show information for any point along "
"the dive profile. It 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, also as gas density in "
"g/l), decompression requirements at that instant in time (Deco), time to "
"surface (TTS), the calculated ceiling, as well as of the statistics in the "
"Information Box, shown as four buttons on the left of the profile "
"panel. These are:"
msgstr ""

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

#. type: Plain text
#: user-manual.txt:2105
msgid ""
"Show 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 -> "
"Profile_ and edit the text box _pO~2~ in calculating MOD_.  When diving "
"below the MOD there is a markedly increased risk of exposure to the dangers "
"of oxygen toxicity."
msgstr ""

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

#. type: Plain text
#: user-manual.txt:2117
msgid ""
"Show 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 a diver has exceeded the NDL and "
"decompression is required (that is, there is an ascent ceiling above the "
"diver) then TTS gives the number of minutes required before the diver can "
"surface. TTS includes ascent time as well as decompression time. Even if the "
"profile contains several gas switches, TTS at a specific moment during the "
"dive is calculated using the current gas.  TTS longer than 2 hours is not "
"accurately calculated and Subsurface only indicates _TTS > 2h_."
msgstr ""

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

#. type: Plain text
#: user-manual.txt:2126
msgid ""
"Show the *Surface Air Consumption (SAC)*, an indication of the "
"surface-normalized respiration rate of a diver. The value of SAC is less "
"than the real respiration rate because a diver at 10m uses breathing gas at "
"a rate roughly double that of the equivalent rate at the surface. SAC gives "
"an indication of breathing gas consumption rate independent of the depth of "
"the dive, so the respiratory rates of different dives can be compared. The "
"units for SAC is liters/min or cubic ft/min."
msgstr ""

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

#. type: Plain text
#: user-manual.txt:2142
msgid ""
"Show the *Equivalent Air Depth (EAD)* for nitrox dives as well as the "
"*Equivalent Narcotic Depth (END)* for trimix dives. These are important to "
"divers 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 equaling 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 equaling the END."
msgstr ""

#. type: Plain text
#: user-manual.txt:2149
msgid ""
"If at some point a isobaric counter diffusion situation is encountered in "
"the leading tissue (defined to be a moment in time where helium is "
"off-gassing while nitrogen is on-gassing and the net effect is on-gassing) "
"this is indicated in the infobox as well. Note that this condition not only "
"depends on the gas that is currently breathed but on the tissue loadings as "
"well."
msgstr ""

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

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

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

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

#. type: Plain text
#: user-manual.txt:2168
msgid ""
"The light green area indicates the gas pressure, with the top margin of the "
"light green area showing the total gas pressure of ALL gases 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:2174
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 equilibrium "
"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:2178
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, with fast tissues on the left hand side."
msgstr ""

#. type: Plain text
#: user-manual.txt:2184
msgid ""
"The top black horizontal line indicates the inert gas pressure limit "
"determined by 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 _Profile_ "
"tab of the *Preferences Panel* of _Subsurface_."
msgstr ""

#. type: Plain text
#: user-manual.txt:2188
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 a significant risk of decompression "
"sickness."
msgstr ""

#. type: Plain text
#: user-manual.txt:2191
msgid ""
"These five values are shown on the left in the image above. The way the Gas "
"Pressure Bar Graph changes during a dive can be seen on the right hand side "
"of the above figure for a diver using EAN32."
msgstr ""

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

#. type: Plain text
#: user-manual.txt:2197
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, so their gas "
"pressures are far below the equilibrium gas pressure."
msgstr ""

#. type: Plain text
#: user-manual.txt:2202
msgid ""
"Graph *C* represents the pressures after 30 minutes at 30 m. The fast "
"compartments have attained equilibrium (i.e. they have reached the height 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:2208
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 approach the gradient factor value "
"(i.e.  the top black horizontal line). Further ascent will result in "
"exceeding the gradient factor value (GFHigh), endangering the diver."
msgstr ""

#. type: Plain text
#: user-manual.txt:2213
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:2214
#, no-wrap
msgid "Computer-reported events during dive"
msgstr ""

#. type: Plain text
#: user-manual.txt:2226
msgid ""
"Many dive computers record events during a dive. For instance, most dive "
"computers report alarms relating to high partial pressures of oxygen, to "
"rapid ascents or the exceeding of no-deco limits (NDL).  On the other hand, "
"other events are classified as warnings and, for instance, occur when the "
"remaining gas in a cylinder falls below a predetermined limit, a deep stop "
"needs to be performed or the need to change gas during multicylinder "
"dives. Some dive computers also report notifications, e.g. when a safety "
"stop is initiated or terminated or when a predetermined amount of OTUs have "
"been incurred.  The alarms, warnings and notifications differs from one dive "
"computer to another: some dive computers do not report any of the above "
"events, while others provide an extensive log of events. The reporting of "
"events is therefore a function of the dive computer used. In addition, "
"_Subsurface_ does not always have the ability to detect all the events "
"reported by a specific dive computer."
msgstr ""

#. type: Plain text
#: user-manual.txt:2231
msgid ""
"Events are indicated by symbols on the dive profile. Notifications are shown "
"as a white, round symbol with a letter _i_; warnings are indicated by a "
"yellow triangle and alarms by a red triangle. By moving the cursor over a "
"symbol, the explanation is given in the bottom-most line of the _Information "
"Box_ (see image below, where the cursor is positioned over the alarm that "
"was reported)."
msgstr ""

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

#. type: Plain text
#: user-manual.txt:2237
msgid ""
"Some dive computers report _bookmarks_ that the diver has set during the "
"dive. These are indicated as a small red flag on the profile and are "
"discussed more fully in the section on <<S_Bookmarks,_inserting "
"bookmarks_>>."
msgstr ""

#. type: Title ====
#: user-manual.txt:2238
#, no-wrap
msgid "The Profile Toolbar"
msgstr ""

#. type: Plain text
#: user-manual.txt:2246
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, "
"nitrogen in black, and helium in dark red. These partial pressure graphs are "
"shown below the profile data."
msgstr ""

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

#. type: Plain text
#: user-manual.txt:2251
msgid ""
"Show the partial pressure of *oxygen* during the dive. This is shown below "
"the dive depth and water temperature graphs."
msgstr ""

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

#. type: Plain text
#: user-manual.txt:2255
msgid "Show the partial pressure of *nitrogen* during the dive."
msgstr ""

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

#. type: Plain text
#: user-manual.txt:2260
msgid ""
"Display of the partial pressure of *helium* during the dive.  This is only "
"important to divers using Trimix, Helitrox or similar breathing gases."
msgstr ""

#. type: Plain text
#: user-manual.txt:2273
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.  Like the depth graph, the slope of the tank pressure provides "
"information about the momentary SAC rate (Surface Air Consumption) when "
"using an air integrated dive computer.  Here the color coding is not "
"relative to some absolute values but relative to the mean normalized air "
"consumption during the dive. So areas in 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: Plain text
#: user-manual.txt:2277
msgid ""
"When in planner mode, the SAC is set to be constant during the bottom part "
"of the dive as well during decompression. Therefore, when planning a dive, "
"the color is a representation of the breathing gas density."
msgstr ""

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

#. type: Plain text
#: user-manual.txt:2282
msgid ""
"Clicking on the heart rate button allows 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:2288
msgid ""
"It is possible to *zoom* into the profile graph. This is done either by "
"using the scroll wheel / scroll gesture of the mouse or trackpad. By default "
"_Subsurface_ always shows a profile area large enough for at least 30 "
"minutes and 30m (100ft) – this way short or shallow dives are easily "
"recognizable; something free divers won’t care about."
msgstr ""

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

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

#. type: Plain text
#: user-manual.txt:2299
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 you "
"wish to measure. Information is then given in the horizontal white area "
"underneath the two red dots."
msgstr ""

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

#. type: Plain text
#: user-manual.txt:2309
msgid ""
"Photographs and videos that have been added to a dive can be shown on the "
"profile by selecting the *Show-media* button. The position of a photo or "
"video on the profile shows the exact time when it was taken.  The runtime of "
"videos is represented by a bar if _Subsurface_ was able to extract this "
"information from the video file.  If this button is not active, the media "
"are hidden."
msgstr ""

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

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

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

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

#. type: delimited block =
#: user-manual.txt:2359
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:2360
#, no-wrap
msgid "images/Ceilings2.jpg"
msgstr ""

#. type: delimited block =
#: user-manual.txt:2363
msgid ""
"Gradient Factor settings strongly affect the calculated ceilings and their "
"depths. For more information about Gradient factors, see the section on "
"xref:GradientFactors_Ref[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:2365 user-manual.txt:3229
#, 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:2367 user-manual.txt:3231
#, 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: Named 'icon' AttributeList argument for style 'icon'
#: user-manual.txt:2371
#, no-wrap
msgid "images/icons/ShowCylindersButton.jpg"
msgstr ""

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

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

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

#. type: delimited block =
#: user-manual.txt:2389
msgid ""
"Display the tissue heat-map. The heat map summarises, for the duration of "
"the dive, the inert gas tissue pressures for each of the 16 tissue "
"compartments of the Bühlmann model. Blue colors mean low gas pressures in a "
"tissue compartment and thus on-gassing, green to red means excess gas in the "
"tissue and thus off-gassing. Fast to slow tissues are indicated from top to "
"bottom. The figure below explains in greater detail how the heat map can be "
"interpreted."
msgstr ""

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

#. type: delimited block =
#: user-manual.txt:2398
msgid ""
"Image *A* on the left shows the xref:S_gas_pressure_graph[Gas Pressure "
"Graph] in the *Information box*, representing a snapshot of inert gas "
"pressures at a particular point in time during the dive. The inert gas "
"pressures of 16 tissue compartments are shown as dark green vertical bars "
"with the quick tissue compartments on the left and the slow tissue "
"compartments on the right. Refer to the section on the "
"xref:S_gas_pressure_graph[Gas Pressure Graph] for more details on the "
"different elements of this graph."
msgstr ""

#. type: delimited block =
#: user-manual.txt:2406
msgid ""
"Image *B* shows a gradient of unique colors, spanning the whole range of "
"inert gas pressures.  It is possible to map the height of each of the dark "
"green vertical bars of *A* to a color in *B*. For instance, the fastest "
"(leftmost) dark green vertical bar in *A* has a height corresponding to the "
"medium green part of *B*. The height of this bar can therefore be summarised "
"using a medium green color. Similarly, the highest dark green bar in *A* is "
"as high as the yellow part of *B*. The 14 remaining tissue pressure bars in "
"*A* can also be translated to colors. The colors represent three ranges of "
"tissue inert gas pressure:"
msgstr ""

#. type: delimited block =
#: user-manual.txt:2414
msgid ""
"The bottom range in *B* (marked _On-gassing_) includes colors from light "
"blue to black, representing tissue gas pressures below the equilibrium "
"pressure of inert gas (bottom horizontal line in *A*). The measurement unit "
"is the % of inert gas pressure, relative to the equilibrium inert gas "
"pressure. In this range on-gassing of inert gas takes place because the "
"inert gas pressure in the tissue compartment is lower than in the "
"surrounding environment. Black areas in the heat map indicate that a tissue "
"compartment has reached the equilibrium inert gas pressure, i.e. the inert "
"gas pressure in the tissue compartment equals that of the water in which the "
"diver is. The equilibrium pressure changes according to depth."
msgstr ""

#. type: delimited block =
#: user-manual.txt:2420
msgid ""
"The central range in *B* includes the colors from black to light green, when "
"the inert gas pressure of a tissue compartment is higher than the "
"equilibrium pressure but less than the ambient pressure.  In this zone "
"decompression is not very efficient because the gradient of inert gas "
"pressure from tissue to the environment is relatively small and indicated by "
"dark green areas of the heat map."
msgstr ""

#. type: delimited block =
#: user-manual.txt:2429
msgid ""
"The top range in *B* (marked _Off-gassing_) includes colors from light green "
"to red and white, repesenting tissue gas pressures above that of the total "
"ambient pressure (top of light green area of *A*). The measurement unit is "
"the % of inert gas pressure above ambient pressure, relative to the Bühlmann "
"M-value gradient (bottom of red area in *A*). These tissue pressures are "
"normally reached while ascending to a shallower depth.  Below a value of "
"100%, this range indicates efficient off-gassing of inert gas from the "
"tissue compartment into the environment. Usually, efficient off-gassing is "
"indicated by light green, yellow or orange colors.  Above 100% (red to white "
"in *B*) the M-value gradient is exceeded and the probability of "
"decompression sickness increases markedly."
msgstr ""

#. type: delimited block =
#: user-manual.txt:2437
msgid ""
"Image *C* shows the color mapping of each of the vertical bars in *A*, the "
"fast tissues (on the left in *A*) depicted at the top and the slow tissue "
"compartments at the bottom of *C*. The highest vertical bar in *A* (vertical "
"bar 3rd from the left) is presented as the yellow rectangle 3rd from the top "
"in *C*. The 16 vertical bars in *A* are now presented as a vertical column "
"of 16 colored rectangles, representing a snapshot of tissue compartment gas "
"pressures at a particular instant during the dive."
msgstr ""

#. type: delimited block =
#: user-manual.txt:2444
msgid ""
"Image *D* is a compilation of similar color mappings of 16 tissue "
"compartments during a 10-minute period of a dive, the colors representing "
"the inert gas loading of a tissue compartment at a point in time during the "
"dive. Faster tissues are shown at the top and slower tissues at the bottom, "
"with time forming the horizontal axis of the graph. The column of rectangles "
"in *C* can be found on the horizontal axis between 9 and 10 minutes."
msgstr ""

#. type: delimited block =
#: user-manual.txt:2448
msgid ""
"The colors of the heat map are not affected by the gradient factor "
"settings.  This is because the heat map indicates tissue pressures relative "
"to the Bühlmann M-value gradient, and not relative to any specific gradient "
"factor. For more information external to this manual see:"
msgstr ""

#. type: delimited block =
#: user-manual.txt:2450
msgid ""
"http://www.tek-dive.com/portal/upload/M-Values.pdf[Understanding M-values by "
"Erik Baker, _Immersed_ Vol. 3, No. 3.]"
msgstr ""

#. type: delimited block =
#: user-manual.txt:2453
msgid ""
"Since the colors of the heat map are not affected by the gradient factor(s), "
"the heat map is also applicable when using the VPM-B decompression model."
msgstr ""

#. type: delimited block =
#: user-manual.txt:2457
msgid ""
"The image below compares the profiles and heat maps for two planned "
"decompression dives to 60m: the first using the Bühlmann decompression "
"model, the second using the VPM-B decompression model.  Both profiles have "
"the same total decompression time, but the VPM-B model requires deeper stops "
"early in the acent phase."
msgstr ""

#. type: delimited block =
#: user-manual.txt:2462
msgid ""
"In both profiles, the inert gas pressures in the faster tissues rise much "
"more rapidly than the slower tissues during the descent and bottom phase, "
"with the colors transitioning from light blue through blue and purple to "
"black.  Similarly, the inert gas pressure in the fast tissues reduces more "
"rapidly than the slow tissues at each decompression stop, with colors "
"transitioning from red, orange and yellow to green and black."
msgstr ""

#. type: delimited block =
#: user-manual.txt:2467
msgid ""
"The comparison of the two profiles and heatmaps shows that by including deep "
"stops, the oversaturation gradient in the faster tissues early in ascent "
"phase is reduced.  However, on-gassing of slower tissues continues during "
"the deep stops, which leads to greater oversaturation gradient in slower "
"tissues at the end of the dive."
msgstr ""

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

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

#. type: Plain text
#: user-manual.txt:2490
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 creating "
"Bookmarks, Gas Change Event markers, or manual CCR set-point changes other "
"than the ones that might have been imported from a Dive Computer. Markers "
"are placed against the depth profile line, with the time of the event "
"determined by the mouse cursor when the right mouse button was clicked to "
"bring up the menu. Gas Change events involve a selection of which gas is "
"being switched TO. The list of choices is based on the available gases "
"defined in the *Equipment* Tab. Setpoint change events open a dialog letting "
"you choose the next setpoint value. As in the planner, a setpoint value of "
"zero shows the diver is breathing from an open circuit system while any "
"non-zero value shows the use of a closed circuit rebreather (CCR).  By "
"right-clicking while over an existing marker a menu appears, adding options "
"to allow deletion of the marker, or to allow all markers of that type to be "
"hidden. Hidden events can be restored to view by selecting Unhide all events "
"from the context menu."
msgstr ""

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

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

#. type: Plain text
#: user-manual.txt:2498
msgid ""
"Several actions on either a single dive, or a group of dives, can be "
"performed using the Dive List Context Menu.  It is found by selecting either "
"a single dive or a group of dives and then right-clicking."
msgstr ""

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

#. type: Plain text
#: user-manual.txt:2502
msgid "The context menu is used in many functions described below."
msgstr ""

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

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

#. type: Plain text
#: user-manual.txt:2514
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*, bringing up a list of columns that can be shown in "
"the dive list (see above). Check an items to be included in the *Dive "
"List*.  The list is immediately updated. Preferences for information shown "
"in the *Dive List* are saved and used when _Subsurface_ is re-opened."
msgstr ""

#. type: Plain text
#: user-manual.txt:2519
msgid ""
"By selecting the _Media_ checkbox in the dropdown list, an icon is shown "
"indicating whether any media are associated with a particular dive. There "
"are three icons:"
msgstr ""

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

#. type: Plain text
#: user-manual.txt:2523
msgid ""
"This dive has photographs or videos taken during the dive, typically using "
"an underwater camera."
msgstr ""

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

#. type: Plain text
#: user-manual.txt:2529
msgid ""
"This dive has photographs or videos taken immediately before or immediately "
"after the dive. This is useful for finding photos/media of dive teams or "
"boats just before/after the dive, whales or other surface animals seen just "
"before or after the dive, or of landscapes as seen from the boat."
msgstr ""

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

#. type: Plain text
#: user-manual.txt:2533
msgid ""
"This dive has photographs or videos taken both during the dive and "
"immediately before or after the dive."
msgstr ""

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

#. type: Plain text
#: user-manual.txt:2547
msgid ""
"Dives are normally numbered incrementally from non-recent dives (low "
"sequence numbers) to recent dives (higher sequence numbers).  Numbering of "
"dives is not always consistent. For instance, when non-recent dives are "
"added, correct numbering does not automatically follow on because of the "
"dives that are more recent in date/time than the newly-added dive with an "
"older date/time. This requires renumbering the dives.  Do this by selecting "
"(from the Main Menu) _Log -> Renumber_. Provide the lowest sequence number "
"to be used.  This results in new sequence numbers (based on date/time)  for "
"all the dives in the *Dive List* panel."
msgstr ""

#. type: Plain text
#: user-manual.txt:2552
msgid ""
"Renumber a few selected dives in the dive list by selecting only the dives "
"that need renumbering. Right-click on the selected list and use the Dive "
"List Context Menu to perform the renumbering. A popup window appears letting "
"the user specify the starting number for the process."
msgstr ""

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

#. type: Plain text
#: user-manual.txt:2562
msgid ""
"For regular divers, the dive list can rapidly become very long. _Subsurface_ "
"can group dives into _trips_. It does this by grouping dives that have "
"date/times not separated by more than two days and 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 of "
"five dive trips (*B*, on the right):"
msgstr ""

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

#. type: Plain text
#: user-manual.txt:2569
msgid ""
"Grouping into trips allows a rapid way of accessing individual dives without "
"having to scan a long lists of dives. To group the dives in a dive list, "
"(from the Main Menu) select _Log -> Auto group_. The *Dive List* panel now "
"shows only the titles for the trips."
msgstr ""

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

#. type: Plain text
#: user-manual.txt:2583
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 bar from the *Dive List*. This shows a *Trip Notes* tab in the *Notes* "
"panel. Here you can add or edit information about the date/time, the trip "
"location and any other general comments about the trip as a whole (e.g. the "
"dive company that was used, the general weather and surface conditions "
"during the trip, etc.).  After entering this information, select *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:2584
#, no-wrap
msgid "Viewing the dives during a particular trip"
msgstr ""

#. type: Plain text
#: user-manual.txt:2589
msgid ""
"Once the dives have been grouped into trips, you can expand one or more "
"trips by clicking the expansion button [+/-] on the left of each trip "
"title. This expands the selected trip, revealing individual dives during the "
"trip."
msgstr ""

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

#. type: Plain text
#: user-manual.txt:2595
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:2596
#, no-wrap
msgid "Splitting a single trip into more than one trip"
msgstr ""

#. type: Plain text
#: user-manual.txt:2605
msgid ""
"If a trip includes, for example, ten dives, you can split this trip into two "
"trips (trip 1: top four dives; trip 2: bottom six dives) by selecting and "
"right-clicking the top four dives. The resulting context menu lets the user "
"create a new trip by choosing the option *Create new trip above*. The top "
"four dives are then grouped into a separate trip. The figures below show the "
"selection and context menu on the left (A) and the completed action on the "
"right (B):"
msgstr ""

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

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

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

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

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

#. type: Plain text
#: user-manual.txt:2625
msgid ""
"You can unlink dives from the trip to which they belong. To do this, select "
"and right-click the relevant dives to bring up the context menu. Then select "
"the option *Remove dive(s)  from trip*. The dive(s) now appear immediately "
"above or below the trip to which they belonged, depending on the date and "
"time of the unlinked dive."
msgstr ""

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

#. type: Plain text
#: user-manual.txt:2631
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:2632
#, no-wrap
msgid "Shift the start time of dive(s)"
msgstr ""

#. type: Plain text
#: user-manual.txt:2642
msgid ""
"Sometimes it’s necessary to adjust the start time of a dive. This may apply "
"to situations where dives are done in different time zones or when the dive "
"computer has a wrong time. To do this, select and right-click the dive(s) to "
"be adjusted. This brings up the context menu on which the *Shift times* "
"option should be selected. You must then specify the time (in hours and "
"minutes) by which the dives should be adjusted and click on the option of "
"whether the time adjustment should be earlier or later."
msgstr ""

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

#. type: Plain text
#: user-manual.txt:2653
msgid ""
"Sometimes a dive is briefly interrupted, for example, 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.  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:2654
#, no-wrap
msgid "images/MergedDive.png"
msgstr ""

#. type: Title ====
#: user-manual.txt:2656
#, no-wrap
msgid "Split selected dives"
msgstr ""

#. type: Plain text
#: user-manual.txt:2664
msgid ""
"On some occasions, a diver reaches the surface and immediately dives "
"again. However, it may happen that the dive computer does not register a new "
"dive, but continues the previous dive due to the brief surface interval. In "
"this case it is possible to split a dive so that the two dives are shown as "
"independent dives on the *Dive List*.  If this operation is performed, "
"_Subsurface_ scans the selected dive(s) and splits the dive at points during "
"the dive where the depth is less than a metre."
msgstr ""

#. type: Title ====
#: user-manual.txt:2665
#, no-wrap
msgid "Load image(s) from file(s)"
msgstr ""

#. type: Plain text
#: user-manual.txt:2667 user-manual.txt:2670
msgid ""
"This topic is discussed in the section: xref:S_LoadImage[Adding photographs "
"or videos to dives]."
msgstr ""

#. type: Title ====
#: user-manual.txt:2668
#, no-wrap
msgid "Load image from web"
msgstr ""

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

#. type: Plain text
#: user-manual.txt:2677
msgid ""
"Important actions on dives or trips, described above, can be undone or "
"redone.  This includes: _delete dives_, _merge dives_, _split selected "
"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:2680
#, no-wrap
msgid "Filtering the dive list"
msgstr ""

#. type: Plain text
#: user-manual.txt:2686
msgid ""
"The dives in the *Dive List* panel can be filtered, selecting only some of "
"the dives based on their attributes, e.g. dive tags, dive site, divemaster, "
"buddy or protective clothing. For instance, filtering lets you list the deep "
"dives at a particular dive site, or otherwise the cave dives with a "
"particular buddy."
msgstr ""

#. type: Plain text
#: user-manual.txt:2694
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 minimized by "
"selecting the *green up-arrow*. When minimized, only these three icons are "
"shown.  The panel can be maximized by clicking the same icon that minimized "
"it. The filter may also be reset and closed by selecting the *red button* "
"with the white cross."
msgstr ""

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

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

#. type: Plain text
#: user-manual.txt:2712
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:2714
#, no-wrap
msgid "Exporting the dive log or parts of the dive log"
msgstr ""

#. type: Plain text
#: user-manual.txt:2717
msgid "There are two ways to export dive information from Subsurface:"
msgstr ""

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

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

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

#. type: Plain text
#: user-manual.txt:2732
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.  From the *Main Menu*, select _Share on -> Connect to "
"-> Facebook_ (image *A* below)  A _Facebook_ login screen appears (image *B* "
"below). Provide a _Facebook_ userID and password.  From the _Subsurface_ "
"window it’s easy to determine whether _Subsurface_ has a valid connection to "
"_Facebook_: from the *Main Menu*, select _Share on_ (image *A*, "
"below). Normally, the _Facebook_ option is greyed out. But if there is a "
"connection to _Facebook_, this option is active (i.e. in black color and can "
"be selected)."
msgstr ""

#. type: Plain text
#: user-manual.txt:2736
msgid ""
"Once logged into to _Facebook_ , a panel is shown with a message: \"_To "
"disconnect Subsurface from your Facebook account, use the 'Share on' menu "
"entry_.\" Close this message panel."
msgstr ""

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

#. type: Plain text
#: user-manual.txt:2750
msgid ""
"Having established a login to _Facebook_, transferring a dive profile to a "
"_Facebook_ timeline is easy.  In the _Subsurface_ *Dive List* panel, "
"highlight the dive to be transferred.  Then, from the *Main Menu*, select "
"_Share on -> Facebook_. A dialogue box is shown, determining the amount of "
"additional information to be transferred with the dive profile (image *A*, "
"below). To transfer a dive profile to _Facebook_, the name of a _Facebook_ "
"album is needed. The checkboxes on the left hand side determine how much "
"additional information is added to the dive profile, shown in the text box "
"on the right hand side of the panel (image *A*, below). Customise the "
"message that will be posted with the dive profile by editing any of the "
"information. After specifying additional information and verifying the text, "
"select the _OK_ button that triggers the transfer to _Facebook_. After the "
"transfer is done, an acknowledgement dialogue appears, indicating it was "
"successful."
msgstr ""

#. type: Plain text
#: user-manual.txt:2754
msgid ""
"Both the album created and the post to your timeline are marked as "
"private. In order for friends to be able to see the post, log into "
"_Facebook_ using a browser or Facebook app and change its permissions."
msgstr ""

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

#. type: Plain text
#: user-manual.txt:2759
msgid ""
"If required, then close the _Facebook_ connection by selecting, from the "
"*Main Menu*, _Share on -> Disconnect from -> Facebook_ (image *B* above)."
msgstr ""

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

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

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

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

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

#. type: Plain text
#: user-manual.txt:2776
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:2780
msgid ""
"_Divelogs.de_, an Internet-based dive log repository. In order to upload to "
"_Divelogs.de_, you need a user-ID as well as a password for "
"_Divelogs.de_. Log into _http://en.divelogs.de_ and subscribe to this "
"service to upload dive log data from _Subsurface_."
msgstr ""

#. type: Plain text
#: user-manual.txt:2784
msgid ""
"_DiveShare_ is also a dive log repository on the Internet focusing on "
"recreational dives. To upload dives, you need a user ID, so registration "
"with _http://scubadiveshare.com_ is required."
msgstr ""

#. type: Plain text
#: user-manual.txt:2789
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:2792
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:2805
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. dive ceiling, "
"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 your dives to a smartphone or a tablet where it "
"would serve as a portable record of dives, useful for dive companies wishing "
"to verify the dive history of a diver, and doing away with the need to carry "
"an original logbook when doing dives with dive companies."
msgstr ""

#. type: Plain text
#: user-manual.txt:2810
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 you "
"select any of the dive sites on the map, a summary of the dive is available "
"in text, as shown in the image below."
msgstr ""

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

#. type: Plain text
#: user-manual.txt:2820
msgid ""
"_TeX_ format, a file for printing using the TeX typesetting software. Choose "
"a filename with a '.tex' extension. You will also need a template file, that "
"can be obtained from "
"link:http://www.atdotde.de/%7erobert/subsurfacetemplate/[http://www.atdotde.de/~robert/subsurfacetemplate/] "
"in the same directory as the '.tex' file. The file can then be processed "
"with plain TeX (not LaTeX), for example by running 'pdftex filename.tex' on "
"the command line."
msgstr ""

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

#. type: Plain text
#: user-manual.txt:2828
msgid ""
"_Image depths_, which creates a text file that contains the file names of "
"all photos or videos attached to any of the selected dives in the _Dive "
"List_, together with the depth underwater where of each of those "
"photos/videos was taken."
msgstr ""

#. type: Plain text
#: user-manual.txt:2835
msgid ""
"When the \"Anonymize\" option is selected for xml-based file formats, the "
"letters A-Z are all replaced by the letter 'X' in the notes, buddy, "
"divemaster, divesite name and divesite description fields. This way, you can "
"share dive log files for debugging purposes without revealing personal "
"information. Please note, though, that other characters are not replaced, so "
"this is not useful for languages with non-latin characters and GPS "
"coordinates of dive sites are preserved as well."
msgstr ""

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

#. type: Plain text
#: user-manual.txt:2846
#, 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:2849
msgid ""
"Under _Style Options_ some style-related options are available like font "
"size and theme."
msgstr ""

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

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

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

#. type: Plain text
#: user-manual.txt:2870
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 you should first register as "
"a user on the cloud.  To use _Subsurface cloud storage_ , follow these "
"steps:"
msgstr ""

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

#. type: Plain text
#: user-manual.txt:2888
#, 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:2889
#, no-wrap
msgid "Using _Subsurface cloud storage_"
msgstr ""

#. type: Plain text
#: user-manual.txt:2899
#, no-wrap
msgid ""
"** Once the cloud storage has been initialized, two new items appear in "
"the\n"
"   _File_ menu of the main menu system: _Open cloud storage_ and _Save to "
"cloud storage_.\n"
"These options let you load and save data to the _Subsurface\n"
"cloud storage_ server.\n"
"** In the _Defaults Preferences_ tab, you can select to use the _Subsurface "
"cloud\n"
"storage_ data as the default data file by checking the box marked _Cloud "
"storage default file_.\n"
" This means the data from\n"
"the _Subsurface cloud storage_ is loaded when _Subsurface_ starts and saved "
"there when _Subsurface_ closes.\n"
msgstr ""

#. type: Plain text
#: user-manual.txt:2904
#, 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 synchronizes the\n"
"data with the cloud server the next time the program is used while the "
"computer is\n"
"connected to the Internet.\n"
msgstr ""

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

#. type: Plain text
#: user-manual.txt:2916
msgid ""
"One of the nice side benefits of using _Subsurface cloud storage_ is that "
"you can also access your dive data from any web browser. Simply open "
"https://cloud.subsurface-divelog.org[_https://cloud.subsurface-divelog.org_], "
"log in with the same email and password, and you can see an HTML export of "
"the last dive data that was synced to _Subsurface cloud storage_. The dive "
"information shown is only the contents of the recorded dive logs, NOT the "
"calculated values shown in the *Profile* panel, including some cylinder "
"pressures, deco ceilings and O~2~/He/N~2~ partial pressures."
msgstr ""

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

#. type: Plain text
#: user-manual.txt:2927
msgid ""
"If you prefer not to use the integrated cloud storage of dive logs (and "
"don't need the web access), it’s simple to store dive logs in the cloud "
"using several of the existing facilities on the Internet.  For instance "
"https://www.dropbox.com/[_Dropbox_] offers a free application that allows "
"files on the Dropbox servers to be seen as a local folder on a desktop "
"computer."
msgstr ""

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

#. type: Plain text
#: user-manual.txt:2937
msgid ""
"The _Dropbox_ program creates a copy of the _Dropbox_ Internet Cloud content "
"on your desktop computer. When the computer is connected to the Internet, "
"the Internet content is automatically updated. Therefore both the _Open_ and "
"_Save_ of dive logs are done using the local copy of the dive log in the "
"local _Dropbox_ folder, so there's no need for a direct internet "
"connection. 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: Title ==
#: user-manual.txt:2940
#, no-wrap
msgid "Several _Subsurface_ users on one desktop computer"
msgstr ""

#. type: Plain text
#: user-manual.txt:2944
msgid ""
"A frequent need is for two or more persons to use _Subsurface_ on the same "
"desktop computer. For instance members of a household may use the same "
"computer or one family member may perform dive uploads for other family "
"members/friends. There are two approaches for doing this."
msgstr ""

#. type: Plain text
#: user-manual.txt:2956
#, no-wrap
msgid ""
"*A)* If the different users of a desktop computer do not log onto the "
"desktop/laptop under different user names\n"
"  then the simplest way is for each person to use her/his own divelog file "
"within Subsurface. In this case John\n"
"  would work with the _Subsurface_ file _johns-divelog_ and Joan would use "
"_joans-divelog_. Select\n"
"  the appropriate dive log by selecting, from the *Main Menu*, _File -> Open "
"logbook_ and then select your own\n"
"  dive log file from the list of files lower down in the menu. However, a "
"problem arises if the users\n"
"  prefer different settings for _Subsurface_. For instance, one diver may "
"prefer to see the dive ceiling in the\n"
"  *Profile Panel* and media icons in the *Dive List*, while the other may "
"not have these preferences. In addition,\n"
"  the cloud connection is normally unique for each _Subsurface_ installation "
"and if more than one user wishes to save\n"
"  dive data on the cloud, it is inconvenient to open the *Preferences* and "
"change the user-ID data every time\n"
"  the cloud is accessed. To solve these problems, launch _Subsurface_ with a "
"_--user=<user name>_ command-line option.\n"
"  John can then activate _Subsurface_ with this command-line instruction:\n"
msgstr ""

#. type: Plain text
#: user-manual.txt:2958
#, no-wrap
msgid "\tsubsurface --user=John\n"
msgstr ""

#. type: Plain text
#: user-manual.txt:2960
msgid "while Joan can launch _Subsurface_ using:"
msgstr ""

#. type: Plain text
#: user-manual.txt:2962
#, no-wrap
msgid "\tsubsurface --user=Joan\n"
msgstr ""

#. type: Plain text
#: user-manual.txt:2970
#, no-wrap
msgid ""
"In this case, each user's preferences, settings and cloud access information "
"are stored separately, allowing\n"
"  each diver to interact with _Subsurface_ in her/his preferred way and with "
"individual cloud access. The above\n"
"  process can be made user-friendly by creating a link/shortcut with a "
"desktop icon that executes the above\n"
"  command-line instruction. Use of the _--user=_ option therefore enables "
"each user to create, maintain and\n"
"  backup a separate dive log within a personalised user interface. This way, "
"when each diver launches _Subsurface_,\n"
"  it opens with the correct dive log as well as the appropriate display and "
"backup preferences, and each diver\n"
"  can access their own divelog on a mobile device using "
"https://subsurface-divelog.org/documentation/subsurface-mobile-user-manual[_Subsurface-Mobile_].\n"
msgstr ""

#. type: Plain text
#: user-manual.txt:2974
#, no-wrap
msgid ""
"*B)* On the other hand, if the users log onto the same computer using "
"different userIDs and passwords (i.e. users each\n"
"have a separate user space), _Subsurface_ is available independently to each "
"user and every diver automatically has a separate\n"
"user profile and settings, including unique cloud and _Subsurface-Mobile_ "
"access.\n"
msgstr ""

#. type: Title ==
#: user-manual.txt:2976
#, no-wrap
msgid "Printing a dive log"
msgstr ""

#. type: Plain text
#: user-manual.txt:2980
#, no-wrap
msgid ""
"_Subsurface_ provides a simple and flexible way to print a whole dive log or "
"only a few selected dives.\n"
"  Pre-installed templates or a custom written template can be used to choose "
"where the data are fitted into the page.\n"
msgstr ""

#. type: Plain text
#: user-manual.txt:2982
msgid "Some decisions need to be made before printing:"
msgstr ""

#. type: Plain text
#: user-manual.txt:2985
msgid ""
"Should the whole dive log be printed or only part of it? If only part is "
"required, select the required dives from the *Dive List* panel."
msgstr ""

#. type: Plain text
#: user-manual.txt:2987
msgid ""
"If the dive profiles are printed, what gas partial pressure information "
"should be shown? Select the appropriate toggle-buttons on the button bar to "
"the left of the *Dive Profile* panel."
msgstr ""

#. type: Plain text
#: user-manual.txt:2990
msgid ""
"If _File -> Print_ is selected from the Main menu, the dialogue below (image "
"*A*) appears. Three specifications are needed to get the desired information "
"and page layout:"
msgstr ""

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

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

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

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

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

#. type: Plain text
#: user-manual.txt:3004
msgid ""
"Printing only the dives selected from the dive list before activating the "
"print dialogue by checking the box _Print only selected dives_. If this "
"check box is *not* checked ALL dives in the *Dive List* panel are printed."
msgstr ""

#. type: Plain text
#: user-manual.txt:3006
msgid ""
"Printing in color, done by checking the box with _Print in color_. If this "
"check box is not checked, printing is in black and white."
msgstr ""

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

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

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

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

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

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

#. type: Plain text
#: user-manual.txt:3020
msgid ""
"_One Dive_: Print one dive per page, also showing the dive profile (see "
"below)"
msgstr ""

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

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

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

#. type: Plain text
#: user-manual.txt:3030
msgid ""
"You can _Preview_ the printed page by selecting the _Preview_ button on the "
"dialogue (see image *A* at the start of this section). After preview, you "
"can change the options in the print dialogue, so the layout fits personal "
"taste."
msgstr ""

#. type: Plain text
#: user-manual.txt:3034
msgid ""
"Next, select the _Print_ button (see image *A* at the start of this "
"section). This activates the regular print dialogue used by the operating "
"system, letting you choose a printer and set its properties (see image "
"below):"
msgstr ""

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

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

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

#. type: Plain text
#: user-manual.txt:3049
msgid ""
"Writing a custom template is an effective way to produce highly customized "
"printouts. Subsurface uses HTML templates to render printing. You can create "
"a template, export a new template, import an existing template and delete an "
"existing template by using the appropriate buttons under the _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:3051
#, no-wrap
msgid "Configuring a dive computer"
msgstr ""

#. type: Plain text
#: user-manual.txt:3059
msgid ""
"_Subsurface_ lets you configure a dive computer. Currently, the "
"Heinrichs-Weikamp (OSTC 2/2N/2C, OSTC 3, Sport) and Suunto Vyper (Stinger, "
"Mosquito, D3, Vyper, Vytec, Cobra, Gekko and Zoop) family of dive computers "
"are supported. A large number of settings of these dive computers can be "
"read and changed to different values. To begin, be sure the appropriate "
"hardware driver is installed for the dive computer (also required for "
"downloading dives) and the device name of the dive computer is known.  See "
"<<_appendix_a_operating_system_specific_information_for_importing_dive_information_from_a_dive_computer,APPENDIX "
"A>> for information on how to do this."
msgstr ""

#. type: Plain text
#: user-manual.txt:3065
msgid ""
"Once the dive computer is connected to the _Subsurface_ computer, select "
"_File -> Configure dive computer_ from the _Main Menu_. Select the "
"appropriate device name (or mount point) in the dropdown list 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:3066
#, no-wrap
msgid "images/Configure_dc_f20.jpg"
msgstr ""

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

#. type: Plain text
#: user-manual.txt:3072
#, 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:3074
#, 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:3076
#, 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:3078
#, 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:3080
#, 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:3083
#, no-wrap
msgid "Setting user _Preferences_ for _Subsurface_"
msgstr ""

#. type: Plain text
#: user-manual.txt:3094
msgid ""
"There are several user-definable settings within _Subsurface_, found by "
"selecting _File -> Preferences_, mostly affecting the way in which "
"_Subsurface_ shows dive information to the user. The settings are in six "
"panels: _General_, _Units_, _Profile_, _Language_, _Network_, and "
"_Georeference_, all of which operate on the same principles: specified "
"settings can be applied to the display of the dive log by selecting "
"_Apply_. At this stage, any new settings only apply to the present session "
"and are not saved. In order to apply new settings permanently, select the "
"_Save_ button. If you do not wish to apply the new preferences, select "
"_Cancel_."
msgstr ""

#. type: Title ===
#: user-manual.txt:3095
#, no-wrap
msgid "General"
msgstr ""

#. type: Plain text
#: user-manual.txt:3098
msgid "There are several headings in the *General* panel:"
msgstr ""

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

#. type: Plain text
#: user-manual.txt:3103
#, no-wrap
msgid ""
"  ** *Lists and tables*: Specify the font type and font size of the\n"
"     *Dive Table* panel: decreasing the font size allows one to see more "
"dives on a screen.\n"
msgstr ""

#. type: Plain text
#: user-manual.txt:3108
#, no-wrap
msgid ""
"  ** *Dives*: For the _Default Dive Log File_ specify the directory and\n"
"     file name of your\n"
"     electronic dive log book. This is a file with filename extension of "
"either _.xml_ or _.ssrf_. When\n"
"     launched, _Subsurface_ will automatically load the specified dive log "
"book. There are three options:\n"
msgstr ""

#. type: Plain text
#: user-manual.txt:3109
#, 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:3110
#, no-wrap
msgid ""
"_Local default file_: When checked, _Subsurface_ automatically loads a dive "
"log from the local hard disk.\n"
msgstr ""

#. type: Plain text
#: user-manual.txt:3112
#, no-wrap
msgid ""
"_Cloud storage default file_: When checked, _Subsurface automatically loads "
"the dive log from the cloud\n"
"device that was initialized using the *Preferences* _Network_ tab (see "
"below).\n"
msgstr ""

#. type: Plain text
#: user-manual.txt:3114
#, 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:3117
#, 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:3119
#, no-wrap
msgid ""
"** *Default cylinder*: From the dropdown list, select the default cylinder "
"to be used in\n"
msgstr ""

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

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

#. type: Plain text
#: user-manual.txt:3128
#, 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:3130
#, no-wrap
msgid ""
"** *Video thumbnails*: In generating thumbnails for videos associated with "
"dives, _Subsurface_\n"
msgstr ""

#. type: Plain text
#: user-manual.txt:3134
#, no-wrap
msgid ""
"needs to have the appropriate information (see section on <<S_ViewMedia,View "
"Images>>). Three preferences need to be set\n"
"as explained in <<S_APPENDIX_F, APPENDIX F>>. These are: a) switch on "
"thumbnails, b) specify\n"
"the location of the _ffmpeg_ program and c) set the place within video where "
"the thumbnail needs\n"
"to be obtained from.\n"
msgstr ""

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

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

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

#. type: Plain text
#: user-manual.txt:3146
msgid ""
"Choose between metric and imperial units of depth, pressure, volume, "
"temperature and mass. By selecting the Metric or Imperial radio button at "
"the top, you can specify that all units are in the chosen measurement "
"system.  Alternatively, if you select the *Personalize* radio button, units "
"can be selected independently, with some in the metric system and others in "
"imperial."
msgstr ""

#. type: Plain text
#: user-manual.txt:3152
msgid ""
"Regardless of the above settings, dive time measurements can be either in "
"seconds or minutes.  Choose the appropriate option. GPS coordinates can be "
"represented either as traditional coordinates (degrees, minutes, seconds) or "
"as decimal degrees Choose the appropriate option."
msgstr ""

#. type: Title ===
#: user-manual.txt:3153
#, no-wrap
msgid "Profile"
msgstr ""

#. type: Plain text
#: user-manual.txt:3155
msgid "This panel has three sections:"
msgstr ""

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

#. type: Plain text
#: user-manual.txt:3170
#, no-wrap
msgid ""
"*Gas pressure display setup*. Even though nitrogen and helium pressures are "
"also included here, these items mainly pertain to oxygen management:\n"
"** _Thresholds_: _Subsurface_ can display graphs of the nitrogen, oxygen and "
"the helium\n"
"   partial pressures during\n"
"   the dive, activated using the toolbar on the left of the *Dive Profile*\n"
"   panel. For each of these graphs, specify a threshold value. If any of the "
"graphs go\n"
"   above the specified threshold, the graph is\n"
"   highlighted in red, indicating the particular partial pressure threshold "
"has been exceeded.\n"
"   The pO~2~ threshold is probably the most important one and a value of 1.6 "
"is commonly used.\n"
"** _pO~2~ in calculating MOD_ is used for calculating the maximum operative "
"depth for a particular\n"
"   nitrox or trimix gas mixture. A value of 1.4 is commonly used.\n"
msgstr ""

#. type: Plain text
#: user-manual.txt:3172
#, no-wrap
msgid "** CCR Options: These options determine oxygen management for CCR dives:\n"
msgstr ""

#. type: Plain text
#: user-manual.txt:3177
#, no-wrap
msgid ""
"*** _Dive planner default setpoint_: Specify the O~2~ setpoint for a\n"
"    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:3181
#, no-wrap
msgid ""
"*** _CCR: Show 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:3185
#, no-wrap
msgid ""
"*** _CCR: Show setpoints when viewing pO~2~:_ With this checkbox activated, "
"the pO~2~\n"
"    graph on the dive profile has an overlay in red which indicates the CCR "
"setpoint\n"
"    values. See the section on xref:S_CCR_dives[Closed Circuit Rebreather "
"dives].\n"
msgstr ""

#. type: Plain text
#: user-manual.txt:3188
#, no-wrap
msgid ""
"**  _pSCR options_. These preferences determine how passive semi-closed "
"circuit (pSCR) dives\n"
"    are planned and how the pSCR deco ceiling is calculated:\n"
msgstr ""

#. type: Plain text
#: user-manual.txt:3192
#, no-wrap
msgid ""
"*** _Metabolic rate:_ this is the\n"
"    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:3195
#, no-wrap
msgid ""
"*** _pSCR ratio:_ The dilution ratio (or dump ratio) is the ratio of gas "
"released to the\n"
"    environment to that of the gas recirculated to the diver. A 1:10 ratio "
"is commonly used.\n"
msgstr ""

#. type: Plain text
#: user-manual.txt:3199
#, no-wrap
msgid ""
"*** _Show equivalent OC with pSCR pO~2~_: The pO~2~ in the pSCR loop is "
"usually lower than the\n"
"    pO~2~ of the fresh gas from the cylinder. Activating this checkbox "
"allows the pO~2~ graph\n"
"    in the dive profile to also show the pO~2~ of the fresh gas entering the "
"loop.\n"
msgstr ""

#. type: Plain text
#: user-manual.txt:3201
#, no-wrap
msgid ""
"*Ceiling display setup*. These settings mostly deal with nitrogen and helium "
"management\n"
msgstr ""

#. type: Plain text
#: user-manual.txt:3202
#, no-wrap
msgid ""
"by determining how the decompression ceiling (ascent ceiling) is calculated "
"and displayed:\n"
msgstr ""

#. type: Plain text
#: user-manual.txt:3209
#, no-wrap
msgid ""
"** _Draw dive computer reported ceiling red_: This checkbox does exactly "
"what it says. By default\n"
"   the computer reported ceiling is shown in white.\n"
"   Not all dive computers report ceiling values. If the dive computer does "
"report it, it may differ\n"
"   from the ceilings calculated by _Subsurface_ because of the different "
"algorithms and\n"
"   gradient factors, as well as the dynamic way a\n"
"   dive computer calculates ceilings during a dive.\n"
msgstr ""

#. type: Plain text
#: user-manual.txt:3214
#, no-wrap
msgid ""
"** _Algorithm for calculating ceiling_. Choose between the Bühlmann "
"Z1H-L16\n"
"   decompression model and the VPM-B model:\n"
"*** _VPM-B_: Provide a conservatism level for calculating the VPM-B "
"ceiling. Values between 0\n"
"    (least conservative) and 4 (most conservative) are valid.\n"
msgstr ""

#. type: Plain text
#: user-manual.txt:3227
#, no-wrap
msgid ""
"*** Bühlmann: Set the _gradient factors_ (GFLow and GFHigh) for calculcating "
"the deco ceiling following\n"
"   the ZH-L16 algorithm. GF_Low is the gradient factor at depth and GF_High "
"is used at the surface.\n"
"   At intermediate depths gradient factors between GF_Low and GF_High are "
"used.\n"
"   Gradient factors add conservatism to nitrogen and helium 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 inert gas loading and the deeper the ceilings are. Gradient\n"
"   factors of 20/60 are considered conservative and values of 70/90 are "
"considered\n"
"   harsh.\n"
"   For more information see:\n"
msgstr ""

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

#. type: Plain text
#: user-manual.txt:3241
#, no-wrap
msgid ""
"** _Show unused cylinders in Equipment Tab_: This checkbox allows display of "
"information about unused cylinders when viewing the\n"
"*Equipment Tab*. If this box is not checked, and if any cylinders entered "
"using the *Equipment Tab* are not used (e.g. there\n"
"was no gas switch to such a cylinder), then these cylinders are omitted from "
"that list.\n"
"**  _Show mean depth_: If this box is checked, the *Dive Profile* panel "
"contains a grey line that shows\n"
"    the mean depth of the dive, up to any time instant during the "
"dive. Normally this is a u-shaped line indicating the deepest mean depth "
"just before\n"
"   ascent.\n"
msgstr ""

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

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

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

#. type: Plain text
#: user-manual.txt:3255
msgid ""
"Check the _System Default_ language i.e. the language of the underlying "
"operating system if this is appropriate. This is the default setting in "
"_Subsurface_.  To change it, uncheck this checkbox and pick a language / "
"country combination from the list of locations. The _Filter_ text box 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: Plain text
#: user-manual.txt:3257
msgid ""
"In this section also specify appropriate date and time formats for showing "
"dive details."
msgstr ""

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

#. type: Plain text
#: user-manual.txt:3262
msgid ""
"This panel facilitates communication between _Subsurface_ and data sources "
"on the Internet.  This is important, for instance, when _Subsurface_ needs "
"to communicate with web services such as Cloud storage, or when you want to "
"communicate through a proxy."
msgstr ""

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

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

#. type: Plain text
#: user-manual.txt:3275
#, no-wrap
msgid ""
"** _Proxy_:\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 your ISP.\n"
msgstr ""

#. type: Plain text
#: user-manual.txt:3280
#, no-wrap
msgid ""
"** _Subsurface cloud storage_: To store your dive log in the cloud, a valid "
"email address\n"
"   and password are required. This lets _Subsurface_ email security "
"information\n"
"   regarding cloud storage to you, and to set up cloud storage "
"appropriately.\n"
"   Two additional options are given:\n"
msgstr ""

#. type: Plain text
#: user-manual.txt:3281
#, 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:3282
#, no-wrap
msgid "while you do other things within _Subsurface_.\n"
msgstr ""

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

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

#. type: Plain text
#: user-manual.txt:3294
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-Mobile_ app). A search on the Internet is done to find the name "
"of the closest known location. This function only works if _Subsurface_ has "
"an Internet connection. The preference of the dive site name can be "
"configured, e.g. _Country/State/City_ or _City/State/Country_ (see image "
"below)."
msgstr ""

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

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

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

#. type: delimited block *
#: user-manual.txt:3311
msgid ""
"The _Subsurface_ dive planner IS 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:3314
msgid ""
"The user is conversant with dive planning and has the necessary training to "
"perform dive planning."
msgstr ""

#. type: delimited block *
#: user-manual.txt:3315
msgid "The user plans dives within his/her certification limits."
msgstr ""

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

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

#. type: Plain text
#: user-manual.txt:3329
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 sections on the left hand and bottom side of the screen.  They are: "
"Available Gases, Rates, Planning, Gas Options and Notes."
msgstr ""

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

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

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

#. type: Plain text
#: user-manual.txt:3344
msgid ""
"Towards the center bottom of the planner (circled in blue in the image "
"above) is a dropbox with three options. Select the appropriate one of these:"
msgstr ""

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

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

#. type: Plain text
#: user-manual.txt:3353
msgid ""
"In the top left-hand area of the planning screen, be sure the constant dive "
"parameters are appropriate. These are: Start date and time of the intended "
"dive, Atmospheric Pressure and Altitude above sea level of the dive "
"site. The atmospheric pressure can also be entered as an altitude in meters, "
"assuming a sea-level atmospheric pressure of 1.013 bar."
msgstr ""

#. type: Plain text
#: user-manual.txt:3362
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 start pressure of this cylinder. By leaving the "
"oxygen concentration (O~2~%) field 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:3364
msgid "The _Available Gases_ table includes three gas depth fields, labelled:"
msgstr ""

#. type: Plain text
#: user-manual.txt:3365
#, no-wrap
msgid ""
"** Deco switch at: the switch depth for deco gases. Unless overridden by the "
"user, this will be\n"
msgstr ""

#. type: Plain text
#: user-manual.txt:3366
#, no-wrap
msgid ""
"automatically calculated based on the Deco pO~2~ preference (default 1.6 "
"bar)\n"
msgstr ""

#. type: Plain text
#: user-manual.txt:3367
#, no-wrap
msgid ""
"** Bot. MOD: the gas Maximum Operating Depth (MOD) if it is used as a bottom "
"mix. Automatically\n"
msgstr ""

#. type: Plain text
#: user-manual.txt:3369
#, no-wrap
msgid ""
"calculated based on the Bottom pO~2~ preference (default 1.4 bar). Editing "
"this field will modify the\n"
"O~2~% according to the depth set. Set to ''*'' to calculate the best O~2~% "
"for the dive maximum depth.\n"
msgstr ""

#. type: Plain text
#: user-manual.txt:3370
#, no-wrap
msgid ""
"** MND: the gas Maximum Narcotic Depth (MND). Automatically calculated based "
"on the Best Mix END\n"
msgstr ""

#. type: Plain text
#: user-manual.txt:3372
#, no-wrap
msgid ""
"preference (default 30m / 98 ft). Editing this field will modify the He% "
"according to the depth set.\n"
"Set to ''*'' to calculate the best He% for the dive maximum depth.\n"
msgstr ""

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

#. type: Plain text
#: user-manual.txt:3379
msgid ""
"Drag the waypoints (the small white circles) on the existing dive profile to "
"represent the dive. Additional waypoints can be created by double-clicking "
"the existing dive profile. Waypoints can be deleted by right-clicking a "
"particular waypoint and selecting the _delete_ item from the resulting "
"context menu."
msgstr ""

#. type: Plain text
#: user-manual.txt:3387
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 "
"setpoint_ 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:3388
#, no-wrap
msgid "Recreational dives"
msgstr ""

#. type: Plain text
#: user-manual.txt:3397
msgid ""
"Recreational mode is intended for what most divers would call "
"\"recreational\", \"sports\"or \"nontechnical\" dives, remaining within "
"no-deco limits (NDL).  It computes the maximum time a diver can stay at the "
"current depth without needing mandatory decompression stops and without "
"using more than the existing gas (minus a reserve). The planner "
"automatically takes into account the nitrogen load incurred in previous "
"dives. But conventional dive tables are also used in a way that can take "
"into account previous dives. Why use a dive planner for recreational dives? "
"The subsurface dive planner provides two significant advantages over the use "
"of recreational dive tables for dive planning."
msgstr ""

#. type: Plain text
#: user-manual.txt:3407
msgid ""
"Firstly, using recreational dive tables, the maximum depth of each previous "
"dive is taken into account. But few dives are done at a constant depth "
"corresponding to the maximum depth (i.e. a \"square\" dive profile). This "
"means dive tables overestimate the nitrogen load incurred during previous "
"dives. The _Subsurface_ dive planner calculates nitrogen load according to "
"the real dive profiles of all uploaded previous dives, in a similar way as "
"dive computers calculate nitrogen load during a dive. This means that the "
"diver gets 'credit,' in terms of nitrogen load, for not remaining at maximum "
"depth during previous dives, so a longer subsequent dive can be planned.  "
"For the planner to work it's therefore crucial to log previous dives in "
"_Subsurface_ before doing dive planning."
msgstr ""

#. type: Plain text
#: user-manual.txt:3413
msgid ""
"Secondly, recreational dive tables are not designed to build additional "
"safety features into a dive. NDL times derived from dive tables often take "
"divers close to the limit where decompression sickness (DCS) can arise. The "
"Subsurface dive planner allows a diver to build more safety features into a "
"dive plan, preventing recreational divers from getting close to the limits "
"of getting a DCS hit. This is performed by specifying appropriate gradient "
"factors for a dive plan, as explained below."
msgstr ""

#. type: Plain text
#: user-manual.txt:3415
msgid "To plan a dive, the appropriate settings need to be defined."
msgstr ""

#. type: Plain text
#: user-manual.txt:3418
msgid ""
"Ensure the date and time is set to that of the intended dive. This allows "
"calculation of the nitrogen load incurred during previous dives."
msgstr ""

#. type: Plain text
#: user-manual.txt:3421
msgid ""
"Immediately under the heading _Planning_ are two checkboxes _Recreational_ "
"and _Safety Stop_.  Check these two boxes."
msgstr ""

#. type: Plain text
#: user-manual.txt:3425
msgid ""
"Then define the cylinder size, the gas mixture (air or % oxygen) and the "
"working cylinder pressure in the top left-hand section of the planner under "
"_Available gases_."
msgstr ""

#. type: Plain text
#: user-manual.txt:3430
msgid ""
"The planner calculates whether the specified cylinder contains enough "
"air/gas to complete the planned dive. In order for this to be accurate, "
"under _Gas options_, specify an appropriate surface air consumption (SAC) "
"rate for _Bottom SAC_. Suitable values are between 15 l/min and 30 l/min, "
"with novice divers or difficult dives requiring SAC rates closer to 30l/min."
msgstr ""

#. type: Plain text
#: user-manual.txt:3437
msgid ""
"Define the amount of gas the cylinder must have at the end of the bottom "
"section of the dive just before ascent. A value of 50 bar is often used. The "
"reason for this reserve gas is to provide for the possible need to bring a "
"buddy to the surface using gas sharing. How much gas is used in sharing "
"depends on the depth of the ascent. This can be difficult to estimate, so "
"most agencies assume a fixed amount of gas, or actually of pressure e.g. 40 "
"or 50 bar or 25% or 33% (rule of thirds). But _Subsurface_ can do better "
"because it knows about the ascent and that is why we add the amount of gas "
"during the ascent."
msgstr ""

#. type: Plain text
#: user-manual.txt:3445
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 described 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:3448
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:3459
msgid ""
"To build additional safety into the dive plan (over and above those of "
"recreational dive tables), specify gradient factors less than 100% (_GFHigh_ "
"and _GFLow_ under the _Planning_ heading in the planner). On the other hand, "
"to approximate the values in recreational dive tables, set the gradient "
"factors to 100.  By reducing the values of GFHigh and GFLow to values below "
"100, one can build more safety into a dive. Decreasing the values of the "
"gradient factors below 100 will shorten the duration of the dive. This is "
"the price of a larger safety margin. Reasons for using gradient factors less "
"than 100 may be the age of the diver, the health of a diver, or unusual "
"conditions such as cold water or strong currents.  Realistic conservative "
"values for the gradient factors are GFLow=40% and GFHigh=80%. This allows "
"you to create a cusom dive plan, suited to yourself as well as the dive "
"conditions."
msgstr ""

#. type: Plain text
#: user-manual.txt:3462
msgid ""
"Below is an image of a dive plan for a recreational dive at 30 meters with "
"gradient factors of 100. Because the no-deco limit (NDL) is 22 minutes, "
"there remains a significant amount of air in the cylinder at the end of the "
"dive."
msgstr ""

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

#. type: Plain text
#: user-manual.txt:3472
msgid ""
"The dive profile in the planner shows the maximum dive time within no-deco "
"limits using the Bühlmann ZH-L16 algorithm and the gas and depth settings "
"specified as described above. The _Subsurface_ planner allows rapid "
"assessment of dive duration as a function of dive depth, given the nitrogen "
"load incurred during previous dives. The dive plan includes estimates of the "
"amount of air/gas used, depending on the cylinder settings specified under "
"_Available gases_. If the start cylinder pressure is left blank, 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:3475
msgid ""
"Below is the same dive plan as above, but with a safety stop and reduced "
"gradient factors for a larger safety margin."
msgstr ""

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

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

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

#. type: Plain text
#: user-manual.txt:3493
#, no-wrap
msgid ""
"*a) Nitrogen management*: This is done by specifying the rates for descent "
"and ascent,\n"
"as well as the deco model (GFLow, GFHigh or Conservatism level) under the "
"headings _Rates_ and _Planning_\n"
"to the bottom left of the planning screen. Two deco models are supported the "
"Bühlmann model and the VPM-B\n"
"model. Select one of the two models. When selecting the Bühlmann model, the "
"gradient factors (GFHigh and GFLow\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_.\n"
"Gradient Factor settings strongly affect the calculated ceilings and their "
"depths.\n"
"A very low GFLow value brings on decompression stops early during the "
"dive.\n"
msgstr ""

#. type: Plain text
#: user-manual.txt:3495
#, no-wrap
msgid ""
" ** 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:3501
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, albeit "
"at the cost of higher tissue compartment pressures in the slow tissues.  "
"When selecting one of these models, keep in mind they are NOT exact "
"physiological models but only mathematical models that appear to work in "
"practice."
msgstr ""

#. type: Plain text
#: user-manual.txt:3512
msgid ""
"Please note as well that there is an intrinsic assumption of the VPM-B model "
"that off-gassing only happens during the ascent phase of the dive (which is "
"the part controlled by the planner). Thus it is possible to get misleading "
"results if you manually enter waypoints well in the decompression phase of "
"your dive. This is particularly relevant when editing a dive read from disk "
"in the planner since that will have waypoints up to the surface. Thus for "
"those dives, first delete all waypoints during the ascent phase. This is "
"most easily done by holding the Ctrl- or Command-key while clicking on the "
"trash can icon next to the first ascent waypoint in the table on the left "
"hand side."
msgstr ""

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

#. type: Plain text
#: user-manual.txt:3516
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:3517
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:3519
msgid ""
"link:https://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:3527
msgid ""
"The ascent rate is critical for nitrogen off-gassing at the end of the dive "
"and is specified for several depth ranges, using the mean depth as a "
"yardstick. The mean depth of the dive plan is shown by a light grey line on "
"the dive profile. Ascent rates at deeper levels are often in the range of "
"8-12 m/min, while ascent rates near the surface are often in the range of "
"4-9 m/min. The descent rate is also specified. If the option _Drop to first "
"depth_ is activated, the descent phase of the planned dive will be at the "
"maximal descent rate specified in the _Rates_ section of the dive setup."
msgstr ""

#. type: Plain text
#: user-manual.txt:3536
#, 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"
"Commonly 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. The depth "
"at which switching to a gas\n"
"takes place can be edited in the\n"
"_Available Gases_ dialog. Normally, the planner decides on switching to a "
"new gas when, during\n"
"ascent, the partial pressure of the new gas has decreased to 1.6 bar.\n"
msgstr ""

#. type: Plain text
#: user-manual.txt:3558
#, no-wrap
msgid ""
"*c) Gas management*: With open-circuit dives this is a primary\n"
"consideration. Divers need to keep within the limits of the amount of\n"
"gas within the dive\n"
"cylinder(s), allowing for an appropriate margin for a safe return to the "
"surface, possibly\n"
"sharing with a buddy. Under the _Gas Options_ heading, specify the best (but "
"conservative) estimate\n"
"of your surface-equivalent air consumption (SAC, also termed RMV) in\n"
"liters/min (for the time being, only SI units are supported). Specify the "
"SAC during the\n"
"bottom part of the dive (_bottom SAC_) as well as during the decompression "
"or safety stops of the\n"
"dive (_deco SAC_). Values of 15-30 l/min are common. For good gas "
"management, a guess\n"
"is not sufficient and you needs to\n"
"monitor gas consumption on a regular basis, dependent on different dive "
"conditions and/or equipment.\n"
"The planner calculates the total volume of gas used during the dive and "
"issues a warning\n"
"if you exceeds the total amount of gas available. Good practice demands that "
"divers not dive to\n"
"the limit of the gas supply but that an appropriate reserve is kept\n"
"for unforeseen circumstances.\n"
"For technical diving, this reserve can be up to 66% of the total available "
"gas.\n"
"In addition to calculating the total gas consumption for every cylinder the "
"planner provides one way\n"
"of calculating the recommended volume of bottom gas which is needed for safe "
"ascent to the\n"
"first deco gas change depth or the surface. This procedure is called the "
"\"minimum gas\" or \"rock bottom\"\n"
"consideration and it is used by various (but not all)\n"
"technical diving organisations. See the text below for a detailed "
"explanation.\n"
msgstr ""

#. type: Plain text
#: user-manual.txt:3570
msgid ""
"Now you can start the detailed time-depth planning of the dive. _Subsurface_ "
"offers an unique graphical interface for doing planning. The mechanics are "
"similar to hand-entering a dive profile in the dive log part of "
"_Subsurface_. Upon activating the planner, a default dive of depth 15 m for "
"20 min is offered in the blue design surface in the top right hand part of "
"the planner window. The white dots (waypoints) on the profile can be dragged "
"with a mouse. Create more waypoints by double-clicking on the profile line "
"and ensuring the profile reflects the intended dive. Drag the waypoints to "
"represent the depth and duration of the dive. It is NOT necessary to specify "
"the ascent part of the dive since the planner calculates this, based on the "
"existing settings.  If any of the management limits (for nitrogen, oxygen or "
"gas) are exceeded, the surface above the dive profile changes from BLUE to "
"RED."
msgstr ""

#. type: Plain text
#: user-manual.txt:3581
msgid ""
"Each waypoint on the dive profile creates a _Dive Planner Point_ in the "
"table on the left of the dive planner panel. Ensure 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). In most cases _Subsurface_ computes additional "
"way points in order to fulfill decompression requirements for that dive. A "
"waypoint can also be moved by selecting it and by using the arrow keys.  The "
"waypoints listed in the _Dive Planner Points_ dialogue can be edited by hand "
"in order to get a precise presentation of the dive plan. In fact, it is "
"sometimes more easy to create the whole dive profile by editing the _Dive "
"Planner Points_ dialog."
msgstr ""

#. type: Plain text
#: user-manual.txt:3587
msgid ""
"Show any changes in gas cylinder used by indicating gas changes as explained "
"in the section <<S_CreateProfile,hand-creating a dive profile>>. These "
"changes should reflect the cylinders and gas compositions defined in the "
"table with _Available Gases_.  If two or more gases are used, automatic gas "
"switches will be planned during the ascent to the surface."
msgstr ""

#. type: Plain text
#: user-manual.txt:3601
msgid ""
"Cylinders used for the plan need to be entered in the table of _Available "
"gases_. In the column _Type_ select the appropriate cylinder size by using "
"the dropdown list that appears when double-clicking a cell in this "
"column. By default, a large number of sizes are listed, and a new cylinder "
"size can be created by typing this into the text box. The cylinder size, "
"start pressure and default switch depths are initialised "
"automatically. Specify the gas composition (e.g. helium and oxygen "
"content). A non-zero value in the \"CC setpoint\" 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 and the planner only "
"considers gas changes in OC mode."
msgstr ""

#. type: Plain text
#: user-manual.txt:3611
msgid ""
"Enter dive profile segments in the _Dive planner points_ table by providing "
"a time duration for a segment as well as its final depth. If more than one "
"cylinder is used during the dive, ensure that the appropriate cylinder is "
"selected for each segment of the dive plan by double-clicking the cell and "
"selecting the appropriate cylinder from the dropdown list in the _Used gas_ "
"column.  If required, insert a row in the _Dive planner points_ table by "
"adding a new line and then setting the _Run time_ value appropriately. In "
"image A below, a segment (using an EAN50 cylinder) has been added and you "
"wish to use this gas during the very start of the dive (the other gas is not "
"breathable at the surface).  Upon pressing Enter on the keyboard, that "
"segment is moved to the top of that table and the plan is adjusted "
"automatically to take into account this new segment of the dive plan (image "
"B below)."
msgstr ""

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

#. type: Plain text
#: user-manual.txt:3616
msgid ""
"Below is an example of a dive plan to 55m using Tx20/30 and the Bühlmann "
"algorithm, followed by an ascent using EAN50 and using the settings as "
"described above."
msgstr ""

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

#. type: Plain text
#: user-manual.txt:3622
msgid ""
"Once the above steps have been completed, save by clicking the _Save_ button "
"towards the top middle of the planner. The saved dive plan will appear in "
"the *Dive List* panel of _Subsurface_."
msgstr ""

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

#. type: Plain text
#: user-manual.txt:3632
msgid ""
"On the bottom right panel of the dive planner, under _Dive Plan Details_, "
"the details of the dive plan are provided. These 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:3637
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: Plain text
#: user-manual.txt:3657
#, no-wrap
msgid ""
"*Dive plan variations*: The planner has a check box _Display plan "
"variations_. By checking this box, the planner\n"
"provides information about a dive that is a little deeper or slightly\n"
"longer than the planned dive. This is found near the top of the _Dive plan "
"details_\n"
"where the dive duration is indicated. The information is intended to be used "
"if it is necessary to\n"
"modify the ascent \"on the fly\" in the case of unexpected deviations from "
"the dive plan during the dive.\n"
"For example, if it says \"Runtime: 123min, Stop times + 2:49 /m + 1:30 "
"/min\" this means: if you dive deeper\n"
"than planned, you should add almost 3 minutes per meter you go deeper to "
"your decompression (and\n"
"you can substract 3 minutes per meter that you stay shallower). If you "
"overstay your bottom\n"
"time, you need to add one and a half minutes to the stops for each minutes "
"you overstay\n"
"and similarly, you can shorten your deco time by one and a half minute for "
"each minute\n"
"you stay shorter. These variations of depth and time are based on the last "
"manually entered segment of the\n"
"dive (not necessarily the deepest). The additional minutes should be "
"distributed\n"
"over the differnent stops in a way proportional to the stop length, i.e. add "
"more of the\n"
"additional minutes to the longer, shallower stops. The given times refer to "
"the\n"
"duration of the decompression phase and do not include the extended bottom "
"time!\n"
"This way of altering dive plans becomes inaccurate for large deviations from "
"the original\n"
"plan. So it should not be trusted for more than a few minutes or meters of\n"
"deviations from the planned bottom time. Checking this option creates a lot "
"of additional computation,\n"
"to such a degree that the planner is slower than otherwise.\n"
msgstr ""

#. type: Plain text
#: user-manual.txt:3667
#, no-wrap
msgid ""
"*Minimum gas requirements*: The planner also estimates the _minimum gas_ "
"pressure\n"
"required for safe ascent after an event that causes the dive to be "
"aborted. The\n"
"calculation assumes that in worst case an out of gas (OoG)\n"
"situation occurs at the end of the planned bottom time at maximum depth, "
"requiring\n"
"additional time at maximum depth to solve the problem and forcing\n"
"the buddy pair the share the gas of one diver. In addition the combined SAC "
"of both\n"
"divers is increased by an estimated factor compared to the SAC of a single "
"diver under normal conditions.\n"
"The result of the minimum gas calculation for the bottom gas is printed to "
"the planner output. There\n"
"are two selector boxes on the left of the _Dive plan details_:\n"
msgstr ""

#. type: Plain text
#: user-manual.txt:3671
msgid ""
"_SAC factor_. This is an estimate of the degree to which your SAC increases "
"if a critical problem arises underwater, e.g. gas sharing or "
"entanglement. Realistic values range from 3 to 5, reflecting the gas use of "
"two divers sharing a single gas cylinder after an OoG situation."
msgstr ""

#. type: Plain text
#: user-manual.txt:3673
msgid ""
"_Problem solving time_. This is an estimate of how long you would take to "
"solve the problem before starting the ascent to terminate the dive. The "
"default value is 2 minutes."
msgstr ""

#. type: Plain text
#: user-manual.txt:3677
msgid ""
"Using the above information, the planner then estimates what the minimum "
"bottom gas cylinder pressure needs to be for a safe ascent. This information "
"is given near the bottom of the _Dive plan details_, following the "
"calculation of bottom gas used during the dive if it exactly follows the "
"plan. the minimum gas is typically given as:"
msgstr ""

#. type: Plain text
#: user-manual.txt:3679
#, no-wrap
msgid "  Minimum gas (based on 2.0xSAC/+1min@81m): 2130 l/90bar/Δ:+80bar\n"
msgstr ""

#. type: Plain text
#: user-manual.txt:3681
msgid "This indicates:"
msgstr ""

#. type: Plain text
#: user-manual.txt:3683
msgid "Within parentheses, the _SAC factor_ and _Problem solving time_ specified."
msgstr ""

#. type: Plain text
#: user-manual.txt:3684
msgid ""
"The number of liters of back gas required for a safe ascent (2130 litres in "
"the example above)"
msgstr ""

#. type: Plain text
#: user-manual.txt:3685
msgid ""
"The number of bars of back gas required for a safe ascent (90 bars in the "
"example above)."
msgstr ""

#. type: Plain text
#: user-manual.txt:3688
msgid ""
"The delta-value: number of bars of back gas available at the end of the "
"bottom section of the dive, _over and above_ the minimum gas requirement (80 "
"bars in the above example). A positive delta reflects a safe plan; a "
"negative delta indicates insufficient gas for a safe ascent."
msgstr ""

#. type: Plain text
#: user-manual.txt:3692
msgid ""
"No automatic checks are performed based on this result.  The feature only "
"gives valid results for simple, rectangular shaped single level dive "
"profiles. For multi level dives one would need to check every leg of the "
"profile independently."
msgstr ""

#. type: Plain text
#: user-manual.txt:3706
#, no-wrap
msgid ""
"*Isobaric counterdiffusion information*: For gas switches during the ascent "
"in hypoxic open-circuit trimix dives information\n"
"about isobaric counterdiffusion (icd) is given near the bottom of the _Dive "
"plan details_, based on the\n"
"rule-of-fifths (i.e. during a gas change, the increase in nitrogen partial "
"pressure should not exceed\n"
"one fifth of the corresponding decrease in partial pressure of helium). For "
"each gas change, two lines\n"
"are printed, indicating the changes in gas fractions (%) and the equivalent "
"changes in partial pressures. If the\n"
"rule-of-fifths is not met, the relevant information is highlighted in red "
"and a warning message appears\n"
"at the bottom of that table. The gas change events on the dive profile also "
"provide information on icd,\n"
"visible at the bottom of the _Information box_ when the mouse hovers on the "
"respective gas change icon. This information\n"
"is only shown for gas changes relevant with respect to icd. If the "
"rule-of-fifths is not met,\n"
"a red warning exclamation mark is shown over the gas change icon. When "
"relevant, the _Information box_ contains\n"
"information such as: ICD ΔHe:-13% ΔN₂+3%>2.6%. This means: for this gas "
"change, the helium\n"
"decreased with 13% while the nitrogen increased with 3% which\n"
"is more than the 2.6% maximum increase in nitrogen suggested by the "
"rule-of-fifths.\n"
msgstr ""

#. type: delimited block *
#: user-manual.txt:3715
msgid ""
"The *plan variations* and *minimum gas* estimates are only guidelines for a "
"diver performing dive planning, intended to enhance the safety of executing "
"a particular dive plan and do not replace formal contingency planning for a "
"specific dive. They are NOT precise and should NOT be relied upon as the "
"only safety features in dive planning. Interpret these estimates within the "
"framework of your formal training to perform dive planning."
msgstr ""

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

#. type: Plain text
#: user-manual.txt:3737
#, 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 ->   Profile_\n"
"from the main menu, where the gas consumption calculation takes into account "
"the pSCR dump\n"
"ratio (default 1:8) as well as the metabolic rate. Specify the bottom and "
"deco SAC rates.\n"
"Here the SAC in the planner is the volume of gas per minute\n"
"that is exhaled into the loop on the surface, *not* the amount of gas that "
"escapes into the water.\n"
"The calculation takes the oxygen drop\n"
"across the mouthpiece of the rebreather into account. If the\n"
"pO~2~ drops below what is considered safe, a warning appears in the _Dive "
"plan\n"
"details_. A typical pSCR cylinder setup is very similar to an open circuit "
"dive;\n"
"one or more dive cylinders, possibly with different bottom and "
"decompression\n"
"gases, including gas switches during the dive like in open circuit diving.\n"
"Therefore, the setup of the _Available gases_ and the _Dive planner points_ "
"tables\n"
"are very similar to that of a open circuit dive plan, described "
"above. 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:3738
#, no-wrap
msgid "images/Planner_pSCR.jpg"
msgstr ""

#. type: Title ====
#: user-manual.txt:3740
#, no-wrap
msgid "Planning for pSCR bailout"
msgstr ""

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

#. type: Plain text
#: user-manual.txt:3767
msgid ""
"Open circuit diving is often part of a pSCR dive because, at shallow depths, "
"the pO~2~ in the loop is often too low for breathing and the shallow parts "
"of a pSCR dive are often done on OC. The change from rebreather mode to OC "
"or _vice versa_ is indicated using bailout events. The image on the left "
"shows a pSCR dive plan (using three cylinders) where the shallow parts of "
"the dive are performed using EAN50 in order to have a sufficient pO~2~. The "
"bottom part of the dive is perfomed with EAN31 (Cyl. 2 in the *Available "
"gases* table, also indicated in the *Dive planner points* table). The third "
"cylinder, also EAN31, is a bailout cylinder which is, initially, not used.  "
"In this case the plan is for a cave dive with a bottom time of 20 minutes "
"and the turning point in the bottom part of the dive is at 16 minutes "
"(i.e. ten minutes into the bottom part of the dive). The orange pO~2~ graph "
"indicates the equivalent OC pO~2~ during the dive and the green pO~2~ "
"indicates the estimated pO~2~ in the loop, the whole dive being performed in "
"rebreather mode. We wish to plan for a worst-case scenario with bailout at "
"the turning point (i.e. the furthest point into the cave). In the *Dive "
"planner points* table, change the *Dive mode* of the last two segments to "
"*OC* (indicated in the left-hand image, labled *A*, below). In this case the "
"existing EAN31 cylinder (Cyl.2 in the *Dive planner points* table is used "
"for bailout (i.e. the bailout cylinder [Cyl. 3] has not been used yet). Note "
"that the pO~2~ graph now indicates the appropriate pO~2~ values, since the "
"gas breathed now has the pO~2~ of an OC configuration. In order to switch to "
"the bailout cylinder (Cyl. 3), indicate this by selecting the appropriate "
"cylinder in the *Dive planner points* table as indicated in the image on the "
"right, below (labeled *B*). The icon on the depth profile now shows an "
"overlapping bailout event with cylinder change. As in the graph on the left, "
"the appropriate pO~2~ values are shown in the pO~2~ graphs. The volumes of "
"gas required can be obtained at the bottom of the *Dive plan details* panel."
msgstr ""

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

#. type: Plain text
#: user-manual.txt:3774
msgid ""
"In the case of a pSCR dive plan for open water, the worst-case scenario is "
"probably bailout at the end of the deepest part of the dive.  Create a "
"1-minute segment at the end of the deepest part of the dive plan. This last "
"segment (represented by the bottom row of the *Dive planner points* table) "
"is then manipulated using the *Dive mode* and *Used gas* columns, as in the "
"cave example, above. See the example of bailout for a CCR dive, below, that "
"uses this approach."
msgstr ""

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

#. type: Plain text
#: user-manual.txt:3779
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:3783
#, 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:3793
#, no-wrap
msgid ""
"*Entering setpoints*: Specify a default setpoint in the Preferences tab, by "
"selecting _File ->  Preferences ->  Profile_ 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. 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"
"this is calculated for bail out ascents.\n"
msgstr ""

#. type: Plain text
#: user-manual.txt:3795
msgid "The dive profile for a CCR dive may look something like the image below."
msgstr ""

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

#. type: Plain text
#: user-manual.txt:3800
msgid ""
"Note that, in the _Dive plan details_, the gas consumption for a CCR segment "
"is not calculated, so gas consumptions of 0 liters are the norm."
msgstr ""

#. type: Title ====
#: user-manual.txt:3801
#, no-wrap
msgid "Planning for CCR bailout"
msgstr ""

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

#. type: Plain text
#: user-manual.txt:3808
msgid ""
"It is often necessary to plan for a worst-case bailout event in order to "
"ensure sufficient bailout gas to reach the surface, taking into account "
"decompression. This is done by defining a 1-minute segment at the end of the "
"bottom part of the dive, as in the image on the left where a CCR dive to 40m "
"for 21 minutes is planned."
msgstr ""

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

#. type: Plain text
#: user-manual.txt:3817
msgid ""
"In the dive planner points table, change the _Dive mode_ of this 1-minute "
"segment to _OC_. This signifies bailout. In this case there is bailout to "
"the existing diluent cylinder (assuming this cylinder has sufficient "
"gas). The appropriate pO~2~ and cylinder pressure graphs are shown in the "
"dive profile, as in the image on the left. Note that the setpoint drops to "
"zero after bailout, since this value does not apply to breathed bailout gas."
msgstr ""

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

#. type: Plain text
#: user-manual.txt:3824
msgid ""
"In order to plan for bailout to an external bailout cylinder, change the "
"_Used gas_ for the 1-minute segment to the appropriate cylinder, as in the "
"example on the left. Note that the cylinder change as well as the bailout "
"are indicated with overlapping icons."
msgstr ""

#. type: Plain text
#: user-manual.txt:3826
msgid ""
"The volumes of gases required for bailout can be found at the bottom of the "
"*Dive plan details* panel."
msgstr ""

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

#. type: Plain text
#: user-manual.txt:3835
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 no way to "
"change a saved dive plan.  To change a dive plan, select it on the *Dive "
"List*. Then, in the main menu, select _Log -> Re-plan dive_. This will open "
"the selected dive plan within the dive planner, allowing changes to be made "
"and saved as usual."
msgstr ""

#. type: Plain text
#: user-manual.txt:3841
msgid ""
"In addition, there is the option \"Save new\". This keeps the original "
"planned dive and adds a (possibly modified, - earlier dives are now taken "
"into account -) 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:3842
#, no-wrap
msgid "Planning for repetitive dives"
msgstr ""

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

#. type: Plain text
#: user-manual.txt:3855
msgid ""
"If you have just completed a long/deep dive and are planning another dive, "
"then highlight, in the *Dive List*, the dive that has just been logged then "
"activate the planner. Depending on the start time of the planned dive, the "
"planner takes into account the gas loading during the completed dive and "
"plans accordingly."
msgstr ""

#. type: Plain text
#: user-manual.txt:3860
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 you "
"want to plan a dive using this configuration, highlight the template dive in "
"the *Dive List* and activate the planner: the planner takes into account the "
"configuration in the highlighted dive."
msgstr ""

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

#. type: Plain text
#: user-manual.txt:3866
msgid ""
"Selecting the _Print_ button in the planner allows printing of the _Dive "
"Plan Details_ for wet notes. You can also cut and paste the _Dive Plan "
"Details_ to include in a text file or word processing document."
msgstr ""

#. type: Plain text
#: user-manual.txt:3872
msgid ""
"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_ function on the main menu in the same way as "
"for dive logs or by copy and paste to a word processor."
msgstr ""

#. type: Title ===
#: user-manual.txt:3874
#, no-wrap
msgid "Saving a dive with its dive plan"
msgstr ""

#. type: Plain text
#: user-manual.txt:3881
msgid ""
"In the section dealing with <<S_MultipleDiveComputers, dives using more than "
"one dive computer>> we discussed the way in which multiple profiles for a "
"single dive can be viewed using the left-arrow and right-arrow keyboard "
"keys. A similar method can be used for saving a dive plan with the profile "
"of the actual dive, once this has been uploaded into _Subsurface_.  In order "
"to do this:"
msgstr ""

#. type: Plain text
#: user-manual.txt:3883
msgid "Do the dive planning and save the final plan in the _Dive List_."
msgstr ""

#. type: Plain text
#: user-manual.txt:3884
msgid "After diving, upload the dive data from the dive computer."
msgstr ""

#. type: Plain text
#: user-manual.txt:3886
msgid ""
"Change the date and time of the _dive plan_ to coincide with that of the "
"real-life dive from the _dive computer_."
msgstr ""

#. type: Plain text
#: user-manual.txt:3889
msgid ""
"In the _Dive List_, highlight the dive plan as well as the data for the real "
"dive and merge the two dives, making use of the Dive List Context Menu "
"(available by right-clicking a dive)."
msgstr ""

#. type: Plain text
#: user-manual.txt:3893
msgid ""
"The text version of the dive plan is appended to the Notes in the _Notes "
"Tab_. With this merged dive highlighted in the _Dive List_, switch between "
"the planned profile and the real-life profile using the "
"right-arrow/left-arrow keyboard keys."
msgstr ""

#. type: Title ==
#: user-manual.txt:3894
#, no-wrap
msgid "Running _Subsurface_ from the command-line"
msgstr ""

#. type: Plain text
#: user-manual.txt:3898
msgid ""
"_Subsurface_ can be launched from the command-line to set some specialised "
"settings or as part of an script-based automated process for manipulating a "
"dive log. The format for launching _Subsurface_ from the command-line is:"
msgstr ""

#. type: Plain text
#: user-manual.txt:3900
#, no-wrap
msgid "\tsubsurface [options] [logfile ...] [--import logfile ...]\n"
msgstr ""

#. type: Plain text
#: user-manual.txt:3902
msgid "The options include:"
msgstr ""

#. type: delimited block |
#: user-manual.txt:3914
#, no-wrap
msgid ""
"|*Command-line option*|*Description*\n"
"|--help|Print a summary of the command-line options\n"
"| -h|Print a summary of the command-line options\n"
"|--import logfile ...|A file name before this option is treated as an "
"existing dive log, everything after is imported into the existing dive log\n"
"|--verbose|Print debug information while running _Subsurface_\n"
"| -v|Print debug information while running _Subsurface_\n"
"| -v -v| Print even more debug information while running _Subsurface_\n"
"|--version|Prints the current version of _Subsurface_\n"
"|--survey|Opens the xref:S_UserSurvey[user survey] immediately after "
"starting _Subsurface_\n"
"|--user=<username>|Choose the xref:S_user_space[configuration space] of user "
"<username>\n"
"|--cloud-timeout=<duration>|Set the timeout for cloud connection (0 < "
"duration < 60). This enables longer timeouts for slow Internet connections\n"
msgstr ""

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

#. type: Plain text
#: user-manual.txt:3921
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:3922
#, no-wrap
msgid "File"
msgstr ""

#. type: Plain text
#: user-manual.txt:3925
msgid ""
"<<S_NewLogbook,_New Logbook_>> - Close the currently open dive logbook and "
"clear all dive information."
msgstr ""

#. type: Plain text
#: user-manual.txt:3927
msgid "_Open logbook_ - Open the file manager to select a dive logbook to open."
msgstr ""

#. type: Plain text
#: user-manual.txt:3928
msgid "_Save_ - Save the dive logbook currently open."
msgstr ""

#. type: Plain text
#: user-manual.txt:3929
msgid "_Save as_ - Save the current logbook under a different file name."
msgstr ""

#. type: Plain text
#: user-manual.txt:3930
msgid ""
"_Open cloud storage_ - Open the dive log previously saved in "
"<<S_Cloud_storage,_Cloud storage_>>."
msgstr ""

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

#. type: Plain text
#: user-manual.txt:3932
msgid ""
"_Cloud storage online_ - Switch between the online version of the logbook, "
"and the locally stored one."
msgstr ""

#. type: Plain text
#: user-manual.txt:3933
msgid "_Close_ - Close the dive logbook currently open."
msgstr ""

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

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

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

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

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

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

#. type: Title ===
#: user-manual.txt:3943
#, no-wrap
msgid "Edit"
msgstr ""

#. type: Plain text
#: user-manual.txt:3945
msgid "The Edit option allows one to undo or redo an action, e.g. deleting dives."
msgstr ""

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

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

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

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

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

#. type: Plain text
#: user-manual.txt:3957
msgid "<<S_DivePlanner,_Plan Dive_>> - Plan dives."
msgstr ""

#. type: Plain text
#: user-manual.txt:3958
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:3960
msgid ""
"<<S_CopyComponents,_Copy dive components_>> - Copy information from several "
"fields of a dive log onto the clipboard."
msgstr ""

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

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

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

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

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

#. type: Plain text
#: user-manual.txt:3972
msgid "<<S_ViewPanels,_All_>> - View the four main _Subsurface_ panels all at once."
msgstr ""

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

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

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

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

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

#. type: Plain text
#: user-manual.txt:3981
msgid ""
"_Prev DC_ - Switch to data from previous dive computer, if a single dive was "
"logged from more than one.  See the sections on "
"<<S_MultipleDiveComputers,using multiple dive computers for the same dive>> "
"and <<S_MergeDivePlan, Saving an uploaded dive with its dive plan>>."
msgstr ""

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

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

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

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

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

#. type: Plain text
#: user-manual.txt:3990
msgid ""
"_About Subsurface_ - Show a panel with the version number of _Subsurface_ as "
"well as licensing information."
msgstr ""

#. type: Plain text
#: user-manual.txt:3992
msgid ""
"_Check for updates_ - Find out whether a newer version of Subsurface is "
"available on the https://subsurface-divelog.org/[_Subsurface_ web site]."
msgstr ""

#. type: Plain text
#: user-manual.txt:3994
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:3995
msgid "_User manual_ - Open a window showing this user manual."
msgstr ""

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

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

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

#. type: Plain text
#: user-manual.txt:4012
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:4016
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:4023
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 "
"https://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:4025
#, 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:4026
#, no-wrap
msgid "images/icons/usb.jpg"
msgstr ""

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

#. type: Plain text
#: user-manual.txt:4039
msgid ""
"Simply try COM1, COM2, etc. The drop down list should contain all connected "
"COM devices."
msgstr ""

#. type: Title ====
#: user-manual.txt:4040 user-manual.txt:4138
#, no-wrap
msgid "On MacOS:"
msgstr ""

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

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

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

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

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

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

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

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

#. type: Plain text
#: user-manual.txt:4071
#, 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:4076
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:4078
msgid "Ensuring the user has write permission to the USB serial port:"
msgstr ""

#. type: Plain text
#: user-manual.txt:4088
msgid ""
"On Unix-like operating systems the USB ports can only be accessed by users "
"who are members special group that can be e.g.  +dialout+ or +uucp+. This "
"can be verified by listing the appropriate device permissions e.g. by +ls -l "
"/dev/ttyUSB0+. Note that the number in the file name depends on how many USB "
"devices you have connected, and must be adjusted appropriately.  If you are "
"not root, you may not be a member of that group and won't be able to use the "
"USB port. Let us assume your username is 'johnB'."
msgstr ""

#. type: Plain text
#: user-manual.txt:4092
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:4097
#, 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:4099
#, no-wrap
msgid ""
"Under some circumstances this change takes only effect (eg. on Ubuntu) "
"after\n"
"you log out and then log in again.\n"
msgstr ""

#. type: Plain text
#: user-manual.txt:4104
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 you "
"should be able to import dives."
msgstr ""

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

#. type: Plain text
#: user-manual.txt:4114
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 device’s name to communicate with "
"_Subsurface_. Follow these steps:"
msgstr ""

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

#. type: Plain text
#: user-manual.txt:4120
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:4122
#, no-wrap
msgid "*Pair the _Subsurface_ computer with the dive computer.*\n"
msgstr ""

#. type: Plain text
#: user-manual.txt:4131
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:4134
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:4137
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:4144
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:4147
msgid ""
"Once the pairing is complete, the correct device is shown in the 'Device or "
"Mount Point' drop-down in the _Subsurface_ *Import* dialog."
msgstr ""

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

#. type: Plain text
#: user-manual.txt:4156
msgid ""
"Be sure Bluetooth is enabled on the _Subsurface_ computer.  On most common "
"distributions this should be true out of the box and pairing should be "
"straightforward. For instance, Gnome3 shows a Bluetooth icon on the right of "
"the toolbar at the top of the screen.  Users have reported difficulties with "
"some Bluetooth controllers.  If you have an onboard controller, try that "
"first.  It is simplest if you remove any USB Bluetooth dongles.  If you have "
"a USB dongle that came with your dive computer, try that before any others."
msgstr ""

#. type: Plain text
#: user-manual.txt:4160
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:4162
msgid "Enable the Bluetooth controller and pair your dive computer"
msgstr ""

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

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

#. type: Plain text
#: user-manual.txt:4170
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:4175
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:4177
msgid "+sudo usermod -a -G dialout username+"
msgstr ""

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

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

#. type: Plain text
#: user-manual.txt:4186
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:4189
msgid ""
"If the graphical method doesn't work, pair the device from the command "
"line. Open a terminal and use +hciconfig+ to check the Bluetooth controller "
"status."
msgstr ""

#. type: Plain text
#: user-manual.txt:4196
#, 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:4201
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:4209
#, 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:4211
msgid "Check that the status now includes '+UP+', '+RUNNING+' AND '+AUTH+'."
msgstr ""

#. type: Plain text
#: user-manual.txt:4213
msgid ""
"If there are multiple controllers running, it's easiest to turn off the "
"unused controller(s). For example, for +hci1+:"
msgstr ""

#. type: Plain text
#: user-manual.txt:4215
#, no-wrap
msgid "\tsudo hciconfig hci1 down\n"
msgstr ""

#. type: Plain text
#: user-manual.txt:4218
msgid ""
"Next step is to 'trust' and 'pair' the dive computer. On distros with Bluez "
"5, such as Fedora 22, you can use a tool called +blutootctl+, which will "
"bring up its own command prompt."
msgstr ""

#. type: Plain text
#: user-manual.txt:4239
#, 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:4242
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:4245
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:4250
#, 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:4252
msgid "Once the dive computer is paired, set up the RFCOMM connection."
msgstr ""

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

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

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

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

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

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

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

#. type: Plain text
#: user-manual.txt:4266
msgid ""
"If you omit 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:4268
msgid "_Shearwater Petrel 1_: channel 1"
msgstr ""

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

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

#. type: Plain text
#: user-manual.txt:4271
msgid "_Heinrichs-Weikamp OSTC Sport_: channel 1"
msgstr ""

#. type: Plain text
#: user-manual.txt:4273
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:4275
#, 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:4277
msgid "This gives the response:"
msgstr ""

#. type: Plain text
#: user-manual.txt:4280
#, 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:4282
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:4286
#, 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:4290
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:4300
#, 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:4303
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:4306
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:4312
#, no-wrap
msgid "APPENDIX B: Dive Computer specific information for importing dive data."
msgstr ""

#. type: Title ===
#: user-manual.txt:4315
#, no-wrap
msgid "Importing from Uemis Zurich"
msgstr ""

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

#. type: Plain text
#: user-manual.txt:4333
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 "
"you don’t enter a device name, but instead the location where the UEMISSDA "
"file system is mounted once connected to the dive computer. On Windows this "
"is a drive letter ( often 'E:' or 'F:'), on a Mac this is "
"'/Volumes/UEMISSDA' and on Linux systems this differs depending on the "
"distribution. On Fedora it usually is "
"'/var/run/media/<your_username>/UEMISSDA'. In all cases _Subsurface_ should "
"suggest the correct location in the drop down list."
msgstr ""

#. type: Plain text
#: user-manual.txt:4348
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 you "
"cannot download more than about 40-50 dives without running out of memory on "
"the SDA. This will usually only happen the very first time you download "
"dives from the Uemis Zurich.  Normally when downloading at the end of a day "
"or even after a dive trip, the capacity is sufficient. If _Subsurface_ "
"displays an error that the dive computer ran out of space, the solution is "
"straightforward.  Disconnect the SDA, turn it off and on again, and "
"reconnect it. You can now retry (or start a new download session) and the "
"download will continue where it stopped previously. You may have to do this "
"more than once, depending on how many dives are stored on the dive computer."
msgstr ""

#. type: Title ===
#: user-manual.txt:4350
#, no-wrap
msgid "Importing from Uwatec Galileo"
msgstr ""

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

#. type: Plain text
#: user-manual.txt:4367
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:4370
msgid ""
"After executing this command, Subsurface will recognize the Galileo dive "
"computer and download dive information."
msgstr ""

#. type: Plain text
#: user-manual.txt:4376
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, with drivers located on the download page for the "
"ScubaPro SmartTrak software."
msgstr ""

#. type: Plain text
#: user-manual.txt:4379
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:4381
#, no-wrap
msgid "Importing from Heinrichs Weikamp DR5"
msgstr ""

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

#. type: Plain text
#: user-manual.txt:4393
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 _Profile 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:4396
#, no-wrap
msgid "Importing from xDEEP BLACK"
msgstr ""

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

#. type: Plain text
#: user-manual.txt:4407
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 _Profile 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:4409
#, no-wrap
msgid "Importing from Shearwater Predator/Petrel/Nerd using Bluetooth"
msgstr ""

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

#. type: Plain text
#: user-manual.txt:4414
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:4416
#, no-wrap
msgid "Importing from Poseidon MkVI Discovery"
msgstr ""

#. type: Named 'icon' AttributeList argument for style 'icon'
#: user-manual.txt:4418
#, no-wrap
msgid "images/MkVI.jpeg"
msgstr ""

#. type: Plain text
#: user-manual.txt:4426
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 utilizes the "
"IrDA infra-red protocol. Only data for one dive can be downloaded at a time, "
"in three files:"
msgstr ""

#. type: Plain text
#: user-manual.txt:4429
msgid ""
"Setup configuration for the dive and key dive parameters (file with a .txt "
"extension)"
msgstr ""

#. type: Plain text
#: user-manual.txt:4430
msgid "Dive log details (file with a .csv extension)"
msgstr ""

#. type: Plain text
#: user-manual.txt:4432
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:4434
msgid ""
"_Subsurface_ accesses the .txt and the .csv files to get dive log "
"information."
msgstr ""

#. type: Title ===
#: user-manual.txt:4436
#, no-wrap
msgid "Importing from APD Inspiration/Evolution CCR"
msgstr ""

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

#. type: Plain text
#: user-manual.txt:4446
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:4448
msgid "Download the dive using _AP Communicator_."
msgstr ""

#. type: Plain text
#: user-manual.txt:4449
msgid "Open a dive within the _AP Log Viewer_."
msgstr ""

#. type: Plain text
#: user-manual.txt:4450
msgid "Select the tab at the top of the screen, entitled \"_Data_\"."
msgstr ""

#. type: Plain text
#: user-manual.txt:4451
msgid ""
"With the raw dive log data show on the screen, click on \"_Copy to "
"Clipboard_\"."
msgstr ""

#. type: Plain text
#: user-manual.txt:4452
msgid "Open a text editor, e.g. Notepad (Windows) or TextWrangler (Mac)."
msgstr ""

#. type: Plain text
#: user-manual.txt:4454
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:4455
msgid ""
"Within _Subsurface_, select _Import -> Import log files_ to open the "
"xref:Unified_import[universal import dialogue]."
msgstr ""

#. type: Plain text
#: user-manual.txt:4456
msgid ""
"In the dropdown list towards the bottom right of the dialogue (labeled "
"'Filter:'), select \"APD log viewer\"."
msgstr ""

#. type: Plain text
#: user-manual.txt:4460
#, no-wrap
msgid ""
"On the list of file names select the _.apd_ file  created. An import\n"
"dialogue opens showing the default settings for the data in the\n"
"_.apd_ file. If changes are required,\n"
"  do this as for xref:S_ImportingCSVDives[CSV imports].\n"
msgstr ""

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

#. type: Plain text
#: user-manual.txt:4469
msgid ""
"The top left hand dropdown box in the import panel lets you select the APD "
"dive computer for which the dive log needs to be imported. The default it is "
"DC1, _i.e._ the first of the two dive computers the APD uses. It is possible "
"to sequentially import the data for both dive computers by first importing "
"CD1 and then DC2.(*Hint*: The logs for the two dive computers are viewed by "
"selecting _View -> Next DC_ from the Main Menu after the uploading has been "
"completed)"
msgstr ""

#. type: Plain text
#: user-manual.txt:4470
msgid "Click the _Ok_ button at the bottom of the import panel."
msgstr ""

#. type: Plain text
#: user-manual.txt:4475
msgid ""
"The APD dive log will appear within _Subsurface_. The dive computer- "
"generated ceiling provided by the Inspiration can be viewed by selecting the "
"appropriate button on the left of the *Dive Profile*. Cylinder pressure data "
"are not logged by the APD equipment but can be manually entered in the "
"_Equipment_ Tab."
msgstr ""

#. type: Title ==
#: user-manual.txt:4476
#, no-wrap
msgid "APPENDIX C: Exporting Dive log information from external dive log software."
msgstr ""

#. type: Plain text
#: user-manual.txt:4485
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:4487
msgid "Export the foreign dive log data to format that is accessible from"
msgstr ""

#. type: Plain text
#: user-manual.txt:4488
msgid "_Subsurface_."
msgstr ""

#. type: Plain text
#: user-manual.txt:4489
msgid "Import the accessible dive log data into _Subsurface_."
msgstr ""

#. type: Plain text
#: user-manual.txt:4493
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:4495
#, no-wrap
msgid "Exporting from *Suunto Divemanager (DM3, DM4 or DM5)*"
msgstr ""

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

#. type: Plain text
#: user-manual.txt:4503
msgid ""
"DiveManager is a 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:4505
#, no-wrap
msgid "*Divemanager 3 (DM3):*\n"
msgstr ""

#. type: Plain text
#: user-manual.txt:4507
msgid "Start 'Suunto Divemanager 3' and log in with the name containing the logs"
msgstr ""

#. type: Plain text
#: user-manual.txt:4508
msgid "Do not start the import wizard to import dives from the dive computer."
msgstr ""

#. type: Plain text
#: user-manual.txt:4510
msgid ""
"In the navigation tree on the left side of the program-window, select the "
"appropriate dives."
msgstr ""

#. type: Plain text
#: user-manual.txt:4511
msgid "Within the list of dives, select the dives you would like to import later:"
msgstr ""

#. type: Plain text
#: user-manual.txt:4512
msgid "To select certain dives: hold 'ctrl' and click the dive"
msgstr ""

#. type: Plain text
#: user-manual.txt:4514
msgid ""
"To select all dives: Select the first dive, hold down shift and select the "
"last dive"
msgstr ""

#. type: Plain text
#: user-manual.txt:4515
msgid "With the dives marked, use the program menu _File -> Export_"
msgstr ""

#. type: Plain text
#: user-manual.txt:4516
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:4517
msgid "Click the browse button next to the field Export Path"
msgstr ""

#. type: Plain text
#: user-manual.txt:4519
#, 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:4520
#, no-wrap
msgid "Divelog.SDE file\n"
msgstr ""

#. type: Plain text
#: user-manual.txt:4522
#, no-wrap
msgid ""
"** Optionally change the name of the file for saving\n"
"** Click 'Save'\n"
msgstr ""

#. type: Plain text
#: user-manual.txt:4523
#, no-wrap
msgid "Back in the Export pop-up, press the button 'Export'\n"
msgstr ""

#. type: Plain text
#: user-manual.txt:4524
#, no-wrap
msgid "The dives are now exported to the file Divelog.SDE.\n"
msgstr ""

#. type: Plain text
#: user-manual.txt:4526
#, no-wrap
msgid "*Divemanager 4 (DM4) and Divemanager 5 (DM5):*\n"
msgstr ""

#. type: Plain text
#: user-manual.txt:4531
msgid ""
"DM4 and DM5 use identical mechanisms for exporting dive logs.  To export a "
"divelog from Divemanager you need to locate the DM4/DM5 database where the "
"dives are stored. You can either look for the original database or make a "
"backup of the dives. Both methods are described here."
msgstr ""

#. type: Plain text
#: user-manual.txt:4533
msgid "Locating the Suunto DM4 (or DM5) database:"
msgstr ""

#. type: Plain text
#: user-manual.txt:4535 user-manual.txt:4544
msgid "Start Suunto DM4/DM5"
msgstr ""

#. type: Plain text
#: user-manual.txt:4536
msgid "Select 'Help -> About'"
msgstr ""

#. type: Plain text
#: user-manual.txt:4537
msgid "Click 'Copy' after text 'Copy log folder path to clipboard'"
msgstr ""

#. type: Plain text
#: user-manual.txt:4538
msgid "Open Windows Explorer"
msgstr ""

#. type: Plain text
#: user-manual.txt:4539
msgid "Paste the address to the path box at the top of the File Explorer"
msgstr ""

#. type: Plain text
#: user-manual.txt:4540
msgid "The database is called DM4.db or DM5.db"
msgstr ""

#. type: Plain text
#: user-manual.txt:4542
msgid "Making a backup copy of the Suunto DM4/DM5 database:"
msgstr ""

#. type: Plain text
#: user-manual.txt:4545
msgid "Select 'File - Create backup'"
msgstr ""

#. type: Plain text
#: user-manual.txt:4547
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:4548
msgid "Click 'Save'"
msgstr ""

#. type: Plain text
#: user-manual.txt:4549
msgid "The dives are now exported to the file DM4.bak (or DM5.bak)"
msgstr ""

#. type: Title ===
#: user-manual.txt:4551
#, no-wrap
msgid "Exporting from Atomic Logbook"
msgstr ""

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

#. type: Plain text
#: user-manual.txt:4561
msgid ""
"Atomic Logbook is 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:4563
#, no-wrap
msgid "Exporting from Mares Dive Organiser V2.1"
msgstr ""

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

#. type: Plain text
#: user-manual.txt:4574
msgid ""
"Mares Dive Organizer is a Windows application. The dive log is kept as a "
"Microsoft SQL Compact Edition database with a '.sdf' filename extension. The "
"database includes all Dive Organizer-registered divers on the particular "
"computer and all Mares dive computers used. The safest way to get a copy of "
"the dive database is to export the information to another compatible format "
"which can then be imported into _Subsurface_."
msgstr ""

#. type: Plain text
#: user-manual.txt:4579
msgid ""
"Within Dive Organizer, select _Database -> Backup_ from the main menu and "
"back up the database to the desk top.  This creates a zipped file "
"DiveOrganizerxxxxx.dbf."
msgstr ""

#. type: Plain text
#: user-manual.txt:4582
msgid ""
"Rename the file to DiveOrganizerxxxxx.zip. Inside the zipped directory is a "
"file _DiveOrganizer.sdf_."
msgstr ""

#. type: Plain text
#: user-manual.txt:4583
msgid "Extract the _.sdf_ file from the zipped folder to your Desktop."
msgstr ""

#. type: Plain text
#: user-manual.txt:4584
msgid "The password for accessing the .zip file is _mares_."
msgstr ""

#. type: Title ===
#: user-manual.txt:4586
#, no-wrap
msgid "Exporting from *DivingLog 5.0 and 6.0*"
msgstr ""

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

#. type: Plain text
#: user-manual.txt:4595
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 would lack, for example, gas switches and information of "
"what units are used. With database import, all this information is included "
"and readily available."
msgstr ""

#. type: Plain text
#: user-manual.txt:4597
msgid "To transfer all files from DivingLog to Subsurface:"
msgstr ""

#. type: Plain text
#: user-manual.txt:4599
msgid "In DivingLog open the 'File -> Export -> SQLite' menu"
msgstr ""

#. type: Plain text
#: user-manual.txt:4600
msgid "Select 'Settings' button"
msgstr ""

#. type: Plain text
#: user-manual.txt:4601
msgid "Set the 'RTF2Plaintext' to 'true'"
msgstr ""

#. type: Plain text
#: user-manual.txt:4602
msgid "Close the Settings dialog"
msgstr ""

#. type: Plain text
#: user-manual.txt:4603
msgid "Click 'Export' button and select the filename"
msgstr ""

#. type: Plain text
#: user-manual.txt:4607
msgid ""
"Once this is done, open the saved database file with Subsurface and the "
"dives are automatically converted to Subsurface’s own format. Last step to "
"do is save the log file in Subsurface."
msgstr ""

#. type: Title ==
#: user-manual.txt:4608
#, no-wrap
msgid "APPENDIX D: Exporting a spreadsheet to CSV format"
msgstr ""

#. type: Plain text
#: user-manual.txt:4618
msgid ""
"Many divers keep a dive log in some form of digital file, commonly a "
"spreadsheet with various fields of information. These logs can be easily "
"imported into _Subsurface_ after the spreadsheet is converted in a .CSV "
"file.  This section explains the procedure to convert a diving logbook "
"stored in a spreadsheet to a .CSV file that will later be imported to "
"_Subsurface_.  Creating a .CSV is straightforward, although the procedure is "
"somewhat different according to which spreadsheet program is used."
msgstr ""

#. type: Plain text
#: user-manual.txt:4624
msgid ""
"Organize the diving data in the spreadsheet, so the first row contains the "
"names (or titles) of each column and the information for each dive is stored "
"in a single row.  _Subsurface_ supports many data items (Dive number, Date, "
"Time, Duration, Location, GPS, Max. Depth, Mean Depth, Buddy, Notes, Weight "
"and Tags).  Organize dive data following a few simple rules:"
msgstr ""

#. type: Plain text
#: user-manual.txt:4626
msgid "Date: use one of the following formats: yyyy-mm-dd, dd.mm.yyyy, mm/dd/yyyy"
msgstr ""

#. type: Plain text
#: user-manual.txt:4627
msgid "Duration: the format should be minutes:seconds."
msgstr ""

#. type: Plain text
#: user-manual.txt:4628
msgid ""
"Unit system: only one unit system should be used (no mix of imperial and "
"metric units)"
msgstr ""

#. type: Plain text
#: user-manual.txt:4629
msgid "Tags and buddies: values should be separated using a comma."
msgstr ""

#. type: Plain text
#: user-manual.txt:4630
msgid "GPS position: use decimal degrees, e.g. 30.22496 30.821798"
msgstr ""

#. type: Title ===
#: user-manual.txt:4631
#, no-wrap
msgid "_LibreOffice Calc_ and _OpenOffice Calc_"
msgstr ""

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

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

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

#. type: Plain text
#: user-manual.txt:4647
msgid ""
"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:4648
#, no-wrap
msgid "Microsoft _Excel_"
msgstr ""

#. type: Plain text
#: user-manual.txt:4654
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 uses the new character as a separator.  You "
"can change the character back to the default character by following the same "
"procedure, outlined below."
msgstr ""

#. type: Plain text
#: user-manual.txt:4656
msgid ""
"In Microsoft Windows, click the *Start* button, then select _Control Panel_ "
"from the list on the right-hand side."
msgstr ""

#. type: Plain text
#: user-manual.txt:4657
msgid "Open the _Regional and Language Options_ dialog box."
msgstr ""

#. type: Plain text
#: user-manual.txt:4659
msgid ""
"Do the following: ** In Windows 7, click the _Formats_ tab, and then click "
"_Customize this format_."
msgstr ""

#. type: Plain text
#: user-manual.txt:4660
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:4661
msgid "Click _OK_ twice."
msgstr ""

#. type: Plain text
#: user-manual.txt:4663
msgid "Below is an image of the _Control Panel_:"
msgstr ""

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

#. type: Plain text
#: user-manual.txt:4667
msgid "To export the dive log in CSV format:"
msgstr ""

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

#. type: Plain text
#: user-manual.txt:4676
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)_. Be sure the "
"appropriate folder has been selected to save the CSV file into."
msgstr ""

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

#. type: Plain text
#: user-manual.txt:4683
msgid ""
"Select the _Save_ button. The CSV-formatted file is saved into the folder "
"that was selected. You can double check the .CSV file by opening it with a "
"text editor, then import the dive data as explained on the section "
"xref:S_ImportingCSVDives[Importing CSV dives]."
msgstr ""

#. type: Title ==
#: user-manual.txt:4684
#, no-wrap
msgid "APPENDIX E: Writing a custom print template"
msgstr ""

#. type: Plain text
#: user-manual.txt:4689
msgid ""
"_Subsurface_ has a way to create or modify templates for printing dive logs "
"to produce customized printouts of them. Templates written in HTML, as well "
"as a simple Grantlee instruction set, are rendered to the print device by "
"_Subsurface_."
msgstr ""

#. type: Plain text
#: user-manual.txt:4691
msgid "Templates are accessed using the print dialogue (see image *B* below)."
msgstr ""

#. type: Plain text
#: user-manual.txt:4699
msgid ""
"The buttons under the _Template_ dropdown box lets you _Edit_, _Delete_, "
"_Import_ and _Export_ templates (see image *A* above). New or modified "
"templates are stored as HTML files in the same directory as the dive log "
"being processed. In order to create or modify a template, select one of the "
"templates from the template dropdown list in the print dialogue (see image "
"*B* above). Choose an existing template that resembles the final desired "
"printout. Then select _Edit_."
msgstr ""

#. type: Plain text
#: user-manual.txt:4701
msgid "The Edit Panel has three tabs:"
msgstr ""

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

#. type: Plain text
#: user-manual.txt:4706
msgid ""
"The _Style_ tab (image *A* above) controls the font, line spacing and color "
"template used for printing the dive log.  The style attributes are "
"editable. Choose one of the four color palettes used for color printing."
msgstr ""

#. type: Plain text
#: user-manual.txt:4710
msgid ""
"The _Colors_ tab (image *B* above) allows editing the colors used for "
"printing the dive log. The colors are highly customizable: the _Edit_ "
"buttons in the _Colors_ tab allows choosing arbitrary colors for different "
"components of the dive log printout."
msgstr ""

#. type: Plain text
#: user-manual.txt:4719
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 can create and format HTML code in a highly simple but "
"efficient way (see below). The HTML of the template can be edited and "
"saved. The saved template is stored in the same directory as the dive being "
"processed. By default, a _Custom_ template is a skeleton with no specific "
"print instructions. The information printed needs to be specified and "
"formatted in the template by replacing the section marked with: \"<!-- "
"Template must be filled -->\". Writing HTML code with Grantlee instructions "
"allows unlimited freedom in determining what is printed and in which way it "
"should be rendered."
msgstr ""

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

#. type: Plain text
#: user-manual.txt:4725
msgid ""
"You can adapt any of the existing templates and save it to the dive log "
"directory. The standard templates (e.g. One dive, Six dives, Table) can be "
"modified in this way. After completing the edits, use the _Export_ button in "
"the print dialogue to save the new template using a new template name."
msgstr ""

#. type: Plain text
#: user-manual.txt:4727
msgid ""
"To write a custom template, the following elements must exist so the "
"template will be correctly handled and rendered."
msgstr ""

#. type: Title ===
#: user-manual.txt:4728
#, no-wrap
msgid "Main dive loop"
msgstr ""

#. type: Plain text
#: user-manual.txt:4730
msgid ""
"_Subsurface_ exports a dive list called (*dives*) to the _Grantlee_ back "
"end. It is possible to iterate over the list as follows:"
msgstr ""

#. type: Block title
#: user-manual.txt:4730 user-manual.txt:4801 user-manual.txt:4818
#, no-wrap
msgid "template.html"
msgstr ""

#. type: delimited block .
#: user-manual.txt:4735
#, 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:4737 user-manual.txt:4806 user-manual.txt:4825
#, no-wrap
msgid "output.html"
msgstr ""

#. type: delimited block .
#: user-manual.txt:4742
#, 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:4745
msgid ""
"Additional information about _Grantlee_ can be found "
"http://www.grantlee.org/apidox/for_themers.html[here]"
msgstr ""

#. type: Title ===
#: user-manual.txt:4746
#, no-wrap
msgid "Grantlee exported variables"
msgstr ""

#. type: Plain text
#: user-manual.txt:4748
msgid "Only a subset of the dive data is exported:"
msgstr ""

#. type: delimited block |
#: user-manual.txt:4777
#, 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*) date of the dive\n"
"|time| (*string*) time of the dive\n"
"|location| (*string*) location of the dive\n"
"|duration| (*string*) duration of the dive\n"
"|depth| (*string*) depth of the dive\n"
"|divemaster| (*string*) divemaster for the dive\n"
"|buddy| (*string*) buddy for the dive\n"
"|airTemp| (*string*) air temperature of the dive\n"
"|waterTemp| (*string*) water temperature of the dive\n"
"|notes| (*string*) dive notes\n"
"|rating| (*int*) dive rating which ranges from 0 to 5\n"
"|sac| (*string*) SAC value for the dive\n"
"|tags| (*string*) list of dive tags for the dive\n"
"|gas| (*string*) list of gases used in the dive\n"
"|suit| (*string*) the suit used for the dive\n"
"|cylinders| (*string*) complete information of all used cylinders\n"
"|cylinder0-7| (*string*) information about a specific cylinder\n"
"|weights| (*string*) complete information of all used weight systems\n"
"|weight0-5| (*string*) information about a specific weight system\n"
"|maxcns| (*string*) maxCNS value for the dive\n"
"|otu| (*string*) OTU value for the dive\n"
"|sumWeight| (*string*) the summed weight of all used weight systems\n"
"|startPressure| (*string*) the start pressure\n"
"|endPressure| (*string*) the end pressure\n"
"|firstGas| (*string*) first used gas\n"
msgstr ""

#. type: Plain text
#: user-manual.txt:4780
msgid ""
"Please note that some of the variables like 'notes' need to be extended with "
"'|safe' to support HTML tags:"
msgstr ""

#. type: delimited block .
#: user-manual.txt:4782
#, no-wrap
msgid "\t<p> {{ dive.notes|safe }} </p>\n"
msgstr ""

#. type: Plain text
#: user-manual.txt:4784
msgid "Otherwise tags like 'br' would not be converted to line breaks."
msgstr ""

#. type: Plain text
#: user-manual.txt:4787
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:4799
#, 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:4804
#, no-wrap
msgid "\tborder-width: {{ template_options.borderwidth }}px;\n"
msgstr ""

#. type: delimited block .
#: user-manual.txt:4809
#, no-wrap
msgid "\tborder-width: 3px;\n"
msgstr ""

#. type: Plain text
#: user-manual.txt:4812
msgid ""
"Another variable that _Subsurface_ exports is *print_options*. This variable "
"contains a single member:"
msgstr ""

#. type: delimited block |
#: user-manual.txt:4815
#, 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:4823
#, no-wrap
msgid ""
"\tbody {\n"
"\t\t{{ print_options.grayscale }};\n"
"\t}\n"
msgstr ""

#. type: delimited block .
#: user-manual.txt:4830
#, no-wrap
msgid ""
"\tbody {\n"
"\t\t-webkit-filter: grayscale(100%);\n"
"\t}\n"
msgstr ""

#. type: Title ===
#: user-manual.txt:4832
#, no-wrap
msgid "Defined CSS selectors"
msgstr ""

#. type: Plain text
#: user-manual.txt:4835
msgid ""
"As the dive profile is placed after rendering, _Subsurface_ uses special "
"_CSS_ selectors to search in the HTML output. The _CSS_ selectors in the "
"following table should be added."
msgstr ""

#. type: delimited block |
#: user-manual.txt:4842
#, no-wrap
msgid ""
"|*Selector*|*Type*|*Description*\n"
"|dive_{{ dive.id }} | id | is used to fetch the relevant dive profile\n"
"|diveProfile | class | each dive that will contain a dive profile should "
"have this class selector in addition to the dive_{{ dive.id }} id selector\n"
"|dontbreak | class | prevents the dive with this class from being divided "
"into two pages. This can be used\n"
"in flow layout templates only (when data-numberofdives = 0)\n"
msgstr ""

#. type: Plain text
#: user-manual.txt:4845
msgid ""
"Rendering dive profiles is not supported for flow layout templates (when "
"data-numberofdives = 0)."
msgstr ""

#. type: Title ===
#: user-manual.txt:4846
#, no-wrap
msgid "Special attributes"
msgstr ""

#. type: Plain text
#: user-manual.txt:4850
msgid ""
"There are two ways of rendering- either rendering a specific number of dives "
"in each page or make _Subsurface_ try to fit as many dives as possible into "
"one page (_flow_ rendering)."
msgstr ""

#. type: Plain text
#: user-manual.txt:4852
msgid ""
"The *data-numberofdives* data attribute is added to the body tag to set the "
"rendering mode."
msgstr ""

#. type: Plain text
#: user-manual.txt:4854
msgid "render 6 dives per page:"
msgstr ""

#. type: delimited block .
#: user-manual.txt:4857
#, no-wrap
msgid "\t<body data-numberofdives = 6>\n"
msgstr ""

#. type: Plain text
#: user-manual.txt:4860
msgid "render as much dives as possible:"
msgstr ""

#. type: delimited block .
#: user-manual.txt:4863
#, no-wrap
msgid "\t<body data-numberofdives = 0>\n"
msgstr ""

#. type: Plain text
#: user-manual.txt:4866
msgid ""
"All CSS units should be in relative lengths only, to support printing on any "
"page size."
msgstr ""

#. type: Title ==
#: user-manual.txt:4869
#, no-wrap
msgid "APPENDIX F: Setting up video thumbnails."
msgstr ""

#. type: Title ===
#: user-manual.txt:4871
#, no-wrap
msgid ""
"Setting up the appropriate thumbnails for videos that are associated with "
"dives."
msgstr ""

#. type: Plain text
#: user-manual.txt:4877
msgid ""
"In handling video associated with dives, _Subsurface_ needs to create a "
"thumbnail for each video that can be shown either on the dive profile or in "
"the _Media_ tab. By default this is a nonspecific placeholder thumbnail.  To "
"see thumbnails that represent individual videos, _Subsurface_ uses an "
"external program calle _FFmpeg_.  To create thumbnails for videos, do two "
"things:"
msgstr ""

#. type: Plain text
#: user-manual.txt:4880
msgid ""
"Install _FFmpeg_ on the computer that runs _Subsurface_. The program can be "
"downloaded from the FFmpeg web site: "
"https://www.ffmpeg.org/download.html. Most Linux distributions ship with an "
"_ffmpeg_ package and therefore do not need an additional download."
msgstr ""

#. type: Plain text
#: user-manual.txt:4884
#, no-wrap
msgid ""
"** On Windows, put the _ffmpeg.exe_ file in the directory containing the "
"_Subsurface_ executable.\n"
"On Mac and Linux, make sure the _ffmpeg_ command is in the path. This should "
"be the case for\n"
"_FFmpeg_ installed from official packages.\n"
msgstr ""

#. type: Plain text
#: user-manual.txt:4887
msgid ""
"In the _General_ tab of the <<S_Preferences, _Preferences_>>, set the "
"preferences for generating video thumbnails. This is achieved by:"
msgstr ""

#. type: Plain text
#: user-manual.txt:4890
#, no-wrap
msgid ""
"** Checking the _Extract video thumbnails_ box. If _Subsurface_ fails to "
"load the _FFmpeg_ executable,\n"
"this option will be turned off. Re-enable it after successfully installing "
"_FFmpeg_.\n"
msgstr ""

#. type: Plain text
#: user-manual.txt:4892
#, no-wrap
msgid "** Specifying the path to the _FFmpeg_ executable.\n"
msgstr ""

#. type: Plain text
#: user-manual.txt:4898
#, no-wrap
msgid ""
"** Choose the position in the video where _Subsurface_\n"
"should try to extract the thumbnail. The left-most and right-most positions "
"of the _Extract at position_\n"
"slider signify the beginning and the end of the video, respectively. Note "
"that if _Subsurface_ cannot\n"
"determine the length of the video (this can be the case for AVI files), the "
"first frame\n"
"of the video will be used.\n"
msgstr ""

#. type: Plain text
#: user-manual.txt:4900
msgid ""
"This should complete the setup of video thumbnails and they should now "
"appear on the dive profile and in the _Media_ tab."
msgstr ""

#. type: Title ==
#: user-manual.txt:4901
#, no-wrap
msgid "APPENDIX G: FAQs."
msgstr ""

#. type: Title ===
#: user-manual.txt:4903
#, no-wrap
msgid "Subsurface appears to miscalculate gas consumption and SAC"
msgstr ""

#. type: Plain text
#: user-manual.txt:4907
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:4913
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:4919
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:4921
msgid "+consumption = (amount_of_air_at_beginning - amount_of_air_at_end)+"
msgstr ""

#. type: Plain text
#: user-manual.txt:4927
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:4929
msgid "+12.2*((220-100)/1.013)+"
msgstr ""

#. type: Plain text
#: user-manual.txt:4934
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:4940
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:4941
#, no-wrap
msgid ""
"Some dive profiles have time discrepancies with the recorded samples from my "
"dive computer..."
msgstr ""

#. type: Plain text
#: user-manual.txt:4945
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:4953
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:4954
#, no-wrap
msgid "Some dive profiles are missing from the download"
msgstr ""

#. type: Plain text
#: user-manual.txt:4968
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? 'Answer': Dive history is different than the dive profiles on the "
"log.  The history only keeps track of the total number of dives and total "
"amount of time spent below surface. The logs, on the other hand, store the "
"dive profile, but they have a limited amount of memory to do so. The exact "
"amount of dive profiles that can be stored on the device depends on sample "
"interval and duration of the dives. Once the memory is full the oldest dives "
"get overwritten with new dives. Thus we are only able to download the last "
"13, 30 or 199 dives."
msgstr ""

#. type: Plain text
#: user-manual.txt:4972
msgid ""
"If you have downloaded your dives to different dive logging software before "
"they were overwritten, there is a good chance that Subsurface can import "
"these. However, if the logs are only on your dive computer, they cannot be "
"salvaged after being overwritten by new dives."
msgstr ""