Hello, I would like to ask you about Slug 's Japanese response.
If I choose encoding with slug generation method, the URL will be in Japanese, but when trying to tweet from the site share button, url will not be recognized correctly.
Does anyone have a solution?
Could you post a link to a forum where this is happening?
Thank you for your quick reply!
What browser / OS is showing the issue? Can you post steps to reproduce the issue?
It looks alright to me.
My problem is that the topic’s URL is not correctly recognized as a URL after being tweeted!
Oh, I didn’t try to tweet it. I guess Twitter doesn’t support such URLs. Maybe we should always share the URL without slug in that case.
Regarding the choice of encoding with slug generation method, I think that discourse needs to encode url and shorten it in terms of posting function to SNS.
So this is Twitter’s bug, not ours?
This is not twitter’s bug.
When sharing with Twitter, since url is recognized as a character string, Twitter can not be recognized as a URL.
So we need to urlencode it before passing off to share?
Yes
I think that Chinese and Korean have similar problems as well!
When is this bug resolved? 
It is not a Bug, it is a Feature request.
I expect it will be resolved once a suitable Pull Request is submitted.
@misaka4e21 can you have a 
at this?
Able to reproduce.
I’m to check it.
PR has been merged in August 2018