PDA

View Full Version : WordPress localization problem



e2e
03-01-2006, 05:20 PM
Hi,
I'm using WP on bluehost but i can't use it in my own language. Everything seems ok on WP side.

It seems our gettext support enabled. But i still need to ask. Does anyone have this kind of problem?

I have no idea what could be the problem...

solowoo
03-12-2006, 12:08 AM
I have exactly the same problem. According to the materials I read, localization should be a pretty simple process. I have uploaded the .mo file and modified the wp-config.php as instructed, but still got an English WP instead of a Chinese one which I need.

I even tried a fresh install, once using a Chinese WP pack. Strangly, the installation was in Chinese, but as soon as it was done the website became English again.

I have also tried removing php.ini as well as altering the default coding of the MySQL database from latin to utf8. It still does not work. So I am thinking if it could be due to some settings on the Bluehost servers.

spencer
07-18-2006, 01:54 PM
This is a workpress bug. You can correct this by editing gettext.php in the wp-includes folder and replacing $MAGIC1 and $MAGIC2 with:

$MAGIC1 = 2500072158;
$MAGIC2 = 3725722773;

Kaizer
08-24-2006, 02:08 PM
This is a workpress bug. You can correct this by editing gettext.php in the wp-includes folder and replacing $MAGIC1 and $MAGIC2 with:

$MAGIC1 = 2500072158;
$MAGIC2 = 3725722773;

Thanks spencer. It's work!

djmcdonald
01-17-2008, 04:59 AM
I am having the same problem, but am not sure what is meant by replacing "$magic1" and "$magic2" with "$MAGIC1 = 2500072158" and "$MAGIC2 = 3725722773" as there is more than one instance of "$magic1" and "$magic2". Would someone be able to show how the troubled lines would be replaced in terms of a "before" and "after" or the like?

Much appreciated!

Early Out
01-17-2008, 05:05 AM
I am having the same problem, but am not sure what is meant by ....This is an old thread, and the solutions here won't cure the current problem. See this thread (http://www.bluehostforum.com/showthread.php?t=11536), instead.