# HG changeset patch
# User František Kučera <franta-hg@frantovo.cz>
# Date 1569105037 -7200
# Node ID 547569f6e675fda6ffdb0d46e7547537b24fba7c
# Parent  413a00a9cde748518eaa966026376532516ca986
add non-breakable spaces (nbsp)

diff -r 413a00a9cde7 -r 547569f6e675 text/ssm.en.xml
--- a/text/ssm.en.xml	Sat Sep 21 20:34:51 2019 +0200
+++ b/text/ssm.en.xml	Sun Sep 22 00:30:37 2019 +0200
@@ -26,7 +26,7 @@
 			<text>Every piece of Sane software is also Free software (as originally defined by Richard Stallman).</text>
 			<text>Which means that the user has freedom to</text>
 			<text>run the program for any purpose,</text>
-			<text>to study and change it (i.e. has access to the source code under a free software license)</text>
+			<text>to study and change it (i.e. has access to the source code under a free software license)</text>
 			<text>and to distribute modified or unmodified copies.</text>
 			<note>see https://www.gnu.org/philosophy/free-sw.html</note>
 			<note>see https://www.gnu.org/philosophy/who-does-that-server-really-serve.html</note>
@@ -59,7 +59,7 @@
 		</item>
 		<item>
 			<id>f39b90ae-0054-467e-a9e2-43379b7c2331</id>
-			<text>If the software is distributed with a hardware, the hardware must support instalation of independently built software without any restrictions or requirements (e.g. digital signature from the original author).</text>
+			<text>If the software is distributed with a hardware, the hardware must support instalation of independently built software without any restrictions or requirements (e.g. digital signature from the original author).</text>
 		</item>
 	</chapter>
 	
@@ -68,7 +68,7 @@
 		<id>e1c828c5-0a4f-4948-9943-db1ae16a42d5</id>
 		<item>
 			<id>c63ea2ac-c255-4f3e-a0e2-b49d1e145347</id>
-			<text>At least basic documentation must be released under a free license (GNU FDL is recommended).</text>
+			<text>At least basic documentation must be released under a free license (GNU FDL is recommended).</text>
 		</item>
 		<item>
 			<id>fd8e3bbd-d46a-40fe-85a6-b902336456d4</id>
@@ -84,11 +84,11 @@
 		</item>
 		<item>
 			<id>e6cd9c52-0e66-402c-930c-901fa66acd22</id>
-			<text>There must be a free documentation with description of building and running the software on a fresh operating system installation including description of all dependencies.</text>
+			<text>There must be a free documentation with description of building and running the software on a fresh operating system installation including description of all dependencies.</text>
 		</item>
 		<!--
 		<item><id></id><text>documentation should focus on all target groups: users, administrators, developers</text></item>
-		<item><id></id><text>there must be a big picture and software architercure described</text></item>
+		<item><id></id><text>there must be a big picture and software architercure described</text></item>
 		-->
 	</chapter>
 	
@@ -100,21 +100,21 @@
 			<text>Semantic versioning is required.</text>
 			<text>The version number consists of three numbers: major.minor.pach.</text>
 			<text>Major version is incremented if there is an incompatible change.</text>
-			<text>Minor version is incremented if a feature is added in a compatible way.</text>
-			<text>Patch version is incremented if a bug is fixed in a compatible way.</text>
+			<text>Minor version is incremented if a feature is added in a compatible way.</text>
+			<text>Patch version is incremented if a bug is fixed in a compatible way.</text>
 			<note>see http://semver.org/</note>
 			<note>If authors are unable to distinguish between compatible and incompatible changes, they must always increment the major version. However this approach is not recommeded</note>
 			<note>Propper Semantic versioning is especially important if the software is suposed to be used as dependency by others.</note>
-			<note>If there is a need of some marketing or cool versioning/codenames like Ultrasonic Umbrella or 2016, they should be used in addition to semantic versioning, not instead of it.</note>
+			<note>If there is a need of some marketing or cool versioning/codenames like Ultrasonic Umbrella or 2016, they should be used in addition to semantic versioning, not instead of it.</note>
 		</item>
 		<item>
 			<id>cf557a11-b307-4c2f-a7b5-5d2485d23258</id>
-			<text>Once publicly released, the package must not be changed anymore – if a change (even a small fix) is needed, new version number must be assigned.</text>
+			<text>Once publicly released, the package must not be changed anymore – if a change (even a small fix) is needed, new version number must be assigned.</text>
 		</item>
 		<item>
 			<id>dd013325-bf22-43d3-9579-0e272e2ac344</id>
 			<text>APIs, file formats and protocols might (and usually should) be semanticly versioned independently from the implementation.</text>
-			<note>In such case, there should be a table documenting which API/format/protocol version matches which implementation version.</note>
+			<note>In such case, there should be a table documenting which API/format/protocol version matches which implementation version.</note>
 		</item>
 		<item>
 			<id>dacb98cc-b558-4f0e-942d-e12004e45606</id>
@@ -149,7 +149,7 @@
 		</item>
 		<item>
 			<id>b2202690-8a6c-467f-a2b1-b154f470aa77</id>
-			<text>Already existing open protocol/format must not be modified or extended in a way which effectively creates a proprietary protocol/format.</text>
+			<text>Already existing open protocol/format must not be modified or extended in a way which effectively creates a proprietary protocol/format.</text>
 		</item>
 		<item>
 			<id>dd206223-9525-4229-be2b-84b07c2b8244</id>
@@ -162,7 +162,7 @@
 		</item>
 		<item>
 			<id>d61b3e31-bb9f-4333-87c8-9fb32f33a49d</id>
-			<text>Also configuration should have machine readable description and the user should be able to test it by executing a command (validator).</text>
+			<text>Also configuration should have machine readable description and the user should be able to test it by executing a command (validator).</text>
 		</item>
 	</chapter>
 	
@@ -206,11 +206,11 @@
 				<text>and/or third-party plugins/modules</text>
 				<item>
 					<id>de7270db-0410-4152-974f-4f0d74ff255b</id>
-					<text>it should be easy to create a third-party module and plug it in an existing system</text>
+					<text>it should be easy to create a third-party module and plug it in an existing system</text>
 				</item>
 				<item>
 					<id>fb4b07d1-6af7-44d9-8e6a-89ea63638652</id>
-					<text>dependencies needed to write an extension (i.e. header files, API classes/interfaces) should be as small as possible (do not require large codebase to write a mere plug-in); the required dependency should contain just interfaces (method/function signatures) and data structures but no implementation (executable code)</text>
+					<text>dependencies needed to write an extension (i.e. header files, API classes/interfaces) should be as small as possible (do not require large codebase to write a mere plug-in); the required dependency should contain just interfaces (method/function signatures) and data structures but no implementation (executable code)</text>
 				</item>
 			</item>
 		</item>
@@ -229,7 +229,7 @@
 		</item>
 		<item>
 			<id>a9f6725d-ddf1-41ee-96b4-15f3b851cb50</id>
-			<text>there should be also automated runtime/postinstall tests – in order to verify that software was installed properly, all required dependencies are met and basic function is guaranteed – the program should report problem during its start (as a warning if it is not fatal), instead of unexpected failures during operation</text>
+			<text>there should be also automated runtime/postinstall tests – in order to verify that software was installed properly, all required dependencies are met and basic function is guaranteed – the program should report problem during its start (as a warning if it is not fatal), instead of unexpected failures during operation</text>
 		</item>
 		<item>
 			<id>d610c04b-cc44-48c7-b069-f41b90bdef0f</id>
@@ -262,7 +262,7 @@
 		</item>
 		<item>
 			<id>fa92aa33-a69f-43b8-9051-9bfdcd3d293f</id>
-			<text>there should be a dictionary of used terms, so whole team and also users and customers will speak the same language</text>
+			<text>there should be a dictionary of used terms, so whole team and also users and customers will speak the same language</text>
 		</item>
 		<item>
 			<id>b9345a0e-c672-45d3-b93b-8d0fb4ece8b3</id>
@@ -308,7 +308,7 @@
 		</item>
 		<item>
 			<id>cbaf55be-8ffb-4109-9c83-083d1b3e793a</id>
-			<text>if dependency on bulky application package is inevitable, add a layer of abstraction – create a generic interface and connector and allow others to replace the bulky package with their own sane implementation</text>
+			<text>if dependency on bulky application package is inevitable, add a layer of abstraction – create a generic interface and connector and allow others to replace the bulky package with their own sane implementation</text>
 		</item>
 		<item>
 			<id>d7655989-a5e4-4123-9147-3782fc05a5ee</id>
@@ -418,7 +418,7 @@
 		<id>fa655b7c-f22d-4b98-ab7b-c0d0f608aad8</id>
 		<item>
 			<id>ad2f572b-497b-4523-b435-f9752fd1518a</id>
-			<text>is is strongly recommended that it should be possible to localize the user interface independently from the original author by writing a language pack</text>
+			<text>is is strongly recommended that it should be possible to localize the user interface independently from the original author by writing a language pack</text>
 		</item>
 		<item>
 			<id>c3827486-6bf5-45c0-9a6d-61ad659d8ba1</id>
@@ -524,7 +524,7 @@
 		</item>
 		<item>
 			<id>e746eb5b-8d8b-4ec8-9315-a311f35e156a</id>
-			<text>do not push users to register at a proprietary social networks resp. at particular company like Facebook – users without such account must not be discriminated – use open and decentralized networks/protocols instead</text>
+			<text>do not push users to register at a proprietary social networks resp. at particular company like Facebook – users without such account must not be discriminated – use open and decentralized networks/protocols instead</text>
 		</item>
 		<item>
 			<id>a1a3c037-37e3-4283-abab-e275f7d17442</id>
@@ -532,11 +532,11 @@
 		</item>
 		<item>
 			<id>ff537045-819e-4dec-a020-d2c9f2c3292b</id>
-			<text>there should be a second-level internet domain for the project or its team</text>
+			<text>there should be a second-level internet domain for the project or its team</text>
 		</item>
 		<item>
 			<id>b54d4978-974b-4743-bdba-7d4957bc9ba7</id>
-			<text>but do not buy an internet domain if you are not prepared to mainain it for decades – rather use third level domain under some reliable second level domain maintained by a credible group or person – think of that every expired domain helps spammers and scammers and hurts the users</text>
+			<text>but do not buy an internet domain if you are not prepared to mainain it for decades – rather use third level domain under some reliable second level domain maintained by a credible group or person – think of that every expired domain helps spammers and scammers and hurts the users</text>
 		</item>
 		<item>
 			<id>a1141312-5177-4d68-bb14-fce952d542c3</id>
@@ -584,7 +584,7 @@
 			</item>
 			<item>
 				<id>dfd6a77f-7c4a-430a-8199-8ea71ec7ee8c</id>
-				<text>to sign a contract (which includes accepting „Terms and conditions“) with any particular third party (e.g. source code hosting provider)</text>
+				<text>to sign a contract (which includes accepting „Terms and conditions“) with any particular third party (e.g. source code hosting provider)</text>
 			</item>
 			<item>
 				<id>af6a589f-d419-483f-b7b2-07b6e9da3924</id>
@@ -604,12 +604,12 @@
 			</item>
 			<item>
 				<id>d7a94eba-efd6-471f-9c32-6ee9d3b8ab29</id>
-				<text>to assign the copyright to the project and grant a free license for all patents relevant to the contribution</text>
+				<text>to assign the copyright to the project and grant a free license for all patents relevant to the contribution</text>
 			</item>
 		</item>
 		<item>
 			<id>e394c792-8294-4f15-a356-89cd0a7aa255</id>
-			<text>the project should record all accepted contributions and maintain a public list of all authors/contributors</text>
+			<text>the project should record all accepted contributions and maintain a public list of all authors/contributors</text>
 		</item>
 		<item>
 			<id>b5a128a2-31d9-49df-890c-59a770f7afa9</id>