PDA

View Full Version : having problems with charset, please help.



Yellow Slider
Wed 17th Dec '08, 6:50pm
I've used the Impex to convert 3.6.8 (who's DB is messed up) to 3.7.4
the 3.6.8 is working in http://forum.g.co.il (it's in UTF8 and working good)

after the convert, the whole forum got messed up
www.iatraf.co.il/g1/ (http://www.iatraf.co.il/g1/) as you can see it's all gibberish.

(when upgrading I have the same problem)

do you have a clue? I've done the things in here - http://www.vbulletin.com/forum/showthread.php?t=267649

with no help, I've a open support ticket but no one seems to figure it out.

Jerry, maybe you can have a look in my support ticket too?

thanks a lot.

Jerry
Wed 17th Dec '08, 7:04pm
Well the post by oktaysari is the best reference I have for ensuring char set comparability between the imports.

A vB -> vB import dosen't parse any of the content (regex or str_replace) so what is selected out on one side is inserted in on the other.

99% of the time it has to be the char set of the source table.

Yellow Slider
Thu 18th Dec '08, 5:11am
Well, this is my problem.

The DB in http://forum.g.co.il contains a lot of gibberish, all the hewbrew stuff in in gibberish, but it works just fine in the board it self, we can read and use Hebrew.

I've backed up and restore this DB into a new server of mine, and used the Impex to go from 3.6.8 db to a clean version of 3.7.4, the DB contains a lot of gibberish too, but in this case, the gibberish stuff is also presented on the board it self.

what can I do?
this is the 3.7.4 part
http://www.iatraf.co.il/g1

I had to use impex cause once a coder changed some thing on my DB so I'll have dynamic url's as you can see at http://forum.g.co.il (http://forum.g.co.il/) and when I've used a regular upgrade the dynamic urls part was still working on the new 3.7.4 board, and I don't want it any more.

Yellow Slider
Thu 18th Dec '08, 6:25am
Well, this is my problem.

The DB in http://forum.g.co.il contains a lot of gibberish, all the hewbrew stuff in in gibberish, but it works just fine in the board it self, we can read and use Hebrew.

I've backed up and restore this DB into a new server of mine, and used the Impex to go from 3.6.8 db to a clean version of 3.7.4, the DB contains a lot of gibberish too, but in this case, the gibberish stuff is also presented on the board it self.

what can I do?
this is the 3.7.4 part
http://www.iatraf.co.il/g1

I had to use impex cause once a coder changed some thing on my DB so I'll have dynamic url's as you can see at http://forum.g.co.il (http://forum.g.co.il/) and when I've used a regular upgrade the dynamic urls part was still working on the new 3.7.4 board, and I don't want it any more.

when I'm posting new messages in Hebrew I can read them and see them properly http://www.iatraf.co.il/g1/showthread.php?goto=newpost&t=5184

but all the other content is in gibberish.

Jerry
Thu 18th Dec '08, 12:30pm
Have you set up vBulletin to display utf-8 as well as setting up both databases ?

Yellow Slider
Thu 18th Dec '08, 3:09pm
off course I had, I thought about using the binary files on the DB but I don't know how to use them.

I don't want to use UTF8 any more, I want to see the data in Hebrew and I'll use standard charset for hebrew.

can you help me with that? after having a regular and working DB I'll use the impex again, but not with the UTF8 charset on.

Jerry
Thu 18th Dec '08, 3:11pm
You have to set the target database to the same char set as the source, as well as setting the char set in ImpExConfig, that is all I can tell you as that is all there is to do.

Yellow Slider
Thu 18th Dec '08, 3:56pm
You have to set the target database to the same char set as the source, as well as setting the char set in ImpExConfig, that is all I can tell you as that is all there is to do.

this is what I've done, and it presents Gibberish on the board.

Jerry
Thu 18th Dec '08, 4:17pm
this is what I've done, and it presents Gibberish on the board.

Then I'd think the clue is likely in your origional post :


I've used the Impex to convert 3.6.8 (who's DB is messed up)

Sounds like the source data is messed up.