# HG changeset patch
# User František Kučera <franta-hg@frantovo.cz>
# Date 1376690304 -7200
# Node ID 1713d991691dd17711732ee8fbba6f8d4b343af1
# Parent  00278d4b6dc7d4a3e1f9226d31de9538d5b43d14
data: MMSC

diff -r 00278d4b6dc7 -r 1713d991691d data/dictionary.xml
--- a/data/dictionary.xml	Fri Aug 16 23:15:27 2013 +0200
+++ b/data/dictionary.xml	Fri Aug 16 23:58:24 2013 +0200
@@ -1076,8 +1076,19 @@
 		<tag>messaging</tag>
 	</concept>
 	<concept>
-		<term abbreviation="MMSC" completeForm="MMS service center" language="en"/>
-		<explanation language="en"><text></text></explanation>
+		<term abbreviation="MMSC" completeForm="Multimedia Messaging Service Centre" language="en"/>
+		<term abbreviation="MMSC" completeForm="MMS Service Centre" language="en"/>
+		<term abbreviation="" completeForm="MMS store and forward server" language="en"/>
+		<explanation language="en">
+			<text>
+				a kind of SC dedicated to processing multimedia messages;
+				the messaging is more comlex process than in case of SMS:
+					MO MMS message is received (in similar format to MIME e-mail) by the MMSC and stored,
+					then SC determines if the recipient is capable to receive MMS,
+					if yes, the message is put at a server with HTTP interface and the recipient gets special SMS containing the URL and downloads it over WAP,
+					if recipient is not capable he gets plain text SMS with URL and have to use computer and www browser
+			</text>
+		</explanation>
 		<tag>messaging</tag>
 	</concept>
 	<concept>