On 4/20/06, Truth
---------- Forwarded message ---------- From: Truth
Date: Apr 20, 2006 1:12 AM Subject: bug report on wiki, about Chinese Characters To: opensuse-wiki@opensuse.org Related pages:
Those are pages containing Chinese Characters. It's actually some preliminary work for setting up a Chinese wiki, And unfortunately the bug makes that impossible so far.
I'll use the page below to explain what the bug is like.
http://en.opensuse.org/CN-Frequently_Asked_Questions
It's Chinese translation for the English FAQ page.
I finished the translation at 14:26, 12 February 2006, after a couple of times' edit. The page history is here:
http://en.opensuse.org/index.php?title=CN-Frequently_Asked_Questions&action=history
I was using the browser Opera, whose default encoding code is UTF-8, editing and posting. It seemed perfect when I just finished. And I did visit the page a week later, it was still fine(both in Opera/firefox). However, someday in March I went back again and found it all messed up. Some characters ( not all) can not ne recognized, and seems replaced by "�?�" or "�?".(in Opera/firefox/IE)
According to the page history, nobody has touched it.
The same issue happens to all Chinese pages on the wiki, such as. http://en.opensuse.org/CN-Communicate http://en.opensuse.org/CN-SDB:SDB .............. all full of "�?�"s.
I'm not quite sure if the problem is related to encoding or fonts. As I saw similar messed-up Chinese pages on the wiki when I first came here, I suppose it an existing bug. Maybe it's related to storing chars? Quite STRANGE.
Any insights? I'm willing to do anything like debug if needed.
Best wishes.
Well, I've had that problem with one of my clients (a chinese company) and the only way I could fix it was by changing the default php.ini charset (UTF-8) to gb2312. I'm not experienced in programming using/for these oriental charsets. That's why I strongly believe there might be some other change besides changing php.ini (like if I had shared hosting, for other people charsets). Of course your case is more specific since it changed from working to not working. Regards, -- Eduardo Bacchi Kienetz http://www.noticiaslinux.com.br/eduardo/