You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I find "owers" really hard to understand, and it does not seem very common. I also have trouble translating it to French, the current translation is "débiteur" which is very technical.
Fortunately, it's not used much in the user interface.
What about renaming it to "beneficiaries"? It's the people that benefit from a bill, which means they need to participate financially.
The text was updated successfully, but these errors were encountered:
Hmm, right, good question, there are three kind of places where it's used:
UI: I checked again and "owers" is only used in the history log
code: changing it should not be very hard, but it has limited usefulness
API fields (such as JSON export): changing that would be a big breaking change
So, it does not seem to be a big UI problem for "normal" users (i.e. not looking at history and not using the API). I was basically annoyed by it when translating the history page.
I propose to leave this open in case somebody else has an opinion, but I'm no longer convinced it's worth changing.
I agree this is a bad naming : beneficiaries is better.
We could try changing this in the project and keep it in the API for backwards compatibility? I'm mainly concerned about breaking the API because we have clients out in the wild using it as-is.
I'm also okay with letting it as-is, and just changing this in the UI.
I find "owers" really hard to understand, and it does not seem very common. I also have trouble translating it to French, the current translation is "débiteur" which is very technical.
Fortunately, it's not used much in the user interface.
What about renaming it to "beneficiaries"? It's the people that benefit from a bill, which means they need to participate financially.
The text was updated successfully, but these errors were encountered: