Training, Open Source computer languages
PerlPHPPythonMySQLApache / TomcatTclRubyJavaC and C++LinuxCSS 
Search for:
Home Accessibility Courses Diary The Mouth Forum Resources Site Map About Us Contact
 
For 2023 (and 2024 ...) - we are now fully retired from IT training.
We have made many, many friends over 25 years of teaching about Python, Tcl, Perl, PHP, Lua, Java, C and C++ - and MySQL, Linux and Solaris/SunOS too. Our training notes are now very much out of date, but due to upward compatability most of our examples remain operational and even relevant ad you are welcome to make us if them "as seen" and at your own risk.

Lisa and I (Graham) now live in what was our training centre in Melksham - happy to meet with former delegates here - but do check ahead before coming round. We are far from inactive - rather, enjoying the times that we are retired but still healthy enough in mind and body to be active!

I am also active in many other area and still look after a lot of web sites - you can find an index ((here))
Mysql Full-Text Search

Posted by haylwk (haylwk), 28 January 2004
Can anyone help to fix the following problem :

I am using Mysql version 4.017 & odbc 3.51.06 under window 2000 environment, the client is window98.
It seems not work when I was using Full-Text Search function with Chinese Character. How can I do ? Thanks!

Posted by admin (Graham Ellis), 28 January 2004
I have to admit I'm not suprised ... when you add the odbc layer on top of my SQL that's another level of obfurscation above using the client directly, and then you start getting involved with unicodes an the rest too ...

Welcome to the board;  I can give you a sanity check and tell you that, no, you're not going mad and have missed an answer that everyone knows.  In fact, I'm rather afraid that your question is rather too specific for most of us here.  Here's hoping that one of the other poster can come up with something, but please don't hold your breath

Posted by delta (delta), 7 April 2004
Try using MySQL v4.1. I believe v4.0 doesn't support Unicode.

I am also doing the same thing, exept with Japanese Kana and Kanji, using MySQL and PHP.

Also it depends on the encoding you are using. Full-text search depends on indexing words, right? It finds words by separating data using spaces and punctuation, but this is a problem in Asian scripts as these criteria for distinguishing words simply do not apply (like in Japanese, where spaces are not used.)

Back to the encoding. UTF-8 is a good choice, as it preserves the 'standard' spaces in the encoding (however this is not true for a full-width space used in Japanese).



This page is a thread posted to the opentalk forum at www.opentalk.org.uk and archived here for reference. To jump to the archive index please follow this link.

You can Add a comment or ranking to this page

© WELL HOUSE CONSULTANTS LTD., 2024: Well House Manor • 48 Spa Road • Melksham, Wiltshire • United Kingdom • SN12 7NY
PH: 01144 1225 708225 • FAX: 01144 1225 793803 • EMAIL: info@wellho.net • WEB: http://www.wellho.net • SKYPE: wellho