I just sent a PR about that, once again, this is a confusion between transliteration and Urlization.

Transliteration is the process of going from 北京 to 'Bei Jing', from non alphabetic characters to latin alphabet ascii characters.

Urlization then is the process of going from "Bei Jing" to "bei-jing".
In my app, I extend the SluggableListener to set:

```php
class SluggableListener extends \Gedmo\Sluggable\SluggableListener{
    
    public function __construct(){
        $this->setTransliterator(array('\Khepin\DrupalTransliteratorBundle\Transliterator', 'transliterate'));
    }
}
```

Because Drupal has a pretty awesome transliterator for Chinese characters. But all this does is 'transliterate', not Urlize. Two different things.

I modified this piece of the code that we're currently commenting on right now about 8 months ago and there was already some discussion about this issue as those 2 processes were not absolutely clear. My guess is that the person who removed it did so because they don't use transliteration, or only basic ones that the Urlizer already takes care of. And since the default transliterator on the class is the Urlizer, it doesn't make a difference for them.

Hope this clarifies things.