Mercurial > hg > xemacs-beta
diff lisp/mule/mule-category.el @ 5662:bed39edf91ba
Be better about word boundaries with JIT unicode characters, mule-category.el
lisp/ChangeLog addition:
2012-05-10 Aidan Kehoe <kehoea@parhasard.net>
* mule/mule-category.el (word-combining-categories):
Be better about default word boundaries when text contains
just-in-time-allocated Unicode code points. Document what we
should do instead once we have Unicode internally.
* mule/misc-lang.el: IPA characters are Latin.
| author | Aidan Kehoe <kehoea@parhasard.net> |
|---|---|
| date | Thu, 10 May 2012 13:53:06 +0100 |
| parents | ac37a5f7e5be |
| children |
line wrap: on
line diff
--- a/lisp/mule/mule-category.el Tue May 08 09:47:41 2012 +0100 +++ b/lisp/mule/mule-category.el Thu May 10 13:53:06 2012 +0100 @@ -252,6 +252,7 @@ (chinese-big5-1 ?t) (chinese-big5-2 ?t) (korean-ksc5601 ?h "Hangul (Korean) 2-byte character set") + (jit-ucs-charset-0 ?J "Just-in-time-allocated Unicode character") ) "List of predefined categories. Each element is a list of a charset, a designator, and maybe a doc string.") @@ -275,7 +276,18 @@ ;;; Setting word boundary. (setq word-combining-categories - '((?l . ?l))) + ;; XEmacs; we should change to defining scripts, as does GNU, once + ;; unicode-internal is the default, and placing word boundaries + ;; between different scripts, not different charsets, by default. + ;; Then we can remove the jit-ucs-charset-0 entry above and all the + ;; entries containing ?J in this list. + ;; + ;; These entries are a bit heuristic, working on the assumption that + ;; characters that will be just-in-time-allocated will not be East + ;; Asian in XEmacs, and there's also no mechanism to apply the ?J + ;; category to further newly-created JIT categories. + '((?l . ?l) (?J . ?l) (?l . ?J) (?J . ?y) (?y . ?J) (?J . ?b) (?b . ?J) + (?J . ?g) (?J . ?w) (?w . ?J))) (setq word-separating-categories ; (2-byte character sets) '((?A . ?K) ; Alpha numeric - Katakana