Furigana engine update for December 2015

Question

It's that time of year again, where the Furigana engine has been starting to show cracks, and there's the feeling it needs to be duly resuscitated.

I've been trying to employ, as much as I reasonably can, a balanced approach in resolving, or mitigating, the following issues in the (now live) new version of the Furigana engine:

• Do we really need ruby characters all the time? and The state of browser support of Furigana, and bottom-aligned Furigana

  First and foremost, I've tried to put focus on reducing the visual impact of Furigana, and making sure things render consistently across browsers and OSes (whether mobile or desktop). Most of the changes can be seen in my answer to the latter question.

• 直 and 喝: Han unification, and being able to write Japanese on JSE

  With {{(lang code):text}} tags, you will be able to insert <span lang="(lang code)">text</span>, and use a font for that language (as chosen by the OS).

• Fix furigana on the mobile version of our page

  The Furigana engine should fully be supported in the mobile site. I'll ask about whether it can be added when asking for the update to be performed.

• User Experience: Discovering the Formatting Syntax Documentation

  I've added "Furigana/Japanese extension help »" links below the inline editors to make sure people can find the docs.

• Encouraging participation from native Japanese speakers: translating posts

  I've added basic translation tage: you can add # Japanese/# 日本語/# 和訳 and # English/# 英語/# 英訳 header tags at the start of lines to allow for tabbed translations.

  This is simplified a lot from what I previously coded to try to keep things simple. I might extend this if it gets used. If it doesn't and it needs to be removed, the answers will be backwards reversible (as they're just standard headings).

• Struckthrough Japanese text doesn't get wrapped in a lang="ja" span and Ultra-minor bug with the JLU furigana extensions

  Have been fixed.

---

I might wait for a week or two before asking for an update to check everything's stable, but if you'd like, you can try the new engine on Chrome or Firefox) in the meantime by:

1. Using adblock plus [Chrome/Firefox] to block //sstatic.net/js/third-party/japanese-l-u.js?v=9 (the current version used on JLSE)

2. Installing Greasemonkey(FF)/Tampermonkey(Chrome)

3. Then going to http://gist.github.com/cyphr/6536814, and clicking "Raw" in the top right.

---

Please let me know if there's any issues I've missed/anything you think should be changed etc.

Answer 1

Minor issues:

1. Very wide furigana causes problems in comments, as in this test comment.

   Here's what I typed in to make that comment (plus a zero-width space to prevent it from rendering):

   Testing: [漢字漢字漢字漢字漢字漢字漢字漢字漢字漢字漢字漢字漢字漢字漢字漢字漢字漢字漢字漢字漢字漢字漢字漢字漢字漢字漢字漢字漢字漢字漢字漢字漢字]​{ああああああああああああああああああああああああああああああああああああああああああああああああああああああああああああああああああ}

   And here's how it renders:

   

   This doesn't happen without the furigana engine. If I write 漢字漢字漢字漢字漢字漢字漢字漢字漢字漢字漢字漢字漢字漢字漢字漢字漢字漢字漢字漢字漢字漢字漢字漢字漢字漢字漢字漢字漢字漢字漢字漢字漢 without any furigana markup, it wraps properly.

   ---

2. I'd like to disable the new mouseover when the furigana consists of emphasis dots, like in the following:

   文字を[強調]{﹅・﹅}する

   This form of emphasis is useful for Japanese and the furigana engine gives us an easy way to do it, and now that we have furigana on mobile I think I might like to use it a little bit more often. But it looks weird when we mouseover:

   

   Since the mouseover is already disabled for pitch accent (it doesn't show up for [やじろべえ]{LHHLL}), maybe we could add one more special case? :-) If we do this, I think we would want to add a special case for at least ◦, ﹆ and ﹅.

   ---

Neither of these is likely to come up very often.

Answer 2

Thank you for the update! It's working very well in my iPhone Safari too. However, I found a tiny problem in seemingly limited environments:

It seems the paragraph with {{​pad}} has oversized characters when ruby attached, which doesn't on my PC Firefox.

PS
Is there any possibility the furigana feature gets imported to official mobile app?