Like all of these permalink solutions, friendly ID uses the parameterize
method to convert a string into a URL safe string. like so:
require 'active_support/all'
puts "Oh Hai There".parameterize
=> oh-hai-there
The problem comes in when you use non ASCII strings, which parameterize replaces with an empty string, causing your problem:
# encoding: UTF-8
require 'active_support/all'
puts "신품".parameterize
=>
ActiveSupport provides a way to change non ASCII strings to a close approximate via the transliterate
method.
# encoding: UTF-8
require 'active_support/all'
include ActiveSupport::Inflector
puts transliterate("Ærøskøbing")
=> AEroskobing
But, if it doesn't know about a character, it'll default to ??
# encoding: UTF-8
require 'active_support/all'
include ActiveSupport::Inflector
puts transliterate "신품"
=> ??
But, you can tell transliterate how to handle the characters. So in a Rails model
# Store the transliterations in locales/en.yml
en:
i18n:
transliterate:
rule:
신: "abc"
품: "def"
puts transliterate "신품"
=> "abcdef"
So, you can use transliterate(title).parameterize
instead of just parameterize. And if you get the korean alphabet into transliterate section, you're close to golden.