Re: Transliterate vs Unidecode

Michael Koziarski
Fri, 16 Jan 2009 22:16:47 -0000

> Agreed, it has absolutely no value unless you have an English
> application and want to get rid of ''those pesky unreadable
> characters''. Because sensible transliteration is dependent on both
the
> source and destination locale it''s really hard to solve. I think
it
> shouldn''t be included in Rails at all and should be solved in a
> separate library or gem.

When you step outside the latin-derived languages the transliterate
code is even more problematic.  馬鹿 should return baka but returns
'''',
the same is true of any korean, thai or cyrillic text.

This kind of thing is completely outside the scope of parameterize and
I can''t imagine we''ll ever get a decent solution baked in to
rails.
For applications which care about this kind of thing, parameterize
won''t ever be a decent solution.  They can and should just put the
values into the url like wikipedia does.  If there are bugs with
routes matching non-ascii values, we''ll fix them.


--
Cheers

Koz