# Disabling English slugfier for topic's URL in Korean language setting **URL:** \ **Category:** Support\ **Created:** [2015年一月8日 13:12 UTC](https://meta.discourse.org/t/disabling-english-slugfier-for-topics-url-in-korean-language-setting/23780 "2015-01-08T13:12:49Z")\ **Posts on this page:** 1\ **Showing post:** 10
**Author:** ![fantasticfears](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/fantasticfears/32/119608_2.png) [@fantasticfears](https://meta.discourse.org/u/fantasticfears)\ **Post date:** [2015年一月10日 05:05 UTC](https://meta.discourse.org/t/disabling-english-slugfier-for-topics-url-in-korean-language-setting/23780/10 "2015-01-10T05:05:25Z")
Actually, some guys appeal to add control over this in Chinese communities. However, I don’t care this. Most Chinese users won’t notice the slug. I may wrong. > [@winterbox](#): > > If Discourse slugfier accepts Korean letters exactly (Not transliteration),I think the best way is that Admin can choose the URL types like Wordpress: Slug may be helpful for SEO, or not. At least, the default `topic` is sufficient. Now I am open to your proposal about options here. But the options should be a site setting. @winterbox Can you open a feature for this option to help me track this proposal. * * * > [@sam](#): > > Old browsers don’t support this but I guess you could opt in . [zh.wikipedia.org](http://zh.wikipedia.org) use Unicode as url since its start at 2002. > [@ben\_lubar](#): > > [http://example.com/안녕하세요-여러분](http://example.com/%EC%95%88%EB%85%95%ED%95%98%EC%84%B8%EC%9A%94-%EC%97%AC%EB%9F%AC%EB%B6%84) is a valid URL Some programs can’t handle it very well, they may show a long encoded string when pasted some url into them which looks bad. Leave a site setting to change is ok. --- _[View the full topic](https://meta.discourse.org/t/disabling-english-slugfier-for-topics-url-in-korean-language-setting/23780)._