message catalogs: fix comment lines, also remove linux hack in merge.c

[oweals/cde.git] / cde / programs / localized / sv_SE.ISO8859-1 / msg / fmt_tbl.msg

diff --git a/cde/programs/localized/sv_SE.ISO8859-1/msg/fmt_tbl.msg b/cde/programs/localized/sv_SE.ISO8859-1/msg/fmt_tbl.msg
index 9682cc0b736a3954820421cf025a0dc884ffac9a..dcd045757b16e5f55947cb095953c53bf5227e0c 100644 (file)
--- a/cde/programs/localized/sv_SE.ISO8859-1/msg/fmt_tbl.msg
+++ b/cde/programs/localized/sv_SE.ISO8859-1/msg/fmt_tbl.msg
@@ -1,6 +1,6 @@
 $ $XConsortium: fmt_tbl.msg /main/3 1995/11/08 13:36:53 rswiston $
 $set 1
-$
+$ 
 $ This file is to specify special formatting characteristics of a
 $ language.  It defines which characters of the language can not end a
 $ line of text, begin a line of text or whether to replace internal
@@ -11,27 +11,27 @@ $ sets.  For single byte character sets (I.E.  English, German, French,
 $ etc.), the system has a built in default list of characters that can
 $ not begin and end a line.  For single byte languages, the system will
 $ also always replace newlines with spaces.
-$
+$ 
 $ This table is for <???>
-$
+$ 
 $ message #1 indicates the list of 2byte punctuation, special characters
 $ and double consonants that cannot start a line.
-$
+$ 
 1 \81<place list here>
 
-$
+$ 
 $ message #2 indicates the list of 2byte punctuation, special characters
 $ and double consonants that cannot end a line.
-$
+$ 
 2 \81<place list here>
 
-$
+$ 
 $ message #3 indicates whether the language wants all end-of-lines in
 $ text to be changed into spaces.  I.E.  in english if you had
-$
+$ 
 $          'the quick brown fox'
 $          'jumps over the lazy dog'
-$
+$ 
 $ would be output as 'the quick brown fox jumps....'.  If this was
 $ translated into Japanese but leaving the break where it appeared in the
 $ sentence, the newline between 'fox' and 'jumps' would be compressed out
@@ -39,7 +39,7 @@ $ and no space would be put between the two words.  But if 'fox' was in
 $ Japanese and 'jump' was in english, the newline would be turned into a
 $ space. The same (newline -> space) would occur if 'fox' was in english
 $ and 'jumps' was in Japanese.
-$
+$ 
 $ Therefore, the values for message #3 should be
 $        1   - means that newlines are always turned into spaces.
 $        0   - means that newlines are turned into space only if they
@@ -47,5 +47,5 @@ $              occur between a multibyte character and a single byte
 $              character.
 $ Example:
 $     For Japanese, the 'value' of message #3 would be '0'
-$
+$ 
 3 1