1 $ $XConsortium: fmt_tbl.msg /main/4 1996/10/16 03:18:48 cde-hit $
4 $ This file is to specify special formatting characteristics of a
5 $ language. It defines which characters of the language can not end a
6 $ line of text, begin a line of text or whether to replace internal
7 $ newlines with spaces.
9 $ This file is ONLY necessary for languages with MULTIBYTE character
10 $ sets. For single byte character sets (I.E. English, German, French,
11 $ etc.), the system has a built in default list of characters that can
12 $ not begin and end a line. For single byte languages, the system will
13 $ also always replace newlines with spaces.
15 $ This table is for <???>
17 $ message #1 indicates the list of 2byte punctuation, special characters
18 $ and double consonants that cannot start a line.
125 $ message #2 indicates the list of 2byte punctuation, special characters
126 $ and double consonants that cannot end a line.
198 $ message #3 indicates whether the language wants all end-of-lines in
199 $ text to be changed into spaces. I.E. in english if you had
201 $ 'the quick brown fox'
202 $ 'jumps over the lazy dog'
204 $ would be output as 'the quick brown fox jumps....'. If this was
205 $ translated into Japanese but leaving the break where it appeared in the
206 $ sentence, the newline between 'fox' and 'jumps' would be compressed out
207 $ and no space would be put between the two words. But if 'fox' was in
208 $ Japanese and 'jump' was in english, the newline would be turned into a
209 $ space. The same (newline -> space) would occur if 'fox' was in english
210 $ and 'jumps' was in Japanese.
212 $ Therefore, the values for message #3 should be
213 $ 1 - means that newlines are always turned into spaces.
214 $ 0 - means that newlines are turned into space only if they
215 $ occur between a multibyte character and a single byte
218 $ For Japanese, the 'value' of message #3 would be '0'