Ah, the horsebird.
The fiasco you're referring to is the time when the game initially launched, the game was filled with so much kanji (the Japanese version of the Chinese alphabet), it made everyone's brain hurt even just to read them. Try to imagine almost every in-game item/ability/feature written in something like Shakespearean English, and it's even worse than that. Being traditional my ass.
The multitude of headaches initiated from the fact that the most kanji letters/symbols can be pronounced in 2(+) different ways, and although people could fathom a guess as to what they mean because the each kanji symbol has an overall meaning behind each one (as an interesting side note, we can use this to our advantage and sort-of communicate with the Chinese through these letters), the problem was that we couldn't figure out the proper way to pronounce them since all these items are supposed to be fantasy and thus real-life equivalents didn't exist. To put it in perspective, it's like telling the English-speaking community to pronounce something like 'Xnvlzpyl" correctly with no references.
This was a huge problem because if we didn't know how to pronounce them, we couldn't type them out. Us Japanese use the romaji system when we type our language with our keyboards, and to put it into simple terms it's pretty much typing the language out in English pronunciation (ex: to type the Japanese letter 'na', we type 'n' and 'a' into the keyboard and the program automatically converts the input into the Japanese character), thus, we couldn't even communicate each other the in-game terms.
This is further complicated by the fact that some of the in-game text was really small, and because kanji has some complex lettering there were times where we couldn't tell which symbol was which since not all of us have perfect 20/20 visions. So yea, an idea of why most of us were in such an uproar when it happened.
Thankfully, this was later corrected by patch that converted most of these fulfilled names into katakana, but because the problem I described in the previous post happened after this patch was put into place, the fiasco really didn't have to do anything with it.