Support filtering on translation values in editTexts about localisation HOT 6 CLOSED

If you switch the language to English don't should see the key instead of the translation? Because if you do then you can filter by that key.

from localisation.

Not if we receive a screenshot from a user of a dialog that only appears in certain cases (for example)

from localisation.

It would be really useful

This is and edge case, more like it would be extremely rarely useful.

When this happen the user can still switch to en and determine the key. If he does not know how to do that and instead sends you a printscreen you can easily search by the translation in the JSON file and get the key.

But if you want to make a PR for this to implement it in a cleam manner be my guest.

from localisation.

you can easily search by the translation in the JSON file and get the key.

Those responsible for translations don't have direct access (nor proper knowledge to handle) such files though.
I'll see how cleanly I can implement it and PR if so.

Given the current structure the best implementation method would likely be to filter by value only if no results are returned (to reduce regular load)

from localisation.

Given the current structure the best implementation method would likely be to filter by value only if no results are returned (to reduce regular load)

I think that the best approach would be to filter by both (key OR value) at all times. Are you experiencing performance problems with the current filter?

from localisation.

Are you experiencing performance problems with the current filter?

No I'm not, but given the added complexity the double-filter would introduce I expect a (slightly?) noticeable slowdown for lower-end devices; This shouldn't be a big issue for the translation page itself though (less likely to be a low-end device)

I'll add it at all times

from localisation.