1 $ $XConsortium: fmt_tbl.msg /main/1 1996/11/07 18:08:33 drk $
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.
20 1
\81<place list here>
23 $ message #2 indicates the list of 2byte punctuation, special characters
24 $ and double consonants that cannot end a line.
26 2
\81<place list here>
29 $ message #3 indicates whether the language wants all end-of-lines in
30 $ text to be changed into spaces. I.E. in english if you had
32 $ 'the quick brown fox'
33 $ 'jumps over the lazy dog'
35 $ would be output as 'the quick brown fox jumps....'. If this was
36 $ translated into Japanese but leaving the break where it appeared in the
37 $ sentence, the newline between 'fox' and 'jumps' would be compressed out
38 $ and no space would be put between the two words. But if 'fox' was in
39 $ Japanese and 'jump' was in english, the newline would be turned into a
40 $ space. The same (newline -> space) would occur if 'fox' was in english
41 $ and 'jumps' was in Japanese.
43 $ Therefore, the values for message #3 should be
44 $ 1 - means that newlines are always turned into spaces.
45 $ 0 - means that newlines are turned into space only if they
46 $ occur between a multibyte character and a single byte
49 $ For Japanese, the 'value' of message #3 would be '0'