Re: Open bugs in 21.5
"Ben Wing" <ben(a)666.com> writes:
>1)
>XEmacs is currently broken in respect to detection of character set
>for European users. This started with a patch by Katsumi Yamaoka which
>fixes some issues for Japanese users, I applied the reverse patch from
>http://list-archive.xemacs.org/xemacs-beta/200209/msg00454.html now
>everything is fine again, there should be a general solution which
>satisfies both groups of users. This bug is very urgent IMO since it
>really makes XEmacs almost unusable.
now that everything is ok, how urgent is it, really? ie how urgent is the
problem for japanese users?
The patch is not in CVS, I applied it to my personal copy. As far as I
understood Katsumi, the patch fixes some issues for Japanese users, but
there are still many problems, he said something like "It's okay to
revert the patch since some more problems don't count"
>
>2)
>It is impossible to display characters which are part of Unicode, but of
>no other coding-system known to XEmacs. Instead of the character a bold
>= is drawn.
we need separate unicode coding systems.
Yepp.
>7)
>XEmacs crashes _very_ often if you choose Edit->Find from the menu
>(about one out of three times for me). Backtrace is attached.
interesting ... it's crashing because of code i put in to try to catch an
elusive bug. i can reproduce this so i'll look at it.
Thanks.
of all these bugs, which are most important?
For me (I guess this is quite different for others):
Number one the "XEmacs guesses wrong character set" problem described
in 1)
Number two the inability to display Unicode-exclusive characters (I'd
like to write mathematical formulas in Unicode in our University
newsgroup)
Number three the problem that I can't input easily a single ^ under MS
Windows.
Number four the inability to say (prefer-coding-system 'utf-8)
MFG Frank
--
One Ring to rule them all, One Ring to find them,
One Ring to bring them all and in the darkness bind them
In the Land of Mordor where the Shadows lie.