New to the community? Start here

latin or utf

Greets:

Can someone care to check to see if your blogs are being created with a utf8 charset when you use the multidb plugin? I’m still getting latin.

thanks,

-drmike

Wed, 12 Sep 2007 19:02:42
  • Luke
    • The Crimson Coder

    Hmmm, is it just on the initial blog creation, or across all blogs?

    I thought that had been fixed?

    Does it work with a standard DB install, without the multiple?

    Oh, what version of MySQL are you using? If I remember correctly, MySQL had an issue with character sets on one of the 4.0/4.1 versions.

    I will note that with 5.0.45, I haven’t noticed any general problems with character sets. Granted that’s with a custom application, but the basic procedures are similar.

    Overall, I prefer UTF-8. Just for the record. Although latin-1, or whatever it comes out as (sweedish latin 1 ci or some crap) doesn’t necessarily “kill” the deal, but can sometimes produce “funky” results for overseas visitors on non-english machines.

  • drmike
    • DEV MAN’s Mascot

    Hmmm, is it just on the initial blog creation, or across all blogs?

    Intial wpmu install is still latin. I opened up a trac ticket way back when on it and it;s still not resolved. I’m currently seeing it with the multidb plugin from here on our testbed and we’re getting latin on the blogs. On the other hosted mu installs, they’re all running the multidb code that Andrew emailed me why back when and those are fine.

    MySQL is version 4.1.22. Strange thing is though is when we first did this test install (which is when I asked about the latin on blog #1 during setup), the utf was used.

    I’ll throw in some echos and test it again. What should that portion of the MySQL code look like for 4.1.22 to declair the correct charset?

  • Luke
    • The Crimson Coder

    I have to edit the main database tables from initial install, but other than that everything has been fine. That’s been a known issue for a while though.

    I will note that I haven’t worked with 1.2.5 yet, and not much with 1.2.4.

    In theory, it is possible that instead of fixing the original complaint that the initial install wasn’t following the UTF-8 collation, that instead the part which had been working (individual blogs) was subsequently broken.

  • drmike
    • DEV MAN’s Mascot

    Must be 1.2.5 then. Actually must be something recent as we keep up out of trac for the most part.

    I noted that the poster, while saying that they fixed the issue, didn’t mention what they did to solve it.

    *sigh*

    On today’s todo list.