when the patters write in chinese, can't be matched, and english works well.zmud works both well, but mushclient show perfectly!
The trigger not support chinese?or unicode?
Posted by Theart on Mon 03 Nov 2003 04:50 AM — 13 posts, 52,263 views.
I think the trigger matching does not support UTF-8. However MUSHclient itself does not really support Unicode, there are lengthy posts on this forum about why this is so.
is it possible to support it in next mushclient version?
No. Sorry. My earlier post explained that, far from being a simple change, it would be thousands and thousands of lines of code, and weeks if not months of work. Basically a rewrite.
Unicode would be primarily of interest to non-English speakers, and to put it into perspective, I recently asked for non-English speakers on this forum to respond to a survey.
Only two people responded, and of those two one was an American who was interested in the idea (and who speaks French) and the other was from Greece.
To be honest, it isn't cost-effective for me to spend months making changes to a program that might result in one or two $20 shareware registrations. To say nothing of the bugs that would creep in after major changes, and which would probably result in further months of work fixing them.
Unicode would be primarily of interest to non-English speakers, and to put it into perspective, I recently asked for non-English speakers on this forum to respond to a survey.
Only two people responded, and of those two one was an American who was interested in the idea (and who speaks French) and the other was from Greece.
To be honest, it isn't cost-effective for me to spend months making changes to a program that might result in one or two $20 shareware registrations. To say nothing of the bugs that would creep in after major changes, and which would probably result in further months of work fixing them.
thanks for your reply.
but, the input line now support uncicode. i think the output windows is same as the input windows?only make the output windows support unicode is not very hard.maybe that should make the trigger supoort unicode. this is my prefer
but, the input line now support uncicode. i think the output windows is same as the input windows?only make the output windows support unicode is not very hard.maybe that should make the trigger supoort unicode. this is my prefer
Hmm - strangely enough I got bogged down on making the input window support Unicode. The output window is easy enough, I think.
you can have a beta test on the output box!input box is works well in chinese,:-) when i input chinese cmommand it show it well in both input box and output box, but when select the word in output box, it become ....can't show well. i think it because the output box don't support unicode. it is easy to make output box support unicode, maybe trigger will works well also!!!
Can you make a screen capture of that? I would be interested to see. The Chinese text in the input and output window I mean.
ok, i send it to you mailbox, i don't know how to send picture here.
test how to pick a link
false 3 times. fanit
look the link yourself
http://final.our365.net/mud/bbs/show.asp?id=2882&bd=72
a forum for shenzhou mud.
false 3 times. fanit
look the link yourself
http://final.our365.net/mud/bbs/show.asp?id=2882&bd=72
a forum for shenzhou mud.
Actually this is not a big surprise. Even if you designed the output control your own way, if you used any form of MS form, textbox, etc. as a base, then it automatically enherits the ability to 'show' unicode. However, all the stuff you impliment in your own application needs to also be aware of it to use it properly.
Fascinating - works better than I expected. It must be using UTF-8 encoding because MUSHclient stores text internally as 8-bit characters.
There is an option with the newer version of the regular expression engine to have UTF-8 support, I have added the suggestion of implementing that as suggestion #502.
There is an option with the newer version of the regular expression engine to have UTF-8 support, I have added the suggestion of implementing that as suggestion #502.
ok, thank you! you done a great thing!
here is another client and opensource, maybe useful for you.it support chinese well!when select word in its output box it select the whole words not the "half" words as the mushclient done now.
http://ytin.sourceforge.net/index_e.html
here is another client and opensource, maybe useful for you.it support chinese well!when select word in its output box it select the whole words not the "half" words as the mushclient done now.
http://ytin.sourceforge.net/index_e.html