>>>> "Hrvoje" == Hrvoje Niksic
<hniksic(a)iskon.hr> writes:
"Stephen J. Turnbull" <turnbull(a)sk.tsukuba.ac.jp> writes:
> Speed is no issue here, man pages just can't get that big.
Hrvoje> Speed is definitely an issue with large English man pages.
Hrvoje> First, nroff takes a while to process them, and Emacs
Hrvoje> takes time to clean them. This is less dire on newer
Hrvoje> machines, but man pages really do get that big (try `man
Hrvoje> zshall' on a slower computer.)
OK, we don't want to do full-buffer regexp substitutions often, and
probably man.el does a lot of them.
Yoshiki> I'm reluctant to do the same thing for Chinese and Korean
Yoshiki> characters as I don't know how they localize man pages.
> ...why not give these other guys a chance of fixing the same
> problem _without_ needing to read the code? With the
> defcustom, _they_ can decide for themselves even if they don't
> grok elisp.
Hrvoje> Ideally, XEmacs should just do the right thing, either by
Hrvoje> hardcoding the stuff or by guessing it. We should
Hrvoje> generally be careful about introducing new user-options.
We don't have the choice of "just working" here. We don't have
Chinese or Koreans to ask at the moment, and we don't know whether
there might be other languages that make the bogus width distinction
that Japanese does.
The defcustom (1) gives Japanese users who know that they'll be
looking mostly at non-Japanese pages the chance to defeat what you say
is an expensive operation, (2) allows non-Japanese whose situations we
don't know yet to make the appropriate choice for themselves
(including the fact that custom is self-documenting, and so they might
actually find it while looking in custom for some option to fix bad
behavior), and (3) documents what we did for the future day when the
*roff folks remove the bogus width distinction.
Unfortunately, I18N is going to mean dealing with bad choices like
this one that have become standard practice in some locales, which we
can't possibly know ahead of time precisely because they're so bogus.
One possibility would be to make a "compatibility" group where we
could put user options (like this one) that we would like to guess
correctly, but can't be sure of doing so.
--
University of Tsukuba Tennodai 1-1-1 Tsukuba 305-8573 JAPAN
Institute of Policy and Planning Sciences Tel/fax: +81 (298) 53-5091
_________________ _________________ _________________ _________________
What are those straight lines for? "XEmacs rules."