>>>> "Ben" == Ben Wing <ben(a)666.com>
writes:
Ben> do we dump trex? what the hell does it do, anyway?
Move it out of the mule-base package, I should think. It looks to me
like it does the same thing that our C code does: produce an array of
bytecodes for the compiled regular expression VM. Or maybe it
generates a finite automaton in LISP. That would be cool. I'll
translate the comments some day.
Ben> or have a global var. just for these commands?
Ben> i meant, a user-settable global variable that controls the
Ben> operation only of query-replace-regexp and other user-level
Ben> commands.
Ah, I hadn't started thinking about that. Yeah, that would work,
since real code only ever sees compiled regexps. We can add bells and
whistles like 'ask-about-re-syntax, too.
> Japanese has the analogous case, of course. You simply set the
> precedence to { nice font for English, nice font for Japanese
> }, and since the repertoire for the English font doesn't cover
> Japanese, you win. I think this will handle the majority of
> such issues.
Ben> but japanese and chinese fonts cover the same space.
Of course, but you can't win that unless you know whether the author
wants the *extent* to be interpreted as Chinese or as Japanese. It's
not a per-character thing, it's a text property.
--
School of Systems and Information Engineering
http://turnbull.sk.tsukuba.ac.jp
University of Tsukuba Tennodai 1-1-1 Tsukuba 305-8573 JAPAN
Ask not how you can "do" free software business;
ask what your business can "do for" free software.