Hrvoje Niksic <hniksic(a)srce.hr> writes:
"Stephen J. Turnbull" <turnbull(a)sk.tsukuba.ac.jp>
writes:
> That's a bug, but deleting spaces (any ASCII space or tab
> characters) in Japanese is data corruption, pure and simple. Don't
> fix it by breaking Japanese.
The Japanese fixed it by breaking English. And French. And
Croatian. And...
We'll revert to the state of affairs when things worked for European
languages, and then we'll accept correct fixes for Japanese. Which is
how we should have dealt with it in the first place.
I don't have an xemacs built with mule, so I can't try it, but do you get
lines of (fill-column + 1) columns if you type a space at fill-column in
Japanese too?
If so, it seems like the current code is wrong for all languages -- what
about my previous suggestion that the right thing to do if you need to
preserve spaces is to have auto-fill actually go back and break at the
_previous_ legal fill boundary? Then the unbreakable text at the end of the
line and the space after it would go down to the beginning of the next line.
There could even be a variable like [auto-?]fill-preserve-spaces or
something like that that you could set in any language that would cause that
behavior. If it wasn't set, the old correct (Western language) behavior of
changing the space to a newline would apply.
People working in Japanese would just need to be sure to set that variable
(if there weren't some automatic way of turning it on while working in
Japanese buffers).
-----------------------------------------------------------------------
Dan Harkless | To prevent SPAM contamination, please
dan-xemacs(a)dilvish.speed.net | do not post this private email address
SpeedGate Communications, Inc. | to the USENET or WWW. Thank you.