Weeehll, thet's whut ah git fer shootin' off at th' mouth. Anybody that really knows care to correct the confusion I've caused?
(See comments below:) Jim Philips wrote: > On Mon, 2002-03-11 at 23:39, Joel Rees wrote: > > Sort of off topic, but here goes: > > > > Jim Philips wrote: > > > > > I am trying to understand how to store both Latin and Cyrillc characters > > > in a database. I built in support for koi-8 and win1251, but I don't > > > seem to be getting real support for Cyrillic. Cyrillic characters are > > > stored as ASCII What sort of effect does setting or not setting the option "CHARACTER SET cp1251_koi8" have, per section 5.5.6 of the manual? Have you tried using blob fields instead of char or text fields? > > Uhmmm, unless there is some parsing and conversion going on along with the > > storing, "storing as ASCII" really doesn't mean anything. A 0x5c (decimal > > 92) is neither back slash nor the yen (JPY) mark. If you are reading text > > from an American source (but not EBCDIC), you think it is backslash, but if > > you are reading text from a Japanese (shift-JIS) source you think it is JPY. > > What you think of it when reading Cyrillic, I don't recall off-hand. > > > > > and are echoed back on the Web page that way. Could you pinpoint where the unwanted conversion is occuring and post that? In other words, would you compare the text before it gets stored with the text stored and the query result that you're feeding to the browser? > > At any rate, this is what the browser is doing, not what MySQL is doing. You > > have to explicitly tell the browser to interpret those bits as one thing or > > another. Most browsers won't let you display more than one character > > set/encoding at a time. > > > My browser, Mozilla, regularly does this. It does it on the following > page, for example: > > http://www.bbc.co.uk/ukrainian/index.shtml > > The page is mostly Ukrainian, but there are sections using Latin fonts > and they show up just fine too. A little investigation showed me that KOI-8 is, indeed, a set that only encodes the upper 128, so it should allow ASCII and Cyrillic to co-exist. I should've checked before I spoke. A little more investigation shows that the MySQL team is somewhat familiar with KOI-8. 8-0 > Using the same browser, I am trying to > load Web pages where the data is stored in my local MySQL database. In > this case, Cyrillic characters are not interpreted and instead I get > something like: > > * Би-би-си | Новости > > So, I am trying to understand where the interpretation to Cyrillic > characters fails. Again, have you tried comparing what you're feeding in with what is stored and what comes out? > It certainly isn't in my browser. Either the > application is using a print method that has problems with other > character sets or there is something wrong with the way I have set up > MySQL. As I said before, I did build it with support for koi-8 and > win1251. So, I am wondering if I missed something else I need to do to > enable support. Joel Rees Alps Giken Kansai Systems Develoment Suita, Osaka --------------------------------------------------------------------- Before posting, please check: http://www.mysql.com/manual.php (the manual) http://lists.mysql.com/ (the list archive) To request this thread, e-mail <[EMAIL PROTECTED]> To unsubscribe, e-mail <[EMAIL PROTECTED]> Trouble unsubscribing? Try: http://lists.mysql.com/php/unsubscribe.php
