1 $ $XConsortium: fmt_tbl.msg /main/3 1995/11/08 11:56:42 rswiston $
6 $ This file is to specify special formatting characteristics of a
7 $ language. It defines which characters of the language can not end a
8 $ line of text, begin a line of text or whether to replace internal
9 $ newlines with spaces.
10 $ This file is ONLY necessary for languages with MULTIBYTE character
11 $ sets. For single byte character sets (I.E. English, German, French,
12 $ etc.), the system has a built in default list of characters that can
13 $ not begin and end a line. For single byte languages, the system will
14 $ also always replace newlines with spaces.
16 $ This table is for <???>
18 $ message #1 indicates the list of 2byte punctuation, special characters
19 $ and double consonants that cannot start a line.
22 1 "
\81<place list here>"
24 $ message #2 indicates the list of 2byte punctuation, special characters
25 $ and double consonants that cannot end a line.
28 2 "
\81<place list here>"
30 $ message #3 indicates whether the language wants all end-of-lines in
31 $ text to be changed into spaces. I.E. in english if you had
33 $ 'the quick brown fox'
34 $ 'jumps over the lazy dog'
36 $ would be output as 'the quick brown fox jumps....'. If this was
37 $ translated into Japanese but leaving the break where it appeared in the
38 $ sentence, the newline between 'fox' and 'jumps' would be compressed out
39 $ and no space would be put between the two words. But if 'fox' was in
40 $ Japanese and 'jump' was in english, the newline would be turned into a
41 $ space. The same (newline -> space) would occur if 'fox' was in english
42 $ and 'jumps' was in Japanese.
44 $ Therefore, the values for message #3 should be
45 $ 1 - means that newlines are always turned into spaces.
46 $ 0 - means that newlines are turned into space only if they
47 $ occur between a multibyte character and a single byte
50 $ For Japanese, the 'value' of message #3 would be '0'