2

For a couple years now, we've had support for furigana on JLU. It always worked pretty well, and although there've been a couple small issues, we've been able to work around them.

Right now, though, furigana appears not to work at all! For example, see this answer which is supposed to be loaded with furigana. The text between {} should appear above the text between [] that comes immediately before it.

Instead, it's as if the furigana script is not run at all. We see the brackets and the text appears between those brackets. The same has been true in every question I've looked at with furigana, both on the main site and meta, in answers and in comments.

It appears to be broken in multiple browsers. I've tested on SeaMonkey 2.20 on Linux, and in Chrome 28.0.1500.95 on Linux. It happens while logged in, and while logged out. And I've never set any "furigana preferences". So I don't think it's a problem on my end.

Any idea what happened to furigana support?

  • Probably related to the fix to this. Can you check the options (link in the footer)? – Oded Sep 12 '13 at 9:39
  • @Oded The options in the footer don't appear to do anything at the moment. (Well, they successfully remember whatever settings I enter, but they don't have a visible effect on anything else.) – snailcar Sep 12 '13 at 9:54
  • OK. Looks like I broke something. Am looking into it - do you have more examples of issues? I need to know when something is fixed... and not being able to read the language doesn't help. – Oded Sep 12 '13 at 9:56
  • There are lots of examples of furigana. The most recent example is here, which should make a decent test case. Where it says 空気{くうき}を読{よ}む, it should look like 空気を読む, but with the text くうき and above it. Another example is in the title of this question, where the characters should appear above the characters written . – snailcar Sep 12 '13 at 10:01
  • More examples: here, in the quoted section. しょ and ある should appear above 背負 and . And in this question and its answer, in the second quote in this answer, in this comment, ... – snailcar Sep 12 '13 at 10:05
  • 1
    The problem is the function getSetting is being called like getSetting[...] rather than getSetting(...). If you replace the square brackets with round brackets, it fixes the problem. (I didn't know you could do that at all, but you learn something new every day!) – cypher Sep 12 '13 at 10:26
  • @cypher - yep. Fix is coming out. Was a silly oversight by me. – Oded Sep 12 '13 at 10:29
3

In an attempt to fix an issue with the user script using localStorage, I inadvertently completely broke its functionality altogether.

This is now fixed.

You must log in to answer this question.

Not the answer you're looking for? Browse other questions tagged .