the Magicball Network Forums

the Magicball Network Forums (
-   International (
-   -   日本語 (Japanese) (

Battler 2016-07-18 18:28

日本語 (Japanese)
日本からみんなさん、ようこそ!ここには、日本語でどうぞ。私は、日本 であるません、でも日本を話すことができます。
Everyone from Japan, welcome! Here, you can feel free to speak Japanese. I am not Japanese but I can speak Japanese.

Battler 2016-07-18 18:29

Is there a word filter or something? For some reason, the 人 character in the post above above became garbled.

Edit: But it's fine in this post. Test: 日本人で.

Edit: Again fine... no idea why then it's getting garbled in the post above.

Battler 2016-07-18 19:48

And now half of my first post is gone.

Neko 2016-07-20 14:58

Can you reproduce the error?

Or have any idea what the issue is?

Battler 2016-07-28 20:54

Let me test again: 日本からみんなさん、ようこそ!ここには、日本語でどうぞ。私は、日本 ��であるません、でも日本を話すことができます。

Battler 2016-07-28 20:55

Now it's even more screwed up. I think the forum database's encoding needs to be change to UTF-8.

Neko 2016-07-28 21:50

I dont have sql acces unfortunately....

Reek 2016-08-05 18:29

Well, let's take comfort in the fact that it doesn't really matter since no one ever comes here anymore.

Polaris 2016-08-27 22:31

Reek, don't you know that it doesn't matter ? It must work, where it's useful or not is beside the point :p

Battler 2016-10-25 05:31

I found the issue: After the Japanese text is converted to UTF-8, the offending part has these characters: 人 . But for some reason, vBulletin changes them to � �� when rendering them. It does seem like vBulletin isn't liking that particular sequence of bytes.
Edit: And every time that sequence appears, it gets reencoded, so if the borked text is passed, it gets even more borked. Maybe there's a word filter that's messing things up?

The weird thing is that when I click edit post, the text is fine there. So it only gets borked when the thread is shown to the user. Test: 日本の人, 日本人で.
日本からみんなさん、ようこそ!ここには、日本語でどうぞ。私は、日本a 人であるません、でも日本を話すことができます。

Edit #2: It screws up the text if a specific combination of characters is in a specific position in the line. Above, I added one space, and the mess up went away.

Edit #3: It has to be any non-ASCII character at that specific position in the line. Specifically, the first 33 characters are fine, but if the 34th character is non-ASCII, it gets messed up.

Edit #4: Look at this line, you will see a space in the middle of it, even though there should be none:
abcdefghijabcdefghijabcdefghijabcdefghijabcdefghijabcdefghijabcdefghijabcdefghijabcdefghijabcdefghij abcdefghijabcdefghijabcdefghijabcdefghijabcdefghijabcdefghij

So basically, when vBulletin thinks there's a very long live without spaces, it automatically inserts one. The problem is, Japanese text has no spaces (neither does Chinese text for that matter), and probably because the database encoding is not set correctly, it inserts the space in the middle of multiple bytes encoding such a character, messing it up. Most likely, it's designed to prevent spuriously long lines from messing up the layout, and it's doing things wrong because the database encoding is not set right, causing the vBulletin backend to interpret the characters as most likely ISO 8859-1 (Latin I / Western Europe) rather than the correct UTF-8.
In short, elmuerte needs to change the database encoding to UTF-8. Until he does, it is best to manually insert a space where you see a mess up occurring.

All times are GMT +2. The time now is 13:21.

Powered by vBulletin®
Copyright ©2000 - 2022, Jelsoft Enterprises Ltd.
Copyright ©2000 - 2022, the Magicball Network