# Disabling English slugfier for topic's URL in Korean language setting

**URL:** <https://meta.discourse.org/t/disabling-english-slugfier-for-topics-url-in-korean-language-setting/23780>\
**Category:** Product Support\
**Created:** [8 يناير 2015، 1: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:** 8

<div class="post-metadata">

**Author:** ![winterbox](https://avatars.discourse-cdn.com/v4/letter/w/6de8d8/32.png) [@winterbox](https://meta.discourse.org/u/winterbox)\
**Post date:** [9 يناير 2015، 5:42ص UTC](https://meta.discourse.org/t/disabling-english-slugfier-for-topics-url-in-korean-language-setting/23780/8 "2015-01-09T05:42:10Z")

</div>

I don’t know how was it originally.

But not long ago, there was `transliteration` filter applied. So slugs were made Korean → English weirdly.  
I asked @sam to disable that feature for Korean language setting.

Also I told him that in my country, Korean slugs( ex. `/t/안녕하세요-여러분-반갑습니다`) are not that commonly used. We prefer just English letters and numbers like `/topics/###`

If Discourse slugfier accepts Korean letters _exactly_ (Not transliteration),  
I think the best way is that Admin can choose the URL types like Wordpress:

![](https://global.discourse-cdn.com/meta/original/3X/f/7/f7a1b953be0d238f45102b69d35396d23b545dec.png)

But I am not sure about Discourse slugfier mechanism, I am not an expert here, so I just report them about my opinions. 😄

---

_[View the full topic](https://meta.discourse.org/t/disabling-english-slugfier-for-topics-url-in-korean-language-setting/23780)._