Re: Problem of auto-fill-mode for wide character

[Kenichi Handa]

In article <address@hidden>, "Herbert Euler" <address@hidden> writes:
[...]
>> I've just registered these apparent characters:
>>    U+3041..U+30FF, U+3400..U+4DB5, U+4e00..U+9fbb, U+F900..U+FAFF,
>>    U+FF00..U+FF9F, U+20000..U+2FFFF
>> So, now auto-fill should work for most Han characters.
>> 
>> But, there are many more questionable characters, for instance:
>>    U+3000..U+303F, U+3200..U+33FF, ...

> In my opinion, this solution is not an applicable one. Trying to register
> most characters in Chinese, Japanese and Korean as auto-fill-chars would
> waste lots of memory, and perhaps some characters would be forgot
> to be registered. For example, in Japanese, Hiragana and Katakana
> probably work, but not for most Kanji. Besides, the policy for filling
> punctuations in English and in Chinese is different: usually, if a 
> punctuation
> appears to be the last character of a line but exceeds the fill-column,
> it will be extended to the next line with the word it follows in English,
> but left there (and following characters will be moved to the next
> line) in Chinese. I don't know whether this is supported by registering
> auto-fill-chars.

At first, a char-table doesn't consume that much space if
you register characters of continuous codes.  For instance,
registering all Han characters is not a problem.

Next, it seems that you misunderstand the role of
auto-fill-chars.  It's a table to register characters that
triggers the auto-fill-function.  How auto-fill-function
fills the line(s) is a different thing.

And, although it's difficult to explain how lines are filled
(it's encoded in functions), at least Emacs considers
special treatment of punctuations (e.g. opening/closing
parentheses at the end/beginning of line) for Chinese and
Japanese.  You'll get a hint if you read
lisp/international/kinsoku.el.

---
Kenichi Handa
address@hidden