# HG changeset patch
# User František Kučera <franta-hg@frantovo.cz>
# Date 1569407928 -7200
# Node ID db3eb602fa6082967a1e69b2bf312fa0f30ed237
# Parent  b4f38381c89fd4f0e6d0703f16c3ec0acb23a202
Internationalization and localization

diff -r b4f38381c89f -r db3eb602fa60 text/ssm.en.xml
--- a/text/ssm.en.xml	Wed Sep 25 00:01:56 2019 +0200
+++ b/text/ssm.en.xml	Wed Sep 25 12:38:48 2019 +0200
@@ -388,52 +388,59 @@
 	</chapter>
 	
 	<chapter>
-		<name>Localized/internationalized</name>
+		<name>Internationalization and localization</name>
 		<id>fa655b7c-f22d-4b98-ab7b-c0d0f608aad8</id>
 		<item>
+			<id>e56aad13-f68e-47ea-8b88-65fee6b5331a</id>
+			<text>Any software with nontrivial user interface must be internationalized</text>
+			<text>which means that it allows localization (translation of the UI to national languages and other customization to national conventions).</text>
+			<note>see https://en.wikipedia.org/wiki/Internationalization_and_localization</note>
+		</item>
+		<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>It should be possible to localize the user interface independently from the original author by creating an additionally installable language pack.</text>
 		</item>
 		<item>
 			<id>c3827486-6bf5-45c0-9a6d-61ad659d8ba1</id>
-			<text>GNU Gettext or other standard framework (like Java resource bundles) should be used</text>
+			<text>GNU Gettext or other standard framework (like Java resource bundles) should be used.</text>
 		</item>
 		<item>
 			<id>a57f4fc8-1f64-46e2-a91d-3a598c37f2e9</id>
-			<text>error messages should have assigned unique error codes, so it is possible to find relevant information regardless current locale</text>
+			<text>Error messages should have assigned unique error codes, so it is possible to find relevant information regardless the current locale.</text>
 		</item>
 		<!-- GEC is recommended for such unique error identifiers -->
 		<item>
 			<id>eba92867-5c1b-45b6-943a-a3fa6ea67e38</id>
-			<text>data formats and protocols must be language/locale independent</text>
+			<text>Data formats and protocols must be language/locale independent.</text>
 			<item>
 				<id>fee73fee-4940-47ac-84b6-15646f5f61c7</id>
 				<text>e.g. use decimal point instead of comma and no thousand separators for numbers, use standardized date formats</text>
 			</item>
 			<item>
 				<id>f1a00487-ed89-4443-99b5-63ab4c635690</id>
-				<text>in general: everything that is expected to be machine-readable or machine-generated must be independent from current locale</text>
+				<text>in general: everything that is expected to be machine-readable or machine-generated must be independent from the current locale</text>
 			</item>
 		</item>
 		<item>
 			<id>e6603e06-0b2c-439e-82ce-45f9744b2ef8</id>
-			<text>character encoding:</text>
+			<text>Character encoding:</text>
 			<item>
 				<id>abd42a7f-bd4b-4034-98ee-85a33094b5c1</id>
-				<text>always be aware of it, do not just blindly use current platform's default (because the other side might run on different platform with different default)</text>
+				<text>The software should always be aware of it and do not just blindly use current platform's default.</text>
+				<note>The other side might run on different platform with different default. Or a file might be opened later on different platform.</note>
 			</item>
 			<item>
 				<id>abd48eae-d287-4729-80ee-52dd018b0ba7</id>
-				<text>if given software/format/protocol has some default encoding, it must be clearly defined in its specification and this default should not be changed without changing the major version number</text>
+				<text>If given software/format/protocol has some default encoding, it must be clearly defined in its specification and this default must not be changed without changing the major version number.</text>
 			</item>
 			<item>
 				<id>c9f4d9f4-f959-48ad-bc68-6720dd4596e3</id>
-				<text>if there is no default, the encoding must be specified in the metadata attached (e.g. protocol headers, extended attributes on filesystem) to the actual data or at least at the begining of the data (like declaration in XML format)</text>
+				<text>If there is no default, the encoding must be specified in the metadata attached (e.g. protocol headers, extended attributes on filesystem) to the actual data or at least at the begining of the data (like declaration in XML format).</text>
 			</item>
 		</item>
 		<item>
 			<id>ce45c382-6ec5-41e8-869a-a0e758621b13</id>
-			<text>the metric system should be used as default</text>
+			<text>The metric system should be used as default.</text>
 		</item>
 	</chapter>