Technically, yeah… but there’s a small update:
I’ve just tested this function out… and it considers different matches, than objects in replacements (when you make a request for JSON). I’ll send screenshots in a moment…
So… here’s when I checked word Monsz. My app thinks, that Mons is the best match for Monsz, JSON API considers mąż, as the best match, what I agree with…
Sorting the matches should probably be left to the backend, i.e. LT. If LT doesn’t get it right, we should improve it. There are ideas about this, and it’s already somewhere on the to do list.
I haven’t expeirenced any completely missed replacements in your JSON API so far. There was one situation I remember, where the first replacement, wasn’t the right replacement. Still, it wasn’t a big miss though, so I don’t really have anything to complain about by now.