So... this just happened in a reading test... any ideas? - Feed Post by MintyHippo
Comments 14
In case you need it to test beeant: http://japaneseclass.jp/readings/read/309709
I tried that reading test and exactly the same thing appeared in the question. If you click the audio button, it plays the audio which matches "to bring / to take / to bring about", so from this you could complete the question...
The "slioriginalspace" thing is interesting for a random string of letters. Searching Google for that string returns only 4 results and they are all for JCJP trends pages!
https://www.google.co.uk/search?q=slioriginalspace
Incidentally, does the audio for もたらす sound more like like もたらさ to you?
If you check out the dictionary pages for this phrase in both its okurigana variants, they are pronounced differently to eachother! :P
http://japaneseclass.jp/dictionary/%E9%BD%8E%E3%81%99
http://japaneseclass.jp/dictionary/%E9%BD%8E%E3%82%89%E3%81%99
The message sent from the server contains both the following:
・non-furigana version of the question, written as "もたらす → 齎す"
・furigana-added version of the question, witten as that mess in your screenshot.
Because it is the furigana-added version that is shown in the quiz question (and its text is messed up within the message sent direct from the server), there is no way to make these questions display properly ourselves.
I'm fairly sure I know what triggers the problem. 齎 isn't a common use kanji and is even outside of the jinmeiyou list. For every reading question with a non jouyou list kanji, I'm fairly sure that the question will always appear messed up like this. It's like whatever is automatically adding furigana to the questions is unable to process certain types of less common kanji.
I've experienced problem in other readings quizes and mentioned this issue recently (although I was more concerned about the "main issue"):
http://japaneseclass.jp/feeds/comment/5488- Yeah it's the same kind of problem you had before. I just thought it was kind of ah... interesting? In the way that the display went totally off the rails.
Also yes it sounds like もたらさ。 
And that's where you use you master ball and get that pokemon!
I just fixed this problem, there was some problem with the encoding. thank you for the report! :)- @beeant Nice! I had another reading I didn't finish because of this bug. Went back to that reading and it was fixed. :)
Still encountered the other bug when I finished that quiz -- user has no weak reading vocabulary in profile, so it has no recommended next readings to list after completing quiz with 100% correct. And then this causes the refresh page 503 error with the reading quiz results page not loading (which crashes the site!).
@DS25 I've played the older pokemon games but struggled to figure out what you meant. Is that a reference to that wierd "missingno." glitch pokemon? you don't wanna catch that one! :D - I just did a reading quiz with 100% correct, and I didn't cause any crash. I'm not sure yet what the problem is, but I have suspected some part of the codes and did a little fix. Can you try it again please?
- Did you do it on your "beeant" profile, because that one DOES has weak reading vocabularies. My profile has 0 weak reading vocabularies. This is why I encounter the issue while you do not. :)
- oh I missed that you mentioned user that has no weak reading vocabulary. how did you even know this? I fixed the problem in that part. did you hack into the source code? lol
- On my other account, I realised that the main difference for why umaro86uk never had this problem might be that it had weak vocabularies.
So I did lots of suggested readings, never encountering the error, until I cleared all umaro86uk's weak vocabulary. On completing the final reading that I needed to do to clear my weak vocabulary, it crashed for the very first time on that account!
The error popped up every time after this until I answered a question wrong, then the error never popped up on quizzes until I had no weak vocabulary again. Was pretty solid evidence. ^^
I don't do hacking and stuff, but I did check the websocket message and it had an array for suggested readings after completing the final question. I thought maybe it would encounter a problem if this array was empty. So further evidence. :P - Anyway, I just completed another reading, getting 100% correct while having no weak vocabularies, and the results page loaded! So this bug is fixed at last. Yay! Thanks. :)
- nice! :) you're so komakai! you even know the cause of that i actually the part of the codes that take weak list into account inside the logic. :)
- It was actually a reference to some of the old "fake save" glitches ;)
- It was actually a reference to some of the old "fake save" glitches ;)
