Mercurial > hg > xemacs-beta

comparison src/syntax.c @ 2297:13a418960a88

Find changesets by keywords (author, files, the commit message), revision number or hash, or revset expression.
[xemacs-hg @ 2004-09-22 02:05:42 by stephent] various doc patches <87isa7awrh.fsf@tleepslib.sk.tsukuba.ac.jp>
author stephent
date Wed, 22 Sep 2004 02:06:52 +0000
parents 04bc9d2f42c7
children 8c96bdabcaf9
comparison
equal deleted inserted replaced
2296:a58ea4d0d0cd 2297:13a418960a88
28 #include "lisp.h" 28 #include "lisp.h"
29 29
30 #include "buffer.h" 30 #include "buffer.h"
31 #include "syntax.h" 31 #include "syntax.h"
32 #include "extents.h" 32 #include "extents.h"
33
34 /* Here is a comment from Ken'ichi HANDA <handa@etl.go.jp>
35 explaining the purpose of the Sextword syntax category:
36
37 Japanese words are not separated by spaces, which makes finding word
38 boundaries very difficult. Theoretically it's impossible without
39 using natural language processing techniques. But, by defining
40 pseudo-words as below (much simplified for letting you understand it
41 easily) for Japanese, we can have a convenient forward-word function
42 for Japanese.
43
44 A Japanese word is a sequence of characters that consists of
45 zero or more Kanji characters followed by zero or more
46 Hiragana characters.
47
48 Then, the problem is that now we can't say that a sequence of
49 word-constituents makes up a WORD. For instance, both Hiragana "A"
50 and Kanji "KAN" are word-constituents but the sequence of these two
51 letters can't be a single word.
52
53 So, we introduced Sextword for Japanese letters. A character of
54 Sextword is a word-constituent but a word boundary may exist between
55 two such characters. */
56
57 /* Mule 2.4 doesn't seem to have Sextword - I'm removing it -- mrb */
58 /* Recovered by tomo */
59 33
60 #define ST_COMMENT_STYLE 0x101 34 #define ST_COMMENT_STYLE 0x101
61 #define ST_STRING_STYLE 0x102 35 #define ST_STRING_STYLE 0x102
62 36
63 Lisp_Object Qsyntax_table; 37 Lisp_Object Qsyntax_table;