Earlier today, someone posted a topic with some hiragana and kanji in the topic title:
Try copying the URL of that topic and pasting it into a new tab. The page doesn’t load for me on Chrome, Safari, or Firefox on macOS. I suspect that this is because there is kanji and hiragana in the permalink. I put some kanji and hiragana in the title of this topic to test this theory.
I’m guessing Ember doesn’t handle routes with non-ascii characters correctly. Links to the topic work, however, because Ember handles transitions within an app that’s already loaded differently.
It looks like navigating directly to this topic doesn’t work either. I thought it was a Discourse issue, but I experimented on the Discourse sandbox and it stripped the non-ASCII characters out of the permalink, so it works.
Ha! I’m going to let the Discourse maintainers know about the bug shortly. They’ve been very responsive in the past, and this one’s kind of a doozy for people using non-ASCII permalinks (like us).
Hmmm, the problems is related to permalink/slug encoding, but not the entire cause. They’ve clearly supported permalinks with non-ASCII characters in the past, but a recent change looks like it’s generating multiple redirects between the encoded and un-encoded versions of the URL.
Yep, I experienced a related issue when trying to post a link to a definition on Weblio earlier tonight. Clicking Paste kept mangling it into all the letters and % crap, which brought up a 404 on weblio. Eventually I manually typed it in and made sure the link was not alone on the line, so it converted into a link rather than a link-box, and that made it work. (A workaround for now while Discourse hopefully fixes this back.)
That’s what I thought. Last activity in the thread Blake posted was 14 hours ago, and said it’s mainly because Discourse is on Rails 4, but there’s a fix in Rails 5, apparently.
