In article [EMAIL PROTECTED], Zhang Wei [EMAIL PROTECTED] writes:
The `kinsoku' processing works great now, but `nospace-between-words'
still doesn't work for:
(set-language-environment UTF-8) and,
(set-language-environment Chinese-GB18030)
Should we do the same thing to the
Kenichi Handa [EMAIL PROTECTED] writes:
That makes too many unnecessary calls of `kinsoku'. I've
just installed a fix of the different way. Could you please
try with the latest code?
The `kinsoku' processing works great now, but `nospace-between-words'
still doesn't work for:
In article [EMAIL PROTECTED], Zhang Wei [EMAIL PROTECTED] writes:
Zhang Wei [EMAIL PROTECTED] writes:
`kinsoku processing' and `nospace-between-words' don't work with
auto-fill-mode.
It don't work with UTF-8 and Chinese-GBK language environment, but
it work with Chinese-GB language
Zhang Wei [EMAIL PROTECTED] writes:
`kinsoku processing' and `nospace-between-words' don't work with
auto-fill-mode.
It don't work with UTF-8 and Chinese-GBK language environment, but
it work with Chinese-GB language envrionment, strange behavior.
Zhang Wei [EMAIL PROTECTED] writes:
`kinsoku processing' and `nospace-between-words' don't work with
auto-fill-mode.
Would this patch be useful?
? patch
? admin/unidata/unidata.txt
Index: lisp/international/characters.el
===
RCS
