diff --git a/Documentation/user-manual.txt b/Documentation/user-manual.txt
index e30a4aea4..aedea9d20 100644
--- a/Documentation/user-manual.txt
+++ b/Documentation/user-manual.txt
@@ -3319,7 +3319,7 @@ image::images/Pref4_f23.jpg["FIGURE: Preferences Graph page",align="center"]
respect to inert gas loading and the deeper the ceilings are. Gradient
factors of 20/60 are considered conservative and values of 70/90 are considered
harsh.
- In addition decide whether to check the _GFLow at max depth_ box. If checked, GF_Low is used for the
+ In addition decide whether to check the _GFLow at max. depth_ box. If checked, GF_Low is used for the
deepest dive depth and linearly increased up to the GF_High value at the surface. If unchecked,
GF_Low is used between the deepest dive depth and the first deco stop, after which the
gradient factor linearly increases up to the GF_High value at the surface. For more information see:
@@ -4556,7 +4556,7 @@ according to which spreadsheet program is used.
Organize the diving data in the spreadsheet, so the first row
contains the names (or titles) of each column and the information for each dive is stored in a single row.
_Subsurface_ supports many data items (Dive number, Date,
-Time, Duration, Location, GPS, Max Depth, Mean Depth, Buddy, Notes, Weight and Tags).
+Time, Duration, Location, GPS, Max. Depth, Mean Depth, Buddy, Notes, Weight and Tags).
Organize dive data following a few simple rules:
1. Date: use one of the following formats: yyyy-mm-dd, dd.mm.yyyy, mm/dd/yyyy
diff --git a/Documentation/user-manual_fr.txt b/Documentation/user-manual_fr.txt
index 12d5bba5c..c4805b6ae 100644
--- a/Documentation/user-manual_fr.txt
+++ b/Documentation/user-manual_fr.txt
@@ -3498,7 +3498,7 @@ image::images/Pref4_f23.jpg["FIGURE: Preferences Graph page", align="center"]
respect to inert gas loading and the deeper the ceilings are. Gradient
factors of 20/60 are considered conservative and values of 70/90 are considered
harsh.
- In addition decide whether to check the _GFLow at max depth_ box. If checked, GF_Low is used for the
+ In addition decide whether to check the _GFLow at max. depth_ box. If checked, GF_Low is used for the
deepest dive depth and linearly increased up to the GF_High value at the surface. If unchecked,
GF_Low is used between the deepest dive depth and the first deco stop, after which the
gradient factor linearly increases up to the GF_High value at the surface. For more information see:
diff --git a/core/deco.c b/core/deco.c
index 8247800da..d2678a922 100644
--- a/core/deco.c
+++ b/core/deco.c
@@ -43,7 +43,7 @@ struct buehlmann_config {
double gf_high; //! gradient factor high (at surface).
double gf_low; //! gradient factor low (at bottom/start of deco calculation).
double gf_low_position_min; //! gf_low_position below surface_min_shallow.
- bool gf_low_at_maxdepth; //! if true, gf_low applies at max depth instead of at deepest ceiling.
+ bool gf_low_at_maxdepth; //! if true, gf_low applies at max. depth instead of at deepest ceiling.
};
struct buehlmann_config buehlmann_config = {
diff --git a/core/dive.c b/core/dive.c
index d7b423ad8..79e89d559 100644
--- a/core/dive.c
+++ b/core/dive.c
@@ -663,7 +663,7 @@ void finish_sample(struct divecomputer *dc)
* new ones.
*
* Why? Because a dive computer may well actually track the
- * max depth and mean depth at finer granularity than the
+ * max. depth and mean depth at finer granularity than the
* samples it stores. So it's possible that the max and mean
* have been reported more correctly originally.
*
@@ -2440,7 +2440,7 @@ static int find_sample_offset(struct divecomputer *a, struct divecomputer *b)
* difference?
*
* So for example, we'd expect different dive computers to give different
- * max depth readings. You might have them on different arms, and they
+ * max. depth readings. You might have them on different arms, and they
* have different pressure sensors and possibly different ideas about
* water salinity etc.
*
diff --git a/core/units.h b/core/units.h
index 029bb64fa..c751328f1 100644
--- a/core/units.h
+++ b/core/units.h
@@ -53,7 +53,7 @@ extern "C" {
* Also strive to use units that can not possibly be mistaken for a
* valid value in a "normal" system without conversion. If the max
* depth of a dive is '20000', you probably didn't convert from mm on
- * output, or if the max depth gets reported as "0.2ft" it was either
+ * output, or if the max. depth gets reported as "0.2ft" it was either
* a really boring dive, or there was some missing input conversion,
* and a 60-ft dive got recorded as 60mm.
*
diff --git a/desktop-widgets/configuredivecomputerdialog.ui b/desktop-widgets/configuredivecomputerdialog.ui
index 4a4c3521f..3b78387df 100644
--- a/desktop-widgets/configuredivecomputerdialog.ui
+++ b/desktop-widgets/configuredivecomputerdialog.ui
@@ -1693,7 +1693,7 @@
{{ dive.depth }}
diff --git a/printing_templates/One Dive.html b/printing_templates/One Dive.html index 8cfc12799..7f7945396 100644 --- a/printing_templates/One Dive.html +++ b/printing_templates/One Dive.html @@ -142,7 +142,7 @@{{ dive.depth }}
diff --git a/printing_templates/Six Dives.html b/printing_templates/Six Dives.html index 1d4bb5b56..0fe48a628 100644 --- a/printing_templates/Six Dives.html +++ b/printing_templates/Six Dives.html @@ -136,7 +136,7 @@Max depth: {{ dive.depth }}
+Max. depth: {{ dive.depth }}
{{ dive.depth }}
diff --git a/printing_templates/statistics/Default.html b/printing_templates/statistics/Default.html index 4ec02766a..28991c09a 100644 --- a/printing_templates/statistics/Default.html +++ b/printing_templates/statistics/Default.html @@ -59,17 +59,17 @@