• http://meta.japanese.stackexchange.com/questions/1486/do-we-really-need-ruby-characters-all-the-times and http://meta.japanese.stackexchange.com/questions/1489/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.

• http://meta.japanese.stackexchange.com/questions/1484/%e7%9b%b4-and-%e5%96%9d-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).

• http://meta.japanese.stackexchange.com/questions/1351/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.

• http://meta.japanese.stackexchange.com/questions/1364/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.

• http://meta.japanese.stackexchange.com/questions/1318/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).

• http://meta.japanese.stackexchange.com/questions/1398/struckthrough-japanese-text-doesnt-get-wrapped-in-a-lang-ja-span and http://meta.japanese.stackexchange.com/questions/1314/ultra-minor-bug-with-the-jlu-furigana-extensions

  Have been fixed.

• 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.

• https://japanese.meta.stackexchange.com/questions/1484/%e7%9b%b4-and-%e5%96%9d-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).

• https://japanese.meta.stackexchange.com/questions/1351/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.

• https://japanese.meta.stackexchange.com/questions/1364/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.

• https://japanese.meta.stackexchange.com/questions/1318/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).

• https://japanese.meta.stackexchange.com/questions/1398/struckthrough-japanese-text-doesnt-get-wrapped-in-a-lang-ja-span and Ultra-minor bug with the JLU furigana extensions

  Have been fixed.

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

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)

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:

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.