While testing this extension on Flarum beta 16 I noticed that all my test data was already handled fine by Flarum without any additional extension.
A big change actually happened last year with the release of Flarum beta 12. In that release, Flarum's basic slugger method was replaced with Laravel
Str::slug method, which itself uses the
to_ascii function of https://github.com/voku/portable-ascii
This means that since Flarum beta 12, FoF Transliterator is probably no longer needed by most of its users.
FriendsOfFlarum has been trying to reduce the number of extensions to maintain by eliminating the least used of them. Based on those observations, FoF Transliterator seems to have become a mostly redundant extension that could be a candidate for end of life.
The extension still receives hundreds of downloads via Packagist, which leads me to wonder if some people are just installing this extension as a placebo, not realizing the default behavior is mostly identical. Unfortunately we don't have enough data to know if those are new forums or just existing forums continuing to update their existing extensions. We also don't have any telemetry to know which of the transliterator options in this extension are most used.
My question then is, does anyone actually benefit from the Behat or PHP transliterators bundled in this extension versus the default portable-ascii now used by Flarum? Do you have example texts or languages that actually require this extension to work?