>Could you provide some comparisons between the effectiveness of your *.dat based implementation, vs. our array mapping?
I don't build .dat file, owner is "thinman" - http://www.silverstripe.org/ForumMemberProfile/show/8091.
>It looks like your mapping is a bit more extensive,
1. Yes, it's big true.
>but how is it conceptually different?
2. Your $table array has very limited set of chars
3. Transliterator.php (whole file) has to be saved as UTF-8. Don't forget for win OS's users (less experienced).
>If you implement your module as a subclass of Transliterator (with toASCII() method), you can just exchange the built-in functionality in core.
3. Yes it's true, but I'm using official SS 2.4 (not svn) version and I want to use only official version.
What can I say or I explain problems to my clients?
>By the way: Your Transliterate controller is unsecured, which is a bit odd - not security critical, but basically you allow the world to use websites with this module as a free transliteration service ;)
What do you mean? Director::addRules is insecure?
